[opensuse-factory] libjpeg v6b support dropped
In https://build.opensuse.org/package/rdiff?linkrev=base&package=libjpeg-turbo&project=graphics&rev=15 support for libjpeg v6b was dropped without any comment in the changelog. Was that intended? Notice (if you care at all, otherwise ignore this) that LSB still defines libjpeg.so.62 (http://refspecs.linux-foundation.org/LSB_4.1.0/LSB-Desktop-generic/LSB-Deskt...) Also notice that we are changing the default for libjpeg-turbo, and that v8 support is still not 100% complete (see README-turbo.txt). Which version libjpeg8 will be installed by default? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 22/09/12 08:25, Cristian Morales Vega escribió:
In https://build.opensuse.org/package/rdiff?linkrev=base&package=libjpeg-turbo&project=graphics&rev=15 support for libjpeg v6b was dropped without any comment in the changelog. Was that intended?
Notice (if you care at all, otherwise ignore this) that LSB still defines libjpeg.so.62 (http://refspecs.linux-foundation.org/LSB_4.1.0/LSB-Desktop-generic/LSB-Deskt...)
Well. that's something for the LSB to fix, or for people that needs an LSB target. We need working stuff instead of paper standards. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 22 September 2012 21:33, Cristian Rodríguez
El 22/09/12 08:25, Cristian Morales Vega escribió:
In https://build.opensuse.org/package/rdiff?linkrev=base&package=libjpeg-turbo&project=graphics&rev=15 support for libjpeg v6b was dropped without any comment in the changelog. Was that intended?
Notice (if you care at all, otherwise ignore this) that LSB still defines libjpeg.so.62 (http://refspecs.linux-foundation.org/LSB_4.1.0/LSB-Desktop-generic/LSB-Deskt...)
Well. that's something for the LSB to fix, or for people that needs an LSB target.
We need working stuff instead of paper standards.
As far as I can see Ubuntu provides both and Fedora only .62. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 22.09.2012 22:33, schrieb Cristian Rodríguez:
El 22/09/12 08:25, Cristian Morales Vega escribió:
In https://build.opensuse.org/package/rdiff?linkrev=base&package=libjpeg-turbo&project=graphics&rev=15 support for libjpeg v6b was dropped without any comment in the changelog. Was that intended?
Notice (if you care at all, otherwise ignore this) that LSB still defines libjpeg.so.62 (http://refspecs.linux-foundation.org/LSB_4.1.0/LSB-Desktop-generic/LSB-Deskt...)
Well. that's something for the LSB to fix, or for people that needs an LSB target.
Come on. Even people who don't care for LSB sometimes require libjpeg.so.62, making Factory unusable for them is not nice. Why can't we build two versions of libjpeg-turbo, one with enabled "--with-jpeg8" and one without?
We need working stuff instead of paper standards.
Exactly. A system without libjpeg.so.62 often is not considered "working stuff". -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 9/23/2012 12:48 PM, Stefan Seyfried wrote:
Am 22.09.2012 22:33, schrieb Cristian Rodríguez:
El 22/09/12 08:25, Cristian Morales Vega escribió:
In https://build.opensuse.org/package/rdiff?linkrev=base&package=libjpeg-turbo&project=graphics&rev=15 support for libjpeg v6b was dropped without any comment in the changelog. Was that intended?
Notice (if you care at all, otherwise ignore this) that LSB still defines libjpeg.so.62 (http://refspecs.linux-foundation.org/LSB_4.1.0/LSB-Desktop-generic/LSB-Deskt...)
Well. that's something for the LSB to fix, or for people that needs an LSB target.
Come on. Even people who don't care for LSB sometimes require libjpeg.so.62, making Factory unusable for them is not nice. Why can't we build two versions of libjpeg-turbo, one with enabled "--with-jpeg8" and one without?
We need working stuff instead of paper standards.
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
Often I have contemplated compiling a list of "Sh** Christian says." (By all means he can compile a similar list from my old posts. I completely welcome that comparison.) -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 28/09/12 14:25, Brian K. White escribió:
Often I have contemplated compiling a list of "Sh** Christian says."
I guess I can voice my disagrement with an "standard" that is doomed to fail,have improved nothing and attempting to comply with it distracts developer's focus on important things can I ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Sep 23, 2012 at 1:48 PM, Stefan Seyfried
Well. that's something for the LSB to fix, or for people that needs an LSB target.
Come on. Even people who don't care for LSB sometimes require libjpeg.so.62, making Factory unusable for them is not nice. Why can't we build two versions of libjpeg-turbo, one with enabled "--with-jpeg8" and one without?
We need working stuff instead of paper standards.
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
Well, I have an app that hasn't seen any updates to its usage of libjpeg for a while, and it transitioned to .8 quite seamlessly (uses 62 on 11.4, 8 on Factory). (I had to check, cuz I didn't do anything explicitly). If they're *that* compatible... why care? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 28.09.2012 19:33, schrieb Claudio Freire:
On Sun, Sep 23, 2012 at 1:48 PM, Stefan Seyfried
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
Well, I have an app that hasn't seen any updates to its usage of libjpeg for a while, and it transitioned to .8 quite seamlessly (uses 62 on 11.4, 8 on Factory). (I had to check, cuz I didn't do anything explicitly).
But it was recompiled on Factory, wasn't it? This is about applications that you cannot recompile.
If they're *that* compatible... why care?
They are compatible on source level, but not binary compatible. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Sep 29, 2012 at 6:12 AM, Stefan Seyfried
Am 28.09.2012 19:33, schrieb Claudio Freire:
On Sun, Sep 23, 2012 at 1:48 PM, Stefan Seyfried
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
Well, I have an app that hasn't seen any updates to its usage of libjpeg for a while, and it transitioned to .8 quite seamlessly (uses 62 on 11.4, 8 on Factory). (I had to check, cuz I didn't do anything explicitly).
But it was recompiled on Factory, wasn't it?
This is about applications that you cannot recompile.
Is OBS suddenly supporting binary blobs?
If they're *that* compatible... why care?
They are compatible on source level, but not binary compatible.
So? OBS rebuilds everything in the distribution from source. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 29.09.2012 20:18, schrieb Claudio Freire:
On Sat, Sep 29, 2012 at 6:12 AM, Stefan Seyfried
wrote: Am 28.09.2012 19:33, schrieb Claudio Freire:
On Sun, Sep 23, 2012 at 1:48 PM, Stefan Seyfried
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
This is about applications that you cannot recompile.
Is OBS suddenly supporting binary blobs?
You know that there are other sources of software than the OBS? There's even such a thing as proprietary software.
If they're *that* compatible... why care?
They are compatible on source level, but not binary compatible.
So? OBS rebuilds everything in the distribution from source.
There's more to "working stuff" than what's available from OBS. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 2012-09-29 20:20, Stefan Seyfried wrote:
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
This is about applications that you cannot recompile.
Is OBS suddenly supporting binary blobs?
You know that there are other sources of software than the OBS? There's even such a thing as proprietary software.
You know that distros generally did not, and do not, bother with keeping old stuff around? I myself need þe olde libcurl.so.3 and libgmp.so.4 for some game servers (HLDS, ModernWarfare4, such things). But if we started to talk about catering for proprietary software, there would be no end to requests for such packages. If proprietary software needs a particular outdated version of a library, it should ship it and use it with LD_LIBRARY_PATH. (VMware WS is one that understood this; MWf4 did not - yet.) NB: "MW" is preoccupied by MechWarrior ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 29 September 2012 20:49, Jan Engelhardt
On Saturday 2012-09-29 20:20, Stefan Seyfried wrote:
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
This is about applications that you cannot recompile.
Is OBS suddenly supporting binary blobs?
You know that there are other sources of software than the OBS? There's even such a thing as proprietary software.
You know that distros generally did not, and do not, bother with keeping old stuff around?
Is this case we are not talking about old stuff. libjpeg.so.6 is the default soname in the latest version of libjpeg-turbo. As already said LSB defines libjpeg.so.6 and Fedora doesn't provide a libjpeg.so.8. For a third party developer it only makes sense to distribute binaries linking against libjpeg.so.6. Since I didn't receive an explanation about why the change was done I will create a submit request to provide both libjpeg.so.6 and libjpeg.so.8 versions of libjpeg-turbo. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Sep 29, 2012 at 7:06 PM, Cristian Morales Vega
Since I didn't receive an explanation about why the change was done I will create a submit request to provide both libjpeg.so.6 and libjpeg.so.8 versions of libjpeg-turbo.
Given what I posted half a second before you, I'd agree with that. It would be wise to check against those third-party apps first, though. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 29.09.2012 21:49, schrieb Jan Engelhardt:
On Saturday 2012-09-29 20:20, Stefan Seyfried wrote:
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
This is about applications that you cannot recompile.
Is OBS suddenly supporting binary blobs?
You know that there are other sources of software than the OBS? There's even such a thing as proprietary software.
You know that distros generally did not, and do not, bother with keeping old stuff around?
Yeah, like gcc33 and libstdc++33 which is also in Factory, libpng12, libpng14,... It's not even like we'd need to keep extra sources around. libjpeg-turbo can build libjpeg62 and libjpeg8, it is just a configure switch. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2012-09-30 00:14, Stefan Seyfried wrote:
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
You know that there are other sources of software than the OBS? There's even such a thing as proprietary software.
You know that distros generally did not, and do not, bother with keeping old stuff around?
Yeah, like gcc33 and libstdc++33 which is also in Factory, libpng12, libpng14,...
You are citing a specific class of packages. libnl-1_1 also falls into that pool, for example. But the reason we still have libpng12, libnl-1_1, etc. is not because some random proprietary program could possibly be linking against it, but because some software, in *source form*, still depends on it for compilation. Yes, you can turn on libjpeg.so.62 generation in jpeg-turbo; ncurses does something similar (producing both libncurses.so.5 and libncurses.so.6), but then again, it does not do that for for proprietary programs _either_. Like with libnl-1_1->libnl3, there was a bigger API change in ncurses5->ncurses6. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Sep 30, 2012 at 12:53:12PM +0200, Jan Engelhardt wrote:
On Sunday 2012-09-30 00:14, Stefan Seyfried wrote:
Exactly. A system without libjpeg.so.62 often is not considered "working stuff".
You know that there are other sources of software than the OBS? There's even such a thing as proprietary software.
You know that distros generally did not, and do not, bother with keeping old stuff around?
Yeah, like gcc33 and libstdc++33 which is also in Factory, libpng12, libpng14,...
You are citing a specific class of packages. libnl-1_1 also falls into that pool, for example.
But the reason we still have libpng12, libnl-1_1, etc. is not because some random proprietary program could possibly be linking against it, but because some software, in *source form*, still depends on it for compilation.
Yes, you can turn on libjpeg.so.62 generation in jpeg-turbo; ncurses does something similar (producing both libncurses.so.5 and libncurses.so.6), but then again, it does not do that for for proprietary programs _either_. Like with libnl-1_1->libnl3, there was a bigger API change in ncurses5->ncurses6.
And it makes a difference if a closed source software needs a library compared to an open source software? Try to see it from the users side. The only goal they have is to get something working. If we're aware of a software requireing a particular library version and it's easy to offer and maintain such a build we should do it. Anything else is going into the dogmatic direction. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Sun, 30 Sep 2012 14:31:10 +0200
Lars Müller
On Sun, Sep 30, 2012 at 12:53:12PM +0200, Jan Engelhardt wrote:
On Sunday 2012-09-30 00:14, Stefan Seyfried wrote: ... it does not do that for for proprietary programs _either_. ... a bigger API change ...
And it makes a difference if a closed source software needs a library compared to an open source software?
Try to see it from the users side. The only goal they have is to get something working. ... Anything else is going into the dogmatic direction.
Combined: * API changes that library authors put in their libraries, * number of software titles we have, * delay library users need to fix their software, * timing to our release, it is actually miracle that anything works. Adding on top of that dogmatic requirements doesn't make easier for that miracle to happen. Besides, it is not only users, but also independent software vendors that need stable API to create version for Linux. Some software will never see open source counterpart. Classic example is tax software where each year it must be updated and validated against current legal requirements and released just in time for tax preparation. The same is valid for accounting software and any other that deals with matters that are legally regulated. User can be forgivable if software doesn't render his picture properly, but not when he is exposed to legal problems and expenses. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Sep 30, 2012 at 9:31 AM, Lars Müller
Yes, you can turn on libjpeg.so.62 generation in jpeg-turbo; ncurses does something similar (producing both libncurses.so.5 and libncurses.so.6), but then again, it does not do that for for proprietary programs _either_. Like with libnl-1_1->libnl3, there was a bigger API change in ncurses5->ncurses6.
And it makes a difference if a closed source software needs a library compared to an open source software?
Try to see it from the users side. The only goal they have is to get something working.
If we're aware of a software requireing a particular library version and it's easy to offer and maintain such a build we should do it.
Anything else is going into the dogmatic direction.
Cheers,
Well, that's why I checked upstream's changelog, and I don't see any ABI-breaking changes mentioned. There could still be some, so someone with access to such third-party software depending on libjpeg should try and report the results. There's a high probability that it could still be supported with relative ease. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2012-09-30 17:11, Claudio Freire wrote:
[libjpeg] Well, that's why I checked upstream's changelog, and I don't see any ABI-breaking changes mentioned. There could still be some,
It's pretty clear-cut. For example, jpeg8 ABI has h and v scaled sizes, while jpeg6 ABI only has one member: diff -dpru jpeg6/jpeglib.h jpeg8(-turbo)/jpeglib.h --- jpeg6/jpeglib.h 2012-08-15 13:19:13.000000000 +0200 +++ jpeg8/jpeglib.h 2012-07-26 12:00:24.000000000 +0200 @@ -140,23 +147,18 @@ typedef struct { */ JDIMENSION width_in_blocks; JDIMENSION height_in_blocks; - /* Size of a DCT block in samples. Always DCTSIZE for compression. - * For decompression this is the size of the output from one DCT block, - * reflecting any scaling we choose to apply during the IDCT step. - * Values of 1,2,4,8 are likely to be supported. Note that different - * components may receive different IDCT scalings. + /* Size of a DCT block in samples, + * reflecting any scaling we choose to apply during the DCT step. + * Values from 1 to 16 are supported. + * Note that different components may receive different DCT scalings. */ -#if JPEG_LIB_VERSION >= 70 int DCT_h_scaled_size; int DCT_v_scaled_size; -#else - int DCT_scaled_size; -#endif /* The downsampled dimensions are the component's actual, unpadded number - * of samples at the main buffer (preprocessing/compression interface), thus - * downsampled_width = ceil(image_width * Hi/Hmax) - * and similarly for height. For decompression, IDCT scaling is included, so - * downsampled_width = ceil(image_width * Hi/Hmax * DCT_[h_]scaled_size/DCTSIZE) + * of samples at the main buffer (preprocessing/compression interface); + * DCT scaling is included, so + * downsampled_width = ceil(image_width * Hi/Hmax * DCT_h_scaled_size/DCTSIZE) + * and similarly for height. */ JDIMENSION downsampled_width; /* actual width in samples */ JDIMENSION downsampled_height; /* actual height in samples */ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Sep 30, 2012 at 12:44 PM, Jan Engelhardt
On Sunday 2012-09-30 17:11, Claudio Freire wrote:
[libjpeg] Well, that's why I checked upstream's changelog, and I don't see any ABI-breaking changes mentioned. There could still be some,
It's pretty clear-cut. For example, jpeg8 ABI has h and v scaled sizes, while jpeg6 ABI only has one member:
Ok, so the OBS package would have to be linked and a new specfile generated that sets LIB_JPEG_VERSION=62. Which means maintaining two specfiles. I guess it's up to the maintainers to say if it's worth it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2012-09-30 17:52, Claudio Freire wrote:
On Sun, Sep 30, 2012 at 12:44 PM, Jan Engelhardt
wrote: On Sunday 2012-09-30 17:11, Claudio Freire wrote:
[libjpeg] Well, that's why I checked upstream's changelog, and I don't see any ABI-breaking changes mentioned. There could still be some,
It's pretty clear-cut. For example, jpeg8 ABI has h and v scaled sizes, while jpeg6 ABI only has one member:
Ok, so the OBS package would have to be linked and a new specfile generated that sets LIB_JPEG_VERSION=62. Which means maintaining two specfiles.
As has been said elsewhere in this thread earlier: the libjpeg-turbo(-1.2.1) source can generate headers & libraries for ABI v6, v7 and v8, by running configure+install multiple times from the same tarball. The ABI however, naturally, is different. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Sep 29, 2012 at 3:20 PM, Stefan Seyfried
If they're *that* compatible... why care?
They are compatible on source level, but not binary compatible.
So? OBS rebuilds everything in the distribution from source.
There's more to "working stuff" than what's available from OBS.
Ok, but... are they actually incompatible? Because I cannot se anything in the changelog that would suggest that, that package was providing 62 before the update, and not anymore after the update. Who's to say it was really needed and not an oversight? Maybe check it out? (grab the binary, name it 62 and find out if any of those programs you mention break). In fact, upstream's changelog[0] seems to suggest they worked to maintain compatibility for libjpeg7 (not sure 62, they didn't mention breaking it anyway) [0] http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/tags/1.2.0/ChangeLog.txt?revision=862&view=markup -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Brian K. White
-
Claudio Freire
-
Cristian Morales Vega
-
Cristian Rodríguez
-
Jan Engelhardt
-
Lars Müller
-
Rajko
-
Stefan Seyfried