To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the runtime library package.
I'm surprised at
+Provides: ${t64:Provides}
+Replaces: libadns1
+Breaks: libadns1 (<< ${source:Version})
I don't know why this isn't just a soname transition. But I think
probably people more involved in this have thoughyt this through.
(Perhaps this to do with making this a no-op on 64-bit arches.)
If you have any concerns about this patch, please reach out ASAP.
Although this package will be uploaded to experimental immediately,
there will be a period of several days before we begin uploads to
unstable; so if information becomes available that your package should
not be included in the transition, there is time for us to amend the planned uploads.
If what I have written doesn't indicate that something has been
overlooked, you should go ahead as planned. I guess I should avoid
uploading myself.
adns is not an "unusual" package, other than insofar as time_t being
part of an ABI-exposed struct makes it unusual.
I have just got an alert saying adns is now scheduled for autoremoval
due to #1061866.
My understanding was that you were intending to NMU to unstable after "several days". I have been holding off making an upload myself so as
not to interfere.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (2 / 14) |
Uptime: | 07:41:42 |
Calls: | 6,666 |
Files: | 12,213 |
Messages: | 5,336,185 |