Active Topics

 


Reply
Thread Tools
zail's Avatar
Posts: 171 | Thanked: 59 times | Joined on Feb 2010 @ Bristol, uk
#1
Been looking through the repo lists (eg http://maemo.org/packages/repository...in_repo_page=1)
and wanted to ask why when a package has been promoted all the way up to extras does a copy (with the same version number) reside in testing and devel too (eg Conky http://maemo.org/packages/view/conky/)? I can understand why there could be a different version in each repo but don't understand why a stable version which is in extras shows as being in testing and devel too...

Sorry if this is obvious to people - I'm quite new and trying to understand stuff!
 
zail's Avatar
Posts: 171 | Thanked: 59 times | Joined on Feb 2010 @ Bristol, uk
#2
Anyone able to explain to me? or point me at an explanation? would be most grateful..
 
krk969's Avatar
Posts: 754 | Thanked: 630 times | Joined on Sep 2009 @ London
#3
the version number is purely decided by the developer that uploads. The system as such doesnt increment the version.

consider an example timeline like this
  • 1.0 version of the s/w uploaded to extras-devel.
  • 1.0 is promoted to extras-testing
  • 2.0 is uploaded to extras-devel
  • 1.0 is promoted to extras
  • 2.0 is promoted to extras-testing
  • 3.0 is uploaded to extras-devel
so now you will have
extras-devel with 1.0 ,2.0 and 3.0 versions
extras-testing with 1.0 and 2.0
extras with 1.0

I think the older version of the s/w get automatically removed from the testing/devel repo, not sure of the devel.
Or if the developer wants he can request to remove the older versions.

Extras , AFAIK , has only 1 version always, but Im not a 100% sure.

does it help ?
__________________
Developer of :
Buddy - budget/expense manager ( website )
Showtime - a telly channel listing viewer/reminder ( website )
Travelapp - london underground status/planner ( website )
Batlevel - desktop widget for battery level ( website )

“I hear and I forget. I see and I remember. I do and I understand.”

Last edited by krk969; 2010-03-31 at 11:33.
 

The Following User Says Thank You to krk969 For This Useful Post:
Posts: 45 | Thanked: 30 times | Joined on Feb 2010 @ Germany
#4
AFAIK debian repositories are self contained, so you could just have the unstable release in /etc/apt/sources.list and you would still get a complete albeit unstable system.

It is not uncommon that a package exists in all three (stable, testing, unstable) with the same version. Especially old packages which do not change anymore often show this behavior.
 

The Following User Says Thank You to drautzburg For This Useful Post:
Khertan's Avatar
Posts: 1,012 | Thanked: 817 times | Joined on Jul 2007 @ France
#5
Or if the developer wants he can request to remove the older versions.
he can request ... but don't know when it ll be done.
 

The Following User Says Thank You to Khertan For This Useful Post:
zail's Avatar
Posts: 171 | Thanked: 59 times | Joined on Feb 2010 @ Bristol, uk
#6
That makes sense and contributes to my greater understanding
 
Reply


 
Forum Jump


All times are GMT. The time now is 07:16.