Re: Xen / EC2 release criteria proposal

On 8/10/19 2:56 AM, Adam Williamson wrote: Hey folks! I'm starting a new thread for this to trim the recipient list a bit and include devel@ and coreos@. The Story So Far: there is a Fedora release criterion which requires Fedora to boot on Xen: "The release must boot successfully as Xen DomU w

Re: Xen / EC2 release criteria proposal

On Sat, 2019-08-10 at 00:53 -0400, Nico Kadel-Garcia wrote: > On Fri, Aug 9, 2019 at 8:57 PM Adam Williamson > wrote: > > Hey folks! I'm starting a new thread for this to trim the recipient > > list a bit and include devel@ and coreos@. > > > > The Story So Far: there is a Fedora release criterio

Re: Xen / EC2 release criteria proposal

On Fri, Aug 9, 2019 at 8:57 PM Adam Williamson wrote: > > Hey folks! I'm starting a new thread for this to trim the recipient > list a bit and include devel@ and coreos@. > > The Story So Far: there is a Fedora release criterion which requires > Fedora to boot on Xen: > > "The release must boot su

Re: Better interactivity in low-memory situations

Just in case anyone wants to try to reproduce this particular example: 1. Grab latest stable from here and untar it https://webkitgtk.org/releases/ 2. Run this included script, which is dnf aware, to install dependencies ./Tools/gtk/install-dependencies 3. Additional packages I had to install to g

[Test-Announce] Proposal to CANCEL: 2019-08-12 Fedora QA and blocker review meetings

Hi folks! I'm proposing we cancel the QA and blocker review meetings on Monday. We do actually have stuff for both meetings, but Flock ends Sunday so I'm expecting a lot of people will be busy traveling/recovering on Monday, so it seems best to wait until next week. If you're aware of anything imp

Xen / EC2 release criteria proposal

Hey folks! I'm starting a new thread for this to trim the recipient list a bit and include devel@ and coreos@. The Story So Far: there is a Fedora release criterion which requires Fedora to boot on Xen: "The release must boot successfully as Xen DomU with releases providing a functional, supporte

Re: Does anybody care about gettext?

9.08.2019 22:10 Jerry James wrote: > On Fri, Aug 9, 2019 at 2:12 AM Alexander Ploumistos > wrote: > > All the patches we carried were merged back in the latest upstream > > version (0.20.1), but when I took a stab at it, I got a lot of errors > > about the variable types and I did not know how to

Re: Does anybody care about gettext?

On Sat, Aug 10, 2019 at 1:42 AM Jerry James wrote: > On Fri, Aug 9, 2019 at 2:12 AM Alexander Ploumistos > wrote: > > All the patches we carried were merged back in the latest upstream > > version (0.20.1), but when I took a stab at it, I got a lot of errors > > about the variable types and I di

Re: Does anybody care about gettext?

On Fri, Aug 9, 2019 at 11:13 PM Jerry James wrote: > > On Fri, Aug 9, 2019 at 2:12 AM Alexander Ploumistos > wrote: > > All the patches we carried were merged back in the latest upstream > > version (0.20.1), but when I took a stab at it, I got a lot of errors > > about the variable types and I d

Re: Better interactivity in low-memory situations

Hi, Chris Murphy writes: > Certain workloads, such as building webkitGTK from source, results in > heavy swap usage eventually leading to the system becoming totally > unresponsive. Look into switching from disk based swap, to swap on a > ZRAM device. It sounds like the same issue that has bee

Re: Disappearing mouse pointer

On Fri, Aug 9, 2019 at 2:07 PM Jerry James wrote: > > On Thu, Aug 8, 2019 at 2:08 PM Antonio M wrote: > > confirmed that running on 5.1.20-300 this issue is not present > > Same here. It does seem to be the 5.2 kernel that triggered this > behavior. I also managed to reproduce it once today wit

Better interactivity in low-memory situations

This subject matches a Fedora Workstation Working Group issue of the same name [1], and this post is intended to be an independent summary of the findings so far, and call for additional testing and discussion, in particular subject matter experts. Problem and thesis statement: Certain workloads,

Re: Does anybody care about gettext?

On Fri, Aug 9, 2019 at 2:12 AM Alexander Ploumistos wrote: > All the patches we carried were merged back in the latest upstream > version (0.20.1), but when I took a stab at it, I got a lot of errors > about the variable types and I did not know how to proceed. Alexander, try the attached spec fi

Re: Disappearing mouse pointer

On Thu, Aug 8, 2019 at 2:08 PM Antonio M wrote: > confirmed that running on 5.1.20-300 this issue is not present Same here. It does seem to be the 5.2 kernel that triggered this behavior. I also managed to reproduce it once today without virt-manager running, so maybe VMs have nothing to do wit

Re: [Bug 1675390] mingw-wine-gecko: FTBFS in Fedora rawhide/f30

On 09. 08. 19 21:10, Michael Cronenworth wrote: On 8/9/19 11:02 AM, Miro Hrončok wrote: The FTBFS bug was set to ASSIGNED yet your script retired it. Correct. It was still failing to build. I misinterpreted the "retire if still failing to build". This is new and unexpected. It is not that

Re: [Bug 1675390] mingw-wine-gecko: FTBFS in Fedora rawhide/f30

On 8/9/19 11:02 AM, Miro Hrončok wrote: The FTBFS bug was set to ASSIGNED yet your script retired it. Correct. It was still failing to build. I misinterpreted the "retire if still failing to build". This is new and unexpected. It is not reasonable to place a hard timeline on a single person

Re: Does anybody care about gettext?

On Fri, 9 Aug 2019 at 14:08, Michael Cronenworth wrote: > On 8/9/19 8:50 AM, Miro Hrončok wrote: > > Because if we don't, people just gonna ignore FTBFS forever. > > > > Could we have known that gettext will be unretired right away anyway? > Probably > > yes, but nobody got time / energy / resour

Re: Does anybody care about gettext?

On Fri, 2019-08-09 at 13:07 -0500, Michael Cronenworth wrote: > On 8/9/19 8:50 AM, Miro Hrončok wrote: > > Because if we don't, people just gonna ignore FTBFS forever. > > > > Could we have known that gettext will be unretired right away anyway? > > Probably > > yes, but nobody got time / energy

Re: Does anybody care about gettext?

On 8/9/19 8:50 AM, Miro Hrončok wrote: Because if we don't, people just gonna ignore FTBFS forever. Could we have known that gettext will be unretired right away anyway? Probably yes, but nobody got time / energy / resources to do any kind of analysis of the FTBFS packages. Next time, I hope

Re: Dropping python2-rpm subpackage?

On 07. 08. 19 12:55, Panu Matilainen wrote: Oh, based on the quoting, I thought the "FTBFS, should have been retired yesterday" remarks in your initial reply covered all these too. Since that's not the case... Sorry for the confusion: $ repoquery --repo=koji{,-source} --whatrequires python2-r

Re: [Bug 1675390] mingw-wine-gecko: FTBFS in Fedora rawhide/f30

On 09. 08. 19 17:45, Michael Cronenworth wrote: On 8/8/19 7:45 PM, Miro Hrončok wrote: What's the bug? Why should have it not been retired exactly? It didn't build since Fedora 26. The retirement message states: Please fix mingw-wine-gecko at your earliest convenience and set the bug's st

Re: [Bug 1675390] mingw-wine-gecko: FTBFS in Fedora rawhide/f30

On 8/8/19 7:45 PM, Miro Hrončok wrote: What's the bug? Why should have it not been retired exactly? It didn't build since Fedora 26. The retirement message states: Please fix mingw-wine-gecko at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the

[HEADS-UP] dav1d and aom SONAME bump

Hello, Next week I will update dav1d to version 0.4.0 which includes a SONAME bump, and will do a GIT snapshot of aom, whose library is unstable. I will push these updates both on F31 and F30, so consumers of these libraries (ffmpeg, xine-lib, vlc) will need to rebuild their packages on both re

Package removal for FTBFS: Add automatic orphaning?

The current policy says: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ 7. A week before the mass branching, any packages which still have open FTBFS bugs from the previous release will be retired. I propose we add a point just before that that says:

Re: Does anybody care about gettext?

On Fri, Aug 9, 2019 at 5:06 PM Miro Hrončok wrote: > > On 09. 08. 19 16:29, Simo Sorce wrote: > > On Fri, 2019-08-09 at 15:50 +0200, Miro Hrončok wrote: > >> Next time, I hope that FTBFS bugs for critical component are actually > >> actively > >> solved sooner than the retirement happens. We can

Re: Does anybody care about gettext?

On 09. 08. 19 16:58, Paul Wouters wrote: On Fri, 9 Aug 2019, Daniel P. Berrangé wrote: We can't carry on postponing things indefinitely though - at some point we have to say enough, and expect a maintainer to actually do some maintaining. That is an argument to orphan, not an argument to remo

Re: Does anybody care about gettext?

On Fri, 2019-08-09 at 10:29 -0400, Simo Sorce wrote: > On Fri, 2019-08-09 at 15:50 +0200, Miro Hrončok wrote: > > Next time, I hope that FTBFS bugs for critical component are actually > > actively > > solved sooner than the retirement happens. We can try to be more aggressive > > with > > the r

Re: Does anybody care about gettext?

On Fri, 9 Aug 2019, Daniel P. Berrangé wrote: We can't carry on postponing things indefinitely though - at some point we have to say enough, and expect a maintainer to actually do some maintaining. That is an argument to orphan, not an argument to remove the package. Had gettext been orphaned,

Re: Does anybody care about gettext?

On 09. 08. 19 16:22, Martin Kolman wrote: On Fri, 2019-08-09 at 15:14 +0100, Daniel P. Berrangé wrote: On Fri, Aug 09, 2019 at 03:13:07PM +0200, Martin Kolman wrote: On Fri, 2019-08-09 at 14:00 +0100, Daniel P. Berrangé wrote: On Fri, Aug 09, 2019 at 02:28:55PM +0200, Jens-Ulrik Petersen wrote

Re: Does anybody care about gettext?

On 09. 08. 19 16:29, Simo Sorce wrote: On Fri, 2019-08-09 at 15:50 +0200, Miro Hrončok wrote: Next time, I hope that FTBFS bugs for critical component are actually actively solved sooner than the retirement happens. We can try to be more aggressive with the reminders, but I don't know if that he

Re: Does anybody care about gettext?

On Fri, 2019-08-09 at 15:50 +0200, Miro Hrončok wrote: > Next time, I hope that FTBFS bugs for critical component are actually > actively > solved sooner than the retirement happens. We can try to be more aggressive > with > the reminders, but I don't know if that helps, because even currently,

Re: Does anybody care about gettext?

On Fri, 2019-08-09 at 15:14 +0100, Daniel P. Berrangé wrote: > On Fri, Aug 09, 2019 at 03:13:07PM +0200, Martin Kolman wrote: > > On Fri, 2019-08-09 at 14:00 +0100, Daniel P. Berrangé wrote: > > > On Fri, Aug 09, 2019 at 02:28:55PM +0200, Jens-Ulrik Petersen wrote: > > > > On Fri, Aug 9, 2019 at 9:

Re: Does anybody care about gettext?

On Fri, Aug 09, 2019 at 03:13:07PM +0200, Martin Kolman wrote: > On Fri, 2019-08-09 at 14:00 +0100, Daniel P. Berrangé wrote: > > On Fri, Aug 09, 2019 at 02:28:55PM +0200, Jens-Ulrik Petersen wrote: > > > On Fri, Aug 9, 2019 at 9:27 AM Igor Gnatenko < > > > ignatenkobr...@fedoraproject.org> wrote:

Re: Does anybody care about gettext?

On 09. 08. 19 14:28, Jens-Ulrik Petersen wrote: On Fri, Aug 9, 2019 at 9:27 AM Igor Gnatenko > wrote: Well, it was retired because it did not built since F30 mass rebuild… I went ahead and built it with the testsuite disabled for now: I suppose any

[HEADS-UP] gradle will go away

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 2019) - it currently doesn't build itself (not even in bootstrap mode)

Re: Does anybody care about gettext?

On Fri, 2019-08-09 at 14:00 +0100, Daniel P. Berrangé wrote: > On Fri, Aug 09, 2019 at 02:28:55PM +0200, Jens-Ulrik Petersen wrote: > > On Fri, Aug 9, 2019 at 9:27 AM Igor Gnatenko < > > ignatenkobr...@fedoraproject.org> wrote: > > > > > Well, it was retired because it did not built since F30 mass

Re: HEADS UP: Source File Verification

On Thu, 2019-08-08 at 16:24 +0200, Björn Persson wrote: > Joe Orton wrote: > > If you don't enforce GPG verification at or before "fedpkg upload" there > > is no assurance that what hits the lookaside cache is trusted, so I > > agree - doing this at build time is a good example of not caring abou

Re: Does anybody care about gettext?

On Fri, Aug 09, 2019 at 02:28:55PM +0200, Jens-Ulrik Petersen wrote: > On Fri, Aug 9, 2019 at 9:27 AM Igor Gnatenko < > ignatenkobr...@fedoraproject.org> wrote: > > > Well, it was retired because it did not built since F30 mass rebuild… > > > > I went ahead and built it with the testsuite disable

Re: gettext retired, rawhide broken

On Fri, Aug 9, 2019 at 7:38 AM Fabio Valentini wrote: > Can somebody please unretire and fix gettext? It was just automatically > retired because it didn't build successfully since fedora 29. And now the > world is broken. > Thanks - I think it has been taken care of for now. Jens __

Re: Does anybody care about gettext?

On Fri, Aug 9, 2019 at 9:27 AM Igor Gnatenko < ignatenkobr...@fedoraproject.org> wrote: > Well, it was retired because it did not built since F30 mass rebuild… > I went ahead and built it with the testsuite disabled for now: I suppose any Proven Packager could also have done, but yeah normally it

Re: Does anybody care about gettext?

On 09. 08. 19 10:09, Alexander Ploumistos wrote: P.S.: Can anyone explain how the builds of other packages went back to normal, even though there was no successful gettext build? I've requested the package to be unretired and when that happened, I've retagged the latest build to f31-pending. T

Missing python-rpm-macros>3.30 on EPEL7 ppc64le

Hi all. 'python-devel-2.7.5-86.el7' requires 'python(2)-rpm-macros > 3-30' on EPEL7 ppc64le only? https://koji.fedoraproject.org/koji/getfile?taskID=36879492&volume=DEFAULT&name=root.log&offset=-4000 -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x6e03

Re: Does anybody care about gettext?

Maybe package the newer version 0.20.1 http://www.gnu.org/software/gettext/ ___ 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

Re: Does anybody care about gettext?

On Fri, Aug 9, 2019 at 1:40 PM Alexander Ploumistos < alex.ploumis...@gmail.com> wrote: > Hello, > > On Fri, Aug 9, 2019 at 11:03 AM Sundeep Anand wrote: > > most probably I’ll fix that by next week. > > All the patches we carried were merged back in the latest upstream > version (0.20.1), but wh

Re: Does anybody care about gettext?

Hello, On Fri, Aug 9, 2019 at 11:03 AM Sundeep Anand wrote: > most probably I’ll fix that by next week. All the patches we carried were merged back in the latest upstream version (0.20.1), but when I took a stab at it, I got a lot of errors about the variable types and I did not know how to proc

Re: Does anybody care about gettext?

Hi, most probably I’ll fix that by next week. thanks, sundeep > On 09-Aug-2019, at 9:26 AM, Igor Gnatenko > wrote: > > Well, it was retired because it did not built since F30 mass rebuild… > > * petersen (Jens Petersen) > * ueno (Daiki Ueno) > * praiskup (Pavel Raiskup) > * suanand (Sundeep

Re: Does anybody care about gettext?

> Well, it was retired because it did not built since F30 mass rebuild… > > 6 maintainers could not fix FTBFS for half a year? Anybody is > interested to maintain gettext? BTW I've just orphaned it, so hopefully somebody will take it and actually make it build. _

Does anybody care about gettext?

Well, it was retired because it did not built since F30 mass rebuild… * petersen (Jens Petersen) * ueno (Daiki Ueno) * praiskup (Pavel Raiskup) * suanand (Sundeep Anand) * nphilipp (Nils Philippsen) * jjanco (Jakub Janco) 6 maintainers could not fix FTBFS for half a year? Anybody is interested to