Bug#1104892: systemd-sysv : Conflicts: sysvinit-core but 3.06-4 is to be installed

2025-05-07 Thread Thorsten Glaser
severity 1104892 normal thanks (This isn’t a bug in the package per se but the way to install it is difficult by necessity.) On Wed, 7 May 2025, Jean-Marc LACROIX wrote: > Consider following log This is hard to read for nōn-french speakers; it would be nice to “export LC_ALL=C.UTF-8” befor

Bug#1050872: MIPS Linux kernel versions for trixie/sid

2025-04-27 Thread Thorsten Glaser
Dixi quod… >I have a workaround in a package where I (also) build binaries >against Linux klibc to not do that for mipsel and mips64el as >klibc 2.0.13+ needs kernel 5.1+ and some buildds and possibly >other infrastructure or relevant users were still on 4.x kernels While https://bugs.debian.org/

Bug#1104049: bash-completion: bashism in /etc/profile.d/ snippet

2025-04-25 Thread Thorsten Glaser
Dixi quod: >Justification: Policy 10.4 Policy has an extra requirement on top of POSIX that -a is supported, but /etc/profile can be read by shells not suitable for /bin/sh in Debian, so a fix would still be appreciated, but I don’t insist on rc severity. bye, //mirabilos -- “It is inappropriat

Bug#1104049: bash-completion: bashism in /etc/profile.d/ snippet

2025-04-24 Thread Thorsten Glaser
Package: bash-completion Version: 1:2.11-6 Severity: serious Justification: Policy 10.4 Tags: bookworm trixie sid Control: found -1 1:2.16.0-7 X-Debbugs-Cc: t...@mirbsd.de /etc/profile.d/bash_completion.sh has: if [ "x${BASH_VERSION-}" != x -a "x${PS1-}" != x -a "x${BASH_COMPLETION_VERSINFO-}" =

Bug#1070860: musescore3: CVE-2023-44428

2025-04-02 Thread Thorsten Glaser
On Wed, 2 Apr 2025, Moritz Mühlenhoff wrote: >This looks good to me! Thanks! >could you please make uploads for musescore2 and musescore3 >with this file added before the trixie freeze? Will do. I had other changes piled up, but not all of the fixes that I think are needed, and these I have no

Bug#1094807: RM: pcre3 -- ROM; Long obsolete

2025-03-24 Thread Thorsten Glaser
On Mon, 24 Mar 2025, Matthew Vernon wrote: > I'm sorry that my MBF didn't find the issue; presumably the package concerned > didn't specify a Build-Depends on pcre3? Yes, exactly: it was only used in debian/tests/control as runtime dependency for autopkgtests, to work around a bug in GNU grep (wh

Bug#1094807: RM: pcre3 -- ROM; Long obsolete

2025-03-23 Thread Thorsten Glaser
On Mon, 3 Feb 2025, Paul R. Tagliamonte wrote: >I agree. I checked all the breakage Unfortunately, neither got the debian/tests/control dependencies, so I had the pleasure to receive an RC bug in my package, which used pcregrep, this short before the freeze, with no advance notice at all. Please

Bug#1100955: initscripts: Wants to remove the running kernel

2025-03-20 Thread Thorsten Glaser
On Thu, 20 Mar 2025, Bjarni Ingi Gislason wrote: >~#apt-get dist-upgrade > > * What was the outcome of this action? > >The following packages were automatically installed and are no longer required: > dracut-install libatopology2t64 linux-doc-6.1 >Use 'apt autoremove' to remove them. >The follo

Bug#922423: initscripts: formatting of scripts

2025-03-17 Thread Thorsten Glaser
On Mon, 17 Mar 2025, Mark Hindley wrote: > Scripts should follow the style produced by shfmt(1) FWIW, never heard of that tool. > - case indented Don’t indent case, it’s useless and just adds clutter. You cannot have something other than the pattern inside, so: case $foo in (bar) echo

Bug#1094245: New upstream version xxx

2025-03-07 Thread Thorsten Glaser
On Thu, 30 Jan 2025, Sam Pinkus wrote: > On 29/1/25 06:41, Sebastian Andrzej Siewior wrote: >>>override_dh_update_autotools_config: >>>     ./autogen.sh >> How is this different from the current autoreconf step that is >> already as part of dh? Not effectively, other than being vulnerable

Bug#932362: move /etc/init.d/mountnfs.sh to bin:nfs-common

2025-03-07 Thread Thorsten Glaser
Mark Hindley dixit: >So, I am inclined to close. What do you think? I guess so, the warning is gone anyway. bye, //mirabilos -- "Using Lynx is like wearing a really good pair of shades: cuts out the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."

Bug#1098778: ntpsec: 'pool' directive causes duplicate server entries

2025-03-03 Thread Thorsten Glaser
On Mon, 3 Mar 2025, Richard Laager wrote: > On 2025-03-03 05:16, Thorsten Glaser wrote: >> Is there a way to say “give me only v4 or only v6 from this pool” > > I haven't tested, but you could try: > > pool -4 > pool -6 Ah! I hadn’t tested it as it’s only documente

Bug#1098778: ntpsec: 'pool' directive causes duplicate server entries

2025-03-03 Thread Thorsten Glaser
On Fri, 28 Feb 2025, Richard Laager wrote: > What does `ntpq -pn` report? > > I suspect the answer is that you are getting the server once with IPv4 > and once with IPv6. Bingo. Incidentally, for the other pool (of a massive size, 4×Legacy IP, 5×IPv6) I’m using, I use a specific alias to only ge

Bug#1065698: update-initramfs: -k all stopped working

2025-03-03 Thread Thorsten Glaser
Hi Ben >It works for me. unfortunately, I do not have the system in question any more. Looking at the version, it’s the same as in bookworm (sans deb12u1), and a bookworm/armel system I have (RPi 1) indeed succeeds. >- What's the full command line that doesn't work? sudo update-initram

Bug#1098778: ntpsec: 'pool' directive causes duplicate server entries

2025-02-23 Thread Thorsten Glaser
Package: ntpsec Version: 1.2.3+dfsg1-3 Severity: normal X-Debbugs-Cc: t...@mirbsd.de With 'pool ntp.hetzner.de' in the config, I get multiple entries of the same servers in 'ntpq -p': $ sudo ntpq -p remote

Bug#1098638: fdisk: creates partitions one sector too large

2025-02-21 Thread Thorsten Glaser
Dixi quod… >I’ve only tested that with GPT at the moment. Same for MBR: Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free) e extended (container for logical partitions) Select (default p): p Partition number (1-4, default 1): 1 First sector (2048-10002152

Bug#1098638: fdisk: creates partitions one sector too large

2025-02-21 Thread Thorsten Glaser
Package: fdisk Version: 2.38.1-5+deb12u1 X-Debbugs-Cc: t...@mirbsd.de When I create a new partition with +sectors, fdisk creates one that is one sector too large: Command (m for help): n Partition number (1-128, default 1): First sector (2048-7814037134, default 2048): Last sector, +/-sectors or

Bug#1095791: dpkg: incompatible and Policy-violating R³ default change breaks packages’ builds

2025-02-13 Thread Thorsten Glaser
On Fri, 14 Feb 2025, Guillem Jover wrote: >> >This bug does not count as RC just because Debian upload bureaucracy >> >hasn't been performed yet. >> >> If packagers cannot rely on Policy to give correct information, what >> *can* they rely on? > >This is not how Debian Policy has ever worked. By t

Bug#1095932: openjdk-8: Misbuilds packages when calling only binary-* targets

2025-02-13 Thread Thorsten Glaser
On Fri, 14 Feb 2025, Guillem Jover wrote: >As was discovered in bug #1095746, this package misbuilds when calling >for example «fakeroot debian/rules binary-arch» w/o first calling >«debian/rules build-arch», which is a policy violation: Yes. I noticed yesterday (or so… memory is a bit fuzzy) and

Bug#1095791: dpkg: incompatible and Policy-violating R³ default change breaks packages’ builds

2025-02-13 Thread Thorsten Glaser
On Fri, 14 Feb 2025, Sean Whitton wrote: >Policy has to go through binary-NEW in order to be released. So there Technicalities. >isn't a quick fix here. Not looking for one. dpkg should revert this until then. >This bug does not count as RC just because Debian upload bureaucracy >hasn't been

Bug#1095791: dpkg: incompatible and Policy-violating R³ default change breaks packages’ builds

2025-02-13 Thread Thorsten Glaser
severity 1095791 serious thanks On Thu, 13 Feb 2025, Guillem Jover wrote: >> >From what I can tell from other mails, I believe the package in >> question is openjdk-8 (unstable only); see bug #1095746. > >Ah, thanks for the context. In that case, going by that bug report, it >looks like openjdk-8

Bug#1093878: openjdk-8: CVE-2025-21502

2025-02-11 Thread Thorsten Glaser
On Tue, 11 Feb 2025, Emilio Pozuelo Monfort wrote: > From the affected versions, I believe this affects Oracle Java 8 > Enterprise Performance Pack, but not OpenJDK 8 Meanwhile, after several mails back and forth, I managed to extract useful information from the Oracle employee who deigned to res

Bug#1095746: openjdk-8-jdk: Link /etc/alternatives/java -> /usr/lib/jvm/java-8-openjdk-amd64/bin/java is missing in 8u442-ga-1

2025-02-11 Thread Thorsten Glaser
Dixi quod… >One thing I do can see is that the older build called >debian/rules build-arch before debian/rules binary-arch, >the newer calls only the latter. So, perhaps, some value >that got reobtained is now cached? (But why only the one?) > >Investigation continues. It’s an incompatible change

Bug#1095791: dpkg: incompatible and Policy-violating R³ default change breaks packages’ builds

2025-02-11 Thread Thorsten Glaser
Source: dpkg Version: 1.22.13 Severity: serious Justification: Policy §5.6.31 X-Debbugs-Cc: t...@mirbsd.de dpkg 1.22.13 implemented a backwards-incompatible change, violating Policy (which states the default value is most certainly *not* “no”) and breaking builds of packages. dpkg (1.22.13) unsta

Bug#1095746: openjdk-8-jdk: Link /etc/alternatives/java -> /usr/lib/jvm/java-8-openjdk-amd64/bin/java is missing in 8u442-ga-1

2025-02-11 Thread Thorsten Glaser
>These seem to be the only ones affected, from the apt-get install >output, though I’ll also look at the packages. I’ll investigate. Best I can say at this point is that the wildcard in… all_jre_tools = $(filter-out javaws, $(notdir $(wildcard $(builddir)/$(jreimg)/bin/*))) jre_tools = $

Bug#1095746: openjdk-8-jdk: Link /etc/alternatives/java -> /usr/lib/jvm/java-8-openjdk-amd64/bin/java is missing in 8u442-ga-1

2025-02-11 Thread Thorsten Glaser
reassign 1095746 openjdk-8-jre-headless thanks On Tue, 11 Feb 2025, Matthias Mueller wrote: >The Link from /etc/alternatives/java -> >/usr/lib/jvm/java-8-openjdk-amd64/bin/java is missing in 8u442-ga-1. Ouch, indeed. This is… surprising, there’s not been a deliberate change even near that area.

Bug#1008911: initscripts: /run often mounted nodev, "/run/rootdev" likely to fail

2025-02-11 Thread Thorsten Glaser
On Tue, 11 Feb 2025, Mark Hindley wrote: >or what an initramfs might have setup. This is probably a point. So, put it under /dev, which has this purpose. bye, //mirabilos -- den AGP stecker anfeilen, damit er in den slot aufm 440BX board passt… oder netzteile, an die man auch den monitor anges

Bug#1093878: Q about 8u442 applicability of JDK-8330045 (Enhance array handling) / CVE-2025-21502

2025-02-09 Thread Thorsten Glaser
On Mon, 10 Feb 2025, David Holmes wrote: > 8u-perf is an Oracle product. You won't find any links to commits for it. Guess so. >> I also cannot read JDK-8330045 (wants a login, in contrast to the >> other JDK-### bugs I peeked into). >> >> So, what’s the state of this? > > The entry here lis

Bug#1095633: vim: FTBFS in stable: fails tests

2025-02-09 Thread Thorsten Glaser
Source: vim Version: 2:9.0.1378-2+deb12u1 Severity: serious Justification: FTBFS Tags: security bookworm James McCoy indicated that… >Indeed, upstream ended up disabling the test that 9.0.1532 introduced >because it took too long: > >https://github.com/vim/vim/compare/v9.0.1533...v9.0.1535 What

Bug#1093878: Q about 8u442 applicability of JDK-8330045 (Enhance array handling) / CVE-2025-21502

2025-02-09 Thread Thorsten Glaser
Hi, I’ve got this report against openjdk-8 in Debian about CVE-2025-21502 and I cannot find whether this even affects openjdk-8 at all, nor if it’s fixed in 8u442. There are links to commits in 21/17/11 and a page saying Oracle’s 8u431-perf is affected with the fix in 8u441-perf, but without a li

Bug#1093393: alpine: broken date format

2025-02-02 Thread Thorsten Glaser
On Sat, 18 Jan 2025, Thorsten Glaser wrote: >I had a look through the setup screen to check for an option to >configure the date format, which was ENOENT. Oh goodie, it sort of honours LC_TIME but sort of doesn’t, now I have mails from “Jan 14”… which is *still* wrong as the locale sa

Bug#1085065: vim: FTBFS: failing tests

2025-02-02 Thread Thorsten Glaser
severity 1085065 serious found 1085065 2:9.0.1378-2+deb12u1 thanks This is now affecting stable-security builds.

Bug#929983: ipxe-qemu: virtio booting no longer works after upgrade to buster

2025-01-19 Thread Thorsten Glaser
retitle 929983 ipxe-qemu: virtio booting no longer works after upgrade to buster due to machine type support change tags 929983 + wontfix close 929983 thanks On Sun, 19 Jan 2025, Sven Geuer wrote: >Reading through the messages to this bug, I am afraid there's nothing >that can be done about it a

Bug#689456: alpine: does not interpret timezone offsets in date headers

2025-01-17 Thread Thorsten Glaser
On Tue, 2 Oct 2012, Dominik George wrote: >The tiem information in the thread index does not take into account >timezone offsets. This has bugged me for a while as well. As far as I can tell, the setup option “Convert Dates To Localtime” (pinerc feature-list convert-dates-to-localtime) is suppos

Bug#1093393: alpine: broken date format

2025-01-17 Thread Thorsten Glaser
Package: alpine Version: 2.26+dfsg-1~bpo11+1 Severity: normal X-Debbugs-Cc: t...@mirbsd.de Besides the awful “Yesterday”, “Monday”, etc. (which in itself is a regression to pine’s always using the “Jan 17” format), it uses “02/06/18” for older messages, which is just plain broken. I had a look th

Bug#1093002: rng-tools-debian: systemd service fails instead of skipping

2025-01-15 Thread Thorsten Glaser
On Thu, 16 Jan 2025, Luca Boccassi wrote: >This is an anti-pattern, and best avoided. What's the problem if the >script runs twice? If it just detects things it should be just fine, Extra effort, though. And, in general, TOCTOU, but probably not applicable here. bye, //mirabilos -- den AGP ste

Bug#1093002: rng-tools-debian: systemd service fails instead of skipping

2025-01-15 Thread Thorsten Glaser
On Thu, 16 Jan 2025, Sven Geuer wrote: >> If not, I’d lean towards one (which?) of the errorlevel-using ones, >> because otherwise we’d have to run the detection code twice. > >Not sure what you mean by 'one of the errorlevel-using ones'. Please >explain your idea in more details. SuccessExitStat

Bug#1093002: rng-tools-debian: systemd service fails instead of skipping

2025-01-15 Thread Thorsten Glaser
On Wed, 15 Jan 2025, Sven Geuer wrote: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162 >Applying ExecCondition to me seems the most reasonable solution to this >bug. Can the script behind ExecCondition pass variables to the script behind ExecStart or, even better, the unit itself

Bug#1093002: rng-tools-debian: systemd service fails instead of skipping

2025-01-14 Thread Thorsten Glaser
On Tue, 14 Jan 2025, Luca Boccassi wrote: >It looks like this is doing some checks, and intends to skip. But just >exiting means the service is recorded as failed, and this will likely >trip other tests, hence the severity to stop migrating to testing for >now. Ah, ouch. Agreed. >There are sever

Bug#1092822: autopkgtest: probably does not need rng-tools* any more

2025-01-12 Thread Thorsten Glaser
(tl;dr at the end) Paride Legovini dixit: >Hello Thorsten and thanks for the suggestion. Currently autopkgtest is >used to test systems as old a Ubuntu Trusty, which ships with Linux >3.13, so what you suggest is too modern. Ah, you test the older systems from a newer host and with newer autopkg

Bug#1092822: autopkgtest: probably does not need rng-tools* any more

2025-01-11 Thread Thorsten Glaser
Source: autopkgtest X-Debbugs-Cc: t...@debian.org, s...@debian.org Hello! It has come to my attention that autopkgtest currently depends on rng-tools-debian as provider of rng-tools for its VMs to ensure entropy is available, or something. If the entropy provider uses the hwrng subsystem (HRNGDE

Bug#504044: rng-tools-debian: systemd complains about missing unit file

2025-01-11 Thread Thorsten Glaser
On Sat, 26 Oct 2024, Sven Geuer wrote: >Feel free to integrate my additions into your repo. You might want to >test the sysv-init functionality still works. According to my tests >sysv-init and systemd unit work flawlessly at least when running >autopkgtest from a Qemu VM. I’ve integrated that, b

Bug#1092660: openjdk-8 builds using GCC 13

2025-01-10 Thread Thorsten Glaser
Matthias Klose dixit: > openjdk-8 still builds using GCC 13, please try to build with the > default GCC. I check the various distros’ default GCC versions before each upload I do, so we’ll try for 8u442. Do you happen to know whether 8u supports GCC 14 by now or whether there are any known issue

Bug#774565: oh, still not jsdoc3

2025-01-10 Thread Thorsten Glaser
reopen 774565 thanks node-jsdoc2 is not jsdoc 3.x :/

Bug#1076728: elogind: privileged operation with polkit fails

2025-01-07 Thread Thorsten Glaser
On Tue, 7 Jan 2025, Andrew Bower wrote: >On Thu, Dec 19, 2024 at 09:53:47AM +, Mark Hindley wrote: >> Looking at docker.io's initscript, it checks if /sys/fs/cgroup is a mount >> point >> before mounting cgroups there. So, adding elogind to LSB header >> 'Should-Start' >I just tried exactly

Bug#1074595: dygraphs: Move from jsdoc-toolkit to node-jsdoc2

2024-12-26 Thread Thorsten Glaser
On Thu, 26 Dec 2024, Georges Khaznadar wrote: >The patch comes as >https://github.com/georgesk/dygraphs/blob/debian/debian/patches/node-jsdoc2.patch > >I guess that node-jsdoc2 may be stable for some time in the near future. > >If you do not mind, I am uploading a NMU for the package libjs-dygrap

Bug#1091448: linux: CDROM_LOCKDOOR does not lock the door

2024-12-26 Thread Thorsten Glaser
Package: src:linux Version: 5.10.226-1 Severity: normal X-Debbugs-Cc: t...@mirbsd.de I wrote a program to run… ioctl(i, CDROM_LOCKDOOR, 1) … on /dev/cdrom aka /dev/sr0, and it executes correctly. The program then holds the file descriptor open until SIGTERM. However, the only effect of th

Bug#1089812: poppler-data: cmap vs. cMap vs. CMap case confusion?

2024-12-12 Thread Thorsten Glaser
Package: poppler-data Version: 0.4.10-1 Severity: normal X-Debbugs-Cc: t...@mirbsd.de I noticed this: /usr/share/fonts/cMap/Identity-UTF16-H /usr/share/fonts/cmap/Identity-H /usr/share/fonts/cmap/Identity-V /usr/share/fonts/cmap/adobe-cns1 /usr/share/fonts/cmap/adobe-gb1 /usr/share/fonts/cmap/ado

Bug#995670: ITP: zig -- General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software

2024-11-29 Thread Thorsten Glaser
On Sat, 20 Jan 2024, Nick Hastings wrote: >I'll likely not even try packaging 0.11 or newer until it can once again >bootstrap. However I don't expect that to happen anytime soon. You can do it like OpenJDK does. First, package 0.10.x which can be bootstrapped from C with just the included code.

Bug#921657: xvfb-run: -e /dev/stderr does not work

2024-11-20 Thread Thorsten Glaser
On Wed, 20 Nov 2024, Simon McVittie wrote: >On Thu, 07 Feb 2019 at 17:59:42 +0000, Thorsten Glaser wrote: >> + xvfb-run -a -e /dev/stderr -s '-screen 0 1024x768x24 -fbdir /var/tmp' -- >> ctest -O ctest.log -j8 --output-on-failure >> /usr/bin/xvfb-run: 159: /usr/b

Bug#1087148: firefox-esr: [regression] leaves even unchanged sqlite files open

2024-11-08 Thread Thorsten Glaser
Package: firefox-esr Version: 128.4.0esr-1~deb11u1 Severity: normal X-Debbugs-Cc: t...@mirbsd.de, debian-...@lists.debian.org Ever since the major upgrade to 128, I noticed during backing up my system that firefox-esr leaves all or almost all of the sqlite files open on exit as if it crashed, leav

Bug#539352: /etc/init.d/mountkernfs.sh: Please mount debugfs when available in the kernel

2024-11-08 Thread Thorsten Glaser
On Fri, 8 Nov 2024, Mark Hindley wrote: >Reading the original thread, I share some of the concerns[1] about >enabling this globally. I’ve recently worked with debugfs+relayfs in a project, and I share the opinion of the kernel documentation that it should not be enabled by default (or rather, it

Bug#504044: hwrng

2024-11-05 Thread Thorsten Glaser
Dixi quod… >Das schließt dann sogar den ursprünglichen #504044 und einige weitere, >da es für alle RNGs gilt, die das hwrng-Interface verwenden. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/hw_random/core.c?id=be4000bc4644d027c519b6361f5ae3bbfc52c347 bye

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-04 Thread Thorsten Glaser
On Mon, 4 Nov 2024, Theodore Ts'o wrote: >> >> (I had tune2fs -r in the back of my head.) >> > >> >I've aways used mke2fs -m and tune2fs -m, myself. I personally very >> >rarely using -m 0. >> >> I use -r 2048 or something like that much more than -m, that’s why. > >Fortunately, if you had tried

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-04 Thread Thorsten Glaser
Dixi quod… >Attaching the current script again, for critique or public utility. Here is a version with sorted output… and an off-by-one fix. Oops. bye, //mirabilos -- [16:04:33] bkix: "veni vidi violini" [16:04:45] bkix: "ich kam, sah und vergeigte"... y2038chk-ext2fs.sh.gz Description: applic

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-04 Thread Thorsten Glaser
Dixi quod… >>So there's no mystery there. It's doing this because for revision 0 >>file system sb->s_first_ino and sb->s_inode_size are undefined. > >OK, so treating them as “you’ve got a Y2038 problem and maybe more” >is probably right? Attaching the current script again, for critique or public

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-04 Thread Thorsten Glaser
On Mon, 4 Nov 2024, Theodore Ts'o wrote: >> (I had tune2fs -r in the back of my head.) > >I've aways used mke2fs -m and tune2fs -m, myself. I personally very >rarely using -m 0. I use -r 2048 or something like that much more than -m, that’s why. >So there's no mystery there. It's doing this be

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-02 Thread Thorsten Glaser
On Sat, 2 Nov 2024, Theodore Ts'o wrote: >Can you send the full output of dumpe2fs -h? I suspect what happens >is that you might be testing a revision 0 file system. I can… and it is revision 0: tg@cafe:~ $ sudo dumpe2fs -h /dev/dm-5 dumpe2fs 1.46.2 (28-Feb-2021) Filesystem volume name: fs-pb

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-01 Thread Thorsten Glaser
Dixi quod… >= /dev/dm-8 >dumpe2fs 1.46.2 (28-Feb-2021) >Inode count: 65536 >Inodes per group: 8192 >Inode blocks per group: 256 >Inode size: 128 Let’s look at the superblock, first here, for orienting. 0430 fe 6b 25 67 02 00 ff ff 53 ef 01 00 01 00 00 0

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-01 Thread Thorsten Glaser
retitle 1086603 tune2fs, dumpe2fs: sometimes do not show the inode size found 1086603 1.44.5-1+deb10u4 found 1086603 1.47.0-2 thanks Testing the versions one up and one down: tg@cafe:~ $ sudo /var/cache/pbuilder/base.cow-buster-amd64/sbin/tune2fs -l /dev/dm-5 | fgrep Inode Inode count:

Bug#1086603: tune2fs, dumpe2fs: sometimes do not show the inode size

2024-11-01 Thread Thorsten Glaser
retitle 1086603 tune2fs, dumpe2fs: sometimes do not show the inode size thanks Dixi quod… >I am working on a tool that checks all your (mounted) >ext2/3/4fs for inode sizes < 256 (Y2038 bug) having Attaching that for public utility, for now; fixes welcome. It gets even weirder: dumpe2fs also do

Bug#1086603: tune2fs: sometimes does not show the inode size

2024-11-01 Thread Thorsten Glaser
Package: e2fsprogs Version: 1.46.2-2+deb11u1 Severity: normal X-Debbugs-Cc: t...@mirbsd.de I am working on a tool that checks all your (mounted) ext2/3/4fs for inode sizes < 256 (Y2038 bug) having just changed one with tune2fs -I, successfully, but… tg@cafe:~ $ sudo tune2fs -l /dev/dm-5 | fgrep I

Bug#504044: systemd complains about missing unit file

2024-10-25 Thread Thorsten Glaser
On Sat, 26 Oct 2024, Sven Geuer wrote: >Here is my repo [1] cloned from yours [0] with some commits added >implementing a systemd unit [2]. It covers soley what was requested >with bug #1039350. Please review. Thanks, will do. >It might make sense to unmerge bug #1039350 from #504044 and close o

Bug#1068024: Fwd: Accepted xz-utils 5.6.3-1 (source) into unstable

2024-10-25 Thread Thorsten Glaser
On Fri, 25 Oct 2024, Christoph Anton Mitterer wrote: >I guess this bug can be closed, can't it? Let’s take the submitter into explict Cc, to get an extra opinion. >If the version that Debian has reverted to after the backdoor was >disclosed or any of the supposedly cleaned versions would have st

Bug#1068024: Fwd: Accepted xz-utils 5.6.3-1 (source) into unstable

2024-10-25 Thread Thorsten Glaser
On Fri, 25 Oct 2024, Moritz Mühlenhoff wrote: >On Fri, Oct 25, 2024 at 08:00:22AM +0200, Sebastian Andrzej Siewior wrote: >> On 2024-10-24 23:38:31 [+0200], Thorsten Glaser wrote: >> > Do we trust these newer versions now? >> >> Yes. We started with 5.6.2 which was

Bug#1068024: Fwd: Accepted xz-utils 5.6.3-1 (source) into unstable

2024-10-24 Thread Thorsten Glaser
Do we trust these newer versions now? -- Forwarded message -- From: Debian FTP Masters Message-ID: To: debian-devel-chan...@lists.debian.org Date: Thu, 24 Oct 2024 21:20:07 + Subject: Accepted xz-utils 5.6.3-1 (source) into unstable Reply-To: Sebastian Andrzej Siewior X-Spam

Bug#504044: systemd complains about missing unit file

2024-10-13 Thread Thorsten Glaser
On Sun, 13 Oct 2024, Sven Geuer wrote: >> like that should look like, and most users will be served with >> rng-tools; rng-tools-debian is for legacy usecases, mostly. > >Unfortunately rng-tools is only a virtual package pulling in rng-tools- >debian. And even worse, autopkgtest installs rng-tools

Bug#504044: systemd complains about missing unit file

2024-10-12 Thread Thorsten Glaser
On Sat, 12 Oct 2024, Sven Geuer wrote: >systemd meanwhile complains about rng-tools-debian not providing a unit >file. Yes, it does not. Apparently, nobody has an idea how something like that should look like, and most users will be served with rng-tools; rng-tools-debian is for legacy usecases,

Bug#1083071: popularity-contest: runs twice

2024-10-04 Thread Thorsten Glaser
On Fri, 4 Oct 2024, Bill Allombert wrote: >On Tue, Oct 01, 2024 at 12:45:13AM +0200, Thorsten Glaser wrote: >> Package: popularity-contest >> Version: 1.76 >> Severity: normal >> X-Debbugs-Cc: t...@mirbsd.de >> >> -rw-r--r-- 1 root root 21239 Sep

Bug#1083071: popularity-contest: runs twice

2024-09-30 Thread Thorsten Glaser
Package: popularity-contest Version: 1.76 Severity: normal X-Debbugs-Cc: t...@mirbsd.de -rw-r--r-- 1 root root 21239 Sep 26 11:06 popularity-contest -rw-r--r-- 1 root root 21260 Sep 26 06:25 popularity-contest.0 -rw-r--r-- 1 root root 4875 Sep 19 11:06 popularity-contes

Bug#1082726: mc: .css file misrecognised as manpage, attempted to be formatted with troff on F3

2024-09-24 Thread Thorsten Glaser
Package: mc Version: 3:4.8.26-1.1 Severity: normal I move to a .css file and press F3 and get: ║╔══ Error ═══╗ 0:43║ ║║

Bug#1082647: copy_exec: [regression] ignores trailing slash, installs file as directory name

2024-09-24 Thread Thorsten Glaser
On Tue, 24 Sep 2024, Ben Hutchings wrote: >> Two, say people are expected to create the directories first. >> But in that case, copy_exec also must not create any missing >> directories any more *at all*, > >No, it was documented to do that for the case where no target argument >was given, and cha

Bug#1082647: copy_exec: [regression] ignores trailing slash, installs file as directory name

2024-09-24 Thread Thorsten Glaser
On Tue, 24 Sep 2024, Ben Hutchings wrote: >I suppose I can make this work again for bookworm, but I won't do so >for unstable. Then, perhaps issue a visible warning so that people can change their scripts? >This was not an intended feature. When specifiing a diectory as the >target you are supp

Bug#1082647: copy_exec: [regression] ignores trailing slash, installs file as directory name

2024-09-23 Thread Thorsten Glaser
Package: initramfs-tools-core Version: 0.142+deb12u1 Severity: serious Justification: hidden breakage for users, ought to be fixed in stable-pu X-Debbugs-Cc: t...@mirbsd.de In bullseye, this would work: copy_exec /usr/lib/klibc/bin/rnd_shuf /usr/libexec/ copy_exec /usr/sbin/rdate /usr/libexec/ I

Bug#1081794: E: /usr/bin/ssh-askpass[39]: too many open files (3 -> 212): Success

2024-09-14 Thread Thorsten Glaser
Hi Timo, >$ ssh-keygen -t ed25519 -f /tmp/test >$ ssh-add /tmp/test < /dev/null >E: /usr/bin/ssh-askpass[39]: too many open files (3 -> 212): Success >$ echo $? >1 > >key is not added to the agent this is quite puzzling. First guess: is $DISPLAY set and points to a usable X11 server? Second gue

Bug#1081501: musescore3: Buttons too big

2024-09-12 Thread Thorsten Glaser
On Thu, 12 Sep 2024, Paul Menzel wrote: > Using Debian sid/unstable with *gnome-shell* 47~rc-3 from the suite > *experimental*, and scaling the screen content to 200 %, the buttons > are too big in MuseScore as seen in the attachment. Hmm. Asides from this potentially being a GNOME issue, there’

Bug#1081331: /usr/share/man/man1/cvs.1.gz: some commands missing from headings?

2024-09-10 Thread Thorsten Glaser
Hi наб, >Quoth cvs(1): the manpage is autogenerated from *parts* of the texinfo source, using arcane and weird scripts. > suck, update, server & pserver, CVS commands > suck‒Download RCS ,v file raw > suck module/pa/th > [...] > > update, , suck, CVS commands > update‒

Bug#1081156: hunspell-en-gb: no /var/lib/dictionaries-common/hunspell/ file

2024-09-08 Thread Thorsten Glaser
Package: hunspell-en-gb Version: 1:7.1.0~rc3-3 Severity: normal X-Debbugs-Cc: t...@x61p.mirbsd.org Not sure whether this is an actual problem, but /var/lib/dictionaries-common/hunspell/ contains what I think are registration files for both hunspell-en-us and myspell-de-de-1901 but hunspell-en-gb i

Bug#1079399: linux: things written to tty vanish after a day or two

2024-08-22 Thread Thorsten Glaser
Package: src:linux Version: 5.10.223-1 Severity: normal X-Debbugs-Cc: t...@mirbsd.de In /etc/rc.local I write a text file to /dev/tty11. I have getty on 1-6 as usual and syslog on 12. After booting the system, I can confirm this works. A day or two later (I have not timed this exactly), I can st

Bug#1079393: lintian: mismatched-override cannot be overridden

2024-08-22 Thread Thorsten Glaser
Package: lintian Version: 2.118.0 Severity: normal X-Debbugs-Cc: t...@mirbsd.de I have trouble creating an override file that works for all architectures. On some architectures, lintian (correctly) issues: mksh: statically-linked-binary [bin/lksh] I can override this. But on other architectures,

Bug#1079165: ansiweather: illegible time format

2024-08-20 Thread Thorsten Glaser
Package: ansiweather Version: 1.11-1.1 Severity: normal Tags: l10n X-Debbugs-Cc: t...@mirbsd.de ansiweather insists on using the weird AM/PM format used by a vast minority of people instead of 24-hour clock format for e.g. sunrise/sundown, even if I set the metric option or the locale. -- System

Bug#856877: Bug#983423: schroot: regression presumably in 1.6.13-4 after fixing #983423

2024-08-20 Thread Thorsten Glaser
in Message --- Hi, On 2023-08-04 21:40, Thorsten Glaser wrote: > Hi, > > some of the buildds still use Linux 4.19 but klibc has started to > require Linux 5.1-specific features with the latest sid upload. > This has implications on mksh (for the mksh-static and lksh binaries

Bug#1006451: drop mimimi-maven-plugin as its only user was removed

2024-08-19 Thread Thorsten Glaser
reassign 1006451 ftp.debian.org retitle 1006451 RM: minify-maven-plugin -- RoM; only remaining user gone severity 1006451 normal thanks guacamole-client was RoQA'd in #926276 so this can be garbage-collected

Bug#856877: Bug#983423: schroot: regression presumably in 1.6.13-4 after fixing #983423

2024-08-19 Thread Thorsten Glaser
Simon McVittie dixit: >was rather recent at that time, but hopefully we no longer have any >machines that are running Debian 8 kernels... The varios MIPS buildds run 4.19 and some even 4.9 kernels (AFAIHH due to hardware/patch constraints), which has led to problems (e.g. I had to disable klibc b

Bug#983423: schroot: regression presumably in 1.6.13-4 after fixing #983423

2024-08-19 Thread Thorsten Glaser
Hi Simon, thanks for testing. >I'm using Thorsten's regression report in #983423 as my representative >sample of a package that regressed with schroot 1.6.13-4, because mksh >builds much more quickly than gcc-14 (You can add mksh-firstbuilt to DEB_BUILD_OPTIONS so it doesn’t build and test binar

Bug#983423: schroot: regression presumably in 1.6.13-4 after fixing #983423

2024-08-19 Thread Thorsten Glaser
Simon McVittie dixit: >> as well as open("/dev/tty", O_RDWR, 0) > >Asserting that /dev/tty is the correct device node and has appropriate >permissions should cover that. Totally not, unfortunately: it only works when it actually has a ctty. >> and later F_DUPFD and F_SETFD, FD_CLOEXEC fcntl > >T

Bug#983423: schroot: regression presumably in 1.6.13-4 after fixing #983423

2024-08-19 Thread Thorsten Glaser
Simon McVittie dixit: >On Mon, 19 Aug 2024 at 16:27:24 +0000, Thorsten Glaser wrote: >> mksh actually does things inside script(1) that use the tty > >For the purposes of having a test-case for schroot that doesn't require >mksh, perhaps a good approximation to this would b

Bug#911312: firefox-esr: automatical download of libgmpopenh264.so with default settings

2024-08-19 Thread Thorsten Glaser
Package: firefox-esr Version: 115.14.0esr-1~deb11u1 Followup-For: Bug #911312 X-Debbugs-Cc: t...@mirbsd.de Control: severity -1 serious The binary plugin is still automatically downloaded (and likely used). This is likely a violation of “main” rules. -- Package-specific info: -- Addons package

Bug#983423: schroot: regression presumably in 1.6.13-4 after fixing #983423

2024-08-19 Thread Thorsten Glaser
Simon McVittie dixit: >On Sun, 18 Aug 2024 at 23:44:57 +0000, Thorsten Glaser wrote: >> On three buildds, mksh FTBFS already because the whole >> /dev/ptmx and /dev/pts stuff is malfunctioning again > >Which buildds? Are you referring to -ports builds >https://buildd.deb

Bug#983423: schroot (1.6.13-4) unstable; urgency=medium

2024-08-18 Thread Thorsten Glaser
Hi, have you actually tested that this works? On three buildds, mksh FTBFS already because the whole /dev/ptmx and /dev/pts stuff is malfunctioning again, after like 15 years of it working after having had to fight for packages being allowed to depend on it to obtain a pty/tty for tests during bu

Bug#1079020: lintian: bin-sbin-mismatch vs. shells

2024-08-18 Thread Thorsten Glaser
Package: lintian Version: 2.118.0 lintian reports now, after dh_movetousr: X: mksh: bin-sbin-mismatch bin/mksh -> usr/bin/mksh [usr/share/doc/mksh/examples/uhr] I can only assume that this is due to the #!/bin/mksh shebang in that file. If so, please carry a list of interpreters in lintian whos

Bug#1078772: pmake: “bmake: no system rules (sys.mk).”

2024-08-15 Thread Thorsten Glaser
Santiago Vila dixit: > El 15/8/24 a las 22:49, Thorsten Glaser escribió: >> a package that Build-Depends on pmake and uses it >> in its debian/rules build targets in a clean bullseye chroot > > Did you really mean bmake (not pmake) here? No, pmake. > If yes: Can y

Bug#1078772: pmake: “bmake: no system rules (sys.mk).” under qemu-user

2024-08-15 Thread Thorsten Glaser
retitle 1078772 pmake: “bmake: no system rules (sys.mk).” under qemu-user severity 1078772 important thanks Dixi quod… >Hm, but I just tested with pmake_1.111-3.2_armel.deb from >the archive, and it also failed. > >Is it possible that it doesn’t work right under qemu-user? Apparently, this is it

Bug#1078772: pmake: “bmake: no system rules (sys.mk).”

2024-08-15 Thread Thorsten Glaser
Dixi quod… >stracing shows that, despite the -m option being passed by >the pmake wrapper, it still accesses /usr/share/mk/. Hm, but I just tested with pmake_1.111-3.2_armel.deb from the archive, and it also failed. Is it possible that it doesn’t work right under qemu-user? (Which would also be

Bug#1078772: pmake: “bmake: no system rules (sys.mk).”

2024-08-15 Thread Thorsten Glaser
Package: bmake Version: 20200710-14+deb11u1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: t...@mirbsd.de Building a package that Build-Depends on pmake and uses it in its debian/rules build targets in a clean bullseye chroot completely fails with: bmake: no system rules (s

Bug#1073608: Request for clarification on RC-ness of DEP17 bugs

2024-08-15 Thread Thorsten Glaser
Paul Gevers dixit: > The Release Team considers packages that ship files in /usr-merged aliased > locations RC buggy. > > We have put our trust in Helmut to come up with the right solutions during the > preparation for trixie Hmpf. He’s doing the dirty work for Md and bluca now. >, so I'm asking

Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Thorsten Glaser
Helmut Grohne dixit: >> Maybe the protective diversions also protect against this problem as well >> as the problem of moved files? I unfortunately failed to spot where the >> protective diversions were added in dh_movetouser (if that even is the >> right place to be looking), so I'm fairly sure

Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-07 Thread Thorsten Glaser
(Another data point is that there’s versions of mksh with version numbers larger than what’s in sid around in my own repo, for those wanting to follow CVS snapshots more closely, backported to all versions up to sarge, so bookworm users can very well have mksh packages with a version number that is

Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-07 Thread Thorsten Glaser
Helmut Grohne dixit: >that the way people tend to use mksh is by adding a local diversion for Unfortunately not. The way we have to do it since squeeze, when dash unilaterally broke cross-package coordination, is: dpkg-reconfigure dash ⇒ remove its owning of /bin/sh (so it reverts to bash) ln

Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-06 Thread Thorsten Glaser
Russ Allbery dixit: >Thorsten Glaser writes: > >> You got your merged /usr already, and to force packages to move their >> files WILL break users’ systems. In particular, mksh as /bin/sh is a >> supported configuration. > >Could you explain how this would break a us

  1   2   3   4   5   6   7   8   9   10   >