Brian May writes:
> Maybe I should have a look at doing the python-slimit and python3-slimit
> split again.
Looks like I don't have commit access to PAPT, so I can't commit my
changes to SVN. How do I get commit access to PAPT?
Thanks
--
Brian May
Raphael Hertzog writes:
> Yeah, skip the test on Python 3, tell upstream that slimit is not
> supported on Python 3 and that the test should be skipped there.
Upstream pipeline seem to think slimit works fine with Python 3:
https://github.com/jazzband/django-pipeline/issues/554#issuecomment-2008
Raphael Hertzog writes:
> Yeah, skip the test on Python 3, tell upstream that slimit is not
> supported on Python 3 and that the test should be skipped there.
Done. https://github.com/jazzband/django-pipeline/issues/554
> Make sure that slimit is not the default.
It wasn't.
However Yuglify wa
On Wed, 23 Mar 2016, Brian May wrote:
> Looks like slimit doesn't support Python3 and hasn't had an upstream
> release since 2013-03-26.
>
> Any suggestions where to go from here?
>
> Maybe hack pipeline to disable the failing test? I think pipeline can be
> configured to use jsmin instead of sli
Raphael Hertzog writes:
> On Wed, 23 Mar 2016, Brian May wrote:
>> I: pybuild base:184: PYTHONPATH=. python3.5 /usr/bin/django-admin test
>> --settings=tests.settings
> ^
>> File "/«PKGBUILDDIR»/pipeline/compressors/slimit.py", line 12, in
>> compre
On Wed, 23 Mar 2016, Brian May wrote:
> I: pybuild base:184: PYTHONPATH=. python3.5 /usr/bin/django-admin test
> --settings=tests.settings
^
> File "/«PKGBUILDDIR»/pipeline/compressors/slimit.py", line 12, in
> compress_js
> from slimit import min
Brian May writes:
> Ok, so now I think I understand, time to test the lastest version of
> pipeline I think. See if that helps.
It fixes the problem. However we get a new problem:
I: pybuild base:184: PYTHONPATH=. python3.5 /usr/bin/django-admin test
--settings=tests.settings
..sssss.
Steve Langasek writes:
> Ok, that was certainly another possibility. "Clean" chroots certainly vary,
> and some ways of building them may include more stuff than others, and some
> of that "more" stuff may be triggering this problem.
Think we were on the wrong track entirely.
If problem occurs
On Wed, Mar 23, 2016 at 09:21:19AM +1100, Brian May wrote:
> Steve Langasek writes:
> > No. I first noticed this bug because the package failed to build in
> > Ubuntu[1], which uses sbuild, not pbuilder. I reproduced the failure in a
> > clean sid schroot. I think either your sbuild environmen
Steve Langasek writes:
> No. I first noticed this bug because the package failed to build in
> Ubuntu[1], which uses sbuild, not pbuilder. I reproduced the failure in a
> clean sid schroot. I think either your sbuild environment is not clean, or
> it is not up-to-date.
Definitely a clean chro
On Tue, Mar 22, 2016 at 09:13:42PM +1100, Brian May wrote:
> Mattia Rizzolo writes:
> > FTR this is also visible in the reproducible CI:
> > https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/django-pipeline.html
> > That's a standard pbuilder instance in a clean chroot.
> > I tried to
Mattia Rizzolo writes:
> FTR this is also visible in the reproducible CI:
> https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/django-pipeline.html
>
> That's a standard pbuilder instance in a clean chroot.
>
> I tried to reproduce it locally and I had the very same failure.
> Though I c
On Tue, Mar 22, 2016 at 05:42:48PM +1100, Brian May wrote:
> I would appreciate help with #818730 for django-pipeline.
>
> The reporter claims the package won't build however I can't reproduce
> any problems myself. Which makes it hard to fix.
FTR this is also visible in the reproducible CI:
http
13 matches
Mail list logo
