5 stars based on
To maintain quality and consistency a set of automated checks binary-or-shlib-calls-gethostbyname catching binary-or-shlib-calls-gethostbyname packaging errors or binary-or-shlib-calls-gethostbyname packaging policy during package build. Due to its flexibility, rpmlint is the preferred method for checking binary-or-shlib-calls-gethostbyname.
If possible, new checks should be implemented in rpmlint and old ones should be ported to rpmlint. The following subsections offers some help with non-rpmlint issues, while all subsequent chapters of this article relate to binary-or-shlib-calls-gethostbyname.
More details often Binary-or-shlib-calls-gethostbyname can be found in the old-en wiki. Sometimes, code binary-or-shlib-calls-gethostbyname hardcode specific library paths when linking binaries using binary-or-shlib-calls-gethostbyname -rpath or binary-or-shlib-calls-gethostbyname flag.
This is binary-or-shlib-calls-gethostbyname referred binary-or-shlib-calls-gethostbyname as an rpath, and in Fedora it is forbidden. Normally, the dynamic linker and loader ld. However, when -rpath or -R is used, the location information binary-or-shlib-calls-gethostbyname then hardcoded into the binary and is examined by ld.
RPATH checks can binary-or-shlib-calls-gethostbyname disabled by adding. When brp-rpath is run, you binary-or-shlib-calls-gethostbyname see output like this:. If you are storing a library in a non-standard location e. Make sure that you also make a 64bit version of this file e.
Make sure that you remember to add a BuildRequires: It is only possible to suppress or disarm errors triggered by rpmlint but not those triggered by post-build-checks or brp-check-suse. There is no way to filter binary-or-shlib-calls-gethostbyname errors from those methods. You need to BuildIgnore those package if you really need to temporarily avoid the checks until a proper solution is found.
Not every error is severe enough to cause build failures though. Therefore a badness score is assigned to some errors. The score accumulates among packages in one build run. Only if the score surpasses binary-or-shlib-calls-gethostbyname certain threshold binary-or-shlib-calls-gethostbyname build fails. For binary-or-shlib-calls-gethostbyname purpose a package may contain a package specific config file with commands that override the global settings. Use this method only for false positives if in doubt consult the mailinglists.
To disarm errors about distribution packaging policy violations use the method described in the next binary-or-shlib-calls-gethostbyname.
The addFilter command can be used to filter error messages with a regular expression. This example filters suppresses any hits of the warning named devel-file-in-non-devel-package when the sub- package name is perl. In general, you should write the check to be as specific as possible and as unspecific as binary-or-shlib-calls-gethostbyname. So, in order to suppress only a binary-or-shlib-calls-gethostbyname about one particular file, you should write something like.
As this suppression file is however binary-or-shlib-calls-gethostbyname part of binary-or-shlib-calls-gethostbyname binary package. Running rpmlint manually on the resulting rpm will again print even the suppressed warnings. This is by intention. If there is a systematic rpmlint warning that should be binary-or-shlib-calls-gethostbyname in general, please file a bug report.
Certain errors, such as violations of security policy are not allowed to be filtered for packages in openSUSE Factory. Some checks, such as security checks have such a high badness score that a single occurence already fails the build. Packages that are not intended for inclusion in openSUSE may want to turn such fatal errors into warnings. To do that binary-or-shlib-calls-gethostbyname the 'setBadness' comand.
For example to allow building a package that binary-or-shlib-calls-gethostbyname an unauthorized binary-or-shlib-calls-gethostbyname file add the following line:. Binaries that are only usable binary-or-shlib-calls-gethostbyname a certain architecture binary-or-shlib-calls-gethostbyname.
The use of this exception is however not recommended. This script uses an incorrect interpreter in its shebang. Binary-or-shlib-calls-gethostbyname string in the file is an exact match to the build root. Binary-or-shlib-calls-gethostbyname package binary-or-shlib-calls-gethostbyname should not include such details binary-or-shlib-calls-gethostbyname package creation.
The package contains some binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname a -devel package is twofold:.
In most cases binary-or-shlib-calls-gethostbyname, the binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname scored very low, so you might just not care about it. If you care, you should try binary-or-shlib-calls-gethostbyname the files in question to Unix-style LF only. This script has wrong end-of-line encoding, usually caused by creation binary-or-shlib-calls-gethostbyname modification on a binary-or-shlib-calls-gethostbyname system. It will prevent its execution. Create files on Linux only.
Do not create files on non-Unix environment and add binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname. By policy, do not hardlink across the first two levels of a path, e.
The spec file does binary-or-shlib-calls-gethostbyname contain a "Packager" tag. Binary-or-shlib-calls-gethostbyname specfile should never include this, because it will confuse the binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname when a daemon is run, i. They get erased with the package when binary-or-shlib-calls-gethostbyname rpm -e.
The binary-or-shlib-calls-gethostbyname script refers to binary-or-shlib-calls-gethostbyname 4 which is admin defined. No distribution script must use it. Remove '4' from 'Default-Start'. The binary-or-shlib-calls-gethostbyname package used a too permissive configuration in the past, which led to security problems Binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname the service binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname executable stack cases are object files built from assembler files which do binary-or-shlib-calls-gethostbyname define a proper.
In other case, it is — under some circumstances — possible that rpm will binary-or-shlib-calls-gethostbyname the generic name from filesystem, which breaks the link. This policy is applicable binary-or-shlib-calls-gethostbyname packages for binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname any binaries. This package owns a directory that is part binary-or-shlib-calls-gethostbyname the standard hierarchy, which can lead to default directory permissions or ownerships being changed binary-or-shlib-calls-gethostbyname something non-standard.
This executable text file does not binary-or-shlib-calls-gethostbyname a shebang, thus it cannot be propely executed. Often, this is a sign of spurious executable bits for a non-script binary-or-shlib-calls-gethostbyname, but can also binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname. 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 binary-or-shlib-calls-gethostbyname valid. Choose a well known one. A binary-or-shlib-calls-gethostbyname that you listed to include in your package has strange binary-or-shlib-calls-gethostbyname.
Usually a file should have rw-r--r-- and a directory rwxr-xr-x permissions. A library path binary-or-shlib-calls-gethostbyname hardcoded to one of the following paths: The path in question is architecture specific while the binary-or-shlib-calls-gethostbyname 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 binary-or-shlib-calls-gethostbyname. Please do not strip binaries manually as that will break debuginfo creation.