Re: F31 System-Wide Change proposal: Update Sphinx to version 2 and drop Python 2 support from Sphinx

> Sphinx 2.0 does not support Python 2. I figured that much :) > We could make it so that we only update Sphinx on python 3, but leave the old > version on Python 2, however that kicking a dead horse, so we decided to drop > python2-sphinx at once. > > > We already have python3-sphinx in f29, so

Re: Attempt to update ispc

Please if possible. I attempt to use gcc to build it but some dependecies are linked to clang which is beyond my skill. This compiler blocks both embree and luxcorerender. See https://src.fedoraproject.org/rpms/ispc Luya On 2019-01-25 9:02 a.m., Jonathan Wakely wrote: > On 25/01/19 08:36 -0800,

Schedule for Thursday's FPC Meeting (2019-02-14 17:00 UTC)

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

Schedule for Thursday's FPC Meeting (2019-02-14 17:00 UTC)

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

Re: GCC 9 OpenMP issues

On Wed, 2019-02-13 at 13:42 -0700, Christoph Junghans wrote: > On Tue, Feb 12, 2019 at 5:39 PM Orion Poplawski > wrote: > > > > On 2/12/19 1:02 AM, Jakub Jelinek wrote: > > > On Mon, Feb 11, 2019 at 07:17:25PM -0700, Orion Poplawski wrote: > > > > Looks like GCC 9 is finally enforcing an OpenMP c

Re: F30 change, bootloaderspec by default

On Tue, Feb 12, 2019 at 5:08 AM Javier Martinez Canillas wrote: > You are correct, we will work on more documentation and also better > tooling to manage the BLS snippets, grubenv file, etc. For example > grub2-editenv is very fragile as was mentioned in this thread. I'm looking at this: https://

Re: Review swaps

On Tue, Feb 5, 2019 at 9:22 PM Jerry James wrote: > Sagemath 8.6 is out, which means that at long last we can upgrade the > gap package. Upgrading gap means dealing with the fact that some of > the fundamental group libraries have now been split out of the main > package and have their own upstre

Re: FC30 Mass Rebuild still not finished

On Thu, 2019-02-14 at 02:45 +0100, Tomasz Kłoczko wrote: > Hi, > > Looks like MR which started two weeks ago still is not fully > finished. Below command has been executed in mirrored rawhide source > packages tree. > > [tkloczko@domek fedora]$ for i in fc{21..30}; do echo "$i $(ls -1 > */*$i.src

Re: openmpi 3.1.3 building

On 2/12/19 10:13 PM, Orion Poplawski wrote: I'm thinking about trying to sneak in openmpi 3.1.3 before the f30 branch.  My COPR rebuilds have been looking pretty good lately so I hope it will go fairly smoothly.  Does anyone have any objections?  I'm planning on starting tomorrow if not. - Or

FC30 Mass Rebuild still not finished

Hi, Looks like MR which started two weeks ago still is not fully finished. Below command has been executed in mirrored rawhide source packages tree. [tkloczko@domek fedora]$ for i in fc{21..30}; do echo "$i $(ls -1 */*$i.src.rpm | wc -l)"; done; echo; ls -1 ?/*|wc -l fc21 16 fc22 15 fc23 21 fc24

Re: F31 System-Wide Change proposal: Update Sphinx to version 2 and drop Python 2 support from Sphinx

On 13. 02. 19 21:55, Dridi Boukelmoune wrote: On Wed, Feb 13, 2019 at 8:38 PM Ben Cotton wrote: https://fedoraproject.org/wiki/Changes/Sphinx2 == Summary == The version 2.0.x of [https://www.sphinx-doc.org/ Sphinx], popular Python documentation generator and framework, is expected to be [http

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On Wednesday, 13 February 2019 at 15:59, Ron Yorston wrote: [...] > Why would a maintainer drop support for the regular package after > they've copied it into a module (or modules)? If, as Neal says, > "module-only" packages can't be used as build dependencies for > regular packages their package

Re: Orphaning some packages

On Wed, 13 Feb 2019, David Cantrell wrote: > these is relatively low. If anyone is interested in taking over the > packages, feel free. I have transferred them to orphaned status: ... > ez-pine-gpg I'll take it, I use this package :-) -- Francisco Javier Tsao Santín http://gattaca.es 1024D/71

Re: F31 System-Wide Change proposal: Update Sphinx to version 2 and drop Python 2 support from Sphinx

On Wed, Feb 13, 2019 at 8:38 PM Ben Cotton wrote: > > https://fedoraproject.org/wiki/Changes/Sphinx2 > > == Summary == > The version 2.0.x of [https://www.sphinx-doc.org/ Sphinx], popular > Python documentation generator and framework, is expected to be > [https://github.com/sphinx-doc/sphinx/issu

Re: Assertion in stl_vector.h

On 13/02/2019 20:35, Christoph Junghans wrote: I am trying to debug https://bugzilla.redhat.com/show_bug.cgi?id=1674863 however I cannot reproduce the issue locally using mock: https://github.com/espressomd/espresso/issues/2507#issuecomment-463262689 nor can upstream, however it still fails in a

Re: GCC 9 OpenMP issues

On Tue, Feb 12, 2019 at 5:39 PM Orion Poplawski wrote: > > On 2/12/19 1:02 AM, Jakub Jelinek wrote: > > On Mon, Feb 11, 2019 at 07:17:25PM -0700, Orion Poplawski wrote: > >> Looks like GCC 9 is finally enforcing an OpenMP change: > >> > >> From https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00628.

Assertion in stl_vector.h

Hi, I am trying to debug https://bugzilla.redhat.com/show_bug.cgi?id=1674863 however I cannot reproduce the issue locally using mock: https://github.com/espressomd/espresso/issues/2507#issuecomment-463262689 nor can upstream, however it still fails in a recent scratch build: https://koji.fedorapro

Orphaning some packages

Hello all, I was going through the list of packages I own in Fedora and see a few that I do not use anymore and do not actively maintain. Traffic on these is relatively low. If anyone is interested in taking over the packages, feel free. I have transferred them to orphaned status: wicd ez-pine

F31 System-Wide Change proposal: Python 3.8

https://fedoraproject.org/wiki/Changes/Python3.8 == Summary == Update the Python stack in Fedora from Python 3.7 to Python 3.8. == Owner == * Name: [[User:Churchyard|Miro Hrončok]] == Detailed Description == We would like to upgrade Python to 3.8 in Fedora 31 thus we are proposing this plan ear

F31 System-Wide Change proposal: Update Sphinx to version 2 and drop Python 2 support from Sphinx

https://fedoraproject.org/wiki/Changes/Sphinx2 == Summary == The version 2.0.x of [https://www.sphinx-doc.org/ Sphinx], popular Python documentation generator and framework, is expected to be [https://github.com/sphinx-doc/sphinx/issues/5950 released in early 2019]. It [https://www.sphinx-doc.org

Re: F30 change, bootloaderspec by default

I glossed over the fact upgrades to Fedora 30 will be converted to the "bls way" of things. So I want to be sure I understand feature scope: - all Fedora 30 editions and spins and archs, *except* 32-bit ARM - new Fedora 30 installations, and upgrades of Fedora 28 and 29 to Fedora 30 - does not app

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

> Fedora Legacy? Please don't call the current way of doing things legacy until modularity shows some maturity. For now it smells like time-to-market-driven protoduction [1] that is still missing crucial core functionality to work end-to-end. Dridi [1] prototype deployed to production __

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On Wed, Feb 13, 2019 at 03:32:55PM +0100, Fabio Valentini wrote: > On Wed, Feb 13, 2019 at 3:23 PM Florian Weimer wrote: > > > > * Fabio Valentini: > > > > > In the past few weeks, it has come up regularly that future > > > "module-only" packages are orphaned (and hence will soon be retired), > >

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On 13. 02. 19 15:32, Fabio Valentini wrote: On Wed, Feb 13, 2019 at 3:23 PM Florian Weimer wrote: * Fabio Valentini: In the past few weeks, it has come up regularly that future "module-only" packages are orphaned (and hence will soon be retired), and nobody stepped up to fix this issue - esp

Re: Error compiling obs-ndi: CMake Error at external/FindLibObs.cmake:

Thanks for your reply, i will contact upstream. Regards Martin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html L

Qt 5.12 coming to rawhide

I will be working to import Qt 5.12.1 into rawhide soon, progress and blockers to be tracked at: https://bugzilla.redhat.com/show_bug.cgi?id=1661849 A good an important thing, as not only is 5.12.x the latest, but also an LTS release as well. Bonus points for (hopefully) fixing a FTBFS issue or

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 13/02/19 14:31, Richard W.M. Jones wrote: > Isn't the assembler syntax different or does gas now support > the nasm syntax (and macros plus a bunch of other stuff AIUI)? > If we require gas then I assume a whole bunch of asm would have > to be rewritten ... Indeed, for example edk2 used to have

Re: [Scitech] openmpi 3.1.3?

On 2/13/19 3:56 AM, Dominik 'Rathann' Mierzejewski wrote: On Wednesday, 13 February 2019 at 06:13, Orion Poplawski wrote: I'm thinking about trying to sneak in openmpi 3.1.3 before the f30 branch. My COPR rebuilds have been looking pretty good lately so I hope it will go fairly smoothly. Does a

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

Emmanuel Seyman wrote: >* Ron Yorston [13/02/2019 08:45] : >> If so, why would they do that? Why would they *not* want their package >> to be available as a regular package? It seems counterproductive for >> them to downgrade their package to this second-class status. > >The goal, IIUC (and I'm n

Re: Error compiling obs-ndi: CMake Error at external/FindLibObs.cmake:

Rex Dieter wrote: > Martin Gansser wrote: >> CMake Error at >> external/FindLibObs.cmake:98 (include): >> include could not find load file: >> >> /usr/include/obs/../cmake/external/ObsPluginHelpers.cmake >> Call Stack (most recent call first): >> CMakeLists.txt:9 (include) > > Easiest ex

Plan to un-retire some NodeJS packages

I plan to un-retire some NodeJS packages that were retired late last year. I've linked to the relevant package review requests. nodejs-is-plain-obj: https://bugzilla.redhat.com/show_bug.cgi?id=1676540 nodejs-event-stream: https://bugzilla.redhat.com/show_bug.cgi?id=1676544 There will likely be se

Re: Error compiling obs-ndi: CMake Error at external/FindLibObs.cmake:

Martin Gansser wrote: > Hi, > > I'am trying to compile obs-ndi for fedora, but this fails with the > following error message: > I use [1] obs-ndi.spec > > + /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG > -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG > -DCMAKE_Fortran_FLAGS_RELEASE:STRING

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On Wed, Feb 13, 2019 at 3:23 PM Florian Weimer wrote: > > * Fabio Valentini: > > > In the past few weeks, it has come up regularly that future > > "module-only" packages are orphaned (and hence will soon be retired), > > and nobody stepped up to fix this issue - especially for non-leaf > > package

Re: How to re-enable all languages in Fedora container images ?

Daniel P. Berrangé wrote: > The Fedora docker container images are built to exclude all gettext > messages files except for the "en" locale. > > What is the "right" way to undo this restriction so that RPM installs > the full RPM contents without stripping anything out. > > Just deleting /etc/rp

Fedora Rawhide-20190213.n.0 compose check report

No missing expected images. Compose FAILS proposed Rawhide gating check! 7 of 47 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not be mapped to openQA tests: FAILED: compose.cloud.all Failed open

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

* Fabio Valentini: > In the past few weeks, it has come up regularly that future > "module-only" packages are orphaned (and hence will soon be retired), > and nobody stepped up to fix this issue - especially for non-leaf > packages. I don't think fedora as a project has a solution for this > yet.

How to re-enable all languages in Fedora container images ?

The Fedora docker container images are built to exclude all gettext messages files except for the "en" locale. What is the "right" way to undo this restriction so that RPM installs the full RPM contents without stripping anything out. Just deleting /etc/rpm/macros.image-language-conf lets future

Re: RFE: logrotate for fedpkg mockbuild -N

On Wed, 13 Feb 2019, Miro Hrončok wrote: Hi, I'm writing to devel to see if others would find this useful or not, before I dig into finding whether it is mock or rpkg to bother about this :D I build packages with `fedpkg mockbuild -N`. i iterate with spec changes and try to build the package

Re: F30 Self-Contained Change proposal: Retire YUM 3

On Wed, Feb 13, 2019 at 9:07 AM Kevin Fenzi wrote: > > On 2/5/19 1:37 PM, Randy Barlow wrote: > > On Mon, 2019-02-04 at 09:56 -0600, Mátyás Selmeci wrote: > >> What's the replacement? > > > > Bodhi switched from mash to pungi, and I think Bodhi might have been > > the last thing using mash. > > Th

Retiring pysvn (was Re: Orphaning pysvn (and non-responsive maintainer: ravenoak))

On Tue, Feb 5, 2019 at 10:01 AM Stephen Gallagher wrote: > > I've been maintaining this for several years since the main admin > (ravenoak) vanished from Fedora. I don't use it anymore (and most of > the world has long since switched to git...) and it has yet again > failed to rebuild during the m

Fedora rawhide compose report: 20190213.n.0 changes

OLD: Fedora-Rawhide-20190212.n.1 NEW: Fedora-Rawhide-20190213.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 1 Dropped packages:6 Upgraded packages: 98 Downgraded packages: 0 Size of added packages: 39.41 KiB Size of dropped packages

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Wed, Feb 13, 2019 at 11:30:43AM +, Nick Clifton wrote: > Hi Paolo, > > > I can maintain nasm if no one else wants to take it. > > Please do, if that it what you want. However I think that it > might be better in the long run if we can retire nasm (and yasm > too) and instead replace them

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On 13/02/2019 12:58, Fabio Valentini wrote: On Wed, Feb 13, 2019 at 10:51 AM Tom Hughes wrote: On 13/02/2019 09:48, Neal Gompa wrote: On Wed, Feb 13, 2019 at 4:34 AM Tom Hughes wrote: On 13/02/2019 09:11, Neal Gompa wrote: On Wed, Feb 13, 2019 at 4:09 AM Tom Hughes wrote: I don't think

Re: Orphaned packages to be retired

Dne 13. 02. 19 v 7:33 Jens-Ulrik Petersen napsal(a): > On Mon, Feb 11, 2019 at 5:44 PM Vít Ondruch > wrote: > > Dne 11. 02. 19 v 4:33 Jens-Ulrik Petersen napsal(a): >> I have to say I am not really enjoying this ongoing aggressive >> package retirement proc

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

* Fabio Valentini [13/02/2019 13:58] : > > It's fine for now, since the ant hasn't been retired from the master > branch - yet. > Once that happens, it will not be available from the regular repos, > but only from the modular repos. The issue here is that, if we have someone who can maintain ant,

Re: Orphaned packages to be retired

On Wed, 13 Feb 2019 at 01:34, Jens-Ulrik Petersen wrote: > > On Mon, Feb 11, 2019 at 5:44 PM Vít Ondruch wrote: >> >> Dne 11. 02. 19 v 4:33 Jens-Ulrik Petersen napsal(a): >> >> I have to say I am not really enjoying this ongoing aggressive package >> retirement process. >> If packages are not br

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On Wed, Feb 13, 2019 at 10:51 AM Tom Hughes wrote: > > On 13/02/2019 09:48, Neal Gompa wrote: > > On Wed, Feb 13, 2019 at 4:34 AM Tom Hughes wrote: > >> > >> On 13/02/2019 09:11, Neal Gompa wrote: > >>> On Wed, Feb 13, 2019 at 4:09 AM Tom Hughes wrote: > >>> > I don't think that second cons

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Wednesday, 13 February 2019 at 12:30, Nick Clifton wrote: > Hi Paolo, > > > I can maintain nasm if no one else wants to take it. > > Please do, if that it what you want. However I think that it > might be better in the long run if we can retire nasm (and yasm > too) and instead replace them w

Re: Orphaned packages that will be retired (and everything will most likely burn)

Hi Paolo, > I can maintain nasm if no one else wants to take it. Please do, if that it what you want. However I think that it might be better in the long run if we can retire nasm (and yasm too) and instead replace them with gas. Cheers Nick PS. In case there is someone reading this email

Re: [Scitech] openmpi 3.1.3?

On Wednesday, 13 February 2019 at 06:13, Orion Poplawski wrote: > I'm thinking about trying to sneak in openmpi 3.1.3 before the f30 branch. > My COPR rebuilds have been looking pretty good lately so I hope it will go > fairly smoothly. Does anyone have any objections? I'm planning on starting >

rawhide fedora-review failed

hi, I can't run fedora-review with rawhide VM. It always failed with message like this: INFO: Build completed INFO: Installing built package(s) INFO: Active plugins: Generic, Shell-api, C/C++ Package basesystem-11-7.fc30.noarch contains no files Package dbus-1:1.12.12-2.fc30.i686 contains no file

RFE: logrotate for fedpkg mockbuild -N

Hi, I'm writing to devel to see if others would find this useful or not, before I dig into finding whether it is mock or rpkg to bother about this :D I build packages with `fedpkg mockbuild -N`. i iterate with spec changes and try to build the package until it passes. I use the -N (reuse the sa

Re: F30 Self-Contained Change proposal: SWID tag enablement

On Thu, Feb 07, 2019 at 05:35:23PM +0100, Jan Pazdziora wrote: > On Tue, Feb 05, 2019 at 07:16:09PM +0100, Miro Hrončok wrote: > > On 05. 02. 19 18:47, Jan Pazdziora wrote: > > > > > ** add SWID metadata awareness to createrepo (but this will not be > > > > Do you mean createrepo_c? createrepo is g

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On 13/02/2019 09:48, Neal Gompa wrote: On Wed, Feb 13, 2019 at 4:34 AM Tom Hughes wrote: On 13/02/2019 09:11, Neal Gompa wrote: On Wed, Feb 13, 2019 at 4:09 AM Tom Hughes wrote: I don't think that second consequence is entirely true. As I understand the the default module stream remains a

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On Wed, Feb 13, 2019 at 4:34 AM Tom Hughes wrote: > > On 13/02/2019 09:11, Neal Gompa wrote: > > On Wed, Feb 13, 2019 at 4:09 AM Tom Hughes wrote: > > > >> I don't think that second consequence is entirely true. > >> > >> As I understand the the default module stream remains available > >> in the

Error compiling obs-ndi: CMake Error at external/FindLibObs.cmake:

Hi, I'am trying to compile obs-ndi for fedora, but this fails with the following error message: I use [1] obs-ndi.spec + /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOO

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On 13/02/2019 09:11, Neal Gompa wrote: On Wed, Feb 13, 2019 at 4:09 AM Tom Hughes wrote: I don't think that second consequence is entirely true. As I understand the the default module stream remains available in the main repo and hence would be installable with things that don't understand mo

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On Wed, Feb 13, 2019 at 4:09 AM Tom Hughes wrote: > > On 13/02/2019 08:05, Neal Gompa wrote: > > > On Wed, Feb 13, 2019 at 2:58 AM Ron Yorston wrote: > > > >> What is a "module-only" package? > > > > These are packages that move from the main Fedora distribution into > > the addon "fedora-modular

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On 13/02/2019 08:05, Neal Gompa wrote: On Wed, Feb 13, 2019 at 2:58 AM Ron Yorston wrote: What is a "module-only" package? These are packages that move from the main Fedora distribution into the addon "fedora-modular" repo that is enabled by default on Fedora systems. There are a couple of

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

* Ron Yorston [13/02/2019 08:45] : > > What causes a package to move? I guess it doesn't just happen > spontaneously, so presumably it's a choice the maintainer makes. It isn't really a move per se. A regular package can be copied into a module. If the package is then orphaned/retired, it ceases

Re: HEADS UP: I plan to correct "python3 setup.py build" calls without proper flags

On 06. 02. 19 15:04, Miro Hrončok wrote: Hi, due to https://fedoraproject.org/wiki/Changes/Python_Extension_Flags it is no longer correct to just call `python3 setup.py build` or `python3 setup.py build_ext` in spec without setting the proper flags (for arched builds with Python extension mod

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

Neal Gompa wrote: >Ron Yorston wrote: >> What is a "module-only" package? > >These are packages that move from the main Fedora distribution into >the addon "fedora-modular" repo that is enabled by default on Fedora >systems. What causes a package to move? I guess it doesn't just happen spontaneou

Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages

On Wed, Feb 13, 2019 at 2:58 AM Ron Yorston wrote: > > Fabio Valentini wrote: > >In the past few weeks, it has come up regularly that future > >"module-only" packages are orphaned (and hence will soon be retired), > >and nobody stepped up to fix this issue - especially for non-leaf > >packages. I