duplicate f13 package announcements

[M A Young]

I don't know if this has already been raised but I notice on the 
package-announce(a)lists.fedoraproject.org list that several Fedora 13 
packages keep getting announced, for example, by checking the archives I 
see that fedora-release-13-0.6 has been announced 6 times in March and a 
further 7 times in February. I suspect there is a glitch in the package 
management system somewhere.

 	Michael Young

[Jon Ciesla]

M A Young wrote:
>  I don't know if this has already been raised but I notice on the
>
>  package-announce(a)lists.fedoraproject.org list that several Fedora 13 
>  packages keep getting announced, for example, by checking the archives I 
>  see that fedora-release-13-0.6 has been announced 6 times in March and a 
>  further 7 times in February. I suspect there is a glitch in the package 
>  management system somewhere.
>
>   	Michael Young
>     
It's happening for 3 F12 packages as well.  I mentioned it in a ticket 
for another issue:

https://fedorahosted.org/rel-eng/ticket/2328

-J

-- 
in your fear, seek only peace
in your fear, seek only love

-d. bowie

[Josh Boyer]

On Thu, Mar 04, 2010 at 08:54:28AM -0600, Jon Ciesla wrote:
> M A Young wrote:
> > I don't know if this has already been raised but I notice on the 
> > package-announce(a)lists.fedoraproject.org list that several Fedora 13 
> > packages keep getting announced, for example, by checking the archives I 
> > see that fedora-release-13-0.6 has been announced 6 times in March and a 
> > further 7 times in February. I suspect there is a glitch in the package 
> > management system somewhere.
> >
> >  	Michael Young
> >   
> It's happening for 3 F12 packages as well.  I mentioned it in a ticket 
> for another issue:
>
> https://fedorahosted.org/rel-eng/ticket/2328 
Bodhi bug.  Hopefully being fixed today.

josh

[shmuel siegel]

On 3/4/2010 5:04 PM, Josh Boyer wrote:
>  On Thu, Mar 04, 2010 at 08:54:28AM -0600, Jon Ciesla wrote:
>     
> > M A Young wrote:
> >      
> >> I don't know if this has already been raised but I notice on the
> >> package-announce(a)lists.fedoraproject.org list that several Fedora 13
> >> packages keep getting announced, for example, by checking the archives I
> >> see that fedora-release-13-0.6 has been announced 6 times in March and a
> >> further 7 times in February. I suspect there is a glitch in the package
> >> management system somewhere.
> >>
> >>   	Michael Young
> >>
> >>        
> > It's happening for 3 F12 packages as well.  I mentioned it in a ticket
> > for another issue:
> >
> > https://fedorahosted.org/rel-eng/ticket/2328
> >      
>  Bodhi bug.  Hopefully being fixed today.
>
>  josh
>      
https://bugzilla.redhat.com/show_bug.cgi?id=567878 has received 10 
notifications that anaconda-13.32-1.fc13 has been pushed to stable. The 
latest one significantly later than this message.  Either the bug isn't 
fixed or this is a different, albeit similar bug. Unless of course this 
is just a timing bug; the old bodhi produced the last build.

[Josh Boyer]

On Fri, Mar 05, 2010 at 10:12:51AM +0200, shmuel siegel wrote:
> On 3/4/2010 5:04 PM, Josh Boyer wrote:
> > On Thu, Mar 04, 2010 at 08:54:28AM -0600, Jon Ciesla wrote:
> >    
> >> M A Young wrote:
> >>      
> >>> I don't know if this has already been raised but I notice on the
> >>> package-announce(a)lists.fedoraproject.org list that several Fedora 13
> >>> packages keep getting announced, for example, by checking the archives I
> >>> see that fedora-release-13-0.6 has been announced 6 times in March and a
> >>> further 7 times in February. I suspect there is a glitch in the package
> >>> management system somewhere.
> >>>
> >>>   	Michael Young
> >>>
> >>>        
> >> It's happening for 3 F12 packages as well.  I mentioned it in a ticket
> >> for another issue:
> >>
> >> https://fedorahosted.org/rel-eng/ticket/2328
> >>      
> > Bodhi bug.  Hopefully being fixed today.
> >
> > josh
> >    
> https://bugzilla.redhat.com/show_bug.cgi?id=567878 has received 10 
> notifications that anaconda-13.32-1.fc13 has been pushed to stable. The 
> latest one significantly later than this message.  Either the bug isn't 
> fixed or this is a different, albeit similar bug. Unless of course this 
> is just a timing bug; the old bodhi produced the last build. 
The latest should be from the fixed bodhi.  It should be the last time these
updates get emails.  Bodhi had to clear the condition that was causing it to
do this.  If it happens again, then the bug isn't fixed.

josh