John Goerzen wrote:
> On Mon, Aug 28, 2006 at 05:09:54PM +0200, Joey Schulze wrote:
> > ciol wrote:
> > > The problem is that Debian doesn't speak a lot about nice features like
> > > volatile and backports, for instance in the official web site, where it's
> > > difficult to see the links.
> >
>
On Tue, Aug 29, 2006 at 07:17:47PM -0700, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> On Tue, Aug 29, 2006 at 08:48:00PM -0400, Nathanael Nerode wrote:
>
> > Debian needs to make a decision on how it will deal with this legal
> > minefield. That is higher priority than the entire discussion goin
On Tue, Aug 29, 2006 at 08:48:00PM -0400, Nathanael Nerode wrote:
> Debian needs to make a decision on how it will deal with this legal
> minefield. That is higher priority than the entire discussion going on
> right now, because it determines whether Debian will distribute these 53
> BLOBs *at a
On Tuesday 29 August 2006 11:02, Allen wrote:
> To whom it may concern, I was wondering if you have schedule or roadmap for
> the next available release version of Debian.
Google finds it easily. http://www.debian.org/releases/
--
Paul Johnson
Email and IM (XMPP & Google Talk): [EMAIL PROTECTED
Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Luk Claes wrote:
>> -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
>> 6c557439-9c21-4eec-ad6c-e6384fab56a8
>> [ 1 ] Choice 1: Release etch on time
>> [ 3 ] Choice 2: Do not ship sourceless firmware in
Anthony Towns wrote:
> (c) A number of drivers in the Linux kernel include firmware to be
> uploaded to the chipsets they support that is provided as
> either a sequence of hex codes, or as a separate binary file --
> while modifying the code is allowed, in many if not
Hi,
Uwe Hermann wrote:
> I _could_ create a merged Debian package (biosdeco maybe?) to prevent
> some overhead (if most people think that would be a good idea),
> but per default I thought it'd be a better idea to keep them
> separated if upstream keeps them separated, too...
> Comments, suggest
Hi,
On Tue, Aug 29, 2006 at 05:48:23AM -0500, Ron Johnson wrote:
> How big are these logo extractors? Would it be easier to roll them
> into 1 package named, for example, bios-logo-extractor?
They're not very big and seem quite similar, but I've talked with
upstream and he thinks it's better kee
On Tue, Aug 29, 2006 at 05:40:52AM -0500, Ron Johnson wrote:
> > Description : Decompress flashfiles equipped with an AWARD BIOS
> >
> > Awardeco is a program which can decompress BIOS images which
> > contain an AWARD BIOS.
>
> Please specify that in this case, "BIOS images" means BIOS *lo
On Tue, Aug 29, 2006 at 01:23:48PM +0100, Chris Lamb wrote:
> I disagree, or I am not understanding the difference between the two.
> FSF/GNU devotees would much prefer to use a free BIOS[0] or EEPROM
> code if they had a choice imho.
Yes, and there is a choice, partly already working, partly in t
On Tue, Aug 29, 2006 at 01:51:39PM +0200, Magnus Holmgren wrote:
> On Monday 28 August 2006 21:06, Steve Langasek took the opportunity to say:
> > On Mon, Aug 28, 2006 at 04:01:57PM +0200, Magnus Holmgren wrote:
> > > Making mail-transport-agent the empty package, and having it depend only
> > > on
Thank you.
Allen
-Original Message-
From: Andrew Donnellan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 29, 2006 1:35 PM
To: [EMAIL PROTECTED]
Cc: debian-devel@lists.debian.org
Subject: Re: Next Debian Release
Meaning Etch? The current target is December 4th 2006.
On 8/30/06, Allen
Scripsit "Allen" <[EMAIL PROTECTED]>
> To whom it may concern, I was wondering if you have schedule or
> roadmap for the next available release version of Debian.
The next release of Debian will happen When It's Ready .
Current projections indicate that it may possibly be realistic to
expect it
On Tue, Aug 29, 2006 at 07:24:31AM -1000, Adeodato Simó wrote:
> * Roberto C. Sanchez [Mon, 28 Aug 2006 02:10:22 -0400]:
>
> > > Nope, that won't help. Knowing you use Mutt, and unless your MTA is
> > > configured in a quite restrictive way, this should solve your problems:
>
> > > % echo set e
Allen wrote:
> To whom it may concern, I was wondering if you have schedule or roadmap for
> the next available
> release version of Debian.
http://lists.debian.org/debian-devel-announce/2006/08/msg5.html
Updates are posted there peridically.
--
see shy jo
signature.asc
Description: Dig
Meaning Etch? The current target is December 4th 2006.
On 8/30/06, Allen <[EMAIL PROTECTED]> wrote:
To whom it may concern, I was wondering if you have schedule or roadmap for
the next available
release version of Debian.
Thank You
Allen Mah
HighPoint Technologies, Inc.
Technical Marketing Man
To whom it may concern, I was wondering if you have schedule or roadmap for the
next available
release version of Debian.
Thank You
Allen Mah
HighPoint Technologies, Inc.
Technical Marketing Manager
408-942-5800 x116
www.highpoint-tech.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Steve Langasek wrote (elsewhere):
> something changes in the archive (often for a transition that needs
> to happen), a large number of packages are broken by this, and some
> appreciable number of the maintainers don't respond in a reasonable amount
> of time ("reasonable" defined as "sufficient t
* Roberto C. Sanchez [Mon, 28 Aug 2006 02:10:22 -0400]:
> > Nope, that won't help. Knowing you use Mutt, and unless your MTA is
> > configured in a quite restrictive way, this should solve your problems:
> > % echo set envelope_from=yes >>~/.muttrc
> That did it. Now, care to explain why/how?
On Tue, Aug 29, 2006 at 12:39:03PM +0200, Pierre Habouzit wrote:
> I'm very suprised by that mail that completely forgot to mention the
> ongoing discussions about a GR about firmwares. There is already three
> proposals for that GR[1] and I wonder why those have not been
> mentionned.
Err, b
On Mon, Aug 28, 2006 at 10:26:22AM -0500, John Goerzen wrote:
[volatile and backports]
> As it is, it is unclear to me who is building those packages, of what
> quality they are, and what kind of security support they are receiving.
Volatile was set up by Andreas Barth, and is maintained by Andrea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lamb wrote:
>
> On Tue, 29 Aug 2006 05:37:23 -0500, Ron Johnson wrote:
>> [ x ] Choice 5: Ship *BLOBs* (does *not* mean closed-source
>> drivers like nvidia) that can be legally
>> redistributed, do not ship BLOBs
On Tue, 29 Aug 2006 05:37:23 -0500, Ron Johnson wrote:
> [ x ] Choice 5: Ship *BLOBs* (does *not* mean closed-source
> drivers like nvidia) that can be legally
> redistributed, do not ship BLOBs that can
> not be legally redistributed.
>
> Yes, I k
On Monday 28 August 2006 21:06, Steve Langasek took the opportunity to say:
> On Mon, Aug 28, 2006 at 04:01:57PM +0200, Magnus Holmgren wrote:
> > Making mail-transport-agent the empty package, and having it depend only
> > on exim4 (the default), should work. Of course, exim4 can't conflict with
>
This is an automatically generated reply from the anti-spam system.
Your message to:
-> [EMAIL PROTECTED]
was rated as probable SPAM and has not been delivered.
If this is in error, we apologise and invite you to consult our Web page
http://web.iue.it/CITS/DocumentDetail.jsp?ID=173
to understand
Package: wnpp
Severity: wishlist
Owner: "Krzysztof Krzyzaniak (eloy)" <[EMAIL PROTECTED]>
* Package name: libconfig-any-perl
Version : 0.04
Upstream Author : Joel Bernstein <[EMAIL PROTECTED]>
* URL :
http://mirrors.kernel.org/cpan/modules/by-module/Config/Config-Any-0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uwe Hermann wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Uwe Hermann <[EMAIL PROTECTED]>
>
> * Package name: amideco
> Version : 0.31e
> Upstream Author : Anton Borisov <[EMAIL PROTECTED]>
> * URL : http://www.kaos.
Package: wnpp
Severity: wishlist
Owner: Uwe Hermann <[EMAIL PROTECTED]>
* Package name: amideco
Version : 0.31e
Upstream Author : Anton Borisov <[EMAIL PROTECTED]>
* URL : http://www.kaos.ru/biosgfx/
* License : GPL, LGPL
Programming Lang: C
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uwe Hermann wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Uwe Hermann <[EMAIL PROTECTED]>
>
> * Package name: phnxdeco
> Version : 0.33
> Upstream Author : Anton Borisov <[EMAIL PROTECTED]>
> * URL : http://www.kaos.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uwe Hermann wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Uwe Hermann <[EMAIL PROTECTED]>
>
> * Package name: awardeco
> Version : 0.2
> Upstream Author : Anton Borisov <[EMAIL PROTECTED]>
> * URL : http://www.kaos.r
Le lun 28 août 2006 20:35, Anthony Towns a écrit :
> Hello, world!
>
> […]
>
> Note that both these polls are just an informal way of finding out
> what people think, and while they will be considered and taken into
> account, they won't necessarily be the final word on the matter.
I'm very supr
Package: wnpp
Severity: wishlist
* Package name: dictionaryreader.app
Version : 0.1
Upstream Author : Günther Noack <[EMAIL PROTECTED]>
* URL:
http://www.unix-ag.uni-kl.de/~guenther/gnustep/dictionaryreader.html
* License : GNU GPL
Description : Dict clie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luk Claes wrote:
> -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
> 6c557439-9c21-4eec-ad6c-e6384fab56a8
> [ 1 ] Choice 1: Release etch on time
> [ 3 ] Choice 2: Do not ship sourceless firmware in main
> [ 2 ] Choice 3: Support
Package: wnpp
Severity: wishlist
Owner: Uwe Hermann <[EMAIL PROTECTED]>
* Package name: phnxdeco
Version : 0.33
Upstream Author : Anton Borisov <[EMAIL PROTECTED]>
* URL : http://www.kaos.ru/biosgfx/
* License : GPL, LGPL
Programming Lang: C
Description
Package: wnpp
Severity: wishlist
Owner: Samuel Mimram <[EMAIL PROTECTED]>
* Package name: midish
Version : 0.2.4
Upstream Author : Alexandre Ratchov <[EMAIL PROTECTED]>
* URL : http://caoua.org/midish/
* License : 2-clauses BSD
Programming Lang: C
Descriptio
Package: wnpp
Severity: wishlist
Owner: Uwe Hermann <[EMAIL PROTECTED]>
* Package name: awardeco
Version : 0.2
Upstream Author : Anton Borisov <[EMAIL PROTECTED]>
* URL : http://www.kaos.ru/biosgfx/
* License : GPL, LGPL
Programming Lang: C
Description :
Hi,
-=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
6c557439-9c21-4eec-ad6c-e6384fab56a8
[ ] Choice 1: Release etch on time
[ 1 ] Choice 2: Do not ship sourceless firmware in main
[ ] Choice 3: Support hardware that requires sourceless firmware
[ ] Choice 4: None of th
On Tue, 29 Aug 2006, Lionel Elie Mamane wrote:
> On the other hand, I already tried to discuss that problem with you
> guys (alioth admin team) in May 2006; nothing really came out of
> it. Wichert questioned that it was a problem at all, I (tried to)
> explain why it was a problem, nothing further
38 matches
Mail list logo
