Please allow resolvconf 1.42 into testing

2008-08-30 Thread Thomas Hood
ifupdown Apart from that, the only change is the updating of two translations. Here is the changelog entry for 1.42. resolvconf (1.42) unstable; urgency=high [ Thomas Hood ] * init script: Add X-Start-Before and Should-Stop dependencies on ifupdown and networking (Closes: #493501

Re: Please push ifupdown 0.6.4-4.12

2005-03-21 Thread Thomas Hood
oved. Thanks for checking it over. The "restart" pattern was removed because there is a "start|restart" pattern earlier in the same case statement. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Please push ifupdown 0.6.4-4.12

2005-03-18 Thread Thomas Hood
ago with one additional change. No new bugs have > been reported. Please push! Maybe if I repeat this I will get some sort of answer. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ifupdown 0.6.4-4.11 needed for sarge

2005-01-27 Thread Thomas Hood
: http://www.aglu.demon.nl/ifupdown I attach the diff between -4.10 and -4.11 so that you can see that the changes are limited to those required to fix #266479. -- Thomas Hood <[EMAIL PROTECTED]> diff -Naur ifupdown-0.6.4-4.10/debian/changelog ifupdown-0.6.4-4.11/debian/changelog --- ifupdown

waproamd in sarge?

2005-01-20 Thread Thomas Hood
Considering that waproamd has been orphaned and even deprecated by its upstream[0] in favor of wpa_supplicant, I wonder whether waproamd should be included in sarge. [0]http://seth.intheinter.net/pipermail/ifplugd-discuss/2004-December/28.html -- Thomas Hood <[EMAIL PROTECTED]>

waproamd in sarge?

2005-01-20 Thread Thomas Hood
Considering that waproamd has been orphaned and even deprecated by its upstream[0] in favor of wpa_supplicant, I wonder whether waproamd should be included in sarge. [0]http://seth.intheinter.net/pipermail/ifplugd-discuss/2004-December/28.html -- Thomas Hood <[EMAIL PROTECTED]>

Re: Please remove alsa-modules-2.4.27-1*

2005-01-11 Thread Thomas Hood
27-2-*. Thanks for the suggestion. -- Thomas Hood

Re: Please remove alsa-modules-2.4.27-1*

2005-01-11 Thread Thomas Hood
27-2-*. Thanks for the suggestion. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Please remove alsa-modules-2.4.27-1*

2005-01-08 Thread Thomas Hood
't in testing yet, but I > don't see alsa-modules-2.4.27-2 anywhere, even in NEW? We haven't done an alsa-modules-2.4.27-2* release yet. That shouldn't affect the decision about whether or not to remove alsa-modules-2.4.27-1, though. -- Thomas Hood <[EMAIL PROTECTED]>

Please remove alsa-modules-2.4.27-1*

2005-01-04 Thread Thomas Hood
elease 2.4.27-2 kernels instead. However, the combinations of 2.4.27-1 kernels with 2.4.27-1 module packages are still available in sarge and are still causing headaches. To alleviate this problem, I request that alsa-modules-2.4.27-1* be removed from sarge. -- Thomas Hood <[EMAIL PROTECTED]>

Re: full transition to libcurl3

2004-12-10 Thread Thomas Hood
l2 and this has cured the segfaults. -- Thomas Hood

Re: removal suggestion: stars

2004-10-24 Thread Thomas Hood
Work that doesn't serve a useful purpose should not be done; the effort should be expended elsewhere. -- Thomas Hood

Re: Some observations regardig the progress towards Debian 3.1

2003-11-15 Thread Thomas Hood
ht from Debian. They should take a look at one of the fine distributions based on Debian or else pay someone to make periodic custom releases that suits their needs. -- Thomas Hood <[EMAIL PROTECTED]>