* Package name    : golang-github-ibm-go-sdk-core
  Version         : 5.25.1
  Upstream Contact: International Business Machines
* URL             : https://github.com/IBM/go-sdk-core
* License         : Apache-2.0
  Programming Lang: Go
  Description     : core functionality for Go from the IBM OpenAPI SDK Generator

This project contains core functionality required by Go code generated
by the IBM Cloud OpenAPI SDK Generator (openapi-sdkgen).

The go-sdk-core project supports the following types of authentication:
    Basic Authentication
    Bearer Token Authentication
    Identity and Access Management (IAM) Authentication (grant type: apikey)
    Identity and Access Management (IAM) Authentication (grant type: assume)
    Container Authentication
    VPC Instance Authentication
    Cloud Pak for Data Authentication
    Multi-Cloud Saas Platform (MCSP) Authentication
    No Authentication (for testing)


Required by rclone
(S3 backend, backend/s3/ibm_signer.go)

To be maintained by the Go Packaging Team.

This is an automated message from the Debian DFSG, Licensing & New
Packages Team.

The Debian NEW review of golang-github-ibm-go-sdk-core 5.25.1-1 has been completed.

Decision: ACCEPTED
Reviewer: Andrew McMillan

Review comment:

Hi,

The LLM review about this not being made available on the /v5 seems like it might be something worth looking into.  If it's wrong about this please reply so I can give it some feedback...

Thanks!

Full review details: https://dfsg-new-queue.debian.org/reviews/golang-github-ibm-go-sdk-core

We believe that the bug you reported is fixed in the latest version of
golang-github-ibm-go-sdk-core, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1151238@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons <dparsons@debian.org> (supplier of updated golang-github-ibm-go-sdk-core package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 18 Oct 2026 21:46:25 +0200
Source: golang-github-ibm-go-sdk-core
Binary: golang-github-ibm-go-sdk-core-v5-dev
Architecture: source all
Version: 5.25.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Changed-By: Drew Parsons <dparsons@debian.org>
Description:
 golang-github-ibm-go-sdk-core-v5-dev - core functionality from the IBM OpenAPI SDK Generator (Go library
Closes: 1151238
Changes:
 golang-github-ibm-go-sdk-core (5.25.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1151238)
Checksums-Sha1:
 20fd62f0125f3286e0843834e69a277d315d21a8 2579 golang-github-ibm-go-sdk-core_5.25.1-1.dsc
 cecdffcae466724e8d27e1919a7463ad69013091 205419 golang-github-ibm-go-sdk-core_5.25.1.orig.tar.gz
 5ec72297164c3edf4d4faf149622a4d2050a850a 2888 golang-github-ibm-go-sdk-core_5.25.1-1.debian.tar.xz
 b0dd71d97c4e838a5826316959a644a946220275 124108 golang-github-ibm-go-sdk-core-v5-dev_5.25.1-1_all.deb
 05f4cd0ab1091b94317eb6b76a4be6d5615fbb90 8820 golang-github-ibm-go-sdk-core_5.25.1-1_amd64.buildinfo
Checksums-Sha256:
 b015780c36d17a785c7b9ed11807dbed8daa950be2344bde3a62d5bfc7561992 2579 golang-github-ibm-go-sdk-core_5.25.1-1.dsc
 707d0cc9543da5b7006800fb6ec9e0ba687a086de7d245844015076b19c6c56b 205419 golang-github-ibm-go-sdk-core_5.25.1.orig.tar.gz
 0c92a640d5ead940cb33003fde86efb7fadd283e42ac22ddf841eb0ab8aeb1fb 2888 golang-github-ibm-go-sdk-core_5.25.1-1.debian.tar.xz
 9650fc95b43cb16f78bf5f6ac54e1a018c06ff514c23294b69953d3a57658fb0 124108 golang-github-ibm-go-sdk-core-v5-dev_5.25.1-1_all.deb
 0b265092f6ad38efa5633b3fdc3430897c50e95c337d2712b324658b0c4c5900 8820 golang-github-ibm-go-sdk-core_5.25.1-1_amd64.buildinfo
Files:
 e893ab1b0e992138ce148743b5fcecfe 2579 golang optional golang-github-ibm-go-sdk-core_5.25.1-1.dsc
 132f18a64dfc07a64ef48acc245d7cbd 205419 golang optional golang-github-ibm-go-sdk-core_5.25.1.orig.tar.gz
 c4f292f88bcc801b7e99ad0746e5d911 2888 golang optional golang-github-ibm-go-sdk-core_5.25.1-1.debian.tar.xz
 d5d8c8cd050f0712863032a5a0c70597 124108 golang optional golang-github-ibm-go-sdk-core-v5-dev_5.25.1-1_all.deb
 97ce449185db157ed1d6636605ccb555 8820 golang optional golang-github-ibm-go-sdk-core_5.25.1-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmrVIm4ACgkQVz7x5L1a
AfpDQBAAip2XO73dj+Qy5thn8EtquAa+wtuAz2PQMTIT7itkEd+nN1iuB991USAI
TMNH33lEsIUyK4IqkbXTS4lqIPaeTRjrPdsbAtQpDL8sj7ZiKAQSUMSUd7rDWPsR
mygu41qbtMI4+dwe+/3aqQPJ1AIXb3o67HaSWrllb/bvz6Y1bw0ZmGyEHtWPnpxi
Jb5KSE+smfJlT2soP/KRrMQcQHWs+2vYYQqWfbE4a0V+m4afrlZr8sAsCBo3JkRH
DXXYQQ/reOT9LxPqou98L1425GW4dJFdD0g+c+axMl1ZTvXo3/ciS9SDqURsPtlm
E+kfEmZ8CjVo9TWc2JsRweUY7xGUGfS54OJ9D54anE5jA859rEGDXfLoctEHIqxt
cfckFnKDtAnwlA1cwtG8R/vui2Feh9LqtvZHmCCP4WCKQOSErL98rLt4l5PvQbnV
oqLp77bJhV4eNnntYycoypPAAoPRCbFzG15Pnrgs9Zoq2Yu6C5enNkZMYJ/M19xl
gU3zAL+R1Y/RKrxH4anluzLUwFpgqhzElS1XHTm0BEqlIbMsbrItcwcNWPSkuXCa
/5bODGOXoaw5f7nd/DJ8xjR+MhINXQAbavtHSlyhxkRa0n7Tj1c7bwuLnltivMdQ
hWf1dVVtBSoxcrKxer2dbA3g8m9AJQ1K+G55z3fuDGCrWMgbwP8=
=SYC9
-----END PGP SIGNATURE-----

It's not "wrong", but the situation is ambiguous.  We haven't had a
golang-github-ibm-go-sdk-core before, so this one provides /v5, and and
from one perspective that's that. No need to register the package name
with -v5.

We use version specific package names when there's ambiguity, or more
precisely when the multiple versions are actually packaged. More
commonly it happens when we start with the original release (implicitly
/v1), and then later upstream makes a /v2 release.  So we need to make a
-v2 package to distinguish the two. And sometimes we still want to keep 
using the /v1 API.

The case of golang-github-anacrolix-missinggo (/v1) is particularly
bizarre. golang-github-anacrolix-missinggo-v2-dev (v2) depends on
golang-github-anacrolix-missinggo (v1). That's bizarre enough, but it
just means missinggo-v2 is an extension of v1, it doesn't supersede it.
But that's not the truly bizarre thing, the truly bizarre thing is that
golang-github-anacrolix-missinggo (/v1) depends on
golang-github-anacrolix-missinggo-v2-dev (v2). Somehow it seems to work.

With golang-github-ibm-go-sdk-core we don't have any older (or newer)
version to conflict against. So the unversioned package works
(understood as /v5, as per the package version). We could rename it to
golang-github-ibm-go-sdk-core-v5 but nothing is conflicting if we don't.

Drew