Hello,
I have added the following chroots
custom-1-i386 custom-1-ppc64le custom-1-x86_64 epel-7-i386
and removed
fedora-rawhide-i386 fedora-rawhide-x86_64 .
Custom chroots were a long expected feature that enable you to configure your build environment almost at free will (by additional repos per chroot and additional buildroot packages).
epel-7-i386 chroot was requested in *Bug 1271977* https://bugzilla.redhat.com/show_bug.cgi?id=1271977 - RFE - asking for el7 i386 build option. It was somehow missed when epel-7 chroots were added so finally we have it.
fedora-rawhide chroots were some residue of the yesterday's release. They should have been already disabled as fedora-26 chroots replaced them.
clime
On Friday, December 2, 2016 11:13:20 AM CET Michal Novotny wrote:
fedora-rawhide chroots were some residue of the yesterday's release. They should have been already disabled as fedora-26 chroots replaced them.
Ah, when I saw rawhide chroots available this morning I was very happy (after your announcement, it looked like 26 && rawhide chroots will coexist, which would be really fine).
This Copr update is really nice, thanks for it -- but small sad news is the missing fedora-rawhide chroot: https://bugzilla.redhat.com/show_bug.cgi?id=1400941
Pavel
Dne 2.12.2016 v 11:13 Michal Novotny napsal(a):
It was somehow missed when epel-7 chroots were added so finally we have it.
They were not missed. RHEL7 was released only for x86_64 and so was only CentOS later. Only some time after the release was added i386 for CentOS. And it was never released for RHEL7.
On Sex, 2016-12-02 at 11:13 +0100, Michal Novotny wrote:
Hello,
I have added the following chroots
custom-1-i386 custom-1-ppc64le custom-1-x86_64 epel-7-i386
and removed
fedora-rawhide-i386 fedora-rawhide-x86_64 .
Custom chroots were a long expected feature that enable you to configure your build environment almost at free will (by additional repos per chroot and additional buildroot packages).
epel-7-i386 chroot was requested in Bug 1271977 - RFE - asking for el7 i386 build option. It was somehow missed when epel-7 chroots were added so finally we have it.
fedora-rawhide chroots were some residue of the yesterday's release. They should have been already disabled as fedora-26 chroots replaced them.
something is not right with fedora26 Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26x86_64_ devel', disabling.
Do you have "manual createrepo" option enabled for your project? I.e. does devel subdirectory exist in the repo?
On Sáb, 2016-12-03 at 19:27 +0000, clime@redhat.com wrote:
Do you have "manual createrepo" option enabled for your project? I.e. does devel subdirectory exist in the repo?
No , I don't have manual repo enabled , the repo was rawhide repo but now is f26 , builroot fail to have packages from that project .
The reason is that the backend_rawhide_to_release command that I used for transition of builds from rawhide to f26 copies only the latest successful builds for each package. Your needed dependency, however, comes from a build 468985 that was marked as failed but still contains (as the only one) the required package kde-workspace-libs that in turn contains libtaskmanager.so.4. What was actually copied was the resubmitted build *469002 https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/469002/* containing only kde-workspace-libs for f23 chroot that failed in the previous build. Smarter backend_rawhide_to_release command could be implemented that looks at individual chroots and copies them from even failed builds. For this case, I, however, just copied the build 468985 into fedora-26-x86_64 and fedora-26-i386 chroots (ppc64le was not built). * https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/469002/* On Sat, Dec 3, 2016 at 8:59 PM, Sérgio Basto sergio@serjux.com wrote:
On Sáb, 2016-12-03 at 19:27 +0000, clime@redhat.com wrote:
Do you have "manual createrepo" option enabled for your project? I.e. does devel subdirectory exist in the repo?
No , I don't have manual repo enabled , the repo was rawhide repo but now is f26 , builroot fail to have packages from that project .
-- Sérgio M. B.
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On Sáb, 2016-12-03 at 22:41 +0100, Michal Novotny wrote:
The reason is that the backend_rawhide_to_release command that I used for transition of builds from rawhide to f26 copies only the latest successful builds for each package. Your needed dependency, however, comes from a build 468985 that was marked as failed but still contains (as the only one) the required package kde-workspace-libs that in turn contains libtaskmanager.so.4. What was actually copied was the resubmitted build 469002 containing only kde-workspace-libs for f23 chroot that failed in the previous build. Smarter backend_rawhide_to_release command could be implemented that looks at individual chroots and copies them from even failed builds. For this case, I, however, just copied the build 468985 into fedora-26-x86_64 and fedora-26-i386 chroots (ppc64le was not built).
I built successfully 2 packages for 26 and on 3rd fails [1] with same error: Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26i386_de vel', disabling.
analyzing i686 root.log (to avoid confusions) : error: nothing provides libjasper.so.1 needed by kdelibs-6:4.14.24- 1.fc26.i686 but I just build kdelibs-6:4.14.26-1.fc26 at first build !
I didn't understand what you mean by backend_rawhide_to_release and why it fail to synchronize , what I can try ?
Thanks.
[1] https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/485509 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/485516 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/485591 /
On Sat, Dec 3, 2016 at 8:59 PM, Sérgio Basto sergio@serjux.com wrote:
On Sáb, 2016-12-03 at 19:27 +0000, clime@redhat.com wrote:
Do you have "manual createrepo" option enabled for your project?
I.e.
does devel subdirectory exist in the repo?
No , I don't have manual repo enabled , the repo was rawhide repo but now is f26 , builroot fail to have packages from that project .
-- Sérgio M. B.
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted .org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg
On Sáb, 2016-12-03 at 22:41 +0100, Michal Novotny wrote:
I built successfully 2 packages for 26 and on 3rd fails [1] with same error: Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26i386_de vel', disabling.
analyzing i686 root.log (to avoid confusions) : error: nothing provides libjasper.so.1 needed by kdelibs-6:4.14.24- 1.fc26.i686 but I just build kdelibs-6:4.14.26-1.fc26 at first build !
I didn't understand what you mean by backend_rawhide_to_release and why it fail to synchronize , what I can try ?
Please, find out which package provides libjasper.so.1 and rebuild it for f26 before building your "3rd" package.
Thanks.
[1] https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/485509 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/485516 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/485591 /
On Sex, 2016-12-09 at 11:41 +0000, Michal Novotný wrote:
On Sáb, 2016-12-03 at 22:41 +0100, Michal Novotny wrote:
I built successfully 2 packages for 26 and on 3rd fails [1] with same error: Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26i38 6_de vel', disabling.
analyzing i686 root.log (to avoid confusions) : error: nothing provides libjasper.so.1 needed by kdelibs-6:4.14.24- 1.fc26.i686 but I just build kdelibs-6:4.14.26-1.fc26 at first build !
I didn't understand what you mean by backend_rawhide_to_release and why it fail to synchronize , what I can try ?
Please, find out which package provides libjasper.so.1 and rebuild it for f26 before building your "3rd" package.
I already did that, kdelibs-6:4.14.26-1.fc26 was rebuilt with new libjasper
Thanks.
[1] https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/48 5509 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/48 5516 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/48 5591 /
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg
On Sex, 2016-12-09 at 16:27 +0000, Sérgio Basto wrote:
On Sex, 2016-12-09 at 11:41 +0000, Michal Novotný wrote:
On Sáb, 2016-12-03 at 22:41 +0100, Michal Novotny wrote:
I built successfully 2 packages for 26 and on 3rd fails [1] with same error: Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26i 38 6_de vel', disabling.
analyzing i686 root.log (to avoid confusions) : error: nothing provides libjasper.so.1 needed by kdelibs- 6:4.14.24- 1.fc26.i686 but I just build kdelibs-6:4.14.26-1.fc26 at first build !
I didn't understand what you mean by backend_rawhide_to_release and why it fail to synchronize , what I can try ?
Please, find out which package provides libjasper.so.1 and rebuild it for f26 before building your "3rd" package.
I already did that, kdelibs-6:4.14.26-1.fc26 was rebuilt with new libjasper
Now it is working well [1] still have Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26x86_64_devel', disabling. but it use packages from coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26x86_64
Thank you.
[1] https://copr-be.cloud.fedoraproject.org/results/sergiomb/kde4for23/fedora-26...
Thanks.
[1] https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/ 48 5509 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/ 48 5516 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/ 48 5591 /
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted .o rg
I am glad it finally works. Let us know in case of any further problems.
Thank you
On Sun, Jan 1, 2017 at 6:16 PM, Sérgio Basto sergio@serjux.com wrote:
On Sex, 2016-12-09 at 16:27 +0000, Sérgio Basto wrote:
On Sex, 2016-12-09 at 11:41 +0000, Michal Novotný wrote:
On Sáb, 2016-12-03 at 22:41 +0100, Michal Novotny wrote:
I built successfully 2 packages for 26 and on 3rd fails [1] with same error: Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26i 38 6_de vel', disabling.
analyzing i686 root.log (to avoid confusions) : error: nothing provides libjasper.so.1 needed by kdelibs- 6:4.14.24- 1.fc26.i686 but I just build kdelibs-6:4.14.26-1.fc26 at first build !
I didn't understand what you mean by backend_rawhide_to_release and why it fail to synchronize , what I can try ?
Please, find out which package provides libjasper.so.1 and rebuild it for f26 before building your "3rd" package.
I already did that, kdelibs-6:4.14.26-1.fc26 was rebuilt with new libjasper
Now it is working well [1] still have Failed to synchronize cache for repo 'coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26x86_64_devel', disabling. but it use packages from coprbecloudfedoraprojectorg_results_sergiomb_kde4for23_fedora26x86_64
Thank you.
[1] https://copr-be.cloud.fedoraproject.org/results/ sergiomb/kde4for23/fedora-26-x86_64/00494325-kde-baseapps/root.log.gz
Thanks.
[1] https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/ 48 5509 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/ 48 5516 / https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/build/ 48 5591 /
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted .o rg
-- Sérgio M. B.
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
devel repo is always added as additional repository even if the actual repo is not present. That might be the cause. It was always like this.
copr-devel@lists.fedorahosted.org