[pkg-xtuple-maintainers] Bug#791230: GCC5 transition and jessie-backports

Daniel Pocock daniel at pocock.pro
Sun Aug 30 12:19:03 UTC 2015

I started looking at updating the packages postbooks, openrpt and csvimp
to the latest upstream versions.  My intention, as with previous
updates, is to put the latest upstream releases into unstable, wait for
them to propagate to testing and then upload them to backports.

As part of the GCC5 update[1], one of the binary packages built from
openrpt has been renamed from libopenrpt1 to libopenrpt1v5 - see bug
#791230[2] - and that is the version that will be in testing.

If I understand the rules for backports correctly, backports is supposed
to contain the same thing that is in testing.

Given that unstable and testing will use GCC5 and jessie-backports
should be using the GCC 4.9 from jessie, what is supposed to happen?
Will GCC5 be available to compile for backports and should such packages
declare a dependency on the newer libstdc++?  Or is it permitted to make
uploads to jessie-backports without the "v5" suffix, so the package name
in backports won't be the same as the package name in testing?  Or
something else?

1. https://wiki.debian.org/GCC5

2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791230

More information about the pkg-xtuple-maintainers mailing list