#44927 closed update (fixed)
s3cmd @1.0.1 update to 1.5.0-rc1
| Reported by: | rockettj@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | kurthindenburg (Kurt Hindenburg) | |
| Port: | s3cmd |
Description
Bump to the latest release.
Attachments (5)
Change History (16)
Changed 10 years ago by rockettj@…
| Attachment: | s3cmd_1.5.0-rc1.diff added |
|---|
comment:1 Changed 10 years ago by mf2k (Frank Schima)
| Cc: | rockettj@… removed |
|---|---|
| Port: | s3cmd added |
| Version: | 2.3.1 |
comment:2 Changed 10 years ago by mf2k (Frank Schima)
- And most importantly, we do not normally use rc versions. We like to use stable release versions. If this were a -devel port, then it could use that version.
comment:3 Changed 10 years ago by rockettj@…
Ok, thanks for the comments. I'll make the corrections.
Changed 10 years ago by rockettj@…
| Attachment: | s3cmd_1.5.0-rc1.2.diff added |
|---|
uses sha256 checksum and revision removed per review comments
comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Each distfile should be validated by at least two different checksum types. Usually we use rmd160 and sha256.
But yes, we should wait to update this port until a new official release is available. 1.5.0-rc1 is not an official release, it is a release canditate. The latest official release still seems to be 1.0.1.
comment:5 Changed 10 years ago by mf2k (Frank Schima)
Yes, sorry for the confusion. I implied, but did not state explicitly, that the rmd160 checksum needs to stay.
comment:6 Changed 10 years ago by rockettj@…
Thanks for your patience (my first submittal here). Should I close and reopen to add a s3cmd-devel or is ok to wait and update this ticket once 1.5.0 is released? I'll add the rmd160 back in.
comment:7 Changed 10 years ago by mf2k (Frank Schima)
It would be easiest to simply wait for the final 1.5.0 release. If you think that a s3cmd-devel is useful going forward, then it would be best to modify the current s3cmd port and add it as a sub-port.
comment:9 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)
It is still at 1.5.0-rc1; ping this trac # when it goes to 1.5.0 and we'll commit it.
Changed 9 years ago by rockettj@…
| Attachment: | s3cmd-1.5.1.2.diff added |
|---|
Changed 9 years ago by rockettj@…
| Attachment: | s3cmd-1.5.1.2.2.diff added |
|---|
Changed 9 years ago by rockettj@…
| Attachment: | s3cmd_1_5_2.diff added |
|---|
comment:10 Changed 9 years ago by rockettj@…
I've updated the diff for the current release version of s3cmd, 1.5.2. I've also added a livecheck.
comment:11 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Thanks done in r132842 - as a FYI, attaching a file doesn't send out an email so no one noticed you're earlier attachments.
Thanks. In the future, please fill in the Port field. As reporter, you do not need to Cc yourself.
Some comments:
revisionline should be deleted because it starts at 0 when increasing the version and that is the default value.