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?
Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgplhZgw2njuV.pgp
Description: Digitale PGP-Unterschrift
