Re: Bug#1108665: override: cron:admin/optional

2025-07-02 Thread наб
On Wed, Jul 02, 2025 at 11:24:59PM +0200, Alexandre Detiste wrote: > Le mer. 2 juil. 2025 à 17:35, Chris Hofstaedtler a écrit : > > > Without any particular hat: I would expect someone wanting to drop cron > > > to come up with some analysis of what remains to be done and what is > > > going to br

Re: Trixie: cryptsetup hangs at boot when trying to create a device file via device mapper

2025-07-02 Thread Konstantin Khomoutov
On Wed, Jul 02, 2025 at 01:10:16PM +0200, Guilhem Moulin wrote: [...] > > Hence I'm inclined to think it's still an "early boot" issue > > No it's not. > > >> Do you have systemd-cryptsetup installed? (See the NEWS entry for > >> systemd=256-2, which I guess should be in the release notes too.)

Re: Bug#1108665: override: cron:admin/optional

2025-07-02 Thread Alexandre Detiste
Le mer. 2 juil. 2025 à 17:35, Chris Hofstaedtler a écrit : > > Without any particular hat: I would expect someone wanting to drop cron > > to come up with some analysis of what remains to be done and what is > > going to break if that were to be implemented. Hi, this has been on the back burner f

Re: Bug#1108665: override: cron:admin/optional

2025-07-02 Thread Cyril Brulebois
Hi, Chris Hofstädtler (2025-07-02): > in a discussion today on IRC #debian-devel, it was mentioned that > cron is "important". However during the trixie development cycle, > many more packages started installing systemd timer units. > On a default install, I would therefore argue that cron is n

Re: Bug#1108665: override: cron:admin/optional

2025-07-02 Thread Chris Hofstaedtler
On Wed, Jul 02, 2025 at 05:29:58PM +0200, Cyril Brulebois wrote: > Hi, > > Chris Hofstädtler (2025-07-02): > > in a discussion today on IRC #debian-devel, it was mentioned that > > cron is "important". However during the trixie development cycle, > > many more packages started installing system

Re: github repo with submodules: non usable source tarball

2025-07-02 Thread Noah Meyerhans
On Wed, Jun 25, 2025 at 09:38:07AM +0200, Jerome BENOIT wrote: > I am considering to package a software stored at GitHub. > It is under active development and it builds well in Sid. > However it appears that its source tarball at GitHub does not > contain all the necessary material: its submodules

Bug#1108643: Trixie Keyboard Shortcut Issues within VMWare

2025-07-02 Thread Thomas Goirand
On 7/2/25 09:34, David Kennedy wrote: Package: general Version: Unknown I am not sure about the package I’m afraid and I did email debian-user for advice as per this “If you are unable to determine which package your bug report should be filed against, please send e-mail to the Debian user

Bug#1108657: ITP: golang-bugst-cleanup -- Go library providing a signal.Interrupt/CTRL-C interruptable context

2025-07-02 Thread Nicolas Peugnet
Package: wnpp Severity: wishlist Owner: Nicolas Peugnet * Package name: golang-bugst-cleanup Version : 1.0.0-1 Upstream Author : bug.st * URL : https://github.com/bugst/go-cleanup * License : BSD-3-clause Programming Lang: Go Description : Go library pr

Re: Trixie: cryptsetup hangs at boot when trying to create a device file via device mapper

2025-07-02 Thread Guilhem Moulin
On Wed, 02 Jul 2025 at 13:13:39 +0300, Konstantin Khomoutov wrote: > On Wed, Jul 02, 2025 at 01:00:39AM +0200, Guilhem Moulin wrote: >> I've noticed that the boot process brings up the LUKS2-encrypted root >> parition just fine > > In my original mail I've mistakenly said "boot" there ^, but in fac

Re: Trixie: cryptsetup hangs at boot when trying to create a device file via device mapper

2025-07-02 Thread Konstantin Khomoutov
On Wed, Jul 02, 2025 at 01:00:39AM +0200, Guilhem Moulin wrote: [...] > > I've hit a regression after upgrading my Debian 12 laptop to Trixie - > > in short, cryptsetup hangs at *early* boot stage when it apparently trying > > to > > create a device mapper node for a LUKS1 device it successfully

Bug#1108643: Trixie Keyboard Shortcut Issues within VMWare

2025-07-02 Thread David Kennedy
Package: general Version: Unknown I am not sure about the package I'm afraid and I did email debian-user for advice as per this "If you are unable to determine which package your bug report should be filed against, please send e-mail to the Debian user mailing list