On Mon, Apr 22, 2024 at 02:41:44PM -0400, Daniel Kahn Gillmor wrote:
> /var/lib/dpkg/tmp.ci/preinst: 12: Syntax error: "fi" unexpected (expecting
> "then")
> dpkg: error processing archive
> /tmp/apt-dpkg-install-aFNmwO/1-libsequoia-octopus-librnp_1.8.1-3_amd64.deb
> (--unpack):
> new
On Mon, Apr 22, 2024 at 02:41:44PM -0400, Daniel Kahn Gillmor wrote:
> /var/lib/dpkg/tmp.ci/preinst: 12: Syntax error: "fi" unexpected (expecting
> "then")
> dpkg: error processing archive
> /tmp/apt-dpkg-install-aFNmwO/1-libsequoia-octopus-librnp_1.8.1-3_amd64.deb
> (--unpack):
> new
hi dkg,
thanks for these bugreports! I've commited fixes and am doing test
builds now and will upload shortly.
On Sun, Apr 21, 2024 at 04:29:10AM -0400, Daniel Kahn Gillmor wrote:
> Why does the package exclude the diversion when preinst runs on upgrade?
I guess because I used a bad example...
On Sat, Apr 20, 2024 at 08:30:52PM +0200, Guillem Jover wrote:
> While I fully support properly marking obsolete packages by putting
> them in the (unfortunately misnamed :) oldlibs section (well excluding
> library-like depended on packages that get dropped as a mater of course).
> I wanted to
On Sat, Apr 20, 2024 at 08:30:52PM +0200, Guillem Jover wrote:
> While I fully support properly marking obsolete packages by putting
> them in the (unfortunately misnamed :) oldlibs section (well excluding
> library-like depended on packages that get dropped as a mater of course).
> I wanted to
Package: diffoscope
Version: 264
Severity: normal
X-Debbugs-Cc: team+pkg...@tracker.debian.org
Dear Maintainer,
diffoscope crashes when comparing the build results of src:dasel. To make it
more fun, src:dasel is only unreproducible on i386 (out of our four tested
archs, amd64/i386/arm64/armhf)
Package: diffoscope
Version: 264
Severity: normal
X-Debbugs-Cc: team+pkg...@tracker.debian.org
Dear Maintainer,
diffoscope crashes when comparing the build results of src:dasel. To make it
more fun, src:dasel is only unreproducible on i386 (out of our four tested
archs, amd64/i386/arm64/armhf)
Hi Vincent,
On Wed, Apr 17, 2024 at 04:24:16AM +0200, Vincent Lefevre wrote:
> Now that the deborphan package has been removed from unstable,
> the section "Make transition packages deborphan compliant" in
> "Best Packaging Practices" is out of date and should be updated.
>
> See
Hi Vincent,
On Wed, Apr 17, 2024 at 04:24:16AM +0200, Vincent Lefevre wrote:
> Now that the deborphan package has been removed from unstable,
> the section "Make transition packages deborphan compliant" in
> "Best Packaging Practices" is out of date and should be updated.
>
> See
On Tue, Apr 16, 2024 at 04:51:09PM +0100, Chris Lamb wrote:
> Just to say that I am totally on board with the idea of ensuring we
> get _something_ out of diffoscope on tests.reproducible-builds.org.
:) great!
> Way better than 250 timeouts.
On Tue, Apr 16, 2024 at 04:51:09PM +0100, Chris Lamb wrote:
> Just to say that I am totally on board with the idea of ensuring we
> get _something_ out of diffoscope on tests.reproducible-builds.org.
:) great!
> Way better than 250 timeouts.
hi,
I was told by formorer that there will be announcement about this change
later today, as well as an update to the documentation.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
hi,
I was told by formorer that there will be announcement about this change
later today, as well as an update to the documentation.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
Package: libscout
Version: 2.3.2-3
Severity: normal
X-Debbugs-Cc: reproducible-bui...@alioth-lists.debian.net, Fay Stegerman
Dear Maintainer,
a few days ago I filed "#1068705: diffoscope crashes on libscout 2.3.2-3 build
on unstable but not bullseye" which then led Fay Stegerman to discover
Package: libscout
Version: 2.3.2-3
Severity: normal
X-Debbugs-Cc: reproducible-builds@alioth-lists.debian.net, Fay Stegerman
Dear Maintainer,
a few days ago I filed "#1068705: diffoscope crashes on libscout 2.3.2-3 build
on unstable but not bullseye" which then led Fay Stegerman to discover
On Mon, Apr 15, 2024 at 03:00:42PM +0200, Fay Stegerman wrote:
> > (thanks again!), am I correct to assume that thus there's no need
> > to file a seperate bug against libscout?
> It's generating a broken ZIP file with duplicate entries. It really shouldn't
> be doing that, regardless of whether
On Mon, Apr 15, 2024 at 03:00:42PM +0200, Fay Stegerman wrote:
> > (thanks again!), am I correct to assume that thus there's no need
> > to file a seperate bug against libscout?
> It's generating a broken ZIP file with duplicate entries. It really shouldn't
> be doing that, regardless of whether
On Tue, Apr 16, 2024 at 02:09:21AM -0400, Boyuan Yang wrote:
> [...] Can I expect
> the homepage and the Packages page to be updated soon?
sooner if you provide patches.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP:
Hi again,
I've got two remaining questions about libscout (and diffoscope)
On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> unzip does seem to extract all the files, though it errors out. Not sure what
> diffoscope should do here. This is definitely a broken ZIP file. That bug
Hi again,
I've got two remaining questions about libscout (and diffoscope)
On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> unzip does seem to extract all the files, though it errors out. Not sure what
> diffoscope should do here. This is definitely a broken ZIP file. That bug
On Sun, Apr 14, 2024 at 08:43:51PM +0800, Sean Whitton wrote:
> ... but if dev-ref is already shipping both, maybe singlepage is indeed
> usable these days ...
I think it is.
> > Could the Policy Editors team check, if everything is fine now, and if
> > this should be published again?
> > At
On Sun, Apr 14, 2024 at 08:43:51PM +0800, Sean Whitton wrote:
> ... but if dev-ref is already shipping both, maybe singlepage is indeed
> usable these days ...
I think it is.
> > Could the Policy Editors team check, if everything is fine now, and if
> > this should be published again?
> > At
On Sun, Apr 14, 2024 at 08:43:51PM +0800, Sean Whitton wrote:
> ... but if dev-ref is already shipping both, maybe singlepage is indeed
> usable these days ...
I think it is.
> > Could the Policy Editors team check, if everything is fine now, and if
> > this should be published again?
> > At
Package: diffoscope
Version: 264
Severity: wishlist
Dear Maintainer,
currenlty diffoscope has a --timeout option
--timeout SECONDS
Best-effort attempt at a global timeout in seconds. If enabled,
diffoscope will not recurse into any further sub-archives
after
Package: diffoscope
Version: 264
Severity: wishlist
Dear Maintainer,
currenlty diffoscope has a --timeout option
--timeout SECONDS
Best-effort attempt at a global timeout in seconds. If enabled,
diffoscope will not recurse into any further sub-archives
after
On Fri, Apr 12, 2024 at 10:29:07AM -0700, Vagrant Cascadian wrote:
> How exactly did you get this error?
upgrading my sid schroot. just confirmed the bug by removing it there
and installing it again. then I mounted /proc but the bug is still
there. /dev is also populated, though /usr/bin/mount
On Fri, Apr 12, 2024 at 10:29:07AM -0700, Vagrant Cascadian wrote:
> How exactly did you get this error?
upgrading my sid schroot. just confirmed the bug by removing it there
and installing it again. then I mounted /proc but the bug is still
there. /dev is also populated, though /usr/bin/mount
On Fri, Apr 12, 2024 at 09:53:29AM +0100, Jonathan Dowland wrote:
> On Tue Apr 9, 2024 at 7:37 PM BST, Holger Levsen wrote:
[...]
> I agree with everything you say here!
:)
> Wrt git-buildpackage, I'd like to add that personally, I respect the gbp
> authors and maintainers and it's a
Package: reprotest
Version: 0.7.27
Severity: important
Dear Maintainer,
when installing reprotest 0.7.27:
SyntaxWarning: invalid escape sequence '\;'
Setting up reprotest (0.7.27) ...
/usr/lib/python3/dist-packages/reprotest/__init__.py:360: SyntaxWarning:
invalid escape sequence '\;'
Package: reprotest
Version: 0.7.27
Severity: important
Dear Maintainer,
when installing reprotest 0.7.27:
SyntaxWarning: invalid escape sequence '\;'
Setting up reprotest (0.7.27) ...
/usr/lib/python3/dist-packages/reprotest/__init__.py:360: SyntaxWarning:
invalid escape sequence '\;'
Dear Chris et al,
On Thu, Apr 11, 2024 at 07:52:39PM +0100, Chris Lamb wrote:
> > Please review the draft for March's Reproducible Builds report:
> This has now been published — thanks to all who contributed.
great, thank you and everyone involved indeed!
I also like the final order of the
Dear Chris,
On Thu, Apr 11, 2024 at 05:51:05PM +, Debian Bug Tracking System wrote:
> Date: Thu, 11 Apr 2024 17:50:02 +
> From: Debian FTP Masters
> To: 1066340-cl...@bugs.debian.org
> Subject: Bug#1066340: fixed in t4kcommon 0.1.1-11.2
> Reply-To: Chris Hofstaedtler
thanks for that
Dear Chris,
On Thu, Apr 11, 2024 at 05:51:05PM +, Debian Bug Tracking System wrote:
> Date: Thu, 11 Apr 2024 17:50:02 +
> From: Debian FTP Masters
> To: 1066340-cl...@bugs.debian.org
> Subject: Bug#1066340: fixed in t4kcommon 0.1.1-11.2
> Reply-To: Chris Hofstaedtler
thanks for that
On Thu, Apr 11, 2024 at 03:02:05PM +0200, Christoph Berg wrote:
> > additionally you could also only classify d/changelog changing commits
> > with "Gbp-Dch: ignore" in them as such, but I'd guess Marc's suggestion
> > really is good enough.
> I don't understand, if debian/changelog-only commits
On Thu, Apr 11, 2024 at 03:02:05PM +0200, Christoph Berg wrote:
> > additionally you could also only classify d/changelog changing commits
> > with "Gbp-Dch: ignore" in them as such, but I'd guess Marc's suggestion
> > really is good enough.
> I don't understand, if debian/changelog-only commits
On Thu, Apr 11, 2024 at 11:28:19AM +0100, Chris Lamb wrote:
[...]
> Applied in Git with attribution taken from your email.
[...]
> Fixed as well. And it adds a nice comment displaying the issue.
awesome, thank you both!
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
On Thu, Apr 11, 2024 at 11:28:19AM +0100, Chris Lamb wrote:
[...]
> Applied in Git with attribution taken from your email.
[...]
> Fixed as well. And it adds a nice comment displaying the issue.
awesome, thank you both!
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
On Thu, Apr 11, 2024 at 09:18:06AM +0200, Thomas Lange wrote:
> A single page html may be an additional option but there's already the
> single page txt version and the PDF. That's sufficient and I see no
> need in providing more formats of this manual.
>
> Therefore we can close this and I will
On Thu, Apr 11, 2024 at 09:18:06AM +0200, Thomas Lange wrote:
> A single page html may be an additional option but there's already the
> single page txt version and the PDF. That's sufficient and I see no
> need in providing more formats of this manual.
>
> Therefore we can close this and I will
On Thu, Apr 11, 2024 at 09:18:06AM +0200, Thomas Lange wrote:
> A single page html may be an additional option but there's already the
> single page txt version and the PDF. That's sufficient and I see no
> need in providing more formats of this manual.
>
> Therefore we can close this and I will
On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> Salsa is probably better for figuring out what to do next, but I get these
> mails
> too :)
:)
> The libscout.jar has duplicate ZIP entries in the central directory, pointing
> to
> the same actual entry in the ZIP. So the
On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> Salsa is probably better for figuring out what to do next, but I get these
> mails
> too :)
:)
> The libscout.jar has duplicate ZIP entries in the central directory, pointing
> to
> the same actual entry in the ZIP. So the
On Fri, Dec 24, 2021 at 01:36:35PM +0100, Marc Haber wrote:
> On Fri, Dec 24, 2021 at 01:15:08PM +0100, Christoph Berg wrote:
> > Re: Marc Haber
> > > To fill my idea, vcswatch would need to classify commits into "real"
> > > commits and "housekeeping" commits, so that the tracker can handle them
On Fri, Dec 24, 2021 at 01:36:35PM +0100, Marc Haber wrote:
> On Fri, Dec 24, 2021 at 01:15:08PM +0100, Christoph Berg wrote:
> > Re: Marc Haber
> > > To fill my idea, vcswatch would need to classify commits into "real"
> > > commits and "housekeeping" commits, so that the tracker can handle them
On Wed, Apr 10, 2024 at 06:12:21PM +0100, Chris Lamb wrote:
> Holger Levsen wrote:
>
> > when building libscout 2.3.2-3 on current unstable, the result is also
> > unreproducible, but diffoscope crashes when analysing the diff.
> I think this is somewhat related to:
>
On Wed, Apr 10, 2024 at 06:12:21PM +0100, Chris Lamb wrote:
> Holger Levsen wrote:
>
> > when building libscout 2.3.2-3 on current unstable, the result is also
> > unreproducible, but diffoscope crashes when analysing the diff.
> I think this is somewhat related to:
>
On Wed, Apr 10, 2024 at 10:02:56AM -0400, David A. Wheeler via rb-general wrote:
> I agree, this one is HUGE news. There's been a lot of awesome work related to
> reproducible builds, but "minimal container userland is a 100% reproducible
> build in a real-world widely-used distro" is a big step
Package: packaging-tutorial
Version: 0.30
Severity: normal
Dear Lucas,
it would be great if the hello pkg would be mentioned, because its a clean
example
and because there's hello-traditional too.
hello is a good example for using dh in d/rules:
#!/usr/bin/make -f
%:
dh $@
Package: packaging-tutorial
Version: 0.30
Severity: normal
Dear Lucas,
packaging-tutorial is great, but please discourage the use of cdbs and even
pure
debhelper more and emphasize to use dh which is great and simple.
& many thanks for packaging-tutorial!
--
cheers,
Holger
hi,
just adding some random data points to this thread:
- I love git.
- I very much dislike git-buildpackage, too much magic. I try to avoid it
where I can.
- I like salsa. (though I think for many new contributors this is rather
a barrier "why not use github" directly. Also salsa is Debian
package: diffoscope
version: 263
hi,
diffoscope 263 crashes on libscout 2.3.2-3 build on unstable but not bullseye:
libscout 2.3.2-3 is part of bullseye (but neither bookworm nor trixie) and
builds unreproducible there and diffoscope is able to show a diff.
when building libscout 2.3.2-3 on
package: diffoscope
version: 263
hi,
diffoscope 263 crashes on libscout 2.3.2-3 build on unstable but not bullseye:
libscout 2.3.2-3 is part of bullseye (but neither bookworm nor trixie) and
builds unreproducible there and diffoscope is able to show a diff.
when building libscout 2.3.2-3 on
On Tue, Mar 12, 2024 at 08:45:03AM -0700, Vagrant Cascadian wrote:
> >> Note: I confused myself when writing this; in fact Salsa-CI reprotest
> >> _does_
> >> continue to test build-path variance, at least until we decide otherwise.
> > this is in fact a bug and should be fixed with the next
The (translated) debian-edu-bookworm manual in PDF, ePUB or HTML formats are
available at https://jenkins.debian.net/userContent/debian-edu-doc//
To understand this mail better, please read
/usr/share/doc/debian-edu-doc/README.
This mail is automatically send by a cronjob run by Holger Levsen
On Fri, Apr 05, 2024 at 09:49:58PM +0200, Aurelien Jarno wrote:
> If we go that route, here is a proposed alternative patch:
>
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -338,7 +338,8 @@
> For example, the build target should pass ``--disable-silent-rules``
> to any
On Fri, Apr 05, 2024 at 09:49:58PM +0200, Aurelien Jarno wrote:
> If we go that route, here is a proposed alternative patch:
>
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -338,7 +338,8 @@
> For example, the build target should pass ``--disable-silent-rules``
> to any
On Wed, Apr 03, 2024 at 10:58:37PM +0200, Aurelien Jarno wrote:
> Thanks Philipp. Following that result, please find a patch proposal:
>
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -338,9 +338,9 @@
> For example, the build target should pass ``--disable-silent-rules``
> to
On Wed, Apr 03, 2024 at 10:58:37PM +0200, Aurelien Jarno wrote:
> Thanks Philipp. Following that result, please find a patch proposal:
>
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -338,9 +338,9 @@
> For example, the build target should pass ``--disable-silent-rules``
> to
On Fri, Apr 05, 2024 at 12:26:03PM +0200, Andreas Tille wrote:
> > also: (NMU-)uploads to DELAYED/15 are great.
> Sorry, I do not feel my time well spent on just curing a symptom
> (unfixed RC bug) via NMU instead of addressing the underlying cause
> that the package is maintained by a single
On Thu, Apr 04, 2024 at 02:32:45PM +0200, Andreas Tille wrote:
> [...] I could follow the normal NMU procedure but I do not consider
> this a sustainable solution.
[...]
> I did not uploaded my work but I would like to know what action is
> considered acceptable by the voters. I repeat that
On Thu, Apr 04, 2024 at 02:59:34PM +0200, Andreas Tille wrote:
> I would like to learn what options I have to realise paragraph
>Packaging standards
> of my platform.
I also think this feels a bit like abusing the election audience for a
topic which should be discussed on -devel outside
On Thu, Apr 04, 2024 at 01:32:11PM +0200, Marc Haber wrote:
> So you have dedicated packet filters on every machine you run, even if
> sshd is the only network-facing service?
on most machines and it was as simple as doing:
apt install ufw
ufw allow ssh
ufw enable
voila, done. rules configured
Dear Justin,
On Sun, Mar 24, 2024 at 05:10:02PM +, Justin B Rye wrote:
> Okay! Suggested version attached.
<3 thank you very much for that lovely & caring review! I love all your
changes and will upload shortly! 珞
> > Description: Sequoia's reimplementation of the GnuPG cli tools
not subscribed to this
list.)
Source: rust-sequoia-chameleon-gnupg
Maintainer: Debian Rust Maintainers
Uploaders:
Alexander Kjäll ,
Holger Levsen
Vcs-Git: https://salsa.debian.org/rust-team/debcargo-conf.git
[src/sequoia-chameleon-gnupg]
Vcs-Browser:
https://salsa.debian.org/rust-team
hi,
< h01ger> helmut: re: #1041832: i just could not reproduce this bug, see
https://paste.debian.net/1311659/ - though we "didnt change
anything" in sequoia-octopus, so what am i missing? :)
that paste had basically this content:
± dpkg -L libsequoia-octopus-librnp |grep
hi,
< h01ger> helmut: re: #1041832: i just could not reproduce this bug, see
https://paste.debian.net/1311659/ - though we "didnt change
anything" in sequoia-octopus, so what am i missing? :)
that paste had basically this content:
± dpkg -L libsequoia-octopus-librnp |grep
On Thu, Mar 21, 2024 at 10:47:21AM +, Ian Jackson wrote:
> Ian Jackson writes ("Re: Package marked for autoremoval due to closed bug?
> [and 1 more messages]"):
> > Steve, could you please do this for *all* the time_t transition RC
> > bugs?
> IMO things are currently ON FIRE.
I'd rather
pong
pong
On Wed, Mar 20, 2024 at 04:31:22PM +, James Addison wrote:
> > or maybe even simpler: first run diffoscope normally, then if that runs
> > into a timeout,
> > run with --max-container-depth=3 (or 5).
It also occured to me that we then could diffoscope with a (way) lower timeout,
eg 60min
On Wed, Mar 20, 2024 at 04:31:22PM +, James Addison wrote:
> Package: jenkins.debian.org
> X-Debbugs-Cc: hol...@layer-acht.org
no need for that cc:, i'm subscribed to the package.
> That seems like a straightforward way to get started, and without adding much
> complexity.
indeed.
> In
package: jenkins.debian.org
severity: wishlist
hi,
in https://salsa.debian.org/qa/jenkins.debian.net/-/merge_requests/163
James Addison suggested to use --max-container-depth=3 (or 5) for
when diffscope runs into a timeout on a package. (or rather not then,
but always, which why this MR wasnt
PGP SIGNATURE-
Holger Levsen (via nm.debian.org)
For details and to comment, visit https://nm.debian.org/process/1257/
--
https://nm.debian.org/process/1257/
package: diffoscope
version: 240
hi,
crashing diffoscope in under 2min (the package build takes 42sec here).
$ apt source golang-github-stvp-tempredis
$ sudo pbuilder build golang-github-stvp-tempredis_0.0~git20231107.8a695b6-1.dsc
$ mkdir p1 ; mv /var/cache/pbuilder/unstable/result/* p1/
$
package: diffoscope
version: 240
hi,
crashing diffoscope in under 2min (the package build takes 42sec here).
$ apt source golang-github-stvp-tempredis
$ sudo pbuilder build golang-github-stvp-tempredis_0.0~git20231107.8a695b6-1.dsc
$ mkdir p1 ; mv /var/cache/pbuilder/unstable/result/* p1/
$
hi,
from irc:
kpcyrd: may i quote on rb-general what you wrote here?
[11:56] < h01ger> kpcyrd: many thanks for your arch linux status
update! i just wonder: does archlinux re-build in the same path as the original
build or not? :)
[11:59] < kpcyrd> | h01ger: yes, the build path always
[22:39] * | h01ger filed a bug about 5/6/15/16 loosing network now
[22:40] * | mapreri ponders the accuracy: the link was still up, so perhaps it
only lost the IP somehow?
[22:40] next time I will look up the dhcp lease if there is anything
odd
[22:40] mapreri: that pondering could be the
package: jenkins.debian.org
not strictly a jenkins.d.o topic, but it would be nice to have mastadon
mentions on #reproducible-builds again in that channel.
https://github.com/hackspace-marburg/troet
is a Mastodon plugin for Sopel IRC bots, sopel is available in Debian.
--
cheers,
package: jenkins.debian.org
some cleanup needs to be done here, we dont need two hosts.
also twitter is dead, so maybe not even one.
though maybe we wanted a mastadon bot?
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP:
package: jenkins.debian.org
(this has been ongoing for month already)
< h01ger> mapreri: i think we need to put restarting network into some sort of
'cronjob' (probably only if network is down), ionos5 is been gone since several
hours and thus half the amd64 builders are down now
< h01ger> not
On Tue, Dec 26, 2023 at 05:50:47PM +, Holger Levsen wrote:
> packages tested on average per day in the last week 596 3484482
> 348
> packages tested on average per day in the last 4 weeks774 4351
> 546 339
> packages tested on average per da
On Mon, Mar 11, 2024 at 06:24:22PM +, James Addison via rb-general wrote:
> Please find below a draft of the message I'll send to each affected bugreport.
looks good to me, thank you for doing this!
> Note: I confused myself when writing this; in fact Salsa-CI reprotest _does_
> continue to
On Mon, Mar 11, 2024 at 08:26:40PM +, Holger Levsen wrote:
> do mutt -s "RM: remove $package" -i tmpfile $package
the 2nd $package in that line must be sub...@bugs.debian.org
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|la
On Mon, Mar 11, 2024 at 09:12:30PM +0100, Andreas Tille wrote:
> I hope there is some better solution than sending single bug reports
> for those packages. If ftpmaster tooling really needs single bug
> reports I wonder how I can automatically create such bug reports with
> always the same text,
On Mon, Mar 11, 2024 at 08:26:40PM +, Holger Levsen wrote:
> do mutt -s "RM: remove $package" -i tmpfile $package
the 2nd $package in that line must be sub...@bugs.debian.org
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|la
On Mon, Mar 11, 2024 at 09:12:30PM +0100, Andreas Tille wrote:
> I hope there is some better solution than sending single bug reports
> for those packages. If ftpmaster tooling really needs single bug
> reports I wonder how I can automatically create such bug reports with
> always the same text,
On Tue, Mar 05, 2024 at 11:51:16PM +, Richard Purdie wrote:
> FWIW Yocto Project is a strong believer in build reproducibiity
> independent of build path and we've been quietly chipping away at those
> issues.
[...]
> OpenEmbedded-Core (around 1000 pieces of software) is 100% reproducible
>
On Tue, Mar 05, 2024 at 08:36:59AM +0800, Steven Shiau wrote:
> debootstrap should be able to solve the libuuid1t64 dependency by installing
> libuuid1 only.
just in case you are not aware, bootstrapping using either mmdebstrap or
cdebootstrap works atm. mmdebstrap is faster and mostly a drop-in
On Tue, Mar 05, 2024 at 08:36:59AM +0800, Steven Shiau wrote:
> debootstrap should be able to solve the libuuid1t64 dependency by installing
> libuuid1 only.
just in case you are not aware, bootstrapping using either mmdebstrap or
cdebootstrap works atm. mmdebstrap is faster and mostly a drop-in
On Mon, Mar 04, 2024 at 11:52:07AM -0800, John Gilmore wrote:
> Why would these become "wishlist" bugs as opposed to actual reproducibility
> bugs
> that deserve fixing, just because one server at Debian no longer invokes this
> bug because it always uses the same build directory?
because it's
On Mon, Mar 04, 2024 at 07:47:08AM -, Sune Vuorela wrote:
> In theory. I don't know if there are any statistics on 'popular'
> 3rdparty repositories and their keys.
I suspect src:extrepo-data is a good starting point for anyone interested
in generating such statistics...
--
cheers,
The (translated) debian-edu-bookworm manual in PDF, ePUB or HTML formats are
available at https://jenkins.debian.net/userContent/debian-edu-doc//
To understand this mail better, please read
/usr/share/doc/debian-edu-doc/README.
This mail is automatically send by a cronjob run by Holger Levsen
hi,
after *one* build I see:
$ git status
On branch master
Your branch is up to date with 'origin/master'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified:
hi,
after *one* build I see:
$ git status
On branch master
Your branch is up to date with 'origin/master'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified:
On Sun, Feb 18, 2024 at 06:32:39PM +0100, Wolfgang Schweer wrote:
> Also, (ro) and (uk) translations seem to be complete:
> debian-edu-bookworm-manual.ro.po: 1038 translated messages.
> debian-edu-bookworm-manual.uk.po: 1038 translated messages.
> New binary packages should be provided.
I've just
On Sat, Feb 17, 2024 at 01:29:54PM +0100, Andreas Metzler wrote:
> Control: block -1 by 1064104 1064105 1064110 1064111 1064112 1064113 1064114
> 1064115 1064116 1064118 1064117 1064119 1064120
> I have submitted bugs against packages in sid with
> Depends/Suggest/Recommends on gnupg-agent.
On Wed, Feb 14, 2024 at 10:31:21AM -0800, Steve Langasek wrote:
> Well, these packages will be garbage collected from experimental upon the
> next upload of a package to unstable or experimental with a higher version;
which might happen next month or next year or in 2027...
> so this is a low
On Wed, Feb 14, 2024 at 10:31:21AM -0800, Steve Langasek wrote:
> Well, these packages will be garbage collected from experimental upon the
> next upload of a package to unstable or experimental with a higher version;
which might happen next month or next year or in 2027...
> so this is a low
On Thu, Feb 15, 2024 at 01:42:35PM +0100, Frank Weißer wrote:
> booting this image tells Debian Edu 12.5, so maybe only the README.txt (as
> README.html too) is the wrong one?
I guess so. Do you get the Edu installer when booting it?
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
On Thu, Feb 15, 2024 at 10:08:11AM +0100, Vincent Lefevre wrote:
> Not for mksh.
so the subject should be "mksh is broken with usrmerge"?
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D
1 - 100 of 22785 matches
Mail list logo
