Re: Accepted lynx 2.8.5-2sarge2.2 (source i386)

2006-11-30 Thread Thomas Dickey
On Mon, Nov 27, 2006 at 10:00:40AM +0100, Andreas Barth wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Format: 1.7 > Date: Mon, 27 Nov 2006 07:43:17 +0100 > Source: lynx > Binary: lynx > Architecture: source i386 > Version: 2.8.5-2sarge2.2 > Distribution: unstable > Urgency: low > Ma

Re: Accepted lynx 2.8.5-2sarge2.2 (source i386)

2006-11-30 Thread Guus Sliepen
On Thu, Nov 30, 2006 at 06:41:21AM -0500, Thomas Dickey wrote: > > Changes: > > lynx (2.8.5-2sarge2.2) unstable; urgency=low > > . > >* Non-maintainer upload. > >* Read user configuration from home directory, not current > > working directory. Closes: #396964 > > Thanks to Tom

Re: Accepted lynx 2.8.5-2sarge2.2 (source i386)

2006-11-30 Thread Thomas Dickey
On Thu, Nov 30, 2006 at 12:47:26PM +0100, Guus Sliepen wrote: > On Thu, Nov 30, 2006 at 06:41:21AM -0500, Thomas Dickey wrote: > > > > Changes: > > > lynx (2.8.5-2sarge2.2) unstable; urgency=low > > > . > > >* Non-maintainer upload. > > >* Read user configuration from home directory, no

Re: Naming a 32-bit/64-bit specific Java package

2006-11-30 Thread Goswin von Brederlow
Ola Lundqvist <[EMAIL PROTECTED]> writes: > Hi > > On Tue, Nov 28, 2006 at 01:41:22PM +, Matthew Johnson wrote: >> Is it possible to upload two different versions of the any package to >> the different architectures? So that you get the -64 version on 64bit >> archs and the -32 version on 32 b

Re: Ftpmaster bug reports are not processed nearly fast enough.

2006-11-30 Thread Goswin von Brederlow
Andreas Barth <[EMAIL PROTECTED]> writes: > * Michael Banck ([EMAIL PROTECTED]) [061129 13:50]: >> On Tue, Nov 28, 2006 at 11:06:55PM -0500, Nathanael Nerode wrote: >> > As for the bugs requesting change of priorities in the Overrides >> > file, many appear to simply be ignored permanently. #26388

Re: Accepted lynx 2.8.5-2sarge2.2 (source i386)

2006-11-30 Thread Guus Sliepen
On Thu, Nov 30, 2006 at 07:00:14AM -0500, Thomas Dickey wrote: > > > There's no possibility of including that patch upstream. > > > > So what? If upstream does not want to accept a patch that fixes a > > so what? Read the patch. You certainly didn't, or if you _did_ you > understand nothing of

Re: Ftpmaster bug reports are not processed nearly fast enough.

2006-11-30 Thread Andreas Barth
* Goswin von Brederlow ([EMAIL PROTECTED]) [061130 13:44]: > So I change the priority to what ftpmaster thinks, wait a month for > the entry to get purged and then change it back to what I think and > get it? I would consider this as abuse, and also, that was the reason why I wrote "(normally)".

Re: Conditionally applying an architecture-dependent patch

2006-11-30 Thread Goswin von Brederlow
Russ Allbery <[EMAIL PROTECTED]> writes: > Goswin von Brederlow <[EMAIL PROTECTED]> writes: > >> I need exactly the same thing. I was lloking for an include statement >> for series files though. Something like > >> debian/patches/series.common: >> version.patch >> foo.patch >> barf.patch > >> debi

Re: Accepted lynx 2.8.5-2sarge2.2 (source i386)

2006-11-30 Thread Thomas Dickey
On Thu, Nov 30, 2006 at 01:46:31PM +0100, Guus Sliepen wrote: > I didn't know PERSONAL_MAILCAP was run-time configurable (it looks > a #define to me). If apt-get source wasn't segfaulting at the moment I'd It's a #define. But the change to use the home directory is in the wrong place. I'd point

Re: Accepted lynx 2.8.5-2sarge2.2 (source i386)

2006-11-30 Thread Andreas Barth
* Thomas Dickey ([EMAIL PROTECTED]) [061130 14:12]: > On Thu, Nov 30, 2006 at 01:46:31PM +0100, Guus Sliepen wrote: > > I didn't know PERSONAL_MAILCAP was run-time configurable (it looks > > a #define to me). If apt-get source wasn't segfaulting at the moment I'd > > It's a #define. But the chang

Bug#98549: Canad!an Pharnnacy,Jamil Dhaouadi

2006-11-30 Thread john d stewart
Hey,bud,happy holiday. http://forusmedz.com - DEMANDTEC EMAIL NOTICE: NOTICE: This email transmission and all attached files contain information intended

Re: Accepted lynx 2.8.5-2sarge2.2 (source i386)

2006-11-30 Thread Thomas Dickey
On Thu, Nov 30, 2006 at 02:15:42PM +0100, Andreas Barth wrote: > * Thomas Dickey ([EMAIL PROTECTED]) [061130 14:12]: > > On Thu, Nov 30, 2006 at 01:46:31PM +0100, Guus Sliepen wrote: > > > I didn't know PERSONAL_MAILCAP was run-time configurable (it looks > > > a #define to me). If apt-get source w

Re: Conditionally applying an architecture-dependent patch

2006-11-30 Thread Russ Allbery
Goswin von Brederlow <[EMAIL PROTECTED]> writes: > That isn't very flexible. > By using cpp I can use #include recursively and at any point of the > series. I can also use #ifdef or any other cpp construct. I can insert > an architecture specific patch by enclosing it in #ifdef __arch__. If > I c

Re: Ftpmaster bug reports are not processed nearly fast enough.

2006-11-30 Thread Goswin von Brederlow
Andreas Barth <[EMAIL PROTECTED]> writes: > * Goswin von Brederlow ([EMAIL PROTECTED]) [061130 13:44]: >> So I change the priority to what ftpmaster thinks, wait a month for >> the entry to get purged and then change it back to what I think and >> get it? > > I would consider this as abuse, and al

Re: Hijacking ITA: sa-exim

2006-11-30 Thread Magnus Holmgren
Another three weeks have passed. I give Anand a last chance to respond as I at the same time CC [EMAIL PROTECTED] On Friday 10 November 2006 13:23, Magnus Holmgren wrote: > sa-exim was [1]orphaned on February 12. Four days later, Anand Kumria > announced his ITA, but he never completed the adopti

BTS: Why no "invalid" or "notabug" tag?

2006-11-30 Thread Magnus Holmgren
http://www.debian.org/Bugs/Developer defines the following tags as reasons to dismiss a bug report: * wontfix: the behaviour described can be reproduced or the feature request is understood; it is indeed an issue with our package but we can't or won't do anything about it because there are stro

Re: BTS: Why no "invalid" or "notabug" tag?

2006-11-30 Thread Marco d'Itri
On Nov 30, Magnus Holmgren <[EMAIL PROTECTED]> wrote: > But what about the middle case, i.e. "the behaviour described could be > reproduced, but it's not a bug, or at least not our fault"? (Bugzilla calls > this "INVALID"). I agree that it could be useful, since I get a lot of these cases... --

Etch, apache-perl and php5 needs manual config

2006-11-30 Thread Patrick Frank
Hello. after a base install of Debian Etch, I selected all necessary packages for a LAMP System - Linux Apache MySQL PHP. Specifically: apache-perl 1.3.34-4 php5 5.1.6-5 libapache-mod-php5 5.1.6-5 [and related packages] But I have to manually edit /etc/apache-perl/httpd.conf and enable "Add

Re: Etch, apache-perl and php5 needs manual config

2006-11-30 Thread Russ Allbery
Patrick Frank <[EMAIL PROTECTED]> writes: > after a base install of Debian Etch, I selected all necessary packages > for a LAMP System - Linux Apache MySQL PHP. > Specifically: > apache-perl 1.3.34-4 If at all possible, I strongly encourage you to use Apache 2.2 instesad of Apache 1.x. Apache

Re: Etch, apache-perl and php5 needs manual config

2006-11-30 Thread Steve Kemp
On Thu, Nov 30, 2006 at 07:48:40PM +0100, Patrick Frank wrote: >But I have to manually edit /etc/apache-perl/httpd.conf and enable >"AddType application/x-httpd-php .php" aswell as >/etc/apache-perl/modules.conf >to add "LoadModule php5_module /usr/lib/apache/1.3/libphp5.so". > >

Re: BTS: Why no "invalid" or "notabug" tag?

2006-11-30 Thread Darren Salt
I demand that Magnus Holmgren may or may not have written... [snip] > Often, but not always, the bug can or should be reassigned to another > package, but then a second user might come around and submit the same bug > report. Then, when showing bugs for that package, shouldn't those reassigned bu

Re: Etch, apache-perl and php5 needs manual config

2006-11-30 Thread sean finney
hi patrick, On Thu, 2006-11-30 at 19:48 +0100, Patrick Frank wrote: > apache-perl 1.3.34-4 > php5 5.1.6-5 > libapache-mod-php5 5.1.6-5 > [and related packages] > > But I have to manually edit /etc/apache-perl/httpd.conf and enable > "AddType application/x-httpd-php .php" aswell > as /etc/apac

Re: BTS: Why no "invalid" or "notabug" tag?

2006-11-30 Thread Don Armstrong
On Thu, 30 Nov 2006, Magnus Holmgren wrote: > what about the middle case, i.e. "the behaviour described could be > reproduced, but it's not a bug, or at least not our fault"? > (Bugzilla calls this "INVALID"). > > Often, but not always, the bug can or should be reassigned to another > package, >

Work-needing packages report for Dec 1, 2006

2006-11-30 Thread wnpp
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: 331 (new: 11) Total number of packages offered up for adoption: 87 (new: 3) Total number of packages request