Bug#1038111: haproxy-log-analysis: current version not usable, new upstream release available
Package: haproxy-log-analysis
Version: 2.0~b0-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
directly after installation of haproxy-log-analysis the postinst script throws
errors:
Selecting previously unselected package python3-haproxy-log-analysis.
Preparing to unpack .../python3-haproxy-log-analysis_2.0~b0-4_all.deb ...
Unpacking python3-haproxy-log-analysis (2.0~b0-4) ...
Selecting previously unselected package haproxy-log-analysis.
Preparing to unpack .../haproxy-log-analysis_2.0~b0-4_all.deb ...
Unpacking haproxy-log-analysis (2.0~b0-4) ...
Setting up python3-pkg-resources (66.1.1-1) ...
Setting up python3-haproxy-log-analysis (2.0~b0-4) ...
/usr/lib/python3/dist-packages/haproxy/filters.py:122: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if start_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:125: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:128: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if start_value is not '' and delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:128: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if start_value is not '' and delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:132: SyntaxWarning: "is" with
a literal. Did you mean "=
="?
if start_value is '':
Setting up haproxy-log-analysis (2.0~b0-4) ...
Also executing haproxy-log-analysis throws an error which makes it basically
unusable:
Traceback (most recent call last):
File "/usr/bin/haproxy_log_analysis", line 33, in
sys.exit(load_entry_point('haproxy-log-analysis==2.0b0', 'console_scripts',
'haproxy_log_analysis')())
File "/usr/lib/python3/dist-packages/haproxy/main.py", line 289, in
console_script
main(arguments)
File "/usr/lib/python3/dist-packages/haproxy/main.py", line 274, in main
for command in args['commands']:
TypeError: 'NoneType' object is not iterable
The currently in Debian available version of haproxy-log-analysis is 7 years
old. There have been several releases by upstream since then. The latest was
version 5.1.0 released on December 3rd, 2022.
Please update haproxy-log-analysis so that we have a working version in Debian
again.
Thank you and kind regards,
Daniel
-- System Information:
Versions of packages haproxy-log-analysis depends on:
ii python3 3.9.2-3
pn python3-haproxy-log-analysis
haproxy-log-analysis recommends no packages.
Bug#877962: prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua
Hi, > From the attached log (scroll to the bottom...): > > Preparing to unpack .../prosody_0.10~hg745e0a783055-3_amd64.deb ... > invoke-rc.d: could not determine current runlevel > invoke-rc.d: policy-rc.d denied execution of stop. > Unpacking prosody (0.10~hg745e0a783055-3) over (0.9.12-2) ... > dpkg: error processing archive > /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb ( > --unpack): > trying to overwrite > '/usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua', which is > also in package prosody-modules 0.0~hg20170929.c53cc1ae4788+dfsg-1 > dpkg-deb: error: subprocess paste was killed by signal (Broken > pipe) > invoke-rc.d: could not determine current runlevel > invoke-rc.d: policy-rc.d denied execution of start. > Errors were encountered while processing: > /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb > with the latest version in sid (0.10.0-1) this shouldn't be the case anymore. This bug actually blocks the transition to testing. Kind regards, Dan smime.p7s Description: S/MIME cryptographic signature
Bug#1035516: php-smbclient broke with samba 4.17.5
Dear maintainers, On Thu, 04 May 2023 16:23:10 +0200 Alan Krempler wrote: > Package: php-smbclient > Version: 1.0.6-8 > Severity: grave > Justification: renders package unusable > > php-smbclient does not work with samba versions 4.17.5 and above: > https://github.com/eduardok/libsmbclient-php/issues/98 > https://github.com/nextcloud/server/issues/367please upload 73 > > php-smbclient upstream version 1.1.1 fixes the issue. php-smbclient 1.1.1 has been released almost over a year ago. Could you update the package to this version in order to fix this issue and reintroduce php-smbclient into testing again? Thank you and kind regards, Dan smime.p7s Description: S/MIME cryptographic signature
Bug#505270: confirm
Am Freitag, den 02.01.2009, 15:10 +1300 schrieb Jochen: > I can confirm this bug on 2 of my systems. However for me > the /etc/directfbrc does not fix the error. > > Cheers > Jochen > > > > I can confirm this bug as well, even with 0.3.13-1 the error persists. The /etc/directfbrc hack doesn't work for me, too. Some random information: I purged and reinstalled: desktop-base, all 3 splashy packages, libdirectfb, all of them with the latest versions. My /tmp is on a tmpfs. Splashy works _every time_ at shutting down and hibernation/resume. All the best, Dan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#505270: Clarification needed.
Am Sonntag, den 04.01.2009, 17:46 + schrieb Neil Williams: > Package: splashy > tag 505270 + unreproducible > tag 505270 + moreinfo > thanks > > This bug appears to only affect non-standard kernels not using > initramfs *and* using /usr on a different partition. > wrong. My configuration: kernel: self-compiled initramfs: yes /usr on different partition: no Please keep in mind: Reproducing this bug within a virtual environment seems not to be possible. All the best, Dan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
