Fedora 16 EOL Bugzilla Closure - strange behavior?

[Jaroslav Reznik]

----- Original Message -----
> Jaroslav Reznik wrote:
> > ----- Original Message -----
> > > I wouldn't be surprised if whatever script is used to do the mass
> > > closings
> > > does a first pass generating the list of bugs that need closing,
> > > and
> > > then does
> > > a second pass closing them unconditionally. If someone changes
> > > the
> > > bug info
> > > between those two passes the script wouldn't notice. And figuring
> > > that there
> > > were probably thousand of bugs closed, it could very well take
> > > the
> > > script
> > > hours to run.
> > 
> > Exactly. The script uses CSV generated from Bugzilla in one time
> > but
> > as the script runs nearly for a day, conflicts can happen...
> 
> I seem to recall that I've seen Bugzilla detect and warn about
> conflicting concurrent changes. It would seem like a good idea to
> have
> the script use that mechanism.

It's not BZ conflict (as you understand BZ conflict) but just 
time consequence. It would have to be a script that queries BZ bugs
matching criteria and acts for every single bug in time. I expect
definitely possible and I can take a look.

Jaroslav

> 
> Björn Persson
> 
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel