Opened 11 years ago

Closed 11 years ago

Last modified 10 years ago

#3765 closed defect (invalid)

Installing libjpeg-turbo-1.2.1 in systems with jpegsrc.v8d breaks jpeg

Reported by: Fernando de Oliveira Owned by: Randy McMurchy
Priority: normal Milestone:
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

Confirmed by Ken and Fernando.

Change History (10)

comment:1 by Armin K, 11 years ago

We don't claim to support such setup. I don't know even what to do. Book has only libjpeg-turbo and everything works if you follow the book. Not sure if we want to support upgrades which LFS doesn't recommend.

comment:2 by Fernando de Oliveira, 11 years ago

That was also my understanding, at first. So, it took a while for me to solve that, but I did not want to bother others (and most particularly, you) with that, and did not wrote about that until Ken asked. However, the book supported jpegsrc.v8d, if I remember correctly, so, users of the book got jpeg broken when the replacement took effect. Usually, distros have instructions/procedures to prevent this to happen, many examples in Arch and Gentoo.

Everybody knows your great work and level, so what I write in the following is not by any means a criticism.

I also understand you not being sure about what to do, as you did not have the problem (how did you do it, have always used the -turbo version?). One thing I thought, if you have a development only system, perhaps you could break it and solve the problem, probably in the lines described by Bruce and Ken, an then add what you did to fix?

I am not an editor, so I cannot do it myself. You know I would like to be in the level of being a developer, you even told me to do so, once, so I could help editing the book, instead of bothering you all, asking things. But the one time I tried to, I failed. It was with a seamonkey update and Bruce corrected me, but I really did not understand Bruce's last reply to me and did not know what I needed to change in order to generate a useful update diff. If I could be instructed, I would be happy to keep some pages that are always delayed, e.g., mozilla packages and OpenJDK, which take relatively a lot more time and space than others, so to be hated to maintain, probably, by all developers.

comment:3 by Armin K, 11 years ago

Well, we are speaking of upgrade, and no upgrade can be done cleanly without previously removing old version.

I assume that user knows what he's doing - and I assure you, instructions in the book work very well. I am not sure if we should cover all possible mistakes that user can make.

Randy, Bruce, Ken, Thomas, what do you say?

comment:4 by Fernando de Oliveira, 11 years ago

Thanks Armin.

I know what I write in the following (with much respect) will not change anything.

It was not an upgrade, it was a replacement.

So, you are implying users Ken and Fernando did not know what they were doing. Instructions are good, if due to this package one discards present installation and do a new one from scratch from LFS to begin with.

You never replied what you did that you have not found this problem.

Bruce seems to have not included in his box the replacement but he seems to not liking upgrades.

You ask Randy, Bruce, Ken, Thomas, but notice that Ken has already written about it.

Thanks again, Armin, to bother replying to previous comment by me, Fernando. I still like very much your work. Please, close the ticket.

comment:5 by Armin K, 11 years ago

I never had such problem because I removed libjpeg v8d first, and then installed libjpeg-turbo. From instructions, you can see that libjpeg-turbo is more of a upgrade than a replacement since it provides everything that libjpeg v8d did, plus some extra features - an extra executable tjbench and an extra shared library libturbojpeg.so

comment:6 by Fernando de Oliveira, 11 years ago

Thanks again, for the comment and for not having closed this yet.

You could add just one line for the book and then close this ticket as fixed. I believe such kind of comment is already in use by some(s) package(s). In your comment: "...I removed libjpeg v8d first, and then installed libjpeg-turbo...". Just drop the subject "I" and change tense from past to imperative (or is it present or infinitive?). This could be added just as a sentence or a note. Perhaps, starting by "to avoid possible problem, ...":

"If it is already installed, to avoid problems, remove libjpeg v8d first, and then install libjpeg-turbo".

Again, sorry for the trouble.

comment:7 by Randy McMurchy, 11 years ago

Owner: changed from blfs-book@… to Randy McMurchy
Status: newassigned

I have the non-turbo version of libjpeg installed. I have package management and log files for every file installed on my system. I can provide the simple commands that it takes to remove the old version of libjpeg before starting with the turbo update.

I agree that the old version MUST be removed. I will add instructions to the new turbo libjpeg page. It will be simple.

comment:8 by Randy McMurchy, 11 years ago

I'm on this one. I just removed libjpeg and installed libjpeg-turbo. I will update the book to include removing files installed by libjpeg. It's all good!

comment:9 by Armin K, 11 years ago

Resolution: invalid
Status: assignedclosed

Long time has been passed and everyone who builds software regulary should've got libjpeg-turbo without the need to upgrade from ijg libjpeg. Closing as invalid.

comment:10 by bdubbs@…, 10 years ago

Milestone: current

Milestone current deleted

Note: See TracTickets for help on using tickets.