Bug#1088739: colors make ip's output unreadable

On 2025-01-02 20:53, Luca Boccassi wrote: Sorry, but as already mentioned in this bug, I disagree with this request, as the output is_much_ clearer with colors. Those who don't want this, can just trivially disable it, just like with networkctl and others. The default should provide the maximum u

Bug#1079532: sbuild copies copies ELF executables into the chroot and expects them to work

On 2024-12-03 23:50, Johannes Schauer Marin Rodrigues wrote: That's a funky issue. Thank's for not giving and reporting it instead. It can actually be reproduced in a quite simplified setting. What you need is an unstable installation with sbuild and a bookworm chroot. Then go (Johannes needs t

Bug#1079532: haproxy FTCBFS: multiple reasons

On 2024-12-01 21:03, Helmut Grohne wrote: The following packages have unmet dependencies: builddeps:/build/haproxy_3.0.5-2.dsc:arm64 : Depends: python3-sphinx:amd64 Depends: python3:arm64 but it is not going to be installed

Bug#1079532: haproxy FTCBFS: multiple reasons

Hello Helmut, On 2024-09-22 20:18, Helmut Grohne wrote: The following packages have unmet dependencies: builddeps:/build/haproxy_3.0.5-2.dsc:arm64 : Depends: python3-sphinx:amd64 Depends: python3:arm64 but it is not going to be installed

Bug#1069959: nan bug

On 2024-11-10 00:52, Pavel Kalvoda wrote: Hi, dev here, should be patched in https://github.com/PJK/libcbor/ pull/335 . Do you need a tagged release version? Hello Pavel, No need, I can cherry-pick https://github.com/PJK/libcbor/pull/335/commits/1ed15

Bug#1084271: Please have /etc/haproxy/haproxy.cfg not owned by package

On 2024-10-07 10:31, Thomas Goirand wrote: During upgrades from one Debian suite to another, dpkg is prompting for changes to /etc/haproxy/haproxy.cfg. This is very annoying and useless, as there's no way someone will keep haproxy.cfg pristine unchanged for a normal workload. Everyone is going t

Bug#1082876: keepalived FTBFS on armhf with GCC 14: [-Wincompatible-pointer-types]

On 2024-09-27 15:50, Athos Ribeiro wrote: In Ubuntu, the attached patch was applied to achieve the following: keepalived FTBFS due to an incompatible pointer type [-Wincompatible-pointer-types] issue when compiling keepalived with GCC 14 [1] in 32-bit architectures where time_t size is 64 bits.

Bug#908500: cups-browsed: Please consider making cups-browsed a Suggests:

On Mon, 10 Sep 2018 15:16:44 +0100 Brian Potkin wrote: cups-browsed is installed by default because cups-daemon (quite rightly) recommends it. With the changed situation in CUPS and applications it would appear that cups-browsed has less relevance with regard to printer and print queue discove

Bug#1079532: haproxy FTCBFS: multiple reasons

Hello Helmut, I am running into this issue when trying to crossbuild with cowbuilder: The following packages have unmet dependencies: builddeps:/build/haproxy_3.0.5-2.dsc:arm64 : Depends: python3-sphinx:amd64 Depends: python3:arm64 but it is not go

Bug#1069959: libcbor FTBFS on hppa and mips to due different NaN encoding

I have temporarily pushed Helge's patch until this is solved upstream. On 2024-09-11 17:01, Bo YU wrote: Hi, Sorry for jumping into this topic. Is there anything I can do to push for updates to this package? Becasue the package blocked debci team to create riscv64/testing chroot on our riscv6

Bug#1072970: RM: graphite-api -- ROM; FTBFS, dead

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: graphite-...@packages.debian.org Control: affects -1 + src:graphite-api User: ftp.debian@packages.debian.org Usertags: remove -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 No commit on upstream since 7 years. -BEGIN PGP SIGNATURE--

Bug#1069959: libcbor FTBFS on hppa and mips to due different NaN encoding

Hello Helge, Couldn't the patch be pushed upstream? And maybe there should be an else branch with the encoding of the other NaN? On 2024-04-27 17:35, Helge Deller wrote: Source: libcbor Version: 0.10.2-1.2 Tags: ftbfs X-Debbugs-Cc: del...@debian.org libcbor fails to build from source on the

Bug#1065690: lldpd: Does not pick correct IP or hostname

The IP address is a global information of the system (so, the same IP address is advertised for all interfaces). The hostname is the result of "getent host $(uname -n)". On 2024-03-09 00:12, Witold Baryluk wrote: Package: lldpd Version: 1.0.18-1 Severity: normal X-Debbugs-Cc: witold.bary...@gm

Bug#1065370: RM: pyiosxr -- ROM; dead upstream

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: pyio...@packages.debian.org Control: affects -1 + src:pyiosxr User: ftp.debian@packages.debian.org Usertags: remove -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1

Bug#929830: lldpd: Memory usage of lldpd implies memory leak

This is only for FDP/EDP (rare protocols). But a similar problem was fixed in earlier releases. So, maybe. On 2024-01-15 10:56, Gürkan Myczko wrote: Maybe the memory leak(s) are fixed with 1.0.18? https://github.com/lldpd/lldpd/releases

Bug#1058794: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

On 2024-01-04 00:30, Alexandre Detiste wrote: @Vincent: this one package "gtextfsm" is yours do you green light an upload ? Yes.

Bug#1040988: fixed in picom 10.2-2

On Tue, 26 Dec 2023 16:19:12 + Debian FTP Masters wrote: * Fix infinite loop with GNOME (Closes: #1040988) Upstream also added: https://github.com/yshui/picom/commit/7366553be2b825495c5b1e09be09d0fabde4b9b4 Otherwise, picom won't start at the beginning of a session (no windows yet)

Bug#1053736: amdgpu firmware are not looked up in all possible paths

Source: linux Version: 6.5.6-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, When amdgpu firmware are in /lib/firmware/updates, they are not detected by the "amdgpu-firmware-required" patch, preventing the module to load while the correct firmwares are present. https:/

Bug#1052613: Keepalived occasionally fails SSL_CHECK

Hello Pavel, I'll be more comfortable if you submitted this patch upstream first. On 2023-09-25 12:48, Pavel Matěja wrote: Package: keepalived Version: 1:2.2.7-1 I'm upgrading our servers from Bullseye to Bookworm. Some of them act as load balancers using keepalived. Right now I have one Bull

Bug#1037185: bpftrace: Fix FTBFS on armhf

On 2023-06-07 12:07, Danilo Egea Gondolfo wrote: * What led up to the situation? The build is failing on armhf because cmake is not detecting the architecture correctly as we cross compile on arm64. Also, after fixing the cmake part, the build will fail in src/triggers.h due to the attribut

Bug#1031912: Package cirrus/ directory

Source: firmware-nonfree Version: 20230210-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! The Cirrus Logic CS35L41 is a DSP with firmwares shipped upstream in the cirrus/ directory. It would be nice to build a package for that (firmware-cirrus?). Thanks! - -- System

Bug#1029992: xtl: new upstream version 0.7.5 available

On 2023-01-30 00:31, Drew Parsons wrote: Source: xtl Version: 0.7.2-2.1 Severity: normal xtl 0.7.5 has just been released. The latest version of xtensor needs it (uses xtl/xcompare.hpp), and we need the latest version of xtensor in order to support the latest version of xsimd. The latest relea

Bug#1030173: Document breaking changes in NEWS.Debian

On 2023-01-31 23:09, Lee Garrett wrote: I've written a NEWS file for you: Thanks, it will be part of the next upload.

Bug#1030173: Document breaking changes in NEWS.Debian

On 2023-01-31 21:44, Lee Garrett wrote: with release 2.6 haproxy has dropped the "ssl-engine" keyword by default. Would be nice to document that in NEWS.Debian so it gets shown by tools such as apt-listchanges during upgrade from bullseye to bookworm. In my case haproxy failed to start with my

Bug#1027382: Please, minimize your build chroots

On 2023-01-28 13:59, Adrian Bunk wrote: I am not saying that trying to force maintainers to spend time on such issues by making them release critical is better, but you are also creating extra work and frustration for the people who are doing QA work in Debian. It also pushes some maintainers t

Bug#1027382: Please, minimize your build chroots

On 2023-01-28 00:20, Santiago Vila wrote: Release Policy exists as a canonical list of what should be RC and > what not, and it's intended to avoid stupid discussions like this one. Extending build-essential is easier than asking many people to do pointless work to satisfy a set of non-existi

Bug#958895: libevhtp-dev: libtool arguments failure

On 2023-01-27 08:48, Alexandre Rossi wrote: Now that the blocking bug is fixed, I thing the patch should be uploaded to unstable. Do you want me to prepare a build for you to upload? Yes, please do. An updated package is available on mentors. https://mentors.debian.net/package/libevhtp/ T

Bug#1021502: lintian: incorrectly complains about debian-news-entry-has-unknown-version

On Tue, 11 Oct 2022 20:11:07 +0200 Axel Beckert wrote: > > Please investigate and fix this bug in lintian. I see no possibility how to do that in Lintian except for switching the check from a binary to a source package check. Not sure if this is that easily doable. Additionally it will become m

Bug#958895: libevhtp-dev: libtool arguments failure

On 2023-01-12 08:46, Alexandre Rossi wrote: Now that the blocking bug is fixed, I thing the patch should be uploaded to unstable. Do you want me to prepare a build for you to upload? Yes, please do.

Bug#1023697: Keep out of testing

On Thu, 10 Nov 2022 22:45:57 +0100 Bastian Germann wrote: As a new maintainer has stepped up, this cannot be the reason anymore to dump the package. Actually, with the next version of swupdate (one of those handful) I wanted to switch from OpenSSL to SWUpdate. As there are no real plan to pr

Bug#689962: linux: Compile with CONFIG_VIRTIO_CONSOLE=y

❦ 24 avril 2021 16:15 +02, Salvatore Bonaccorso: Is this still something we should consider, or can the bug be closed? I suppose that's since almost nobody chimes in in all these years, there is no need. Now that 989153 and 989181 have been merged into this one and the bug is reopened, the

Bug#1023537: bpftrace/libbpf: SIGSEGV at btf_find_by_name_kind()

On Sun, 06 Nov 2022 10:01:09 + Breno Leitao wrote: bpftrace is segfault on everycommand when running on 6.0 kernel: It works for me. Can you try again with bpftrace 0.16.0-1+b1?

Bug#1023974: Dependency missing

On 2022-11-13 12:30, Philipp Marek wrote: # bpftrace bpftrace: error while loading shared libraries: libclang-15.so.13: cannot open shared object file: No such file or directory I am not able to reproduce on my system. I don't have libclang1-15 at all and it works. bpftrace is not

Bug#1023485: Shipped blkid is incompatible with the one in util-linux, break cryptsetup

Package: busybox-static Version: 1:1.35.0-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! blkid was added as an applet in busybox. This makes it available in initramfs in place of the one from util-linux. This prevents cryptsetup to works as the syntax used is not reco

Bug#1021157: missing firmwares for Qualcomm NFA725A

On 2022-10-29 20:05, Diederik de Haas wrote: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?qt=grep&q=WCN6855 does show various results which come very close ...SILICONZ_LITE-3.6510.7 vs the referenced ...SILICONZ_LITE-3.6510.16. And one commit is for symlinks to

Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

On 2022-10-29 09:23, Salvatore Bonaccorso wrote: So question is,.. would it make sense to request that linux-image-amd64 depends on the signed | unsigned version? No unfortunately we cannot do that. The reason is similar to what lead to https://salsa.debian.org/kernel-team/linux/-/commit/248736

Bug#1021157: missing firmwares for Qualcomm NFA725A

On 2022-10-29 07:15, Vincent Bernat wrote:  07:14 ❱ dpkg -L firmware-atheros | grep -E '(WCM6855|nvm_usb_00130201)' I made a typo in WCN, but the files are not here either.

Bug#1021157: missing firmwares for Qualcomm NFA725A

On 2022-10-29 00:50, Diederik de Haas wrote: The card works just fine with a 5.19 kernel after installing these files in /usr/lib/firmware/ath11k/WCN6855/hw2.0/: https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/1.1/WLAN.H SP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16/ams

Bug#968997: fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot

On Fri, 10 Sep 2021 10:35:31 +0200 Julian Andres Klode wrote: Control: reassign -1 shim Control: affects -1 fwupd On Fri, Sep 10, 2021 at 09:27:11AM +0200, Norbert Schulz wrote: > Package: fwupd > Version: 1.2.14-1~deb10u1 > Followup-For: Bug #968997 > > Dear Maintainer, > > this bug still ex

Bug#1010039: autorandr: python deprecation warnings

On Fri, 22 Apr 2022 16:52:35 -0700 Don Armstrong wrote: > % autorandr > /usr/bin/autorandr:42: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives > from distutils.version import LooseVersi

Bug#1017676: bpftrace: Please upgrade to llvm-toolchain-14

On 2022-08-18 23:43, Sylvestre Ledru wrote: Source: bpftrace Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -14. We are trying NOT to ship Bookworm with llvm-toolchain-13. llvm-defaults

Bug#1017079: ITP: netbox -- WebUI based tool designed to manage and document computer networks

On 2022-08-13 09:59, Carsten Schoenert wrote: The NetBox UI is using some comprehensive JS files which are shipped as minimized files. Currently I'm unable to drop the shipped minimized code and rebuild all the needed files from scratch. If possible I'd like to get some help on this, currently ne

Bug#1015210: OUI lookups incorrect

On 2022-07-17 21:54, Jonathon Reinhart wrote: Are you suggesting that python3-netaddr would need its own directory somewhere under /var for the updated index files? (Because /usr shouldn't change, and /var/lib/ieee-data isn't controlled by python3-netaddr) That's right.

Bug#1015210: OUI lookups incorrect

On 2022-07-17 20:40, Jonathon Reinhart wrote: OUI lookups are returning incorrect / corrupt results. Take for example OUI F4-6D-04. The data in ieee-data is correct: F4-6D-04 (hex)ASUSTek COMPUTER INC. F46D04 (base 16)ASUSTek COMPUTER INC. 1

Bug#1013581: Please rebuild to pick up the new libXi.6 dependency.

Version: 3.19-9 On 6/24/22 13:39, Peter Pentchev wrote: If this is the case, could you just request a binNMU? Hm, that's actually an interesting idea... I'll look into it, and, in that case, sorry for bothering you! :) So yeah, I will look into it and probably close this bug accordingly. I h

Bug#1013581: Please rebuild to pick up the new libXi.6 dependency.

On 6/24/22 13:05, Peter Pentchev wrote: Source: xnee Version: 3.19-8 Severity: serious X-Debbugs-Cc: r...@debian.org Hi, First of all, thanks for taking care of cnee/xnee in Debian! At some point recently, the XIQueryVersion() function from the X11 API moved to a separate library, libXi.so.6,

Bug#1011391: [Pkg-openssl-devel] Bug#1011391: openssl: please support quictls patchset

❦ 8 June 2022 07:44 +02, Sebastian Andrzej Siewior: >> Willy Tarreau already asked the team for QuicTLS packaging without an >> answer: >> >> https://alioth-lists.debian.net/pipermail/pkg-openssl-devel/2021-October/007668.html > > there was an answer: > > https://alioth-lists.debian.net/pip

Bug#1011391: openssl: please support quictls patchset

❦ 22 May 2022 16:50 +02, Sakirnth Nagarasa: > This patchset of OpenSSL is necessary to build the crypto helper > libraries for ngtcp2 with OpenSSL as well. HAProxy is also a user of such a fork. It should be noted the fork is backed by Akamai and Microsoft and is able to release updated versions

Bug#1010849: DWARF support disabled during build / no symbolic stack traces or argument types

❦ 11 May 2022 16:00 +02, Harald Welte: > It seems the Debian bpftrace is built without libdw support. This means no > stack > traces can be provided with uprobes, and one cannot dereference structs or > other > type information from the DWARF information. > > # bpftrace -lv > 'uprobe:/usr/loc

Bug#1008323: bpftrace: fix FTBFS

❦ 11 April 2022 21:14 +02, Hector Oron: > According to https://github.com/iovisor/bpftrace/issues/2068 > > I applied the following patch to make the package build: Thanks! I will use the more minimal patch found here instead: https://github.com/iovisor/bpftrace/pull/2174 -- Make sure specia

Bug#960420: Needs versioned dependency on slop

❦ 12 May 2020 14:25 +02, Yuri D'Elia: > I didn't realize maim depended on slop through a dso (I assumed it > simply called the binary). > > slop was updated to 7.5, which broke maim as a result: > > maim: error while loading shared libraries: libslopy.so.7.4: cannot > open shared object file: No

Bug#995028: ncal: incorrect week numbers listed when using -w option

❦ 24 September 2021 16:33 -07, Andy Bussman: > ncal lists incorrect week numbers when using the -w option. > > Week numbers do not conform in the ISO-8601 standard, even though the > man page states that the "-w" option is ISO-8601 compliant. FI, the bug is also present upstream. -- Make sure a

Bug#1008222: bind unicast_src x.y.z.w failed 99 - Cannot assign requested address

❦ 25 March 2022 11:48 +01, Arturo Borrero Gonzalez: >> After looking twice, I notice the VIP is in the same subnet as the peer. >> If you don't have any other address on the subnet, I don't see how this >> could work. If you have, maybe it would be better to use a /32 for the >> VIP. > > Would yo

Bug#1008222: bind unicast_src x.y.z.w failed 99 - Cannot assign requested address

severity -1 important fixed -1 1:2.2.7-1~bpo11+1 thanks ❦ 24 March 2022 17:24 +01, Arturo Borrero Gonzalez: > This exact same setup was previously working, and actually, the next version > works just fine. > Not sure if this has anything to do with the kernel version warning at the > beginning

Bug#1007800: golang-golang-x-tools: FTBFS with Go 1.18

❦ 16 March 2022 18:39 -05, William 'jawn-smith' Wilson: > golang-golang-x-tools currently FTBFS with Go 1.18 > > In Ubuntu, the attached patch was applied to achieve the following: > > > * Fix FTBFS with Go 1.18 Hello, gopls has issues with Go 1.18. Better upgrade to the latest upstream versi

Bug#1006427: New upstream version: 2.2.7

❦ 9 March 2022 12:37 +01, Alexander Wirt: >> >> A new upstream version has been published. Would you mind if I take >> >> over the package? I work next to the upstream author and I am often >> >> badgered by the package being not up-to-date. :) >> >> > I would be glad if you would take over. Un

Bug#1006961: exabgp.env not loaded with systemd Service

❦ 9 March 2022 13:18 +01, Adrian: > ExecStart=/usr/sbin/exabgp -e /etc/exabgp/exabgp.env /etc/exabgp/exabgp.conf > # < manually added env file /etc/exabgp/exabgp.env is the default value when no -e option is provided. -- A horse! A horse! My kingdom for a horse! -- Wm. S

Bug#1006427: New upstream version: 2.2.7

❦ 4 March 2022 10:47 +01, Alexander Wirt: >> A new upstream version has been published. Would you mind if I take >> over the package? I work next to the upstream author and I am often >> badgered by the package being not up-to-date. :) > I would be glad if you would take over. Unfortunately I a

Bug#1006427: New upstream version: 2.2.7

Source: keepalived Version: 1:2.2.4-0.2 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! A new upstream version has been published. Would you mind if I take over the package? I work next to the upstream author and I am often badgered by the package being not up-to-date. :)

Bug#1006007:

❦ 19 February 2022 10:02 -03, Andreas Hasenack: > Salsa PR at https://salsa.debian.org/haproxy-team/haproxy/-/merge_requests/7 > with the upstream patch that ubuntu has been carrying. I have asked upstream about guidance on this. It seems that despite compiling, there are regressions during inte

Bug#1003108: Dependency on python3-cachecontrol has an odd alternative

Package: python3-poetry Version: 1.1.12+dfsg-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! python3-cachecontrol (>= 0.12.6) | python3 (>> 3.6) So, python3-cachecontrol don't get installed. Dunno who is generating this dependency. Checked cachecontrol repository, but no

Bug#965696: libwhisker2-perl: diff for NMU version 2.5-1.2

Thanks! If you want to take over this package, be my guest! On January 1, 2022 6:35:04 PM GMT+01:00, gregor herrmann wrote: >Control: tags 965696 + patch >Control: tags 965696 + pending >Control: tags 999044 + patch >Control: tags 999044 + pending > > >Dear maintainer, > >I've prepared an NMU fo

Bug#998242: cron-failure@.service delivery fails due to DynamicUser with exim

Control: forwarded -1 https://github.com/systemd-cron/systemd-cron/issues/75 ❦ 21 December 2021 21:14 +01, Vincent Bernat: > I have the same issue with Postfix. This is a problem known upstream. DynamicUser= implies NoNewPrivileges=. https://github.com/systemd-cron/systemd-cron/issues

Bug#995212: ungoogled-chromium? [

❦ 14 December 2021 09:13 GMT, Jeff Blake: > Unless there are licensing or technical objections, I would suggest building > with upstream > bundled clang to avoid all sorts of incompatibilities and obviate the need > for extra patching > (stable's clang is often too old and upstream currently

Bug#998242: cron-failure@.service delivery fails due to DynamicUser with exim

❦ 1 November 2021 14:27 +01, Yuri D'Elia: > cron-failure@ is using DynamicUser=yes, however this causes a silent > delivery failure when using exim4: > > systemd[1]: Starting cron-failure@cron-monthly.service... > mail_on_failure[328561]: 2021-11-01 14:11:23 1mhX5v-001NTN-LU Failed > to create s

Bug#996165: firmware-sof-signed: sound/mic also does not work on Dell Precision 5760

❦ 17 December 2021 17:55 +01, Dirk Kostrewa: > I have also tried before the 5.14 kernel from the Bullseye backports > repository (with firmware-sof-signed 1.7.1), which also didn't work. I > would be grateful for any other suggestion! No idea. You should try to ask upstream: https://github.com/

Bug#996165: firmware-sof-signed: sound/mic also does not work on Dell Precision 5760

❦ 17 December 2021 10:19 +01, Dirk Kostrewa: > 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device > [8086:43c8] (rev 11) >     Subsystem: Dell Device [1028:0a5e] >     Flags: bus master, fast devsel, latency 64, IRQ 16, IOMMU group 17 >     Memory at 618d1d8000 (64-b

Bug#1001507: RFS: dwm/6.2-1 [ITA] -- dynamic window manager

❦ 11 December 2021 10:43 GMT, Matteo Bini: >* New maintainer Is there some agreement with the original maintainer? >* New upstream release. You can close #978687 and #945281. -- Debian package sponsoring guidelines: https://vincent.bernat.ch/en/debian-package-sponsoring

Bug#1001474: bullseye-pu: package bpftrace/0.11.3-5

7PzAKAxuCP Ulx3pTpsock1jS/LSAbPoyUTOo2skm39tC9zOuixLQuLy81NVMIUr2SQQctLiLAk /avo0leQDqZihJY2Di7idvm9El/VbHq80SYi2ddMsD8WeFvIU77xwrP1azlnjkhg hdP5YokOmKBt =pJ4O -END PGP SIGNATURE- >From b06bd9dfd60e58f6c5164fd283cb19801513fb09 Mon Sep 17 00:00:00 2001 From: Vincent Bernat Date: Fri, 10 Dec

Bug#1001449: array indexing broken

❦ 10 December 2021 10:40 +01, Julian Taylor: > This has been fixed upstream with this patch: > https://github.com/iovisor/bpftrace/pull/1457 I'll try to push the update for the next point release (Dec 18). -- The last thing one knows in constructing a work is what to put first.

Bug#999673: bullseye-pu: package lldpd/1.0.11-1

❦ 29 November 2021 17:32 GMT, Adam D. Barratt: >> > What you've uploaded to bullseye is *not* what you proposed in this >> > request, however. >> > >> > The debdiff attached to this bug report amounts to "4 files >> > changed, >> > 130 insertions(+)", the uploaded package is "39 files changed, 5

Bug#977738: rofi: New upstream release 1.6.1

❦ 9 September 2021 09:04 +02, Vincent Bernat: >> https://github.com/davatorium/rofi/releases/tag/1.6.1 >> >> Version 1.6.0 is very interesting because it adds a new [1]script mode >> that allows more powerful selectors. >> >> I tried to build the package u

Bug#999673: bullseye-pu: package lldpd/1.0.11-1

is "39 files changed, 561 > insertions(+), 221 deletions(-)" and includes a new upstream release. Ugh. Very sorry about that! Here is the appropriate diff. How can I sort out my bad upload? Bumping the version number? I hold uploading anything else until you approve. >From a5a413c

Bug#1000707: bullseye-pu: package keepalived/1:2.1.5-0.2

ckdhX e3DXALjBZLhd =uiHe -END PGP SIGNATURE- >From 9b4813899b1bd0ba9b719f458d794534e9989d22 Mon Sep 17 00:00:00 2001 From: Vincent Bernat Date: Sat, 27 Nov 2021 15:53:33 +0100 Subject: [PATCH] Fix shipped too broad DBus policy. CVE-2021-44225 --- debian/changelog | 6 ++

Bug#999673: bullseye-pu: package lldpd/1.0.11-1

❦ 14 November 2021 19:21 +01, Vincent Bernat: > Package: release.debian.org > Severity: normal > Tags: bullseye > User: release.debian@packages.debian.org > Usertags: pu [...] I did the upload to bullseye as I think the change is not controversial. -- The lunatic, the love

Bug#995817: ERROR: Could not resolve symbol: /proc/self/exe:BEGIN_trigger

❦ 15 November 2021 07:51 +01, Salvatore Bonaccorso: >> I have tried to just not strip the binary, but this produces a quite >> huge binary. I didn't get time to investigate much yet. > > Asked a bit around, and got the following hint from Niels Thykier: > > https://bugs.debian.org/cgi-bin/bugrepo

Bug#999673: bullseye-pu: package lldpd/1.0.11-1

00:00:00 2001 From: Vincent Bernat Date: Sun, 14 Nov 2021 15:42:12 +0100 Subject: [PATCH] Tentative security update for Bullseye --- debian/changelog | 8 ++ ...et-VLAN-tag-if-client-did-not-set-it.patch | 27 ++ ...-overflow-when-reading-SONMP-

Bug#995817: ERROR: Could not resolve symbol: /proc/self/exe:BEGIN_trigger

❦ 13 November 2021 15:06 +01, Salvatore Bonaccorso: >> > In fact, it does not happen if you have debug symbols. My patch does not >> > work anymore either and the previous upload did not fix this bug. Some >> > distributions work around that by asking "strip" to keep BEGIN_trigger. >> > It seems

Bug#964934: cookiecutter: Upgrade to version 1.7.x

❦ 12 November 2021 12:52 -04, Wesley Schwengle: >>> In December 2019 version 1.7.0 was released and in April 2020 1.7.1 and >>> 1.7.2 were released. It adds a very useful feature: >>> >>>https://cookiecutter.readthedocs.io/en/1.7.2/advanced/directories.html >>> >>> I would like to make use of

Bug#997218: keepalived: FTBFS: if.h:44:5: error: redeclaration of enumerator ‘IFF_UP’

ersion 2.2.1 * [ecf662d] Keepalived has now support for systemd notify - -- Alexander Wirt Mon, 25 Jan 2021 09:04:08 +0100 + [ Vincent Bernat ] + * Non-maintainer upload. + * New upstream version 2.2.4. Closes: #980563. +- Fix FTFBS. Closes: #997218. + * d/rules: enable systemd as an i

Bug#998108: Tracking this bug down

❦ 4 November 2021 23:39 +01, Eugen Dedu: > Maybe I am wrong, but, for me, the simplest method to track this bug > down is to check the changes between the two versions, 93.0 and > 93.0-1+b1. Firefox code has not changed, only one or some libraries > it depends on. I thought that the only chan

Bug#990821: aptly fails to run if both gnupg2 and gnupg1 are installed

❦ 8 July 2021 16:51 +02, Christoph Berg: > As soon as gpg1 (package gnupg1) and gpgv (from gnupg 2) are > installed, aptly fails to run. I think aptly should "Conflicts: > gnupg1", but maybe there is a better fix. This also happens when gpgv1 is installed. -- Don't sacrifice clarity for small

Bug#995823: bullseye-pu: package kodi/2:19.2+dfsg1-1~deb11u1 (pre-upload unblock bug)

❦ 7 October 2021 16:24 GMT, Vasyl Gello: > FYI, kodi 2:19.1+dfsg2-2_19.2+dfsg1-1 is in unstable :) I have been running a version rebuilt for Bullseye since a few days (notably due to issues with HD audio which are fixed in this release) and it works fine for me. -- For a light heart lives long

Bug#995817: ERROR: Could not resolve symbol: /proc/self/exe:BEGIN_trigger

❦ 6 October 2021 15:03 +02, Salvatore Bonaccorso: > After updating bpftrace to 0.13.0-1 in unstable, I noticed invocation > using a BEGIN block do not work anymore, the BEGIN_trigger symbol > cannot be resolved, basically reproducible with the minimal: > > # bpftrace -e 'BEGIN { }' > Attaching 1

Bug#930557: i3-gaps RFS/ITP

❦ 3 October 2021 09:16 +02, Michael Stapelberg: > I will stress one more time that what we need here is not a one-time > sponsorship offer, but a multi-year commitment for maintaining the > i3-gaps package in Debian. Let's hear from antisocrates. I can offer a multi-year commitment for sponsors

Bug#930557: i3-gaps RFS/ITP

❦ 3 October 2021 08:48 +02, Michael Stapelberg: > I still think it’d be better to spend time on merging gaps rather than > packaging gaps, > but it seems like nobody has the skill set and/or motivation. This is a very different skillset from packaging. > Is there someone who would continuously

Bug#930557: i3-gaps RFS/ITP

❦ 17 June 2019 18:30 +02, Michael Stapelberg: > Ingo will outline what needs to be done to get i3-gaps into a mergable > state, so that we can eventually bring these features to all i3 users. > > For the time being, our recommendation is to NOT add i3-gaps to Debian or > any other Linux distribut

Bug#994865: Delayed start due to Pipewire not running

❦ 23 September 2021 17:09 +02, Vincent Bernat: > Let me reboot at the end of the day with just xdg-desktop-portal in > verbose mode, it may be enough to find the cause. If not, I will apply > your other tricks. OK, a bit late, but on verbose, I get: Sep 30 07:57:56 chocobo xdg-deskt

Bug#994865: Delayed start due to Pipewire not running

❦ 23 September 2021 15:37 +01, Simon McVittie: > I see from your initial bug report that you are using systemd as pid 1, > systemd --user, and dbus-user-session (i.e. dbus-daemon --session is > running as a systemd --user unit). Is that correct? Yes. > What desktop environment are you using? Or

Bug#994865: Delayed start due to Pipewire not running

❦ 23 September 2021 10:08 +01, Simon McVittie: >> Since upgrading to 1.10.1-1, xdg-desktop-portal service takes a lot of >> time to start on a desktop not using Pipewire. > > Looking at the diff, I don't understand why this particular upgrade > would trigger this: the only Pipewire-related change

Bug#994890: New upstream version (5.7.4)

Package: maim Version: 5.6.3-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Could you please upload a new version? 5.6.3 is getting a bit old and I am running into an annoying bug that may be fixed in a more recent version. Thanks! - -- System Information: Debian Re

Bug#980300: libcbor: Please upgrade to new version 0.8.0

❦ 21 September 2021 14:54 -04, Nicolas Mora: > Friendly ping request for this bug. > If you need help, I'll be happy to help you with this upgrade. Done. It is waiting in NEW. -- Identify bad input; recover if possible. - The Elements of Programming Style (Kernighan & Plauger)

Bug#994865: Delayed start due to Pipewire not running

Package: xdg-desktop-portal Version: 1.10.1-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Since upgrading to 1.10.1-1, xdg-desktop-portal service takes a lot of time to start on a desktop not using Pipewire. 09:52 ❱ journalctl -b0 --user-unit=xdg-desktop-portal - -- J

Bug#992149: firmware-sof: Internal microphone (DMIC) not working on Lenovo Thinkpad 13S

❦ 21 September 2021 18:03 +03, Andrei POPESCU: >> The work-around is presented here: >> https://github.com/thesofproject/linux/issues/2460#issuecomment-779212719 >> >> In a nutshell, a binary blob is offered there to replace the file >> sof-hda-generic-2ch.tplg in firmware-sof-signed. >From my

Bug#977738: rofi: New upstream release 1.6.1

❦ 19 December 2020 20:18 GMT, Ayose: > A new version was published: > > https://github.com/davatorium/rofi/releases/tag/1.6.1 > > Version 1.6.0 is very interesting because it adds a new [1]script mode > that allows more powerful selectors. > > I tried to build the package using the current [2]deb

Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

Package: systemd Version: 247.9-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! After upgrading to libc6 2.32-1, some services are unable to restart. In my case, systemd-resolved, systemd-timesyncd and colord. Using "systemctl daemon-reexec" fixes the issue. Unsure if the

Bug#993658: qemu-user-static does not work through binfmt since 6.0

❦ 4 September 2021 15:49 +03, Michael Tokarev: >> Kernel: Linux 5.13.0-trunk-amd64 (SMP w/12 CPU threads) > > Can you please check if it works with not-so-fresh kernel > (eg the one from bullseye)? > > I wont able to do this until late evening today. > > I'm guessing this is the upstream way to

Bug#993658: qemu-user-static does not work through binfmt since 6.0

Package: qemu-user-static Version: 1:6.1+dfsg-4 Severity: critical -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Since 6.0, qemu-user-static does not seem to work properly through binfmt. I am a bit lost on how to diagnose that: 13:23 ❱ cat /proc/sys/fs/binfmt_misc/qemu-aarch64 enabled

Bug#993429: Please indent example in package description

❦ 1 September 2021 08:23 +02, Christoph Biedl: > please check https://packages.debian.org/sid/jo - there is a small and > nice usage example in the package description, but unfortunately the > formatting is rather poor. > > According to policy, just adding another space at the beginning of the >

Bug#865793: hsetroot FTCBFS: uses the build architecture pkg-config

❦ 24 June 2017 22:31 +02, Helmut Grohne: > hsetroot fails to cross build from source, because the patch added in > #735758 uses the build architecture pkg-config. It should be using the > PKG_PROG_PKG_CONFIG macro and access pkg-config through $PKG_CONFIG > instead. After doing so, hsetroot cross

  1   2   3   4   5   6   7   8   9   10   >