#47195 closed update (fixed)
vcs_blackbox @1.20150318 Update to latest upstream
Reported by: | tal@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch maintainer | Cc: | ryandesign (Ryan Carsten Schmidt) |
Port: | vcs_blackbox |
Description
New upstream of vcs_blackbox. github.setup and checksums updated.
Attachments (1)
Change History (6)
Changed 10 years ago by tal@…
Attachment: | Portfile-vcs_blackbox.diff added |
---|
comment:1 Changed 10 years ago by mf2k (Frank Schima)
Keywords: | haspatch added |
---|---|
Version: | 2.3.3 |
comment:2 Changed 10 years ago by neverpanic (Clemens Lang)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Committed in r134130. The Id line change doesn't really matter, because svn will ignore and overwrite the change anyway.
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
Replying to tal@…:
github.setup and checksums updated.
You didn't, actually, update the checksums, yet the old checksums seem to match. Which suggests to me that this version is byte-for-byte identical to the previous one and there was no reason to update to it.
comment:4 Changed 10 years ago by tal@…
When the Portfile refers to a github label, what does the checksum actually mean?
comment:5 Changed 10 years ago by neverpanic (Clemens Lang)
MacPorts doesn't actually use git to fetch sources from github, unless the maintainer specifically requests that. Instead, we use tarballs that github auto-generates for each commit or tag. The checksums are for the tarball github generates for the tag. Since the tag changed, but the tarball contents didn't (because the checksum would have changed if they did), Ryan concluded the update was actually a no-op.
Thanks, but please do not change the
$Id: $
line.