Bug#1101232: libmicrohttpd: FTBFS: Wrong URI: `/one%0dtwo', line: 304

On Fri, Apr 11, 2025 at 08:50:34PM +0300, Evgeny Grin wrote: > Please use patch from upstream: > https://git.gnunet.org/libmicrohttpd.git/patch/?id=036f8fdec2802e48e2555b2caf381bb1c565ab82 Thanks, just uploaded. > See also: https://github.com/curl/curl/issues/17029 Noted, thanks. Cheers, Flo

Bug#1101232: Re: Bug#1101232: libmicrohttpd: FTBFS: Wrong URI: `/one%0dtwo', line: 304

Hello Samuel, On Sat, Mar 29, 2025 at 06:37:12PM +, Samuel Henrique wrote: > On Wed, 26 Mar 2025 at 15:19, Florian Ernst wrote: > > When I downgrade libcurl from 8.13.0~rc2-2 (as currently present in > > trixie/sid) to 8.12.1-3 (the last non-rc version present before) the >

Bug#1101232: libmicrohttpd: FTBFS: Wrong URI: `/one%0dtwo', line: 304

Control: tags -1 confirmed Control: forwarded -1 https://bugs.gnunet.org/view.php?id=9664 On Tue, Mar 25, 2025 at 12:10:59AM +, Santiago Vila wrote: > [...] > == >GNU libmicrohttpd 1.0.1: src/testcurl/test-suite.log >

Bug#1095360: nghttp2: FTBFS: Could not import extension rubydomain.rubydomain

Control: tags -1 patch On Fri, Feb 07, 2025 at 12:12:03PM +, Santiago Vila wrote: > [...] > sphinx-build -b html -d manual/doctrees . manual/html > Running Sphinx v8.1.3 > loading translations [en]... done > > Extension error: > Could not import extension rubydomain.rubydomain (exception: N

Bug#1099520: [Pkg-auth-maintainers] Bug#1099520: yubikey-manager-qt: ImportError: cannot import name '_PrepareUploadFailed' from 'ykman.otp' - Qt application is EOL and uses outdated ykman API

t too, so I too would like to keep it around, as long as it stays working and is useful. I'm going to upload a patched version in a minute. Best, Florian

Bug#1099553: xpdf: Fails to build with poppler 25.03

n xpdf in Debian. Prior to the switch to the xpopple upstream, many people contributed fixes, and when taking over maintenance I had no intention to monopolize that. Florian

Bug#1086478: kmymoney: kdiagram transition / Bug#1088984: kmymoney: KDE PIM transition

Hello everyone, just adding some notes before this package gets autoremoved due to these two RC bugs. On Thu, Oct 31, 2024 at 06:01:17AM +0100, Patrick Franz wrote: > We have updated kdiagram to version 3.0.1 in experimental. The biggest change > is the port from Qt 5 to Qt 6, i.e. kdiagram 3.0.1

Bug#1090126: pyte: FTBFS: ERROR: Invalid value `None` in intersphinx_mapping['http://docs.python.org/']. Expected a two-element tuple or list.

On Mon, Dec 30, 2024 at 01:22:09PM +0500, Andrey Rakhmatullin wrote: > On Mon, Dec 30, 2024 at 09:10:27AM +0100, Florian Ernst wrote: > > @debian-python: > > > > However, AFAIK intersphinx will download things from the internet during > > build, which is not allow

Bug#1090126: pyte: FTBFS: ERROR: Invalid value `None` in intersphinx_mapping['http://docs.python.org/']. Expected a two-element tuple or list.

Control: tags -1 upstream patch Control: forwarded -1 https://github.com/selectel/pyte/issues/191 Dear maintainer, [ adding a CC to debian-pyt...@lists.debian.org to solicit further input on best practices ] On Mon, Dec 16, 2024 at 01:47:05PM +, Santiago Vila wrote: > [...] > python3 -m sphi

Bug#1075188: libmpc: ftbfs with GCC-14

On Mon, Dec 23, 2024 at 03:50:33PM +0100, Florian Ernst wrote: > [...] > I will upload the resulting package to DELAYED/10. Please let me know if > I should delay the upload longer or cancel it altogether. Now dcut due to maintainer activity. Thanks for taking care. Cheers, Flo sign

Bug#1091118: device-tree-compiler: FTBFS: libfdt_wrap.c:5599:17: error: too few arguments to function ‘SWIG_Python_AppendOutput’

-1,3 +1,10 @@ +device-tree-compiler (1.7.2-0.1) unstable; urgency=medium + + * Non-maintainer upload. + * test build + + -- Florian Ernst Mon, 23 Dec 2024 16:28:43 +0100 + device-tree-compiler (1.7.0-2) unstable; urgency=medium * debian/patches/fix-tests-for-Python3.12.patch: new patch diff -N

Bug#1088037: Simple patch to fix Celementine FTBFS

Hello Thomas, On Sat, Dec 21, 2024 at 03:34:48PM +0100, Florian Ernst wrote: > @Thomas, are you going to work on this? If not, I could NMU as per the > attached debdiff. With that the package built fine locally, I'll attach > the build log for reference. I have now uploaded the

Bug#1037322: Librabbitmq : CVE-2023-35789

Hello again, On Thu, Dec 12, 2024 at 06:42:47PM +0100, Florian Ernst wrote: > By its very nature (cf. the detailed description as linked above), this > vulnerability cannot be fixed with a drop-in replacement while keeping > the current user interface: if credentials have been enter

Bug#1037322: Librabbitmq : CVE-2023-35789

Hello, the following is based on the publicly available information as present on / linked to from . On Mon, Dec 09, 2024 at 03:20:03PM +, P Tamil Selvam wrote: > We are currently using Debian Bookworm 12.8 and have identified a > vu

Bug#1086285: libplacebo: FTBFS: undefined reference to `glslang::TShader::setStrings(char const* const*, int)'

Control: tags -1 upstream fixed-upstream patch Control: forwarded -1 https://code.videolan.org/videolan/libplacebo/-/merge_requests/685 thanks On Tue, Oct 29, 2024 at 07:46:55PM +0100, Santiago Vila wrote: > [...] > FAILED: src/libplacebo.so.349 > c++ -o src/libplacebo.so.349 > src/libplacebo.s

Bug#1088037: clementine: FTBFS: error: ‘’ may be used uninitialized [-Werror=maybe-uninitialized]

On Fri, Nov 22, 2024 at 02:05:23PM +0100, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: > [...] > /usr/include/c++/14/bits/invoke.h:74:46: error: ‘’ may be used > uninitialized [-Werror=maybe-uninitialized] FWIW, on my local system the build fa

Bug#1075322: nspr: ftbfs with GCC-14

On Wed, Jul 03, 2024 at 12:38:08PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. > [...] I just confirmed

Bug#1075590: tuxpaint: ftbfs with GCC-14

On Sun, Oct 06, 2024 at 06:04:49PM +0200, Florian Ernst wrote: > [...] > So, not only is "-lm" missing, but now there is a bunch of additional > libraries (Gnome?) present that wasn't there before, for whatever > reason. H. In May 2023 upstream already decided t

Bug#1075590: tuxpaint: ftbfs with GCC-14

On Sun, Oct 06, 2024 at 02:31:48PM +0200, Chris Hofstaedtler wrote: > On Sun, Aug 11, 2024 at 01:35:34PM +0200, Florian Ernst wrote: > > With the attached minimized patch this tuxpaint version compiles again > > with gcc-14. It seems this was first fixed upstream in 0.9.29,

Bug#1075109: kbd: ftbfs with GCC-14

Control: tags -1 upstream fixed-upstream patch On Sun, Aug 18, 2024 at 01:58:12AM +0200, Andreas Henriksson wrote: > forwarded 1075109 https://github.com/legionus/kbd/pull/119 Just confirmed: this patch fixes the FTBFS. It was already merged upstream. Thus now tagging accordingly. Cheers, Flo

Bug#1074915: discount: ftbfs with GCC-14

Control: tags -1 patch On Wed, Jul 03, 2024 at 12:25:19PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Bug#1075157: libcddb: ftbfs with GCC-14

Control: tags -1 patch On Wed, Jul 03, 2024 at 12:32:51PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Bug#1075188: libmpc: ftbfs with GCC-14

Control: tag -1 patch On Wed, Jul 03, 2024 at 12:33:50PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Bug#1075269: mhash: ftbfs with GCC-14

Control: tag -1 patch On Wed, Jul 03, 2024 at 12:36:24PM +, Matthias Klose wrote: > [...] > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will be raised before the trixie release. >

Bug#1075590: tuxpaint: ftbfs with GCC-14

Control: tags -1 upstream fixed-upstream patch On Wed, Jul 03, 2024 at 12:46:36PM +, Matthias Klose wrote: > [...] > src/tuxpaint.c: In function ‘do_new_dialog’: > src/tuxpaint.c:22025:54: error: passing argument 3 of > ‘autoscale_copy_smear_free’ from incompatible pointer type > [-Wincompat

Bug#1075586: trickle: ftbfs with GCC-14

Control: tag 1075586 patch Control: forwarded 1075586 https://github.com/mariusae/trickle/issues/34#issuecomment-2134139388 On Wed, Jul 03, 2024 at 12:46:27PM +, Matthias Klose wrote: > [...] > xdr.c: In function ‘xdr_msg’: > xdr.c:106:32: error: passing argument 5 of ‘xdr_union’ from incompa

Bug#1072366: libndp: CVE-2024-5564

On Thu, Jun 13, 2024 at 08:17:41PM +0200, Moritz Muehlenhoff wrote: > Thanks, these look good! Please upload to security-master, I'll take care > of the DSA over the weekend. Thanks for verifying, thus just uploaded to security-master. And thanks in advance for taking care of the DSA. Cheers, Flo

Bug#1072366: libndp: CVE-2024-5564

w.debian.org/doc/manuals/developers-reference/pkgs.html#uploading-the-fixed-package> I didn't directly upload them to the security upload queue as I was still unsure whether they exactly meet the Debian Security Team's requirements, so instead I just placed them in <https://people.debian.or

Bug#1072366: libndp: CVE-2024-5564

Dear Security Team, On Sat, Jun 01, 2024 at 04:57:53PM +0200, Salvatore Bonaccorso wrote: > [...] > [0] https://security-tracker.debian.org/tracker/CVE-2024-5564 > https://www.cve.org/CVERecord?id=CVE-2024-5564 An updated package containing upstream's fix has just been uploaded and is waiting

Bug#1071321: tagging 1071321

Following up on this: On Sun, May 26, 2024 at 11:42:56AM +0200, Florian Ernst wrote: > On Sun, May 26, 2024 at 10:54:21AM +0200, Christoph Biedl wrote: > > Étienne Mollier wrote... > > > If that helps, the symbols strlcat and strlcpy have been added > > > to the glibc 2

Bug#1071321: marked as done (libdumbnet: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file)

Hello Bastian, thanks for taking care and fixing this speedily. However, I am wondering whether there was a particular need to speed up fixing this bug that I might have missed and that might need to have been added to the bug for further consideration / clarification. After all I, as the mainta

Bug#1071321: tagging 1071321

Hello everyone, On Sun, May 26, 2024 at 10:54:21AM +0200, Christoph Biedl wrote: > Étienne Mollier wrote... > > If that helps, the symbols strlcat and strlcpy have been added > > to the glibc 2.38, so I believe it should be safe to remove the > > following symbols without soname bump: > > Just ca

Bug#1066113: guix: CVE-2024-27297

in “guix shell -CW” container isolation, there is risk. Regards, Florian

Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

Control: tag 1063361 + bookworm On Sat, Feb 10, 2024 at 03:49:45PM +0100, wrote: > Control: found 1063361 470.223.02-2~deb12u1 > [...] > Thus now marking this bug accordingly. Not quite, but hopefully now. FWIW, manually adding 0035-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch[0] fixes the buil

Bug#1063361: nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux

Control: found 1063361 470.223.02-2~deb12u1 On Tue, Feb 06, 2024 at 09:18:15PM +0100, Paul Gevers wrote: > Source: nvidia-graphics-drivers-tesla-470 > Version: 470.223.02-3 > Severity: serious > X-Debbugs-CC: li...@packages.debian.org > Tags: sid trixie > User: debian...@lists.debian.org > Usertag

Bug#1060698: [Pkg-auth-maintainers] Bug#1060698: Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.

pare an upload that includes your patch and will close #1060698 now. Florian

Bug#1060698: [Pkg-auth-maintainers] Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.

Hi Sébastien, On Sat, Jan 13, 2024 at 01:34:44PM +0100, Sébastien Noel wrote: > On Sat, 13 Jan 2024 11:26:50 +0100 Florian Schlichting > wrote: > > > > [...] > > While it might be possible to patch py/yubikey.py to work with the > > interface changes in current py

Bug#1060698: [Pkg-auth-maintainers] Bug#1060698: yubioath-desktop: Doesn't see yubikeys anymore.

t too comfortable (yet) with Debian policies. I fear this means the end of yubioath-desktop in Debian, as long as flutter isn't packaged (see #931793). The "legacy" branch on Github doesn't seem to have received any commits since the release of version 6.0.0. While it might be possible to patch py/yubikey.py to work with the interface changes in current python3-ykman, I doubt this is a sensible thing to do if upstream has decided to abandon the QT version. Florian

Bug#1052899: closing 1052899

close 1052899 thanks python-fido2 1.1.2-2 uploaded to unstable, closing.

Bug#1060266: [Pkg-auth-maintainers] Some help for coordinated uploads needed

n-fido2 to unstable in the course of this weekend? Do you want to do that yourself, so you can update solo1-cli at the same time, or are you ok with me going ahead and you follow with solo1-cli whenever convenient? Best, Florian

Bug#1051592: Regression: Commit "netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID" breaks ruleset loading in linux-stable

Timo Sigurdsson wrote: > > Linux regression tracking (Thorsten Leemhuis) > > wrote: > >> On 12.09.23 00:57, Pablo Neira Ayuso wrote: > >> > Userspace nftables v1.0.6 generates incorrect bytecode that hits a new > >> > kernel check that rejects adding rules to bound chains. The incorrect > >> > by

Bug#1051592: Regression: Commit "netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID" breaks ruleset loading in linux-stable

Linux regression tracking (Thorsten Leemhuis) wrote: > On 12.09.23 00:57, Pablo Neira Ayuso wrote: > > Userspace nftables v1.0.6 generates incorrect bytecode that hits a new > > kernel check that rejects adding rules to bound chains. The incorrect > > bytecode adds the chain binding, attach it to

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

Control: severity ! important On Fri, Apr 21, 2023 at 03:24:25PM +0200, Geoffroy Youri Berret wrote: > Le 11/04/2023 à 23:52, Florian Schlichting a écrit : > > […] > > I think we should take a step back and think about how a freshly > > installed mpd package should look

Bug#1034236: mpd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

? Also in the --user case?) Florian Am 11. April 2023 21:01:02 MESZ schrieb Geoffroy Youri Berret : >On 4/11/23 17:57, Max Kellermann wrote: >> On 2023/04/11 17:40, Andreas Henriksson wrote: >>> I think 2 is better myself and I'm attaching a proof of concept >>>

Bug#1004285: [DAViCal-devel] Bug#1004285: fixed in davical 1.1.11-1

issues/171 The important bit is to make sure that update-davical-database is run from the new package, and that it has replaced the expand_memberships function to not contain a CASE statement any more. Florian

Bug#1014506: slurm-wlm: flaky autopkgtest: sbatch fails without

Control: affects 1014506 src:libyaml On Thu, Jul 07, 2022 at 11:22:44AM +0200, Paul Gevers wrote: > [...] > I looked at the results of the autopkgtest of you package on armhf because > it was showing up as a regression for the upload of perl. I noticed that the > test regularly fails and I saw fai

Bug#1012587: [Pkg-auth-maintainers] Bug#1012587: /usr/share/doc/yubikey-manager empty

prior-version set to 4.0.8-1~, and keep that until after the bookworm release, no? Florian

Bug#1008312: clementine: diff for NMU version 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1

On Thu, Apr 14, 2022 at 06:23:53PM +0200, Florian Ernst wrote: > Please note that this bug also affects current stable, i.e. bullseye, and > should be fixed there as well, as per > <https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable>. JFTR, this will no

Bug#1008312: clementine: diff for NMU version 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1

@ -1,3 +1,10 @@ +clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add explicit Depends on libqt5sql5-sqlite (Closes: #1008312) + + -- Florian Ernst Thu, 14 Apr 2022 18:00:57 +0200 + clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-

Bug#1008687: FTBFS: as-test_pool FAIL killed by signal 6 SIGABRT

Hello Matthias, On Mon, Apr 11, 2022 at 11:14:41AM +0200, Matthias Klumpp wrote: > I'll likely downgrade this bug, but this is fairly odd! If the tests > fail on some building machines, there is a chance that the actual > application also doesn't work everywhere. I can say though that this > works

Bug#1008687: FTBFS: as-test_pool FAIL killed by signal 6 SIGABRT

Hello Matthias, thank you for your reply and for the appstream update. On Sun, Apr 10, 2022 at 11:08:40PM +0200, Matthias Klumpp wrote: > Am Mi., 30. März 2022 um 20:21 Uhr schrieb Florian Ernst > : > > during a rebuild of the reverse b-d of libyaml I found that this package > &g

Bug#1008312: clementine doesn't start

Hello scorpion2185, thanks for your report. Please bear with me, as I am not the package maintainer but just stumbled over this report. On Sat, Mar 26, 2022 at 05:55:26PM +0100, realroot wrote: > clementine doesn't start: > > - > clementine > 17:53:14.456 WARN unknown

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

eally1.20.2/debian/changelog --- kubernetes-1.20.5+really1.20.2/debian/changelog 2021-06-13 09:08:18.0 +0200 +++ kubernetes-1.20.5+really1.20.2/debian/changelog 2022-04-02 16:49:13.0 +0200 @@ -1,3 +1,10 @@ +kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium + + * Non-m

Bug#1000980: kubernetes: diff for NMU version 1.20.5+really1.20.2-1.1

o find attached the local build log. Best regards, Flo diff -Nru kubernetes-1.20.5+really1.20.2/debian/changelog kubernetes-1.20.5+really1.20.2/debian/changelog --- kubernetes-1.20.5+really1.20.2/debian/changelog 2021-06-13 09:08:18.0 +0200 +++ kubernetes-1.20.5+really1.20.2/debian/change

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

JFTR: On Wed, Mar 30, 2022 at 10:00:26PM +0200, Florian Ernst wrote: > libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev > anymore, and as such this package here is now uninstallable due to a > Depends on it. [...] Some more background can be found

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

Package: libprelude-dev Version: 5.2.0-5+b2 Severity: grave Justification: renders package unusable Hello there, libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev anymore, and as such this package here is now uninstallable due to a Depends on it. For reference, libtool migr

Bug#1004285: Fwd: Re: [DAViCal-devel] Bug#1004285: Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"

Hi Benno, I just realized this email didn't reach the Debian BTS and may not have reached you. It's probably best to keep both the bug (and thus davical-devel) in Cc. Florian - Forwarded message from Andrew Ruthven - From: Andrew Ruthven To: davical-de...@lists.sourceforg

Bug#1004285: [DAViCal-devel] Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"

he exact place in the code where the fatal error occurred, as well as the PHP error message. Florian

Bug#1005449: [DAViCal-devel] Bug#1005449: awl: FTBFS: sh: 1: error: Problems running dot: exit code=127, command='dot', arguments='"/<>/docs/api/inherit_graph_10.dot" -Tpng -o "/<

On Sun, Feb 13, 2022 at 08:00:15AM +0100, Lucas Nussbaum wrote: > Source: awl > Version: 0.62-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220212 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your packag

Bug#984114: liblastfm: diff for NMU version 1.0.9-1.2

Hello Stefan, On Sun, Feb 13, 2022 at 11:30:07AM +, Stefan Ahlers wrote: > I apologize for the very long delay. Thank you for preparing an NMU. Due to > my private situation I'm unable to continue maintaining this package. > Therefore, where is no reason to delay the upload any longer. Thanks

Bug#984114: liblastfm: diff for NMU version 1.0.9-1.2

tream PR. (Closes: #984114) + + -- Florian Ernst Sun, 13 Feb 2022 08:04:58 +0100 + liblastfm (1.0.9-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch --- liblastfm-1.0.9/d

Bug#1002192: kitinerary: FTBFS: 12: QWARN : ExtractorScriptEngineTest::testInfiniteLoop() org.kde.kitinerary: JS ERROR: [qrc://buggy.js]:0: Error: Interrupted

tags 1002192 patch thanks On Tue, Dec 21, 2021 at 05:02:35PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > [...] > > test 29 > > Start 29: calendarhandlertest > > > > 29: Test command: > > /<>/obj-x86_64-linux-gnu/bin/cal

Bug#984114: liblastfm: ftbfs with GCC-11

d it again. This is referenced in https://github.com/lastfm/liblastfm/issues/39 from where I extracted the patch. HTH, and please feel free to adjust to your liking. Cheers, Florian diff -Nru liblastfm-1.0.9/debian/changelog liblastfm-1.0.9/debian/changelog --- liblastfm-1.0.9/debian/changelog20

Bug#984014: clementine: ftbfs with GCC-11

bug, but with the attached debdiff implementing the fix from upstream I was able to build it again. HTH, and please feel free to adjust to your liking. Cheers, Florian diff -Nru clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/de

Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'

build + python3-installer to > build > Python modules as wheels and then unpack the wheel. This is the new > interface used by modern Python packaging tools. (Closes: #984824) Could be, but it't not :) > Full entry (in cases something didn't look suspicious to me)

Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'

> deps = parse_pydep(self.impl, fn, bdep=self.bdep, **section_options) > > File "/usr/share/dh-python/dhpython/pydist.py", line 522, in parse_pydep > > for part in dependency.split(',')) > > AttributeError: 'NoneType' object has no at

Bug#1000339: Aw: Re: Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

I can only agree. Thanks for the effort, you guys!   Florian   Gesendet: Sonntag, 12. Dezember 2021 um 10:54 Uhr Von: "Nilesh Patra" An: "Andreas Tille" Cc: "Robert J. Hijmans" , "Debian R" , "Florian Detsch" , 1000...@bugs.debian.org Bet

Bug#1000339: Aw: Re: Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

changes introduces to satellite with https://github.com/environmentalinformatics-marburg/satellite/commit/08837e9a04ae7bdb481d3ca0342fb3c9b81be891 weren't enough.. any ideas?   Thanks,  Florian   sessionInfo():   R version 4.1.2 (2021-11-01) Platform: x86_64-pc-linux-gnu (64-bit) Ru

Bug#1000187: [Pkg-auth-maintainers] Bug#1000187: yubikey-manager: Exception when trying to add an oath account

out a valid format for the secret: $ echo '123456' | base64 MTIzNDU2Cg== $ ykman oath accounts add foo 'MTIzNDU2Cg==' $ echo $? 0 $ ykman oath accounts list foo Florian

Bug#887834: [Pkg-mpd-maintainers] Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid

'll do that. If you want me to run (some) tests, I can do that too. 0.23.4. which I'm uploading to unstable just now should properly fix this issue (even without the need to comment out pid_file). Florian

Bug#887834: [Pkg-mpd-maintainers] Bug#887834: Bug#887834: Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid

fied"). Why is that, given that sndiod is not installed? Does libsndio7.0 perhaps mis-detect some pluseaudio compatibility devices, do we need to configure a default output (alsa?) in /etc/mpd.conf so that things work out of the box? Florian

Bug#887834: [Pkg-mpd-maintainers] Bug#887834: Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid

;s broken from an upstream perspective as well, and only works when running mpd as user. I suppose the best way forward is to specify User=mpd and Group=audio in the system unit, however this immediately hits a snag when mpd tries to open its log file /var/log/mpd/mpd.log, which up to now is created as root. This we could probably work around in Debian, and defaulting to log to syslog/journal also feels sensible, but I'm not sure if there may be other things that mpd might want to be root for when starting up as a system service? Florian

Bug#998156: contains non-DFSG-free files

* Henry Cejtin: > (I assume you meant ml-nlffigen.) ml-nlffigen is part of SML/NJ, not > part of MLton. /usr/bin/mlnlffigen is part of mlton-tools. I believe the code generation requirements are different for MLton and SML/NJ.

Bug#998156: contains non-DFSG-free files

* Henry Cejtin: > As far as I know, the ckit stuff is just included because it needed > some tweaks to work under MLton. > I don't think that any of "our" stuff depends on it. I think mlnffigen needs ckit.

Bug#993162: libc6: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL

uting it. Anyway this shows that the problem is in libgcc-s1, I am > therefore reassigning the bug. Correct, CET uses long NOPs, which are not supported by some x86 CPUs and trap on them. Thanks, Florian

Bug#900821: workaround confirmed

Hi all, we were experiencing this bug in a debian 10.4 docker container (FROM php:apache) it only happens with plain http not with https. I can confirm that workaround from Stefan Fritsch by turning EnableMMAP off is working for us! Cheers, Florian

Bug#955552: marked as pending in xpdf

Control: tag -1 pending Hello, Bug #92 in xpdf 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: https://salsa.debian.org/debian/xpdf/-/commit/215057b1f8088fe263053f774b1013f048be50f6

Bug#938858: marked as pending in xxdiff

Control: tag -1 pending Hello, Bug #938858 in xxdiff 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: https://salsa.debian.org/debian/xxdiff/-/commit/c818272bbd1d3d637e856d28e5261ab7bfa4

Bug#938858: xxdiff: Python2 removal in sid/bullseye

On Wed, Nov 25, 2020 at 05:06:29PM +0100, Matthias Klose wrote: > On 11/25/20 4:54 PM, Florian Schlichting wrote: > > I considered simply dropping the xxdiff-scripts package, but as the > > Python2 interpreter seems to stay around for the bullseye release, I > > think it is i

Bug#938858: xxdiff: Python2 removal in sid/bullseye

x27;m lowering the severity of this bug. I've uploaded a modified xxdiff that does not depend on the python package or the existence of /usr/bin/python. Florian

Bug#967140: [Pkg-mpd-maintainers] Bug#967140: gmpc-plugins: Unversioned Python removal in sid/bullseye

#x27;t find any relationship between gmpc-plugins and Python 2. Is this a > false positive, or is there some dependency that I'm missing? I suspect this got mixed up with the GTK 2 deprecation? Lowering severity so that gmpc-plugins can re-enter testing. Florian

Bug#975219: [Debichem-devel] Bug#975219: elkcode: FTBFS: internal compiler error: in lookup_field_for_decl, at tree-nested.c:288

* Lucas Nussbaum: > Hi Michael, > > On 22/11/20 at 15:32 +0100, Michael Banck wrote: >> Hi Lucas, >> >> That looks like an ICE, shouldn't that be filed with gfortran? > > Usually my logic is: if there's only one similar failure, I file a bug > against the affected package, rather than against the

Bug#964815: it looks like dprof2calltree cannot be distributed with a GPL-2 work

* Nicholas D. Steeves: > Hi, > > Adrian Bunk writes: > >> On Fri, Jul 10, 2020 at 07:48:31PM -0400, Nicholas D Steeves wrote: >> >>> it would still not be DFSG-free, because it >>> fails the "desert island test" for snail mail. Were OmniTI Computer >>> Consulting would accept email, it would als

Bug#962653: [DAViCal-devel] Bug#962653: davical: diff for NMU version 1.1.9.3-1.1

expected future of his package, but I guess no answer is also an answer, and rst2pdf has no bearing at all on the functioning of davical. So thanks for going ahead with this. Florian > diff -Nru davical-1.1.9.3/debian/changelog davical-1.1.9.3/debian/changelog > --- davical-1.1.9.3/debian

Bug#942988: displaycal: Python2 removal in sid/bullseye

at SF is also that I'm going to move code repos. Too much going on atm. -- Florian Höch https://displaycal.net

Bug#954715: glibc: FTBFS: tests failed: signal/tst-minsigstksz-1 signal/tst-minsigstksz-2

* Lucas Nussbaum: > Source: glibc > Version: 2.30-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200322 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. >> FAIL: signal/tst-minsigstks

Bug#943173: Not in testing yet?

Hey Dmitry, On Thu, Feb 06, 2020 at 01:04:35PM +0300, Dmitry Shachnev wrote: > Hi Florian! > > On Thu, Feb 06, 2020 at 10:36:22AM +0100, Florian Bruhin wrote: > > Hey, > > > > It looks like 5.14.0-2 with the fix isn't in testing yet? See > > https:/

Bug#943173: Not in testing yet?

.9.0-1 is marked for autoremoval from testing on 2020-02-16 It (build-)depends on packages with these RC bugs: 943173: pyqt5webengine: Python2 removal in sid/bullseye Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://git

Bug#943042: gitso: Python2 removal in sid/bullseye

an definitely do the testing. > > I submitted a merge request on salsa: > https://salsa.debian.org/debian/gitso/merge_requests/2 > > Let me know if you run into any problems or have any comments. that was fast! In my testing, the package behaves just like the old version, so I'll prepare an upload in a minute. Thanks a TON! Florian

Bug#943042: gitso: Python2 removal in sid/bullseye

Hi Scott, > The package doesn't look all that complicated. I can take a stab at trying > to port it to Python 3. If I get it working, perhaps I can ask you to test > it? that would be awesome! I can definitely do the testing. Florian

Bug#943042: gitso: Python2 removal in sid/bullseye

bullseye release, but the Python 2 removal seems to be progressing with a lot of energy lately... Florian

Bug#945911: APT leaks repository credentials

echanisms is good enough to conclude that there is no reliable defense against this attack in any of the scenarios I described, let alone all of them.) > So far I see only very generic guess and maybe-ifs which are not > actionable and very much not a release critical bug – mostly because > I don't see an actual bug be described so far… Well, that is unfortunate!? > (also, it is a good idea /if/ you found a security problem to disclose it > more responsibly to the security teams involved so they can coordinate > fixes, patches and uploads. If you don't do that you are forcing the > hand of the involved people, which tends to cause more aggressive and > crisply responses as they are forced to deal with things NOW.) You are assuming that people who would exploit this sort of vulnerability don't know about it, which seems very unlikely given how blatantly obvious it is to anyone with such a background. Regards, Florian

Bug#945911: APT leaks repository credentials

> > The credentials to transmit for a request are selected not based on the > > host name specified in the sources.list, but rather based on the URI that > > is being requested. Thus, any repository server that APT ever makes an > > HTTP(S) request to can issue an HTTP redirect to any URI that poin

Bug#945911: APT leaks repository credentials

Package: apt Version: 1.8.2 Severity: critical APT now promotes using auth.conf to store repository credentials. Unfortunately, the way these credentials are handled causes a confused deputy style problem: The credentials to transmit for a request are selected not based on the host name specified

Bug#941414: certificates about to expire

u are seeing and share more details? Indeed, that seems to not be a problem with HTTP challenges, but it is with DNS challenges, if all the _acme_challenge names point to the same canonical name for the dynamically updated TXT record (as they do in my setup). Regards, Florian

Bug#941414: certificates about to expire

to actually be deployed, and thus the verification for the first host name to succeed. Then you just have to re-run dehydrated until all the host names have been verified. Regards, Florian

Bug#941414: certificates about to expire

about a week. Is there any plan to fix this bug before then, or will users have to work around this individually to avoid running into expired certificates? And if the latter, what is the recommended workaround? Is the current backports version usable? Regards, Florian

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

* Francesco Poli: > Hello everyone, > I am sorry to ask, but... I cannot understand what's the status of > [this bug report]. > > [this bug report]: > > A serious bug for libc6-dev without any apparent activity since last > March? Sure there must have been some hi

Bug#930484: e2fsck corrupts sparse files with -E bmap2extent

Package: e2fsprogs Version: 1.43.4-2 Severity: critical e2fsck potentially moves blocks around in sparse files when running with -E bmap2extent, in particular when the blocks are physically adjacent on the underlying block device, but have a hole in between in the file. This script reproduces the

Bug#921599: [debian-mysql] Bug#921599: mariadb-10.3: always connects to localhost ignoring host entry in option file

The changes from my merge request (same as https://github.com/MariaDB/mariadb-connector-c/pull/101) are not included in the mariadb-10.3 1:10.3.14-1 source, and testing shows that a hostname set through my.cnf is ignored. Florian

  1   2   3   4   5   6   7   8   9   10   >