[opensuse-buildservice] .oscignore to ignore tarballs downloaded by source service?
Hi, I see there is no way to set ignore patterns on a per-package basis, i.e. some .oscignore or rather _oscignore file. Would you accept a patch that adds such feature? The problem I'm trying to solve is following: The kernel-source package is maintained in a git repository and a script exists to generate a source package that can be built using rpmbuild, osc build or the buildservice. To avoid having to upload the 70M+ linux tarball each time you branch the package in the buildservice, I would like to use the download_url service to let the server download it. But at the same time, I would like to have the tarball locally as before, so that plain rpmbuild works. But then I need to tell osc to ignore the linux tarball and avoid messages like this: $ osc ci File "linux-2.6.38.tar.bz2" is listed in package meta but does not exist. (s)kip/(r)emove/(e)dit file lists/(c)ommit/(A)bort? I *could* save the tarball as "_service:download_url:linux-2.6.38.tar.bz2", which osc properly ignores, and handle such filename in the %prep section, but that would be really hackish. Being able to just do echo "linux-$version.tar.bz2" >kernel-source/_oscignore when generating the source package would be much cleaner. Thanks, Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, On 2011-04-13 11:36:25 +0200, Michal Marek wrote:
I see there is no way to set ignore patterns on a per-package basis, i.e. some .oscignore or rather _oscignore file. Would you accept a patch that adds such feature?
I'm always happy about patches:) (I'm even more happy if a testcase is attached, too:)) (to implement such a feature these files should be marked with state "S" (skipped)).
The problem I'm trying to solve is following: The kernel-source package is maintained in a git repository and a script exists to generate a source package that can be built using rpmbuild, osc build or the buildservice. To avoid having to upload the 70M+ linux tarball each time you branch the package in the buildservice, I would like to use the download_url service to let the server download it. But at the same time, I would like to have the tarball locally as before, so that plain rpmbuild works. But then I need to tell osc to ignore the linux tarball and avoid messages like this:
Hmm what about the following: Either - use "osc service run" in the package working copy so that osc executes the source services locally (it'll create the _service:download_url:linux... file) - or run "osc up -S" to download the "_service:download_url:linux..." file from the obs In both cases osc won't bother you when doing the commit. Does this help? Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 13.4.2011 14:16, Marcus Hüwe wrote:
Hi,
On 2011-04-13 11:36:25 +0200, Michal Marek wrote:
I see there is no way to set ignore patterns on a per-package basis, i.e. some .oscignore or rather _oscignore file. Would you accept a patch that adds such feature?
I'm always happy about patches:) (I'm even more happy if a testcase is attached, too:)) (to implement such a feature these files should be marked with state "S" (skipped)).
OK.
To avoid having to upload the 70M+ linux tarball each time you branch the package in the buildservice, I would like to use the download_url service to let the server download it. But at the same time, I would like to have the tarball locally as before, so that plain rpmbuild works. But then I need to tell osc to ignore the linux tarball and avoid messages like this:
Hmm what about the following: Either - use "osc service run" in the package working copy so that osc executes the source services locally (it'll create the _service:download_url:linux... file) - or run "osc up -S" to download the "_service:download_url:linux..." file from the obs
In both cases osc won't bother you when doing the commit.
The problem is how to support plain rpmbuild, which expects linux-$version.tar.bz2, at the same time. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Michal Marek wrote:
On 13.4.2011 14:16, Marcus Hüwe wrote:
On 2011-04-13 11:36:25 +0200, Michal Marek wrote:
To avoid having to upload the 70M+ linux tarball each time you branch the package in the buildservice, I would like to use the download_url service to let the server download it. But at the same time, I would like to have the tarball locally as before, so that plain rpmbuild works. But then I need to tell osc to ignore the linux tarball and avoid messages like this:
Hmm what about the following: Either - use "osc service run" in the package working copy so that osc executes the source services locally (it'll create the _service:download_url:linux... file) - or run "osc up -S" to download the "_service:download_url:linux..." file from the obs
In both cases osc won't bother you when doing the commit.
The problem is how to support plain rpmbuild, which expects linux-$version.tar.bz2, at the same time.
That use case likely wasn't thought of. Those _service:* files are ugly anyways IMO. Maybe we should just get rid of them and implement services differently. The obs services could for example write an index file that lists all files maintained by source services. osc could then read that index and ignore the files listed in it. The obs server side must then deny pushing files listed in the index instead of matching for _service:*. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 14.4.2011 09:47, Ludwig Nussel wrote:
That use case likely wasn't thought of. Those _service:* files are ugly anyways IMO. Maybe we should just get rid of them and implement services differently. The obs services could for example write an index file that lists all files maintained by source services. osc could then read that index and ignore the files listed in it. The obs server side must then deny pushing files listed in the index instead of matching for _service:*.
From my end-user point of view, that sounds like a good idea. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Ludwig Nussel -
Marcus Hüwe -
Michal Marek