Your message dated Thu, 18 Apr 2024 13:12:26 +0200
with message-id
<cajxtcxxpj7kpxzvr3da-6mho+h11xfwrdssxdnownrw-amp...@mail.gmail.com>
and subject line Re: Bug#1069227: man-db: Please do not change MANWIDTH
behavior just in Debian
has caused the Debian Bug report #1069227,
regarding setting MANWIDTH 80 gives different result in sid
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.)
--
1069227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069227
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: man-db
Version: 2.12.1-1
Severity: normal
Hi,
It seems that man-db debian maintainer decided on its own to make
some arbitrary change to how MANWIDTH is handled.
This is probably going to break things, for no good reason besides a personal
preference.
Please revert that.
Jérémy
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages man-db depends on:
ii bsdextrautils 2.39.3-6
ii bsdmainutils 12.1.8
ii debconf [debconf-2.0] 1.5.86
ii groff-base 1.23.0-3
ii libc6 2.37-15
ii libgdbm6 1.23-5+b1
ii libpipeline1 1.5.7-2
ii libseccomp2 2.5.5-1
ii zlib1g 1:1.3.dfsg-3+b1
man-db recommends no packages.
Versions of packages man-db suggests:
ii apparmor 3.0.13-2
ii chromium [www-browser] 123.0.6312.105-1~deb13u1
ii dillo [www-browser] 3.0.5-7+b1
ii epiphany-browser [www-browser] 46~beta-1
ii firefox-esr [www-browser] 115.8.0esr-1
ii groff 1.23.0-3
ii less 590-2
ii lynx [www-browser] 2.9.0rel.0-2
ii w3m [www-browser] 0.5.3+git20230121-2+b2
-- debconf information:
man-db/install-setuid: false
man-db/auto-update: true
--- End Message ---
--- Begin Message ---
Le jeu. 18 avr. 2024 à 13:10, Colin Watson <[email protected]> a écrit :
> On Thu, Apr 18, 2024 at 12:56:06PM +0200, Jérémy Lal wrote:
> > Le jeu. 18 avr. 2024 à 12:29, Colin Watson <[email protected]> a
> écrit :
> > Ok, and sorry, I got frustrated by the "1 column space on the right"
> change
> > of
> > https://gitlab.com/man-db/man-db/-/merge_requests/11
> [...]
> > Indeed, the upstream version changes how width is configured.
> > - man: match the display width to the configured width (closes:#1059537).
> >
> > It's just making another package (node-marked-man) render man pages
> > differently, and fail its tests, preventing some other package
> > migration (nodejs) and it would have been nice not having that change
> > during this t64 transition.
>
> Well, I'm sorry for the inconvenience, but I think this change was
> reasonable on its own merits and I don't plan to revert it. The exact
> details of margins and such are very much an implementation detail that
> other packages should in no way be relying upon.
>
> Perhaps node-marked-man should do a whitespace-insensitive comparison of
> some kind? Whitespace details in the output don't seem terribly
> relevant to what it's trying to do.
Ok, yes it should.
Closing, then.
--- End Message ---
