Issues installing Protobuf v3.0.0-beta-3,1?

[Drew Diver]

For some reason this package fails to pull gmock-1.7.0.zip and continuously fails.

protobuf-3.0.0-beta-3.1/util/python/BUILD
Google Mock not present.  Fetching gmock-1.7.0 from the web...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1582  100  1582    0     0   9269      0 --:--:-- --:--:-- --:--:-- 10986
[gmock-1.7.0.zip]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of gmock-1.7.0.zip or
        gmock-1.7.0.zip.zip, and cannot find gmock-1.7.0.zip.ZIP, period.
=============================
Starting package list
=============================
Starting protobuf
Good MD5
Error

I have checked in /tmp/se/protobuf-3.0.0-beta-3.1 and can confirm gmock-1.7.0.zip exists, I've also re-downloaded and replaced from the github hosting. However it fails to see it in the directory. I'm digging around trying to see which piece of the install script is making the call to fetch gmock and replace it was an absolute path to the zip itself. Not sure if you are aware or have any immediate insight on how to resolve.

Can't wait to get this rolling and start playing :)

[B Watson]

On 9/26/16, Drew Diver <drew.j...@gmail.com> wrote:
> For some reason this package fails to pull gmock-1.7.0.zip and continuously

> [gmock-1.7.0.zip]
> End-of-central-directory signature not found. Either this file is not
> a zipfile, or it constitutes one disk of a multi-part archive. In the

Bet if you examine the gmock-1.7.0.zip it's downloading, it'll turn
out to be an HTML file with an error message (404 not found or such),
not a zip file at all.

If the same URL works in a browser, then the web server is doing stupid
stuff like checking the Referer header or User-agent string. If this
were SBo and not Studioware, and that turned out to really be the case,
I'd say it definitely counts as a bug and needs to be fixed by the
build maintainer. I dunno what the Studioware policy is for stuff like
that though.

[Drew Diver]

Ah yep.. running the file command on it reveals it, double clicking or opening in Firefox only loops me back to the /tmp/se/protobuf-3.0.0-beta-3.1 directory though, not sure if or how I can get the URL?

root@SLACK:/tmp/se/protobuf-3.0.0-beta-3.1> file gmock-1.7.0.zip
gmock-1.7.0.zip: HTML document, UTF-8 Unicode text, with very long lines

[David Woodfall]

>Ah yep.. running the file command on it reveals it, double clicking or
>opening in Firefox only loops me back to the
>/tmp/se/protobuf-3.0.0-beta-3.1 directory though, not sure if or how I can
>get the URL?
>

>root@SLACK:/tmp/se/protobuf-3.0.0-beta-3.1> *file *gmock*-1.7.0.zip *

>gmock-1.7.0.zip: HTML document, UTF-8 Unicode text, with very long lines
>
>
>On Monday, September 26, 2016 at 3:30:24 PM UTC-4, B Watson wrote:
>>

>> On 9/26/16, Drew Diver <drew.j...@gmail.com <javascript:>> wrote:
>> > For some reason this package fails to pull gmock-1.7.0.zip and
>> continuously
>>
>> > [gmock-1.7.0.zip]
>> > End-of-central-directory signature not found. Either this file is not
>> > a zipfile, or it constitutes one disk of a multi-part archive. In the

I've just updated protobuf to 3.1.0 which fixes the issue. I've also
added rubberband to the mixxx queue to fix some dependency issues.

You should:

sepkg -u
sepkg -q mixxx

>> Bet if you examine the gmock-1.7.0.zip it's downloading, it'll turn
>> out to be an HTML file with an error message (404 not found or such),
>> not a zip file at all.
>>
>> If the same URL works in a browser, then the web server is doing stupid
>> stuff like checking the Referer header or User-agent string. If this
>> were SBo and not Studioware, and that turned out to really be the case,
>> I'd say it definitely counts as a bug and needs to be fixed by the
>> build maintainer. I dunno what the Studioware policy is for stuff like
>> that though.

If gmock goes missing again I'll have to see about installing it as a
separate package I think, and perhaps hosting the source ourselves.
But let's see what happens.

Cheers

-Dave

[Drew Diver]

That did it! Thanks a lot everyone!

--
You received this message because you are subscribed to a topic in the Google Groups "Studioware" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/studioware/8BChFZ-vhrc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to studioware+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Drew Diver

drewdiver.com