[S3tools-general] Open issues for 1.5.0-beta

[Matt Domsch]

I think 1.5.0 is getting close to release. There are a few issues I'd
still like to see addressed before another beta/rc release though. Any
input to these would be appreciated.

Open Pull Requests that I think are close to being mergeable, but need a
little love:

* https://github.com/s3tools/s3cmd/pull/249
Fix incorrect content-header assignment and charset bug

adoliver said he'd take a crack at it.


Other Open Issues:

* Generically: unicode fixups.
It's not as simple as using LANG=en_US.UTF-8, but that's a good start, and
is the root cause of a lot of the bug reports recently.

* https://github.com/s3tools/s3cmd/issues/212
Regression: --exclude '*.*' --rinclude '^one_file#39; excludes all files


* https://github.com/s3tools/s3cmd/issues/37
s3cmd modify command
needs a patch, not just a bunch of +1s asking for the feature.


* https://github.com/s3tools/s3cmd/issues/269
s3cmd (1.5.0-beta1) on Windows and full file path with drive letter when
uploading a file

Windows support has atrophied significantly lately. I've fixed up a few
spots, adding abstractions to noop for code paths that don't exist on
Windows, but I'm amazed when it works at all. The test suite fails.


The other outstanding pull requests are not in a good shape to be pulled.
Each needs review for appropriateness, and updating to match current
upstream. If you have an outstanding pull request waiting for my action,
please review the comments I may have made, and adjust accordingly.

Newer (within a few patches of mainline) packages are available in Fedora
18, 19, 20, EPEL 6 updates-testing trees, and rawhide. Mikhail has offered
to push it to Debian experimental. Or just grab the master tree from
github.

Thanks,
Matt

[Matt Domsch]

Post by Matt Domsch
I think 1.5.0 is getting close to release. There are a few issues I'd
still like to see addressed before another beta/rc release though. Any
input to these would be appreciated.
Open Pull Requests that I think are close to being mergeable, but need a
* https://github.com/s3tools/s3cmd/pull/249
Fix incorrect content-header assignment and charset bug

A fix is in upstream master now for this.

Post by Matt Domsch
* Generically: unicode fixups.
It's not as simple as using LANG=en_US.UTF-8, but that's a good start, and
is the root cause of a lot of the bug reports recently.

I've found a few more of these. Tests and reports of success/failure will
be appreciated.

Post by Matt Domsch
* https://github.com/s3tools/s3cmd/issues/212
Regression: --exclude '*.*' --rinclude '^one_file#39; excludes all files

I just committed a fix for this. To exclude a directory, use
--exclude=somedir/ (trailing forward slash).

Post by Matt Domsch
* https://github.com/s3tools/s3cmd/issues/37
s3cmd modify command
needs a patch, not just a bunch of +1s asking for the feature.

No change.

Post by Matt Domsch
* https://github.com/s3tools/s3cmd/issues/269
s3cmd (1.5.0-beta1) on Windows and full file path with drive letter when
uploading a file

Windows support has atrophied significantly lately. I've fixed up a few

Post by Matt Domsch
spots, adding abstractions to noop for code paths that don't exist on
Windows, but I'm amazed when it works at all. The test suite fails.

I haven't done anything about this. As no one else has stepped up, I say
we release as-is and let users complain. Or point them at other tools that
do work on Windows.

Thanks,
Matt

[Matt Domsch]

I expect a -beta2 or maybe even call it 1.5.0 "real soon now". Please
download github.com/s3tools/s3cmd master branch and verify that it still
works for your use cases, and file bugs at github.com if not. It's a good
as I can make it for now.

Thanks,
Matt

Post by Matt Domsch

Post by Matt Domsch
I think 1.5.0 is getting close to release. There are a few issues I'd
still like to see addressed before another beta/rc release though. Any
input to these would be appreciated.
Open Pull Requests that I think are close to being mergeable, but need a
* https://github.com/s3tools/s3cmd/pull/249
Fix incorrect content-header assignment and charset bug

A fix is in upstream master now for this.

Post by Matt Domsch
* Generically: unicode fixups.
It's not as simple as using LANG=en_US.UTF-8, but that's a good start,
and is the root cause of a lot of the bug reports recently.

I've found a few more of these. Tests and reports of success/failure will
be appreciated.

Post by Matt Domsch
* https://github.com/s3tools/s3cmd/issues/212
Regression: --exclude '*.*' --rinclude '^one_file#39; excludes all files

I just committed a fix for this. To exclude a directory, use
--exclude=somedir/ (trailing forward slash).

Post by Matt Domsch
* https://github.com/s3tools/s3cmd/issues/37
s3cmd modify command
needs a patch, not just a bunch of +1s asking for the feature.

No change.

Post by Matt Domsch
* https://github.com/s3tools/s3cmd/issues/269
s3cmd (1.5.0-beta1) on Windows and full file path with drive letter when
uploading a file

Windows support has atrophied significantly lately. I've fixed up a few

Post by Matt Domsch
spots, adding abstractions to noop for code paths that don't exist on
Windows, but I'm amazed when it works at all. The test suite fails.

I haven't done anything about this. As no one else has stepped up, I say
we release as-is and let users complain. Or point them at other tools that
do work on Windows.
Thanks,
Matt