Your message dated Thu, 08 Jul 2021 20:25:55 +0000 with message-id <E1m1aap-0008VU-9O@respighi.debian.org> and subject line unblock libvdestack has caused the Debian Bug report #990803, regarding unblock: libvdestack/0.1.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 990803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990803 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: libvdestack/0.1.2-1
- From: Renzo Davoli <renzo@cs.unibo.it>
- Date: Wed, 7 Jul 2021 21:21:49 +0200
- Message-id: <YOX+zcb2quZ/r7Ey@cs.unibo.it>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package libvdestack [ Reason ] There was a bug: a race condition. The diff is minimal: just a mutex has been added. [ Impact ] vde_msocket can return the wrong socket in case uf multithread usage. [ Tests ] There is no automated test covering that part. Manually tested. [ Risks ] No specific risks, apart from the program misbehavior. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock libvdestack/0.1.2-1 -- regards, renzo davoli
--- End Message ---
--- Begin Message ---
- To: 990803-done@bugs.debian.org
- Subject: unblock libvdestack
- From: Sebastian Ramacher <sramacher@respighi.debian.org>
- Date: Thu, 08 Jul 2021 20:25:55 +0000
- Message-id: <E1m1aap-0008VU-9O@respighi.debian.org>
Unblocked.
--- End Message ---