the Fedora
Community with questions or wanting to bring up a security topic. It's
fully public, so dont post embargoed information there.
JT
On Tue, Aug 20, 2024 at 7:43 AM Daniel P. Berrangé
wrote:
> On Tue, Aug 20, 2024 at 12:54:52PM +0200, Fabio Valentini wrote:
> > On Sun, Aug 18
Ran into the same when I voted. I believe the claim links have been broken
for a while. Nb discovered at RH Summit, the badge links were broken when
we tried to claim the Summit badge. Dont know how long they've been broken,
but I guess that needs to go on the list of things to do.
On Sun, May 19
.
JT
[0]https://networkbuilders.intel.com/docs/networkbuilders/accelerate-snort-performance-with-hyperscan-and-intel-xeon-processors-on-public-clouds-1680176363.pdf
[1] https://github.com/VectorCamp/vectorscan
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2263601
u
cannot wait another day for this, then by all means someone else can push
the fix to the various repos.
JT
On Sat, Feb 3, 2024 at 2:56 AM wrote:
>
>
> On 2024-02-01 11:26 p.m., Neal Gompa wrote:
> > On Fri, Feb 2, 2024 at 2:04 AM Mamoru TASAKA
> wrote:
> > >
> >
I'm the maintainer of those packages and I've already spoken with Neal
Gompa about it. I'll be addressing that when I get home, I'm on the road
until Sunday without my system to be able to commit to fix it.
JT
On Thu, Feb 1, 2024 at 8:26 PM Luya Tshimbalanga
wrote:
> Hel
On Sun, Nov 19, 2023 at 1:35 PM Richard W.M. Jones
wrote:
> On Sun, Nov 19, 2023 at 08:33:02AM +, Mattia Verga via devel wrote:
> > rpms/cairo
> > rpms/createrepo_c
> > rpms/desktop-backgrounds
> > rpms/ed
> > rpms/libcap
> > rpms/vim
>
> Just noting that these packages seem to be very import
I pickled up the theme and background packages since I'm already doing
those for Fedora Jam.
On Sat, Nov 18, 2023 at 5:12 PM Sérgio Basto wrote:
> On Sat, 2023-11-18 at 21:57 +0100, Sandro wrote:
> > On 18-11-2023 21:08, Kevin Fenzi wrote:
> > > After 6 weeks, the package will be retired.
> > >
the community
around security matters. We have no visibility into any embargoed matters
until it's made public. That's the nature of a fully open project -- no
secrets.
JT
On Sat, Sep 30, 2023 at 5:59 PM Justin Forbes wrote:
> On Sat, Sep 30, 2023 at 10:55 AM Kevin Fenzi wrote:
>
That looks like it's just a proposal by some random people that KDE and
GNOME should to work together. I've not seen a statement by either
desktop. the file referenced is literally under a directory called
"proposals". and I've never heard of this "Plaintext Group" before.
It does not look like KD
, 2023-06-21 at 17:18 -0400, JT wrote:
> >
> > > How are you downloading RHEL ISO images?
> >
> > I already sent you the URL in a prior response:
> > https://developers.redhat.com/products/rhel/download
> >
> > > Please do not tell me to take a deep br
xplaining that you
dont need to be worried.
On Wed, Jun 21, 2023 at 5:12 PM Philip Wyett
wrote:
> On Wed, 2023-06-21 at 17:07 -0400, JT wrote:
> > > Who says that developer account will be available soon, Have Red Hat
> made a commitment to keep
> > it?
> > > Pe
;t worry, take a deep breath and relax, the code will remain open source
and it will remain freely available.
On Wed, Jun 21, 2023 at 4:56 PM Philip Wyett
wrote:
> On Wed, 2023-06-21 at 16:49 -0400, JT wrote:
> > > I believe the GPL asks you never have to make agreement to access GPL
&
er and use
it. So anyone grabbing that ISO has legal right to the source code for the
base system.
On Wed, Jun 21, 2023 at 4:35 PM Philip Wyett
wrote:
> On Wed, 2023-06-21 at 16:23 -0400, JT wrote:
> > Red Hat doesn't need to mention it. It's a legal requirement of the
> G
account, there would just be another account to
do the same thing again. Red Hat would have to play whack-a-mole to try to
stop people from doing that constantly.
On Wed, Jun 21, 2023 at 4:14 PM Philip Wyett
wrote:
> On Wed, 2023-06-21 at 16:10 -0400, JT wrote:
> > > I see an impa
> I see an impasse here. Why contribute to fedora when Red Hat will lock it
down in other products?
They literally cannot "Lock it down" due to the GPL. Anyone using RHEL
binaries has legal right to the code.
What they seem to have done is limit source code access to those who are
actually using
are and
address/mitigate any potential threat.
JT
On Mon, Jun 19, 2023 at 5:49 PM Philip Wyett
wrote:
> On Mon, 2023-06-19 at 23:39 +0200, Emmanuel Seyman wrote:
> > * Philip Wyett [19/06/2023 22:20] :
> > > Private mailing list? No part of this project should have private
> an
As the current Maintainer of Fedora Jam... I'm on board with this idea.
~JT
On Mon, Jun 19, 2023 at 3:33 PM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:
> Hello!
>
> With the growing number of multimedia packages in Fedora, mostly owing
> to t
Interesting that this came up. I was just talking to someone else about
this the other day. From what I understand, that sysctl affects the max
number of memory map areas a process can have, i.e. contiguous reserved
memory. For a game that's great because it can pack more into memory and
decreas
On Fri, Apr 21, 2023 at 1:15 PM Matthew Miller
wrote:
> On Fri, Apr 21, 2023 at 10:47:24AM -0400, JT wrote:
> > While there definitely was an increase in interaction with people, that
> > also came at a cost. Two or three devs having a conversation in a thread
> > would als
On Fri, Apr 21, 2023 at 12:07 PM Chris Adams wrote:
>
> So, I will say this is kind of a peeve of mine about server-based
> discussion systems (whether web or client like Slack/Discord): allowing
> people to edit messages, especially after people have replied to them,
> is a bad idea. Person 1 s
> But with my Fedora Ambassador hat on I can tell you that the problem
we see right now is not that we don't have people coming to Fedora. We have
a problem helping people to connect to where the work is happening in a way
that they can contribute.
> And this includes both mentoring them to be abl
> I am very much in favor of modernizing our communication tools. But I
don't think this is the way to go (but I don't know anything better, except
maybe a more "traditional", more structured forum).
I'm up for modernizing things and making them more efficient as well,
though as Matthew replied t
n that.
I'm still getting settled in to a new job after a few months of being
without work, and I need to build another safety net for myself for the
next transitional period I face, but when I've gotten that taken care of,
I'd be interested in funding some dev work towards making t
great. But I'd
appreciate it if there was a way to move forward with new tools while not
taking away the abilities that older tools gave us to archive things for
the future.
JT
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To uns
Sounds good. I'll sync up with you guys in another email tomorrow morning
so we can work things out without spamming the whole mailing list.
~JT
On Sun, Jan 29, 2023 at 3:08 PM Jonathan Dieter wrote:
> That's wonderful news! I've moved roles since adding it to Fedora and no
I can pick this package up if you're stepping back. The lizards devs are
planning on a new release sometime this year, but there's still a few
things they're trying to finish up first before releasing v3.13. Last I
heard they wanted it to be out before summer.
JT
On January 28
Hey Neil,
Great to see you here. Hopefully we'll bump into each other again sometime
in 2023.
JT
On Thu, Jan 26, 2023 at 4:34 PM Neil Hanlon wrote:
> Hi folks!
>
> My name is Neil Hanlon and I was recently sponsored into the packager's
> group by Michel Salim, adding py
There's been some discussion in the security meeting about CVEs, and I've
been meaning to get some time to chat with Ben about his thoughts on the
best way to move forward. But I keep forgetting everytime I talk to him.
I guess now is a good time as ever for him to read this and call me out at
the
If Fab doesn't have time I'll pick up the Security Spin. But if memory
serves, we ran into him not responding before because he was on vacation.
So that may be the case again. However until we know for sure, I'll raise
my hand that if he doesnt want to keep it up, cant keep it up, or doesn't
resp
control above all else. That being said though...
> In any case, this seems like functionality best provided by
crypto-policies itself.
Agreed, the simpler and less code complex the better.
On Mon, May 2, 2022 at 12:27 PM Robbie Harwood wrote:
> JT writes:
>
> >> IMO, there&
> IMO, there's a rather desperate need to be able to override the
system-wide policy for individual processes, maybe via some sort of wrapper
around one of the containerization technologies.
There's part of me that's almost surprised that there's not an SELinux
Policy flag of some kind that would
> Sadly, some of this is due to the "media" organization's need to drive
page views and not journalistic ignorance of the facts that this is just a
proposal.
> I don't know how you fix the underlying revenue enhancement approaches
that have driven hyperbole and attempts to drive engagement and outr
On Thu, Apr 7, 2022 at 4:16 PM Samuel Sieb wrote:
> On 4/7/22 13:04, JT wrote:
> > How will this affect Desktop Developers who are still reliant on x for
> > their DE/WM to work? For example, I dont have the needed bits in Lumina
> > for it to work with Wayland.
> >
How will this affect Desktop Developers who are still reliant on x for
their DE/WM to work? For example, I dont have the needed bits in Lumina for
it to work with Wayland.
I'm asking because I dont know how this will or won't affect me and other
desktops in a similar situation.
On Thu, Apr 7, 2022
On Wed, Apr 6, 2022 at 4:06 AM laolux laolux via devel <
devel@lists.fedoraproject.org> wrote:
> I have no strong opinion on this, and not much say anyways, but I thought
> I could share my little piece of info.
> My currently one and only computer is a 2012 MSI GE60 0ND, with a core
> i7-3630QM,
On Thu, Mar 3, 2022 at 8:01 PM Rahul Sundaram wrote:
> Hi
>
> On Wed, Mar 2, 2022 at 11:40 AM Matthew Miller wrote:
>
>> On Thu, Feb 24, 2022 at 08:13:15PM +0100, Zbigniew Jędrzejewski-Szmek
>> wrote:
>> > It would probably be good to use more of those features, but you need
>> > to understand th
With the obvious understanding that all work is done by people who are
willing to pitch in... who's domain does this fall under? Would this be
something that the Fedora Security Team would focus on? Would this be done
by the maintainers of the individual 'services'. I realize a lot of what
peop
ome of that is helpful.
>
> – Ben
>
> [1] https://www.darktable.org/development/
>
> [2]
>
> https://src.fedoraproject.org/rpms/debugbreak/blob/e009ccfac2b8e05a6018921ed6d3e732837a9e52/f/debugbreak.spec#_62
>
> On 12/28/21 08:08, JT wrote:
> > Hey all,
> > I
e it's crashing to have an idea of where to set up
breakpoints.
Unless my memory is off, I was sure there was a way to do this but I just
can't seem to remember or figure out how to do it.
Any pointers? Thanks!
JT
___
devel mailing list -- deve
As someone who has to use Slack for work, this is disappointing, but
at least there is still a flatpak for Slack:
https://www.flathub.org/apps/details/com.slack.Slack
On Thu, Nov 4, 2021 at 8:24 PM Gordon Messmer
wrote:
>
> https://slack.com/help/articles/115002037526-System-requirements-for-usi
I think an important question we should ask is who is the target user we're
thinking about when we consider 'recommendations'. I used to have a pretty
clear picture of what 'recommended/required' meant, and then I did some
charity/volunteer work in Namibia back in the early 2000s and realized that
Nice. I did an update from F26-F33 last year doing one version at time
instead of jumping more than one version... and had no major issues. I
wonder how far back its possible to start from and walk through the version
updates.
On Mon, Oct 11, 2021 at 3:55 AM Jiri Vanek wrote:
> Hello good peopl
t with the chip
shortage just like everyone else.
I really look forward to the day when Open ISAs like RISC-V and OpenPower
have better availability. I know I'm eager to move to them as soon as I
can.
I have no experience with emulating it, so I can't really give any feedback
on that. Do
I ran into the same thing, but I assumed it was me doing something wrong
since I'm just starting out learning the Fedora Build process,
The failures I am seeing are exactly the same as yours:
https://download.copr.fedorainfracloud.org/results/q5sys/Fedora-Jam/fedora-rawhide-x86_64/02521113-fedora-
nyone has any concerns, issues, or advice, I'm all ears.
Respectfully,
JT Pennington
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Condu
12, 2021 7:52:24 AM PDT Matthew Miller wrote:
> > > On Sun, Apr 11, 2021 at 11:38:40PM -, JT Pennington wrote:
> > >
> > > > I'd like to volunteer to pick up the Fedora Jam project and maintain
> it.
> > >
> > >
> > > Awesome -- th
Ive reported the 400 error, here:
https://pagure.io/fedora-infrastructure/issue/9990
On Thu, May 27, 2021 at 1:19 PM Silvia Sánchez wrote:
>
> I tried to login to vote but I get a 400 error when I try.
> It's been 3 days already.
>
>
>
> On Thu, 27 May 2021 at 18:57, Ben Cotton wrote:
>
>> You
Erich, you want to transfer those two pagure repos over to me?
You should still have my email from back in the day, but let me know if there's
anything info you want to pass long on things you were working on, current
issues you were aware of, things that were requested or planned, etc.
___
I'd like to volunteer to pick up the Fedora Jam project and maintain it.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en
On Tue, 2019-02-12 at 16:13 -0500, jt wrote:
> On Tue, 2019-02-12 at 21:06 +, Pete Walter wrote:
> > Looking at the build log, it seems to be checking for 'libpcre =
> > 8.41', but the build root has 8.43-RC1 which causes the build to
> > error out.
> >
On Tue, 2019-02-12 at 21:06 +, Pete Walter wrote:
> Looking at the build log, it seems to be checking for 'libpcre =
> 8.41', but the build root has 8.43-RC1 which causes the build to
> error out.
>
> Pete
>
> 12.02.2019, 20:43, "jt" :
> >
ch to fix in this
case?
If it isn't a linker issue, where should I start poking next?
Thanks in advance for any pointers.
[0] https://koji.fedoraproject.org/koji/taskinfo?taskID=32400415
[1] https://gist.github.com/jmtaylor90/bd9680de68d1f8486dacd4e0b64
52 matches
Mail list logo
