__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
This applet has no unittests (yet). In order to test changes you need to kill update-notifier from your running session (there can only be one) and start it from your local build dir. Make sure you build with --prefix=/usr (or some other location where your ui files are). Then you can do the following: Test updates: Install a package from a previous version and check if update-notifier detects that and shows a update icon. Run apt-get update and check if it detects that a package manager is running. Test hooks: Copy a example hook file into /usr/lib/update-notifier/user.d/ (or touch it) and touch /var/lib/update-notifier/dpkg-run-stamp to trigger it reading the hooks. Modify ~/.update-notifier/hooks_seen to simulate certain conditions. Add identical files to "user.d" to test the duplicates detection. Test reboot notification: Run /usr/share/update-notifier/notify-reboot-required and then do touch /var/lib/update-notifier/dpkg-run-stamp. Test cdrom detection: Put a ubuntu CD into the driver and verify that its detected. Test auto-launch: The "faketime" package is useful for testing the auto-launch funtionatliy $ NO_FAKE_STAT=1 faketime '10 days' update-notifier --debug-updates # aftwards the launch time in u-m needs to be reset $ gsettings reset com.ubuntu.update-manager launch-time
| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| HOOKS | File | 3.66 KB | 0644 |
|
| README | File | 1.64 KB | 0644 |
|
| README.testing | File | 1.28 KB | 0644 |
|
| changelog.gz | File | 5.86 KB | 0644 |
|
| copyright | File | 1.17 KB | 0644 |
|