On Fri, 2021-02-12 at 14:40 +0100, Ola Lundqvist wrote:
> The discussion is more or less whether packages should be allowed in
> Debian in the first place. This should be discussed on some general
> mailinglist, like debian-devel or debian-project. LTS cannot put
> restrictions on what should ente
Hi,
On Feb/12/2021, Sylvain Beucler wrote:
> Hi,
>
> On 12/02/2021 01:17, Carles Pina i Estany wrote:
> > When I was discussing this with a friend I had thought if Debian could
> > make available and visible for the users some metrics, contextualised in
> > similar (per functionality) packages:
Hi
I think this is an interesting discussion, but I think we are not doing it
in the right place.
The discussion is more or less whether packages should be allowed in Debian
in the first place. This should be discussed on some general mailinglist,
like debian-devel or debian-project. LTS cannot pu
On Fri, Feb 12, 2021 at 11:21 AM Sylvain Beucler wrote:
> Pushing your point, we'd need to consider all software insecure by
> default, perform regular code audits on the full Debian archive, which
> would be very costly, and blocking packages from reaching testing, which
> would introduce another
Hi,
On 12/02/2021 01:17, Carles Pina i Estany wrote:
When I was discussing this with a friend I had thought if Debian could
make available and visible for the users some metrics, contextualised in
similar (per functionality) packages:
-popularity
-number of recent updates in upstream
-number of
Hi,
When packages reach LTS, users have been using them for years, and it
makes sense we try our best to fix vulnerabilities, and when that proves
near-impossible, we mark them unsupported on a case-by-case basis. This
accounts for poorly written software, but more often orphaned projects,
co
On Friday, 12 February 2021 09:48:12 CET Utkarsh Gupta wrote:
> Hi Thorsten,
[...]
> Whilst working on the security update for stretch, do you think you
> can accommodate this request for a bug fix as well?
Unfortunately, it is not even fixed in unstable (2:2.9.0-17) nor experimental
(2:2.9.0+git
Hi Thorsten,
On Fri, Feb 12, 2021 at 2:03 PM Andrej Shadura wrote:
> > It was observed that Debian's wpa_supplicant is not able to connect to
> > connect to networks with key_mgmt WPA-EAP-SUITE-B and/or
> > WPA-EAP-SUITE-B-192 (aka WPA3-Enterprise 192-bit mode). The upstream
> > wpa_supplicant su
The suite "oldstable-proposed-updates" does not accept source uploads.
Mapping oldstable-security to oldstable-proposed-updates.
binary:libunbound8 is NEW.
binary:libunbound8 is NEW.
source:unbound1.9 is NEW.
===
Please feel free to respond to this email if you don't understand why
your files
