openSUSE Packaging June 2014

packaging@lists.opensuse.org

23 participants
18 discussions

[opensuse-packaging] Packaging PHP: composer slowly kills PEAR as a base

by Ralf Lang

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

6 years, 4 months

[opensuse-packaging] Misleading package name?

by jcsl

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

6 years, 5 months

[opensuse-packaging] A Question about using /var/target

by Lee Duncan

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

6 years, 5 months

[opensuse-packaging] search query.

by doiggl＠velocitynet.com.au

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

6 years, 5 months

[opensuse-packaging] Getting you better informed about progress

by Stephan Kulow

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

6 years, 5 months

[opensuse-packaging] Can you see then number of a package downloads?

by jcsl

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

6 years, 5 months

[opensuse-packaging] Enforcing rpmlintrc as source

by Stephan Kulow

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

6 years, 5 months

[opensuse-packaging] Next drops

by Stephan Kulow

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

6 years, 5 months

[opensuse-packaging] How to localize the description and add a screenshot for a package?

by jcsl

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

6 years, 5 months

[opensuse-packaging] Please aggregate libsodium to server:dns

by Marguerite Su

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

6 years, 5 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging June 2014