You are not logged in.
- Topics: Active | Unanswered
#1 2016-10-18 07:09:14
- Goofball_Jones
- Member
- Registered: 2016-10-18
- Posts: 2
How does it usually work for packages going from "Testing" to "Live"?
When a new package has been released out into the wild, I've noticed that it comes to Arch in a "testing" phase, then it goes live later on. But is it instantly go to live after the testing is over?
The reason I ask is that a few days ago, Chromium 54 was listed on the Package Database as "testing", along with the live Chromium 53. But today I notice that there's no reference for Chromium 54 anywhere now. Does this mean that this package has gone through testing and is ready for going live? Or was it pulled for bugs or what?
Offline
#2 2016-10-18 09:25:50
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: How does it usually work for packages going from "Testing" to "Live"?
It was pulled for a pretty grievous bug: https://bugs.archlinux.org/task/51387
Packages in [testing] require signoffs before being moved in to the repos.
Offline
#3 2016-10-18 14:05:49
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 19,770
Re: How does it usually work for packages going from "Testing" to "Live"?
It was pulled for a pretty grievous bug: https://bugs.archlinux.org/task/51387
Hey, THAT is why I had to use Firefox this weekend to access my Google appspot.com dashboard this weekend 
I feel better.
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