On Sat, Oct 28, 2023 at 03:34:47PM +0300, Adrian Bunk wrote:
> On Fri, Oct 20, 2023 at 07:03:41AM +0100, Julian Gilbey wrote:
> > Hi!
> >
> > I'm completely out of my depth on this one, and I wonder whether
> > anyone might be able to help.
> > [...]
Package: dupload
Version: 2.9.4
Severity: wishlist
Hi!
Now that the release team have said that only source-only uploads will
be accepted for migration to bullseye (at least in debian/main), could
dupload be patched to check for this, asking for confirmation if the
.changes file is not source-onl
Package: dpkg-dev
Version: 1.16.12
The dpkg-buildflags manpage says that FFLAGS should be the same as
CFLAGS, but:
polya:~ $ dpkg-buildflags
CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security
CPPFLAGS=-D_FORTIFY_SOURCE=2
CXXFLAGS=-g -O2 -fstack-protector
Package: dpkg-dev
Version: 1.16.9
Severity: wishlist
It would be nice if dpkg-source could support 7z compressed files.
Julian
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
severity 303030 important
thanks
On Mon, Apr 04, 2005 at 02:04:24PM +0100, Francois wrote:
> Hello Scott,
>
> I still don't know where my problem came from, but I've (temporarily)
> solved it with 'dpkg --clear-avail'. Before that dpkg was refusing to
> install new packages from deb archives. Str
On Thu, Feb 19, 2009 at 07:18:43AM -0800, Daniel Burrows wrote:
> > The culprit seems to be dpkg itself; at the end of running "dpkg
> > --unpack ..." (called from aptitude), the available file is updated
> > (or at least touched); the same happened at the end of "dpkg
> > --configure ...".
> >
>
On Sun, Jul 06, 2008 at 06:39:32PM +0300, Guillem Jover wrote:
> Hi,
> [...]
> > > The fact that dpkg pays attention to the available file at all is a bug;
> > > it should only care about the state of the system and not about external
> > > repositories. Only higher level package managers like apt
On Thu, Dec 20, 2007 at 03:41:59AM +0100, dAniel hAhler wrote:
> With diverted files the "unable to create" error is confusing. [...]
> With the attached patch the error will look like the following instead:
> dpkg: error processing
> /var/cache/apt/archives/xserver-xorg-core_2%3a1.4.1~git2007121
Package: dpkg
Version: 1.14.16.6
When the texinfo info doc has been installed, the info file contains:
INFO-DIR-SECTION Texinfo documentation system
and so the dir file ends up with a section entitled "Texinfo
documentation system"
However, when packages providing info files specifying:
INFO-D
On Fri, Nov 24, 2006 at 05:18:31AM +0200, Guillem Jover wrote:
> tags 107449 - wontfix
> merge 393924 107449
> thanks
>
> Hi,
>
> > 2006/11/9, Julian Gilbey <[EMAIL PROTECTED]>:
> > > I'm reopening this bug report and reassigning it to dpkg, as dpkg
tags 397479 + patch
thanks
This trivial patch allows people who do -B -b to not get bitten; it
simply pays attention to the last option and not the first.
--- /usr/bin/dpkg-buildpackage 2006-06-21 16:08:36.0 +0100
+++ /tmp/dpkg-buildpackage 2006-11-08 16:02:50.0 +
@@ -10
I'm unclear why this bug has been tagged wontfix - no explanation is
given.
I'd like to see this bug resurrected and the (tiny) patch applied for
the following reason.
As the BTS now accurately tracks bug reports using version numbers,
and it is quite common to grab the version number using dpkg
Package: dpkg-dev
Version: 1.13.19
Severity: minor
Tags: patch
Problem with error message reading "at changelog , at changelog",
one-liner patch attached.
Julian
--- /usr/lib/dpkg/parsechangelog/debian 2006-05-04 12:08:59.0 +0100
+++ /tmp/debian 2006-05-28 09:44:50.0 +0100
@@ -
On Sun, Dec 04, 2005 at 12:42:40AM +0300, Nikita V. Youshchenko wrote:
> Devscripts may handle this situation by just picking not
> $package_$version_$arch.changes, but instead find the file that matches
> $package_$version_*.changes pattern.
> In one of the the previous mails, I wrote that there
On Sat, Dec 03, 2005 at 11:41:14PM +0300, Nikita V. Youshchenko wrote:
> I probably understood how 'sources' come in.
> If one first runs 'dpkg-buildpackage -S', a .changes file will be created
> with 'sources' in the arch part of the name. Later, if 'dpkg-buildpackage'
> is run to create binary
On Sat, Aug 20, 2005 at 11:32:07PM +0400, Nikita V. Youshchenko wrote:
> > Package: dpkg-cross, devscripts, dpkg-dev
> > Severity: normal
> >
> > If dpkg-cross is installed, it provides it's own dpkg-buildpackage,
> > which potentially replaces the *_${arch}.changes file with
> > *_source+${arch}.c
16 matches
Mail list logo
