The problem is with this line: https://github.com/jeandet/vera/blob/master/vera.spec#L26, where you specify -n vera-master for %autosetup. That's how directory is called in https://github.com/jeandet/vera/archive/master.tar.gz. But in dist-git the directory in the tarball is called vera++-1.3 (name of the package + version). If the command was %autosetup -q, it would work. Are you able to change the name of the directory in the archive at https://github.com/jeandet/vera/archive/master.tar.gz?
climeOn Wed, May 31, 2017 at 11:59 AM, Michal Novotny <firstname.lastname@example.org> wrote:Hello, I am just deploying a new version of copr-dist-git that should fix that particular problem so you can try that. There seems to be a problem later on in building phase but we need to solve it afterwards. climeOn Wed, May 31, 2017 at 12:54 AM, Jeandet Alexis <email@example.com
>wrote:______________________________Hi,I try to build a package from gtihub, it seems that git repo name must be the same that package name in spec file?Looking this build:Looking the log here:I tried on my desktop, I had to replace the following options:package=vera by package=vera++andgit_get=git clone --depth 1 https://github.com/jeandet/ver a.gitvera by git_get=git clone --depth 1 https://github.com/jeandet/ver a.gitvera++Did I miss something? On github, it seems that I can't call my repo vera++, how can I override previous options?Best regards,Alexis. _________________
copr-devel mailing list -- firstname.lastname@example.org.
To unsubscribe send an email to email@example.com
_______________________________________________ copr-devel mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com