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
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
>
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
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
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
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
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
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
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
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
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
>
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
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
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
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
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
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 =
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
> >
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:
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]
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
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
On Sun, 2019-07-14 at 15:03:28 -0700, Russ Allbery wrote:
> In that case, should we increase the strength of this by changing the
> first sentence? I'm not seeing much purpose served by developer
> discretion here, and this clarifies matters for tool developers.
Sure.
> diff --git
Hi!
On Sat, 2003-11-01 at 13:47:30 +0100, Robert Millan wrote:
> Package: debhelper
> Version: 4.1.77
> Severity: wishlist
> I'm working on the Glibc-based GNU/KNetBSD port, and have some problems with
> the way debhelper determines its arch-specific files in debian/ directory.
>
> Due to
Hi!
On Sun, 2019-07-14 at 09:31:16 -0700, Russ Allbery wrote:
> Yeah, this just seems generally wrong to me. I assume the idea was that a
> package may have mirrors of its packaging repository in multiple VCS
> systems and list all of them, but I'm dubious there's much point. My
> leaning is to
Control: reassign -1 debian-policy
Hi!
On Sat, 2019-07-13 at 10:27:24 +0200, Jörg Frings-Fürst wrote:
> Package: dpkg-dev
> Version: 1.19.7
> Severity: important
> With two Vsc-Git statements in debian/control I get:
>
> dpkg-checkbuilddeps: error: syntax error in debian/control at line 14:
>
Hi!
On Sat, 2015-10-17 at 15:31:22 +0100, Antoine Amarilli wrote:
> Package: gnupg
> Version: 1.4.19-5
> Severity: wishlist
> By default, gpg requests keys using HKP server . This allows a
> passive attacker to obtain information about the keys requested by the user,
> which may be harmful in
Hi!
On Tue, 2019-07-02 at 15:55:32 +0200, Guillem Jover wrote:
> Package: dirmngr
> Version: 2.2.16-2
> Severity: wishlist
> According to the dirmngr(8) man page, the default built-in server is
> «hkps://hkps.pool.sks-keyservers.net». Given the recent attacks, and
> the
Package: dirmngr
Version: 2.2.16-2
Severity: wishlist
Hi!
According to the dirmngr(8) man page, the default built-in server is
«hkps://hkps.pool.sks-keyservers.net». Given the recent attacks, and
the problems inherent in that network, could we just change the
default to be
Hi!
On Mon, 2019-07-01 at 11:19:59 +0200, Marketa Calabkova wrote:
> I am afraid this bug got forgotten somehow... could you please look at
> it and give some answers?
Ah, sorry, this was filed against a non-existent package, and when
reassigned, it was not CCed.
On Tue, 2019-04-02 at 12:40:57
Hi!
On Fri, 2019-06-28 at 15:50:19 +0100, Ian Jackson wrote:
> Package: wiki.debian.org
> Control: block 864925 by -1
> Control: block 931224 by -1
> The default style has two bugs, at least one of which is IMO fairly
> serious and has gone unfixed for 2 years now:
> | #864925 wiki.debian.org:
On Sun, 2019-06-23 at 21:32:19 +0200, Sven Joachim wrote:
> On 2019-06-20 18:19 +0200, Ansgar Burchardt wrote:
> > Package: apt,dselect
> > Severity: normal
> > today I learned that debootstrap as special code to create the file
> > /var/lib/dpkg/cmethopt (contents: "apt apt"); this is the
Hi!
On Wed, 2019-06-26 at 08:24:10 +0200, Harald Dunkel wrote:
> Package: dpkg
> Version: 1.19.7
> Obviously
>
> export DPKG_PAGER=""
>
> doesn't work as expected (overriding $PAGER, as promised by the man page).
Hmm, I guess I could change it to treat "" the same as "cat", even
though
On Thu, 2019-06-27 at 11:52:05 +0100, Colin Watson wrote:
> On Thu, Jun 27, 2019 at 10:57:42AM +0200, Martin Bagge / brother wrote:
> > On 2019-06-26 21:06, Stefan Potyra wrote:
> > > the following translation in the "FEATURE AREAS" -> "qa" might need
> > > some improvement:
> > >
> > > LANG=C
Hi!
On Sun, 2019-06-16 at 14:40:53 +0800, Wenbin Lv wrote:
> Package: release-notes
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Recent transition from .dbk to .po for the ca language leaves some
> untracked .dbk files in
Hi!
On Fri, 2019-06-14 at 12:17:27 +0200, Rhonda D'Vine wrote:
> severity 930072 important
> thanks
> On 6/12/19 10:35 PM, Peter Pentchev wrote:
> > On Thu, Jun 06, 2019 at 04:04:39PM +0200, Guillem Jover wrote:
> >> Package: dctrl-tools
> >> Version: 2.24-3
>
Package: chromium
Version: 75.0.3770.80-1
Severity: serious
Hi!
I was using 73.0.3683.75-1, held due to the problems with later
version. Upgraded to the latest version in unstable, and now I'm
getting insta-segfaults on startup. The output when running normally
(first without --debug) is not
Control: reassign -1 fuse-overlayfs
[ Please check the bug report for the original problem. ]
Hi!
On Tue, 2019-04-09 at 10:02:25 +0200, Santiago Vila wrote:
> Hmm, I said:
> > Is dpkg in buster calling tar with any options that makes this
> > behaviour to happen more easily? Is tar in buster
Package: dctrl-tools
Version: 2.24-3
Severity: serious
Hi!
The join-dctrl command segfaults with the attached files.
,---
$ join-dctrl Packages-A Packages-B
Segmentation fault (core dumped)
`---
Thanks,
Guillem
Package: aaa
Version: 1.0
Package: bbb
Version: 1.1
Package: zzz
Version:
Source: dctrl-tools
Source-Version: 2.24-3
Severity: important
Tags: patch
Hi!
The -a option in join-dctrl does not work when passing it a 2
argument. The attached patch should fix it.
Thanks,
Guillem
diff --git i/join-dctrl/join-dctrl.c w/join-dctrl/join-dctrl.c
index f3856ac..056a5aa 100644
Hi!
On Fri, 2019-05-17 at 21:12:28 +0200, Andreas Beckmann wrote:
> On 2019-05-14 02:35, Guillem Jover wrote:
> > setup some chroot somewhere to do that.
> >
> > I'm attaching the patch. Otherwise already built (and signed) binary
> > packages can be temporarily
Source: mozjs60
Source-Version: 60.2.3-3
Severity: important
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Hi!
The cross-compilation support in this package seems to be broken. The
debian/rules file contains some confused logic:
* DEB_BUILD_ARCH is not defined, so it will not build
Control: tags -1 moreinfo
Hi!
On Sun, 2019-05-26 at 16:37:01 -0400, Gerard Weatherby wrote:
> Package: dpkg-dev
> Version: 1.18.4ubuntu1.5
> Severity: minor
> Tags: newcomer
> I cloned https://git.dpkg.org/git/dpkg/dpkg.git. When I went to build it I
> found I had to install autopoint along
Control: severity -1 wishlist
Hi!
On Thu, 2019-05-23 at 18:20:05 +0530, Pirate Praveen wrote:
> package: dpkg
> severity: important
> version: 1.19.6
> For example node-gulp package depend on "object.defaults" node module.
> But when running dpkg-source -b . with
Package: lintian
Version: 2.14.0
Severity: wishlist
Hi!
The mk-origtargz program from devscripts was producing bogus upstream
tarball .asc files. It would be nice if this could be warned, so that
people know this is the case and so that they have sufficient data to
decide whether to fix it right
Package: lintian
Version: 2.14.0
Severity: wishlist
Hi!
It would be nice if the various checks that involve R³ and currently
reference the dpkg-dev rootless-builds.txt spec, would also get refs
to policy §4.9.2 and §5.6.31.
Thanks,
Guillem
On Wed, 2019-05-15 at 14:42:53 +0200, Santiago Vila wrote:
> On Wed, May 15, 2019 at 02:21:49PM +0200, Guillem Jover wrote:
> > > To be precise, if I apply the patch below to hello-traditional_2.10-5
> > > and do "dpkg-buildpackage -uc -us -b" in a sid chroot, I ge
Hi!
On Wed, 2019-05-15 at 13:40:19 +0200, Santiago Vila wrote:
> Package: dpkg-dev
> Version: 1.19.6
> I don't fully understand how Rules-Requires-Root is supposed to work
> when not using dh or debhelper.
>
> To be precise, if I apply the patch below to hello-traditional_2.10-5
> and do
On Mon, 2019-05-13 at 17:24:55 +0200, Bastian Blank wrote:
> On Mon, May 13, 2019 at 11:22:35AM +0100, Ian Jackson wrote:
> > In #923091, Guillem (with dpkg maintainer hat on) asks for a
> > base-installer option to allow installing buster without merged-usr.
>
> No, he did not mention dpkg.
Hi!
On Tue, 2019-05-14 at 11:29:04 +0200, Holger Levsen wrote:
> Package: debian-security-support
> Version: 2019.02.02
> Severity: minor
> check-support-status.hook contains code (copied from postinst) to create
> the d-s-s user, which (I believe) is useless as the user is created in
>
Hi!
On Fri, 2019-05-10 at 21:45:09 +0200, Andreas Beckmann wrote:
> On 2019-05-09 06:00, Guillem Jover wrote:
> > awaiting trigger does not help matters, I'm not entirely sure this
> > might not be still a problem with dpkg itself. :/
>
> I can also reproduce the prob
Hi!
On Tue, 2019-05-07 at 14:57:53 +0200, Guillem Jover wrote:
> Thanks! I tried yesterday and today to get a deterministic reproducer
> with the version from unstable, but I'm not sure what's the trigger,
> perhaps the torrent peers or the chunk arrival order or something. In
>
Hi!
On Sat, 2019-05-04 at 15:13:58 +0200, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.19.6
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 + education-desktop-gnome education-desktop-mate
> education-desktop-xfce education-main-server
Hi!
On Sat, 2019-05-04 at 13:02:13 +0100, Alessandro Ghedini wrote:
> On Sat, Apr 20, 2019 at 01:39:36PM +0200, Guillem Jover wrote:
> > Source: curl
> > Source-Version: 7.64.0-2
> > Severity: serious
> > Control: affects -1 rtorrent
> > I've started noticing rto
Hi!
On Tue, 2016-05-24 at 05:37:26 -0500, Michael Kerrisk (man-pages) wrote:
> Note that around May 2015, by mutual agreement between the man-pages
> and libattr projects (which hitherto had both carried versions of the
> *xattr(2) pages), man-pages became the canonical home for these pages,
>
On Tue, 2019-04-23 at 19:35:50 -0500, John Goerzen wrote:
> On Tue, Apr 23 2019, Michael Biebl wrote:
> > Am 23.04.19 um 11:12 schrieb Michael Biebl:
> >> But splitting each tiny module into a separate package adds significant
> >> overhead packaging-wise.
> >
> > (not to forget NEW round trips)
>
On Wed, 2019-04-24 at 04:39:50 -0400, Anthony DeRobertis wrote:
> On 4/23/19 5:12 AM, Michael Biebl wrote:
> > My main concern is to keep the rsyslog core package reasonably small
> > (dependency wise).
I think either a new package for this plugin or a conglomerate package
with extra stuff sound
Control: severity -1 minor
Hi!
On Wed, 2019-04-17 at 12:03:34 +0800, Drew Parsons wrote:
> Package: dpkg-dev
> Version: 1.19.6
> Severity: normal
> dpkg-buildpackage -F is supposed to be equivalent to
> dpkg-buildpackage --build=source,binary
>
> The dpkg-buildpackage manpage tells us that if
Control: severity -1 minor
Control: retitle -1 dpkg: --clear-selections marks unknown packages for
deinstall
Hi!
On Tue, 2019-04-23 at 01:55:17 +0800, 積丹尼 Dan Jacobson wrote:
> Package: dpkg
> Version: 1.19.6
> Severity: wishlist
> File: /usr/share/man/man1/dpkg.1.gz
> Man page says
>
>
Source: curl
Source-Version: 7.64.0-2
Severity: serious
Control: affects -1 rtorrent
Hi!
I've started noticing rtorrent busy-looping at some points after
finishing a torrent. stracing and gdb'ing the process it was doing
that in its main loop, spamming on gettimeofday() and epoll_wait().
Package: mmdebstrap
Version: 0.4.1-2
Severity: important
Hi!
The fix in 0.4.0-1 to cleanup aufxiles does not seem entirely
effective, as there's subsequent «apt-get update» which will
regenerate the directory.
I was a bit confused about this when we found the stretch-based VMs
we are produced
kly shows this is still the case. The attached patch
makes this package build again for me, and removes a warning from
using an internal header.
Thanks,
Guillem
Author: Guillem Jover
Description: Update code against latest mariadb libraries
- Do not include internal header which emits warnings now.
- D
Control: reassign -1 pommed
Hi!
On Mon, 2009-04-13 at 20:40:13 +0200, Martin Mares wrote:
> > This bug is not present in version 3.0.3 (Lenny), it's in 3.1.2 as
> > explained above by Julien.
>
> This is not a bug in libpci, but rather a deficiency in its documentation
> leading to improper
Hi!
On Tue, 2019-03-05 at 15:43:05 +0100, Vincent Lefevre wrote:
> I've done a test with "iozone -a -e", and with this -e option
> (to include fsync), the operations are much slower than on the
> other machine.
>
> zira:~> iozone -a -e
> [...]
>
Control: tag -1 moreinfo
Hi!
On Thu, 2019-04-04 at 10:27:29 +, Santiago Vila wrote:
> Package: src:oxygen-icons5,dpkg-dev,tar
> Tags: ftbfs
> I tried to build "oxygen-icons5" in buster but it failed:
> This happens randomly. Sometimes it fails, sometimes it does not. It
> happens in other
Control: retitle -1 dpkg: --pending should enqueue packages in hold state
Control: severity -1 normal
Hi!
On Fri, 2019-04-05 at 19:29:28 +0200, Vincent Lefevre wrote:
> Package: dpkg
> Version: 1.19.6
> Severity: wishlist
> When a package is on hold, its triggers are not processed
>
Hi!
On Wed, 2018-04-25 at 14:05:12 +0200, Laura Arjona Reina wrote:
> Guillem, I didn't commit your patch for 2 reasons:
>
> * The debian/changelog file in https://salsa.debian.org/l10n-team/dl10n/ has
> evolved since you sent your patch (as well as the dl10n codebase) and I'm not
> sure how to
maintainer upload.
+ * Do not unconditionally use SSE2 instructions on i386, as some processors
+that conform to the architecture ISA baseline, do not support that
+instruction set.
+
+ -- Guillem Jover Sat, 23 Mar 2019 19:24:32 +0100
+
pcre2 (10.32-4) unstable; urgency=medium
* Take
Hi!
On Fri, 2019-03-15 at 20:27:57 +0530, Gaurav Mishra wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Gaurav Mishra
> Package name : fossology
> Version : 3.4.0
> Upstream Author : Michael Jaeger
> URL : https://www.fossology.org/
> License : GPL-2.0-only, LGPL-2.1-only
>
Hi!
On Sat, 2018-11-24 at 10:24:09 +0100, Johannes 'josch' Schauer wrote:
> Package: dpkg
> Version: 1.19.2
> Severity: wishlist
> lintian recently tagged mmdebstrap with uses-dpkg-database-directly
> because mmdebstrap contains the string "/var/lib/dpkg" in several
> places. Instead of
Hi!
On Fri, 2019-03-15 at 00:37:33 +0100, Santiago Vila wrote:
> Maybe, but this is neither a new miscellaneous file nor a new
> bootstrapping action. This is yet another bootstrapping tool
> forgetting the lessons learned from the other bootstrapping tools.
My impression though is that the
om the packages themselves into
external bootstrapping tools is bogus IMO, and something we should
try to fix.
> Maybe the rule should be to retry configuration of each unconfigured
> package until either they all succeed, or forward progress stops being
> made? Pythonesque pseudocode:
I
Source: pciutils
Source-Version: 1:3.5.2-1
Severity: important
Hi!
This package needs some attention, and looks like a candidate for
salvaging. Anibal is already being tracked by the MIA team, and it's
just a matter of days until he gets an orphaning pass.
I'd like to get updated packages
Hi!
On Sun, 2019-03-03 at 02:38:10 +0100, Vincent Lefevre wrote:
> On 2019-03-03 00:15:13 +0100, Guillem Jover wrote:
> > Did this start happening due to the new kernel version?
>
> In March 2018, this was already slow, but much less:
>
> [...]
> 2018-03-08 00:55:55
Hi!
On Thu, 2019-02-28 at 01:06:28 +0100, Vincent Lefevre wrote:
> Package: texlive-fonts-extra
> Version: 2018.20190227-1
> Severity: serious
> Installation of texlive-fonts-extra 2018.20190227-1 hangs.
> 17m01s ago dpkg was started, at 2019-02-28T00:48:45+01:00.
> 1.5% has been its average
Control: tag -1 moreinfo
Hi!
On Tue, 2008-07-01 at 09:14:40 +0300, Guillem Jover wrote:
> On Thu, 2004-02-19 at 18:22:20 +0100, Michele Mencacci wrote:
> > Package: dpkg
> > Version: 1.10.18
> > Severity: minor
> > Upgrading from 4.2.1-15, ( working system) to
Control: retitle -1 dpkg: Provide an interface for bootstrapping an installation
Hi!
On Sun, 2003-11-23 at 16:44:37 +0100, Koblinger Egmont wrote:
> Package: dpkg
> Version: 1.10.18
> Currently if more unconfigured packages are being configured, their
> ordered is determined by the Depends
Hi!
On Fri, 2005-12-16 at 11:42:02 +0100, A Mennucc wrote:
> Package: dpkg
> Version: 1.13.11.0.1
> Severity: normal
> did you ever ran out of disk space while installing/upgrading packages?
> When the dreaded message "dpkg: . No space left on device" appears,
> you readily know it is time
Control: reassign -1 ftp.debian.org
Control: retitle -1 dak: Please ignore packages with empty arch keys from
Package-List
Hi!
[ Leaving enough context for the reassign. ]
On Mon, 2012-09-10 at 17:46:26 +0200, Andreas Beckmann wrote:
> Package: dpkg-dev
> Version: 1.16.8
> Severity: normal
>
On Thu, 2019-02-28 at 17:22:53 +0100, Matthias Klose wrote:
> Package: src:acl
> Version: 2.2.52-5
> Severity: important
> Tags: sid buster
>
> acl fails it's autopkg tests, missing some of the build dependencies in the
> tests. However even with that, some root test fail, seen at
>
Control: tag -1 moreinfo
Hi!
On Mon, 2019-02-25 at 20:21:01 +0100, definetti wrote:
> Package: libaio1
> Version: 0.3.111-1
> Severity: important
> after updating libaio1 to version 0.3.112-1 the system does not detect the
> wireless network card after reboot. Dmesg shows the following error:
>
Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: ddpo
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi!
The reproducible build state is currently only provided for «testing»,
because «sid» contains additional checks that are deemed would annoy
Control: retitle -1 dpkg: conffile prompts should use debconf
Hi!
I was asked by Julian Andres Klode on IRC about the status of this,
so let's update the bug too.
On Sat, 2007-02-10 at 15:16:30 -, peter green wrote:
> in situations where a user cannot interact directly with dpkg
>
Package: base-installer
Version: 1.187
Severity: wishlist
Hi!
The current base-installer uses the default debootstrap settings
which end up unconditionally installing systems with the
merged-usr-via-symlinks deployment method which is broken by design,
please see:
Package: reportbug
Version: 7.5.2
Severity: wishlist
Hi!
The merged-/usr deployment method of using directory symlinks, instead
of properly moving the files or symlinking the contents of these
directories is broken by design.
Please see
Hi!
On Mon, 2019-02-18 at 19:37:38 +, Dmitry Bogatov wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Dmitry Bogatov
>
> * Package name : build-alternative
> Version : 0.0.1
> Upstream Author : Dmitry Bogatov
> * Url :
Hi!
On Tue, 2019-02-12 at 17:33:03 +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> > # Breaks autopkgtests and is therefore a migration blocker
> > severity 921031 grave
> Bug #921031 [libdpkg-perl] Dpkg::Source::Package missing use of ::Format
>
Control: retitle -1 Please warn on packages using getconf(1), except to get
PATH, _NPROCESSORS_{CONF,ONLN}
On Mon, 2017-10-30 at 09:05:46 +, Chris Lamb wrote:
> retitle 879935 Please warn on packages using getconf(1) to get PATH,
> _NPROCESSORS_{CONF,ONLN} etc.
> thanks
> > Well this only
On Mon, 2019-02-18 at 14:16:56 +0100, Chris Lamb wrote:
> > The problem with emitting this tag unconditionally, even within the
> > Debian-vendor realm, is that people create local packages for their
> > own, or for $work, etc.
>
> Hmm. Emitting such a tag here still seems right to me, or at
Hi!
On Mon, 2019-02-18 at 14:51:42 +0100, Chris Lamb wrote:
> > There is already such a tag, orig-tarball-missing-upstream-signature.
> > That's a .changes checks, not a .dsc one, so it would be emitted only
> > for -1.
Right, had seen it but from a very quick skim got the impression it
was for
On Sun, 2019-02-17 at 23:45:37 +0100, Chris Lamb wrote:
> Do others have thoughts before I apply this patch?
As I mentioned initially, I don't think the patch is ready as is, it
even has syntax errors (at least one ‘?‘ :). It would probably need
a new pass over the newly created tags, a review of
to it.
Attached patch should fix this.
Thanks,
Guillem
From 5aa9e83baf01384ddd5a5d10ef3ab29d67360dc9 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Tue, 19 Feb 2019 15:17:52 +0100
Subject: [PATCH] debian: Fix init script return code on restart action
The errcode is only assigned conditionally when
Package: lintian
Version: 2.7.0
Severity: wishlist
Hi!
I just noticed that I've sometimes been failing to include the orig
tarball signature file for some of the uploads after the first new
upstream release. Let me clarify with an example:
- Fetch upstream xfstt 1.9.3 orig.tar.xz and
Hi!
On Sun, 2019-02-17 at 22:41:19 +0100, Chris Lamb wrote:
> > So, I'd appreciate very much to see this tag emitted exclusively when
> > running lintian on lintian.d.o and Debian's ftp-master […] but not when
> > running locally
> Whilst I have not seen Ubuntu folks complain about this tag
On Sun, 2019-02-17 at 23:07:50 +0100, Chris Lamb wrote:
> > I'd request that no more such tag names be added, and ideally the
> > current ones be renamed, although the longer they stay the more
> > overrides they might accumulate. :/
>
> That's my only concern at this point. I mean, there's
should-be-oldlibs-extra
Thanks,
Guillem
From b094a6099aaeba702d3d88cca6da88494ce48297 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Sun, 17 Feb 2019 20:43:53 +0100
Subject: [PATCH] RFC: Mass tag rename to try to unify naming conventions
---
data/override/renamed-tag
Package: lintian
Version: 2.7.0
Severity: minor
Hi!
Here's a couple of patches I had sitting on my local lintian tree.
Thanks,
Guillem
From af1af30e9973e7da6f59fec405611392d1bf2aaf Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Sun, 17 Feb 2019 20:28:53 +0100
Subject: [PATCH 1/2] c/deb
Package: lintian
Version: 2.7.0
Severity: wishlist
Hi!
As the maintainer of dpkg, I do not agree at all (well I'd go as far as
to consider them to be just bogus :) with the rationale and conclusions
that were arrived to get the package-uses-vendor-specific-patch-series
tag implemented.
But the
Package: lintian
Version: 2.7.0
Severity: normal
Hi!
The uses-dpkg-database-directly tag is emitted for both dpkg and
base-files, even though the code tried to avoid doing that. :)
Thanks,
Guillem
Package: libtool
Version: 2.4.6-9
Severity: normal
Hi!
The libtool program emits warnings in bold red which is a very
unexpected and confusing color for a warning (in contrast to an error),
and it always triggers alarms when I see it scroll by, for example for:
,---
libtool: warning:
1001 - 1100 of 4852 matches
Mail list logo
