On Mon, Jul 08, 2024 at 12:50:52PM +, Tim Landscheidt wrote:
> Developers might not want to work for a project any longer
> that engages in behaviour that is perceived as being at odds
> with why they chose to work for that project in the first
> place.
Well... yeah?
That sounds like a
On Mon, Jul 08, 2024 at 11:03:53AM +, Tim Landscheidt wrote:
> But with that knowledge comes the ability to work for a va-
> riety of organizations who will spend many resources on
> nudging their users to behave in a way that is not necessar-
> ily in their best interests.
What does "a
On Wed, Feb 21, 2024 at 08:11:49AM +0100, Miroslav Suchý wrote:
> Do you want to make Fedora 40 better? Please spend 1 minute of your time and
> try to run:
From the Fedora systems I have immediate access to:
Well-used F39 Workstation:
Problem: problem with installed package
On Tue, Feb 20, 2024 at 03:54:54PM +0100, Kevin Kofler via devel wrote:
> the smaller one and letterboxing the larger one as it should.) So this means
> 1. Wayland will never be suitable for my notebook, and 2. one of these days
> I am going to have to port Plasma Mobile to X11.
Or, uh, (3)
On Wed, Feb 07, 2024 at 01:21:15PM +0100, Peter Boy wrote:
> Unfortunately, some Fedora maintainers seem to take their cue from the
> missionaries and conquistadors of the 16th and 17th centuries and try
> fire and sword and coercion. A bad strategy in a free world.
Congratulations, you just
On Fri, Dec 22, 2023 at 10:27:55PM +0100, Florian Weimer wrote:
> >> gutenprint jpopelka jridky twaugh zdohnal
> > ...FWIW as of a few minutes ago this should be resolved upstream.
>
> Thanks, I can confirm this fixes the issue for the Fedora package as
> well. Should I push this to
On Fri, Dec 22, 2023 at 02:18:54PM +0100, Florian Weimer wrote:
> gutenprint jpopelka jridky twaugh zdohnal
...FWIW as of a few minutes ago this should be resolved upstream.
- Solomon
--
Solomon Peachypizza at shaftnet dot org (email)
On Tue, Oct 03, 2023 at 08:50:53PM +0200, Leon Fauster via devel wrote:
> If a bumped version of a package fixes an issue (stream variant of
> CentOS) e.g 2.2, and a released package (rhel variant) has a
> backported fix for e.g. 2.1, that doesn't mean that the code is also
> in the stream git
On Mon, Sep 11, 2023 at 09:26:44AM -0700, Kevin Fenzi wrote:
> I think we need to figure out the way forward, but... I don't think we
> should do it here and now. Please go test f39. ;)
While I'm personally glad that the forced-onto-proprietary-gitlab
migration has effectively stalled
On Mon, Sep 11, 2023 at 07:58:03AM -0500, Michael Catanzaro wrote:
> No? All of our packages are on https://src.fedoraproject.org/ and our
> Fedora-specific source code goes on https://pagure.io/. These are both
> Pagure, not GitLab. It is open source.
https://lwn.net/Articles/817426/
On Mon, Sep 11, 2023 at 04:35:50AM +0200, Kevin Kofler via devel wrote:
> +1, Fedora MUST NOT rely on proprietary infrastructure. IMHO, it is a
> mistake that Red Hat is doing so, and Fedora should not follow that
> unfortunate move.
Not to retread old drama, but doesn't Fedora now rely on a
On Fri, Aug 25, 2023 at 09:08:23PM -0700, Samuel Sieb wrote:
> No, it's a demonstration of applications that aren't being properly
> maintained when they're still using functions that have been deprecated for
> 6 releases which is also that many years. Python core is very stable.
So... you're
On Fri, Aug 25, 2023 at 06:55:17PM -0700, Adam Williamson wrote:
> It's a lot of output, but not *so* many problems when you boil it down.
Yeah, it's ultimately another example (or four) of how Python is utterly
worthless as a "stable" application platform.
> I suppose we could just vendor
On Wed, Aug 23, 2023 at 08:22:42PM +0200, Miroslav Suchý wrote:
> Do you want to make Fedora 39 better? Please spend 1 minute of your time and
> try to run:
I ran this on a bunch of my fleet, lots of problems, and they all seem
to be related to the Python 3.12 bump.
F38 Workstation #1:
On Wed, Jul 26, 2023 at 04:36:13PM +0200, Ralf Corsépius wrote:
> My (older) lenovo laptop and my HPE Micro-Server are obviously not.
The laptop is a T495 (introduced late 2019), but the workstation is an
older HP Z440 (introduced in late 2014!)
> This is the second time, somebody mentions
On Wed, Jul 26, 2023 at 11:48:36AM +0300, Alexander Ploumistos wrote:
> That would require people volunteering to potentially brick their
> machines in order to test the updates. If something goes wrong, the
> equipment (and the knowledge) necessary to reprogram a chip is rather
> scarce. I'm
On Wed, Jul 26, 2023 at 09:45:13AM +0200, Ralf Corsépius wrote:
> It could be "my bubble", but for me, in all these fwupd is around, it has
> never, ever worked on any piece of HW for me.
Most of the stuff I have that is updated through fwupd are peripherals
[1] that are independent of the
On Mon, Jul 24, 2023 at 04:51:38PM +0100, Richard W.M. Jones wrote:
> You don't actually need to do any of this if you're using libguestfs,
> because the worst that can happen is the filesystem will pwn the
> kernel inside the KVM appliance (which is just a userspace process, so
> you can kill
On Mon, Jul 24, 2023 at 04:00:21PM +0100, Daniel P. Berrangé wrote:
> If I have a USB flash stick I plug in every day, it shouldn't ask me
> about that after the first time I use it.
Based on this "threat model" all an attacker has to do then is
snag/modify/replace your existing drive and then
On Sun, Jul 23, 2023 at 11:25:12AM -0400, Neal Gompa wrote:
> > If the system administrator wants to mount $UNCOMMONFS, they should be
> > able to do so without hassle, but that doesn't mean that a normal user
> > who got handed a sketchy USB stick at a conference should be able to do
> > so with
On Fri, Jun 30, 2023 at 01:41:18PM +, Leslie Satenstein via devel wrote:
> What should I do, if the person I gave the software to, removes my
> copyright, rebrands the software and sells my software as their own?
> Is it right? And when I release a bug fix, they take it, insert the
> fix
On Thu, Jun 29, 2023 at 10:27:49AM -0400, David Both wrote:
> I also spent about 4 days trying to get Dovecot to work with SendMail in
> a test VM setup. I'm either missing one or more important bits or its
> just too complex for me.
I've been running a dovecot + sendmail setup on Fedora for
On Thu, Apr 27, 2023 at 10:47:15AM -0700, Kevin Fenzi wrote:
> Our discourse instance is hosted for us by discourse.
> We shouldn't have to do maint on it, but we will have to do moderation,
> etc.
So... if maintaining discourse is too much overhead but it's okay to pay
someone else to handle,
On Thu, Apr 27, 2023 at 07:01:15AM -0400, Stephen Smoogen wrote:
> breaking mail altogether. My frustration and anger comes from the fact that
> I spent most of the last 5 years assuming that it was somebody else's
> problem and they would take care of it so I could focus on keeping other
> things
On Wed, Apr 26, 2023 at 02:42:56PM +0200, Kevin Kofler via devel wrote:
> And as I already answered, I think this is completely backwards. If you want
> to newly join a project, you learn their way to do things and adapt to it.
> If, on the other hand, you are already involved in a project and
On Tue, Apr 25, 2023 at 02:59:22PM -0400, Josh Boyer wrote:
> That's certainly a choice one could make. Personally, I would not
> prioritize keeping my bespoke email setup intact over working with a
> community on a project I care about.
My "besoke email setup" benefits *me* and my
On Fri, Apr 21, 2023 at 04:38:28PM -0400, Ben Cotton wrote:
> There are a lot of questions left unanswered by this quick analysis,
> but there's a clear trend in fewer participants over time. In fact,
> last month had the second smallest participant count (tied with
> October 2022). Of course,
On Fri, Apr 21, 2023 at 05:07:28PM +0200, Aleksandra Fedorova wrote:
> No, not really. I advised you to look into it, because you may actually get
> more from it personally, than you currently expect. I haven't proposed it to
> become a required Fedora activity, I gave you the unsolicited advice.
On Fri, Apr 21, 2023 at 04:55:00PM +0200, Emmanuel Seyman wrote:
> I agree there's a huge lack of netiquette in Fedora's mailing lists,
> with wholesale quoting, top-posting, subjects not being updated, etc but
> changing mediums seems far more expensive than asking people to post
> emails that
On Fri, Apr 21, 2023 at 08:24:14AM +0300, Benson Muite wrote:
> As such, simply adopting it because it can be deployed may leave out
> many contributors, in particular those who drive development forward.
I have made this point several times in other contexts; a new
tool/workflow has to yield
On Fri, Apr 21, 2023 at 11:42:20AM +0200, Aleksandra Fedorova wrote:
> That's a slight exaggeration of course, but so is your statement. People
> come to Fedora via many ways. But I doubt any of it starts with e-mail
> nowadays. And the fact that you don't see newcomers _here_ actually proves
>
On Thu, Apr 20, 2023 at 07:21:54PM -0400, Simo Sorce wrote:
> Hi Matthew, you say: "We're missing people", and I think, "who?".
> And who are you going to miss if you move to discourse?
Again and again I have seen this "we're missing people" sentiment be
used to justify scrapping "old"
On Fri, Feb 24, 2023 at 05:55:55AM +0100, Kevin Kofler via devel wrote:
> Ah right, I had forgotten about that issue. I do not think I will ever
> understand the fascination some projects have for JIRA. It is proprietary,
> and IMHO the web UI for users to report bugs in JIRA is very confusing
On Wed, Feb 22, 2023 at 10:30:40AM +0100, Miroslav Suchý wrote:
> dnf --releasever=38 --setopt=module_platform_id=platform:f38 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
F36 snowflake
On Wed, Feb 22, 2023 at 10:46:12AM -0500, Ben Cotton wrote:
> Red Hat Bugzilla has introduced a 12 month lifetimes for API keys. You
> must replace your API keys at least once a year. Additionally, any API
> key that is not used for 30 days will be suspended but can be
> re-enabled on the
35 matches
Mail list logo
