Your message dated Sun, 3 Mar 2019 20:35:55 +0100 with message-id <7b603213-96c5-8056-b6d3-7b2c7a62a7f6@debian.org> and subject line close release-notes bugs for releases before stretch has caused the Debian Bug report #803356, regarding release-notes: cryptdisks conflicts with documentation, and is cryptic to use [jessie] 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 owner@bugs.debian.org immediately.) -- 803356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803356 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: cryptdisks conflicts with documentation, and is cryptic to use
- From: Ian Kelling <ian@iankelling.org>
- Date: Thu, 29 Oct 2015 00:05:48 -0700
- Message-id: <1446102348.3782774.423321305.0CC10A11@webmail.messagingengine.com>
Package: systemd Version: 215-17+deb8u2 https://www.debian.org/releases/stable/amd64/install.txt.en says "you will have to mount them manually after the boot" ... "/etc/init.d/cryptdisks start" In reality, this exits with success but does nothing. Looking through the code, I find that the init.d does exit 0 and nothing else if parent pid != 1, unless the command is "reload." It should actually do something, and it should not report success when doing nothing, and if you are somehow blind to that truth, the documentation should not claim otherwise. I'm curious how this got added. It just feels like such a basic debian thing to do: update a config file, and run stop or start or restart on an init.d file that ran during startup. It's even written the installation guide. I'm imagining some sadistic maintainer thinking "I'll make it so if they rerun this command after startup, it will succeed and do NOTHING. *evil laughter*." A second bug: Before I figured that out, I heard we use systemd now, so I run systemctl, see some related services, named after specific disks or partitions if I remember right, but starting/restarting them doesn't do anything, and nothing else I could identify relating to /etc/crypttab that would be equivalent to the init.d/cryptdisks. Are we using systemctl or /etc/init.d? Apparently some things with one, some things with the other. which for what? I have no idea.
--- End Message ---
--- Begin Message ---
- To: 706610-done@bugs.debian.org, 762026-done@bugs.debian.org, 783232-done@bugs.debian.org, 783235-done@bugs.debian.org, 803356-done@bugs.debian.org, 683698-done@bugs.debian.org, 699754-done@bugs.debian.org, 706217-done@bugs.debian.org, 769388-done@bugs.debian.org, 774563-done@bugs.debian.org, 706131-done@bugs.debian.org, 617982-done@bugs.debian.org, 708135-done@bugs.debian.org, 610194-done@bugs.debian.org, 713914-done@bugs.debian.org, 770533-done@bugs.debian.org
- Subject: close release-notes bugs for releases before stretch
- From: Paul Gevers <elbrus@debian.org>
- Date: Sun, 3 Mar 2019 20:35:55 +0100
- Message-id: <7b603213-96c5-8056-b6d3-7b2c7a62a7f6@debian.org>
Hi, We are sorry that we were not able to handle your contribution or suggestion for changes to the release-notes. I am going over old bugs and I am closing all the items that were suggested for the release-notes of Debian releases before stretch. On the good side, some even appear to have been applied, without the bug being closed. Please don't hesitate to open a new bug if you think your suggestion is still valuable for the release-notes of buster. If you do that, we'd appreciate it when you try to summarize the issue properly when the closed bug was more than a couple of messages. PaulAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---