Where custom ebuilds stores git source files?

orion777

I have a custom ebuild https://forums.gentoo.org/viewtopic-t-1080522.html?sid=ae1bd9016062c908d52fe074d2663166. It uses git to download sources and python 2.7 to compile them. Now I wish to delete this package and its sources to force emerge to take new version from the github repository. (version on the github was not changed, but some minor modifications has been done there and I need these modifications in my installation)

fedeliallalinea · Posted: Mon Sep 03, 2018 5:30 pm Post subject:

In /usr/portage/distfiles/git3-src/<repository>_<package-name>.git
_________________
Questions are guaranteed in life; Answers aren't.

orion777 · Posted: Mon Sep 03, 2018 5:52 pm Post subject:

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

I think you are trying to solve the wrong problem. Deleting the local sources is not the right solution. If the upstream project has not changed, then redownloading will do nothing. If upstream has changed, then you want to sync to the commit with those changes. You say both that the version on github was not changed and that some modifications are present, but these are contradictory. If upstream has modified the code, then the version available from github has changed. Do you mean that upstream has committed fixes, but not tagged a release? If so, then you need to pull the latest commit. The git eclass should handle this automatically if your ebuild does not pin to a specific commit. Please show the full output of a clean install of your live ebuild. If the ebuild in the linked thread no longer represents the ebuild you are using, then please post your current version.

orion777 · Posted: Wed Sep 05, 2018 6:00 pm Post subject:

The github page is here https://github.com/ArduPilot/MAVProxy and it is possibe to find that the folder of MAVProxy has been last edited 5 of September. I hope (but note sure) that these modifications contains problem, that was (probably) resolved https://discuss.ardupilot.org/t/mavproxy-master-to-wait-for-incoming-connections/32533/2

I was deleted files from my previous installation from /usr/portage/distfiles/git3-src/ , so now I can't compare them. However, emerge is still able to install the MAVProxy whereas /usr/portage/distfiles/git3-src/ remains empty, so somewhere these sources are still available in my system

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

Unless inhibited, a live ebuild should automatically sync to the latest changes in the target branch before it begins to build. That ebuild does not appear to inhibit the update check.

app-text/wgetpaste is a popular way of uploading full build logs. Please use emerge to install your live ebuild, then pastebin the resulting build log.

orion777 · Posted: Fri Sep 07, 2018 6:57 am Post subject:

Good day!

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

As I said, that ebuild looks like it will sync on every run. The log you showed is produced by Portage, but looks to me like it is not a build log. I think you are reinstalling a previously built binary package. If you want the new code, you must actually build the package, not just reinstall an archive of the older version. What is the output of emerge --pretend --verbose mavproxy ; emerge --info?

orion777 · Posted: Sat Sep 08, 2018 7:55 am Post subject:

I use Sakaki's Raspberry PI3B (rpi3) 64 bit image https://forums.gentoo.org/viewtopic-p-8257016.html#8257016 This image, to save compile time on the embedded rpi3 system check for the prepared binary first https://github.com/sakaki-/gentoo-on-rpi3-64bit#have-your-gentoo-pc-do-the-heavy-lifting But due to I'm using custom ebuild of the mavproxy, there is no prepared binary for the mavproxy on the binhost remote server, so I was not mentioned about this

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

orion777 · Posted: Sun Sep 09, 2018 8:25 am Post subject:

So, finally:
the command emerge -cav ros-meta/mavproxy deletes /usr/portage/packages/ros-meta/mavproxy-9999.tbz2 as well both /usr/lib64/python2.7/site-packages/MAVProxy/ and /usr/lib64/python2.7/site-packages/MAVProxy-1.6.4-py2.7.egg-info/ . Further, MC is unable to find anything with the mavproxy* (with NO case sensitive option). However, during further installation emerge still uses binary, instead of sources [binary R *] , the internet connection remains in idle and /usr/portage/distfiles/git3-src/ remains empty (its content has been deleted to perform the experiment).

Now, if to comment strings FEATURES="${FEATURES} buildpkg" and FEATURES="${FEATURES} getbinpkg" in the make.conf, then during the installation it has been activating the internet access, git-3-src now contains sources and emerge looks like [ebuild instead of binary].

So Yes, the problem is solved! However, I still unable to understand where these binary are stored in if above mentioned options in the make.conf are not commented.

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

emerge -c should not delete the prebuilt tbz2. You must delete that by hand or through a supporting tool, such as eclean.

orion777 · Posted: Fri Sep 14, 2018 6:30 am Post subject:

Good morning. How to use sources in the git folder?
The custom ebuild was downloaded sources from the github.
Now I have to manually fix this code issue https://github.com/ArduPilot/MAVProxy/pull/544/commits/71dab4fb4f2c382ac97a0a4ff2172c4023fcfc8a
However, I can't find original structure of the github sources https://github.com/ArduPilot/MAVProxy

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

Use a local user patch, as you would for any other package which needs a post-release fix.

orion777 · Posted: Thu Sep 20, 2018 8:26 am Post subject:

As I understood, I have to make local patch and emerge will apply it every time when i will emerge the mavproxy.
1) So, there are no other possibilities to apply commits https://github.com/ArduPilot/MAVProxy/pull/544/commits/71dab4fb4f2c382ac97a0a4ff2172c4023fcfc8a or manual changes instead of making local patch, right?
2) As was mentioned, the developers makes some minor modifications without changing version of the mavproxy. This means that when additional changes in the mavproxy.py will be made by someone, then my patch starts to fail during reinstall, right?
Thank You.

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

Local patches are the standard solution if you want to include a change that is not part of the upstream sources you are building. If upstream has already fixed the issue, and done so in the branch you intend to build, you can sync to their change and not use a local patch.

Yes, if they write a conflicting change, your patch will break. This is always a risk when patching a live ebuild.