Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 21160
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Brad Cowan (RETIRED) <bcowan@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: John Burwell <jburwell@nni.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 21160 depends on: Show dependency tree
Bug 21160 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-05-17 10:48 0000
The sys-apps/xfsprogs ebuild will fail if autoconf has been installed.  It 
seems that the sys-apps/xfsprogs should have a dependency on autoconf to ensure 
its presence when merging -- causing it to be installed if it is not present.  

As an additional note, this behavior causes a failure when following the 
current installation instructions and using XFS as nothing in the preceeding 
steps causes autoconf to be installed.  Therefore, a user following the 
installation instructions will encounter an error in the happy path which seems 
to be a Bad Thing(tm).

There is an obvious workaround -- emerge sys-devel/autoconf before emerging sys-
apps/xfsprogs.

------- Comment #1 From Brad Cowan (RETIRED) 2003-05-18 23:44:50 0000 -------
autoconf should be installed already after an emerge system. its a standard
tool that's in all our profiles. I can add it as a dep but most all ebuilds
rely on it so I don't usually add it. also if you were following the install
guide emergeing FS utilities is  one of the last things listed to do....well
after emerge system where autoconf gets installed

------- Comment #2 From John Burwell 2003-05-19 11:45:26 0000 -------
In response to he comment, I had executed an emerge system and then emerged the
FS tools -- following the instructions to the letter.  It seems to me that an
ebuild should not rely on the fact the emerge system brought anything into the
system.  If a package depends on a package, it seems to me that it should call
it explictly.  What is emerge system removed a package from what is considered
the "system"?  EBuilds would break.  Granted, autoconf is one of the most build
tools, and I was frankly shocked it didn't come in as part of emerge system ...
 In order for me to consider the bug verified, it seems that one of two things
should happen:

   a) Determine if/why emerge system does always merge autoconf
   b) Add autconf as a dependency to the xfsprogs package

I can also say that after executing the installation instructions, they are
woefully broken.  A number of critical packages are not merged (i.e. mount, ps,
loadkeys, setfonts, ifconfig) that cause the boots following installation to
fail.  There is a thread devoted to this subject in the "Installing Gentoo"
forum.

------- Comment #3 From Brad Cowan (RETIRED) 2003-05-20 23:12:10 0000 -------
do an emerge -ep system ....autoconf should be there

------- Comment #4 From Brad Cowan (RETIRED) 2003-06-03 01:59:35 0000 -------
added dep to latest build

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug