Package: duplicity
Version: 0.7.11-1
Severity: important
It is presently impossible to use Duplicity to back up to Backblaze B2
endpoints, at least where there already exists a bucket.
This is FIXED in the latest upstream, i.e. 0.7.17. Installing this (via
dpkg-buildpackage) worked just fine
Package: xen-utils-common
Version: 4.1.3-8
Severity: important
When antispoof is set to 'on', the vif-common script does not create an ALLOW
firewall rule for the emulated vif devices. This means that HVM nodes, unless a
Xen PV driver is installed and running, cannot access the external
Package: dtc-xen
Version: 0.5.14-1~bpo60+1
Severity: normal
When installing a new CentOS domU, DTC-Xen forces the 'extra' parameter in the
/etc/xen/xenXX file to be '4'. This is fine normally, but it appears as though
when using a = 3.0 kernel (possibly with Xen hypervisor 4.x) that the term
Package: dtc-xen
Version: 0.5.14-1~bpo60+1
Severity: normal
/usr/share/dtc-xen/dtc-xen-parse-param can be called with arguments like
--xenu_extra_parm 4 xterm=xvc0 which isn't quite valid. If we change a line
in the calc_forward_parms function in dtc_reinstall_os to read the following,
we will
--
Marc Warne
m...@indivisibilities.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
be accessible
by any user.
To correct this, I had to do the following:
cd /var/lib/python-support/python2.4/
chmod -R a+rx trac
Hope this helps,
Marc Warne
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: x86_64
Shell: /bin/sh linked
Package: nvidia-glx
Version: 1.0.8178-3
Severity: grave
Justification: renders package unusable
The latest nvidia-glx will not install because it depends on
nvidia-kernel-1.0.8756. This is not available, but nvidia-kernel-1.0.8756-4
does appear to be available. Presumably, because the version
7 matches
Mail list logo
