June 2014 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Setting up an openSUSE repository
by Wouter Verhelst 19 Jun '14

19 Jun '14

[I sent this to -programming first, which I now realize is probably the wrong list -- apologies for the double post] Hi folks, I'm trying to set up a repository with packages precompiled for a number of distributions, openSUSE being one of them. Running "createrepo" is fairly easy and seems to work, except that zypper complains that the repomd.xml file isn't signed. Adding "gpg --clearsign -b" to my script fixed that, except that now it starts complaining that the key isn't known, and I can't seem to figure out how zypper decides which keys are known, and/or to which repository they belong. Is this documented somewhere? If not, can someone explain to me how the pieces fit together? Ideally, I would like to just create a package containing the .repo file and other configuration files that I can then tell people to install. (Yes, I know about OBS, but due to various other requirements in our environment that isn't an option) Thanks, -- Wouter Verhelst NixSys BVBA M: +32 486 836 198 -- 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] removing old package files during version update
by Dmitry Roshchin 19 Jun '14

19 Jun '14

I am working on fixing update-alternatives mechanism for BLAS and LAPACK libraries. Libraries must be moved from %_libdir to %_libdir/blas and %_libdir/lapack to avoid conflict with ldconfig. %_libdir will contain only symlinks libblas.so.3 and liblapack.so.3, created by update-alternatives. [1] But main problem is migration between configurations. As I understand rpm use this sequence: 1. %pre (new version) 2. installing files 3. %post (new version) 4. %preun (old version) 5. delete difference in files 6. %postun (old version) Looks like step 5 deletes not only %_libdir/libblas.so.3.*, but %_libdir/libblas.so.3 too despite it is listed in new package. > %ghost %{_libdir}/libblas.so.3 Are there any ways to fix it? Without ugly hacks like this: > %post -n libblas3 > if [ "$1" = 2 ] ; then > if [ -f %{_libdir}/libblas.so.3.* ] ; then > rm %{_libdir}/libblas.so.3.* > "%_sbindir/update-alternatives" --auto libblas.so.3 > fi > fi Current package - lapack New package - https://build.opensuse.org/package/show/home:Dmitry_R:branches:devel:librar… [1] https://bugzilla.novell.com/show_bug.cgi?id=861081 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 1

[opensuse-packaging] Where can I find a plain kernel-vanilla on obs based on version linux-3.14x
by doiggl＠velocitynet.com.au 19 Jun '14

19 Jun '14

Hello, Some Questions: - Where can I find a plain kernel-vanilla on obs based on version linux-3.14.tar.xz [url to project] - If thats not available, is it possible do copy of Kernel:stable kernel-vanilla and down grade it to version 3.14.x The reason ask is the patch applies to linux-3.14.tar.xz version Thanks Glenn -- 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] Unifying libimobiledevice packages to one repository
by Marguerite Su 17 Jun '14

17 Jun '14

Hi, packagers, I updated libimobiledevice, libplist, libusbmuxd, usbmuxd and ifuse packages last night to fix the "forever" trust prompt on iOS 7 devices. Let me share some interesting things: 1. libimobiledevice buildrequires libplist & libusbmuxd 2. usbmuxd buildrequires libimobiledevice 3. ifuse buildrequires libimobiledevice 4. They are strictly tied in versions (of course they're developed by the same team) and: 1. libimobiledevice resides in mobile:synchronization:FACTORY 2. libplist resides in devel:libraries:c_c++ 3. libusbmuxd is a new package, which can be seen as a split from usbmuxd 4. usbmuxd resides in hardware 5. ifuse resides in filesystem Well, I think you know what I am going to say: 1. update libplist in home:MargueriteSu:branches:devel:libraries:c_c++ 2. package libusbmuxd in home:MargueriteSu:branches:devel:libraries:c_c++ 3. aggregate those two to home:MargueriteSu:branches:mobile:synchronization:FACTORY and home:MargueriteSu:branches:hardware 4. update libimobiledevice and usbmuxd 5. aggregate those two and libimobiledevice to home:MargueriteSu:branches:filesystem 6. update ifuse 7. submit them But even if I did so much work, they're still at unresolveable/failed status in their separated repositories untill repo maintainers do the same work. So I think can we move those 5 single purpose packages into 1 repository like hardware (because the purpose of these packages is to "support" a type of hardware) ? then the BURP will be quite easy. If no one is against my suggestion, I'll submit them to hardware and send a couple of changedevel requests to Factory. Greetings Marguerite -- 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] Where can I find the package to solve this install problem - Can't install perl-Email-MIME-Modifier-1.443-1.4.337.gc6d9374.rb2@noarch: no package provides perl(Email::MIME::ContentType) >= 1.0
by doiggl＠velocitynet.com.au 09 Jun '14

09 Jun '14

Hello, Where can I find the package to solve this install problem [see following]? - Have you a url to the package [in obs] --Thanks Glenn Error message: Can't install perl-Email-MIME-Modifier-1.443-1.4.337.gc6d9374.rb2@noarch: no package provides perl(Email::MIME::ContentType) >= 1.0 This is part of the spec: Name: perl-Email-MIME-Modifier Version: 1.443 Release: 1.%{_gitrelease} Provides: %{_gitprovides} Summary: Modify Email::MIME Objects Easily License: GPL+ or Artistic Group: Development/Libraries URL: http://search.cpan.org/dist/Email-MIME-Modifier/ Source0: http://www.cpan.org/modules/by-module/Email/Email-MIME-Modifier-%{version}.… Source99: gitinfo BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildArch: noarch BuildRequires: perl(Email::MIME) BuildRequires: perl(Email::MIME::ContentType) >= 1.0 BuildRequires: perl(Email::MIME::Encodings) >= 1.3 BuildRequires: perl(Email::MessageID) >= 1.2 BuildRequires: perl(Email::Simple) BuildRequires: perl(ExtUtils::MakeMaker) BuildRequires: perl(Test::More) >= 0.47 Requires: perl(Email::MIME) Requires: perl(Email::MIME::ContentType) >= 1.0 Requires: perl(Email::MIME::Encodings) >= 1.3 Requires: perl(Email::MessageID) >= 1.2 Requires: perl(Email::Simple) Requires: perl(Test::More) >= 0.47 Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version)) %define _perl_prov_blacklist ^Email::MIME$ This what was done: # zypper ar http://download.opensuse.org/repositories/home:/doiggl/openSUSE_13.1 test Adding repository 'test' ...........................................................................................................[done] Repository 'test' successfully added Enabled: Yes Autorefresh: No GPG check: Yes URI: http://download.opensuse.org/repositories/home:/doiggl/openSUSE_13. # zypper in bugzilla Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides perl-Email-MIME-Modifier >= 1.442 needed by bugzilla-4.4.4-30.1.noarch Solution 1: do not install bugzilla-4.4.4-30.1.noarch Solution 2: break bugzilla-4.4.4-30.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): # -- 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] revamping cgal : review
by Bruno Friedmann 05 Jun '14

05 Jun '14

To have several 3d related component ready for Application:Geo ( mainly sfcgal for postgis2 ) I've reviewed and revamp cgal package. The result is available here https://build.opensuse.org/package/show/home:bruno_friedmann:branches:Appli… I would like to have your feeling and precious advices about what I could have missed. Mostly the base package cgal doesn't deliver something and no more called libcgalSONAME libcgalSONAME is now independent and contain only lib. thus libcgal-devel doesn't exist anymore but cgal-devel deliver it I'm having troubles with %fdupes not being able to symlink all the png use in -doc-example-devel if someone has an idea why. The package will be submitted to Application:Geo and Dirk offer me to push it back to games. Thanks for your review time and advise. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board GPG KEY : D5C9B751C4653227 irc: tigerfoot ~~~Don't take Life too serious. Nobody gets out alive anyway!~~~ -- 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] update-alternatives: Conflict between wiki and rpmlint
by Michal Srb 03 Jun '14

03 Jun '14

Hi, I added support for update-alternatives to a package by following this page: http://en.opensuse.org/openSUSE:Packaging_Multiple_Version_guidelines When built, rpmlint complains about suse-alternative-link-missing and suse- alternative-generic-name-missing, even that they are there. The problem is that I used the update-alternatives command exactly as it is in the wiki page - with quotation marks around it: "%_sbindir/update-alternatives" --install /bin/vim vim /bin/vim-normal 15 Rpmlint doesn't parse this correctly (it takes the first thing after update- alternatives that doesn't start with "--", in this case it is the closing quotation mark instead of /bin/vim). Should this be reported as bug of rpmlint, or should I just change the wiki page? Isn't it too paranoid to put the quotation marks there? Michal -- 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] Python package and .po files
by jcsl 01 Jun '14

01 Jun '14

Hi. The Solaar package is in several repositories, but none of them install the translations files. I've branched the package to try to build it with the translations but if I do what I have done with other packages, use the %lang_package macro and add %files lang -f %{name}.lang in the spec file, it doesn't work. I get this: find: '/home/abuild/rpmbuild/BUILDROOT/solaar-0.9.2-22.1.x86_64/usr/share/locale/': No such file or directory find: '/home/abuild/rpmbuild/BUILDROOT/solaar-0.9.2-22.1.x86_64/usr/share/help/': No such file or directory No translations found for solaar in /home/abuild/rpmbuild/BUILDROOT/solaar-0.9.2-22.1.x86_64 error: Bad exit status from /var/tmp/rpm-tmp.GyVbWN (%install) I have no clue on how to fix this. Any hints? I've tried copying the .po files to the locale dir and it doesn't work. I'm making the translation for my languaje and I'd like it to be included in the package. Greetings. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 5