Your message dated Wed, 26 Apr 2017 10:55:50 +0100 with message-id <[email protected]> and subject line Re: Bug#796203: don't ask user again years later has caused the Debian Bug report #796203, regarding Should provide a native .service file and integration with systemd to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 796203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796203 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: nodm Version: 0.11-1.3 Severity: important Hi, nodm provides a special kind of display manager. I therefor think, it should use the same mechanism as other display managers like gdm3 or lightdm, to make sure that only ever one display manager is started during boot. For proper integration with systemd, nodm will have to provide a native .service file and make sure, a symlink /etc/systemd/system/display-manager.service is created in postinst which points at the nodm service, if it is chosen as default. Please have a look at other packages like lightdm or gdm3 on how to do that. If further help is needed, please don't hesitate to ask. Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---Version: 0.13-1 On Wed, 25 Jan 2017 at 04:33:06 +0800, 積丹尼 Dan Jacobson wrote: > I've used nodm for years. > Suddenly it is asking me if it should start by default again. That is not Bug#796203. Please do not reopen fixed bugs to report something that was not the topic of the reopened bug. When you do, it breaks the version tracking that developers rely on. If you have encountered a different issue, report it as a different bug, with the necessary information to be able to fix it (steps to reproduce bug, expected result, actual result, versions of relevant packages). Even if you suspect that the issue you encountered is a regression caused by fixing Bug#796203, that does not justify reopening Bug#796203. The only reason to reopen Bug#796203 "Should provide a native .service file and integration with systemd" would have been if nodm 0.13-1 did not contain a native .service file or integration with systemd. S
--- End Message ---
