On 2015-05-06 Niels Möller <ni...@lysator.liu.se> wrote:
> Andreas Metzler <ametz...@bebt.de> writes:
>> No, that does not work. wget would be looking for unversioned
>> references to nettle-symbols, and given the choice ot two differently
>> versioned ones it will not prefer either over the other.
> I see. So for a really smooth transition from jessie and up, including
> partial upgrades, one would need an update with nettle-2.7.x with
> versioned symbols, and all packages linking explicitly with nettle
> rebuilt against that version (about 30 packages, if apt-cache rdepends
> libnettle4 is a good way to list them). And try to ensure all of these
> packages are upgraded *before* the packages with nettle-3.1 and current
> gnutls are installed.
> Maybe too complicated to be worth the effort?
> Are there any shortcuts, which improve the situation over the status
> quo?
[...]
Hello,
What I originally had in mind was a a part of things listed above:
1. Update nettle-2.7.x to versioned symbols.
2. Let it propagate to sid (unstable) from testing.
3. Trigger rebuild of all rdepends, they will quickly propagate to
testing, too.
At this point both sid and testing ("stretch") would be ready for a
painless upgrade to nettle3, with no breakage in any system upgraded
to this point. (And for sid/testing users imho one can expect systems
being kept reasonably up to date.)
1. Upload nettle3. *Optionally* the nettle3 library packages could
temporarily have a Breaks: on the list of binaries that were built
against unversioned nettle-2.7.x, enforcing an upgrade to the rebuilt
versions.
2. Trigger rebuild of all rdepends.
3. Wait for propagation to testing. Some months later the Breaks: can
be dropped.
---------------
This would not improve the jessie->stretch upgrade in two years.
However I do not think that is that big of an issue. I guess almost
all crash-candidates (direct link against a nettle library, and
indirect link via another library) will involve gnutls as the library
bringing in the second indirect link to nettle. jessie-->stretch will
include a gnutls soname change (3.4.x), which afaict solves the issue
as a side-effect:
Package release Depends
wget jessie libgnutls-deb0-28->libnettle4 / libnettle4
wget stretch libgnutls30->libnettle6 / libnettle6
So there is no mixup of different nettle versions in the wget linkage
possible.
The effort involved would not be two bad, imho. However I am not
totally sure it is worth it. Since nettle2 and nettle3 will use the
same source package upgrading stretch to nettle3 will need to happen
by
a) rebuild everything in sid against nettle3,
b) Only when all rdeps are ready to propagate at the same time to
stretch (old enough, no new rc-bugs), all of them go into stretch at
the same time.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
