Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 21545 ideas, 132412 comments, 2606687 votes
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas
Idea #1331: Add a volatile repository, like in Debian

bug This idea was marked as implemented the 9 July 11. Available starting Ubuntu 9.04 Jaunty Jackalope.
Written by cbrunet the 29 Feb 08 at 12:25. Category: System. Related project: Nothing/Others. Status: Implemented
Rationale
Some packages (ClamAV, for example) need regular version updates, for security reasons. Debian solved this problem with a "volatile" repository that allow some special packages to be updated rapidly, There should be something similar on Ubuntu.
Tags: (none)

521
votes
implemented
Selected solution (#1): Auto-generated solution of idea #1331
Written by cbrunet the 29 Feb 08 at 12:25.
Ubuntu Brainstorm was updated in January 2009. Since the idea #1331 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

Attachments


Duplicates


Comments
Het Irv wrote on the 29 Feb 08 at 15:44
Good Idea, AV and games could be put here, since both get updated frequently.

elias1884 wrote on the 29 Feb 08 at 16:07
And proprietary display drivers

jschlicht wrote on the 29 Feb 08 at 23:53
Couldn't backports be used for this?

roo wrote on the 1 Mar 08 at 07:42
Absolutely agree with this.

Add DSPAM to the list for volatile repo.

twright wrote on the 4 Mar 08 at 00:01
libgpod is a must as everytime itunes get's updated it breaks it

daradib wrote on the 4 Mar 08 at 03:02
Backports that are common and frequent

GatoLoko wrote on the 9 Jun 08 at 10:48
Backports are a completely different thing. A backport is a port form an Ubuntu release to a previous one.

What this idea proposes is a new repository that could be updated FAST, like in a daily basis, directly from upstream.

For example, when Hardy was frozen for stabilization, the ClamAV was frozen too. Before Hardy was released, the shipped ClamAV was old and when launched it gave errors due to outdated virus signatures databases.
With a volatile repo, the virus signatures can be updated as fast as they are released.

bobbo (Idea reviewer) wrote on the 11 Jun 08 at 21:29
This would require a lot of work from a team of dedicated developers. If you want to keep as up to date as possible subscribe to the projects RSS feeds and compile from source.

cheesehead (Brainstorm admin) wrote on the 9 Jul 11 at 16:20
PPAs and SRUs fill this role now.

backpack wrote on the 12 Jul 11 at 05:15
It's good that they have thought about that. It was about time they did something. Thanks for sharing.


Post your comment