On 2023-10-17 22:08:07 [+0200], Jérémy Lal wrote:
> I did not forget about this. Really sorry for the delay.
> Currently I'd be more willing to help someone maintain nodejs than doing it
> myself.
> However, I'll probably deal with the next 18.x update very soon, including
> your patch.
Thank you.
Package: openssl
Version: 3.1.2-1
Severity: wishlist
Tags: ftbfs
User:debian-de...@lists.debian.org
Usertags: loongarch64
OpenSSL 3.1.x in experimental FTBFS on loong64:
|crypto/aes/vpaes-loongarch64.S: Assembler messages:
|crypto/aes/vpaes-loongarch64.S:24: Error: no match insn: vori.b
$
enSSL 3.1 error codes (Closes: #1051795).
+
+ -- Sebastian Andrzej Siewior Tue, 17 Oct 2023 21:44:49 +0200
+
m2crypto (0.38.0-4) unstable; urgency=high
[ Stefano Rivera ]
diff -Nru m2crypto-0.38.0/debian/patches/0005-Force-enable-tlsv1-for-the-tls1-tests.patch m2crypto-0.38.0/debian/patches
On 2023-09-22 22:52:48 [+0200], Jérémy Lal wrote:
> Thanks, will include it soon.
Thanks. Any update on this?
I added two patches. The first one is a cherry-pick from upstream, the
second has been forwarded upstream via
https://github.com/nodejs/node/pull/49885
but upstream has no interes
On 2023-10-02 13:41:17 [+0200], Cyril Brulebois wrote:
> Adam D. Barratt (2023-10-02):
> > Unfortunately, the version format change from -0+deb11uX to -0~deb11uX
> > has broken the installer.
> >
> > The udebs end up with dependencies of the form ">= 1.1.1w", which
> > 1.1.1w-0~deb11u1 doesn't fu
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
Package: release.debian.org
Control: affects -1 + src:openssl
X-Debbugs-Cc: open...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
X-Debbugs-Cc: sebast...@breakpoint.cc
Severity: normal
This is an update of the openssl package to the 3.0.11 version, a
On 2023-09-23 20:39:32 [+0100], Adam D. Barratt wrote:
> Please go ahead.
Thanks, done.
> Regards,
>
> Adam
Sebastian
On 2023-09-22 17:59:51 [+0200], To sub...@bugs.debian.org wrote:
> Now I'm about to test this… But it looks promising ;)
Okay, builds.
Sebastian
ff-by: Sebastian Andrzej Siewior
---
test/common/index.js | 6 +-
.../test-https-agent-session-eviction.js | 1 +
test/parallel/test-tls-alert.js | 1 +
test/parallel/test-tls-getprotocol.js| 16 +---
test/parallel/tes
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
Package: release.debian.org
Control: affects -1 + src:mutt
X-Debbugs-Cc: m...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
X-Debbugs-Cc: sebast...@breakpoint.cc
Severity: normal
This is an update mutt package as provided by upstream to version 2.2.12
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
On 2023-09-14 21:52:25 [+0100], Adam D. Barratt wrote:
>
> That's now out, as SUA-240-1.
Thank you Adam.
> Regards,
>
> Adam
Sebastian
On 2023-09-14 06:31:26 [+0100], Adam D. Barratt wrote:
> On Wed, 2023-09-13 at 22:01 +0200, Sebastian Andrzej Siewior wrote:
> > On 2023-09-13 17:26:46 [+0100], Adam D. Barratt wrote:
> > > How does this sound for an SUA?
> [...]
> > This sounds entirely fine to me. I do
this file except in compliance with the License. You can obtain a copy
@@ -82,13 +82,16 @@
if (!rsa_param_encode(pkey, &str, &strtype))
return 0;
penclen = i2d_RSAPublicKey(pkey->pkey.rsa, &penc);
- if (penclen <= 0)
+if (penclen <= 0) {
+ASN1_STRI
On 2023-09-13 17:26:46 [+0100], Adam D. Barratt wrote:
> How does this sound for an SUA?
>
> ===
> Package : clamav
> Version : 1.0.3+dfsg-1~deb12u1 [bookworm]
>0.103.10+dfsg-0+deb11u1 [bullseye]
> Importance : medium
>
> ClamAV
Package: m2crypto
Version: 0.38.0-4
Severity: important
Control: affects -1 + src:openssl
Control: tags -1 + upstream patch fixed-upstream
Hi,
As far as I can tell, m2crypto compiles and passes the testsuite if
compiled and run against openssl 3.0 or 3.1. What currently fails is if
m2crypto is co
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
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
> >
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:
>
-1.0.3+dfsg/debian/changelog 2023-09-09 16:36:13.0 +0200
@@ -1,3 +1,10 @@
+clamav (1.0.3+dfsg-1~deb12u1) bookworm; urgency=medium
+
+ * Import 1.0.3
+ * Remove unnecessary warning messages in freshclam during update.
+
+ -- Sebastian Andrzej Siewior Sat, 09 Sep 2023 16:36:13 +0200
T([ClamAV], [0.103.9], [https://github.com/Cisco-Talos/clamav/issues], [clamav], [https://www.clamav.net/])
+AC_INIT([ClamAV], [0.103.10], [https://github.com/Cisco-Talos/clamav/issues], [clamav], [https://www.clamav.net/])
dnl put configure auxiliary into config
AC_CONFIG_AUX_DIR([config])
diff -Nru
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
On 2023-09-04 21:18:35 [+0200], To Adam D. Barratt wrote:
> > The next point release for both bullseye and bookworm is in a month.
> > Were you looking to have the clamav updates published via -updates
> > before that point?
>
> I almost started preparing 0.103.10 I think it will be easier to go w
On 2023-08-26 14:50:09 [+0200], To sub...@bugs.debian.org wrote:
> This is an update of the openssl package to the 1.1.1v version, a patch
> release
Upstream announced to release 1.1.1w on 11th September. They said it is
a "security-fix" with the highest severity defined as "low". This is
also th
On 2023-09-05 17:36:41 [+0100], Jonathan Wiltshire wrote:
>
> Please go ahead.
Thanks, done.
> Thanks,
Sebastian
On 2023-09-04 19:52:23 [+0100], Adam D. Barratt wrote:
> On Sun, 2023-08-27 at 13:20 +0200, Sebastian Andrzej Siewior wrote:
> > This is a stable update from clamav upstream in the 0.103.x series.
> > It fixes the following CVE
> > - CVE-2023-20197 (Possible DoS in HFS+ file p
date links for version update.
+ * Fix package description. (Closes: #1028585)
+
+ -- Sebastian Andrzej Siewior Sat, 02 Sep 2023 15:29:41 +0200
+
kernelshark (2.2.0-2) unstable; urgency=medium
* Fix symlink names. (Closes: #1035449)
diff -Nru kernelshark-2.2.0/debian/control kernelshark-2.
], [https://github.com/Cisco-Talos/clamav/issues], [clamav], [https://www.clamav.net/])
dnl put configure auxiliary into config
AC_CONFIG_AUX_DIR([config])
diff -Nru clamav-0.103.8+dfsg/debian/changelog clamav-0.103.9+dfsg/debian/changelog
--- clamav-0.103.8+dfsg/debian/changelog 2023-02-17 21:4
On 2023-03-21 08:42:00 [+0100], Giancarlo Giesa wrote:
> description: the clamav upgrade via apt-get failed
> the reason seems to be that the file /var/log/clamav/freshclam.log is not
> detected but instead this exists
Is this still valid? Asking because…
> proceeding with the command dpkg --conf
On 2023-08-13 17:42:29 [+0200], Andreas Guenther wrote:
> you can clearly see that the service is triggered by the associated
> socket! This was not the case with Debian Linux Bullseye!
>
> The only currently working solution is this:
>
> systemctl disable --now clamav-daemon.s
On 2022-09-07 15:26:44 [-0500], Tim McConnell wrote:
> --log="$HOME/.clamtk/history/$(date +\%b-\%d-\%Y).log" 2>/dev/null # clamtk-
> scan"
> Loaded: loaded (/var/spool/cron/crontabs/tmick; generated)
> Active: failed (Result: exit-code) since Wed 2022-09-07 04:39:26 CDT; 1s
> ago
> Trigg
On 2023-06-12 08:39:53 [+0300], Martin-Éric Racine wrote:
> Syslog already suggests what the fix should be:
>
> $ grep Clamonacc /var/log/syslog
> 2023-06-12T08:33:40.562184+03:00 p8h61 clamonacc[248359]: ERROR:
> Clamonacc: at least one of OnAccessExcludeUID, OnAccessExcludeUname,
> or OnAccessEx
On 2023-06-26 18:10:57 [+0100], Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
>
> You're both going to have to help me a) understand what is the user-facing
> problem you're solving which is necessary to fix in stable and b) whether
> you're both agreed on how to fix it.
a) The bpo of manp
control: retitle -1 unblock: openssl/3.0.9-1
On 2023-05-30 22:16:53 [+0200], To sub...@bugs.debian.org wrote:
>
> Please unblock package openssl.
>
> The 3.0.9 release contains security and non-security related fixes for
> the package. There are five new CVEs in total that has been addressed.
>
On 2023-05-09 22:58:43 [+0200], Samuel Thibault wrote:
> My patch is not a nop. Previously to Lasse's commit, the
> --enable-assembler=x86_64 option would make no difference from
> --enable-assembler=no. With Lasse's commit, --enable-assembler=x86_64
> is now *refused* by ./configure. And thus amd6
On 2023-05-06 15:49:33 [+0200], Samuel Thibault wrote:
> debian/rules is passing --enable-assembler=x86_64 to configure, but that
> case was removed, see ChangeLog:
>
> commit ac10b1b3622e70881595586edfb8a3ebdcd76bb6
> Author: Lasse Collin
> Date: 2022-11-14 17:58:07 +0200
>
> Build: Omit
control: retitle -1 openssh: Relax version check with OpenSSL 3.0+
control: tags -1 fixed-upstream
control: forwarded -1 https://bugzilla.mindrot.org/show_bug.cgi?id=3548
It has been fixed upstream in commit
b7afd8a4ecaca ("Handle OpenSSL >=3 ABI compatibility.")
Sebastian
ork-Manager.
I retried it and it appears to be openssh. It might be the part with the
X on startup starts the ssh agent and this fails since the ssh command
itself aborts due to the version check.
I kept the severity as reported but it only affects openssl in
experimental.
Sebastian
From: Sebastian
On 2023-04-30 18:43:18 [+0200], Helge Kreutzmann wrote:
> Hello Sebastian,
Hi Helge,
> > - the backport package of manpages-de and manpages-fr provides a
> > man page for xz. These files conflict with the one provided by
> > xz-utils package. The bpo package and xz-utils in Bookworm have prope
Package: mutt
Version: 2.2.9-1
Severity: important
control: tags -1 patch upstream fixed-upstream
control: forwarded -1
https://gitlab.com/muttmua/mutt/-/commit/5df86199463b5cf893fb6a37457fa02804d3b02a.patch
>From https://gitlab.com/muttmua/mutt/-/issues/400
| Currently, mutt message-id generati
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
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
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
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
&
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
>
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
+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
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
V], [0.103.8], [https://github.com/Cisco-Talos/clamav/issues], [clamav], [https://www.clamav.net/])
dnl put configure auxiliary into config
AC_CONFIG_AUX_DIR([config])
diff -Nru clamav-0.103.7+dfsg/debian/changelog clamav-0.103.8+dfsg/debian/changelog
--- clamav-0.103.7+dfsg/debian/changelog
Source: puma
Version: 5.6.5-2
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails from time to
time.
From
https://ci.debian.net/packages/p/puma/testing/a
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
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
>
>
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
On 2023-02-03 10:43:43 [+0800], zhangdandan wrote:
> Dear maintainer(s),
> The configuration of Loongarch64 should be modified in Openssl.
> Please consider the suggestion of Han Gao. I have tested the patch.
So it has been tested, thank you.
There will be an upload on TUE evenning of 3.0.8 an
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
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.
>
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
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
control: forwarded -1 https://translationproject.org/domain/xz.html
On 2023-01-21 16:36:30 [+0100], Helge Kreutzmann wrote:
> Please kindly include the attached da.po and forward it to upstream so
> that it is included there in future versions as well.
upstream (xz) does not accept any translatio
On 2023-01-21 00:05:53 [+0800], Han Gao wrote:
> Loongarch64 is little endian. So [1] should be removed.
Are you sure? I applied exactly what I received in #1024414. Please test
the patches that you send.
> [1]:
> https://salsa.debian.org/debian/openssl/-/blob/debian/openssl-3.0.7-2/debian/pat
Package: devscripts
Version: 2.22.2
Severity: wishlist
uscan can created a repacked file based on d/copyright and I *think*
this is handled by devscripts. It invokes `xz' for compression without
the -T flag. Passing the -T argument with either 0 or 1 as the number of
CPUs has the following benefit
On 2023-01-19 12:02:52 [-0800], Ryan Tandy wrote:
> Hello Jonathan and Sebastian.
Hi Ryan,
> In any case I believe the use of Recommends is Policy-compliant since there
> are myriad ways to specify the trusted CAs and the default ldap.conf setting
> is only for convenience.
It sounds reasonable.
control: reassign -1 ldap-utils 2.4.57+dfsg-3
On 2023-01-04 13:50:53 [+], Jonathan Rietveld wrote:
> We've since found out that installing libldap-common resolves our
> issue, as others
> (https://github.com/wheelybird/ldap-user-manager/issues/172 and
> https://github.com/docker-mailserver/doc
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
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,
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
On 2023-01-09 21:13:16 [+0100], Helge Kreutzmann wrote:
> Hello Sebastian,
Hi Helge,
just to correct your previous email, the bug report was/is from Raphaël
Halimi not me. I just pinged you.
> > Interresing. manpages-fr and manpages-de from manpages-l10n in bookworm
> > does not ship $LANG/man1/
On 2023-01-08 18:32:26 [+0100], Raphaël Halimi wrote:
> Today I tried to upgrade a Bullseye laptop to Bookworm.
>
> The upgrade crashed with xz-utils trying to overwrite
> /usr/share/man/fr/man1/xz.1.gz which belonged to manpages-fr from backports
> (4.16.0-3~bpo11+1).
>
> After running dpkg --fo
Package: trace-cmd
Version: 3.1.4-1
Severity: wishlist
A new version of trace-cmd, 3.1.5, is available. Please package it for
Bookworm.
Sebastian
On 2023-01-03 20:21:57 [+], Jonathan wrote:
> Package: openssl
>* What led up to the situation?
>
> After trying to update to bullseye, connecting to our LDAP server no longer
> works, both with pam_ldap package as well as using ldapsearch from ldap-utils.
What happens with if you add "-
On 2022-12-31 01:09:46 [-0500], Scott Kitterman wrote:
> I looked at it some and the testfiles appear to be gone. Let's drop the
> binary
> and move on.
I references them from the build-directory. So we have some of them. I
don't know if new files are there (in the build directory) but the .rar
On 2020-04-09 19:43:34 [+0800], Paul Wise wrote:
> On Thu, 9 Apr 2020 11:45:49 +0200 Sebastian Andrzej Siewior wrote:
>
> > Can this be closed?
>
> Since the patch and feature hasn't been merged, I don't think so.
What about now given that #956452 has been closed?
Sebastian
On 2022-12-31 01:09:46 [-0500], Scott Kitterman wrote:
> I discovered that the experimental (and upstream-experimental) branches still
> have the crates that are now excluded when the tarball is created. I made a
> new branch called upstream-experimental-fixup and pushed it. You ought to be
>
On 2022-12-30 16:22:21 [-0500], Scott Kitterman wrote:
> Great. I finished the changes for the embedded crates (it's not perfect
> machine readable copyright format, but it's close and I think it will do for
> the moment) and pushed the change. It should be a fast forward for you when
> you pu
On 2022-12-29 00:37:20 [-0500], Scott Kitterman wrote:
> I've pushed additional d/copyright changes to the experimental branch. With
> those changes, uscan should produce a DFSG free tarball. Because I ripped
> out
> all the Windows specific stuff, the Rust crates don't compile. I don't know
On 2022-12-26 10:50:44 [+0100], Joerg Dorchain wrote:
> the latest update to version 0.103.7+dfsg-1+b2 gives for me
> ERROR: Can't verify database integrity
> for clamav-daemon and clamav-freshclam
>
> Downgrading to libclamav9 0.103.7+dfsg-1+b1 as a workaround
> helps.
Just to be clear: You also
On 2022-12-22 18:31:37 [-0500], Scott Kitterman wrote:
> I think we should focus on getting clamav up to 1.0.0 before the freeze and
> deal with the unrar bits later (should be easy enough to get a freeze
> exception for if we need it).
>
> If you think tha'ts reasonable, I'll manually make the
On 2022-12-12 22:45:57 [-0500], Scott Kitterman wrote:
>
> That doesn't sound too bad. I'll see if I can find some time to work on the
> split, but probably not until Wednesday or Friday.
So I managed to tell cmake to use the tfm library instead of the bundled
code and the testsuite fails now b
Package: libtracefs
Version: 1.5.0-1
Severity: wishlist
Please update libtracefs to v1.6+. The later trace-cmd depends on 1.6+
Sebastian
On 2022-12-07 12:51:30 [-0500], Scott Kitterman wrote:
> OK. I'm back to having some time for Debian again, so let me know how I can
> help.
I pushed something to the experimental branch. It ain't much…
This updates the build dependencies and you still need download the
upstream .tar.gz yourself
On 2022-10-30 14:44:16 [+], Scott Kitterman wrote:
> Looks like we'll also need to patch tomsfastmath, such upstream parched their
> embedded copy:
>
> https://github.com/Cisco-Talos/clamav/commit/17e52a09a91d8f6535014873ab6cb99c827b5e20
that needs we need to do mini transition for libtfm1 u
On 2022-11-21 21:39:21 [+0100], John Paul Adrian Glaubitz wrote:
> Hi!
Hi,
> On 11/21/22 00:07, John Paul Adrian Glaubitz wrote:
> > This issue has shown in other packages such as glibc on ia64 [1]:
> >
> > /usr/bin/ld:
> > /<>/build-tree/ia64-libc/dlfcn/bug-atexit3-lib.so: version
> > node not
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
>
On 2022-09-29 20:03:56 [+0200], Richard B. Kreckel wrote:
> On 9/27/22 08:15, Sebastian Andrzej Siewior wrote:
> > It is not part of any standard.
>
> It could hardly be less standardized. See ISO/IEC 10118-3:2018.
That is not what I meant.
Wahat I meant that it is par
On 2022-09-26 00:10:27 [+0200], Richard B. Kreckel wrote:
> W.r.t. RIPEMD160, this seems to be a mistake:
> https://github.com/openssl/openssl/issues/16994
> Also, Fedora seems to have worked around this.
The issue is not closed by OpenSSL upstream so there is nothing that I
can backport. I don't
On 2022-09-25 22:59:27 [+0200], Richard B. Kreckel wrote:
> On 9/25/22 21:14, Sebastian Andrzej Siewior wrote:
> > See the man page for OSSL_PROVIDER-legacy.
>
> Having to add a the extra option -provider legacy breaks otherwise flawless
> existing software.
This happens. You c
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
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
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
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
On 2022-09-18 21:06:59 [+0200], Kurt Roeckx wrote:
> I'm not sure that having the legacy provider automatically enabled by
> default when it's installed is a good idea. That means once it's
> installed, all applications have it by default. I think it needs to be
> enabled per application.
The only
On 2020-07-16 08:46:43 [+0200], Kurt Roeckx wrote:
> On Thu, Jul 16, 2020 at 03:57:17AM +0100, Dimitri John Ledkov wrote:
> >
> > openssl package could ship `.include /etc/ssl/providers.d/` in ssl.conf.
>
> That would actually make sense.
>
> We could use the include thing to ship a config file
On 2022-09-13 18:30:05 [+0200], Kurt Roeckx wrote:
> > > 3) provide a symlink from /usr/lib/ssl/cert.pem to
> > >/etc/ssl/certs/ca-certificates.crt
> >
> > Kurt, I tend to provide this symlink. Any objections?
> > I'm kind of confused that it works for others, like curl. But I don't
> > see an
On 2016-01-04 23:50:10 [+0100], Jan Dittberner wrote:
> I don't know whether this will have negative side effects but from my point
> of view it would be nice if the openssl package would do one of the
> following to properly solve this issue:
>
> 1) properly load certificates from /etc/ssl/certs
On 2022-09-11 07:25:47 [-0400], Jeremy Bicha wrote:
> Attached. Or you can use the 2 Salsa merge proposals.
I prefer the workflow where it is attached to the bug. This makes things
easier for me, especially while traveling.
Fell free to reschedule it to 0-day/now.
Have they been forwarded upstream
On 8 September 2022 11:44:16 UTC, Jeremy Bicha
wrote:
>To allow clamtk-gnome to continue working after the Nautilus 43
>transition which will begin soon, I am uploading an NMU with a delay
>of 5 days to fix this bug. Please let me know if I should speed up or
>slow down this upload.
>
>The NMU co
On 2022-09-02 17:02:38 [+0100], Adam D. Barratt wrote:
> Please go ahead, bearing in mind that the window for getting updates
> into 11.5 (and thus bullseye-updates prior to 11.5 being released)
> closes over this weekend.
just uploaded.
> Given that 11.5 is scheduled for a week tomorrow, would y
Package: ftp.debian.org
X-Debbugs-Cc: sebast...@breakpoint.cc
Severity: normal
havp is no longer work as of linux-image-* v5.15. This is not a Debian
thing but actually the relevant code has been removed from the linux
kernel. The whole explanation is in
https://bugs.debian.org/1017637
It
101 - 200 of 1684 matches
Mail list logo