Bug#304291: ITP: libtk-splashscreen-perl -- Toplevel mega widget to display a splashscreen

Package: wnpp Severity: wishlist Owner: Carlo Segre <[EMAIL PROTECTED]> * Package name: libtk-splashscreen-perl Version : 1.0 Upstream Author : Stephen O. Lidie <[EMAIL PROTECTED]> * URL : http://cpan.perl.org/CPAN/authors/id/L/LU/LUSOL/ * License : GPL / Artis

Bug#304289: ITP: libtk-pod-perl -- Tk Pod browser widget with hypertext capability

Package: wnpp Severity: wishlist Owner: Carlo Segre <[EMAIL PROTECTED]> * Package name: libtk-pod-perl Version : 0.9929 Upstream Author : Slaven Rezic <[EMAIL PROTECTED]> * URL : http://cpan.perl.org/CPAN/authors/id/S/SR/SREZIC/ * License : GPL / Artistic Des

Re: lintian & linda (was: Automatic testing of Debian packages)

On Mon, 11 Apr 2005, Martin Schulze wrote: Why are there Vi and Emacs? Different taste of the users - valid reason. Why are there Perl and Python? Different taste of programmers - valid reason. Why are there viewcvs and cvsweb? Why are there cvs-syncmail and cvs-mailcommit? Why are there tkirc and

Bug#304288: ITP: libtk-histentry-perl -- Implements an entry widget with history

Package: wnpp Severity: wishlist Owner: Carlo Segre <[EMAIL PROTECTED]> * Package name: libtk-histentry-perl Version : 0.42 Upstream Author : Slaven Rezic <[EMAIL PROTECTED]> * URL : http://cpan.perl.org/CPAN/authors/id/S/SR/SREZIC/ * License : GPL / Artistic

Bug#304287: ITP: libtk-gbarr-perl -- Various Tk Perl widgets

Package: wnpp Severity: wishlist Owner: Carlo Segre <[EMAIL PROTECTED]> * Package name: libtk-gbarr-perl Version : 2.06 Upstream Author : Slaven Rezic <[EMAIL PROTECTED]> * URL : http://cpan.perl.org/CPAN/authors/id/S/SR/SREZIC/ * License : GPL / Artistic Des

Re: Introducing Ichthux as a possibly new CDD

On Tue, 12 Apr 2005, [ISO-8859-1] Raphaël Pinson wrote: We are now thinking of making Ichthux a CDD, and include it as such in the Debian project. According to your forewarded letter this would make sense. Any comments and ideas are welcome :) If I were you I would start with reading http://p

T-Shirt Affiliate Program and Link Exchange

Dear Debian Devel, I visited debian.org today, and think you would make a good affiliate and link partner. We pay you 10% of any sale that comes from anyone who clicks our banner on your site and we will include a reciprocal link on our links page: http://www.tshirtinsanity.com/links.asp If yo

Re: etch release target: SELinux?? (was: Re: Bits (Nybbles?) from the Vancouver release team meeting)

On Mon, Apr 11, 2005 at 09:46:37PM +0200, Javier Fernández-Sanguino Peña wrote: > On Mon, Apr 11, 2005 at 11:50:23PM +1000, Russell Coker wrote: > > > > For people who don't use SE Linux the support in those programs will only > > take > > a few K of disk space and will not give a performance ov

Bug#304271: ITP: lighttpd -- a secure, fast, compliant and very flexible web-server

Package: wnpp Severity: wishlist Owner: "Steven R. Baker" <[EMAIL PROTECTED]> * Package name: lighttpd Version : 1.3.13 Upstream Author : [EMAIL PROTECTED] * URL : http://www.lighttpd.net/ * License : MIT/X Description : a secure, fast, compliant and very

Bug#304270: ITP: libfishsound -- simple programming interface that wraps Xiph.Org audio codecs

Package: wnpp Severity: wishlist Owner: Jamie Wilkinson <[EMAIL PROTECTED]> * Package name: libfishsound Version : 0.6.3 Upstream Author : Conrad Parker <[EMAIL PROTECTED]>, Silvia Pfeiffer <[EMAIL PROTECTED]> Zentaro Kavanagh <[EMAIL PROTECT

Bug#304266: ITP: sdate -- never ending september date

Package: wnpp Severity: wishlist Owner: Christoph Berg <[EMAIL PROTECTED]> * Package name: sdate Version : 0.1 Upstream Author : Christoph Berg <[EMAIL PROTECTED]> * URL : http://www.df7cb.de/projects/sdate/ * License : GPL Description : never ending septe

Re: Introducing Ichthux as a possibly new CDD

I'm very interested in this work. I am already involved in two different Christian ministries that might be able to make use of Ichthux, and have some ideas for others. Ben signature.asc Description: This is a digitally signed message part

Introducing Ichthux as a possibly new CDD

Hi all, I'm Raphaël Pinson, from the Ichthux project (http://ichthux.free.fr). The ichthux project was started some week ago, gathering already existing Christian Linux Projects. Its goal is to release a Debian-based OS focusing on Christianity. I'm enclosing to this message the post that was sen

Re: Bug#304220: ITP: libqt4lab -- Qt4Lab plugin library

On Mon, Apr 11, 2005 at 09:05:56PM +0200, Fathi BOUDRA wrote: > I'm looking for a sponsor for my qt4lab package. > The project seems already promising, and there's a collaboration > with qwt project. > > You can find my package here : > http://fboudra.free.fr/debian/ > > best regards, > > Fathi

Re: lintian & linda (was: Automatic testing of Debian packages)

* [ 11-04-05 - 22:03 ] Nico Golde <[EMAIL PROTECTED]> wrote: > * Martin Schulze <[EMAIL PROTECTED]> [2005-04-11 22:00]: > > Why are there Vi and Emacs? > > Why are there Perl and Python? > [...] > But thats not my problem. The programs etc. you showed are very > different in using, look etc

Re: lintian & linda (was: Automatic testing of Debian packages)

* Martin Schulze <[EMAIL PROTECTED]> [2005-04-11 22:00]: > Nico Golde wrote: > > There is another thing that I don't understand often. Why > > are there linda and lintian? > > In my opinion this makes things difficulter. Both have to > > coordinate themselves and keep their policy rules up to > > d

Re: etch release target: SELinux?? (was: Re: Bits (Nybbles?) from the Vancouver release team meeting)

On Mon, Apr 11, 2005 at 11:50:23PM +1000, Russell Coker wrote: > > For people who don't use SE Linux the support in those programs will only > take > a few K of disk space and will not give a performance overhead. Given the fact that the current standard installation installs both gcc, gdb and

Bug#304220: ITP: libqt4lab -- Qt4Lab plugin library

Package: wnpp Severity: wishlist Owner: Fathi BOUDRA <[EMAIL PROTECTED]> Hi, I'm looking for a sponsor for my qt4lab package. The project seems already promising, and there's a collaboration with qwt project. You can find my package here : http://fboudra.free.fr/debian/ best regards, Fathi *

Re: lintian & linda

In article <[EMAIL PROTECTED]> you wrote: > There are some but in my opinion this is *not* the way open > source works in general. The program is designed for users > and users in most cases don't recognize in which language > the program is written. No open source is not about the user it is abou

Re: lintian & linda (was: Automatic testing of Debian packages)

Nico Golde wrote: > There is another thing that I don't understand often. Why > are there linda and lintian? > In my opinion this makes things difficulter. Both have to > coordinate themselves and keep their policy rules up to > date. Why are there Vi and Emacs? Why are there Perl and Python? Why

Bug#304218: ITP: drawtiming -- tool for documenting hardware designs through timing diagrams

Package: wnpp Severity: wishlist Owner: "Wesley J. Landaker" <[EMAIL PROTECTED]> * Package name: drawtiming Version : 0.3 Upstream Author : Edward Counce <[EMAIL PROTECTED]> * URL : * License : GPL Description : tool fo

Re: Bug#302309: ITP: bcron -- Bruce's cron system

On Sun, 10 Apr 2005, Steve Greenland wrote: > On 10-Apr-05, 10:55 (CDT), Reinhard Tartler <[EMAIL PROTECTED]> wrote: > > On Apr 8, 2005 12:05 AM, Steve Greenland <[EMAIL PROTECTED]> wrote: > > > > > Expect people to whine. I personally don't see why "@daily" is > > > significantly easier than "0 0

Re: please make ARM buildd more efficient, was Re: arm seems OK: release status?

Op ma, 11-04-2005 te 18:40 +0200, schreef Andrea Mennucc: > Paul TBBle Hampson wrote: > > I'm sure it's been suggested that the buildds remove the extra packages > > after each run, but that is considered too inefficient, and the buildds > > are not _expected_ to pick up all build-depends bugs. >

Re: arm seems OK: release status?

Op ma, 11-04-2005 te 23:36 +1000, schreef Paul TBBle Hampson: > On Mon, Apr 11, 2005 at 02:31:15PM +0200, A Mennucc wrote: > > when a buildd builds a package, it first install all > > build-dependencies, then compiles, then remove all build-dependencies. > > For my package, that was a total of 113

please make ARM buildd more efficient, was Re: arm seems OK: release status?

Paul TBBle Hampson wrote: On Mon, Apr 11, 2005 at 02:31:15PM +0200, A Mennucc wrote: when a buildd builds a package, it first install all build-dependencies, then compiles, then remove all build-dependencies. For my package, that was a total of 113 MB of data to be moved in and out of disks; since

Re: lintian & linda

Hello Marc, * Marc 'HE' Brockschmidt <[EMAIL PROTECTED]> [2005-04-11 15:08]: > Nico Golde <[EMAIL PROTECTED]> writes: > > Sometimes there is the case that major design decisions are > > too different from the original source so there is no other > > way. but is this the case with lintian and linda

Re: lintian & linda

Hello Bernd, * Bernd Eckenfels <[EMAIL PROTECTED]> [2005-04-11 15:09]: > In article <[EMAIL PROTECTED]> you wrote: > > Everybody agrees here, but (AFAIK) this is not the situation we are > > discussing. No 'Better Ideas' in linda. > > You have to see that in the context. Linda was written while l

Re: lintian & linda

Hello Bernd, * Bernd Eckenfels <[EMAIL PROTECTED]> [2005-04-11 15:07]: > In article <[EMAIL PROTECTED]> you wrote: > > Sure, but only if two projects have at least some differences; in 'The > > Cathedral and the Bazaar' popclient becomes fetchmail. > > There are a lot differences between linda an

Re: thank you for your support

Michael Banck a écrit : It is clear that Debian will have to change in order to face the issues it is confronted with, and I think the Vancouver proposal is a good starting point. It might need some fine-tuning, but I believe everybody is aware of that by now, so just screaming at the original pro

Re: lintian & linda

On Monday 11 April 2005 06:39 am, Steve Kowalik wrote: > 1) Proper English descriptions, rather than tags. > [EMAIL PROTECTED]:~% linda /var/cache/apt/archives/abiword_2.2.7-1_i386.deb   >   > E: abiword; No manual page for binary AbiWord-2.2. -i. Daniel -- /--- Daniel Burr

Re: lintian & linda

On Monday 11 April 2005 03:14 am, Ron Johnson wrote: > Then why was aptitude written?  Why not send patches against apt-get > and dselect? The correct question is why not send patches against console-apt, which you youngsters might not remember ;-). In fact, I did exactly that -- I sent about

Re: etch release target: SELinux?? (was: Re: Bits (Nybbles?) from the Vancouver release team meeting)

On Wednesday 16 March 2005 22:14, David Schmitt <[EMAIL PROTECTED]> wrote: > Just that it is not lost: SELinux soft support (patched utilities available > in main). There seems to be a repository that mostly works (I'm not in the > loop about currentness though) and it'd is probably an important s

Re: arm seems OK: release status?

On Mon, Apr 11, 2005 at 02:31:15PM +0200, A Mennucc wrote: > when a buildd builds a package, it first install all > build-dependencies, then compiles, then remove all build-dependencies. > For my package, that was a total of 113 MB of data to be moved in and > out of disks; since ARM is running lat

Re: Right of a maintainer not to respect FHS

On Sat, Apr 09, 2005 at 10:33:58PM +0200, Tollef Fog Heen wrote: > * Don Armstrong > | The maintainer is primarily responsible for the severity levels of the > | bugs in their package. Basically, the only exception[1] to this are > | the RMs, who may decide that a bug needs to be above or below th

Re: arm seems OK: release status?

when a buildd builds a package, it first install all build-dependencies, then compiles, then remove all build-dependencies. For my package, that was a total of 113 MB of data to be moved in and out of disks; since ARM is running late, maybe it would be wise to not remove build-dependencies at th

InterScan MSS has deleted a message

This notification has been sent to inform you that a message has been quarantined by MTEC company policies. Mail from: debian-devel@lists.debian.org Sent to: [EMAIL PROTECTED] Subject: Good day Reason: Global Policy, Antivirus Filter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subjec

Re: lintian & linda

Hi Lars, * [ 11-04-05 - 13:25 ] Lars Wirzenius <[EMAIL PROTECTED]> wrote: > ma, 2005-04-11 kello 13:19 +0200, Emanuele Rocca kirjoitti: > > It would be very nice to add these to linda's description. > > This way, every user can decide to install linda rather than lintian if > > they need thes

Retired!

Lesley Nicholls retired on the 30th April 2004. If you need to contact her re the Jane Kelley Chacmool Session, you can contact her through [EMAIL PROTECTED] All correspondence relating to the Department of Archaeology should be sent to Nicole Ethier at [EMAIL PROTECTED] -- To UNSUBSCRIBE,

Re: lintian & linda

ma, 2005-04-11 kello 13:19 +0200, Emanuele Rocca kirjoitti: > It would be very nice to add these to linda's description. > This way, every user can decide to install linda rather than lintian if > they need these specific features. Given that the two tools have different sets of tests, even if man

Re: lintian & linda

Hi Steve, * [ 11-04-05 - 12:39 ] Steve Kowalik <[EMAIL PROTECTED]> wrote: > On Mon, 11 Apr 2005 09:45:04 +0200, Emanuele Rocca uttered > > Everybody agrees here, but (AFAIK) this is not the situation we are > > discussing. No 'Better Ideas' in linda. > Speak for yourself. I obiouvsly speak

Bug#304160: O: toshutils

Package: wnpp Severity: normal I can't test toshutils any more, therefore I cannot meaningfully maintain it. Please find a nice home for it. Drew -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11 Loc

Re: lintian & linda

On Mon, 11 Apr 2005 09:45:04 +0200, Emanuele Rocca uttered > Everybody agrees here, but (AFAIK) this is not the situation we are > discussing. No 'Better Ideas' in linda. > Speak for yourself. Here are three (off the top of my head) that spring to mind that lintian can't do, and I feel better serv

Re: arm seems OK: release status?

In article <[EMAIL PROTECTED]> you wrote: > I would not have a problem to stop unstable building on architectures who > need to catch up on testing (especially since freezing testing would allow > them to catch up). Actually that was a bit missworded, I mean packages "destinated for testing" (i.e

Re: lintian & linda

Emanuele Rocca wrote: > * [ 11-04-05 - 09:14 ] Ron Johnson <[EMAIL PROTECTED]> wrote: > > ISTM that the good reason for writing-from-scratch duplicate > > functionality is if you have a Better Idea (better data structures, > > better interfaces, extra functionality, etc, etc) that are so > > f

Re: arm seems OK: release status?

In article <[EMAIL PROTECTED]> you wrote: > What's stopping the freeze is all the people uploading their low-priority > packages and keeping the arm autobuilders from ever catching up on the ones > that are actually medium and high priority. Why is that? Last explanation we seen here was, that hig

racoon-tool generates no config file for racoon

Hi, I'm using racoon-0.5-5 on debian/testing with 2.6.8-2-386 kernel. After installing ipsec-tools and racoon via apt-get, I added some lines to /etc/racoon/racoon-tool.conf (see below). Starting racoon with "racoon-tool start" shows: Loading IPSEC/crypto modules... IPSEC/crypto modules loaded.

Re: lintian & linda

In article <[EMAIL PROTECTED]> you wrote: > Everybody agrees here, but (AFAIK) this is not the situation we are > discussing. No 'Better Ideas' in linda. You have to see that in the context. Linda was written while lintian was not-so-good maintained. And of course if somebody decides to pick up a

Re: arm seems OK: release status?

Steve Langasek wrote: So I am curious : what is stopping the freeze now? testing-security? What's stopping the freeze is all the people uploading their low-priority packages and keeping the arm autobuilders from ever catching up on the ones that are actually medium and high priority. ARM is *

Re: arm seems OK: release status?

On Mon, 11 Apr 2005, Steve Langasek wrote: > What's stopping the freeze is all the people uploading their low-priority Nah, let's be fair. the real culprit is the especially crafted queue mishandling strategy used by the autobuilders, that works well only when the queue is almost empty and thus it

Re: arm seems OK: release status?

On Mon, Apr 11, 2005 at 09:25:56AM +0200, A Mennucc wrote: > reading the latest message on the status of the release > http://lists.debian.org/debian-devel-announce/2005/04/msg3.html > I understood that the release was near, and that, given good progress > with d-i and > testing-security, the

arm seems OK: release status?

hi reading the latest message on the status of the release http://lists.debian.org/debian-devel-announce/2005/04/msg3.html I understood that the release was near, and that, given good progress with d-i and testing-security, the main showstopper was the arm buildds trouble. (*) Yesterday I hav

Re: Upload of new stuff to unstable

On Sun, Apr 10, 2005 at 04:05:31PM +0200, Enrico Zini wrote: > I renamed libtagcoll-dev to libtagcoll1-dev and libdebtags-dev to > libdebtags1-dev, and I'm considering uploading to unstable in a day or > two: > > - it's too late for it to go in sid (good!) > - it doesn't break existing stuff (i

Re: lintian & linda

* [ 11-04-05 - 09:14 ] Ron Johnson <[EMAIL PROTECTED]> wrote: > ISTM that the good reason for writing-from-scratch duplicate > functionality is if you have a Better Idea (better data structures, > better interfaces, extra functionality, etc, etc) that are so > fundamental that You Can't Get Th

Re: lintian & linda

On Mon, 11 Apr 2005, Ron Johnson wrote: Then why was aptitude written? Why not send patches against apt-get and dselect? I just use apt-get so I'm not completely competent to answer this question. But IMHO aptitude was written to *replace* dselect. If we agree that a certain application can not b

Re: lintian & linda

On Mon, 2005-04-11 at 07:36 +0200, Andreas Tille wrote: > On Sun, 10 Apr 2005, Bernd Eckenfels wrote: [snip] > > Which is if course a big point if you consider > > programmers can only help in one but not the other. > Hmmm - I wonder whether rewriting an application wouldn't take more time than > d