Backporting shibboleth-sp2 to wheezy

[Etienne Dysli-Metref]

On 14/11/16 17:13, Etienne Dysli-Metref wrote:
> On 14/11/16 13:09, Ferenc Wágner wrote:
>>>   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
>>
>> Looks like piuparts can't see the 2.6 version of libapache2-mod-shib2 in
>> the repository.  Is it there (I don't know where)?

Hi Ferenc,

That backport is quite a dead horse (even more so now since wheezy
became oldoldstable...) but I want to beat until I can release it. 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).

1) piuparts -b /var/cache/pbuilder/base-wheezy-amd64.tgz
--distribution=wheezy-backports-sloppy --arch=amd64 -D debian
--install-recommends --no-upgrade-test
../shibboleth-sp2_2.6.0+dfsg1-3_amd64.changes

2) same command as (1) but without `--no-upgrade-test`

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? I've tried to reintroduce the breaks and
replaces (<< 2.5.3+dfsg) that I removed during the merge (8abed0f), but
it doesn't make a difference.

3) piuparts -d wheezy-backports -d wheezy-backports-sloppy [...]
4) piuparts -d wheezy -d wheezy-backports -d wheezy-backports-sloppy [...]

I've pushed my changes in
shibboleth-sp2:edm/debian/wheezy-backports-sloppy. Can we release the
package in that state or does it need more fixes?

Cheers,
  Etienne

-------------- 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/20170711/15cac700/attachment.sig>