Bug#689212: unzip doesn't restore uid/gid

Package: unzip Version: 6.0-7 Severity: important Tags: upstream When unzipping a file with -X unzip doesn't restore uid/gid information although it is present in the zip file. I asked about this on the infozip forum and they confirmed it was a bug in the build system. They also supplied patches

Bug#705740: gprolog: update to newer version

compiled it on amd64 and powerpc on which it runs without any problems. Thanks, Kind regards, Axel Scheepers -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.8.8 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C

Bug#742803: ksh: in vi-mode using esc= on an empty line opens a new fd device

/ 0@ 1@ 10@ 11@ 12@ 13@ 2@ 3@ 4@ 5@ 6@ 7@ 8@ 9@ I'm not sure if this is intended behaviour. Kind regards, Axel Scheepers -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64

Bug#742815: twm: when using mplayer -fs (fullscreen) twm reports X11 badwindow errors and terminates

. It happens not all the time though, sometimes everything plays ok. I've switched to openbox and since then i never had the error so i think it's related to twm. Kind regards, Axel Scheepers -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing

Bug#843978: opensmtpd: wrong permissions in /var/spool/smtpd

On Tue, 7 Feb 2017 16:04:59 +0100 Harald Dunkel wrote: > Attached you can find a suggestion for a fix. It kicks /var/spool/smtpd > out of the package, relying upon smtpd itself to create the directories > with the right permissions on the first startup. Maybe its rude, but it >

Bug#756877: pax: claims POSIX compliance but doesn't support pax format

Hello, Is there a reason why the heirloom pax can't be imported instead? Kind regards, Axel Scheepers

Bug#932722: Please add CONFIG_CRYPTO_ZSTD

Package: linux-image-amd64 Version: 4.19+105 Severity: wishlist Dear maintainer(s), I'm trying to use zram with zstd compression, a bit of research tells me this is done by the crypto framework(*). Including CONFIG_CRYPTO_ZSTD should enable zstd for zram. Thank you, Kind regards, Axel

Bug#776413: Please include ed in base

Hi, Can we please have ed back in base? If a request for removal from one person is honored then maybe more people complaining about it missing will work too. Thanks, Kind regards, Axel

Bug#776413: Please include ed in base

ind regards, Axel Scheepers

Bug#983591: iproute2: running 'ip -6 -r route' results in printing an unitialized buffer for the hostname on 'dev' routes

strncpy(buf, n, buflen); 1128return n; 1129} 1130} 1131#endif results in: ./ip/ip -6 -r r XXX: here n is 'localhost' localhost dev lo proto kernel metric 256 pref medium Something better then this awful hack should be implemented i gue

Bug#992038: systemd: regression with systemd-networkd + dropbear initramfs and kernel ip autoconfig(?)

to help resolve the issue as long as time permits. Kind regards, Axel Scheepers

Bug#983591: iproute2: running 'ip -6 -r route' results in printing an unitialized buffer for the hostname on 'dev' routes

Hello Luca, On Thu, Sep 02, 2021 at 11:44:09AM +0100, Luca Boccassi wrote: > This is fixed for me with 5.13, which is now in testing - can you > confirm? Yes indeed it works on testing for me too, thanks! Kind regards, Axel Scheepers

Bug#992038: systemd: regression with systemd-networkd + dropbear initramfs and kernel ip autoconfig(?)

routablefailed I'm not sure how common this failure is, maybe it's also the fritzbox's fault for doing something weird. Can't imagine other people not running into this otherwise. Kind regards, Axel Scheepers

Bug#992038: debug logs + severity

DHCP CLIENT (0x475755a3): STOPPED After which both ipv4 and ipv6 stop working. I can still reach the box due to the kernel dhcp configuration done, wired fails also but keeps it's pre systemd-networkd configured address. Kind regards, Axel Scheepers

Bug#992038: systemd: regression with systemd-networkd + dropbear initramfs and kernel ip autoconfig(?)

a local package with this patch included, will see if that works. v249 is quite different in this area. Fwiw, the machines are connected to a Fritz!Box 5490 router/access point and has ipv6 prefix delegation configured (but this is not used for the clients). Kind regards, Axel Scheepers On Wed, Aug 11

Bug#992038: systemd: regression with systemd-networkd + dropbear initramfs and kernel ip autoconfig(?)

Hi Michael, I've installed v249, will let you know if it still doesn't work. Kind regards, Axel Scheepers On Tue, Aug 10, 2021 at 10:55 AM Michael Biebl wrote: > Control: tags -1 + moreinfo > > Am 09.08.21 um 19:12 schrieb Michael Biebl: > > Am 09.08.21 um 18:03 schrieb

Bug#992038: systemd: regression with systemd-networkd + dropbear initramfs and kernel ip autoconfig(?)

t a kernel parameter because this delays the prompt when a console is attached. Kind regards, Axel Scheepers On Mon, Aug 9, 2021 at 7:13 PM Michael Biebl wrote: > Am 09.08.21 um 18:03 schrieb Axel Scheepers: > > Package: systemd > > Version: 247.3-6 > > Severity:

Bug#992038: systemd: regression with systemd-networkd + dropbear initramfs and kernel ip autoconfig(?)

ave reverted the production system to use debian's /etc/network/interfaces file instead of other options to keep it standard and hence more tested. I can't test this anymore, sorry. Kind regards, Axel Scheepers

Bug#1010071: wireguard-tools: the wg tool outputs color on monochrome terminals

Hi again, This patch avoids out of bounds access. --- terminal.c.orig 2022-04-24 13:57:34.231668500 +0200 +++ terminal.c 2022-04-24 14:34:35.798847083 +0200 @@ -24,8 +24,10 @@ mode = true; else if (var && !strcmp(var, "never")) mode = false; -

Bug#1010071: patch

Hi, Complaining doesn't help. I've created the following patch which fixes the issue. --- terminal.c.orig 2022-04-24 13:57:34.231668500 +0200 +++ terminal.c 2022-04-24 13:57:38.519643229 +0200 @@ -24,8 +24,11 @@ mode = true; else if (var && !strcmp(var, "never"))

Bug#1010806: apt: Avoid color output on monochrome terminals

Op wo 25 mei 2022 21:36 schreef Adam Borowski : > And how, pray tell, may I know in advance what terminal will be used on the > other end of the serial link? Especially if it's a box people ssh into > from > random places, using a plethora of various terminals on their side? > That's the most

Bug#1010806: apt: Avoid color output on monochrome terminals

Hi, On Mon, May 16, 2022 at 6:30 PM Adam Borowski wrote: > The terminfo entries stopped being maintained by late 80's. And even if > they were, every new terminal would need to wait several years before it can > have its definition known by operating systems (today, distributions). > The

Bug#1010806: apt: Avoid color output on monochrome terminals

Hi, Thanks for your quick response and thoughtful comments, On Tue, May 10, 2022 at 6:04 PM Julian Andres Klode wrote: > On Tue, May 10, 2022 at 04:54:21PM +0200, Adam Borowski wrote: > > You mean monochrome terminals such as "xterm", "rxvt", "linux", ...? Yes, and screenreaders or other

Bug#1010806: apt: Avoid color output on monochrome terminals

Hi, Regarding terminal capabilities, On Tue, May 10, 2022 at 6:04 PM Julian Andres Klode wrote: > > in programs. But there's no common characteristic of a terminal that'd > > allow autodetecting your wishes. The 'proper' way would be to query the terminfo entry Co I think. The best way to

Bug#981139: Status

Hi, What is the current status? I did a quick and dirty build with the commit mentioned (https://github.com/FRRouting/frr/commit/4f08c715db6893ff439d0a39bf4506cd26256d13.patch) and this resolves the issue for me. It would be nice to have this bug resolved. Kind regards, Axel Scheepers

Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales

a different locale setting for date and lang. This however breaks gnome since it requires a utf-8 locale and I'm unable to select C.UTF-8 at installation. A workaround is to uncomment the C.UTF-8 locale in /etc/locale.gen and run dpkg-reconfigure locales after installation. Kind regards, Axel Scheepers

Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales

andom locale to be > generated, then you should be able to select the C.UTF-8 locale as > default. Thanks, yes indeed that's better. Kind regards, Axel Scheepers

Bug#1060288: locales: Please allow selection of C.UTF-8 when (re)configuring locales

fine during a major upgrade, between the time libc6 and locales > are unpacked. Ah ok I understand, thanks for explaining. > I have just implemented that in git, the current behaviour is a > left-over from before the time C.UTF-8 existed. Thanks! Kind regards, Axel Scheepers

Bug#1057417: systemd tmpfiles seems to delete lost+found again

Yes you are right, I overlooked the existing exception, it is indeed probably the setup which causes it. I had rebooted the box previously and tested only the clearing service. Kind regards, Axel Op di 5 dec. 2023 00:38 schreef Michael Biebl : > Am 04.12.23 um 23:09 schrieb Michael Biebl: > >

Bug#1057417: systemd tmpfiles seems to delete lost+found again

On Mon, Dec 4, 2023 at 6:58 PM Luca Boccassi wrote: > You have a separate, non-tmpfs filesystem on /tmp? How did you end up > with such a setup? Hi Luca, I always configure separate /var, /tmp and /home filesystems. In this case the system is also low on ram so tmpfs is not really an option (I

Bug#1057417: systemd tmpfiles seems to delete lost+found again

On Mon, Dec 4, 2023 at 8:27 PM Luca Boccassi wrote: > But the main point is, it's fine if you do a custom local setup with > the appropriate local configuration, but then you also need to add the > appropriate config for tmpfiles.d. You can either mask or replace > tmp.conf, simply add your own

Bug#1057417: systemd tmpfiles seems to delete lost+found again

Package: systemd Version: 252.17-1~deb12u1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? (previous bug at #788193). Automatic run of e2scrub reported: So sorry, the automatic e2scrub of /tmp on mahogany.vultrusercontent.com failed. A log of what happened

Bug#1010806: apt: Avoid color output on monochrome terminals

1010...@bugs.debian.org On Thu, 26 May 2022 11:03:25 +0200 Axel Scheepers wrote: > Or the other way around as I proposed. The entire problem of knowing what > and how to use color goes away when curses is used. Would you accept a > patch for using that instead? I've forgot about thi

Bug#1010806: apt: Avoid color output on monochrome terminals

(NULL, 1, ) == OK) { n = tigetnum("colors"); del_curterm(cur_term); } return n; } You should also link ncurses (which brings in a bit of cruft). Kind regards, Axel On Mon, Jan 29, 2024 at 1:53 PM Axel Scheepers wrote: > > 1010...

Bug#743650: looks like a terminal config problem to me

Hi, On Tue, 22 Nov 2016 10:50:23 +0100 Adam Borowski wrote: > It's not a text program's duty to choose the exact shades, it's the terminal > that's supposed to provide something readable. And for the 16 basic colors, > all of them are supposed to be readable against the default background. ...