2016-01-15 23:33 GMT+01:00 David Allouche <da...@allouche.net>: > > On 15 Jan 2016, at 23:23, Nicolai Hess <nicolaih...@gmail.com> wrote: > 2016-01-15 23:16 GMT+01:00 David Allouche <da...@allouche.net>: >> >> On 15 Jan 2016, at 21:01, stepharo <steph...@free.fr> wrote: >> Le 15/1/16 20:45, David Allouche a écrit : >> >> >> 1. it does not show the package that contains my fix (Spec-Tools) >> >> This is strange. And MC shows the package as dirty? Then this is a bug. >> >> >> I do not know how MC shows a package as dirty. >> > > This is how it should look in slice maker (left side) and monticello > browser (right side). > The " * " marks dirty packages. > > > Okay, got that. > > So yes, it's broken, but maybe it's something else entirely, I get new > reproducible errors every few minutes: errors when activating pretty > printing in the diff viewer in Monticello, >
this is a known error from the "recent" change for rubric text component > unexpected contextual menu showing up when I do Cmd-T in the debugger, > known ( from the recent changes for debugger :) ) > infinite recursions when trying to debug through the > MonticelloRepositoryBrowser... > I don't know this error. But I don't think "this" MonticelloRepositoryBrowser is actually used. > All things that are so obvious that I have trouble believing they are > actual bugs. Maybe there was something wrong in how my image was generated. > I will try building another image. > > I also wonder… so this "list of dirty packages" is actually a list of > every package where some of them are marked dirty? I mean, why is it not > just the list of dirty package, as the name implies? >
