Control: clone -1 -2
Control: reassign -2 apt-listchanges
Control: severity -2 important
Control: retitle -2 apt-listchanges doesn't show NEWS entries
On Sun, 19 May 2019 13:55:39 +0200 Michael Biebl wrote:
> Am 19.05.19 um 13:43 schrieb Guido Günther:
>
> > On Sat, May 18, 2019 at 01:20:05PM
Am 19.05.19 um 13:43 schrieb Guido Günther:
> # apt-listchanges --profile=apt --dump-seen | grep systemd
> libconfig-model-systemd-perl 0.239.1-1
> systemd 241-4
Hm, interesting. That returns
$ apt-listchanges --profile=apt --dump-seen | grep systemd
systemd 241-1
Which makes no sense at all,
Am 19.05.19 um 13:43 schrieb Guido Günther:
> On Sat, May 18, 2019 at 01:20:05PM +0200, Michael Biebl wrote:
>> https://salsa.debian.org/systemd-team/systemd/commit/e3772a013721083a740ab9dedbf060cf5b3c3709
>> but either I made a mistake or apt-listchanges is buggy, since on none
>> of my systems
Hi,
On Sat, May 18, 2019 at 01:20:05PM +0200, Michael Biebl wrote:
> Am 23.04.19 um 19:48 schrieb Guido Günther:
>
> > On Tue, Apr 23, 2019 at 07:29:52PM +0200, Michael Biebl wrote:
>
> >> Hm, I'm a bit undecided. This seems like a very special setup you have
> >> there and a NEWS entry is shown
Am 23.04.19 um 19:48 schrieb Guido Günther:
> On Tue, Apr 23, 2019 at 07:29:52PM +0200, Michael Biebl wrote:
>> Hm, I'm a bit undecided. This seems like a very special setup you have
>> there and a NEWS entry is shown to basically every user.
>> If it was a more common issue, I would totally
Hi,
On Tue, Apr 23, 2019 at 07:29:52PM +0200, Michael Biebl wrote:
> On Fri, 12 Apr 2019 10:47:39 +0200 Guido =?iso-8859-1?Q?G=FCnther?=
> wrote:
> > Hi,
> > On Thu, Apr 11, 2019 at 11:27:05PM +0200, Michael Biebl wrote:
> > > Am 11.04.2019 um 22:47 schrieb Michael Biebl:
> > > > Am 11.04.19 um
On Fri, 12 Apr 2019 10:47:39 +0200 Guido =?iso-8859-1?Q?G=FCnther?=
wrote:
> Hi,
> On Thu, Apr 11, 2019 at 11:27:05PM +0200, Michael Biebl wrote:
> > Am 11.04.2019 um 22:47 schrieb Michael Biebl:
> > > Am 11.04.19 um 21:46 schrieb Guido Günther:
> >
> > >> it took me a while to figure out why
Hi,
On Thu, Apr 11, 2019 at 11:27:05PM +0200, Michael Biebl wrote:
> Am 11.04.2019 um 22:47 schrieb Michael Biebl:
> > Am 11.04.19 um 21:46 schrieb Guido Günther:
>
> >> it took me a while to figure out why rendering got broken in my wayland
> >> compositor. It would be great if the change from
Am 11.04.19 um 23:27 schrieb Michael Biebl:
> Btw, what exactly was the breakage?
> I assume you worked around that for now by adding your user to group
> render?
> Which wayland compositor is that, btw? How do you start it?
Fwiw, GNOME on Wayland (with gdm) seems to work fine here. At least I
Am 11.04.2019 um 22:47 schrieb Michael Biebl:
> Am 11.04.19 um 21:46 schrieb Guido Günther:
>> it took me a while to figure out why rendering got broken in my wayland
>> compositor. It would be great if the change from video to render group
>> could be mentioned in udev.NEWS.
>
> That is
Control: notfound -1 243-1
Control: found -1 241-3
Hi Guido
Am 11.04.19 um 21:46 schrieb Guido Günther:
> Package: udev
> Version: 243-1
I suppose you meant 241-3 here...
> Severity: normal
>
> Hi,
> it took me a while to figure out why rendering got broken in my wayland
> compositor. It
Package: udev
Version: 243-1
Severity: normal
Hi,
it took me a while to figure out why rendering got broken in my wayland
compositor. It would be great if the change from video to render group
could be mentioned in udev.NEWS.
Cheers,
-- Guido
-- Package-specific info:
-- System Information:
12 matches
Mail list logo
