Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

2017-06-14 Thread Pavel Raiskup
On Wednesday, June 14, 2017 11:38:38 PM CEST Till Maas wrote: > On Wed, Jun 14, 2017 at 04:20:25PM +0200, Pavel Raiskup wrote: > > On Tuesday, June 13, 2017 2:26:33 PM CEST Petr Pisar wrote: > > > On 2017-06-13, Pavel Raiskup wrote: > > > >> vim-syntastic praiskup

Announce: Fedora Layered Image Release

2017-06-14 Thread Adam Miller
Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release[2]. At this time the following Container Images are available in the Fedora Registry. Base Images:

Schedule for Thursday's FPC Meeting (2017-06-15 16:00 UTC)

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

Re: F26 Mesa update

2017-06-14 Thread Michael Cronenworth
On 06/14/2017 04:06 AM, Peter Robinson wrote: the buildroot issues are now fixed, but I built mesa before the llvm-4 were stable in F-26 (about the time stuff unfroze) but I need to pull a couple of patches in for RPi stability, I'll do that today and push an update. Thanks. I've created a bui

Fedora 26-20170614.n.1 compose check report

2017-06-14 Thread Fedora compose checker
Missing expected images: Workstation live i386 Kde live x86_64 Workstation live x86_64 Kde live i386 Failed openQA tests: 5/102 (x86_64), 2/22 (i386), 1/2 (arm) New failures (same test did not fail in 26-20170611.n.1): ID: 108234 Test: i386 Everything-boot-iso install_default URL: https://

Re: Package suggestions

2017-06-14 Thread Adam Williamson
On Thu, 2017-06-15 at 01:22 +0200, rugk wrote: > Hi, > I've been looking into how to suggest packages for inclusion in Fedora > for some time. See > https://ask.fedoraproject.org/en/question/106042/where-do-i-request-new-packages-to-be-added-to-the-fedora-repos/. > > Finally I'm giving a list of

Package suggestions

2017-06-14 Thread rugk
Hi, I've been looking into how to suggest packages for inclusion in Fedora for some time. See https://ask.fedoraproject.org/en/question/106042/where-do-i-request-new-packages-to-be-added-to-the-fedora-repos/. Finally I'm giving a list of some very useful pieces of software I am partially miss

Flock hotel discount code is available + Last-minute CFP reminder!

2017-06-14 Thread Máirín Duffy
Hi everyone, Our hotel discount code for Flock went live yesterday. It is... *drumroll* "FLOCK". Here are the rates: - A $139/night* rate per double, queen, or king room is available from August 27 to August 31. You will need to use the "Group Attendee" code "FLOCK" on the hotel reservatio

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

2017-06-14 Thread Till Maas
On Wed, Jun 14, 2017 at 04:20:25PM +0200, Pavel Raiskup wrote: > On Tuesday, June 13, 2017 2:26:33 PM CEST Petr Pisar wrote: > > On 2017-06-13, Pavel Raiskup wrote: > > >> vim-syntastic praiskup 38 > > >> weeks ago > > > > > > Please don't remove this set o

Re: Migrating sub-package to a different package: How to resolve file conflicts

2017-06-14 Thread Matthew Miller
On Wed, Jun 14, 2017 at 02:58:32PM -0500, Jason L Tibbitts III wrote: > Sure. It seems a lot of people miss this, though I tried to announce it > loudly back when it changed (in August). I've been trying to cut down > on the bureaucracy, and a package that needs to add a > parallel-installable ve

Re: Migrating sub-package to a different package: How to resolve file conflicts

2017-06-14 Thread Jason L Tibbitts III
> "MM" == Matthew Miller writes: MM> Thanks for the correction! Sure. It seems a lot of people miss this, though I tried to announce it loudly back when it changed (in August). I've been trying to cut down on the bureaucracy, and a package that needs to add a parallel-installable version i

Re: Migrating sub-package to a different package: How to resolve file conflicts

2017-06-14 Thread Matthew Miller
On Wed, Jun 14, 2017 at 02:05:38PM -0500, Jason L Tibbitts III wrote: > MM> All other things aside, this is pragmatically easier, because > MM> creating a new package4 or package5 triggers a new package review. > That's not actually the case, though: > https://fedoraproject.org/wiki/Package_Review_

Re: Migrating sub-package to a different package: How to resolve file conflicts

2017-06-14 Thread Jason L Tibbitts III
> "MM" == Matthew Miller writes: MM> All other things aside, this is pragmatically easier, because MM> creating a new package4 or package5 triggers a new package review. That's not actually the case, though: https://fedoraproject.org/wiki/Package_Review_Process "Note that some new packages

Re: F27 Self Contained Change: Making sudo pip Safe (Again)

2017-06-14 Thread Michal Cyprian
There are plenty of bugs [0] reported by users, who break their systems using sudo pip and new bugs appear very often. For example the bug [1] was opened a week ago. The biggest issue is that in the current state it is not easy or even possible to recover from such situations. This issue is well

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Adam Williamson
On Wed, 2017-06-14 at 16:43 +0100, Peter Robinson wrote: > > Yes, I'm well aware of the plans but it doesn't help us now. There was > over 3500 package updates in the compose, it shows how quickly we got > behind. FWIW I really see this as a resource/priority problem, not a process problem. We ju

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Martin Kolman
On Wed, 2017-06-14 at 14:58 +0100, Daniel P. Berrange wrote: > On Tue, Jun 13, 2017 at 07:11:21AM -0600, Kevin Fenzi wrote: > > Greetings. > > > > Some folks may have noticed that there have been no completed > > rawhide > > composes in a while (13 days as of today). > > > > This has been due to

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Kevin Fenzi
On 06/14/2017 10:00 AM, Jonathan Dieter wrote: > On Wed, 2017-06-14 at 09:36 -0600, Kevin Fenzi wrote: >> * Composes are really slow (likely related to storage slowness), if they >> were faster or could fail faster we could untag/fix/iterate more. Right >> now we are lucky to get 2 chances a day. >

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Kevin Fenzi
On 06/14/2017 04:16 AM, Martin Kolman wrote: > I agree with that - for example the Anaconda installer CI broke due to > a rawhide package change in the last "working" compose. There is a > fixed package available and built in Koji, but it's not reaching the > Rawhide repos due to the broken compos

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Jonathan Dieter
On Wed, 2017-06-14 at 09:36 -0600, Kevin Fenzi wrote: > * Composes are really slow (likely related to storage slowness), if they > were faster or could fail faster we could untag/fix/iterate more. Right > now we are lucky to get 2 chances a day. When you're mentioning storage slowness, are we talk

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Peter Robinson
On Wed, Jun 14, 2017 at 4:36 PM, Kevin Fenzi wrote: > On 06/13/2017 03:47 PM, Peter Robinson wrote: >> >> For actual artifacts such as cloud/disk/installer images I agree but >> at least pushing out individual packages so people can do "dnf >> upgrade" picks up issues such as dependency issues tha

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Kevin Fenzi
On 06/13/2017 03:47 PM, Peter Robinson wrote: > > For actual artifacts such as cloud/disk/installer images I agree but > at least pushing out individual packages so people can do "dnf > upgrade" picks up issues such as dependency issues that also kill the > compose and allows people to still test e

Re: Non-responsive maintainer process for caillon, and retiring xchat

2017-06-14 Thread Gwyn Ciesla
I'd be interested in gnuchess and xboard, should they be orphaned. I've been doing a lot with gnuchess in later years. On Wed, Jun 14, 2017 at 10:19 AM, Debarshi Ray wrote: > Hello everybody, > > I would like to initiate the non-responsive maintainer process [1] for > Christopher Aillon [2]. A

Non-responsive maintainer process for caillon, and retiring xchat

2017-06-14 Thread Debarshi Ray
Hello everybody, I would like to initiate the non-responsive maintainer process [1] for Christopher Aillon [2]. A long time ago, he used to be part of the Fedora and Red Hat desktop teams. He is no longer around. He left software development and was last seen living off the grid in Hawaii [3]. The

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

2017-06-14 Thread Pavel Raiskup
On Tuesday, June 13, 2017 2:26:33 PM CEST Petr Pisar wrote: > On 2017-06-13, Pavel Raiskup wrote: > >> vim-syntastic praiskup 38 > >> weeks ago > > > > Please don't remove this set of vim-syntastic* packages, there's > > nothing to do about this. Once we h

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Daniel P. Berrange
On Tue, Jun 13, 2017 at 07:11:21AM -0600, Kevin Fenzi wrote: > Greetings. > > Some folks may have noticed that there have been no completed rawhide > composes in a while (13 days as of today). > > This has been due to a variety of bugs and issues, along with pungi now > failing composes that don'

Re: Migrating sub-package to a different package: How to resolve file conflicts

2017-06-14 Thread Matthew Miller
On Wed, Jun 14, 2017 at 12:22:53PM +0200, Vít Ondruch wrote: > IMO, the latest package should be always non-versioned one and versioned > should be only the compat packages. > E.g. the llvm package is always the latest, shipping llvm 4.0 ATM and > llvm3.9 should be compat package, shipping the prev

Re: dnf bodhi plugin

2017-06-14 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jun 14, 2017 at 04:08:55AM +0100, Sérgio Basto wrote: > On Fri, 2017-05-19 at 16:04 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Fri, May 19, 2017 at 11:48:37AM -0400, Matthew Miller wrote: > > > On Fri, May 19, 2017 at 11:44:57AM -0400, Matthew Miller wrote: > > > > See https://bugzill

Fedora Rawhide-20170613.n.1 compose check report

2017-06-14 Thread Fedora compose checker
Missing expected images: Workstation live i386 Kde live x86_64 Server boot i386 Workstation live x86_64 Kde live i386 Failed openQA tests: 78/102 (x86_64), 18/18 (i386), 1/2 (arm) New failures (same test did not fail in Rawhide-20170531.n.1): ID: 107819 Test: x86_64 Server-boot-iso install

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

2017-06-14 Thread Michael Schwendt
On Mon, 12 Jun 2017 22:38:11 + (UTC), till fedoraproject org wrote: > eflspot, dchen, sereinit 114 weeks ago > audacious-plugins (maintained by: mschwendt, atkac, danfruehauf) > audacious-plugins-jack-3.8.2-2.fc26.i686 requires libjack

Re: Migrating sub-package to a different package: How to resolve file conflicts

2017-06-14 Thread Vít Ondruch
IMO, the latest package should be always non-versioned one and versioned should be only the compat packages. E.g. the llvm package is always the latest, shipping llvm 4.0 ATM and llvm3.9 should be compat package, shipping the previous version. Once new version is released, lets say llvm 5.0, the n

Re: Rawhide: where for art thou? (why no rawhide composes recently)

2017-06-14 Thread Martin Kolman
On Tue, 2017-06-13 at 22:47 +0100, Peter Robinson wrote: > > > > > Greetings. > > > > > > > > > > Some folks may have noticed that there have been no completed > > > > > rawhide > > > > > composes in a while (13 days as of today). > > > > > > > > > > This has been due to a variety of bugs and iss

Re: F26 Mesa update

2017-06-14 Thread Peter Robinson
On Wed, Jun 14, 2017 at 1:32 AM, Michael Cronenworth wrote: > Hello, > > Is there a reason for delaying the update for mesa-17.1.2 to F26? > > We're getting buildroot failures for some F26 packages that depend on mesa > (llvm was updated). The mesa update and the buildroot failures were unrelated

Re: F26 Mesa update

2017-06-14 Thread Kalev Lember
On 06/14/2017 05:05 AM, Orion Poplawski wrote: > On 06/13/2017 06:32 PM, Michael Cronenworth wrote: >> Hello, >> >> Is there a reason for delaying the update for mesa-17.1.2 to F26? >> >> We're getting buildroot failures for some F26 packages that depend on >> mesa (llvm was updated). >> >> Thanks,