Accepted obnam 1.20.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 30 Oct 2016 10:46:18 +0200 Source: obnam Binary: obnam Architecture: source Version: 1.20.2-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l...@liw.fi>

Accepted obnam 1.20-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Oct 2016 12:25:37 +0300 Source: obnam Binary: obnam Architecture: source Version: 1.20-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l...@liw.fi>

Re: Is missing SysV-init support a bug?

On Tue, Oct 18, 2016 at 07:34:28PM +0200, Xen wrote: > If that is the case then they have enbedded hostility into their name simply > becaus eit offends normal grammar roles. I don't that's it at all. The reason many people react to the SystemD spelling is becuase, for some years now, trolls use

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 06:03:28PM +0200, Jakub Wilk wrote: > The WTFness of this code is certainly way above what we're normally used to, > but (AIUI) it's only used as a fallback for nodejs < 4. Debian currently has > 4.6.0. In that case, perhaps this package isn't needed in Debian at all? > >

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 08:40:49PM +0530, Pirate Praveen wrote: > I don't particularly enjoy doing this either. Please direct your anger > at the nodejs developers. I'm doing this only because the packages I > care (diaspora and gitlab won't be accepted in main, unless I build > libjs-handlebars

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 08:59:20PM +0530, Pirate Praveen wrote: > On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: > > This is so wrong, I would like to ask that this package not be allowed > > into Debian until it's fixed. > > I agree this could be marked RC a

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 08:49:27PM +0530, Pirate Praveen wrote: > On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: > > This is so wrong, I would like to ask that this package not be allowed > > into Debian until it's fixed. > > This is already reported upstream

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 03:27:46PM +0100, Steve McIntyre wrote: > The code, well... > > if (process.platform === 'linux') { > return home || (process.getuid() === 0 ? '/root' : (user ? > '/home/' + user : null)); > } > > Things are more complicated than that. What

Re: Package name conflict question

On Tue, Oct 18, 2016 at 03:36:56PM +0800, SZ Lin (林上智) wrote: > Although these packages are not API-compatible, they are using the > same installation path and file name; therefore, I think "Conflict:" > section is needed. The problem with this is that this prevents our users from having both of

Re: non-Debian software on ftp*.*.debian.org mirrors

On Mon, Oct 17, 2016 at 12:55:39PM +, Ivan Shmakov wrote: > I'd say that those who can discern Debian non-free from Debian > proper are at low risk of confusing, say, [1] with the "software > [...] endorsed or even produced by Debian." http://ftp.se.debian.org/ and

Accepted mysql-5.7 5.7.15-1 (source amd64 all) into unstable

mysql-testsuite-5.7 mysql-source-5.7 Architecture: source amd64 all Version: 5.7.15-1 Distribution: unstable Urgency: medium Maintainer: Robie Basak <robie.ba...@ubuntu.com> Changed-By: Lars Tangvald <lars.tangv...@oracle.com> Description: libmysqlclient-dev - MySQL database devel

Re: non-Debian software on ftp*.*.debian.org mirrors

On Sun, Oct 16, 2016 at 11:50:46AM +, Ivan Shmakov wrote: > Doesn’t the presence of the ‘non-free’ section in the official > Debian Release (InRelease) files /already/ mislead inexperienced > people into thinking that such software is either part of Debian > or endorsed

Re: problem with libc6 / iconv

On Sun, Oct 09, 2016 at 01:49:14AM +0200, Jérémy Lal wrote: > node-iconv used to be able to translit utf-8 chars (ça va) to ascii (ca va) > using setlocale("C.UTF-8") trick. > > However, several libc6 version ago, that behavior changed, to the point > node-iconv fails its tests now. > > I've

Accepted cmdtest 0.27-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 21 Sep 2016 10:32:41 +0300 Source: cmdtest Binary: cmdtest Architecture: source Version: 0.27-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Re: Bug#837606: general: system freeze

On Wed, Sep 14, 2016 at 11:23:56AM +0200, Abou Al Montacir wrote: > Because you think people will not be frustrated if they experience a bug and > that we prevent them to raise bugs? Hiding reality is always bad?. Look at the > original reporter last message. He seems quite disappointed by the

Accepted vmdebootstrap 1.7-1 (source) into unstable

org> Changed-By: Lars Wirzenius <l...@liw.fi> Description: vmdebootstrap - Bootstrap Debian into a (virtual machine) disk image Changes: vmdebootstrap (1.7-1) unstable; urgency=medium . * New maintainer: Lars Wirzenius replaces Neil Williams. Checksums-Sha1: 20f6b1daff5ce4a6047ccefaf6a1

Re: Uploading existing source but with different size

On Fri, Sep 09, 2016 at 01:08:08PM +0100, Marcin Kulisz wrote: > Unfortunately there is difference in size for *.orig.tar.gz between what's in > the archive and what's updated package produces thus upload fails. > > I'm not sure why this difference occurs (it's 27 bytes). > > Any ideas how can I

Re: Upcoming change to perl: current directory in @INC

On Thu, Sep 08, 2016 at 11:55:26AM +0100, Dimitri John Ledkov wrote: > On 29 August 2016 at 14:39, Dominic Hargreaves wrote: > > tl;dr: '.' is being removed from perl's @INC by default; some breakage > > in apps expected. > > > > For some years[1], it's been known that perl's habit

Re: Network access during build

On Thu, Sep 08, 2016 at 09:42:57AM +0200, Emmanuel Bourg wrote: > That makes sense, but in this case what is the usefulness of the > Standards-Version field? And more precisely, why is it considered an > error [1] to omit it? As far as I care, the only point of the field is to document which

Re: Network access during build

On Wed, Sep 07, 2016 at 09:29:53AM +0200, Emmanuel Bourg wrote: > This rule appeared in the version 3.9.7 of the policy. Just declare in > debian/control that your package conforms to the version 3.9.6 and the > issue will no longer be a RC policy violation ;) That's not how policy compliance

Re: Network access during build

On Wed, Sep 07, 2016 at 07:17:20AM +0200, Vincent Bernat wrote: > The fix is easy: just disable the test. > > However, I have a hard time to find this useful for anyone. To sum up: As a counterpoint, it's useful to prevent others from wondering why the build attempts to access the network. In

Re: Common location for face files

On Wed, Aug 31, 2016 at 11:43:43AM +0200, Martin Bammer wrote: > Hi, > > why are the face files located in user's home? In case of encrypted home > directories the login managers cannot access them and the user management > programs of the different DEs need to create an extra copy of the face

Re: Is missing SysV-init support a bug?

On Fri, Aug 26, 2016 at 10:59:48AM +0200, Carsten Leonhardt wrote: > Robert Edmonds writes: > > > I would guess that the vast majority of folks still using sysvinit with > > Debian are running wheezy or older, and thus removing sysvinit scripts > > from packages in unstable

Re: ifupdown2: debconf followup

On Mon, Aug 01, 2016 at 09:01:20PM +0200, Marco d'Itri wrote: > On Aug 01, Lars Wirzenius <l...@liw.fi> wrote: > > > > Sorry, what I actually meant was "every non-toy Debian system". > > we get that you have strong preferences. However, could you please

Re: ifupdown2: debconf followup

On Mon, Aug 01, 2016 at 12:42:39PM +0200, Marco d'Itri wrote: > Sorry, what I actually meant was "every non-toy Debian system". Marco, we get that you have strong preferences. However, could you please avoid inflammatory language when talking about anything that isn't according to your

Accepted python-cliapp 1.20160724-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 24 Jul 2016 21:50:40 +0300 Source: python-cliapp Binary: python-cliapp Architecture: source Version: 1.20160724-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzen

Accepted cmdtest 0.26-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 23 Jul 2016 19:22:01 +0300 Source: cmdtest Binary: cmdtest Architecture: source Version: 0.26-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted cmdtest 0.25-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Jul 2016 21:20:57 +0300 Source: cmdtest Binary: cmdtest Architecture: source Version: 0.25-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Re: Bug#830983: ITP: field -- extracts a list of fields from a file

On Wed, Jul 13, 2016 at 01:08:25PM -0500, Matt Zagrabelny wrote: > Perhaps moreutils? > > The utilities provided therein are (partially) written in perl. So it > is out of place in that regards - but certainly not a show stopping > road block. > > Joey Hess is the maintainer according to: > >

Re: synaptics vs libinput and GNOME 3.20 no longer supporting synaptics

On Tue, Jul 12, 2016 at 03:52:56PM +1000, Russell Stuart wrote: > Maybe libinput does the typing detection syndaemon does, but I can't > find any evidence for it. I remember trying the typing detection some years ago. It didn't help me much, since the order of events, for me, tend to be that the

Re: synaptics vs libinput and GNOME 3.20 no longer supporting synaptics

On Tue, Jul 12, 2016 at 02:45:49PM +0900, Mike Hommey wrote: > It's just probably that your config didn't have palm detection enabled > with the synaptics driver. `synclient | grep PalmDetect` would tell you. I've been using the following script, with variations on the parameters to find a

Re: synaptics vs libinput and GNOME 3.20 no longer supporting synaptics

On Tue, Jul 12, 2016 at 09:36:16AM +1000, Russell Stuart wrote: > Briefly: synaptics is much better touchpad driver than libinput. For me, the opposite is true. After Raphael's mail yesterday, I switched from the synaptics driver to the xinput one (by removing xserver-xort-input-synaptics) and

Re: opinions of snappy packages

On Thu, Jun 30, 2016 at 10:11:23PM -0700, Steve Langasek wrote: > The point has been made that there are lots of other clients in Debian main > that only talk to a single, proprietary server implementation; so if snapd > did only talk to the Canonical store, I believe its placement in main would >

Re: Keysigning via Video Conferencing

On Thu, Jun 23, 2016 at 12:52:35PM -0700, Nikolaus Rath wrote: > On Jun 23 2016, Lars Wirzenius <l...@liw.fi> wrote: > > On Thu, Jun 23, 2016 at 09:23:07AM -0700, Nikolaus Rath wrote: > >> As I said in my other email, I am wondering if the extra burden is worth &

Re: Keysigning via Video Conferencing

On Thu, Jun 23, 2016 at 09:23:07AM -0700, Nikolaus Rath wrote: > As I said in my other email, I am wondering if the extra burden is worth > the gain in security. Is there an extra burden? Seems to me that it'd happen naturally if you contribute to Debian and as part of that interact with other

Re: opinions of snappy packages

On Wed, Jun 22, 2016 at 06:58:25PM +0200, Zlatan Todoric wrote: > With mps-youtube going to contrib, all web browsers should also go > to contrib as they can access Youtube and so on. That's not my opinion. There is plenty of free software to run on the server side to serve content to web

Re: opinions of snappy packages

On Wed, Jun 22, 2016 at 05:29:12PM +0100, Iain Lane wrote: > I don't understand this. What about Twitter clients[0], YouTube > clients[1], Flickr clients[2], and probably clients for many other > non-free web services?[3] If a piece of free software requires, for its essential function, some

Re: Keysigning via Video Conferencing

On Wed, Jun 22, 2016 at 07:58:43AM -0700, Nikolaus Rath wrote: > On Jun 21 2016, Gunnar Wolf wrote: > > Now, I have said this too many times, but once more: As keyring-maint, > > we are not collecting samples of people showing valid-looking ID > > documents to others. This is

Re: opinions of snappy packages

On Sun, Jun 19, 2016 at 03:44:54PM -0700, Steve Langasek wrote: > snapd is available in Debian unstable for roughly the past two weeks. Disclaimer: I've never used snap packages, and I haven't even read their documentation. https://packages.debian.org/sid/snapd indicates the package is in the

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Sat, Jun 11, 2016 at 08:46:30AM +, Holger Levsen wrote: > On Sat, Jun 11, 2016 at 10:24:48AM +0200, Ole Streicher wrote: > > We do patching as part of our daily packaging already: to replace (or > > circumvent) non-dfsg functionality, to integrate into our environment, > > and everything

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, Jun 08, 2016 at 10:41:33PM +0100, Ben Hutchings wrote: > I don't see what's so unreasonable about that. They're asking you to > provide the same licence for your contributions, as the licence for the > existing Gitlab software.  Every FOSS project expects that, even if > they don't make

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, Jun 08, 2016 at 09:47:56AM +0200, Alexander Wirt wrote: > I am also not very keen on using a system with a "open core / enterprise" > model. For such a crucial service I would really prefer a real open source > system. But maybe I am alone with that oppinion. You're not alone. The open

Re: Dropping upstart jobs (or not)

On Sat, Jun 04, 2016 at 09:49:10AM +0200, Marco d'Itri wrote: > On Jun 04, Marc Haber wrote: > > > Another piece of diversity lost in the open source world. > http://www.islinuxaboutchoice.com/ > > > systemd is winning the war. > You are wrong: this war was won

Re: Vcs-* and shared repos

On Wed, May 25, 2016 at 10:09:47PM +0200, Stefano Zacchiroli wrote: > By also considering the fact that the "-d DIR" solution does not prevent > to add a "-l" in the future, I think minimality wins here (hence my > "Yay" to your proposal in separate mail). YMMV. My only concern here is the

Accepted cmdtest 0.24-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Apr 2016 22:03:18 +0300 Source: cmdtest Binary: cmdtest Architecture: source Version: 0.24-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted python-cliapp 1.20160316-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Mar 2016 19:27:16 +0200 Source: python-cliapp Binary: python-cliapp Architecture: source Version: 1.20160316-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzen

New requirements for ITPs? (was: Bug#815675: ITP: ftpbackup -- Script to backups your data from a Debian system to a ftp space)

On Wed, Feb 24, 2016 at 03:29:35PM +0100, Jakub Wilk wrote: > To avoid unpleasant situations like this, I recommend to never combine roles > of upstream and Debian maintainer. > > If you wrote something cool, instead of uploading it to ftp-master, write a > blog post about it. If it's really as

Re: 50.000 binary packages

On Mon, Feb 08, 2016 at 10:53:26AM +0100, Holger Levsen wrote: > So 50k not yet :-) I remember when Christoph Lameter wrote the first packaging helper, and the number of packages skyrocketed. If I remember the numbers correctly, the package count went from 200 to 400 in a matter of a small number

Accepted cmdtest 0.22-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 04 Feb 2016 11:33:30 +0200 Source: cmdtest Binary: cmdtest Architecture: all source Version: 0.22-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted obnam 1.19.1-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 30 Jan 2016 11:07:22 +0200 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.19.1-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted cmdtest 0.20-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Jan 2016 16:11:02 +0200 Source: cmdtest Binary: cmdtest Architecture: all source Version: 0.20-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted cmdtest 0.21-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Jan 2016 17:26:10 +0200 Source: cmdtest Binary: cmdtest Architecture: all source Version: 0.21-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted obnam 1.19-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Jan 2016 18:23:05 +0200 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.19-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Re: Debian package non-strict equal dependencies

On Tue, Jan 12, 2016 at 05:58:48PM +0300, Dmitrii Kashin wrote: > Hm. It seems to be a solution. But I don't really understand how version > comparison works with symbols `.', `~' and `+'. Where can I read > comparison rules? This is the specification for version comparison rules in Debian:

Accepted python-ttystatus 0.32-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Jan 2016 11:55:02 +0200 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.32-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted python-cliapp 1.20160109-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Jan 2016 12:32:32 +0200 Source: python-cliapp Binary: python-cliapp Architecture: all source Version: 1.20160109-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted cmdtest 0.19-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Jan 2016 11:16:26 +0200 Source: cmdtest Binary: cmdtest Architecture: all source Version: 0.19-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Re: support for merged /usr in Debian

On Fri, Jan 08, 2016 at 01:31:12PM -0800, Russ Allbery wrote: > What will kill Debian faster than anything else is to have every idea for > changing something large, interesting, or possibly revolutionary in Debian > be met with anger, derision, and attacks. Hear, hear. I snipped out the rest of

Re: Known issues with automatic dbgsym packages (Was: Automatic dbgsym packages built by default as of today!)

On Sun, Dec 20, 2015 at 10:35:05AM +, Niels Thykier wrote: > * reprepro rejects upload with automatic debug symbols as it does not >support them yet[1]. (#730572) >- Workaround #1: Build with --no-ddebs / DEB_BUILD_OPTIONS=noddebs >- Workaround #2: Pass --ignore=surprisingbinary

Accepted obnam 1.18.2-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Nov 2015 22:12:15 +0200 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.18.2-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted obnam 1.18.1-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Nov 2015 11:52:58 + Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.18.1-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted cmdtest 0.18-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Nov 2015 11:13:11 + Source: cmdtest Binary: cmdtest Architecture: all source Version: 0.18-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted obnam 1.18-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 04 Nov 2015 21:52:25 +0200 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.18-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted summain 0.20-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Oct 2015 09:24:06 +0200 Source: summain Binary: summain Architecture: amd64 i386 source Version: 0.20-1 Distribution: unstable Urgency: low Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted python-coverage-test-runner 1.11-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Oct 2015 13:17:24 +0200 Source: python-coverage-test-runner Binary: python-coverage-test-runner Architecture: all source Version: 1.11-1 Distribution: unstable Urgency: low Maintainer: Lars Wirzenius <l...@liw.fi> C

Accepted python-larch 1.20151025-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Oct 2015 12:32:05 +0200 Source: python-larch Binary: python-larch Architecture: all source Version: 1.20151025-1 Distribution: unstable Urgency: low Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzen

Accepted python-tracing 0.9-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Oct 2015 09:54:54 +0200 Source: python-tracing Binary: python-tracing Architecture: all source Version: 0.9-1 Distribution: unstable Urgency: low Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzen

Accepted cmdtest 0.17-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Oct 2015 19:29:07 +0300 Source: cmdtest Binary: cmdtest Architecture: all source Version: 0.17-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted genbackupdata 1.9-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 18 Oct 2015 10:29:58 +0300 Source: genbackupdata Binary: genbackupdata Architecture: all source Version: 1.9-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzen

Accepted python-ttystatus 0.30-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 17 Oct 2015 19:04:52 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.30-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted python-ttystatus 0.29-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 11 Oct 2015 19:08:24 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.29-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted python-ttystatus 0.27-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 10 Oct 2015 12:04:59 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.27-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted python-ttystatus 0.28-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 10 Oct 2015 16:18:36 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.28-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Re: init script, installed but not activated

On Wed, Oct 07, 2015 at 11:28:41AM +0300, Hleb Valoshka wrote: > On 10/6/15, Antonio Terceiro wrote: > > > for sysvinit you need to code that manually in the initscript. several > > packages have their initscripts source /etc/default/$package, and check > > for some variable

Re: Defaulting to i686 for the Debian i386 architecture

On Tue, Oct 06, 2015 at 04:45:08PM +0300, Konstantin Khomoutov wrote: > A minor heads-up: your script incorrectly uses "tac" instead of "tsc". If anyone wants to put this into a package, please fix that. :) Would it be useful to have something like that script in a package? If so, which package?

Re: Defaulting to i686 for the Debian i386 architecture

On Tue, Oct 06, 2015 at 10:47:43AM +0200, Jakub Wilk wrote: > * Philip Hands , 2015-10-06, 09:35: > > sed -ne > > '/^flags\t/{s/\b\(fpu\|tsc\|cx8\|cmov\)\b/%/g;s/[^%]*//g;s//i686 > > SUPPORTED/p}' /proc/cpuinfo > > Or a more readable version: > > [ $(lscpu | grep ^Flags: |

Accepted python-ttystatus 0.26-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 06 Oct 2015 12:29:11 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.26-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted python-ttystatus 0.25-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 05 Oct 2015 22:37:01 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.25-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted python-ttystatus 0.24.1-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Oct 2015 19:23:22 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.24.1-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wir

Accepted python-ttystatus 0.24-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Sep 2015 10:14:35 +0300 Source: python-ttystatus Binary: python-ttystatus Architecture: all source Version: 0.24-1 Distribution: unstable Urgency: low Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzen

Re: DAK Commands for Bikesheds

On Fri, Sep 18, 2015 at 01:29:22PM +0100, Wookey wrote: > +++ Colin Tuckley [2015-09-18 12:22 +0100]: > > We certainly (imho) don't want anything in Debian given that description > > > > Oh yes we do! > > Should we leave this naming to the people actually doing the work to implement this?

Accepted obnam 1.17-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 12 Sep 2015 12:40:10 +0300 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.17-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Accepted obnam 1.16-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 06 Sep 2015 16:25:28 +0300 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.16-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius <l...@liw.fi> Changed-By: Lars Wirzenius <l.

Re: Security concerns with minified javascript code

On Tue, Sep 01, 2015 at 06:05:09PM -0700, Russ Allbery wrote: > Healthy language communities have their own metadata systems and > standardized build systems that allow Debian packaging to be nearly > automated, *provided* that we use the same unit of distribution as > upstream. If we want to

Accepted python-cliapp 1.20150829-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 29 Aug 2015 20:24:30 +0300 Source: python-cliapp Binary: python-cliapp Architecture: all source Version: 1.20150829-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l

Re: GoogleCode, gitorious and codehaus.org end of life, expected URL breakage ahead!

On Wed, Aug 26, 2015 at 12:10:18PM +0200, Simon Kainz wrote: [ list of package names removed ] I believe Neil would like you to run the following command: dd-list $(cat codehaus.org.txt) and similarly for any other lists. This results in output listing the maintainers for each package, and

Accepted obnam 1.15-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 19 Aug 2015 21:37:55 +0200 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.15-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi Closes

Accepted obnam 1.14-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Aug 2015 20:51:41 +0200 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.14-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi

Accepted obnam 1.13-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Aug 2015 19:24:46 +0300 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.13-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi Closes

Accepted genbackupdata 1.8-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 14 Jul 2015 18:07:07 +0300 Source: genbackupdata Binary: genbackupdata Architecture: all source Version: 1.8-1 Distribution: unstable Urgency: low Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi

Accepted obnam 1.12-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 08 Jul 2015 15:58:31 +0300 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.12-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi

Accepted obnam 1.11-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Jul 2015 17:02:10 +0300 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.11-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi Closes

Accepted obnam 1.10-1 (amd64 i386 source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 01 Jul 2015 18:14:49 +0300 Source: obnam Binary: obnam Architecture: amd64 i386 source Version: 1.10-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi Closes

Accepted python-cliapp 1.20150701-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 01 Jul 2015 08:30:01 +0300 Source: python-cliapp Binary: python-cliapp Architecture: all source Version: 1.20150701-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l

Accepted cmdtest 0.16-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 30 Jun 2015 17:20:37 +0300 Source: cmdtest Binary: cmdtest Architecture: all source Version: 0.16-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l...@liw.fi

Accepted soundconverter 2.1.4-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Nov 2014 09:15:12 + Source: soundconverter Binary: soundconverter Architecture: source all Version: 2.1.4-1 Distribution: unstable Urgency: medium Maintainer: Lars Wirzenius l...@liw.fi Changed-By: Lars Wirzenius l

Re: Bug#765512: general: distrust old crypto algos and protocols perdefault

On Thu, Oct 16, 2014 at 05:42:23AM +0200, Christoph Anton Mitterer wrote: On Wed, 2014-10-15 at 18:31 -0700, Russ Allbery wrote: It feels to me like you're spending lots of time telling other people they're wrong and telling other people what they should be spending time on, and then

Re: daemon user naming scheme

On Tue, Aug 26, 2014 at 12:40:04PM -0500, Matt Zagrabelny wrote: On Tue, Aug 26, 2014 at 12:10 PM, Matthias Urlichs matth...@urlichs.de wrote: adduser tango --uid $UID --gid $GID typo? adduser _tango --uid $UID --gid $GID The sysadmin may have written scripts and things that assume

Re: systemd service and /etc/default/

On Mon, Aug 18, 2014 at 09:31:37AM -0700, Russ Allbery wrote: More generally (and this part is not pointed at Thomas), I realize it's become de rigueur in any thread about systemd to reply to hm, you could consider getting a dog with WHY DO YOU WANT TO KILL MY KITTENS?!?!?, but seriously

Re: Standardizing the layout of git packaging repositories

On Mon, Aug 18, 2014 at 07:28:51PM -0400, Barry Warsaw wrote: Also, it makes me somewhat uncomfortable to assume that a git tag in the upstream repo will always be equivalent to their released tarball. In fact, it's often not, as is the case with Python packages containing a MANIFEST.in. I

<    1   2   3   4   5   6   7   8   9   10   >