golang-opentelemetry-otel - Debian Package Tracker

general

source: golang-opentelemetry-otel (main)
version: 1.46.0-2
maintainer: Debian Go Packaging Team (DMD)
uploaders: Shengjing Zhu [DMD]
arch: all
std-ver: 4.7.4
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

oldstable: 1.1.0-2
stable: 1.31.0-4
testing: 1.46.0-2
unstable: 1.46.0-2

versioned links

1.1.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.31.0-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.46.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

golang-opentelemetry-otel-dev

action needed

Marked for autoremoval on 22 November due to golang-github-prometheus-client-golang: #1150442 high

Version 1.46.0-2 of golang-opentelemetry-otel is marked for autoremoval from testing on Sun 22 Nov 2026. It depends (transitively) on golang-github-prometheus-client-golang, affected by #1150442. You should try to prevent the removal by fixing these RC bugs.

Created: 2026-10-16 Last update: 2026-10-18 09:00

A new upstream version is available: 1.47.0 high

A new upstream version 1.47.0 is available, you should consider packaging it.

Created: 2026-10-03 Last update: 2026-10-18 03:30

4 security issues in sid high

There are 4 open security issues in sid.

4 important issues:

CVE-2026-45404: OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 0.11.0 through 1.44.0, the OpenTracing bridge's bridgeSpan contains an unsynchronized extraBaggageItems map which can cause a panic. Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can trigger a fatal runtime error—such as concurrent map read and map write or concurrent map iteration and map write—terminating the process and causing denial of service. This issue is fixed in version 1.45.0.
CVE-2026-81870: OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.
CVE-2026-81871: OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the exporters/otlp/otlplog/otlploggrpc package loads OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE, OTEL_EXPORTER_OTLP_CERTIFICATE, and related client certificate environment variables through loadEnvTLS into cfg.tlsCfg, but newGRPCDialOptions does not apply cfg.tlsCfg when creating gRPC transport credentials. The environment-only TLS path instead uses credentials.NewTLS with system roots and no configured client certificate, bypassing intended private CA pinning and mutual TLS unless the application also supplies WithTLSCredentials. A network attacker able to intercept or spoof the collector connection with a system-trusted certificate can read or alter log telemetry. This issue is fixed in version 0.21.0.
CVE-2026-81872: OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the go.opentelemetry.io/otel/sdk/log BatchingProcessor can enter a tight CPU loop when attacker-driven log emission fills its asynchronous export buffer while the exporter is backpressured. NewBatchingProcessor wraps the exporter with newBufferExporter(exporter, 1), and the poll loop calls queue.TryDequeue and bufferExporter.EnqueueExport before immediately signaling pollTrigger whenever the queue remains at or above batchSize. Because a failed nonblocking EnqueueExport leaves the queue length unchanged, the processor repeatedly retries without waiting for its ticker, exhausting CPU and degrading or denying service in the embedding process. This issue is fixed in version 0.21.0.

Created: 2026-06-05 Last update: 2026-10-09 08:30

4 security issues in forky high

There are 4 open security issues in forky.

4 important issues:

CVE-2026-45404: OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 0.11.0 through 1.44.0, the OpenTracing bridge's bridgeSpan contains an unsynchronized extraBaggageItems map which can cause a panic. Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can trigger a fatal runtime error—such as concurrent map read and map write or concurrent map iteration and map write—terminating the process and causing denial of service. This issue is fixed in version 1.45.0.
CVE-2026-81870: OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.
CVE-2026-81871: OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the exporters/otlp/otlplog/otlploggrpc package loads OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE, OTEL_EXPORTER_OTLP_CERTIFICATE, and related client certificate environment variables through loadEnvTLS into cfg.tlsCfg, but newGRPCDialOptions does not apply cfg.tlsCfg when creating gRPC transport credentials. The environment-only TLS path instead uses credentials.NewTLS with system roots and no configured client certificate, bypassing intended private CA pinning and mutual TLS unless the application also supplies WithTLSCredentials. A network attacker able to intercept or spoof the collector connection with a system-trusted certificate can read or alter log telemetry. This issue is fixed in version 0.21.0.
CVE-2026-81872: OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the go.opentelemetry.io/otel/sdk/log BatchingProcessor can enter a tight CPU loop when attacker-driven log emission fills its asynchronous export buffer while the exporter is backpressured. NewBatchingProcessor wraps the exporter with newBufferExporter(exporter, 1), and the poll loop calls queue.TryDequeue and bufferExporter.EnqueueExport before immediately signaling pollTrigger whenever the queue remains at or above batchSize. Because a failed nonblocking EnqueueExport leaves the queue length unchanged, the processor repeatedly retries without waiting for its ticker, exhausting CPU and degrading or denying service in the embedding process. This issue is fixed in version 0.21.0.

Created: 2026-04-09 Last update: 2026-10-09 08:30

24 new commits since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 84dea9176ae2a8216ec4aa48ee7c601a1d1b020b
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Fri Oct 2 17:50:39 2026 -0400

    Update changelog for 1.46.0-2 release

commit fd347a1e56dbb40056421936abcf4f83e2d03aa0
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Fri Oct 2 14:16:43 2026 -0400

    debian/control: upgrade to debhelper-compat (= 14)

commit 5f008374ee646ef3f03a99f278763fd149903647
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Fri Oct 2 14:07:03 2026 -0400

    d/patches: clean up and standardize DEP-3 headers

commit fbcbfd20172051d16a5a79118abbc8bc76cd7e32
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Fri Oct 2 14:04:07 2026 -0400

    d/lintian-overrides: suppress package-contains-documentation-outside-usr-share-doc

commit 4b830ffdd5d866e3c1cdb053b6655fc8fb2b597f
Merge: 96b1a73cd9 feda8c47e4
Author: Reinhard Tartler <siretart@tauware.de>
Date:   Fri Oct 2 13:00:00 2026 -0400

    Merge commit 'feda8c47e48a847764d7a076acc24693eb4e2245' into debian/sid
    
    # Conflicts:
    #       debian/changelog
    #       debian/watch

commit 96b1a73cd9eef804d0adec1688e00ebf2328b05d
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Fri Oct 2 13:11:21 2026 +0200

    d/changelog: prepare 1.46.0-1 for unstable
    
    1.46.0-1~exp1 has been in experimental since 2026-09-27, so the unstable
    entry goes on top of it.
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit 49c694bb057c06c0cfbd7dcd521babb9eda27b70
Merge: 44857760ad 4232d3a7e6
Author: Andrew Lee (李健秋) <ajqlee@debian.org>
Date:   Sun Sep 27 22:01:09 2026 +0200

    Merge branch 'debian/experimental' into 'debian/experimental'
    
    golang-opentelemetry-otel 1.46.0-1~exp1
    
    See merge request go-team/packages/golang-opentelemetry-otel!4

commit 4232d3a7e6ce01cc6eed49a1fbeccafbdb483132
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Tue Sep 22 16:07:18 2026 +0200

    d/control: add back golang-github-masterminds-semver-dev
    
    schema/internal/parser_checks.go imports github.com/Masterminds/semver/v3
    and schema/go.mod requires it, but the dependency was dropped in the July
    cleanup. sbuild does not notice because another build dependency pulls
    the package into the chroot; the autopkgtest installs only Depends and
    fails with 'cannot find package github.com/Masterminds/semver/v3'.
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
    (cherry picked from commit 45f12be59c4593eddbbe19836043f7b7518ac2b9)

commit 3a8de349b9e3a55ec6646f59aca7fb721ed16b61
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Tue Sep 22 15:02:27 2026 +0200

    d/salsa-ci.yml: switch to the standard Salsa CI pipeline
    
    The project CI configuration path now points at debian/salsa-ci.yml, so
    replace the pkg-go archive test job with the standard pipeline.
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
    (cherry picked from commit 73deed6cc309c812412fe1651d5a22bbe8eb3aa6)

commit a5c2c344260ee9b828d9b5d44690fcaba46823f5
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Tue Sep 22 14:16:47 2026 +0200

    d/control: build against golang-github-cespare-xxhash-v2-dev
    
    Andrew Lee renamed the source and binary in 2.3.0-1, now in unstable.
    The new package ships the module at github.com/cespare/xxhash/v2, which
    is the path go.mod imports, while golang-github-cespare-xxhash-dev ships
    the v2 module under the non-v2 path.
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
    (cherry picked from commit 5f0f0ce24733842b2bba527adc71184901dd82ea)

commit 599063bb77062cab449684e8c6b405ec8f4a4ff2
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Sep 21 18:50:47 2026 +0200

    d/control: bump prometheus-dev Breaks to 3.5.3+ds1-6~
    
    3.5.3+ds1-5 also went to unstable without the semconv v1.43.0 update;
    it was a kube-openapi dependency change. The semconv bump moves to -6.
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
    (cherry picked from commit 1abfff777091270b073e35952e27f8bd32f1a839)

commit 5a01fcbdd93a1628bc5f93eba9e949a0971c7c34
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Sun Sep 20 21:58:50 2026 +0200

    d/changelog: target experimental as 1.46.0-1~exp1
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit b72c97418657612c1e3b18abef8bdd569bb99a16
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Sun Sep 20 21:58:32 2026 +0200

    d/control: bump prometheus-dev Breaks to 3.5.3+ds1-5~
    
    3.5.3+ds1-4 went to unstable without the semconv v1.43.0 update; that
    patch now lands in 3.5.3+ds1-5.
    
    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit 03324b4f2d94588b2e2151a86a7079be9465e2fa
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Wed Sep 16 01:16:34 2026 +0200

    d/changelog: reference the siso bug that this unblocks

commit 0e35663819e2abc0fda6c4c59d6efd30170bf2ef
Merge: 79d31318b9 ac2d3b23b0
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Tue Sep 15 18:40:00 2026 +0200

    Merge commit 'ac2d3b23' into debian/sid

commit 79d31318b9d722f68ed88edf164267bc0c513265
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Sep 14 21:16:39 2026 +0200

    d/control: bump Breaks for prometheus and alertmanager
    
    sdk/resource now uses semconv v1.43.0; prometheus 3.5.3+ds1-3 and
    alertmanager 0.33.1-4 pin semconv v1.40.0 and fail tracer provider
    setup with a conflicting schema URL.

commit f90e6610a94f5416c4b61d6d9ee04a93306f458f
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Sep 14 20:20:52 2026 +0200

    d/changelog: mark as team upload

commit aea5518709986d9f8df2be90a63d87012dd309dd
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Sep 14 20:07:55 2026 +0200

    New upstream version 1.46.0
    
    - Merge the unreleased 1.44.0-1 entry (CVE-2026-45287, CVE-2026-41178)
    - Drop 0001-Fix-import-comment.patch, applied upstream

commit c866a8fc5500dddd0ddabbbff8fff595d1a232a4
Merge: e406fbcf1e 4ae865da45
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Sep 14 20:06:30 2026 +0200

    Update upstream source from tag 'upstream/1.46.0'
    
    Update to upstream version '1.46.0'
    with Debian dir 7a84c88a64d9fa5c64d2da5d6b5442170d1cdc42

commit 4ae865da45eb4cb08201d949500deb1e5b58bf4f
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Sep 14 20:06:30 2026 +0200

    New upstream version 1.46.0

commit e406fbcf1e5ac367e2562721ef67920b2f20c113
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Sep 14 20:06:06 2026 +0200

    d/watch: use GitHub refs API, ignore pre-releases and per-module tags
    
    The GitHub tags page only shows the latest tags, which are flooded by
    per-module tags (and release candidates), hiding the stable vX.Y.Z tags.

commit 7f2d2305ffc666f566d033609cfb1810b7174773
Author: Juan Manuel Mendez Rey <juan.mendezr@proton.me>
Date:   Mon Jun 8 04:01:38 2026 +0200

    New upstream version 1.44.0, fixing CVE-2026-45287 and CVE-2026-41178
    
    - CVE-2026-45287: file descriptor leak in schema ParseFile (Closes: #1139168)
    - CVE-2026-41178: DoS via oversized baggage headers (Closes: #1139167)
    - Bump Breaks for prometheus-alertmanager-dev and prometheus-dev
      due to semconv schema URL conflict (v1.40.0 vs v1.41.0)

commit f2f08fccf285458c61fb8fb14deb773f9c7ff82a
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Jun 8 04:09:44 2026 +0200

    New upstream version 1.44.0

commit 485e8c9b6526776a637a0df8bf4d4c8dcad232b3
Merge: 252efa1f08 f2f08fccf2
Author: Juan Manuel Méndez Rey <juan.mendezr@proton.me>
Date:   Mon Jun 8 04:09:44 2026 +0200

    Update upstream source from tag 'upstream/1.44.0'
    
    Update to upstream version '1.44.0'
    with Debian dir d7fd5ec5ddadaced44b8fd11c19d1b5dbce7d352

Created: 2026-07-19 Last update: 2026-10-16 07:30

1 open merge request in Salsa normal

There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2026-10-08 Last update: 2026-10-08 03:20

lintian reports 1 warning normal

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2026-10-03 Last update: 2026-10-03 12:01

8 low-priority security issues in trixie low

There are 8 open security issues in trixie.

8 issues left for the package maintainer to handle:

CVE-2026-39882: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.
CVE-2026-41178: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. Versions 1.41.0 and 1.43.0 removed raw-length rejection and it causes `Parse` to process arbitrarily large/invalid baggage headers and log errors, enabling DoS via oversized inputs. Versions 1.42.0 and 1.44.0 fix the issue.
CVE-2026-45287: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.0.17, `go.opentelemetry.io/otel/schema/v1.0` and `go.opentelemetry.io/otel/schema/v1.1` leaks one file descriptor on each successful `ParseFile` call. `ParseFile` opens the schema file and passes it to `Parse` without closing it; repeated parsing in a long-running process can exhaust the process file descriptor limit and cause denial of service. Exploitation depends on a consuming application exposing repeated schema parsing to an attacker-controlled path. Version 0.0.17 contains a patch for the issue.
CVE-2026-45404: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 0.11.0 through 1.44.0, the OpenTracing bridge's bridgeSpan contains an unsynchronized extraBaggageItems map which can cause a panic. Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can trigger a fatal runtime error—such as concurrent map read and map write or concurrent map iteration and map write—terminating the process and causing denial of service. This issue is fixed in version 1.45.0.
CVE-2026-81869: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.10.0 until 1.33.0, the sdk/trace/span.go attribute truncation path can fail to enforce AttributeValueLengthLimit for string and string-slice attributes containing the valid Unicode replacement character U+FFFD. safeTruncateValidUTF8 treats the valid replacement rune as invalid UTF-8 and returns the original input, while strings.ToValidUTF8 leaves that valid rune unchanged, so a second safeTruncate attempt can also return the oversized value. An attacker who controls span attribute content can retain values longer than the configured limit, increasing per-span memory use and weakening denial-of-service protection in the instrumented process. This issue is fixed in version 1.33.0.
CVE-2026-81870: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.
CVE-2026-81871: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the exporters/otlp/otlplog/otlploggrpc package loads OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE, OTEL_EXPORTER_OTLP_CERTIFICATE, and related client certificate environment variables through loadEnvTLS into cfg.tlsCfg, but newGRPCDialOptions does not apply cfg.tlsCfg when creating gRPC transport credentials. The environment-only TLS path instead uses credentials.NewTLS with system roots and no configured client certificate, bypassing intended private CA pinning and mutual TLS unless the application also supplies WithTLSCredentials. A network attacker able to intercept or spoof the collector connection with a system-trusted certificate can read or alter log telemetry. This issue is fixed in version 0.21.0.
CVE-2026-81872: (needs triaging) OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the go.opentelemetry.io/otel/sdk/log BatchingProcessor can enter a tight CPU loop when attacker-driven log emission fills its asynchronous export buffer while the exporter is backpressured. NewBatchingProcessor wraps the exporter with newBufferExporter(exporter, 1), and the poll loop calls queue.TryDequeue and bufferExporter.EnqueueExport before immediately signaling pollTrigger whenever the queue remains at or above batchSize. Because a failed nonblocking EnqueueExport leaves the queue length unchanged, the processor repeatedly retries without waiting for its ticker, exhausting CPU and degrading or denying service in the embedding process. This issue is fixed in version 0.21.0.

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-04-09 Last update: 2026-10-09 08:30

news

[rss feed]

[2026-10-09] golang-opentelemetry-otel 1.46.0-2 MIGRATED to testing (Debian testing watch)
[2026-10-02] Accepted golang-opentelemetry-otel 1.46.0-2 (source) into unstable (Reinhard Tartler)
[2026-09-27] Accepted golang-opentelemetry-otel 1.46.0-1~exp1 (source) into experimental (Juan Manuel Méndez Rey) (signed by: 李健秋 Andrew Lee)
[2026-06-08] golang-opentelemetry-otel 1.43.0-4 MIGRATED to testing (Debian testing watch)
[2026-06-04] Accepted golang-opentelemetry-otel 1.43.0-4 (source) into unstable (Mathias Gibbens)
[2026-06-02] Accepted golang-opentelemetry-otel 1.43.0-3 (source) into unstable (Mathias Gibbens)
[2026-05-19] Accepted golang-opentelemetry-otel 1.43.0-2 (source) into unstable (Andrew Lee (李健秋)) (signed by: 李健秋 Andrew Lee)
[2026-05-17] Accepted golang-opentelemetry-otel 1.43.0-1 (source) into unstable (Andrew Lee (李健秋)) (signed by: 李健秋 Andrew Lee)
[2025-12-14] golang-opentelemetry-otel 1.31.0-6 MIGRATED to testing (Debian testing watch)
[2025-12-11] Accepted golang-opentelemetry-otel 1.31.0-6 (source) into unstable (Simon Josefsson)
[2025-08-21] golang-opentelemetry-otel 1.31.0-5 MIGRATED to testing (Debian testing watch)
[2025-08-18] Accepted golang-opentelemetry-otel 1.31.0-5 (source) into unstable (Daniel Swarbrick)
[2025-03-22] golang-opentelemetry-otel 1.31.0-4 MIGRATED to testing (Debian testing watch)
[2025-03-20] Accepted golang-opentelemetry-otel 1.31.0-4 (source) into unstable (Simon Josefsson)
[2024-11-06] golang-opentelemetry-otel 1.31.0-3 MIGRATED to testing (Debian testing watch)
[2024-11-01] Accepted golang-opentelemetry-otel 1.31.0-3 (source) into unstable (Reinhard Tartler)
[2024-10-31] Accepted golang-opentelemetry-otel 1.31.0-2 (source) into unstable (Reinhard Tartler)
[2024-10-21] Accepted golang-opentelemetry-otel 1.31.0-1 (source) into experimental (Reinhard Tartler)
[2024-08-30] golang-opentelemetry-otel 1.21.0-4 MIGRATED to testing (Debian testing watch)
[2024-08-27] Accepted golang-opentelemetry-otel 1.21.0-4 (source) into unstable (Shengjing Zhu)
[2024-08-18] golang-opentelemetry-otel 1.21.0-3 MIGRATED to testing (Debian testing watch)
[2024-08-15] Accepted golang-opentelemetry-otel 1.21.0-3 (source) into unstable (Shengjing Zhu)
[2024-08-07] golang-opentelemetry-otel 1.21.0-2 MIGRATED to testing (Debian testing watch)
[2024-07-25] Accepted golang-opentelemetry-otel 1.21.0-2 (source) into unstable (Mathias Gibbens)
[2024-06-30] Accepted golang-opentelemetry-otel 1.21.0-1 (source) into experimental (Reinhard Tartler)
[2024-06-15] Accepted golang-opentelemetry-otel 1.19.0-0 (source) into experimental (Reinhard Tartler)
[2024-06-06] Accepted golang-opentelemetry-otel 1.16.0-2 (source) into experimental (Reinhard Tartler)
[2023-06-20] golang-opentelemetry-otel 1.16.0-1 MIGRATED to testing (Debian testing watch)
[2023-06-15] Accepted golang-opentelemetry-otel 1.16.0-1 (source) into unstable (Shengjing Zhu)
[2022-11-03] Accepted golang-opentelemetry-otel 1.10.0-1 (source) into experimental (Thomas Goirand)

bugs [bug history graph]

all: 2
RC: 0
I&N: 2
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian (0, 1)
buildd: logs, reproducibility
popcon
browse source code
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.43.0-4build1