You are not logged in.

#1 2023-05-16 10:25:47

Foxboron
Package Maintainer (PM)
From: Norway
Registered: 2013-06-09
Posts: 34
Website

Git migration announcement

This Friday morning (2023-05-19) the Git packaging migration will start until Sunday (2023-05-21). The Arch Linux packaging team will not be able to update packages in any of the repositories during this period.

Notification when the migration starts, and when it is completed, will be published on the [arch-dev-public] mailing list.

How does this impact Arch Linux users?
The [testing] repository will be split into [core-testing] and [extra-testing], the [staging] repository will be split into [core-staging] and [extra-staging]. The [community] repository will be merged into [extra] and will therefore be empty after the migration.

All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before.

Note: After the migration is done, users that have the testing repositories enabled need to include the new repositories ([core-testing] and [extra-testing] instead of [testing]) in their pacman.conf before updating their system.

Other changes:

  • SVN access is discontinued and will dissappear.

  • The svn2git mirror will no longer be updated.

  • asp, which relies on the svn2git mirror, will stop working. It is replaced by pkgctl repo clone.

How does this impact Arch Linux tier 1 mirrors?
During the migration rsync and HTTP access will be shut down. We will send an email notification to arch-mirrors once everything has been finished.

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

Offline

#2 2023-05-16 10:55:42

kokoko3k
Member
Registered: 2008-11-14
Posts: 2,411

Re: Git migration announcement

Thanks.

All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before.

What if one does not update his system from now till after the transition period?
If I have, say, community/package1, will pacman update it to extra/package1 automagically?


Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !

Offline

#3 2023-05-16 11:14:45

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,424
Website

Re: Git migration announcement

kokoko3k wrote:

If I have, say, community/package1, will pacman update it to extra/package1 automagically?

Pacman has no concept of what repository a package came from.  So it will work fine.

Offline

#4 2023-05-16 11:38:43

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: Git migration announcement

What about [community-testing]? Will it go to [extra-testing]?

Offline

#5 2023-05-16 11:56:56

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,424
Website

Re: Git migration announcement

Stefan Husmann wrote:

What about [community-testing]? Will it go to [extra-testing]?

Yes.

Offline

#6 2023-05-16 12:04:34

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,741
Website

Re: Git migration announcement

Is there more information about how the scope of these repos is defined and / or who manages them?  Specificially, the previous definitions of core, extra, and community no longer hold.  What criteria are used to distinguish between the new core and extra?  Will TUs now have all the same access as full developers?  Or will TUs cease to have any main repo access (and only oversee the AUR)?


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#7 2023-05-16 12:08:16

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,109

Re: Git migration announcement

Afaik TUs can now push to extra as if it was community (so there's no extra restriction on "extra" anymore) and core still locked to developers. Which is also one of the reasons why the forum title of Trusted User switched to Package Maintainer.

Last edited by V1del (2023-05-16 12:09:01)

Offline

#8 2023-05-16 12:13:10

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,424
Website

Re: Git migration announcement

Offline

#9 2023-05-16 14:57:42

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,900

Re: Git migration announcement

Sticking topic until after the migration.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#10 2023-05-16 15:51:13

icar
Member
From: Catalunya
Registered: 2020-07-31
Posts: 469

Re: Git migration announcement

Will this have any implication for the users of the devtools package? Specifically the build scripts.

Last edited by icar (2023-05-16 15:51:35)

Offline

#11 2023-05-19 06:12:46

d.ALT
Member
Registered: 2019-05-10
Posts: 927

Re: Git migration announcement

Foxboron wrote:

The [community] repository will be merged into [extra] and will therefore be empty after the migration.

[...]

For regular users, this means that everything works as before.

Sorry guys, I don't understand. I was thinking that this merge would imply removing [community] declaration from pacman.conf. What am I missing?


<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#12 2023-05-19 07:44:28

johnzeuler
Member
Registered: 2023-05-19
Posts: 1

Re: Git migration announcement

Is this and the new pkgctl a step towards an automatic build farm?
Any timeline on that?

Offline

#13 2023-05-19 07:58:55

moson
Member
Registered: 2021-06-03
Posts: 10
Website

Re: Git migration announcement

d.ALT wrote:

Sorry guys, I don't understand. I was thinking that this merge would imply removing [community] declaration from pacman.conf. What am I missing?

Afaik, the (empty) community repo stays there for a while to give users the chance to adopt their config and remove [community] from it.
Then after some time I'd expect that [community] is being removed completely.

Last edited by moson (2023-05-19 08:01:09)

Offline

#14 2023-05-19 08:41:59

Fuxino
Member
From: Slovakia
Registered: 2014-09-26
Posts: 191

Re: Git migration announcement

d.ALT wrote:

Sorry guys, I don't understand. I was thinking that this merge would imply removing [community] declaration from pacman.conf. What am I missing?

There will probably be a new default pacman.conf without [community] repo, I would guess.


Arch + XMonad

Dotfiles: https://github.com/Fuxino/dotfiles

Offline

#15 2023-05-20 06:18:00

Enrico1989
Member
Registered: 2018-07-05
Posts: 212

Re: Git migration announcement

How do I know if I need to take any action, now or after the migration?

Surely this suggests I have to do nothing

For regular users, this means that everything works as before.

but at the same time I read that

The [community] repository will be merged into [extra] and will therefore be empty after the migration. All affected repositories will be provided as empty repositories for a transition period after the migration.

so I wonder if I'll need to remove the following lines from my /etc/pacman.conf

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

Offline

#16 2023-05-20 08:55:27

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 12,037
Website

Re: Git migration announcement

You can remove it if you want, nothing will break if you do, and nothing will break if you don't. It'll probably be removed from the packaged version of pacman.conf at a later date (which will result in a .pacnew file for most people).


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#17 2023-05-20 10:14:11

micronetic
Member
Registered: 2020-02-26
Posts: 40

Re: Git migration announcement

Foxboron wrote:

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

Offline

#18 2023-05-20 10:40:02

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,022
Website

Re: Git migration announcement

micronetic wrote:
Foxboron wrote:

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

2Gb.gif


macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

Offline

#19 2023-05-20 12:02:04

Foxboron
Package Maintainer (PM)
From: Norway
Registered: 2013-06-09
Posts: 34
Website

Re: Git migration announcement

micronetic wrote:
Foxboron wrote:

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

We need to validate that the new setup works. So a restricted set of packagers get access early to limit any issues if we forgot something.


There is a complete runbook available: https://md.archlinux.org/utjjQ-bQTsipIKntPrpf8g?both

Offline

#20 2023-05-20 15:08:56

micronetic
Member
Registered: 2020-02-26
Posts: 40

Re: Git migration announcement

Foxboron wrote:
micronetic wrote:
Foxboron wrote:

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

We need to validate that the new setup works. So a restricted set of packagers get access early to limit any issues if we forgot something.


There is a complete runbook available: https://md.archlinux.org/utjjQ-bQTsipIKntPrpf8g?both

Thank you very much for the explanation!


-----

schard wrote:
micronetic wrote:
Foxboron wrote:

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

https://i.gifer.com/2Gb.gif

Good one :-D

Last edited by micronetic (2023-05-20 15:09:23)

Offline

#21 2023-05-21 15:42:07

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,900

Re: Git migration announcement


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#22 2023-05-22 10:42:20

harcher
Member
Registered: 2015-04-08
Posts: 6

Re: Git migration announcement

This is probably not a big deal but the arch announcement I got via email didn't hae a properly formatted quotes in the instructions.
It looks like this:

    $ pacman -Syu &quot;pacman&gt;=6.0.2-7&quot;`

Offline

#23 2023-05-22 18:32:51

Enrico1989
Member
Registered: 2018-07-05
Posts: 212

Re: Git migration announcement

Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file.

I guess that the merging is manual, in the sense that I need to update the old one (e.g. [community] -> [extra]) an presumably keep my personal edits to it (e.g. ILoveCandy).

Anyway, which of the two files shluld we merge into? As in, after the merge, am I supposed to have only /etc/pacman.conf.pacnew or only /etc/pacman.conf?

Offline

#24 2023-05-22 18:35:07

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,900

Re: Git migration announcement

Leave only /etc/pacman.conf.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#25 2023-05-23 04:14:31

arnuld
Member
From: INDIA
Registered: 2005-12-19
Posts: 220
Website

Re: Git migration announcement

This does not seem to work:

[arnuld@arch64 ~ ]$ sudo pacman -Syu "pacman>=6.0.2-7"
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
error: target not found: pacman>=6.0.2-7

[arnuld@arch64 ~ ]$ pacman -Q pacman
pacman 6.0.2-6

Last edited by arnuld (2023-05-23 04:15:00)

Offline

Board footer

Powered by FluxBB