Control: reassign -1 libcrypt1 Control: forcemerge -1 953562 On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote: > On 2020-11-13 18:23 +0100, Niels Thykier wrote: > > > Control: reassign -1 perl-base > > Control: affects -1 upgrade-reports > > Control: severity -1 grave > > > > Hi Perl team, > > > > I have reassigned this bug to perl because perl-base being essential > > must remain functional during an upgrade and AFAICT perl-base fails in > > this case here. > > > > If it is a direct linkage, then you might be needing a Pre-Depends. If > > it is an indirect linkage then I am not sure how to fix it. :-/ > > I don't think perl-base is doing anything wrong here, it already uses > Pre-Depends. AFAICS the problem is that libcrypt.so.1 can temporarily > go missing if libc6 2.31-4 is unpacked before libcrypt1, breaking the > assumption that binaries from essential packages are always usable. > > I don't have a good idea how to fix that, though. :-(
Right - perl-base 5.32.0-5 has the following: Pre-Depends: libc6 (>= 2.29), libcrypt1 (>= 1:4.1.0) I don't think we can do anything about this on the perl side, so reassigning to libcrypt. This seems to be same as #953562 which was reported in March.