Accepted ruby-defaults 1:2.5~1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 08:31:00 -0200 Source: ruby-defaults Binary: ruby ruby-dev ruby-all-dev libruby ruby-tcltk ri ruby-full Architecture: source Version: 1:2.5~1 Distribution: unstable Urgency: medium Maintainer: Antonio Terceiro

Accepted eccodes 2.6.0-2 (source all amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 11:23:32 + Source: eccodes Binary: libeccodes0 libeccodes-data libeccodes-dev libeccodes-tools python3-eccodes libeccodes-doc Architecture: source all amd64 Version: 2.6.0-2 Distribution: unstable Urgency:

Accepted process-cpp 3.0.1-3 (source amd64 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 10:15:27 + Source: process-cpp Binary: libprocess-cpp3 libprocess-cpp-dev libprocess-cpp-doc Architecture: source amd64 all Version: 3.0.1-3 Distribution: unstable Urgency: medium Maintainer: Chris Lamb

Accepted getdns 1.3.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 06:08:08 -0500 Source: getdns Binary: libgetdns-dev libgetdns6 getdns-utils stubby Architecture: source Version: 1.3.0-1 Distribution: unstable Urgency: medium Maintainer: getdns packagers

Accepted ibus-libpinyin 1.9.2-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 17:50:37 +0800 Source: ibus-libpinyin Binary: ibus-libpinyin Architecture: source Version: 1.9.2-2 Distribution: unstable Urgency: medium Maintainer: IME Packaging Team

Accepted telepathy-glib 0.24.1-2 (source amd64 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 11:50:21 +0100 Source: telepathy-glib Binary: libtelepathy-glib0 libtelepathy-glib-dev libtelepathy-glib-doc gir1.2-telepathyglib-0.12 Architecture: source amd64 all Version: 0.24.1-2 Distribution: unstable

Re: proposal: ITR (was Re: Removing packages perhaps too aggressively?)

* Scott Kitterman [180201 09:04]: > On February 1, 2018 1:47:17 PM UTC, Marvin Renich wrote: > >I agree that the FTP team should not second guess the maintainer's > >removal request. However, with or without a new ITR process, I think > >it would be

Re: Removing packages perhaps too aggressively?

On Thu, Feb 01, 2018 at 11:10:43AM +0100, Andrej Shadura wrote: > > On 01/02/18 09:45, Andrej Shadura wrote: > >> On 01/02/18 09:40, Ansgar Burchardt wrote: > >>> So there was plenty of time to fix them. > >>> > >>> Why would filing a third RC bug (the "proposed-RM") and waiting one > >>> month

Accepted pnetcdf 1.9.0-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 09:32:52 + Source: pnetcdf Binary: libpnetcdf-dev pnetcdf-bin libpnetcdf0d Architecture: source amd64 Version: 1.9.0-1 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry

Re: Removing packages perhaps too aggressively?

On Thu, Feb 1, 2018 at 5:18 PM, Philipp Kern wrote: > Oh wow, I didn't realize x3270 got removed. :( ... > I agree that you shouldn't second-guess, but I think you can at least > enforce some comment to be present. As someone who now ponders to > re-introduce the package I have zero context as

Accepted sbcl 2:1.4.4-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 10:56:57 +0100 Source: sbcl Binary: sbcl sbcl-doc sbcl-source Architecture: source Version: 2:1.4.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Common Lisp Team

Accepted libnfs 1.11.0-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 11:00:46 +0100 Source: libnfs Binary: libnfs-dev libnfs8 Architecture: source Version: 1.11.0-3 Distribution: unstable Urgency: medium Maintainer: Ritesh Raj Sarraf Changed-By: Balint Reczey

Accepted id3v2 0.1.12+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 13:24:36 +0100 Source: id3v2 Binary: id3v2 Architecture: source Version: 0.1.12+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Tille

Accepted gnome-builder 3.26.4-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 07:49:41 -0500 Source: gnome-builder Binary: gnome-builder Architecture: source Version: 3.26.4-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers

Accepted snapper 0.5.4-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 22:11:03 +0900 Source: snapper Binary: snapper libsnapper4 libsnapper-dev libpam-snapper Architecture: source amd64 Version: 0.5.4-1 Distribution: unstable Urgency: medium Maintainer: Hideki Yamane

Accepted network-manager-strongswan 1.4.2-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Jan 2018 06:08:36 +0100 Source: network-manager-strongswan Binary: network-manager-strongswan Architecture: source Version: 1.4.2-2 Distribution: unstable Urgency: medium Maintainer: Harald Dunkel

Re: proposal: ITR (was Re: Removing packages perhaps too aggressively?)

* Mattia Rizzolo [180201 03:26]: > I seriously doubt ITRs or somesuch would help, you wouldn't notice them > anyway. > If you can parse a list of ITRs you can equally easy parse a list of > packages with open RC bugs with next to the same effect. I disagree. As a user, if I

Accepted eventstat 0.04.03-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 1 Feb 2018 10:03:05 + Source: eventstat Binary: eventstat Architecture: source amd64 Version: 0.04.03-1 Distribution: unstable Urgency: medium Maintainer: Colin King Changed-By: Colin King

Accepted node-uuid 1.4.7-2 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 13:04:59 +0100 Source: node-uuid Binary: libjs-node-uuid node-node-uuid Architecture: source all Version: 1.4.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

Accepted quota 4.04-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 12:53:43 +0100 Source: quota Binary: quota Architecture: source amd64 Version: 4.04-2 Distribution: unstable Urgency: medium Maintainer: Michael Meskes Changed-By: Michael Meskes

Accepted screenfetch 3.8.0-7 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 20:53:27 +0900 Source: screenfetch Binary: screenfetch Architecture: source all Version: 3.8.0-7 Distribution: unstable Urgency: medium Maintainer: Hideki Yamane Changed-By: Hideki Yamane

Re: Removing packages perhaps too aggressively?

Scott Kitterman writes ("Re: Removing packages perhaps too aggressively?"): > As the FTP team member that processed that removal, I can tell you I think > it's perfectly fine. I don't think the FTP team should be in the business of > second guessing maintainers that say their packages should be

Accepted borgbackup 1.1.4-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 30 Jan 2018 22:14:58 +0100 Source: borgbackup Binary: borgbackup borgbackup-doc Architecture: source Version: 1.1.4-2 Distribution: unstable Urgency: medium Maintainer: Danny Edel Changed-By: Mattia

Re: Removing packages perhaps too aggressively?

On February 1, 2018 12:53:40 PM UTC, Ian Jackson wrote: >Scott Kitterman writes ("Re: Removing packages perhaps too >aggressively?"): >> As the FTP team member that processed that removal, I can tell you I >think >> it's perfectly fine. I don't think the FTP

Bug#889054: ITP: pytest-astropy -- Metapackage to resolve pytest dependencies for Astropy

Package: wnpp Severity: wishlist Owner: Ole Streicher X-Debbugs-Cc: debian-pyt...@lists.debian.org, debian-devel@lists.debian.org * Package name: pytest-astropy Version : 0.2.1 Upstream Author : Thomas Robitaille * URL :

Accepted node-uuid 1.4.7-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:00:19 +0530 Source: node-uuid Binary: libjs-node-uuid node-node-uuid Architecture: source Version: 1.4.7-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

Accepted nvme-cli 1.5-1 (source ppc64el) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 29 Jan 2018 12:59:02 -0500 Source: nvme-cli Binary: nvme-cli Architecture: source ppc64el Version: 1.5-1 Distribution: unstable Urgency: medium Maintainer: Breno Leitao Changed-By: Breno Leitao

Accepted ansible 2.4.3.0+dfsg-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 13:45:09 +0100 Source: ansible Binary: ansible Architecture: source all Version: 2.4.3.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Harlan Lieberman-Berg Changed-By: Lee

Accepted gnome-documents 3.26.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 07:53:38 -0500 Source: gnome-documents Binary: gnome-documents Architecture: source Version: 3.26.2-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers

Re: proposal: ITR (was Re: Removing packages perhaps too aggressively?)

On February 1, 2018 1:47:17 PM UTC, Marvin Renich wrote: >* Mattia Rizzolo [180201 03:26]: >> I seriously doubt ITRs or somesuch would help, you wouldn't notice >them >> anyway. >> If you can parse a list of ITRs you can equally easy parse a list of >>

Accepted miniupnpd 2.0.20171212-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 16:39:16 + Source: miniupnpd Binary: miniupnpd Architecture: source amd64 Version: 2.0.20171212-1 Distribution: unstable Urgency: medium Maintainer: Thomas Goirand Changed-By: Thomas Goirand

Accepted hw-detect 1.130 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:21:09 +0100 Source: hw-detect Binary: hw-detect ethdetect disk-detect driver-injection-disk-detect archdetect Architecture: source Version: 1.130 Distribution: unstable Urgency: medium Maintainer: Debian Install

Accepted python-django 1:1.11.10-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 17:42:06 + Source: python-django Binary: python-django python-django-common python-django-doc python3-django Built-For-Profiles: nocheck Architecture: source all Version: 1:1.11.10-1 Distribution: unstable

Accepted autopep8 1.3.4-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 20:31:10 +0100 Source: autopep8 Binary: python-autopep8 Architecture: source Version: 1.3.4-1 Distribution: unstable Urgency: medium Maintainer: Sylvestre Ledru Changed-By: Sylvestre Ledru

Bug#889075: ITP: qt5-engines-kvantum -- SVG-based theme engine for Qt5

Package: wnpp Severity: wishlist Owner: Alf Gaida * Package name: qt5-engines-kvantum Version : 10.5 Upstream Author : Pedram Pourang * URL : https://github.com/tsujan/Kvantum * License : GPL-3.0+ Programming

Accepted uwsgi-plugin-php 0.0.3 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 19:43:43 +0100 Source: uwsgi-plugin-php Binary: uwsgi-plugin-php Architecture: source amd64 Version: 0.0.3 Distribution: unstable Urgency: medium Maintainer: uWSGI packaging team

Accepted opendht 1.5.0-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 17:47:24 + Source: opendht Binary: libopendht-dev dhtnode Architecture: source Version: 1.5.0-3 Distribution: unstable Urgency: medium Maintainer: Alexandre Viau Changed-By: Alexandre Viau

Accepted hugin 2018.0.0~rc2+dfsg-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 18:48:05 +0100 Source: hugin Binary: hugin hugin-tools hugin-data Architecture: source Version: 2018.0.0~rc2+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian PhotoTools Maintainers

Accepted libebur128 1.2.4-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:58:27 +0100 Source: libebur128 Binary: libebur128-dev libebur128-1 Architecture: source Version: 1.2.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers

Accepted iso-scan 1.64 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:51:53 +0100 Source: iso-scan Binary: iso-scan load-iso Architecture: source Version: 1.64 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By:

Re: Removing packages perhaps too aggressively?

If you do reintroduce it, please note the extra steps (reopening bugs in particular) On that note one thing that doesn't seem to be easy/well documented is how to go about finding the bugs that affected a package at the time of it's removal. If I go to the bugs page for the package and select

Accepted bitstream 1.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 19:32:28 +0100 Source: bitstream Binary: libbitstream-dev Architecture: source Version: 1.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers

Accepted biboumi 7.2-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 20:03:54 +0100 Source: biboumi Binary: biboumi Architecture: source amd64 Version: 7.2-1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team

Accepted vlc 3.0.0~rc8-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 20:00:43 +0100 Source: vlc Binary: vlc libvlc-dev libvlc5 libvlccore-dev libvlccore9 libvlc-bin vlc-bin vlc-data vlc-l10n vlc-plugin-base vlc-plugin-access-extra vlc-plugin-video-output vlc-plugin-video-splitter

Accepted python-django 2:2.0.2-1 (source all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 17:57:13 + Source: python-django Binary: python3-django python-django-doc Built-For-Profiles: nocheck Architecture: source all Version: 2:2.0.2-1 Distribution: experimental Urgency: medium Maintainer: Debian

Accepted ring 20180119.1.9e06f94~ds1-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 17:49:53 + Source: ring Binary: ring ring-daemon Architecture: source Version: 20180119.1.9e06f94~ds1-3 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team

Accepted ignition-cmake 0.4.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Jan 2018 23:32:15 + Source: ignition-cmake Binary: libignition-cmake-dev Architecture: source Version: 0.4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Accepted spectre-meltdown-checker 0.34-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 20:27:53 +0100 Source: spectre-meltdown-checker Binary: spectre-meltdown-checker Architecture: source Version: 0.34-1 Distribution: unstable Urgency: medium Maintainer: Sylvestre Ledru

Re: Removing packages perhaps too aggressively?

On Thu, 2018-02-01 at 12:23 +0200, Lars Wirzenius wrote: > On Thu, 2018-02-01 at 11:10 +0100, Abou Al Montacir wrote: > > In general I agree with this as a DD, but when I wear my user hat I don't. > > I disagree, I'm afraid. As a user, the speed in which we do removals > from testing or unstable

Accepted quantlib 1.12-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 05:56:04 -0600 Source: quantlib Binary: libquantlib0v5 libquantlib0-dev quantlib-examples Architecture: source amd64 Version: 1.12-1 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel

Accepted node-uuid 1.4.7-5 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 16:00:43 +0100 Source: node-uuid Binary: libjs-node-uuid node-node-uuid Architecture: source all Version: 1.4.7-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

Accepted php-mongodb 1.3.4-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 15:07:41 + Source: php-mongodb Binary: php-mongodb Architecture: source Version: 1.3.4-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PECL Maintainers

Accepted liblivemedia 2018.01.29-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:31:09 +0100 Source: liblivemedia Binary: liblivemedia-dev libbasicusageenvironment1 libgroupsock8 liblivemedia62 libusageenvironment3 livemedia-utils Architecture: source Version: 2018.01.29-1 Distribution:

Accepted libplacebo 0.3.0-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:36:39 +0100 Source: libplacebo Binary: libplacebo-dev libplacebo3 Architecture: source Version: 0.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers

Accepted gnome-photos 3.26.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 09:00:48 -0500 Source: gnome-photos Binary: gnome-photos Architecture: source Version: 3.26.3-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers

Accepted python-pymummer 0.10.3-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 29 Jan 2018 15:46:12 +0100 Source: python-pymummer Binary: python3-pymummer Architecture: source all Version: 0.10.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team

Accepted node-uuid 1.4.7-4 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 15:15:03 +0100 Source: node-uuid Binary: libjs-node-uuid node-node-uuid Architecture: source all Version: 1.4.7-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

Accepted aephea 12-248-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 14:46:06 +0100 Source: aephea Binary: aephea Architecture: source Version: 12-248-3 Distribution: unstable Urgency: medium Maintainer: Joost van Baal-Ilić Changed-By: Andreas Tille

Accepted node-buf-compare 1.0.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:16:45 +0530 Source: node-buf-compare Binary: node-buf-compare Architecture: source Version: 1.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

Accepted xkeyboard-config 2.23.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 17:30:40 +0200 Source: xkeyboard-config Binary: xkb-data xkb-data-udeb Architecture: source Version: 2.23.1-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force

Accepted streamtuner2 2.2.0+dfsg-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 02 Feb 2018 00:40:40 +0900 Source: streamtuner2 Binary: streamtuner2 Architecture: source all Version: 2.2.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers

Re: proposal: ITR (was Re: Removing packages perhaps too aggressively?)

On 2018-02-01 15:03, Scott Kitterman wrote: I agree that the FTP team should not second guess the maintainer's removal request. However, with or without a new ITR process, I think it would be justified (and good practice) for the FTP team to start requiring the maintainer to record in the bug

Accepted farstream-0.2 0.2.8-4 (source amd64 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 16:26:57 +0100 Source: farstream-0.2 Binary: libfarstream-0.2-5 libfarstream-0.2-dev libfarstream-0.2-doc gir1.2-farstream-0.2 Architecture: source amd64 all Version: 0.2.8-4 Distribution: unstable Urgency: medium

Accepted php-ast 0.1.6-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 15:20:35 + Source: php-ast Binary: php-ast Architecture: source Version: 0.1.6-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PECL Maintainers Changed-By:

Accepted xdebug 2.6.0+2.5.5-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 31 Jan 2018 21:29:22 + Source: xdebug Binary: php-xdebug Architecture: source Version: 2.6.0+2.5.5-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PECL Maintainers

Accepted php-solr 2.4.0-5 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Sep 2017 07:13:35 +0200 Source: php-solr Binary: php-solr Architecture: source Version: 2.4.0-5 Distribution: unstable Urgency: medium Maintainer: Debian PHP PECL Maintainers

Accepted php7.2 7.2.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 15:19:04 + Source: php7.2 Binary: libapache2-mod-php7.2 libphp7.2-embed php7.2 php7.2-cgi php7.2-cli php7.2-dev php7.2-fpm php7.2-phpdbg php7.2-xsl php7.2-odbc php7.2-readline php7.2-recode php7.2-sqlite3

Accepted iio-sensor-proxy 2.4-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 20:39:37 +0530 Source: iio-sensor-proxy Binary: iio-sensor-proxy Architecture: source amd64 Version: 2.4-2 Distribution: unstable Urgency: medium Maintainer: Ritesh Raj Sarraf Changed-By: Ritesh

Re: Removing packages perhaps too aggressively?

On Thu, Feb 01, 2018 at 09:45:55AM +0100, Andrej Shadura wrote: > On 01/02/18 09:40, Ansgar Burchardt wrote: > > Why would filing a third RC bug (the "proposed-RM") and waiting one > > month more change anything? Why would someone turn up to fix them now? > > Why not? I *was* already doing just

What is the point of RFA? Was: Re: proposal: ITR

On Thu, Feb 1, 2018 at 5:46 PM, Thomas Goirand wrote: > We already have RFA, where maintainers are asking for adoption. I fail > to see how a different type of bug will trigger a quicker adoption. An > ITR is going to (unfortunately) achieve the exact same thing as an RFA, >

Re: Removing packages perhaps too aggressively?

On Thu, Feb 01, 2018 at 09:24:05PM +0100, Abou Al Montacir wrote: > On Thu, 2018-02-01 at 12:23 +0200, Lars Wirzenius wrote: > > I disagree, I'm afraid. As a user, the speed in which we do removals > > from testing or unstable shouldn't matter to you. What matters is that > > the software you need

Re: Removing packages perhaps too aggressively?

On Thu, Feb 01, 2018 at 09:42:13PM +0100, Ansgar Burchardt wrote: > peter green writes: > >> If you do reintroduce it, please note the extra steps (reopening bugs > >> in particular) > > On that note one thing that doesn't seem to be easy/well documented is > > how to go about finding the bugs

Accepted libre 0.5.7-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 21:06:38 +0100 Source: libre Binary: libre0 libre-dev Architecture: source amd64 Version: 0.5.7-1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team

Accepted multicat 2.2-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 20:57:31 +0100 Source: multicat Binary: multicat Architecture: source Version: 2.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers

Mass bug filing for the removal of freetype-config and freetype.m4

Hi everyone, I intend to do a mass bug filing against all packages that use freetype-config and/or freetype.m4, as these APIs will be removed from libfreetype6-dev in the next maintainer release. This is a Debian-specific change. Freetype-config has been considered deprecated for several

Re: Removing packages perhaps too aggressively?

peter green writes: >> If you do reintroduce it, please note the extra steps (reopening bugs >> in particular) > On that note one thing that doesn't seem to be easy/well documented is > how to go about finding the bugs that affected a package at the time > of it's removal. If I go to the bugs page

Accepted movit 1.6.1-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 31 Jan 2018 23:02:40 +0100 Source: movit Binary: libmovit-dev libmovit8 Architecture: source amd64 Version: 1.6.1-1 Distribution: unstable Urgency: medium Maintainer: Steinar H. Gunderson Changed-By: Steinar

Accepted brewtarget 2.3.1-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 22:27:04 +0100 Source: brewtarget Binary: brewtarget Architecture: source Version: 2.3.1-3 Distribution: unstable Urgency: medium Maintainer: Dr. Tobias Quathamer Changed-By: Dr. Tobias Quathamer

Accepted dput-ng 1.16 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 22:33:26 +0100 Source: dput-ng Binary: dput-ng python-dput dput-ng-doc Architecture: source Version: 1.16 Distribution: unstable Urgency: medium Maintainer: dput-ng Maintainers

Accepted commons-httpclient 3.1-14 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 21:16:27 +0100 Source: commons-httpclient Binary: libcommons-httpclient-java libcommons-httpclient-java-doc Architecture: source Version: 3.1-14 Distribution: unstable Urgency: medium Maintainer: Debian Java

Accepted ginac 1.7.3-1 (source amd64) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 20:05:15 +0100 Source: ginac Binary: libginac6 libginac-dev ginac-tools Architecture: source amd64 Version: 1.7.3-1 Distribution: experimental Urgency: low Maintainer: Richard Kreckel Changed-By:

Accepted pytest-pylint 0.7.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 23:38:58 +0100 Source: pytest-pylint Binary: python-pytest-pylint python3-pytest-pylint Architecture: source Version: 0.7.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

Re: proposal: ITR (was Re: Removing packages perhaps too aggressively?)

On 02/01/2018 01:12 AM, Adam Borowski wrote: > One issue: on a small screen, crap font and no glasses, "ITR" looks similar > to "ITP", an alternate acronym could be better. > > Meow. Hi, I very much appreciate your intent here, which is for sure, to make Debian nicer and more welcoming.

Re: Removing packages perhaps too aggressively?

On February 1, 2018 8:24:05 PM UTC, Abou Al Montacir wrote: >On Thu, 2018-02-01 at 12:23 +0200, Lars Wirzenius wrote: >> On Thu, 2018-02-01 at 11:10 +0100, Abou Al Montacir wrote: >> > In general I agree with this as a DD, but when I wear my user hat I >don't. >> >> I

Accepted gcl 2.6.12-63 (source amd64 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 18:36:29 + Source: gcl Binary: gcl gcl-doc Architecture: source amd64 all Version: 2.6.12-63 Distribution: unstable Urgency: medium Maintainer: Camm Maguire Changed-By: Camm Maguire

Accepted dgit-test-dummy 1.21 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Feb 2018 20:20:18 + Source: dgit-test-dummy Binary: dgit-test-dummy Architecture: source Version: 1.21 Distribution: experimental Urgency: medium Maintainer: Ian Jackson Changed-By: Ian

Accepted pathspider 2.0.1-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 20:30:43 + Source: pathspider Binary: pathspider Architecture: source amd64 Version: 2.0.1-2 Distribution: unstable Urgency: medium Maintainer: Internet Measurement Packaging Team

Accepted pycurl 7.43.0.1-0.2 (source amd64 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 20:23:45 + Source: pycurl Binary: python-pycurl python3-pycurl python-pycurl-dbg python3-pycurl-dbg python-pycurl-doc Architecture: source amd64 all Version: 7.43.0.1-0.2 Distribution: unstable Urgency: medium

Re: Removing packages perhaps too aggressively?

On Fri, Feb 02, 2018 at 12:00:58AM +0100, Wouter Verhelst wrote: > Currently, RM bugs are filed against ftp.debian.org. > > It might make sense to have them filed against ftp.debian.org *and* the > package to be removed, instead. That way, people who care about the > package are more likely to

Accepted ncurses-hexedit 0.9.7+orig-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Feb 2018 03:51:43 +1100 Source: ncurses-hexedit Binary: ncurses-hexedit Architecture: source Version: 0.9.7+orig-2 Distribution: unstable Urgency: medium Maintainer: Carlos Maddela Changed-By: Carlos

Accepted papirus-icon-theme 20180201-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 18:32:45 +0800 Source: papirus-icon-theme Binary: papirus-icon-theme Architecture: source Version: 20180201-1 Distribution: unstable Urgency: medium Maintainer: Debian Deepin Packaing Team <pkg-deepin

Accepted rex 1.6.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 16:37:50 +0100 Source: rex Binary: rex Architecture: source Version: 1.6.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Alexandre

Accepted winetricks 0.0+20171222-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Feb 2018 00:15:15 +0100 Source: winetricks Binary: winetricks Architecture: source Version: 0.0+20171222-1 Distribution: unstable Urgency: medium Maintainer: Debian Wine Party

Accepted vim 2:8.0.1451-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 19:07:29 -0500 Source: vim Binary: vim-common vim-gui-common vim-runtime vim-doc vim-tiny vim vim-gtk vim-gtk3 vim-nox vim-athena vim-gnome xxd Architecture: source Version: 2:8.0.1451-1 Distribution: unstable

Re: Mass bug filing for the removal of freetype-config and freetype.m4

On Thu, Feb 1, 2018 at 7:07 PM, Hugh McMaster wrote: > This is a Debian-specific change. Will you be asking upstream to remove it too? -- bye, pabs https://wiki.debian.org/PaulWise

Re: What is the point of RFA? Was: Re: proposal: ITR

On Fri, Feb 2, 2018 at 7:23 AM, Jeremy Bicha wrote: > What is the point of RFA? > > I mean why don't you just Orphan it and continue to maintain it with > QA uploads until a volunteer wants to adopt it? I wasn't around when RFA was invented, but: You might want to have choose amongst the

Work-needing packages report for Feb 2, 2018

The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1158 (new: 2) Total number of packages offered up for adoption: 167 (new: 7) Total number of packages

Re: Removing packages perhaps too aggressively?

On Fri, Feb 2, 2018 at 2:26 AM, peter green wrote: > On that note one thing that doesn't seem to be easy/well documented is how > to go about finding the bugs that affected a package at the time of it's > removal. If I go to the bugs page for the package and select "archived and > unarchived" I

Accepted awstats 7.6+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Feb 2018 02:21:35 +0100 Source: awstats Binary: awstats Architecture: source Version: 7.6+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski

Accepted gnome-online-accounts 3.26.2-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Feb 2018 20:29:48 -0500 Source: gnome-online-accounts Binary: gnome-online-accounts libgoa-1.0-0b libgoa-1.0-dev libgoa-backend-1.0-1 libgoa-backend-1.0-dev libgoa-1.0-common libgoa-1.0-doc gir1.2-goa-1.0 Architecture:

  1   2   >