03.06.2012 22:57, Tadej Janež wrote:
I post message there over week ago. I thought it was sufficient. Provenpackager rights off course do not excuse that or other mistakes. On the contrary it only take me possibility make such tasks without make troubles for others. If I must also write to each maintainer separately - I promise do it next time. Sorry.Pavel, On Tue, 2012-05-29 at 20:21 +0400, Pavel Alexeev wrote:It is main reason why I request provenpackager rights. In fedora 17 it was so painful because I several times asks build dependencies and then ask help to push updates too. I think in that turn now I can do all that myself, so it should be smoother. As there around 6 security issues, I think update upstream release is easiest, and furthermore robust way handle it.I've seen you didn't listen to Tomáš's or Kalev's advice on not bumping the ImageMagick's soname in a stable release. Furthermore, you didn't give any warning to the maintainers of the dependent packages (except for the message on this list). In my opinion, being a provenpackager is no excuse for not doing that. Please, use the packagename-owner@xxxxxxxxxxxxxxxxx addresses to send out emails to the appropriate package maintainers. I do not known unfortunately.For techne (one of the dependent packages which I maintain) you bumped the release from 0.2.3-2 to 0.2.3-3, which breaks upgrades to F-17 and rawhide. Is there a way to revert the change and make a 0.2.3-2.fc16.1 build? Furthermore I've submitted update to testing ta moment read that [1]. May be it possible just update in Fedora 17 too? Additionally have worth I try read carefully all docs about provenpackager and such updates and have not found how deal with such versions. I had look in my packages and few others and found it was updated many times in that way. In packages were was present subrelease after %{?dist} - I increase it. Should or must in next time I add it in any package even it does not have it?? I apologize for the inconvenience. Can I help something now? If you or other will insist I may unpush that update and try patch IM for all issues off course... But I really do not want doing it now. Best regards, Tadej Janež [1] https://admin.fedoraproject.org/updates/nip2-7.28.4-2.fc16,q-7.11-12.fc16,gdl-0.9.2-4.fc16,dx-4.4.4-21.fc16,dmapd-0.0.47-3.fc16,k3d-0.8.0.2-5.fc16,inkscape-0.48.1-10.fc16,zbar-0.10-9.fc16,xine-lib-1.1.20.1-2.fc16,xastir-2.0.0-4.fc16,techne-0.2.3-3.fc16,ruby-RMagick-2.13.1-6.fc16.4,rss-glx-0.9.1.p-10.fc16,psiconv-0.9.8-9.fc16,php-pecl-imagick-3.0.0-10.fc16,php-magickwand-1.0.9-2.fc16,pfstools-1.8.3-3.fc16,oxine-0.7.1-12.fc16,libdmtx-0.7.2-5.fc16,kxstitch-0.8.4.1-7.fc16,calibre-0.8.33-3.fc16,vips-7.28.2-2.fc16,imageinfo-0.05-14.fc16,drawtiming-0.7.1-5.fc16,converseen-0.4.9-2.fc16,autotrace-0.31.1-26.fc16.2,ale-0.9.0.3-6.fc16,ImageMagick-6.7.7.5-1.fc16 |
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
