>> It seems the transition to qt5 is inevitable. Simply holding back to
>> 1.5.3 means it's one year behind and definitely inability to work
>> properly with new devices and the lack of GeoJSON write support
>
> Good point. I'm putting together an update to 1.5.4, and I'll leave a
> note in the
On 6/15/17, Willy Sudiarto Raharjo wrote:
>>> Looks like it's trying to build against Qt5. I've only tested against
>>> Qt4.
>>>
>>> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
>>> since 1.5.4 requires Qt5. Can you try a simple version bump and see
>> Looks like it's trying to build against Qt5. I've only tested against Qt4.
>>
>> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
>> since 1.5.4 requires Qt5. Can you try a simple version bump and see
>> if the errors go away with 1.5.4?
It seems the transition to qt5 is
>> You might want to ping upstream ;-)
>
> Done. Thanks
Love it when our community contribute back to upstream :)
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
> I searched for scripts that require both python-requests and one of its
> four new dependencies. Found these:
>
> (have python-certifi)
> development/jupyter-nbdime
> multimedia/Mopidy
> system/salt
>
> (have python-urllib3)
> libraries/dropbox-python
> network/deis
> system/virt-manager
>
>
On 2017-06-16 00:14:50 +0100, baildon.resea...@googlemail.com wrote:
> [...]
> You might want to ping upstream ;-)
Done. Thanks
signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
On 16/06/17 01:03, Andrew Clemons wrote:
I can reproduce. For me, removing `--verbose` in the call to `x.py
build` allows the build to complete. If that also works for you, I'll
submit an update which this change, although it's not clear to me from
a cursory read of the source why this should
> I can reproduce. For me, removing `--verbose` in the call to `x.py
> build` allows the build to complete. If that also works for you, I'll
> submit an update which this change, although it's not clear to me from
> a cursory read of the source why this should cause it to use the wrong
> path to
On 2017-06-15 20:00:09 +0200, atelszew...@gmail.com wrote:
> Hi,
>
> I'm trying to build rust 1.18.0 with LOCAL_BOOTSTRAP=yes, but the build
> fails with error [1].
>
> I have both previous versions of rust-1.17.0 and cargo-0.18.0 installed
> before building.
>
> Help appreciated :-)
>
> [...]
> I'm trying to build rust 1.18.0 with LOCAL_BOOTSTRAP=yes, but the build
> fails with error [1].
>
> I have both previous versions of rust-1.17.0 and cargo-0.18.0 installed
> before building.
Reproduced both in slackrepo and sbopkg
https://github.com/rust-lang/rust/issues/42543
1.18 doesn't
On Thursday, June 15, 2017 12:19:41 PM PDT Audrius Kažukauskas wrote:
> On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote:
> > Audrius
> > Thanks for spotting that. It build fine without it, so we never notice
> > it. I will add them to python-requests.
>
> I searched for scripts
On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote:
> Audrius
> Thanks for spotting that. It build fine without it, so we never notice
> it. I will add them to python-requests.
I searched for scripts that require both python-requests and one of its
four new dependencies. Found
Hi,
I'm trying to build rust 1.18.0 with LOCAL_BOOTSTRAP=yes, but the build
fails with error [1].
I have both previous versions of rust-1.17.0 and cargo-0.18.0 installed
before building.
Help appreciated :-)
_The contents of config.toml is:_
$ cat config.toml
[build]
vendor = true
rustc
> One small note: your changes to python/idna mangled years on copyright
> line, probably the result of '2.1' regexp where dot here matches any
> character (should have been '2\.1' instead).
Fixed
Thanks again
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote:
> Audrius
> Thanks for spotting that. It build fine without it, so we never notice
> it. I will add them to python-requests.
One small note: your changes to python/idna mangled years on copyright
line, probably the result of
> Willy, these four are actually direct dependencies of python-requests,
> as can be seen in its setup.py. You should add them to python-requests
> REQUIRES instead of letsencrypt.
Audrius
Thanks for spotting that. It build fine without it, so we never notice
it. I will add them to
On Thu, 2017-06-15 at 20:55:37 +0700, Willy Sudiarto Raharjo wrote:
> after further testing, it requires more than python-certifi
> here's what i need to do in order for LE to work again
> - python-certifi (new dep)
> - python-chardet-3.0.4 (new dep and bump new version)
> - idna-2.5 (bump new
> Just to give you some heads-up for letsencrypt users
>
> Due to python-requests bump to 2.17.3, certifi is now a mandatory
> requirement for letsencrypt otherwise, it will complaint with these errors
>
> Traceback (most recent call last):
> File "/usr/bin/letsencrypt", line 5, in
> from
Just to give you some heads-up for letsencrypt users
Due to python-requests bump to 2.17.3, certifi is now a mandatory
requirement for letsencrypt otherwise, it will complaint with these errors
Traceback (most recent call last):
File "/usr/bin/letsencrypt", line 5, in
from pkg_resources
Sorry for the unscheduled updates but we have several update that
contains security fixes on this batch and we think it's important to
have them delivered to you as soon as possible, thus this update is
pushed ahead of my weekend schedule. Some sources were missing and
Matteo (ponce) managed to
20 matches
Mail list logo