Processing of dpkg_1.17.9_amd64.changes

dpkg_1.17.9_amd64.changes uploaded successfully to localhost along with the files: libdpkg-dev_1.17.9_amd64.deb dpkg_1.17.9_amd64.deb dselect_1.17.9_amd64.deb dpkg-dev_1.17.9_all.deb libdpkg-perl_1.17.9_all.deb dpkg_1.17.9.dsc dpkg_1.17.9.tar.xz Greetings, Your Debian queue

dpkg_1.17.9_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Apr 2014 05:45:20 +0200 Source: dpkg Binary: libdpkg-dev dpkg dpkg-dev libdpkg-perl dselect Architecture: source amd64 all Version: 1.17.9 Distribution: unstable Urgency: high Maintainer: Dpkg Developers Change

stable update of dpkg (>= 1.17.2) and apt (>= 0.9.16.1) for build profiles

Hi, adding Adam because of request from Helmut (also added). Quoting Johannes Schauer (2014-04-26 07:15:03) > We would like to add build profile support [1] to packages in the archive and > because build profiles add a new syntax to Build-Depends, tools like dpkg and > apt need to be able to unde

Re: stable update of dpkg (>= 1.17.2) and apt (>= 0.9.16.1) for build profiles

On Wed, 2014-04-30 at 15:28 +0200, Johannes Schauer wrote: > adding Adam because of request from Helmut (also added). fwiw, if you're looking for a Release Team opinion on something that's already public, CCing me personally often isn't the best way of getting one. Aside from the fact that you ma

Dpkg translation schedule and current issues

Hello Guillem et al, given that the Freeze is approaching I'm asking when the major string changes announced in [1] are completed so that languages may start their update efforts, espeically for the man pages (I took the liberty to CC the translators you also CC'ed to make them aware of this as wel

Processing of dpkg_1.15.10_amd64.changes

dpkg_1.15.10_amd64.changes uploaded successfully to localhost along with the files: dpkg_1.15.10.dsc dpkg_1.15.10.tar.bz2 libdpkg-dev_1.15.10_amd64.deb dpkg_1.15.10_amd64.deb dselect_1.15.10_amd64.deb dpkg-dev_1.15.10_all.deb libdpkg-perl_1.15.10_all.deb Greetings, Your Debi

Processing of dpkg_1.16.14_amd64.changes

dpkg_1.16.14_amd64.changes uploaded successfully to localhost along with the files: dpkg_1.16.14.dsc dpkg_1.16.14.tar.xz libdpkg-dev_1.16.14_amd64.deb dpkg_1.16.14_amd64.deb dselect_1.16.14_amd64.deb dpkg-dev_1.16.14_all.deb libdpkg-perl_1.16.14_all.deb Greetings, Your Debia

dpkg_1.15.10_amd64.changes ACCEPTED into oldstable-proposed-updates->oldstable-new

Mapping oldstable-security to oldstable-proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Apr 2014 15:15:09 +0200 Source: dpkg Binary: libdpkg-dev dpkg dpkg-dev libdpkg-perl dselect Architecture: source amd64 all Version: 1.15.10 Distribution:

dpkg_1.16.14_amd64.changes ACCEPTED into proposed-updates->stable-new

Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Apr 2014 08:14:16 +0200 Source: dpkg Binary: libdpkg-dev dpkg dpkg-dev libdpkg-perl dselect Architecture: source amd64 all Version: 1.16.14 Distribution: wheezy-securi

Re: stable update of dpkg (>= 1.17.2) and apt (>= 0.9.16.1) for build profiles

Hi! On Wed, 2014-04-30 at 15:28:27 +0200, Johannes Schauer wrote: > Quoting Johannes Schauer (2014-04-26 07:15:03) > > Because of this syntax change, packages that use this syntax can only be > > uploaded once tools in Debian stable support it because the build > > infrastructure runs Debian stabl

Re: stable update of dpkg (>= 1.17.2) and apt (>= 0.9.16.1) for build profiles

On 2014-05-01 05:29, Guillem Jover wrote: > Just out of curiosity what part of the infrastructure requires an > updated dpkg to get profiles support? My guess would be lintian and > sbuild, anything else? Although isn't lintian run from a git checkout, > or is that only for lintian.d.o and not for

Re: Dpkg translation schedule and current issues

Quoting Helge Kreutzmann (deb...@helgefjell.de): > Hello Guillem et al, > given that the Freeze is approaching I'm asking when the major string > changes announced in [1] are completed so that languages may start > their update efforts, espeically for the man pages (I took the > liberty to CC the t