Hi,
Jérôme Marant wrote:
- the list of posts to be declassified will be made available to
developers two weeks before publication, so that the decisions
Two weeks is too short to review, IMO.
I didn't read that as a hard time limit between announcement and
publication, but rather as t
Kevin Locke <[EMAIL PROTECTED]> wrote:
> Fundamentally, our goal is to create an architecture-independent,
> power-system-independent, and power-daemon-independent system to handle
> power-related events (e.g. lid close, battery events). This will likely
> happen by hooks from the power daemons (
On Fri, 02 Dec 2005, Matthew Garrett wrote:
> To a large extent, this sort of work is currently being done in HAL. Is
> there any need to create another level of abstraction, or should we just
> work on that? It also sounds (though I'm not certain) like you're
Can I tell HAL to just handle power m
Package: wnpp
Severity: wishlist
Owner: "Rogério Brito" <[EMAIL PROTECTED]>
* Package name: ppower4
Version : 0.9.4
Upstream Author : Klaus Guntermann, <[EMAIL PROTECTED]>
* URL :
http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html
* License
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> Can I tell HAL to just handle power management instead of touching anything
> else, and get it to do the right thing in a headless, GUIless server
> environment? Can I do that with standard, system-wide configuration files?
HAL on its own
On Fri, Dec 02, 2005 at 12:53:51AM +0100, Alexander Schmehl wrote:
> * Peter Samuelson <[EMAIL PROTECTED]> [051202 00:33]:
>
> > This has been suggested before; the standard counterargument is "what
> > about closing an ITP?"
>
> Then why not make a check (source package of bug and changelog are
On Fri, Dec 02, 2005 at 10:45:31AM +1100, Matthew Palmer wrote:
>
> Your mission, should you choose to accept it, is dig through the Perl code
> in merkel:/org/bugs.debian.org/scripts and work out how to add this
> functionality.
>
> - Matt
Maybe it is a good thing that I am neither a DD (yet)
On Fri, 2 Dec 2005, [UTF-8] Rogério Brito wrote:
* Package name: ppower4
Version : 0.9.4
Upstream Author : Klaus Guntermann, <[EMAIL PROTECTED]>
* URL :
http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html
PPower4 is a post-processor for making PDF
On Fri, 2005-12-02 at 10:47 +, Matthew Garrett wrote:
> Kevin Locke <[EMAIL PROTECTED]> wrote:
>
> > Fundamentally, our goal is to create an architecture-independent,
> > power-system-independent, and power-daemon-independent system to handle
> > power-related events (e.g. lid close, battery
Hi,
Matthew Palmer wrote:
Your mission, should you choose to accept it, is dig through the Perl code
in merkel:/org/bugs.debian.org/scripts and work out how to add this
functionality.
You can use "package foo" as a command to control@ to tell it ignore
everything that does not affect bugs
My biggest problem with all this is that it's gonna mean a lot of work -
for the 'declassifying team' and for people who want to be bothered
about commenting on the process is respect of particular email. Thats
time that I feel could be better spent.
I do understand the motives...
--
Paul
On Thu
Kevin Locke <[EMAIL PROTECTED]> wrote:
> However, I realize that the
> GNOME Power Manager[1], and likely a KDE equivalent, already handles
> several of the tasks normally associated with power-management, so
> perhaps there is no need for another program to be handling events.
>
> What are your (
On Fri, 2 Dec 2005 12:35:28 +1000, Anthony Towns said:
> (Followups to -vote)
> On Fri, Dec 02, 2005 at 08:30:37AM +1100, Robert Collins wrote:
>> The primary reason for this is that the existing messages were sent
>> to debian-private with an expectation of privacy.
> As Matthew pointed out in
On Fri, 02 Dec 2005, Kevin Locke wrote:
> What are your (or anyone else's) thoughts about the value of a daemon to
> invoke scripts based on the power-related HAL events? Is this
> unnecessary given the function of the GNOME Power Manager and
> equivalents, or would it have enough value to be wort
On Thu, Nov 24, 2005 at 06:45:58PM +, Ian Jackson wrote:
> So the best idea is indeed for
> downstream systems to have policies which are no more strict than
> upstream systems.
Would it be possible for master to make call-outs to chiark ?
would that solve the problem ?
Regards,
Paddy
--
Per
hi everybody
two friends of mine tried (separately) to install sarge using the
netinst cdrom, and failed
in both cases, the first part of the install was OK, but, after
reboot, when APT was called to upgrade the system, it stopped
claiming:
E: This installation run will require temporarily remo
* A. Mennucc:
> in both cases, the first part of the install was OK, but, after
> reboot, when APT was called to upgrade the system, it stopped
> claiming:
> E: This installation run will require temporarily removing the essential
> package e2fsprogs due to a Conflicts/Pre-Depends loop. This is
Simon Richter wrote:
> Matthew Palmer wrote:
>
>> Your mission, should you choose to accept it, is dig through the Perl
>> code in merkel:/org/bugs.debian.org/scripts and work out how to add
>> this functionality.
>
> You can use "package foo" as a command to control@ to tell it ignore
> every
On Sat, 3 Dec 2005 03:03, Kevin B. McCarty wrote:
> Simon Richter wrote:
> > Matthew Palmer wrote:
> >> Your mission, should you choose to accept it, is dig through the Perl
> >> code in merkel:/org/bugs.debian.org/scripts and work out how to add
> >> this functionality.
> >
> > You can use "pack
Kevin Locke <[EMAIL PROTECTED]> wrote:
> Interesting. I wasn't aware to what extent HAL is able to notify
> programs about power-related events. In fact, we had briefly discussed
> receiving events from HAL in addition to the power-daemons. Perhaps
> with some work, we would be able to rely com
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> 1. power management is system infrastructure. I can explain WHY it
> is so, but I don't think many people would argue that power
> management is an user-level service.
Whether a laptop suspends when you close the lid is a per-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin B. McCarty wrote:
> Simon Richter wrote:
>
>
>>Matthew Palmer wrote:
>>
>>
>>>Your mission, should you choose to accept it, is dig through the Perl
>>>code in merkel:/org/bugs.debian.org/scripts and work out how to add
>>>this functionality.
On Fri, 02 Dec 2005, Matthew Garrett wrote:
> Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
>
> > 1. power management is system infrastructure. I can explain WHY it
> > is so, but I don't think many people would argue that power
> > management is an user-level service.
>
>
That day, Florian Weimer wrote
> I've seen this as well, but attributed it to an old sarge installer
> which used "testing" instead of "sarge" (or "stable") in the installed
> sources.list file. In this case, an update from a pre-sarge testing
> snapshot (is installed by the base system) to a curr
Package: wnpp
Severity: wishlist
Owner: Sean Finney <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(explanation for why there needs to be a nagios2 given after the blurb)
Package name: nagios2
Version : 2.0 (when released)
Upstream Author : Ethan Galstad
UR
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> Nobody said the user can't give his input on how the service will behave.
> That's what the GUI is for, and what configuration files are for.
The user needs to be able to configure this without any form of
excessive privileges, which means
Hi Matt,
if that would help, I'd include a (n option that allows to) check via
bts2ldap + the attached script into dput.
That'd be less intrusive than changing the behaviour of Closes:, for
better or worse.
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
#!/usr/bin/python
import
Thomas Viehmann wrote:
> if sys.stdin.readline()[1:] not in ['y','Y']:
For added utility I might want to improve on that.
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
'What'll we drink to?' Nick asked, holding up the glass.
'Let's drink to testing,' Bill said.
'All right,'
A lintian-like test to see if the listed bugs match the package before
uploading seems more useful to me. It would have prevented this
particular problem.
Perhaps I am sloppy, but I often find it useful to close some bug in a
changelog that I might not necessary have taken the time or remembered
t
Joey Hess <[EMAIL PROTECTED]> writes:
> A lintian-like test to see if the listed bugs match the package before
> uploading seems more useful to me. It would have prevented this
> particular problem.
IMHO, is the best and easier alternative.
--
O T A V I OS A L V A D O R
On Fri, Dec 02, 2005 at 06:35:19PM +0100, A Mennucc wrote:
> That day, Florian Weimer wrote
> > By the way, your Mail-Followup-To: header is broken.
>
> thanks;some time ago I decided to abide by
> http://larve.net/people/hugo/2000/07/ml-mutt
> but I forgot to fix this account
So, shouldn't you
This message is to verify that you wish to have your
email address: debian-devel@lists.debian.org removed from the
Alharamain Sermon(english)
Subscribe Me mailing list.
You MUST click on the link below to have your address removed
from our list. This is to ensure that someone doesn't remove your
On Fri, Dec 02, 2005 at 09:26:46AM -0800, Blars Blarson wrote:
> Sorry it has taken so long for me to get you this info.
thank you very much Blars for the help, this is much apreciated.
the bus error on sparc64:
> #0 0x701029cc in inet_aton () from /lib/libc.so.6
> #1 0x00013f84 in INET_resol
Mike Hommey wrote:
> Hi
>
> As you may or may not know, I'm currently working on packaging
> xulrunner, which is ought to be the central point for all future mozilla
> technology, meaning that at more or less long term, all mozilla products
> (firefox, thunderbird, etc.) will be built on top of it
This message is to confirm the removal of your
email address: debian-devel@lists.debian.org from the
Alharamain Sermon(english)
Subscribe Me mailing list.
We're sorry to see you go!
If you feel you have received this notice in error,
please visit the Alharamain Sermon(english)
Subscribe Me maili
"Kevin B. McCarty" <[EMAIL PROTECTED]> writes:
> Karl Berry wrote:
>> Regretfully, Dr. Shinsaku unambiguously replied to me that he wishes to
>> restrict XyMTeX distribution. So I'll be taking it out of TeX Live for
>> next year.
>
> I'm very sorry to hear that my inquiry resulted in the removal
This message is to confirm the addition of your
email address: debian-devel@lists.debian.org to the
Alharamain Sermon(english)
Subscribe Me mailing list.
If you feel you have received this notice in error,
please visit the Alharamain Sermon(english)
Subscribe Me mailing list
at our website:
htt
This message is to verify that you wish to have your
email address: debian-devel@lists.debian.org removed from the
Alharamain Sermon(english)
Subscribe Me mailing list.
You MUST click on the link below to have your address removed
from our list. This is to ensure that someone doesn't remove your
This message is to confirm the removal of your
email address: debian-devel@lists.debian.org from the
Alharamain Sermon(english)
Subscribe Me mailing list.
We're sorry to see you go!
If you feel you have received this notice in error,
please visit the Alharamain Sermon(english)
Subscribe Me maili
> On Thu, Nov 24, 2005 at 06:45:58PM +, Ian Jackson wrote:
>> So the best idea is indeed for
>> downstream systems to have policies which are no more strict than
>> upstream systems.
>
> Would it be possible for master to make call-outs to chiark ?
> would that solve the problem ?
I don't thin
> "Kevin" == Kevin B McCarty <[EMAIL PROTECTED]> writes:
> I'm very sorry to hear that my inquiry resulted in the removal of
> XyMTeX from TeXLive. :-( It is a really useful tool.
> Let's hope that when Dr. Shinsaku considers XyMTeX more polished,
> he'll reconsider the license.
Don'
This one time, at band camp, Florian Weimer said:
> > On Thu, Nov 24, 2005 at 06:45:58PM +, Ian Jackson wrote:
> >> So the best idea is indeed for
> >> downstream systems to have policies which are no more strict than
> >> upstream systems.
> >
> > Would it be possible for master to make call-o
On Fri, Dec 02, 2005 at 02:22:41PM +0100, Simon Richter wrote:
> Matthew Palmer wrote:
>
> >Your mission, should you choose to accept it, is dig through the Perl code
> >in merkel:/org/bugs.debian.org/scripts and work out how to add this
> >functionality.
>
> You can use "package foo" as a comm
Estimado Sr(a),
Me dirijo a ustedes con el objetivo de iniciar de alguna forma, lo que podría
ser el inicio de una reforma interesante y justa para los dominios de internet
dados bajo la autorización de NIC Argentina. Aunque tanto en Argentina como en
el extranjero, lo que es "Legal" o "en el m
This message is to confirm the addition of your
email address: debian-devel@lists.debian.org to the
Alharamain Sermon(english)
Subscribe Me mailing list.
If you feel you have received this notice in error,
please visit the Alharamain Sermon(english)
Subscribe Me mailing list
at our website:
htt
This message is to verify that you wish to have your
email address: debian-devel@lists.debian.org removed from the
Alharamain Sermon(english)
Subscribe Me mailing list.
You MUST click on the link below to have your address removed
from our list. This is to ensure that someone doesn't remove your
This message is to verify that you wish to have your
email address: debian-devel@lists.debian.org removed from the
Alharamain Sermon(english)
Subscribe Me mailing list.
You MUST click on the link below to have your address removed
from our list. This is to ensure that someone doesn't remove your
This message is to verify that you wish to have your
email address: debian-devel@lists.debian.org removed from the
Alharamain Sermon(english)
Subscribe Me mailing list.
You MUST click on the link below to have your address removed
from our list. This is to ensure that someone doesn't remove your
Hi,
Joey Hess schrieb:
> A lintian-like test to see if the listed bugs match the package before
> uploading seems more useful to me. It would have prevented this
> particular problem.
The problem here would be that said test requires network connectivity,
while the rest of lintian does not.
On 12/3/05, Fabian Fagerholm <[EMAIL PROTECTED]> wrote:
> After several months of work, the DebConf5 Final Report has been
> released. The report is intended for a large audience, and includes
> impressions and facts from the conference. Whether you were there or
> not, we hope you will find the re
On Fri, 02 Dec 2005, Matthew Garrett wrote:
> Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> > Nobody said the user can't give his input on how the service will behave.
> > That's what the GUI is for, and what configuration files are for.
>
> The user needs to be able to configure this w
This message is to verify that you wish to have your
email address: debian-devel@lists.debian.org removed from the
Alharamain Sermon(english)
Subscribe Me mailing list.
You MUST click on the link below to have your address removed
from our list. This is to ensure that someone doesn't remove your
On Fri, Dec 02, 2005 at 05:52:03PM -0800, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> On Fri, Dec 02, 2005 at 08:47:47PM +0100, Mike Hommey wrote:
>
> > As you may or may not know, I'm currently working on packaging
> > xulrunner, which is ought to be the central point for all future mozilla
> >
53 matches
Mail list logo
