https://bugzilla.novell.com/show_bug.cgi?id=756640 https://bugzilla.novell.com/show_bug.cgi?id=756640#c0 Summary: Services aparently run against old versions of spec files Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: source services AssignedTo: adrian@suse.com ReportedBy: christian.morales.vega@gmail.com QAContact: adrian@suse.com Found By: Community User Blocker: --- See https://build.opensuse.org/package/files?package=scummvm&project=home%3ARedDwarf%3Amultimedia as an example. A link to a package to the version 1.4.1 downloads the tarball of the 1.2.0 version. The problem is not specific of the download_files service, it has been also been observed with the format_spec_file (http://lists.opensuse.org/opensuse-buildservice/2012-03/msg00230.html).

From previous tests I guess a retrigger of the service would "fix" the problem in the given scummvm example. That's not the objective, the question is why the file _service:download_url:scummvm-1.2.0.tar.bz2 is right now there.

It's just a theory that I didn't try to verify, but I think the problem triggers when: 1) I have projectA configured to run the format_spec_file (and perhaps also others) service in the server side. 2) I have packageA in projectA. 3)I do a commit of packageA with a spec file that format_spec_file doesn't like. A _service:...*.spec file is created. 4)I do a new commit of packageA, with a spec file that format_spec_file likes, and the _service:...*.spec file dissapears. 5) I create packageB in projectB, subproject of projectA, as a link to packageA. Since projectB is a subproject of projectA the services also trigger for packageB. But I __think__ that the services are running against the old _service:...*.spec file generated in step 3 (and in theory deleted in step 4) instead of against the latest .spec file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.