On Sat, Oct 25, 2003 at 01:06:44AM -0700, Ian Truelsen wrote:
> Hopefully, someone out there knows a bit about ezmlm and can answer
> this, because it is driving me up the wall.
>
> I just installed ezmlm-idx to set up a small mailing list. I went to
> ezmlm.org and checked out the quick start th
On Sat, Oct 11, 2003 at 05:02:16PM -0700, Andrew Farmer wrote:
> On Fri, 10 Oct 2003 18:48:21 -0700, spiff.devotion muttered:
> > I've been having a problem with glibc not installing any locales for a
> > longer period of time now. It all started when glibc was upgraded from
&
I've been having a problem with glibc not installing any locales for a longer period
of time now. It all started when glibc was upgraded from 2.3.1-r4 to 2.3.2-r1. I've
tried emerging glibc a few times to no avail. Last time I emerged I noticed that
iconvconfig dies on execution (whatever relev
Thanks for the comments.
On Fri, Aug 15, 2003 at 04:07:01PM -0700, el lodger wrote:
>
> I'm curious if your portage is compiled against the old or newer glibc.
> lodger
It was compiled against the old glibc. I issued an emerge portage to compile it with
the new glibc, but it didn't change anyth
Hi,
I'm still having problems with emerge wanting to downgrade glibc from 2.3.2-r1 to
2.3.1-r4. It doesn't matter if I do emerge -u system or emerge -U system, it still
tries to downgrade before doing something else:
embryo portage # emerge -up system
These are the packages that I would mer
On Tue, Aug 05, 2003 at 02:22:48PM +0100, Frederic Soulier wrote:
> On Tue, 2003-08-05 at 14:14, Ming-Che Lee wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi!
> >
> > On Tuesday, 5. August 2003 12:05 spiff.devotion wrote:
> >
Some additional information; I decided to try to do an emerge -U system rather than
emerge -u system, being under the impression that emerge wouldn't downgrade my glibc
to 2.3.1 again. Well, it tried to do that anyway.
It feels like my emerge is broken.
If anyone can explain to me what's happ
After having resolved the problem when emerge downgraded my glibc from 2.3.2-r1
2.3.1-r4, i did an emerge -u system which upgraded my glibc to 2.3.2-r1 again. Emerge
continued to update packages, but choked on selinux-small-2003040709-r3. I then did an
emerge -up system to see what packages wer
When doing an emerge -up system yesterday, I noticed that emerge wanted to downgrade
my glibc from 2.3.2-r1 to 2.3.1-r4. I didn't understand why it wanted to do that, so
to update some other packages that needed updating I performed
'emerge groff hdparm linux-headers psmisc automake patch libto
