Bug#596450: unblock: micro-evtd/3.3.3-7
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please allow micro-evtd/3.3.3-7 to migrate to squeeze. The package has
been reviewed and uploaded to unstable by Martin Michlmayr (CCed). The
package is only used on the Buffalo Linkstation Pro/Live and Kurobox Pro
platforms, so the affected userbase is very small; however the update is
quite important for those users.
The upload fixes a bug causing the daemon not to start automatically in
debian-installer, and fixes a number of bashisms in scripts included in
d-i where bash is is not available. Please see the annotated changelog
below for more details.
Thanks,
Ryan
* debian/udeb/micro_evtd.command: Fixed test condition for whether
daemon is already running. (Closes: #580549)
If the daemon is not started correctly, the built-in watchdog timer
kills the machine after 5 minutes. Therefore this fix is important for
debian-installer so that users are not required to start it manually.
* debian/patches/microapl-bashisms.patch: Fixed several more bashisms in
microapl. Based on a patch by Noriaki Mitsunaga. (Closes: #534257)
* debian/patches/eventscript.patch: Fixed more bashisms, so the script
actually copies and runs now.
* debian/patches/script-paths.patch: Refreshed.
These scripts are currently not functional unless bash is used as the
interpreter. It is not reasonable to set bash as the interpreter for
them because they are included in debian-installer.
* debian/init.d:
- Replaced Required-{Start,Stop} with values from
/etc/init.d/skeleton, as the daemon has no special requirements. (Fixes
a lintian error.)
- Added runlevel 1 to Default-Stop. (Fixes a lintian warning.)
Trivial change to fix a lintian error.
* debian/rules: Overrode CFLAGS to work around a segfault that appears
when built with optimizations.
This change is the reason for the delay in sending an unblock request,
since I was trying to debug the crash. It is not caused by my changes;
it appears even when building the unmodified previous version. I wasn't
able to find the cause and so I included this workaround.
Reply to: