* Package name : udev-notify Version : 0.1.3 Upstream Author : USU Team <lfu.project@gmail.com> * URL : http://udev-notify.learnfree.eu/ * License : GPLv3 Programming Lang: Python Description : Display notifications about newly plugged hardware udev-notify is a simple free software app for Ubuntu that runs in background and shows visual notifications when you plug-in a new device - Camera, Joystick, Removable Drive, Media Player etc... cIt uses udev for monitoring hardware changes, and NotifyOSD, notification-daemon, xfce4-notifyd or knotify (whichever you have installed) for the notifications.
Hi, nodiscc wrote: Nice idea. I'd like to see such functionality in Debian, too. Thanks for the request. Upstream (Cc'ed) already has a .deb package of it, which does work on Debian, too. But it does not meet Debian's standards yet. At least I found the following issues: * Neither copyright nor changelog file * Mixed up section and archive (maybe an Ubuntu thing) * No source package at all. Binary package is built by a script tools/debian-package.sh plus Makefile * Embedded code copy of pyudev instead of depending on python-pyudev * /usr/bin/udev-notify necessarily starts a bash process (should either use /bin/sh instead of /bin/bash and exec or it should be replaced by be a symlink to /usr/share/udev-notify/udev-notify.py) * Missing dependency (either "Depends" or at least "Recommends") on a notification-daemon. (I don't expect it to work without as it's stated on the website that a notification-daemon is needed.) This information can neither be found on the web page nor in the source code, just on https://launchpad.net/udev-notify so far -- it would more convincing if there would be a license mentioned (or included) somewhere inside the source code. I'd be glad if upstream would bring their own .deb in shape for Debian and I'd help with that and would sponsor uploads to Debian. Regards, Axel
RFP has no visible progress for a long time, so closing.
Hi, I'm still interested in such a feature in Debian, hence reopening. And since the bug report has been closed by the original submitter, I'm setting myself as submitter now so the original submitter won't be bothered anymore. Regards, Axel