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
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.
Yes, the problem is that the kernel side uses this path unfortunately.
We could relocate policy and fabric to /var/lib/target, but that would
mean keeping both /lib/target and /var/target around for now, as the
kernel will use that for storing alua metadata in /var/target/alua.
However, what about relocating now, and keeping around a symlink to
/var/target, created in post-install?
This way, as soon as Nic can push the relocation to /var/lib/alua, we
are ready and just have to remove the symlink from packaging.
I am cc'ing the ML on this one.
Best,
--
Jerome
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
