Re: How to troubleshoot conffile files problems

2021-12-05 Thread Tong Sun
On Sun, Dec 5, 2021 at 1:05 AM Andrey Rahmatullin wrote:
>
> On Sat, Dec 04, 2021 at 11:29:58PM -0500, Tong Sun wrote:
> > > You should remove them manually in postrm, but only on
> > > purge.
> >
> But now you will need to also recover from a bad state
> left by upgrades to 1.5.7-1.

Ah... it is getting more and more complicated. Nobody would be able to
upgrade to 1.5.7-1 normally, so it is OK to use next good version as
the fix please? Else, all the upgrade related problems can be easily
fixed by purging the old version, and installing a brand new version.
Would that be OK as the fix please? This is really a simple script,
and I really hope that the debian side won't be complicated by any
one-off end cases.

> > How to do that please?
> The correct way, it seems, would be to follow the suggestion in the
> original bug report and fix the "rm -f /etc/dnsmasq.d/dbab.*" line in
> the 1.3.3-1 postrm.

I still don't quite understand what you actually mean, but let me make
a guess (and commit) and you can tell me if it is what you mean or
not...

thx Andrey



Bug#984460: marked as done (RFS: tlog/12-1 [ITP] -- terminal I/O recording)

2021-12-05 Thread Debian Bug Tracking System
Your message dated Sun, 5 Dec 2021 16:53:05 +0100
with message-id <965396d4-e737-c3a4-06b0-a5755d490...@debian.org>
and subject line Re: RFS: tlog/12-1 [ITP] -- terminal I/O recording and playback
has caused the Debian Bug report #984460,
regarding RFS: tlog/12-1 [ITP] -- terminal I/O recording
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 ow...@bugs.debian.org
immediately.)


-- 
984460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "tlog":

 * Package name: tlog
   Version : 11-1
   Upstream Author : Nikolai Kondrashov 
 * URL : http://scribery.github.io/tlog/
 * License : GPL-2+
 * Vcs : https://github.com/Scribery/tlog
   Section : misc

It builds those binary packages:

  libtlog0 - library for terminal I/O recording and playback
  tlog - terminal I/O recording and playback

To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/tlog/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/t/tlog/tlog_11-1.dsc

Changes for the initial release:

 tlog (11-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #886927)

Regards,
Markus
--- End Message ---
--- Begin Message ---

Uploaded. Thanks for your contribution.--- End Message ---


Bug#1001177: marked as done (RFS: ffmpegfs/2.8-1~bpo11+1 -- Fuse Multi Media Filesystem)

2021-12-05 Thread Debian Bug Tracking System
Your message dated Mon, 6 Dec 2021 00:18:22 +0100
with message-id 
and subject line Re: Bug#1001177: RFS: ffmpegfs/2.8-1~bpo11+1 -- Fuse Multi 
Media Filesystem
has caused the Debian Bug report #1001177,
regarding RFS: ffmpegfs/2.8-1~bpo11+1 -- Fuse Multi Media Filesystem
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 ow...@bugs.debian.org
immediately.)


-- 
1001177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ffmpegfs":

 * Package name: ffmpegfs
   Version : 2.8-1~bpo11+1
   Upstream Author : Norbert Schlia 
 * URL : https://nschlia.github.io/ffmpegfs/
 * License : GPL-3+, CC0-1.0, GFDL-1.3 or GPL-3+
 * Vcs : https://github.com/nschlia/ffmpegfs
   Section : utils

It builds those binary packages:

  ffmpegfs - Fuse Multi Media Filesystem

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/ffmpegfs/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/f/ffmpegfs/ffmpegfs_2.8-1~bpo11+1.dsc

Changes since the last upload:

 ffmpegfs (2.8-1~bpo11+1) bullseye-backports; urgency=medium
 .
   * Rebuild for bullseye-backports.

--- End Message ---
--- Begin Message ---
On Sun, Dec 05, 2021 at 07:34:13PM +0100, Norbert Schlia wrote:
>  * Package name: ffmpegfs
>Version : 2.8-1~bpo11+1

>  ffmpegfs (2.8-1~bpo11+1) bullseye-backports; urgency=medium
>  .
>* Rebuild for bullseye-backports.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ I was born a dumb, ugly and work-loving kid, then I got swapped on
⠈⠳⣄ the maternity ward.--- End Message ---


Re: How to troubleshoot conffile files problems

2021-12-05 Thread Stuart Prescott
On Friday, 3 December 2021 02:46:43 AEDT Tong Sun wrote:
> 
> grep: /etc/dbab/dbab.list-: No such file or directory
> cat: /etc/dbab/dbab.addr: No such file or directory
> 
> 
> They should be there but I have no idea why they are not.

Note that this isn't just about conffile handling in the package, these error 
messages also highlight bugs in the scripts that this package includes in 
/usr/sbin. 

* The scripts are assuming that files exist and do not test whether they exist. 
A conffile can be removed by the admin at any time; the software might not be 
able to work in that case, but it should exit with an informative error 
message not malfunction.

* The scripts do not handle errors properly (at all, really). I think you need 
to go through each script line by line and ask "what might make this command 
fail?", "can that failure be prevented?", "if not, what should happen after 
failure?"

* The scripts have at least predictable temp-file issue that allow an 
unprivileged user to do arbitrary damage to a system, overwriting any file they 
choose with a simple "ln -s /some/victim/file /tmp/dbab-map.adblock.conf" prior 
to the admin installing or upgrading the package, or running that script.

* maintainer scripts should try very very hard to avoid failing (non-zero exit 
code) as that failure can be quite awkward to recover from. Failing the 
postinst because there's a blank line in the config file, for instance, seems 
pretty harsh.

regards
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7