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.b
close 958430
# error on user side, the libvirt box is fine.
thanks
> 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-buste
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
vagra
rebuilt vagrant boxes have been uploaded to atlas with the fix discussed
here
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 ?
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
Date: Tue, 15 Nov 2016 14:52:23 +0100
Subject: [PATCH v2] use grub-mount as
goes back as far as 2011.
>From 58c2cbf7660e93f52e43bdf076a5db9bc95d9889 Mon Sep 17 00:00:00 2001
From: Emmanuel Kasper
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
kerne
+ * Bump DEB_AUTO_UPDATE_AUTOMAKE to 1.14 (closes: #713211)
+
+ -- Emmanuel Kasper Tue, 11 Feb 2014 10:57:46 +0100
+
sysbench (0.4.12-1) unstable; urgency=low
* New upstream version
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
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
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
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
> ... 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: looki
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 unp
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 s
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/shar
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 listma
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
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 "un
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, espec
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
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 sort
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". Troub
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...@
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.debi
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 t
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 (ht
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 r
29 matches
Mail list logo
