Bug 150669 - "Unable to create installation source" error due to missing yast2-packagemanager rpm
Summary: "Unable to create installation source" error due to missing yast2-packagemana...
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: PC SuSE Linux 10.1
: P5 - None : Minor with 5 votes (vote)
Target Milestone: ---
Assignee: Andreas Jaeger
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-14 05:31 UTC by D, D,
Modified: 2006-02-15 14:44 UTC (History)
0 users

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

Attachments
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 D, D, 2006-02-14 05:31:09 UTC 
http://ftp.ale.org/pub/mirrors/opensuse/opensuse/distribution/SL-OSS-factory/inst-source/suse/i586/
(rpm tree for OpenSuse 10.1 beta3 as of Feb 13, 2006)

is missing the yast2-packagemanager*.rpm file.

Because of this, 
- Yast's "Installation Source" module is empty and produces only "Unable to create installation source" messages.
- installation_sources -a is not available
- No further updates are possible.

Temporary workaround:
Use KPackage by adding the source to RPM sources in "Settings" > "Configure KPackage"
Comment 1 Michael Gross 2006-02-14 12:16:33 UTC 
Sorry, but it happens that certain servers are not completly synchronized or just take longer to do so. As these are external servers, you should always contact their respective owners/admins.
Comment 2 D, D, 2006-02-14 21:17:34 UTC 
(In reply to comment #1)
> Sorry, but it happens that certain servers are not completly synchronized or
> just take longer to do so. As these are external servers, you should always
> contact their respective owners/admins.

ALL of the mirrors I checked have this problem with OpenSuse 10.1 "Factory" tree for more than a 3 days! I checked ALL of the US mirrors. There are TWO yast2-packagemanager-devel rpms (diff version) and NONE of yast2-packagemanager.

The problem is UPSTREAM somewhere. It happened sometime around Feb 10, 06.

Please, check for yourself.
Comment 3 Michael Gross 2006-02-15 14:35:40 UTC 
Is probably related to the profound changes in that module.
Andreas?
Comment 4 Andreas Jaeger 2006-02-15 14:44:35 UTC 
This is a fallout of the libzypp integration that I announced, installation
source is currently broken. :-(

This is on the todo list of the developers, so let's close this one.