Blind to new development release -proposed pocket
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Merge-o-Matic |
Triaged
|
High
|
Unassigned |
Bug Description
Example:
REPORT currently says:
base: 5.4.15-1
php5_
php5_
php5_
ubuntu: 5.4.15-1ubuntu3
php5_
php5_
php5_
base -> ubuntu
php5_
debian: 5.5.0+dfsg-13
php5_
php5_
php5_
base -> debian
php5_
However saucy-proposed contains 5.5.0+dfsg-
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.
Changed in merge-o-matic: | |
status: | New → Triaged |
importance: | Undecided → High |
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/ testing- proposed- updates ubuntu-hardy ubuntu-lucid ubuntu-precise ubuntu-stable-hardy ubuntu-wily
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-
So this would likely require some coordination with the patches.ubuntu.com code.