From: Enno B. <enn...@gm...> - 2014-01-30 18:44:43
|
Found on Solyd, also in Mint: enno@enno-desktop ~/Downloads/gramps-3.4.7 $ ./autogen.sh There is something wrong with your source tree. You are missing gramps-autogen.sh configure and make work OK |
From: Jerome <rom...@ya...> - 2014-01-30 19:21:18
|
/autogen.sh is rather for svn/git repository. https://www.gnu.org/software/autoconf/manual/autoconf.html#The-GNU-Build-System In general, to run ./autogen.sh will also run ./configure with default options. https://www.gnu.org/software/autoconf/manual/autoconf.html#Making-configure-Scripts Tarball already made these steps (automake, autotool, etc ...) https://www.gnu.org/software/automake/manual/html_node/Checking-the-Distribution.html With any tarball, you often just need: $ make $ make install # with admin rights Le jeu. 30 janv. 2014 at 19:44,Enno Borgsteede <enn...@gm...> a écrit : > Found on Solyd, also in Mint: > > enno@enno-desktop ~/Downloads/gramps-3.4.7 $ ./autogen.sh > There is something wrong with your source tree. > You are missing gramps-autogen.sh > > configure and make work OK > > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply > import > a virtual appliance and go from zero to informed in seconds. > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Enno B. <enn...@gm...> - 2014-01-30 19:49:13
|
Jerome, > With any tarball, you often just need: > > $ make > $ make install # with admin rights Not here. I was used to configure and make (install) when building GNU packages in my job, but this time it's about getting Gramps 3.4.7 for users without git, just SF. We have a situation where the 3.4.7 deb does not work on debian (SolydXK), and instructions in INSTALL don't work either, so I'm trying to figure out the simplest way to get 3.4.7 running there, and put that on the wiki, without scaring users too much. Anyone else have an opinion about this? regards, Enno |
From: Jerome <rom...@ya...> - 2014-01-31 07:32:13
|
Nick, I also looked at a proper way, which should avoid the setup.py modification around resource path, during .deb generation! http://docs.python.org/2/install/index.html Neither --install-dir schemes nor --prefix, --home, etc... will hep with Debian layout and root argument. 'python setup.py build' makes it right, then it is 'corrupted' by Debian configuration/ecosytem/environment! Sure, there is some temp solutions[1]. Into setup.py, is there any proper way for handling self.install_data with debian layout? [1] https://www.gramps-project.org/wiki/index.php?title=Debian#Build > include gramps-autogen.sh in the tar Not certain this will help, but we can include it into configure.in. http://sourceforge.net/p/gramps/source/ci/maintenance/gramps34/~/tree/configure.in Jérôme Le jeu. 30 janv. 2014 at 21:56,Nick Hall <nic...@ho...> a écrit : > On 30/01/14 19:49, Enno Borgsteede wrote: >>> With any tarball, you often just need: >>> > >>> >$ make >>> >$ make install # with admin rights >>> >> Not here. I was used to configure and make (install) when building >> GNU >> packages in my job, but this time it's about getting Gramps 3.4.7 >> for >> users without git, just SF. >> >> We have a situation where the 3.4.7 deb does not work on debian >> (SolydXK), and instructions in INSTALL don't work either, so I'm >> trying >> to figure out the simplest way to get 3.4.7 running there, and put >> that >> on the wiki, without scaring users too much. >> >> Anyone else have an opinion about this? >> > It looks like we should include gramps-autogen.sh in the tar. > > We could also review the debian dependencies. > > Nick. > > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply > import > a virtual appliance and go from zero to informed in seconds. > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2014-01-31 13:48:28
|
On 31/01/14 07:31, Jerome wrote: > I also looked at a proper way, which should avoid the setup.py > modification around resource path, during .deb generation! > > http://docs.python.org/2/install/index.html > > Neither --install-dir schemes nor --prefix, --home, etc... will hep > with Debian layout and root argument. > > 'python setup.py build' makes it right, then it is 'corrupted' by > Debian configuration/ecosytem/environment! > > Sure, there is some temp solutions[1]. > Into setup.py, is there any proper way for handling self.install_data > with debian layout? We can modify the distutils scripts to make things easier. I tested the basic functionality and John Ralls tested the Mac installation. There was no input from anyone else. What is the problem using the --root or --prefix options? What is the problem with the resource path? We must keep the GRAMPS_RESOURCES environment variable for the Mac installation, but we can make other changes. I thought that Debian would use the resource-path file. The alternatives would be to use GRAMPS_RESOURCES, or get the startup script to look in common locations. Let me know the requirements and I'll help make the necessary changes. Nick. |
From: Jerome <rom...@ya...> - 2014-01-31 17:27:54
|
My bad, by 'corrupted' we should rather read 'own cooking' during package generation... > "The deb problem on SolydXK is Gramps 3.4.7" Is it a dependency problem or something else? Does command line, like: sudo dpkg -i gramps-3.4.7*.deb failed? > "What is the problem using the --root or --prefix options?" In fact, everything works as expected ... The problem is the content of resource path with debian layout! Without modification, during .deb generation, we get something like: os.path.join(root, install_data, 'share'), where root is a path with write access (eg, ./debian/gramps). So, I cannot generate a .deb with resource path pointing to: '/home/.../Gramps/debian/gramps/...'; and I need to force '/usr/share' into setup.py. :( I looked at python setup.py --install-help, then tested many configurations without success. Right now, the command line looks like: override_dh_auto_install: $ python setup.py install --root=debian/gramps --install-layout=deb http://sourceforge.net/p/gramps/source/ci/maintenance/gramps40/~/tree/debian/rules $ python setup.py build $ python setup.py install is OK, only above specific command line needs a customization. John, How do you set install_data for setup.py into your building process? Nick, Maybe we could also try to include a Debian/Mac/Win section into setup.py? Jérôme. Le ven. 31 janv. 2014 at 14:57,Enno Borgsteede <enn...@gm...> a écrit : > Jerome, Nick, >> 'python setup.py build' makes it right, then it is 'corrupted' by >> Debian configuration/ecosytem/environment! >> > The deb problem on SolydXK is Gramps 3.4.7, so it can't be a python > build. 4.0.3 deb is OK. > > https://www.gramps-project.org/wiki/index.php?title=Debian#For_version_3.4_and_before >> >> > We can modify the distutils scripts to make things easier. I tested > the basic functionality and John Ralls tested the Mac installation. > There was no input from anyone else. > > What is the problem using the --root or --prefix options? > > What is the problem with the resource path? > > We must keep the GRAMPS_RESOURCES environment variable for the Mac > installation, but we can make other changes. I thought that Debian > would use the resource-path file. The alternatives would be to use > GRAMPS_RESOURCES, or get the startup script to look in common > locations. > > Let me know the requirements and I'll help make the necessary changes. > > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply > import > a virtual appliance and go from zero to informed in seconds. > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Jerome <rom...@ya...> - 2014-01-31 18:32:12
|
OK, I made a version 3 for '3.4.7.*.deb" package! Set of dependencies is now minimal. User might see warnings at first startup (gramps) about missing dependencies: python-osmgpsmap, python-pyexiv2), but packages manager will no more complain. Version 3 also includes updated german translation and a minor fix from git. Le ven. 31 janv. 2014 at 19:14,Enno Borgsteede <enn...@gm...> a écrit : > Jerome, >> > "The deb problem on SolydXK is Gramps 3.4.7" >> >> Is it a dependency problem or something else? >> >> Does command line, like: >> >> sudo dpkg -i gramps-3.4.7*.deb >> >> failed? >> > Yes. > > dpkg: dependency problems prevent configuration of gramps: > gramps is afhankelijk van python-osmgpsmap; maar: > Pakket `python-osmgpsmap' is niet geïnstalleerd. > > When I start synaptic, there is no python-osmgpsmap available for > install, so I guess that the package manager simply quits because it > doesn't know what to do. Since it doesn't quit on Linux Mint, I guess > that on that, python-osmgpsmap is available. I'll check that in a > minute, and add that info to Mantis. > > regards, > > Enno > |
From: Jerome <rom...@ya...> - 2014-01-31 19:31:43
|
If need, I added a missing 'gramps-autogen.sh' reference, for next tarballs (3.4.x)... Enno, I see '3.4.7-3' in the about box! I guess you are testing something like: $ /usr/local/bin/gramps -v # your compilation After installing the package, it should be rather: $ /usr/bin/gramps -v GDebi/Synaptic/Aptitude are just GUI front-end(s)[1] related to linux distributions or desktops! apt, dpkg[2] are more oriented .deb, in general! Note, something else around package management. Gramps 4 has an AppData support with screenshots[3]. I do not know the future of this specification[4], but if you wonder where these screenshots come from, they are stored on wiki! So, gramps-project has a control on them and could update them. Maybe just try to keep the same size and resolution? [1] https://en.wikipedia.org/wiki/Advanced_Packaging_Tool#Front-ends [2] https://wiki.debian.org/Teams/Dpkg [3] https://www.gramps-project.org/wiki/index.php?title=Category:AppData [4] http://www.freedesktop.org/software/appstream/docs/sect-AppStream-Metadata-AppData.html Jérôme Le ven. 31 janv. 2014 at 19:41,Enno Borgsteede <enn...@gm...> a écrit : > Hi Jerome, >> OK, I made a version 3 for '3.4.7.*.deb" package! >> > Thanks, that works. It still says 3.4.7-1 in the about box though, > but that's a very minor issue. > > Note: After trying the dpkg -i that you advised, GDebi complained > that there was a broken package that I had to remove with synaptic > first. That didn't happen when I tried earlier packages with GDebi. > > From that, I conclude that dpkg can be a dangerous command, because > it leaves traces that need to be cleaned. GDebi blocks install > without a trace, so I prefer that we advise that on the wiki instead. > > Installation on Linux Mint is ok, because on that synaptic knows > where to find python-osmgpsmap. Consequence is that when you build a > deb on Ubuntu, you get no complaints about that dependency. > > regards, > > Enno > |
From: Enno B. <enn...@gm...> - 2014-01-31 23:57:00
|
Jerome, > I see '3.4.7-3' in the about box! > I guess you are testing something like: > > $ /usr/local/bin/gramps -v # your compilation > > After installing the package, it should be rather: > > $ /usr/bin/gramps -v You're right. I keep forgetting that Linux menu's are not like Windows and just activate the 1st gramps in my path. Version is OK. regards, Enno |
From: Enno B. <enn...@gm...> - 2014-02-01 01:00:39
|
Jerome, > GDebi/Synaptic/Aptitude are just GUI front-end(s)[1] related to linux > distributions or desktops! > > apt, dpkg[2] are more oriented .deb, in general! Ok, but what I saw was that dpkg started install, discovered that the dependency was not met, and then left a mess on my system. GDebi checked dependencies before install, and didn't leave anything behind. And for users, I think that makes quite a difference. cheers, Enno |
From: Nick H. <nic...@ho...> - 2014-01-30 20:56:56
|
On 30/01/14 19:49, Enno Borgsteede wrote: >> With any tarball, you often just need: >> > >> >$ make >> >$ make install # with admin rights > Not here. I was used to configure and make (install) when building GNU > packages in my job, but this time it's about getting Gramps 3.4.7 for > users without git, just SF. > > We have a situation where the 3.4.7 deb does not work on debian > (SolydXK), and instructions in INSTALL don't work either, so I'm trying > to figure out the simplest way to get 3.4.7 running there, and put that > on the wiki, without scaring users too much. > > Anyone else have an opinion about this? It looks like we should include gramps-autogen.sh in the tar. We could also review the debian dependencies. Nick. |
From: Enno B. <enn...@gm...> - 2014-01-31 13:57:22
|
Jerome, Nick, > 'python setup.py build' makes it right, then it is 'corrupted' by > Debian configuration/ecosytem/environment! The deb problem on SolydXK is Gramps 3.4.7, so it can't be a python build. 4.0.3 deb is OK. https://www.gramps-project.org/wiki/index.php?title=Debian#For_version_3.4_and_before > > include gramps-autogen.sh in the tar > > Not certain this will help, but we can include it into configure.in. > > http://sourceforge.net/p/gramps/source/ci/maintenance/gramps34/~/tree/configure.in I haven't tried a build from tar since long, so I have no idea if it was there in earlier tars. Anyway, it certainly helps to tell users to use configure for this particular tar. That's just a few lines on the wiki, right? regards, Enno |
From: Enno B. <enn...@gm...> - 2014-01-31 18:14:57
|
Jerome, > > "The deb problem on SolydXK is Gramps 3.4.7" > > Is it a dependency problem or something else? > > Does command line, like: > > sudo dpkg -i gramps-3.4.7*.deb > > failed? Yes. dpkg: dependency problems prevent configuration of gramps: gramps is afhankelijk van python-osmgpsmap; maar: Pakket `python-osmgpsmap' is niet geïnstalleerd. When I start synaptic, there is no python-osmgpsmap available for install, so I guess that the package manager simply quits because it doesn't know what to do. Since it doesn't quit on Linux Mint, I guess that on that, python-osmgpsmap is available. I'll check that in a minute, and add that info to Mantis. regards, Enno |
From: Enno B. <enn...@gm...> - 2014-01-31 18:41:45
|
Hi Jerome, > OK, I made a version 3 for '3.4.7.*.deb" package! Thanks, that works. It still says 3.4.7-1 in the about box though, but that's a very minor issue. Note: After trying the dpkg -i that you advised, GDebi complained that there was a broken package that I had to remove with synaptic first. That didn't happen when I tried earlier packages with GDebi. From that, I conclude that dpkg can be a dangerous command, because it leaves traces that need to be cleaned. GDebi blocks install without a trace, so I prefer that we advise that on the wiki instead. Installation on Linux Mint is ok, because on that synaptic knows where to find python-osmgpsmap. Consequence is that when you build a deb on Ubuntu, you get no complaints about that dependency. regards, Enno |