June 2013 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] CrossToolchain question
by Matwey V. Kornilov 25 Oct '13

25 Oct '13

Hi, In CrossToolchain:avr, I see avr-gcc-* and cross-avr-gcc. What is the difference? What is correct naming? (I suppose the last one). What guidelines/rules should I follow to create CrossToolchain subproject for yet unsupported arch? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 22

[opensuse-packaging] Packaging Guideline enforcement
by Dominique Leuenberger a.k.a DimStar 10 Sep '13

10 Sep '13

Dear Factory contributors and packagers, As openSUSE 12.2 is frozen and Factory is 'open to go wild' again, I would like to announce that the packaging guidelines have some extensions (not really new) that will be stricter enforced than they used to be. Currently a common rule to be 'ignored' or packagers are not aware is around the topics of: - .Changes entries - Patches First, the .changes entry (rpm changelog) surves two purposes: - News for the user - History tracking of packaging changes (often referenced in bugs to verify if a user has the latest packaging bugfixeS). A simple "Update to version x.y.z" is, as before, not accepted. There should be some buzz around the update for the user; some major reasons to the upgrade should be listed Changes on the package itself should be mentioned in a way that any other contributor to the same package can follow traces of why something is the way it is. Commonly, Added (build)dependencies are interesting to be seen, special hacks to make something work in a particular way [..]: Always consider that package maintenance is a distributed task and various contributors need to be able to step up at will. Patches: The rules about patches are listed at http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines . Most prominent is likely the mentioning of the patches life cycle, which forces you to mention additions and removals of patches in the changelog. As history shows, this can be helpful if a patch got removed, and later a regression is reported; finding out when a patch was removed can be crucial in reconstructing feature sets (including contacting the contributor that dropped it.. which is easily extracted from the .changes if listed) The main appeal is to the devel project maintainers / reviewers, to keep out for those rules, to live according to them, as it is frustrating for everybody if a package needs to be declined by the Factory Review team: - The dev prj maintainer is the one getting the 'decline' (as it was usually a forwarded request), which often leaves the 'fixing' to the devel project maintainers, where the 'originator' of the fix would have been willing to actually do that... And the Factory Review team also prefers to see complying submissions to having to reject SRs... reject is not fun for anybody! Looking forward to many more SRs to accept! Dominique / DimStar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

29 105

[opensuse-packaging] SONAME question
by Greg Freemyer 28 Aug '13

28 Aug '13

I just updated filesystems:ntfs-3g_ntfsprogs to have a new SONAME (83 -> 84) Do I need to add a Obsoletes: statement? Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 8

[opensuse-packaging] Package looking for volunteers: CodeAnalyst
by Cristian Morales Vega 08 Aug '13

08 Aug '13

As per https://bugzilla.novell.com/show_bug.cgi?id=793541 it seems CodeAnalyst needs a new maintainer. Any volunteer? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 13

[opensuse-packaging] Libclutter and Gala for Pantheon
by Antoine Saroufim 03 Jul '13

03 Jul '13

Good day, I've recently attempted to repackage Pantheon, Elementary's Desktop Environment, for openSUSE 12.3. I was able to get almost everything to work by simply using Alien and installing the correct dependencies in the correct order. However, Gala, the window manager, wasn't working well at all. Gala was showing an erroneous rendering of animations. As such I've decided to port the libclutter that Elementary uses. Gala worked admirably well with that version of libclutter, but it was at the expense of the GNOME Desktop, GDM, and Lightdm. They couldn't use Elementary's Libclutter and I had to reinstall openSUSE completely to get rid of it (unisntalling and reinstalling didn't work). Zypper counts Elementary's Libclutter as a downgrade of the one provided by openSUSE 12.3. They use libclutter-1.0.so.0 and libclutter-gtk-1.0.so.0. My coding skills are too poor to port Gala to a higher level of Libclutter and I can't figure out how to make Gala use an exclusive version of Libclutter while the rest of the GNOME Desktop would use the default one. The majority of Pantheon apps work very well under openSUSE and thanks to the GNOME:Ayatana repo, we have most of the dependencies. Plank has already been ported and packaged by an openSUSE user. I was able to get Noise, Pantheon-files, Slingshot-launcher, and Wingpanel working. If someone is interested in repackaging Gala for openSUSE, we can have another desktop environment available. Sincerely, Antoine Saroufim -- 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] games|Factory/xmahjong(g) package
by Dmitriy Perlow 01 Jul '13

01 Jul '13

Hello. Recently I've decided to play xmahjongg and surprised that I had failed to find out it in repos. So I made and submited it to games. When I opened a request to Factory, coolo answered that we already had xmahjong (not xmahjongg). I suggest to delete xmahjong and submit xmahjongg, that would provide and obsolete xmahjong :) Do I hear any objections? -- Dmitriy DA(P).DarkneSS Perlow / Linux x64 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] Is it only me ? osc tool broken
by Bruno Friedmann 25 Jun '13

25 Jun '13

Since a few day I've osc broken osc --help Traceback (most recent call last): File "/usr/bin/osc", line 24, in <module> osccli = commandline.Osc() File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 82, in __init__ self._load_plugins() File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 7926, in _load_plugins mod = imp.load_source(modname, os.path.join(plugin_dir, extfile)) File "/var/lib/osc-plugins/osc-collab.py", line 53, in <module> exclude_stuff.append(helper) NameError: name 'exclude_stuff' is not defined osc-0.140.0-103.1.noarch osc-plugin-install-0.22-1.1.noarch osc-plugin-overview-0.3.0-1.1.i586 osc-plugin-collab-0.96-12.1.noarch all coming from openSUSE:/Tools/openSUSE_12.3/ repository normal ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 6

[opensuse-packaging] Basic git-archive --remote question
by Greg Freemyer 24 Jun '13

24 Jun '13

I'm trying to create a tarball from a git tag and I'm not getting logged in for some reason. What is the right syntax for: git archive --format=tar --remote=ssh://git@github/com/dkovar/analyzeMFT.git v2.0.4 > analyzeMFT-v2.0.4.tar The upstream git repo is at: https://github.com/dkovar/analyzeMFT Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] libortp
by Mariusz Fik 21 Jun '13

21 Jun '13

Hi, I'm working on update libortp[1]. For now, we have package named libortp8 and version 0.20.0. Updating to current release 0.22.0 bumps so from 8 to 9. And now I have a dilemma, should I create a new package named libortp9 and let it reside along with libortp8 or create libortp (and avoid re-adding new package in the future when so gets higher number) and remove libortp8? [1] https://build.opensuse.org/package/show?package=libortp8&project=devel%3Ali… -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

2 2

[opensuse-packaging] Try to use BuildRequires ghostscript-mini[-devel]
by Johannes Meixner 20 Jun '13

20 Jun '13

Hello, this is a request to all package maintainers who have any kind of BuildRequires for Ghostscript in the spec files. I ask you to try out if it works for your particular packages when you use for building packages since openSUSE 12.2 only either BuildRequires: ghostscript-mini or BuildRequires: ghostscript-mini-devel in spec files that have any kind of BuildRequires for Ghostscript. Background information and reasoning: Since openSUSE 12.2 we have Ghostscript in the new source packages "ghostscript" and "ghostscript-mini" ("ghostscript-mini" is only a link to "ghostscript") and the Ghostscript fonts in the new separated source package ghostscript-fonts, see https://bugzilla.novell.com/show_bug.cgi?id=735824 In particular regarding "ghostscript-mini" see https://build.opensuse.org/package/show?package=ghostscript-mini&project=Pr… Excerpt: ----------------------------------------------------------------- Minimal Ghostscript provides only the file format drivers in particular to output JPEG PNG PostScript and PDF files but no printer drivers (in particular neither 'cups' nor 'ijs') and no X11 drivers. The ghostscript-mini package is only meant to be used by the openSUSE build service to avoid possible loops in the build dependencies because ghostscript-mini has minimal build dependencies (in particular neither CUPS nor X11 build dependencies). For most packages which need to only run Ghostscript during build, a single line "BuildRequires: ghostscript-mini" should be sufficient in the RPM spec file. For most packages which need Ghostscript development files to build, a single line "BuildRequires: ghostscript-mini-devel" should be sufficient in the RPM spec file. ----------------------------------------------------------------- You should not need BuildRequires for ghostscript-fonts-* packages because ghostscript-mini has RPM requires for ghostscript-fonts-std and ghostscript-fonts-other to make sure that Ghostscript has its fonts, see https://build.opensuse.org/package/view_file?expand=1&file=ghostscript-mini… 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

1 0

[opensuse-packaging] can apache HTTP Server be updated to version 2.4.4 [from v-2.4.3]
by doiggl＠velocitynet.com.au 19 Jun '13

19 Jun '13

Hello, Can apache HTTP Server be updated to version 2.4.4 [from v-2.4.3] https://build.opensuse.org/package/show?package=apache2&project=openSUSE%3A… http://httpd.apache.org/download.cgi Stable Release - Latest Version: 2.4.4 (released 2013-02-25) http://httpd.apache.org/download.cgi#apache24 -- Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] package looking for maintainer: the AT daemon
by Cristian Rodríguez 18 Jun '13

18 Jun '13

Hi: I will no longer maintain fix or otherwise care about the "at" daemon, starting now because I would rather devout my time testing and improving systemd.timer(5) So it is now up for grabs. that's all ;) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

19 47

[opensuse-packaging] Factory drop candidates
by Stephan Kulow 17 Jun '13

17 Jun '13

Hi, Due to long term failing I would like to drop these before end of June. Greetings, Stephan mono-tools Mono:Factory Fails for 182 days uiaatkbridge Mono:Factory Fails for 181 days uiautomationwinforms Mono:Factory Fails for 181 days branding-basedonopensuse system:install:head Fails for 127 days openstack-dashboard Cloud:OpenStack:Factory Fails for 121 days sblim-testsuite systemsmanagement:wbem Fails for 95 days openvas-manager security:OpenVAS:STABLE:v4 Fails for 95 days sblim-cmpi-firewall systemsmanagement:wbem Fails for 95 days sblim-cmpi-dns systemsmanagement:wbem Fails for 95 days libcompizconfig X11:Compiz Fails for 95 days compiz-plugins-main X11:Compiz Fails for 95 days compizconfig-settings-manager X11:Compiz Fails for 95 days -- 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] The Python3 devel project will be devel:languages:python3
by Sascha Peilicke 17 Jun '13

17 Jun '13

Hi guys, since the Python bunch had the discussion recently, I want to drop all python3 package _links in devel:languages:python and use their counterparts in devel:languages:python3 as devel packages for Factory from now on. This would include a number of chgdevel requests for Factory [1]. The idea behind to have only python2 packages in devel:languages:python. Currently, this project reached a size where it became tedious to use "zypper up". However, we will continue to track spec files for both python versions at the old package location (d:l:p). It should be easier to keep spec files in sync this way and you can submit changes for both in a single submit request. So for the packager, this won't change much. If you add a python3 spec file, a project maintainer will branch it to devel:languages:python3 once your sr is accepted. If we end up in far distant future where only python3 matters and the py2 maintenance burden isn't justified anymore, both projects can become independent of each other. For that we would simply remove _link files to d:l:p. So if nobody objects, I'll do it this afternoon. [1] http://paste.opensuse.org/83082794 -- Viele Grüße, Sascha Peilicke -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 5

[opensuse-packaging] libchoice for libjpeg devel for 12.3 ???
by Bruno Friedmann 16 Jun '13

16 Jun '13

On obs there's a increasing number of failed package ( essentially for x86_64 arch) For example https://build.opensuse.org/package/show?package=php5&project=server%3Aphp libjpeg62-devel libjpeg8-devel We have normally only libjpeg8-devel for 12.3 What happens ?? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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] Looking for new home for ejabberd
by Matwey V. Kornilov 16 Jun '13

16 Jun '13

Hi, Ejabberd XMPP server (package ejabberd) is currently hosting at devel:lanugages:erlang. And this is not appropriate place from which it may be submitted to Factory. Long time ago, we had erlang only in devel:languages:erlang, so ejabberd has been developing here. Now (since 12.2), we have erlang in Factory. So it is time to find more appropriate place for ejabberd, because it has nothing in common with development on erlang. In my personal opinion, I would like ejabberd to find asylum in server:messaging. I will miss it. Please, summon people, to whom it may concern. -- 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] Changelog: Reference github issues or pull requests
by Johannes Weberhofer 13 Jun '13

13 Jun '13

At http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Current_set_of… there is a quite impressive list of abbreviations to link to tickets of different system; As there is a growing number of tools which come from github, it would be great to have the possibility to reference the bugs; unfortunately they don't offer system-wide IDs but project specific IDs... Is there any plan how to handle this? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 7

[opensuse-packaging] How to proceed when upstream bundles prohibited sofware
by toganm＠opensuse.org 12 Jun '13

12 Jun '13

Hi, As the subject says how do we proceed when there is problematic bundled library code in the upstream. darktable package has bundled squish library in the sources, and after discussing with the legal team it is best we follow the same route as fedora. https://bugzilla.redhat.com/show_bug.cgi?id=972604 In fedora guidelines the solution outlined can be found in the following link: https://fedoraproject.org/wiki/Packaging:SourceURL#When_Upstream_uses_Prohi… Since there is no suggestion in our guidelines, how do I proceed in this case, as implementing the removal of offending code is not the issue but AFAIK our buildservice has some checks for the source code from the Source URL Also does this removal of the code should be applied in the home project also, as I am providing nightly git builds as well in addition to the official package. Togan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 7

[opensuse-packaging] Anyone willing to maintain libraw?
by Vincent Untz 12 Jun '13

12 Jun '13

Hi, Is there anyone who would like to be the maintainer of libraw (in the graphics OBS project)? I last touched this package in November 2010, but I never really considered myself as maintainer of it... FWIW, there's a security bug to deal with: https://bugzilla.novell.com/show_bug.cgi?id=822665 But otherwise, I don't think there's much work. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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] directories not owned by a package
by doiggl＠velocitynet.com.au 10 Jun '13

10 Jun '13

Hello, What would fix this problem [1]? What definition do I add to the %files section ? --Glenn [1] from the buildlog: [ 369s] mod_ssl-debuginfo-1:2.4.4-28.1.i586 [ 369s] ... running 01-check-debuginfo [ 369s] ... testing for empty debuginfo packages [ 369s] ... running 02-check-gcc-output [ 369s] ... testing for serious compiler warnings [ 369s] (using /usr/lib/build/checks-data/check_gcc_output) [ 369s] (using //.build.log) [ 370s] ... running 03-check-binary-kernel-log [ 370s] ... running 04-check-filelist [ 370s] ... checking filelist [ 370s] httpd-2.4.4-28.1.i586.rpm: directories not owned by a package: [ 370s] - /usr/lib/initscripts [ 370s] - /usr/lib/initscripts/legacy-actions Full spec file at https://build.opensuse.org/package/view_file?expand=1&file=httpd.spec&packa… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 6

[opensuse-packaging] Discontinuing some old GNOME:* projects in OBS
by Vincent Untz 09 Jun '13

09 Jun '13

Hi, I was looking at https://build.opensuse.org/project/subprojects?project=GNOME and realized we have many many subprojects, with many of them being really old. I've started marking as DISCONTINUED (in the description) some of these projects: - GNOME:STABLE:2.x - GNOME:STABLE:{3.0,3.2,3.4} - GNOME:Backports:2.x - GNOME:Community (superseded with GNOME:Apps, really) At the same time, I'm removing all maintainers and only leaving the gnome-maintainers group (to avoid people changing packages in these projects, but still have a group who can jump in if really needed) and disabling build on Factory when it was still there. I'm planning to do the same for the following projects which have not been active in a long time, so please shout fast (within a week) if you don't want this: - GNOME:Apps:F-Spot - GNOME:Apps:F-Spot:Unstable - GNOME:Apps:Tasque - GNOME:Apps:Tomboy - GNOME:Apps:Tomboy:Unstable - GNOME:Ayatana:11.4 - GNOME:Ayatana:deprecated - GNOME:Evolution and GNOME:Evolution:* - GNOME:GNOME1 Note that I'm not removing any package, nor dropping any repository. So all of this should be revertable. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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] [reminder] openSUSE 13.1 Milestone 2 is next week
by openSUSE Roadmap Reminder 05 Jun '13

05 Jun '13

Hello all, openSUSE 13.1 Milestone 2 will be released next week, on Thursday 13 June 2013. Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday. For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap Thanks, -- openSUSE Roadmap Reminder -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0