From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: wangmy <wangmy@fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] lighttpd: upgrade 1.4.69 -> 1.4.71
Date: Thu, 1 Jun 2023 23:35:10 +0200 [thread overview]
Message-ID: <202306012135103d72bd44@mail.local> (raw)
In-Reply-To: <1685610221-29015-10-git-send-email-wangmy@fujitsu.com>
Hello,
On the autobuilders, this causes:
WARNING: lighttpd-1.4.71-r0 do_package_qa: QA Issue: lighttpd rdepends on lighttpd-module-indexfile, but it isn't a build dependency? [build-deps]
WARNING: lighttpd-1.4.71-r0 do_package_qa: QA Issue: lighttpd rdepends on lighttpd-module-staticfile, but it isn't a build dependency? [build-deps]
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-06-01 21:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 9:03 [OE-core] [PATCH] babeltrace2: upgrade 2.0.4 -> 2.0.5 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] curl: upgrade 8.1.1 -> 8.1.2 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] dos2unix: upgrade 7.4.4 -> 7.5.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] enchant2: upgrade 2.3.4 -> 2.5.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] fribidi: upgrade 1.0.12 -> 1.0.13 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] libdnf: upgrade 0.70.0 -> 0.70.1 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] libmicrohttpd: upgrade 0.9.76 -> 0.9.77 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] libxft: upgrade 2.3.7 -> 2.3.8 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] libxpm: upgrade 3.5.15 -> 3.5.16 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] lighttpd: upgrade 1.4.69 -> 1.4.71 wangmy
2023-06-01 21:35 ` Alexandre Belloni [this message]
2023-06-01 9:03 ` [OE-core] [PATCH] mobile-broadband-provider-info: upgrade 20221107 -> 20230416 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] bind: upgrade 9.18.14 -> 9.18.15 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] ccache: upgrade 4.8 -> 4.8.1 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] libcap: upgrade 2.68 -> 2.69 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] libuv: upgrade 1.44.2 -> 1.45.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-pip: upgrade 23.0.1 -> 23.1.2 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-psutil: upgrade 5.9.4 -> 5.9.5 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-ruamel-yaml: upgrade 0.17.21 -> 0.17.31 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-sphinx: upgrade 6.1.3 -> 7.0.1 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] orc: upgrade 0.4.33 -> 0.4.34 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-cython: upgrade 0.29.34 -> 0.29.35 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-dbusmock: upgrade 0.28.7 -> 0.29.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-hatch-fancy-pypi-readme: upgrade 22.8.0 -> 23.1.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.71.0 -> 6.75.7 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-numpy: upgrade 1.24.2 -> 1.24.3 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-pycryptodome: upgrade 3.17 -> 3.18.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-pycryptodomex: " wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-requests: upgrade 2.30.0 -> 2.31.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-setuptools-rust: upgrade 1.5.2 -> 1.6.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-sphinx-rtd-theme: upgrade 1.2.0 -> 1.2.1 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-trove-classifiers: upgrade 2023.5.2 -> 2023.5.24 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] python3-typing-extensions: upgrade 4.5.0 -> 4.6.2 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] repo: upgrade 2.32 -> 2.34.1 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] sysklogd: upgrade 2.4.4 -> 2.5.0 wangmy
2023-06-01 9:03 ` [OE-core] [PATCH] xdpyinfo: upgrade 1.3.3 -> 1.3.4 wangmy
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=202306012135103d72bd44@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.