From debian-bts-link at lists.debian.org Mon Jan 12 17:37:41 2026 From: debian-bts-link at lists.debian.org (debian-bts-link at lists.debian.org) Date: Mon, 12 Jan 2026 17:37:41 +0000 Subject: [Debian-iot-maintainers] [bts-link] source package src:libcoap3 Message-ID: <176823946189.342028.1496878788210678442.btslink@sonntag.debian.org> # # bts-link upstream status pull for source package src:libcoap3 # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-link at lists.debian.org # remote status report for #1124407 (http://bugs.debian.org/1124407) # Bug title: libcoap3: CVE-2025-34468 # * https://github.com/obgm/libcoap/pull/1737 # * remote status changed: (?) -> closed # * closed upstream tags 1124407 + fixed-upstream usertags 1124407 + status-closed thanks From owner at bugs.debian.org Mon Jan 12 18:06:10 2026 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 12 Jan 2026 18:06:10 +0000 Subject: [Debian-iot-maintainers] Processed: [bts-link] source package src:libcoap3 References: <176823946189.342028.1496878788210678442.btslink@sonntag.debian.org> Message-ID: Processing commands for control at bugs.debian.org: > # > # bts-link upstream status pull for source package src:libcoap3 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-link at lists.debian.org Setting user to debian-bts-link at lists.debian.org (was debian-bts-link at lists.debian.org). > # remote status report for #1124407 (http://bugs.debian.org/1124407) > # Bug title: libcoap3: CVE-2025-34468 > # * https://github.com/obgm/libcoap/pull/1737 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1124407 + fixed-upstream Bug #1124407 [src:libcoap3] libcoap3: CVE-2025-34468 Added tag(s) fixed-upstream. > usertags 1124407 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1124407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124407 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From bunk at debian.org Fri Jan 16 18:00:59 2026 From: bunk at debian.org (Adrian Bunk) Date: Fri, 16 Jan 2026 20:00:59 +0200 Subject: [Debian-iot-maintainers] Bug#1125723: liboauth2-0: ABI break without soname change Message-ID: <176858645934.3318662.11099029227915119249.reportbug@localhost> Package: liboauth2-0 Version: 2.2.0-1 Severity: serious Control: block 1125720 by -1 https://github.com/OpenIDC/liboauth2/commit/5dd88a09b988cbcf2d7834f37b65fb6b589c39aa bool oauth2_token_verify(oauth2_log_t *log, oauth2_http_request_t *request, oauth2_cfg_token_verify_t *verify, const char *token, - json_t **json_payload); + json_t **json_payload, + oauth2_http_status_code_t *status_code); The weird part is that oauth2_token_verify() does not even use the new parameter. From owner at bugs.debian.org Fri Jan 16 18:03:03 2026 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 16 Jan 2026 18:03:03 +0000 Subject: [Debian-iot-maintainers] Processed: liboauth2-0: ABI break without soname change References: <176858645934.3318662.11099029227915119249.reportbug@localhost> <176858645934.3318662.11099029227915119249.reportbug@localhost> Message-ID: Processing control commands: > block 1125720 by -1 Bug #1125720 [src:libapache2-mod-oauth2] libapache2-mod-oauth2 FTBFS with liboauth2 2.2.0 1125720 was not blocked by any bugs. 1125720 was not blocking any bugs. Added blocking bug(s) of 1125720: 1125723 -- 1125720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125720 1125723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125723 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From nicolas at babelouest.org Fri Jan 16 19:12:49 2026 From: nicolas at babelouest.org (Nicolas Mora) Date: Fri, 16 Jan 2026 14:12:49 -0500 Subject: [Debian-iot-maintainers] Bug#1125723: Processed: liboauth2-0: ABI break without soname change In-Reply-To: References: <176858645934.3318662.11099029227915119249.reportbug@localhost> <176858645934.3318662.11099029227915119249.reportbug@localhost> <176858645934.3318662.11099029227915119249.reportbug@localhost> Message-ID: <28384306-9477-4529-8e89-dc5b6f3356f3@babelouest.org> Hello, thanks for the bug report. The new upstream version 4.1.0 seems to fix the FTBFS with liboauth2 2.2.0. /Nicolas