Makefile: run 'bitbake package-index' after bitbake command building packages

It was recently spotted that during a build of 201705-testing where
sysmocom-openvpn-config was being rebuilt, the Packages(.gz) files
(opkg package indexes) were rebuilt before the new .ipk files for
sysmocom-openvpn-config were written to disk. Also then the Packages
file didn't contain a reference to the new sysmocom-openvpn-config
package version. So, it seems there was a race condition where the
package index was built too early.

Yocto documentation provides some hints:
https://docs.yoctoproject.org/dev-manual/packages.html?highlight=bitbake+package+index#build-considerations
"""
Whenever you perform any sort of build step that can potentially generate
a package or modify existing package, it is always a good idea to
re-generate the package index after the build by using the following
command: bitbake package-index
Do not do "$ bitbake some-package package-index" as BitBake does not schedule
the package index for after the completion of the package you are building.
Consequently, you cannot be sure of the package index including
information for the package you just built. Thus, be sure to run the
package update step separately after building any packages.
"""

So far it seems we were relying on the "create filesystem" task
triggered for image creation which would also trigger the package index
recreation, according to
https://yocto.yoctoproject.narkive.com/rjvLrVpW/question-about-rebuilding-rpm-package-index-for-updated-rpms-when-bitbake-completes
"""
The feed is normally indexed (createrepo) either when you manually run the
package-index operation, or when you construct a filesystem. Until you do that,
the feed directories are transient.
"""

Related: SYS#6023

Makefile

@@ -25,11 +25,11 @@ endif
 SYSMOCOM_RELEASE=201705
 POKY_RELEASE=pyro
 REPOS=poky meta-telephony meta-qt5 meta-sysmocom-bsp meta-smalltalk
-MACHINES=sysmobts sysmobts2100 sysmocom-apu2 sysmocom-alix
+MACHINES=sysmobts sysmobts2100 sysmocom-apu2 sysmocom-alix oc2g
 FEED_NAME=$(SYSMOCOM_RELEASE)-testing
 
 # The default targets to pick depending on machine
-BUILD_TARGET_sysmobts = meta-toolchain-osmo task-sysmocom-feed sysmocom-core-image sysmocom-nitb-image sysmocom-core-rauc-image sysmocom-nitb-rauc-image image-rauc-rescue-initramfs image-rauc-slot-initramfs image-rauc-ubi
+BUILD_TARGET_sysmobts = meta-toolchain-osmo task-sysmocom-feed sysmocom-core-image sysmocom-nitb-image sysmocom-voice-sip-image sysmocom-core-rauc-image sysmocom-nitb-rauc-image image-rauc-rescue-initramfs image-rauc-slot-initramfs image-rauc-ubi
 BUILD_TARGET_sysmobts2100 = meta-toolchain-osmo task-sysmocom-feed sysmocom-core-image sysmocom-nitb-image
 BUILD_TARGET_oc2g = meta-toolchain-osmo task-sysmocom-feed sysmocom-core-image sysmocom-nitb-image
 BUILD_TARGET_sysmocom-apu2 = core-image-minimal-initramfs meta-toolchain-osmo task-sysmocom-feed sysmocom-core-image sysmocom-nitb-image core-image-minimal-initramfs
@@ -93,15 +93,15 @@ git:
 
 ## Clone repositories. The other option is by variable something like BRNACH_poky, REPO_poky
 git/poky: | git
-	$(V)cd git && git clone --branch=$(GIT_BRANCH_POKY) --depth=1 git://git.yoctoproject.org/poky
+	$(V)cd git && git clone --branch=$(GIT_BRANCH_POKY) --depth=1 https://gitea.sysmocom.de/sysmo-bts/generic-poky poky
 git/meta-sysmocom-bsp: | git
-	cd git && git clone --branch=$(GIT_BRANCH_SYSMOCOM_BSP) git://git.sysmocom.de/poky/meta-sysmocom-bsp
+	cd git && git clone --branch=$(GIT_BRANCH_SYSMOCOM_BSP) https://gitea.sysmocom.de/sysmo-bts/meta-sysmocom-bsp
 git/meta-telephony: | git
-	cd git && git clone --branch=$(GIT_BRANCH_TELEPHONY) git://git.osmocom.org/meta-telephony
+	cd git && git clone --branch=$(GIT_BRANCH_TELEPHONY) https://gerrit.osmocom.org/meta-telephony
 git/meta-smalltalk: | git
-	cd git && git clone --branch=$(GIT_BRANCH_SMALLTALK) git://github.com/sysmocom/meta-smalltalk
+	cd git && git clone --branch=$(GIT_BRANCH_SMALLTALK) https://github.com/sysmocom/meta-smalltalk
 git/meta-qt5: | git
-	cd git && git clone --branch=$(GIT_BRANCH_QT5) git://github.com/sysmocom/meta-qt5
+	cd git && git clone --branch=$(GIT_BRANCH_QT5) https://github.com/sysmocom/meta-qt5
 
 ## Create a build directory, e.g. build.sysmobts
 ## Use Poky to set-up the directory and then customize it. Copy files
@@ -131,7 +131,7 @@ build.%: | git/poky
 
 # Start a build..
 %-build: | build.$(subst -build,,%) git/poky
-	$(Q)/bin/bash -c "source git/poky/oe-init-build-env build.$(CUR_MACHINE) && bitbake $(BUILD_TARGETS)"
+	$(Q)/bin/bash -c "source git/poky/oe-init-build-env build.$(CUR_MACHINE) && bitbake $(BUILD_TARGETS) && bitbake package-index"
 
 %-upload: | build.$(subst -upload,,%) git/poky
 	$(Q)cd build.$(CUR_MACHINE) && ../scripts/upload-build.sh $(CUR_MACHINE) $(FEED_NAME)

cfg/oc2g/01_oc2g

@@ -6,3 +6,5 @@ PACKAGE_FEED_URIS = "https://autoupdate:eechiesuboot@downloads.sysmocom.de/gener
 # HW doesn't have rtc
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
 
+# Disable DAHDI support in libosmo-abis:
+PACKAGECONFIG_remove_pn-libosmo-abis = "dahdi"

cfg/sysmobts/01_sysmobts

@@ -9,3 +9,6 @@ MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
 # Ignore old kernels
 BBMASK="recipes-bsp/linux/linux_2.6.39.bb recipes-bsp/linux/linux-sysmocom_3.10.bb"
 PREFERRED_VERSION_linux-sysmocom = "4.9.14+git%"
+
+# Disable DAHDI support in libosmo-abis:
+PACKAGECONFIG_remove_pn-libosmo-abis = "dahdi"

cfg/sysmobts2100/01_sysmobts2100

@@ -6,3 +6,5 @@ PACKAGE_FEED_URIS = "https://autoupdate:eechiesuboot@feeds.sysmocom.de/generic/s
 # HW doesn't have rtc
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
 
+# Disable DAHDI support in libosmo-abis:
+PACKAGECONFIG_remove_pn-libosmo-abis = "dahdi"