[gentoo-user] portage bugs?

[gentoo-user] portage bugs?

[Erwin Lang]

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

hi!

During installation of a new system I recognised two things:

1)  `emerge -e system' aborted two times.

    * The first time the command autoconf was missing so I manually installed the package autoconf.
    * The second time the command aclocal was missing so I manually installed the package automake (which contains aclocal)

I tried `emerge -ep system' an the two packages (autoconf and automake) are mentioned in the list of packages which portage will install. But it seems that portage installs them to late.


2) after `emerge -e system' I tried to install the following packages:
  `emerge -va reiserfsprogs lvm2 syslog-ng vixie-cron postfix'

vixie-cron needs an mta and tries to install ssmtp - which conflicts with postfix. portage didn't recognised that I mentioned an mta on command line.

I worked around by mentioning postfix before vixie-cron on command line:
  `emerge -va reiserfsprogs lvm2 syslo-ng postfix vixie-cron'

Then portage recognised postfix and didn't try to install another mta.

Shouldn't portage be smart enough to solve this by itself?

greetings
erwin

[-- Attachment #2: Type: text/html, Size: 1408 bytes --]

RE: [gentoo-user] portage bugs?

[Bob Young]

[-- Attachment #1: Type: text/plain, Size: 2427 bytes --]

FWIW, while bringinging up a new dual AMD64 box last night, I got the exact
same abort on autoconf during an emerge system. I solved it the same way, by
manualy emerging autoconf and restarting the emerge with the -newuse flag. I
didn't run into the aclocal problem, instead the emerge of samba caused a
second abort for me. That appeared to be a genuine compile error, so I
removed the samba use flag and continued the emerge system which completed
without further error.

On a side note, bringing this box up has been very frustrating. By default
the kernel on the install CD enables both CPUs, I spent a week starting and
restarting the install from various points. The problem was that the
compiles would just stop in the middle of compiling some random package. No
error message, no indicated system malfunction of any kind, the compiler
just stopped doing anything. It appeared to be just the compiler that was
hung, as a ctrl-c would return me to the command prompt. Forcing "nosmp" and
"noapic" on the boot command line of the install CD resolved that hang.
Unfortunately that was after trying a *lot* of other things and command line
options.

Regards,
Bob Young


-----Original Message-----
From: Erwin Lang [mailto:lang.erwin@gmx.at]
Sent: Thursday, October 06, 2005 6:16 AM
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] portage bugs?

hi!
During installation of a new system I recognised two things:
1) `emerge -e system' aborted two times.
* The first time the command autoconf was missing so I manually installed
the package autoconf.
* The second time the command aclocal was missing so I manually installed
the package automake (which contains aclocal)
I tried `emerge -ep system' an the two packages (autoconf and automake) are
mentioned in the list of packages which portage will install. But it seems
that portage installs them to late.
2) after `emerge -e system' I tried to install the following packages:
`emerge -va reiserfsprogs lvm2 syslog-ng vixie-cron postfix'
vixie-cron needs an mta and tries to install ssmtp - which conflicts with
postfix. portage didn't recognised that I mentioned an mta on command line.
I worked around by mentioning postfix before vixie-cron on command line:
`emerge -va reiserfsprogs lvm2 syslo-ng postfix vixie-cron'
Then portage recognised postfix and didn't try to install another mta.
Shouldn't portage be smart enough to solve this by itself?
greetings
erwin

[-- Attachment #2: Type: text/html, Size: 12342 bytes --]