On Wed, 13 Jul 2005, Joerg Jaspert wrote:
While checking your package in NEW I found that it has the cdbs "Play with
my debian/control in a bad way" option turned on, and thus modifies
Build-Dependencies on the fly.
[...]
You may want to follow bug #311724, which is about exactly this issue.
On 10350 March 1977, Martin-Eric Racine wrote:
>> You may want to follow bug #311724, which is about exactly this issue.
> Understood, but out of my hands; it appears to be a CDBS issue.
Yep, including this feature is a cdbs mistake. Using it is a maintainer mistake.
> The last version of the de
I just updated to X.org. With apt. Automatically. Woohoo!! I mean full
on xserver-xorg too. I did not touch ANYTHING.
X team you rock. This is why I started using Debian 7 years ago. This is
what keeps me here.
One and only one snag. purging the xfree86-common package failed because
it was t
Hello,
my congratulation to the team too. However I was not as fortunate as the
Sean.
What about the xlibmesa-glu packages? Can we expect them to enter the
archive again? Else I have to remove some of my shiny GL applications
(crystalspace, freewrl, libdevil,...)
Greetings Ben
--
Please do no
On Thu, Jul 14, 2005 at 10:17:24AM +0200, Benjamin Mesing wrote:
> What about the xlibmesa-glu packages? Can we expect them to enter the
> archive again? Else I have to remove some of my shiny GL applications
> (crystalspace, freewrl, libdevil,...)
Build-dep on "libglu1-xorg-dev | libglu-dev", and
* Mattia Dongili
| - setting the CPUFreq policy must be done as early as possible in the
| boot process (IMHO)
Why? This looks just like an opinion without any rationale.
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky a
On Thu, Jul 14, 2005 at 10:17:24AM +0200, Benjamin Mesing wrote:
> my congratulation to the team too. However I was not as fortunate as the
> Sean.
>
Me too, at least on this machine I had to explicitly install
xserver-xorg to complete the move. BTW, I see the rendering of some ttf
fonts looks no
On Wed, 13 Jul 2005, Matt Kraai wrote:
> texi2html's behavior changed recently: if it is invoked with
> -split=chapter, old versions place the HTML files in the same
> directory as the documentation source, whereas new versions place the
> generated files in a subdirectory.
>
> After I'd filed a
* Francesco P. Lovergine:
> Me too, at least on this machine I had to explicitly install
> xserver-xorg to complete the move. BTW, I see the rendering of some ttf
> fonts looks not so good. For instance I used happily this resource:
>
> XTerm*Font: -monotype-andale mono-medium-r-normal--15-0-0-0-c
Robert Jordens writes:
> Hello!
>
> [Tue, 05 Jul 2005] Matthias Klose wrote:
>
> > - - 5-day NMU for all C++ library packages, which can be converted, but
> > are left alone.
> >
> > i.e. if libfoo1++ depends on libbar1++, libfoo1++ can be NMU'ed 5 days
> > after libbar1++ is uploaded.
>
> S
On Thu, 14 Jul 2005, Joerg Jaspert wrote:
On 10350 March 1977, Martin-Eric Racine wrote:
You may want to follow bug #311724, which is about exactly this issue.
Understood, but out of my hands; it appears to be a CDBS issue.
Yep, including this feature is a cdbs mistake. Using it is a mainta
On 10350 March 1977, Martin-Eric Racine wrote:
>>> Doing an NMU on CDBS to fix #311724 might be a more constructive approach
>>> than asking everyone who uses CDBS with debian/control.in to go and fix
>>> their package's static debian/control for absolutely no gain, given how it
>>> will be overwr
On Thu, 14 Jul 2005, Sean Perry wrote:
> I just updated to X.org. With apt. Automatically. Woohoo!! I mean full
> on xserver-xorg too. I did not touch ANYTHING.
My only gripe is that the upload did not have pciids for
radeon X700 etc.
http://lists.debian.org/debian-x/2005/06/msg00179.html
N
* Matt Kraai ([EMAIL PROTECTED]) [050714 02:21]:
> texi2html's behavior changed recently: if it is invoked with
> -split=chapter, old versions place the HTML files in the same
> directory as the documentation source, whereas new versions place the
> generated files in a subdirectory.
>
> After I'd
On Mon, Jul 11, 2005 at 11:50:14AM -0400, David Nusinow wrote:
> What I'd like to see is no more new items added to that list without
> someone signing up and taking responsibility for them. What I really want
> to see more than anything with that list is for each and every item to have
> at leas
Jon Dowland <[EMAIL PROTECTED]> writes:
> I suggest having __two__ lists: a wishlist and a worklist (with the
> latter being the existing TODOlist)
A decent idea, since items can be moved back and forth as needed.
--
Stig Sandbeck Mathisen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Package: wnpp
Severity: wishlist
Owner: Mark Purcell <[EMAIL PROTECTED]>
* Package name: asterisk-sounds
Version : 1.0.9
Upstream Author : [EMAIL PROTECTED]
* URL :
http://www.asterisk.org/html/downloads/asterisk-sounds-1.0.9.tar.gz
* License : BSD
Descriptio
I see that yesterday a modularized xserver (xorg) entered ubuntu
breezy (the current development branch) archives.
I've some questions: Is XSF coordinating its work with them or what ?
Is modularized xorg a goal for us ? I think that it's easy to do since
some if not all xorg ubuntu maintainers ar
Hi,
Mark Purcell schrieb:
> * Package name: asterisk-sounds
Please name it asterisk-sounds-extra, as there is already a virtual
package called "asterisk-sounds". Also, I suppose these are not spoken
by Allison, in which cade this should be mentioned in the description.
Simon
--
To UNS
On Thu, Jul 14, 2005 at 11:02:09AM -0300, Gustavo Franco wrote:
> I see that yesterday a modularized xserver (xorg) entered ubuntu
> breezy (the current development branch) archives.
>
> I've some questions: Is XSF coordinating its work with them or what ?
> Is modularized xorg a goal for us ? I t
On 7/14/05, Daniel Stone <[EMAIL PROTECTED]> wrote:
>
> The server hasn't been modularised yet, it's just that I split up all
> the packaging. I've been working closely with Josh Triplett on the
> libraries, and keeping David fully in the loop with everything I'm doing
> in Breezy, and I'm pretty
Hi Anand,
On Fri, Jul 15, 2005 at 12:32:54AM +1000, Anand Kumria wrote:
> Thanks for your comments -- however I don't think anyone should be able
> afraid to point out when a debian developer is obviously not able to
> satisfy all the Debian-related demands on their time; let alone their
> commit
Hi Torsten,
Thanks for your comments -- however I don't think anyone should be able
afraid to point out when a debian developer is obviously not able to
satisfy all the Debian-related demands on their time; let alone their
committments.
>From http://www.debian.org/intro/organization> you can vari
On Thu, Jul 14, 2005 at 11:02:09AM -0300, Gustavo Franco wrote:
> I see that yesterday a modularized xserver (xorg) entered ubuntu
> breezy (the current development branch) archives.
It's exciting stuff, but my primary goal is to get the current X.Org
release in to etch.
> I've some questions: Is
On Thu, Jul 14, 2005 at 12:08:00PM +0200, Francesco P. Lovergine wrote:
> On Thu, Jul 14, 2005 at 10:17:24AM +0200, Benjamin Mesing wrote:
> > my congratulation to the team too. However I was not as fortunate as the
> > Sean.
> >
>
> Me too, at least on this machine I had to explicitly install
>
On Thu, Jul 14, 2005 at 02:41:18PM +0300, Jaakko Niemi wrote:
> On Thu, 14 Jul 2005, Sean Perry wrote:
> > I just updated to X.org. With apt. Automatically. Woohoo!! I mean full
> > on xserver-xorg too. I did not touch ANYTHING.
>
> My only gripe is that the upload did not have pciids for
> rad
On Thu, Jul 14, 2005 at 12:42:54AM -0700, Sean Perry wrote:
> I just updated to X.org. With apt. Automatically. Woohoo!! I mean full
> on xserver-xorg too. I did not touch ANYTHING.
>
> X team you rock. This is why I started using Debian 7 years ago. This is
> what keeps me here.
>
> One and on
Hi,
I'll just write a mail here to notify people using pbuilder, that
sid is a wild place.
My testsuite tells me that currently Debian sid/etch is not
debootstrap'able. This is due to several problems,
including g++ ABI transition breaking aptitude.
However, the good news is that you should b
Hello,
Anand Kumria wrote:
Thanks for your comments -- however I don't think anyone should be able
afraid to point out when a debian developer is obviously not able to
satisfy all the Debian-related demands on their time; let alone their
committments.
First of all, in my opinion your mail nev
[I am stopping the cross-posting to -release, as -release is no
discussion list]
On 2005-07-14 Junichi Uekawa <[EMAIL PROTECTED]> wrote:
> I'd like to propose, for new -dev packages, to
> name -dev packages after their runtime library counterparts.
>
> If the library package is named lib$NAME,
>
On Thu, 14 Jul 2005 13:13:49 +0200, BJoerg Jaspert <[EMAIL PROTECTED]>
wrote:
>And now please go and read my reject mail again - I propose a way for
>people who really need help to set the correct Build-Depends.
The way you propose in your original bug report must be made possible
by a CDBS change
On Wed, July 13, 2005 04:04, Nigel Jones wrote:
>> Or, should you find the demands on your time too pressing, why not use
>> this opportunity to step-aside as the Debian press contact.
> Love the pun, but IMHO he does a good job.
I do not - while I don't want to judge Joey's skills, for me it's a
Hi Steve,
Thanks for your email. I'd like to say touche but I basically believe
you are wrong. Unfortunately I found from past-personal experience that
email to busy people is generally ignored unless brought to their
attention.
Additionally personal personality conflicts between myself and pre
On Thu, July 14, 2005 17:20, Thijs Kinkhorst wrote:
> On Wed, July 13, 2005 04:04, Nigel Jones wrote:
>> but IMHO he does a good job.
>
> I do not -
of couse I meant "I do not agree"... :-)
Thijs
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [
Package: wnpp
Severity: wishlist
Owner: Federico Di Gregorio <[EMAIL PROTECTED]>
* Package name: baobab
Version : 1.0.0
Upstream Author : Fabio Marzocca <[EMAIL PROTECTED]>
* URL : http://www.marzocca.net/linux/baobab.html
* License : GPL
Description : gra
Hi,
I'd like to propose, for new -dev packages, to
name -dev packages after their runtime library counterparts.
If the library package is named lib$NAME,
call the -dev package lib$NAME-dev.
For example,
libxxx0 will have
libxxx0-dev.
libfoobar-2.1-0 will have
libfoobar-2.1-0-dev.
This
On Thu, Jul 14, 2005 at 02:55:48PM +0200, Stig Sandbeck Mathisen wrote:
> Jon Dowland <[EMAIL PROTECTED]> writes:
>
> > I suggest having __two__ lists: a wishlist and a worklist (with the
> > latter being the existing TODOlist)
>
> A decent idea, since items can be moved back and forth as needed.
* Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> I'd like to propose, for new -dev packages, to
> name -dev packages after their runtime library counterparts.
Uh, no? The -dev packages have no need to match to a specific runtime
library and this just creates unnecessary work.
> This allows mechani
On Thu, 2005-07-14 at 20:16 +0900, Junichi Uekawa wrote:
> I'd like to propose, for new -dev packages, to
> name -dev packages after their runtime library counterparts.
I personally found it very handy that the dev packages automatically
selects the most recent API compatible version. Why do you
Hi,
> > I'd like to propose, for new -dev packages, to
> > name -dev packages after their runtime library counterparts.
> >
> > If the library package is named lib$NAME,
> > call the -dev package lib$NAME-dev.
> [...]
>
> Hej,
> The obvious downside of this is that the name of dev-package will
On 7/14/05, Christian Fromme <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Anand Kumria wrote:
>
> > Thanks for your comments -- however I don't think anyone should be able
> > afraid to point out when a debian developer is obviously not able to
> > satisfy all the Debian-related demands on their time;
Hi,
> * Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> > I'd like to propose, for new -dev packages, to
> > name -dev packages after their runtime library counterparts.
>
> Uh, no? The -dev packages have no need to match to a specific runtime
> library and this just creates unnecessary work.
Well
On Thu, 2005-07-14 at 17:57 +0200, Olaf van der Spek wrote:
> On 7/14/05, Christian Fromme <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > Anand Kumria wrote:
> >
> > > Thanks for your comments -- however I don't think anyone should be able
> > > afraid to point out when a debian developer is obvio
* Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> There may be other showstoppers.
What does doing this solve? What does it even help with?
> I would really like this 10-year old non-regulation to
> go to a concensus (it is indeed rather embarassing we don't
> agree on a good solution after 10 yea
* Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> > * Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> > > I'd like to propose, for new -dev packages, to
> > > name -dev packages after their runtime library counterparts.
> >
> > Uh, no? The -dev packages have no need to match to a specific runtime
> > li
* Olaf van der Spek:
>> First of all, in my opinion your mail never should have gone to -devel,
>> but only to Martin Schulze and maybe to Branden Robinson.
>
> Why can't this be discussed in public? There are probably more people
> concerned about this then only him.
It's considered bad style to
Junichi Uekawa <[EMAIL PROTECTED]> writes:
> Hi,
>
>> > I'd like to propose, for new -dev packages, to
>> > name -dev packages after their runtime library counterparts.
>> >
>> > If the library package is named lib$NAME,
>> > call the -dev package lib$NAME-dev.
>> [...]
>>
>> Hej,
>> The obvio
[once more, doesn't belong on -release...]
On Thu, Jul 14, 2005 at 12:11:21PM -0400, Stephen Frost wrote:
> * Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> > > * Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> > > > I'd like to propose, for new -dev packages, to
> > > > name -dev packages after their r
Hi,
> > There may be other showstoppers.
>
> What does doing this solve? What does it even help with?
Hmmm... we are talking about naming
Debian development shareed library package names based on
Debian runtime shared library package names.
>
> > I would really like this 10-year old non-reg
Hi,
> > I'd like to propose, for new -dev packages, to
> > name -dev packages after their runtime library counterparts.
>
> I personally found it very handy that the dev packages automatically
> selects the most recent API compatible version. Why do you want this
> switch by the way? You did not
On Thursday 14 July 2005 17:14, Junichi Uekawa wrote:
> The current recommendation I'm trying to give is:
>
> Package: libXXX-dev
> Conflicts: libXXX-dev
> Provides: libXXX-dev
>
>
> Thus, it won't contradict with your requirement to
> be able to just build-depend on libXXX-dev.
I may be wron
Hi,
> You can (and it is often done) extend an api to include more
> functionality without breaking the existing api. Any program using one
> of the new functions must use a versioned depend on the libfoo-dev
> package introducing the function.
>
> The API can (and will) even stay compatibly acro
* Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> > > There may be other showstoppers.
> >
> > What does doing this solve? What does it even help with?
>
> Hmmm... we are talking about naming
> Debian development shareed library package names based on
> Debian runtime shared library package names.
* Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> BTW, having Build-Depends: libfoo-dev in
> a library's build-deps, will allow the developer
> to overlook a soname change in depending shared library.
> Which is a bad idea in the QA standpoint.
Uh, no it isn't. SONAME changes are fine, the package h
Hi,
> > 2. The information of -dev packages depending on other -dev packages
> > cannot be automatically determined currently;
> > it should be possible to obtain a minimal list by analyzing the
> > NEEDED field of the objdump output.
>
> Errr, -dev packages generally don't (and shouldn't) depe
* Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> The current recommendation I'm trying to give is:
>
> Package: libXXX-dev
> Conflicts: libXXX-dev
> Provides: libXXX-dev
>
>
> Thus, it won't contradict with your requirement to
> be able to just build-depend on libXXX-dev.
Uhh, then it doesn't
Adobe Creative Suite CS CE Premium Edition - $99
Autocad 2006 - $69.95
Roxio Easy Media Creator 7.0 - $19.95
Nero Burning Rom 6.6.0.5 - $19.95
and much more. at http://replacesoft.com/?a=3331 with fr e e e bonus.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
#include
* Will Newton [Thu, Jul 14 2005, 05:36:05PM]:
> > Thus, it won't contradict with your requirement to
> > be able to just build-depend on libXXX-dev.
>
> I may be wrong, but I thought it was incorrect to build-dep only on a pure
> virtual package? e.g.:
>
> Build-Depend: xlibmesa-gl-de
Microsoft Digital Image Suite Pro v10.0 - $19.95
Microsoft Autoroute 2005 DvD UK - $19.95
Microsoft Office System Professional 2003 - $54.95
Microsoft Digital Image Suite Pro v10.0 - $19.95
and much more. at http://replacesoft.com/?a=3331 with fr e e e bonus.
--
To UNSUBSCRIBE, email to
"Francesco P. Lovergine" <[EMAIL PROTECTED]> writes:
> On Thu, Jul 14, 2005 at 10:17:24AM +0200, Benjamin Mesing wrote:
>> my congratulation to the team too. However I was not as fortunate as the
>> Sean.
>>
>
> Me too, at least on this machine I had to explicitly install
> xserver-xorg to comple
Get the medication you need delivered to your door in 24 hours.
http://ffyw.vag6hwv6snd3hed.upwhircadmh.net
Creativity comes from trust. Trust your instincts.
Age isÂ…wisdom, if one has lived one's life properly.
God gives us our relatives--thank God he lets us choose our friends.
Will Newton <[EMAIL PROTECTED]> writes:
> On Thursday 14 July 2005 17:14, Junichi Uekawa wrote:
>
>> The current recommendation I'm trying to give is:
>>
>> Package: libXXX-dev
>> Conflicts: libXXX-dev
>> Provides: libXXX-dev
>>
>>
>> Thus, it won't contradict with your requirement to
>> be ab
Junichi Uekawa <[EMAIL PROTECTED]> writes:
> Having a solid naming scheme will allow me to
>
> ldd /usr/lib/libwhatever.so to track down its
> shared library dependency, and appending "-dev"
> to individual package to create the list of
> requisite -dev packages.
With the current scheme it is:
Junichi Uekawa <[EMAIL PROTECTED]> writes:
> BTW, having Build-Depends: libfoo-dev in
> a library's build-deps, will allow the developer
> to overlook a soname change in depending shared library.
> Which is a bad idea in the QA standpoint.
Yes and no.
The programer can overlook the soname chang
On Wed, Jul 13, 2005 at 11:11:49AM +0200, Florian Weimer wrote:
> * Anand Kumria:
>
> > [1]: > http://smh.com.au/news/breaking/debian-debates-support-for-ports/2005/07/12/1120934228145.html>
>
> Apparently, this is subscription only. 8-(
>
> Has this article been republished by another newspape
On Wed, Jul 13, 2005 at 08:48:44PM -0400, Charles Fry wrote:
> * License : The Open Group Test Suite License
I'm not optimistic about this licence being DFSG-free.
- Matt
signature.asc
Description: Digital signature
On Thu, Jul 14, 2005 at 11:21:52AM +0200, Tollef Fog Heen wrote:
> * Mattia Dongili
>
> | - setting the CPUFreq policy must be done as early as possible in the
> | boot process (IMHO)
>
> Why? This looks just like an opinion without any rationale.
It's dumb anyway. If you wanted it set early
On Thu, Jul 14, 2005 at 12:03:00PM -0400, Greg Folkert wrote:
> On Thu, 2005-07-14 at 17:57 +0200, Olaf van der Spek wrote:
> > On 7/14/05, Christian Fromme <[EMAIL PROTECTED]> wrote:
> > > Anand Kumria wrote:
> > >
> > > > Thanks for your comments -- however I don't think anyone should be able
>
On Thu, 2005-07-14 at 00:42 -0700, Sean Perry wrote:
> I just updated to X.org. With apt. Automatically. Woohoo!! I mean full
> on xserver-xorg too. I did not touch ANYTHING.
>
> X team you rock. This is why I started using Debian 7 years ago. This is
> what keeps me here.
>
> One and only one
On Thu, 2005-07-14 at 21:25 +0100, Andrew Suffield wrote:
> On Thu, Jul 14, 2005 at 12:03:00PM -0400, Greg Folkert wrote:
> > On Thu, 2005-07-14 at 17:57 +0200, Olaf van der Spek wrote:
> > > On 7/14/05, Christian Fromme <[EMAIL PROTECTED]> wrote:
> > > > Anand Kumria wrote:
> > > >
> > > > > Than
On Thursday 14 July 2005 15:12, Simon Richter wrote:
> Please name it asterisk-sounds-extra, as there is already a virtual
> package called "asterisk-sounds". Also, I suppose these are not spoken
> by Allison, in which cade this should be mentioned in the description.
Simon,
Yes I discovered thi
Package: wnpp
Severity: wishlist
Owner: Mark Purcell <[EMAIL PROTECTED]>
* Package name: asterisk-sounds-moh
Version : 20050715
Upstream Author : Enjoy Elena Kuschnerova and Lev Guelbard
* URL : http://www.signate.com/moh.php
* License : Public Domain
Descript
On Thu, Jul 14, 2005 at 11:43:50AM -0300, Gustavo Franco wrote:
> On 7/14/05, Daniel Stone <[EMAIL PROTECTED]> wrote:
> > The server hasn't been modularised yet, it's just that I split up all
> > the packaging. I've been working closely with Josh Triplett on the
> > libraries, and keeping David fu
Hello.
I would like to move one subject. What are the required skills of the
developers/developers-to-be?
Debian Policy, Developers' Reference, New Maintainers' Guide and most
documentation describe only _how to make a good package_.
Good package in that case means it will comply with Debian P
On 7/14/05, Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> wrote:
> In sum. Maybe it's time to create additional positions in Debian project?
> Maybe something like Packager (with knowledge about Bash and Debian
> Policy), Translator (with knowledge about some particular language and
> English), Help
Hi Bartosz,
On Fri, 2005-07-15 at 01:52 +0200, Bartosz Fenski aka fEnIo wrote:
> What are the required skills of the
> developers/developers-to-be?
Skip, as we both passed the NM process.
> should everyone be able to maintain every package on the world?
No, packaging is not just put the right f
FWIW, I previously had xorg from Ubuntu installed, and upgrading from
that to Debian's xorg _didn't_ go smoothly: the file "/etc/X11/Xsession"
was created by two packages, x11-common [debian], and xorg-common
[ubuntu], and in upgrading tried to install x11-common before removing
xorg-common.
I en
> "Junichi" == Junichi Uekawa <[EMAIL PROTECTED]> writes:
Junichi> Hi, I'll just write a mail here to notify people using
Junichi> pbuilder, that sid is a wild place.
I recently had major dramas trying to create a sid chroot from a sarge
system. So perhaps these issues have been fixed
> "Greg" == Greg Folkert <[EMAIL PROTECTED]> writes:
Greg> Common Courtesy states that one should also mention personal
Greg> communications, even if completely ignored by the person(s)
Greg> in question.
Doesn't this also run the risk of making the person look bad?
I guess it de
Howdy,
The aspell dictionary packages build-depend on aspell-bin (>> 0.60).
aspell-bin is now a virtual package provided by aspell, but virtual
packages cannot be versioned, so these build-dependency cannot be
satisfied.
There are fifteen such packages:
aspell-br
aspell-cy
aspell-de
aspell-d
On Fri, Jul 15, 2005 at 11:54:15AM +1000, Brian May wrote:
> Ideally there needs to be either
>
> * a login environment where changes are saved AND/OR
there is one: use
pbuilder login --save-after-login
(have been confronted with the same problem yesterday...)
--
c u
henning
--
To UNSUBSCR
also sprach Junichi Uekawa <[EMAIL PROTECTED]> [2005.07.14.1416 +0300]:
> libfoobar-2.1-0 will have
> libfoobar-2.1-0-dev.
Please distinguish between API and ABI!
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud
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: 215 (new: 2)
Total number of packages offered up for adoption: 112 (new: 11)
Total number of packages reques
83 matches
Mail list logo
