Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: sahara
Version : 2014.2
Upstream Author : OpenStack Development Mailing List
* URL : https://github.com/openstack/sahara
* License : Apache-2.0
Programming Lang: Python
Description
Hi,
> Le Tue, Sep 23, 2014 at 07:22:11PM +0200, Marco d'Itri a écrit :
>> On Sep 23, Ralf Jung wrote:
>>
>>> I've seen multiple machines, including older machines of myself, to be
>>> under full disk load for at least several minutes due to (some form of)
>>> locate - every time the cronjob runs.
This is a particularly common problem with team maintenance packages or
with psuedo-packages (like release.debian.org) where a lot of people
may be on the list.
Please always include the package name / topic in the subject of the
email or, as a matter of last resort, in the first few lines of the
Hi Neil,
On Mon, Sep 08, 2014 at 04:43:03PM +0100, Neil McGovern wrote:
[...]
> The compatibility information comes from users testing hardware on
> systems running only free software. Previously, h-node site guidelines
> required they be running one of the FSF's endorsed distributions [2].
> Whil
On 24/09/14 11:46, Neil Williams wrote:
> This is a particularly common problem with team maintenance packages or
> with psuedo-packages (like release.debian.org) where a lot of people
> may be on the list.
>
> Please always include the package name / topic in the subject of the
> email or, as a m
Wouter Verhelst writes:
> This paragraph is phrased carefully so as to make it ambiguous whether
> the FSF acknowledges that Debian's main repository is the only place
> packages come from by default. Do they?
They do, in their explanation of why Debian is not FSF endorsed.
Debian's Social
Emilio Pozuelo Monfort writes:
> Or even better: properly set In-Reply-To / References. You can easily
> do this by downloading an email from the bug thread and replying to
> that.
Good advice. It's as easy as:
$ bts show --mbox
or add the ‘--mailreader=foo’ option if you want a MUA other
Hi,
>> Or even better: properly set In-Reply-To / References. You can easily
>> do this by downloading an email from the bug thread and replying to
>> that.
>
> Good advice. It's as easy as:
>
> $ bts show --mbox
>
> or add the ‘--mailreader=foo’ option if you want a MUA other than Mutt.
* Philipp Kern [2014-09-11 09:15]:
> Not everyone uses init scripts. There is e.g. also a plugin for
> network-manager, in which case it will just work.
Last time I used n-m for OpenVPN it could only launch one VPN, not
multiple ones. Has that changed? Tough it seems systemd upstream is not
happ
Hi,
[Full quote of the intitial message for the benefit of the BTS archive.]
> On 24/09/14 11:46, Neil Williams wrote:
>> This is a particularly common problem with team maintenance packages or
>> with psuedo-packages (like release.debian.org) where a lot of people
>> may be on the list.
>>
>> Pl
On Wed, Sep 24, 2014 at 12:32 PM, David Prévot wrote:
> Or convince the BTS maintainers that #744339 is actually worth fixing
> (the subjects already get mangled to add the bug number one can already
> see in the To: field anyway, adding the package name on top or instead
> of it wouldn’t be such
On 24/09/14 11:45, Martin Wuertele wrote:
> Last time I used n-m for OpenVPN it could only launch one VPN, not
> multiple ones. Has that changed?
Yes, I've had home and office VPNs up at the same time.
(Obviously if you have more than one VPN that wants to provide the
default route, or more gener
Hi *,
I’ve just written a hookscript for pbuilder which makes the
locally cached files available during a package build. Just
chmod +x it, drop it into the --hookdir, and you’re set¹².
Usage scenario here is mostly debian-ports: when building
packages that depend on each other, you no longer have
On Wed, 24 Sep 2014, Thorsten Glaser wrote:
> Usage scenario here is mostly debian-ports: when building
> packages that depend on each other, you no longer have to
> wait until the first package is Installed until you can
> build the second package³. It also makes older packages,
Hrm. Just, there
Package: wnpp
Severity: wishlist
Owner: Timo Aaltonen
* Package name: jackson-jaxrs-providers
Version : 2.4.2
Upstream Author : Tatu Saloranta
* URL : http://wiki.fasterxml.com/JacksonHome
* License : Apache 2.0
Programming Lang: Java
Description : Jack
Hi,
It's not abuse, "possible" abuse (IMO, at least :)
- xz -z9 is very efficient for some cases (e.g. huge font package)
- good for mirror infrastructures and low-bandwidth client
On Thu, 4 Sep 2014 10:49:59 +0200
Thorsten Glaser wrote:
> Such as mips?
Surely it would be not comfortable
* Emilio Pozuelo Monfort , 2014-09-24, 12:10:
On 24/09/14 11:46, Neil Williams wrote:
can people from this list *please* include something specific to the
actual package/topic in the Subject of emails to bug reports? At the
very least, something in the first few lines of the content saying
wha
* David Prévot , 2014-09-24, 06:32:
Or convince the BTS maintainers that #744339 is actually worth fixing
(the subjects already get mangled to add the bug number one can already
see in the To: field anyway, adding the package name on top or instead
of it wouldn’t be such a bad move IMHO).
So
On Wed, 24 Sep 2014 19:10:54 +0200
Jakub Wilk wrote:
> * David Prévot , 2014-09-24, 06:32:
> >Or convince the BTS maintainers that #744339 is actually worth
> >fixing (the subjects already get mangled to add the bug number one
> >can already see in the To: field anyway, adding the package name on
On Wed, 24 Sep 2014 18:30:28 +0100
Neil Williams wrote:
One other idea - maybe the top level reply link (the one showing the bug
number at the very top of the page) could use the current bug title as
the subject of the reply rather than leaving it blank?
--
Neil Williams
=
http://
On 09/02/2014 09:39 PM, Henrique de Moraes Holschuh wrote:
> For -z9, it is as bad as ~670MiB to
> compress, and ~65MiB to decompress.
I'd say this really depends on what you do. For what I do (eg: OpenStack
packages), I don't see how 65MB could be a problem. I do compress with
-z9, and have no in
On 09/03/2014 01:49 PM, Andrey Rahmatullin wrote:
> Decompression costs were mentioned too, and they always matter
I don't agree.
Thomas
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http
On 09/04/2014 03:10 AM, Christian Kastner wrote:
> Benefits: from the numbers posted in this thread, the size savings
> compared to the default compression level for some sample packages are
> somewhere around 3% to 4%. I claim that *practical* benefits from this
> saving are insignificant to minor
On 09/04/2014 04:58 PM, Ansgar Burchardt wrote:
> On 09/04/2014 10:49, Thorsten Glaser wrote:
>> On Wed, 3 Sep 2014, Christian Kastner wrote:
>>> That is the key question, and I believe considering the worst possible
>>> cost -- a package that cannot be unpacked, as in #757740 -- the
>>> trade-off
On Thu, 25 Sep 2014, Thomas Goirand wrote:
> On 09/02/2014 09:39 PM, Henrique de Moraes Holschuh wrote:
> > For -z9, it is as bad as ~670MiB to
> > compress, and ~65MiB to decompress.
>
> I'd say this really depends on what you do. For what I do (eg: OpenStack
> packages), I don't see how 65MB cou
On Wed, Sep 24, 2014 at 08:28:24PM +1000, Ben Finney wrote:
> Wouter Verhelst writes:
>
> > This paragraph is phrased carefully so as to make it ambiguous whether
> > the FSF acknowledges that Debian's main repository is the only place
> > packages come from by default. Do they?
>
> They do, in
Package: wnpp
Severity: wishlist
Owner: "Patrick Matthäi"
* Package name: apt-dater-host
Version : 1.0.0~
Upstream Author : Thomas Liske
* URL : https://github.com/DE-IBH/apt-dater-host
* License : GPL2+
Programming Lang: Perl
Description : host helper
Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant
* Package name: pyoperators
Version : 0.12.13
Upstream Author : Pierre Chanial
* URL : http://pchanial.github.io/pyoperators/
* License : CeCILL-B
Programming Lang: Python
Description : Op
Dear Debian Developers,
since 1974 researchers and software developers try to ease software
debugging. Over the last years, they created many new tools and
formalized methods. We are interested if these advancements have
reached professional software developers and how they influenced their
approa
29 matches
Mail list logo
