-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Mark,
I was under the impression that packages with the ~amd64 (or ~x86) keywords are
in testing, but no serious instabilities had been found, or they would be hard
masked.
I have had non-testing packages break my system before, as well.
On Sunday 02 March 2008, Dan Farrell wrote:
Can anyone tell me what packages you know of that will break
your system if you choose to put ACCEPT_KEYWORDS=~amd64 in your
make.conf file? I have had my system break, twice now, from a
package upgrade - I think that one of the culprits
On Sat, 01 Mar 2008 14:09:45 -0500, Chris Walters wrote:
Can anyone tell me what packages you know of that will break your
system if you choose to put ACCEPT_KEYWORDS=~amd64 in your make.conf
file? I have had my system break, twice now, from a package upgrade -
I think that one of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Neil Bothwick wrote:
| On Sat, 01 Mar 2008 14:09:45 -0500, Chris Walters wrote:
| I run two completely ~amd64 systems here and have very few problems.
I've run testing on Gentoo and other distributions. With Gentoo, for over a
year, with few
On Sun, 02 Mar 2008 12:03:44 -0500
Chris Walters [EMAIL PROTECTED] wrote:
I find these paragraphs to be rude and insulting. I am not an idiot
- I know exactly what testing means, and what unstable means.
Just because I ask a relatively simple question in this group does
not mean that I am
Alan McKinnon wrote:
On Sunday 02 March 2008, Dan Farrell wrote:
doesn't sound like a broken package to me. perhaps something else
got borked?
Or maybe some unusual compiler settings?
OP, please post your /etc/make.conf
I don't think it is the compiler settings - they are fairly standard
On Sunday 02 March 2008, Chris Walters wrote:
Alan McKinnon wrote:
On Sunday 02 March 2008, Dan Farrell wrote:
doesn't sound like a broken package to me. perhaps something else
got borked?
Or maybe some unusual compiler settings?
OP, please post your /etc/make.conf
I don't think
On Sun, 02 Mar 2008 12:03:44 -0500, Chris Walters wrote:
I find these paragraphs to be rude and insulting. I am not an idiot -
I know exactly what testing means, and what unstable means.
Sorry if you feel that way, but many people confuse the various meanings
of unstable and stable in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alan McKinnon wrote:
| On Sunday 02 March 2008, Chris Walters wrote:
| Alan McKinnon wrote:
| I don't -O3 can ever be considered standard. Also you say you don't
| think that's it, then admit -O3 changes the code substantially. I'm
| having
On Sun, 02 Mar 2008 14:20:08 -0500, Chris Walters wrote:
Well, apparently either the latest ~amd64 keyword masked version of
coreutils does not install /bin/mktemp, or makes changes so
that /sbin/depscan.sh cannot find it, because /bin/mktemp missing is
a part of the error message, I receive.
On Sunday 02 March 2008, Chris Walters wrote:
Alan McKinnon wrote:
snip
| What you wrote doesn't make sense. depscan.sh is installed by
| baselayout and mktemp is installed by coreutils. You have
| depscan.sh Which package is blocking which? You don't have to guess
| which one, portage will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
Can anyone tell me what packages you know of that will break your system if you
choose to put ACCEPT_KEYWORDS=~amd64 in your make.conf file? I have had my
system break, twice now, from a package upgrade - I think that one of the
culprits
On Sat, Mar 1, 2008 at 11:09 AM, Chris Walters [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
Can anyone tell me what packages you know of that will break your system if
you
choose to put ACCEPT_KEYWORDS=~amd64 in your make.conf file? I have had my
On Sat, 1 Mar 2008 12:16:36 -0800
Mark Knecht [EMAIL PROTECTED] wrote:
On Sat, Mar 1, 2008 at 11:09 AM, Chris Walters [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
Can anyone tell me what packages you know of that will break your
system if you
Steve [Gentoo] wrote:
What's wrong?
If you are using the default config that comes with apache, there should
be a file in /etc/apache2/modules.d/ that contains a correctly setup SSL
host. You may need to add -D SSL to APACHE2_OPTS in /etc/conf.d/apache2
to enable it. You shouldn't need to
This time a bamboozling Apache/vhost/https problem.
I have a working vhost configuration for several domains in apache2
(latest stable from portage - 2.0.58) and I want to support not only
http services, but, for one domain name at least, I want to support an
https service. The working
Hi,
On Tue, 03 Oct 2006 15:06:33 +0100
Steve [Gentoo] [EMAIL PROTECTED] wrote:
I have a working vhost configuration for several domains in apache2
(latest stable from portage - 2.0.58) and I want to support not only
http services, but, for one domain name at least, I want to support an
https
Hi, sorry,
On Tue, 3 Oct 2006 16:48:50 +0200
Hans-Werner Hilse [EMAIL PROTECTED] wrote:
So basically that means you can only have one SSL server per IP.
should have been per IP:Port combination.
-hwh
--
gentoo-user@gentoo.org mailing list
On Tue, 3 Oct 2006 19:25:17 +0200
Hi, sorry,
On Tue, 3 Oct 2006 16:48:50 +0200
Hans-Werner Hilse [EMAIL PROTECTED] wrote:
So basically that means you can only have one SSL server per IP.
should have been per IP:Port combination.
-hwh
As Mr. Hans-Werner Hilse already explained,
19 matches
Mail list logo
