Hi Daniel,
On 29/02/2024 8:43 pm, Daniel Swarbrick wrote:
Hi Maytham,
On 29.02.24 12:16, Maytham Alsudany wrote:
Could we avoid bumping the epoch by suffixing the version with the
git commit? e.g. for the case of azure-sdk-for-go, the next version
would be 68.0.0+git20240229.d33ad0-1s
I did
Hi Maytham,
On 29.02.24 12:16, Maytham Alsudany wrote:
Could we avoid bumping the epoch by suffixing the version with the git
commit? e.g. for the case of azure-sdk-for-go, the next version would be
68.0.0+git20240229.d33ad0-1s
I did this kind of thing previously for golang-github-azure-go-au
Hi Daniel,
On 29/02/2024 12:42 am, Daniel Swarbrick wrote:
In the case of azure-sdk-for-go, I see that upstream has tags in the
form of "sdk/azcore/vX.Y.Z" (among many others). Can we assume that
"azcore" is as close an analog as we are going to get to the former
simple "vX.Y.Z" tags?
Severa
The outdated golang-github-azure-azure-sdk-for-go is also now a blocker
for updated versions of Prometheus, which requires newer
azure-sdk-for-go since v2.48.0. We currently package v2.45.3, which is
an LTS release; current upstream Prometheus version is 2.50.1.
I am also pretty baffled by som
Source: golang-github-azure-azure-sdk-for-go
Severity: important
X-Debbugs-Cc: debian...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Go team,
The golang-github-azure-azure-sdk-for-go package is outdated, as
upstream have stopped versioning the SDK as a whole (last version
5 matches
Mail list logo
