<div dir="ltr">Hi all, <br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 14, 2014 at 5:18 AM, Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com" target="_blank">awilliam@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>On Thu, 2014-02-13 at 09:26 +0530, Parag N(पराग़) wrote:<br>
> Hi,<br>
><br>
> From the yesterday's pkgs git commit logs I see 3-4 people built<br>
> few packages for libicu soname bump. I am not sure why a single person<br>
> can't carry such a few package rebuilds for libicu soname bump.<br>
><br>
> Whoever (people names) want to rebuild packages should announce on<br>
> devel list first. Looks like harfbuzz package is picked twice for<br>
> these rebuilds. Both rebuilds happened in within 30 minutes time<br>
> period.<br>
<br>
</div></div>It doesn't really cause any terrible pain for a double rebuild to<br>
happen. devel@ being flooded with "I'm about to rebuild X!" would<br>
certainly cause a lot more inconvenience.<br>
<span><font color="#888888"></font></span></blockquote><br></div><div class="gmail_quote"> Right there is no harm. One can only bump the release and carry a rebuild without any change in spec. What I thought is that generally people whose packages gets soname bump used to carry package rebuilds for its dependent packages also. Same has already happened with libicu soname bump in the past. This time it was not clear if libicu maintainer is going for these package rebuilds or not.<br>
</div><div class="gmail_quote"> Anyway I assume libicu maintainer want to only push libicu update and let the dependent package owners to rebuild their packages. I have just rebuilt fontmatrix now.<br><br></div><div class="gmail_quote">
Thanks,<br></div><div class="gmail_quote">Parag.<br><br></div></div></div>