Can't clone repo weave/libweave or download bundle

[tomdu...@gmail.com]

Hi all,

I'm attempting to access the git bundle for this repository: https://weave.googlesource.com/weave/libweave

It seems like I don't have the permissions needed to do so event after going to the homepage and selecting "Generate Password" and putting the specified information in ~/.gitcookies

Is this repository off-limits for non-google devs? I don't think that's the case since many of the contents behind this site are indexed by Google. Just try Googling "libweave weave" to see what I mean.

Any help is appreciated.

Best,

Tom.

[tomdu...@gmail.com]

Forgot to mention that the repo also exists in https://chromium.googlesource.com/weave/libweave which I do have access to.

I just don't know if that one contains the latest changes.

[Mike Frysinger]

why are you trying to download that repo ?  the CrOS manifests point to the copy on chromium.googlesource.com now.

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[tomdu...@gmail.com]

The R59 branch of CrOS manifest points it to weave:

<project name="weave/libweave" path="src/weave/libweave" remote="weave" revision="1e86228fcd597847d23dbd83ae03434da8a3329f" />

That's why I checked there.

[Mike Frysinger]

i'll see about syncing the history and updating the branch manifests

-mike

[tomdu...@gmail.com]

Just saw you uploaded all the missing branches. Thanks a lot for the quick response!

Best,

Tommy Dunkan.

[Vadim Bendebury]

I still can't repo sync branches though.

say in  a firmware-cr50-9308.24.B chroot, running repo sync stalls somewhere around:

From https://chromium.googlesource.com/chromiumos/third_party/kernel

   d89d473..f07093e  chromeos-3.14 -> cros/chromeos-3.14

   a9277f4..b9613c9  chromeos-3.18 -> cros/chromeos-3.18

   21d83b8..3f3630b  chromeos-3.8 -> cros/chromeos-3.8

   c02884a..e52d4e7  chromeos-4.4 -> cros/chromeos-4.4

   b6cf595..da471e0  release-R61-9765.B-chromeos-3.14 -> cros/release-R61-9765.B-chromeos-3.14

   cf16793..3e5ac8a  release-R61-9765.B-chromeos-3.18 -> cros/release-R61-9765.B-chromeos-3.18

   fd5b5d7..03cf2ba  release-R61-9765.B-chromeos-3.8 -> cros/release-R61-9765.B-chromeos-3.8

   c24a1c0..f64189f  release-R61-9765.B-chromeos-4.4 -> cros/release-R61-9765.B-chromeos-4.4

 * [new branch]      stabilize-9592.82.B-chromeos-3.10 -> cros/stabilize-9592.82.B-chromeos-3.10

 * [new branch]      stabilize-9592.82.B-chromeos-3.14 -> cros/stabilize-9592.82.B-chromeos-3.14

 * [new branch]      stabilize-9592.82.B-chromeos-3.18 -> cros/stabilize-9592.82.B-chromeos-3.18

 * [new branch]      stabilize-9592.82.B-chromeos-3.8 -> cros/stabilize-9592.82.B-chromeos-3.8

 * [new branch]      stabilize-9592.82.B-chromeos-4.4 -> cros/stabilize-9592.82.B-chromeos-4.4

sits there for very long time, when interrupted with ^C shows the following:

^Cerror: Cannot fetch weave/libweave

[Mike Frysinger]

yes, firmware branches are affected too.  if you're a googler though, it probably should work fine if your ~/.gitcookies are configured for all googlesource hosts.

-mike

[Mike Frysinger]

i've re-enabled read access to the libweave repo on the weave GoB, so people should be able to sync again regardless of their settings

-mike

[ggg]

Tom,

You didn't answer Mike's question ("why do you need this?") other than M59 references it.

I just want to make sure you also see the headline for the libweave repo:

    "(DEAD) development moved to libiota; library with device side implementation of Weave protocol"

And the state of libiota isn't clear either since I can't access libiota git repo either (public google search led me here):

   https://weave.googlesource.com/weave/libiota/+show/libiota-v2.0.0/docs/GETTING_STARTED.md

Can anyone comment on the state of libiota?

Public search for "libiota open source" gives this as "first page" result:

"libiota-v2.0.0 - weave/libiota - Git at Google

https://weave.googlesource.com/weave/libiota/+/libiota-v2.0.0

Mar 30, 2017 - The Iota codebase is open source and distributed under Apache 2.0 license available ... The platform/ directory contains platform-specific code."

but I get  "403" when trying to access that link when signed in with my public gmail account.  I'm guessing the permissions on this page changed since it was first published since the search engine is "leaking" cached results.

cheers,

grant

[Mike Frysinger]

On Thu, Aug 17, 2017 at 1:30 PM, ggg <grun...@chromium.org> wrote:

On Wednesday, August 16, 2017 at 9:59:50 AM UTC-7, tomdu...@gmail.com wrote:

Hi all,

I'm attempting to access the git bundle for this repository: https://weave.googlesource.com/weave/libweave

It seems like I don't have the permissions needed to do so event after going to the homepage and selecting "Generate Password" and putting the specified information in ~/.gitcookies

Is this repository off-limits for non-google devs? I don't think that's the case since many of the contents behind this site are indexed by Google. Just try Googling "libweave weave" to see what I mean.

Tom,

You didn't answer Mike's question ("why do you need this?") other than M59 references it.

i'm pretty sure that's the only reason :)

I just want to make sure you also see the headline for the libweave repo:

    "(DEAD) development moved to libiota; library with device side implementation of Weave protocol"

And the state of libiota isn't clear either since I can't access libiota git repo either (public google search led me here):

   https://weave.googlesource.com/weave/libiota/+show/libiota-v2.0.0/docs/GETTING_STARTED.md

Can anyone comment on the state of libiota?

nothing has been announced publicly currently

-mike

 

Public search for "libiota open source" gives this as "first page" result:

"libiota-v2.0.0 - weave/libiota - Git at Google

https://weave.googlesource.com/weave/libiota/+/libiota-v2.0.0

Mar 30, 2017 - The Iota codebase is open source and distributed under Apache 2.0 license available ... The platform/ directory contains platform-specific code."

but I get  "403" when trying to access that link when signed in with my public gmail account.  I'm guessing the permissions on this page changed since it was first published since the search engine is "leaking" cached results.

cheers,

grant

--