December 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Why openSUSE still uses ifup by default?
by Ignacio Areta 11 Dec '13

11 Dec '13

Hello list, So, the question is in the subject. I'd like to understand the motivation behind this choice. In my opinion, NetworkManager should be the default for network setup. The use of ifup doesn't show any advantage: configuration for WiFi is problematic (and sometimes for wired networks too), it increases the startup time and the service doesn't restart properly. OK, NetworkManager has its problems too, but it's a better solution than this, specially for newbies in this distro. So, does someone have any plans to change this? Ignacio -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

41 95

[opensuse-factory] Re: puzzled by rsync
by L.A. Walsh 11 Dec '13

11 Dec '13

On 12/9/2013 5:36 PM, Felix Miata wrote: > source & target have same filesystem size, block size, filesystem type > OS 11.4 running on both --- Couple of scenarios to rule out: 1) going from disk1 a -> 500G file b->empty to disk2 a=>empty b->500G file ---- --delete = --delete-during which means it won't try to delete a later encountered directory until it gets to copying 'b'. If your disk is 750G, your copy will die in the middle of copying "a". Maybe delete-before would be better, though theoretically less safe, in that you might be deleting 500G before the copy on disk1 has safely made it to disk2. But if you are tight on disk space.... 2) If your target disk is more fragmented, then it will need more free-space extents(clusters) -- rather than 1 range with 2G, it might need 20 ranges with 100MB each. That means disk 2 will need more "indirect" space to hold the extra ranges. Those are possibilities that come to mind off the top of my head... -- 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] delete open-ovf package
by Jim Fehlig 10 Dec '13

10 Dec '13

Hi, I'll be sending a delete request to remove open-ovf from Factory. This project never really acquired an upstream community, and what little it did has been dead for years. The code is overly complex, poorly written, has a terrible interface, and doesn't belong in openSUSE IMO. Regards, Jim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] with apparmor enabled by default, shouldn't all packages come with an apparmor profile?
by Per Jessen 10 Dec '13

10 Dec '13

Now that we have reverted to having apparmor enabled by default, shouldn't we also require (or least suggest) that all packages include a suitable apparmor profile? Running "aa-logprof" is no big deal for an experienced admin, but having ready-to-go apparmor profiles would make life easier for the newbie. -- Per Jessen, Zürich (2.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 8

[opensuse-factory] libsolv broken in Factory -> Unable to refresh repositories
by Raymond Wooninck 10 Dec '13

10 Dec '13

Hi Everyone, Just a heads up, it seems that after the big update from factory last night, it is broken again. zypper ref doesn't update the repositories anymore as that it fails due to ta missing appdata2solv command. Seems Zypp:HEAD got already the correct update, but I assume that even after this fix gets into factory, you have to update it manually as that zypper will no longer work. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] zypper dup 12.2 -> 13.1 fail
by Archie Cobbs 10 Dec '13

10 Dec '13

I upgraded a machine yesterday via "zypper dup" from 12.2 -> 13.1. Several things went wrong. Instead of creating a bunch of bugs in bugzilla (which I don't have time for anyway) and having half of them be irrelevant, already fixed, etc. I thought I'd run these issues by the mailing list first in case anyone wants to step up to investigate. An edited log of the upgrade is here: http://pastebin.com/YYr9gGT7 Note, "Installing" lines are only shown for those RPMs that spit out errors. Problems are listed in order of severity most to least... Problem #1: After the upgrade, /boot/grub/menu.lst was empty (contained zero choices). In other words, zypper left my system in an unbootable state. I have no idea why this happened. Fortunately I had a backup which I edited to match the new kernel and installed before rebooting. Problem #2: The upgrade hung during "Installing rtkit-0.11_git201205151338-5.2.1" The stuck process was: dbus-send --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig > /dev/null 2>&1 I had to kill -9 this process in order to get zypper running again. Problem #3: Several mkinitrd's failed due to "plymouth: symbol lookup error: plymouth: undefined symbol: ply_logger_is_tracing_enabled" Several RPMs run the mkinitrd stuff in %post. At first these worked, then they started failing with the above error, and then later they started working again once plymouth had been installed. Perhaps there is a missing Requires(post): dependency? Problem #4: Multiple errors of the form "/etc/init.d/foo: No such file or directory" For example: Installing: at-3.1.13-5.4.1 .... /var/tmp/rpm-tmp.DPrmiC: line 8: /etc/init.d/atd: No such file or directory Problem #5: Lots and lots of other random errors in various %post scripts. See the log... http://pastebin.com/YYr9gGT7 -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

21 46

[opensuse-factory] inexplicable 32bit vs. 64bit zypper difference
by Felix Miata 10 Dec '13

10 Dec '13

Running 32 bit, only 32 bit and noarch packages are returned by zypper se -s output. Running 64 bit, both arches and noarch are returned, making output typically little short of double in size, conflated by normally irrelevant packages. Is there good reason why this is so? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] Zypper dup broken packages problem on Tumbleweed
by Nacho Man 10 Dec '13

10 Dec '13

Hello, I am having problems with my system. I'm new to OpenSUSE, however, I'm not new to Linux. I hadn't been getting updates for a while so I went to check what was wrong and when I run zypper dup --from 7 (with 7 being my Tumbleweed repository, I receive this: 11 Problems: Problem: problem with installed package kernel-desktop-3.7.10-1.1.1.x86_64 Problem: problem with installed package kernel-desktop-devel-3.12.0-34.2.ge8fa6b4.x86_64 Problem: problem with installed package kernel-devel-3.12.0-34.1.ge8fa6b4.noarch Problem: problem with installed package kernel-source-3.12.0-34.1.ge8fa6b4.noarch Problem: problem with installed package microcode_ctl-1.17-142.5.1.x86_64 Problem: libpurple-2.10.7-4.4.1.x86_64 requires perl = 5.16.2, but this requirement cannot be provided Problem: limal-nfs-server-perl-1.6.3-7.1.1.x86_64 requires perl = 5.16.2, but this requirement cannot be provided Problem: limal-perl-1.6.3-10.1.1.x86_64 requires perl = 5.16.2, but this requirement cannot be provided Problem: yast2-dbus-client-2.22.0-4.1.1.x86_64 requires libycpvalues.so.5()(64bit), but this requirement cannot be provided Problem: libyui-gtk-pkg4-2.42.2-3.1.1.x86_64 requires libzypp.so.1200()(64bit), but this requirement cannot be provided Problem: libyui-ncurses-pkg4-2.43.4.1-1.5.1.x86_64 requires libzypp.so.1200()(64bit), but this requirement cannot be provided Problem: problem with installed package kernel-desktop-3.7.10-1.1.1.x86_64 Solution 1: keep obsolete kernel-desktop-3.7.10-1.1.1.x86_64 Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): When I run zypper dup, it gives me a list of programs that will need to be downgraded. Does anyone have any suggestions on how to fix this? I'd rather not downgrade my software. To me, that means I messed something up some wheres along the line. I'm just not sure how. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[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] Re: zypper dup 12.2 -> 13.1 fail
by Jim Henderson 09 Dec '13

09 Dec '13

On Mon, 09 Dec 2013 02:27:44 +0100, Carlos E. R. wrote: >> I spent the better part of 3 hours trying to get it working, and in the >> end, I decided there was some old cruft on the system that was probably >> causing problems, and I could have spent another day trying to get it >> to work, or I could just install / from scratch and have a clean setup. >> I opted for the latter. > > There are two kinds of cruft after a system upgrade. Three, but OK. > * One, is that as the DVD is too small to contain the full oss repo, a > lot is missing. So you have to do after it: Well, yes, or if you've installed software from other sources that's not compatible with the new libraries, etc. Or if you have lots of repos configured (as I have done in the past). > * The second issue is stale config files. If you run "rcrpmconfigcheck" > you get a list of config files to check. Even on normal updates you get > them: I back those up regardless of how I do an upgrade. Better to be safe than sorry. This time around, I missed user cron jobs. Ah well, nothing overly complex in them, so recreating them isn't a problem. Third kind of cruft, BTW - are those things that are installed from unofficial sources. To each his own - I prefer doing a clean install every now and then regardless of the OS. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3