On Sat, 23 Jun 2012, John R. Dennison wrote: > On Sat, Jun 23, 2012 at 09:45:49PM -0400, Nico Kadel-Garcia wrote: >> >> A better question, perhaps, is "how can we best help" ? > > Not from my vantage point. It's been pretty clear that Dag will not > relinquish sole rights to kick off builds and push to the mirrors; at > least that has been his stance for a long time. And that's fine, it's > his repo after all. But it's not an ideal situation when things sit in > the pending queue for as long as they do.
Incorrect. I have stated many times that I would prefer a central buildsystem and that I am no longer a single point of failure. > The package in question, clam and it's subpackages, is arguably a > security update due to issues with the internal tar and chm components; > and while both can be considered to be corner-cases in the real world, > they are still cases nonetheless; the package should have been available > by this time. Out of fairness I will note that EPEL does not yet have > an update available either. The problem in this case is not the fact that I didn't want to update it. I have tried to build this the day it was released and two days later. The problem is that upstream changed the tarball (no longer shipping a database) and this has implications to our packages. If anyone care, the logfiles were pushed in both cases showing the problem with the build. The lack of time to dive into this and think about a solution is what is causing the delay, if it was a mere update the packages would have been online the same day as the release. The fact that upstream only started to discuss this after the recent release did not help a bit. It should have discussed before changing. -- -- dag wieers, [email protected], http://dag.wieers.com/ -- dagit linux solutions, [email protected], http://dagit.net/ [Any errors in spelling, tact or fact are transmission errors] _______________________________________________ users mailing list [email protected] http://lists.repoforge.org/mailman/listinfo/users
