August 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] 12.1 is around the corner, and I must make my concerns known.
by Roger Luedecke 20 Aug '11

20 Aug '11

To the Green Blooded, The excitement is building as yet another release of our beloved openSUSE is just around the corner. This coming release looks as though it may be yet more exciting than 11.4 was; 11.4 being the distro I run only and place my clients on as well. Last release was a bit rough around the edges at launch, and had issues that shook confidence of new users. Though it brought enormous improvements in speed and stability, I must still worry about the first experience. As you most likely will recall, there were several discrepancies and throwbacks to previous versions that sullied 11.4 upon release. Primarily ones I noticed were the oddity of the DVD using the old Knetwork Manager as opposed to the current plasmoid version that was present in the KDE Live CD version. There was also the matter of the pre 11 series behavior of AppArmor in blocking Samba; this I found was more pronounced in the DVD install. (To this day I can't get Samba to work properly in a DVD install.) Since I am not a developer, and have only a brief familiarity with many of the logistical issues facing a project of this magnitude I will not offer an immediate critique. However as an Ambassador I must emphasize that these sort of anomalies, no matter how technically minor will shake the confidence of someone trying the new release. The things that we may consider minor, a new user will consider to be clues to the overall experience and what to expect; this is especially true for new users coming from Windows. Thus we lose a potential asset to the community in favor of some other distro (usually Ubuntu, Mint, Fedora, or Mandriva). Frankly, I would rather we be a bit late on releasing 12.1 than to release it as finished with the same sort of issues 11.4 showed. 11.4 was a grand milestone, creating enormous buzz with its massive improvements. 11.4 launched openSUSE to a new height of interest and popularity, and with that in consideration we must be careful to not put off the new users. Further, openSUSE has long been known as the flagship for KDE and as such many people will be looking to us for an alternative to the much disliked Gnome3 and Unity. Sincerely, Roger openSUSE Ambassador P.S. In this section I wanted to raise some questions, critiques, and a small wishlist. As this is less important by far I have placed it where it is. The odd discrepancies in the DVD vs LiveCD version leads me to wonder where there was some sort of disconnect between teams. I further wonder why there was not a central unified repository for the two versions, as I imagine that would have helped remove discrepancies. Why did this occur and how can it be prevented? Though I know its late in the game to make a lot of changes to the final product, this is my personal wishlist of things to see in future openSUSE (Gnome team disregard KDE specific things): 1. Have a simple default configuration for Samba, like in Ubuntu where it simply works out of the box. a. Fix AppArmor so it isn't battling with Samba constantly. 2. AppArmor desktop notifier. It would be nice for the user to know when AppArmor blocks something, and be able to click straight through to the Profile Update wizard. But even somethin as simple as a system announcement would be superior and be picked up by the KDE notification system. 3. Maintain more current versions of some neglected packages, especially WINE. Rekonq being the other package I would have liked to see updated. 4. Amarok is known as one of the most feature rich players in all of Linux. However, it often suffers from bugs that crash it constantly, or degrade its performance. Also its interface suffers from not using common conventions, and thus confounds new users. I recommend replacing it with Clementine as it is more stable and has a friendlier interface, and is yet KDE native. 5: There has been some talk about replacing the YaST Printer module with a KDE one in userspace. Frankly I think this is a terrible idea as YaST is the only tool on any platform that has actually made configuration of the god-forsaken yet popular HP AllInOne devices simple. Thank you for your time and consideration. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

22 89

[opensuse-factory] Study on the configuration of the Linux kernel
by Arnaud Hubaux 19 Aug '11

19 Aug '11

Dear openSUSE users, we are a team of researchers from the GSD Lab of the University of Waterloo (ON, Canada). We do research on configuration methods and algorithms and are conducting a study on the problems faced by users during the configuration of the Linux kernel. We would greatly appreciate it if you could answer this questionnaire: https://docs.google.com/spreadsheet/viewform?formkey=dHJrQ1B6OXVCRTRmbGJ2Zl… It should not take you more than 15 minutes to complete. Thank you very much for your contribution. Arnaud Hubaux, University of Namur/University of Waterloo Yingfei Xiong, University of Waterloo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 5

[opensuse-factory] python-gobject 2.90.x hit Factory
by Dimstar / Dominique Leuenberger 19 Aug '11

19 Aug '11

Hi all, We submitted an update of python-gobject to Factory. The new version, 2.90.2 is now based PURELY on the gobject-introspection based bindings and is not compatible to code relying on the old bindings. This link explains it better than I could ever write it: http://www.j5live.com/2011/08/14/announce-pygobject-2-90-1-released-3-0-pre… As this is of course a big change for Factory and the time to a final release is getting shorter, we do not expact everybody to change their codes (just yet). So we also submitted the 'old' version to Factory as python-gobject2 (the new version will become 3.0 when it's fully ready). python-gobject2 is not yet available in Factory (as of now), but that is likely to change in the not to distant future (SR pending). A big amount of packages might have turned into 'Unresolvable' after this change, as they were (still) BuildRequiring python-gobject2-devel (which in turn was a virtual symbol provided) or they are BuildRequiring pkgconfig(pygobject-2.0). For those packages, the virtue is patiance: simply wait and the problem will get sorted for you with the 'old' version being checked in. The ones BuildRequiring python-gobject-devel will need to verify if their code does what it is supposed to to. Failures to build or start might hint that the other bindings are required. I hopes not to many started debugging their new build Failures or expansion errors yet. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] more systemd
by Alin Marin Elena 19 Aug '11

19 Aug '11

Hi there, today got new messages from systemd. [ 3.391686] systemd-cryptsetup-generator[294]: Failed to open /etc/crypttab: Bad file descriptor [ 3.391902] systemd[1]: /lib/systemd/system-generators/systemd-cryptsetup- generator exited with exit status 1. [ 4.464321] systemd[1]: Cannot add dependency job for unit crypto.service, ignoring: Unit crypto.service is masked. [ 43.423929] systemd-uaccess[518]: Failed to determine active user on seat seat0. [ 43.535655] systemd-uaccess[604]: Failed to determine active user on seat seat0. [ 43.701841] systemd-uaccess[685]: Failed to determine active user on seat this one many times. Alin -- Without Questions there are no Answers! _____________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________

4 10

[opensuse-factory] syslog(-ng) and systemd
by Peter Czanik 19 Aug '11

19 Aug '11

Hello, What is the current status of syslog(-ng) and systemd? I read in the syslog-ng changelog, that: "- Removed obsolete systemd integration patch, added to install syslog-ng service file as forced in bnc#696963 even feature 311316 is not yet implemented, that is, log rotation files do not work, chroot socket config file is never generated when running under systemd. " I just prepared an updated package for syslog-ng, which updates the package to syslog-ng 3.3 beta2. It works nicely with sysvinit. Should I care about systemd, or the above problems are still not solved? I don't see any progress reports at https://features.opensuse.org/311316 My syslog-ng 3.3 beta2 packages are available at https://build.opensuse.org/project/show?project=home%3Aczanik%3Asyslog-ng33 (still compiling). Notes: - mongodb is broken (fix is available in git) - compiled in timestamp is disabled now by a patch, will be turned into a configure option by upstream - there is a versioned binary in the plugin directory, no fix yet Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] Request for new project devel:languages:ocaml
by Andrew Psaltis 19 Aug '11

19 Aug '11

Objective Caml (OCaml) [1] is a multiparadigm language in the ML family of languages. OCaml is itself already in the openSUSE distribution, located in devel:languages:misc. I have located three other packages that use it: - lablgtk2 (in devel:languages:misc) - ocaml-facile (in KDE:Distro:Factory) - unison (in network) I have recently submitted a large patch to the ocaml package in devel:languages:misc, and I have 25 other OCaml library packages in my home project, accumulated over the last several months [2]. Upon approval, I will submit them there, excluding camlimages, which currently has a build problem on 64-bit architectures. Since there are already a large number of OCaml packages in Fedora, I have modified various spec files from there when packages from there already exist. Those that were derived from fedora are marked as such. The Fedora Contributor License Agreement [3] permits users to re-license them as seen fit. All spec files are placed under the MIT license, unless there was already a license upon them (as was the case with the ocaml package, which came from SUSE itself). As for packaging guidelines, I have attempted to follow those specified by the Fedora project [4]. As such, they tend to conform to whatever specifications that rpmlint uses. Furthermore, to ensure that inter-package dependencies resolve correctly, I have enabled the internal dependency generator on builds that were on openSUSE distributions before the current Factory build. Doing such enables features that essentially match what ocaml.attr does in RPM 4.9. ~Andrew [1] http://caml.inria.fr/ [2] https://build.opensuse.org/project/show?project=home:NaCl:ocaml [3] http://fedoraproject.org/wiki/Legal:Licenses/CLA [4] http://fedoraproject.org/wiki/Packaging:OCaml

3 8

[opensuse-factory] apparmor problem
by Peter Czanik 18 Aug '11

18 Aug '11

Hello, I'm planning to update syslog-ng to the latest beta release (3.3 final should be here real soon now). I checked the current syslog-ng in factory and ran into an interesting problem: linux-1wrf:/etc/apparmor.d # rcsyslog start Starting syslog servicesError opening file for reading; filename='/proc/kmsg', error='Operation not permitted (1)' Error initializing source driver; source='src', id='src#1' Error initializing message pipeline; startproc: exit status of parent of /sbin/syslog-ng: 2 failed linux-1wrf:/etc/apparmor.d # grep kmsg sbin.syslog-ng @{PROC}/kmsg r, It works fine when I disable AppArmor. Any hints why I get "Operation not permitted", when access to the file is actually allowed? Bye, CzP (from syslog-ng upstream) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

[opensuse-factory] rpm --delsign fails on factory packages
by Pascal Bleser 18 Aug '11

18 Aug '11

We're having a really weird issue at Packman with packages that are built with/for Factory: when we do an "rpm --delsign" on those packages, it just fails with exit code 255 (and no further ado). Needless to say that it works fine with stuff up to 11.4. (We do it because it's part of our process, we re-sign packages with another key when they're being put into the public repositories, for security reasons but, unfortunately, --resign doesn't work at all and we have to --delsign first, then --addsign). Did anything change in rpm in factory in the last couple of weeks that could affect that ? It worked until a few weeks ago (don't have the exact time, unfortunately) Here is such an RPM where --delsign doesn't work (it's just 5kb) -- it really affects all of them, but only on Factory: http://dl.dropbox.com/u/2940942/fail.rpm cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf

1 2

[opensuse-factory] openqa -some adjustments//fixes
by doiggl＠velocitynet.com.au 18 Aug '11

18 Aug '11

Hello >From results of http://openqa.opensuse.org/results/openSUSE-NET-x86_64-Build0217-kdedevel There are a few items with messages that a simple action would fix Glenn -trust key {timeout section} http://openqa.opensuse.org/viewimg/opensuse/testresults/openSUSE-NET-x86_64… -command not found aplay,sudo http://openqa.opensuse.org/viewimg/opensuse/testresults/openSUSE-NET-x86_64… http://openqa.opensuse.org/viewimg/opensuse/testresults/openSUSE-NET-x86_64… mismatch - Looks like script went wrong http://openqa.opensuse.org/viewimg/opensuse/testresults/openSUSE-NET-x86_64… -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] mariadb exploding in size?
by Stefan Seyfried 18 Aug '11

18 Aug '11

Hi all, is this normal? The following packages are going to be upgraded: libmariadbclient16 5.1.44-7.5 -> 5.2.7-2.1 x86_64 factory-oss openSUSE libmariadbclient_r16 5.1.44-7.5 -> 5.2.7-2.1 x86_64 factory-oss openSUSE mariadb 5.1.44-7.5 -> 5.2.7-2.1 x86_64 factory-oss openSUSE mariadb-client 5.1.44-7.5 -> 5.2.7-2.1 x86_64 factory-oss openSUSE 4 packages to upgrade. Overall download size: 6.1 MiB. After the operation, additional 14.6 MiB will be used. The installed packages are 24.7 MiB, so it's a significant increase... I'm doing "zypper rm *maria*" since I don't need it anyway, but just was interested if this is as designed... -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0