Bug#212796: Newest Microsoft Critical Upgrade

2003-10-26 Thread Security Department
ALERT!This e-mail, in its original form, contained one or more attached files that were infected with a virus, worm, or other type of security threat. This e-mail was sent from a Road Runner IP address. As part of our continuing initiative to stop the spread of malicious viruses, Road Runner scans

Processed: still broken

2003-10-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reopen 212796 Bug#212796: dpkg-checkbuilddeps fails with arch-restricted build-deps Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administr

Bug#212796: still broken

2003-10-26 Thread Ryan Murray
reopen 212796 thanks Now dpkg-checkbuilddeps requires arch dependent build-deps on all archs, not just the specified arch: Build-Depends: debhelper (>> 4), cdbs (>= 0.4.5.3), autotools-dev, libttf-dev (>=1.4pre.20030402-1), libglib1.2-dev, libgtk1.2-dev, liborbit-dev, libncurses5-dev, xlibs-dev

Bug#213524: automake: serious breakage with new install-info behaviour

2003-10-26 Thread Andreas Metzler
Adam Heath wrote: > On Sun, 26 Oct 2003, Santiago Vila wrote: >> Adam Heath wrote: >> > I'm not fixing this bug. automake should not be doing what it is >> > doing, as it was bound to fail. automake was depending on questionable, >> > and wrong behaviour, and it's not surprising it died as it has

Bug#213524: automake: serious breakage with new install-info behaviour

2003-10-26 Thread Andreas Barth
* Adam Heath ([EMAIL PROTECTED]) [031026 19:55]: > For instance, if we delay this 'fix' until after sarge is release, we will > *still* have the problem then. There will be backed in sarge that *will not > build* when sarge+1 is released. No. If you change this as soon as sarge is out, it's very

Processed: Re: Bug#217605: dselect: cannot configure xdm, it works with other pkgs though. it says: "basename: toomany arguments"

2003-10-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 217605 xdm Bug#217605: dselect: cannot configure xdm, it works with other pkgs though. it says: "basename: toomany arguments" Bug reassigned from package `dselect' to `xdm'. > thanks Stopping processing here. Please contact me if you need as

Processed: Re: Bug#213524: marked as done (dpkg: new install-info creates serious breakage, see #213524)

2003-10-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > close 213524 Bug#213524: dpkg: new install-info creates serious breakage, see #213524 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Santiago Vila <[EMAIL PROTECTED]> > thanks Stopp

Bug#151662: #151662: dselect: changes selections without notice

2003-10-26 Thread Adam Heath
On Sun, 26 Oct 2003, Colin Watson wrote: > I see there was a dpkg upload today, but it didn't fix this. Please, is > there any chance that this patch could be applied before sarge? dselect > makes bad mistakes due to this bug, and it will result in much confusion > if it makes it into a stable rel

Bug#213524: automake: serious breakage with new install-info behaviour

2003-10-26 Thread Adam Heath
On Sun, 26 Oct 2003, Santiago Vila wrote: > Adam Heath wrote: > > I'm not fixing this bug. automake should not be doing what it is > > doing, as it was bound to fail. automake was depending on questionable, > > and wrong behaviour, and it's not surprising it died as it has. > > Yes, we all agree

Bug#217605: dselect: cannot configure xdm, it works with other pkgs though. it says: "basename: toomany arguments"

2003-10-26 Thread Adam Heath
reassign 217605 xdm thanks On Sun, 26 Oct 2003, Aldo Maggi wrote: > Configuro xdm (4.2.1-12.1) ... > basename: troppi argomenti > Usare `basename --help' per ulteriori informazioni. > dpkg: errore processando xdm (--configure): > il sottoprocesso post-installation script ha restituito un codic

Processed: your mail

2003-10-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 151662 + pending Bug#151662: dselect: changes selections without notice Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administ

Bug#217415: #217415: dpkg: failed to lock dir for editing! Operation not permitted

2003-10-26 Thread Arnaud Vandyck
> * Adam Heath <[EMAIL PROTECTED]> [2003-10-25 12:50]: > > To: [EMAIL PROTECTED] > > tag 217415 moreinfo > > severity 217415 important > > thanks > > > > Can you repeat this? I need more info. I do try to install Debian on my new powerbookG4 but I can't. The only thing I could do was to boot w

Bug#151662: #151662: dselect: changes selections without notice

2003-10-26 Thread Colin Watson
On Wed, Oct 15, 2003 at 06:50:28PM +0100, Colin Watson wrote: > On Sat, Oct 04, 2003 at 12:16:18AM +0100, Colin Watson wrote: > > I think the following patch is the right fix. I'm cc'ing Joey on this > > because I'd like him to confirm that it makes sense with the original > > intent of his change.

Re: Another attempt at the build-arch problem (fwd)

2003-10-26 Thread Santiago Vila
Hi. Frankly, I believe the whole build-arch idea is flawed. The introduction of a new package format five years ago was a huge improvement over the previous format. The proposals I've seen to "improve" the current source format add a lot of complexities for very little gain.

Another attempt at the build-arch problem (fwd)

2003-10-26 Thread Julian Gilbey
What do you guys think of this idea? I think it's one of the smartest I've heard for a while, and leaves open the possibility of further extensions. Another possibility is to have something like debian/rules.features, which would have a list of features supported by the debian/rules file. For ex

Processed: Re: Bug#213524: marked as done (dpkg: new install-info creates serious breakage, see #213524)

2003-10-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reopen 213524 Bug#213524: dpkg: new install-info creates serious breakage, see #213524 Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (admini

Bug#213524: marked as done (dpkg: new install-info creates serious breakage, see #213524)

2003-10-26 Thread Andreas Metzler
reopen 213524 thanks Adam Heath <[EMAIL PROTECTED]> wrote: > From: Santiago Vila <[EMAIL PROTECTED]> [...] >> In the most recent dpkg package, "install-info --version" now shows its >> output on stdout, not stderr. >> As a result, this code in /usr/share/automake-1.7/am/texinfos.am >> does not wor

Bug#213524: automake: serious breakage with new install-info behaviour

2003-10-26 Thread Santiago Vila
Adam Heath wrote: > I'm not fixing this bug. automake should not be doing what it is > doing, as it was bound to fail. automake was depending on questionable, > and wrong behaviour, and it's not surprising it died as it has. Yes, we all agree on that, but the issue here is not to blame dpkg or a

Bug#217622: dpkg: ldconfig runs everytime a library has to be configured

2003-10-26 Thread Patrizio Bruno
Package: dpkg Version: 1.10.15 Severity: wishlist Tags: sid Why don't add to dpkg a way to schedule command executions, evoiding to run a command everytime a package is configured. ldconfig runs everytime a library is configured, I have a slow laptop and I think it could be useful to schedule ldco

Bug#217605: dselect: cannot configure xdm, it works with other pkgs though. it says: "basename: toomany arguments"

2003-10-26 Thread Aldo Maggi
Package: dselect Version: 1.10.10 Severity: normal -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux paperino 2.6.0-test8 #1 Thu Oct 23 22:13:51 CEST 2003 i586 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (ignored: LC_ALL set to [EMAIL PROTECTED]) Version