From: Kevin <spamite@ev1.net>
Subject: Runit-run and socklog-run upgrades on Debian sid, be careful!
Date: Wed, 22 Mar 2006 09:23:50 -0600 [thread overview]
Message-ID: <200603220923.57498.spamite@ev1.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
I discovered this morning when upgrading my sid box, that runit-run and
socklog-run both failed in interesting ways.
Runit-run replaces the getty links in /var/service with new ones
in /etc/sv. If you're running the upgrade from a getty, the getty will
die when its service dir link is removed to be replaced, leaving
non-functional services. I was able to get in via ssh and fix the links
so that the getty's worked, and also tested not-fixing them and letting
dpkg --configure -a finish the job. Both worked.
The next problem is less of a show-stopper, but still needs to be paid
attention to. Socklog-run upgrade similar replaces the
old /etc/socklog-? links with /etc/sv/socklog-?. but it doesn't remove
the old symlinks in /var/service first, and so ln fails because the
target already exists. Removing the old links allows the postinst
portion of the deb installation to finish.
I'm not sure there are good ways to get around this on an upgrade of these
packages, so I'm uncertain if I should try to file a bug report. Any
thoughts?
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next reply other threads:[~2006-03-22 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 15:23 Kevin [this message]
2006-03-22 19:38 ` Matthew R. Dempsky
2006-03-23 6:34 ` Joshua N Pritikin
2006-04-01 8:31 ` Gerrit Pape
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200603220923.57498.spamite@ev1.net \
--to=spamite@ev1.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).