Dominik 'Rathann' Mierzejewski writes:
> I guess it could be fixed with a clean-room reimplementation of the
> stripped parts of FDK-AAC.
Clean-room reimplementation negates the very applicability of any
pre-existing *copyright* to your work. It does not affect applicability
of pre-existing
Stephen John Smoogen writes:
> I believe those need to be tied into a couple of other questions
> 1. How does any organization work with these various prominent vendors?
I doubt that this is a very useful question as stated. Even
near-peers like Red Hat itself and Ubuntu are probably
Lukas Javorsky writes:
> I want to apologize one more time.
> This experience will be written in my mind forever.
Try not to punish yourself. A good friend once completely broke
XEmacs by bumping the version number in version.el from "20.0-betaXX"
to "20.0". (It turned out that somebody had
Frank Ch. Eigler writes:
> adamwill wrote:
> > Freenode has also shut down every channel that posted a libera.chat
> > link in its topic. That's not very 'trustworthy'. This happened to
> > multiple Fedora-related projects/channels, including #cockpit , for
> > instance.
>
> Those
Peter Hutterer writes:
> Now that the XorgUtilityDeaggregation [1] is complete, I'm planning to
> retire a set of old X utilities that I think don't need to be in Fedora:
>
> oclock
> xbiff
> xload
> xman
> xrefresh
> xlogo
> xpr
> xfd
> viewres
> listres
> xconsole
Wow. Can't
Jerry James writes:
> On Thu, Dec 31, 2020 at 5:37 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> > Normally, I'd be in favour of "dragging out" the removal a bit, but
> > in this case I think we don't need to, because of the relatively
> > close replacement and the small number of users.
It's
I'm really uncomfortable about the amount of crossp-posting, so I'm
limiting this to devel@ (I receive it) and test@ (obvious to me why
relevant).
Kamil Paral writes:
> Adam writes:
> > Arguably the environment from which they logged in is not
> > "working as expected" if you can't then log
Nicolas Mailhot via devel writes:
> Practically some people do care about original English. And, there is
> little to win deployment side,
In theory there is: common local names of people, places, and
organizations. I don't know how many of those English variants
include very many of them,
Jerry James writes:
> My experience is that the build dependencies in the opam files are of
> high quality, but that test and documentation dependencies are often
> omitted. We could add those manually, so that may not be a big deal.
If you add them manually, maybe upstream would accept a
Paul Dufresne via devel writes:
> Now I do believe the reason you need to give a version to shared
> libraries is because of the FHS. Because FHS suggest to regroup
> libraries inside a specific directory and/or directories. But if you
> have a common directory that contains every packages
Jerry James writes:
> I think Richard addressed most of the points you raised.
Yes, and no new questions, either. So I think I'm done here (well,
I'll spectate, but the internals of the OCaml compiler are well beyond
my skillset :-).
Good luck!
Steve
--
Associate Professor
Hi Jerry! Long time no see.
Jerry James writes:
> I built the whole stack for Rawhide with no issues.
Zero compiler warnings? No fiddling to suppress compiler warnings
*anywhere* in the build chain (whether options or pragmas)?
Not suggesting you go looking for pragmas (probably have 10
Nico Kadel-Garcia writes:
> On Thu, Jan 16, 2020 at 10:53 PM Jerry James wrote:
> >
> > On Thu, Jan 16, 2020 at 8:29 PM Nico Kadel-Garcia wrote:
> > > The lack of a good backup tool for Berkeley DB earned me nearly a year
> > > of contracting salary from the BBC to keep alive an obsolete
Matthew Miller writes:
> On Sun, May 05, 2019 at 12:43:02PM -0700, stan via devel wrote:
> > To each their own, of course, but there was a long discussion of
> > discourse here a while ago. I tried it out, but it was like a bad
> > version of a mailing list. It sent me a mail informing me
Florian Weimer writes:
> Based on some reports, I don't think this is how the Gmail
> implementation works. It will discard mailing list mail for senders
> with a DMARC policy that does not set p=reject, too.
Based on conversations with GMail developers, that has nothing to do
with DMARC,
Vitaly Zaitsev via devel writes:
> I think it should be an option in mailman's settings. Each user can
> enable or disable mitigations for his email address.
Patches welcome at GNU Mailman.
Potential time waste warning: The list owner must have the choice
whether to delegate the choice to
Kevin Fenzi writes:
> On 4/30/19 4:46 AM, Vitaly Zaitsev wrote:
> > Hello all!
> >
> > Currently Fedora mailing lists use "From" field from original messages
> > and if sender's domain use DMARC=reject policy, mailing lists
> > subscribers cannot receive any messages from such users because
Kevin Fenzi writes:
Thanks for the conversation and a lot of useful information. I think
it's mostly moved to "users", which is a channel which I think is more
suited to forum style. So I'll go back to lurking, after one comment.
> Yep. Perhaps we could (re)direct people to file issues with
Kevin Fenzi writes:
> On 10/21/18 6:12 PM, Stephen J. Turnbull wrote:
> > years now. abompard has a few commits, he and pingu still answer mail
> > but that's about it.
>
> Well, he has 980 commits, much more than anyone else.
Sure, but in the last couple of years th
Brian (bex) Exelbierd writes:
> The question was genuine. Additionally, even at this site, the user
> profile doesn't seem to be present.
I doubt there is a user profile chapter or page for HyperKitty at the
Mailman project. If there is one, it would be in the HyperKitty docs
themselves.
>
Kevin Fenzi writes:
> Huh. The only person I know of from Fedora at least that was
> working on it was abompard. While he's working on other things now,
> as far as I know he's still working on mailman3/hyperkitty as time
> permits.
pingu and abadger also contributed. Don't know their exact
Dan Book writes:
> It is not a format of their own, but it's not appropriate for
> plaintext, so it sounds like a bug to me.
But that's exactly my point. *We* think it's a bug, but *they* chose
it deliberately. Undoubtedly people have tools expecting it, etc.
I've been on both sides of that
stan writes:
> So, you are really gung-ho for Discourse.
IMO, that's not nasty, but it wasn't necessary and could be taken
badly in context. Just, "as a proponent, I'd like to ask you" is good
when things are getting heated.
Your questions are important[1], and I'd like to gloss them:
>
Kevin Fenzi writes:
> On 10/19/18 6:43 AM, Neal Gompa wrote:
> > You know why the usage numbers bear that out? Because the upgrade to
> > HyperKitty was mishandled and delayed over and over. We were screwed
> > over by the fact that our infrastructure doesn't run on Fedora, so
> > that made
Required disclosure: Mailman dev, and my sympathies are with the list
advocates for this channel both for that reason, and for more
objective ones. I don't really argue against a move to Discourse
here, but I do know a bit about the problem space, and I'd like to
discuss *some* aspects here. I
25 matches
Mail list logo
