[Bug 1632660] TLSv1.3 - enable post-handshake auth

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
perl-IO-Socket-SSL-2.060-3.fc29 has been submitted as an update to Fedora 29.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-8d92841c14

-- 
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

[389-devel] Re: creating a universal class to replace "Entry"

[William Brown]

> On 11 Feb 2019, at 17:43, Anuj Borah  wrote:
> 
> @William Brown  Thanks for the reply , please look into the PR: 
> https://pagure.io/389-ds-base/pull-request/50171
> 
> Its to create nsfilterrole . 

I don’t understand how this email and that PR are related? 
> 

—
Sincerely,

William Brown
Software Engineer, 389 Directory Server
SUSE Labs
___
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

[389-devel] Re: creating a universal class to replace "Entry"

[Anuj Borah]

@William Brown   Thanks for the reply , please
look into the PR: https://pagure.io/389-ds-base/pull-request/50171

Its to create nsfilterrole .

On Mon, Feb 11, 2019 at 1:06 PM William Brown  wrote:

>
>
> > On 11 Feb 2019, at 17:01, Anuj Borah  wrote:
> >
> > Hi,
> >
> > As 'Entry' is not allowed to use now , In replace of Entry we are
> suggested to use UserAccounts and UserAccount which is very limited to some
> object classes .
> (['account','posixaccount','inetOrgPerson','organizationalPerson’]
>
> > )
> >
>
> There are many other types than this though?
>
> src/lib389/lib389/plugins.py:23:class Plugin(DSLdapObject):
> src/lib389/lib389/plugins.py:199:class MEPConfig(DSLdapObject):
> src/lib389/lib389/plugins.py:233:class MEPTemplate(DSLdapObject):
> src/lib389/lib389/plugins.py:444:class
> ReferentialIntegrityConfig(DSLdapObject):
> src/lib389/lib389/plugins.py:758:class MemberOfSharedConfig(DSLdapObject):
> src/lib389/lib389/plugins.py:887:class
> AutoMembershipRegexRule(DSLdapObject):
> src/lib389/lib389/plugins.py:905:class
> AutoMembershipDefinition(DSLdapObject):
> src/lib389/lib389/plugins.py:1015:class
> AutoMembershipRegexRule(DSLdapObject):
> src/lib389/lib389/plugins.py:1120:class
> LinkedAttributesConfig(DSLdapObject):
> src/lib389/lib389/plugins.py:1551:class AccountPolicyConfig(DSLdapObject):
> src/lib389/lib389/plugins.py:1598:class DNAPluginConfig(DSLdapObject):
> src/lib389/lib389/idm/organizationalrole.py:17:class
> OrganizationalRole(DSLdapObject):
> src/lib389/lib389/idm/nscontainer.py:11:class nsContainer(DSLdapObject):
> src/lib389/lib389/idm/nscontainer.py:49:class
> nsHiddenContainer(DSLdapObject):
> src/lib389/lib389/idm/domain.py:11:class Domain(DSLdapObject):
> src/lib389/lib389/idm/posixgroup.py:18:class PosixGroup(DSLdapObject):
> src/lib389/lib389/idm/organization.py:17:class Organization(DSLdapObject):
> src/lib389/lib389/idm/ipadomain.py:11:class IpaDomain(DSLdapObject):
> src/lib389/lib389/idm/group.py:17:class Group(DSLdapObject):
> src/lib389/lib389/idm/group.py:104:class UniqueGroup(DSLdapObject):
> src/lib389/lib389/idm/organizationalunit.py:16:class
> OrganizationalUnit(DSLdapObject):
> src/lib389/lib389/idm/account.py:15:class Account(DSLdapObject):
> src/lib389/lib389/tombstone.py:18:class Tombstone(DSLdapObject):
> src/lib389/lib389/backend.py:393:class Backend(DSLdapObject):
> src/lib389/lib389/backend.py:831:class DatabaseConfig(DSLdapObject):
> src/lib389/lib389/tasks.py:24:class Task(DSLdapObject):
> src/lib389/lib389/pwpolicy.py:287:class PwPolicyEntry(DSLdapObject):
> src/lib389/lib389/config.py:28:class Config(DSLdapObject):
> src/lib389/lib389/config.py:205:class Encryption(DSLdapObject):
> src/lib389/lib389/config.py:233:class RSA(DSLdapObject):
> src/lib389/lib389/config.py:358:class LDBMConfig(DSLdapObject):
> src/lib389/lib389/monitor.py:16:class Monitor(DSLdapObject):
> src/lib389/lib389/monitor.py:109:class MonitorLDBM(DSLdapObject):
> src/lib389/lib389/monitor.py:143:class MonitorBackend(DSLdapObject):
> src/lib389/lib389/monitor.py:190:class MonitorChaining(DSLdapObject):
> src/lib389/lib389/saslmap.py:12:class SaslMapping(DSLdapObject):
> src/lib389/lib389/index.py:27:class Index(DSLdapObject):
> src/lib389/lib389/index.py:64:class VLVSearch(DSLdapObject):
> src/lib389/lib389/index.py:147:class VLVIndex(DSLdapObject):
> src/lib389/lib389/encrypted_attributes.py:15:class
> EncryptedAttr(DSLdapObject):
> src/lib389/lib389/_mapped_object.py:84:class DSLdapObject(DSLogging):
> src/lib389/lib389/_mapped_object.py:441:if not
> issubclass(type(obj1), DSLdapObject) or not issubclass(type(obj2),
> DSLdapObject):
> src/lib389/lib389/_mapped_object.py:442:raise
> ValueError("Invalid arguments: Expecting object types that inherits
> 'DSLdapObject' class")
> src/lib389/lib389/agreement.py:23:class Agreement(DSLdapObject):
> src/lib389/lib389/cos.py:18:class CosTemplate(DSLdapObject):
> src/lib389/lib389/cos.py:65:class CosIndirectDefinition(DSLdapObject):
> src/lib389/lib389/cos.py:111:class CosPointerDefinition(DSLdapObject):
> src/lib389/lib389/replica.py:881:class Replica(DSLdapObject):
> src/lib389/lib389/replica.py:1288:class
> BootstrapReplicationManager(DSLdapObject):
> src/lib389/lib389/mappingTree.py:381:class MappingTree(DSLdapObject):
> src/lib389/lib389/chaining.py:18:class ChainingConfig(DSLdapObject):
> src/lib389/lib389/chaining.py:59:class ChainingDefault(DSLdapObject):
> src/lib389/lib389/chaining.py:81:class ChainingLink(DSLdapObject):
> src/lib389/lib389/changelog.py:20:class Changelog5(DSLdapObject):
> src/lib389/lib389/rootdse.py:15:class RootDSE(DSLdapObject):
> src/lib389/lib389/referral.py:14:class Referral(DSLdapObject):
> src/lib389/lib389/schema.py:71:class Schema(DSLdapObject):
>
> At worst, you can always use a raw:
>
> DSLdapObject(instance, dn)
>
> to get “minimal” access to *anything* regardless of type. The entire value
> proposition of lib389 is that we wrap *the most common and useful types*.
> Each 

[Bug 1632660] TLSv1.3 - enable post-handshake auth

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
   Fixed In Version||perl-IO-Socket-SSL-2.060-4.
   ||fc30
   Assignee|p...@city-fan.org   |ppi...@redhat.com



-- 
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

Re: Orphaned packages to be retired

[Miro Hrončok]

On 11. 02. 19 8:24, Miro Hrončok wrote:
This is needed for ARM by ghc:8.4 and 
https://fedoraproject.org/wiki/Changes/GHC_8.4


And will you take it?


I now see you will. Thank You!

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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

Re: Orphaned packages to be retired

[Miro Hrončok]

On 11. 02. 19 4:33, Jens-Ulrik Petersen wrote:
On Tue, Feb 5, 2019 at 4:27 AM Miro Hrončok I plan to retire packages that were already announced 3 times next Monday.



Which packages?



Such packages that will be listed as 7+ weeks orphaned and will have no open 
releng ticket. Might very well be none today.



llvm5.0                       jistone, orphan, tstellar            0 weeks 
ago


This is needed for ARM by ghc:8.4 and 
https://fedoraproject.org/wiki/Changes/GHC_8.4


And will you take it?


llvm6.0                       orphan, tstellar                     0 weeks 
ago


This is needed on ARM by ghc:8.6.


The same.

I have to say I am not really enjoying this ongoing aggressive package 
retirement process.


OK, let's discuss this!

If packages are not broken and needed by other packages, then I don't see why we 
are hurrying to break things.


Because we don't want orphaned packages. It brings further danger to the 
distribution.


I think a better process might be for maintainers orphaning packages to contact 
dependent package maintainers directly asking them to take over the package they 
want to drop.


They should do this, but we cannot force them. Hence instead we are contacting 
the dependent package owners via this mass e-mail. All maintainers determined as 
affected are bcc'ed.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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

[Bug 1672470] perl-HTTP-BrowserDetect-3.21 is available

[bugzilla]

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

Emmanuel Seyman  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-HTTP-BrowserDetect-3.2
   ||1-1.fc30
 Resolution|--- |RAWHIDE
Last Closed||2019-02-11 07:07:28



--- Comment #1 from Emmanuel Seyman  ---
Built for rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1207197

-- 
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

Re: Help needed for FTBFS in rawhide because of libraries order

[Mamoru TASAKA]

Peng Wu wrote on 2019/02/11 14:12:

Thanks for the investigation, I just back port the patch for Fedora rawhide
now.

Peng

On Mon, Feb 4, 2019 at 10:32 PM Parag Nemade  wrote:




I think this commit
https://gitlab.gnome.org/GNOME/pango/commit/d0cb6be7431d1a3c711bd45bcf05b34601604037
will revert it back but we need to wait for next upstream pango release.

Parag


Okay, thank you for applying the upstream patch. Actually this fixes at least
FTBFS issues for several packages.

Regards,
Mamoru
___
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

Re: Orphaning: llvm5.0, clang5.0, llvm6.0, clang6.0

[Jens-Ulrik Petersen]

I can take llvm5.0: I already requested unorphaning from releng.

llvm5.0 is needed on ARM by ghc:8.4 and ghc:8.6 needs llvm6.0.

Jens

ps (It *might* be possible to bump some of those for ghc but I don't really
have the extra time needed for that.)

On Tue, Jan 29, 2019 at 6:27 AM Tom Stellard  wrote:

> Hi,
>
> I am orphaning the llvm and clang compatibility packages for versions 5.0
> and 6.0.
> We are about to push LLVM 8.0 into rawhide, so I will no longer maintain
> these
> older versions.  There are still a few users of these packages, so the
> package
> owners can either rebuild their packages for LLVM 7/8 or take over
> ownership
> of the compatibility package they need.
>
> -Tom
> ___
> 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
>


-- 
Jens Petersen
Associate Manager
i18n Software Engineering
Emerging Platform Group
Platform Engineering
Singapore
___
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

Re: Help needed for FTBFS in rawhide because of libraries order

[Peng Wu]

Thanks for the investigation, I just back port the patch for Fedora rawhide
now.

Peng

On Mon, Feb 4, 2019 at 10:32 PM Parag Nemade  wrote:

>
>
> On Mon, Feb 4, 2019 at 5:44 PM Mamoru TASAKA 
> wrote:
>
>> Guido Aulisi wrote on 2019/02/03 20:31:
>> > Hi,
>> > I'm trying to debug a FTBFS in rawhide:
>> >
>> > https://koji.fedoraproject.org/koji/taskinfo?taskID=32412101
>> >
>> > Apparently it fails because of library ordering, but it works in f29.
>> > g_object_unref is defined in gobject-2.0 and it gets surely added by
>> > the 'pkgconf  --libs cairo pangocairo pango' command.
>> >
>> > Did anything about gobject or glib change in rawhide recently?
>> >
>> > Thank you for any help.
>> >
>> > Guido
>> >
>> Apparently this is because rawhide pango.pc does not add -lglib-2.0
>> when called with pkgconf --libs:
>>
>> F-29
>> $ rpm -q pango
>> pango-1.42.4-2.fc29.x86_64
>> $ pkgconf --libs pango
>> -lpango-1.0 -lgobject-2.0 -lglib-2.0
>>
>> F-30
>> $ rpm -q pango
>> pango-1.43.0-1.fc30.x86_64
>> $ pkgconf --libs pango
>> -lpango-1.0
>>
>> pango-1.43.0-1.fc30.x86_64 pango.pc shows:
>> --
>> Name: Pango
>> Description: Internationalized text handling
>> Version: 1.43.0
>> Requires.private: glib-2.0 >=  2.38.0, gobject-2.0 >=  2.38.0, fribidi
>> >=  0.19.7, libthai >=  0.1.9, harfbuzz >=  1.4.2, fontconfig >=  2.11.91,
>> freetype2, xrender, xft >=  2.0.0, cairo >=  1.12.10
>> Libs: -L${libdir} -lpango-1.0
>> Libs.private: -lm
>> --
>> So -lglib-2.0 is moved to Requires.private.
>>
>> I guess this is due to this commit:
>>
>> https://gitlab.gnome.org/GNOME/pango/commit/86855b6a458fd9b82d246f723a7e3c9cdb37a8a0
>> It seems to be doing some refactoring (with adding some fallback), and
>> "requires: gobject_dep," line is deleted.
>>
>> Currently I am not sure if it is intentional or accidental.
>>
>
> I think this commit
> https://gitlab.gnome.org/GNOME/pango/commit/d0cb6be7431d1a3c711bd45bcf05b34601604037
> will revert it back but we need to wait for next upstream pango release.
>
> Parag
> ___
> 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
>
___
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

[Bug 1674344] New: perl-Geo-ShapeFile-2.66 is available

[bugzilla]

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

Bug ID: 1674344
   Summary: perl-Geo-ShapeFile-2.66 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Geo-ShapeFile
  Keywords: FutureFeature, Triaged
  Assignee: dd...@cpan.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: dd...@cpan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 2.66
Current version/release in rawhide: 2.64-7.fc30
URL: http://search.cpan.org/dist/Geo-ShapeFile/

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/2921/

-- 
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

Re: Orphaned packages to be retired

[Jens-Ulrik Petersen]

On Tue, Feb 5, 2019 at 4:27 AM 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:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>
> I plan to retire packages that were already announced 3 times next Monday.
>

Which packages?


llvm5.0   jistone, orphan, tstellar0 weeks
> ago
>

This is needed for ARM by ghc:8.4 and
https://fedoraproject.org/wiki/Changes/GHC_8.4


> llvm6.0   orphan, tstellar 0 weeks
> ago


This is needed on ARM by ghc:8.6.


I have to say I am not really enjoying this ongoing aggressive package
retirement process.
If packages are not broken and needed by other packages, then I don't see
why we are hurrying to break things.
I think a better process might be for maintainers orphaning packages to
contact dependent package maintainers directly asking them to take over the
package they want to drop.

Jens
___
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

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

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  58  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b7556983e8   
tomcat-7.0.92-1.el6
  54  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-a0ddb153b8   
game-music-emu-0.6.2-1.el6
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-809dcc772f   
golang-1.11.5-1.el6


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

jglobus-2.1.0-7.el6
safekeep-1.4.5-1.el6

Details about builds:



 jglobus-2.1.0-7.el6 (FEDORA-EPEL-2019-d376460fd6)
 Globus Java client libraries

Update Information:

Disallow TLS 1.1.

ChangeLog:

* Sun Feb 10 2019 Mattias Ellert  - 2.1.0-7
- Only allow TLSv1 and TLSv1.2 (not TLSv1.1)
- Remove unused FORCE_SSLV3_AND_CONSTRAIN_CIPHERSUITES_FOR_GRAM
- Adapt to changes in bouncycastle 1.61




 safekeep-1.4.5-1.el6 (FEDORA-EPEL-2019-6423f3eecb)
 The SafeKeep backup system

Update Information:

Latest upstream release

ChangeLog:

* Sun Feb 10 2019 Frank Crawford  1.4.5-1
- Latest upstream release
* Fri Feb  8 2019 Frank Crawford  - 1.4.4-8
- Correct FTBS error due to default in F30 as python3, replace with python2
* Sat Feb  2 2019 Fedora Release Engineering  - 
1.4.4-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Sat Jul 14 2018 Fedora Release Engineering  - 
1.4.4-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Fri Feb  9 2018 Fedora Release Engineering  - 
1.4.4-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Jan 31 2018 Iryna Shcherbina  - 1.4.4-4
- Update Python 2 dependency declarations to new packaging standards
  (See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3)
* Thu Jul 27 2017 Fedora Release Engineering  - 
1.4.4-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
* Sat Feb 11 2017 Fedora Release Engineering  - 
1.4.4-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild


___
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

Re: F30 Self-Contained Change proposal: Bash 5.0

[Neal Gompa]

On Sun, Feb 10, 2019 at 9:22 PM Dridi Boukelmoune
 wrote:
>
> > I don't read repodata manually, libsolv does it for me. Using libdnf and/or 
> > libmodulemd is not something what (for example) OBS would do. They rely on 
> > libsolv for all dependency solving operations. And unless it will support 
> > modularity (which depends heavily on DNF people's ability to speak to 
> > upstream), nothing will improve.
>
> I don't know how things are currently done, but shouldn't modularity
> build on top instead of being bolted in?
>

"Build on top" does not make sense, because each of the aspects are
crossing into each other in order to provide a useful solution.

> I assume libsolv can already deal with multiple repodata since yum/dnf
> support having multiple repositories. Shouldn't modules simply provide
> repodata and have the "modularity" plugin figure which repodata to
> fetch depending on the selected streams? That wouldn't require any
> change in libsolv.
>

This is actually how it works now, but causes all kinds of problems,
even in DNF itself. If you try to get debugsolver data for debugging
issues with DNF, it makes absolutely no sense because the solver
doesn't know anything about RH modularity. This means that solutions
are slower and suboptimal. It also makes development on improving the
technology very hard. It also increases the memory requirements
because everything has to be held in memory while a second solver runs
on the data to apply various filters. And the solution "logic" for
modules is very similar to how yum did solutions for RPMs, so it's
quite slow and prone to issues.

> Disclaimer, I don't know any better but if modules are simply
> parallel-available RPMs, it shouldn't be bothering libsolv (except
> maybe to enforce a stream downgrade).
>

Modules are effectively mutually conflicting collections of RPMs,
operating like stacked/nested repos with the properties of composition
groups. They also contain all kinds of extra information which is used
to determine availability, usability, and other things.

If they worked the way you thought they did, we wouldn't be having
these issues. :(



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
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

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 196  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f9d6ff695a   
bibutils-6.6-1.el7 ghc-hs-bibutils-6.6.0.0-1.el7 pandoc-citeproc-0.3.0.1-4.el7
 180  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d   
condor-8.6.11-1.el7
  54  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6fa6cebc3   
game-music-emu-0.6.2-1.el7
  51  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b43fdd19c3   
vcftools-0.1.16-1.el7
  24  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-17b3c81533   
cacti-1.2.0-1.el7 cacti-spine-1.2.0-2.el7
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bd6a1ae962   
pdns-recursor-4.1.9-1.el7
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-26a7022f9a   
golang-1.11.5-1.el7
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-cf8b89de02   
mosquitto-1.5.6-1.el7


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

jglobus-2.1.0-13.el7
kf5-kauth-5.52.0-2.el7
libaec-1.0.3-3.el7
safekeep-1.4.5-1.el7

Details about builds:



 jglobus-2.1.0-13.el7 (FEDORA-EPEL-2019-4f3d10ac4b)
 Globus Java client libraries

Update Information:

Disallow TLS 1.1.

ChangeLog:

* Sun Feb 10 2019 Mattias Ellert  - 2.1.0-13
- Only allow TLSv1 and TLSv1.2 (not TLSv1.1)
- Remove unused FORCE_SSLV3_AND_CONSTRAIN_CIPHERSUITES_FOR_GRAM
- Adapt to changes in bouncycastle 1.61
* Fri Feb  1 2019 Fedora Release Engineering  - 
2.1.0-12
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild




 kf5-kauth-5.52.0-2.el7 (FEDORA-EPEL-2019-5f60a8861f)
 KDE Frameworks 5 Tier 2 integration module to perform actions as privileged 
user

Update Information:

Backport security fix for CVE-2019-7443

ChangeLog:

* Sat Feb  9 2019 Rex Dieter  - 5.52.0-2
- (branch) Remove support for passing gui QVariants to KAuth helpers




 libaec-1.0.3-3.el7 (FEDORA-EPEL-2019-d9f3aeb15c)
 Adaptive Entropy Coding library

Update Information:

Version bump to 1.0.3

ChangeLog:

* Sat Feb  9 2019 Christoph Junghans  - 1.0.3-3
- Include missing header
* Tue Feb  5 2019 Christoph Junghans  - 1.0.3-2
- Enable all tests
* Mon Feb  4 2019 Christoph Junghans  - 1.0.3-1
- Version bump to 1.0.3 (bug #1672326)
* Fri Feb  1 2019 Fedora Release Engineering  - 
1.0.2-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Fri Jul 13 2018 Fedora Release Engineering  - 
1.0.2-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Wed Feb  7 2018 Fedora Release Engineering  - 
1.0.2-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Sat Feb  3 2018 Igor Gnatenko  - 1.0.2-2
- Switch to %ldconfig_scriptlets

References:

  [ 1 ] Bug #1672326 - libaec-1.0.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1672326




 safekeep-1.4.5-1.el7 (FEDORA-EPEL-2019-76b5029309)
 The SafeKeep backup system

Update Information:

Latest upstream release

ChangeLog:

* Sun Feb 10 2019 Frank Crawford  1.4.5-1
- Latest upstream release
* Fri Feb  8 2019 Frank Crawford  - 1.4.4-8
- Correct FTBS error due to default in F30 as python3, replace with python2
* Sat Feb  2 2019 Fedora Release Engineering  - 
1.4.4-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Sat Jul 14 2018 Fedora Release Engineering  - 
1.4.4-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Fri Feb  9 2018 Fedora Release Engineering  - 
1.4.4-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Wed Jan 31 2018 Iryna Shcherbina  - 1.4.4-4
- Update Python 2 dependency declarations to new packaging standards
  (See 

Re: Orphaning: llvm5.0, clang5.0, llvm6.0, clang6.0

[David Airlie]

On Sat, Feb 9, 2019 at 5:50 PM Igor Gnatenko
 wrote:
>
> https://cgit.freedesktop.org/beignet/
>
> Last commits are from 2018/08 which is half year ago.
>
> I'd like to keep it, but try using master branch.

Beignet is dead upstream, Intel are no longer supporting it.

Dave.
___
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

[Bug 1674288] New: perl-Excel-Writer-XLSX-0.99 is available

[bugzilla]

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

Bug ID: 1674288
   Summary: perl-Excel-Writer-XLSX-0.99 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Excel-Writer-XLSX
  Keywords: FutureFeature, Triaged
  Assignee: dd...@cpan.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: dd...@cpan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.99
Current version/release in rawhide: 0.98-4.fc30
URL: http://search.cpan.org/dist/Excel-Writer-XLSX/

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/2860/

-- 
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

Re: F30 change, bootloaderspec by default

[Chris Murphy]

On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas
 wrote:
>
> On Wed, Feb 6, 2019 at 5:28 AM Chris Murphy  wrote:
> >
> > https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
> >
> > I want this change to succeed but I'm experiencing a regression, and
> > while trying to troubleshoot it I'm finding it difficult to understand
> > the myriad differences:
> >
>
> Is this on F29 or Rawhide? Also, it's on an EFI or BIOS install?

Rawhide UEFI. I thought it was a regression compared to grubby and
grub2-mkconfig, because the problem doesn't happen with them. But
those tools work directly on the grub.cfg which on UEFI only ever
appears on FAT. Meanwhile, blscfg's .conf files are located at
/boot/loader/entries which on this particular test setup is subject to
zstd compression, and GRUB doesn't yet support zstd compression. GRUB
couldn't read the file contents, therefore it's not a regression, it's
a missing feature. Removing the compression solved the problem.


> > there's a lot of grub2 documentation in Fedora and outside Fedora, all
> > of which conflicts with this feature. And Fedora's experts in QA and
>
> Could you please elaborate a little bit? If you see a big mismatch
> between some documentation and how the BLS support behaves, please
> point out so we can try to make it more transparent for users.

If a user has bootloader related issues, I ordinarily would only ask
for a copy of the grub.cfg. But with bls systems, I need to ask for
the grub.cfg, all the .conf files, and the grubenv file. All of them
need to be interpreted. Each of those files are only described in
generic terms by upstream GRUB, and no one else is using those files
in the specific way they're being used in Fedora.

Between this feature for F30, and the F29 feature to hide the grub
menu which comes with boot success+fail marking by using the grubenv,
there are substantial changes in bootloading on Fedora that exist no
where else and near as I can tell there is no documentation at all. I
can't really call specs we don't fully follow, or feature pages, to be
documentation.



> On Rawhide the blscfg command now supports to load BLS entries to
> troubleshoot these cases. For example you should be able to do:
>
> blscfg (hd0,gpt2)/loader/entries/
>
> to load all the BLS snippets from a directory or:
>
> blscfg 
> (hd0,gpt2)/loader/entries/loader/entries/036f3661be4047b6b678d491f76df6f4-5.0.0-0.rc4.git3.1.fc30.x86_64.conf
>
> to load a single BLS snippet.

Ok that is a useful troubleshooting technique. In my case this was
totally silent, ergo it found nothing even though there were files
there. Adding 'set debug=all' and then following that up with blscfg
exposed what directories it was looking at and the contents weren't
readable - and that's when I clued in.



--
Chris Murphy
___
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

Re: java: Unrecognized option: --add-modules

[Richard Shaw]

On Sun, Feb 10, 2019 at 11:13 AM Tako Schotanus  wrote:

> Not done anything with Java modules yet so I might be completely wrong,
> but isn't modules a Java 9 feature?
>

Yeah, I think I jumped the gun... Having issues and should have backed up
first, now I can't downgrade to a previous version of unifi...

Thanks,
Richard
___
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

Identical doxygen docs on different architectures

[Orion Poplawski]

With the introduction of doxygen 1.8.15 in rawhide (or perhaps just 
better noarch rpmdiff checks?), the paraview-doc noarch sub-package is 
now different on different architectures:


BuildError: The following noarch package built differently on different 
architectures: paraview-doc-5.5.2-20.fc30.noarch.rpm

rpmdiff output was:
removed /usr/share/doc/paraview/doxygen/html/dir_01_06.html
removed /usr/share/doc/paraview/doxygen/html/dir_01_22.html
removed /usr/share/doc/paraview/doxygen/html/dir_01_71.html
removed /usr/share/doc/paraview/doxygen/html/dir_02_06.html
removed /usr/share/doc/paraview/doxygen/html/dir_02_22.html
removed /usr/share/doc/paraview/doxygen/html/dir_02_71.html
removed /usr/share/doc/paraview/doxygen/html/dir_03_06.html
removed /usr/share/doc/paraview/doxygen/html/dir_04_06.html
added   /usr/share/doc/paraview/doxygen/html/dir_04_09.html
removed /usr/share/doc/paraview/doxygen/html/dir_04_22.html
added   /usr/share/doc/paraview/doxygen/html/dir_04_25.html

I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1673236 but as of 
yet we have fix.  Any other doxygen experts out there with some ideas? 
The -doc package is relatively large (60M) so it would be nice to keep 
it as noarch.


--
Orion Poplawski
Manager of NWRA Technical Systems  720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
___
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

Re: Self Introduction: Dragos Iorga

[idf31]

Hello Leigh!
Here is my first review: https://bugzilla.redhat.com/show_bug.cgi?id=1674278
I know it's a pretty small program but it seems ok for a start.
Thank you!


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
La duminică, februarie 10, 2019 5:15 PM, Leigh Scott  
a scris:

> Welcome.
> Feel free to CC me to your first package review, maybe I can assist.
>
> 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

___
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

[Test-Announce] 2019-02-11 @ 16:00 UTC - Fedora QA Meeting

[Adam Williamson]

# Fedora Quality Assurance Meeting
# Date: 2019-02-11
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We didn't meet for a couple of weeks, so let's get together and
complete the agenda from the last meeting.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 30 status and Change review
3. Release criteria / test case proposal status
4. Test Day / community event status
5. Open floor
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@lists.fedoraproject.org
___
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

[Test-Announce] 2019-02-11 @ 17:00 UTC - Fedora 30 Blocker Review Meeting

[Adam Williamson]

# F30 Blocker Review meeting
# Date: 2019-02-11
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have 4 proposed Beta blockers and 4 proposed Final blockers
to review, so let's have a Fedora 30 blocker review meeting on Monday!

If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting -  the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

We'll be evaluating these bugs to see if they violate any of the 
Release Criteria and warrant the blocking of a release if they're not 
fixed. Information on the release criteria for F30 can be found on the 
wiki [0].

For more information about the Blocker and Freeze exception process, 
check out these links:
 - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
 - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting 
works - or how it's supposed to go and you want to run one - check out 
the SOP on the wiki:
 - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good weekend and see you on Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@lists.fedoraproject.org
___
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

Re: %py3_build should accept options

[Miro Hrončok]

On 09. 02. 19 14:51, Richard Shaw wrote:
On Sat, Feb 9, 2019 at 7:48 AM Igor Gnatenko > wrote:


You can do "%py3_build -- --some-cool-option".


I'll see about trying that.. I'm trying to build PySide2 but it's not passing 
--verbose or -j12 to the cmake builds so it looks like it doesn't matter anyway.


Try defining %py_setup_args.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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

Re: Self Introduction: Dragos Iorga

[Leigh Scott]

Welcome.
Feel free to CC me to your first package review, maybe I can assist. 
___
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

[Bug 1674274] New: perl-XML-LibXML-2.0134 is available

[bugzilla]

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

Bug ID: 1674274
   Summary: perl-XML-LibXML-2.0134 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-XML-LibXML
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: caillon+fedoraproj...@gmail.com, jples...@redhat.com,
ka...@ucw.cz, mbar...@fastmail.com,
perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com,
sandm...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 2.0134
Current version/release in rawhide: 2.0133-1.fc30
URL: https://metacpan.org/release/XML-LibXML

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/3527/

-- 
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

Re: java: Unrecognized option: --add-modules

[Tako Schotanus]

Not done anything with Java modules yet so I might be completely wrong, but
isn't modules a Java 9 feature?

On Sun, Feb 10, 2019 at 4:00 PM Richard Shaw  wrote:

> When did java lose its option for --add-modules?!?!?
>
> # java --add-modules java.activation
> Unrecognized option: --add-modules
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
>
> # rpm -q java-1.8.0-openjdk
> java-1.8.0-openjdk-1.8.0.191.b13-0.fc29.x86_64
>
> I can't start my unifi server now because it needs the java.activation
> module that's depreciated.
>
> Thanks,
> Richard
> ___
> 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
>


-- 

TAKO SCHOTANUS

SENIOR SOFTWARE ENGINEER

Red Hat



___
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

Re: signing status

[Kevin Fenzi]

On 2/10/19 8:01 AM, Sérgio Basto wrote:
> On Sat, 2019-02-09 at 10:33 -0800, Kevin Fenzi wrote:
>> On 2/9/19 2:00 AM, Miro Hrončok wrote:
>>> On 08. 02. 19 17:41, Kevin Fenzi wrote:
 Just wanted to update everyone on our current status.

 ...

 I'm hopeful that it will catch back up today and we can go back
 to
 normal.
>>>
>>> Is this somehow relevant?
>>
>> This was caused by my fixing upgrade path on f30.
>> ie, there was an older 'dar' tagged in, so I tagged in the 'newer'
>> (by
>> NVR) one. It was signed, but apparently the written out rpms were
>> garbage collected already.
>>
>> I'm fixing these up and will fire a new rawhide after.
> 
> 
> Hi, I don't if it helps but I don't know you notice that Fedora-
> Rawhide- 20190207 [1] still running and pungi.log [2] last write was
> 2019-02-08 16:45:52 ( 2 days ago) ...

It crashed/died and the status didn't update.

It's not still composing, it will just be stuck in started forever. ;(

Yesterdays failed in an anaconda traceback on the kde live, so I am
untagging the new anaconda(s) and restarting it.

Signing should be all caught up as of yesterday.

kevin
--
> 
> Best regards,
> 
> [1]
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190207.n.0/
> 
> [2]
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190207.n.0/logs/global/pungi.global.log
> 
> 
>> kevin
>> --
>>>
>>>
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190209.n.1/logs/global/pungi.global.log
>>>
>>>
>>> 2019-02-09 08:44:00 [ERROR   ] Compose run failed: RPM(s) not found
>>> for
>>> sigs: ['CFC659B9']. Check log for details. Unsigned packages:
>>> dar-2.6.0-2.fc30
>>> dar-debuginfo-2.6.0-2.fc30
>>> dar-debugsource-2.6.0-2.fc30
>>> electrum-3.3.2-3.fc30
>>> libdar-2.6.0-2.fc30
>>> libdar-debuginfo-2.6.0-2.fc30
>>> libdar-devel-2.6.0-2.fc30
>>> mysqltuner-1.7.19-2.git.59e5f40.fc30
>>> openscap-1.3.0_alpha2-2.fc30
>>> openscap-containers-1.3.0_alpha2-2.fc30
>>> openscap-debuginfo-1.3.0_alpha2-2.fc30
>>> openscap-debugsource-1.3.0_alpha2-2.fc30
>>> openscap-devel-1.3.0_alpha2-2.fc30
>>> openscap-engine-sce-1.3.0_alpha2-2.fc30
>>> openscap-engine-sce-debuginfo-1.3.0_alpha2-2.fc30
>>> openscap-engine-sce-devel-1.3.0_alpha2-2.fc30
>>> openscap-perl-1.3.0_alpha2-2.fc30
>>> openscap-perl-debuginfo-1.3.0_alpha2-2.fc30
>>> openscap-python3-1.3.0_alpha2-2.fc30
>>> openscap-scanner-1.3.0_alpha2-2.fc30
>>> openscap-scanner-debuginfo-1.3.0_alpha2-2.fc30
>>> openscap-utils-1.3.0_alpha2-2.fc30
>>> openscap-utils-debuginfo-1.3.0_alpha2-2.fc30
>>> python-oslo-messaging-8.0.0-1.fc29
>>> python-oslo-messaging-doc-8.0.0-1.fc29
>>> python2-oslo-messaging-8.0.0-1.fc29
>>> python2-oslo-messaging-tests-8.0.0-1.fc29
>>> python3-oslo-messaging-8.0.0-1.fc29
>>> python3-oslo-messaging-tests-8.0.0-1.fc29
>>>
>>
>>
>> ___
>> 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




signature.asc
Description: OpenPGP digital signature
___
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

Re: MBI (Playground 2.0)

[Stephen John Smoogen]

On Fri, 8 Feb 2019 at 16:00, Stephen John Smoogen  wrote:
>
> On Fri, 8 Feb 2019 at 14:31, Adam Williamson  
> wrote:
> >
> > On Thu, 2019-02-07 at 12:21 -0500, Stephen John Smoogen wrote:
> > > On Thu, 7 Feb 2019 at 09:40, Stephen John Smoogen  
> > > wrote:
> > > > On Thu, 7 Feb 2019 at 09:21, Fabio Valentini  
> > > > wrote:
> > > > > On Thu, Feb 7, 2019 at 3:01 PM Stephen John Smoogen 
> > > > >  wrote:
> > > > > > On Thu, 7 Feb 2019 at 07:34, Fabio Valentini  
> > > > > > wrote:
> > > > librepo.LibrepoException: (8, 'Cannot prepare internal mirrorlist:
> > > > Curl error (28): Timeout was reached for
> > > > https://mirrors.fedoraproject.org/metalink?repo=updates-released-f29=x86_64
> > > > [Operation too slow. Less than 1000 bytes/sec transferred the last 30
> > > > seconds]', 'An Curl handle error')
> > > >
> > > > That says the proxy it was trying to get to was too slow.. I will see
> > > > if I can find which one it was at that timezone and see if I can
> > > > address.
> > > >
> > >
> > > OK the problem does not look like it is mirrorlist related but
> > > something to do with the copr host/network at that time
> > >
> > > 209.132.184.33 - - [07/Feb/2019:00:01:59 +] "GET
> > > /metalink?repo=updates-released-f29=x86_64 HTTP/1.1" 200 18343
> > > "-" "dnf/2.7.5"
> > >
> > > says it sent the data but it looks like something that the client was
> > > looking for timed out. I will work with the copr team to diagnose
> > > further.
> >
> > FWIW, openQA tests have been failing relatively frequently with
> > timeouts while refreshing repos or 503s from mirrormanager for the last
> > few weeks. I'm pretty sure this didn't used to be anything like as
> > common...
>
> I am checking if we are seeing an increase and when. There are
> generally some every hour when mirrormanager changes out pkls but
> sometimes it grows.

OK looking at the general stats for the last 2 months, we were seeing
an average of  0.2% of all connections generating a 503 (Out of
22114356 connections on 2018/12/03 only 41263 were 503 and the rest
are 200, similar to all days). There doesn't seem to be any large
uptick in them that stands out but I am not ruling out specific
mirrors, times of requests or clients yet that could make these more
likely.




--
Stephen J Smoogen.
___
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

Re: signing status

[Sérgio Basto]

On Sat, 2019-02-09 at 10:33 -0800, Kevin Fenzi wrote:
> On 2/9/19 2:00 AM, Miro Hrončok wrote:
> > On 08. 02. 19 17:41, Kevin Fenzi wrote:
> > > Just wanted to update everyone on our current status.
> > > 
> > > ...
> > > 
> > > I'm hopeful that it will catch back up today and we can go back
> > > to
> > > normal.
> > 
> > Is this somehow relevant?
> 
> This was caused by my fixing upgrade path on f30.
> ie, there was an older 'dar' tagged in, so I tagged in the 'newer'
> (by
> NVR) one. It was signed, but apparently the written out rpms were
> garbage collected already.
> 
> I'm fixing these up and will fire a new rawhide after.


Hi, I don't if it helps but I don't know you notice that Fedora-
Rawhide- 20190207 [1] still running and pungi.log [2] last write was
2019-02-08 16:45:52 ( 2 days ago) ...

Best regards,

[1]
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190207.n.0/

[2]
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190207.n.0/logs/global/pungi.global.log


> kevin
> --
> > 
> > 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190209.n.1/logs/global/pungi.global.log
> > 
> > 
> > 2019-02-09 08:44:00 [ERROR   ] Compose run failed: RPM(s) not found
> > for
> > sigs: ['CFC659B9']. Check log for details. Unsigned packages:
> > dar-2.6.0-2.fc30
> > dar-debuginfo-2.6.0-2.fc30
> > dar-debugsource-2.6.0-2.fc30
> > electrum-3.3.2-3.fc30
> > libdar-2.6.0-2.fc30
> > libdar-debuginfo-2.6.0-2.fc30
> > libdar-devel-2.6.0-2.fc30
> > mysqltuner-1.7.19-2.git.59e5f40.fc30
> > openscap-1.3.0_alpha2-2.fc30
> > openscap-containers-1.3.0_alpha2-2.fc30
> > openscap-debuginfo-1.3.0_alpha2-2.fc30
> > openscap-debugsource-1.3.0_alpha2-2.fc30
> > openscap-devel-1.3.0_alpha2-2.fc30
> > openscap-engine-sce-1.3.0_alpha2-2.fc30
> > openscap-engine-sce-debuginfo-1.3.0_alpha2-2.fc30
> > openscap-engine-sce-devel-1.3.0_alpha2-2.fc30
> > openscap-perl-1.3.0_alpha2-2.fc30
> > openscap-perl-debuginfo-1.3.0_alpha2-2.fc30
> > openscap-python3-1.3.0_alpha2-2.fc30
> > openscap-scanner-1.3.0_alpha2-2.fc30
> > openscap-scanner-debuginfo-1.3.0_alpha2-2.fc30
> > openscap-utils-1.3.0_alpha2-2.fc30
> > openscap-utils-debuginfo-1.3.0_alpha2-2.fc30
> > python-oslo-messaging-8.0.0-1.fc29
> > python-oslo-messaging-doc-8.0.0-1.fc29
> > python2-oslo-messaging-8.0.0-1.fc29
> > python2-oslo-messaging-tests-8.0.0-1.fc29
> > python3-oslo-messaging-8.0.0-1.fc29
> > python3-oslo-messaging-tests-8.0.0-1.fc29
> > 
> 
> 
> ___
> 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
-- 
Sérgio M. B.
___
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

[Bug 1674257] New: perl-Module-Load-0.34 is available

[bugzilla]

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

Bug ID: 1674257
   Summary: perl-Module-Load-0.34 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Module-Load
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org,
ppi...@redhat.com, st...@silug.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.34
Current version/release in rawhide: 0.32-418.fc30
URL: http://search.cpan.org/dist/Module-Load/

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/3102/

-- 
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

java: Unrecognized option: --add-modules

[Richard Shaw]

When did java lose its option for --add-modules?!?!?

# java --add-modules java.activation
Unrecognized option: --add-modules
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

# rpm -q java-1.8.0-openjdk
java-1.8.0-openjdk-1.8.0.191.b13-0.fc29.x86_64

I can't start my unifi server now because it needs the java.activation
module that's depreciated.

Thanks,
Richard
___
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

Self Introduction: Dragos Iorga

[idf31]

Hello. My name is Dragos.
I'm 14 years old. I like programming, computing, GNU/Linux, Fedora and system 
administration.
I've used GNU/Linux and other FOSS software for 5 years.
I can program in Python and C/C++. I feel comfortable in Bash.
I want to contribute to Fedora because I want to give something back to the 
FOSS world.
I chose to be a package maintainer because packages are an important part of 
GNU/Linux distributions like Fedora.

Sent with [ProtonMail](https://protonmail.com) Secure Email.___
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

Re: MBI (Playground 2.0)

[Fabio Valentini]

On Sat, Feb 9, 2019 at 9:29 AM Dridi Boukelmoune
 wrote:
>
> > FWIW, openQA tests have been failing relatively frequently with
> > timeouts while refreshing repos or 503s from mirrormanager for the last
> > few weeks. I'm pretty sure this didn't used to be anything like as
> > common...
>
> Whether it's dnf upgrade of my system or mock builds, both problems
> have been increasingly frustrating me by orders of magnitude.
> Especially for mock build, I had to make sure to --offline a given
> build after a successful repo refresh & rpm download because it became
> ridiculously hard to get mock --buildsrpm and mock --rebuild to
> succeed in a row!
>
> And my internet access has been flaky for "the last few weeks" too so
> I thought it was causing the failures, but then even on a good
> connection it kept happening.

That's exactly my experience, as well.

First I've put it off as "my internet connection being unreliable".
But, since almost everything works fine, but mock builds continue to fail
(mostly because of "Failed to synchronize cache for repo 'foo'", where
foo is either fedora, updates, or rawhide),
I now think this really is some infra problem.

Also, I think some of the problems that happen in COPR are caused by
its very burst-y behavior:

https://copr.fedorainfracloud.org/status/stats/

For example, today, some of my builds were pending for over 7 hours,
during which time almost no running build completed, but pending tasks
blew up from the average 0-10 to over 140, since no pending tasks
moved to running at all, during that time, from what I can tell.
Then, a lot of builds (about 35) were moved to the "running" state at
once, and some of them failed with connectivity issues, again - which
doesn't surprise me, when there are possibly hundreds of mock builds
triggered by COPR at about the same time, obviously overwhelming the
system serving the repositories.

Fabio


> Dridi
> ___
> 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
___
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

Changes in nheko and mtxclient packages

[Vitaly Zaitsev]

Hello!

I'm going to change upstream of nheko and mtxclient packages to a fork.
Original upstreams are dead and no longer maintained.

Original upstream: https://github.com/mujx/nheko

New upstream: https://github.com/Nheko-Reborn/nheko


--
Sincerely,
 Vitaly Zaitsev (vit...@easycoding.org)
___
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

Re: Policy regarding service preset enabled (e.g. performance co-pilot)

[Georg Sauthoff]

Hello,

On Sun, Feb 10, 2019 at 10:08:51AM +1100, Nathan Scott wrote:
> On Sun, Feb 10, 2019 at 6:47 AM Georg Sauthoff  wrote:
> > [...]
> > I'm asking because installing the dstat replacement[1] in Fedora 29
> > resulted in 3 additional always running systemd services[2] and 2 open
> > ports.
 
> The new dstat script resides in the pcp-system-tools sub-package of
> PCP.  This package depends on python3, python3-pcp and pcp-libs.  None
> of these packages contain systemd services.

The {pmcd,pmlogger,pmie}.service files are provided by the 'pcp'
package. And pcp-system-tools *does* depend on pcp. See also:

# dnf remove pcp
Dependencies resolved.

 PackageArch Version   Repository  Size

Removing:
 pcpx86_64   4.3.0-3.fc29  @updates   4.2 M
Removing dependent packages:
 pcp-system-tools   x86_64   4.3.0-3.fc29  @updates   620 k


[..]
> I wonder if you have installed the (optional) pcp-zeroconf package,
> Georg?  This is a convenience package which automates setup of

No, I don't have it installed:

# rpm -q pcp-zeroconf
package pcp-zeroconf is not installed

> frequently needed PCP services for use in customer support situations.
> You do not need to install this package to use dstat.

As-is, because of the dependencies (see above) I have to install them.

> The new dstat does not require running services, by default it runs in

Yes, this is true, the service don't need to be running for the new dstat.

> a standalone fashion.
[..]

> > Perhaps it's just me, but having 3 services enabled after installing the
> > dstat replacement ('which strives for 100% output compatibility with the
> > original dstat') feels like a violation of the principle of least
> > astonishment.
 
> Agreed - that's why the code is written the way it is, and the
> packages are structured the way they are.  It is not the case that you
> need to have 3 additional services running when using the new dstat.

The problem is that pmie/pmcd/pmlogger are enabled by default because they have
their 'vendor preset' configured to 'enabled'. See also:

# systemctl status pmie pmcd pmlogger  
● pmie.service - Performance Metrics Inference Engine
   Loaded: loaded (/usr/lib/systemd/system/pmie.service; disabled; vendor 
preset: enabled)
[..]

# find /usr/lib/systemd -name '*.preset' | xargs grep 
'\<\(pmcd\|pmlogger\|pmie\)'
/usr/lib/systemd/system-preset/90-default.preset:enable pmcd.service
/usr/lib/systemd/system-preset/90-default.preset:enable pmlogger.service
/usr/lib/systemd/system-preset/90-default.preset:enable pmie.service

# dnf provides /usr/lib/systemd/system-preset/90-default.preset 
fedora-release-29-7.noarch : Fedora release files
[..]

Do I need to create a Bugzilla tickets for fixing the pcp dependencies and
presets or do you take care of it?

Best regards
Georg

-- 
https://gms.tf/
___
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

[Bug 1672325] perl-XML-Feed-0.59 is available

[bugzilla]

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

Emmanuel Seyman  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-XML-Feed-0.59-1.fc30
 Resolution|--- |RAWHIDE
Last Closed||2019-02-10 09:34:54



--- Comment #4 from Emmanuel Seyman  ---
Built for rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1207201

-- 
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