Signed-off-by: Ansgar Burchardt ans...@43-1.org
---
The man page includes the following line
$v =item $v-as_string()
as there is no empty line before the =item statement. Just using a comma
instead of multiple =items is done a few lines before as well.
Regards,
Ansgar
scripts/Dpkg
Hi,
On 06/11/2012 11:26 AM, Niels Thykier wrote:
Archive support
---
The FTP masters have requested that all signatures are stored in a
single ar member of the deb. That member should then contain a flat
directory (ie no sub-directories) of signature files, [...]
Hi,
with wheezy released and development on jessie started the problem with
binNMUs for multiarch-enabled packages is back: binNMU'ed packages have
different changelog entries and upgrades fail (for example [1]).
[1] http://bugs.debian.org/708097
It's quite annoying as the problem is only
Hi,
[ dropped -release and -wb-team, added 681289@bugs.d.o ]
Guillem Jover guil...@debian.org writes:
On Mon, 2013-05-13 at 17:04:51 +0100, Ian Jackson wrote:
The real problem is that these changelog files are primarily intended
for human beings. They should live in /usr/share/doc, and their
Hi,
[ dropped -release and -wb-team ]
Jonathan Nieder jrnie...@gmail.com writes:
One problem that that doesn't solve is what to do when a package would
be able to borrow its /doc/package directory from another package
(using a symlink) but for the changelog and copyright (which gets even
For the override file we also need to know which binaries are udeb's.
I suggest using udeb:package in this case (analogous to
src:package).
Regards,
Ansgar
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: dpkg
Version: 1.16.1.2
Severity: wishlist
Hi,
it would be nice if dpkg-query could show the source package and source
version for a binary, for example for use in the Built-Using field:
Built-Using: foo-source (= 1.2)
Maybe something like
dpkg-query -f='${show:Source-Package} (=
Guillem Jover guil...@debian.org writes:
On Thu, 2011-12-29 at 17:36:35 +0100, Raphael Hertzog wrote:
On Thu, 29 Dec 2011, Ansgar Burchardt wrote:
Maybe something like
dpkg-query -f='${show:Source-Package} (= ${show:Source-Version})' -W
foo-binary
I suggested this to Ansgar on IRC
Package: dpkg-dev
Version: 1.16.9
Severity: minor
File: /usr/bin/dpkg-architecture
dpkg-archtecture -iany-armel does not work as expected, ie. it returns false on
armel:
% dpkg-architecture -aarmel -iarmel; echo $?
0
% dpkg-architecture -aarmel -iany-armel; echo $?
1
But returns true for
On 11/28/2012 05:25 PM, Guillem Jover wrote:
Precisely because it's the cpu and not the arch, as can be seen from
«dpkg-architecture -aarmel -qDEB_HOST_ARCH_CPU». I can well concede that
though, that this might not seem intuitive, but then lots of things in
dpkg architecture names aren't
Package: dpkg-dev
Version: 1.16.9
Severity: important
File: /usr/bin/dpkg-source
dpkg-source --require-valid-signature -x gnupg_1.4.12-6.dsc with the attached
dsc file will process the gnupg part of the dsc. This is however not covered by
the signature.
This happens as Dpkg::Control::Hash skips
Meh, forgot the attachment...
Ansgar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 3.0 (native)
Source: dpkg
Binary: libdpkg-dev, dpkg, dpkg-dev, libdpkg-perl, dselect
Architecture: any all
Version: 1.16.9
Origin: debian
Maintainer: Dpkg Developers debian-d...@lists.debian.org
Hi,
On 12/14/2012 02:51 PM, Guillem Jover wrote:
This happens as Dpkg::Control::Hash skips until an empty line:
145 } elsif (m/^-BEGIN PGP SIGNED MESSAGE/) {
146 $expect_pgp_sig = 1;
147 if ($$self-{'allow_pgp'}) {
148
Package: dpkg-dev
Version: 1.17.10
Severity: normal
Hi,
dpkg-source -x will fail on certain archives if SIGPIPE is ignored as
can happen is some non-interactive uses. The archives need trailing
zeroes so that tar exits, but the compressor still has data to write
to the pipe.
An example can be
Holger Levsen hol...@layer-acht.org writes:
together with Lunar we four sad together on the last Saturday of DebConf15 in
Heidelberg and discussed the next steps forward to achieve the inclusion of
.buildinfo inclusion in the Debian archive and output by dpkg.
On the ftpmaster side we
Package: dpkg-dev
Version: 1.17.25
Severity: minor
File: /usr/bin/dpkg-architecture
Hi,
I was wondering what the difference between "host machine" and "target
machine" is. Clearly the compiler has to build binaries for the target
machine.
>From dpkg's changelog I understand that "target
Package: dpkg
Version: 1.18.24
Severity: important
source-only uploads sometimes include a _amd64.buildinfo (or other
architecture). This sometimes causes problems as the amd64 buildd
upload will include a file using the same name.
In particular, it breaks any uploads going to policy queues
Package: dpkg
Version: 1.18.24
Severity: important
For similar reasons as given in #869184, please also include the
binNMU version in generated .buildinfo files (as already done in
.changes).
We recently had a samba upload to security which also got binNMUed as
it was built in an unclean
Package: dupload
Version: 2.8.2
Some time ago we moved the upload queues away from ftp-master.d.o to
ftp.upload.d.o. This allowed us to no longer run ftpd directly on
ftp-master.
The same will hopefully happen to security-master: eventually
security-master will no longer run a ftpd, but uploads
Package: dupload
Version: 2.8.4
Severity: normal
dupload 2.8.4 and 2.9.0 currently use the following rsync options:
rsync --partial -zave ssh $options -x
-a implies quite a lot:
-r: recursive; not wanted
-l: copy-symlinks-as-symlinks; not wanted, opposite is needed
-p: copy
Guillem Jover writes:
> In any case, I looked the other day into implementing the
> --map-pathname option for dpkg-query, and I've got most of the code
> ready. The problem is that this requires adding support for config
> files and config fragments to dpkg-query, which has the additional
>
On Mon, 2019-06-17 at 13:12 -0700, Vagrant Cascadian wrote:
> > This behaviour is really causing issues for the security-archive so in
> > one way or the other there needs to be a solution. Regularly we need
> > to fetch the buildd changes and build binary packages, resign them and
> > reupload
Mattia Rizzolo writes:
> On Tue, Jun 18, 2019 at 06:29:12PM +0200, Ansgar Burchardt wrote:
>> The .buildinfo files are referred to in the .changes files; renaming
>> them would require updating the .changes file. The .changes files are
>> used to upload the security
Package: apt,dselect
Severity: normal
Hi,
[ X-Debbugs-Cc'ed -boot@ for debootstrap ]
today I learned that debootstrap as special code to create the file
/var/lib/dpkg/cmethopt (contents: "apt apt"); this is the function
setup_dselect_method in functions. It seems wrong that debootstrap
has
24 matches
Mail list logo
