Re: Adam D. Barratt 2012-09-08 <1347135924.8753.72.ca...@jacala.jungle.funky-badger.org> > Often this is achieved by ftp-master copying the packages "upwards" > during the point release. My understanding is that this would be > unwelcome in this case, as it would re-introduce a number of binary > packages which have been dropped from the wheezy packages.
Nod. (We should probably also add something about this to the release notes.) > As far as I can see, the easiest way to resolve this would therefore be > a no-changes upload to unstable with a higher version number, which we > could then allow to transition to testing. This could be a fake > "8.4.14.really.8.4.12" style version, but this has the potential to > break again in future. My suggestion would be to add an epoch, ensuring > that the wheezy packages always have a higher version - I've assumed > that the packages won't be seeing any further updates for jessie. I think the proper solution would be to really update the wheezy package with the 8.4.13 postgresql source. There might even be relevant pl/perl changes that should go into wheezy. I'll check the changelog for that. I'd rather avoid adding an epoch version (or some other artificially high version number) as that would break upgrades for people moving to some other source for postgresql-8.4 packages (pgapt.debian.net, soon to be moved to postgresql.org infrastructure). Not sure how we can keep the versions properly sorted, short of always also updating 8.4 in wheezy. We'll think about that. Martin? Christoph -- c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
