#6015 closed enhancement (fixed)
libjpeg-turbo-1.4.0
| Reported by: | Fernando de Oliveira | Owned by: | Fernando de Oliveira |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.7 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by )
http://downloads.sourceforge.net/libjpeg-turbo/libjpeg-turbo-1.4.0.tar.gz
http://sourceforge.net/p/libjpeg-turbo/mailman/message/33210889/
Significant changes since 1.4 beta1 =================================== ...
http://sourceforge.net/p/libjpeg-turbo/mailman/message/32773162/
Significant changes since 1.3.1 =============================== ...
Change History (8)
comment:1 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
comment:3 by , 9 years ago
Package list was wrong.
cups-filters emacs feh fltk fontforge gdk-pixbuf gegl graphviz gs gst-plugins-good gst10-plugins-good gwenview imagemagick imlib2 jasper k3b kde-runtime kdelibs lcms lcms2 libmng libquicktime libraw libraw libreoffice libtiff libwebp links mplayer mupdf okular perl-modules php poppler qt4 qt5 sane tigervnc transcode tumbler
comment:4 by , 9 years ago
I suggest picking a couple of packages and testing them. If it goes OK, then just add to the book. We are only about 5 weeks away from a package freeze and we will be building everything during the freeze and can sort out this type of issue then.
It's OK to break things in svn. Better to find out problems now.
comment:6 by , 9 years ago
No API was changed as it would break the ABI too, which would be unacceptable without a major version bump (2.0 in this case). According to the changes @ sourceforge.net, some stale code was removed that has nothing to do with API and some new has been added, which shouldn't break anything that wasn't using it before (can't use something that didn't exist in the first place). The rest appears to be some {de,en}coder fixes and minor features for the executables that are provided in the package.
comment:8 by , 9 years ago
| Description: | modified (diff) |
|---|
I don't know how to proceed here, because there are 40 packages using it and the API has important changes.
Thinking that priority should be switched to low.
Giving back to the book.
This is a good candidate for those that test packages from building a system from scratch.
Meanwhile, will try to test a couple of packages a day, to see if eventually I could complete the list below.
Perhaps somebody has a better solution/suggestion and I am superestimtaing the risk of breaking dependent packages.
Apologies for that.