Some files not fetched by debmirror

2017-10-27 Thread dalo...@gmail.com
Hi list, I'm trying to fetch the wheezy mirror using debmirror. However, some files are ignored by debmirror. For instance, wheezy-updates' main binary-installer for i386 has a Packages.gz [1] file that seems an empty (20 bytes) . debmirror ignores it. When running debmirror to only fetch that deb

Re: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

2017-10-27 Thread Pirate Praveen
On ഞായര്‍ 08 ഒക്ടോബര്‍ 2017 05:57 വൈകു, Pirate Praveen wrote: > Though it will require updating npm to a newer version [3] and/or > packaging yarn [4] (both are in progress). Yesterday Sruthi launched a crowd funding campaign to update npm. https://www.generosity.com/fundraising/update-npm-package

Re: Removing Qt4 in Buster

2017-10-27 Thread Paul Wise
On Fri, Oct 27, 2017 at 11:05 PM, Andrey Rahmatullin wrote: > Just bundle the libs, as you would do on Windows, and you'll be fine (wrt > Qt, not wrt libc, but that's a separate problem). After all, running > software compiled on a different system was never fully supported even if > the dependenc

Bug#879968: ITP: python-sushy -- small library to communicate with Redfish based systems

2017-10-27 Thread Thomas Goirand
Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: python-sushy Version : 1.1.0 Upstream Author : OpenStack Foundation * URL : https://github.com/openstack/sushy * License : Apache-2.0 Programming Lang: Python Description : small li

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread Holger Levsen
On Fri, Oct 27, 2017 at 11:24:29AM -0400, Anthony DeRobertis wrote: > > recommends wont work, they arent installed on upgrades… > I haven't tested it, but at least according to apt's changelog new > recommends are installed on upgrade as of 0.7.0 as log as > APT::Install-Recommends is true, which h

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread Anthony DeRobertis
On Fri, Oct 27, 2017 at 01:00:58PM +, Holger Levsen wrote: > recommends wont work, they arent installed on upgrades… I haven't tested it, but at least according to apt's changelog new recommends are installed on upgrade as of 0.7.0 as log as APT::Install-Recommends is true, which has been the

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread Anthony DeRobertis
On Fri, Oct 27, 2017 at 10:01:18AM +0200, Mathieu Parent wrote: > Could'nt we: > > 5. Make linux-image-$abi-$arch Depends on apparmor | selinux-basics | > tomoyo-tools | linux-no-lsm > > With linux-no-lsm being a new empty package, and all of apparmor, > selinux-basics, tomoyo-tools enable the c

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread Anthony DeRobertis
On Fri, Oct 27, 2017 at 08:57:26AM -0400, Jeremy Bicha wrote: > On Thu, Oct 26, 2017 at 11:29 PM, Anthony DeRobertis > wrote: > > 3. Have a Recommends or Depends on it from another package that is > > installed. (Presumably that'd be a Recommends from the linux-image-* > > packages, and would be d

Re: Removing Qt4 in Buster

2017-10-27 Thread Andrey Rahmatullin
On Fri, Oct 27, 2017 at 03:40:25PM +0100, Jonathan Dowland wrote: > The rationale for keeping qt4 in the archive for me (same for gtk1, > gtk2, etc.) is so that people could continue to build or run > out-of-distro legacy software far into the future. It saddens me that I > could very likely run an

Re: Removing Qt4 in Buster

2017-10-27 Thread Jonathan Dowland
On Fri, Oct 27, 2017 at 11:34:14AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: No, we are actively working towards removing Qt4 from the archive during the Buster cycle. In this case libressl might help giving it a little bit longer life, but nothing more. That's entirely up to you; but,

Re: Removing Qt4 in Buster

2017-10-27 Thread Lisandro Damián Nicanor Pérez Meyer
Hi Jonathan! On martes, 17 de octubre de 2017 08:49:58 -03 Jonathan Dowland wrote: > On Tue, Sep 05, 2017 at 03:29:31PM -0300, Lisandro Damián Nicanor Pérez > > Meyer wrote: > >Hi everyone! This is the required notice before starting with the mass > >bug filling in order to *try* to remove Qt4 in

Bug#879946: ITP: suggest-el -- discover Emacs Lisp functions based on examples

2017-10-27 Thread Lev Lamberov
Package: wnpp Owner: Lev Lamberov Severity: wishlist * Package name: suggest-el Version : 0.5 Upstream Author : Wilfred Hughes * URL or Web page : https://github.com/Wilfred/suggest.el * License : GPL-3+ Programming Lang: Emacs Lisp Description : discover Emacs Li

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread Holger Levsen
On Fri, Oct 27, 2017 at 08:57:26AM -0400, Jeremy Bicha wrote: > > 3. Have a Recommends or Depends on it from another package that is > > installed. (Presumably that'd be a Recommends from the linux-image-* > > packages, and would be dropped down to a Suggests for buster+1). > Why shouldn't it stay

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread Jeremy Bicha
On Thu, Oct 26, 2017 at 11:29 PM, Anthony DeRobertis wrote: > 3. Have a Recommends or Depends on it from another package that is > installed. (Presumably that'd be a Recommends from the linux-image-* > packages, and would be dropped down to a Suggests for buster+1). Why shouldn't it stay a Recomm

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread intrigeri
Hi, intrigeri: > Chris Lamb: >> So… in the spirit of taking (reversible!) risks, can you briefly outline >> what's blocking us enabling this today? :) > Thanks for asking! > I've scheduled time on October 23-27 to: We made good progress. Thanks a lot to Vincas Dargis and the Ubuntu and openSUSE

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread intrigeri
Mathieu Parent: > Could'nt we: > 5. Make linux-image-$abi-$arch Depends on apparmor | selinux-basics | > tomoyo-tools | linux-no-lsm > With linux-no-lsm being a new empty package, and all of apparmor, > selinux-basics, tomoyo-tools enable the corresponding LSM. This would be ideal on the long te

Re: Let's enable AppArmor by default (why not?)

2017-10-27 Thread Mathieu Parent
Hi, 2017-10-27 5:29 GMT+02:00 Anthony DeRobertis : > I think the only two ways to get a new package installed upon stretch → > buster are: > > 1. Suggest the admin do it in the release notes. (It should be documented in > the release notes no matter which option we pick, of course.) > > 2. Suggest