To fix, make sure that debugging symbols are created and that they not are stripped so they are available for rpmbuild post-processing. Indicates that the text encoding of the specified file, usually a documentation file, is not in UTF8. A library path is hardcoded to one of the following paths: In all cases, upstream should be informed about this.
This is the only requirement with respect to this error. Other files can be patched if deemed suitable. The updated GPL 2. The package maintainer should notify upstream or patch it. The value of the License tag was not recognized. The handling of this error depends on ld. Public libraries are libs expected to be used by other packages, Other libraries e. Instead, use a rpath to let the application locate the library.
You need to add a line like the following one in the header of the init script:. When installed, the package will be started on runlevel 2, 3, 4 and 5, and stopped for 1 and 6.
See InitscriptHowto for more information. There are several instances where this is acceptable:. See man page LD 1. The group specified in your spec file is not valid.
Many times this can be solved by following the procedure listed on Packaging: There used to be limitations on filtering as described in this post.
However, these limitations are not valid any more thread FPC bug. Older methods of filtering out private shared objects are deprecated and should be replaced with the macros from the Guidelines as time permits. This executable text file does not contain a shebang, thus it cannot be properly executed. Often this is a sign of spurious executable bits for a non-script file, but can also be a case of a missing shebang.
To fix this error, find out which case of the above it is, and either remove the executable bits or add the shebang. Or you can add shebang. Indicates that a shared library contains non Position Independent Code. This is often caused by the libraries being compiled without the -fPIC option or being statically linked with non-PIC code. This package owns a directory that is part of the standard hierarchy, which can lead to default directory permissions or ownerships being changed to something non-standard.
A file that you listed to include in your package has strange permissions. The package contains some files duplicate, which wastes installation space and package size. Documentation should not be executable. Files that are likely not supposed to be executable are marked as such. This can be subject of false positives, so carefully review if those are correct or if not, suppress them. The package contains content that should be in a -devel subpackage. The advantage of cleaning your package up and splitting it properly into a -devel package is twofold:.
In most cases however, the error is triggered because of versioned libtool modules. To apply versioning, the subdirectory the plugins are installed to should be versioned instead.
Under certain circumstances, this can cause incompatibilities with viewer applications. The check is scored very low, so you might just not care about it. If you care, you should try recoding the files in question to Unix-style LF only. This script has wrong end-of-line encoding, usually caused by creation or modification on a non-Unix system.
It will prevent its execution. Create files on Linux only. Do not create files on non-Unix environment and add it in package. Your package contains two files that are apparently hardlinked and that are likely on different partitions. Installation of such an RPM will fail due to RPM being unable to unpack the hardlink, if the files that are hardlinked are ending up on two different physical partitions. By policy, do not hardlink across the first two levels of a path, e. The spec file does not contain a "Packager" tag.
A specfile should never include this, because it will confuse the hell out of people when someone rebuilds a package and then cannot contact the right person when there is a bug with the package. Your package does not follow the SUSE library packaging policy. The files are not in the RPM archive itself but created dynamically by the package, at install time or most often later when a daemon is run, i. They get erased with the package when you rpm -e.
The init script refers to runlevel 4 which is admin defined. No distribution script must use it. Remove '4' from 'Default-Start'. The dbus package used a too permissive configuration in the past, which led to security problems CVE During investigation of this problem, it was found that many packages contain dbus configuration files that contain useless settings, settings that harm other services or settings that even break after the dbus security update. Fix the dbus configuration file. In most cases, the config can be reduced to a few lines.
If that is missing the service will not work as dbus uses deny as default policy. Executable stack is usually an error as it is only needed if the code contains GCC trampolines or similar constructs which uses code on the stack. One common source for needlessly executable stack cases are object files built from assembler files which do not define a proper. In other case, it is — under some circumstances — possible that rpm will remove the generic name from filesystem, which breaks the link.
This policy is applicable for packages for openSUSE Previous versions contains a version of RPM which disallows a same ghost file owned by several packages, so this would results in a conflict on installation. The package should be of the noarch architecture because it does not contain any binaries.
This package owns a directory that is part of the standard hierarchy, which can lead to default directory permissions or ownerships being changed to something non-standard. This executable text file does not contain a shebang, thus it cannot be propely executed.
Often, this is a sign of spurious executable bits for a non-script file, but can also be a case of a missing shebang. To fix this error, find out which case of the above it is, and either remove the executable bits or add the shebang. You have included file s internally used by a version control system in the package. Move these files out of the package and rebuild it.
Most likely not installed by intention. This could be accomplished with the following command in the install section after all files have been installed:. The group specified in your spec file is not valid. Choose a well known one. A file that you listed to include in your package has strange permissions.
Usually a file should have rw-r--r-- and a directory rwxr-xr-x permissions. A library path is hardcoded to one of the following paths: The path in question is architecture specific while the package is marked architecture independent.
Either move the file to a architecture neutral location or remove the noarch tag from the package. The init script name should be the same as the package name in lower case, or one with 'd' appended if it invokes a process by that name. This error should actually never show up in the build service. The build script automatically strips binaries according to global project settings.
Left over unstripped binaries could therefore indicate a bug in the automatic tripping process so please file a bug report. Please do not strip binaries manually as that will break debuginfo creation. Applications should use getaddrinfo 3 and getnameinfo 3 instead.
Please work with upstream to port the applictation to the modern interface. Ulrich Drepper explains the issues in more detail. A gettext translation file those ending in.
This information might be useful in the future to be able to leave out certain languages during installation. We frequently get translation bugs that occur because. Doing so will allow the openSUSE translators and the SUSE translation team to add translations for your desktop files automatically during your package build. See the Packaging Conventions.
Fixing this is necessary so that de installation of the package happens in the correct order, e. Moreover, the directory is intended for legacy device lock files e. Don't use it for other purposes. Other distributions use it to mark that an init script has run.
There is no equivalent on openSUSE. In cases where init scripts actually need to store init script specific state information use e. As per distribution policy some binaries, such as important network facing programs as well as setuid binaries, need to be compiled as position independent executable PIE. PIE randomizes the start address of programs to make it harder for attackers to create reliable exploits.
The package allows unprivileged users to carry out privileged operations without authentication. This could cause security problems if not done carefully.