FYI, I submitted a patch to Debian on 19 March, over two months ago.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067126
It has taken Debian developers (volunteers) over 10 weeks (!!!)
to pick up a simple patch that I packaged for them and signed on
salsa.debian.org. :(
Gianfranco, thank you for sponsoring this upload.
> Please some nitpicks for a future upload
> 1) wait for the sponsor upload before tagging,
>many of your entries were never uploaded
ack.
Still, this seems like unnecessary latency between humans once a Debian
developer volunteer picks up
lighttpd-1.4.76-3 passes autopkgtests and expected CI tests,
and is tagged. (This is a non-DD maintainer upload.)
* Package name : lighttpd
Version : 1.4.76-3
Upstream contact : team+light...@tracker.debian.org
* URL : https://lighttpd.net/
* License :
lighttpd-1.4.76-2 passes autopkgtests and expected CI tests,
and is tagged. (This is a non-DD maintainer upload.)
* Package name : lighttpd
Version : 1.4.76-2
Upstream contact : team+light...@tracker.debian.org
* URL : https://lighttpd.net/
* License :
lighttpd-1.4.76-1 passes autopkgtests and expected CI tests,
and is tagged. (This is a non-DD maintainer upload.)
* Package name : lighttpd
Version : 1.4.76-1
Upstream contact : team+light...@tracker.debian.org
* URL : https://lighttpd.net/
* License :
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: gs-bugs.debian@gluelogic.com
Dear mentors,
I am looking for a DD sponsor for my package "lighttpd":
https://salsa.debian.org/debian/lighttpd/
I am an upstream lighttpd developer and have participated in
maintaining lighttpd on
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: gs-bugs.debian@gluelogic.com
Dear mentors,
I am looking for a DD sponsor for my package "lighttpd":
https://salsa.debian.org/debian/lighttpd/
I am an upstream lighttpd developer and have participated in
maintaining lighttpd on
On Mon, Dec 04, 2023 at 11:49:30AM +0100, Emanuele Rocca wrote:
> With the attached patch lighttpd cleanly cross-builds from source.
Thanks, Emanuele.
A slightly different patch:
https://salsa.debian.org/debian/lighttpd/-/commit/a7d695d59c9a8bffe154aae29e335102beaaf3f2
was committed a few
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: gs-bugs.debian@gluelogic.com
Dear mentors,
I am looking for a DD sponsor for my package "lighttpd":
https://salsa.debian.org/debian/lighttpd/
I am an upstream lighttpd developer and have participated in
maintaining lighttpd on
Repeating: lighttpd TLS configuration recommendations supercede
the issue reported here. (https://wiki.lighttpd.net/Docs_SSL)
> I now removed that cipher list (falling back to the default), and this
> disabled the 2 remaining ciphers (DHE-RSA-AES256-GCM-SHA384 and
> DHE-RSA-AES128-GCM-SHA256)
Marco, please review my previous messages and try to help provide
additional information.
Thank you. Glenn
On Fri, Jul 07, 2023 at 09:28:24AM +, Alain Knaff wrote:
> Package: lighttpd
> Version: 1.4.69-1
>
> Since our upgrade to Debian 12, lighttpd now uses insecure
> Diffie-Hellman parameters
> c90fdaa22168c234c4c6628b80dc1cd129024e088a67cc74020bbea63
>
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: gs-bugs.debian@gluelogic.com
Dear mentors,
I am looking for a DD sponsor for my package "lighttpd":
https://salsa.debian.org/debian/lighttpd/
I am an upstream lighttpd developer and have participated in
maintaining lighttpd on
Macro, please review my previous messages and try to help provide
additional information.
Thank you. Glenn
On Thu, May 11, 2023 at 11:49:21AM +0200, Michael Moore wrote:
...
> Issue and suggested fix:
> ===
> In lighttpd.conf the includes for conf-enabled/*.conf happens after passing
> server.port to the use-ipv6.pl script. Re-ordering these lines so that the
> conf files are included
Ubuntu fixed this bug with
jq (1.6-2.1ubuntu1) hirsute; urgency=medium
[ Alex Murray ]
* Fix fromdate when local time is during daylight savings (LP: #1910162)
- d/p/fix-ftbfs-when-localtime-is-dst.patch: Backport upstream patch
which ensures fromdate uses the correct time during
Can this be closed? Are there any action items remaining for this bug?
I am still getting messages that packages depending on wolfssl are
"marked for autoremoval from testing on 2023-01-27"
Thank you. Glenn
> I plan to upload version 5.5.1 in the near future.
Felix, a month has passed and we are still waiting for an upload.
Failure to upload a version with security fixes within the next few days
will result in wolfssl and packages which depend on wolfssl to be
removed from Debian Testing.
Please
Thank you very much! Adding CAP_DAC_OVERRIDE solved it for me as well. Not sure
how many hours it would have taken for me to figure it out.
Does systemd or the linux kernel log capability violations somewhere? (is it
even possible)
smime.p7s
Description: S/MIME Cryptographic Signature
Hey there, got this warning, dunno why, never read this before.
Here's what I did before I got this warning.
Be aware that I use parrot 4.6, which is based on debian but is a
rolling distribution.
The not upgraded (helt back) packages are some nvidia packages, not
needed on my system (no nvidia
Additionnal informations:
python
Python 2.7.11+ (default, May 9 2016, 15:54:33)
[GCC 5.3.1 20160429] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import requests; requests.__version__.split('.')
Traceback (most recent call last):
File "", line 1, in
Hello, right after this morning last upgrade, my proftp server and my
webmin stopped to work throwing out these errors :
/var/log/webmin/miniserv.error:/usr/bin/perl: relocation error:
/lib/libresolv.so.2: symbol __res_iclose, version GLIBC_PRIVATE not
defined in file libc.so.6 with link time
22 matches
Mail list logo
