Ahh, I see now, kind of, but it looks more like a repackaging of lxsession
caused this, as a package contents search on jessie shows lxlock as appearing
as part of the lxsession package, and indeed, lxlock still builds out of the
lxsession source in testing/unstable.
My pleasure for reporting, ju
Thanks Pino,
A few comments/questions...
root/debian/changelog
This contains only the line for this package, this seems a bit odd to ditch the
changelog from before. While Krita technically goes in to debian as a new
package,
it just replaces the older krita package, and I do not presume that u
Hi,
> My guess is that most of these bugs will fix themselves once 2.9 is
> packaged. I think there were some attempts to fix these before, but the
> package was rejected by the ftpmasters on copyright grounds - so they'll
> need to be some work to sort that out.
Yes, pretty much my philosophy
Just found out about Krita, and thinking about giving it a try...
Does the fact that the latest stable version of Krita upstream (3.x) has now
split from Calligra have any bearing
on this bug?
I.e. instead of trying to fix these issues, we should just start from a clean
slate with Calligra?
B
severity 756450 important
--
Looking at https://www.debian.org/Bugs/Developer#severities they define critical
(and grave) as ``*introduces* a security hole'', so I agree with you of the
importance
of this bug, but I see this as an inherent security flaw that needs to get
addressed,
rather then a
5 matches
Mail list logo
