Bug#693371: insserv: Please update insserv.conf to ensure mountall-bootclean is run

_bootmisc_order test to suite to verify the mountall-bootclean +dependency works as expected. + + -- Kel Modderman Sun, 18 Nov 2012 11:55:44 +1000 + insserv (1.14.0-4) unstable; urgency=low * Provide machine parseable output which may be used by file-rc to calculate Index: debian/patches/11_

Bug#670085: insserv: update-rc.d is a dangling symlink

Sep 17 00:00:00 2001 From: Kel Modderman Date: Mon, 23 Apr 2012 20:38:40 +1000 Subject: [PATCH] Unconditionally remove diversion of update-rc.d to update-rc.d-insserv. --- debian/sysv-rc.postinst |6 ++ 1 file changed, 6 insertions(+) diff --git a/debian/sysv-rc.postinst b/debian/sysv

Bug#670085: insserv: update-rc.d is a dangling symlink

Hi Roger, > On 22.04.2012 23:03, Eddy Petrișor wrote: > > On 22.04.2012 22:58, Eddy Petrișor wrote: > >> Subject: insserv: update-rc.d is a dangling symlink > >> Package: insserv > >> Version: 1.14.0-3 > > > > I forgot to add this info: > > > > heidi:/home/eddy# ls -l /usr/sbin/update-rc* > > lrwx

Bug#650995: causes dependency loop in boot sequence (according to insserv)

Hi all, > Package: console-common > Version: 0.7.86 > Severity: serious > > Installation of console-common 0.7.86 has failed in unstable for me with the > following insserv error: I'd like to think of it as a console-common error which causes insserv to reject the keymap.sh script header causing

Bug#623003: [Pkg-sysvinit-devel] Bug#623003: initscripts: checkfs fails with already mounted error after lenny to squeeze upgrade

On Sun, 17 Apr 2011 01:12:35 AM Thorben Jändling wrote: > Package: initscripts > Version: 2.88dsf-13.1 > Severity: critical > Tags: squeeze > Justification: breaks unrelated software > > After upgrade from lenny to squeeze my system no longer boots. > Here is the boot up text: > > " --- > Synthes

Bug#618719: FTBFS on kfreebsd: ../src/utils/pcsc_funcs.o: undefined reference to symbol 'dlsym@@GLIBC_2.3'

On Mon, 11 Apr 2011 09:03:49 AM Michael Biebl wrote: > Am 10.04.2011 20:48, schrieb Guillem Jover: > > On Sat, 2011-03-19 at 22:17:38 +1000, Kel Modderman wrote: > >>> Looks like the build failure is due to 08_pcsc_dynamic.patch > > > >> We could drop the patch

Bug#618719: FTBFS on kfreebsd: ../src/utils/pcsc_funcs.o: undefined reference to symbol 'dlsym@@GLIBC_2.3'

--- debian/changelog(revision 1573) +++ debian/changelog(working copy) @@ -1,3 +1,10 @@ +wpasupplicant (0.7.3-2) UNRELEASED; urgency=low + + * Modify debian/patches/08_pcsc_dynamic.patch to add dl to LIBS to link +with. + + -- Kel Modderman

Bug#595431: Aborting fsck aborts all scripts in rcS.d

On Saturday 04 September 2010 06:39:49 Goswin von Brederlow wrote: > Package: insserv > Version: 1.14.0-2 > Severity: critical > > Hi, > > during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't > been checked for 197 days) as well as giving some errors for missing > devices. Since

Bug#580564: kdb: Hangs under certain circumstances during boot with CONCURRENCY enabled

tags 580564 pending thanks On Friday 07 May 2010 16:22:53 Petter Reinholdtsen wrote: > severity 580564 grave > thanks > > [Michael Guntsche] > > For other packages it seems to work ok (udev). > > Sure, but udev was already listed in insserv.conf. > > > I tried that and it works here as well. KB

Bug#573048: hostapd incompatible with 2.6.33 kernel

severity 573048 important thanks On Tuesday 09 March 2010 00:17:55 Daniel wrote: > Package: hostapd > Version: 1:0.6.10-2 > Severity: grave > Justification: renders package unusable Bull. > > Running kernel 2.6.32.8 together with the above hostapd version worked > just fine That's why the sub

Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed

reassign 524314 splashy retitle 524314 splashy causes init scripts to exit with error tags 524314 - moreinfo thanks On Thursday 16 April 2009 19:50:38 Carlo Aquilini wrote: > Il giorno gio, 16/04/2009 alle 19.18 +1000, Kel Modderman ha scritto: > > I installed the freepops package to in

Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed

On Thursday 16 April 2009 18:42:39 Carlo Aquilini wrote: > Hello, I discovered it during acpid upgrade that failed claiming that it > couldn't stop and restart the service (solved by momentarily > renaming /etc/init.d/acpid and then upgrading). The output of the upgrade should be provided. > >

Bug#524314: [Pkg-sysvinit-devel] Bug#524314: [sysv-rc] Sysv-rc always reports that actions failed

tags 524314 moreinfo thanks On Thursday 16 April 2009 18:04:27 Carlo Aquilini wrote: > Package: sysv-rc > Version: 2.86.ds1-61 > Severity: critical > > > Sysv-rc always reports that actions failed even if they are successfully > accomplished. > This breaks reconfiguration of every package that

Bug#509484: [pkg-wpa-devel] Bug#509484: wpasupplicant prevent kpowersave kde4.2 powersave to suspend

severity 509484 important thanks On Tuesday 23 December 2008 07:33:21 Eric Valette wrote: > Kel Modderman wrote: > > On Tuesday 23 December 2008 05:25:32 valette wrote: > >> Package: wpasupplicant > >> Version: 0.6.6-1 > >> Severity: critical > >

Bug#509484: [pkg-wpa-devel] Bug#509484: wpasupplicant prevent kpowersave kde4.2 powersave to suspend

On Tuesday 23 December 2008 05:25:32 valette wrote: > Package: wpasupplicant > Version: 0.6.6-1 > Severity: critical > Justification: breaks unrelated software Which? Duplicate of #508526 ? Thanks, Kel. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "un

Bug#504696: ndiswrapper-source: longs ESSIDs can expose security vulnerability

/changelog @@ -1,3 +1,11 @@ +ndiswrapper (1.53-2) unstable; urgency=high + + * Add debian/patches/CVE-2008-4395.patch to fix a vulnerability in handling +of long ESSIDs which allows execution of code as root via remote attacker. +(Closes: #504696) + + -- Kel Modderman <[EMAIL PROTECTED]>

Bug#504696: ndiswrapper-source: longs ESSIDs can expose security vulnerability

Package: ndiswrapper-source Version: 1.53-1 Severity: grave Tags: security patch Justification: user security hole >From [0]: Anders Kaseorg discovered that ndiswrapper did not correctly handle long ESSIDs. For a system using ndiswrapper, a physically near-by attacker could generate specially craf

Bug#485769: [pkg-wpa-devel] Bug#485769: wpasupplicant crashes: not with 32bit kernel

severity 485769 important thanks On Sunday 24 August 2008 23:50:05 Stefan Fritsch wrote: > Hrm. It works with linux-image-2.6.25-2-686. > > Maybe the severity is not grave after all. But wpasupplicant should not > crash. I cannot reproduce the problem, neither can my peer. Also have little idea

Bug#494514: insserv: Test suite fail on alpha

Hi Petter and Steve, On Monday 18 August 2008 16:46:08 Petter Reinholdtsen wrote: > [Steve Langasek] > > In this case, NFS... > > Right. So ext3 and NFS should be ok. :) > > > I can try against a different filesystem tomorrow if you like. > > If you happen to know what file system is used on t

Bug#494166: madwifi-source: HAL ABI mismatch with 0.9.4+r3772.20080716-1

severity 494166 important thanks On Sunday 10 August 2008 22:11:37 Kel Modderman wrote: > On Friday 08 August 2008 01:08:29 Luc Begault wrote: > > Package: madwifi-source > > Version: 1:0.9.4+r3772.20080716-1 > > Severity: grave > > Justification: renders package

Bug#481752: [Pkg-spca5xx-devel] Bug#481752: Cannot install on a custom kernel

tags 481752 wishlist thanks On Sunday 18 May 2008 21:46:41 Jonny Lamb wrote: > Package: gspca-source > Version: 01.00.20-1 > Severity: grave > Justification: Makes package uninstallable gspca-source is installable just fine ;-) Sarcasm aside, I partially agree with you, but do not agree with the

Bug#477765: refer to #476689

Hi Martin, Please refer to bug #476689, I believe your bootstrap issue is tracked there. Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#476689: [debian-archive-keyring] Downgrading dependency of gnupg causes failure to cdebootstrap minimal chroot

Is anyone interested in fix this this bug? It has been bounced around the BTS, is incorrectly marked as "wontfix" after the last forcemerge, and no response to last suggestion a few days ago. To reiterate: The downgrade of dependency of gnupg to recommends causes problems because apt cannot handl

Bug#476689: [debian-archive-keyring] Downgrading dependency of gnupg causes failure to cdebootstrap minimal chroot

On Saturday 19 April 2008 00:03:58 Philipp Kern wrote: > Not a bug in debian-archive-keyring, but in cdebootstrap. It should > install recommends. OTOH it's also #476532 in apt, as it should use > gpgv instead and depend on it Wouldn't it be easier to just revert to depending on gnupg considerin

Bug#472653: wrong CONFIG_BUSYBOX_EXEC_PATH

Package: busybox Version: 1:1.9.2-1 I believe this configuration change is needed if busybox is to be used as 'mount' before /proc is mounted: --- diff -Nrup busybox-1.9.2.orig/debian/config/config.deb busybox-1.9.2/debian/config/config.deb --- busybox-1.9.2.orig/debian/config/config.deb 2008-03-

Bug#467198: madwifi-source: m-a doesn't install due to dependencies problems (madwifi-tools)

On Sunday 24 February 2008 13:36:28 Colomban Wendling wrote: > > > > What exact command did you use? What distribution (testing|sid)? > > > > Do you have latest madwifi-tools installed? If so what version? > > What does apt-cache policy madwifi-tools say? > > > > Kel. > > > > > Hi, > > I'm us

Bug#467198: madwifi-source: m-a doesn't install due to dependencies problems (madwifi-tools)

On Sunday 24 February 2008 03:54:30 Colomban Wendling wrote: > Package: madwifi-source > Version: 1:0.9.4~rc2-1 > Severity: grave > Justification: renders package unusable > > The installation of the new version of madwifi-source doesn't work due to > madwifi-tools dpendencies problems. > > Afte

Bug#464514: [pkg-wpa-devel] Bug#464514: wpasupplicant segfaults after successful authentication

tags 464514 pending thanks On Thursday 07 February 2008 19:56:05 Alex wrote: > Package: wpasupplicant > Version: 0.6.2+git20080202.gde6ccd7-1 0 > Severity: critical > > > Using the configuration (no problems with older wpasupplicant) > network={ > [...] > key_mgmt=IEEE8021X > e

Bug#463353: madwifi-source: patch for compilation under 2.6.24

tags 463353 pending thanks On Wednesday 06 February 2008 05:46:11 Eric Cooper wrote: > Package: madwifi-source > Version: 1:0.9.3.2-2 > Tags: patch > Followup-For: Bug #463353 Did you read the bug report before going to trouble of making patch? pkg-madwifi is fixed with regard to this issue, som

Bug#463547: [pkg-wpa-devel] Bug#463547: FTBFS: uic file generated with too recent version of Qt Designer

tags 463547 pending thanks On Monday 04 February 2008 07:00:16 Joachim Breitner wrote: > Version: 0.6.2-1 > > Hi, > > Am Sonntag, den 03.02.2008, 01:22 +1000 schrieb Kel Modderman: > > On Friday 01 February 2008 21:58:14 Kel Modderman wrote: > > > On Friday 01

Bug#463547: [pkg-wpa-devel] Bug#463547: FTBFS: uic file generated with too recent version of Qt Designer

On Friday 01 February 2008 21:58:14 Kel Modderman wrote: > On Friday 01 February 2008 21:11:03 Joachim Breitner wrote: > > Package: wpasupplicant > > Version: 0.6.1~git20071119-1 > > Severity: serious > > > > Hi, > > > > trying to recompile the packa

Bug#463547: [pkg-wpa-devel] Bug#463547: FTBFS: uic file generated with too recent version of Qt Designer

On Friday 01 February 2008 21:11:03 Joachim Breitner wrote: > Package: wpasupplicant > Version: 0.6.1~git20071119-1 > Severity: serious > > Hi, > > trying to recompile the package here I get this error: > > /usr/share/qt3/bin/uic wpagui.ui -o .ui/wpagui.h > uic: File generated with too recent ve

Bug#463353: madwifi-source: cannot build with 2.6.24-1-686

On Thursday 31 January 2008 23:56:21 Damyan Ivanov wrote: > > Proposed updates are at: > > http://sidux.net/kelmo/debian/pool/non-free/m/madwifi/madwifi_0.9.4~rc1-1.dsc > > http://sidux.net/kelmo/debian/pool/contrib/m/madwifi-tools/madwifi-tools_0.9.3+dfsg-4.dsc > > I gave these a try. They built

Bug#463353: madwifi-source: cannot build with 2.6.24-1-686

On Thursday 31 January 2008 22:01:02 Stephen Gran wrote: > This one time, at band camp, Kel Modderman said: > > Am pretty well informed about ath5k movements with regards to mainline > > inclusion (am involved with madwifi.org team that handles development > > of the non-

Bug#463353: madwifi-source: cannot build with 2.6.24-1-686

On Thursday 31 January 2008 20:41:00 Stephen Gran wrote: > This one time, at band camp, Kel Modderman said: > > Thank you for this very useful information. > > > > Even when this obstacle is passed, the current madwifi version will fail to > > build. I've been wo

Bug#463353: madwifi-source: cannot build with 2.6.24-1-686

On Thursday 31 January 2008 15:59:08 Damyan Ivanov wrote: > -=| Kel Modderman, Thu, Jan 31, 2008 at 01:11:35PM +1000 |=- > > On Thursday 31 January 2008 12:57:51 Chip Salzenberg wrote: > > > make[3]: Entering directory `/usr/src/linux-headers-2.6.24-1-686' > > >

Bug#463353: madwifi-source: cannot build with 2.6.24-1-686

On Thursday 31 January 2008 12:57:51 Chip Salzenberg wrote: > Package: madwifi-source > Version: 1:0.9.3.2-2 > Severity: grave > Justification: renders package unusable > > Here's a log of the failure: > > > dh_testdir > dh_testroot

Bug#426224: [Pkg-sysvinit-devel] Bug#426224: shutdown patches - the choices

Hi, On Thursday 13 December 2007 17:35:20 Artur Szymiec wrote: > Kel Modderman pisze: > > Package: sysvinit > > Version: 2.86.ds1-38.1 > > > > Hi, > > > > I'm following up on this ticket, since I've not received any response > > for the &g

Bug#426224: shutdown patches - the choices

Package: sysvinit Version: 2.86.ds1-38.1 Hi, I'm following up on this ticket, since I've not received any response for the best part of 6 months. The patch I proposed here is, IMHO, the most complete of the ones offered so far. Recently, I was made aware of someone also claiming [0] the patch [1

Bug#446824: CVE-2007-5448 remote denial of service via crafted beacon frame

On Wed, 17 Oct 2007 03:01:24 am Nico Golde wrote: > Hi, > > * Nico Golde <[EMAIL PROTECTED]> [2007-10-16 17:59]: > > Hi Kel, > > > > * Kel Modderman <[EMAIL PROTECTED]> [2007-10-16 17:14]: > > > tags 446824 pending > > > thanks >

Bug#446824: CVE-2007-5448 remote denial of service via crafted beacon frame

tags 446824 pending thanks On Tue, 16 Oct 2007 08:37:31 am Nico Golde wrote: > | Madwifi 0.9.3.2 and earlier allows remote attackers to cause a denial > | of service (panic) via a beacon frame with a large length value in the > | extended supported rates (xrates) element, which triggers an asserti

Bug#446039: madwifi-source: won't complie under 2.6.23

severity 446039 wishlist tags 446039 pending thanks On Wed, 10 Oct 2007 12:37:24 pm R E Riding wrote: > Package: madwifi-source > Version: 1:0.9.3.2-1 > Severity: grave > Justification: renders package unusable > > > after configuring and making kernel 2.6.23 using > make-kpkg, "make-kpkg --added-

Bug#438746: libqt4-qt3support needs tighter dependency on libqt4-*

reassign 438746 libqt4-qt3support thanks libqt4-qt3support can be installed alongside incompatible qt4 libs, eg: libqt4-core4.3.1-2 libqt4-gui 4.3.1-2 libqt4-qt3support 4.3.0-4 The above combination of packages inhibited wpagui to start for a user

Bug#438746: wpa_gui not useable : Cannot mix incompatible Qt libraries

Hi, On Mon, 20 Aug 2007 01:00:08 am Didier Raboud wrote: > Package: wpagui > Version: 0.6.0-2 > Severity: serious > > --- Please enter the report below this line. --- > > Hi, > > when launching wpa_gui, I get this error which makes the whole wpagui > package unuseable : > > $ wpa_gui > Cannot mix

Bug#434816: Doesn't work at all with kernel 2.6.22

severity 434816 important thanks On Fri, 27 Jul 2007 08:23:11 am David wrote: > Package: madwifi-source > Version: 1:0.9.3-3 > Severity: grave > > --- Please enter the report below this line. --- > > After upgrading the kernel and, of course, doing m-a a-i madwifi and > rebooting, debian can't see

Bug#429437: new MAKEDEV usage chroot un friendly

On Tue, 19 Jun 2007 07:58:35 am Ludovic RESLINGER wrote: > > Hello, > > I need to know if you use makedev or udev. I should have said: In the chroot, at the time libraw1394-8.postinst was called, udev was installed but inactive due to the fact that it detects it was installed in a chroot in ude

Bug#429437: new MAKEDEV usage chroot un friendly

On Tue, 19 Jun 2007 07:58:35 am Ludovic RESLINGER wrote: > On Mon, Jun 18, 2007 at 01:10:38PM +1000, [EMAIL PROTECTED] wrote: > > Package: libraw1394-8 > > Version: 1.2.1-3 > > Severity: serious > > Tags: patch > > > > The new postinst is broken for the common case of installing package in > > chro

Bug#425738: madwifi: several DOS-able holes

-u madwifi-0.9.2+r1842.20061207/debian/control madwifi-0.9.2+r1842.20061207/debian/control --- madwifi-0.9.2+r1842.20061207/debian/control +++ madwifi-0.9.2+r1842.20061207/debian/control @@ -2,7 +2,7 @@ Section: non-free/net Priority: optional Maintainer: Debian madwifi team <[EMAIL PRO

Bug#419057: ndiswrapper-source: Fails to compile with Upstream Kernel source 2.6.20.6

severity 419057 wishlist thanks Hi Subhashis, On Saturday 14 April 2007 00:19, Subhashis Roy wrote: > Package: ndiswrapper-source > Version: 1.28-1 > Severity: grave > Justification: renders package unusable ...when used with stuff outside of what is in etch. This is not a grave shortcoming of

Bug#403301: [pkg-wpa-devel] Bug#403301: wpasupplicant: segfaults with Cisco Aironet

severity 403301 important thanks Hi Matteo, Lowered severity, this does not meet grave bug criteria, IMHO. The package works fine with supported devices and did not cause you any harm. On Saturday 16 December 2006 11:50, Matteo Croce wrote: > Package: wpasupplicant > Version: 0.5.5-4 > Severity

Bug#398466: NMU Ready

On Saturday 09 December 2006 08:00, Matt Brown wrote: > The fix described in the third post is incorrect. The backported patches > applied in -3 have already reordered this part of the code so that it > works correctly with madwifi. > > Unfortunately that backport missed the final component of the

Bug#401345: [Pkg-spca5xx-devel] Bug#401345: builds fine here..

On Sunday 03 December 2006 12:11, Andreas Henriksson wrote: > I can't reproduce your problem with spca5xx-source. How are you > building? > > I've tried building the spca5xx-source in an unstable amd64 pbuilder, > then installing the spca5xx-source package and building that with > module-assistant

Bug#398466: hostapd 0.5.5-3 serious regression with madwifi

On Tuesday 14 November 2006 08:43, Kel Modderman wrote: > Package: hostapd > Version: 1:0.5.5-3 > Severity: grave > Justification: renders package unusable > > The subtle changes between 0.5.5-2 and 0.5.5-3 have exposed a > showstopping bug when used in conjunction with c

Bug#398466: hostapd 0.5.5-3 serious regression with madwifi

Package: hostapd Version: 1:0.5.5-3 Severity: grave Justification: renders package unusable The subtle changes between 0.5.5-2 and 0.5.5-3 have exposed a showstopping bug when used in conjunction with certain madwifi driver versions (specifically 0.9.2+r1784.20061027-1 currently in debian). This

Bug#396055: [PATCH]: include sioq.[ch] in module tarball

at is +responsible for copying required upstream contents into debian module +source tarball staging area. + + -- Kel Modderman <[EMAIL PROTECTED]> Sun, 12 Nov 2006 12:21:59 +1000 + unionfs (1.3.20061029.0124+debian-1) unstable; urgency=low * New upstream snapshot:

Bug#386227: [Pkg-spca5xx-devel] Bug#386227: spca5xx-source: Compile failure with kernel 2.6.18

On Wednesday 18 October 2006 04:22, Brad Sawatzky wrote: > On Tue, 17 Oct 2006, Kel Modderman wrote: > > On Tuesday 17 October 2006 05:23, Moritz Muehlenhoff wrote: > > > severity 386227 grave > > > thanks > > > > > > > Package: spca5xx-sou

Bug#386227: [Pkg-spca5xx-devel] Bug#386227: spca5xx-source: Compile failure with kernel 2.6.18

On Tuesday 17 October 2006 05:23, Moritz Muehlenhoff wrote: > severity 386227 grave > thanks > > On Tue, Sep 05, 2006 at 11:54:29PM -0400, Brad Sawatzky wrote: > > Package: spca5xx-source > > Version: 20060501-1 > > Severity: important > > Tags: patch > > > > > > Some v4l header information got shu

Bug#390787: Unusable: "ath_pci: disagrees about version of symbol "

On Tuesday 03 October 2006 11:46, Chip Salzenberg wrote: > Package: madwifi-source > Version: 1:0.9.2+r1710.20060914-1 > Severity: grave > Justification: renders package unusable > > The drivers seem to build OK for kernel 2.6.16-2-686, but when I try to > actually use them, I get a raft of "disagr

Bug#389171: ndiswrapper-source: doesn't compile on 2.6.17-1 and 2.6.17-2

On Sunday 24 September 2006 23:28, ste wrote: > Package: ndiswrapper-source > Version: 1.23-1 > Severity: grave > Justification: renders package unusable IMHO, this is not grave, but lets not worry about arguing that point . . . > > Building this module fails on 2.6.17-1 and 2.6.17-2 giving me th

Bug#386164: [pkg-wpa-devel] Bug#386164: wpasupplicant is missing versioned depends: on lsb-base

On Wednesday 06 September 2006 05:24, Andreas Janssen wrote: > The missing functions log_action_begin and log_action_end were > introduced in lsb-base 3.0-6. Ok, thanks. wpasupplicant packaging has been updated accordingly. Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "

Bug#386156: hostapd is missing versioned depends: on lsb-base

On Wednesday 06 September 2006 03:32, Andreas Janssen wrote: > Package: hostapd > Version: 1:0.5.5-1 > Severity: serious > Justification: Policy 3.5 > > > hostapd 0.5.5 needs init script functions that are not available > in older versions of lsb-base. Running a backport on Sarge > results in: > >

Bug#374342: Needs more testing

Reinhard Tartler wrote: Madwifi will eventually propagate to testing, and the wpa_supplicant version in same archive will not support it. You mean Version 0.svnr1644.0.9.0-2? Perhaps we can coordinate transition of the two packages? On the other hand, we can tell users to install wpasuppli

Bug#374342: [pkg-wpa-devel] Bug#374342: Needs more testing

Hi Reinhard I am fine if you feel that this package needs more testing for a while, however, I would like to point out what small problems occur if we roll back to the 0.4 series of wpa_supplicant upstream: * non-backwards compatible wpa_supplicant.conf options may disrupt the end use

Bug#364582: [Pkg-spca5xx-devel] Bug#364582: spca5xx-modules-i386: Recommend on non-Debian package

Joerg Jaspert wrote: Package: spca5xx-modules-i386 Severity: serious Hi Your binaries contain a line "Recommends: spcacat, spcaview, spcaserv", but Im unable to find those packages in Debian (or in Provides). Thats against Policy 2.2.1. --8

Bug#362265: madwifi: FTBFS on mipsel

Kel Modderman wrote: Aurelien Jarno wrote: Package: madwifi Version: 0.svn20060207-4 Severity: serious Justification: no longer builds from source Trying to builf madwifi version 0.svn20060207-4 on mipsel, I have seen it now fails to build from source: rm -rf debian/patched /usr/bin/make

Bug#362265: madwifi: FTBFS on mipsel

Aurelien Jarno wrote: Package: madwifi Version: 0.svn20060207-4 Severity: serious Justification: no longer builds from source Trying to builf madwifi version 0.svn20060207-4 on mipsel, I have seen it now fails to build from source: rm -rf debian/patched /usr/bin/make -C tools clean make

Bug#360387: [pkg-wpa-devel] Bug#360387: init script gone

What would people say to providing an init daemon for wpasupplicant in a separate binary package, for example, wparoamd or so? Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#351658: [Pkg-spca5xx-devel] Bug#351658: spca5xx-modules-2.6-k7-smp: doesn't depend on the corresponding kernel package

Gerfried Fuchs wrote: * Kel Modderman <[EMAIL PROTECTED]> [2006-02-07 06:15]: Gerfried Fuchs wrote: Furthermore, a mailinglist -request address as maintainer address is a *very* bad idea, I seriously hope you consider changing that, too. I did not see this in our s

Bug#351658: [Pkg-spca5xx-devel] Bug#351658: spca5xx-modules-2.6-k7-smp: doesn't depend on the corresponding kernel package

Gerfried Fuchs wrote: Package: spca5xx-modules-2.6.15-1-686 Version: 20060101+1 Severity: serious Justification: Policy 7.2 Hi! The modules packages slipped into testing because they don't depend on their corresponding kernel images they are built against. They don't make any sense stan