public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] ebuild execute permissions: problem with cvs
Date: Tue Jul 17 14:53:02 2001	[thread overview]
Message-ID: <20010717145220.B2641@cvs.gentoo.org> (raw)
In-Reply-To: <01071723392805.00582@localhost>; from danarmak@gentoo.org on Tue, Jul 17, 2001 at 11:39:28PM +0300

On Tue, Jul 17, 2001 at 11:39:28PM +0300, Dan Armak wrote:
> Hi all,
> 
> There's a problem (at least on my machine) with some ebuilds. They have some 
> or all execute permissions set. Examples are skel.build, all but one of the 
> sys-kernel/linux/linux-* ebuilds, and about 50 others. 
> 
> I tried disabling execute permissions on skel.build. cvs wouldn't recognize 
> it as a new revision, so I also removed a dot from the end of a sentence in 
> the file. When I commited and re-updated, it was executable again.
> 
> I don't know what's going on, but I think someone with cvs root access should 
> handle this.

OK, I did some things to the CVS repository and now all ebuilds should *not*
be executable.  I didn't want to do it to all files because I'm sure we have
some executable scripts lying around somewhere and I don't want to mess them
up.  This problem may have been caused by a permissions mishap caused my me
a couple of months ago.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			



  reply	other threads:[~2001-07-17 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 14:40 [gentoo-dev] ebuild execute permissions: problem with cvs Dan Armak
2001-07-17 14:53 ` Daniel Robbins [this message]
2001-07-17 15:42   ` Dan Armak
2001-07-17 16:19     ` Daniel Robbins
2001-07-17 14:57 ` Jerry A!

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=20010717145220.B2641@cvs.gentoo.org \
    --to=drobbins@gentoo.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