December 2007 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Suggested package updates
by Krzysztof Kotlenga 13 Dec '07

13 Dec '07

Hi. Suggested package updates: Name Current New Repos ---------------------------------------------------------- python-qt4 4.3 4.3.3 standard, devel:languages:python python-sip 4.7 4.7.3 standard, devel:languages:python eric 4.0.1 4.0.3 standard gajim 0.11.1 0.11.4 server:messaging gpsd 2.34 2.35 Application:Geo lyx 1.5.1 1.5.2 standard, KDE:Backports ntfsprogs 1.13 2.0.0 standard, filesystems BTW: Which mailing list is best for reporting outdated packages? Where can I know why some packages are in more than one repo? Why standard repo is so poor and I have to use gazillion of BS repos? -- Krzysztof Kotlenga <piernik$gmail,com> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 7

[opensuse-packaging] Xen 3.2 packages, guest installation, etc.
by Ian Jackson 12 Dec '07

12 Dec '07

We're working on having Xen 3.2 released soon. We at Xensource have been in the habit of providing binary packages for various distributions and at the moment OpenSUSE 10.3 probably looks like one we would like to support in that way. It seemed to me that the best approach would be, where possible, to use a distro's own packaging setup. That would be more likely to generate packages which integrate well with the distro and behave more like the distro's own Xen packaging arrangements. I haven't looked at the OpenSUSE Xen srpms in detail but would that be a reasonable starting point for generating our 3.2 binary rpms ? Also, while I'm here: I've been having quite some difficulty getting a working OpenSUSE Xen guest install. Is there a recommended procedure for this when the host is not OpenSUSE ? (In my case the host is Debian etch.) For many other distributions there are ways of running what amounts to a port of the installer directed at a filesystem tree, but just as a normal program on the host; so for example with Fedora and Centos one uses rinse, and for Debian derivatives debootstrap does the job (and all of these tools seem to be readily portable). Is there an analogous tool for OpenSUSE ? In the absence of such a utility I've been trying to install OpenSUSE as an HVM (fully virtualised rather than paravirtualised) guest but have been having serious trouble: so far a couple of annoying bugs in the Xen emulations (which I've got past) and now I have a bug where the installer's kernel gets very upset with the emulated IDE controller. Is installing OpenSUSE as a Xen HVM guest (or indeed as a PV guest) expected to work ? Can it be sensibly done without the use of difficult-to-port hostside management tools from OpenSUSE ? Regards, Ian. --------------------------------------------------------------------- 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] prefix horde apps with horde-*
by Marcus Hüwe 10 Dec '07

10 Dec '07

Hi, what about if we prefix all horde applications with "horde-"? Example: horde -> horde imp -> horde-imp ingo -> horde-ingo ... The idea is that it is obvious to the user that a package is a horde application. This naming change would only affect the "imp" package in the distribution. If you agree with this change I could rename the horde packages in the server:php:applications buildservice project too. What do you think? Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 6

[opensuse-packaging] Which dependencies should I set?
by Christian Boltz 09 Dec '07

09 Dec '07

Hello, I have an interesting question: Which dependencies should I set for Postfixadmin? (package is postfixadmin-svn in home:cboltz, specfile is attached for easier access) Short summary: - Postfixadmin is a PHP web interface, used for administration of virtual domains in postfix - it can use MySQL and PostgreSQL as database Now to the dependency problems: - php-mysql and/or php-pgsql? One of them is always unused, but you never know which one in advance (from RPM's POV) - Should I require MySQL and/or PostgreSQL? You never know which one is used, and accessing the database on another machine is also possible, so technically none of them is really needed. - Should I require Postfix? Sure, Postfixadmin is used to administrate it, but it's the same as with MySQL: It could run on another machine. Postfixadmin also comes with a vacation script, which needs a user "vacation" and some additions to the postfix config. - should I create the user "vacation" in %pre? - if yes, should I delete it again in %preun? How to avoid this on package updates? - is it a good idea to add some lines to /etc/postfix/master.cf auto- matically ("grep vacation master.cf || cat some_lines >> master.cf") or should I let this to the user? Other packaging questions: - setup.php is installed by the package, but needs to be deleted to make Postfixadmin work. Is there any special trick how to handle this in RPM? - any other comments on the specfile are also welcome ;-) I'm quite sure there is no "perfect" solution for the above questions, but some hints about good practise would be welcome. Regards, Christian Boltz -- There are no bugs expected after Beta3, that's why it is called RC. [Jan Engelhardt]

6 9

[opensuse-packaging] Research: effects of diversity on threads from malware
by Knijff, S.A.W. van der 07 Dec '07

07 Dec '07

I'm performing an research about the effects of diversity on malware. In this research there will be looked at the effects of diversity within an operating system on malware, in this case different GNU/Linux distro's. Cause of the limited time schedule there will only be tested with three distro's, after this there will be picked one distro which is tested on different architectures. There is chosen to work with Fedora Core 6, OpenSuse 10.2 and Ubuntu 6.10. Before starting the real-life tests there is a need to make some assumptions on what will happen when the malware is run on a system. Here for there will be looked at the compiler flags that are used during compilation of the distribution, I'm namely interested in the compiler flags which enhance the security within the distro. Also are there any kind of security measurements besides the compiler flags, for example SELinux, AppArmor, Address Randomization Execshield, PIE or others? I hope that you can provide me with some answers on my questions so i can move on with the research. Stephan --------------------------------------------------------------------- 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] How to deal with Python .pyc and .pyo files?
by jan matejek 06 Dec '07

06 Dec '07

Michal Marek napsal(a): > Jan Matejek wrote: >> Second worst case would be if you upgraded to a new major version of >> python, i.e. from 1.5 to 2.0. In that case python would report errors >> about bad bytecode, and i'm really not sure if it would recompile >> automatically. But i think it would. > > So... could python stop reporting errors in such cases and just silently > ignore the precompiled files? For mere mortals it's hard to understand > that they can use the same package with ELF binaries for years, but have > to rebuild python packages each time the python bytecode format changes. well sorry if python bytecode format changes more often than ELF standard :P There was no major (read 'incompatible') change since 2.0 release, i just went through the changelogs. So if you see any such errors somewhere, please report a bug and i'll make them go away. And, there *will* be a big breakage when python3k comes. But that is going to be an entirely new level of fun - py3k will not be backwards compatible and most apps will need to be modified. Let's not concern ourselves with that, for now... > "Why scripts and bytecode files have to be in lib64" comes as next ;) Because there is no better place for them, that's why ;e) Either we have to keep them in lib[64], and then they're arch-dependent because of that. Or, we go the Ubuntu way and store all .py in /usr/share/python or something, but that's a lot of trouble in itself (half-binary-half-python packages need to be installed in an interesting way, which can be a problem if you don't use distutils), and to add insult to injury, it violates FHS. Or somebody comes up with a clever way to keep stuff in lib and make python in lib64 recognize it and not break on binary files it finds there. (which i've been trying to do, but with little success so far) regards m. > > Michal > --------------------------------------------------------------------- > To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org > --------------------------------------------------------------------- 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] ant build error for java package - java.lang.NoClassDefFoundError
by Denny Beyer 05 Dec '07

05 Dec '07

Hi! I tried to build a java program, during the packaging day last week, but didn't get it to build. See the error message below. If i change into the directory "columba-1.4-src" manually and execute ant within the directory, everything seems to build fine. So the problem might be, that ant is not executed in that directory, but the previous command changed into the directory (and the directory exists). What did I miss? see the package spec file: https://api.opensuse.org/source/home:lumnis/columba/columba.spec Any Help is much appreciatet. This is my first project on the OBS, and java programs are rare in the build service and not well documented howto build in opensuse, and there is a lack of java programs in opensuse in general. Cheers, Denny error message: Exception in thread "main" Exception while printStackTrace(): java.lang.NoClassDefFoundError: java/lang/System error: Bad exit status from /var/tmp/rpm-tmp.46996 (%build) --------------------------------------------------------------------- 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] licenses.rpm again
by Lukas Ocilka 03 Dec '07

03 Dec '07

Hi, I've found this output in the finished 'build': --- cut --- Your package contains a file that contains the FSF GPLv2 license. If you really have to ship it, consider symlinking it from the licenses package. --- cut --- I remember deciding that we'll not use the licenses.rpm... or am I wrong? What's the current status, please :)? Thanks Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

4 3

[opensuse-packaging] rpm versions?
by Dan Stromberg 01 Dec '07

01 Dec '07

We have a product with versions like: 3.0.1-dev 3.0.2-rc2 3.0.2.5 (for a customer version) ...etc. As I'm packaging these as RPM's, we've been trying to do: %define major 3 %define minor 0 %define patchlevel 2 %define relnum rc2 ...but is that going to confuse rpm? That is, is relnum going to be compared numerically or as an ASCII string, or as something else? How can we ensure that dev < rc2 < 5 for relnum? Do we need to come up with a numbering scheme like "dev is 0-20, rc is 21-40, customer versions are 41-60" etc? Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3