Re: How to troubleshoot conffile files problems
On Thu, Dec 2, 2021 at 10:46 AM Tong Sun wrote:
>
> Hi,
>
> I'm having problem with my conffile files, see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995769
>
> I.e.,
>
> ----
> grep: /etc/dbab/dbab.list-: No such file or directory
> cat: /etc/dbab/dbab.addr: No such file or directory
> ----
OK, I want to remove all conffile files and reinstall the new ones
when doing package upgrade, as there isn't much user intervention to
those conffile files. All are provided by the package.
So I do `rm_conffile` to the old conffile files when doing package
upgrade, but the new conffile files provided by the new upgrading
package did not get installed afterwards, before they were used.
> They should be there but I have no idea why they are not.
That's why they are there if doing fresh package installation but they
are not there if doing package upgrade.
How to properly handle conffile files in such a case?
Please, please help.
Again, the package source is at:
https://salsa.debian.org/debian/dbab/
Thanks
> Is there any way to have more insights into what's going on during the
> package upgrade or conffile files handling?
>
> thx
>
> On Thu, Nov 25, 2021 at 3:45 PM Tong Sun
> <suntong001@users.sourceforge.net> wrote:
> >
> > Hi Mentors,
> >
> > I need help.
> >
> > My package cannot be upgraded from current version to latest version
> > -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995769
> >
> > It might have something to do with obsoleted conffile files or it
> > might even not. The problem is, I've been trying to understand how the
> > conffile files work, and I think I'm doing the right thing, yet my
> > package cannot be properly upgraded.
> >
> > - I don't understand what breaks and why, from the output of the
> > package upgrade log (see
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995769).
> > - Thus, I have no idea how to fix it, and all my previous attempts failed. So,
> >
> > Please help. The package source is at:
> >
> > https://salsa.debian.org/debian/dbab/
> >
> >
> > Also, I've been trying to solve it on my own for so long that now the
> > good version in testing is marked for autoremoval, for the reason
> > that:
> >
> > > If a package is out of sync between unstable and testing for a longer
> > period, this usually means that bugs in the package in testing cannot be
> > fixed via unstable.
> >
> > However, this is not true in my case. So if I still cannot fix the
> > problem by myself by the deadline, would I be able to at least stop my
> > package being autoremed from testing?
> >
> > Thanks for helping
> >
> > ---------- Forwarded message ---------
> > From: Debian testing autoremoval watch <noreply@release.debian.org>
> > Date: Sat, Nov 20, 2021 at 11:40 PM
> > Subject: dbab is marked for autoremoval from testing
> > To: <dbab@packages.debian.org>
> >
> >
> > dbab 1.5.01-1 is marked for autoremoval from testing on 2021-12-11
> >
> > It is affected by these RC bugs:
> > 999581: dbab: fails to migrate to testing for too long: unresolved RC bug
> > https://bugs.debian.org/999581
> >
> >
> >
> > This mail is generated by:
> > https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
> >
> > Autoremoval data is generated by:
> > https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
Reply to: