openSUSE Packaging October 2006

packaging@lists.opensuse.org

25 participants
17 discussions

Re: [opensuse-packaging] Updates of packages (right numbering scheme?)

by Dominique Leuenberger

>>> Marcus Meissner <meissner(a)suse.de> 18-10-2006 14:24 >>> On Wed, Oct 18, 2006 at 01:26:30PM +0200, Dominique Leuenberger wrote: > Hi, > > I have created packages for SuperTuxKart 0.2rc2 and then for > SuperTuxKart 0.2 (obsoleteing 0.2rc2) (only home: repo up to now) > > RUG and other tools don't recognize 0.2 being newer as 0.2rc2 > > What suggestion can you give me for future Numbering schemes of > RC-Releases? > >The upstream project should do so... > >0.1.99rc2 I would have used for the RC ;) Thanks Marcus, I'll get in touch with the upstream maintainers for this. Hopefully for the next release, it will be adopted. Would 0.2.0 be treated newer as 0.2rc2? Dominique

15 years, 8 months

[opensuse-packaging] Updates of packages (right numbering scheme?)

by Dominique Leuenberger

Hi, I have created packages for SuperTuxKart 0.2rc2 and then for SuperTuxKart 0.2 (obsoleteing 0.2rc2) (only home: repo up to now) RUG and other tools don't recognize 0.2 being newer as 0.2rc2 What suggestion can you give me for future Numbering schemes of RC-Releases? Thanks for an advise, Dominique

15 years, 8 months

[opensuse-packaging] brasero ?

by Pascal Bleser

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone already packaging "brasero" (used to be named "bonfire") ? http://gnomefiles.org/app.php/Brasero - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFMRwpr3NMWliFcXcRApPZAJ95NbTLEsZCOXwSDtDPXIxHFoDMlACfTUwv cLgiob0PcntpIpnjKyXVRXE= =aItd -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

15 years, 8 months

[opensuse-packaging] question on packaging and gconf failures

by Rauch Christian

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List, today I packaged the newly released Gnucash 2.0.2, but it failed this time, whereas 2.0.1 worked just fine. The following error caused the build (or better make install) to stop: > mkdir -p /var/tmp/gnucash-compiler/etc/gconf/gconf.xml.defaults > GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults > /opt/gnome/bin/gconftool-2 --makefile-install-rule > apps_gnucash_history.schemas > Failed to load source "xml::/etc/gconf/gconf.xml.defaults": Failed: > Could not make directory `/etc/gconf/gconf.xml.defaults': No such file > or directory After asking back on gnucash-devel, this issue could be resolved by adding the following line just before "%__make install DESTDIR=%{buildroot}" > export GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 According to http://www.gnome.org/projects/gconf/ (Section Application developer information), this is known and they tell a workaround there. Is this the established way to workaround this or is there a "suse way" to do this? Thanks, Christian Rauch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFKj20ayhvFxrDZlkRApjmAJ9VwD/S5i58FFLSez2TUN8z1fe3VgCdEi8S UeYuGMMXSlmk3zRkoA0dF34= =bMbt -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

15 years, 8 months

[opensuse-packaging] Packaging kernel module with conflicting file

by Mauricio Teixeira (netmask)

Is there a way I can build a package which would install a new kernel module that already exists on the kernel-default package? AFAIK, the packages would conflict with an error telling that the file already exists. Anyone know a solution for that? LKM maybe? I wish to build a package with the prebuilt module so that the user doesn't need to build it by himself. TIA -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

15 years, 8 months

[opensuse-packaging] Gnome/KDE Path

by Andreas Schneider

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, what will be the Gnome and KDE path in openSUSE 10.2? Bye, -- andreas - -- http://www.cynapses.org/ - cybernetic synapses -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE8wMlf94+j/M+P8YRAnH4AKCUITnaSxeCyFQLLzmnLcSHuxMgEwCcDqk0 MtgbCS2WdDguDrYPd6sTGw0= =KUH4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

15 years, 8 months

[opensuse-packaging] Differencies between tools?

by Anders Norrbring

I've been thinking a little.. What's the differencies between building packages with y2pmbuild and build? I'd like the best of the worlds.. I'd like to build several architectures in one run (build), but I'd also like to have the packages signed and dumped to the repositary I'm building. One problem is that it appears as the rpm's doesn't get signed.. I have to dig into that a bit more, I'm setting some traps in the y2pmbuild script to see if I can find something out.. I guess a script running 'y2pmbuild-10.1' and then 'linux32 y2pmbuild' would do the trick, but I'd like to know which exit codes y2pmbuild generates for failure and success. -- Anders Norrbring Norrbring Consulting

15 years, 8 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging October 2006