- openSUSE Factory

Add-On icon kicked out
by Azerion 06 Apr '06

06 Apr '06

Seems that the 'Add-On Product' incons has been kicked out in last factory-package. It was just fixed, and now it is broken again? Can someone confirm or reject this bug (before I reopen it in Bugzilla) >> newer yast2 (2.13.41-3 / 2.13.42-2) yast2-core (2.13.19-3 / 2.13.20-2) yast2-theme-SuSELinux (2.13.5-2 / 2.13.5-2) Azerion

1 0

update configuration
by Peter Czanik 05 Apr '06

05 Apr '06

Hello, Is it supposed to work with current factory? I downloaded it this morning. When I got to "Update Configuration", I left it on the default "Configure now (Recommended)" and pushed "Next". For the past 20 minutes I have seen just the hour glass mouse pointer. All elements on screen are clickable, so I could change to "Configure Later", click "abort" "back", etc., but YaST does not respond to anything. Is it worth a bug report, or "Update Configuration" is still under heavy construction? Bye, CzP

4 4

Where can I dump Translation 'bug'-reports?
by Azerion 05 Apr '06

05 Apr '06

I found some Dutch-translation problemsin Setup that may exist in other languages too. Where do I post the report? "Include Add-On (Media?)" is not translated "Traditional method without NetWorkManager" is not translated The Online-update-page is nog translated ===================================== Dutch only: - Welcom bij SUSE Linux >> Welkom - Bezoek opensuse.org over hoe u >> Bezoek opensuse.org -en lees- over hoe u - OpenOffice bevat oa......een database (is dat zo, ik denk dat dat database-beheer moet zijn) Azerion

3 6

Beta9 Minimal Install
by Chad Groneman 04 Apr '06

04 Apr '06

Hi, >From AJ's announcement: > The distribution comes with 5 CDs. You need: > * CD1 only for a minimal text installation (English) > * CDs 1-3 for a default KDE or GNOME installation in German or English > * All CDs for other selections I just did an i386 minimal text install, it took approx 450 MB from CD1, but also required about 3 packages from CD2. Should I file a bug report? Thanks, Chad

5 9

Beta 9: Automatic entries in Installation Source?!
by David Wright 04 Apr '06

04 Apr '06

Just added gwdg.de factory to YaST and went back in to see if the ordering bug has been fixed (it hasn't), and I found that YaST had automatically added a new entry to the list for me that wasn't there on my first viewing of the form! It had automatically added http://ftp.lug.ro/suse/suse/update/10.1/ Is this expected behaviour? (This was a new install and the first operation I did after logging on was to go into YaST and add gwdg.de...) Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck

3 5

makeSUSEdvd broken for beta9
by Azerion 04 Apr '06

04 Apr '06

Seems like makeSUSEdvd is broken in combination with beta9. The md5sums of the iso's are okey. When I wanted to install it reported that it could not found the packages. So I makeSUSEdvd-ed again and tried with y2pmsh. That one reports this: source -a /setup/beta9repo failed to detect sources on file:/setup/beta9repo ERROR(InstSrc:E_cache_dir_create) Azerion

5 32

Update Configuration step fails - sometimes
by David Wright 04 Apr '06

04 Apr '06

I've installed Beta 9 around 8 times now - tracking down various problems. The Update Configuration page sometimes comes up with a failed message with the text "Transaction already in progress. No product to register."... Also the user authentication page only gives me local or ldap now, is this an error or a change in specification? Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck

1 1

beta9 - installation hiccups
by Per Jessen 04 Apr '06

04 Apr '06

I'm just now installing beta9 on a test-machine - and I'm seeing some unusual behaviour. I don't really have much info/diagnostics, which is why I thought I'd ask here before going to bugzilla. The installation is now on CD2, and I've seen 6-7 popups saying "unable to install <package> blahblah ... file or directory not found". All I had to do was say "Retry", and it worked just fine. Also, a couple of times, maybe three, I've seen the installation complain that CDx has suddenly become unavailable - to which I have just said OK, and everything worked fine again. I'm doing a network install, booted off CD1. Has anyone seen anything similar? /Per Jessen, Zürich

2 1

SUSE-Linux10.1-Beta9-Extra problems
by Michael DePaulo 04 Apr '06

04 Apr '06

Hey all, First of all, it looks like the non-OSS software repository for opensuse beta9 isn't setup right. ftp://ftp.suse.com/pub/suse/install/10.1/SUSE-Linux10.1-Beta9-Extra/ I get this message when I hit finish after adding it as a source (with opensuse 10.1 beta9 x86_64): Curl error for: ftp://ftp.suse.com/pub/suse/install/10.1/SUSE-Linux10.1-Beta9-Extra/content. key: Error code: File not found Error message: RETR response: 550 You can still hit skip and use this install source fine. Upon looking at beta9 and previous sources, it looks like the beta9 sources are supposed to have the file content.key containing a PGP key, unlike previous versions, and this key is missing from this repository. This is only an inconvenience for us beta testers, since even if you dont know about using skip, you can download the RPMs themselves. Nevertheless, this should be fixed in the final version for the sake of casual users. Also, nano has been added since beta8. This is GPL and is already included on the media (10.1 x86-64 at least), and thus probably doesn't belong there. I would have posted this to bugzilla, but I figure these are problems with the suse.com repository that can be fixed relatively easily, not a problem with opensuse itself. -Mike

5 6

commit ML & Factory/Beta
by Graham Anderson 03 Apr '06

03 Apr '06

Evening folks, Do packages that appear on the commit ML make their way into the factory master repo at commit time or is there a further stage? If this is the case I presume then it's preferable ( from you dev's point of view ) for people using beta(9) to update beta packages from the beta release to the updated factory ones? cheers the noo, Graham

3 4