- openSUSE Packaging

[opensuse-packaging] old version of SPC online
by Anna Bernathova 10 Jul '07

10 Jul '07

Hello, when we were migrating SPC into wiki (see my last mail), we unfortunately uploaded an older revision of the document. Please do not edit it until we upload the current version, which should be done ASAP. Anicka -- Best Regards, Anna Bernathova, software developer --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: anicka(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 965 190 00 Prague 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

3 2

[opensuse-packaging] Wiki page: Czech Packagers Team
by Petr Gajdos 09 Jul '07

09 Jul '07

Hello, I would like to announce our wiki page, which has two main purposes: * briefly introduce Czech packagers team and * ask for help in maintainance of several packages in BuildService. If you are interested in, please see http://en.opensuse.org/Czech_Packagers_Team Petr --------------------------------------------------------------------- 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] RPM license header update
by Juergen Weigert 09 Jul '07

09 Jul '07

Hi all! RPM packages have a one-liner header field to store license information. You see this with "rpm -q --qf '%{License}\n' <name>' or in 'rpm -qi <name>'. With our SuSE Linux products, the quality of the entries there was not optimal, since we were restricted to a choice of ca. 20 predefined texts. We now have changed how license information is compiled into the RPM package header, and support an arbitrary number of license settings. I'd appreciate everbodys help in representing licenses (as defined by upstream) more accuratly in our RPM headers. First, I'd like to eliminate texts like 'Contact author', 'No license agreement found', 'Other license, see package'. Please hunt them down and report to legal-devel(a)suse.de Second, Please check the exact version of the GPL and LGPL. We used to have one general entry 'GNU General Public License', now we have four entries: 'GPLv2 only', 'GPLv2 or later', 'GPLv3 only', 'GPLv3 or later'. Most GPL packages are now listed as 'GPLv2 or later', please adjust or let us know (again legal-devel(a)suse.de) where this is incorrect. Same logic applies to LGPL. thanks, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw(a)suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8 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

3 3

[opensuse-packaging] Changing YaST Packages in Autobuild
by Lukas Ocilka 09 Jul '07

09 Jul '07

Hi, It happens time to time that someone needs to urgently change some YaST package in autobuild. This is actually possible but you should know that autobuild is not the primary source of YaST packages. Our primary source is our SVN: http://svn.opensuse.org/svn/yast/ First, you had better contact the MAINTAINER of the package and consult the change with him/her. You can change the package in autobuild but you need to send a diff file to the maintainer or change SVN as well. Please, NEVER submit a changed package to autobuild without announcing the change to the maintainer of the package and without providing the patch or changing the source directly in SVN. Thanks & 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] e2fsprogs library branch off
by Matthias Koenig 05 Jul '07

05 Jul '07

Hi, with the recent update of e2fsprogs to version 1.40, the libraries have been branched off from the package, the following e2fsprogs packages do exist now: e2fsprogs libext2fs2 libblkid1 libuuid1 libcom_err2 with the development packages: libext2fs-devel libblkid-devel libuuid-devel libcom_err-devel If your package build requires one of the libraries please adjust your BuildRequires tag with the next touch of your package. For smooth transition there is still a dummy e2fsprogs-devel package which just pulls in the devel packages previously been in there, so in theory there should no immediate action required. Matthias --------------------------------------------------------------------- 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] updated update-desktop-files
by Stephan Kulow 05 Jul '07

05 Jul '07

Hi! I changed update-desktop-files do not provide "templates" and icons anymore. I tried to change and submit every package from factory that relies on this feature, but I might have missed some. In this case your package will fail in %suse_update_desktop_file - in this case you need to copy the file from ~coolo/Export/update-desktop-files. I sure hope no package in the build service relies on this, in this case you need to install 10.2's update-desktop-files and copy from there. 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

1 0

[opensuse-packaging] SUSE Package Conventions in openSUSE wiki
by Anna Bernathova 03 Jul '07

03 Jul '07

Hello, I am gladly announcing that we are going to share maintaining of SUSE Package Conventions together with the openSUSE community. You will find them in openSUSE wiki now: http://en.opensuse.org/SUSE_Package_Conventions I hope you will get involved and help with making this document as precise and complete, as possible. Enjoy! Anicka Best Regards, Anna Bernathova, software developer --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: anicka(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 965 190 00 Prague 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] Handling rpmlintrc files in packages
by Lars Vogdt 02 Jul '07

02 Jul '07

Hi Packagers As we add more and more rpmlintrc-files to our packages to deal with rpmlint warnings and errors, I think we should clarify some things here and afterwards add a new chapter to the packagers manual and the rpmlint site on en.opensuse.org. 1) Name your rpmlintrc-file! Please _do_not_ add a plain rpmlintrc file to your package! Think about installing multiple src.rpms on your system: the last rpmlintrc will win... (yes, we should discuss the "installing src.rpms in an extra directory" problematic - but not within this mail ;-) So please follow the description on http://en.opensuse.org/Packaging/RpmLint and name your rpmlintrc file: %{name}-rpmlintrc or %{name}-%{version}-rpmlintrc 2) Add your rpmlintrc file to your specfile Please add a line like: Source100: %{name}-%{version}-rpmlintrc to your specfile. Otherwise both the check_if_valid_source_dir script will fail and autobuild will reject to check in your package. Adding the rpmlintrc file as source will also add it to the src.rpm - so other packagers outsite can have a look at it and perhaps came up with a better solution. Any other/better suggestions about rpmlintrc-files are welcome! Regards, Lars -- Lars Vogdt <lrupp(a)suse.de> Autobuild Team SUSE Linux Products GmbH GF: Markus Rex Nuernberg, Germany 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] icecream cross compile
by Peter Czanik 26 Jun '07

26 Jun '07

Hello, I was compiling Packman packages for PowerPC for more than a year. Then my PPC machine broke and my first son was born, so I did not have a machine or time to do it. Now I have a bit more time and a strong X86 machine, so I would like to resume this activity. I looked at http://en.opensuse.org/Icecream and compiling on machines of the same architecture works fine. I have now a small cluster of embedded PPC machines :-) Of course, the ultimate goal would be to use the X86 monster to compile PPC packages. My problem is, that it's not clear from the above mentioned documentation, that which cross-xxx-icecream packages should I install on X86 and PPC and how I should parameter ICECC_VERSION. Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] Call for testing
by Stephan Hermann 25 Jun '07

25 Jun '07

Good Morning, I packaged nexuiz for opensuse 10.2/openSuSE:Factory...and I'm calling for testers for these packages. Coming from the debian side of life, I used the debian sources for packaging, with the difference, that the source package isn't divided into two source packages but one. The nexuiz version is the latest stable release and it works for me (tm) ;) Have fun testing it...if you have any problems, please send me bugreports to the mentioned communication channels in my .sig. Thx for your help, \sh -- Stephan Hermann eMail: sh(a)sourcecode.de Blog: http://linux.blogweb.de/ JID: sh(a)linux-server.org OSS-Developer and Admin

2 3