Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: libsodium
Version : 0.3
Upstream Author: Frank Denis
URL : https://github.com/jedisct1/libsodium
License : ISC
Description
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: python-v8
Version: 1.0-preview-r446
Upstream Author: Xiaohai Lu
URL: http://code.google.com/p/pyv8/
License: APL2.0
Description
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: pyftgl
Version: 0.5c
Upstream Author: Anders Dahnielson
URL: http://code.google.com/p/pyftgl/
License: GPLv2
Description: pytho
Hi,
when beeing at Debian Med sprint I explicitely recommended the
participants to also look above our fence for general bugs inside Debian
because also Debian Med development is somehow stalled in the times of
freeze. However, when discussing this I found that other DDs made the
very same observ
On Donnerstag, 28. Februar 2013, Holger Levsen wrote:
> signed commits, so you can identify unwanted bits and clean up in the very
> care case that's actually needed?
^^ rare case
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
On 02/28/2013 08:33 PM, Andrew Shadura wrote:
> we'd have both hg and git in one unified interface.
That is a very nice feature. I saw few sites having that, for example
bitbucket, unfortunatley, bitbucket doesn't allow git anonymous
checkout over http (it's only available with hg, if I understood
On 02/28/2013 06:07 PM, Stefano Zacchiroli wrote:
> On Thu, Feb 28, 2013 at 10:39:26AM +0100, Daniel Pocock wrote:
>> Has anybody had experience controlling access to git repositories, for
>> example, to give users access but prevent some of the following
>> dangerous operations?
> Related to this,
On 1 March 2013 10:54, Thomas Goirand wrote:
> On 02/28/2013 06:07 PM, Stefano Zacchiroli wrote:
>> On Thu, Feb 28, 2013 at 10:39:26AM +0100, Daniel Pocock wrote:
>>> Has anybody had experience controlling access to git repositories, for
>>> example, to give users access but prevent some of the fo
On Fri, Mar 01, 2013 at 10:29:49AM +0100, Andreas Tille wrote:
> However, I failed in keeping this 1 RC bug per week up
> and running just because I realised that a there exist a lot of bugs
> with at least one of the following features:
>
> 1) technically hard to address without doing heavy res
Hi Andreas,
I wholeheartedly agree. I have written about this in 2012-11¹, but in my
article, I complained about the way bugreports are handled, which, IMO,
are much too free-form to be useful for RC bug hunters.
Anyway, I definitely share your experience that many RC bugs are
hardware-specific o
On 03/01/2013 07:21 PM, Dmitrijs Ledkovs wrote:
> On 1 March 2013 10:54, Thomas Goirand wrote:
>> On 02/28/2013 06:07 PM, Stefano Zacchiroli wrote:
>>> On Thu, Feb 28, 2013 at 10:39:26AM +0100, Daniel Pocock wrote:
Has anybody had experience controlling access to git repositories, for
ex
Thomas Goirand (01/03/2013):
> I wasn't discussing what can be done for backing up a Git repository,
> I was asking what is *currently installed* in production as a backup
> for Alioth.
Why are you asking debian-devel@ instead of asking the actual admins?
(http://wiki.debian.org/Alioth#Maintenan
On 03/01/2013 09:34 PM, Cyril Brulebois wrote:
> Thomas Goirand (01/03/2013):
>> I wasn't discussing what can be done for backing up a Git repository,
>> I was asking what is *currently installed* in production as a backup
>> for Alioth.
> Why are you asking debian-devel@ instead of asking the act
Hello,
Its me again. Once again, I'm throwing myself on your mercy because
although I like programming and packaging, I am having a horrible time
finding my way through your web pages to adopt a package and keep it
up to date.
So far I have succeeded in declaring the ITP on the blt packages and
On 2 March 2013 00:12, Paul Johnson wrote:
> Hello,
>
> Its me again. Once again, I'm throwing myself on your mercy because
> although I like programming and packaging, I am having a horrible time
> finding my way through your web pages to adopt a package and keep it
> up to date.
>
> So far I ha
Andreas Tille writes:
> when beeing at Debian Med sprint I explicitely recommended the
> participants to also look above our fence for general bugs inside Debian
> because also Debian Med development is somehow stalled in the times of
> freeze. However, when discussing this I found that other DD
Package: wnpp
Severity: wishlist
Owner: Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: patool
Version : 1.0
Upstream Author : Bastian Kleineidam
* URL : http://wummel.github.com/patool/
* License : GPL
Programming Lang: Pyt
Hello,
On Fri, 01 Mar 2013 18:48:51 +0800
Thomas Goirand wrote:
> On 02/28/2013 08:33 PM, Andrew Shadura wrote:
> > we'd have both hg and git in one unified interface.
> That is a very nice feature. I saw few sites having that, for example
> bitbucket, unfortunatley, bitbucket doesn't allow git
On Fri, Mar 01, 2013 at 06:10:18PM +0600, Andrey Rahmatullin wrote:
> If we ignore those, we get 60 bugs.
46 currently.
--
WBR, wRAR
signature.asc
Description: Digital signature
> I wonder in how far I could do my share in the bug count reduction
> business. Perhaps in helping finding bugs belonging into such
> categories to attract the right people to the right bug and help
> reducing the time for people to detect a reasonable target for
> squashing?
There are always se
Michael Gilbert writes:
>> I wonder in how far I could do my share in the bug count reduction
>> business. Perhaps in helping finding bugs belonging into such
>> categories to attract the right people to the right bug and help
>> reducing the time for people to detect a reasonable target for
>>
On Fri, Mar 1, 2013 at 8:36 PM, Russ Allbery wrote:
>> They may seem intimidating, but they're usually fairly straightforward
>> with a little research.
>
> While I certainly don't want to discourage people from working on
> security-related bugs, note that security-related bugs don't block the
> r
Le Fri, Mar 01, 2013 at 10:29:49AM +0100, Andreas Tille a écrit :
>
> I wonder in how far I could do my share in the bug count reduction
> business. Perhaps in helping finding bugs belonging into such
> categories to attract the right people to the right bug and help
> reducing the time for peopl
Looks like you did everything correctly, except one thing:
On Sat, Mar 2, 2013 at 12:12 AM, Paul Johnson wrote:
> * Closes: #664092
> * Closes: #524149
> * Closes: #636629
It is best to explain what is being closed, please read the devref
section on changelog best practices:
http://www.de
On 03/02/2013 04:42 AM, Paul Wise wrote:
Looks like you did everything correctly, except one thing:
I'd like to disagree here. After having a quick glance at the package on
mentors [1], there is lots of work to be done until the package is
lintian-clean which is what I always prefer when spon
Quoting Charles Plessy (ple...@debian.org):
> In the previous release cycles, it looks like the main blocker was the Debian
> Installer. As soon as it was ready, lots of remaining buggy packages were
> purged from Testing and release followed quite soon. Is that the case for
> this
> release cy
I think debian-devel is not quite a correct place to discuss such kind of
things. Please, use debian-mentors instead.
Thanks,
Anton
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://l
27 matches
Mail list logo
