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: qa.debian.org
Severity: normal
X-Debbugs-Cc: debbug.qa.debian@sideload.33mail.com
Control: affects -1 +www.debian.org
There are essentially no documented policies or procedures for bug
report archival. The only disclosure on the website is here:
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: vmtouch
Version: 1.3.1-2
Severity: important
looking at the cmdline arguments the service actually provides to vmtouch it is
mangling the provided ones and thereby creates invalid arguments.
esp. for "-p 0-50k" which becomes "-p 0 50" and "-P /run/vmtouch" which somehow
gets joined
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
Hello Moritz,
I've read your bug report at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031046
I believe it to be unacceptable to exclude Asterisk from Bookworm.
Asterisk is used by a LOT of users worldwide and, as you've noted, is
frequently the subject of security concerns.
The
On 2023-08-27 12:14, Jonas Smedegaard wrote:
Hi David,
Quoting debian@spam.lublink.net (2023-08-27 16:04:20)
I wrote and applied the required patch ( see attached ).
I built the asterisk package 1:20.4.0~dfsg+~cs6.13.40431414-2 and
signed
it successfully.
I installed the new package
Merge request is in Salsa :
https://salsa.debian.org/pkg-voip-team/asterisk/-/merge_requests/4
On 2023-08-27 10:04, debian@spam.lublink.net wrote:
I wrote and applied the required patch ( see attached ).
I built the asterisk package 1:20.4.0~dfsg+~cs6.13.40431414-2 and
signed it
I wrote and applied the required patch ( see attached ).
I built the asterisk package 1:20.4.0~dfsg+~cs6.13.40431414-2 and signed
it successfully.
I installed the new package on my local machine and tested a lua
dialplan. I connected using chan_sip+baresip, and setup a new lua
context in
It would seem there is now a release 3.4.0.
https://github.com/baresip/baresip/tree/v3.4.0
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
On Tue, May 02, 2023 at 02:35:05AM -0400, gs-debian@gluelogic.com wrote:
> On Fri, Apr 21, 2023 at 01:47:22PM -0400, gs-debian@gluelogic.com wrote:
> > On Fri, Apr 21, 2023 at 06:14:25PM +0200, Marco d'Itri wrote:
> > > On Apr 21, gs-debian@gluelogic.com wrote:
> > >
> > > > I
On Fri, Apr 21, 2023 at 01:47:22PM -0400, gs-debian@gluelogic.com wrote:
> On Fri, Apr 21, 2023 at 06:14:25PM +0200, Marco d'Itri wrote:
> > On Apr 21, gs-debian@gluelogic.com wrote:
> >
> > > I probably should have started with the most basic thing:
> > >
> > > What is the date on your
On Fri, Apr 21, 2023 at 06:14:25PM +0200, Marco d'Itri wrote:
> On Apr 21, gs-debian@gluelogic.com wrote:
>
> > I probably should have started with the most basic thing:
> >
> > What is the date on your device?
> NTP-accurate.
Perhaps there is something amiss in the Debian 32-bit build of
On Fri, Apr 21, 2023 at 09:38:31AM +0200, Marco d'Itri wrote:
> On Apr 21, gs-debian@gluelogic.com wrote:
>
> > What your `uname -a` ?
> Linux omitted.mi.bofh.it 6.1.0-7-arm64 #1 SMP Debian 6.1.20-2 (2023-04-08)
> aarch64 GNU/Linux
>
> > What is the output of the following for you?
> > $
On Fri, Apr 21, 2023 at 07:41:13AM +0200, Marco d'Itri wrote:
> On Apr 21, gs-debian@gluelogic.com wrote:
>
> > Please confirm you are running an arm64 kernel, as you posted above.
> Confirmed.
What your `uname -a` ?
What is the output of the following for you?
$ lighttpd -V | grep "Y2038
On Wed, Apr 19, 2023 at 01:39:02AM +0200, Marco d'Itri wrote:
> Package: lighttpd
> Version: 1.4.69-1
> Severity: normal
>
> I am using the latest openssl and lighttpd packages on an armhf (with an
> arm64 kernel) and an amd64 system, and only on the armhf system I always
> get this warning at
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
Thanks.
Re-install helped.
Achim
On 09.01.23 15:03, Antonio Russo wrote:
On 1/9/23 01:48, Achim Schaefer wrote:
Package: zfs-dkms
Version: 2.1.7-1
Severity: important
X-Debbugs-Cc: bts.debian@schaefer-home.eu
When installing the new 6.1 kernel headers, dkms starts to build the zfs
> 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
On Mon, May 10, 2021 at 08:00:00AM -0700, Otto Kekäläinen wrote:
> Hello!
>
> If you want to help improve MariaDB in Debian in the open source way,
> you could for example:
>
> - submit your suggestion for a fix as a Merge Request at
> https://salsa.debian.org/mariadb-team/mariadb-10.5
> - help
On Wed, Mar 31, 2021 at 08:30:24AM -0400, PICCORO McKAY Lenz wrote:
> linux is so popular (wh ugh) today.. but only for enterprices.. i do
> not see any help for normal users that wants more freedom .. sad and
> oscure!
Please go away troll.
Your language is inappropriate and you are clearly
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
On Wed, Nov 16, 2016 at 03:18:04PM -, Mutt wrote:
> Debian changed the default to use GPGME for GPG and S/MIME encryption.
>
> Please try putting "unset crypt_use_gpgme" in your .muttrc and restart
> mutt. (You must restart mutt for this option to have any effect).
>
> Let me know if
I'm having the exact same issue
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
Tie/StdHash.pm is missing from Perl 5.20.1
It is there. You have unreadable paths in your @INC and perl
complains. See the above bug log for more information.
sh dpkg -L perl-base | grep Tie
/usr/share/perl/5.20.2/Tie
/usr/share/perl/5.20.2/Tie/Hash.pm
Same issue with amanda looking
After having the problem again, I went back and checked
/var/log/messages. This turned up:
May 17 15:26:47 hostname kernel: [815860.826184] flickrfs[21821]:
segfault at 0 ip b7deb0bf sp b4f0eca8 error 4 in
libc-2.7.so[b7d85000+155000]
I hope this sheds further light on what is causing this
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
42 matches
Mail list logo
