Re: Rawhide buildroot broken by dnf or dnf-plugins-core

2018-11-22 Thread Richard W.M. Jones
On Thu, Nov 22, 2018 at 01:14:18PM +0100, Jaroslav Mracek wrote: > Thanks for your offer, but builds have been finished. Hope that it solved > all of issues. Can confirm it's all working now, thanks. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my

Re: Rawhide buildroot broken by dnf or dnf-plugins-core

2018-11-22 Thread Jaroslav Mracek
Thanks for your offer, but builds have been finished. Hope that it solved all of issues. libdnf-0.22.3-1.fc30 dnf-4.0.9-1.fc30 dnf-plugins-core-4.0.2-1.fc30

Re: Rawhide buildroot broken by dnf or dnf-plugins-core

2018-11-22 Thread Neal Gompa
On Thu, Nov 22, 2018 at 6:25 AM Richard W.M. Jones wrote: > > On Thu, Nov 22, 2018 at 12:21:04PM +0100, Jaroslav Mracek wrote: > > The update of dnf-plugins-core and dnf-plugins-extras is ready for rawhide. > > But I cannot make fedpkg build due to error: > > Kerberos authentication fails: unable

Re: Rawhide buildroot broken by dnf or dnf-plugins-core

2018-11-22 Thread Richard W.M. Jones
On Thu, Nov 22, 2018 at 12:21:04PM +0100, Jaroslav Mracek wrote: > The update of dnf-plugins-core and dnf-plugins-extras is ready for rawhide. > But I cannot make fedpkg build due to error: > Kerberos authentication fails: unable to obtain a session > Could not execute build: Could not login to >

Re: Rawhide buildroot broken by dnf or dnf-plugins-core

2018-11-22 Thread Jaroslav Mracek
The update of dnf-plugins-core and dnf-plugins-extras is ready for rawhide. But I cannot make fedpkg build due to error: Kerberos authentication fails: unable to obtain a session Could not execute build: Could not login to https://koji.fedoraproject.org/kojihub I will ask a college to do it for

Rawhide buildroot broken by dnf or dnf-plugins-core

2018-11-22 Thread Richard W.M. Jones
DEBUG util.py:439: Error: DEBUG util.py:439: Problem: package dnf-plugins-core-4.0.0-2.fc30.noarch requires python3-dnf-plugins-core = 4.0.0-2.fc30, but none of the providers can be installed DEBUG util.py:439:- package dnf-4.0.9-1.fc30.noarch conflicts with python3-dnf-plugins-core <

Re: Rawhide buildroot broken?

2018-02-04 Thread Doug Ledford
On Sun, 2018-02-04 at 14:30 -0800, Kevin Fenzi wrote: > On 02/04/2018 01:38 PM, Jan Kratochvil wrote: > > On Sun, 04 Feb 2018 22:14:47 +0100, Doug Ledford wrote: > > > cc1: fatal error: inaccessible plugin file plugin/annobin.so expanded > > > from short plugin name annobin: No such file or

Re: Rawhide buildroot broken?

2018-02-04 Thread Kevin Fenzi
On 02/04/2018 01:38 PM, Jan Kratochvil wrote: > On Sun, 04 Feb 2018 22:14:47 +0100, Doug Ledford wrote: >> cc1: fatal error: inaccessible plugin file plugin/annobin.so expanded >> from short plugin name annobin: No such file or directory > ... >> So, where is the gcc plugin annobin? > > In

Re: Rawhide buildroot broken?

2018-02-04 Thread Jan Kratochvil
On Sun, 04 Feb 2018 22:14:47 +0100, Doug Ledford wrote: > cc1: fatal error: inaccessible plugin file plugin/annobin.so expanded > from short plugin name annobin: No such file or directory ... > So, where is the gcc plugin annobin? In my fresh Rawhide buildroot

Rawhide buildroot broken?

2018-02-04 Thread Doug Ledford
I'm having an issue, and as far as I can tell it's not in my package. The rdma-core package uses cmake and ninja-build to build itself, and the very first test in the CMakeLists.txt makefile is the TestCCompiler test that is shipped with CMake, not one of our own tests. And it's failing because

Rawhide buildroot broken?

2013-10-04 Thread Paul Howarth
I'm seeing this in root.log for all Rawhide builds: DEBUG util.py:316: Executing command: ['fedpkg', 'sources'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'echo -n mock-chroot', 'HOME': '/builddir', 'PATH':

Re: Rawhide buildroot broken?

2013-10-04 Thread Jon Ciesla
I'm seeing this too. http://koji.fedoraproject.org/koji/taskinfo?taskID=6024388 -J On Fri, Oct 4, 2013 at 8:22 AM, Paul Howarth p...@city-fan.org wrote: I'm seeing this in root.log for all Rawhide builds: DEBUG util.py:316: Executing command: ['fedpkg', 'sources'] with env {'LANG':

Re: Rawhide buildroot broken?

2013-10-04 Thread Dan Mashal
Seems to be working OK here. Dan On Fri, Oct 4, 2013 at 6:24 AM, Jon Ciesla limburg...@gmail.com wrote: I'm seeing this too. http://koji.fedoraproject.org/koji/taskinfo?taskID=6024388 -J On Fri, Oct 4, 2013 at 8:22 AM, Paul Howarth p...@city-fan.org wrote: I'm seeing this in root.log

Re: Rawhide buildroot broken?

2013-10-04 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/2013 10:10 AM, Dan Mashal wrote: Seems to be working OK here. Dan On Fri, Oct 4, 2013 at 6:24 AM, Jon Ciesla limburg...@gmail.com wrote: I'm seeing this too. http://koji.fedoraproject.org/koji/taskinfo?taskID=6024388 -J On

Re: Rawhide buildroot broken?

2013-10-04 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/2013 10:20 AM, Stephen Gallagher wrote: On 10/04/2013 10:10 AM, Dan Mashal wrote: Seems to be working OK here. Dan On Fri, Oct 4, 2013 at 6:24 AM, Jon Ciesla limburg...@gmail.com wrote: I'm seeing this too.

Rawhide buildroot broken?

2013-06-19 Thread Jerry James
I just tried to do a Rawhide build (http://koji.fedoraproject.org/koji/taskinfo?taskID=5521135), and got this in root.log: ... DEBUG util.py:264: Transaction Summary DEBUG util.py:264: DEBUG util.py:264: Install

Re: Rawhide buildroot broken?

2013-06-19 Thread Kevin Fenzi
On Wed, 19 Jun 2013 09:36:58 -0600 Jerry James loganje...@gmail.com wrote: I just tried to do a Rawhide build (http://koji.fedoraproject.org/koji/taskinfo?taskID=5521135), and got this in root.log: ...snip... What's going on with the filesystem package? It's broken. ;) I've already

Re: Rawhide buildroot broken?

2013-06-19 Thread Jerry James
On Wed, Jun 19, 2013 at 9:38 AM, Kevin Fenzi ke...@scrye.com wrote: It's broken. ;) I've already untagged it and mailed the maintainer who is looking into it. Should be ready to build after the next newrepo finishes. Excellent! Thanks, Kevin. -- Jerry James http://www.jamezone.org/ --

Re: rawhide buildroot broken: octave packages?

2012-12-04 Thread José Matos
On 2012-12-04 02:08, Ankur Sinha wrote: Hi folks, I recently packaged octave-odepkg[1] reviewed and approved for fedora. I've been able to build it for both f18 and f17, but the rawhide builds keep failing because of what looks like a broken dep chain: INFO: Results and/or logs in:

Re: rawhide buildroot broken: octave packages?

2012-12-04 Thread Orion Poplawski
On 12/04/2012 07:39 AM, José Matos wrote: On 2012-12-04 02:08, Ankur Sinha wrote: Hi folks, I recently packaged octave-odepkg[1] reviewed and approved for fedora. I've been able to build it for both f18 and f17, but the rawhide builds keep failing because of what looks like a broken dep chain:

rawhide buildroot broken: octave packages?

2012-12-03 Thread Ankur Sinha
Hi folks, I recently packaged octave-odepkg[1] reviewed and approved for fedora. I've been able to build it for both f18 and f17, but the rawhide builds keep failing because of what looks like a broken dep chain: INFO: Results and/or logs in: /var/lib/mock/fedora-rawhide-x86_64/result ERROR:

Re: rawhide buildroot broken: octave packages?

2012-12-03 Thread Bruno Wolff III
On Tue, Dec 04, 2012 at 13:08:13 +1100, Ankur Sinha sanjay.an...@gmail.com wrote: Hi folks, I recently packaged octave-odepkg[1] reviewed and approved for fedora. I've been able to build it for both f18 and f17, but the rawhide builds keep failing because of what looks like a broken dep

Re: rawhide buildroot broken: octave packages?

2012-12-03 Thread Ankur Sinha
On Mon, 2012-12-03 at 21:52 -0600, Bruno Wolff III wrote: On Tue, Dec 04, 2012 at 13:08:13 +1100, Ankur Sinha sanjay.an...@gmail.com wrote: Hi folks, I recently packaged octave-odepkg[1] reviewed and approved for fedora. I've been able to build it for both f18 and f17, but the rawhide

Rawhide buildroot broken - I rebuilt libtool

2012-06-29 Thread Richard W.M. Jones
DEBUG util.py:257: Error: Package: libtool-2.4.2-3.fc17.x86_64 (build) DEBUG util.py:257: Requires: gcc = 4.7.0 DEBUG util.py:257: Installed: gcc-4.7.1-1.fc18.x86_64 (@build/$releasever) DEBUG util.py:257: gcc = 4.7.1-1.fc18 DEBUG util.py:257: You could