Fedora updates-20180715.0 compose check report

[Fedora compose checker]

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: 257683  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/257683
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JYNWGADS6JLE4NIAG2I5LJW7IW7Y722S/

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

[vashirov]

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 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org/message/RBVWDLCPWWCPBQXFEUKLMDJ2QXDCYHYS/

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

[updates]

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  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8c4ebc0d2d   
wordpress-4.9.7-1.el6
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-d801e05f92   
uwsgi-2.0.17.1-1.el6


The following builds have been pushed to Fedora EPEL 6 updates-testing

gtk-gnutella-1.1.13-1.el6

Details about builds:



 gtk-gnutella-1.1.13-1.el6 (FEDORA-EPEL-2018-4dc5586627)
 GUI based Gnutella Client

Update Information:

Update to 1.1.13

ChangeLog:

* Sat Jul 14 2018 Dmitry Butskoy  - 1.1.13-1
- update to 1.1.13

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/IBE4EGXB3DRMXJ2D5LNREJFI4CT435OH/

Re: Fedora 29 Mass Rebuild

[Jason L Tibbitts III]

> "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 -- 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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/RTO4J3AGNK7PT4LHICRSU2GIUWDOOXXR/

Re: Fedora 29 Mass Rebuild

[Avram Lubkin]

>
> 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, 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, it's not retired in rawhide, so it's going to keep getting built
> and branched.  If it's an EPEL-only package, you need to immediately
> retire the master branch when the repository is created.
>
> Currently you should run this:
>   fedpkg retire "This is an EPEL only package"
> in both the master and f28 branches.
>
> The buildsystem should then automatically block that package from future
> composes so it will disappear from the repositories, and it should not
> acquire an f29 branch when the branching happens.
>
>  - J<
>
___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/7G5JJOMF7GE6FOQN55D5NLW7RUJTPVNQ/

Re: Fedora 29 Mass Rebuild

[Jason L Tibbitts III]

> "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, it's not retired in rawhide, so it's going to keep getting built
and branched.  If it's an EPEL-only package, you need to immediately
retire the master branch when the repository is created.

Currently you should run this:
  fedpkg retire "This is an EPEL only package"
in both the master and f28 branches.

The buildsystem should then automatically block that package from future
composes so it will disappear from the repositories, and it should not
acquire an f29 branch when the branching happens.

 - J<
___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/QVLRNXFY3FM6B4R2BU4E3QEOXEH56CJQ/

Re: Fedora 29 Mass Rebuild

[Avram Lubkin]

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 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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/NLUXR2TSZ2HERJZUWNHG5PWAWPMUJ6JE/

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

[Richard W.M. Jones]

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 this change will break Koji.
We're using Koji on top of Fedora 29 to build Fedora/RISC-V.

We'd love to use dnf instead of yum of course, but it seems like Koji
uses a bunch of yum APIs, rather than just using the yum command line
tool,so I've no idea how much work it's going to be to fix that.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BNTY2R7DVC3MWHHFDQDZN25CYA6WXQPD/

Re: Fedora 29 Mass Rebuild

[José Abílio Matos]

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

https://taskotron.fedoraproject.org/artifacts/all/90f31b8a-86a6-11e8-8b63-525400fc9f92/
tests.yml/fftw2-2.1.5-35.fc29.log

That basically says:
=== changes of 'libfftw.so.2.0.7'===
  Functions changes summary: 0 Removed, 0 Changed (4 filtered out), 0 Added 
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
  Function symbols changes summary: 2 Removed, 0 Added function symbols not 
referenced by 
debug info
  Variable symbols changes summary: 0 Removed, 0 Added variable symbol not 
referenced by 
debug info

  2 Removed function symbols not referenced by debug info:

_fini
_init

 end of changes of 'libfftw.so.2.0.7'===

The same applying to other so variants.

Are these ABI changes real or harmless?

> Regards
> 
> Mohan Boddu

Regards, :-)
-- 
José Abílio
___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/X22MQ63J63BIUBNOUVBHVHSM46J7AI6F/

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

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1601132

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-Statistics-Descriptive |perl-Statistics-Descriptive
   |-3.0700 is available|-3.0701 is available



--- Comment #1 from Upstream Release Monitoring 
 ---
Latest upstream release: 3.0701
Current version/release in rawhide: 3.0613-2.fc29
URL: http://search.cpan.org/dist/Statistics-Descriptive/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/7545/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/QCKK3LPG72I7RG2K2WFVI7DCQN3FA3FN/

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

[bugzilla]

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: c...@m.fsf.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: c...@m.fsf.org, mefos...@gmail.com,
perl-devel@lists.fedoraproject.org



Latest upstream release: 1.132
Current version/release in rawhide: 1.131-6.fc29
URL: http://search.cpan.org/dist/Business-ISMN

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/5433/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/DFZ6OVVXTUQBSGIGT7N6RLM3OXJHPZYW/

Re: Self Introduction: Chris/BunnyApocalypse

[Matthew Miller]

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
___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/NCC6BCL6RVE4W7UFCYYHU65W53NHCDTS/

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

[Rolf Fokkens]

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
>
,
I'm
> going to automatically add BuildRequires: gcc and/or BuildRequires:
> gcc-c++ to packages which fail to build with common messages
(like gcc:
> command not found, also autotools/cmake/meson are supported).
>
> I'm going to do this tomorrow.
>
> After which, I'm going to ask rel-eng to finally remove it from
> buildroot. This will happen before mass rebuild. Stay tuned.
> --

I've clicked randomly trough failures during the mass rebuild at [1].

I see quite a lot of commands not founds for gcc, cc, c++...

I think the maintainers should add them and that's fine, but it
seemed
that during this change you said you will add those. Did it happen?


Yes, I've pushed over 2k commits adding those, however regexp might 
have not catched all possible cases. Would appreciate if you would 
link such packages so that I can fix them. Or maintainers can do it 
themselves.


[1] https://kojipkgs.fedoraproject.org/mass-rebuild/f29-failures.html

-- 
Miro Hrončok

--
Phone: +420777974800
IRC: mhroncok

--

-Igor Gnatenko



___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/INTODKJDI2NU36RBHKPYNLDOPSBRAPV6/



___
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
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/3EI357BHP6LWUEJH7FM6R3KYX4RLHFZA/