too much for an NMU?
-----BEGIN PGP SIGNED MESSAGE-----
In the following message, I'm asking if I'm doing too much with an NMU.
I'd like your opinions.
I've already fixed the following bugs in pilot-link:
#40343: Date fields are incorrect with install-datebook in the pilot-link
#41511: pilot-link still depends on perl
#32192: Alpha patches for pilot-link in potato (actually testing this
one right now.)
#41616: pilot-link: upgrade to perl-5.005 removes pilot-link in unstable (potato)
#35034: pilot-link-perl: cannot locate loadable object
The following are already fixed:
#38051: pilot-link: `pilotconfig' permission denied in postinst
#40337: pilot-link: pilotconfig has a spelling error: crable
I'd like to fix the following bugs but I'm worried that I might be
stepping pasts the bounds of an NMU to fix them:
#34423: pilot-xfer: "press hotsync" should be on stderr
#37361: pilot-link asked me again about /dev/pilot
#38382: pilot-link: Pilot-mail does not prompt you to press the HotSync button on the Pilot cradle.
#31631: pilot-link.deb depends on tcl and tk
#38383: pilot-link: Pilot-mail segfaults when Ctrl-C is used to stop the process.
This actually only leaves:
#24357: pilot-link has namespace pollution
#20782: pilot-link suggestion
#40336: pilot-link: can't compile gnome-pilot
which I think are definitely too much for an NMU...
<firstname.lastname@example.org> <http://www.daft.com/~torin> <email@example.com> <firstname.lastname@example.org>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI/Pilot programmer/tutor @
@ Make a little hot-tub in your soul. @
-----BEGIN PGP SIGNATURE-----
Comment: Processed by Mailcrypt 3.5.1, an Emacs/PGP interface
-----END PGP SIGNATURE-----