The problem is due to the upgrade of python3 from 3.6 to 3.7 version.
In line 81 of /usr/share/pyzo/pyzo/yoton/clientserver.py, there is:
def __init__(self, address, async=False, verbose=0):
which is not possible anymore as async is now a reserved name.
A simple solution: change async to anot
Few more informations,
I also met this bug on another computer, where both separate / and /usr
partitions were on lvm. I didn't have problem beforehand, but the
upgrade of initramfs-tools indeed lead to the same problem.
Interestingly, it is clear during the boot time that the lvm root
partition i
Hello,
This bug is now also a problem with the new version of initramfs-tools
in the case of a separate /usr partition on a lvm, as /usr is also being
mounting early in the boot sequence by initramfs (this problem wasn't
hitting me beforehand as I did put a small root partition on a non-lvm
partit
Hello,
I confirm that this new version is also breaking the ipython qtconsole,
that cannot be lauched as it is leading to a similar error. Downgrading
back to the testing version 4.14.6-1 solves the problem.
Raphaël
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a sub
Package: ranger
Version: 1.4.3-1
Severity: grave
Justification: renders package unusable
Hello,
ranger cannot be launched since the default python switched from 2.6 to
2.7. After the python upgrade, calling ranger in commandline gives:
Traceback (most recent call last):
File "/usr/bin/ranger",
Hello,
I think that this bug should be moved from "Serious" to "Grave", as
actually its current state makes it uninstallable in most of the
situations. The package shouldn't have been moved to testing before
solving the bug.
This should be solved by making it compatible with the python-vtk
Package: glob2
Version: 0.8.23-1.1
Severity: grave
Subject: glob2: Uninstallable on i386
Package: glob2
Version: 0.8.23-1.1
Severity: grave
Justification: renders package unusable
glob2 as been recently updated to the version 0.9.2-1. However, if the
package glob2-data was correctly updated to
Shouldn't this be typically the case where alternatives can be used,
with the "/usr/lib/libboost_***.so" being links pointing on
"/etc/alternatives/libboost_***.so", these links pointing either on
"/usr/lib/libboost_***-mt.so" or "/usr/lib/libboost_***-st.so". This
should point on the -st files
Excuse me, I've just seen that I mistook the severity category. It
should be classed as "Important" rather than "Serious".
Raphaël Plasson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: acx100-source
Version: 20060521-3
Severity: serious
--- Please enter the report below this line. ---
I already have compiled with no problem the acx100 module to the kernel
2.6.18, with the module assistant. I actually checked again, it is still
working. This module do not want to com
Package: beagle
Version: 0.2.6-2
Severity: grave
Justification: renders package unusable
When switched to the 0.2.8 version of beagle, I couldn't used it
anymore. When launching the daemon by "beagled --bg" the process stops.
The logs says "Beagle ERROR EX: System.DllNotFoundException: libgobject
Package: grep
Version: 2.5.1.ds2-3
Severity: Critical
I was very recently unable to boot properly, after having upgrading my Debian Sid machine.
During the early stages of the boot process, errors were reported, saying that the file
"/usr/lib/libpcre.so.3" couldn't be find. It couldn't be obv
12 matches
Mail list logo
