Invald XML errors

112 views
Skip to first unread message

sondjata olatunji

unread,
Sep 25, 2020, 2:53:59 PM9/25/20
to reposado
Tried to sync today to get the latest updates and I'm getting a bunch of Invalid XML errors. Everything was fine on the 17th when I last synced. Anyone else seeing this?

It is saying the invalid XML is on the local machine (path to local repo...) rather than Apple's servers. Just want to see before I nuke the repo and start over again.

Gregory Neagle

unread,
Sep 25, 2020, 2:54:49 PM9/25/20
to repo...@googlegroups.com
Did you pull the latest code?

Sent from my iPhone

On Sep 25, 2020, at 11:54 AM, sondjata olatunji <sond...@gmail.com> wrote:

Tried to sync today to get the latest updates and I'm getting a bunch of Invalid XML errors. Everything was fine on the 17th when I last synced. Anyone else seeing this?

It is saying the invalid XML is on the local machine (path to local repo...) rather than Apple's servers. Just want to see before I nuke the repo and start over again.

--
You received this message because you are subscribed to the Google Groups "reposado" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reposado+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reposado/5ff6156f-1161-4a8c-a697-3200f7a0f916n%40googlegroups.com.

eho...@gmail.com

unread,
Sep 25, 2020, 4:51:56 PM9/25/20
to reposado
No need to nuke the whole repo.
The recent updates from Apple are providing the .dist files in a compressed format.
The latest reposado code includes a new curl option to handle that, but if you have already synced with the previous code you need to do a little cleanup.

1) Update the reposado code to the latest from the repo
2) Identify the Invalid XML files from the repo_sync log and remove those files from the paths they are at.  You only need to remove the .dist files, not the whole folder.
3) Run repo_sync again with the new code.

That will clean up the errors you're seeing.

sondjata olatunji

unread,
Sep 28, 2020, 9:17:42 AM9/28/20
to reposado
Thanks for the prompt replies. Updating the code and removing the errant XML files fixed the issue.
Reply all
Reply to author
Forward
0 new messages