Hi, On Sat, Aug 1, 2015 at 12:48 AM, Akshita Jha <[email protected]> wrote: > > On Fri, Jul 31, 2015 at 10:06 PM, Andreas Tille <[email protected]> wrote: > > > > Moreover I realised that the old implementation of "Versions and Archs" > > is not the way I described before. I think there ordering is > > > > ORDER BY version, release > > > > (See for instance bwa package in bio) > > > > I admit I'm not very proud upon this since it looks a bit mixed but for > > the sake of comparison it makes sense if you may be also simply use the > > original query (or at least the ordering. > > Ok. So, initially I was using the already prepared queries - qurey_pkgs, query_new and now query_vcs as it is (without changing anything). Still there was a difference in Version and Archs of the tasks files that were generated from tasks_udd.py and tasks.py files. I'll recheck if I've missed something and let you know/ >
The order of releases in versions and archs for debian-med tasks file: 1) deployed [0], 2) created from tasks.py (in my system) and 3) created from tasks_udd.py (ordering by 'sort') - all seem to be different. Eg: task : bio in debian-med package :Abacas -------------------------- 1) For deployed debian-med tasks html page [0]: wheezy jessie stretch sid 2) For debian-med tasks file created from tasks.py: Release Version Architectures wheezy 1.3.1-1 all sid 1.3.1-2 all stretch 1.3.1-2 all jessie 1.3.1-2 all 3) For debian-med tasks file created from tasks_udd.py: Release Version Architectures wheezy 1.3.1-1 all jessie 1.3.1-2 all stretch 1.3.1-2 all sid 1.3.1-2 all Package: bwa --------------------- 1) For deployed debian-med tasks html page: Release Version Architectures squeeze 0.5.8c-1 amd64,armel,i386,ia64,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,s390,sparc wheezy 0.6.2-1 amd64,armel,armhf,i386,ia64,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,s390,s390x,sparc sid 0.6.2-1 hurd-i386 jessie 0.7.10-1 amd64 stretch 0.7.12-4 amd64 sid 0.7.12-4 amd64,kfreebsd-amd64 2) For debian-med tasks file created from tasks.py: Release Version Architectures sid 0.7.12-4 amd64,kfreebsd-amd64 sid 0.6.2-1 hurd-i386 wheezy 0.6.2-1 amd64,armel,armhf,i386,ia64,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,s390,s390x,sparc squeeze 0.5.8c-1 amd64,armel,i386,ia64,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,s390,sparc jessie 0.7.10-1 amd64 stretch 0.7.12-4 amd64 3) For debian-med tasks file created from tasks_udd.py: Release Version Architectures squeeze 0.5.8c-1 amd64,armel,i386,ia64,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,s390,sparc wheezy 0.6.2-1 amd64,armel,armhf,i386,ia64,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,s390,s390x,sparc jessie 0.7.10-1 amd64 stretch 0.7.12-4 amd64 sid 0.7.12-4 amd64,kfreebsd-amd64 sid 0.6.2-1 hurd-i386 For some reason, the order of releases is not same even for the deployed html tasks files and tasks files created from tasks.py for debian-med (task: bio). What is the expected order of releases ? Is it to be ordered by 'sort' or by 'version, releases' ? Currently, tasks_udd.py orders releases based on 'sort' field. Regards, Akshita Jha [0] http://blends.debian.org/med/tasks/bio
