Fedora Rawhide-20181212.n.1 compose check report

No missing expected images. Compose FAILS proposed Rawhide gating check! 1 of 47 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 30/131 (x86_64), 9/24 (i386), 1/2 (arm) New failures (same test not failed in

Fedora rawhide compose report: 20181212.n.1 changes

OLD: Fedora-Rawhide-20181211.n.0 NEW: Fedora-Rawhide-20181212.n.1 = SUMMARY = Added images:2 Dropped images: 1 Added packages: 4 Dropped packages:1 Upgraded packages: 122 Downgraded packages: 0 Size of added packages: 329.14 MiB Size of dropped packages

Re: Multilib inconsistencies between fedora/updates/updates-testing composes

On 12/12/2018 02:32 AM, Florian Weimer wrote: > We have seen reports that glibc-headers.i686 comes and goes from the > x86_64 updates compose. Previously, we have seen this only for the > updates-testing compose: > > This leads to a very bad update

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

On Wed, 12 Dec 2018 16:50:10 -0700 Chris Murphy wrote: > OK that worked for an nvme drive, but not for an internal SATA HDD. > > $ sudo lsmod | grep bfq > $ sudo cat /sys/block/sda/queue/scheduler > noop deadline [cfq] > $ sudo > insmod

[389-devel] 389 DS nightly 2018-12-13 - 90% PASS

https://fedorapeople.org/groups/389ds/ci/nightly/2018/12/13/report-389-ds-base-1.4.0.19-20181213git5ed5f87.fc29.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

[Test-Announce] Fedora 30 Rawhide 20181212.n.1 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 30 Rawhide 20181212.n.1. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

Re: Backwards incompatible changes planned for Bodhi 4.0.0

> Greetings fellow Fedorans! > > I am about to start working on a set of backwards incompatible changes > to Bodhi for its upcoming 4.0.0 release (Bodhi follows Semantic > Versioning[0]): > > https://github.com/fedora-infra/bodhi/projects/6 > > If the thought of backwards incompatible changes to

[EPEL-devel] Re: missing -devel packages in 8 beta

On Tue, 11 Dec 2018, Dave Love wrote: > Obviously I can do that and set up a repo for use with mock, but you > surely don't expect all package maintainers to do that. when it is testing a Beta in a new Major, I do not feel that is an unreasonable expectation There is also a .repo file which

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

OK that worked for an nvme drive, but not for an internal SATA HDD. $ sudo lsmod | grep bfq $ sudo cat /sys/block/sda/queue/scheduler noop deadline [cfq] $ sudo insmod /usr/lib/modules/4.19.8-300.fc29.x86_64/kernel/block/bfq.ko.xz $ sudo cat /sys/block/sda/queue/scheduler noop deadline [cfq] $

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

On Wed, Dec 12, 2018 at 4:31 PM stan wrote: > > Enabled deadline and cfq again, but still no bfq available. > > $ cat /sys/block/sda/queue/scheduler > noop deadline [cfq] Tried this and it showed up for me: [root@flap ~]# cat /sys/block/nvme0n1/queue/scheduler [none] mq-deadline [root@flap ~]#

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

On Wed, 12 Dec 2018 14:41:37 -0700 stan wrote: > On Wed, 12 Dec 2018 16:07:49 -0500 > Jeff Moyer wrote: > > Thanks for your insight. Doesn't look good for my use of BFQ. > > > Note that you can change the current I/O scheduler for any block > > device by echo-ing into

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

On Wed, Dec 12, 2018 at 2:07 PM Jeff Moyer wrote: > > Hi, > > Chris Murphy writes: > > > I used two boot params: scsi_mod.use_blk_mq=1 elevator=bfq. I don't > > think that's a good way for a distribution to set the default though. > > You shouldn't need the "scsi_mod.use_blk_mq=1" option. As of

Fedora 30 Self-Contained Change proposal: Deprecate Sonatype OSS Parent

https://fedoraproject.org/wiki/Changes/Deprecate_Sonatype_OSS_Parent == Summary == Mark Sonatype OSS Parent software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description == Upstream declares that the project is no

Fedora 30 System-Wide Change proposal: Remove Obsolete Scriptlets

https://fedoraproject.org/wiki/Changes/RemoveObsoleteScriptlets == Summary == Remove scriptlets which are not needed anymore (ldconfig, gtk-update-icon-cache, etc.). == Owner == * Name: [[User:ignatenkobrain|Igor Gnatenko]] * Email: ignatenkobr...@fedoraproject.org == Scope == * Proposal

Fedora 30 Self-Contained Change proposal: Deprecate Apache Maven 2.x

https://fedoraproject.org/wiki/Changes/Deprecate_Apache_Maven_2.x == Summary == Mark Apache Maven 2.x software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description == The last upstream release of Apache Maven 2.x was

Fedora 30 Self-Contained Change proposal: Deprecate Apache Jakarta ORO and Regexp

https://fedoraproject.org/wiki/Changes/Deprecate_Apache_Jakarta_ORO_and_Regexp == Summary == Mark Apache Jakarta ORO and Apache Jakarta Commons Regexp software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description ==

Fedora 30 Self-Contained Change proposal: Deprecate Apache Jakarta Commons HttpClient

https://fedoraproject.org/wiki/Changes/Deprecate_Apache_Jakarta_Commons_HttpClient == Summary == Mark Apache Jakarta Commons HttpClient software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description == Apache Jakarta

Fedora 30 System-Wide Change proposal: Remove Obsolete Scriptlets

https://fedoraproject.org/wiki/Changes/RemoveObsoleteScriptlets == Summary == Remove scriptlets which are not needed anymore (ldconfig, gtk-update-icon-cache, etc.). == Owner == * Name: [[User:ignatenkobrain|Igor Gnatenko]] * Email: ignatenkobr...@fedoraproject.org == Scope == * Proposal

Fedora 30 Self-Contained Change proposal: Deprecate Sonatype OSS Parent

https://fedoraproject.org/wiki/Changes/Deprecate_Sonatype_OSS_Parent == Summary == Mark Sonatype OSS Parent software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description == Upstream declares that the project is no

Fedora 30 Self-Contained Change proposal: Deprecate Apache Maven 2.x

https://fedoraproject.org/wiki/Changes/Deprecate_Apache_Maven_2.x == Summary == Mark Apache Maven 2.x software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description == The last upstream release of Apache Maven 2.x was

Fedora 30 Self-Contained Change proposal: Deprecate Apache Jakarta ORO and Regexp

https://fedoraproject.org/wiki/Changes/Deprecate_Apache_Jakarta_ORO_and_Regexp == Summary == Mark Apache Jakarta ORO and Apache Jakarta Commons Regexp software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description ==

Fedora 30 Self-Contained Change proposal: Deprecate Apache Avalon

https://fedoraproject.org/wiki/Changes/Deprecate_Apache_Avalon == Summary == Mark Apache Avalon software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description == Apache Avalon project was closed by upstream

Fedora 30 Self-Contained Change proposal: Deprecate Apache Jakarta Commons HttpClient

https://fedoraproject.org/wiki/Changes/Deprecate_Apache_Jakarta_Commons_HttpClient == Summary == Mark Apache Jakarta Commons HttpClient software packages as deprecated. == Owner == * Name: [[User:Mizdebsk|Mikolaj Izdebski]] * Email: mizde...@redhat.com == Detailed Description == Apache Jakarta

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

On Wed, 12 Dec 2018 16:07:49 -0500 Jeff Moyer wrote: Thanks for your insight. Doesn't look good for my use of BFQ. > Note that you can change the current I/O scheduler for any block > device by echo-ing into /sys/block//queue/scheduler. Cat-ing > that file will give you the list of available

Re: Self Introduction: J."MUFTI" Scheurich

On Mon, 10 Dec 2018 11:25:55 +0100, J. Scheurich wrote: > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Introduce_yourself > > | When a new package maintainer joins the Fedora Project, we request > that he/she introduces > | themselves on the Fedora devel >

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

Hi, Chris Murphy writes: > Really Readding devel@ this time... > > On Wed, Dec 12, 2018 at 11:08 AM stan wrote: >> >> On Tue, 11 Dec 2018 11:48:29 - >> "Alan Jenkins" wrote: >> >> > [3] BFQ: >> > http://algo.ing.unimo.it/people/paolo/disk_sched/description.php >> > >> > [4] >> >

Re: Which I/O scheduler is Fedora switching to in 4.21? mq-deadline or BFQ?

Really Readding devel@ this time... On Wed, Dec 12, 2018 at 11:08 AM stan wrote: > > On Tue, 11 Dec 2018 11:48:29 - > "Alan Jenkins" wrote: > > > [3] BFQ: > > http://algo.ing.unimo.it/people/paolo/disk_sched/description.php > > > > [4] > >

Re: fedora-rawhide-kernel-nodebug is not getting updates

On Thu, 2018-12-06 at 14:29 +, Richard W.M. Jones wrote: > On Mon, Nov 26, 2018 at 07:14:50AM -0600, Justin Forbes wrote: > > On Fri, Nov 23, 2018 at 7:47 AM Dan Horák wrote: > > > On Fri, 23 Nov 2018 14:28:46 +0100 > > > Igor Gnatenko wrote: > > > > > > > Does anybody know why? > > > > >

Re: fedora-rawhide-kernel-nodebug is not getting updates

On Thu, Dec 06, 2018 at 14:29:15 +, "Richard W.M. Jones" wrote: Anyway it seems like Rawhide isn't getting new nodebug kernels. - Latest nodebug kernel: kernel-4.20.0-0.rc1.git4.2.fc30.x86_64.rpm (https://dl.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/x86_64/) - Latest Rawhide

Re: How to avoid re-generating Pagure API keys all the time?

On 12/12/18 4:10 AM, Ben Rosser wrote: > On Tue, Dec 11, 2018 at 4:07 PM Till Maas wrote: >> >> Hi Ben, >> >> On Tue, Dec 11, 2018 at 11:42:51AM +0100, Ben Rosser wrote: >> >>> I don't know. I feel like we could do a lot to improve the experience >>> of packaging by investing time into fixing

Backwards incompatible changes planned for Bodhi 4.0.0

Greetings fellow Fedorans! I am about to start working on a set of backwards incompatible changes to Bodhi for its upcoming 4.0.0 release (Bodhi follows Semantic Versioning[0]): https://github.com/fedora-infra/bodhi/projects/6 If the thought of backwards incompatible changes to Bodhi raises one

Re: authselect: what to do with systemd and nss-mdns that modify nsswith.conf

On Mi, 12.12.18 10:10, Simo Sorce (s...@redhat.com) wrote: > Acceptance is also not a problem, the point is integrating when and > where it makes sense on Fedora. Well, systemd is not a Fedora-only project. It's in fact an excercise in unification across distros, and hence interfacing with upper

Re: authselect: what to do with systemd and nss-mdns that modify nsswith.conf

On Thu, 2018-12-06 at 17:49 +0100, Lennart Poettering wrote: > On Do, 06.12.18 11:25, Simo Sorce (s...@redhat.com) wrote: > > > > > Summary: I'd make things simple, and enable all four unconditionally > > > > and by default without any dynamic infrastructure, without postinst > > > > scripts or

Re: blender: Not linking against libGL

Ok, setting OpenGL_gl_PREFERENCE to LEGACY fixed it for now until blender updates their CMake config. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code

Re: blender: Not linking against libGL

On Wed, Dec 12, 2018 at 8:41 AM Rex Dieter wrote: > Richard Shaw wrote: > > > Answering part of my own question here using the rawhide test instance: > > > > $ pkg-config --libs glew > > -lGLEW -lGLU -lGL > > > > Minimal CMake test config: > > > > $ cmake . > > -- GLEW_LIBRARIES:

Re: blender: Not linking against libGL

Richard Shaw wrote: > Answering part of my own question here using the rawhide test instance: > > $ pkg-config --libs glew > -lGLEW -lGLU -lGL > > Minimal CMake test config: > > $ cmake . > -- GLEW_LIBRARIES: /usr/lib64/libGLEW.so > -- Configuring done > -- Generating done > > It looks like

Re: blender: Not linking against libGL

Answering part of my own question here using the rawhide test instance: $ pkg-config --libs glew -lGLEW -lGLU -lGL Minimal CMake test config: $ cmake . -- GLEW_LIBRARIES: /usr/lib64/libGLEW.so -- Configuring done -- Generating done It looks like -lGLU is being picked up somewhere else in the

blender: Not linking against libGL

I'm working on updating the blender package to build against OpenImageIO 2.0.3 in rawhide and have worked through the API changes but the build still fails when linking blenderplayer due to undefined references to functions provided by the libGL library. I checked the last good build in koji and

Re: How to avoid re-generating Pagure API keys all the time?

On Tue, Dec 11, 2018 at 4:07 PM Till Maas wrote: > > Hi Ben, > > On Tue, Dec 11, 2018 at 11:42:51AM +0100, Ben Rosser wrote: > > > I don't know. I feel like we could do a lot to improve the experience > > of packaging by investing time into fixing these sorts of minor > > annoyances. (But here I

Multilib inconsistencies between fedora/updates/updates-testing composes

We have seen reports that glibc-headers.i686 comes and goes from the x86_64 updates compose. Previously, we have seen this only for the updates-testing compose: This leads to a very bad update experience. Users file bugs against the glibc package, but I

[Modularity] Working Group IRC meeting minutes (2018-12-11)

= #fedora-meeting-3: Weekly Meeting of the Modularity Working Group = Meeting started by nils at 15:02:54 UTC. Minutes: