Re: FTBFS for illegal archs

[Simon Richter]

Hi,
Wouter Verhelst wrote:
That being said, I'm not sure this is necessary. For starters, Jeroen
included the "if that's possible" bit; but apart from that, it's not
because the ACPI interface does not exist for an architecture today that
it will never exist; it's not completely impossible that one day,
someone will make a PowerPC-based system with an ACPI interface, even if
it is unlikely. At that point, it'd be nice if the package would build
for PowerPC without /too/ much effort. And as long as it won't build on
PowerPC today, your job is done, I'd say.
Not quite unlikely. In fact ACPI support for the Pegasos is on my todo
list. :-)
   Simon


signature.asc
Description: OpenPGP digital signature

Re: What do you win by moving things to non-free?

[Wouter Verhelst]

On Sat, Apr 16, 2005 at 08:42:25PM +0100, Matthew Woodcraft wrote:
> Wouter Verhelst wrote:
> >* The Invariant Section is retained, but another Invariant Section
> >  containing a rebuttal is added to the document. This would a) look
> >  silly, and b) be a beginning of Invariant Section bloat, in which a
> >  document could consist of 10% Invariant Sections, 60% rebuttals to
> >  Invariant Sections, and 30% of actual, useful, documentation.
> 
> I do not think this option is as bad as you make it sound.

The fact that there is a need for a rebuttal, in the first place, is
already a sign that something is very wrong.

> There is no need for the rebuttal to be made invariant, and the
> rebuttal could just be a brief note explaining that the invariant
> section refers to a situation which has gone away.

Well, yeah, in the specific example I gave. Consider the possibility
that the original section refers to a situation which has not gone away,
but that the original author of the document has moved on to go do other
stuff, and that the current maintainers have a different opinion on what
the problem exactly is.

... and now they move on to other things as well.

See?

-- 
The amount of time between slipping on the peel and landing on the
pavement is precisely one bananosecond


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: FTBFS for illegal archs

[Christoph Hellwig]

On Mon, Apr 18, 2005 at 09:08:14AM +0200, Simon Richter wrote:
> Hi,
> 
> Wouter Verhelst wrote:
> 
> >That being said, I'm not sure this is necessary. For starters, Jeroen
> >included the "if that's possible" bit; but apart from that, it's not
> >because the ACPI interface does not exist for an architecture today that
> >it will never exist; it's not completely impossible that one day,
> >someone will make a PowerPC-based system with an ACPI interface, even if
> >it is unlikely. At that point, it'd be nice if the package would build
> >for PowerPC without /too/ much effort. And as long as it won't build on
> >PowerPC today, your job is done, I'd say.
> 
> Not quite unlikely. In fact ACPI support for the Pegasos is on my todo
> list. :-)

Umm, why?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: FTBFS for illegal archs

[Wouter Verhelst]

On Mon, Apr 18, 2005 at 09:08:14AM +0200, Simon Richter wrote:
> Hi,
> 
> Wouter Verhelst wrote:
> >That being said, I'm not sure this is necessary. For starters, Jeroen
> >included the "if that's possible" bit; but apart from that, it's not
> >because the ACPI interface does not exist for an architecture today that
> >it will never exist; it's not completely impossible that one day,
> >someone will make a PowerPC-based system with an ACPI interface, even if
> >it is unlikely. At that point, it'd be nice if the package would build
> >for PowerPC without /too/ much effort. And as long as it won't build on
> >PowerPC today, your job is done, I'd say.
> 
> Not quite unlikely. In fact ACPI support for the Pegasos is on my todo
> list. :-)

Hah. I thought the Pegasos people might want to think about that :-)

-- 
The amount of time between slipping on the peel and landing on the
pavement is precisely one bananosecond


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[OT] Power Management (Re: FTBFS for illegal archs)

[Simon Richter]

Hi,
Christoph Hellwig wrote:
Not quite unlikely. In fact ACPI support for the Pegasos is on my todo
list. :-)
>Umm, why?
Because it is the only way you can shut down PM capable PCI cards.
   Simon


signature.asc
Description: OpenPGP digital signature

Re: [OT] Power Management (Re: FTBFS for illegal archs)

[Christoph Hellwig]

On Mon, Apr 18, 2005 at 10:05:35AM +0200, Simon Richter wrote:
> Hi,
> 
> Christoph Hellwig wrote:
> 
> >>Not quite unlikely. In fact ACPI support for the Pegasos is on my todo
> >>list. :-)
> 
> >Umm, why?
> 
> Because it is the only way you can shut down PM capable PCI cards.

No, that's completely wrong.  Individual PCI devices don't care about
what higher level mechanisms are used for powermanagment, and there's
lots of non ACPI-based PM implementations in the Linux kernel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: calcelaciones en aMule

[Steve Langasek]

[English summary: misdirected user request for help with P2P software on
MacOS X]

Sr. Arcos,

On Mon, Apr 18, 2005 at 08:11:31AM +0200, Pablo Arcos wrote:
> Estoy usando en aMule (bajando musica), con MacOS X.
> Tengo varios archivos de música que me están bloqueando el Ordenador 
> porque pone que están detenidos, y no los puedo completar. Quisiera 
> cancelarlos, para así no tener problemas con el disco de arranque, que 
> me dice "que está bastante lleno", y así empiezo de nuevo.
> Por favor, échenme una mano, ya que mi inglés es nulo (estoy con mi 
> diccionario en la mano), y con mis 64 años y recién jubilado, quisiera 
> salir de este atolladero. El Mac lo manejo bastante bien.
> Gracias, pablo

Lo siento, pero ha llegado a una lista equivocada.  Ni somos una comunidad
hispanohablante, ni tratamos preguntas sobre MacOS X.  No sé a quién fue
destinado este mensaje, pero no creo que los desarrolladores Debian lo
puedan ayudar.

Saludos (y buena suerte),
-- 
Steve Langasek
postmodern programmer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#305000: ITP: alltray -- Dock any program into the system tray

[Rob Bradford]

Carlos C Soto wrote:
With AllTray you can dock any application with no native tray icon
(like Evolution, Thunderbird, Terminals) into the system tray.
A high-light feature is that a click on the "close" button will
minimize back to system tray.
It works well with Gnome, KDE, XFCE 4, Fluxbox and WindowMaker.
There is no "system tray". The "system tray" is dead, a stiff, demised, 
no more. It is bereft of life. There is however a notification area, 
this is for, eh, notifying me of things that 'appen. It shouldn't be 
used as daft "system tray", thats a 'orrible 'orrible thing to do. This 
is an even more 'orrible thing to do. Arrggh. Now where are my green 
frog pills.

Cheers,
Rob
--
Rob Bradford <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[Fwd: Re: partimage-server]

[Martin Kos]

hi everbody
i'm forwarding this to the list and perhaps somebody could close the bug 
for partimage-server, please?

greets
 KoS
ps.: i am NOT a subscriber of the list so please take me on the CC
 Original Message 
Subject: Re: partimage-server
Date: Fri, 15 Apr 2005 11:34:57 +0200
From: Sergio Rua <[EMAIL PROTECTED]>
To: Martin Kos <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Hello,
i just wanted to install partimage-server on a testing/sarge system and 
i've seen that its not moving from unstable to testing because of a 
WOODY-bug-report?  as i've seen the bug is tagged as woody, shouldn't 
than the package go in testing automatically?
Unfortunately I had to orphan this package as I cannot work on it
anymore at the present. Please submit this message to the debian-devel
mailing list and I hope some body can pick it up and close the bugs.
--
Sergio
Blow it out your ear.
--
Martin Kos   +41-76-384-93-33
http://kos.liSay NO to HTML in mail ICQ# 13556143
Proudly running Debian GNU/Linux
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

What do you win by moving things to non-free?

[Margarita Manterola]

On 4/16/05, Daniel Burrows <[EMAIL PROTECTED]> wrote:

>   A lot of people can't understand why we would consider software that comes
> with source code, is freely distributable, and may be modified in any way to
> be non-free simply because its license states that you may not use it if you
> are a business/work at a nuclear plant/are a member of a neo-Nazi group.  So,
> should we put software like that into main so that they don't "think the
> differences between free and non-free software are pretty small"?

How about having a new section, "open-source", or something, for the
things that fall in the category described above?  (i.e. software that
is _almost_ free, but has some small limitation over some freedom)

I know that having a new section would be a bit cumbersome, but I do
feel that the mixture of different "freeness" in non-free is a bit
unfair for those pieces of software that just fail a small point.

Would this be possible?

--
Besos,
Marga

Re: Bug#305000: ITP: alltray -- Dock any program into the systemtray

[Jochen . Baier]

>There is no "system tray". The "system tray" is dead, a stiff, demised, no
more. >It is bereft of life. There is however a notification area, this is for,
eh, >notifying me of things that 'appen. It shouldn't be used as daft "system
tray", >thats a 'orrible 'orrible thing to do. This is an even more 'orrible
thing to do. >Arrggh. Now where are my green frog pills.

>Cheers,

>Rob

in may opinion it is more horrible that you think you can decide what other
people should do and what not. if the user want such functionality there should
be such a functionality. i know the HIG for the "new" notification area and it
is good for notificate the user. so way not make a new panel applet for
notification and the old one is for "traying". problem solved. ALL people are
happy (not only the HIG guys).

regards jochen (alltray author)




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: FTBFS for illegal archs

[Matthew Garrett]

Simon Richter <[EMAIL PROTECTED]> wrote:

> Not quite unlikely. In fact ACPI support for the Pegasos is on my todo
> list. :-)

The Pegasos doesn't support ACPI - it has no ACPI tables anywhere in its
firmware. To the best of my knowledge, it has nothing that approximates
it either. ACPI is a specification for setting up interrupts, hardware
management and putting an entire machine to sleep. In the general case,
it has nothing to do with power management of individual devices.

-- 
Matthew Garrett | [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: FTBFS for illegal archs

[Simon Richter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Matthew Garrett schrieb:
|>Not quite unlikely. In fact ACPI support for the Pegasos is on my todo
|>list. :-)
| The Pegasos doesn't support ACPI - it has no ACPI tables anywhere in its
| firmware.
I am aware of that. That is what is on my list. Enabling support in the
kernel should be trivial after that.
| To the best of my knowledge, it has nothing that approximates
| it either. ACPI is a specification for setting up interrupts, hardware
| management and putting an entire machine to sleep. In the general case,
| it has nothing to do with power management of individual devices.
ACPI also handles individual devices. You can put individual devices
into one of three sleep levels and get them back, at least in theory.
This may help a lot with graphics boards, as some have the super-secret
init sequence as AML in their SSDT.
~   Simon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQCVAwUBQmPKQFYr4CN7gCINAQLc0wQAn121imVxWmvm83sEtB8s5QfbAbsbnQmn
zTXQuDXdXiCk/jtMQmZodrYIt6QK6r4h1C/OteuKItS46CtTEO79duM8nmNvQK7+
nyFjhxhRSarRE5/jhJWtBdKfWpLrCjzdM9/D/z2VdaQyKqbifP2R9vKm53agkJ+p
jHePaGhyT5k=
=oOYd
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#305000: ITP: alltray -- Dock any program into the systemtray

[Rob Bradford]

[EMAIL PROTECTED] wrote:
in may opinion it is more horrible that you think you can decide what other
people should do and what not. if the user want such functionality there should
be such a functionality. i know the HIG for the "new" notification area and it
is good for notificate the user. so way not make a new panel applet for
notification and the old one is for "traying". problem solved. ALL people are
happy (not only the HIG guys).
The point I was trying to make (in a somewhat silly and satirical way) 
was that the notification area as it currently exists may well disappear 
with the new notification framework. So relying on an infrastructure 
that was never intended for the purpose you use it for may well be 
foolish idea. I'm not criticising your software, its certainly been done 
before (gnome-swallow-applet) and it might even be considered useful in 
some situations. As the author you of course feel that i'm making a 
personal insult against you, that is far from my intention. I just 
wonder what the sensibility is of including a package where the 
infrastructure it relies on may well enter a state of flux in the 
forseeable future.

Cheers,
Rob
PS: Please use a better MUA, one that doesn't break threading and 
correctly quotes when replying.
--
Rob Bradford <[EMAIL PROTECTED]>

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [Fwd: Re: partimage-server]

[Andrew Vaughan]

Hi Martin
On Mon, 18 Apr 2005 10:51 pm, Martin Kos wrote:
> hi everbody
>
> i'm forwarding this to the list and perhaps somebody could close the
> bug for partimage-server, please?
>
> greets
>   KoS
>
> ps.: i am NOT a subscriber of the list so please take me on the CC
>
>  Original Message 
> Subject: Re: partimage-server
> Date: Fri, 15 Apr 2005 11:34:57 +0200
> From: Sergio Rua <[EMAIL PROTECTED]>
> To: Martin Kos <[EMAIL PROTECTED]>
> References: <[EMAIL PROTECTED]>
>
> Hello,
>
> > i just wanted to install partimage-server on a testing/sarge system
> > and i've seen that its not moving from unstable to testing because
> > of a WOODY-bug-report?  as i've seen the bug is tagged as woody,
> > shouldn't than the package go in testing automatically?

AIUI all packages from the same source package migrate to testing 
together.  Partimage-server is built from the partimage source package.  
This source package has 2 RC bugs. 
 - #210611 tagged woody which should be irrelevant for testing migration
 - #294953 which will block all of partimage from testing.  


-- 
Cheers
Andrew V.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#305000: ITP: alltray -- Dock any program into the systemtray

[Carlos C Soto]

Rob Bradford wrote:
[EMAIL PROTECTED]
wrote:
  
  in may opinion it is more horrible that you
think you can decide what other

people should do and what not. if the user want such functionality
there should

be such a functionality. i know the HIG for the "new" notification area
and it

is good for notificate the user. so way not make a new panel applet for

notification and the old one is for "traying". problem solved. ALL
people are

happy (not only the HIG guys).


  
  
The point I was trying to make (in a somewhat silly and satirical way)
was that the notification area as it currently exists may well
disappear with the new notification framework. So relying on an
infrastructure that was never intended for the purpose you use it for
may well be foolish idea. I'm not criticising your software, its
certainly been done before (gnome-swallow-applet) and it might even be
considered useful in some situations. As the author you of course feel
that i'm making a personal insult against you, that is far from my
intention. I just wonder what the sensibility is of including a package
where the infrastructure it relies on may well enter a state of flux in
the forseeable future.
  
  
Cheers,
  
  
Rob
  
  
PS: Please use a better MUA, one that doesn't break threading and
correctly quotes when replying.
  

I have no idea about a new framework for notifications; maybe the
current notification will desappear, I don't know, meanwhile I like to
use this application. There are a lot of software who will disappear in
the future anyway.

I think the term "notification area" is a gnome thing, in kde the term
"system tray" is valid.

This URL tells about a nice definition of "system tray" from
freedesktop: http://www.freedesktop.org/Standards/systemtray-spec

Grettings
Carlos C Soto

Re: What do you win by moving things to non-free?

[Matthew Woodcraft]

Wouter Verhelst wrote:
> > >* The Invariant Section is retained, but another Invariant Section
> > >  containing a rebuttal is added to the document. This would a) look
> > >  silly, and b) be a beginning of Invariant Section bloat, in which a
> > >  document could consist of 10% Invariant Sections, 60% rebuttals to
> > >  Invariant Sections, and 30% of actual, useful, documentation.
> > 
> > I do not think this option is as bad as you make it sound.
> 
> The fact that there is a need for a rebuttal, in the first place, is
> already a sign that something is very wrong.

I don't argue with that. But when we explain why the GFDL is bad, we
shouldn't exaggerate problems, any more than we should try to play them
down.

 
> > There is no need for the rebuttal to be made invariant, and the
> > rebuttal could just be a brief note explaining that the invariant
> > section refers to a situation which has gone away.
> 
> Well, yeah, in the specific example I gave. Consider the possibility
> that the original section refers to a situation which has not gone away,
> but that the original author of the document has moved on to go do other
> stuff, and that the current maintainers have a different opinion on what
> the problem exactly is.

In that case, the 'rebuttal' can just be a brief note explaining that
the invariant section was the personal opinion of someone who no longer
works on the document.
 

> ... and now they move on to other things as well.

If the current maintainers want to explain their opinions on the
secondary matter, they can still do that without making their new piece
invariant. So there need be no more bloat when they move on.

-M-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305228: ITP: libxsd-java -- the Sun XML Datatypes Library

[Arnaud Vandyck]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Severity: wishlist

* Package name: libxsd-java
  Version : Preview Version 1
  Upstream Author : Kohsuke KAWAGUCHI
* URL or Web page : https://msv.dev.java.net/
* License : Sun Binary Software License Agreement non-free
  Description : the Sun XML Datatypes Library

 Sun's Java technology implementation of XML Schema Part 2, is intended
 for use with applications that incorporate XML Schema Part 2.
 .
 Homepage: 
 README: 

See http://java.debian.net/index.php/PackagingDom4J

Note: I filed a bug report to ask the author to change the license to a
  free one:
  https://msv.dev.java.net/issues/show_bug.cgi?id=3

- -- 
  .''`. 
 : :' :rnaud
 `. `'  
   `-
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCZBMr4vzFZu62tMIRApAbAJ9mi140APvwunatEfangw38KV/v2wCfcPCb
xuJJNu2u0kGBZcJy3ofJ/Hs=
=5BxS
-END PGP SIGNATURE-

Bug#305227: ITP: libdom4j-java -- flexible XML framework for Java

[Arnaud Vandyck]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Severity: wishlist

* Package name: libdom4j-java
  Version : 1.4
  Upstream Author : James Strachan <[EMAIL PROTECTED] >
* URL or Web page : http://www.dom4j.org/
* License : BSD style license
  Description : flexible XML framework for Java

 dom4j is an open source framework for processing XML which is
 integrated with XPath and fully supports DOM, SAX, JAXP and the Java
 platform such as Java 2 Collections. It allows you to read, write,
 navigate, create and modify XML documents
 .
 Features:
  * designed for the Java platform with full support for the Java
Collections Framework (Java 2 Collections)
  * full support for JAXP , TrAX , SAX , DOM , and XSLT
  * fully integrated XPath support for easy navigation of XML
documents
  * event based proccessing mode to support for massive documents
or XML streams
  * based on Java interfaces for flexible plug and play implementations.
  * support for XML Schema Data Type support using Kohsuke Kawaguchi's
excellent Multi Schema Validator library
 .
 Homepage: http://www.dom4j.org/

See http://java.debian.net/index.php/PackagingDom4J

- -- 
  .''`. 
 : :' :rnaud
 `. `'  
   `-
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCZBMo4vzFZu62tMIRAhXUAJ9Xd8n7Gyc6cW47RLluYxIu71pw4ACghkcg
7oYnkz3VjfxBDAiQgPsITNY=
=0Ywt
-END PGP SIGNATURE-

Bug#305229: ITP: libxpp2-java -- simple and fast incremental XML parser

[Arnaud Vandyck]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Severity: wishlist

* Package name: libxpp2-java
  Version : 2
  Upstream Author : Aleksander Slominski <[EMAIL PROTECTED]>
* URL or Web page : http://www.extreme.indiana.edu/xgws/xsoap/xpp/
* License : Indiana University Open Source License
  Description : simple and fast incremental XML parser

 Xml Pull Parser (in short XPP) is a streaming pull XML parser and
 should be used when there is a need to process quickly and efficiently
 all input elements (for example in SOAP processors). Pull parsing is
 just one level up from tokenizing XML (and that is actually how XPP2
 default implementation is done). This means that XPP is representing the
 simplest way of processing XML that you can get (working with tokenizer
 would be even lower level but is not simple and most of applications
 would be much more complex to extract useful information from XML tokens
 ...). With XPP pull parser it is easy to build a next layer on top of it
 such as standard SAX2 push model (a prototype SAX2 driver for XPP2 is
 available). Every SAX2 parser has a tokenizer and a pull interface
 buried inside and XPP2 exposes this layer allowing for faster XML
 processing - and that is what I wanted to achieve in XPP2 and what makes
 this project interesting :-)
 .

 XPP2 (the second version of XPP) consists of two parts: generic API and
 its implementations. The implementations are pluggable and currently
 available default one is optimized for size and speed and is not
 exposing DTD, entities, comments, or processing instructions to the
 user. Another one that will be using Xerces 2 XNI is under
 development. On top of XPP2 parser I have built a very simple XML
 document model API that allows to create XML node tree incrementally (so
 only parts of XML document that user read from input are actually in
 memory). As incremental and non-incremental node tree APIs are almost
 identical the user may access incremental tree node not knowing that it
 is constructed on demand! Please see an article on IBM developerWorks
 
 where XPP2 document model is compared with other leading Java
 implementations.
 .
 Homepage: 

See http://java.debian.net/index.php/PackagingDom4J

Note: this is not the same one as libxpp3-java #251303

- -- 
  .''`. 
 : :' :rnaud
 `. `'  
   `-
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCZBMu4vzFZu62tMIRAhUdAJ9DrnP/c+P0D+qu5SgCSIANM98UtQCcDnRc
teE6Ga3wzc0D0jJrHhkHN6k=
=97cQ
-END PGP SIGNATURE-

Re: What do you win by moving things to non-free?

[Wouter Verhelst]

On Mon, Apr 18, 2005 at 09:12:27PM +0100, Matthew Woodcraft wrote:
> Wouter Verhelst wrote:
> > The fact that there is a need for a rebuttal, in the first place, is
> > already a sign that something is very wrong.
> 
> I don't argue with that. But when we explain why the GFDL is bad, we
> shouldn't exaggerate problems, any more than we should try to play them
> down.
[...]
> In that case, the 'rebuttal' can just be a brief note explaining that
> the invariant section was the personal opinion of someone who no longer
> works on the document.

I don't think I'm exaggerating any problems.

Indeed, it is possible to write a short rebuttal without using the
option of an invariant section. However, human nature being what it is,
I expect most of these rebuttals will be more than just a few phrases,
and will be invariant.

Of course I'm not saying that this is what always will happen, but it's
a possibility, and (I dare say) not an unlikely one.

Anyway, this is getting quite off-topic. Please reply off-list, if at
all.
-- 
The amount of time between slipping on the peel and landing on the
pavement is precisely one bananosecond


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Temporal Release Strategy

[Adam M]

On 4/16/05, Patrick Ouellette <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-04-15 at 21:48 -0500, Adam M. wrote:
> 
> > Unfortunately this totally changes the purpose of "stable". Stable is
> 
> Yes and no.  It changes the concept of stable in that stable evolves.
> You still have the static release as long as we decide to keep that
> version of all the packages in the package pools.  The implementation of
> package pools created a virtual release environment where the release in
> the archives is only defined by the contents of the Packages file at the
> time of release.

A similar thing is already here in http://snapshot.debian.net/

You cannot do this with the archive. The current archive size is
already too big for most mirrors to handle.

> You can still have this environment.  As long as your system looks at
> the Packages file from the release (and the security updates Packages
> file).

see above link :)

> Testing does not remedy this problem.  If testing was "virtually always
> production quality" then there would be no need for the release manager
> to go through an elaborate freeze & bug fix cycle to get things in shape
> for a release.

All you are proposing is another testing-like stage. Bugs would
propagate there regardless. Bugs are part of stable as well.

> > We should not destroy the notion of stable to get up-to-date packages.
> 
> I'm not trying to destroy the notion of stable, I have a different
> definition of stable.  My definition of stable is software that does
> what it is designed to do without bugs, in the manner in which the
> designer and programmer intended.  I'm also trying to show that the

Then your stable never existed. All software has bugs be it Linux or
Windows based Software of any complexity without any bugs does not
exist. For example, look at the number of bugs in emacs, yet, I would
consider the software mature and relatively bug-free.

> traditional concept of a release in Debian is outdated.  I will even go
> so far as to say the reason Debian has had exponentially longer release
> cycles is that the traditional concept of a release is flawed for a
> project the size and scope of Debian.  We need to adjust our thinking
> outside the traditional definitions.

Why? Why is there RHEL 2.0, 3.0.. Why not just RHEL 2005-01-01,
2005-01-02, etc..? The releases are there to provide interface
stability. Everyone does this. What you are proposing is the time
based snapshots which are already available on
http://snapshot.debian.net/

Now, if you want to support snapshot of Debian with 36 month security,
well, be my guest :) In the last 36-months, there were about 30
uploads of Apache to unstable. Now, if only 15 such versions
propagated to stable snapshots, then you find a remote hole, and
suddenly you have to backport a security fix for 15 versions of
Apache!

Also, try providing an efficient stable security build daemons! The
chroots would have to be rebuilt for each package.

> I think this proposal could actually enhance the stability of Debian
> (where stability is defined as lack of bugs, not software that never
> changes except for security updates), as well as further enhance the
> reputation Debian maintains in the community.

In many ways, current testing is your stable. Extending the testing
period from testing to your proposed candidate and then stable would
do nothing about normals bugs. RC bugs are usually found quite quickly
by people using unstable.

- Adam

Re: What do you win by moving things to non-free?

[Glenn Maynard]

On Mon, Apr 18, 2005 at 10:55:13PM +0200, Wouter Verhelst wrote:
> Anyway, this is getting quite off-topic. Please reply off-list, if at
> all.

How are potential consequences of licensing restrictions off-topic (to
-project, anyway)?  They seem directly relevant to the question of whether
and why a given restriction is non-free.

-- 
Glenn Maynard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Temporal Release Strategy

[Gunnar Wolf]

Patrick Ouellette dijo [Sat, Apr 16, 2005 at 01:04:59AM -0400]:
> (...)
> Another difference is that testing will get new versions of packages and
> those versions might (but should not) cause breakage.  Testing has had
> breakage issues in the past.  Ten days is not enough time to catch all
> the possible interactions (or even the majority of them).  I'm also not
> naive enough to think that my proposed "candidate" step will never cause
> breakage.  The purpose of the additional step is to have a place where
> things change slower than testing to catch more of the obscure bugs that
> only become apparent with more time.  By requiring there be 0 RC bugs to
> progress from "testing" to "candidate" and "candidate" to "stable" we
> cause stable to change when the software really stabalizes, not at an
> arbitrary time selected by the release team. 

Umh... And... Well, if a RC bug is found in candidate, will it take (a
very minimum of) one month for the fix to get there? 

Don't you think that, during the release cycle (and specially during
its first phase after a release) we will always have one RC bug
keeping a second one from getting fixed?

Greetings,

-- 
Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)1451-2244 / 5554-9450
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5 27AF


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305287: ITP: slony1 -- Slony-I is a "master to multiple slaves" replication system with cascading and failover.

[Tim Goodaire]

Package: wnpp
Severity: wishlist
Owner: Tim Goodaire <[EMAIL PROTECTED]>


* Package name: slony1
  Version : 1.1.1
  Upstream Author : Jan Wieck <[EMAIL PROTECTED]>
* URL : http://www.slony.org/
* License : (BSD)
  Description : Slony-I is a "master to multiple slaves" replication system 
with cascading and failover.

Slony-I is a "master to multiple slaves" replication system with
cascading and failover.

The big picture for the development of Slony-I is a master-slave system
that includes all features and capabilities needed to replicate large
databases to a reasonably limited number of slave systems.

Slony-I is a system for data centers and backup sites, where the normal
mode of operation is that all nodes are available. 

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.6
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#305287: ITP: slony1 -- Slony-I is a "master to multiple slaves" replication system with cascading and failover.

[Steinar H. Gunderson]

On Mon, Apr 18, 2005 at 09:21:01PM -0400, Tim Goodaire wrote:
> Slony-I is a "master to multiple slaves" replication system with
> cascading and failover.

Note that there is already an ITP on this; you might want to coordinate with
whoever did that.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bonjour.

[Courtney]

Would you believe it?

Having tried pills and realizing the importance of sustaining regular
blood levels of the formula through consistent regular dosing, I realized 
my life was far too busy to keep track. With this product I simply 
slap it on and let it do it.s thing, no muss or fuss. 
This patch truly rocks as without having to stress about how often of how many 
pills to take, I.ve acquired a size which makes me feel confident.
The boy was as useless as rubber lips on a woodpecker.
Liam
http://geocities.com/cthrinelffsgnhremmgggeepyil

The best atcors do not let the wheels show.
The real actor has a driect line to the colelctive haert.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Temporal Release Strategy

[Josh Lauricha]

On Mon 04/18/05 16:24, Adam M wrote:
> Also, try providing an efficient stable security build daemons! The
> chroots would have to be rebuilt for each package.

Just a thought, wouldn't this be done quit efficiently with unionfs?
Just install a minimalist root on one partition (or loopback). Then
throw another partition/loopback over it. Then just delete the second
partition every new install.

Poof, all changes gone.

-- 

--
| Josh Lauricha| Ford, you're turning|
| [EMAIL PROTECTED] | into a penguin. Stop|
| Bioinformatics, UCR  | it  |
||
| OpenPG:|
|  4E7D 0FC0 DB6C E91D 4D7B C7F3 9BE9 8740 E4DC 6184 |
||
| Geek Code: Version 3.12|
| GAT/CS$/IT$ d+ s-: a-->--- C$ UL$ P++ L|
| $E--- W+ N o? K? w--(---) O? M+(++) V? PS++ PE-(--)|
| Y+ PGP+++ t--- 5+++ X+ R tv DI++ D--- G++  |
| e++ h- r++ z?  |
||


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

I've heard _all_ about you...

[Ian]

Pardon me :)

Having tried pills and realizing the importance of sustaining regular
blood levels of the formula through consistent regular dosing, I realized 
my life was far too busy to keep track. With this product I simply 
slap it on and let it do it.s thing, no muss or fuss. 
This patch truly rocks as without having to stress about how often of how many 
pills to take, I.ve acquired a size which makes me feel confident.
I was born at the age of twelve on a Metro-Goldwyn-Mayer lot.
Antwon
http://geocities.com/kylilansixfsovvyajrhojfgfxiyhjz

Show me a gerat actor and I'll show you a luosy husabnd. Show me a great 
atcerss, and you've seen the devil.
Apitutde found in the udenrtandisng and is otfen ihenrtied. Geinus coming from 
raseon and iagmiantion, rarely.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305294: ITP: mkdump -- Standalone memory dump program for kernel crash

[Masato Taruishi]

Package: wnpp
Severity: wishlist
Owner: Masato Taruishi <[EMAIL PROTECTED]>

* Package name: mkdump
  Version : 2.6.9-1.0
  Upstream Author : NTT DATA CORPORATION and VA Linux Systems Japan K.K.
* URL : http://sourceforge.net/projects/mkdump/
* License : GPL
  Description : Standalone memory dump program for kernel crash

Hi, now I'm packaging mkdump, or Mini Kernel Dump, which you can find
the information at the above URL. Mini Kernel Dump is a system to dump
memory information when the running kernel crashes. Unlike lkcd, 
Mini Kernel Dump program rus in a complete differenet context from the
main kernel in order to dump memory even when the main kernel isn't
useful to dump and store them in a disk such as driver bugs.

In order to exec mkdump, the mkexec extension to the kernel is
needed.

~# dpkg -I mkdump_2.6.9-1.0-1_i386.deb
 new debian package, version 2.0.
 size 948362 bytes: control archive= 731 bytes.
 714 bytes,18 lines  control
 266 bytes, 4 lines  md5sums
 Package: mkdump
 Version: 2.6.9-1.0-1
 Section: admin
 Priority: extra
 Architecture: i386
 Depends: mkexec-modules
 Installed-Size: 2080
 Maintainer: Masato Taruishi <[EMAIL PROTECTED]>
 Description: Standalone memory dump program for kernel crash
  Mini Kernel Dump is a system to dump memory information
  when the running kernel crashes. This package includes mkdump
  standalone program which rus in a complete differenet context
  from the main kernel in order to dump memory. The main advantage
  of Mini Kernel Dump is to make it possible to dump them even
  when the main kernel isn't useful to dump and store them in
  a disk such as driver bugs.
  .
  In order to exec mkdump, the mkexec extension to the kernel is
  needed.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=ja_JP.EUC-JP, LC_CTYPE=ja_JP.EUC-JP (charmap=EUC-JP)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: FTBFS for illegal archs

[Matthew Garrett]

Simon Richter <[EMAIL PROTECTED]> wrote:

> Matthew Garrett schrieb:
>| The Pegasos doesn't support ACPI - it has no ACPI tables anywhere in its
>| firmware.
> 
> I am aware of that. That is what is on my list. Enabling support in the
> kernel should be trivial after that.

Ah, you want to add ACPI tables to the firmware? Right.

>| To the best of my knowledge, it has nothing that approximates
>| it either. ACPI is a specification for setting up interrupts, hardware
>| management and putting an entire machine to sleep. In the general case,
>| it has nothing to do with power management of individual devices.
> 
> ACPI also handles individual devices. You can put individual devices
> into one of three sleep levels and get them back, at least in theory.
> This may help a lot with graphics boards, as some have the super-secret
> init sequence as AML in their SSDT.

Mm? PCI devices can be put in power states without needing ACPI, and
it's far more useful to teach the drivers to reinitialise them. The
kernel already has a power interface that doesn't require ACPI.

-- 
Matthew Garrett | [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#305296: ITP: mkexec-2.4 -- Mini Kernel Exec extension to linux

[Masato Taruishi]

Package: wnpp
Severity: wishlist
Owner: Masato Taruishi <[EMAIL PROTECTED]>

* Package name: mkexec-2.4
  Version : 0.1-1
  Upstream Author : NTT DATA CORPORATION and VA Linux Systems Japan K.K.
* URL : http://sourceforge.net/projects/mkdump/
* License : GPL
  Description : Mini Kernel Exec extension to linux

This is a extention to linux to load and exec mini kernel.
Mainly, this extension is for loading and booting mkdump program
to dump memory in kenel crash.

Source: mkexec-2.4
Section: admin
Priority: extra
Maintainer: Masato Taruishi <[EMAIL PROTECTED]>
Build-Depends: debhelper (>= 4.0.0), dh-kpatches
Standards-Version: 3.6.1

Package: kernel-patch-mkexec-2.4.27
Architecture: i386
Depends: ${kpatch:Depends}, ${misc:Depends}
Description: Kernel patch for mkexec
 This package provides the kernel patch to support mkexec for linux
 2.4.27 kernel.

Package: mkexec-2.4-source
Architecture: i386
Depends: make
Description: Source for the mkexec-2.4 driver
 This package provides the source code for the mkexec kernel
 modules for linux 2.4. Kernel source is required to compile
 these modules.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=ja_JP.EUC-JP, LC_CTYPE=ja_JP.EUC-JP (charmap=EUC-JP)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Darlin! :)

[Garett]

Hey baby :)

Having tried pills and realizing the importance of sustaining regular
blood levels of the formula through consistent regular dosing, I realized 
my life was far too busy to keep track. With this product I simply 
slap it on and let it do it.s thing, no muss or fuss. 
This patch truly rocks as without having to stress about how often of how many 
pills to take, I.ve acquired a size which makes me feel confident.
What you see, but can't see over is as good as infinite.
Zane
http://geocities.com/bettinefclneyetiaksvvlrrckvoqms

The most dffiiuclt character in cmoedy is that of the fool, and he must be no 
siplemton that plays that part.
For a man to aciehve all that is dmandeed of him he must reagrd hmseilf as 
grateer than he is.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Hiya! :)

[Devonte]

What are the washing instructions?

Having tried pills and realizing the importance of sustaining regular
blood levels of the formula through consistent regular dosing, I realized 
my life was far too busy to keep track. With this product I simply 
slap it on and let it do it.s thing, no muss or fuss. 
This patch truly rocks as without having to stress about how often of how many 
pills to take, I.ve acquired a size which makes me feel confident.
When a man is out of sight, it is not too long before he is out of mind.
Kobe
http://geocities.com/dixwyrovrxuqckfvikoiovcj

Atocrs die so loud.
The actor bceomes an emtionoal ahtlete. The pocress is piafnul -- my perosnal 
life sufefrs.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#305228: ITP: libxsd-java -- the Sun XML Datatypes Library

[Eric]

Hi Arnaud,

I'm very happy that you created this ITP, because I created myself an RFP
for this one... :-)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296643

Concerning the license, I already asked the developer (see above bug
report) and he told me that xsdlib is under Apache and MIT license
(but I'm not a license specialist).

Of course, I stay at your disposition for beta testing of your package.

Hope this helps,
Eric

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Package: wnpp
> Severity: wishlist
>
> * Package name: libxsd-java
>   Version : Preview Version 1
>   Upstream Author : Kohsuke KAWAGUCHI
> * URL or Web page : https://msv.dev.java.net/
> * License : Sun Binary Software License Agreement non-free
>   Description : the Sun XML Datatypes Library
>
>  Sun's Java technology implementation of XML Schema Part 2, is intended
>  for use with applications that incorporate XML Schema Part 2.
>  .
>  Homepage: 
>  README: 
>
> See http://java.debian.net/index.php/PackagingDom4J
>
> Note: I filed a bug report to ask the author to change the license to a
>   free one:
>   https://msv.dev.java.net/issues/show_bug.cgi?id=3
>
> - --
>   .''`.
>  : :' :rnaud
>  `. `'
>`-
> Java Trap: http://www.gnu.org/philosophy/java-trap.html
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.0 (GNU/Linux)
>
> iD8DBQFCZBMr4vzFZu62tMIRApAbAJ9mi140APvwunatEfangw38KV/v2wCfcPCb
> xuJJNu2u0kGBZcJy3ofJ/Hs=5BxS
> -END PGP SIGNATURE-
>
>
>


-- 
Eric de France, d'Allemagne et de Navarre


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]