[tahoe-lafs-trac-stream] [tahoe-lafs] #1717: 'sudo make install' doesn't work

[tahoe-lafs]

#1717: 'sudo make install' doesn't work
----------------------------+--------------------------------
     Reporter:  davidsarah  |      Owner:
         Type:  defect      |     Status:  new
     Priority:  major       |  Milestone:  undecided
    Component:  packaging   |    Version:  1.9.1
   Resolution:              |   Keywords:  setuptools install
Launchpad Bug:              |
----------------------------+--------------------------------
Description changed by davidsarah:

Old description:

> erpo41 wrote on volunteergrid2-l:
> > Hi all,
> >
> > Since my node seems stable, I'm beginning to upload my backups into
> > the grid. Since tahoe is running on a dedicated server in its own user
> > account, I need to make the tahoe executable available to my personal
> > user account on that server. (Previously I had been running tahoe out
> > of /home/volunteergrid2/allmydata-tahoe-1.9.1/bin.)
> >
> > When I tried to install tahoe, I got the following error messages:
> >
> > -------------------
> > eric at io:/home/volunteergrid2/allmydata-tahoe-1.9.1$ sudo make install
> > python ./setup.py install --single-version-externally-managed
> > running update_version
> > no version-control data found, leaving _version.py alone
> > running install
> > error: You must specify --record or --root when building system
> packages
> > make: *** [install] Error 1
> > ----------------------
> >
> > This is why I hate building/installing from source on Linux. What do
> > --record and --root do? Does "building system packages" refer to
> > building the executable or a deb/rpm package? Do I actually have to go
> > back and rebuild the tahoe executable with those options? If so, where
> > do I insert those options in the "python setup.py build" command line
> > recommended by quickstart.rst for building the executable? What do
> > those options do and what should I set them to on my system?
>
> The 'install' Makefile target should not be using
> {{{--single-version-externally-managed}}}.
>
> As a workaround, use '{{{sudo python ./setup.py install}}}'.

New description:

 erpo41 wrote on volunteergrid2-l:
 > Hi all,
 >
 > Since my node seems stable, I'm beginning to upload my backups into
 > the grid. Since tahoe is running on a dedicated server in its own user
 > account, I need to make the tahoe executable available to my personal
 > user account on that server. (Previously I had been running tahoe out
 > of /home/volunteergrid2/allmydata-tahoe-1.9.1/bin.)
 >
 > When I tried to install tahoe, I got the following error messages:
 {{{
   eric at io:/home/volunteergrid2/allmydata-tahoe-1.9.1$ sudo make install
   python ./setup.py install --single-version-externally-managed
   running update_version
   no version-control data found, leaving _version.py alone
   running install
   error: You must specify --record or --root when building system packages
   make: *** [install] Error 1
 }}}
 > This is why I hate building/installing from source on Linux. What do
 > --record and --root do? Does "building system packages" refer to
 > building the executable or a deb/rpm package? Do I actually have to go
 > back and rebuild the tahoe executable with those options? If so, where
 > do I insert those options in the "python setup.py build" command line
 > recommended by quickstart.rst for building the executable? What do
 > those options do and what should I set them to on my system?

 The 'install' Makefile target should not be using
 {{{--single-version-externally-managed}}}.

 As a workaround, use '{{{sudo python ./setup.py install}}}'.

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1717#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage