search for: 763102

Displaying 12 results from an estimated 12 matches for "763102".

Did you mean: 761302
2015 Aug 21
0
Processed: unarchiving 763102, reopening 763102, forcibly merging 763102 787193
Processing commands for control at bugs.debian.org: > unarchive 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Unarchived Bug 763102 > reopen 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils...
2014 Sep 27
5
Bug#763102: xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains
Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File
2015 Aug 21
0
Processed: tagging 763102
Processing commands for control at bugs.debian.org: > tags 763102 + patch Bug #763102 [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Bug #787193 [xen-utils-common] xen-utils-common: xen-init-list crashes with TypeError, renders reboots unfeasible after upgrade from wheezy to jessie...
2015 Aug 22
2
Bug#763102: Bug#763102: xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains
...how on earth did I miss it! > there are two > places that need to be fixed. I'm using it since November. Thanks. Since loads is a classmethod I think the right fix for that issue is to s/self/cls/ in the body rather than s/cls/self/ in the declaration. I've updated the feature/bug763102 with the following extra patch: @@ -14,7 +14,7 @@ class SXPParser(object): def loads(cls, input): data = [] stack = [] - for match in self.tokenizer_re.finditer(input): + for match in cls.tokenizer_re.finditer(input): if match.group('open')...
2015 Aug 23
0
Bug#763102: Bug#763102: xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I've updated the feature/bug763102 with the following extra patch: With both your patches applied, xen-init-list works. Cheers, Volker -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlXZ2cgACgkQgKD4KXUzSrhELACg2CCtFNUPtHxNz7XgpQjaYH6b Gn4An26yNob9A7vhz1L8RTWTMCrfc6RY =M2dx -----END PGP SIGNATURE-----
2014 Nov 15
0
Processed: closing 726827, closing 763102, closing 711273, closing 744163, closing 603366, closing 648670 ...
...1' at version '4.4.0-1' with architecture '' Unable to make a source version for version '4.4.0-1' Marked as fixed in versions 4.4.0-1. Bug #726827 [xen-utils-4.1] xen-utils-4.1: Xen doesn't start on a laptop with Nvidia Optimus graphics Marked Bug as done > close 763102 4.4.0-1 Bug #763102 [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Marked as fixed in versions xen/4.4.0-1. Bug #763102 [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdow...
2015 May 29
1
Bug#787193: xen-utils-common: xen-init-list crashes with TypeError, renders reboots unfeasible after upgrade from wheezy to jessie
Package: xen-utils-common Version: 4.4.1-9 Severity: important This bug was already reported as #763102 and was brushed off because maintainer says it implicates xend which is not there in 4.4 anymore. However, this problem is present during upgrade from wheezy to jessie and means that reboots are not possible without physical interventions. As noted in #763102, during shutdown, we can see this mess...
2015 Aug 21
2
Bug#763102: xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains
...p) + s = SXPParser.loads(p) self.data = d = {} for i in s: if i and i[0] == 'domain': Please can you try making that change to /usr/lib/xen-common/bin/xen -init-list and report whether or not it works? I've also published the fix to the feature/bug763102 branch of the pkg -xen git repository. Thanks, Ian
2015 Aug 21
0
Bug#763102: xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ian, you can use the patch I posted in the original report, there are two places that need to be fixed. I'm using it since November. Cheers, Volker -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlXXpS8ACgkQgKD4KXUzSriihQCgidnLz9Lx475uQ4dzWz4jDrzM nsUAn3Z/Sy3tA2yquXvyAXnY04pxgOop =GYjR -----END PGP SIGNATURE-----
2015 Aug 21
0
Bug#787193: xen-utils-common: xen-init-list crashes with TypeError, renders reboots unfeasible after upgrade from wheezy to jessie
> This bug was already reported as #763102 and was brushed off because maintainer > says it implicates xend which is not there in 4.4 anymore. Quoting the explanation sent when closing #763102: If you think a bug has been associated with xend in error please check if it still reproduces with the packages in Jessie (currentl...
2015 Jan 09
0
Processed (with 2 errors): user debian-qa@lists.debian.org, affects 774889, affects 771755, unarchiving 767561 ...
...s Klumpp <mak at debian.org>} [pk-update-icon] No update notifications - Debian Wheezy 7.6 - gnome-packagekit 3.4.2-2 Added indication that 710355 affects gnome-packagekit Added indication that 710565 affects gnome-packagekit Added indication that 757989 affects gnome-packagekit > notfound 763102 4.4.0-5 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains No longer marked as found in versions xen/4.4.0-5. > fixed 760327 2:8.35-3.2 Bug #760327 {Done: Tho...
2002 Oct 10
0
Re:
Torsdag, 10 oktober 2002, skrev du: >On the other hand, it's certainly possible that the published >specification contains errors that need to be addressed. It is not a >monolithic document written in stone. The only way we'll really be able >to sort those issues out is when people try to build stuff from scratch >using the published data, and come across discrepancies.