November 2007 - openSUSE Packaging - openSUSE Mailing Lists

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] 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

Re: [opensuse-packaging] Problem with 'build' glibc
by Jonathan E. Brickman 30 Nov '07

30 Nov '07

>> rpmbuild would not build a stock glibc, same errors. Trying 'build'. I >> set my environment at: >> >> BUILD_ROOT=/home/BUILD >> BUILD_RPMS=/home/BUILD/SUSE_DVD_MOUNT/suse/i586:/home/BUILD/SUSE_DVD_MOUNT/suse/i686:/home/BUILD/SUSE_DVD_MOUNT/suse/noarch >> BUILD_RPM_BUILD_STAGE=-bb >> >> error: File >> /usr/src/packages/SOURCES/glibc-nptl-2.6.1-2007080316.tar.bz2: No >> > > Well, is this file in the directory where you call build? > > Yes. /usr/src/packages has been copied in toto to /home/BUILD/usr/src/packages. J.E.B. --------------------------------------------------------------------- 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] Problem with 'build' glibc
by Jonathan E. Brickman 30 Nov '07

30 Nov '07

rpmbuild would not build a stock glibc, same errors. Trying 'build'. I set my environment at: BUILD_ROOT=/home/BUILD BUILD_RPMS=/home/BUILD/SUSE_DVD_MOUNT/suse/i586:/home/BUILD/SUSE_DVD_MOUNT/suse/i686:/home/BUILD/SUSE_DVD_MOUNT/suse/noarch BUILD_RPM_BUILD_STAGE=-bb and indeed the RPMS are at the locations in BUILD_RPMS. 'build' installs everything it needs, quite successfully. But it is setting permissions wrongly in the build root. Below are the messages. What occurs actually, is /home/BUILD and everything below it, is set to 99.99 (user.group), and although the files are all in place, the permissions are so far wrong that it can't run. I am running 'build' from superuser; is there something I need to do to get the chroot to do permissions correctly, or something else? keeping gcc-4.2-24 keeping gcc42-c++-4.2.1_20070724-17 keeping gcc-c++-4.2-24 removing nis flags from /home/BUILD/etc/nsswitch.conf... now finalizing build dir... Checking permissions and ownerships - using the permissions files /tmp/Check.perms.qK2721 setting /etc/shadow to root:shadow 0640. (wrong owner/group root:root permission s 0644) setting /usr/src/packages/SOURCES/ to root:root 1777. (wrong owner/group abuild: abuild permissions 0755) setting /usr/src/packages/BUILD/ to root:root 1777. (wrong owner/group abuild:ab uild permissions 0755) setting /usr/src/packages/RPMS/ to root:root 1777. (wrong owner/group abuild:abu ild permissions 0755) setting /usr/src/packages/RPMS/i386/ to root:root 1777. (wrong owner/group abuil d:abuild permissions 0755) setting /usr/src/packages/RPMS/i686/ to root:root 1777. (wrong owner/group abuil d:abuild permissions 0755) setting /usr/src/packages/RPMS/noarch/ to root:root 1777. (wrong owner/group abu ild:abuild permissions 0755) setting /usr/src/packages/SPECS/ to root:root 1777. (wrong owner/group abuild:ab uild permissions 0755) setting /usr/src/packages/SRPMS/ to root:root 1777. (wrong owner/group abuild:ab uild permissions 0755) Starting SuSEconfig, the SuSE Configuration Tool... Running in full featured mode. Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.groff... Executing /sbin/conf.d/SuSEconfig.perl... Executing /sbin/conf.d/SuSEconfig.permissions... Finished. ----------------------------------------------------------------- ----- building glibc.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- error: File /usr/src/packages/SOURCES/glibc-nptl-2.6.1-2007080316.tar.bz2: No su ch file or directory --------------------------------------------------------------------- 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] Various Packet formats - Linux development
by Benjamin Kramer 29 Nov '07

29 Nov '07

Hallo, I ' am using Linux for about 10 years and I am looking to see that Linux is developing to an Operating System which all people can use without any difficulties. So that it can easy be used by firms, small business and private persons. How can we reach this? The main reason why people do not change to Linux is that the Software ist not available on Linux. For example Adobe Photoshop, Fireworks, Flash, Dreamweaver and not to forget the games. I know that I can emulate with wine some of the applications, but it is very difficult in handling. I see the problem in the various packet formates like rpm, deb... It would be better do come with other distributions to a solution for one packet format. That would be useful in developing Software only for one packet system. That can't be so difficult can it? And when we have one packet format, I think bigger Company's like Adobe will produce their software for Linux. We should keep in mind that the spreading of Linux should be in front. Benjamin Kramer --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] [Fwd: [yast-devel] sw_single Acccessibility Category]
by Lukas Ocilka 29 Nov '07

29 Nov '07

Hi, It seems that this mail rather belongs here. RPM Groups should be assigned in RPM spec file. YaST software management doesn't assign packages to groups (here called "category"). Thx && Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

1 0

[opensuse-packaging] rpmbuild glibc for OpenSuse?
by Jonathan E. Brickman 28 Nov '07

28 Nov '07

Greetings. I am trying to rebuild glibc under OpenSUSE 10.3, optimizing for CPU, and am running into a peculiar problem. I am running the command: rpmbuild -bb --target athlon glibc.spec from /usr/src/packages/SPECS, with the glibc .src.rpm for 2.6.1 installed; and all goes very well, until rather near the end: + cd .. + export RPM_BUILD_ROOT + mkdir -p /var/tmp/glibc-2.6.1-build/lib/obsolete + cp -av bits/stdio-lock.h /var/tmp/glibc-2.6.1-build/usr/include/bits/stdio-lock.h `bits/stdio-lock.h' -> `/var/tmp/glibc-2.6.1-build/usr/include/bits/stdio-lock.h' + install -m 0700 glibc_post_upgrade /var/tmp/glibc-2.6.1-build/usr/sbin + mkdir -p /var/tmp/glibc-2.6.1-build/usr/include/resolv + install -m 0644 resolv/mapv4v6addr.h /var/tmp/glibc-2.6.1-build/usr/include/resolv/ + install -m 0644 resolv/mapv4v6hostent.h /var/tmp/glibc-2.6.1-build/usr/include/resolv/ + mkdir -p /var/tmp/glibc-2.6.1-build/usr/share/doc/glibc + cp -p 'manual/libc/*.html' /var/tmp/glibc-2.6.1-build/usr/share/doc/glibc cp: cannot stat `manual/libc/*.html': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.66519 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.66519 (%install) Should I be using a tool other than rpmbuild? Or is there a package I am missing? I have tried a number of things, but haven't been able to figure it out. J.E.B. --------------------------------------------------------------------- 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] rpmbuild glibc for OpenSuse?
by Jonathan E. Brickman 28 Nov '07

28 Nov '07

Greetings. I am trying to rebuild glibc under OpenSUSE 10.3, optimizing for CPU, and am running into a peculiar problem. I am running the command: rpmbuild -bb --target athlon glibc.spec from /usr/src/packages/SPECS, with the glibc .src.rpm for 2.6.1 installed; and all goes very well, until rather near the end: + cd .. + export RPM_BUILD_ROOT + mkdir -p /var/tmp/glibc-2.6.1-build/lib/obsolete + cp -av bits/stdio-lock.h /var/tmp/glibc-2.6.1-build/usr/include/bits/stdio-lock.h `bits/stdio-lock.h' -> `/var/tmp/glibc-2.6.1-build/usr/include/bits/stdio-lock.h' + install -m 0700 glibc_post_upgrade /var/tmp/glibc-2.6.1-build/usr/sbin + mkdir -p /var/tmp/glibc-2.6.1-build/usr/include/resolv + install -m 0644 resolv/mapv4v6addr.h /var/tmp/glibc-2.6.1-build/usr/include/resolv/ + install -m 0644 resolv/mapv4v6hostent.h /var/tmp/glibc-2.6.1-build/usr/include/resolv/ + mkdir -p /var/tmp/glibc-2.6.1-build/usr/share/doc/glibc + cp -p 'manual/libc/*.html' /var/tmp/glibc-2.6.1-build/usr/share/doc/glibc cp: cannot stat `manual/libc/*.html': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.66519 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.66519 (%install) Should I be using a tool other than rpmbuild? Or is there a package I am missing? I have tried a number of things, but haven't been able to figure it out. J.E.B. --------------------------------------------------------------------- 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] rpmbuild glibc for OpenSuse?
by Jonathan E. Brickman 26 Nov '07

26 Nov '07

Greetings. I am trying to rebuild glibc under OpenSUSE 10.3, optimizing for CPU, and am running into a peculiar problem. I am running the command: rpmbuild -bb --target athlon glibc.spec from /usr/src/packages/SPECS, with the glibc .src.rpm for 2.6.1 installed; and all goes very well, until rather near the end: + cd .. + export RPM_BUILD_ROOT + mkdir -p /var/tmp/glibc-2.6.1-build/lib/obsolete + cp -av bits/stdio-lock.h /var/tmp/glibc-2.6.1-build/usr/include/bits/stdio-lock.h `bits/stdio-lock.h' -> `/var/tmp/glibc-2.6.1-build/usr/include/bits/stdio-lock.h' + install -m 0700 glibc_post_upgrade /var/tmp/glibc-2.6.1-build/usr/sbin + mkdir -p /var/tmp/glibc-2.6.1-build/usr/include/resolv + install -m 0644 resolv/mapv4v6addr.h /var/tmp/glibc-2.6.1-build/usr/include/resolv/ + install -m 0644 resolv/mapv4v6hostent.h /var/tmp/glibc-2.6.1-build/usr/include/resolv/ + mkdir -p /var/tmp/glibc-2.6.1-build/usr/share/doc/glibc + cp -p 'manual/libc/*.html' /var/tmp/glibc-2.6.1-build/usr/share/doc/glibc cp: cannot stat `manual/libc/*.html': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.66519 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.66519 (%install) Should I be using a tool other than rpmbuild? Or is there a package I am missing? I have tried a number of things, but haven't been able to figure it out. J.E.B. --------------------------------------------------------------------- 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] Errors during the erase of Hipo
by Vincenzo Barranco 26 Nov '07

26 Nov '07

Hi, I tried to do the rpm of Hipo ( http://www.gnome.org/projects/hipo/ ), wich i've inserted in the Buildservice on my home project (http://download.opensuse.org/repositories/home:/barravince112/), and if i would remove this package the pc says to me that is impossible, look at there: linux-xxxx:/home/barravince # rpm -e hipo-0.5-6.1 /var/tmp/rpm-tmp.42486: line 1: fg: no job control error: %postun(hipo-0.5-6.1.i586) scriptlet failed, exit status 1 What can it be? Best Regards Vincenzo --------------------------------------------------------------------- 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] glibc 2.7 in Beta testing
by Stephan Kulow 26 Nov '07

26 Nov '07

Hi! Petr checked in glibc 2.7 into autobuild and we see build failures in quite some packages that look like this one: In function 'int open(const char*, int, ...)', inlined from 'void NCurses::RedirectToLog()' at NCurses.cc:587: /usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments I think the error is speaking for itself, in case it does not: this is about int open(const char *pathname, int flags); int open(const char *pathname, int flags, mode_t mode); So please fix the code, for most cases 0666 or 0600 should be the right choice. BTW: as far as I can tell, glibc 2.6 did not have a default value, so the code in question should be buggy and can't have worked before. Greetings, Stephan -- 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

2 1

[opensuse-packaging] Requires in -devel packages
by Adrian Schröter 25 Nov '07

25 Nov '07

Hi, while OBS reconfiguration and brief internal discussion, I figured out that we do use Requires: in -devel packages inconsistend atm. A -devel package should Require: all other packages what provides header files or other stuff needed at compile time. It should NOT require a compiler package like gcc or gcc-c++. Also not Require the SUSE only alias like c_compiler or c++-compiler. I know that our packages are inconsistend in this regard atm. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 6

[opensuse-packaging] Qt Eclipse Integration
by Nikolay Derkach 23 Nov '07

23 Nov '07

Hi, I recently tried Qt Eclipse Integration and I have to say it works pretty well here except for Designer. Since Eclipse in 10.3 works only with Java 6, integration of Qt Designer is broken - it turned out that qt-eclipse-integration 1.0.0 requires Java 5 to work properly (http://lists.trolltech.com/qt-interest/2007-07/msg00707.html). I suppose there are some people familiar with Eclipse plugin packaging, so is it possible to make a workaround for the above mentioned bug? And yes, I'm searching for volunteers who want to package this eclipse plugin :) Qt Eclipse Integration can be downloaded from here: http://trolltech.com/developer/downloads/qt/eclipse-integration-download -- Regards, Nikolay Derkach --------------------------------------------------------------------- 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] libSieve, wherefore art thou?
by tabris 23 Nov '07

23 Nov '07

It seems that libSieve dropped out of OpenSuSE 10.3 (but was in OpenSuSE 10.2), and I can find no note in google or the changelog as to why. Any takers?

3 3

[opensuse-packaging] commoncpp2 looking for a new maintainer
by Ralf Haferkamp 22 Nov '07

22 Nov '07

Hi, anybody interested in taking over the autobuild maintainership for the CommonC++ packages? I am not able to take care of this well enough any longer. It seems to be used by some VOIP packages, otherwise I'd probably file a drop request. -- Ralf --------------------------------------------------------------------- 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] automatic BuildRequires and Requires
by Stanislav Brabec 21 Nov '07

21 Nov '07

Hallo. I am just starting to work on my idea of automatic generating of devel BuildRequires and Requires. The goal is: - Increase quality of packages preventing unwanted failed checks and consequent building of feature stripped packages. - Drop obsolete dependencies (now added manually, removed after bug report) 1) As I wrote in past, I created a pkg-buildrequires package, which should help with automatic generating of BuildRequires. 2) Next idea would be automatic creating of devel Requires/Provides using information provided by pkg-config files. 1) Package pkg-buildrequires with a simple documentation is available for download from OBS home:sbrabec. https://build.opensuse.org/package/show?project=home%3Asbrabec&package=pkg-… I just started to experiment with pkg-buildrequires it in OBS GNOME:UNSTABLE repository with it. https://build.opensuse.org/project/show?project=GNOME%3AUNSTABLE There is still a lot of failures, but low level packages (glib2, cairo, pango) are already built using pkg-buildrequires. It creates BuildRequires automatically in following form compatible with RPM: BuildRequires: list of packages added manually #BEGIN pkg-buildrequires # Created by pkg-buildrequires. Do not edit by hand. BuildRequires: list of packages added by pkg-buildrequires %define pkg_buildrequires_checksum b49abeb28e08721413a59a3d53324613 %define pkg_buildrequires_unknown_checksum cb977b8752a03a75a077316c2efdd439 #END pkg-buildrequires One checksum includes all needed packages. If the list changes, special type of failure will happen. It can be detected, BuildRequires automatically updated and package built again. Second (optional) checksum sums list of all failed pkg-config checks and its presence should confirm, that packager reviewed all failed checks and confirms, that it is correct. If this number changes, user will be notified to take manual action (i. e. add missing package, rebuild and update values). Currently I have no idea, how to do it better and still stay RPM compatible (i. e. in one step). 2) Second idea would require modification of %find_provides and %find_requires to provide/require symbols like PC(libIDL-2.0), which could create devel dependency chain automatically. I see no chance to convert these symbols to package names - if you are building two devel packages from one spec file, there is no way to generate dependencies between them - script does not know file lists of other sub-packages. I plan to extend my experiments in GNOME:UNSTABLE with this (not yet written) script. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- 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 dsfagdf 19 Nov '07

19 Nov '07

Johannes Meixner napsal(a): > > By the way: > > Isn't there a general problem with "python files strewn > all over the system"? Well, yes, that's why i wrote it's bad packaging. But it's a minor problem. Python will work with it (unless the misplaced thing is a python module, in which case python won't be able to find and import it without some hassle) and ordinary user will not notice. This might change when Python is accepted into LSB, because there will probably be some restriction on .py files placement. > How does Python deal with .py files from whatever personal > Python projects in user's home directories? > The user has write access so that he gets .pyc or .pyo files > stored where his .py files are. > What happens if the system admin upgrades to a new major > version of Python? I'm not entirely sure about this, but i think that python will complain and recompile the bytecode files in question. Sadly, i don't have an old enough python anywhere nearby, so i can't test the assumption now. > I think the same problem (perhaps even in a worse shape) > exists for whatever third-party Python stuff which gets > installed somewhere under /opt/ or /usr/local/. > Think about proprietary third-party software which cannot > be changed and which exists for more than one SLES version. Oldest python we support is version 2.2.1 in SLES8, and all new versions since that are at least backwards compatible. So if anyone has a third-party software for python 1.5, too bad for them. But i think that third party vendors would provide python2 compatible packages by now. > I don't know if the Python license allows to have proprietary > Python stuff but I think you understand the basic idea behind. > http://www.python.org/doc/1.5.1p1/tut/node43.html > seems to indicate that at least semi-proprietary Python stuff > can exist because it reads: > --------------------------------------------------------------- > It is possible to have a file called "spam.pyc" (or "spam.pyo" > when -O is used) without a module "spam.py" in the same module. > This can be used to distribute a library of Python code in a > form that is moderately hard to reverse engineer. > --------------------------------------------------------------- > There could be even "binary-only" third-party Python stuff > where no .py files exist. > What happens if a system upgrade (e.g. SLES N -> SLES N+1) > upgrades Python to a new major version? The software will no longer work. Users would need to either keep the older python around, or ask the vendor to recompile the package. But the bytecode files will not be deleted. >> But even more important is that regular user doesn't have write access >> to wherever the .py files are stored. You would need to run each python >> program as root first, otherwise python would need to compile the >> sources every time the program is run. > > This has another consequence: > It doesn't help not to provide .pyc or .pyo files in the RPM > to avoid problems with outdated .pyc or .pyo files if the > Python major version changes because when root runs whatever > .py files, the matching .pyc or .pyo files are created in any case. Right. > > >>> I am no Python expert at all and I would be happy if a Python expert >>> could provide some background information. >> is this background sufficient? ;e) > > Yes, it is perfect and I am happy. glad to read that. regards jan matejek --------------------------------------------------------------------- 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] update and renaming blocxx package according to Shared_Library_Packaging_Policy
by Michael Calmer 19 Nov '07

19 Nov '07

Hi, we updated the blocxx package to version 2.1.0 . With this update we also renamed the package to follow the Shared Library Packaging Policy. blocxx-devel => libblocxx-devel blocxx => libblocxx6 Compat package: libblocxx4 Documentation package still has the old name: blocxx-doc The Requires/Obsolets are set correctly, so that everyting should still build. (Tested in BETA since a week now.) But if your package Requires/BuildRequires blocxx/blocxx-devel please change this to libblocxx6/libblocxx-devel the next time when you touch your package. Thanks. -- MFG Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer(a)suse.com -------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

1 0

[opensuse-packaging] SUSE Linux 10.0 coming to a close
by Marcus Meissner 19 Nov '07

19 Nov '07

Hi, This mail is interesting only for SUSE packagers. Starting after Novell Bug 342146 security issues reported are no longer to be fixed for SUSE Linux 10.0 unless specifically requested by the security team. Existing bugs (<= 342146) still need to be fixed for 10.0. Ciao, Marcus --------------------------------------------------------------------- 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] openSUSE GNOME & KDE Packaging Day: Nov 30 - Dec 1
by Michael Wolf 16 Nov '07

16 Nov '07

Hello Members of the openSUSE GNOME and KDE teams will be holding a packaging day (two days, actually :)). If you're interested in learning how to build KDE or GNOME packages for openSUSE, read on: http://en.opensuse.org/Packaging/Packaging_Day Michael --------------------------------------------------------------------- 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] How to deal with Python .pyc and .pyo files?
by Jan Matejek 16 Nov '07

16 Nov '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Johannes Meixner napsal(a): > Hello, > > On Nov 14 16:00 Marcus Rueckert wrote (shortened): > >>> On Wed, 2007-11-14 at 15:08 +0100, Johannes Meixner wrote: >>>> Hello, >>>> >>>> what is the recommended way for packaging Python stuff? >>>> >>>> Either >>>> have byte-compiled Python .pyc and .pyo files packaged into the RPM >>>> or >>>> let this be done by the currently actually installed Python system >>>> during run-time on the end-user's computer and not by whatever >>>> (perhaps different) Python system during package build-time? >> as we build with the same python version as the user will run it later. >> you can safely package the .pyc files. > > I understand that it is the same Python version directly after > a new system installation. > > But what happens when the user later change/update his Pyhon? > > Think about the "worst case" when the user replaces our Pyhon > with whatever self-compiled Pyhon. > > Are byte-compiled Python .pyc and .pyo files the same for any Python > and/or is any Python sufficiently smart to know when .pyc and/or .pyo > files are outdated (even if the matching .py files are unchanged)? They are (mostly) the same, AND there is some kind of version check in the file. Don't worry about this, python would notice any problem by itself ;e) 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. Worst case would be if you downgraded, i don't think python 1.5 could cope... But on the other hand, i don't think this problem is worth considering. That's why python has versioned site-packages. In your other post you noticed that python files are strewn all over the system. In most cases that is bad packaging. Generally speaking, all python files should be located in /usr/lib[64]/pythonx.y/site-packages (of course there are exceptions, but let's not go into that). >> i would even recommend packaging >> them so they get removed if you uninstall the package. > > Removal when uninstalling could also be done by whatever > other magic (e.g. via %ghost or a %preun scriptlet in RPM). Bad magic, bad bad magic. We have enough trouble with scriptlets as they are now. > I wonder why in this case small RPMs seem not to count. > > For example the installed .pyc and .pyo files in python > on a openSUSE 10.3 i386 system are more than 7MB and > still about 1.6MB after "bzip2" so that those files > should make the python RPM about 1.6MB bigger. > > At least according to > http://www.python.org/doc/1.5.1p1/tut/node43.html > I wonder if there is a noticeable advantage to provide > .pyc and .pyo files in the RPM because it reads: > "A program doesn't run any faster when it is read from > a ".pyc" or ".pyo" file than when it is read from a ".py" file; > the only thing that's faster about ".pyc" or ".pyo" files is > the speed with which they are loaded." True, and that's why we provide them. Think about it this way: python programs need to be compiled too. We provide the "binaries" form so that users' computers don't need to do the compilation themselves. But even more important is that regular user doesn't have write access to wherever the .py files are stored. You would need to run each python program as root first, otherwise python would need to compile the sources every time the program is run. > I am no Python expert at all and I would be happy if a Python expert > could provide some background information. is this background sufficient? ;e) > > > Kind Regards > Johannes Meixner regards jan matejek -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHPJmGjBrWA+AvBr8RAu4nAJ44givXOzCG9LY1ge9DWoSouwTFHQCgjlf2 WA9ogJSDXliAvm2NxmAsy2E= =zapY -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] How to deal with Python .pyc and .pyo files?
by Johannes Meixner 15 Nov '07

15 Nov '07

Hello, what is the recommended way for packaging Python stuff? Either have byte-compiled Python .pyc and .pyo files packaged into the RPM or let this be done by the currently actually installed Python system during run-time on the end-user's computer and not by whatever (perhaps different) Python system during package build-time? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex --------------------------------------------------------------------- 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] KMP package file
by Alex Lau 13 Nov '07

13 Nov '07

Dear all packagers Let say we wanted to put document into the kmp is that possible and is it against police? Thanks Alex ----------------------------------- 刘俊贤 Alex Lau PRC Beijing Linux R&D Engineer Mainland-Mobile (8610) 13910181404 HongKong-Mobile (852) 91621631 --------------------------------------------------------------------- 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] libdbcxx_cxx-4_5-devel missing on 10.3 and Factory
by Pascal Bleser 13 Nov '07

13 Nov '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Trying to build an application that includes "db_cxx.h". On 10.2 and below, that file is part of "db-devel" but on 10.3 it has been split out into libdb_cxx-*-devel Problem is, it has: * libdb_cxx-4_4-4.4.20-28.i586.rpm * libdb_cxx-4_4-devel-4.4.20-28.i586.rpm but it also has: * libdb-4_5-devel-4.5.20-29.i586.rpm * libdb-4_4-devel-4.4.20-28.i586.rpm When the OBS starts the build VM for 10.3 and Factory, it preinstalls libdb-4_5: preinstalling libdb-4_5... My .spec file includes %if %suse_version >= 1030 BuildRequires: libdb_cxx-4_4-devel %endif which causes this: installing libdb-4_4-devel-4.4.20-28 installing libdb-4_5-devel-4.5.20-29 file /usr/include/db.h from install of libdb-4_5-devel-4.5.20-29 conflicts with file from package libdb-4_4-devel-4.4.20-28 Makes sense but... where's libdb_cxx-4_5-devel ? cheers - -- -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.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHOVyJr3NMWliFcXcRAvQAAJ46LrZ+FCYYdL8TENjhFHvR2IEiGQCeKd9i X60m9Fn9S5wZpiXNRjVM30M= =NSZn -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] python and valgrind
by Martin Vidner 12 Nov '07

12 Nov '07

Hi, when hunting a bug in yast2-python-bindings I tried to use valgrind on python. How silly of me! Errors from inside python all over the place: mvidner@valkyrie:~$ valgrind python -c "print 'hello'" 2>&1 | wc -l 558 I am attaching a suppression file to fix that. Can't python use more civilized code? Apparently not, as explained in http://svn.python.org/projects/python/trunk/Misc/README.valgrind Can valgrind include this suppression by default? mvidner@valkyrie:~$ valgrind --suppressions=PyObject_Free-sucks.supp python -c "print 'hello'" 2>&1 | wc -l 23 -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[opensuse-packaging] dependencies, why and where
by Christofer Olofsson 12 Nov '07

12 Nov '07

Hi everyone, hope i'm on the correct list. Let me start by thanking you for opensuse, not to come off to bad asking these questions ;) Why does a package depend on another and where/how can I find out how? I'm asking this because there are certain deps. that I don't fully understand; Such as php5 depends sqlite, php5-json and other packages that I atleast, cannot find out why it does? And man, installs cronjob which would use makewhatis, but does not depend on it? subversion.. want's apache but not any DAV support? I'm puzzled, please enlighten me =) ps. I really love that the base install is below 400MB, thank you for that! ;) c. -- When mirror toward umbrella ruminates, diskette for prays. -------------------------------------------------------- Christofer Olofsson Technical Specialist Net Entertainment NE AB, Birger Jarlsgatan 57 B, S-113 56 Stockholm, Sweden T: , F:+46 8 556 967 07 christofer.olofsson(a)netent.com, www.netent.com Better Games --------------------------------------------------------------------- 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] openSUSE Factory update (gcc 4.3)
by Adrian Schröter 12 Nov '07

12 Nov '07

Hi, the openSUSE:Factory distro got an update and does use gcc 4.3 from now on as default compiler. This may have some effect when compiling your stuff inside or outside of the build service. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de --------------------------------------------------------------------- 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] Procinfo-NG 2.0.135 released.
by tabris 11 Nov '07

11 Nov '07

Changelog * Various packaging changes, at request of OpenSuSE project. * Silence some sprintf warnings about %llu vs %lu and 64-bit vs 32-bit arches. * Move bzero macro into routines.cpp * Add C++ type-safe zalloc macro * move readFile into routines.cpp * Make readFile accept larger lines (40958 bytes instead of 4094 bytes). ** Probably should be made adaptive, rather than using a static-sized buffer * Cygwin support. ** IRQ stats don't exist ** Disk stats don't exist ** 'nice' CPU stat doesn't work, always zero. * Reorganize a lot of code ** prettyPrint is now in its own independent .cpp file ** Various time-routine bugfixes ** Added some time-specific macro/constants, to make people happy who hate magic numbers. * Add __time_rel_long from SrSv, not that I use it in this project.

1 0

[opensuse-packaging] -mini packages purpose
by Cristian Rodriguez 09 Nov '07

09 Nov '07

Hi: What is the specific reason for having foobar-mini packages ? I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ? -- "If eval() is the answer, you're almost certainly asking the wrong question." --Rasmus Lerdorf Cristian Rodríguez R, 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

6 7

[opensuse-packaging] vboxvfs seems to be broken
by Rajko M. 08 Nov '07

08 Nov '07

My favorite virtualization program in Build Service, ftp://ftp5.gwdg.de/pub/opensuse/repositories/Virtualization:/VirtualBox/openSUSE_10.3/x86_64 has broken package (again). virtualbox-guest-tools-1.5.2-13.1 /usr/bin/vboxadd-timesync /usr/bin/vboxadd-xclient /usr/sbin/mountvboxsf Changelog: |* Fri Nov 2 07:00:00 2007 suse-tux(a)gmx.de |- Added own Makefiles for the kernel modules (vboxvfs seems | to be broken though) I'm not sure, but it seems that: mv /usr/sbin/mountvboxsf /usr/sbin/mountvboxfs should fix the problem. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] Requires: %name = %version-%release
by Michal Marek 07 Nov '07

07 Nov '07

Hi, A lot of openSUSE packages require an exact version-release of another subpackage of the same spec. Is this really needed? While it makes sense for some special packages like *-debuginfo or the gcc subpackages, does a *-devel or even *-doc package really need to depend on the runtime package from the _same build_? IMHO it only makes debugging and testing harder, because one has to update / downgrade certain sets of packages atomically, instead of just upgrading the one package with one patch added. And "one patch added" is usually the only difference (if any) between libxy-version-release and libxy-version-(release+1). Opinions? Should we eliminate these strict dependencies where possible? Or should we use them everywhere? As it is now, it's inconsistent at least. I attached a script that I used for checking which Factory RPMS have such dependencies. The second attachment is the output of the script. Michal aelfred-demo requires aelfred = %version-%release bsh2-demo requires bsh2 = %version-%release castor-demo requires castor = %version-%release castor-test requires castor = %version-%release castor-xml requires castor = %version-%release geronimo-jetty-servlet-container requires geronimo = %version-%release geronimo-tomcat-servlet-container requires geronimo = %version-%release gnu-regexp-demo requires gnu-regexp = %version-%release jakarta-commons-httpclient3-demo requires jakarta-commons-httpclient3 = %version-%release jdepend-demo requires jdepend = %version-%release junit-demo requires junit = %version-%release jython-demo requires jython = %version-%release moodle-af requires moodle = %version-%release moodle-ar requires moodle = %version-%release moodle-be requires moodle = %version-%release moodle-bg requires moodle = %version-%release moodle-bs requires moodle = %version-%release moodle-ca requires moodle = %version-%release moodle-cs requires moodle = %version-%release moodle-da requires moodle = %version-%release moodle-de requires moodle = %version-%release moodle-de_du requires moodle = %version-%release moodle-el requires moodle = %version-%release moodle-es requires moodle = %version-%release moodle-et requires moodle = %version-%release moodle-eu requires moodle = %version-%release moodle-fa requires moodle = %version-%release moodle-fi requires moodle = %version-%release moodle-fr requires moodle = %version-%release moodle-ga requires moodle = %version-%release moodle-gl requires moodle = %version-%release moodle-he requires moodle = %version-%release moodle-hi requires moodle = %version-%release moodle-hr requires moodle = %version-%release moodle-hu requires moodle = %version-%release moodle-id requires moodle = %version-%release moodle-is requires moodle = %version-%release moodle-it requires moodle = %version-%release moodle-ja requires moodle = %version-%release moodle-ka requires moodle = %version-%release moodle-km requires moodle = %version-%release moodle-kn requires moodle = %version-%release moodle-ko requires moodle = %version-%release moodle-lt requires moodle = %version-%release moodle-lv requires moodle = %version-%release moodle-mi_tn requires moodle = %version-%release moodle-ms requires moodle = %version-%release moodle-nl requires moodle = %version-%release moodle-nn requires moodle = %version-%release moodle-no requires moodle = %version-%release moodle-pl requires moodle = %version-%release moodle-pt requires moodle = %version-%release moodle-ro requires moodle = %version-%release moodle-ru requires moodle = %version-%release moodle-sk requires moodle = %version-%release moodle-sl requires moodle = %version-%release moodle-so requires moodle = %version-%release moodle-sq requires moodle = %version-%release moodle-sr requires moodle = %version-%release moodle-sv requires moodle = %version-%release moodle-th requires moodle = %version-%release moodle-tl requires moodle = %version-%release moodle-tr requires moodle = %version-%release moodle-uk requires moodle = %version-%release moodle-vi requires moodle = %version-%release moodle-zh_cn requires moodle = %version-%release struts-webapps-tomcat5 requires struts = %version-%release tomcat55-admin-webapps requires tomcat55 = %version-%release tomcat55-common-lib requires tomcat55-servlet-2.4-api = %version-%release tomcat55-common-lib requires tomcat55-jsp-2.0-api = %version-%release tomcat55-common-lib requires tomcat55-jasper = %version-%release tomcat55-common-lib requires tomcat55-servlet-2.4-api = %version-%release tomcat55-common-lib requires tomcat55-jsp-2.0-api = %version-%release tomcat55-common-lib requires tomcat55-jasper = %version-%release tomcat55-jasper requires tomcat55-servlet-2.4-api = %version-%release tomcat55-jsp-2_0-api requires tomcat55-servlet-2.4-api = %version-%release tomcat55-server-lib requires tomcat55-jasper = %version-%release tomcat55-server-lib requires tomcat55-jasper = %version-%release tomcat55-webapps requires tomcat55 = %version-%release tomcat55 requires tomcat55-common-lib = %version-%release tomcat55 requires tomcat55-server-lib = %version-%release tomcat55 requires tomcat55-common-lib = %version-%release tomcat55 requires tomcat55-server-lib = %version-%release xalan-j2-demo requires xalan-j2 = %version-%release xerces-j2-demo requires xerces-j2 = %version-%release xerces-j2-scripts requires xerces-j2 = %version-%release xml-commons-apis requires xml-commons = %version-%release xml-commons-which requires xml-commons = %version-%release ConsoleKit-devel requires ConsoleKit = %version-%release NetworkManager-devel requires NetworkManager = %version-%release NetworkManager-devel requires NetworkManager-glib = %version-%release NetworkManager-glib requires NetworkManager = %version-%release NetworkManager-gnome requires NetworkManager = %version-%release NetworkManager-kde-devel requires NetworkManager-kde = %version-%release NetworkManager-novellvpn-gnome requires NetworkManager-novellvpn = %version-%release NetworkManager-openvpn-gnome requires NetworkManager-openvpn = %version-%release NetworkManager-openvpn-kde requires NetworkManager-kde = %version-%release NetworkManager-vpnc-gnome requires NetworkManager-vpnc = %version-%release NetworkManager-vpnc-kde requires NetworkManager-kde = %version-%release PolicyKit-gnome-demo requires PolicyKit-gnome = %version-%release anthy-devel requires anthy = %version-%release apt-devel requires apt = %version-%release apt-devel requires apt-libs = %version-%release apt-server requires apt-libs = %version-%release apt requires apt-libs = %version-%release audit-devel requires audit-libs = %version-%release audit requires audit-libs = %version-%release binutils-devel requires binutils = %version-%release bytefx-data-mysql requires mono-core = %version-%release bytefx-data-mysql requires mono-data = %version-%release camlp4 requires ocaml = %version-%release cimple-devel requires cimple = %version-%release cimple-openwbem-adapter requires cimple = %version-%release cimple-openwbem-devel requires cimple = %version-%release cimple-openwbem-devel requires cimple-openwbem-adapter = %version-%release cimple-openwbem-devel requires cimple-devel = %version-%release evolution-data-server-devel requires evolution-data-server = %version-%release evolution-devel requires evolution = %version-%release evolution-pilot requires evolution = %version-%release fftw-devel requires fftw = %version-%release fftw-mpi-devel requires fftw = %version-%release fftw-mpi requires fftw = %version-%release fftw-threads-devel requires fftw-threads = %version-%release fftw-threads-devel requires fftw-devel = %version-%release fftw-threads requires fftw = %version-%release fftw3-devel requires fftw3 = %version-%release fftw3-threads-devel requires fftw3-threads = %version-%release fftw3-threads-devel requires fftw3-devel = %version-%release fftw3-threads requires fftw3 = %version-%release file-devel requires file = %version-%release freeglut-devel requires freeglut = %version-%release freeradius-client-devel requires freeradius-client-libs = %version-%release freeradius-client requires freeradius-client-libs = %version-%release gcc41-32bit requires gcc41 = %version-%release gcc41-ada requires gcc41 = %version-%release gcc41-ada requires libada41 = %version-%release gcc41-c++ requires gcc41 = %version-%release gcc41-c++ requires libstdc++41-devel = %version-%release gcc41-fortran-32bit requires gcc41-32bit = %version-%release gcc41-fortran requires gcc41 = %version-%release gcc41-java requires gcc41 = %version-%release gcc41-locale requires gcc41 = %version-%release gcc41-obj-c++ requires gcc41-objc = %version-%release gcc41-obj-c++ requires gcc41-c++ = %version-%release gcc41-objc-32bit requires gcc41-32bit = %version-%release gcc41-objc requires gcc41 = %version-%release gcc41 requires cpp41 = %version-%release gcc42-32bit requires gcc42 = %version-%release gcc42-ada requires gcc42 = %version-%release gcc42-ada requires libada42 = %version-%release gcc42-c++ requires gcc42 = %version-%release gcc42-c++ requires libstdc++42-devel = %version-%release gcc42-fortran-32bit requires gcc42 = %version-%release gcc42-fortran requires gcc42 = %version-%release gcc42-java requires gcc42 = %version-%release gcc42-locale requires gcc42 = %version-%release gcc42-obj-c++ requires gcc42-objc = %version-%release gcc42-obj-c++ requires gcc42-c++ = %version-%release gcc42-objc-32bit requires gcc42 = %version-%release gcc42-objc requires gcc42 = %version-%release gcc42 requires cpp42 = %version-%release gcc43-32bit requires gcc43 = %version-%release gcc43-ada requires gcc43 = %version-%release gcc43-ada requires libada43 = %version-%release gcc43-c++ requires gcc43 = %version-%release gcc43-c++ requires libstdc++43-devel = %version-%release gcc43-fortran-32bit requires gcc43 = %version-%release gcc43-fortran requires gcc43 = %version-%release gcc43-java requires gcc43 = %version-%release gcc43-locale requires gcc43 = %version-%release gcc43-obj-c++ requires gcc43-objc = %version-%release gcc43-obj-c++ requires gcc43-c++ = %version-%release gcc43-objc-32bit requires gcc43 = %version-%release gcc43-objc requires gcc43 = %version-%release gcc43 requires cpp43 = %version-%release git-arch requires git-core = %version-%release git-cvs requires git-core = %version-%release git-email requires git-core = %version-%release git-svn requires git-core = %version-%release gitk requires git-core = %version-%release gnome-sharp2-complete requires art-sharp2 = %version-%release gnome-sharp2-complete requires gconf-sharp2 = %version-%release gnome-sharp2-complete requires gnome-sharp2 = %version-%release gnome-sharp2-complete requires gnome-vfs-sharp2 = %version-%release gnome-sharp2-complete requires gtkhtml-sharp2 = %version-%release gnome-sharp2-complete requires rsvg-sharp2 = %version-%release gnome-sharp2-complete requires vte-sharp2 = %version-%release gok-devel requires gok = %version-%release graphviz-gd requires graphviz = %version-%release graphviz-guile requires graphviz = %version-%release graphviz-java requires graphviz = %version-%release graphviz-lua requires graphviz = %version-%release graphviz-ocaml requires graphviz = %version-%release graphviz-perl requires graphviz = %version-%release graphviz-php requires graphviz = %version-%release graphviz-python requires graphviz = %version-%release graphviz-ruby requires graphviz = %version-%release graphviz-sharp requires graphviz = %version-%release graphviz-tcl requires graphviz = %version-%release gtk-sharp2-complete requires glade-sharp2 = %version-%release gtk-sharp2-complete requires glib-sharp2 = %version-%release gtk-sharp2-complete requires gtk-sharp2 = %version-%release gtk-sharp2-complete requires gtk-sharp2-doc = %version-%release gtk-sharp2-complete requires gtk-sharp2-gapi = %version-%release hal-devel requires hal = %version-%release ibm-data-db2 requires mono-core = %version-%release id3lib-devel requires id3lib = %version-%release java-1_4_2-cacao-devel requires java-1_4_2-cacao = %version-%release java-1_4_2-gcj-compat-devel requires java-1_4_2-gcj-compat = %version-%release java-1_4_2-ibm-demo requires java-1_4_2-ibm = %version-%release java-1_4_2-ibm-devel requires java-1_4_2-ibm = %version-%release java-1_4_2-ibm-src requires java-1_4_2-ibm = %version-%release java-1_5_0-ibm-demo requires java-1_5_0-ibm = %version-%release java-1_5_0-ibm-devel requires java-1_5_0-ibm = %version-%release java-1_5_0-ibm-src requires java-1_5_0-ibm = %version-%release java-1_5_0-sun-alsa requires java-1_5_0-sun = %version-%release java-1_5_0-sun-alsa requires jre-1.5.0-sun-64 = %version-%release java-1_5_0-sun-demo requires java-1_5_0-sun = %version-%release java-1_5_0-sun-demo requires jre-1.5.0-sun-64 = %version-%release java-1_5_0-sun-devel requires java-1_5_0-sun = %version-%release java-1_5_0-sun-devel requires jre-1.5.0-sun-64 = %version-%release java-1_5_0-sun-jdbc requires java-1_5_0-sun = %version-%release java-1_5_0-sun-jdbc requires jre-1.5.0-sun-64 = %version-%release java-1_5_0-sun-src requires java-1_5_0-sun = %version-%release java-1_5_0-sun-src requires jre-1.5.0-sun-64 = %version-%release java-1_6_0-ibm-demo requires java-1_6_0-ibm = %version-%release java-1_6_0-ibm-devel requires java-1_6_0-ibm = %version-%release java-1_6_0-ibm-jdbc requires java-1_6_0-ibm = %version-%release java-1_6_0-ibm-src requires java-1_6_0-ibm = %version-%release java-1_6_0-sun-alsa requires java-1_6_0-sun = %version-%release java-1_6_0-sun-demo requires java-1_6_0-sun = %version-%release java-1_6_0-sun-devel requires java-1_6_0-sun = %version-%release java-1_6_0-sun-jdbc requires java-1_6_0-sun = %version-%release java-1_6_0-sun-src requires java-1_6_0-sun = %version-%release kernel-syms requires kernel-source = %version-%release ksh-devel requires ksh = %version-%release labltk requires ocaml = %version-%release libapparmor-devel requires libapparmor1 = %version-%release libcfitsio-devel requires libcfitsio0 = %version-%release libcfitsio-doc requires libcfitsio0 = %version-%release libetpan-devel requires libetpan11 = %version-%release libnl-devel requires libnl = %version-%release libtidy-devel requires libtidy = %version-%release libunwind-devel requires libunwind = %version-%release libvolume_id-devel requires libvolume_id = %version-%release mono-complete requires bytefx-data-mysql = %version-%release mono-complete requires ibm-data-db2 = %version-%release mono-complete requires mono-core = %version-%release mono-complete requires mono-data = %version-%release mono-complete requires mono-data-oracle = %version-%release mono-complete requires mono-data-postgresql = %version-%release mono-complete requires mono-data-sqlite = %version-%release mono-complete requires mono-data-sybase = %version-%release mono-complete requires mono-extras = %version-%release mono-complete requires mono-locale-extras = %version-%release mono-complete requires mono-web = %version-%release mono-complete requires mono-winforms = %version-%release mono-data-firebird requires mono-core = %version-%release mono-data-firebird requires mono-data = %version-%release mono-data-oracle requires mono-core = %version-%release mono-data-oracle requires mono-data = %version-%release mono-data-postgresql requires mono-core = %version-%release mono-data-postgresql requires mono-data = %version-%release mono-data-sqlite requires mono-core = %version-%release mono-data-sqlite requires mono-data = %version-%release mono-data-sybase requires mono-core = %version-%release mono-data-sybase requires mono-data = %version-%release mono-data requires mono-core = %version-%release mono-devel requires mono-core = %version-%release mono-extras requires mono-core = %version-%release mono-jscript requires mono-core = %version-%release mono-locale-extras requires mono-core = %version-%release mono-nunit requires mono-core = %version-%release mono-web requires mono-core = %version-%release mono-winforms requires mono-core = %version-%release mozilla-nss-devel requires mozilla-nss = %version-%release ncurses-devel requires ncurses = %version-%release ocaml-docs requires ocaml = %version-%release ocaml-emacs requires ocaml = %version-%release ocaml-ocamldoc requires ocaml = %version-%release openwbem-devel requires openwbem = %version-%release powersave-devel requires powersave = %version-%release python-pygame-doc requires python-pygame = %version-%release sabayon-admin requires sabayon = %version-%release seahorse-devel requires seahorse = %version-%release smart-gui requires smart = %version-%release smart-ksmarttray requires smart = %version-%release smart-ksmarttray requires smart-gui = %version-%release splashy-themes requires splashy = %version-%release tack requires ncurses = %version-%release udev requires libvolume_id = %version-%release x11-input-gunze-tools requires x11-input-gunze = %version-%release x11-input-wacom-devel requires x11-input-wacom-tools = %version-%release x11-input-wacom-tools requires x11-input-wacom = %version-%release yum-updatesd requires yum = %version-%release

2 1

[opensuse-packaging] Standard way to install a font?
by Paul Elliott 06 Nov '07

06 Nov '07

Is there a standard way (a macro perhaps), to install a font? I have a spec file written by someone else that puts the following in %post: [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -a %{datadir}/fonts/default/Type1;\ [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -a %{datadir}/fonts/default/Type1/adobestd35;\ [ -x /usr/bin/fc-cache ] && /usr/bin/fc-cache Is this correct? Works with all distros? -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

2 1

[opensuse-packaging] New rpmlint check in BETA
by Dirk Mueller 06 Nov '07

06 Nov '07

Hi, as a followup of the discussion of yesterday: There is a new check in BETA which will check for missing prerequires for your %pre/%post/%preun%postun scripts. An example would be : kdemultimedia3-extra.i586: E: no-prereq-on coreutils for mv which says, that kdemultimedia3-extra contains a %post script that contains a call to "/bin/mv", however coreutils or /bin/mv is not in the prereq for that package. The check is fatal for repeated abuse. for (other) details, please refer to http://en.opensuse.org/Packaging/RpmLint Please file bugreports if you run accross a false positive/false negative/do not understand the report/etc. Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- 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] *-examples subpackage
by Petr Gajdos 06 Nov '07

06 Nov '07

Hi, it's not possible to have source files in *-examples subpackage in beta? Petr -- cut -- JFYI: package Source-Navigator failed to build in distribution beta-i386. Build started Thu 2007-11-01 10:34:56 on alsa2. http://w3d.suse.de/abuildstat/failed/beta-i386/Source-Navigator See /work/built/info/failed/beta-i386/Source-Navigator for details. tail -n 30 /work/built/info/failed/beta-i386/Source-Navigator E: Source-Navigator-examples.i586 devel-file-in-non-devel-package (Badness: 50) /opt/snavigator/share/demos/c++_demo/glish/Queue.h --- end cut --- --------------------------------------------------------------------- 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] RPM dependencies vs. post-install scripts
by Lukas Ocilka 06 Nov '07

06 Nov '07

Hi, I've found that some packages containing post-install scripts might not have defined RPM dependencies correctly. All those commands used in post-scripts should be explicitly requested. Please, correct me if I'm wrong :) --- examples --- 2007-10-31 19:20:46 lukemftp-1.5-660.x86_64.rpm installed ok Additional rpm output: /var/tmp/rpm-tmp.16471: line 1: rm: command not found 2007-10-31 19:21:50 preload-0.2-110.x86_64.rpm installed ok Additional rpm output: /var/tmp/rpm-tmp.11270: line 16: sed: command not found --- examples --- Please, check and fix your packages. Thanks Maybe someone could extend our 'build' scripts to check the post-install scripts whether they contain only commands (binaries) mentioned in RPM dependencies? Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

6 9

[opensuse-packaging] ... testing for pre/postinstall scripts that break patchrpms
by Bart Whiteley 05 Nov '07

05 Nov '07

Autobuild fails my package with the following error: ... testing for pre/postinstall scripts that break patchrpms postinstall script of <package>.rpm failed Can someone tell me what this might mean? That doesn't mean that the %post fails during a normal installation, right? But instead, some inspection of the script determined that it's not compatible with patchrpms? Any pointers on tracking down the problem? Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] [Info] libsmbios changes
by Danny Kukawka 05 Nov '07

05 Nov '07

Hi, JFYI: I have submitted a new libsmbios version (v0.13.12) to Factory. With this version all binaries of the package (from libsmbios-bin, libsmbios-unsupported-bin and libsmbiosxml-bin) are moved from /usr/bin to /usr/sbin. Please adapt your packages if they depend on one of these packages. I prepared HAL already to work also with this version. Danny -- Danny Kukawka dkukawka(a)suse.de Mobile Devices SUSE LINUX a Novell Business Maxfeldstr. 5, D-90409 Nuernberg, Germany SUSE LINUX Products GmbH, Nuernberg; 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

1 0

[opensuse-packaging] CentOS repository
by Leo Eraly 04 Nov '07

04 Nov '07

Hi, Would it be an option to add centOS repositories to the BS? Since there are already fedora repositories I assume it would be kinda straightforward to add a centos repository as well. Centos 5 is the latest release. More information about centos is available from www.centos.org Kind regards, Leo -- Leo Eraly <leo(a)unstable.be> --------------------------------------------------------------------- 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] conjunction Supplements for packages
by Stanislav Brabec 02 Nov '07

02 Nov '07

Hallo. I have more packages with following situation: I have package libgda It has libgda-mysql plugin I want to have libgda-mysql automatically selected, if if both libgda and mysql are going to be installed. I found page http://en.opensuse.org/Libzypp/Dependencies/Conjunctions But RPM does not accept Freshens: keyword. Is there any way to do it? -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- 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] please review your *rpmlintrc rules
by Dirk Mueller 02 Nov '07

02 Nov '07

Hi, rpmlint 0.81 has changed the output format: E: package check-id detail was the old format. the new format is <package>.<arch>:<lineno> E: check-id detail The new format is going to be active with the next checkin round to BETA. Please review your personal rpmlintrc rules and adapt them accordingly. I plan to merge the new checker, which has many improvements to Factory, within the next week and will cause new failures. I`ve fixed the non-leaf packages already myself. Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- 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] /usr/local/bin/perl dependency weirdness
by Günter Dannoritzer 01 Nov '07

01 Nov '07

Hi, I have some weired requirement to my systemc package that I built through the build service. Here is one of the packages for example: http://download.opensuse.org/repositories/home:/dannori/openSUSE_10.2/x86_6… When I do: > rpm -qp --requires systemc-2.2.0-5.1.x86_64.rpm gcc gcc-c++ rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /bin/awk /bin/csh /bin/sh /usr/local/bin/perl rpmlib(PayloadIsBzip2) <= 3.0.5-1 Now where does that /usr/local/bin/perl requirement come from? In my spec file I only specified that it requires gcc and gcc-c++. Now that I want to install the package, I am getting an error about nothing providing /usr/local/bin/perl. Where does that requirement come from? Has it to do with rpmlib? Thanks for your help. Cheers, Guenter --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 4

[opensuse-packaging] %debug_package issues with Suse only
by mrdocs＠scribus.info 01 Nov '07

01 Nov '07

Sent originally to -buildservice by mistake.... Hi, I have hit a weird issue when enabling %debug_package when wrapped inside something like this: %if 0%{?suse_version} %debug_package Build Requires: blah... %endif If %debug_package is enabled, the install portion fails on all Suse versions by seemingly unsetting RPM_BUILD_ROOT so the install part tries to install into /usr not /var/tmp/package/usr Package in question is: https://build.opensuse.org/package/show?project=home%3Amrdocs&package=gsview Now Mandriva seems to automagically enable debug packages, so there is no need to enable it in the spec file. This package has reliably built before on OBS on all rpm distros and arches. Is this a subtle difference in the rpm versions from FC. Mdk and Suse ? or could this be an OBS issue? Thoughts ? Thanks, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1