Accepted calibre 3.39.1+dfsg-3 (source amd64 all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 10 May 2019 11:47:37 +0900 Source: calibre Binary: calibre calibre-bin calibre-bin-dbgsym Architecture: source amd64 all Version: 3.39.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Norbert Preining Changed-By:

Re: .deb format: let's use 0.939, zstd, drop bzip2

On Fri, May 10, 2019 at 05:18:18AM +0200, Guillem Jover wrote: > On Wed, 2019-05-08 at 19:38:26 +0200, Adam Borowski wrote: > > First, the 0.939 format, as described in "man deb-old". While still being > > accepted by dpkg, it had been superseded before even the very first stable > > release.

Accepted slt 0.0.git20140301-6 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 17:57:40 -0400 Source: slt Architecture: source Version: 0.0.git20140301-6 Distribution: unstable Urgency: medium Maintainer: Daniel Kahn Gillmor Changed-By: Daniel Kahn Gillmor Changes: slt (0.0.git20140301-6)

Re: .deb format: let's use 0.939, zstd, drop bzip2

> On 10 May 2019, at 10:39, Adam Borowski wrote: > > I understand that this was an issue when prototyping, but have you used ar > to manipulate .deb archives even once this millenium? By now, the deb > format is common, while ar is an obscure implementation detail. I did used ar to unpack

Re: .deb format: let's use 0.939, zstd, drop bzip2

On Wed, May 08, 2019 at 09:53:19PM +0100, Ian Jackson wrote: > (adding debian-dpkg) Probably too late to move the thread :( > Adam Borowski writes (".deb format: let's use 0.939, zstd, drop bzip2"): > > First, the 0.939 format, as described in "man deb-old". While still being > > accepted by

Re: .deb format: let's use 0.939, zstd, drop bzip2

Hi! On Wed, 2019-05-08 at 19:38:26 +0200, Adam Borowski wrote: > First, the 0.939 format, as described in "man deb-old". While still being > accepted by dpkg, it had been superseded before even the very first stable > release. Why? It has at least two upsides over 2.0: I'll try to detangle

Work-needing packages report for May 10, 2019

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: 1413 (new: 14) Total number of packages offered up for adoption: 160 (new: 0) Total number of packages

Accepted profanity 0.6.0+git20190503.4a165b8-2 (source amd64) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 22:17:34 + Source: profanity Binary: profanity profanity-dbgsym Architecture: source amd64 Version: 0.6.0+git20190503.4a165b8-2 Distribution: experimental Urgency: medium Maintainer: Debian XMPP Maintainers

Accepted golang-1.12 1.12.5-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 22:34:40 +0200 Source: golang-1.12 Architecture: source Version: 1.12.5-1 Distribution: unstable Urgency: medium Maintainer: Go Compiler Team Changed-By: Dr. Tobias Quathamer Changes: golang-1.12 (1.12.5-1)

Bug#928731: ITP: ruby-has-secure-token -- provides an easy way to generate uniques random tokens for any model in ruby on rails

Package: wnpp Severity: wishlist Owner: Manas Kashyap X-Debbugs-CC: debian-devel@lists.debian.org, debian-r...@lists.debian.org * Package name: ruby-has-secure-token Version : 1.0.0 Upstream Author : Roberto Miranda * URL :

Accepted pdal 1.9.1+ds-1~exp1 (source amd64 all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 20:41:54 +0200 Source: pdal Binary: libpdal-base8 libpdal-base8-dbgsym libpdal-dev libpdal-plugin-faux libpdal-plugin-faux-dbgsym libpdal-plugin-greyhound libpdal-plugin-greyhound-dbgsym libpdal-plugin-icebridge

Accepted gdal 3.0.0+dfsg-1~exp2 (source amd64 all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 20:17:25 +0200 Source: gdal Binary: gdal-bin gdal-bin-dbgsym gdal-data libgdal-dev libgdal-doc libgdal-java libgdal-java-dbgsym libgdal-perl libgdal-perl-dbgsym libgdal-perl-doc libgdal26 libgdal26-dbgsym

Accepted ogdi-dfsg 4.1.0+ds-1~exp1 (source amd64) into experimental, experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Apr 2019 14:09:37 +0200 Source: ogdi-dfsg Binary: libogdi-dev libogdi4.1 libogdi4.1-dbgsym ogdi-bin ogdi-bin-dbgsym Architecture: source amd64 Version: 4.1.0+ds-1~exp1 Distribution: experimental Urgency: medium Maintainer:

Accepted libctl 4.3.0-1 (source amd64 all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 08 May 2019 18:06:46 +0200 Source: libctl Binary: libctl-dev libctl-doc libctl7 libctl7-dbgsym Architecture: source amd64 all Version: 4.3.0-1 Distribution: experimental Urgency: medium Maintainer: Thorsten Alteholz

Accepted sa-exim 4.2.1-17 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 08 May 2019 23:11:16 +0200 Source: sa-exim Binary: sa-exim sa-exim-dbgsym Architecture: source amd64 Version: 4.2.1-17 Distribution: unstable Urgency: medium Maintainer: Magnus Holmgren Changed-By: Magnus Holmgren

Bug#928724: ITP: opensbi -- RISC-V Open Source Supervisor Binary Interface

Package: wnpp Severity: wishlist Owner: Vagrant Cascadian X-Debbugs-Cc: debian-devel@lists.debian.org, mer...@debian.org, debian-ri...@lists.debian.org * Package name: opensbi Version : 0.3+ Upstream Author : Anup Patel/Western Digital, other contributors * URL :

Re: .deb format: let's use 0.939, zstd, drop bzip2

Hi, On Thu, 9 May 2019, 15:57 Ian Jackson, wrote: > Ansgar writes ("Re: .deb format: let's use 0.939, zstd, drop bzip2"): > > `ar` needs to be replaced for the file size limitation mentioned in the > > initial mail: ar represents file size as a 10 digit decimal number[1] > > which limits the

Accepted libqtxdg 3.3.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 17:57:01 +0200 Source: libqtxdg Architecture: source Version: 3.3.1-2 Distribution: unstable Urgency: medium Maintainer: LXQt Packaging Team Changed-By: Alf Gaida Closes: 928721 Changes: libqtxdg (3.3.1-2)

Accepted devscripts 2.19.5 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 17:01:29 +0200 Source: devscripts Architecture: source Version: 2.19.5 Distribution: unstable Urgency: medium Maintainer: Devscripts Maintainers Changed-By: Mattia Rizzolo Closes: 927350 927367 927373 927864

Accepted groonga 9.0.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 23:34:20 +0900 Source: groonga Architecture: source Version: 9.0.1-2 Distribution: unstable Urgency: medium Maintainer: Groonga Project Changed-By: Kentaro Hayashi Closes: 928304 Changes: groonga (9.0.1-2)

Accepted fonts-fanwood 1.1-6 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 12:49:45 +0200 Source: fonts-fanwood Architecture: source Version: 1.1-6 Distribution: experimental Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Gürkan Myczko Closes: 927580 Changes:

Accepted fonts-f500 1.0-9 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 12:56:38 +0200 Source: fonts-f500 Architecture: source Version: 1.0-9 Distribution: experimental Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Gürkan Myczko Closes: 927583 Changes: fonts-f500

Re: Preferred git branch structure when upstream moves from tarballs to git [and 1 more messages]

Holger Levsen writes ("Re: Preferred git branch structure when upstream moves from tarballs to git [and 1 more messages]"): > On Thu, May 09, 2019 at 01:46:19PM +0100, Ian Jackson wrote: > > debcheckout *certainly* doesn't do this. It just gives you the > > current master which may not have been

Re: Preferred git branch structure when upstream moves from tarballs to git [and 1 more messages]

On Thu, 2019-05-09 at 12:51 +, Holger Levsen wrote: > On Thu, May 09, 2019 at 01:46:19PM +0100, Ian Jackson wrote: > > debcheckout *certainly* doesn't do this. It just gives you the > > current master which may not have been uploaded anywhere. > > nope: > > $ debcheckout munin > declared

Re: .deb format: let's use 0.939, zstd, drop bzip2

Ansgar writes ("Re: .deb format: let's use 0.939, zstd, drop bzip2"): > `ar` needs to be replaced for the file size limitation mentioned in the > initial mail: ar represents file size as a 10 digit decimal number[1] > which limits the members (control.tar.*, data.tar.*) to ~10G. ... > Replacing

Re: Preferred git branch structure when upstream moves from tarballs to git [and 1 more messages]

On Thu, May 09, 2019 at 01:46:19PM +0100, Ian Jackson wrote: > debcheckout *certainly* doesn't do this. It just gives you the > current master which may not have been uploaded anywhere. nope: $ debcheckout munin declared git repository at https://salsa.debian.org/debian/munin.git -b debian git

Re: Preferred git branch structure when upstream moves from tarballs to git [and 1 more messages]

Holger Levsen writes ("Re: Preferred git branch structure when upstream moves from tarballs to git [and 1 more messages]"): > On Wed, May 08, 2019 at 04:14:00PM +0100, Ian Jackson wrote: > > * Debian should provide source code as git branches which: > - can be built using a standard set

Re: .deb format: let's use 0.939, zstd, drop bzip2

On Thu, 2019-05-09 at 12:32 +, Jeremy Stanley wrote: > On 2019-05-09 06:27:36 +0900 (+0900), Mike Hommey wrote: > > On Wed, May 08, 2019 at 09:04:49PM +, Jeremy Stanley wrote: > [...] > > > Are you talking about source packages or binary packages here? > > > The > > > latter use ar, not

Accepted gdal 3.0.0+dfsg-1~exp1 (source amd64 all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 May 2019 13:30:40 +0200 Source: gdal Binary: gdal-bin gdal-bin-dbgsym gdal-data libgdal-dev libgdal-doc libgdal-java libgdal-java-dbgsym libgdal-perl libgdal-perl-dbgsym libgdal-perl-doc libgdal26 libgdal26-dbgsym

Re: .deb format: let's use 0.939, zstd, drop bzip2

On 2019-05-09 06:27:36 +0900 (+0900), Mike Hommey wrote: > On Wed, May 08, 2019 at 09:04:49PM +, Jeremy Stanley wrote: [...] > > Are you talking about source packages or binary packages here? The > > latter use ar, not tar. > > Binary packages use both. > > $ ar t

Re: Preferred git branch structure when upstream moves from tarballs to git

(adding #903392) Ben Finney writes ("Re: Preferred git branch structure when upstream moves from tarballs to git"): > What I remain unconvinced of is the worth of abandoning the clean > separation between an upstream source repository (whether Git repository > or not) and a VCS repository for

Re: Preferred git branch structure when upstream moves from tarballs to git

Ansgar writes ("Re: Preferred git branch structure when upstream moves from tarballs to git"): > On Thu, 2019-05-09 at 10:33 +0100, Ian Campbell wrote: > > I think there's a common misconception here which has cropped up > > several times in this thread. (NB: I've not used dgit in anger yet, but

Re: .deb format: let's use 0.939, zstd, drop bzip2

On Thu, May 09, 2019 at 09:22:56AM +0200, Ansgar wrote: > Also dpkg keeps metadata in /var, but changelogs, NEWS, copyright > documentation isn't variable state data and should be below /usr... The > same is really true for lists of files and maintainer scripts though. It's a mess: * Most of

Accepted poedit 2.2.1-2exp3 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 13:15:02 +0200 Source: poedit Binary: poedit poedit-common Architecture: source Version: 2.2.1-2exp3 Distribution: experimental Urgency: medium Maintainer: Debian l10n developers Changed-By: Gianfranco Costamagna

Accepted cpprest 2.10.13-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 13:17:01 +0200 Source: cpprest Binary: libcpprest2.10 libcpprest-dev libcpprest-doc Architecture: source Version: 2.10.13-2 Distribution: unstable Urgency: medium Maintainer: Gianfranco Costamagna Changed-By:

Re: .deb format: let's use 0.939, zstd, drop bzip2

On Thu, May 09, 2019 at 08:10:00AM +, Anthony DeRobertis wrote: > On May 8, 2019 9:43:50 PM UTC, Adam Borowski wrote: > > >I just checked Stretch: not a single .bz2, either control nor data. I'm > >not going to download all of Jessie just to check -- but even assuming > >something was left

Re: Preferred git branch structure when upstream moves from tarballs to git

On Thu, 2019-05-09 at 10:33 +0100, Ian Campbell wrote: > On Thu, 2019-05-09 at 11:19 +1000, Ben Finney wrote: > > What I remain unconvinced of is the worth of abandoning the clean > > separation between an upstream source repository (whether Git repository > > or not) and a VCS repository for

Re: Preferred git branch structure when upstream moves from tarballs to git [and 1 more messages]

On Wed, May 08, 2019 at 03:26:32PM +, Holger Levsen wrote: > thanks for the pointer, but I don't see the string debcheckout in that > message and vcs-git only once, where you write: > > ---begin quote--- > > >From these we can conclude: > > * Debian should provide source code as git

Accepted needrestart 3.4-4 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 11:18:46 +0200 Source: needrestart Binary: needrestart Architecture: source all Version: 3.4-4 Distribution: unstable Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description:

Accepted mlt 6.16.0-1 (source amd64 all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 11:05:03 +0200 Source: mlt Binary: libmlt++-dev libmlt++3 libmlt++3-dbgsym libmlt-data libmlt-dev libmlt6 libmlt6-dbgsym melt melt-dbgsym python-mlt python-mlt-dbgsym Architecture: source amd64 all Version:

Re: Preferred git branch structure when upstream moves from tarballs to git

On Thu, 2019-05-09 at 11:19 +1000, Ben Finney wrote: > What I remain unconvinced of is the worth of abandoning the clean > separation between an upstream source repository (whether Git repository > or not) and a VCS repository for Debian packaging (typically in Git). I think there's a common

Accepted movim 0.14.1-5 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 08 May 2019 22:38:32 +0200 Source: movim Binary: movim Architecture: source all Version: 0.14.1-5 Distribution: unstable Urgency: medium Maintainer: Debian XMPP Maintainers Changed-By: Dominik George Description: movim

Accepted py-macaroon-bakery 1.2.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 09:54:14 +0100 Source: py-macaroon-bakery Architecture: source Version: 1.2.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Colin Watson Changes: py-macaroon-bakery

Accepted postgresql-common 201 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 May 2019 10:02:05 +0200 Source: postgresql-common Architecture: source Version: 201 Distribution: experimental Urgency: medium Maintainer: Debian PostgreSQL Maintainers Changed-By: Christoph Berg Changes:

Accepted postgresql-11 11.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 07 May 2019 12:04:34 +0200 Source: postgresql-11 Architecture: source Version: 11.3-1 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers Changed-By: Christoph Berg Changes: postgresql-11

Re: .deb format: let's use 0.939, zstd, drop bzip2

On May 8, 2019 9:43:50 PM UTC, Adam Borowski wrote: >I just checked Stretch: not a single .bz2, either control nor data. >I'm not >going to download all of Jessie just to check -- but even assuming >something >was left by Jessie's time, by Bullseye trying to install such a .deb >will >mean

Bug#928699: ITP: HelioPy -- Python for heliospheric and planetary physics

Package: heliopy Owner: Shreyas Bapat Severity: wishlist X-Debbugs-Cc: debian-devel@lists.debian.org,debian-as...@lists.debian.org, debian-pyt...@lists.debian.org * Package name: heliopy Version: 0.6.7 Upstream Author : David Stansby * URL

Re: .deb format: let's use 0.939, zstd, drop bzip2

On Wed, May 08, 2019 at 09:01:27PM -0400, Michael Stone wrote: > On Thu, May 09, 2019 at 07:37:55AM +0800, Paul Wise wrote: > > On Thu, May 9, 2019 at 1:38 AM Adam Borowski wrote: > > > > > Thus, even though we'd want to stick with xz for the official archive, > > > speed > > > gains from zstd

Re: .deb format: let's use 0.939, zstd, drop bzip2

Adam Borowski writes: > On Wed, May 08, 2019 at 10:35:58PM +0200, Ansgar wrote: >> Adam Borowski writes: >> > I've recently did some research on how can we improve the speed of >> > unpacking >> > packages. There's a lot of other stages that can be improved, but let's >> > talk about the .deb

Accepted phpunit-environment 4.2.2-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 08 May 2019 20:50:17 -1000 Source: phpunit-environment Architecture: source Version: 4.2.2-1 Distribution: experimental Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: David Prévot Changes:

Re: .deb format: let's use 0.939, zstd, drop bzip2

On Thu, May 09, 2019 at 12:02:26AM +0200, Adam Borowski wrote: > > We have various applications that only want to extract single members of > > the package (changelog, NEWS, copyright, ...); tar is a really bad > > format for such an operation. Other formats (zip, 7z, ...) are more > > suited for