firewalllogs*dat: Simplify code for color calculation #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replace 10 if statements with duplicated code for print and setting background color by using a variable and one if statement.
…ure_cgibin_cleanup
Add support for caching package files for ArchLinux in updxlrator, by adding pkg.tar.xz to the regular expression for Linux vendor.
The updatexlrator.cgi is assuming that colon is not part of any filenames downloaded by updxlrator. Fix this by fixing regular expression used for listing pending download files, and by fixing regular expression used to listing files in maintenance view. The fix for listing in maintenance is not very nice, I just use ":separator:" as field separator instead of just ":", which was used earlier. This should make it very unlikely to collide with a part of the filename. Also make the files in download be sorted using lower case, like it is done for files in the vendor path. The problem can be reproduced by downloading http://mirror.us.leaseweb.net/archlinux/community/os/x86_64/ docker-1:0.7.6-1-x86_64.pkg.tar.xz, after pkg.tar.xz files support has been added to updxlrator.
The menus in the new default theme does not work properly on ipad and I guess other devices using mobile safari. The reason is that <a> tags without href is not marked as clickable by ios, and therefore no css hover effect is applied. The fix is either to add a href="#" attribute or a onclick="return true;" atribute on the <a> tag. I prefer the href solution, since it is a no javascript solution.
qos.cgi and media.cgi depend on swapVisibility function, this is defined in each theme, but was missing from the new theme. Add the function, and implement it using jquery, since jquery is always present in the new theme.
The proper way to mark readonly is to use readonly="readonly", not readonly="true", like it was done some places.
Almost all of <input type="image"... has both an alt and a title attribute, but some are missing title, and when the icon is not very clear, it makes it harder to understand what the icon does. By adding title, the browser displays text when mouse pointer is over the icon. Also add missing quotes for alt and title attributes where needed.
Add missing colon and put them into one column in the table.
igb v5.0.6 and e1000e v2.5.4
|
Problems with rebasing, closing this |
mtremer
pushed a commit
that referenced
this pull request
May 14, 2021
- Update from 0.2.7 to 0.2.10
- Convert from python-inotify to python3-inotify
make.sh, lfs & rootfiles
- Update rootfiles
- Changelog
0.2.8: - We now just *skip* the event if not known
- Implement InotifyTree and InotifyTrees as sub-classes of new BaseTree
class
- Made InotifyTree and InotifyTrees sub-classes of new base class
BaseTree
- Recursively watch a list of paths/trees
0.2.9: - Added getter for Inotify object from tree objects
- Added note to docs about race-conditions. Added small change for
redundant adds.
- Slightly reorganized documentation. Updated example.
- Merge pull request #35 from dsoprea/dustin. Added extensive unit-test
coverage. Closes all bug requests.
- Added large amount of unit-test coverage.
- Now handle rename-specific events.
- Can now also ignore issues with new directories not existing if
you're created *and* deleted or renamed a folder since the last
time events were read.
- Adjusted requirements for simplicity.
- Added Python 3 compatibility.
- Fixed Unicode support.
- Can now provide `filter_predicate` to event_gen() to allow custom
loop termination based on events.
- We'll now terminate the loop when certain events are encountered.
These events are passed into event_gen() as `terminal_events`. By
default these are the IN_Q_OVERFLOW and IN_UNMOUNT types.
- Fixes #28
- Fixes #23
- Fixes #22
- Fixes #19
- Fixes #16
- Fixes #15
- Fixes #5
- Check presence of both glibc errno and musl libc err
- Support for musl libc (Alpine Linux)
- Merge pull request #27 from jessesuen/master. Support for musl libc
(Alpine Linux)
- Check presence of both glibc errno and musl libc err
- Merge pull request #26 from hathcock/hathcock/issue-25. resolves #25,
list of binary paths can't be logged with existing call
- Support for musl libc (Alpine Linux)
- Resolves #25, list of binary paths can't be logged with existing
call
0.2.10: - Merge pull request #34 from davidparsson/
feature/support-moved-directories
- Support MOVED_FROM and MOVED_TO in BaseTree
- events: Now log event types from epoll vs data stream.
- This release implicitly fixed the botched binary package released
in 0.2.9
Signed-off-by: Adolf Belka <[email protected]>
Reviewed-by: Peter Müller <[email protected]>
Signed-off-by: Michael Tremer <[email protected]>
mtremer
pushed a commit
that referenced
this pull request
Feb 14, 2022
- Update from 2.3.3op2 to 2.4.1
- Update of rootfile
- Changelog
Changes in CUPS v2.4.1 (27th January 2020)
- The default color mode now is now configurable and defaults to the printer's
reported default mode (Issue #277)
- Configuration script now checks linking for -Wl,-pie flags (Issue #303)
- Fixed memory leaks - in testi18n (Issue #313), in `cups_enum_dests()`
(Issue #317), in `_cupsEncodeOption()` and `http_tls_upgrade()` (Issue #322)
- Fixed missing bracket in de/index.html (Issue #299)
- Fixed typos in configuration scripts (Issues #304, #316)
- Removed remaining legacy code for `RIP_MAX_CACHE` environment variable
(Issue #323)
- Removed deprecated directives from cupsctl and cups-files.conf (Issue #300)
- Removed `purge-jobs` legacy code from CGI scripts and templates (Issue #325)
Changes in CUPS v2.4.0 (29th November 2021)
- Added configure option --with-idle-exit-timeout (Issue #294)
- Added --with-systemd-timeoutstartsec configure option (Issue #298)
- DigestOptions now are applied for MD5 Digest authentication defined
by RFC 2069 as well (Issue #287)
- Fixed compilation on Solaris (Issue #293)
- Fixed and improved German translations (Issue #296, Issue #297)
Changes in CUPS v2.4rc1 (12th November 2021)
- Added warning and debug messages when loading printers
if the queue is raw or with driver (Issue #286)
- Compilation now uses -fstack-protector-strong if available (Issue #285)
Changes in CUPS v2.4b1 (27th October 2021)
- Added support for CUPS running in a Snapcraft snap.
- Added basic OAuth 2.0 client support (Issue #100)
- Added support for AirPrint and Mopria clients (Issue #105)
- Added configure support for specifying systemd dependencies in the CUPS
service file (Issue #144)
- Added several features and improvements to `ipptool` (Issue #153)
- Added a JSON output mode for `ipptool`.
- The `ipptool` command now correctly reports an error when a test file cannot
be found.
- CUPS library now uses thread safe `getpwnam_r` and `getpwuid_r` functions
(Issue #274)
- Fixed Kerberos authentication for the web interface (Issue #19)
- The ZPL sample driver now supports more "standard" label sizes (Issue #70)
- Fixed reporting of printer instances when enumerating and when no options are
set for the main instance (Issue #71)
- Reverted USB read limit enforcement change from CUPS 2.2.12 (Issue #72)
- The IPP backend did not return the correct status code when a job was canceled
at the printer/server (Issue #74)
- The `testlang` unit test program now loops over all of the available locales
by default (Issue #85)
- The `cupsfilter` command now shows error messages when options are used
incorrectly (Issue #88)
- The PPD functions now treat boolean values as case-insensitive (Issue #106)
- Temporary queue names no longer end with an underscore (Issue #110)
- The USB backend now runs as root (Issue #121)
- Added pkg-config file for libcups (Issue #122)
- Fixed a PPD memory leak caused by emulator definitions (Issue #124)
- Fixed a `DISPLAY` bug in `ipptool` (Issue #139)
- The scheduler now includes the `[Job N]` prefix for job log messages, even
when using syslog logging (Issue #154)
- Added support for locales using the GB18030 character set (Issue #159)
- `httpReconnect2` did not reset the socket file descriptor when the TLS
negotiation failed (Apple #5907)
- `httpUpdate` did not reset the socket file descriptor when the TLS
negotiation failed (Apple #5915)
- The IPP backend now retries Validate-Job requests (Issue #132)
- Now show better error messages when a driver interface program fails to
provide a PPD file (Issue #148)
- Added dark mode support to the CUPS web interface (Issue #152)
- Added a workaround for Solaris in `httpAddrConnect2` (Issue #156)
- Fixed an interaction between `--remote-admin` and `--remote-any` for the
`cupsctl` command (Issue #158)
- Now use a 60 second timeout for reading USB backchannel data (Issue #160)
- The USB backend now tries harder to find a serial number (Issue #170)
- Fixed `@IF(name)` handling in `cupsd.conf` (Apple #5918)
- Fixed documentation and added examples for CUPS' limited CGI support
(Apple #5940)
- Fixed the `lpc` command prompt (Apple #5946)
- Now always pass "localhost" in the `Host:` header when talking over a domain
socket or the loopback interface (Issue #185)
- Fixed a job history update issue in the scheduler (Issue #187)
- Fixed `job-pages-per-set` value for duplex print jobs.
- Fixed an edge case in `ippReadIO` to make sure that only complete attributes
and values are retained on an error (Issue #195)
- Hardened `ippReadIO` to prevent invalid IPP messages from being propagated
(Issue #195, Issue #196)
- The scheduler now supports the "everywhere" model directly (Issue #201)
- Fixed some IPP Everywhere option mapping problems (Issue #238)
- Fixed support for "job-hold-until" with the Restart-Job operation (Issue #250)
- Fixed the default color/grayscale presets for IPP Everywhere PPDs (Issue #262)
- Fixed support for the 'offline-report' state for all USB backends (Issue #264)
- Documentation fixes (Issue #92, Issue #163, Issue #177, Issue #184)
- Localization updates (Issue #123, Issue #129, Issue #134, Issue #146,
Issue #164)
- USB quirk updates (Issue #192, Issue #270, Apple #5766, Apple #5838,
Apple #5843, Apple #5867)
- Web interface updates (Issue #142, Issue #218)
- The `ippeveprinter` tool now automatically uses an available port.
- Fixed several Windows TLS and hashing issues.
- Deprecated cups-config (Issue #97)
- Deprecated Kerberos (`AuthType Negotiate`) authentication (Issue #98)
- Removed support for the (long deprecated and unused) `FontPath`,
`ListenBackLog`, `LPDConfigFile`, `KeepAliveTimeout`, `RIPCache`, and
`SMBConfigFile` directives in `cupsd.conf` and `cups-files.conf`.
- Stubbed out deprecated `httpMD5` functions.
- Add test for undefined page ranges during printing.
Signed-off-by: Adolf Belka <[email protected]>
Reviewed-by: Peter Müller <[email protected]>
mtremer
pushed a commit
that referenced
this pull request
Jan 24, 2025
- Update from version 6.4.39 to 6.5.2
- Update of rootfile not required
- Changelog
6.5.2
ADVANCE WARNING OF FEATURES TO BE REMOVED OR CHANGED IN FUTURE VERSIONS
(There are no plans to remove features from a 6.5.X release, but they may be
removed from a 6.6.0 or newer release.)
* Support for operating systems that are not sufficiently POSIX compliant may be
removed or operation on such systems may be suboptimal for future releases.
* Future fetchmail releases may require compilers and operating systems
that adhere to standards issued 2011 or later. (See README for requirements.)
* Future fetchmail releases may tighten up security and lean towards
it a bit more by, for instance, implementing recommendations from
RFC-7817 or RFC-8314. This may, for instance, require that TLS v1.1
or newer be used.
* The MX and host alias DNS lookups that fetchmail performs in multidrop mode
are based on assumptions that are rarely met in practice, somewhat defective,
deprecated and may be removed from a future fetchmail version.
They have never supported IPv6 (including IPv6-mapped IPv4).
Non-DNS based alias keywords such as "aka" will remain in fetchmail.
* The monitor and interface options may be removed from a future fetchmail
version as they are not reasonably portable across operating systems.
* POP2 is obsolete, support will be removed from a future fetchmail version.
* IMAP2 and IMAP4 (not IMAP4r1) are obsolete, support may be removed from a
future fetchmail version.
* RPOP is obsolete, support will be removed from a future fetchmail release.
* The multidrop To/Cc guessing code along with the fragile duplicate suppressor
is deprecated and may be removed from a future release.
* The "envelope Received" option may be removed from a future release, because
the Received header was never meant to be machine-readable, the format varies
widely, and various other differences in behavior make parsing Received an
unreliable undertaking. The envelope option as such will remain though, in
order to support Delivered-To, X-Envelope-To, X-Original-To and similar.
See also <http://home.pages.de/~mandree/mail/multidrop>.
* The "protocol auto" default inside fetchmail may be removed from a future
fetchmail release. Explicit configuration of the protocol is recommended.
* Kerberos IV support may be removed from a future fetchmail release.
* Kerberos 5 support may be removed from a future fetchmail release.
(Although GSS-API support should remain as long as it's viable.)
* The --principal option may be removed from a future fetchmail release.
* SIGHUP wakeup support may be removed from a future fetchmail release and
cause fetchmail to terminate - it was broken for many years.
* The maintainer may migrate fetchmail to C++, and impose further requirements
(dependencies), such as Boost or other class libraries.
* The softbounce option default will change to "false" in the next release.
* The --bsmtp - mode of operation may be removed in a future release.
* Fetchmailconf is deprecated and will be removed from a future release.
* Fetchmail does not guarantee compatibility with EOL OpenSSL versions. Support
for end-of-life OpenSSL versions may be removed even from patchlevel releases.
* Nonstandard or by today's standards insufficiently secure authentication
schemes (such as OPIE, RPA) may be removed from future fetchmail versions.
* Nonstandard protocol extensions (such as SDPS/*ENV) may be removed from future
fetchmail versions.
* --auth ssh may be removed from future fetchmail versions. Use --auth implicit.
* Future fetchmail releases (even minor ones) may change undocumented parts of
the .netrc parser in incompatible ways to enhance compatibility with typical
ftp(1) .netrc parsers.
KNOWN BUGS AND WORKAROUNDS
* Fetchmail does not handle messages without Message-ID header well
(See sourceforge.net bug #780933)
* Fetchmail currently uses 31-bit signed integers in several places
where unsigned and/or wider types should have been used. Please report
issues with this.
* BSMTP is mostly untested and errors can cause corrupt output.
* Fetchmail does not track pending deletes across crashes.
* The command line interface is sometimes a bit stubborn, for instance,
fetchmail -s doesn't work with a daemon running.
* Linux systems may return duplicates of an IP address in some circumstances if
no or no global IPv6 addresses are configured.
(No workaround. Ubuntu Bug#582585, Novell Bug#606980.)
* Kerberos 5 may be broken, particularly on Heimdal, and provide bogus error
messages. This will not be fixed, because the maintainer has no Kerberos 5
server to test against. Use GSSAPI.
* For IMAP connections, fetchmail will print "will idle after poll" in
verbose mode even though --idle is not given, as an artifact of the 6.4.22
security fixes. Fetchmail means "could idle after poll", but this would
have required another loop through the translators.
* aka ... hostnames are not considered for upstream server X.509 certificate
verification, aka was meant for alias detection with multidrop mailboxes.
* When compiled against wolfSSL, note that it is not a feature-complete
emulation of OpenSSL. Main functionality is given, but some minor details
may not work the same as in OpenSSL builds.
* When compiled against LibreSSL (due to licensing, this only works on OpenBSD
where LibreSSL is part of the OS), note that LibreSSL is somewhat behind
recent OpenSSL versions, so prefer OpenSSL to LibreSSL if you can.
* FreeBSD's OPIE implementation cannot be found when using a C++ compiler.
This should not affect the normal build, which uses a C compiler.
* Using ccache may trigger "implicit fallthrough" warnings because
the comments that, for instance, GCC understands, are removed by ccache's
separate preprocessing. Fixing this portably requires C++17.
* Fetchmail's RFC-2047 encoder (used for localized Subject: lines of locally-
originated e-mail messages) is simplistic and violates the RFC-2047
requirement that multibyte characters must not be split across
encoded-words.
TRANSLATIONS: fetchmail's translations were updated, courtesy of:
* cs: Petr Pisar [Czech]
* sr: Мирослав Николић (Miroslav Nikolić) [Serbian]
CHANGES:
* Minor documentation consistency fixes (versions, dates).
6.5.1
BUG AND PORTABILITY FIXES:
* Drop two wolfSSL compile-time checks that were for older 6.4 or for future
7.0 releases and broke compilation with wolfSSL 5.7.4.
Fixes https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282413#c4
* Use %p instead of non-portable %#p for one wolfSSL-related diagnostic message
(FreeBSD defines %#p to be %p, on many other platforms it's undefined
behavior).
* Add regex_helper.c to list of files that contain translatable strings,
which contains two strings we missed to translate.
CHANGES:
* Simplify EVP_MD_fetch API detection ("like OpenSSL 3" vs. "like OpenSSL 1")
for version switch and base it on the claimed OpenSSL version of the crypto
SSL, which works for LibreSSL (claims OpenSSL 2) and wolfSSL alike.
TRANSLATIONS: fetchmail's messages were translated by these fine people:
* sq: Besnik Bleta [Albanian]
* es: Cristian Othón Martínez Vera [Spanish]
* ro: Remus-Gabriel Chelu [Romanian]
* fr: Frédéric Marchal [French]
* pl: Jakub Bogusz [Polish]
* sv: Göran Uddeborg [Swedish]
* ja: Takeshi Hamasaki [Japanese]
* eo: Keith Bowes [Esperanto]
6.5.0
SECURITY FIX:
* .netrc now may not have more than 0700 permission if it contains passwords,
else fetchmail will warn and ignore the file.
REMOVED FEATURES
* fetchmail no longer supports using an MDA as SMTP fallback. This is required
to make deliveries consistent.
The --enable-fallback configure option is gone.
* fetchmail no longer supports SSLv3. --sslproto ssl3 and ssl3+ options have
been removed and behave as though "--sslproto auto" had been given.
INCOMPATIBLE CHANGES
* fetchmail by default only negotiates TLS v1.2 or higher. (RFC-7525)
* fetchmail can auto-negotiate TLS v1.1 through the --sslproto tls1.1+ option.
* fetchmail can auto-negotiate TLS v1.0 through the --sslproto tls1+ option.
* fetchmailconf now requires Python 3.7.0 or newer.
* fetchmail, with --logfile, now logs time stamps into the file, in localtime
and in the format "Jun 20 23:45:01 fetchmail: ". It will be localized through
the environment variables LC_TIME (or LC_ALL) and TZ.
Contributed by Holger Hoffstätte.
* fetchmail sets the OPENSSL security level to 2 by default.
Override is possible from an environment variable,
see EXPERIMENTAL CHANGES below.
* The ca, da, en_GB, id, it, nl, ru, zh_CN translations have been disabled,
they are too far behind.
CHANGED REQUIREMENTS
* fetchmail 6.5.0 is written in C99 and requires a SUSv3 (Single Unix
Specification v3, a superset of POSIX.1-2001 aka. IEEE Std 1003.1-2001 with
XSI extension) compliant system.
In particular, older fetchmail versions had workarounds or replacement code
for several functions standardized in the Single Unix Specification v3, these
have been removed. Hence:
- The trio/ library has been removed from the distribution.
- The libesmtp/getaddrinfo.? library has been removed from the distribution.
- The KAME/getnameinfo.c file has been removed from the distribution.
* fetchmail 6.5.0 requires a TLSv1.3-capable version of OpenSSL or wolfSSL,
at a minimum OpenSSL v3.0.9 or wolfSSL v5.7.2.
TRANSLATIONS: fetchmail's messages were translated by these fine people:
* cs: Petr Pisar [Czech]
* eo: Keith Bowes [Esperanto]
* es: Cristian Othón Martínez Vera [Spanish]
* fr: Frédéric Marchal [French]
* ja: Takeshi Hamasaki [Japanese]
* ro: Remus-Gabriel Chelu [Romanian]
* sv: Göran Uddeborg [Swedish]
* sq: Besnik Bleta [Albanian]
* pl: Jakub Bogusz [Polish]
BUG FIXES
* fetchmail can now report mailbox sizes of 2^31 octets and beyond (2 GibiB).
This required C99 support (for the long long type).
Fixes Debian Bug#873668, reported by Andreas Schmidt.
* fetchmail now defines its OpenSSL API level to 3.0.0 so as to expose the
3.0.0 APIs from OpenSSL.
* The .netrc parser no longer permits "machine" after "default".
* Add manpage info on the .netrc syntax, as ftp(1) is not standardized and
may not be installed. Fixes Launchpad Bug #1976361 reported by Bill Yikes.
* Received: lines now return GMT time if the tzoffset cannot be represented
as whole minutes. Reported by @rriddicc via Gitlab #49.
* If fetchmail was running localized, generated an error e-mail message locally,
and if the selected translation would require the Subject: line to wrap
inside an RFC-2047 encoded word (=?UTF-8?Q?...?=), the wrapped encoded-word
was not indented, thus not marked as a continuation line.
* SSL error handling was improved, fetchmail now consistently clears the
thread/SSL error queue before SSL I/O operations and checks SSL_get_error
afterwards. The SSL_connect() error handling has been revised to log more
consistently.
CHANGES
* When fetchmail attempts to log out from an IMAP4 server and the server messes
up its responses (it is supposed to send an untagged * BYE and a tagged
A4711 OK) and sends a tagged A4711 BYE response, tolerate that, rather than
reporting a protocol error. We don't intend to chat any more so the protocol
violation is harmless, and we know the server cannot send more untagged
status responses.
Analysis and fix courtesy of Maciej S. Szmigiero, GitLab merge request !20.
* The configure script now spends more effort for getting --with-ssl right, by
running pkg-config in the right environment, and using the AC_LIB_LINKFLAGS
macro to obtain run-time library path setting flags.
* For typical POP3/IMAP ports 110, 143, 993, 995, if port and --ssl option
do not match, emit a warning and continue. Closes Gitlab #31.
* There is now a --idletimeout feature contributed by Eric Durand, to
permit setting a shorter timeout for the --idle option, because many
servers violate the protocol (requiring 30 minutes) and hang up sooner than
the 28 minutes fetchmail waits before refreshing IDLE.
GitLab merge request !35.
* There is now a --forceidle feature to force idle mode even if not advertised
in the server capabilities. This is a dangerous option, use it carefully.
Courtesy of Eric Durand, GitLab merge request !39.
* There is now a --moveto feature (only feasible in IMAP) that, instead of
flushing mail, moves it to a user-specified folder. This is to assist with
archiving, or when providers (G...) break the IMAP model.
Courteously provided by Damjan Jovanovic.
* rcfile parsing errors are now reported in more detail, and with -vv mode,
also lead to a non-importable Python dump of what was obtained, for debugging.
* fetchmail's --auth option ssh was renamed to implicit, to make clear that it
does *NOT* imply any particular type or features of the --plugin. --auth ssh
will be understood for a while for compatibility but fetchmail will report it
as implicit.
* fetchmail no longer warns about port/service mismatches with/without ssl
option when a "plugin" is in use because fetchmail cannot know whether the
plugin talks SSL or STARTTLS/STLS. Fixes Debian Bug#1076604.
* fetchmail re-executes itself if the .netrc file's modification change
is found to be newer at the beginning of a new run.
* fetchmail can now use other digest algorithms than MD5 for the
--sslfingerprint option. To use, specify the algorithm's name in
curly braces as prefix in the finger print, say,
--sslfingerprint '{SHA256}00:01:[...]:1F'. This will also switch the
algorithm for printing. All algorithms supported by the TLS/SSL library
can be specified. Fixes Gitlab issue #19, Debian Bug#700266.
EXPERIMENTAL CHANGES - these are not documented anywhere else, only here:
* fetchmail supports a FETCHMAIL_SSL_SECLEVEL environment variable that
can be used to override the OpenSSL security level. Fetchmail by default
raises the security level to 2 if lower. This variable can be used to lower it.
Use with extreme caution. Note that levels 3 or higher will frequently cause
incompabilities with servers because server-side data sizes are often too low.
Valid range: 0 to 5 for OpenSSL 1.1.1 and 3.0.
* fetchmail supports a FETCHMAIL_SSL_CIPHERS environment variable that
sets the cipher string (through two different OpenSSL functions) for SSL and
TLS versions up to TLSv1.2.
If setting the ciphers fails, fetchmail will not connect.
If not given, defaults to Postfix's "medium" list,
"aNULL:-aNULL:HIGH:MEDIUM:+RC4:@strength".
* fetchmail supports a FETCHMAIL_TLS13_CIPHERSUITES environment variable
that sets the ciphersuites (a colon-separated list, without + ! -) for
TLSv1.3. If not given, defaults to OpenSSL's built-in list. If setting the
ciphersuites fails, fetchmail refuses to connect.
* NOTE the features above are simplistic. For instance, even though you
configure --sslproto tls1.3, a failure to set tls1.2 ciphers could cause
a connection abort.
* fetchmail can be built with meson 1.30 or newer <https://mesonbuild.com/>.
fetchmail is not currently written in a way that supports unity
(amalgamated) builds.
Signed-off-by: Adolf Belka <[email protected]>
Signed-off-by: Arne Fitzenreiter <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove unnecessary code for setting colors on rows.