Control: severity -1 normal
Am 02.10.2014 um 22:38 schrieb Rob Browning:
reopen 746012
thanks
Debian Bug Tracking System ow...@bugs.debian.org writes:
This is an automatic notification regarding your Bug report
which was filed against the graphviz package:
#746012: graphviz: please
Matthias Klose d...@debian.org writes:
this is hardly release critical. Please set severities correctly when
reopening
issues.
Actually, I was explicitly told to raise all the guile-2.0 migration
bugs to be RC as we approched the freeze, since guile-1.8 really
shouldn't be in jessie.
Am 07.10.2014 um 17:52 schrieb Rob Browning:
Matthias Klose d...@debian.org writes:
this is hardly release critical. Please set severities correctly when
reopening
issues.
Actually, I was explicitly told to raise all the guile-2.0 migration
bugs to be RC as we approched the freeze,
Am 07.10.2014 um 18:42 schrieb Rob Browning:
Matthias Klose d...@debian.org writes:
so what exactly is release critical in the current package?
A long while back I wanted to remove 1.8 from jessie, so I was told to
first file bugs, then file an RM/ROM, and then, after a while, upgrade
any
Matthias Klose d...@debian.org writes:
so what exactly is release critical in the current package?
A long while back I wanted to remove 1.8 from jessie, so I was told to
first file bugs, then file an RM/ROM, and then, after a while, upgrade
any remaining bugs to serious.
The reason I want to
Matthias Klose d...@debian.org writes:
no, 1.8 shouldn't be shipped in jessie (I removed 1.8 from Ubuntu some months
before). I think you take the wrong approach. I think a lot of bug reports,
including this one, are handled wrong. I'm asking you why you think this
issue
prevents removal
reopen 746012
thanks
Debian Bug Tracking System ow...@bugs.debian.org writes:
This is an automatic notification regarding your Bug report
which was filed against the graphviz package:
#746012: graphviz: please migrate to guile-2.0
It has been closed by Matthias Klose d...@debian.org.
It
7 matches
Mail list logo
