This particular portion of the transition is done in -proposed, which
allows the builds being complained about to build again. The rest of
the transition is still ongoing, but there's no point keeping this bug
open until it's done.
** Changed in: nettle (Ubuntu)
Status: Confirmed = Fix
** Changed in: nettle (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463875
Title:
Crash in libnettle6 on armhf and powerpc archs
To manage notifications
** Tags added: lt-category-noimpact
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463875
Title:
Crash in libnettle6 on armhf and powerpc archs
To manage notifications about this bug go to:
** Description changed:
Currently, in wily, some landing silos are blocked now, due to a
segfault occurring when attempting to run certain test binaries, which
depend on the gnutls stack. Most notably so far, I've hit this issue in
projects which are using QtNetwork or libcurl for network
Log in the bug description is from:
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-022/+build/7526566
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463875
Title:
Crash in
** Description changed:
Currently, in wily, some landing silos are blocked now, due to a
segfault occurring when attempting to run certain test binaries, which
depend on the gnutls stack. Most notably so far, I've hit this issue in
projects which are using QtNetwork or libcurl for network
** Changed in: nettle (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463875
Title:
Crash in libnettle6 on armhf and powerpc archs
To manage notifications
gnutls is a core part of the system, so the version in the release
pocket that is already built against libnettle4 is already installed in
the base image, along with libnettle4, yes. Because there isn't a newer
version of libnettle4 available, it is not being upgraded at the start.
On Wed,
There's nothing to fix i nettle. but other packages depending on it need to be
rebuilt in order.
I don't know how Ubuntu manages library transitions like this, but you can have
a look at https://release.debian.org/transitions/html/auto-nettle.html (check
the good box).
What I find strange is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nettle (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463875
Title:
** Bug watch added: Debian Bug tracker #787620
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787620
** Also affects: nettle (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787620
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Description changed:
Currently, in wily, some landing silos are blocked now, due to a
segfault occurring when attempting to run certain test binaries, which
depend on the gnutls stack. Most notably so far, I've hit this issue in
projects which are using QtNetwork or libcurl for network
12 matches
Mail list logo
