March 2015 - openSUSE Packaging - openSUSE Mailing Lists

[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