Arch moving to git packaging

General system EndeavourOS installation
43

image
image774×42 12.9 KB

The date seems fishy but this is what I’m getting at this link:
https://ftp.sh.cvut.cz/arch/core/os/x86_64/

44

Oof, I sync from this buddy now ftp.sh.cvut.cz/arch. F4st.host is borked.

45

but … why not simply waiting some hours more :wink: mirrors will be overloaded in addition i bet…

1 Like
46

They actually aren’t. Only packages updated upstream during the migration are borked.
Just installed mesa 23.1 update from extra-testing (added it manually) but still haven’t received pacman or devtools update as mirrors offer only files containing 404 pages for those …

47

updates seem to be possible again. haven’t updated yet.

grafik
grafik797×612 118 KB

48

I was also able to get updates with the updated pacman.

1 Like
49

Please read news to update correctly:

https://archlinux.org/news/git-migration-completed/

@dalto
maybe it’s a good idea to pin that on top of forum?

That part at least:

Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file. This is required as we have moved the [community] repository into [extra].

pacman -Syu "pacman>=6.0.2-7"
3 Likes
50

I was a bit too hasty when I took care of the pacman.conf.pacnew file (just had visitors here and was also a bit distracted), deleted the pacman.conf.pacnew with r. However, the update worked fine after that. Just got another one.

51

Ya, no. Not anymore.
I was syncing from that one (as Tier2 mirror), but at some point I couldn’t see progress nor being fully synced. “He” is ok again though :wink:

Time for a pacseek bump :grinning:

52

For some reason I couldn’t merge the files.

I ran a pacdiff and copied the endeavouros repo to the pacman.conf.new (first repo), enabled multilib repo, changed all the other settings that were in the old pacman.conf to the .new, then a save and overwrite.

53

I just let it update. I rarely merge these pacnew files. Mostly because i feel like I will mess it up. Everything has been seamless for me. I have updated 3 out of 5.

54

In this case you either need to merge it or make the changes manually.

At the very least you need to remove the community repo from your pacman.conf.

55

I guess I’m not understanding what it is i need to do. I just updated and i have the new pacman? What else is there?

Edit: Do only this?

Edit:2 I thought it would do this automatically when it updated pacman?

56

If you don’t use testing, that is the only thing that is important, yes.

No, that is what pacnew files are for.

57

I do use testing on and off? So what does that mean?

58

Then you need to replace testing, core, extra, community and multilib with this:

#[core-testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

#[extra-testing]
#Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist
1 Like
59

So is there no community testing?

60

There is no community at all. It has been combined with extra.

You shouldn’t have references to community in your pacman.conf anymore.

1 Like
61

Edited:

Thanks. I misunderstood as i thought when it updated everything would be automatic. On my other systems i guess i could just copy the pacnew file to the pacman.conf?

62

Not if they are EOS systems, that will remove the EOS repo.