Bug 296332 - Build 603: Getting error: "Failed to initialize the repository" during NFS installion
Summary: Build 603: Getting error: "Failed to initialize the repository" during NFS in...
Status: RESOLVED INVALID
: 296349 296392 (view as bug list)
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Installation (show other bugs)
Version: Alpha 7
Hardware: x86-64 Other
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Michael Andres
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-01 08:00 UTC by Holger Sickenberg
Modified: 2007-08-09 16:32 UTC (History)
6 users (show)

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

Attachments
y2logs.tar.bz2 (42.01 KB, application/x-bzip2)
2007-08-01 08:01 UTC, Holger Sickenberg 		Details
logs.tar.gz (26.02 KB, application/x-gzip)
2007-08-09 15:54 UTC, Christoph Thiel 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Sickenberg 2007-08-01 08:00:52 UTC 
When installing DVD Build 603 on x86_64 I do get following error message:

    Failed to initialize the repository. Try again?
Comment 1 Holger Sickenberg 2007-08-01 08:01:23 UTC 
Created attachment 154666 [details]
y2logs.tar.bz2
Comment 2 Stephan Kulow 2007-08-01 08:04:48 UTC 
this happens also on the CD build of x86_64, but is x86_64 specific
Comment 3 Stanislav Visnovsky 2007-08-01 08:08:02 UTC 
2007-08-01 03:49:22 <1> 10.10.4.37(3757) [zypp] TagParser.cc(parse):201 Start parsing /var/cache/zypp/raw/20070801-034907/suse/setup/descr/rest_cd-32bit-10.3-92.x86_64.pat[g___]
2007-08-01 03:49:22 <5> 10.10.4.37(3757) [zypp] Exception.cc(log):119 CapabilityImpl.cc(buildFilesystem):254 THROW:    CapabilityImpl.cc(buildFilesystem):254: Unsupported kind of Filesystem Capability'filesystem(minix)-32bit'
2007-08-01 03:49:22 <5> 10.10.4.37(3757) [zypp] Exception.cc(log):119 CapabilityImpl.cc(parse):312 RETHROW:  CapabilityImpl.cc(buildFilesystem):254: Unsupported kind of Filesystem Capability'filesystem(minix)-32bit'
Comment 4 Stephan Kulow 2007-08-01 08:11:56 UTC 
I'm not sure yet what creates the 32bit patterns, but it obviously doesn't care for comments:

Original:
// filesystem(minix)
util-linux

Version on DVD:
//-32bit
filesystem(minix)-32bit
util-linux-32bit
Comment 5 Stanislav Visnovsky 2007-08-01 08:13:21 UTC 
Anyway, a better error report would be more that welcome.
Comment 6 Stephan Kulow 2007-08-01 08:50:55 UTC 
ok, I fixed the shell script that generates the 32bit patterns to take comments into account.

I leave the bug open as Stano suggests - especially as we'll allow custom patterns in build service projects soonish
Comment 7 Stanislav Visnovsky 2007-08-01 11:36:52 UTC 
*** Bug 296392 has been marked as a duplicate of this bug. ***
Comment 8 Claes Backstrom 2007-08-02 10:26:08 UTC 
*** Bug 296349 has been marked as a duplicate of this bug. ***
Comment 9 Nikolay Derkach 2007-08-02 12:36:48 UTC 
so, fixed?
Comment 10 Michael Andres 2007-08-02 14:49:43 UTC 
AFAIK fixed, but Stano wants to keep the bug open until the error reports are
improved too.
Comment 11 Felix Miata 2007-08-06 22:07:50 UTC 
Same problem on http install from ftp-1.gwdg.de and mirrors.kernel.org, both of which seem to have had sync late yesterday.
Comment 12 Felix Miata 2007-08-06 22:15:32 UTC 
Forgot to mention on tty3 that 404 error occurred on inst-source//part.info and on inst-source/driverupdate/file_0001, which I don't see on mirror. The behavior was slightly different on the two mirrors. On mirrors.kernel.org there was an extra window that opened stating "download failed: media exception". I tried 3rd time on carroll.cac.psu.edu and got behavior matching gwdg.
Comment 13 Felix Miata 2007-08-06 23:03:54 UTC 
Also forgot to mention using i586.
Comment 14 Andreas Jaeger 2007-08-09 15:36:38 UTC 
This looks to me like a different problem.  Can you provide some more details - after checking that it still fails with current factory?
Comment 15 Christoph Thiel 2007-08-09 15:51:04 UTC 
I'v reproduced the problem locally -- attaching logs shortly.
Comment 16 Christoph Thiel 2007-08-09 15:54:22 UTC 
Created attachment 156547 [details]
logs.tar.gz
Comment 17 Stanislav Visnovsky 2007-08-09 15:58:17 UTC 
Broken repo, pattern with a wrong revision.
Comment 18 Stephan Kulow 2007-08-09 16:32:16 UTC 
great, now we got hijackers of that bug to make "better error reporting" INVALID - and reopening is pointless as it has 17 comments now and only one with a meaning ;(