Join us in Montreal on March 28th and 29th for a Bug Squashing Party!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello! We're happy to announce we will be hosting a Bug Squashing Party in Montreal on Friday March 28th and Saturday 29th. The event will take place at the "Ateliers de la transition socio-écologique", near the Beaubien subway station. A short r

Re: Bug#1096150: ITP: forwords -- A very simple but effective tool to learn foreign language words

Does it include the data files or just software? If not, does this data exist and is easy to find? Best -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galile

Bug#1098438: ITP: python-simple-pid -- Simple and easy-to-use PID controller

Package: wnpp Severity: wishlist Owner: Alexander Sulfrian X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org * Package name: python-simple-pid Version : 2.0.1 Upstream Contact: Martin Lundberg * URL : https://github.com/m-lundberg/simple-pid

Bug#1098424: ITP: python-packageurl -- Package URL (purl) spec Python implementation

Package: wnpp Severity: wishlist Owner: Santiago Ruano Rincón X-Debbugs-Cc: debian-devel@lists.debian.org, 1089...@bugs.debian.org * Package name: python-packageurl Version : 0.16.0 Upstream Contact: https://gitter.im/package-url/Lobby * URL : https://github.com/packag

Re: Packages with a history of security issues and whose packaged version is not up to date

On 2025-02-20 15:37, Raphael Hertzog wrote: So provided that we don't spam maintainers with "new upstream release" bug reports hours after the upstream release, and that we don't open new bug reports for as long as the former one has not been closed (but instead update the existing bug with the n

Re: Packages with a history of security issues and whose packaged version is not up to date

Hi, On Mon, 17 Feb 2025, Santiago Ruano Rincón wrote: > Other than to take into account recent activity, I think it is important > to look for possible reasons for not packaging the version reported by > uscan, before filing a bug report. I actually see it the other way. When a new upstream relea

Re: Debian Policy 4.7.1.0 and program names

Am 20.02.25 um 11:13 schrieb Vincent Lefevre: Hi, On 2025-02-20 17:51:40 +0800, Sean Whitton wrote: I just pushed version 4.7.1.0 of the Debian Policy Manual and related documents to the binary-NEW queue for sid. Below you will find the significant normative changes from the previously-announce

Debian Policy 4.7.1.0 and program names

Hi, On 2025-02-20 17:51:40 +0800, Sean Whitton wrote: > I just pushed version 4.7.1.0 of the Debian Policy Manual and related > documents to the binary-NEW queue for sid. > Below you will find the significant normative changes from the > previously-announced release of Policy (4.7.0.0). [...] > 10

Re: Advice for directory to symlink transition

On Thu, Feb 20, 2025 at 10:05:36AM +0100, Timo Röhling wrote: > Hello, > > I have run into an unexpected quirk of dpkg (I think) and would like to > solicit some advice on how to handle it. > > For better cross building/multi-arch support, I recently moved a bunch of > files from python3-numpy to

Re: Advice for directory to symlink transition

Hi, I assume it is because the _core directory is new in NumPy 2, so dpkg can just create the symlinks at unpack time. The latter two directories need to be transitioned from a real directory in NumPy 1 to a symlink during the package upgrade. Apparently this step fails, leaving an empty dire

Advice for directory to symlink transition

Hello, I have run into an unexpected quirk of dpkg (I think) and would like to solicit some advice on how to handle it. For better cross building/multi-arch support, I recently moved a bunch of files from python3-numpy to python3-numpy-dev. More precisely, I moved /usr/lib/python3/dist-pac