Copied to hardy-updates.
** Changed in: procps (Ubuntu Hardy)
Status: Fix Committed => Fix Released
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Tags added: verification-done
** Tags removed: verification-needed
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Well, I suspect I may be the only person "testing" this, but I can
verify that it does the right thing on both upgrades and a clean
install.
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
B
procps (1:3.2.7-8ubuntu2) intrepid; urgency=low
* Remove rcS.d/S17procps.sh on upgrade, eliminating Ubuntu cruft.
-- Adam Conrad < [EMAIL PROTECTED]> Mon, 30 Jun 2008 15:46:16 -0600
** Changed in: procps (Ubuntu)
Status: Triaged => Fix Released
** Changed in: procps (Ubuntu Hardy)
This is the patch that was uploaded to hardy-proposed
** Attachment added: "ungh"
http://launchpadlibrarian.net/15923100/ungh
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
Bugs, which
Fixed in intrepid in version 3.2.7-8ubuntu2, and uploaded to hardy-
proposed as version 3.2.7-5ubuntu3
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
For the record, while the impact of this bug is cosmetic at best, based
on the number of subscribers, I suspect I'm not alone in finding rc?.d/*
cruft a bit alarming and untidy in a dist-upgrade, hence the nomination
for hardy.
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.
Here's a debdiff for hardy. I'm uploading the same change to intrepid
in a few minutes.
** Attachment added: "procps-hardy.debdiff"
http://launchpadlibrarian.net/15720375/procps-hardy.debdiff
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received t
For the record, this happens on ALL upgrades, and is a result of us
having moved the procps.sh start link from S30 (debian's default) to
S17. The postinst attempts to remove S30procps.sh (as well as
S05procps.sh, for historical reasons) on upgrade, which fails for
Ubuntu:
# Remove old pro
** Changed in: procps (Ubuntu)
Importance: Undecided => Low
Status: Confirmed => Triaged
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: procps (Ubuntu)
** Tags added: gusty2hardy
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
As I said, I am not sure at what point this issue occurred. I've been
running hardy (32-bit) for some time now. I only happened to notice the
broken symlink by running a find over /etc. It doesn't actually cause
any problems, since broken symlinks in /etc/rc*.d are just ignored.
I'm a bit confu
Also could you please attach the files in /var/log/dist-upgrade to this
bug report?
Thanks!
--
/etc/rcS.d/S17procps.sh left after upgrade
https://bugs.launchpad.net/bugs/228406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Thank you for reporting this issue, in order to triage this bug I need
more information.
1) What version of gusty were you upgrading from? 32 bit or 64 bit?
2) What kind of hardware do you have?
3) How would I go about re-creating this bug? Is it just a straight upgrade
from gusty?
Thanks in a
15 matches
Mail list logo
