Hello, This ebuild is a minor modification to the stock one for kipi-plugins that includes the patch in kde bug#132659. Upstream is silent on when the fix will be in; several people including me can confirm that the patch fixes the problem with the flickr upload. I understand that the best place to fix this is in upstream, but it might be a good idea to fix the problem for the ebuilds that gentoo already provides. Reproducible: Always Steps to Reproduce: 1. Open digikam 2. Try to upload any photo to flickr 3.
Created attachment 119867 [details] New ebuild for 0.1.0_rc1
Created attachment 119869 [details, diff] patch This is the same patch uploaded by Bera here: http://bugs.kde.org/attachment.cgi?id=17772&action=view
As far as I can see this patch is already integrate into kipi-plugins-0.1.3-r1. I don't actually have a flickr account to verify that with, but why are you wanting to patch the old version? This won't bypass stable marking - usually the ebuild will be bumped and tested for 30 days before being marked stable. Would we be better off targeting 0.1.3 for stable? It has already been in the testing branch for long enough and seems to work well.
(In reply to comment #3) > As far as I can see this patch is already integrate into kipi-plugins-0.1.3-r1. > I don't actually have a flickr account to verify that with, but why are you > wanting to patch the old version? This won't bypass stable marking - usually > the ebuild will be bumped and tested for 30 days before being marked stable. > > Would we be better off targeting 0.1.3 for stable? It has already been in the > testing branch for long enough and seems to work well. Thanks. I usually don't emerge unstable packages unless they have some must-have features. I did not see that this was fixed in the latest version, the kde bug report was very quiet which lead me to assume that it was forgotten about. Thanks for checking, and I feel you are right, its better to bury this bug :)
We can't stabilise kipi-plugins-0.1.3-r1 at the moment because other packages it depends on are unstable and will stay unstable for some time yet. As we have a fix in the tree which works nicely and is functionally stable, I'm resolving this bug for now.
