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 945ead2ab03b7c83b3fbaecf3e1e543525e476f0
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Thu Jan 30 15:34:51 2025 +0100
solver3: Credit MiniSAT
Gbp-Dch: ignore
commit 6425f211c0c85863232afb2d8e7eff95d150bddd
Merge: 184ac78d afc0a378
Author: Julian Andres Klode <jak@debian.org>
Date: Thu Jan 30 14:12:56 2025 +0000
Merge branch 'solver3' into 'main'
solver3: Unit propagation queues
See merge request apt-team/apt!440
commit afc0a37872b24a6e4cc31d0a7b04a16d7b8f149a
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Thu Jan 30 14:48:34 2025 +0100
solver3: Remove fixed test cases from broken list
commit 3523efb15d48ce3c6f9212f50dfc892497ba9dcb
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Sat Nov 2 13:55:39 2024 +0100
solver3: Use a propagation queue
Instead of directly propagating in a recursive fashion,
queue propagations in a queue and work on them in a loop
per the miniSAT paper.
We call Propagate() only at the end of the FromDepCache()
function and then in the Solve loop. Delaying the initial
propagation means that we get a stronger reasoning:
Assume you have x->a->b->c, y->c and you install x,y:
- Previously we traversed: x, y, x->a, a->b, b->c, (y->c)
- but now we traverse: x, y, x->a, y->c, a->b, (b->c)
Notably c now has the implication y->c instead of x->a->b->c.
Inside the solver we need to call Propagate in a loop:
Propagating facts can fail and we then backtrack. If backtracking
is succesful, we have gained a new fact to propagate.
commit ccdbea353a30de597a00a88cf4c7216370a21882
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Sat Nov 2 13:54:04 2024 +0100
solver3: Replace Install() with Enqueue(), and PropagateInstall()
Do not enqueue common dependencies if a version is selected already,
this avoids test suites changing now in behavior as the ordering is
different.
commit 45432cc57144715109f27d0bb83356b12e2a4ef5
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Thu Jan 30 13:46:09 2025 +0100
solver3: Remove NewUnsatRecommends group
This is more or less unused; but it particularly has the bad
problem of forcing new unsat recommends to be solved *before*
dependencies. Which is awkward.
commit a20242cf3a7321e78cfd4afd892d67255d8282ba
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Thu Jan 30 13:04:47 2025 +0100
solver3: Soft unit propagation for optional items
If both items are optional, unit items should be processed
first.
commit 184ac78d3dd21b9d6c3b539703de803f0f7132a7
Author: Rafael Fontenelle <rafaelff@gnome.org>
Date: Thu Jan 30 12:13:07 2025 +0000
Brazilian Portuguese program translation update
Closes: #1092563
commit b0e3c7eb2a0b65912e4b5cf83ed63544a79679c3
Merge: 7cd26558 e68daac8
Author: Julian Andres Klode <jak@debian.org>
Date: Tue Jan 28 21:52:21 2025 +0000
Merge branch 'mr-update-zh_cn-translation-apt2.9.24' into 'main'
po/zh_CN.po: Refresh Simplified Chinese translation for apt
See merge request apt-team/apt!432
commit e68daac8052fc3c2cf9dc311cf6ac1e5b4ff7cf6
Author: Boyuan Yang <byang@debian.org>
Date: Tue Jan 28 16:26:43 2025 -0500
po/zh_CN.po: Refresh Simplified Chinese translation for apt
commit 7cd265586eb255781d0a009c4ebe9918a2f36022
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Tue Jan 28 20:44:35 2025 +0100
Symbols: Update for 2.9.23/2.9.25
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/apt.png){kind=link}