Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On 09/21/2014 12:36 AM, Ritesh Raj Sarraf wrote:
On Saturday 20 September 2014 03:23 PM, Jerome Martin wrote:
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.
The manpage, written by Andy, refers to /var/lib/. Which would imply
that Fedora/RHEL and all its derivatives must be using the new path.
I don't see any mention of /var/lib. In any case, RH packaging isn't
creating /var/target/{alua,pr} directories, whose absence will cause PR
ops to fail in 3.11+-based kernels even if they don't use APTPL. I need
to fix that soon.
If I came up with a kernel patch that made the path that ALUA PR files
were written to settable via configfs, would that also be helpful to you?
Nick, thoughts?
Regards -- Andy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On Saturday 20 September 2014 03:23 PM, Jerome Martin wrote: 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. The manpage, written by Andy, refers to /var/lib/. Which would imply that Fedora/RHEL and all its derivatives must be using the new path. -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
Hi, * Jerome Martin [Sat Sep 20, 2014 at 07:57:47PM +0200]: On 09/20/2014 01:24 PM, Ritesh Raj Sarraf wrote: On Saturday 20 September 2014 02:58 PM, Ritesh Raj Sarraf wrote: 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. Okay!! All of the new components of LIO, i.e. configshell, rtslib and targetcli are now in Debian experimental. Now the quality of these packages depend on user testing and bug reports. Great, thanks for that. Michael: Since you (and others on this bug report) have interest in LIO, I'd request if you folks can give the version in experimental a test. At this time, I do not have the resources to test an LIO stack. 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 with reports :-) Kernel version is always one critical piece of information for testing, so please remember to include it! Sure, I'll test my use-cases ASAP and will report back for sure. Thanks for your work, highly appreciated. regards, -mika- signature.asc Description: Digital signature
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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 with reports :-) Kernel version is always one critical piece of information for testing, so please remember to include it! Sure, I'll test my use-cases ASAP and will report back for sure. Thanks for your work, highly appreciated. Thank you! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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, 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. -- Ritesh Raj Sarraf RESEARCHUT -http://www.researchut.com Necessity is the mother of invention. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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.
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On Saturday 20 September 2014 02:58 PM, Ritesh Raj Sarraf wrote: 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. Okay!! All of the new components of LIO, i.e. configshell, rtslib and targetcli are now in Debian experimental. Now the quality of these packages depend on user testing and bug reports. Michael: Since you (and others on this bug report) have interest in LIO, I'd request if you folks can give the version in experimental a test. At this time, I do not have the resources to test an LIO stack. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On 09/20/2014 01:24 PM, Ritesh Raj Sarraf wrote: On Saturday 20 September 2014 02:58 PM, Ritesh Raj Sarraf wrote: 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. Okay!! All of the new components of LIO, i.e. configshell, rtslib and targetcli are now in Debian experimental. Now the quality of these packages depend on user testing and bug reports. Excellent. Michael: Since you (and others on this bug report) have interest in LIO, I'd request if you folks can give the version in experimental a test. At this time, I do not have the resources to test an LIO stack. 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 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
@Python Team: Can you please provide some guidance on this bug ? Earlier the python modules used to get installed into pyshared/ folder, from which I created symlinks to /usr/sbin/. Now, the modules get installed into python specific dist-packages/ folder. How do we add symlinks in this scenario ? @Michael / Jerome: In case the new version of targetcli does not make on time, we may have to use this as the fallback plan. Ritesh On Thursday 18 September 2014 04:06 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 not be carried out for this one, though, and it still is to be decided how we will version it etc. Any news here, Jerome or Ritesh? I'm just worried because I'd like to see targetcli in Debian/jessie. :) Thanks! regards, -mika- -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
[Ritesh Raj Sarraf, 2014-09-19] @Python Team: Can you please provide some guidance on this bug ? Earlier the python modules used to get installed into pyshared/ folder, from which I created symlinks to /usr/sbin/. Now, the modules get installed into python specific dist-packages/ folder. How do we add symlinks in this scenario ? /usr/share/pyshared is implementation detail (changed recently) which you shouldn't know about (and use it since you shouldn't know it exists ;). Symlinking to /usr/lib/python2.7/dist-packages/foo.py is not a good idea as well (although there will be no Python 2.8, I hope - if you use it, backporters will not be happy). I suggest to use `python -m foo` or write a wrapper that uses this command or Python script that imports foo and calls foo.main() (where main() is whatever is called after if __name__ == '__main__': in this file) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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 not be carried out for this one, though, and it still is to be decided how we will version it etc. Any news here, Jerome or Ritesh? I'm just worried because I'd like to see targetcli in Debian/jessie. :) Thanks! regards, -mika- signature.asc Description: Digital signature
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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 not be carried out for this one, though, and it still is to be decided how we will version it etc. Any news here, Jerome or Ritesh? 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. I'm just worried because I'd like to see targetcli in Debian/jessie. :) Yes, I would love that too :-) Thanks for caring and asking! ;-) Thanks! regards, -mika- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
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, -- Jerome On 08/11/2014 10:43 AM, Ritesh Raj Sarraf wrote: On 08/09/2014 01:05 PM, Ritesh Raj Sarraf wrote: On 08/09/2014 03:31 AM, Aurelien Jarno wrote: On Wed, Jun 04, 2014 at 12:16:06PM +0530, Ritesh Raj Sarraf wrote: For the sake of users who may land on this bug report. lio-utils is deprecated upstream. Users are advised to switch to targetcli. lio-utils may soon be removed from the Debian repositories. Even if lio-utils is deprecated, targetcli depends on it. Ignoring this bug just mean we currenyl don't have scsi target support in Jessie, which is be a pitty. No. It is on my list and will be fixed very soon.. Personal stuff has delayed it but soon I'll be resuming work on it. Jerome, When do you plan the 3.0 release ? I see you and Andy talking on merges and newer designs. Please let me know the timelines when you plan a release. Debian will freeze in 2 months and I'd like to push the newer stack as soon as possible. -- Ritesh Raj Sarraf |http://people.debian.org/~rrs Debian - The Universal Operating System -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On 08/09/2014 01:05 PM, Ritesh Raj Sarraf wrote: On 08/09/2014 03:31 AM, Aurelien Jarno wrote: On Wed, Jun 04, 2014 at 12:16:06PM +0530, Ritesh Raj Sarraf wrote: For the sake of users who may land on this bug report. lio-utils is deprecated upstream. Users are advised to switch to targetcli. lio-utils may soon be removed from the Debian repositories. Even if lio-utils is deprecated, targetcli depends on it. Ignoring this bug just mean we currenyl don't have scsi target support in Jessie, which is be a pitty. No. It is on my list and will be fixed very soon.. Personal stuff has delayed it but soon I'll be resuming work on it. Jerome, When do you plan the 3.0 release ? I see you and Andy talking on merges and newer designs. Please let me know the timelines when you plan a release. Debian will freeze in 2 months and I'd like to push the newer stack as soon as possible. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On 08/09/2014 03:31 AM, Aurelien Jarno wrote: On Wed, Jun 04, 2014 at 12:16:06PM +0530, Ritesh Raj Sarraf wrote: For the sake of users who may land on this bug report. lio-utils is deprecated upstream. Users are advised to switch to targetcli. lio-utils may soon be removed from the Debian repositories. Even if lio-utils is deprecated, targetcli depends on it. Ignoring this bug just mean we currenyl don't have scsi target support in Jessie, which is be a pitty. No. It is on my list and will be fixed very soon.. Personal stuff has delayed it but soon I'll be resuming work on it. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On Wed, Jun 04, 2014 at 12:16:06PM +0530, Ritesh Raj Sarraf wrote: For the sake of users who may land on this bug report. lio-utils is deprecated upstream. Users are advised to switch to targetcli. lio-utils may soon be removed from the Debian repositories. Even if lio-utils is deprecated, targetcli depends on it. Ignoring this bug just mean we currenyl don't have scsi target support in Jessie, which is be a pitty. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
For the sake of users who may land on this bug report. lio-utils is deprecated upstream. Users are advised to switch to targetcli. lio-utils may soon be removed from the Debian repositories. On 06/03/2014 12:31 AM, David Suárez wrote: Source: lio-utils Version: 3.1+git2.fd0b34fd-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd' # Hack for now. chmod a+x /«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory make[1]: *** [override_dh_link] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/lio-utils_3.1+git2.fd0b34fd-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
Source: lio-utils Version: 3.1+git2.fd0b34fd-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd' # Hack for now. chmod a+x /«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory make[1]: *** [override_dh_link] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/lio-utils_3.1+git2.fd0b34fd-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
