Backporting shibboleth-sp2 to wheezy

[Etienne Dysli-Metref]

Hi Ferenc,

On 19/07/17 14:20, Ferenc Wágner wrote:
> Sorry for the delayed reply, I've been either busy or on holiday, and
> this won't change much for the rest of this summer.

No worries, summer here is "catch up time" for delayed projects. :)

> I'm not sure how long wheezy-backports(-sloppy) will stay open.  By
> https://backports.debian.org/news/stretch-backports/ I'd expect it to
> close soon, because wheezy supported by LTS only...  Maybe worth asking
> the LTS team.

Oh! so this is a wee bit more urgent than I thought.

>> Now I think I understand what happens in piuparts a bit more: the
>> first test (install-purge) passes (1), but the second test
>> (install-upgrade-purge) fails (2).
> 
> Did you also find the cause of the failure?  I've got negligible
> experience with piuparts.

piuparts(1) describes the failing test this way:
> 2. A simple install-upgrade-purge test within one Debian 
> distribution. This test is like the install-purge test, but install 
> the packages first via apt-get and then from the package files given 
> on the command line.
From what I understand/see piuparts takes the names of the tested
packages and tries to install that with apt-get, then upgrades with the
tested packages. The last (failing) command that piuparts runs is:

    apt-get -y -t wheezy-backports-sloppy install \
    libapache2-mod-shib2 libshibsp-plugins libshibsp-dev \
    libshibsp-doc shibboleth-sp2-common shibboleth-sp2-schemas \
    shibboleth-sp2-utils

and it reports:

    Reading package lists...
    Building dependency tree...
    Reading state information...
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
     libshibsp-plugins : Breaks: libapache2-mod-shib2 (< 2.5.3+dfsg) but
2.4.3+dfsg-5+deb7u1 is to be installed
     shibboleth-sp2-common : Breaks: libapache2-mod-shib2 (< 2.5.3+dfsg)
but 2.4.3+dfsg-5+deb7u1 is to be installed
                           Breaks: shibboleth-sp2-schemas (< 2.5.3+dfsg)
but 2.4.3+dfsg-5+deb7u1 is to be installed
     shibboleth-sp2-utils : Breaks: libapache2-mod-shib2 (< 2.5.3+dfsg)
but 2.4.3+dfsg-5+deb7u1 is to be installed
    E: Unable to correct problems, you have held broken packages.

The weird thing is that I *can* smoothly upgrade from 2.4.3 to 2.6.0
with those packages. I just tried it in a Docker container. I have to
use `apt-get dist-upgrade` though. So I'm probably missing some special
piuparts option or I messed up a dependency definition.

>> Moreover, upgrading from wheezy-backports works properly (3,4), but
>> upgrading from wheezy directly to wheezy-backports-sloppy doesn't. Is
>> the later supposed to work?
> 
> Well, direct upgrades from wheezy to stretch are not supported, but from
> wheezy to wheezy-backports-sloppy... er, I don't know.  But it would be
> nice, if feasible.

I meant upgrading the Shibboleth packages, not the whole system. That
should work now, as I said above. :) For this I used piuparts's third
test mode with `-d wheezy -d wheezy-backports -d wheezy-backports-sloppy`.

> You certainly have to revert 4a20cce3 to enable direct upgrades from
> < 2.5.3+dfsg, so this is a good move.  Could you please send me the full
> piuparts logs of the failing scenario with this change included?

Log from `sudo piuparts -b /var/cache/pbuilder/base-wheezy-amd64.tgz
--distribution=wheezy-backports-sloppy --arch=amd64 -D debian
--install-recommends --no-install-purge-test -l ../piuparts.log
../shibboleth-sp2_2.6.0+dfsg1-3_amd64.changes` is attached.

> 20863ed8 is another revert candidate for wheezy, by the way.

Thanks, I'll revert it too.

Cheers,
  Etienne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: piuparts_shibboleth-sp2_2.6.0+dfsg1-3_wheezy.log
Type: text/x-log
Size: 48764 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/attachments/20170720/628f7029/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/attachments/20170720/628f7029/attachment-0001.sig>