Skip to main content ↑ ↓
Topic: Why are pkgs come from system or world and not from Gremlins? (Read 1090 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Why are pkgs come from system or world and not from Gremlins?

Maybe I've never paid that much attention before, but after a few hours of updating I updated again and 5 fresh replacements came through.  1 was from Gremlins and 4 from world.  Specifically and as an example:

Code: [Select]
gremlins/iana-etc     20180205-1   20180221-1     0.00 MiB       0.35 MiB
world/libraqm         0.4.0-1      0.5.0-1        0.00 MiB       0.02 MiB
world/python2-urwid   1.3.1-3      2.0.1-1        0.05 MiB       0.32 MiB
world/wavpack         5.1.0-1      5.1.0-2        0.04 MiB       0.16 MiB
world/zita-resampler  1.3.0-5      1.6.0-2        0.05 MiB       0.11 MiB

Now, if we are following the testing wouldn't these packages from world been through testing, meaning they would have already been updated before they got to stable?  Reversely, iana-etc 20180221-1 after no bugs are reported will eventually end up in stable, but only those that have gremlins disabled will see it as a new package then.

Is it that some packages have minor safe revisions that don't require testing and appear straight to system or world?

Re: Why are pkgs come from system or world and not from Gremlins?

Reply #1 –
I would say it like this (strictly my opinion):
As we all knows Artix is following Arch, so packages which are not related to openrc or systemd can follow decisions made by Arch.
With new infrastructure it is possible to deploy only selected packages to stable repositories.
Compared to previous state when the whole testing branch had to be deployed...
This new approach is much better.

Re: Why are pkgs come from system or world and not from Gremlins?

Reply #2 –
Quote from: fungalnet – on
Maybe I've never paid that much attention before, but after a few hours of updating I updated again and 5 fresh replacements came through.  1 was from Gremlins and 4 from world.  Specifically and as an example:

Code: [Select]
gremlins/iana-etc     20180205-1   20180221-1     0.00 MiB       0.35 MiB
world/libraqm         0.4.0-1      0.5.0-1        0.00 MiB       0.02 MiB
world/python2-urwid   1.3.1-3      2.0.1-1        0.05 MiB       0.32 MiB
world/wavpack         5.1.0-1      5.1.0-2        0.04 MiB       0.16 MiB
world/zita-resampler  1.3.0-5      1.6.0-2        0.05 MiB       0.11 MiB

Now, if we are following the testing wouldn't these packages from world been through testing, meaning they would have already been updated before they got to stable?  Reversely, iana-etc 20180221-1 after no bugs are reported will eventually end up in stable, but only those that have gremlins disabled will see it as a new package then.

Is it that some packages have minor safe revisions that don't require testing and appear straight to system or world?
All system/core packages go through gremlins/testing since they are mission critical. As for world and galaxy, they are at the discretion of the person doing the packaging. Packages that won't cause problems/crashes can go straight to world and galaxy and skip gremlins. But for packages that could cause issues we would send those to gremlins first then later move them to the stable repos.

iana-etc is a system package, that is why it went to gremlins. The other packages you listed went straight to world because they were already tested to be stable upstream at arch linux.
Chris Cromer

Re: Why are pkgs come from system or world and not from Gremlins?

Reply #3 –
This makes perfect sense and it was the only logical explanation I could forsee, other than a possible mistake.

Do you know if that is the exact policy arch is using for extra and community?

My debian based mentality where everything flows downstream a few steps (unstable, testing, stable, .. except for security patches) has not let me adjust to arch world yet.
 

Re: Why are pkgs come from system or world and not from Gremlins?

Reply #4 –
Yes, arch linux does the same thing. All packages in "core" go through testing first which is mandatory. Packages in extra and community can go directly to the repos without going into testing, or they can put them in testing for packages that could have issues, it is the package maintainers choice for extra and community.

Debian is definitely much stricter with their testing which is why updates and new packages take so long to reach the end user. They prefer stability rather than having the latest versions of all the packages.
Chris Cromer