Bug#860227: unblock: gnome-shell-pomodoro/0.13.1-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gnome-shell-pomodoro The new version that has been in unstable for 15 days fixes: - 1 important bug #860149 that affects greatly the usability of the application -

Processed: Re: unblock (pre-approval): python-tornado/4.4.3-1

Processing control commands: > tags -1 - moreinfo Bug #859876 [release.debian.org] unblock (pre-approval): python-tornado/4.4.3-1 Removed tag(s) moreinfo. -- 859876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#859876: unblock (pre-approval): python-tornado/4.4.3-1

Control: tags -1 - moreinfo Hi, 2017-04-12 19:49 GMT+02:00 Ivo De Decker : > Looks like you forgot the diff. Could you send it? > yep, sorry for it, attaching now. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B

Bug#860215: marked as done (unblock: gegl/0.3.8-4)

Your message dated Wed, 12 Apr 2017 22:12:13 + with message-id and subject line unblock gegl has caused the Debian Bug report #860215, regarding unblock: gegl/0.3.8-4 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#860215: unblock: gegl/0.3.8-4

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, please unblock package gegl. This revision fixes the FTBFS on arm64, as reported in #856135. Attached, a debdiff from former failing -3 revision. Cheers. mfv --

Bug#857752: marked as done (unblock: apt-cacher-ng/3-1)

Your message dated Wed, 12 Apr 2017 22:10:19 +0200 with message-id <20170412201017.ga2...@ugent.be> and subject line Re: Bug#857752: unblock: apt-cacher-ng/3-1 has caused the Debian Bug report #857752, regarding unblock: apt-cacher-ng/3-1 to be marked as done. This means that you claim that the

Processed: Re: Bug#857752: unblock: apt-cacher-ng/3-1

Processing control commands: > reopen 857752 Bug #857752 {Done: Ivo De Decker } [release.debian.org] unblock: apt-cacher-ng/3-1 Bug reopened Ignoring request to alter fixed versions of bug #857752 to the same values previously set -- 856635:

Bug#857752: marked as done (unblock: apt-cacher-ng/3-1)

Your message dated Wed, 12 Apr 2017 21:05:33 +0200 with message-id <20170412190531.ga1...@ugent.be> and subject line Re: Bug#857752: unblock: apt-cacher-ng/3-1 has caused the Debian Bug report #857752, regarding unblock: apt-cacher-ng/3-1 to be marked as done. This means that you claim that the

Bug#859306: unblock: django-anymail/0.8-2

On Wednesday, April 12, 2017 08:33:57 PM Ivo De Decker wrote: > Control: tags -1 moreinfo > > Hi, > > On Sat, Apr 01, 2017 at 05:32:18PM -0400, Scott Kitterman wrote: > > Please unblock package django-anymail > > > > This is a pre-upload request. django-anymail 0.8-1 is currently in > > in

Processed: tagging 859794

Processing commands for cont...@bugs.debian.org: > tags 859794 + moreinfo Bug #859794 [release.debian.org] unblock: salt/2016.11.2+ds-1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 859794:

Processed: Re: unblock: django-anymail/0.8-2

Processing control commands: > tags -1 moreinfo Bug #859306 [release.debian.org] unblock: django-anymail/0.8-2 Added tag(s) moreinfo. -- 859306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#859306: unblock: django-anymail/0.8-2

Control: tags -1 moreinfo Hi, On Sat, Apr 01, 2017 at 05:32:18PM -0400, Scott Kitterman wrote: > Please unblock package django-anymail > > This is a pre-upload request. django-anymail 0.8-1 is currently in > in experimental. If this is approved, I'll upload to unstable with no changes > other

Bug#860186: marked as done (unblock: bijiben/3.20.2-1.1)

Your message dated Wed, 12 Apr 2017 18:30:10 + with message-id and subject line unblock bijiben has caused the Debian Bug report #860186, regarding unblock: bijiben/3.20.2-1.1 to be marked as done. This means that you claim that the problem has been

Bug#860196: marked as done (unblock: ansible/2.2.1.0-2)

Your message dated Wed, 12 Apr 2017 18:31:07 + with message-id and subject line unblock ansible has caused the Debian Bug report #860196, regarding unblock: ansible/2.2.1.0-2 to be marked as done. This means that you claim that the problem has been

Bug#860025: marked as done (unblock: bsdmainutils/9.0.12+nmu1)

Your message dated Wed, 12 Apr 2017 18:27:12 + with message-id and subject line unblock bsdmainutils has caused the Debian Bug report #860025, regarding unblock: bsdmainutils/9.0.12+nmu1 to be marked as done. This means that you claim that the problem

Bug#858779: marked as done (unblock: rt-extension-customfieldsonupdate/1.02-1)

Your message dated Wed, 12 Apr 2017 18:25:29 + with message-id and subject line unblock rt-extension-customfieldsonupdate has caused the Debian Bug report #858779, regarding unblock: rt-extension-customfieldsonupdate/1.02-1 to be marked as done. This

Bug#860196: unblock: ansible/2.2.1.0-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ansible Ansible has a potentially exploitable RCE that was just made public today. In cooperation with the security team, I've prepared an upload to unstable with

Bug#859962: marked as done (unblock: augeas/1.8.0-1)

Your message dated Wed, 12 Apr 2017 18:00:00 + with message-id <3e2bf17c-e219-c107-01b1-36e4a3c80...@thykier.net> and subject line Re: Bug#859962: unblock: augeas/1.8.0-1 has caused the Debian Bug report #859962, regarding unblock: augeas/1.8.0-1 to be marked as done. This means that you

Processed: Re: unblock (pre-approval): python-tornado/4.4.3-1

Processing control commands: > tags -1 moreinfo Bug #859876 [release.debian.org] unblock (pre-approval): python-tornado/4.4.3-1 Added tag(s) moreinfo. -- 859876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#859872: unblock (pre-approval): flask/0.12.1-1

Control: tags -1 confirmed moreinfo On Sat, 08 Apr 2017 12:57:41 +0200 Ondřej Nový wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please consider unblocking of flask 0.12.1-1. > > This upstream

Processed: Re: unblock (pre-approval): flask/0.12.1-1

Processing control commands: > tags -1 confirmed moreinfo Bug #859872 [release.debian.org] unblock (pre-approval): flask/0.12.1-1 Added tag(s) moreinfo and confirmed. -- 859872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859872 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#859876: unblock (pre-approval): python-tornado/4.4.3-1

Control: tags -1 moreinfo Hi, On Sat, Apr 08, 2017 at 01:20:32PM +0200, Ondřej Nový wrote: > Please consider unblock of package python-tornado 4.4.3-1. > > This is new upstream bugfix release, which fix this bug: > - The tornado.auth module has been updated for compatibility with a change >

Bug#859708: unblock: kodi/2:17.1+dfsg1-2

Control: tags -1 confirmed moreinfo On Thu, 6 Apr 2017 11:20:25 +0200 Balint Reczey wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Dear Release Team, > > Current kodi version in Stretch is

Processed: Re: unblock: kodi/2:17.1+dfsg1-2

Processing control commands: > tags -1 confirmed moreinfo Bug #859708 [release.debian.org] unblock: kodi/2:17.1+dfsg1-2 Added tag(s) confirmed and moreinfo. -- 859708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#859599: unblock: qemu/1:2.8+dfsg-4

Michael Tokarev: > 05.04.2017 20:42, Niels Thykier wrote: >> Control: tags -1 moreinfo >> >> On Wed, 05 Apr 2017 09:35:19 +0300 Michael Tokarev wrote: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian@packages.debian.org >>> Usertags: unblock >>>

Bug#856610: marked as done (unblock: sqlalchemy/1.1.5+ds1-1)

Your message dated Wed, 12 Apr 2017 19:19:39 +0200 with message-id <20170412171937.ga1...@ugent.be> and subject line Re: Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1 has caused the Debian Bug report #856610, regarding unblock: sqlalchemy/1.1.5+ds1-1 to be marked as done. This means that you claim

Bug#858891: marked as done (unblock: non-free otrs2/5.0.17-1)

Your message dated Wed, 12 Apr 2017 18:47:51 +0200 with message-id <20170412164750.ga1...@ugent.be> and subject line Re: Bug#858891: unblock: non-free otrs2/5.0.17-1 has caused the Debian Bug report #858891, regarding unblock: non-free otrs2/5.0.17-1 to be marked as done. This means that you

Processed: Re: unblock: tomcat8/8.5.12-1

Processing control commands: > tags -1 confirmed moreinfo Bug #858016 [release.debian.org] unblock: tomcat8/8.5.12-1 Added tag(s) moreinfo and confirmed. -- 858016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#858016: unblock: tomcat8/8.5.12-1

Control: tags -1 confirmed moreinfo Hi, On Fri, Mar 17, 2017 at 09:54:42AM +, Emmanuel Bourg wrote: > This is a pre-upload request to update tomcat8 to the version 8.5.12-1 > in stretch. This version is mostly a bug fix release, it also addresses > compatibility issues with Java 9 which will

Re: Resolving the kernel debug symbols vs signing problem

On Wed, 2017-04-12 at 07:50 +, Niels Thykier wrote: > Ben Hutchings: > > When implementing signed kernel packages, I wanted to make the signed > > image packages (built from linux-signed) take un-suffixed names so that > > existing procedures to install specific kernel versions would pick the

Bug#855229: marked as done (unblock: LDC and rdeps)

Your message dated Wed, 12 Apr 2017 18:34:51 +0200 with message-id <20170412163448.ga1...@ugent.be> and subject line Re: unblock: LDC and rdeps has caused the Debian Bug report #855229, regarding unblock: LDC and rdeps to be marked as done. This means that you claim that the problem has been

Bug#859756: marked as done (unblock: xapian-core/1.4.3-2)

Your message dated Wed, 12 Apr 2017 16:21:00 + with message-id <267ca027-60f9-e04a-3956-0bb6e95aa...@thykier.net> and subject line Re: unblock: xapian-core/1.4.3-2 has caused the Debian Bug report #859756, regarding unblock: xapian-core/1.4.3-2 to be marked as done. This means that you claim

Bug#860186: unblock: bijiben/3.20.2-1.1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, Please unblock package bijiben I discovered that the bijiben gnome-shell provider and internal bijiben search were not working at all. The included patch fix that by renaming the

Re: [Piuparts-devel] [stretch] Status on upgrade paths

On Wed, Apr 12, 2017 at 05:59:29PM +0200, Andreas Beckmann wrote: > On 2017-04-12 16:35, Holger Levsen wrote: > > On Wed, Apr 12, 2017 at 03:06:12PM +0200, Andreas Beckmann wrote: > >> Looking at wheezy2jessie2stretch (we don't have that on piuparts.d.o), > > > > how is that different from

Re: [Piuparts-devel] [stretch] Status on upgrade paths

On Wed, Apr 12, 2017 at 05:59:29PM +0200, Andreas Beckmann wrote: > On 2017-04-12 16:35, Holger Levsen wrote: > > On Wed, Apr 12, 2017 at 03:06:12PM +0200, Andreas Beckmann wrote: > >> Looking at wheezy2jessie2stretch (we don't have that on piuparts.d.o), > > > > how is that different from

Re: [Piuparts-devel] [stretch] Status on upgrade paths

On 2017-04-12 15:19, Michael Biebl wrote: > We regularly get a report about > https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch_aptdpkg_first/ > failing. > > Regular dist-upgrades of GNOME (i.e. no separate apt/dpkg upgrade first) > work fine though. > >

Bug#859255: marked as done (binNMU needed for more R packages.)

Your message dated Wed, 12 Apr 2017 15:40:00 + with message-id <034189af-57db-245e-f359-c46a392e9...@thykier.net> and subject line Re: Bug#859255: binNMU needed for more R packages. has caused the Debian Bug report #859255, regarding binNMU needed for more R packages. to be marked as done.

Re: Coordinated tzdata uploads between wheezy + jessie?

* Emilio Pozuelo Monfort [Wed Apr 12, 2017 at 04:29:36PM +0200]: > On 12/04/17 15:49, Michael Prokop wrote: > > According to https://tracker.debian.org/pkg/tzdata we have: > > [2017-04-07] Accepted tzdata 2017b-0+deb7u1 (source all) into oldstable > > (Emilio Pozuelo Monfort) > > [2017-04-08]

Bug#860025: unblock: bsdmainutils/9.0.12+nmu1 (pre-approval)

retitle 860025 unblock: bsdmainutils/9.0.12+nmu1 tags 860025 - moreinfo thanks Niels Thykier dixit: >Please go ahead and remove the moreinfo tag once the NMU has reached >unstable + have been built on all relevant architectures. According to

Processed: Re: Bug#860025: unblock: bsdmainutils/9.0.12+nmu1 (pre-approval)

Processing commands for cont...@bugs.debian.org: > retitle 860025 unblock: bsdmainutils/9.0.12+nmu1 Bug #860025 [release.debian.org] unblock: bsdmainutils/9.0.12+nmu1 (pre-approval) Changed Bug title to 'unblock: bsdmainutils/9.0.12+nmu1' from 'unblock: bsdmainutils/9.0.12+nmu1 (pre-approval)'.

Re: [Piuparts-devel] [stretch] Status on upgrade paths

On Wed, Apr 12, 2017 at 03:06:12PM +0200, Andreas Beckmann wrote: > Looking at wheezy2jessie2stretch (we don't have that on piuparts.d.o), how is that different from https://piuparts.debian.org/wheezy222testing/ which we *do* have on piuparts.d.o? (added by you :) for those not aware:

Re: Coordinated tzdata uploads between wheezy + jessie?

On 12/04/17 15:49, Michael Prokop wrote: > Hi, > > (explicitly Cc-ing Emilio and Aurelien, who usually take care of tzdata > uploads) > > According to https://tracker.debian.org/pkg/tzdata we have: > > [2017-04-07] Accepted tzdata 2017b-0+deb7u1 (source all) into oldstable > (Emilio Pozuelo

Coordinated tzdata uploads between wheezy + jessie?

Hi, (explicitly Cc-ing Emilio and Aurelien, who usually take care of tzdata uploads) According to https://tracker.debian.org/pkg/tzdata we have: [2017-04-07] Accepted tzdata 2017b-0+deb7u1 (source all) into oldstable (Emilio Pozuelo Monfort) [2017-04-08] Accepted tzdata 2017b-0+deb8u1 (source

Re: [Piuparts-devel] [stretch] Status on upgrade paths

Hi, Am 12.04.2017 um 15:06 schrieb Andreas Beckmann: > On 2017-04-12 13:26, Niels Thykier wrote: >> I see you have been busy filing bugs for issues in the upgrade path. >> Many thanks for that, it is greatly appreciated. :) >> >> Do you have an overview of how the upgrade paths are looking these

Re: [Piuparts-devel] [stretch] Status on upgrade paths

On 2017-04-12 13:26, Niels Thykier wrote: > I see you have been busy filing bugs for issues in the upgrade path. > Many thanks for that, it is greatly appreciated. :) > > Do you have an overview of how the upgrade paths are looking these days? > Like how much have we tested vs. how much is

Bug#859255: binNMU needed for more R packages.

Le Sat, Apr 01, 2017 at 03:24:53PM +0900, Charles Plessy a écrit : > > as a follow-up to #858183, I looked at which other R Bioconductor > packages were broken by R 3.3.3-1, and it seems that the previous round > of binNMUs did not repair some of them. > nmu r-bioc-rsamtools_1.26.1-2 . ANY . -m

Bug#860022: unblock: bsd-mailx/8.1.2-0.20160123cvs-3.1 (pre-approval)

On Wed, 12 Apr 2017, Niels Thykier wrote: > If the maintainer agrees with you on it, I am happy to accept that patch > for stretch. OK, thanks. > Mind you, I am also open to reviewing his proposal of > adding those headers even with -a (letting -a override the > auto-generated ones when there

Bug#858779: [request-tracker-maintainers] RFS: rt-extension-customfieldsonupdate-1.02-1

On Thu, Apr 06, 2017 at 08:20:04PM +0900, Satoru KURASHIKI wrote: > hi, > > To fix RC bug #857748, I've upload updated package to mentors, > which include changes only: > - new upstream version > - use libmodule-install-rtx-perl >

[stretch] Status on upgrade paths

Hi piuparts developers, I see you have been busy filing bugs for issues in the upgrade path. Many thanks for that, it is greatly appreciated. :) Do you have an overview of how the upgrade paths are looking these days? Like how much have we tested vs. how much is missing? Thanks, ~Niels

Bug#860140: unblock: libmongo-client/0.1.8-3

Ugh, Joerg told me he verified it to work :(. > On Apr 12, 2017, at 12:54 PM, Andreas Beckmann wrote: > > Control: reopen -1 > > diff -Nru libmongo-client-0.1.8/debian/libmongo-client-doc.maintscript > libmongo-client-0.1.8/debian/libmongo-client-doc.maintscript > ---

Bug#860140: unblock: libmongo-client/0.1.8-3

Control: reopen -1 diff -Nru libmongo-client-0.1.8/debian/libmongo-client-doc.maintscript libmongo-client-0.1.8/debian/libmongo-client-doc.maintscript --- libmongo-client-0.1.8/debian/libmongo-client-doc.maintscript 2017-04-08 21:57:18.0 +0200 +++

Processed: Re: Bug#860140: unblock: libmongo-client/0.1.8-3

Processing control commands: > reopen -1 Bug #860140 {Done: Niels Thykier } [release.debian.org] unblock: libmongo-client/0.1.8-3 Bug reopened Ignoring request to alter fixed versions of bug #860140 to the same values previously set -- 860140:

Bug#859950: marked as done (unblock: plasma-framework/5.28.0-2)

Your message dated Wed, 12 Apr 2017 09:54:31 +0200 with message-id and subject line Re: Bug#859950: unblock: plasma-framework/5.28.0-2 has caused the Debian Bug report #859950, regarding unblock: plasma-framework/5.28.0-2 to be marked as done.

Re: Resolving the kernel debug symbols vs signing problem

Ben Hutchings: > When implementing signed kernel packages, I wanted to make the signed > image packages (built from linux-signed) take un-suffixed names so that > existing procedures to install specific kernel versions would pick the > signed packages, and users would be discouraged from

Bug#859922: marked as done (unblock: cinnamon-screensaver/3.2.13-3)

Your message dated Wed, 12 Apr 2017 07:34:00 + with message-id and subject line Re: Bug#859922: unblock: cinnamon-screensaver/3.2.13-3 has caused the Debian Bug report #859922, regarding unblock: cinnamon-screensaver/3.2.13-3 to be marked as

Bug#859931: marked as done (unblock: kpty/5.28.0-2)

Your message dated Wed, 12 Apr 2017 07:31:00 + with message-id <1b0e98ef-4720-a21d-3e78-ae0031127...@thykier.net> and subject line Re: Bug#859931: unblock: kpty/5.28.0-2 has caused the Debian Bug report #859931, regarding unblock: kpty/5.28.0-2 to be marked as done. This means that you claim

Bug#859939: marked as done (unblock: kwidgetsaddons/5.28.0-2)

Your message dated Wed, 12 Apr 2017 07:28:00 + with message-id and subject line Re: Bug#859939: unblock: kwidgetsaddons/5.28.0-2 has caused the Debian Bug report #859939, regarding unblock: kwidgetsaddons/5.28.0-2 to be marked as done. This

Bug#859936: marked as done (unblock: ktexteditor/5.28.0-2)

Your message dated Wed, 12 Apr 2017 07:30:00 + with message-id and subject line Re: Bug#859936: unblock: ktexteditor/5.28.0-2 has caused the Debian Bug report #859936, regarding unblock: ktexteditor/5.28.0-2 to be marked as done. This means

Bug#859942: marked as done (unblock: networkmanager-qt/5.28.0-2)

Your message dated Wed, 12 Apr 2017 07:22:00 + with message-id and subject line Re: Bug#859942: unblock: networkmanager-qt/5.28.0-2 has caused the Debian Bug report #859942, regarding unblock: networkmanager-qt/5.28.0-2 to be marked as done.

Bug#859950: unblock: plasma-framework/5.28.0-2

Maximiliano Curia: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Dear release team, > > I've backported some upstream fixes in kio for stretch that I consider > worthwhile, these are all described in the correspoding

Bug#860022: unblock: bsd-mailx/8.1.2-0.20160123cvs-3.1 (pre-approval)

Control: tags -1 confirmed moreinfo Thorsten Glaser: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > I would like to request a pre-approval before uploading a fixed > package. The bug in question is #859935 (bsd-mailx sends

Bug#860127: marked as done (unblock gcc packages)

Your message dated Wed, 12 Apr 2017 06:37:00 + with message-id <724be128-c3e2-ec81-0224-534c657c4...@thykier.net> and subject line Re: Bug#860127: unblock gcc packages has caused the Debian Bug report #860127, regarding unblock gcc packages to be marked as done. This means that you claim that

Bug#860131: marked as done (unblock: freedink/108.4+dfsg-3)

Your message dated Wed, 12 Apr 2017 06:25:00 + with message-id and subject line Re: Bug#860131: unblock: freedink/108.4+dfsg-3 has caused the Debian Bug report #860131, regarding unblock: freedink/108.4+dfsg-3 to be marked as done. This means

Bug#860129: marked as done (unblock: cytadela/1.1.0-4)

Your message dated Wed, 12 Apr 2017 06:05:00 + with message-id <949dae92-509a-7424-4138-4e7ec4fb6...@thykier.net> and subject line Re: Bug#860129: unblock: cytadela/1.1.0-4 has caused the Debian Bug report #860129, regarding unblock: cytadela/1.1.0-4 to be marked as done. This means that you

Bug#860130: marked as done (unblock: zsh/5.3.1-4)

Your message dated Wed, 12 Apr 2017 06:05:00 + with message-id <1e1f3c74-3539-5399-6780-f766d17ee...@thykier.net> and subject line Re: Bug#860130: unblock: zsh/5.3.1-4 has caused the Debian Bug report #860130, regarding unblock: zsh/5.3.1-4 to be marked as done. This means that you claim that

Bug#860140: marked as done (unblock: libmongo-client/0.1.8-3)

Your message dated Wed, 12 Apr 2017 06:04:00 + with message-id and subject line Re: Bug#860140: unblock: libmongo-client/0.1.8-3 has caused the Debian Bug report #860140, regarding unblock: libmongo-client/0.1.8-3 to be marked as done. This