Note: the patch will not change the flow if not exception happens in mark_install(cache, pkg)
Given so, I think there won't have regression if we apply this. ** Description changed: This happen in oem project because we have lots pkg to upgrade during installation because the design of factory process need it. As package list have certain dependency, and the the order that we get the pkg from the python set object is not good for underlying apt engine, then exception will raise. - A workaround fix is move those failed to next iteration and the fix test - pass as we try it in installation for like 50 times. + A workaround fix is move those failed debs to next iteration and the fix + test pass as we try it in installation for like 50 times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891599 Title: installation stopped by an random exception from mark_install() in Cache class of python3-apt To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
