Needs file rename to conform with pm-utils

[Noel J. Bergman]

As reported in Bug 307312 by Victor Lowther:

===========
Please move the 95anacron and 96laptop-mode hooks out of the 90 - 99
range. See HOWTO.hooks for the ordering convention.

Also, action_wpa should have a numeric prefix -- right now it will run
after NetworkManager has gone to sleep, interfaces possibly taken down,
and network card driver modules unloaded. Needless to say, that might
affect the functioning of the hook.
===========

The documented convention is:

00 - 49: user and (most) package supplied hooks.
If your hook assumes that all of the usual services and userspace
infrastructure is still running, it should be here.

50 - 74: service-handling hooks.
If you need to stop or start a service, you should have a hook in this range.

75 - 89: module and non-core hardware handling.
If you need to load/unload a module, or mess with some non-video related
hardware that would otherwise break suspend or hibernate, the hook that
does that should be in this range.

90 - 99: reserved for critical suspend hooks.
The hooks in this range should not be messed with unless you know what
you are doing. They start with 90chvt and end with 99video

[Scott James Remnant (Canonical) (canonical-scott)]

Has this been reported to Debian? That seems the correct place to fix this

[Noel J. Bergman (noeljb)]

Not by me. At some point, this frequent question/request begs the question: how many accounts on how many systems should an Ubuntu user need to report bugs? I've had to go upstream to Gnome, OpenOffice, more than a few individual developers, when all I want to do is report a bug in Ubuntu.

In any event, how do you suggest reporting to Debian? reportbug?

[Scott James Remnant (Canonical) (canonical-scott)]

You've filed the bug, so you clearly know more about the issue than anyone else pertinent.

If I was just to echo your bug to Debian, and Debian were to ask a question, I wouldn't know how to respond, etc.

[Chow Loong Jin (hyperair)]

On Thursday 22,April,2010 10:57 AM, Noel J. Bergman wrote:
> Not by me. At some point, this frequent question/request begs the
> question: how many accounts on how many systems should an Ubuntu user
> need to report bugs? I've had to go upstream to Gnome, OpenOffice, more
> than a few individual developers, when all I want to do is report a bug
> in Ubuntu.

If you don't do it, someone else would need to do it, be it an Ubuntu developer,
a concerned upstream, or another user. If you want to see an upstream bug fixed
fast, then report it directly upstream. Otherwise you will have to wait for
someone to stumble upon your bug downstream here, and then forward it upstream,
wait for a response (often a request for more information), bring it back here,
so on and so forth. These round-trips take a considerable amount of time per bug.

Now, imagine dealing with hundreds of bugs the same way. The least you could do,
as the bug reporter, is to bring it upstream yourself. Or you could just be
patient, but sometimes that can lead to bugs being forgotten.

Do also keep in mind that due to the nature of Ubuntu as a distribution, there
are loads of software upstream of Ubuntu that the bugs originate from. I'd
estimate 90% of the bugs in Ubuntu to be upstream bugs, in any case.

> In any event, how do you suggest reporting to Debian? reportbug?

Yes, reportbug.

--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Developer

[Launchpad Janitor (janitor)]

This bug was fixed in the package wpasupplicant - 0.6.10-2

---------------
wpasupplicant (0.6.10-2) unstable; urgency=low

  * Switch to source format 3.0 (quilt), drop quilt build dependency
    and remove '--with quilt' from dh command in debian/rules.
  * Fix "FTBFS on kfreebsd-gnu" with addition of 21_kfreebsd.patch.
    Thanks to work by Stefan Lippers-Hollmann and Petr Salinger.
    (Closes: #480572)
  * Disable experimental feature CONFIG_IEEE80211W (management frame
    protection) due to it not being supported by any driver but ath9k
    and it generating ioctl errors which cause much concern among users
    for little to no benefit.
  * Add traling blank line to debian/NEWS to assist apt-listchanges as
    per lintian advice.
  * Cherry pick 30_cfg80211_association_optimisation.patch from upstream
    git. Add cfg80211-specific optimization to avoid silly behavior.

wpasupplicant (0.6.10-1) unstable; urgency=low

  * New upstream release.
    - wpa_msg_ctrl helper which can send messages to the control interface
      without logging when running in non-debug mode. Used for
      CTRL-EVENT-SCAN-RESULTS. (Closes: #539915) (LP: #352118)
  * Remove members of pkg-wpa-devel team from Uploaders who no longer
    participate in maintenance. Thanks for their past work. (Closes: #529501)
  * Disable building of atmel driver backend, neither atmel_{cs,pci},
    nor at76c50x-usb ever used it and atmelwlandriver is not in Debian
    and has been abandoned upstream in 2005. Thanks to Stefan Lippers-
    Hollmann for doing the research.
  * Remove a few traces of ath/madwifi from debian/NEWS and
    debian/README.Debian, thanks again to Stefan Lippers-Hollmann.
  * Prefix etc/pm/sleep.d/ pm-utils hook in the 50 - 74 sequence range to
    comply with sequencing rules as per pm-action(8) (LP: #307493). Provide
    the symlink to our hook in /usr/lib/pm-utils/sleep.d/ rather than
    /etc/pm/sleep.d/. (Closes: #557344)
  * Modify wpa_action and associated functions to use logger(1) instead of
    piping to /var/log/wpa_action.$IFACE.log.
  * Ensure removal of obsolete logrotate conffiles now that all
    wpa_supplicant/wpa_cli output is logged to syslog.
  * Support help action in action_wpa.sh. (Closes: #548995)
  * Build-depend on libreadline-dev instead of libreadline5-dev.
    (Closes: #553891)
  * Do not use sed to comment all network blocks out in the example
    wpa_supplicant.conf.
  * Do not strip upstream manual pages from source tree, do no generate
    them at build time, do not build-depend on dockbook. We currently do
    not modify them, so these build-dependencies and steps are expensive.
  * Convert debian/rules to use dh
    - build depend on debhelper (>= 7.4.12~) for dh override support, qmake
      build class support and --builddirectory argument support
    - install wpagui files via debian/wpagui.install
    - rename debian/ifupdown/wpa_action.sh to debian/ifupdown/wpa_action
      and install via debian/wpasupplicant.install
    - install wpasupplicant ifupdown scripts via debian/wpasupplicant.install
  * CFLAGS, CXXFLAGS, LDFLAGS and V are exported by debian/rules.
  * Remove uupdate command from debian/watch, it is not ...

[Serge Hallyn (serge-hallyn)]

Please reply if this is still an issue on a supported release.