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: 333 (new: 16)
Total number of packages offered up for adoption: 106 (new: 3)
Total number of packages reques
[EMAIL PROTECTED] wrote:
> Hello,
>
> Frank Küster napsal:
>> "Jiri Palecek" <[EMAIL PROTECTED]> wrote:
>>
>> > Hello,
>> >
>> > can anyone explain why gcc-4.2 build-depends on libgconf2-dev,
>> > libxul-dev, libart-2.0-dev, libgtk2.0-dev,
>> > lib32asound2-dev, libcairo2-dev, libqt4-dev and seve
On 10/19/06, Mike Hommey <[EMAIL PROTECTED]> wrote:
Waw, actually, i was trying to be less aggressive...
Anyways, since I'm too pissed and since I see no reason to put myself in
that mood any further, I'm taking a few days off Debian, which means my
current work on seamonkey^Hiceape will be on h
access news: Hot XXX Fuckoing!!! Thebse girls lopve a nice stbiff coyck!! :)
GOTO: *** plbrl.zopurar.com ***
their capo look really eyes provide soon, after here can, form twice link all
form?
loose eyes surf add today out forever order; self and, just other they.
face online are told, access ey
On Friday 20 October 2006 08:06, Peter Samuelson wrote:
> [Sander Marechal]
>
> > True, but I meant that an app can kill X, requiring it to be restarted.
> > Newbies get very confused at that point.
>
> Look, if you typed "startx" once, you can type it again.
>
> If you didn't, it means you're usin
On Fri, 20 Oct 2006 08:47:48 +1000, Aníbal Monsalve Salazar wrote:
> I also couldn't find in the FAQ [3] any reference about how to
> download checklib.
> [3] http://rerun.lefant.net/checklib/faq.html
> How can download and run checklib?
On http://rerun.lefant.net/checklib/ the last line says:
"
Hello,
There is a link to Checklib [0] in the Packages Overview page
of every maintainer. See for example vorlon's page at [1] where
you could see that link in the line starting with "Reports:".
[0] http://rerun.lefant.net/checklib/
[1] http://qa.debian.org/developer.php?login=vorlon
I couldn't
On Thu, 19 Oct 2006, Kevin Mark wrote:
> DD's trying to use Debian policy as a guide to make all packages
> pass policy requirement. Is this not what they are tasked to do?
There's nothing wrong with these goals. Indeed, I'm sure no one would
object to patches and bugs being filed to fix these pol
[Sander Marechal]
> True, but I meant that an app can kill X, requiring it to be restarted.
> Newbies get very confused at that point.
Look, if you typed "startx" once, you can type it again.
If you didn't, it means you're using a display manager like xdm, and
xdm will restart X when it dies.
I
On Thu, Oct 19, 2006 at 10:52:25PM +0200, Mike Hommey wrote:
> On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> wrote:
> > * Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
> > > [another agression]
> Waw, actually, i was trying to be less aggressive...
This is a ver
On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
> > [another agression]
>
> Sorry, but enough is enough. I'm fed up about your sudden agressions
> towards me for no reason at all. Welcome to my killfile.
>
>
Hi Andi,
from my pers
On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
> > [another agression]
Waw, actually, i was trying to be less aggressive...
Anyways, since I'm too pissed and since I see no reason to put myself in
that mood a
Mike Hommey <[EMAIL PROTECTED]> wrote:
> Be aware that, even if you don't like it, this looks like you bend the
> rules so that it doesn't alter the release plan.
> Be also aware that too much bending the rules makes them useless.
Don't try to bend the rules, it's impossible. Instead, only realiz
Mike Hommey <[EMAIL PROTECTED]> writes:
>> So, what does the Etch RC policy remove from the bugs.d.o description?
>
> 'is a severe violation of Debian policy (roughly, it violates a "must" or
> "required" directive), or'
Perhaps you should concentrate on the word "roughly" there. What
constitut
On Thursday 19 October 2006 13:37, Christoph Haas wrote:
> I'm the maintainer of the "ethstatus" package - a console-based ethernet
> statistics monitor. You can e.g. run it on your gateway's 9" CRT on the
> console and see how much bandwidth is currently used in a bar-like view.
> I'm in the proce
Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 19, 2006 at 10:20:46PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> wrote:
>> * Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]:
>> > Where does it say the scope for 4. Autobuilding is "buildds must not
>> > fail" ?
>>
>> There are always bugs in
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
> [another agression]
Sorry, but enough is enough. I'm fed up about your sudden agressions
towards me for no reason at all. Welcome to my killfile.
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Hello,
Frank Küster napsal:
> "Jiri Palecek" <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > can anyone explain why gcc-4.2 build-depends on libgconf2-dev,
> > libxul-dev, libart-2.0-dev, libgtk2.0-dev,
> > lib32asound2-dev, libcairo2-dev, libqt4-dev and several others? It
> > seems quite strang
On Thu, Oct 19, 2006 at 10:20:46PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]:
> > Where does it say the scope for 4. Autobuilding is "buildds must not
> > fail" ?
>
> There are always bugs in any document.
Be aware that, even if you don't
On Thu, Oct 19, 2006 at 10:15:16PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061019 22:06]:
> > That was not a link before it was changed before sarge release, in July
> > 2004.
>
> The link was added later because people were barking around. The meaning
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]:
> Where does it say the scope for 4. Autobuilding is "buildds must not
> fail" ?
There are always bugs in any document.
For sarge, we e.g. sarge-ignored some MTAs which didn't provide -bs,
though LSB requires that. Now, we adjusted the policy to m
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:06]:
> That was not a link before it was changed before sarge release, in July
> 2004.
The link was added later because people were barking around. The meaning
was always the same.
Anyways, July 2004 is a *bit* history now, don't you think so?
> So, w
Hello d-dev,
I noticed yesterday that after an upgrade I got a /usr/lib64 dir
with some (not neded) stuff in it. I am not running any 64 bit arch.
$ dpkg -S /usr/lib64 # says:
libg2c0-dev, fakeroot, libgfortran1-dev: /usr/lib64
I have found that there is a bug [1] on fakeroot reporting the same.
On Thu, Oct 19, 2006 at 09:56:37PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> * Aurelien Jarno ([EMAIL PROTECTED]) [061019 21:31]:
> > Andreas Barth a écrit :
> > >A violation of the parts of the debian policy as listed on
> > >http://release.debian.org/etch_rc_policy.txt is serious level (
On Thu, Oct 19, 2006 at 03:53:56PM -0400, Eric Dorland <[EMAIL PROTECTED]>
wrote:
> * Andreas Barth ([EMAIL PROTECTED]) wrote:
> > * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
> > > On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth <[EMAIL
> > > PROTECTED]> wrote:
> > > > * Mike Hommey
On Thu, Oct 19, 2006 at 09:35:38PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> But I need to admit that I get sick, seriously sick. If someone doesn't
> agree with something, he just says "you do it wrong just for release of
> etch on $date". I really hate that. Especially when it's about th
* Aurelien Jarno ([EMAIL PROTECTED]) [061019 21:31]:
> Andreas Barth a écrit :
> >A violation of the parts of the debian policy as listed on
> >http://release.debian.org/etch_rc_policy.txt is serious level (that
> >should be the same as the must-directives in policy, but - well, I hope
> >that I ha
* Andreas Barth ([EMAIL PROTECTED]) wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
> > On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> > wrote:
> > > * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
> > > > Note how subtly the Etch RC policy removes the f
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:25]:
> On Thu, Oct 19, 2006 at 09:17:38PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> wrote:
> > * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
> > > On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth <[EMAIL
> > > PROTECTED]> wrote:
> > > > * M
Andreas Barth a écrit :
A violation of the parts of the debian policy as listed on
http://release.debian.org/etch_rc_policy.txt is serious level (that
should be the same as the must-directives in policy, but - well, I hope
that I have finally time post-etch to sync that finally).
Any other polic
On Thu, Oct 19, 2006 at 09:17:38PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
> > On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> > wrote:
> > > * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
> > > > Note ho
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
> On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> wrote:
> > * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
> > > Note how subtly the Etch RC policy removes the first alternative of the
> > > serious bug description
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> * Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
> > Note how subtly the Etch RC policy removes the first alternative of the
> > serious bug description...
>
> Which do you mean? Please read the Etch RC policy.
* Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
> Note how subtly the Etch RC policy removes the first alternative of the
> serious bug description...
Which do you mean? Please read the Etch RC policy. It tells:
| In addition to the issues listed in this document, an issue is release
| critical
On Thu, Oct 19, 2006 at 11:29:38AM -0700, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> On Thu, Oct 19, 2006 at 07:51:19PM +0200, Mike Hommey wrote:
> > On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> > wrote:
> > > > Doesn't policy violation warrant Critical severity?
On Thu, Oct 19, 2006 at 07:51:19PM +0200, Mike Hommey wrote:
> On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> wrote:
> > > Doesn't policy violation warrant Critical severity?
> > No. Please see the top of http://release.debian.org/etch_rc_policy.txt
> > for which bu
On Thu, 2006-10-19 at 10:00 -0700, Kevin B. McCarty wrote:
> Tshepang Lekhonkhobe wrote:
>
> > Doesn't policy violation warrant Critical severity?
>
> No, it "only" warrants the lowest RC severity, serious [0], unless the
> bug in addition makes the package or other software (mostly) unusable,
>
On Thu, 2006-10-19 at 19:51 +0200, Mike Hommey wrote:
> On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth <[EMAIL PROTECTED]>
> wrote:
> > > Doesn't policy violation warrant Critical severity?
> >
> > No. Please see the top of http://release.debian.org/etch_rc_policy.txt
> > for which bugs
On Thu, Oct 19, 2006 at 07:01:20PM +0200, Frans Pop wrote:
> On Thursday 19 October 2006 18:45, Petter Reinholdtsen wrote:
> > If no problem is caused by it, I believe 'normal' or even 'wishlist'
> > severity is the proper severity to use.
> s/wishlist/minor/
> It _is_ a bug after all.
s/minor/i
On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth <[EMAIL PROTECTED]>
wrote:
> > Doesn't policy violation warrant Critical severity?
>
> No. Please see the top of http://release.debian.org/etch_rc_policy.txt
> for which bugs are critical, grave and serious.
That is irrelevant for the sever
* Aurelien Jarno ([EMAIL PROTECTED]) [061019 15:06]:
> Among all of the bugs reported by lintian, one concerns a lot of
> packages, the presence of the clean, binary, binary-arch, binary-indep
> and build targets. This is required by both the section 4.9 of the
> policy and the Etch release standa
* Tshepang Lekhonkhobe ([EMAIL PROTECTED]) [061019 18:09]:
> On 10/19/06, Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
> >
> >[Aurelien Jarno]
> >> I have just run lintian on all the archive (amd64) for both binaries and
> >> sources, and the results are a bit scary. It looks like a lot of
> >> m
On Thu, Oct 19, 2006 at 06:45:53PM +0200, Petter Reinholdtsen wrote:
> Well, policy isn't a stick to beat other maintainers with, it is a
> tool to make sure our packages are well integrated and work properly.
> Thus, policy issues are not problems by themselves, they are policy
> issues because th
On Thursday 19 October 2006 18:45, Petter Reinholdtsen wrote:
> If no problem is caused by it, I believe 'normal' or even 'wishlist'
> severity is the proper severity to use.
s/wishlist/minor/
It _is_ a bug after all.
pgp8CuxfBlHbn.pgp
Description: PGP signature
Tshepang Lekhonkhobe wrote:
> Doesn't policy violation warrant Critical severity?
No, it "only" warrants the lowest RC severity, serious [0], unless the
bug in addition makes the package or other software (mostly) unusable,
causes data loss, or introduces a security hole.
[0] http://www.debian.o
[Tshepang Lekhonkhobe]
> Doesn't policy violation warrant Critical severity?
Well, policy isn't a stick to beat other maintainers with, it is a
tool to make sure our packages are well integrated and work properly.
Thus, policy issues are not problems by themselves, they are policy
issues because
On 10/19/06, Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
[Aurelien Jarno]
> I have just run lintian on all the archive (amd64) for both binaries and
> sources, and the results are a bit scary. It looks like a lot of
> maintainers are uploading their packages, and don't really care with the
>
On 10/19/06, Jean Parpaillon <[EMAIL PROTECTED]> wrote:
As a side effect, can someone tell me if there is a command to search
for packages regarding Build-Depends ?
grep-dctrl -sPackage -F Build-Depends,Build-Depends-Indep cmake
/var/lib/apt/lists/*Sources
Or, see the more elaborate version,
[Aurelien Jarno]
> I have just run lintian on all the archive (amd64) for both binaries and
> sources, and the results are a bit scary. It looks like a lot of
> maintainers are uploading their packages, and don't really care with the
> policy.
What is the technical problem triggered by the pack
Hi all,
I maintain the package wormux and my dear upstream devels decided to
switch from autotools to cmake, for the best and the worse.
Are there people with experiences with it ? Maybe kde packagers are
already working on it ?
As a side effect, can someone tell me if there is a command to se
Christoph Haas <[EMAIL PROTECTED]> writes:
> I'm unhappy with the missing upstream situation. I could also wait for a
> volunteer to maintain both the software and the maintainer.
^^
What kind of maintenance do *you* need?
Matthias
--
Hi all,
I have just run lintian on all the archive (amd64) for both binaries and
sources, and the results are a bit scary. It looks like a lot of
maintainers are uploading their packages, and don't really care with the
policy.
Maybe some errors (E:) of lintian could be changed to critical (C:)
Dear list...
I'm the maintainer of the "ethstatus" package - a console-based ethernet
statistics monitor. You can e.g. run it on your gateway's 9" CRT on the
console and see how much bandwidth is currently used in a bar-like view.
I'm in the process of RFA'ing the package. But I wonder whether
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.10.17.1618 +0200]:
> Thus, unless I get other suggestions, I'll package it up in its
> own package, which diverts /sbin/{reboot,halt,shutdown} and puts
> my shell script in their place. I'll Enhance whatever init systems
> there are and I'll ask
Em Wed, 18 Oct 2006 10:26:26 -0200
"Yves Junqueira" <[EMAIL PROTECTED]> escreveu:
> It may be much cleaner to include help links /etc/motd, adivising the
> user to read a hipothetical
> "/usr/share/doc/linux-beginners/new-users", or enter a help-mode by
> typing a certain command.
Much cleaner, b
On Thu, Oct 19, 2006 at 09:47:10AM +0100, David Moore wrote:
> Hi,
>
> I have developed some new software, an audioscrobbler client for
> _l_a_s_t_._f_m, which
> I would
> like to see included, probably under Multimedia.
>
> It consists of two simple C source files - how do I go about ge
#include
* Thomas Viehmann [Thu, Oct 19 2006, 10:58:42AM]:
> Wouter Verhelst wrote:
> > Or we could mimic FreeBSD behaviour: create a fortune-file with helpful
> > tips for newbies, and add a line in the default initialization files
> > (i.e., those in /etc/skel) for different shells that calls fo
On Thu, Oct 19, 2006 at 09:47:10AM +0100, David Moore wrote:
> Hi,
>
> I have developed some new software, an audioscrobbler client for last.fm,
> which I would
> like to see included, probably under Multimedia.
>
> It consists of two simple C source files - how do I go about getting it
> include
On Thu, Oct 19, 2006 at 10:58:42AM +0200, Thomas Viehmann wrote:
> Wouter Verhelst wrote:
> > Or we could mimic FreeBSD behaviour: create a fortune-file with helpful
> > tips for newbies, and add a line in the default initialization files
> > (i.e., those in /etc/skel) for different shells that cal
Hi,
I have developed some new software, an audioscrobbler client for last.fm, which I would
like to see included, probably under Multimedia.
It consists of two simple C source files - how do I go about getting it included
in Debian?
Cheers,
David.
[EMAIL PROTECTED] --
http://dmct
Wouter Verhelst wrote:
> Or we could mimic FreeBSD behaviour: create a fortune-file with helpful
> tips for newbies, and add a line in the default initialization files
> (i.e., those in /etc/skel) for different shells that calls fortune for
> those tips.
You mean like fortunes-debian-hints[1]?
Ki
On Wed, Oct 18, 2006 at 10:26:26AM -0200, Yves Junqueira wrote:
> It may be much cleaner to include help links /etc/motd, adivising the
> user to read a hipothetical
> "/usr/share/doc/linux-beginners/new-users", or enter a help-mode by
> typing a certain command.
Or we could mimic FreeBSD behaviou
Error in the command: The original message was received at Thu, 19 Oct 2006
14:05:57 +0600 from 177.180.128.188
Unrecognized command verb: THE
Subsequent commands ignored because of previous error.
Ignored: - The following addresses had permanent fatal errors -
Ignored: <[EMAIL PROTECTED]>
63 matches
Mail list logo
