Your message dated Mon, 9 Dec 2024 23:40:09 +0200
with message-id <Z1djuX6UvIbqPLgs@localhost>
and subject line Re: Bug#1089583: python-jinja2: Post Installation Script Fails
After Upgrade to 2.11.3-1+deb11u1 Due to Syntax Error
has caused the Debian Bug report #1089583,
regarding python-jinja2: Post Installation Script Fails After Upgrade to
2.11.3-1+deb11u1 Due to Syntax 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 [email protected]
immediately.)
--
1089583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089583
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-jinja2
Version: 2.11.3-1+deb11u1
Severity: normal
Dear Maintainer,
today, one of our servers received an update for python-jinja2 that
appears to
be a Debian LTS security update:
dpkg.log:
2024-12-09 08:36:55 upgrade python-jinja2:all 2.11.3-1 2.11.3-1+deb11u1
Our monitoring suggests that the update failed to install successfully:
www0.iserv.eu ~ # LC_ALL=C dpkg --configure python-jinja2
Setting up python-jinja2 (2.11.3-1+deb11u1) ...
+ which pycompile
+ pycompile -p python-jinja2
File "/usr/lib/python2.7/dist-packages/jinja2/filters.py", line 251
raise ValueError(f"Invalid character in attribute name: {key!r}")
^
SyntaxError: invalid syntax
dpkg: error processing package python-jinja2 (--configure):
installed python-jinja2 package post-installation script subprocess
returned error exit status 101
Errors were encountered while processing:
python-jinja2
For your convenience, I have enabled +x in the post installation script.
I am by no means a Python expert, the nature of the error suggests to me
that
the cause is a syntax error in the update itself, not local
configuration etc.
The file in question has not been modified locally. I was able to reproduce
the issue on a 2nd machine.
I'd like to take the opportunity again to say thanks for your ongoing
support.
Kind regards,
Kim-Alexander Brodowski
IServ GmbH
-- System Information:
Debian Release: 11.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'),
(500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-33-amd64 (SMP w/1 CPU thread)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-jinja2 depends on:
ii python-markupsafe 1.1.1-1+b3
ii python2 2.7.18-3
Versions of packages python-jinja2 recommends:
ii python-pkg-resources 44.1.1-1
Versions of packages python-jinja2 suggests:
pn python-jinja2-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.11.3-1+deb11u2
On Mon, Dec 09, 2024 at 08:46:20AM -0300, Santiago Ruano Rincón wrote:
>...
> El 09/12/24 a las 11:04, Kim-Alexander Brodowski escribió:
> > Package: python-jinja2
> > Version: 2.11.3-1+deb11u1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > today, one of our servers received an update for python-jinja2 that appears
> > to
> > be a Debian LTS security update:
Thanks for the bug report, and apologies for the breakage.
Python 2 is not supported for running applications in bullseye,
and while testing the update I missed that jinja2 still builds
a package for Python 2 in addition to the package for Python 3.
Since it is bad to break things even when they are unsupported,
I have released a regression update fixing this:
https://lists.debian.org/debian-lts-announce/2024/12/msg00012.html
cu
Adrian
--- End Message ---
