On Thu, 15 Feb 2018 08:11:17 +0100
Vít Ondruch <vondruch(a)redhat.com> wrote:
Dne 15.2.2018 v 07:55 Remi Collet napsal(a):
> Le 15/02/2018 à 07:47, Igor Gnatenko a écrit :
>> On Wed, 2018-02-14 at 14:06 -0500, Rob Crittenden wrote:
>>> nicolas.mailhot(a)laposte.net wrote:
>>>> Hi,
>>>>
>>>> Thank you for cleaning up the cruft in the repository !
>>>>
>>>> Regards,
>>>>
>>> Agreed. I'm usually pretty anal about others touching packages I
>>> maintain without at least a heads-up but in this case it doesn't
>>> bother me. I guess particularly since he didn't spin up a build
>>> or poke the n-v-r so reverting it if I really hated it or it
>>> broke something would be trivially easy.
>>> As an aside, it might be nice though to be able to watch a
>>> package and get automated notifications when things change. I
>>> don't maintain that many packages though. I'd imagine that for
>>> some this could be rather onerous, but I had no idea these
>>> changed were applied until I went and looked.
>> It is possible with fedmsg which we use. You can set notifications
>> in special webservice[0] (although I find settings in it
>> counter-intuitive). Simplest one is to set up notifications on all
>> packages you maintain.
> Sadly, commit notifications does NOT work for months
> (works for old packages, not for newly imported one)
It does not work at all. I did not get any notification about mass
rebuild changes what so ever. No build notifications, no commit
notifications, anything ...
Same here. Whilst I don't mind this change, as it stands I'm getting no
notifications when the packages I maintain are changed by other people,
and that's supposed to be one of the safeguards against potential
errors by provenpackagers.
Paul.