Hi,
On Sun, Apr 23, 2017 at 12:08:57AM +0200, Andreas Tille wrote:
> On Sat, Apr 22, 2017 at 12:09:00PM +, Ximin Luo wrote:
> > >> So, you could try to build the version currently in sid, against sid. If
> > >> it FTBFS you can file an RC bug and force the maintainer to fix it. :p
> > >
> >
On Sat, Apr 22, 2017 at 12:09:00PM +, Ximin Luo wrote:
> >> So, you could try to build the version currently in sid, against sid. If
> >> it FTBFS you can file an RC bug and force the maintainer to fix it. :p
> >
> > I admit I do not understand this hint, sorry.
>
> If you look at the "Logs"
Andreas Tille:
> [..]
>
>> I notice also that the maintainer uploaded the arch:all packages to sid, so
>> the buildds didn't attempt this build that you're doing:
>>
>> https://buildd.debian.org/status/package.php?p=matplotlib
>>
>> So, you could try to build the version currently in sid, agains
Hi Ximin,
On Fri, Apr 21, 2017 at 07:24:00AM +, Ximin Luo wrote:
> >
> > /build/matplotlib-2.0.0+dfsg1/doc# find . -name "*MarkerStyle*"
> > /build/matplotlib-2.0.0+dfsg1/doc# grep -R
> > matplotlib.markers.MarkerStyle.markers
> > Binary file build/doctrees/api/markers_api.doctree matches
>
On Fri, Apr 21, 2017 at 08:28:58PM +, Patrick Hastings wrote:
> Based on the message received, it seems as though the warning is interpreted
> as an error during runtime. I believe because it is treated the warning is
> treated as an error, it would cause a failure to build.
>
> In some code
Hi Micha,
On Fri, Apr 21, 2017 at 10:02:07PM +0200, Micha Lenk wrote:
> > I'm not sure why it's failing, I thought maybe you need to backport sphinx
> > but it's already backported.
>
> The existence of a backport doesn't mean that it is automatically being
> used when building a backport of ano
Good Afternoon,
Forgive me if this is overstepping my boundary. Mailing list says posting is
allowed by all.
> Warning, treated as error:
> I can confirm that the missing file does not exist inside the source
Based on the message received, it seems as though the warning is interpreted as
an er
Hi Ximin,
Am 21.04.2017 um 09:24 schrieb Ximin Luo:
> I'm not sure why it's failing, I thought maybe you need to backport sphinx
> but it's already backported.
The existence of a backport doesn't mean that it is automatically being
used when building a backport of another package. Do the build
d
Andreas Tille:
> [..]
>
> However, now when really trying to build matplotlib the build ends up
> with
>
> ...
> generating thumbnails... [ 98%]
> build/plot_directive/mpl_examples/pylab_examples/demo_ribbon_box.png
> generating thumbnails... [ 99%]
> build/plot_directive/mpl_examples/api/bbox_
Hi Ximin,
On Tue, Apr 18, 2017 at 03:15:00PM +, Ximin Luo wrote:
> Ah, I didn't realise it would be this hard. You could try backporting 1.5
> instead of 2.0, that is what Sage themselves are using:
>
> https://people.debian.org/~thansen/debian-sage-7.4-status.html (see the
> matplotlib row
Ah, I didn't realise it would be this hard. You could try backporting 1.5
instead of 2.0, that is what Sage themselves are using:
https://people.debian.org/~thansen/debian-sage-7.4-status.html (see the
matplotlib row)
If that is not allowed by backports policy, I'm not sure of the best way
for
Hi,
my continuous attempt to backport now also seems to require
matplotlib (and its dependency which are not yet in Jessie).
Kind regards
Andreas.
- Forwarded message from Ximin Luo -
Date: Mon, 17 Apr 2017 22:01:00 +
From: Ximin Luo
To: Development issues of sagemath and rel
12 matches
Mail list logo
