Bug#1110254: [Pkg-openssl-devel] Bug#1110254:

control: forwarded -1 https://github.com/openssl/openssl/issues/28171 On 2025-08-05 11:00:52 [+1000], Daniel Black wrote: > upstream lodged: https://github.com/openssl/openssl/issues/28171 Thank you. Sebastian

Bug#1110254: [Pkg-openssl-devel] Bug#1110254: libssl3: segfault in libcrypto.so.3

On 2025-08-04 08:37:42 [+0800], Jim Barber wrote: > > Jim, can you confirm this? > > Hi Sebastian. Hi Jim, > I'm happy to give it a go, but will need a bit of guidance since I'm > not a Debian developer. Don't worry, I prepared an update at https://breakpoint.cc/openssl-3.0.17-1~deb12u2.tar Ca

Bug#1110254: [Pkg-openssl-devel] Bug#1110254: libssl3: segfault in libcrypto.so.3

On 2 August 2025 17:24:36 CEST, Stefan Ehmann wrote: >If I revert > >(and also 7141330fb98ceab643729f2d0f445f79f26addce), ebook-convert works fine >again. Jim, can you confirm this? > >According to the commen

Bug#1106786: git ftbfs on s390x (test failures)

On 2025-06-07 11:31:07 [+0200], Jonathan Nieder wrote: > New uploads coming later today. :) I don't want to rush or anything but… If you want me to prepare an unblock request before the upload happens or so, just say so ;) > For the future: in general if you prepare a "git format-patch" format >

Bug#1106786: git ftbfs on s390x (test failures)

On 2025-06-07 10:38:12 [+0200], Jonathan Nieder wrote: > Hi Sebastian, Hi Jonathan, > Sebastian Andrzej Siewior wrote: > > >> Even after the fix from https://bugs.debian.org/1102106, git ftbfs on > >> s390x. Filing as a separate bug because this is a different failure.

Bug#1106786: git ftbfs on s390x (test failures)

106786). + + -- Sebastian Andrzej Siewior Fri, 06 Jun 2025 18:07:16 +0200 + git (1:2.49.0-2) unstable; urgency=medium * debian/rules: remove overly strict check for license file diff -Nru git-2.49.0/debian/patches/0001-parse-fix-off-by-one-for-minimum-signed-values.patch git-2.49.0/debian/p

Bug#1104813: Not trivial to fix

On 2025-05-29 13:31:40 [+0200], Jordi Mallach wrote: > Hi! Hi, > I attempted getting rid of the embbeded libs in the past, and the > result was quite a disaster for several reasons. The biggest offender, > ckeditor, was not compatible with the one distributed by Debian, but I > will revisit this n

Bug#1102957: geventhttpclient: diff for NMU version 2.3.3-1.1

* Non-maintainer upload. + * Add patch to fix the testuite with OpenSSL 3.5 (Closes: #1102957). + + -- Sebastian Andrzej Siewior Fri, 23 May 2025 21:06:15 +0200 + geventhttpclient (2.3.3-1) unstable; urgency=medium * New upstream release diff -Nru geventhttpclient-2.3.3/debian/patches/s

Bug#1102957: [Pkg-openssl-devel] Bug#1102957: Bug#1102957: geventhttpclient: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13

> > Unsurprisingly this is caused by libssl. debbisect points to: > > I'm pretty busy the upcomming week so I won't be able to take a look. So > far this is the only bug reported against openssl 3.5 vs 3.4… turns out openssl is innocent. A patch is attached. > > Chris

Bug#1102957: [Pkg-openssl-devel] Bug#1102957: geventhttpclient: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13 returned exit code 13

On 2025-04-30 15:26:54 [+0200], Chris Hofstaedtler wrote: > Control: reassign -1 libssl3t64 > Control: affects -1 src:geventhttpclient … > Unsurprisingly this is caused by libssl. debbisect points to: > > bisection finished successfully > last good timestamp: 20250408T205804Z > first bad times

Bug#1096245: libnet-ssleay-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

control: tags -1 patch > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. I was working on it but then got distracted and now here is the patch. Sebastian From: Sebastian Andrzej Siewior Date: Tue, 18 Feb 2025 18:57:15 +0100 Subject: [

Bug#1091505: ruby3.3: diff for NMU version 3.3.6-1.1

ccess internet (Closes: #1091505). + + -- Sebastian Andrzej Siewior Fri, 10 Jan 2025 21:56:50 +0100 + ruby3.3 (3.3.6-1) unstable; urgency=medium [ Sylvain Beucler ] diff -Nru ruby3.3-3.3.6/debian/patches/ruby3.3-ruby-openssl-Only-CSR-version-1-encoded-as-0-is-allo.patch ruby3.3-3.3.6/debian/pa

Bug#1091505: ruby3.3: will FTBFS during trixie support period

On 2025-01-10 20:12:01 [+0100], Santiago Vila wrote: > Hi. Hi, > Note that for the purposes of fixing the bug it would be enough > if you refactor the test to assume that the internet connection > would never succeed, i.e. you can save the connection > altogether and do as if it always failed. If

Bug#1091505: ruby3.3: will FTBFS during trixie support period

On 2025-01-10 18:49:44 [+0100], Santiago Vila wrote: > You are absolutely right. This is not a "will fail to build in the future" > type of bug but a "tries to access Internet during build" bug. > > Such bugs are already RC, and have been for a long time, so I'm adjusting > the metadata accordingl

Bug#1087954: ruby3.3: diff for NMU version 3.3.6-1.1

L 3.4 (Closes: #1087954). + + -- Sebastian Andrzej Siewior Fri, 10 Jan 2025 17:22:05 +0100 + ruby3.3 (3.3.6-1) unstable; urgency=medium [ Sylvain Beucler ] diff -Nru ruby3.3-3.3.6/debian/patches/ruby3.3-ruby-openssl-Only-CSR-version-1-encoded-as-0-is-allo.patch ruby3.3-3.3.6/debian/patches/ruby3.3

Bug#1085589: m2crypto: FTBFS on arm*

Package: m2crypto Version: 0.42.0-1 Severity: serious Tags: sid The package FTBFS on armel and armhf but used to build in the previous version. Sebastian

Bug#1078274: clamav: FTBFS: clamscan/assorted_test.py::TC::test_pe_cert_trust FAILED

On 2024-09-01 22:02:27 [+0200], Santiago Vila wrote: > Could we please fix it in bookworm as well? > (packages in stable must build in stable) I plan to prepare 1.0.7 as pu this weekend. > Thanks. Sebastian

Bug#1073128: [Pkg-clamav-devel] Bug#1073128: clamav: unaligned access on armhf architecture

control: forwarded -1 https://github.com/Cisco-Talos/clamav/pull/1293 On 2024-06-24 22:10:27 [+0200], To Gianfranco Costamagna wrote: > Instead of arguing with me, you could forward it directly to upstream > and give a pointer to apply whatever upsteams did. Forwarded upstream. Would be nice if y

Bug#1073128: [Pkg-clamav-devel] Bug#1073128: clamav: unaligned access on armhf architecture

On 2024-06-13 09:34:14 [+0200], Gianfranco Costamagna wrote: > Hello, in Ubuntu, where the kernel is configured to forbid unaligned accesses > on armhf, the package FTBFS > (this should be reproducible also on some Debian buildd machines, this is why > I'm reporting as serious severity) Isn't

Bug#1073013: nodejs: Testsuite fails with OpenSSL 3.2.2

/24338. I don't know if node relies on that error outside of the testsuite. The patch attached swaps the error code and the test passes. OpenSSL 3.2.2 is currently in unstable. Sebastian From: Sebastian Andrzej Siewior Date: Tue, 11 Jun 2024 19:30:13 + Subject: [PATCH] tests: Check for

Bug#1069603: [Pkg-openssl-devel] Bug#1069603: Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

On 2024-04-21 19:30:21 [+0200], Paul Gevers wrote: > Hi Hi, > > Could britney be hinted to migrate both at the same time? This should > > solve the issue you pointed out. > > There is no "please test together" knob if that's what you mean (is that > what you mean?). Yes, it is/ was. >

Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

On 2024-04-21 13:42:03 [+0200], Paul Gevers wrote: > opensslfrom testing3.2.1-3 > libcrypt-smime-perlfrom testing0.28-1 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. > > Currently this regression is

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

#x27;s test file. Further testing is welcome by actual users ;) I can NMU if needed just yell. Sebastian From a54b5e81a61aa7e77e45a970ce88b9b4269fde7d Mon Sep 17 00:00:00 2001 From: Sebastian Andrzej Siewior Date: Mon, 8 Apr 2024 18:03:30 +0200 Subject: [PATCH 1/2] crypt/blowfish: Remove EVP_CIPHER_CT

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

On 2024-04-07 15:36:37 [+0800], Sean Whitton wrote: > Hello, Hi, > On Sat 06 Apr 2024 at 03:24pm +02, Salvatore Bonaccorso wrote: > > > As it is a regression caused by libssl3 3.0.11 based to 3.0.13, why is > > it reassigned to yapet? (the regression is as well present in > > unstable). > > I wa

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

On 2024-04-06 17:17:45 [+0800], Sean Whitton wrote: > Hello, Hi, > It looks like the problem is opening YAPET1.0-format databases, which > the manpage explicitly says is meant to work. > > I've made a sample YAPET1.0 database using a stretch VM. Using the > attached: > > - On bookworm, invoke '

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

On 2024-03-31 19:42:24 [+], tony mancill wrote: > Given what has unfolded over the past few days regarding xz-utils and > CVE-2024-3094 [0], should we revisit the patches applied here and for > #1063252? Are they still needed? Not with the fallback to pre 5.4.x series but *I* don't think this

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

On 30 March 2024 13:14:37 CET, Sean Whitton wrote: >Hello, Hi, >I downgraded, changed the password for my database to 'asdf', >changed it back to the password it had before, upgraded libssl3, >and the bug did not appear. > >I reverted to my original db, downgraded again, deleted an entry wit

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

On 2024-03-30 09:25:27 [+0800], Sean Whitton wrote: > Package: libssl3 > Version: 3.0.13-1~deb12u1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: t...@security.debian.org > Control: affects -1 + yapet > > Dear maintainer, > > This version of libssl3 from bookworm-prop

Bug#1066576: nagios-plugins-contrib: FTBFS: check_memcached.l:339:37: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

control -1 tags patch the patch attached fixes the warnings in check_memcached.l. Sebastian >From 155e35ace12f41bbaa42e4ea19bfea6de416bd95 Mon Sep 17 00:00:00 2001 From: Sebastian Andrzej Siewior Date: Fri, 22 Mar 2024 19:48:09 +0100 Subject: [PATCH] Compile warnings. Address various comp

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

On 2024-03-12 09:26:32 [-0400], Jeremy Bícha wrote: > > Could someone check this, please? > > Did you try running autopkgtests on this version? The autopkgtests fail for > me. autopkgtests were the first thing that pointed me here and they passed. If you say they fail for you then I may have use

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

On 2024-03-11 21:23:03 [+], Amin Bandali wrote: > Hi, Hi, > On Mon, Mar 11, 2024 at 05:55:31PM +0100, Sebastian Andrzej Siewior wrote: > > On 2024-03-11 00:05:54 [+], Amin Bandali wrote: > > > Hi Sebastian, all, > > Hi, > > > > > Will this fix

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

On 2024-03-11 00:05:54 [+], Amin Bandali wrote: > Hi Sebastian, all, Hi, > Will this fix be enough for addressing all cases, though? I think so. Do you have a test case for me to check? > I'm thinking specifically of cases where tarball repacking > is involved, for example when using git-bui

Bug#1063252: Proposed fix broke pristine-tar for me

On 2024-03-10 00:12:46 [+0100], Andrea Pappacoda wrote: > Hi, thanks for your fix! Hi, > Unfortunately it seems that your patch has broke tarball generation for one > of the packages I maintain, dynarmic. > >$ gbp export-orig >gbp:info: Creating /home/tachi/dev/deb/dynarmic_6.5.0+ds.orig.

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

EASED; urgency=medium + + * Non-maintainer upload. + * Preoperly account -T parameter for xz. Thanks to Jia Tan for the hint. +(Closes: #1065751). + + -- Sebastian Andrzej Siewior Sun, 10 Mar 2024 21:38:16 +0100 + pristine-tar (1.50+nmu1) unstable; urgency=medium * Non-maintainer upload. diff

Bug#1062072: [Pkg-clamav-devel] Bug#1062072: clamav: NMU diff for 64-bit time_t transition

On 2024-01-31 09:16:02 [+], Steve Langasek wrote: > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a > period of several days before we begin uploads to unstable; so if information > becomes

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

control: tags -1 patch fixed-upstream On 2023-10-02 17:12:53 [+0200], Julian Andres Klode wrote: > Being subscribed to the mailing list, grabbing the patch and applying > it and shipping it isn't hard, but if you were wondering why it's There are different views here. But Daniel was nice enough t

Bug#1055416: nodejs: Testsuite failure in test-crypto-dh since OpenSSL 3.0.12/3.1.4.

s up the new OpenSSL vesion then it should be okay to apply the original commit. Sebastian From: Sebastian Andrzej Siewior Date: Sun, 5 Nov 2023 13:08:23 +0100 Subject: [PATCH] test: Alter error message. This is variant of upstream's commit 8eea2d3709090 ("test: fix crypto-dh error message

Bug#1054546: openssl: The engine interface seems to be broken.

Package: openssl Version: 3.0.12-1 Severity: serious Control: affects -1 + src:libp11 Control: forwarded -1 https://github.com/openssl/openssl/issues/22508 At least for libp11 the engine interface seems to be broken. Sebastian

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

On 2023-09-27 21:45:03 [-0400], Jon DeVree wrote: > I posted an updated v3 version of the patch: > > https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00110.html Just rebuilt grub with v3 of the patch and I can confirm that it works. Thank you. Referencing the message-id or the link to lo

Bug#1052331: libcrypt-openssl-pkcs12-perl

Package: libcrypt-openssl-pkcs12-perl Version: 1.9-2 severity: serious I reported FTBFS against openssl 3.0 in #1006386 and now it kind of falls apart again. The check in patch is | $major eq "3.1" and $minor <= 2) or ($major eq "3.0" and $minor <= 10) and I have now 3.1.3 in experimental and 3

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

On 2023-09-15 15:51:51 [+0200], Felix Zielcke wrote: > Hi Sebastian, Hi Felix, > there's now a patch from Jon DeVree upstream, which might fix this for > you. Is it possible for you to test his patch? > > https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00059.html Yes it sovles the issu

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

On 2023-09-12 15:43:34 [+0200], Daniel Kiper wrote: > Hey, Hi, > Adding Lidong... > > Sebastian, Lidong is working on a fix for this issue. ach great. > Lidong, please keep Sebastain in the loop. > > Daniel Sebastian

Bug#1051563: mutt: CVE-2023-4874 CVE-2023-4875

Hi Antonio! On 2023-09-10 15:57:58 [+0200], Antonio Radici wrote: > On Sun, Sep 10, 2023 at 01:38:33PM +0200, Salvatore Bonaccorso wrote: > > Hi Antonio, > > > > FWIW, I have done the bookworm-security upload already to > > security-master, and still working on the bullseye-security one (with > >

Bug#1051563: mutt: CVE-2023-4874 CVE-2023-4875

On 2023-09-10 15:57:13 [+0200], Antonio Radici wrote: Hi Antonio, > On Sun, Sep 10, 2023 at 01:47:30PM +0200, Salvatore Bonaccorso wrote: > > Hi Antonio, > > > > On Sun, Sep 10, 2023 at 01:24:10PM +0200, Antonio Radici wrote: > > > On Sun, Sep 10, 2023 at 01:05:31PM +0200, Antonio Radici wrote: >

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

Package: grub2 Version: 2.12~rc1-9 Severity: Serious control: forwarded -1 https://savannah.gnu.org/bugs/?64376 I have a single XFS partition which contains the root filesystem and the boot partition. Since the recent upgrade to the 2.12 series I can't boot anymore because grub complains that it c

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 25 February 2023 16:20:45 UTC, Scott Kitterman wrote: >True. > >I'm not a C programmer, so I may be unduly concerned about the maintenance >load. I'll defer to your judgement. I'm going to throw this on my machine to get more testing - more than just the test suite. What about going through

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 25 February 2023 14:57:28 UTC, Scott Kitterman wrote: >Generally favorably, but I'd rather wait for upstream to agree on it, >otherwise it may be a patch we have to maintain forever. Now we maintain the tfm bits. >What's their reaction to the change? No reply so far. The first few patches

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 2023-02-24 21:00:43 [+], Scott Kitterman wrote: > I don't know of anything. I'd go ahead and upload the fix. how do you feel about replacing libtfm with openssl? > Scott K Sebastian

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 2023-02-24 12:44:49 [-0800], Nye Liu wrote: > On Fri, Feb 24, 2023 at 09:39:03PM +0100, Sebastian Andrzej Siewior wrote: > > Can you re-install libtfm1 and ensure that both point to that lib? > > libtfm1 0.13-4.1 fixed the problem. Should probably be version bumped in the &

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 2023-02-24 12:21:48 [-0800], Nye Liu wrote: > Feb 24 12:19:44 ln clamd[1537504]: LibClamAV debug: in cli_cvdload() > Feb 24 12:19:44 ln clamd[1537504]: LibClamAV debug: MD5(.tar.gz) = > f7eaac9ce4a83cc4c2526fe8f7d669db > Feb 24 12:19:44 ln clamd[1537504]: LibClamAV debug: cli_versig: Decoded >

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 2023-02-24 11:22:12 [-0800], Nye Liu wrote: > Tried mirroring working cvds from another machine > > $ md5sum * > 09c62fbb8d2de9cfeca516b3927347ba bytecode.cvd > 7294b378c7bd3bf86314365d96aea3e4 daily.cvd > a7bd2fc1eafcb260e76769a5821cb204 freshclam.dat > 3a42e5027c90fba0e54d2abdaa9e86b4 mai

Bug#1031509: [Pkg-clamav-devel] Bug#1031509: ETA on Patch for Buster

+LTS On 2023-02-20 12:22:48 [+0200], Andries Malan wrote: > Hi There Hi, > Would you be so kind as to provide an ETA for the above mentioned bug that > was reported. > This would be greatly appreciated. I Cced the LTS team because Buster is LTS territory. > Regards Sebastian

Bug#1031509: [Pkg-clamav-devel] Bug#1031509: clamav: 2 RCE bugs in ClamAV

On 2023-02-18 08:58:57 [+], Laura Smith wrote: > Could you confirm when the Debian Bullseye updates are due to be uploaded ? https://bugs.debian.org/1031536 > Thanks ! Sebastian

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

On 2023-02-10 20:22:54 [+], Thorsten Glaser wrote: > Sebastian Andrzej Siewior dixit: > > >Good. So unless Thorsten disagrees this is done ;) > > Please also test the upgrade with 4.16.0-1~bpo11+1 installed > on bullseye instead of 4.17.0-2~bpo11+1 (since that is a

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

On 2023-02-10 20:43:01 [+0100], Helge Kreutzmann wrote: > Hello Sebastian, Hi Helge, > From the manpages-l10n side everything is in place, I would then also > properly close #1028233. (Uploads to bpo do not manipulate the BTS). Good. So unless Thorsten disagrees this is done ;) > Greetings > >

Bug#1028375: Accepted xz-utils 5.4.1-0.1 (source) into unstable

On 2023-02-01 17:59:57 [+], Thorsten Glaser wrote: > > xz-utils (5.4.1-0.1) unstable; urgency=medium > > . > > * Non-maintainer upload. > > * Update pt_BR translations. > > * Add lintian overrides and an override for blhc. > > This is missing the updated Breaks+Replaces for manpages-l10n

Bug#1028375: still conflicting with manpages-fr 4.16.0-3~bpo11+1

On 31 January 2023 08:00:23 UTC, Thorsten Glaser wrote: >Sebastian Andrzej Siewior dixit: > >>Then I will update the versions as suggested. My understanding was the >>problem persists because the bpo version was not yet updated. The >>version in sid did not ship the man-p

Bug#1028375: still conflicting with manpages-fr 4.16.0-3~bpo11+1

On 2023-01-30 21:57:28 [+], Thorsten Glaser wrote: > Sebastian Andrzej Siewior dixit: > > >Okay. So I do nothing and just wait for the bpo package to appear which > >will then solve the problem? > > No, you must fix the problem in xz-utils in bookworm/sid as well. >

Bug#1028375: still conflicting with manpages-fr 4.16.0-3~bpo11+1

On 2023-01-30 21:51:11 [+0100], Helge Kreutzmann wrote: > Hello Sebastian, Hi Helge, > On Mon, Jan 30, 2023 at 07:53:51PM +0100, Sebastian Andrzej Siewior wrote: > > On 2023-01-30 18:04:35 [+], Thorsten Glaser wrote: > > > reopen 1028375 > > > found

Bug#1028375: still conflicting with manpages-fr 4.16.0-3~bpo11+1

On 2023-01-30 18:04:35 [+], Thorsten Glaser wrote: > reopen 1028375 > found 1028375 5.4.1-0.0 > thanks > > Patrice Duroux dixit: > > >Was this supposed to be closed? Or will it be with another manpages-fr bpo? > > 5.4.1-0.0 only conflicts with manpages-fr (<< 4.1.0-1) > so the upload did not

Bug#1028233: xz-utils: tries to overwrite files in manpages-fr (4.16.0-3~bpo11+1)

On 2023-01-11 21:01:11 [+0100], To Helge Kreutzmann wrote: > > For your update you should use as version "<< 4.1.0-1". > > (and remember to put it in for both manpages-de and manpages-fr) > > Okay, will do. Just to double check: This is what I did: https://salsa.debian.org/debian/xz-utils/-/c

Bug#1028233: xz-utils: tries to overwrite files in manpages-fr (4.16.0-3~bpo11+1)

On 2023-01-11 21:53:14 [+0100], Helge Kreutzmann wrote: > Hello Sebastian, Hello Helge, > Well, this is not correct. See, e.g., > https://packages.debian.org/bullseye-backports/all/manpages-de/filelist > > The man pages are there. yes, in backports. Not in the "regular" package. > Of course,

Bug#1028233: xz-utils: tries to overwrite files in manpages-fr (4.16.0-3~bpo11+1)

On 2023-01-10 09:36:04 [+0100], Helge Kreutzmann wrote: > Hello Sebastian, Hi Helge, > On Mon, Jan 09, 2023 at 09:38:31PM +0100, Sebastian Andrzej Siewior wrote: > Sorry, I was really tired yesterday evening and just wanted to send a > short "ack". no worries. Just warnin

Bug#1022336: xz-utils: FTBFS: Can't exec "cmake": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 526.

On 2022-10-23 15:12:35 [+0200], Lucas Nussbaum wrote: > Relevant part (hopefully): > > debian/rules build > > dh build --parallel > > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) > >dh_update_autotools_config -O--parallel > >dh_auto_configure -O--parallel >

Bug#1020592: [Pkg-javascript-devel] Bug#1020592: nodejs: Testsuite is using smoil keys

On 23 September 2022 21:18:26 UTC, "Jérémy Lal" wrote: >I'll upload nodejs 18.9.1 this week-end, along with a/your fix for that >issue. Thank you. > >Jérémy -- Sebastian

Bug#1020592: [Pkg-javascript-devel] Bug#1020592: nodejs: Testsuite is using smoil keys

control: found -1 odejs/18.7.0+dfsg-5 On 2022-09-23 22:55:23 [+0200], Jérémy Lal wrote: > Thanks, I'm already aware of the need to run nodejs testsuite using > their own specific openssl.cnf. > It seems you are reporting a bug against a version of nodejs that has never > made it > to debian. Did y

Bug#1020592: nodejs: Testsuite is using smoil keys

via the config file. A patch for the latter has been attached. Sebastian From: Sebastian Andrzej Siewior Date: Fri, 23 Sep 2022 22:39:50 +0200 Subject: [PATCH] Add a CipherString for nodejs If the default security level is overwritten at build time of openssl then it is needed to lower it again

Bug#1020308: openssl: Test 90-test_threads.t fails randomly.

Package: openssl Version: 3.0.5-3 Severity: serious control: forwarded -1 https://github.com/openssl/openssl/issues/19243 After touching test/default.cnf in the last upload, the 90-test_threads.t test fails randomly on the last step (test_lib_ctx_load_config()). Sometimes "malloc(): unalig

Bug#1017637: havp: Not working anymore since linux-image-* v5.15.

On 2022-08-18 19:36:28 [+], Scott Kitterman wrote: Hi Scott, > I agree. It's been dead upstream for a long time. I think this is a > logical point to put an end to trying to keep it alive in Debian. nice to hear from you! Sorry for not replying earlier but I'm kind of busy… Anyway, I manage

Bug#1017637: havp: Not working anymore since linux-image-* v5.15.

Source: havp Version: 0.93-2 Severity: grave While testing havp before uploading I noticed that starting havp ends quickly with: | Starting HAVP Version: 0.93 | Filesystem not supporting mandatory locks! | On Linux, you need to mount filesystem with "-o mand" The so called "mandatory locks" have

Bug#1016290: openssl: EC code appears to be broken on s390x

Package: openssl Version: 3.0.5-1 Severity: serious Control: forward -1 https://github.com/openssl/openssl/issues/18912 Control: affects -1 libnet-dns-sec-perl It appears the EC code is broken for ed25519/ed448 on s390x. Sebastian

Bug#1011101: nodejs: FTBFS on mipsel: multiple failures with openssl 3.0

On 2022-05-16 22:38:44 [+0200], Jérémy Lal wrote: > Last time so many openssl-related test failures happened, > OPENSSL_CONF env was set to a relative path, and nodejs/openssl3 > expected an absolute path. I don't understand why mipsel is different here. The init looks okay. I copied the .cnf from

Bug#1006585: tpm2-tss-engine: FTBFS with OpenSSL 3.0

On 2022-02-27 23:37:35 [+], Luca Boccassi wrote: > This is known and expected, this package is an engine for OpenSSL 1.x. > The 3.x version is shipped as a separate and different project, already > uploaded to experimental: > > https://tracker.debian.org/pkg/tpm2-openssl > > Once OpenSSL 3.x

Bug#1011127: libssl3 breaks systems vith VIA Nehemiah cpu

control: forward -1 https://github.com/openssl/openssl/issues/18334 On 2022-05-17 16:01:35 [+0200], Wolfgang Walter wrote: > > Yes, with libssl3_3.0.3-4.noendbr_i386.deb this is fixed. perfect, thank you for the confirmation. I forwarded it upstream and I hope to have something for the next uplo

Bug#1011127: [Pkg-openssl-devel] Bug#1011127: libssl3 breaks systems vith VIA Nehemiah cpu

On 2022-05-17 12:53:07 [+0200], Wolfgang Walter wrote: > Systems with VIA Nehemiah cpu break after upgrading unstable. All commands > using libssl3 fail with … > lscpu shows: > > Architecture:i686 > CPU op-mode(s): 32-bit … > Flags: fp

Bug#1006568: rauc: FTBFS with OpenSSL 3.0

On 2022-05-11 17:58:22 [+0200], Uwe Kleine-König wrote: > I just confirmed that. I built libp11 in sid + openssl3. With the > resulting packages installed rauc just builds fine against openssl3. > > So I'm unsure what I should do about this bug. Close it? Reassign to > libp11? Just wait until it r

Bug#1010698: stunnel4: debci testsuite fails after openssl version update.

On 2022-05-07 20:52:41 [+0200], Paul Gevers wrote: > Hi Sebastian, Hi Paul, > On 07-05-2022 18:22, Sebastian Andrzej Siewior wrote: > > Usertags: flaky > > Why do you conclude that? Normally we call something flaky if it has a > reasonable amount of failures in pure testin

Bug#1010698: stunnel4: debci testsuite fails after openssl version update.

Package: stunnel4 Version: 3:5.63-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky The debci testsuite failed for all architectures after the recent openssl upload https://ci.debian.net/data/autopkgtest/testing/amd64/s/stunnel4/21436404/log.gz Am I right to assume as per |

Bug#907691: petri-foo: License incompatibility: links with OpenSSL

On 2018-08-31 15:03:38 [+0300], Yavor Doganov wrote: > Package: petri-foo > Version: 0.1.87-4 > Severity: serious > > This package is licensed under GPLv2 only but links with the OpenSSL > library which makes it impossible for distribution as the licenses are > incompatible. See > > https://www.

Bug#990228: [Pkg-openssl-devel] Bug#990228: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:

On 2021-06-23 14:46:37 [+0200], Andreas Beckmann wrote: > Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key' > - > Warning: No -copy_extensions given; ignoring any extensions in the request > Cannot write random bytes: > 8022CB35777F:error:127A:random number g

Bug#986622: [Pkg-clamav-devel] Bug#986622: Bug#986622: fixes

On 2021-04-21 08:17:53 [+0100], Athanasius wrote: > So long as any Debian update of the packages both addresses the > outstanding CVEs *and* quiets this logging I'll be happy. Be aware that I am following the process to get an update into Buster. Sebastian

Bug#986622: [Pkg-clamav-devel] Bug#986622: fixes

On 2021-04-13 16:08:17 [+0530], Utkarsh Gupta wrote: > Hi Sebastian, Hi, > Sebastian Andrzej Siewior wrote: > > My plan is to get 103.2 into Buster after I spent the day today > > to look what should be backported and what not. > > Do we not generally backport clamav as

Bug#980592: [Pkg-clamav-devel] Bug#980592: clamav: diff for NMU version 0.103.0+dfsg-3.1

On 2021-02-21 16:07:37 [+0100], Sebastian Ramacher wrote: > Control: tags 980592 + pending > > Dear maintainer, > > I've prepared an NMU for clamav (versioned as 0.103.0+dfsg-3.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. I clearly missed that par

Bug#983013: [Pkg-openssl-devel] Bug#983013: m2crypto: autopkgtest needs update for new version of openssl: M2Crypto.RSA.RSAError: sslv3 rollback attack

On 2021-02-18 08:15:15 [+0100], Paul Gevers wrote: > > I copied some of the output at the bottom of this report. I *think* > this may be related to CVE-2020-25657 "bleichenbacher timing attacks in > the RSA decryption API" against m2crypto, hence I file this bug against > m2crypto. The openssl s

Bug#979865: m2crypto FTBFS on IPV6-only buildds

control: found -1 0.31.0-1 On 2021-01-24 23:08:27 [+0200], Adrian Bunk wrote: > > The release team considers these bugs release critical. it would be easier to enforce to have all buildds configured equally so the package does not fail on a random buildd. > > and let it migrate to > > testing.

Bug#979865: m2crypto FTBFS on IPV6-only buildds

On 2021-01-12 08:22:05 [+0200], Adrian Bunk wrote: > Source: m2crypto > Version: 0.37.1-1 > Severity: serious > Tags: ftbfs I suggest to lower the severity to important and let it migrate to testing. After all this bug did not first appear in 0.37.1-1, it has been exposed after it hit buildd that

Bug#979146: gnat-gps: FTBFS because BD can not be installed (gnat-9 vs 10)

Package: src:gnat-gps Version: 19.2-3 Severity: serious Tags: sid ftbfs Hi, some BD of gnat-gps depend on packages which were built by gnat-9 others moved to gnat-10. libgnatcoll-db and libgnatcoll-bindings changed their binary packages and the old ones are by built by gnat-9, the new ones are bu

Bug#973955: bind9: flaky autopkgtest: DNS query rootserver

Source: bind9 Version: 1:9.16.6-3 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: flaky Hi, the autopkg test validates DNSSEC of internetsociety.org for it requires unrestricted internet access. For this it is needed to specify Restrictions: needs-internet in the

Bug#972974: [Pkg-clamav-devel] Bug#972974: Bug#972974: clamav-freshclam start faild.

On 2020-10-28 23:52:05 [-0500], ari...@despayre.org wrote: > I have checked the apparmor profile for clamav-daemon at /usr/sbin/clamd > > and > > | capability dac_override, > > exists. The bug report is about freshclam not clamd. > I had to install apparmor-utils to aa-disable the usr.sbin.cl

Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

On 2020-10-27 07:22:22 [+], Michael Borgelt wrote: > I have tried different permissions for the file and the directory without > success. The obove permissions are after a clean reinstall off clamav > package. The problem appears to be the apparmor or freshclam's profile for it. So disabling a

Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

On 2020-10-26 19:02:58 [+0100], Michael Borgelt wrote: > clamav-freshclam start faild with: > Okt 26 18:44:41 host freshclam[31527]: ERROR: initialize: libfreshclam init > failed. > Okt 26 18:44:41 host freshclam[31527]: ERROR: Initialization error! > Okt 26 18:44:41 bert freshclam[31527]: ERROR: C

Bug#963853: [Pkg-clamav-devel] Bug#963853: clamav: FTBFS on IPv6-only environments

On 2020-06-28 12:48:20 [+0100], Dominic Hargreaves wrote: > Source: clamav > Version: 0.102.3+dfsg-1 > Severity: serious > Justification: FTBFS (when it built before) > > During archive-wide test rebuilding of an IPv6-only environment (which Is this decision blessed by the release team? If so whe

Bug#945961: xz-utils: FTBFS: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'

On 2020-04-09 14:32:07 [+0100], Dimitri John Ledkov wrote: > Here is the debdiff that makes everything work for me. > > It smells like a subtle breakage in detecting/parsing makefile > targets, or like make regression. > > It is still odd, i.e. there is build target, then binary target, which > t

Bug#945961: xz-utils: FTBFS: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*'

On 2019-12-03 20:18:20 [-0800], Jonathan Nieder wrote: > Hi, Hi, > Let's track down the cause first, before pursuing workarounds. Nothing happened here so far and I almost forgot about it. xz 5.2.5 has been released in the meantime. Do you want me to help you out in anyway? I could add the fix I

Bug#955535: httping: flaky autopkgtest: PING google.com:80

Source: httping Version: 2.5-5 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: flaky The test for httping passed on amd64[0] and failed on arm64[1]. Looking at the failed log |autopkgtest [17:03:58]: test command3: httping -F -c 4 http://google.com |autopkgtest [17:

Bug#954402: OpenSSL EOF handling, severity import

Control: severity -1 important OpenSSL 1.1.1f is in unstable now which reverts the unexpected EOF reporting via SSL_ERROR_SSL. In the OpenSSL 3.0 release it will be reported again as SSL_ERROR_SSL with reason code SSL_R_UNEXPECTED_EOF_WHILE_READING. Therefore the severity is downgraded to `importa

Bug#954371: [Pkg-openssl-devel] Bug#954371: Bug#954371: libio-socket-ssl-perl: FTBFS since openssl 1.1.1e

On 2020-03-31 21:49:51 [+0200], Salvatore Bonaccorso wrote: > Hi Kurt, Hi Salvatore, > I see, but then I prefer to loop in Steffen Ullrich into the loop > (upstream of IO::Socket::SSL). Steffen, see the above comment from > Kurt in the Debian bug, so it looks we cannot close > https://github.com/n

Bug#955442: [Pkg-openssl-devel] Bug#955442: openssl breaks libio-socket-ssl-perl autopkgtest: 20 times "not ok"

On 2020-03-31 21:41:12 [+0200], Paul Gevers wrote: >passfail > opensslfrom testing1.1.1e-1 > libio-socket-ssl-perl from testing2.067-1 > all others from testingfrom testing there is more than just this. OpenSSL upstream r

Bug#954402: m2crypto: FTBFS since openssl 1.1.1e

On 2020-03-26 23:57:24 [-0400], Sandro Tosi wrote: > > So the test expects no error. Since the commit mention there is an > > error where earlier there was none. From the Changes file: > > > > | *) Properly detect EOF while reading in libssl. Previously if we hit an > > EOF > > |while reading

Bug#954402: m2crypto: FTBFS since openssl 1.1.1e

On 2020-03-21 23:33:34 [-0400], Sandro Tosi wrote: > > > The package FTBFS since openssl has been updated to 1.1.1e because the > > > testsuite fails. The failure is due to commit db943f43a60d ("Detect EOF > > > while reading in libssl") [0] in openssl. There an issue ticket [1] > > > which introdu

  1   2   3   4   5   6   >