On Wed, Dec 8, 2021 at 11:49 PM Tong Sun wrote:
>
> On Sun, Nov 28, 2021 at 1:51 PM Boyuan Yang wrote:
>
> > Getting package autoremoved from testing is not end-of-the-world
>
> It might not be the end-of-the-world for you, but apparently it is for
> me already, even before the deadline.

Oh, sorry, my package was turn to NEW for another reason. I'll try to
find a sponsor for it myself.

> > -- once the
> > bug is fixed, it can get back to Debian Testing at any time. Meanwhile, the
> > previous bug is real and will need to be fixed sooner or later.
>
> I fixed the 1.5.7-1 problem in 1.5.7-2, but when I'm uploading the fix
> of 1.5.7-2, I got:
>
> ----------------------
> ACL dm: NEW uploads are not allowed
>
> binary:dbab is NEW.
> source:dbab is NEW.
> ----------------------
>
> The Debian FTP Masters explains that it means "DMs may not upload
> packages going to NEW. Need to use a sponsor for those".
>
> My package is already marked for autoremoval from testing
> -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995769
>
> there isn't much time left for me but I have to go through a sponsor
> now, even that I've got everything ready.
>
> Can you help sponsor me please?
>
> > I may get back to look into the bug later, bug I don't have enough time
> > recently. Feel free to find help from others, or I may get involved when I
> > have enough time.
> >
> > Thanks,
> > Boyuan Yang
> >
> >
> > 在 2021-11-28星期日的 11:35 -0500,Tong Sun写道:
> > > Hi Boyuan, please please help.
> > >
> > > ---------- Forwarded message ---------
> > > From: Tong Sun <suntong...@users.sourceforge.net>
> > > Date: Sun, Nov 28, 2021 at 11:33 AM
> > > Subject: Re: Bug#995769: dbab: v1.5.7 package fail to upgrade from
> > > bullseye (1.5.01-1)
> > > To: Boyuan Yang <by...@debian.org>, <995...@bugs.debian.org>
> > >
> > >
> > > To Boyuan, or any mentors reading this issue.
> > >
> > > I've been trying to fix it myself, but all my previous attempts
> > > failed, because I don't understand what breaks and why, from the
> > > output of the package upgrade log.
> > >
> > > I've sent a help request to debian-mentors a few days ago, but nobody
> > > answers yet.
> > >
> > > My package is now marked for autoremoval from testing, with a wrong
> > > reason, and I don't know how to stop my package being autoremed from
> > > testing, and I got no answers/help on that either.
> > >
> > > Since I don't know how to fix it myself, and all my previous attempts
> > > failed, if nobody helps me by next weekend, I'll do the only thing
> > > that I know -- to change the severity of this bug to minor, because
> > > there is a simple solution to it as explained below. This will solve
> > > everything and win me the time it takes for me to do further
> > > investigation/testing.
> > >
> > > Really hope it won't be the case.
> > > Somebody help please.
> > > Thanks
> > >
> > > On Thu, Oct 7, 2021 at 9:31 PM Tong Sun wrote:
> > > >
> > > > On Tue, Oct 5, 2021 at 7:27 AM Boyuan Yang  wrote:
> > > >
> > > > > Package dbab/1.5.7-1 has broken maintscript and cannot be properly
> > > > > upgraded
> > > > > from dbab/1.5.01-1 to dbab/1.5.7-1:
> > > >
> > > > Thanks for reporting. I'll try to fix it ASAP.
> > > >
> > > > In the meantime, for anyone who doesn't want to wait for the fix to be
> > > > published --
> > > > do not do an upgrade -- remove the package completely, then do a fresh
> > > > install.
> > > >
> > > > thx
> >

Reply via email to