February 2014 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] policy for naming users?
by Dirk Müller 20 Feb '14

20 Feb '14

Hi, is there any kind of policy for the name of a user that is created by an opensuse package %pre script? Does it have to match the name of the package? the init script? https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups is quite vague on that. Is there a way to "register" usernames ? if so, which one is it? I looked at FHS but couldn't find a good pointer. Is there one? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

9 13

[opensuse-packaging] rpmbuild - %doc keeps wiping out additional %docdir files?
by David C. Rankin 20 Feb '14

20 Feb '14

All, I need help. I am working on packaging WordNet. Doing so, I have 5 doc files in the base directory of the source packages I want in the documentation directory of the final package: %doc AUTHORS ChangeLog COPYING LICENSE README Fine - works, puts the files in /usr/share/doc/packages/WordNet where I want them. However, I also have the html, pdf, and ps documentation directories I want to put in that SAME directory. In the %install section I create the directory and move the documentation dirs (html,pdf,ps) to /usr/share/doc/packages/WordNet with the following: # Make proper document dir, mv doc files, rm old doc dir mkdir -p %{buildroot}/usr/share/doc/packages/WordNet mv %{buildroot}/usr/doc/* %{buildroot}/usr/share/doc/packages/WordNet rm -rf %{buildroot}/usr/doc/ I then add: %files ... %docdir /usr/share/doc /usr/share/doc rpmbuild completes fine, but NONE of the (html,pdf,or ps) directories are present in the final package. None of these exists: /usr/share/doc/packages/WordNet/html /usr/share/doc/packages/WordNet/pdf /usr/share/doc/packages/WordNet/ps Grr.. From research I found that this was due to the %doc AUTHORS... line wiping out everything else in the /usr/share/doc/packages/WordNet directory -- the reason given: "that is just rpm being dumb, that's just the way it has always been." But there was no explanation how to fix this issue. It seems simple. All I want to do is move the documentation from %{buildroot}/usr/doc/{html,pdf,ps} to %{buildroot}/usr/doc/packages/WordNet/{html,pdf,ps} and include those directories along with the files AUTHORS ChangeLog COPYING LICENSE and README. But how do I do it without the first %doc line wiping them out? I have given up in the interim and just created a %{buildroot}/usr/doc/packages/WordNet-docs directory and move the html, pdf and ps directories there, but I really would like all documentation under /usr/share/doc/packages/WordNet. How do I do that?? Here is my current %files setup. %files %defattr(-,root,root) /usr/bin /usr/include /usr/lib64 /usr/lib /usr/share/applications /usr/share/pixmaps /usr/share/wordnet %doc AUTHORS ChangeLog COPYING LICENSE README %docdir /usr/share/doc/packages/WordNet-docs /usr/share/doc/packages/WordNet-docs What say the masters? What is the trick? The full spec file is here: http://www.3111skyline.com/dl/openSUSE/pkg/wordnet.spec -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 9

[opensuse-packaging] Tumbleweed build problem for a package I support
by Lee Duncan 19 Feb '14

19 Feb '14

I support the hardware / iscsitarget package, and recently the Tumbleweed builds started failing. The patching for my spec file looks like this: ------------------------>8---------------------- %prep %setup -q -n %name-%version-svn %if 0%{?suse_version} > 1220 %patch1 -p1 %patch2 -p1 %patch3 -p1 %if 0%{?suse_version} > 1230 %patch4 %endif %if 0%{?suse_version} > 1310 %patch5 -p1 %endif %endif ------------------------>8---------------------- I traced down the Tumbleweed build errors to the fact that patch 5 is not being applied but should be. This seems to imply (to me) that the suse_version for tumbleweed has recently changed, or that the kernel that Tumbleweed uses has changed, since this patch is only needed for kernel 3.13 or higher. All other platforms are compiling as expected. Any ideas? -- Lee Duncan SUSE Labs -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] CI rights management
by Sascha Peilicke 19 Feb '14

19 Feb '14

Hi guys, since more and more openSUSE projects start to make use of our CI infrastructure, we have to organize who's allowed to do what. In the past we just added more and more people with rights to organize everything. So I tried to reduce the global list of users with admin rights. Instead, we now have a per-project (translates to Jenkins job) ACL matrix where each project can organize stuff themselves. In simple words, you now can configure per job who's allowed to change things. There should be no need to bug me again :-) That said, the list of ci.o.o admins now is: coolo, jdsn, bmwiedemann and saschpe (me). The following openSUSE projects currently use ci.opensuse.org: - Open Build Service / osc - OpenStack - Yast / libyui The first two projects have per-job based access rules set already. If you have a ci.o.o job and want to grant somebody the right to modify it, just check "Enable project-based security" and add the (already registered) user in question. And if you want to add your openSUSE-related project to our CI, please get in touch with any of the guys mentioned above. That's it. -- 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) -- 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] systemd macroes
by Matwey V. Kornilov 19 Feb '14

19 Feb '14

Hi, It is not clear how to use %service_add_pre and co. correctly. If I have foo.service and foo.socket, should I use %service_add_pre foo.service or %service_add_pre foo.service foo.socket ? Different packages use different strategy. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] systemd packaging: how to deregister services?
by Johannes Meixner 19 Feb '14

19 Feb '14

Hello, I would like to know how to correctly deregister services in RPM package install scripts. https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines only talks about "Register services in install scripts" Assume an older version of package "foobar" that provided both foo.service and bar.service as described in https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines is already installed. Now a newer version of "foobar" does no longer provide bar.service (but foo.service is still provided). What is the correct way in foobar.spec to deregister bar.service when updating the package "foobar"? I would like to use something like --------------------------------------------------- %pre %service_add_pre foo.service %service_del_pre bar.service %post %service_add_post foo.service %service_del_post bar.service --------------------------------------------------- I found "service_del_post" only mentioned in http://lists.opensuse.org/opensuse-packaging/2011-06/msg00160.html but it is not documented at https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines so that I don't know if it really exists and even if it exists I don't know if it would do "the right thing". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 17

Re: [opensuse-packaging] rpmbuild - %doc keeps wiping out additional %docdir files?
by Greg Freemyer 17 Feb '14

17 Feb '14

David, In this case, the best case process would have been: Search build.opensuse.org for wordnet. You would see it was in factory, so go to that package: https://build.opensuse.org/package/show/openSUSE:Factory/wordnet If you have an OBS account (and you do since you use bugzilla), log into OBS and click "Branch Project" directly below the description. Then use osc on the command line to create a local copy on your box. In my case I have ~gaf/obs as a folder I maintain, so I would: cd ~/obs osc co home:gregfreemyer:branches:Education/wordnet (It is automatically branched from Education because that is the official devel project for wordnet). You can then edit the specfile / *changes file / etc. to your hearts content. Use "osc build" to do local test builds and make sure your edits are fine. Once you are happy, use "osc commit" to push your local edits back to OBS. I then wait a few minutes/hours for the package to rebuild on all of the distros I care about. I check that status back on the WebUI. Once you are even happier, use "osc submit" to send the edits to the package maintainer for review. If he likes them, he will hopefully accept them and forward them to factory for inclusion in 13.2 (or whatever is next). At that point you have officially become a packaging contributor. Greg -- Greg Freemyer On Mon, Feb 17, 2014 at 3:04 PM, David C. Rankin <drankinatty(a)suddenlinkmail.com> wrote: > On 02/17/2014 01:50 PM, Greg Freemyer wrote: >> David, >> >> Is there something wrong with the way it is currently done in the >> Education project for the wordnet package? >> >> https://build.opensuse.org/package/view_file/Education/wordnet/wordnet.spec… >> >>>From the %install section: >> >> # Remove duplicate copies of docs installed by make install >> rm -rf %{buildroot}%{_datadir}/%{name}-%{version}/doc >> # Remove useless Makefiles installed by %%doc >> rm -rf doc/{html,ps,pdf}/Makefile* >> >>>From the %files section: >> >> %doc AUTHORS COPYING INSTALL ChangeLog README doc/{html,ps,pdf} >> >> Greg > > No, nothing, just me being too dumb to stumble across it before recreating the > Wheel. <lightbulb-on> The key with the %doc line seems to be no leading '/'. I > see their use of doc/{html,ps,pdf} and that would have made life easier :) > > The only other difference (other than me not having the patches) is I am > overlaying the wn3.1.dict.tar.gz database extensions on top of the WordNet-3.0 > release. > > Source: %{name}-%{version}.tar.bz2 > Source1: wn3.1.dict.tar.gz > <snip> > %prep > %setup -q > %setup -T -D -a 1 > > Basically, I got into this project packaging WordNet for the koffice/kthesaurus > WordNet extension for TDE on Arch. It worked so well and added a new "in > sentence context" to the thesaurus, I thought I would get a package together for > Ilya to include as an option for openSuSE/KDE3 (seems I'm a bit late :) > > Thanks again for the help and the link! > > -- > David C. Rankin, J.D.,P.E. -- 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] PAM usage needs sgid? Or am I doing something wrong?
by Stefan Seyfried 17 Feb '14

17 Feb '14

Hi all, While searching for an alternative to xscreensaver (I find the unlock screen plain ugly and don't use any of the animations anyway), I came across i3lock, which is already included in Factory. It does all I need (lock the screen) and is very lightweight. However, it misses one important feature: the actual unlocking of the screen :-) This works as root, and it works if I SGID shadow the i3lock binary. But I guess this is not the right thing to do? The package even includes a pam file /etc/pam.d/i3lock (this is suse package specific different from the upstream one) containing: #%PAM-1.0 auth include common-auth account include common-account password include common-password session include common-session But I cannot determine what this is good for. I put in some debug code and found out that pam_authenticate() fails with PAM_AUTH_ERR, for insufficient access to /etc/shadow, I would expect PAM_CRED_INSUFFICIENT, but then I know next to nothing about PAM internals. So what to do? make i3lock sgid shadow? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 11

[opensuse-packaging] wxwidgets 32bit Packages
by Philipp Seiler 12 Feb '14

12 Feb '14

Hi all, Why there aren't any wxwidgets related 32bit packages in openSUSE? Is there an appropriate reason to keep them out or there is just a missing baselibs.conf? For v2.8 I added baselibs.conf to the package and it works fine. https://build.opensuse.org/package/show?project=home%3Aseilerphilipp&packag… Should I add it for wxwidgets-2_9 too and then submit these packages to the correct devel project or is there a reason to keep the 32bit packages back? br, Philipp Seiler -- Philipp Seiler Linux Consultant Mail: seiler(a)b1-systems.de GPG Key: 0x75911461 B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 2

[opensuse-packaging] about update-alternatives usage
by Stephan Kulow 10 Feb '14

10 Feb '14

Hi, Please take more care about update-alternatives usage. There is only one correct usage and that's documented at http://en.opensuse.org/openSUSE:Packaging_Multiple_Version_guidelines I declined several requests lately that I just happen to spot. Most important is that files in %bindir are *not* ghosts, they are *always* binaries or fixed links to /etc/alternatives/* The links in /etc/alternatives/ in return are handled by update-alternatives and as such are %ghosts. One pitfall to consider: pre-13.1 rpmlint versions have a wrong check and they will tell you incorrect usage. Just ignore all rpmlint warnings for < Factory. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5