On Wed, Jun 19, 2019 at 12:48:49AM +0200, Kevin Kofler wrote:
> Kevin Fenzi wrote:
> > I again completely disagree. There is no reason for weeks of breakage.
> > Most of the issues that break composes are unannounced abi bumps where
> > just rebuilding dependent packages fixes it. Or broken deps (l
On Tue, 18 Jun 2019 at 19:42, Kevin Kofler wrote:
> Kevin Fenzi wrote:
>
> This has all worked just fine in the past, before it was decided to make
> basically every single broken dependency fail the entire Rawhide compose.
> Soname bumps did not even have to be announced, they would get announce
On Wed, Jun 19, 2019 at 10:29 AM Vít Ondruch wrote:
>
>
> Dne 18. 06. 19 v 16:54 Aleksandra Fedorova napsal(a):
> > On Tue, Jun 18, 2019 at 1:31 PM Neal Gompa wrote:
> >> On Tue, Jun 18, 2019 at 5:21 AM Aleksandra Fedorova
> >> wrote:
> >>> Hi,
> >>> On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa
Dne 18. 06. 19 v 16:54 Aleksandra Fedorova napsal(a):
> On Tue, Jun 18, 2019 at 1:31 PM Neal Gompa wrote:
>> On Tue, Jun 18, 2019 at 5:21 AM Aleksandra Fedorova
>> wrote:
>>> Hi,
>>> On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa wrote:
On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
Kevin Fenzi wrote:
> I again completely disagree. There is no reason for weeks of breakage.
> Most of the issues that break composes are unannounced abi bumps where
> just rebuilding dependent packages fixes it. Or broken deps (likewise).
> Or mistakes made in kickstarts/comps. Or something that do
Sorry, missed part of the sentence.
> There are several ways how one can implement it. I would personally
> prefer pull requests to dist-git over scratch builds. I think it is
> important to keep some visibility in the system, so that not just the
> owner of a change, but also random lurkers can s
On Tue, Jun 18, 2019 at 1:31 PM Neal Gompa wrote:
>
> On Tue, Jun 18, 2019 at 5:21 AM Aleksandra Fedorova
> wrote:
> >
> > Hi,
> > On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa wrote:
> > >
> > > On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
> > > >
> > > > On 6/17/19 4:47 PM, Kevin Kofler w
On Tue, Jun 18, 2019 at 5:21 AM Aleksandra Fedorova wrote:
>
> Hi,
> On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa wrote:
> >
> > On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
> > >
> > > On 6/17/19 4:47 PM, Kevin Kofler wrote:
> > > > Kevin Fenzi wrote:
> > > >> I disagree. I think we need ga
On Tue, Jun 18, 2019 at 11:21 AM Aleksandra Fedorova wrote:
>
> Hi,
> On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa wrote:
> >
> > On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
> > >
> > > On 6/17/19 4:47 PM, Kevin Kofler wrote:
> > > > Kevin Fenzi wrote:
> > > >> I disagree. I think we need g
Hi,
On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa wrote:
>
> On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
> >
> > On 6/17/19 4:47 PM, Kevin Kofler wrote:
> > > Kevin Fenzi wrote:
> > >> I disagree. I think we need gating to block as much stuff that breaks
> > >> things from landing as we can a
Dne 18. 06. 19 v 2:03 Kevin Fenzi napsal(a):
> On 6/17/19 4:47 PM, Kevin Kofler wrote:
>> Kevin Fenzi wrote:
>>> I disagree. I think we need gating to block as much stuff that breaks
>>> things from landing as we can and then we should find that keeping
>>> composes going is much easier on all of
On Tue, Jun 18, 2019 at 3:01 AM Kevin Fenzi wrote:
>
> On 6/17/19 4:47 PM, Kevin Kofler wrote:
> > Kevin Fenzi wrote:
> >> I disagree. I think we need gating to block as much stuff that breaks
> >> things from landing as we can and then we should find that keeping
> >> composes going is much easie
On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
>
> On 6/17/19 4:47 PM, Kevin Kofler wrote:
> > Kevin Fenzi wrote:
> >> I disagree. I think we need gating to block as much stuff that breaks
> >> things from landing as we can and then we should find that keeping
> >> composes going is much easie
On 6/17/19 4:47 PM, Kevin Kofler wrote:
> Kevin Fenzi wrote:
>> I disagree. I think we need gating to block as much stuff that breaks
>> things from landing as we can and then we should find that keeping
>> composes going is much easier on all of us. Then things can be fixed
>> when gating catches
Kevin Fenzi wrote:
> I disagree. I think we need gating to block as much stuff that breaks
> things from landing as we can and then we should find that keeping
> composes going is much easier on all of us. Then things can be fixed
> when gating catches them and it's on the person who broke things.
On 6/10/19 3:00 PM, Kevin Kofler wrote:
> Martin Kolman wrote:
>> But even for package development and integration you need something that
>> works at least a bit. If you won't get a compose for a few weeks due to
>> the constant breakage you won't get much work done on landing your latest
>> libra
Martin Kolman wrote:
> But even for package development and integration you need something that
> works at least a bit. If you won't get a compose for a few weeks due to
> the constant breakage you won't get much work done on landing your latest
> library rebase or integrating a new package.
In th
- Original Message -
> From: "Kevin Kofler"
> To: devel@lists.fedoraproject.org
> Sent: Sunday, June 9, 2019 12:20:34 AM
> Subject: Re: RFC: Multiple parallel side tags
>
> Nicolas Mailhot via devel wrote:
> > But, what is different here from t
I think there should be some feature in fedpkg, which would check for
side-tag builds and prevent any other builds if there is. The problem
is, that people does not know there are some builds in side tag and that
is understandable.
Vít
Dne 08. 06. 19 v 11:23 Igor Gnatenko napsal(a):
> Hi,
>
> Im
On 08. 06. 19 19:20, Zbigniew Jędrzejewski-Szmek wrote:
On Sat, Jun 08, 2019 at 10:29:29AM -0400, Stephen John Smoogen wrote:
On Sat, Jun 8, 2019 at 6:12 AM Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
Hi,
Imagine situation that somebody is working on KDE rebase and me on
libgit2
Nicolas Mailhot via devel wrote:
> But, what is different here from the Fedora circles / Fedora modules /
> etc endeavours? Isn’t the root problem synchronizing common code paths,
> because free software means pervasive code reuse, apps ends up being
> deployed together, and un-sharing generates co
On Sat, Jun 08, 2019 at 10:29:29AM -0400, Stephen John Smoogen wrote:
> On Sat, Jun 8, 2019 at 6:12 AM Igor Gnatenko <
> ignatenkobr...@fedoraproject.org> wrote:
>
> > Hi,
> >
> > Imagine situation that somebody is working on KDE rebase and me on
> > libgit2 rebase. Both involve rebuilding/updatin
On Sat, Jun 8, 2019 at 6:12 AM Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
> Hi,
>
> Imagine situation that somebody is working on KDE rebase and me on
> libgit2 rebase. Both involve rebuilding/updating some package, let's
> say kf5-ktexteditor.
>
> We both work in different side tags
On Sat, Jun 8, 2019 at 9:15 AM Fabio Valentini wrote:
>
> On Sat, Jun 8, 2019 at 2:10 PM Igor Gnatenko
> wrote:
> >
> > On Sat, Jun 8, 2019 at 12:54 PM Nicolas Mailhot via devel
> > wrote:
> > >
> > > Le samedi 08 juin 2019 à 11:23 +0200, Igor Gnatenko a écrit :
> > > > Hi,
> > > >
> > > > Imagi
On Sat, Jun 8, 2019 at 3:21 PM Fabio Valentini wrote:
>
> On Sat, Jun 8, 2019 at 2:10 PM Igor Gnatenko
> wrote:
> >
> > On Sat, Jun 8, 2019 at 12:54 PM Nicolas Mailhot via devel
> > wrote:
> > >
> > > Le samedi 08 juin 2019 à 11:23 +0200, Igor Gnatenko a écrit :
> > > > Hi,
> > > >
> > > > Imagi
On Sat, Jun 8, 2019 at 2:10 PM Igor Gnatenko
wrote:
>
> On Sat, Jun 8, 2019 at 12:54 PM Nicolas Mailhot via devel
> wrote:
> >
> > Le samedi 08 juin 2019 à 11:23 +0200, Igor Gnatenko a écrit :
> > > Hi,
> > >
> > > Imagine situation that somebody is working on KDE rebase and me on
> > > libgit2 r
On Sat, Jun 8, 2019 at 12:54 PM Nicolas Mailhot via devel
wrote:
>
> Le samedi 08 juin 2019 à 11:23 +0200, Igor Gnatenko a écrit :
> > Hi,
> >
> > Imagine situation that somebody is working on KDE rebase and me on
> > libgit2 rebase. Both involve rebuilding/updating some package, let's
> > say kf5
Le samedi 08 juin 2019 à 11:23 +0200, Igor Gnatenko a écrit :
> Hi,
>
> Imagine situation that somebody is working on KDE rebase and me on
> libgit2 rebase. Both involve rebuilding/updating some package, let's
> say kf5-ktexteditor.
>
> We both work in different side tags, in KDE rebase kf5-ktext
Hi,
Imagine situation that somebody is working on KDE rebase and me on
libgit2 rebase. Both involve rebuilding/updating some package, let's
say kf5-ktexteditor.
We both work in different side tags, in KDE rebase kf5-ktexteditor
gets updated to a new version. In libgit2 rebase, old version gets
re
29 matches
Mail list logo
