[389-devel] 389 DS nightly 2019-12-24 - 96% PASS

https://fedorapeople.org/groups/389ds/ci/nightly/2019/12/24/report-389-ds-base-1.4.3.0-20191224git3022f46.fc31.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

[Fedocal] Reminder meeting : Modularity Team (weekly)

Dear all, You are kindly invited to the meeting: Modularity Team (weekly) on 2019-12-24 from 15:00:00 to 16:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Meeting of the Modularity Team. More information available at: [Modularity Team

Fedora-Rawhide-20191223.n.0 compose check report

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

Fedora rawhide compose report: 20191223.n.0 changes

OLD: Fedora-Rawhide-20191222.n.0 NEW: Fedora-Rawhide-20191223.n.0 = SUMMARY = Added images:1 Dropped images: 3 Added packages: 0 Dropped packages:0 Upgraded packages: 8 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size

Re: How to reuild wdune ?

On Monday, 23 December 2019 21:29:41 CET J. Scheurich wrote: > Hi, > > I got > > $ fedpkg build > > for wdune running, but what i need to publish it ? > > So i can install it with > > # yum install wdune > > ? > > so long > MUFTI Check the results of your build:

Re: How to reuild wdune ?

Hi, I got $ fedpkg build for wdune running, but what i need to publish it ? So i can install it with # yum install wdune ? so long MUFTI ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: How to reuild wdune ?

On Mon, Dec 23, 2019 at 07:18:24PM -, Leigh Scott wrote: > Why don't you listen to your sponsors advise? > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/WHP6UKNKFX7RY7Y22CNNGWWKBBJX3JI6/ > > If I was your sponsor I would consider withdrawing your

Re: Fedora 32 System-Wide Change proposal: Use update-alternatives for /usr/bin/cc and /usr/bin/c++

On 12/21/2019 02:30 PM, Tomasz Kłoczko wrote: > > > On Sat, 21 Dec 2019 at 00:37, Neal Gompa > wrote: > [..] > > I believe it's also used by the %cmake and %meson macros. > > > Yep. > Look on the output of the “rpm -E %cmake” and you will find that to switch to

Re: How to reuild wdune ?

> Hi, > > I tried the following: > > $ kinit mufti11(a)FEDORAPROJECT.ORG > rm -rf wdune > fedpkg clone wdune > cd wdune > $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null > > $ git commit -sm "Initial import (#1658153)" > error: gpg failed to sign the data > fatal: failed

Re: How to reuild wdune ?

Fabio Valentini wrote: > On Mon, Dec 23, 2019, 17:45 J. Scheurich wrote: >> $ git commit >> error: gpg failed to sign the data >> fatal: failed to write commit object >> >> Same problem 8-( >> > Looks like you have the option to sign your git commits turned on globally, > probably in ~/.gitconfig

Re: How to reuild wdune ?

On Mon, Dec 23, 2019, 17:45 J. Scheurich wrote: > > I tried the following: >> >> $ kinit muft...@fedoraproject.org >> rm -rf wdune >> fedpkg clone wdune >> cd wdune >> $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null >> >> $ git commit -sm "Initial import (#1658153)" >> >

Re: How to reuild wdune ?

I tried the following: $ kinit muft...@fedoraproject.org rm -rf wdune fedpkg clone wdune cd wdune $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null $ git commit -sm "Initial import (#1658153)" You do

Re: How to reuild wdune ?

On Mon, Dec 23, 2019, 16:16 J. Scheurich wrote: > Hi, > > I tried the following: > > $ kinit muft...@fedoraproject.org > rm -rf wdune > fedpkg clone wdune > cd wdune > $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null > > $ git commit -sm "Initial import (#1658153)" > You

How to reuild wdune ?

Hi, I tried the following: $ kinit muft...@fedoraproject.org rm -rf wdune fedpkg clone wdune cd wdune $ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null $ git commit -sm "Initial import (#1658153)" error: gpg failed to sign the data fatal: failed to write commit object $

Re: Fedora 32 System-Wide Change proposal: Enable fstrim.timer by default

Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/EnableFSTrimTimer Maybe it should be obvious, but the feature page doesn't include details on how to manually enable(opt-in) or disable(opt-out) of the feature. Please add that. -- Rex ___

Re: Orphaned packages looking for new maintainers

On Mon, Dec 23, 2019 at 11:01:33AM +0100, Miro Hrončok wrote: > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you know for sure > that the package should be retired, please do so now with a proper reason: >

Re: orphaning bleachbit

Am 23.12.19 um 01:23 schrieb John M. Harris Jr: > So long as Python2 remains installable, I don't see why you feel the need to > rip it out of the distro. Also imho I expect that Fedora packages will receive security fixes and serious bugs will be fixed (of course still considering that Fedora

Re: Port fedora for RISC-V with out compressed instructions

On Thu, Dec 19, 2019 at 11:40 AM Sreenadh S wrote: > > We want to port fedora for RISC-V with out compressed (RV64IMAFD) > instructions. > > We are from Centre for Development of Advanced Computing (C-DAC) India. > We have implemented an Out-of order quad core RISC-V processor on FPGA. > > The

List of long term FTBFS packages to be retired in February

Dear maintainers. Based on the latest fail to build from source policy, the following packages will be retired from Fedora 32 approximately one week before branching (February 2020). Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The

Re: Build complete, but result generic error

On Mon, Dec 23, 2019, 11:27 Guido Aulisi wrote: > Il giorno lun 23 dic 2019 alle ore 09:24 Guido Aulisi > ha scritto: > > > > Hi, > > Koji reports that build [0] is complete, but it is marked with this > error: > > GenericError: cannot update build 1424540, state: COMPLETE > > > > It's not

Re: Build complete, but result generic error

Il giorno lun 23 dic 2019 alle ore 09:24 Guido Aulisi ha scritto: > > Hi, > Koji reports that build [0] is complete, but it is marked with this error: > GenericError: cannot update build 1424540, state: COMPLETE > > It's not selectable in Bodhi. > Do I have to run it again? > > Thanks > Ciao >

Orphaned packages looking for new maintainers

The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If

Re: orphaning bleachbit

On 23. 12. 19 1:23, John M. Harris Jr wrote: On Sunday, December 22, 2019 4:56:52 AM MST Miro Hrončok wrote: On 22. 12. 19 12:01, John M. Harris Jr wrote: On Sunday, December 22, 2019 3:11:51 AM MST Zbigniew Jędrzejewski-Szmek wrote: 1 was rejected because there was no hope for a python3

Build complete, but result generic error

Hi, Koji reports that build [0] is complete, but it is marked with this error: GenericError: cannot update build 1424540, state: COMPLETE It's not selectable in Bodhi. Do I have to run it again? Thanks Ciao Guido [0]: https://koji.fedoraproject.org/koji/buildinfo?buildID=1424540