Can anyone explain this broken dependencies alert?

[Björn Persson]

Why am I getting this broken dependencies alert several times a day? I
built a new AWS in Rawhide two days ago, but the program that sends
these emails has apparently not noticed.

I'd understand if it complained about F25, as I think I missed the
alpha freeze deadline, but Rawhide isn't supposed to be frozen, is it?

Björn Persson

[Timotheus Pokorra]

Hello Björn,

>  Why am I getting this broken dependencies alert several times a day?
> I
>  built a new AWS in Rawhide two days ago, but the program that sends
>  these emails has apparently not noticed.
>
>  I'd understand if it complained about F25, as I think I missed the
>  alpha freeze deadline, but Rawhide isn't supposed to be frozen, is it? 
I have similar problems, and filed a ticket:
https://fedorahosted.org/rel-eng/ticket/6459
answer: "rawhide has failed to compose. it is being worked on"

Timotheus

[Björn Persson]

Timotheus Pokorra <timotheus.pokorra(a)solidcharity.com&gt; wrote:
>  > Why am I getting this broken dependencies alert several times a
> day? I
>  > built a new AWS in Rawhide two days ago, but the program that sends
>  > these emails has apparently not noticed.
>  >
>  > I'd understand if it complained about F25, as I think I missed the
>  > alpha freeze deadline, but Rawhide isn't supposed to be frozen, is it?  
>  
>  I have similar problems, and filed a ticket:
>  https://fedorahosted.org/rel-eng/ticket/6459
>  answer: "rawhide has failed to compose. it is being worked on" 
OK, thanks.

It would be nice if the program would understand that, and not complain
to the wrong people about the wrong problem.

Björn Persson

[Kevin Fenzi]

On Thu, 11 Aug 2016 19:07:56 +0200
Björn Persson <Bjorn(a)xn--rombobjrn-67a.se&gt; wrote:

>  Timotheus Pokorra <timotheus.pokorra(a)solidcharity.com&gt; wrote:
>  > > Why am I getting this broken dependencies alert several times a
>  > > day? I built a new AWS in Rawhide two days ago, but the program
>  > > that sends these emails has apparently not noticed.
>  > >
>  > > I'd understand if it complained about F25, as I think I missed the
>  > > alpha freeze deadline, but Rawhide isn't supposed to be frozen,
>  > > is it?    
>  > 
>  > I have similar problems, and filed a ticket:
>  > https://fedorahosted.org/rel-eng/ticket/6459
>  > answer: "rawhide has failed to compose. it is being worked on"  
>  
>  OK, thanks.
>  
>  It would be nice if the program would understand that, and not
>  complain to the wrong people about the wrong problem. 
The underlying issue here is that failed composes are still sending
broken dep emails. They shouldn't. They should just fail. 

Filed: https://pagure.io/pungi-fedora/issue/56

on it. 

kevin

[Björn Persson]

Kevin Fenzi wrote:
>  On Thu, 11 Aug 2016 19:07:56 +0200
>  Björn Persson <Bjorn(a)xn--rombobjrn-67a.se&gt; wrote:
>  
>  > Timotheus Pokorra <timotheus.pokorra(a)solidcharity.com&gt; wrote:  
>  > > > Why am I getting this broken dependencies alert several times a
>  > > > day? I built a new AWS in Rawhide two days ago, but the program
>  > > > that sends these emails has apparently not noticed.
>  > > >
>  > > > I'd understand if it complained about F25, as I think I missed
>  > > > the alpha freeze deadline, but Rawhide isn't supposed to be
>  > > > frozen, is it?      
>  > > 
>  > > I have similar problems, and filed a ticket:
>  > > https://fedorahosted.org/rel-eng/ticket/6459
>  > > answer: "rawhide has failed to compose. it is being worked on"    
>  > 
>  > OK, thanks.
>  > 
>  > It would be nice if the program would understand that, and not
>  > complain to the wrong people about the wrong problem.  
>  
>  The underlying issue here is that failed composes are still sending
>  broken dep emails. They shouldn't. They should just fail.  
There seems to be more to it than that. At
https://apps.fedoraproject.org/mdapi/rawhide/pkg/aws it now says
«"release": "1.fc26", "version": "2016"», and at
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everyth...
I find aws-2016-1.fc26, so as far as I can tell the new build is really
actually in Rawhide now. Yet I'm still getting these alerts about
aws-2015-5.fc24 having broken dependencies in the rawhide tree.

I assume that once a compose has succeeded the new build is in and the
old one is gone, so later composes shouldn't cause alerts about the old
build regardless of whether they succeed or fail, right? So there must
be some other reason why I'm still getting these emails.

Could it be that it's actually trying to complain about F25, even
though it says "in the rawhide tree"? Because if it's about F25 then I
understand that it's broken (and the fix is waiting to be pushed when
it thaws), but what am I supposed to think when it says clearly and
unambiguously "rawhide"?

Björn Persson