Bug#1023697: wolfSSL 5.5.4 uploaded

Hi, > there is considerable interest in using WolfSSL I uploaded version 5.5.4-1, which was released last week, to the archive. Kind regards Felix Lechner

Bug#1023697: Keep out of testing

tacted for guidance via IRC. Kind regards Felix Lechner [1] https://bugs.debian.org/1025789 cc: Security Team

Bug#1023697: Keep out of testing

Hi, On Tue, Nov 8, 2022 at 12:00 PM Moritz Muehlenhoff wrote: > > open security issues I also just uploaded a backport for bullseye. Kind regards, Felix Lechner

Bug#1023835: wolfssl: FTBFS because of amd64-only symbols in symbols file

ot;optional" please? Thanks! Kind regards, Felix Lechner

Bug#1023697: Version 5.5.3-1 is in the NEW queue

Hi, FWIW, version 5.5.3-1 was accepted into the NEW queue. Kind regards Felix Lechner

Bug#1023697: Keep out of testing

Hi, On Tue, Nov 8, 2022 at 12:00 PM Moritz Muehlenhoff wrote: > > wolfssl has no active maintainer, plenty of open security issues and we > already > have too many TLS libraries in our releases. Keep it out of testing. I'm going > to file bugs against the handful of reverse deps. Sorry, I have

Bug#1021021: Upload planned

Hi, I plan to upload version 5.5.1 in the near future. Kind regards Felix Lechner

Bug#1010703: haskell-hashable: FTBFS on i386: unrecognized 'configure' option `-D_FILE_OFFSET_BITS=64'

le arguments # with their own quoting so run through a shell expansion my $ghc_configure_args = run_quiet( qw{sh -c}, 'echo -n ' . $DOUBLE_QUOTE . ($ENV{DEB_SETUP_GHC_CONFIGURE_ARGS} // $EMPTY) . $DOUBLE_QUOTE ); Kind regards, Felix Lechn

Bug#1000234: marked as pending in lintian

Control: tag -1 pending Hello, Bug #1000234 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1000476: lintian: autopkgtest regression: autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t

tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t That test was adjusted for recent versions of Binutils. [2] Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/lintian/-/commit/deba665363a3dd4da8b806df07091c9c482206d7 [2] https://salsa.d

Bug#995492: lintian: Broken --fails-on=none as default never got reverted

Hi Guillem, On Fri, Oct 1, 2021 at 6:57 PM Guillem Jover wrote: > > Unamused, I am sorry that happened. Did I not accept your patch in full? [1] Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/lintian/-/commit/3758bfafd5dd742c327f2312dac8e3a71b1f036e

Bug#995216: simple-scan: B Text scans saved as gibberish

when I wrote). The bug is also somewhat treacherous: The image on the screen looks fine. One has to open the saved file to see the issue. Thanks for simple-scan! It's a great and best-in-class program! Kind regards Felix Lechner [1] https://www.debian.org/Bugs/Developer#severities

Bug#995215: postgresql-semver: Wait for acceptance of backport

Package: postgresql-semver Severity: serious The sole purpose of this bug is to keep version 0.31.1-3 out of testing until version 0.31.1-2~bpo11+1 is in backports.

Bug#993955: marked as pending in lintian

Control: tag -1 pending Hello, Bug #993955 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#993651: marked as pending in lintian

Control: tag -1 pending Hello, Bug #993651 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#982459:

Debian unstable. Feel free to try that too. Thank you! Kind regards Felix Lechner

Bug#982459: mdadm --examine in chroot without /proc,/dev,/sys mounted corrupts host's filesystem

https://packages.debian.org/source/experimental/mdadm Kind regards Felix Lechner

Bug#985468: Please cherry-pick 7d2222cf from upstream for bullseye

he program for everyone else. I used the 'serious' level—normally only available to the maintainer—to bring the bug to the attention of the release team, who recommended this filing. Below is a debdiff for the resulting sources, in addition to the patch. Thanks for taking a look! Kind regards Felix L

Bug#984716: gocryptfs: data loos upon full root file system

e reasons, I am downgrading this report to the highest non-RC level—at least until bullseye is released. Kind regards Felix Lechner

Bug#962921: Please fix spam for bullseye

Dear maintainer, The release team will accept this patch for bullseye. They raised the bug status to "serious" after I asked on your behalf. Please upload a patched version and ask for unblocking in a bug against release.d.o. Thanks for your contributions to Debian! Kind regards Felix Lechner

Bug#984554: libnginx-mod-stream-geoip: ngx_stream_geoip_module.so: undefined symbol: ngx_stream_add_variable

The following thread is more recent and describes the same phenomenon: https://github.com/oerdnj/deb.sury.org/issues/1437#issuecomment-734722970

Bug#984554: [SOLVED] Bug#984554: libnginx-mod-stream-geoip: ngx_stream_geoip_module.so: undefined symbol: ngx_stream_add_variable

/mod-stream.conf 50-mod-stream.conf Hope that helps! Kind regards Felix Lechner [1] http://mailman.nginx.org/pipermail/nginx/2016-July/051323.html

Bug#984554: libnginx-mod-stream-geoip: ngx_stream_geoip_module.so: undefined symbol: ngx_stream_add_variable

034 ("nginx: improve dependency of dynamic modules") but on first glance that did not look related. For more detailed messages from 'apt -t bullseye dist-upgrade', please see below. Thank you! Kind regards Felix Lechner * * * dpkg: dependency problems prevent configuration of nginx: nginx de

Bug#962844: marked as pending in mdadm

Control: tag -1 pending Hello, Bug #962844 in mdadm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs

Hi Chris, On Sun, Feb 7, 2021 at 9:22 AM Chris Hofstaedtler wrote: > > friendly ping here, are you planning to fix this for bullseye? Thanks for the reminder! I will probably include efivars in the next couple of days. Kind regards Felix

Bug#979534: wolfssl: CVE-2020-36177

apply, or apply only partially, because we are changing the way the sources are repackaged. Kind regards Felix Lechner

Bug#977594: liblist-moreutils-perl: autopkgtest regressions, breaks lintian

ebian.org/lintian/lintian/-/blob/2.104.0/checks/fields/package-relations.pm#L129 That code was likewise replaced for unrelated reasons, and is no longer available in Lintian. Kind regards Felix Lechner

Bug#974829: marked as pending in mdadm

Control: tag -1 pending Hello, Bug #974829 in mdadm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#970896: lintian times out while analyzing package

from your failed job in Salsa. Perhaps it had something to do with the fact that you were building for bionic, a Ubuntu codename. Meanwhile, I downgraded the severity of this bug. Kind regards, Felix Lechner * * * [/l/l/l/git]─[⎇ master]─[+]|> bin/lintian /mirror/debian/pool/main

Bug#969663: polyphone is marked for autoremoval from testing

wolfssl_4.5.0+dfsg-1_source.buildinfo > > Greetings, > > Your Debian queue daemon (running on host usper.debian.org) Kind regards Felix Lechner

Bug#969663: polyphone is marked for autoremoval from testing

Hi Thorsten, > Is there anything I can help to ensure it’s not autoremoved? I just saw it this morning and plan to upload 4.5.0 later today. From what I understand, closing #969663 should postpone the autoremoval process? Kind regards Felix

Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs

suggests that some people use IMSM arrays in legacy BIOS mode. Does mdadm support IMSM only when the system is booted in UEFI mode? Sorry that I do not know the answer to that question. I just assumed maintenance of mdadm and do not use IMSM. At this point, I am reading code. Thank you! Kind regards

Bug#964405: marked as pending in lintian

Control: tag -1 pending Hello, Bug #964405 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#964234: dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root

Hi Andreas, > dpkg-source: error: pathname > points outside source root Maybe the same as Bug#964111? Kind regards Felix Lechner

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

tor of cURL, works there. I see the developers from time to time and receive free support. The library has been in Debian for five years. Kind regards Felix Lechner [1] https://www.wolfssl.com/community/

Bug#962158: marked as pending in lintian

Control: tag -1 pending Hello, Bug #962158 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#962158: lintian: New very problematic --fail-on default value

e derivative ecosystem. Simon may receive feedback from Ubuntu, a significant derivative. If there are real problems, I am happy to discuss a solution that reverts the default to Lintian's old setting. Kind regards Felix Lechner

Bug#962158: lintian: Swapped exit statuses and --fail-on default value require downstream adjustments

explicit. And again, automated users already had to look at their scripts. It was the perfect timing to make both changes. Kind regards, Felix Lechner

Bug#961684: marked as pending in lintian

Control: tag -1 pending Hello, Bug #961684 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#956077: marked as pending in lintian

Control: tag -1 pending Hello, Bug #956077 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Hi Paul, On Sun, Mar 22, 2020 at 8:40 PM Paul Wise wrote: > > Will the new Perl tests be enabled by default? Well, that's what I did with xdeb, but it is causing #954415. My inclination is yes, although personal profiles will soon become very tweakable. Kind regards Felix Lechner

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

Kind regards Felix Lechner

Bug#954761: lintian: crashes with: coercion for "original_severity" failed: Unknown tag severity serious

e how to best close this bug. Maybe 'forcemerge'? Kind regards Felix Lechner

Bug#954331: Please adjust tag severities

led at > /usr/share The meaning of the Severity field in tag declarations has changed. Please modify the tags in pkg-perl-tools accordingly. For details, please see #935706 or this and the surrounding commits: https://salsa.debian.org/lintian/lintian/-/commit/e1e12f7f4190ab5718e2317dd7e466d8b56d6043 Kind regards Felix Lechner

Bug#949066: marked as pending in lintian

Control: tag -1 pending Hello, Bug #949066 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#949066: lintian: testsuite failures on arm*

Hi Gianfranco, On Fri, Jan 24, 2020 at 8:39 AM Gianfranco Costamagna wrote: > > Felix gentle ping please? > (in Ubuntu I disabled that test BTW and the result package autopkgtestsuite > was green on all archs) The release took place solely to facilitate upgrading lintian.d.o, which has been

Bug#949066: lintian: testsuite failures on arm*

Hi Gianfranco, On Thu, Jan 16, 2020 at 8:26 AM Gianfranco Costamagna wrote: > > Hello, looks like tests regressed on arm64 and armhf Thanks for pointing this out. It is a result of splitting the build and test specifications. The best thing is probably to restrict the building of affected tests

Bug#946396: Missing fcrypt causes Lintian test failure

Hi Aurelien, On Sun, Dec 8, 2019 at 3:08 PM Aurelien Jarno wrote: > > Hi, > > On 2019-12-07 13:42, Felix Lechner wrote: > > Hi, > > > > Starting in `libc6 2.29-5`, the Lintian test > > `t/tags/checks/binaries/binaries-obsolete-des` fails in `unstable`: >

Bug#945299: lintian: ignores all but last override of a tag

Fixed in: https://salsa.debian.org/lintian/lintian/commit/cbf3f6487b19d16a99e8582e24ddc2817a5487ac Kind regards, Felix Lechner

Bug#945299: marked as pending in lintian

Control: tag -1 pending Hello, Bug #945299 in lintian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

closed. The BTS never switched to pending, presumably due to the version restriction via 'found'. Or, do I need to backport the patch to that specific version? Kind regards, Felix Lechner

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

Christoph should speak up. >From my perspective no action is required. Kind regards, Felix Lechner

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

. Kind regards, Felix Lechner On Thu, Nov 7, 2019 at 11:34 AM Adam D. Barratt wrote: > > On Thu, 2019-11-07 at 10:49 -0800, Felix Lechner wrote: > > Also, as a side note, would someone please explain why someone still > > on stretch would need lintian? I am personally on stable, bu

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

e explain why someone still on stretch would need lintian? I am personally on stable, but most package maintainers out there seem to track testing or the bleeding edge, unstable. Kind regards, Felix Lechner

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

bian.org/cgi-bin/bugreport.cgi?bug=943910#25 Kind regards, Felix Lechner CC: Andreas Beckmann

Bug#942252: lintian: No vendor given at /<>/lib/Lintian/Maintainer.pm line 33

h version Lintian do you have installed? Kind regards, Felix Lechner

Bug#918952: Bug#929468: wolfssl: NMU for wolfssl 4.1.0.

Hi Paul, On Wed, Sep 11, 2019 at 6:12 AM Ying-Chun Liu (PaulLiu) wrote: > > I'm maintaining telegram-cli. I'm using wolfssl because telegram-cli is > GPL. > > They are using openssl but it is actually violates the GPL license. So I > tried to build telegram-cli with wolfssl and it just works

Bug#918952: Bug#929468: wolfssl: NMU for wolfssl 4.1.0.

Hi Paul, I am the maintainer of this library package. Are you aware of any packages that depend on it? Kind regards Felix

Bug#932000: In testing

On Wed, Jul 24, 2019 at 6:31 AM Benjamin Kaduk wrote: > > It's hard to come up with many scenarios in which they could be related. > The only remotely plausible one that comes to mind is if the idmapd is > somehow using a different keytab (or libkrb5) than the core NFS server, but > I don't

Bug#932000: In testing

On Tue, Jul 16, 2019 at 8:07 AM Greg Hudson wrote: > > Candidate patch here: Thank you. The update works great, although I now have problems with idmap not working on a kerberized NFSv4 mount. I write with hesitation. A week has passed and many other packages were likewise updated. My idmap

Bug#918817: lintian: Returns with exit code of 0 (zero) on failed tests

Please see https://salsa.debian.org/lintian/lintian/merge_requests/121 although I cannot explain the exit code '2' right now.

Bug#917752: lintian: FTBFS: tests failed

This bug is fixed. It can be marked as pending when the merge requests for the two blocking bugs are accepted.

Bug#913930: Confirmed for sbuild only

in https://salsa.debian.org/lintian/lintian/merge_requests/114 Kind regards Felix Lechner

Bug#917844: Fixed

Hi, I did not see the separate report at first and commented on #917752. For a fix, please see: https://salsa.debian.org/lintian/lintian/merge_requests/113 Felix Lechner

Bug#917752: lintian: FTBFS: tests failed

On Sun, Dec 30, 2018 at 3:06 PM Chris Lamb wrote: > > > > -W: manpages-general: manpage-has-errors-from-man > > > usr/share/man/man1/test.1p.gz 14: warning: macro `dep' not defined > […] > > Like you, I have not seen this one. This test was not changed recently; > > neither was the associated

Bug#917752: lintian: FTBFS: tests failed

On Sun, Dec 30, 2018 at 3:06 PM Chris Lamb wrote: > > > > +I: changes-upstream-signature-not-missing source: > > > public-upstream-key-unusable upstream/signing-key.asc cannot be > > > processed > > > > This looks like #913930. I have only seen it in sbuild, but not otherwise. > >

Bug#917752: lintian: FTBFS: tests failed

Chris, On Sat, Dec 29, 2018 at 3:23 PM Chris Lamb wrote: > > > > +I: changes-upstream-signature-not-missing source: > public-upstream-key-unusable upstream/signing-key.asc cannot be processed > > Felix, not sure your MR/branch handles this one? > This looks like #913930. I have only seen it in

Bug#911403: Please always include a copyright notice in 'LicenseWithSummary::summary_or_text'

Hi Dominique, I am fine with your suggestion. We will wait for your implementation. Thank you for providing this package! Kind regards, Felix On Mon, Oct 29, 2018 at 9:44 AM Dominique Dumont wrote: > > On Monday, 29 October 2018 16:51:45 CET you wrote: > > I am happy to provide patches and

Bug#905614: Patch invalid

Control: tags 905614 - patch The owner of libsoftware-licensemoreutils would like to resolve the issue differently. (For details, please see #911403.) The patch I submitted earlier is outdated. Thank you! Kind regards, Felix

Bug#911403: Please always include a copyright notice in 'LicenseWithSummary::summary_or_text'

Hi Dominique, I am happy to provide patches and merge requests that implement your idea, but are you sure there are other meaningful consumers of the summary_or_text method? Your posting [1] restricts uses to Debian, and a search on codesearch.debian.net shows no other packages that rely on the

Bug#905614: Patch

! Kind regards, Felix Lechner remove-duplicate-copyright-notice.patch.xz Description: application/xz

Bug#906466: Upload pending

Control: severity 906466 normal Hi, A pending upload is expected to resolve this bug report. To prevent auto removal, I am downgrading the severity to normal. Thank you! Felix Lechner

Bug#904711: On Mentors

Hi, I am waiting for a sponsor to upload the fixed version. If you are in a hurry, please build from Mentors (https://mentors.debian.net/package/wolfssl). Thank you!

Bug#888587: Revert to Arch:all

Package: golang-github-rfjakob-eme Version: 1.1-2 Severity: serious For a brief time, the package is being marked Arch:any to produce detailed logs. We would like to support additional release architectures, but the package is Golang source (and autopkgtest did not run on the affected

Bug#887952: Revert to Arch:all

Package: golang-github-jacobsa-crypto Version: 0.0_git2016.0.293ce0c+dfsg1-5 Severity: serious For a brief time, the package is being marked Arch:any to produce detailed logs. We would like to support additional release architectures, but the package is Golang source (and autopkgtest did not

Bug#853672: svxlink: diff for NMU version 15.11-2.1

Adrian, Thank you for doing this! Felix On Fri, Sep 1, 2017 at 6:20 AM, Adrian Bunk wrote: > Control: tags 853672 + pending > > Dear maintainer, > > I've prepared an NMU for svxlink (versioned as 15.11-2.1) and uploaded > it to DELAYED/10. Please feel free to tell me if I

Bug#860046: wolfssl: Incomplete debian/copyright?

Chris, Sorry about the oversight. Please find a new upload on Mentors, closing two bugs. Thank you! Best regards, Felix On Mon, Apr 10, 2017 at 10:13 AM, Chris Lamb wrote: > Source: wolfssl > Version: 3.10.2+dfsg-1 > Severity:

Bug#856114: wolfssl: CVE-2017-6076

ry for the late reply! > > On Sat, Feb 25, 2017 at 08:10:22AM -0800, Felix Lechner wrote: > > Hi Salvatore, > > > > Thank you for your email. I would like to package the new version but > > 3.10.2 was not signed on GitHub. (Upstream recently added those > signatures &

Bug#856114: wolfssl: CVE-2017-6076

Hi Salvatore, Thank you for your email. I would like to package the new version but 3.10.2 was not signed on GitHub. (Upstream recently added those signatures for us.) The more recent release actually fixes two additional vulnerabilities, with one being more serious. Details are in [0] and

Bug#793134: Packaging of newest upstream version in progress

Uploaded and pending in NEW. On Fri, Dec 2, 2016 at 12:11 AM, Nobuhiro Iwamatsu wrote: > Hi, > > > Newest version will be uploaded soon. Upstream is reviewing configured > > ciphers and options. > > ping? > > -- > Nobuhiro Iwamatsu >iwamatsu at {nigauri.org /

Bug#793134: Packaging of newest upstream version in progress

Newest version will be uploaded soon. Upstream is reviewing configured ciphers and options.

Bug#801265: Build problem has been fixed upstream

A recent upload to Mentors fixes this issue. It should be in the archive shortly. Should Britney remove the package from testing on Nov 5, you can still get it from unstable. Just download it from https://packages.debian.org or via apt. On Mon, Nov 2, 2015 at 2:25 PM, SM0SVX