Processed: Re: Bug#854512: ftpcopy: FTBFS: dpkg-shlibdeps: error: cannot read «BUILDDIR»/debian/ftpcopy/usr/bin/ftpcp

2017-02-07 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #854512 [src:ftpcopy] ftpcopy: FTBFS: dpkg-shlibdeps: error: cannot read «BUILDDIR»/debian/ftpcopy/usr/bin/ftpcp Bug 854512 cloned as bug 854536 > reassign -2 libdpkg-perl Bug #854536 [src:ftpcopy] ftpcopy: FTBFS: dpkg-shlibdeps: error: cannot read

Bug#845436: dpkg-dev: dpkg-buildpackage leaves spurious debian/files in source tree

2017-02-07 Thread Guillem Jover
Hi! On Tue, 2017-02-07 at 16:08:44 +0100, Sven Joachim wrote: > On 2017-02-07 14:41 +0100, Guillem Jover wrote: > > Well, yes and no. This was brought up on IRC by Ansgar when this new > > behavior showed up. The problem here is that you are building a source > > package by making a source-only

Bug#852539: dpkg: run maintainer scripts with SELinux user system_u

2017-02-07 Thread Guillem Jover
Hi! On Wed, 2017-01-25 at 12:02:47 +0100, cgzones wrote: > Package: dpkg > Version: 1.18.18 > User: selinux-de...@lists.alioth.debian.org > Usertags: selinux > Currently, dpkg runs its maintainer tasks in the SELinux type > dpkg_script_t without changing the SELinux user or role. > So when

Bug#845436: dpkg-dev: dpkg-buildpackage leaves spurious debian/files in source tree

2017-02-07 Thread Sven Joachim
On 2017-02-07 14:41 +0100, Guillem Jover wrote: > On Wed, 2016-11-23 at 12:23:20 +0100, Thorsten Glaser wrote: >> Package: dpkg-dev >> Version: 1.18.15 >> Severity: minor > >> Run: dpkg-buildpackage -S -d -nc >> >> Watch this: >> >> tglase@tglase-nb:~/squirrel-sql $ svn st >> ?

Bug#854478: dpkg: triggers cycle while upgrading gnome-menus and ufw

2017-02-07 Thread Raphael Geissert
Package: dpkg Version: 1.18.18 x-debbugs-cc: jo...@debian.org, a...@debian.org [CC'ing Andreas as it might be related to #810724] Hi, As per our IRC discussion, here's the bug report for the following cycle: dpkg: cycle found while processing triggers: chain of packages whose triggers are or

Bug#814244: marked as done (dpkg: provide a flag to determine the dpkg 'status')

2017-02-07 Thread Debian Bug Tracking System
Your message dated Tue, 7 Feb 2017 14:47:18 +0100 with message-id <20170207134718.lqsyxrbahf3rc...@gaara.hadrons.org> and subject line Re: Bug#814244: dpkg: provide a flag to determine the dpkg 'status' has caused the Debian Bug report #814244, regarding dpkg: provide a flag to determine the dpkg

Bug#846211: dpkg-dev: dpkg-shlibdeps execs objdump on wrong lib architecture

2017-02-07 Thread Guillem Jover
Hi! On Wed, 2016-11-30 at 08:25:12 +0100, Jean-Francois Dockes wrote: > Guillem Jover writes: > > Control: tags -1 moreinfo > > Control: severity -1 normal > > On Tue, 2016-11-29 at 03:19:31 -0700, Jean-Francois Dockes wrote: > > > Package: dpkg-dev > > > Version: 1.17.27 > > > Severity:

Bug#845436: dpkg-dev: dpkg-buildpackage leaves spurious debian/files in source tree

2017-02-07 Thread Guillem Jover
Hi! On Wed, 2016-11-23 at 12:23:20 +0100, Thorsten Glaser wrote: > Package: dpkg-dev > Version: 1.18.15 > Severity: minor > Run: dpkg-buildpackage -S -d -nc > > Watch this: > > tglase@tglase-nb:~/squirrel-sql $ svn st > ? debian/files > tglase@tglase-nb:~/squirrel-sql $ cat debian/files

Bug#847926: Reverted in dpkg 1.18.21

2017-02-07 Thread Guillem Jover
Control: reopen -1 Hi! This got reverted, let's reopen the bug so that we can discuss how to go forward. Thanks, Guillem

Bug#852821: marked as done (Dropping Built-For-Profiles is risky)

2017-02-07 Thread Debian Bug Tracking System
Your message dated Tue, 7 Feb 2017 14:22:55 +0100 with message-id <20170207132255.yigyhb6zgsz4t...@gaara.hadrons.org> and subject line Re: Bug#852821: Dropping Built-For-Profiles is risky has caused the Debian Bug report #852821, regarding Dropping Built-For-Profiles is risky to be marked as done.

Bug#854438: dpkg: please allow Architecture:all packages to satisfy :native build dependencies

2017-02-07 Thread Johannes Schauer
Source: dpkg Severity: wishlist Hi, I want to make the case that it makes sense to let Architecture:all packages satisfy :native build dependencies. We talked about this on IRC but having a bug lets us not forget about all the arguments for either side. Here are some reasons: 1. It is pointed