Processing commands for [email protected]:

> retitle 791077 transition: libmagick++-6.q16-5v5
Bug #791077 [src:imagemagick] imagemagick: library transition is needed when 
GCC 5 is the
Changed Bug title to 'transition: libmagick++-6.q16-5v5' from 'imagemagick: 
library transition is needed when GCC 5 is the'
> user [email protected]
Setting user to [email protected] (was [email protected]).
> usertag 791077 + transition
There were no usertags set.
Usertags are now: transition.
> block 791077 by 790756
Bug #791077 [src:imagemagick] transition: libmagick++-6.q16-5v5
791077 was blocked by: 794734
791077 was not blocking any bugs.
Added blocking bug(s) of 791077: 790756
> reassign 791077 release.debian.org
Bug #791077 [src:imagemagick] transition: libmagick++-6.q16-5v5
Bug reassigned from package 'src:imagemagick' to 'release.debian.org'.
No longer marked as found in versions imagemagick/6.8.9.9-5.
Ignoring request to alter fixed versions of bug #791077 to the same values 
previously set
> severity 791077 normal
Bug #791077 [release.debian.org] transition: libmagick++-6.q16-5v5
Severity set to 'normal' from 'serious'
> On Fri, 07 Aug 2015 at 23:53:23 +0200, Bastien ROUCARIES wrote:
Unknown command or malformed arguments to command.
> > On Fri, Aug 7, 2015 at 11:28 PM, Matthias Klose <[email protected]> wrote:
Unknown command or malformed arguments to command.
> > > confirmed, attaching a patch. however first ilmbase needs a transition, 
> > > and then
Unknown command or malformed arguments to command.
> > > openexr, before you can start this one.
Unknown command or malformed arguments to command.
> >
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
791077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791077
Debian Bug Tracking System
Contact [email protected] with problems


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: 
https://lists.debian.org/[email protected]

Reply via email to