Bug#826334: dget: removes existing dir by default without asking

Control: notfound -1 1.17.27 Control: tags -1 - unreproducible moreinfo On 2016-06-05 00:49 +0200, Guillem Jover wrote: > Control: severity -1 important > Control: tags -1 unreproducible moreinfo > > Hi! > > On Sat, 2016-06-04 at 17:43:41 +0100, Adam D. Barratt wrote: >> Control: reassign -1

Processed: Re: Bug#826334: dget: removes existing dir by default without asking

Processing control commands: > notfound -1 1.17.27 Bug #826334 [dpkg-dev] dpkg-source -x overwrites existing directories No longer marked as found in versions dpkg/1.17.27. > tags -1 - unreproducible moreinfo Bug #826334 [dpkg-dev] dpkg-source -x overwrites existing directories Removed tag(s)

Bug#826404: dpkg-parsechangelog: allow selection of only parts of the version field

Package: dpkg-dev Severity: wishlist File: /usr/bin/dpkg-parsechangelog There are lots of packages that manually split the version up into epoch, upstream and or Debian version number parts: https://codesearch.debian.net/search?q=path%3Adebian%2Frules+dpkg-parsechangelog.*Version.* It would be

Bug#677865: Alternative solution: flock is NFS-safe now

Rather than depending on or recommending libfile-fcntllock-perl, I think dpkg-dev can now just unconditionally use flock. According to "man 2 flock": > In Linux kernels up to 2.6.11, flock() does not lock files over NFS (i.e., the > scope of locks was limited to the local system). Instead, one

Processed: [PATCH] Always use flock for file locking; drop Recommends on libfile-fcntllock-perl

Processing control commands: > tags -1 + patch Bug #677865 [libdpkg-perl] dpkg-gencontrol warns about 'File::FcntlLock not available' Bug #679777 [libdpkg-perl] libdpkg-perl: Please warn only once about File::FcntLock being missing Added tag(s) patch. Added tag(s) patch. -- 677865:

Bug#677865: [PATCH] Always use flock for file locking; drop Recommends on libfile-fcntllock-perl

Control: tags -1 + patch The attached patch implements the change I suggested, dropping fcntl locking in favor of flock, and documenting that change in the changelog along with the rationale. - Josh Triplett >From 0c6eddc8200e7bea482ad65c5870f7977847d26a Mon Sep 17 00:00:00 2001 From: Josh

Bug#826334: dget: removes existing dir by default without asking

Control: severity -1 wishlist On Sun, 2016-06-05 at 12:58:50 +0200, Sven Joachim wrote: > Control: notfound -1 1.17.27 > Control: tags -1 - unreproducible moreinfo > On 2016-06-05 00:49 +0200, Guillem Jover wrote: > > Control: severity -1 important > > Control: tags -1 unreproducible moreinfo >

Processed: Re: Bug#826334: dget: removes existing dir by default without asking

Processing control commands: > severity -1 wishlist Bug #826334 [dpkg-dev] dpkg-source -x overwrites existing directories Severity set to 'wishlist' from 'important' -- 826334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826334 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#826161: dpkg-buildpackage -g should create a changes file for 'all' architectures

Hi! On Thu, 2016-06-02 at 15:47:03 -0400, Greg Manning wrote: > Package: dpkg-dev > Version: 1.17.26 > Severity: normal > > Dear Maintainer, > > When building an architecture independent package: > > "dpkg-buildpackage -A" generates ..._all.changes (correct) > > but > > "dpkg-buildpackage

Bug#825918: Bug#813546: Actually 1954 error message groups

> "GJ" == Guillem Jover writes: GJ> I guess you have tried to install this package many many times? Also GJ> you are having this problem when installing a package not even from GJ> unstable but from experimental! This needs fixing in the affected GJ> package. Maybe on a

Bug#773425: marked as done (please increase default logrotate duration for /var/log/dpkg.log)

Your message dated Mon, 6 Jun 2016 03:32:18 +0200 with message-id <20160606013218.ga27...@gaara.hadrons.org> and subject line Re: Bug#773425: please increase default logrotate duration for /var/log/dpkg.log has caused the Debian Bug report #773425, regarding please increase default logrotate

Bug#825918: Bug#813546: Actually 1954 error message groups

Control: severity -1 minor Control: forcemerge -1 813546 On Fri, 2016-06-03 at 21:17:11 +0800, 積丹尼 Dan Jacobson wrote: > reopen 825918 > There is actually 1954 error groups on my machine. I don't know really what that means, though. > A normal user would and should kill the seemingly runaway

Processed: Re: Bug#813546: Actually 1954 error message groups

Processing control commands: > severity -1 minor Bug #825918 [dpkg] dpkg enters infinite loop upon installing some packages Bug #825897 [dpkg] dpkg-maintscript-helper dir_to_symlink: infinite dpkg-query loop Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' > forcemerge

Bug#825915: marked as done ([dpkg] --print-avail broken)

Your message dated Mon, 6 Jun 2016 02:58:03 +0200 with message-id <20160606005803.ge11...@gaara.hadrons.org> and subject line Re: Bug#825915: [dpkg] --print-avail broken has caused the Debian Bug report #825915, regarding [dpkg] --print-avail broken to be marked as done. This means that you claim