From: Peter Jones <pjones@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] /usr/bin/fakeroot: debian/rules: Permission denied - Building Lustre client (v2.13.53)
Date: Fri, 24 Jul 2020 12:44:47 +0000 [thread overview]
Message-ID: <E9DF4E52-8874-41CF-AD89-07FBFA678FBF@ddn.com> (raw)
In-Reply-To: <CAKVGuZYWmGswLZMAzLh1xQ=B872SwddyKt8dFGO6BynW63sQew@mail.gmail.com>
Hopefully you understand this already but just in case.- 2.13.53 is a development build and not intended for production usage. You should be able to build Ubuntu 18.04 clients for 2.12.x releases.
From: lustre-devel <lustre-devel-bounces@lists.lustre.org> on behalf of Ankit Ladhania <ankit@tripock.com>
Date: Friday, July 24, 2020 at 2:45 AM
To: "lustre-devel at lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] /usr/bin/fakeroot: debian/rules: Permission denied - Building Lustre client (v2.13.53)
Hi,
We are installing the Lustre Client (v2.13.53) on Ubuntu 18.04 (linux header: 5.4.0-42-generic)
While doing `make debs` we are getting below error:
make[1]: Leaving directory '/home/zeblok/lustre-release'
dpkg-genbuildinfo
dpkg-genchanges >../lustre_2.13.53-1_amd64.changes
dpkg-genchanges: warning: package lustre-server-utils in control file but not in files list
dpkg-genchanges: warning: package lustre-resource-agents in control file but not in files list
dpkg-genchanges: warning: package lustre-client-modules-dkms in control file but not in files list
dpkg-genchanges: info: including full source code in upload
dpkg-source -I.git -I*.out[0-9]* -I*.swp --after-build lustre-release
dpkg-buildpackage: info: full upload; Debian-native package (full source is included)
~/lustre-release/debian/tmp/modules-deb ~/lustre-release
Removing old /home/zeblok/lustre-release/debian/tmp/modules-deb/usr_src/modules/lustre/ tree
Extracting the package tarball, /usr/src/lustre.tar.bz2, please wait...
/usr/bin/fakeroot: 175: /usr/bin/fakeroot: debian/rules: Permission denied
/usr/bin/fakeroot: 175: /usr/bin/fakeroot: debian/rules: Permission denied
BUILD FAILED!
See /home/zeblok/lustre-release/debian/tmp/modules-deb/var_cache_modass/lustre.buildlog.5.4.0-42-generic.1595583181 for details.
mv: cannot stat '../lustre-dev__*.deb': No such file or directory
mv: cannot stat '../lustre-source__all.deb': No such file or directory
mv: cannot stat '../lustre-iokit__*.deb': No such file or directory
mv: cannot stat '../lustre-tests__*.deb': No such file or directory
mv: cannot stat '../lustre-*-utils__*.deb': No such file or directory
mv: cannot stat '../lustre_.dsc': No such file or directory
mv: cannot stat '../lustre__*.changes': No such file or directory
mv: cannot stat '../lustre_.tar.gz': No such file or directory
mv: cannot stat '../lustre-*-modules-5.4.0-42-generic__*.deb': No such file or directory
autoMakefile:1190: recipe for target 'debs' failed
make: *** [debs] Error 1
Also tried doing 'chmod a+x debian/rules' but with no progress.
Not able to understand why this is breaking, any help is highly appreciated.
Regards,
Ankit Ladhania
IN: +91 933 444 2209
US: +1 (256) 203-0077
Skype: ankit.ladhania
[Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20200724/053ffcb3/attachment.html>
prev parent reply other threads:[~2020-07-24 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 9:45 [lustre-devel] /usr/bin/fakeroot: debian/rules: Permission denied - Building Lustre client (v2.13.53) Ankit Ladhania
2020-07-24 10:00 ` Degremont, Aurelien
2020-07-24 10:50 ` Ankit Ladhania
2020-07-24 11:35 ` [lustre-devel] [UNVERIFIED SENDER] " Degremont, Aurelien
2020-07-24 22:29 ` [lustre-devel] " Christian Kuntz
2020-07-27 17:08 ` Ankit Ladhania
2020-07-24 12:44 ` Peter Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E9DF4E52-8874-41CF-AD89-07FBFA678FBF@ddn.com \
--to=pjones@whamcloud.com \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.