27.07.2011 05:38, Otavio Salvador wrote:
On Wed, Jun 22, 2011 at 15:04, m...@tls.msk.ru mailto:m...@tls.msk.ru
wrote:
...
Maybe it's a good idea to include it into squeeze-p-u, and it's
definitely nice fix to have for sid. I'll apply the patch to
git later today.
Can
notfound 678408 4.1.4+debian-3
found 678408 5.0.6-2
tags 678408 + moreinfo
thanks
24.06.2012 3:35, Marc Lehmann wrote:
On Fri, Jun 22, 2012 at 09:05:17PM +0300, Michael Tokarevm...@tls.msk.ru
wrote:
21.06.2012 17:24, Marc Lehmann wrote:
Package: autofs
Version: 4.1.4+debian-3
Really?
25.06.2012 15:47, Dmitrijs Ledkovs пишет:
# Copy udev rules, which udev no longer does
- mkdir -p $DESTDIR/lib/udev/rules.d/
- cp/lib/udev/rules.d/64-md-raid.rules $DESTDIR/lib/udev/rules.d/
+ UDEV_RULE=64-md-raid.rules
+ for rules_folder in /lib/udev/rules.d /etc/udev/rules.d; do
+
25.06.2012 16:00, Dmitrijs Ledkovs пишет:
On 25/06/12 13:55, Michael Tokarev wrote:
[]
It is enough to copy first of /etc/udev, /lib/udev file, to ONE
place (either to /lib/udev or /etc/udev). No need to copy both,
and generally, no need to use two (/etc/udev and /lib/udev) dirs
in initramfs
25.06.2012 15:44, Dmitrijs Ledkovs пишет:
Package: mdadm
Version: 3.2.5-1
Severity: wishlist
Please consider applying the following patch.
Instead of using hand-crafted snippet to prevent restarting mdadm, use
debhelper's snippet.
This appears to be a reasonable cleanup, but do we actually
28.06.2012 16:43, Liang Guo wrote:
On Wed, Jun 27, 2012 at 04:46:41PM +0930, Ron wrote:
So far as I can see, you Michael and I all agree that the experimental
package is the only viable candidate for Wheezy. But you will lose that
option if you do not upload it very, very soon. The freeze
Package: librbd1
Version: 0.47.2-1
Severity: normal
Current librbd1/librbd-dev in unstable does not include symvers/libvers
mechanism but includes changes in symbols so that current version in
testing (0.43-1) does not work for binaries built against current version
in wheezy (0.47.2-1). When
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
Severity: normal
kvm userspace process segfaults (null pointer dereference)
when used with
-M pc-1.0 -device virtio-net-pci,vhost=on
right when linux guest loads virtio-net module.
--
To UNSUBSCRIBE, email to
28.06.2012 14:07, Ian Campbell wrote:
On Wed, 2012-06-27 at 12:10 +0100, Ian Campbell wrote:
SeaBIOS using a config derived from xen/tools/firmware/seabios-config
(which is the 1.6.x based config we use) works for me while a config
from make defconfig does not. I will investigate further.
02.07.2012 14:01, Nico Prenzel wrote:
Package: qemu-kvm
Hello qemu-kvm maintainer,
on Linux 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux
with qemu-kvm package 1.1~z0+dfsg-1 I do receive the following error:
kvm --version
kvm: symbol lookup error: kvm: undefined
tags 679904 + unreproducible
forcemerge 679904 679899
thanks
02.07.2012 15:27, Nico Prenzel wrote:
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
Justification: renders package unusable
Severity: grave
Dear Maintainer,
with qemu-kvm package I do receive the following error with amd64 kernel:
02.07.2012 15:59, Michael Tokarev wrote:
kvm: symbol lookup error: kvm: undefined symbol:
usbredirfilter_string_to_rules
I can't reproduce this on my amd64 sid host. The library in question -
ii libusbredirparser0 0.4.3-2
is the same on my machine and on the buildd box which built
On 03.07.2012 11:58, Josef Spillner wrote:
[]
Currently, the qemu-kvm package has many tight dependencies which are useful
on desktop systems (SDL, pulseaudio, SPICE etc.) but less useful on headless
or
embedded virtualisation setups. Approximately 67 MB of space are claimed by
the
package
03.07.2012 13:51, Marc Haber wrote:
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
Severity: important
Hi,
after upgrading qemu-kvm from 1.0+dfsg-11 to 1.1~z0+dfsg-1, my Linux
guests go back into Shutoff mode early after invoking init. This
both applies to Debian unstable and to grml.
Can
03.07.2012 17:37, Marc Haber wrote:
In virt-manager, I click on Run. boot manager is is visible, Linux
kernel boots, I remember that one sees the starting init message,
and the machine is shut down again. Click on Run again, repeat.
So, it doesn't actually run, it stops right away, right?
If
03.07.2012 17:49, Marc Haber wrote:
On Tue, Jul 03, 2012 at 05:43:02PM +0400, Michael Tokarev wrote:
03.07.2012 17:37, Marc Haber wrote:
In virt-manager, I click on Run. boot manager is is visible, Linux
kernel boots, I remember that one sees the starting init message,
and the machine is shut
Replying to an old bugreport. Old details can be found
at http://bugs.debian.org/653396 .
Kein, did you try anything since January about this issue?
Do you still have the issue?
Especially, does current wheezy kernel (3.2) and qemu-kvm
(1.1) shows it too?
Thank you!
/mjt
--
To
(Replying to somewhat old bugreport)
12.05.2012 04:04, David Fries wrote:
On Fri, May 11, 2012 at 10:59:38AM +0400, Michael Tokarev wrote:
On 05.05.2012 19:07, David Fries wrote:
Package: qemu-kvm
Version: 1.0+dfsg-12
Severity: normal
Tags: patch
Dear Maintainer,
qemu-kvm stops parsing
15.06.2012 18:58, Gary Dale wrote:
[]
OK, so the Windows install is still hanging. This time it stopped when
looking for devices. That's a little further than it got when I used
virt-manager to install over the existing image.
Since this is a brand new image file, it suggests that there is
severity 674919 normal
tags 674919 - moreinfo unreproducible
tags 674919 + confirmed
summary 674919 -1
thanks
the cause is old glibc used on the user system, while qemu-kvm were compiled
with a more recent version, so the real problem is lack of correct versioned
dependencies for libglib2.0
[Replying to an old bugreport]
01.05.2012 14:50, Vugar Dzhamalov wrote:
Another quick update here. It could be related somehow...
Just got a kernel failure popup, here is the message:
Kernel failure message 1:
[ cut here ]
WARNING: at
Christoph, please excuse me for the long delay with
this bugreport. I was busy, and later went to 2-week vacation,
and now I'm busy again, you see... ;)
On 06.05.2012 18:15, Christoph Biedl wrote:
Package: qemu-kvm
Version: 1.0+dfsg-11
Severity: important
Dear Maintainer,
after about
tags 679377 + moreinfo
thanks
On 28.06.2012 13:14, Jordi Pujol wrote:
Package: busybox
Version: 1:1.20.0-4
Severity: important
the patch shell-ash-export-HOME.patch causes a segmentation fault when
initramfs boots,
I believe that this fault occurs the first time that initramfs looks for
a misfeature in util-linux
implementation).
So marking this bug as wontfix, and appropriately
lowering severity.
Thanks,
/mjt
On 08.06.2012 21:36, Michael Tokarev wrote:
On 08.06.2012 15:22, maximilian attems wrote:
On Fri, Jun 08, 2012 at 03:10:42PM +0400, Michael Tokarev wrote:
On 08.06.2012 14:52
reassign 680307 librbd1 0.47.2-1
thanks
On 05.07.2012 01:14, Vincent Danjean wrote:
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
Severity: serious
Justification: dependencies must allow the program to work
Hi,
qemu-kvm (=1.1~z0+dfsg-1) depends on librbd1 without any specific version.
Package: busybox
Version: 1:1.20.0-4
Severity: important
xargs does not implement options and features mandated by POSIX:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/xargs.html
Notable, it does not process quotes and backslash on input, does
not implement -p (prompt) and -x
On 05.07.2012 04:32, Stefan Lippers-Hollmann wrote:
[]
I'm having trouble with the same problem in a custom (not Debian live)
live boot environment, where busybox awk segfaults with
shell-ash-export-HOME.patch applied. The code in question is[1]:
FINGERED=$(awk -F: '
[]
Executing the very
On 05.07.2012 21:36, Gary Dale wrote:
I'm getting an error when I try to create a new virtual machine using the
command string you suggested earlier (
kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
-cpu qemu64).
kvm: symbol lookup error: kvm: undefined
tags 680460 + moreinfo
thanks
On 06.07.2012 05:46, Hor Jiun Shyong wrote:
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
Package: libvirt-bin
Version: 0.9.12-3
Linux version 3.4.4 (root@szechuan) (gcc version 4.7.1 (Debian 4.7.1-2) ) #1
SMP Thu Jul 5 11:04:55 MYT 2012
CPU: AMD A6-3670 APU
merge 679788 680460
thanks
On 06.07.2012 11:23, Haruo Kinoshita wrote:
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
Followup-For: Bug #680460
Hello,
I have same problem.
qemu-kvm dies at guest kernel loading.
uname information of host
# uname -a
Linux mia 3.4.4-rt13 #1 SMP
On 06.07.2012 01:46, Gary Dale wrote:
That's got some things working. The virtual machine I had previously started
installing XP64 on has completed the install (after picking up where it
previously hung) and is now installing SP2.
However, another new VM I tried creating (with XP64) using
forwarded 665821 http://thread.gmane.org/gmane.comp.emulators.kvm.devel/88820
reopen 665821
thanks
On 04.07.2012 14:54, Michal Suchanek wrote:
[]
Hello,
Upstream says it's working for them with kvm git but requires both
recent kernel and recent kvm userspace I guess.
Oh okay I found it
On 20.06.2012 14:15, Philipp Kern wrote:
On Tue, Jan 09, 2007 at 11:03:56PM +0100, Geert Stappers wrote:
# Op 09-01-2007 om 19:09 schreef Frans Pop:
# close 406114
# thanks
#
# Bug#406114: Installer netinst needs ping and better ifconfig
# Bug reopened, originator not changed.
#
On 16.06.2012 12:00, Hiroshi Miura wrote:
Package: vgabios
Version: 0.7a-3
There is a patch that intend to support
VESA DDC EDID feature and to s upport recent popular
high resolutions on Guest OS with -vga std on KVM/QEMU.
You can select resolutions on guest os in qemu/kvm with -vga std
On 06.07.2012 13:25, Hor Jiun Shyong wrote:
Where's the kvm command line??
#virsh start diaoyudao
Hint: I asked for KVM command line, not for VIRSH command line.
Where's the output from qemu-kvm bug script?
I have installed qemu-kvm-dgb package and set the logging option as below.
On 06.07.2012 18:01, Laurent Bigonville wrote:
severity 679788 serious
severity 680508 serious
merge 680508 679788
thanks
Hi,
I'm setting the severity of these bugs to serious (not critical as it's
not completely broken). I really have the feeling that this cannot
migrate to testing
On 06.07.2012 20:25, Micah Anderson wrote:
Package: qemu-kvm
Version: 1.0+dfsg-8
Severity: important
Hi,
While using 1.0+dfsg-8+bpo60+1 I attempted to hotplug a CPU, it failed with
the
kvm process crashing and destroying the guest.
CPU hotplug in qemu-kvm has been broken for a long
On 07.07.2012 07:09, INFONIC Haruo Kinoshita wrote:
Following is workaround for loading guest by libvirtd.
Hope this helps.
- remove machine attribute from type element.
# editor /etc/libvirtd/qemu/guest-machine.xml
domain type='kvm'
snip
os
!-- type
On 07.07.2012 00:13, Vugar Dzhamalov wrote:
Thank you for coming back to me! I am absolutely committed! If you won't give
up on me than I am ready to do my best to help with it. Lets push it to the
very (happy) end :-)
Heh. Well, I ignored your bugreport for quite a while, and now,
tags 680609 + confirmed pending
thanks
On 07.07.2012 13:36, Jamie Heilman wrote:
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
KVM doens't look for cpus-x86_64.conf where Debian puts it:
$ strace -e trace=file kvm -cpu ? 21 |grep -F .conf
open(/usr/share/kvm/cpus-x86_64.conf, O_RDONLY) = -1
On 07.07.2012 16:25, Gary Dale wrote:
[]
I copied you in on it because this seems to a new behaviour in the krfb
and/or kvm software.
It is not. For qemu/kvm case, you have to tell it explicitly where
(on which port) to listen. This has always been the case. So you
either told qemu-kvm
On 07.07.2012 17:53, Gary Dale wrote:
On 07/07/12 09:04 AM, Michael Tokarev wrote:
On 07.07.2012 16:25, Gary Dale wrote:
[]
I copied you in on it because this seems to a new behaviour in the krfb
and/or kvm software.
It is not. For qemu/kvm case, you have to tell it explicitly where
retitle 679377 busybox awk segfaults when called from ash and no PATH set (eg
initramfs /init)
tags 679377 + pending
thanks
On 05.07.2012 15:12, Jordi Pujol wrote:
[]
the patch shell-ash-export-HOME.patch causes a segmentation fault when
initramfs boots,
I believe that this fault occurs the
is within the patch comments. (Closes: #679377)
+
+ -- Michael Tokarev m...@tls.msk.ru Sun, 08 Jul 2012 01:37:18 +0400
+
busybox (1:1.20.0-4) unstable; urgency=low
* ps-get-uptime.patch: make procps/ps.c compilable on non-linux again
diff -Nru busybox-1.20.0/debian/config/pkg/deb
busybox
of crashing.
+(Closes: #680551)
+
+ -- Michael Tokarev m...@tls.msk.ru Tue, 03 Jul 2012 18:01:33 +0400
+
qemu-kvm (1.1~z0+dfsg-1) unstable; urgency=low
* merge a few more stable-1.1 upstream commits
@@ -7,7 +26,7 @@
qemu-kvm (1.1~rc+dfsg-1) experimental; urgency=low
- * new upstream
tags 680719 + moreinfo unreproducible
thanks
On 08.07.2012 11:57, Jamie Heilman wrote:
Package: qemu-kvm
Version: 1.1~z0+dfsg-1
1.1.0+dfsg-1 is still affected; but the problem hit unstable with
1.1~z0+dfsg-1. This is essentially upstream bug 1021649. Which has
evidently been closed as
tags 680719 - unreproducible
tags 680719 + confirmed
thanks
On 08.07.2012 12:26, Michael Tokarev wrote:
On 08.07.2012 11:57, Jamie Heilman wrote:
The problem I'm facing is that my VMs that used -nodefaults -nographic
-device isa-serial,chardev=char0 -chardev pty,id=char0 (or -display
none
On 08.07.2012 13:32, Jamie Heilman wrote:
[]
You need to provide ways to reproduce this.
I've been trying to figure that out, I didn't give an explicit detail
becuase I haven't been able to isolate the minimal case yet, and I was
watching 1021649 thinking upstream was on top of it already...
On 08.07.2012 17:08, Cyril Brulebois wrote:
Michael Tokarev m...@tls.msk.ru (08/07/2012):
#680342 - http://bugs.debian.org/679377
xargs applet does not implement basic POSIX-specified features
Question: is it expected it's not available in the initramfs?
it is not available there now
On 08.07.2012 20:41, Cyril Brulebois wrote:
Michael Tokarev m...@tls.msk.ru (08/07/2012):
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package qemu-kvm. Please note that the package has
already been uploaded
On 08.07.2012 23:10, Cyril Brulebois wrote:
Michael Tokarev m...@tls.msk.ru (08/07/2012):
That version grew a bug which people were hitting often -- #679788,
thats the only reason I hurried up with the new version. People
started upping severity exactly to STOP it from entering testing.
So
On 08.07.2012 23:37, Michael Tokarev wrote:
On 08.07.2012 23:10, Cyril Brulebois wrote:
[]
Maybe we could make something happen anyway, e.g. by letting it stay for
a longer period in unstable before considering an unblock. But I'll let
some other team members voice their opinion on this topic
Um. This is just insane. The bug is filed 22-Dec 2011,
today is 09-Jul 2012, you have the actual cause, and it
is still open, and the maintainers of suspected package
(busybox) knows nothing about it... :(
Okay.
Rui, you found the root cause of this issue, it is there:
Package: extlinux
Version: 2:4.05+dfsg-5
Severity: normal
There are at least two issues in extlinux here.
extlinux --once does not print newline after the error message.
For example (running on a read-only /boot):
# extlinux --once 3.2.0-amd64 /boot
/boot is device /dev/sda2
Bad file
severity 632401 important
merge 639830 632401
summary 639830
thanks
When creating initramfs, alternative MD device names (/dev/md/X) apparently are
not handled correctly by mdadm initramfs hook
I'm mergeing the two bugs which are about the same thing.
Yes, it looks like something ins't exactly
tags 639830 + moreinfo unreproducible
thanks
On 26.05.2012 13:03, Michael Tokarev wrote:
When creating initramfs, alternative MD device names (/dev/md/X) apparently
are not handled correctly by mdadm initramfs hook
Ok. After quite some digging I was able to - sort of, anyway -
reproduce
retitle 660932 Double quote in (some) wget's international output for
downloaded filename
thanks
The same happens in Russian locale too:
Сохранение в каталог: ««debian-testing-amd64-netinst.iso»».
Saving to catalog: ««debian-testing-amd64-netinst.iso»».
In en_US locale, this is done by
On 26.05.2012 13:47, H.A.J. Koster wrote:
Ran into the same problem with the debian-testing-amd64-netinst.iso.
Specifically, the installer screen goes red when trying to install the
busybox package, the log shows indeed that it cannot find the source image,
while it is still mounted. I
On 26.05.2012 15:59, Michael Tokarev wrote:
Err cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot amd64
NETINST Binary-1 20120526-09:20]/ wheezy/main busybox amd64 1:1.19.3-7
Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update
cannot be used to add new
[Back to the original bugreport, after removing all private data]
On 26.05.2012 16:06, Cristian Ionescu-Idbohrn wrote:
On Sat, 26 May 2012, Michael Tokarev wrote:
On 26.05.2012 15:37, Cristian Ionescu-Idbohrn wrote:
On Sat, 26 May 2012, Michael Tokarev wrote:
Do you still remember how did you
On 26.05.2012 18:11, Michael Tokarev wrote:
[]
when generating the image. The only possible case I can think
of is when you listed
INITRDSTART=/dev/md0
(the same as for root filesystem in fstab), but using /dev/md/0
in mdadm.conf -- in this case, mkinitramfs reports:
W: mdadm: I am
Neil, can you comment on the change to Monitor offered
in the mentioned bugreport please?
On 12.04.2012 23:28, Michael Tokarev wrote:
Neil, re http://bugs.debian.org/658701 , how do you think,
is it okay if mdadm --monitor will send email in case check
found mismatches, the same way it sends
On 26.05.2012 19:03, Cristian Ionescu-Idbohrn wrote:
[]
Note also that you still have the same inconsistency -- you list
/dev/md/0 in mdadm.conf, but use /dev/md0 as root filesystem. I
can't say it works by design, more by a chance, it is better to
use consistent naming there.
Alright. You
Source: roxterm
Version: 2.6.3-1
Severity: normal
This is another variant of #639687.
When current directory of the shell running inside a roxterm window gets
removed, there's no way to start a new window/tab: roxterm complains that
it can't chdir to a deleted directory because that directory
tags 674919 + moreinfo unreproducible
thanks
On 28.05.2012 20:00, Wakko Warner wrote:
Package: qemu-kvm
Version: 1.0+dfsg-11
Severity: important
I'm using libvirt 0.9.9-3+b2 to start VMs with kvm. I just upgraded qemu-kvm.
I am no longer able to start VMs where I have defined a file
On 29.05.2012 07:56, Wakko Warner wrote:
[]
(process:14897): GLib-CRITICAL **: g_thread_pool_new: assertion
`g_thread_supported ()' failed
worker thread initialization failed
[]
You know what, forget all of the above. My libglib version is 2.28.6-1. I
extracted the library from
On 01.06.2012 16:23, Michael Tokarev wrote:
On 01.06.2012 16:15, Dmitry Smirnov wrote:
Hi Michael and William
Dmitrijs called off his NMU and expressed his interest to join our team
while I updated repository with more changes.
I'm doing some last-minute changes too, which we discussed
On 01.06.2012 18:42, Dmitry Smirnov wrote:
Hi Michael,
Dmitry, your two changes, both marked as fixing #674391,
are wrong and needs revered.
First, a small thing, the kmod change,
c6ac061e12208cdf32291223b27caeefec6ce241.
Here's the changelog difference from it:
[Dmitry Smirnov]
-
Lucas, can you please verify the new release
actually fixes the bug you reported? We made
some changes in attempt to fix this issue, but
Dmitry says it still fails to build, and I can't
reproduce it locally.
Thank you!
/mjt
--
To UNSUBSCRIBE, email to
Package: ftp.debian.org
Following the autofs package rename (from autofs5 to autofs),
the old package names become dummy/transitional, hence oldlibs/extra.
New packages are autofs, autofs-hesiod and autofs-ldap.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to
On 18.12.2011 22:28, Michael Tokarev wrote:
On 18.12.2011 22:23, Michael Tokarev wrote:
On 18.12.2011 22:16, Petter Reinholdtsen wrote:
Package: busybox-udeb
Version: 1:1.17.1-8
The Debian/Squeeze installer fail with /32 netmasks provided from DHCP.
From URL: https://bugs.busybox.net
On 02.06.2012 23:59, Conrad Wood wrote:
[]
In some cloud environments, including ours, we configure an ethernet device
with a single /32 IP Address. Say, for example 5.6.7.8/32. The Default
Gateway is, for example, 9.10.11.12. The linux kernel and BSD happily work as
desired and send out an
On 03.06.2012 13:43, Thijs Kinkhorst wrote:
Hi all,
Reading the bug about CVE-2011-2716, I think the only question left is this:
So, in all cases the variable is enclosed in double quotes.
Yes this look secure. What about the udeb script?
On 03.06.2012 12:21, Andreas B. Mundt wrote:
Hi,
first, thank you all for the work on a refurbished autofs package! I
would like to draw your attention to #639529, as it would be great to
fix this before the wheezy freeze and it's just a minor modification.
Let me sum up, as the lengthy
On 03.06.2012 15:15, Andreas B. Mundt wrote:
[]
automount: files ldap
Will it be bad if this line will be left out after removing autofs-ldap
package, ie, when automount nsswitch entry is listing non-existing lookup
method? I guess I should try...
Apart from leaving cruft back, I
On 03.06.2012 16:31, Jamie Heilman wrote:
Package: autofs
Version: 5.0.6-2
Severity: important
For reasons I haven't entirely taken the time to figure out, the
changes between 5.0.6-1 and 5.0.6-2 have destroyed my ability to
automount NFSv4 shares. My configs are dead simple, my entire
tags 675796 + pending
thanks
On 03.06.2012 16:36, Jamie Heilman wrote:
Package: autofs
Version: 5.0.6-2
The autofs package's postrm script it calls ucfr -p autofs5 $CONFF
for CONFF in /etc/auto.master /etc/auto.net /etc/auto.misc
/etc/auto.smb /etc/default/autofs; which no longer works as
On 03.06.2012 16:55, Andreas B. Mundt wrote:
On Sun, Jun 03, 2012 at 04:06:37PM +0400, Michael Tokarev wrote:
I guess autofs doesn't use nsswitch.conf at all, does it?
Apparently it does -- this is the very end of default /etc/auto.master
file:
# Include central master map if it can be found
On 03.06.2012 15:29, Thijs Kinkhorst wrote:
[]
Good! Will you ensure that 1.20 ends up in wheezy?
Yes I very much like to have at least this version
in wheezy.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On 03.06.2012 17:35, Michael Tokarev wrote:
tags 675796 + pending
thanks
On 03.06.2012 16:36, Jamie Heilman wrote:
Package: autofs
Version: 5.0.6-2
The autofs package's postrm script it calls ucfr -p autofs5 $CONFF
for CONFF in /etc/auto.master /etc/auto.net /etc/auto.misc
/etc/auto.smb
retitle 675798 autofs requires portmapper on server even for NFSv4 mounts
tags 675798 confirmed upstream
thanks
On 03.06.2012 17:31, Michael Tokarev wrote:
[]
Does it work if you enable portmapper/rpcbind on the server?
(It is enabled here)
I just verified - and indeed, with no rpcbind running
On 03.06.2012 18:39, Michael Tokarev wrote:
On 03.06.2012 17:31, Michael Tokarev wrote:
[]
Does it work if you enable portmapper/rpcbind on the server?
(It is enabled here)
I just verified - and indeed, with no rpcbind running on the
server, automount does not work anymore, ie, it requires
On 03.06.2012 23:38, Jamie Heilman wrote:
[]
For now I suggest to actually run rpcbind on the server, this
issue needs to be dealt with upstream. Neither version of the
code is right.
Hell no. The entire reason I bothered with v4 is because it gets rid
of the external portmapper
On 03.06.2012 23:15, Jamie Heilman wrote:
Michael Tokarev wrote:
[]
I dunno, and I don't really know what advantages the in-autofs NFS
handling gives, over nfs-utils utilities.
Then why did you enable it?
Because it is how the code is supposed to work initially.
The previous (working
04.06.2012 05:34, Dmitry Smirnov wrote:
Michael, please excuse me for adding my portion of rant.
Generally speaking assumptions and changes to package' logic outside
of packaging updates would be safer to avoid when we should release
ASAP due to freeze time.
Even to me the change in
On 17.04.2012 16:04, Sven Schnelle wrote:
Package: vgabios
Version: 0.7a-2
Severity: wishlist
I'm using kvm + vgabios on a QXGA resolution screen. Unfortunately, it doesn't
have this resolution in its VBE tables. Here's a patch to add it:
diff -Naur vgabios-0.6c.ori/vbetables-gen.c
severity 677528 normal
tags 677528 + upstream confirmed
thanks
On 14.06.2012 19:24, Jakub Wilk wrote:
Package: qemu-kvm
Version: 1.1~rc+dfsg-1
Severity: minor
$ kvm -m 1.4g
KVM internal error. Suberror: 1
Wow. Just.. wow.
I'm raising the severity to normal, it is definitely not a minor
On 15.06.2012 00:10, Gary Dale wrote:
I finally bit the bullet to try a fresh install from the command line. After
much gnashing of teeth, the command line I came up with is:
virt-install -n ghostwheel --cpu kvm64 -c
/home/garydale/Downloads/WindowsXPPro64.iso --os-variant=winxp64 --disk
On 14.06.2012 16:39, Sergey B Kirpichev wrote:
[lots of good stuff]
Guys. I'm leaving for a 2-week vacation (I had no vacation
for 2 years in a row, and can't stand anymore). I'll try to
review this stuff while being in a sea beach, maybe will commit
something.
But to me, much more important
On 15.06.2012 01:46, Gary Dale wrote:
On 14/06/12 04:26 PM, Michael Tokarev wrote:
kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
-cpu qemu64
I get an error about SDL:
I told you it will open an X window. Give it a $DISPLAY.
/mjt
--
To UNSUBSCRIBE, email
On 15.06.2012 02:11, Gary Dale wrote:
[]
It doesn't open an X window. It complains about:
No protocol specified
Could not initialize SDL(No available video device) - exiting
Now I seem to have SDL installed. However, searching through the kvm
documentation to find information about SDL
forwarded 677528 http://thread.gmane.org/gmane.comp.emulators.kvm.devel/92493
thanks
On 15.06.2012 02:41, Jakub Wilk wrote:
* Michael Tokarev m...@tls.msk.ru, 2012-06-14, 23:25:
$ kvm -m 1.4g
KVM internal error. Suberror: 1
Wow. Just.. wow.
I'm raising the severity to normal
14.06.2012 17:56, Steve Petruzzello wrote:
Package: autofs
Version: 5.0.6-2
Severity: wishlist
Hi,
Here is a patch correcting minor typos in /etc/init.d/autos.
Well. these are not typos, these were old attempts to
internationalize the messages initscript produces:
- log_action_begin_msg
18.06.2012 23:14, Bastian Blank wrote:
Package: seabios
Version: 1.7.0-1
Severity: wishlist
Please enable Xen support in seabios. It will be used by the next Xen
release and maybe the version in Wheezy.
Do you know what's the outcome of this? As far as I remember, it is just
a config option,
16.06.2012 13:34, Sergey Kirpichev wrote:
On Fri, Jun 15, 2012 at 12:47 AM, Michael Tokarevm...@tls.msk.ru wrote:
I'll try to review this stuff while being in a sea beach,
maybe will commit something.
Unfortunately I can't do anything from here at all. The wifi in the hotel
works, but
Ok. After fixing the connectivity a bit, I was finally able to
take a look at the patches. I applied whole series (5 patches)
but I had to edit two of them:
0002-Fix-spelling-in-binaries-and-debian-changelog-fix-li.patch
I removed touching of debian/changelog from there, and fixed
the
Ok. I reviewed the patches and proposed solutions, but
I can't commit/implement any of them so far.
The main issue which all proposed solutions share is when
there's a large array, say, md0, and a small array, say,
md1, both shares the same set of underlying disks, so md
subystem will not
21.06.2012 17:24, Marc Lehmann пишет:
Package: autofs
Version: 4.1.4+debian-3
Really?
Severity: important
after upgrading, accessing automount-mountpoints make automount segfault:
Upgrading from what to what?
Thanks,
/mjt
--
To UNSUBSCRIBE, email to
tags 673904 + wontfix
thanks
As I explained several times, this problem must be fixed
on both sides - both gmp and qemu, and it is more correct
to fix it in gmp side. The problem im gmp is that it uses
abort() statements in cases where it detects impossible,
to its thinking, CPU. Instead of
[]
As I explained several times, this problem must be fixed
on both sides - both gmp and qemu, and it is more correct
to fix it in gmp side. The problem im gmp is that it uses
abort() statements in cases where it detects impossible,
to its thinking, CPU. Instead of these aborts(), it should
401 - 500 of 2533 matches
Mail list logo
