6648a434d5
pam_snapper.so is installed in libdir as the default in configure.ac is:
PAM_SECURITY=${libdir}/security
https://github.com/openSUSE/snapper/blob/master/configure.ac#L66
and depending on multilib configuration this fails with:
ERROR: QA Issue: lib32-snapper: Files/directories were installed but not shipped in any package:
/usr/lib32/security/pam_snapper.so
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
lib32-snapper: 1 installed and not shipped files. [installed-vs-shipped]
or
ERROR: QA Issue: snapper: Files/directories were installed but not shipped in any package:
/usr/lib64/security/pam_snapper.so
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
snapper: 1 installed and not shipped files. [installed-vs-shipped]
when default libdir doesn't match with nonarch_libdir
Some recipes are using ${base_libdir}/security and some just
${libdir}/security with the usrmerge being the default and required
with systemd I'm not sure which one is better.
Now all files are packaged some in libdir some in nonarch_libdir:
snapper/0.11.2 $ find packages-split/snapper/usr/lib*
packages-split/snapper/usr/lib
packages-split/snapper/usr/lib/systemd
packages-split/snapper/usr/lib/systemd/system
packages-split/snapper/usr/lib/systemd/system/snapper-timeline.timer
packages-split/snapper/usr/lib/systemd/system/snapper-timeline.service
packages-split/snapper/usr/lib/systemd/system/snapper-boot.timer
packages-split/snapper/usr/lib/systemd/system/snapper-cleanup.timer
packages-split/snapper/usr/lib/systemd/system/snapperd.service
packages-split/snapper/usr/lib/systemd/system/snapper-boot.service
packages-split/snapper/usr/lib/systemd/system/snapper-cleanup.service
packages-split/snapper/usr/lib/snapper
packages-split/snapper/usr/lib/snapper/systemd-helper
packages-split/snapper/usr/lib/snapper/plugins
packages-split/snapper/usr/lib/snapper/installation-helper
packages-split/snapper/usr/lib/pam_snapper
packages-split/snapper/usr/lib/pam_snapper/pam_snapper_pamconfig.sh
packages-split/snapper/usr/lib/pam_snapper/pam_snapper_userdel.sh
packages-split/snapper/usr/lib/pam_snapper/pam_snapper_homeconvert.sh
packages-split/snapper/usr/lib/pam_snapper/pam_snapper_useradd.sh
packages-split/snapper/usr/lib64
packages-split/snapper/usr/lib64/libsnapper.so.7.4.3
packages-split/snapper/usr/lib64/security
packages-split/snapper/usr/lib64/security/pam_snapper.so
packages-split/snapper/usr/lib64/snapper
packages-split/snapper/usr/lib64/snapper/testsuite
packages-split/snapper/usr/lib64/snapper/testsuite/directory1
packages-split/snapper/usr/lib64/snapper/testsuite/permissions2
packages-split/snapper/usr/lib64/snapper/testsuite/error2
packages-split/snapper/usr/lib64/snapper/testsuite/simple1
packages-split/snapper/usr/lib64/snapper/testsuite/ug-tests
packages-split/snapper/usr/lib64/snapper/testsuite/xattrs1
packages-split/snapper/usr/lib64/snapper/testsuite/owner3
packages-split/snapper/usr/lib64/snapper/testsuite/run-all
packages-split/snapper/usr/lib64/snapper/testsuite/missing-directory1
packages-split/snapper/usr/lib64/snapper/testsuite/permissions1
packages-split/snapper/usr/lib64/snapper/testsuite/test-btrfsutils
packages-split/snapper/usr/lib64/snapper/testsuite/owner2
packages-split/snapper/usr/lib64/snapper/testsuite/xattrs3
packages-split/snapper/usr/lib64/snapper/testsuite/permissions3
packages-split/snapper/usr/lib64/snapper/testsuite/CAUTION
packages-split/snapper/usr/lib64/snapper/testsuite/xattrs4
packages-split/snapper/usr/lib64/snapper/testsuite/ascii-file
packages-split/snapper/usr/lib64/snapper/testsuite/setup-and-run-all
packages-split/snapper/usr/lib64/snapper/testsuite/owner1
packages-split/snapper/usr/lib64/snapper/testsuite/xattrs2
packages-split/snapper/usr/lib64/snapper/testsuite/error4
packages-split/snapper/usr/lib64/snapper/testsuite/error1
packages-split/snapper/usr/lib64/libsnapper.so.7
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| dynamic-layers | ||
| files | ||
| lib/oeqa/selftest/cases | ||
| licenses | ||
| recipes-benchmark | ||
| recipes-bsp | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-crypto | ||
| recipes-dbs | ||
| recipes-devtools | ||
| recipes-extended | ||
| recipes-gnome | ||
| recipes-graphics | ||
| recipes-kernel | ||
| recipes-multimedia | ||
| recipes-navigation | ||
| recipes-networking/cyrus-sasl | ||
| recipes-printing | ||
| recipes-security | ||
| recipes-shells | ||
| recipes-support | ||
| recipes-test | ||
| COPYING.MIT | ||
| README.md | ||
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
layer maintainer: Khem Raj raj.khem@gmail.com