[opensuse-packaging] OBS tests fail after building package
Hello, I'm trying to build a package[1] that fixes several problems with google-earth. It builds fine and works locally, but the OBS performs some tests after the package is built, which fail. Since it depends on google-earth, which cannot be installed in the OBS as far as I know, is there a way to prevent these tests from running? -------- [1] https://build.opensuse.org/package/show/home:auxsvr/google-earth-fix -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Friday 2015-08-07 15:49, auxsvr wrote:
I'm trying to build a package[1] that fixes several problems with google-earth. It builds fine and works locally, but the OBS performs some tests after the package is built, which fail. Since it depends on google-earth, which cannot be installed in the OBS as far as I know, is there a way to prevent these tests from running?
You will have to make the %post script deal with failure, in particular that puny mkdir call. But a distro package is not well-suited for this task anyway, because at the next installation of GE, they will overwrite your fix again. If you then also uninstall your rpm package, you are then copying back an old GE binary, further breaking the new GE version. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Friday 07 of August 2015 16:14:00 Jan Engelhardt wrote:
You will have to make the %post script deal with failure, in particular that puny mkdir call.
Ok, done.
But a distro package is not well-suited for this task anyway, because at the next installation of GE, they will overwrite your fix again. If you then also uninstall your rpm package, you are then copying back an old GE binary, further breaking the new GE version.
I know it's a hack, nevertheless a needed one, because the problems it fixes are several years old and Google prefers to ship google earth with them. Is there any way to tie the two packages together so that when GE is updated, the fix is reinstalled or the scripts are run? For example, if I make the files affected belong to this package, what will zypper do if GE is updated or reinstalled? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
auxsvr <auxsvr@gmail.com> writes:
Is there any way to tie the two packages together so that when GE is updated, the fix is reinstalled or the scripts are run?
You can use %triggerscript for that. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Monday 10 of August 2015 10:40:51 Andreas Schwab wrote:
auxsvr <auxsvr@gmail.com> writes:
Is there any way to tie the two packages together so that when GE is updated, the fix is reinstalled or the scripts are run?
You can use %triggerscript for that.
I tried replacing %postin and %postun with %triggerin and %triggerun respectively, but no script runs when the fix is installed. Am I doing something wrong? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Show your trigger condition. Отправлено с iPhone
10 авг. 2015 г., в 22:01, auxsvr <auxsvr@gmail.com> написал(а):
On Monday 10 of August 2015 10:40:51 Andreas Schwab wrote: auxsvr <auxsvr@gmail.com> writes:
Is there any way to tie the two packages together so that when GE is updated, the fix is reinstalled or the scripts are run?
You can use %triggerscript for that.
I tried replacing %postin and %postun with %triggerin and %triggerun respectively, but no script runs when the fix is installed. Am I doing something wrong? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Monday 10 of August 2015 23:02:45 Andrei Borzenkov wrote:
Show your trigger condition.
%triggerin -- google-earth %triggerun -- google-earth
From the project[1].
-------- [1] https://build.opensuse.org/package/show/home:auxsvr/google-earth-fix -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
В Mon, 10 Aug 2015 23:25:38 +0300 auxsvr <auxsvr@gmail.com> пишет:
On Monday 10 of August 2015 23:02:45 Andrei Borzenkov wrote:
Show your trigger condition.
%triggerin -- google-earth
%triggerun -- google-earth
From the project[1].
-------- [1] https://build.opensuse.org/package/show/home:auxsvr/google-earth-fix
Both your triggers run, first triggerin then triggerun, so result is NOOP. As in case of pre/post scripts you need to check whether it is first install or update. See http://rpm.org/api/4.4.2.2/triggers.html. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 11 of August 2015 06:35:48 Andrei Borzenkov wrote:
Both your triggers run, first triggerin then triggerun, so result is NOOP. As in case of pre/post scripts you need to check whether it is first install or update. See http://rpm.org/api/4.4.2.2/triggers.html.
I commented out the %triggerun section to no avail. None of the triggers is executed. I'm using oS 132, perhaps its rpm does not support triggers? Any other ideas? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (4)
-
Andreas Schwab -
Andrei Borzenkov -
auxsvr -
Jan Engelhardt