Hi,

Getting package autoremoved from testing is not end-of-the-world -- 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 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