How do I resolve version conflicts in autobuilder?

Member's Online

aspidites | # 1 | 2010-05-08, 09:03 | Report

I'm recently developed a new version of aptly and changed the version scheme in the process. Before I was using a date-based version scheme:
yyyy-mm-dd

But I've changed to a number based scheme:
2.0a3

How do I request that the old version be removed so that autobuild doesn't auto-fail?

qwerty12 | # 2 | 2010-05-08, 09:09 | Report

You can ask X-Fade to have it removed.
If all else fails, you can always use an epoch...

The Following User Says Thank You to qwerty12 For This Useful Post:
aspidites

aspidites | # 3 | 2010-05-08, 10:06 | Report

Doing it the other way around. Trying epoch first, then I'll bug X-Fade.

Still no reply from X-Fade and epochs break autobuilder (at least when using py2deb), So I'm just going to have to use my old naming scheme.

Last edited by aspidites; 2010-05-09 at 14:42.

Graham Cobb | # 4 | 2010-05-09, 16:12 | Report

Originally Posted by aspidites View Post

Still no reply from X-Fade and epochs break autobuilder (at least when using py2deb)

Just FYI... Epochs definitely work in the autobuilder for normal packages: maybe it is a py2deb restriction.

Last edited by Graham Cobb; 2010-05-09 at 16:12. Reason: Poor quoting