Hi,
On 2009-04-20, Bdale Garbee wrote:
On Mon, 2009-04-20 at 12:05 -0500, Jonathan Nieder wrote:
but I should have said Breaks: dpkg-dev ( 1.14.26). Sorry about that.
Oh! Of course. Thanks for the catch!
I suspect support for Breaks: was not so great in the past, so I can
see at least
Hi,
I wrote:
Would it be possible to add a
Breaks: dpkg ( 1.14.26)
line to a future release?
but I should have said Breaks: dpkg-dev ( 1.14.26). Sorry about that.
Regards,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
On Mon, 2009-04-20 at 12:05 -0500, Jonathan Nieder wrote:
but I should have said Breaks: dpkg-dev ( 1.14.26). Sorry about that.
Oh! Of course. Thanks for the catch!
Bdale
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Hi,
Julien Cristau wrote:
Same here. Looking at the tar changelog it's likely this is due to:
2008-11-25 Sergey Poznyakoff g...@gnu.org.ua
Do not try to drain the input pipe before closing the
archive.
tar closes its input fd, which sends SIGPIPE to gunzip, and dpkg
clone 522858 -1
reassign -1 dpkg
kthxbye
On Mon, Apr 6, 2009 at 17:45:33 -0700, Daniel Schepler wrote:
Since installing the latest version of tar, I'm getting failures in
attempting to extract certain deb packages. For example, with
telepathy-glib:
frobozz:/tmp$ dpkg-source -x
Package: tar
Version: 1.22-1
Severity: important
Since installing the latest version of tar, I'm getting failures in
attempting to extract certain deb packages. For example, with
telepathy-glib:
frobozz:/tmp$ dpkg-source -x telepathy-glib_0.7.29-1.dsc
dpkg-source: extracting telepathy-glib
6 matches
Mail list logo
