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

[opensuse-packaging] How can following error be fixed. error: Installed (but unpackaged) file(s) found.
by doiggl＠velocitynet.com.au 26 Mar '15

26 Mar '15

Hello, How can following error be fixed. Thanks. --Glenn [ 367s] Provides: bluefish-debuginfo = 2.2.7-27.1 bluefish-debuginfo(x86-64) = 2.2.7-27.1 debuginfo(build-id) = 33d64a2efb6d435d4030e0238a393e4657c82557 debuginfo(build-id) = 3da20a034b5270145c229d3b570fcd9196d878ad debuginfo(build-id) = 589934c4e86cb3abeab34737e72e5878ce319292 debuginfo(build-id) = 5f44b139da0a20a039580ca393ac3f6275dfe8c8 debuginfo(build-id) = b29515060e58a8c9beb50299c0c667185d7bd53c debuginfo(build-id) = d39e22f8d866921b33e4ac0b0060b6f5d43941a1 debuginfo(build-id) = db464483b2642547a9ae49d01e89c733c7fe665a [ 367s] Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 [ 367s] Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/abuild/rpmbuild/BUILDROOT/bluefish-2.2.7-27.1.x86_64 [ 367s] error: Installed (but unpackaged) file(s) found: [ 367s] /usr/share/mime/packages/bluefish.xml - Does it go in this section ? %files -f all.lang %defattr(-,root,root) . . . %{_datadir}/usr/share/mime/packages/bluefish.xml [1] .spec file https://build.opensuse.org/package/view_file/home:doiggl/bluefish/bluefish.… [2] build log https://build.opensuse.org/package/live_build_log/home:doiggl/bluefish/open… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Policy about Source tags and URLs
by Cristian Morales Vega 26 Mar '15

26 Mar '15

I have been very little active for a while. I have SR#290195 changing Source0: https://github.com/LMMS/lmms/archive/v%{version}.tar.gz for Source0: https://github.com/LMMS/lmms/archive/%{name}-%{version}.tar.gz Since the new version has been created in the author's machine through git. The thing is that https://github.com/LMMS/lmms/archive/%{name}-%{version}.tar.gz doesn't exist. There will be some source service (download_files?) in openSUSE:Factory that will complain? And what's the current policy about this? a) The SR is OK b) If upstream offers a tarball, even if with a weird name, it must be used c) It's acceptable to use "git archive" like this, but fake URLs are not. Just use "Source0: %{name}-%{version}.tar.gz" d) None of the others Thanks. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 4

[opensuse-packaging] Re: [opensuse-factory] Avoid use of %systemd_requires
by Jan Engelhardt 25 Mar '15

25 Mar '15

Ccing opensuse-packaging. On Wednesday 2015-03-18 14:36, Jan Engelhardt wrote: > >TLDR: I would ask to not use %systemd_requires in your .spec >files anymore - they impose a dependency on systemd even though the >programs per se do not require systemd in all case to run. > > >Long story: >While playing around with containers, I set myself up one for the >purpose of running a single application in it (boinc-client if you want >to know). This is reasonably easy to pull off: > >1. mkdir /compute >2. Populate /compute/etc/zypp/repos.d >3. Populate with a basic /etc/passwd & /etc/group so that installed > files don't revert to root during installation. One can use > `zypper -R /compute in --no-r aaa_base && rm -Rf > /compute/var/lib/rpm` to that effect... >4. zypper -R /compute in --no-r aaa_base >5. zypper -R /compute in --no-r boinc-client >6. Create a user account in /compute (e.g. useradd). >6. systemd-nspawn -D /compute -u jengelh /bin/sh -c 'cd /home/jengelh; >exec /usr/bin/boinc_client' > >That works really nice. I love it - it is a minimal system, like >security-concious people want it. Well, almost. The boinc-client >package requires systemd due to use of %systemd_requires in its >specfile. However, there is nothing in the boinc package that depends >soooo much on systemd that the program won't run without its >presence. > >I therefore think that we can omit using that macro from specfiles, >as "regular" systems (installed via YAST/kiwicds) will cause >installation of an init implementation through their static patterns >anyway. >The %systemd_* macros in %pre,%post,etc. can all deal with the >absence of systemd. > >An issue I can imagine is that if a packages does not explicitly >Requires systemd, then, in an unpopulated system, systemd might be >installed after the program package, and the `systemctl preset ..` >commands as part of %service_add_post won't do anything. > > >Comments..? >-- >To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] are download statistics available for a specific project/package?
by Johannes Meixner 25 Mar '15

25 Mar '15

Hello, last Friday I had Printing/ghostscript upgraded to Ghostscript version 9.16 release candidate 2 I like to know a rough number of how many times its binary RPM(s) have been downloaded since last Friday. Reason: I would like to get a rough estimate how many users use it which would help me to get an idea if it seems to work o.k. or if there are obvious issues with that version upgrade. It is meaningless when I get no bug report but it was only less than about 100 times downloaded in contrast to when I get no bug report and it was more than about 10000 times downloaded. I only know about the inactive https://features.opensuse.org/308540 where it seems no download statistics are available but perhaps I am wrong ( hope dies last ;-) Kind Regards Johannes Meixner -- 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

2 1

[opensuse-packaging] getting bluefish-2.2.7 to build.
by doiggl＠velocitynet.com.au 25 Mar '15

25 Mar '15

Hello, bluefish-2.2.7 build fails while bluefish-2.2.6 build passes. All I change is Version: {from 2.2.6 to 2.2.7} What other changes allow Version 2.2.7 to build ? Thanks --Glenn Spec: https://build.opensuse.org/package/view_file/home:doiggl/bluefish/bluefish.… Full build log: https://build.opensuse.org/build/home:doiggl/openSUSE_13.2/x86_64/bluefish/… Build log bluefish-2.2.7 build -fail ################################### [ 365s] Obsoletes: bluefish-unstable < 2.2.3 [ 365s] Processing files: bluefish-debugsource-2.2.7-18.1.x86_64 [ 365s] Provides: bluefish-debugsource = 2.2.7-18.1 bluefish-debugsource(x86-64) = 2.2.7-18.1 [ 365s] Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 [ 365s] Processing files: bluefish-debuginfo-2.2.7-18.1.x86_64 [ 365s] warning: File listed twice: /usr/lib/debug/.build-id [ 365s] warning: File listed twice: /usr/lib/debug/.build-id [ 365s] warning: File listed twice: /usr/lib/debug/.build-id [ 365s] warning: File listed twice: /usr/lib/debug/.build-id [ 365s] warning: File listed twice: /usr/lib/debug/.build-id [ 365s] warning: File listed twice: /usr/lib/debug/.build-id [ 365s] Provides: bluefish-debuginfo = 2.2.7-18.1 bluefish-debuginfo(x86-64) = 2.2.7-18.1 debuginfo(build-id) = 33d64a2efb6d435d4030e0238a393e4657c82557 debuginfo(build-id) = 589934c4e86cb3abeab34737e72e5878ce319292 debuginfo(build-id) = 5f44b139da0a20a039580ca393ac3f6275dfe8c8 debuginfo(build-id) = b29515060e58a8c9beb50299c0c667185d7bd53c debuginfo(build-id) = d39e22f8d866921b33e4ac0b0060b6f5d43941a1 debuginfo(build-id) = db464483b2642547a9ae49d01e89c733c7fe665a debuginfo(build-id) = e91bbf5aefb9fb6c91aa3c3021f467a5de45a927 [ 365s] Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 [ 365s] Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/abuild/rpmbuild/BUILDROOT/bluefish-2.2.7-18.1.x86_64 [ 365s] Wrote: /home/abuild/rpmbuild/SRPMS/bluefish-2.2.7-18.1.src.rpm [ 377s] Wrote: /home/abuild/rpmbuild/RPMS/x86_64/bluefish-2.2.7-18.1.x86_64.rpm [ 380s] Wrote: /home/abuild/rpmbuild/RPMS/x86_64/bluefish-debugsource-2.2.7-18.1.x86_64.rpm [ 383s] Wrote: /home/abuild/rpmbuild/RPMS/x86_64/bluefish-debuginfo-2.2.7-18.1.x86_64.rpm [ 383s] Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.kaJlCa [ 383s] + umask 022 [ 383s] + cd /home/abuild/rpmbuild/BUILD [ 383s] + cd bluefish-2.2.7 [ 383s] + rm -rf /home/abuild/rpmbuild/BUILDROOT/bluefish-2.2.7-18.1.x86_64 [ 383s] + exit 0 [ 383s] ... checking for files with abuild user/group [ 383s] ... running 00-check-install-rpms [ 383s] ... installing all built rpms [ 383s] Preparing packages... [ 384s] bluefish-2.2.7-18.1.x86_64 [ 385s] bluefish-debugsource-2.2.7-18.1.x86_64 [ 385s] bluefish-debuginfo-2.2.7-18.1.x86_64 [ 386s] ... running 01-check-debuginfo [ 386s] ... testing for empty debuginfo packages [ 386s] ... running 02-check-gcc-output [ 386s] ... testing for serious compiler warnings [ 386s] (using /usr/lib/build/checks-data/check_gcc_output) [ 386s] (using //.build.log) [ 386s] [ 386s] I: Program is likely to break with new gcc. Try -fno-strict-aliasing. [ 386s] W: bluefish strict-aliasing-punning zeneditor-interface.c:472 [ 386s] E: bluefish 64bit-portability-issue document.c:2448 [ 386s] ### WATCHDOG MARKER START ### [ 389s] [ 358.983591] SysRq : Power Off [ 389s] [ 358.990176] reboot: Power down [ 391s] ### WATCHDOG MARKER END ### Build log bluefish-2.2.6 build -pass ################################### [ 150s] dependency check for bluefish-debugsource-2.2.6-2.3.1.x86_64.rpm: [ 150s] ... running 06-check-installtest [ 150s] ... testing for pre/postinstall scripts that are not idempotent [ 151s] ... running 08-check-permissions [ 151s] ... testing for modified permissions [ 152s] ... running 09-check-packaged-twice [ 152s] ... running 10-check-lanana [ 152s] ... running 12-check-libtool-deps [ 152s] ... testing devel dependencies required by libtool .la files [ 152s] (can be skipped by "skip-check-libtool-deps" anywhere in spec) [ 152s] ... running 13-check-invalid-provides [ 152s] ... running 14-check-gconf-scriptlets [ 152s] ... testing GConf scriptlet presence [ 152s] ... running 72-translate-appdata [ 152s] ... running 99-check-remove-rpms [ 152s] ... removing all built rpms [ 153s] (order: reverse bluefish bluefish-debuginfo bluefish-debugsource) [ 153s] [ 153s] RPMLINT report: [ 153s] =============== [ 156s] 2 packages and 0 specfiles checked; 0 errors, 0 warnings. [ 156s] [ 156s] ... creating baselibs [ 156s] ... saving statistics [ 156s] ... saving built packages [ 156s] RPMS/x86_64/bluefish-2.2.6-2.3.1.x86_64.rpm [ 156s] RPMS/x86_64/bluefish-debuginfo-2.2.6-2.3.1.x86_64.rpm [ 156s] RPMS/x86_64/bluefish-debugsource-2.2.6-2.3.1.x86_64.rpm [ 156s] SRPMS/bluefish-2.2.6-2.3.1.src.rpm [ 156s] OTHER/rpmlint.log [ 156s] OTHER/_statistics [ 156s] OTHER/bluefish-appdata.xml [ 156s] [ 156s] cloud105 finished "build bluefish.spec" at Mon Mar 23 09:51:47 UTC 2015. [ 156s] [ 156s] ### WATCHDOG MARKER START ### [ 159s] [ 139.002799] SysRq : Power Off [ 159s] [ 139.016293] reboot: Power down [ 163s] ### WATCHDOG MARKER END ### [ 163s] build: extracting built packages... [ 164s] RPMS/x86_64/bluefish-2.2.6-2.3.1.x86_64.rpm [ 164s] RPMS/x86_64/bluefish-debuginfo-2.2.6-2.3.1.x86_64.rpm [ 164s] RPMS/x86_64/bluefish-debugsource-2.2.6-2.3.1.x86_64.rpm [ 164s] SRPMS/bluefish-2.2.6-2.3.1.src.rpm [ 164s] OTHER/rpmlint.log [ 164s] OTHER/_statistics [ 164s] OTHER/bluefish-appdata.xml -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 6

[opensuse-packaging] Citi Merchant Services statements - 49708619-2803
by user 25 Mar '15

25 Mar '15

Attached is your Merchant Statement. It is secured so that only an authorized recipient can open it. To open, click on the attachment. In order to view the attached PDF file, you need Adobe Acrobat Reader Version 8.0 installed. Click on the following link: <http://www.adobe.com/products/acrobat/readstep2.html> to complete a free install or re-install if you have an older version. Visit Microsoft's self help website at www.microsoft.com or contact your ISP if you do not receive the attachment. Delivering your statements directly to your desktop is just one more way we've increased the speed of business. Thanks again for choosing CTS Holdings, LLC as your merchant processor. CTS Holdings, LLC, you can count on us! This is a post-only mailing. Please do not respond. To change preferences please contact Customer Service at 1-800-238-7675.

1 0

[opensuse-packaging] nothing provides...
by doiggl＠velocitynet.com.au 23 Mar '15

23 Mar '15

Hello, I copied a .spec to a package and got a "nothing provides..." see bitmap spec at [1] [1] https://build.opensuse.org/package/view_file/home:doiggl/bluefish/bluefish.… What BuildRequires: lines need changing to allow package to build ? Thanks --Glenn

2 1

[opensuse-packaging] Can bluefish- be updated to version 2.2.7 from 2.2.6
by doiggl＠velocitynet.com.au 23 Mar '15

23 Mar '15

Hello, Can bluefish- be updated to version 2.2.7 from 2.2.6 Thanks --Glenn https://build.opensuse.org/package/show/editors/bluefish Source: http://www.bennewitz.com/bluefish/stable/source/ bluefish-2.2.7.tar.bz2 bluefish-2.2.7.tar.gz -- 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] How can I get this package to build - komodo
by doiggl＠velocitynet.com.au 20 Mar '15

20 Mar '15

Hello, - How can I get this package to build [1] - Trying to use the documentation from [2] - Spec [3] -Trying to Run Installation Script ./install.sh Help appreciated. Thanks Glenn [1] https://build.opensuse.org/package/show/home:doiggl/komodo [2] http://tutorialforlinux.com/2014/01/28/how-to-install-komodo-edit-on-opensu… [3] Spec https://build.opensuse.org/package/view_file/home:doiggl/komodo/komodo.spec… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 9

[opensuse-packaging] Can LibreOffice be updated to 4.4.1 from earlier versions.
by doiggl＠velocitynet.com.au 20 Mar '15

20 Mar '15

Hello, Can LibreOffice be updated to 4.4.1 from earlier versions. Thank you. --Glenn https://build.opensuse.org/package/show/LibreOffice:Factory/libreoffice https://www.libreoffice.org/download/release-notes/ https://www.libreoffice.org/download/libreoffice-fresh/ http://donate.libreoffice.org/home/dl/rpm-x86_64/4.4.1/en-US/LibreOffice_4.… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Pictures
by Tod 20 Mar '15

20 Mar '15

Hi, Sorry for the delay I just received these this morning. Here are the pictures of the panels that you requested. Thank you, Adam Office Manager American Wholesale Co. Phone: 216-426-8882 Fax: 216-426-8883 Email: ea(a)awrco.com Email 2: eaawrco(a)aol.com Web: www.awrco.com

1 0

[opensuse-packaging] info handling in specfile
by Martin Pluskal 18 Mar '15

18 Mar '15

Hi as some of you have probably noticed there are some mildly annoying messages when packages which installed info files are being uninstalled - i.e: ... Additional rpm output: install-info: No such file or directory for /usr/share/info/autoconf.info.gz warning: %postun(autoconf-2.69-11.2.noarch) scriptlet failed, exit status 1 It is my understanding that this is caused by install-info --delete being called in postun stage, when info file is already gone. This issue has already been reported and discussed [1] but not resolved. I have also noticed that in some packages, issue has been solved/hidden by moving install-info to preun, but [1] indicates that such solution has side effect of info entries being removed on update of package. On the other hand, fedora seems to be currently using same solution - i.e [2] . I have meanwhile updated our wiki [3] - but I have some doubts whether this solution is actually correct. I would welcome any suggestions or comments (preferably constructive :) ). Kind regards Martin Pluskal [1] https://bugzilla.opensuse.org/show_bug.cgi?id=776008 [2] http://pkgs.fedoraproject.org/cgit/make.git/tree/make.spec [3] https://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets#Texinfo

3 2

[opensuse-packaging] Checking systemd version
by Togan Muftuoglu 16 Mar '15

16 Mar '15

Hi Depending on the systemd version available a different service file needs to be installed. What is the easy way to check if systemd version is > 214 Thanks -- Life is endless possibilities -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] Can seamonkey be updated to SeaMonkey 2.33 please. from 2.32.1
by doiggl＠velocitynet.com.au 12 Mar '15

12 Mar '15

Hello, Can seamonkey be updated to SeaMonkey 2.33 please. from 2.32.1 https://download.mozilla.org/?product=seamonkey-2.33&os=linux&lang=en-US https://build.opensuse.org/package/show/mozilla/seamonkey Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] How can the broken line be found in patch ?
by doiggl＠velocitynet.com.au 11 Mar '15

11 Mar '15

hello, How can the broken line be found in patch? Attaching reiser4-precise-discard.patch Thank you Glenn - https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla - https://build.opensuse.org/package/live_build_log/home:doiggl/kernel-vanill… home:doiggl/kernel-vanilla/patches.rpmify.tar.bz2 The patch is made from these locations: # http://www.spinics.net/lists/reiserfs-devel/msg04616.html # http://www.spinics.net/lists/reiserfs-devel/msg04617.html # http://www.spinics.net/lists/reiserfs-devel/msg04618.html >From log: [ 123s] + /home/abuild/rpmbuild/SOURCES/guards --default=0 base [ 124s] + cd linux-3.18 [ 124s] + /home/abuild/rpmbuild/SOURCES/apply-patches --vanilla /home/abuild/rpmbuild/SOURCES/series.conf .. [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-3.18.1 [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-3.18.1-2 [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-3.18.2-3 [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-3.18.3-4 [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-3.18.4-5 [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-3.18.5-6 [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-3.18.6-7 [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/reiser4-for-3.18.6.patch [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/reiser4.various.patch [ 124s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/reiser4-precise-discard.patch [ 124s] 4 out of 4 hunks FAILED -- saving rejects to file fs/reiser4/discard.c.rej [ 124s] 4 out of 4 hunks FAILED -- saving rejects to file fs/reiser4/discard.c.rej [ 124s] patch unexpectedly ends in middle of line [ 124s] 1 out of 1 hunk FAILED -- saving rejects to file fs/reiser4/discard.c.rej [ 124s] patch unexpectedly ends in middle of line [ 124s] ++ echo '*** patch ../patches.rpmify/reiser4-precise-discard.patch failed ***' [ 124s] *** patch ../patches.rpmify/reiser4-precise-discard.patch failed *** [ 124s] error: Bad exit status from /var/tmp/rpm-tmp.h2qxix (%prep) [ 124s] [ 124s] [ 124s] RPM build errors:

3 3

[opensuse-packaging] Can gramps package be updated to version 4.1.2 from 4.1.1
by doiggl＠velocitynet.com.au 08 Mar '15

08 Mar '15

Hello, Can gramps package be updated to version 4.1.2 from 4.1.1 Thank you Glenn https://build.opensuse.org/package/show/openSUSE:Factory/gramps http://sourceforge.net/projects/gramps/files/Stable/4.1.2/gramps-4.1.2.tar.… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0