Bug#722027: dates ready to be removed?!
Hello! Since "dates" is orphaned and seems pretty dead upstream, I'd suggest removing this package. The package seems to have been dropped from both Ubuntu and Fedora already. -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130916202627.ga16...@amd64.fatal.se
Bug#722025: removal bug filed for contacts
Control: severity -1 serious Hello! I've filed a removal bug for this package since "contacts" is orphaned, unmaintained upstream, no longer builds, and "gnome-contacts" is probably a better alternative these days... See Bug#723772 -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130919175117.ga31...@amd64.fatal.se
Bug#753722: dnet-common: please suggest iproute2 instead of iproute transitional package
Package: dnet-common Version: 2.63 Severity: normal Usertags: iproute-removal Dear Maintainer, The iproute package is now a transitional package to iproute2. It will soon be removed. Please update your suggests to iproute2. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140704135242.547.41359.report...@heavy.fatal.se
Bug#748935: Fwd: Initial patch
Hello Samuli Suominen. Thanks for the patch! Adding the correct bug number to CC to file it there. On Mon, Jul 07, 2014 at 11:01:57AM +0300, Samuli Suominen wrote: > I totally suck at using Debian bugs and I don't really want to spend > time figuring out what I did wrong > > Maybe you can post it to the proper bug. Sorry for trouble. > > Using this patch in Gentoo. Minimal changes to make it build again. > > > Original Message > Subject: Initial patch > Date: Mon, 07 Jul 2014 10:58:34 +0300 > From: Samuli Suominen > To: 748...@bugs.debian.org > > > > Initial patch to compile against UPower >= 0.99 > > > > --- upower.c > +++ upower.c > @@ -62,8 +62,10 @@ > return 0; > } > > + #if !UP_CHECK_VERSION(0, 9, 99) > /* Allow a battery that was not present before to appear. */ > up_client_enumerate_devices_sync(up, NULL, NULL); > + #endif > > devices = up_client_get_devices(up); > > -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140707083125.ga29...@fatal.se
Bug#752443: upower 0.99 transition started
Control: severity -1 serious Hello! The upower transitions (#751953) has now been started and this makes your package fail to build from source in unstable. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714092519.ga32...@fatal.se
Bug#748935: upower transition started
Control: severity -1 serious Hello! The upower transition started and the wmbattery package now fails to build from source in unstable. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714105431.ga...@fatal.se
Bug#1022011: dleyna-server: transition to gssdp/gupnp 1.6.0
Package: dleyna-server Version: 0.7.2-1 Severity: normal Tags: fixed-upstream Dear (non-existant) Maintainer, New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI and thus bumped the SONAME. A transition is needed. The new versions are currently stuck in binary-NEW but should hopefully soon be available in experimental (you can `gbp clone vcsgit:gssdp`, `gbp clone vcsgit:gupnp` and build them yourself for now if you wish). Please consider uploading a version of dleyna-server to experimental that is compatible with the new SONAMEs. The relevant upstream commit is: https://github.com/phako/dleyna-server/commit/e7f64192643f5783e19482a11697d The relevant bug report for coordinating the transition is #1022003 Regards, Andreas Henriksson
Bug#1022009: dleyna-core: transition to gssdp/gupnp 1.6.0
Source: dleyna-core Version: 0.7.0-1 Severity: normal Tags: fixed-upstream Dear (non-existant) Maintainer, New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI and thus bumped the SONAME. A transition is needed. The new versions are currently stuck in binary-NEW but should hopefully soon be available in experimental (you can `gbp clone vcsgit:gssdp`, `gbp clone vcsgit:gupnp` and build them yourself for now if you wish). Please consider uploading a version of dleyna-core to experimental that is compatible with the new SONAMEs. The relevant upstream commit is: https://github.com/phako/dleyna-core/commit/b88f231affc697be813d7c77c17e3130df8 The relevant bug report for coordinating the transition is #1022003 Regards, Andreas Henriksson
Bug#1022010: dleyna-renderer: transition to gssdp/gupnp 1.6.0
Package: dleyna-renderer Version: 0.7.2-1 Severity: normal Tags: fixed-upstream Dear (non-existant) Maintainer, New upstream releases of gssdp and gupnp 1.6.0 has broken the ABI and thus bumped the SONAME. A transition is needed. The new versions are currently stuck in binary-NEW but should hopefully soon be available in experimental (you can `gbp clone vcsgit:gssdp`, `gbp clone vcsgit:gupnp` and build them yourself for now if you wish). Please consider uploading a version of dleyna-renderer to experimental that is compatible with the new SONAMEs. The relevant upstream commit is: https://github.com/phako/dleyna-renderer/commit/b3a06c8bc4b91803d7bde312f49a6 The relevant bug report for coordinating the transition is #1022003 Regards, Andreas Henriksson
Bug#1022009: UPCOMING REMOVAL, also: New upstream release - new home, new repo layout
Control: severity -1 serious Control: clone 1022009 -2 Control: reassign -2 dleyna-connector-dbus Control: retitle -2 dleyna-connector-dbus: transition to gssdp/gupnp 1.6.0 Hello who ever is interested in dLeyna in Debian, dLeyna 0.7 had a new upstream maintainer[1] and a new home[2]. With dLeyna 0.8 the project again moved[3] and the four repositories was merged into a single dleyna repo[4]. Likely the project should be updated to 0.8 using a single source package based on the new upstream mono-repo. I've prepared a new initial packaging at https://salsa.debian.org/debian/dleyna in case anyone wants to persue this, but I will *NOT* upload this myself. I'm not a user of dLeyna and I'm not interested in maintaining the packages. I could possibly send them into experimental to get some exposure and to easier to find for who ever is interented in picking them up. If you want to maintain the package but need a sponsor, feel free to ask me (but debian-mentors and possibly debian-gnome are also great places to reach out to)! Since a gupnp transition[9] is coming up I'm planning to very soon ask for dleyna to be removed from Debian (unstable, and thus testing)! In case noone steps up to take care of dLeyna that likely means it will not be part of the next/upcoming Debian Stable release. FWIW the initial packaging (at https://salsa.debian.org/debian/dleyna) has only been compile tested and file comparison with old binary packages and new binary packages are roughly the same. Running piuparts would likely be a good idea. Adding debian/*.symbols files for keeping track of library symbols as well (could possibly be picked up from the old repositories[5][6][7][8]). Please contact me immediately if you'd like to take care of this package and avoid me filing for removal! [1]: http://jensge.org/2021/04/08/dleyna-updates-and-general-project-things/ [2]: https://github.com/phako/ [3]: http://jensge.org/2022/07/26/dleyna-has-moved/ [4]: https://gitlab.gnome.org/World/dLeyna [5]: https://salsa.debian.org/debian/dleyna-core [6]: https://salsa.debian.org/debian/dleyna-renderer [7]: https://salsa.debian.org/debian/dleyna-server [8]: https://salsa.debian.org/debian/dleyna-connector-dbus [9]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022003
Bug#1034223: powerman: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Hello Laurent Bigonville, On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: powerman > Version: 2.3.27-2 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package powerman is shipping files (.service, .socket or > .timer) in /usr/lib/systemd/system. > > This is not supported by the version of dh_installsystemd/debhelper currently > in unstable and bookworm (See: #1031695). That means that currently your > service might not be enabled at boot and/or started as expected. [...] Note that debian/rules has: ``` override_dh_installinit: dh_installinit --no-start --no-enable override_dh_installsystemd: dh_installsystemd --no-start --no-enable ``` So do you agree that the severity of this bug report should be downgraded (maybe even closed)? Regards, Andreas Henriksson
Bug#1034214: tcmu-runner: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: tcmu-runner > Version: 1.5.4-4 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package tcmu-runner is shipping files (.service, .socket or > .timer) in /usr/lib/systemd/system. [...] tcmu-1.5.4> grep -R systemd.system . ./debian/tcmu-runner.install:debian/tmp/usr/lib/systemd/system/tcmu-runner.service ./README.md:1. If using systemd, copy `org.kernel.TCMUService1.service` to `/usr/share/dbus-1/system-services/` and `tcmu-runner.service` to `/lib/systemd/system`. ./CMakeLists.txt: install(FILES tcmu-runner.service DESTINATION /usr/lib/systemd/system/) These paths are wrong and the culprit of this bug report. You could change them to use the currently correct path, but then you would have to revert that again after bookworm is released when the paths will change again. A better solution would derive the path from systemd.pc, eg. pkg-config --variable=systemdsystemunitdir systemd (Note: this needs pkg-config and systemd in build-deps) Since the upstream build system is CMake, there are plenty of others to look at of how to implement using pkg-config and querying the variable in CMake. This should give you atleast a few hits that could be possible examples to follow: https://codesearch.debian.net/search?q=systemdsystemunitdir+path%3ACMake&literal=0 https://codesearch.debian.net/search?q=systemdsystemunitdir+path%3AFindSystemd&literal=0 Regards, Andreas Henriksson
Bug#862847: still using transitional package dependency, will become uninstallable
Control: severity 862850 important Control: severity 862848 important Control: severity 824679 important Control: severity 841001 important Control: severity 862847 important Hello! A gentle reminder that the dropping of the transitional iproute package (which has now been obsolete for several releases) is imminent. This will result in your package becoming uninstallable if the reported issue is still not fixed. Regards, Andreas Henriksson
libglade2 unmaintained and affected by python2 removal
affects 895517 + aeskulap desmume exult-studio foxtrotgps fyre g3dviewer gfm ghemical gpaint guile-gnome2-gtk kconfig-frontends kino libglade2.0-cil libglademm-2.4-1v5 libgnomecanvas2-0 libgtkdatabox0-libglade liblablgtk2-ocaml libswami0 marionnet mdk mialmpick ogmrip ogmrip-plugins planner plotdrop rfdump screentest tiemu wbar-config xscreensaver thanks Please note that src:libglade2 is affected by the ongoing python2 removal and as #895517 states: "libglade2-0: deprecated and unmaintained upstream" so don't expect anyone to port it. See #936867 for the specific python2 bug report. (Please remove your package from affects once you no longer depend on libglade2.) Regards, Andreas Henriksson
Bug#872118: mdadm: fdisk build-dependency needed (for tests)
Hi, I've quickly looked at this again and I'm not unsure if an fdisk build-dependency really is needed (for tests). The tests/07autodetect file uses sfdisk, this file seems to potentially get executed from ./test The Makefile has a test target, but that only echos out to run ./test as root and doesn't actually run it. It thus doesn't look to me like the 07autodetect test is actually run during a normal build. Invoking the ./test suite seems to be something (only) manually done, so maybe there's no need for a (build-)dependency after all Regards, Andreas Henriksson
Bug#887298: libploop1 should depend on e2fsprogs explicitly
Control: tags -1 + patch
Hello,
See attached patch adding e2fsprogs dep to libploop1.
(Don't have my key here, so can't upload.)
Regards,
Andreas Henriksson
diff -Nru ploop-1.15/debian/changelog ploop-1.15/debian/changelog
--- ploop-1.15/debian/changelog 2017-11-24 20:07:16.0 +0100
+++ ploop-1.15/debian/changelog 2018-01-15 16:57:26.0 +0100
@@ -1,3 +1,10 @@
+ploop (1.15-5) unstable; urgency=medium
+
+ * QA upload.
+ * Add e2fsprogs to dependencies of libploop1 (Closes: #887298)
+
+ -- Andreas Henriksson Mon, 15 Jan 2018 16:57:26 +0100
+
ploop (1.15-4) unstable; urgency=medium
* QA upload.
diff -Nru ploop-1.15/debian/control ploop-1.15/debian/control
--- ploop-1.15/debian/control 2017-11-24 20:07:16.0 +0100
+++ ploop-1.15/debian/control 2018-01-15 16:56:24.0 +0100
@@ -24,7 +24,7 @@
Section: libs
Architecture: linux-any
Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}, parted
+Depends: ${shlibs:Depends}, ${misc:Depends}, parted, e2fsprogs
Recommends: lsof
Pre-Depends: ${misc:Pre-Depends}
Description: ploop API library
Bug#887233: libploop-dev should depend on e2fsprogs explicitly
Control: tags -1 + wontfix On Sun, Jan 14, 2018 at 08:07:05PM +0100, Helmut Grohne wrote: [...] > /usr/lib/x86_64-linux-gnu/libploop.a contains dumpe2fs, e2fsck, e4defrag, > filefrag, fsck.ext4, resize2fs and tune2fs. According to file it is a current > ar archive [...] I've investigated libploop which indeed has code to run commands from e2fsprogs. For the case of dynamic linking dependencies should be added, see #887298. This particular bug report is about the *static* library shipped in the -dev package though, and I don't think any changes should be done here for the following reason: * e2fsprogs is not needed at *build*-time (only runtime). * e2fsprogs will be needed by the application that (statically) links to libploop.a (at runtime), and there's no way for the libploop-dev to 'transfer' the correct dependencies. * There's no reason to expect the libploop-dev package be installed on users systems running the applications that have statically linked to libploop.a (Please also note that Debian normally avoids using static linking so this would mainly affect third party applications not shipped in debian.) I'm thus tagging this bug report wontfix. (And alternative approach might be to stop shipping libploop.a at all.) Regards, Andreas Henriksson
Bug#887274: boxbackup-server should depend on e2fsprogs explicitly
Control: tags -1 + patch
On Sun, Jan 14, 2018 at 08:03:02PM +0100, Helmut Grohne wrote:
> Package: boxbackup-server
> Version: 0.12~gitcf52058f-3
> User: helm...@debian.org
> Usertags: nonessentiale2fsprogs
[...]
> DEBIAN/config contains tune2fs. According to file it is a Bourne-Again shell
> script, ASCII text executable
> DEBIAN/templates contains tune2fs. According to file it is a UTF-8 Unicode
> text
[...]
The templates match could be considered a false positive. The
boxbackup-server.config match on the other hand is guarded with
a check for tune2fs existance, but unfortunately because of broken
shell quoting it will likely not work as intended.
(Atleast in my tests 'if [ -x $EMPTYORUNSET ]' evaluates to true.)
I'm attaching a patch that both fixes the quoting (in several more
places than just the one mentioned above) and also adds e2fsprogs
to recommends (but suggests might also work).
I'm not uploading this since boxbackup has other bugs (including RC)
which should also be investigated. (and if boxbackup is getting
removed from buster because of unfixed RC bugs there's no point in
fixing this one either...)
If someone cares for boxbackup they should adopt the package. (It
atleast seems to be actively maintained upstream.)
Regards,
Andreas Henriksson
diff -Nru boxbackup-0.12~gitcf52058f/debian/boxbackup-server.config
boxbackup-0.12~gitcf52058f/debian/boxbackup-server.config
--- boxbackup-0.12~gitcf52058f/debian/boxbackup-server.config 2017-06-30
21:01:19.0 +0200
+++ boxbackup-0.12~gitcf52058f/debian/boxbackup-server.config 2018-01-17
16:28:30.0 +0100
@@ -32,14 +32,14 @@
DIR2=`echo "$RET" | awk '{ print $2 }'`
DIR3=`echo "$RET" | awk '{ print $3 }'`
-if [ -n $DIR1 ]; then
+if [ -n "$DIR1" ]; then
if [ -z "$DIR2" -o -z "$DIR3" ]; then
- DIR2=$DIR1
- DIR3=$DIR1
+ DIR2="$DIR1"
+ DIR3="$DIR1"
fi
PATHOK=1
- for i in $DIR1 $DIR2 $DIR3; do
+ for i in "$DIR1" "$DIR2" "$DIR3"; do
if [ `echo $i | awk '{ if
(/^\/[A-Za-z0-9\.\-_]+\/?([A-Za-z0-9\.\-_]+\/?)*$/) { print 1 } else { print 0
} }'` = 0 ]; then
PATHOK=0
fi
@@ -60,13 +60,13 @@
# Try to figure out the block size of the first partition given
db_get boxbackup-server/raidDirectories
if [ "$OLDRAIDDIR" != "$RET" ]; then # Directories have been changed so we can
try to guess the block size
-TMPDIR=`echo $DIR1 | sed 's/\/$//'`
+TMPDIR=`echo "$DIR1" | sed 's/\/$//'`
while [ "$TMPDIR" != "" ]; do
DEV=`df -P | grep "$TMPDIR$" | awk '{ print $1 }'`
if [ -z "$DEV" ]; then
- TMPDIR=`echo $TMPDIR | sed 's/\/[^\/]*$//'`
+ TMPDIR=`echo "$TMPDIR" | sed 's/\/[^\/]*$//'`
else
TMPDIR=""
fi
@@ -74,10 +74,10 @@
if [ "$DEV" != "" ]; then
TUNE2FS="$(command -v tune2fs)"
- if [ -x ${TUNE2FS} ]; then
+ if [ -x "${TUNE2FS}" ]; then
BS=`${TUNE2FS} -l $DEV 2>/dev/null | grep 'Block size' | awk
'{print $3 }'`
- if [ $? = 0 -a $BS != "" ]; then
+ if [ $? = 0 -a "$BS" != "" ]; then
db_set boxbackup-server/raidBlockSize "$BS"
fi
fi
@@ -97,7 +97,7 @@
fi
fi
-if [ $BSOK = 0 ]; then
+if [ "$BSOK" = 0 ]; then
db_input critical boxbackup-server/incorrectBlocksize || true
db_go
fi
@@ -108,4 +108,3 @@
db_go
exit 0
-
diff -Nru boxbackup-0.12~gitcf52058f/debian/changelog
boxbackup-0.12~gitcf52058f/debian/changelog
--- boxbackup-0.12~gitcf52058f/debian/changelog 2017-06-30 21:01:19.0
+0200
+++ boxbackup-0.12~gitcf52058f/debian/changelog 2018-01-17 16:28:35.0
+0100
@@ -1,3 +1,14 @@
+boxbackup (0.12~gitcf52058f-4) UNRELEASED; urgency=medium
+
+ * QA upload.
+ * debian/boxbackup-server.config: Fix quoting of variables primarily
+fixing the logic that handles when tune2fs is not available.
+ * Have boxbackup-server package Recommend e2fsprogs since the
+package configuration (optionally) uses tune2fs in some cases.
+(Closes: #887274)
+
+ -- Andreas Henriksson Wed, 17 Jan 2018 16:28:35 +0100
+
boxbackup (0.12~gitcf52058f-3) unstable; urgency=medium
* QA upload.
diff -Nru boxbackup-0.12~gitcf52058f/debian/control
boxbackup-0.12~gitcf52058f/debian/control
--- boxbackup-0.12~gitcf52058f/debian/control 2017-06-30 21:01:19.0
+0200
+++ boxbackup-0.12~gitcf52058f/debian/control 2018-01-17 16:28:35.0
+0100
@@ -33,6 +33,7 @@
ucf,
${misc:Depends},
${shlibs:Depends}
+Recommends: e2fsprogs
Description: server for the BoxBackup remote backup system
BoxBackup is an automatic on-line backup system.
The server waits for connections from remote clients,
Bug#887243: gfxboot should depend on e2fsprogs explicitly
On Sun, Jan 14, 2018 at 08:05:04PM +0100, Helmut Grohne wrote: > Package: gfxboot [...] > /usr/bin/gfxboot contains tune2fs. According to file it is a Perl script text > executable [...] It indeed seems like gfxboot will launch both mkfs.ext[23] and tune2fs when the filesystem is ext2 or ext3 (while ext4 falls under 'unsupported filesystem'). https://sources.debian.org/src/gfxboot/4.5.2-1.1-5/gfxboot/#L382 Apart from ext2/ext3 gfxboot also seems to support reiserfs (but not reiser4), xfs and fat filesystems but there's no package relationship specified to any of reiserfsprogs, xfsprogs or dosfstools either. Would be great to hear from maintainers if all of them missing is a mistake or if maybe there's no need for a relationship against e2fsprogs either. Regards, Andreas Henriksson
Accepted partimage 0.6.9-6 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Feb 2018 02:12:09 +0100 Source: partimage Binary: partimage-server partimage Architecture: source Version: 0.6.9-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Henriksson Description: partimage - backup partitions into a compressed image file partimage-server - server to use partimage across a network Closes: 887200 Changes: partimage (0.6.9-6) unstable; urgency=medium . * QA upload. * Have partimage recommend e2fsprogs (Closes: #887200) - code first checks if /sbin/e2fsck is available, so hard dependency should not be needed. Users likely still want it to be though, so recommend e2fsprogs. Checksums-Sha1: ad2dd22a0feb2722fb31723ad50f9e80e3dc9a92 1952 partimage_0.6.9-6.dsc 71cf80e5ad8532890cf2e1367e3e79623d1544f4 16592 partimage_0.6.9-6.debian.tar.xz f39e74347c6bdc7ad6a844bd20546277c08c2bec 6642 partimage_0.6.9-6_amd64.buildinfo Checksums-Sha256: c21174ed0d569e75aeff7ae1bf37ced6495febf30b3e6fc6f06b76c68f09286a 1952 partimage_0.6.9-6.dsc 1a29e50eaca3544cf1de24583d39cc182abfc0408e6aab55025739abbaed7986 16592 partimage_0.6.9-6.debian.tar.xz 09ccb2850d2690afb851f43a9b4afe7120afb96728188b38c6eaeaaba3373166 6642 partimage_0.6.9-6_amd64.buildinfo Files: 3dbb0876c79a4793a075afec3ec218b4 1952 admin optional partimage_0.6.9-6.dsc 52d187eee4b7f2b2fd61924cee3effe9 16592 admin optional partimage_0.6.9-6.debian.tar.xz b1653bb479a0115a218231caea8b4ec7 6642 admin optional partimage_0.6.9-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlp2X30RHGFuZHJlYXNA ZmF0YWwuc2UACgkQC8R9xk0TUwZfJA/+JUQvc5oaXnMb0JVH8kk1EVcsRF7Ti6Fe +yGfcAoiBATqqsBduI7E1yv9vQDJPsuqTtBUimEQedxfPrGgt6skq9oejMdsvOw9 jAoi/bJmG5Ox5Ok/8WWReGseNB2htYterQQY7WXpDUsymg2ellT0UG8e9bpd89+m j34Kfx+9kpye0WClZO9jQJk162+pJmamiYU8+3b3bp+iwCBt9xm8vVLloyIa3OcI 19C8Ke4AOpgTMvCLkrB/Pfuv18yEXqEGFrbOEcDwe/M7WxdeYY5CRBvYSFXKgpbE cTgFHMGKZ2jcn4pKeLu6Zxjc4X+StoX0/ayYrFWKJnLlC2jAyCbvmEw1Dx3RVelf w3L/JZg7RUhH7bkSZ/QP1b6q5vGZJkxjQJz5h5wUvF3Yixujmuubl/9l1mFwtIHu W8MsO+EKFRH0/nO9SVMuCkTJewtUoghVuRmHWNBM6ANY2ylYXS2d4QUVUFcPB6HB ZwDDXGYQtmRceDFdeyIrsrhydhoRVWeMQ+eHHTcrVvOTpiYCd9Tj8HtEfezOIqa1 i0Hm/IN7JVvFNcFYAnliNEufKFiaiTwDgWZfQGQkhY0DkFxDoDGL+1D3En8yBX1q f+kQIAFDgOc2XgGROifaPzjNEShaWKklzf4Yop9B46x6cU3LDDO1DsKvHJ3Pq2kg B1LehJiTmmA= =wMSE -END PGP SIGNATURE-
Accepted lxctl 0.3.1+debian-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 Feb 2018 18:06:27 +0100 Source: lxctl Binary: lxctl Architecture: source Version: 0.3.1+debian-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Henriksson Description: lxctl - Utility to manage LXC Closes: 887199 Changes: lxctl (0.3.1+debian-4) unstable; urgency=medium . * QA upload. * Add e2fsprogs to Recommends. (Closes: #887199) - lvextend is used before resize2fs, but lvm2 is only a recommends rather than Depends, so likely a hard dependency isn't needed. * debian/watch: replace deprecated github redirector as suggested by lintian. Checksums-Sha1: 993a776088ac40caef6ab26187ac5292ae90371f 1871 lxctl_0.3.1+debian-4.dsc c0fafe9c23e9ed9dc46267d44a36f65ecd798af1 4856 lxctl_0.3.1+debian-4.debian.tar.xz 6c62e753a3c798989a146583f64e8181d7281705 5498 lxctl_0.3.1+debian-4_amd64.buildinfo Checksums-Sha256: 8e0f948a18a9329a6c5af5f69d8b195023f5e1a1f6eaa879aa4cfa9bd2d19493 1871 lxctl_0.3.1+debian-4.dsc cce015f786327141c59879ac0f4d731a858c6b050f3520f4fc588564cf4a479b 4856 lxctl_0.3.1+debian-4.debian.tar.xz c00ed9d6ea4d3553b283633a91758e50dd70c0eb440f9a66baed78e0084f166f 5498 lxctl_0.3.1+debian-4_amd64.buildinfo Files: 72aa4027e4d21218b27c84da27f9dbc7 1871 admin optional lxctl_0.3.1+debian-4.dsc a5da292265d8ba16cc5b80efdb39722a 4856 admin optional lxctl_0.3.1+debian-4.debian.tar.xz 35b5ad66ef0625dd327e3e1740fdfc8b 5498 admin optional lxctl_0.3.1+debian-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlqBy+ERHGFuZHJlYXNA ZmF0YWwuc2UACgkQC8R9xk0TUwYXtw/8D4nFrU7f/RqNRzW1Jj1HrGk3EkNitLw6 7jBNNDYsHFZwnZxf54r76WyCn0x9xNzSLRyXA5unzZJoePgGZphO5Cdcj4RXA/E2 mQay0I5Z7Ynoy8JNAE8ZVvNpaL79920tPzacsFDyn83u5zgb582R+ycgQHgh9wTY InzVi9Ao9NTb/q9kFsuPW1DR8FrrfWyRza/1smSLuQ4SFoHpF0GrINkKScMhWHe3 FiIzVR+Km2H4XrhvISVqiBQ474DL3s3zdf+4CEhmBpgW2U69h6q41pV3NzPRaVLD KKr0P/hErRrpShqexgQ3lmBNsogIZ8AprM9fyXvNyWuRQgBSLE/8EP9EKhtfRcED jQzEBSjhiXKand6K5dtUohE4uHor+ftKRs7+ykzLbp8AJeQIX6P67IJ4ThXHjk5N DLuirNU9kwlXBg5R9h5rEy26t8AwY2FzSkAMgCLtWl2wx3665K59wokRdMRVBu60 cFlJ9poXDay/G4F+Y/1F5oglYrZ5NWdUSZi6OBije5daSyQJVAry3ki+k3rg8He0 S4q5Hn4iNQVKyaX4Q2IADPoDp7op11fU1yA/511vqY761GXtHqZ64VlzKdj6dvwr ++Lv0EjkZiUX4LPxIZhgg+gRPbrYl6jch+232a4uGDyukgD4NnJWvE+dEj/iuhvX bzpGoMtxXYk= =JvZr -END PGP SIGNATURE-
Bug#887284: autofs should depend on e2fsprogs explicitly
Control: retitle -1 autofs should build-depend and recommend e2fsprogs Control: tags -1 + confirmed On Sun, Jan 14, 2018 at 08:02:46PM +0100, Helmut Grohne wrote: > Package: autofs [...] > /usr/lib/x86_64-linux-gnu/autofs/mount_ext2.so contains fsck.ext2, fsck.ext3 > and fsck.ext4. According to file it is a ELF 64-bit LSB shared object, > x86-64, version 1 (SYSV) [...] Other filesystem specific mount modules has the package for their respective tools in the Recommends field so I would say that's where e2fsprogs belongs as well. (But someone might decide to make it a stronger Depends just because ext is somehow special.) Additionally the configure script tries to look up the full path for the tools, so e2fsprogs should likely also be added to build-depends to make sure the tools are around and can be detected at build-time. I'm CCing Laurent Bigonville who has done the previous QA upload and also has a pending change in the packaging repository hoping he can upload both of them at the same time. Regards, Andreas Henriksson
Accepted autofs 5.1.2-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 17 Feb 2018 22:24:44 +0100 Source: autofs Binary: autofs autofs-ldap autofs-hesiod Architecture: source Version: 5.1.2-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Henriksson Description: autofs - kernel-based automounter for Linux autofs-hesiod - Hesiod map support for autofs autofs-ldap - LDAP map support for autofs Closes: 887284 Changes: autofs (5.1.2-3) unstable; urgency=medium . * QA upload. . [ Laurent Bigonville ] * debian/control: Switch all the packages to Arch:linux-any . [ Andreas Henriksson ] * Add e2fsprogs to build-dep and recommends (Closes: #887284) * Drop incorrect depends on lsb-base * Drop incorrect *build*-dep on lsb-base Checksums-Sha1: 939bc69fb6701e70e2678af9d4aeb00a42e5b3b5 2145 autofs_5.1.2-3.dsc 86419b63f91e1cfb324342a0d0f1e3297117517e 16112 autofs_5.1.2-3.debian.tar.xz bb21156f8d71b5ef0c58f6b30f907fd59532ec37 9360 autofs_5.1.2-3_amd64.buildinfo Checksums-Sha256: 91ed24783b9709d591e36331d6ae166970175dcf537ef98e72d74d0dac0d1b6e 2145 autofs_5.1.2-3.dsc 27109ff272001952024e5c9f130468f053b496970554f14b4a9c6ef6e820bcde 16112 autofs_5.1.2-3.debian.tar.xz d36befde5857ec640e3f96f79f7d45226201969eb93c5b035803199af435d01f 9360 autofs_5.1.2-3_amd64.buildinfo Files: fad9619c7b8f9085b64743262319a59a 2145 utils optional autofs_5.1.2-3.dsc 61787f76e4450d47d863b7518f024cd6 16112 utils optional autofs_5.1.2-3.debian.tar.xz 9e234112fe57a18eb42ff3f142c175a3 9360 utils optional autofs_5.1.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlqInmYRHGFuZHJlYXNA ZmF0YWwuc2UACgkQC8R9xk0TUwZH7Q/+Mjmy5slXz3CMmb6qON9GujWUdzoaJ5Is xJJeEmu6w4ie1MCRviV6qWXaqrC9Hxboi0ETbSiwDM+/8NoBz4Wi3etET9MYdLpP 25s2zFDOMqGGoVcagzzDLPMEZYhldtn/eaTg7pjCcD+JGdV45/jPaVammXeR/SLL bUow16YcCw9MwkyLHBkRJnpMkJZN75KDHFbm/9f4P2H1p0AYTyLSm0q8Dfpf0zyx F30+E4RKNuvBqX1dUIzF0owc0hNDJHDJRGDprvvnzm6cYlC0SjEFrxMseKO6lrkr j+2tjooYhschq3QllRvIcrEqzRySMKDN2uLKq9JwgpKh4YjcC55aAuVTCXXExGIh 3gBniaXiwuzCCLQOjuTwPuvGfU5xJ7WzUYTw1uLYH+zcHwOPbjd+DV9yZVi2x6Va 217v9Laj3+T+7MH2+iWWowZoG5Fi00g0h5Oe43CZnE9cKJewqQmRPLsKLLcVE0O/ yPblYsGggPSQX+Gt3uMbQ/hDTa6mMx8iaTmM4yRzrsa2qHuPzlHVBd7FSI/q8KSB d+0CbygkhvOnriDqsceg7+UH9/DCanMKQx01mxb9GgtrRy0aINlu77zYzlyH6mfg Jmkh8JePin9eyYmvD9lsN06SR3yaqivUB4XeT8fVE7DIC/yQVGpwS/OMxlveEE3r 40ynCd05BiU= =HTpF -END PGP SIGNATURE-
Bug#887243: qa upload of gfxboot
Debdiff attached.
diff -Nru gfxboot-4.5.2-1.1/debian/changelog gfxboot-4.5.2-1.1/debian/changelog
--- gfxboot-4.5.2-1.1/debian/changelog 2014-07-25 20:58:48.0 +0200
+++ gfxboot-4.5.2-1.1/debian/changelog 2018-03-06 17:08:15.0 +0100
@@ -1,3 +1,14 @@
+gfxboot (4.5.2-1.1-6) unstable; urgency=medium
+
+ * QA Upload.
+ * Add e2fsprogs to Recommends, also add reiserfsprogs and xfsprogs to
+Suggests. (Closes: #887243)
+ * Add debian/watch pointing to https://github.com/OpenSUSE/gfxboot
+ * Do dbgsym migration and drop gfxboot-dbg package.
+ * Switch from deprecated Priority: extra to optional.
+
+ -- Andreas Henriksson Tue, 06 Mar 2018 17:08:15 +0100
+
gfxboot (4.5.2-1.1-5) unstable; urgency=low
* I don't care anymore, not worth it.. orphaning.
diff -Nru gfxboot-4.5.2-1.1/debian/control gfxboot-4.5.2-1.1/debian/control
--- gfxboot-4.5.2-1.1/debian/control2014-07-25 20:58:37.0 +0200
+++ gfxboot-4.5.2-1.1/debian/control2018-03-06 17:08:15.0 +0100
@@ -1,6 +1,6 @@
Source: gfxboot
Section: misc
-Priority: extra
+Priority: optional
Maintainer: Debian QA Group
Build-Depends:
debhelper (>= 9),
@@ -20,27 +20,14 @@
Depends:
${misc:Depends},
${shlibs:Depends},
-Suggests: gfxboot-themes
+Recommends: e2fsprogs
+Suggests: gfxboot-themes, reiserfsprogs, xfsprogs
Description: tool to test and create graphical boot logos (runtime)
gfxboot is a tool to test and create graphical boot logos for gfxboot
compliant
boot loaders. Currently, this includes grub, lilo, and syslinux (all
payloads).
.
This package contains the runtime utility.
-Package: gfxboot-dbg
-Section: debug
-Priority: extra
-Architecture: any-amd64 any-i386
-Depends:
- ${misc:Depends},
- gfxboot (= ${binary:Version}),
- gfxboot-dev (= ${binary:Version}),
-Description: tool to test and create graphical boot logos (debug)
- gfxboot is a tool to test and create graphical boot logos for gfxboot
compliant
- boot loaders. Currently, this includes grub, lilo, and syslinux (all
payloads).
- .
- This package contains the debugging symbols.
-
Package: gfxboot-dev
Architecture: any-amd64 any-i386
Depends:
diff -Nru gfxboot-4.5.2-1.1/debian/rules gfxboot-4.5.2-1.1/debian/rules
--- gfxboot-4.5.2-1.1/debian/rules 2014-06-24 16:43:33.0 +0200
+++ gfxboot-4.5.2-1.1/debian/rules 2018-03-06 17:08:15.0 +0100
@@ -93,4 +93,4 @@
dh_install --fail-missing
override_dh_strip:
- dh_strip --dbg-package=gfxboot-dbg
+ dh_strip --dbgsym-migration='gfxboot-dbg (<< 4.5.2-1.1-6~)'
diff -Nru gfxboot-4.5.2-1.1/debian/watch gfxboot-4.5.2-1.1/debian/watch
--- gfxboot-4.5.2-1.1/debian/watch 1970-01-01 01:00:00.0 +0100
+++ gfxboot-4.5.2-1.1/debian/watch 2018-03-06 17:08:15.0 +0100
@@ -0,0 +1,3 @@
+version=4
+opts=filenamemangle=s/.+\/v?(\d\S+)\.tar\.gz/gfxboot-$1\.tar\.gz/ \
+ https://github.com/OpenSUSE/gfxboot/tags .*/v?(\d\S+)\.tar\.gz
Accepted gfxboot 4.5.2-1.1-6 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Mar 2018 17:08:15 +0100 Source: gfxboot Binary: gfxboot gfxboot-dev gfxboot-themes Architecture: source Version: 4.5.2-1.1-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Henriksson Description: gfxboot- tool to test and create graphical boot logos (runtime) gfxboot-dev - tool to test and create graphical boot logos (development) gfxboot-themes - tool to test and create graphical boot logos (themes) Closes: 887243 Changes: gfxboot (4.5.2-1.1-6) unstable; urgency=medium . * QA Upload. * Add e2fsprogs to Recommends, also add reiserfsprogs and xfsprogs to Suggests. (Closes: #887243) * Add debian/watch pointing to https://github.com/OpenSUSE/gfxboot * Do dbgsym migration and drop gfxboot-dbg package. * Switch from deprecated Priority: extra to optional. Checksums-Sha1: e50515dc3e03a69819149e58fd8b4a786bb9e053 2122 gfxboot_4.5.2-1.1-6.dsc c450e012ea113c0885b4e913a076fd16789b1264 7404 gfxboot_4.5.2-1.1-6.debian.tar.xz be33d72b37f40c238bdfef7f3145b6693c3725f5 6817 gfxboot_4.5.2-1.1-6_amd64.buildinfo Checksums-Sha256: 7794c12f137b14b3ae286b8720c98607452166fa3734f0f81b7f4db550f515b5 2122 gfxboot_4.5.2-1.1-6.dsc 0cfdb5b749947f71502ac44cda1e7aaf66142e811ccfec3ca4c721adadb4e72b 7404 gfxboot_4.5.2-1.1-6.debian.tar.xz a05ceb365643ea7910b856827f55533bdf7ddd7efce4301bad134571278d6c5a 6817 gfxboot_4.5.2-1.1-6_amd64.buildinfo Files: 10692ed87056a113c37ab00b47e1b9c4 2122 misc optional gfxboot_4.5.2-1.1-6.dsc f61dd129361c088899c25821fe0a95ae 7404 misc optional gfxboot_4.5.2-1.1-6.debian.tar.xz ef6af4b077091ebed3ddcdea6b16da79 6817 misc optional gfxboot_4.5.2-1.1-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlqewBwRHGFuZHJlYXNA ZmF0YWwuc2UACgkQC8R9xk0TUwbg7A//TbCeXnJ2c77nzxu8NOyZcuec7tqQOwYO krSlNnjtcvaDOe4CDC62RjT5rKLF6h8Ef3EkzfftjfyyqJrA5PTsovNaHiyW38pD osfVj8CRD94FNgVzYmky/d6RUpNEt8XW/jDu9kbUjwQ1wHtdvD+CvBCkSUgfxuMg 2XrQem8JmhWbKvP2q/ju81hEtgE94LhO4MVsgo+OoxpHSRxR7Cs/N0pcAQK3rrN5 I/K72jT1vORn1esEfeP44lCas8JtYuapvwZqsFwMCQ2SMmwRmwI5RHQByi3IhUaM +7EYp+N856yRnJ3iz8h80di9yFxg59ud/awIOszln6/8IQHPSX150HFioM9ZamI6 3aMHnclu52L+4dPxkmJ+8J5rBLvinCyCWRLfCP57nMJDMlI6HEtu5pgoMN/4TNtc sAK3rJt3qbmWc7XqQvINiiYueePOryFOqfvq5D1E/IUScnMw1NogNohyimU+POBT D+plN7Tfa5VpbUikS65PEIubqUndfSbX1x8OyQmOXQAoBS2S6d3PiugqV7Hcph+1 vFHYaslyPCXTOyP9c2PFl5nq1n2KmQVDmkUPKiS07T5Z3fVtqBJrmRkQIGft5G6E BANFtjhdZngwZiwOsRseA3U80ikNecbPxWzq93lTDfQGm0sljBeouNf8Px373OSP igI0egOhdl0= =UFGo -END PGP SIGNATURE-
Bug#904049: cricket: Please consider using getent instead of sg in maintscript
Source: cricket Version: 1.0.5-21 Severity: wishlist User: andr...@fatal.se Usertags: sg-maintscript-removal Hello, Your package cricket was one of the few matches for 'sg' usage in maintainer scripts[1]. As a preparation for potentially solving #833256 in the future, I'd like to ask you to change your package to adhere to what seems to be the established defacto standard in maintainer-script code for adding users/groups these days, eg. if ! getent passwd | grep ^joeuser: > /dev/null; then adduser ... fi ... and similar for groups with 'getent group'. More examples can be found at https://codesearch.debian.net/search?q=path%3A.*postinst+adduser or for a specific example see: https://sources.debian.org/src/util-linux/2.32-0.1/debian/uuid-runtime.postinst/ Please note that adding (and removing) system users and groups are still not described in Debian Policy (see #228692), but this will eliminate the need for the 'sg' utility and be more in line with what other packages are doing. If your package are removing users or groups during purge, you might want to consider that there seems to be consensus against ever doing so (see mailing list thread linked from #228692). If time permits and I haven't heard anything back I'll consider fixing this via a NMU while at DebCamp/DebConf. Regards, Andreas Henriksson [1]: https://codesearch.debian.net/search?q=path%3Adebian%2F.*p%28ost%7Cre%29%28inst%7Crm%29+%5C+sg%5C+
Bug#926305: nis startup scripts are completely broken
Hello everyone, Greetings from the Gothenburg BSP. If someone is interested in modernizing the nis package it seems like ArchLinux has native systemd units for nis and related services so I'd suggest importing those: https://aur.archlinux.org/packages/nis-utils/ https://www.archlinux.org/packages/core/x86_64/rpcbind/ See also https://wiki.archlinux.org/index.php/NIS Regards, Andreas Henriksson
Bug#938884: python-zeitgeist (binary) removal blocked by gtk-doc
Control: block -1 by 939500 Hi, Once the two applications using python-zeitgeist stops doing that, disabling the use of python2 use in zeitgeist build is still not super trivial. The reason is that zeitgeist needs python(3)-rdflib to generate the onthologies and the configure.ac uses the AM_PATH_PYTHON macro that will find python2 before python3. As long as something pulls in python(2) into the build, it doesn't work to just use python3:any and python3-rdflib to build zeitgeist because of that. The package pulling in python(2) is gtk-doc, which has been fixed in experimental but is still pending upload to unstable. Set the relevant tracking bug as a blocker for this. In other words, as soon as all the blockers has been resolved it should hopefully be as easy to fix this bug report as: - drop the python-zeitgeist binary package (together with dh-python and other related machinery). - switch python-rdflib build-dep to python3-rdflib and python to python3:any. (Atleast I'm not aware of any futher problems right now.) Regards, Andreas Henriksson
Bug#936117: [PATCH] drop alliance python build-dep + dh-python usage
Control: tags -1 + patch Hello, It seems there's no runtime dependency on python and I can't find any mention of python anywhere outside the debian/ directory. Thus I think this is a lingering build-dependency that's no longer used. Attached patch has been build-tested. Regards, Andreas Henriksson diff -Nru alliance-5.1.1/debian/changelog alliance-5.1.1/debian/changelog --- alliance-5.1.1/debian/changelog 2018-04-20 10:04:52.0 +0200 +++ alliance-5.1.1/debian/changelog 2019-09-28 11:33:33.0 +0200 @@ -1,3 +1,10 @@ +alliance (5.1.1-4) unstable; urgency=medium + + * QA Upload. + * Drop (unused?!) (dh-)python build-dependency. (Closes: #936117) + + -- Andreas Henriksson Sat, 28 Sep 2019 11:33:33 +0200 + alliance (5.1.1-3) unstable; urgency=medium * Fix FTBFS with recent TeX Live by specifying the input encoding diff -Nru alliance-5.1.1/debian/control alliance-5.1.1/debian/control --- alliance-5.1.1/debian/control 2018-04-15 12:21:03.0 +0200 +++ alliance-5.1.1/debian/control 2019-09-28 11:26:32.0 +0200 @@ -18,7 +18,6 @@ libxt-dev, libxpm-dev, dpkg-dev (>= 1.16.1~), - python (>= 2.6.6-3~), transfig, graphicsmagick-imagemagick-compat Homepage: https://soc-extras.lip6.fr/en/alliance-abstract-en/ diff -Nru alliance-5.1.1/debian/rules alliance-5.1.1/debian/rules --- alliance-5.1.1/debian/rules 2016-01-14 00:22:10.0 +0100 +++ alliance-5.1.1/debian/rules 2019-09-28 11:26:40.0 +0200 @@ -8,7 +8,7 @@ include /usr/share/dpkg/buildflags.mk %: - dh $@ --with python2 + dh $@ override_dh_auto_configure: ./autostuff
Bug#969319: wifi cannot connect after combined suspend & gateway reboot
Hi all, On Tue, Sep 08, 2020 at 11:35:27PM +0200, Michael Biebl wrote: [...] > I'm bringing Andreas, the maintainer iwd into the loop here. [...] (Seems you forgot to CC me but I stumbled upon this, so giving my 5c) FYI I lost interest and orphaned iwd. I'm can't tell if this is an iwd or NM bug. My best recommendation is to try without NM, connecting via iwctl and see if the problem can be reproduced standalone to help finding that out. Please also contact iwd upstream directly, either via their mailing list or irc channel. Make sure to include iwmon traces and debug output for them to be able to properly analyze what's going on. In my own experience there are many issues lingering in the NM iwd backend before it can be expected to be production quality. A very good way of triggering NM iwd backend problems is by using a hidden SSID for unknown reason. Please note that NM actively refused to connect to a hidden SSID using the iwd backend until recently (and I only fixed up the very basic things so that it is not actively refused, there should be comments on the upstream issue/merge-request about several remaining problems that needs to be adressed still if you're interested). Please note: - iwd upstream actively discurages usage of hidden SSIDs simply because there's no upside and many downsides to using it. - NM upstream actively discurages using the iwd backend (likely because they are tired of noone contributing to fixing it up). For a data point you can compare against, I'm using NM with iwd backend myself against a hidden SSID quite often. I only quickly glanced over your description, but I don't feel like I can relate to your problem description. I can however say that I do have to apply different hacks to get things going more often then I'd want to. Usually doing (a) below solves hickups when NM doesn't get along anymore with iwd, but rarely I also need to do (b) when NM decides there are no usable interfaces available. a/ systemctl stop iwd ; systemctl restart NetworkManager ; poke the GNOME ui to "select [wifi] network" so that NM dbus activates iwd again. b/ systemctl stop iwd; systemctl stop NetworkManager; rmmod ; modprobe ; systemctl start NetworkManager ; ... Regards, Andreas Henriksson
Bug#796588: Bug796588#: adjtimex: Has init script in runlevel S but no matching service file
Hello Roger Shimizu. On Sat, Nov 28, 2015 at 11:12:38PM +0900, Roger Shimizu wrote: > Dear systemd maintainers, [...] I'm just a random bystander, but hope I can come up with a few useful suggestion. > Enclosed the "adjtimex.service" file I wrote and confirmed working > well on my box. > Since this is the first time I write service file, it would be helpful > if you can help to review it. Thanks for your interest in participating in resolving the rcS situation. > > I also have one doubt whether to have "RemainAfterExit=yes", which is > commented out now. > After setting the kernel time variables, adjtimex simply exits and > don't need to remain as daemon. I guess it should be okay to be "no". I'd suggest you remove the line entirely. (The default is RemainAfterExit=no.) You have no "stop" method, thus there's no point in using this directive to mark the service as still running so that it can later be "stopped". For more information: http://www.freedesktop.org/software/systemd/man/systemd.service.html#RemainAfterExit= > > Looking forward to your reply. Thank you! I also suggest you look into the possibility to not running the init script from the service file. Should be possible by making the following changes: Remove: ConditionFileIsExecutable=/etc/init.d/adjtimex Add: Environment="TICK=1 FREQ=0" EnvironmentFile=-/etc/default/adjtimex See: http://www.freedesktop.org/software/systemd/man/systemd.exec.html#Environment= EnvironmentFile= should "win" over default settings in Environment=, while the dash (-) prefix says it's ok if the file does not exist. Replace: ExecStart=/etc/init.d/adjtimex start with: ExecStart=/sbin/adjtimex -tick "$TICK" -frequency "$FREQ" In case these changes sounds useful to you, then please confirm the above to make sure my understanding of the situation is correct. Regards, Andreas Henriksson
Bug#796630: rdnssd: Has init script in runlevel S but no matching service file
Control: tags -1 + patch Hello Felipe Sateler! On Sat, Aug 22, 2015 at 10:42:00PM -0300, fsate...@debian.org wrote: [...] > Your package rdnssd has an initscript that is enabled in runlevel S, > but it does not provide a corresponding systemd service unit. [...] Since rdnssd is QA-maintained, I looked into if I could create a service file for it and ended up with the attached debdiff. If you have time to have a look at it that would be great! Regards, Andreas Henriksson diff -Nru ndisc6-1.0.1/debian/changelog ndisc6-1.0.1/debian/changelog --- ndisc6-1.0.1/debian/changelog 2015-09-14 14:00:02.0 +0200 +++ ndisc6-1.0.1/debian/changelog 2015-12-22 08:22:18.0 +0100 @@ -1,3 +1,11 @@ +ndisc6 (1.0.1-5) UNRELEASED; urgency=medium + + * QA upload. + * Add debian/rdnssd.service (Closes: #796630) + * Drop dead/obsolete XS-Vcs-Svn url from debian/control. + + -- Andreas Henriksson Tue, 22 Dec 2015 08:19:53 +0100 + ndisc6 (1.0.1-4) unstable; urgency=medium * QA upload. diff -Nru ndisc6-1.0.1/debian/control ndisc6-1.0.1/debian/control --- ndisc6-1.0.1/debian/control 2015-09-14 14:00:00.0 +0200 +++ ndisc6-1.0.1/debian/control 2015-12-22 08:19:52.0 +0100 @@ -5,7 +5,6 @@ Build-Depends: cdbs, debhelper (>= 7), autotools-dev, gettext Standards-Version: 3.9.1 Homepage: http://www.remlab.net/ndisc6/ -XS-Vcs-Svn: http://anonsvn.remlab.net/svn/pkg-remlab/ndisc6 Package: ndisc6 Architecture: any diff -Nru ndisc6-1.0.1/debian/rdnssd.service ndisc6-1.0.1/debian/rdnssd.service --- ndisc6-1.0.1/debian/rdnssd.service 1970-01-01 01:00:00.0 +0100 +++ ndisc6-1.0.1/debian/rdnssd.service 2015-12-22 08:18:50.0 +0100 @@ -0,0 +1,19 @@ +[Unit] +Description=IPv6 Recursive DNS Server discovery Daemon +Documentation=man:rdnssd(8) +Before=network.target +Requires=network.target + +[Service] +# Note: -u user (default:nobody) only applies to worker process, +#manager (executing merge-hook) still runs as root. +Environment=MERGE_HOOK=/bin/true "OPTIONS=-u rdnssd" +EnvironmentFile=-/etc/default/rdnssd +Type=forking +ExecStartPre=/bin/mkdir -p /var/run/rdnssd +ExecStartPre=/bin/chown rdnssd:nogroup /var/run/rdnssd +ExecStartPre=/bin/chmod 0755 /var/run/rdnssd +ExecStart=/sbin/rdnssd $OPTIONS -H $MERGE_HOOK + +[Install] +WantedBy=multi-user.target
