I have been having issues with updating to 16.06.1 from RC1 (Manjaro was not rolling automatically), which have thankfully been solved with help from the forum. However, Pacman hasn’t shown me any updated packages in a few weeks (even before I updated from RC1), while my other machine running Linux Lite has updates every other day.
Is this normal for the past few weeks? Or is Manjaro still stuck and not rolling and am I just not receiving updates for some reason? How can I check this?
There hasn’t been a stable update for about a week and a half. I think Manjaro updates are usually once every one or two weeks, in large batches. First updates are released to those on the testing branch, then a few days later to the stable branch. You can see in the Announcement section that there have been some testing updates recently and when the developers are satisfied they will be released for those on the stable branch. There will be a forum announcement for the next stable update (here’s the last one), so you can look for the update after that. I’d guess this coming weekend.
This short delay and testing provides a bit more stability to the rolling release model that Manjaro uses.
@Faust I you did what Jonathan said and still don’t receive updates, don’t panic.
I you get to three/four weeks without a large update, then you should start worrying, but anything under two weeks waiting for an update is normal.
@jonathon: Thanks, I know those commands and have tried them. I get the “There’s nothing to do” message, which means… well, that. I’ll look in the announcements section for those posts (@cimarronline: thanks for this tip as well).
@fatboy: my question was more in relation to updates in general. I know the Manjaro stable updates can take a few days, up to two weeks, I read somewhere. But does that apply to package updates in general, such as for installed programs from the repos and AUR? Or do those get bundled in with the stable update run?
See, you can ping the servers on the mirrorlist and have a look if something is wrong.
And yes, if there are no updates for a couple of weeks, something went wrong. It’s not a matter of simply waiting for an update.
Well, ever since that issue with Manjaro not rolling from RC1 to RC2, and then to 16.06.1, I’m suspicious. I have tried pinging the servers on the mirror list (I have tried 5 different ones, in fact), but I get “Name or service not known” for each try, while Google pings just fine.
Here you have the contents of the mirrorlist file (I edited some out so as not to make the post too long):
Manjaro Linux repository mirrorlist
Generated on 24 June 2016 15:13
Well, I’m basing it on the fact that on my machine Manjaro didn’t update to subsequent versions on its own. I had to use a solution proposed in another thread in order to solve this issue. Because of this, I think not all problems might have been solved, and that I might still be stuck for some reason. I’m going off the version of Manjaro itself that was installed on the machine.
I have tried pinging NLUUG. The site itself works just fine, but when I try to ping the FTP I get this:
I think it’s just a matter of being unused to the rolling release model. “Versions” don’t matter. Everything just keeps getting updated and you never do a major upgrade to a newer version. That’s one of the best features.
The risk in rolling release is that because different parts are continually being updated, it can potentially (and actually) break things. So in Manjaro stable, to help avoid breakages, updates are tested for about a week (by the testing branch users) to try to make sure no major breakages will occur. Or give warnings or solutions to difficulties that will result (like the recent GTK3 update that broke many themes). Then the packages are released to the stable branch users. I really appreciate this feature of Manjaro.
I think it would be best for a new user to try it out for a couple months before messing with the update processes or switching to the testing branch (which is more likely to experience breakages).