Re: Strange rawhide behaviour

On Sun, Feb 03, 2019 at 05:27:45PM -0500, Neal Gompa wrote: > On Sat, Feb 2, 2019 at 3:51 PM Adam Williamson > wrote: > > > > On Wed, 2019-01-30 at 15:37 +0100, Michal Schorm wrote: > > > Right. > > > > > > Yes, I'm trying to test the installation from the mirrors. There will > > > be a delay. > >

Re: Strange rawhide behaviour

On Sat, Feb 2, 2019 at 3:51 PM Adam Williamson wrote: > > On Wed, 2019-01-30 at 15:37 +0100, Michal Schorm wrote: > > Right. > > > > Yes, I'm trying to test the installation from the mirrors. There will > > be a delay. > > > > Buildroot repo != compose repo. > > That's where I was mistaken. > > >

Re: Strange rawhide behaviour

On 2/1/19 2:17 AM, Dan Horák wrote: > On Fri, 1 Feb 2019 11:01:26 +0100 > > BTW wouldn't it make sense to expand the list of mandatory products, > that must succeed for the whole to compose to succeed, when getting > closer to the release? Like after branch point to have a single product > (x86 e

Re: Strange rawhide behaviour

On Fri, 2019-02-01 at 11:07 +0100, Miro Hrončok wrote: > On 01. 02. 19 11:01, Miro Hrončok wrote: > > On 31. 01. 19 11:43, Miro Hrončok wrote: > > > On 31. 01. 19 11:18, Miro Hrončok wrote: > > > > On 31. 01. 19 10:56, Adam Williamson wrote: > > > > > Just as a note, what's in the 'rawhide' repo ri

Re: Strange rawhide behaviour

On 01. 02. 19 11:08, Dan Horák wrote: On Fri, 1 Feb 2019 11:01:26 +0100 Miro Hrončok wrote: On 31. 01. 19 11:43, Miro Hrončok wrote: On 31. 01. 19 11:18, Miro Hrončok wrote: On 31. 01. 19 10:56, Adam Williamson wrote: Just as a note, what's in the 'rawhide' repo right now differs quite a lo

Re: Strange rawhide behaviour

On Fri, 1 Feb 2019 11:01:26 +0100 Miro Hrončok wrote: > On 31. 01. 19 11:43, Miro Hrončok wrote: > > On 31. 01. 19 11:18, Miro Hrončok wrote: > >> On 31. 01. 19 10:56, Adam Williamson wrote: > >>> Just as a note, what's in the 'rawhide' repo right now differs > >>> quite a lot from what's in the

Re: Strange rawhide behaviour

On Fri, 1 Feb 2019 11:01:26 +0100 Miro Hrončok wrote: > On 31. 01. 19 11:43, Miro Hrončok wrote: > > On 31. 01. 19 11:18, Miro Hrončok wrote: > >> On 31. 01. 19 10:56, Adam Williamson wrote: > >>> Just as a note, what's in the 'rawhide' repo right now differs > >>> quite a lot from what's in the

Re: Strange rawhide behaviour

On 01. 02. 19 11:01, Miro Hrončok wrote: On 31. 01. 19 11:43, Miro Hrončok wrote: On 31. 01. 19 11:18, Miro Hrončok wrote: On 31. 01. 19 10:56, Adam Williamson wrote: Just as a note, what's in the 'rawhide' repo right now differs quite a lot from what's in the buildroot as we haven't had a suc

Re: Strange rawhide behaviour

On 31. 01. 19 11:43, Miro Hrončok wrote: On 31. 01. 19 11:18, Miro Hrončok wrote: On 31. 01. 19 10:56, Adam Williamson wrote: Just as a note, what's in the 'rawhide' repo right now differs quite a lot from what's in the buildroot as we haven't had a successful compose since 2019-01-21. This is

Re: Strange rawhide behaviour

On 31. 01. 19 11:51, Stephen John Smoogen wrote: On Thu, 31 Jan 2019 at 05:21, Miro Hrončok > wrote: On 31. 01. 19 10:56, Adam Williamson wrote: > Just as a note, what's in the 'rawhide' repo right now differs quite a > lot from what's in the buildroo

Re: Strange rawhide behaviour

On Thu, 31 Jan 2019 at 05:21, Miro Hrončok wrote: > On 31. 01. 19 10:56, Adam Williamson wrote: > > Just as a note, what's in the 'rawhide' repo right now differs quite a > > lot from what's in the buildroot as we haven't had a successful compose > > since 2019-01-21. This is for various reasons

Re: Strange rawhide behaviour

On 31. 01. 19 11:18, Miro Hrončok wrote: On 31. 01. 19 10:56, Adam Williamson wrote: Just as a note, what's in the 'rawhide' repo right now differs quite a lot from what's in the buildroot as we haven't had a successful compose since 2019-01-21. This is for various reasons - most recently libreo

Re: Strange rawhide behaviour

On 31. 01. 19 10:56, Adam Williamson wrote: Just as a note, what's in the 'rawhide' repo right now differs quite a lot from what's in the buildroot as we haven't had a successful compose since 2019-01-21. This is for various reasons - most recently libreoffice needed rebuilding for the poppler so

Re: Strange rawhide behaviour

On Wed, 2019-01-30 at 15:37 +0100, Michal Schorm wrote: > Right. > > Yes, I'm trying to test the installation from the mirrors. There will > be a delay. > > Buildroot repo != compose repo. > That's where I was mistaken. > > Case closed, I'll wait :) Just as a note, what's in the 'rawhide' repo

Re: Strange rawhide behaviour

Am Mittwoch, den 30.01.2019, 15:50 +0100 schrieb Tomasz Torcz: > I saw exactly this on Monday. I submitted a build of owfs package, > which immediately failed with > DEBUG util.py:490: BUILDSTDERR: - nothing provides gcc = 8.69 > needed by annobin-8.69-2.fc30.x86_64 > > Strange thing was,

Re: Strange rawhide behaviour

On 30/01/2019 14:50, Tomasz Torcz wrote: I saw exactly this on Monday. I submitted a build of owfs package, which immediately failed with DEBUG util.py:490: BUILDSTDERR: - nothing provides gcc = 8.69 needed by annobin-8.69-2.fc30.x86_64 Strange thing was, annobin-8.69-2.fc30.x86_64

Re: Strange rawhide behaviour

On Wed, Jan 30, 2019 at 03:20:31PM +0100, Michal Schorm wrote: > On Wed, Jan 30, 2019 at 3:06 PM Fabio Valentini wrote: > > Not necessarily. Builds are only pushed to repositories after a successful > > compose, but are available in koji only a few minutes after they were built. > > That means th

Re: Strange rawhide behaviour

Yes I think it's been about a week since the last rawhide compose so the mirrors are well out of date. With the mass rebuild about to start it's probably not going to get better any time soon either... Tom On 30/01/2019 14:37, Michal Schorm wrote: Right. Yes, I'm trying to test the installati

Re: Strange rawhide behaviour

Right. Yes, I'm trying to test the installation from the mirrors. There will be a delay. Buildroot repo != compose repo. That's where I was mistaken. Case closed, I'll wait :) Thanks -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Wed, Jan 30, 2019 at 3:30 PM T

Re: Strange rawhide behaviour

What do you mean by "install time" exactly? Do you mean you have a system using rawhide from the mirrors and you are trying to install there? If so are you installing community-mysql itself from the mirrors? or have you fetched than from koji to install manually? Tom On 30/01/2019 14:20, Micha

Re: Strange rawhide behaviour

* Michal Schorm: > That means, it was available in the buildroot, but not in the repository. > How is that possible? The buildroot also need the exact same > repository to install packages from, right? The default repository for mock and installations is a compose. It is regularly recreated from

Re: Strange rawhide behaviour

On Wed, Jan 30, 2019 at 3:06 PM Fabio Valentini wrote: > Not necessarily. Builds are only pushed to repositories after a successful > compose, but are available in koji only a few minutes after they were built. > That means that packages built locally or on COPR (which use the rawhide > reposito

Re: Strange rawhide behaviour

On Wed, Jan 30, 2019, 14:56 Michal Schorm Hello, > > I built "community-mysql" package in version 8.0.14 in rawhide. > It was built on top of "libicu-devel" 63.1-1.fc30 > > -- > > 1) > But when I tried to install the community-mysql package into Rawhide, I > got: > nothing provides libicuio.so.63(