[Review needed] oidn package

Hello team, oidn package is ready for review as dependant for luxcorerender. https://bugzilla.redhat.com/show_bug.cgi?id=1694553 I will gladly do a review swap when needed. Thanks. Luya ___ devel mailing list -- devel@lists.fedoraproject.org To unsu

Re: clang segmentation fault on armv7hf

On 3/31/19 7:31 AM, Richard Shaw wrote: I'm working on building PySide2 for Fedora and have a problem with clang segfaulting only on armv7hf[1]... [1] https://kojipkgs.fedoraproject.org//work/tasks/4670/33794670/build.log https://kojipkgs.fedoraproject.org/packages/ does not have python-py

Re: dnf crashes make fedpkg / mock unusable

On 31. 03. 19 16:04, Fabio Valentini wrote: Hi everybody, Since about one or two days, I am completely unable to build any packages with fedpkg locally, and even running dnf on the host system is really crashy. It looks like dnf crashes while it's refreshing repository metadata. ABRT won't let

PSA: workaround for segfault when running dnf update in F30

librepo-1.9.6 has a major bug that will cause a segfault when a repository has zchunk metadata. To temporarily work around the problem, set zchunk=False in /etc/dnf/dnf.conf or wait until the next updates push comes out About a week ago, we disabled zchunk metadata in the main F30 repository be

Re: provider bad repo (network) or bug development ?

On Sun, 2019-03-31 at 10:56 +0100, Tom Hughes wrote: > On 31/03/2019 10:44, Cătălin George Feștilă wrote: > > > Take a look at my output ( see time and bad response of dnf tool > > versus > > kivi package) > > Where "bad response" means telling you there is no match? > > > I don't sure it is a

Re: dnf crashes make fedpkg / mock unusable

On Sun, Mar 31, 2019, at 11:02 AM, Fabio Valentini wrote: > On Sun, Mar 31, 2019 at 4:04 PM Fabio Valentini wrote: > > > > Hi everybody, > > > > Since about one or two days, I am completely unable to build any > > packages with fedpkg locally, and even running dnf on the host system > > is really

Re: VirtualBox 6 and Vagrant in Fedora 29

On Sun, 2019-03-31 at 10:04 +0200, Dridi Boukelmoune wrote: > Hello, > > If like me you use Vagrant with VirtualBox, you may see an update to > version 6 from RPM Fusion free for f29. The problem you may face > later > is that f29's version of Vagrant doesn't support VirtualBox 6. > > This was en

Re: dnf crashes make fedpkg / mock unusable

On Sun, Mar 31, 2019 at 4:04 PM Fabio Valentini wrote: > > Hi everybody, > > Since about one or two days, I am completely unable to build any > packages with fedpkg locally, and even running dnf on the host system > is really crashy. > > It looks like dnf crashes while it's refreshing repository m

clang segmentation fault on armv7hf

I'm working on building PySide2 for Fedora and have a problem with clang segfaulting only on armv7hf[1]... The source package has shiboken2, pyside2, and pyside2-tools in one big archive but I am building shiboken2 and pyside2-tools with GCC and only pyside2 with clang because if makes use of some

dnf crashes make fedpkg / mock unusable

Hi everybody, Since about one or two days, I am completely unable to build any packages with fedpkg locally, and even running dnf on the host system is really crashy. It looks like dnf crashes while it's refreshing repository metadata. ABRT won't let me report the issue due to "low informational

Fedora rawhide compose report: 20190331.n.0 changes

OLD: Fedora-Rawhide-20190327.n.0 NEW: Fedora-Rawhide-20190331.n.0 = SUMMARY = Added images:5 Dropped images: 4 Added packages: 8 Dropped packages:1 Upgraded packages: 228 Downgraded packages: 0 Size of added packages: 30.74 MiB Size of dropped packages

Re: provider bad repo (network) or bug development ?

On 31/03/2019 10:44, Cătălin George Feștilă wrote: Take a look at my output ( see time and bad response of dnf tool versus kivi package) Where "bad response" means telling you there is no match? I don't sure it is a bug or development issue( the fedora.pkgs.org/29/

Fedora Rawhide-20190331.n.0 compose check report

Missing expected images: Atomichost qcow2 x86_64 Atomichost raw-xz x86_64 Compose FAILS proposed Rawhide gating check! 5 of 47 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not

provider bad repo (network) or bug development ?

Dear team. Take a look at my output ( see time and bad response of dnf tool versus kivi package) I don't sure it is a bug or development issue( the fedora.pkgs.org/29/ has a kivy package). I don't have many options to test it , but you can have a good image on it. Can be a clone or bad repo? Thank

Fedora 30-20190330.n.3 compose check report

Missing expected images: Atomichost raw-xz x86_64 Atomichost qcow2 x86_64 Failed openQA tests: 1/24 (i386), 1/2 (arm), 5/144 (x86_64) ID: 374629 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/374629 ID: 374668 Test: arm Minimal-raw_xz-raw.xz inst

VirtualBox 6 and Vagrant in Fedora 29

Hello, If like me you use Vagrant with VirtualBox, you may see an update to version 6 from RPM Fusion free for f29. The problem you may face later is that f29's version of Vagrant doesn't support VirtualBox 6. This was enough to solve it for me: dnf upgrade vagrant --releasever 30 Assuming

[Test-Announce] Fedora 30 Branched 20190330.n.3 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 30 Branched 20190330.n.3. 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/QA:Release_validation_tes