Re: S3QL Upload Reject
On Tue, 31 Jul 2018, Nikolaus Rath wrote:
> On Jul 23 2018, James Clarke <jrtc27@debian.org> wrote:
> > On 23 Jul 2018, at 19:21, Nikolaus Rath <Nikolaus@rath.org> wrote:
> >> On Jul 23 2018, Mattia Rizzolo <mattia@debian.org> wrote:
> >>> On Mon, Jul 23, 2018 at 11:06:17AM +0100, Nikolaus Rath wrote:
> >>>> On Jul 21 2018, Debian FTP Masters <ftpmaster@ftp-master.debian.org> wrote:
> >>>>> Subject: Re: s3ql_2.29+dfsg-1~bpo9+1_source.changes REJECTED
> >>>>>
> >>>>> Not accepted by any per-suite acl (suite=stretch-backports)
> >>>>
> >>>> I thought if I have upload permissions for unstable, the package is
> >>>> already in backports, then I should be able to update it. Am I mistaken?
> >>>
> >>> The reject message is so clear: you are not in the ACL.
> >>> Have you read https://backports.debian.org/Contribute/ ?
> >>> Have you ever uploaded anything to backports yourself?
> >>
> >> Yes and yes. That's why I thought this should just work :-). As I said,
> >> I've uploaded the same package to jessie-backports in the past.
> >
> > In the past the ACL was erroneously unenforced, so my guess is you uploaded
> > before this was fixed and were never in the ACL in the first place.
>
> I've filed rt.debian.org ticket #7362 about this a week ago, but still
> haven't gotten any response. Is anyone able to check if this went to the
> right person/team/list?
Be patient, it went to the right tracker.
>
>
> Thanks!
> -Nikolaus
>
> --
> GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
>
> »Time flies like an arrow, fruit flies like a Banana.«
>
Reply to: