[opensuse-buildservice] Removing binaries fail
for some reasons, but I not able to resolve, why. In order to build vdr-plugin-softhddevice, I needed to add ffmpeg from multimedia:libs to my project home:frispete:vdr. After a successful build, I noticed, that the ffmpeg binaries shouldn't be published, as we all use the packman versions, of course. Diabling the publish flag obviously doesn't cut it after the fact, but an attempt of osc wipebinaries --all home:frispete:vdr ffmpeg didn't cut it either. That smells like a bug, btw. Well, stronger weapons were needed: osc wipebinaries --all home:frispete:vdr but as things stand, after the full project was rebuild and published, the old ffmpeg binaries are still lying around: http://download.opensuse.org/repositories/home:/frispete:/vdr/openSUSE_13.2/... What more can I do to get rid of them? Thanks in advance, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, 2015-09-10 at 18:31 +0200, Hans-Peter Jansen wrote:
for some reasons, but I not able to resolve, why.
In order to build vdr-plugin-softhddevice, I needed to add ffmpeg from multimedia:libs to my project home:frispete:vdr. After a successful build, I noticed, that the ffmpeg binaries shouldn't be published, as we all use the packman versions, of course.
Diabling the publish flag obviously doesn't cut it after the fact, but an attempt of
osc wipebinaries --all home:frispete:vdr ffmpeg
publishing for the package which you want to wipe must be enabled... otherwise, changes of the package are not published to the repository. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thursday 2015-09-10 18:38, Dominique Leuenberger / DimStar wrote:
On Thu, 2015-09-10 at 18:31 +0200, Hans-Peter Jansen wrote:
[...] I needed to add ffmpeg from multimedia:libs to my project home:frispete:vdr. [...] After a successful build, I noticed, that the ffmpeg binaries shouldn't be published, as we all use the packman versions, of course.
Having published enabled in this case is of no ill effect, since you ignore the build result anyway and go with PM instead.. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 10. September 2015 18:55:32 Jan Engelhardt wrote:
On Thursday 2015-09-10 18:38, Dominique Leuenberger / DimStar wrote:
On Thu, 2015-09-10 at 18:31 +0200, Hans-Peter Jansen wrote:
[...] I needed to add ffmpeg from multimedia:libs to my project home:frispete:vdr. [...] After a successful build, I noticed, that the ffmpeg binaries shouldn't be published, as we all use the packman versions, of course.
Having published enabled in this case is of no ill effect, since you ignore the build result anyway and go with PM instead..
Jan, I don't quite grasp, what you want to say here. Having publishing enabled will make the ffmpeg binaries available for download, and those packages are getting in the way of everybody, who wants to use it from a different source. As a coincidence, you updated ffmpeg yesterday, and that might even result in a library mismatch now, if binding against it, while intenting to use another (of version 2.7.2). Looks, like I need to link against a specific version in multimedia:libs to avoid that. What I don't want, is forcing people to fiddle with package locks and the like (as it doesn't always work as expected, when limiting to certain repos). Or do you have something different in mind with saying "ignore build result". Thanks, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thursday 2015-09-10 21:25, Hans-Peter Jansen wrote:
On Donnerstag, 10. September 2015 18:55:32 Jan Engelhardt wrote:
On Thursday 2015-09-10 18:38, Dominique Leuenberger / DimStar wrote:
On Thu, 2015-09-10 at 18:31 +0200, Hans-Peter Jansen wrote:
[...] I needed to add ffmpeg from multimedia:libs to my project home:frispete:vdr. [...] After a successful build, I noticed, that the ffmpeg binaries shouldn't be published, as we all use the packman versions, of course.
Having published enabled in this case is of no ill effect, since you ignore the build result anyway and go with PM instead..
Jan, I don't quite grasp, what you want to say here. Having publishing enabled will make the ffmpeg binaries available for download, and those packages are getting in the way of everybody, who wants to use it from a different source.
At least for `zypper up`, the different value in the vendor tag field between OBS and PMBS is reason enough for zypper up to not change what you have installed, and I would presume most people already have the PMBS one. (Indeed, the consideration leaves `zypper in` out - but that is something anyone will encounter at some point in an installation's lifetime anyhow.) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 10. September 2015 22:15:49 Jan Engelhardt wrote:
On Donnerstag, 10. September 2015 18:55:32 Jan Engelhardt wrote:
On Thursday 2015-09-10 18:38, Dominique Leuenberger / DimStar wrote:
On Thu, 2015-09-10 at 18:31 +0200, Hans-Peter Jansen wrote:
[...] I needed to add ffmpeg from multimedia:libs to my project home:frispete:vdr. [...] After a successful build, I noticed, that the ffmpeg binaries shouldn't be published, as we all use the packman versions, of course.
Having published enabled in this case is of no ill effect, since you ignore the build result anyway and go with PM instead..
Jan, I don't quite grasp, what you want to say here. Having publishing enabled will make the ffmpeg binaries available for download, and those packages are getting in the way of everybody, who wants to use it from a different source. At least for `zypper up`, the different value in the vendor tag field between OBS and PMBS is reason enough for zypper up to not change what you have installed, and I would presume most people already have
On Thursday 2015-09-10 21:25, Hans-Peter Jansen wrote: the PMBS one. (Indeed, the consideration leaves `zypper in` out - but that is something anyone will encounter at some point in an installation's lifetime anyhow.)
And zypper dup as well, which is, what I use to check, if some package in other repos is a preferred one. If all are fine, I even allow it to run. Other times, I cherry pick stuff with zypper in from a denied zypper dup run... Hence, I always try to keep my systems zypper dup safe (and recommend to everyone else to never use it that way ;)! BTW, I think, I finally managed to solve the issue: I disabled build and enabled publish in the project and all packages, then I wiped the project, waited for the files to disappear, linked ffmpeg to the last 2.7.2 revision, disabled publish on ffmpeg, and enabled build of the project. Easy, no?!? I will immolate something for the guards of wasted resources on the next occasion. Pete BTW: the package dtv-scan-tables, linked from vdr project, not changed for the last last 5 month, starts to fail for 13.2 reproducible now, while successfully building for Tumbleweed. Oh well. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 10. September 2015 18:38:56 Dominique Leuenberger / DimStar wrote:
On Thu, 2015-09-10 at 18:31 +0200, Hans-Peter Jansen wrote:
for some reasons, but I not able to resolve, why.
In order to build vdr-plugin-softhddevice, I needed to add ffmpeg from multimedia:libs to my project home:frispete:vdr. After a successful build, I noticed, that the ffmpeg binaries shouldn't be published, as we all use the packman versions, of course.
Diabling the publish flag obviously doesn't cut it after the fact, but an attempt of
osc wipebinaries --all home:frispete:vdr ffmpeg
publishing for the package which you want to wipe must be enabled... otherwise, changes of the package are not published to the repository.
Dear Dominique, thanks for the answer, but now I'm even more puzzled with the result. When I entered my workspace, first thing I did was a reload of the 64bit download page to check the state: nothing changed, still a ffmpeg-2.7.2 and friends lying around. Then I read your and Jan's answer, but yours seems to better match my intentions. Hence, I enabled publishing just to wipe the _package_, and disabled publishing again. Next I checked the result - but that really puzzled me - as that operation made a new ffmpeg version (2.8) appear, which means, that an ffmpeg update was picked up from multimedia:libs and built meanwhile. The small time window of enable publishing was enough to push it out, and the wipe - even with publishing enabled - seem to be dysfunctional. The situation is even uglier now, since there's a version mismatch with the packman version. Hrmpf. Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Dominique Leuenberger / DimStar -
Hans-Peter Jansen -
Jan Engelhardt