| 1 |
On Fri, 20 Nov 2015 15:26:43 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> Dnia 20 listopada 2015 11:19:35 CET, Alexis Ballier |
| 5 |
> <aballier@g.o> napisał(a): |
| 6 |
> >On Thu, 19 Nov 2015 23:21:52 +0100 |
| 7 |
> >Michał Górny <mgorny@g.o> wrote: |
| 8 |
> > |
| 9 |
> >> And here you removed the newest version having ~ia64 keyword, |
| 10 |
> >breaking |
| 11 |
> >> revdeps: |
| 12 |
> >> |
| 13 |
> >> https://qa-reports.gentoo.org/output/gentoo-ci/1061286/7.html#l885 |
| 14 |
> >> |
| 15 |
> >> I suggest you use eshowkw before removing packages. Please fix or |
| 16 |
> >> revert this. |
| 17 |
> > |
| 18 |
> >done; thx for the reminder |
| 19 |
> > |
| 20 |
> > |
| 21 |
> >feel free to revert such commits (at least mine) and send me an email |
| 22 |
> >so that i get notified something went wrong in the future |
| 23 |
> > |
| 24 |
> >PS: can't these checks/emails be automated ? it must be very boring |
| 25 |
> >to manually track the culprit from ci output |
| 26 |
> |
| 27 |
> Not one that I can think of. This usually requires looking at what |
| 28 |
> changed in both packages, and sometimes profiles. I don't want to |
| 29 |
> blame wrong people just because someone made an irrelevant commit in |
| 30 |
> a package. |
| 31 |
|
| 32 |
if CI runs after each commit, it should just be a matter of emailing |
| 33 |
the author when some new breakage appears |
Archives