Am Dienstag, den 09.05.2017, 07:25 +0000 schrieb Nico Schlömer:
> Btw I'm on a stable connection. If you let me know what to do
> exactly, I'll be happy to open up a fresh vtk7 repo.
I've now created an empty vtk7 repository on git.debian.org using the
git/debian/science/setup-repository
script, the path is
git.debian.org/git/debian-science/packages/vtk7.git/
You can clone this repo, and add the VTK 7 source code normally and
copy over the vtk6/debian directory, add them to git, and push.
Rolling back vtk6 could be a bit more difficult. You can try to re-base
to the last commit Anton made, and then force-push the result.
A different approach would be to checkout Anton's last commit as a new
branch vtk6 and then make this branch master. [1]
In both cases this probably means that we have to do a fresh clone to
get our local copies into a sane state.
[1] https://stackoverflow.com/questions/30105210/git-overwrite-master-w
ith-branch
> > It failed to build from source when using the system-provided
> > packages (but I didn't save the error messages). Should I put that
> > in the changelog?
This should be okay for now. It would be even better to have a bug
report for each failure though :)
> After we have a first version of vtk7 in, we can work on
> readjusting it for the system packages perhaps.
That sounds reasonable. I think it would also be okay to already upload
what you did to experimental (after moving to the new git repo).
Best,
Gert
> >
> > Cheers,
> > Nico
> >
> > On Tue, May 9, 2017 at 8:59 AM Gert Wollny <gw.fossdev@gmail.com>
> > wrote:
> > > Hi,
> > >
> > > Am Montag, den 08.05.2017, 16:52 +0000 schrieb Nico Schlömer:
> > > > Alright, excellent, so we all agree to put it in a new repo.
> > > >
> > > > Would anyone open one and import the VTK7 from the vtk6 repo?
> > > I'll do it, but currently I'm on a volume limited Internet
> > > connection
> > > (this should change in a few days), so it will take a few days
> > > until I
> > > can implement it.
> > >
> > > BTW: Nico I, ve seen that you changed back to not using system-
> > > provided
> > > versions for GL2P, LIBPROJ4, and GLEW. Could you be a bit more
> > > specific in the changelog about why you did this?
> > >
> > > Many thanks,
> > > Gert
> > >
> > > >
> > > > Cheers,
> > > > Nico
> > > >
> > > > On Mon, May 8, 2017 at 6:47 PM Anton Gladky <gladk@debian.org>
> > > wrote:
> > > > > Hi Nico, I was not quite explicit. I meant to have in a
> > > separate
> > > > > branch.
> > > > > But it is not so critical.
> > > > >
> > > > > Regards
> > > > >
> > > > > Anton
> > > > >
> > > > >
> > > > > 2017-05-08 18:28 GMT+02:00 Nico Schlömer <nico.schloemer@gmai
> > > l.com>
> > > > > :
> > > > > > Thanks Gert for the comment.
> > > > > >
> > > > > > I committed it to the vtk6 repo after consulting with the
> > > Anton,
> > > > > see [1].
> > > > > >
> > > > > > Cheers,
> > > > > > Nico
> > > > > >
> > > > > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=0;bug
> > > =81025
> > > > > 4;msg=45
> > > > > >
> > > > > > On Mon, May 8, 2017 at 6:24 PM Gert Wollny <gw.fossdev@gmai
> > > l.com>
> > > > > wrote:
> > > > > >>
> > > > > >> Hello Nico,
> > > > > >>
> > > > > >> I've seen that you have started packaging vtk 7.1 within
> > > the
> > > > > vtk6 tree,
> > > > > >> effectively targeting at replacing vtk 6.3.
> > > > > >>
> > > > > >> Please don't do this, we might have to package vtk-6.3 and
> > > vtk-
> > > > > 7.1 in
> > > > > >> parallel (at least for some time). For further details see
> > > > > >>
> > > > > >> https://lists.debian.org/debian-science/2017/04/msg00009
> > > .html
> > > > > >>
> > > > > >> So just like we did with vtk6 vs. vtk5 at least I would
> > > prefer
> > > > > to
> > > > > >> package vtk7 in a separate repository.
> > > > > >>
> > > > > >> Many thanks,
> > > > > >> Gert
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > >