Fedora-Rawhide-20201206.n.1 compose check report

Missing expected images: Xfce raw-xz armhfp Compose FAILS proposed Rawhide gating check! 3 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 20/180 (x86_64), 13/122 (aarch64) New failures (same test not failed in

Fedora rawhide compose report: 20201206.n.1 changes

OLD: Fedora-Rawhide-20201205.n.0 NEW: Fedora-Rawhide-20201206.n.1 = SUMMARY = Added images:1 Dropped images: 11 Added packages: 3 Dropped packages:0 Upgraded packages: 95 Downgraded packages: 0 Size of added packages: 330.91 KiB Size of dropped packages:0

announce: rhbzquery

Hi, I want to announce another small tool I made called rhbzquery . It generates bugzilla query urls (and can open them automatically) like this: $ rhbzquery f33 kernel summary=network https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&product=Fed

Re: Reducing noise on devel list

Fwiw I have been filtering out the rawhide report to a separate folder for years... I mean I originally did it for the opposite reason: I wanted to be able to find the reports without all the other devel discussions. Jens ___ devel mailing list -- devel

Re: btrfs: nodatacow and snapshots

On Sun, Dec 6, 2020 at 3:54 PM Sergio Belkin wrote: > > Hi, > Let's say that I have 2 subvolumes for both / and /home. What happen with a > snapshot of /home if I run before : > chattr +C /home/jdoe/VMs ? If /home/jdoe/VMs is a directory, then it and its contents are included in the snapshot. A

btrfs: nodatacow and snapshots

Hi, Let's say that I have 2 subvolumes for both / and /home. What happen with a snapshot of /home if I run before : chattr +C /home/jdoe/VMs ? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org ___ devel mailing list -- devel@

Re: [EPEL-devel] Broken EPEL7 builds

On Sun, Dec 06, 2020 at 07:51:13PM +0100, Antonio T. sagitter wrote: > https://koji.fedoraproject.org/koji/taskinfo?taskID=56903884 > > I opened a ticket about: > https://pagure.io/releng/issue/9887 Should be fixed now. Please reopen the ticket if you see any further issues... kevin signatur

Re: Broken EPEL7 builds

On Sun, Dec 6, 2020 at 10:08 AM Antonio T. sagitter wrote: > > Hi everyone. > > EPEL7 builds are not executed due to this error: Since no one knows which EPEL 7 package you are referring to, built with which software on which build platform, perhaps you could provide a hint? > DEBUG util.py:634

Re: Review requests: virt-backup & chunkfs

Hau idatzi du Richard Shaw (hobbes1...@gmail.com) erabiltzaileak (2020 abe. 5, lr. (17:47)): > > Two pretty simple review requests. Reviewed & approved ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@li

Re: [EPEL-devel] Broken EPEL7 builds

https://koji.fedoraproject.org/koji/taskinfo?taskID=56903884 I opened a ticket about: https://pagure.io/releng/issue/9887 On 06/12/20 19:46, Stephen John Smoogen wrote: On Sun, 6 Dec 2020 at 10:08, Antonio T. sagitter mailto:sagit...@fedoraproject.org>> wrote: Hi everyone. EPEL7

Re: [EPEL-devel] Broken EPEL7 builds

On Sun, 6 Dec 2020 at 10:08, Antonio T. sagitter wrote: > Hi everyone. > > EPEL7 builds are not executed due to this error: > > I am guessing you are talking about building packages in Fedora Infrastructure? Do you have a koji job we can point developers to? > DEBUG util.py:634: Traceback (

Broken EPEL7 builds

Hi everyone. EPEL7 builds are not executed due to this error: DEBUG util.py:634: Traceback (most recent call last): DEBUG util.py:634:File "/usr/bin/dnf", line 57, in DEBUG util.py:634: from dnf.cli import main DEBUG util.py:634:File "/usr/lib/python2.7/site-packages/dnf/__ini

Re: Should the default editor be changed from vi to nano on upgrades to Fedora 33+

On Fri, Dec 4, 2020 at 7:23 AM Dridi Boukelmoune wrote: > > > > Maybe I need to reboot my system for vim to take over again? > > > > You will at least need to logout and log back in. > > You're right, if I force a login instead of plain sudo it becomes apparent: > > $ sudo env | grep EDITOR > $ su