I want to maintain amdgpu_top in Factory and would like to use hardware as the devel/feeder project. This is a tool that allows users to check AMD GPU utilization.
The README for obs-service-tar_scm states that tar_scm is deprecated and obs_scm with obscpio is the preferred way to package. Is that not the case?
The referenced source can be generated by running the tar and recompress source services.
Although I don't mind changing it, if it's a problem.
That's very unfortunate. In the typical mindset of 'move forward, break things' (not really move fast when OBS is concerned) a new option is provided which is not really finished to usable state, yet the old option is marked deprecated.
There is similarly a push to use mutibuild instead of package links yet multibuild is not fully equivalent, functionality-wise.
I want to maintain amdgpu_top in Factory and would like to use hardware as the devel/feeder project. This is a tool that allows users to check AMD GPU utilization.
Can you use intelligible source format?
obscpio is not recognized by rpmbuild.
In fact the package is broken for rpmbuild because the referenced source does not exist.
The README for obs-service-tar_scm states that tar_scm is deprecated and obs_scm with obscpio is the preferred way to package. Is that not the case? The referenced source can be generated by running the tar and recompress source services. Although I don't mind changing it, if it's a problem.
That's very unfortunate. In the typical mindset of 'move forward, break things' (not really move fast when OBS is concerned) a new option is provided which is not really finished to usable state, yet the old option is marked deprecated.
There is similarly a push to use mutibuild instead of package links yet multibuild is not fully equivalent, functionality-wise.
deprecated does not mean gone. so just stick to tar_scm. I know I do.
@a_faerber, @duwe, @hreinecke, @jengelh, @lrupp, @michals, @seife, @seilerphilipp, @trenn, @tsaupe: review reminder