On lunes, 5 de septiembre de 2016 12:07:49 A. M. ART Michael Biebl wrote:
> Am 04.09.2016 um 23:57 schrieb Lisandro Damián Nicanor Pérez Meyer:
> > On domingo, 4 de septiembre de 2016 3:03:12 A. M. ART Michael Biebl wrote:
> >> Am 04.09.2016 um 02:44 schrieb Lisandro Damián Nicanor Pérez Meyer:
>
Am 04.09.2016 um 23:57 schrieb Lisandro Damián Nicanor Pérez Meyer:
> On domingo, 4 de septiembre de 2016 3:03:12 A. M. ART Michael Biebl wrote:
>> Am 04.09.2016 um 02:44 schrieb Lisandro Damián Nicanor Pérez Meyer:
>>> I have friends that used to use klipper in gnome, although i don't know
>>> if
On domingo, 4 de septiembre de 2016 3:03:12 A. M. ART Michael Biebl wrote:
> Am 04.09.2016 um 02:44 schrieb Lisandro Damián Nicanor Pérez Meyer:
> > I have friends that used to use klipper in gnome, although i don't know
> > if that's still possible.
>
> They can easily remove the key from the
[Oops, accidentally sent a private reply the first time.]
Hi, Sandro.
In general, it's possible to request temporary guest access to specific
porterboxes, but I don't know how promptly such requests tend to go
through. For the record, you can find relevant documentation at
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
ksnapshot | 4:15.04.3-1 | source, kfreebsd-amd64, kfreebsd-i386
ksnapshot | 4:15.08.0-1 | source, amd64, arm64, armel, armhf, hurd-i386, i386,
mips, mips64el, mipsel, powerpc, ppc64el,
I rarely print email messages, but every now and then I can't avoid it. That's
when I remember that "there is a problem". Every version of KMail I remember
up to the latest (5.2.3) insists on printing the message body in a tiny font
size, maybe 6pt.
I've tried the default settings, tinkered
On Samstag, 3. September 2016 18:24:09 CEST Michael Schuerig wrote:
> On Mittwoch, 31. August 2016 22:14:16 CEST Martin Steigerwald wrote:
> > All seems fine so far.
>
> For me, automatic screen locking after some idle time and screen power
> management doesn't work. The screen just stays on all
Thank you Diederik. I see the unstable knaspshot package is now a
transitional package. I'm not sure if I didn't notice this before or if
this was maybe prompted by this bug report here. Anyway, thank you for the
info and work as a Debian maintainer :)
On 3 September 2016 at 13:42, Diederik de
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
Processing control commands:
> block 836604 by -1
Bug #836604 [ftp.debian.org] RM: llvm-toolchain-3.6 -- ROM; We should ship only
3.8, 3.9 and maybe 4.0 in the next stable
836604 was blocked by: 836607 836606
836604 was not blocking any bugs.
Added blocking bug(s) of 836604: 836608
--
836604:
Source: qtcreator
Severity: important
Control: block 836604 by -1
Hello,
This package depends on llvm-toolchain-3.6.
To limit the number of llvm versions in the next Debian stable, we
would like all packages using/depending llvm/clang/lldb to move to version
3.8 or 3.9 so that we can remove
Hi,
On 04/09/16 05:42, juichenieder-deb...@yahoo.co.uk wrote:
> 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
12 matches
Mail list logo
