October 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] New packages submission to factory - rubygem-rspec, rubygem-packaging_rake_tasks and rubygem-yast-rake
by Josef Reidinger 09 Dec '13

09 Dec '13

Hi, I'd like to introduce a few new packages that I would like to have in factory ( not 13.1 ). All is related to changes in YaST development and conversion to ruby. rubygem-rspec[1]: Very famous testing frame-work for ruby. It is quite stable now and it is widely used in various projects for testing. Inclusion allows YaST to runs its new tests written in rspec during rpm build to help with early bugs detection ( Yast use CI, but check in during rpm helps with problem detection if dependency change and obs trigger rebuild ). I am willing to maintain it in factory and fix related bugs. rubygem-packaging_rake_tasks[2]: The gem is set of tasks for ruby build tool rake contains helpers for checking code quality, easy submit to Build Service or run local build. Project is around 2 years old and I maintain it myself. It is used in few projects to make submitting ruby projects to build service easier. It reaches version 1.0.0 where API of tasks is stable. I am author and I am willing to maintain it. rubygem-yast-rake[3]: The gem is rake configuration for yast projects. It is very young project and started few weeks ago, but it is needed for new yast CI. It uses packaging rake tasks. It provides to them configuration for yast projects ( like default devel project, default target project, etc. ) and add tasks specific for yast development. It is not much stable now, but yast is only project which depend on it and now it is not needed to build, so there is no risk, it just make yast developer life easier. I am author and I am willing to maintain it. If you have any question, complain or you are interested in such packages, do not hesitate to contact me. Josef [1] http://rspec.info/ [2] https://github.com/openSUSE/packaging_tasks/ [3] https://github.com/yast/yast-rake -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] Thunderbird and Firefox not working, Dolphin and stopping via KDE-menu very slow
by Jogchum Reitsma 24 Nov '13

24 Nov '13

Hi, After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show (process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed when started from the command line. There are several posts (also very recent ones) on various ml's about this error message for FF and TB, but none on opensuse (and none with a solution which works for me). After first start of FF, the FF-window appears, with the entries on the main menu, but without the corresponding icons. Starting it a second - or third, fourth etc.) the icons appear also, and a subwindow which lists the sessions that could not be opened (which is all sessions). No input is taken from mouse or keyboard, and also closing the window does not work (intil KDE kicks in). Also - but maybe not related - some applications are very, very slow starting up. For example to start dolphin it takes 75 secs. To restart or shutdown from the KDE menu it takes 2 minutes for the little stop-menu to appear, and another 75 secs before the real shutdown is started after choosing restart or shutdown. Shutdown as root from a terminal has it's normal speed. What can be going on here? regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 22

[opensuse-factory] running zypper from crontab
by doiggl＠velocitynet.com.au 23 Nov '13

23 Nov '13

Hello, Questions: 1. What command switches allow 'zypper -v up' to run from crontab ? 2. What command switches allow zypper to download the packages/rpm ? Thanks Glenn # zypper --help Usage: zypper [--global-options] <command> [--command-options] [arguments] Global Options: --help, -h Help. --version, -V Output the version number. --promptids Output a list of zypper's user prompts. --config, -c <file> Use specified config file instead of the default. --userdata <string> User defined transaction id used in history and plugins. --quiet, -q Suppress normal output, print only error messages. --verbose, -v Increase verbosity. --no-abbrev, -A Do not abbreviate text in tables. --table-style, -s Table style (integer). --rug-compatible, -r Turn on rug compatibility. --non-interactive, -n Do not ask anything, use default answers automatically. --non-interactive-include-reboot-patches Do not treat patches as interactive, which have the rebootSuggested-flag set. --xmlout, -x Switch to XML output. --ignore-unknown, -i Ignore unknown packages. --reposd-dir, -D <dir> Use alternative repository definition file directory. --cache-dir, -C <dir> Use alternative directory for all caches. --raw-cache-dir <dir> Use alternative raw meta-data cache directory. --solv-cache-dir <dir> Use alternative solv file cache directory. --pkg-cache-dir <dir> Use alternative package cache directory. Repository Options: --no-gpg-checks Ignore GPG check failures and continue. --gpg-auto-import-keys Automatically trust and import new repository signing keys. --plus-repo, -p <URI> Use an additional repository. --disable-repositories Do not read meta-data from repositories. --no-refresh Do not refresh the repositories. --no-cd Ignore CD/DVD repositories. --no-remote Ignore remote repositories. Target Options: --root, -R <dir> Operate on a different root directory. --disable-system-resolvables Do not read installed packages. Commands: help, ? Print help. shell, sh Accept multiple commands at once. Repository Management: repos, lr List all defined repositories. addrepo, ar Add a new repository. removerepo, rr Remove specified repository. renamerepo, nr Rename specified repository. modifyrepo, mr Modify specified repository. refresh, ref Refresh all repositories. clean Clean local caches. Service Management: services, ls List all defined services. addservice, as Add a new service. modifyservice, ms Modify specified service. removeservice, rs Remove specified service. refresh-services, refs Refresh all services. Software Management: install, in Install packages. remove, rm Remove packages. verify, ve Verify integrity of package dependencies. source-install, si Install source packages and their build dependencies. install-new-recommends, inr Install newly added packages recommended by installed packages. Update Management: update, up Update installed packages with newer versions. list-updates, lu List available updates. patch Install needed patches. list-patches, lp List needed patches. dist-upgrade, dup Perform a distribution upgrade. patch-check, pchk Check for patches. Querying: search, se Search for packages matching a pattern. info, if Show full information for specified packages. patch-info Show full information for specified patches. pattern-info Show full information for specified patterns. product-info Show full information for specified products. patches, pch List all available patches. packages, pa List all available packages. patterns, pt List all available patterns. products, pd List all available products. what-provides, wp List packages providing specified capability. Package Locks: addlock, al Add a package lock. removelock, rl Remove a package lock. locks, ll List current package locks. cleanlocks, cl Remove unused locks. Other Commands: versioncmp, vcmp Compare two version strings. targetos, tos Print the target operating system ID string. licenses Print report about licenses and EULAs of installed packages. source-download Download source rpms for all installed packages to a local directory. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] Extended Chromium builds for openSUSE !
by Raymond Wooninck 22 Nov '13

22 Nov '13

Dear list mates, Based on the official chromium tarballs, the process of building Chromium for openSUSE has become a lot easier. This allowed me to extend the Chromium offering for openSUSE users and the following is now available: openSUSE releases and Factory will follow the stable channel updates. I believe this is the right way where a stable Chromium is provided with a stable openSUSE release The OBS repository network:chromium, will provide besides the chromium package (stable channel), also the following packages: chromium-beta (This is based on the beta channel releases) chromium-dev (This is based on the dev channel releases). Please be aware that these packages are mutual exclusive and it is ONLY possible to install one of them. This to prevent issues with the chromium config files for the user. The Packman OBS has been updated to build the corresponding ffmpeg packages for each build to prevent issues. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] Syncing fixes between mkinitrd and dracut
by Michal Vyskocil 14 Nov '13

14 Nov '13

Hi, there is a new request [1] for mkinitrd fixing few bugs for openSUSE Factory. However there was a big effort to replace dracut as a default initrd tool, which seems to be turned on in Factory (see This will replace mkinitrd with dracut as the default initrd generator. in dracut.changes). So I would expect all development and fixing effort should go into dracut instead of mkinitrd (which is hard as even 13.1 won't have it as a default, so most reports are for mkinitrd). So atm the best we can do is to port mkinitrd fixes to dracut (and vice-versa?). Are all interested people aware about the intended switch and is there a process to forward bugs/feature requests from one group to an another? CCying people found in last .changes for both as not sure, who is subscribed here [1] https://build.opensuse.org/request/show/203579 BTW: there is no bugowner for dracut in Base:System/dracut Regards Michal Vyskocil

11 33

[opensuse-factory] Ancient hardware support statement
by Sascha Peilicke 13 Nov '13

13 Nov '13

Hi guys, without checking any mail archives, our forums or wikis for prior art, I would like to know if we have any general hardware support statements. I'm currently staring at a maintenance update that disables SSE2 support on certain software because the CPU doesn't support it. The manufacturing of that CPU stopped in 2004, so I'm not really sure what to think of it. Any thoughts? -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)

8 16

[opensuse-factory] RFC: new package: wemux
by Adam Spiers 08 Nov '13

08 Nov '13

Hi all, I've just packaged wemux: https://build.opensuse.org/package/show/home:aspiers/wemux and would like to find a suitable develproject to be its home. Suggestions gratefully received! Thanks, Adam -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] Plain text restriction [Was: Testing many small file write on several filesystems]
by Archie Cobbs 07 Nov '13

07 Nov '13

Jan Engelhardt <jengelh(a)inai.de> wrote: > 14:42 ares07:~ > xfs_info . > meta-data=/dev/md7 isize=256 agcount=32, agsize=22891675 blks > = sectsz=512 attr=2 > data = bsize=4096 blocks=732533583, imaxpct=5 > = sunit=0 swidth=0 blks > naming =version 2 bsize=4096 ascii-ci=0 > log =internal bsize=4096 blocks=357682, version=2 > = sectsz=512 sunit=0 blks, lazy-count=1 > realtime =none extsz=4096 blocks=0, rtextents=0 Sorry for the following rant, I just can't stand to be silent anymore... This filesystem performance discussion is very interesting! Unfortunately, I can't read any of the reported statistics. Why are they unreadable? Because all of the emails are plain text, but rendered in Gmail in a non-fixed width font, so the columns don't line up. Why are all of the emails plain text? Because all openSUSE mailing lists require this. Why do all openSUSE mailing lists require plain text? HECK IF I KNOW!?! This is 2013. Is anyone out there still reading email using /usr/bin/mail? It sure would be nice if people could send HTML email, like the rest of the world (and every other open source project I'm involved in) has been doing for the past 15 years, so that, say, a fixed-width font could be specified for stuff that needs a fixed-width font. We could even require HTML emails to be "multipart/alternative" for those remaining 17 /usr/bin/mail users. What am I missing? -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

23 60

[opensuse-factory] Going forward with Plymouth (based on dracut changes)
by Raymond Wooninck 07 Nov '13

07 Nov '13

Hi, Based on the recent changes for Dracut and making it replace mkinitrd, also has some consequences for Plymouth. Using Dracut at the moment would generate a smaller initrd file, then utilizing mkinitrd. Main reason for this is not that Dracut is so much smarter, but more that only partial Plymouth support is provided. The initrd that Dracut generated does not include the Pango libraries/modules and Font that is required to present the user with a question or comments during the boot process. In most cases this is never used, but for those users that utilize encrypted disks, this would be a major issue. This particular combination has been always a hot topic in the past and I would like to resolve it in the best way possible. As far as I can see, we have the following possibilities: 1) Drop the ask-for-password stuff from Plymouth, which would allow us to drop the additional library requirements. This would mean that the password for encrypted disks is validated before plymouth starts (all within the initrd) 2) Drop plymouth from initrd and start plymouth from disk after password, etc have been required. This would then be the task for systemd, which already has this support. 3) Try to establish a checking mechanism that implements option 2 for particular kernels/encrypted root/swap disks. For the other users there is no change. Option 2 would be easy to implement. For the others I don't know and I might have to rely on others to support me. However I would like to have your opinion on the right way forward. Thanks Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

14 21

[opensuse-factory] [13.1 RC1] - upgrade test: no network device
by Carlos E. R. 07 Nov '13

07 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm testing the offline upgrade method (DVD) from 12.3 to 13.1, in a vmplayer machine. I've hit a strange problem: no network. Aparently there is a conflict between the old network name, eth0, and the new, ens33. I had a look at yast network module (yast says the name is eth0), then rebooted. This is what the service status says now: +++······························· network.service - LSB: Configure network interfaces and set up routing Loaded: loaded (/usr/lib/systemd/system/network.service; enabled) Active: failed (Result: exit-code) since Tue 2013-10-29 00:37:31 CET; 1h 11min ago Process: 902 ExecStart=/etc/init.d/network start (code=exited, status=7) Oct 29 00:37:01 eleanor3 network[902]: Setting up network interfaces: Oct 29 00:37:01 eleanor3 network[902]: lo Oct 29 00:37:01 eleanor3 ifup[1186]: lo Oct 29 00:37:01 eleanor3 ifup[1230]: lo Oct 29 00:37:01 eleanor3 ifup[1233]: IP address: 127.0.0.1/8 Oct 29 00:37:01 eleanor3 network[902]: lo IP address: 127.0.0.1/8 Oct 29 00:37:01 eleanor3 ifup[1235]: Oct 29 00:37:01 eleanor3 network[902]: ..done ens33 Startmode is 'manual' -> skipping Oct 29 00:37:01 eleanor3 ifup[1301]: ens33 Startmode is 'manual' -> skipping Oct 29 00:37:01 eleanor3 network[902]: ..skippedWaiting for mandatory devices: eth0 Oct 29 00:37:31 eleanor3 network[902]: 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 6 5 4 3 2 1 0 Oct 29 00:37:31 eleanor3 network[902]: eth0 No interface found Oct 29 00:37:31 eleanor3 network[902]: ..failedSetting up service network . . . . . . . . . . . . ...failed Oct 29 00:37:31 eleanor3 systemd[1]: network.service: control process exited, code=exited status=7 Oct 29 00:37:31 eleanor3 systemd[1]: Failed to start LSB: Configure network interfaces and set up routing. Oct 29 00:37:31 eleanor3 systemd[1]: Unit network.service entered failed state. ·······························++- How should this be handled? If I try to delete the interface in YaST, and then add a new interface, it still says the name is eth0. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJvCJsACgkQtTMYHG2NR9UDdQCeIehd/YSBlnAFRXZok2+1UREr PM4An12cMm7q93fAsas1PrgqC3et14qJ =CY5N -----END PGP SIGNATURE-----

5 9