similar to: Bug#1036475: unblock: xen/4.17.1+2-gb773c48e36-1

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was anbe at debian.org). > found 986475 4.1.9-1 Bug #986475 [libocamlnet-ocaml-doc] libocamlnet-ocaml-doc: broken symlinks: /usr/share/doc/libocamlnet-ocaml-dev/examples -> ../libocamlnet-ocaml-doc/examples Marked as found in versions ocamlnet/4.1.9-1.

FYI: The status of the xen source package in Debian's testing distribution has changed. Previous version: 4.17.0+74-g3eac216e6e-1 Current version: 4.17.1+2-gb773c48e36-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See

Package: release.debian.org Severity: normal User: release.debian.org at packages.debian.org Usertags: unblock Hi, Please unblock package xen-api. The PAM fix which we did for version 1.3.2-10 wasn't correct, and thanks to the help of Steve Langasek, we have it in a good shape now. The details of the conversation is available in the Ubuntu BTS here:

Package: release.debian.org Severity: normal The current README.Debian is quite old It gives some advice that will lead to people having a broken system (e.g. no networking). It describes a procedure for configuring networking that is completely opposite to what has been described more recently on the upstream mailing list http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 I'm happy

Package: release.debian.org Severity: normal User: release.debian.org at packages.debian.org Usertags: unblock Hi, I have uploaded xen-api/1.3.2-13, which corrects 2 things: the hostname change script was designed by CentOS, so I've fixed that, and also, the init script was hanging waiting forever if the xen-api host was a slave node, so I added a test in the init script, thanks to a patch

Package: xen-system-amd64 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainer, after upgrading my bullseye server to bookworm I ran into the issue that all VMs of type hvm are not starting anymore. xl throws an error: libxl: error: libxl_qmp.c:1399:qmp_ev_fd_callback: Domain 8:error on QMP socket: Connection reset by peer libxl: error: libxl_qmp.c:1438:qmp_ev_fd_callback: Domain

Source: xen Version: 4.17.1+2-gb773c48e36-1 Severity: serious Tags: ftbfs trixie sid Forwarded: https://github.com/xen-project/xen/commit/99a9c3d7141063ae3f357892c6181cfa3be8a280 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xen.html ... xg_offline_page.c: In function 'backup_ptes': xg_offline_page.c:191:13: error: pointer 'orig' may be used after

On Tue, 2016-01-19 at 10:39 +0000, Ian Campbell wrote: > On Thu, 2015-11-26 at 15:16 +0000, Ian Campbell wrote: > > anything better would need to be arranged upstream. > > http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=de858271c16851d662b26 > 13 > 699401df6ecec8ef8 has now landed upstream, which allows the leaf dir to > be > set at configure time and therefore

FYI: The status of the xen source package in Debian's testing distribution has changed. Previous version: 4.17.1+2-gb773c48e36-1 Current version: 4.17.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for

Moritz Muehlenhoff writes ("Re: Xen package security updates for jessie 4.4, XSA-213, XSA-214"): > On Thu, May 04, 2017 at 05:59:18PM +0100, Ian Jackson wrote: > > Should I put jessie-security in the debian/changelog and dgit push it > > (ie, from many people's pov, dput it) ? > > Yes, the distribution line should be jessie-security, but please send > a

Dear release team, I would like update the Wheezy package of xen-api with numerous small fixes. These aren't RC bugs, but I believe they are all worth fixing. I believe that the most important one to fix is #682202. Here's the changelog: * Fixes bashism in install-debian-pv.sh (Closes: #690612). * Fixes bashism in interface-visualise (Closes: #690710). * The /etc/init.d/xcp-squeezed

On Thu, 2015-11-26 at 15:16 +0000, Ian Campbell wrote: > anything better would need to be arranged upstream. http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=de858271c16851d662b2613 699401df6ecec8ef8 has now landed upstream, which allows the leaf dir to be set at configure time and therefore allows the packaging to avoid patching some stuff. HVM guests have been broken in Stretch for ages

http://bugzilla.mindrot.org/show_bug.cgi?id=271 Summary: SSHD should unblock SIGCHLD - POSIX signal blocks survive exec() Product: Portable OpenSSH Version: -current Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo:

Are you tired of being in your highschool/university classroom or at work and not being able to visit the website you want? With sfsf loan you can now unblock popular social networking sites such as Myspace, Bebo, Facebook and many other sites. Don’t give yourself a heart attack worrying about being caught surfing the sites you want at work! Use sfsf loan and your ip cannot be monitored! Get on

Processing commands for control at bugs.debian.org: > unblock 718767 with 710650 Bug #718767 [release.debian.org] transition: ocaml 4.00.1 718767 was blocked by: 726010 710650 718767 was not blocking any bugs. Removed blocking bug(s) of 718767: 710650 > thanks Stopping processing here. Please contact me if you need assistance. -- 718767:

http://bugzilla.mindrot.org/show_bug.cgi?id=271 ------- Additional Comments From djm at mindrot.org 2003-01-07 18:13 ------- We already reset SIGCHLD to SIG_DFL in main(), maybe we don't do it early enough... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=271 ------- Additional Comments From djm at mindrot.org 2003-05-16 13:29 ------- Could you verify this with a recent version, preferably including diag output. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

If SIGTERM is blocked in the main program, then it ends up still being blocked in the subprocess after we fork. This means that we cannot kill qemu by sending SIGTERM to it. This commit fixes the problem by unblocking SIGTERM unconditionally after fork. Thanks: wtfuzz on IRC for reporting and analysis. --- lib/launch-direct.c | 15 +++++++++++++++ lib/launch-uml.c | 11 +++++++++++ 2 files

On Thu, 2015-01-22 at 16:08 +0100, Stefan Bader wrote: > On 22.01.2015 13:02, Stefan Bader wrote: > > Hi, > > > > I just finished preparing the Xen-4.5 merge from experimental into our next > > release (Vivid/15.04). And something I actually should have done since the 4.4 > > times is to report back the delta I have in case there are things Debian might > >

Hi everyone at the security team, I'd like to upload an update of xen-qemu-dm-4.0 in Squeeze. Below is the Xen Security Advisory as I received it, attached is the patch that they provided. Both the debdiff and the updated packages are available in here: http://archive.gplhost.com/pub/security/xen-qemu-dm-4.0/ Please allow me to upload this fix. If you wish, I can prepare a DSA as well (but