Bugzilla – Bug 151323
cannot add installation source (inst-source from factory)
Last modified: 2006-02-17 21:01:03 UTC
When trying to add the installation source inst-source from factory on a local directory /mnt/factory/inst-source I get: "There is no product information availlable at the given location..." y2log says: 2006-02-15 22:46:19 <1> sighup(6633) [wfm] clients/inst_source.ycp:103 Pkg Builtin called: SourceScan 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaAccess.cc(open):81 Trying scheme 'dir' 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaDIR.cc(MediaDIR):47 MediaDIR::MediaDIR(dir:/mnt/factory/inst-source) 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaAccess.cc(open):110 Opened: dir(dir:/mnt/factory/inst-source not attached; localRoot "/mnt/factory/inst-source") 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaManager.cc(open):219 Opened new media access using id 1 to dir:/mnt/factory/inst-source 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaHandler.cc(attach):313 Attached: dir:/mnt/factory/inst-source attached; localRoot "/mnt/factory/inst-source" 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaManager.cc(checkDesired):106 checkDesired(): desired (report) 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaHandler.cc(provideFile):425 provideFile(./media.1/products) 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaHandler.cc(release):372 Request to release attached media dir</mnt/factory/inst-source>, not unique 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaHandler.cc(release):389 Releasing shared media reference only 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaHandler.cc(release):393 Released: dir:/mnt/factory/inst-source not attached; localRoot "/mnt/factory/inst-source" 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaAccess.cc(open):81 Trying scheme 'dir' 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaDIR.cc(MediaDIR):47 MediaDIR::MediaDIR(dir:/mnt/factory/inst-source) 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaAccess.cc(open):110 Opened: dir(dir:/mnt/factory/inst-source not attached; localRoot "/mnt/factory/inst-source") 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaManager.cc(open):219 Opened new media access using id 2 to dir:/mnt/factory/inst-source 2006-02-15 22:46:19 <1> sighup(6633) [media] MediaHandler.cc(attach):313 Attached: dir:/mnt/factory/inst-source attached; localRoot "/mnt/factory/inst-source" 2006-02-15 22:46:19 <1> sighup(6633) [DEFINE_LOGGROUP] SourceFactory.cc(createFrom):122 Trying the YUM source 2006-02-15 22:46:19 <1> sighup(6633) [yum] YUMSourceImpl.cc(factoryInit):59 Adding no media verifier 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaManager.cc(checkDesired):106 checkDesired(): desired (report) 2006-02-15 22:46:19 <5> sighup(6633) [DEFINE_LOGGROUP] Exception.cc(log):83 MediaHandler.cc(getFile):636 THROW: MediaHandler.cc(getFile):636: File /repodata/repomd.xml not found on media: dir:/mnt/factory/inst-source 2006-02-15 22:46:19 <5> sighup(6633) [DEFINE_LOGGROUP] Exception.cc(log):83 2006-02-15 22:46:19 <0> sighup(6633) [DEFINE_LOGGROUP] SourceImpl.cc(provideFile):130 ProvideFile exception caught, callback answer: 0 2006-02-15 22:46:19 <5> sighup(6633) [DEFINE_LOGGROUP] Exception.cc(log):83 SourceImpl.cc(provideFile):134 RETHROW: MediaHandler.cc(getFile):636: File /repodata/repomd.xml not found on media: dir:/mnt/factory/inst-source 2006-02-15 22:46:19 <5> sighup(6633) [DEFINE_LOGGROUP] Exception.cc(log):83 2006-02-15 22:46:19 <3> sighup(6633) [yum] YUMSourceImpl.cc(factoryInit):98 Cannot read repomd file, cannot initialize source 2006-02-15 22:46:19 <5> sighup(6633) [DEFINE_LOGGROUP] Exception.cc(log):83 YUMSourceImpl.cc(factoryInit):99 THROW: YUMSourceImpl.cc(factoryInit):99: Cannot read repomd file, cannot initialize source 2006-02-15 22:46:19 <5> sighup(6633) [DEFINE_LOGGROUP] Exception.cc(log):83 SourceImpl.cc(factoryCtor):70 RETHROW: YUMSourceImpl.cc(factoryInit):99: Cannot read repomd file, cannot initialize source 2006-02-15 22:46:19 <5> sighup(6633) [DEFINE_LOGGROUP] Exception.cc(log):83 SourceFactory.cc(createFrom):132 CAUGHT: SourceImpl.cc(factoryCtor):70: Cannot read repomd file, cannot initialize source 2006-02-15 22:46:19 <1> sighup(6633) [DEFINE_LOGGROUP] SourceFactory.cc(createFrom):133 Not YUM source, trying next type 2006-02-15 22:46:19 <1> sighup(6633) [DEFINE_LOGGROUP] SourceFactory.cc(createFrom):137 Trying the SUSE tags source 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaManager.cc(checkDesired):108 checkDesired(): desired (cached) 2006-02-15 22:46:19 <0> sighup(6633) [media] MediaHandler.cc(provideFile):425 provideFile(./media.1/media) 2006-02-15 22:46:19 <1> sighup(6633) [susetags] SuseTagsImpl.cc(factoryInit):100 Adding susetags media verifier: 2006-02-15 22:46:19 <1> sighup(6633) [susetags] SuseTagsImpl.cc(factoryInit):101 Vendor: SUSE LINUX Products GmbH 2006-02-15 22:46:19 <1> sighup(6633) [susetags] SuseTagsImpl.cc(factoryInit):102 Media ID: 20060215172944 2006-02-15 22:46:19 <1> sighup(6633) [DEFINE_LOGGROUP] SourceFactory.cc(createFrom):140 Found the SUSE tags source 2006-02-15 22:46:19 <1> sighup(6633) [wfm] Source.cc(SourceScan):644 Added source 0: dir:/mnt/factory/inst-source 2006-02-15 22:46:19 <1> sighup(6633) [wfm] Source.cc(SourceScan):670 Found sources: [0] 2006-02-15 22:46:19 <1> sighup(6633) [wfm] clients/inst_source.ycp:130 Pkg Builtin called: SourceGeneralData
I hope it's fixed now, we put a fix for this in yesterday.
Ah, ok. Will sync now again to the latest set of packages and report again when I have installed them.
Ok, I have now updated all packages whose name start with 'y' and libzypp to the latest version. Result: - I can add now installation sources but the name is still "unknown". - When adding a directory that contains no installation source it still crashes. - When trying to update from the set up installation source, YaST still complains that the product in the installation source is incompatible with the installed system. - On update YaST tries to install the x86_64 packages on a 32 bit system. Anything else I should test here?
source management -> Stano ;-)
Robert, please, file a bug for each problem and mark their priority properly. This monster all-in-one bug is not possible to track. Thanks!
Sorry, I thought that these results might be directly related to this problem and thus did not open separate reports. I did so now as bug #151942, bug #151945, bug #151950, and bug #151954 thus closing this bug as fixed.