Fedora updates-20180715.0 compose check report

Missing expected images: Atomichost qcow2 x86_64 Atomichost raw-xz x86_64 Passed openQA tests: 2/2 (x86_64) New passes (same test did not pass in updates-20180713.0): ID: 257682 Test: x86_64 AtomicHost-dvd_ostree-iso install_default URL: https://openqa.fedoraproject.org/tests/257682 ID:

[389-devel] 389 DS nightly 2018-07-15 - 89% PASS

https://fedorapeople.org/groups/389ds/ci/nightly/2018/07/15/report-389-ds-base-1.4.0.11-20180714git6d4caac.fc28.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Fedora EPEL 6 updates-testing report

The following Fedora EPEL 6 Security updates need testing: Age URL 35 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6c663378c unrtf-0.21.9-8.el6 19 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-98ff28b9d0 drupal7-backup_migrate-3.5-1.el6 8

Re: Fedora 29 Mass Rebuild

> "AL" == Avram Lubkin writes: AL> Makes sense, but is this documented anywhere? It's in the EPEL FAQ: https://fedoraproject.org/wiki/EPEL/FAQ#Is_it_possible_to_get_a_package_only_into_EPEL_and_not_Fedora.3F - J< ___ devel mailing list --

Re: Fedora 29 Mass Rebuild

> > Currently you should run this: > fedpkg retire "This is an EPEL only package" > in both the master and f28 branches. > Makes sense, but is this documented anywhere? On Sat, Jul 14, 2018 at 1:46 PM, Jason L Tibbitts III wrote: > > "AL" == Avram Lubkin writes: > > AL> We had issues,

Re: Fedora 29 Mass Rebuild

> "AL" == Avram Lubkin writes: AL> We had issues, Bug 1600418, because python3-dns, which is intended AL> only for EPEL7, was included in the mass rebuild for 28 and had an AL> f28 branch created. Now it's been included in the f29 mass AL> rebuild. How do we keep this from happening? Well,

Re: Fedora 29 Mass Rebuild

We had issues, Bug 1600418, because python3-dns, which is intended only for EPEL7, was included in the mass rebuild for 28 and had an f28 branch created. Now it's been included in the f29 mass rebuild. How do we keep this from happening? Avram ___ devel

Koji (was: Re: F29 Self Contained Change: Deprecate YUM 3)

On Thu, Jul 12, 2018 at 10:15:38AM +0200, Daniel Mach wrote: > > koji > > > > koji is kinda important. I think this is meaning python2-koji? > > I would hope python3-koji/koji stays around? > > > ditto I don't understand, will Koji still work or not? I was told (I don't know for sure) that

Re: Fedora 29 Mass Rebuild

On Friday, 6 July 2018 14.29.40 WEST Mohan Boddu wrote: > > We will be running scripts to output failure stats. > please be sure to let releng know if you see any bugs in the reporting. > ... I got this: dist.abicheck FAILED for fftw2-2.1.5-35.fc29

[Bug 1601132] perl-Statistics-Descriptive-3.0701 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1601132 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-Statistics-Descriptive

[Bug 1601159] New: perl-Business-ISMN-1.132 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1601159 Bug ID: 1601159 Summary: perl-Business-ISMN-1.132 is available Product: Fedora Version: rawhide Component: perl-Business-ISMN Keywords: FutureFeature, Triaged Assignee:

Re: Self Introduction: Chris/BunnyApocalypse

On Fri, Jul 13, 2018 at 04:06:20PM -0400, BunnyApocalypse wrote: > I look forward to meeting you and getting involved in the many > amazing things happening in the Fedora community! Hi Chris, and welcome! -- Matthew Miller Fedora Project Leader ___

Re: [HEADS UP] Removal of GCC from the buildroot

This bit the bcache-tools package too, which I fixed. On 07/13/2018 12:39 PM, Igor Gnatenko wrote: On Fri, Jul 13, 2018, 11:19 Miro Hrončok > wrote: On 8.7.2018 20:46, Igor Gnatenko wrote: > As per Changes/Remove GCC from BuildRoot >