Failing f31 spins/labs/images

2019-10-05 Thread Kevin Fenzi
d. Do it now and you will save everyone time later. ;) Python-Classroom: `` [pungi.global.log](https://kojipkgs.fedoraproject.org/compose/branched/Fedora-31-20191005.n.0/compose/../logs/global/pungi.global.log) - [38066743](https://koji.fedoraproject.org/koji/taskinfo?taskID=38066743) ``` [LIVE

Re: New updates straight to obsolete after Epoch bump?!?

2019-10-05 Thread Kevin Fenzi
On Sat, Oct 05, 2019 at 01:35:03PM -0500, Richard Shaw wrote: > On Sat, Oct 5, 2019 at 1:17 PM Kevin Fenzi wrote: > > > On Thu, Oct 03, 2019 at 06:32:13PM -0500, Richard Shaw wrote: > > > Anyone have any ideas? I tried re-submitting them but they were obsoleted > > > by bodhi again. > > > > It lo

Vim :Gbrowse support for pagure

2019-10-05 Thread Jakub Kadlcik
Hello, I don't know how many of you are Vim users and what fraction of those use plugins. Anyway, there is a great, well-known plugin called vim-fugitive (by notorious Tim Pope), that provides a lot of cool features. My favorite one is probably `:Gbrowse` command, which opens the current file, lin

Re: New updates straight to obsolete after Epoch bump?!?

2019-10-05 Thread Richard Shaw
On Sat, Oct 5, 2019 at 1:17 PM Kevin Fenzi wrote: > On Thu, Oct 03, 2019 at 06:32:13PM -0500, Richard Shaw wrote: > > Anyone have any ideas? I tried re-submitting them but they were obsoleted > > by bodhi again. > > It looks like the newer pyside is now in > https://bodhi.fedoraproject.org/update

Re: Defining the future of the packager workflow in Fedora

2019-10-05 Thread Kevin Fenzi
On Sat, Oct 05, 2019 at 02:35:59AM +0200, Kevin Kofler wrote: > Vít Ondruch wrote: > > It depends how you maintain your packages. My guess is (and I am sorry > > if I am mistaken) that you don't follow the > > > > https://fedoraproject.org/wiki/Updates_Policy#Philosophy > > > > If you followed th

Re: New updates straight to obsolete after Epoch bump?!?

2019-10-05 Thread Kevin Fenzi
On Thu, Oct 03, 2019 at 06:32:13PM -0500, Richard Shaw wrote: > Anyone have any ideas? I tried re-submitting them but they were obsoleted > by bodhi again. It looks like the newer pyside is now in https://bodhi.fedoraproject.org/updates/FEDORA-2019-2a4f82aa58 perhaps try and get the author of that

Fedora rawhide compose report: 20191005.n.0 changes

2019-10-05 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20191004.n.1 NEW: Fedora-Rawhide-20191005.n.0 = SUMMARY = Added images:1 Dropped images: 2 Added packages: 1 Dropped packages:0 Upgraded packages: 99 Downgraded packages: 0 Size of added packages: 31.64 KiB Size of dropped packages:0 B

Fedora-Rawhide-20191005.n.0 compose check report

2019-10-05 Thread Fedora compose checker
No missing expected images. Compose FAILS proposed Rawhide gating check! 2 of 45 required tests failed, 6 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not be mapped to openQA tests: FAILED: compose.clo

[EPEL-devel] Re: FreeRDP version updates.

2019-10-05 Thread Darren Wise
Sounds like an amazing solution to me, I'll follow up on the link you've sent me along with the kodi link Stephen J Smoogen kindly offered me in order to reach a viable future solution. Thanks very much for getting back to me so soon and at the weekend on this matter. During the process I'm go

Re: Defining the future of the packager workflow in Fedora

2019-10-05 Thread Richard Shaw
On Wed, Oct 2, 2019 at 1:18 PM Ben Rosser wrote: > > 1. Creating new packages has become (more of) a pain since the > retirement of pkgdb2. I know I keep complaining about needing to > manually fetch Pagure API keys, but it is actually extremely annoying > when I go to request a repo and realize

Re: Defining the future of the packager workflow in Fedora

2019-10-05 Thread Kevin Kofler
Miro Hrončok wrote: > Your example is not valid. This is not a mass change, this was an > individual change presented to the package maintainers via a PR that was > not merged by me: > > https://src.fedoraproject.org/rpms/qt5-qtwebengine/pull-request/3 > > Had there been a "please, make it build

Re: Impact of dropping QEMU emulation on 32-bit hosts ? (~Fedora 33)

2019-10-05 Thread Stephen John Smoogen
On Fri, 4 Oct 2019 at 20:10, Kevin Kofler wrote: > > Stephen John Smoogen wrote: > > What do you mean by breaking breaking because you use that term like a > > sledge hammer for anything from a 'pixel off' bug to 'too old software > > is in repos', 'too young software is in repos' , 'software is n

Re: Defining the future of the packager workflow in Fedora

2019-10-05 Thread Miro Hrončok
On 05. 10. 19 2:16, Kevin Kofler wrote: Miro Hrončok wrote: It goes like this: - master and f31 are at the same commit "aa" - I push a change only possible in rawhide, commit "bb" to master (it includes release bump and changelog entry) - a commit relevant for both, "c

Fedora-31-20191005.n.0 compose check report

2019-10-05 Thread Fedora compose checker
No missing expected images. Failed openQA tests: 6/153 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-31-20191004.n.0): ID: 463524 Test: x86_64 Server-dvd-iso install_repository_hd_variation URL: https://openqa.fedoraproject.org/tests/463524 ID: 463563 Test: x86_64 KD

Fedora 31 compose report: 20191005.n.0 changes

2019-10-05 Thread Fedora Branched Report
OLD: Fedora-31-20191004.n.0 NEW: Fedora-31-20191005.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 12 Dropped packages:0 Upgraded packages: 167 Downgraded packages: 1 Size of added packages: 13.45 MiB Size of dropped packages:0 B Size of

Re: what to do without fedocal [was Re: CPE Team Weekly Update: 2019-10-04]

2019-10-05 Thread Aleksandra Fedorova
Let's start from the very beginning maybe. What are the use cases for the Fedora Calendar? * Group meetings These events need shared ownership, we submit them once and keep "forever". I think this is a good candidate for Git PR workflow used by OpenStack. * Test Days Test Days are always associ

Re: Defining the future of the packager workflow in Fedora

2019-10-05 Thread Kevin Kofler
Fabio Valentini wrote: > Additionally, if-guarding every non-backwards compatible change will > result in unmaintainable, brittle and broken .spec files pretty fast. > Nobody should be expected to work through if-else-endif spaghetti (and I'm > not even talking about automated tools here, which alm

Re: Modularity and the system-upgrade path

2019-10-05 Thread Kevin Kofler
Fabio Valentini wrote: > Another benefit of this would be that the "*-modular" repositories > could be disabled by default, which would eliminate a whole lot of > upgrade issues for "normal users". > Only people who *actually want* alternate versions would enable > modules (and *-modular repos?), a

Re: what to do without fedocal [was Re: CPE Team Weekly Update: 2019-10-04]

2019-10-05 Thread Aleksandra Fedorova
Hi, Matthew, On Fri, Oct 4, 2019 at 9:47 PM Matthew Miller wrote: > > On Fri, Oct 04, 2019 at 05:58:19PM +0100, Aoife Moloney wrote: > >Fedocal: If no maintainer is found by October 18th, it will be > >decommissioned. > > This is pretty huge, since we use this to keep IRC meeting channel

Re: Modularity and the system-upgrade path

2019-10-05 Thread Fabio Valentini
On Fri, Oct 4, 2019 at 9:32 PM Miro Hrončok wrote: > > On 04. 10. 19 16:57, Stephen Gallagher wrote: > > Right now, there are two conflicting requirements in Fedora Modularity > > that we need to resolve. > > > > 1. Once a user has selected a stream, updates should follow that > > stream and not i

Intent to retire libvtemm

2019-10-05 Thread Krzesimir Nowak
Hi, I'm the "upstream maintainer" of libvtemm. In quotes, because last change I have made to the project was 8 years ago. It depends on an orphaned package vte (which is based on gtk2). It's also a leaf package. I don't think it makes sense to even orphan it. I intend to retire the package within

Re: Defining the future of the packager workflow in Fedora

2019-10-05 Thread Fabio Valentini
On Sat, Oct 5, 2019, 02:17 Kevin Kofler wrote: > Miro Hrončok wrote: > > It goes like this: > > > > - master and f31 are at the same commit "aa" > > - I push a change only possible in rawhide, commit "bb" to master > > (it includes release bump and changelog entry) > > - a commi