Two entry points:
a)
$ pull-lp-source qemu focal; cd qemu-4.2
b)
$ git ubuntu clone qemu; cd qemu; git checkout pkg/ubuntu/focal-proposed; dquilt push -a --fuzz=0
And the very same but for groovy.
Running a local build like ./debian/rules build and checking the behavior of submodules.
pull:
Source path /tmp/qemu-4.2
GIT binary git
GIT submodules
C compiler cc
...
sh /tmp/qemu-4.2/scripts/create_config < config-host.mak > config-host.h-timestamp
(GIT="git" "/tmp/qemu-4.2/scripts/git-submodule.sh" ignore )
Cross verify, without the patch it fails with the new d/rules:
ERROR: unknown option --with-git-submodules=ignore
Try '../../configure --help' for more information
Things are in place as planned and the PKG build in launchpad and such still works fine.
Maybe my testcase is moot :-/
@DDstreet I still see the submodules listed in the configure output, since it is your upstream change and your initial testcase could you have a look at this for SRU verification?
Two entry points: focal-proposed; dquilt push -a --fuzz=0
a)
$ pull-lp-source qemu focal; cd qemu-4.2
b)
$ git ubuntu clone qemu; cd qemu; git checkout pkg/ubuntu/
And the very same but for groovy.
Running a local build like ./debian/rules build and checking the behavior of submodules.
pull: 4.2/scripts/ create_ config < config-host.mak > config- host.h- timestamp 4.2/scripts/ git-submodule. sh" ignore )
Source path /tmp/qemu-4.2
GIT binary git
GIT submodules
C compiler cc
...
sh /tmp/qemu-
(GIT="git" "/tmp/qemu-
git: ldflags= "-Wl,-Bsymbolic -functions -Wl,-z,relro -Wl,--as-needed" --prefix=/usr --sysconfdir=/etc --libdir= /usr/lib/ x86_64- linux-gnu --libexecdir= /usr/lib/ qemu --firmwarepath= /usr/share/ qemu:/usr/ share/seabios: /usr/lib/ ipxe/qemu --localstatedir =/var --disable-blobs --disable-strip --interp- prefix= /etc/qemu- binfmt/ %M --localstatedir =/var --with- git-submodules= ignore \ berkeley- testfloat- 3 tests/fp/ berkeley- softfloat- 3
...
_FORTIFY_SOURCE=2" --extra-
...
GIT binary git
GIT submodules ui/keycodemapdb tests/fp/
Cross verify, without the patch it fails with the new d/rules: git-submodules= ignore
ERROR: unknown option --with-
Try '../../configure --help' for more information
Things are in place as planned and the PKG build in launchpad and such still works fine.
Maybe my testcase is moot :-/
@DDstreet I still see the submodules listed in the configure output, since it is your upstream change and your initial testcase could you have a look at this for SRU verification?