[aur-general] away

[Rashif Ray Rahman]

On 2 August 2012 00:30, Ike Devolder <ike.devolder at gmail.com> wrote:
> Op woensdag 1 augustus 2012 12:15:43 schreef Stéphane Gaudreault:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Le 2012-08-01 12:04, Ike Devolder a écrit :
>> > Op woensdag 1 augustus 2012 18:03:20 schreef u:
>> >> Op woensdag 1 augustus 2012 11:49:58 schreef Dave Reisner:
>> >>> On Wed, Aug 01, 2012 at 05:47:17PM +0200, Ike Devolder wrote:
>> >>>> Op maandag 30 juli 2012 06:43:52 schreef Xyne:
>> >>>>> Ike Devolder wrote:
>> >>>>>> Hi,
>> >>>>>>
>> >>>>>> I'll be away for a couple of days, normally everything should get
>> >>>>>> updated
>> >>>>>> automatically while i'm out.
>> >>>>>
>> >>>>> How are you updating things automatically?
>> >>>>>
>> >>>>>
>> >>>>> Regards,
>> >>>>> Xyne
>> >>>>
>> >>>> cronjobs on a server :)
>> >>>> i have to add more but most are already to be found:
>> >>>> https://github.com/BlackIkeEagle/archbuild
>> >>>>
>> >>>> --Ike
>> >>>
>> >>> So you're blindly signing and pushing packages based on the fact that
>> >>> they compile?
>> >>
>> >> yes why not ?
>> >>
>> >> --Ike
>> >
>> > i could modify the script that they land in community-testing first
>> >
>> > --Ike
>>
>> Compiling != Working, so I think it is a good practice for a maintainer
>> to test packages before uploading them.
>>
>> In some case this could be difficult to do (eg massive rebuild for a
>> libname change) and in these cases it is ok to "blindly" push package on
>> the basis that is compile and test it later. In any case, I would expect
>> that a package is minimally tested before it goes to the repos.
>>
>> Stéphane
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.19 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQEcBAEBAgAGBQJQGVYvAAoJEOpoNuGrRBGWT7QIALr88yM242d4ub4eQQQgZYJk
>> Ub6M+6IYwzho8rkO6YwyoNDCREVBWCf30LBbCobBjeUy+s93BByhd9CG7UL9JBaa
>> UtRc1LCKMczzmJheoH/fAdxHy+my6Ye8NaAh+v8vuK0pd86nJLxkw1TsSCcwtjSi
>> +F4jLy/FrigkCClPFEY8CKDQY4pl6mbvP4NE559ufZHdLJQTlMMD0HLYCmedb2W4
>> OWbbMylmXGEmPL9Enx7nk67nh17HceAZVkIUKGwfx1SwWBdDynwZ4/eMISImpSX2
>> qoYOE5Th7c7I/zpXYRaDWzVzRR32rI4MZE8xsAjMV/kFR6UtQrhBp4vRsMWJIPM=
>> =nVW1
>> -----END PGP SIGNATURE-----
>
> Well then i'll drop the auto-updaters for community. but in general i find this
> very handy. i'll leave the scripts in the git repo for now but i'll drop the
> cronjob now.
>
> --Ike

Automating like this is very bad practice. I believe a maintainer's
job is to ensure that a package works before making it accessible to
everyone. Of course sometimes we're guilty of assuming stuff "should
probably just work" but let's not automate that attitude.

Otherwise it's OK if you push these to a testing repo me thinks. But
to do justice after you return you should check them one by one :P
Also you can do this on a case-by-case basis depending on how often
things are likely to break. Yet I think just auto building is fine but
not auto pushing.


--
GPG/PGP ID: C0711BF1