Bug#796711: [Pkg-crosswire-devel] Bug#796711: sword: library transition is needed with GCC 5 as default

[Simon McVittie]

On Mon, 24 Aug 2015 at 11:24:19 +0100, Daniel Glassey wrote:
> A new version of the library (1.7.5) is imminent and will require a
> transition anyway. So we'll start planning the transition to libsword12.

Please do the v5 transition anyway; the wider libstdc++ transition has
eaten a month so far, and we would really like it to be over. The
release team are more likely to kick packages out of testing than waiting
for a new SONAME. As I think I mentioned at the Debian-UK BBQ,
there are ~ 300 transitions involving ~ 3000 packages at the moment,
so the people dealing with them would really prefer to see conservative,
minimal-risk changes.

If you had 1.7.5 already staged in experimental, it had already built
on all architectures, and you had test-built its rdeps successfully,
then going directly to libsword12 might be OK; but that doesn't
appear to be the case. The libsword12 transition can still happen in the
usual way (with a transition slot and so on) after the libstdc++ horror
has finished; there aren't many packages involved, so it should be an
easy one under normal circumstances.

Vaguely related to this, a ftp team member noted that there are open
RM bugs for bibledit-gtk and xiphos, which seem to be in the same
general area (bible study), and might get processed soon. If these
are of interest to you, please reply to the removal bugs and either
say "yes, this should be removed from unstable", or say what the plan
is for fixing the issues that led to the bug.

S

Bug#796711: [Pkg-crosswire-devel] Bug#796711: sword: library transition is needed with GCC 5 as default

[Julien Cristau]

On Fri, Sep  4, 2015 at 15:52:58 +0100, Daniel Glassey wrote:

> On Fri, Sep 04, 2015 at 02:48:45PM +0100, Simon McVittie wrote:
> > Vaguely related to this, a ftp team member noted that there are open
> > RM bugs for bibledit-gtk and xiphos, which seem to be in the same
> > general area (bible study), and might get processed soon. If these
> > are of interest to you, please reply to the removal bugs and either
> > say "yes, this should be removed from unstable", or say what the plan
> > is for fixing the issues that led to the bug.
> 
> I haven't worked out who I should contact yet but I uploaded a new version of 
> bibledit-gtk earlier in the week that 
> had been in experimental (bibledit-gtk_4.8-1). I uploaded the source as well 
> by mistake with bibledit-gtk_4.8-2. I 
> got a mail saying it had been uploaded but didn't get an ACCEPT email. After 
> I realised that I made some more changes 
> and uploaded bibledit-gtk_4.8-3 binary only which was to close the removal 
> bug and had the same thing happen.
> 

20150901000442|process-upload|dak|bibledit-gtk_4.8-2_amd64.changes|Error while 
loading changes: No valid signature found. (GPG exited with status code 0)
gpg: Signature made Mon Aug 31 23:00:14 2015 UTC using RSA key ID AF060C5A
gpg: Good signature from "Daniel Glassey "
gpg: aka "Daniel Glassey "
gpg: aka "Daniel Glassey "
gpg: WARNING: Using untrusted key!

jcristau@franck:~$ gpg --no-default-keyring --keyring 
/srv/keyring.debian.org/keyrings/debian-keyring.gpg --list-key AF060C5A
pub   4096R/AF060C5A 2013-08-08 [expired: 2015-07-27]

Your key's expiration date needs an update in the debian keyring.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#796711: [Pkg-crosswire-devel] Bug#796711: sword: library transition is needed with GCC 5 as default

[Daniel Glassey]

On Fri, Sep 04, 2015 at 05:07:50PM +0200, Julien Cristau wrote:
> On Fri, Sep  4, 2015 at 15:52:58 +0100, Daniel Glassey wrote:
> 
> > On Fri, Sep 04, 2015 at 02:48:45PM +0100, Simon McVittie wrote:
> > > Vaguely related to this, a ftp team member noted that there are open
> > > RM bugs for bibledit-gtk and xiphos, which seem to be in the same
> > > general area (bible study), and might get processed soon. If these
> > > are of interest to you, please reply to the removal bugs and either
> > > say "yes, this should be removed from unstable", or say what the plan
> > > is for fixing the issues that led to the bug.
> > 
> > I haven't worked out who I should contact yet but I uploaded a new version 
> > of bibledit-gtk earlier in the week that 
> > had been in experimental (bibledit-gtk_4.8-1). I uploaded the source as 
> > well by mistake with bibledit-gtk_4.8-2. I 
> > got a mail saying it had been uploaded but didn't get an ACCEPT email. 
> > After I realised that I made some more changes 
> > and uploaded bibledit-gtk_4.8-3 binary only which was to close the removal 
> > bug and had the same thing happen.
> > 
> 
> 20150901000442|process-upload|dak|bibledit-gtk_4.8-2_amd64.changes|Error 
> while loading changes: No valid signature found. (GPG exited with status code 
> 0)
> gpg: Signature made Mon Aug 31 23:00:14 2015 UTC using RSA key ID AF060C5A
> gpg: Good signature from "Daniel Glassey "
> gpg: aka "Daniel Glassey "
> gpg: aka "Daniel Glassey "
> gpg: WARNING: Using untrusted key!
> 
> jcristau@franck:~$ gpg --no-default-keyring --keyring 
> /srv/keyring.debian.org/keyrings/debian-keyring.gpg --list-key AF060C5A
> pub   4096R/AF060C5A 2013-08-08 [expired: 2015-07-27]
> 
> Your key's expiration date needs an update in the debian keyring.

Ah, of course. I updated the expiry and sent it to the debian keyserver last 
weekend so I'll email those RM bugs and 
prepare the transition patch and wait til the keyring is updated before doing 
any more uploads.

Thanks,
Daniel



signature.asc
Description: Digital signature

Bug#796711: [Pkg-crosswire-devel] Bug#796711: sword: library transition is needed with GCC 5 as default

[Daniel Glassey]

On Fri, Sep 04, 2015 at 02:48:45PM +0100, Simon McVittie wrote:
> On Mon, 24 Aug 2015 at 11:24:19 +0100, Daniel Glassey wrote:
> > A new version of the library (1.7.5) is imminent and will require a
> > transition anyway. So we'll start planning the transition to libsword12.
> 
> Please do the v5 transition anyway; 
[good reasons]

Hi Simon, Funnily enough as 1.7.5 wasn't as imminent as I thought I'd started 
preparing the transition so I should 
get that done either later today or at the weekend.

> Vaguely related to this, a ftp team member noted that there are open
> RM bugs for bibledit-gtk and xiphos, which seem to be in the same
> general area (bible study), and might get processed soon. If these
> are of interest to you, please reply to the removal bugs and either
> say "yes, this should be removed from unstable", or say what the plan
> is for fixing the issues that led to the bug.

I haven't worked out who I should contact yet but I uploaded a new version of 
bibledit-gtk earlier in the week that 
had been in experimental (bibledit-gtk_4.8-1). I uploaded the source as well by 
mistake with bibledit-gtk_4.8-2. I 
got a mail saying it had been uploaded but didn't get an ACCEPT email. After I 
realised that I made some more changes 
and uploaded bibledit-gtk_4.8-3 binary only which was to close the removal bug 
and had the same thing happen.

Regards,
Daniel


signature.asc
Description: Digital signature

Bug#796711: [Pkg-crosswire-devel] Bug#796711: sword: library transition is needed with GCC 5 as default

[Simon McVittie]

On 04/09/15 15:52, Daniel Glassey wrote:
> On Fri, Sep 04, 2015 at 02:48:45PM +0100, Simon McVittie wrote:
>> Vaguely related to this, a ftp team member noted that there are open
>> RM bugs for bibledit-gtk and xiphos, which seem to be in the same
>> general area (bible study), and might get processed soon. If these
>> are of interest to you, please reply to the removal bugs and either
>> say "yes, this should be removed from unstable", or say what the plan
>> is for fixing the issues that led to the bug.
> 
> I haven't worked out who I should contact yet

https://bugs.debian.org/ftp.debian.org

and more specifically

https://bugs.debian.org/797564
https://bugs.debian.org/797568

which I see you have contacted already. That was the right thing to do.

> I uploaded the source as well by mistake with bibledit-gtk_4.8-2.

All uploads of new versions to Debian need source code; it's kind of the
point :-)

Redundantly uploading the orig.tar.gz even though it is in the archive
already (due to using e.g. debuild -sa) is harmless, apart from wasting
a bit of bandwidth.

> After I realised that I made some more changes 
> and uploaded bibledit-gtk_4.8-3 binary only

Binary-only uploads of a version whose source is not in the archive
would be rejected. Do you mean "diff only"?

> which was to close the removal bug

Closing removal bugs (and other bugs in pseudo-packages) via packages'
changelogs doesn't seem right in any case. If a removal request seems
wrong, send mail to its bug address explaining why it shouldn't be
removed, as you already did; and if you're really sure your reasons are
good, close it by using the -done address (but there's no need to do
that for those two removal bugs, because Scott already did).

S

Bug#796711: [Pkg-crosswire-devel] Bug#796711: sword: library transition is needed with GCC 5 as default

[Daniel Glassey]

Thanks Julien,

A new version of the library (1.7.5) is imminent and will require a
transition anyway. So we'll start planning the transition to libsword12.

Regards,
Daniel

On Sun, Aug 23, 2015 at 4:18 PM, Julien Cristau jcris...@debian.org wrote:

 Source: sword
 Version: 1.7.3+dfsg-2.1
 Severity: serious
 Tags: sid stretch
 User: debian-...@lists.debian.org
 Usertags: libstdc++-cxx11

 Hi,

 sword's public API relies on types like std::string and std::list
 provided by libstdc++6, meaning that libsword11 needs to be renamed.

 Cheers,
 Julien

 The following is a form letter:

 Background [1]: libstdc++6 introduces a new ABI to conform to the
 C++11 standard, but keeps the old ABI to not break existing binaries.
 Packages which are built with g++-5 from experimental (not the one
 from testing/unstable) are using the new ABI.  Libraries built from
 this source package export some of the new __cxx11 or B5cxx11 symbols,
 and dropping other symbols.  If these symbols are part of the API of
 the library, then this rebuild with g++-5 will trigger a transition
 for the library.

 What is needed:

  - Rebuild the library using g++/g++-5 from experimental. Note that
most likely all C++ libraries within the build dependencies need
a rebuild too. You can find the log for a rebuild in
  https://people.debian.org/~doko/logs/gcc5-20150813/
Search for BEGIN GCC CXX11 in the log.

  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
library API, and are used by the reverse dependencies of the
library.

  - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
forming the library API, you should close this issue with a short
explanation.

  - If there are no reverse dependencies, it should be the package
maintainers decision if a transition is needed.  However this might
break software which is not in the Debian archive, and built
against these packages.

  - If a library transition is needed, please prepare for the change.
Rename the library package, append v5 to the name of the package
(e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you
have a soversion bump and you upload this version instead of the
renamed package.  Prepare a patch and attach it to this issue (mark
this issue with patch), so that it is possible to NMU such a
package. We'll probably have more than hundred transitions
triggered. Then reassign the issue to release.debian.org and
properly tag it as a transition issue, by sending an email to
cont...@bugs.debian.org:

  user release.debian@packages.debian.org
  usertag this issue + transition
  block this issue by 790756
  reassign this issue release.debian.org

  - If unsure if a transition is needed, please tag the issue with help
to ask for feedback from other Debian developers.

 The libstdc++6 transition will be a large one, and it will come with a
 lot of pain.  Please help it by preparing the follow-up transitions.

 [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition

 ___
 Pkg-crosswire-devel mailing list
 pkg-crosswire-de...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel