it could be a problem of mutual interaction created by a package that removes the directory while the other tries to write a file on the same path. If so, it would be a case not managed during the update process...
Il giorno ven 1 nov 2019 alle ore 07:12 Stefan Hornburg (Racke) <ra...@linuxia.de> ha scritto: > > On 10/31/19 8:54 AM, Antonio wrote: > > Package: pure-ftpd > > Version: 1.0.49-1 > > Severity: important > > > > Dear Maintainer, > > there is an error on pure-ftpd-common package when I try to upgrade pure-ftp > > > > Preparativi per estrarre .../pure-ftpd-common_1.0.49-1_all.deb... > > Estrazione di pure-ftpd-common (1.0.49-1) su (1.0.47-3)... > > dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/pure-ftpd- > > common_1.0.49-1_all.deb (--unpack): > > impossibile aprire "/usr/share/doc/pure-ftpd-common/README.Authentication- > > Modules.gz.dpkg-new": File o directory non esistente > > Si sono verificati degli errori nell'elaborazione: > > /var/cache/apt/archives/pure-ftpd-common_1.0.49-1_all.deb > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > > Thanks, > > Antonio > > > > Hello Antonio, > > I can reproduce the problem but can't explain why it happens. > Thanks for the report. > > Regards > Racke > > > -- > Ecommerce and Linux consulting + Perl and web application programming. > Debian and Sympa administration. Provisioning with Ansible. >
