Re: [Slackbuilds-users] pcsc-lite - download url not working

[Willy Sudiarto Raharjo]

>> there's a problem with
>> > .tar.bz2>
>> which is unavailable.
>>
>> Maybe https://pcsclite.apdu.fr/files/ will be a better mirror?

I have this fixed on my branch

Thanks


-- 
Willy Sudiarto Raharjo



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

Re: [Slackbuilds-users] dmca takedown notice?!

[Μιχάλης Μιχαλούδης]

13 Ιουν 2018, 6:11 μμ, ο/η Greg' Ar Tourter  έγραψε:

> I just  received a dmca takedown notice for my slackbuild repo copy on github 
> (I looking at the document, I am not the only one from this community).
> 
> It seems that steinberg is claiming jack-tools and anything related to it is 
> affected.

fst is clean?
http://slackbuilds.org/repository/14.2/audio/fst/?search=Fst

Sorry I am away from my computer to check the source.

To my understanding the problem is with one header file like aeffect.h if my 
memory serves correctly.

> Should we respond as a group or as individual? In this case there definitely 
> nothing in the slackbuild that belongs to steinberg but I am not a lawyer...
> 
> Any thoughts?
> 
> Greg
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://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
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20180614.1

[Willy Sudiarto Raharjo]

> We have removed those files from the Git history, but unfortunately
> everybody who has a clone of our main git repo, or any of our mirrors,
> will need to fetch and force update the master branch and rebase all
> your local branches.

This also applies to maintainers who have been given git commit access
to our repository.

Please make sure you run this commands before submitting your updates in
your branch again:

git checkout master
git fetch --all
git reset --hard origin/master


-- 
Willy Sudiarto Raharjo



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

Re: [Slackbuilds-users] pcsc-lite - download url not working

[Daniel Prosser]

I can confirm this issue. The tarball on github (https://github.com/Lud
ovicRousseau/PCSC/archive/pcsc-1.8.14.tar.gz) works if you autoreconf
before running configure.

Dan

On Wed, 2018-06-13 at 17:43 +0200, Thomas Szteliga wrote:
> Hello,
> 
> there's a problem with
>  .tar.bz2>
> which is unavailable.
> 
> Maybe https://pcsclite.apdu.fr/files/ will be a better mirror?
> 
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Updates - 20180614.1

[David Spencer]

Hello everybody!

This surprise public update is sponsored by Steinberg -- motto: "We
enable you to express your creativity" [1]

As you will already have read, they sent a copyright complaint to Github
about hundreds of repos that contain a couple of header files --
including the audio/jack-tools SlackBuild in the SlackBuilds.org mirror,
and 15 other clones of our repo.

We have removed those files from the Git history, but unfortunately
everybody who has a clone of our main git repo, or any of our mirrors,
will need to fetch and force update the master branch and rebase all
your local branches.

If you are one of the people on Github with SBo forks who have received
a takedown notice, you should do those pulls and rebases as soon as
possible, and then force-push to Github, and then reply to the email
that they sent you :(

You might also notice that the Git tags are unsigned at the moment -- we
will fix that soon.

We're really sorry that all this happened :(

Anyway, in other news, here are some nice updates :)

Thanks everybody!
-D.

[1] https://www.steinberg.net/en/company/vision_mission.html


Thu Jun 14 00:28:07 UTC 2018
academic/fet: Updated for version 5.35.7.
academic/veusz: Updated for version 3.0.
accessibility/flite: Updated for version 2.1.
audio/jack-tools: Updated for version 20141211.
audio/mp3gain: Updated for version 1.6.2.
desktop/caffeine-ng: Updated for version 3.4.2.
desktop/wmudmount: Fix build on -current.
development/byacc: Updated for version 20180609.
development/digikey-kicad-library: Added (KiCad DigiKey EDA lib).
development/fossil: Updated for version 2.6.
development/hub: Updated for version 2.4.0.
development/jupyter-nbdime: Updated for version 1.0.1.
development/neovim: Updated for version 0.3.0.
development/nodejs6: Updated for version 6.14.3.
development/nodejs: Updated for version 8.11.3.
development/pkgconf: Update homepage.
development/sbcl: Updated for version 1.4.8.
development/spice-protocol: Updated for version 0.12.14.
games/fortune-game_of_thrones: Added (fortune file).
games/fortune_doctor_who: Fix md5sum.
games/gzdoom: Updated for version 3.4.0.
games/hatari: Updated for version 2.1.0.
games/open-adventure: Fix md5sum.
games/opendune: Updated for version 0.9.
games/qzdoom: Updated for version 2.1.0.
games/sdlpop: Updated for version 1.18.1.
games/snes9x: Updated for version 1.56.1.
games/solarus-quest-editor: Update source.
games/solarus: Update source.
games/stella: Updated for version 5.1.3.
games/vbam: Updated for version 2.0.2.
games/zelda-roth-se: Update source.
games/zsdx: Update source.
games/zsxd: Update source.
gis/Fiona: Updated for version 1.7.12.
gis/pointcloud: Updated for version 1.1.0.
graphics/jpegoptim: Updated for version 1.4.6.
libraries/efivar: Updated for version 36.
libraries/exiftool: Updated for version 11.01.
libraries/jbig2enc: Updated for version 0.29.
libraries/libinput: Updated for version 1.11.0.
libraries/ntl: Updated for version 11.1.0.
libraries/ulfius: Updated for version 2.3.6.
libraries/webkit2gtk: Updated for version 2.20.3.
misc/wcd: Updated for version 6.0.2.
network/darkhttpd: Switch to i586.
network/lldpd: Updated for version 1.0.1.
network/pgpool-II: Added (Connection pooler for PostgreSQL).
network/prosody-mod-block-strangers: Updated for version hg3023.
network/qutebrowser: Updated for version 1.3.2.
network/spice-gtk: Updated for version 0.35.
network/telegram: Updated for version 1.3.7.
network/tor-browser: Updated for version 7.5.5.
network/transmission: Updated for version 2.94.
network/uget: Updated for version 2.2.1.
network/waterfox: Fix .info.
office/MasterPDFEditor: Updated for version 5.0.23.
office/calibre: Updated for version 3.25.0
office/kmymoney: Updated for version 4.8.2.
office/texstudio: Updated for version 2.12.8
perl/perl-GD: Updated for v2.68, fix 32-bit build, add FastCGI.
python/cssselect: Updated for version 1.0.3
python/dukpy: Added (JavaScript runtime environment for Python).
python/html5-parser: Updated for version 0.4.5
python/lxml: Updated for version 4.2.1
python/netifaces: Updated for version 0.10.7
python/psutil: Updated for version 5.4.6
python/python-dateutil: Updated for version 2.7.3
python/setuptools-scm: Updated for version 2.1.0.
system/forkstat: Updated for version 0.02.03.
system/fzf: Updated for version 0.17.4.
system/isdct: Updated for version 3.0.13.
system/isomd5sum: Updated for version 1.2.3.
system/loggedfs: Updated for version 0.9.
system/lz4: Updated for version 1.8.2.
system/man-db: Updated for version 2.8.3.
system/qemu: Update README.
system/spman: Updated for version 1.5.4.
+--+



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

Re: [Slackbuilds-users] How do I get @slackbuilds.org email?

[Azure Zanculmarktum]

I see.

On 6/14/18, Willy Sudiarto Raharjo  wrote:
>> Should I become slackbuilds.org contributor first?
>
> Hi Azure
>
> @slackbuilds.org is intended for admins only
>
>
> --
> Willy Sudiarto Raharjo
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] How do I get @slackbuilds.org email?

[Willy Sudiarto Raharjo]

> Should I become slackbuilds.org contributor first?

Hi Azure

@slackbuilds.org is intended for admins only


-- 
Willy Sudiarto Raharjo



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

[Slackbuilds-users] How do I get @slackbuilds.org email?

[Azure Zanculmarktum]

Should I become slackbuilds.org contributor first?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Compile an android app for Linux

[Didier Spaier]

Hello,

I want to compile the pico2wave app that is part of svox.

I tried to get the Debian package and deps:
libpopt0_1.16-11_amd64.deb # Not seure I need this one)
libttspico-data_1.0+git20130326-8_all.deb
libttspico-utils_1.0+git20130326-8_amd64.deb
libttspico0_1.0+git20130326-8_amd64.deb
then used deb2tg to make "Slackware" packages.

Of course I need to move some files in their right place,

But also I came across a segmentation fault trying to run pico2wave.

Before I investigate further (files not where they should be, versions
mismatch, etc.), I would like to know if their is a relatively simple
way to compile this stuff from source on Slackware (as does Debian).
I could have a look at how the Debian maintainer (Samuel Thibault) does,
but maybe there is a less time consuming way?

I could request clues from Samuel, but he is already more than busy.

Arch Linux has a pacakage in the AUR, but they seem to repackage the
Debian binaries:
https://aur.archlinux.org/packages/svox-pico-bin/

TIA for any clue,

Didier

PS I would also use the Python script picospeaker from Kyle:
https://aur.archlinux.org/cgit/aur.git/tree/picospeaker?h=svox-pico-bin
if I can solve this issue.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[B Watson]

On 6/13/18, Matteo Bernardini  wrote:

> of their commits, move them somewhere handy to reapply them later over
> a new checkout -b of the new master branch that you will have to
> update with

OK. After all this is done, *then* I'll commit a new jack-tools that
doesn't include the steinberg headers, but is capable of using them if
it finds them. So anyone really wanting jack-lxvst will be able to sign
up for a steinberg account, agree to the license, place the headers in
the right place, and go from there.

This sound good to everyone?

> we will think about a stricter set of rules to avoid things like this
> to happen in the future (like not allowing things with unclear
> licenses).

Better to say "nuclear licenses".

This kind of stuff makes me want to quit trying. I do this as a fun hobby,
and the legal BS sucks the fun right out of it.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Building `atom` fails

[Thomas Szteliga]

On 2018-06-13 22:46, Thomas Szteliga wrote:

building `atom` on Slackware64 14.2 fails at:
Package version: 0.8.3 not found
child_process.js:624
throw err;
^




The latest stable 1.27.2 fails too:


Dumping symbols in /tmp/SBo/atom-1.27.2/out/symbols
Running electron-packager on /tmp/SBo/atom-1.27.2/out/app with app name 
"atom"

Downloading electron-v1.7.15-linux-x64.zip
[>] 100.0% of 51.2 MB (3.59 
MB/s)

Packaging app for platform linux x64 using electron v1.7.15
Changing permissions for node files in 
/tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64
Copying non-ASAR resources to 
/tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64/resources
Writing LICENSE.md to 
/tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64/resources

Application bundle created at /tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64
Generating snapshot script at "/tmp/SBo/atom-1.27.2/out/startup.js" 
(1552)Unable to transform source code for module 
/tmp/SBo/atom-1.27.2/out/app/node_modules/yauzl/index.js.

Error: /tmp/SBo/atom-1.27.2/out/app/node_modules/yauzl/index.js
Cannot replace with lazy function because the supplied node does not 
belong to an assignment expression or a variable declaration!
  at FileRequireTransform.replaceAssignmentOrDeclarationWithLazyFunction 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:180:11)
  at Context.visitIdentifier 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:72:18)
  at Context.invokeVisitorMethod 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:344:49)
  at Visitor.PVp.visitWithoutReset 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:196:32)
  at visitChildren 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
  at Visitor.PVp.visitWithoutReset 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
  at visitChildren 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
  at Visitor.PVp.visitWithoutReset 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
  at visitChildren 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
  at Visitor.PVp.visitWithoutReset 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
  at NodePath.each 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path.js:101:26)
  at visitChildren 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:219:18)
  at Visitor.PVp.visitWithoutReset 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
  at visitChildren 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
  at Visitor.PVp.visitWithoutReset 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
  at visitChildren 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25)
  at Visitor.PVp.visitWithoutReset 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20)
  at Visitor.PVp.visit 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:133:29)
  at Object.visit 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:101:55)
  at FileRequireTransform.replaceDeferredRequiresWithLazyFunctions 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:68:20)
  at FileRequireTransform.apply 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:25:10)
  at 
/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/generate-snapshot-script.js:55:56

  at Generator.next (:null:null)
  at step 
(/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/generate-snapshot-script.js:3:191)
  at 
/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/generate-snapshot-script.js:3:361

  at :null:null



--
Best regards

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

Re: [Slackbuilds-users] dmca takedown notice?!

[Matteo Bernardini]

2018-06-13 21:08 GMT+02:00 B Watson :
> On 6/13/18, Matteo Bernardini  wrote:
>> 2018-06-13 17:26 GMT+02:00 Greg' Ar Tourter :
>>> That repo is also on the takedown list!
>>
>> in that case maybe dropping the jack-lxvst stuff may be more
>> appropriate: from the SlackBuild
>>
>> # - Added VST headers to get jack-lxvst to build. Not sure the
>> #   licensing status of these, but they were cloned from a public
>> #   github repo.
>>
>> if we could do with downloading an SDK, maybe accepting a license, and
>> get those files from it I suppose it's fine too.
>>
>> IMHO, Urchlay decides the course of action.
>
> Wow, what a mess.
>
> Does anyone actually *use* jack-lxvst? I don't, I just included it for
> completeness' sake. Upstream's description:
>
> jack cli host for linux vst instruments
>
> There aren't very many native Linux VST instruments. The vast majority
> of them are for Windows... And, the vast majority of people wanting to
> use VST would be using a host with a GUI, I think. Would anyone miss
> this if it were gone?
>
> Another possibility: there exists a project that reverse engineered the
> VST headers (I want to say it's called "fst" or maybe "festige"). Possibly
> these could be used instead, but it's a riskier course of action (we're
> already being sniffed at by a pack of trained attack lawyers, doing this
> might get the other project in trouble too).
>
> Ideally I'd like to discuss this before taking any action. Are we under a
> time limit? Remove the headers within X days or they unleash the slavering
> horde upon us?

every repository on github must comply with the takedown in (more or
less) 18 hours...

we talked about it a little with the other SBo admins and we think to
proceed this way:

- first step will be to erase commit
c7682c3631f4a4b1c7611dcaddeda526a90077cd from the git history of the
master branch: we will do that by rebasing the 11867 commits that
followed it on master;

- we will push it on SBo's git server and then force-push on github SBo mirror;

- tags following 14.2-20170128.1 will be removed from github and we
will decide how to handle those in the next days;
to comply with the takedown you git user should take care to remove
tags also on your github forks with something like 'git push github
:refs/tags/14.2-20170204.1' and 'git tag -d 14.2-20170204.1'.

everybody having forks or branches checked out over the old master
branch will better do a local

git format-patch master

of their commits, move them somewhere handy to reapply them later over
a new checkout -b of the new master branch that you will have to
update with

git checkout master
git fetch --all
git reset --hard origin/master

this will apply to every branch forked from SBo's master, on local, on
github, on SBo's git, etc.

we will think about a stricter set of rules to avoid things like this
to happen in the future (like not allowing things with unclear
licenses).

Matteo

P.S. We will notify the list when the newer master branch will be
pushed on SBo's git.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Building `atom` fails

[Thomas Szteliga]

Hello,

building `atom` on Slackware64 14.2 fails at:


apm  1.18.12
npm  3.10.10
node 6.9.5 x64
atom unknown
python 2.7.15
git 2.14.4
Installing modules â
Installing atom-dark-syntax@0.28.0 â
Installing atom-dark-ui@0.53.0 â
Installing atom-light-syntax@0.29.0 â
Installing atom-light-ui@0.46.0 â
Installing base16-tomorrow-dark-theme@1.5.0 â
Installing base16-tomorrow-light-theme@1.5.0 â
Installing one-dark-ui@1.10.8 â
Installing one-light-ui@1.10.8 â
Installing one-dark-syntax@1.8.0 â
Installing one-light-syntax@1.8.0 â
Installing solarized-dark-syntax@1.1.2 â
Installing solarized-light-syntax@1.1.2 â
Installing about@1.7.8 â
Installing archive-view@0.64.1 â
Installing autocomplete-atom-api@0.10.5 â
Installing autocomplete-css@0.17.4 â
Installing autocomplete-html@0.8.3 â
Installing autocomplete-plus@2.40.0 â
Installing autocomplete-snippets@1.11.2 â
Installing autoflow@0.29.0 â
Installing autosave@0.24.6 â
Installing background-tips@0.27.1 â
Installing bookmarks@0.44.4 â
Installing bracket-matcher@0.88.0 â
Installing command-palette@0.42.0 â
Installing dalek@0.2.1 â
Installing deprecation-cop@0.56.9 â
Installing dev-live-reload@0.47.1 â
Installing encoding-selector@0.23.7 â
Installing exception-reporting@0.42.0 â
Installing find-and-replace@0.215.0 â
Installing fuzzy-finder@1.7.3 â
Installing github@0.8.3 â
Package version: 0.8.3 not found
child_process.js:624
throw err;
^

Error: Command failed: 
/tmp/SBo/atom-1.23.3/apm/node_modules/atom-package-manager/bin/apm 
--loglevel=error install

at checkExecSyncError (child_process.js:601:13)
at Object.execFileSync (child_process.js:621:13)
at module.exports 
(/tmp/SBo/atom-1.23.3/script/lib/run-apm-install.js:14:16)

at Object. (/tmp/SBo/atom-1.23.3/script/bootstrap:35:1)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)





--
Best regards

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

Re: [Slackbuilds-users] dmca takedown notice?!

[Ole Andre Rodlie]

I do this in an application that requires the SDK:
https://github.com/rodlie/airwave/blob/master/CMakeLists.txt#L65

Basically just extract the zip, run the mac shell script to fix include (or
do it manually, it's just a move command), then add the path to the
includes in the build script.

On Wed, Jun 13, 2018 at 5:33 PM, Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:

> 2018-06-13 17:26 GMT+02:00 Greg' Ar Tourter :
> > That repo is also on the takedown list!
>
> in that case maybe dropping the jack-lxvst stuff may be more
> appropriate: from the SlackBuild
>
> # - Added VST headers to get jack-lxvst to build. Not sure the
> #   licensing status of these, but they were cloned from a public
> #   github repo.
>
> if we could do with downloading an SDK, maybe accepting a license, and
> get those files from it I suppose it's fine too.
>
> IMHO, Urchlay decides the course of action.
>
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://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
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] pcsc-lite - download url not working

[Thomas Szteliga]

Hello,

there's a problem with

which is unavailable.

Maybe https://pcsclite.apdu.fr/files/ will be a better mirror?


--
Best regards

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

Re: [Slackbuilds-users] dmca takedown notice?!

[Matteo Bernardini]

2018-06-13 17:26 GMT+02:00 Greg' Ar Tourter :
> That repo is also on the takedown list!

in that case maybe dropping the jack-lxvst stuff may be more
appropriate: from the SlackBuild

# - Added VST headers to get jack-lxvst to build. Not sure the
#   licensing status of these, but they were cloned from a public
#   github repo.

if we could do with downloading an SDK, maybe accepting a license, and
get those files from it I suppose it's fine too.

IMHO, Urchlay decides the course of action.

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

Re: [Slackbuilds-users] dmca takedown notice?!

[Greg' Ar Tourter]

And yeah I looked at the slackbuild after I sent my original email and
noticed the 2 header files. I had not realised there were there.

On 13 June 2018 at 16:26, Greg' Ar Tourter  wrote:

> That repo is also on the takedown list!
>
> On 13 June 2018 at 16:22, Matteo Bernardini 
> wrote:
>
>> 2018-06-13 17:11 GMT+02:00 Greg' Ar Tourter :
>> > I just  received a dmca takedown notice for my slackbuild repo copy on
>> > github (I looking at the document, I am not the only one from this
>> > community).
>> >
>> > It seems that steinberg is claiming jack-tools and anything related to
>> it is
>> > affected.
>> >
>> > Should we respond as a group or as individual? In this case there
>> definitely
>> > nothing in the slackbuild that belongs to steinberg but I am not a
>> lawyer...
>> >
>> > Any thoughts?
>> >
>> > Greg
>>
>> maybe the SlackBuild can just be modified to use the Steinberg headers
>> from
>>
>> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/V
>> ST/pluginterfaces/vst2.x/aeffect.h
>> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/V
>> ST/pluginterfaces/vst2.x/aeffectx.h
>>
>> as additional DOWNLOADs in the jack-tools.info file.
>>
>> Matteo
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://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
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Ole Andre Rodlie]

The header will sooner or later be removed as well, due too license issues.
You should just point to the official SDK download page and/or add an
additional download with full url to the SDK (note that that link must be
maintained).

You could also just use something like SDK_FILE= variable in
the SlackBuild and extract the zip file before build.

On Wed, Jun 13, 2018 at 5:22 PM, Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:

> 2018-06-13 17:11 GMT+02:00 Greg' Ar Tourter :
> > I just  received a dmca takedown notice for my slackbuild repo copy on
> > github (I looking at the document, I am not the only one from this
> > community).
> >
> > It seems that steinberg is claiming jack-tools and anything related to
> it is
> > affected.
> >
> > Should we respond as a group or as individual? In this case there
> definitely
> > nothing in the slackbuild that belongs to steinberg but I am not a
> lawyer...
> >
> > Any thoughts?
> >
> > Greg
>
> maybe the SlackBuild can just be modified to use the Steinberg headers from
>
> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/
> VST/pluginterfaces/vst2.x/aeffect.h
> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/
> VST/pluginterfaces/vst2.x/aeffectx.h
>
> as additional DOWNLOADs in the jack-tools.info file.
>
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://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
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Greg' Ar Tourter]

That repo is also on the takedown list!

On 13 June 2018 at 16:22, Matteo Bernardini 
wrote:

> 2018-06-13 17:11 GMT+02:00 Greg' Ar Tourter :
> > I just  received a dmca takedown notice for my slackbuild repo copy on
> > github (I looking at the document, I am not the only one from this
> > community).
> >
> > It seems that steinberg is claiming jack-tools and anything related to
> it is
> > affected.
> >
> > Should we respond as a group or as individual? In this case there
> definitely
> > nothing in the slackbuild that belongs to steinberg but I am not a
> lawyer...
> >
> > Any thoughts?
> >
> > Greg
>
> maybe the SlackBuild can just be modified to use the Steinberg headers from
>
> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/
> VST/pluginterfaces/vst2.x/aeffect.h
> https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/
> VST/pluginterfaces/vst2.x/aeffectx.h
>
> as additional DOWNLOADs in the jack-tools.info file.
>
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://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
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Matteo Bernardini]

2018-06-13 17:11 GMT+02:00 Greg' Ar Tourter :
> I just  received a dmca takedown notice for my slackbuild repo copy on
> github (I looking at the document, I am not the only one from this
> community).
>
> It seems that steinberg is claiming jack-tools and anything related to it is
> affected.
>
> Should we respond as a group or as individual? In this case there definitely
> nothing in the slackbuild that belongs to steinberg but I am not a lawyer...
>
> Any thoughts?
>
> Greg

maybe the SlackBuild can just be modified to use the Steinberg headers from

https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/VST/pluginterfaces/vst2.x/aeffect.h
https://raw.githubusercontent.com/RomanKubiak/ctrlr/master/VST/pluginterfaces/vst2.x/aeffectx.h

as additional DOWNLOADs in the jack-tools.info file.

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

[Slackbuilds-users] dmca takedown notice?!

[Greg' Ar Tourter]

I just  received a dmca takedown notice for my slackbuild repo copy on
github (I looking at the document, I am not the only one from this
community).

It seems that steinberg is claiming jack-tools and anything related to it
is affected.

Should we respond as a group or as individual? In this case there
definitely nothing in the slackbuild that belongs to steinberg but I am not
a lawyer...

Any thoughts?

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