On Wed, Jun 21, 2017 at 02:26:01PM +0200, Christian Ehrhardt wrote:
> On Wed, Jun 21, 2017 at 1:01 PM, Robie Basak <robie.basak@ubuntu.com> wrote:
> > On Wed, Jun 21, 2017 at 03:32:00AM -0700, Christian Ehrhardt wrote:
> > > I wondered about a package being in -updates and thought "was anything
> > > forced when this migrated"?
> > Individual migration run output is logged in
> > http://people.canonical.com/~ubuntu-archive/proposed-migration/log/.
> > From a quick look, as verbose as it is, I think details of hints seen at
> > the time are in there.
> Yeah very verbose and many individual logs, but I found the hints being
> spelled out in there.
> While I could not find my particular example case in any of the logs of
> that day so far I might just need to give the parsing more time.
> > It might be more practical to examine
> > https://code.launchpad.net/~ubuntu-release/britney/hints-ubuntu for
> > hints that the release time have added and removed over time.
> Thanks I remember hearing of that, the link certainly helps to check them.
> Thanks a lot!
However, you mentioned -updates, which implies you're looking at SRUs.
SRU promotions are currently not driven by proposed-migration -
proposed-migration results are advisory only. (This is something I want to
fix, but it's not done yet.) So any SRU team member can run 'sru-release'
at any time, with no record of what was being overridden to do the release.
When we correct this in the hopefully not-too-distant future, you would then
have a record of all the overrides in the history of
<lp:~ubuntu-sru/britney/hints-ubuntu-$release>.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
