Blind to new development release -proposed pocket

[Robie Basak]

Example:

REPORT currently says:

base: 5.4.15-1
    php5_5.4.15-1.dsc
    php5_5.4.15.orig.tar.bz2
    php5_5.4.15-1.debian.tar.gz

ubuntu: 5.4.15-1ubuntu3
    php5_5.4.15-1ubuntu3.dsc
    php5_5.4.15.orig.tar.bz2
    php5_5.4.15-1ubuntu3.debian.tar.gz

base -> ubuntu
    php5_5.4.15-1ubuntu3.patch

debian: 5.5.0+dfsg-13
    php5_5.5.0+dfsg-13.dsc
    php5_5.5.0+dfsg.orig.tar.xz
    php5_5.5.0+dfsg-13.debian.tar.gz

base -> debian
    php5_5.5.0+dfsg-13.patch

However saucy-proposed contains 5.5.0+dfsg-6ubuntu1.

Since I need to re-merge php5 in saucy-proposed before php5 can migrate to saucy, it would be useful if it had used 5.5.0+dfsg-6ubuntu1 for the base->ubuntu patch instead.

I'm also not sure that using 5.4.15-1ubuntu3 would be useful at all, since it has been superceded in saucy-proposed already.

[Brian Murray (brian-murray)]

In momlib.py we can see that merge-o-matic uses local Sources files. I believe these sources files are shared with patches.ubuntu.com and it also is not aware of -proposed. On the server which hosts merge-o-matic we can see the following:

 ls /srv/patches.ubuntu.com/dists/
debian-experimental debian-unstable ubuntu-intrepid ubuntu-maverick ubuntu-quantal ubuntu-trusty ubuntu-xenial
debian-stable ubuntu-feisty ubuntu-jaunty ubuntu-natty ubuntu-raring ubuntu-utopic
debian-testing ubuntu-gutsy ubuntu-karmic ubuntu-oneiric ubuntu-saucy ubuntu-vivid
debian-testing-proposed-updates ubuntu-hardy ubuntu-lucid ubuntu-precise ubuntu-stable-hardy ubuntu-wily

So this would likely require some coordination with the patches.ubuntu.com code.