On Saturday 20 September 2014 02:58 PM, 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, with the goal to release for distros at the end of the week. This i going to be solely bugfixes and more hardware targets validation tests.

The delay is due to both personal issues (it's amazing how a sick kid can crush your productivity to ashes, even for a minor throat infection...) and some delays in getting access to the proper test hardware for some of the validation tests.

Can you push your changes to the repo at least?

I will prep something out of that. The current lio-utils build has broken and I don't want to spend time there. I'd instead bring in the new targetcli which would invalidate the old lio-utils.


I just pushed configshel 1.5 into experimental.
Next in line is rtslib and targetcli (both from git tip). Once all are in experimental, and we have some test results, I'll push it to unstable.


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
W: python-rtslib: file-in-unusual-dir var/target/fabric/loopback.spec
W: python-rtslib: file-in-unusual-dir var/target/fabric/qla2xxx.spec
W: python-rtslib: file-in-unusual-dir var/target/fabric/tcm_fc.spec
W: python-rtslib: file-in-unusual-dir var/target/fabric/usb_gadget.spec


I have added a lintian override for now. From what I recall, we didn't want to change it because this same path was consumed in the kernel component of LIO.

--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

Reply via email to