(I got this reply privately, but I think it was meant for the list) On 13.4.2011 15:28, Michal Vyskocil wrote:
On Wed, Apr 13, 2011 at 11:36:25AM +0200, Michal Marek wrote:
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
Well, as osc build runs all service files by default on each build, which is braindead, as people will be really confused why their build has a delay (during it they can download 70MB big file ...).
I don't observe this with osc-0.130.1 2, osc build uses the existing _service:download_url:linux-2.6.39-rc3.tar.bz2 tarball.
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?
You can either skip this check by -f or check_filelist in ~/.oscrc, see source code
3087 if conf.config['check_filelist'] and not opts.force: 3088 check_filelist_before_commit(pacs)
I'm aware of the global config, but this is really specific to one package.
As an original author I'd say we can remove this one, as this is a duplicate of source-validator.
Great, that would solve my problem. I don't care if the tarball shows up with a question mark in 'osc status', as long as it doesn't complain during commit.
If you want to write a patch, then consider reverting of existing braindead osc build logic and add add --service, --force-service, or --run-service option to force a _service execution. Or in the most clever case, save a time of last execution and compare a timestamp, so the _service files will be triggered only in case of change.
The current logic works fine for my specific use case. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org