Thomas Goirand wrote:
> Hi,
>
> I'm sorry that it took us so much time to make a working yum package,
> but we were quite overloaded with our work, taking over all the
> customers of another web hosting company (taking all our time doing
> support). Anyway, I could today take the time to upload a
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 402 (new: 1)
Total number of packages offered up for adoption: 119 (new: 0)
Total number of packages request
Package: wnpp
Severity: wishlist
Owner: Stefanos Harhalakis
* Package name: katimon
Version : 1.0.2
Upstream Author : Stefanos Harhalakis
* URL : http://www.v13.gr/proj/katimon/
* License : GPLv2
Programming Lang: Python
Description : KDE ATI Graphics
On Fri, 17 Apr 2009, Holger Levsen wrote:
> On Donnerstag, 16. April 2009, Don Armstrong wrote:
> > reassign 524276 general
> > forcemerge 524286 524276
> > tags 524276 moreinfo
>
> why did you reassign them to general?
524276 and 524286 have to be in the same package to be merged. If you
think t
Hi Don,
On Donnerstag, 16. April 2009, Don Armstrong wrote:
> reassign 524276 general
> forcemerge 524286 524276
> tags 524276 moreinfo
why did you reassign them to general? why are these bugs a general problem in
Debian which is not related to any particular package?
(you probably wanted to re
Neil McGovern writes:
> On Wed, Apr 15, 2009 at 12:53:58PM +1000, Ben Finney wrote:
> > That would be premature. As I understand it, we're waiting on (and I'm
> > actively soliciting) input for other purposes of the information in the
> > ‘debian/copyright’ file; not least from the legal counsel
Hi all,
I think that the bug #523187 is the real problem. I solved my problem
unistalling splashy.
Thanks,
Luca
On Thu, Apr 16, 2009 at 5:15 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against t
On Thu, Apr 16, 2009 at 12:50:12PM -0500, Manoj Srivastava wrote:
> I think we need to enumerate some goals for this proposed
> change. Here is a start:
>
> - Minimal disruption for current packages. The impact should be
>measured by numbers of packages impacted
> At this point, I would say
Package: wnpp
Severity: wishlist
Owner: Maximilian Wilhelm
* Package name: wakeupmanager
Version : 0.9.4
Upstream Author : Maximilian Wilhelm
* URL : http://wum.rfc2324.org /
https://rfc2324.org/redmine/projects/show/wum
* License : GPL
Programming Lang: P
On Thu, Apr 16 2009, Giacomo Catenazzi wrote:
> Manoj Srivastava wrote:
>> - Ability to recognize and render the following logical entities, in
>>decreasing order of importance:
>>+ unordered lists
>>+ ordered lists
>
> really needed?
I would think these are the guts of this
On Thu, 16 Apr 2009, Marco d'Itri wrote:
> On Apr 16, Holger Levsen wrote:
> > Marco, if this is not a udev bug, please reassign it to the proper
> > package, but dont make users workaround you. Also note that 524276
> > is about udev in stable, which is not etch anymore.
>
> I have no reason to b
Processing commands for cont...@bugs.debian.org:
> reassign 524276 general
Bug#524276: udev not loading hardware modules
Bug reassigned from package `udev' to `general'.
> forcemerge 524286 524276
Bug#524286: general: kernel modules does not automatically load
Bug#524276: udev not loading hardwar
reassign 524276 general
forcemerge 524286 524276
tags 524276 moreinfo
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manoj Srivastava wrote:
> - Ability to recognize and render the following logical entities, in
>decreasing order of importance:
>+ unordered lists
>+ ordered lists
really needed?
>+ emphasis
>+ strong emphasis
>+ definition l
Hi,
I think we need to enumerate some goals for this proposed
change. Here is a start:
- Minimal disruption for current packages. The impact should be
measured by numbers of packages impacted
+ Any specification of which of *, +, - to use as th first level item
will impact mo
On Thu, Apr 16, 2009 at 5:11 PM, Marco d'Itri wrote:
> On Apr 16, Holger Levsen wrote:
>
> > Marco, if this is not a udev bug, please reassign it to the proper
> package,
> > but dont make users workaround you. Also note that 524276 is about udev
> in
> > stable, which is not etch anymore.
> I h
Quoting Lars Wirzenius (l...@liw.fi):
> to, 2009-04-16 kello 08:42 +0200, Christian Perrier kirjoitti:
> > I have never been able to find any such solid reference for English.
> > There is probably something in the Chicago Manual of Style, that's
> > generally accepted as the Right Reference for en
On Thu, Apr 16 2009, Josselin Mouette wrote:
> Le mercredi 15 avril 2009 à 23:05 -0500, Manoj Srivastava a écrit :
>> So, no, policy does not just document current practice. Policy
>> tries to document what is right.
>
> I think it should be both. When we do things right, they should be
>
Hi,
Oh, markdown is only confused when you have `two' `words'
quoted like this, wqhen there is only one such quote in the package, we
are fine.
This package contains the programs `abc2midi' which
So, less than 149 instances of the tag where we want none.
manoj
findi
On Thu, Apr 16 2009, Andreas Tille wrote:
> On Thu, 16 Apr 2009, Manoj Srivastava wrote:
>
>>> my initial posting. Detecting these would need either a defined
>>> character or a defined spacing (IMHO an 'and' would be better than
>>> a non-exclusive 'or' here).
>>
>>Umm. I am not sure tha
On Thu, Apr 16 2009, Tzafrir Cohen wrote:
> On Thu, Apr 16, 2009 at 04:01:20AM -0500, Manoj Srivastava wrote:
>
>> Umm. I am not sure that follows. I am also not convinced we need
>> to invent our own rules. Text::Markdown or Text::MultiMarkdown could
>> help. And they do not seem to hav
On Thu, Apr 16 2009, Andreas Tille wrote:
> On Thu, 16 Apr 2009, Ben Finney wrote:
>
>> Note that, like Manoj, I'm suggesting only a *subset*, not the full
>> specification.
>
> Well, in this thread we had several suggestions reaching from complete
> change to different format up to "not in detail
Your message dated Thu, 16 Apr 2009 17:11:58 +0200
with message-id <20090416151158.ga13...@bongo.bofh.it>
and subject line Re: Bug#524286: general: kernel modules does not automatically
load
has caused the Debian Bug report #524286,
regarding general: kernel modules does not automatically load
to
On Thu, Apr 16 2009, Ben Finney wrote:
> (following up on IRC discussion)
>
> Manoj Srivastava writes:
>
>> I suggest we follow a convention and tool set already in place,
>> with multiple language bindings, if you must insist on adding rules to
>> the long description.
>>
>> T
On Apr 16, Holger Levsen wrote:
> Marco, if this is not a udev bug, please reassign it to the proper package,
> but dont make users workaround you. Also note that 524276 is about udev in
> stable, which is not etch anymore.
I have no reason to believe that there is a bug (hint: "my computer is
reassign 524286 udev
thanks
On Donnerstag, 16. April 2009, Luca Boncompagni wrote:
> Package: general
> I try to open this as and udev bug (#524276) but Marco closed it because he
> think that this is not an udev bug.
I'm speechless. (About users filing bugs against the wrong package because the
On Wed, Apr 15, 2009 at 12:53:58PM +1000, Ben Finney wrote:
> That would be premature. As I understand it, we're waiting on (and I'm
> actively soliciting) input for other purposes of the information in the
> ‘debian/copyright’ file; not least from the legal counsel at SPI.
>
I could be wrong, bu
On Thu, 2009-04-16 at 10:18 +0200, Gabor Gombas wrote:
> ...except with latest hal/X.org/whatever it also stopped working. Latest
> X.org pulled in console-setup, and now the settings under
> /etc/hal/fdi/policy get ignored. What a mess.
that's called a bug. ranting on mailing lists doesn't do an
Le jeudi 16 avril 2009 à 15:06 +0200, Bjørn Mork a écrit :
> >> a) laptop keys remapped or disappearing (might be caused by the driver -
> >>I don't know)
> >
> > Yes, they are remapped to the standard XF86* names, so that applications
> > configuring shortcuts can have sensible defaults.
>
>
Josselin Mouette writes:
> Le jeudi 16 avril 2009 à 00:34 +0200, Bjørn Mork a écrit :
>> My list of hal related regressions are
>> a) laptop keys remapped or disappearing (might be caused by the driver -
>>I don't know)
>
> Yes, they are remapped to the standard XF86* names, so that applicatio
On Thu, 16 Apr 2009, Ben Finney wrote:
Note that, like Manoj, I'm suggesting only a *subset*, not the full
specification.
Well, in this thread we had several suggestions reaching from complete
change to different format up to "not in detail specified" subsets of
other formats. IMHO this does
Le mercredi 15 avril 2009 à 23:05 -0500, Manoj Srivastava a écrit :
> So, no, policy does not just document current practice. Policy
> tries to document what is right.
I think it should be both. When we do things right, they should be
specified in the Policy, and there’s no point specifyi
Le mercredi 15 avril 2009 à 17:12 -0500, Raphael Geissert a écrit :
> Then there must be some sort of missunderstanding. My intention was not to
> troll, but to demonstrate the implications of what you said. I would like
> to apologise for my previous message as I had understood something
> complet
Ben Finney writes:
> (following up on IRC discussion)
>
> Manoj Srivastava writes:
>
> > I suggest, for readability, to use a subset of markdown; the
> > link and image tags are not that human readable.
>
> reStructuredText http://docutils.sourceforge.net/rst.html> (reST)
> is, I arg
Le jeudi 16 avril 2009 à 01:25 +0200, Luca Niccoli a écrit :
> I think I (and the other people who are against X dependency on hal)
> have been pretty clear on the fact that we would just like an
> alternative, not to kick hal away (we're not stupid nor crazy). I
> think this would be good for debi
On Thu, 16 Apr 2009, Manoj Srivastava wrote:
my initial posting. Detecting these would need either a defined
character or a defined spacing (IMHO an 'and' would be better than
a non-exclusive 'or' here).
Umm. I am not sure that follows. I am also not convinced we need
to invent our own
Le jeudi 16 avril 2009 à 00:34 +0200, Bjørn Mork a écrit :
> My list of hal related regressions are
> a) laptop keys remapped or disappearing (might be caused by the driver -
>I don't know)
Yes, they are remapped to the standard XF86* names, so that applications
configuring shortcuts can have
On Thu, Apr 16, 2009 at 04:01:20AM -0500, Manoj Srivastava wrote:
> Umm. I am not sure that follows. I am also not convinced we need
> to invent our own rules. Text::Markdown or Text::MultiMarkdown could
> help. And they do not seem to have issues with recognizing
> indentation/differen
(following up on IRC discussion)
Manoj Srivastava writes:
> I suggest we follow a convention and tool set already in place,
> with multiple language bindings, if you must insist on adding rules to
> the long description.
>
> There are alternatives (Text::Textile comes to mind)
On Thu, Apr 16 2009, Andreas Tille wrote:
> On Thu, 16 Apr 2009, Manoj Srivastava wrote:
>
>>Any script should be able to take the top 4 symbols currently
>> used, and be able to detect them. I think *, +, - and o cover most
>> packages, and the scripts in question can be readily expanded
On Wed, Apr 15, 2009 at 10:25:36AM +0200, Bjørn Mork wrote:
> I still haven't got a clue how to really fix this, but have resorted to
> this for now:
>
>
>
>
>
> pc105
> no
>
>
>
...except with latest hal/X.org/whatever it also stopped working. Latest
X.org pulled
On Thu, Apr 16, 2009 at 02:34:52AM -0500, Manoj Srivastava wrote:
> Having sad that, I would not be averse to specifying that leading
> white space and *, +, and - would be acceptable as bullet marks (I
> thought specifying which mark at which level was overspecification).
Why don't we
On Thu, 16 Apr 2009, Manoj Srivastava wrote:
Any script should be able to take the top 4 symbols currently
used, and be able to detect them. I think *, +, - and o cover most
packages, and the scripts in question can be readily expanded. All
kinds of markup languages already do something
On Thu, Apr 16 2009, Andreas Tille wrote:
> On Thu, 16 Apr 2009, Manoj Srivastava wrote:
>
>>Do we really have nothing better to do than to impose
>> bureaucratic rules on what characters to use as bullet symbols in long
>> descriptions even if the user can tell that the character is a bul
On Thu, 16 Apr 2009, Manoj Srivastava wrote:
Do we really have nothing better to do than to impose
bureaucratic rules on what characters to use as bullet symbols in long
descriptions even if the user can tell that the character is a bullet?
The user can tell, but scripts can't reliably.
On Thu, Apr 16 2009, Christian Perrier wrote:
> Andreas Tille a écrit :
>
>> I have not found any recommendation regarding this at the SRP Wiki page
>> [1].
>> I vaguely remember that this Smith project was initially driven by a French
>> guy who might try to push a French habit into the English w
By reserving a top spot in our global home business, you will be above
thousands of others soon joining.
As the economy struggles, you can thrive:
http://alive7.myintensivesuccess.in/?b=ZGViaWFuLWRldmVsQGxpc3RzLmRlYmlhbi5vcmc
Thank you,
M. Gold
The quality of you
to, 2009-04-16 kello 08:42 +0200, Christian Perrier kirjoitti:
> I have never been able to find any such solid reference for English.
> There is probably something in the Chicago Manual of Style, that's
> generally accepted as the Right Reference for en_US.
>
> Maybe more input from our experts on
48 matches
Mail list logo
