Bug#1098822: otpclient: otpclient complains about lock memory limits (show_memlock_warning)

On Wed 2025-04-23 12:32:45 -0700, Soren Stoutner wrote: > For the sake of completeness, this value is set by the Linux kernel, > can be reset by systemd, and can also be overwritten by pam for > particular groups using /etc/security/limits.conf, which is shipped in > libpam-modules. In the past

Bug#1103937: dokuwiki: Update/add debconf template translation [INTL:ca]

ve used an older version of the pot file, there's one more thing to update for you at the bottom of the file. Regards, Daniel

Bug#1103938: curl FTCBFS: intentionally broken for cross compilation

On Wed, 23 Apr 2025, Helmut Grohne wrote: curl intentionally broke cross compilation in its last upstream release. This is a ridiculous and incorrect statement. Before curl 8.13.0, the completion scripts would not be produced for cross-compiles because they required *executing* the curl exec

Bug#1103937: dokuwiki: Update/add debconf template translation [INTL:ca]

t the authoritative git repo for dokuwiki anymore, so I'd be glad if you could just send the file to this bug. additionally, having looked at the po file, could you also please remove the unneeded commented "fuzzy" entries (apache2/lighttp) at the bottom? Regards, Daniel

Bug#1103769: dnscap: FTBFS on armel, armhf: test failures

close 1103769 2.3.0-2 thanks Hi, the patch upstream provided to test did indeed fix it, hence closing this bug. thanks for reporting! Regards, Daniel

Bug#1100748: Acknowledgement (segfault when using get_text() on arm64)

> said that since pymupdf is in Bookworm, this would be eligible for an > exception. Bastian, do you want to file the pre-approval bug or would > you like me to take care of it? > > Thanks! > > cheers, josch > > P.S.: currently on vacation and hence sending without PGP s

Bug#1100958: sopv-gpgv: Does not consider RIPEMD160 and SHA-1 as weak digests

Control: reassign 1100958 gpgv Control: retitle 1100958 gpgv does not consider RIPEMD160 and SHA-1 as weak digests Control: found 1100958 2.4.7-15 Control: found 1100958 2.2.46-6 Control: found 1100958 2.2.40-1.1 Hi Guillem-- On Fri 2025-03-21 01:28:40 +0100, Guillem Jover wrote: > On a minimal

Bug#1103719: dhcpcd configured DNS server disappears when using systemd-resolved

cratic and slow, so if we'd want to have a go at this it'd be best to get something together before then. However any DNS breakage easily qualifies for a severity:serious RC bug which we can fix any time before the release as long as the change diff is reasonably small and we can motiva

Bug#1099499: requires pyarrow

On 4/21/25 12:13, Paul Gevers wrote: So they should have never made it to testing. yes. I though filling the RC bug against harlequin right after it left NEW would be enough to never let harlequin-* migrate, seems not. Sorry about the confusion it caused. Regards, Daniel

Bug#1103759: new upstream (8.24.3)

Package: gitleaks Hi, thank you for maintaining gitleaks in Debian. The current version (8.16.0) is rather old (Februar 2023), it would be nice if you could upgrade it to the current one (8.24.3). Regards, Daniel

Bug#886697: RFP: commitizen -- Git command that helps format commit messages correctly

-this-project-affiliated-with-the-commitizen-js-project Regards, Daniel

Bug#1099499: requires pyarrow

intention with their depends to harlequin, so that they in turn also don't make it to testing until apache arrow is in Debian). Regards, Daniel

Bug#1099499: requires pyarrow

tead chose to immediately fill an RC bug to block its migration. That way it is installable in sid and thus easier to test/work with for people until apache arrow is in the archive. If you'd like me to do it different, just let me know. Regards, Daniel

Bug#1017770: rework dpkg-divert handling for newer dpkg

for newer dpkg. Regards, Daniel

Bug#1103448: mdadm: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

retitle 1103448 glibc: [INTL:pt_BR] debconf templates translation reassign 1103448 glibc thanks Hi Adriano, it seems you've accidentally attached the updated debconf translations for glibc instead of mdadm, thus reassigning this bug to glibc. Regards, Daniel

Bug#1099425: dhcpcd: Please disable IPv4LL by default for trixie

block this without explicit admin intervention. > > We'd have to remove that Provides yeah. > > That's already gone. My point mostly was that if we add 'noipv4ll' to > the config Debian ships, we technically no longer support the feature > by default (although i

Bug#1103358: ceph: FTBFS in testing/arm64: c++: fatal error: Killed signal terminated program cc1plus

that with a simpler and more correct variant (where less ram than cpu cores is accounted for).. ..how much cores and ram does the buildd have you've run the build on? if you have less than 4g per core, the build will currently fail. Regards, Daniel

Bug#946879: git: please build package with libsecret credential helper

Hello I'm very interested in this feature too. Is there something I can do to help? Regards -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF signature.asc Description: PGP signature

Bug#1103481: ITP: bincrypter -- compress, encrypt or obfuscate ELF binaries and shell scripts

Package: wnpp Owner: Daniel Echeverri Severity: wishlist * Package name: bincrypter * Version : 1.1 * Upstream Author : skyper * URL or Web page : https://github.com/hackerschoice/bincrypter * License : GPL-2.0+ * Description : compress, encrypt or obfuscate ELF binaries

Bug#1091201: sqv: Consider building with OpenSSL

On Mon 2024-12-23 13:20:44 +0100, Julian Andres Klode wrote: > APT now build with OpenSSL (and sqv), hence sqv is the only thing > left pulling in nettle in the base system. FWIW, i have more confidence in Nettle as a cryptographic backend than i have in OpenSSL. If the project as a whole prefers

Bug#1103358: ceph: FTBFS in testing/arm64: c++: fatal error: Killed signal terminated program cc1plus

at these things can be spottet with less roundtrips directly from the build log. I plan do to that for the 18.2.5 point-release update (which currently FTBFS for other reasons and has two regressions that need fixing over 18.2.4, sigh). Regards, Daniel

Bug#1103417: chatty: Failed to launch app 'Discussions' on Librem5

i libgdk-pixbuf2.0-bin 2.42.12+dfsg-2 ii mmsd-tng 2.6.3-1 pn purple-lurch ii purple-xmpp-carbons 0.2.3-1.1 ii purple-xmpp-http-upload 0.2.4-2.1 Versions of packages chatty suggests: ii gnome-calls 48.1-1 -- no debconf information -- Daniel Dehennin Ré

Bug#1103358: ceph: FTBFS in testing/arm64: c++: fatal error: Killed signal terminated program cc1plus

efore spending lots of time on this and on my rpi5 it build fine, a n>1 failure would be nice). Regards, Daniel

Bug#1101757: unblock: dovecot/1:2.4.1+dfsg1-1

's something for the 'ol MiniDebConf Hamburg TODO list for me to procrastinate on I suppose :-) I'm not sure I'll get to it TBH. If you want anyone to be able to connect to dovecot then networking probably shouldn't be as broken as it is now ;-P (thats my focus). --Daniel signature.asc Description: PGP signature

Bug#1101757: unblock: dovecot/1:2.4.1+dfsg1-1

eady! I was going to file an unblock request but this would be redundant with dovecot 2.4 in trixie. --Daniel signature.asc Description: PGP signature

Bug#1099425: dhcpcd: Please disable IPv4LL by default for trixie

ople with Macs and see if they can test this for us if you like. > I also ponder whether we can claim to offer a suitable substitute for > avahi-autoipd anymore if we disable IPv4LL in dhcpcd's stock > configuration. We'd have to remove that Provides yeah. --Daniel signature.asc Description: PGP signature

Bug#1103308: mlmmj: build failures on non-mainstream arches

; Trixie release. While not the first thing we should try, process wise you can also declare architectures mlmmj doesn't build on as unsupported by asking ftp-master to RM them from the archive. Then the working binaries will migrate just fine. A less than ideal solution, but it's a decision you ultimately get to make as Maintainer. --Daniel signature.asc Description: PGP signature

Bug#1102545: lbdb: eval quoting for $@ still doesn't work - shattering hopes

Hi Roland, On Thu, Apr 10, 2025 at 07:41:44PM +0200, Roland Rosenfeld wrote: > On Thu, 10 Apr 2025, Daniel Gröber wrote: > > I'm trying to use lbdb for Debian work, but I found some of my > > queries are not returning results. > > Could you please be more concrete in

Bug#1102693: src:frr: fails to migrate to testing for too long: FTBFS on s390x

Hi David, On 4/16/25 11:59, David 'equinox' Lamparter wrote: https://github.com/FRRouting/frr/commit/0ede1a830285c3fa3a8424fa69486a217c1e05ce.patch great, thanks! I've just uploaded it as 10.3-2. Regards, Daniel

Bug#1101471: [pkg-gnupg-maint] Bug#1101471: starting of agent for system accounts is inacceptable

On Sun 2025-04-13 15:21:43 +0200, Marc Haber wrote: > On Wed, Apr 09, 2025 at 04:39:14PM -0400, Daniel Kahn Gillmor wrote: >>Marc, what does this command show for you? >> >> gpgconf --list-options gpg-agent | grep ^enable-ssh-agent: > > Nothing. sorry, this should ha

Bug#1103016: incompatibility with gpg causing FTBFS

On Mon 2025-04-14 16:26:07 +0200, René Engelhard wrote: > [ dkg wrote: ] >> To the extent that LibreOffice's OpenPGP integration is all done in Java > > Nope. gpgmepp. Ah, condolences, that is a complex and fiddly mechanism if the only things needed are signing (with known keys)and verification (w

Bug#1103056: Bug#1103016: incompatibility with gpg causing FTBFS

On Mon 2025-04-14 13:53:16 +0200, René Engelhard wrote: > It's still only test keys to test whether signing/verify works, not real > world keys. > > But yeah, they need to be updated, will propose upstream. It's > definitely too late for Trixie though, will try to get it upstream > for forky.

Bug#1103016: incompatibility with gpg causing FTBFS

On Mon 2025-04-14 13:43:20 +0200, Justus Winter wrote: > René Engelhard writes: > >> If you divert /usr/bin/gpg, IMHO you need to behave like gpg. > > gpg doesn't behave like gpg. Just look at all the version-specific > hacks in GPGME if you don't take my word for it. Any code relying on a > spe

Bug#1103037: openssh-client: ssh-agent: Improve systemd user service socket activation

Package: openssh-client Version: 1:10.0p1-1 Severity: normal Tags: patch Since OpenSSH 10.0, ssh-agent now has nice, simple support for systemd-style user service socket activation. The attached patch updates debian's ssh user services to make the agent socket-activated with basically no overhead

Bug#1102621: [pkg-gnupg-maint] Bug#1102621: gpgv-udeb can't be installed: depend on non-udeb libassuan9 and libnpth0t64

On Sat 2025-04-12 08:28:31 +0200, Cyril Brulebois wrote: > Thanks to both of you for the kick turnaround! It looks like gpgv-udeb > 2.4.7-14 has satisfiable dependencies *and* manages to validate mirrors > from within d-i. Great to hear! I appreciate your following up to let us know that the fix

Bug#1100292: Debian packaged Fastcluster fails its test (Was: r-cran-fastcluster: FTBFS: FAIL: test_vector (tests.fastcluster_test.test_vector))

input used to produce an ad hoc result. Since 1.15.0, numeric input is converted to Boolean before computation." I am going to suggest a fix soon. Please stay tuned. Best, Daniel Am 13.04.25 um 8:11 AM schrieb Andreas Tille: Control: tags -1 upstream Control: forwarded -1 Daniel Mülln

Bug#1102621: [pkg-gnupg-maint] Bug#1102621: gpgv-udeb can't be installed: depend on non-udeb libassuan9 and libnpth0t64

unnecessary for gpgv. They appear to have been pulled in from common/sysutils.c when built with pth, which suggests that we just need to link gpgv against a non-pth libcommon. I'll test further and report back. --dkg From 10db0bcdabf13adbbd9ffbb34e3b2b8516455ab3 Mon Sep 17 00:00:0

Bug#1102669: linphone-desktop: segfault in registerFont at startup

Package: linphone-desktop Version: 5.2.6+dfsg-1 Severity: grave I've been using linphone-desktop for years, so i have an existing linphone configuration. When i recently upgraded from 5.0.2-4+b5 to 5.2.6+dfsg-1, linphone declined to start at all with this complaint: ``` 0 dkg@bob:~$ linphone li

Bug#1102621: [pkg-gnupg-maint] Bug#1102621: gpgv-udeb can't be installed: depend on non-udeb libassuan9 and libnpth0t64

On Fri 2025-04-11 08:45:47 +0200, Cyril Brulebois wrote: > The upload of the 2.4.7 series to unstable just broke gpgv-udeb, which > bootstrap-base and net-retriever rely on: > > Depends: libassuan9 (>= 3.0.2), libc6-udeb (>= 2.41), libgcrypt20-udeb > (>= 1.11.0), libgpg-error0-udeb (>= 1.51),

Bug#1057384: openresolv: Please don't change resolv.conf when it's a symlink

12:30:03PM +0100, Daniel Gröber wrote: > On Mon, Dec 04, 2023 at 11:41:57AM +0100, Daniel Gröber wrote: > > This is similar to how networkmanager and systemd-resolvd handle > > ownership conflicts and following this protocol will ensure only one > > (or none in my case :) ma

Bug#1102555: bfh-metapackages (and progress-linux-metapackages) testing migration issues

Hi Adrian, thanks - I'll fix both of them later today and tomorrow. Regards, Daniel

Bug#1102545: lbdb: eval quoting for $@ still doesn't work - shattering hopes

: - eval ${method}_query \""$@"\" >> "$collection" || true + ${method}_query "$@" >> "$collection" || true This seems to fix my problem at least, but I'm not sure passing the $@ args individually is the behaviour you intended? --Dan

Bug#1010868: marked as pending in dovecot-fts-flatcurve

Hi Joseph, I found your WIP packaging for dovecot-fts-flatcurve and was wondering if you're still intending to upload it? I'd like to get this into trixie ASAP before the freeze on the 15th. --Daniel On Fri, May 24, 2024 at 02:58:58AM +, Joseph Nahmias wrote: > Bug #1010868 i

Bug#1101471: [pkg-gnupg-maint] Bug#1101471: starting of agent for system accounts is inacceptable

On Mon 2025-03-31 21:53:41 +0200, Marc Haber wrote: > It is probably enough to have an ssh-agent running on the side of the > ssh client to invoke a gpg agent on the server side? I am not using gpg > in any way here. If we were to remove the systemd sockets, then gpg would auto-launch the daemon

Bug#1100782: rtorrent: Keyboard input doesn't work

severity 1100782 important thanks Hi Balint, not everyone uses rtorrent via tty. XMLRPC is also possible. This issue is at best important severity, i.e. doesn't warrent rtorrent's removal from testing. Lowering accordingly. Hope you can find a fix for the issue. --Daniel On Tue, Ma

Bug#1098822: otpclient: otpclient complains about lock memory limits (show_memlock_warning)

On Sat 2025-03-22 17:06:12 -0700, Soren Stoutner wrote: > There is some information as to why this is important in the upstream > README. > > “Please note that the memlock value should be >= 64 MB. Any value less > than this may cause issues when dealing with tens of tokens > (especially when im

Bug#1100929: debian-security-support: Mark odoo as EOL'ed in bullseye LTS

ning of the month. I couldn't determine the patch that supposedly fixed CVE-2024-12368. IIRC there were multiple thousand commits between main releases. Based on my own observation and FWIW, I would second that proposal. Regards, Daniel

Bug#1101032: dh-make-golang: Why not a 3.0 (native) package?

ht in Salsa? Is there a good reason for keeping it at a distance on GH and as a 3.0 (quilt) package? Thanks, --Daniel signature.asc Description: PGP signature

Bug#1101029: ITP: golang-agwa-go-listener -- library for creating net.Listeners

Package: wnpp Severity: wishlist Owner: Daniel Gröber X-Debbugs-Cc: debian-de...@lists.debian.org, d...@darkboxed.org * Package name: golang-agwa-go-listener Version : 0.6.1 Upstream Contact: Andrew Ayer * URL : https://github.com/AGWA/go-listener * License

Bug#1098822: otpclient: otpclient complains about lock memory limits (show_memlock_warning)

Control: forwarded 1098822 https://github.com/paolostivanin/OTPClient/issues/397 OK, i've forwarded the concern upstream. Thanks, Soren! --dkg signature.asc Description: PGP signature

Bug#1031046: Add asterisk to debian trixie

ast anyway). See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031046 for details. Nobody has yet committed to doing that work and that's why it's not in trixie. --Daniel signature.asc Description: PGP signature

Bug#1090749: Bug#1090749: ITP: bird3 -- Internet Routing Daemon (version 3.x)

On Thu, Apr 03, 2025 at 05:07:20PM +0200, Paul Gevers wrote: > Hi > > On 03-04-2025 12:30, Daniel Gröber wrote: > > So I guess the question was: say we plan on being done by date X-Y which is > > after/during soft freeze. Is there any flexibility on the "no new src pkgs

Bug#1101980: unbound-host: Name is confusing; how about unbound-lookup?

nd-host direcly: https://codesearch.debian.net/search?q=unbound-host&page=1&perpkg=1 Happy to forward this upstream too but I think we should move on this first and before trixie still. --Daniel signature.asc Description: PGP signature

Bug#1090749: Bug#1090749: ITP: bird3 -- Internet Routing Daemon (version 3.x)

Hi Paul, On Thu, Apr 03, 2025 at 12:16:36PM +0200, Paul Gevers wrote: > On 03-04-2025 11:41, Daniel Gröber wrote: > > d-release: It's not clear to me if we can get an exception for bird3 here? > > > I'm not seeing a reason for an exception here. Maybe I missed it

Bug#1090749: Bug#1090749: ITP: bird3 -- Internet Routing Daemon (version 3.x)

e. d-release: It's not clear to me if we can get an exception for bird3 here? I would assume we can't, upload 3.0.2 to unstable *now* and let it migrate then we at least have a head start on the longer migration times come Soft Freeze :-) --Daniel signature.asc Description: PGP signature

Bug#1101842: ITP: racd -- Extensible IPv6 Router Advertisement Client Daemon

On 1 April 2025 22:33:50 CEST, Michael Richardson wrote: >Daniel Gröber wrote: >> I haven't 100% decided on the script interface yet. I'm thinking either >> (binary) files in /run/racd/$IFACE (in raw ICMPv6 option format) with a >> commandline tool

Bug#1101842: ITP: racd -- Extensible IPv6 Router Advertisement Client Daemon

Package: wnpp Severity: wishlist Owner: Daniel Gröber X-Debbugs-Cc: debian-de...@lists.debian.org, debian-i...@lists.debian.org, d...@darkboxed.org Forging ever on along the IPv6-only path. RAcd is a peice of glue intended to allow system components such as src:clatd to interface easily with

Bug#1101876: /bin/ip: disappearing permanent arp entries

in one of those formats. Beware: The files will be public in the Debian BTS. Send it to me directly if you don't like sharing your IP(s) publically. --Daniel signature.asc Description: PGP signature

Bug#1101834: ITP: recent-rgrep -- search recently modified files with grep

Package: wnpp Severity: wishlist Owner: Daniel Gröber X-Debbugs-Cc: debian-de...@lists.debian.org, d...@darkboxed.org * Package name: recent-rgrep Version : 0.1.0 Upstream Contact: Charles Y. Choi * URL : https://github.com/kickingvegas/recent-rgrep * License

Bug#1101366: Bug#1101365: RFH: ifupdown -- high level tools to configure network interfaces

> > I'll try to work on this over the weekend but I don´t promise anything, > if someone wants to step in please do! IMO You shouldn't feel like you have to. I'd just be happy for input on any particularly jucy/difficult bugs, maybe major overall problems you think need addressing and the like. --Daniel signature.asc Description: PGP signature

Bug#1101758: ifupdown-ng: Can't name bridge device "br"

repo — yet ;-). --Daniel On Mon, Mar 31, 2025 at 05:37:01AM -0700, Alex Hermann wrote: > The [ dev ] or [ name ] keywords are only optional if the interface name > does not clash with keywords. An interface named "br" would > cause failures. > > Fixes #256 > You ca

Bug#1101689: ejabberd-contrib: Missing upstream modules

. I'm particularly interested in the mod_prometheus and mod_tombstones modules and would appreciate if ejabberd-contrib would be updated to include all upstream modules again. Regards, Daniel -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 

Bug#1085140: ejabberd does not listen on any port after update to 24.07

On Friday, March 28, 2025 16:37:53 UTC Soren Stoutner wrote: > Fair enough. Has anyone successfully tested an upgrade from 23.10-1? > That broke for me. If it breaks for everyone upgrading from 23.10-1, > then the severity of grave would be justified. If it only breaks for > a subset of upgr

Bug#1098783: bookworm-pu: package fort-validator/1.5.4-1+deb12u1

Am Donnerstag, dem 27.03.2025 um 17:41 +0100 schrieb Daniel Leidert: > Am Samstag, dem 01.03.2025 um 10:57 + schrieb Adam D. Barratt: [..] > > +fort-validator (1.5.4-1+deb12u1) bookworm-security; urgency=medium > > > > That should be "bookworm". I just r

Bug#1098783: bookworm-pu: package fort-validator/1.5.4-1+deb12u1

Hi Adam, thanks for going through the PU. Am Samstag, dem 01.03.2025 um 10:57 + schrieb Adam D. Barratt: > Control: tags -1 + moreinfo > > On Mon, 2025-02-24 at 02:40 +0100, Daniel Leidert wrote: > > There are multiple known CVEs (CVE-2024-45234, CVE-2024-45235, CVE- >

Bug#1101144: bookworm-pu: package xfce4-weather-plugin/0.11.3-1 (-2 for stable)

4-weather-plugin/-/commit/ced862292318d40f7dea4f53e6a00366234e2722 to backport. Do you maintain that is necessary effort over "just" getting the 0.11.3-1 version from stable-backports into stable-p-u (as 0.11.3-1+deb12u1 then)? Kind regards, Daniel

Bug#1101325: nextpnr: New upstream release 0.8

e $@ --device GW1NR-LV9QN88PC6/I5 --family > GW1N-9C --cst tangnano9k.cst > > becomes: > > $(NEXTPNR) --json $< --write $@ --device GW1NR-LV9QN88PC6/I5 --vopt > family=GW1N-9C --vopt cst=tangnano9k.cst Got it: it's incompatible. Thanks for looking. --Daniel signature.asc Description: PGP signature

Bug#1100872: RFS: wireguard-initramfs/2025.03.02-1 [ITP] -- WireGuard initramfs integration

.debian.org/~eriberto/README.package-tests.html. Setting up a "remote" wireguard peer is going to be the biggest challange, but even that can be done relatively easily with ip-netns and perhaps unshare -u to control the time of the other peer if we want to test time sync. --Daniel signature.asc Description: PGP signature

Bug#1101325: nextpnr: New upstream release 0.8

ckage new upstream version" bug if there isn't one already. Actually helps grease the wheels process wise in most cases so you should always do that :-). If my BTS-foo doesn't fail me this mail should open a bugreport. Let's see. > Thanks for your work maintaining the free FPGA toolchain on Debian. <3 --Daniel

Bug#1101323: nextpnr: Upstream started shipping unreviewable *.json.gz files for tests

sions/issue0237/top.json.gz ./ice40/regressions/issue0258/twopll.json.gz ./ice40/regressions/pr0226/top.json.gz ./ice40/regressions/pr0252/top.json.gz --Daniel signature.asc Description: PGP signature

Bug#1100461: [Pkg-electronics-devel] Bug#1100461: ghdl: BD-Uninstallable: gnat-13 vs gnat-14

On Tue, Mar 25, 2025 at 12:12:15AM +0100, Andreas Bombe wrote: > Anyway, I have mostly finished packaging ghdl 5.0.1 which will also use > the current default gnat. There were some problems building with gcc 14 > holding me up, but I think I can just bypass those. NMUing these changes > right now w

Bug#1093255: RFP: beszel -- lightweight server monitoring hub with historical data, docker stats, and alerts

I worked on creating a Debian package for beszel-agent upstream: https://github.com/henrygd/beszel/pull/497. I'm not sure what changes would need to be made to pull this package into the Debian repo (I've never done that before), and unfortunately don't have time to work on it myself. This is

Bug#1101033: dh-make-golang: Please add knownHost mapping for src.agwa.name

tener. Thanks, --Daniel signature.asc Description: PGP signature

Bug#1101011: Comparison run & diff, one of the Debian patches is the culprit

Hi Andreas, Am 22.03.25 um 07:33 schrieb Andreas Metzler: On 2025-03-22 Daniel Lange wrote: [...] @dkg: any idea which of the last patches breaks this code path? [...] freepg/0027-gpg-Fix-newlines-in-Cleartext-Signature-Framework-CS.patch Confirmed. Dropping just this patch makes gpgv

Bug#1101001: chrony: Please cleanup dpkg-statoverrides properly

Control: done -1 Hi Vincent, On Fri, Mar 21, 2025 at 09:47:09PM +0100, Vincent Blut wrote: > Control: tags -1 + moreinfo > > Hi Daniel, > > Le 2025-03-21 16:57, Daniel Gröber a écrit : > > Package: chrony > > Version: 4.6.1-1 > > Severity: normal >

Bug#1101006: ITP: snid -- TLS-SNI proxy with zero config IPv4/v6 translation

Package: wnpp Severity: wishlist Owner: Daniel Gröber X-Debbugs-Cc: debian-de...@lists.debian.org, d...@darkboxed.org Hi d-devel, Continuing on my IPv6-only trajectory, snid is a very convinent program for those brave enough to leave the legacy IP world behind them, or well, at least in a dark

Bug#1101011: Comparison run & diff, one of the Debian patches is the culprit

Good version: $ gpgv --version gpgv (GnuPG) 2.2.40 libgcrypt 1.10.1 Copyright (C) 2022 g10 Code GmbH License GNU GPL-3.0-or-later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. $ LC_ALL=

Bug#1101003: dhcpcd-base: dhcpcd-run-hooks .d dir support would be useful

fine. dhcpcd is collab maintained last I checked being in the debian/ namespace on salsa. Right? I'm planning to work on a number of these issues to get it into shape for trixie and BTS is my TODO list here. --Daniel signature.asc Description: PGP signature

Bug#1101003: dhcpcd-base: dhcpcd-run-hooks .d dir support would be useful

/dhcpcd.enter-hook and /etc/dhcpcd.exit-hook exist. However those are singular scripts that can be hard to manage. We should add support for /etc/dhcpcd.{enter,exit}-hook.d. --Daniel signature.asc Description: PGP signature

Bug#1101001: chrony: Please cleanup dpkg-statoverrides properly

an up it's dpkg-statoverrides: $ dpkg-statoverride --list | grep chrony root _chrony 640 /etc/chrony/chrony.keys _chrony _chrony 750 /var/lib/chrony _chrony _chrony 750 /var/log/chrony --Daniel signature.asc Description: PGP signature

Bug#1061278: deluge-gtk: type to search fails with console error

proper "filter search", ctrl-f has always been the proper way to acchieve this. Regards, Daniel

Bug#1100901: RM: libyang2 -- Replaced by libyang [RoM]

.d.o gives an empty result too. Regards, Daniel

Bug#1100863: clatd: libnet-ip-perl and libnet-dns-perl should be among the dependencies

I'm planning to get to it in time for Trixie in any case. --Daniel signature.asc Description: PGP signature

Bug#1100774: RM: yosys [armel armhf i386] -- ROM; poor upstream 32bit support

i386]. Multiple upstream projects involved have poor 32bit support now and we don't feel it's worth the effort to keep this working for a niche toolchain. Thanks, --Daniel signature.asc Description: PGP signature

Bug#1100851: yosys: Unreproducible yet again

Again with fixed CC list. On Wed, Mar 19, 2025 at 03:41:27PM +0100, Daniel Gröber wrote: > X-Debbugs-Cc: > pkg-electronics-de...@alioth-lists.debian.net, > Scott Ashcroft , > Steffen Möller , > Tarik Graba , > Philipp Klaus Krause , > "J. Neuschäfer" , >

Bug#1100851: yosys: Unreproducible yet again

0 a locale thing or something? O_O --Daniel signature.asc Description: PGP signature

Bug#1100769: sbuild-debian-developer-setup: Support non-native chroot architectures

Hi josch, On Tue, Mar 18, 2025 at 02:30:57PM +0100, Johannes Schauer Marin Rodrigues wrote: > Quoting Daniel Gröber (2025-03-18 13:57:12) > > [branch]: https://salsa.debian.org/debian/sbuild/-/tree/fix-sdds-multi-arch > > $ git fetch https://salsa.debian.org/debian/sbuild.gi

Bug#1100781: yosys: Bring back i386/32bit support

On Tue, Mar 18, 2025 at 04:36:53PM +0100, Daniel Gröber wrote: > Package: yosys > Version: 0.51-1 > X-Debbugs-CC: > > (Sound of me praying the huge X-Debbugs-CC pseudoheader doesn't break) Apparently prayer doesn't work when it's line wrapped by email. Go fig

Bug#1100781: yosys: Bring back i386/32bit support

break) On Tue, Mar 18, 2025 at 03:08:30PM +, Scott Ashcroft wrote: > On Tue, 2025-03-18 at 15:02 +0100, Daniel Gröber wrote: > > Last time it just needed a strategically placed (double) cast. Idk > > why this would have started breaking again? > > htt

Bug#1068174: yosys: Please package the latest upstream release

On Tue, Mar 18, 2025 at 01:51:49PM +, Scott Ashcroft wrote: > On Tue, 2025-03-18 at 01:32 +0100, Daniel Gröber wrote: > > We've seen FST problems due to i386 floating point weirdness before > > (rounding, 80bit>64bit conversion IIRC). Might just be something like that

Bug#1068174: [Pkg-electronics-devel] Bug#1068174: yosys: Please package the latest upstream release

On Tue, Mar 18, 2025 at 11:19:00AM +, Scott Ashcroft wrote: > On Tue, 2025-03-18 at 00:16 +0100, Daniel Gröber wrote: > > I tried quickly building 0.51 and that seems to have yet more issues: > > > > /usr/bin/ld: /tmp/cc8nRSkd.ltrans73.ltrans.o: in function > >

Bug#1100769: sbuild-debian-developer-setup: Support non-native chroot architectures

to the existing UNRELEASED-$arch-sbuild for consistency. [branch]: https://salsa.debian.org/debian/sbuild/-/tree/fix-sdds-multi-arch $ git fetch https://salsa.debian.org/debian/sbuild.git fix-sdds-multi-arch --Daniel signature.asc Description: PGP signature

Bug#1068174: [Pkg-electronics-devel] Bug#1068174: yosys: Please package the latest upstream release

d reference to `abc::gzclose(void*)' collect2: error: ld returned 1 exit status It never ends :D --Daniel signature.asc Description: PGP signature

Bug#1068174: yosys: Please package the latest upstream release

ould we just be dropping 32-bit support? We've seen FST problems due to i386 floating point weirdness before (rounding, 80bit>64bit conversion IIRC). Might just be something like that again. Could drop 32bit or just skip tests there. I may have a quick look tomorrow and drop if its too annoying. --Daniel Hi Scott

Bug#1068174: yosys: Please package the latest upstream release

done. Uploading yosys_0.49.orig.tar.gz: done. Uploading yosys_0.49-1.debian.tar.xz: done. Uploading yosys_0.49-1_amd64.buildinfo: done. Uploading yosys_0.49-1_source.changes: done. Successfully uploaded packages. Thanks, --Daniel signature.asc Description: PGP signature

Bug#1068174: yosys: Please package the latest upstream release

025-03-14 at 21:10 +0100, Daniel Gröber wrote: > > tl;dr: yosys packaging still has issues in the docs build. Python/sphinx > > help wanted :-). > > When I try to build the package I get: > > $ gbp buildpackage > gbp:info: Creating /home/scott/yosys_0.49.orig.tar.gz > gbp:

Bug#1100420: ITP: wireguard-initramfs -- WireGuard initramfs integration

dropbear connections and DNS resolution can be used to find > WireGuard endpoints. This essentially enables the creation of a > fully encrypted remote-managed node, with the ability to prevent > all local access. That sounds awesome! Do you need any help packaging or a sponsor for the upload? LMK. --Daniel signature.asc Description: PGP signature

Bug#1068174: yosys: Please package the latest upstream release

ect yosys. It's not a toolchain package by Debian's definition -- no other package builds binary packages using it, AFAIK anyway ;-). --Daniel signature.asc Description: PGP signature

Bug#1092968: debian-installer: LUKS encrypted installation does not use /etc/crypttab to decrypt other drives

This bug is easy to reproduce without possibility for the user to make an error resulting in issues: - acquire the lastest netinstall image as of 2025-03-14. - partition for lvm - create lvm - create 2 lvs - set those lv for encyption - encrypt both with password - set 1 for /, set the other for

Bug#1068174: yosys: Please package the latest upstream release

Hi Scott, Hi ∀¬Scott, tl;dr: yosys packaging still has issues in the docs build. Python/sphinx help wanted :-). On Mon, Feb 10, 2025 at 01:04:01AM +0100, Daniel Gröber wrote: > I'm also working my way through the copyright review. I think 48k was > underestimating the amount of code

  1   2   3   4   5   6   7   8   9   10   >