When I first requested this backport it was to fix a rather major flaw.
The gui window didn't update to show installed drivers. I suppose I
should have filed a bug report instead. My mistake.
--
Please backport ndisgtk 0.7
https://bugs.launchpad.net/bugs/12
You received this bug notification
Public bug reported:
Shouldn't be too difficult as the dependencies are all in Feisty anyway and it
solves some of the main bugs in the version 0.6.
I've installed through prevu and it works great for me.
** Affects: feisty-backports (upstream)
Importance: Undecided
Status: New
**
Is there an ETA for this package to hit the backports repo?
--
Please backport madwifi-tools
https://bugs.launchpad.net/bugs/84952
You received this bug notification because you are a member of Ubuntu
Backporters, which is the bug contact for Edgy Backports.
--
ubuntu-backports mailing list
ubu
I'm rather new to this so please forgive my ignorance.
If b/i/r means that the package builds/installs/runs with prevu on Edgy,
then is does all of these things for me.
I followed the instructions at https://wiki.ubuntu.com/Prevu on my
laptop using an Atheros based D-Link DWL-G650 wireless card a
Public bug reported:
Could you please backport madwifi-tools so that I don't have to build
the whole madwifi package from source just to have monitor/adhoc mode
support. It only appears to depend on libc6.
Does a package have to be in main to be considered? I ask because this
package it in univer
Public bug reported:
Would it be possible to backport nmap 4.10-1 to Dapper?
The Edgy version seems to depend on libc6 (>= 2.4-1), libgcc1 (>=
1:4.1.0) and libstdc++6 (>= 4.1.0).
Would these newer packages exclude nmap from being backported?
Thanks
** Affects: dapper-backports (upstream)
