Accepted netcdf4-python 1.5.1.1-1~exp1 (source amd64) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 May 2019 06:15:44 +0200 Source: netcdf4-python Binary: python-netcdf4 python-netcdf4-dbgsym python3-netcdf4 python3-netcdf4-dbgsym Architecture: source amd64 Version: 1.5.1.1-1~exp1 Distribution: experimental Urgency:

Bug#928372: ITP: golang-github-anacrolix-dms-dev -- a UPnP DLNA Digital Media Server that includes basic video transcoding

Package: wnpp Severity: wishlist Owner: Drew Parsons * Package name: golang-github-anacrolix-dms-dev Version : 1.0.0 Upstream Author : Matt Joiner * URL : https://github.com/anacrolix/dms * License : BSD Programming Lang: Go Description : a UPnP DLNA

Accepted python-meshio 2.3.7-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2019 23:32:32 +0800 Source: python-meshio Architecture: source Version: 2.3.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Changes: python-meshio (2.3.7-2)

Work-needing packages report for May 3, 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: 1400 (new: 0) Total number of packages offered up for adoption: 162 (new: 1) Total number of packages

Accepted vmemcache 0.8-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 17:31:06 +0200 Source: vmemcache Architecture: source Version: 0.8-3 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Adam Borowski Changes: vmemcache (0.8-3) unstable; urgency=medium

Accepted alttab 1.4.0-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 1 May 2019 20:47:47 +0300 Source: alttab Architecture: source Version: 1.4.0-1 Distribution: experimental Urgency: medium Maintainer: Alexander Kulak Changed-By: Alexander Kulak Changes: alttab (1.4.0-1) experimental;

Accepted atftp 0.7.git20120829-3.1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 29 Apr 2019 19:37:52 +0200 Source: atftp Architecture: source Version: 0.7.git20120829-3.1 Distribution: unstable Urgency: high Maintainer: Ludovic Drolez Changed-By: Salvatore Bonaccorso Closes: 927553 Changes: atftp

Accepted dnsrecon 0.9.1-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 01 May 2019 00:35:48 +0200 Source: dnsrecon Binary: dnsrecon Architecture: source all Version: 0.9.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Marcos Fouces Description: dnsrecon

Accepted hcloud-cli 1.12.0-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 19:49:38 +0200 Source: hcloud-cli Binary: hcloud-cli Architecture: source amd64 Version: 1.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Thorsten Alteholz

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

Ben Hutchings writes ("Re: Preferred git branch structure when upstream moves from tarballs to git"): > On Thu, 2019-05-02 at 11:23 +0100, Ian Jackson wrote: > > Sorry for shouting, but, really. It is kind of frustrating to have > > designed and implemented and deployed a complex piece of

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

Ansgar writes: > On Thu, 2019-05-02 at 09:15 -0700, Russ Allbery wrote: >> I'm confused. I'm a happy user of dgit and don't have to think about >> any of those things as part of using dgit. I choose to use branches, >> but I certainly wouldn't have to, and merging, multiple remotes, and so >>

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

On Thu, 2019-05-02 at 09:15 -0700, Russ Allbery wrote: > Ansgar writes: > > > Having to know about branches, merging, dealing with multiple remotes, > > ... *is* an entry barrier compared to not having to know about it. Now > > you have to teach people that before you even get to how to write a

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

Ansgar writes: > Having to know about branches, merging, dealing with multiple remotes, > ... *is* an entry barrier compared to not having to know about it. Now > you have to teach people that before you even get to how to write a > build recipe. I'm confused. I'm a happy user of dgit and

Accepted python-meshio 2.3.7-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2019 23:08:06 +0800 Source: python-meshio Architecture: source Version: 2.3.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Changes: python-meshio (2.3.7-1)

Accepted libhtp 1:0.5.30-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 16:38:21 +0200 Source: libhtp Architecture: source Version: 1:0.5.30-1 Distribution: unstable Urgency: medium Maintainer: Arturo Borrero Gonzalez Changed-By: Sascha Steinbiss Changes: libhtp (1:0.5.30-1)

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

On Thu, 2019-05-02 at 11:23 +0100, Ian Jackson wrote: [...] > Sorry for shouting, but, really. It is kind of frustrating to have > designed and implemented and deployed a complex piece of software > which solves a lot of problems, and constantly hear people > - proposing solutions which do not

Bug#928341: ITP: golang-github-renekroon-ttlcache -- An in-memory string-interface{} map with various expiration options for golang

Package: wnpp Severity: wishlist Owner: Sascha Steinbiss * Package name: golang-github-renekroon-ttlcache Version : 1.4.0+git20190429.e7780e9-1 Upstream Author : Rene Kroon * URL : https://github.com/ReneKroon/ttlcache * License : MIT Programming Lang: Go

UPC-Chello

debian-devel@lists.debian.org Bitte wechseln Sie zu den neuen Maileinstellungen, indem Sie das IT-Portal unten nutzen und sich auf Ihrem Konto anmelden, um innerhalb von vierundzwanzig Stunden eine Serviceinterstellung zu vermeiden.

Accepted suricata-update 1.0.5-1 (source amd64) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 11:34:15 +0200 Source: suricata-update Binary: suricata-update Architecture: source amd64 Version: 1.0.5-1 Distribution: experimental Urgency: medium Maintainer: Sascha Steinbiss Changed-By: Sascha Steinbiss

Accepted salt 2018.3.4+dfsg1-5 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 13:23:44 +0200 Source: salt Architecture: source Version: 2018.3.4+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: Debian Salt Team Changed-By: Benjamin Drung Closes: 928337 Changes: salt

Accepted cross-toolchain-base-mipsen 4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2019 14:51:40 +0200 Source: cross-toolchain-base-mipsen Architecture: source Version: 4 Distribution: unstable Urgency: medium Maintainer: Cross Toolchain Base Team Changed-By: Matthias Klose Changes:

Accepted plastimatch 1.8.0+dfsg.1-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 30 Apr 2019 16:59:46 -0400 Source: plastimatch Binary: plastimatch plastimatch-dbgsym Architecture: source amd64 Version: 1.8.0+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team

Accepted cross-toolchain-base 35 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2019 14:31:48 +0200 Source: cross-toolchain-base Architecture: source Version: 35 Distribution: unstable Urgency: medium Maintainer: Cross Toolchain Base Team Changed-By: Matthias Klose Changes: cross-toolchain-base

Accepted cross-toolchain-base-ports 29 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2019 14:49:13 +0200 Source: cross-toolchain-base-ports Architecture: source Version: 29 Distribution: unstable Urgency: medium Maintainer: Cross Toolchain Base Team Changed-By: Matthias Klose Changes:

Accepted certmonger 0.79.6-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 15:41:32 +0300 Source: certmonger Architecture: source Version: 0.79.6-2 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team Changed-By: Timo Aaltonen Closes: 852691 Changes: certmonger

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

On Thu, 2019-05-02 at 13:45 +0100, Ian Jackson wrote: > Ansgar Burchardt writes ("Re: Preferred git branch structure when > upstream moves from tarballs to git"): > > On Tue, 2019-04-30 at 16:00 -0700, Sean Whitton wrote: > > > As a package maintainer, if you don't keep the whole source package in

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

Ansgar Burchardt writes ("Re: Preferred git branch structure when upstream moves from tarballs to git"): > On Tue, 2019-04-30 at 16:00 -0700, Sean Whitton wrote: > > As a package maintainer, if you don't keep the whole source package in > > git, you're giving up on a lot of the power of git. > >

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

On Tue, 2019-04-30 at 16:00 -0700, Sean Whitton wrote: > > On Tue 30 Apr 2019 at 08:05AM +02, Ansgar wrote: > > > As an example: to update to a new upstream release, I ideally just have > > to drop the new upstream tarball, update d/changelog and am done. > > Compare with [1] which is much more

Accepted lemonldap-ng 2.0.2+ds-7 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 08:54:06 +0200 Source: lemonldap-ng Architecture: source Version: 2.0.2+ds-7 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Xavier Guimard Changes: lemonldap-ng (2.0.2+ds-7)

Accepted mhc 1.2.1-2 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2019 20:17:00 +0900 Source: mhc Binary: mhc mhc-utils Architecture: source all Version: 1.2.1-2 Distribution: unstable Urgency: medium Maintainer: Tatsuya Kinoshita Changed-By: Tatsuya Kinoshita Description: mhc

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

My initial question resulted in a lot of useful advice and opinions, and spurred quite an interesting discussion. Thanks to everyone who contributed, and apologies for not contributing myself.

Accepted sqlmap 1.3.5-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2019 12:53:13 +0200 Source: sqlmap Binary: sqlmap Architecture: source Version: 1.3.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Gianfranco Costamagna Description: sqlmap

Accepted buku 4.2.2+ds-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 18:13:59 +0800 Source: buku Binary: buku Architecture: source all Version: 4.2.2+ds-1 Distribution: unstable Urgency: medium Maintainer: SZ Lin (林上智) Changed-By: SZ Lin (林上智) Description: buku - Powerful

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

Philipp Kern writes ("Re: Preferred git branch structure when upstream moves from tarballs to git"): > On 5/2/2019 7:11 AM, Ben Finney wrote: > > Conversely, I think it does a disservice to downstream users to mix in > > Debian packaging changes with upstream changes. The separation is useful > >

Accepted ipset 6.38-1.1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 25 Apr 2019 11:37:45 +0200 Source: ipset Binary: ipset ipset-dbgsym libipset-dev libipset11 libipset11-dbgsym Architecture: source amd64 Version: 6.38-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter

Accepted policy-rcd-declarative 0.2 (source all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 11:31:23 +0200 Source: policy-rcd-declarative Binary: policy-rcd-declarative Architecture: source all Version: 0.2 Distribution: experimental Urgency: medium Maintainer: Wouter Verhelst Changed-By: Wouter Verhelst

Accepted bro-pkg 1.7.1-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 11:10:05 +0200 Source: bro-pkg Binary: bro-pkg Architecture: source all Version: 1.7.1-1 Distribution: unstable Urgency: medium Maintainer: Robert Haist Changed-By: Robert Haist Description: bro-pkg- Bro

Accepted pushpin 1.21.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 10:55:08 +0200 Source: pushpin Architecture: source Version: 1.21.0-1 Distribution: unstable Urgency: medium Maintainer: Jan Niehusmann Changed-By: Jan Niehusmann Changes: pushpin (1.21.0-1) unstable;

Accepted network-console 1.81 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2019 08:24:07 + Source: network-console Architecture: source Version: 1.81 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Closes: 926947 927516 928299

Accepted puppet-module-puppetlabs-mysql 8.1.0-1 (source all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Apr 2019 11:05:28 +0200 Source: puppet-module-puppetlabs-mysql Binary: puppet-module-puppetlabs-mysql Architecture: source all Version: 8.1.0-1 Distribution: experimental Urgency: medium Maintainer: Puppet Package

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

On 5/2/2019 7:11 AM, Ben Finney wrote: > Conversely, I think it does a disservice to downstream users to mix in > Debian packaging changes with upstream changes. The separation is useful > and much easier to maintain when the repositories are separate. To be honest the greatest disservice is that