Your message dated Wed, 28 Aug 2019 11:23:22 +0200
with message-id <17039837.3djn6FEBSk@deimos>
and subject line Re: Bug#935419: RM:
python-django-session-security/2.6.5+dfsg-1 -- ROM; cruft
has caused the Debian Bug report #935419,
regarding RM: python-django-session-security/2.6.5+dfsg-1 -- ROM; cruft
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
935419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935419
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: rm
Hello
Due to #933034, I believe I need manual decrufting:
source package django-session-security 2.6.5+dfsg-2 no longer builds
binary package(s): python-django-session-security
Please remove python-django-session-security/2.6.5+dfsg-1 from testing so that
django-session-security 2.6.5+dfsg-2 can migrate from sid to testing.
https://qa.debian.org/madison.php?package=django-session-security&table=debian&a=&c=&s=bullseye&S=on
django-session-security | 2.6.5+dfsg-1 | bullseye | source
python-django-session-security | 2.6.5+dfsg-1 | bullseye | all
python3-django-session-security | 2.6.5+dfsg-1 | bullseye | all
The binary only removal itself is because of python2 removal (#931659).
--- End Message ---
--- Begin Message ---
Thank you for your help! Closing.
(I reuploaded with only the source. The migration occurred today.)
On Thursday, 22 August 2019 15:04:04 CEST Adam D. Barratt wrote:
> Control: reassign -1 ftp.debian.org
>
> On 2019-08-22 13:16, Jean-Michel Vourgère wrote:
> > Due to #933034, I believe I need manual decrufting:
> >
> > source package django-session-security 2.6.5+dfsg-2 no longer builds
> >
> > binary package(s): python-django-session-security
>
> That may well be the case, but this:
> > Please remove python-django-session-security/2.6.5+dfsg-1 from testing
> > so that
> > django-session-security 2.6.5+dfsg-2 can migrate from sid to testing.
>
> is not. The cruft is in unstable, and it needs removing from unstable,
> which is handled by the FTP Team. I'm reassigning the request to them.
>
> As an additional note, the excuses include this item:
>
> Not built on buildd: arch all binaries uploaded by
> [email protected]
>
> which means that the package still will not be able to migrate in any
> case, and you will need to make a new source upload. If you're not
> already aware of this, see the second topic in
> https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html
>
> Regards,
>
> Adam
On Thursday, 22 August 2019 15:15:13 CEST Paul Gevers wrote:
> Control: reassign -1 ftp.debian.org
>
> Hi Jean-Michel,
>
> On 22-08-2019 14:16, Jean-Michel Vourgère wrote:
> > Due to #933034, I believe I need manual decrufting:
> True, but it needs decrufting in unstable, so reassigning to ftp.debian.org.
> > Please remove python-django-session-security/2.6.5+dfsg-1 from testing so
> > that django-session-security 2.6.5+dfsg-2 can migrate from sid to
> > testing.
> The excuses [1] say:
> """
> old binaries left on all: python-django-session-security (from
> 2.6.5+dfsg-1) (but ignoring cruft, so nevermind)
> """
>
> So it's not the cruft that's blocking migration. The issue you are
> facing is:
> """
> Not built on buildd: arch all binaries uploaded by [email protected]
> """
>
> Somebody will need to do a source only upload [2]. (For the record,
> binNMU isn't even possible for arch:all packages).
>
> Paul
>
> [1] https://qa.debian.org/excuses.php?package=django-session-security
> [2] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html
> (section: No binary maintainer uploads for bullseye)
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
