Re: ImageMagick update
I have rebuild eom yesterday for rawhide. Untaging would force me another rebuild of eom. I hope the update won't push to stable branches. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update
Cool. What packages don't use the 7? This is from 2017, anything new since then? https://legacy.imagemagick.org/discourse-server/viewtopic.php?t=32622 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update
On Sat, 2021-10-16 at 06:39 +0900, Mamoru TASAKA wrote: > Michael Catanzaro wrote on 2021/10/16 0:37: > > On Fri, Oct 15 2021 at 10:22:36 AM +0200, Remi Collet < > > fed...@famillecollet.com> wrote: > > > Sorry, but such update, with soname change is not acceptable in > > > stable > > > branches. > > > > Hi Luya, > > > > Please note that soname changes are allowed in rawhide only after a > > one-week notice period. Since you did not give other maintainers > > notice, everything that depends on ImageMagick is now likely broken > > in rawhide > > > > Can we untag rawhide new ImageMagick, create side tag and move new > ImageMagick to side tag? > I Like the idea , is it possible ? > Regards, > Mamoru > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update
On 2021-10-15 08:37, Michael Catanzaro wrote: On Fri, Oct 15 2021 at 10:22:36 AM +0200, Remi Collet wrote: Sorry, but such update, with soname change is not acceptable in stable branches. Hi Luya, Please note that soname changes are allowed in rawhide only after a one-week notice period. Since you did not give other maintainers notice, everything that depends on ImageMagick is now likely broken in rawhide Ah ok. I'll be careful next time. -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update
Michael Catanzaro wrote on 2021/10/16 0:37: On Fri, Oct 15 2021 at 10:22:36 AM +0200, Remi Collet wrote: Sorry, but such update, with soname change is not acceptable in stable branches. Hi Luya, Please note that soname changes are allowed in rawhide only after a one-week notice period. Since you did not give other maintainers notice, everything that depends on ImageMagick is now likely broken in rawhide Can we untag rawhide new ImageMagick, create side tag and move new ImageMagick to side tag? Regards, Mamoru ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update
On Fri, Oct 15 2021 at 10:22:36 AM +0200, Remi Collet wrote: Sorry, but such update, with soname change is not acceptable in stable branches. Hi Luya, Please note that soname changes are allowed in rawhide only after a one-week notice period. Since you did not give other maintainers notice, everything that depends on ImageMagick is now likely broken in rawhide ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update
Le 15/10/2021 à 10:22, Remi Collet a écrit : This list is not complete, at least php-pecl-imagick is missing and this one is broken by recent changes... # dnf repoquery --whatrequires ImageMagick-libs ImageMagick R-magick WINGs-libs autotrace chafa converseen digikam-libs dmtx-utils dvdauthor eom gtatool-imagemagick inkscape libopenshot php-pecl-imagick psiconv pstoedit q-magick rss-glx rubygem-rmagick synfig synfigstudio vips xine-lib-extras ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update
Le 15/10/2021 à 10:05, Luya Tshimbalanga a écrit : Hello everyone, ImageMagick is now pushed to 6.9.12.25 as a long-overdue update [1] for all releases except EPEL8 branch, which I do not use (co-maintainer welcome). Affected packages below may need to rebuild: Sorry, but such update, with soname change is not acceptable in stable branches. If really wanted, you have to create a grouped update for all packages NsCDE a2ps anyremote c-graph caja-image-converter chordpro-abc conky-manager darktable-tools-noise devedeng dvd-slideshow epix fbida ffmulticonverter freewrl geeqie gscan2pdf gyazo jumpnbump-menu latex2rtf libpst lives lyx mediawiki mtpaint nautilus-image-converter nemo-image-converter perl-Graphics-TIFF-tests perl-PDF-API2-tests perl-PDF-Builder-tests perl-Panotools-Script playonlinux rubygem-mini_magick rubygem-rmagick shutter texlive-graphicxpsd variety vfrnav-utils w3m-img wdune This list is not complete, at least php-pecl-imagick is missing and this one is broken by recent changes... Remi ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
17.03.2015 02:57, Kevin Fenzi wrote: On Mon, 16 Mar 2015 21:02:25 +0300 Pavel Alexeev fo...@hubbitus.com.ru wrote: The main question should it be done in such manner? May be it have worth run at least off-tree (without commits and versions bump) mass rebuild? It allow estimate amount of broken packages and see dependencies. Do we have resources to do so? I was hoping to run a rebuild in copr on our new cloud (which would help this and also help make sure the new cloud is running ok). We will see how long such a rebuild will take and if it's not too long run it. Thank you Kevin. I hope it will be announced shortly. kevin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Mon, 16 Mar 2015 21:02:25 +0300 Pavel Alexeev fo...@hubbitus.com.ru wrote: The main question should it be done in such manner? May be it have worth run at least off-tree (without commits and versions bump) mass rebuild? It allow estimate amount of broken packages and see dependencies. Do we have resources to do so? I was hoping to run a rebuild in copr on our new cloud (which would help this and also help make sure the new cloud is running ok). We will see how long such a rebuild will take and if it's not too long run it. kevin pgpOk3Cd61HbJ.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
15.03.2015 16:57, Michael Schwendt пишет: On Tue, 10 Mar 2015 14:49:28 +0100, Ralf Corsepius wrote: Right now, many issues/problems are interacting and affecting packages simultanously, which occasionally render fixing these issues quite complicated. So far I've hit: - GCC-5.0 - Hardening - boost upgrade - ImageMagick - autotool upgrade. Openly said, the situation on f23 is a mess. Agreed. People run into failed builds, find out that a lib needs a rebuild because of GCC C++ ABI issues. After the rebuild, runtime linking fails for other dependencies, and they need a rebuild, too. This is non-trivial (and dangerous) for larger dep-chains in the distribution. I'm also not sure how many packagers even run Rawhide instead of F22 testing. The main question should it be done in such manner? May be it have worth run at least off-tree (without commits and versions bump) mass rebuild? It allow estimate amount of broken packages and see dependencies. Do we have resources to do so? -- With best wishes, Pavel Alexeev (aka Pahan-Hubbitus). For fast contact with me use jabber: hubbi...@jabber.ru -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Tue, 10 Mar 2015 14:49:28 +0100, Ralf Corsepius wrote: Right now, many issues/problems are interacting and affecting packages simultanously, which occasionally render fixing these issues quite complicated. So far I've hit: - GCC-5.0 - Hardening - boost upgrade - ImageMagick - autotool upgrade. Openly said, the situation on f23 is a mess. Agreed. People run into failed builds, find out that a lib needs a rebuild because of GCC C++ ABI issues. After the rebuild, runtime linking fails for other dependencies, and they need a rebuild, too. This is non-trivial (and dangerous) for larger dep-chains in the distribution. I'm also not sure how many packagers even run Rawhide instead of F22 testing. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Monday, 09 March 2015 at 16:06, Pavel Alexeev wrote: 06.03.2015 19:34, Kevin Fenzi пишет: On Fri, 6 Mar 2015 11:31:45 -0500 Rich Mattes richmat...@gmail.com wrote: There's no planned f22 rebuild for gcc5, as f22 defaults to -D_GLIBCXX_USE_CXX11_ABI=0. These issues are cropping up in f23. There should probably be a mass rebuild for f23, and sooner rather than later as rawhide is currently a big game of whack-a-mole when building c++ packages. As soon as gcc folks say things are settled down enough to do one, we can look at scheduling one. ;) It would be a shame to do it too soon though and have a bug requiring another one. I've been rebuilding things as I run into them being broken. (The other day it was the gobby stack: net6, libxml++, obby, gobby). Is it ok to rebuild all dependencies f.e. for fix build issue with pfstools introduced by that update? Or just fill bugzilla issues for owners? If a simple rebuild works, I'd say go ahead and do it. If it's more complicated, file a bug and attach any necessary patches (and ask the POC if you can act on it yourself). That's what I usually do. Regards, -- Fedora http://fedoraproject.org/wiki/User:Rathann RPMFusion http://rpmfusion.org Faith manages. -- Delenn to Lennier in Babylon 5:Confessions and Lamentations -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On 03/10/2015 01:30 PM, Dominik 'Rathann' Mierzejewski wrote: On Monday, 09 March 2015 at 16:06, Pavel Alexeev wrote: 06.03.2015 19:34, Kevin Fenzi пишет: On Fri, 6 Mar 2015 11:31:45 -0500 Rich Mattes richmat...@gmail.com wrote: There's no planned f22 rebuild for gcc5, as f22 defaults to -D_GLIBCXX_USE_CXX11_ABI=0. These issues are cropping up in f23. There should probably be a mass rebuild for f23, and sooner rather than later as rawhide is currently a big game of whack-a-mole when building c++ packages. As soon as gcc folks say things are settled down enough to do one, we can look at scheduling one. ;) It would be a shame to do it too soon though and have a bug requiring another one. I've been rebuilding things as I run into them being broken. (The other day it was the gobby stack: net6, libxml++, obby, gobby). Is it ok to rebuild all dependencies f.e. for fix build issue with pfstools introduced by that update? Or just fill bugzilla issues for owners? If a simple rebuild works, I'd say go ahead and do it. It only partially does. If it's more complicated, Right now, many issues/problems are interacting and affecting packages simultanously, which occasionally render fixing these issues quite complicated. So far I've hit: - GCC-5.0 - Hardening - boost upgrade - ImageMagick - autotool upgrade. Openly said, the situation on f23 is a mess. Ralf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
06.03.2015 19:34, Kevin Fenzi пишет: On Fri, 6 Mar 2015 11:31:45 -0500 Rich Mattes richmat...@gmail.com wrote: There's no planned f22 rebuild for gcc5, as f22 defaults to -D_GLIBCXX_USE_CXX11_ABI=0. These issues are cropping up in f23. There should probably be a mass rebuild for f23, and sooner rather than later as rawhide is currently a big game of whack-a-mole when building c++ packages. As soon as gcc folks say things are settled down enough to do one, we can look at scheduling one. ;) It would be a shame to do it too soon though and have a bug requiring another one. I've been rebuilding things as I run into them being broken. (The other day it was the gobby stack: net6, libxml++, obby, gobby). Is it ok to rebuild all dependencies f.e. for fix build issue with pfstools introduced by that update? Or just fill bugzilla issues for owners? kevin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Fri, 6 Mar 2015 14:11:03 +0100 Michael Schwendt mschwe...@gmail.com wrote: On Fri, 06 Mar 2015 12:49:12 +0300, Pavel Alexeev wrote: Hello. ImageMagick itself built in rawhide. just go ahead an rebuild pfstools, please. I'll intervene only in the case something goes wrong. First attempt fails [1] with: pfsinimgmagick.opfsoutimgmagick.o: : InIn functionfunction ``writeFrames(readFramesint(,int ,char* *char)**)': /builddir/'build:/ BUILD/builddir/build/BUILD//pfstools-1.8.5/src/fileformatpfstools/-pfsinimgmagick.cpp1.8.5/:src112/:fileformat/ pfsoutimgmagick.cppundefined: 194:reference undefined toreference `to Magick`:Magick:::ImageImageImage(Imageunsigned( intstd,: :unsigned __cxx11int:,: stdbasic_string::__cxx11char:,: basic_stringstdchar:, :std:char_traits:char_traitscharchar, , stdstdallocatorallocatorcharchar const ,const MagickCore):': StorageType, void const*)' /builddir/build/BUILD/pfstools-1.8.5/src/fileformat/pfsoutimgmagick.cpp:198: undefined reference to `Magick::Image::write(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' collect2: error: ld returned 1 exit status But I think it is not ImageMagick issue, but GCC5 instead[2]. I had try add -D_GLIBCXX_USE_CXX11_ABI=0, and error gone, but now it is: /usr/include/OpenEXR/ImfAttribute.h:295: undefined reference to `Imf_2_2::TypedAttributestd::string::staticTypeName()' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x30): undefined reference to `Imf_2_2::TypedAttributestd::string::writeValueTo(Imf_2_2::OStream, int) const' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x38): undefined reference to `Imf_2_2::TypedAttributestd::string::readValueFrom(Imf_2_2::IStream, int, int)' Right now unsure how to handle it. But I continue digging. [1] https://kojipkgs.fedoraproject.org//work/tasks/6035/9146035/build.log [2] http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/ It wasn't build with your upgrade, but an older one: https://kojipkgs.fedoraproject.org//work/tasks/6035/9146035/root.log DEBUG util.py:388: ImageMagick i686 6.8.8.10-7.fc22 build 159 k DEBUG util.py:388: ImageMagick-c++ i686 6.8.8.10-7.fc22 build 167 k DEBUG util.py:388: ImageMagick-libsi686 6.8.8.10-7.fc22 build 2.0 M You may need to look into using koji wait-repo … to give koji some time to recreate the buildroot repo metadata after including a new build. It may take roughly up to 20 minutes for a build to be included. Meanwhile, the buildroot should be up-to-date, so give it another try. Thanks. You were faster... I'm also afraid the example above shows building only the ImageMagick direct dependencies might not be sufficient. Seems that right now there are some packages that have been rebuilt with gcc-5 and some not yet. This may lead to more linker failures when one binary wants to link with several libraries with incompatible ABIs... Regards, -- Tomáš Smetana Platform Engineering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Fri, 06 Mar 2015 12:49:12 +0300, Pavel Alexeev wrote: Hello. ImageMagick itself built in rawhide. just go ahead an rebuild pfstools, please. I'll intervene only in the case something goes wrong. First attempt fails [1] with: pfsinimgmagick.opfsoutimgmagick.o: : InIn functionfunction ``writeFrames(readFramesint(,int ,char* *char)**)': /builddir/'build:/ BUILD/builddir/build/BUILD//pfstools-1.8.5/src/fileformatpfstools/-pfsinimgmagick.cpp1.8.5/:src112/:fileformat/ pfsoutimgmagick.cppundefined: 194:reference undefined toreference `to Magick`:Magick:::ImageImageImage(Imageunsigned( intstd,: :unsigned __cxx11int:,: stdbasic_string::__cxx11char:,: basic_stringstdchar:, :std:char_traits:char_traitscharchar, , stdstdallocatorallocatorcharchar const ,const MagickCore):': StorageType, void const*)' /builddir/build/BUILD/pfstools-1.8.5/src/fileformat/pfsoutimgmagick.cpp:198: undefined reference to `Magick::Image::write(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' collect2: error: ld returned 1 exit status But I think it is not ImageMagick issue, but GCC5 instead[2]. I had try add -D_GLIBCXX_USE_CXX11_ABI=0, and error gone, but now it is: /usr/include/OpenEXR/ImfAttribute.h:295: undefined reference to `Imf_2_2::TypedAttributestd::string::staticTypeName()' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x30): undefined reference to `Imf_2_2::TypedAttributestd::string::writeValueTo(Imf_2_2::OStream, int) const' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x38): undefined reference to `Imf_2_2::TypedAttributestd::string::readValueFrom(Imf_2_2::IStream, int, int)' Right now unsure how to handle it. But I continue digging. [1] https://kojipkgs.fedoraproject.org//work/tasks/6035/9146035/build.log [2] http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/ It wasn't build with your upgrade, but an older one: https://kojipkgs.fedoraproject.org//work/tasks/6035/9146035/root.log DEBUG util.py:388: ImageMagick i686 6.8.8.10-7.fc22 build 159 k DEBUG util.py:388: ImageMagick-c++ i686 6.8.8.10-7.fc22 build 167 k DEBUG util.py:388: ImageMagick-libsi686 6.8.8.10-7.fc22 build 2.0 M You may need to look into using koji wait-repo … to give koji some time to recreate the buildroot repo metadata after including a new build. It may take roughly up to 20 minutes for a build to be included. Meanwhile, the buildroot should be up-to-date, so give it another try. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
Hello. 06.03.2015 16:51, Tomáš Smetana wrote: On Fri, 6 Mar 2015 14:11:03 +0100 Michael Schwendt mschwe...@gmail.com wrote: On Fri, 06 Mar 2015 12:49:12 +0300, Pavel Alexeev wrote: Hello. ImageMagick itself built in rawhide. just go ahead an rebuild pfstools, please. I'll intervene only in the case something goes wrong. First attempt fails [1] with: pfsinimgmagick.opfsoutimgmagick.o: : InIn functionfunction ``writeFrames(readFramesint(,int ,char* *char)**)': /builddir/'build:/ BUILD/builddir/build/BUILD//pfstools-1.8.5/src/fileformatpfstools/-pfsinimgmagick.cpp1.8.5/:src112/:fileformat/ pfsoutimgmagick.cppundefined: 194:reference undefined toreference `to Magick`:Magick:::ImageImageImage(Imageunsigned( intstd,: :unsigned __cxx11int:,: stdbasic_string::__cxx11char:,: basic_stringstdchar:, :std:char_traits:char_traitscharchar, , stdstdallocatorallocatorcharchar const ,const MagickCore):': StorageType, void const*)' /builddir/build/BUILD/pfstools-1.8.5/src/fileformat/pfsoutimgmagick.cpp:198: undefined reference to `Magick::Image::write(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' collect2: error: ld returned 1 exit status But I think it is not ImageMagick issue, but GCC5 instead[2]. I had try add -D_GLIBCXX_USE_CXX11_ABI=0, and error gone, but now it is: /usr/include/OpenEXR/ImfAttribute.h:295: undefined reference to `Imf_2_2::TypedAttributestd::string::staticTypeName()' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x30): undefined reference to `Imf_2_2::TypedAttributestd::string::writeValueTo(Imf_2_2::OStream, int) const' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x38): undefined reference to `Imf_2_2::TypedAttributestd::string::readValueFrom(Imf_2_2::IStream, int, int)' Right now unsure how to handle it. But I continue digging. [1] https://kojipkgs.fedoraproject.org//work/tasks/6035/9146035/build.log [2] http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/ It wasn't build with your upgrade, but an older one: https://kojipkgs.fedoraproject.org//work/tasks/6035/9146035/root.log DEBUG util.py:388: ImageMagick i686 6.8.8.10-7.fc22 build 159 k DEBUG util.py:388: ImageMagick-c++ i686 6.8.8.10-7.fc22 build 167 k DEBUG util.py:388: ImageMagick-libsi686 6.8.8.10-7.fc22 build 2.0 M You may need to look into using koji wait-repo … to give koji some time to recreate the buildroot repo metadata after including a new build. It may take roughly up to 20 minutes for a build to be included. Meanwhile, the buildroot should be up-to-date, so give it another try. Thanks. Thanks. You were faster... I'm also afraid the example above shows building only the ImageMagick direct dependencies might not be sufficient. Seems that right now there are some packages that have been rebuilt with gcc-5 and some not yet. This may lead to more linker failures when one binary wants to link with several libraries with incompatible ABIs... And how we should deal with it? According to https://fedoraproject.org/wiki/Changes/GCC5 there no planned mass-rebuild for GCC5. I could try rebuild dependencies, but should I use -D_GLIBCXX_USE_CXX11_ABI=0? Do we have some policy about it? Regards, -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Fri, 6 Mar 2015 11:31:45 -0500 Rich Mattes richmat...@gmail.com wrote: There's no planned f22 rebuild for gcc5, as f22 defaults to -D_GLIBCXX_USE_CXX11_ABI=0. These issues are cropping up in f23. There should probably be a mass rebuild for f23, and sooner rather than later as rawhide is currently a big game of whack-a-mole when building c++ packages. As soon as gcc folks say things are settled down enough to do one, we can look at scheduling one. ;) It would be a shame to do it too soon though and have a bug requiring another one. I've been rebuilding things as I run into them being broken. (The other day it was the gobby stack: net6, libxml++, obby, gobby). kevin pgp3Qnz9Gr_A0.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Fri, Mar 6, 2015 at 11:04 AM, Pavel Alexeev fo...@hubbitus.com.ru wrote: According to https://fedoraproject.org/wiki/Changes/GCC5 there no planned mass-rebuild for GCC5. There's no planned f22 rebuild for gcc5, as f22 defaults to -D_GLIBCXX_USE_CXX11_ABI=0. These issues are cropping up in f23. There should probably be a mass rebuild for f23, and sooner rather than later as rawhide is currently a big game of whack-a-mole when building c++ packages. Rich -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
Hello. ImageMagick itself built in rawhide. 05.03.2015 15:52, Tomáš Smetana wrote: On Thu, 05 Mar 2015 02:09:00 +0300 Pavel Alexeev fo...@hubbitus.com.ru wrote: Hello. I have long outstanding update of ImageMagick[1] and plan do it in rawhide in 1-3 days. ... Affected packages needs to be rebuild: ... pfstools Package owners in cc. Please let me known if you wish me to rebuild your package. Hi, just go ahead an rebuild pfstools, please. I'll intervene only in the case something goes wrong. First attempt fails [1] with: pfsinimgmagick.opfsoutimgmagick.o: : InIn functionfunction ``writeFrames(readFramesint(,int ,char* *char)**)': /builddir/'build:/ BUILD/builddir/build/BUILD//pfstools-1.8.5/src/fileformatpfstools/-pfsinimgmagick.cpp1.8.5/:src112/:fileformat/ pfsoutimgmagick.cppundefined: 194:reference undefined toreference `to Magick`:Magick:::ImageImageImage(Imageunsigned( intstd,: :unsigned __cxx11int:,: stdbasic_string::__cxx11char:,: basic_stringstdchar:, :std:char_traits:char_traitscharchar, , stdstdallocatorallocatorcharchar const ,const MagickCore):': StorageType, void const*)' /builddir/build/BUILD/pfstools-1.8.5/src/fileformat/pfsoutimgmagick.cpp:198: undefined reference to `Magick::Image::write(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' collect2: error: ld returned 1 exit status But I think it is not ImageMagick issue, but GCC5 instead[2]. I had try add -D_GLIBCXX_USE_CXX11_ABI=0, and error gone, but now it is: /usr/include/OpenEXR/ImfAttribute.h:295: undefined reference to `Imf_2_2::TypedAttributestd::string::staticTypeName()' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x30): undefined reference to `Imf_2_2::TypedAttributestd::string::writeValueTo(Imf_2_2::OStream, int) const' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x38): undefined reference to `Imf_2_2::TypedAttributestd::string::readValueFrom(Imf_2_2::IStream, int, int)' Right now unsure how to handle it. But I continue digging. [1] https://kojipkgs.fedoraproject.org//work/tasks/6035/9146035/build.log [2] http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/ Thanks and regards, -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 - libMagick++-6.Q16.so.6
On Fri, 06 Mar 2015 12:49:12 +0300 Pavel Alexeev fo...@hubbitus.com.ru wrote: Hello. ImageMagick itself built in rawhide. pfsinimgmagick.opfsoutimgmagick.o: : InIn functionfunction ``writeFrames(readFramesint(,int ,char* *char)**)': /builddir/'build:/ BUILD/builddir/build/BUILD//pfstools-1.8.5/src/fileformatpfstools/-pfsinimgmagick.cpp1.8.5/:src112/:fileformat/ pfsoutimgmagick.cppundefined: 194:reference undefined toreference `to Magick`:Magick:::ImageImageImage(Imageunsigned( intstd,: :unsigned __cxx11int:,: stdbasic_string::__cxx11char:,: basic_stringstdchar:, :std:char_traits:char_traitscharchar, , stdstdallocatorallocatorcharchar const ,const MagickCore):': StorageType, void const*)' /builddir/build/BUILD/pfstools-1.8.5/src/fileformat/pfsoutimgmagick.cpp:198: undefined reference to `Magick::Image::write(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' collect2: error: ld returned 1 exit status ... But I think it is not ImageMagick issue, but GCC5 instead[2]. I had try add -D_GLIBCXX_USE_CXX11_ABI=0, and error gone, but now it is: /usr/include/OpenEXR/ImfAttribute.h:295: undefined reference to `Imf_2_2::TypedAttributestd::string::staticTypeName()' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x30): undefined reference to `Imf_2_2::TypedAttributestd::string::writeValueTo(Imf_2_2::OStream, int) const' pfsoutexr.o:(.data.rel.ro._ZTVN7Imf_2_214TypedAttributeISsEE[_ZTVN7Imf_2_214TypedAttributeISsEE]+0x38): undefined reference to `Imf_2_2::TypedAttributestd::string::readValueFrom(Imf_2_2::IStream, int, int)' Right now unsure how to handle it. But I continue digging. Hi, thanks for the effort... I'll see if I could do something about this. Regards, -- Tomáš Smetana Platform Engineering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
17.03.2013 05:39, Rex Dieter wrote: Orion Poplawski wrote: On 03/16/2013 07:38 AM, Rex Dieter wrote: Orion Poplawski wrote: On 03/14/2013 09:34 AM, Orion Poplawski wrote: Okay, looks like upstream cmake has a patch, I'll get it into rawhide ASAP. Scratch that, it was a hack for Arch Linux's hacked version of ImageMagick sonames that doesn't work for Fedora. Will need to work on a fix... I've a little experience adding pkg-config hints to cmake, I'll help look into it. As noted in http://public.kitware.com/Bug/view.php?id=14012 an issue with pkg-config in cmake is that it isn't always present on all of the platforms that cmake supports. But it is still probably the way to go on Linux. OK, first-draft patch sent upstream and applied to cmake-2.8.11-0.3.rc1.fc20 As far as I could tell, only one package in fedora is affected, converseen, and confirmed it builds ok now. Thank you very much! Then I push ImageMagick into rawhide. Could you please provide upstream bug url for that to monitor status? -- rex -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Pavel Alexeev wrote: 17.03.2013 05:39, Rex Dieter wrote: As noted in http://public.kitware.com/Bug/view.php?id=14012 an issue with pkg-config in cmake is that it isn't always present on all of the platforms that cmake supports. But it is still probably the way to go on Linux. OK, first-draft patch sent upstream and applied to cmake-2.8.11-0.3.rc1.fc20 As far as I could tell, only one package in fedora is affected, converseen, and confirmed it builds ok now. Thank you very much! Then I push ImageMagick into rawhide. Could you please provide upstream bug url for that to monitor status? The one orion gave earlier in the thread, http://public.kitware.com/Bug/view.php?id=14012 -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
17.03.2013 16:40, Rex Dieter пишет: Pavel Alexeev wrote: 17.03.2013 05:39, Rex Dieter wrote: As noted in http://public.kitware.com/Bug/view.php?id=14012 an issue with pkg-config in cmake is that it isn't always present on all of the platforms that cmake supports. But it is still probably the way to go on Linux. OK, first-draft patch sent upstream and applied to cmake-2.8.11-0.3.rc1.fc20 As far as I could tell, only one package in fedora is affected, converseen, and confirmed it builds ok now. Thank you very much! Then I push ImageMagick into rawhide. Could you please provide upstream bug url for that to monitor status? The one orion gave earlier in the thread, http://public.kitware.com/Bug/view.php?id=14012 Sorry. Thank you. Meantime ImageMagick landed in rawhide - http://koji.fedoraproject.org/koji/taskinfo?taskID=5132168 -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
13.03.2013 20:24, Remi Collet wrote: Le 13/03/2013 17:16, Remi Collet a écrit : php-pecl-imagick As you're the owner of this one, if you prefer to update it, see http://svn.php.net/viewvc?view=revisionrevision=329769 Patch incorporated, thanks again. http://koji.fedoraproject.org/koji/taskinfo?taskID=5134433 Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
14.03.2013 12:17, Remi Collet wrote: Le 13/03/2013 17:16, Remi Collet a écrit : php-magickwand Upstream 1.0.9-2 (yes with a -) includes the fix (and the php54 patch) Thanks. It built too - http://koji.fedoraproject.org/koji/taskinfo?taskID=5134893 Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Orion Poplawski wrote: On 03/14/2013 09:34 AM, Orion Poplawski wrote: Okay, looks like upstream cmake has a patch, I'll get it into rawhide ASAP. Scratch that, it was a hack for Arch Linux's hacked version of ImageMagick sonames that doesn't work for Fedora. Will need to work on a fix... I've a little experience adding pkg-config hints to cmake, I'll help look into it. -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 03/16/2013 07:38 AM, Rex Dieter wrote: Orion Poplawski wrote: On 03/14/2013 09:34 AM, Orion Poplawski wrote: Okay, looks like upstream cmake has a patch, I'll get it into rawhide ASAP. Scratch that, it was a hack for Arch Linux's hacked version of ImageMagick sonames that doesn't work for Fedora. Will need to work on a fix... I've a little experience adding pkg-config hints to cmake, I'll help look into it. As noted in http://public.kitware.com/Bug/view.php?id=14012 an issue with pkg-config in cmake is that it isn't always present on all of the platforms that cmake supports. But it is still probably the way to go on Linux. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Orion Poplawski wrote: On 03/16/2013 07:38 AM, Rex Dieter wrote: Orion Poplawski wrote: On 03/14/2013 09:34 AM, Orion Poplawski wrote: Okay, looks like upstream cmake has a patch, I'll get it into rawhide ASAP. Scratch that, it was a hack for Arch Linux's hacked version of ImageMagick sonames that doesn't work for Fedora. Will need to work on a fix... I've a little experience adding pkg-config hints to cmake, I'll help look into it. As noted in http://public.kitware.com/Bug/view.php?id=14012 an issue with pkg-config in cmake is that it isn't always present on all of the platforms that cmake supports. But it is still probably the way to go on Linux. OK, first-draft patch sent upstream and applied to cmake-2.8.11-0.3.rc1.fc20 As far as I could tell, only one package in fedora is affected, converseen, and confirmed it builds ok now. -- rex -- rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
13.03.2013 20:24, Remi Collet wrote: Le 13/03/2013 17:16, Remi Collet a écrit : php-pecl-imagick As you're the owner of this one, if you prefer to update it, see http://svn.php.net/viewvc?view=revisionrevision=329769 Thanks for pointing. Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
14.03.2013 20:04, Orion Poplawski пишет: On 03/14/2013 09:34 AM, Orion Poplawski wrote: Okay, looks like upstream cmake has a patch, I'll get it into rawhide ASAP. Scratch that, it was a hack for Arch Linux's hacked version of ImageMagick sonames that doesn't work for Fedora. Will need to work on a fix... Could you do that? I think then I should wait until that happened before IM landed to rawhide, is not? -- With best wishes, Pavel Alexeev (aka Pahan-Hubbitus). For fast contact with me use jabber: hubbi...@jabber.ru -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Le 13/03/2013 17:16, Remi Collet a écrit : php-magickwand Upstream 1.0.9-2 (yes with a -) includes the fix (and the php54 patch) Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Le 13/03/2013 23:49, Orion Poplawski a écrit : In any case, this is going to be pretty disruptive. I think we need to do some hard thinking about whether we want to go with this naming scheme or not. If we do, I think we need to do IM development in a side tag to work out all the kinks. If consumer correctly use pkg-config information, there should not have any problem... Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 14/03/13 01:18 AM, Remi Collet wrote: Le 13/03/2013 23:49, Orion Poplawski a écrit : In any case, this is going to be pretty disruptive. I think we need to do some hard thinking about whether we want to go with this naming scheme or not. If we do, I think we need to do IM development in a side tag to work out all the kinks. If consumer correctly use pkg-config information, there should not have any problem... Would that be the pkgconfig file whose name changed as part of this change? :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Le 14/03/2013 10:30, Adam Williamson a écrit :
On 14/03/13 01:18 AM, Remi Collet wrote:
Le 13/03/2013 23:49, Orion Poplawski a écrit :
In any case, this is going to be pretty disruptive. I think we need to
do some hard thinking about whether we want to go with this naming
scheme or not. If we do, I think we need to do IM development in a side
tag to work out all the kinks.
If consumer correctly use pkg-config information, there should not have
any problem...
Would that be the pkgconfig file whose name changed as part of this
change? :)
No, as both names are provided.
%{_libdir}/pkgconfig/MagickCore.pc
++%{_libdir}/pkgconfig/MagickCore-6.Q16.pc
%{_libdir}/pkgconfig/ImageMagick.pc
++%{_libdir}/pkgconfig/ImageMagick-6.Q16.pc
%{_libdir}/pkgconfig/MagickWand.pc
++%{_libdir}/pkgconfig/MagickWand-6.Q16.pc
And the foo-config commands are unchanged.
%{_bindir}/Magick-config
%{_bindir}/MagickWand-config
%{_bindir}/Wand-config
$ pkg-config MagickWand --cflags --libs
-fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16
-I/usr/include/ImageMagick-6 -lMagickWand-6.Q16 -lm
-lMagickCore-6.Q16
Remi.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 14/03/13 02:49 AM, Remi Collet wrote:
Le 14/03/2013 10:30, Adam Williamson a écrit :
On 14/03/13 01:18 AM, Remi Collet wrote:
Le 13/03/2013 23:49, Orion Poplawski a écrit :
In any case, this is going to be pretty disruptive. I think we need to
do some hard thinking about whether we want to go with this naming
scheme or not. If we do, I think we need to do IM development in a side
tag to work out all the kinks.
If consumer correctly use pkg-config information, there should not have
any problem...
Would that be the pkgconfig file whose name changed as part of this
change? :)
No, as both names are provided.
%{_libdir}/pkgconfig/MagickCore.pc
++%{_libdir}/pkgconfig/MagickCore-6.Q16.pc
%{_libdir}/pkgconfig/ImageMagick.pc
++%{_libdir}/pkgconfig/ImageMagick-6.Q16.pc
%{_libdir}/pkgconfig/MagickWand.pc
++%{_libdir}/pkgconfig/MagickWand-6.Q16.pc
And the foo-config commands are unchanged.
%{_bindir}/Magick-config
%{_bindir}/MagickWand-config
%{_bindir}/Wand-config
$ pkg-config MagickWand --cflags --libs
-fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16
-I/usr/include/ImageMagick-6 -lMagickWand-6.Q16 -lm
-lMagickCore-6.Q16
Ah, I missed that it was just an addition.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 03/14/2013 02:18 AM, Remi Collet wrote: Le 13/03/2013 23:49, Orion Poplawski a écrit : In any case, this is going to be pretty disruptive. I think we need to do some hard thinking about whether we want to go with this naming scheme or not. If we do, I think we need to do IM development in a side tag to work out all the kinks. If consumer correctly use pkg-config information, there should not have any problem... Remi. Agreed. But it appears that unfortunately cmake does not do this. This will need to get addressed. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 03/14/2013 09:30 AM, Orion Poplawski wrote: On 03/14/2013 02:18 AM, Remi Collet wrote: Le 13/03/2013 23:49, Orion Poplawski a écrit : In any case, this is going to be pretty disruptive. I think we need to do some hard thinking about whether we want to go with this naming scheme or not. If we do, I think we need to do IM development in a side tag to work out all the kinks. If consumer correctly use pkg-config information, there should not have any problem... Remi. Agreed. But it appears that unfortunately cmake does not do this. This will need to get addressed. Okay, looks like upstream cmake has a patch, I'll get it into rawhide ASAP. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 03/14/2013 09:34 AM, Orion Poplawski wrote: Okay, looks like upstream cmake has a patch, I'll get it into rawhide ASAP. Scratch that, it was a hack for Arch Linux's hacked version of ImageMagick sonames that doesn't work for Fedora. Will need to work on a fix... -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On Wed, Mar 13, 2013 at 4:03 PM, Pavel Alexeev fo...@hubbitus.com.ru wrote: Good day. By request https://bugzilla.redhat.com/show_bug.cgi?id=849065 I plan split off ImageMagick-libs sub-package and update ImageMagick to last 6.8.3-9 version. There many changes including so-name bump and version scheme change from upstream: libMagickCore.so.5 became libMagickCore-6.Q16.so I plan push it in rawhide 14-17 March if no one will argue. By rawhide you mean F-20 rawhide right? Or do you plan to land this in F-19 too? Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Le 13/03/2013 17:03, Pavel Alexeev a écrit : I plan push it in rawhide 14-17 March if no one will argue. Sounds good. Dependency rebuild required. php-magickwand php-pecl-imagick This 2 packages requires some patches to build with latest ImageMagick. I already have them ready. So ping me as soon as available in rawhide, I will take care of updating those ones. Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
Le 13/03/2013 17:16, Remi Collet a écrit : php-pecl-imagick As you're the owner of this one, if you prefer to update it, see http://svn.php.net/viewvc?view=revisionrevision=329769 Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 03/13/2013 10:03 AM, Pavel Alexeev wrote:
Good day.
By request https://bugzilla.redhat.com/show_bug.cgi?id=849065 I plan split off
ImageMagick-libs sub-package and update ImageMagick to last 6.8.3-9 version.
There many changes including so-name bump and version scheme change from
upstream:
libMagickCore.so.5 became libMagickCore-6.Q16.so
I plan push it in rawhide 14-17 March if no one will argue.
Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5117303
Also changed some directories. Major differences in layout:
%files devel
--%{_libdir}/libMagickCore.so
--%{_libdir}/libMagickWand.so
++%{_libdir}/libMagickCore-6.Q16.so
++%{_libdir}/libMagickWand-6.Q16.so
%{_libdir}/pkgconfig/MagickCore.pc
++%{_libdir}/pkgconfig/MagickCore-6.Q16.pc
%{_libdir}/pkgconfig/ImageMagick.pc
++%{_libdir}/pkgconfig/ImageMagick-6.Q16.pc
%{_libdir}/pkgconfig/MagickWand.pc
++%{_libdir}/pkgconfig/MagickWand-6.Q16.pc
%files c++-devel
--%{_libdir}/libMagick++.so
++%{_libdir}/libMagick++-6.Q16.so
This renaming is going to break a *lot* of things (including cmake finding
ImageMagick). Why was it done?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 http://www.nwra.com
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update in rawhide to 6.8.3-9 version, so-name change, split libs sub package
On 03/13/2013 04:41 PM, Orion Poplawski wrote:
On 03/13/2013 10:03 AM, Pavel Alexeev wrote:
Good day.
By request https://bugzilla.redhat.com/show_bug.cgi?id=849065 I plan split off
ImageMagick-libs sub-package and update ImageMagick to last 6.8.3-9 version.
There many changes including so-name bump and version scheme change from
upstream:
libMagickCore.so.5 became libMagickCore-6.Q16.so
I plan push it in rawhide 14-17 March if no one will argue.
Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5117303
Also changed some directories. Major differences in layout:
%files devel
--%{_libdir}/libMagickCore.so
--%{_libdir}/libMagickWand.so
++%{_libdir}/libMagickCore-6.Q16.so
++%{_libdir}/libMagickWand-6.Q16.so
%{_libdir}/pkgconfig/MagickCore.pc
++%{_libdir}/pkgconfig/MagickCore-6.Q16.pc
%{_libdir}/pkgconfig/ImageMagick.pc
++%{_libdir}/pkgconfig/ImageMagick-6.Q16.pc
%{_libdir}/pkgconfig/MagickWand.pc
++%{_libdir}/pkgconfig/MagickWand-6.Q16.pc
%files c++-devel
--%{_libdir}/libMagick++.so
++%{_libdir}/libMagick++-6.Q16.so
This renaming is going to break a *lot* of things (including cmake finding
ImageMagick). Why was it done?
There is some discussion here:
http://www.imagemagick.org/discourse-server/viewtopic.php?f=2t=22932sid=94067bc9bfe15d538f61865a7346a497
In any case, this is going to be pretty disruptive. I think we need to do
some hard thinking about whether we want to go with this naming scheme or not.
If we do, I think we need to do IM development in a side tag to work out all
the kinks.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 http://www.nwra.com
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/25/2012 01:20 AM, Pavel Alexeev wrote: 24.03.2012 02:18, Orion Poplawski wrote: On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. No, I still can't edit it because got errors: hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update now? May someone help with it if my rights is not enough? If you delete the update, I can submit a batch update. I have provenpackager rights. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
28.03.2012 19:23, Orion Poplawski написал: On 03/25/2012 01:20 AM, Pavel Alexeev wrote: 24.03.2012 02:18, Orion Poplawski wrote: On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. No, I still can't edit it because got errors: hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update now? May someone help with it if my rights is not enough? If you delete the update, I can submit a batch update. I have provenpackager rights. It will be very-very helpful and desired. But maybe you could just edit this update? -- With best wishes, Pavel Alexeev (aka Pahan-Hubbitus). For fast contact with me use jabber: hubbi...@jabber.ru -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/28/2012 09:36 AM, Pavel Alexeev wrote: 28.03.2012 19:23, Orion Poplawski написал: On 03/25/2012 01:20 AM, Pavel Alexeev wrote: 24.03.2012 02:18, Orion Poplawski wrote: On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. No, I still can't edit it because got errors: hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update now? May someone help with it if my rights is not enough? If you delete the update, I can submit a batch update. I have provenpackager rights. It will be very-very helpful and desired. But maybe you could just edit this update? Apparently I cannot do that. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/28/2012 10:01 AM, Pavel Alexeev wrote: 28.03.2012 19:42, Orion Poplawski написал: On 03/28/2012 09:36 AM, Pavel Alexeev wrote: 28.03.2012 19:23, Orion Poplawski написал: On 03/25/2012 01:20 AM, Pavel Alexeev wrote: 24.03.2012 02:18, Orion Poplawski wrote: On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. No, I still can't edit it because got errors: hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update now? May someone help with it if my rights is not enough? If you delete the update, I can submit a batch update. I have provenpackager rights. It will be very-very helpful and desired. But maybe you could just edit this update? Apparently I cannot do that. Ok, deleted ImageMagick-6.7.5.6-3.fc17 update. Please be so kind push new one. https://admin.fedoraproject.org/updates/techne-0.2.1-4.fc17,gdl-0.9.2-5.fc17,autotrace-0.31.1-29.fc17.1,ImageMagick-6.7.5.6-3.fc17 There were already calibre and pfstools updates so I couldn't add them. Let me know if there are other builds that need to be added. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
28.03.2012 20:17, Orion Poplawski написал: On 03/28/2012 10:01 AM, Pavel Alexeev wrote: 28.03.2012 19:42, Orion Poplawski написал: On 03/28/2012 09:36 AM, Pavel Alexeev wrote: 28.03.2012 19:23, Orion Poplawski написал: On 03/25/2012 01:20 AM, Pavel Alexeev wrote: 24.03.2012 02:18, Orion Poplawski wrote: On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. No, I still can't edit it because got errors: hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update now? May someone help with it if my rights is not enough? If you delete the update, I can submit a batch update. I have provenpackager rights. It will be very-very helpful and desired. But maybe you could just edit this update? Apparently I cannot do that. Ok, deleted ImageMagick-6.7.5.6-3.fc17 update. Please be so kind push new one. https://admin.fedoraproject.org/updates/techne-0.2.1-4.fc17,gdl-0.9.2-5.fc17,autotrace-0.31.1-29.fc17.1,ImageMagick-6.7.5.6-3.fc17 There were already calibre and pfstools updates so I couldn't add them. Let me know if there are other builds that need to be added. Thank you very much! But perl-GD-SecurityImage-1.71-3.fc17 shouldn't be there also? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On Wed, 28 Mar 2012 10:17:30 -0600 Orion Poplawski or...@cora.nwra.com wrote: On 03/28/2012 10:01 AM, Pavel Alexeev wrote: 28.03.2012 19:42, Orion Poplawski написал: On 03/28/2012 09:36 AM, Pavel Alexeev wrote: 28.03.2012 19:23, Orion Poplawski написал: On 03/25/2012 01:20 AM, Pavel Alexeev wrote: 24.03.2012 02:18, Orion Poplawski wrote: On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. No, I still can't edit it because got errors: hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update now? May someone help with it if my rights is not enough? If you delete the update, I can submit a batch update. I have provenpackager rights. It will be very-very helpful and desired. But maybe you could just edit this update? Apparently I cannot do that. Ok, deleted ImageMagick-6.7.5.6-3.fc17 update. Please be so kind push new one. https://admin.fedoraproject.org/updates/techne-0.2.1-4.fc17,gdl-0.9.2-5.fc17,autotrace-0.31.1-29.fc17.1,ImageMagick-6.7.5.6-3.fc17 There were already calibre and pfstools updates so I couldn't add them. Let me know if there are other builds that need to be added. I unpushed the calibre one. Please add it. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/28/2012 10:24 AM, Pavel Alexeev wrote: 28.03.2012 20:17, Orion Poplawski написал: https://admin.fedoraproject.org/updates/techne-0.2.1-4.fc17,gdl-0.9.2-5.fc17,autotrace-0.31.1-29.fc17.1,ImageMagick-6.7.5.6-3.fc17 There were already calibre and pfstools updates so I couldn't add them. Let me know if there are other builds that need to be added. Thank you very much! But perl-GD-SecurityImage-1.71-3.fc17 shouldn't be there also? Added. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
Orion Poplawski or...@cora.nwra.com writes: https://admin.fedoraproject.org/updates/techne-0.2.1-4.fc17,gdl-0.9.2-5.fc17,autotrace-0.31.1-29.fc17.1,ImageMagick-6.7.5.6-3.fc17 There were already calibre and pfstools updates so I couldn't add them. Let me know if there are other builds that need to be added. emacs-24.0.94-3.fc17 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/28/2012 10:25 AM, Kevin Fenzi wrote: On Wed, 28 Mar 2012 10:17:30 -0600 Orion Poplawskior...@cora.nwra.com wrote: https://admin.fedoraproject.org/updates/techne-0.2.1-4.fc17,gdl-0.9.2-5.fc17,autotrace-0.31.1-29.fc17.1,ImageMagick-6.7.5.6-3.fc17 There were already calibre and pfstools updates so I couldn't add them. Let me know if there are other builds that need to be added. I unpushed the calibre one. Please add it. kevin Done. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/28/2012 10:33 AM, Karel Klíč wrote: Orion Poplawskior...@cora.nwra.com writes: https://admin.fedoraproject.org/updates/techne-0.2.1-4.fc17,gdl-0.9.2-5.fc17,autotrace-0.31.1-29.fc17.1,ImageMagick-6.7.5.6-3.fc17 There were already calibre and pfstools updates so I couldn't add them. Let me know if there are other builds that need to be added. emacs-24.0.94-3.fc17 Done. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On Wed, 2012-03-28 at 20:32 -0400, Orcan Ogetbil wrote: On Wed, Mar 28, 2012 at 4:08 PM, Adam Williamson wrote: On Wed, 2012-03-28 at 21:58 +0400, Pavel Alexeev wrote: No, I have been tried edit update which was deleted to gave way to update of Orion Poplawski - bodhi said I can't add it because I have not commit rights to that package. Please see before in quote. Ah :/ so I guess provenpackagers *can* add any package to an update they have commit rights to, but they can't edit other people's updates. Non-proven-packagers can only add packages they specifically have commit rights for, to their own updates. Thanks for the clarification. This is new to me as well. Is it intentional that non-provenpackager J is not allowed to add other people's builds (of packages J does not co-maintain) to his update? I suspect it probably is, but I just didn't know. It kind of makes sense. However, I'm pretty sure it's a bug that provenpackagers can't edit other people's updates. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
24.03.2012 02:18, Orion Poplawski wrote: On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. No, I still can't edit it because got errors: hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update now? May someone help with it if my rights is not enough? -- With best wishes, Pavel Alexeev (aka Pahan-Hubbitus). For fast contact with me use jabber: hubbi...@jabber.ru -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
25.03.2012 11:59, Emmanuel Seyman wrote: * Pavel Alexeev [25/03/2012 09:51] : hubbitus does not have commit access to perl-GD-SecurityImage Ask for co-maintainer status for this package and I'll grant it right away. Hello, Emmanuel. I have asked it, thank you. But It change nothing give me in global plane - then I need be co-maintainer of all dependent packages. Emmanuel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
24.03.2012 01:30, Orcan Ogetbil wrote: On Fri, Mar 23, 2012 at 4:11 PM, Pavel Alexeev wrote: 08.03.2012 20:24, Orion Poplawski wrote: On 03/08/2012 04:18 AM, Pavel Alexeev wrote: 08.03.2012 01:16, Orion Poplawski wrote: On 03/06/2012 01:29 PM, Pavel Alexeev wrote: 05.03.2012 21:47, Sérgio Basto wrote: On Mon, 2012-03-05 at 21:11 +0400, Pavel Alexeev wrote: 05.03.2012 01:04, Sérgio Basto пишет: On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Do you think it have worth? I ready to do it. yes , not in koji ? Ok, that's done. https://admin.fedoraproject.org/updates/ImageMagick-6.7.5.6-3.fc17 If you're going to push this to F17, please submit a buildroot override and we're going to need to rebuild everything that needs it in F17. Do you mean I should submit ticket for that? Unfortunately I'm not provenpackager and have no such capability to rebuild deps. But rуфвн вщdo that or anything to help. Anyone can submit a buildroot override now here: https://admin.fedoraproject.org/updates/override/new Then you should notify all relevant package owners that they need to do a rebuild. I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You should be able to re-push the same update that you once canceled, after adding the other packages. hubbitus does not have commit access to perl-GD-SecurityImage hubbitus does not have commit access to techne I have not provenpackager rights indeed. I kindly ask FESCO to grant its me, but it not in that moment in any case. If I had them, I could compile all the packages on their own, without asking anyone. Please could you say how I may push such update? May someone help with it if my rights is not enough? Pfstools update also already exists - https://admin.fedoraproject.org/updates/pfstools-1.8.3-7.fc17 . So it does not included there. I hope its landed in repos in parallel and that deletion is not necessary. Let's hope the pfstools maintainer is aware of this issue. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
08.03.2012 20:24, Orion Poplawski wrote: On 03/08/2012 04:18 AM, Pavel Alexeev wrote: 08.03.2012 01:16, Orion Poplawski wrote: On 03/06/2012 01:29 PM, Pavel Alexeev wrote: 05.03.2012 21:47, Sérgio Basto wrote: On Mon, 2012-03-05 at 21:11 +0400, Pavel Alexeev wrote: 05.03.2012 01:04, Sérgio Basto пишет: On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Do you think it have worth? I ready to do it. yes , not in koji ? Ok, that's done. https://admin.fedoraproject.org/updates/ImageMagick-6.7.5.6-3.fc17 If you're going to push this to F17, please submit a buildroot override and we're going to need to rebuild everything that needs it in F17. Do you mean I should submit ticket for that? Unfortunately I'm not provenpackager and have no such capability to rebuild deps. But rуфвн вщdo that or anything to help. Anyone can submit a buildroot override now here: https://admin.fedoraproject.org/updates/override/new Then you should notify all relevant package owners that they need to do a rebuild. I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? Pfstools update also already exists - https://admin.fedoraproject.org/updates/pfstools-1.8.3-7.fc17 . So it does not included there. I hope its landed in repos in parallel and that deletion is not necessary. Would be nice to have a single update for all if possible. I would suggest unpushing from F17 testing until the rebuilds are done as well. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On Fri, Mar 23, 2012 at 4:11 PM, Pavel Alexeev wrote: 08.03.2012 20:24, Orion Poplawski wrote: On 03/08/2012 04:18 AM, Pavel Alexeev wrote: 08.03.2012 01:16, Orion Poplawski wrote: On 03/06/2012 01:29 PM, Pavel Alexeev wrote: 05.03.2012 21:47, Sérgio Basto wrote: On Mon, 2012-03-05 at 21:11 +0400, Pavel Alexeev wrote: 05.03.2012 01:04, Sérgio Basto пишет: On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Do you think it have worth? I ready to do it. yes , not in koji ? Ok, that's done. https://admin.fedoraproject.org/updates/ImageMagick-6.7.5.6-3.fc17 If you're going to push this to F17, please submit a buildroot override and we're going to need to rebuild everything that needs it in F17. Do you mean I should submit ticket for that? Unfortunately I'm not provenpackager and have no such capability to rebuild deps. But rуфвн вщdo that or anything to help. Anyone can submit a buildroot override now here: https://admin.fedoraproject.org/updates/override/new Then you should notify all relevant package owners that they need to do a rebuild. I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You should be able to re-push the same update that you once canceled, after adding the other packages. Pfstools update also already exists - https://admin.fedoraproject.org/updates/pfstools-1.8.3-7.fc17 . So it does not included there. I hope its landed in repos in parallel and that deletion is not necessary. Let's hope the pfstools maintainer is aware of this issue. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/23/2012 02:11 PM, Pavel Alexeev wrote: I want push now builds perl-GD-SecurityImage-1.71-3.fc17 techne-0.2.1-4.fc17 gdl-0.9.2-5.fc17 calibre-0.8.39-1.fc17 autotrace-0.31.1-29.fc17.1 ImageMagick-6.7.5.6-3.fc17 with tat build overrides but got error from bodhi what ImageMagick-6.7.5.6-3.fc17 update already exists. Should I delete it first and unpushing is not enough? You can edit it and adds builds. You may have to be a proven packager or a co-maintainer to submit an update though. Others will have to confirm. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/08/2012 04:18 AM, Pavel Alexeev wrote: 08.03.2012 01:16, Orion Poplawski wrote: On 03/06/2012 01:29 PM, Pavel Alexeev wrote: 05.03.2012 21:47, Sérgio Basto wrote: On Mon, 2012-03-05 at 21:11 +0400, Pavel Alexeev wrote: 05.03.2012 01:04, Sérgio Basto пишет: On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Do you think it have worth? I ready to do it. yes , not in koji ? Ok, that's done. https://admin.fedoraproject.org/updates/ImageMagick-6.7.5.6-3.fc17 If you're going to push this to F17, please submit a buildroot override and we're going to need to rebuild everything that needs it in F17. Do you mean I should submit ticket for that? Unfortunately I'm not provenpackager and have no such capability to rebuild deps. But rуфвн вщdo that or anything to help. Anyone can submit a buildroot override now here: https://admin.fedoraproject.org/updates/override/new Then you should notify all relevant package owners that they need to do a rebuild. Would be nice to have a single update for all if possible. I would suggest unpushing from F17 testing until the rebuilds are done as well. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On 03/06/2012 01:29 PM, Pavel Alexeev wrote: 05.03.2012 21:47, Sérgio Basto wrote: On Mon, 2012-03-05 at 21:11 +0400, Pavel Alexeev wrote: 05.03.2012 01:04, Sérgio Basto пишет: On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Do you think it have worth? I ready to do it. yes , not in koji ? Ok, that's done. https://admin.fedoraproject.org/updates/ImageMagick-6.7.5.6-3.fc17 If you're going to push this to F17, please submit a buildroot override and we're going to need to rebuild everything that needs it in F17. Would be nice to have a single update for all if possible. I would suggest unpushing from F17 testing until the rebuilds are done as well. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
05.03.2012 21:47, Sérgio Basto wrote: On Mon, 2012-03-05 at 21:11 +0400, Pavel Alexeev wrote: 05.03.2012 01:04, Sérgio Basto пишет: On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Do you think it have worth? I ready to do it. yes , not in koji ? Ok, that's done. https://admin.fedoraproject.org/updates/ImageMagick-6.7.5.6-3.fc17 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Hi to all, I am relative new in Fedora packager group. I am the maintainer of converseen and I receive this email: converseen has broken dependencies in the rawhide tree: On x86_64: converseen-0.4.9-1.fc17.x86_64 requires libMagickWand.so.4()(64bit) converseen-0.4.9-1.fc17.x86_64 requires libMagickCore.so.4()(64bit) converseen-0.4.9-1.fc17.x86_64 requires libMagick++.so.4()(64bit) On i386: converseen-0.4.9-1.fc17.i686 requires libMagickWand.so.4 converseen-0.4.9-1.fc17.i686 requires libMagickCore.so.4 converseen-0.4.9-1.fc17.i686 requires libMagick++.so.4 Please resolve this as soon as possible. I contact the developer to understand if he should do something or I do something. Could you give me a little clarification? How can I resolve this issue? Thank you! -- Mario Santagiuliana www.marionline.it signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
Hi Mario, I think you should try rebuild your package in rawhide. The problem is that converseen-0.4.9-1.fc17.x86_64 is used in rawhide, but it was built with the previous version of imagemagick and requires soname .so.4. If all goes well you can simply give a pkgdb build (after changing version to 0.4.9-2) in master to rebuild converseen. Bye Mattia Il 04/03/2012 19:33, Mario Santagiuliana ha scritto: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Hi to all, I am relative new in Fedora packager group. I am the maintainer of converseen and I receive this email: converseen has broken dependencies in the rawhide tree: On x86_64: converseen-0.4.9-1.fc17.x86_64 requires libMagickWand.so.4()(64bit) converseen-0.4.9-1.fc17.x86_64 requires libMagickCore.so.4()(64bit) converseen-0.4.9-1.fc17.x86_64 requires libMagick++.so.4()(64bit) On i386: converseen-0.4.9-1.fc17.i686 requires libMagickWand.so.4 converseen-0.4.9-1.fc17.i686 requires libMagickCore.so.4 converseen-0.4.9-1.fc17.i686 requires libMagick++.so.4 Please resolve this as soon as possible. I contact the developer to understand if he should do something or I do something. Could you give me a little clarification? How can I resolve this issue? Thank you! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Thanks, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update coming to 6.7.6-5 (.so.5)
On Sun, 2012-03-04 at 21:04 +, Sérgio Basto wrote: On Sun, 2012-03-04 at 19:33 +0100, Mario Santagiuliana wrote: In data domenica 26 febbraio 2012 18:39:14, Pavel Alexeev ha scritto: Hello. ImageMagick-6.7.6-5 will land to rawhide in short time. Soname change happened (.so.5), so dependency rebuild needed. Does it land on F17 ? , if not, why ? Off-topic question: What I really want to know, is what is more stable to an production environment that use ImageMagick and I wish make an update from ImageMagick-6.5.9-9. ImageMagick-6.7.1.9-3.fc17, ImageMagick-6.7.0.10-4.fc16 or ImageMagick-6.7.5.6-3.fc18 ? Thanks, -- Sérgio M. B. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Re: ImageMagick update coming to 6.7.6-5 (.so.5)
In data domenica 04 marzo 2012 20:40:26, Mattia Verga ha scritto: Hi Mario, I think you should try rebuild your package in rawhide. The problem is that converseen-0.4.9-1.fc17.x86_64 is used in rawhide, but it was built with the previous version of imagemagick and requires soname .so.4. If all goes well you can simply give a pkgdb build (after changing version to 0.4.9-2) in master to rebuild converseen. Thank you Mattia! I do that and should works: http://koji.fedoraproject.org/koji/taskinfo?taskID=3852075 Thanks! -- Mario Santagiuliana www.marionline.it signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
22.05.2010 17:28, Hans de Goede пишет:
Hi,
On 05/17/2010 03:13 AM, Chen Lei wrote:
2010/5/16 Pavel Alexeev (aka Pahan-Hubbitus)fo...@hubbitus.com.ru
mailto:fo...@hubbitus.com.ru
About ABI breakage there separate problem in ImageMagick -
http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg736218.html
So, upstream is not carefully there and I never can't guarantee what
there no ABI breakage in any update...
P.S. It seams it does not hit list, i post mail again. It is reason
such big delay...
--
Normally, if the update is a pure bugfix release, it's safe to update
and don't need a rebuild, and you should update them on rawhide as well
as stable branches to fix bugs
If API/ABI is changed, only the following packages need a rebuild.
Packages depends on ImageMagick itself actually don't need a rebuild
even the API is changed.
Wrong, the main ImageMagick provides libs too, on F-13 the full list is:
[h...@localhost anaconda]$ repoquery -q --whatrequires
'libMagickCore.so.2()(64bit)' 'libMagickWand.so.2()(64bit)'
'libMagick++.so.2()(64bit)'
ruby-RMagick-0:2.13.1-1.fc13.1.x86_64
ImageMagick-djvu-0:6.5.8.10-6.fc13.x86_64
vips-tools-0:7.20.7-1.fc13.x86_64
rss-glx-0:0.9.1.p-2.fc13.x86_64
q-magick-0:7.11-6.fc12.x86_64
nip2-0:7.20.7-3.fc13.x86_64
ale-0:0.9.0.3-2.fc12.x86_64
zbar-0:0.10-2.fc13.x86_64
psiconv-0:0.9.8-5.fc12.x86_64
xastir-1:1.9.6-3.fc13.x86_64
ImageMagick-c++-0:6.5.8.10-6.fc13.x86_64
ImageMagick-perl-0:6.5.8.10-6.fc13.x86_64
vips-0:7.20.7-1.fc13.x86_64
autotrace-0:0.31.1-23.fc12.x86_64
inkscape-view-0:0.47-6.fc13.x86_64
k3d-0:0.8.0.1-1.fc13.x86_64
drawtiming-0:0.7.1-1.fc13.x86_64
dx-libs-0:4.4.4-15.fc13.x86_64
dx-0:4.4.4-15.fc13.x86_64
pfstools-0:1.8.1-1.fc13.x86_64
gdl-python-0:0.9-0.10.rc4.fc13.x86_64
oxine-0:0.7.1-6.fc13.x86_64
xine-lib-extras-0:1.1.18.1-1.fc13.x86_64
transcode-0:1.1.5-4.fc13.x86_64
ImageMagick-devel-0:6.5.8.10-6.fc13.x86_64
imageinfo-0:0.05-10.fc12.x86_64
vips-python-0:7.20.7-1.fc13.x86_64
calibre-0:0.6.42-1.fc13.x86_64
pfstools-imgmagick-0:1.8.1-1.fc13.x86_64
php-pecl-imagick-0:2.2.2-4.fc12.x86_64
inkscape-0:0.47-6.fc13.x86_64
php-magickwand-0:1.0.8-4.fc12.x86_64
k3d-0:0.7.11.0-6.fc13.x86_64
gdl-0:0.9-0.10.rc4.fc13.x86_64
zbar-0:0.10-2.fc13.x86_64
transcode-0:1.1.5-4.fc13.x86_64
ImageMagick-devel-0:6.5.8.10-6.fc13.x86_64
vips-python-0:7.20.7-1.fc13.x86_64
calibre-0:0.6.42-1.fc13.x86_64
ImageMagick-c++-0:6.5.8.10-6.fc13.x86_64
vips-tools-0:7.20.7-1.fc13.x86_64
rss-glx-0:0.9.1.p-2.fc13.x86_64
vips-0:7.20.7-1.fc13.x86_64
php-magickwand-0:1.0.8-4.fc12.x86_64
oxine-0:0.7.1-6.fc13.x86_64
nip2-0:7.20.7-3.fc13.x86_64
xine-lib-extras-0:1.1.18.1-1.fc13.x86_64
php-pecl-imagick-0:2.2.2-4.fc12.x86_64
inkscape-0:0.47-6.fc13.x86_64
k3d-0:0.8.0.1-1.fc13.x86_64
ImageMagick-c++-devel-0:6.5.8.10-6.fc13.x86_64
drawtiming-0:0.7.1-1.fc13.x86_64
pfstools-imgmagick-0:1.8.1-1.fc13.x86_64
gdl-python-0:0.9-0.10.rc4.fc13.x86_64
pfstools-0:1.8.1-1.fc13.x86_64
k3d-0:0.7.11.0-6.fc13.x86_64
inkscape-view-0:0.47-6.fc13.x86_64
gdl-0:0.9-0.10.rc4.fc13.x86_64
repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick-c++
ImageMagick-c++-0:6.6.0.2-8.fc14.i686
ImageMagick-c++-0:6.6.0.2-8.fc14.x86_64
inkscape-0:0.48-0.2.20100505bzr.fc14.x86_64
ImageMagick-c++-devel-0:6.6.0.2-8.fc14.x86_64
gdl-0:0.9-0.12.rc4.fc14.x86_64
pfstools-imgmagick-0:1.8.1-1.fc14.x86_64
drawtiming-0:0.7.1-1.1.fc14.x86_64
pfstools-0:1.8.1-1.fc14.x86_64
ImageMagick-c++-devel-0:6.6.0.2-8.fc14.i686
k3d-0:0.8.0.1-1.fc14.x86_64
gdl-python-0:0.9-0.12.rc4.fc14.x86_64
inkscape-view-0:0.48-0.2.20100505bzr.fc14.x86_64
BTW, some subpackages contain .la files, you should remove them in %install.
e.g.
This is not necessarily good advice either:
1) As these la files are for plugins which are located outside of %{_libdir},
they do no harm
2) In the past there have been cases with plugins where the libraries plugins
loading mechanism relies on the .la files being present, that might very well
be the case here.
Regards,
Hans
Very interesting.
Actually spec file contain string to delete in root build directory:
rm $RPM_BUILD_ROOT%{_libdir}/*.la
What can happened bad if I do:
find $RPM_BUILD_ROOT -type f -name *.la -exec rm -f {} \;
as Chen Lei suggested before?
Actually I done that, but update is not pushed yet.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
On Sun, May 30, 2010 at 10:59 AM, Pavel Alexeev (aka Pahan-Hubbitus) wrote:
Actually spec file contain string to delete in root build directory:
rm $RPM_BUILD_ROOT%{_libdir}/*.la
What can happened bad if I do:
find $RPM_BUILD_ROOT -type f -name *.la -exec rm -f {} \;
as Chen Lei suggested before?
Actually I done that, but update is not pushed yet.
https://admin.fedoraproject.org/mailman/listinfo/devel
I wouldn't push that. I did the merge review for ImageMagick a long
time ago and things may have changed since then though. From what I
remember, the .la files that are not directly in %{_libdir} were
needed by some plugins. If you remove those .la files, you kill the
plugins.
Orcan
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
Pavel Alexeev (aka Pahan-Hubbitus) wrote, at 05/30/2010 11:59 PM +9:00:
22.05.2010 17:28, Hans de Goede пишет:
This is not necessarily good advice either:
1) As these la files are for plugins which are located outside of %{_libdir},
they do no harm
2) In the past there have been cases with plugins where the libraries plugins
loading mechanism relies on the .la files being present, that might very well
be the case here.
Regards,
Hans
Very interesting.
Actually spec file contain string to delete in root build directory:
rm $RPM_BUILD_ROOT%{_libdir}/*.la
What can happened bad if I do:
find $RPM_BUILD_ROOT -type f -name *.la -exec rm -f {} \;
as Chen Lei suggested before?
Actually I done that, but update is not pushed yet.
At least you have to check if removing libtool files in module directory
won't raise this issue again:
https://bugzilla.redhat.com/show_bug.cgi?id=185237
Regards,
Mamoru
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
30.05.2010 19:22, Mamoru Tasaka пишет:
Pavel Alexeev (aka Pahan-Hubbitus) wrote, at 05/30/2010 11:59 PM +9:00:
22.05.2010 17:28, Hans de Goede пишет:
This is not necessarily good advice either:
1) As these la files are for plugins which are located outside of
%{_libdir},
they do no harm
2) In the past there have been cases with plugins where the libraries
plugins
loading mechanism relies on the .la files being present, that might very
well
be the case here.
Regards,
Hans
Very interesting.
Actually spec file contain string to delete in root build directory:
rm $RPM_BUILD_ROOT%{_libdir}/*.la
What can happened bad if I do:
find $RPM_BUILD_ROOT -type f -name *.la -exec rm -f {} \;
as Chen Lei suggested before?
Actually I done that, but update is not pushed yet.
At least you have to check if removing libtool files in module directory
won't raise this issue again:
https://bugzilla.redhat.com/show_bug.cgi?id=185237
Awesome!
$ convert -list format | wc -l
7
Mamoru, very thank you! I add comment in spec now with link to that bug
to do not miss it in the future!
Regards,
Mamoru
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
Hi,
On 05/17/2010 03:13 AM, Chen Lei wrote:
2010/5/16 Pavel Alexeev (aka Pahan-Hubbitus) fo...@hubbitus.com.ru
mailto:fo...@hubbitus.com.ru
About ABI breakage there separate problem in ImageMagick -
http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg736218.html
So, upstream is not carefully there and I never can't guarantee what
there no ABI breakage in any update...
P.S. It seams it does not hit list, i post mail again. It is reason
such big delay...
--
Normally, if the update is a pure bugfix release, it's safe to update
and don't need a rebuild, and you should update them on rawhide as well
as stable branches to fix bugs
If API/ABI is changed, only the following packages need a rebuild.
Packages depends on ImageMagick itself actually don't need a rebuild
even the API is changed.
Wrong, the main ImageMagick provides libs too, on F-13 the full list is:
[h...@localhost anaconda]$ repoquery -q --whatrequires
'libMagickCore.so.2()(64bit)' 'libMagickWand.so.2()(64bit)'
'libMagick++.so.2()(64bit)'
ruby-RMagick-0:2.13.1-1.fc13.1.x86_64
ImageMagick-djvu-0:6.5.8.10-6.fc13.x86_64
vips-tools-0:7.20.7-1.fc13.x86_64
rss-glx-0:0.9.1.p-2.fc13.x86_64
q-magick-0:7.11-6.fc12.x86_64
nip2-0:7.20.7-3.fc13.x86_64
ale-0:0.9.0.3-2.fc12.x86_64
zbar-0:0.10-2.fc13.x86_64
psiconv-0:0.9.8-5.fc12.x86_64
xastir-1:1.9.6-3.fc13.x86_64
ImageMagick-c++-0:6.5.8.10-6.fc13.x86_64
ImageMagick-perl-0:6.5.8.10-6.fc13.x86_64
vips-0:7.20.7-1.fc13.x86_64
autotrace-0:0.31.1-23.fc12.x86_64
inkscape-view-0:0.47-6.fc13.x86_64
k3d-0:0.8.0.1-1.fc13.x86_64
drawtiming-0:0.7.1-1.fc13.x86_64
dx-libs-0:4.4.4-15.fc13.x86_64
dx-0:4.4.4-15.fc13.x86_64
pfstools-0:1.8.1-1.fc13.x86_64
gdl-python-0:0.9-0.10.rc4.fc13.x86_64
oxine-0:0.7.1-6.fc13.x86_64
xine-lib-extras-0:1.1.18.1-1.fc13.x86_64
transcode-0:1.1.5-4.fc13.x86_64
ImageMagick-devel-0:6.5.8.10-6.fc13.x86_64
imageinfo-0:0.05-10.fc12.x86_64
vips-python-0:7.20.7-1.fc13.x86_64
calibre-0:0.6.42-1.fc13.x86_64
pfstools-imgmagick-0:1.8.1-1.fc13.x86_64
php-pecl-imagick-0:2.2.2-4.fc12.x86_64
inkscape-0:0.47-6.fc13.x86_64
php-magickwand-0:1.0.8-4.fc12.x86_64
k3d-0:0.7.11.0-6.fc13.x86_64
gdl-0:0.9-0.10.rc4.fc13.x86_64
zbar-0:0.10-2.fc13.x86_64
transcode-0:1.1.5-4.fc13.x86_64
ImageMagick-devel-0:6.5.8.10-6.fc13.x86_64
vips-python-0:7.20.7-1.fc13.x86_64
calibre-0:0.6.42-1.fc13.x86_64
ImageMagick-c++-0:6.5.8.10-6.fc13.x86_64
vips-tools-0:7.20.7-1.fc13.x86_64
rss-glx-0:0.9.1.p-2.fc13.x86_64
vips-0:7.20.7-1.fc13.x86_64
php-magickwand-0:1.0.8-4.fc12.x86_64
oxine-0:0.7.1-6.fc13.x86_64
nip2-0:7.20.7-3.fc13.x86_64
xine-lib-extras-0:1.1.18.1-1.fc13.x86_64
php-pecl-imagick-0:2.2.2-4.fc12.x86_64
inkscape-0:0.47-6.fc13.x86_64
k3d-0:0.8.0.1-1.fc13.x86_64
ImageMagick-c++-devel-0:6.5.8.10-6.fc13.x86_64
drawtiming-0:0.7.1-1.fc13.x86_64
pfstools-imgmagick-0:1.8.1-1.fc13.x86_64
gdl-python-0:0.9-0.10.rc4.fc13.x86_64
pfstools-0:1.8.1-1.fc13.x86_64
k3d-0:0.7.11.0-6.fc13.x86_64
inkscape-view-0:0.47-6.fc13.x86_64
gdl-0:0.9-0.10.rc4.fc13.x86_64
repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick-c++
ImageMagick-c++-0:6.6.0.2-8.fc14.i686
ImageMagick-c++-0:6.6.0.2-8.fc14.x86_64
inkscape-0:0.48-0.2.20100505bzr.fc14.x86_64
ImageMagick-c++-devel-0:6.6.0.2-8.fc14.x86_64
gdl-0:0.9-0.12.rc4.fc14.x86_64
pfstools-imgmagick-0:1.8.1-1.fc14.x86_64
drawtiming-0:0.7.1-1.1.fc14.x86_64
pfstools-0:1.8.1-1.fc14.x86_64
ImageMagick-c++-devel-0:6.6.0.2-8.fc14.i686
k3d-0:0.8.0.1-1.fc14.x86_64
gdl-python-0:0.9-0.12.rc4.fc14.x86_64
inkscape-view-0:0.48-0.2.20100505bzr.fc14.x86_64
BTW, some subpackages contain .la files, you should remove them in %install.
e.g.
This is not necessarily good advice either:
1) As these la files are for plugins which are located outside of %{_libdir},
they do no harm
2) In the past there have been cases with plugins where the libraries plugins
loading mechanism relies on the .la files being present, that might very well
be the case here.
Regards,
Hans
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
2010/5/22 Hans de Goede hdego...@redhat.com
Hi,
On 05/17/2010 03:13 AM, Chen Lei wrote:
repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick-c++
ImageMagick-c++-0:6.6.0.2-8.fc14.i686
ImageMagick-c++-0:6.6.0.2-8.fc14.x86_64
inkscape-0:0.48-0.2.20100505bzr.fc14.x86_64
ImageMagick-c++-devel-0:6.6.0.2-8.fc14.x86_64
gdl-0:0.9-0.12.rc4.fc14.x86_64
pfstools-imgmagick-0:1.8.1-1.fc14.x86_64
drawtiming-0:0.7.1-1.1.fc14.x86_64
pfstools-0:1.8.1-1.fc14.x86_64
ImageMagick-c++-devel-0:6.6.0.2-8.fc14.i686
k3d-0:0.8.0.1-1.fc14.x86_64
gdl-python-0:0.9-0.12.rc4.fc14.x86_64
inkscape-view-0:0.48-0.2.20100505bzr.fc14.x86_64
BTW, some subpackages contain .la files, you should remove them in
%install.
e.g.
This is not necessarily good advice either:
1) As these la files are for plugins which are located outside of
%{_libdir},
they do no harm
2) In the past there have been cases with plugins where the libraries
plugins
loading mechanism relies on the .la files being present, that might very
well
be the case here.
.
This is actually my fault:) . ImageMagick strangely relies on those .la
files to load modules. Containing .la files in packages will pull in libtool
as dependency, can we filter it out?
Chen Lei
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
03.05.2010 03:37, Orcan Ogetbil пишет: On Sun, May 2, 2010 at 7:20 PM, Pavel Alexeev (aka Pahan-Hubbitus) wrote: 26.04.2010 05:04, Orcan Ogetbil пишет: On Sun, Apr 25, 2010 at 7:13 PM, Kevin Kofler wrote: Christoph Wickert wrote: repoquery --disablerepo=\* --enablerepo=rawhide --whatrequires ImageMagick FYI, repoquery --repoid=rawhide --whatrequires ImageMagick does the trick too. That does not detect packages that require ImageMagick-c++, ImageMagick-perl etc. The wildcard \* seems to work. So it would be good to run a command to include the subpackages of ImageMagick, with the --alldeps flag, e.g. $ repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick\* etc Orcan It produce big list of packages, thank you. What about second part of my questions? How frequently I should (can) update package? There was a huge debate about the updating packages policy in the last months in this list. I don't think there is a unique answer to this question. I would say, it is left to the decision of the maintainer. It all comes down how big the update is. * Suppose there is a big API/ABI change: If you believe that you can deal with rebuilding all the dependent packages, and support them all in stable branches, go ahead and update. Otherwise update only in rawhide and let people know that they need to rebuild their packages, or rebuild them yourself. * Just a bugfix release, with no API/ABI breakage: In this case it should be safe to update. I tried to answer the question as neutral as possible as I don't want to restart the bitchfest. Orcan Thank you, Orcan. And off course I do not want any holly-war. I just wonder about frequently of upstream releases (as I say before around one in week). Is it normal update it in rawhide each time? About ABI breakage there separate problem in ImageMagick - http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg736218.html So, upstream is not carefully there and I never can't guarantee what there no ABI breakage in any update... P.S. It seams it does not hit list, i post mail again. It is reason such big delay... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
16.05.2010 19:35, Orcan Ogetbil пишет: On Sun, May 16, 2010 at 11:14 AM, Pavel Alexeev (aka Pahan-Hubbitus) wrote: I just wonder about frequently of upstream releases (as I say before around one in week). Is it normal update it in rawhide each time? About ABI breakage there separate problem in ImageMagick - http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg736218.html So, upstream is not carefully there and I never can't guarantee what there no ABI breakage in any update... Hi Pavel, It should be okay to update stuff in rawhide, but you probably need to give time to maintainers to rebuild their packages before branchings (for example, to F-14) or rebuild them yourself. Is the upstream not bumping the soname when they change the ABI? That's not very nice. Is there no way to educate them? You can use Debian's unresolved symbols detection script that is mentioned in the above link. I would say, rebuilding 30(?) packages every other week just for an ImageMagick update would be impractical, even if it is done in rawhide only. If you are not comfortable with detecting the ABI breakage, or if you can't dedicate enough time, I recommend to update every 2-3 months. Let's hear what others will say. Orcan Thank you very much for the answers. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
On 16 May 2010 21:05, Orcan Ogetbil wrote: On Sun, May 16, 2010 at 11:14 AM, Pavel Alexeev (aka Pahan-Hubbitus) wrote: I just wonder about frequently of upstream releases (as I say before around one in week). Is it normal update it in rawhide each time? About ABI breakage there separate problem in ImageMagick - http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg736218.html So, upstream is not carefully there and I never can't guarantee what there no ABI breakage in any update... [..] mentioned in the above link. I would say, rebuilding 30(?) packages every other week just for an ImageMagick update would be impractical, even if it is done in rawhide only. If you are not comfortable with detecting the ABI breakage, or if you can't dedicate enough time, I recommend to update every 2-3 months. +1, Keeping a careful look at changes they introduce with each release and whether it is really worth the hassle. -- Rakesh Pandit https://fedoraproject.org/wiki/User:Rakesh freedom, friends, features, first -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
On 05/16/2010 02:53 PM, Rakesh Pandit wrote: On 16 May 2010 21:05, Orcan Ogetbil wrote: mentioned in the above link. I would say, rebuilding 30(?) packages every other week just for an ImageMagick update would be impractical, Are you referring to ABI changes or just rebuilds. For rebuilds, we should have a complete rebuild every night or every weekend - anything that needs rebuilding does and if it doesn't it doesn't. That way we have a consistent build tree always. And oh yeh - we should do that build using rawhide too. For ABI changes that are not backward compatible (is thats what happening here?) ... it depends how hard it is to script any changes to other packages. g -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
26.04.2010 05:04, Orcan Ogetbil пишет: On Sun, Apr 25, 2010 at 7:13 PM, Kevin Kofler wrote: Christoph Wickert wrote: repoquery --disablerepo=\* --enablerepo=rawhide --whatrequires ImageMagick FYI, repoquery --repoid=rawhide --whatrequires ImageMagick does the trick too. That does not detect packages that require ImageMagick-c++, ImageMagick-perl etc. The wildcard \* seems to work. So it would be good to run a command to include the subpackages of ImageMagick, with the --alldeps flag, e.g. $ repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick\* etc Orcan It produce big list of packages, thank you. What about second part of my questions? How frequently I should (can) update package? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
On Sun, May 2, 2010 at 7:20 PM, Pavel Alexeev (aka Pahan-Hubbitus) wrote: 26.04.2010 05:04, Orcan Ogetbil пишет: On Sun, Apr 25, 2010 at 7:13 PM, Kevin Kofler wrote: Christoph Wickert wrote: repoquery --disablerepo=\* --enablerepo=rawhide --whatrequires ImageMagick FYI, repoquery --repoid=rawhide --whatrequires ImageMagick does the trick too. That does not detect packages that require ImageMagick-c++, ImageMagick-perl etc. The wildcard \* seems to work. So it would be good to run a command to include the subpackages of ImageMagick, with the --alldeps flag, e.g. $ repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick\* etc Orcan It produce big list of packages, thank you. What about second part of my questions? How frequently I should (can) update package? There was a huge debate about the updating packages policy in the last months in this list. I don't think there is a unique answer to this question. I would say, it is left to the decision of the maintainer. It all comes down how big the update is. * Suppose there is a big API/ABI change: If you believe that you can deal with rebuilding all the dependent packages, and support them all in stable branches, go ahead and update. Otherwise update only in rawhide and let people know that they need to rebuild their packages, or rebuild them yourself. * Just a bugfix release, with no API/ABI breakage: In this case it should be safe to update. I tried to answer the question as neutral as possible as I don't want to restart the bitchfest. Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
Am Sonntag, den 25.04.2010, 18:11 +0400 schrieb Pavel Alexeev (aka Pahan-Hubbitus): I'll plan update ImageMagick now - [snipped] Must I notify someone about coming update? How? Is it enough write here? I suggest to use repoquery --whatrequires ImageMagick and repoquery --disablerepo=\* --enablerepo=rawhide --whatrequires ImageMagick and mail all the owners of the packages directly. You can use packagename-ow...@fedoraproject.org instead of looking up the individual addresses. Regards, Christoph -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
Christoph Wickert wrote: repoquery --disablerepo=\* --enablerepo=rawhide --whatrequires ImageMagick FYI, repoquery --repoid=rawhide --whatrequires ImageMagick does the trick too. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: ImageMagick update
On Sun, Apr 25, 2010 at 7:13 PM, Kevin Kofler wrote: Christoph Wickert wrote: repoquery --disablerepo=\* --enablerepo=rawhide --whatrequires ImageMagick FYI, repoquery --repoid=rawhide --whatrequires ImageMagick does the trick too. That does not detect packages that require ImageMagick-c++, ImageMagick-perl etc. The wildcard \* seems to work. So it would be good to run a command to include the subpackages of ImageMagick, with the --alldeps flag, e.g. $ repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick\* etc Orcan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
