There are some performance/stability issues currently with picom. From my
experience of using compton and picom I would recommend packaging both compton
5.1 (https://github.com/yshui/picom/releases/tag/v5.1) and current picom.
Hi all:
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96143
If I understood correctly, migration will be manual. It would be nicer
if automatic (fake compton that depends on real picom?), or at least
some kind of notification beyond emails like this one.
Cheers,
GSR
*blush* Copy paste error, missed the 2 at the end.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961432
Sorry for the noise.
GSR
glob2 0.9.4.4-4 is marked for autoremoval from testing on 2020-06-21
It is affected by these RC bugs:
960422: glob2: FTBFS with boost 1.71
Source: meanwhile
Version: 1.0.2-9
Severity: important
Tags: sid bullseye
The new upstream is at https://github.com/obriencj/meanwhile with some new
releases.
--
Regards,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 15 Jun 2020 13:38:29 -0300
Source: ample
Architecture: source
Version: 0.5.7-10
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Fabio Augusto De Muzio Tobich
Closes: 715633
Changes
ample_0.5.7-10_source.changes uploaded successfully to localhost
along with the files:
ample_0.5.7-10.dsc
ample_0.5.7-10.debian.tar.xz
ample_0.5.7-10_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Mon, 15 Jun 2020 20:48:32 +
with message-id
and subject line Bug#715633: fixed in ample 0.5.7-10
has caused the Debian Bug report #715633,
regarding [Mayhem] Bug report on ample: ample crashes with exit status 139
to be marked as done.
This means that you claim that the pro
8 matches
Mail list logo
