Hi Tomek, I think in In 2014.0 it's ok probably because for that you only need to rebuild the "update" repository as the main one becomes static at release. Perhaps we should introduce a testing repo to Cooker and run it in a simialr way to how we run 2014 testing repo it would maybe allow us to avoid the difficulties that arise when for example perls falls over. Worth some thought. Best, Colin On Tuesday 24 Nov 2015 10:35:52 Tomasz Gajc wrote: > Anyone ? > > 2015-11-22 23:50 GMT+01:00 Tomasz Paweł Gajc <[email protected]>: > > > Hi, > > > > > > > > i've noticed that when package is published on cooker(2014.0 is fine), > > then whole repository is being recreated from scratch, and ofcourse this > > takes time. > > > > > > > > For example see here: > > > > https://abf.io/build_lists/2600783 > > > > > > > > abfworker::publish-worker-2600746.log.tar.gz > > <http://file-store.rosalinux.ru/api/v1/file_stores/0f34ec6943404d65faf4d143208d46bced9a207c> > > > > > > > > Log is 10MiB size and this happens everythime each package is published. > > Looks like rpmtools are broken. Would be nice if someone (Robert, Cris, > > ...) could take a look on the issue. Thanks. > > > > -- > > > > Cheers > > > > TPG > >
_______________________________________________ OM-Cooker mailing list [email protected] http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
