OpenMPI 5.0 to be 32-bit only ?

Hi I've been pinged by the upstream maintainer of OpenMPI    Jefff Squyres as to our opinions on maintaining 32-bit support. See a  thread here: https://github.com/open-mpi/ompi/pull/11282 Until now I've asked for OMPI to hold off going to 64-bit only; saying we can help with the maintenance

Bug#1030756: ITP: python-test-stages -- Run Tox, Nox, etc. tests in groups, stopping on errors

Package: wnpp Severity: wishlist Owner: Peter Pentchev X-Debbugs-Cc: debian-devel@lists.debian.org, team+pyt...@tracker.debian.org, r...@debian.org * Package name: python-test-stages Version : 0.1.1 Upstream Contact: Peter Pentchev * URL : https://gitlab.com/ppentche

Bug#1030757: ITP: python-parse-stages -- Parse a mini-language for selecting objects by tag or name

Package: wnpp Severity: wishlist Owner: Peter Pentchev X-Debbugs-Cc: debian-devel@lists.debian.org, team+pyt...@tracker.debian.org, r...@debian.org * Package name: python-parse-stages Version : 0.1.1 Upstream Contact: Peter Pentchev * URL : https://gitlab.com/ppentch

Re: OpenMPI 5.0 to be 32-bit only ?

On 2023-02-07 10:54, Alastair McKinstry wrote: Hi I've been pinged by the upstream maintainer of OpenMPI    Jefff Squyres as to our opinions on maintaining 32-bit support. See a  thread here: https://github.com/open-mpi/ompi/pull/11282 Until now I've asked for OMPI to hold off going to 64-bit

Bug#1030768: ITP: repro-apk -- scripts to make android apks reproducible

Package: wnpp Severity: wishlist Owner: FC Stegerman X-Debbugs-Cc: debian-devel@lists.debian.org, f...@obfusk.net * Package name: repro-apk Version : 0.2.2 Upstream Contact: FC Stegerman * URL : https://github.com/obfusk/reproducible-apk-tools * License : GPLv

Bug#1030776: ITP: quickjs -- small and embeddable Javascript engine

Package: wnpp Severity: wishlist Owner: Sebastian Humenda X-Debbugs-Cc: debian-devel@lists.debian.org, pkg-a11y-de...@alioth-lists.debian.net, shume...@gmx.de * Package name: quickjs Version : 2021.03.27 Upstream Contact: Fabrice Bellard, Charlie Gordon * URL : https:

Bug#1030780: Maintainers wanted for softether-vpn

Package: wnpp Severity: normal X-Debbugs-Cc: debian-devel@lists.debian.org Hi all, I packaged SoftEther VPN back in 2020 when people in Belarus protested against decades of dictatorship, and they needed a safe way to communicate with the outside world and with each other, circumventing the stat

Bug#1030794: ITP: libcatmandu-oai-perl -- modules for working with OAI repositories within the Catmandu framework

Package: wnpp Owner: Mason James Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libcatmandu-oai-perl Version : 0.19 Upstream Author : Nicolas Steenlant * URL : https://metacpan.org/release/Catmandu-OAI * Li

Bug#1030800: ITP: liblido-xml-perl -- Lido XML parser and writer

Package: wnpp Owner: Mason James Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: liblido-xml-perl Version : 0.07 Upstream Author : Patrick Hochstenbach * URL : https://metacpan.org/release/Lido-XML * License

-ffile-prefix-map option and reproducibility

Hi, When building packages, a -ffile-prefix-map option is automatically injected into CFLAGS. Where does it come from? Since when? I suspect this was added to improve reproducibility. Ironically, it makes packages that capture this variable non reproducible, since the build path seems to be

Bug#1030803: ITP: mdns-reflector -- lightweight and performant multicast DNS (mDNS) reflector

Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: mdns-reflector Version : 0.0.1+ Upstream Author : Yuxiang Zhu * URL : https://github.com/vfreex/mdns-reflector * License : GPL-3+ Programming Lan

Re: -ffile-prefix-map option and reproducibility

Hi, Quoting Stéphane Glondu (2023-02-07 16:41:47) > When building packages, a -ffile-prefix-map option is automatically injected > into CFLAGS. Where does it come from? Since when? probably due to https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/commit/?id=b60c243ba99b8483202a6f6a814476275204fdf

Re: -ffile-prefix-map option and reproducibility

Hi! On Tue, 2023-02-07 at 16:41:47 +0100, Stéphane Glondu wrote: > When building packages, a -ffile-prefix-map option is automatically injected > into CFLAGS. Where does it come from? Since when? This is coming from dpkg-buildflags (in this case probably indirectly via debhelper). AFAICS it was a

Re: -ffile-prefix-map option and reproducibility

On Tue, Feb 07, 2023 at 04:41:47PM +0100, Stéphane Glondu wrote: > When building packages, a -ffile-prefix-map option is automatically injected > into CFLAGS. Where does it come from? Since when? > > I suspect this was added to improve reproducibility. Ironically, it makes > packages that capture

Re: -ffile-prefix-map option and reproducibility

On 2023-02-07 17:50 +0100, Guillem Jover wrote: > On Tue, 2023-02-07 at 16:41:47 +0100, Stéphane Glondu wrote: >> When building packages, a -ffile-prefix-map option is automatically injected >> into CFLAGS. Where does it come from? Since when? > > This is coming from dpkg-buildflags (in this case

Security (Was: OpenMPI 5.0 to be 32-bit only ?)

Hi Alastair, Thanks for relaying OpenMPI's upstream maintainer's interest in our opinions on maintaining 32 bit support. My humble comments are 1.) 32 bit hardware can be more secure because it's so old it predates back doors known as Intel's Management Engine[1] and AMD's

Bug#1030835: ITP: ruff -- linter for Python, written in Rust

Package: wnpp Severity: wishlist Owner: James Addison X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: ruff Version : 0.0.243 Upstream Contact: Charlie Marsh * URL : https://github.com/charliermarsh/ruff/ * License : MIT Programming Lang: Rust De