Bug#1110097: marked as done (general: boot failure)

Your message dated Wed, 30 Jul 2025 00:39:56 +0200 with message-id and subject line Re: Bug#1110097: general: boot failure has caused the Debian Bug report #1110097, regarding general: boot failure to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1110105: ITP: myositis -- Simple check list application with import/export and printing support

Package: wnpp Severity: wishlist Owner: Benoît Rouits X-Debbugs-Cc: debian-devel@lists.debian.org, brou...@free.fr * Package name: myosotis Version : 0.1.0 Upstream Contact: Benoît Rouits * URL : https://git.noise.rocks/ben/myosotis * License : GPL Programmi

Bug#1110097: general: boot failure

Package: general Severity: important X-Debbugs-Cc: brian.bi...@tutamail.com Dear Maintainer, On laptop when plugged in debian 13 fails to boot or goes into boot loop have to unplug and boot into recovery mode to get it to boot

Bug#1110089: ITP: phoenix-esr -- phoenix-esr - A Firefox-ESR config designed to put the user first.

Package: wnpp Severity: wishlist Owner: wnpp X-Debbugs-Cc: debian-devel@lists.debian.org * Package name : phoenix-esr Version : 2025.07.11.1-1 * URL : https://phoenix.celenity.dev * License : GPL-3+ Description : phoenix-esr - A Firefox-ESR config designed to put the user first. phoenix-esr -

Re: when to drop t64 postfix from lib packages?

On Tue, Jul 29, 2025 at 07:10:10PM +0500, Andrey Rakhmatullin wrote: > On Tue, Jul 29, 2025 at 03:40:09PM +0200, Jakub Ružička wrote: > > When should I drop t64 postfix from Debian lib packages? > > Only when bumping the soname. To expand a bit on that answer, the reason for adding the postfix wa

Re: when to drop t64 postfix from lib packages?

On Tue, Jul 29, 2025 at 03:40:09PM +0200, Jakub Ružička wrote: When should I drop t64 postfix from Debian lib packages? Only when bumping the soname. -- WBR, wRAR signature.asc Description: PGP signature

when to drop t64 postfix from lib packages?

Hello, I wonder how to proceed with libraries affected by 64bit time_t transition in Debian and upstream repos going forward. In particular, libraries of src:knot gained t64 postfix: Package: libdnssec9t64 Provides: ${t64:Provides} Replaces: libdnssec9 Breaks: libdnssec9 (<< ${so

Re: tooling to perform updates to many packages in a team?

Hi! On Tue, 2025-07-29 at 09:35:15 +0200, Lucas Nussbaum wrote: > I will be looking into doing some mass updates/cleanup in the context of > the Ruby team, and was wondering: what are the useful tools in that > case? > > I'm aware of: > - the salsa CLI tool (in devscripts) > - the glab package >

Re: tooling to perform updates to many packages in a team?

On Tue, Jul 29, 2025 at 09:41:47AM +0200, Niels Thykier wrote: > Lucas Nussbaum: > > Hi, > > > > I will be looking into doing some mass updates/cleanup in the context of > > the Ruby team, and was wondering: what are the useful tools in that > > case? > > > > I'm aware of: > > - the salsa CLI too

Re: tooling to perform updates to many packages in a team?

Hi, The salsa tool has been designed for massive updates and used successfully by some teams for massive updates such as : - switch to DEP14 - configure IRC channel, tag-pending hooks - ... Raphaël used it, me too for JS Team (the --group + --all permit this) The mr tool is used by Perl Team to

Re: tooling to perform updates to many packages in a team?

Lucas Nussbaum: Hi, I will be looking into doing some mass updates/cleanup in the context of the Ruby team, and was wondering: what are the useful tools in that case? I'm aware of: - the salsa CLI tool (in devscripts) - the glab package - mr (multi repo) - lintian-brush What are teams typicall

tooling to perform updates to many packages in a team?

Hi, I will be looking into doing some mass updates/cleanup in the context of the Ruby team, and was wondering: what are the useful tools in that case? I'm aware of: - the salsa CLI tool (in devscripts) - the glab package - mr (multi repo) - lintian-brush What are teams typically using? Lucas