From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH installer 0/2] fix 2 cosmetic glitches with the tests.
Date: Tue, 30 Apr 2024 17:18:45 +0200 [thread overview]
Message-ID: <20240430151847.568829-1-s.ivanov@proxmox.com> (raw)
while testing a patch-series today I saw quite a few:
```
Use of uninitialized value...
```
warnings from running the tests. While the issues are cosmetic, and don't
harm, the actual build - they were enough to distract me for 10 minutes,
which I want to spare others (including my future self).
Stoiko Ivanov (2):
d/control: add geoip-bin to Build-Depends
tests: prevent uninitialized value warning with undef as fqdn
debian/control | 1 +
test/parse-fqdn.pl | 5 +++--
2 files changed, 4 insertions(+), 2 deletions(-)
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-04-30 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:18 Stoiko Ivanov [this message]
2024-04-30 15:18 ` [pve-devel] [PATCH installer 1/2] d/control: add geoip-bin to Build-Depends Stoiko Ivanov
2024-04-30 15:18 ` [pve-devel] [PATCH installer 2/2] tests: prevent uninitialized value warning with undef as fqdn Stoiko Ivanov
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=20240430151847.568829-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox