Hi Jonathan,
On Sep 10 2015, Jonathan Wiltshire <jmw@debian.org> wrote:
> On Thu, Sep 10, 2015 at 01:00:27PM -0700, Nikolaus Rath wrote:
>> The s3ql package is not migrating to testing. As far as I understand,
>> this is because it's not building on armhf.
>
> Your analysis is correct.
>
>> However, I think it would be a lot better to have s3ql in testing for
>> the other archituctures than not to have it in testing at all (there is
>> no S3QL version in testing at the moment).
>>
>> Is this intended behavior?
>
> I'm not sure which behaviour you're asking about;
I mean if it's intended that S3QL does not migrate to testing just
because it doesn't build on one architecture.
> the intended (and correct, and visible) behaviour is to remove s3ql
> from testing because it has an RC bug.
Hmm. I thought I took care of that. Which bug is that?
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=s3ql
lists only #792685 - but that only affects jessie and not sid/stretch.
>> If so, is there a way to make an exception here and allow migration?
>
> It's not an exception, but if you want to not ship s3ql on armhf in Stretch
> you can ask ftp-masters to remove it from sid, taking into account any
> reverse dependencies.
Hasn't s3ql *already* been removed from testing? At least this is what I
conclude from https://tracker.debian.org/pkg/s3ql.
Thanks!
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
Attachment:
signature.asc
Description: PGP signature