Bug#1009892: ITP: mkdocstrings -- Automatic Python documentation from sources for MkDocs

Package: wnpp Severity: wishlist Owner: Carsten Schoenert X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: mkdocstrings Version : 0.17.0 Upstream Author : Timothée Mazzucotelli * URL : https://github.com/mkdocstrings/mkdocstrings * License : ISC

Accepted ruby-i18n-inflector 2.6.7-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 20 Apr 2022 13:32:20 +0900 Source: ruby-i18n-inflector Architecture: source Version: 2.6.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Marc Dequènes (Duck) Closes: 1009441 1009612

Accepted cyrus-sasl2 2.1.28+dfsg-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 20 Apr 2022 01:01:01 +0200 Source: cyrus-sasl2 Architecture: source Version: 2.1.28+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Cyrus Team Changed-By: Bastian Germann Closes: 977360 1009851 Changes:

Re: Firmware - what are we going to do about it?

On 2022-04-19 22:51:59 +0200 (+0200), Bastian Blank wrote: > On Tue, Apr 19, 2022 at 12:17:06PM +, Jeremy Stanley wrote: > > It's probably what you meant, but just to be clear, as a user I'd > > also want to know which of the firmware packages used/installed were > > pulled from non-free and

Re: Firmware - what are we going to do about it?

On Tue, 2022-04-19 at 23:33 +0200, Jonas Smedegaard wrote: > I do not think that we should impose on our users to trust black magic > by default, though. > > I think that all non-free code distributed by Debian (be that code > executed on the main CPU, and code uploaded to external devices, and

Accepted python-m2r 0.2.1-7.1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 20 Apr 2022 00:03:38 +0200 Source: python-m2r Architecture: source Version: 0.2.1-7.1 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jochen Sprickerhof Closes: 1009396 Changes: python-m2r

Accepted btop 1.2.6-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 17 Apr 2022 01:10:38 +0200 Source: btop Architecture: source Version: 1.2.6-1 Distribution: unstable Urgency: medium Maintainer: Marius Gripsgard Changed-By: Marius Gripsgard Changes: btop (1.2.6-1) unstable; urgency=medium

Bug#1009887: ITP: proftpd-mod-kafka -- ProFTPD module mod_kafka

Package: wnpp Severity: wishlist Owner: Hilmar Preusse X-Debbugs-Cc: debian-devel@lists.debian.org, ProFTPD Maintainance Team * Package name: proftpd-mod-kafka Version : 0.1-1 Upstream Author : TJ Saunders * URL : https://github.com/Castaglia/proftpd-mod_kafka *

Accepted unbound 1.15.0-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 20 Apr 2022 00:37:17 +0300 Source: unbound Architecture: source Version: 1.15.0-3 Distribution: unstable Urgency: medium Maintainer: unbound packagers Changed-By: Michael Tokarev Changes: unbound (1.15.0-3) unstable;

Accepted libvirt-dbus 1.4.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 23:47:16 +0200 Source: libvirt-dbus Architecture: source Version: 1.4.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Libvirt Maintainers Changed-By: Andrea Bolognani Changes: libvirt-dbus

Re: Firmware - what are we going to do about it?

Jonas Smedegaard writes: > Quoting Russ Allbery (2022-04-19 19:29:09) >> We need some way to clearly label non-free firmware packages so that >> you can apply whatever installation or upgrade policy locally that you >> want to apply, but solution #5 provides that by keeping the non-free >>

Accepted openturns 1.18-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 22:07:10 +0200 Source: openturns Architecture: source Version: 1.18-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Pierre Gruet Closes: 1009003 Changes: openturns

Accepted liboauth2 1.4.4.2-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 17:22:44 -0400 Source: liboauth2 Architecture: source Version: 1.4.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian IoT Maintainers Changed-By: Nicolas Mora Changes: liboauth2 (1.4.4.2-2)

Re: Firmware - what are we going to do about it?

Quoting Russ Allbery (2022-04-19 19:29:09) > Jonas Smedegaard writes: > > > Now, some may argue that I am describing a case for package pinning > > here, and that *might* be true but I don't know that yet - because > > the proposed change to the system does not exist yet so I cannot > >

Accepted yt 4.0.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 09:29:22 +0200 Source: yt Architecture: source Version: 4.0.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Changes: yt (4.0.3-1) unstable; urgency=medium

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 12:17:06PM +, Jeremy Stanley wrote: > It's probably what you meant, but just to be clear, as a user I'd > also want to know which of the firmware packages used/installed were > pulled from non-free and what devices prompted their addition. > Something like "The

Re: Keep both images but stop pretending no-free is unofficial

Hi Sam On Tue, Apr 19, 2022 at 02:05:20PM -0600, Sam Hartman wrote: > Marc> Would that not be possible by having an image WITH firmware > Marc> and an installer asking whether the user wants a free or a > Marc> usable system? > For example I would thinki it would be entirely

Re: Keep both images but stop pretending no-free is unofficial

On Apr 19, Sam Hartman wrote: > For example I would thinki it would be entirely reasonable for someone > to want to include a version of Debian installer for use with qemu in an > environment that needed to be DFSG free. > Similarly, I think it would be reasonable for someone to want to provide

Accepted node-lexical-scope 1.2.0+dfsg1-6 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 19:38:13 +0200 Source: node-lexical-scope Architecture: source Version: 1.2.0+dfsg1-6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1009541 Changes:

Accepted node-create-require 1.1.1-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 19:34:17 +0200 Source: node-create-require Architecture: source Version: 1.1.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1009498 Changes:

Re: Firmware - what are we going to do about it?

Quoting Andrey Rahmatullin (2022-04-19 19:49:59) > On Tue, Apr 19, 2022 at 06:51:16PM +0200, Jonas Smedegaard wrote: > > > > > > When I install systems, I consider non-free blobs more risky > > > > > > than other code. > > > > > Do you consider loadable non-free blobs more risky than their > > >

Accepted typedload 2.16-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 20 Jan 2022 21:41:50 +0100 Source: typedload Architecture: source Version: 2.16-1 Distribution: unstable Urgency: low Maintainer: Salvo 'LtWorf' Tomaselli Changed-By: Salvo 'LtWorf' Tomaselli Changes: typedload (2.16-1)

Accepted keyman 15.0.235-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 19:08:18 +0200 Source: keyman Built-For-Profiles: noudeb Architecture: source Version: 15.0.235-1 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: Eberhard Beilharz Changes:

Re: Keep both images but stop pretending no-free is unofficial

> "Marc" == Marc Haber writes: Marc> On Tue, 19 Apr 2022 08:21:10 -0600, Sam Hartman Marc> Marc> wrote: >> One valuable suggestion was to make sure users could easily >> select freedom if that's what they wanted. So I think a free >> installation image is important.

Re: Firmware - what are we going to do about it?

> 3. We could stop pretending that the non-free images are unofficial, and > maybe move them alongside the normal free images so they're published > together. > This would make them easier to find for people that need them, but is > likely to cause users to question why we still make

Accepted rsyslog-doc 8.2204.0+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 20:31:24 +0200 Source: rsyslog-doc Architecture: source Version: 8.2204.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Michael Biebl Changed-By: Michael Biebl Changes: rsyslog-doc (8.2204.0+dfsg-1)

Accepted libtorrent-rasterbar 2.0.6-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 20:41:48 +0200 Source: libtorrent-rasterbar Architecture: source Version: 2.0.6-3 Distribution: unstable Urgency: medium Maintainer: Christian Marillat Changed-By: Christian Marillat Closes: 1009875 Changes:

Accepted screentest 2.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 14:11:39 -0400 Source: screentest Architecture: source Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Closes: 946280 967887 Changes: screentest (2.1-1)

Accepted rsyslog 8.2204.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 20:26:20 +0200 Source: rsyslog Architecture: source Version: 8.2204.0-1 Distribution: unstable Urgency: medium Maintainer: Michael Biebl Changed-By: Michael Biebl Changes: rsyslog (8.2204.0-1) unstable;

Accepted qemu-web-desktop 22.04.17+ds1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 14:49:22 +0200 Source: qemu-web-desktop Architecture: source Version: 22.04.17+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Roland Mas Changes:

Accepted unbound 1.15.0-2 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 20:39:12 +0300 Source: unbound Architecture: source Version: 1.15.0-2 Distribution: experimental Urgency: medium Maintainer: unbound packagers Changed-By: Michael Tokarev Closes: 828699 900751 903390 931583

Accepted screentest 2.0-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 13:36:57 -0400 Source: screentest Architecture: source Version: 2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Closes: 965813 999297 1009826 Changes: screentest

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 06:51:16PM +0200, Jonas Smedegaard wrote: > > > > > When I install systems, I consider non-free blobs more risky > > > > > than other code. > > > > Do you consider loadable non-free blobs more risky than their > > > > older versions soldered onto the hardware? > > > > >

Accepted findutils 4.9.0-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 19:17:31 +0200 Source: findutils Architecture: source Version: 4.9.0-3 Distribution: unstable Urgency: low Maintainer: Andreas Metzler Changed-By: Andreas Metzler Closes: 1009874 Changes: findutils (4.9.0-3)

Accepted asql 1.6-1.2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Apr 2022 13:40:34 -0300 Source: asql Architecture: source Version: 1.6-1.2 Distribution: unstable Urgency: medium Maintainer: Steve Kemp Changed-By: Joao Eriberto Mota Filho Closes: 965418 999113 Changes: asql (1.6-1.2)

Re: Firmware - what are we going to do about it?

Jonas Smedegaard writes: > Now, some may argue that I am describing a case for package pinning > here, and that *might* be true but I don't know that yet - because the > proposed change to the system does not exist yet so I cannot really know > that yet. Possibly the implementation will be so

Re: Firmware - what are we going to do about it?

On Tue, 2022-04-19 at 18:51 +0200, Jonas Smedegaard wrote: > I notice that you shift the conversation topic from *upgrading* > firmware to *introducing* firmware. > > I already mentioned that I would sometimes upgrade to newer firmware, > which I mean to imply that yes I would sometimes dare to

Accepted odil 0.12.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 17:36:06 +0200 Source: odil Architecture: source Version: 0.12.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Julien Lamy Changes: odil (0.12.2-1) UNRELEASED;

Re: Keep both images but stop pretending no-free is unofficial

On Tue, 19 Apr 2022 08:21:10 -0600, Sam Hartman wrote: >One valuable suggestion was to make sure users could easily select >freedom if that's what they wanted. >So I think a free installation image is important. Would that not be possible by having an image WITH firmware and an installer asking

Re: Firmware - what are we going to do about it?

On Tue, 19 Apr 2022, Andrey Rahmatullin wrote: On Tue, Apr 19, 2022 at 04:30:44PM +0100, Tim Woodall wrote: On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: When I install systems, I consider non-free blobs more risky than other code. Do you consider loadable non-free blobs

Re: Firmware - what are we going to do about it?

Quoting Andrey Rahmatullin (2022-04-19 18:01:10) > On Tue, Apr 19, 2022 at 04:30:44PM +0100, Tim Woodall wrote: > > > On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: > > > > When I install systems, I consider non-free blobs more risky > > > > than other code. > > > Do you

Accepted thrift 0.16.0-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 17:08:21 +0200 Source: thrift Architecture: source Version: 0.16.0-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1008810 Changes:

Re: Firmware - what are we going to do about it?

> > My laptop requires the non-free binary blobs for WiFi, AMD GPU and HDMI > Sound. I think making the non-free images easier to find is a good idea. I > didn't know they even existed until I got this new laptop and nothing was > working with the regular installer. Placing the non-free and

Accepted xmltv 1.1.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 15:31:59 +0100 Source: xmltv Architecture: source Version: 1.1.2-1 Distribution: unstable Urgency: medium Maintainer: Nick Morrott Changed-By: Nick Morrott Changes: xmltv (1.1.2-1) unstable; urgency=medium .

Accepted parted 3.5-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 17:05:20 +0100 Source: parted Architecture: source Version: 3.5-1 Distribution: unstable Urgency: medium Maintainer: Parted Maintainer Team Changed-By: Colin Watson Changes: parted (3.5-1) unstable;

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 04:30:44PM +0100, Tim Woodall wrote: > > On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: > > > When I install systems, I consider non-free blobs more risky than other > > > code. > > Do you consider loadable non-free blobs more risky than their older > >

Accepted node-escape-html 1.0.3+~1.0.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 17 Apr 2022 06:15:58 -0400 Source: node-escape-html Architecture: source Version: 1.0.3+~1.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Michael Ikwuegbu Changes:

Re: Firmware - what are we going to do about it?

On Tue, 19 Apr 2022, Andrey Rahmatullin wrote: On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: When I install systems, I consider non-free blobs more risky than other code. Do you consider loadable non-free blobs more risky than their older versions soldered onto the

Bug#1009868: ITP: node-openurl -- Open a URL via the operating system

Package: wnpp Severity: wishlist Owner: Michael Ikwuegbu X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-openurl Version : 1.1.1 Upstream Author : Axel Rauschmayer * URL : https://github.com/rauschma/openurl#readme * License

Accepted gspell 1.10.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 10:38:03 -0400 Source: gspell Built-For-Profiles: noudeb Architecture: source Version: 1.10.0-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Changes:

Accepted amtk 5.3.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 10:32:45 -0400 Source: amtk Built-For-Profiles: noudeb Architecture: source Version: 5.3.2-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 993922

Accepted mutter 42.0-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 11:54:56 +0100 Source: mutter Architecture: source Version: 42.0-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 1008998 Changes: mutter (42.0-4)

Accepted lutris 0.5.10.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 16:20:58 +0200 Source: lutris Architecture: source Version: 0.5.10.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Stephan Lachnit Closes: 1009160 Changes: lutris

Accepted libaio 0.3.113-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 15:57:07 +0200 Source: libaio Architecture: source Version: 0.3.113-2 Distribution: unstable Urgency: medium Maintainer: Guillem Jover Changed-By: Guillem Jover Changes: libaio (0.3.113-2) unstable;

Accepted gnome-shell 42.0-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 12:28:27 +0100 Source: gnome-shell Architecture: source Version: 42.0-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 869230 Changes: gnome-shell

Keep both images but stop pretending no-free is unofficial

Steve> 3. We could stop pretending that the non-free images are Steve> unofficial, and maybe move them alongside the normal free Steve> images so they're published together. This would make them Steve> easier to find for people that need them, but is likely to Steve> cause

Re: Firmware - what are we going to do about it?

Quoting Andrey Rahmatullin (2022-04-19 14:47:27) > On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: > > When I install systems, I consider non-free blobs more risky than > > other code. > Do you consider loadable non-free blobs more risky than their older > versions soldered

Accepted octave-stk 2.7.0-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 15:10:14 +0200 Source: octave-stk Architecture: source Version: 2.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Sébastien Villemot Closes: 1009136 Changes: octave-stk

Accepted hmat-oss 1.7.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 15:08:33 +0200 Source: hmat-oss Architecture: source Version: 1.7.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Pierre Gruet Changes: hmat-oss (1.7.1-2) unstable;

Accepted fonts-junicode 2+git20220419+ds-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 14:24:50 +0200 Source: fonts-junicode Architecture: source Version: 2+git20220419+ds-1 Distribution: experimental Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Gürkan Myczko Changes:

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: > When I install systems, I consider non-free blobs more risky than other > code. Do you consider loadable non-free blobs more risky than their older versions soldered onto the hardware? > When I (sometimes, but not always¹)

Accepted uif 1.99.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 13:45:36 +0200 Source: uif Architecture: source Version: 1.99.0-1 Distribution: unstable Urgency: medium Maintainer: Mike Gabriel Changed-By: Mike Gabriel Changes: uif (1.99.0-1) unstable; urgency=medium . *

Re: Firmware - what are we going to do about it?

Quoting intrigeri (2022-04-19 13:20:19) > Jonas Smedegaard (2022-04-19): > > In other words: Please let's take this is multiple steps, first > > being to distinguish non-free firmware from other non-free code, > > without deciding yet exactly how strongly we then allow that new > > section to

Re: Firmware - what are we going to do about it?

On 2022-04-19 01:27:46 +0100 (+0100), Steve McIntyre wrote: [...] > Along with adding non-free firmware onto media, when the installer > (or live image) runs, we should make it clear exactly which > firmware packages have been used/installed to support detected > hardware. We could link to docs

Accepted r-zoo 1.8-10-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 06:53:27 -0500 Source: r-zoo Architecture: source Version: 1.8-10-1 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel Changes: r-zoo (1.8-10-1) unstable;

Accepted libsdl2 2.0.22~rc1+git20220418+dfsg-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 10:54:50 +0100 Source: libsdl2 Architecture: source Version: 2.0.22~rc1+git20220418+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian SDL packages maintainers Changed-By: Simon McVittie

Accepted jsxgraph 1.4.3+dfsg1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 12:43:03 +0200 Source: jsxgraph Architecture: source Version: 1.4.3+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Changes: jsxgraph (1.4.3+dfsg1-1)

Accepted evince 42.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Apr 2022 09:23:50 -0400 Source: evince Built-For-Profiles: noudeb Architecture: source Version: 42.2-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Changes: evince

Re: Firmware - what are we going to do about it?

On 2022-04-19 12:41, Jonas Smedegaard wrote: > Quoting Christian Kastner (2022-04-19 11:33:30) >> Here's a somewhat radical idea: I propose that we make option (1) and >> (2) conditional on all Debian infra switching to hardware entirely >> free of binary firmware/microcode blobs. >> >> Because

Accepted node-optimist 0.6.1+~0.0.30-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 13:28:24 +0200 Source: node-optimist Architecture: source Version: 0.6.1+~0.0.30-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1009602 Changes:

Accepted node-browser-unpack 1.4.2-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 13:32:04 +0200 Source: node-browser-unpack Architecture: source Version: 1.4.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1009577 Changes:

Accepted nbdkit 1.30.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 13:35:02 +0200 Source: nbdkit Architecture: source Version: 1.30.3-1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Changes: nbdkit (1.30.3-1) unstable; urgency=medium

Accepted cjose 0.6.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 13:24:38 +0200 Source: cjose Architecture: source Version: 0.6.2-1 Distribution: unstable Urgency: medium Maintainer: Moritz Schlarb Changed-By: Moritz Schlarb Changes: cjose (0.6.2-1) unstable; urgency=medium

Re: Firmware - what are we going to do about it?

Hi, Jonas Smedegaard (2022-04-19): > In other words: Please let's take this is multiple steps, first being to > distinguish non-free firmware from other non-free code, without deciding > yet exactly how strongly we then allow that new section to be integrated > with our "pure" parts. I tend

Accepted dynare 5.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 12:47:59 +0200 Source: dynare Architecture: source Version: 5.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Sébastien Villemot Closes: 1009130 Changes: dynare (5.1-2)

Re: Re: Concerns about Security of packages in Debain OS and the Operating system itself.

> Do you have a publication of that analysis? I was thinking the same > about the organization of Debian for some time but never did analysis > or compared it to other distros. i found it here http://lkcl.net/reports/wot/ it's dated 2017 (not a bad guess, 4 years). please bear in mind, the

Re: Firmware - what are we going to do about it?

Quoting Christian Kastner (2022-04-19 11:33:30) > On 2022-04-19 02:27, Steve McIntyre wrote: > > 1. Keep the existing setup. It's horrible, but maybe it's the best > > we can do? (I hope not!)> > > 2. We could just stop providing the non-free unofficial images > > altogether. That's

Accepted pysoundfile 0.10.3+post1-2~exp1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 12:02:40 +0200 Source: pysoundfile Architecture: source Version: 0.10.3+post1-2~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU)

Accepted starjava-task 0.2+2022.03.17-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 12:06:18 +0200 Source: starjava-task Architecture: source Version: 0.2+2022.03.17-1 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Changes: starjava-task

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 11:33:30AM +0200, Christian Kastner wrote: > Hi Steve, > > thank you for bringing this up. > > On 2022-04-19 02:27, Steve McIntyre wrote: > > 1. Keep the existing setup. It's horrible, but maybe it's the best we can > > do? > > (I hope not!)> > > 2. We could just

Accepted rust-gif 0.11.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 09:45:35 + Source: rust-gif Architecture: source Version: 0.11.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Changes: rust-gif (0.11.3-1)

Re: Firmware - what are we going to do about it?

Hi Steve, * Steve McIntyre [2022-04-19 01:27]: TL;DR: firmware support in Debian sucks, and we need to change this. See the "My preference, and rationale" Section below. [...] 5. We could split out the non-free firmware packages into a new non-free-firmware component in the archive, and

Accepted ableton-link 3.0.5+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 11:48:12 +0200 Source: ableton-link Architecture: source Version: 3.0.5+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Changes:

Re: Firmware - what are we going to do about it?

w...@debian.org wrote: > >Also, drivers and firmware are different things. *Totally*. This is one of my pet peeves - many *many* people confuse the two and talk about "non-free drivers" in Debian when they actually mean firmware... ARGH. -- Steve McIntyre, Cambridge, UK.

Re: Firmware - what are we going to do about it?

Hi Steve, thank you for bringing this up. On 2022-04-19 02:27, Steve McIntyre wrote: > 1. Keep the existing setup. It's horrible, but maybe it's the best we can do? > (I hope not!)> > 2. We could just stop providing the non-free unofficial images altogether. > That's not really a

Re: Firmware - what are we going to do about it?

On Tue, 2022-04-19 at 01:27 +0100, Steve McIntyre wrote: > What would I choose to do? My personal preference would be to go with option > 5: > split the non-free firmware into a special new component and include that on > official media. This is a great write-up and proposal, thank you very much

Accepted starjava-util 1.0+2022.04.04-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 10:46:57 +0200 Source: starjava-util Architecture: source Version: 1.0+2022.04.04-1 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Changes: starjava-util

Accepted starjava-array 0.2+2022.03.23-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 10:50:58 +0200 Source: starjava-array Architecture: source Version: 0.2+2022.03.23-1 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Changes: starjava-array

Accepted sonic-visualiser 4.5-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 19 Apr 2022 11:05:51 +0200 Source: sonic-visualiser Architecture: source Version: 4.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Changes:

Accepted optee-client 3.17.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 15:27:27 +0800 Source: optee-client Architecture: source Version: 3.17.0-1 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Ying-Chun Liu (PaulLiu) Changes: optee-client

Accepted fsspec 2022.3.0-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 08:39:29 + Source: fsspec Architecture: source Version: 2022.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Emmanuel Arias Changes: fsspec (2022.3.0-2) unstable;

Accepted vdirsyncer 0.18.0-6.1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Apr 2022 17:39:33 +0300 Source: vdirsyncer Architecture: source Version: 0.18.0-6.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Michael Tokarev Closes: 1009204 Changes: vdirsyncer

Accepted python-secretstorage 3.3.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 12:06:27 +0300 Source: python-secretstorage Architecture: source Version: 3.3.2-1 Distribution: unstable Urgency: medium Maintainer: Dmitry Shachnev Changed-By: Dmitry Shachnev Closes: 1009824 Changes:

Accepted iceoryx 2.0.2+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 11:07:51 +0200 Source: iceoryx Architecture: source Version: 2.0.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Robotics Team Changed-By: Timo Röhling Changes: iceoryx (2.0.2+dfsg-1)

Accepted h2o 2.2.5+dfsg2-6.2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 13 Apr 2022 20:41:51 + Source: h2o Architecture: source Version: 2.2.5+dfsg2-6.2 Distribution: unstable Urgency: medium Maintainer: Apollon Oikonomopoulos Changed-By: Chris Hofstaedtler Closes: 1008426 Changes: h2o

Accepted linux 5.17.3-1 (source) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Apr 2022 14:36:36 +0200 Source: linux Architecture: source Version: 5.17.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 860957 1008501 1009302 Changes:

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 10:22:15AM +0200, parodper wrote: > > 5. We could split out the non-free firmware packages into a new > > non-free-firmware component in the archive, and allow a specific > > exception > > only to allow inclusion of those packages on our official media. We > >

Re: Firmware - what are we going to do about it?

5. We could split out the non-free firmware packages into a new non-free-firmware component in the archive, and allow a specific exception only to allow inclusion of those packages on our official media. We would then generate only one set of official media, including those

Re: Firmware - what are we going to do about it?

On Apr 19, Steve McIntyre wrote: > What would I choose to do? My personal preference would be to go with option > 5: > split the non-free firmware into a special new component and include that on > official media. I agree, and actually I have been supporting this position for 20 years (time

Accepted radicale 3.1.6-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Apr 2022 09:57:25 +0200 Source: radicale Architecture: source Version: 3.1.6-2 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Changes: radicale (3.1.6-2) unstable;

  1   2   >