Re: Let's revisit the FTBFS policy

Dne 14. 08. 19 v 19:43 Miro Hrončok napsal(a): > On 14. 08. 19 19:22, Ben Cotton wrote: >> I want to publicly express my appreciation for Miro's efforts to >> enforce our policy and his willingness to take the hits from people >> being rightly upset at its flaws. I also appreciate that the

Schedule for Thursday's FPC Meeting (2019-08-15 16:00 UTC)

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2019-08-15 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): = Day: Thursday == 2019-08-15 09:00 PDT US/Pacific 2019-08-15

Re: Why retire Python 2 packages and games that still work to end user ?

On Wed, Aug 14, 2019 at 4:31 PM Kevin Kofler wrote: > > David Sommerseth wrote: > > Instead of spending time and resources keeping old stuff alive longer than > > needed, rather spend that energy on porting the old Python 2 over to > > Python 3. In the long run, this will result in far less work

[389-devel] 389 DS nightly 2019-08-15 - 93% PASS

https://fedorapeople.org/groups/389ds/ci/nightly/2019/08/15/report-389-ds-base-1.4.1.6-20190814gitca915d5.fc30.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Re: EPEL 8 not finding buildroot overrides

Here's the link... https://bodhi.fedoraproject.org/overrides/hdf5-1.10.5-3.el8 Which is showing as active. Thanks, Richard ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot

On Wed, 14 Aug 2019 at 18:07, Orion Poplawski wrote: > >> I see virt modules (from dnf module info virt): > >> 820190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > >> 820190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > >> 820190529063309 -

[HEADS UP] Fedora 32 Python 3.8 rebuilds have started in a side tag

Hello, in order to deliver Python 3.8, we are running a coordinated rebuild in a side tag.     https://fedoraproject.org/wiki/Changes/Python3.8 If you see a "Rebuild for Python 3.8" commit in your package, please don't rebuild it in regular rawhide. If you need to, please let me know, so we

Re: friday roundup of failing images in rawhide

On Friday, 2 August 2019 03:24:44 CEST Luya Tshimbalanga wrote: > > It appears the current packaged version is far behind the upstream > release. It would be nice a proven package release an updated version. > > > Luya Since I handled the previous update and have already one of the dependency

[EPEL-devel] Re: how to use epel8-playground?

Hi Troy! I created my branch for singularity from epel8, but that wouldn't make a difference, would it? When I do fedpkg push from epel8-playground I get Current branch cannot be pushed anywhere! Counting objects: 5, done. Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 327

[HEADS UP] Fedora 32 Python 3.8 rebuilds have started in a side tag

Hello, in order to deliver Python 3.8, we are running a coordinated rebuild in a side tag.     https://fedoraproject.org/wiki/Changes/Python3.8 If you see a "Rebuild for Python 3.8" commit in your package, please don't rebuild it in regular rawhide. If you need to, please let me know, so we

[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot

On 8/14/19 3:35 PM, Orion Poplawski wrote: > On 8/14/19 3:26 PM, Orion Poplawski wrote: >> On 8/14/19 2:54 PM, Stephen John Smoogen wrote: >>> On Wed, 14 Aug 2019 at 16:01, Orion Poplawski wrote: My zabbix40 build for epel8 failed:

[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot

On 8/14/19 3:26 PM, Orion Poplawski wrote: > On 8/14/19 2:54 PM, Stephen John Smoogen wrote: >> On Wed, 14 Aug 2019 at 16:01, Orion Poplawski wrote: >>> >>> My zabbix40 build for epel8 failed: >>> >>> https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678 >>> >>> DEBUG util.py:585:

[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot

On 8/14/19 2:54 PM, Stephen John Smoogen wrote: > On Wed, 14 Aug 2019 at 16:01, Orion Poplawski wrote: >> >> My zabbix40 build for epel8 failed: >> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678 >> >> DEBUG util.py:585: BUILDSTDERR: Error: >> DEBUG util.py:585: BUILDSTDERR:

[Bug 1385002] Upgrade perl-Pod-PseudoPod-LaTeX to 1.20190729

https://bugzilla.redhat.com/show_bug.cgi?id=1385002 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #4 from

Re: RFC: Drop lz4-static

> "DS" == David Sommerseth writes: DS> As I can see it, there is little benefit of removing lz4-static. Isn't that entirely the decision of those maintaining the package? It's still completely reasonable if they want to remove it for no other reason than it eliminates ten lines from the

Re: Unretire linuxconsoletools package

Thanks Vascom. I've just found my fpc based build failing in Rawhide due to that. Marcin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: Why retire Python 2 packages and games that still work to end user ?

On Wed, 14 Aug 2019 at 16:31, Kevin Kofler wrote: > > David Sommerseth wrote: > > Instead of spending time and resources keeping old stuff alive longer than > > needed, rather spend that energy on porting the old Python 2 over to > > Python 3. In the long run, this will result in far less work

Re: Unretire txt2tags package?

On 14. 08. 19 22:52, Christoph Junghans wrote: Do I need a review to unretire this package? No. It was not retired for 8 weeks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To

[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot

On Wed, 14 Aug 2019 at 16:01, Orion Poplawski wrote: > > My zabbix40 build for epel8 failed: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678 > > DEBUG util.py:585: BUILDSTDERR: Error: > DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests > DEBUG util.py:585:

Re: Unretire txt2tags package?

On Wed, Aug 14, 2019 at 12:20 PM Miro Hrončok wrote: > > On 14. 08. 19 20:03, Christoph Junghans wrote: > > Hi, > > > > txt2tags was recently retired due to FTBFS > > (https://bugzilla.redhat.com/show_bug.cgi?id=1676168) as it requires > > python2. > > Just a note: We haven't retired any package

Re: Why retire Python 2 packages and games that still work to end user ?

On 14. 08. 19 22:28, Kevin Kofler wrote: It is not practical to get all the legacy Python 2 code ported over to Python 3. Keeping Python 2 (or something backwards-compatible with it such as Tauthon) available is actually the much more scalable approach. We are keeping the Python 2 interpreter.

Re: RFC: Drop lz4-static

On 14/08/2019 07:49, Igor Gnatenko wrote: > Hello, > > I found out that nothing in Fedora depends on lz4-static (neither > runtime nor buildtime). Is anybody using it or I'm free to drop it? > > Any thoughts? Ehm ... This is a _static_ library. Which means you can build against it, uninstall

Re: Why retire Python 2 packages and games that still work to end user ?

David Sommerseth wrote: > Instead of spending time and resources keeping old stuff alive longer than > needed, rather spend that energy on porting the old Python 2 over to > Python 3. In the long run, this will result in far less work over time. It is not practical to get all the legacy Python 2

[EPEL-devel] libssh2 issues in EPEL8 buildroot

My zabbix40 build for epel8 failed: https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678 DEBUG util.py:585: BUILDSTDERR: Error: DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests DEBUG util.py:585: BUILDSTDERR: - nothing provides libssh2(x86-64) =

Re: Let's revisit the FTBFS policy

On 14. 08. 19 19:43, Miro Hrončok wrote: E.g. when we release Fedora 32, Fedora 28 is already EOL for 5 months. It is IMHO reasonable to expect the packages were rebuilt at least on Fedora 29. Oh. When we release Fedora 32, Fedora 29 is already EOL for 5 months. But the rest checks out. So

Re: Let's revisit the FTBFS policy

- Original Message - > From: "Miro Hrončok" > To: devel@lists.fedoraproject.org > Sent: Wednesday, August 14, 2019 7:43:13 PM > Subject: Re: Let's revisit the FTBFS policy > > On 14. 08. 19 19:22, Ben Cotton wrote: > > I want to publicly express my appreciation for Miro's efforts to > >

Re: Join the new Minimization Team

> Here's the scriptlet: > > %triggerun libs -- krb5-libs < 1.15.1-5 > if ! grep -q 'includedir /etc/krb5.conf.d' /etc/krb5.conf ; then > sed -i '1i # To opt out of the system crypto-policies > configuration of krb5, > remove the\n# symlink at /etc/krb5.conf.d/crypto-policies which will > not

Re: Why does anaconda-core runtime depend on python3-coverage?

On Wed, 2019-08-14 at 11:29 -0700, Brian C. Lane wrote: > On Mon, Aug 12, 2019 at 08:44:24PM +0200, Igor Gnatenko wrote: > > What is the point of this? I am probably missing something obvious.. > > I think this was because getting good coverage data from anaconda > without actually booting the

Re: Why does anaconda-core runtime depend on python3-coverage?

On Mon, Aug 12, 2019 at 08:44:24PM +0200, Igor Gnatenko wrote: > What is the point of this? I am probably missing something obvious.. I think this was because getting good coverage data from anaconda without actually booting the installer iso wasn't possible. atodorov may be able to provide more

Re: Unretire txt2tags package?

On 14. 08. 19 20:03, Christoph Junghans wrote: Hi, txt2tags was recently retired due to FTBFS (https://bugzilla.redhat.com/show_bug.cgi?id=1676168) as it requires python2. Just a note: We haven't retired any package just because it requires python2 (not yet anyway). -- Miro Hrončok --

Unretire txt2tags package?

Hi, txt2tags was recently retired due to FTBFS (https://bugzilla.redhat.com/show_bug.cgi?id=1676168) as it requires python2. txt2tags is still needed for some of my packages, e.g. votca-csg to build manpages. There is an python3 port of the last release by rednotebook (see

Re: Let's revisit the FTBFS policy

On 14. 08. 19 19:22, Ben Cotton wrote: I want to publicly express my appreciation for Miro's efforts to enforce our policy and his willingness to take the hits from people being rightly upset at its flaws. I also appreciate that the community has done a good job of understanding that the policy

Re: Let's revisit the FTBFS policy

On Wed, Aug 14, 2019 at 1:31 PM Adam Williamson wrote: > > I actually think the consequences of the revival of the old policy have > been fine. We are throwing out tons of cruft. Occasionally we find > something very crufty yet important: this is a *good* outcome of the > process. It alerts us to

Re: [HEADS-UP]: Mercurial with Python3 on rawhide?

I just tested hg-5.1.0 with the latest git version of hg-evolve on python3 and at least some basic things seem to be working. One problem: hg *** failed to import extension hggit: No module named 'compat' That's with the latest pip version of hg-git (0.8.12). hg-git is a supported fedora

Re: Let's revisit the FTBFS policy

On Wed, 2019-08-14 at 13:22 -0400, Ben Cotton wrote: > I want to publicly express my appreciation for Miro's efforts to > enforce our policy and his willingness to take the hits from people > being rightly upset at its flaws. I also appreciate that the community > has done a good job of

Re: Let's revisit the FTBFS policy

I want to publicly express my appreciation for Miro's efforts to enforce our policy and his willingness to take the hits from people being rightly upset at its flaws. I also appreciate that the community has done a good job of understanding that the policy is the problem and not making it a

Re: Let's revisit the FTBFS policy

> "FW" == Florian Weimer writes: FW> Debian treats FTBFS bugs as release-critical. They either have to FW> be fixed, or the package gets removed from the release. However, FW> this is not an automated process. Of course, Debian works on a slightly different release schedule, so it's not

Re: Requesting F31 branches

I believe Mohan has corrected this in git, but hasn't cut a release yet. --  Gwyn Ciesla she/her/hers   in your fear, seek only peace  in your fear, seek only love -d. bowie Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On

Re: Requesting F31 branches

I think Gwyn needs to update fedscm-admin. On Wed, Aug 14, 2019, 17:52 Robert-André Mauchin wrote: > Hello, > > What does this error means when requesting F31 branches: > > > Invalid body, keys: sls missing > > https://pagure.io/releng/fedora-scm-requests/issue/15093 > > This is cryptic, can

Re: Let's revisit the FTBFS policy

> "MH" == Miro Hrončok writes: MH> If we stop here, the current "setting to ASSIGNED to stop this" MH> remains a problem. Let's think about why this is perceived as a problem. The maintainer has performed an affirmative act that shows they noticed. Can't we just accept that as some

Requesting F31 branches

Hello, What does this error means when requesting F31 branches: > Invalid body, keys: sls missing https://pagure.io/releng/fedora-scm-requests/issue/15093 This is cryptic, can anyone explain what is the issue? Best regards, Robert-André ___ devel

Re: Let's revisit the FTBFS policy

On Wed, 2019-08-14 at 14:55 +0200, Vít Ondruch wrote: > Dne 14. 08. 19 v 14:23 Miro Hrončok napsal(a): > > Hello. > > > > Recently, a couple hundred packages were retired from rawhide (Fedora > > 31 at that time) based on the Fedora Failed to Build From Source > > Policy [1]. From various

Announcing EPEL-8.0 Release

The EPEL Steering Committee is pleased to announce that the initial EPEL-8 is ready for release. We would like to thank everyone in the community for helping us get the initial set of builds out to mirrors and to consumers worldwide. Special thanks go to Patrick Uiterwijk, Jeroen van Meeuwen,

Announcing EPEL-8.0 Release

The EPEL Steering Committee is pleased to announce that the initial EPEL-8 is ready for release. We would like to thank everyone in the community for helping us get the initial set of builds out to mirrors and to consumers worldwide. Special thanks go to Patrick Uiterwijk, Jeroen van Meeuwen,

[EPEL-devel] Announcing EPEL-8.0 Release

The EPEL Steering Committee is pleased to announce that the initial EPEL-8 is ready for release. We would like to thank everyone in the community for helping us get the initial set of builds out to mirrors and to consumers worldwide. Special thanks go to Patrick Uiterwijk, Jeroen van Meeuwen,

Re: Unretire linuxconsoletools package

Just FTR, the re-review was not necessary: https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package V. Dne 13. 08. 19 v 14:12 Vascom napsal(a): > Please approve review of linuxconsoletools package >

Re: Better interactivity in low-memory situations

(Oops, sorry, re-post because I messed up the threading.) I'm not a developer, nor do I pretend to understand the nuances of memory management. But I signed up for this list just to say "thanks" to all the devs and others that are finally discussing what I consider to be one of the biggest

Bugzilla branching emails

Hi everyone! It turns out that the Bugzilla branching script was not correctly suppressing email notifications, so you may have received "a few" messages as we branched rawhide bugs to F31 yesterday. This is fixed now, with help from Miro Hrončok. I apologize for the spam. -- Ben Cotton He /

[EPEL-devel] Re: EPEL 8 not finding buildroot overrides

On Wed, Aug 14, 2019 at 6:39 AM Troy Dawson wrote: > > On Wed, Aug 14, 2019 at 6:36 AM Stephen John Smoogen wrote: > > > > > > > > On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote: > >> > >> I have hdf5 (amongst others) in a buildroot override but when I tried to > >> build OpenImageIO I got

[EPEL-devel] Re: EPEL 8 not finding buildroot overrides

On Wed, Aug 14, 2019 at 6:36 AM Stephen John Smoogen wrote: > > > > On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote: >> >> I have hdf5 (amongst others) in a buildroot override but when I tried to >> build OpenImageIO I got the following errors in root.log: >> Where is the link to that

re: Better interactivity in low-memory situations

I'm not a developer, nor do I pretend to understand the nuances of memory management. But I signed up for this list just to say "thanks" to all the devs and others that are finally discussing what I consider to be one of the biggest problems with Linux on the desktop. My experience with

Re: Let's revisit the FTBFS policy

Dne 14. 08. 19 v 15:20 Miro Hrončok napsal(a): > On 14. 08. 19 14:55, Vít Ondruch wrote: >> I think it would be probably enough to stop here. Orphaned packages gets >> garbage collected ATM. The step 4 was a bit unexpected for packages with >> bugs in ASSIGNED state especially. > > If we stop

[EPEL-devel] Re: EPEL 8 not finding buildroot overrides

On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote: > I have hdf5 (amongst others) in a buildroot override but when I tried to > build OpenImageIO I got the following errors in root.log: > > DEBUG util.py:585: BUILDSTDERR: No matching package to install: > 'hdf5-devel' > > I'm I missing

Re: Why retire Python 2 packages and games that still work to end user ?

On 14/08/2019 15:01, Kevin Kofler wrote: > David Sommerseth wrote: >> Like it or not, Python 2 is going to die: >> >> >> Python 2 will not be maintained by upstream after January 1, 2020. Python >> 2 will go EOL during the lifetime of Fedora 31. > > So

Re: Let's revisit the FTBFS policy

On 14. 08. 19 14:55, Vít Ondruch wrote: I think it would be probably enough to stop here. Orphaned packages gets garbage collected ATM. The step 4 was a bit unexpected for packages with bugs in ASSIGNED state especially. If we stop here, the current "setting to ASSIGNED to stop this" remains a

Re: Orphaning 13 packages

Dne 14. 08. 19 v 12:39 Jan Kaluza napsal(a): > Hi, > > I'm orphaning packages which I used to maintain in my spare time. I do > not have enough time and motivation these days/months/years to > continue maintaining them: > > - adevs - https://src.fedoraproject.org/rpms/adevs > - dfish -

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

Florian Weimer wrote: > You dropped too much context here. Drivers which are rottenware (Panu's > term) are exactly in this category. We can only hope that upstreams > remove them, based on feedback from the larger community. The question is, how do you know whether the unmaintained driver last

Re: Why retire Python 2 packages and games that still work to end user ?

David Sommerseth wrote: > Like it or not, Python 2 is going to die: > > > Python 2 will not be maintained by upstream after January 1, 2020. Python > 2 will go EOL during the lifetime of Fedora 31. So what? Qt 3 had its last release (3.3.8b) in 2008

Re: Let's revisit the FTBFS policy

Dne 14. 08. 19 v 14:23 Miro Hrončok napsal(a): > Hello. > > Recently, a couple hundred packages were retired from rawhide (Fedora > 31 at that time) based on the Fedora Failed to Build From Source > Policy [1]. From various reactions over several threads it seems this > policy is not ideal. This

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

On Wed, Aug 14, 2019 at 3:31 PM Kevin Kofler wrote: > Aleksandar Kurtakov wrote: > > The real question which every packager should ask himself is: Do I have > > the capacity (time, knowledge, hardware, etc.) to solve problems on > > non-supported architecture by upstream? > > And if the answer

Re: Why retire Python 2 packages and games that still work to end user ?

Peter Robinson wrote: > So why do package maintainers have to do a whole lot of extra work to > keep a package that has already been approved in the distro. There's a > lot of work going into various stacks upstream for python3 work but in > a lot of cases the time available is split and now we're

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

* Kevin Kofler: > Florian Weimer wrote: >> I think that's only a problem if reported bugs don't get fixed. If such >> bugs are fixed, shipping everything that builds aligns well with >> building a community-tested distribution. >> >> Exceptions could be software that leads to purchases of some

[Bug 1741084] Upgrade perl-MongoDB to 2.2.0

https://bugzilla.redhat.com/show_bug.cgi?id=1741084 Petr Pisar changed: What|Removed |Added Status|MODIFIED|CLOSED Fixed In

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

Florian Weimer wrote: > I think that's only a problem if reported bugs don't get fixed. If such > bugs are fixed, shipping everything that builds aligns well with > building a community-tested distribution. > > Exceptions could be software that leads to purchases of some kind, based > on an

[Bug 1741084] Upgrade perl-MongoDB to 2.2.0

https://bugzilla.redhat.com/show_bug.cgi?id=1741084 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version|

Re: Let's revisit the FTBFS policy

* Miro Hrončok: > Recently, a couple hundred packages were retired from rawhide (Fedora > 31 at that time) based on the Fedora Failed to Build From Source > Policy [1]. From various reactions over several threads it seems this > policy is not ideal. This is an attempt to collect feedback and make

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

Aleksandar Kurtakov wrote: > The real question which every packager should ask himself is: Do I have > the capacity (time, knowledge, hardware, etc.) to solve problems on > non-supported architecture by upstream? > And if the answer is no - it is probably better to drop the arch instead > of

Re: Where can I remove myself from bug emails for packages I am not a maintainer anymore

On 8/14/19 4:08 AM, Petr Pisar wrote: On 2019-08-13, Robert Marcano wrote: I am not maintaining eclipse-subclipse from a long time ago, I am not listed as a member at https://src.fedoraproject.org/rpms/eclipse-subclipse but I still get FTBFS bugzilla emails. That's because synchronization

Let's revisit the FTBFS policy

Hello. Recently, a couple hundred packages were retired from rawhide (Fedora 31 at that time) based on the Fedora Failed to Build From Source Policy [1]. From various reactions over several threads it seems this policy is not ideal. This is an attempt to collect feedback and make the policy

[Bug 1731802] Upgrade perl-Carp-Assert-More to 1.20

https://bugzilla.redhat.com/show_bug.cgi?id=1731802 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version|

Notes from the "Fedora Loves Python" session at Flock

Hello! I ended up running the "Fedora Loves Python" session at Flock. As the abstract says: > It seems that the Fedora ❤ Python initiative has recently become more > stagnated. It's not that Fedora no longer loves Python, but the > relationship has become rather boring, after several years >

Re: [HEADS-UP] gradle will go away

On Wed, Aug 14, 2019, 13:48 Mat Booth wrote: > > > On Fri, 9 Aug 2019 at 14:24, Fabio Valentini wrote: > > > > Hi everybody! > > > > After some discussions, we (the Stewardship SIG) have decided that we > > cannot continue to maintain gradle in fedora. > > > > - the current version packaged in

Re: efivar and mokutil long standing FTBFS

On 14. 08. 19 12:54, Peter Robinson wrote: Well you can't currently see the forest for the trees and this bullshit, for the first time in 15 years in making me think about quitting the Fedora project, and I spoke with many at Flock are seriously stressed about it and sick of it. I will be

Re: [HEADS-UP] gradle will go away

On Fri, 9 Aug 2019 at 14:24, Fabio Valentini wrote: > > Hi everybody! > > After some discussions, we (the Stewardship SIG) have decided that we > cannot continue to maintain gradle in fedora. > > - the current version packaged in fedora is outdated (4.4.1, from Dec. > 2017, vs. 5.5.1 from July

Re: Why retire Python 2 packages and games that still work to end user ?

On 11/08/2019 01:45, Kevin Kofler wrote: >> My opinion at least postpone this decision one or two releases to >> Fedors 33/34 , many things still just work with python 2 . > > I second that wholeheartedly. Like it or not, Python 2 is going to die:

Re: Why retire Python 2 packages and games that still work to end user ?

On Sun, Aug 11, 2019 at 9:33 AM Miro Hrončok wrote: > > On 11. 08. 19 3:45, Kevin Kofler wrote: > > Nico Kadel-Garcia wrote: > >> Maintaining python 2 requires maintaining a*lot* of infrastructure. > > What kind of infrastructure do you need to maintain a package that is (will > > be) no longer

[Bug 1694444] Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.32), passed through in regex; marked by <-- HERE in m/ ( { <-- HERE } (?: / \* )? | \* ) / at (eval 97) line

https://bugzilla.redhat.com/show_bug.cgi?id=169 Paul Howarth changed: What|Removed |Added CC||p...@city-fan.org --- Comment #3 from

[Bug 1729976] Add perl-LWP-Protocol-connect to EPEL-7

https://bugzilla.redhat.com/show_bug.cgi?id=1729976 Paul Howarth changed: What|Removed |Added Keywords||FutureFeature CC|

Re: efivar and mokutil long standing FTBFS

> On 13. 08. 19 19:43, Peter Robinson wrote: > > Firstly they're just FTBFS in F-30 This isn't exactly long > > standing, if it was F-26 like some that were retired I could > > completely understand that statement but F-30 is pushing the rhetoric > > a bit here. > > It has been half a year

[Bug 1731805] Upgrade perl-Clone to 0.42

https://bugzilla.redhat.com/show_bug.cgi?id=1731805 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED CC|

Orphaning 13 packages

Hi, I'm orphaning packages which I used to maintain in my spare time. I do not have enough time and motivation these days/months/years to continue maintaining them: - adevs - https://src.fedoraproject.org/rpms/adevs - dfish - https://src.fedoraproject.org/rpms/dfish - gob2 -

[Bug 1741079] Upgrade perl-DBD-Pg to 3.9.0

https://bugzilla.redhat.com/show_bug.cgi?id=1741079 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version|

Some Java packages in need of new permanent maintainer(s)

Hello packagers, The Stewardship SIG is currently providing only bare-minimum maintenance for some Java packages, and none of our packages depend on them anymore. So, we're looking for someone to take better care of them, preferably someone who actively uses these packages or maintains a package

[Bug 1741078] Upgrade perl-BSON to 1.12.1

https://bugzilla.redhat.com/show_bug.cgi?id=1741078 Petr Pisar changed: What|Removed |Added Fixed In Version|perl-BSON-1.12.1-1.fc32 |perl-BSON-1.12.1-1.fc31 -- You are

[Bug 1741078] Upgrade perl-BSON to 1.12.1

https://bugzilla.redhat.com/show_bug.cgi?id=1741078 --- Comment #2 from Fedora Update System --- FEDORA-2019-b29dcd61b1 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b29dcd61b1 -- You are receiving this mail because: You are on the CC list

[Bug 1741078] Upgrade perl-BSON to 1.12.1

https://bugzilla.redhat.com/show_bug.cgi?id=1741078 --- Comment #3 from Fedora Update System --- FEDORA-2019-35720869ef has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-35720869ef -- You are receiving this mail because: You are on the CC list

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

On 8/14/19 12:28 PM, Florian Weimer wrote: * Panu Matilainen: Attitudes like that is why there's rottenware in the distro that last actually worked sometime around 2011, dutifully rebuilt on each mass-rebuild and even spec cleanups taking place but the software itself crashes on startup (or is

Some NodeJS packages in need of new permanent maintainer(s)

Hello packagers, The Stewardship SIG is currently providing only bare-minimum maintenance for some NodeJS packages, and none of our packages depend on them anymore. So, we're looking for someone to take better care of them, preferably someone who actively uses these packages or maintains a

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

* Panu Matilainen: > Attitudes like that is why there's rottenware in the distro that last > actually worked sometime around 2011, dutifully rebuilt on each > mass-rebuild and even spec cleanups taking place but the software > itself crashes on startup (or is otherwise entirely dysfunctional) >

[Bug 1741078] Upgrade perl-BSON to 1.12.1

https://bugzilla.redhat.com/show_bug.cgi?id=1741078 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version|

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

On 8/14/19 10:59 AM, Andreas Tunek wrote: On Tue, 13 Aug 2019, 23:33 Kevin Kofler, > wrote: Kaleb Keithley wrote: > Building it on 32-bit in the CI is only to ensure correctness of sprintf > format strings. It's a compile-only test. And

[Bug 1738385] Request mod_perl package for EPEL 8

https://bugzilla.redhat.com/show_bug.cgi?id=1738385 --- Comment #9 from yoshida.ryui...@bsearchtech.com --- The reason we used mod_perl was, simply because we did not want our 10K+ lines of perl codes (stateless API) compiled at each request. Now my prototype (full coverage) is running on

[Bug 1741086] New: Upgrade perl-Text-Autoformat to 1.75

https://bugzilla.redhat.com/show_bug.cgi?id=1741086 Bug ID: 1741086 Summary: Upgrade perl-Text-Autoformat to 1.75 Product: Fedora Version: rawhide Status: NEW Component: perl-Text-Autoformat Assignee: emman...@seyman.fr

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

On Wed, Aug 14, 2019 at 11:29 AM Miro Hrončok wrote: > On 14. 08. 19 8:55, Frantisek Zatloukal wrote: > > It depends on package maintainer. If upstream dropped 32-bit support, > I'd stop > > building it for that arch in Fedora. > > > > Why would package maintainer have to bear the burden of

[Bug 1741084] New: Upgrade perl-MongoDB to 2.2.0

https://bugzilla.redhat.com/show_bug.cgi?id=1741084 Bug ID: 1741084 Summary: Upgrade perl-MongoDB to 2.2.0 Product: Fedora Version: rawhide Status: NEW Component: perl-MongoDB Assignee: ppi...@redhat.com

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

On 14. 08. 19 8:55, Frantisek Zatloukal wrote: It depends on package maintainer. If upstream dropped 32-bit support, I'd stop building it for that arch in Fedora. Why would package maintainer have to bear the burden of potential breakage if upstream doesn't test it? If neither of my

[Bug 1741079] New: Upgrade perl-DBD-Pg to 3.9.0

https://bugzilla.redhat.com/show_bug.cgi?id=1741079 Bug ID: 1741079 Summary: Upgrade perl-DBD-Pg to 3.9.0 Product: Fedora Version: rawhide Status: NEW Component: perl-DBD-Pg Assignee: jples...@redhat.com

[Bug 1741078] New: Upgrade perl-BSON to 1.12.1

https://bugzilla.redhat.com/show_bug.cgi?id=1741078 Bug ID: 1741078 Summary: Upgrade perl-BSON to 1.12.1 Product: Fedora Version: rawhide Status: NEW Component: perl-BSON Assignee: ppi...@redhat.com Reporter:

Re: Where can I remove myself from bug emails for packages I am not a maintainer anymore

On 2019-08-13, Robert Marcano wrote: > I am not maintaining eclipse-subclipse from a long time ago, I am not > listed as a member at > https://src.fedoraproject.org/rpms/eclipse-subclipse but I still get > FTBFS bugzilla emails. > That's because synchronization from dist-git Pagure to Bugzilla

Re: Fedora 32 System-Wide Change: glusterfs dropping 32-bit arches

On Tue, 13 Aug 2019, 23:33 Kevin Kofler, wrote: > Kaleb Keithley wrote: > > Building it on 32-bit in the CI is only to ensure correctness of sprintf > > format strings. It's a compile-only test. > > And that is sufficient. As long as it compiles, you can package it. > Whether > upstream

  1   2   >