Hi,
Considering that the KDE builds are still failing, what is a fairly failsafe way to add packages to the Scientific spin (which is based on KDE) and then push the changes ?
Shall I build on Fedora 19, and if all is fine, commit the changes? (after checking if those packages are present in F20 as well)
Thanks for any input.
Best, Amit.
On Wed, Aug 21, 2013 at 22:31:24 -0400, Amit Saha asaha@redhat.com wrote:
Hi,
Considering that the KDE builds are still failing, what is a fairly failsafe way to add packages to the Scientific spin (which is based on KDE) and then push the changes ?
What is your end goal?
Shall I build on Fedora 19, and if all is fine, commit the changes? (after checking if those packages are present in F20 as well)
If you are talking about building live images using the f19 repo, that probably won't test what you want. If you are talking about build the live images on an f19 system using f20 or rawhide repos, that is probably reasonable.
If the problem with builds you are seeing is with dependency resolution, you might try helping resolve those.
----- Original Message -----
From: "Bruno Wolff III" bruno@wolff.to To: "Amit Saha" asaha@redhat.com Cc: "The Spin Special Interest Group mailing list" spins@lists.fedoraproject.org Sent: Thursday, August 22, 2013 11:42:57 PM Subject: Re: [Fedora-spins] KDE spin builds
On Wed, Aug 21, 2013 at 22:31:24 -0400, Amit Saha asaha@redhat.com wrote:
Hi,
Considering that the KDE builds are still failing, what is a fairly failsafe way to add packages to the Scientific spin (which is based on KDE) and then push the changes ?
What is your end goal?
Add new packages to the spin.
Shall I build on Fedora 19, and if all is fine, commit the changes? (after checking if those packages are present in F20 as well)
If you are talking about building live images using the f19 repo, that probably won't test what you want. If you are talking about build the live images on an f19 system using f20 or rawhide repos, that is probably reasonable.
If the problem with builds you are seeing is with dependency resolution, you might try helping resolve those.
This is what I am talking about: http://kojipkgs.fedoraproject.org//work/tasks/7089/5847089/root.log
Thanks, Amit.
On Sat, Aug 24, 2013 at 13:43:22 -0400, Amit Saha asaha@redhat.com wrote:
This is what I am talking about: http://kojipkgs.fedoraproject.org//work/tasks/7089/5847089/root.log
This suggests that hugin-base was not rebuilt after the boost update. Checking koji shows the package is FTBFS. You could try to figure out why this is happening and if you figure it out and contact the maintainers. You might also want to consider avoiding that package if it looks like getting it fixed is going to be a problem, since the release isn't that far off.
----- Original Message -----
From: "Bruno Wolff III" bruno@wolff.to To: "Amit Saha" asaha@redhat.com Cc: "The Spin Special Interest Group mailing list" spins@lists.fedoraproject.org Sent: Sunday, August 25, 2013 5:29:47 AM Subject: Re: [Fedora-spins] KDE spin builds
On Sat, Aug 24, 2013 at 13:43:22 -0400, Amit Saha asaha@redhat.com wrote:
This is what I am talking about: http://kojipkgs.fedoraproject.org//work/tasks/7089/5847089/root.log
This suggests that hugin-base was not rebuilt after the boost update. Checking koji shows the package is FTBFS. You could try to figure out why this is happening and if you figure it out and contact the maintainers. You might also want to consider avoiding that package if it looks like getting it fixed is going to be a problem, since the release isn't that far off.
Unfortunately, the root.log is for the KDE spin build upon which the Scientific spin is built upon. I will have to make some time to figure it out, let's see.
Thanks, Amit.
On Mon, Aug 26, 2013 at 01:14:16 -0400, Amit Saha asaha@redhat.com wrote:
Unfortunately, the root.log is for the KDE spin build upon which the Scientific spin is built upon. I will have to make some time to figure it out, let's see.
It isn't a spin specific problem. hugin-base (from hugin) needs to be rebuilt in order to be able to link with the current version of boost. However it is failing to build for some reason. So the place to help out is getting hugin to build again. If this is really blocking the KDE spin, then an alpha blocker bug should be filed against hugin. In the likely case that there is already an FTBFS bug filed against hugin, you can just nominate that one as an alpha blocker.