Howdy all,
When submitting a bug to [EMAIL PROTECTED], the instructions at
URL:http://www.debian.org/Bugs/Reporting show some of the control
that can be operated by fields in the pseudo-header of the bug report
message.
One aspect of the bug I can't see represented there is the 'blocked
by'
On Mon, 19 May 2008, Ben Finney wrote:
When submitting a bug to [EMAIL PROTECTED], the instructions at
URL:http://www.debian.org/Bugs/Reporting show some of the control
that can be operated by fields in the pseudo-header of the bug report
message.
[...]
Is there a way to do this when
Hi,
On Monday 19 May 2008 10:04, Ben Finney wrote:
Is there a way to do this when submitting the bug report?
AFAIK not, but Dondelcarlo said on -devel the last few days that implementing
this is on his not-so-distant todo-list.
regards,
Holger
pgpLFcCEv7XHe.pgp
Description: PGP
Don Armstrong [EMAIL PROTECTED] writes:
Block by (and a few other control mechanisms) aren't support at
submit@ time; it's a valid wishlist bug, and one that I'm going to
be resolving soon.
Thanks. Would you like me to submit a bug report for this wishlist
bug?
--
\ Jealousy: The
On Sat, 17 May 2008 10:41:15 +0200 Vincent Bernat wrote:
I have uploaded the three of them.
Thank you Vincent!
Regards
Evgeni
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, 19 May 2008, Ben Finney wrote:
Don Armstrong [EMAIL PROTECTED] writes:
Block by (and a few other control mechanisms) aren't support at
submit@ time; it's a valid wishlist bug, and one that I'm going to
be resolving soon.
Thanks. Would you like me to submit a bug report for this
Don Armstrong [EMAIL PROTECTED] writes:
On Mon, 19 May 2008, Ben Finney wrote:
Don Armstrong [EMAIL PROTECTED] writes:
Block by (and a few other control mechanisms) aren't support at
submit@ time; it's a valid wishlist bug, and one that I'm going
to be resolving soon.
Thanks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cristian Greco wrote:
[missing text]
On the contrary, I think that relying on developers' care is not enough,
and libtorrent10 is too generic name. Moreover, actually only one client
depends on that library (rtorrent), where a lot of projects ([1]
Ruben Molina scrisse:
Dear mentors,
I am looking for a sponsor for the new version 1.2.0-6
of the package xplanet, which I'm adopting.
Here's a quick review of your package, which actually isn't in an
uploadable state:
* Your debian/copyright is lacking large third parties' copyright
Dear mentors,
I am looking for help and a sponsor for my package alternc.
Package name: alternc
Version : 0.9.9-1
Upstream Author : [EMAIL PROTECTED]
URL : alternc.org
License : GNU GENERAL PUBLIC LICENSE
Section : admin
It builds these binary
Dear mentors,
I am looking for a sponsor for my package lsat (My sponsor is very busy).
* Package name: lsat
Version : 0.9.7.1-1
Upstream Author : Triode [EMAIL PROTECTED]
* URL : http://usat.sourceforge.net
* License : GPL2+
Section : utils
It
bonjour,
j'ai créer un paquet debian pour installer une configuration générale
d'authentification sur ldap.
pour cela j'ai utilisé ucf sur les fichiers /etc/pam_ldap.conf,
nsswitch.conf, ldap.conf et conf pam.
je voudrais savoir comment je peux récupérer la configuration avant
installation du
Jose Luis Rivas Contreras wrote:
Sorry, I don't think that libtorrent-rakshasa is used by only one
client is argument enough to get it a name change.
I'm wondering if libtorrent-rakshasa even needs a shared library, given that the
only person using it is rakshasa.
--
Felipe Sateler
--
Dear mentors,
I am looking for a sponsor for my package irsim.
* Package name: irsim
Version : 9.7.65-1
Upstream Author : Dr. Timothy Edwards [EMAIL PROTECTED]
* URL : http://opencircuitdesign.com/irsim/
* License : GPL
Section
Hi!
The packaging for debian goes pretty well and I would like to request for a
sponsor in debian soon. The only thing preventing this so far is the unclear
licencing situation and maybe the lack of some documentation (manpages etc.).
I already work on some rudimentary manpages that will the
Hi!
Sorry for the last mail. I hit the send-button too early there :(. Sorry for
the probably confusing stuff without even saying hi.
Here is the stuff I missed:
The mails are a summary of my talk to upstream. I currently wait for the
licence to be set and then officially request for a
Hi,
I am looking for help and a sponsor for my package alternc.
It's clear that the package need a *lot* more work before it get here.
Sorry for the noise.
Patrick
signature.asc
Description: Ceci est une partie de message numériquement signée
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felipe Sateler wrote:
Jose Luis Rivas Contreras wrote:
Sorry, I don't think that libtorrent-rakshasa is used by only one
client is argument enough to get it a name change.
I'm wondering if libtorrent-rakshasa even needs a shared library, given
Jose Luis Rivas Contreras wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felipe Sateler wrote:
Jose Luis Rivas Contreras wrote:
Sorry, I don't think that libtorrent-rakshasa is used by only one
client is argument enough to get it a name change.
I'm wondering if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felipe Sateler wrote:
[some text missing]
The thing is you just named 3 cases were they are useful for unrelated reasons
(namely, saving mirror space via an arch: all package), while you didn't
provide the reason for libtorrent.
Maybe I was
20 matches
Mail list logo
