Bug#1020698: O: dlocate -- fast alternative to dpkg -L and dpkg -S

Control: owner -1 ! Control: retitle -1 ITA: dlocate -- fast alternative to dpkg -L and dpkg -S Hi! On Mon, 2022-10-03 at 01:45:12 +0200, Guillem Jover wrote: > On Fri, 2022-09-30 at 04:07:05 +0200, Guillem Jover wrote: > > On Sun, 2022-09-25 at 16:19:08 +0200, Tobias Frost wrote: >

Bug#1085127: ITP: go-nmap -- Nmap XML parsing library for Go (library)

Hi! On Mon, 2024-10-14 at 22:20:11 -0300, Marcos Rodrigues de Carvalho (aka oday) wrote: > Package: wnpp > Severity: wishlist > Owner: "Marcos Rodrigues de Carvalho (aka oday)" > X-Debbugs-Cc: debian-de...@lists.debian.org, marcosrcarvalh...@gmail.com > > * Package name: go-nmap > Version

Bug#1085073: dpkg: please expose no-triggers mode to hooks

Hi! On Sun, 2024-10-13 at 21:35:05 -0400, Aaron M. Ucko wrote: > Package: dpkg > Version: 1.22.11 > Severity: normal > X-Debbugs-Cc: debian-security-supp...@packages.debian.org > As dpkg's man page notes, complex apt runs can yield multiple > invocations of dpkg and hence also of dpkg-level hooks

Bug#953932: Upcoming dropping of compat from libattr1-dev

Control: severity -1 serious Hi! On Wed, 2024-08-28 at 04:15:39 +0200, Guillem Jover wrote: > This is a heads-up that I'm going to be dropping the "temporary" header > that was dropped from libattr1-dev upstream more than 5 years ago, and > where I added it back for

Bug#947287: fixed in python-certifi 2024.8.30+dfsg-1

Hi! On Mon, 2024-10-07 at 13:29:31 +, Debian FTP Masters wrote: > Source: python-certifi > Source-Version: 2024.8.30+dfsg-1 > Done: Sebastien Delafond > Format: 1.8 > Date: Mon, 07 Oct 2024 14:43:02 +0200 > Source: python-certifi > Architecture: source > Version: 2024.8.30+dfsg-1 > Distribut

Bug#1084509: rsopv: Does not seem ready to provide sopv

Package: rsopv Version: 0.3.8-1 Severity: serious Hi! While trying to integrate rsop/rsopv into dpkg, I noticed that it at least fails with https://codeberg.org/heiko/rsop/issues/5, for inline-verify with binary data. I'd say this disqualifies it to be able to provide sopv. I've set this to serio

Bug#1084495: rsop: Missing Homepage field

Package: rsop Version: 0.3.8-1 Severity: wishlist Hi! This package has no Homepage field to https://codeberg.org/heiko/rsop. I was looking to find upstream bug reports and missed it. :) Thanks, Guillem

Bug#1077345: chromium: video on wayland, each frame emits warning to stderr: "gbm_pixmap_wayland.cc(82)] Cannot create bo with format=YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE"

Hi! On Wed, 2024-10-02 at 03:14:59 +0200, Guillem Jover wrote: > On Sat, 2024-09-28 at 23:12:36 -0400, Andres Salomon wrote: > > On 9/28/24 22:42, Guillem Jover wrote: > > > > In particular, i see a line like this appear roughly once per frame: > > > > > &

Bug#1060272: libsysfs2: ""trying to overwrite shared changelog.Debian.gz', which is different"

Version: 2.1.1-6 Hi! On Wed, 2024-01-10 at 22:47:24 +0100, Guillem Jover wrote: > On Mon, 2024-01-08 at 15:45:41 +0100, Sven-Haegar Koch wrote: > > Package: libsysfs2 > > Version: 2.1.1-5+b1 > > Severity: normal > > > Trying to upgrade libsysfs2 from 2.1.1

Bug#1083015: openssh-known-hosts: Improve OpenPGP support

Hi! On Mon, 2024-09-30 at 20:01:25 +0200, Timo Weingärtner wrote: > 30.09.24 02:18 Guillem Jover: > > I've prepared a few patches to improve the OpenPGP support. I think at > > least the one fixing the gpgv usage means that part is probably > > currently unusable?

Bug#1075982: Bug#1077345: chromium: video on wayland, each frame emits warning to stderr: "gbm_pixmap_wayland.cc(82)] Cannot create bo with format=YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE"

Hi! On Sat, 2024-09-28 at 23:12:36 -0400, Andres Salomon wrote: > On 9/28/24 22:42, Guillem Jover wrote: > > > In particular, i see a line like this appear roughly once per frame: > > > > > > ``` > > > [635461:635515:0728/122929.891862:ERROR:gbm_pixmap_

Bug#1083118: kitty: Do not hardcode golang-github-shirou-gopsutil v3

uffix, which should make it build with both v3 and v4. So it would be nice if this could be uploaded right away to make this not block this mini-transition anymore. :) Thanks, Guillem From b6000c9f68a871ec68f7de07814ea36bc694195c Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Wed, 2 Oct 2024

Bug#1083117: podman: Do not hardcode golang-github-shirou-gopsutil v3

ed v3 suffix, which should make it build with both v3 and v4. So it would be nice if this could be uploaded right away to make this not block this mini-transition anymore. :) Thanks, Guillem From 9b8d0ea36d0cce1d867129a9f8f2a82f8175a6d4 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Wed, 2 Oct 20

Bug#1083048: python3-vobject: SyntaxWarning: invalid escape sequence '\,'

Package: python3-vobject Version: 0.9.7-1 Severity: normal Hi! While upgrading this package I got the following warning: Setting up python3-vobject (0.9.7-1) ... /usr/lib/python3/dist-packages/vobject/hcalendar.py:1: SyntaxWarning: invalid escape sequence '\,' """ Thanks, Guillem

Bug#1083015: openssh-known-hosts: Improve OpenPGP support

ttaching a small patch for the packaging. Thanks, Guillem From b32b285019eb749cfc650748fa4a4ce3b4fda736 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Mon, 30 Sep 2024 01:36:22 +0200 Subject: [PATCH 1/3] Use OpenPGP when referring to the standard or objects These are OpenPGP signatures that any

Bug#1083014: openssh-known-hosts: Upstream Homepage and Vcs links point to archived project

Source: openssh-known-hosts Source-Version: 0.6.2-1.1 Severity: wishlist Hi! While preparing some changes for this package, I noticed that the upstream project is now archived. It would be nice to update the Homepage and Vcs-* fields to point to the current project. I assume that might be: htt

Bug#1077345: chromium: video on wayland, each frame emits warning to stderr: "gbm_pixmap_wayland.cc(82)] Cannot create bo with format=YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE"

Control: forwarded -1 https://issues.chromium.org/issues/331796411 Control: tags -1 upstream fixed-upstream Hi! On Sun, 2024-07-28 at 09:51:09 -0700, Daniel Kahn Gillmor wrote: > Package: chromium > Version: 126.0.6478.126-1~deb13u1 > Severity: normal > When i use chromium to watch a video, usin

Bug#1079489: dpkg-dev: buildflags.mk messes with string double quoting

Control: block -1 by 1029106 [ Nicolas CCed you only FYI. :) ] Hi! On Fri, 2024-08-23 at 22:54:05 +0200, Andrea Pappacoda wrote: > Package: dpkg-dev > Version: 1.22.11 > Severity: normal > Hi! I've just noted a strange behaviour of buildflags.mk. In short, including > the file seems to remove s

Bug#1082896: Please provide a configuration option to set an environment variable

On Fri, 2024-09-27 at 13:22:07 -0700, Josh Triplett wrote: > Package: dpkg > Version: 1.22.11 > Severity: wishlist > X-Debbugs-Cc: j...@joshtriplett.org > I'd love to be able to set an option in dpkg.cfg.d that causes dpkg to > set an environment variable when running any commands. This would make

Bug#1082901: libpcre2-dev: Mention natural libpcrecpp successor in Description

Package: libpcre2-dev Version: 10.42-4 Severity: wishlist X-Debbugs-Cc: libgoby-j...@packages.debian.org, g...@packages.debian.org, passwordmaker-...@packages.debian.org Hi! I was recently in need of switching some C++ projects using libpcrecpp from PCRE to PCRE2, when I realized the C++ library

Bug#1081951: kannel: FTBFS on 32 bit architectures where time is time64_t

Hi! On Mon, 2024-09-16 at 21:12:51 +0200, Chris Hofstaedtler wrote: > On Mon, Sep 16, 2024 at 04:01:06PM +0200, Gianfranco Costamagna wrote: > > Hello, after the time64_t transition, kannel started FTBFS on armel, armhf > > and where time_t is 64 bit defined. > > With my ex-kannel-maintainer hat

Bug#1082850: ITP: golang-github-mitchellh-pointerstructure -- Addressing and modifying values in Go structures using a string syntax

Hi! On Fri, 2024-09-27 at 12:28:51 +, Francisco Vilmar Cardoso Ruviaro wrote: > Package: wnpp > Severity: wishlist > Owner: Francisco Vilmar Cardoso Ruviaro > X-Debbugs-Cc: debian-de...@lists.debian.org, vil...@debian.org > * Package name: golang-github-mitchellh-pointerstructure > Ver

Bug#1002056: Supporting alternative zlib implementations

Hi! On Wed, 2024-09-25 at 00:39:10 +0200, Fay Stegerman wrote: > * Guillem Jover [2024-09-24 17:45]: > > Personally, I think fully migrating from zlib to zlib-ng would sound > > great (even for trixie), but I guess we can take it slow if you do not > > feel confident or ha

Bug#1082703: libvolume-key1: Drop gnupg dependency?

Package: libvolume-key1 Version: 0.3.12-8 Severity: wishlist Hi! This library uses GnuPG through the GPGME library, and currently depends on libgpgme11t64. In addition it also explicitly depends on the gnupg package. I guess strictly speaking this direct dependency might make sense as the code se

Bug#1002056: Supporting alternative zlib implementations

Hi! On Tue, 2024-09-24 at 15:58:10 +0200, Mark Brown wrote: > In the past I've pushed back on doing anything here since zlib is > essential and it seemed better to be consistent over the ecosystem than > to use a more niche implementation, and some of the early optimisation > efforts had not worke

Bug#1082558: dpkg: confusing warning message

Hi! On Tue, 2024-09-24 at 09:47:55 +0200, Patrice Duroux wrote: > Also, the installed package providing the current file that is > conflicting might not be related > to that package (multiarch or not). I mean that it could be another > unrelated package. No, this message is always only concerned

Bug#1082651: libjson-rpc-perl: Do not try to parse non-existing JSON

Thanks, Guillem From fc84cb2df7ef9cbc33f6fc03975b3a96f34bb9ff Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Sun, 21 Jul 2024 23:27:16 +0200 Subject: [PATCH] JSON::RPC::Legacy::Client: Do not try to parse non-existing JSON If the server reported a server error, then we get no JSON. We should return immediately instea

Bug#1082558: dpkg: confusing warning message

Hi! On Sun, 2024-09-22 at 10:42:03 +0200, Patrice Duroux wrote: > Source: dpkg > Version:1.22.11 > Severity: wishlist > On a biarch system (amd64,i386) and using --force options (note that I am > aware of the taken risk ;-)), dpkg shows: > > $ dpkg --force-all -i libllvm19_1%3a19.1.0-3_i386.deb

Bug#1082638: libresawn, strongswan-starter: Permission mismatch for /etc/ipsec.secrets

Package: libreswan, strongswan-starter Severity: important Tags: security X-Debbugs-Cc: Helmut Grohne Hi! While analyzing the archive for mismatched file metadata (as part of the preparation to add support into dpkg), thanks to Helmut gathering the data from the archive. I noticed that these two

Bug#1082430: krb5-kdc, krb5-keytab-backend: Permission mismatch for /etc/krb5kdc/

Hi! On Fri, 2024-09-20 at 16:40:57 -0700, Russ Allbery wrote: > Control: reassign -1 krb5-keytab-backend > Guillem Jover writes: > > While analyzing the archive for mismatched file metadata (as part of the > > preparation to add support into dpkg), thanks to Helmut gathering

Bug#1082433: drbd-utils: Permission mismatch for /var/lock/ directory

Package: drbd-utils Version: 9.22.0-1.1 Severity: important X-Debbugs-Cc: Helmut Grohne Hi! While analyzing the archive for mismatched file metadata (as part of the preparation to add support into dpkg), thanks to Helmut gathering the data from the archive. I noticed that this package has a mism

Bug#1082432: audit, rust-laurel: Permission mismatch for /etc/audit/ dirs

Source: audit, rust-laurel Severity: important X-Debbugs-Cc: Helmut Grohne Hi! While analyzing the archive for mismatched file metadata (as part of the preparation to add support into dpkg), thanks to Helmut gathering the data from the archive. I noticed that these two source packages generate b

Bug#1082430: krb5-kdc, krb5-keytab-backend: Permission mismatch for /etc/krb5kdc/

Package: krb5-kdc, krb5-keytab-backend Severity: important X-Debbugs-Cc: Helmut Grohne Hi! While analyzing the archive for mismatched file metadata (as part of the preparation to add support into dpkg), thanks to Helmut gathering the data from the archive. I noticed that these two packages have

Bug#1082275: dpkg-dev: powerpc ignores DEB_BUILD_MAINT_OPTIONS qa

Hi! On Thu, 2024-09-19 at 17:39:49 +0200, Drew Parsons wrote: > Package: dpkg-dev > Version: 1.22.11 > Severity: normal > dpkg-buildflags has started tightening build conditions such that > implicit declarations are now treated as errors (C flag > -Werror=implicit-function-declaration) > > This

Bug#1077904: ledmon FTBFS on 32-bit with gcc 14

Control: tags -1 patch Hi! On Sun, 2024-08-04 at 12:24:24 +0300, Adrian Bunk wrote: > Source: ledmon > Version: 0.97-1.1 > Severity: serious > Tags: ftbfs > https://buildd.debian.org/status/logs.php?pkg=ledmon&ver=0.97-1.1 > > ... > utils.c: In function ‘get_uint64’: > utils.c:105:18: error: pa

Bug#1074954: ffproxy: ftbfs with GCC-14

bprocess returned exit status 2 The attached patch fixes the build. Thanks, Guillem diff --git c/debian/patches/fix-incompat-ptr-types.patch i/debian/patches/fix-incompat-ptr-types.patch new file mode 100644 index 000..42f3f48 --- /dev/null +++ i/debian/patches/fix-incompat-ptr-types.patch @@

Bug#1081434: dpkg-source: should refuse to apply indented diffs, or at least give a warning

Hi! On Wed, 2024-09-11 at 16:43:24 +0100, Simon McVittie wrote: > Package: dpkg-dev > Version: 1.22.11 > Severity: normal > However, patch(1) and therefore dpkg-source looks for anything in the > patch text that looks vaguely diff-like, even if it's indented (!), and > applies it. The result is t

Bug#1080429: ITP: golang-github-mostynb-go-grpc-compression -- Go gRPC encoding wrappers for compression algorithms missing from google.golang.org/grpc

Package: wnpp Severity: wishlist Owner: Guillem Jover * Package name: golang-github-mostynb-go-grpc-compression Version : 1.2.3-1 Upstream Author : Mostyn Bramley-Moore * URL : https://github.com/mostynb/go-grpc-compression * License : Apache-2.0 Programming

Bug#1080428: ITP: golang-github-go-viper-mapstructure -- decode generic map values into native Go structures and vice versa

Package: wnpp Severity: wishlist Owner: Guillem Jover * Package name: golang-github-go-viper-mapstructure Version : 2.1.0-1 Upstream Author : Viper * URL : https://github.com/go-viper/mapstructure * License : Expat Programming Lang: Go Description

Bug#1080354: ITP: golang-opentelemetry-collector -- OpenTelemetry Collector (library)

Package: wnpp Severity: wishlist Owner: Guillem Jover * Package name: golang-opentelemetry-collector Version : 0.108.1-1 Upstream Author : OpenTelemetry - CNCF * URL : https://github.com/open-telemetry/opentelemetry-collector * License : Apache-2.0

Bug#1080351: ITP: golang-github-bboreham-go-loser -- Loser Tree data structure, for fast k-way merge

Package: wnpp Severity: wishlist Owner: Guillem Jover * Package name: golang-github-bboreham-go-loser Version : 0.0~git20230920.fcc2c21-1 Upstream Author : Bryan Boreham * URL : https://github.com/bboreham/go-loser * License : Apache-2.0 Programming Lang: Go

Bug#1080349: ITP: golang-github-victoriametrics-easyproto -- simple building blocks for protobuf marshaling and unmarshaling

Package: wnpp Severity: wishlist Owner: Guillem Jover * Package name: golang-github-victoriametrics-easyproto Version : 0.1.4-1 Upstream Author : VictoriaMetrics * URL : https://github.com/VictoriaMetrics/easyproto * License : Apache-2.0 Programming Lang: Go

Bug#1079967: should policy and dpkg agree on allowed versions?

Control: reassign -1 debian-policy Hi! On Wed, 2024-08-28 at 18:11:23 +0200, Helmut Grohne wrote: > Package: dpkg-dev,debian-policy > Severity: wishlist > X-Debbugs-Cc: po...@debian.org > Emilio and me noticed that policy and dpkg have subtly different ideas > of what is a version. While man deb

Bug#953932: Upcoming dropping of compat from libattr1-dev

Hi! This is a heads-up that I'm going to be dropping the "temporary" header that was dropped from libattr1-dev upstream more than 5 years ago, and where I added it back for backwards compatibility. Once I've done that upload, I'll increase the severity of these reports to serious. Most of these p

Bug#1073992: debconf: failure between unpack and configure dpkg runs via apt

Control: reassign -1 debconf Control: retitle -1 debconf: failure between unpack and configure dpkg runs via apt Hi! On Fri, 2024-06-21 at 10:53:20 +0300, Martin-Éric Racine wrote: > Package: pci.ids > Version: 0.0~2024.05.31-1 > Severity: normal > > Unpacking pci.ids (0.0~2024.05.31-1) over (0

Bug#1073992: pci.ids: configuration fails

Hi! On Sat, 2024-06-22 at 15:55:34 +0300, Martin-Éric Racine wrote: > la 22. kesäk. 2024 klo 14.39 Chris Hofstaedtler (z...@debian.org) kirjoitti: > > On Fri, Jun 21, 2024 at 01:42:59PM +0300, Martin-Éric Racine wrote: > > > APT logs and 'dpkg -L debconf' are attached. > > > > Could you also attac

Bug#1079768: resolvconf: Perform full /usr-move

: Guillem Jover Date: Mon, 27 Nov 2023 04:22:00 +0100 Subject: [PATCH 1/3] Add a debian/.gitignore file --- debian/.gitignore | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 debian/.gitignore diff --git a/debian/.gitignore b/debian/.gitignore new file mode 100644 index 000

Bug#1070123: attr FTBFS: -Werror=implicit-function-declaration triggers on basefile for missing libgen.h

Control: tags -1 - patch Hi! On Tue, 2024-04-30 at 13:52:52 +0200, Helmut Grohne wrote: > Source: attr > Version: 1:2.5.2-1 > Severity: important > Tags: ftbfs patch > User: helm...@debian.org > Usertags: rebootstrap > attr may fail to build from source with > -Werror=implicit-function-declarati

Bug#1079648: lvm2: Build fixes and improvements

: Guillem Jover Date: Sun, 25 Aug 2024 19:57:57 +0200 Subject: [PATCH 1/4] Check for grep and egrep explicitly in configure These macros were being pulled out transitively from other projects, but that has stopped happening now, and the build fails. As we explicitly use both the GREP and EGREP make

Bug#1079627: kmod: Build fixes and improvements

0 2001 From: Guillem Jover Date: Wed, 21 Aug 2024 19:03:46 +0200 Subject: [PATCH 1/9] Add a debian/.gitignore file This ignores all build artifacts and currently generated files from build tooling and helpers. --- debian/.gitignore | 12 1 file changed, 12 insertions(+) create mode 10

Bug#1079594: reiserfsprogs: Build fixes and improvements

ch as using absolute names for the files shipped by the package, instead of looking them up in PATH, and/or keeping the dh-sequence-movetousr part). Let me know, and I'm happy to rework them. Thanks, Guillem From 7f81050fc475b8eb881633a0a32a57d5ba453af7 Mon Sep 17 00:00:00 2001 From: Guillem J

Bug#1057238: debian-policy: Take dpkg-build-api into account for Rules-Requires-Root

Hi! On Sun, 2024-08-25 at 10:04:33 +0800, Sean Whitton wrote: > On Thu 15 Aug 2024 at 11:07am +02, Niels Thykier wrote: > > How about adding > > > > """ > > The default for Rules-Requires-Root depends on the dpkg-build-api level (the > > dpkg-build-api is defined in "man 7 dpkg-build-api"). At lev

Bug#1079573: fuse3: Perform full /usr-move

122eb980aeef9800921dc41cb427ab1cce95d987 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Sat, 24 Aug 2024 20:42:02 +0200 Subject: [PATCH] Use canonical pathnames in initramfs hook Perform a full /usr-move to make the pathname consistent with the actual location of the files being installed

Bug#1069256: debian-policy: clarify requirement for use of Static-Built-Using

Hi! On Sat, 2024-04-27 at 17:40:49 +0800, Maytham Alsudany wrote: > Thanks for your input and suggestions. I've attached an updated patch with > several changes, including improving making the description of the field more > specific, adding another example that is not Go/Rust related, and improvi

Bug#1079187: openmx: Build fixes

Source: openmx Source-Version: 3.8.5+dfsg1-1 Severity: normal Tags: patch Hi! This package patches the upstream build system to include a dpkg make fragment file so that it can pass build flags. This is rather unorthodox, and makes the patch non-eligible for upstream submission. And in addition,

Bug#1079186: devscripts: Includes dpkg make fragment file from subdir

Source: devscripts Source-Version: 2.24.1 Severity: normal Hi! This package includes the dpkg/vendor.mk fragment file from the scripts/Makefile, which does not reside in the source package root directory, which is not supported by the dpkg fragment files. This is now generating errors such as:

Bug#1079185: wine-development: Removes and generates debian/control at build time

Source: wine-development Source-Version: 8.21~repack-1 Severity: important Hi! This package regenerates the debian/control file on each build, from my reading of the archive https://ftp-master.debian.org/REJECT-FAQ.html, this is not allowed. I realize the regeneration is supposed to not change t

Bug#1079184: wine: Removes and generates debian/control at build time

Source: wine Source-Version: 9.0~repack-4 Severity: important Hi! This package regenerates the debian/control file on each build, from my reading of the archive https://ftp-master.debian.org/REJECT-FAQ.html, this is not allowed. I realize the regeneration is supposed to not change the content of

Bug#1076924: metadata

Hi! On Tue, 2024-08-13 at 17:33:58 +0200, Santiago Vila wrote: > El 13/8/24 a las 16:30, Guillem Jover escribió: > > I'm now closing it, because only with the fixed marking is not > > enough for the BTS, and it was being kept open. :) > > Yes, I was aware that &qu

Bug#1078998: cyrus-sasl2: Includes dpkg fragment Makefiles from subdir

From 39c9e6a3123a02d7d8e173d367fcda7a9382b80c Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Sun, 18 Aug 2024 02:18:12 +0200 Subject: [PATCH] debian: Fix and simplify sample server/client build We can use make's implicit rules to simplify the Makefile. We should also run the Makefile from the source tree root

Bug#1057238: debian-policy: Take dpkg-build-api into account for Rules-Requires-Root

Hi! On Thu, 2024-08-15 at 11:07:43 +0200, Niels Thykier wrote: > How about adding > > """ > The default for Rules-Requires-Root depends on the dpkg-build-api level (the > dpkg-build-api is defined in "man 7 dpkg-build-api"). At level 0 (or when > not declared), Rules-Requires-Root defaults to bin

Bug#1064454: debian-policy: Restrict deb822 field names more

f dpkg fails I'd assume that might be a side effect from something else, and it might make sense to make sure this is handled explicitly. Thanks, Guillem From 9b284029b29b3f27cc478198f7de73dfed61cf6d Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Fri, 16 Aug 2024 19:59:51 +0200 Subject: [PATCH] D

Bug#1076788: adequate: Messes up the console apt was running from

Control: forcemerge -1 1077210 Control: reassign -1 adequate Control: affects -1 apt Control: severity -1 serious Control: retitle -1 adequate: Messes up the console apt was running from Hi! [ Merged both bugs, as I see adequate being setup in both systems. ] On Tue, 2024-07-23 at 13:08:19 +0300

Bug#1078183: dpkg: Problems with CTRL+C and text consoles.

Hi! [ The quoting in your previous message got mangled, so it was a bit hard to read. ] On Thu, 2024-08-08 at 16:53:07 +0200, Santiago José López Borrazás wrote: > El 8/8/24 a las 13:09, Guillem Jover escribió: > > Hmm, I can still not reproduce it with dpkg, while I can with

Bug#1078183: dpkg: Problems with CTRL+C and text consoles.

Hi! On Thu, 2024-08-08 at 08:10:29 +0200, Santiago José López Borrazás wrote: > El 8/8/24 a las 02:27, Guillem Jover escribió: > > Well, I can very easily reproduce this with apt or aptitude, but not > > with dpkg alone. Just to make sure, before you call dpkg, Ctrl+C works, > &

Bug#1078183: dpkg: Problems with CTRL+C and text consoles.

Hi! On Thu, 2024-08-08 at 01:31:34 +0200, Santiago José López Borrazás wrote: > El 8/8/24 a las 01:21, Guillem Jover escribió: > > Have you really experienced this after running dpkg standalone > > (without using apt or aptitude) on a terminal where Ctrl+C is still > > workin

Bug#1078183: dpkg: Problems with CTRL+C and text consoles.

Control: tags -1 unreproducible moreinfo Hi! On Thu, 2024-08-08 at 00:05:38 +0200, Santiago José López Borrazás wrote: > Package: dpkg > Version: 1.22.11 > Severity: important > With dpkg, when I am in console mode, with konsole, the combination > CTRL + C breaks. Non-graphical consoles break wh

Bug#1067087: dpkg-buildflags: Enable frame pointers by default

Control: tags 1058664 moreinfo Control: forcemerge 1058664 -1 Hi! [ Merging with the other dupes. :) ] On Sat, 2024-04-06 at 01:48:04 +0200, Guillem Jover wrote: > Control: tags -1 moreinfo > Control: retitle -1 dpkg-buildflags: Enable frame pointers by default > > On Mon, 2024-03

Bug#1070027: apt: daily systemd service handles dpkg frontend locking incorrectly?

wrote: > Control: reopen -1 > Control: severity -1 important > > On 2024-07-11 00:49:20 +0200, Guillem Jover wrote: > > libdpkg: Try to print the executable name of the lock contending process > > > > Just printing the PID is not very useful to try to track dow

Bug#1078103: piuparts: dpkg has been marked as cannot-be-tested for a while

Package: piuparts Version: 1.4.2 Severity: normal Hi! I'm not sure when this started, but I think it's been a while now, probably several months, perhaps more? The dpkg package has been marked as cannot-be-tested, from logs such as

Bug#1077871: debtags: Add new time related tags

Package: debtags Version: 2.1.5 Severity: wishlist Hi! It would be nice to add time related tags. The ones that come to mind are at least: works-with:time admin:time These would be useful for things like NTP daemons, or tools that set the clock, or even clock or calendar applications. Than

Bug#735497: closed by Debian FTP Masters (Bug#1076502: Removed package(s) from unstable)

d bug reports. We are sorry > that we couldn't deal with your issue properly. > > For details on the removal, please see https://bugs.debian.org/1076502 Bug still relevant, reopening and reassigning. Keeping the original bug report below for context. > Date: Wed, 15 Jan 2014 2

Bug#1076892: libzen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file

Control: reassign -1 libdpkg-perl 1.22.7 Control: retitle -1 "libdpkg-perl: Angle bracket symbol normalization incorrectly applies to operators" Control: affects -1 libzen Hi! On Sun, 2024-07-28 at 15:16:58 +0800, Chow Loong Jin wrote: > This looks like an issue with dpkg-gensymbols -- in the di

Bug#1076904: [Pkg-javascript-devel] Bug#1076904: pkg-js-tools: FTBFS: help2man: can't get `--version' info from ./tools/debcheck-node-repo

Control: reopen -1 Control: notfixed -1 dpkg/1.22.9 Control: affect -1 = src:pkg-js-tools Control: retitle -1 dpkg-dev: Make fragments lack internal dpkg_lazy_eval macros Control: tags -1 = On Fri, 2024-07-26 at 15:21:16 +0200, Santiago Vila wrote: > unmerge 1076904 > thanks > Hi. I can indeed re

Bug#1077005: CFLAGS+=foo etc stopped working

Hi! On Fri, 2024-07-26 at 13:20:28 +0200, Nicolas Boulenguez wrote: > > Hmm, at this point I'm starting to ponder whether to revert the > > optimization commit for the Makefile fragment files, because this > > is starting to feel like too much breakage, and then the fragment > > code is becoming t

Bug#1077005: CFLAGS+=foo etc stopped working

Hi! On Thu, 2024-07-25 at 10:19:28 +0300, Michael Tokarev wrote: > Package: dpkg-dev > Version: 1.22.8 > Severity: important > It seems like constructs like > > include /usr/share/dpkg/buildflags.mk > CFLAGS += -DFOO > LDFLAGS += -lbar > > etc somehow stopped working on buildds since dpkg

Bug#1076863: dpkg-deb: Weird errors from dpkg-deb while building some packages

Hi On Wed, 2024-07-24 at 16:35:44 +0200, Guillem Jover wrote: > On Wed, 2024-07-24 at 14:37:53 +0200, Guillem Jover wrote: > > Both look like the same problem, which would be a regression from the > > recent rework of the Makefile fragments. I'm CCing Nicolas as a > >

Bug#1076863: dpkg-deb: Weird errors from dpkg-deb while building some packages

Hi! On Wed, 2024-07-24 at 14:37:53 +0200, Guillem Jover wrote: > Both look like the same problem, which would be a regression from the > recent rework of the Makefile fragments. I'm CCing Nicolas as a > heads-up, and I'm looking into this to try to do a quick fix upload. S

Bug#1076863: dpkg-deb: Weird errors from dpkg-deb while building some packages

Control: forcemerge -1 1076939 Hi! On Wed, 2024-07-24 at 12:17:21 +0200, Santiago Vila wrote: > Package: dpkg > Version: 1.22.8 > While building some packages I get weird errors like this: > > dpkg-deb: building package 'aspell-nl' in '../aspell-nl_2.20.19-2_all.deb'. > dpkg-deb: building packa

Bug#1076568: dpkg: no longer evaluates variables in DEB_CPPFLAGS_MAINT_APPEND

Hi! On Fri, 2024-07-19 at 14:49:20 +0200, Nicolas Boulenguez wrote: > Previous implementation was preventing one expansion with $(value), > but this quotation is now counter-productive. > > Three commits are attached: > 2/ regression test > 3/ patch > 1/ an unrelated suggestion inspired by thi

Bug#1076568: dpkg: no longer evaluates variables in DEB_CPPFLAGS_MAINT_APPEND

Hi! On Fri, 2024-07-19 at 04:02:18 +0200, Andreas Beckmann wrote: > Package: dpkg > Version: 1.22.7 > Severity: important > X-Debbugs-Cc: Graham Inggs > I suspect dpkg 1.22.7 to cause a regression when building > nvidia-cuda-toolkit, e.g. > > https://buildd.debian.org/status/fetch.php?pkg=nvidi

Bug#1076511: dpkg: should --force-remove-essential imply --force-remove-protected?

Hi! On Thu, 2024-07-18 at 01:30:48 +0200, Guillem Jover wrote: > > A workaround is to detect the dpkg version in use, and if it's >= 1.20.1, > > add --force-remove-protected to the dpkg command-line. > > The expected way to detect whether you might need to pass tha

Bug#1076511: dpkg: should --force-remove-essential imply --force-remove-protected?

Hi! On Wed, 2024-07-17 at 15:24:36 +0100, Simon McVittie wrote: > Package: dpkg > Version: 1.21.22 > Severity: wishlist > Before Debian trixie, login was Essential; now it's merely Protected > (included in normal installations, but removable). > > In minimal container environments where logins a

Bug#1075993: dpkg: Please allow merge requests on Salsa

Hi! On Wed, 2024-07-10 at 22:45:01 -0700, Otto Kekäläinen wrote: > > > Please allow Merge Requests at https://salsa.debian.org/dpkg-team/dpkg > > > so that it is easier for others to contribute to the package. > > > > These repos are just mirrors (I've updated the repo descriptions there > > now),

Bug#1076061: cppcheck: Syntax error on func(&data)[0] valid C code

Package: cppcheck Version: 2.14.0-1 Severity: important Hi! I just stumbled over the following issue after some code changes in dpkg, which is currently failing one of its CI (the one in salsa) due to this, but I'll modify the involved code to avoid this though. It seems cppcheck does not handle

Bug#805592: adequate: Please check pid file permissions

Hola! On Sat, 2024-06-15 at 21:29:35 +0200, Serafeim Zanikolas wrote: > do you think that this bug is still relevant, especially with most daemons now > being handled internally by systemd? Personally I think portability is very important, and systemd being Linux-only, it means any other port can

Bug#872381: dpkg-dev: optimize Makefile snippets for debian/rules

Hi! On Mon, 2024-07-01 at 04:43:40 +0200, Guillem Jover wrote: > On Sat, 2024-06-29 at 17:29:49 +0200, Guillem Jover wrote: > > There's another regression that I found on various BSDs, where they > > already have GNU make 4.4.1, where the buildtools test fails for the >

Bug#872381: dpkg-dev: optimize Makefile snippets for debian/rules

Hi! On Sat, 2024-06-29 at 17:29:49 +0200, Guillem Jover wrote: > There's another regression that I found on various BSDs, where they > already have GNU make 4.4.1, where the buildtools test fails for the > AR and AR_FOR_BUILD checks, and I've not managed to track down yet &g

Bug#872381: dpkg-dev: optimize Makefile snippets for debian/rules

Hi! On Mon, 2024-05-06 at 12:32:45 +0200, Nicolas Boulenguez wrote: > You have not applied > 0001-scripts-mk-stop-hard-coding-dpkg_datadir.patch > probably because you prefer the related parts in > f1175056 (build: Rework subst handling for built or installed artifacts). As I think I mentione

Bug#1074135: lintian: error due to login no longer being Essential:yes

Package: lintian Version: 2.117.0 Severity: important X-Debbugs-Cc: Chris Hofstaedtler Hi! Since shadow 1:4.15.1-1, the login package is no longer Essential:yes, instead it is now Protected:yes. But lintian still considers it the former and emits an error tag when a package Depends on login, whi

Bug#1073608: mksh: move aliased files from / to /usr (DEP17)

Hi! On Thu, 2024-06-20 at 23:27:07 +, Thorsten Glaser wrote: > Dixi quod… > >Or, better yet, absence of that entry in the ustar (possibly > >combined with a Pre-Depends). It’s ridiculous that every pak‐ > >kage ships all those directory entries anyway. That avoids These directories are includ

Bug#1073992: pci.ids: configuration fails

Hi! There is not enough context in the report to really see what's going on here. On Fri, 2024-06-21 at 10:53:20 +0300, Martin-Éric Racine wrote: > Package: pci.ids > Version: 0.0~2024.05.31-1 > Severity: normal > Unpacking pci.ids (0.0~2024.05.31-1) over (0.0~2024.04.20-1) ... > debconf: Unable

Bug#1023619: , Bug#1053715: libx86emu: Add riscv64 and loong64 support

Control: tag 1023619 - patch Hi! On Tue, 2022-11-08 at 01:58:30 +0800, Yifan Xu wrote: > Source: libx86emu > Version: 3.5-1 > Severity: wishlist > Tags: ftbfs patch > User: debian-ri...@lists.debian.org > Usertags: riscv64 > X-Debbugs-Cc: debian-ri...@lists.debian.org > Please enable riscv64 arc

Bug#1073038: po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext

Hi! On Thu, 2024-06-13 at 00:45:14 +0200, Martin Quinson wrote: > Le jeudi 13 juin 2024 à 00:29 +0200, Guillem Jover a écrit : > > On Thu, 2024-06-13 at 00:02:43 +0200, Martin Quinson wrote: > > > The problem is that Perl has a rather unexpected behavior wrt utf8, UTF-8 >

Bug#1073038: po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext

Hi! On Thu, 2024-06-13 at 00:02:43 +0200, Martin Quinson wrote: > Le mercredi 12 juin 2024 à 17:14 +0200, Guillem Jover a écrit : > > I think the charset comparison is too naive though, and does not cover > > for example any aliases listed in «man Encode::Supported». I thi

Bug#1073038: po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext

Hi! On Wed, 2024-06-12 at 15:42:57 +0200, Guillem Jover wrote: > On Wed, 2024-06-12 at 10:36:52 +0200, Martin Quinson wrote: > > Le mercredi 12 juin 2024 à 04:47 +0200, Guillem Jover a écrit : > > > Package: po4a > > > Version: 0.70 > > > Severity: serious &

Bug#1073038: po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext

Hi! On Wed, 2024-06-12 at 10:36:52 +0200, Martin Quinson wrote: > Le mercredi 12 juin 2024 à 04:47 +0200, Guillem Jover a écrit : > > Package: po4a > > Version: 0.70 > > Severity: serious > > When building dpkg, it now fails with something like this: > > >

Bug#1073038: po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext

Package: po4a Version: 0.70 Severity: serious Hi! When building dpkg, it now fails with something like this: ,--- Making check in man make[1]: Entering directory '/dpkg/man' /usr/bin/po4a --previous --srcdir . --destdir . --no-backups --porefs file --msgmerge-opt=--add-location=file --p

Bug#1069498: libx86emu: FTBFS on armhf: mem.c:581:12: error: implicit declaration of function ‘inb’; did you mean ‘ins’? [-Werror=implicit-function-declaration]

Control: tag -1 patch [ CCing debian-arm list to loop them into the porting issue. ] Hi! On Fri, 2024-06-07 at 14:42:18 +0200, Guillem Jover wrote: > On Sat, 2024-04-20 at 14:56:40 +0200, Lucas Nussbaum wrote: > > Source: libx86emu > > Version: 3.5-1 > > Severity: seri

Bug#1069426: nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined

Control: tag -1 patch Hi! On Sat, 2024-04-20 at 15:01:27 +0200, Lucas Nussbaum wrote: > Source: nocache > Version: 1.1-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf > During a rebuild of all

  1   2   3   4   5   6   7   8   9   10   >