[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Hm, they are the same ones I use to successfully build the CM13.0 version? I found the likely source of my repo sync problems (and to some extent the build problems), but haven't been able to solve it.

It seems that upon running brunch lt03wifi the build script doesn't recognise the lt03wifi device tree for some reason and creates a roomservice.xml in local_manifests with at least some wrong lines with a double reference to CyanogenMod/CyanogenMod/... see below:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Joshndroid/android_device_samsung_lt03wifi" path="device/samsung/lt03wifi" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/ShevT/kernel_samsung_lt033g" path="kernel/samsung/lt033g" remote="github" />
<project name="CyanogenMod/ShevT/vendor_samsung_lt033g" path="vendor/samsung/lt033g" remote="github" />
<project name="CyanogenMod/CyanogenMod/hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/CyanogenMod/hardware_samsung_slsi_exynos" path="hardware/samsung_slsi/exynos" remote="github" />
<project name="CyanogenMod/CyanogenMod/hardware_samsung_slsi-exynos5-insignal" path="hardware/samsung_slsi/exynos5-insignal" remote="github" />
<project name="CyanogenMod/CyanogenMod/hardware_samsung_slsi_exynos5420" path="hardware/samsung_slsi/exynos5420" remote="github" />
<project name="CyanogenMod/CyanogenMod/hardware_samsung_slsi_openmax" path="hardware/samsung_slsi/openmax" remote="github" />
<project name="CyanogenMod/CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
</manifest>

This is also expressed in the output of brunch lt03wifi given below. What I don't understand is why it's looking for lt033g in the first place, and why it doesn't find seem to find/recognise the lt03wifi device tree (which is however defined in my local manifest)?? The rest of the errors seem to stem from that, as it makes the device pull in the various hardware/samsung repos that are actually already defined in my local manifest (and afterwards cause a break due to being defined twice). When I get a chance, I'll try fiddling around more, but hints as to what may be causing this to behave different from the CM13.0 version would be great, as I'd like to understand what's happening (and ideally be able to fix it).

build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/lt03wifi/cm.mk]]: "device/samsung/lt033g/full_lt033g.mk" does not exist. Stop.
Device lt03wifi not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_lt03wifi
Default revision: cm-12.1
Checking branch info
CyanogenMod/android_device_samsung_lt03wifi already exists
Syncing repository to retrieve project.
Fetching project Joshndroid/android_device_samsung_lt03wifi
Fetching projects: 100% (1/1), done.

Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/ShevT/kernel_samsung_lt033g -> kernel/samsung/lt033g
Using default branch for ShevT/kernel_samsung_lt033g
Adding dependency: CyanogenMod/ShevT/vendor_samsung_lt033g -> vendor/samsung/lt033g
Using default branch for ShevT/vendor_samsung_lt033g
Adding dependency: CyanogenMod/CyanogenMod/hardware_samsung -> hardware/samsung
Using default branch for CyanogenMod/hardware_samsung
Adding dependency: CyanogenMod/CyanogenMod/hardware_samsung_slsi_exynos -> hardware/samsung_slsi/exynos
Using default branch for CyanogenMod/hardware_samsung_slsi_exynos
Adding dependency: CyanogenMod/CyanogenMod/hardware_samsung_slsi-exynos5-insignal -> hardware/samsung_slsi/exynos5-insignal
Using default branch for CyanogenMod/hardware_samsung_slsi-exynos5-insignal
Adding dependency: CyanogenMod/CyanogenMod/hardware_samsung_slsi_exynos5420 -> hardware/samsung_slsi/exynos5420
Using default branch for CyanogenMod/hardware_samsung_slsi_exynos5420
Adding dependency: CyanogenMod/CyanogenMod/hardware_samsung_slsi_openmax -> hardware/samsung_slsi/openmax
Using default branch for CyanogenMod/hardware_samsung_slsi_openmax
Adding dependency: CyanogenMod/CyanogenMod/android_packages_apps_SamsungServiceMode -> packages/apps/SamsungServiceMode
Using default branch for CyanogenMod/android_packages_apps_SamsungServiceMode
Syncing dependencies
fatal: duplicate path hardware/samsung in /media/georg/fastschloider/dev/temasek-cm12.1/.repo/manifest.xml
Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Looking for dependencies
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/lt03wifi/cm.mk]]: "device/samsung/lt033g/full_lt033g.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_lt03wifi'
** Do you have the right repo manifest?

PS: If I comment out the lt033g related lines and the hardware/samsung line in the newly created roomservice.xml repo sync starts and goes up to 99%, but then hangs eternally trying to fetch slsi_exynos and exnos5-insignal (I had left it running for a couple of hours, it only provides the error messages after manually aborting):

Fetching projects: 99% (561/566) Fetching project CyanogenMod/android_hardware_qcom_display
^Cerror: Cannot fetch CyanogenMod/hardware_samsung_slsi_exynos
error: Cannot fetch CyanogenMod/hardware_samsung_slsi-exynos5-insignal
error: Cannot fetch CyanogenMod/hardware_samsung_slsi_openmaxaborted by user

If I comment out the offending lines in roomservice.xml, considering that my local manifest actually has these files I get the same error at brunch as described in the beginning. My manifest has the hardware/samsung repos as cm_ variants, I suspect that makes a difference. I tried looking for the offending repos online, and it seems that at least for some of them only a cm_ variant is available, so e.g. CyanogenMod/hardware_samsung_slsi-cm_openmax.

I tried adapting my local manifest as below, which allows me to run repo sync, but at brunch I still get the problem described at the beginning that the device tree for lt03wifi seems to be not found.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Joshndroid/android_device_samsung_lt03wifi" path="device/samsung/lt03wifi" remote="github" revision="cm-12.1" />
<project name="Joshndroid/android_kernel_samsung_lt03wifi" path="kernel/samsung/lt03wifi" remote="github" revision="cm-12.1" />
<project name="Joshndroid/android_vendor_samsung_lt03wifi" path="vendor/samsung/lt03wifi" remote="github" revision="cm-12.1" />

<project name="CyanogenMod/android_kernel_samsung_exynos5420" path="kernel/samsung/exynos5420" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi/exynos" remote="github" revision="cm-12.1" />
<!-- <project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5-insignal" path="hardware/samsung_slsi/exynos5-insignal" remote="github" revision="cm-12.1" />
--> <project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi/exynos5420" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi/openmax" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="package/apps/SamsungServiceMode" remote="github" revision="cm-12.1" />

</manifest>