_service with "obs_scm" and "tar" error: /usr/lib/obs/service//tar.service No such file or directory
Hi, I try to edit "_service" and switch from '<service name="tar_scm">' to '<service name="obs_scm">'. However I get error in OBS: Files could not be expanded: service error: 400 remote error: /usr/lib/obs/service//tar.service No such file or directory I saw comment, elsewhere examples that 'tar' is not needed in OBS, only at buildtime, however: 1) source code is much larger (~70MB of obscpio archive) than TAR.GZ compressed archive (~24MB); 2) this source code con not be build for other distributions than openSUSE. Indeed, if I add mode="buildtime" (for build in OBS) or mode="localonly" (for recompress in local computer) – it works, but how to use TAR.GZ or TAR.XZ compression in OBS prior buidtime (as it was with '<service name="tar_scm">')? If not, how long '<service name="tar_scm">' will be supported? P.S. _service content: <services> <service name="obs_scm"> <param name="filename">goldendict</param> <param name="scm">git</param> <param name="url">git://github.com/xiaoyifang/goldendict.git</param> <param name="revision">feature/qwebengine-port</param> <param name="versionformat">1.5.0~rc2+git.%ci</param> <param name="changesgenerate">disable</param> </service> <service name="set_version"/> <service name="tar"/><!-- mode="buildtime" mode="localonly" --> <service name="recompress"><!-- mode="buildtime" mode="localonly" --> <param name="compression">xz</param> <param name="file">*.tar</param> </service> </services> -- Regards, Mindaugas
On Dienstag, 8. Februar 2022, 07:42:56 CET opensuse.lietuviu.kalba wrote:
Hi,
I try to edit "_service" and switch from '<service name="tar_scm">' to '<service name="obs_scm">'. However I get error in OBS:
Files could not be expanded: service error: 400 remote error: /usr/lib/obs/service//tar.service No such file or directory
yes, not installed on purpose on the service server.
I saw comment, elsewhere examples that 'tar' is not needed in OBS, only at buildtime, however: 1) source code is much larger (~70MB of obscpio archive) than TAR.GZ compressed archive (~24MB);
obscpio archives can get stored incremental, so therefore we win by using them instead of using tar archives.
2) this source code con not be build for other distributions than openSUSE.
you lack services at buildtime? Build against the openSUSE:Tools repo then. It provides them for most distros.
Indeed, if I add mode="buildtime" (for build in OBS) or mode="localonly" (for recompress in local computer) – it works, but how to use TAR.GZ or TAR.XZ compression in OBS prior buidtime (as it was with '<service name="tar_scm">')? If not, how long '<service name="tar_scm">' will be supported?
P.S. _service content:
<services> <service name="obs_scm"> <param name="filename">goldendict</param> <param name="scm">git</param> <param name="url">git://github.com/xiaoyifang/goldendict.git</param> <param name="revision">feature/qwebengine-port</param> <param name="versionformat">1.5.0~rc2+git.%ci</param> <param name="changesgenerate">disable</param> </service> <service name="set_version"/> <service name="tar"/><!-- mode="buildtime" mode="localonly" --> <service name="recompress"><!-- mode="buildtime" mode="localonly" --> <param name="compression">xz</param> <param name="file">*.tar</param> </service> </services>
-- Regards, Mindaugas
--
Adrian Schroeter
On Tuesday 2022-02-08 07:49, Adrian Schröter wrote:
I saw comment, elsewhere examples that 'tar' is not needed in OBS, only at buildtime, however: 1) source code is much larger (~70MB of obscpio archive) than TAR.GZ compressed archive (~24MB);
obscpio archives can get stored incremental, so therefore we win by using them instead of using tar archives.
cpio seems like such a silly choice. rpmbuild/quilt can't handle Source: x.cpio lines; on the other hand, tar should support incrementalism just fine (tar -G). If anything, it would be the optional compression on top that "breaks" such a feature.
On Dienstag, 8. Februar 2022, 10:17:31 CET Jan Engelhardt wrote:
On Tuesday 2022-02-08 07:49, Adrian Schröter wrote:
I saw comment, elsewhere examples that 'tar' is not needed in OBS, only at buildtime, however: 1) source code is much larger (~70MB of obscpio archive) than TAR.GZ compressed archive (~24MB);
obscpio archives can get stored incremental, so therefore we win by using them instead of using tar archives.
cpio seems like such a silly choice. rpmbuild/quilt can't handle Source: x.cpio lines; on the other hand, tar should support incrementalism just fine (tar -G).
tar format is unfortunatly way more complex, so the implementation is nearly impossible.
If anything, it would be the optional compression on top that "breaks" such a feature.
yes.
Future solution should be the git remote assets. This will also improve
the tracebility of the upstream sources.
--
Adrian Schroeter
participants (3)
-
Adrian Schröter -
Jan Engelhardt -
opensuse.lietuviu.kalba