May 2006 - openSUSE Factory - openSUSE Mailing Lists

OOo, fonts, and PDF: bad character spacing (jn 10.0)
by Ulrich Windl 29 May '06

29 May '06

Hi, FYI: I've just created bug #179549 about bad character specing in PDFs created with OOo in SuSE Linux 10.0. I had just discovered that yesterday. I found a similar bug, but couldn't find out what the original reporter actually complained about, so I started a new one (where I hope the problem is very clear). I would assume that the problem is 70% the font quality, 20% the font rendering engine, and 10% likelihood OOo. Maybe the gurus can find out what the problem actually is. Regards, Ulrich

1 0

Why I hate package manager in 10.1 3 hours 30 minutes to check dependentcies.
by Boyd Lynn Gerber 28 May '06

28 May '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like to report why I object to 10.1 package manager. I just finished with the first CD (CD1). I tried to upgrade a production 10.0 server. I choose the upgrade option. It complained about not being able to reslove them and had to have manual intervention. It would bring up conflicts one at a time with 30 seconds to 3.5 minute wait between them. It took over 3 hours and 30 minutes just to review the conflicts. It then took an other hour after I tried to re-add back selections that were removed. Most of the time I had to click unlock and check again. This makes the upgrade totally not an option. I will stay with 10.0 on the other 30 systems I have control over. I do not have the time to try and do this for each and every system. The old package manager I could be done fixing the conflicts in 10-30 minutes depending on the system. This system was one I thought would be the easiest to upgrade. I thought I had better warn others. - -- Boyd Gerber <gerberb(a)zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFEZ4sHVtBjDid73eYRAprdAJ9p75DXfBXqcQQKOzbHbmSg/IVvpQCfbVYf Nrz1LSncaNKgTNWf/rVfSRQ= =3Rh9 -----END PGP SIGNATURE-----

6 12

Feedback for test-update
by Martin Schlander 27 May '06

27 May '06

I assume the point of releasing the updates for testing was to get feedback - so here goes.. I haven't done heavy testing - but I've had Zen updater running for a few days - added some repos with rug, zen and YaST etc. I must say that I don't feel much of a difference. Performance wise it still takes a lot of time to "parse metadata" and "update-status" on my amd64 3000+ with inst-source, non-oss, kde-update, guru, packman. And it often ends up using about 150-250 megs of swap - I have 1 gig of ram, and normally don't swap at all. But I guess no promises were made in this department. I was under the impression that the "unsigned repo warning"-issue would be fixed by these updates - but I still get those. But I definitely haven't noticed any new bugs or worsening in any area - so for all I can say the updates are ready to go. I Think some people will be dissapointed though - when they see the updates they're probably going to think all the issues will be fixed. Btw., to finish up on a positive note, I had a look at the changelog for the packages, using the new changelog-feature in YaST - I really love how YaST SW gives me huge amounts of information and control. Also gives insight to the huge amount of work that's being done on the packagemanagement stuff. Martin / cb400f

2 1

YOU filters
by jdd 26 May '06

26 May '06

the updating problems with 10.1 made me look better at this yast module and notice that it seems able to do all the software install. I didn't notice it before, but maybe this is an old feature :-() The present screen http://en.opensuse.org/Image:Yast-gui-you.jpg in the filter menu you have all what you have in the software module, + the patches entry does this mean the YOU (or the software install) menu is going do desapear? jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos

2 1

oprofile backtracing support [x86_64]
by Kay Tiong Khoo 26 May '06

26 May '06

Hello there, I have several questions with regard to oprofile backtracing support in the kernel and would appreciate responses from SUSE Developers. 1. Currently, CONFIG_DEBUG_INFO is not set on openSUSE and SLES9. Will it be set in future SUSE products? This is required for oprofile backtracing to work in user space. 2. Because CONFIG_FRAME_POINTER is not set on openSUSE and SLES9, samples in the kernel will not have backtraces. Is there any possibility that future releases of openSUSE and SLES will have CONFIG_FRAME_POINTER set? I am currently in the process of developing a front-end with a rewritten oprofile kernel module as the backend. Proper support for backtracing on SUSE products will help customers properly visualize the callstacks. Thanks Kay Tiong

2 2

updating yum repodata
by Greg Edwards 24 May '06

24 May '06

Is there a reason why the yum repodata (inst-source/suse/repodata) in factory only updates every few days to a week? It seems like this should be getting updated at least nightly as new packages are added and updated. Greg

3 3

regedit for linux?
by Frank-Michael Fischer 24 May '06

24 May '06

Maybe someone can help me out of some of my bad feelings I am having around putting config data into XML files. One of the striking advantages (and used in day-to-day work almost daily) of linux versus windows was the use of plain text files for basically anything concerning system or application configuration. Putting more and more config data into XML files makes me worry if we are not going the "registry way" where reading, interpreting and changing config data becomes more and more a programmers job. Not that I hate the idea to create more and more higher qualified jobs around linux and the creation of the LCE (Linux Certified Engineer) position for simple system administration tasks. It might just raise the hurdle to switch to linux if the thing gets as confusing in administration as windows. Yes, XML is a "open" standard, compared to Windows registry. But in real life tasks it does not matter. FMF

3 3

Update stack test build
by Graham Anderson 24 May '06

24 May '06

Morning folks, Would this list be the best place to post feedback regarding the test build of the update stack packages you posted yesterday Andreas? Or is it better moved to bugzilla...? If so I can move all this to bugzilla with logs etc. Here are my observations so far anyway. 1. The 10.1 release update stack successfully installed the test builds after I added the URL as a YUM service via zen-updater. However the whole upgrade took an extremely long time ( 15 minutes approx ). I was unable to determine why it was taking so long, i dont *think* it was the downloading... 2. Adding services via rug is just fine, and as per the 10.1 release builds ZYPP services are synced with YaST, YUM services are not. Adding services via zen-updater, same as rug, it works and the synching is the same. 2. Adding a larger service such as main online installation from mirror( inst-sources ) is much smoother. The service itself was added to the list in yast inst_sources almost instantaneously and unlilke the 10.1 release the catalog was not immediately downloaded but was only fetched when the finish button was pressed. At a rough guess I would say the whole process of adding the main installation source is 50% quicker now. 3. ZMD scheduling seems to be a bit broken now. It appears that the service refresh happens at the same time as the hourly maintenance, even though it is scheduled for the next day. Once the full service refresh and maintenance has run ( hourly by default it seems ) the schedule is reset with an updated time for the service refresh 24 hours later and 1 hour later for the maintenance. Of course the service refresh still happens one hour later and another new time i scheduled for it. This has the side effect of a full service refresh will run if my system is booted outside of the hourly maintenance window, parse-metadata and update-status hogging 100% CPU for a few minutes on boot. If i reboot my system inside the hourly maintenance window this does not happen.

4 4

zmd from the inside
by Druid 24 May '06

24 May '06

So we happen to get together some people today in irc, and since the package management is so popular theme these last days, we happen to get a talk about it with some of the developers. Since there has been so much complaining and talk, but so little information, we tried to get some information about it and set a wiki page, and added some of the discussed points. http://en.opensuse.org/Zmd There is also a log about the talk (http://susewiki.apanela.com/zen.log), with too much garbage on it, but Ill let it online if anyone cares to read it. Thanks for all of you who helped. You know who you are. The point was starting some information gathering, and hopefully it will keep growing. So feel Free to complete the page, put infos that are not there, etc. sds Marcio --- druid ### I will try to address the points that were explained: Lots of users were concerned about the current situation of having the zypp (yast) data and the zmd data (like /var/lib/zmd and /var/lib/zypp).This situation of having the metadata twice was said that its because zmd likes to have its own db. Other common point is that they can be very resource intensive and lots of suers are experiencing that. AJ rolled out some beta updates ( ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/) for people to test and heard some reports it solved some problems. Also it was said that Yast module is not a zmd frontend. Instead it uses libzypp directly to install packages. Libzypp provides the dependency solving functionality, and it supports traditional susetags and YUM/rpm-md metadata formats. Zmd has support for other sources too, like redcarpet ones, for example, but can also do YUM metada repositories. Zmd and rug also uses libzypp for dependency solving. Zmd uses an sqlite db */var/lib/zmd/zmd.db to store most of its pertinent data. The libzypp helpers are not written in C++ (and thats the reason its not integrated in libzypp, which is C++ code), but in a separated stage. Zmd interface also works with libredcarpet (as it used to do), so you cant simply go modifying that interface too. It was noted that some of the helpers (like parse-metadata and update-status, for example) seems to be the ones most hogging the system (but it would need to try to do some profiling, so we can stop the I-think-it-is and start the It-is-for-sure). It was also said that due to the close deadline of release, zypp wasnt yet optimized, so there is a big field for improvements in there. Note that from this description it is clear that we have some overlapping of solutions, specially about yum sources, that could be in the future be done using only one solution (which I think is what all people wants, the use of zmd, and a yast frontend to zmd as a common yast module, what currently is the sw_single/online_update module). For the people willing to help with debug, here is how to set debug information (beware of logfiles getting bigger in ./log/zmd-messages.log): $ rug set log-level debug ; $ rug set log-exception-traces true

1 0

Yast translation
by Dinar Valeev 23 May '06

23 May '06

Hi where i can find team that working on Yast translation to Russian language? thnx

2 3