Closed alxroyer closed 5 years ago
I think this is an issue in dpkg-source
. Also note that to build from git you need to run (Edit: ./configure
first because it auto-generates the changelog../tools/tarsource.sh -V
does that for you, sorry, I missed that.)
Closing since this is very likely a Debian tooling bug, not a FRR bug.
Describe the bug When frr.git is used as a submodule, the debian packaging procedure fails.
(put "x" in "[ ]" if you already tried following) [x] Did you check if this is a duplicate issue? [x] Did you test it on the latest FRRouting/frr master branch?
To Reproduce Steps to reproduce the behavior:
doc/developer/packaging-debian.rst
, steps 4 & 6 (assuming all tools have already been installed):Backtrace Below the output of the
dpkg-buildpackage
command:Versions
First analysis When frr.git is cloned directly,
frr/.git
is a directory which contains all git information. When frr.git is cloned as a submodule,frr.git/.git
is a text file which contentgitdir: ../.git/modules/frr
tells where the actual gitdir is stored. I cannot say whether the failure comes from frr.git scripts, or thedpkg-source
command, or the use ofdpkg-source
by the frr.git scripts.