Your message dated Sun, 17 Sep 2023 20:19:01 +0200
with message-id <zqddffirlcxfa...@thunder.hadrons.org>
and subject line Re: Bug#951200: base-files: unable to upgrade, conffile error
has caused the Debian Bug report #951200,
regarding base-files: unable to upgrade, conffile error
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 ow...@bugs.debian.org
immediately.)
--
951200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base-files
Version: 9.9+deb9u11
Severity: important
Dear Maintainer,
after rebooting my system and trying to update my packages an error with the
base-files package occured which brought me into the situation that I am unable
to install any new packages.
There must be a problem with the conffile that is temporarily created when
installing base-files.
apt-clean, dpkg-reconfigure base-files didn't help. The checksum of the
packages are correct.
The error line states "new info file "/var/lib/dpkg/tmp.ci/conffiles" can't be
installed: incorrect message
There is no further error code or information.
Thanks for helping.
-- System Information:
Debian Release: 9.11
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.18-24-pve (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages base-files depends on:
ii mawk [awk] 1.3.3-17+b3
base-files recommends no packages.
base-files suggests no packages.
-- Configuration Files:
/etc/issue changed:
------------------------------------------------------------------------------
Welcome to the Proxmox Virtual Environment. Please use your web browser to
configure this server - connect to:
https://192.168.178.51:8006/
------------------------------------------------------------------------------
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
On Fri, 2023-07-14 at 00:30:26 +0200, Guillem Jover wrote:
> On Wed, 2020-02-12 at 11:31:35 +0000, Luca Koroll wrote:
> > Package: base-files
> > Version: 9.9+deb9u11
> > Severity: important
>
> > after rebooting my system and trying to update my packages an error with
> > the base-files package occured which brought me into the situation that
> > I am unable to install any new packages.
> > There must be a problem with the conffile that is temporarily created
> > when installing base-files.
>
> > The error line states
> > "new info file "/var/lib/dpkg/tmp.ci/conffiles" can't be installed:
> > incorrect message
>
> Hmm, weird I cannot see an error message in the dpkg history that
> matches this message. Can you paste the exact message, even if it is
> localized.
>
> The only error messages that are close to that one are either:
>
> "unable to install (supposed) new info file '%.250s'"
> "unable to install new info file '%.250s' as '%.250s'"
>
> both are related to a failed rename of the new info file, but that
> would not explain either the error message (from errno) which I cannot
> find either in glibc.
>
> > -- Configuration Files:
> > /etc/issue changed:
> > ------------------------------------------------------------------------------
> > Welcome to the Proxmox Virtual Environment. Please use your web browser to·
> > configure this server - connect to:
> > https://192.168.178.51:8006/
> > ------------------------------------------------------------------------------
>
> I assume this is from the system where the problem was found? Perhaps
> there's an issue with Proxmox?
>
> I've marked this moreinfo and unreproducible, because the error
> message does not make sense to me given the code history, so if I
> don't hear anything in a while, I guess I'll just have to close this
> as a non-actionable report.
I'm going to close this now, if there's new or updated information,
please feel free to reopen or file a new bug report.
Thanks,
Guillem
--- End Message ---
