openSUSE Packaging July 2008

packaging@lists.opensuse.org

22 participants
11 discussions

[opensuse-packaging] Kbuild w/ configure... Chicken and egg problem?
by Ann Davis 30 Jul '08

30 Jul '08

Hi, I have a KMP build structure as follows: sample.spec sample/ Kbuild samplemod1 configure *.c and *.h files samplemod2 configure *.c and *.h files My problem is that my Kbuild file has to specify the object files to use, but I don't know the object files until I run the configure command. And I want to run the configure command as part of %build. Any thoughts on how to do this? Note: it seems to work if I am willing to have my samplemod1.ko and samplemod2.ko files wind up in samplemod1/ and samplemod2/, respectively. For that I can just have my Kbuild file look like this: obj-m += samplemod1/ samplemod2/ But I want samplemod1.ko and samplemod2.ko to wind up in /sample. So I do the following: obj-m += samplemod1.o samplemod2.o samplemod1-objs := samplemod1/ samplemod2-objs := samplemod2/ This does not work... it seems that the *-objs lines will not accept a directory but instead require an explicit list of object files to be linked. Hence my problem. TIA for any ideas. Ann --------------------------------------------------------------------- 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] bin 9.5.0P1-5.1 for older suse
by Andre Hübner 30 Jul '08

30 Jul '08

Hi, i do have a really practical question. For security reasons i try to package newest bind for old suse 8.2 Yes, i know suse 8.2 is really old, we have also newer machines, but i cannot convince my boss of removing them. What i did is to look at http://software.opensuse.org/search for src-rpm version suse 10.2 which is nearest to suse 8.2 ;) http://download.opensuse.org/repositories/server:/dns/openSUSE_10.2/src/bin… I unrpmed all and did some changes to spec-file to make it work for suse 8.2 And thats the point. it is compiling and packaging but installing wont work by failed dependencies: error: failed dependencies: libbind9.40 is needed by bind-9.5.0P1-5.1 libdns.43 is needed by bind-9.5.0P1-5.1 libisc.41 is needed by bind-9.5.0P1-5.1 libisccc.40 is needed by bind-9.5.0P1-5.1 libisccfg.40 is needed by bind-9.5.0P1-5.1 liblwres.40 is needed by bind-9.5.0P1-5.1 libbind9.40 is needed by bind-utils-9.5.0P1-5.1 libdns.43 is needed by bind-utils-9.5.0P1-5.1 libisc.41 is needed by bind-utils-9.5.0P1-5.1 libisccc.40 is needed by bind-utils-9.5.0P1-5.1 libisccfg.40 is needed by bind-utils-9.5.0P1-5.1 liblwres.40 is needed by bind-utils-9.5.0P1-5.1 these libs are all included in bind-libs-9.5.0P1-5.1.i386.rpm which can be installed. the required libs can be found in /var/lib/ i checked the new packaged binaries with ldd and path for required libs is correct. i do not know what is going wrong. I know, its not the best way to downgrade spec-files, but i do not have a choice... Can someone give a hint to solve my problem Thank you Andre --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 1

[opensuse-packaging] Don't overwrite highscore file on update
by Christian Morales Vega 28 Jul '08

28 Jul '08

I have packaged Tower Toppler in home:RedDwarf. If a /var/games/toppler/toppler.hsc file exists the game uses it to store highscores for all users, if doesn't exists it uses ~/.toppler/toppler.hsc. I use %verify(not size md5 mtime) %attr(-, root, games) %{_localstatedir}/games/%{name}/%{name}.hsc so any user in games group can use it and rpm -V doesn't complains. But when I update the package a new empty file is created that deletes previous highscores! What's the best way to package this file so old highscores aren't lost? And since I'm with this... - The binary should go to /usr/bin or /usr/games? There is any openSUSE official policy? - What are the plans for %suse_update_desktop_file? Should not desktop-file-install from freedesktop.org be enough? I have never fully understood how X-SuSE-translate is used. When you want to support other distros isn't funny to %if every package with a .desktop file. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] NEW: up-to-date OpenVZ kernels at 'Virtualization:OpenVZ' BS project
by Jean-Baptiste Giraudeau 25 Jul '08

25 Jul '08

Hello all of you, virtualization addicts! [reference] OpenVZ is container-based virtualization for Linux -> http://wiki.openvz.org/Main_Page [/reference] It's been quite a while since any OpenVZ kernel package shows up on the Build Service. SLES10 2.6.16 kernel is still maintain by the OpenVZ team but openSUSE users had it hard getting newer OpenVZ kernel running without giving up on Suse kernel configuration and patches. So here comes the new 'Virtualization:OpenVZ' project hosted on BS. It aims at providing recent openvz kernel builds while being as close as possible to the original Suse kernel ABIs and default configurations. Some trade-offs had to be made though. Most notably, Apparmor patches could not accommodate with OpenVZ ones. I suspect this would take a significant amount of work and testing to get them both. Two OpenVZ kernels has been packaged: - 2.6.24 -> Virtualization:OpenVZ:STABLE sub-project, available repositories : SLE_10, openSUSE_10.3 and openSUSE_11.0. - 2.6.26 git -> Virtualization:OpenVZ:HEAD sub-project, available repositories : openSUSE_11.0 and openSUSE_Factory. Appropriate administration tools are included in each repository. Packages are: kernel-ovz-default, kernel-ovz-pae, kernel-ovz-debug vzctl, vzquota, linux-kernel-headers, kernel-ovz-source. OpenVZ requires templates to create containers. You can find some of them at http://wiki.openvz.org/Download/template/precreated or create one yourself (search openvz wiki). I will soon add an openSuse 11.0 template in the 'Virtualization:OpenVZ' repository. Also you need IPv6 enabled (use Yast) to load required openvz kernel modules. Last but not least, please consider those packages at beta stage. Comments/bug reports are greatly appreciated. Especially I would be grateful to any experienced kernel packager who would have a look at Virtualization:OpenVZ:HEAD/kernel-source and the set of diff applied to Kernel:HEAD/kernel-source and tell me if I did commit any 'spec file blasphemy'. Project homepages: http://build.opensuse.org/project/show?project=Virtualization:OpenVZ http://build.opensuse.org/project/show?project=Virtualization:OpenVZ:STABLE http://build.opensuse.org/project/show?project=Virtualization:OpenVZ:HEAD have a lot of fun! -Jb. G --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 11

[opensuse-packaging] some "interesting" rpmlint warnings
by Christian Boltz 24 Jul '08

24 Jul '08

Hello, I found some "interesting" rpmlint warnings with my package "patch2mail" in home:cboltz. patch2mail.noarch: W: explicit-lib-dependency libxslt You must let rpm find the library dependencies by itself. Do not put unneeded explicit Requires: tags. I tested without libxslt in Requires:, but it is _not_ autodetected that it is needed. (The patch2mail script calls xsltproc.) patch2mail.noarch: W: missing-dependency-to-cron for logrotate script /etc/cron.daily/patch2mail This package installs a file in /etc/logrotate.d/ or in /etc/cron.*/ but doesn't require cron to be installed. as cron is not part of the essential packages, your package should explicitely require cron to make sure that your logrotate or cron job is executed. Hmm, what's wrong with my Requires: line? It already includes cron... Requires: bash mktemp mail grep zypper coreutils net-tools cron libxslt Should I simply ignore these warnings or are this bugs in rpmlint? BTW: Does the buildservice read the rpm changelog from patch2mail.changes or do I have to include it in the spec directly? Regards, Christian Boltz -- Hmm, wenn Du von CD aus Dein Linux-System booten kannst, dann scheint vielleicht Dein MBR gerade Urlaub zu machen ;-) [Martin Mewes in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

9 17

[opensuse-packaging] Packages renames
by Stephan Kulow 20 Jul '08

20 Jul '08

Hi, Yesterday I learned something new and I think, so will you now: most of us (including me) did package renames the wrong way and the documentation in the wiki on it is unfortunately not very clear. So let me get this straight and I hope everyone will use it correctly from now on: oldpac.spec: Name: oldpac Version: 1.0 baselibs.conf: oldpac You want to rename it to newpac on update, what do you have to do? newpac.spec: Name: newpac Version: 1.1 Provides: oldpac <= 1.0 Obsoletes: oldpac <= 1.0 baselibs.conf: newpac obsoletes "oldpac-<targettype> <= 1.0" provides "oldpac-<targettype> <= 1.0" That's it - please always use <= with the latest version oldpac had, everything else is most likely wrong. And don't forget about the baselibs. Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

15 35

[opensuse-packaging] where to open a bug report of packman repo?
by Gabriel 16 Jul '08

16 Jul '08

Where can I report an "issue/feature" regarding a package of the packman repository? The problem is with k3b, it has kdebase as dependency (witch is really unnecessary). You see, I'm using gnome and don't want to install kdebase because it install a bunch of app that I don't need. k3b works perfectly without kdebase, so I want to ask to remove this dependency. -- Kind Regards --------------------------------------------------------------------- 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] Procinfo-NG 2.0.196 released.
by tabris 13 Jul '08

13 Jul '08

Procinfo-NG is a rewrite of the old Procinfo program, updated to work properly on 32bit and 64bit versions of Linux (tested on x86 and x86_64), with the following goals: * Code easier to maintain/read. * Restore old broken features that haven't worked since 2.2 or 2.4 * Add new features where found useful. * Eliminate useless features such as output of /proc/modules and /proc/filesystems. https://sourceforge.net/project/showfiles.php?group_id=195336 * Add network bandwidth statistics * Add 'human' numbers to memory stats. commandline-option -H * Lots of code updates/reorganizations * "real" Memory stats were misaligned, and thus made very little sense. * Update IRQ stats to work with kernel 2.6.23 * Use ncurses to handle terminal/keyboard. * readFile now uses a dynamic line-buffer, and some more of the C++ file-I/O code. * Fix a heap leak. * fixup some column-widths * prettyPrint improvements * Numerous other changes and bugfixes.

2 2

[opensuse-packaging] Motion detection software.
by Erik Jakobsen 10 Jul '08

10 Jul '08

Hi. I'm a member of the Motion mailinglist, and had the idea -along with other on the list included the developers- that it would be a nice idea, to implement the Motion detection software in openSUSE too. It's already included with other linux os'es, and I wonder why it's not already in openSUSE, that I have used since very many years. For information here's a URL: http://www.lavrsen.dk/twiki/bin/view/Motion/ >From /Adrian Schroeter I got this. / Everybody can package it via the build service, check http://build.opensuse.org for this :) Or ask someone on the opensuse-packaging mailing list to do so. I now ask if there's a person, that can/will do the work? Sincerelly Erik Jakobsen --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

Re: [opensuse-packaging] where to open a bug report of packman repo?
by Gabriel 06 Jul '08

06 Jul '08

On Sat, Jul 5, 2008 at 7:45 PM, Pascal Bleser <pascal.bleser(a)opensuse.org> wrote: > Send an email to packman(a)links2linux.de > (no need to subscribe, already CC'd for this mail) I'll have it in mind. > Incidentally, I'm one of the k3b package maintainers @packman so... ;) :-) > > Note that bug 114320 says otherwise: > https://bugzilla.novell.com/show_bug.cgi?id=114320 > > I don't know for which openSUSE versions it is still applicable though. > > The k3b package in Factory still contains the following: > %if %suse_version >1030 > Requires: suse_help_viewer kdebase3-runtime > %else > Requires: kdebase3 > > I'm going to fix the k3b package @packman to use that (as above) instead > of just "Requires: kdebase3" as we have now. > (will be fixed in k3b-1.0.5-0.pm.5) > Perfect then. Kind Regards. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging July 2008