[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1003973: Should we pull in fwupd by default for most systems?



On Tue, Jan 18, 2022 at 04:40:02PM -0300, Osmario Avila wrote:
> How to unsubscribe from this newsletter?
> 
> 
> Em ter., 18 de jan. de 2022 às 16:39, Osmario Avila <olvavila@gmail.com>
> escreveu:
> 
> > How to unsubscribe from this newsletter?
> >
> >

Osmario,

I think you may be subsribed to notifications about the bug report itself.

This part from https://www.debian.org/Bugs/Developer may help

[Em portugues:://www.debian.org/Bugs/Developer.pt.html ]

It is also possible to unsubscribe from a bug. Unsubscribing can be done by sending an email to nnn-unsubscribe@bugs.debian.org. The subject and body of the email are again ignored by the BTS. Users will be sent a confirmation message which they must reply to if they wish to be unsubscribed from the bug.

By default, the address subscribed is the one found in the From header. If you wish to subscribe another address to a bug, you will need to encode the address to be subscribed into the subscription message. This takes the form of: nnn-subscribe-localpart=example.com@bugs.debian.org. That example would send localpart@example.com a subscription message for bug nnn. The @ sign must be encoded by changing it to an = sign. Similarly, an unsubscription takes the form nnn-unsubscribe-localpart=example.com@bugs.debian.org. In both cases, the subject and body of the email will be forwarded to the email address within the request for confirmation.

If you are also subscribed to Debian-boot mailing list:

https://www.debian.org/MailingLists/unsubscribe

YOu will receive a confirmation email so that you can confirm that
the unsubscription request is not a mistake.

With every good wish, as ever,

Andy Cater




> > Em ter., 18 de jan. de 2022 às 16:15, Steve McIntyre <steve@einval.com>
> > escreveu:
> >
> >> Source: tasksel
> >> Severity: normal
> >> Tags: security
> >>
> >> Hi,
> >>
> >> At the moment, fwupd will only be installed by default on systems
> >> installed to use a Gnome desktop (checked for Buster, Bullseye and
> >> Sid).
> >>
> >> We should probably pull it in and enable it by default for most
> >> systems (i.e. all desktops and servers) - it's the primary way
> >> expected to drive updates to UEFI system firmware and the DBX
> >> list. Maybe just for UEFI installations?
> >>
> >> -- System Information:
> >> Debian Release: 10.11
> >>   APT prefers oldstable-updates
> >>   APT policy: (500, 'oldstable-updates'), (500, 'oldstable-debug'), (500,
> >> 'oldoldstable'), (500, 'oldstable')
> >> Architecture: amd64 (x86_64)
> >> Foreign Architectures: i386
> >>
> >> Kernel: Linux 5.10.0-0.bpo.9-amd64 (SMP w/4 CPU cores)
> >> Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
> >> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> >> LANGUAGE=en_GB:en (charmap=UTF-8)
> >> Shell: /bin/sh linked to /usr/bin/dash
> >> Init: systemd (via /run/systemd/system)
> >> LSM: AppArmor: enabled
> >>
> >> -- debconf information excluded
> >>
> >>


Reply to: