March 2010 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Directories for message catalogs
by Philipp Thomas 25 Mar '10

25 Mar '10

for a package of mine I get filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/bg_BG/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ca_ES(a)valencia/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/cs_CZ/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/da_DK/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/et_EE/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/eu_ES/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/fi_FI/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/fr_CA/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/gl_ES/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/he_IL/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/hu_HU/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/id_ID/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ja_JP/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/km_KH/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ko_KR/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/lt_LT/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/lv_LV/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/mk_MK/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/nb_NO/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/nn_NO/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/pl_PL/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/pt_PT/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ro_RO/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/sk_SK/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/sl_SI/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/th_TH/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/uk_UA/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/vi_VN/LC_MESSAGES/filezilla.mo from rpmlint. Could somebody please tell me where a list of the correct directories exists? Philipp -- 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] Push iPhone/iPod Touch Support Library into Factory for openSUSE 11.3
by Martin S. 24 Mar '10

24 Mar '10

Hi, I was approached by Vincent Untz as I am the maintainer of libimobiledevice to push the library into openSUSE:Factory. Further information about the library is available here: http://www.libimobiledevice.org/ Currently confirmed is that Ubuntu, Fedora and Mandriva feature the stack in their next releases and it would be nice if openSUSE 11.3 would not be left behind. Especially since I am maintaining the packages in my OBS project home:FunkyM:iphone since the early beginnings of the library. Required new (source) packages are: - usbmuxd - libplist - libimobiledevice - ifuse This would enable libgpod4 (music/video sync) and GNOME's GVFS (filesystem access) to build with iPhone/iPod Touch support and would be a nice gain for marketing. Rhythmbox, latest Amarok and GTKPod use libgpod and thus will work, too. The question left is into which project to push the stack alongside the related libraries and how to get it into factory. Looking forward to your feedback. --- Martin S. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 3

[opensuse-packaging] have choice for perl(Error) needed by perl-Mail-SPF: perl-Error git-core
by Christian 21 Mar '10

21 Mar '10

Hi, I get this expansion error in devel:languages:perl. When I search for "git-core" I do not get any reasonable result. Download_repositories <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> *git-core* <https://build.opensuse.org/package/show?package=git-core&project=Ports%3ADe…> (project Ports:DebianBased:Auto <https://build.opensuse.org/project/show?project=Ports%3ADebianBased%3AAuto>) [goto download repositories] <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> 36 fast, scalable, distributed revision control system Git is popular version control system designed to handle very large projects with speed and efficiency; it is used mainly for various open source ... Download_repositories <http://download.opensuse.org/repositories/home:/voronov84/> *git-core* <https://build.opensuse.org/package/show?package=git-core&project=home%3Avor…> (project home:voronov84 <https://build.opensuse.org/project/show?project=home%3Avoronov84>) [goto download repositories] <http://download.opensuse.org/repositories/home:/voronov84/> 36 git - stupid content tracker package /<no description>/ Download_repositories <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> *devscripts* <https://build.opensuse.org/package/show?package=devscripts&project=Ports%3A…> (project Ports:DebianBased:Auto <https://build.opensuse.org/project/show?project=Ports%3ADebianBased%3AAuto>) [goto download repositories] <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> 4 scripts to make the life of a Debian Package maintainer easier ...t] - debcommit: commit changes to cvs, svn, svk, tla, bzr, git, or hg, basing commit message on changelog [cvs | subversion | svk | tla | bzr | *git-core* | mercurial] - debdiff: compare two versions of a Debian package to check for added and removed files [wdiff, patchutils] - debi: install a just... I don't think any of these is inluded for build to d:l:p. But perhaps someone knows what to do and how to fix it. To get packages build I did a workaround in prjconf "Prefer: perl-Error" Thanks for help Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] binary is linked against libraries in /usr/ or /opt
by Sascha 'saigkill' Manns 20 Mar '10

20 Mar '10

Hello Mates, today i've tried to build tuxcmd (home:saigkill). The Package builds to the brp-check brp-rootfs with the Issue: http://pastebin.ca/1846034 Does anyone know, how to fix this? Have a nice evening... -- Sincerely yours Sascha Manns openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 7

[opensuse-packaging] fixing an empty RPM
by doiggl＠velocitynet.com.au 20 Mar '10

20 Mar '10

Hello, A rpm I am building on opensuse build service looks like it builds the modules as i see a directory structure with files, but at the end the log says :- ... 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: An empty RPM is not allowed anymore in SuSE Linux Question: Is it the filelist that needs fixing here, if so how can it be populated ? Project -> https://build.opensuse.org/package/show?package=bugzillatest&project=home%3… Spec -> https://build.opensuse.org/package/view_file?file=bugzillatest.spec&package… Last build log -> https://build.opensuse.org/package/rawlog?arch=x86_64&package=bugzillatest&… Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5

Re: [opensuse-packaging] binary is linked against libraries in /usr/ or /opt
by Sascha 'saigkill' Manns 19 Mar '10

19 Mar '10

Am Freitag, 19. März 2010 21:56:00 you wrote: > Hi Sascha, > > On Fri, 19 Mar 2010, Sascha 'saigkill' Manns wrote: > > today i've tried to build tuxcmd (home:saigkill). The Package > > builds to the brp-check brp-rootfs with the Issue: > > http://pastebin.ca/1846034 > > > > Does anyone know, how to fix this? > > Easy Rule: if a program (binary or script) uses libs or other > programs from the /usr/... hierarchy, the program also resides in > the /usr/... hierarchy, usually /usr/bin /usr/sbin /usr/local/bin > /usr/local/sbin or /opt. I've checked the Makefile: http://pastebin.ca/1846119 . The Path are set to: DEFAULT_DESTDIR=/usr And inside the install Section: $(INSTALL) -d $(DESTDIR)/bin $(INSTALL) -m 755 tuxcmd $(DESTDIR)/bin $(INSTALL) -d $(DESTDIR)/lib$(LIB_SUFFIX)/tuxcmd In my view this looks right... Binary in /usr/bin and Libs in /usr/lib(64). -- Sincerely yours Sascha Manns openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] binary is linked against libraries in /usr/ or /opt
by Sascha 'saigkill' Manns 19 Mar '10

19 Mar '10

Am Freitag, 19. März 2010 21:56:00 you wrote: > Hi Sascha, > > On Fri, 19 Mar 2010, Sascha 'saigkill' Manns wrote: > > today i've tried to build tuxcmd (home:saigkill). The Package > > builds to the brp-check brp-rootfs with the Issue: > > http://pastebin.ca/1846034 > > > > Does anyone know, how to fix this? > > Easy Rule: if a program (binary or script) uses libs or other > programs from the /usr/... hierarchy, the program also resides in > the /usr/... hierarchy, usually /usr/bin /usr/sbin /usr/local/bin > /usr/local/sbin or /opt. > > In this case your build tries to install 'tuxcmd' in /bin, this can > not be allowed because all the libs it links against are under > /usr/... Aaah, sure. That i haven't noticed. Thanks for clarifying :-) -- Sincerely yours Sascha Manns openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) -- 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] noarch perl packages
by Ludwig Nussel 19 Mar '10

19 Mar '10

Hi, Many pure perl packages are not noarch just because of that .packlist file in %perl_vendorarch. Is that file good for anything in an rpm managed system? Ie could it be savely omitted from packages? 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

3 3

[opensuse-packaging] compiler / devel files in package
by Dominique Leuenberger 19 Mar '10

19 Mar '10

Good day everybody, Today I have a question regarding the packaging policy. i'm building the package orc (which is the successor of liboil). now, orc is a compiler, called orcc and a bunch of libraries. The libraries are split in a package according shlib (no problem there). The binary orcc would be in the main package and the -doc contains the extensive documentation. now the question is mainly with focus on the development headers: Should those really be split in a -devel package? As I see it so far pretty much every package that will require orc compiler will need access to the specific headers (but who know, this might change). The -devel package without the compiler itself is rather useless too I think. What are your suggestions? 1) Having the devel files in the main package and make rpmlint quiet ? b) Move orcc to the -devel package? If I look at gcc45 for example this contains a list of header files as well, so I'm very much inclined to do the same for orc (so option a). Any comments / suggestions / recommendations / objections / [...]ions ? Dominique -- 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] apparmor help
by Peter Czanik 17 Mar '10

17 Mar '10

Hello, I'm working on upgrading syslog-ng from 2.0 to 3.0. My packages are available at http://download.opensuse.org/repositories/home:/czanik/openSUSE_11.2/ The current syslog-ng profile at /etc/apparmor.d/syslog-ng is for syslog-ng 2.0 and does not work for syslog-ng 3.0. I get: Mar 17 10:46:19 bigone112 syslog-ng[455]: Error opening control socket, bind() failed; socket='/var/run/syslog-ng.ctl', error='Address already in use (98)' First of all: is there anybody, who could help me to fix the apparmor profile? And of course I also have a packaging question: The apparmor profile file is not owned by syslog-ng, but by apparmor-profiles: bigone112:~ # rpm -qf /etc/apparmor.d/sbin.syslog-ng apparmor-profiles-2.3-50.2.noarch What is the proper way of packaging a new /etc/apparmor/sbin.syslog-ng, if I want to provide syslog-ng packages for 11.1, 11.2 and factory? Bye, CzP -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4