July 2007 - openSUSE Packaging - openSUSE Mailing Lists

[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