Bug#746973: dpkg-gensymbols(1) is misleading to omit important part of symbols file maintainance

2014-05-04 Thread Bernhard R. Link
Sep 17 00:00:00 2001 From: "Bernhard R. Link" Date: Sun, 4 May 2014 15:31:54 +0200 Subject: [PATCH] dpkg-gensymbols(1): Fix seriously misleading part about applying diffs to symbols files --- man/dpkg-gensymbols.1 | 16 ++-- 1 file changed, 14 insertions(+), 2 deletions(-)

Bug#737634: dpkg-dev: please reject native/non-native version when building native/non-native source packages

2014-02-05 Thread Bernhard R. Link
anges. This answers the question why you want to use a 3.0 (native) package. But the real question here is: Why do you want to use a version with "-" for such a package? Bernhard R. Link -- F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC -- To UNSUBSCRIBE, email to debian-d

Bug#700177: dpkg-dev: please reject native/non-native version when building native/non-native source packages

2013-04-18 Thread Bernhard R. Link
> for > a package built from python3.3 and python3.3-stdlib-extensions would be > unexpected and confusing. You seem to be speaking about source package names. I fail to see how that is related to dashes in versions. Bernhard R. Link -- To UNSUBSCRIBE, email to debian-dpkg-bug

Bug#688550: patch for 688550

2013-04-16 Thread Bernhard R. Link
If found that one laying around here. No idea if I already sent it or why not: >From ba00cfbdc68124d95836b86414f4ebca782875d1 Mon Sep 17 00:00:00 2001 From: "Bernhard R. Link" Date: Wed, 19 Sep 2012 15:49:16 +0200 Subject: [PATCH] silence warnings about versions in available file

Bug#700177: dpkg-dev: please reject native/non-native version when building native/non-native source packages

2013-02-10 Thread Bernhard R. Link
matic. To ease adoption, patch split into two attached. Bernhard R. Link >From b10e8210cdebe3fd897a13e6d8194ca4b454cb59 Mon Sep 17 00:00:00 2001 From: "Bernhard R. Link" Date: Sat, 9 Feb 2013 14:59:00 +0100 Subject: [PATCH 1/2] Dpkg::Version, Dpkg::Source::Package::V3::quilt: c

Bug#700177: dpkg-dev: please reject native/non-native version when building native/non-native source packages

2013-02-10 Thread Bernhard R. Link
* Raphael Hertzog [130209 18:14]: > On Sat, 09 Feb 2013, Bernhard R. Link wrote: > > Please ensure that the package version matches its nativity state > > in 3.0 (quilt/native) packages. Having dpkg-source allow to create > > native packages with non-native versions and non

Bug#700177: dpkg-dev: please reject native/non-native version when building native/non-native source packages

2013-02-09 Thread Bernhard R. Link
confusing, so better reject them directly. (Attached patch does this for 3.0 (quilt) and 3.0 (native) packages, where this change should be safe to be done and does not touch any legacy source package formats). From: "Bernhard R. Link" Date: Sat, 9 Feb 2013 14:59:00 +0100 Subject: [P

Bug#681371: outputs parts of the error message to stdout

2012-07-12 Thread Bernhard R. Link
. The following patch (against current git master) fixes that. Bernhard R. Link From: "Bernhard R. Link" Date: Thu, 12 Jul 2012 18:24:47 +0200 Subject: [PATCH] scripts: do not output usage part of error message to stdout Add an optional argument to usage() functions to determi

Bug#664058: dpkg-dev: please add action to dpkg-buildflags to get an overview of the settings

2012-06-05 Thread Bernhard R. Link
et the first two patches with the infrastructure groundwork already applied? Is there any chance to still get this into wheezy? Bernhard R. Link -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#664058: dpkg-dev: please add action to dpkg-buildflags to get an overview of the settings

2012-03-19 Thread Bernhard R. Link
e) I undestand that since 1.16.2 was released in between, I need to change the version? Attached are new versions of this patches with the version changed. Bernhard R. Link >From 267a6cff648a9c2e7fab96e9126ceda0d4a631d6 Mon Sep 17 00:00:00 2001 From: "Bernhard R. Link" Date: F

Bug#664058: dpkg-dev: please add action to dpkg-buildflags to get an overview of the settings

2012-03-16 Thread Bernhard R. Link
g to describe flags modified that way. > > Do you really see some value to this? You already have the *_MAINT_* variables > in the output. > > I don't believe that this is required. It's not required but it might help people a lot to understand it. Maintaine

Bug#664058: dpkg-dev: please add action to dpkg-buildflags to get an overview of the settings

2012-03-16 Thread Bernhard R. Link
f the maintainer and thus of the > vendor. And since it happens at the end, it would hide any > user/system-wide customization... and I don't want this. Added a patch on top of it to show more information here. I've split the first one into preparations to the in

Bug#664058: dpkg-dev: please add action to dpkg-buildflags to get an overview of the settings

2012-03-15 Thread Bernhard R. Link
ng at some build log instead of requesting each piece of information manually). Attached is a patch relative to current dpkg git master to output environment variables, vendor, feature flags and compiler flags in a nice way as new action '--status'. Be

Bug#619131: New field Package-List in .dsc

2011-03-24 Thread Bernhard R. Link
ds appearing depending on > whether a source is uploaded or not"). I'd rather see this as "fields only there if the upload has something to say in this regard". Bernhard R. Link [1] Which is something I'm very happy if it changes[2]. Though having it as "

Bug#619131: New field Package-List in .dsc

2011-03-24 Thread Bernhard R. Link
ey have not > yet seen). If it really is in the .dsc files then it would be nice if it also could include the Architecture: of those packages. That would make it easier for things like reprepro to decide if there might be some binary package missing. (Or for other forms of poor-man's statel

Bug#493743: dpkg-dev: dpkg-buildpackage's manpage not updates for new -si

2008-08-04 Thread Bernhard R. Link
Package: dpkg Version: 1.14.20 While dpkg-genchanges lists the new -si behaviour already, dpkg-buildpackage still documents the old. Hochachtungsvoll, Bernhard R. Link -- "Never contain programs so few bugs, as when no debugging tools are available!" Niklaus Wirth

Bug#454036: dpkg-dev: dpkg-shlibdeps misses symbols and thus outputs false warnings

2008-01-03 Thread Bernhard R. Link
Sorry for my late reply. Somehow the mail did not reach me. (perhaps some spam filtering gone wild...) * Cyril Brulebois <[EMAIL PROTECTED]> [071226 05:03]: > "Bernhard R. Link" <[EMAIL PROTECTED]> (02/12/2007): > The point here is "-r". Both symbols are

Bug#454036: dpkg-dev: dpkg-shlibdeps misses symbols and thus outputs false warnings

2007-12-02 Thread Bernhard R. Link
DF *UND*0034 GLIBC_2.4 sprintf | 00028388 DF *UND*0088 GLIBC_2.0 waitpid I'm missing a i386 unstable currently, but looking there at the binary in etch, I think this will not be sparc specific at all. Hochachtungsvoll, Bernhard R. Link -- "N

Bug#427210: dpkg-gencontrol: confusing error message when using inofficial architecture

2007-06-02 Thread Bernhard R. Link
ts do not depend on the architecture it is run on). Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]