Re: Marcelo Magallon (lib3ds maintainer) MIA?

2006-07-08 Thread Martin Michlmayr
* Miles Bader <[EMAIL PROTECTED]> [2006-07-08 10:33]: > Does anybody know if the lib3ds maintainer, Marcelo Magallon (email > mmagallo), is still active? He has been busy with RL lately but things got better recently. Signing your messages to him with GPG helps him filter it out from all the spam

Re: Marcelo Magallon (lib3ds maintainer) MIA?

2006-07-08 Thread Miles Bader
Martin Michlmayr <[EMAIL PROTECTED]> writes: >> Does anybody know if the lib3ds maintainer, Marcelo Magallon (email >> mmagallo), is still active? > > He has been busy with RL lately but things got better recently. > Signing your messages to him with GPG helps him filter it out from all > the spam

Re: Marcelo Magallon (lib3ds maintainer) MIA?

2006-07-08 Thread Martin Michlmayr
* Miles Bader <[EMAIL PROTECTED]> [2006-07-08 17:32]: > Er, does that imply that my (non-signed) message likely ended up in the > bit-bucket...? Problably not. I sent him non-signed mail in the past and got replies. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL

Long blurbs repeated in many package descriptions considered harmful

2006-07-08 Thread Enrico Zini
Hello, some groups of packages in Debian share introductory pieces in the package description. For example, most pike packages have this: Pike is an interpreted, object-oriented, dynamic programming language with a syntax similar to C. It includes many powerful data types and a module system

Re: Long blurbs repeated in many package descriptions considered harmful

2006-07-08 Thread Lars Wirzenius
la, 2006-07-08 kello 12:40 +0200, Enrico Zini kirjoitti: > some groups of packages in Debian share introductory pieces in the > package description. For example, most pike packages have this: I tend to like them, if they're concise and at the end of the description. They save me from having to lo

Re: Long blurbs repeated in many package descriptions considered harmful

2006-07-08 Thread Mike Hommey
On Sat, Jul 08, 2006 at 12:40:57PM +0200, Enrico Zini <[EMAIL PROTECTED]> wrote: > Many thanks to the KDE developers for removing the similar blurb that > they used to have. They did it nicely, and in a way that others could > follow. ... which is... ? -- To UNSUBSCRIBE, email to [EMAIL PROTEC

Re: Long blurbs repeated in many package descriptions considered harmful

2006-07-08 Thread Enrico Zini
On Sat, Jul 08, 2006 at 01:47:48PM +0200, Mike Hommey wrote: > On Sat, Jul 08, 2006 at 12:40:57PM +0200, Enrico Zini <[EMAIL PROTECTED]> > wrote: > > Many thanks to the KDE developers for removing the similar blurb that > > they used to have. They did it nicely, and in a way that others could > >

Re: Long blurbs repeated in many package descriptions considered harmful

2006-07-08 Thread Enrico Zini
On Sat, Jul 08, 2006 at 01:52:57PM +0300, Lars Wirzenius wrote: > la, 2006-07-08 kello 12:40 +0200, Enrico Zini kirjoitti: > > some groups of packages in Debian share introductory pieces in the > > package description. For example, most pike packages have this: > I tend to like them, if they're co

Re: Long blurbs repeated in many package descriptions considered harmful

2006-07-08 Thread Adam Borowski
On Sat, Jul 08, 2006 at 02:18:19PM +0200, Enrico Zini wrote: > For example, the pike blurb could be summarised with something like: > > Pike is an interpreted, object-oriented, dynamic programming language > with a syntax similar to C. To learn more about pike, see the package > pike7.6 or

confirmed, fuse really needs a start of udev after adding a group, or /dev/fuse ends up with a wrong group

2006-07-08 Thread Junichi Uekawa
reopen 368674 reassign 368674 fuse-utils thanks Hi, >It works today. Now I remember I installed fuse-utils yesterday, which >means the fuse group did not still exist when udev started. Restarting >udev (or rebooting the system, obviously) fixes the issue. >This behavior seems like the only one p

Re: Broken applications: Could we be honest?

2006-07-08 Thread Török Edvin
On 7/8/06, Art Edwards <[EMAIL PROTECTED]> wrote: I have been writing to the list about two applications that are so broken on the AMD64 distribution that they render the box pretty useless. Did you send bugreports for those programs? Btw, what is the appropriate severity level for a package tha

Broken applications: Could we be honest?

2006-07-08 Thread Art Edwards
I have been writing to the list about two applications that are so broken on the AMD64 distribution that they render the box pretty useless. I'm sure one could say that two measly applications are no big deal. However, if you do scientific computation for a living, and two of the primary tools are

Re: Broken applications: Could we be honest?

2006-07-08 Thread Jimmy Tang
On 7/8/06, Art Edwards <[EMAIL PROTECTED]> wrote: I have been writing to the list about two applications thatare so broken on the AMD64 distribution that they render thebox pretty useless. I'm sure one could say that two measlyapplications are no big deal. However, if you do scientific computation

Re: Broken applications: Could we be honest?

2006-07-08 Thread Roger Leigh
Art Edwards <[EMAIL PROTECTED]> writes: > I have been writing to the list about two applications that are so > broken on the AMD64 distribution that they render the box pretty > useless. From the look of things, we are talking about a single bug in a single library. So the system is hardly "usel

Re: Broken applications: Could we be honest?

2006-07-08 Thread Oliver Rother
Art Edwards wrote: Unless such core pieces as the debugging tool (ddd) and the data display tool (xmgrace) are working, it is dishonest to pretend that the 64-bit version is ready for testing. ddd and grace are in Debian testing (etch) amd64 and work fine. So where exactly is the issue? W

Re: Broken applications: Could we be honest?

2006-07-08 Thread Oliver Rother
Jimmy Tang wrote: At the risk of imposing what we do at our work place onto your work flow, i find that users generally should have access to better debuggers/profilers than what ships with standard gnu distros. Well, if you intend to start a flame war on the lists... but enough on that. p

Re: Broken applications: Could we be honest?

2006-07-08 Thread Jimmy Tang
Hi, On 7/8/06, Oliver Rother <[EMAIL PROTECTED]> wrote: > At the risk of imposing what we do at our work place onto your work > flow, i find that users generally should have access to better > debuggers/profilers than what ships with standard gnu distros. Well, if you intend to start a flame w

Testing and honesty

2006-07-08 Thread Ben Armstrong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Art Edwards wrote: > Unless such core pieces as the debugging tool (ddd) and the data display tool > (xmgrace) are working, it is dishonest to pretend that the 64-bit version > is ready for testing. It seems your expectations for our "testing" distribu

Bug#377402: ITP: oss-compat -- OSS compatibility package

2006-07-08 Thread Robert Millan
Package: wnpp Severity: wishlist Owner: Robert Millan <[EMAIL PROTECTED]> * Package name: oss-compat * URL : http://aybabtu.com/rmh/deb/ * License : GPL Description : OSS compatibility package This package ensures that OSS support is provided in some way. On Linux,

Re: Bug#368674: confirmed, fuse really needs a start of udev after adding a group, or /dev/fuse ends up with a wrong group

2006-07-08 Thread Marco d'Itri
On Jul 08, Junichi Uekawa <[EMAIL PROTECTED]> wrote: > I've confirmed that this really requires restart of udev after fuse install. No, nothing requires restarting udevd. The problem is that for performance reasons udevd resolves users and groups only when loading the rules files. Since the rule

Re: header sanity check?

2006-07-08 Thread Marc 'HE' Brockschmidt
Tyler MacDonald <[EMAIL PROTECTED]> writes: [...] > 1. If you #include a header directly, you have to depend on that > package. [...] > 4. If you #include a header that doesn't belong to *any* package > (including the source package you're currently building), that's just > outright evi

Re: Bug#368674: confirmed, fuse really needs a start of udev after adding a group, or /dev/fuse ends up with a wrong group

2006-07-08 Thread Hamish Moffatt
On Sat, Jul 08, 2006 at 09:21:09PM +0200, Marco d'Itri wrote: > On Jul 08, Junichi Uekawa <[EMAIL PROTECTED]> wrote: > > > I've confirmed that this really requires restart of udev after fuse install. > No, nothing requires restarting udevd. > > The problem is that for performance reasons udevd re

select() to /dev/rtc to wait for clock tick timed out. : a different solution

2006-07-08 Thread Junichi Uekawa
Hi, I've been worried about this small bug where hwclock waits for timeout in while booting, with a message: select() to /dev/rtc to wait for clock tick timed out. The machine is a MacBook, and I see references to this message on dual-core Intel processors, so it looks like a generic problem.

Re: failure notice

2006-07-08 Thread Junichi Uekawa
Hi, MD, Please fix. regards, junichi At 8 Jul 2006 16:27:28 -, [EMAIL PROTECTED] wrote: > > Hi. This is the qmail-send program at viper2.netfort.gr.jp. > I'm afraid I wasn't able to deliver your message to the following addresses. > This is a permanent error; I've given up. Sorry i

Re: Broken applications: Could we be honest?

2006-07-08 Thread Charles Plessy
Le Sat, Jul 08, 2006 at 10:09:56AM -0600, Art Edwards a écrit : > It would be very nice if you, and other distro's, were > to put appropriate caveats on the websites, saying that 64-bit is really not > ready for the prime-time desktop. That way, we could make better purchasing > decisions. Dea

Re: greylisting on debian.org?

2006-07-08 Thread Thomas Bushnell BSG
martin f krafft <[EMAIL PROTECTED]> writes: > This has been brought up. Basically I don't think people were > opposed to it, but there was noone available to implement it. There were people opposed to it, in fact. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". T

Re: greylisting on debian.org?

2006-07-08 Thread Christian Perrier
Quoting Thomas Bushnell BSG ([EMAIL PROTECTED]): > martin f krafft <[EMAIL PROTECTED]> writes: > > > This has been brought up. Basically I don't think people were > > opposed to it, but there was noone available to implement it. > > There were people opposed to it, in fact. What were their argu