Re: corporatemarketingguide
Maybe he just wants to help fedora. By making it more accessible to the masses. I am not sure but I am just a mere QA volunteer. On Thu, 18 Jul 2024, 11:59 Andrej Manduch, wrote: > Why you're spamming fedora mailing list? Do you have any shame? > > On Thu, Jul 18, 2024, 12:41 PM Rock Dsouza > wrote: > >> I am rock dsouza, working for corporatemarketingguide PR consultant, with >> more than six years of experience in the PR and Digital Industry, helping >> teams achieve goals by streamlining the process. >> https://www.corporatemarketingguide.com/ >> -- >> ___ >> 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 >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > -- > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: *****SPAM***** Enabling GOPROXY and GOSUMDB in Fedora
Personally I agree with maxwells stance fedora is a privacy friendly distro. On Fri, 12 Jul 2024 at 12:03, Ralf Corsépius wrote: > > > Am 11.07.24 um 1:16 PM schrieb Chris Suszynski: > >> I support keeping the Google Go module proxy disabled by default. Our > packages should not send telemetry data to Google without explicit opt-in. > > > > What's the reason for treating Go differently than other languages? > Fedora does not patch out calls to sites like npmjs.com, pypi.org, > rubygems.org or repo.maven.apache.org, doesn't it? > Fedora has a policy of "no phone home without explicit user consent". > > Ralf > -- > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: example example example example example
spam mail On Mon, 1 Jul 2024 at 12:25, charan chintu wrote: > https://www.example.com;> example > [url=https://www.example.com] example [/url] > https://www.example.com;> example > example example example example example example example example example > example example example example example example example example example > example example example example example example example example example > example example example example example > -- > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Fedocal] Reminder meeting : ELN SIG
It will be 5pm in London and I will attend the meeting. On Thu, 9 Mar 2023 at 12:00, wrote: > Dear all, > > You are kindly invited to the meeting: >ELN SIG on 2023-03-10 from 12:00:00 to 13:00:00 US/Eastern >At fedora-meet...@irc.libera.chat > > The meeting will be about: > > > > Source: https://calendar.fedoraproject.org//meeting/10449/ > > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Test upgrades from F37 to F38 - it will take you just a minute
Mostly upgrades, here are the other results. Installing weak dependencies: ipp-usb x86_640.9.23-2.fc38 fedora 2.1 M passt x86_640^20230216.g4663ccc-1.fc38 fedora 174 k Downgrading: fwupd x86_641.8.10-1.fc38 fedora 1.8 M fwupd-plugin-flashrom x86_641.8.10-1.fc38 fedora 26 k fwupd-plugin-modem-manager x86_641.8.10-1.fc38 fedora 60 k fwupd-plugin-uefi-capsule-data x86_641.8.10-1.fc38 fedora 1.8 M Transaction Summary == Install 41 Packages Upgrade1782 Packages Downgrade 4 Packages Total download size: 1.7 G Operation aborted. On Fri, 24 Feb 2023 at 09:53, Ankur Sinha wrote: > Looks good, with a few downgrades: > > Downgrading: > buildah x86_64 1.29.0-2.fc38 > calcium-calculator x86_64 7.9.5-10.fc38 > enchant2 x86_64 2.3.3-6.fc38 > enchant2-aspell x86_64 2.3.3-6.fc38 > freerdp-libs x86_64 2:2.9.0-3.fc38 > fwupdx86_64 1.8.10-1.fc38 > fwupd-plugin-flashromx86_64 1.8.10-1.fc38 > fwupd-plugin-modem-manager x86_64 1.8.10-1.fc38 > fwupd-plugin-uefi-capsule-data x86_64 1.8.10-1.fc38 > libjcat x86_64 0.1.12-2.fc38 > libwinpr x86_64 2:2.9.0-3.fc38 > mock-core-configsnoarch 38.1-1.fc38 > octave x86_64 6:7.3.0-1.fc38 > perl-Module-CoreList noarch 1:5.20230120-1.fc38 > python3-PyDrive2 noarch 1.15.0-2.fc38 > python3-xlsxwriter noarch 3.0.7-1.fc38 > syncthingx86_64 1.22.0-1.fc38 > syncthing-tools x86_64 1.22.0-1.fc38 > transmission-common x86_64 4.0.0-3.fc38 > transmission-gtk x86_64 4.0.0-3.fc38 > > > -- > Thanks, > Regards, > Ankur Sinha "FranciscoD" (He / Him / His) | > https://fedoraproject.org/wiki/User:Ankursinha > Time zone: Europe/London > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Proposal: drop delta rpms (for real this time)
I agree with the idea that Ben suggested of not enabling deltas by default and giving users the option until a certain time where it can be phased out fully. I remember in my personal experience that delta slowed down update durations. On Wed, 22 Feb 2023, 15:40 Ben Cotton, wrote: > On Tue, Feb 21, 2023 at 3:48 PM Matthew Miller > wrote: > > > > What we're doing now — as has been the case for several years, already > noted > > in the previous discussion — has very little end-user value. Also as > noted > > in that thread (as in the ticket)... that's unfortunate, because it did > > bring some real benefits (and could possibly do even more.) > > The fact that the value of deltas requires frequent updates means that > most people don't get the benefit. And since delta RPMs trade > bandwidth for CPU, it probably makes things worse for folks in > developing countries. So I agree, it's probably not worth keeping > deltas as the default. > > > But, I think it's time to move on. We have ostree and various > > container-delta approaches. We should focus on those — and give > DeltaRPMs a > > sad, fond farewell. > > Could we do this as a two-step approach? First change the default to > not use deltas but still allow people to opt-in to it. Then (assuming > we can track this, which maybe we can't) see how much they're used > before we decide to pull the plug on producing them. > > -- > Ben Cotton > He / Him / His > Fedora Program Manager > Red Hat > TZ=America/Indiana/Indianapolis > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Web Assembly on Fedora: interested in a Fedora SIG to work on this?
I'm interested and am keen to learn more about how it all works. On Fri, 2 Dec 2022 at 18:07, Michael Dawson wrote: > Great to see all the interest so far. Will continue to point people to > this thread to collect those who are interested in being involved and will > look to get the SIG rolling early in the new year. > ___ > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Can't login into Wiki
I had that issue as well, I thought it was only just me. On Wed, 22 Jun 2022 at 16:18, Ben Cotton wrote: > On Wed, Jun 22, 2022 at 11:10 AM Dmitry Belyavskiy > wrote: > > > > I can't login into Fedora Wiki. I get an error > > "You have made too many recent login attempts. Please wait 2 days before > trying again." > > I hit this last night for a little bit, but it eventually worked. I > filed an issue with the infra team since it's happening again: > https://pagure.io/fedora-infrastructure/issue/10783 > > -- > Ben Cotton > He / Him / His > Fedora Program Manager > Red Hat > TZ=America/Indiana/Indianapolis > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Spins SIG Proposal: Fedora Mate SIG and Cinnamon SIG
I am part of the Fedora QA team so I will see to it right away! On Sat, 4 Jun 2022 at 17:59, Chris Murphy wrote: > Most things related to testing and prerelease happen in the Fedora QA > team. We're just post-release for F36 so there's not a lot of visible > activity, but things will be picking up again soon. > > https://fedoraproject.org/wiki/QA > > > -- > Chris Murphy > > On Sat, Jun 4, 2022, 12:04 PM Ahmed Almeleh < > aalmeleh.whatever.0...@gmail.com> wrote: > >> I could do the testing for you. >> >> On Sat, 4 Jun 2022 at 17:01, Leigh Scott wrote: >> >>> The Cinnamon spin (kickstart and comps) are managed by Dan Book. >>> >>> https://fedoraproject.org/wiki/Changes/Cinnamon_Spin#Owner >>> >>> >>> I'm the only fedora developer working on Cinnamon. >>> I don't have any spare time to do more things including testing. >>> ___ >>> 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 >>> Do not reply to spam on the list, report it: >>> https://pagure.io/fedora-infrastructure >>> >> ___ >> 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 >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Spins SIG Proposal: Fedora Mate SIG and Cinnamon SIG
I could do the testing for you. On Sat, 4 Jun 2022 at 17:01, Leigh Scott wrote: > The Cinnamon spin (kickstart and comps) are managed by Dan Book. > > https://fedoraproject.org/wiki/Changes/Cinnamon_Spin#Owner > > > I'm the only fedora developer working on Cinnamon. > I don't have any spare time to do more things including testing. > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Spins SIG Proposal: Fedora Mate SIG and Cinnamon SIG
Hello, I have been a fan of the Mate-Compiz and Cinnamon desktops for a while now. And I am aware that the "Mate-Compiz" and "Cinnamon" spins are available. However, I feel more should be done with it for example: testing and developing and supporting it's growth. Open to any opinions / comments regarding my proposals . Thanks, Ahmed Almeleh He / Him / His Fedora QA Contributor. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Installing ffmeg-free degrades firefox video support
I could try that I just happened to have tested Firefox updates on Fedora 35 and 36, today and yesterday. I encountered problems with media playback even with openh264 enabled. I will let you know if it fixes the audio issue as well. On Sat, 4 Jun 2022 at 12:05, Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote: > On 04/06/2022 00:05, Otto Urpelainen wrote: > > It seems clear that there is a bug somewhere, but I cannot decide, > > where, hence this post to devel. Should Fedora's Firefox actually have > > media.ffmpeg.enabled set to false by default, because Fedora's variant > > of ffmpeg has this problem? Should upstream Firefox be smarted about > > which decoder library it attempts to use? Or should ffmpeg-free package > > do something to avoid this from happening. Any opinions are welcome! > > 1. Enable RPM Fusion repository. > 2. sudo dnf install ffmpeg-libs --allowerasing > > -- > Sincerely, >Vitaly Zaitsev (vit...@easycoding.org) > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Updated criteria proposal: networking requirements
Sounds good to me. On Sat, 4 Jun 2022, 01:25 Michael Catanzaro, wrote: > On Fri, Jun 3 2022 at 04:35:41 PM -0700, Adam Williamson > wrote: > > Using the default network configuration tools for the console and for > > release-blocking desktops, it must be possible to establish a working > > connection to common OpenVPN, openconnect-supported and vpnc-supported > > VPN servers with typical configurations. > > I would add Wireguard too, plus a limitation that the criterion only > applies if the desktop ships with support for these protocols. > > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Onboarding package
Could be useful for me to do too, I'm new to infra as an apprentice. On Tue, 30 Nov 2021 at 18:57, Ken Dreyer wrote: > On Sun, Oct 10, 2021 at 2:33 PM Dan Čermák > wrote: > > > Maybe we can make a VM image (for KVM/qemu + VirtualBox) with a small > > > set of Fedora infra, including Koji+Bodhi. > > > > How about a vagrant box or a docker-compose file :) > > > > However, I'm a little worried that this might be too fat or not too > > simple to set up automatically (koji itself uses Kerberos for auth, > > which by itself is a huge beast…) > > Here's my Vagrant file that sets up Kerberos and Koji. > https://github.com/ktdreyer/koji-playbooks/tree/master/vagrant > > It's overkill for new Fedora contributors but it helps with setting up > dev Koji environments. > > - Ken > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Question for election candidates: do you support allowing Fedora src-git repositories to be hosted on a proprietary software git forge?
I echo your views and agree with you completely. FOSS implementations should be used whenever available. - Ahmed Almeleh (Candidate for FESCo, the youngest of them.) On Mon, 29 Nov 2021 at 19:59, Fabio Valentini wrote: > On Mon, Nov 29, 2021 at 7:06 PM Michael Catanzaro > wrote: > > > > Hi, I have a question for the FESCo and Council candidates: do you > > support allowing Fedora src-git repositories to be hosted on > > gitlab.com, which a proprietary software git forge? > > > > Fedora Council has already effectively stated that dist-git > > infrastructure must remain open source, but has no such promises for > > src-git. I understand Council has previously stated that Fedora > > infrastructure should depend on proprietary software only if no open > > source alternative is suitable. Do you believe that there exist no open > > source git forges that would be suitable for Fedora src-git? > > > > The most obvious open source alternative would be the open source > > version of GitLab. There is also Pagure. I think we're giving up on > > open source infrastructure rather quickly here. I'd like to know what > > the candidates think before voting. > > > > Context: > > https://pagure.io/fedora-source-git/sig/issue/1 > > > https://communityblog.fedoraproject.org/fedora-council-and-the-git-forge/ > > Well, it's too late to have this as an official question on the > interview, but it doesn't hurt to ask. > I actually briefly mentioned this topic in my last interview for > FESCo, one year ago (last paragraph, the "open question"): > > https://communityblog.fedoraproject.org/fesco-election-interview-with-fabio-valentini-decathorpe-4/ > > And since nothing has happened in this space, and my opinion has not > changed, I didn't want to just provide the same answer in this year's > interview again, but I can reiterate my opinion here, with a freshly > typed version: > > I think switching from a well-integrated, fully open-source solution > (pagure + pagure-dist-git) that was developed under the Fedora Project > umbrella to a proprietary solution from a vendor with an "open core" > business model is a bad idea, sends the wrong message to the FOSS > community, and should be avoided, if at all possible. Philosophical > issues aside, I also fear that switching out the "forge" would mean > losing integration with other Fedora services again. Some features > were lost when pkgdb2 was retired, but almost everything is now > available again in the pagure/pagure-dist-git UI or other places, and > switching to GitLab would mean reimplementing all those integrations > from scratch, using the GitLab API - and if I remember correctly, at > least some of the necessary features or APIs are only available in the > proprietary "Ultimate" tier of GitLab - which means either losing > features, or giving up on a FOSS solution, and neither should be > acceptable. > > TL;DR: I do not support switching to proprietary software, especially > if there's already a well-integrated FOSS alternative deployed to > production. > > I'm pretty sure I'm also "on the record" with that opinion since the > pagure / GitLab issue originally come up over a year ago, in both > mailing list archives and FESCo votes associated with this issue. :) > > Fabio > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora elections voting now open
Ok thanks On Sat, 27 Nov 2021 at 17:19, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, Nov 27, 2021 at 04:35:24PM +0000, Ahmed Almeleh wrote: > > Are candidates allowed to vote on their own application? I voted for > > council / mindshare as i'm not in the running for those. > > Yes, we don't think there's any expectation that candidates will not > vote. > > Zbyszek > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora elections voting now open
Are candidates allowed to vote on their own application? I voted for council / mindshare as i'm not in the running for those. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: jpegxl soname bump
yikes On Sun, 21 Nov 2021, 20:40 Scott Talbert, wrote: > Hi @eclipseo, > > Looks like jpegxl soname was bumped, breaking a bunch of stuff: > > 2021-11-21 20:20:51 > Package resolution failed > > Problem: package gd-2.3.3-3.fc36.x86_64 requires > libavif.so.12()(64bit), but none of the providers can be installed > - package graphviz-2.49.3-2.fc36.x86_64 requires libgd.so.3()(64bit), > but none of the providers can be installed > - package libavif-0.9.2-2.fc35.x86_64 requires libaom.so.3()(64bit), > but none of the providers can be installed > - conflicting requests > - nothing provides libjxl.so.0()(64bit) needed by > libaom-3.1.2-1.fc35.x86_64 > - nothing provides libjxl.so.0(JXL_0)(64bit) needed by > libaom-3.1.2-1.fc35.x86_64 > Problem: package graphviz-2.49.3-2.fc36.x86_64 requires > libgd.so.3()(64bit), but none of the providers can be installed > - package gd-2.3.3-3.fc36.x86_64 requires libavif.so.12()(64bit), but > none of the providers can be installed > - package doxygen-2:1.9.1-12.fc36.x86_64 requires graphviz, but none > of the providers can be installed > - package libavif-0.9.2-2.fc35.x86_64 requires libaom.so.3()(64bit), > but none of the providers can be installed > - conflicting requests > - nothing provides libjxl.so.0()(64bit) needed by > libaom-3.1.2-1.fc35.x86_64 > - nothing provides libjxl.so.0(JXL_0)(64bit) needed by > libaom-3.1.2-1.fc35.x86_64 > > Thanks, > Scott > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A way to request/vote for packages to add next to Fedora Linux?
I do see your point though On Fri, 19 Nov 2021, 12:12 Neal Gompa, wrote: > On Fri, Nov 19, 2021 at 7:05 AM Ahmed Almeleh > wrote: > > > > I do think voting for packages to be included in the next Fedora release > is an amazing idea maybe we could create a survey through Google forms or > make a custom website for Fedora. I.e. Telling users select all packages > you would like to see in Fedora 36. > > > > It's a horrible idea, because it will just lead to disappointed users. > Nothing compels anyone to do anything about that, so people who fill > them out and see no results would just get angry at us. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: A way to request/vote for packages to add next to Fedora Linux?
I do think voting for packages to be included in the next Fedora release is an amazing idea maybe we could create a survey through Google forms or make a custom website for Fedora. I.e. Telling users select all packages you would like to see in Fedora 36. On Fri, 19 Nov 2021, 09:59 Tomasz Torcz, wrote: > On Fri, Nov 19, 2021 at 05:32:28AM -, Reon Beon via devel wrote: > > Video2X would be a nice add. > > There's a package wishlist here: > https://fedoraproject.org/wiki/Package_maintainers_wishlist > > But adding the package there is no guarantee anyone will pick it up. > I believe most items are there for years without action. > Best way is to become a packager and add a package by yourself: > > https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ > > -- > Tomasz Torcz Morality must always be based on practicality. > to...@pipebreaker.pl — Baron Vladimir Harkonnen > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: RFC: Reduce number of packages that are built for i686
I see your point, I am a part of the Quality Assurance team here.
+1 Making it easier on package maintainers
+1 On retiring all i686 (32 Bit Systems)
On Wed, 17 Nov 2021, 11:18 Fabio Valentini, wrote:
> On Wed, Nov 17, 2021 at 11:53 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Tue, Nov 16, 2021 at 03:05:37PM -0500, Robbie Harwood wrote:
>
> (small snip)
>
> > > Is it really not? This seems the easiest way to go about it, honestly
> -
> > > just have it be permitted for maintainers to opt their stuff out of
> > > building on x86 and let the problem take care of itself recursively.
> >
> > Yeah, I think I'd go this way too. Instead of trying to maintain this
> > centrally in koji, do it at package level, using proven-packager
> privileges
> > to smooth the initial process.
> >
> > I.e. something like: OK, we don't want to build libreoffice for i686.
> > libreoffice is annotated with "ExcludeArch: %{ix86}", and *at the same
> time*
> > any packages which (transitively) BR:libreoffice, are also annotated.
> > (They don't even need to be rebuild.)
> > And then repeat for another "big" package.
> >
> > I think this way to go is OK because we mostly care about some of the
> > "big" packages that take a long time to build. Most low-level packages
> > build just fine on i686 so we don't care if they are built unnecessarily.
> >
> > And obviously the advantage is that this can be done now, and doesn't
> > require any new infra or maintenance. The only trick would be how to
> > figure out the transitive BR tree, but apparently there are some scripts
> > that people have.
>
> I really *don't* think a manual, individual opt-out like this is a good
> idea.
>
> Imagine the scenario where a package maintaner unilaterally adds
> "ExcludeArch: %{ix68}" to one of their packages. This might be an
> honest mistake, for example, because the repoquery was not done
> correctly, or because they thought that nothing depends on that
> package. Then, this results in cascading build failures of all
> dependent packages, because a broken build on any arch fails the whole
> build, requiring cascading changes to all packages in the dependency
> tree, more work for all manitainers that are involved.
>
> Because I think we should respect package maintainers' time, I don't
> think I should put the burden of figuring this out and fixing
> breakages on them, which is why I suggested a centralized approach
> that will not put more work on *every single package maintainer*.
>
> Fabio
> ___
> 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
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
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
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: F37 Change: RetireARMv7 (System-Wide Change proposal)
I agree that the ARMv7 architecture is in decline and echo the opinion of Zbigniew that the user base will be very low once the EOL for F36 falls. Overall I think it is best to remove the ARMv7 architecture. It may also make it easier to push advanced features into new releases quicker. Thanks, Ahmed Almeleh, Fedora QA On Tue, 16 Nov 2021 at 08:02, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Nov 15, 2021 at 02:15:49PM -0500, Ben Cotton wrote: > > https://fedoraproject.org/wiki/Changes/RetireARMv7 > > > > == Owner == > > * Name: [[User:pbrobinson| Peter Robinson]] > > * Email: > > > > == Detailed Description == > > > > The ARMv7 arm architecture was the second variant of the arm > > architecture that Fedora has supported, the first was ARMv5, the third > > is aarch64. The proposal is to retire ARMv7 as part of the Fedora 37 > > release. This will allow ARMv7/armhfp to be supported until the Fedora > > 36 end of life in around June 2023. > > > > Overall arm32 is generally waning with generally few new ARMv7 devices > > added to Fedora in recent releases. To add to that a number of newer > > Fedora features designed to improve speed and security of the Fedora > > release are causing 32 bit architectures in general primarily due to > > "issues" or "problems" seems to be missing in this sentence. > > > the process memory limit when linking large applications. The > > ARMv7/armhfp is the last fully supported 32 bit architecture, we still > > currently build i686 packages, but it's not shipped as artefacts. > > "it's" → "they are"? > > > == User Experience == > > Any current users of Fedora on ARMv7 devices won't be able to upgrade > > to Fedora 37, they will have to stay on Fedora 36 until it's EOL. > > Please add "and will have to retire the hardware or move to a different > distribution afterwards". Explicit is good. > > > == Release Notes == > > > > Fedora Linux 37 with the ARMv7 architecture is retired into the > > sunset. There will definitely be celebrations, there will likely be > > some that shed some tears! Overall for the maintainers it will likely > > be seen as a net win, for the few, generally shrinking, users it's > > probably a net loss but they can probably just go and buy a Raspberry > > Pi Zero 2W for US$15. ¯\_(ツ)_/¯ > > Based on the countme graphs that mattdm has been showing, the fraction > on arm32 systems is very very small. And arm32 has been a drag on > maintainer resources, with the slow builds and timeouts. Dropping the > arch will not be without some pain for the people using those boards, > but I think it's the right thing to do for the distro. And the whole > thing will happen more then a year from now, and by that time the > number of those arm32 boards will be even lower. > > Zbyszek > ___ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
