Repo Problems?

[darrenliew96]

Once I added ininjas repo.
I got a message that apt-get encounter no header.
I tried to restore. And add another repo. There's no problem.
Until I added ininjas repo again, It show up the no header warning again.
Is this ininjas repo problem?

[OneHappyTaco]

try apt-get update. If that doesn't work just download and install packages manually with safari.

[darrenliew96]

It's not apt-get update issue. I think is the ininjas repo issue. Can someone confirm that?

[Trcx528]

I would be surprised if it's an iNinjas repo issue, as I haven't heard of an issue from anyone else.  My best recommendation is to try again.

[darrenliew96]

As this issue is not a big deal. But it's quite annoying. It lasted for a month. Today, I restored my iPhone to stock and rejailbreak it.
Nothing happen when updating repos. Until I added the ininjas repo. Then this problem existed.

[UberN00b]

If I remember I correctly i started getting right after y'all upgraded the python version or some other major package around mid-November to early December.

[Trcx528]

Can you screen shot the error message please? I don't have an iOS device to test on.

[UberN00b]

Hmm, I failed to find the thread here of the staff talking about switching to a newer version of whatever major program or package it was. I then added the Radare repo to search for a package that would jog my memory because i believed that was the repo you guys got that newer version of whatever from. My point is, after adding cydia.radare.org I no longer get the the missing header error after refreshing.

[NplusM]

In my opinion it's not due to the ininjas repo but rather one of the others, I suggest removing several of your un needed or small time repos as you may not really need them and it just clutters things up causing complications, this is general an easy fix for situations like this.

[darrenliew96]

Solved it today. When I re add the repo today.
None of the warning message appeared.
Weird huh? For the past 1 month, problem exist even though I restored it. Then today, it when back to normal again. BTW +1 to everyone!