Your message dated Tue, 27 Dec 2022 15:58:31 +0100
with message-id <[email protected]>
and subject line Re: Bug#1027068: cryptsetup: syntax error, unexpected ERROR,
expecting CCHAR or UNUMBER or AS
has caused the Debian Bug report #1027068,
regarding cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or
UNUMBER or AS
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 [email protected]
immediately.)
--
1027068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027068
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:2.6.0-2
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
After doing the following updates:
[UPGRADE] cryptsetup:amd64 2:2.6.0-1 -> 2:2.6.0-2
[UPGRADE] cryptsetup-bin:amd64 2:2.6.0-1 -> 2:2.6.0-2
[UPGRADE] cryptsetup-initramfs:amd64 2:2.6.0-1 -> 2:2.6.0-2
[UPGRADE] libcryptsetup12:amd64 2:2.6.0-1 -> 2:2.6.0-2
I see the following error when my system starts just after the GRUB splash
screen:
syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
Please note that it's hard to read this error and I only could take a video of
it so I'm not sure of the exact message. After downgrading the packages the
error message no longer appears.
-- Package-specific info:
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cryptsetup depends on:
ii cryptsetup-bin 2:2.6.0-1
ii debconf [debconf-2.0] 1.5.80
ii dmsetup 2:1.02.185-2
ii libc6 2.36-7
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
pn cryptsetup-initramfs <none>
ii dosfstools 4.2-1
pn keyutils <none>
ii liblocale-gettext-perl 1.07-5
-- debconf information:
cryptsetup/prerm_active_mappings: true
--- End Message ---
--- Begin Message ---
On Wed, 28 Dec 2022 at 01:49:18 +1100, Konomi wrote:
>> There is no occurrence of ‘CCHAR’ or ‘UNUMBER’ in the source, so I
>> suspect this might be orthogonal to src:cryptsetup.
>
> You're right I'm not sure what's going on. I allowed the packages to
> update again and now there's no error, it just seems to have gone away
> on its own. I really hate when that happens. I'll open another bug
> report with no specific package if I see the error again. Sorry for
> the false report.
No worries :-) Closing this one then.
--
Guilhem.
signature.asc
Description: PGP signature
--- End Message ---
