chore: update ipfs-repo

[hugomrdias]

Needs this PR linked ipfs/js-ipfs#1335

[vasco-santos]

@diasdavid should I be able to merge PRs for js-ipfsd-ctl? I have no permissions for that.

[victorb]

@vasco-santos as a lead maintainer, yes. Added write permissions for you to this repository now.

[daviddias]

@vasco-santos weird, you should have had write permissions all the time given that you are in the JS team

[daviddias]

this repo version causes issues with latest js-ipfs (until the CLI errors PR is merged) //cc @hugomrdias

[daviddias]

This PR is blocked until ipfs/js-ipfs#1335 is done given ipfs/js-ipfs-repo#165

[daviddias]

This PR is blocked until ipfs/js-ipfs#1335 is done given ipfs/js-ipfs-repo#165

[dryajov]

@vasco-santos @hugomrdias @victorbjelkholm I believe that we need to pin the ipfs-repo version to 0.20.0, since anything above that will break due to the changes in which repo errors are being handled in newer versions.

[vasco-santos]

I think that we need to release the new versions of ipfsd-ctl and ipfs (with the CLI errors fixing branch), in order to get everything green again. With ipfs-repo@0.20.0, I believe that the @hugomrdias 's CLI errors branch will not work.

[dryajov]

I think that we need to release the new versions of ipfsd-ctl and ipfs (with the CLI errors fixing branch), in order to get everything green again.

Sure, but ipfsd-ctl is most likely broken for everybody right now due to the use of ^ instead of ~ for ipfs-repo version.

[daviddias]

See

42597c1

and IRC log

21:00 <@daviddias> dryajov: why does ipfsd-ctl need to import ipfs-repo?
21:00 <@daviddias> What I see is that it grabs a path and creates a new IPFSRepo rather than passing that path to js-ipfs itself
21:01 <dryajov> trying to remember what was the reason for that now…
21:01 <dryajov> let me think
21:01 → jesse22 joined  ⇐ jesse22_ quit  
21:03 <@daviddias> testing with it removed, works
21:03 <@daviddias> it is used by tests
21:04 <@daviddias> let me see if tests also need it
21:04 <@daviddias> removing
21:04 <@daviddias> *moving
21:05 <dryajov> I think it was done so we can generate random repo names...
21:06 <dryajov> but we can just generate the path, without having to use the repo...
21:06 <@daviddias> exactly

ipfs-repo is not needed by this module at all :)