FWIW, I love when people rebuild my packages. And no need to inform.
Maybe we could enhance the buildsystem to BCC the maintainer in case:
1. there is a maintainer
2. submitter isn't the maintainer
Though can understand you want to know up front, this at least ensures
there is some visibility.
Olav Vitters a écrit :
FWIW, I love when people rebuild my packages. And no need to inform.
Me too :)
Although it is a good courtesy to inform the maintainer.
Maybe we could enhance the buildsystem to BCC the maintainer in case:
1. there is a maintainer
2. submitter isn't the maintainer
I noticed that a very skilled, good packager built lilypond 2.15.23 that
failed when I tried to build it.
Thanks a lot.
However, I would have appreciated if I as maintainer would have been informed
about it and how it was done. This is currently under development upstreams
and feedback to them
2011/12/30 Thomas Spuhler tho...@btspuhler.com:
I noticed that a very skilled, good packager built lilypond 2.15.23 that
failed when I tried to build it.
Thanks a lot.
However, I would have appreciated if I as maintainer would have been informed
about it and how it was done. This is currently
On Friday, December 30, 2011 10:39:26 AM Jani Välimaa wrote:
2011/12/30 Thomas Spuhler tho...@btspuhler.com:
I noticed that a very skilled, good packager built lilypond 2.15.23 that
failed when I tried to build it.
Thanks a lot.
However, I would have appreciated if I as maintainer would
Le vendredi 30 décembre 2011 à 10:58 -0700, Thomas Spuhler a écrit :
It was me. Sorry about not informing you about it. All I change was
guile BR. Hope this will unveil some of my motives:
https://bugs.mageia.org/show_bug.cgi?id=3911.
Wally, strange, I didn't see the bug report. Shouldn't
2011/12/30 Thomas Spuhler tho...@btspuhler.com:
On Friday, December 30, 2011 10:39:26 AM Jani Välimaa wrote:
2011/12/30 Thomas Spuhler tho...@btspuhler.com:
I noticed that a very skilled, good packager built lilypond 2.15.23 that
failed when I tried to build it.
Thanks a lot.
However, I
