Re: [CentOS-devel] [EPEL-devel] RHEL moving to issues.redhat.com only long term
The package I need is redhat-lsb-core. I built the package, and its dependencies on RHEL 9 from SRPMs downloaded from an RHEL 8 instance. I am using a developer subscription of Red Hat. Thanks --- Lee On Fri, May 20, 2022 at 1:57 AM Josh Boyer wrote: > > On Thu, May 19, 2022 at 4:11 PM Kevin Fenzi wrote: > > > > On Thu, May 19, 2022 at 07:37:46AM +0200, Branislav Náter wrote: > > > Hi, > > > > > > On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee > > > wrote: > > > > > > > Hi, > > > > > > > > I am trying to request a package for RHEL 9, but I cannot find RHEL > > > > under Projects at issues.redhat.com. > > > > What is the correct project for RHEL 9 ? > > > > > > > > > > You have to file a bug for "distribution" component in Bugzilla. > > > > Please don't file it there. :) > > Small point of clarification. If you want to add a package to Red Hat > Enterprise Linux 9 (the product), then you should likely open a > support case via the Customer Portal and request it as an RFE. > > If you want to request a subpackage of an existing RHEL 9 package that > is not included in RHEL, follow this and replace 8 with 9: > https://wiki.centos.org/FAQ/CentOS8/UnshippedPackages > > If you want to add a package to Extra Packages for Enterprise Linux 9 > (the wonderful community project), then follow what Kevin says below. > > It really depends on the exact thing you are after. > > josh > > > > Take a look at the handy doc: > > > > https://docs.fedoraproject.org/en-US/epel/epel-package-request/ > > > > If anything is unclear there, please do let us know. > > > > While RHEL may be moving to jira with RHEL10, EPEL is very likely to > > stay with whatever Fedora is using (currently bugzilla). > > > > kevin > > ___ > > CentOS-devel mailing list > > centos-de...@centos.org > > https://lists.centos.org/mailman/listinfo/centos-devel > > ___ > CentOS-devel mailing list > centos-de...@centos.org > https://lists.centos.org/mailman/listinfo/centos-devel ___ 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
[EPEL-devel] Re: [CentOS-devel] RHEL moving to issues.redhat.com only long term
Hi, I filed on Bugzilla. I wondered why there is no such option on issues.redhat.com (Jira ?). Thanks --- Lee On Thu, May 19, 2022 at 11:08 AM Branislav Náter wrote: > > Hi, > > On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee wrote: >> >> Hi, >> >> I am trying to request a package for RHEL 9, but I cannot find RHEL >> under Projects at issues.redhat.com. >> What is the correct project for RHEL 9 ? > > > You have to file a bug for "distribution" component in Bugzilla. > > Regards > B. > >> >> >> Thanks >> >> --- >> Lee >> >> >> On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer wrote: >> > >> > Hi Fedora, CentOS, and EPEL Communities! >> > >> > As part of our continued 3 year major Red Hat Enterprise Linux release >> > cadence, RHEL 9 development is starting to wrap up with the spring >> > 2022 release coming soon. That means planning for the next release >> > will start in earnest in the very near future. As some of you may >> > know, Red Hat has been using both Bugzilla and Jira via >> > issues.redhat.com for RHEL development for several years. Our >> > intention is to move to using issues.redhat.com only for the major >> > RHEL releases after RHEL 9. >> > >> > What does this mean for Fedora and CentOS? This discussion is in part >> > to figure that out. Based on some very brief analysis, the following >> > should hold: >> > >> > - RHEL customers should continue to file support cases through the Red >> > Hat Customer portal, which will remain consistent regardless of the >> > backend tooling used. >> > >> > - There is no imminent retirement of the Red Hat Bugzilla instance >> > being planned at this time. RHEL 7, 8, and 9 will continue to use >> > bugzilla in some form and RHEL 9 has a very long lifecycle. >> > >> > - Fedora Linux and EPEL have their own Bugzilla product families and >> > are not directly impacted in their own workflows by the choice to use >> > only issues.redhat.com for RHEL. >> > - There will be impacts on existing documentation that provide >> > guidance on requesting things from RHEL in various places like EPEL. >> > We will be happy to help adjust these. >> > >> > - CentOS Stream contribution and bug reporting workflows will be >> > adjusted to use issues.redhat.com instead of bugzilla in the relevant >> > places. This should apply to all versions of CentOS Stream for a >> > unified contributor workflow. This will happen gradually as we >> > discover the best workflow to use. >> > >> > If there are other impacts that you can think of, please raise them on >> > this thread. We’d like to ensure we’re covering as much as possible >> > as this rolls out. >> > >> > josh >> > ___ >> > epel-devel mailing list -- epel-devel@lists.fedoraproject.org >> > To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org >> > Do not reply to spam on the list, report it: >> > https://pagure.io/fedora-infrastructure >> ___ >> CentOS-devel mailing list >> centos-de...@centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel > > > > -- > Branislav Náter > Principal Quality Engineer, Stacks QE > IRC: bnater at #qa #urt #brno > Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > ___ > CentOS-devel mailing list > centos-de...@centos.org > https://lists.centos.org/mailman/listinfo/centos-devel ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [CentOS-devel] [EPEL-devel] RHEL moving to issues.redhat.com only long term
Hi, I filed on Bugzilla. I wondered why there is no such option on issues.redhat.com (Jira ?). Thanks --- Lee On Thu, May 19, 2022 at 11:08 AM Branislav Náter wrote: > > Hi, > > On Thu, May 19, 2022 at 4:15 AM Thomas Stephen Lee wrote: >> >> Hi, >> >> I am trying to request a package for RHEL 9, but I cannot find RHEL >> under Projects at issues.redhat.com. >> What is the correct project for RHEL 9 ? > > > You have to file a bug for "distribution" component in Bugzilla. > > Regards > B. > >> >> >> Thanks >> >> --- >> Lee >> >> >> On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer wrote: >> > >> > Hi Fedora, CentOS, and EPEL Communities! >> > >> > As part of our continued 3 year major Red Hat Enterprise Linux release >> > cadence, RHEL 9 development is starting to wrap up with the spring >> > 2022 release coming soon. That means planning for the next release >> > will start in earnest in the very near future. As some of you may >> > know, Red Hat has been using both Bugzilla and Jira via >> > issues.redhat.com for RHEL development for several years. Our >> > intention is to move to using issues.redhat.com only for the major >> > RHEL releases after RHEL 9. >> > >> > What does this mean for Fedora and CentOS? This discussion is in part >> > to figure that out. Based on some very brief analysis, the following >> > should hold: >> > >> > - RHEL customers should continue to file support cases through the Red >> > Hat Customer portal, which will remain consistent regardless of the >> > backend tooling used. >> > >> > - There is no imminent retirement of the Red Hat Bugzilla instance >> > being planned at this time. RHEL 7, 8, and 9 will continue to use >> > bugzilla in some form and RHEL 9 has a very long lifecycle. >> > >> > - Fedora Linux and EPEL have their own Bugzilla product families and >> > are not directly impacted in their own workflows by the choice to use >> > only issues.redhat.com for RHEL. >> > - There will be impacts on existing documentation that provide >> > guidance on requesting things from RHEL in various places like EPEL. >> > We will be happy to help adjust these. >> > >> > - CentOS Stream contribution and bug reporting workflows will be >> > adjusted to use issues.redhat.com instead of bugzilla in the relevant >> > places. This should apply to all versions of CentOS Stream for a >> > unified contributor workflow. This will happen gradually as we >> > discover the best workflow to use. >> > >> > If there are other impacts that you can think of, please raise them on >> > this thread. We’d like to ensure we’re covering as much as possible >> > as this rolls out. >> > >> > josh >> > ___ >> > epel-devel mailing list -- epel-de...@lists.fedoraproject.org >> > To unsubscribe send an email to epel-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/epel-de...@lists.fedoraproject.org >> > Do not reply to spam on the list, report it: >> > https://pagure.io/fedora-infrastructure >> ___ >> CentOS-devel mailing list >> centos-de...@centos.org >> https://lists.centos.org/mailman/listinfo/centos-devel > > > > -- > Branislav Náter > Principal Quality Engineer, Stacks QE > IRC: bnater at #qa #urt #brno > Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > ___ > CentOS-devel mailing list > centos-de...@centos.org > https://lists.centos.org/mailman/listinfo/centos-devel ___ 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: [EPEL-devel] RHEL moving to issues.redhat.com only long term
Hi, I am trying to request a package for RHEL 9, but I cannot find RHEL under Projects at issues.redhat.com. What is the correct project for RHEL 9 ? Thanks --- Lee On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer wrote: > > Hi Fedora, CentOS, and EPEL Communities! > > As part of our continued 3 year major Red Hat Enterprise Linux release > cadence, RHEL 9 development is starting to wrap up with the spring > 2022 release coming soon. That means planning for the next release > will start in earnest in the very near future. As some of you may > know, Red Hat has been using both Bugzilla and Jira via > issues.redhat.com for RHEL development for several years. Our > intention is to move to using issues.redhat.com only for the major > RHEL releases after RHEL 9. > > What does this mean for Fedora and CentOS? This discussion is in part > to figure that out. Based on some very brief analysis, the following > should hold: > > - RHEL customers should continue to file support cases through the Red > Hat Customer portal, which will remain consistent regardless of the > backend tooling used. > > - There is no imminent retirement of the Red Hat Bugzilla instance > being planned at this time. RHEL 7, 8, and 9 will continue to use > bugzilla in some form and RHEL 9 has a very long lifecycle. > > - Fedora Linux and EPEL have their own Bugzilla product families and > are not directly impacted in their own workflows by the choice to use > only issues.redhat.com for RHEL. > - There will be impacts on existing documentation that provide > guidance on requesting things from RHEL in various places like EPEL. > We will be happy to help adjust these. > > - CentOS Stream contribution and bug reporting workflows will be > adjusted to use issues.redhat.com instead of bugzilla in the relevant > places. This should apply to all versions of CentOS Stream for a > unified contributor workflow. This will happen gradually as we > discover the best workflow to use. > > If there are other impacts that you can think of, please raise them on > this thread. We’d like to ensure we’re covering as much as possible > as this rolls out. > > josh > ___ > epel-devel mailing list -- epel-de...@lists.fedoraproject.org > To unsubscribe send an email to epel-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/epel-de...@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
[EPEL-devel] Re: RHEL moving to issues.redhat.com only long term
On Wed, Mar 16, 2022 at 12:00 PM Thomas Stephen Lee wrote: > > On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer wrote: > > > > Hi Fedora, CentOS, and EPEL Communities! > > > > As part of our continued 3 year major Red Hat Enterprise Linux release > > cadence, RHEL 9 development is starting to wrap up with the spring > > 2022 release coming soon. That means planning for the next release > > will start in earnest in the very near future. As some of you may > > know, Red Hat has been using both Bugzilla and Jira via > > issues.redhat.com for RHEL development for several years. Our > > intention is to move to using issues.redhat.com only for the major > > RHEL releases after RHEL 9. > > > > What does this mean for Fedora and CentOS? This discussion is in part > > to figure that out. Based on some very brief analysis, the following > > should hold: > > > > - RHEL customers should continue to file support cases through the Red > > Hat Customer portal, which will remain consistent regardless of the > > backend tooling used. > > > > - There is no imminent retirement of the Red Hat Bugzilla instance > > being planned at this time. RHEL 7, 8, and 9 will continue to use > > bugzilla in some form and RHEL 9 has a very long lifecycle. > > > > - Fedora Linux and EPEL have their own Bugzilla product families and > > are not directly impacted in their own workflows by the choice to use > > only issues.redhat.com for RHEL. > > - There will be impacts on existing documentation that provide > > guidance on requesting things from RHEL in various places like EPEL. > > We will be happy to help adjust these. > > > > - CentOS Stream contribution and bug reporting workflows will be > > adjusted to use issues.redhat.com instead of bugzilla in the relevant > > places. This should apply to all versions of CentOS Stream for a > > unified contributor workflow. This will happen gradually as we > > discover the best workflow to use. > > > > If there are other impacts that you can think of, please raise them on > > this thread. We’d like to ensure we’re covering as much as possible > > as this rolls out. > > > > josh > > Hi, > > I tried logging in with my Red Hat id to see what it is. > I got the below message. > -%<- > SAML Single Sign On failed > Please contact your administrator and provide the tracker-id X or > log in at the login page. > SAML-Login failed: You’ve logged in with username user.name but you > already have an account on Jira, so please relogin with email_id > -%<- > > Thanks > > --- > Lee Issue resolved by Red Hat support. Now I am able to log in. --- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: RHEL moving to issues.redhat.com only long term
On Mon, Mar 7, 2022 at 11:14 PM Josh Boyer wrote: > > Hi Fedora, CentOS, and EPEL Communities! > > As part of our continued 3 year major Red Hat Enterprise Linux release > cadence, RHEL 9 development is starting to wrap up with the spring > 2022 release coming soon. That means planning for the next release > will start in earnest in the very near future. As some of you may > know, Red Hat has been using both Bugzilla and Jira via > issues.redhat.com for RHEL development for several years. Our > intention is to move to using issues.redhat.com only for the major > RHEL releases after RHEL 9. > > What does this mean for Fedora and CentOS? This discussion is in part > to figure that out. Based on some very brief analysis, the following > should hold: > > - RHEL customers should continue to file support cases through the Red > Hat Customer portal, which will remain consistent regardless of the > backend tooling used. > > - There is no imminent retirement of the Red Hat Bugzilla instance > being planned at this time. RHEL 7, 8, and 9 will continue to use > bugzilla in some form and RHEL 9 has a very long lifecycle. > > - Fedora Linux and EPEL have their own Bugzilla product families and > are not directly impacted in their own workflows by the choice to use > only issues.redhat.com for RHEL. > - There will be impacts on existing documentation that provide > guidance on requesting things from RHEL in various places like EPEL. > We will be happy to help adjust these. > > - CentOS Stream contribution and bug reporting workflows will be > adjusted to use issues.redhat.com instead of bugzilla in the relevant > places. This should apply to all versions of CentOS Stream for a > unified contributor workflow. This will happen gradually as we > discover the best workflow to use. > > If there are other impacts that you can think of, please raise them on > this thread. We’d like to ensure we’re covering as much as possible > as this rolls out. > > josh Hi, I tried logging in with my Red Hat id to see what it is. I got the below message. -%<- SAML Single Sign On failed Please contact your administrator and provide the tracker-id X or log in at the login page. SAML-Login failed: You’ve logged in with username user.name but you already have an account on Jira, so please relogin with email_id -%<- Thanks --- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Pre-release EPEL
On Thu, Sep 16, 2021 at 8:21 PM Troy Dawson wrote: > > EPEL Next[1][2] is meant for machines running CentOS Stream. > We currently have epel8-next, and are working on getting epel9-next setup so > that maintainers can build on it. > Technically epel9-next will be a "Pre-Release" of epel9, but saying it is a > "pre-release" implies that it will go away. > epel9-next will not go away when epel9 is released, but will continue to be > for machines running CentOS Stream 9 > > Brought to you by the EPEL ELves > > [1] - https://docs.fedoraproject.org/en-US/epel/#what_is_epel_next > [2] - https://docs.fedoraproject.org/en-US/epel/epel-about-next/ > > On Thu, Sep 16, 2021 at 7:30 AM Stephen Gallagher wrote: >> >> On Thu, Sep 16, 2021 at 10:11 AM Neal Gompa wrote: >> > >> > On Thu, Sep 16, 2021 at 9:38 AM Thomas Stephen Lee >> > wrote: >> > > >> > > Hi, >> > > >> > > Thanks to people on the CentOS mailing list. >> > > We managed to get CentOS Stream 9 pre-release with updates working on a >> > > VM. >> > > Is there also a pre-release version of EPEL 9 we can use? >> > > >> > >> > Not just yet, I'm hoping that'll be soon... >> >> The EPELves are working as hard as they can, stay tuned! >> ___ >> epel-devel mailing list -- epel-devel@lists.fedoraproject.org >> To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure > > ___ We will wait. Keep up the excellent work. Thanks --- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Pre-release EPEL
Hi, Thanks to people on the CentOS mailing list. We managed to get CentOS Stream 9 pre-release with updates working on a VM. Is there also a pre-release version of EPEL 9 we can use? Thanks --- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] RHEL 8.3
Hi, RHEL 8.3 got released. --- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: TeamViewer on RHEL 8 and qt. Help needed
Hi, Working fine now. Thanks a lot. did dnf install qt5-qtwebchannel qt5-qtsensors qt5-qtlocation qt5-qtbase-gui qt5-qtx11extras qt5-qtdeclarative thanks. -- Thomas Stephen Lee On Tue, Sep 24, 2019 at 12:17 AM Troy Dawson wrote: > On Mon, Sep 23, 2019 at 10:53 AM Stephen John Smoogen > wrote: > > > > On Mon, 23 Sep 2019 at 12:31, Thomas Stephen Lee > wrote: > > > > > > Hi, > > > > > > download the tar version and extract > > > > > > https://download.teamviewer.com/download/linux/teamviewer_amd64.tar.xz > > > > > > cd to the folder > > > > > > run > > > > > > ./tv-setup checklibs > > > > > > the output shows > > > > > > - > > > Analyzing dependencies ... > > > libQt5Positioning.so.5 => not found > > > libQt5Sensors.so.5 => not found > > > libQt5WebChannel.so.5 => not found > > > > > > The libraries listed above seem to be missing. > > > > > > > You need to install qt5-qtwebchannel qt5-qtsensors qt5-qtlocation > > qt5-qtbase-gui qt5-qtx11extras qt5-qtdeclarative and probably a bunch > > others.. > > > > dnf repoquery --whatprovides=libQt5WebKitWidgets.so.5 > > > > and similar will tell you what is needed > > > > > -- > > > > > > and it also asks to run the command. > > > > > > dnf install 'libdbus-1.so.3()(64bit)' 'libQt5Gui.so.5()(64bit)' > 'libQt5Widgets.so.5()(64bit)' 'libQt5Qml.so.5()(64bit)' > 'libQt5Quick.so.5()(64bit)' 'libQt5WebKitWidgets.so.5()(64bit)' > 'libQt5X11Extras.so.5()(64bit)' 'libqtquick2plugin.so()(64bit)' > 'libwindowplugin.so()(64bit)' 'libqquicklayoutsplugin.so()(64bit)' > 'libqtquickcontrolsplugin.so()(64bit)' 'libdialogplugin.so()(64bit)' > > > > > > > From teh above the following don't seem available: > > > > libwindowplugin.so > > libqquicklayoutsplugin.so > > libdialogplugin.so > > > > but they don't show up in a Fedora 30 box either so I am guessing it > > needs something not listed. > > > > Correct. > This isn't a RHEL8 thing. > > > > > > > Ran the command on RHEL 8 and most libraries are missing > (epel-playground and epel-testing repos are enabled). > > > Is it something to do with RHEL 8 not supporting KDE? > > > > > > What is the solution to get TeamViewer working on RHEL 8? > > From the teamviewer page > https://www.teamviewer.com/en-us/download/linux/ > you can download an rpm designed for CentOS and Fedora > > https://www.teamviewer.com/en-us/teamviewer-automatic-download/?package=teamviewer=x86_64.rpm=linux > > That package seems to be able to install on both Fedora and RHEL8 with > epel8-playground enabled. > > > > > > > thanks. > > > > > > -- > > > Thomas Stephen Lee > > > ___ > > > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > > > To unsubscribe send an email to > epel-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/epel-devel@lists.fedoraproject.org > > > > > > > > -- > > Stephen J Smoogen. > > ___ > > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > > To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] TeamViewer on RHEL 8 and qt. Help needed
Hi, download the tar version and extract https://download.teamviewer.com/download/linux/teamviewer_amd64.tar.xz cd to the folder run ./tv-setup checklibs the output shows - Analyzing dependencies ... libQt5Positioning.so.5 => not found libQt5Sensors.so.5 => not found libQt5WebChannel.so.5 => not found The libraries listed above seem to be missing. -- and it also asks to run the command. dnf install 'libdbus-1.so.3()(64bit)' 'libQt5Gui.so.5()(64bit)' 'libQt5Widgets.so.5()(64bit)' 'libQt5Qml.so.5()(64bit)' 'libQt5Quick.so.5()(64bit)' 'libQt5WebKitWidgets.so.5()(64bit)' 'libQt5X11Extras.so.5()(64bit)' 'libqtquick2plugin.so()(64bit)' 'libwindowplugin.so()(64bit)' 'libqquicklayoutsplugin.so()(64bit)' 'libqtquickcontrolsplugin.so()(64bit)' 'libdialogplugin.so()(64bit)' Ran the command on RHEL 8 and most libraries are missing (epel-playground and epel-testing repos are enabled). Is it something to do with RHEL 8 not supporting KDE? What is the solution to get TeamViewer working on RHEL 8? thanks. -- Thomas Stephen Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: [Fedocal] Reminder meeting : EPEL Steering Co
Hi All, you probably have seen this. https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/thread/F6Z7KFVNHB26NXL2IROARWZQVQPT7J6O/ thanks. On Tue, Aug 27, 2019 at 11:30 PM wrote: > Dear all, > > You are kindly invited to the meeting: >EPEL Steering Co on 2019-08-28 from 18:00:00 to 19:00:00 GMT >At freenode@fedora-meeting > > The meeting will be about: > This is the weekly EPEL Steering Committee Meeting. Agenda is in the > https://infinote.fedoraproject.org/cgit/infinote/tree/epel-meeting-next > > > Source: https://apps.fedoraproject.org/calendar/meeting/9364/ > > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: EPEL-ANNOUNCE EPEL-8 package requests are now open
Thank you all for releasing EPEL 8 -- Lee On Fri, Aug 9, 2019 at 3:12 AM Orion Poplawski wrote: > On 8/8/19 8:38 AM, Robert Scheck wrote: > > Hello Stephen, > > > > On Thu, 01 Aug 2019, Stephen John Smoogen wrote: > >> I would like to thank everyone for their patience and for the people who > >> have put in a lot of work to get us to where we can start building > >> packages. > > > > even it's late, I still want to thank you for your hard work on EPEL 8 > and > > for handling my perpetual nagging (is it the correct phrase?) very > kindly! > > > > For me, RHEL without EPEL is kind of incomplete in about all enviroments > I > > have or need to support - thus all efforts on EPEL are highly > appreciated. > > > > > > Regards, > > Robert > > A hearty second! EPEL is key to our use of EL. Thanks Stephen, Kevin, and > everyone else. > > > -- > Orion Poplawski > Manager of NWRA Technical Systems 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 https://www.nwra.com/ > > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: EPEL 8 on RHEL 8.1 Beta
Hi Stephen. Thanks for the update. -- Lee On Sat, Aug 3, 2019 at 4:24 AM Stephen John Smoogen wrote: > > > On Thu, 1 Aug 2019 at 01:47, Thomas Stephen Lee > wrote: > >> Hi, >> >> Trying to install EPEL 8 on RHEL 8.1 Beta. >> >> I did >> >> $ yum install >> https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/e/epel-release-8-1.noarch.rpm >> >> and doing >> >> $ yum update >> >> gives the error >> >> failed to open: >> /var/cache/dnf/epel-7223eb0d0c06d046/repodata/78c05abe94a83354e9759eacd446d11a44df882d8c45fbf74b147b09a7fd6c83-updateinfo.xml.zck >> >> > So this problem seems to be a bug in dnf versus anything we are doing. If > you use the dnf from the 8.0 release it will work perfectly well. However > the 8.1 version seems to barf on it. I am trying to find out if this is a > config issue we can tell dnf to ignore and have opened > https://bugzilla.redhat.com/show_bug.cgi?id=1737160 > > > > >> Tried changing baseurl in /etc/yum.repos.d/epel.repo to >> >> https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64 >> >> and >> >> https://dl.fedoraproject.org/pub/epel/testing/8/Everything/x86_64 >> >> both give the same error >> >> Kindly check. >> >> thanks >> >> -- >> Lee >> ___ >> epel-devel mailing list -- epel-devel@lists.fedoraproject.org >> To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org >> > > > -- > Stephen J Smoogen. > > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] EPEL 8 on RHEL 8.1 Beta
Hi, Trying to install EPEL 8 on RHEL 8.1 Beta. I did $ yum install https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/e/epel-release-8-1.noarch.rpm and doing $ yum update gives the error failed to open: /var/cache/dnf/epel-7223eb0d0c06d046/repodata/78c05abe94a83354e9759eacd446d11a44df882d8c45fbf74b147b09a7fd6c83-updateinfo.xml.zck Tried changing baseurl in /etc/yum.repos.d/epel.repo to https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64 and https://dl.fedoraproject.org/pub/epel/testing/8/Everything/x86_64 both give the same error Kindly check. thanks -- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] RHEL 8.1 Beta
Hi, https://www.redhat.com/en/blog/red-hat-enterprise-linux-81-beta-now-available RHEL 8.1 Beta released. -- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] RHEL 7.7 Beta
Hi, Just for your information. https://www.redhat.com/en/blog/red-hat-enterprise-linux-77-beta-now-available Python 3.6 is there in 7.7 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7-beta/html/7.7_release_notes/overview thanks -- Lee ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: EPEL 8 Beta/Alpha?
Hi All, https://www.redhat.com/en/enterprise-linux-8 RHEL 8 is released. thanks -- Lee On Mon, Feb 18, 2019 at 10:43 AM Thomas Stephen Lee wrote: > Hi All, > > Probably you already know this. > > RHEL 8 is based on Fedora 28 > > https://www.redhat.com/en/blog/road-red-hat-enterprise-linux-8-beta > > thanks > > -- > > Lee > > On Wed, Nov 28, 2018 at 7:47 PM Paul Howarth wrote: > >> On Wed, 28 Nov 2018 07:01:04 -0600 >> Richard Shaw wrote: >> >> > On Wed, Nov 28, 2018 at 5:29 AM Paul Howarth >> > wrote: >> > >> > > On Wed, 28 Nov 2018 10:53:58 +0530 >> > > >> > > I seem to remember that for EL-7 we generally just branched the f19 >> > > packages for epel7, rebuilt and that was pretty much it. >> > > >> > >> > I thought it was more of an "opt-in" situation, that packages that >> > had a EL -1 branch didn't automatically get an EL new branch? >> > >> > I would definitely like the opportunity to do some major version >> > upgrades of some of the packages I maintain. >> >> It was mostly opt-in as I recall it, but some packages got EPEL >> branches for the first time as they were needed as dependencies. Anyone >> packaging for EPEL-8 should of course be free to choose whichever >> version of their package is best suited to it; I think f19 was the >> latest at the time of the EL7 beta release when a lot of stuff got >> built. >> >> Paul. >> ___ >> epel-devel mailing list -- epel-devel@lists.fedoraproject.org >> To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org >> > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
