Re: How do I check what is autobuilding successfully?

[Ryan Schmidt]

On Apr 26, 2018, at 15:48, Rainer Müller wrote:

> On 2018-04-26 22:31, Clemens Lang wrote:
>> | Error: Checksum (rmd160) mismatch for coffee-script-1.3.3.tar.gz
>> | Portfile checksum: coffee-script-1.3.3.tar.gz rmd160 
>> 22cf20180c06c92f5fdc223180ba94bb96b6ff7b
>> | Distfile checksum: coffee-script-1.3.3.tar.gz rmd160 
>> e069ff420bc2584015f4a412d5595f04c8be8df6
>> | DEBUG: Calculated (sha256) is 
>> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
>> | Error: Checksum (sha256) mismatch for coffee-script-1.3.3.tar.gz
>> | Portfile checksum: coffee-script-1.3.3.tar.gz sha256 
>> 21b6782b23e09e768ff8b440eeddb0c42c7ad94990d120a348bfd4ffaf6511e0
>> | Distfile checksum: coffee-script-1.3.3.tar.gz sha256 
>> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
>> | The correct checksum line may be:
>> | checksums   rmd160  e069ff420bc2584015f4a412d5595f04c8be8df6 \
>> | sha256  
>> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
>> | Error: Failed to checksum coffee-script: Unable to verify file checksums
>> 
>> Maybe a stealth update?
> 
> coffee-script is one of the ports affected by the git update at GitHub
> half a year ago.
> 
> https://trac.macports.org/ticket/54839

Actually the checksums changed because the GitHub project name changed from 
"coffee-script" to "coffeescript".

Re: How do I check what is autobuilding successfully?

[Perry E. Metzger]

On Thu, 26 Apr 2018 22:48:18 +0200 Rainer Müller
 wrote:
> coffee-script is one of the ports affected by the git update at
> GitHub half a year ago.
> 
> https://trac.macports.org/ticket/54839

But this implies that rethinkdb has been broken a long time and so I
shouldn't be overly worried about breaking the build.

I should have gone to Trac of course. It hasn't built in a long time.

https://trac.macports.org/query?0_port=rethinkdb&0_port_mode=~&0_status=%21closed=id=summary=port=status=owner=type=priority=time=changetime

Perry
-- 
Perry E. Metzgerpmetz...@macports.org

Re: How do I check what is autobuilding successfully?

[Rainer Müller]

On 2018-04-26 22:48, Rainer Müller wrote:
> On 2018-04-26 22:31, Clemens Lang wrote:
>> | Error: Checksum (rmd160) mismatch for coffee-script-1.3.3.tar.gz
>> | Portfile checksum: coffee-script-1.3.3.tar.gz rmd160 
>> 22cf20180c06c92f5fdc223180ba94bb96b6ff7b
>> | Distfile checksum: coffee-script-1.3.3.tar.gz rmd160 
>> e069ff420bc2584015f4a412d5595f04c8be8df6
>> | DEBUG: Calculated (sha256) is 
>> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
>> | Error: Checksum (sha256) mismatch for coffee-script-1.3.3.tar.gz
>> | Portfile checksum: coffee-script-1.3.3.tar.gz sha256 
>> 21b6782b23e09e768ff8b440eeddb0c42c7ad94990d120a348bfd4ffaf6511e0
>> | Distfile checksum: coffee-script-1.3.3.tar.gz sha256 
>> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
>> | The correct checksum line may be:
>> | checksums   rmd160  e069ff420bc2584015f4a412d5595f04c8be8df6 \
>> | sha256  
>> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
>> | Error: Failed to checksum coffee-script: Unable to verify file checksums
>>
>> Maybe a stealth update?
> 
> coffee-script is one of the ports affected by the git update at GitHub
> half a year ago.

Scratch that, it was fixed just yesterday.

Rainer

Re: How do I check what is autobuilding successfully?

[Rainer Müller]

On 2018-04-26 22:31, Clemens Lang wrote:
> | Error: Checksum (rmd160) mismatch for coffee-script-1.3.3.tar.gz
> | Portfile checksum: coffee-script-1.3.3.tar.gz rmd160 
> 22cf20180c06c92f5fdc223180ba94bb96b6ff7b
> | Distfile checksum: coffee-script-1.3.3.tar.gz rmd160 
> e069ff420bc2584015f4a412d5595f04c8be8df6
> | DEBUG: Calculated (sha256) is 
> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
> | Error: Checksum (sha256) mismatch for coffee-script-1.3.3.tar.gz
> | Portfile checksum: coffee-script-1.3.3.tar.gz sha256 
> 21b6782b23e09e768ff8b440eeddb0c42c7ad94990d120a348bfd4ffaf6511e0
> | Distfile checksum: coffee-script-1.3.3.tar.gz sha256 
> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
> | The correct checksum line may be:
> | checksums   rmd160  e069ff420bc2584015f4a412d5595f04c8be8df6 \
> | sha256  
> 509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
> | Error: Failed to checksum coffee-script: Unable to verify file checksums
> 
> Maybe a stealth update?

coffee-script is one of the ports affected by the git update at GitHub
half a year ago.

https://trac.macports.org/ticket/54839

Rainer

Re: How do I check what is autobuilding successfully?

[Clemens Lang]

Hi,

On Wed, Apr 25, 2018 at 02:58:13PM -0400, Perry E. Metzger wrote:
> There's a port I suspect hasn't built in a long while. How can I check
> on what is and isn't building on the buildbots?

Recently, we added build status reporting to commits in macports-ports.
If a port has been updated recently, you can go to the Portfile's change
history on GitHub and click the little status indicator icon next to the
commit.

In case of rethinkdb, see [1]. If you click the red X, you'll see that
none of the build succeeded. If you follow the links for the 'builder'
jobs you'll see that all of them failed in the 'install-dependencies'
step. Clicking the 'dependencies' link will show you that coffee-script
failed to install on all buildbots. You can also use the 'stdio' link to
get the full build output to figure out why coffee-script failed.

I'll spare you the work for this simple case, though:


| Error: Checksum (rmd160) mismatch for coffee-script-1.3.3.tar.gz
| Portfile checksum: coffee-script-1.3.3.tar.gz rmd160 
22cf20180c06c92f5fdc223180ba94bb96b6ff7b
| Distfile checksum: coffee-script-1.3.3.tar.gz rmd160 
e069ff420bc2584015f4a412d5595f04c8be8df6
| DEBUG: Calculated (sha256) is 
509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
| Error: Checksum (sha256) mismatch for coffee-script-1.3.3.tar.gz
| Portfile checksum: coffee-script-1.3.3.tar.gz sha256 
21b6782b23e09e768ff8b440eeddb0c42c7ad94990d120a348bfd4ffaf6511e0
| Distfile checksum: coffee-script-1.3.3.tar.gz sha256 
509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
| The correct checksum line may be:
| checksums   rmd160  e069ff420bc2584015f4a412d5595f04c8be8df6 \
| sha256  
509797e0bbfa534f7ea1c67d6df9f638c30d28f76f75cc74adbdc10096992f4a
| Error: Failed to checksum coffee-script: Unable to verify file checksums

Maybe a stealth update?

[1] 
https://github.com/macports/macports-ports/commits/master/databases/rethinkdb/Portfile

-- 
Clemens

Re: How do I check what is autobuilding successfully?

[Ryan Schmidt]

On Apr 25, 2018, at 16:50, Jan Stary wrote:

> On Apr 25 14:44:51, Ryan Schmidt wrote:
> 
>> On Apr 25, 2018, at 14:26, Perry E. Metzger wrote:
>> 
>>> So the package in question is "rethinkdb",
>> 
>>> packages.macports.org doesn't seem to show the package there. Does
>>> that mean it indeed hasn't built in a long time?
>> 
>> In this case, it means rethinkdb is not distributable.
> 
> wat makes a package distributable (or not)?

Whether its license, and those of its recursive dependencies, allow it. Read 
the license texts if you like. The GNU General Public License, in particular, 
causes some software to be non-distributable. This is the script we use which 
comprises our understanding of license compatibility:

https://github.com/macports/macports-infrastructure/blob/master/jobs/port_binary_distributable.tcl

This is what the buildbot runs to determine whether it is permitted for us to 
distribute a binary we have built.

Re: How do I check what is autobuilding successfully?

[Jan Stary]

On Apr 25 14:44:51, ryandes...@macports.org wrote:
> 
> On Apr 25, 2018, at 14:26, Perry E. Metzger wrote:
> 
> > So the package in question is "rethinkdb",
> 
> > packages.macports.org doesn't seem to show the package there. Does
> > that mean it indeed hasn't built in a long time?
> 
> In this case, it means rethinkdb is not distributable.

wat makes a package distributable (or not)?

Re: How do I check what is autobuilding successfully?

[Ryan Schmidt]

On Apr 25, 2018, at 14:26, Perry E. Metzger wrote:

> So the package in question is "rethinkdb",

> packages.macports.org doesn't seem to show the package there. Does
> that mean it indeed hasn't built in a long time?

In this case, it means rethinkdb is not distributable.

Re: How do I check what is autobuilding successfully?

[Perry E. Metzger]

On Wed, 25 Apr 2018 12:13:37 -0700 Ken Cunningham
 wrote:
> On 2018-04-25, at 11:58 AM, Perry E. Metzger wrote:
> 
> > There's a port I suspect hasn't built in a long while. How can I
> > check on what is and isn't building on the buildbots?
> 
> check packages.macports.org and see if it's there

So the package in question is "rethinkdb", which is on the list of
things that need (in theory) to get updated from protobuf-cpp to
protobuf3-cpp. It looks like our version is really ancient and can't
possibly build right now -- though if someone else can try building
it to confirm that I'm right and it won't build I'd appreciate it.

packages.macports.org doesn't seem to show the package there. Does
that mean it indeed hasn't built in a long time? Given that,
rather than update it, I'm going to suggest we remove it as it seems
beyond abandoned.

Perry
-- 
Perry E. Metzgerpmetz...@macports.org

Re: How do I check what is autobuilding successfully?

[Ken Cunningham]

On 2018-04-25, at 11:58 AM, Perry E. Metzger wrote:

> There's a port I suspect hasn't built in a long while. How can I
> check on what is and isn't building on the buildbots?
> 
> -- 
> Perry E. Metzger  pmetz...@macports.org

check packages.macports.org and see if it's there

and if not

ask Ryan for login rights to the buildbots and force a build.

Ken

How do I check what is autobuilding successfully?

[Perry E. Metzger]

There's a port I suspect hasn't built in a long while. How can I
check on what is and isn't building on the buildbots?

-- 
Perry E. Metzgerpmetz...@macports.org