How are packages in core/extra updated?

ngoonee · 2009-06-16 01:37:43

Hi all,

I know the title sounds noob-ish, but hopefully my description would make it a BIT less so.

Basically, I know there are contributors to the AUR, TUs who can promote to community, and devs who maintain core/extra (and testing as well). My question is - what is the procedure is for updates to core/extra? I can see packages updated every couple of days, almost in lock-step with upstream, so I assume the devs are really busy. But how do I keep track if a particular upstream has already been included into core/extra?

In my particular case, there's a dual-screen bug/regression since the beginning of the year in glibc. I've been tracking the bug, which I and others originally reported to Ubuntu's launchpad, and the fix was released upstream recently. The OCD in me just wants to track when this fix is actually implemented upstream and when the new version is actually included into core/extra. I assume it spends some time in testing first, or is that not required for all packages (testing doesn't seem very full, come to think of it, so I doubt EVERYTHING goes there first?).

Thanks for your patience with a non-dev.

rson451 · 2009-06-16 01:41:55

I'd suggest you subscribe to the arch-dev mailing list to see package bumps that are coming. They often list changes in the emails they send out looking for signoffs.

Allan · 2009-06-16 02:26:34

So, how it works for me is:

- I see an upstream update released announced on a mailing list or a user flags my package out-of-date. For most packages, users notifying me of an update is very fast...
- When I have time, I update the package and take it for a local test run
- If it is a [core] package, then it must go to [testing] first. Packages can go straight to [extra] but the maintainer can put them in [testing] first if other packages require rebuilt because of the update or if they just feel it is needed.

As far as the glibc fix goes, I currently have no reason to make a new glibc release as none have been released upstream and no bugs(*) are filed against the current release... If your fix has been included upstream (preferably on the 2.10 branch), feel free to file a bug report with all the details (what is broken, link to upstream fix, even better if you apply the patch yourself and confirm it works).

(*) well, there is one... but it does not warrant a new release.

ngoonee · 2009-06-17 09:30:36

Strange that no bugs are filed against glibc. I'll check that out and follow up.

Arch Linux

#1 2009-06-16 01:37:43

How are packages in core/extra updated?

#2 2009-06-16 01:41:55

Re: How are packages in core/extra updated?

#3 2009-06-16 02:26:34

Re: How are packages in core/extra updated?

#4 2009-06-17 09:30:36

Re: How are packages in core/extra updated?

Board footer