Re: Self Introduction: Adam McCartney
On 3/16/24 5:03 AM, Adam McCartney wrote: Dear Fedora Developers, Thanks for your work in developing and maintaining such a useful Linux distribution! I'm relatively new to open source development and am trying to make my first contributions. Basically, I'm hoping to package some dependencies for the `nix and `guix package managers in fedora. To give a bit of backstory, in the past both package managers have depended on nscd[1], which has been recently removed from glibc. Since it had been marked for deprecation in glibc, distributions have been removing their reliance on it's functionality [2]. There has been some discussion on the guix mailing list about possible replacements for nscd. A popular suggestion is to transition to nsncd, a program written in rust that provides similar functionality. Following this dicussion I volunteered to package nsncd for fedora. I've started the process by packaging some upstream dependencies. This is my first attempt at contributing packages to fedora (or any distro for that matter!). Fabio Valentini has been very helpful in providing some guidance and reviewing my initial bug report[3]. I'm a little bit unsure of the next steps are for having the package accepted. I would welcome any further advice or guidance that you could provide. With kind regards, Adam Welcome Adam! We are glad you are here. I look forward to seeing your contributions to Fedora. :) Joe -- Joe Doss j...@solidadmin.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
Re: Introduction
On 2/17/24 6:38 AM, Loren M. Lang wrote: Hello all, I am looking to get more involved in the Fedora Project and contributing back into it. I have been using Linux since Red Hat Linux 5.1 was released in 1998. Since then, I have been able to provide a variety of contributions back to various projects including Debian, Ubuntu, and even FreeBSD. I tend to work mostly in either C, Python, or Rust but can work in a variety of languages. Over the last few years, Fedora has become one of my main drivers for development and I'd like to give back and help maintain some packages in need of loving. I am looking forward to joining the community and offering my assistance. Welcome Loren! We are all glad that you are here. :) Joe -- Joe Doss j...@solidadmin.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
Re: Self Introduction: Tim Semeijn
On 10/12/23 4:17 PM, tim--- via devel wrote: Hey everyone, My name is Tim Semeijn and I am an infrastructure engineer from The Netherlands. I have been in the Fedora ecosystem as a user for many years and the last few years I got more and more into building RPMs for personal/hobby use. I wanted to directly contribute to the source and decided to try become a packager for Fedora. My first package got approved a few days ago (thanks Steve Cossette) and Neal Gompa stepped up to the plate to sponsor me. My focus now will be on showing my understanding of RPM packaging by doing unofficial package reviews. Looking forward to being part of this wonderful community! Welcome Tim! You are in wonderful hands with Neal as your sponsor. I can't wait to see your contributions added to the project. Joe -- Joe Doss j...@solidadmin.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
Re: New contributor interested in taking maintainership of SWORD, Xiphos, and Bibletime
On 9/29/23 1:10 PM, Aaron Rainbolt wrote: Hello, and thanks for your time. I am a former (and possibly future) Ubuntu and Lubuntu Developer who recently started using Fedora on some of my systems. I have about a year of experience in Linux distro development from my previous work with Lubuntu and Ubuntu. After trying Fedora, I liked it so much I decided I wanted to contribute to it, and discovered that the SWORD package had become orphaned and retired due to a bug in its Python bindings. As I use SWORD and programs it depends on in my day-to-day work, I decided I'd like to try to fix SWORD and become its maintainer. Over the last few days I've worked to get the SWORD package into a usable and policy-compliant state, including: * Fixing the Python-related bug * Updating the packaging to comply with the current Fedora Packaging Guidelines * Doing a full license audit of the SWORD code * Clarifying the licensing of various files with upstream * Asking for one non-free component to be relicensed under a Fedora-compatible license (a request which was granted) * Repacking the upstream tarball to remove optional non-free components After discussion with the SWORD developers, I found that the original maintainer of SWORD in Fedora also maintained Xiphos and Bibletime, two applications which depend on SWORD and are closely related to it. For this reason, I would like to become the maintainer of all three ultimately, though for the moment I'm only actively pursuing maintainership of SWORD since it's the only package that needs help at the moment. Depending on how things go, I also am interested in assisting with the development of Fedora LXQt Spin, as it is quite similar to Lubuntu, a project I worked closely with for about a year. I hope I can be valuable to the Fedora community! Thanks for your help, and have a great day! Heck yeah Aaron! Welcome to the party! I am glad you are here. :) Joe -- Joe Doss j...@solidadmin.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
Re: An update on RHEL moving to issues.redhat.com
On 9/9/23 1:27 AM, Adam Williamson wrote: On Sat, 2023-09-09 at 04:17 +, Gary Buhrmaster wrote: On Sat, Sep 9, 2023 at 1:05 AM Brendan Conoboy wrote: RHEL making this change does not imply or require that Fedora do the same. I am neither suggesting Fedora should do so, or not do so, but just as a hypothetical, should Fedora choose to do so, do you know if RedHat would be amenable for such use of issues.redhat.com for Fedora bug tracking(*). I think this would be a non-starter as Jira is not F/OSS. Fedora infra must be F/OSS by policy. Obligatory uhh not JIRA comment. (sorry, kinda) Joe -- Joe Doss j...@solidadmin.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
Re: Election Status?
On 5/24/23 4:49 PM, Mattia Verga via devel wrote: Wait, what?? Someone at RH wakes up in the morning and decides to cut one of the key roles (or better, THE) of Fedora community and this goes completely unannounced, unnoticed and without any backup plan? I have seen other dumb decisions by RH about Fedora in the past, but I think this is the greatest one, both for Ben's role and for their person. I totally agree. I am pretty upset that they chose to let bcotton go. His work was top notch and I will miss him and his contributions. Losing him as the Fedora Program Manager is going to be very impacting to the project in the short to medium term. We are already seeing things fall through the cracks. What a short-sighted decision. Also finding out about this in a random thread is a bummer. There should have been an announcement. To the RH powers that be that made this decision. You chuckleheads dun goofed. Joe -- Joe Doss j...@solidadmin.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
Re: Self Introduction: Miguel Bernal Marin
On 4/8/23 7:52 PM, Miguel Bernal Marin wrote: Hi Fedora community, My name is Miguel Bernal Marin and usually my nickname is miguelinux, I work at Intel corporation in Guadalajara, Jalisco, Mexico and I would like to add some new packages from Intel to Fedora and keep maintaining them. I will look for a sponsor for those package in a near future. Regarded my past experience on open source projects, I was in the Clear Linux team maintaining some packages, and I had contributed to others open source projects. My FAS user is miguelinux. Welcome Miguel. I am glad you have joined us! :) Joe -- Joe Doss j...@solidadmin.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
Re: Self Introduction: Dalton Hubble
On 2/22/23 11:19 PM, Dalton Hubble wrote: I'm an engineer working in the Go, cloud, and infrastructure space. I've been a Linux user for a while, a Fedora user for the last ~8 years, and used to work for CoreOS. I maintain a few open source Go libraries, maintain a Kubernetes distro, and operate the AS207563 network. When I can, I enjoy hiking and tinkering on my infra. Glad to have you with us Dalton! I am a very big fan of Typhoon and Matchbox! :D Joe -- Joe Doss j...@solidadmin.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
Re: Package naming suggestion?
On 2/7/23 8:28 PM, Chris Adams wrote: I've got a few useful Nagios monitoring plugins I'd like to add to Fedora/EPEL. I'm rather unimaginative at naming, so the Github repo for them is "nagios-plugins-cmadams"... while I wouldn't mind having a package with my username in it in Fedora, it seems a little vain. :) Before I go making a package and submitting a new package ticket, any suggestions about that? https://github.com/cmadamsgit/nagios-plugins-cmadams My two cents. I am a big fan of packages that are very explicit on what they are in the name. Doing a `dnf search nagios` turns up that most plugins start with nagios-plugin- so your current repo name follows that established convention. I'd say leave it as is and get that package submitted. :) Joe -- Joe Doss j...@solidadmin.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
Re: Self Introduction: Dale Turner
On 12/26/22 12:18 PM, Dale Turner via devel wrote: Hello everyone. My name is Dale Turner, and I am new to the list. I live in Nova Scotia, Canada. I have been using Fedora Linux since 2008 (version 9). At that time, I decided Microsoft Windows was not really for me, so I began looking elsewhere. I considered several Linux distributions before finally choosing Fedora. I like that Fedora is always pushing forward and is very up-to-date. I really like that Fedora works so closely with upstream, so that when Fedora solves a problem, it benefits everyone, not just the Fedora users. The community also seems excellent. My professional background is healthcare. I have no formal computer training, so I am best considered a hobbyist/enthusiast/user. Although new to the list, I have viewed the archives many times. I have been building packages for some time, both locally on my machine and COPR (https://copr.fedorainfracloud.org/coprs/dturner/ <https://copr.fedorainfracloud.org/coprs/dturner/>). I have also filed a few bugs over the years. The main reason for me finally posting to this list is that I noticed xaos is now unmaintained. I am not in the Packager group, but I think I would be able to maintain this package, or at least assist. It is not critical to any system, but is interesting to me, and hopefully would not be too daunting a task. I do have a successful build in my COPR. Thanks for everything, and your consideration. Welcome Dale. I am glad you joined us! :) -- Joe Doss j...@solidadmin.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
Re: Self Introduction: Simon Bachenberg
On 11/11/22 3:15 AM, Simon Bachenberg wrote: Ideally, I would like Fedora to become the standard Linux client of the Deutsche Welle instead of Ubuntu. But I would also like to help make Fedora even better and more popular. Welcome Simon. I agree with you and I am glad you have joined us. :) Joe -- Joe Doss j...@solidadmin.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
Re: status update on "ostree native containers"
On 9/27/22 5:08 PM, Colin Walters wrote: But back to Fedora CoreOS, another thing that's happened recently is https://github.com/coreos/coreos-layering-examples has matured and has many functional examples of using this. We're getting increasingly close to the point where I want to call this all stable, so it's a great time if you haven't to kick the tires and try it out! This looks fantastic Colin. I will definitely be checking this out. Joe -- Joe Doss j...@solidadmin.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
Re: Self Introduction: Kate Hsuan
On 6/21/22 12:42 AM, Kate Hsuan wrote: Hi Folks, My name is Kate Hsuan. I'm a software engineer from Red Hat. Currently, I'm working on integration with fwupd, gnome-shell, and gnome settings. They can be used to show the firmware security details and warnings to the user to reduce the risk of the security event. Before joining Red Hat, I'm working on ONAP DCAE project. ONAP is an open-source network automation framework for the telecom industry. We had developed a microservice to collect every message from the message bus for analysis to find the abnormal events. Now, I am going to work on package maintenance for libusb, libusb1, and libusb-compat. Thank you :) Welcome Kate!! Glad you are with us. :) -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Possibly off topic: Slack will discontinue packaging for Fedora
On 11/5/21 12:41 AM, Benson Muite wrote: The Mattermost client is open source and will connect to Slack. There are a number of packages in copr: https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=mattermost Thanks for the suggestion but I prefer the official client for work. Joe -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Possibly off topic: Slack will discontinue packaging for Fedora
On 11/4/21 8:55 PM, Joe Doss wrote: It would be cool if we could rally some sort of support on our end to help Slack produce a functioning RPM. I hit up some buds that used to work at Slack to see if they can help connect us with some folks there to work this out. Joe -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Possibly off topic: Slack will discontinue packaging for Fedora
On 11/4/21 7:23 PM, Gordon Messmer wrote: I don't know if that's of interest to Fedora, as an organization, but on the off-chance that it is: Is anyone in a position to ask someone at Slack about that decision? And whether there's anything that Fedora can do to make publishing that package more feasible? I have had an open support ticket for over 6 months with Slack Support about idle detection being totally broken since Fedora 33 on GNOME + Wayland with their RPM. Slack stopped detecting when I was idle on my workstations and it would never send notifications to mobile devices. They responded recently this was working as intended(?) and tried to close the ticket which was a real bummer. Fortunately The flatpak works just fine. It would be cool if we could rally some sort of support on our end to help Slack produce a functioning RPM. Joe -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F34 Cloud Amazon AMIs unbootable after updates
On 10/6/21 3:18 PM, Christopher wrote: Hi, Has anybody else noticed that the Amazon Public Cloud images for F34 (https://alt.fedoraproject.org/cloud/) no longer boot after the latest updates? I had an instance that I've been keeping up-to-date with dnf system upgrades and is now on F34, which is now unbootable after recent updates within the last week. So I tried to create a new instance using a newer base image at https://alt.fedoraproject.org/cloud/, and that one is also now unbootable after doing a routine dnf update. Has anybody else seen this? Does anybody know which package update caused it? (I saw some grub-related updates, but not sure if they are to blame) Does anybody know how to fix a currently broken instance and can share their solution? Is there anything on the console log when you reboot it after the updates? If you can share the log that would be helpful. Joe -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Donate 1 minute of your time to test upgrades from F34 to F35
On 9/7/21 11:14 AM, Miroslav Suchý wrote: > Do you want to make Fedora 35 better? Please spend 1 minute of your time > and try to run: Heck yeah! Sign me up! > # Run this only if you use default Fedora modules > # next time you run any DNF command default modules will be enabled again > sudo dnf module reset '*' > > sudo dnf --releasever=35 --setopt=module_platform_id=platform:f35 \ > > --enablerepo=updates-testing --enablerepo=updates-testing-modular \ > > distro-sync > > This command does not replace `dnf system-upgrade`, but it will reveal > potential problems. > > You may also run `dnf upgrade` before running this command. > > > If you get this prompt: > > ... > Total download size: XXX M > Is this ok [y/N]: > > you can answer N and nothing happens, no need to test the actual upgrade. Install 89 Packages Upgrade3833 Packages Remove6 Packages Downgrade22 Packages Total download size: 4.1 G Is this ok [y/N]: n Operation aborted. LGTM! Ohhh yeah!! Joe -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora CoreOS stable stream now rebased to Fedora 34
On 5/19/21 4:13 PM, Michael Catanzaro wrote: FYI we are using zram in other Fedora editions. zswap is different. Sorry, got my names mixed up. Thanks Michael! Joe -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora CoreOS stable stream now rebased to Fedora 34
On Wed, May 19, 2021 at 2:45 AM Clement Verna wrote: I think this is the fundamental difference here, Fedora CoreOS does not have a version number. It has 3 streams, stable, testing and next, these streams are based on a version of Fedora Linux but that should just be a detail that most end users should not have to care about. I disagree here. Fedora CoreOS has the Fedora name in it and it should have the same fundamental features and changes that ship with each Fedora release. To say it doesn't have a base version and that users shouldn't care about it is pretty dismissive. Another difference is that Fedora CoreOS has automatic updates and if we want our users to trust these automatic updates we need them to be rock solid. This leads to Fedora CoreOS being more conservative on how changes are rolled out to users, taking the example rolling out cgroups v2 in the Fedora 31 time frame would have broken all users that are using Docker to run their containers and this was not acceptable :-). If some users are getting confused and get curious about why there are these differences and learn more about how Fedora CoreOS works, that's a good thing IMO :-) Confusing and frustrating your users is a bad thing. On 5/19/21 6:54 AM, Neal Gompa wrote: No. This is a cop-out and a bad answer. The reason this happened is because Fedora CoreOS historically has not participated in the development of Fedora Linux, including the Changes process, and generally rolled back features instead of adapting with them during the development cycle. It's not like making changes and breaking upgrades is acceptable in Fedora Linux either. It's just that the Fedora CoreOS WG has not participated in the main development process and rolled back changes instead of adapting to them, which has frustrated pretty much everyone. The containers team in particular was extremely unhappy to find out cgroup v1 was still used in FCOS. I was pretty cheesed off when I discovered the sqlite rpmdb feature was rolled back in FCOS. In general, I'm not pleased with how Fedora CoreOS does this. Hopefully they will do better in the future. I'll echo Neal's sentiment here. This is a cop-out and bad answer. It is frustrating to consume FCOS only to see features that are in the current release of Fedora are rolled back. Even in today's FCOS WG meeting I brought up adding in zswap to FCOS and it is shelved until Kubernetes adds for support swap enabled systems. The RHCOS and Openshift teams should be back porting these breaking changes, so FCOS can look to the future with Fedora. FCOS should not be shackled by limits imposed by RHCOS/Openshift/Kubernetes. Joe -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Mock fedora-34-x86_64 on Fedora 34 beta broken
Hey devel, Is anyone else getting this issue on Fedora 34 beta when using mock with the fedora-34-x86_64 chroot? mock -r fedora-33-x86_64 shell works just fine on Fedora 34 beta. Also mock -r fedora-34-x86_64 shell works on Fedora 33. What is the best way to troubleshoot this? I already nuked all the containers and repulled them. mock -r fedora-34-x86_64 shell INFO: mock.py version 2.9 starting (python version = 3.9.4, NVR = mock-2.9-2.fc34)... Start(bootstrap): init plugins INFO: selinux enabled Finish(bootstrap): init plugins Start: init plugins INFO: selinux enabled Finish: init plugins INFO: Signal handler active Start: run Start(bootstrap): chroot init INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start(bootstrap): cleaning package manager metadata Finish(bootstrap): cleaning package manager metadata INFO: enabled HW Info plugin INFO: Using bootstrap image: registry.fedoraproject.org/fedora:34 INFO: Pulling image: registry.fedoraproject.org/fedora:34 Trying to pull registry.fedoraproject.org/fedora:34... Getting image source signatures Copying blob sha256:999e4fc5d528c12d604e932457da70575edba2e190e4b49889e6c0329ebf Copying config sha256:e9a62e90440de88a10995fec385993016911aa3410abee8d50035e84e430bb40 Writing manifest to image destination Storing signatures e9a62e90440de88a10995fec385993016911aa3410abee8d50035e84e430bb40 Error: no container with name or ID "time=\"2021-04-14T10:40:24-05:00\" level=warning msg=\"The input device is not a TTY. The --tty and --interactive flags might not work properly\"\n0810c4332dc722feede422372be9a57b397003cb75309bfde00a04340ee5b953" found: no such container ERROR: Command failed: # podman exec time="2021-04-14T10:40:24-05:00" level=warning msg="The input device is not a TTY. The --tty and --interactive flags might not work properly" 0810c4332dc722feede422372be9a57b397003cb75309bfde00a04340ee5b953 /usr/bin/dnf -y install dnf dnf-plugins-core -- Joe Doss j...@solidadmin.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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package Review: github-cli 1.1.0
On 10/27/20 10:47 AM, Joe Doss wrote: On 10/27/20 10:11 AM, Joe Doss wrote: On 10/16/20 11:21 AM, Joe Doss wrote: Hello all, Here is the updated package review request for github-cli 1.1.0 ... golang-github-cli-shurcool-graphql https://bugzilla.redhat.com/show_bug.cgi?id=1888971 golang-github-shurcool-githubv4 https://bugzilla.redhat.com/show_bug.cgi?id=1888972 Still looking for two last package reviews so I can move forward on including the GitHub CLI package in Fedora. These need reviews too: https://bugzilla.redhat.com/show_bug.cgi?id=1888966 https://bugzilla.redhat.com/show_bug.cgi?id=1888966 https://bugzilla.redhat.com/show_bug.cgi?id=1888968 Can someone reapprove these packages since they hit the arbitrary 60 day age limit and I can't reapprove them myself. https://bugzilla.redhat.com/show_bug.cgi?id=1803309 https://bugzilla.redhat.com/show_bug.cgi?id=1803312 https://bugzilla.redhat.com/show_bug.cgi?id=1803303 This paper pushing process sucks for new packages sucks and it's super frustrating to navigate. Joe -- Joe Doss j...@solidadmin.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
Re: Package Review: github-cli 1.1.0
On 10/27/20 10:11 AM, Joe Doss wrote: On 10/16/20 11:21 AM, Joe Doss wrote: Hello all, Here is the updated package review request for github-cli 1.1.0 ... golang-github-cli-shurcool-graphql https://bugzilla.redhat.com/show_bug.cgi?id=1888971 golang-github-shurcool-githubv4 https://bugzilla.redhat.com/show_bug.cgi?id=1888972 Still looking for two last package reviews so I can move forward on including the GitHub CLI package in Fedora. These need reviews too: https://bugzilla.redhat.com/show_bug.cgi?id=1888966 https://bugzilla.redhat.com/show_bug.cgi?id=1888966 https://bugzilla.redhat.com/show_bug.cgi?id=1888968 -- Joe Doss j...@solidadmin.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
Re: Package Review: github-cli 1.1.0
On 10/16/20 11:21 AM, Joe Doss wrote: Hello all, Here is the updated package review request for github-cli 1.1.0 ... golang-github-cli-shurcool-graphql https://bugzilla.redhat.com/show_bug.cgi?id=1888971 golang-github-shurcool-githubv4 https://bugzilla.redhat.com/show_bug.cgi?id=1888972 Still looking for two last package reviews so I can move forward on including the GitHub CLI package in Fedora. Thanks! Joe -- Joe Doss j...@solidadmin.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
Package Review: github-cli 1.1.0
Hello all, Here is the updated package review request for github-cli 1.1.0 and the eleven dependency... Ooof. github-cli https://bugzilla.redhat.com/show_bug.cgi?id=1803302#c8 golang-github-netflix-expect https://bugzilla.redhat.com/show_bug.cgi?id=1803309 golang-github-hinshun-vt10x https://bugzilla.redhat.com/show_bug.cgi?id=1803312 golang-github-alecaivazis-survey https://bugzilla.redhat.com/show_bug.cgi?id=1803303 golang-github-muesli-reflow https://bugzilla.redhat.com/show_bug.cgi?id=1888965 golang-github-muesli-termenv https://bugzilla.redhat.com/show_bug.cgi?id=1888966 golang-github-charmbracelet-glamour https://bugzilla.redhat.com/show_bug.cgi?id=1888967 golang-github-henvic-httpretty https://bugzilla.redhat.com/show_bug.cgi?id=1888968 golang-github-rivo-uniseg https://bugzilla.redhat.com/show_bug.cgi?id=1888970 golang-github-cli-shurcool-graphql https://bugzilla.redhat.com/show_bug.cgi?id=1888971 golang-github-shurcool-githubv4 https://bugzilla.redhat.com/show_bug.cgi?id=1888972 golang-github-enescakir-emoji https://bugzilla.redhat.com/show_bug.cgi?id=1888974 -- Joe Doss j...@solidadmin.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
Re: our containers with alias vim=vi
On 10/12/20 1:50 AM, Zdenek Dohnal wrote: This would break using Vim when vim-minimal and vim-enhanced are installed (it would start Vi instead of typed Vim). To make it work, vim-minimal would have to conflict with vim-enhanced, which doesn't make sense - Vi and Vim binaries can exist together just fine. I have vim-enhanced and vim-minimal installed # rpm -qa |grep vim vim-common-8.2.1770-1.fc33.x86_64 vim-filesystem-8.2.1770-1.fc33.noarch vim-minimal-8.2.1770-1.fc33.x86_64 vim-enhanced-8.2.1770-1.fc33.x86_64 and when I type vi it launches vim. # whereis vi vi: /usr/bin/vi /usr/share/man/man1p/vi.1p.gz /usr/share/man/man1/vi.1.gz # /usr/bin/vi --version VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 29 2020 00:00:00) It doesn't look like these are existing together just fine. It seems that vim takes over vi. Shouldn't these conflict and only one can be installed over the other? In the end I find it incorrect to mislead users by default by telling them 'Vim works' but Vi is run instead - Vi and Vim don't have the same set of features, which may lead into bug reports caused by this mistake. Isn't that the reverse behavior detailed above? I type vi on Fedora Workstation it launches vim? I assume this isn't causing bug reports. Joe -- Joe Doss j...@solidadmin.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
Re: our containers with alias vim=vi
On 10/10/20 7:37 AM, clime wrote: Didn't want to write about this first but maybe there are more people with the same problem. You are not alone. I had to set the same alias for Fedora CoreOS because I kept typing vim out of habit and FCOS ships vim-minimal. It was driving me nuts. Maybe the vim-minimal package needs the alias instead? I have been adding the alias on my end because it felt like a personal problem on my end, but I am sure there are more of us. Joe -- Joe Doss j...@solidadmin.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
GitHub CLI was Re: Orphaning 'hub' (the git wrapper for Github)
On 9/29/20 12:07 PM, Joe Doss wrote: On 9/29/20 10:44 AM, Rich Megginson wrote: Is there a plan to package `gh` in Fedora? https://bugzilla.redhat.com/show_bug.cgi?id=1803302 I am slogging through it slowly. OK, I have things built for Rawhide and F33. You can check it out here https://copr.fedorainfracloud.org/coprs/jdoss/github-cli/builds/ if you want to give it a spin. I will file the BZ new package paperwork to get the 11 new RPMs reviewed once I emotionally recover from this Golang RPM packaging adventure in the next day or so. Oh, and if we want it in F32 sooner rather than later this needs some Karma: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c199daf5b3 A special shout out to Robert-André Mauchin for helping me off list with all of my go2rpm / Golang RPM questions. Joe -- Joe Doss j...@solidadmin.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
Re: splitting out systemd-networkd, systemd-standalone-{sysusers,tmpfiles} subpackages in F33+
On 9/30/20 7:14 PM, Colin Walters wrote: That's not true, you can `rpm-ostree override remove`. It'd still be there in the ostree repository on disk, but you don't see it in the "deployment" (what you actually boot into). Few people care about disk space that much, and if you do you can do custom builds. ...but can we can do that and will updates to FCOS work after? I am pretty sure currently the answer is no, unless I don't fully understand the impacts of https://github.com/coreos/fedora-coreos-tracker/issues/400 I would be making tons of package changes to my deployment of FCOS but the chance of breaking updates isn't worth it. Even after this split happens and you can install systemd-networkd will I break my updates then too? About half the people on this thread are living the experience ofhttps://xkcd.com/386/ Ehh. There has been a lot of talking past each other in this thread and in https://github.com/coreos/fedora-coreos-config/pull/574 which is the reason for this thread in the first place. All of this grief and extra work could have be avoided if we added added the ~1M of hacked out systemd-networkd binaries back into FCOS and moved on with our lives... but here we are! Joe -- Joe Doss j...@solidadmin.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
Re: splitting out systemd-networkd, systemd-standalone-{sysusers,tmpfiles} subpackages in F33+
On 9/30/20 4:36 PM, Neal Gompa wrote: On Wed, Sep 30, 2020 at 5:27 PM Matthew Miller wrote: "All Fedora variants, both with ostree and without..." maybe? OSTree-based variants are also "regular Fedora". I would only even remotely consider agreeing with that premise for Silverblue. Neither Fedora CoreOS nor Fedora IoT qualify for that, in my view, since they completely sidestep the normal release engineering process, don't use the same repositories, and have the power to include and exclude packages from the total available package set at their leisure. There is no expectation with those variants that anything you do will necessarily show up there. Heck, Fedora CoreOS is reverting a system-wide change in its variant (SQLite rpmdb), and had previously also reverted another one (cgroup v2). The merits of those changes aside, this makes the experience materially different than everything else we have. This is a pretty good point Neal. Let's take cgroups v2 for example. The expectation of Fedora 32 having cgroups v2 is pretty clear, but stable FCOS which is based off of Fedora 32 has cgroups v1 enabled instead. This is a pretty jarring experience when you are moving from say Fedora 32 Cloud to FCOS 32.20200907.3.0. Both say Fedora 32 in their versions, but have a totally different technical experience when it comes to cgroups. Same can be said with systemd-networkd, but I won't rehash what is already said in https://github.com/coreos/fedora-coreos-config/pull/574 FCOS and Fedora IOT carry the Fedora name but they break ranks with the rest of Fedora in terms of packages, release engineering, and Fedora wide changes. This leads to frustrating experiences as a Fedora user because the technical expectations of what should be Fedora wide technical stances are a moving target for these variants. Joe -- Joe Doss j...@solidadmin.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
Re: Orphaning 'hub' (the git wrapper for Github)
On 9/29/20 10:44 AM, Rich Megginson wrote: Is there a plan to package `gh` in Fedora? https://bugzilla.redhat.com/show_bug.cgi?id=1803302 I am slogging through it slowly. Joe -- Joe Doss j...@solidadmin.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
Re: wireguard kmod package
On June 25, 2020 4:50:12 PM Justin Forbes wrote: On Thu, Jun 25, 2020 at 6:33 AM Leigh Scott wrote: From what I understood of the thread it's purely removing the akmod and the new kernels have the module so how does it break their VPNs? If you remove akmod-wireguard it will also remove the wireguard package which will cause the VPN to stop functioning. Wireguard/wireguard-tools is required for a working VPN. That would be a rather serious flaw in the wireguard tools package to have a dep on akmod-wireguard when it has been upstream and included in the Fedora kernel-modules package for a few months at this point. wirerguard-tools has no dep on akmod-wireguard? Unless I'm misunderstanding the point you are trying to make here? ___ 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: wireguard kmod package
On 6/24/20 5:36 PM, Peter Robinson wrote: As rpmfusion isn't an official Fedora repository the kernel wouldn't obsolete it, how would that work for the 100s of quasi fedora repos that spring up all over the place? Maybe rpmfusion should have something akin to fedora-obsolete-package for components such as kernel-modules that are cleanly replaced by something like kernel bits that are there by default. Maybe the wireguard-tools package might want to obsolete it. This package isn't an official install method for WireGuard. My copr and elrepo for EL are. Obsoleting it isn't something that should be done in wireguard-tools IMO. Joe -- Joe Doss j...@solidadmin.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
Re: wireguard kmod package
On 6/24/20 4:28 PM, Przemek Klosowski via devel wrote: It was akmod-wireguard (thanks Laura, Alexander, Joe, Leigh and Ian). This leaves the question: Shouldn't kernel>5.6.0 obsolete kmod-wireguard and akmod-wireguard? and maybe replace wireguard with wireguard-tools? Looking at this RPM's change log it looks like they are doing that: * Tue Apr 14 2020 Nicolas Chauvet - 0.0.20191219-3 - Disable wireguard until obsoleted https://pkgs.rpmfusion.org/cgit/free/wireguard-kmod.git/commit/?h=f31=2c0a54bad7eed78c459a5f41ff1f4d71070e626c -- Joe Doss j...@solidadmin.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
Re: wireguard kmod package
On 6/24/20 4:02 PM, Przemek Klosowski via devel wrote: repo id repo name code Visual Studio Code (blush) fedora Fedora 31 - x86_64 fedora-cisco-openh264 Fedora 31 openh264 (From Cisco) - x86_64 fedora-modular Fedora Modular 31 - x86_64 rpmfusion-free RPM Fusion for Fedora 31 - Free rpmfusion-free-updates RPM Fusion for Fedora 31 - Free - Updates rpmfusion-nonfree RPM Fusion for Fedora 31 - Nonfree rpmfusion-nonfree-updates RPM Fusion for Fedora 31 - Nonfree - Updates updates Fedora 31 - x86_64 - Updates updates-modular Fedora Modular 31 - x86_64 - Updates This is most likely coming from the rpmfusion-free repo and it should be safe to remove if you are running a kernel higher than 5.6.0. Joe -- Joe Doss j...@solidadmin.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
Re: [External] Re: Fedora+Lenovo
On 4/30/20 10:10 PM, Mark Pearson wrote: > As a note - if you do have the 00bd device: firmware is on LVFS but it's in > testing state (should be released really soon). If you do enable > lvfs-testing > and do an update to get it installed then fingerprints should work with F32 > (they did for my X1C7 and P1G2) Yes!!! This works on my T490s! fwupdmgr enable-remote lvfs-testing fwupdmgr refresh fwupdmgr update fwupdmgr disable-remote lvfs-testing Then go Settings > Users and enable fingerprint login. No more fumbling my login password while running late for standup without coffee! Yes! YES!! Joe -- Joe Doss j...@solidadmin.com signature.asc Description: OpenPGP digital signature ___ 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: Packaging of github cli?
On 2/17/20 10:40 AM, Richard Shaw wrote: > I might when I have some time but it looks like a lot of dependent > package reviews! :) I think we are good on reviews now. It did have a lot of dependencies. Ooof! Joe -- Joe Doss j...@solidadmin.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
Re: Packaging of github cli?
On 2/15/20 5:10 AM, Till Hofmann wrote: > Would you mind submitting builds for F30? Some people (me) are still on > F30... Sure! It wasn't building on F30 for some reason but I am looking at some other Golang packages that are not building on F30 too so I will look into it. Joe -- Joe Doss j...@solidadmin.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
Re: Packaging of github cli?
On 2/14/20 12:36 PM, Joe Doss wrote: > I will see what it takes to get this submitted for review this weekend. Here we go https://bugzilla.redhat.com/show_bug.cgi?id=1803302 If anyone has any some time to give these package a review that would be great. Joe -- Joe Doss j...@solidadmin.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
Re: Packaging of github cli?
On 2/14/20 10:23 AM, Joe Doss wrote: > On 2/14/20 9:56 AM, Richard Shaw wrote: >> Anyone working on packaging github's CLI? >> >> https://github.com/cli/cli >> >> I've never packaged a GO application before... > > I have a spec I am working on right now. I will try to get it up on my > Copr this weekend. Well that was easier than I thought. https://copr.fedorainfracloud.org/coprs/jdoss/github $ dnf copr enable jdoss/github $ dnf install github-cli I will see what it takes to get this submitted for review this weekend. Joe -- Joe Doss j...@solidadmin.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
Re: Packaging of github cli?
On 2/14/20 9:56 AM, Richard Shaw wrote: > Anyone working on packaging github's CLI? > > https://github.com/cli/cli > > I've never packaged a GO application before... I have a spec I am working on right now. I will try to get it up on my Copr this weekend. Joe -- Joe Doss j...@solidadmin.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
Re: What would it take to drop release and changelog from our spec files? (and do we want to?)
On 1/12/20 3:19 PM, Marius Schwarz wrote: > Am 10.01.20 um 17:36 schrieb Pierre-Yves Chibon: >> Good Morning Everyone, >> >> This is not a new idea, it has been presented at flock last year and spoken >> about on this very list this fall, so I'd like to push it a little further. >> >> Do we want to drop release and changelog from our spec file? > Vote: no. > > The correct releases and changelogs in the rpms are important to check > for security patches made. This need of any admin will override > any argument for a removal, as it's the most important source on a > working system to gather it's security state. Finally the reply I was looking for! As someone who relies the changelog of the RPM for security reasons this whole thread has me worried. On 1/12/20 3:38 PM, Miro Hrončok wrote: > It would stay in the RPM, we would just populate it differently and it > would no longer be hardcoded in the spec file in our infrastructure. How will it be populated? Will it ensure that the information that is important for security minding end users is still available? Sorry in advance if I missed the details of how it would still be managed and included for end users to consume? Thanks! Joe -- Joe Doss j...@solidadmin.com pEpkey.asc Description: application/pgp-keys ___ 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: Let's talk about Fedora in the '20s!
On 1/7/20 11:33 AM, Adam Williamson wrote: > If anyone has a handy generous multi-millionaire up their sleeve, > please call Matt. :) *coughs* Red Hat... Joe -- Joe Doss j...@solidadmin.com pEpkey.asc Description: application/pgp-keys ___ 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: Defining the future of the packager workflow in Fedora
On 9/26/19 11:57 AM, Ken Dreyer wrote: I would like to hear if you see Pagure as still strategic, and if so, how we can make these common user operations faster. I always wondered why Fedora home rolled their own Github/Gitlab clone. Using either Github or Gitlab would be better for new users to get started with helping to contribute back to Fedora without having to jump through hoops to figure out how to work around the pitfalls of Pagure. Joe -- Joe Doss j...@solidadmin.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
Re: Orphaning cloud-init, python-boto
On 8/13/19 8:54 AM, Dusty Mabe wrote: On 8/10/19 9:06 PM, Garrett Holmstrom wrote: Hi, My time to work on Fedora cloud-related things has diminished in recent months, so I have not been able to give the cloud-init and python-boto packages the care they deserve. They are free to a good home. Can you give cloud-init to me and major hayden (@mhayden) for now? Dusty I can help in a pinch on these packages as well to back up Dusty and Major. Joe -- Joe Doss j...@solidadmin.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
Re: Fixing Wireguard spec file
On 2/4/19 6:38 PM, Dominique Martinet wrote: It's the second time I read wireguard would be coming in the 5.0 kernel here - what makes you folk say that? I certainly haven't seen anything to that extent lately and 5.0 is petty well under way, something as big a zinc likely won't make the cut this late. The people that are working on WireGuard think things should be stable by this summer (June) so it most likely won't make 5.0 but something a bit after. My point is, I rather spend my efforts stabilizing the DKMS packages that have worked for years now, rather than change things totally over to using an akmod based approach. Especially with the possibility of having WireGuard upstream sometime this year. (as for akmods, it's packaged as such as well in rpmfusion, and that just works afaict) Indeed. If those fit peoples needs, I urge them to use them. Joe -- Joe Doss j...@solidadmin.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fixing Wireguard spec file
Was dkms working before you did the upgrade or was it already in a broken state? wireguard-dkms-0.0.20190123-2.fc29.noarch won't fix an already broken install, so you need to remove it and then install the new version. It should hopefully fix it moving forward. I started a thread on the WireGuard mailing list to track this issue https://lists.zx2c4.com/pipermail/wireguard/2019-February/003851.html so please reply there with any feedback once the next snapshot is released. Thanks, Joe ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fixing Wireguard spec file
I know what akmods are and I don't have the bandwidth on my end to switch to them with WireGuard coming in the 5.0 kernel. Joe ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fixing Wireguard spec file
Hey Germano, I have a working RPM that does not error out with Error! Could not locate dkms.conf file if you want to test it out before I push it to copr. https://copr-be.cloud.fedoraproject.org/results/jdoss/wireguard-testing/fedora-29-x86_64/00852015-wireguard-dkms/wireguard-dkms-0.0.20190123-2.fc29.noarch.rpm It is an issue with DKMS as I suspected. `%post` runs before the new package's `%preun` and the --rpm_safe_upgrade isn't working as it should. https://github.com/dell/dkms/issues/25#issuecomment-360275619. I followed this post's suggestion and moved from %post to %posttrans and this issue no longer happens. It feels hacky and I might spend some more time this weekend trying to find a better solution. ZFS worked around it with a bunch of bash https://github.com/zfsonlinux/zfs/blob/master/rpm/generic/zfs-dkms.spec.in#L74-L102 so that might be what we try down the road. If anyone on the list has a better idea on how to work around this issue please let me know. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fixing Wireguard spec file
I am actively trying to track down why DKMS is not removing the old WireGuard version correctly. I suspect it is something to do with DKMS as other WireGuard users that use DKMS for things like ZFS (https://utcc.utoronto.ca/~cks/space/blog/linux/MyKernelUpdateSteps) are setting the same kinds of issues. If anyone on this list has any insight on what might be the cause, please let me know. Joe ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
