Possibly overkill to file this, but to flag it up wheezy was just released so http://debian.aegirproject.org/ needs to catch up.

Thanks

Comments

anarcat’s picture

Title: Update stable to wheezy » Don't use codenames in our debian repository
Priority: Normal » Minor

we really shouldn't use code names in our repositories, they don't have the same meaning. ie. it's not because you use sid that you should install Aegir unstable.

The only reason the codenames are still there is to not break everything for users that put those codenames in back then.

helmo’s picture

Assigned: Unassigned » anarcat

Why not use codenames.... if I still use squeeze then I want packages suitable for squeeze...
Had I placed 'stable' in my sources.list I would now suddenly get wheezy packages.... which could have unmet dependencies.

It's fine to have 'stable' as a symlink to wheezy, but I personally prefer to point my sources to a version specific name.

anarcat’s picture

The reason is that we don't *actually* build separate packages for wheezy and squeeze - it's all one single package which should work everywhere. It is the reason why we ship drush 5 within our repository nowaday, btw.

helmo’s picture

With these codenames we have the option to make a distinction between Debian releases in the future.

I suggest won't fix here, leaving the symlinks to let users decide if they want to point to stable or wheezy.

anarcat’s picture

the problem with that is that we will then need to maintain aliases like "oldstable" or "oldoldstable", and that people using jessie or sid would automatically use dev releases, which may not be what they want.

and what about people on ubuntu? would stable be 12.04 or 10.04?

helmo’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

closing due to lack of activity, see also #2817199: Alternative hosting of the Debian package archive