Bug#944972: opensvc: Module accesses internal dpkg database

Source: opensvc Source-Version: 1.8~20170412-3 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package ships a module («lib/rcPkgLinux.py»), which directly accesses the dpkg internal database, instead of using one of the public interfaces provided

Bug#944970: salt: Modules access internal dpkg databases

Source: salt Source-Version: 2018.3.4+dfsg1-7 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package contains modules («salt/modules/dpkg.py» and «salt/modules/alternatives.py»), which directly access the dpkg internal database, instead of using

Bug#944968: popularity-contest: Program accesses internal dpkg database

Source: popularity-contest Source-Version: 1.69 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package contains the «popularity-contest» program, which directly accesses the dpkg internal database, instead of using one of the public interfaces

Bug#944967: multistrap: Script accesses internal dpkg database

Source: multistrap Source-Version: 2.2.10 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-ctrl Hi! This package contains the «multistrap» program, which directly accesses the dpkg internal database, instead of using one of the public interfaces provided by dpkg.

Bug#944966: ruby-debian: Module accesses internal dpkg database

Source: ruby-debian Source-Version: 0.3.10 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package contains the «debian» module, which directly accesses the dpkg internal database, instead of using one of the public interfaces provided by dpkg.

Bug#944965: debsums: Script accesses internal dpkg database

Source: debsums Source-Version: 2.2.4 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package contains the «debsums» program, which directly accesses the dpkg internal database, instead of using one of the public interfaces provided by dpkg. The

Bug#944964: dh-make-perl: Module accesses internal dpkg database

Source: dh-make-perl Source-Version: 0.107 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package contains a perl module [M], which directly accesses the dpkg internal database. Instead of using one of the public interfaces provided by dpkg.

Bug#944963: debian-goodies: Scripts access internal dpkg database

Source: debian-goodies Source-Version: 0.84 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package programs («which-pkg-broke» and «dglob»), which directly accesses the dpkg internal database, instead of using one of the public interfaces

Bug#944951: cabal-debian: Code accesses internal dpkg database

Source: cabal-debian Source-Version: 5.0-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package contains a module («src/Debian/Debianize/Prelude.hs»), which directly accesses the dpkg internal database, instead of using one of the public

Bug#944926: cruft: Scripts access internal dpkg databases

Package: cruft Version: 0.9.38 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-db-access-blocker Hi! This package contains several scripts [S], which directly accesses the dpkg internal database. Instead of using one of the public interfaces provided by dpkg. The file

Bug#935772: libbsd0: lacks strnvisx

Hi! On Mon, 2019-08-26 at 02:39:32 +, brian m. carlson wrote: > Package: libbsd0 > Version: 0.10.0-1 > Severity: normal > libbsd0 seems to have several of the vis(3) functions and documents > strnvisx(3), but it isn't in the shared library: > > $ nm -D

Bug#944083: libbsd-dev: Lacks user_from_uid() & uid_from_user() functions

Hi! On Sun, 2019-11-03 at 23:37:39 +0100, Robert Luberda wrote: > Package: libbsd-dev > Version: 0.10.0-1 > Severity: wishlist > I'm trying to prepare new version of bsd-mailx package from the OpenBSD > repository, but it unfortunatelly fails to compile because they switched > to using to

Bug#944837: ladvd: Switch from pciutils to pci.ids

Package: ladvd Version: 1.1.2-1 Severity: normal Hi! This package depends on the pciutils package to get the pci.ids database, even though it does not use it directly. The database has now been split into its own source and binary package so that it can updated more regularly, and be depended

Bug#944836: discover-data: Embeds old copies of pci.ids and usb.ids

Source: discover-data Source-Version: 2.2013.01.11 Severity: normal Hi! This package embeds old copies of the pci.ids and usb.ids databases which get converted into xml files. These databases are now packaged on their own source and binary packages so that it's very easy to update regularly.

Bug#944835: lsvpd: Missing dependencies on pci.ids and usb.ids

Package: lsvpd Version: 1.7.9-1 Severity: normal Hi! This package loads and parses the pci.ids and usb.ids databases directly in «src/internal/devicelookup.cpp», but it does not declare a dependency on the pci.ids and usb.ids packages. Please add them. Thanks, Guillem

Bug#944296: debian-policy: Source provenance requirement is WET

On Sat, 2019-11-09 at 08:55:23 -0700, Sean Whitton wrote: > On Thu 07 Nov 2019 at 09:00AM -08, Russ Allbery wrote: > > I'm in favor of dropping this information from debian/copyright and > > instead writing some language saying that packages should include this > > information in Homepage in

Bug#919190: keepassxc-browser status?

Hi! On Thu, 2019-11-14 at 19:23:08 +0800, Bruno Kleinert wrote: > Am Donnerstag, den 14.11.2019, 12:03 +0100 schrieb Guillem Jover: > > I noticed that the keepassxc-browser packages that were sitting in > > NEW(<https://ftp-master.debian.org/new.html>;), disappeared

Bug#944834: ddcutil: Missing dependencies on pci.ids and usb.ids

Package: ddcutil Version: 0.9.7-1 Severity: normal Hi! This package is loading and parsing the pci.ids and usb.ids databases in «src/util/device_id_util.c», but it does not declare a dependency on them. Please add these as Depends. Thanks, Guillem

Bug#944833: nvme-cli: Bogus debian/source/include-binaries?

Source: nvme-cli Source-Version: 1.7-1 Severity: normal Hi! While checking the source for this package I noticed that it contains a debian/source/include-binaries with a bunch of *.o files. This seems bogus as these files should not get included in the source package. Thanks, Guillem

Bug#944832: nvme-cli: Missing dependency on pci.ids

Package: nvme-cli Version: 1.7-1 Severity: normal Hi! This package tries to parse the pci.ids database (in nvme-models.c), but it does not have a dependency on a package providing it. You should add a dependency on the pci.ids package. Thanks, Guillem

Bug#944830: ricks-amdgpu-utils: Please switch to use pci.ids package

Source: ricks-amdgpu-utils Source-Version: 2.6.0-1 Severity: wishlist Hi! The python3-gpumodules binary package embeds a copy of the pci.ids database. This database is now packaged on its own source and binary packages, so that it can be updated more regularly, and so that dependencies do not

Bug#919190: keepassxc-browser status?

Hi! I noticed that the keepassxc-browser packages that were sitting in NEW (), disappeared from there and are not in the archive either. Does this mean they got REJECTED? Thanks, Guillem

Bug#944364: dpkg: ldconfig is not invoked for Depends or even Pre-Depends

Control: reassign -1 python3-augeas Control: severity -1 serious Hi! On Sat, 2019-11-09 at 11:06:15 +0100, Jakub Wilk wrote: > * Alexander Thomas , 2019-11-08, 15:50: > > Traceback (most recent call last): > > File "/usr/lib/the-package/setup-package.py", line 3, in > >from augeas import

Bug#944629: RFP: libcatalyst-plugin-session-store-redis-perl -- Redis Session store for Catalyst

Package: wnpp Severity: wishlist Tags: patch * Package name: libcatalyst-plugin-session-store-redis-perl Version : 0.09 Upstream Author : Thomas Klausner * URL : https://metacpan.org/release/Catalyst-Plugin-Session-Store-Redis * License : Artistic or GPL-1+

Bug#944588: lib-st-console-perl: Strange naming convention for a perl package

Package: lib-st-console-perl Version: 1.1.4-1 Severity: normal Hi! This package uses a non-standard naming convention for a perl module. Usually perl modules follow the policy of taking the base name of the hierarchy provided and normalizing that into a package name. For this case that would be

Bug#944503: lshw: Can switch from pciutils and usbitils to pci.ids and usb.ids

Source: lshw Source-Version: 02.18.85-0.3 Severity: normal Hi! The PCI and USB ID databases have been split into their own source and binary packages so that they can be updated more regularly, and can be depended on w/o having to pull in the tools. The Recommends could be switched to a Depends

Bug#944502: libosinfo: Can switch from pciutils and usbitils to pci.ids and usb.ids

Source: libosinfo Source-Version: 1.6.0-1 Severity: normal The PCI and USB ID databases have been split into their own source and binary packages so that they can be updated more regularly, and can be depended on w/o having to pull in the tools. The Build-Depends and the Depends in

Bug#944500: hwdata: Can switch from pciutils and usbitils to pci.ids and usb.ids

Package: hwdata Version: 0.290-1 Severity: normal The PCI and USB ID databases have been split into their own source and binary packages so that they can be updated more regularly, and can be depended on w/o having to pull in the tools. The Depends could be switched from pciutils to pci.ids and

Bug#944498: libpciaccess0: Can switch from Suggests pciutils to Depends pci.ids

Package: libpciaccess0 Version: 0.14-1 Severity: normal Hi! I've split the pci.ids database into its own source and binary package, which means this package could switch to a Depends (or perhaps a Recommends if that's too much), w/o having to pull in any tools package anymore. Thanks, Guillem

Bug#944332: debian-policy: Broken markup in policy source

Source: debian-policy Source-Version: 4.4.1.1 Severity: normal Hi! Found this markup issue while going over the policy: - chapter 4, footnote [6], rendered as: ,--- listed in the :ref:"`Maintainer" <#s-f-Maintainer` or "`Uploaders" ` control fields of the package), the first line

Bug#944331: debian-policy: Spurious space after dash in plain text output

Package: debian-policy Version: 4.4.1 Severity: minor Hi! Noticed the following instances of spurious spaces after a dash, while skimming over the plain text policy document: - index, rendered as: ,--- * 7.8. Additional source packages used to build the binary - "Built- Using"

Bug#944330: debian-policy: Hyphenation damage on plain text output

Package: debian-policy Version: 4.4.1 Severity: minor Hi! The rendering to plain text contain many technical terms, program names, email addresses, make rule names, etc., that have been cut at their hypen at the end of line. This makes copy more difficult, and it reads confusingly. I started

Bug#944329: debian-policy: Unclear text about password files modifications

Package: debian-policy Version: 4.4.1 Severity: normal Hi! There's this text in section §9.2.1: ,--- Packages other than "base-passwd" must not modify "/etc/passwd", "/etc/shadow", "/etc/group" or "/etc/gshadow". `--- It's not clear to me, whether this refers to the packaging or any

Bug#944296: debian-policy: Source provenance requirement is WET

On Thu, 2019-11-07 at 09:00:29 -0800, Russ Allbery wrote: > Guillem Jover writes: > > This means that when using a debian/watch file one has to duplicate > > the information in two places, with the possibility of this getting > > out-of-sync, etc. > > > In additi

Bug#944296: debian-policy: Source provenance requirement is WET

Package: debian-policy Version: 4.4.1.1 Severity: wishlist Hi! We currently require (with a must) in section §12.5, to add to the debian/copyright, where the upstream source was obtained from: ,--- In addition, the copyright file must say where the upstream sources (if any) were obtained,

Bug#944155: lintian: Version format vs source format mismatch tags disappeared

Hi! On Tue, 2019-11-05 at 03:39:19 -0800, Felix Lechner wrote: > On Tue, Nov 5, 2019 at 2:27 AM Guillem Jover wrote: > > At least the following tags: > > have disappeared, > > > > debian-changelog-version-requires-debian-revision > > hyphen-in-native-debian

Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

Hi! On Sat, 2019-11-02 at 16:31:24 +0100, intrigeri wrote: > Guillem Jover: > > On Sat, 2019-07-27 at 12:20:00 -0300, intrigeri wrote: > >> Oh, this is very interesting, thanks! I had taken a look at that > >> module, but from the documentation I understood it onl

Bug#944155: lintian: Version format vs source format mismatch tags disappeared

Package: lintian Version: 2.32.0 Severity: normal Hi! At least the following tags: debian-changelog-version-requires-debian-revision hyphen-in-native-debian-changelog-version latest-debian-changelog-entry-changed-to-native have disappeared, I suspect because dpkg-source does not allow a

Bug#791362: perl: build timezone affects LOCALTIME_{MIN,MAX}

Hi! On Wed, 2019-10-23 at 22:40:00 +0300, Niko Tyni wrote: > On Fri, Jul 03, 2015 at 11:16:46PM +0300, Niko Tyni wrote: > > On Mon, May 04, 2015 at 02:28:04PM +0200, Jérémy Bobbio wrote: > > > Another issue that surfaced now that we are doing timezone variations is > > > that LOCALTIME_MIN and

Bug#943586: lintian: confusing usage+internal+warning messages on binary packages

Package: lintian Version: 2.30.0 Severity: normal Hi! I'm getting this when checking a binary package explicitly, which is rather confusing when not using the --verbose option, as I initially thought it did not lint the package at all: ,--- $ lintian -v libdpkg-dev_1.20.0_amd64.deb N:

Bug#942813: debhelper: Passes unknown options to autoconf configure

From 5e9e36b7a0bcfca992c6a82e104be892efee6a60 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Mon, 21 Oct 2019 23:35:32 +0200 Subject: [PATCH] autoconf.pm: Do not check for unknown --disable/enable/with/without-* options By default autoconf will check for unknown --disable/enable/with/withouth

Bug#942416: khard: Split huge example files into a different package?

Hi! On Wed, 2019-10-16 at 00:27:00 +0200, Guillem Jover wrote: > Package: khard > Version: 0.14.0-2 > Severity: wishlist > The khard packages uses 10 MiB when installed, alsmost 9 of which are > taken by a couple of .wav files in the examples directory. Could the > twinkle stu

Bug#942416: khard: Split huge example files into a different package?

Package: khard Version: 0.14.0-2 Severity: wishlist Hi! The khard packages uses 10 MiB when installed, alsmost 9 of which are taken by a couple of .wav files in the examples directory. Could the twinkle stuff (or perhaps all the examples) be split into a different khard-examples package or

Bug#942315: tcpdump: Version in oldoldstable is higher than oldstable and stable

Package: tcpdump Version: 4.9.2-1~deb9u1 Severity: serious Tags: stretch buster Hi! With the latest upload to oldoldstable-security, the versions in oldstable and stable are now lower. This means that upgrades will not take effect for this package, which will be left built against libraries and

Bug#939516: [PATCH] d/rules: replace custom rule for 'configure' with call to dh_autoreconf

Control: tags -1 patch Hi! On Thu, 2019-09-05 at 16:27:38 -0400, Dan Streetman wrote: > Having a custom rule to create 'configure' means that if the file > may not get correctly rebuilt; instead dh_autoreconf should be > called to make sure it is always correctly rebuilt. Thanks for the patch!

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

On Sat, 2019-10-12 at 09:29:18 +0200, Ansgar wrote: > Guillem Jover writes: > > On Thu, 2019-10-10 at 09:44:21 +0200, Ansgar wrote: > >> Guillem Jover writes: > >> > On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: > >> >> With the first binNMU

Bug#940571: dpkg-buildflags should support an optimization area for things like lto and pgo

On Thu, 2019-10-10 at 10:39:23 +0200, Matthias Klose wrote: > On 09.10.19 20:28, Guillem Jover wrote: > > I take you are requesting both adding this and also enabling LTO by > > default? > > the infrastructure should provide both, having the option to enable it

Bug#942111: dpkg,debhelper: please set HOME, XDG_* to a temporary location during the build

Control: reassign -1 dpkg-dev,debhelper Hi! On Thu, 2019-10-10 at 14:58:11 +0100, Simon McVittie wrote: > Package: dpkg,debhelper > Severity: wishlist > I'm reporting this feature request against both dpkg and debhelper because > I don't yet know whether it's feasible to implement in debhelper,

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

On Thu, 2019-10-10 at 09:44:21 +0200, Ansgar wrote: > Guillem Jover writes: > > On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: > >> With the first binNMU the changelog used 5.2.17+1+b1 as the version > >> and this caused disagreement between different parts of dpkg.

Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1

Control: reassign -1 dpkg-dev/1.18.25 On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: > Package: dpkg > Version: 1.18.25 > Severity: normal > For the Secure Boot support in Debian we automatically generate source > packages that include the signatures (linux-signed-*) from files > shipped in

Bug#288822: marked as done (developers-reference: "Bugs" control field not documented)

On Tue, 2019-10-08 at 10:33:46 +, Holger Levsen wrote: > On Tue, Oct 08, 2019 at 12:30:50PM +0200, Guillem Jover wrote: > > > I don't really understand "#288822: developers-reference: "Bugs" control > > > field > > > not documented" and I'm n

Bug#940571: dpkg-buildflags should support an optimization area for things like lto and pgo

Control: tag -1 - patch + moreinfo Control: retitle -1 dpkg-buildflags: Add support for an optimize area for things like LTO On Tue, 2019-09-17 at 14:36:44 +0200, Matthias Klose wrote: > Package: src:dpkg > Version: 1.19.7 > Tags: patch > Please add an optimization area (opt, optimization) for

Bug#288822: marked as done (developers-reference: "Bugs" control field not documented)

Hi! On Tue, 2019-10-08 at 10:09:08 +, Debian Bug Tracking System wrote: > Date: Tue, 8 Oct 2019 10:05:05 + > From: Holger Levsen > To: 288822-d...@bugs.debian.org > Subject: bug purpose vague and unclear > Message-ID: <20191008100505.grkghleotjlxn...@layer-acht.org> > I don't really

Bug#941803: debian-policy: dependencies on font packages

Hi! On Sat, 2019-10-05 at 21:44:25 +0200, Stephen Kitt wrote: > Package: debian-policy > Version: 4.4.1.1 > Severity: normal > Policy section 11.8.5, point 1 says > > > If one or more of the fonts so packaged are necessary for proper > > operation of the package with which they are associated

Bug#639086: jhbuild: Missing moduleset DTD and schemas

Hi! On Sun, 2019-09-29 at 17:53:44 -0400, Jeremy Bicha wrote: > The general opinion is that people should download the moduleset > they want from > https://gitlab.gnome.org/GNOME/jhbuild/tree/master/modulesets/ > > jhbuild upstream used to keep old versioned modulesets around. Now > they don't

Bug#940748: lintian: False positives on debug-symbol-migration-possibly-complete

On Sat, 2019-09-21 at 20:25:50 +0200, Chris Lamb wrote: > > Was recently introducing an automatic debug symbol package, and got > > this lintian warning, which seems just wrong. I think the correct way > > to go about emitting it would be to: > Thanks for the implementation idea. However, could

Bug#935607: lintian: classify "Starting $DESC" in init.d scripts

On Wed, 2019-09-11 at 16:50:54 +, Dmitry Bogatov wrote: > [2019-09-08 21:26] "Chris Lamb" > > > unwanted and to be fixed. > > > > ... but, unless I'm missing something you can surely do that now > > almost trivially using codesearch.debian.net and certainly much > > quicker, independetly and

Bug#940878: lintian: Matches non-supported substvars

Package: lintian Version: 2.22.0 Severity: minor Hi! [ Commented in passing in #935138, filing it now to not get it lost. ] I notice that the code matching the source version substvars will now match the non-supported substvar Source-:Upstream-Version. I guess the easiest way to fix that is to

Bug#940877: lintian: Wrongly emits unreleased-changelog-distribution for unreleased suite

Package: lintian Version: 2.22.0 Severity: normal Hi! [ I posted this at but as one never knows whether salsa is black-holing stuff, and it makes it difficult to track this kind of

Bug#940748: lintian: False positives on debug-symbol-migration-possibly-complete

Package: lintian Version: 2.21.0 Severity: normal Hi! Was recently introducing an automatic debug symbol package, and got this lintian warning, which seems just wrong. I think the correct way to go about emitting it would be to: - Check for the m/--(?:ddeb|dbgsym)-migration=/ and extract the

Bug#929062: Updated and reworked log4cplus packaging

and mark as affecting this package. Thanks, Guillem From 7b08ac0a56db8c3ef2d52a8fa77021d27f8d464b Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Thu, 19 Sep 2019 00:01:03 +0200 Subject: [PATCH 01/16] Switch to automatically generated debug packages --- debian/changelog | 6 ++ debian

Bug#940234: debian-policy: add a section about source reproducibility

On Sat, 2019-09-14 at 08:58:21 -0700, Sean Whitton wrote: > On Sat 14 Sep 2019 at 02:01PM +00, Holger Levsen wrote: > > On Sat, Sep 14, 2019 at 01:34:49PM +0200, Aurelien Jarno wrote: > >> There is already a section about reproducibility in the debian-policy, > >> but it only mentions the binary

Bug#939969: dpkg-buildflags sets C++ incompatible warning implicit-function-declaration if qa=+all is used

Hi! On Tue, 2019-09-10 at 16:57:05 +0200, Paul Dreik wrote: > Package: dpkg > Version: 1.19.7 > Severity: normal > I use dpkg-buildflags in my continuous integration script, to make > sure my software (rdfind, available in debian) will build ok when the official > rdfind package is built. I

Bug#939997: dpkg: Please expose other data to post-invoke and pre-invoke commands

Hi! On Tue, 2019-09-10 at 16:39:22 -0500, Matt Zagrabelny wrote: > Package: dpkg > Version: 1.19.7 > Severity: wishlist > I would like to access other meta data (besides DPKG_HOOK_ACTION) when > running various pre/post-invoke commands. > > Would you consider exposing: > >

Bug#939998: systemd-logind: Assert due to insufficient function return checks

Source: systemd Source-Version: 241-7~deb10u1 Severity: important Tags: upstream patch buster Hi! We hit an assert in logind from the latest systemd package in buster: systemd-logind coredumped: in log_assert_failed_realm ... at ../src/basic/log.c:795 Investiaging from the following stack

Bug#939819: mariadb-10.3: Replication hangs with "preparing" and never starts

Source: mariadb-10.3 Source-Version: 1:10.3.17-0+deb10u1 Severity: serious Forwarded: https://jira.mariadb.org/browse/MDEV-20247 Hi! It seems like there's a serious regression in the latest stable update, fixed already in upstream in 10.3.18, where replication malfunctions. Please see the

Bug#816693: ftp.debian.org: Please add new 'perl6' section

Hi! On Fri, 2016-03-04 at 14:02:44 +0100, Dominique Dumont wrote: > Package: ftp.debian.org > Severity: wishlist > rakudo packaging teams is packaging perl6 compiler (rakudo) and > will package several Perl6 modules packages. > > It would make sense to use a 'perl6' section for all these

Bug#939809: ftp.debian.org: Please provide more informative NEW graphs

Package: ftp.debian.org Severity: wishlist Hi! The NEW queue web page points to some graphs about the queue itself over time . The problem is that this only shows whether there's been progress as long as there has been no new uploads, or the processing

Bug#939808: exim4: Very problematic default DKIM_SIGN_HEADERS

FC4871 and RFC6376 in their §5.4 section mentions that signing missing fields should be done carefully. . Add also duplicate entries for the From and Subject fields, to reject appended fields. Author: Guillem Jover Last-Update: 2019-09-08 --- src/pdkim/pdkim.h | 16

Bug#939560: xen: Various problems in debian/rules

Source: xen Source-Version: 4.11.1+92-g6c33308a8d-2 Severity: normal Hi! During the debhelper recommendation thread there was a mail from Ian pointing out to the xen debian/rules file, I took a look and noticed the following. :) The debian/rules file is setting DEB_BUILD_MAINT_OPTIONS with

Bug#939556: numpy-stl: Use after free condition

Source: numpy-stl Source-Version: 2.9.0-1 Severity: important Hi! During some code matching searches in codesearch.debian.net, and some staring, I noticed there's a use-after-free condition in the file stl/_speedups.pyx function ascii_read, as it uses uselocale(3) to immediately freelocale(3) it

Bug#935910: apt: Should be less tolerant of dpkg errors when forcing removal

Control: reassign -1 apt Hi! On Wed, 2019-08-28 at 09:30:45 +0100, Mark Hindley wrote: > On Tue, Aug 27, 2019 at 08:26:30PM +0200, Julian Andres Klode wrote: > > > I suggest that --abort-after=1 should be apt's default when forcing > > > package > > > removal. This was a false lead and the

Bug#939297: breezy: Please provide git-remote-bzr program

Source: breezy Source-Version: 3.0.1-3 Severity: wishlist Hi! I see upstream contains a git-remote-bzr program, but it's not currently being installed(?). With the removal of the git-remote-bzr binary package, and the transition away from bazaar (and the dummy bzr-git which has stopped providing

Bug#939153: nfs-utils: Fix LSB init output

Source: nfs-utils Source-Version: 1:1.3.4-2.5 Severity: wishlist Tags: patch Hi! The attached patch fixes the LSB init script to have more consistent output. Thanks, Guillem From b6e07cae38198643828a4e4008eda6edd25d9be0 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Sun, 1 Sep 2019 00:07

Bug#884999: debhelper: Please default Rules-Require-Root to no

Hi! On Fri, 2019-05-24 at 13:42:28 +0900, Hideki Yamane wrote: > > > In summary: The debhelper fundamentally cannot affect whether > > > Rules-Requires-Root: no is default or not. The debhelper compat level > > > system is the wrong interface to do this as well. > > > > > > That said, in a

Bug#935721: RM: device3dfx -- ROM; unneeded, RC buggy

Package: ftp.debian.org Severity: normal Hi! The Linux modules built from this package were needed by the glide2 libraries, which are not built anymore by the glide source package. The glide3 libraries use DRI exclusively, so there is no point in the old module. In addition the module does not

Bug#935669: assaultcube-data: Outdated version makes assaultcube uninstallable

Package: assaultcube-data Version: 1.1.0.4+repack1-2.1 Severity: serious Hi! The assaultcube package got updated to version 1.2.0.2.1-1, but the matching assaultcube-data package has not been uploaded which makes the former to be currently uninstallable in unstable. Thanks, Guillem

Bug#935530: libjsoncpp: Uses non-standard item indentation in package description

Source: libjsoncpp Source-Version: 1.7.4-3 Severity: minor Hi! This package uses «^ \* » to itemize the list in the package description, this is a non-standard indentation that is not recognized by aptitude, which would otherwise not reflow the text as if it was a normal paragraph. Please add

Bug#935529: linkchecker: Uses non-standard itemizers and indentation in package description

Source: linkchecker Source-Version: 9.4.0-2 Severity: minor Hi! This package uses «^ o » to itemize the list in the package description, this is both a non-standard itemizer and indentation that is not recognized by aptitude, which would otherwise be able to reflow the text in the items. Please

Bug#935138: closed by Chris Lamb (Bug#935138: fixed in lintian 2.19.0)

Hi! On Wed, 2019-08-21 at 17:27:17 +, Debian Bug Tracking System wrote: > Changes: > lintian (2.19.0) unstable; urgency=medium > . […] >[ Chris Lamb ] […] >* Also check for "${source:Upstream:Version}" etc. in the > version-substvar-for-external-package tag, not just >

Bug#935217: buildd.debian.org: Giveback service complains about version mismatch

Package: buildd.debian.org Hi! Just tried the new giveback service (which looks great, thanks!) for attr on sh4, and I got this error message: URL:https://buildd.debian.org/auth/giveback.cgi?pkg=attr=sid=sh4 ,--- You are authenticated as guillem. ✓ Working on package attr, suite sid and

Bug#934470: arj FTCBFS: typo in gnu/makefile.in

Hi! On Sun, 2019-08-11 at 13:08:49 +0200, Helmut Grohne wrote: > Source: arj > Version: 3.10.22-21 > Tags: patch upstream > User: debian-cr...@lists.debian.org > Usertags: ftcbfs > The last arj upload moves arj a lot closer to cross building. > Unfortunately, there is a little typo that makes it

Bug#934135: [Aptitude-devel] Bug#934135: aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer

Hi! On Thu, 2019-08-08 at 01:49:24 +0200, Axel Beckert wrote: > Guillem Jover wrote: > > I'm attaching an old patch I had around, which I thought I had sent > > out, but apparently not (perhaps only on IRC), to switch to > > libdpkg-perl's parser which is the successor of t

Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

On Wed, 2019-08-07 at 16:19:30 +0200, Axel Beckert wrote: > Guillem Jover wrote: > > Some of the features got removed, to trim down dependencies, and the > > API adapted to match the rest of the libdpkg-perl codebase, but if > > the removed output formats are needed, o

Bug#933134: lintian: depends on libparse-debianchangelog-perl that has no upstream maintainer

Hi! On Wed, 2019-07-31 at 09:56:31 -0700, Felix Lechner wrote: > On Wed, Jul 31, 2019 at 8:29 AM intrigeri wrote: > > - Your MR introduces yet another debian/changelog parser. > > > > Given the trouble we had with keeping Parse::DebianChangelog somewhat > > working and up-to-date so far, I

Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

Hi! On Sun, 2019-07-28 at 22:38:29 +0200, Axel Beckert wrote: > the Debian Perl Team maintained libparse-debianchangelog-perl for > quite some years now using debian-specific patches against your > upstream version 1.2.0 from http://www.djpig.de/software/. > > Being sick of doing upstream work

Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

Hi! On Sat, 2019-07-27 at 12:20:00 -0300, intrigeri wrote: > gregor herrmann: > > In dpt-new-upstream we're using Dpkg::Changelog::Debian from > > libdpkg-perl, which might help here as well. > Oh, this is very interesting, thanks! I had taken a look at that > module, but from the documentation

Bug#934135: aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer

any work duplication. Thanks, Guillem From a1c7206ecdae8e3b33eef406be3ac9b44190b0d8 Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Tue, 18 Oct 2016 23:55:28 +0200 Subject: [PATCH] Switch from libparse-debianchangelog-perl to libdpkg-perl The former was merged into the latter some time ago

Bug#933962: dpkg --force-confold, does not say anywhere in it's cmdline output why it's overriding --force-confold

Hi! On Mon, 2019-08-05 at 15:53:08 +0100, Dreamcat4 wrote: > Package: dpkg > Version: 1.19.6 > If I specify --force-confold option to dpkg -i while upgrading / > reinstalling. Then I get the following output: > > $ sudo DEBIAN_FRONTEND=noninteractive dpkg -D200 --force-confold -i >

Bug#933609: How hard it is to find the Date of a package

Hi! I don't think there's any bug here, TBH. And if there was this would be the wrong package to assign to. On Thu, 2019-08-01 at 09:22:29 +0800, 積丹尼 Dan Jacobson wrote: > Package: www.debian.org > Let's examine how extremely hard it is for a user to squeeze update date > of a package he is

Bug#933152: dpkg-dev: DEP3 spam with single-debian-patch

Hi! On Sat, 2019-07-27 at 03:28:23 +0200, Adam Borowski wrote: > Package: dpkg-dev > Version: 1.19.7 > Severity: normal > If a package has single-debian-patch in debian/source/options, quilt is not > supposed to be used (it is technically still used because there's no > quilt-less non-native

Bug#933335: dpkg: error: dpkg frontend lock is locked by another process

Control: reassign -1 aptitude Control: severity -1 important Control: retitle -1 aptitude: Please add support for dpkg frontend lock Hi! On Mon, 2019-07-29 at 13:47:05 +0200, Vincent Lefevre wrote: > Package: dpkg > Version: 1.19.7 > Severity: serious > I wanted to upgrade with aptitude, but it

Bug#933015: libssh FTBFS on hurd: unconditional usage of PATH_MAX

Hi! On Thu, 2019-07-25 at 20:36:31 +0200, Paul Sonnenschein wrote: > Package: src:libssh > Severity: Important > Version: 0.9.0-1 > Tags: patch > User: debian-h...@lists.debian.org > Usertags: hurd > X-Debbugs-CC: debian-h...@lists.debian.org > the package libssh fails to build from source on

Bug#933336: lxqt-config: FTBFS on hurd-i386: udev not available

Hi! On Mon, 2019-07-29 at 13:49:45 +0200, Paul Sonnenschein wrote: > Package: lxqt-config > Severity: important > Version: 0.14.1-2 > Tags: patch > User: debian-h...@lists.debian.org > Usertags: hurd > > the package lxqt-config fails to build from source on hurd-i386 because > udev is not

Bug#932841: libdpkg-perl: Dpkg::Source::Package installs a permanent SIGINT handler

Hi! On Tue, 2019-07-23 at 20:44:35 +0100, Ian Jackson wrote: > Package: libdpkg-perl > Version: 1.18.25 > Severity: normal > $ perl -we 'use Data::Dumper; print Dumper($SIG{INT})' > $VAR1 = undef; > $ perl -we 'use Data::Dumper; use Dpkg::Source::Package; print > Dumper($SIG{INT})' > $VAR1 =

Bug#932258: console-setup-freebsd: missing dependency

On Wed, 2019-07-17 at 18:06:00 +0300, Anton Zinoviev wrote: > On Wed, Jul 17, 2019 at 04:15:51PM +0200, Guillem Jover wrote: > > this seems like a problem with console-setup-freebsd being arch:all > > and depending on kFreeBSD-specific packages which will not be > >

Bug#932258: console-setup-freebsd: missing dependency

Hi! [ I'm not sure this bug closure is entirely correct? See below. ] On Wed, 2019-07-17 at 13:25:50 +0100, James Clarke wrote: > On 17 Jul 2019, at 10:55, Holger Wansing wrote: > > Héctor Orón Martínez (2019-07-17): > > > Package: console-setup-freebsd > > > Version: 1.191 > > > Severity:

Bug#932283: RM: libpmount -- ROM; inadequate API, no known users, abandoned

Package: ftp.debian.org Severity: normal Hi! I request the removal of libpmount from Debian, for which I'm also upstream, and just marked it as abandoned there [A] due to it having an inadequate API, no known users, and not being as portable as it is claimed to be. [A]

Bug#931135: German translation made me laugh during a meeting

Hi! On Wed, 2019-06-26 at 21:06:19 +0200, Stefan Potyra wrote: > Package: dpkg-dev > Version: 1.19.6 > Severity: minor > Tags: l10n > the following translation in the "FEATURE AREAS" -> "qa" might need some > improvement: > > LANG=C man dpkg-buildflags > ___snip___ >canary This setting

Bug#932152: debhelper: Make commands use pkgname.name.fragment automatically?

Source: debhelper Source-Version: 12.2 Severity: wishlist Hi! I've noticed when using the dh sequencer, one of the common reasons to override targets is to pass --name arguments to debhelper commands. It would be nice if the name arguments would be inferred from the presence of the filenames

<    5   6   7   8   9   10   11   12   13   14   >