Bug#817035: marked as done (transition: qwt)
Your message dated Sun, 13 Mar 2016 23:39:02 +0100
with message-id <56E5EC06.7000601@debian.org>
and subject line Re: Bug#817035: transition: qwt
has caused the Debian Bug report #817035,
regarding transition: qwt
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
817035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817035
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Dear RT: this is a request to transition qwt from experimental to unstable.
As the auto tracker noted this release has an API/ABI breakage without
upstream doing a proper SONAME bump and so Qt4's libqwt6 is transitioning to
libqwt6ab1.
It also adds Qt5's libqwt-qt5-6.
So rdeps can either use the Qt4 version or migrate to Qt5.
Current rdeps and their statuses wrt this transition:
- libterralib: it's not marked in the auto tracker because they are mixing
Qt4 and Qt5 and it's probably not using libqwt at all. I already filed a bug
for them.
- nlkt: source already builds against libqwt-qt5-dev... in unstable
This basically means: binNMU all archs except amd64, as the auto tracker
shows.
- qgis: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784514#27
So maintainers are ready for the transition. It will also help with removing
qt4's webkit rdeps.
- qsapecng: It works as well with qwt 6.1.2 as with qwt 6.0.0 so the package
seems able to be binNMUed. It segfaults on exit (see bug #816898) but this
doesn't seems to be related to qwt (or at least the transition shouldn't
neither improve nor worsen the current situation).
- zygrib: version in experimental needs to be pushed to unstable according to
#798875.
Ben file: the auto-tracker is about right, so let's keep it like that.
Kinds regards, Lisandro.
-- System Information:
Debian Release: stretch/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 07/03/16 18:22, Emilio Pozuelo Monfort wrote:
Control: tags -1 confirmed
On 07/03/16 13:43, Lisandro Damián Nicanor Pérez Meyer wrote:
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Dear RT: this is a request to transition qwt from experimental to unstable.
As the auto tracker noted this release has an API/ABI breakage without
upstream doing a proper SONAME bump and so Qt4's libqwt6 is transitioning to
libqwt6ab1.
It also adds Qt5's libqwt-qt5-6.
So rdeps can either use the Qt4 version or migrate to Qt5.
Current rdeps and their statuses wrt this transition:
- libterralib: it's not marked in the auto tracker because they are mixing
Qt4 and Qt5 and it's probably not using libqwt at all. I already filed a bug
for them.
- nlkt: source already builds against libqwt-qt5-dev... in unstable
This basically means: binNMU all archs except amd64, as the auto tracker
shows.
- qgis: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784514#27
So maintainers are ready for the transition. It will also help with removing
qt4's webkit rdeps.
- qsapecng: It works as well with qwt 6.1.2 as with qwt 6.0.0 so the package
seems able to be binNMUed. It segfaults on exit (see bug #816898) but this
doesn't seems to be related to qwt (or at least the transition shouldn't
neither improve nor worsen the current situation).
- zygrib: version in experimental needs to be pushed to unstable according to
#798875.
Ben file: the auto-tracker is about right, so let's keep it like that.
Go ahead.
The old shared libs just got removed from testing.
Cheers,
Emilio
--- End Message ---
Reply to: