Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for the following package:
* Package name: xtensor
Version : 0.10.1-1
Upstream Author : Johan Mabille and Sylvain Corlay
* URL : http://quantstack.net/xtensor
* License : B
Andreas Tille wrote:
> the gviz package received a bug report about trying to access a remote
> location at package build time which is forbidden by Debian policy.
[…]
> Do you have any hints how this access could be prevented?
Just in case it helps, in other packages I've seen that exporting an
Hi,
the gviz package received a bug report about trying to access a remote
location at package build time which is forbidden by Debian policy.
I wonder if there is an easy way to prevent this. Due to so called
Build-Depends it is granted that biocinstaller code is installed on
the building machi
Very nice.
As far as I can tell, everything is cleaned up now to the point where vtk7
could be uploaded to experimental.
Cheers,
Nico
On Tue, May 9, 2017 at 2:55 PM Gert Wollny wrote:
>
> > >I've also sanitized the vtk6 repo; as Gert pointed out, you'll
> > probably need a fresh clone.
>
> Act
On 9 May 2017 at 14:57, Andreas Tille wrote:
| Hi Chris,
|
| On Sun, May 07, 2017 at 06:06:10PM +0100, Chris Lamb wrote:
| >
| > Whilst r-bioc-gviz builds successfully on unstable/amd64, according to
| > Debian Policy 4.9 packages may not attempt network access during
| > a build.
| >
| >00
> >I've also sanitized the vtk6 repo; as Gert pointed out, you'll
> probably need a fresh clone.
Actually a
git rebase -i HEAD^^^
and dropping the last patches should suffice.
Best,
Gert
Hi Chris,
On Sun, May 07, 2017 at 06:06:10PM +0100, Chris Lamb wrote:
>
> Whilst r-bioc-gviz builds successfully on unstable/amd64, according to
> Debian Policy 4.9 packages may not attempt network access during
> a build.
>
>00:00:00.00 IP 5f02d4499efa.36140 > dns.z9.domain: 4778+ A?
>
Alright, I've pushed it all to vtk7; check it out with
```
git clone https://anonscm.debian.org/git/debian-science/packages/vtk7.git
```
I've also sanitized the vtk6 repo; as Gert pointed out, you'll probably
need a fresh clone.
> That sounds reasonable. I think it would also be okay to already up
Am Dienstag, den 09.05.2017, 07:25 + 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
sc
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.
Cheers,
Nico
On Tue, May 9, 2017 at 9:24 AM Nico Schlömer
wrote:
> > BTW: Nico I, ve seen that you changed back to not using system-provided
> > versions for GL2P, LIBPROJ4, and G
> 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?
It failed to build from source when using the system-provided packages (but
I didn't save the error messag
Hi,
Am Montag, den 08.05.2017, 16:52 + 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 da
12 matches
Mail list logo