Bug#1104721: ruff: ruff fails to run on Asahi Linux kernel (Apple M2) because jemalloc complains about page size

Package: python3-ruff Version: 0.0.291+dfsg1-4 Severity: serious Dear Maintainer, running ruff on my Debian/testing system based on the Asahi Linux kernel only gives me the following error messages: , | $ ruff | : Unsupported system page size | : Unsupported system page size | memory allocat

Bug#1081015: marked as pending in wcc

Control: tag -1 pending Hello, Bug #1081015 in wcc 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/pkg-security-team/wcc/-/commit/84aeb17b9c0c4a4eb8ff4392a06ecb

Bug#1094199: Sorting by dependencies is not sufficient to solve the problem

think that dependency sorting + cycle detection should be added to dh-rust so we can move on with other packaging tasks before the freeze. Cheers, -Hilko >From 6333c51012f134340a8544508dd9fd5266bf013a Mon Sep 17 00:00:00 2001 From: Hilko Bengen Date: Wed, 5 Feb 2025 22:48:26 +0100 Subject: [PAT

Bug#1094199: Sorting by dependencies is not sufficient to solve the problem

Hi, I tinkered around with dh-rust a bit tonight and implemented a function that tries to sort packages by dependencies rather than dependency count[1]. This solves the FTBFS issues for some packages, such as wasmtime, bounded-static. Unfortunately, the sort function hangs if there are dependency

Bug#1093743: marked as pending in plaso

Control: tag -1 pending Hello, Bug #1093743 in plaso 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/pkg-security-team/plaso/-/commit/d5ca0591c2d668bc01870915b9

Bug#1093743: marked as pending in plaso

Control: tag -1 pending Hello, Bug #1093743 in plaso 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/pkg-security-team/plaso/-/commit/d5ca0591c2d668bc01870915b9

Bug#1091572: hyperscan: FTBFS on i386: limex_exceptional.h:249:41: error: passing argument 1 of ‘findAndClearLSB_32’ from incompatible pointer type [-Wincompatible-pointer-types]

control: forwarded -1 https://github.com/intel/hyperscan/pull/439 I'm not 100% sure about my patch; put in a PR upstream at . Cheers, -Hilko

Bug#1088290: libc6: On mips64el, nbdkit --help segfaults in printf()

* Aurelien Jarno: > I have not time to look at the issue right now, but it appears that the > issue already exists in version 2.40-3. Marking it as such in the BTS so > that it doesn't prevent migration of 2.40-4 to testing. Yes, I can confern, the issue exists in 2.40-3 also. Can you give any h

Bug#1086351: Removal notice: obsolete

control: severity -1 normal control: retitle -1 Issues with the elm-compiler package Ilias, I was finally able to fix the FTBFS issue in elm-compiler today, even though I'll need more time for what I'd consider a proper fix. (Losing colored formatting for compiler error messages isn't an RC bug,

Bug#1082751: nbdkit --help segfault from within printf() on mips64el: libc bug?

control: fixed -1 1.40.4-4 I have disabled tests on mips64el for now. nbdkit is still going unusable on mips64el until the issue in glibc gets fixed, but in my opinion, it's not worth to let that keep nbdkit and reverse dependencies out of testing. Cheers, -Hilko

Bug#1088290: libc6: On mips64el, nbdkit --help segfaults in printf()

Package: libc6 Version: 2.40-4 Severity: serious Control: notfound -1 2.39-7 Dear Maintainer, in investigating the root cause for #1082751 I found that current nbdkit built on unstable/mips64el segfaults in printf() with libc6/2.40-4 – but not with 2.39. , | nbdkit [-4|--ipv4-only] [-6|--ipv

Bug#1082751: nbdkit --help segfault from within printf() on mips64el: libc bug?

* Petter Reinholdtsen: > [Hilko Bengen] >> Running nbdkit --help under gdb on the porterbox (eberlin) shows that >> the segfault happens inside libc's I/O code when called from printf: > > Did you try to run it under valgrind too? Not yet, but I was able to replicate

Bug#1082751: nbdkit --help segfault from within printf() on mips64el: libc bug?

control: tag -1 confirmed [CC'ing debian-mips@ in the hope that someone else can help in tracking the root cause down.] Running nbdkit --help under gdb on the porterbox (eberlin) shows that the segfault happens inside libc's I/O code when called from printf: , | Program received signal SIGSE

Bug#1086264: elm-compiler: FTBFS: Error: hlibrary.setup: Encountered missing or private dependencies: ansi-wl-pprint <1

control: tag -1 confirmed I can reproduce the issue. The "ansi-wl-pprint <1" dependency can no longer be satisfied. Once I remove the "<1", building starts, but it fails due to an API change. Will investigate further. Cheers, -Hilko

Bug#1086351: Removal notice: obsolete

* Ilias Tsitsimpis: > Source: elm-compiler > Version: 0.19.1-3 > Severity: serious > > I intend to remove this package: > > * It has no rev dependencies The compiler itself is considered stable upstream and I'd argue that the number of reverse dependencies is not necessarily a measure of its us

Bug#1079968: Should zeek-aux be removed from unstable?

Control: severity -1 normal Control: retitle -1 RM: zeek-aux -- RoM; rc-buggy Control: reassign -1 ftp.debian.org Control: affects -1 + src:zeek-aux * Helmut Grohne: > I suggest removing zeek-aux from Debian for the following reasons: I agree.

Bug#1071597: rust-laurel - autopkgtest failure on s390x

* Peter Green: > When preparing the upload of 0.6.2-1, Hilko once again > dropped the patch with a changelog entry of > "Drop unneeded patches". > > So that brings us to where we are now, the package > fails it's autopkgtests on s390x and I do not feel > it's appropriate to reinstate the patch for

Bug#1066831: nbd-server: Crash on -C /dev/null or -C /missing/file

Package: nbd-client Version: 1:3.26.1-1 Severity: serious Tags: patch X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, While investigating libnbd build failures (see ##1066766), I stumbled across a bug that makes nbd-server crash without an error message when trying to read its configuration

Bug#1061004: guestfs-tools: FTBFS: make[6]: *** [Makefile:1723: test-suite.log] Error 1

control: fixed -1 1.52.0-2

Bug#1037568: Ajust fixed versions

control: fixed -1 0.18.7-1~exp1

Bug#1000012: marked as pending in nmap

Control: tag -1 pending Hello, Bug #112 in nmap 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/pkg-security-team/nmap/-/commit/62ddf31c2f04c4ca8db04513da5d

Bug#1037541: libguestfs: FTBFS: supermin: error: lstat: Value too large for defined data type: /var/tmp/supermin2b73c8.tmpdir/base.d/init

* Sebastian Ramacher: > Source: libguestfs > Version: 1:1.50.1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org … and it also fails to build on armhf. Likely a 32bit-arch-specific issue. My gu

Bug#1036263: Package can be built just fine

Hi, At least as of 1.50.1-1, the pacakge builds just fine, cf. https://buildd.debian.org/status/fetch.php?pkg=guestfs-tools&arch=amd64&ver=1.50.1-1&stamp=1686585170&raw=0 Cheers, -Hilko

Bug#1030511: Apparent s390x kernel bug

Control: tags -1 + pending Control: block -1 by 1031753 The hangs manifest in qemu-img, but according to #1030545, the root cause seems to be an s390x-specific kernel bug which has been described in #1031753.

Bug#1031471: guestfs-tools: FTBFS: make[5]: *** [Makefile:1073: test-suite.log] Error 1

control: tag -1 confirmed I have been able to confirm the test failure in an unstable/amd64 schroot environment. Cheers, -Hilko

Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x

* Michael Tokarev: > 04.02.2023 23:19, Hilko Bengen wrote: >> Package: src:qemu >> Version: 1:7.2+dfsg-2 > .. >> qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 >> 512 >> would hang in what appears a tight loop (100% CPU). > &

Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x

Package: src:qemu Version: 1:7.2+dfsg-2 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, While investigating recent s390x build failures of libguestfs, I noticed that variants of qemu-img create -f qcow2 -o preallocation=metadata blank-disk-1s.qcow2 512 would hang in

Bug#1022352: lua-mode: FTBFS: tests failed

FTBFS confirmed with elpa-buttercup/1.26-{1,2,3}, tests work just fine using elpa-buttercup/1.24-1.

Bug#1021833: nbdkit: FTBFS: FAIL test-partitioning3.sh (exit status: 1)

control: block -1 by 1020446 The failing test is due to sgdisk misbehaving as documented in #1020446. Once the patch for #1020446 is applied, rebuilding the package should fix things. Cheers, -Hilko

Bug#1020005: nbdkit: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

control: tag -1 confirmed I can confirm that some curl-related test programs hang, both on an up-to-date sid/amd64 machine and within a sid/amd64 sbuild/schroot environment. Seems to be curl-related: Downgrading *curl* packages from 7.85.0-1 to 7.84.0-2 makes those problems disappear. Cheers, -H

Bug#1007962: sslsplit NMU: Bug #1007962: sslsplit FTBFS when only loopback interface is configured

* Timo Lindfors: > I hope it is ok to NMU this to get sslsplit back to Debian. If not, > please let me know! I'll wait wait for 10 days in case there are > comments from you, others in Debian or upstream. I also hope it is ok > to push these patches to salsa after the package has been uploaded. P

Bug#1019303: librm0: library mismatch between roger-router and librm0

control: reassign -1 roger-router

Bug#1019303: librm0: library mismatch between roger-router and librm0

control: severity -1 seriouos >* What led up to the situation? > Installing the new version of roger-router, which > started using libsoup3 instead of libsoup2 We'll have to port librm to libsoup-3.0, too. This is going to be … fun. Cheers, -Hilko

Bug#1017985: marked as pending in roger-router

Control: tag -1 pending Hello, Bug #1017985 in roger-router 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/roger-router/-/commit/1a547f9d1a353a35ec55425

Bug#1014795: libtorrent-rasterbar-dev: pkg-config --libs is wrong, leads to FTBFS, again.

Package: libtorrent-rasterbar-dev Version: 2.0.6-4 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, apparently the bug described (and fixed) in #1009875 has re-appeared in the most recent version. , | (sid-amd64)bengen@ataraxia: $ dpkg-query --show libtorrent-rasterbar-dev

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

I think I found the root cuase in boost1.74 – and reported it as #1014180. Please note that libtorrent-rasterbar has to be rebuilt for the change to take effect. (It might be a good idea to add a Built-Using line to debian/control.) Cheers, -Hilko

Bug#1014180: src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+

Source: boost1.74 Version: 1.74.0-16 Severity: grave Tags: patch, upstream X-Debbugs-Cc: Hilko Bengen Dear Maintainer, I recently received #1013470 (nbdkit FTBFS because of segfaults when running test suite); this turned out to be caused by #1013931 (segfault in libtorrent-rasterbar cleanup

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

* Christian Marillat: > Could you try this upstream patch ? > > https://github.com/arvidn/libtorrent/pull/6941 Perhaps I'm missing something … it seems to me that this patch is to be appplied onto version 1.2, not 2.0 – and the verrsion nbdkit was most recently built with is 2.0.6. Cheers, -Hilk

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

Package: libtorrent-rasterbar2.0 Version: 2.0.6-3+b1 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Control: notfound -1 2.0.6-3 Dear Maintainer, bug #1013470 about a nbdkit rebuild failure was reported and it turned out that this happens because of a crash that happens even in trivial cases

Bug#1009875: libtorrent-rasterbar-dev: pkg-config --libs is wrong, leads to FTBFS

Package: libtorrent-rasterbar-dev Version: 2.0.6-2 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, nbdkit which build-depends on libtorrent-rasterbar-dev fails to build from source: , | Making all in torrent | make[3]: Entering directory '/home/bengen/p/deb/nbdkit/pl

Bug#1008701: Should broctl be removed?

severity -1 normal reassign -1 ftp.debian.org retitle -1 RM: broctl -- RoM; obsolete, superceded by zeekctl thx

Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive

* Laurent Bigonville: > It looks like libguestfs-tools version 1:1.46.2-1 in depending on > guestfs-tools that is not in the archive making the package uninstalable > > guestfs-tools is currently stuck in the new queue Right. Let's just wait. (Or do you know of a way to speed this up?) Cheers,

Bug#1002773: nbdkit: FTBFS: build-dependency not installable: guestfs-tools

* Lucas Nussbaum: >> The following packages have unmet dependencies: >> libguestfs-tools : Depends: guestfs-tools but it is not installable >> E: Unable to correct problems, you have held broken packages. >> apt-get failed. Sure, we'll just need to wait for the guestfs-tools package (#1002577) t

Bug#997273: virt-v2v: FTBFS: (.text+0x12a): undefined reference to `rpl_free'

control: reassign -1 libguestfs control: fixed -1 libguestfs/1:1.46.2-1 The root cause seems to lie in the libguestfs-ocaml library and it can no longer be reproduced with 1:1.46.2-1 which I have just uploaded. Cheers, -Hilko

Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs

* Paul Gevers: > On Thu, 2 Sep 2021 10:17:22 +0200 Sascha Steinbiss wrote: >> I think this is done now. With YARA 4.1.2 and >> golang-github-hillu-go-yara 4.1.0 now in unstable, the build works again >> as the build-time tests complete fine. >> >> @Hilko any other comments? > > If there are in

Bug#988024: hivex: CVE-2021-3504

* Salvatore Bonaccorso: > CVE-2021-3504[0]: > | Buffer overflow when provided invalid node key length > > Making the severity RC as I think the fix needs to go into bullseye. Right. I contacted team@security.d.o a about the issue, including a proposed hivex/1.3.18-1+deb10u1 for stable-security a

Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs

control: tag -1 confirmed control: notfound -1 golang-github-hillu-go-yara/4.0.4-1 * Paul Gevers: > Source: yara, golang-github-hillu-go-yara > Control: found -1 yara/4.1.0~rc2-1 > Control: found -1 golang-github-hillu-go-yara/4.0.4-1 > Severity: serious > Tags: sid bullseye ftbfs bullseye-ignore

Bug#982143: supermin: supermin binary does not work on architectures without native OCaml compiler

Package: src:supermin Version: 5.2.0-2 Severity: grave X-Debbugs-Cc: none, Hilko Bengen The libguestfs package fails to build on mipsel, mips64el, armel because dh_strip as used in the supermin build renders the supermin binary unusable.

Bug#971296: rekall: Switch to python3-pycryptodome

* Sascha Steinbiss: > Just bringing this up again... I would be in favour of removing it > completely. Would be happy to file a RM from unstable if there are no > objections. I agree and have filed the RM bug. Cheers, -Hilko

Bug#978163: go-dep: Not release with bullseye

* Shengjing Zhu: > dep is deprecated by upstream. The upstream repo is now read-only. > Users should have migrated to Go modules. I agree. Not because I think that the Go Modules concept is generally more sensible, but because it has caused the go-dep project to stop. > I was thinking just to re

Bug#974574: nbdkit: diff for NMU version 1.22.3-1.1

Hi Dominic, thanks for your NMU. Please push your changes since 1.22.3-1 to git and reschedule for immediate acceptance into unstable. Cheers, -Hilko

Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)

* Richard W.M. Jones: > guestfsd: error while loading shared libraries: libtirpc.so.3: cannot > open shared object file: No such file or directory > > Did something change with how libtirpc gets packaged on Debian > or upstream? Yes, libtirpc package got renamed because that's what Debian does wh

Bug#972216: nmap: New NPSL 0.92 license likely non-free

control: severity -1 normal Hi Göran, thanks for your bug report. I think that the issue is less serious than it seems at first glance (see below). At the moment, I'm inclined to update debian/copyright (which must be done anyway), close the issue, and be done with this. The alternatives would b

Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)

control: tag -1 confirmed control: tag -1 pending * Stéphane Glondu: > Package: src:libguestfs > Version: 1:1.42.0-9 > Severity: serious > Tags: ftbfs > > Dear Maintainer, > > Your package FTBFS on amd64 and i386: > > https://buildd.debian.org/status/package.php?p=libguestfs&suite=sid > > The

Bug#966992: cause: sfdisk

control: reassign -1 fdisk 2.36-2 control: retitle -1 Regression in sfdisk I have traced the cause fo the nbdkit build failures (e.g. [1] to what seems to be a regression in sfdisk that manifests itself in a "No space left on device" error when creating some trivial partitioned disk images. ,---

Bug#968900: docbook-to-man: /usr/bin/instant is no longer installed

Package: docbook-to-man Version: 1:2.0.0-43 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, while trying to fix an FTBFS introduced with the upgrade to GCC 10 in hfsplus, I have stumbled across a docbook-to-man failure because /usr/bin/instant is no longer installed. Looking

Bug#936206: binplist: Python2 removal in sid/bullseye

* Moritz Mühlenhoff: >> Your package either build-depends, depends on Python2, or uses Python2 >> in the autopkg tests. Please stop using Python2, and fix this issue >> by one of the following actions. > > https://github.com/google/binplist/issues/6 is without any update since 2016 > and there >

Bug#938866: marked as pending in yara-python

Control: tag -1 pending Hello, Bug #938866 in yara-python 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/pkg-security-team/yara-python/commit/3f534949160c0e112

Bug#950372: Is radare2 suitable for stable Debian releases?

* Moritz Mühlenhoff: >> FTR, this was as well raised back in [1]. AFAIK there was no direct >> feedback to the question from Moritz back then. > > Yeah, we should at least remove radare2 from oldstable (IIRC for > buster there's an rdep which prevents that) That reverse dependency is radare2-cutt

Bug#949194: libnbd: FTBFS: dh: unable to load addon python3

* Mattia Rizzolo: > On Mon, Jan 20, 2020 at 11:18:34AM +0100, Hilko Bengen wrote: >> control: fixed -1 1.2.0-1 >> >> The missing dh-python3 dependency was added in 1.2.0-1; that version >> should no longer fail to rebuild from source in your setup. > > Maybe, but

Bug#949194: libnbd: FTBFS: dh: unable to load addon python3

control: fixed -1 1.2.0-1 The missing dh-python3 dependency was added in 1.2.0-1; that version should no longer fail to rebuild from source in your setup. Cheers, -Hilko

Bug#936872: Fixed in unstable, still debugging build issues

Although this bug has been fixed in unstable for some time, the package isn't migrating due to OCaml-related FTBFS issues on several architectures which I haven't been able to reproduce on porterboxes so far. Cheers, -Hilko

Bug#938692: trace-summary: diff for NMU version 0.89-1.1

* Adrian Bunk: > I've prepared an NMU for trace-summary (versioned as 0.89-1.1) and > uploaded it to DELAYED/14. Please feel free to tell me if I should > cancel it. Just reschedule your upload to go through right away. Cheers, -Hilko

Bug#883161: marked as pending in nmap

Control: tag -1 pending Hello, Bug #883161 in nmap 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/pkg-security-team/nmap/commit/a47969f12dd5cfbf2cb520d5b1774ab

Bug#885498: marked as pending in nmap

Control: tag -1 pending Hello, Bug #885498 in nmap 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/pkg-security-team/nmap/commit/86cfd4e13bd2474b0ffbcfa5a750359

Bug#936091: pending

Control: tag -1 pending A (Python-only) pyaff4 package has been uploaded to unstable and is waiting in NEW. See https://salsa.debian.org/pkg-security-team/pyaff4 for the corresponding Salsa repository. Cheers, -Hilko

Bug#939078: bro: unfulfilled (build) dependencies libbroker-dev and libbroker0

* Matthias Klose: > according to https://tracker.debian.org/pkg/bro, it references a > nn-existing libbroker0, and doesn't build on any other architecture > because of a missing libbroker-dev package. libbroker0 does not exist yet; src:broker is waiting in NEW (re-uploaded after the first REJECT)

Bug#925546: How to reproduce?

Joonas, I can get rid of the issues by backporting a number of commits from github.com/nsf/gocode and will submnit an updated package for stretch-proposed-updates. Are you able to build .deb packages from source or should I provide a binary package for you to test? Cheers, -Hilko

Bug#925546: How to reproduce?

control: tag -1 moreinfo Hi Joonas, could you describe in more detail how I might be able to reproduce the error? Does it happen with any file? Cheers, -Hilko

Bug#925592: elpa-org: Fails to install, due to byte compile error

Package: elpa-org Version: 9.2.2+dfsg-1 Severity: grave Dear Maintainer, when upgrading org-mode from unstable today, it failed in postinst in compiling the .el files. The full of a subsequent "dpkg --configure --all" run is attached. It seems to me that the message... , | In toplevel form:

Bug#923341: Bug #923341 in radare2 marked as pending

Control: tag -1 pending Hello, Bug #923341 in radare2 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/pkg-security-team/radare2/commit/690c7ad21ebb091c4ea2d4f2d

Bug#923321: Root cause likely in src:radare2

control: tag -1 confirmed Hi, it seems to me that the culprit is libradare2-dev which has lost libr_magic.so and r_magic.pc between versions 3.2.1+dfsg-2 and 3.2.1+dfsg-3 which src/cmake/FindRadare2 seems to look for. Cheers, -Hilko

Bug#922513: capstone: Block from entering testing

* Ivo De Decker: > The change should really be reverted and 3.0.5 should be re-uploaded > to unstable (obviously using a version number that is higher than > what's there now). Not only is this an uncoordinated transition long > after the transition freeze, it will also block new uploads of qemu >

Bug#921757: delayed NMU, patch

Hilko >From 2baa6f6ab0ef62ef9b9ff4214f5470b323e84c6d Mon Sep 17 00:00:00 2001 From: Hilko Bengen Date: Mon, 25 Feb 2019 20:00:01 +0100 Subject: [PATCH 1/2] Add patch to avoid race condition in osutils::runcmd (Cloese: #921757) --- ...6-Eliminate-race-condition-in-runcmd.pa

Bug#921757: Can reproduce

:00 2001 From: Hilko Bengen Date: Mon, 25 Feb 2019 09:47:35 +0100 Subject: [PATCH] Eliminate race condition in runcmd --- osutils.pm | 17 +++-- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/osutils.pm b/osutils.pm index b06a042b..ec582c66 100644 --- a/osutils.pm +++

Bug#921757: Can reproduce

Santiago, thanks for the follow-up. Your logfile with a more context looks a bit different that what I got and gives a hint. The "Use of uninitialized value" warnings suggest a race condition in runcmd. Calling waitpid in a signal handler certainly has a smell to it. I'll investigate further as

Bug#921757: Can't reproduce

user debian-rele...@lists.debian.org usertag 921757 + bsp-2019-02-de-bonn tag 921757 + unreproducible thank you Greetings from the BSP taking place at Teckids e.V./tarent solutions GmbH in Bonn this weekend. I have tried to reproduce the bug using an up-to-date sid-amd64 chroot but couldn't. My

Bug#915319: Some diagnosis

user debian-rele...@lists.debian.org usertag 915319 + bsp-2019-02-de-bonn tag 915319 + confirmed thank you Greetings from the BSP taking place at Teckids e.V./tarent solutions GmbH in Bonn this weekend. I have been abl

Bug#917216: Bug has been fixed

user debian-rele...@lists.debian.org usertag 917216 + bsp-2019-02-de-bonn fixed 917216 python-apt 1.8.1 thank you Greetings from the BSP taking place at Teckids e.V./tarent solutions GmbH in Bonn this weekend. This bug can be closed as the fix was added before python-apt/1.8.1 by yourself: ,

Bug#920000: NMU

1-6.1) unstable; urgency=medium + + * Non-maintainer upload + * Update patch to remove superfluous build flags, thanks to Laurent Bigonville +(Closes: #92) + + -- Hilko Bengen Sun, 24 Feb 2019 10:54:10 +0100 + nacl (20110221-6) unstable; urgency=medium [ Ondřej Nový ] diff -Nru nacl-201

Bug#922513: capstone: Block from entering testing

Source: capstone Version: 3.0.5-4 Severity: grave I recently uploaded the capstone4 as a separate source package, assuming that this would not have consequences in testing. As I was told on #debian-release, that is not the case because the capstone4 package takes over python-capstone, python3-caps

Bug#922271: camomile: ocaml-gettext build still fails, due to wrong search path caused by camomile build

Source: camomile Version: 1.0.1-2 Severity: grave Dear Maintainer, I just had a look at the still-failing builds of ocaml-gettext/0.3.7-1 with the pacakges produced by camomile/1.0.1-2. The logs don't show a lot, just a Not_found exception: ,[ https://buildd.debian.org/status/fetch.php?pkg=

Bug#919974: NMU, patch

* Nicholas D Steeves: > Thank you for taking care of this, but what happened to this upload? > I didn't see the updated yapf in NEW, and the upload does not appear > in any logs (wRAR checked for me). Apparently, I had not actually made the upload. Now I have. Cheers, -Hilko

Bug#920442: Detailed errors

user debian-rele...@lists.debian.org usertag 920442 + bsp-2019-02-de-berlin tag 920442 + confirmed thank you Hi! Greetings from the BSP at the DCSO office in Berlin. I have been able to reproduce the build failure. The pdflatex program does not tell us

Bug#921305: zfs-dkms: fails to upgrade from stretch

* Andreas Beckmann: > I don't think that will help, but one would have to try it. > In my test the new spl-dkms was already installed and configured. > > The problematic part was: > > configure new spl-dkms (build for linux-headers-foo-old) > install new linux-headers-foo > configure new zfs-dkms

Bug#921305: zfs-dkms: fails to upgrade from stretch

Andreas, I seem to have no way to test this in a chroot, but I'm pretty sure that this issue could be fixed by adding a versioned Pre-Depends: spl-dkms to zfs-dkms. Am I missing something? Cheers, -Hilko

Bug#919974: NMU, patch

oader did not act on this bug within the last 15 days. My patches are attached. Cheers, -Hilko >From 4fcac9c97186da7904f397ca84dc6cb21b89930c Mon Sep 17 00:00:00 2001 From: Hilko Bengen Date: Sat, 9 Feb 2019 18:11:48 +0100 Subject: [PATCH 1/3] Revert removal of Python2 support (Closes:

Bug#921871: grr: Prevent entering testing

Source: grr Version: 3.1.0.2+dfsg-6 Severity: grave The Buster release should not contain GRR. The version in unstable (3.1.0.2) is outdated and effectively unsuppoted by upstream. Current upstream versions require many thus far unpackaged build-dependencies for building the web-based UI, includi

Bug#909383: Patch, NMU

x27;d python-mode/6.2.3-1.1 which removes XEmacs21 support and fixes three bugs to DELAYED/2. Please feel free to reschedule or cancel my upload as you see fit. Patches based on 6.2.3-1 are attached. Cheers, -Hilko >From 191d5f737c5b59b93777633d1363b753d1a622d7 Mon Sep 17 00:00:00 2001 From: Hilk

Bug#915995: NMU, patch

ee to reschedule or cancel my upload as you see fit. I have attached the diffs based upon the last Git commit in Salsa. Cheers, -Hilko >From fe2dd58a3bbee3369a2d44da6e997f5a5e0ff88f Mon Sep 17 00:00:00 2001 From: Hilko Bengen Date: Sat, 9 Feb 2019 15:25:20 +0100 Subject: [PATCH 1/2] Add missing include

Bug#916151: Fix, NMU

.1 to DELAYED/2. Please feel free to reschedule or cancel my upload as you see fit. I have attached the diff. Cheers, -Hilko >From 0f24a751b7acc0952152739a5398c8140f02c098 Mon Sep 17 00:00:00 2001 From: Hilko Bengen Date: Sat, 9 Feb 2019 14:43:38 +0100 Subject: [PATCH] Add missing include, fixi

Bug#906365: Still FTBFS, different

user debian-rele...@lists.debian.org usertag 906365 + bsp-2019-02-de-berlin tag 906365 fixed-upstream thank you Hi! Greetings from the BSP at the DCSO office in Berlin. I find that building from source still fails, on

Bug#921549: golang-1.8: Security update of golang-1.8 breaks pieces of cgo pkg-config support

Source: golang-1.8 Version: 1.8.1-1+deb9u1 Severity: grave Dear Maintainer, with libyara-dev, libyara3, golang-github-hillu-go-yara-dev from stretch-backports, the attached trivial tool used to build fine, both with and without build tag "yara_static" which causes pkg-config to be called using th

Bug#920524: Fix by setting RUNPATH

control: tag -1 patch fixed-upstream This can be fixed by setting a RUNPATH for the valabind binary, see also: https://github.com/radare/valabind/pull/49 This is something Lintian will yell about, but there seems to be no other way at this stage. Cheers, -Hilko

Bug#920524: valabind: valabind does not start, libvalaccodegen.so not found.

Package: valabind Version: 1.5.0-3 Severity: serious Dear Maintainer, when trying to run valabind, I get: , | $ valabind | valabind: error while loading shared libraries: libvalaccodegen.so: | cannot open shared object file: No such file or directory ` valac/0.42.5-1 ships the shared li

Bug#919658: root cause lies in camomile package

control: reassign -1 1.0.1-1 With libcamomile-ocaml-dev/1.0.1-1 installed, the following command no longer works, breaking the ocaml-gettext build: ocamlfind query camomile Instead of installing everything (including META) to /usr/{lib,share}/ocaml/camomile, files are now installed into /usr

Bug#918645: Bug #918645 in dfwinreg marked as pending

Control: tag -1 pending Hello, Bug #918645 in dfwinreg 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/pkg-security-team/dfwinreg/commit/89cc9ffe0ab7fcfb1ec8eb3

Bug#918326: Bug #918326 in dfwinreg marked as pending

Control: tag -1 pending Hello, Bug #918326 in dfwinreg 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/pkg-security-team/dfwinreg/commit/d41dbcf1d81efc36cb92f8a

Bug#900269: Also hit by this bug

Hi, I just had the what seems to be the same bug happen to me. This is the relevant output form pstree: , | `-sudo,21446 apt dist-upgrade | `-apt,21447 dist-upgrade | `-dpkg,22875 --status-fd 39 --configure --pending | `-ifupdown.postin,22876 /var/lib/dpkg/info/ifupdo

Bug#916895: Bug #916895 in pytsk marked as pending

Control: tag -1 pending Hello, Bug #916895 in pytsk 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/pkg-security-team/pytsk/commit/b2b2527d77922f3ff0de7220faa51

  1   2   3   4   5   >