NEW changes in stable-new

2018-12-30 Thread Debian FTP Masters
Processing changes file: libdatetime-timezone-perl_2.09-1+2018h_all.changes ACCEPT

Bug#917196: transition: qtbase-opensource-src

2018-12-30 Thread Lisandro Damián Nicanor Pérez Meyer
Hi! For what I understand, at this point, we currently need to: - Wait for calibre being built - Somehow make ci.debian.net understand that the latest kdeconnect upload fixed a buggy test (so not really a qt issue, just a race condition in the test) - Wait ~1 more day. Am I missing something el

Bug#906016: transition: gjs built with mozjs60

2018-12-30 Thread Jeremy Bicha
On Sun, Dec 23, 2018 at 10:30 AM John Paul Adrian Glaubitz wrote: > Can we postpone the decision until after the holidays? Then I have enough > time for trying to whip up a patch. I don't see any value in delaying any longer. It's pretty easy to let gjs/s390x back in; removing it has been quite a

NEW changes in stable-new

2018-12-30 Thread Debian FTP Masters
Processing changes file: libarchive_3.2.2-2+deb9u1_amd64.changes ACCEPT Processing changes file: libarchive_3.2.2-2+deb9u1_arm64.changes ACCEPT Processing changes file: libarchive_3.2.2-2+deb9u1_armel.changes ACCEPT Processing changes file: libarchive_3.2.2-2+deb9u1_armhf.changes ACCEPT Pro

Processed: libdatetime-timezone-perl 2.09-1+2018h flagged for acceptance

2018-12-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #917820 [release.debian.org] stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2018h Ignoring request to alter tags of bug #917820 to the same tags previously set -- 917820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917820 Debian

Bug#917820: libdatetime-timezone-perl 2.09-1+2018h flagged for acceptance

2018-12-30 Thread Adam D Barratt
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian . Thanks for your contribution! Upload details == Package: libdatetime-timezone-perl Version: 2.09-1+2018h Explanation: update includ

Processed: libdatetime-timezone-perl 2.09-1+2018h flagged for acceptance

2018-12-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #917820 [release.debian.org] stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2018h Added tag(s) pending. -- 917820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917820 Debian Bug Tracking System Contact ow...@bugs.debian.org with

[britney]: Do you use --control-files or the "legacy package layout" in your derivative?

2018-12-30 Thread Niels Thykier
Hi, I am writing to you, because I know that you are (or have been) involved in setting up or maintaining a britney instance for a Debian derivative. If you are no longer involving please let me know who to contact instead (where applicable). We are considering to deprecate the "legacy package

NEW changes in stable-new

2018-12-30 Thread Debian FTP Masters
Processing changes file: libdatetime-timezone-perl_2.09-1+2018h_sourceonly.changes REJECT

Bug#917820: stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2018h

2018-12-30 Thread gregor herrmann
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've uploaded libdatetime-timezone-perl 1:2.09-1+2018h to spu; it includes the data from tzdata 2018h as a quilt patch. >From the t

Bug#917805: release.debian.org: autopkgtests wrongly assume that package work in testing

2018-12-30 Thread Mattia Rizzolo
On Sun, Dec 30, 2018 at 03:10:27PM +0100, Aurelien Jarno wrote: > The upload of glibc 2.28-4 has trigger the pacemaker autopkgtest, which > failed due to bug#917801, caused by the migration of corosync 3.0.0-1 to > testing on 2018-12-26: > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/p

Re: Proposal: Repository for fast-paced package backports

2018-12-30 Thread Thomas Goirand
On 12/30/18 12:47 AM, Wouter Verhelst wrote: > On Wed, Dec 26, 2018 at 07:19:02PM +0100, Dominik George wrote: >> - It costs a lot time that could better be used elsewhere. >> - It costs extra money, which I for one do not have to spare. > > So ask someone who does and who would care about this

Bug#917803: marked as done (nmu: pacemaker_1.1.18-2)

2018-12-30 Thread Debian Bug Tracking System
Your message dated Sun, 30 Dec 2018 15:46:07 +0100 with message-id <20181230144605.xasn2aanmaklj...@debian.org> and subject line Re: nmu: pacemaker_1.1.18-2 has caused the Debian Bug report #917803, regarding nmu: pacemaker_1.1.18-2 to be marked as done. This means that you claim that the problem

Bug#917805: release.debian.org: autopkgtests wrongly assume that package work in testing

2018-12-30 Thread Aurelien Jarno
Package: release.debian.org Severity: normal The upload of glibc 2.28-4 has trigger the pacemaker autopkgtest, which failed due to bug#917801, caused by the migration of corosync 3.0.0-1 to testing on 2018-12-26: https://ci.debian.net/data/autopkgtest/testing/amd64/p/pacemaker/1613604/log.gz It

Bug#917803: nmu: pacemaker_1.1.18-2

2018-12-30 Thread Aurelien Jarno
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu pacemaker in buster hasn't been rebuilt in buster for the corosync transition, causing it to fail to start. In turns it causes the pacemaker autopkgtests to fail, which is considered as a gli

Processed: libi8x: Please rebuild for the Python 3.7 transition

2018-12-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.0.5-1 Bug #917781 [src:libi8x] libi8x: Please rebuild for the Python 3.7 transition Marked as fixed in versions libi8x/0.0.5-1. Bug #917781 [src:libi8x] libi8x: Please rebuild for the Python 3.7 transition Marked Bug as done > block 916817 by -1 8753731 Bu