openSUSE Packaging January 2009

packaging@lists.opensuse.org

43 participants
33 discussions

[opensuse-packaging] Please do not bypass the devel projects

by Vincent Untz

Hi, We just got 7 packages in GNOME:Factory that broke because the project.diff files don't apply anymore: the packages were all updated in Factory. It's not the first time it happens, and I'm sure each time it happens, the person doesn't think it will break anything. But sometimes it does :/ Don't get me wrong: I'm really happy to see people contributing to the packages the GNOME team maintains, and especially when it comes to cleaning up things -- it makes the world a better place. But it'd be really nice to submit all updates to GNOME:Factory first. I think Mozilla:Factory was hit by this issue in the past too, and I'd guess other projects too. So, please, think about the pain that people feel when they have to handle those manual merges, and use the devel projects. Thanks, 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

11 years, 9 months

[opensuse-packaging] Desktop categories: mismatch in brp-desktop and rpmlint

by Michal Vyskocil

Hi, I have a problem with a desktop file. The upstream one has Categories=Application;AudioVideo; but brp-desktop stops the build with Insufficient Category. ERROR: No sufficient Category definition: /var/tmp/playitslowly-1.1.0- build//usr/share/applications/playitslowly.desktop Errors in installed desktop file detected. Please mail stbinner(a)suse.de, if you think this is wrong. error: Bad exit status from /var/tmp/rpm-tmp.79930 (%install) So I changed it according SUSE Packaging Conventions [1] to Categories=Multimedia;Player;AudioVideo;AudioVideoPlayer; but now I got a rpmlint warning: playitslowly.x86_64: W: invalid-desktopfile /usr/share/applications/playitslowly.desktop value "Multimedia;Player;AudioVideo;AudioVideoPlayer;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Multimedia"; values extending the format should start with "X-" /tmp/playitslowly-1.1.0-1.x86_64.rpm.23739/usr/share/applications/playitslowly.desktop: .desktop file is not valid, check with desktop-file-validate So what should be in Categories which will pass brp-desktop and rpmlint checks? And is there any reason why we have a double check of the same thing? [1] http://en.opensuse.org/SUSE_Package_Conventions/Desktop_Menu#9.4.6._Multime… Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 9 months

[opensuse-packaging] Changelog policy

by Magnus Boman

Hello, I've noticed that a lot of packages going in to Factory does not have "proper" Changelog entries as explained to me (ie, copy redundant information from NEWS/Changelog entries upstream and put it in <packagename>.changes). My question is, do we have a project wide policy for this, or would it be enough to add what has been done by the package updater (ie, update to version x.y.z, add/remove patch etc)? Personally, I am in favor of not having to put it what changed upstream, since in most cases, this would be contained in a NEWS/Changelog file anyway. Thanks, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 10 months

[opensuse-packaging] Who should own a directory that is used by many packages?

by Vincent Untz

Hi, In the GNOME world, we have a few directories that are used by quite a few packages to put some files. Two examples are /usr/share/gnome/help /usr/share/gtk-doc The thing is that the first one is "owned" by libgnome and the second one is owned by gtk-doc. However, now, many packages don't need libgnome and still put files in /usr/share/gnome/help and it's bad to require the gtk-doc package at runtime only to have /usr/share/gtk-doc existing. So, how can we handle this case? Should we create some package like the filesystem one that would contain the common directories for GNOME stuff? Is it okay to add GNOME-related directories to the filesystem package? Or should we just be happy with having all packages owning a part of those directories? Thanks, 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

11 years, 10 months

[opensuse-packaging] Could someone please fix snort?

by Low Kian Seong

Dear powers that be, The package snort that is in the community repository has a problem with the init script. It doesn't work and errors out. The fix is here : http://www.kriyayoga.com/love_blog/post.php/1067 Could someone that have access please fix the problem? Thanks. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 10 months

[opensuse-packaging] packages for sale, get yours for free !

by Cristian Rodríguez

The following packages are looking for new maintainer - libical - cvsps I also accept package interchanges ;-) -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Software Developer Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/

11 years, 10 months

[opensuse-packaging] new dbus policy rpmlint check in Factory

by Ludwig Nussel

Hi, The dbus package used a too permissive configuration in the past which led to security problems (CVE-2008-4311). During investigation of that problem it was found that many packages install dbus configuration files that contain useless settings, settings that harm other services or settings that even break after the dbus security update. Therefore I've written an rpmlint check that warns about such flaws. The check 'dbus-policy-missing-allow' will abort the build though. If you encounter that error you need to fix your dbus policy as the package will break (ie the service it offers via dbus won't work) after a dbus with the restrictive config gets checked in. A minimal config for a service that uses PolicyKit for access control typically looks like this: <busconfig> <policy user="someuser"> <allow own="org.foo.bar"/> </policy> <policy context="default"> <allow send_destination="org.foo.bar"/> </policy> </busconfig> cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 10 months

[opensuse-packaging] no-spec-file

by Sascha 'saigkill' Manns

Hello List, i've read one error, and i don't understand him. RPMLINT says to me: "no-spec-file". But i have used a Specfile to build the Package. Anyone knows the Error Message? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 10 months

[opensuse-packaging] unstripped binary or object

by Sascha 'saigkill' Manns

Hello, i have an question about the RPMLINT Error "unstripped binary or object". The Project is home:saigkill Package: mountmanager. I tried: find $RPM_BUILD_ROOT%{_libdir}/mountmanager/plugins -type f $ -name '*.so' -o -name '*.so.*' $ \ -exec chmod 755 {} \; but the same error. Has anyone ideas? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 10 months

[opensuse-packaging] Is it possible to edit a debian source package w/o using a debian system?

by Paul Elliott

Is it possible to do the following w/o using a debian system, that is on my opensuse development system: 1)Take an existing debian source package consisting of a)a pristine tarbal in .bz2 format b)a diff file c)a dsc file The above are known to build on debian development system. 2)Edit the source package with out a debian sytem, doing: a)slapping on a upgraded pristine tarbal, (new upstream source) b)edit the configure line in the rules file 3)Sending the resulting new debian source package to opensuse-buildservice to be built? Is this possible, or do I have to install a debian/ubuntu system to edit the debian source package? If it is possible, what are the steps of the procedure? Thank You. By the way, about a year and 1/2 ago I tried to build a ubuntu package using opensuse-buildservice, but it failed because the package had dependancies in the Universe, that opensuse-buildservice did not support the universe. Is this still a problem? Is there a workaround? Supporting the Universe sounds tiring . Even Atlas only tried to support the world. :-) -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

11 years, 10 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging January 2009