Things got updated: The tracker job https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/ has now a version number check + the recent pharo version allows the #update command line handler to detect if wrong update files were specified. Together with Stef's fix to always merge updates the update process should now be more stable.
On 2013-10-23, at 20:24, Sven Van Caekenberghe <[email protected]> wrote: > Everybody does a lot of work for Pharo, visible and invisible. > We are complementary and we need each other - so we have to work together. > > On 23 Oct 2013, at 18:53, Camillo Bruni <[email protected]> wrote: > >> On 2013-10-23, at 16:06, Camillo Bruni <[email protected]> wrote: >>> On 2013-10-23, at 13:48, Stéphane Ducasse <[email protected]> wrote: >>>> On Oct 23, 2013, at 10:52 AM, Camillo Bruni <[email protected]> wrote: >>>>> On 2013-10-22, at 10:44, Camillo Bruni <[email protected]> wrote: >>>>>>>> For retracting files you need access to files.pharo.org. >>>>>>> >>>>>>> This is what should be written in the readme. >>>>>> >>>>>> BTW have you tried that you actually have access to the machine? >>>>>> Because I remember that it didn't work for you nor Esteban... >>>>> >>>>> >>>>> So stef, did you check that you can actually edit the file? >>>> >>>> I cannot access it but I least I know that I should not look for it. >>>> And next time if there is a problem I just stop integrated and continue >>>> hacking on my cool stuff and look smart. >>> >>> Why can't you access it? >>> What do you want instead? >>> How do we avoid this situation in the future? (happened already before a >>> couple of times) >> >> Just to get something straight here: >> >> You have hardly something to complain... What you see is the tip of the >> iceberg. >> I spend roughly 1-2 hours per week maintaining all the jenkins instances >> with all >> the slaves and all the jobs that run (and there is Christoph to, regularly >> fixing >> and tweaking things all around). >> >> Now running around wild and screaming that everything does not work and is >> not >> documented is highly demotivating. Marcus and Esteban work on it on a daily >> basis. >> If maintaining jenkins were so much fun, you would do it, but you don't. >> >> >> So enjoy, and focus on the things you are truly great at: motivating people >> for a better pharo! > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
