Bug#1008084: adduser --system behavior if trying to create existing locked account

2022-03-22 Thread Marc Haber
Package: adduser Version: 3.121 Severity: important Tags: confirmed If adduser --system is called to create a user that already exists as a system accout but is locked, adduser should not error out and instead silently unlock the account, restore the password to a useable state and set the shell

Bug#1008083: Implement deluser --system configurability

2022-03-22 Thread Marc Haber
Package: adduser Version: 3.121 Severity: important This is one of the bugs resulting from the policy and debian-devel consultations that happened in March 2022. deluser --system should not remove an account but instead lock it (same procedure than deluser --lock, see #1008082) There should be

Bug#521883: adduser: Have different regexps for system and user account names

2022-03-22 Thread Marc Haber
Control: retitle -1 Have different regexps for system and user account names thanks I apologize for botching up the first instance of this message. The following is identical to message #64 and quoted for completeness. On Sun, Oct 23, 2016 at 03:52:57PM +0200, Guillem Jover wrote: > I've

Bug#1008082: implement deluser --system --lock functionality

2022-03-22 Thread Marc Haber
Package: adduser Version: 3.121 Severity: important This is one of the bugs resulting from the policy and debian-devel consultations that happened in March 2022. There should be an option --lock for deluser --system that leaves the account intact but makes login impossible (by setting an invalid

Bug#1008081: implement SYS_DIR_MODE

2022-03-22 Thread Marc Haber
Package: adduser Version: 3.121 Severity: important This is one of the bugs resulting from the policy and debian-devel consultations that happened in March 2022. It is the prerequisite to address #202943, #202944, #442627 and #782001. adduser --system should chmod the home directory of the

Bug#521883: adduser: Have different regexps for system and user account names

2022-03-22 Thread Marc Haber
Bcc: Subject: Re: Bug#521883: adduser: Please accept underscore prefixed system names Reply-To: In-Reply-To: <20161023135257.qdgedfnzd2q2w...@gaara.hadrons.org> Control: retitle -1 Have different regexps for system and user account names thanks On Sun, Oct 23, 2016 at 03:52:57PM +0200,

Bug#1008080: Some sites do not work

2022-03-22 Thread Stéphane Glondu
Package: chromium Version: 99.0.4844.74-1 Severity: grave Dear Maintainer, On two different, up-to-date Debian testing machines, at least the following sites: https://framatalk.org https://replit.com do not work properly (but not all sites are broken). I get spurious "Your connection was

Bug#1008079: ITP: libanyevent-aio-perl -- Perl module to seamlessly integrate IO::AIO into AnyEvent

2022-03-22 Thread Nick Morrott
Package: wnpp Owner: Nick Morrott Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libanyevent-aio-perl Version : 1.1 Upstream Author : Marc A. Lehmann * URL : https://metacpan.org/release/AnyEvent-AIO *

Bug#1008078: zstd: Bump version to 1.4.10

2022-03-22 Thread Sedat Dilek
Package: zstd Version: 1.4.9+dfsg-1 Severity: normal X-Debbugs-Cc: sedat.di...@gmail.com Dear Maintainer, I use where I can ZSTD to compress and decompress in things of file archiving. The Linux kernel introduced a stable API on ZSTD v1.4.10 with Linux v5.16. This version was tagged after my

Bug#1008077: new upstream, new name

2022-03-22 Thread Harald Dunkel
Package: kafkacat Version: 1.6.0-1 Upstream has changed the name and provides a new version 1.7.0: https://github.com/edenhill/kcat Would it be possible to update the package in Debian? I wouldn't care if the source and binary packages are still called kafkacat. Thank you very much

Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long

2022-03-22 Thread YunQiang Su
Paul Gevers 于2022年3月22日周二 04:04写道: > > Hi mips porters, > > On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers wrote: > > The Release Team considers packages that are out-of-sync between testing > > and unstable for more than 60 days as having a Release Critical bug in > > testing [1]. Your package

<    1   2