Bug 275587 - file system utilities (xfs) is not be installed even if it was used in installation
Summary: file system utilities (xfs) is not be installed even if it was used in insta...
Status: RESOLVED DUPLICATE of bug 271912
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Alpha 4
Hardware: i686 openSUSE 10.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stefan Schubert
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-17 14:44 UTC by Yasuhiko Kamata
Modified: 2007-05-24 08:36 UTC (History)
3 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
yast logs (464.37 KB, application/x-gzip)
2007-05-21 13:38 UTC, Matej Horvath
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yasuhiko Kamata 2007-05-17 14:44:19 UTC
To reproduce:

1. start YaST2 installation.
2. format the root partition with XFS.
3. mkinitrd fails "cp: cannot stat '/sbin/fsck.xfs': no such file or directory." after software installation.

surely xfsprogs was not installed during YaST2 installation.

Was xfsprogs removed from standard install selection?
Comment 1 Matej Horvath 2007-05-21 13:37:45 UTC
I was able to reproduce it.
Comment 2 Matej Horvath 2007-05-21 13:38:14 UTC
Created attachment 141264 [details]
yast logs
Comment 3 Matej Horvath 2007-05-21 14:26:16 UTC
Confirmed, xfsprogs package isn't installed and therefore /sbin/fsck.xfs doesn't exist, although xfs filesystem has been selected. I'm going to reassign it to Lukas as the Yast Installation maintainer.
Comment 4 Lukas Ocilka 2007-05-21 14:36:23 UTC
I saw such wanted feature in FATE but now I can't find it. But I guess it should be done in solver.

If it is fixed as bug: aschnell@novell.com,fehr@novell.com
or enhancement: schubi@novell.com
for ZYPP evaluation: kkaempf@novell.com
Comment 5 Stefan Schubert 2007-05-24 08:36:37 UTC

*** This bug has been marked as a duplicate of bug 271912 ***