Seconding that, the did, at least in the past, and they do interpret the severity of
deviations differently than the written standard.
On 24.10.23 14:26, Michael Catanzaro wrote:
On Tue, Oct 24 2023 at 08:06:12 AM -0400, Neal Gompa wrote:
The two tools don't have incompatible ideas of valid
Hi list,
just a heads up: because we're talking about how to validate appstream metadata: When
validating metadata, one of the "default" warnings you get is:
> In the past, mailto: URL schemas to link to email addresses were also supported for
this URL type. It is recommended to not use them
Hi Marius,,
I'd also point out that if you want to inform the security team about something, you
should inform directly – and it seems you've done that, by properly labeling that issue
(which I can't read at all) as sensitive. As the others pointed out, there's nothing that
can be done
I must say that I found appstreamcli to be to unstable in CI of projects that I used to
maintain, and file format documentation and validator source code reality diverge, and
behaviour is understandably changed between appstreamcli revisions. We had to disable and
later re-enable the metainfo
Just realized:
- using avahi for local peer discovery, how does this compare to good ole bittorrent with
Protocol/Message Stream Encryption turned on, and DHT instead of a tracker?
- I guess the "self-signed certificate" discussion stems from the fact that TLS assumes
you have certificates –
That sounds very good, and having a libs package desirable anyway should more
consumers pop up
On 25.08.23 20:43, Richard Hughes wrote:
On Fri, 25 Aug 2023 at 19:34, Richard Hughes wrote:
Yes, that's what I have right now. I do need to split out a
passim-libs so that you can remove the
Hi Richard,
On 25.08.23 19:24, Richard Hughes wrote:
So that's the thing; if it's default disabled then I can say with
certainty that almost nobody will use it and we won't see any
reduction in network traffic at all.
I fully agree with that assessment. "Here's a knob you turn that has the
Hi Sumantro and Debarshi, hi fellow podman users,
trying to wade through all this: I don't think there's anything podman can do to solve
this now.
Background:
- the container format metadata has a field for|RLIMIT_NPROC (i.e., what you set via
`ulimit -u`)|
|- this field is optional, but
Because it's typically not an option in these kinds of VMs – you'd need
to create a swapfile, enable it, before you could launch the first DNF
command. Ideally, disable it after, as chances are a certain bookseller
is billing you per IOPS.
It's completely out of the questions for (e.g.
Wait, getting a legal opinion on code is an option? Even if the code is
GPLv3 but fedora removes some part of it out of fear it *might* infringe
patent.
Cheers,
Marcus
On 8/6/22 19:49, Gary Buhrmaster wrote:
On Sat, Aug 6, 2022, 10:35 AM Richard Fontana wrote:
[re FDK-AAC, which has
Uff, that thread has been a … sobering read, on a technical and human level.
Thank you for linking me to it!
Best regards,
Marcus
On 26.07.22 09:58, Peter Oliver wrote:
On Sat, 23 Jul 2022, Marcus Müller wrote:
On 23.07.22 01:37, Peter Oliver wrote:
The emacs developers discourage use
ah, true, different sonames solves this :)
On 28.07.22 10:52, Daniel P. Berrangé wrote:
On Thu, Jul 28, 2022 at 10:44:14AM +0200, Marcus Müller wrote:
The latter change seems unwise. Packages which now depend on minizip (to be
minizip-ng) will continue to do depend on whatever Provides(minizip
The latter change seems unwise. Packages which now depend on minizip (to be minizip-ng)
will continue to do depend on whatever Provides(minizip); if you rename the zlib
subpackage to minizip, they will depend on the wrong thing.
Cheers,
Marcus
On 28.07.22 10:31, Lukas Javorsky wrote:
Hi
Oh, I wasn't aware of that, is there somewhere I can read up on that?
On 23.07.22 01:37, Peter Oliver wrote:
On Mon, 18 Jul 2022, Marcus Müller wrote:
Since the pgtk toolkit supports both X and wayland under the hood, I'd very much
propose that we do not only package an emacs-pgtk binary
native compilation is also enabled, so maybe something
slipped through a little early?
Cheers,
Marcus
On 20.07.22 21:36, Kevin P. Fleming wrote:
On 7/20/22 14:57, Marcus Müller wrote:
Oh! That comes as a surprise. Let me try a rebuild!
:( I was really looking forward to emacs-pgtk.
Forgive my r
Oh! That comes as a surprise. Let me try a rebuild!
:( I was really looking forward to emacs-pgtk.
Best regards,
Marcus
On 19.07.22 11:53, Jens-Ulrik Petersen wrote:
On Tue, Jul 19, 2022 at 5:14 AM Marcus Müller wrote:
Since the pgtk toolkit supports both X and wayland under the hood
Dear Bhavin,
A big "yay!" for packaging 28.1; I've been running my own emacs.spec modifications to play
around with this, for one reason, and one reason alone:
PGTK support. Without it, emacs is virtually unusable on Wayland on hidpi screens with the
compositors I've used, as xwayland simply
17 matches
Mail list logo
