Bug#933343: marked as done (ITP: tcmu -- handles the userspace side of the LIO TCM-User backstore)
Your message dated Mon, 05 Aug 2019 11:00:25 +0000
with message-id <E1huaj3-000FDt-5r@fasolo.debian.org>
and subject line Bug#933343: fixed in tcmu 1.4.0-1
has caused the Debian Bug report #933343,
regarding ITP: tcmu -- handles the userspace side of the LIO TCM-User backstore
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.)
--
933343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933343
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: ITP: tcmu -- handles the userspace side of the LIO TCM-User backstore
- From: Sebastien Delafond <seb@debian.org>
- Date: Mon, 29 Jul 2019 15:25:05 +0200
- Message-id: <156440670536.5584.2577605646467966970.reportbug@hulk.befour.org>
Package: wnpp
Severity: wishlist
Owner: Sebastien Delafond <seb@debian.org>
* Package name : tcmu
Version : 1.4.0
URL : https://github.com/open-iscsi/tcmu-runner
* License : LGPL 2.1 & Apache 2.0
Programming Lang: C
Description : handles the userspace side of the LIO TCM-User backstore
LIO is the SCSI target in the Linux kernel. It is entirely kernel
code, and allows exported SCSI logical units (LUNs) to be backed by
regular files or block devices. But, if we want to get fancier with
the capabilities of the device we're emulating, the kernel is not
necessarily the right place. While there are userspace libraries for
compression, encryption, and clustered storage solutions like Ceph or
Gluster, these are not accessible from the kernel.
.
The TCMU userspace-passthrough backstore allows a userspace process
to handle requests to a LUN. But since the kernel-user interface that
TCMU provides must be fast and flexible, it is complex enough that
we'd like to avoid each userspace handler having to write boilerplate
code.
.
tcmu-runner handles the messy details of the TCMU interface -- UIO,
netlink, pthreads, and DBus -- and exports a more friendly C plugin
module API. Modules using this API are called "TCMU
handlers". Handler authors can write code just to handle the SCSI
commands as desired, and can also link with whatever userspace
libraries they like.
--- End Message ---
--- Begin Message ---
Source: tcmu
Source-Version: 1.4.0-1
We believe that the bug you reported is fixed in the latest version of
tcmu, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 933343@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastien Delafond <seb@debian.org> (supplier of updated tcmu package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 29 Jul 2019 16:01:03 +0200
Source: tcmu
Binary: libtcmu2 libtcmu2-dbgsym tcmu-runner tcmu-runner-dbgsym
Architecture: source amd64
Version: 1.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team <team+freexian@tracker.debian.org>
Changed-By: Sebastien Delafond <seb@debian.org>
Description:
libtcmu2 - Library that handles the userspace side of the LIO TCM-User backs
tcmu-runner - Daemon that handles the userspace side of the LIO TCM-User backst
Closes: 933343
Changes:
tcmu (1.4.0-1) unstable; urgency=medium
.
* First release (Closes: #933343)
Checksums-Sha1:
4610386fa81cc5e1566ee6af895de0201752f874 1705 tcmu_1.4.0-1.dsc
899dad638ff21273a5e8e42efbfeab52c8f50e73 122448 tcmu_1.4.0.orig.tar.xz
82c22281e68b8b05e722896104ed8cb0c15be28c 4592 tcmu_1.4.0-1.debian.tar.xz
214b746d8c2ec5394ff040f50ab964178b8f876b 117768 libtcmu2-dbgsym_1.4.0-1_amd64.deb
5f4e20537f66cd975faf67648d898be41fa1e372 39564 libtcmu2_1.4.0-1_amd64.deb
6ce21e968dee43699fab25baee7a2e515d426709 213820 tcmu-runner-dbgsym_1.4.0-1_amd64.deb
d31642893ecee5aa9dd9a7190da6bfa2adab4a4c 77472 tcmu-runner_1.4.0-1_amd64.deb
a4310ad1136b1638b2739d990a070016ac8ae9cc 8622 tcmu_1.4.0-1_amd64.buildinfo
Checksums-Sha256:
3e71e5431d57836d851c68078ea462c15ef4c0064f607dbb87154b610062b989 1705 tcmu_1.4.0-1.dsc
a0aa332608fcc7400723e3b406480f75a5b30578126298836611c67ebf426b2f 122448 tcmu_1.4.0.orig.tar.xz
fcaac3945a33effe286419260ceab19a5dc5dc256aae6e5f26d260cf2efbfb2c 4592 tcmu_1.4.0-1.debian.tar.xz
921c160701428f4fff4cb9f87d2258bce1840ab50e47917517eabd6a31b50245 117768 libtcmu2-dbgsym_1.4.0-1_amd64.deb
dcb07a4c3e052b9b571f85e3cc01604ebc50cea8e936610092176ac484b12d60 39564 libtcmu2_1.4.0-1_amd64.deb
b92e29c473692aad765b490636339efd2582bb0fd0c114ec83eb552f2eea4506 213820 tcmu-runner-dbgsym_1.4.0-1_amd64.deb
55d7c5e861c28a119d3e821bf8d27512d847cf048a343c3bd281ac4b0e6b1bb4 77472 tcmu-runner_1.4.0-1_amd64.deb
1f51f0167d7332a38f7eefc697c41f27d6825461732cc62f419aeaededdcfe38 8622 tcmu_1.4.0-1_amd64.buildinfo
Files:
5c340d69ecfe9308cf010bd4d358465d 1705 admin optional tcmu_1.4.0-1.dsc
75104ea72e67e944b2347f390961d603 122448 admin optional tcmu_1.4.0.orig.tar.xz
b27ab0662038334eed30f9f3b4d5aefe 4592 admin optional tcmu_1.4.0-1.debian.tar.xz
f63a77f4f649ddb259ac3734f50e192d 117768 debug optional libtcmu2-dbgsym_1.4.0-1_amd64.deb
552b32c214ce260395a87fd578441433 39564 libs optional libtcmu2_1.4.0-1_amd64.deb
7f801562bee88dfb521703a34a5ccbe3 213820 debug optional tcmu-runner-dbgsym_1.4.0-1_amd64.deb
783e4b3a3d7846802e9dd5c17a970ef3 77472 admin optional tcmu-runner_1.4.0-1_amd64.deb
cacb67c429b5801bce57c9721622761b 8622 admin optional tcmu_1.4.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAl1H3QUACgkQEL6Jg/PV
nWRXbAf/W9FvFxAI6zJJpFFPslrf0IefetFYZOMs8s0fCPiSvX7muAYXPAtydy5g
x/M/oE+5vGJ2ypowfkaP/Qa2vB0T1gYotC9LamMuNgnwuEoYM09Jd9q6uvpeWeGt
tZdAYk0UocLVWfzLoQnhYjJazqm/D1/cC3Nwd5oE0lAtih06Udm+/POUMvHShHn7
5XtoyKrhre6rWrNPBGkWZoRNtJFyeeSR4A6uu7Q22ErzA5/tTXOCrKrN4qEGYpFv
GQjxYuZRVuVK1rukmXAb2HgZPYaudBGY0GxM/XxOOUcAYPzCP/VBVokAKcjtIztb
B1PpvE9o1cuggAjaeUOsJyxf697Gsg==
=ozp5
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: