Okay, unpublished. "plugman unpublish" said it succeeded, but plugman/npm info after that showed that it was still there.
npm --registry http://registry.cordova.io unpublish [email protected] Seemed to do more work, but then did gave an error. However, running "info" now shows that it's gone. Scary things about this: - I think what happened is that "plugman unpublish" deleted the tgz without deleting the package.json - The npm should not have had my plugman credentials when I ran it. Either our registry isn't checking credentials for unpublish, or "plugman adduser" is putting credentials into ~/.npmrc On Fri, Apr 25, 2014 at 10:25 AM, Mike Billau <[email protected]> wrote: > Herp derp. Thanks Andrew. > > > On Fri, Apr 25, 2014 at 10:18 AM, Ian Clelland <[email protected]>wrote: > >> Yeah; it's clearly broken. If someone knows the plugman incantation to do >> that them we should. >> >> We can figure out the apache way to unreleased from dist later :) >> >> >> On Friday, April 25, 2014, Andrew Grieve <[email protected]> wrote: >> >> > Actually, why don't we just unpublish 0.1.5? >> > >> > On Fri, Apr 25, 2014 at 9:55 AM, Andrew Grieve <[email protected] >> <javascript:;>> >> > wrote: >> > > That syntax is for git URLs. try [email protected] >> > > >> > > Note that "plugman info" is a bit useless, but you can use npm info >> > > with our registry via: >> > > >> > > npm --registry http://registry.cordova.io info >> > org.apache.cordova.statusbar >> > > >> > > Also, +1 for a quick fix & vote. Short vote times are completely fine >> > > for small emergency fixes. >> > > >> > > >> > > On Fri, Apr 25, 2014 at 7:38 AM, Mike Billau <[email protected] >> <javascript:;>> >> > wrote: >> > >> +1 for quick release, we have some people who would like to see this >> > fixed >> > >> as well. We tried `cordova plugin add >> > org.apache.cordova.statusbar#r0.1.3` >> > >> (to pull it in before the borked Android impl) but for some reason the >> > tags >> > >> were deleted? Maybe I am misunderstanding something but I thought that >> > >> would have been a valid way to grab the plugin when it just had the >> iOS >> > >> stuff. >> > >> >> > >> >> > >> On Fri, Apr 25, 2014 at 12:58 AM, Michal Mocny <[email protected] >> <javascript:;>> >> > wrote: >> > >> >> > >>> On Thu, Apr 24, 2014 at 10:31 PM, Ian Clelland < >> [email protected]<javascript:;> >> > >>> >wrote: >> > >>> >> > >>> > Quick vote and release of 0.1.6? If the vote starts soon enough, it >> > could >> > >>> > get released early in the weekend. >> > >>> > >> > >>> > I'll admit that I didn't attempt to test this properly (it's not a >> > >>> plugin I >> > >>> > use), and forgot that although it was in the plugin bundle, it's >> not >> > >>> > represented in mobile-spec at all :( >> > >>> > >> > >>> >> > >>> Ugh. >> > >>> >> > >>> >> > >>> > >> > >>> > >> > >>> > >> > >>> > >> > >>> > On Thu, Apr 24, 2014 at 6:47 PM, Steven Gill < >> [email protected]<javascript:;> >> > > >> > >>> > wrote: >> > >>> > >> > >>> > > >> > >>> > > >> > >>> > >> > >>> >> > >> https://issues.apache.org/jira/browse/CB-6513?jql=project%20%3D%20CB%20AND%20text%20~%20statusbar >> > >>> > > >> > >>> > > Breaking compiling for Android. Ionic Framework installs this by >> > >>> default >> > >>> > > and it totally breaks. >> > >>> > > >> > >>> > >> > >>> >> > >>
