On 02/01/17 22:29, Ryan P.C. McQuen wrote:
This would be nearly impossible for some packages. |atom|, for
instance
has hundreds of module dependencies.
OK. That’s a bit of a shame, because it’s against the philosophy we try
to keep here (i.e. SlackBuild shall not
This would be nearly impossible for some packages. |atom|, for instance
has hundreds of module dependencies.
OK. That’s a bit of a shame, because it’s against the philosophy we try
to keep here (i.e. SlackBuild shall not download on its own).
It’s a good philosophy, but it is not practical for a
If the dependencies are properly listed by the package maintainer, and
they're installed prior to trying to install the main package, it obviously
won't need to download any.
But if there is no real option to pass to the build/install process to
prevent downloading additional modules, that's a
On 02/01/17 21:46, Ryan P.C. McQuen wrote:
Do you know if it's possible to disable automatic downloading by the
setup script (on the command line)?
If it is, I think we should apply this rule to SlackBuilds and then
we had the true dependencies ;-)
This would be nearly
> Do you know if it's possible to disable automatic downloading by the setup
> script (on the command line)?
>
> If it is, I think we should apply this rule to SlackBuilds and then we had
> the true dependencies ;-)
>
This would be nearly impossible for some packages. atom, for instance has
Best I could find is modifying the program's setup.cfg and add the
following:
[easy_install]
allow_hosts: None
This doesn't disable attempting to download packages (I couldn't find
anything for that), but it does prevents connections because it, obviously,
doesn't have any allowable hosts.
On
On 02/01/17 18:37, Audrius Kažukauskas wrote:
On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:
Maybe slackrepo does not allow to download something needed by the Python
install script.
I don't know slackrepo well enough, but this seems likely.
But it shouldn't be downloaded
On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:
> Maybe slackrepo does not allow to download something needed by the Python
> install script.
I don't know slackrepo well enough, but this seems likely.
> But it shouldn't be downloaded in the first place.
>
> I don't know enough
>> libraries/chromaprint: Updated for version 1.4.
>
> clementine fails to build here with the following:
Fixed in my branch
Thanks for reporting
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users
On 02/01/17 01:14, Ryan P.C. McQuen wrote:
I tried building the packages by hand (i.e. without any help of any
tool) and it indeed succeeded.
Then I tried again using slackrepo and that's what I get:
Could it be a bug with slackrepo?
If so, then I would say, indirectly.
Maybe slackrepo
> I tried building the packages by hand (i.e. without any help of any
> tool) and it indeed succeeded.
>
> Then I tried again using slackrepo and that's what I get:
Could it be a bug with slackrepo?
--
-Ryan
[ryanpcmcquen.org]
___
SlackBuilds-users
On 01/01/17 00:40, Willy Sudiarto Raharjo wrote:
python/python3: Updated for version 3.6.0.
I'm not entirely sure if the updated Python is the reason for borgbackup
failing to build, but it surely was building before.
Anyways, adding setuptools-scm as requirement for borgbackup allows for
On 31/12/16 03:07, Willy Sudiarto Raharjo wrote:
libraries/chromaprint: Updated for version 1.4.
clementine fails to build here with the following:
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:
In member function 'QString Chromaprinter::CreateFingerprint()':
> And yes, 2 virtualbox's .pdf-s has not correct md5.
I tested the PDFs and they do have the correct MD5 values
md5sum *.pdf
1503b03024f790b2344c4728c27a8e2a SDKRef.pdf
7bb5e3dcfa06bb8ff7d5d7cfc1f80e69 UserManual.pdf
MD5SUM="9ba8ff724dadfb7327dc4c6401afb7a8 \
And yes, 2 virtualbox's .pdf-s has not correct md5.
1 січ. 2017 05:41, користувач Willy Sudiarto Raharjo
написав:
>
> > Unable to download/verify source file(s) for lxml:
> > md5sum failure for
> >/usr/local/poo/usr-sbo-142/distfiles/lxml-lxml-3.7.1.tar.gz.
>
>
> Unable to download/verify source file(s) for lxml:
> md5sum failure for
> /usr/local/poo/usr-sbo-142/distfiles/lxml-lxml-3.7.1.tar.gz.
Fixed already on my branch :)
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
>> python/python3: Updated for version 3.6.0.
>
> I'm not entirely sure if the updated Python is the reason for borgbackup
> failing to build, but it surely was building before.
>
> Anyways, adding setuptools-scm as requirement for borgbackup allows for
> successful build.
>
> So, please add
>> python/lxml: Updated for version 3.7.1
>
> Looks like download has wrong md5.
> Seems it should be e1fd1051aa08437f54d1e18c3b80342b.
Yes, it has been fixed in my branch already :)
--
Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
On 31/12/16 03:07, Willy Sudiarto Raharjo wrote:
python/python3: Updated for version 3.6.0.
I'm not entirely sure if the updated Python is the reason for
borgbackup failing to build, but it surely was building before.
Anyways, adding setuptools-scm as requirement for borgbackup allows for
On 31/12/16 03:07, Willy Sudiarto Raharjo wrote:
python/lxml: Updated for version 3.7.1
Looks like download has wrong md5.
Seems it should be e1fd1051aa08437f54d1e18c3b80342b.
--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
> That's weird. It must be the same issue with content-disposition that I'm
> seeing with transgui when using slackrepo. I'll probably rework both
> scripts to handle things better and submit updated scripts for next week's
> public update.
>
> It seems I either didn't understand how github
> Thanks for your (and all the other SBo admins) work on this and Happy New
> Year. However, I'm hoping you can get out a relatively minor update to fix
> sickrage. It seems during your cleanup, the source versions got screwed up
> and it fails to build. I did a quick fix of it and have the patch
Willy,
Thanks for your (and all the other SBo admins) work on this and Happy New
Year. However, I'm hoping you can get out a relatively minor update to fix
sickrage. It seems during your cleanup, the source versions got screwed up
and it fails to build. I did a quick fix of it and have the patch
23 matches
Mail list logo