Updates in svn
lool+alioth at via.ecp.fr
Fri Apr 14 11:40:54 UTC 2006
On Wed, Mar 29, 2006, Kel Modderman wrote:
> I prepared the package in the experimental branch of our svn archive.
Hmm, I've found it in notuploaded/, and I moved it to experimental/
(after removing an empty madwifi/debian tree). Perhaps your svn mv
This move is necessarily disruptive, if you had anything unchecked in
your private copies, you'll have to merge it by hand with the move.
I've uploaded the package to experimental, and I'm now using the
modules with unstbale's wpasupplicant in -D wext mode.
I didn't change anything else because I wanted your name to appear in
the upload (you did all the work after all), here are a couple of
- the madwifi-ng-dev package is useless for most packages in Debian:
since packages which could build against it such as wpasupplicant are
in main, it is not possible for them to build against packages in
- there's no upgrade path for people with current madwifi-source or
madwifi-tools packages installed (that is aptitude update && aptitude
upgrade won't pull madwifi-ng-source)
- the Conflicts are not necessary, Replaces are enough (yeah this is
weird, but it makes upgrades easier, and downgrades harder, and is
really recommended for the sanity of apt)
This issues will have to be worked out before uploading to unstable,
but there's a fundamental naming choice to settle on first: how will
binary packages be named in Debian unstable after the switch?
Because I'm not sure of the output this decision, I uploaded the
madwifi-ng source (in a madwifi source package) to experimental with
the new names for binary packages (this is because of the new binary
packages, the source will be stuck in NEW for a while).
But is it really useful to rename madwifi-* packages to madwifi-ng-*
IMO, it's at least as complicated (if not more) to handle a
transition from madwifi-* packages to madwifi-ng-*, than to make a
transition from madwifi-ng-* packages to madwifi-* packages in the
distributions already using the madiwif-ng-* binary packages.
Here a couple of reasons why I think madwifi-* names are preferable
for Debian unstable and/or in general:
- this would make the upgrade in Debian unstable and probably some
other distros easier (no transitional packages to keep around until
the next Debian stable release)
- the current pacakges are not called madwifi-old :)
- "ng" doesn't mean anything to end users, it would make sense if we
were keeping a madwifi source package with madwifi-old sources
parallel installable with madwifi-ng
But perhaps I miss some arguments on advantages of madwifi-ng-* binary
On a completely unrelated note, I used to have two interfaces handled
by the driver: ath0 and ath1, ath0 being the builtin atheros of my
thinkpad (802.11b) and ath1 the PCMCIA card (Netgear WG511T). I now
have only wifi0 and ath0 (which are IIUC the control interface and the
managed virtual interface of the PCMCIA card), is this is a regression?
0000:02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211
802.11ab NIC (rev 01)
0000:03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212
802.11abg NIC (rev 01)
The driver claims support for AR5211 in my dmesg output.
Loïc Minier <lool at dooz.org>
"You can gtk_main_run, but you can't gtk_widget_hide." --danw, 19-jul-04
More information about the Pkg-madwifi-maintainers