[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1058749: marked as done (scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf')



Your message dated Mon, 7 Oct 2024 21:34:49 +0200
with message-id <ZwQ32SLZMv2G-veI@per.namespace.at>
and subject line Re: #1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'
has caused the Debian Bug report #1058749,
regarding scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1058749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058749
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: scanbd
Version: 1.5.1-7
Severity: serious
User: debian-qa@lists.debian.org
Usertags: piuparts
X-Debbugs-Cc: Chris Hofstaedtler <zeha@debian.org>

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'bookworm'.
It installed fine in 'bookworm', then the upgrade to 'sid' fails.

This test intentionally skipped 'testing' to find problems before packages
migrate from 'unstable' to 'testing'.

>From the attached log (scroll to the bottom...):

  Setting up scanbd (1.5.1-7) ...
  mv: not replacing '/etc/scanbd/dll.conf'
  dpkg: error processing package scanbd (--configure):
   installed scanbd package post-installation script subprocess returned error exit status 1


cheers,

Andreas

Attachment: scanbd_1.5.1-7.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Looks like this was fixed in coreutils in the meantime.

Chris

--- End Message ---

Reply to: