Re: [Slackbuilds-users] dmca takedown notice?!
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... ___ 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?!
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 is true." Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB signature.asc Description: PGP 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?!
> 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 still working out what are the best commands for > people to use > > If your remote 'origin' is your own fork at Github, instead of one of > the SBo repos, then this is probably the quickest and safest way: > >> 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? > > > Alternatively, you can add another remote for our repo and fetch it: > > git checkout master > git remote add sbo https://git.slackbuilds.org/slackbuilds/ > git fetch --all > git fetch --tags sbo > git reset --hard sbo/master > git push -f origin master > git push -f --tags origin master > > If you have other branches (like 14.2) you need to delete them too. > > Hope this is ok, thanks for the feedback! > -D. I did this to my branches to delete the history: git filter-branch --force --index-filter 'git rm --cached --ignore-unmatch audio/jack-tools/aeffect*' --prune-empty --tag-name-filter cat -- --all It took me a long time since I have 3 different branches, but at the end it delete completely the history. I didn't have enough time yesterday to sync with SBo I just delete for the time the affected SlackBuild. P.S. Sorry David I just noticed that accidentally reply on you instead of the list. Regards Panagiotis ___ 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?!
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 still working out what are the best commands for people to use :( If your remote 'origin' is your own fork at Github, instead of one of the SBo repos, then this is probably the quickest and safest way: > 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? :) Alternatively, you can add another remote for our repo and fetch it: git checkout master git remote add sbo https://git.slackbuilds.org/slackbuilds/ git fetch --all git fetch --tags sbo git reset --hard sbo/master git push -f origin master git push -f --tags origin master If you have other branches (like 14.2) you need to delete them too. Hope this is ok, thanks for the feedback! -D. 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?!
* 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 option of deleting my GitHub fork and creating a new fork and then setting up a new clone? I'm not fluent enough with Git to know what to do in this circumstance. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB signature.asc Description: PGP 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] dmca takedown notice?!
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] dmca takedown notice?!
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/
Re: [Slackbuilds-users] dmca takedown notice?!
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?!
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?!
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?!
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?!
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/
