[Nut-upsuser] UPS configuration issue?
Sam Varshavchik
mrsam at courier-mta.com
Wed May 14 02:05:37 BST 2025
gene heskett via Nut-upsuser writes:
> However debians legendary slowness to update things does test my patience at
> times. The fact that bookworms default nut is 2.8.0 is an example.
That sounds familiar. Debian's been shipping very old versions of my
packages, which was …irritating. I am not being accusatory, I understand
that it's all volunteer work, and most of the time …there was no volunteer.
But it was still a problem for me.
I solved this problem by boning up, learning how to create deb packages,
then including a script in my tarballs that create deb packages from their
own tarballs – very similar to how including a package.spec in the tarball
allows rpmbuild to build installable rpms directly from the tarball:
"rpmbuild -ta package-version.tar.bz2", sit back, and wait for the binary
rpms to be created.
As far as I know debuild doesn't have anything comparable to this, but what
I hacked up came pretty close. The report from the field was that non-
developers are able to use it. And this solved the "old packages in Debian"
issue and made it go away, for the most part. I only made sure that what I
did was not going to interfere with anything a real, honest to goodness,
Debian or Ubuntu maintainer needs to do, so when one shows up, occasionally,
from time to time, it stays out of their way.
Unfortunately this is not something that works generically, the script is
tailored specifically to the tarball's contents. But that's the general
solution to addressing old stuff in Debian or Ubuntu.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250513/cf2c16e0/attachment.sig>
More information about the Nut-upsuser
mailing list