Bug#1071466: gpg-from-sq: clear-sign failed: Signing key maps to different keys

Package: gpg-from-sq Version: 0.8.0-5 Severity: normal Dear Maintainer ;) when trying to upload I got this failure: gpg: /tmp/debsign.ctzWuMYi/rust-sequoia-directories_0.1.0-1.dsc: clear-sign failed: Signing key hol...@debian.org maps to 2 different keys:

Bug#1069322: diffoscope crashes when trying to compare unreproducible src:dasel build artifacts

On Tue, May 14, 2024 at 11:43:29AM +0100, Chris Lamb wrote: > Ah, I was hoping that the systemd slice apparatus would be able to > contain any traceback, but now that I think of it, being OOM-killed is > not quite the same as CPython-level crash (and thus traceback). :) > >

Bug#1069322: diffoscope crashes when trying to compare unreproducible src:dasel build artifacts

On Wed, May 08, 2024 at 03:07:00PM +0100, Chris Lamb wrote: > Hm, I can't seem to reproduce the crash with these files. In the first > instance, can you paste a traceback or similar of the crash in > question? Maybe it is fixable just from that without having to find > and upload more files, etc.

Bug#966621: Make /tmp/ a tmpfs and cleanup /var/tmp/ on a timer by default [was: Re: systemd: tmpfiles.d not cleaning /var/tmp by default]

clone 966621 -1 reassign -1 release-notes thanks On Mon, May 06, 2024 at 10:40:00AM +0200, Michael Biebl wrote: > We have two separate issues here: > > a/ /tmp-on-tmpfs > b/ time based clean-up of /tmp and /var/tmp > > I think it makes sense to discuss/handle those separately. very much

Bug#1069934: 4.9.2. The dak ls utility should mention rmadison

control: severity -1 wishlist thanks Hi Bill, On Sat, Apr 27, 2024 at 12:11:21PM +0200, Bill Allombert wrote: > 4.9.2. The dak ls utility > could mention rmadison from devscripts > that does not require to log to ftp-master.debian.org. yes. patches, commits & pushes welcome. -- cheers,

Bug#1069853: pbuilder: add support for '--debootstrap mmdebstrap'

Package: pbuilder Version: 0.231 Severity: wishlist Dear Maintainer, please add support for '--debootstrap mmdebstrap'. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ figures

Bug#1069727: libsequoia-octopus-librnp: Thunderbird integration autopkgtests

On Tue, Apr 23, 2024 at 10:02:13AM -0400, Daniel Kahn Gillmor wrote: > It would be great to have an autopkgtest that confirms that it actually > interoperates with Thunderbird as expected. [...] > Perhaps upstream could help us assemble a comparable test that would run > reliably in

Bug#1069242: official bookworm-backports of rust packages unlikely

control: tags -1 + wontfix hi Jérôme, backports of rust packages at least currently are very unlikely, because one cannot simply backport one package plus one or two libraries maybe, or 5 libraries, but instead one would need to backport src:rust-sequoia-octopus-librnp which would need around

Bug#1069686: libsequoia-octopus-librnp: postinst script Syntax error: "fi" unexpected

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

Bug#1069593: libsequoia-octopus-librnp: dpkg-divert in preinst doesn't happen on upgrade

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...

Bug#1069139: developers-reference: out-of-date section "Make transition packages deborphan compliant"

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

Bug#1069322: diffoscope crashes when trying to compare unreproducible src:dasel build artifacts

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)

Bug#1069139: developers-reference: out-of-date section "Make transition packages deborphan compliant"

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

Bug#1068890: diffoscope: --hard-timeout option

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.

Bug#1069100: libscout.jar has duplicate ZIP entries in the central directory

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

Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

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

Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

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

Bug#877337: single-page html of debian-policy to be revived?

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

Bug#1068890: diffoscope: --hard-timeout option

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

Bug#1068853: reprotest: SyntaxWarning: invalid escape sequence '\;'

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

Bug#1068853: reprotest: 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 '\;'

Bug#1066340: marked as done (t4kcommon: FTBFS: linebreak.c:163:19: error: implicit declaration of function ‘u8_mbtouc_unsafe’ [-Werror=implicit-function-declaration])

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

Bug#1002458: "version in VCS newer than in repository" might be a bit overzealous

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

Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

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 ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁

Bug#872944: #872944 www.debian.org: Remove JavaScript from Policy Manual published on web mirrors

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

Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

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

Bug#1002458: "version in VCS newer than in repository" might be a bit overzealous

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

Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

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: >

Bug#1068761: packaging-tutorial: mention hello and hello-traditional examples

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 $@

Bug#1068760: packaging-tutorial: discourage cdbs and even pure debhelper more

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

Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

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

Bug#1068192: debian-policy: extended forbidden network access to contrib and non-freeo

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

Bug#1068192: debian-policy: extended forbidden network access to contrib and non-free

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

Bug#1041832: #1041832: libsequoia-octopus-librnp: undeclared file conflict with thunderbird

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

Bug#1062904: ping to prevent autoremoval

pong

Bug#1067232: limit diffoscope recursions on packages where diffoscope runs into a timeout

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

Bug#1067232: limit diffoscope recursions on packages where diffoscope runs into a timeout

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

Bug#1067232: limit diffoscope recursions on packages where diffoscope runs into a timeout

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

Bug#1066991: easy way to crash diffoscope

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/ $

Bug#1066121: ionos 5/6/15/16 loosing network

[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

Bug#1066186: setup mastadon2irc bot

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,

Bug#1066122: ionos3 configured twice

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:

Bug#1066121: ionos 5/6/15/16 loosing network

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

Bug#1059479: r-b CI tests very slow

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

Bug#1063376: How to ask efficiently for removal of 32 bit architectures of about 40 packages (Was: reverse dependenc)

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

Bug#1063376: How to ask efficiently for removal of 32 bit architectures of about 40 packages (Was: reverse dependenc)

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,

Bug#1065463: debootstrap can deal with native dpkg file replacement feature

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

Bug#1049716: some analysis

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:

Bug#1032752: please drop transitional package gnupg-agent from src:gnupg2

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.

Bug#1062259: libcomps: NMU diff for 64-bit time_t transition

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

Bug#1063736: snort removal from bullseye (Re: Bug#1063736: RM: snort -- RoQA; security issues, unmaintained)

clone 1063736 -1 reassign -1 debian-security-support retitle -1 document snort situation in bullseye thanks hi, On Sun, Feb 11, 2024 at 09:44:18PM +, Jonathan Wiltshire wrote: > Package: release.debian.org > Severity: normal > Tags: bullseye > User: release.debian@packages.debian.org >

Bug#1063712: check-dfsg-status: integration of monthly cron job with systemd-cron

On Sun, Feb 11, 2024 at 07:39:41PM +0100, Alexandre Detiste wrote: > > > PS: this need a not yet released systemd-cron to actually work. > > any idea when it will be released? > Now, we are both upstream & downstream, it's easy. ok, please ping this bug once it's in trixie. -- cheers,

Bug#1063712: check-dfsg-status: integration of monthly cron job with systemd-cron

On Sun, Feb 11, 2024 at 04:32:58PM +0100, Alexandre Detiste wrote: > Unless #1026287 "use systemd .timer unit instead of /etc/cron.monthly" > got implemented, would it be possible to ship a > tiny 2 lines "old-style-mail.conf" drop-in systemd overide that > overides how systemd-cron will style

Bug#1062259: libcomps: NMU diff for 64-bit time_t transition

On Wed, Feb 07, 2024 at 04:25:17PM +, Luca Boccassi wrote: > Control: tags -1 -pending > Control: close -1 [...] > There are no mentions of 'time_t' in the public headers of this > library. The logs shows that it's a false positive, as the automated > tool simply wasn't able to build it: [...]

Bug#1062983: Developers Reference in A4 instead of US Letter

On Mon, Feb 05, 2024 at 11:00:42AM +0800, Paul Wise wrote: > > I think for English at least I'd prefer to offer both A4 and letter, for eg > > the German translation I think it's enough to only provide A4. > Looks like that info can be gotten from the locales on glibc systems: [...] nice, thanks.

Bug#1062983: Developers Reference in A4 instead of US Letter

hi & thanks for filing this bug report! On Sun, Feb 04, 2024 at 10:57:03AM +0100, Sebastian Geiger (Lanoxx) wrote: > May I request, that: > > a) We switch to A4 as the default format for the developers-reference > since that is the format used by most of the world. > b) We consider offering both

Bug#1062233: Acknowledgement (bookworm-pu: package debian-edu-doc/2.12.23~deb12u1)

On Wed, Jan 31, 2024 at 08:01:15PM +, Holger Levsen wrote: > debdiff no attached. I've also uploaded already. now! (the attachment was in my previous mail to this bug however.) -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).

Bug#1062233: bookworm-pu: package debian-edu-doc/2.12.23~deb12u1

Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu x-debbugs-cc: debian-...@lists.debian.org [ Reason ] Documentation updates for the Debian Edu bookworm manual, translations updates for the Debian Edu bookworm and bullseye

Bug#1061983: bullseye-pu: package debian-security-support/1:11+2024.01.30

-ended.deb11, thanks to Andres Salomon. +Closes: #1061268 + * Add tiles and libspring-java to security-support-limited. Closes: #1057343 + * Drop debian/.gitlab-ci.yml. + + -- Holger Levsen Tue, 30 Jan 2024 17:55:19 +0100 + debian-security-support (1:11+2023.12.11) bullseye; urgency=medium

Bug#1057527: munin: FTBFS with default Java 21

On Tue, Jan 30, 2024 at 11:57:07AM +1300, Vladimir Petko wrote: > Would it be possible to consider a merge request[1] that addresses this > issue? yes, thanks for your patch. I'll upload some time in February... -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁

Bug#1061487: bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1

On Thu, Jan 25, 2024 at 02:39:03PM +0200, Peter Pentchev wrote: > [ Impact ] > Users who upgrade from RPM 4.16.0 or earlier to 4.18.0 cannot use > their database of packages already installed via RPM. IOW, qubes 4.x users: https://github.com/QubesOS/qubes-issues/issues/8482 "Dom0 updates fail

Bug#1061258: rpm: enable read-only BerkeleyDB backend for bookworm?

On Thu, Jan 25, 2024 at 03:36:30PM +0200, Peter Pentchev wrote: > FWIW, I just filed #1061487 with the proposed stable update. awesome. and fwiw, the attached patch there looks sensible to me! ;) -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org

Bug#1061258: rpm: enable read-only BerkeleyDB backend for bookworm?

Hi Peter, On Mon, Jan 22, 2024 at 07:49:53PM +0200, Peter Pentchev wrote: > Yes, I did fully intend to submit it for stable-updates after it had > spent a couple of days in unstable and possibly migrated to > testing. Thanks, though - for all you knew, I had not even > considered it, so thanks

Bug#1061258: rpm: enable read-only BerkeleyDB backend for bookworm?

hi, from reading the d/changelog entry "Enable the read-only BerkeleyDB backend. Closes: #1061258" it sounds like it should be possible to have this fix in bookworm too, via the upcoming point release?! I think it would qualify, as it's breaking updating Qubes dom0 via a debian based update-vm

Bug#1054189: bullseye-pu: package debian-security-support/1:11+2023.10.17

hi! On Fri, Dec 29, 2023 at 03:23:55PM +, Jonathan Wiltshire wrote: > In the past this package has been released early via stable-updates; is > that your intention this time, or can it wait until the next point release > expected in February? after having spent a bit too much time thinking

Bug#1061153: ITP: sigsum-go -- tools for public and transparent logging of signed checksums

Hi Simon, On Fri, Jan 19, 2024 at 05:32:05PM +0100, Simon Josefsson wrote: > * URL : https://git.glasklar.is/sigsum/core/sigsum-go > Description : tools for public and transparent logging of signed > checksums > > The goal of Sigsum is to provide building blocks that can be

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

On Mon, Jan 15, 2024 at 10:46:14AM +, Luca Boccassi wrote: > > huh, if there's a bug in the firmware to accidently store the encryption > > key on the drive in plaintext, it doesn't cost anything extra. > Sure, and if there's a bug in your CPU to accidentally reveal all > kernel secrets to any

Bug#1060367: release.debian.org: RFC: Transitions check for dupload?

On Sun, Jan 14, 2024 at 10:06:44PM +0100, Guillem Jover wrote: > Warning: Source package barnowl is part of ongoing transitions: > > > (I think I'll be adding some generic way to

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

On Sun, Jan 14, 2024 at 08:37:30PM +, Luca Boccassi wrote: > Most definitely wrong. If your threat model is "hardware vendor will > spend hundreds of millions of dollars to get at me" then your cpu > vendor, memory controller vendor, etc etc can do that too, so you > better not use this nor

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

On Thu, Jan 11, 2024 at 07:55:18PM +, Luca Boccassi wrote: > Thank you for the feedback, MR on Salsa is updated as described. <3 -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C

Bug#1059480: r-b CI: some packages are tried several times...

hi, sks is a frequent example of this, it seems: root@jenkins:/var/log/reproducible-builds# ls -lart diffoscope_stamp_sks_* [omitted results in 2023 even...] -rw-r--r-- 1 jenkins jenkins 0 Jan 6 14:42 diffoscope_stamp_sks_bookworm_amd64_1704552146 -rw-r--r-- 1 jenkins jenkins 0 Jan 7 22:22

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

On Thu, Jan 11, 2024 at 11:56:28AM +, Luca Boccassi wrote: [...] > How about if I changed the Description from: > Self-encrypting disk (opal with LUKS2) > to something like: > Firmware-backed self-encrypting disk (vendor-implemented OPAL with > LUKS2) > Would that suffice? If not, do you

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

On Thu, Jan 11, 2024 at 01:47:59AM +, Luca Boccassi wrote: > cryptsetup 2.7.0, currently in experimental, added support for self > encrypting drives using the OPAL functionality as the encryption layer > (managed by the kernel, not by the TCG utilities), both in standalone [...] > I have added

Bug#1059492: r-b CI: drop i386

package: jenkins.debian.org To ease maintenance and to free ressources for testing amd64 and because Debian trixie will probably be released without an i386 kernel (and without d-i too), I'd like to stop doing CI builds for i386. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁

Bug#1059491: r-b CI: drop bullseye

package: jenkins.debian.org To easy maintance, to use fewer ressources and to make individual package pages a bit less confusing, I want to stop testing bookworm. Bookworm test results for individual packages are still visible in each package test history page. -- cheers, Holger

Bug#1059489: r-b CI: run latest diffoscope again

package: jenkins.debian.org Ever since debugging why jenkins.d.n rebooted frequently, we've been doing Debian CI builds using diffoscope from bookworm. We should switch back to using diffoscope from unstable. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁

Bug#1059483: Acknowledgement (r-b CI: oom killer must not kill certain processes)

diffoscope and sshd are other processes which should not be killed. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The road to fascism is lined with people telling you to stop

Bug#1059488: /var/log/mail.log and .../syslog are filling up / sometimes

package: jenkins.debian.org Once every while we are notified like this: Fri Dec 22 11:05:01 UTC 2023 - Warning: too large files found in /var/log: -rw-r- 1 root adm 33G Dec 22 11:05 /var/log/mail.log -rw-r- 1 root adm 33G Dec 22 11:05 /var/log/syslog And then, instead of fixing this

Bug#1059483: r-b CI: oom killer must not kill certain processes

package: jenkins.debian.org Up until this week, we could see several cases of the oom killer gone wild frequently: - postgresql killed and stopped on jenkins - squid being killed and stopped on codethink04 - jenkins, the service, restarted on jenkins This week I've increased swap from 10g to

Bug#1059482: r-b: missing .buildinfo files from bookworm

package: jenkins.debian.org https://tests.reproducible-builds.org/debian/bookworm/amd64/index_no_buildinfos.html lists 45 missing .buildinfo files for bookworm src:bind9 pkgs:1:9.18.19-1~deb12u1 / .buildinfo src:cjose pkgs:0.6.2.1-1+deb12u1 / .buildinfo src:curl pkgs:7.88.1-10+deb12u4 /

Bug#1059481: r-b: missing .buildinfo files from trixie

package: jenkins.debian.org https://tests.reproducible-builds.org/debian/trixie/amd64/index_no_buildinfos.html lists three missing .buildinfo files for trixie: src:lorene pkgs:0.0.0~cvs20161116+dfsg-1 / .buildinfo src:maria pkgs:1.3.5-4.1 / .buildinfo src:ruby-rinku pkgs:1.7.3-2 / .buildinfo

Bug#1059480: r-b CI: some packages are tried several times...

package: jenkins.debian.org Hi, each time before an unreproducible package is compared with diffoscope, a stamp file is created, which is then removed after diffoscope was run. Thus I can see that sometimes a package is tried again and again and again, until its eventually not tried anymore.

Bug#1059479: r-b CI tests very slow

package: jenkins.debian.org Hi, somehow there are far less packages being tested these days then previously: amd64 arm64 armhf i386 packages tested on average per day in the last week 596 3484482 348 packages tested

Bug#926388: status of this bug: #926388 / Stop adding the DebianEdu root CA to NSS shared database

On Mon, Dec 25, 2023 at 01:06:55PM +0100, Guido Berhoerster wrote: > This commit is currently part of a draft MR: > https://salsa.debian.org/debian-edu/debian-edu-config/-/merge_requests/28 > The fix is only applicable for unstable and cannot be backported to bookworm. thanks for the

Bug#926388: status of this bug: #926388 / Stop adding the DebianEdu root CA to NSS shared database

control: tags -1 - pending thanks hi, #926388 "let Firefox trust /etc/ssl/certs/ca-certificates.crt" has been marked as pending with https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/4b63838ab777314d4611195f0be58c29203b8f1a but this commit was never merged into the master branch,

Bug#1056222: bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1

control: forcemerge -1 1057891 control: retitle -1 bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1 thanks Hi, I've just uploaded debian-edu-artwork/2.12.4-1 to unstable and expect that we'd want to at least update in bookworm to this. However I'm not sure which debdiff you'd like to

Bug#1057315: src:tiles added to security-support-limited.(13|12|11|10)

hi, so I'm adding src:tiles to security-support-limited.(13|12|11|10), as no removal is planned (and it's dead upstream etc). -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ If

Bug#1054189: bullseye-pu: package debian-security-support/1:11+2023.10.17

On Thu, Dec 21, 2023 at 08:59:31PM +, Jonathan Wiltshire wrote: > > I've updated this update request for adding 3 more lines to > > security-support-ended.deb11 (and updating d/changelog) > Please go ahead. thanks, uploaded. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁

Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness

control: reopen -1 control: reassign -1 debian-policy control: retitle -1 please stop mentioning urgency=critical thanks On Wed, Dec 13, 2023 at 10:27:20PM +0100, Daniel Gröber wrote: > On Wed, Dec 13, 2023 at 07:24:49PM +0000, Holger Levsen wrote: > > I believe Debian policy should b

Bug#1058589: developers-reference: please mention urgency=critical/emergency for completeness

On Wed, Dec 13, 2023 at 07:04:01PM +0100, Daniel Gröber wrote: > That's fine, but in that case this fact should be documented instead no? > Right now there's confusion across the docs what criticality levels are > available. Britney.conf and d-policy mention critical/emergency but nothing > else

Bug#1054189: bullseye-pu: package debian-security-support/1:11+2023.10.17

control: retitle -1 bullseye-pu: package debian-security-support/1:11+2023.12.11 thanks hi, I've updated this update request for adding 3 more lines to security-support-ended.deb11 (and updating d/changelog) On Wed, Oct 18, 2023 at 04:46:44PM -0300, Santiago Ruano Rincón wrote: > [ Reason ] >

Bug#1057343: Processed: Re: Bug#1057315: tiles: CVE-2023-49735

Hi Salvatore, thanks for your continous work on Debian security! On Sun, Dec 03, 2023 at 08:03:05PM +, Debian Bug Tracking System wrote: > > clone -1 -2 -3 > Bug #1057315 [src:tiles] tiles: CVE-2023-49735 > Bug 1057315 cloned as bugs 1057342-1057343 > > retitle -2 tiles: Add

Bug#1057314: check-dfsg-status: package rename broke "reasons" functionality

On Sun, Dec 03, 2023 at 08:20:54PM +1100, Dmitry Smirnov wrote: > Rename of the package from "vrms" broke important functionality. > Formerly packages could install "reasons" file to > /usr/share/vrms/reasons/ > but since (redundant) package rename (for non-technical concerns), "reasons"

Bug#1057103: Acknowledgement (bookworm-pu: package debian-edu-doc/2.12.20~deb12u1)

hi, attached is the compressed debdiff. I've also uploaded the package to bookworm in the meantime. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ If nothing saves us from

Bug#1057103: bookworm-pu: package debian-edu-doc/2.12.20~deb12u1

rasilian Portuguese: Fred Maranhão. - Spanish:Eulalio Barbero Espinosa and Francisco Javier Carro Orgeira. . [ Holger Levsen ] * stop sending monthly mails about the bullseye edu manual . debian-edu-doc (2.12.19) unstable; urgency=medium . [ Holger Levsen ] * Update Debian Edu

Bug#1057057: debian-policy: Please make Checksums-Sha1 optional

hi, snapshot.d.o also uses sha1 sums, at least internally, but I'd not surprised if also for external verification. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Reporter:

Bug#1055919: python-ansible-pygments: please make the build reproducible

On Wed, Nov 15, 2023 at 01:31:26PM +, Chris Lamb wrote: > I would be more than willing to conclude that this is an issue in > tests.reproducible-builds.org setup. However, I am actually seeing > these test files when I build locally as well — and my patch > consequently fixes the "problem".

Bug#1055648: debian-edu-config: once trixie development started, remove cruft from pre-pkgsel

Package: debian-edu-config Version: 2.13.x Severity: wishlist Dear Maintainer, the attached patch should be applied once trixie development for Debian Edu has started. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP:

Bug#1055647: debian-edu-config: On main server internal name resolving fails: /etc/resolv.conf is empty

Package: debian-edu-config Version: 2.12.32 Severity: important Dear Maintainer, Wolfgang Schweer wrote: On a main server, internal name resolving fails: /etc/resolv.conf is empty. Reason is a wrong /etc/network/interfaces file, generated during installation. In case the LTSP-server profile is

Bug#1055534: sq-wot should stay a bit longer

hi, in https://gitlab.com/sequoia-pgp/sequoia-wot/-/issues/50 Neal H. Walfield wrote 5 days ago: begin quote I think that long term, we should drop sq-wot, the CLI. Right now, it has one advance over the sq CLI: it implements gpg's trust model (--gpg-ownertrust). It's unclear whether

  1   2   3   4   5   6   7   8   9   10   >