[Bug 2063031] Re: [noble] Not compatible with Python 3.12

Maia Everett 2063031 at bugs.launchpad.net
Sun Apr 21 12:10:18 UTC 2024


To reproduce under Noble:

1. sudo apt install s3cmd
2. s3cmd --configure, input credentials for any S3 bucket you own (a local Minio installation with Docker would do)
3. s3cmd ls s3://bucket-name

With the broken version 2.3.0-1:

TypeError: sequence item 1: expected str instance, bytes found

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    An unexpected error has occurred.
<snip>

With the patched version 2.3.0-1ubuntu1, the root directory of the
bucket is successfully listed.

Attaching debdiff for ubuntu-sponsors. I believe that this qualifies for
a pre-release freeze exception because it's a trivial bugfix-only
upload.

** Patch added: "s3cmd_2.3.0-1ubuntu1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/2063031/+attachment/5768756/+files/s3cmd_2.3.0-1ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2063031

Title:
  [noble] Not compatible with Python 3.12

Status in s3cmd package in Ubuntu:
  New

Bug description:
  Under Noble, s3cmd 2.3.0 is completely broken because of an
  incompatibility with Python 3.12, producing the exception:

  https://github.com/s3tools/s3cmd/issues/1343

  All operations fail with the error message:

  TypeError: sequence item 1: expected str instance, bytes found

  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
      An unexpected error has occurred.
    Please try reproducing the error using
    the latest s3cmd code from the git master
    branch found at:
      https://github.com/s3tools/s3cmd
    and have a look at the known issues list:
      https://github.com/s3tools/s3cmd/wiki/Common-known-issues-and-their-solutions-(FAQ)
    If the error persists, please report the
    above lines (removing any private
    info as necessary) to:
     s3tools-bugs at lists.sourceforge.net
  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  This issue has been fixed upstream in this commit:

  https://github.com/s3tools/s3cmd/commit/9ecb2d853c54f87c6a3ec0423986dcc1a80e4678

  which has been included in upstream release 2.4.0, released in
  December 2023. Unfortunately, it was not packaged in Debian, and it's
  too late in the release timeline to upload it directly into Noble.

  I'll prepare a patch for Noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/2063031/+subscriptions




More information about the Ubuntu-sponsors mailing list