Package: wnpp
Severity: wishlist
Owner: Hideki Yamane
* Package name: ruby-sigdump
Version : 0.2.4
Upstream Author : Sadayuki Furuhashi
* URL : https://github.com/frsyuki/sigdump
* License : MIT
Programming Lang: Ruby
Description : Use signal to show s
As a KDE user, I don't have much knowledge about GNOME.
But I remember at the Chinese user support channel, many people have
problems with the default input method (fcitx) and GNOME. The answer is
usually to ask them to switch to GNOME on Xorg.
Someone may argue that ibus(another input method) is
On Sat, 2019-04-06 at 21:48:57 +0200, Bastian Blank wrote:
> On Sat, Apr 06, 2019 at 08:47:51PM +0200, Guillem Jover wrote:
> > I don't use GNOME at all, but I tried to switch to Wayland last month
> > (from i3 to sway), and sadly the experience lasted only a couple of days.
>
> You changed displa
On Sat, 06 Apr 2019 at 20:47:51 +0200, Guillem Jover wrote:
> On Fri, 2019-04-05 at 16:12:22 +0100, Jonathan Dowland wrote:
> > I was surprised to learn — by way of synaptic being autoremoved — that
> > the default desktop in Buster will be GNOME/Wayland.
It's perhaps important to point out before
Hi!
On Fri, 2019-02-08 at 16:25:41 +, Mo Zhou wrote:
> For most programs the "-march=native" option is not expected to bring any
> significant performance improvement. However for some scientific applications
> this proposition doesn't hold. When I was creating the tensorflow debian
> package,
On Sat, Apr 06, 2019 at 08:47:51PM +0200, Guillem Jover wrote:
> I don't use GNOME at all, but I tried to switch to Wayland last month
> (from i3 to sway), and sadly the experience lasted only a couple of days.
You changed display manager implementations and are trying to compare
that? How can yo
Hi!
On Fri, 2019-04-05 at 16:12:22 +0100, Jonathan Dowland wrote:
> I was surprised to learn — by way of synaptic being autoremoved — that
> the default desktop in Buster will be GNOME/Wayland. I personally do not
> think that Wayland is a sensible choice for the default *yet*; and if
> the conseq
Hi!
On Sat, 2019-04-06 at 14:11:57 +0100, Samuel Henrique wrote:
> In order for that to happen I need to introduce an epoch as we were using
> calver and now we have semver, I'm assuming this is a non-controversial
> epoch but I need to send this email on d-devel anyway.
>
> Previous version:
Let me also CC Sebastien Badia, I just CC'ed the first two people that I
found out and are active on the LetsEncrypt team.
On Sat, 6 Apr 2019 at 14:11, Samuel Henrique wrote:
> Hello d-devel, and Harlan,
>
> I'm currently working on a fix for an RC bug on acme-tiny that requires
> the packaging
Hello d-devel, and Harlan,
I'm currently working on a fix for an RC bug on acme-tiny that requires the
packaging of the latest upstream release:
acme-tiny: Please update to ACMEv2 API #924393 [0]
In order for that to happen I need to introduce an epoch as we were using
calver and now we have semv
Andrey Rahmatullin wrote:
> [-- text/plain, encoding quoted-printable, charset: utf-8, 11 lines --]
> On Fri, Apr 05, 2019 at 09:07:06PM +0200, Sven Hartge wrote:
>> CMake is a bit "special" in that regard. To get the right hardening
>> flags to work for some parts of Bacula, we had to include th
11 matches
Mail list logo
