August 2009 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Patch0 versus %patch
by Michael Schroeder 26 Aug '09

26 Aug '09

Hi packaging folks, FYI: rpm-4.7 complains if the Patch tag doesn't match the %patch call, i.e. if you use Patch0/%patch or Patch/%patch0. I've fixed and submitted all Factory packages where this was a problem. So don't be alarmed ;-) Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] ANNOUNCE: changing the role of pre_checkin.sh
by Stephan Kulow 25 Aug '09

25 Aug '09

Hi, We just had a little discussion about one little detail of our checkins and I would like to announce the result: - we will no longer call pre_checkin.sh while accepting, it has to be called by the packager _before_ submit (pre checkin basically :) This has two reasons: 1. be less suprising if accepting changes spec file texts - especially for people new to packaing this proved to be a factor 2. avoid one more risk of our infrastructure by malformed scripts (the more important reason) - osc commit will (later) call the script before transfering to the server, so you also have more freedom in what you call in that script, it only has to be on your computer [as long as you can live without co-maintainers] Unrelated to this I would like to remind everyone that every extra script and data file needs to be listed as Source in the .spec file. The change is not yet active, but please stop relying on others calling pre_checkin.sh now. Thanks, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Libs Dev?
by Sascha 'saigkill' Manns 25 Aug '09

25 Aug '09

Hello Mates, i'm trying to port an Program to openSUSE: Have we an Place similar to /usr/share/libs/dev? I don't heard that place before... -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

[opensuse-packaging] need help with bugzilla 3.4.1 .spec file
by doiggl＠velocitynet.com.au 25 Aug '09

25 Aug '09

Hello, I am trying to compile the bugzilla 3.4.1x series The last compile attempt shows these errors. warning: group apache does not exist - using root ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist bugzilla-doc-build-3.4.1-24.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs bugzilla-doc-3.4.1-24.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs bugzilla: "/etc/httpd/conf.d/bugzilla.conf" is not allowed anymore in SuSE Linux. bugzilla-3.4.1-24.1.noarch.rpm: directories not owned by a package: - /etc/httpd - /etc/httpd/conf.d - /usr/share/bugzilla/extensions - /usr/share/bugzilla/lib System halted. So far I added in to the specfile 1. Fix warning 'warning: group apache does not exist - using root' BuildRequires: pwdutils , apache2-devel Requires: apache2 %{apache_mmn} %pre id apache >/dev/null 2>&1 if [ $? -ne 0 ]; then /usr/sbin/groupadd apache /usr/sbin/useradd -r -d %{_libdir}/%{name} -c "apache id" apache fi 2. set ownership as directories not owned by a package /usr/share/bugzilla/extensions /usr/share/bugzilla/lib /usr/share/bugzilla/docs Set to in %files section. Question: Is this the correct syntax to use ? %{buildroot}/usr/share/bugzilla/extensions %{buildroot}/usr/share/bugzilla/lib %{buildroot}/usr/share/bugzilla/docs 3. What should be done with these entries as they are directories not owned by a package ? - /etc/httpd - /etc/httpd/conf.d 4. How can this line be fixed, where should the file be moved to ? bugzilla: "/etc/httpd/conf.d/bugzilla.conf" is not allowed anymore in SuSE Linux Specfile -> https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=Bug… Last log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=Bugzi… Any help appreciated. Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 8

[opensuse-packaging] new package: python-psycopg2
by Jon Nelson 25 Aug '09

25 Aug '09

I have in my home:jnelson-suse project a ready-to-go package: python-psycopg2 I'd like to get it in to Factory, but the first step is to use submitreq. I'm not sure which devel project to submit it to, however, therefore I would like some suggestions, please! -- Jon -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] Status update on Action Item: Screencast about the collaboration features of the BS
by Andreas Jaeger 24 Aug '09

24 Aug '09

Quite some time ago during one of the openSUSE project meetings, an AI was created to do a screencast about the collaboration features of the BuildService (https://bugzilla.novell.com/show_bug.cgi?id=397053) Those people that wanted to do it, did not have time - and I have not found any other volunteer. So, I've marked this now as WONTFIX - but on the other hand, this is something that I still think makes sense. We do need good documentation on how to build packages together and get them into factory. If anybody is interested to work on such documentation, I would appreciate it and I'll promise to review anything and get questions answered. Anybody interested? Andreas -- Andreas Jaeger, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 3

[opensuse-packaging] spec-cleaner script
by Vincent Untz 21 Aug '09

21 Aug '09

Hi all, I wrote a spec-cleaner script yesterday, with the goal to, hrm, well, clean spec files ;-) My main goal was mainly to have something that I could use to make it easier to review the moblin packages, but I think it can be useful for other people. You can find it at http://gitorious.org/opensuse/spec-cleaner It's certainly broken in many interesting ways, but for packages that are not too complex, it should work relatively well. Note that it uses some "spec style" that is close to what we use in the GNOME team. So feel free to play with it and report any issue you find! Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 3

[opensuse-packaging] Packages that need a new maintainer
by Stefan Seyfried 21 Aug '09

21 Aug '09

Hi, some of my packages are urgently in need o fa loving hand. Some already have found a new home, but those probably also can benefit from a helpful co-maintainer. Some are not very useful IMHO and good candidates for dropping, but maybe someone thinks differently and wants to maintain them. Here we go: Package | drop? |Notes -------------|----------|------------------------------------------------ acpid | probably | low maintenance effort brlemu | no | very low effort comgt | yes | not really useful anymore cpufrequtils | yes | not really needed libdaemon | no | ifplugd needs this. low effort ifplugd | no | network without NM needs this, low effort kqemu-kmp | yes | everybody has VT capable processors anyway ;) laptop-mode-tools | no | leafnode | yes | anybody using this? not me. Low effort, though libebml | yes | needed by mkvtoolnix libmatroska | yes | needed by mkvtoolnix mkvtoolnix | yes | easy to maintain, but I don't use it libsynaptics | yes libx86 | no | needed by suspend and vbetool mailsync | yes | anybody using this? ozerocdoff | yes | the kernel now should do this AFAIK pm-utils | no | need some amount of love to sync with upstream radeontool | yes | nobody should use it anyway rovclock | yes | see radeontool suspend | no | needed for s2ram, s2disk tuxcursors | yes | but I'll keep them in my home project ;) umtsmon | no | should be obsoleted by NM since years usb_modeswitch | yes | see ozerocdoff vbetool | yes | see radeontool Those have already found new maintainers, but surely could benefit from active co-maintainership: (maintained by Vladimir Botka, vbotka): bluez | no | active upstream, but easy to maintain bluez-firmware | no | see bluez bluez-hcidump | no | see bluez-firmware (maintained by Matthias Hopf, mopf) lablgtk2 | no | needed by unison, needs some packaging cleanup unison | no | useful, not too much effort Thanks, seife -- Stefan Seyfried R&D Preload Department | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." This footer brought to you by insane German lawmakers: SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 14

[opensuse-packaging] Development of .spec files
by doiggl＠velocitynet.com.au 21 Aug '09

21 Aug '09

Hello, Would this tool assist people on the creation of .spec files ?. http://wiki.eclipse.org/Linux_Tools_Project/SpecfileEditor/User_Guide The Specfile Editor plug-in provides a wizard for creating new .spec files too. Cheers Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Packagers Section in Weekly News
by Sascha 'saigkill' Manns 20 Aug '09

20 Aug '09

Hello Mates, today i got an interesting Idea in our Weekly News Survey. An User asks for an own Packaging Section. He mean that that is an place for Packagers to announce fixed Packages (with an Bugzilla Reference). So the Weekly News Format is maybe: * Bugzilla-Number and Summary * Package and Version * Date and Packager * Free Text: What is changed. (Short Issue). Exists interesting about that Idea? Would Packager like to announce through the Weekly News? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 5