[Aptitude-devel] Bug#964916: Option to allow packages from backports but without forcing it

Pirate Praveen praveen at onenetbeyond.org
Tue Jul 14 16:59:42 BST 2020

On Tue, Jul 14, 2020 at 17:23, Pirate Praveen 
<praveen at onenetbeyond.org> wrote:
> On Tue, Jul 14, 2020 at 13:57, Pirate Praveen 
> <praveen at onenetbeyond.org> wrote:
>> I think rebuilding ruby-json with ruby 2.7 might fix it.
> But now we need to update our build scripts to build with ruby 2.7.
> https://git.fosscommunity.in/praveen/debian-scripts/-/blob/master/sbuild-fto 
> was how we used to build earlier. With apt priority 500, it used to 
> pick up ruby 2.7, but now with a lower apt priority it picks up ruby 
> 2.5 from buster. I need to figure out the best way to force ruby 2.7. 
> I think forcing it via gem2deb may be the best option.

I think the root cause for aptitude failing to resolve the situation 
automatically is because ruby-json is now provided by libruby2.7. I 
think that is a bug in aptitude (and possibly apt too).

aptitude now succeeds in second try for fresh installations and 
succeeds after 4 tries when upgrading


More information about the Aptitude-devel mailing list