On Thu, Oct 03, 2019 at 04:32:04PM -0600, Jerry James wrote:
> On Wed, Oct 2, 2019 at 11:45 AM Kevin Fenzi wrote:
> > So, this is my 'fault' I guess.
> >
> > There were some builds stuck in the signing tag in rawhide, so I
> > retagged them to get them signed and in. In this case it made an 'older
On Wed, Oct 2, 2019 at 11:45 AM Kevin Fenzi wrote:
> So, this is my 'fault' I guess.
>
> There were some builds stuck in the signing tag in rawhide, so I
> retagged them to get them signed and in. In this case it made an 'older'
> build show up. ;(
>
> I'll check f32 for older builds and fix them
On Wed, Oct 02, 2019 at 10:13:43AM -0600, Jerry James wrote:
> I just received the email below. I built ntl-11.3.4-1.fc32 on
> September 24. Later that day, upstream released version 11.4.0, so I
> built ntl-11.4.0-1.fc32 the next day, September 25. Why has the
> previous build suddenly come bac
I just received the email below. I built ntl-11.3.4-1.fc32 on
September 24. Later that day, upstream released version 11.4.0, so I
built ntl-11.4.0-1.fc32 the next day, September 25. Why has the
previous build suddenly come back from the dead? Having it go stable
now is going to break all of th
