|
|--+--++---++-++---|
Kurt Roeckx
Debian Project Secretary
signature.asc
Description: PGP signature
|
|--+--++---++-++---|
Kurt Roeckx
Debian Project Secretary
signature.asc
Description: PGP signature
There might be a related change that doesn't allow restarting the operation
with the same context without setting things up again.
There might be a related change that doesn't allow restarting the operation
with the same context without setting things up again.
Hi,
This is the fist call for votes for the DPL election of 2024.
Voting period starts 2024-04-06 00:00:00 UTC
Votes must be received by 2024-04-19 23:59:59 UTC
This vote is being conducted as required by the Debian Constitution.
You may see the constitution at
Here is the draft ballot:
Voting period starts 2024-04-06 00:00:00 UTC
Votes must be received by 2024-04-19 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
We're now into the campaigning period. We have 2 candidates this year:
- Andreas Tille
- Sruthi Chandran
I will make the platforms available when I have received them at:
https://www.debian.org/vote/2024/platforms/
Kurt Roeckx
Debian Project Secretary
signature.asc
Description: PGP signature
Source: gcc-14
Severity: wishlist
Please consider enabling frame pointers on 64 bit arches. See:
https://www.brendangregg.com/blog/2024-03-17/the-return-of-the-frame-pointers.html
Kurt
Source: gcc-14
Severity: wishlist
Please consider enabling frame pointers on 64 bit arches. See:
https://www.brendangregg.com/blog/2024-03-17/the-return-of-the-frame-pointers.html
Kurt
round 2024-03-23.
Details and results for the vote will be published at:
http://www.debian.org/vote/2024/vote_001
Please make sure that nominations are sent to (or cc:'d to)
debian-vote, and are cryptographically signed.
Kurt Roeckx
Debian Project Secretary
signature.asc
Description: PGP signature
Hi,
It's unclear to me what you're reporting as error. The connection seems to be
working. The verification of the certificate seems to fail. It seems you have
your own CA, but the CA is not trusted because it's not in the certificate
store.
Kurt
Hi,
This is the schedule for the DPL election:
Nomination period: Saturday 2024-03-09 Friday 2024-03-15
Campaigning period: Saturday 2024-03-16 Friday 2024-04-05
Voting period: Saturday 2024-04-06 Friday 2024-04-19
Kurt
Hi,
This is the first call for votes abouti:
Statement about the EU Legislation "Cyber Resilience Act and Product Liability
Directive"
Voting period starts 2023-12-09 00:00:00 UTC
Votes must be received by 2023-12-22 23:59:59 UTC
This vote is being conducted as required by the
On Wed, Nov 29, 2023 at 10:39:38PM +0100, Kurt Roeckx wrote:
> Hi,
>
> I've updated the page at https://www.debian.org/vote/2023/vote_002 which
> the current status.
Here is the draft ballot:
Voting period starts 2023-12-09 00:00:00 UTC
Votes must be received by 2023
e next line. But it
might also just be fine. There is at least some code that only checks
the first few words or something like that.
Kurt
> Am 08.12.23 um 20:40 schrieb Kurt Roeckx:
> > The CRA and PLD will be detrimental to open source software
>
Kurt
On Thu, Dec 07, 2023 at 04:43:09PM +0100, Bart Martens wrote:
> May I suggest for proposal C:
> "The EU should not overrule DFSG 6 and FOSS licenses"
>
>
> On Thu, Dec 07, 2023 at 07:19:44AM +0300, Kurt Roeckx wrote:
> > Can people make suggestions for the bal
Can people make suggestions for the ballot options text?
Kurt
On November 30, 2023 12:39:38 AM GMT+03:00, Kurt Roeckx wrote:
>Hi,
>
>I've updated the page at https://www.debian.org/vote/2023/vote_002 which
>the current status.
>
>We're at the maximum discussion period of 3
Hi,
I've updated the page at https://www.debian.org/vote/2023/vote_002 which
the current status.
We're at the maximum discussion period of 3 weeks, so the vote will
probably start the 10th of December.
Kurt
On Wed, Nov 22, 2023 at 07:16:48PM +0100, Bart Martens wrote:
> Hello, I hereby welcome seconds for adding this text to 2023/vote_002
> as a separate proposal.
I'm currently counting 3 seconds for this.
Kurt
On Sun, Nov 19, 2023 at 11:21:47PM +, Luca Boccassi wrote:
> Second version, taking into account feedback. Looking for seconds at
> this point:
So I'm still only counting 4 seconds at this point.
Kurt
On Tue, Nov 21, 2023 at 10:26:09PM +0100, Bill Allombert wrote:
> Dear Debian voters,
>
> While Debian has stakes in the CRA, and should issue a statement if
> only to show we exists, I am quite sure that a GR is not necessary for Debian
> to issue such statement, and I am quite unconvinced the
On Mon, Nov 20, 2023 at 12:40:58AM +0100, Aigars Mahinovs wrote:
> I second adding this version to the vote
I'm getting a bad signature on this.
> On Mon, 20 Nov 2023 at 00:22, Luca Boccassi wrote:
> Second version, taking into account feedback. Looking for seconds at
> this point:
Maybe
On Sun, Nov 12, 2023 at 01:03:38PM -0600, Simon Quigley wrote:
> Just for good measure, seconded.
This is the 5th second.
Kurt
You seem to have moved the config file for some reason. Are you sure you wanted
to do that?
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
Can I suggest that if you file a few bugs and add some information in it so
that maybe someone can look at it? If it only affects one architecture, send a
mail to that list asking for help.
Kurt
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>
> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
On June 18, 2023 11:37:55 PM GMT+02:00, Rob Landley wrote:
>On 6/18/23 14:58, Rene Engelhard wrote:
>>> Three years ago Samba maintainer Jeremy Allison lamented that "Both GPLv3
>>> and
>>> the AGPL have been rejected soundly by most developers" and talked about
>>> how he
>>> regretted the
|455 | 89 | 44.695 | 9.50706 |
| 2022 | 1023 | 47.976 | 363 |354 | 73 | 34.604 | 7.37860 |
| 2023 | 996 | 47.339 | 283 |279 | 71 | 28.012 | 5.89363 |
|--+--++---++-++---|
Kurt Roeckx
Debian Project Secretary
|455 | 89 | 44.695 | 9.50706 |
| 2022 | 1023 | 47.976 | 363 |354 | 73 | 34.604 | 7.37860 |
| 2023 | 996 | 47.339 | 283 |279 | 71 | 28.012 | 5.89363 |
|--+--++---++-++---|
Kurt Roeckx
Debian Project Secretary
This seems to be caused by a missing build-depends. If I build it
locally, I do get support for 32 bit builds.
On Sat, Apr 01, 2023 at 02:38:06AM +0200, Kurt Roeckx wrote:
> Hi,
>
> It seems something broke devotee, as usual. I've stopped the
> processing of the mails, it will not send any reply. But you
> can send your vote and it will be processed later.
The ACKs should all be sent out now.
Kurt
Hi,
It seems something broke devotee, as usual. I've stopped the
processing of the mails, it will not send any reply. But you
can send your vote and it will be processed later.
Kurt
Hi,
Here is the draft ballot.
Voting period starts 2023-04-01 00:00:00 UTC
Votes must be received by 2023-04-14 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
We're now into the campaigning period. We have 1 candidate this
year:
- Jonathan Carter
The platform is available at:
https://www.debian.org/vote/2023/platforms/
Kurt Roeckx
Debian Project Secretary
signature.asc
Description: PGP signature
Hi,
Is the issue that with older glibc versions, it was silently casted
to a 32 bit value, but now that glibc supports 64 bit, it knows
it can't represent it, and gives an error?
Maybe for bookworm, we should just ignore the test error?
Kurt
Hi,
Is the issue that with older glibc versions, it was silently casted
to a 32 bit value, but now that glibc supports 64 bit, it knows
it can't represent it, and gives an error?
Maybe for bookworm, we should just ignore the test error?
Kurt
Hi,
Are you waiting for something before uploading this fix?
Kurt
Hi,
Are you waiting for something before uploading this fix?
Kurt
round 2023-03-19.
Details and results for the vote will be published at:
http://www.debian.org/vote/2023/vote_001
Please make sure that nominations are sent to (or cc:'d to)
debian-vote, and are cryptographically signed.
Kurt Roeckx
Debian Project Secretary
signature.asc
Description: PGP signature
Hi,
It seems a fix for this is sitting git, but hasn't been uploaded. Is
there a reason it's not been uploaded yet?
Kurt
Hi,
It seems a fix for this is sitting git, but hasn't been uploaded. Is
there a reason it's not been uploaded yet?
Kurt
Hi,
This is the schedule for the DPL election:
Nomination period: Saturday 2023-03-04 Friday 2023-03-10
Campaigning period: Saturday 2023-03-11 Friday 2023-03-31
Voting period: Saturday 2023-04-01 Friday 2023-04-14
Kurt
On Fri, Dec 30, 2022 at 09:42:43AM +0200, Peter Pentchev wrote:
> Hi,
>
> First of all, thanks a lot for all your work on porting Debian to
> the IBM z* systems!
>
> Are there any differences in the hardware or software configuration of
> the zandonai and zani Debian buildd hosts? There is a
Source: aflplusplus
Version: 4.04c-2
Severity: serious
Hi,
Your package is failing to build on s390x:
[*] Compiling afl++ for OS Linux on ARCH s390x
./test/unittests/unit_maybe_alloc
[==] Running 6 test(s).
[ RUN ] test_pow2
[ OK ] test_pow2
[ RUN ] test_null_allocs
[
Source: aflplusplus
Version: 4.04c-2
Severity: serious
Hi,
Your package is failing to build on s390x:
[*] Compiling afl++ for OS Linux on ARCH s390x
./test/unittests/unit_maybe_alloc
[==] Running 6 test(s).
[ RUN ] test_pow2
[ OK ] test_pow2
[ RUN ] test_null_allocs
[
Source: aflplusplus
Version: 4.04c-1
Severity: serious
Hi,
On the buildds, we get:
# -/usr/bin/make -C utils/plot_ui
/usr/bin/make -C frida_mode
make[3]: Entering directory '/<>/frida_mode'
mkdir -p /<>/frida_mode/build/
mkdir -p /<>/frida_mode/build/frida/
wget -qO
Source: aflplusplus
Version: 4.04c-1
Severity: serious
Hi,
On the buildds, we get:
# -/usr/bin/make -C utils/plot_ui
/usr/bin/make -C frida_mode
make[3]: Entering directory '/<>/frida_mode'
mkdir -p /<>/frida_mode/build/
mkdir -p /<>/frida_mode/build/frida/
wget -qO
Source: aflplusplus
Version: 4.04c-1
Hi,
The LTO mode is not build at runtime, the log shows:
[+] llvm_mode detected llvm 10+, enabling neverZero implementation and c++14
[+] llvm_mode detected llvm 11+, enabling afl-lto LTO implementation
GNUmakefile.llvm:229: ld.lld not found, cannot enable
On Tue, Nov 22, 2022 at 06:13:30PM +0100, Kurt Roeckx wrote:
> In any case, the default cluster points to 14, it's just not on port 5432.
That doesn't seem to be true. Commands like createdb, psql default to
port 5432 if there is nothing overriding it, like PGPORT env variable.
Kurt
On Tue, Nov 22, 2022 at 06:13:30PM +0100, Kurt Roeckx wrote:
> In any case, the default cluster points to 14, it's just not on port 5432.
That doesn't seem to be true. Commands like createdb, psql default to
port 5432 if there is nothing overriding it, like PGPORT env variable.
K
On Tue, Nov 22, 2022 at 10:20:06PM +0530, Pirate Praveen wrote:
>
>
> On Tue, Nov 22 2022 at 02:27:05 PM +01:00:00 +01:00:00, Kurt Roeckx
> wrote:
> > Package: gitlab
> > Version: 15.4.2+ds1-1~fto11+3
> >
> > On install I get:
> > /var/lib/dpk
On Tue, Nov 22, 2022 at 10:20:06PM +0530, Pirate Praveen wrote:
>
>
> On Tue, Nov 22 2022 at 02:27:05 PM +01:00:00 +01:00:00, Kurt Roeckx
> wrote:
> > Package: gitlab
> > Version: 15.4.2+ds1-1~fto11+3
> >
> > On install I get:
> > /var/lib/dpk
fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version
from backports is too new it seems, and it what gets installed when
you just do: apt install gitlab
fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version
from backports is too new it seems, and it what gets installed when
you just do: apt install gitlab
fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version
from backports is too new it seems, and it what gets installed when
you just do: apt install gitlab
___
Pkg-ruby-extras-maintainers mailing list
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
On install I get:
/var/lib/dpkg/tmp.ci/preinst: 7 [: Illagal number: 9.1
I have several postgresql clusters, 9.1, 9.6, 12, 14. Not all of them
are used. 9.1 is using port 5432.
Kurt
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
On install I get:
/var/lib/dpkg/tmp.ci/preinst: 7 [: Illagal number: 9.1
I have several postgresql clusters, 9.1, 9.6, 12, 14. Not all of them
are used. 9.1 is using port 5432.
Kurt
___
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: serious
Setting up gitlab (15.4.2+ds1-1~fto11+3) ...
Bundler could not find compatible versions for gem "omniauth-oauth2":
In Gemfile:
omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on
omniauth-oauth2 (~> 1.4)
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: serious
Setting up gitlab (15.4.2+ds1-1~fto11+3) ...
Bundler could not find compatible versions for gem "omniauth-oauth2":
In Gemfile:
omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on
omniauth-oauth2 (~> 1.4)
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: serious
Setting up gitlab (15.4.2+ds1-1~fto11+3) ...
Bundler could not find compatible versions for gem "omniauth-oauth2":
In Gemfile:
omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on
omniauth-oauth2 (~> 1.4)
Source: cargo
Version: 0.57.0-7
Severity: wishlist
Hi,
Would it be possible to upload a newer version of cargo? The current
version is preventing me from building things. I think the 0.62 version
matches the 1.61 version of rustc that's currently in testing/unstable.
Kurt
Hi,
The results of the General Resolution about non-free firmware:
Option 5 "Change SC for non-free firmware in installer, one installer"
The details of the results are available at:
https://www.debian.org/vote/2022/vote_003
Kurt Roeckx
Debian Project Secretary
signature.asc
D
Hi,
The results of the General Resolution about non-free firmware:
Option 5 "Change SC for non-free firmware in installer, one installer"
The details of the results are available at:
https://www.debian.org/vote/2022/vote_003
Kurt Roeckx
Debian Project Secretary
signature.asc
D
On Wed, Sep 28, 2022 at 07:22:38AM +0200, Kurt Roeckx wrote:
>
> As far as I understand of what is going wrong is that gnupg tries to
> write to the status fd, but libgnupg-interface-perl is trying to read
> gnupg's stdout and they just deadlock.
So I applied this patch and things
On Wed, Sep 28, 2022 at 04:27:56PM +0800, Shengjing Zhu wrote:
> On Wed, Sep 28, 2022 at 07:22:38AM +0200, Kurt Roeckx wrote:
> > On Mon, Sep 26, 2022 at 12:51:48AM +0800, Shengjing Zhu wrote:
> > > Hi,
> > >
> > > Is there any plan to support cv25519 key on de
On Mon, Sep 26, 2022 at 12:51:48AM +0800, Shengjing Zhu wrote:
> Hi,
>
> Is there any plan to support cv25519 key on devotee?
>
> Or could devotee send unencrypted ack to the voter? I really don't
> mind the vote secrecy... But I want to see my vote hash. I see dvt-ack
> has something like
1 - 100 of 14770 matches
Mail list logo
