Bug#492822: ITP: drizzle -- A Lightweight SQL Database for Cloud and Web

[Monty Taylor]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org

The Drizzle project is building a database optimized for Cloud and Net
applications. It is being designed for massive concurrency on modern
multi-cpu/core architecture. The code is originally derived from MySQL.

The project is focused on making a database that is:
1) Reliable
2) Fast and scalable on modern architecture
3) Simply design for ease of installation and management

Drizzle's home is http://launchpad.net/drizzle.
Drizzle is distributed under the GPLv2



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

Re: Good communication with upstream is good idea

[Ben Finney]

Florian Weimer <[EMAIL PROTECTED]> writes:

> * Ben Finney:
> 
> >> I guess it's more of a Google QA issue
> >
> > No, if the pages exist and other pages tend to treat them as
> > interesting (i.e. interesting pages link to those pages), Google
> > is working as advertised if it indexes and reports them.
> 
> Sorry, but this is just wrong. If the page is not interesting to a
> particular query and its sender, it's got no place in the search
> results. Searching isn't about spec conformance, it's about results.

That's why the statement above is qualified. Google's Page Rank
algorithm — its heuristic for "is the page interesting to a
particular querent" — is advertised to be largely driven by other
pages (which have their own Page Rank affecting their weight) linking
to the page under consideration.

So, if this is indeed what occurs, Google is working as advertised.

Now that (reportedly) these pages under discussion have a standard
"please don't spider" request, perhaps this issue has become moot.

-- 
 \   “Never use a long word when there's a commensurate diminutive |
  `\available.” —Stan Kelly-Bootle |
_o__)  |
Ben Finney


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

Re: Standard way to disable services

[Henrique de Moraes Holschuh]

On Tue, 29 Jul 2008, Franklin PIAT wrote:
> I haven't investigated it, but I wonder if it isn't the sane way to have
> complex dependency (à  la LSB) stored in one place, and system admin
> preference in another place.

Well, policy-rc.d is obeyed by invoke-rc.d, and therefore, by all maintainer
scripts.

But manually trying to run the initscript will still work.

And sysv-init will STILL run it.  If you want it to not run on runlevel
changes/boot, you NEED to use a K link, or you need to disable it in
whatever alternative initscript you use (such as file-rc, runit, etc).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


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

Re: Standard way to disable services

[Franklin PIAT]

On Sat, 2008-07-26 at 10:40 -0700, Steve Langasek wrote:
> On Sat, Jul 26, 2008 at 07:27:27PM +0200, Luk Claes wrote:
> > Steve Langasek wrote:
> > > On Sat, Jul 26, 2008 at 02:11:26PM +0200, Josselin Mouette wrote:
> > >> Le samedi 26 juillet 2008 a  13:18 +0200, Harald Braumann a ecrit
:
> > >>> quite often I just want to disable a service in /etc/init.d.
> > >>> But there doesn't seem to be a standard way to do that.
>
> > >> The standard way is to remove the symlinks in /etc/rc?.d
>
> > > No, the standard way is to *rename* the S symlinks to K symlinks.
>
> > One draw back is that it's not obvious what used to be an S link if
> > you want to reenable them, that's why I rename them to s symlinks...
>
> Unfortunately, that still leaves the service state undefined and will
> cause services to be restarted when invoke-rc.d is used.

Recently[0], Don Armstrong said that policy-rc.d[1] can be used to disable
a service, based on local policy.

I haven't investigated it, but I wonder if it isn't the sane way to have
complex dependency (à  la LSB) stored in one place, and system admin
preference in another place.

Franklin

[0] In a d-devel thread about /var/www vs FHS, Stephen Gran
wondered "how to have network services disabled by default".
[1] /usr/share/doc/sysv-rc/README.policy-rc.d.gz





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

Bug#492807: ITP: procinfo-ng -- displays system information from /proc

[Giuseppe Iuculano]

Package: wnpp
Severity: wishlist
Owner: Giuseppe Iuculano <[EMAIL PROTECTED]>

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

* Package name: procinfo-ng
  Version : 2.0.196
  Upstream Author : Thaddeus Messenger <[EMAIL PROTECTED]>
* URL : http://procinfo-ng.sourceforge.net
* License : GPL
  Programming Lang: C++
  Description : displays system information from /proc


Procinfo-NG is a small program that gathers some system information from
diverse files under /proc and prints it to the screen.
Procinfo-NG is a complete rewrite of the old system monitoring app
procinfo. The goal is to make more readable (and reusable) code and to
restore broken functionality.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiOU6gACgkQNxpp46476ap6sACeLp+34LO762Z2falQMU7+JuiS
FYUAn08UbdIkpaOBo/DMBRGBlG7mr1e7
=T/A6
-END PGP SIGNATURE-



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

Re: procinfo maintainership

[Bernd Zeimetz]

tabris wrote:
> Bernd Zeimetz wrote:
>> Thanks for the info. As I wasn't able to find any other email adress or
>> activity from the maintainer, I've orphaned the package and it will be
>> listed within the orphaned packages on http://www.debian.org/devel/wnpp/
>> soon. So you could either adopt it and take care of it on your own...
>>   
> If I were to do so (or find a maintainer) would they have the option
> of obsoleting procinfo-18 and replacing it with procinfo-ng ? 

yes, although I doubt it would be able to go in Lenny as it is frozen now.


-- 
 Bernd Zeimetz   Debian GNU/Linux Developer
 GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79


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

Re: procinfo maintainership

[tabris]

Bernd Zeimetz wrote:
> Thanks for the info. As I wasn't able to find any other email adress or
> activity from the maintainer, I've orphaned the package and it will be
> listed within the orphaned packages on http://www.debian.org/devel/wnpp/
> soon. So you could either adopt it and take care of it on your own...
>   
If I were to do so (or find a maintainer) would they have the option
of obsoleting procinfo-18 and replacing it with procinfo-ng ? The old
procinfo code is a) grotty b) very very 1990's C c) broken on 64bit
platforms d) many features are broken e) other features are pointless on
2.6 kernels (cat /proc/filesystems, done as a every 2 seconds poll? wtf?)
Procinfo-NG is a) hopefully more readable b) At least early-2000's C++
c) Working on 64bit x86 and 32bit x86 (don't have any PPC or SPARC Linux
boxen to test on yet) d) fixed some broken features e) added new ones f)
never implemented the more odd features like polling /proc/filesystems
and /proc/modules

If there are any questions over the maintainership of the
procinfo-ng upstream codebase, I'll open it to other interested developers.




signature.asc
Description: OpenPGP digital signature

Re: New Testing Name ???

[Adeodato Simó]

> Im just a little bit curious, I wanted to know
> what will be the new testing name?
> haye you already choose the name or it will be defined later.
> Lenny will be stable soon, so this is why the question.

No, it hasn't been decided yet, but it will be decided before lenny
releases.

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Don't be irreplaceable, if you can't be replaced, you can't be promoted.


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

Re: Good communication with upstream is good idea

[Russ Allbery]

James Westby <[EMAIL PROTECTED]> writes:

> On unactivated account pages launchpad now sets
>
>   
>
> so these pages should not show up in results from well behaved
> search engines.

Ah, excellent, thank you.

-- 
Russ Allbery ([EMAIL PROTECTED])   


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

New Testing Name ???

[Victor Muchica]

Hi all

Im just a little bit curious, I wanted to know
what will be the new testing name?
haye you already choose the name or it will be defined later.
Lenny will be stable soon, so this is why the question.

Greetings
-- 
Victor Muchica
http://muchikon.blogspot.com
http://planeta.debianperu.org
LRU: #416557


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

Re: procinfo maintainership

[Bernd Zeimetz]

tabris wrote:
> Bernd Zeimetz wrote:
 So who do I need to contact to find a debian package maintainer for a)
 procinfo-18 b) procinfo-ng ?

>>
>> did you try to contact the maintainer of procinfo? If they're not
>> interested, look at  http://www.debian.org/devel/wnpp/
>>
> Yes, I tried to contact the maintainer. the maintainer's email address
> is [EMAIL PROTECTED] and that domain is now owned by a squatter.
> 

Thanks for the info. As I wasn't able to find any other email adress or
activity from the maintainer, I've orphaned the package and it will be
listed within the orphaned packages on http://www.debian.org/devel/wnpp/
soon. So you could either adopt it and take care of it on your own...

-- 
 Bernd Zeimetz   Debian GNU/Linux Developer
 GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79


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

Re: FHS and /var/www

[Patrick Matthäi]

Carl Fürstenberg schrieb:
> FHS 2.3 specifies in
> http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM
> to use /srv for "Data for services provided by this system", for
> example /srv/www for web root.
> In the policy, the section
> 9.1.1(http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.1)
> specifies that FHS 2.3 is mandatory, except for some exception, and
> the use of /var/www isn't included in that list.
> 
> Should we force all httpd:s to use /srv/www instead of /var/www, or
> should an exception to the policy be added? Per
> http://wiki.debian.org/Apache2LennyGoals it states that apache2 has
> support for /srv/www, but it's still defaulting to /var/www.
> 

Hello,

I fully agree with you, but there are some problems.

1) lintian states that packagers should add a regular httpd config file
which should work on most http-daemons - this is in my opinion garbage
and not user friendly.

2) lintian also states (yes against lintian) that the packagers
shouldn't point symlinks or anything like that in / from
/var/www/ but they should add instructions (in README.Debian)
for the administator how he could set up his web application, this is
also not very user friendly..

Yes the FHS says, that such data has to be places in /srv/ so what have
we to do? We should NOT go the user unfriendly way and place at every
webapp-package some README.Debian files, we should migrate after lenny
from /var/www to /srv/www - I think it will solve the issue with less
user problems.

-- 
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi

E-Mail: [EMAIL PROTECTED]

Comment:
Always if we think we are right,
we were maybe wrong.
*/


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

Re: Good communication with upstream is good idea

[Florian Weimer]

* Ben Finney:

>> I guess it's more of a Google QA issue
>
> No, if the pages exist and other pages tend to treat them as
> interesting (i.e. interesting pages link to those pages), Google is
> working as advertised if it indexes and reports them.

Sorry, but this is just wrong.  If the page is not interesting to a
particular query and its sender, it's got no place in the search
results.  Searching isn't about spec conformance, it's about results.


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

Bug#492760: ITP: freedink -- A portable version of the Dink Smallwood game engine.

[Bradley Smith]

Package: wnpp
Severity: wishlist
Owner: Bradley Smith <[EMAIL PROTECTED]>

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

* Package name: freedink
  Version : 1.0.7 (Not 'officially' released yet)
  Upstream Author : Sylvain Beucler <[EMAIL PROTECTED]>
* URL : http://www.gnu.org/software/freedink/
* License : GPL
  Programming Lang: C
  Description : A portable version of the Dink Smallwood game engine.

Dink Smallwood is an adventure/role-playing game, similar to Zelda, made
by RTsoft. Besides twisted humour, it includes the actual game editor,
allowing players to create hundreds of new adventures called Dink
Modules or D-Mods for short. The Dink Network hosts a copy of almost all
of them.

In 2003, Seth A. Robinson from RTsoft released the source code of the
game engine, at version 1.07, under a free software license.


Notes:

Currently parts of the official data for this package are still under
the control of RTSoft, although this is hoped to be resolved at some
point. Until this point either this package will be placed in contrib
with the data in non-free, or I shall create some simple data files
myself under a free license, and not depend on the non-free data at all.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiOBHkACgkQj3BimscY00cwtQCgmTnXSrXcEDusM/PXZtCurrfp
5tsAoKHL8oqLjS1EwpscRAUUO9HeUpfi
=Lf7T
-END PGP SIGNATURE-



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

Re: Lenny frozen

[Franklin PIAT]

On Mon, 2008-07-28 at 16:51 +0100, Martin Meredith wrote:
> On Mon, 2008-07-28 at 17:15 +0200, Olivier Berger wrote:
> > OK, thanks.
> >
> > I still am not completely sure about something : should only bugs
> > of severity >= "important" be fixed (and uploaded to unstable for
> > the "important" ones) in order for inclusion in lenny, or also
> > lesser severities too ?
>
> As far as I can tell, unstable continues as normal. However, nothing
> that is uploaded to unstable as of the start of the freeze will be
> automatically migrated into testing.

If I understand correctly, uploading a new version to unstable
(targeting lenny+1), will prevent you from uploading a minor bug-fix'ed
version to unstable. This means that Lenny bug-fix will be uploaded to
testing-proposed-update... which won't go through unstable for wide
testing.

Franklin






On Mon, 2008-07-28 at 16:51 +0100, Martin Meredith wrote:


On Mon, 2008-07-28 at 17:15 +0200, Olivier Berger wrote:
> OK, thanks.
> 
> I still am not completely sure about something : should only bugs of
> severity >= "important" be fixed (and uploaded to unstable for the
> "important" ones) in order for inclusion in lenny, or also lesser
> severities too ?

As far as I can tell, unstable continues as normal. However, nothing
that is uploaded to unstable as of the start of the freeze will be
automatically migrated into testing. 





If I understand correctly, uploading a new version to unstable (targeting lenny+1), will prevent you from uploading a minor bug-fix'ed version to unstable. This means that Lenny bug-fix will be uploaded to testing-proposed-update... which won't go through unstable for wide testing.

Franklin

Re: procinfo maintainership

[tabris]

Bernd Zeimetz wrote:

So who do I need to contact to find a debian package maintainer for a)
procinfo-18 b) procinfo-ng ?
   


did you try to contact the maintainer of procinfo? If they're not
interested, look at  http://www.debian.org/devel/wnpp/
   
Yes, I tried to contact the maintainer. the maintainer's email address 
is [EMAIL PROTECTED] and that domain is now owned by a squatter.



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

Re: Lenny frozen

[Martin Meredith]

On Mon, 2008-07-28 at 17:15 +0200, Olivier Berger wrote:
> OK, thanks.
> 
> I still am not completely sure about something : should only bugs of
> severity >= "important" be fixed (and uploaded to unstable for the
> "important" ones) in order for inclusion in lenny, or also lesser
> severities too ?

As far as I can tell, unstable continues as normal. However, nothing
that is uploaded to unstable as of the start of the freeze will be
automatically migrated into testing. 

severity >= "important" are a reason that you might ask for an exception
to the freeze, which, if accepted, will allow that package to be
migrated to testing as it would normally do.


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

Re: Lenny frozen

[Olivier Berger]

Le lundi 28 juillet 2008 à 17:06 +0200, Luk Claes a écrit :
> Olivier Berger wrote:
> > Hi.
> > 
> > Can you provide a link to policy documents explaining the freeze process
> > in more details ?
> > 
> > In particular, I'm not sure I understand the last paragraph quoted
> > bellow,  the "only when this can be done via unstable" :
> 
> That means that you shouldn't try to fix these kind of bugs via
> testing-proposed-updates as they wouldn't be accepted anyway as they
> don't get the usual testing from aging in unstable...
> 

OK, thanks.

I still am not completely sure about something : should only bugs of
severity >= "important" be fixed (and uploaded to unstable for the
"important" ones) in order for inclusion in lenny, or also lesser
severities too ?

Thanks in advance.
-- 
Olivier BERGER <[EMAIL PROTECTED]>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


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

Re: Lenny frozen

[Luk Claes]

Olivier Berger wrote:
> Hi.
> 
> Can you provide a link to policy documents explaining the freeze process
> in more details ?
> 
> In particular, I'm not sure I understand the last paragraph quoted
> bellow,  the "only when this can be done via unstable" :

That means that you shouldn't try to fix these kind of bugs via
testing-proposed-updates as they wouldn't be accepted anyway as they
don't get the usual testing from aging in unstable...

Cheers

Luk

> Le dimanche 27 juillet 2008 à 16:00 +0200, Marc 'HE' Brockschmidt a
> écrit :
>> Now, so as not to have everyone contact us at once about packages we
>> know we won't approve, here are the guidelines for changes that will be
>> accepted into testing during the freeze:
> 
>>   - fixes for severity: important bugs in packages of priority: optional
>> or extra, only when this can be done via unstable;
>>
> 
> Thanks in advance for your clarification.
> 
> Best regards,


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

Re: Lenny frozen

[Cyril Brulebois]

Olivier Berger <[EMAIL PROTECTED]> (28/07/2008):
> Can you provide a link to policy documents explaining the freeze
> process in more details ?
> 
> In particular, I'm not sure I understand the last paragraph quoted
> bellow,  the "only when this can be done via unstable" :

Sure: http://www.debian.org/doc/developers-reference/pkgs.html#t-p-u

Debian Policy + Developers Reference usually answer all questions you
might have.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Lenny frozen

[Olivier Berger]

Hi.

Can you provide a link to policy documents explaining the freeze process
in more details ?

In particular, I'm not sure I understand the last paragraph quoted
bellow,  the "only when this can be done via unstable" :

Le dimanche 27 juillet 2008 à 16:00 +0200, Marc 'HE' Brockschmidt a
écrit :
> Now, so as not to have everyone contact us at once about packages we
> know we won't approve, here are the guidelines for changes that will be
> accepted into testing during the freeze:

>   - fixes for severity: important bugs in packages of priority: optional
> or extra, only when this can be done via unstable;
> 

Thanks in advance for your clarification.

Best regards,
-- 
Olivier BERGER <[EMAIL PROTECTED]>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


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

Re: Good communication with upstream is good idea

[James Westby]

On Mon, 2008-07-28 at 23:18 +1000, Ben Finney wrote:
> No, if the pages exist and other pages tend to treat them as
> interesting (i.e. interesting pages link to those pages), Google is
> working as advertised if it indexes and reports them.

On unactivated account pages launchpad now sets

  

so these pages should not show up in results from well behaved
search engines.

Thanks,

James


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

Bug#492727: ITP: uuidm -- Universally unique identifiers for OCaml

[Sylvain Le Gall]

Package: wnpp
Severity: wishlist
Owner: Sylvain Le Gall <[EMAIL PROTECTED]>


* Package name: uuidm
  Version : 0.9.1
  Upstream Author : Daniel C. Bünzli
* URL : http://erratique.ch/software/uuidm
* License : BSD
  Programming Lang: OCaml
  Description : Universally unique identifiers for OCaml

 This library is an OCaml module implementing 128 bits universally
 unique identifiers (uuid) version 3, 5 (name based with MD5, SHA-1
 hashing) and 4 (random based) according to RFC 4122.  
 .
 This package contains header and OCaml library.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)




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

Re: Good communication with upstream is good idea

[Ben Finney]

Florian Weimer <[EMAIL PROTECTED]> writes:

> * Russ Allbery:
> 
> > Unfortunately, this then generates a whole pile of web pages
> > supposedly for "you" that then show up in Google searches and the
> > like despite having no information on them. I think that's one of
> > the things that's turned DDs off on Launchpad; I know that it gave
> > me a bad initial impression.
> 
> I guess it's more of a Google QA issue

No, if the pages exist and other pages tend to treat them as
interesting (i.e. interesting pages link to those pages), Google is
working as advertised if it indexes and reports them.

The problem is the treatment of this information by Launchpad, i.e.
creating pages that have no prospect of being useful, yet linking to
them (I presume, from the discussion here) as though they're
important.

-- 
 \ “To label any subject unsuitable for comedy is to admit |
  `\   defeat.” —Peter Sellers |
_o__)  |
Ben Finney


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

Re: Good communication with upstream is good idea

[Florian Weimer]

* Russ Allbery:

> Unfortunately, this then generates a whole pile of web pages supposedly
> for "you" that then show up in Google searches and the like despite having
> no information on them.  I think that's one of the things that's turned
> DDs off on Launchpad; I know that it gave me a bad initial impression.

I guess it's more of a Google QA issue, but I see what you mean.  I
agree that this is a strange situation.


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

Re: procinfo maintainership

[Bernd Zeimetz]

>> So who do I need to contact to find a debian package maintainer for a)
>> procinfo-18 b) procinfo-ng ?

did you try to contact the maintainer of procinfo? If they're not
interested, look at  http://www.debian.org/devel/wnpp/

-- 
 Bernd Zeimetz   Debian GNU/Linux Developer
 GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79


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

Re: No announcement for etch&half seen ?

[Cyril Brulebois]

Olivier Berger <[EMAIL PROTECTED]> (28/07/2008):
> I haven't noticed any announcement sent to [EMAIL PROTECTED] about "Debian
> GNU/Linux 4.0 updated and support for newer hardware added"
> (http://lists.debian.org/debian-announce/2008/msg3.html) ...
> maybe this is a user news mostly, but doesn't hurt to notify devs,
> IMHO.

Well, d-a is so low traffic that if you're interested in user news, you
really should subscribe.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#492701: ITP: libwx-perl-processstream-perl -- access IO of external processes via events (Wx::Perl module)

[Damyan Ivanov]

Package: wnpp
Severity: wishlist
Owner: Damyan Ivanov <[EMAIL PROTECTED]>

* Package name: libwx-perl-processstream-perl
  Version : 0.11
  Upstream Author : Mark Dootson, 
* URL : http://search.cpan.org/dist/Wx-Perl-ProcessStam-0.11/
* License : Same as Perl (GPL-1+|Artistic)
  Programming Lang: Perl
  Description : access IO of external processes via events (Wx::Perl module)

  Wx::Perl::ProcessStream provides the STDOUT, STDERR and exit codes of
  asynchronously running processes via events. It may be used for long
  running or blocking processes that provide periodic updates on state
  via STDOUT.  Simple IPC is possible via STDIN.

Package to be maintained under Debian Perl Group's umbrella.



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

No announcement for etch&half seen ?

[Olivier Berger]

Hi.

I haven't noticed any announcement sent to [EMAIL PROTECTED] about "Debian
GNU/Linux 4.0 updated and support for newer hardware
added" (http://lists.debian.org/debian-announce/2008/msg3.html) ... 
maybe this is a user news mostly, but doesn't hurt to notify devs, IMHO.

In any case, you're aware now ;)

Best regards,
-- 
Olivier BERGER <[EMAIL PROTECTED]>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


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

Bug#492696: ITP: padre -- Perl Application Development and Refactoring Environment

[Damyan Ivanov]

Package: wnpp
Severity: wishlist
Owner: Damyan Ivanov <[EMAIL PROTECTED]>

* Package name: padre
  Version : 0.2
  Upstream Author : Gabor Szabo http://www.szabgab.com/
* URL : http://search.cpan.org/dist/Padre/
* License : Same as Perl5 (GPL-1+|Artistic)
  Programming Lang: Perl
  Description : Perl Application Development and Refactoring Environment

  A simple editor for Perl, written in Perl and using WxWidgets.
  .
  Still in early stages of development, but useful regardless.

It seems to me that the package is more an application than a set of
Perl modules so perhaps it is not suitable for pkg-perl. Of course, I'd
be more than happy to maintain it there, in a well-developed
environment, if there are no objections :)

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)



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