Bug#537800: marked as pending

Author: Raphael Hertzog Date: Tue Jul 21 10:14:00 2009 +0200 Dpkg::Changelog: fix heuristic to identify correct start entry The heuristic to identify the version number that is most approaching was not working properly for the case where the version number was smaller than the

Bug#537800: dpkg-buildpackage: -v support including all changelog entries

On Mon, 20 Jul 2009, Matt Taggart wrote: > Could it be changed so -v0 or something like -vall included everything? Yes, that behaviour is a bug/regression that was not intended. Fixed in git. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org wit

Bug#539268: dpkg: like to extract only individual files

On Thu, 30 Jul 2009, Toni Mueller wrote: > I'd like to be able to extract individual files from binary packages. Why should dpkg provide that? You can do that yourself anyway, there are severals way to do it already. The nicest way to do it is probably something like this: dpkg --fsys-tarfile pac

Bug#485330: Non-unified patches and dpkg source format ‘3.0 (quilt)’.

retitle 485330 Allow context diff in debian/patches/ in 3.0 (quilt) format thanks On Thu, 06 Aug 2009, Pierre Habouzit wrote: > That said, yes, using non-unified diff is as laughable as using RCS or > SCCS nowadays. Though I consider it a bug if dpkg refuses to apply a > patch that patch(1) (that

Bug#541077: [libc6]

On Tue, 11 Aug 2009, Peter Fritzsche wrote: > Ok, tried again and it seems to be that the first time it gets installed it > exists. The next time it is removed and doesnt appear again. What removes it? I suspect it's not dpkg... (or we would have noticed it already) > So > $ /var/cache/apt/archi

Bug#541077: [libc6]

On Tue, 11 Aug 2009, Peter Fritzsche wrote: > > What removes it? I suspect it's not dpkg... (or we would have noticed it > > already) > Hm, only started dpkg. So I suspected it. Did your machine crash/lose power during an upgrade? > work. The only thing I did in between was to reboot. Maybe it is

Bug#541077: [libc6]

On Thu, 13 Aug 2009, Guillem Jover wrote: > On Wed, 2009-08-12 at 23:27:05 +0200, Raphael Hertzog wrote: > > On Tue, 11 Aug 2009, Peter Fritzsche wrote: > > > > What removes it? I suspect it's not dpkg... (or we would have noticed it > > > > already) > >

Bug#485330: Non-unified patches and dpkg source format ‘3.0 (quilt)’.

On Thu, 13 Aug 2009, Pierre Habouzit wrote: > > - create directories that do not exist yet (patch will not do that for > > you AFAIK or at least that's the assumption that the current codebase > > made, it might have changed since this part of the code has been written) > > According to the ma

Bug#485330: Non-unified patches and dpkg source format ‘3.0 (quilt)’.

On Fri, 14 Aug 2009, Charles Plessy wrote: > Le Fri, Aug 14, 2009 at 10:41:40AM +0200, Raphael Hertzog a écrit : > > On Thu, 13 Aug 2009, Pierre Habouzit wrote: > > > > - create directories that do not exist yet (patch will not do that for > > > > you AFAIK or at

Bug#541464: dpkg-gensymbols: Does not fail with -c2 and new symbols.

On Fri, 14 Aug 2009, Kurt Roeckx wrote: > The documentation says that -c2 should fail if new symbols got > added, but it doesn't for me. Wildcard symbols do not allow this currently since you don't have any comprehensive list of symbols in the reference symbol file. Any symbol in the final file is

Bug#541412: dpkg: implement backups currently in cron package and better document it

On Fri, 14 Aug 2009, Leo 'costela' Antunes wrote: > Currently the code responsible for creating the files in > /var/backups/dpkg.status.* is in /etc/cron.daily/standard, which belongs > to the cron package. > > I'd suggest this functionality be brought into the dpkg package and > slightly better d

Bug#533916: Wontfix for now

tag 533916 + wontfix summary 533916 0 thanks with the feedback received and from what I understand, it's not a feature that I would like to support on the long term since there is no finite set of substitutions and those can change depending on external include files. Externalizing the definition

Bug#541829: dpkg-source.1: -m, -e, -C not documented

Hi, On Sun, 16 Aug 2009, Joachim Breitner wrote: > dpkg-buildpackage(1) claims that -C, -m and -e options are passed to > dpkg-source and documented in it’s manpage, but they are not mentioned > in either dpkg-source(1) nor "dpkg-source --help". Quoting dpkg-buildpackage(1) I see: -Cchange

Bug#542149: dpkg: please use “xz --format=lzma” instead of “lzma” when available

On Tue, 18 Aug 2009, Jonathan Nieder wrote: > I have been working on packaging XZ Utils, which is supposed to > eventually supersede LZMA Utils. To that end, it provides “lzma”, > “unlzma”, etc commands for compatibility with lzma, but scripts and > other programs are encouraged to use “xz” directl

Bug#535138: [dpkg] please also handle empty files in /var/lib/dpkg/alternatives

Hi, On Thu, 20 Aug 2009, Zoran Dzelajlija wrote: > A related bug, choking on leftover zero-length files in > /var/lib/dpkg/alternatives, might or might not warrant a separate report. The report already exists, it's 537558 and it's fixed in 1.15.4 (in git only for now). Cheers, -- Raphaël Hertzo

Bug#533916: Wontfix for now

On Thu, 20 Aug 2009, Modestas Vainius wrote: > Unfortunately, I have not got around to write tests / update man page for > these changes yet hence I never submitted the patch for review :/ I may post > it in the current state if you want to see it. Yeah, feel free to push it in a private git rep

Bug#543581: automatic patches in 3.0 (quilt) should contain a DEP-3 compliant header

Package: dpkg-dev Severity: wishlist User: d...@packages.debian.org Usertags: dpkg-source Automatic patches (debian/patches/debian-changes-) generated when using 3.0 (quilt) source packages should contain an autogenerated DEP-3 compliant header. This would facilitate usage of this format and contr

Bug#543603: dpkg-genchanges -v is unable to include the first changelog entry

forcemerge 537800 543603 thanks On Tue, 25 Aug 2009, Raphael Geissert wrote: > It is currently impossible to include the first changelog entry by the means > of dpkg-genchange's -v option, since specifying the first version will only > include the change sets greater than that version and specif

Bug#539692: dpkg-buildpackage ignores default-key in gpg.conf

clone 539692 -1 reassign -1 gnupg 1.4.9-4 retitle -1 gnupg should respect default-key when --local-user matches several private keys retitle 539692 dpkg-buildpackage should have a config file severity 539692 wishlist user d...@packages.debian.org usertags 539692 dpkg-buildpackage thanks On Mon, 0

Bug#544481: diff should not be an essential package

reassing 544481 apt 0.7.23.1 severity 544481 normal retitle 544481 apt mixes essential flag from all sources On Tue, 01 Sep 2009, Vincent Lefevre wrote: > > > I could help you to determine what's wrong in your system, but *not* > > > on the basis that I have to do something that I've *already* don

Bug#544732: dpkg preinst fails with empty file in /var/lib/dpkg/alternatives

forcemerge 537558 544732 thanks On Wed, 02 Sep 2009, Colin Tuckley wrote: > Package: dpkg > Version: 1.15.3.1 > Severity: normal > > dpkg preinst fails if there is a zero length file in > /var/lib/dpkg/alternatives The bug is already reported, did you check before filing it? Anyway, it's fixed

Bug#544732: dpkg preinst fails with empty file in /var/lib/dpkg/alternatives

On Wed, 02 Sep 2009, Colin Tuckley wrote: > Raphael Hertzog wrote: > > > The bug is already reported, did you check before filing it? Anyway, it's > > fixed in the upcoming 1.15.4. > > Yes I did check. But with over 300 bugs against the package it's very >

Bug#139569: Status of this bug?

On Thu, 03 Sep 2009, Vincent Lefevre wrote: > Hi, > > What's the status of this bug? > > On , it is said: > > Blocking fix for 411722: coreutils: "info printf" just gets the man > page, 483554: coreutils: "info chcon" gives the man pag

Bug#139569: Status of this bug?

On Thu, 03 Sep 2009, Vincent Lefevre wrote: > On 2009-09-03 11:34:30 +0200, Raphael Hertzog wrote: > > What about reading the last message in the history? dpkg's > > install-info is going away in 1.15.4 and all install-info bugs will > > be closed/reassigned to the new in

Bug#545081: dpkg-dev: dpkg-buildpackage -B should UNCONDITIONALLY invoke debian/rules build-arch

forcemerge 229357 545081 thanks On Fri, 04 Sep 2009, Zack Weinberg wrote: > As is well known, dpkg-buildpackage -B does not know whether it can If you knew well, you would have known that this bug already exists... it's #229357 and you're not helping us by opening a new bug report. dpkg-dev has

Bug#545081: dpkg-dev: dpkg-buildpackage -B should UNCONDITIONALLY invoke debian/rules build-arch

On Fri, 04 Sep 2009, Zack Weinberg wrote: > I disagree that this is 229357. That bug is about Build-Options. > This is a new proposal to *unconditionally* use build-arch in > dpkg-buildpackage -B. I'm not going to play control ping-pong, but > please reconsider. It's all the same, we can't fix t

Bug#545274: dpkg-dev: dpkg-source cannot verify GPG signatures

Hello, On Sun, 06 Sep 2009, Ian Bruce wrote: > $ dpkg-source --require-valid-signature -x psutils_1.17-27.dsc > gpgv: keyblock resource `/home/ian/.gnupg/trustedkeys.gpg': general error > gpgv: Signature made Wed 19 Aug 2009 04:21:54 PM PDT using DSA key ID > D688E0A7 > gpgv: Can'

Bug#229357: Bug#545081: dpkg-dev: dpkg-buildpackage -B should UNCONDITIONALLY invoke debian/rules build-arch

On Sun, 06 Sep 2009, Bill Allombert wrote: > Good, good, progress at last. Please find a patch that is a port of the > old patch.3.0 in the first post of #229357 and implement > Build-Options: build-arch as specified therein. First, if Build-Options is not integrated with DEB_BUILD_OPTIONS it shou

Bug#545274: dpkg-dev: dpkg-source cannot verify GPG signatures

On Sun, 06 Sep 2009, ian_br...@fastmail.net wrote: > On Sun, 6 Sep 2009 10:38:37 +0200 > Raphael Hertzog wrote: > > What's up with /home/ian/.gnupg/trustedkeys.gpg? > > Is it a good keyring file? Does it have correct permissions? > > > > Try again after moving

Bug#545366: dselect 1.15.4 does not distinguish between new and old packages

On Sun, 06 Sep 2009, Petr Vandrovec wrote: > Since today's update run dselect is completely confused and does not > remember which packages are new and which are old - it lists all > available and not installed packages as new, again and again. And > not only that, it also marks some of them for i

Bug#545529: dpkg: Version numbers won't be displayed correctly

On Mon, 07 Sep 2009, Carsten Grohmann wrote: > New version number isn't formatted properly. Especially the colon (":", > hex 3a) won't be displayed correctly. It's properly an i18n/l10n problem > because I use German language setting. What led you to believe that

Bug#545366: dselect 1.15.4 does not distinguish between new and old packages

severity 545366 serious thanks On Tue, 08 Sep 2009, Petr Vandrovec wrote: > IMHO change should be reverted until old functionality can be > achieved through some other way - unless you can achieve such > functionality today. I'd like to remind everybody that we're looking for someone to step up a

Bug#546577: Set DPKG_MAINTSCRIPT_NAME to the script name in maintainer scripts environment

Package: dpkg Version: 1.15.4 Severity: wishlist Please export DPKG_MAINTSCRIPT_NAME in the environment of maintainer scripts, it should contain the name of the maintainer script (prerm, postrm, preinst, postinst, config) that is currently running. See #546165 for an example of where it would hav

Bug#546731: Fwd: Re: Bug#546731: dpkg: 1.15.4 version pulls kde for upgrade

On Tue, 15 Sep 2009, Aleksey Midenkov wrote: > Guys! Placing some hints on dpkg about packages that may be broken is > wrong. Imagine that count of such packages is infinity, so you will > be keep putting all them inside dpkg control info? This is an > abstraction and the next is reality. You fi

Bug#536066: dpkg-dev: dpkg-parsechangelog doesn't emit Launchpad-Bugs-Fixed when vendor is Ubuntu

Hi Colin, On Tue, 07 Jul 2009, Colin Watson wrote: > dpkg-parsechangelog doesn't emit the Launchpad-Bugs-Fixed field when the > vendor is Ubuntu. In general I think handling this in dpkg-genchanges is > just the wrong place for it; other scripts mention Closes and so need to > handle Launchpad-Bug

Bug#546204: [dpkg-dev] dpkg-source: ignore flag doesn't work as expected

Hello, On Sat, 12 Sep 2009, Jason Heeris wrote: > When I use "dpkg-source -b -i" on an SVN source tree, the resulting > source package still contains the SVN control dirs. I would expect that > it would leave these out. Do you have a file nautilussvn_0.12.beta1.2.orig.tar.gz available? Because yo

Bug#229357: dpkg-buildpackage: support for Build-Options: build-arch

Hi, On Tue, 22 Sep 2009, Javier Serrano Polo wrote: > Could someone explain (again?) why "dpkg-buildpackage -B" should not add > build-arch to DEB_BUILD_OPTIONS? It doesn't require any control fields, > any make fiddling, it's compatible with old rules files... it just > works. What are you tryin

Bug#548663: dpkg: Save the config files's default content

forcemerge 32877 548663 thanks On Sun, 27 Sep 2009, Stefan Monnier wrote: > I think dpkg should systematically save the default content of each and > every file that might reasonably be expected to be modified by the user. This request is not new... please try to check open bug reports on the top

Bug#548661: dpkg: Override package dependencies

reassign 548661 general thanks On Mon, 28 Sep 2009, Stefan Monnier wrote: > reopen 548661 > thanks Please don't play ping-pong with bugs. Start a discussion on -devel if you want to get input on how to properly solve your problem, but it's far from being a reasonable wishlist request for dpkg at

Bug#549011: dpkg: Uses PATH rm (so might use safe-rm, which can be broken by broken perl), should use /bin/rm

reassign 549011 safe-rm retitle 549011 safe-rm provides a conflicting and less reliable rm command severity 549011 normal thanks On Wed, 30 Sep 2009, Didier Raboud wrote: > I had safe-rm installed and perl broke (#548848). dpkg went unuseable because > it was using /usr/bin/rm from safe-rm, broken

Bug#537800: marked as pending

Author: Raphael Hertzog Date: Tue Jul 21 10:14:00 2009 +0200 Dpkg::Changelog: fix heuristic to identify correct start entry The heuristic to identify the version number that is most approaching was not working properly for the case where the version number was smaller than the

Bug#537558: marked as pending

Author: Raphael Hertzog Date: Mon Jul 20 08:47:09 2009 +0200 Fix preinst to not fail on read on broken alternatives status files The internal structure of alternatives status file is line based. Empty lines end each section. read call can fail if the file is truncated at some

Bug#9771: marked as pending

: Raphael Hertzog Date: Fri Jul 3 15:35:50 2009 +0200 Add changelog entry for the install-info transition diff --git a/debian/changelog b/debian/changelog index a45f189..5722977 100644 --- a/debian/changelog +++ b/debian/changelog @@ -11,6 +11,13 @@ dpkg (1.15.4) UNRELEASED; urgency=low

Bug#523980: marked as pending

Author: Raphael Hertzog Date: Fri Jul 3 15:35:50 2009 +0200 Add changelog entry for the install-info transition diff --git a/debian/changelog b/debian/changelog index a45f189..5722977 100644 --- a/debian/changelog +++ b/debian/changelog @@ -11,6 +11,13 @@ dpkg (1.15.4) UNRELEASED; urgency=low

Bug#535138: marked as pending

Author: Raphael Hertzog Date: Fri Jul 3 15:43:29 2009 +0200 Fix dpkg's preinst when alternatives dir contains unexpected subdirs Adjust the lintian overrides accordingly. diff --git a/debian/changelog b/debian/changelog index 5722977..2dd90db 100644 --- a/debian/changelog

Bug#551638: 1.15.4.1 still broken

On Wed, 21 Oct 2009, Sandro Weiser wrote: > Today I installed dpkg, dpkg-dev and dselect 1.15.4.1. > I hoped that the error is fixed, but he is still there. > I use _only_ dselect, because I love it! > Can you please fix it? What is precisely the error that you're seeing? Cheers, -- Raphaël Hert

Bug#545366: the fix does not work

On Sat, 24 Oct 2009, Takehiko Abe wrote: > The fix does not work for me. dselect behaves the same way as it did > with 1.15.4.1. What dselect method are you all using? Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscr

Bug#551638: Bug#545366: dselect 1.15.4 does not distinguish between new and old packages

Version: 1.15.4.1 On Sun, 25 Oct 2009, Piotr Engelking wrote: > The only difference between 1.15.4 and 1.15.4.1 is that former marks > new and old packages as new, and the latter marks new and old packages > as old. That's what we wanted. Closing this bug again. The fact that it doesn't keep trac

Bug#545366: Am I missing something?

On Tue, 27 Oct 2009, Takehiko Abe wrote: > >That's what we wanted. Closing this bug again. The fact that it > >doesn't keep track of new packages is tracked in #551638 and is not > >release critical for us. > > What about the "it also marks some of them for installation although I > do not want th

Bug#545366: Am I missing something?

On Wed, 28 Oct 2009, Christian Perrier wrote: > Frankly speaking, for other packages where there is no real > maintainer, where the userbase is small and that have many bugs, we > are not that sentimental and the packages are removed from the > archive. Period, basta and voilà. > > Who is really t

Bug#553928: Change dpkg-source to produce new source formats by default

Package: dpkg-dev Severity: wishlist It's been my plan since some time to modify dpkg-source to produce new source formats by default, now that the archive accepts the new formats, it's about time to look closer on how to make this happen. For Debian as a whole, we need to fix the bugs listed her

Bug#553580: dpkg: "Unable to alter IO priority" when running inside a vserver

On Sun, 01 Nov 2009, Markus Fischer wrote: > When running inside a vserver, the capability to alter the IO priority may not > be available. This error has already been demoted to a simple warning in the upcoming dpkg 1.15.5. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-dpkg-

Bug#554612: /usr/bin/dpkg-source: include-binaries doesn't work

On Thu, 05 Nov 2009, Mike Hommey wrote: > A bit more information. It *hum*hum* works, actually, and the error > message above was due to remaining stuff in > debian/source/include-binaries. No, it really doesn't work as expected. It works in lenny but doesn't work properly in sid. I think it might

Bug#554612: /usr/bin/dpkg-source: include-binaries doesn't work

On Thu, 05 Nov 2009, Mike Hommey wrote: > > No, it really doesn't work as expected. It works in lenny but doesn't work > > properly in sid. I think it might be due to a behavioural difference > > in perl's File::Find... In fact no, it's a regression that I introduced in 3525f79792cff51757d99d45f51

Bug#554488: dpkg-dev: dpkg-source should support -su or -sn for 3.0 format packages

On Fri, 06 Nov 2009, Mike Hommey wrote: > On Thu, Nov 05, 2009 at 09:56:03AM +0100, Raphael Hertzog wrote: > > What I can do however is add a supplementary option like > > --create-empty-orig that would help bootstrap the process for your > > specific case (that would not e

Bug#554488: dpkg-dev: dpkg-source should support -su or -sn for 3.0 format packages

On Fri, 06 Nov 2009, Jaldhar H. Vyas wrote: > On Thu, 5 Nov 2009, Raphael Hertzog wrote: > > >On Wed, 04 Nov 2009, Jaldhar H. Vyas wrote: > >>What I would like to do instead is to use the multiple .orig.tar.gz > >>feature of the 3.0 (quilt) source format. Each modul

Bug#554488: dpkg-dev: dpkg-source should support -su or -sn for 3.0 format packages

On Fri, 06 Nov 2009, Mike Hommey wrote: > That pretty much depends on what dak is expecting to be the right files. > If it can handle the additional tarballs, doesn't it mean it properly > parses the .dsc and/or .changes files ? It does and verify that we have all the required files for the announ

Bug#554689: /usr/bin/dpkg-source: is slow

On Sat, 07 Nov 2009, Mike Hommey wrote: > We can go even further, with another optimization. > > As appeared in the profiles, abs2rel and canonpath take a lot of time. > It look like abs2rel is bloated for what it is used for. I applied the patch as well. Thanks! Cheers, -- Raphaël Hertzog

Bug#556786: dpkg-shlibdeps: Can't call method "epoch" on an undefined value

On Tue, 17 Nov 2009, Michael Biebl wrote: > since the update of dpkg-dev from 1.15.4 to 1.15.5, my packages fail to > build with the following message: > > Can't call method "epoch" on an undefined value at > /usr/share/perl5/Dpkg/Version.pm line 132. > dh_shlibdeps: dpkg-shlibdeps returned exit c

Bug#556786: dpkg-shlibdeps: Can't call method "epoch" on an undefined value

On Wed, 18 Nov 2009, Raphael Hertzog wrote: > On Tue, 17 Nov 2009, Michael Biebl wrote: > > since the update of dpkg-dev from 1.15.4 to 1.15.5, my packages fail to > > build with the following message: > > > > Can't call method "epoch" on an undefined val

Bug#556786: dpkg-shlibdeps: Can't call method "epoch" on an undefined value

On Wed, 18 Nov 2009, Raphael Hertzog wrote: > It doesn't seem to be the case. It fails doing > $dependencies{$cur_field}{$subdep} eq '' when the first arg is a Dpkg::Version > object and not a string. > > So it's definitely an RC bug. But it affects only packag

Bug#557459: dpkg-source: should not fallback to other formats without user intervention

Package: dpkg-dev Version: 1.15.5.2 Severity: wishlist It has been suggested on IRC that having dpkg-source switch back to native mode if it can't find the .orig tarball was probably a bad idea from the beginning and that it tends to confuse people. However, with the addition of new formats, I gen

Bug#557618: dpkg-dev - dpkg-source trashs source changes in "3.0 (quilt)" format if debian/patches is occupied

On Mon, 23 Nov 2009, Bastian Blank wrote: > dpkg-source trashs local changes in the "3.0 (quilt)" format if > debian/patches is occupied by a different patch system, like the > linux-2.6 package uses. Don't use 3.0 (quilt) if you don't want to comply with the restriction that it imposes... What d

Bug#557619: dpkg-dev - "3.0 (quilt)" format is incompatible to quilt

On Mon, 23 Nov 2009, Bastian Blank wrote: > The quilt usage in the "3.0 (quilt)" format is incompatible with normal > quilt. It uses debian/patches instead of patches. And what I am supposed to do? Ask quilt to use debian/patches and be done with it? Shall we document this in dpkg-source(1) ? $

Bug#557618: dpkg-dev - dpkg-source trashs source changes in "3.0 (quilt)" format if debian/patches is occupied

On Mon, 23 Nov 2009, Bastian Blank wrote: > You want to change the default, so you have to use a definition that > works. A definition? What do you mean? I never said all packages can be converted without some prior work. > > What do you expect me to do in response to this bug? > > * Document t

Bug#557619: dpkg-dev - "3.0 (quilt)" format is incompatible to quilt

On Mon, 23 Nov 2009, Bastian Blank wrote: > Find a way with the quilt maintainer to make this working without > special configuration. #557623 could be an answer. > > Ask quilt to use debian/patches and be done with it? > > Ask upstream about it, but I don't think this is a good idea. I

Bug#557667: dpkg-dev: behaving differently wether quilt is installed or not

notfound 557667 1.13.26 found 557667 1.14.25 thanks On Mon, 23 Nov 2009, Gerfried Fuchs wrote: > Version: 1.13.26 The etch version has no support of new formats at all... :) > Behaving differently wether quilt is installed or not is working against > the principles of least surprise, results in

Bug#557664: dpkg-dev - dpkg-source does not apply patches prior to generating 3.0 (quilt) source

tag 557664 moreinfo thanks On Mon, 23 Nov 2009, Bastian Blank wrote: > Package: dpkg-dev > Version: 1.15.5.2 > Severity: important > > The doc specifies, that dpkg-source will apply all quilt patches prior > to generating the automatic diff, however this seem to not work always: Read more closel

Bug#557668: dpkg-dev: Undefined subroutine crash on parsechangelog

On Mon, 23 Nov 2009, Andreas Marschke wrote: > Package: dpkg-dev > Version: 1.15.5.2 > Severity: important > > currently trying to package bangarang for my ppa on launchpad. > dpkg-buildpackage runs parsechangelog and it crashes with this line : > Undefined subroutine &Dpkg::Changelog::Entry::Debi

Bug#557664: dpkg-dev - dpkg-source does not apply patches prior to generating 3.0 (quilt) source

On Mon, 23 Nov 2009, Bastian Blank wrote: > On Mon, Nov 23, 2009 at 10:25:04PM +0100, Raphael Hertzog wrote: > > > A quick shows that this happens if the patch is unclean. > > Indeed, a first patch that can't be applied without having patch return an > > error c

Bug#557668: dpkg-dev: Undefined subroutine crash on parsechangelog

On Mon, 23 Nov 2009, Andreas Marschke wrote: > bangarang (1.0+beta2) karmic; urgency=low You have a 0x09 char after the "low". And in general the changelog is not really conforming to the norm. You should try "dch" to edit it, really. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, emai

Bug#557667: dpkg-dev: behaving differently wether quilt is installed or not

On Wed, 25 Nov 2009, Gerfried Fuchs wrote: > block 553928 with 557667 It's not up to you to decide such things... > > Would it be more acceptable if it could no more lead to FTBFS at all? > > That's a bit overrated, please keep the discussion to a sensible level. The remark is serious, I commi

Bug#557667: Breaks autobuilding

retitle 557667 dpkg-source does not create .pc without quilt severity 557667 important thanks On Fri, 27 Nov 2009, Marc Brockschmidt wrote: > This bug is a serious problems for our buildds. This is what happens on > praetorius, a modern installation using a chrooted (!) call of > dpkg-source: The

Bug#558233: marked as pending

tag 558233 pending thanks On Fri, 27 Nov 2009, Gerfried Fuchs wrote: > Actually, this isn't what Phil reported: > > * Philipp Kern [2009-11-27 10:09:33 CET]: > > dpkg-source breaks the assumption that it does the same with and > > without quilt being installed. C.f. crawl: > > Your changelog

Bug#558262: "dpkg-reconfigure -a" fails to complete

On Fri, 27 Nov 2009, Kalle Michanek wrote: > When one runs "dpkg-reconfigure -a" the process stops when it comes to a > package > that has changed from dpkg install-info to GNU install-info. Which package is that? That package should be fixed, there's nothing dpkg can do. The problem is probably

Bug#558262: "dpkg-reconfigure -a" fails to complete

reassign 558262 debconf thanks On Fri, 27 Nov 2009, Kalle Michanek wrote: > 2009/11/27 Raphael Hertzog > > > On Fri, 27 Nov 2009, Kalle Michanek wrote: > > > When one runs "dpkg-reconfigure -a" the process stops when it comes to a > > package > > >

Bug#559033: dpkg-dev: dpkg-buildpackage may fail on binary-only builds when using 3.0 (quilt) source format

Hi, On Tue, 01 Dec 2009, Cristian Greco wrote: > it seems that calling a debian/rules binary-only build target (i.e. with > dpkg-buildpackage -b, -B or -A option) when package is 3.0 (quilt) source > format and there is no quilt logic (patch/unpatch) in debian/rules (which is > what FAQ[0] page su

Bug#560391: dpkg-dev: dpkg-source --print-format fails to recognise 3.0 (quilt)

On Thu, 10 Dec 2009, Neil Williams wrote: > $ cd gpe-calendar-0.92/ > gpe-calendar-0.92$ dpkg-source --print-format . > 1.0 Try building with "dpkg-source -b ." and you'll see that it fails to select 3.0 (quilt). You need to call it in the same conditions than "dpkg-source -b", that means from so

Bug#560391: dpkg-dev: dpkg-source --print-format fails to recognise 3.0 (quilt)

On Fri, 11 Dec 2009, Neil Williams wrote: > That makes some very large assumptions about directory layout for > something as simple as querying/verifying a source format string. Well, it's the same code than -b except we stop right after having selected the target format. > Why does --print-forma

Bug#560587: /usr/bin/dpkg-source: Use $TMPDIR for .orig.tar.gz extraction

On Fri, 11 Dec 2009, Mike Hommey wrote: > There are currently 2 problems with the way the .orig.tar.gz file is > extracted during dpkg-source -b: > - When a package-ver.orig directory pre-exists, it gets removed. With format 1.0, there are many -s* options precisely to control this (you may want t

Bug#560587: /usr/bin/dpkg-source: Use $TMPDIR for .orig.tar.gz extraction

On Fri, 11 Dec 2009, Mike Hommey wrote: > On Fri, Dec 11, 2009 at 01:40:34PM +0100, Raphael Hertzog wrote: > > On Fri, 11 Dec 2009, Mike Hommey wrote: > > > There are currently 2 problems with the way the .orig.tar.gz file is > > > extracted during dpkg-source -b: >

Bug#560764: dpkg: format '3.0 (quilt)' patches fail but succeed with pure quilt

forcemerge 557667 560764 thanks On Sat, 12 Dec 2009, Jari Aalto wrote: > Version: 1.15.5.3 Please test with the latest version before reporting new bugs. > Building with debuild returns a failure but with quilt it > succeeds. See attached archive for use with testing. This has been fixed in 1.1

Bug#562155: dpkg-dev: Format 3.0 (quilt): Strange behaviour when debian/patches/series points to a file in one of the orig-$foo tarballs

On Wed, 23 Dec 2009, Fabian Greffrath wrote: > No comes the strange part: When I extract the resulting source package > 'test_1-1.dsc' via "dpkg-source -x test_1-1.dsc" it creates two(!) > directories, namely 'test-1' and 'foo'. The 'foo' directory contains > another directory with the name of the

Bug#562799: /usr/bin/dpkg is installed with 000 permission

tag 562799 unreproducible moreinfo severity 562799 important thanks On Mon, 28 Dec 2009, Cameron Horsburgh wrote: > dpkg stopped working after installing this version of the > package. Investigation revealed that /usr/bin/dpkg had permissions > of 000. `chmod 755 /usr/bin/dpkg` fixed the problem.

Bug#561237: dpkg: format 3.0 (quilt) -- If no patches, dpkg dies on error

Hi, On Thu, 07 Jan 2010, Jonathan Wiltshire wrote: > I reproduced this last night by chance with a package source stored in git > that I hadn't touched in just over a year. I just put "3.0 (quilt)" into > debian/source/format and built, but it failed because dpkg-source does not > create the .pc/

Bug#564140: dpkg-source: cannot write .pc/applied-patches when no patches present but upstream sources changed

forcemerge 561237 564140 thanks On Thu, 07 Jan 2010, Jonathan Nieder wrote: > Making the .pc directory by hand makes this work again. > > If a test case or more information is needed, please let me know. This is a duplicate report, it's already fixed in the sid branch. Cheers, -- Raphaël Hertz

Bug#563752: dpkg-dev: implementation of symbol patterns framework as well as c++, wildcard, regexp patterns

Hi Modestas, thanks for your work! Here are the results of my review. On Tue, 05 Jan 2010, Modestas Vainius wrote: > a7533ad Add Cppfilt module - interface to the c++filt utility. What happens when the toolchain starts using a (supposedly new) gnu-v4 method of mangling? How will we deal with tha

Bug#563752: dpkg-dev: implementation of symbol patterns framework as well as c++, wildcard, regexp patterns

On Sat, 09 Jan 2010, Modestas Vainius wrote: > Hello, > > On šeštadienis 09 Sausis 2010 20:14:39 Raphael Hertzog wrote: > > On Tue, 05 Jan 2010, Modestas Vainius wrote: > > > a7533ad Add Cppfilt module - interface to the c++filt utility. > > > > What happe

Bug#563752: dpkg-dev: implementation of symbol patterns framework as well as c++, wildcard, regexp patterns

On Sun, 10 Jan 2010, Modestas Vainius wrote: > Therefore, I will change 'gnu-v3' to 'auto'. Java will need to be implemented > separately (Cppfilt module supports any number of daemons). I wrote pattern > framework with 'java' in mind hence adding it will probably be only a couple > lines of cod

Bug#563752: dpkg-dev: implementation of symbol patterns framework as well as c++, wildcard, regexp patterns

Hi, On Sun, 10 Jan 2010, Modestas Vainius wrote: > Remote branch [1] has been updated. Notes: I cleaned up your branch and added some changes of mine, it's here: http://git.debian.org/?p=users/hertzog/dpkg.git;a=shortlog;h=refs/heads/pu/symbol-patterns I squashed some small fixes in some of your

Bug#563752: dpkg-dev: implementation of symbol patterns framework as well as c++, wildcard, regexp patterns

On Mon, 11 Jan 2010, Modestas Vainius wrote: > > Feel free to review. I'm going to merge this soon if you don't see any > > problem. > > You will need testsuite-fix.diff patch to make the code pass the testsuite. I > suggest --amend it to your old-style wildcards commit because the later > chang

Bug#566230: dpkg-buildpackage: please support --single-debian-patch

retitle 566230 dpkg-buildpackage: support passing arbitrary options to sub-commands tags 566230 - patch thanks Hi, > Please add --single-debian-patch to the list of options to be passed to > dpkg-source only. No, I'm not going to add all the dpkg-source options to dpkg-buildpackage. And that op

Bug#566406: after upgrade link group editor is broken

Hi, On Sat, 23 Jan 2010, mroot wrote: > After an upgrade dpkg gives me error message: > > Setting up ed (1.4-1) ... > Can't call method "slave" on an undefined value at > /usr/sbin/update-alternatives line 1037. > dpkg: error processing ed (--configure): > subprocess installed post-installation

Bug#566406: after upgrade link group editor is broken

On Sun, 24 Jan 2010, k...@mikroweb.hu wrote: > server:~# grep -v ^$ /var/lib/dpkg/alternatives/editor Empty lines are meaningful... don't drop them, attach the file as it is please. Were you trying to remove vim from your system when you got the problem ? Cheers, -- Raphaël Hertzog -- To UN

Bug#566406: after upgrade link group editor is broken

On Sun, 24 Jan 2010, k...@mikroweb.hu wrote: > manual Did you configure your alternative to manual mode at some point? Or did you change /etc/alternatives/editor manually? Many things are weird in your setup: - /usr/bin/editor points to /usr/bin/vim when it should point to /etc/alternatives/ed

Bug#567089: [LONG] Re: "Exec format error" bugs

Package: dpkg Version: 1.15.5.6 Severity: important [ For debian-dpkg, see https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/512096 for a description of the problem, basically a configuration script is empty /broken due to data loss and the recovery needs manual intervention ] Le mardi 26 janvi

Bug#569556: dpkg: [S-S-D] empties content of variable $SYSLOGD

On Fri, 12 Feb 2010, Wolfgang Wagner wrote: > Package: dpkg > Version: 1.14.25 > Severity: normal > > Tried to start sysklogs with option -r. > Set this option in /etc/init.d/sysklogd below line 18 SYSLOGD="-r" does > not work as in older debian versions. Is that after or before the line ". /etc

Bug#569618: Closes: lists duplicate bug numbers

found 569618 1.15.4 notfound 569618 1.15.4.1ubuntu1 thanks Hi, On Fri, 12 Feb 2010, Brian Murray wrote: > Package: dpkg > Version: 1.15.4.1ubuntu1 Please do not use ubuntu version numbers in the Debian BTS. > This isn't a very green solution and wastes lots of pixels and bits. > While the examp

Bug#569618: Closes: lists duplicate bug numbers

On Fri, 12 Feb 2010, Brian Murray wrote: > I did after the initial bug filing, sorry about that. Fine, I have been too quick in responding. :) > > Anyway, I suggest changing Dpkg/Vendor/Ubuntu.pm in the same way that I > > changed find_closes() in a8a51a4a53e923250ccc4bf0c2c040a211991c90. Feel >

Bug#567089: patch proposal to prevent delayed allocation and the zero-length file problem

tag 567089 + patch thanks Hi, On Sun, 14 Feb 2010, Jean-Baptiste Lallement wrote: > Here is a patch which adds some fsync on files and directories to > prevent delayed allocation and the zero-length file problem on ext4 > filesystem. Great, thanks for this! > This patch is build against dpkg 1.

<    1   2   3   4   5   6   7   8   9   10   >