vboot.x86_64: W: files-duplicate /usr/share/vboot/devkeys/recovery_kernel_data_key.vbprivk /usr/share/vboot/devkeys/installer_kernel_data_key.vbprivk
vboot.x86_64: W: files-duplicate /usr/share/vboot/devkeys/recovery_kernel_data_key.vbpubk /usr/share/vboot/devkeys/installer_kernel_data_key.vbpubk
vboot.x86_64: W: hidden-file-or-dir /usr/share/vboot/devkeys/uefi/db/db.children/.srl
The file or directory is hidden. You should see if this is normal, and delete
it from the package if not.

vboot.src:28: W: macro-in-comment %{major_version}
vboot.src:28: W: macro-in-comment %{minor_version}
There is a unescaped macro after a shell style comment in the specfile. Macros
are expanded everywhere, so check if it can cause a problem in this case and
escape the macro with another leading % if appropriate.

vboot.src: W: name-repeated-in-summary C vboot
vboot.x86_64: W: name-repeated-in-summary C vboot
The name of the package is repeated in its summary.  This is often redundant
information and looks silly in various programs' output.  Make the summary
brief and to the point without including redundant information in it.

vboot.src: W: no-version-in-last-changelog
vboot.x86_64: W: no-version-in-last-changelog
The latest changelog entry doesn't contain a version. Please insert the
version that is coherent with the version of the package and rebuild it.

vboot.x86_64: W: non-executable-in-bin /usr/bin/common_minimal.sh 644
A file is being installed in /usr/bin, but is not an executable. Be sure that
the file is an executable or that it has executable permissions.

vboot.x86_64: W: non-executable-script /usr/bin/common_minimal.sh 644 /bin/sh 
This text file contains a shebang or is located in a path dedicated for
executables, but lacks the executable bits and cannot thus be executed.  If
the file is meant to be an executable script, add the executable bits,
otherwise remove the shebang or move the file elsewhere.

vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/android/media.x509.pem
vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/android/platform.x509.pem
vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/android/releasekey.x509.pem
vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/android/shared.x509.pem
vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/uefi/db/db.children/db_child.pem
vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/uefi/db/db.pem
vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/uefi/kek/kek.pem
vboot.x86_64: W: pem-certificate /usr/share/vboot/devkeys/uefi/pk/pk.pem
Shipping a PEM certificate is likely wrong. If used for the default
configuration, this is insecure ( since the certificate is public ). If this
is used for validation, ie a CA certificate store, then this must be kept up
to date due to CA compromise. The only valid reason is for testing purpose, so
ignore this warning if this is the case.

2 packages and 0 specfiles checked; 0 errors, 19 warnings.