February 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Important changes to patterns in factory
by Stephan Kulow 05 Feb '14

05 Feb '14

Hi, For years the whole patterns story was a very sad one. It was under-documented, in a strange format, spread over several strange files, generated by crude scripts, .... And this has changed now with a rather bold move in https://build.opensuse.org/request/show/220699 All scripts are gone - patterns-openSUSE is just yet another package and the solver will see what packages in the repository provides pattern(). This has several consequences: - patterns are tracked in OBS and no longer in github - I'll need to spend quite some time to redo the package list tracking for Lives and DVDs, but I'll gladly work on that ;) - we can actually split the patterns-openSUSE package into logical groups The last one is very important - it means we can e.g. have patterns-openSUSE-kde.spec in K:D:F and patterns-openSUSE-gnome.spec in G:F without the teams having to go through me to update their desktops. All that matters in the end is that their packages provide "pattern() = <DESKTOP>". Of course we don't have to, but I like the idea of being able to do that ;) Greetings, Stephan -- 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] staging concepts
by Matwey Kornilov 05 Feb '14

05 Feb '14

Hello, All. I don't completely understand staging concepts. Now we have stage for new kernel version. But It is not built for arm. How should we now that new kernel won't brake factory:arm? Currently, kernel is broken fir arm. -- Best regards! Posted using Hotdoged on Android -- 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] Wicked segfaults
by Sid Boyce 04 Feb '14

04 Feb '14

Bug #862234 submitted. And it's been a dog configuring the network by hand, bridge br0 does not work so I had to configure eth0 with ifconfig. No results from yast2 network either. From dmesg ----------------- [12052.581286] wickedd-dhcp6[26423]: segfault at 4 ip 00007f12e3b1acca sp 00007fff0a03b678 error 4 in libc-2.18.90.so[7f12e3a98000+1a2000] [12052.581338] wickedd-auto4[26422]: segfault at 4 ip 00007f1728fa2cca sp 00007fff9d612958 error 4 in libc-2.18.90.so[7f1728f20000+1a2000] [12052.588532] wickedd-dhcp4[26425]: segfault at 4 ip 00007f8bac5facca sp 00007fff9d9cb9c8 error 4 in libc-2.18.90.so[7f8bac578000+1a2000] [12052.684090] wickedd[26439]: segfault at 4 ip 00007f59c7beacca sp 00007fff979dba48 error 4 in libc-2.18.90.so[7f59c7b68000+1a2000] [12052.695699] wickedd-auto4[26441]: segfault at 4 ip 00007f6235182cca sp 00007fff8aaf5f48 error 4 in libc-2.18.90.so[7f6235100000+1a2000] [12052.696825] wickedd-dhcp6[26442]: segfault at 4 ip 00007fe6239b2cca sp 00007fffbfc10158 error 4 in libc-2.18.90.so[7fe623930000+1a2000] [12052.778915] wickedd-dhcp4[26449]: segfault at 4 ip 00007f6c9eb62cca sp 00007fff85e68268 error 4 in libc-2.18.90.so[7f6c9eae0000+1a2000] [12052.841878] wickedd-auto4[26451]: segfault at 4 ip 00007f3a9c622cca sp 00007fff3314b828 error 4 in libc-2.18.90.so[7f3a9c5a0000+1a2000] [12052.843604] wickedd-dhcp6[26452]: segfault at 4 ip 00007ffcd94c2cca sp 00007fffe1c23488 error 4 in libc-2.18.90.so[7ffcd9440000+1a2000] Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- 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] Python Packaging / PEP 426 / Request for involvement
by Tim Serong 04 Feb '14

04 Feb '14

Hi All, One of the talks I saw at linux.conf.au 2014 was Python Packaging 2.0: Playing Well With Others: https://www.youtube.com/watch?v=7An2GobbSWU Nick (the speaker) wanted me to make sure that we in openSUSE were aware of Python package metadata efforts, and is seeking feedback from distro people to make sure Python is doing things we can work with on a packaging front. I'm not especially deep into Python myself, so I'm putting this out here on opensuse-packaging and opensuse-factory in case someone more suitable is around ;) Relevant PEPs are: Metadata for Python Software Packages 2.0 http://www.python.org/dev/peps/pep-0426/ Version Identification and Dependency Specification http://www.python.org/dev/peps/pep-0440/ Standard Metadata Extensions for Python Software Packages http://www.python.org/dev/peps/pep-0459/ Regards, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.com -- 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] Trying to improve our communication
by Michal Hrusecky 03 Feb '14

03 Feb '14

Hi, as I was the one that sent this first highly confusing team mail about future releases, let's try again to clear stuff. We summarized everything (this time hopefully right) here in the blog post: http://lizards.opensuse.org/2014/02/03/trying-to-add-some-light/ -- Michal HRUSECKY SUSE LINUX, s.r.o. openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- 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] Timeline and roadmap V2
by Michal Hrusecky 03 Feb '14

03 Feb '14

Hi all, As you know we had a week-long meeting in Nuremberg. Quite a few of the things we've been working on (openQA, OBS workflow etc) were shared by now. Besides discussing features, we scheduled our work. In the previous thread on $SUBJECT, Simon noted that going for a release in November seemed a far smarter compromise between the benefits of releasing and getting some improvements in our tool chain than skipping a release. Most of the team agreed on this right away and we'd like to go for that. However. This does not mean the initial idea of doing a more 'relaxed' release is off the table. Planning software development is hard, planning experimentation (like the staging projects we are toying with) is impossible so we can not predict when we will be done. This means that we still intend to take those of you who stepped forward to help out with the release up on their offer. The exact nature of what we release is still to be determined and we'd like to make a more final decision on how much effort we can and will put in in August. So far it is sure that we would need some volunteer to keep eye on Factory and release milestones at least till then. So, for now, this will be a 'community release'. This might mean less QA but also no security updates provided by SUSE! Especially if it comes to the latter case we should communicate this carefully to our users as it will be more like a slightly more stabilized milestone than a successor to openSUSE 13.1. How to call it, how to communicate and what exactly it will look like - August. When exactly we will be fully back to working on Factory, releasing milestones, and working on the release we will hopefully be able to determine in August as well. Thoughts? The openSUSE Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

26 43

[opensuse-factory] rc* symlinks and systemd
by Ludwig Nussel 03 Feb '14

03 Feb '14

Hi, openSUSE has a packing policy of requiring rc* symlinks for each init script. So for e.g. /etc/init.d/foo there must be a symlink /usb/sbin/rcfoo -> /etc/init.d/foo. There is an rpmlint check for this policy (suse-missing-rclink). Now that more and more packages correctly switch to systemd only and drop the init scripts the rpmlint check doesn't work anymore. So we are slowly losing a nice convenience feature of openSUSE. Techically the feature works also for systemd units by making the rc symlinks point to /usr/sbin/service. When in involked as e.g. "rcfoo start" this script would then run "systemctl start foo.service". Personally I'd like to see us keeping the rc* feature also in the future so I'd like to propose introducing an rpmlint check to complain about missing rc* symlinks also for systemd unit files. Any objections on that? Otherwise I'd extend the suse-missing-rclink rpmlint check to .service files at some point. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 21

[opensuse-factory] 13.1 —> 13.2
by Kyrill Detinov 03 Feb '14

03 Feb '14

Hello. /etc/os-release is outdated. NAME=openSUSE VERSION="13.1 (Harlequin)" VERSION_ID="13.1" PRETTY_NAME="openSUSE 13.1 (Harlequin) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:13.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" -- WBR Kyrill

4 5

[opensuse-factory] OT: SLES 11 Register service are broken ?
by Günther J. Niederwimmer 03 Feb '14

03 Feb '14

Hello, I mean the NOVELL / SUSE register Server are broken? On my System all online Repository are deleted? My Key is not expired. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Maintainers wanted for Dracut and Plymouth
by Raymond Wooninck 02 Feb '14

02 Feb '14

Hi, I have come to the point where I can no longer maintain the two packages Dracut and Plymouth. It has already been quite some time that I did anything with the two packages and I found myself lucky that some other people made some updates and fixes to it. The reason why I am looking for new maintainers is simply due to: 1) Lack of time on my side 2) Specific required knowledge I hope that somebody will step up to take the maintenance of these two packages, otherwise according to the Factory rules unmaintained packages should be removed. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0