Re: greylisting on debian.org?

On Sun, 09 Jul 2006, Thomas Bushnell BSG wrote: > I don't think I understand just what you're saying. Can you spell out > the details for me? Does the second email I sent (with the missing stuff) provides the clarification you asked for? > It distresses me that I have said twice now that a "so

ITP: ri-li -- Control a toy wood engine and collect the items

Package: wnpp Severity: wishlist * Package name: ri-li Version : 1.0.3 Upstream Author : Dominique Roux-Serret <[EMAIL PROTECTED]> Maf464 <[EMAIL PROTECTED]> * URL : http://www.ri-li.org * License : GNU GPL Description : Con

Re: greylisting on debian.org?

Thomas Bushnell BSG becket.net> writes: > martin f krafft debian.org> writes: [...] > It assumes, for example, that the remote MTA will use the same IP > address each time it sends the message. [...] eh no. Standard greylisting practise nowadays (it already was standard when sarge was release

Re: greylisting on debian.org?

Le lun 10 juillet 2006 02:17, Matthew R. Dempsky a écrit : > On Sun, Jul 09, 2006 at 05:02:39PM -0700, Thomas Bushnell BSG wrote: > > Another problem is with hosts that do not accept a message from an > > MTA unless that MTA is willing to accept replies. This is a common > > spam prevention measur

Re: greylisting on debian.org?

Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > Another way to avoid problems with clusters is to assume certain common > setup patterns for server farms, like a cheap netmask match. This does, in > a way, "require you to know in advance the setup of remote networks", in the > sense tha

Re: greylisting on debian.org?

Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > On Sun, 09 Jul 2006, Thomas Bushnell BSG wrote: >> Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: >> > You can, for example, use dynamic IP supersets to do the greylisting >> > "triplet" match. Now the problem is a matter of creat

Re: doc compilations: build-time or pre-built?

[EMAIL PROTECTED] writes: > Hi. > > My dillema: > > 1) compile docs pre-build-time; or > 2) compile docs in build-time > > > Pros of 1: < build-time and < Build-Depends > > Pros of 2: < diff.gz and unnecessary manual intervention of downstream > maintainer (me :) ) > > So, what are best practices

Re: greylisting on debian.org?

On Mon, 10 Jul 2006, Henrique de Moraes Holschuh wrote: > > Is there a way of doing this which doesn't require you to know in > > advance the setup of remote networks and such? Does it scale? > > Yes. The most absurd way is to consider every non-stolen, valid for the > public Internet IPv4 netbl

Re: greylisting on debian.org?

On Sun, 09 Jul 2006, Thomas Bushnell BSG wrote: > Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > > You can, for example, use dynamic IP supersets to do the greylisting > > "triplet" match. Now the problem is a matter of creating the supersets in a > > way to not break incoming email fro

Re: greylisting on debian.org?

Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > You can, for example, use dynamic IP supersets to do the greylisting > "triplet" match. Now the problem is a matter of creating the supersets in a > way to not break incoming email from outgoing-SMTP clusters. Is there a way of doing this

Re: greylisting on debian.org?

On Sun, 09 Jul 2006, Thomas Bushnell BSG wrote: > It assumes, for example, that the remote MTA will use the same IP > address each time it sends the message. If the remote MTA is a big The earlier *implementations* of greylisting did that, true. They were simple-minded at best. > server farm, wi

Re: greylisting on debian.org?

"Matthew R. Dempsky" <[EMAIL PROTECTED]> writes: > On Sun, Jul 09, 2006 at 05:02:39PM -0700, Thomas Bushnell BSG wrote: >> Another problem is with hosts that do not accept a message from an MTA >> unless that MTA is willing to accept replies. This is a common spam >> prevention measure. > > It al

Bug#377556: ITP: sork-vacation-h3 -- autovacation module for Horde Framework

Package: wnpp Severity: wishlist Owner: Gregory Colpart (evolix) <[EMAIL PROTECTED]> * Package name: sork-vacation-h3 Version : 3.0 Upstream Author : The Horde Team <[EMAIL PROTECTED]> * URL : http://www.horde.org/vacation/ * License : Apache License 1.1-like

Re: select() to /dev/rtc to wait for clock tick timed out. : a different solution

At Sun, 09 Jul 2006 09:43:49 +0900, Junichi Uekawa wrote: > > Hi, > The question I have is how to accomplish this. It looks like hotplug > is loading stuff at boot-time, and it's not quite clear as how to make > it not load rtc. > > I have tried not loading rtc with blacklisting, but apparently

Re: greylisting on debian.org?

On Sun, Jul 09, 2006 at 05:02:39PM -0700, Thomas Bushnell BSG wrote: > Another problem is with hosts that do not accept a message from an MTA > unless that MTA is willing to accept replies. This is a common spam > prevention measure. It also prevents mail from setups that use different servers fo

Re: greylisting on debian.org?

martin f krafft <[EMAIL PROTECTED]> writes: > Anyway, I'll be interested to hear a summary of their arguments, as > Christian Perrier requested. I find it hard to imagine how properly > configured greylisting should cause any problems. It's a violation of the standard. It is especially problemat

Re: Broken applications: Could we be honest?

On Sat, Jul 08, 2006 at 07:23:54PM +0300, Török Edvin wrote: > Btw, what is the appropriate severity level for a package that doesn't > work on a certain architecture at all? Is it release critical? If the architecture is a release candidate, yes. -- Fun will now commence -- Seven Of Nine, "As

Re: Debian Bug Tracking System

On Sat, Jul 08, 2006 at 01:02:44AM +0530, Ritesh Raj Sarraf wrote: > Hi, > > Not trying to start a flame war but can somebody give a convincing > explanation as to why don't we have a standard BTS ? Because most "standard" BTSes suck? > If I need to subscribe to a bug I can't use the web interfa

Bug#377551: ITP: libvrb -- Virtual Ring Buffer library

Package: wnpp Severity: wishlist Owner: "Székelyi Szabolcs" <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: libvrb Version : 0.5.0 Upstream Author : Philip Howard <[EMAIL PROTECTED]> * URL : http://vrb.slashusr.org/ * License :

Re: Marcelo Magallon (lib3ds maintainer) MIA?

Thanks for the advice; I've sent Marcelo another message, this time GPG-signed... -Miles -- "Though they may have different meanings, the cries of 'Ye-haw!' and 'Allahu akbar!' are, in spirit, not actually all that different." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject o

Re: Long blurbs repeated in many package descriptions considered harmful

Enrico Zini wrote: While these blurbs are informative, they provide information not strictly related to the package itself. As a consequence, if you do "apt-cache search image" you get all of pike, including irrelevant things like "pike7.6-public.network.pcap" or "pike7.6-public.protocols.syslo

Re: greylisting on debian.org?

Le dim 9 juillet 2006 14:30, Marc Haber a écrit : > On Sun, 9 Jul 2006 08:14:20 +0200, Christian Perrier > > <[EMAIL PROTECTED]> wrote: > >Quoting Thomas Bushnell BSG ([EMAIL PROTECTED]): > >> martin f krafft <[EMAIL PROTECTED]> writes: > >> > This has been brought up. Basically I don't think peopl

Bug#377546: ITP: schedtools -- Queries/alters process's scheduling policy; supports the -ck kernel patch

Package: wnpp Severity: wishlist Owner: Thibaut VARENE <[EMAIL PROTECTED]> * Package name: schedtools Version : 1.2.6 Upstream Author : Freek * URL : http://freequaos.host.sk/schedtool/ * License : GPLv2 Programming L

Re: cdrtools

Eduard Bloch wrote: >#include >* Kevin Bube [Fri, Jul 07 2006, 11:29:21AM]: >> Eduard Bloch <[EMAIL PROTECTED]> writes: >> > * Adam Borowski [Fri, Jul 07 2006, 10:38:32AM]: >> >> >> * dvdrtools, a fork of the last GPLed version, is in non-free >> > >> > Please look at dvdrtools' files, eg. cdreco

Re: Bug#359073: Net/RBLClient.pm (postgreyreport)

> On Sun, 09 Jul 2006 21:51, Adrian von Bidder wrote: ^ [... package doesn't exist, perhaps somebody on [EMAIL PROTECTED] has time to do the package? ... ] On Sunday 09 July 2006 22:17, you wrote: ^ > Done. Now that is what I call response ti

Re: Alioth Tracker: no correspondence to BTS?

Peter Samuelson, 2006-07-09 21:30:11 +0200 : > [Toni Mueller] >> I've just poked around a bit in Alioth for a project I'm working on >> and found a bug report with a bug number that has no resemblance to >> anything in BTS, quite contrary to my initial assumption. > > Yeah, the sourceforge softwar

Re: Alioth Tracker: no correspondence to BTS?

On 7/10/06, Frans Pop <[EMAIL PROTECTED]> wrote: On Sunday 09 July 2006 21:29, Peter Samuelson wrote: > > I've just poked around a bit in Alioth for a project I'm working on > > and found a bug report with a bug number that has no resemblance to > > anything in BTS, quite contrary to my initial a

Re: Alioth Tracker: no correspondence to BTS?

Quoting Peter Samuelson ([EMAIL PROTECTED]): > Yeah, I couldn't tell you why that feature is even enabled on alioth. > Do people actually use it? I certainly never check the tracker for > alioth projects I'm involved with; I just assume people will use the > Debian BTS instead. We (iso-codes mai

Re: Alioth Tracker: no correspondence to BTS?

On Sunday 09 July 2006 21:29, Peter Samuelson wrote: > > I've just poked around a bit in Alioth for a project I'm working on > > and found a bug report with a bug number that has no resemblance to > > anything in BTS, quite contrary to my initial assumption. > > Yeah, the sourceforge software inclu

Re: Alioth Tracker: no correspondence to BTS?

[Toni Mueller] > I've just poked around a bit in Alioth for a project I'm working on > and found a bug report with a bug number that has no resemblance to > anything in BTS, quite contrary to my initial assumption. Yeah, the sourceforge software includes a primitive bug tracker which, as far as I

Re: Alioth Tracker: no correspondence to BTS?

also sprach Toni Mueller <[EMAIL PROTECTED]> [2006.07.09.2017 +0200]: > I've just poked around a bit in Alioth for a project I'm working > on and found a bug report with a bug number that has no > resemblance to anything in BTS, quite contrary to my initial > assumption. Imho this would only make s

Alioth Tracker: no correspondence to BTS?

Hello, I've just poked around a bit in Alioth for a project I'm working on and found a bug report with a bug number that has no resemblance to anything in BTS, quite contrary to my initial assumption. Imho this would only make sense if integrating these two is hard, and if non-Debian projects are

Bug#377527: ITP: liboping -- C library to generate ICMP_ECHO requests

Package: wnpp Severity: wishlist Owner: Sebastian Harl <[EMAIL PROTECTED]> * Package name: liboping Version : 0.3 Upstream Author : Florian Forster <[EMAIL PROTECTED]> * URL : http://verplant.org/liboping/ * License : GPLv2 Description : C library to gene

Bug#377513: ITP: libcam-pdf-perl -- library for PDF manipulation

Package: wnpp Severity: wishlist Owner: "Zak B. Elep" <[EMAIL PROTECTED]> * Package name: libcam-pdf-perl Version : 1.06 Upstream Author : Clotho Advanced Media, Inc. <[EMAIL PROTECTED]> * URL : http://search.cpan.org/~clotho/ * License : Dual License (Artistic/

Re: greylisting on debian.org?

Quoting Marc Haber ([EMAIL PROTECTED]): > For example, that greylisting puts significant load on systems that > deliver mail to us, and that it is only a question of time before spam > zombies retry. Yep, I know about these arguments but Pierre Habouzit bringed an interesting enhancement to grey

Re: greylisting on debian.org?

also sprach Thijs Kinkhorst <[EMAIL PROTECTED]> [2006.07.09.1622 +0200]: > Indeed, the current Alioth config only greylists those hosts that have > some kind of 'problem', like no reverse DNS entry or are featured on > some kind of RBL. > > Any decent mailserver is allowed right through. Any indec

Re: greylisting on debian.org?

On Sun, 2006-07-09 at 16:14 +0200, martin f krafft wrote: > > A far more reasonable solution is to only greylist mail with an > > unreasonably high spamassassin score. Normal mail I assume generally > > doesn't score high and is not susceptable to greylisting. > > Sure. Or greylist only when it's

Re: greylisting on debian.org?

Martijn van Oosterhout <[EMAIL PROTECTED]> wrote: [...] > The point was about mailers sending mail to debian. If they receive a > 4xx they have to queue the mail and retry later. It's cheap for > debian, but expensive for everyone else. > A far more reasonable solution is to only greylist mail wit

Re: greylisting on debian.org?

also sprach Martijn van Oosterhout <[EMAIL PROTECTED]> [2006.07.09.1548 +0200]: > The point was about mailers sending mail to debian. If they receive a > 4xx they have to queue the mail and retry later. It's cheap for > debian, but expensive for everyone else. My point was: even 100 such queued ma

Re: greylisting on debian.org?

On 7/9/06, martin f krafft <[EMAIL PROTECTED]> wrote: also sprach Marc Haber <[EMAIL PROTECTED]> [2006.07.09.1430 +0200]: > For example, that greylisting puts significant load on systems > that deliver mail to us, I am sorry, I don't buy this argument at all. First, a 4xx is not "significant loa

Re: greylisting on debian.org?

also sprach Thomas Bushnell BSG <[EMAIL PROTECTED]> [2006.07.09.0557 +0200]: > There were people opposed to it, in fact. Sure, nobody expected it to be any different. This is Debian, after all. :) There will always be opposers. If we let our work be hindered by them, we're going to stagnate. Any

Re: greylisting on debian.org?

also sprach Marc Haber <[EMAIL PROTECTED]> [2006.07.09.1430 +0200]: > For example, that greylisting puts significant load on systems > that deliver mail to us, I am sorry, I don't buy this argument at all. First, a 4xx is not "significant load" on any mailer unless you're running some piece of cra

Re: Bug#376521: ITP: kwlan -- wpasupplicant frontend for KDE

On Monday 03 July 2006 17:16, Fathi Boudra wrote: > Hi Reinhard, > > > Perhaps you are interested in joining the pkg-wpa team on alioth [1]? [...] > There's many K wireless tools but none really perfect maybe > we can cooperate to have only one good tool nicely integrated with > wpa_supplicant. Yo

New LSB compliance list of init-scripts and guide for maintainers (SoC 2006)

Hi, a list containing the LSB-compliance to runtime dependencies of init scripts is now available at http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/lsblist.html>. It has currently only the desktop task init-script subset for Sid and relates each script with a bug report issued to

Re: greylisting on debian.org?

On Sun, 9 Jul 2006 08:14:20 +0200, Christian Perrier <[EMAIL PROTECTED]> wrote: >Quoting Thomas Bushnell BSG ([EMAIL PROTECTED]): >> martin f krafft <[EMAIL PROTECTED]> writes: >> > This has been brought up. Basically I don't think people were >> > opposed to it, but there was noone available to im

Bug#377467: RFH: svn-buildpackage -- helper programs to maintain Debian packages with Subversion

Package: wnpp Severity: normal I request assistance with maintaining the svn-buildpackage package. My spare time is exhausted by other things IRL and other more urgent projects. The codeveloper should ideally be a good perl coder. The package description is: svn-buildpackage (formerly svn-devscr

Re: Another weird tar issue (100 character filenames)

On Tue, Jun 27, 2006 at 01:09:40PM +0200, Jeroen van Wolffelaar wrote: > On Tue, Jun 27, 2006 at 09:07:03AM +0100, Roger Leigh wrote: > > It sounds like a bug that dpkg is using the old v7 tar format which > > had that 99 char limitation.s tar has a fixed-length field for short (upto 100 bytes) fi