I've got my repo synced to the pac-4.4 branch, but now that the team has switched repos to Pinky Inky and Clyde, my repo syncs have been failing. Can somebody help walk me through the steps to set everything back up using the new repo?
numel007 said:
I've got my repo synced to the pac-4.4 branch, but now that the team has switched repos to Pinky Inky and Clyde, my repo syncs have been failing. Can somebody help walk me through the steps to set everything back up using the new repo?
Click to expand...
Click to collapse
What device are you trying to build for, what is the error you're getting, what is the contents of your roomservice file?
Sent from my Xperia Ray using Tapatalk
Langes said:
What device are you trying to build for, what is the error you're getting, what is the contents of your roomservice file?
Sent from my Xperia Ray using Tapatalk
Click to expand...
Click to collapse
I will be building for the HTC LTE aka Jewel
Fatal error message was: Fetching projects: 80% (355/443) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Full log can be found here: http://pastebin.com/G9UbGBuG
Roomservice.xml inside .repo/local_manifests is:
<manifest><project name="CyanogenMod/android_device_htc_jewel" path="device/htc/jewel" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-11.0"/><project name="Pinky-Inky-and-Clyde/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0"/></manifest>
Click to expand...
Click to collapse
numel007 said:
I will be building for the HTC LTE aka Jewel
Fatal error message was: Fetching projects: 80% (355/443) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Full log can be found here: http://pastebin.com/G9UbGBuG
Roomservice.xml inside .repo/local_manifests is:
Click to expand...
Click to collapse
roomservice is 100%
Delete the default.xml file in .repo folder and do the init repo command again. This should fix you up as the pacman folder was renamed and your repo did not update that somehow.
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
Langes said:
roomservice is 100%
Delete the default.xml file in .repo folder and do the init repo command again. This should fix you up as the pacman folder was renamed and your repo did not update that somehow.
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
Click to expand...
Click to collapse
Deleting the file and rerunning the command causes an immediate fatal error since the default.xml file can not be found. Should I restore it and just delete everything inside the file?
[email protected]:~/PacRom-4.4$ repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
[email protected]:~/PacRom-4.4$
Click to expand...
Click to collapse
numel007 said:
Deleting the file and rerunning the command causes an immediate fatal error since the default.xml file can not be found. Should I restore it and just delete everything inside the file?
Click to expand...
Click to collapse
My bad, you should delete manifest.xml inside the ~/PacRom-4.4/.repo folder and init again.
Langes said:
My bad, you should delete manifest.xml inside the ~/PacRom-4.4/.repo folder and init again.
Click to expand...
Click to collapse
File deleted, terminal restarted. Initiated repo again, ran repo sync, same failure as before unfortunately. Looks like somehow my repo isn't updating even after manifest.xml was deleted.
numel007 said:
File deleted, terminal restarted. Initiated repo again, ran repo sync, same failure as before unfortunately. Looks like somehow my repo isn't updating even after manifest.xml was deleted.
Click to expand...
Click to collapse
Do you have any other xml files in .repo and in .repo/local_manifests? If you do, delete them all.
Do you have an android or a pacman folder in the top folder of you source tree? Or both?
Langes said:
Do you have any other xml files in .repo and in .repo/local_manifests? If you do, delete them all.
Do you have an android or a pacman folder in the top folder of you source tree? Or both?
Click to expand...
Click to collapse
Any and all xmls? And yes I have an Android folder in root of files.
Edit: Did a search for all xml files and deleted roomservice and manifest. Had to keep default to make the repo init still run. Repo sync ended with one error less. Still can not retrieve from pac. I also deleted the default.xml in the android folder.
Fetching project platform/external/lzma
Fetching projects: 99% (434/438) fatal: Not a git repository: '/home/derek/PacRom-4.4/.repo/projects/pacman.git'
error: Cannot fetch pacman
error: Exited sync due to fetch errors
numel007 said:
Any and all xmls? And yes I have an Android folder in root of files.
Edit: Did a search for all xml files and deleted roomservice and manifest. Had to keep default to make the repo init still run. Repo sync ended with one error less. Still can not retrieve from pac. I also deleted the default.xml in the android folder.
Fetching projects: 99% (434/438) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Click to expand...
Click to collapse
ok, delete all folders and files in your source folder except .repo (the source code you have downloaded is in .repo so you will not have to re-download everything)
then run the init command again and sync again
Langes said:
ok, delete all folders and files in your source folder except .repo (the source code you have downloaded is in .repo so you will not have to re-download everything)
then run the init command again and sync again
Click to expand...
Click to collapse
Deleted everything but .repo and ran init again. Repo sync still can't fetch from pac. Maybe I should just do a fresh start and reset the entire build envirnment.
numel007 said:
Deleted everything but .repo and ran init again. Repo sync still can't fetch from pac. Maybe I should just do a fresh start and reset the entire build envirnment.
Click to expand...
Click to collapse
Compare the contents of manifests.xml inside the .repo folder to this: https://github.com/PAC-man/pacman/blob/pac-4.4/default.xml
Line 499 should read:
Code:
<project path="pacman" name="pacman" remote="pac" revision="pac-4.4" />
Langes said:
Compare the contents of manifests.xml inside the .repo folder to this: https://github.com/PAC-man/pacman/blob/pac-4.4/default.xml
Line 499 should read:
Code:
<project path="pacman" name="pacman" remote="pac" revision="pac-4.4" />
Click to expand...
Click to collapse
Yes line 499 read that. But to play it safe, I deleted the entire file and replaced it with a straight paste from that link you gave me. Repo init again, then repo sync, same failure. Out of ideas yet? lol
rm -rf .repo/projects/device/*
repo sync
arrrghhh said:
rm -rf .repo/projects/device/*
repo sync
Click to expand...
Click to collapse
Thank you. Unfortunately I already deleted my entire source code and redownloaded. Thankfully everything works now. Thanks for the input, both of you.
Sent from my EVO
Related
Hi,
I'm going to port Firefox OS to my I9082 but I have some problems after "./config.sh i9082".
It can't get some repositories from android.git.linaro.com and after that it stuck at "Fetching objects: 25% (20/78)" and after this, I waited for 8 hours!!!!! :crying:
after this, i closed the terminal.
I tried again using "repo sync" to continue but there is a new problem! It says that some of repos not found! for example i can't get "platform/external/freetype" and "platform/external/dbus" from linaro git.
Can anybody help me?
Delete broken projects and sync again
DataUnit said:
Hi,
I'm going to port Firefox OS to my I9082 but I have some problems after "./config.sh i9082".
It can't get some repositories from android.git.linaro.com and after that it stuck at "Fetching objects: 25% (20/78)" and after this, I waited for 8 hours!!!!! :crying:
after this, i closed the terminal.
I tried again using "repo sync" to continue but there is a new problem! It says that some of repos not found! for example i can't get "platform/external/freetype" and "platform/external/dbus" from linaro git.
Can anybody help me?
Click to expand...
Click to collapse
Delete all folder expect .repo and start over.
arky_r said:
Delete all folder expect .repo and start over.
Click to expand...
Click to collapse
I did this action 4 times and when I executed the command again, it will stop at another project! :crying:
DataUnit said:
I did this action 4 times and when I executed the command again, it will stop at another project! :crying:
Click to expand...
Click to collapse
Did you reading the repo tips at xda-universityDOTcom ?
Syncing a full new source tree in minutes!
Time might come when you’ll need to work with several full source trees. For example, you may want to have an AOKP source tree as well as a CM tree.
Obvisouly, you could repeat the same steps, to repo init and then repo sync -j 8 -c for both. But that would be twice as time consuming.
There is an alternative that should be much faster. Lets say that you have already initialized and synced a CM source tree, in ~/android/cm.
Now, we will prepare a new repo for AOKP tree, in ~/android/aokp. Here comes the trick: We will use the --reference flag of repo init to indicate to repo that we already have a local repository that it can take information from, instead of downloading everything from Internet again:
mkdir ~/android/aokp cd ~/android/aokp repo init --reference=~/android/cm -u git://github.com/AOKP/platform_manifest.git -b jb
1
2
3
mkdir ~/android/aokp
cd ~/android/aokp
repo init --reference=~/android/cm -u git://github.com/AOKP/platform_manifest.git -b jb
You should notice a big time diference, from hours for a full repo sync, down to minutes using this trick!
Keep in mind when you read this that I am a complete noob at building android in general, I just can't wait to use this rom. I have successfully built CyanogenMod before, but that's it.
So, I've got my Ubuntu VM which I've built CyanogenMod in before, and I'm attempting to init a repo with the command (repo init -u git://github.com/omnirom/android.git), and it creates a bunch of tags, then I get an error "Error: revision refs/heads/master in manifests not found". Each subsequent time I try to run the command I get "Error: manifest required for this command -- please run init". It also appears that the .repo folder is pretty empty as compared to my cyanogen one.
Am I doing something wrong? Or am I just jumping the gun and the rom isn't ready to build yet.
Or they named the manifest different, or it needs to be updated first I think, I got the same error.
Sent from my Nexus 7 using XDA Premium 4 mobile app
legomaster181 said:
Keep in mind when you read this that I am a complete noob at building android in general, I just can't wait to use this rom. I have successfully built CyanogenMod before, but that's it.
So, I've got my Ubuntu VM which I've built CyanogenMod in before, and I'm attempting to init a repo with the command (repo init -u git://github.com/omnirom/android.git), and it creates a bunch of tags, then I get an error "Error: revision refs/heads/master in manifests not found". Each subsequent time I try to run the command I get "Error: manifest required for this command -- please run init". It also appears that the .repo folder is pretty empty as compared to my cyanogen one.
Am I doing something wrong? Or am I just jumping the gun and the rom isn't ready to build yet.
Click to expand...
Click to collapse
Archaic1881 said:
Or they named the manifest different, or it needs to be updated first I think, I got the same error.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this, after looking in the omnirom/android sub you will see there is a branch option which you must supply in the repo init command thru the -b command line parameter
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.3
it's working for me, downloading source as we speak.. If I can get a successful build for my N4 I will post any findings / issues that I come across that can possibly help others to build also..
VoiD_Dweller said:
Try this, after looking in the omnirom/android sub you will see there is a branch option which you must supply in the repo init command thru the -b command line parameter
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.3
it's working for me, downloading source as we speak.. If I can get a successful build for my N4 I will post any findings / issues that I come across that can possibly help others to build also..
Click to expand...
Click to collapse
I think they must've fixed it, because I swear I tried that before, but it's working now. Thanks!
Same here. At least it works now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
legomaster181 said:
I think they must've fixed it, because I swear I tried that before, but it's working now. Thanks!
Click to expand...
Click to collapse
Yeah, I originally tried it without the branch specified and got the same error..
I faced similar problem, found a workaround
VoiD_Dweller said:
Yeah, I originally tried it without the branch specified and got the same error..
Click to expand...
Click to collapse
In repo sync I faced similar problem.
...
Fetching projects: 68% (11/16) Fetching project css/scripts.git
Fetching projects: 75% (12/16) Fetching project linuxbsp/u-boot.git
Fetching projects: 100% (16/16), done.
error: manifest required for this command -- please run init
After analyzing a bit, I found for one of the git repo the checkout folder is created and it is empty.
(originally It happend because the branch I was trying to checkout was not existing)
I deleted the empty folder and ran repo sync again. problem was solved.
May be a bug in repo to be fixed?
another option is to use an "strace" for instance when i have problems downloading i will use this $ strace repo sync -f" it will show you the path of the missing file which can easily be removed for a resync
hi guys,
I don't know if it is the good thread to post such question but i don't find any other thread related.
So, I got some problem syncing the omni repo. Whilst it was working fine since saturday last repo sync.
I dunno know how the happens. I actually felt into this error
Code:
Syncing work tree: 62% (260/418) error: revision android-4.4_r1 in platform/hardware/qcom/bt not found
I try to find some answer with my best friend goolgle but failed to grab one.
I checked the tree, files are there.
As far as i know this comes from roomservice.xml located into .repo/local_manifests.
It is advice to <!--Please do not manually edit this file-->
I'm searching some way to solved this issues (repo command or git? )as i m starting to translate some projects, i would not lost my already work done.
hope someone could point me to the right direction
thanks everyone
fragargon said:
Code:
Syncing work tree: 62% (260/418) error: revision android-4.4_r1 in platform/hardware/qcom/bt not found
Click to expand...
Click to collapse
Well, looking at https://github.com/omnirom/android/blob/android-4.4/default.xml#L286 there is no android-4.4_r1. Not sure where it pulled that from. So try removing the _r1 so it just matches the android-4.4. Rather, you could try removing the line altogether since the default manifest already has that. What device are you trying to compile? If it's trying to pull that repo's branch (which doesn't exist) it needs to be fixed. But in the mean time, you should be able to remove the line and be good.
PonsAsinorem said:
Well, looking at https://github.com/omnirom/android/blob/android-4.4/default.xml#L286 there is no android-4.4_r1. Not sure where it pulled that from. So try removing the _r1 so it just matches the android-4.4. Rather, you could try removing the line altogether since the default manifest already has that. What device are you trying to compile? If it's trying to pull that repo's branch (which doesn't exist) it needs to be fixed. But in the mean time, you should be able to remove the line and be good.
Click to expand...
Click to collapse
Hi PonsAsinorem,
thanks for your answer
The targeted device is nexus4. I just don't understand how this happens since i have already succesfully compile the firmware.
Latest compile was on 15/01/2014 and used to sync twice a week. I spotted that i could start learn commit on github by translation so...
i will delete the compromiting line into the roomservice.xml
hope
fragargon said:
Hi PonsAsinorem,
thanks for your answer
The targeted device is nexus4. I just don't understand how this happens since i have already succesfully compile the firmware.
Latest compile was on 15/01/2014 and used to sync twice a week. I spotted that i could start learn commit on github by translation so...
i will delete the compromiting line into the roomservice.xml
hope
Click to expand...
Click to collapse
Ok, the mako's omni.dependencies was just changed (3 days ago). I'd also take a further look at your roomservice (or paste it in CODE tags here) to make sure you don't have any other offending lines.
https://github.com/omnirom/android_...3b880dc#diff-dfae556379c73dbe35de7e48b1ff5d81
okay, i have removed the offending line and repo sync successfully.
here is the original roomservice.xml (located into /.repo/local_manifests)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
<project name="android_device_lge_mako" path="device/lge/mako" remote="omnirom" revision="android-4.4" />
<project name="android_kernel_lge_mako" path="kernel/lge/mako" remote="omnirom" revision="android-4.4" />
<project name="platform/hardware/qcom/bt" path="hardware/qcom/bt" remote="aosp" revision="android-4.4_r1" />
</manifest>
I just manually removed the last line and syncing work tree succeed.
i checked project.list, i had twice
Code:
hardware/qcom/bt
but since a removed the offending line and repo sync successfully the second one has gone.
thanks a lot for your support, i didn't dare editing this file.
Btw i saw someone on G+ commenting the same error while repo syncing is the link
as far as google driven my quest i spotted that, for some unknown reason to me, leads to the blob
https://github.com/android/platform_manifest/blob/android-4.4_r1/default.xml
anyway, now this seems fixed
Yeah. Here's a summary of what happened:
Months ago, someone decided to move a bunch of hardware repos out of the default manifest and into omni.dependencies. This was first done for mako.
Problem was, removing a repo from the default manifest and moving it into device dependencies is easier said than done - in many cases, people had entire work branches deleted without warning. So the hardware repos were put back into the default manifest, but not removed from mako's omni.dependencies (the latter was an accidental omission - we forgot). Thing is, at that point, it didn't break anything - as long as omni.dependencies and the default manifest were pointing to the same location it was OK.
The problem was that hardware/qcom/bt got forked from AOSP into Omni so we could make changes - then mako's omni.dependencies started causing weird breakage.
This shouldn't happen to anyone else, but anyone who did have their roomservice.xml corrupted will need to remove that one line manually.
I am posting cause topic is already here. Since yesterday it is forth time in a row now while I am trying to sync repo.
Two weeks ago it went without a glitch, I builded for mako with success. I am actually running this build now. Anyway, while syncing repo I got something like this at the "unexpected" end :
Code:
Syncing work tree: 5% (21/416) error: in `sync`: [Errno 2] No such file or directory: u'/home/tytus/android/omni/device/generic/mini-emulator-mips/.git/HEAD'
error: manifest missing or unreadable -- please run init
I am building on Ubuntu 13.10, fresh install, bulding for mako as of now.
morganmf said:
I am posting cause topic is already here. Since yesterday it is forth time in a row now while I am trying to sync repo.
Two weeks ago it went without a glitch, I builded for mako with success. I am actually running this build now. Anyway, while syncing repo I got something like this at the "unexpected" end :
Code:
Syncing work tree: 5% (21/416) error: in `sync`: [Errno 2] No such file or directory: u'/home/tytus/android/omni/device/generic/mini-emulator-mips/.git/HEAD'
error: manifest missing or unreadable -- please run init
I am building on Ubuntu 13.10, fresh install, bulding for mako as of now.
Click to expand...
Click to collapse
Are you sure you didn't run out of disk space at some point?
You have some sort of weird corruption in your tree.
Well, I did run out of space on previous Ubuntu installation, than I grab bigger drive and setup Ubuntu from scratch and setup building environment as well. Anyway after few more tries it went good. Thanks, every help is really appreciated as I am a bit of a newbie.
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
I was downloading mako specific files and i closed the terminal before it finished. now when i start again it give me this error:-
build/core/config.mk:369: * Error: could not find jdk tools.jar, please install JDK6, which you can download from java.sun.com. Stop.
WARNING: Trying to fetch a device that's already there
build/core/config.mk:369: * Error: could not find jdk tools.jar, please install JDK6, which you can download from java.sun.com. Stop.
** Don't have a product spec for: 'omni_mako'
** Do you have the right repo manifest?
what should i do?
Maybe try deleting the mako directory and roomservice.xml, then repo sync and recompile.
PonsAsinorem said:
Maybe try deleting the mako directory and roomservice.xml, then repo sync and recompile.
Click to expand...
Click to collapse
where exactly is the mako directory?
PonsAsinorem said:
Maybe try deleting the mako directory and roomservice.xml, then repo sync and recompile.
Click to expand...
Click to collapse
ok thanks!!! it worked!!
Hey everyone, hope someone can help
When I run the command "breakfast hlte"
I get:
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_samsung_hlte
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/msm8960-common/msm8960.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
[email protected]:~/android/system$
Click to expand...
Click to collapse
Also, if I proceed and try to extract the proprietry blobs with "extract-files.sh" I get:
Extracting /system/etc/firmware/a330_pfp.fw ...
37 KB/s (2212 bytes in 0.058s)
Extracting /system/etc/firmware/a330_pm4.fw ...
91 KB/s (9220 bytes in 0.098s)
Extracting /system/vendor/lib/libmm-color-convertor.so ...
87 KB/s (9308 bytes in 0.103s)
Extracting /system/lib/cdma/libsec-ril.so ...
remote object '/system/lib/cdma/libsec-ril.so' does not exist
Click to expand...
Click to collapse
Any help would be appreciated
EDIT: the line where it fails is pointing the wrong place :/ I found it in root explorer so I'll see what I can do
EDIT: fixed the cdma/libsec-ril.so
but now it's complaining it can't find a gsm version...
Use the blobs from the GitHub repo TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/hlte. Unfortunately I can't post a direct link due to onerous XDA restrictions on new user's posts. I am having the same problem with not being able to extract all the propietary blobs from my Note 3 device.
CW03 said:
Hey everyone, hope someone can help
When I run the command "breakfast hlte"
I get:
Also, if I proceed and try to extract the proprietry blobs with "extract-files.sh" I get:
Any help would be appreciated
EDIT: the line where it fails is pointing the wrong place :/ I found it in root explorer so I'll see what I can do
EDIT: fixed the cdma/libsec-ril.so
but now it's complaining it can't find a gsm version...
Click to expand...
Click to collapse
Did you ever get this figured out? I am trying to build right now and am having the same problem. I got the blobs from that github repository, and am still running into this same error.
[email protected]:~/android/system$ breakfast hlte
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/msm8960-common/msm8960.mk" does not exist. Stop.
Device hlte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_hlte
Default revision: cm-11.0
Checking branch info
CyanogenMod/android_device_samsung_hlte already exists
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_samsung_hlte
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/msm8960-common/msm8960.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
[email protected]:~/android/system$
Click to expand...
Click to collapse
iamdanhenry said:
Did you ever get this figured out? I am trying to build right now and am having the same problem. I got the blobs from that github repository, and am still running into this same error.
Click to expand...
Click to collapse
Do you have device/samsung/msm8960-common/msm8960.mk? If you did used "lunch", it should add this repo (and a few others) to your .repo/local_manifests/roomservice.xml. The repos are defined in device/samsung/hlte/cm.dependencies, which should already be there.
If it doesn't fetch the repos automatically, you can do this with "repo sync".
For the proprietary blobs, you only need to add the samsung repo from TheMuppets github to your .repo/local_manifests/whatever.xml and "repo sync" to pull it in. No need to try to extract anything from your device.
jisoo said:
Do you have device/samsung/msm8960-common/msm8960.mk? If you did used "lunch", it should add this repo (and a few others) to your .repo/local_manifests/roomservice.xml. The repos are defined in device/samsung/hlte/cm.dependencies, which should already be there.
If it doesn't fetch the repos automatically, you can do this with "repo sync".
For the proprietary blobs, you only need to add the samsung repo from TheMuppets github to your .repo/local_manifests/whatever.xml and "repo sync" to pull it in. No need to try to extract anything from your device.
Click to expand...
Click to collapse
After I posted I went and downloaded msm8960-common repository and extracted it into the build directory, it then got the same error for some qualcomm libraries that were missing so I downloaded those as well. I then added the proprietary files from the "TheMuppets" repo.
It would appear things are going better now, but still can't build because of some errors with the kernel not being there. I am going to go download the kernel source and try to get it figured out. If I can't I will make a new thread.
Thank you for your help!