Strange effects when building Arch packages
While the build of a package in home:munix9:gambas works without any problems, in home:munix9:gambas:test the almost same package is suddenly displayed as “unresolvable”. This means that system packages are missing that are actually there. Even stranger is that the build in home:munix9:gambas:test has already worked, and after a few tests “unresolvable” is suddenly displayed. Does anyone have a helpful explanation for this? Thanks & regards
Am 17.11.24 um 08:56 schrieb munix9:
While the build of a package in home:munix9:gambas works without any problems, in home:munix9:gambas:test the almost same package is suddenly displayed as “unresolvable”.
This means that system packages are missing that are actually there.
Even stranger is that the build in home:munix9:gambas:test has already worked, and after a few tests “unresolvable” is suddenly displayed.
Does anyone have a helpful explanation for this?
Thanks & regards
Ok, a little more testing: If the build files are available natively, the error does not occur, if tar_scm or obs_scm is used via a _service file, then the mentioned “unresolvable” appears. Since this has worked before, I assume that something is wrong in obs - it would be nice if an admin would take a closer look at this. Thanks & regards
Am 17.11.24 um 09:54 schrieb munix9:
Am 17.11.24 um 08:56 schrieb munix9:
While the build of a package in home:munix9:gambas works without any problems, in home:munix9:gambas:test the almost same package is suddenly displayed as “unresolvable”.
This means that system packages are missing that are actually there.
Even stranger is that the build in home:munix9:gambas:test has already worked, and after a few tests “unresolvable” is suddenly displayed.
Does anyone have a helpful explanation for this?
Thanks & regards
Ok, a little more testing:
If the build files are available natively, the error does not occur, if tar_scm or obs_scm is used via a _service file, then the mentioned “unresolvable” appears.
Since this has worked before, I assume that something is wrong in obs - it would be nice if an admin would take a closer look at this.
Thanks & regards
Part of the problem is solved: Line terminator was PKGBUILD: ASCII text, with CRLF line terminators but must be PKGBUILD: ASCII text The other problem which leads to the fact that I have to use tar_scm and not obs_scm: [ 86s] bsdtar: Failed to set default locale [ 87s] bsdtar: Pathname can't be converted from UTF-8 to current locale. [ 87s] bsdtar: Error exit delayed from previous errors. whatever that means ...
participants (1)
-
munix9