On Sat, Nov 24, 2012 at 2:29 PM, Don Armstrong <[email protected]> wrote: > On Sat, 24 Nov 2012, Michael Gilbert wrote: >> The first issue was when Josselin uploaded the fix. At that time, >> the bug was assigned to nautilus-open-terminal, but the fix was >> included in a gsettings-desktop-schemas upload. So, after that the >> bug was in package nautilus-open-terminal, but marked as fixed in >> gsettings-desktop-schemas/3.4.2-3. I wonder if these types of >> situations could be improved by automatically reassigning bugs when >> they're fixing in other packages? > > No, because typos will end up in bugs migrating from package to > package.
That's exactly what I said and why I offered proposed the secondary more ideal solution, which would be to not close bugs that are assigned to different packages than the upload itself. Is there a reason not to do that? > In general, you should reassign the bug before you close it. Agreed, it wasn't my mistake, I just came in to correct it. >> My next command was reassigning the bug to the the right package >> (gsettings-desktop-schemas), which marked the bug as notfound in >> nautilus-open-terminal, but also unexpectedly marked the bug as no >> longer fixed in gsettings-desktop-schemas/3.4.2-3 > > Right, because generally when you reassign, the version information is > wrong. It would be reasonable to keep the version information if it > matched the package which the bug was assigned to, but that requires > extra logic. This would be nice. >> So my next step was to correct that, and also set the found >> information. The found command unexpectedly reopened the bug (I >> suppose because there was no fixed info at that time, and I suppose >> I could train myself to put fixed lines first, but that's a bit >> tedious). > > See the documentation of found;[1] if the highest found version is > greater than the highest fixed version, the bug shouldn't be closed, > so it is automatically reopened. Set fixed versions first if you want > this to happen. Point being that it's rather easy to forget ordering relevance, and it's not very intuitive anyway. Would it be possible to define something akin to aritmetic operator ordering (i.e. addition follows multiplication). So, on receiving a found x y fixed w z The server would consider operator ordering and automatically reformat the message to fixed w z found xy Best wishes, Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
