You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Josh Tynjala <jo...@apache.org> on 2018/01/24 17:21:19 UTC
Cannot install royale-swf from npm
I get the following console output when I run `npm install -g royale-swf`
https://paste.apache.org/xA7e
It appears that royale-asjs is missing from the path when running the `npm/dependencies/download_dependencies.js` script.
- Josh
Re: Cannot install royale-swf from npm
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Jan 24, 2018 2:10 PM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi, please as NPM is ready, make a new thread a resume all important info
about how many npm packages we have, urls, instructions and all that is
needed so I can add it to the website. Thanks
Will do.
Thanks,
Om
2018-01-24 22:51 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
> On Wed, Jan 24, 2018 at 1:15 PM, Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
> > OK, but I believe the royale-swf package still won't run. Or are you
> > going to fix that before publishing?
> >
>
> Hmm, fixing it will require a new release, right? If that is the case, I
> would rather push what we have as is.
> The correct fix can go with the next release.
>
> We might need a couple of such releases to get things right.
>
>
>
> > Please use NPM 5.6.0 so we can use whatever steps you end up using in
the
> > RM script.
> >
>
> Will try that.
>
> Thanks,
> Om
>
>
>
> >
> > Thanks,
> > -Alex
> >
> > On 1/24/18, 1:08 PM, "omuppi1@gmail.com on behalf of OmPrakash
> Muppirala"
> > <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
> >
> > >I'm going to republish both under the apache royale organization.
> Please
> > >hold off on making any changes till then.
> > >
> > >Thanks,
> > >Om
> > >
> > >On Jan 24, 2018 12:31 PM, "Alex Harui" <ah...@adobe.com.invalid>
> wrote:
> > >
> > >> Interesting. There might be different rules for Apache Royale since
> our
> > >> repos are under the Apache organization, but if you can get it to
> work,
> > >>I
> > >> think that would be helpful.
> > >>
> > >> -Alex
> > >>
> > >> On 1/24/18, 12:21 PM, "Piotr Zarzycki" <pi...@gmail.com>
> > >>wrote:
> > >>
> > >> >Ahh Yes!
> > >> >
> > >> >You can do nice release on the GH. We are doing such based on TAG.
> I'm
> > >> >putting in the description links to the release [1]
> > >> >
> > >> >[1]
> > >> >https://na01.safelinks.protection.outlook.com/?url=
> > >> https%3A%2F%2Fgithub.co
> > >>
> > >>>m%2Fprominic%2FMoonshine-IDE%2Freleases&data=02%7C01%7Caharui%
> > 40adobe.co
> > >>>m
> > >> %
> > >> >7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1%7C0%
> > >> >7C0%7C636524220939419032&sdata=WThjkWpxGSPICEBhySb0JJtVJOIKT%
> > >> 2B1wevQ9mi9Kv
> > >> >Lg%3D&reserved=0
> > >> >
> > >> >
> > >> >
> > >> >2018-01-24 20:58 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> > >> >
> > >> >> The NPM install name is defined in package.json.
> > >> >>
> > >> >> The -bin-js package is JS only, no SWF support. It's package name
> is
> > >> >> 'royale'. Turns out there is already a 'royale' out there, so
I've
> > >> >> already changed it to 'apache-royale' in the nightly builds and
for
> > >>the
> > >> >> next release. Technically, we shouldn't NPM publish this package
> > >>with
> > >> >>its
> > >> >> new name until we've officially released the source file with the
> new
> > >> >>name
> > >> >> in it, but also, technically, binary packages are not official
> > >>releases
> > >> >>of
> > >> >> the ASF. I think any individual could publish a nightly as
> > >> >>apache-royale,
> > >> >> but I'm not sure it is worth it. Folks can just use npm install
> > >><url to
> > >> >> the package> as I instructed upthread. If someone wants to put
> that
> > >> >> package some place that isn't mirrored, they can do that as well.
> We
> > >> >> could put it on the CI server, for example.
> > >> >>
> > >> >> The -bin-js-swf package contains SWF support and thus it contains
a
> > >>.js
> > >> >> file that downloads the Adobe SDKs. It looks like that .js file
> > >>needs
> > >> >> fixing so no matter where or how you get at that package, it will
> > >>throw
> > >> >>an
> > >> >> error on installation. Someone needs to take the time to fix that
> > >>.js
> > >> >> file and then we can discuss whether to publish it or not.
> > >> >>
> > >> >> IMO, we should just tell folks who ask to install the 'royale'
> > >>package
> > >> >>via
> > >> >> the mirrors or maybe put a copy up on another server. Does GH
> have a
> > >> >> releases folder or something like that? I hope to start the 0.9.1
> > >> >>release
> > >> >> in 10 to 14 days.
> > >> >>
> > >> >> Thoughts?
> > >> >> -Alex
> > >> >>
> > >> >> On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
> > >> >>wrote:
> > >> >>
> > >> >> >I just wanted to say that we shouldn't loose opportunity to show
> > >>that
> > >> >> >release. If npm is not working let's provide simple urls on the
> > >> >>website.
> > >> >> >
> > >> >> >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki
> > >><pi...@gmail.com>:
> > >> >> >
> > >> >> >> If npm is broken and it's require fix in the source I
> understand.
> > >> >>What's
> > >> >> >> with second option ? For this release we could provide on the
> > >> >>website at
> > >> >> >> least links.
> > >> >> >>
> > >> >> >> Thanks,
> > >> >> >> Piotr
> > >> >> >>
> > >> >> >> 2018-01-24 19:33 GMT+01:00 Alex Harui <aharui@adobe.com.invalid
> >:
> > >> >> >>
> > >> >> >>> I'm not sure how to fix the npm issues without changing a
> source
> > >> >>file.
> > >> >> >>> Any ideas?
> > >> >> >>>
> > >> >> >>> Get Outlook for
> > >> >>
> > >>
> > >>>>>>>Android<https://na01.safelinks.protection.outlook.
> > com/?url=https%3A%
> > >>>>>>>2F%2Fna01.safelinks.protection.outlook&data=02%
> > 7C01%7Caharui%40adobe
> > >>>>>>>.com%7C9f94ce4974d442d5d62008d5636ea830%
> > 7Cfa7b1b5a7b34438794aed2c178
> > >>>>>>>decee1%7C0%7C0%7C636524249282687049&sdata=
> > 8Km8DMHggeDksyAoPbhx7p0hEZ
> > >>>>>>>8uDYWLtS2IAZc2nic%3D&reserved=0.
> > >> com/?url=https%3A%2F
> > >> >>>>>%2Fna01.safelinks.protection.outlook&data=02%7C01%7Caharui%
> > >> 40adobe.com
> > >> >>>>>%7C4f0876c2f05f4609fc0408d563680ef3%
> 7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1
> > >> >>>>>%7C0%7C0%7C636524220939419032&sdata=Q2ckBrKyA%
> > >> 2BPcM9J7bsJskhw14m2ynBTr
> > >> >>>>>ue3SuHD6QCI%3D&reserved=0.
> > >> >> com/?url=https%3A%2F%2
> > >> >> >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%
> > >> >> 7Cdec5bceb963f427bfce
> > >> >> >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241990598
> > >> >>
> > >> >>>>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf2
> > >> 09IgzgXGZhvL4%3D&reserved=0>
> > >> >> >>>
> > >> >> >>> ________________________________
> > >> >> >>> From: Piotr Zarzycki <pi...@gmail.com>
> > >> >> >>> Sent: Wednesday, January 24, 2018 10:17:12 AM
> > >> >> >>> To: dev@royale.apache.org
> > >> >> >>> Subject: Re: Cannot install royale-swf from npm
> > >> >> >>>
> > >> >> >>> Alex,
> > >> >> >>>
> > >> >> >>> Can we republish once again everything ? If not can we upload
> > >> >>binaries
> > >> >> >>>to
> > >> >> >>> Apache mirrors[1] as we had this with Flex ?
> > >> >> >>>
> > >> >> >>> [1]
> > >> >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
> > >> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
> > >> >> >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
> > >> >> >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
> > >> >> >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> > >> >> >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgU
> > KfNBRMr5qb%2Blc%3D&reserved=0
> > >> >> >>>
> > >> >> >>> Thanks,
> > >> >> >>> Piotr
> > >> >> >>>
> > >> >> >>>
> > >> >> >>> 2018-01-24 19:11 GMT+01:00 Alex Harui
<aharui@adobe.com.invalid
> > >:
> > >> >> >>>
> > >> >> >>> > Bummer. Maybe nobody actually tested the royale-swf
package.
> > >>I
> > >> >>only
> > >> >> >>> > tested the royale package which we did not publish due to
> > >> >>collision
> > >> >> >>>with
> > >> >> >>> > another royale package out there. In the next release we
> will
> > >> >>name
> > >> >> >>>the
> > >> >> >>> > packages apache-royale and apache-royale-swf.
> > >> >> >>> >
> > >> >> >>> > Do you have time to try to fix it? Running "ant release"
> > >>builds
> > >> >> >>> packages
> > >> >> >>> > in the "out" folder. Or you can commit changes, and wait
for
> > >>the
> > >> >> >>> nightly
> > >> >> >>> > build. In theory, instead of running "npm install
> royale-swf",
> > >> >>you
> > >> >> >>>can
> > >> >> >>> > swap in the path to your out folder or the url to the
nightly
> > >> >>build
> > >> >> >>> > package instead of "royale-swf".
> > >> >> >>> >
> > >> >> >>> > If you don't really need SWF support, you can try npm on the
> > >> >>released
> > >> >> >>> > bin-js.tar.gz file. Go get the link to the package on the
> > >> >>mirrors by
> > >> >> >>> > hitting this link:
> > >> >> >>> >
> > >> >> >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
> > >> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
> > >> >> >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
> > >> >> >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> > >> >> >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
> > >> >> >>> 2nxga4gg309Oh48I%3D&reserved=0
> > >> >> >>> > binaries/apache-royale-0.
> > >> >> >>> > 9.0-bin-js.tar.gz
> > >> >> >>> >
> > >> >> >>> > Then try 'npm install -g <link to mirrored package>'.
> > >> >> >>> >
> > >> >> >>> > It seemed to work for me.
> > >> >> >>> >
> > >> >> >>> > HTH,
> > >> >> >>> > -Alex
> > >> >> >>> >
> > >> >> >>> >
> > >> >> >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org>
> > >> >>wrote:
> > >> >> >>> >
> > >> >> >>> > >I get the following console output when I run `npm install
> -g
> > >> >> >>> royale-swf`
> > >> >> >>> > >
> > >> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> > >> >> >>> > https%3A%2F%2Fpaste.apa
> > >> >> >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> > >> >> >>> > 7C10eefaebf4d64e560dc708d
> > >> >> >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> > >> >> >>> > 7C636524112827939628&
> > >> >> >>> >
> > >>>sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> > >> >> >>> > >
> > >> >> >>> > >It appears that royale-asjs is missing from the path when
> > >>running
> > >> >> >>>the
> > >> >> >>> > >`npm/dependencies/download_dependencies.js` script.
> > >> >> >>> > >
> > >> >> >>> > >- Josh
> > >> >> >>> >
> > >> >> >>> >
> > >> >> >>>
> > >> >> >>>
> > >> >> >>> --
> > >> >> >>>
> > >> >> >>> Piotr Zarzycki
> > >> >> >>>
> > >> >> >>> Patreon:
> > >>*https://na01.safelinks.protection.outlook.com/?url=https%
> > >> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> > >> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> > >> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> > >> >> >>>
> > >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
> > >> >> >>> <https://na01.safelinks.protection.outlook.com/?url=https%
> > >> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> > >> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> > >> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> > >> >> >>>
> > >> >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%
> 3D&reserved=0>*
> > >> >> >>>
> > >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >> >> --
> > >> >> >>
> > >> >> >> Piotr Zarzycki
> > >> >> >>
> > >> >> >> Patreon:
> > >> >> >>*https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.pat
> > >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> > >> >> %7Cdec5bceb963f
> > >> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241
> > >> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserv
> > >> >> >>ed=0
> > >> >> >>
> > >> >> >><https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.pat
> > >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> > >> >> %7Cdec5bceb963f
> > >> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241
> > >> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserv
> > >> >> >>ed=0>*
> > >> >> >>
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >--
> > >> >> >
> > >> >> >Piotr Zarzycki
> > >> >> >
> > >> >> >Patreon:
> > >> >> >*https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.patr
> > >> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> >> 7Cdec5bceb963f42
> > >> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241990
> > >> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserved=0
> > >> >> ><https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.patr
> > >> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> >> 7Cdec5bceb963f42
> > >> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241990
> > >> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserved=0
> > >> >> >>*
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >> >--
> > >> >
> > >> >Piotr Zarzycki
> > >> >
> > >> >Patreon:
> > >> >*https://na01.safelinks.protection.outlook.com/?url=
> > >> https%3A%2F%2Fwww.patr
> > >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> 7C4f0876c2f05f46
> > >> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1%7C0%7C0%7C6365242209
> > >> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> > >> %2ByOPhFXMV4rCQ%3D&reserved=0
> > >> ><https://na01.safelinks.protection.outlook.com/?url=
> > >> https%3A%2F%2Fwww.patr
> > >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> 7C4f0876c2f05f46
> > >> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1%7C0%7C0%7C6365242209
> > >> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> > >> %2ByOPhFXMV4rCQ%3D&reserved=0
> > >> >>*
> > >>
> > >>
> >
> >
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Cannot install royale-swf from npm
Posted by Carlos Rovira <ca...@apache.org>.
Hi, please as NPM is ready, make a new thread a resume all important info
about how many npm packages we have, urls, instructions and all that is
needed so I can add it to the website. Thanks
2018-01-24 22:51 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
> On Wed, Jan 24, 2018 at 1:15 PM, Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
> > OK, but I believe the royale-swf package still won't run. Or are you
> > going to fix that before publishing?
> >
>
> Hmm, fixing it will require a new release, right? If that is the case, I
> would rather push what we have as is.
> The correct fix can go with the next release.
>
> We might need a couple of such releases to get things right.
>
>
>
> > Please use NPM 5.6.0 so we can use whatever steps you end up using in the
> > RM script.
> >
>
> Will try that.
>
> Thanks,
> Om
>
>
>
> >
> > Thanks,
> > -Alex
> >
> > On 1/24/18, 1:08 PM, "omuppi1@gmail.com on behalf of OmPrakash
> Muppirala"
> > <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
> >
> > >I'm going to republish both under the apache royale organization.
> Please
> > >hold off on making any changes till then.
> > >
> > >Thanks,
> > >Om
> > >
> > >On Jan 24, 2018 12:31 PM, "Alex Harui" <ah...@adobe.com.invalid>
> wrote:
> > >
> > >> Interesting. There might be different rules for Apache Royale since
> our
> > >> repos are under the Apache organization, but if you can get it to
> work,
> > >>I
> > >> think that would be helpful.
> > >>
> > >> -Alex
> > >>
> > >> On 1/24/18, 12:21 PM, "Piotr Zarzycki" <pi...@gmail.com>
> > >>wrote:
> > >>
> > >> >Ahh Yes!
> > >> >
> > >> >You can do nice release on the GH. We are doing such based on TAG.
> I'm
> > >> >putting in the description links to the release [1]
> > >> >
> > >> >[1]
> > >> >https://na01.safelinks.protection.outlook.com/?url=
> > >> https%3A%2F%2Fgithub.co
> > >>
> > >>>m%2Fprominic%2FMoonshine-IDE%2Freleases&data=02%7C01%7Caharui%
> > 40adobe.co
> > >>>m
> > >> %
> > >> >7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1%7C0%
> > >> >7C0%7C636524220939419032&sdata=WThjkWpxGSPICEBhySb0JJtVJOIKT%
> > >> 2B1wevQ9mi9Kv
> > >> >Lg%3D&reserved=0
> > >> >
> > >> >
> > >> >
> > >> >2018-01-24 20:58 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> > >> >
> > >> >> The NPM install name is defined in package.json.
> > >> >>
> > >> >> The -bin-js package is JS only, no SWF support. It's package name
> is
> > >> >> 'royale'. Turns out there is already a 'royale' out there, so I've
> > >> >> already changed it to 'apache-royale' in the nightly builds and for
> > >>the
> > >> >> next release. Technically, we shouldn't NPM publish this package
> > >>with
> > >> >>its
> > >> >> new name until we've officially released the source file with the
> new
> > >> >>name
> > >> >> in it, but also, technically, binary packages are not official
> > >>releases
> > >> >>of
> > >> >> the ASF. I think any individual could publish a nightly as
> > >> >>apache-royale,
> > >> >> but I'm not sure it is worth it. Folks can just use npm install
> > >><url to
> > >> >> the package> as I instructed upthread. If someone wants to put
> that
> > >> >> package some place that isn't mirrored, they can do that as well.
> We
> > >> >> could put it on the CI server, for example.
> > >> >>
> > >> >> The -bin-js-swf package contains SWF support and thus it contains a
> > >>.js
> > >> >> file that downloads the Adobe SDKs. It looks like that .js file
> > >>needs
> > >> >> fixing so no matter where or how you get at that package, it will
> > >>throw
> > >> >>an
> > >> >> error on installation. Someone needs to take the time to fix that
> > >>.js
> > >> >> file and then we can discuss whether to publish it or not.
> > >> >>
> > >> >> IMO, we should just tell folks who ask to install the 'royale'
> > >>package
> > >> >>via
> > >> >> the mirrors or maybe put a copy up on another server. Does GH
> have a
> > >> >> releases folder or something like that? I hope to start the 0.9.1
> > >> >>release
> > >> >> in 10 to 14 days.
> > >> >>
> > >> >> Thoughts?
> > >> >> -Alex
> > >> >>
> > >> >> On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
> > >> >>wrote:
> > >> >>
> > >> >> >I just wanted to say that we shouldn't loose opportunity to show
> > >>that
> > >> >> >release. If npm is not working let's provide simple urls on the
> > >> >>website.
> > >> >> >
> > >> >> >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki
> > >><pi...@gmail.com>:
> > >> >> >
> > >> >> >> If npm is broken and it's require fix in the source I
> understand.
> > >> >>What's
> > >> >> >> with second option ? For this release we could provide on the
> > >> >>website at
> > >> >> >> least links.
> > >> >> >>
> > >> >> >> Thanks,
> > >> >> >> Piotr
> > >> >> >>
> > >> >> >> 2018-01-24 19:33 GMT+01:00 Alex Harui <aharui@adobe.com.invalid
> >:
> > >> >> >>
> > >> >> >>> I'm not sure how to fix the npm issues without changing a
> source
> > >> >>file.
> > >> >> >>> Any ideas?
> > >> >> >>>
> > >> >> >>> Get Outlook for
> > >> >>
> > >>
> > >>>>>>>Android<https://na01.safelinks.protection.outlook.
> > com/?url=https%3A%
> > >>>>>>>2F%2Fna01.safelinks.protection.outlook&data=02%
> > 7C01%7Caharui%40adobe
> > >>>>>>>.com%7C9f94ce4974d442d5d62008d5636ea830%
> > 7Cfa7b1b5a7b34438794aed2c178
> > >>>>>>>decee1%7C0%7C0%7C636524249282687049&sdata=
> > 8Km8DMHggeDksyAoPbhx7p0hEZ
> > >>>>>>>8uDYWLtS2IAZc2nic%3D&reserved=0.
> > >> com/?url=https%3A%2F
> > >> >>>>>%2Fna01.safelinks.protection.outlook&data=02%7C01%7Caharui%
> > >> 40adobe.com
> > >> >>>>>%7C4f0876c2f05f4609fc0408d563680ef3%
> 7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1
> > >> >>>>>%7C0%7C0%7C636524220939419032&sdata=Q2ckBrKyA%
> > >> 2BPcM9J7bsJskhw14m2ynBTr
> > >> >>>>>ue3SuHD6QCI%3D&reserved=0.
> > >> >> com/?url=https%3A%2F%2
> > >> >> >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%
> > >> >> 7Cdec5bceb963f427bfce
> > >> >> >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241990598
> > >> >>
> > >> >>>>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf2
> > >> 09IgzgXGZhvL4%3D&reserved=0>
> > >> >> >>>
> > >> >> >>> ________________________________
> > >> >> >>> From: Piotr Zarzycki <pi...@gmail.com>
> > >> >> >>> Sent: Wednesday, January 24, 2018 10:17:12 AM
> > >> >> >>> To: dev@royale.apache.org
> > >> >> >>> Subject: Re: Cannot install royale-swf from npm
> > >> >> >>>
> > >> >> >>> Alex,
> > >> >> >>>
> > >> >> >>> Can we republish once again everything ? If not can we upload
> > >> >>binaries
> > >> >> >>>to
> > >> >> >>> Apache mirrors[1] as we had this with Flex ?
> > >> >> >>>
> > >> >> >>> [1]
> > >> >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
> > >> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
> > >> >> >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
> > >> >> >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
> > >> >> >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> > >> >> >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgU
> > KfNBRMr5qb%2Blc%3D&reserved=0
> > >> >> >>>
> > >> >> >>> Thanks,
> > >> >> >>> Piotr
> > >> >> >>>
> > >> >> >>>
> > >> >> >>> 2018-01-24 19:11 GMT+01:00 Alex Harui <aharui@adobe.com.invalid
> > >:
> > >> >> >>>
> > >> >> >>> > Bummer. Maybe nobody actually tested the royale-swf package.
> > >>I
> > >> >>only
> > >> >> >>> > tested the royale package which we did not publish due to
> > >> >>collision
> > >> >> >>>with
> > >> >> >>> > another royale package out there. In the next release we
> will
> > >> >>name
> > >> >> >>>the
> > >> >> >>> > packages apache-royale and apache-royale-swf.
> > >> >> >>> >
> > >> >> >>> > Do you have time to try to fix it? Running "ant release"
> > >>builds
> > >> >> >>> packages
> > >> >> >>> > in the "out" folder. Or you can commit changes, and wait for
> > >>the
> > >> >> >>> nightly
> > >> >> >>> > build. In theory, instead of running "npm install
> royale-swf",
> > >> >>you
> > >> >> >>>can
> > >> >> >>> > swap in the path to your out folder or the url to the nightly
> > >> >>build
> > >> >> >>> > package instead of "royale-swf".
> > >> >> >>> >
> > >> >> >>> > If you don't really need SWF support, you can try npm on the
> > >> >>released
> > >> >> >>> > bin-js.tar.gz file. Go get the link to the package on the
> > >> >>mirrors by
> > >> >> >>> > hitting this link:
> > >> >> >>> >
> > >> >> >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
> > >> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
> > >> >> >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
> > >> >> >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> > >> >> >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
> > >> >> >>> 2nxga4gg309Oh48I%3D&reserved=0
> > >> >> >>> > binaries/apache-royale-0.
> > >> >> >>> > 9.0-bin-js.tar.gz
> > >> >> >>> >
> > >> >> >>> > Then try 'npm install -g <link to mirrored package>'.
> > >> >> >>> >
> > >> >> >>> > It seemed to work for me.
> > >> >> >>> >
> > >> >> >>> > HTH,
> > >> >> >>> > -Alex
> > >> >> >>> >
> > >> >> >>> >
> > >> >> >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org>
> > >> >>wrote:
> > >> >> >>> >
> > >> >> >>> > >I get the following console output when I run `npm install
> -g
> > >> >> >>> royale-swf`
> > >> >> >>> > >
> > >> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> > >> >> >>> > https%3A%2F%2Fpaste.apa
> > >> >> >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> > >> >> >>> > 7C10eefaebf4d64e560dc708d
> > >> >> >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> > >> >> >>> > 7C636524112827939628&
> > >> >> >>> >
> > >>>sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> > >> >> >>> > >
> > >> >> >>> > >It appears that royale-asjs is missing from the path when
> > >>running
> > >> >> >>>the
> > >> >> >>> > >`npm/dependencies/download_dependencies.js` script.
> > >> >> >>> > >
> > >> >> >>> > >- Josh
> > >> >> >>> >
> > >> >> >>> >
> > >> >> >>>
> > >> >> >>>
> > >> >> >>> --
> > >> >> >>>
> > >> >> >>> Piotr Zarzycki
> > >> >> >>>
> > >> >> >>> Patreon:
> > >>*https://na01.safelinks.protection.outlook.com/?url=https%
> > >> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> > >> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> > >> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> > >> >> >>>
> > >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
> > >> >> >>> <https://na01.safelinks.protection.outlook.com/?url=https%
> > >> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> > >> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> > >> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> > >> >> >>>
> > >> >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%
> 3D&reserved=0>*
> > >> >> >>>
> > >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >> >> --
> > >> >> >>
> > >> >> >> Piotr Zarzycki
> > >> >> >>
> > >> >> >> Patreon:
> > >> >> >>*https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.pat
> > >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> > >> >> %7Cdec5bceb963f
> > >> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241
> > >> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserv
> > >> >> >>ed=0
> > >> >> >>
> > >> >> >><https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.pat
> > >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> > >> >> %7Cdec5bceb963f
> > >> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241
> > >> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserv
> > >> >> >>ed=0>*
> > >> >> >>
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >--
> > >> >> >
> > >> >> >Piotr Zarzycki
> > >> >> >
> > >> >> >Patreon:
> > >> >> >*https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.patr
> > >> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> >> 7Cdec5bceb963f42
> > >> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241990
> > >> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserved=0
> > >> >> ><https://na01.safelinks.protection.outlook.com/?url=
> > >> >> https%3A%2F%2Fwww.patr
> > >> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> >> 7Cdec5bceb963f42
> > >> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> > >> >> cee1%7C0%7C0%7C6365241990
> > >> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> > >> >> 90aC%2BAyOhGtLI%3D&reserved=0
> > >> >> >>*
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >> >--
> > >> >
> > >> >Piotr Zarzycki
> > >> >
> > >> >Patreon:
> > >> >*https://na01.safelinks.protection.outlook.com/?url=
> > >> https%3A%2F%2Fwww.patr
> > >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> 7C4f0876c2f05f46
> > >> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1%7C0%7C0%7C6365242209
> > >> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> > >> %2ByOPhFXMV4rCQ%3D&reserved=0
> > >> ><https://na01.safelinks.protection.outlook.com/?url=
> > >> https%3A%2F%2Fwww.patr
> > >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> > >> 7C4f0876c2f05f46
> > >> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> > >> cee1%7C0%7C0%7C6365242209
> > >> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> > >> %2ByOPhFXMV4rCQ%3D&reserved=0
> > >> >>*
> > >>
> > >>
> >
> >
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Cannot install royale-swf from npm
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, Jan 24, 2018 at 1:15 PM, Alex Harui <ah...@adobe.com.invalid>
wrote:
> OK, but I believe the royale-swf package still won't run. Or are you
> going to fix that before publishing?
>
Hmm, fixing it will require a new release, right? If that is the case, I
would rather push what we have as is.
The correct fix can go with the next release.
We might need a couple of such releases to get things right.
> Please use NPM 5.6.0 so we can use whatever steps you end up using in the
> RM script.
>
Will try that.
Thanks,
Om
>
> Thanks,
> -Alex
>
> On 1/24/18, 1:08 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
> <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>
> >I'm going to republish both under the apache royale organization. Please
> >hold off on making any changes till then.
> >
> >Thanks,
> >Om
> >
> >On Jan 24, 2018 12:31 PM, "Alex Harui" <ah...@adobe.com.invalid> wrote:
> >
> >> Interesting. There might be different rules for Apache Royale since our
> >> repos are under the Apache organization, but if you can get it to work,
> >>I
> >> think that would be helpful.
> >>
> >> -Alex
> >>
> >> On 1/24/18, 12:21 PM, "Piotr Zarzycki" <pi...@gmail.com>
> >>wrote:
> >>
> >> >Ahh Yes!
> >> >
> >> >You can do nice release on the GH. We are doing such based on TAG. I'm
> >> >putting in the description links to the release [1]
> >> >
> >> >[1]
> >> >https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fgithub.co
> >>
> >>>m%2Fprominic%2FMoonshine-IDE%2Freleases&data=02%7C01%7Caharui%
> 40adobe.co
> >>>m
> >> %
> >> >7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%
> >> >7C0%7C636524220939419032&sdata=WThjkWpxGSPICEBhySb0JJtVJOIKT%
> >> 2B1wevQ9mi9Kv
> >> >Lg%3D&reserved=0
> >> >
> >> >
> >> >
> >> >2018-01-24 20:58 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >> >
> >> >> The NPM install name is defined in package.json.
> >> >>
> >> >> The -bin-js package is JS only, no SWF support. It's package name is
> >> >> 'royale'. Turns out there is already a 'royale' out there, so I've
> >> >> already changed it to 'apache-royale' in the nightly builds and for
> >>the
> >> >> next release. Technically, we shouldn't NPM publish this package
> >>with
> >> >>its
> >> >> new name until we've officially released the source file with the new
> >> >>name
> >> >> in it, but also, technically, binary packages are not official
> >>releases
> >> >>of
> >> >> the ASF. I think any individual could publish a nightly as
> >> >>apache-royale,
> >> >> but I'm not sure it is worth it. Folks can just use npm install
> >><url to
> >> >> the package> as I instructed upthread. If someone wants to put that
> >> >> package some place that isn't mirrored, they can do that as well. We
> >> >> could put it on the CI server, for example.
> >> >>
> >> >> The -bin-js-swf package contains SWF support and thus it contains a
> >>.js
> >> >> file that downloads the Adobe SDKs. It looks like that .js file
> >>needs
> >> >> fixing so no matter where or how you get at that package, it will
> >>throw
> >> >>an
> >> >> error on installation. Someone needs to take the time to fix that
> >>.js
> >> >> file and then we can discuss whether to publish it or not.
> >> >>
> >> >> IMO, we should just tell folks who ask to install the 'royale'
> >>package
> >> >>via
> >> >> the mirrors or maybe put a copy up on another server. Does GH have a
> >> >> releases folder or something like that? I hope to start the 0.9.1
> >> >>release
> >> >> in 10 to 14 days.
> >> >>
> >> >> Thoughts?
> >> >> -Alex
> >> >>
> >> >> On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
> >> >>wrote:
> >> >>
> >> >> >I just wanted to say that we shouldn't loose opportunity to show
> >>that
> >> >> >release. If npm is not working let's provide simple urls on the
> >> >>website.
> >> >> >
> >> >> >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki
> >><pi...@gmail.com>:
> >> >> >
> >> >> >> If npm is broken and it's require fix in the source I understand.
> >> >>What's
> >> >> >> with second option ? For this release we could provide on the
> >> >>website at
> >> >> >> least links.
> >> >> >>
> >> >> >> Thanks,
> >> >> >> Piotr
> >> >> >>
> >> >> >> 2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >> >> >>
> >> >> >>> I'm not sure how to fix the npm issues without changing a source
> >> >>file.
> >> >> >>> Any ideas?
> >> >> >>>
> >> >> >>> Get Outlook for
> >> >>
> >>
> >>>>>>>Android<https://na01.safelinks.protection.outlook.
> com/?url=https%3A%
> >>>>>>>2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7Caharui%40adobe
> >>>>>>>.com%7C9f94ce4974d442d5d62008d5636ea830%
> 7Cfa7b1b5a7b34438794aed2c178
> >>>>>>>decee1%7C0%7C0%7C636524249282687049&sdata=
> 8Km8DMHggeDksyAoPbhx7p0hEZ
> >>>>>>>8uDYWLtS2IAZc2nic%3D&reserved=0.
> >> com/?url=https%3A%2F
> >> >>>>>%2Fna01.safelinks.protection.outlook&data=02%7C01%7Caharui%
> >> 40adobe.com
> >> >>>>>%7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1
> >> >>>>>%7C0%7C0%7C636524220939419032&sdata=Q2ckBrKyA%
> >> 2BPcM9J7bsJskhw14m2ynBTr
> >> >>>>>ue3SuHD6QCI%3D&reserved=0.
> >> >> com/?url=https%3A%2F%2
> >> >> >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%
> >> >> 7Cdec5bceb963f427bfce
> >> >> >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> >> cee1%7C0%7C0%7C6365241990598
> >> >>
> >> >>>>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf2
> >> 09IgzgXGZhvL4%3D&reserved=0>
> >> >> >>>
> >> >> >>> ________________________________
> >> >> >>> From: Piotr Zarzycki <pi...@gmail.com>
> >> >> >>> Sent: Wednesday, January 24, 2018 10:17:12 AM
> >> >> >>> To: dev@royale.apache.org
> >> >> >>> Subject: Re: Cannot install royale-swf from npm
> >> >> >>>
> >> >> >>> Alex,
> >> >> >>>
> >> >> >>> Can we republish once again everything ? If not can we upload
> >> >>binaries
> >> >> >>>to
> >> >> >>> Apache mirrors[1] as we had this with Flex ?
> >> >> >>>
> >> >> >>> [1]
> >> >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
> >> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
> >> >> >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
> >> >> >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
> >> >> >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >> >> >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgU
> KfNBRMr5qb%2Blc%3D&reserved=0
> >> >> >>>
> >> >> >>> Thanks,
> >> >> >>> Piotr
> >> >> >>>
> >> >> >>>
> >> >> >>> 2018-01-24 19:11 GMT+01:00 Alex Harui <aharui@adobe.com.invalid
> >:
> >> >> >>>
> >> >> >>> > Bummer. Maybe nobody actually tested the royale-swf package.
> >>I
> >> >>only
> >> >> >>> > tested the royale package which we did not publish due to
> >> >>collision
> >> >> >>>with
> >> >> >>> > another royale package out there. In the next release we will
> >> >>name
> >> >> >>>the
> >> >> >>> > packages apache-royale and apache-royale-swf.
> >> >> >>> >
> >> >> >>> > Do you have time to try to fix it? Running "ant release"
> >>builds
> >> >> >>> packages
> >> >> >>> > in the "out" folder. Or you can commit changes, and wait for
> >>the
> >> >> >>> nightly
> >> >> >>> > build. In theory, instead of running "npm install royale-swf",
> >> >>you
> >> >> >>>can
> >> >> >>> > swap in the path to your out folder or the url to the nightly
> >> >>build
> >> >> >>> > package instead of "royale-swf".
> >> >> >>> >
> >> >> >>> > If you don't really need SWF support, you can try npm on the
> >> >>released
> >> >> >>> > bin-js.tar.gz file. Go get the link to the package on the
> >> >>mirrors by
> >> >> >>> > hitting this link:
> >> >> >>> >
> >> >> >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
> >> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
> >> >> >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
> >> >> >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> >> >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
> >> >> >>> 2nxga4gg309Oh48I%3D&reserved=0
> >> >> >>> > binaries/apache-royale-0.
> >> >> >>> > 9.0-bin-js.tar.gz
> >> >> >>> >
> >> >> >>> > Then try 'npm install -g <link to mirrored package>'.
> >> >> >>> >
> >> >> >>> > It seemed to work for me.
> >> >> >>> >
> >> >> >>> > HTH,
> >> >> >>> > -Alex
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org>
> >> >>wrote:
> >> >> >>> >
> >> >> >>> > >I get the following console output when I run `npm install -g
> >> >> >>> royale-swf`
> >> >> >>> > >
> >> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> >> >> >>> > https%3A%2F%2Fpaste.apa
> >> >> >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> >> >> >>> > 7C10eefaebf4d64e560dc708d
> >> >> >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> >> >>> > 7C636524112827939628&
> >> >> >>> >
> >>>sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> >> >> >>> > >
> >> >> >>> > >It appears that royale-asjs is missing from the path when
> >>running
> >> >> >>>the
> >> >> >>> > >`npm/dependencies/download_dependencies.js` script.
> >> >> >>> > >
> >> >> >>> > >- Josh
> >> >> >>> >
> >> >> >>> >
> >> >> >>>
> >> >> >>>
> >> >> >>> --
> >> >> >>>
> >> >> >>> Piotr Zarzycki
> >> >> >>>
> >> >> >>> Patreon:
> >>*https://na01.safelinks.protection.outlook.com/?url=https%
> >> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> >> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> >> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >> >> >>>
> >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
> >> >> >>> <https://na01.safelinks.protection.outlook.com/?url=https%
> >> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> >> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> >> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >> >> >>>
> >> >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
> >> >> >>>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >>
> >> >> >> Piotr Zarzycki
> >> >> >>
> >> >> >> Patreon:
> >> >> >>*https://na01.safelinks.protection.outlook.com/?url=
> >> >> https%3A%2F%2Fwww.pat
> >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> >> >> %7Cdec5bceb963f
> >> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> >> cee1%7C0%7C0%7C6365241
> >> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> >> 90aC%2BAyOhGtLI%3D&reserv
> >> >> >>ed=0
> >> >> >>
> >> >> >><https://na01.safelinks.protection.outlook.com/?url=
> >> >> https%3A%2F%2Fwww.pat
> >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> >> >> %7Cdec5bceb963f
> >> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> >> cee1%7C0%7C0%7C6365241
> >> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> >> 90aC%2BAyOhGtLI%3D&reserv
> >> >> >>ed=0>*
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> >--
> >> >> >
> >> >> >Piotr Zarzycki
> >> >> >
> >> >> >Patreon:
> >> >> >*https://na01.safelinks.protection.outlook.com/?url=
> >> >> https%3A%2F%2Fwww.patr
> >> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> >> >> 7Cdec5bceb963f42
> >> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> >> cee1%7C0%7C0%7C6365241990
> >> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> >> 90aC%2BAyOhGtLI%3D&reserved=0
> >> >> ><https://na01.safelinks.protection.outlook.com/?url=
> >> >> https%3A%2F%2Fwww.patr
> >> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> >> >> 7Cdec5bceb963f42
> >> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> >> cee1%7C0%7C0%7C6365241990
> >> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> >> 90aC%2BAyOhGtLI%3D&reserved=0
> >> >> >>*
> >> >>
> >> >>
> >> >
> >> >
> >> >--
> >> >
> >> >Piotr Zarzycki
> >> >
> >> >Patreon:
> >> >*https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fwww.patr
> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> >> 7C4f0876c2f05f46
> >> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6365242209
> >> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> >> %2ByOPhFXMV4rCQ%3D&reserved=0
> >> ><https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fwww.patr
> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> >> 7C4f0876c2f05f46
> >> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6365242209
> >> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> >> %2ByOPhFXMV4rCQ%3D&reserved=0
> >> >>*
> >>
> >>
>
>
Re: Cannot install royale-swf from npm
Posted by Alex Harui <ah...@adobe.com.INVALID>.
OK, but I believe the royale-swf package still won't run. Or are you
going to fix that before publishing?
Please use NPM 5.6.0 so we can use whatever steps you end up using in the
RM script.
Thanks,
-Alex
On 1/24/18, 1:08 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>I'm going to republish both under the apache royale organization. Please
>hold off on making any changes till then.
>
>Thanks,
>Om
>
>On Jan 24, 2018 12:31 PM, "Alex Harui" <ah...@adobe.com.invalid> wrote:
>
>> Interesting. There might be different rules for Apache Royale since our
>> repos are under the Apache organization, but if you can get it to work,
>>I
>> think that would be helpful.
>>
>> -Alex
>>
>> On 1/24/18, 12:21 PM, "Piotr Zarzycki" <pi...@gmail.com>
>>wrote:
>>
>> >Ahh Yes!
>> >
>> >You can do nice release on the GH. We are doing such based on TAG. I'm
>> >putting in the description links to the release [1]
>> >
>> >[1]
>> >https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fgithub.co
>>
>>>m%2Fprominic%2FMoonshine-IDE%2Freleases&data=02%7C01%7Caharui%40adobe.co
>>>m
>> %
>> >7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%
>> >7C0%7C636524220939419032&sdata=WThjkWpxGSPICEBhySb0JJtVJOIKT%
>> 2B1wevQ9mi9Kv
>> >Lg%3D&reserved=0
>> >
>> >
>> >
>> >2018-01-24 20:58 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >
>> >> The NPM install name is defined in package.json.
>> >>
>> >> The -bin-js package is JS only, no SWF support. It's package name is
>> >> 'royale'. Turns out there is already a 'royale' out there, so I've
>> >> already changed it to 'apache-royale' in the nightly builds and for
>>the
>> >> next release. Technically, we shouldn't NPM publish this package
>>with
>> >>its
>> >> new name until we've officially released the source file with the new
>> >>name
>> >> in it, but also, technically, binary packages are not official
>>releases
>> >>of
>> >> the ASF. I think any individual could publish a nightly as
>> >>apache-royale,
>> >> but I'm not sure it is worth it. Folks can just use npm install
>><url to
>> >> the package> as I instructed upthread. If someone wants to put that
>> >> package some place that isn't mirrored, they can do that as well. We
>> >> could put it on the CI server, for example.
>> >>
>> >> The -bin-js-swf package contains SWF support and thus it contains a
>>.js
>> >> file that downloads the Adobe SDKs. It looks like that .js file
>>needs
>> >> fixing so no matter where or how you get at that package, it will
>>throw
>> >>an
>> >> error on installation. Someone needs to take the time to fix that
>>.js
>> >> file and then we can discuss whether to publish it or not.
>> >>
>> >> IMO, we should just tell folks who ask to install the 'royale'
>>package
>> >>via
>> >> the mirrors or maybe put a copy up on another server. Does GH have a
>> >> releases folder or something like that? I hope to start the 0.9.1
>> >>release
>> >> in 10 to 14 days.
>> >>
>> >> Thoughts?
>> >> -Alex
>> >>
>> >> On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
>> >>wrote:
>> >>
>> >> >I just wanted to say that we shouldn't loose opportunity to show
>>that
>> >> >release. If npm is not working let's provide simple urls on the
>> >>website.
>> >> >
>> >> >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki
>><pi...@gmail.com>:
>> >> >
>> >> >> If npm is broken and it's require fix in the source I understand.
>> >>What's
>> >> >> with second option ? For this release we could provide on the
>> >>website at
>> >> >> least links.
>> >> >>
>> >> >> Thanks,
>> >> >> Piotr
>> >> >>
>> >> >> 2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >> >>
>> >> >>> I'm not sure how to fix the npm issues without changing a source
>> >>file.
>> >> >>> Any ideas?
>> >> >>>
>> >> >>> Get Outlook for
>> >>
>>
>>>>>>>Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%
>>>>>>>2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7Caharui%40adobe
>>>>>>>.com%7C9f94ce4974d442d5d62008d5636ea830%7Cfa7b1b5a7b34438794aed2c178
>>>>>>>decee1%7C0%7C0%7C636524249282687049&sdata=8Km8DMHggeDksyAoPbhx7p0hEZ
>>>>>>>8uDYWLtS2IAZc2nic%3D&reserved=0.
>> com/?url=https%3A%2F
>> >>>>>%2Fna01.safelinks.protection.outlook&data=02%7C01%7Caharui%
>> 40adobe.com
>> >>>>>%7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
>> cee1
>> >>>>>%7C0%7C0%7C636524220939419032&sdata=Q2ckBrKyA%
>> 2BPcM9J7bsJskhw14m2ynBTr
>> >>>>>ue3SuHD6QCI%3D&reserved=0.
>> >> com/?url=https%3A%2F%2
>> >> >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%
>> >> 7Cdec5bceb963f427bfce
>> >> >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> >> cee1%7C0%7C0%7C6365241990598
>> >>
>> >>>>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf2
>> 09IgzgXGZhvL4%3D&reserved=0>
>> >> >>>
>> >> >>> ________________________________
>> >> >>> From: Piotr Zarzycki <pi...@gmail.com>
>> >> >>> Sent: Wednesday, January 24, 2018 10:17:12 AM
>> >> >>> To: dev@royale.apache.org
>> >> >>> Subject: Re: Cannot install royale-swf from npm
>> >> >>>
>> >> >>> Alex,
>> >> >>>
>> >> >>> Can we republish once again everything ? If not can we upload
>> >>binaries
>> >> >>>to
>> >> >>> Apache mirrors[1] as we had this with Flex ?
>> >> >>>
>> >> >>> [1]
>> >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
>> >> >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
>> >> >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
>> >> >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> >> >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
>> >> >>>
>> >> >>> Thanks,
>> >> >>> Piotr
>> >> >>>
>> >> >>>
>> >> >>> 2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >> >>>
>> >> >>> > Bummer. Maybe nobody actually tested the royale-swf package.
>>I
>> >>only
>> >> >>> > tested the royale package which we did not publish due to
>> >>collision
>> >> >>>with
>> >> >>> > another royale package out there. In the next release we will
>> >>name
>> >> >>>the
>> >> >>> > packages apache-royale and apache-royale-swf.
>> >> >>> >
>> >> >>> > Do you have time to try to fix it? Running "ant release"
>>builds
>> >> >>> packages
>> >> >>> > in the "out" folder. Or you can commit changes, and wait for
>>the
>> >> >>> nightly
>> >> >>> > build. In theory, instead of running "npm install royale-swf",
>> >>you
>> >> >>>can
>> >> >>> > swap in the path to your out folder or the url to the nightly
>> >>build
>> >> >>> > package instead of "royale-swf".
>> >> >>> >
>> >> >>> > If you don't really need SWF support, you can try npm on the
>> >>released
>> >> >>> > bin-js.tar.gz file. Go get the link to the package on the
>> >>mirrors by
>> >> >>> > hitting this link:
>> >> >>> >
>> >> >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
>> >> >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
>> >> >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
>> >> >>> 2nxga4gg309Oh48I%3D&reserved=0
>> >> >>> > binaries/apache-royale-0.
>> >> >>> > 9.0-bin-js.tar.gz
>> >> >>> >
>> >> >>> > Then try 'npm install -g <link to mirrored package>'.
>> >> >>> >
>> >> >>> > It seemed to work for me.
>> >> >>> >
>> >> >>> > HTH,
>> >> >>> > -Alex
>> >> >>> >
>> >> >>> >
>> >> >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org>
>> >>wrote:
>> >> >>> >
>> >> >>> > >I get the following console output when I run `npm install -g
>> >> >>> royale-swf`
>> >> >>> > >
>> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
>> >> >>> > https%3A%2F%2Fpaste.apa
>> >> >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
>> >> >>> > 7C10eefaebf4d64e560dc708d
>> >> >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> >>> > 7C636524112827939628&
>> >> >>> >
>>>sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
>> >> >>> > >
>> >> >>> > >It appears that royale-asjs is missing from the path when
>>running
>> >> >>>the
>> >> >>> > >`npm/dependencies/download_dependencies.js` script.
>> >> >>> > >
>> >> >>> > >- Josh
>> >> >>> >
>> >> >>> >
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>>
>> >> >>> Piotr Zarzycki
>> >> >>>
>> >> >>> Patreon:
>>*https://na01.safelinks.protection.outlook.com/?url=https%
>> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> >> >>>
>>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
>> >> >>> <https://na01.safelinks.protection.outlook.com/?url=https%
>> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> >> >>>
>> >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >>
>> >> >> Piotr Zarzycki
>> >> >>
>> >> >> Patreon:
>> >> >>*https://na01.safelinks.protection.outlook.com/?url=
>> >> https%3A%2F%2Fwww.pat
>> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> >> %7Cdec5bceb963f
>> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> >> cee1%7C0%7C0%7C6365241
>> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> >> 90aC%2BAyOhGtLI%3D&reserv
>> >> >>ed=0
>> >> >>
>> >> >><https://na01.safelinks.protection.outlook.com/?url=
>> >> https%3A%2F%2Fwww.pat
>> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> >> %7Cdec5bceb963f
>> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> >> cee1%7C0%7C0%7C6365241
>> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> >> 90aC%2BAyOhGtLI%3D&reserv
>> >> >>ed=0>*
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> >--
>> >> >
>> >> >Piotr Zarzycki
>> >> >
>> >> >Patreon:
>> >> >*https://na01.safelinks.protection.outlook.com/?url=
>> >> https%3A%2F%2Fwww.patr
>> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
>> >> 7Cdec5bceb963f42
>> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> >> cee1%7C0%7C0%7C6365241990
>> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> >> 90aC%2BAyOhGtLI%3D&reserved=0
>> >> ><https://na01.safelinks.protection.outlook.com/?url=
>> >> https%3A%2F%2Fwww.patr
>> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
>> >> 7Cdec5bceb963f42
>> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> >> cee1%7C0%7C0%7C6365241990
>> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> >> 90aC%2BAyOhGtLI%3D&reserved=0
>> >> >>*
>> >>
>> >>
>> >
>> >
>> >--
>> >
>> >Piotr Zarzycki
>> >
>> >Patreon:
>> >*https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
>> 7C4f0876c2f05f46
>> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365242209
>> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
>> %2ByOPhFXMV4rCQ%3D&reserved=0
>> ><https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
>> 7C4f0876c2f05f46
>> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365242209
>> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
>> %2ByOPhFXMV4rCQ%3D&reserved=0
>> >>*
>>
>>
Re: Cannot install royale-swf from npm
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I'm going to republish both under the apache royale organization. Please
hold off on making any changes till then.
Thanks,
Om
On Jan 24, 2018 12:31 PM, "Alex Harui" <ah...@adobe.com.invalid> wrote:
> Interesting. There might be different rules for Apache Royale since our
> repos are under the Apache organization, but if you can get it to work, I
> think that would be helpful.
>
> -Alex
>
> On 1/24/18, 12:21 PM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> >Ahh Yes!
> >
> >You can do nice release on the GH. We are doing such based on TAG. I'm
> >putting in the description links to the release [1]
> >
> >[1]
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.co
> >m%2Fprominic%2FMoonshine-IDE%2Freleases&data=02%7C01%7Caharui%40adobe.com
> %
> >7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%
> >7C0%7C636524220939419032&sdata=WThjkWpxGSPICEBhySb0JJtVJOIKT%
> 2B1wevQ9mi9Kv
> >Lg%3D&reserved=0
> >
> >
> >
> >2018-01-24 20:58 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >
> >> The NPM install name is defined in package.json.
> >>
> >> The -bin-js package is JS only, no SWF support. It's package name is
> >> 'royale'. Turns out there is already a 'royale' out there, so I've
> >> already changed it to 'apache-royale' in the nightly builds and for the
> >> next release. Technically, we shouldn't NPM publish this package with
> >>its
> >> new name until we've officially released the source file with the new
> >>name
> >> in it, but also, technically, binary packages are not official releases
> >>of
> >> the ASF. I think any individual could publish a nightly as
> >>apache-royale,
> >> but I'm not sure it is worth it. Folks can just use npm install <url to
> >> the package> as I instructed upthread. If someone wants to put that
> >> package some place that isn't mirrored, they can do that as well. We
> >> could put it on the CI server, for example.
> >>
> >> The -bin-js-swf package contains SWF support and thus it contains a .js
> >> file that downloads the Adobe SDKs. It looks like that .js file needs
> >> fixing so no matter where or how you get at that package, it will throw
> >>an
> >> error on installation. Someone needs to take the time to fix that .js
> >> file and then we can discuss whether to publish it or not.
> >>
> >> IMO, we should just tell folks who ask to install the 'royale' package
> >>via
> >> the mirrors or maybe put a copy up on another server. Does GH have a
> >> releases folder or something like that? I hope to start the 0.9.1
> >>release
> >> in 10 to 14 days.
> >>
> >> Thoughts?
> >> -Alex
> >>
> >> On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
> >>wrote:
> >>
> >> >I just wanted to say that we shouldn't loose opportunity to show that
> >> >release. If npm is not working let's provide simple urls on the
> >>website.
> >> >
> >> >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki <pi...@gmail.com>:
> >> >
> >> >> If npm is broken and it's require fix in the source I understand.
> >>What's
> >> >> with second option ? For this release we could provide on the
> >>website at
> >> >> least links.
> >> >>
> >> >> Thanks,
> >> >> Piotr
> >> >>
> >> >> 2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >> >>
> >> >>> I'm not sure how to fix the npm issues without changing a source
> >>file.
> >> >>> Any ideas?
> >> >>>
> >> >>> Get Outlook for
> >>
> >>>>>Android<https://na01.safelinks.protection.outlook.
> com/?url=https%3A%2F
> >>>>>%2Fna01.safelinks.protection.outlook&data=02%7C01%7Caharui%
> 40adobe.com
> >>>>>%7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> cee1
> >>>>>%7C0%7C0%7C636524220939419032&sdata=Q2ckBrKyA%
> 2BPcM9J7bsJskhw14m2ynBTr
> >>>>>ue3SuHD6QCI%3D&reserved=0.
> >> com/?url=https%3A%2F%2
> >> >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%
> >> 7Cdec5bceb963f427bfce
> >> >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6365241990598
> >>
> >>>>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf2
> 09IgzgXGZhvL4%3D&reserved=0>
> >> >>>
> >> >>> ________________________________
> >> >>> From: Piotr Zarzycki <pi...@gmail.com>
> >> >>> Sent: Wednesday, January 24, 2018 10:17:12 AM
> >> >>> To: dev@royale.apache.org
> >> >>> Subject: Re: Cannot install royale-swf from npm
> >> >>>
> >> >>> Alex,
> >> >>>
> >> >>> Can we republish once again everything ? If not can we upload
> >>binaries
> >> >>>to
> >> >>> Apache mirrors[1] as we had this with Flex ?
> >> >>>
> >> >>> [1]
> >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
> >> >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
> >> >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
> >> >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >> >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
> >> >>>
> >> >>> Thanks,
> >> >>> Piotr
> >> >>>
> >> >>>
> >> >>> 2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >> >>>
> >> >>> > Bummer. Maybe nobody actually tested the royale-swf package. I
> >>only
> >> >>> > tested the royale package which we did not publish due to
> >>collision
> >> >>>with
> >> >>> > another royale package out there. In the next release we will
> >>name
> >> >>>the
> >> >>> > packages apache-royale and apache-royale-swf.
> >> >>> >
> >> >>> > Do you have time to try to fix it? Running "ant release" builds
> >> >>> packages
> >> >>> > in the "out" folder. Or you can commit changes, and wait for the
> >> >>> nightly
> >> >>> > build. In theory, instead of running "npm install royale-swf",
> >>you
> >> >>>can
> >> >>> > swap in the path to your out folder or the url to the nightly
> >>build
> >> >>> > package instead of "royale-swf".
> >> >>> >
> >> >>> > If you don't really need SWF support, you can try npm on the
> >>released
> >> >>> > bin-js.tar.gz file. Go get the link to the package on the
> >>mirrors by
> >> >>> > hitting this link:
> >> >>> >
> >> >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
> >> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
> >> >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
> >> >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
> >> >>> 2nxga4gg309Oh48I%3D&reserved=0
> >> >>> > binaries/apache-royale-0.
> >> >>> > 9.0-bin-js.tar.gz
> >> >>> >
> >> >>> > Then try 'npm install -g <link to mirrored package>'.
> >> >>> >
> >> >>> > It seemed to work for me.
> >> >>> >
> >> >>> > HTH,
> >> >>> > -Alex
> >> >>> >
> >> >>> >
> >> >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org>
> >>wrote:
> >> >>> >
> >> >>> > >I get the following console output when I run `npm install -g
> >> >>> royale-swf`
> >> >>> > >
> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> >> >>> > https%3A%2F%2Fpaste.apa
> >> >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> >> >>> > 7C10eefaebf4d64e560dc708d
> >> >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> >>> > 7C636524112827939628&
> >> >>> > >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> >> >>> > >
> >> >>> > >It appears that royale-asjs is missing from the path when running
> >> >>>the
> >> >>> > >`npm/dependencies/download_dependencies.js` script.
> >> >>> > >
> >> >>> > >- Josh
> >> >>> >
> >> >>> >
> >> >>>
> >> >>>
> >> >>> --
> >> >>>
> >> >>> Piotr Zarzycki
> >> >>>
> >> >>> Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%
> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >> >>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
> >> >>> <https://na01.safelinks.protection.outlook.com/?url=https%
> >> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> >> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> >> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >> >>>
> >>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> Piotr Zarzycki
> >> >>
> >> >> Patreon:
> >> >>*https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fwww.pat
> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> >> %7Cdec5bceb963f
> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6365241
> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> 90aC%2BAyOhGtLI%3D&reserv
> >> >>ed=0
> >> >>
> >> >><https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fwww.pat
> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> >> %7Cdec5bceb963f
> >> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6365241
> >> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> 90aC%2BAyOhGtLI%3D&reserv
> >> >>ed=0>*
> >> >>
> >> >
> >> >
> >> >
> >> >--
> >> >
> >> >Piotr Zarzycki
> >> >
> >> >Patreon:
> >> >*https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fwww.patr
> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> >> 7Cdec5bceb963f42
> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6365241990
> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> 90aC%2BAyOhGtLI%3D&reserved=0
> >> ><https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fwww.patr
> >> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> >> 7Cdec5bceb963f42
> >> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C6365241990
> >> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> >> 90aC%2BAyOhGtLI%3D&reserved=0
> >> >>*
> >>
> >>
> >
> >
> >--
> >
> >Piotr Zarzycki
> >
> >Patreon:
> >*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7C4f0876c2f05f46
> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365242209
> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> %2ByOPhFXMV4rCQ%3D&reserved=0
> ><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7C4f0876c2f05f46
> >09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365242209
> >39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H
> %2ByOPhFXMV4rCQ%3D&reserved=0
> >>*
>
>
Re: Cannot install royale-swf from npm
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Interesting. There might be different rules for Apache Royale since our
repos are under the Apache organization, but if you can get it to work, I
think that would be helpful.
-Alex
On 1/24/18, 12:21 PM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>Ahh Yes!
>
>You can do nice release on the GH. We are doing such based on TAG. I'm
>putting in the description links to the release [1]
>
>[1]
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fprominic%2FMoonshine-IDE%2Freleases&data=02%7C01%7Caharui%40adobe.com%
>7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>7C0%7C636524220939419032&sdata=WThjkWpxGSPICEBhySb0JJtVJOIKT%2B1wevQ9mi9Kv
>Lg%3D&reserved=0
>
>
>
>2018-01-24 20:58 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> The NPM install name is defined in package.json.
>>
>> The -bin-js package is JS only, no SWF support. It's package name is
>> 'royale'. Turns out there is already a 'royale' out there, so I've
>> already changed it to 'apache-royale' in the nightly builds and for the
>> next release. Technically, we shouldn't NPM publish this package with
>>its
>> new name until we've officially released the source file with the new
>>name
>> in it, but also, technically, binary packages are not official releases
>>of
>> the ASF. I think any individual could publish a nightly as
>>apache-royale,
>> but I'm not sure it is worth it. Folks can just use npm install <url to
>> the package> as I instructed upthread. If someone wants to put that
>> package some place that isn't mirrored, they can do that as well. We
>> could put it on the CI server, for example.
>>
>> The -bin-js-swf package contains SWF support and thus it contains a .js
>> file that downloads the Adobe SDKs. It looks like that .js file needs
>> fixing so no matter where or how you get at that package, it will throw
>>an
>> error on installation. Someone needs to take the time to fix that .js
>> file and then we can discuss whether to publish it or not.
>>
>> IMO, we should just tell folks who ask to install the 'royale' package
>>via
>> the mirrors or maybe put a copy up on another server. Does GH have a
>> releases folder or something like that? I hope to start the 0.9.1
>>release
>> in 10 to 14 days.
>>
>> Thoughts?
>> -Alex
>>
>> On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com>
>>wrote:
>>
>> >I just wanted to say that we shouldn't loose opportunity to show that
>> >release. If npm is not working let's provide simple urls on the
>>website.
>> >
>> >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki <pi...@gmail.com>:
>> >
>> >> If npm is broken and it's require fix in the source I understand.
>>What's
>> >> with second option ? For this release we could provide on the
>>website at
>> >> least links.
>> >>
>> >> Thanks,
>> >> Piotr
>> >>
>> >> 2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >>
>> >>> I'm not sure how to fix the npm issues without changing a source
>>file.
>> >>> Any ideas?
>> >>>
>> >>> Get Outlook for
>>
>>>>>Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F
>>>>>%2Fna01.safelinks.protection.outlook&data=02%7C01%7Caharui%40adobe.com
>>>>>%7C4f0876c2f05f4609fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178decee1
>>>>>%7C0%7C0%7C636524220939419032&sdata=Q2ckBrKyA%2BPcM9J7bsJskhw14m2ynBTr
>>>>>ue3SuHD6QCI%3D&reserved=0.
>> com/?url=https%3A%2F%2
>> >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%
>> 7Cdec5bceb963f427bfce
>> >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365241990598
>>
>>>>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf209IgzgXGZhvL4%3D&reserved=0>
>> >>>
>> >>> ________________________________
>> >>> From: Piotr Zarzycki <pi...@gmail.com>
>> >>> Sent: Wednesday, January 24, 2018 10:17:12 AM
>> >>> To: dev@royale.apache.org
>> >>> Subject: Re: Cannot install royale-swf from npm
>> >>>
>> >>> Alex,
>> >>>
>> >>> Can we republish once again everything ? If not can we upload
>>binaries
>> >>>to
>> >>> Apache mirrors[1] as we had this with Flex ?
>> >>>
>> >>> [1]
>> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
>> >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
>> >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
>> >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
>> >>>
>> >>> Thanks,
>> >>> Piotr
>> >>>
>> >>>
>> >>> 2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >>>
>> >>> > Bummer. Maybe nobody actually tested the royale-swf package. I
>>only
>> >>> > tested the royale package which we did not publish due to
>>collision
>> >>>with
>> >>> > another royale package out there. In the next release we will
>>name
>> >>>the
>> >>> > packages apache-royale and apache-royale-swf.
>> >>> >
>> >>> > Do you have time to try to fix it? Running "ant release" builds
>> >>> packages
>> >>> > in the "out" folder. Or you can commit changes, and wait for the
>> >>> nightly
>> >>> > build. In theory, instead of running "npm install royale-swf",
>>you
>> >>>can
>> >>> > swap in the path to your out folder or the url to the nightly
>>build
>> >>> > package instead of "royale-swf".
>> >>> >
>> >>> > If you don't really need SWF support, you can try npm on the
>>released
>> >>> > bin-js.tar.gz file. Go get the link to the package on the
>>mirrors by
>> >>> > hitting this link:
>> >>> >
>> >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
>> >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
>> >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
>> >>> 2nxga4gg309Oh48I%3D&reserved=0
>> >>> > binaries/apache-royale-0.
>> >>> > 9.0-bin-js.tar.gz
>> >>> >
>> >>> > Then try 'npm install -g <link to mirrored package>'.
>> >>> >
>> >>> > It seemed to work for me.
>> >>> >
>> >>> > HTH,
>> >>> > -Alex
>> >>> >
>> >>> >
>> >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org>
>>wrote:
>> >>> >
>> >>> > >I get the following console output when I run `npm install -g
>> >>> royale-swf`
>> >>> > >
>> >>> > >https://na01.safelinks.protection.outlook.com/?url=
>> >>> > https%3A%2F%2Fpaste.apa
>> >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
>> >>> > 7C10eefaebf4d64e560dc708d
>> >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >>> > 7C636524112827939628&
>> >>> > >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
>> >>> > >
>> >>> > >It appears that royale-asjs is missing from the path when running
>> >>>the
>> >>> > >`npm/dependencies/download_dependencies.js` script.
>> >>> > >
>> >>> > >- Josh
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>> --
>> >>>
>> >>> Piotr Zarzycki
>> >>>
>> >>> Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%
>> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> >>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
>> >>> <https://na01.safelinks.protection.outlook.com/?url=https%
>> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> >>>
>>sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Piotr Zarzycki
>> >>
>> >> Patreon:
>> >>*https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fwww.pat
>> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> %7Cdec5bceb963f
>> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365241
>> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> 90aC%2BAyOhGtLI%3D&reserv
>> >>ed=0
>> >>
>> >><https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fwww.pat
>> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
>> %7Cdec5bceb963f
>> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365241
>> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> 90aC%2BAyOhGtLI%3D&reserv
>> >>ed=0>*
>> >>
>> >
>> >
>> >
>> >--
>> >
>> >Piotr Zarzycki
>> >
>> >Patreon:
>> >*https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
>> 7Cdec5bceb963f42
>> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365241990
>> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> 90aC%2BAyOhGtLI%3D&reserved=0
>> ><https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fwww.patr
>> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
>> 7Cdec5bceb963f42
>> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6365241990
>> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
>> 90aC%2BAyOhGtLI%3D&reserved=0
>> >>*
>>
>>
>
>
>--
>
>Piotr Zarzycki
>
>Patreon:
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4f0876c2f05f46
>09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365242209
>39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H%2ByOPhFXMV4rCQ%3D&reserved=0
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C4f0876c2f05f46
>09fc0408d563680ef3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365242209
>39419032&sdata=UMtaFwbRWSs6eTdTNRgZOZxIIM6L6H%2ByOPhFXMV4rCQ%3D&reserved=0
>>*
Re: Cannot install royale-swf from npm
Posted by Piotr Zarzycki <pi...@gmail.com>.
Ahh Yes!
You can do nice release on the GH. We are doing such based on TAG. I'm
putting in the description links to the release [1]
[1] https://github.com/prominic/Moonshine-IDE/releases
2018-01-24 20:58 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> The NPM install name is defined in package.json.
>
> The -bin-js package is JS only, no SWF support. It's package name is
> 'royale'. Turns out there is already a 'royale' out there, so I've
> already changed it to 'apache-royale' in the nightly builds and for the
> next release. Technically, we shouldn't NPM publish this package with its
> new name until we've officially released the source file with the new name
> in it, but also, technically, binary packages are not official releases of
> the ASF. I think any individual could publish a nightly as apache-royale,
> but I'm not sure it is worth it. Folks can just use npm install <url to
> the package> as I instructed upthread. If someone wants to put that
> package some place that isn't mirrored, they can do that as well. We
> could put it on the CI server, for example.
>
> The -bin-js-swf package contains SWF support and thus it contains a .js
> file that downloads the Adobe SDKs. It looks like that .js file needs
> fixing so no matter where or how you get at that package, it will throw an
> error on installation. Someone needs to take the time to fix that .js
> file and then we can discuss whether to publish it or not.
>
> IMO, we should just tell folks who ask to install the 'royale' package via
> the mirrors or maybe put a copy up on another server. Does GH have a
> releases folder or something like that? I hope to start the 0.9.1 release
> in 10 to 14 days.
>
> Thoughts?
> -Alex
>
> On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>
> >I just wanted to say that we shouldn't loose opportunity to show that
> >release. If npm is not working let's provide simple urls on the website.
> >
> >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki <pi...@gmail.com>:
> >
> >> If npm is broken and it's require fix in the source I understand. What's
> >> with second option ? For this release we could provide on the website at
> >> least links.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> 2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >>
> >>> I'm not sure how to fix the npm issues without changing a source file.
> >>> Any ideas?
> >>>
> >>> Get Outlook for
> >>>Android<https://na01.safelinks.protection.outlook.
> com/?url=https%3A%2F%2
> >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%
> 7Cdec5bceb963f427bfce
> >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365241990598
> >>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf209IgzgXGZhvL4%3D&reserved=0>
> >>>
> >>> ________________________________
> >>> From: Piotr Zarzycki <pi...@gmail.com>
> >>> Sent: Wednesday, January 24, 2018 10:17:12 AM
> >>> To: dev@royale.apache.org
> >>> Subject: Re: Cannot install royale-swf from npm
> >>>
> >>> Alex,
> >>>
> >>> Can we republish once again everything ? If not can we upload binaries
> >>>to
> >>> Apache mirrors[1] as we had this with Flex ?
> >>>
> >>> [1]
> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
> >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
> >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
> >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>>
> >>> 2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >>>
> >>> > Bummer. Maybe nobody actually tested the royale-swf package. I only
> >>> > tested the royale package which we did not publish due to collision
> >>>with
> >>> > another royale package out there. In the next release we will name
> >>>the
> >>> > packages apache-royale and apache-royale-swf.
> >>> >
> >>> > Do you have time to try to fix it? Running "ant release" builds
> >>> packages
> >>> > in the "out" folder. Or you can commit changes, and wait for the
> >>> nightly
> >>> > build. In theory, instead of running "npm install royale-swf", you
> >>>can
> >>> > swap in the path to your out folder or the url to the nightly build
> >>> > package instead of "royale-swf".
> >>> >
> >>> > If you don't really need SWF support, you can try npm on the released
> >>> > bin-js.tar.gz file. Go get the link to the package on the mirrors by
> >>> > hitting this link:
> >>> >
> >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
> >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
> >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
> >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
> >>> 2nxga4gg309Oh48I%3D&reserved=0
> >>> > binaries/apache-royale-0.
> >>> > 9.0-bin-js.tar.gz
> >>> >
> >>> > Then try 'npm install -g <link to mirrored package>'.
> >>> >
> >>> > It seemed to work for me.
> >>> >
> >>> > HTH,
> >>> > -Alex
> >>> >
> >>> >
> >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org> wrote:
> >>> >
> >>> > >I get the following console output when I run `npm install -g
> >>> royale-swf`
> >>> > >
> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> >>> > https%3A%2F%2Fpaste.apa
> >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> >>> > 7C10eefaebf4d64e560dc708d
> >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >>> > 7C636524112827939628&
> >>> > >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> >>> > >
> >>> > >It appears that royale-asjs is missing from the path when running
> >>>the
> >>> > >`npm/dependencies/download_dependencies.js` script.
> >>> > >
> >>> > >- Josh
> >>> >
> >>> >
> >>>
> >>>
> >>> --
> >>>
> >>> Piotr Zarzycki
> >>>
> >>> Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%
> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
> >>> <https://na01.safelinks.protection.outlook.com/?url=https%
> >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
> >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
> >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
> >>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon:
> >>*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> %7Cdec5bceb963f
> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365241
> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> 90aC%2BAyOhGtLI%3D&reserv
> >>ed=0
> >>
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> %7Cdec5bceb963f
> >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365241
> >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> 90aC%2BAyOhGtLI%3D&reserv
> >>ed=0>*
> >>
> >
> >
> >
> >--
> >
> >Piotr Zarzycki
> >
> >Patreon:
> >*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7Cdec5bceb963f42
> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365241990
> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> 90aC%2BAyOhGtLI%3D&reserved=0
> ><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patr
> >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%
> 7Cdec5bceb963f42
> >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365241990
> >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN
> 90aC%2BAyOhGtLI%3D&reserved=0
> >>*
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Cannot install royale-swf from npm
Posted by Alex Harui <ah...@adobe.com.INVALID>.
The NPM install name is defined in package.json.
The -bin-js package is JS only, no SWF support. It's package name is
'royale'. Turns out there is already a 'royale' out there, so I've
already changed it to 'apache-royale' in the nightly builds and for the
next release. Technically, we shouldn't NPM publish this package with its
new name until we've officially released the source file with the new name
in it, but also, technically, binary packages are not official releases of
the ASF. I think any individual could publish a nightly as apache-royale,
but I'm not sure it is worth it. Folks can just use npm install <url to
the package> as I instructed upthread. If someone wants to put that
package some place that isn't mirrored, they can do that as well. We
could put it on the CI server, for example.
The -bin-js-swf package contains SWF support and thus it contains a .js
file that downloads the Adobe SDKs. It looks like that .js file needs
fixing so no matter where or how you get at that package, it will throw an
error on installation. Someone needs to take the time to fix that .js
file and then we can discuss whether to publish it or not.
IMO, we should just tell folks who ask to install the 'royale' package via
the mirrors or maybe put a copy up on another server. Does GH have a
releases folder or something like that? I hope to start the 0.9.1 release
in 10 to 14 days.
Thoughts?
-Alex
On 1/24/18, 11:44 AM, "Piotr Zarzycki" <pi...@gmail.com> wrote:
>I just wanted to say that we shouldn't loose opportunity to show that
>release. If npm is not working let's provide simple urls on the website.
>
>2018-01-24 19:59 GMT+01:00 Piotr Zarzycki <pi...@gmail.com>:
>
>> If npm is broken and it's require fix in the source I understand. What's
>> with second option ? For this release we could provide on the website at
>> least links.
>>
>> Thanks,
>> Piotr
>>
>> 2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>>
>>> I'm not sure how to fix the npm issues without changing a source file.
>>> Any ideas?
>>>
>>> Get Outlook for
>>>Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2
>>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%7Cdec5bceb963f427bfce
>>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365241990598
>>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf209IgzgXGZhvL4%3D&reserved=0>
>>>
>>> ________________________________
>>> From: Piotr Zarzycki <pi...@gmail.com>
>>> Sent: Wednesday, January 24, 2018 10:17:12 AM
>>> To: dev@royale.apache.org
>>> Subject: Re: Cannot install royale-swf from npm
>>>
>>> Alex,
>>>
>>> Can we republish once again everything ? If not can we upload binaries
>>>to
>>> Apache mirrors[1] as we had this with Flex ?
>>>
>>> [1]
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
>>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
>>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
>>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
>>>
>>> Thanks,
>>> Piotr
>>>
>>>
>>> 2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>>>
>>> > Bummer. Maybe nobody actually tested the royale-swf package. I only
>>> > tested the royale package which we did not publish due to collision
>>>with
>>> > another royale package out there. In the next release we will name
>>>the
>>> > packages apache-royale and apache-royale-swf.
>>> >
>>> > Do you have time to try to fix it? Running "ant release" builds
>>> packages
>>> > in the "out" folder. Or you can commit changes, and wait for the
>>> nightly
>>> > build. In theory, instead of running "npm install royale-swf", you
>>>can
>>> > swap in the path to your out folder or the url to the nightly build
>>> > package instead of "royale-swf".
>>> >
>>> > If you don't really need SWF support, you can try npm on the released
>>> > bin-js.tar.gz file. Go get the link to the package on the mirrors by
>>> > hitting this link:
>>> >
>>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
>>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
>>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
>>> 2nxga4gg309Oh48I%3D&reserved=0
>>> > binaries/apache-royale-0.
>>> > 9.0-bin-js.tar.gz
>>> >
>>> > Then try 'npm install -g <link to mirrored package>'.
>>> >
>>> > It seemed to work for me.
>>> >
>>> > HTH,
>>> > -Alex
>>> >
>>> >
>>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org> wrote:
>>> >
>>> > >I get the following console output when I run `npm install -g
>>> royale-swf`
>>> > >
>>> > >https://na01.safelinks.protection.outlook.com/?url=
>>> > https%3A%2F%2Fpaste.apa
>>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
>>> > 7C10eefaebf4d64e560dc708d
>>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>> > 7C636524112827939628&
>>> > >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
>>> > >
>>> > >It appears that royale-asjs is missing from the path when running
>>>the
>>> > >`npm/dependencies/download_dependencies.js` script.
>>> > >
>>> > >- Josh
>>> >
>>> >
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%
>>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
>>> <https://na01.safelinks.protection.outlook.com/?url=https%
>>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
>>>
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon:
>>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pat
>>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdec5bceb963f
>>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365241
>>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN90aC%2BAyOhGtLI%3D&reserv
>>ed=0
>>
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pat
>>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdec5bceb963f
>>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365241
>>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN90aC%2BAyOhGtLI%3D&reserv
>>ed=0>*
>>
>
>
>
>--
>
>Piotr Zarzycki
>
>Patreon:
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdec5bceb963f42
>7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365241990
>59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN90aC%2BAyOhGtLI%3D&reserved=0
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdec5bceb963f42
>7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365241990
>59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN90aC%2BAyOhGtLI%3D&reserved=0
>>*
Re: Cannot install royale-swf from npm
Posted by Piotr Zarzycki <pi...@gmail.com>.
I just wanted to say that we shouldn't loose opportunity to show that
release. If npm is not working let's provide simple urls on the website.
2018-01-24 19:59 GMT+01:00 Piotr Zarzycki <pi...@gmail.com>:
> If npm is broken and it's require fix in the source I understand. What's
> with second option ? For this release we could provide on the website at
> least links.
>
> Thanks,
> Piotr
>
> 2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> I'm not sure how to fix the npm issues without changing a source file.
>> Any ideas?
>>
>> Get Outlook for Android<https://aka.ms/ghei36>
>>
>> ________________________________
>> From: Piotr Zarzycki <pi...@gmail.com>
>> Sent: Wednesday, January 24, 2018 10:17:12 AM
>> To: dev@royale.apache.org
>> Subject: Re: Cannot install royale-swf from npm
>>
>> Alex,
>>
>> Can we republish once again everything ? If not can we upload binaries to
>> Apache mirrors[1] as we had this with Flex ?
>>
>> [1]
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%
>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%
>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa
>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
>>
>> Thanks,
>> Piotr
>>
>>
>> 2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>>
>> > Bummer. Maybe nobody actually tested the royale-swf package. I only
>> > tested the royale package which we did not publish due to collision with
>> > another royale package out there. In the next release we will name the
>> > packages apache-royale and apache-royale-swf.
>> >
>> > Do you have time to try to fix it? Running "ant release" builds
>> packages
>> > in the "out" folder. Or you can commit changes, and wait for the
>> nightly
>> > build. In theory, instead of running "npm install royale-swf", you can
>> > swap in the path to your out folder or the url to the nightly build
>> > package instead of "royale-swf".
>> >
>> > If you don't really need SWF support, you can try npm on the released
>> > bin-js.tar.gz file. Go get the link to the package on the mirrors by
>> > hitting this link:
>> >
>> > https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%
>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4
>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F
>> 2nxga4gg309Oh48I%3D&reserved=0
>> > binaries/apache-royale-0.
>> > 9.0-bin-js.tar.gz
>> >
>> > Then try 'npm install -g <link to mirrored package>'.
>> >
>> > It seemed to work for me.
>> >
>> > HTH,
>> > -Alex
>> >
>> >
>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org> wrote:
>> >
>> > >I get the following console output when I run `npm install -g
>> royale-swf`
>> > >
>> > >https://na01.safelinks.protection.outlook.com/?url=
>> > https%3A%2F%2Fpaste.apa
>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
>> > 7C10eefaebf4d64e560dc708d
>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> > 7C636524112827939628&
>> > >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
>> > >
>> > >It appears that royale-asjs is missing from the path when running the
>> > >`npm/dependencies/download_dependencies.js` script.
>> > >
>> > >- Josh
>> >
>> >
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
>> <https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu
>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7
>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&
>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
>>
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Cannot install royale-swf from npm
Posted by Piotr Zarzycki <pi...@gmail.com>.
If npm is broken and it's require fix in the source I understand. What's
with second option ? For this release we could provide on the website at
least links.
Thanks,
Piotr
2018-01-24 19:33 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> I'm not sure how to fix the npm issues without changing a source file.
> Any ideas?
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> ________________________________
> From: Piotr Zarzycki <pi...@gmail.com>
> Sent: Wednesday, January 24, 2018 10:17:12 AM
> To: dev@royale.apache.org
> Subject: Re: Cannot install royale-swf from npm
>
> Alex,
>
> Can we republish once again everything ? If not can we upload binaries to
> Apache mirrors[1] as we had this with Flex ?
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.
> 16.1%2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%
> 7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata=
> KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
>
> Thanks,
> Piotr
>
>
> 2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
> > Bummer. Maybe nobody actually tested the royale-swf package. I only
> > tested the royale package which we did not publish due to collision with
> > another royale package out there. In the next release we will name the
> > packages apache-royale and apache-royale-swf.
> >
> > Do you have time to try to fix it? Running "ant release" builds packages
> > in the "out" folder. Or you can commit changes, and wait for the nightly
> > build. In theory, instead of running "npm install royale-swf", you can
> > swap in the path to your out folder or the url to the nightly build
> > package instead of "royale-swf".
> >
> > If you don't really need SWF support, you can try npm on the released
> > bin-js.tar.gz file. Go get the link to the package on the mirrors by
> > hitting this link:
> >
> > https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%
> 2F0.9.0%2F&data=02%7C01%7Caharui%40adobe.com%
> 7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%
> 2F2nxga4gg309Oh48I%3D&reserved=0
> > binaries/apache-royale-0.
> > 9.0-bin-js.tar.gz
> >
> > Then try 'npm install -g <link to mirrored package>'.
> >
> > It seemed to work for me.
> >
> > HTH,
> > -Alex
> >
> >
> > On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org> wrote:
> >
> > >I get the following console output when I run `npm install -g
> royale-swf`
> > >
> > >https://na01.safelinks.protection.outlook.com/?url=
> > https%3A%2F%2Fpaste.apa
> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> > 7C10eefaebf4d64e560dc708d
> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> > 7C636524112827939628&
> > >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> > >
> > >It appears that royale-asjs is missing from the path when running the
> > >`npm/dependencies/download_dependencies.js` script.
> > >
> > >- Josh
> >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%
> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata=
> SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%
> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata=
> SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Cannot install royale-swf from npm
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I'm not sure how to fix the npm issues without changing a source file. Any ideas?
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Piotr Zarzycki <pi...@gmail.com>
Sent: Wednesday, January 24, 2018 10:17:12 AM
To: dev@royale.apache.org
Subject: Re: Cannot install royale-swf from npm
Alex,
Can we republish once again everything ? If not can we upload binaries to
Apache mirrors[1] as we had this with Flex ?
[1]
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1%2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0
Thanks,
Piotr
2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> Bummer. Maybe nobody actually tested the royale-swf package. I only
> tested the royale package which we did not publish due to collision with
> another royale package out there. In the next release we will name the
> packages apache-royale and apache-royale-swf.
>
> Do you have time to try to fix it? Running "ant release" builds packages
> in the "out" folder. Or you can commit changes, and wait for the nightly
> build. In theory, instead of running "npm install royale-swf", you can
> swap in the path to your out folder or the url to the nightly build
> package instead of "royale-swf".
>
> If you don't really need SWF support, you can try npm on the released
> bin-js.tar.gz file. Go get the link to the package on the mirrors by
> hitting this link:
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F2nxga4gg309Oh48I%3D&reserved=0
> binaries/apache-royale-0.
> 9.0-bin-js.tar.gz
>
> Then try 'npm install -g <link to mirrored package>'.
>
> It seemed to work for me.
>
> HTH,
> -Alex
>
>
> On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org> wrote:
>
> >I get the following console output when I run `npm install -g royale-swf`
> >
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fpaste.apa
> >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> 7C10eefaebf4d64e560dc708d
> >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636524112827939628&
> >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> >
> >It appears that royale-asjs is missing from the path when running the
> >`npm/dependencies/download_dependencies.js` script.
> >
> >- Josh
>
>
--
Piotr Zarzycki
Patreon: *https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>*
Re: Cannot install royale-swf from npm
Posted by Piotr Zarzycki <pi...@gmail.com>.
Alex,
Can we republish once again everything ? If not can we upload binaries to
Apache mirrors[1] as we had this with Flex ?
[1]
http://www.apache.org/dyn/closer.lua/flex/4.16.1/binaries/apache-flex-sdk-4.16.1-bin.zip
Thanks,
Piotr
2018-01-24 19:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> Bummer. Maybe nobody actually tested the royale-swf package. I only
> tested the royale package which we did not publish due to collision with
> another royale package out there. In the next release we will name the
> packages apache-royale and apache-royale-swf.
>
> Do you have time to try to fix it? Running "ant release" builds packages
> in the "out" folder. Or you can commit changes, and wait for the nightly
> build. In theory, instead of running "npm install royale-swf", you can
> swap in the path to your out folder or the url to the nightly build
> package instead of "royale-swf".
>
> If you don't really need SWF support, you can try npm on the released
> bin-js.tar.gz file. Go get the link to the package on the mirrors by
> hitting this link:
>
> http://www.apache.org/dyn/closer.lua/royale/0.9.0/
> binaries/apache-royale-0.
> 9.0-bin-js.tar.gz
>
> Then try 'npm install -g <link to mirrored package>'.
>
> It seemed to work for me.
>
> HTH,
> -Alex
>
>
> On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org> wrote:
>
> >I get the following console output when I run `npm install -g royale-swf`
> >
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fpaste.apa
> >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%
> 7C10eefaebf4d64e560dc708d
> >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636524112827939628&
> >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
> >
> >It appears that royale-asjs is missing from the path when running the
> >`npm/dependencies/download_dependencies.js` script.
> >
> >- Josh
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Cannot install royale-swf from npm
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Bummer. Maybe nobody actually tested the royale-swf package. I only
tested the royale package which we did not publish due to collision with
another royale package out there. In the next release we will name the
packages apache-royale and apache-royale-swf.
Do you have time to try to fix it? Running "ant release" builds packages
in the "out" folder. Or you can commit changes, and wait for the nightly
build. In theory, instead of running "npm install royale-swf", you can
swap in the path to your out folder or the url to the nightly build
package instead of "royale-swf".
If you don't really need SWF support, you can try npm on the released
bin-js.tar.gz file. Go get the link to the package on the mirrors by
hitting this link:
http://www.apache.org/dyn/closer.lua/royale/0.9.0/binaries/apache-royale-0.
9.0-bin-js.tar.gz
Then try 'npm install -g <link to mirrored package>'.
It seemed to work for me.
HTH,
-Alex
On 1/24/18, 9:21 AM, "Josh Tynjala" <jo...@apache.org> wrote:
>I get the following console output when I run `npm install -g royale-swf`
>
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%7C10eefaebf4d64e560dc708d
>5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524112827939628&
>sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0
>
>It appears that royale-asjs is missing from the path when running the
>`npm/dependencies/download_dependencies.js` script.
>
>- Josh