Bug#986814: Latest vagrant Buster libvirt image not found
Le 12/04/2021 à 13:14, Christopher Huhn a écrit : > Package: cloud.debian.org > Severity: serious > > The latest Buster libvirt image for vagrant gives me a 404, `vagrant box > update` fails. > > λ > curl > https://app.vagrantup.com/debian/boxes/buster64/versions/10.20210409.1/providers/libvirt.box Hi Thanks for your interest for the Debian Vagrant boxes. when I'm doing vagrant box update the box is downloaded from https://vagrantcloud.com/debian/boxes/buster64/versions/10.20210409./providers/libvirt.box and is properly found vagrant box update ==> default: Checking for updates to 'debian/buster64' default: Latest installed version: 10.4.0 default: Version constraints: default: Provider: libvirt ==> default: Updating 'debian/buster64' with provider 'libvirt' from version ==> default: '10.4.0' to '10.20210409.1'... ==> default: Loading metadata for box 'https://vagrantcloud.com/debian/buster64' ==> default: Adding box 'debian/buster64' (v10.20210409.1) for provider: libvirt default: Downloading: https://vagrantcloud.com/debian/boxes/buster64/versions/10.20210409.1/providers/libvirt.box Download redirected to host: vagrantcloud-files-production.s3-accelerate.amazonaws.com ==> default: Successfully added box 'debian/buster64' (v10.20210409.1) for 'libvirt'! when creating a fresh environment with export VAGRANT_DEFAULT_PROVIDER=libvirt vagrant init debian/buster64` vagrant up is the box properly downloaded on your side ? -- You know an upstream is nice when they even accept m68k patches. - John Paul Adrian Glaubitz, Debian OpenJDK maintainer
Bug#958430: closing 958430
close 958430 # error on user side, the libvirt box is fine. thanks
Bug#958430: Vagrant libvirt
> Call to virDomainCreateWithFlags failed: internal error: process > exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 > Device or resource busy > 2020-04-22T19:06:13.421798Z qemu-system-x86_64: failed to initialize > KVM: Device or resource busy > And this fatal error in vb-buster when lv-buster is already started: > The guest machine entered an invalid state while waiting for it to > boot. Valid states are 'starting, running'. The machine is in the > 'gurumeditation' state. Yes, unfortunately VirtualBox and Libvirt with Qemu/Kvm cannot run at the same time. See https://github.com/canonical/multipass/issues/6#issuecomment-359802193 for details.
Bug#958430: Vagrant libvirt
Thank you for your interest in the vagrant boxes. A fresh vagrant env with libvirt and 10.3 works for me (see: http://paste.debian.net/1142057/) Can you reproduce the problem in a fresh environment ? ie erase your current box and create a new vagrant env vagrant box remove debian/buster64 vagrant init debian/buster64 vagrant up --provider=libvirt and post here the commands output.
Bug#861282: (no subject)
rebuilt vagrant boxes have been uploaded to atlas with the fix discussed here
Bug#861282: (no subject)
I can confirm the behaviour is mentioning. @JD: does the commits from pull requests 4900 and 4910 apply cleanly on 0.10.2 ? can you build a working packer passing the build tests with the patches applied ?
Bug#806273: use grub-mount as the sole source of partition probes (disable kernel readonly mounts)
changes since v1:
* do not fallback on dangerous read only kernel mounts if grub-mount is
missing, just exit with error
>From 34a2c247fa08d4e01aa08b5b75977c66d71df4f8 Mon Sep 17 00:00:00 2001
From: Emmanuel Kasper <emman...@libera.cc>
Date: Tue, 15 Nov 2016 14:52:23 +0100
Subject: [PATCH v2] use grub-mount as the sole source of partition probes
(disable kernel readonly mounts)
the read only kernel mounts of os-probes caused various data corruption in virtual machines
and exported block devices due to the following chain of event:
1. os-prober tries to mount via grub-mount each block device as seen from /sys/block
2. in case of iscsi exported block devices or virtualization environment, such
a block device could be a whole disk image with a partition table
3. since grub-mount expects a filesystem superblock but encounters a partition table
it fails and then give hand to
4. kernel read only mounts, calling the function ro_partition
5. the ro_partition function sets the block device readonly via blockdev --setro
6. a number of kernel mounts are attempted via various kernel modules
7. the block device is set to readwrite
now when I/O happened on the iscsi initiator or virtual machines between 5-7
the blocks cannot be flushed to the block device since it has been
locked by os-prober. This causes a filesystem error and the filesystem to be
remounted read only.
since grub-mount is now available on all the platforms debian supports
we assume we can disable the risky behaviour without losing too much os-prober functionnality
grub-mount has also now support for all filesystems which the kernel knows,
the exception being QNX
---
debian/control | 2 +-
os-probes/common/50mounted-tests | 27 +++
2 files changed, 12 insertions(+), 17 deletions(-)
diff --git a/debian/control b/debian/control
index 10459bd..ac307f5 100644
--- a/debian/control
+++ b/debian/control
@@ -22,7 +22,7 @@ Package: os-prober
Architecture: any
Section: utils
Priority: extra
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, grub-common
Description: utility to detect other OSes on a set of drives
This package detects other OSes available on a system and outputs the
results in a generic machine-readable format.
diff --git a/os-probes/common/50mounted-tests b/os-probes/common/50mounted-tests
index 561163b..8e1c87f 100755
--- a/os-probes/common/50mounted-tests
+++ b/os-probes/common/50mounted-tests
@@ -47,25 +47,20 @@ fi
mounted=
if type grub-mount >/dev/null 2>&1 && \
- type grub-probe >/dev/null 2>&1 && \
- grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
- mounted=1
- type="$(grub-probe -d "$partition" -t fs)" || true
- if [ "$type" ]; then
- debug "mounted using GRUB $type filesystem driver"
- else
- debug "mounted using GRUB, but unknown filesystem?"
+ type grub-probe >/dev/null 2>&1; then
+ if grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
+ mounted=1
+ type="$(grub-probe -d "$partition" -t fs)" || true
+ if [ "$type" ]; then
+ debug "mounted using GRUB $type filesystem driver"
+ else
+ debug "mounted using GRUB, but unknown filesystem?"
type=fuseblk
+ fi
fi
else
- ro_partition "$partition"
- for type in $types $delaytypes; do
- if mount -o ro -t "$type" "$partition" "$tmpmnt" 2>/dev/null; then
- debug "mounted as $type filesystem"
- mounted=1
- break
- fi
- done
+ echo "Cannot find grub-mount (Try installing grub-common)" >&2
+ exit 1
fi
if [ "$mounted" ]; then
--
2.1.4
Bug#806273: Patch for disabling kernel mounts when grub-mount is available
The included patch disables read_only mounts when grub-mount is available.
This patch should also fix #788062 and #648208, which I presume are the
same bug.
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701814#57
it seems that the fallback for kernel mounts were mostly added as a
"conservative fallback".
Actually this conservative fallback can lead to data corruption as shown
in #788062 and #648208 and when a failed grub-mount will be succeeded
by the attempt of a readonly
I am looking forward for comments about the patch since the bug is
release critical and goes back as far as 2011.
>From 58c2cbf7660e93f52e43bdf076a5db9bc95d9889 Mon Sep 17 00:00:00 2001
From: Emmanuel Kasper <e.kas...@proxmox.com>
Date: Tue, 15 Nov 2016 14:52:23 +0100
Subject: [PATCH] do not mount partitions via 'mount' if grub-mount fails on a
block device closes: #806273, #788602
kernel read-only 'mount' via ro_partition causes data loss if the block device
is actually mounted outside our environement (for example via iscsi, or
a virtual machine)
since grub-mount has now support for all the filesystems needed in os-probes/mounted,
(with the execption of QNX) it is assumed to be safe to disable kernel read-only
mounts except for the case where grub-mount is not available
---
debian/control | 2 +-
os-probes/common/50mounted-tests | 17 +
2 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/debian/control b/debian/control
index 10459bd..00c4a63 100644
--- a/debian/control
+++ b/debian/control
@@ -22,7 +22,7 @@ Package: os-prober
Architecture: any
Section: utils
Priority: extra
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, grub-common [i386 amd64 powerpc ppc64 ppc64el sparc mipsel kfreebsd-i386 kfreebsd-amd64]
Description: utility to detect other OSes on a set of drives
This package detects other OSes available on a system and outputs the
results in a generic machine-readable format.
diff --git a/os-probes/common/50mounted-tests b/os-probes/common/50mounted-tests
index 561163b..f1e35c1 100755
--- a/os-probes/common/50mounted-tests
+++ b/os-probes/common/50mounted-tests
@@ -47,15 +47,16 @@ fi
mounted=
if type grub-mount >/dev/null 2>&1 && \
- type grub-probe >/dev/null 2>&1 && \
- grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
- mounted=1
- type="$(grub-probe -d "$partition" -t fs)" || true
- if [ "$type" ]; then
- debug "mounted using GRUB $type filesystem driver"
- else
- debug "mounted using GRUB, but unknown filesystem?"
+ type grub-probe >/dev/null 2>&1; then
+ if grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
+ mounted=1
+ type="$(grub-probe -d "$partition" -t fs)" || true
+ if [ "$type" ]; then
+ debug "mounted using GRUB $type filesystem driver"
+ else
+ debug "mounted using GRUB, but unknown filesystem?"
type=fuseblk
+ fi
fi
else
ro_partition "$partition"
--
2.1.4
Bug#713211: (no subject)
I have uploaded in mentors http://mentors.debian.net/package/sysbench and I am looking for a sponsor ! if someone stumbles over here ... diff -u sysbench-0.4.12/debian/rules sysbench-0.4.12/debian/rules --- sysbench-0.4.12/debian/rules +++ sysbench-0.4.12/debian/rules @@ -6,8 +6,8 @@ # Add here any variable or target overrides you need. DEB_CONFIGURE_SCRIPT_ENV += LDFLAGS= -Wl,-as-needed -DEB_AUTO_UPDATE_AUTOMAKE = 1.11 -DEB_AUTO_UPDATE_ACLOCAL = 1.11 +DEB_AUTO_UPDATE_AUTOMAKE = 1.14 +DEB_AUTO_UPDATE_ACLOCAL = 1.14 DEB_AUTO_UPDATE_LIBTOOL = pre DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl diff -u sysbench-0.4.12/debian/changelog sysbench-0.4.12/debian/changelog --- sysbench-0.4.12/debian/changelog +++ sysbench-0.4.12/debian/changelog @@ -1,3 +1,10 @@ +sysbench (0.4.12-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Bump DEB_AUTO_UPDATE_AUTOMAKE to 1.14 (closes: #713211) + + -- Emmanuel Kasper emman...@libera.cc Tue, 11 Feb 2014 10:57:46 +0100 + sysbench (0.4.12-1) unstable; urgency=low * New upstream version
Bug#713211: (no subject)
I have prepared a package to do a nmu to fix this bug. Should I go ahead ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713211: (no subject)
The above patch works, though you need to also add dh-autoreconf as a dependency @hendrik: would you consider applying it ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695818: (no subject)
I tried to reproduce this bug and the possible fix. After inserting a valid installation CD (tried with a Windows NT and a Debian Wheezy CD), Gnome Boxes does not indeed propose to use this install media in his Source Selection Screen Installing the libosinfo-bin pacakge does not help, altough libosinfo itselfs correctly detects the CD to be an install media. /usr/bin/osinfo-detect /dev/sr0 Media is bootable. cat /etc/apt/sources.list deb http://debian.inode.at/debian wheezy main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free deb-src http://debian.inode.at/debian wheezy main contrib non-free -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695818: (no subject)
I downgrade the severity of this bug report to serious as the problem reported here is serious: important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. Gnome Boxes can be used to do three things: * connect to a remove VM via the spice or qemu+ssh protocol * install a VM from a local file * install a VM from a local installation media As *one* of this function is currently broken, I don't think we can say it makes the package unfit for release. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689718: xmame-sdl,xmess-sdl: missing copyright file after upgrade from squeeze
... and *mame-tools is built from src:mess which doesn't help to reduce confusion yes mame and mess have a difficult track love/fork history. According to the last news the two upstreams merged their source code repo, but still want to provide differen binaries. Andreas PS: looking forward to see all the transitional packges being dropped for wheezy+1 :-) I agree ! :-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689718: xmame-sdl,xmess-sdl: missing copyright file after upgrade from squeeze
Le 11/10/2012 11:15, Andreas Beckmann a écrit :
mame (0.146-4) unstable; urgency=low
* Removes danglink symlink after xmame-sdl,xmame-x,xmame-svga
update.
That is too late, as the files will be installed over the broken
symlink. The symlinks must be deleted in preinst and unpackaging the
updated package will create a directory in place of the (now missing)
hello andreas
actually the link removal *does* appear in preinst though I agree that
my changelog entry could have been more clear
the bug should be fixed for xmame-{sdl,x,svga} but it is still open for
xmess-{sdl,x,svga}
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687654: (no subject)
I took a look at commit 6d0c77edac6cf78e2fbe6e71e64836a51fb40623 and I don't think it is relevant here, as it deals with ubuntu version upgrades between packages which were never in debian I am thinking to fix this bug by adding a pre.inst to xmame-x and xmame-sdl/0.146-2. which would remove the symbolic link on upgrade -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685470: (no subject)
it seems the problem stems from the use of symbolic links in xmess-sdl, xmess-x, xmame-x. xmame-sdl in debian 6 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685653#25 details the same problem in another debian package on a debian 6 dpkg -L xmess-x | xargs file | grep symbolic link /usr/share/doc/xmess-x: symbolic link to `xmess-common' /usr/share/man/man6/xmess.x11.6.gz: symbolic link to `xmess.6.gz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678249: (no subject)
Dear debian user We will believe the bug you reported is fixed in mame 0.146-2, availaible in wheezy and sid. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685470: (no subject)
Since xmess-x and xmess-sdl are transitional packages, they depend on mess which has the right copyright file anyway. Is that enough to satisfy the copyright file claim ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678249: (no subject)
Sorry Mame still segfaults with mame -O3 and the latest gcc available in debian ( I guess my build env was broken ) The package mame/0.146-2 will fix this bug tough (by recompiling with -O2 on all arches) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661697: FTBFS on arm* and kfreebsd*: libnss-ldap missing files (debian/tmp/usr/lib/*/*), aborting
Am 2012-08-08 02:32, schrieb peter green: Emmanuel Kasper: can you tell us if the patch in http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=14;bug=683011 fixes libnss-ldap on kfreebsd for you? sorry I don't have any kFreeBSD system anymore to test (I found it not production ready, especially lack of documentation) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678249: (no subject)
I have recompiled mame with the current wheezy gcc (Debian 4.7.1-6), and I cannot make mame segfault anymore on i386. I have seen there has been a slew of bug fixes in the debian gcc changelog but nothing that I can really pin point to this bug. As the best way to see if a bug still exist, is to reproduce it ;) could you maybe recompile the mame binary on your system with -O3, the current wheezy compiler mentionned aboce and see if it still segfaults ? mame -verbose Parsing mame.ini Parsing mame.ini Build version: 0.146 (Aug 6 2012) Build architecure: SDLMAME_ARCH=-march=pentium2 Build defines 1:SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1 Build defines 1:LSB_FIRST=1 DISTRO=generic SYNC_IMPLEMENTATION=tc SDL/OpenGL defines: SDL_COMPILEDVERSION=1215 USE_OPENGL=1 USE_DISPATCH_GL=1 Compiler defines A: __GNUC__=4 __GNUC_MINOR__=7 __GNUC_PATCHLEVEL__=1 __VERSION__=4.7.1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678249: (no subject)
So i have reproduced the bug, and you're right, using -O2 or compiling with gcc 4.6 resolves the problem. As official gcc 4.7 support is only coming in mame 0.146 update 2, I am thinking of using the second option to resolve the bug on the package. @Berto: Upstream is however interested in sorting out this bug, so could you maybe submit your backtrace as asked in http://forums.bannister.org/ubbthreads.php?ubb=showflatNumber=80250 ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678249: your mail
thanks for the time you took to investigate this problem ! a quick question, which architecture are you using on the problematic machine ? Can you post the output of dpkg-architecture ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678249: (no subject)
I have here a debian wheezy system in VirtualBox , and I can't reproduce this bug. Could try maybe without a mame.ini file ? Are all your libraries up to date ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661697: libnss-ldap does not work on kFreeBSD
Package: libnss-ldap Version: 264-2.2 Severity: grave Justification: renders package unusable Libnss-ldap does not work on a kfreebsd-amd64 system. Using the same setup on a bunch of Debian Linux hosts works. The user writing at http://www.docunext.com/wiki/Debian_LDAP_Authentication also met this this problem ldapsearch definitively works. When starting slapd in debug mod ( -d 768 ) I don't see any connection attempt coming from the kFreeBSD system. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 8.1-1-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnss-ldap depends on: ii debconf [debconf-2. 1.5.36.1 Debian configuration management sy ii libc0.1 2.11.3-3 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libgssapi-krb5-21.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - k ii libkrb5-3 1.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-7.2 OpenLDAP libraries ii libsasl2-2 2.1.23.dfsg1-7 Cyrus SASL - authentication abstra Versions of packages libnss-ldap recommends: ii libpam-ldap 184-8.5Pluggable Authentication Module fo ii nscd 2.11.3-3 Embedded GNU C Library: Name Servi libnss-ldap suggests no packages. -- debconf information: * libnss-ldap/dblogin: false libnss-ldap/override: true * shared/ldapns/base-dn: dc=openforce,dc=com * libnss-ldap/rootbinddn: cn=manager,dc=example,dc=net * shared/ldapns/ldap_version: 3 libnss-ldap/binddn: cn=proxyuser,dc=example,dc=net * shared/ldapns/ldap-server: ldap://10.200.1.60 * libnss-ldap/nsswitch: * libnss-ldap/confperm: false * libnss-ldap/dbrootlogin: false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661702: amanda-client: please relax Build-Depends to allow building on kFreeBSD
Package: amanda-client Version: 1:3.3.0-1~bpo60+1 Severity: serious Justification: fails to build from source amanda-client has two Build-Depends on dump (ext3/3/4 dump), and xfsdumps which obviously only exists on Linux Systems. This prevents the autobuilding of the package: https://buildd.debian.org/status/fetch.php?pkg=amandaarch=kfreebsd-amd64ver=1%3A2.6.1p1-2stamp=1263357711 However by moving out these two depencies, it is possible to build a working package and binary which works using tar as the compress method. I have build such a (backport) package and it works perfectly. Maybe it is possible to relax the build deps for kFreeBSD ? -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 8.1-1-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages amanda-client depends on: ii amanda-common1:3.3.0-1~bpo60+1 Advanced Maryland Automatic Networ ii libc0.1 2.11.3-3Embedded GNU C Library: Shared lib ii libcurl3 7.21.0-2.1+squeeze1 Multi-protocol file transfer libra ii libglib2.0-0 2.24.2-1The GLib library of C routines ii libreadline6 6.1-3 GNU readline and history libraries ii libssl0.9.8 0.9.8o-4squeeze7SSL shared libraries amanda-client recommends no packages. Versions of packages amanda-client suggests: pn dump none (no description available) ii gnuplot 4.4.0-1.1 A command-line driven interactive ii smbclient 2:3.5.6~dfsg-3squeeze6 command-line SMB/CIFS clients for -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612648: kamefu: Kamefu fails to see any Mame Roms
Package: kamefu Version: 0.1.1-4+b1 Severity: grave Justification: renders package unusable After setting the path to a mame rom collection, kamefu is unable to see any roms, und so unable to start them. This happens both with xmame-x v 0.106 and with the mame package 0.140 from the new queue (http://ftp-master.debian.org/new/mame_0.141-1.html ) Besides this upstream seems to have disappeared ( http://kamefu.pwsp.net. empty since some time now ) I think it would be a good idea to remove this package from the archive. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kamefu depends on: ii kamefu-data0.1.1-4 Data files for Kamefu ii kdelibs4c2a4:3.5.10.dfsg.1-5 core libraries and binaries for al ii libacl12.2.49-4 Access control list shared library ii libart-2.0-2 2.3.21-1 Library of functions for 2D graphi ii libattr1 1:2.4.44-2Extended attribute shared library ii libaudio2 1.9.2-4 Network Audio System - shared libr ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libfam02.7.0-17 Client library to control the FAM ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1 FreeType 2 font engine, shared lib ii libgcc11:4.4.5-8 GCC support library ii libice62:1.0.6-2 X11 Inter-Client Exchange library ii libidn11 1.15-2GNU Libidn library, implementation ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG ii libkamefu0 0.1.1-4+b1Libraries for Kamefu ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libpng12-0 1.2.44-1 PNG library - runtime ii libqt3-mt 3:3.3.8b-7+b1 Qt GUI Library (Threaded runtime v ii libsm6 2:1.1.1-1 X11 Session Management library ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-4 X11 client-side library ii libxcursor11:1.1.10-2X cursor management library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxft22.1.14-2 FreeType-based font drawing librar ii libxi6 2:1.3-6 X11 Input extension library ii libxinerama1 2:1.1-3 X11 Xinerama extension library ii libxrandr2 2:1.3.0-3 X11 RandR extension library ii libxrender11:0.9.6-1 X Rendering Extension client libra ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime kamefu recommends no packages. kamefu suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496125: libxml2 problem confirmed on different platform: etch ppc
Package: libxml2 Followup-For: Bug #496125 Hello Sorry for the me-too of this report, but I can confirm this bug on debian etch running on a single processor ppc (G4) 32 bits platform. It happens I also use the Gorilla theme, and the symptoms were exactly those reported in message 39 of this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496125#39 I downgraded to lixml2 from 2.6.27.dfsg-3 to 2.6.27.dfsg-2 and the problem does not appear. For people reading ths bug report: the procedure to downgrade a security fix is documented here ( that's what I used ) http://wiki.debian.org/RollbackUpdate -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages libxml2 depends on: ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages libxml2 recommends: ii xml-core 0.09-0.1 XML infrastructure and XML catalog -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
