Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-03 Thread Andrzej Telszewski

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 download on its own).

It’s a good philosophy, but it is not practical for a tool like
|slackrepo| to block scripts from doing /anything/. The classic Unix way
is to allow the user to shoot themselves in the foot … this is why no
tools are officially endorsed by SBo other than the old fashioned way of
running everything manually. Like I said before, I’d call this a
|slackrepo| issue, and it should be reported to their issue
tracker/mailing list.



Well, no ;-)

I don't blame slackrepo officially, because I don't know where the 
problem really is.


But what I really meant was that it is against SBo philosophy, forget 
about slackrepo (slackrepo just discovered the problem).


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-02 Thread Ryan P.C. McQuen
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 tool like slackrepo
to block scripts from doing *anything*. The classic Unix way is to allow
the user to shoot themselves in the foot … this is why no tools are
officially endorsed by SBo other than the old fashioned way of running
everything manually. Like I said before, I’d call this a slackrepo issue,
and it should be reported to their issue tracker/mailing list.

—
-Ryan
[ryanpcmcquen.org]
​
-- 
--
[ryanpcmcquen.org]
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-02 Thread Jeremy Hansen
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 little frustrating. It's a
nice option for those who like it, but it should be easily disableable.

On Mon, Jan 2, 2017, 4:21 PM Andrzej Telszewski 
wrote:

> 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 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).
>
> --
> Best regards,
> Andrzej Telszewski
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-02 Thread Andrzej Telszewski

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 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).


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-02 Thread Ryan P.C. McQuen
> 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
hundreds of module dependencies.
​


-- 
-Ryan
[ryanpcmcquen.org]
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-02 Thread Jeremy Hansen
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 Mon, Jan 2, 2017, 2:17 PM Andrzej Telszewski 
wrote:

> 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 in the first place.
> >>
> >> I don't know enough about Python installation scripts to say the final
> word.
> >
> > borgbackup's setup.py contains the following line:
> >
> >   setup_requires=['setuptools_scm>=1.7'],
> >
> > Thus setuptools_scm should really be a requirement for borgbackup.
> >
> > setuptools documentation has this description of setup_requires field:
> >
> >   A string or list of strings specifying what other distributions need
> >   to be present in order for the setup script to run.  setuptools will
> >   attempt to obtain these (even going so far as to download them using
> >   EasyInstall) before processing the rest of the setup script or
> >   commands. <...>
> >
> > This explains why the build succeeded for Willy and, if slackrepo does
> > indeed disable network access, why it didn't for you.
> >
>
> Thanks for clarification.
> That is what I was thinking is more or less happening.
>
> 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 ;-)
>
> --
> Best regards,
> Andrzej Telszewski
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-02 Thread Andrzej Telszewski

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 in the first place.

I don't know enough about Python installation scripts to say the final word.


borgbackup's setup.py contains the following line:

  setup_requires=['setuptools_scm>=1.7'],

Thus setuptools_scm should really be a requirement for borgbackup.

setuptools documentation has this description of setup_requires field:

  A string or list of strings specifying what other distributions need
  to be present in order for the setup script to run.  setuptools will
  attempt to obtain these (even going so far as to download them using
  EasyInstall) before processing the rest of the setup script or
  commands. <...>

This explains why the build succeeded for Willy and, if slackrepo does
indeed disable network access, why it didn't for you.



Thanks for clarification.
That is what I was thinking is more or less happening.

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 ;-)


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-02 Thread Audrius Kažukauskas
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 about Python installation scripts to say the final word.

borgbackup's setup.py contains the following line:

  setup_requires=['setuptools_scm>=1.7'],

Thus setuptools_scm should really be a requirement for borgbackup.

setuptools documentation has this description of setup_requires field:

  A string or list of strings specifying what other distributions need
  to be present in order for the setup script to run.  setuptools will
  attempt to obtain these (even going so far as to download them using
  EasyInstall) before processing the rest of the setup script or
  commands. <...>

This explains why the build succeeded for Willy and, if slackrepo does
indeed disable network access, why it didn't for you.

-- 
Audrius Kažukauskas
http://neutrino.lt/


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-01 Thread Willy Sudiarto Raharjo
>> 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 mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-01 Thread Andrzej Telszewski

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 does not allow to download something needed by the 
Python install script.


But it shouldn't be downloaded in the first place.

I don't know enough about Python installation scripts to say the final word.

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-01 Thread Ryan P.C. McQuen
> 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 mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-01 Thread Andrzej Telszewski

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
successful build.

So, please add setuptools-scm to REQUIRES of borgbackup, or wait until I
push an updated version.


All this being said, thanks and happy new year ;-)
See you soon :-)


Well, it's working fine here

msgpack-python:
  MD5SUM check for msgpack-python-0.4.8.tar.gz ... OK
  Building package msgpack-python-0.4.8-x86_64-1_SBo.tgz ... OK
  Installing package msgpack-python-0.4.8-x86_64-1_SBo.tgz ... OK

lz4:
  MD5SUM check for r131.tar.gz ... OK
  Building package lz4-r131-x86_64-1_SBo.tgz ... OK
  Installing package lz4-r131-x86_64-1_SBo.tgz ... OK

python3:
  MD5SUM check for Python-3.6.0.tar.xz ... OK
  Building package python3-3.6.0-x86_64-1_SBo.tgz ... OK
  Installing package python3-3.6.0-x86_64-1_SBo.tgz ... OK

borgbackup:
  MD5SUM check for borgbackup-1.0.7.tar.gz ... OK
  Building package borgbackup-1.0.7-x86_64-1_SBo.tgz ... OK
  Installing package borgbackup-1.0.7-x86_64-1_SBo.tgz ... OK



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:


Download error on https://pypi.python.org/simple/setuptools_scm/: [Errno 
-3] Temporary failure in name resolution -- Some packages may not be found!
Download error on https://pypi.python.org/simple/setuptools-scm/: [Errno 
-3] Temporary failure in name resolution -- Some packages may not be found!

Couldn't find index page for 'setuptools_scm' (maybe misspelled?)
Download error on https://pypi.python.org/simple/: [Errno -3] Temporary 
failure in name resolution -- Some packages may not be found!

No local packages or working download links found for setuptools_scm>=1.7
Traceback (most recent call last):
  File "setup.py", line 278, in 
extras_require=extras_require,
  File "/usr/lib64/python3.6/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
  File "/usr/lib64/python3.6/site-packages/setuptools/dist.py", line 
315, in __init__

self.fetch_build_eggs(attrs['setup_requires'])
  File "/usr/lib64/python3.6/site-packages/setuptools/dist.py", line 
361, in fetch_build_eggs

replace_conflicting=True,
  File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", 
line 850, in resolve

dist = best[req.key] = env.best_match(req, ws, installer)
  File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", 
line 1122, in best_match

return self.obtain(req, installer)
  File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", 
line 1134, in obtain

return installer(requirement)
  File "/usr/lib64/python3.6/site-packages/setuptools/dist.py", line 
429, in fetch_build_egg

return cmd.easy_install(req)
  File 
"/usr/lib64/python3.6/site-packages/setuptools/command/easy_install.py", 
line 659, in easy_install

raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution 
for Requirement.parse('setuptools_scm>=1.7')



I don't know why this error occurs, but anyways, maybe it's a signal 
that setuptools-scm should be actually in the REQUIRES?


Why the hell the install script tries to download anything?

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2017-01-01 Thread Andrzej Telszewski

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()':
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35: 
error: invalid conversion from 'void*' to 'const int16_t* {aka const 
short int*}' [-fpermissive]

data.size() / 2);
   ^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:235:45: note:   initializing argument 2 of 
'int chromaprint_feed(ChromaprintContext*, const int16_t*, int)'
 CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const 
int16_t *data, int size);

 ^
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72: 
error: invalid conversion from 'void**' to 'uint32_t** {aka unsigned 
int**}' [-fpermissive]

   int ret = chromaprint_get_raw_fingerprint(chromaprint, &fprint, &size);
^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:273:45: note:   initializing argument 2 of 
'int chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**, int*)'
 CHROMAPRINT_API int chromaprint_get_raw_fingerprint(ChromaprintContext 
*ctx, uint32_t **fingerprint, int *size);

 ^
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62: 
error: invalid conversion from 'void*' to 'const uint32_t* {aka const 
unsigned int*}' [-fpermissive]

&encoded, &encoded_size, 1);
  ^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:331:45: note:   initializing argument 1 of 
'int chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, 
int*, int)'
 CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t *fp, 
int size, int algorithm, char **encoded_fp, int *encoded_size, int base64);

 ^
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62: 
error: invalid conversion from 'void**' to 'char**' [-fpermissive]

&encoded, &encoded_size, 1);
  ^
In file included from 
/tmp/slackrepo-desktop/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0:
/usr/include/chromaprint.h:331:45: note:   initializing argument 4 of 
'int chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, 
int*, int)'
 CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t *fp, 
int size, int algorithm, char **encoded_fp, int *encoded_size, int base64);

 ^
At global scope:
cc1plus: error: unrecognized command line option 
'-Wno-unknown-warning-option' [-Werror]
cc1plus: error: unrecognized command line option 
'-Wno-unused-private-field' [-Werror]

cc1plus: all warnings being treated as errors
src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target 
'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o' failed
make[2]: *** 
[src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o] Error 1

make[2]: *** Waiting for unfinished jobs
CMakeFiles/Makefile2:1071: recipe for target 
'src/CMakeFiles/clementine_lib.dir/all' failed

make[1]: *** [src/CMakeFiles/clementine_lib.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread Willy Sudiarto Raharjo
> 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 \
b484878eaafcf6b62b3a290a28495e56 \
->  7bb5e3dcfa06bb8ff7d5d7cfc1f80e69 \
->  1503b03024f790b2344c4728c27a8e2a"


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread Reedych
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. 
>
> Fixed already on my branch :) 
>
>
> -- 
> Willy Sudiarto Raharjo 
>
> ___ 
> SlackBuilds-users mailing list 
> SlackBuilds-users@slackbuilds.org 
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users 
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ 
> FAQ - https://slackbuilds.org/faq/ 
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread 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.

Fixed already on my branch :)


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread Willy Sudiarto Raharjo
>> 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 setuptools-scm to REQUIRES of borgbackup, or wait until I
> push an updated version.
> 
> 
> All this being said, thanks and happy new year ;-)
> See you soon :-)

Well, it's working fine here

msgpack-python:
  MD5SUM check for msgpack-python-0.4.8.tar.gz ... OK
  Building package msgpack-python-0.4.8-x86_64-1_SBo.tgz ... OK
  Installing package msgpack-python-0.4.8-x86_64-1_SBo.tgz ... OK

lz4:
  MD5SUM check for r131.tar.gz ... OK
  Building package lz4-r131-x86_64-1_SBo.tgz ... OK
  Installing package lz4-r131-x86_64-1_SBo.tgz ... OK

python3:
  MD5SUM check for Python-3.6.0.tar.xz ... OK
  Building package python3-3.6.0-x86_64-1_SBo.tgz ... OK
  Installing package python3-3.6.0-x86_64-1_SBo.tgz ... OK

borgbackup:
  MD5SUM check for borgbackup-1.0.7.tar.gz ... OK
  Building package borgbackup-1.0.7-x86_64-1_SBo.tgz ... OK
  Installing package borgbackup-1.0.7-x86_64-1_SBo.tgz ... OK



-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread Willy Sudiarto Raharjo
>> 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
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread Jim Diamond
On Sat, Dec 31, 2016 at 09:07 (+0700), Willy Sudiarto Raharjo wrote:

> Hi folks,

> this is the last public update in 2016!!

> python/lxml: Updated for version 3.7.1

% sboupgrade lxml
...
lxml-lxml-3.7.1.tar 100%[===>] 903.51K  4.79MB/sin 0.2s

2016-12-31 12:58:38 (4.79 MB/s) - ‘lxml-lxml-3.7.1.tar.gz’ saved [925193/925193]

--2016-12-31 12:58:38--  
ftp://slackware.uk/sbosrcarch/by-md5/1/f/1fd1051aa08437f54d1e18c3b80342b/lxml-lxml-3.7.1.tar.gz
   => ‘lxml-lxml-3.7.1.tar.gz’
Resolving slackware.uk (slackware.uk)... 91.109.244.240
Connecting to slackware.uk (slackware.uk)|91.109.244.240|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) 
/sbosrcarch/by-md5/1/f/1fd1051aa08437f54d1e18c3b80342b ... 
No such directory ‘sbosrcarch/by-md5/1/f/1fd1051aa08437f54d1e18c3b80342b’.

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.

Cheers.

And Happy New Year to all.

Jim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread Andrzej Telszewski

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 
successful build.


So, please add setuptools-scm to REQUIRES of borgbackup, or wait until I 
push an updated version.



All this being said, thanks and happy new year ;-)
See you soon :-)

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-31 Thread Andrzej Telszewski

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
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-30 Thread Willy Sudiarto Raharjo
> 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 handles their releases or
> they've recently changed something. I was under the impression that you
> could title the file anything after the version number, but it seems that
> only works now without content-dispassion (eg using wget)... if you use a
> browser or wget with --content-disposition option, it replaces the name
> with the repo name.
> 
> https://github.com/leonsoft-kras/transmisson-remote-gui/archive/v5.5.0/transgui-5.5.0.tar.gz
> 
> From plain wget, you get transgui-5.5.0.tar.gz.
> 
> But from the browser or wget --content-disposition, you get
> transmisson-remote-gui-5.5.0.tar.gz.
> 
> I guess that's what I get for changing names and/or version numbers to make
> things easier for me. I'll have fixed scripts submitted within a day or two
> that will handle it properly.

I think you can use
https://github.com/leonsoft-kras/transmisson-remote-gui/archive/v5.5.0/transmisson-remote-gui-5.5.0.tar.gz

tested on browser and plain wget it resulted as a
transmisson-remote-gui-5.5.0.tar.gz


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-30 Thread Jeremy Hansen
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 handles their releases or
they've recently changed something. I was under the impression that you
could title the file anything after the version number, but it seems that
only works now without content-dispassion (eg using wget)... if you use a
browser or wget with --content-disposition option, it replaces the name
with the repo name.

https://github.com/leonsoft-kras/transmisson-remote-gui/archive/v5.5.0/transgui-5.5.0.tar.gz

>From plain wget, you get transgui-5.5.0.tar.gz.

But from the browser or wget --content-disposition, you get
transmisson-remote-gui-5.5.0.tar.gz.

I guess that's what I get for changing names and/or version numbers to make
things easier for me. I'll have fixed scripts submitted within a day or two
that will handle it properly.

Thanks again

On Fri, Dec 30, 2016, 11:47 PM Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > 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 below.
>
> Hi Jeremy
>
> it builds fine here (tested just now using sbopkg)
>
> sickrage:
>   MD5SUM check for sickrage-2016.12.27-1.tar.gz ... OK
>   Building package sickrage-2016.12.27_1-x86_64-1_SBo.tgz ... OK
>   Installing package sickrage-2016.12.27_1-x86_64-1_SBo.tgz ... OK
>
> I changed the VERSION into 2016.12.27_1 instead of 2016.12.27-1 to avoid
> confusion with pkgtool.
>
> --
> Willy Sudiarto Raharjo
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-30 Thread Willy Sudiarto Raharjo
> 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 below.

Hi Jeremy

it builds fine here (tested just now using sbopkg)

sickrage:
  MD5SUM check for sickrage-2016.12.27-1.tar.gz ... OK
  Building package sickrage-2016.12.27_1-x86_64-1_SBo.tgz ... OK
  Installing package sickrage-2016.12.27_1-x86_64-1_SBo.tgz ... OK

I changed the VERSION into 2016.12.27_1 instead of 2016.12.27-1 to avoid
confusion with pkgtool.

-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



Re: [Slackbuilds-users] Updates - 20161231.1

2016-12-30 Thread Jeremy Hansen
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 below.

Thanks,
Jeremy

On Fri, Dec 30, 2016 at 9:07 PM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> Hi folks,
>
> this is the last public update in 2016!!
> Big thanks to all maintainers who have done a great job maintaining
> their scripts this year and welcome to all new maintainer in SBo.
> At this moment, we have 6200+ scripts in our 14.2 repository, which is
> big improvements since we opened 14.2 repository for submission.
>
> In this last update, we pushed a major change which is Python 3.6.0
> We are looking forward for updated scripts to be compatible with Python
> 3.6.0 in future submission.
>
> Heinz updated VirtualBox to latest 5.0.x release, David pushed darktable
> 2.2.0, and Matteo bumped most of his packages as well.  It's all in in
> this 150+ commits.
>
> On behalf of all SBo admins, We wish you a happy new year 2017.
>
>
> Sat Dec 31 01:24:19 UTC 2016
> academic/avl: Added (aerodynamic analysis).
> academic/fet: Updated for version 5.30.7.
> academic/papi: Added (Performance API).
> academic/reduce-algebra: Updated for version 20161220svn3844.
> academic/wxmacmolplt: Updated for version 7.7.
> academic/xfoil: Added (program for design and analysis of airfoils).
> audio/SAM: Updated for version 20160807_fc56501.
> audio/cmus: Updated for version 2.7.1.
> audio/flacon: Updated for version 2.1.1.
> audio/opusfile: Updated for version 0.8.
> audio/qastools: Updated for version 0.21.0.
> audio/quodlibet: Updated for version 3.8.0.
> audio/speex: Updated for version 1.2.0.
> desktop/awesome-appmenu: Updated for version 0.3.
> desktop/lxpanel: Updated for version 0.9.2.
> desktop/numix-folders: Added (alt. folders for Numix Icon Theme).
> desktop/numix-icon-theme-bevel: Removed (use n.i.t.-circle instead).
> desktop/numix-pack: Updated for version 0.4.5.
> desktop/ptbatterysystemtray: Cleanups, added a license.
> desktop/qlipper: Updated for version 20161212_14bfc66.
> desktop/razorqt: Noted obsolescence, cleanups
> desktop/rss-guard: Updated for version 3.3.5, various cleanups.
> desktop/xlunch: Updated for version 2.3.2.
> desktop/yad: Updated for version 0.38.0.
> development/acpica: Updated for version 20161222.
> development/device-tree-compiler: Updated for version 1.4.2.
> development/diffoscope: Added (in-depth comparison tool).
> development/dpkg: Updated for version 1.18.18.
> development/fsharp: Updated for version 4.0.1.20.
> development/git-lfs: Updated for version 1.5.4.
> development/glm: Updated for version 0.9.8.3.
> development/gsoap: Updated for version 2.8.40.
> development/kcov: Added (code coverage tester).
> development/lazarus: Updated for version 1.6.2.
> development/libcutl: Added (C++ utility library).
> development/libodb-boost: Added (C++ ORM Boost Profile Libraries).
> development/libodb-mysql: Added (MySQL library for ODB c++ ORM).
> development/libodb-pgsql: Added (PostgreSQL library for ODB).
> development/libodb-qt: Added (C++ ORM Qt Profile Libraries).
> development/libodb-sqlite: Added (Sqlite library for ODB c++ ORM).
> development/libodb: Added (Common Runtime Library for ODB c++ ORM).
> development/lua52: Removed.
> development/lua: Removed lua52 reference.
> development/meld3: Updated for version 3.16.4.
> development/mono: Updated for version 4.6.2.7.
> development/monodevelop: Updated for version 6.1.3.19.
> development/mutagen: Updated for version 1.36.
> development/ocamlbuild: Updated for version 0.10.1.
> development/odb: Added (C++ Object-Relational Mapping).
> development/xsp: Updated for version 4.4.
> games/OpenJK: Added (Port of the Jedi Academy game engine).
> games/armagetronad: Updated for version 0.2.8.3.4.
> games/bloodfrontier: Changed homepage, cleanups.
> games/desmume: Removed lua52 reference.
> games/fs2open: Added (FreeSpace 2 Source Code Project).
> games/qzdl: Disable updater + new maintainer.
> games/roccat-tools: Removed lua52 reference.
> graphics/darktable: Updated for version 2.2.0.
> graphics/gource: Updated for version 0.44, changed homepage.
> graphics/nomacs: Updated for version 3.4.
> graphics/photoqt: Updated for version 1.4.1.1.
> graphics/sng: Added (lossless editing of PNGs).
> libraries/PrettyTable: Update DOWNLOAD url.
> libraries/SDL2_ttf: Updated for version 2.0.14.
> libraries/chromaprint: Updated for version 1.4.
> libraries/folly: Fixed md5sum.
> libraries/frei0r: Updated for version 1.5.0.
> libraries/gflags: Fixed tarball handling.
> libraries/leptonica: Updated for version 1.74.
> libraries/libass: Updated for version 1.3.5.
> libraries/libcacard: Updated for version 2.5.2.
> libraries/libgee: Updated for version 0.18.1.
> libraries/libmikmod: Updated for version 3.3.10.
> libraries/liburcu: Updated