From: Teresa and Dale <teendale@vista-express.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge mod_security: ERROR 404: Not Found.
Date: Sat, 24 Jun 2006 13:31:25 -0500 [thread overview]
Message-ID: <449D84FD.3090502@vista-express.com> (raw)
In-Reply-To: <200606242022.04469.bo.andresen@zlin.dk>
Bo Ørsted Andresen wrote:
>On Saturday 24 June 2006 18:51, Jarry wrote:
>
>
>>Anyway, I am still surprised a little. I thought sources
>>of portage-packages are mirrored on gentoo-mirrors...
>>
>>
>
>They are. If the package has just been added to the tree they may not have
>reached your mirror yet. If that is not the reason then it is probably a bug.
>The official mirror should be in the ebuild to tell the mirrors where to
>fetch it from and as a backup if it cannot be found on the Gentoo mirrors.
>
>
>
>>It seems to me to be a little "insecure", to download
>>mod_security from somewhere "from wild" instead of
>>gentoo-mirrors or homepage. One can not be sure those
>>sources have not been modified...
>>
>>
>
>As long as you don't override a digest verification error you are safe. Beware
>of those who tell you to override a digest verification error by running:
>
># ebuild $ebuild digest
>
>or:
>
># emerge --digest $pkg
>
>
>
Very true. I have seen people on this list tell people just that.
Dale
:-) :-)
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-06-24 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 16:38 [gentoo-user] emerge mod_security: ERROR 404: Not Found Jarry
2006-06-23 17:40 ` Teresa and Dale
2006-06-23 17:56 ` Jarry
2006-06-23 18:21 ` Teresa and Dale
2006-06-23 19:07 ` Jarry
2006-06-23 19:46 ` Daniel da Veiga
2006-06-23 19:47 ` Teresa and Dale
2006-06-24 11:50 ` Teresa and Dale
2006-06-24 16:51 ` Jarry
2006-06-24 18:11 ` Teresa and Dale
2006-06-24 18:22 ` Bo Ørsted Andresen
2006-06-24 18:31 ` Teresa and Dale [this message]
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=449D84FD.3090502@vista-express.com \
--to=teendale@vista-express.com \
--cc=gentoo-user@lists.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