openSUSE Packaging January 2008

packaging@lists.opensuse.org

51 participants
34 discussions

[opensuse-packaging] Preview Xen 3.2 rc* packages

by Ian Jackson

Xen 3.2 is in the final stages of preparation. We (Xen upstream) are planning to provide binary packages for OpenSUSE 10.3, amongs others. I've merged the patches and so on from xen-3.1.0_15042-51.src.rpm with a recent xen-3.2-testing RC tip (16678:2491691e3e69). With a bit of effort I have managed to get a set of packages which appear to be able to work, in my simple `does this function at all' test, at least as well as the original packages (which aren't perfect IME). I'm mentioning it here so that you can have a look at what I've done and comment on it. We'll probably be making official upstream rpms very soon after the Xen 3.2 release, which we hope will be today. Please send me feedback either here on-list or privately. Most of the useful patches from xen-3.1.0_15042-51.src.rpm have been incorporated upstream so I just deleted those from my srpm. There were a number of other substantial changes, many of which I have just dropped as similar functionality has been included upstream or because they seemed to be irrelevant. I'm not particularly pleased with the resulting packages but I think something is probably better than nothing. You can find the actual files here: http://www.chiark.greenend.org.uk/~ijackson/xen-3.2-package-previews/opensu… These packages should not be used for production - they're previews and I may have made elementary packaging mistakes. Xen 3.2 is still unreleased and these packages were not made from the final release candidate in any case. Please check the SHA256's before installing them: 3d459ed17b074955c165d740145c7db423b28065b6f17f0b37d4b89fbce0516a xen-3.1.9-0xs.osuse10.i586.rpm b8953097234e39a636108945ff760bdee6eebf838d0fadcc1e7a6f3b743902a3 xen-debuginfo-3.1.9-0xs.osuse10.i586.rpm 1d0c2862b15d4dccfdc43864ebdeb47710f7026603f5f30e1097abb9c3ab3305 xen-devel-3.1.9-0xs.osuse10.i586.rpm 964d87a130d99a8e45e898bcdfafa042bcd69e702bf7f7ba223e677cc2cfed2e xen-doc-html-3.1.9-0xs.osuse10.i586.rpm 7a03031e6e59d0d601d2810021b9600863644d6664151f2494435b2edd228f64 xen-doc-pdf-3.1.9-0xs.osuse10.i586.rpm ccd9693ba71b36ae13b7b8ea1dcd74005bf3364715d2b901a01de491fb9b1235 xen-libs-3.1.9-0xs.osuse10.i586.rpm 2470d0a764ef2355e91b670994f19df549c1e0710dbc7823048a99c0b0780e99 xen-tools-3.1.9-0xs.osuse10.i586.rpm 7d8b9cf89eb1187755014114bc5a1db9dbcb601d32ad8df7bfa6ec8a61a0c95b xen-tools-domU-3.1.9-0xs.osuse10.i586.rpm 8856fb7d3582904d1b37cccd38519884f26baa562dc9d347bce392a6f6b7452f xen-tools-ioemu-3.1.9-0xs.osuse10.i586.rpm Regards, Ian. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 3 months

[opensuse-packaging] While updating purge translation-update

by Karl Eichwalder

https://bugzilla.novell.com/show_bug.cgi?id=353229 translation-update is already in use (for SLED 10) and we also want to make use of it for openSUSE. Thus the bug already exist. coolo wants me to open the discussion about this feature on the list. Here are the statements already posted: As part of bug 350693 we release "translation overrides" translation-update for 10.3. Package names are translation-update and as sub-packages translation-update-de, translation-update-es, translation-update-fi, translation-update-ja, and translation-update-pt_BR. In the past, we did something similar for SLE10 and SLE10 SP1 (more to come). At update time we must make sure to remove these packages. To make this happen, I'll add empty packages for 11.0 (and, if wanted for SLE11). Now we must find a way, that translation-update and the sub-package will always be available on the installation media (and in the patterns?). See Ladislav's comment in bug 350693#c2 : Date: Thu, 6 Dec 2007 15:15:53 +0100 From: Ladislav Michnovič Subject: Re: [opensuse-translation] translation-update 2007/12/6, Carlos E. R. <>: > The Thursday 2007-12-06 at 10:46 +0100, Karl Eichwalder wrote: > >> For LCN it would be harder, because the translations are distributed > >> in various packages. > > > > This could be done using the overload strategy with the shadow directory > > for the .mo files. We did those things for SLED10. The package name is > > translation-update. > > > > The tough part is to get rid of the package if you update from 10.3 to > > 11.0. > > Ouch. > > It has to be an optional package, with a warning to the user; and then try > to remind whoever does that in Yast development to remove the package on > upgrade... not a clean solution, it can backfire. I have an idea how to solve it. Create this package within Suse and do a proper numbering. For example 10.3.x.y, which shows, that it is connected to openSUSE Linux 10.3. Release translation updates as often as needed, but when next SuSE release comes, renumber it to 11.0.x.y and make this package empty. This package will come within installation media and it would be without any files, only README for some information. If somebody will do an update, YaST, zypper, rpm can handle this and will erase all files which was installed on the system by that package in previous version. One thing is needed, to make some dependency on some basic package or Pattern which will ensure, that this package will be always installed. Ask YaST2 maintainers for details. Regards Ladislav. Comments ------- Comment #1 From Lars Vogdt 2008-01-11 18:08:29 MST [reply] ------- Private Just my 2 cents: I don't think that this is the right way to go: I expect the translations in the "real" package resp. the package-lang file. And only these files should be updated if needed. So I vote that translations should go into the packages themselves so the package maintainers know what's happening with their package. This needs perhaps a bit more background work to sort the translations into the correct packages again, but this would also give us the possibility to upgrade just a single translation - and even the user has just to download translations for packages he wants to have. (Just think about users with a small internet connection.) But apart from this: installing some "pseudo" packages to obsolete our patch-framework is a good idea ;-) ------- Comment #2 From Lars Vogdt 2008-01-11 18:12:07 MST [reply] ------- Private Just have a look at #255716c2 to get an additional idea why I'm agains an additional package. "Several packages were dropped or renamed"... ...and perhaps even not installed on the users machine.... ------- Comment #3 From Karl Eichwalder 2008-01-14 01:38:44 MST [reply] ------- Private Touching "frozen" packages just because of updated translation files is not an option. At least it did not work in the past. Bug 255716 is unrelated. Package maintainers must learn not to fix translation bugs in their packages (once the product is released), but either add the fixed file to translation-update or ask me (or Ladislav) to do it. Since most package maintainers are not that fond of fixing translation issue, they might even appreciate to hear that we'd happily like to offer a helping hand. If we make sure to release empty translation-update-LL packages with every product (openSUSE/SLE), we are probably on the right track ;) -- Karl Eichwalder R&D / Documentation 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

13 years, 3 months

[opensuse-packaging] yauap package for sale

by Sascha Sommer

Hi, as my time as working student is ending I'm looking for a new maintainer for the yauap package. yauap is a small commandline player that is based on the GStreamer multimedia framework. It is currently used in amarok where it acts as a dbus controlled backend. I will still do the upstream maintenance. Feel free to contact me there if there are problems. Regards Sascha --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 3 months

[opensuse-packaging] new perl, new glibc

by Stephan Kulow

Hi! There is now perl 5.10, glibc 2.7 and NetworkManager 0.7 in Factory (not yet synced out though). So don't be suprised if you see new failures - you have to fix them yourself :) Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 3 months

[opensuse-packaging] 64bit problem with package cgicc-3.2.3 in openSUSE10.3

by David Saint

Hi, I'm new to openSUSE development and I have a question about how to get a package updated in a distribution of openSUSE. Currently openSUSE10.3 includes package cgicc-3.2.3, but there's a known bug in that version of cgicc that impacts execution in a 64-bit environment. This bug is fixed in cgicc-3.2.4 (and I've tested the fix on openSUSE10.3) so I would like that package updated in the official distribution, but I don't know who to ask to get this done. The RPMs I built were named: cgicc-3.2.4-3.x86_64.rpm cgicc-devel-3.2.4-3.x86_64.rpm I found the list of issues fixed in cgicc-3.2.4 at: http://fresh.t-systems-sfr.com/unix/www/cgicc-3.2.4.tar.gz:a/cgicc-3.2.4 /NEWS Thanks... Dave. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 3 months

[opensuse-packaging] Multiple RPM's owning the same file

by Dan Stromberg

We have about 1.5 dozen files (EG inittab) that are owned by openSUSE and SLES, and also owned by an RPM that holds our product. I gather this is generally considered poor practice - just how bad is it? If we install the OS, install our product, then remove our product, are we in for losing those OS files? Will the changes be reverted (I'm guessing they won't be reverted)? What if we never uninstall it? It would seem to violate the principle of least surprise to have an RPM you should "just never uninstall", but is there more to it than that? What if we do an upgrade of our product RPM's - could trouble ensue there with two RPM's owning a file? I might prefer to move the tweaks to these system files into a shell script (outside an RPM) as part of our OS installer (via autoyast), but it's not entirely up to me. What if we had our RPM's make algorithmic changes to files like inittab instead of trying to own the files, and then have those same RPM's attempt to algorithmically revert the changes on rpm deletion - would that leave us in the same situation as having two RPM's owning a given file? I'm guessing not, but I'd like to make sure we cover all the bases. Oh, and are "application installation scripts" going the way of the dodo now that rpm's and deb's and pkg's are taking off? Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 3 months

Re: [opensuse-packaging] Problems with RPM Supplements

by Cristian Rodríguez

Stefan Schubert escribió: >> > php5-timezonedb will only be installed if an older version of php5 will > be installed > too at the same time. > It will not be installed if there is already an installed version of php5. hrmmm.. then there is a bug in the documentation ? http://en.opensuse.org/Software_Management/Dependencies#Weak_dependencies "This resolvable will be installed if this capability is provided by an **installed** resolvable." Ok, then how I can do this ??, install php5-timezonedb only when php5 provides an older version of php(tzdatabase) ? -- "The only thing that interferes with my learning is my education." - Albert Einstein Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 3 months

[Fwd: Re: [opensuse-packaging] Problems with RPM Supplements]

by Stefan Schubert

-------- Original-Nachricht -------- Betreff: Re: [opensuse-packaging] Problems with RPM Supplements Datum: Wed, 09 Jan 2008 09:23:02 +0100 Von: Stefan Schubert <schubi(a)suse.de> An: Cristian Rodríguez <crrodriguez(a)suse.de> Referenzen: <47845029.50801(a)suse.de> Cristian Rodríguez schrieb: > Hi all ;-) > > I have two packages > > a) php5.rpm > Provides: php(tzdatabase) = 2007.9 > > > b) php5-timezonedb.rpm > Supplements: php(tzdatabase) < 2007.11 > > > I expect php5-timezonedb to be installed automatically by the package > manager when php5.rpm provides an older version of php(tzdatabase) > however it does not work. any hint about what Im missing ? > > > php5-timezonedb will only be installed if an older version of php5 will be installed too at the same time. It will not be installed if there is already an installed version of php5. Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- 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

13 years, 3 months

[opensuse-packaging] [Fwd: Re: [zypp-devel] zypper up installs -32bit rpm]

by Stefan Schubert

-------- Original-Nachricht -------- Betreff: Re: [zypp-devel] zypper up installs -32bit rpm Datum: Wed, 09 Jan 2008 09:17:57 +0100 Von: Stefan Schubert <schubi(a)suse.de> An: Cristian Rodríguez <crrodriguez(a)suse.de> Referenzen: <47841EA5.6030800(a)suse.de> There is not enough information to give an answer here. Please use the "--debug-solver" option, generate a testcase and an bugzilla entry. Greetings Stefan Cristian Rodríguez schrieb: > Hi folks: > > I just wonder why zypper up seems to always install -32bit rpms even if > those were not previously installed > > i.e recent with recent mysql update > > zypper up > > The following packages are going to be upgraded: > libmysqlclient15 mysql mysql-client > > The following NEW package is going to be installed: > libmysqlclient15-32bit > > The following NEW patch is going to be installed: > libmysqlclient-devel > > > even more , it wants to install a new patch of libmysqlclient-devel > which is not installed on the system either.. > > This is a bug I guess.. or Im missing something here ? ;-) > > > > -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- 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

13 years, 3 months

[opensuse-packaging] Problems with RPM Supplements

by Cristian Rodríguez

Hi all ;-) I have two packages a) php5.rpm Provides: php(tzdatabase) = 2007.9 b) php5-timezonedb.rpm Supplements: php(tzdatabase) < 2007.11 I expect php5-timezonedb to be installed automatically by the package manager when php5.rpm provides an older version of php(tzdatabase) however it does not work. any hint about what Im missing ? -- "The only thing that interferes with my learning is my education." - Albert Einstein Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 3 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging January 2008