Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

2022-09-25 Thread Kurt Roeckx
On Sun, Sep 25, 2022 at 02:16:00AM +, Thorsten Glaser wrote: > Kurt Roeckx dixit: > > >On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote: > >> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 > >> -legacy_renegotiation -tls1 &

Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

2022-09-25 Thread Kurt Roeckx
On Sun, Sep 25, 2022 at 02:16:00AM +, Thorsten Glaser wrote: > Kurt Roeckx dixit: > > >On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote: > >> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 > >> -legacy_renegotiation -tls1 &

Bug#965041: [Pkg-openssl-devel] Bug#965041: Bug#965041: libssl3: Please stop building legacy provider

2022-09-18 Thread Kurt Roeckx
On Sun, Sep 18, 2022 at 07:09:05PM +0200, Sebastian Andrzej Siewior wrote: > On 2020-07-16 08:46:43 [+0200], Kurt Roeckx wrote: > > On Thu, Jul 16, 2020 at 03:57:17AM +0100, Dimitri John Ledkov wrote: > > > > > > openssl package could ship `.include /etc/ss

Re: vote acknowledgement not being sent

2022-09-18 Thread Kurt Roeckx
On Sun, Sep 18, 2022 at 02:34:14AM +0200, Kurt Roeckx wrote: > Vote acknowledgement are currently not being sent out. I've been looking > at it, but currently can't get it to work again. I will look at this > again in the morning. All the acknowledgement are sent out now. Kurt

vote acknowledgement not being sent

2022-09-17 Thread Kurt Roeckx
Vote acknowledgement are currently not being sent out. I've been looking at it, but currently can't get it to work again. I will look at this again in the morning. Kurt

General Resolution: Non-free firmware: First call for votes

2022-09-17 Thread Debian Project Secretary - Kurt Roeckx
Hi, This is the first call for votes for the General Resolution about non-free firmware. Voting period starts 2022-09-18 00:00:00 UTC Votes must be received by 2022-10-01 23:59:59 UTC This vote is being conducted as required by the Debian Constitution. You may see the

Draft ballot

2022-09-17 Thread Kurt Roeckx
Hi, This is the draft ballot. Voting period starts 2022-09-18 00:00:00 UTC Votes must be received by 2022-10-01 23:59:59 UTC This vote is being conducted as required by the Debian Constitution. You may see the constitution at https://www.debian.org/devel/constitution. For voting

Re: Voting period

2022-09-17 Thread Kurt Roeckx
On Fri, Sep 16, 2022 at 05:18:21PM -0700, Russ Allbery wrote: > Kurt Roeckx writes: > > > I welcome suggestion for the ballot texts. > > Tentative proposal, and the proponents of other options should jump in and > correct these. > > A: "Only one installer,

Re: Voting period

2022-09-17 Thread Kurt Roeckx
On Sat, Sep 17, 2022 at 12:28:23PM +0200, Bart Martens wrote: > On Fri, Sep 16, 2022 at 05:18:21PM -0700, Russ Allbery wrote: > > Kurt Roeckx writes: > > > > > I welcome suggestion for the ballot texts. > > > > Tentative proposal, and the pro

Voting period

2022-09-16 Thread Kurt Roeckx
Hi, I will most likely start the voting period tomorrow evening, so 2022-09-18 00:00 UTC. I did not have time to put the last option on the website, but it has enough seconds. I welcome suggestion for the ballot texts. Kurt

Re: Possible draft non-free firmware option with SC change

2022-09-16 Thread Kurt Roeckx
On Fri, Sep 16, 2022 at 04:50:41PM +, Philipp Kern wrote: > > Seconded. Thanks, Russ! The signature check failed, and the discussion period is over. Kurt

Re: new proposal: free and and non-free installers with SC change

2022-09-15 Thread Kurt Roeckx
> seconded Your message wasn't signed. Kurt

Bug#805646: [Pkg-openssl-devel] Bug#805646: Bug#805646: Package using openssl functions does not find default certificates

2022-09-13 Thread Kurt Roeckx
On Tue, Sep 13, 2022 at 06:40:19PM +0200, Sebastian Andrzej Siewior wrote: > On 2022-09-13 18:30:05 [+0200], Kurt Roeckx wrote: > > > > 3) provide a symlink from /usr/lib/ssl/cert.pem to > > > >/etc/ssl/certs/ca-certificates.crt > > > > > > Kurt, I

Bug#805646: [Pkg-openssl-devel] Bug#805646: Package using openssl functions does not find default certificates

2022-09-13 Thread Kurt Roeckx
On Tue, Sep 13, 2022 at 05:23:43PM +0200, Sebastian Andrzej Siewior wrote: > On 2016-01-04 23:50:10 [+0100], Jan Dittberner wrote: > > I don't know whether this will have negative side effects but from my point > > of view it would be nice if the openssl package would do one of the > > following

Re: Changing how we handle non-free firmware

2022-09-06 Thread Kurt Roeckx
On Tue, Sep 06, 2022 at 08:33:51PM +0200, Bart Martens wrote: > On Tue, Sep 06, 2022 at 05:26:10PM +0100, Steve McIntyre wrote: > > On Tue, Sep 06, 2022 at 06:15:21PM +0200, Bart Martens wrote: > > >On Sun, Sep 04, 2022 at 03:43:36AM +0700, Judit Foglszinger wrote: > > >> > I hereby propose the

Re: supermajority requirements and their inheritance (was: Re: Changing how we handle non-free firmware)

2022-09-06 Thread Kurt Roeckx
On Tue, Sep 06, 2022 at 08:09:15AM +0200, Ansgar wrote: > On Mon, 2022-09-05 at 21:51 +0200, Kurt Roeckx wrote: > > You can argue that the developers making the installer and live images, > > and those maintaining the website can make those decisions. You can even > > sa

Re: Changing how we handle non-free firmware

2022-09-05 Thread Kurt Roeckx
On Sun, Sep 04, 2022 at 08:00:48PM -0500, Richard Laager wrote: > > Thus, a possible precursor to an interpretive GR is that some person/group > (e.g. ftpmaster, Project Leader, TC, Secretary[1]) makes the interpretive > decision. > > If someone can make the decision, then they can be

Re: Changing how we handle non-free firmware

2022-09-04 Thread Kurt Roeckx
On Sun, Sep 04, 2022 at 09:57:45AM +0200, Tobias Frost wrote: > Hi Steve, > > On Fri, Sep 02, 2022 at 09:14:53PM +0200, Kurt Roeckx wrote: > > On Tue, Aug 30, 2022 at 03:11:25PM -0500, Richard Laager wrote: > > > > > > > I like to discussion about any

Re: Changing how we handle non-free firmware

2022-09-03 Thread Kurt Roeckx
On Tue, Aug 23, 2022 at 10:39:57AM +0200, Simon Josefsson wrote: > As far as I can tell, both Steve's and Gunnar's proposal would make > Debian less of a free software operating system than it is today. That > makes me sad. My preference for an outcome would be along the following > lines. > >

Re: Changing how we handle non-free firmware

2022-09-02 Thread Kurt Roeckx
On Tue, Aug 30, 2022 at 03:11:25PM -0500, Richard Laager wrote: > > > I like to discussion about anything related to this, so that I can at > > least get an idea what the consensus is. > > DSC 1 and DSC 5 have some implications about "the Debian system" vis-a-vis > non-free, but the plan here is

Re: Changing how we handle non-free firmware

2022-08-30 Thread Kurt Roeckx
On Tue, Aug 30, 2022 at 09:00:50PM +0100, Steve McIntyre wrote: > Hi Kurt! Let's send this signed now, > > On Sat, Aug 27, 2022 at 04:26:40PM +0200, Kurt Roeckx wrote: > >On Fri, Aug 19, 2022 at 11:26:51AM +0100, Steve McIntyre wrote: > >> Hey Wouter! > >> > &

Re: Changing how we handle non-free firmware

2022-08-30 Thread Kurt Roeckx
On Tue, Aug 30, 2022 at 03:27:46AM -0500, Richard Laager wrote: > On 8/29/22 16:02, Kurt Roeckx wrote: > > It's my current interpretation that all voting options, even if they > > might conflict with the DSC, will be on the ballot, and might not > > require a 3:1 majority. T

Re: Changing how we handle non-free firmware

2022-08-29 Thread Kurt Roeckx
On Mon, Aug 29, 2022 at 09:38:52PM +0100, Steve McIntyre wrote: > Hi Kurt! > > On Sat, Aug 27, 2022 at 04:26:40PM +0200, Kurt Roeckx wrote: > >On Fri, Aug 19, 2022 at 11:26:51AM +0100, Steve McIntyre wrote: > >> Hey Wouter! > >> > >> On Fri, Aug 19,

Re: Changing how we handle non-free firmware

2022-08-29 Thread Kurt Roeckx
On Mon, Aug 29, 2022 at 09:36:37AM +0200, Simon Josefsson wrote: > Jonas Smedegaard writes: > > > I view the official Debian install image as a component of Debian, and > > consequently if the (only) official Debian install image were to contain > > non-free bits then we would violate DSC#1. >

Re: Changing how we handle non-free firmware

2022-08-28 Thread Kurt Roeckx
On Sun, Aug 28, 2022 at 10:52:42AM +0200, Kurt Roeckx wrote: > On Sat, Aug 27, 2022 at 07:26:04PM -0700, Russ Allbery wrote: > > Kurt Roeckx writes: > > > > > That changes it from 5 to 4 seconds. It's unclear to me what I need to > > > do with the discussion per

Re: Changing how we handle non-free firmware

2022-08-28 Thread Kurt Roeckx
On Sat, Aug 27, 2022 at 07:26:04PM -0700, Russ Allbery wrote: > Kurt Roeckx writes: > > > That changes it from 5 to 4 seconds. It's unclear to me what I need to > > do with the discussion period because of this. If I process the message > > in order, I think this was ac

Re: Changing how we handle non-free firmware

2022-08-27 Thread Kurt Roeckx
On Sat, Aug 27, 2022 at 03:56:25PM +0200, Kurt Roeckx wrote: > > That changes it from 5 to 4 seconds. It's unclear to me what I need to > do with the discussion period because of this. If I process the message > in order, I think this was accepted and A.1.4 changes the discuss

Re: Changing how we handle non-free firmware

2022-08-27 Thread Kurt Roeckx
On Fri, Aug 19, 2022 at 11:26:51AM +0100, Steve McIntyre wrote: > Hey Wouter! > > On Fri, Aug 19, 2022 at 12:19:55PM +0200, Wouter Verhelst wrote: > >On Thu, Aug 18, 2022 at 08:58:21PM +0100, Steve McIntyre wrote: > >> system will *also* be configured to use the non-free-firmware > >> component

Re: Changing how we handle non-free firmware

2022-08-27 Thread Kurt Roeckx
On Fri, Aug 26, 2022 at 07:06:01AM +0200, Jonas Smedegaard wrote: > Quoting Jonas Smedegaard (2022-08-24 19:14:26) > > Quoting Bart Martens (2022-08-24 10:12:48) > > > = > > > > > > The Debian project is permitted to make distribution media (installer > > > images

Re: Changing how we handle non-free firmware

2022-08-27 Thread Kurt Roeckx
On Tue, Aug 23, 2022 at 10:56:06AM -0400, Hubert Chathi wrote: > > s/Therefor/Therefore I've adopted this change. > > Thereby re-inforcing the interpretation that any installer or image I've also changed that to reinforcing. Let me know if that's not ok. Kurt

Re: Changing how we handle non-free firmware

2022-08-27 Thread Kurt Roeckx
On Tue, Aug 23, 2022 at 10:39:57AM +0200, Simon Josefsson wrote: > As far as I can tell, both Steve's and Gunnar's proposal would make > Debian less of a free software operating system than it is today. That > makes me sad. My preference for an outcome would be along the following > lines. The

Re: Changing how we handle non-free firmware

2022-08-27 Thread Kurt Roeckx
On Mon, Aug 22, 2022 at 05:50:43PM +0200, Thomas Goirand wrote: > > Seconded. Your message was not signed. Kurt

Re: Changing how we handle non-free firmware

2022-08-27 Thread Kurt Roeckx
On Fri, Aug 19, 2022 at 07:36:17AM -0500, Devin Prater wrote: > Seconded, thanks for mentioning the accessibility aspect! > Devin Prater > r.d.t.pra...@gmail.com Your message was not signed, nor can I find you in the list of Debian Developers. So I'm not registering this as a second. There are

Re: Changing how we handle non-free firmware

2022-08-23 Thread Kurt Roeckx
On Thu, Aug 18, 2022 at 08:58:21PM +0100, Steve McIntyre wrote: > So, I propose the following: > > = > > We will include non-free firmware packages from the > "non-free-firmware" section of the Debian archive on our official > media (installer images and live

[openssl/openssl] 2bd819: Change name of parameter in documentation from sig...

2022-08-04 Thread Kurt Roeckx
Branch: refs/heads/master Home: https://github.com/openssl/openssl Commit: 2bd8190aace8109a06aff495a3e20c863ef48653 https://github.com/openssl/openssl/commit/2bd8190aace8109a06aff495a3e20c863ef48653 Author: Kurt Roeckx Date: 2022-08-04 (Thu, 04 Aug 2022) Changed paths

Bug#1016526: [Pkg-openssl-devel] Bug#1016526: openssl: Regression on mips64el throws error:1E08010C:DECODER

2022-08-02 Thread Kurt Roeckx
On Tue, Aug 02, 2022 at 12:50:05PM +0200, Jérémy Lal wrote: > Package: openssl > Version: 3.0.5-1 > Severity: normal > Control: affects -1 nodejs > > Hi, > > while building nodejs 18.6.0+dfsg-4 on mips64el, some SSL tests did regress, >

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

2022-07-19 Thread Kurt Roeckx
On Tue, Jul 19, 2022 at 06:11:23PM +0200, Diederik de Haas wrote: > According to that bug report it should be fixed with 5.19-rc6 and that > version > is available in experimental. Can you verify whether it also fixes your issue? With that version the error goes away.

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

2022-07-19 Thread Kurt Roeckx
On Tue, Jul 19, 2022 at 06:11:23PM +0200, Diederik de Haas wrote: > According to that bug report it should be fixed with 5.19-rc6 and that > version > is available in experimental. Can you verify whether it also fixes your issue? With that version the error goes away.

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

2022-07-18 Thread Kurt Roeckx
This is probably https://bugzilla.kernel.org/show_bug.cgi?id=216140 Kurt

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

2022-07-18 Thread Kurt Roeckx
This is probably https://bugzilla.kernel.org/show_bug.cgi?id=216140 Kurt

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

2022-07-18 Thread Kurt Roeckx
I tried older kernels, 5.17.3-1 didn't show it.

Bug#1015240: Acknowledgement (linux: rejecting DMA map of vmalloc memory)

2022-07-18 Thread Kurt Roeckx
I tried older kernels, 5.17.3-1 didn't show it.

Bug#1015240: linux: rejecting DMA map of vmalloc memory

2022-07-18 Thread Kurt Roeckx
Package: linux-image-5.18.0-2-amd64 Version: 5.18.5-1 Hi, I'm currently seeing this during boot: [5.632167] usb 1-14: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02 [5.632171] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.655513]

Bug#1015240: linux: rejecting DMA map of vmalloc memory

2022-07-18 Thread Kurt Roeckx
Package: linux-image-5.18.0-2-amd64 Version: 5.18.5-1 Hi, I'm currently seeing this during boot: [5.632167] usb 1-14: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02 [5.632171] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.655513]

Re: Flying out via Skopje

2022-07-17 Thread Kurt Roeckx
On Sat, Jul 16, 2022 at 04:11:20PM +0200, Enrico Zini wrote: > Hello, > > I'm looking for ferry alternatives for my trip back home, and I see > there's a reasonably priced flight to Bologna from Skopje. > > Question: how hard is it to reach Skopje? Would it be a good idea to > attempt traveling

Re: Your personalized DC22 Key Signing Party Map is now available!

2022-07-12 Thread Kurt Roeckx
On Tue, Jul 12, 2022 at 09:54:32AM +0200, Kurt Roeckx wrote: > On Tue, Jul 12, 2022 at 12:02:20AM -0500, Gunnar Wolf wrote: > > Hello world! > > > > My reports show that many of you are already enjoying the Balkans in > > Prizren, and I am very very jealous! It's just a

Re: Your personalized DC22 Key Signing Party Map is now available!

2022-07-12 Thread Kurt Roeckx
On Tue, Jul 12, 2022 at 12:02:20AM -0500, Gunnar Wolf wrote: > Hello world! > > My reports show that many of you are already enjoying the Balkans in > Prizren, and I am very very jealous! It's just a couple more days > until I pack myself together with the rest of the > very-small-form-of-cattle

Re: [SECURITY] [DSA 5173-1] linux security update

2022-07-04 Thread Kurt Roeckx
On Sun, Jul 03, 2022 at 03:49:12PM +, Ben Hutchings wrote: > > For the oldstable distribution (buster), these problems have been > fixed in version 4.19.249-2. It seems that linux-image-amd64 does not depend on linux-image-4.19.0-21-amd64 but still on linux-image-4.19.0-20-amd64, so the

Bug#995636: transition: openssl

2022-06-05 Thread Kurt Roeckx
On Sun, Jun 05, 2022 at 08:44:22PM +0200, Sebastian Andrzej Siewior wrote: > On 2022-06-05 19:42:43 [+0200], Sebastian Ramacher wrote: > > Hi Sebastian > Hi Sebastian, > > > > Otherwise I'd fear that the only other options are openssl breaking > > > libssl1.1 or renaming /etc/ssl/openssl.cnf to

Bug#995636: transition: openssl

2022-06-05 Thread Kurt Roeckx
On Sun, Jun 05, 2022 at 08:44:22PM +0200, Sebastian Andrzej Siewior wrote: > On 2022-06-05 19:42:43 [+0200], Sebastian Ramacher wrote: > > Hi Sebastian > Hi Sebastian, > > > > Otherwise I'd fear that the only other options are openssl breaking > > > libssl1.1 or renaming /etc/ssl/openssl.cnf to

Bug#995636: transition: openssl

2022-05-27 Thread Kurt Roeckx
On Thu, May 26, 2022 at 06:26:57PM +0200, Sebastian Ramacher wrote: > > That leaves #1011051. What's your view on that bug? So my understanding is that 1.1.1 doesn't understand the new configuration file and tries to load an engine (instead of a provider). We could ship a file that's comptabile

Bug#995636: transition: openssl

2022-05-27 Thread Kurt Roeckx
On Thu, May 26, 2022 at 06:26:57PM +0200, Sebastian Ramacher wrote: > > That leaves #1011051. What's your view on that bug? So my understanding is that 1.1.1 doesn't understand the new configuration file and tries to load an engine (instead of a provider). We could ship a file that's comptabile

Bug#1011243: nvidia-cuda-toolkit: Hard dependency on libssl1.1

2022-05-18 Thread Kurt Roeckx
Source: nvidia-cuda-toolkit Version: 11.4.3-2 Severity: serious Tags: sid bookworm Hi, It seems build-depends on libssl1.1 and not on libssl-dev. It also depends on libssl1.1 and doesn't transition to libssl3 on rebuild. Can you please move to using libssl3? Kurt

Bug#1011242: thrift: No depends on libssl after rebuild against OpenSSL 3.0

2022-05-18 Thread Kurt Roeckx
Source: thrift Version: 0.16.0-5 Severity: serious Tags: sid bookworm Hi, It seems that thrift does not depend on libssl after being rebuild against OpenSSL 3.0, but did depend on libssl1.1. Kurt

Bug#1011243: nvidia-cuda-toolkit: Hard dependency on libssl1.1

2022-05-18 Thread Kurt Roeckx
Source: nvidia-cuda-toolkit Version: 11.4.3-2 Severity: serious Tags: sid bookworm Hi, It seems build-depends on libssl1.1 and not on libssl-dev. It also depends on libssl1.1 and doesn't transition to libssl3 on rebuild. Can you please move to using libssl3? Kurt

Bug#1011242: thrift: No depends on libssl after rebuild against OpenSSL 3.0

2022-05-18 Thread Kurt Roeckx
Source: thrift Version: 0.16.0-5 Severity: serious Tags: sid bookworm Hi, It seems that thrift does not depend on libssl after being rebuild against OpenSSL 3.0, but did depend on libssl1.1. Kurt

Bug#1010958: sscg FTBFS with OpenSSL 3.0.3

2022-05-15 Thread Kurt Roeckx
It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247

Bug#1010958: sscg FTBFS with OpenSSL 3.0.3

2022-05-15 Thread Kurt Roeckx
It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

2022-05-11 Thread Kurt Roeckx
On Wed, May 11, 2022 at 07:25:45PM +0300, Andriy Grytsenko wrote: > >You can test it by installing the version from unstable. > > It is not in unstable yet, see That should have said experimental. Kurt

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

2022-05-11 Thread Kurt Roeckx
On Wed, May 11, 2022 at 07:25:45PM +0300, Andriy Grytsenko wrote: > >You can test it by installing the version from unstable. > > It is not in unstable yet, see That should have said experimental. Kurt

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

2022-05-11 Thread Kurt Roeckx
tags 996276 - bookworm-ignore experimental + bookworm sid thanks This is affecting the bookworm release. The release managers approved the upload to unstable and marked it as serious/release critical. You can test it by installing the version from unstable.

Bug#996276: foxeye: FTBFS with OpenSSL 3.0

2022-05-11 Thread Kurt Roeckx
tags 996276 - bookworm-ignore experimental + bookworm sid thanks This is affecting the bookworm release. The release managers approved the upload to unstable and marked it as serious/release critical. You can test it by installing the version from unstable.

Debian Project Leader Election 2022 Results

2022-04-21 Thread Debian Project Secretary - Kurt Roeckx
|455 | 89 | 44.695 | 9.50706 | | 2022 | 1023 | 47.976 | 363 |354 | 73 | 34.604 | 7.37860 | |--+--++---++-++---| Kurt Roeckx Debian Project Secretary signature.asc Description: PGP signature

Debian Project Leader Election 2022 Results

2022-04-21 Thread Debian Project Secretary - Kurt Roeckx
|455 | 89 | 44.695 | 9.50706 | | 2022 | 1023 | 47.976 | 363 |354 | 73 | 34.604 | 7.37860 | |--+--++---++-++---| Kurt Roeckx Debian Project Secretary signature.asc Description: PGP signature

Debian Project Leader election 2022: First call for votes

2022-04-02 Thread Debian Project Secretary - Kurt Roeckx
Hi, This is the first call for votes for the 2022 Debian Project Leader election. Voting period starts 2022-04-03 00:00:00 UTC Votes must be received by 2022-04-16 23:59:59 UTC This vote is being conducted as required by the Debian Constitution. You may see the constitution at

DPL vote draft ballot

2022-04-02 Thread Kurt Roeckx
Hi, Here is the draft ballot. Voting period starts 2022-04-03 00:00:00 UTC Votes must be received by 2022-04-16 23:59:59 UTC This vote is being conducted as required by the Debian Constitution. You may see the constitution at https://www.debian.org/devel/constitution. For voting

Bug#692917: printer-driver-escpr: color error on armel

2022-04-02 Thread Kurt Roeckx
On Sat, Apr 02, 2022 at 11:19:26AM +0200, Thorsten Alteholz wrote: > Hi Kurt and Patrik, > > thanks a lot for your reports. Can you please check whether the problem > still exists after a few new upstream versions? Both the printer and the armel server have been replaced in the mean time. Kurt

Bug#692917: printer-driver-escpr: color error on armel

2022-04-02 Thread Kurt Roeckx
On Sat, Apr 02, 2022 at 11:19:26AM +0200, Thorsten Alteholz wrote: > Hi Kurt and Patrik, > > thanks a lot for your reports. Can you please check whether the problem > still exists after a few new upstream versions? Both the printer and the armel server have been replaced in the mean time. Kurt

DPL voting period

2022-04-01 Thread Kurt Roeckx
Hi, The voting period should have be open by now. It will be delayed by 1 day. Kurt

Re: Results for Voting secrecy

2022-03-29 Thread Kurt Roeckx
On Tue, Mar 29, 2022 at 03:54:28PM -0700, Russ Allbery wrote: > > My understanding of the implications of this process (and Kurt is > authoritative here, of course) is that if you rank NOTA equally with an > option, that vote is not part of V(A,D) or V(D,A) since neither option is > preferred

General Resolution: Voting secrecy result

2022-03-29 Thread Debian Project Secretary - Kurt Roeckx
Hi, The result of the General Resolution is: Option 2 "Hide identities of Developers casting a particular vote and allow verification" The details of the results are available at: https://www.debian.org/vote/2022/vote_001 Kurt Roeckx Debian Project Secretary signature.asc Descri

General Resolution: Voting secrecy result

2022-03-29 Thread Debian Project Secretary - Kurt Roeckx
Hi, The result of the General Resolution is: Option 2 "Hide identities of Developers casting a particular vote and allow verification" The details of the results are available at: https://www.debian.org/vote/2022/vote_001 Kurt Roeckx Debian Project Secretary signature.asc Descri

Re: Results for Voting secrecy

2022-03-29 Thread Kurt Roeckx
On Mon, Mar 28, 2022 at 12:26:51PM -0600, Sam Hartman wrote: > >>>>> "Kurt" == Kurt Roeckx writes: > > > >> It inadvertently weakened the constitutional protection against > >> changes to the constitution. > > Kurt> I

Re: Results for Voting secrecy

2022-03-28 Thread Kurt Roeckx
On Sun, Mar 27, 2022 at 01:30:53PM -0700, Felix Lechner wrote: > Hi Kurt, > > On Sun, Mar 27, 2022 at 11:03 AM Kurt Roeckx wrote: > > > > Clearly people don't think it's identical, otherwise it would not have > > been an option, or people would have voted it equally

Re: Results for Voting secrecy

2022-03-27 Thread Kurt Roeckx
On Sun, Mar 27, 2022 at 10:31:44AM -0700, felix.lech...@lease-up.com wrote: > Dear Mr. Secretary, > > As a Second for the winning Option 2, I was personally happy with last > night's vote, but I nonetheless object to your certification of these > tentative results: > > > Option 2 defeats Option

Re: Question about voting when the key on the debian keyring is expired...

2022-03-23 Thread Kurt Roeckx
On Wed, Mar 23, 2022 at 12:22:09AM -0400, Theodore Ts'o wrote: > Apologies for this administrative question, but we have a couple of > votes active at the moment, and so inquiring minds want to know. > > Due to an oversight, I managed to forget to update my GPG subkey's > expiration date. I've

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 10:13:25PM +0100, Sebastian Andrzej Siewior wrote: > On 2022-03-22 21:47:52 [+0100], Kurt Roeckx wrote: > > On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote: > > > OpenSSL signature algorith

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 10:13:25PM +0100, Sebastian Andrzej Siewior wrote: > On 2022-03-22 21:47:52 [+0100], Kurt Roeckx wrote: > > On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote: > > > OpenSSL signature algorith

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote: > OpenSSL signature algorithm check tightening > = > > The OpenSSL update included in this point release includes a change to > ensure that the requested signature algorithm is supported

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote: > OpenSSL signature algorithm check tightening > = > > The OpenSSL update included in this point release includes a change to > ensure that the requested signature algorithm is supported

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote: > Is the note below accurate? Yes. Kurt

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote: > Is the note below accurate? Yes. Kurt

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 07:37:00PM +, Adam D. Barratt wrote: > On Mon, 2022-03-21 at 00:12 +0100, Sebastian Andrzej Siewior wrote: > > The change in openssl is commit > >cc7c6eb8135b ("Check that the default signature type is allowed") > > > > Before the commit in question it connects as:

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-22 Thread Kurt Roeckx
On Tue, Mar 22, 2022 at 07:37:00PM +, Adam D. Barratt wrote: > On Mon, 2022-03-21 at 00:12 +0100, Sebastian Andrzej Siewior wrote: > > The change in openssl is commit > >cc7c6eb8135b ("Check that the default signature type is allowed") > > > > Before the commit in question it connects as:

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-20 Thread Kurt Roeckx
On Mon, Mar 21, 2022 at 12:12:11AM +0100, Sebastian Andrzej Siewior wrote: > > The change in openssl is commit >cc7c6eb8135b ("Check that the default signature type is allowed") So that's: commit cc7c6eb8135be665d0acc176a5963e1eaf52e4e2 Author: Kurt Roeckx Date: Thu

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-20 Thread Kurt Roeckx
On Mon, Mar 21, 2022 at 12:12:11AM +0100, Sebastian Andrzej Siewior wrote: > > The change in openssl is commit >cc7c6eb8135b ("Check that the default signature type is allowed") So that's: commit cc7c6eb8135be665d0acc176a5963e1eaf52e4e2 Author: Kurt Roeckx Date: Thu

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-20 Thread Kurt Roeckx
On Sun, Mar 20, 2022 at 10:00:15PM +0100, Paul Gevers wrote: > Dear Sebastian, Kurt, > > On 19-03-2022 12:33, Adam D Barratt wrote: > > Upload details > > == > > > > Package: openssl > > Version: 1.1.1n-0+deb10u1 > > > > Explanation: new upstream release > > We're seeing a

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

2022-03-20 Thread Kurt Roeckx
On Sun, Mar 20, 2022 at 10:00:15PM +0100, Paul Gevers wrote: > Dear Sebastian, Kurt, > > On 19-03-2022 12:33, Adam D Barratt wrote: > > Upload details > > == > > > > Package: openssl > > Version: 1.1.1n-0+deb10u1 > > > > Explanation: new upstream release > > We're seeing a

Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

2022-03-18 Thread Kurt Roeckx
On Fri, Mar 18, 2022 at 10:22:57PM +0100, Sebastian Andrzej Siewior wrote: > On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote: > > Boo. Hope you're doing better. > > Thanks, yes. > > > > I would also do the upload for Buster, would that work? I remember > > > that > > > the packages, that

Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

2022-03-18 Thread Kurt Roeckx
On Fri, Mar 18, 2022 at 10:22:57PM +0100, Sebastian Andrzej Siewior wrote: > On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote: > > Boo. Hope you're doing better. > > Thanks, yes. > > > > I would also do the upload for Buster, would that work? I remember > > > that > > > the packages, that

Re: Bug#1003484: bullseye-pu: package openssl/1.1.1m-0+deb11u1

2022-03-18 Thread Kurt Roeckx
On Fri, Mar 18, 2022 at 10:22:57PM +0100, Sebastian Andrzej Siewior wrote: > On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote: > > Boo. Hope you're doing better. > > Thanks, yes. > > > > I would also do the upload for Buster, would that work? I remember > > > that > > > the packages, that

Re: Debian Project Leader Elections 2022: Candidates

2022-03-16 Thread Kurt Roeckx
On Tue, Mar 15, 2022 at 04:31:38PM +0100, Kurt Roeckx - Debian Project Secretary wrote: > We're now into the campaigning period. We have 3 candidates this > year: > - Felix Lechner > - Jonathan Carter > - Hideki Yamane > > I will make his platforms available when I have rece

Debian Project Leader Elections 2022: Candidates

2022-03-15 Thread Kurt Roeckx - Debian Project Secretary
We're now into the campaigning period. We have 3 candidates this year: - Felix Lechner - Jonathan Carter - Hideki Yamane I will make his platforms available when I have received them at: https://www.debian.org/vote/2022/platforms/ Kurt Roeckx Debian Project Secretary signature.asc

General Resolution: Voting secrecy: First call for votes: corrected ballot

2022-03-13 Thread Debian Project Secretary - Kurt Roeckx
Hi, A part of the ballot option in choice 2 was missing. Here is the corrected ballot. Voting period starts 2022-03-13 00:00:00 UTC Votes must be received by 2022-03-26 23:59:59 UTC The following ballot is for voting on changing the resolution process. This vote is being

General Resolution: Voting secrecy: First call for votes

2022-03-12 Thread Debian Project Secretary - Kurt Roeckx
Hi, This is the first call for votes on the General Resolution about voting secrecy. Voting period starts 2022-03-13 00:00:00 UTC Votes must be received by 2022-03-26 23:59:59 UTC The following ballot is for voting on changing the resolution process. This vote is being conducted

Re: Draft ballot voting secrecy GR

2022-03-12 Thread Kurt Roeckx
An other update: Voting period starts 2022-03-13 00:00:00 UTC Votes must be received by 2022-03-26 23:59:59 UTC The following ballot is for voting on changing the resolution process. This vote is being conducted as required by the Debian Constitution. You may see the constitution

Re: Draft ballot voting secrecy GR

2022-03-12 Thread Kurt Roeckx
Updated ballot: Voting period starts 2022-03-13 00:00:00 UTC Votes must be received by 2022-03-26 23:59:59 UTC The following ballot is for voting on changing the resolution process. This vote is being conducted as required by the Debian Constitution. You may see the constitution

Draft ballot voting secrecy GR

2022-03-12 Thread Kurt Roeckx
Here is the draft ballot: Voting period starts 2022-03-13 00:00:00 UTC Votes must be received by 2022-03-26 23:59:59 UTC The following ballot is for voting on changing the resolution process. This vote is being conducted as required by the Debian Constitution. You may see the

Re: Ballot option 2 - Merely hide Identities of Developers Casting a Particular Vote and allow verification

2022-03-12 Thread Kurt Roeckx
On Mon, Mar 07, 2022 at 03:12:57PM -0700, Sam Hartman wrote: > > "Judit" == Judit Foglszinger writes: > > >> I think it would be clearer to add "that" between "confirm" and > >> "their": > >> > >> {+ public, but developers will be given an option to confirm that > >>

Re: Secure, Secret, and Publicly Verifiable Voting

2022-03-09 Thread Kurt Roeckx
On Wed, Mar 09, 2022 at 07:33:05PM +, Bill Allombert wrote: > On Sun, Mar 06, 2022 at 11:26:28AM -0800, Russ Allbery wrote: > > "Barak A. Pearlmutter" writes: > > > > > In the discussion of the "voting secrecy" resolution, people seem to > > > have assumed that it is impossible for a voting

<    1   2   3   4   5   6   7   8   9   10   >