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

2018-06-14 Thread B Watson
On 6/14/18, Nate Bargmann wrote: > Do I just need to do the nuclear option of deleting my GitHub fork > and creating a new fork and then setting up a new clone? Just did this, at sbosrcarch. The archive is still sitting at 99.9% complete... ___ SlackBu

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

2018-06-14 Thread Nate Bargmann
Thanks, David. I followed your commands and everything looks proper in the master branch and I simply deleted the already merged local branches on GitHub, so that should be clean now. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this i

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

2018-06-14 Thread Panagiotis Nikolaou via SlackBuilds-users
> Hi Nate, Hi everybody, > > On 14/06/18 13:39, Nate Bargmann wrote: >> * On 2018 13 Jun 16:05 -0500, Matteo Bernardini wrote: >>> git checkout master >>> git fetch --all >>> git reset --hard origin/master >> I did those commands and still have the files remaining in my local >> tree. > Sorry about

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

2018-06-14 Thread David Spencer
Hi Nate, Hi everybody, On 14/06/18 13:39, Nate Bargmann wrote: > * On 2018 13 Jun 16:05 -0500, Matteo Bernardini wrote: >> git checkout master >> git fetch --all >> git reset --hard origin/master > > I did those commands and still have the files remaining in my local > tree. Sorry about that, we

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

2018-06-14 Thread Nate Bargmann
* On 2018 13 Jun 16:05 -0500, Matteo Bernardini wrote: > git checkout master > git fetch --all > git reset --hard origin/master I did those commands and still have the files remaining in my local tree. I had not WIP so I was sync'ed with Willy's 2 June update. Do I just need to do the nuclear op

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

2018-06-13 Thread Μιχάλης Μιχαλούδης
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 > affec

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

2018-06-13 Thread 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 header

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

2018-06-13 Thread 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 heade

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

2018-06-13 Thread 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,

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

2018-06-13 Thread 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

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

2018-06-13 Thread 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-

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

2018-06-13 Thread 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

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

2018-06-13 Thread 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 > > communi

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

2018-06-13 Thread 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. > >

[Slackbuilds-users] dmca takedown notice?!

2018-06-13 Thread 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