-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/06 00:03, Goswin von Brederlow wrote:
> "Roberto C. Sanchez" <[EMAIL PROTECTED]> writes:
>
>> On Sat, Oct 14, 2006 at 07:30:15PM +0200, Holger Levsen wrote:
[snip]
> I think it should be in the porters control what packages to
> build for an
On Sun, 15 Oct 2006, Charles Plessy wrote:
The interest with debtags is that it allows to change the policy for a
package without needing an upload or the intervention of the maintainer.
This way, the decision of not building could be taken by the maintainer,
and it could be reverted quickly by
"Roberto C. Sanchez" <[EMAIL PROTECTED]> writes:
> On Sat, Oct 14, 2006 at 07:30:15PM +0200, Holger Levsen wrote:
>>
>> Isn't it up to the maintainer to say $package is not suited for
>> $architecture?
>> And aren't maintainers happy to receive hints (e.g. from porters or users of
>> a certain
On Mon, Oct 02, 2006 at 11:21:45AM +0200, Aurelien Jarno wrote:
> Aurelien Jarno wrote:
> >Hi all,
> >
> >As Debian^WDunc-tank experiments with funding, I have loosed motivation
> >to spend so much time on my packages. I have therefore decided to
> >experiment with orphaning a few of my packages
I'm orphaning the following packages. I'm no longer interested in
maintaining them unless the project pays me for it.
* h5utils
* hdf5 - very useful tool for finding ICEs in gcc. Otherwise,
fragile library which implies working around bugs introduced by
incompetent upst
Le Sat, Oct 14, 2006 at 11:51:49AM +0100, Wookey a écrit :
>
> Perhaps debtags could be used as an appropriate classification
> mechanism.
Hi all,
As a maintainer of scientific packages, I agree with this idea. I
always feel sorry to see my packages sitting in the queue of slow arches
while I a
Greetings,
This message is an automated, unofficial publication of vote results.
Official results shall follow, sent in by the vote taker, namely
Debian Project Secretary
This email is just a convenience for the impatient.
I remain, gentle folks,
Your humble servant,
De
Greetings,
This message is an automated, unofficial publication of vote results.
Official results shall follow, sent in by the vote taker, namely
Debian Project Secretary
This email is just a convenience for the impatient.
I remain, gentle folks,
Your humble servant,
De
Greetings,
This message is an automated, unofficial publication of vote results.
Official results shall follow, sent in by the vote taker, namely
Debian Project Secretary
This email is just a convenience for the impatient.
I remain, gentle folks,
Your humble servant,
De
Greetings,
This message is an automated, unofficial publication of vote results.
Official results shall follow, sent in by the vote taker, namely
Debian Project Secretary
This email is just a convenience for the impatient.
I remain, gentle folks,
Your humble servant,
De
Aurélien GÉRÔME <[EMAIL PROTECTED]> writes:
> Hi,
>
> On Thu, Oct 12, 2006 at 12:10:51AM +0200, Mario Iseli wrote:
>> as described in
>> http://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt
>> I announce here my idea of the virtual package ircd. When I count
>> correctly are
I would think that keyboard repeat rate is the domain of the kernel's
keyboard driver. Since there are multiple kernels which can underly
Debian, I don't see how this is feasible. Especially since each will
have its own mechanism for that sort of thing.
Regards,
-Roberto
--
Roberto C. Sanchez
On Sat, Oct 14, 2006 at 02:30:14AM +0100, Wookey wrote:
> In general debian builds everything for every architecture. This is a
> very good plan and finds a lot of bugs.
Hi Wookey,
endian bugs, 32/64 bit bugs, int size bugs, more eyes on bad code, more
users on bad code, low-mem compiling, low-mem
Processing commands for [EMAIL PROTECTED]:
> reassign 391118 general
Bug#391118: The longer you hold down keyboard keys, the faster they should
repeat
Warning: Unknown package 'unknown'
Bug reassigned from package `unknown' to `general'.
> --
Stopping processing here.
Please contact me if you n
On Sat, Oct 14, 2006 at 10:52:41PM +0200, Uwe Hermann wrote:
> Hi Steve,
>
> On Tue, Oct 10, 2006 at 08:25:26PM +0100, Steve Kemp wrote:
> >* flawfinder
> >* pscan
>
> As I haven't gotten around to do too much audit work, I'll at least take
> care of a few audit tools: flawfinder and psca
Hi Steve,
On Tue, Oct 10, 2006 at 08:25:26PM +0100, Steve Kemp wrote:
>* flawfinder
>* pscan
As I haven't gotten around to do too much audit work, I'll at least take
care of a few audit tools: flawfinder and pscan. It seems rats already
has a new maintainer...
Cheers, Uwe.
--
Uwe Herma
On Sat, Oct 14, 2006 at 07:30:15PM +0200, Holger Levsen wrote:
>
> Isn't it up to the maintainer to say $package is not suited for
> $architecture?
> And aren't maintainers happy to receive hints (e.g. from porters or users of
> a certain package), which specific package is not suited for a spe
Hi,
On Saturday 14 October 2006 12:51, Wookey wrote:
> Nevertheless I think it is clear that we do need mechanisms to keep
> the load and package set appropriate for slower arches. If we design
> the mechanism properly I would hope it could be useful for various
> categorisation/subsetting purpose
On Sat, Oct 14, 2006 at 12:21:35PM +0200, Toni Mueller wrote:
> I agree with most of what Wookey and you said, but would like some
> clarification on this:
> On Sat, 14.10.2006 at 12:06:20 +0200, Ingo Juergensmann <[EMAIL PROTECTED]>
> wrote:
> > But sadly, I have very little hope that Debian wil
On 2006-10-14 12:06 +0200, Ingo Juergensmann wrote:
> On Sat, Oct 14, 2006 at 02:30:14AM +0100, Wookey wrote:
> I believe the Vancouver proposal went into wrong direction by excluding
> (slower) archs from releases. Of course, dropping archs is a quick and easy
> way to lighten the load for a rele
Hello,
I agree with most of what Wookey and you said, but would like some
clarification on this:
On Sat, 14.10.2006 at 12:06:20 +0200, Ingo Juergensmann <[EMAIL PROTECTED]>
wrote:
> But sadly, I have very little hope that Debian will change anything it's
> release structure soon. *sigh*
Best
Package: wnpp
Severity: wishlist
Owner: "Adam Cécile (Le_Vert)" <[EMAIL PROTECTED]>
* Package name: ophcrack
Version : 2.3.3
Upstream Author : Philippe Oechslin <[EMAIL PROTECTED]>
Cedric Tissieres <[EMAIL PROTECTED]>
* URL : http://ophcrack.sourcefo
Package: wnpp
Severity: wishlist
Owner: "Adam Cécile (Le_Vert)" <[EMAIL PROTECTED]>
* Package name: samdump2
Version : 1.0.0
Upstream Author : Nicola Cuomo <[EMAIL PROTECTED]>
* URL : http://www.studenti.unina.it/~ncuomo/syskey/
* License : GPL w/ OpenSSL except
On Sat, Oct 14, 2006 at 02:30:14AM +0100, Wookey wrote:
> In general debian builds everything for every architecture. This is a
> very good plan and finds a lot of bugs.
Agreed.
> However there are some packages which are clearly not sensible on some
> arches. Numerical analysis software in gene
Package: wnpp
Severity: wishlist
Owner: "Adam Cécile (Le_Vert)" <[EMAIL PROTECTED]>
* Package name: bkhive
Version : 1.0.0
Upstream Author : Nicola Cuomo <[EMAIL PROTECTED]>
* URL : http://www.studenti.unina.it/~ncuomo/syskey/
* License : GPL
Description :
On Friday 13 October 2006 17:18, John Goerzen wrote:
> Even worse, you again have to use KDE or Gnome to take advantage of
> network-manager. Why are we leaving CLI users out in the cold? It is
> quite possible to use mutt, ssh, and ftp on a laptop. And it's
> frustrating to know that my network
Qua, 2006-10-11 às 23:17 +0200, Tim Dijkstra escreveu:
> One problem is that a user can launch a daemon that keeps the device file
> open before she logs out
> Also I was referring to how pam_group works, but I find this way of
> handling permissions even more broken than pam_group. For example,
>
Hello,
I have a problem with the package tagcoll2: it builds on all
architectures:
http://people.debian.org/~igloo/status.php?email=enrico%40debian.org
except Alpha:
http://buildd.debian.org/fetch.cgi?pkg=tagcoll2;ver=2.0.3-2;arch=alpha;stamp=1160679986
I already spent quite some time some m
Steve Langasek <[EMAIL PROTECTED]> wrote:
> According to http://ftp-master.debian.org/new.html, the oldest package in
> NEW is 3 weeks old. 3 weeks ago was more than a full month after the
> original proposed base freeze date for etch[1].
That might be misleading, because the date is reset when
[Jörg Sommer]
>> It was pointed out to me, that even the scripts starting with S are
>> called with argument 'stop' for runlevels 0 and 6 by /etc/init.d/rc.
>> However, the reason why it is implemented that way is still not clear.
>
> Because the S scripts are run after the K scripts. This way i
[Christian Perrier]
> From what I see, having this will not happen for etch. Do you think it
> could be a release goal for etch+1?
I believe it should be a release goal for etch+1 to switch sysv-rc to
use a dependency based sequencing, yes.
> With that already decided and widely accepted, it wou
31 matches
Mail list logo
