On Fri, Sep 2, 2011 at 7:42 PM, Mathieu Malaterre
wrote:
> vtk 5.8 has been uploaded to my public space on vasks:
>
> https://alioth.debian.org/~malat-guest/vtk/
>
> I could not push to mentors for some reason. This is a /minimal/
> package, I did not turn any new option on, this should only serve
On Thu, Sep 1, 2011 at 10:58 AM, Mathieu Malaterre
wrote:
> On Mon, Aug 29, 2011 at 2:43 PM, Sylvestre Ledru wrote:
>> Le lundi 29 août 2011 à 13:31 +0100, Alastair McKinstry a écrit :
>>> On 2011-08-29 07:14, Mathieu Malaterre wrote:
>>> > On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbins wrote
On Thu, Sep 01, 2011 at 10:58:33AM +0200, Mathieu Malaterre wrote:
> Meanwhile could someone please NMU vtk-5.6 with the proper
> fix and fix for lintian.
I will do an NMU that overrides the lintian errors, which will unblock
VTK and give us time to properly deal with the embedded libraries.
-St
On Mon, Aug 29, 2011 at 2:43 PM, Sylvestre Ledru wrote:
> Le lundi 29 août 2011 à 13:31 +0100, Alastair McKinstry a écrit :
>> On 2011-08-29 07:14, Mathieu Malaterre wrote:
>> > On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbins wrote:
>> >> I think the rest of this thread got off onto a tangent.
Hi,
I see that as maintainer of VTK you were not on the CC: list, so I'm
forwarding this email
to you directly: do you think it would be much work to build an
experimental vtk5.8 package?
regards
Alastair McKinstry
Original Message
Subject: Re: Bug#637397: Pos
Le lundi 29 août 2011 à 13:31 +0100, Alastair McKinstry a écrit :
> On 2011-08-29 07:14, Mathieu Malaterre wrote:
> > On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbins wrote:
> >> I think the rest of this thread got off onto a tangent. In my mind,
> >> the germane question is not why Paraview emb
On 2011-08-29 07:14, Mathieu Malaterre wrote:
On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbins wrote:
I think the rest of this thread got off onto a tangent. In my mind,
the germane question is not why Paraview embeds a patched VTK source
tree but, rather: why is the paraview binary package n
On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbins wrote:
> I think the rest of this thread got off onto a tangent. In my mind,
> the germane question is not why Paraview embeds a patched VTK source
> tree but, rather: why is the paraview binary package now installing
> the VTK tools like vtkWrapP
On Sun, Aug 28, 2011 at 08:30:50PM +0200, Sylvestre Ledru wrote:
> Le dimanche 28 août 2011 à 21:23 +0300, Anton Gladky a écrit :
> > Paraview is really not an easy source to package.
> >
> > Now the debian-directory is rewritten almost completely to make the
> > packaging as simple as possible. I
On Sun, Aug 28, 2011 at 05:47:50PM +0200, Sylvestre Ledru wrote:
> > It was tolerated that paraview be build with the convenient VTK
> > library, but now the package are now installing vtk related tools
> > (tools that are already installed by VTK-* package), eg:
I think the rest of this thread
On Sun, Aug 28, 2011 at 21:23:56 +0300, Anton Gladky wrote:
> I prefer to escape "overpatching", because it complicates a
> maintainance.
>
So does having to fix bugs 50 times instead of one because a library is
copied all over the place.
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-bug
Le dimanche 28 août 2011 à 21:23 +0300, Anton Gladky a écrit :
> Paraview is really not an easy source to package.
>
> Now the debian-directory is rewritten almost completely to make the
> packaging as simple as possible. I prefer to escape "overpatching",
> because it complicates a maintainance.
Paraview is really not an easy source to package.
Now the debian-directory is rewritten almost completely to make the
packaging as simple as possible. I prefer to escape "overpatching",
because it complicates a maintainance.
I am afraid, that replacing the vtk is not an easy work. It can
produce
On 2011-08-28 16:47, Sylvestre Ledru wrote:
Le dimanche 28 août 2011 à 17:30 +0200, Mathieu Malaterre a écrit :
On Sat, Aug 27, 2011 at 12:35 PM, Sylvestre Ledru wrote:
Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit :
I see only 2 opportunities to fix it:
1) Disable python-supp
Le dimanche 28 août 2011 à 17:30 +0200, Mathieu Malaterre a écrit :
> On Sat, Aug 27, 2011 at 12:35 PM, Sylvestre Ledru
> wrote:
> > Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit :
> >> I see only 2 opportunities to fix it:
> >> 1) Disable python-support in paraview;
> >> 2) Clai
On Sat, Aug 27, 2011 at 12:35 PM, Sylvestre Ledru wrote:
> Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit :
>> I see only 2 opportunities to fix it:
>> 1) Disable python-support in paraview;
>> 2) Claim, that paraview conflicts with python-vtk;
> 3) get in touch with upstream and a
Your message dated Sun, 28 Aug 2011 13:33:55 +
with message-id
and subject line Bug#637397: fixed in paraview 3.10.1-3
has caused the Debian Bug report #637397,
regarding paraview and python-vtk: error when trying to install together
to be marked as done.
This means that you claim that the
tags 637397 + pending
thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit :
> I see only 2 opportunities to fix it:
> 1) Disable python-support in paraview;
> 2) Claim, that paraview conflicts with python-vtk;
3) get in touch with upstream and ask them to consider changing the name
of the binary.
;)
Sylvestr
I see only 2 opportunities to fix it:
1) Disable python-support in paraview;
2) Claim, that paraview conflicts with python-vtk;
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hello,
when updating my unstable/amd64 system I still get the error:
The following packages will be upgraded:
paraview
The following packages are RECOMMENDED but will NOT be installed:
paraview-python
1 packages upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Need to get 0 B/4
637397 indicates the following issue 'paraview and python-vtk: error
when trying to install together". And this bug is fixed in 3.10.1-2,
maybe by a "brute" way but fixed.
Cleaning paraview from vtk-files is an another issue, so it should be
definitely another bug not to mix the problems. I do not
On Mon, Aug 22, 2011 at 9:21 PM, Anton Gladky wrote:
>> paraview* package should be cleanup from any vtk binaries.
>
> I think, it should be better another M&W-bug, not 637397.
I filled it as serious not minor/wishlist to prevent migration to
testing for that specific purpose.
Why do you think t
> paraview* package should be cleanup from any vtk binaries.
I think, it should be better another M&W-bug, not 637397.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
reopen 637397
thanks
In order to build both gdcm-vtk-python plugin and gdcm-paraview
plugin, gdcm needs both paraview-dev and paraview-python.
paraview* package should be cleanup from any vtk binaries.
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
I would like to add that the CMake/* files belongs to the paraview-dev
package now:
/usr/lib/paraview/CMake/FindMySQL.cmake
/usr/lib/paraview/CMake/FindPythonLibs.cmake
/usr/lib/paraview/CMake/FindTCL.cmake
/usr/lib/paraview/CMake/ParaViewBranding.cmake
/usr/lib/paraview/CMake/ParaViewBrandingCPac
[Top posting]
I believe that this will bites us later on. gdcm can build paraview
plugins (therefore needs paraview-dev), and at the same time can build
gdcm-vtk-python plugins (therefore need vtk-python). Ideally paraview*
packages should not install none of the vtk related stuff. I would
really
Python stuff of Paraview has been moved to paraview-python
binary. And this binary is conflicting with python-vtk.
On 8/18/11, Steve M. Robbins wrote:
> On Wed, Aug 17, 2011 at 07:09:09PM +, Debian Bug Tracking System wrote:
>> This is an automatic notification regarding your Bug report
>>
On Wed, Aug 17, 2011 at 07:09:09PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the python-vtk,paraview package:
>
> #637397: Undeclared conflict with python-vtk
>* [27f6ded] Split paraview into paraview and p
Your message dated Wed, 17 Aug 2011 19:05:26 +
with message-id
and subject line Bug#637397: fixed in paraview 3.10.1-2
has caused the Debian Bug report #637397,
regarding paraview and python-vtk: error when trying to install together
to be marked as done.
This means that you claim that the
tags 637397 + pending
thanks
Anton
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):
/usr/bin/vtkWrapPython
/usr/bin/vtkWrapPythonInit
-Ralf
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subjec
32 matches
Mail list logo
