Re: End of CentOS Linux: What about Fedora?

[Ondrej Budai]

Hello!

st 9. 12. 2020 v 12:35 odesílatel Jaroslav Prokop 
napsal:

> Hello,
>
> On 09/12/2020 12:12, Christoph Karl wrote:
> > Hello!
> >
> > On 09.12.20 04:26, Sergio Belkin wrote:
> >> How does this (https://blog.centos.org/2020/12/future-is-centos-stream/
> )
> >> affect Fedora?
> >
> > I think Fedora now needs some kind of LTS.
> > At least I was planning to support CentOS via EPEL as
> > a kind of "Fedora LTS".
>
> If I remember correctly and not making it up there was a discussion some
> years back about Fedora LTS.
> I think it was dismissed because we had CentOS providing LTS stability.
> But now it does not seem like
> we can rely on long term stability. Maybe it's time to revive that
> discussion?
>

Maybe the community can use CentOS Stream as a base for some kind of LTS
distro.


>
> I am starting to get really confused on Fedora's position here. Are we
> anywhere in the pipeline?
>

RHEL/CentOS Stream is branched out of Fedora.

RHEL and CentOS Stream have a much closer relationship. Someone put it very
nicely: RHEL minor versions are branched off CentOS Stream every 6 months.
It's a bit of oversimplification but it very nicely describes how tight
their relationship is. On the other hand, RHEL/CentOS Stream is branched
off Fedora every 3 years. There's much bigger space for a deviation between
them.

Are we prelude for software before it gets on CentOS streams or maybe
> testing grounds for
> RHEL if something got proved on the ground of CentsOS streams?
>
> ___
> 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-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Cheers,

Ondřej
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 33 in GCP

[Ondrej Budai]

pá 20. 11. 2020 v 1:43 odesílatel Dusty Mabe  napsal:

> We have published an image into GCP for Fedora 33 (see [1]).
>
> The details are:
>
> image project: fedora-cloud
> image name:fedora-cloud-base-gcp-33-1-2-x86-64
>
> We're hoping to get this information added to the website at some point.
>
> Dusty
>
> [1] https://pagure.io/cloud-sig/issue/318
> ___
> 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-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


Hello! I work on the Image Builder project[1]. We do support uploading
Fedora images to AWS and Azure and we would love to get support for GCP.
Can you point me at some resources on how Fedora images are built for GCP
and how they are uploaded/registered?

Thanks!

Cheers,

Ondřej

[1] https://www.osbuild.org/

-- 

Ondřej Budai

Software Engineer

Red Hat 

___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: The default fs.inotify.max_user_watches limit is too low.

[Ondrej Budai]

st 18. 11. 2020 v 10:16 odesílatel Gargoyle  napsal:

> I've just made the switch from Ubuntu to Fedora 33 for my main desktop
> system. Of the few teething problems I am going through, the initial
> 8192 limit for fs.inotify.max_user_watches was probably causing the most
> side effects. As a developer, I pretty much have netbeans open all day
> and am forever tailing log files, so I hit this problem pretty much
> straight away.
>
> After some digging around I found a script to list the current count of
> watchers per process. The half-dozen worst offenders were:-
>
> INOTIFY
> WATCHER
>  COUNT PID CMD
> 
> 4903 4620  /data/Applications/java/jdk-15/bin/java
> -Djdk.home=/data/Applications/java/jdk-15 -classpath
> /data/Applications/netbeans
>  3573 3032  /usr/libexec/tracker-miner-fs-3
>64 2022  /usr/lib/systemd/systemd --user
>47 2663  /usr/libexec/gsd-xsettings
>2734846  /usr/share/atom/atom --type=renderer
> --enable-experimental-web-platform-features
> --field-trial-handle=123480363484759119
>18 2812  /usr/bin/gnome-software --gapplication-service
>
> So netbeans + tracker-miner had pretty much consumed the entire pool
> within an hour of starting the system.
>
> I've bumped the figure up to 65K by adding an entry to /etc/sysctl.conf
> and asked on #fedora if anyone knew of the side effects of having a high
> number - the only answers found were that approx 1K of unswapable kernel
> memory is used per watcher. So this increase only puts an additional
> 57MB of such memory usage onto my system.
>
> Are there any other side effects of this to worry about?
>
> If not, then perhaps the default should be significantly increased with
> the aim of removing the problem for new users with modern desktop/laptop
> machines which probably have 4GB+ RAM. I've not rebooted my machine
> overnight and netbeans is now up to 13,000 watches and tracker-miner
> upto 4,500. So in less than 24 hours I have exceeded 16K watches.
>
> Perhaps an new default value in the region of 32K - 64K would be more
> appropriate?
>
>
> -- Gargoyle
> ___
> 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-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


I have the exact same experience with Goland and PyCharm. I raised the
limit to 524288 using this guide[1] and it works like a charm.

[1]: https://confluence.jetbrains.com/display/IDEADEV/Inotify+Watches+Limit

-- 

Ondřej Budai

Software Engineer

Red Hat 

___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: [ELN] Cannot build a package in mock on F32

[Ondrej Budai]

Sadly, that did not help, still the same error.

O.

út 13. 10. 2020 v 11:00 odesílatel Pavel Raiskup 
napsal:

> On Tuesday, October 13, 2020 9:07:18 AM CEST Ondrej Budai wrote:
> > Hello,
> >
> > I'm trying to build RPM from SRPM for ELN on F32 host using this command:
> >
> > mock -r fedora-eln-x86_64 --resultdir results --rebuild PATH_TO_SRPM
> >
> > However, I get the following error message when mock tries to bootstrap
> > Fedora ELN buildroot using dnf:
>
> Can you try to update distribution-gpg-keys to the updates-testing version?
> https://bodhi.fedoraproject.org/updates/FEDORA-2020-867d08764a
>
> Pavel
>
> > GPG key at
> >
> file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary
> > (0x9570FF31) is already installed
> > The GPG keys listed for the "Fedora ELN - Developmental modular packages
> > for the next Enterprise Linux release" repository are already installed
> but
> > they are not correct for this package.
> > Check that the correct key URLs are configured for this repository..
> > Failing package is: dnf-4.4.0-1.eln104.noarch
> >  GPG Keys are configured as:
> >
> file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary
> >
> > and many more GPG failures for all the installed packages...
> >
> > Is it somehow possible to build packages for ELN using mock on Fedora 32?
> >
> > Thanks
> >
> > Ondřej
> >
>
>
>
>
>
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[ELN] Cannot build a package in mock on F32

[Ondrej Budai]

Hello,

I'm trying to build RPM from SRPM for ELN on F32 host using this command:

mock -r fedora-eln-x86_64 --resultdir results --rebuild PATH_TO_SRPM

However, I get the following error message when mock tries to bootstrap
Fedora ELN buildroot using dnf:

GPG key at
file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary
(0x9570FF31) is already installed
The GPG keys listed for the "Fedora ELN - Developmental modular packages
for the next Enterprise Linux release" repository are already installed but
they are not correct for this package.
Check that the correct key URLs are configured for this repository..
Failing package is: dnf-4.4.0-1.eln104.noarch
 GPG Keys are configured as:
file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary

and many more GPG failures for all the installed packages...

Is it somehow possible to build packages for ELN using mock on Fedora 32?

Thanks

Ondřej
___
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-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org