Your message dated Fri, 22 Sep 2017 17:50:09 +0000
with message-id <e1dvs5z-000hgx...@fasolo.debian.org>
and subject line Bug#876208: Removed package(s) from unstable
has caused the Debian Bug report #689584,
regarding Please remove sleep patch which does not work and does not resolve
any problem
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 ow...@bugs.debian.org
immediately.)
--
689584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aiccu
Severity: normal
Creating a new bug as 531003 is archived and thus can't comment there
any more unfortunately.
Related links:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531003
https://bugs.launchpad.net/bugs/1058883
-------- Original Message --------
Subject: Please remove sleep patch which does not work and does not
resolve any problem
Date: Thu, 04 Oct 2012 00:52:26 +0200
From: Jeroen Massar <jer...@unfix.org>
To: 531...@bugs.debian.org, 1058...@bugs.launchpad.net
[Caleb: thanks for finding the origin of this "fix"]
So it seems this sleep "fix", by just restarting (I thought Debian was
not an ancient Microsoft product where one just reboots all the time),
which was not tested is now causing issues for people:
https://bugs.launchpad.net/bugs/1058883
Would it not be prudent to revert such a patch, or better, never have
applied it if the patch was not tested or proven working at all?!?
It seems there are no logs or other details included about this issue,
just a "it does not work" and "I restart it now it works" and then a
patch for just restarting it.
Would be great if there actually where logs for this issue or other
details that would demonstrate the problem.
Maybe time to remove this patch?
As I have stated in various places: AICCU does not need to be restarted,
the protocols used should handle it, that is why those protocols, exist.
If the tunnel 'breaks', please provide details of what is broken so that
the real problem can be addressed.... just restarting it does not
resolve such a problem.
Bigger note:
If anybody has logs which demonstrate breakage please provide them,
then I can take those situations along in the testing of the new AICCU.
I've added to the to-check list to check with Virtualbox how a
acpisleepbutton event affects the state of AICCU, thus lets see what
the result of such a test is (best I can do, no Linux on a laptop
anywhere near me at the moment... but this should be similar)
Greets,
Jeroen
--- End Message ---
--- Begin Message ---
Version: 20070115-17+rm
Dear submitter,
as the package aiccu has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/876208
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
