From: Alexis Lothoré
Add a "-l"/"--limit" option to allow changing the display limit in
resulttool.
- If no value is passed, resulttool uses its default value.
- If 0 is passed, the display limit is removed and every regression will be
displayed
- If a custom value is passed, this value
From: Alexis Lothoré
Since "matched" and "improved" tests are not as important as regressions,
reduce the place they take in the regression report:
- merge "matched" and "improved" tests, while removing the label
- add a single line of additional info per pair
Those changes make the "Matches
tegory suffers the same status (test missing, test failing, test
skipped, etc)
Prevent those huge, worthless lists by limiting the output for each test
group:
- current default limit is arbitrarily set to 50
- limit can still be overriden with a new "-l"/"--limit" flag,
It has been observed that useful information in regression report can be
drowned in huge regression lists which are often false-positives (for
example, a whole set of tests has been temporarily disabled). Additionally,
the regression report usually starts with not-so-useful information when
On 10/20/23 18:05, pete wrote:
Hi Folks
Well this normally runs so smooth it is crazy but today
...
I don't use kde any longer - but part of your problem is likely orphaned
packages.
you should remove kfloppy and telepathy-kde-contact-runner
for starters and any other orphans you find.
On 20/10/2023 14:41, Richard Biener wrote:
On Fri, 20 Oct 2023, Andre Vieira (lists) wrote:
Hi,
This patch stops lowering of bitfields by ifcvt when they have non-constant
offsets as we are not likely to be able to do anything useful with those
during
vectorization. That also fixes
Hi,
This patch stops lowering of bitfields by ifcvt when they have non-constant
offsets as we are not likely to be able to do anything useful with those
during
vectorization. That also fixes the issue reported in PR 111882, which was
being caused by an offset with a side-effect being lowered,
Hello,
I am trying to use selinux (refpolicy-targeted) in read-only root filesystem
with kirkstone. Volatile-binds recipe create overlays, but we have multiple
selinux denied logs (even with allow_mount_anyfile boolean set to on).
Most of them are because scontext is
If the distro feature usrmerge is set, all files from /bin are moved to
/usr/bin, i.e. /usr/bin/sh is the same as /bin/sh and should be allowed be
ignored, because it's always present.
Signed-off-by: Jörg Sommer
---
meta/classes-global/insane.bbclass | 4
1 file changed, 4 insertions(+)
Hello Alexandre,
On 10/20/23 08:05, Alexandre Belloni via lists.openembedded.org wrote:
> Hello Alexis,>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/5886/steps/14/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5935/steps/14/logs/stdio
>
base and target
2. Different HOSTS _can_ be cross-checked
But the issue you are pointing tends to show it does not work well in some
cases. I will have to do some tests to see if dropping 2. reduce this noise
without loosing valuable data, or if we need to find something smarter
>
> The report
It has been observed that useful information in regression report can be
drowned in huge regression lists which are often false-positives (for
example, a whole set of tests has been temporarily disabled).
This series brings a default limit to how many changes are displayed per
base/target
From: Alexis Lothoré
Add a "-l"/"--limit" option to allow changing the display limit in
resulttool.
- If no value is passed, resulttool uses its default value.
- If 0 is passed, the display limit is removed and every regression will be
displayed
- If a custom value is passed, this value
tegory suffers the same status (test missing, test failing, test
skipped, etc)
Prevent those huge, worthless lists by limiting the output for each test
result pair:
- current default limit is arbitrarily set to 50
- limit can still be overriden with a new "-l"/"--limit" flag,
Hello,
On 10/18/23 08:16, Pokybuild User wrote:
>
> A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder
> and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc1
The regression report looks worryingly empty. It has been generated
and argument types have been vectorized.
On 04/10/2023 13:40, Andre Vieira (lists) wrote:
On 04/10/2023 11:41, Richard Biener wrote:
On Wed, 4 Oct 2023, Andre Vieira (lists) wrote:
On 30/08/2023 14:04, Richard Biener wrote:
On Wed, 30 Aug 2023, Andre Vieira (lists) wrote
Rebased, no major changes, still needs review.
On 30/08/2023 10:19, Andre Vieira (lists) via Gcc-patches wrote:
This patch finalizes adding support for the generation of SVE simd
clones when no simdlen is provided, following the ABI rules where the
widest data type determines the minimum
Rebased on top of trunk, minor change to check if loop_vinfo since we
now do some slp vectorization for simd_clones.
I assume the previous OK still holds.
On 30/08/2023 13:54, Richard Biener wrote:
On Wed, 30 Aug 2023, Andre Vieira (lists) wrote:
When analyzing a loop and choosing
Refactor simd clone handling code ahead of support for poly simdlen.
gcc/ChangeLog:
* omp-simd-clone.cc (simd_clone_subparts): Remove.
(simd_clone_init_simd_arrays): Replace simd_clone_supbarts with
TYPE_VECTOR_SUBPARTS.
(ipa_simd_modify_function_body):
Rebased, needs review.
On 30/08/2023 10:13, Andre Vieira (lists) via Gcc-patches wrote:
This patch enables the compiler to use inbranch simdclones when
generating masked loops in autovectorization.
gcc/ChangeLog:
* omp-simd-clone.cc (simd_clone_adjust_argument_types): Make function
helper function.
On 30/08/2023 13:54, Richard Biener wrote:
On Wed, 30 Aug 2023, Andre Vieira (lists) wrote:
The vect_get_smallest_scalar_type helper function was using any argument to a
simd clone call when trying to determine the smallest scalar type that would
be vectorized. This included
Posting the changed patch for completion, already reviewed.
On 30/08/2023 13:32, Richard Biener wrote:
On Wed, 30 Aug 2023, Andre Vieira (lists) wrote:
Teach parloops how to handle a poly nit and bound e ahead of the changes to
enable non-constant simdlen.
Can you use poly_int_tree_p
Just posting a rebase for completion.
On 30/08/2023 13:31, Richard Biener wrote:
On Wed, 30 Aug 2023, Andre Vieira (lists) wrote:
SVE simd clones require to be compiled with a SVE target enabled or the
argument types will not be created properly. To achieve this we need to copy
confusing with removing and adding patches to the series.
On 30/08/2023 09:49, Andre Vieira (lists) via Gcc-patches wrote:
Hi,
This patch series aims to implement support for SVE simd clones when not
specifying a 'simdlen' clause for AArch64. This patch depends on my
earlier patch: '[PATCH] aarch64
So OK to commit this?
This patch makes sure the profile_count information is initialized for
the new
bb created in move_sese_region_to_fn.
gcc/ChangeLog:
* tree-cfg.cc (move_sese_region_to_fn): Initialize profile_count for
new basic block.
Bootstrapped and regression tested
Hey,
Just a minor update to the patch, I had missed the libgomp testsuite, so
had to make some adjustments there too.
gcc/ChangeLog:
* config/aarch64/aarch64.cc (lane_size): New function.
(aarch64_simd_clone_compute_vecsize_and_simdlen): Determine
simdlen according to NDS
If the ipv6 feature for the distribution is not set, the package should not
contain settings for ipv6. This makes rpcbind doesn't try to bind to a IPv6
socket, and complain that this fails.
Signed-off-by: Jörg Sommer
---
.../libtirpc/libtirpc/ipv6.patch | 52 +++
If a distribution doesn't provide IPv6, the mapping of localhost and ::1 has
to be removed.
Signed-off-by: Jörg Sommer
---
meta/recipes-core/base-files/base-files_3.0.14.bb | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb
On 16/10/2023 08:51, Dale wrote:
Anyone here have ideas? Keep in mind, that thing uses systemd. I
thought I hated that before. I truly hate that thing now. Trying to
figure out how to restart something is like pulling teeth with no pain
meds.
systemctl restart servicename?
I like
On 05/09/2023 16:00, Richard Sandiford via Gcc-patches wrote:
> Szabolcs Nagy writes:
>> Update tests for the new branch-protection parser errors.
>>
>> gcc/testsuite/ChangeLog:
>>
>> * gcc.target/aarch64/branch-protection-attr.c: Update.
>> *
On 12 October 2023 21:13, Dan McGregor wrote:
> On Thu, 12 Oct 2023 at 11:10, Jörg Sommer via lists.openembedded.org
> wrote:
> >
> > This is only a minor change, because oelint-adv had warned about the space
> > after " of PACKAGECONFIG.
> >
> >
> > From:
This is only a minor change, because oelint-adv had warned about the space
after " of PACKAGECONFIG.
From: openembedded-core@lists.openembedded.org
on behalf of Jörg Sommer via
lists.openembedded.org
Sent: Thursday, 12 October 2023 18:34
To:
If the ipv6 feature for the distribution is not set, the package should not
contain settings for ipv6. This makes rpcbind doesn't try to bind to a IPv6
socket, and complain that this fails.
Signed-off-by: Jörg Sommer
---
.../libtirpc/libtirpc/ipv6.patch | 52 +++
If the ipv6 feature for the distribution is not set, the package should not
contain settings for ipv6. This makes rpcbind doesn't try to bind to a IPv6
socket, and complain that this fails.
Signed-off-by: Jörg Sommer
---
.../libtirpc/libtirpc/ipv6.patch | 52 +++
If the ipv6 feature for the distribution is not set, the package should not
contain settings for ipv6. This makes rpcbind doesn't try to bind to a IPv6
socket, and complain that this fails.
Signed-off-by: Jörg Sommer
---
meta/recipes-extended/libtirpc/libtirpc_1.3.2.bb | 14 +-
1
The recipe *podman* requires the distro feature *ipv6*. Using a distro
without it causes the build of *packagegroup-container* fails, even if
*packagegroup-podman* is not used:
ERROR: Nothing RPROVIDES 'podman' (but
On 11/10/2023 17:44, Philip Webb wrote:
231011 Alan McKinnon wrote:
Today a sync and emerge world produces a huge list of blockers.
qt 5.15.10 is currently installed and qt 5.15.11 is new in the tree and
being blocked.
All the visible blockers are Qt itself so --verbose-conflicts is needed.
On 11/10/2023 14:56, Jeff Law wrote:
>
>
> On 10/11/23 04:39, Florian Weimer wrote:
>> I've started to look at what it is required to convert the testsuite to
>> C99 (without implicit ints, without implicit function declarations, and
>> a few other legacy language features).
> I bet those older
On Wed, October 11, 2023 10:44 pm, Matus UHLAR - fantomas wrote:
> On 11.10.23 22:21, li...@sbt.net.au wrote:
> Here is your 5-minute delay. It's possible that scanning took too much of
> time. Perhaps too many concurrent amavis sessions?
from htop , by CPU %
PID USER PRI NI VIRT
On 11/10/2023 09:58, Andrew Stubbs wrote:
> On 11/10/2023 07:54, Chung-Lin Tang wrote:
>>
>>
>> On 2023/10/10 11:11 PM, Andrew Stubbs wrote:
>>> Hi all,
>>>
>>> I'm trying to add a new register set to the GCN port, but I've hit a
>>> problem I don't understand.
>>>
>>> There are 256 new registers
The recipe *podman* requires *ipv6* in *DISTRO_FEATURES*, which causes the
build of the whole recipe fail, even if packagegroup-podman is not used.
Signed-off-by: Jörg Sommer
---
recipes-core/packagegroups/packagegroup-container.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On 10/10/23 11:30, Alexis Lothoré via lists.openembedded.org wrote:
> With those two patches, I have been able to properly generate the
> regression report from [1] with the following command:
It looks like I forgot to paste the relevant command. Here it is, for
documentation purpose:
On 09/10/2023 14:12, Victor Do Nascimento wrote:
>
>
> On 10/7/23 12:53, Richard Sandiford wrote:
>> Richard Earnshaw writes:
>>> On 03/10/2023 16:18, Victor Do Nascimento wrote:
In implementing the ACLE read/write system register builtins it was
observed that leaving argument type
On 10/10/23 07:00, Erich Eckner wrote:
Hi,
...
This is (one possibility for) the second option, that I mentioned, which
I was afraid might break a lot of stuff on my machines :-/
I meant put it in /usr/local/xxx/ not directly in /usr/local.
Or in /opt/xxx/
I see, that the root cause (and
On 10/10/2023 11:46, Richard Earnshaw (lists) via Gcc wrote:
> On 10/10/2023 10:47, Florian Weimer via Gcc wrote:
>> Currently, -fsigned-char and -funsigned-char are only documented as C
>> language options, although they work for C++ as well (and Objective-C
>> and Objective
On 10/10/2023 10:47, Florian Weimer via Gcc wrote:
> Currently, -fsigned-char and -funsigned-char are only documented as C
> language options, although they work for C++ as well (and Objective-C
> and Objective-C++, I assume, but I have not tested this). There does
> not seem to be a place for
From: Alexis Lothoré
Whenever we ask gitarchive to retrieve test results for specific revisions,
we first do a "large" search in get_tags, which uses glob patterns with git
ls-remote, and then we filter received tags with a regex to parse the tags
fields.
Currently gitarchive assumes that all
There are still issues in Autobuilder when trying to generate regression
reports on master-next branch, as visible in [1]. This issue makes build
status as failed
After being finally able to replicate the issue locally (which is quite
difficult since master-next is a force-pushed branch), I
From: Alexis Lothoré
Whenever we ask gitarchive to search for tags, we can provide it with a
pattern (containing glob patterns). However, when searching for example for
tags matching branch master-next, it can find more tags which does not
correspond exactly to branch master-next (e.g.
On 10/10/23 02:41, Erich Eckner wrote:
Hi fellow-archers,
Hi!
I have two packages, A and B, which both provide the same file X.
...
Without knowing more its a bit hard to say.
For example are A and B actually the same application but different
versions (git vs stable). If so, then just
On 10/7/23 02:59, Zener wrote:
Hi.
[opencl_init] could not get platforms: Unknown OpenCL error
[opencl_init] FINALLY: opencl is NOT AVAILABLE and NOT ENABLED.
I dont use this but the docs [1] have a (long) list of requirements that
must be met to use it. It sounds like or more is
Just an FYI for you all, Netcraft have been flagging the contents of the
/error/ folder (a bunch of basic plain HTML) as phishing.. They de-listed the
ones I responded to and have a separate ticket with them about the issue in
general - they have acknowledged it is a mistake..
I do wonder if
Hallo,
ich fände es sehr nützlich! Letztes Mal hatten wir tatsächlich genau das
Problem, dass unserer Tisch nicht so erkennbar war.
Zu den anderen HalLEipziger·innen: soll ich einfach eine OSM-Fahne für
unseren Stammtisch bestellen?
Ich hätte übrigens Lust, uns bald noch mal zu treffen :)
o about ptest such as
"begin", "end", "duration", "exitcode" or "timeout". Another example is a
"reproducible" section, which does not have a "status" field but rather
contains a big "files" entry containing lists of identic
On 28/09/2023 12:55, Siddhesh Poyarekar wrote:
> +Security features implemented in GCC
> +
> +
[...]
> +
> +Similarly, GCC may transform code in a way that the correctness of
> +the expressed algorithm is preserved, but supplementary properties
> +
Signed-off-by: Jörg Sommer
---
meta-oe/recipes-extended/collectd/collectd_5.12.0.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta-oe/recipes-extended/collectd/collectd_5.12.0.bb
b/meta-oe/recipes-extended/collectd/collectd_5.12.0.bb
index 479c12d6a..bd4a5b3e8 100644
On 04/10/2023 11:41, Richard Biener wrote:
On Wed, 4 Oct 2023, Andre Vieira (lists) wrote:
On 30/08/2023 14:04, Richard Biener wrote:
On Wed, 30 Aug 2023, Andre Vieira (lists) wrote:
This patch adds a new target hook to enable us to adapt the types of return
and parameters of simd
On 30/08/2023 14:04, Richard Biener wrote:
On Wed, 30 Aug 2023, Andre Vieira (lists) wrote:
This patch adds a new target hook to enable us to adapt the types of return
and parameters of simd clones. We use this in two ways, the first one is to
make sure we can create valid SVE types
Some failures have been observed on jobs targeting master-next, with the
following logs as an example:
Exception: No reference found for commit
3edb9acca18171894771c36c19b0c2e905852ce5 in /tmp/sendqaemail.dkwg__g9
See [1] for more logs, which is trying to compare master-next results to
master
From: Alexis Lothoré
Test results repository url is used at least twice, so define a constant
holding the url instead of hardcoding it multiple times
Signed-off-by: Alexis Lothoré
---
scripts/send_qa_email.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
From: Alexis Lothoré
There are some inversions in words used to describe elements of comparison
for regression reporting: the main function of send_qa_email starts using
"base" to talk about the target revision and "compare" to talk about the
reference against which it is compared. Then later in
From: Alexis Lothoré
It has been observed that some regression reports generation may failed
when the comparision base is a branch (e.g master) because we can not find
any test results associated to the branch HEAD. This is especially true for
branches which often change, because not all
I think it is going to have to happen. We have several folks on the IX and
various consulting clients who only need 3-6 Ips but have to burn a full /24 to
participate in BGP. I wrote a blog post awhile back on this topic
Hi Honza,
My current patch set for AArch64 VLA omp codegen started failing on
gcc.dg/gomp/pr87898.c after this. I traced it back to
'move_sese_region_to_fn' in tree/cfg.cc not setting count for the bb
created.
I was able to 'fix' it locally by setting the count of the new bb to the
On 31/08/2023 07:39, Richard Biener wrote:
On Wed, Aug 30, 2023 at 5:02 PM Andre Vieira (lists)
wrote:
On 30/08/2023 14:01, Richard Biener wrote:
On Wed, Aug 30, 2023 at 11:15 AM Andre Vieira (lists) via Gcc-patches
wrote:
This patch adds a machine_mode parameter
Hi,
On 14/09/2023 13:10, Kyrylo Tkachov via Gcc-patches wrote:
Hi Stam,
The arm parts look sensible but we'd need review for the df-core.h and
df-core.cc changes.
Maybe Jeff can help or can recommend someone to take a look?
Thanks,
Kyrill
FWIW the changes LGTM, if we don't want these
On 26/09/2023 17:37, Andrew Stubbs wrote:
I don't have authority to approve anything, but here's a review anyway.
Thanks for working on this.
Thank you for reviewing and apologies for the mess of a patch, may have
rushed it ;)
diff --git a/gcc/testsuite/gcc.dg/vect/vect-simd-clone-19.c
On 26/09/2023 21:26, Bernhard Reutner-Fischer wrote:
On 26 September 2023 18:46:11 CEST, Tobias Burnus
wrote:
On 26.09.23 18:37, Andrew Stubbs wrote:
If the fall-through is deliberate please add a /* FALLTHROUGH */
comment (or whatever spelling disables the warning).
It's:
On 26/09/2023 17:48, Jakub Jelinek wrote:
On Tue, Sep 26, 2023 at 05:24:26PM +0100, Andre Vieira (lists) wrote:
@@ -5816,6 +5817,18 @@ get_references_in_stmt (gimple *stmt, vec *references)
}
case IFN_MASK_LOAD:
case IFN_MASK_STORE:
+ case
The const attribute is ignored when simdclone's are used inbranch. This
is due to the fact that when analyzing a MASK_CALL we were not looking
at the targeted function for flags, but instead only at the internal
function call itself.
This patch adds code to make sure we look at the target
On 26/09/2023 14:46, Wilco Dijkstra wrote:
>
> The outline atomic functions have hidden visibility and can only be called
> directly. Therefore we can remove the BTI at function entry. This improves
> security by reducing the number of indirect entry points in a binary.
> The BTI markings on
On 9/24/23 07:22, Genes Lists wrote:
nft -c nftables.conf
typo - should be:
nft -c -f nftables.conf
gene
On 9/24/23 02:52, David C. Rankin wrote:
On 9/23/23 12:51, Christian wrote:
In addition to the workstation (single interface) nftables example, I
have just uploaded an example of nftables firewall rules. i.e. for a
router with 2 interfaces that sits between the internet and internal
On 9/23/23 13:51, Christian wrote:
...
In case of interest, the nft rules that I shared with David previously
are available here [1].
This is a sample nftables ruleset for a laptop or workstation.
It allows established / related packets to come back. These packets are
returned after a
On 19/09/2023 10:13, Dale wrote:
That's a interesting way to come up with passwords tho. I've seen that
is a few whodunit type shows. Way back in the old days, they had some
interesting ways of coding messages. Passwords are sort of similar.
Back when we were busy conquering India ...
The
On 20/09/2023 19:05, Frank Steinmetzger wrote:
In principle, a repeated space character in your passphrase could help
reduce the computational burden of an offline brute force attack, by e.g.
helping an attacker to identify the number of individual words in a
passphrase.
Due to the rotation,
On 19/09/2023 10:10, Jude DaShiell wrote:
Once the set spots got figured
five dice got used for letters add the total and subtract 4 for the
particular letter.
Which actually isn't random. It's a bell curve peaking probably between
J and M. Think, if you throw 2 dice, there are 36 possible
On 20/09/2023 23:39, Grant Edwards wrote:
Assuming GParted is smart enough to do overlapping moves, is it smart
enough to only copy filesystem data and not copy "empty" sectors?
According to various forum posts, it is not: moving a partion copies
every sector. [That's certainly the obvious, safe
On 20/09/2023 14:50, Wilco Dijkstra wrote:
>
> The cpymemdi/setmemdi implementation doesn't fully support strict alignment.
> Block the expansion if the alignment is less than 16 with STRICT_ALIGNMENT.
> Clean up the condition when to use MOPS.
>
> Passes regress/bootstrap, OK for commit?
>
On 9/20/23 04:36, David C. Rankin wrote:
Archdevs,
Depending on how restrictive the iptables rules, if the IP for
archlinux-keyring-wkd-sync falls into a blocked range, the logs quickly
fill. An idea is to have the service insert a temporary rule to either
(1) allow the IP for the sync
On Sun, September 17, 2023 4:45 pm, Patrick Ben Koetter wrote:
Benny, Patrick, thanks
> Even simplier than that:
> $ postconf -d mynetworks
> mynetworks = 127.0.0.0/8 192.168.179.0/24 192.168.122.0/24 [::1]/128
> [fd00:0:0:1::]/64 [fe80::]/64
that includes 2nd ethernet, eth1, do I need to keep
On 18/09/2023 11:13, Frank Steinmetzger wrote:
With so many drives, you should also include a pricey power supply. And/or a
server board which supports staggered spin-up. Also, drives of the home NAS
category (and consumer drives anyways) are only certified for operation in
groups of up to
On 18/09/2023 12:16, Rich Freeman wrote:
This is part of why I like storage implementations that have more
robustness built into the software. Granted, it is still only as good
as your clients, but with distributed storage I really don't want to
be paying for ECC on all of my nodes. If the
On 19/09/2023 00:40, Dale wrote:
I get it when you wanna do it your way because it always worked™ (which is
not wrong — don’t misunderstand me) and perhaps you had some bad experience
in the past. OTOH it’s a pricey component usually only needed by gamers and
number crunchers. On-board graphics
On 17/09/2023 19:37, Michael wrote:
However, unlike locate, baloo is meant to index not just file names, but also
metadata tags and relationships relevant to files, emails and contacts. Its
devs would argue it has a small footprint. So it is meant to be*more* than a
simple file name indexer.
On 17/09/2023 19:35, Peter Böhm wrote:
Am Sonntag, 17. September 2023, 19:46:05 CEST schrieb Wols Lists:
It always annoys me, but baloo seems to be being an absolute nightmare
at the moment.
I tried to kill it and it appears to have just restarted. Is there a use
flag I can use to just get
It always annoys me, but baloo seems to be being an absolute nightmare
at the moment.
Iirc, it's "the file indexer for KDE" - in other words it knackers your
response time reading all the files, wastes disk space building an
index, and all for what?
So that programs you never use can a bit
Hi:
I believe that bash 5.2 was/is held back due to incompatible Changes
with 5.1 [1].
The obvious first thought would be to set BASH_COMPAT="5.1" globally and
then update to the current 5.2 version.
This would work for any shell which sees the BASH_COMPAT variable.
User login shells,
I;m just checking my amavis setup, under mynetworks I have:
@mynetworks = qw( 127.0.0.0/8 [::1] [FE80::]/10 [FEC0::]/10
10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 );
should I also include actual server IP ?
in postfix main.cf I have several IPs (server backup server):
mynetworks
From: Pavel Zhukov
Without specifing runstatedir tmpfiles.d is configured to use /var/run
for dbus and this causes deprecation warnings in system logs.
(From OE-Core rev: 4df1a16e5c38d0fb724f63d37cc032aa37fa122f)
Signed-off-by: Pavel Zhukov
Signed-off-by: Luca Ceresoli
Signed-off-by: Richard
Hello,
the patch »dbus: Specify runstatedir configure option« [1] is in the master
branch, but not in the kirkstone branch. Is it possible to get it applied
there, too? Whom can I ping for this?
[1]
On 9/14/23 14:34, Polarian wrote:
Hello,
...
- DKIM signatures are broken in transit, and ...
...
hi
There was a discussion of DKIM and mail list back last October [1].
There was, and seems still is, an open mailman issue [2].
The Arch thread is informative, in particular around
Maybe there should be a general good-practice recommendation / policy
that bots running in this fashion to keep things in sync should only
automatically add/update/remove a tag that they've previously set if
the current state/value in OSM is unchanged from the last state/value
that the bot set.
and can't run at
full pelt anyway ...
You might find it's actually better (and more efficient) to run at lower
loading. Certainly following the kernel lists you get the impression
that the CPU regularly goes into thermal throttling under heavy load,
and also that using a couple of cores lightly
On Sun, September 10, 2023 2:03 am, Viktor Dukhovni via Postfix-users wrote:
> Hard to say, you're not well prepared to isolate the issue, and
> the symptoms are diverse.
Viktor, Matus, many thanks!!
Viktor, I think and I'm afraid you've hit the nail on the head... that's
certainly large if not
September 18.
-Original Message-
From: macvisionaries@googlegroups.com On
Behalf Of Lorie McCloud
Sent: Wednesday, September 13, 2023 7:11 AM
To: via MacVisionaries
Subject: IOS17
does anybody know when IOS17 will be formally released? I ask because I try to
run 1 behind the current
On 11/09/2023 16:22, Jonathan Wakely via Gcc-patches wrote:
> On Mon, 11 Sept 2023 at 14:57, Christophe Lyon
> wrote:
>>
>>
>>
>> On Mon, 11 Sept 2023 at 15:12, Jonathan Wakely wrote:
>>>
>>> On Mon, 11 Sept 2023 at 13:36, Christophe Lyon
>>> wrote:
On Mon, 11 Sept 2023 at
On 11/09/2023 16:22, Jonathan Wakely via Gcc-patches wrote:
> On Mon, 11 Sept 2023 at 14:57, Christophe Lyon
> wrote:
>>
>>
>>
>> On Mon, 11 Sept 2023 at 15:12, Jonathan Wakely wrote:
>>>
>>> On Mon, 11 Sept 2023 at 13:36, Christophe Lyon
>>> wrote:
On Mon, 11 Sept 2023 at
On 08/09/2023 19:18, Siddhesh Poyarekar wrote:
> Hello,
>
> I want to begin by apologizing because I know from first hand experience that
> scheduling can be an immensely painful job.
>
> The Cauldron 2023 schedule[1] looks packed and I noticed that Qing and
> David's talks on security
On Sat, September 9, 2023 9:00 pm, Matus UHLAR - fantomas via
Postfix-users wrote:
>> On Sat, September 9, 2023 2:42 am, Matus UHLAR - fantomas via
>> Postfix-users wrote:
Matus, Michel, thanks
> did you reorder those lines? look at timestamps.
didn't intend to, but maybe stuffed up when I've
401 - 500 of 37076 matches
Mail list logo
