March 2015 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Python 2 and 3 in single specfile
by Jan Matějek 22 Jul '15

22 Jul '15

Fellow packagers, after some discussions in our team, we figured that it would be neat if we could build python modules for Python 2 and 3 from a single spec file. Now that a great deal of python modules work with both pythons, this makes a lot of sense. A good deal of work can be done by RPM macros. Then we could even seamlessly start building modules for PyPy, Jython and other pythons. A sample specfile, and the corresponding set of RPM macros, is attached. As you can see, the appropriate subpackage is generated automatically by %python_subpackages, build and install steps are handled through %python_build and %python_install respectively. There is some more magic involved, as well as possibilities for customization. There is a minor problem with BuildRequires. As long as you only need python-devel, it's not too bad to just list $flavor-devel requirements by hand. It's worse when you require more subpackages, because then you need all of them in both python2 and python3 versions. It would be nice to be able to specify %{python_require Mako} and expand that to all the necessary BuildRequires, but OBS blocks us here, because the limited environment will not expand such macros. mls, ro, or anyone from the OBS team, would it be possible to solve this? Still, it basically doesn't matter if you list all the BuildRequires twice in one spec or in two specs, so there. Another thing I'm still unclear on are the filelists. It's certainly possible to make a generic filelist, something along the lines of: %package -n %flavor-%modname # python3-Mako %defattr(-, root, root) %{%flavor_sitelib}/* %{%flavor_sitearch}/* but this doesn't solve docs and possible other files. Again, obviously, we can write the filelists by hand. But if you have good suggestions for some smart macros here, I'd love to see them. What do you folks think? Comments, questions? m.

3 5

[opensuse-packaging] What needs to be changed in specfiles to allow 64 bit modules to be used instead of 32 bit ones [using opensuse x86_64 system to install on] ?
by doiggl＠velocitynet.com.au 17 Apr '15

17 Apr '15

Hello, What needs to be changed in specfiles [1] to allow 64 bit modules to be used instead of 32 bit ones [using opensuse x86_64 system to install on] ? usimg opensuse 13.x Thank you. --Glenn # uname -a Linux test.site 3.10.1-3.g0cd5432-desktop #1 SMP PREEMPT Fri Jul 19 14:39:31 UTC 2013 (0cd5432) x86_64 x86_64 x86_64 GNU/Linux Thank you. --Glenn # rpm -ivhU bugzilla-4.5.1-30.1.noarch.rpm error: Failed dependencies: perl-Email-MIME >= 1.816 is needed by bugzilla-4.5.1-30.1.noarch perl-Email-MIME-Modifier >= 1.442 is needed by bugzilla-4.5.1-30.1.noarch # rpm -ivhU bugzilla-4.5.1-30.1.noarch.rpm error: Failed dependencies: perl-Email-MIME >= 1.816 is needed by bugzilla-4.5.1-30.1.noarch perl-Email-MIME-Modifier >= 1.442 is needed by bugzilla-4.5.1-30.1.noarch [1]specfiles: https://build.opensuse.org/package/view_file/home:doiggl/bugzilla/bugzilla.… https://build.opensuse.org/package/view_file/home:doiggl/perl-Email-MIME-Mo… Packages: https://build.opensuse.org/package/show/home:doiggl/bugzilla https://build.opensuse.org/package/show/home:doiggl/perl-Email-MIME-Modifier Source rpms built: http://ftp5.gwdg.de/pub/opensuse/repositories/home:/doiggl/openSUSE_13.2/sr… http://download.opensuse.org/repositories/home:/doiggl/openSUSE_Factory/src… 64 bit opensuse perl modules installed ##################################### # rpm -qa |grep -i perl |sort perl-5.18.1-2.1.11.x86_64 perl-AppConfig-1.66-103.1.2.noarch perl-Bootloader-0.711-1.1.x86_64 perl-Config-Crontab-1.33-6.3.noarch perl-Crypt-SmbHash-0.12-154.3.x86_64 perl-DBI-1.628-2.1.4.x86_64 perl-Data-Dump-1.22-1.2.noarch perl-Digest-HMAC-1.03-16.3.noarch perl-Digest-MD4-1.9-1.3.x86_64 perl-Digest-SHA1-2.13-15.4.x86_64 perl-Email-Date-Format-1.004-2.1.2.noarch perl-Email-Simple-2.201-2.1.2.noarch perl-Encode-Locale-1.03-5.4.noarch perl-File-Listing-6.04-5.3.noarch perl-HTML-Parser-3.69-16.5.x86_64 perl-HTML-Tagset-3.20-69.3.noarch perl-HTML-Tidy-1.54-3.4.x86_64 perl-HTTP-Cookies-6.01-5.3.noarch perl-HTTP-Daemon-6.01-5.3.noarch perl-HTTP-Date-6.02-5.4.noarch perl-HTTP-Message-6.02-10.3.noarch perl-HTTP-Negotiate-6.01-5.3.noarch perl-IO-Socket-SSL-1.953-1.2.noarch perl-LWP-MediaTypes-6.02-5.3.noarch perl-LWP-Protocol-https-6.04-1.1.noarch perl-MIME-Types-1.34-6.1.2.x86_64 perl-Net-DBus-1.0.0-6.6.x86_64 perl-Net-HTTP-6.06-1.3.noarch perl-Net-LibIDN-0.12-12.4.x86_64 perl-Net-SSLeay-1.55-1.1.x86_64 perl-NetxAP-0.02-718.3.x86_64 perl-Parse-RecDescent-1.967009-5.3.x86_64 perl-Pod-POM-0.28-2.1.2.noarch perl-SNMP-5.7.2-9.8.1.x86_64 perl-Template-Toolkit-2.25-2.1.2.x86_64 perl-Term-ReadKey-2.30-10.1.4.x86_64 perl-Text-Wrapper-1.04-1.2.noarch perl-Tie-IxHash-1.23-1.2.noarch perl-TimeDate-1.20-22.3.noarch perl-URI-1.60-5.4.noarch perl-WWW-RobotRules-6.02-5.3.noarch perl-X11-Protocol-0.56-10.3.x86_64 perl-X500-DN-0.29-104.2.x86_64 perl-XML-LibXML-2.0019-1.3.x86_64 perl-XML-NamespaceSupport-1.11-19.3.x86_64 perl-XML-Parser-2.41-19.5.x86_64 perl-XML-SAX-0.99-20.3.x86_64 perl-XML-SAX-Base-1.08-6.7.noarch perl-XML-SAX-Expat-0.50-1.2.noarch perl-XML-Simple-2.20-1.2.noarch perl-XML-Twig-3.44-1.3.noarch perl-XML-Writer-0.623-1.2.noarch perl-XML-XPath-1.13-97.3.x86_64 perl-XML-XPathEngine-0.14-1.2.noarch perl-base-5.18.1-2.1.11.x86_64 perl-gettext-1.05-161.4.x86_64 perl-libwww-perl-6.05-1.2.noarch yast2-perl-bindings-3.0.1-3.1.x86_64 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 14

[opensuse-packaging] Upcoming transition to GCC 5
by Richard Biener 09 Apr '15

09 Apr '15

Hi, we are currently trying to get openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX clean to build with GCC 5 in the openSUSE:Factory:Staging:Gcc49 project. Once that works reasonably I will push GCC 5 to Factory without enabling it as a default - that will be done when it works fully (help appreciated at that point). There is a porting-to document that explains some issues you may run into (also consider the 4.9 variant as we didn't transition to that): https://gcc.gnu.org/gcc-5/porting_to.html https://gcc.gnu.org/gcc-4.9/porting_to.html You may also find the analysis of Fedora interesting which explains why some packages now fail to build: https://lists.fedoraproject.org/pipermail/devel/2015-February/207549.html GCC 5 packages can be installed from devel:gcc where they are regularly updated. Those sources also feed openSUSE:Factory:Staging:Gcc49. Richard. -- Richard Biener <rguenther(a)suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 16

[opensuse-packaging] Troubles with AM_INIT_AUTOMAKE macro
by Benjamin Denisart 01 Apr '15

01 Apr '15

Hello, I'm trying for a while to package h323plus, to be able to push new versions of opal's softs to openSUSE but i'm not able to process an autoconf or autoreconf correctly. If I run autoreconf -fiv, the output tells me there is no makefile.am for configure output and if I run autoconf --force, the output tells me : "error: possibly undefined macro: AM_INIT_AUTOMAKE". I've tried to fix it with suggests from forums when this error appens like with this patch : --- a/configure.ac 2014-03-26 00:58:15.000000000 +0100 +++ b/configure.ac 2015-03-30 17:03:20.135824631 +0200 @@ -1,4 +1,10 @@ -AC_INIT(include/h323.h) +AC_INIT([h323plus], [1.26.5]) +AC_CONFIG_SRCDIR([include/h323.h]) +AM_INIT_AUTOMAKE + +AC_CONFIG_MACRO_DIR([m4]) + +LT_INIT AC_PROG_CXX AC_HEADER_STDC but nothing's better. So if someone could help me, many thanks in advance. The package lives in home:posophe:branches:network:telephony/h323plus . Regards. Benjamin -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 16

[opensuse-packaging] file conflicts kernel update on Tumbleweed
by Michael Ströder 31 Mar '15

31 Mar '15

HI! The second kernel update after upgrading to Tumbleweed results in file conflicts: File /boot/.vmlinuz-3.19.2-1-desktop.hmac from install of kernel-desktop-3.19.2-1.2.x86_64(openSUSE-20150311-0) conflicts with file from package kernel-desktop-3.19.2-1.1.x86_64(@System) File /boot/vmlinux-3.19.2-1-desktop.gz from install of kernel-desktop-3.19.2-1.2.x86_64(openSUSE-20150311-0) conflicts with file from package kernel-desktop-3.19.2-1.1.x86_64(@System) File /boot/vmlinuz-3.19.2-1-desktop from install of kernel-desktop-3.19.2-1.2.x86_64(openSUSE-20150311-0) conflicts with file from package kernel-desktop-3.19.2-1.1.x86_64(@System) What's going on here? Ciao, Michael.

4 4

[opensuse-packaging] Package integration into AppStream based stores
by Dominique Leuenberger / DimStar 31 Mar '15

31 Mar '15

Dear Packagers, Since recently, openSUSE Tumbleweed has a new generator for AppStream Metadata, which processes all RPMs during the Repository creation. What uses AppStream Metadata **************************** The metadata describes what 'Applications' can be found in a repository, rather than what packages. As such, it's obvious target is 'Software Centers'. At this moment, GNOME Software is the only Software center shipped in openSUSE Tumbleweed that makes use of this metadata. But I heard of a KDE Software Center in 'the works' as well. So this is not GNOME Thing. What does my package have to provide to be shown in the Software Center *********************************************************************** AS a bare minimum, the package containing the application must have a .desktop file (sounds almost obvious). If nothing else, the .destop file must have a Name, Generic Name and Comment field to describe the app at a bare minimum. The package must contain an icon, of at least 32x32 pxels (64x64 preferred). The icon must be installed below /usr/share/icons/ or /usr/share/pixmaps. It must not be referenced from the .desktop file by an absolute path outside these locations. Also, it must be a real file, not a symlink to a file outside /usr/share/{icons,pixmaps}. The same is also required by another project, called 'xdg-app', which aims at containerizing applications (using ostree and nspawn). Icons must be accessible in the defined locations. Optional: The applicstion can present itself with much better information in the Software Center (incl. Screenshots, work in progress for openSUSE). In this case, the package containing the .desktop file has to also install a .appdata.xml file. The specification for the appdata format can be found at http://people.freedesktop.org/~hughsient/appdata/ Which applications do currently show up inthe Software Center ************************************************************* As a human aid, the metadata generator also outputs a HTML File, which can be found at http://download.opensuse.org/tumbleweed/repo/oss/suse/setup/descr/appdata.h… My package does not show in the SC ********************************** Ensure all the pre-requisites are met. You can also check http://download.opensuse.org/tumbleweed/repo/oss/suse/setup/descr/appdata-f… which generally contains information of a 'veto', why a package was skipped to be added to the AppStream metadata. Most common one is "No 'Comment' in desktop or in AppData" Is it mandatory for my package to provide all this ************************************************** At this moment it is not mandated, but is surely a good thing for the users. Packages are fine from a technical PoV, but they are not what a user should have to care for. Allowing to work in an 'Application' view is more helpful in the long run. Should you have any questions, simply ask, Cheers, Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5

[opensuse-packaging] Packaging day(s?) at oSC 2015
by Lars Vogdt 30 Mar '15

30 Mar '15

Hi @ll You hopefully know already that the openSUSE Conference[1] in The Hague from May 01 - 04, 2015 will also have some nice talks and workshops around packaging. Currently we plan to organize a whole day with presentations and workshops around packaging from beginner sessions to discussions with experts around everything you can imagine (especially after a few beers ;-) As YOU are the core target audience, it would be very cool if we can get your attention - and you already can start helping us with your input... Are there any topics that you want to get covered during the openSUSE Conference? Please note that we plan to do recording, so even if you do not participate directly, you might get your questions answered via Video. with kind regards, Lars -- [1]: https://events.opensuse.org/conference/oSC15 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 1

[opensuse-packaging] Another appeal
by Robert Schweikert 30 Mar '15

30 Mar '15

Hi, I know we have had this discussion/appeal before but it appears it has not reached everyone yet. To those that have the power to accept SRs on the behalf of others please be so kind and give package maintainers at least a few days before you accept submit request. What is the point of having individual package maintainers when those at the project maintainer or higher level simply accept submit requests for package that they do not really maintain? This is a discouraging practice and unless as a project maintainer you have the intention to maintain all those packages in the project yourself I suggest you exercise restraint for a few days before you run that accept command. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei(a)suse.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 12

[opensuse-packaging] What fixes these errors. [ for mysql-workbench ]
by doiggl＠velocitynet.com.au 28 Mar '15

28 Mar '15

Hello, What fixes these errors. [ for mysql-workbench ] Thanks --Glenn package: https://build.opensuse.org/package/show/home:doiggl/mysql-workbench BuildRequires: libgdal-devel unresolvable: nothing provides libgdal-devel Specfile: https://build.opensuse.org/package/view_file/home:doiggl/mysql-workbench/my… buildlog: https://build.opensuse.org/package/live_build_log/home:doiggl/mysql-workben… [ 211s] Using bundled Antlr C runtime [ 211s] Generating mysql.parser files... [ 211s] The antlr-3.4-complete.jar file could not be found. [ 211s] Please make sure that linux-res is in /home/abuild/rpmbuild/BUILD or add the ANTLR_JAR_PATH enviroment variable with the path to the file. [ 211s] You'll also need Java Runtime Enviroment installed, so the parser files can be regenerated. [ 211s] CMake Error at library/mysql.parser/grammar/CMakeLists.txt:9 (message): [ 211s] Generating mysql.parser files failed with result='1' [ 211s] [ 211s] [ 211s] -- Configuring incomplete, errors occurred! [ 211s] See also "/home/abuild/rpmbuild/BUILD/mysql-workbench-community-6.2.5-src/build/CMakeFiles/CMakeOutput.log". [ 211s] See also "/home/abuild/rpmbuild/BUILD/mysql-workbench-community-6.2.5-src/build/CMakeFiles/CMakeError.log". [ 211s] error: Bad exit status from /var/tmp/rpm-tmp.yyYoUf (%build) [ 211s] [ 211s] [ 211s] RPM build errors: [ 211s] Bad exit status from /var/tmp/rpm-tmp.yyYoUf (%build) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Can the bluefish repos be updated to version 2.2.7 please.
by doiggl＠velocitynet.com.au 27 Mar '15

27 Mar '15

Hello, Can the bluefish repos be updated to version 2.2.7 please. --Glenn - Here is bluefish 2.2.7 with build completed ok for opensuse 13.2. https://build.opensuse.org/package/show/home:doiggl/bluefish - see bitmaps. # - Here is a list of bluefish repositories with older version builds [to 2.2.6 or older - using search] that may be updated to 2.2.7 https://build.opensuse.org/package/show/editors/bluefish Bluefish is a HTM... Package package editors / bluefish Bluefish is a HTML editor designed for the experienced Web designer. It is ba... Package package Education / bluefish Bluefish is a HTML editor designed for the experienced Web designer. It is ba... Package package home:malcolmlewis:SLE_12_General / bluefish Bluefish is a HTML editor designed for the experienced Web designer. It is ba... Package package openSUSE:13.2 / bluefish Bluefish is a HTML editor designed for the experienced Web designer. It is ba... Package package openSUSE:Factory / bluefish Bluefish is a HTML editor designed for the experienced Web designer. It is ba... Package package openSUSE:13.1 / bluefish Bluefish is a HTML editor designed for the experienced Web designer. It is ba... Package package home:PSerkov / Bluefish Package package home:BryanLester / Bluefish Bluefish is a powerful editor targeted towards programmers and webdesigners, ... Package package openSUSE:12.3 / bluefish Bluefish is a HTML editor designed for the experienced Web designer. It is ba... Package package home:please_try_again / bluefish Bluefish is a powerful editor targeted towards programmers and webdesigners, ... Package package home:tasq271 / bluefish Package package home:pkreussel:EasyLinux / bluefish Package package home:natuchmaster903 / bluefish Blue fish is, a popular html editor Package package Education / bluefish-doc Bluefish: The Definitive Guide Package package Education / bluefish-unstable Bluefish is a HTML editor designed for the experienced Web designer. Package package editors / bluefish-unstable Bluefish is an HTML editor designed for the experienced Web designer. Project project home:tasq271:bluefish

2 1