From: Ben Beuchler <insyte@emt-p.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] rc-update and /etc/rc.d/config/functions
Date: Mon Sep 3 21:28:01 2001 [thread overview]
Message-ID: <20010903222707.C3501@emt-p.org> (raw)
In-Reply-To: <20010903205648.H20781@cvs.gentoo.org>
On Mon, Sep 03, 2001 at 08:56:48PM -0600, Daniel Robbins wrote:
> On Mon, Sep 03, 2001 at 09:51:38PM -0500, Ben Beuchler wrote:
>
> > I'm definitely using 1.0_rc6. I don't recall saying differently, but perhaps
> > we miscommunicated. /etc/make.profile is symlinked to
> > /usr/portage/profiles/insyte-1.0_rc6
>
> OK; I may have thought you were someone else :) Do an emerge rsync, and merge
> openssh-2.9_p2-r2, and you shouldn't have problems except having rc-update not
> being able to run. This is normal.
I did an emerge rsync earlier today prior to mergeing openssh-2.9_p2-r2, right
after you updated it. But I just did another one for good measure. Anyway, I
thought you had told me earlier to do openssh-2.0_p2 (without the r2) but that
may have been my spongy brain cells. So I did an emerge on openssh-2.9_p2-r2,
which gave me this:
================
mazer openssh # emerge openssh-2.9_p2-r2.ebuild
Calculating dependencies.
!!! Portage had a problem processing this file:
!!! /usr/portage/net-misc/openssh/openssh-2.9_p2-r2.ebuild
/usr/sbin/ebuild.sh: /usr/portage/net-misc/openssh/openssh-2.9_p2-r2.ebuild:
line 57: syntax error near unexpected token `}'
/usr/sbin/ebuild.sh: /usr/portage/net-misc/openssh/openssh-2.9_p2-r2.ebuild:
line 57: `}'
!!! aborting.
!!! emerge aborting.
================
Just for the hell of it, I also did an emerge on 'openssh-2.0_p2', which
failed the same way it did earlier, which gave me this:
================
>>> original instance of package unmerged safely.
>>> /usr/sbin/ebuild.sh: /etc/rc.d/config/functions: No such file or directory
>>> /usr/sbin/ebuild.sh: einfo: command not found
>>> /usr/sbin/ebuild.sh: //usr/sbin/rc-update: No such file or directory
>>> !!! pkg_postinst() script failed; exiting.
>>>
================
And, of course, the init scripts don't actually work as
/etc/rc.d/config/functions doesn't exist. Nor does /usr/sbin/rc-update, but I
guess that doesn't matter. Right?
What is the current status with init scripts? I understand they're in
considerable flux these days. For example, which location is correct for the
'functions' file? /etc/rc.d/config/functions or /etc/init.d/functions.sh?
Thanks,
Ben
--
Ben Beuchler There is no spoon.
insyte@emt-p.org -- The Matrix
next prev parent reply other threads:[~2001-09-04 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 19:00 [gentoo-dev] rc-update and /etc/rc.d/config/functions Ben Beuchler
2001-09-03 20:49 ` Daniel Robbins
2001-09-03 20:52 ` Ben Beuchler
2001-09-03 20:57 ` Daniel Robbins
2001-09-03 21:28 ` Ben Beuchler [this message]
2001-09-03 22:53 ` Daniel Robbins
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=20010903222707.C3501@emt-p.org \
--to=insyte@emt-p.org \
--cc=gentoo-dev@cvs.gentoo.org \
/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