buildd and experimental

2006-02-27 Thread Thomas Bushnell BSG
I recently uploaded gnucash 1.9.1 to Debian experimental, but this doesn't seem to have affected buildd.debian.org. Is this normal? Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: timezone data packaged separately and in volatile?

2006-02-27 Thread Lionel Elie Mamane
On Thu, Feb 09, 2006 at 07:42:25PM +0900, GOTO Masanori wrote: > At Tue, 7 Feb 2006 14:30:01 +1100, > Anand Kumria wrote: >> On Thu, Feb 02, 2006 at 11:42:31PM +0100, Lionel Elie Mamane wrote: >>> I just realised that the timezone data in glibc is taken from an >>> upstream database (namely ftp://

Re: buildd and experimental

2006-02-27 Thread Brian M. Carlson
On Mon, 2006-02-27 at 22:59 -0800, Thomas Bushnell BSG wrote: > I recently uploaded gnucash 1.9.1 to Debian experimental, but this > doesn't seem to have affected buildd.debian.org. Is this normal? Yes. You want experimental.ftbfs.de, specifically:

Re: Bug#353277: ndiswrapper in main

2006-02-27 Thread Marc Haber
On Mon, 27 Feb 2006 13:33:04 -0800, Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote: >[EMAIL PROTECTED] (Marco d'Itri) writes: >> On Feb 27, Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote: >>> If it were put in contrib (by accident, say), how would this cause a >>> problem, assuming that the installer

Re: buildd and experimental

2006-02-27 Thread Thomas Bushnell BSG
"Brian M. Carlson" <[EMAIL PROTECTED]> writes: > On Mon, 2006-02-27 at 22:59 -0800, Thomas Bushnell BSG wrote: >> I recently uploaded gnucash 1.9.1 to Debian experimental, but this >> doesn't seem to have affected buildd.debian.org. Is this normal? > > Yes. You want experimental.ftbfs.de, specif

Re: Bug#353277: ndiswrapper in main

2006-02-27 Thread Hamish Moffatt
On Mon, Feb 27, 2006 at 10:16:38PM +, Stephen Gran wrote: > This one time, at band camp, Thomas Bushnell BSG said: > > I think this is clearly incorrect. The DFSG and the SC do not say > > anything about the requirements for main that I can see. > > This is a clear misunderstanding, AFAICT.

<    1   2