RPM-Build-Fehler: Datei muss beginnen mit "/"

Hier ist meine Skillung Datei: http://pastebin.com/MtzxC1kv

Wenn ich versuche zu laufen rpmbuild -ba myfile.spec möchte, bekomme ich folgenden Fehler:

+ /usr/lib/rpm/brp-python-bytecompile
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: PA_Connector-1.0-1.0
error: File must begin with "/": %{_initddir}/pa_connector
error: File must begin with "/": attr(755,impulse,impulse)
error: File must begin with "/": attr(644,impulse,impulse)
error: File must begin with "/": attr(644,impulse,impulse)
error: File must begin with "/": attr(644,impulse,impulse)
error: File must begin with "/": attr(644,impulse,impulse)
error: File must begin with "/": attr(644,impulse,impulse)
error: File must begin with "/": attr(644,impulse,impulse)
Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/PA_Connector-1.0-1.0-root
error: Installed (but unpackaged) file(s) found:
   /%{_initddir}/pa_connector
   /opt/pa_connector/config.xml
   /opt/pa_connector/lib/commons-logging-1.1.1.jar
   /opt/pa_connector/lib/log4j-1.2.17.jar
   /opt/pa_connector/lib/pa_connector.jar
   /opt/pa_connector/log4j.properties
   /opt/pa_connector/pa_connector.sh


RPM build errors:
    File must begin with "/": %{_initddir}/pa_connector
    File must begin with "/": attr(755,impulse,impulse)
    File must begin with "/": attr(644,impulse,impulse)
    File must begin with "/": attr(644,impulse,impulse)
    File must begin with "/": attr(644,impulse,impulse)
    File must begin with "/": attr(644,impulse,impulse)
    File must begin with "/": attr(644,impulse,impulse)
    File must begin with "/": attr(644,impulse,impulse)
    Installed (but unpackaged) file(s) found:
   /%{_initddir}/pa_connector
   /opt/pa_connector/config.xml
   /opt/pa_connector/lib/commons-logging-1.1.1.jar
   /opt/pa_connector/lib/log4j-1.2.17.jar
   /opt/pa_connector/lib/pa_connector.jar
   /opt/pa_connector/log4j.properties
   /opt/pa_connector/pa_connector.sh

Ich habe gelesen, ein paar Beiträge auf SO zu korrigieren, was BuildRoot sein sollte, und es behoben, aber es funktioniert immer noch nicht.

  • Leider sind die OP ' s erste spec-Datei ist nicht mehr verfügbar, so dass einige der Kontext erforderlich, um zu verstehen genehmigt die Antwort ist jetzt fehlt.
Schreibe einen Kommentar