Hi! Strange, my upgrade from 10.2 to Beta3 worked successfully (I used only the Beta3 instlalation repository). Probably because of no disk renames, since I have a SATA system.
Also, I have not noticed any memory problem (same amount of memory as you, 64-bit system). May be caused by excluding Factory repository. I think you can file bugreports for all of these issues unless someone gives an update on them. I don't think we can track them on the mailing list... Jiri Dne Monday 27 of August 2007 01:44:03 Christian Boltz napsal(a): > Hello, > > I just updated my 10.2 to 10.3 beta2 and, well, it was a bit > adventurous ;-) and I'm asking myself if someone has tried to install > beta2 as update - there are too many obvious bugs, and some of them are > critical from my POV :-( > > Installation source: Factory tree + non-OSS tree, mirrored yesterday > > Just a short overview about the problems I had as short overview: > > - my 10.2 partition is only offered for update if I select "show all > partitions" (and: no, I don't think that > https://bugzilla.novell.com/show_bug.cgi?id=299667 is invalid - the > solution would be to ask for the password of the encrypted partition > earlier) > - /etc/cryptotab is not converted to /dev/sd*, so mounting encrypted > partitions while installation fails > - /etc/fstab is also not converted, so mounting everything except / > fails > - /boot/grub/device.map also wasn't modified, resulting in a failure > at bootloader installation > - installing the kernel also failed because mkinitrd was still trying to > use hda - workaround: change fstab manually These three sound like a one bug in detecting the disk mapping. I doubt we managed to break it on that many places, since it worked in the past. > - the tab order in the dialog to add an add-on repository is broken > - the pattern "update test packages" does not drop in any of the > "update-test-*" packages > - I had the latest KDE packages from Buildservice on 10.2, and the beta2 > installation had to downgrade them. This resulted in lots of > conflicts, YaST even marked the beta2 KDE packages with "arch change" > and did not honor what I chose in the conflict dialog. > I had to go to the packages mask and mark the KDE packages to be > refreshed. > - strange version difference: I'm still using agrep from SUSE 8.2, which > is version 4.0 (newer releases didn't contain it) and now re-appeared > with version 0.7. > - on the first run, the installation aborted unexpectedly, probably > because the y2logs and a testcase needed too much RAM. > Sidenote: I have 1GB RAM... > Next run without testcase generation worked, but still created ~300 MB > y2logs. > Question: does "manual" mode create bigger logs does this always > happen? (reason for manual mode: linuxrc forces me to manual > installation mode because it doesn't find my HTTP installation source > in the first run - already filed a bug about this) No, it should not. However, IIRC logs from previous (failed) installations are concatenated unless you reboot. > Anyways, expected result is a warning "out of RAM, please cleanup the > logs or add swap." > - oh, just after clicking "accept" in the pattern details view, I got > about 200 MB additional y2log in 10 seconds... > - dependency check is quite slow when you have many conflicts (but fast > after you have solved them) > - for OpenOffice, thesaurus packages are installed for lots of languages > I never use. I'd expect to only have packages for my system language > by default. > - Some packages unselected in pattern details (the OpenOffice thesaurus > packages) were re-selected after clicking "packages" in the proposal - > which means YaST does changes after a user has done a per-package > selection in the pattern details view > - what about gtk-qt-engine? It conflicts with kcm_gtk... > - java_1_4_2_sun_jdbc also caused a conflict, maybe it should be > obsoleted by a current (1.5.0) package > - YaST didn't display the slide show, dunno why > - installation of several non-OSS packages failed with error > message "Inconsistency detected by ld.so: dl-open.c: 623: _dl_open: > Assertion `_dl_debug_initialize [...]" > %post failed with exit status 127 > affected: nspluginwrapper, acroread, flash-player, RealPlayer > - according to the y2log, the downloaded release notes have version > 10.2.3 which is obviously older than 10.3.5 in Factory > - SuSEconfig.zzzopt_gnome-compat code looks ugly code, it should have > more than one FIXME ;-) > - opensuse-updater is not obsoleted by opensuse-updater-kde, so I have > installed both of them now > > > And some things I already found in the running system: > - something seems to run "insserv -r boot.crypto" while installation, so > my encrypted partition wasn't mounted at boot > (workaround: insserv it again) > > - opensuse-updater (the old one, still running after the update) lists > also *packages* to update, not only patches (intended?) > - opensuse-updater (again the old one) has a grey, empty area at the > bottom - where's the patch description? > > - the new opensuse-updater-kde initially shows only an overview. I'm not > yet sure if I really like this (for me it's a click more to see the > available updates) - so please add an "always show details" checkbox. > > - YOU doesn't display information about packages, just lists the patches > (empty list at the right section of the window) > > > I would be happy if someone could add a short note to every item if it > is already known or if I need to file a bugreport ;-) > > > Regards, > > Christian Boltz > > PS: I'll now going to verify if all YaST modules support the help > parameter (bugs 269886 to 269914) to get a better feeling... -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: [EMAIL PROTECTED] Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
signature.asc
Description: This is a digitally signed message part.
