Thanks Chris,
I'll take a look at it in the coming days!
Best,
--
Jerome
On 12/17/2014 11:03 PM, Chris Boot wrote:
On 17 Dec 2014, at 21:11, Chris Boot wrote:
On 17 Dec 2014, at 13:56, Ritesh Raj Sarraf wrote:
On 10/07/2014 03:54 PM, Jerome Martin wrote:
On 10/07/2014 12:
On 10/16/2014 07:49 PM, Ritesh Raj Sarraf wrote:
Thank you for this bug report. I'm just replying to say that I'll look
into these issues very soon. THanks.
Excellent.
Jerome: In case if you have time, there recently have been a couple of
bug reports filed against targetcli, for the newer ve
On 10/07/2014 12:21 PM, Ritesh Raj Sarraf wrote:
On Tuesday 07 October 2014 03:49 PM, Ritesh Raj Sarraf wrote:
Okay!! Thanks to both of you. I will prepare something next week. My
only request is if (other) users can test it in time.
By the way, Jerome, do you still plan on a newer release
Hi Chris et al.,
On 10/05/2014 05:45 PM, Chris Boot wrote:
From my perspective, it would be nice to keep the old tcm_node and lio_node
tools around. I know that they are deprecated but there are a lot of tools
around that rely on them.
Do you have any particular examples of such tools?
Are
transition lio-utils code to start the targets and then dump the config
in the new format.
But that would involve keeping around the lio-utils code just for that
one-shot usage... And I hate the idea of having a dependency on it just
for that.
WDYT?
On 10/05/2014 10:30 AM, Jerome Martin wrote:
On
On 10/05/2014 09:37 AM, Ritesh Raj Sarraf wrote:
Thanks for the bug report.
Jerome: How can we ensure to have the old 2.x settings / targets in 3.x ?
Manually, this is easy.
But to automate package upgrade is bit of a brain-twister.
I haven't found yet a good way to do it.
Basically, the con
On 09/21/2014 12:14 PM, Michael Prokop wrote:
* Jerome Martin [Sat Sep 20, 2014 at 07:57:47PM +0200]:
I could use (read "desperately require" :-) ) tests and reports
myself, so please guys, I will be working on the upstream code next
week, now is a good time to fill my inbox wi
ime to fill my inbox with reports :-)
Kernel version is always one critical piece of information for testing,
so please remember to include it!
--
Jerome Martin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi Ritesh,
On 09/20/2014 11:39 AM, Ritesh Raj Sarraf wrote:
By the way, are there plans on fixing this ?
E: python-rtslib: non-standard-dir-in-var var/target/
W: python-rtslib: file-in-unusual-dir var/target/fabric/ib_srpt.spec
W: python-rtslib: file-in-unusual-dir var/target/fabric/iscsi.spec
Excellent, thanks Ritesh!
On 09/20/2014 11:28 AM, Ritesh Raj Sarraf wrote:
On Friday 19 September 2014 03:40 PM, Ritesh Raj Sarraf wrote:
On Thursday 18 September 2014 05:56 PM, Jerome Martin wrote:
Well, obviously I missed that deadline, and am planning on being on
it full-time next week
Hi,
On 09/18/2014 12:36 PM, Michael Prokop wrote:
Hi,
* Jerome Martin [Tue Aug 12, 2014 at 12:05:18PM +0200]:
Hi Ritesh,
Sorry for the late reply, I am on vacation right now.
I am aiming at first week of September for the final release.
Will keep you posted :-)
The merge effort will
Hi Ritesh,
Sorry for the late reply, I am on vacation right now.
I am aiming at first week of September for the final release.
Will keep you posted :-)
The merge effort will not be carried out for this one, though, and it
still is to be decided how we will version it etc.
Best Regards,
--
Je
12 matches
Mail list logo
