April 2015 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] changelog exists in my OSC pacakge build, but RPMLINT not finding it
by aleph2＠vfemail.net 25 Apr '15

25 Apr '15

I'm creating a package using OBS, and keep getting an rpmlint error about changelog that I can't figure out. My spec file has the required '%changelog' section cat test.spec ... %build make %install make INSTALL_PREFIX=$RPM_BUILD_ROOT install %clean rm -rf %{buildroot} %post %postun %files %changelog test.changes And the changelog file exists in the package dir locally ls test.changes test.changes But when I run the build osc build --clean --local-package test.spec This is in the RMPLINT report [ 42s] RPMLINT report: [ 42s] =============== [ 42s] test.noarch: W: suse-filelist-empty packages without any files are discouraged in SUSE [ 42s] test.noarch: W: no-changelogname-tag [ 42s] test.src: W: no-changelogname-tag [ 42s] There is no changelog. Please insert a '%changelog' section heading in your [ 42s] spec file and prepare your changes file using e.g. the 'osc vc' command. [ 42s] [ 42s] 2 packages and 0 specfiles checked; 0 errors, 3 warnings. [ 42s] What do I gotta do here to get this changelog settled? ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 9

[opensuse-packaging] Packaging web-apps for Apache 2.2/2.4 containing require/deny sections
by Johannes Weberhofer 25 Apr '15

25 Apr '15

Dear all! Recently many Webapp packages contain complicated constructions to allow/deny access to directories; those constructions can IMHO be simplified. 1) Allow access. To ensured that access on Apache 2.4 is allowed it must be ensured that the compatibility module (if installed) allows access _and_ the new module, too. Both could inherit DENY from other paths: <IfVersion >= 2.4> <IfModule mod_access_compat.c> Order allow,deny Allow from all </IfModule> Require all granted </IfVersion> <IfVersion < 2.4> Order allow,deny Allow from all </IfVersion> 2) Disallow access. For Apache 2.4 it's enough to disallow access with one strategy. So the structure can be more simple: <IfVersion >= 2.4> Require all denied </IfVersion> <IfVersion < 2.4> Order allow,deny Deny from all </IfVersion> Is this logic correct? Does anyone see a problem with that? Shall that be documented in the wiki? -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- 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] missing Requires in gstream subpackages
by Olaf Hering 23 Apr '15

23 Apr '15

This morning I was toying around with a SLED12 installation. It has all SLE channels and packman enabled. At some point I tried to play a wmv file. Video did not find the missing codec. Then I tried to replace the various installed gstreamer packages manually with the version from packman. While changing gstreamer.rpm for example automatically pulled the newer version of gstream-lang.rpm, most gstreamer related packages did not get automatically updated to their matching main package because they lack the appropriate Requires: %{name}-%{version} tag. In the end I had a mix of 1.2 and 1.4.5 %packages, until I manually changed each package. Why is that so, just an oversight? Olaf -- 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] RPM verification for /etc configuration files
by Bjoern Voigt 22 Apr '15

22 Apr '15

During an openSUSE server migration I had the idea to audit all changed files on the old server. (I also managed new files, but with another strategy.) My idea was to list all changed RPM files. # rpm -Va | tee changed-rpm-files.txt The problem is, that I missed some actual changed files from /etc in changed-rpm-files.txt output like /etc/hosts and /etc/aliases. After some investigation I found that these files are listed with special verification options in RPM SPEC files: /usr/src/packages/SPECS/netcfg.spec (from netcfg-11.5-24.5.1.noarch, openSUSE 13.2): %verify(not md5 size mtime) %config(noreplace) %{_sysconfdir}/aliases [...] %verify(not md5 size mtime) %config(noreplace) %{_sysconfdir}/hosts I guess, that some config files get this options, because they are changed too often during normal system configuration tasks and especially during automated tasks. My questions: - Is there a way to query these files (files with options "%verify(not md5 size mtime)") in a running system? - Is there a way to query changed of these files regardless of this option? - Do you think, that managing some config files with the "%verify(not md5 size mtime)" options is generally a good idea or should this change in coming openSUSE versions (bug report)? Greetings, Björn -- 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] 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] To all perl packagers: my hackweek project
by Stephan Kulow 17 Apr '15

17 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, For years I'm trying to fight outdated perl modules in devel:languages:perl and openSUSE:Factory with various scripts and a lot of man power. But it was a lost battle from the start - there are just too many modules and too many changes to review. And the worst of all: manual fixes required after cpanspec had to be manually readded - and the changes to be extracted for .changes file. It was a lot of work and updating more than 10 modules a day make you feel like a robot. For rubygems we use since some months a mechanism that proved itself, so I reimplemented something very similar for cpan modules. - - I have a script that tries to update every outdated module in devel:languages:perl and if the update builds, it will create a submit request (I plan to run this every night once the dust settled) - - cpanspec got a feature to extract the diff between the changelogs and "pastes" it into the .changes file. If this is not possible, it will add a pointer to the installed change file. - - cpanspec's behaviour can now be controlled by a cpanspec.yml file next to the sources. We previously changed the cpanspec generated .spec manually and had to transfer these changes for every update. This lead to the rather sad state that 1188 of 2662 packages in dlp were outdated (checked monday). Now it's friday and we're down to 250 outdated packages - which is still a lot, but at least the tools should make sure we're not regressing on this number. But as we fix packages to have their changes transfered to the yaml file, this number will go down. So how does such a yaml file look like? - --- #description_paragraphs: 3 #no_testing: broken upstream #sources: # - source1 # - source2 #patches: # foo.patch: -p1 # bar.patch: #preamble: |- # BuildRequires: gcc-c++ post_prep: |- sed -i -e 's,/usr/bin/bash,/bin/bash,' bin/test-yaml #post_install: |- # sed on %{name}.files #license: SUSE-NonFree #skip_noarch: 1 #custom_build: - #./Build build flags=%{?_smp_mflags} --myflag Most packages only require a custom license - but you can limit the description, overwrite the noarch guessing, add patches or more sources or skip testing. And if you need more, feel free to do a pull request for https://github.com/openSUSE/cpanspec Thanks for reading, Stephan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlUxDJ8ACgkQwFSBhlBjoJY4jgCfYeubqCY4QgFQqh3ISBUiiG7U 8ecAn3Ah80dvaVD9gqeDW8eAc2Y/m/Tf =7BG0 -----END PGP SIGNATURE----- -- 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] Shared Library Packaging; SONAME is missed
by Matwey V. Kornilov 17 Apr '15

17 Apr '15

Hi, I need a piece of advice on packaging shared library. I follow https://en.opensuse.org/openSUSE:Shared_library_packaging_policy and I want to package the following library: https://github.com/beagleboard/am335x_pru_package that has neither SONAME nor version (so, package version will be 0.0.0+gitXXXXX). And according to the section "When there is no versioning" of the guideline I would have to have libprussdrv-0.0.0_gitXXXXX.so that is quite ugly and will break majority of scripts and makefiles which have -lprussdrv -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] Update to Clang 3.6 pulls in hundreds of package changes
by Christoph Grüninger 15 Apr '15

15 Apr '15

Hi packagers, I wanted to update Clang 3.5 to 3.6 using the devel:/tools:/compiler repository. When doing so with Yast2, it complained that several packages require libclang-3.5 and they offered to change more then 1600 packages from 64 bit to 32 bit. That's ridiculous. Is there a way to keep the old libclang and install the new one, too? Why is it not possible to have several Clang version installed? With GCC it works quite fine and to my knowledge GCC is by far more integrated in the whole software stack. Bye Christoph -- 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] RPMLINT report items: apache-SizeLimit
by doiggl＠velocitynet.com.au 10 Apr '15

10 Apr '15

Hello, What specfile changes resolves these items ? Thanks --Glenn [ 36s] RPMLINT report: [ 36s] =============== [ 37s] (none): E: badness 50000 exceeds threshold 1000, aborting. [ 37s] Apache-SizeLimit.noarch: E: suse-filelist-forbidden-noarch (Badness: 10000) /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/auto/Apache2 is not allowed in a noarch package [ 37s] Apache-SizeLimit.noarch: E: suse-filelist-forbidden-noarch (Badness: 10000) /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/auto/Apache2/SizeLimit/.packlist is not allowed in a noarch package [ 37s] Apache-SizeLimit.noarch: E: suse-filelist-forbidden-noarch (Badness: 10000) /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/auto is not allowed in a noarch package [ 37s] Apache-SizeLimit.noarch: E: suse-filelist-forbidden-noarch (Badness: 10000) /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/auto/Apache2/SizeLimit is not allowed in a noarch package [ 37s] Apache-SizeLimit.noarch: W: perl5-naming-policy-not-applied /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/auto/Apache2 [ 37s] This package doesn't respect the naming policy for perl5 packages. Its name [ 37s] should match the regular expression ^perl(-|$). [ 37s] [ 37s] Apache-SizeLimit.noarch: W: no-dependency-on perl-base 5.20.1 [ 37s] Apache-SizeLimit.noarch: W: invalid-license Apache v2.0 [ 37s] Apache-SizeLimit.src: W: invalid-license Apache v2.0 [ 37s] The specified license string is not recognized. Please refer to [ 37s] http://license.opensuse.org/ for the list of known licences and their exact [ 37s] spelling. [ 37s] [ 37s] Apache-SizeLimit.noarch: E: file-contains-buildroot (Badness: 10000) /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/auto/Apache2/SizeLimit/.packlist [ 37s] Your file contains traces of $RPM_BUILD_ROOT. [ 37s] [ 37s] 2 packages and 0 specfiles checked; 5 errors, 4 warnings. [ 37s] [ 37s] ### WATCHDOG MARKER START ### [ 40s] [ 30.508232] SysRq : Power Off [ 40s] [ 30.528491] reboot: Power down [ 42s] ### WATCHDOG MARKER END ### -Added to spec file: BuildRequires: apache2-mod_perl BuildRequires: apache2-devel links: ----- https://build.opensuse.org/package/show/home:doiggl/apache-SizeLimit https://build.opensuse.org/package/live_build_log/home:doiggl/apache-SizeLi… https://build.opensuse.org/package/view_file/home:doiggl/apache-SizeLimit/A… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[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