libsoup2.4 - Debian Package Tracker

general

source: libsoup2.4 (main)
version: 2.74.3-10.1
maintainer: Debian GNOME Maintainers (archive) (DMD)
uploaders: Iain Lane [DMD] – Jeremy Bicha [DMD] – Sebastien Bacher [DMD]
arch: all any
std-ver: 4.7.0
VCS: Git (Browse, QA)

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

[pool directory]

o-o-stable: 2.72.0-2
o-o-sec: 2.72.0-2+deb11u2
oldstable: 2.74.3-1+deb12u1
stable: 2.74.3-10.1
unstable: 2.74.3-10.1

versioned links

2.72.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.72.0-2+deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.74.3-1+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.74.3-10.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

gir1.2-soup-2.4
libsoup-2.4-1
libsoup-gnome-2.4-1
libsoup-gnome2.4-dev
libsoup2.4-common
libsoup2.4-dev
libsoup2.4-doc
libsoup2.4-tests

action needed

Debci reports failed tests high

unstable: fail (log)
The tests ran in 0:08:31
Last run: 2025-11-05T08:21:17.000Z
Previous status: unknown

testing: pass (log)
The tests ran in 0:03:15
Last run: 2025-09-14T00:09:03.000Z
Previous status: unknown

stable: fail (log)
The tests ran in 0:08:38
Last run: 2025-11-08T13:57:35.000Z
Previous status: unknown

Created: 2025-11-05 Last update: 2025-11-15 18:32

9 security issues in sid high

There are 9 open security issues in sid.

9 important issues:

CVE-2025-4035: A flaw was found in libsoup. When handling cookies, libsoup clients mistakenly allow cookies to be set for public suffix domains if the domain contains at least two components and includes an uppercase character. This bypasses public suffix protections and could allow a malicious website to set cookies for domains it does not own, potentially leading to integrity issues such as session fixation.
CVE-2025-4476: A denial-of-service vulnerability has been identified in the libsoup HTTP client library. This flaw can be triggered when a libsoup client receives a 401 (Unauthorized) HTTP response containing a specifically crafted domain parameter within the WWW-Authenticate header. Processing this malformed header can lead to a crash of the client application using libsoup. An attacker could exploit this by setting up a malicious HTTP server. If a user's application using the vulnerable libsoup library connects to this malicious server, it could result in a denial-of-service. Successful exploitation requires tricking a user's client application into connecting to the attacker's malicious server.
CVE-2025-4945: A flaw was found in the cookie parsing logic of the libsoup HTTP library, used in GNOME applications and other software. The vulnerability arises when processing the expiration date of cookies, where a specially crafted value can trigger an integer overflow. This may result in undefined behavior, allowing an attacker to bypass cookie expiration logic, causing persistent or unintended cookie behavior. The issue stems from improper validation of large integer inputs during date arithmetic operations within the cookie parsing routines.
CVE-2025-4948: A flaw was found in the soup_multipart_new_from_message() function of the libsoup HTTP library, which is commonly used by GNOME and other applications to handle web communications. The issue occurs when the library processes specially crafted multipart messages. Due to improper validation, an internal calculation can go wrong, leading to an integer underflow. This can cause the program to access invalid memory and crash. As a result, any application or server using libsoup could be forced to exit unexpectedly, creating a denial-of-service (DoS) risk.
CVE-2025-4969: A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).
CVE-2025-9901: A flaw was found in libsoup’s caching mechanism, SoupCache, where the HTTP Vary header is ignored when evaluating cached responses. This header ensures that responses vary appropriately based on request headers such as language or authentication. Without this check, cached content can be incorrectly reused across different requests, potentially exposing sensitive user information. While the issue is unlikely to affect everyday desktop use, it could result in confidentiality breaches in proxy or multi-user environments.
CVE-2025-32049: A flaw was found in libsoup. The SoupWebsocketConnection may accept a large WebSocket message, which may cause libsoup to allocate memory and lead to a denial of service (DoS).
CVE-2025-32907: A flaw was found in libsoup. The implementation of HTTP range requests is vulnerable to a resource consumption attack. This flaw allows a malicious client to request the same range many times in a single HTTP request, causing the server to use large amounts of memory. This does not allow for a full denial of service.
CVE-2025-46421: A flaw was found in libsoup. When libsoup clients encounter an HTTP redirect, they mistakenly send the HTTP Authorization header to the new host that the redirection points to. This allows the new host to impersonate the user to the original host that issued the redirect.

Created: 2025-04-03 Last update: 2025-11-04 21:33

10 security issues in bullseye high

There are 10 open security issues in bullseye.

10 important issues:

CVE-2025-4035: A flaw was found in libsoup. When handling cookies, libsoup clients mistakenly allow cookies to be set for public suffix domains if the domain contains at least two components and includes an uppercase character. This bypasses public suffix protections and could allow a malicious website to set cookies for domains it does not own, potentially leading to integrity issues such as session fixation.
CVE-2025-4476: A denial-of-service vulnerability has been identified in the libsoup HTTP client library. This flaw can be triggered when a libsoup client receives a 401 (Unauthorized) HTTP response containing a specifically crafted domain parameter within the WWW-Authenticate header. Processing this malformed header can lead to a crash of the client application using libsoup. An attacker could exploit this by setting up a malicious HTTP server. If a user's application using the vulnerable libsoup library connects to this malicious server, it could result in a denial-of-service. Successful exploitation requires tricking a user's client application into connecting to the attacker's malicious server.
CVE-2025-4945: A flaw was found in the cookie parsing logic of the libsoup HTTP library, used in GNOME applications and other software. The vulnerability arises when processing the expiration date of cookies, where a specially crafted value can trigger an integer overflow. This may result in undefined behavior, allowing an attacker to bypass cookie expiration logic, causing persistent or unintended cookie behavior. The issue stems from improper validation of large integer inputs during date arithmetic operations within the cookie parsing routines.
CVE-2025-4948: A flaw was found in the soup_multipart_new_from_message() function of the libsoup HTTP library, which is commonly used by GNOME and other applications to handle web communications. The issue occurs when the library processes specially crafted multipart messages. Due to improper validation, an internal calculation can go wrong, leading to an integer underflow. This can cause the program to access invalid memory and crash. As a result, any application or server using libsoup could be forced to exit unexpectedly, creating a denial-of-service (DoS) risk.
CVE-2025-4969: A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).
CVE-2025-9901: A flaw was found in libsoup’s caching mechanism, SoupCache, where the HTTP Vary header is ignored when evaluating cached responses. This header ensures that responses vary appropriately based on request headers such as language or authentication. Without this check, cached content can be incorrectly reused across different requests, potentially exposing sensitive user information. While the issue is unlikely to affect everyday desktop use, it could result in confidentiality breaches in proxy or multi-user environments.
CVE-2025-32049: A flaw was found in libsoup. The SoupWebsocketConnection may accept a large WebSocket message, which may cause libsoup to allocate memory and lead to a denial of service (DoS).
CVE-2025-32907: A flaw was found in libsoup. The implementation of HTTP range requests is vulnerable to a resource consumption attack. This flaw allows a malicious client to request the same range many times in a single HTTP request, causing the server to use large amounts of memory. This does not allow for a full denial of service.
CVE-2025-46420: A flaw was found in libsoup. It is vulnerable to memory leaks in the soup_header_parse_quality_list() function when parsing a quality list that contains elements with all zeroes.
CVE-2025-46421: A flaw was found in libsoup. When libsoup clients encounter an HTTP redirect, they mistakenly send the HTTP Authorization header to the new host that the redirection points to. This allows the new host to impersonate the user to the original host that issued the redirect.

Created: 2025-04-03 Last update: 2025-11-04 21:33

lintian reports 1 error and 2 warnings high

Lintian reports 1 error and 2 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2025-05-03 Last update: 2025-09-10 06:03

9 security issues in forky high

There are 9 open security issues in forky.

9 important issues:

CVE-2025-4035: A flaw was found in libsoup. When handling cookies, libsoup clients mistakenly allow cookies to be set for public suffix domains if the domain contains at least two components and includes an uppercase character. This bypasses public suffix protections and could allow a malicious website to set cookies for domains it does not own, potentially leading to integrity issues such as session fixation.
CVE-2025-4476: A denial-of-service vulnerability has been identified in the libsoup HTTP client library. This flaw can be triggered when a libsoup client receives a 401 (Unauthorized) HTTP response containing a specifically crafted domain parameter within the WWW-Authenticate header. Processing this malformed header can lead to a crash of the client application using libsoup. An attacker could exploit this by setting up a malicious HTTP server. If a user's application using the vulnerable libsoup library connects to this malicious server, it could result in a denial-of-service. Successful exploitation requires tricking a user's client application into connecting to the attacker's malicious server.
CVE-2025-4945: A flaw was found in the cookie parsing logic of the libsoup HTTP library, used in GNOME applications and other software. The vulnerability arises when processing the expiration date of cookies, where a specially crafted value can trigger an integer overflow. This may result in undefined behavior, allowing an attacker to bypass cookie expiration logic, causing persistent or unintended cookie behavior. The issue stems from improper validation of large integer inputs during date arithmetic operations within the cookie parsing routines.
CVE-2025-4948: A flaw was found in the soup_multipart_new_from_message() function of the libsoup HTTP library, which is commonly used by GNOME and other applications to handle web communications. The issue occurs when the library processes specially crafted multipart messages. Due to improper validation, an internal calculation can go wrong, leading to an integer underflow. This can cause the program to access invalid memory and crash. As a result, any application or server using libsoup could be forced to exit unexpectedly, creating a denial-of-service (DoS) risk.
CVE-2025-4969: A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).
CVE-2025-9901: A flaw was found in libsoup’s caching mechanism, SoupCache, where the HTTP Vary header is ignored when evaluating cached responses. This header ensures that responses vary appropriately based on request headers such as language or authentication. Without this check, cached content can be incorrectly reused across different requests, potentially exposing sensitive user information. While the issue is unlikely to affect everyday desktop use, it could result in confidentiality breaches in proxy or multi-user environments.
CVE-2025-32049: A flaw was found in libsoup. The SoupWebsocketConnection may accept a large WebSocket message, which may cause libsoup to allocate memory and lead to a denial of service (DoS).
CVE-2025-32907: A flaw was found in libsoup. The implementation of HTTP range requests is vulnerable to a resource consumption attack. This flaw allows a malicious client to request the same range many times in a single HTTP request, causing the server to use large amounts of memory. This does not allow for a full denial of service.
CVE-2025-46421: A flaw was found in libsoup. When libsoup clients encounter an HTTP redirect, they mistakenly send the HTTP Authorization header to the new host that the redirection points to. This allows the new host to impersonate the user to the original host that issued the redirect.

Created: 2025-08-09 Last update: 2025-09-06 12:03

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 5-day delay is over. Check why.

Created: 2025-09-24 Last update: 2025-11-15 17:47

3 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 538837f52872eac70fd7b220d00750d8ca92f459
Author: Sean Whitton <spwhitton@spwhitton.name>
Date:   Tue May 20 11:03:03 2025 +0100

    Revert "Move broken tests out of CVE-2025-46421.patch"
    
    This reverts commit fdc596f7b3a04603f30b15eea08e628ea9060843.
    
    This commit was broken.

commit fdc596f7b3a04603f30b15eea08e628ea9060843
Author: Sean Whitton <spwhitton@spwhitton.name>
Date:   Tue May 20 11:01:30 2025 +0100

    Move broken tests out of CVE-2025-46421.patch

commit 3ce52af407456c2246e795cd3692a4531daf8ebc
Author: Sean Whitton <spwhitton@spwhitton.name>
Date:   Tue May 20 11:00:52 2025 +0100

    Add WIP manual test for CVE-2025-46421

Created: 2025-05-20 Last update: 2025-11-11 18:00

9 low-priority security issues in trixie low

There are 9 open security issues in trixie.

9 issues left for the package maintainer to handle:

CVE-2025-4035: (needs triaging) A flaw was found in libsoup. When handling cookies, libsoup clients mistakenly allow cookies to be set for public suffix domains if the domain contains at least two components and includes an uppercase character. This bypasses public suffix protections and could allow a malicious website to set cookies for domains it does not own, potentially leading to integrity issues such as session fixation.
CVE-2025-4476: (needs triaging) A denial-of-service vulnerability has been identified in the libsoup HTTP client library. This flaw can be triggered when a libsoup client receives a 401 (Unauthorized) HTTP response containing a specifically crafted domain parameter within the WWW-Authenticate header. Processing this malformed header can lead to a crash of the client application using libsoup. An attacker could exploit this by setting up a malicious HTTP server. If a user's application using the vulnerable libsoup library connects to this malicious server, it could result in a denial-of-service. Successful exploitation requires tricking a user's client application into connecting to the attacker's malicious server.
CVE-2025-4945: (needs triaging) A flaw was found in the cookie parsing logic of the libsoup HTTP library, used in GNOME applications and other software. The vulnerability arises when processing the expiration date of cookies, where a specially crafted value can trigger an integer overflow. This may result in undefined behavior, allowing an attacker to bypass cookie expiration logic, causing persistent or unintended cookie behavior. The issue stems from improper validation of large integer inputs during date arithmetic operations within the cookie parsing routines.
CVE-2025-4948: (needs triaging) A flaw was found in the soup_multipart_new_from_message() function of the libsoup HTTP library, which is commonly used by GNOME and other applications to handle web communications. The issue occurs when the library processes specially crafted multipart messages. Due to improper validation, an internal calculation can go wrong, leading to an integer underflow. This can cause the program to access invalid memory and crash. As a result, any application or server using libsoup could be forced to exit unexpectedly, creating a denial-of-service (DoS) risk.
CVE-2025-4969: (needs triaging) A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).
CVE-2025-9901: (needs triaging) A flaw was found in libsoup’s caching mechanism, SoupCache, where the HTTP Vary header is ignored when evaluating cached responses. This header ensures that responses vary appropriately based on request headers such as language or authentication. Without this check, cached content can be incorrectly reused across different requests, potentially exposing sensitive user information. While the issue is unlikely to affect everyday desktop use, it could result in confidentiality breaches in proxy or multi-user environments.
CVE-2025-32049: (needs triaging) A flaw was found in libsoup. The SoupWebsocketConnection may accept a large WebSocket message, which may cause libsoup to allocate memory and lead to a denial of service (DoS).
CVE-2025-32907: (needs triaging) A flaw was found in libsoup. The implementation of HTTP range requests is vulnerable to a resource consumption attack. This flaw allows a malicious client to request the same range many times in a single HTTP request, causing the server to use large amounts of memory. This does not allow for a full denial of service.
CVE-2025-46421: (needs triaging) A flaw was found in libsoup. When libsoup clients encounter an HTTP redirect, they mistakenly send the HTTP Authorization header to the new host that the redirection points to. This allows the new host to impersonate the user to the original host that issued the redirect.

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

Created: 2025-04-03 Last update: 2025-11-04 21:33

21 low-priority security issues in bookworm low

There are 21 open security issues in bookworm.

21 issues left for the package maintainer to handle:

CVE-2025-2784: (needs triaging) A flaw was found in libsoup. The package is vulnerable to a heap buffer over-read when sniffing content via the skip_insight_whitespace() function. Libsoup clients may read one byte out-of-bounds in response to a crafted HTTP response by an HTTP server.
CVE-2025-4035: (needs triaging) A flaw was found in libsoup. When handling cookies, libsoup clients mistakenly allow cookies to be set for public suffix domains if the domain contains at least two components and includes an uppercase character. This bypasses public suffix protections and could allow a malicious website to set cookies for domains it does not own, potentially leading to integrity issues such as session fixation.
CVE-2025-4476: (needs triaging) A denial-of-service vulnerability has been identified in the libsoup HTTP client library. This flaw can be triggered when a libsoup client receives a 401 (Unauthorized) HTTP response containing a specifically crafted domain parameter within the WWW-Authenticate header. Processing this malformed header can lead to a crash of the client application using libsoup. An attacker could exploit this by setting up a malicious HTTP server. If a user's application using the vulnerable libsoup library connects to this malicious server, it could result in a denial-of-service. Successful exploitation requires tricking a user's client application into connecting to the attacker's malicious server.
CVE-2025-4945: (needs triaging) A flaw was found in the cookie parsing logic of the libsoup HTTP library, used in GNOME applications and other software. The vulnerability arises when processing the expiration date of cookies, where a specially crafted value can trigger an integer overflow. This may result in undefined behavior, allowing an attacker to bypass cookie expiration logic, causing persistent or unintended cookie behavior. The issue stems from improper validation of large integer inputs during date arithmetic operations within the cookie parsing routines.
CVE-2025-4948: (needs triaging) A flaw was found in the soup_multipart_new_from_message() function of the libsoup HTTP library, which is commonly used by GNOME and other applications to handle web communications. The issue occurs when the library processes specially crafted multipart messages. Due to improper validation, an internal calculation can go wrong, leading to an integer underflow. This can cause the program to access invalid memory and crash. As a result, any application or server using libsoup could be forced to exit unexpectedly, creating a denial-of-service (DoS) risk.
CVE-2025-4969: (needs triaging) A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).
CVE-2025-9901: (needs triaging) A flaw was found in libsoup’s caching mechanism, SoupCache, where the HTTP Vary header is ignored when evaluating cached responses. This header ensures that responses vary appropriately based on request headers such as language or authentication. Without this check, cached content can be incorrectly reused across different requests, potentially exposing sensitive user information. While the issue is unlikely to affect everyday desktop use, it could result in confidentiality breaches in proxy or multi-user environments.
CVE-2025-32049: (needs triaging) A flaw was found in libsoup. The SoupWebsocketConnection may accept a large WebSocket message, which may cause libsoup to allocate memory and lead to a denial of service (DoS).
CVE-2025-32050: (needs triaging) A flaw was found in libsoup. The libsoup append_param_quoted() function may contain an overflow bug resulting in a buffer under-read.
CVE-2025-32052: (needs triaging) A flaw was found in libsoup. A vulnerability in the sniff_unknown() function may lead to heap buffer over-read.
CVE-2025-32053: (needs triaging) A flaw was found in libsoup. A vulnerability in sniff_feed_or_html() and skip_insignificant_space() functions may lead to a heap buffer over-read.
CVE-2025-32906: (needs triaging) A flaw was found in libsoup, where the soup_headers_parse_request() function may be vulnerable to an out-of-bound read. This flaw allows a malicious user to use a specially crafted HTTP request to crash the HTTP server.
CVE-2025-32907: (needs triaging) A flaw was found in libsoup. The implementation of HTTP range requests is vulnerable to a resource consumption attack. This flaw allows a malicious client to request the same range many times in a single HTTP request, causing the server to use large amounts of memory. This does not allow for a full denial of service.
CVE-2025-32909: (needs triaging) A flaw was found in libsoup. SoupContentSniffer may be vulnerable to a NULL pointer dereference in the sniff_mp4 function. The HTTP server may cause the libsoup client to crash.
CVE-2025-32910: (needs triaging) A flaw was found in libsoup, where soup_auth_digest_authenticate() is vulnerable to a NULL pointer dereference. This issue may cause the libsoup client to crash.
CVE-2025-32911: (needs triaging) A use-after-free type vulnerability was found in libsoup, in the soup_message_headers_get_content_disposition() function. This flaw allows a malicious HTTP client to cause memory corruption in the libsoup server.
CVE-2025-32912: (needs triaging) A flaw was found in libsoup, where SoupAuthDigest is vulnerable to a NULL pointer dereference. The HTTP server may cause the libsoup client to crash.
CVE-2025-32913: (needs triaging) A flaw was found in libsoup, where the soup_message_headers_get_content_disposition() function is vulnerable to a NULL pointer dereference. This flaw allows a malicious HTTP peer to crash a libsoup client or server that uses this function.
CVE-2025-32914: (needs triaging) A flaw was found in libsoup, where the soup_multipart_new_from_message() function is vulnerable to an out-of-bounds read. This flaw allows a malicious HTTP client to induce the libsoup server to read out of bounds.
CVE-2025-46420: (needs triaging) A flaw was found in libsoup. It is vulnerable to memory leaks in the soup_header_parse_quality_list() function when parsing a quality list that contains elements with all zeroes.
CVE-2025-46421: (needs triaging) A flaw was found in libsoup. When libsoup clients encounter an HTTP redirect, they mistakenly send the HTTP Authorization header to the new host that the redirection points to. This allows the new host to impersonate the user to the original host that issued the redirect.

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

Created: 2025-04-03 Last update: 2025-11-04 21:33

debian/patches: 27 patches to forward upstream low

Among the 30 debian patches available in version 2.74.3-10.1 of the package, we noticed the following issues:

27 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2025-05-03 23:33

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.2 instead of 4.7.0).

Created: 2025-02-21 Last update: 2025-05-03 17:33

testing migrations

excuses:
- Migration status for libsoup2.4 (- to 2.74.3-10.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Updating libsoup2.4 would introduce bugs in testing: #1056125, #1118886
- ∙ ∙ Autopkgtest for libsoup2.4/2.74.3-10.1: amd64: Pass, arm64: Failed ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsoup2.4.html
- ∙ ∙ Reproducible on amd64 - info ♻
- ∙ ∙ Reproducible on arm64 - info ♻
- ∙ ∙ 196 days old (needed 5 days)
- Not considered

news

[rss feed]

[2025-09-25] libsoup2.4 REMOVED from testing (Debian testing watch)
[2025-09-25] libsoup2.4 REMOVED from testing (Debian testing watch)
[2025-05-13] libsoup2.4 2.74.3-10.1 MIGRATED to testing (Debian testing watch)
[2025-05-03] Accepted libsoup2.4 2.74.3-10.1 (source) into unstable (Sean Whitton)
[2025-04-27] Accepted libsoup2.4 2.72.0-2+deb11u2 (source) into oldstable-security (Andreas Henriksson)
[2025-04-15] libsoup2.4 2.74.3-10 MIGRATED to testing (Debian testing watch)
[2025-04-12] Accepted libsoup2.4 2.74.3-10 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
[2025-03-22] libsoup2.4 2.74.3-9 MIGRATED to testing (Debian testing watch)
[2025-03-19] Accepted libsoup2.4 2.74.3-9 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
[2024-12-21] Accepted libsoup2.4 2.74.3-1+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Sean Whitton)
[2024-12-12] libsoup2.4 2.74.3-8.1 MIGRATED to testing (Debian testing watch)
[2024-12-12] Accepted libsoup2.4 2.72.0-2+deb10u1 (source) into oldstable-security (Sean Whitton)
[2024-12-12] Accepted libsoup2.4 2.72.0-2+deb11u1 (source) into oldstable-security (Sean Whitton)
[2024-12-10] Accepted libsoup2.4 2.74.3-8.1 (source) into unstable (Sean Whitton)
[2024-10-05] libsoup2.4 2.74.3-8 MIGRATED to testing (Debian testing watch)
[2024-10-03] Accepted libsoup2.4 2.74.3-8 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
[2024-04-30] libsoup2.4 2.74.3-7 MIGRATED to testing (Debian testing watch)
[2024-04-04] Accepted libsoup2.4 2.74.3-7 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
[2024-03-14] Accepted libsoup2.4 2.74.3-6 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
[2024-02-29] Accepted libsoup2.4 2.74.3-5 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
[2024-02-25] Accepted libsoup2.4 2.74.3-3.1~exp3 (source) into experimental (Steve Langasek)
[2024-02-24] Accepted libsoup2.4 2.74.3-3.1~exp2 (source) into experimental (Steve Langasek)
[2024-02-02] Accepted libsoup2.4 2.74.3-3.1~exp1 (source) into experimental (Steve Langasek)
[2024-02-01] libsoup2.4 2.74.3-3 MIGRATED to testing (Debian testing watch)
[2024-02-01] libsoup2.4 2.74.3-3 MIGRATED to testing (Debian testing watch)
[2024-01-29] Accepted libsoup2.4 2.74.3-3 (source) into unstable (Jeremy Bícha) (signed by: Jeremy Bicha)
[2023-11-20] libsoup2.4 2.74.3-2 MIGRATED to testing (Debian testing watch)
[2023-11-17] Accepted libsoup2.4 2.74.3-2 (source) into unstable (Simon McVittie)
[2022-10-14] libsoup2.4 2.74.3-1 MIGRATED to testing (Debian testing watch)
[2022-10-11] Accepted libsoup2.4 2.74.3-1 (source) into unstable (Jeremy Bicha)

bugs [bug history graph]

all: 21 22
RC: 2
I&N: 19 20
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian (1, 2)
buildd: logs, cross
popcon
browse source code
edit tags
other distros
security tracker
l10n (-, 98)
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.74.3-10.1ubuntu4
14 bugs
patches for 2.74.3-10.1ubuntu4