W dniu 26.08.2015 o 03:50, Daniel van Vugt pisze: > Wait a sec, is there really "going to be trouble"? > > I am reminded that the landing on the train branch (lp:mir/ubuntu) is > always the _last_ thing to happen by far. lp:ubuntu/mir and > lp:ubuntu/wily-proposed/mir as well as the archive itself with shiny new > debs all get updated around a DAY earlier than the final landing to the > dummy branch (lp:mir/ubuntu) happens. It's annoyingly delayed, so that's > hard to forget.
Hmm? Not sure what changed since I was last here, but that shouldn't be the case. The target branch of the landed MP(s) (lp:mir/ubuntu?) should be pushed to as soon as the packages migrate to the release pocket. That's the same time when lp:ubuntu/mir is updated, with lp:ubuntu/wily-proposed/mir being updated as soon as the silo is published and the packages pushed to the proposed pocket. > Therefore, I doubt that using lp:ubuntu/something for the train to > monitor would cause trouble at all. Worst case is that it tries to land > the same branch twice. And we all know from previous experience that bzr > blindly succeeds and shows no diff landing any branch multiple times. I > think it would just work. I think you're missing one thing here: lp:ubuntu/mir does not get merged into. Launchpad just takes the source package as uploaded to the archive and imports the changes as a new commit. While the contents might be the same, it will be a different commit. If you really don't want to maintain a Ubuntu packaging branch (which lp:mir/ubuntu really is), you'll just need to build the source packages by hand and ask the train staff to upload them to your silos. -- Michał Sawicz <michal.saw...@canonical.com> Canonical Ltd.
signature.asc
Description: OpenPGP digital signature
-- Mir-devel mailing list Mir-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/mir-devel
