Bug#1038980: ITP: guile-avahi -- guile bindings for avahi

2023-06-23 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian X-Debbugs-Cc: debian-devel@lists.debian.org, vagr...@debian.org, l...@gnu.org Severity: wishlist * Package name: guile-avahi Version : 0.4.1 Upstream Contact: l...@gnu.org, guile-avahi-b...@nongnu.org * URL : https

Re: FTBFS on all recent uploads

2023-06-22 Thread Vagrant Cascadian
On 2023-06-22, Boyuan Yang wrote: > 在 2023-06-20星期二的 06:31 +0200,Joachim Zobel写道: >> I have a FTBFS on all uploads after the end of the freeze. Example: >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gap-aclib.html >> >> All these packages had been changed to compat 13. Unfo

Re: Bug#1030785: -ffile-prefix-map option and reproducibility

2023-02-08 Thread Vagrant Cascadian
xfilepath (a.k.a. -ffile-prefix-map) Enabled by default: dpkg (1.20.6) unstable; urgency=medium ... * dpkg-buildflags: Enable reproducible=fixfilepath by default. Thanks to Vagrant Cascadian . See https://lists.debian.org/debian-devel/2020/10/msg00222.html. Closes: #974087 ... -- G

Bug#1025776: O: amavisd-milter -- amavisd-new interface for milter-capable MTAs

2022-12-08 Thread Vagrant Cascadian
Package: wnpp Severity: normal Description: amavisd-new interface for milter-capable MTAs This package provides a milter for amavisd-new that works with Sendmail or Postfix, using the AM.PDP protocol. . Replacing the older amavisd-new-milter program, amavisd-milter makes use of the full funct

Re: Including build metadata in packages

2022-05-07 Thread Vagrant Cascadian
On 2022-02-16, Simon McVittie wrote: > On Sun, 13 Feb 2022 at 14:13:10 -0800, Vagrant Cascadian wrote: >> Obviously, this would interfere with any meaningful reproducible builds >> testing for any package that did something like this. Ideally metadata >> like this about a

Re: Including build metadata in packages

2022-05-07 Thread Vagrant Cascadian
On 2022-02-14, Paul Wise wrote: > On Sun, 2022-02-13 at 14:13 -0800, Vagrant Cascadian wrote: > >> * Split build metadata into a separate file or archive >> >> Some of the debian-installer packages generate tarballs that are not >> .deb files and are included in the

Re: Embedded buildpath via rpath using cmake

2022-04-03 Thread Vagrant Cascadian
On 2022-02-03, Vagrant Cascadian wrote: > Over the last several months, I and others have found quite a few > packages that embed build paths via rpath when building with cmake. I > found myself slowly edging into a mass bug filing, one bug report at a > time... > > I ended u

Including build metadata in packages

2022-02-13 Thread Vagrant Cascadian
A while ago I noticed binutils had some embedded logs in one of it's packages, which included timing information about the test suite runs which will almost certainly have differences between the different builds, even on the exact same machine: https://bugs.debian.org/950585 My proposed patch

Re: Embedded buildpath via rpath using cmake

2022-02-05 Thread Vagrant Cascadian
On 2022-02-04, Simon McVittie wrote: > On Fri, 04 Feb 2022 at 13:07:53 +0800, Paul Wise wrote: >> Vagrant Cascadian wrote: >> > Over the last several months, I and others have found quite a few >> > packages that embed build paths via rpath when building with cmake. >

Re: Embedded buildpath via rpath using cmake

2022-02-05 Thread Vagrant Cascadian
On 2022-02-04, David Prévot wrote: > Le 04/02/2022 à 08:58, Andreas Ronnquist a écrit : >> On Thu, 03 Feb 2022 16:41:21 -0800, >> Vagrant Cascadian wrote: > >>> If you're on the list, would love if you could check if your package >>>

Re: Embedded buildpath via rpath using cmake

2022-02-04 Thread Vagrant Cascadian
On 2022-02-04, Seth Arnold wrote: > On Thu, Feb 03, 2022 at 04:41:21PM -0800, Vagrant Cascadian wrote: >> Over the last several months, I and others have found quite a few >> packages that embed build paths via rpath when building with cmake. I >> found myself slowly edging i

Re: Embedded buildpath via rpath using cmake

2022-02-04 Thread Vagrant Cascadian
On 2022-02-04, Paul Wise wrote: > Vagrant Cascadian wrote: > >> Over the last several months, I and others have found quite a few >> packages that embed build paths via rpath when building with cmake. > > This seems like the sort of thing that will be an ongoing problem,

Embedded buildpath via rpath using cmake

2022-02-03 Thread Vagrant Cascadian
Over the last several months, I and others have found quite a few packages that embed build paths via rpath when building with cmake. I found myself slowly edging into a mass bug filing, one bug report at a time... I ended up submitting a few patches and noting some affected packages: https:/

Re: merged /usr

2021-08-17 Thread Vagrant Cascadian
On 2021-08-17, Holger Levsen wrote: > On Sun, Aug 15, 2021 at 12:16:39AM +0100, Simon McVittie wrote: >> The failure mode we have sometimes seen is packages that were built in >> a merged-/usr chroot not working on a non-merged-/usr system, although >> that's detected by the reproducible-builds inf

Re: Need help with getting a package to build reproducibly on arm*

2021-02-11 Thread Vagrant Cascadian
On 2021-01-08, Vagrant Cascadian wrote: > On 2021-01-08, Vagrant Cascadian wrote: >> On 2021-01-07, Vagrant Cascadian wrote: >>> On 2021-01-07, Michael Biebl wrote: >>>> Am 07.01.21 um 18:24 schrieb Michael Biebl: >>>>> as can be seen at [1], sys

Re: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2021-01-09 Thread Vagrant Cascadian
On 2021-01-09, Lisandro Damián Nicanor Pérez Meyer wrote: > Note: in case we do not agree on this topic this will be the text I'll > send to the > tech-ctte. Thanks for taking the time to draft some text. If we can come closer to agreement on the proposed text, that would probably take a bit of th

Re: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2021-01-09 Thread Vagrant Cascadian
On 2021-01-09, Lisandro Damián Nicanor Pérez Meyer wrote: > Oh, I have sadly forgotten to mention another thing. > > On Sat, 9 Jan 2021 at 15:53, Lisandro Damián Nicanor Pérez Meyer > wrote: >> # __FILE__ is a public, well defined API > > According to: > Adrian Bunks mentions it in > https://bugs.

Re: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2021-01-09 Thread Vagrant Cascadian
On 2021-01-08, Lisandro Damián Nicanor Pérez Meyer wrote: > On Fri, 8 Jan 2021 at 21:15, Lisandro Damián Nicanor Pérez Meyer > wrote: > In fact most of those packages would not be unreproducible if the > environment would be the same as the original build. That includes the > build path. True, th

Re: Need help with getting a package to build reproducibly on arm*

2021-01-08 Thread Vagrant Cascadian
On 2021-01-08, Vagrant Cascadian wrote: > On 2021-01-07, Vagrant Cascadian wrote: >> On 2021-01-07, Michael Biebl wrote: >>> Am 07.01.21 um 18:24 schrieb Michael Biebl: >>>> as can be seen at [1], systemd does not build reproducibly on armhf and >>>> arm

Re: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2021-01-08 Thread Vagrant Cascadian
On 2021-01-08, Lisandro Damián Nicanor Pérez Meyer wrote: > On Fri, 13 Nov 2020 at 17:40, Vagrant Cascadian > wrote: >> >> On 2020-11-13, Sune Vuorela wrote: >> > On 2020-10-27, Vagrant Cascadian wrote: >> >> Though, of course, identifying the exact

Re: Need help with getting a package to build reproducibly on arm*

2021-01-08 Thread Vagrant Cascadian
On 2021-01-07, Vagrant Cascadian wrote: > On 2021-01-07, Michael Biebl wrote: >> Am 07.01.21 um 18:24 schrieb Michael Biebl: >>> as can be seen at [1], systemd does not build reproducibly on armhf and >>> arm64 (while there is no problem on amd64 and i386). >>>

Re: Need help with getting a package to build reproducibly on arm*

2021-01-07 Thread Vagrant Cascadian
On 2021-01-07, Michael Biebl wrote: > Am 07.01.21 um 18:24 schrieb Michael Biebl: >> as can be seen at [1], systemd does not build reproducibly on armhf and >> arm64 (while there is no problem on amd64 and i386). >> >> The problem is, I have no idea what the diffoscope diff [2] means and >> how I

Re: Porter roll call for Debian Bullseye

2020-11-30 Thread Vagrant Cascadian
On 2020-11-20, Graham Inggs wrote: > A friendly reminder about the porter roll call for bullseye. > > On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: >> We are doing a roll call for porters of all release architectures. If >> you are an active porter behind one of the release architectures [1] >

Re: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2020-11-14 Thread Vagrant Cascadian
On 2020-11-14, Sune Vuorela wrote: > On 2020-11-13, Vagrant Cascadian wrote: >> If it could be fixed at the core for QFINDTESTDATA, that would be nicer >> than fixing 20-30 packages individually, though we're not there right >> now. > > Unfortunately, only like 1

Re: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2020-11-13 Thread Vagrant Cascadian
On 2020-11-13, Sune Vuorela wrote: > On 2020-10-27, Vagrant Cascadian wrote: >> Though, of course, identifying the exact reproducibility problem would >> be preferable. One of the common issues is test suites relying on the >> behavior of __FILE__ returning a full path to f

Re: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2020-11-09 Thread Vagrant Cascadian
On 2020-10-27, Vagrant Cascadian wrote: > The dpkg-buildflags feature reproducible=+fixfilepath was added to dpkg > in 2018. ... > The result of enabling this feature by default will be to make several > hundred packages reproducible with varying build-path and reduce the > diff

Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

2020-10-27 Thread Vagrant Cascadian
The dpkg-buildflags feature reproducible=+fixfilepath was added to dpkg in 2018. ## What does this feature do exactly? From the dpkg-buildflags(1) manpage: fixfilepath This setting (disabled by default) adds -ffile-prefix-map=BUILDPATH=. to CFLAGS, CXXFLAGS, OBJCFLAGS,

Re: Co-maintaining some packages

2020-10-11 Thread Vagrant Cascadian
On 2020-10-10, Brett Gilio wrote: > It is Brett Gilio. I pinged you on IRC last evening regarding advice for > joining Debian in helping maintain some packages. Below I have Paul > Wise's response to my inquiry, and was wondering if you would be willing > to sponsor my work on some orphaned package

Bug#950315: ITP: m4api -- access Mini-Box M4-ATX power supplies

2020-01-31 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: m4api Version : 0.3~ Upstream Author : Ken Tossell * URL or Web page : https://github.com/ktossell/m4api * License : LGPL-2.1 Description : access Mini-Box M4-ATX power supplies Utility and

Bug#929095: ITP: scheme-bytestructures -- Structured access to bytevector contents

2019-05-16 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: scheme-bytestructures or guile-bytestructures Version : 1.0.5 Upstream Author : Taylan Ulrich Bayırlı/Kammer * URL or Web page : https://github.com/TaylanUB/scheme-bytestructures/ * License : GPL-3

Bug#929094: ITP: guile-git -- guile bindings for git

2019-05-16 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: guile-git Version : 0.2.0 Upstream Author : Amirouche Boubekki * URL or Web page : https://gitlab.com/guile-git/guile-git/ * License : GPL-3+, LGPL-3+, GFDL-1.3+ (with exceptions), others

Bug#929093: ITP: guile-ssh -- guile bindings to ssh

2019-05-16 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: guile-ssh Version : 0.11.3 Upstream Author : Artyom V. Poptsov * URL or Web page : https://github.com/artyom-poptsov/guile-ssh/ * License : GPL-3+, Expat, LGPL-3+, and more! Description

Bug#929092: ITP: guile-sqlite3 -- guile bindings for sqlite3

2019-05-16 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: guile-sqlite3 Version : 0.1.0 Upstream Author : Andy Wingo * URL or Web page : https://notabug.org/guile-sqlite3/guile-sqlite3 * License : LGPL-3+, GPL-3+ Description : guile bindings for

Bug#929091: ITP: guile-gcrypt -- gcrypt bindings for guile

2019-05-16 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: guile-gcrypt Version : 0.1.0 Upstream Author : Christopher Allan Webber and others * URL or Web page : https://notabug.org/cwebber/guile-gcrypt * License : GPL-3+, Expat, GFDL-1.3+ (with exceptions

Bug#928724: ITP: opensbi -- RISC-V Open Source Supervisor Binary Interface

2019-05-09 Thread Vagrant Cascadian
Package: wnpp Severity: wishlist Owner: Vagrant Cascadian X-Debbugs-Cc: debian-devel@lists.debian.org, mer...@debian.org, debian-ri...@lists.debian.org * Package name: opensbi Version : 0.3+ Upstream Author : Anup Patel/Western Digital, other contributors * URL

Re: Nix and non-standard-toplevel-dir

2019-01-20 Thread Vagrant Cascadian
Luke Faraone wrote: > On Wed, 2 Jan 2019 at 20:28, Russ Allbery wrote: > > If anything, they probably already know > > how Nix works and are expecting it to use those paths. There doesn't seem > > to be much drawback in this carefully-chosen lack of compliance with the > > FHS. > > > > I don't th

Bug#895057: RFH: ltsp -- network booted thin and fat clients

2018-04-06 Thread Vagrant Cascadian
Package: wnpp Severity: normal It has been several years since I've actually maintained a real-world deployment of LTSP, and there are very few other active developers of the project upstream. I have continued to maintain it in Debian as best I can, and would love to see it continue to be supporte

Bug#881620: ITP: arm-trusted-firmware -- reference implementation of secure world software for ARMv8-A

2017-11-13 Thread Vagrant Cascadian
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: arm-trusted-firmware Version : 1.4 Upstream Author : ARM Limited and Contributors * URL or Web page : https://github.com/ARM-software/arm-trusted-firmware/ * License : BSD-2-Clause, BSD-3-Clause

Re: Summary of the Arm ports BoF at DC17

2017-09-17 Thread Vagrant Cascadian
On 2017-09-15, Ben Hutchings wrote: > On Thu, 2017-09-14 at 03:40 +0100, Steve McIntyre wrote: > [...] >> There is optional kernel support to trap the exceptions here >> and emulate the instructions, but it's really not recommended for >> serious use (e.g. on a build machine!). > [...] > > Why is i

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-16 Thread Vagrant Cascadian
On 2016-12-16, Roger Shimizu wrote: > On Sat, Dec 10, 2016 at 11:31 PM, Christoph Biedl > wrote: >>> Is it possible to put a bootloader like u-boot in the flash partitions >>> and have it load the Linux kernel and initrd from elsewhere? There's no technical reason this wouldn't be possible, just

Bug#760314: RFH: zoneminder

2014-09-02 Thread Vagrant Cascadian
Package: wnpp Severity: normal Zoneminder maintenance has fallen behind; neither myself nor Peter Howard seem to have enough time to maintain it properly. I no longer use zoneminder at work. Another maintainer, ideally one who actively uses zoneminder, is probably long overdue... Homepage: http:

Re: Arm64 port live on debian-ports

2014-04-20 Thread Vagrant Cascadian
On Sun, Apr 20, 2014 at 04:28:45PM +0100, Ian Campbell wrote: > On Sun, 2014-04-20 at 16:13 +0100, Ben Hutchings wrote: > > Given that, it seems like a good time to add arm64 to src:linux with a > > configuration that will run on at least a typical QEMU ARM64 emulation. > > AIUI qemu 2.0 only does

Bug#646971: ITP: epoptes -- Computer lab management tool

2011-10-28 Thread Vagrant Cascadian
Package: wnpp Severity: wishlist Owner: Vagrant Cascadian * Package name: epoptes Version : 0.3.0 Upstream Author : Alkis Georgopoulos , Fotis Tsamis * URL : http://www.epoptes.org/ * License : GPL Programming Lang: Python, bash Description

Bug#616466: ITP: xul-ext-perspectives -- verify HTTPS sites through notary servers

2011-03-04 Thread Vagrant Cascadian
Package: wnpp Severity: wishlist Owner: Vagrant Cascadian * Package name: xul-ext-perspectives Version : 4.1 Upstream Author : Dan Wendlandt and others * URL : http://www.cs.cmu.edu/~perspectives * License : GPL VCS : git://github.com/danwent

Re: Accepted sdm 0.4.1-2 (source all)

2010-06-26 Thread Vagrant Cascadian
On Sat, Jun 26, 2010 at 02:40:37PM +0100, Julien Cristau wrote: > On Sat, Jun 26, 2010 at 12:57:45 +0000, Vagrant Cascadian wrote: > > > sdm (0.4.1-2) unstable; urgency=low > > . > [...] > >* No longer include dash as a dependency; it is included in essential. >

Bug#543423: ITP: ltsp-docs -- LTSP Documentation

2009-08-24 Thread Vagrant Cascadian
Package: wnpp Severity: wishlist Owner: Vagrant Cascadian * Package name: ltsp-docs Version : 0.99+bzr87 Upstream Author : Scott Balneaves * URL : http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream * License : GPL2 Description : LTSP

BSP October 26th, Portland, Oregon, USA

2008-10-14 Thread Vagrant Cascadian
Freegeek, a Debian GNU/Linux using organization since 2001 or thereabouts, would like to a host a Bug Squashing Party: October 26th, 2008, 10am-whenever Portland, Oregon, USA directions: http://freegeek.org/map please bring your fine bug squashing skills and maybe a potluck dish. plen