March 2014 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] rpmlint-mini
by Matwey V. Kornilov 18 Mar '14

18 Mar '14

Hi Dirk and all, Some time in the past, I've integrated my rpmlint check (ErlangCheck.py) to openSUSE's checks. It is in Factory's rpmlint for a long time. Now, I would like to continue and make my check available as option to maintainers in OBS. The dependencies to ErlangCheck.py are python-pybeam, python-construct and python-six. All of them are in Factory for a long time. I need to modify rpmlint-mini to pack parts of python-pybeam, python-construct in order to make ErlangCheck.py working in OBS workers. I see that rpmlint-mini.spec is full of magic. What is the preferred way to pick python modules from %python_sitelib? Should I add another deps.txt and yet another loop...? I can make this is hundred different ways but it is better to ask prior. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] py2pack in openSUSE 13.1 is broken
by Olav Reinert 16 Mar '14

16 Mar '14

Hi, On the wiki page detailing the packaging guidelines for python, the very first example (section "The fast and automated way") does not work (on 13.1 with all updates installed), it fails as follows: $ py2pack search zope.interface searching for package zope.interface... Traceback (most recent call last): File "/usr/bin/py2pack", line 22, in <module> main() File "/usr/lib/python2.7/site-packages/py2pack/py2pack.py", line 245, in main args.func(args) File "/usr/lib/python2.7/site-packages/py2pack/py2pack.py", line 71, in search for hit in pypi.search({'name': args.name}): File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1578, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1312, in single_request response.msg, xmlrpclib.ProtocolError: <ProtocolError for python.org/pypi: 301 Moved Permanently> So it seems python.org changed the web API for accessing pypi. On GitHub there's a newer version of py2pack which seems able to handle it. Is a py2pack update coming for openSUSE 13.1 that makes the tool work again? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] What settings are needed for seamonkey mail to show mail of localhost [linux]
by doiggl＠velocitynet.com.au 16 Mar '14

16 Mar '14

Hello, This is a setting up a package question. I was unsure what forum to post this to. How can a mail client [eg. seamonkey mail client]show or list the contents of /var/spool/mail/root on localhost [127.0.0.1]. What settings are needed to do this? I attached existing screenshots of settings. Thanks Glenn # mailx shows: # mailx Heirloom mailx version 12.5 7/5/10. Type ? for help. "/var/spool/mail/root": 29 messages 8 new 29 unread U 1 root(a)test.site Fri Mar 14 00:55 24/743 Cron <root@test> /sbin/dhcpcd -d eth0 U 2 root(a)test.site Fri Mar 14 01:00 30/854 Cron <root@test> /usr/bin/createrepo /home/rpms-customised/ . . N 28 root(a)test.site Fri Mar 14 18:55 23/733 Cron <root@test> /sbin/dhcpcd -d eth0 N 29 root(a)test.site Fri Mar 14 19:00 29/844 Cron <root@test> /usr/bin/createrepo /home/rpms-customised/ ? q Held 29 messages in /var/spool/mail/root You have mail in /var/spool/mail/root

1 0

[opensuse-packaging] fubar mozilla repos?
by Felix Miata 16 Mar '14

16 Mar '14

On a 13.1 system I just tried to upgrade firefox-esr from MozillaLegacy from 17.0.10 to 17.0.11. I've been doing this on multiple systems for months since 17.0.x reached end of life last fall with no apparent problems. Today if failed, as 17.0.11 now in the repos requires mozilla-nss and/or mozilla-certs >= the highest available in any standard or Mozilla or MozillaLegacy 13.1 repo. To get it to install the required minimum version and thus install 17.0.11 I had to add the Mozilla repo for Factory. Installed and apparently working now on host gx62b: firefox-esr-17.0.11-1.3.x86_64 firefox-esr-branding-upstream-17.0.11-1.3.x86_64 mozilla-nspr-4.10.4-67.1.x86_64 mozilla-nss-3.15.5-1.1.x86_64 mozilla-nss-certs-3.15.5-1.1.x86_64 -- "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-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 4

[opensuse-packaging] krb5 dependency in Base:System
by Stephan Kulow 12 Mar '14

12 Mar '14

Hi, It's currently impossible to submit packages from Base:System due to repo-checker blocking submissions as base packages suddenly require krb5. This is due to a change in libtirpc, that creates a huge cycle. As I'm protecting Factory from having that cycle too, I block such updates. Unfortunately the check hits other packages in the cycle too, so this means: unless this change is reverted, it won't be possible to submit base packages. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

14 48

[opensuse-packaging] allowing download in python package?
by Jason Craig 07 Mar '14

07 Mar '14

I am upgrading the package python-zope.testbrowser to its latest version. The tests were disabled because they were broken, but I have reason to believe from the change log that upstream has fixed the broken tests. Indeed, re-enabling the tests have only one failure now instead of four. The test that is failing is trying "browser.open('http://google.com/ncr')", so clearly the restriction to block installation of other python packages during a build is causing this failure. Is there any way to work around the restriction to allow this test to happen: temporarily disable the restriction or allow a certain URL or subset of URLs? Tests are good, it would be nice to enable them again. -- Jason Craig -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 6

[opensuse-packaging] Building bobcat, error in sendmail-devel?
by Daniël Huisman 06 Mar '14

06 Mar '14

Hi all, I'm still trying to build bobcat[1] and make it in an RPM. It always keeps hanging on the same error. This error has to do with a package included in openSUSE. I was hoping any one knows a workaround for this. The buildlog can be found here[2]. But to make it easier here are the error lines: Creating shared library libbobcat.so g++ --std=c++0x -O2 -g -Wall -isystem tmp -fPIC -shared -Wl,--as-needed,-z,defs,-soname,libbobcat.so.3 -o tmp/lib/libbobcat.so.3.16.00 */os/*.o -lX11 -lssl -lcrypto -lreadline -lmilter -L/usr/lib/libmilter /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libmilter.a(listener.o): In function `mi_listener': /home/abuild/rpmbuild/BUILD/sendmail-8.14.7/obj.Linux.3.7.10-1.1-default.x86_64/libmilter/listener.c:941: undefined reference to `pthread_create' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libmilter.a(handler.o): In function `mi_handle_session': /home/abuild/rpmbuild/BUILD/sendmail-8.14.7/obj.Linux.3.7.10-1.1-default.x86_64/libmilter/handler.c:42: undefined reference to `pthread_detach' /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../lib64/libmilter.a(signal.o): In function `mi_spawn_signal_thread': /home/abuild/rpmbuild/BUILD/sendmail-8.14.7/obj.Linux.3.7.10-1.1-default.x86_64/libmilter/signal.c:174: undefined reference to `pthread_sigmask' /home/abuild/rpmbuild/BUILD/sendmail-8.14.7/obj.Linux.3.7.10-1.1-default.x86_64/libmilter/signal.c:180: undefined reference to `pthread_create' If I'm not mistaking this error has to do with something from sendmail that is missing. I hope someone can help in any way possible. Daniël Huisman [1] http://bobcat.sourceforge.net/ [2] https://build.opensuse.org/package/live_build_log/home:Drunken/bobcat/openS… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 5

[opensuse-packaging] Hidden patches/updated tarballs
by Michal Hrusecky 04 Mar '14

04 Mar '14

Hi, I just started helping review team with reviews and I'm running into people who instead of creating patches and documenting them just update and change tarball (without bumping the version) effectivelly hiding patches inside. It is obviously wrong, but I was asked for the policy and I'm failing to find it. Anybody can help? Apart from that, what are the best practices for git snaphot packages? It can be related... Thanks -- 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-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 9

[opensuse-packaging] Another round of drops of old failures
by Stephan Kulow 04 Mar '14

04 Mar '14

Hi, I filed delete request for nqp and python-lazr.authentication, both fail for > 100 days. Without these rakudo and apport won't build either, so I filed delete requests for them too. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] RFC: Namespacing group and usernames
by Guido Berhoerster 03 Mar '14

03 Mar '14

I'd like to propose the following addition to the packaging policy regarding users and groups (https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups): The names of users and groups which are created by a package should be prefixed with an underscore "_". This creates a safe namespace for the distribution and avoids collisions between system group and usernames which are created by packages and regular group and usernames. Existing users and groups can be renamed with the following scriptlet: %pre getent group GROUP >/dev/null && groupmod -n _GROUP GROUP getent group _GROUP >/dev/null || groupadd -r _GROUP getent passwd USER >/dev/null && usermod -l _USER USER getent passwd _USER >/dev/null || useradd -r -g _GROUP -d HOMEDIR -s /sbin/nologin -c "user for PACKAGENAME" _USER Group or username collisions can be problematic, if a username required for a package already exists, the pre-scriptlet will silently re-use the user/group for the package. While YaST apparently contains a blacklist preventing the creation of known system users/goups, this is tedious to maintain manually and doesn't cover the case where an administrator creates accounts via useradd/groupadd or maintains users/groups in LDAP. The lack of a separate namespace also prevents the use of certain group or usernames which might be desired. There is precedent for the above policy, it has been implemented in OpenBSD since 2002/2003 where it requires changes to about half of the packages that provide users and/or groups. However, the overwhelming majority are simple configuration file changes and one-line patches to change hard-coded names (see also http://lists.opensuse.org/opensuse-packaging/2014-02/msg00103.html for a the numbers and https://build.opensuse.org/package/view_file/openSUSE:Factory/rpmlint/confi… for the group and usernames currently in use). This policy should only be enforced for new packages while existing packages can be gradually converted, I'd be willing to help with that. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 13