June 2014 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Packaging PHP: composer slowly kills PEAR as a base
by Ralf Lang 28 Jul '14

28 Jul '14

Hi folks, recently, a lot of PHP packages have been either converted from PEAR format to composer or offered in both format. Some new software has been composer-only right from the start. As far as I know, we only have tools for automatically dealing with PEAR format packages. This is going to get worse as the most widely used 3rd party pear server software, pirum, has been deprecated in favor of composer. This renders more and more pear based installations useless. http://pirum.sensiolabs.org/ https://twitter.com/fabpot/status/434256189258735616 Do you know how other distributions handle this? Is there any effort for (semi)automatic composer->rpm conversion tools? -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

4 4

[opensuse-packaging] Misleading package name?
by jcsl 30 Jun '14

30 Jun '14

Hi. I've just installed Glade and when I tried to open a GTK2 project I discovered that it is for the GTK3 version because it complains about obsolete widgets and it also says that it is only for GTK+ 3. However, the GTK2 version package is named glade3, hence my confussion. Is this intentionally or a mistake? Greetings. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 6

[opensuse-packaging] A Question about using /var/target
by Lee Duncan 30 Jun '14

30 Jun '14

Hello: I am trying to update an existing package in openSUSE called python-rtslib. This software keeps a database of configuration files in /var/target, under 4 subdirectories. I recently updated the software, and now it fails to build on OBS, giving the error: > python-rtslib: "/var/target" is not allowed anymore in FHS 2.2. > [ 61s] python-rtslib: "/var/target/alua" is not allowed anymore in FHS 2.2. > [ 61s] python-rtslib: "/var/target/fabric" is not allowed anymore in FHS 2.2. > [ 61s] python-rtslib: "/var/target/fabric/ib_srpt.spec" is not allowed anymore in FHS 2.2. > ... I looked up the Filesystem Hierarchy Standard 2.2, and I don't see any place where it says /var/target cannot be used. Can somebody point me at the part of the standard that disallows this? If this holds, this means that either we have to maintain our own set of patches to modify this package, or we have to sell the upstream folks on the merits of moving this (which would be difficult, since I don't see such merits). -- 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

3 2

[opensuse-packaging] search query.
by doiggl＠velocitynet.com.au 27 Jun '14

27 Jun '14

Hello, Some questions: - Is it possible to download all the obs repos that have a kernel-vanilla spec file in a kernel-vanilla package The reason I ask is: I am looking for a specific kernel-vanilla version of 3.14x Have you some code to loop through all the projects:packages to do this. What osc command can be used to download the spec file - have you got an example. I know it would take a long time to loop through all package names. Thankyou Glenn -- 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] Getting you better informed about progress
by Stephan Kulow 26 Jun '14

26 Jun '14

Hi, As the staging projects are a crucial part of the Factory submission workflow, the staging plugin (the tool we use to manage the submissions) adds comments to the staging projects so that interested users can see what's going on. For a while now we experimented with this, but only added the submitter without actually CCing him. So a comment in Staging:E looks like this: The list of requests tracked in openSUSE:Factory:Staging:E has changed: Request#236752 for package libwpd submitted by [AT]fstrba Request#236754 for package libodfgen submitted by [AT]fstrba Request#236755 for package libabw submitted by [AT]fstrba Request#236756 for package libcdr submitted by [AT]fstrba Request#236757 for package libixion submitted by [AT]fstrba Request#236759 for package libe-book submitted by [AT]fstrba Request#236760 for package libetonyek submitted by [AT]fstrba Request#236761 for package libfreehand submitted by [AT]fstrba Request#236762 for package libmspub submitted by [AT]fstrba Request#236764 for package libvisio submitted by [AT]fstrba Request#236765 for package libwps submitted by [AT]fstrba Request#236766 for package writerperfect submitted by [AT]fstrba Request#236842 for package libwpg submitted by [AT]scarabeus_iv Request#236843 for package liborcus submitted by [AT]scarabeus_iv Request#236846 for package libmwaw submitted by [AT]scarabeus_iv Request#238625 for package libreoffice submitted by [AT]scarabeus_iv Request#238626 for package liblangtag submitted by [AT]scarabeus_iv Now I want to replace the [AT] with a @, which will send emails to everyone involved. This means you will get more emails about your submissions - but you will also know better what's going on with your submission. I'm well aware that most of you get enough mails already, but I see no better way to inform the involved developers about problems. In the case of staging:E - if openQA finds a problem with libreoffice, I want to tell everyone who submitted a change to it. You can't expect anyone else to know which of the submitted package broke the libreoffice test. Greetings, Stephan -- 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] Can you see then number of a package downloads?
by jcsl 26 Jun '14

26 Jun '14

Hi. This is just curiosity and I'm not sure of if this is the right list. But, can you see the number of times that a package has been downloaded? I think that could be useful to decide whether to submit a package to some of the main repos or not. Greetings. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 8

[opensuse-packaging] Enforcing rpmlintrc as source
by Stephan Kulow 25 Jun '14

25 Jun '14

Hi, Tons of packages are broken as they don't mention rpmlintrc as Source. To remove work from the review team to check that, I fixed that case in the source_validator. It was incorrectly not giving a warning in this case. Please note that the way documented in the wiki is: "add a file named %name-rpmlintrc to your sources and list it in the spec file." - but we will accept any *rpmlintrc file if they are tracked as Source and don't contain setBadness calls. 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] Next drops
by Stephan Kulow 25 Jun '14

25 Jun '14

Hi, This time there are some more packages affected: opensuse-startup_en Fails for 158 days: broken by daps update? openstack-tempest Fails for 133 days: E: non-ghost-in-var-lock python3-pysendfile Fails for 118 days: python 3.4 update broke it python3-Mako Fails for 118 days: python 3.4 update broke it python3-kombu Fails for 118 days: python 3.4 update broke it rubygem-eventmachine Fails for 113 days: buildroot in generated files ndiswrapper Fails for 106 days: kernel 3.14 update Qrosspython Fails for 106 days: Could NOT find PythonLibs python3-mock Fails for 106 days: 'method-wrapper' object has no attribute '__module__' f-spot Fails for 106 days: mono crash pdfmod Fails for 106 days: mono crash Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- 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] How to localize the description and add a screenshot for a package?
by jcsl 21 Jun '14

21 Jun '14

Hi. Some packages show a localized description text in YaST's software management description section, and some of them show a screenshot in software.opensuse.org. How can I do that? Greetings. -- 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] Please aggregate libsodium to server:dns
by Marguerite Su 19 Jun '14

19 Jun '14

Hi, Please aggregate libsodium from devel:libraries:c_c++ to server:dns, It's a dependency for dnscrypt, which is now in unresolveable status except for 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

1 0

[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