On 2024-04-29 03:05:50 +0200, Guillem Jover wrote:
> I don't think dpkg is at fault here, I assume something else is either
> getting activated in the middle of the transaction while the package
> manager frontend driving dpkg has released the lock (which it should
> not), or the package manager
Control: severity -1 normal
Hi!
On Mon, 2024-04-29 at 00:01:02 +0200, Chris Hofstaedtler wrote:
> Control: reassign -1 dpkg
>
> * Vincent Lefevre [240428 22:33]:
> > Package: fdisk
> > Version: 2.40-8
> > Severity: serious
> ...
> > Setting up util-linux (2.40-8) ...
> > fstrim.service is a
Here's the /var/log/apt/history.log part that corresponds to this
upgrade:
Start-Date: 2024-04-28 22:05:30
Upgrade: libsmartcols1:amd64 (2.40-6, 2.40-8), libvpx8:amd64 (1.13.1-2,
1.13.1-2+b1), libltdl7:amd64 (2.4.7-7, 2.4.7-7+b1), libpaper1:amd64 (1.1.29,
1.1.29+b1), libnftnl11:amd64 (1.2.6-2,
Control: reassign -1 dpkg
* Vincent Lefevre [240428 22:33]:
> Package: fdisk
> Version: 2.40-8
> Severity: serious
...
> Setting up util-linux (2.40-8) ...
> fstrim.service is a disabled or a static unit not running, not starting it.
> dpkg: error: dpkg frontend lock was locked by another
Package: fdisk
Version: 2.40-8
Severity: serious
During an upgrade with aptitude 0.8.13-6, I got:
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 417244 files and directories currently installed.)
Preparing to unpack .../bsdutils_1%3a2.40-8_amd64.deb
5 matches
Mail list logo
