Bug#528700: Visible in 6.12.22, still?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, May 25, 2011 at 09:11:04PM +0200, Steffen Möller wrote: I just uploaded 6.12.27. Had not verified that the fix made it into the source tree. Does it fix the issue? Yes, that looks good. Boinc starts up happily now. - -- Paul Saunders -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJN3j7bAAoJEKB7YbRsd8TG3hgP/0gJzUEkZ0s90hWoHydxieE2 IbkPJZs6vvzarXo+cwAyCdAo3ulv57fjmeKwrMGQkGVQLtVr7YZ/ej+tRRVvc/xr 2YQHJCE6lcdCG+wnbmyoAxhMRPjVLISeX+C/L/bZTAOaoHZoJtLUSnaK37nac72/ /3YinFAuUQik9FGgFiWkgdHGkLMjwOyOBacIjWhSqao9uu68CjAwCSPPHfAjgLBh D1QoZBEj2SdwrSv8VvqqHp7m1ZH+G1lZsbLIVGkgpUDspYKDsZXKHmtaQvZSDR9E YkXaltNcF7LI9oTeYdSvsvTcqGl9ectHDwVedOXt2I6wwXR3DOBAQ35Rz9k1UVzX qbYh4RVAEvs7J89Ns+AjDLrReGaVU/BnhAy56d89o19UZBDjovtNux5uC5f/ut+k rj1a393auLLypKjQBHQVa/gXiEzQKBggAEMcnOxkPGlJ451dxaNO5D6puvG8meSo 5+nsvqx2XdrZ3sgOh+cea6q8itPZvx6kzPfKrB8bbjSsGExdIRc/9Kmjjk3HfCtv M+Ze+IeZbKjzzVxxWGIp8qe4Er98eXbVR1SoaXPvF53nXO0bd+BUFbui8Mc6ZBBq bjCoA/HQQWnQjXyr+jyTvBx9FBloxWX4hZ8zXPghuIkCXaEXGMPKKQmOeYZnNkDV cJOsbpGcWBqXMxihMFka =+RHk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528700: Visible in 6.12.22, still?
On 05/24/2011 12:11 PM, Darac Marjal wrote: On Sat, Apr 16, 2011 at 10:33:32PM +0200, Steffen Möller wrote: Hello, we had upstream fix something for the manager of 6.10.58, so maybe there is something for the client side of 6.10.58, too. It very much looks like it, indeed. There is a version 6.10.60 out and I'd need to get it confirmed for that first, I am afraid. Now, I don't have a package for it, yet. Could you please try confirming it on 6.12.22? Hello, I am experiencing this problem on boinc-client 6.12.26+dfsg-1. According to http://comments.gmane.org/gmane.comp.distributed.boinc.devel/4281, this is a problem when attached to the yoyo@home project which creates a recursive symlink under ~boinc/.wine Following the links suggests that the problem is fixed upstream by BOINC bug #1108. Presumably, though this needs to be patched into the sid version? I just uploaded 6.12.27. Had not verified that the fix made it into the source tree. Does it fix the issue? Cheers, Steffen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528700: Visible in 6.12.22, still?
On Sat, Apr 16, 2011 at 10:33:32PM +0200, Steffen Möller wrote: Hello, we had upstream fix something for the manager of 6.10.58, so maybe there is something for the client side of 6.10.58, too. It very much looks like it, indeed. There is a version 6.10.60 out and I'd need to get it confirmed for that first, I am afraid. Now, I don't have a package for it, yet. Could you please try confirming it on 6.12.22? Hello, I am experiencing this problem on boinc-client 6.12.26+dfsg-1. According to http://comments.gmane.org/gmane.comp.distributed.boinc.devel/4281, this is a problem when attached to the yoyo@home project which creates a recursive symlink under ~boinc/.wine Following the links suggests that the problem is fixed upstream by BOINC bug #1108. Presumably, though this needs to be patched into the sid version? -- Paul Saunders signature.asc Description: Digital signature
Bug#528700: Visible in 6.12.22, still?
Hello, we had upstream fix something for the manager of 6.10.58, so maybe there is something for the client side of 6.10.58, too. It very much looks like it, indeed. There is a version 6.10.60 out and I'd need to get it confirmed for that first, I am afraid. Now, I don't have a package for it, yet. Could you please try confirming it on 6.12.22? This would be very helpful. Also, I would prefer bringing 6.12.x once it is tagged as stable to backports, not the 6.10.x series again. So, please give it a spin. Cheers, Steffen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
