Bug#612341: bumblebee, libjpeg-turbo: Wheezy does not work well with modern notebook PCs.
- To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
- Cc: Osamu Aoki <osamu@debian.org>, Fathi Boudra <fabo@debian.org>, 612341@bugs.debian.org, Mathieu Malaterre <malat@debian.org>, Ivan Baldo <ibaldo@adinet.com.uy>, Igor Urazov <z0rc3r@gmail.com>, ballombe@debian.org, Matthias Klose <doko@debian.org>
- Subject: Bug#612341: bumblebee, libjpeg-turbo: Wheezy does not work well with modern notebook PCs.
- From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
- Date: Sun, 3 Jun 2012 11:32:47 +0200
- Message-id: <[🔎] 20120603093247.GB11764@yellowpig>
- Reply-to: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>, 612341@bugs.debian.org
- In-reply-to: <[🔎] 20120603105113.13784ro2nb9pwm81@mail.das-netzwerkteam.de>
- References: <20120526151102.GA9031@localhost> <20120526183146.629042o05hljl8j6@mail.das-netzwerkteam.de> <20120526183439.GA20618@localhost> <CANZTuJrSt5vD1Mo+Js80CoiQL1LSD25J34nihiAA7sB9S8ggmA@mail.gmail.com> <20120531135528.GA13369@localhost> <20120531235019.1766255mbykfuie3@mail.das-netzwerkteam.de> <[🔎] 20120601145754.GA21617@localhost> <[🔎] 1338613131.1455.8.camel@Nokia-N900> <[🔎] 20120602185310.GA6095@localhost> <[🔎] 20120603105113.13784ro2nb9pwm81@mail.das-netzwerkteam.de>
On Sun, Jun 03, 2012 at 10:51:13AM +0200, Mike Gabriel wrote:
> Hi Osamu, hi all,
>
> On Sa 02 Jun 2012 20:53:10 CEST Osamu Aoki wrote:
>
> >Hi,
> >
> >On Sat, Jun 02, 2012 at 06:58:51AM +0200, Mike Gabriel wrote:
> >>Hi Osamu,
> >>
> >>> Hi,
> >>>
> >>> On Thu, May 31, 2012 at 11:50:19PM +0200, Mike Gabriel wrote:
> >>> ...
> >>> > you may want to have a very little bit more history... (and a
> >>> > packaging folder)
> >>> > http://code.x2go.org/gitweb?p=libjpeg-turbo.git;a=summary
> >>>
> >>> This is one of them. Ubuntu package history is another one.
> >>
> >>Sure.
> >>
> >>> > We would have to import latest upstream on top of that
> >>>
> >>> Well, unless we all agree to reset git repo, this is impossible to do. I
> >>> like to do it....
> >>
> >>+1 from me. However, as Fathi is ITP holder, he may have the last word.
> >
> >I know. But it is easy to have another repo with everything :-)
> >Alioth can host it:
> >
> > http://anonscm.debian.org/gitweb/?p=users/osamu/libjpeg-turbo.git
> >
> >I see you had some revert implimented. Some package splits are a bit
> >different. You get better picture from gitk screen.
>
> Looks good to me. I have cloned a working copy where I can write to
> on my own git server (and already did some work):
> http://code.das-netzwerkteam.de/gitweb?p=debian/libjpeg-turbo.git;a=summary
>
> >>@Fathi: will the above named vcs on code.x2go.org work for you as
> >>starting point? Osamu could clone that on collab-maint. Are you ok
> >>with co- aintenance? Shall we create a team-context for maintenance?
> >>One possibility could be that we place the development of the LJT
> >>package under the roof of the pkx-x2go-devel@a.l.d.o packaging
> >>team(easy for me :-) ). Any other context is fine as well.
> >
> >I an with you.
>
> Fathi? There also is a pkg-tigervnc project on Alioth, that would be
> an even better context, I guess.
>
> >>> So we need to make the assignment of works who does what.
> >>
> >>Once Fathi gave his go, I will be happy to extract the diversion
> >>stuff from the library stuff.
> >>
> >>> I can help general simple packaging based on Ubuntu work but I can not
> >>> be competent on complicated library packaging with ABI compatibility
> >>> etc.
> >>
> >>I guess the QA has to be done by Fathi, Doko or someone with similar
> >>experience. However, we can give them our work and together the
> >>package may evolve.
> >
> >Yes.
> >
> >As I read the source, I can see why Independent JPEG Group is bitter.
> >
> >Modified file by non-IJG people are identifies as if they were done by
> >IJG people. I am sure it is upsetting when code is broken from IJG
> >people's view. I think no malice but just sloppiness ...
>
> Not getting what you mean exactly here. Can anything be done about
> it? Anything that we can do?
I assume that Osamu refer to this line of the IJG license:
(1) If any part of the source code for this software is distributed, then this
README file must be included, with this copyright and no-warranty notice
unaltered; and any additions, deletions, or changes to the original files
must be clearly indicated in accompanying documentation.
For example, when I released libjpeg 6b1, I added a file README.6b1
with the complete list of modified files (in attachment).
(I am not especially fond of this requirement, but it is not really onerous).
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Extra README for release 6b1 of 1-Jun-2010
==========================================
This release is identical to release 6b with the exception of the build system,
and of library symbols versioning on platforms that support them. This release
is only intended as a transition help toward the upgrade to libjpeg8. If you
can upgrade directly to libjpeg8, you do not need libjpeg6b1.
This release was prepared by Bill Allombert <ballombe@debian.org> from release
6b and the build system of release 8 by Guido Vollbeding and Bob Friesenhahn.
Files changed:
config.guess (updated from automake)
config.sub (updated from automake)
configure (autogenerated)
ltmain.sh (updated from libtool)
Files added:
aclocal.m4 (from libjpeg8)
configure.ac (from libjpeg8)
depcomp (from automake)
libjpeg.map (from libjpeg8, modified)
Makefile.am (from libjpeg8, modified)
Makefile.in (autogenerated)
missing (from automake)
README.6b1 (this file)
File removed:
ltconfig (obsoleted)
Reply to: