[Bug 2076655] Re: [FFe] APT 3.0 solver updates

Julian Andres Klode 2076655 at bugs.launchpad.net
Mon Aug 12 15:37:30 UTC 2024


** Description changed:

- I'm asking for a blanket FFe for the experimental 3.0 solver that can be
- used with the --solver 3.0 argument. It's mostly really bug fixing
- that's happening, I'm not sure what would constitute a feature at this
- point*, but the changes are still fairly big as I'm refactoring it to
- align more with the MiniSAT paper; that fixes bugs along the process.
+ I'm asking for a blanket August FFe for the experimental 3.0 solver that
+ can be used with the --solver 3.0 argument. It's mostly really bug
+ fixing that's happening, I'm not sure what would constitute a feature at
+ this point*, but the changes are still fairly big as I'm refactoring it
+ to align more with the MiniSAT paper; that fixes bugs along the process.
+ 
+ The 1st big refactoring is almost ready; I'm missing refactoring the
+ install code (removal/do-not-install) has been refactored and then
+ refactoring from recursive propagation to a queue (which is easy the
+ annoying part is validating the change).
+ 
+ I don't think we'll get the 2nd big refactoring in this month.
  
  * If you consider we don't have conflict-driven clause learning which
  makes it slow, but is it a feature? Right now it doesn't terminate in my
  real life mantic -> noble upgrade test case, this seems an essential bug
- fix.
+ fix. Not that this is ready for 24.10 but as an example.
  
  This FFe is restricted to the solver3 code in apt-pkg/solver3.{cc,h} and
  does not cover modifications to other APT parts.
  
  In any case given this is an undocumented experimental option we don't
  have to be worried about regression potential.

** Summary changed:

- [FFe] APT 3.0 solver updates
+ [FFe] APT 3.0 solver updates in August

** Description changed:

  I'm asking for a blanket August FFe for the experimental 3.0 solver that
  can be used with the --solver 3.0 argument. It's mostly really bug
  fixing that's happening, I'm not sure what would constitute a feature at
  this point*, but the changes are still fairly big as I'm refactoring it
  to align more with the MiniSAT paper; that fixes bugs along the process.
  
  The 1st big refactoring is almost ready; I'm missing refactoring the
  install code (removal/do-not-install) has been refactored and then
  refactoring from recursive propagation to a queue (which is easy the
  annoying part is validating the change).
  
- I don't think we'll get the 2nd big refactoring in this month.
+ I don't think we'll get the 2nd big refactoring in this month. Starting
+ September we'll essentially only apply important bug fixes to APT.
  
  * If you consider we don't have conflict-driven clause learning which
  makes it slow, but is it a feature? Right now it doesn't terminate in my
  real life mantic -> noble upgrade test case, this seems an essential bug
  fix. Not that this is ready for 24.10 but as an example.
  
  This FFe is restricted to the solver3 code in apt-pkg/solver3.{cc,h} and
  does not cover modifications to other APT parts.
  
  In any case given this is an undocumented experimental option we don't
  have to be worried about regression potential.

** Description changed:

- I'm asking for a blanket August FFe for the experimental 3.0 solver that
- can be used with the --solver 3.0 argument. It's mostly really bug
- fixing that's happening, I'm not sure what would constitute a feature at
- this point*, but the changes are still fairly big as I'm refactoring it
- to align more with the MiniSAT paper; that fixes bugs along the process.
+ I'm asking for a blanket August FFe for 1-2 uploads in August for the
+ experimental 3.0 solver that can be used with the --solver 3.0 argument.
+ It's mostly really bug fixing that's happening, I'm not sure what would
+ constitute a feature at this point*, but the changes are still fairly
+ big as I'm refactoring it to align more with the MiniSAT paper; that
+ fixes bugs along the process.
  
  The 1st big refactoring is almost ready; I'm missing refactoring the
  install code (removal/do-not-install) has been refactored and then
  refactoring from recursive propagation to a queue (which is easy the
  annoying part is validating the change).
  
  I don't think we'll get the 2nd big refactoring in this month. Starting
  September we'll essentially only apply important bug fixes to APT.
  
  * If you consider we don't have conflict-driven clause learning which
  makes it slow, but is it a feature? Right now it doesn't terminate in my
  real life mantic -> noble upgrade test case, this seems an essential bug
  fix. Not that this is ready for 24.10 but as an example.
  
  This FFe is restricted to the solver3 code in apt-pkg/solver3.{cc,h} and
  does not cover modifications to other APT parts.
  
  In any case given this is an undocumented experimental option we don't
  have to be worried about regression potential.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2076655

Title:
  [FFe] APT 3.0 solver updates in August

Status in apt package in Ubuntu:
  New

Bug description:
  I'm asking for a blanket August FFe for 1-2 uploads in August for the
  experimental 3.0 solver that can be used with the --solver 3.0
  argument. It's mostly really bug fixing that's happening, I'm not sure
  what would constitute a feature at this point*, but the changes are
  still fairly big as I'm refactoring it to align more with the MiniSAT
  paper; that fixes bugs along the process.

  The 1st big refactoring is almost ready; I'm missing refactoring the
  install code (removal/do-not-install) has been refactored and then
  refactoring from recursive propagation to a queue (which is easy the
  annoying part is validating the change).

  I don't think we'll get the 2nd big refactoring in this month.
  Starting September we'll essentially only apply important bug fixes to
  APT.

  * If you consider we don't have conflict-driven clause learning which
  makes it slow, but is it a feature? Right now it doesn't terminate in
  my real life mantic -> noble upgrade test case, this seems an
  essential bug fix. Not that this is ready for 24.10 but as an example.

  This FFe is restricted to the solver3 code in apt-pkg/solver3.{cc,h}
  and does not cover modifications to other APT parts.

  In any case given this is an undocumented experimental option we don't
  have to be worried about regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2076655/+subscriptions




More information about the foundations-bugs mailing list