public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Justin Whitney <ripple.gentoo@ripple.be>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] wget 1.8.2 breaks resumed emerges when using sandboxing
Date: 13 Apr 2003 01:32:11 -0400	[thread overview]
Message-ID: <1050211931.15530.22.camel@osiris.ripple.be> (raw)

There's bug (feature?) in wget 1.8.2 where any wget from an ftp source
that resumes to an existing file (-c flag) gets chmod'd to 0600.  If
you're using "userpriv usersandbox" (in portage's FEATURES flag) this
means that any time you ctrl-c an emerge during a download from an ftp
mirror, then emerge again, the resumed file will no loger have o+r
priv's, and therefore emerge will give you an "access denied".  The fix
is simple: chmod o+r the file, and emerge a third time.  Alternatively,
one could change the default download commands in make.conf to use curl
or something else.

Here's an excerpt from the guilty wget source file:

ftp.c-      /* #### Is this correct? */
ftp.c://      chmod (con->target, 0600);

Seems like the answer is no, this is not correct.  It is worth noting
that, as I said above, this applies to only resumed files... which is
curious behaviour.  I've emailed the wget-bug list, but no one has
responded - so maybe the wget maintainers want to take a look at this,
and patch it.  Or maybe portage should make sure o+r is set when
userpriv/usersandbox is being used.

--Justin


--
gentoo-dev@gentoo.org mailing list


                 reply	other threads:[~2003-04-13  5:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1050211931.15530.22.camel@osiris.ripple.be \
    --to=ripple.gentoo@ripple.be \
    --cc=gentoo-dev@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