Bug#904248: Beginnings of a patch to add netbase to build-essential

Josh Triplett writes: > Which effectively means the admin should never delete any existing entry > in the file, only add their own. It's a configuration file that is not supposed to ever be changed. If there are local changes, an admin will likely not include updates provided by newer packages.

Bug#911165: debian-policy: drop requirement to ship sysvinit init script with same name

Ansgar Burchardt writes: > c. It is better to ship integration with some init systems than >no integration at all. (Including sysvinit scripts at all is not >required, only when any other integrations are provided.) As a special example: DBus can start services on-demand. O

Bug#911165: debian-policy: drop requirement to ship sysvinit init script with same name

Package: debian-policy Version: 4.2.1.2 Severity: normal This requirement is currently included in Debian Policy: +--- | However, any package integrating with other init systems must also | be backwards-compatible with sysvinit by providing a SysV-style init | script with the same name as and

Bug#902180: RM: golang-github-docker-engine-api -- ROM; obsolete

Control: tag -1 moreinfo Dmitry Smirnov writes: > Please remove "golang-github-docker-engine-api" from "unstable". > > golang-github-docker-engine-api is an obsolete Docker client that has been > incorporated into Docker a while ago. Remaining reverse build dependencies > don't matter and they

Bug#902059: RM: docker-runc -- ROM; obsolete

Control: tag -1 moreinfo Dmitry Smirnov writes: > Please remove "docker-runc" from "unstable". There is still a package build-depending on docker-runc: # Broken Build-Depends: kubernetes: golang-github-opencontainers-docker-runc-dev Ansgar

Bug#910488: lists.debian.org: web archive for debian-efi@ not updated

Package: lists.debian.org X-Debbugs-Cc: debian-...@lists.debian.org The web archive for debian-efi@ at https://lists.debian.org/debian-ci/ do not seem to get updated since this month. There have been at least two messages that went over the list this month, but they aren't shown in the

Bug#909047: libc6.preinst: possible typo in 's/\bsamaba\b/smbd/g'

Package: libc6 Version: 2.27-6 Severity: normal libc6.preinst includes: -e's/\bsamaba\b/smbd/g' This looks like a typo to me. I assume it should be samba instead of samaba? Ansgar

Bug#905674: #905674: please describe ftpmasters' official position

On Sat, 2018-09-15 at 14:04 +0200, Adam Borowski wrote: > It would be nice if we had an official ftpmasters' position. So far, all > we have are remarks on IRC. > > The case here is the package "parallel" having recentlish grown a demand for > either a citation or 1€. This is explicitely

Bug#907483: grub-efi-*-signed-template: `Built-Using` must refer to source packages

Package: grub-efi-amd64-signed-template Version: 2.02+dfsg1-5 Severity: serious The `Built-Using` field of the source template refers to binary packages instead of source packages. This makes dak reject the upload of the signed packages: +--- | grub-efi-amd64-signed_1+2.02+dfsg1+5_amd64.deb:

Bug#906599: fwupd-*-signed-template: template generates empty binary packages

Package: fwupd-amd64-signed-template Version: 1.1.1-1 Severity: important >From the build log on amd64: +--- | drwxr-xr-x root/root 0 2018-08-13 13:08 ./ | drwxr-xr-x root/root 0 2018-08-13 13:08 ./usr/ | drwxr-xr-x root/root 0 2018-08-13 13:08 ./usr/share/ | drwxr-xr-x

Bug#906596: grub2: secure boot source templates build same source on different architectures

Package: src:grub2 Version: 2.02+dfsg1-5 Severity: important The source template in grub-efi-amd64-signed-template _amd64.deb and _i386.deb builds the same source package: grub-efi-amd64-signed. That is not possible. Same for the ia32 version. I suggest to only build the signed version for the

Bug#906351: dune-istl: FTBFS in buster/sid (error: static assertion failed)

Control: tag -1 fixed-upstream confirmed Control: forwarded -1 https://gitlab.dune-project.org/core/dune-istl/merge_requests/216 Santiago Vila writes: > /usr/include/c++/8/bits/stl_tree.h:457:21: error: static assertion failed: > comparison object must be invocable as const >

Bug#905482: fwupd-amd64-signed-template: invalid Depends (syntax error)

Package: fwupd-amd64-signed-template Version: 1.1.0-6 Severity: serious There is still one syntax error in the `Depends` field of the source package template (the `}`): Depends: ..., fwupd (= 1.1.0-6}) ^^^ This resulted in a build failure for

Bug#905471: fwupd-amd64-signed-template: conflicting source package name

Package: fwupd-amd64-signed-template Version: 1.1.0-5 Severity: serious >From the code signing service: +--- | dpkg-source: error: source package has two conflicting values - fwupd-amd64-signed and fwupd-signed-amd64 +--- d/changelog and d/control use different source package names. This

Bug#905468: fwupd-amd64-signed-template: invalid Build-Depends (syntax error)

Package: fwupd-amd64-signed-template Version: 1.1.0-4 Severity: serious The source template for code signing contains invalid Build-Depends: Build-Depends: ... fwupd (= ) [amd64] The version is missing. The same problem occurs in `Depends` too: Depends: ... fwupd (= }) Ansgar

Bug#905401: permit access to apt repositories during builds

Ian Jackson writes: > Apropos of discussion in #813471: > Paul writes: >> In addition, d-i relies on access to the apt repo for the system. >> I can imagine other uses of that, so I added a carve-out for that. > > In general I think this should be done by saying that packages may > access the apt

Bug#904864: pdftk-java: not (or no longer) licensed under MPL-1.1

Package: pdftk-java Version: 0.0.0+20180620.1-1 +--- | Files: java/pdftk/com/* |... | License: LGPL-2+ or MPL-1.1 +---[ debian/copyright ] But there is no mention of MPL-1.1 in the source files. There is however a script to remove the MPL-1.1 dual-license (as allowed):

Bug#898306: spl: conflicts with splat, but should not (was: splat: packaging error? : installation will remove apparently-unrelated packages)

Control: reopen -1 Control: reassign -1 spl 0.7.9-3 Control: retitle -1 spl: conflicts with splat, but should not "D. R. Evans" writes: > Marked as important, since this problem prevents installation here, so the > program cannot be used. > > Synaptic reports that installation of this package

Bug#903389: valgrind can't read debug info from binaries built with -z separate-code

Hi, I can confirm that the patch referenced at [1] seems to fix the problem (upstream commit 64aa729bfae71561505a40c12755bd6b55bb3061). I'll try to prepare a NMU for valgrind; maybe already this evening if I have time. The package isn't usable in the current state. Ansgar [1]

Bug#903038: expeyes: wrong autoremoval?

Control: reassign -1 qa.debian.org Control: user qa.debian@packages.debian.org Control: usertag -1 + udd On Thu, 2018-07-05 at 15:40 +0200, Georges Khaznadar wrote: > I got a notification, Message-Id: org>, > that: > > ---8<-- > expeyes 4.3.7+dfsg-2 is

Bug#902385: blacs-pvm-test: depends on removed package blacs-test-common

Control: clone 902385 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: blacs-pvm -- RoQA; blacs-test-common depends on removed package; PVM no longer used for parallel computing Control: severity -2 normal Muammar El Khatib writes: > On Mon, Jun 25, 2018 at 3:00 PM Ansgar Burcha

Bug#902922: lists.debian.org: web archive for debian-ci@l.d.o not updated

Package: lists.debian.org It looks like the web archives on https://lists.debian.org/debian-ci/ are not updated. I think the current archive only includes posts from the imported archive (from the old list on Alioth). Ansgar

Bug#902409: grep-excuses: uses YAML::Syck in a unsafe way

Package: devscripts Version: 2.18.3 Severity: grave File: /usr/bin/grep-excuses Tags: patch security grep-excuses uses YAML::Syck without telling YAML::Syck to not bless objects which might lead to running code the author of grep-excuses might not have intended to run. The attached patch tells

Bug#902385: blacs-pvm-test: depends on removed package blacs-test-common

Package: blacs-pvm-test Version: 1.1-21+b1 Severity: serious blacs-pvm-test depends on blacs-test-common which was just removed (#886711). I wonder if blacs-pvm is still useful? pvm was orphaned (#824403) and I don't know anyone still using PVM for parallel computations. Ansgar

Bug#902111: RM: libdune-grid-dev [armel] -- ROM; test failures on armel

Package: ftp.debian.org Severity: normal Control: close -1 -2 -3 Control: retitle -2 RM: libdune-grid-glue-dev [armel] -- ROM; depends on libdune-grid-dev Control: retitle -3 RM: libdune-pdelab-dev [armel] -- ROM; depends on libdune-grid-dev Control: block -1 by -2 -3 Please remove

Bug#902041: openmpi: broken on armel

FWIW, the same program also hangs on powerpc (partch.d.o). Ansgar

Bug#902101: openmpi: OpenMPI 3 on ppc64el seems unstable

Source: openmpi Version: 3.1.0-7 Severity: important OpenMPI 3 on ppc64el seems unstable: the test suite for dune-grid only passes ~30% of the time on ppc64el. In the other cases it hangs in MPI communication or gets unexpected results. I haven't been able to find a simpler test case yet (unlike

Bug#902041: openmpi: broken on armel

Source: openmpi Version: 3.1.0-7 Severity: serious OpenMPI seems to be very broken on armel. The C++ program below hangs often at a random iteration on abel.d.o (in a sid_armel-dchroot). I built the program using `mpic++ -Wall -std=c++14 -o test test.cc` and ran it with two ranks `mpirun -np 2

Bug#901320: debian-archive-keyring: remove Wheezy keys

Package: debian-archive-keyring Version: 2017.7 Severity: normal As Debian Wheezy is no longer maintained, the Wheezy keys should be removed from the keyring package: +--- | pub rsa4096/0x6FB2A1C265FFB764 2012-05-08 [SC] [expires: 2019-05-07] | ED6D65271AACF0FF15D123036FB2A1C265FFB764 |

Bug#900286: ITP: spm -- simple password manager

On Tue, 2018-05-29 at 13:11 -0400, Nicholas D Steeves wrote: > On Mon, May 28, 2018 at 07:46:59PM +0200, Jakub Wilk wrote: > > * Paride Legovini , 2018-05-28, 17:33: > > > spm is a single fully POSIX shell compliant script > > [...] > > > In Debian the script will be installed as 'spm.sh' > > >

Bug#898949: schroot: PAM config should use common-session-noninteractive

Package: schroot Version: 1.6.10-3 Severity: important The /etc/pam.d/schroot included in the package uses @include common-session Please use @include common-session-noninteractive instead as cron, at, ... already do. On systems with libpam-systemd installed using common-session will

Bug#898049: libdune-grid-dev: Differing versions break multi-arch support

Hi, Francois Gouget writes: > This concerns Debian Testing and Unstable: > > * For the alpha, amd64, arm64, mips64el and ppc64el architectures only > version 2.6.0-1+b1 is available. > > * For the armel, armhf, i386, mipsel and x32 architectures only > version 2.6.0-1 is available. Yes,

Bug#896769: ITP: tini -- tiny but valid init for containers

On Tue, 2018-04-24 at 16:39 +0800, ChangZhuo Chen wrote: > Tini is the simplest init you could think of. > . > All Tini does is spawn a single child (Tini is meant to be run in a > container), and wait for it to exit all the while reaping zombies > and > performing signal forwarding. What is

Bug#895804: RM: dune-grid [s390x] -- ROM; FTBFS on big-endian archs

Package: ftp.debian.org Severity: normal Control: clone -1 -2 -3 Control: retitle -2 RM: dune-grid-glue [s390x] -- ROM; FTBFS on big-endian archs Control: retitle -3 RM: dune-pdelab [s390x] -- ROM; FTBFS on big-endian archs Please remove dune-grid and its reverse dependencies dune-grid-glue and

Bug#895347: atheist: useless dependency on nmap

Package: atheist Version: 0.20110402-2.1 Severity: normal atheist depends on nmap, but doesn't seem to use it any more. I could only find the following occurences in the source package: +--- | ./atheist/plugins/net.py:#return os.system(self.cmd = 'nmap -p%s %s | grep "%s/%s open" >

Bug#894123: RM: nvidia-graphics-modules/oldstable -- RoQA; license problem; incompatible with current kernel ABI

Control: reassign -1 release.debian.org Control: user release.debian@packages.debian.org Control: usertag -1 + rm Control: tag -1 + jessie Removals from (old)*stable are handled by the release team; reassigning this bug to them. On Mon, 2018-03-26 at 16:51 +0100, Ben Hutchings wrote: > See

Bug#894195: beep: use `Package-Type: udeb` for beep-udeb in d/control

Package: src:beep Version: 1.3-4 Severity: important Please use `Package-Type: udeb` in d/control for beep-udeb. Otherwise wrong information ends up in the source package's Package-List field: it claims that beep-udeb is a `deb` (not a `udeb`). The special handling in d/rules (`dpkg --build ...

Bug#893873: reportbug: CC debian-boot@ for bugs against ftp.d.o asking for priority change

Package: reportbug Version: 7.1.10 Severity: wishlist [ Cc'ed -boot@ to ack this suggestion. ] Hi, the d-i team wants to be informed of priority changes affecting the default install. With Priority: extra gone, these are now all changes to the Priority. Please consider adding X-Debbugs-Cc:

Bug#893591: e2fsprogs: circular build dependency block build on kfreebsd

> On Tue, Mar 20, 2018 at 08:50:43AM +0100, Petter Reinholdtsen wrote: >> The automatic builders in Debian are unable to build e2fsprogs on >> kfreebsd, because the build depend on libtirpc1 depending on libcomerr2 >> (>= 1.01). Is there a good way to break this loop? >> >> The missing build

Bug#833525: debootstrap: Deleted my entire /home partition using "mostly harmless" debootstrap --print-debs option

Hideki Yamane writes: > Unfortunately, this patch would break behavior of --make-tarball option, > after creating tarball it cleans $TARGET but this patch prevent it even if > $TARGET doesn't exist before command runs. > > Here's revised patch attached. > +if [ -e

Bug#892819: at: improvements to atd.service

Package: at Version: 3.1.20-3.1 Severity: normal Tags: upstream atd.service should be ordered after nss-user-lookup.target to ensure user names can be looked up via NSS. This was recently fixed in cron, see for example https://bugs.debian.org/801384, and atd should have the same problems. It

Bug#891005: RFS: gdbm/1.14.1-5

Gianfranco Costamagna writes: >>This means building the package will give different results depending >>on dietlibc-dev installed or not? That shouldn't happen... >> >>Please check via some other means that a build using dietlibc has been >>requested; don't do different things just because a

Bug#891005: RFS: gdbm/1.14.1-5

On Tue, 2018-02-27 at 13:58 +0300, kact...@gnu.org wrote: > Anyhow, if you want to enable, you can do something like this, to > make > > me and you happy, and then easily revert when new bugs are opened > > > HAVE_DIETLIBC=no > ifeq ($(shell dpkg -s dietlibc-dev | grep -o

Bug#890258: ITP: quark -- An extremely small and simple HTTP GET-only web server

On Mon, 2018-02-12 at 16:05 +0100, Paride Legovini wrote: > * Package name: quark > Version : soon to be tagged > Upstream Author : Laslo Hunhold > * URL : https://tools.suckless.org/quark/ > * License : ISC > Programming Lang: C >

Bug#839046: debootstrap: enable --merged-usr by default

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 >

Bug#839046: debootstrap: enable --merged-usr by default

Ian Jackson writes: > Also, I fear that unless we provide a straightforward way to retain > separate /usr, including an appropriate d-i command line option, we > will get further pushback and anger from traditionalists. We risk > reopening old wounds (see some of the less temperate responses

Bug#889924: aptitude: obtaining changelogs

Hi, FWIW we added a `Changelogs` field to Debian's Release files so tools like apt or aptitude no longer have to hardcode the source URL for changelogs for every distribution. This was requested by the apt maintainers. See https://lists.debian.org/debian-dak/2015/08/msg00012.html Ansgar

Bug#840104: Encrypted uploads to the security archive

Philipp Kern writes: > On 01.02.2018 10:30, Ansgar Burchardt wrote: [...] >> There is already a `buildd-uploader` role account on the upload hosts >> both main and security archive, a `rsync-ssh-wrap` script, and someone >> also set up authorized_keys. >> >> I

Bug#889060: colord.postinst: colord -> root escalation on systems with fs.protected_hardlinks=0

Package: colord Version: 1.3.3-2 Severity: important Tags: security On systems with fs.protected_hardlinks=0 the postinst script allows escalation from the colord user to root: +--- | # sysctl fs.protected_hardlinks=0 | # runuser -u colord ln /bin/bash /var/lib/colord/bash | # ls -l /bin/bash |

Bug#840104: Encrypted uploads to the security archive

Philipp Kern writes: > On 31.01.2018 01:11, Ansgar Burchardt wrote: >> I'm not sure if buildds are already configured to upload to the security >> archive via ssh as they do for the main archive. It might be a good >> idea to do so. > > What's the requirement here? I

Bug#840104: Encrypted uploads to the security archive

Kurt Roeckx writes: > It's been a longstanding problem that the uploads to the security > archive are not encrypted in any way. I think this is a problem > for all embargoed uploads that we are doing. > > Upstream might actually do all that's possible to keep the > security issues secret. But it

Bug#887978: Backtrace

Hi, On Thu, 2018-01-25 at 21:43 -0600, John Hasler wrote: > No symbols package to be found: > > toncho/~ 23 sudo apt-get install solvespace-dbgsym > [sudo] password for john: > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to

Bug#888262: dh_strip: include debug symbols for binary maintainer "scripts"

Package: debhelper Version: 11.1.2 Severity: wishlist dh_strip should also include debug symbols for maintainer "scripts" that are binary programs in the *-dbgsym packages. The only example I'm aware of is dash (preinst). Ansgar

Bug#888096: archive.debian.org: add wheezy to archive.d.o

Package: mirrors Severity: normal Please import the wheezy suites from ftp.d.o to archive.d.o: - wheezy - wheezy-backports - wheezy-backports-sloppy - wheezy-proposed-updates - wheezy-updates This would allow us to remove the non-LTS architectures from the main archive, freeing a bit space

Bug#886639: tracker.debian.org: use Vcs-* fields from package with highest version

Package: tracker.debian.org Severity: wishlist tracker.debian.org seems to use the Vcs-* fields from the package currently in unstable for the links in the "general" section. It would be nice if it used the information from the package with the highest version instead. This is useful when an

Bug#886238: Please introduce official nosystemd build profile

On Wed, 2018-01-03 at 14:26 +0100, Samuel Thibault wrote: > > Do we really need systemd-less builds? I'm not convinced this is > > something relevant to Debian. > > Well, if Debian wants to remain relevant to downstreams, it'd be > better to accomodate their needs. I think there is only one

Bug#882736: [pkg-gnupg-maint] Bug#882736: gpg-agent: does not always use same socketdir

On Mon, 2017-11-27 at 20:30 +0100, Werner Koch wrote: > On Mon, 27 Nov 2017 18:24, ans...@debian.org said: > > > > this is a deliberate choice by upstream. > > > > Yes, I saw it in the source :-/ > > There is a clear reason for this. In the past we had lot of troubles > with too freely

Bug#882736: [pkg-gnupg-maint] Bug#882736: gpg-agent: does not always use same socketdir

On Mon, 2017-11-27 at 10:02 -0500, Daniel Kahn Gillmor wrote: > On Sun 2017-11-26 12:00:31 +0100, Ansgar Burchardt wrote: > > gpg(-agent) uses a different socketdir when a non-default homedir > > is > > specified depending on the environment: > > > > If /run/u

Bug#882736: gpg-agent: does not always use same socketdir

Package: gnupg Version: 2.1.18-8~deb9u1 Severity: normal gpg(-agent) uses a different socketdir when a non-default homedir is specified depending on the environment: If /run/user/ exists, it will use /run/user//gnupg/d.; otherwise it will fall back to . XDG_RUNTIME_DIR is intentionally

Bug#881424: RFP: ausweisapp2 -- online authentication using German identity document

"W. Martin Borgert" writes: > Owner: "W. Martin Borgert" A RFP bug with an owner? :-) > * Package name: ausweisapp2 > Version : 1.12.4 > Upstream Author : Governikus GmbH & Co. KG > * URL : https://github.com/Governikus/AusweisApp2 [...] > It

Bug#881812: xul-ext-treestyletab: new version required for Firefox 57

Package: xul-ext-treestyletab Version: 0.19.2017061601-1 Severity: important The version of xul-ext-treestyletab currently available in Debian doesn't work with Firefox 57. Please consider uploading the current upstream release to either experimental (in case the new version no longer works with

Bug#881612: debian-science: s/libalberta2-dev/libalberta-dev/

Package: src:debian-science Version: 1.7 Severity: normal Control: block 878199 by -1 Please depend on libalberta-dev instead of libalberta2-dev (which is a transitional package). Ansgar

Bug#881009: src:clips: typo in maintainer address (.og instead of .org)

Source: clips Source-Version: 6.30-3 Tags: sid Severity: serious > Source: clips > Binary: clips libclips libclips-dev clips-common clips-doc [...] > Version: 6.30-4 [...] > Maintainer: Javier Fernández-Sanguino Peña > Changed-By: Javier Fernández-Sanguino Peña

Bug#880645: wrong content in xz-compressed dep11 Components files (outdated)

Julian Andres Klode writes: [...] >> E: Failed to fetch >> store:/var/lib/apt/lists/partial/mirrors.wikimedia.org_debian_dists_unstable_non-free_dep11_Components-amd64.yml.xz >> Hash Sum mismatch >>Hashes of expected file: >> - Filesize:65721 [weak] >> -

Bug#877024: Modemmanager probing of unknown Devices

Sam Hartman writes: > Also, as may be obvious from my previous post today, I was shaken by > some of the meta issues here. I am much more focused at the moment on > thinking about the TC process and our community than I am about this issue. If the ctte believes that

Bug#876313: jessie-pu: package dput/0.9.6.4+deb8u1

"Adam D. Barratt" writes: > On Wed, 2017-09-20 at 22:10 +0200, Ansgar Burchardt wrote: >> I prepared an update for dput to point security uploads to >> ftp.security.upload.d.o instead of security-master.d.o, see >> attached diff. > > Please go ahead. Thanks, uploaded. Ansgar

Bug#869184: dpkg: source uploads including _amd64.buildinfo cause problems

Hi, > 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. This broke two uploads to the security archive again. That's not great, so this bug really should be

Bug#877024: modemmanager should ask before messing with serial ports

"Keith Packard" writes: > Ian Jackson writes: > > (speaking as a Debian user, not as a TC member) > >> I'm afraid don't really want to do the work of writing a better UI. >> But I have provided a simple patch which at least makes the behaviour >> safe. > > Would

Bug#876962: systemd: Default /etc/resolv.conf leak DNS lookups to Google

Control: unarchive 761658 Control: forcemerge 761658 -1 Petter Reinholdtsen writes: > By default, the systemd-resolved service in systemd will insert Google > controlled DNS servers in /etc/resolv.conf (8.8.8.8, 8.8.4.4, > 2001:4860:4860::,2001:4860:4860::8844) . The effect is that all DNS >

Bug#876900: dupload: option to not set permissions for uploads via rsync

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

Bug#876896: dput: please have rsync not change permissions (-p)

Package: dput Version: 0.12.1 Severity: normal dput 1.0.1 (and also 0.12.1) use the following rsync options (from dput/methods/rsync.py): --copy-links --progress --partial -zave 'ssh -x' -a implies quite a lot: -r: recursive; not wanted -l: copy-symlinks-as-symlinks; not wanted,

Bug#679751: Patch to close out this bug

Sean Whitton wrote: > +.. _s-nonexistent: > + > +Non-existent home directories > +~ > + > +The canonical non-existent home directory is ``/nonexistent``. Users > +who should not have a home directory should have their home directory > +set to this value. This is fine.

Bug#876313: jessie-pu: package dput/0.9.6.4+deb8u1

2013-07-19 13:08:40.0 +0200 +++ dput-0.9.6.4+deb8u1/debian/changelog2017-09-20 21:32:45.0 +0200 @@ -1,3 +1,10 @@ +dput (0.9.6.4+deb8u1) jessie; urgency=medium + + * dput.cf: replace security-master.d.o with ftp.upload.security.d.o +(Closes: #863348) + + -- Ansgar

Bug#874337: src:gr-iio: maintainer address bounces

Source: gr-iio Version: 0.2.36-1 Severity: serious [ X-Debbugs-Cc'ed last uploader. ] The maintainer address for gr-iio bounces (same for libad9361 and libiio), see below. Ansgar > Delivery has failed to these recipients or groups: > > Paul Cercueil

Bug#874291: developers-reference: security uploads should go to *.security.upload.d.o

Package: src:developers-reference Version: 3.4.18 Severity: normal Tags: patch Security uploads should not be uploaded to security-master.d.o, but ftp.security.upload.debian.org or (in the future) ssh.security.upload.debian.org. A patch to refer to *.security.upload.d.o or

Bug#688251: #688251: Built-Using description too aggressive

Sean Whitton writes: > +This field should not be used for purposes other than satisfying > +license requirements to provide full source code. The DFSG requires source code to be provided too... Ansgar

Bug#871671: Please treat non-uploader Debian Members like Debian Maintainers

Control: tag -1 confirmed Enrico Zini writes: > I would like dak to consider non-uploader Debian Members the same as Debian > Maintainers. This is fine with us. I contacted DSA to get the non-uploading keyring available on hosts processing uploads. Ansgar

Bug#872948: debootstrap: Debootstrap does not explain what is calls a Debian base system

Emmanuel Kasper writes: > The default base system installed by debootstrap includes all packages > with Pritority essential and > important, but this was not yet documented. There is no "essential" priority. There is only "required" (and its dependencies). Ansgar

Bug#872577: debootstrap: Handle existing /dev

Dan Nicholson writes: > On Fri, Aug 18, 2017 at 2:48 PM, Henrique de Moraes Holschuh > wrote: >> Wouldn't it be more straigthforward to "test -e || mknod" ? > > I definitely considered that, but it seemed more noisy to the code to > add a conditional for every call. But I'd be

Bug#798000: ftp.debian.org: please allow discarding maintainer-built binaries after NEW

Control: tag -1 wontfix Daniel Kahn Gillmor writes: > I agree with Simon that we should definitely discard maintainer-built > binaries from NEW (i also think we should discard them everywhere, but i > agree that NEW includes extra problems due to delays, transitions, etc). > > If the goal is to

Bug#798476: Maintainer information in source packages (was: Re: Returning to the requirement that Uploaders: contain humans)

Hi, as a more radical change one could also ask the question where to maintain the maintainer information. Currently we handle this in the source package via the Maintainer and Uploaders field, and via team memberships. This has several limitations: for teams, Uploaders will often be useless

Bug#869858: RM: pyfits -- ROM; superseeded by astropy

Control: tag -1 + moreinfo Aurelien Jarno writes: > Users have been warned to transition from pyfits to astropy. Now that > stretch has been released, it's time to remove pyfits from the archive. pyfits still has a reverse build-dep in the archive: +--- | dak rm -D -p -d 869858 -R -C package -m

Bug#870642: RM: python-afl [armel kfreebsd-i386 kfreebsd-amd64] -- RoQA; removal of afl requested

Package: ftp.debian.org Severity: normal Control: block 868734 by -1 Control: block 868735 by -1 Removal of afl from armel (#868734) and kfreebsd-* (#868735) has been requested by the maintainer. Its only reverse dependency python{,3}-afl should probably also be removed from these architectures.

Bug#870203: dune-grid FTBFS on mips: test-ug (Timeout)

Control: severity -1 important Adrian Bunk writes: > Start 31: test-ug > 31/60 Test #31: test-ug > ...***Timeout 300.02 sec Yes, saw the same issue also on PowerPC. I haven't found time to look at this yet and have asked for dune-grid and rdeps

Bug#870076: src:chrony: maintainer address bounces

Source: chrony Severity: serious Tags: sid The maintainer address for chrony bounces, see below. Ansgar Mail Delivery System writes: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one

Bug#870075: src:pdf-presenter-console: maintainer address bounces

Source: pdf-presenter-console Tags: sid Severity: serious The maintainer address for pdf-presenter-console bounces, see below. Ansgar Mail Delivery System writes: > This message was created automatically by mail delivery software. > > A message that you sent

Bug#869688: RM: dune-grid dune-grid-glue dune-pdelab [mips powerpc] -- ROM; test hangs on mips and powerpc

Package: ftp.debian.org Severity: normal One of the tests in dune-grid currently hangs on mips and powerpc. I haven't yet found time to investigate, but the updated package should migrate to testing. So please remove dune-grid and its reverse dependencies dune-grid-glue and dune-pdelab from

Bug#869236: dpkg: include binNMU version in .buildinfo file name

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

Bug#869184: dpkg: source uploads including _amd64.buildinfo cause problems

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

Bug#868737: gnome-exe-thumbnailer: unsafe use of /tmp

Package: gnome-exe-thumbnailer Version: 0.9.4-2 Severity: important Tags: security upstream gnome-exe-thumbnailer creates temporary files in /tmp using `mktemp` (e.g. ${TEMPFILE1}), but also uses those names with a suffix (e.g. ${TEMPFILE1}.vbs) which is not safe to do. Examples are (from [1]):

Bug#868057: davmail_4.8.0.2479-2_amd64.changes REJECTED, why

Hi, On Mon, 2017-07-17 at 13:19 +0200, Geert Stappers wrote: > Currently I don't know what I do wrong > while uploading davmail 4.8.0.2479-2 The upload did not include the source package. > Upload of davmail 4.8.0.2479-1 did happen. > It did in include the orig.tar.gz > > Upon my first upload

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

Hi, Russ Allbery writes: > Ansgar Burchardt <ans...@debian.org> writes: >> I discussed this a bit on IRC with the other ftp-masters and we came to >> this summary: [...] >> 2) We wonder if the 'standard' priority can also be dropped: as far as >>we know, it is

Bug#865536: systemd-sysv: Causes kernel panic if /usr isn't mounted due to liblz4.so being in /usr/lib

On Thu, 2017-06-22 at 07:56 -0500, John Goerzen wrote: > After the upgrade to stretch, my kernel paniced on boot.  I > eventually tracked the problem down to /usr not yet being mounted, > and /sbin/init needing liblz4.so which was in /usr. The /usr filesystem must be mounted by the initramfs (if

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

Hi, Russ Allbery writes: > ftp-master folks, we're discussing eliminating the requirement that > packages only depend on other packages with the same or higher priority > (so important packages would be able to depend on optional packages), and > deprecating the extra priority entirely (so

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

Hi, Russ Allbery writes: > Andreas Henriksson writes: >> Even if ftp-masters where really keen on actively managing the overrides >> file I wonder what purpose this would serve? > >> As already mentioned previously in this bug backlog it would just be a >> waste of ftp-master time. > >> Either

Bug#865279: xul-ext-noscript: new upstream version supporting e10s available

Package: xul-ext-noscript Version: 2.9.0.14-1 Severity: wishlist There are several new upstream releases. Of interest to me is that newer versions of noscript support e10s, starting with 2.9.5: + Full e10s compatibility Please update the package. Ansgar

Bug#865222: ftp.debian.org: incorrect links in README.html

Hi, Robert Luberda writes: > The http://ftp.debian.org/debian/README.html page contains the following > paragraph about stretch: > > Debian 9.0, or stretch > Debian 9.0 was released Saturday, 17th June 2017. Installation and > upgrading instructions, More information > > but both

Bug#865109: tryton-*: maintainer address bounces

Package: tryton-modules-production-routing Severity: serious Version: 4.4.0-1 X-Debbugs-Cc: Mathias Behrle Hi, please fix the maintainer address, see attachment. Ansgar --- Begin Message --- This is the mail system at host mail.virtual-things.org. I'm sorry to have to inform

Bug#864949: RM: ug -- ROM; superseded by dune-uggrid

Package: ftp.debian.org Severity: normal Please remove src:ug from the archive. It's use in DUNE is superseded by dune-uggrid which now contains UG's grid manager. Ansgar

Bug#864515: ITP: apiwrap-el -- api-wrapping macros

Control: owner -1 Matteo F. Vescovi "Matteo F. Vescovi" writes: > Package: wnpp > Owner: Matteo F. Vescovi ^ The domain part is somehow wrong. > API-Wrap.el is a tool to interface with the APIs of your favorite > services.

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