Github messages for voidlinux
 help / color / mirror / Atom feed
From: gstrauss <gstrauss@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lighttpd: update to 1.4.73
Date: Tue, 31 Oct 2023 06:51:02 +0100	[thread overview]
Message-ID: <20231031055102.HBVv574OIUQknGPL5abGE9DCMDUYKLda2sCU8iuv83A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46978@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

New comment by gstrauss on void-packages repository

https://github.com/void-linux/void-packages/pull/46978#issuecomment-1786492906

Comment:
@classabbyamp the void linux CI does perform lighttpd `make check`, as I can see from the build logs:
```
=> lighttpd-1.4.73_1: running do_check ...
ninja: Entering directory `build'
[0/1] Running all tests.
1/9 test_configfile  OK              0.01s
2/9 test_common      OK              0.01s
3/9 test_mod         OK              0.01s
4/9 prepare          OK              0.01s
5/9 request.t        OK              0.26s
6/9 core-condition.t OK              0.09s
7/9 mod-fastcgi.t    OK              0.10s
8/9 mod-scgi.t       OK              0.08s
9/9 cleanup          OK              0.01s
```

  parent reply	other threads:[~2023-10-31  5:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  5:26 [PR PATCH] " gstrauss
2023-10-31  5:29 ` classabbyamp
2023-10-31  5:30 ` classabbyamp
2023-10-31  5:43 ` gstrauss
2023-10-31  5:44 ` gstrauss
2023-10-31  5:49 ` gstrauss
2023-10-31  5:49 ` gstrauss
2023-10-31  5:50 ` classabbyamp
2023-10-31  5:50 ` classabbyamp
2023-10-31  5:51 ` gstrauss [this message]
2023-10-31  5:53 ` classabbyamp
2023-10-31  5:55 ` classabbyamp
2023-10-31  6:22 ` gstrauss
2023-10-31  6:47 ` 0x5c
2023-10-31  7:17 ` [PR PATCH] [Merged]: " classabbyamp
2023-10-31 15:59 ` gstrauss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231031055102.HBVv574OIUQknGPL5abGE9DCMDUYKLda2sCU8iuv83A@z \
    --to=gstrauss@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).