[Bug 1577433] New: perl-YAML-1.25 is available

[bugzilla]

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

Bug ID: 1577433
   Summary: perl-YAML-1.25 is available
   Product: Fedora
   Version: rawhide
 Component: perl-YAML
  Keywords: FutureFeature, Triaged
  Assignee: p...@city-fan.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org,
st...@silug.org



Latest upstream release: 1.25
Current version/release in rawhide: 1.24-2.fc28
URL: http://search.cpan.org/dist/YAML/

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

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

[Bug 1577426] New: perl-Mojolicious-7.78 is available

[bugzilla]

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

Bug ID: 1577426
   Summary: perl-Mojolicious-7.78 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Mojolicious
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr,
perl-devel@lists.fedoraproject.org,
robinlee.s...@gmail.com, yan...@declera.com



Latest upstream release: 7.78
Current version/release in rawhide: 7.77-1.fc29
URL: http://mojolicio.us/

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

-- 
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 Media Writer for macOS, is not signed?

[Chris Murphy]

Hi,

The Fedora Media Writer for macOS at getfedora.org is not signed. I
filed this bug a couple weeks ago but somehow lost track of it, and
also it's possibly not the right location for the bug report as it
relates to what's offered on getfedora.org

As I mention in the bug, it's not a big deal to use the work around
for unsigned binaries when testing. But today I tested both the macOS
and Windows versions available on getfedora.org, the macOS version is
not signed, the Windows version is signed by Red Hat Inc.

https://github.com/FedoraQt/MediaWriter/issues/163

Is this this a releng issue I should file a separate bug for?


-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: "invalid path: ~/.fedora-server-ca.cert"

[Tim Jackson]

On 11/05/18 21:23, Björn Persson wrote:


Tim Jackson wrote:

Firstly, could the error message "invalid path: ~/.fedora-server-ca.cert" be
improved? There _is_ a CA certificate in that location, untouched since August
2014.


I think that error message is probably correct. Tilde expansion is a
shell feature, and shouldn't be expected to work if the pathname isn't
processed by a shell. 


Good point.


Unless Fedpkg promises shell-like expansion features, that pathname truly is 
invalid.
I don't know why you didn't have this problem earlier. Perhaps it
worked by accident before because a shell was invoked somewhere in the
process?


Having established that it was the Koji config (see other mail), perhaps Koji 
(or some underlying library) supported expansions of config file values at 
some point? (Perhaps unintentionally). Agree that it's somewhat unexpected 
though, both that it worked for 10+ years, and that it stopped working...


Thanks

Tim
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: "invalid path: ~/.fedora-server-ca.cert"

[Tim Jackson]

On 11/05/18 19:23, Patrick  マルタインアンドレアス  Uiterwijk wrote:


You very likely have an /etc/koji.conf.rpmnew.
Could you please move that over /etc/koji.conf?
If not, maybe you have a ~/.koji, with custom config, you might need to remove.


Thanks! That solved it. I had a ~/.koji/config, last modified 2007-11-15 (!) 
which had various config options set (to what seem to be "default" values), 
including "serverca". I don't recall ever manually editing this, I don't have 
any particular interest in Koji (i.e. I'm unlikely to have edited it without 
being told to), and the values all look like "defaults". So I suspect that 
some tooling set that, somewhere along the way. But it's 10.5 years ago, so 
who knows.


Sometimes I get the feeling that a "longstanding" + "infrequent" contributor 
is, ironically, a even worse combination than merely being an infrequent 
contributor...this is probably a good example ;-)


Tim
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[rpms/perl-Time-Moment] New Commits To "rpms/perl-Time-Moment" (f28)

[pagure]

The following commits were pushed to the repo rpms/perl-Time-Moment on branch
f28, which you are following:
fe137d095f4868b4c2d848b7ff2ccf465d61343dDenis Fateyevperl-Time-Moment: 
0.44 release



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-Time-Moment/commits/f28
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[rpms/perl-Time-Moment] New Commits To "rpms/perl-Time-Moment" (f27)

[pagure]

The following commits were pushed to the repo rpms/perl-Time-Moment on branch
f27, which you are following:
fe137d095f4868b4c2d848b7ff2ccf465d61343dDenis Fateyevperl-Time-Moment: 
0.44 release



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-Time-Moment/commits/f27
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[rpms/perl-Time-Moment] New Commits To "rpms/perl-Time-Moment" (f26)

[pagure]

The following commits were pushed to the repo rpms/perl-Time-Moment on branch
f26, which you are following:
fe137d095f4868b4c2d848b7ff2ccf465d61343dDenis Fateyevperl-Time-Moment: 
0.44 release



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-Time-Moment/commits/f26
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1568834] Missing BuildRequires: kde-filesystem in perl-Qt.spec

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version||perl-Qt-4.14.3-14.fc28
 Resolution|--- |ERRATA
Last Closed||2018-05-11 17:12:54



--- Comment #19 from Fedora Update System  ---
perl-Qt-4.14.3-14.fc28 has been pushed to the Fedora 28 stable repository. If
problems still persist, please make note of it in this bug report.

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

[rpms/perl-Time-Moment] New Commits To "rpms/perl-Time-Moment" (epel7)

[pagure]

The following commits were pushed to the repo rpms/perl-Time-Moment on branch
epel7, which you are following:
fe137d095f4868b4c2d848b7ff2ccf465d61343dDenis Fateyevperl-Time-Moment: 
0.44 release



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-Time-Moment/commits/epel7
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[rpms/perl-Time-Moment] New Commits To "rpms/perl-Time-Moment" (master)

[pagure]

The following commits were pushed to the repo rpms/perl-Time-Moment on branch
master, which you are following:
fe137d095f4868b4c2d848b7ff2ccf465d61343dDenis Fateyevperl-Time-Moment: 
0.44 release



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-Time-Moment/commits/master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1575520] abi-compliance-checker doesn't work under F28

[bugzilla]

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



--- Comment #16 from Fedora Update System  ---
abi-compliance-checker-2.2-3.el7 has been pushed to the Fedora EPEL 7 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-1171f003c1

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

[Bug 1576567] abi-compliance-checker: misses find dependency

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
abi-compliance-checker-2.2-3.el7 has been pushed to the Fedora EPEL 7 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-1171f003c1

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

[Bug 1576617] perl-Net-HTTP-6.18 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
perl-Net-HTTP-6.18-1.fc26 has been pushed to the Fedora 26 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-0f68b0d22f

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

Re: "invalid path: ~/.fedora-server-ca.cert"

[Björn Persson]

Tim Jackson wrote:
> Firstly, could the error message "invalid path: ~/.fedora-server-ca.cert" be 
> improved? There _is_ a CA certificate in that location, untouched since 
> August 
> 2014.

I think that error message is probably correct. Tilde expansion is a
shell feature, and shouldn't be expected to work if the pathname isn't
processed by a shell. Unless Fedpkg promises shell-like expansion
features, that pathname truly is invalid.

I don't know why you didn't have this problem earlier. Perhaps it
worked by accident before because a shell was invoked somewhere in the
process?

Björn Persson


pgp57MDI80SvY.pgp
Description: OpenPGP digital signatur
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1576567] abi-compliance-checker: misses find dependency

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
abi-compliance-checker-2.2-3.fc28 has been pushed to the Fedora 28 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-8de33c103f

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

[Bug 1575520] abi-compliance-checker doesn't work under F28

[bugzilla]

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



--- Comment #15 from Fedora Update System  ---
abi-compliance-checker-2.2-3.fc28 has been pushed to the Fedora 28 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-8de33c103f

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

[Bug 1576617] perl-Net-HTTP-6.18 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
perl-Net-HTTP-6.18-1.fc28 has been pushed to the Fedora 28 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-9656824c88

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

[Bug 1575520] abi-compliance-checker doesn't work under F28

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #14 from Fedora Update System  ---
abi-compliance-checker-2.2-3.fc27 has been pushed to the Fedora 27 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-a727930b7f

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

[Bug 1576567] abi-compliance-checker: misses find dependency

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
abi-compliance-checker-2.2-3.fc27 has been pushed to the Fedora 27 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-a727930b7f

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

[Bug 1576617] perl-Net-HTTP-6.18 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
perl-Net-HTTP-6.18-1.fc27 has been pushed to the Fedora 27 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-0e3327b1d8

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

Re: "invalid path: ~/.fedora-server-ca.cert"

[Sérgio Basto]

On Fri, 2018-05-11 at 11:35 +0200, Tim Jackson wrote:
> Any pointers?

yeah  this one [1] and [2] more [3]

> [1]: https://fedoraproject.org/wiki/ReleaseEngineering/FlagDay2016


[2] https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb

[3] https://fedoraproject.org/wiki/Infrastructure/Kerberos



-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: "invalid path: ~/.fedora-server-ca.cert"

[Patrick マルタインアンドレアス Uiterwijk]

Hi,

You very likely have an /etc/koji.conf.rpmnew.
Could you please move that over /etc/koji.conf?
If not, maybe you have a ~/.koji, with custom config, you might need to remove.

If you have neither, can you make sure you have at least these package versions 
(from [1]):
 python2-cccolutils-1.4-1
fedpkg-1.26-2
fedora-packager-0.6.0.0-1
pyrpkg-1.47-3
koji-1.11.0-1

This custom CA has been entirely retired and unused for over a year, so some 
old configuration is still referring to it.

[1]: https://fedoraproject.org/wiki/ReleaseEngineering/FlagDay2016

Patrick
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2018-05-11)

[Stephen Gallagher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

===
#fedora-meeting: FESCO (2018-05-11)
===


Meeting started by sgallagh at 15:00:19 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting/2018-05-11/fesco.2018-05-11-15.00.log.html
.



Meeting summary
- ---
* init process  (sgallagh, 15:00:19)

* #1872 Disable Test Gating requirements until more UI is enabled
  (sgallagh, 15:05:08)
  * AGREED: turn bodhi gating back on, configure greenwave not to gate
all packages for now, allow opt-in for packagers when greenwave
supports it (+5, 0, -0)  (sgallagh, 15:16:00)
  * LINK:
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=a4bae0f
(threebean, 15:16:54)
  * AGREED: When devs think it's ready, opt-in some important
non-FESCo-member-maintained packages and get feedback for at least
50 updates before turning it back on globally.  (+6, 0, -0)
(sgallagh, 15:47:47)

* #1888 Non-responsive maintainer - Ivan Romanov  (sgallagh, 15:48:00)
  * AGREED: Move maintainership to xvitaly, keep ivanroman as
co-maintainer (+6, 0, -0)  (sgallagh, 15:51:51)

* #1889 F29 FESCo blocker: Module support in libdnf  (sgallagh,
  15:51:58)
  * AGREED: FESCo approves adamw's proposed criterion phrasing and asks
that it be included for Fedora 29 (+6, 0, -0)  (sgallagh, 15:54:50)

* #1891 Election Interview Questions - FESCo (May 2018)  (sgallagh,
  15:54:56)
  * LINK: https://pagure.io/fesco/issue/1805#comment-484891   (zbyszek,
15:56:36)
  * AGREED: Use same three questions from
https://pagure.io/fesco/issue/1805#comment-484891, but have election
wrangler ask people in the election announcement to ask question to
specific candidates on @devel if they want (+5, 0, -0)  (sgallagh,
16:02:04)

* Next week's chair  (sgallagh, 16:02:14)
  * ACTION: zbyszek to chair 2018-05-18 meeting  (sgallagh, 16:03:05)

* Open Floor  (sgallagh, 16:03:11)
  * LINK: https://pagure.io/fesco/issue/1890   (tyll, 16:09:19)

Meeting ended at 16:25:51 UTC.




Action Items
- 
* zbyszek to chair 2018-05-18 meeting




Action Items, by person
- ---
* zbyszek
  * zbyszek to chair 2018-05-18 meeting
* **UNASSIGNED**
  * (none)




People Present (lines said)
- ---
* bowlofeggs (146)
* sgallagh (100)
* zbyszek (39)
* nirik (37)
* tyll (34)
* zodbot (17)
* jsmith (11)
* threebean (9)
* dgilmore (2)
* jwb (0)
* maxamillion (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-BEGIN PGP SIGNATURE-
Version: Mailvelope v2.2.1
Comment: https://www.mailvelope.com

wkYEAREIABAFAlr1xMIJEHolVWI2uqOjAACbiQCcDxk1XrZkdTP7EwDRn2bc
JXXoP+IAnAiqnGJuENrAGKGg5gDDyN15+YJJ
=cgPu
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Intent to drop python2-notebook

[Miro Hrončok]

python2-notebook is a leaf package (nothing in Fedora (build)requires 
it). I'd like to drop it from rawhide. Any objections?


This **does not** affect the ability to run Jupyter Notebook (via the 
jupyter-notebook command) with Python 2 kernel (from the 
python2-ipykernel package).

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

libidn soname bump

[Miroslav Lichvar]

The libidn upstream has released 1.35, which increments the soname.
I'm planning to update the package on the next Tuesday.

The following packages will need to be rebuilt. I don't see anything
critical that should break the buildroot. Please let me know if that's
not the case.

certmonger-0.79.5-7.fc29
cone-0.96.2-3.fc28
echoping-6.1-0.7.beta.r434svn.fc28
eiskaltdcpp-2.2.11-13.20180207git6ca065b.fc29
freeDiameter-1.2.0-13.fc28
ghostscript-9.23-2.fc29   
gloox-1.0.14-5.fc27
hesiod-3.2.1-11.fc29
hydra-8.6-6.fc28
iris-1.0.0-0.32.20170212git8c2c9cb.fc28
jabberd-2.6.1-8.fc28
jreen-1.2.1-10.fc28
kopete-18.04.0-2.fc29
libgsasl-1.8.0-12.fc28
loudmouth-1.5.3-4.fc27
mcabber-1.1.0-1.fc29
monotone-1.1-25.fc28
perdition-2.1-7.fc26
perl-Net-LibIDN-0.12-29.fc28
pidgin-2.13.0-1.fc29
podofo-0.9.5-7.fc28
prosody-0.10.0-2.fc28
psi-plus-1.0-0.6.20170612git9.fc28
python-slixmpp-1.3.0-5.fc29
rubygem-idn-0.0.2-24.fc28
skipfish-2.10-0.16.b.fc28
swift-3.0-0.12.rc2.fc27
tgif-4.2.5-15.fc28
vacuum-im-1.3.0-0.8.20180214git01910e9.fc29

-- 
Miroslav Lichvar
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[389-devel] Re: Please review: Issue 49657 - Fix cascading replication scenario in lib389 API

[Simon Pichugin]

The issues mentioned by Mark were fixed.

On Thu, May 03, 2018 at 02:32:22PM +0200, Simon Pichugin wrote:
> Hi team,
> please, review:
> 
> https://pagure.io/389-ds-base/pull-request/49659
> https://pagure.io/389-ds-base/issue/49657
> 
> Thanks!
> Simon
> ___
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] please review: Ticket 49671 - Readonly replicas should not write internal ops to changelog

[Mark Reynolds]

https://pagure.io/389-ds-base/issue/49671

https://pagure.io/389-ds-base/pull-request/49672
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

Re: RPM spec style

[Nicolas Mailhot]

Le 2018-05-11 16:33, Merlin Mathesius a écrit :

Greetings.

I'd like a quick opinion on spec file style...

Nearly all specs I've seen dealing with subpackages group all the
%package/%description stanzas near the beginning, and put all the 
%files

stanzas near the the end. (Example 1 below)

However, are there any reasons, stylistic or otherwise, that the %files
stanzas shouldn't be grouped with their corresponding
%package/%description stanzas? (Example 2 below) Especially when there
are a large number of subpackages...


It's a lot easier to reventilate files between subpackages when a new 
version changes layout, if all the files sections are next to one 
another. Same for the descriptions. Hunting down description snippets do 
reflect one function was moved to or from another subpackage, is not 
fun.


--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RPM spec style

[Fernando Nasser]

On 2018-05-11 10:33 AM, Merlin Mathesius wrote:

Greetings.

I'd like a quick opinion on spec file style...

Nearly all specs I've seen dealing with subpackages group all the
%package/%description stanzas near the beginning, and put all the %files
stanzas near the the end. (Example 1 below)

However, are there any reasons, stylistic or otherwise, that the %files
stanzas shouldn't be grouped with their corresponding
%package/%description stanzas? (Example 2 below) Especially when there
are a large number of subpackages...


If you think of it, the usual order of spec file sections reflects the 
timing where they are used.


So you have the tags at the top, which are used to set things up, then 
preparation, building, installation and the list of files which is used 
firstly to verify if what was produced matches what you expect.


Granted, scriptlets like %pre %post etc. are grouped together so a 
general vision of hooks is given.


You could say the same about packages and their Descriptions being 
together.  It gives a whole vision of what this SRPM will produce.




Regards,
Fernando





Thanks.

Regards,

Merlin



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: "invalid path: ~/.fedora-server-ca.cert"

[Tim Jackson]

On 11/05/18 14:39, Chenxiong Qi wrote:

On Fri, May 11, 2018 at 5:35 PM, Tim Jackson  wrote:

As an example, today's error is something to do with logging
into Koji when running "fedpkg build":


For "fedpkg build", should just need "kinit [FAS username]@FEDORAPROJECT.ORG".


Thanks, but I've already (succesfully) done that and have something related to 
Koji:


$klist
[snip]
Valid starting ExpiresService principal
11/05/18 10:56:31  12/05/18 10:55:06 
host/koji.fedoraproject@fedoraproject.org

renew until 18/05/18 10:55:06

Tim
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

RPM spec style

[Merlin Mathesius]

Greetings.

I'd like a quick opinion on spec file style...

Nearly all specs I've seen dealing with subpackages group all the
%package/%description stanzas near the beginning, and put all the %files
stanzas near the the end. (Example 1 below)

However, are there any reasons, stylistic or otherwise, that the %files
stanzas shouldn't be grouped with their corresponding
%package/%description stanzas? (Example 2 below) Especially when there
are a large number of subpackages...

Thanks.

Regards,

Merlin


Example 1:

... preable ...

%description

%package server
%description server

%package client
%description client

%package lib
%description lib

%prep

%build

%install

%files

%files server

%files client

%files lib

%changelog
...


Example 2:

... preable ...

%description
%files

%package server
%description server
%files server

%package client
%description client
%files client

%package lib
%description lib
%files lib

%prep

%build

%install

%changelog
...

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Outage Report: EPEL 7 repository corruption problem

[Stephen John Smoogen]

Problem Description:

On 2018-05-11 04:00 UTC reports started coming into centos IRC
channels about EPEL being corrupted and causing breakages. These were
then reported to #fedora-admin and #epel-devel. The problem would show
up as something like:

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

The problem was examined and turned out to be that an NFS problem on
the backend systems causing the createrepo_c to create the
repositories to create a corrupted SQL file. A program which was to
catch this did not work for some reason still being investigated and
the corrupted sqllite file was mirrored out.

Admins began filling up the #epel and #centos channel asking why their
systems were broken. I would like to thank avij, tmz and others who
worked on answering as many of the people as possible.

Solution:

Because of the way mirroring works, this problem may affect clients
for hours after the fix has been made on the server. There are three
things a client can do:

1. If you have a dedicated mirror, have the mirror update itself with
the upstream mirrors.

2. On client systems you may need to do a 'yum clean all' in order to
remove the bad sql in case yum thinks it is still good to cache from.

3. You can skip yum on updates with:

yum --disablerepo=epel update


Further updates may occur as research is done.

-- 
Stephen J Smoogen.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: EPEL repository corrupted

[Stephen John Smoogen]

On 11 May 2018 at 09:34, Stephen John Smoogen  wrote:
>
>
> On 11 May 2018 at 02:43, Sandro Bonazzola  wrote:
>>
>> Hi,
>> this morning yum update complains with:
>>
>>  One of the configured repositories failed (Unknown),
>>  and yum doesn't have enough cached data to continue. At this point the
>> only
>>  safe thing yum can do is fail. There are a few ways to work "fix" this:
>
>
> We need a lot more information in the future. Which repository were you
> getting this with (EL6, EL7, EL5?) What mirror did you get this error with.
> How is the baseurl/metalink configured in your system that got this?

I have caught up with the goings on of last night and it turned out
there was a major problem. I will be putting out an announcement to
the lists shortly.


>
>
>
> --
> Stephen J Smoogen.
>



-- 
Stephen J Smoogen.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: Schedule for Friday's FESCo Meeting (2018-05-11)

[Randy Barlow]

On 05/11/2018 08:42 AM, Stephen Gallagher wrote:> = Followups =

I'd like us to discuss what the next steps are for:

#topic #1872 Disable Test Gating requirements until more UI is enabled
.fesco 1872
https://pagure.io/fesco/issue/1872



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: EPEL repository corrupted

[Stephen John Smoogen]

On 11 May 2018 at 02:43, Sandro Bonazzola  wrote:

> Hi,
> this morning yum update complains with:
>
>  One of the configured repositories failed (Unknown),
>  and yum doesn't have enough cached data to continue. At this point the only
>  safe thing yum can do is fail. There are a few ways to work "fix" this:
>
>
We need a lot more information in the future. Which repository were you
getting this with (EL6, EL7, EL5?) What mirror did you get this error with.
How is the baseurl/metalink configured in your system that got this?




-- 
Stephen J Smoogen.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[Bug 1570371] perl-DateTime-Tiny-1.07 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||jples...@redhat.com
   Fixed In Version||perl-DateTime-Tiny-1.07-1.f
   ||c29
 Resolution|--- |RAWHIDE
   Assignee|robinlee.s...@gmail.com |jples...@redhat.com
Last Closed||2018-05-11 08:57:12



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

[rpms/perl-DateTime-Tiny] New Commits To "rpms/perl-DateTime-Tiny" (master)

[pagure]

The following commits were pushed to the repo rpms/perl-DateTime-Tiny on branch
master, which you are following:
d7215e036f4d5f9abf6ba1347d36884a49089fc6Jitka Plesnikova1.07 bump



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-DateTime-Tiny/commits/master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2018-05-11)

[Stephen Gallagher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting onirc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2018-05-11 15:00 UTC'


Links to all issues below can be found
at:https://pagure.io/fesco/report/meeting_agenda

= Followups =

= New business =

#topic #1888 Non-responsive maintainer - Ivan Romanov
.fesco 1888https://pagure.io/fesco/issue/1888

#topic #1889 F29 FESCo blocker: Module support in libdnf
.fesco 1889https://pagure.io/fesco/issue/1889

#topic #1891 Election Interview Questions - FESCo (May 2018)
.fesco 1891https://pagure.io/fesco/issue/1891



= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found
athttps://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue athttps://pagure.io/fesco,
e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
-BEGIN PGP SIGNATURE-
Version: Mailvelope v2.2.1
Comment: https://www.mailvelope.com

wkYEAREIABAFAlr1j8wJEHolVWI2uqOjAACwqQCfaI0i1qbxtqPWBm5pNQ5X
bB/H2isAniet6bwRTi+acIIkt+X6Lv+s1k0g
=e/p3
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Release rpkg-1.54

[Chenxiong Qi]

Hi all,

A new version rpkg-1.54  is released.

Changelog

- Pass the -s/--set-default-stream to mbs-manager for module local
builds. (jkaluza)
- Write mock config correctly when run in Py 3 (cqi)
- Add --with and --without options to 'local' - rhbz#1533416 (tmz)
- Add a test for 3f93433 (cqi)
- Raise error if rpm command returns non-zero (cqi)
- Use getpass.getuser() instead of pwd.getpwuid(os.getuid())[0] (jpopelka)
- Allow setting custom MBS config file and config section in
rpkg.conf. (jkaluza)
- Remove py35 testenv (cqi)
- Ignore .env and tags (cqi)
- Remove question mark from giturl (cqi)
- Added custom ArgumentParser (supports allow_abbrev) (jkucera)
- Grab the correct first line in case of rpm output (zebob.m)

rpkg is available from PyPI.

Bodhi updates: https://bodhi.fedoraproject.org/updates/?packages=rpkg

-- 
Regards,
Chenxiong Qi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: "invalid path: ~/.fedora-server-ca.cert"

[Chenxiong Qi]

On Fri, May 11, 2018 at 5:35 PM, Tim Jackson  wrote:
> As an infrequent contributor, I have unfortunately had to resign myself to
> the fact that every time I try to make a change to a package, something has
> broken/changed, and thus 95% of the time goes on fixing the environment and
> 5% on the package in question. However, I do wonder whether, when
> refactoring the tooling, some improvements could be made to error handling
> and reporting.  As an example, today's error is something to do with logging
> into Koji when running "fedpkg build":

For "fedpkg build", should just need "kinit [FAS username]@FEDORAPROJECT.ORG".

>
> Kerberos authentication fails: Could not find a suitable TLS CA certificate
> bundle, invalid path: ~/.fedora-server-ca.cert
> Could not execute build: Could not login to
> http://koji.fedoraproject.org/kojihub
>
> Firstly, could the error message "invalid path: ~/.fedora-server-ca.cert" be
> improved? There _is_ a CA certificate in that location, untouched since
> August 2014. As far as I can tell it's still valid (at least it's not
> expired according to "openssl x509 -text <~/.fedora-server-ca.cert"). What's
> suddenly "invalid" about it now? ("-d" doesn't provide any additional
> information). It would be really helpful, especially to us less-frequent
> packagers, if the error message could give a clue what might be wrong or how
> to solve it.
>
> Trying to be constructive, I thought maybe fedora-packager-setup or
> fedora-cert might give me some more info. However...
>
> $ fedora-packager-setup
> Setting up Fedora packager environment
> Traceback (most recent call last):
>   File "/usr/bin/fedora-packager-setup", line 123, in 
> main()
>   File "/usr/bin/fedora-packager-setup", line 103, in main
> if fedora_cert.certificate_expired():
>   File "/usr/lib/python2.7/site-packages/fedora_cert/__init__.py", line 83,
> in certificate_expired
> if my_cert.has_expired():
> AttributeError: 'NoneType' object has no attribute 'has_expired'
>
> $ fedora-cert
> Traceback (most recent call last):
>   File "/usr/bin/fedora-cert", line 85, in 
> main(opts)
>   File "/usr/bin/fedora-cert", line 52, in main
> if fedora_cert.certificate_expired():
>   File "/usr/lib/python2.7/site-packages/fedora_cert/__init__.py", line 83,
> in certificate_expired
> if my_cert.has_expired():
> AttributeError: 'NoneType' object has no attribute 'has_expired'
>
>
> This seems to be a >1 year old bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1412260
>
> If I remove ~/.fedora.upn (why?) and re-run fedora-packager-setup, I
> apparently get a new ~/.fedora-server-ca.cert, but the mysterious "invalid
> path" error remains.
>
> Any pointers?
>
> Thanks
>
> Tim
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org



-- 
Regards,
Chenxiong Qi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1570263] perl-Config-IniFiles-2.98 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||jples...@redhat.com
   Fixed In Version||perl-Config-IniFiles-2.98-1
   ||.fc29
 Resolution|--- |RAWHIDE
   Assignee|tcall...@redhat.com |jples...@redhat.com
Last Closed||2018-05-11 08:09:03



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

[rpms/perl-Config-IniFiles] New Commits To "rpms/perl-Config-IniFiles" (master)

[pagure]

The following commits were pushed to the repo rpms/perl-Config-IniFiles on 
branch
master, which you are following:
050c7aae81970e8668016f0270b29012daf1fee7Jitka Plesnikova2.98 bump



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-Config-IniFiles/commits/master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[rpms/perl-ExtUtils-InstallPaths] New Commits To "rpms/perl-ExtUtils-InstallPaths" (master)

[pagure]

The following commits were pushed to the repo rpms/perl-ExtUtils-InstallPaths 
on branch
master, which you are following:
81ffa3951ca719dff5014e244ef0440bce904672Paul HowarthUpdate to 0.012



To view more about the commits, visit:
https://src.fedoraproject.org/rpms/perl-ExtUtils-InstallPaths/commits/master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

"invalid path: ~/.fedora-server-ca.cert"

[Tim Jackson]

As an infrequent contributor, I have unfortunately had to resign myself to the 
fact that every time I try to make a change to a package, something has 
broken/changed, and thus 95% of the time goes on fixing the environment and 5% 
on the package in question. However, I do wonder whether, when refactoring the 
tooling, some improvements could be made to error handling and reporting.  As 
an example, today's error is something to do with logging into Koji when 
running "fedpkg build":


Kerberos authentication fails: Could not find a suitable TLS CA certificate 
bundle, invalid path: ~/.fedora-server-ca.cert

Could not execute build: Could not login to 
http://koji.fedoraproject.org/kojihub

Firstly, could the error message "invalid path: ~/.fedora-server-ca.cert" be 
improved? There _is_ a CA certificate in that location, untouched since August 
2014. As far as I can tell it's still valid (at least it's not expired 
according to "openssl x509 -text <~/.fedora-server-ca.cert"). What's suddenly 
"invalid" about it now? ("-d" doesn't provide any additional information). It 
would be really helpful, especially to us less-frequent packagers, if the 
error message could give a clue what might be wrong or how to solve it.


Trying to be constructive, I thought maybe fedora-packager-setup or 
fedora-cert might give me some more info. However...


$ fedora-packager-setup
Setting up Fedora packager environment
Traceback (most recent call last):
  File "/usr/bin/fedora-packager-setup", line 123, in 
main()
  File "/usr/bin/fedora-packager-setup", line 103, in main
if fedora_cert.certificate_expired():
  File "/usr/lib/python2.7/site-packages/fedora_cert/__init__.py", line 83, 
in certificate_expired

if my_cert.has_expired():
AttributeError: 'NoneType' object has no attribute 'has_expired'

$ fedora-cert
Traceback (most recent call last):
  File "/usr/bin/fedora-cert", line 85, in 
main(opts)
  File "/usr/bin/fedora-cert", line 52, in main
if fedora_cert.certificate_expired():
  File "/usr/lib/python2.7/site-packages/fedora_cert/__init__.py", line 83, 
in certificate_expired

if my_cert.has_expired():
AttributeError: 'NoneType' object has no attribute 'has_expired'


This seems to be a >1 year old bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=1412260


If I remove ~/.fedora.upn (why?) and re-run fedora-packager-setup, I 
apparently get a new ~/.fedora-server-ca.cert, but the mysterious "invalid 
path" error remains.


Any pointers?

Thanks

Tim
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[389-devel] Re: lib389 usage cheatsheet

[Simon Pichugin]

Hi Thierry,
I agree with you, it was exactly my proposition :)

Keeping main python-ldap elements is important because we don't want
to implement or mask/wrap this basic functionality (like working with controls, 
etc)
we just want to redirect them.

Ideally, we should make our admin library very intuitive for the people
who already knows python-ldap and just LDAP concepts.

I will continue adding more information to the docs regarding DSLdapObject
and I'll try to make it a bit closer to LDAP concepts (at least in
wording), I already have something in mind.

Thanks,
Simon


On Wed, May 09, 2018 at 06:12:33PM +0200, thierry bordaz wrote:
>Hi Simon,
> 
>  Thanks Simon starting this thread :)
>  Currently lib389 is mostly used by ldap devel/QE and seems realistic
>  to become the admin library (for example used by freeipa or others)
>  and component of 389 administrative tools. LDAP knowledge is a
>  requirement for all of them. In that sense, lib389 should continue
>  to follow/offer basic LDAP elements (connections, naming_ctx,
>  req/resp, synchronous/asynchronous, extop, control...).
>  I agree that those elements are a bit frustrating for people wanting
>  to use LDAP as a simple repository. The DSLdapObject abrstaction
>  looks very promising. It can be oriented to simple use case: create
>  users and groups, manage memberships, authentication/rights,
>  automatic deployement on several replicated instances. Then extended
>  on demand.
>  In short, IMHO I would prefer to keep the most of the LDAP elements
>  (option 1) and propose/extend easy POC interface (option 2). I am
>  not sure the work DSLdapObject is my favorite, we could name it
>  according to the use case we want to propose.
>  For me option 3 will be the worse option. I remember an abstraction
>  layer that had a so high level that I constantly looked at the
>  access/error log, to be sure that the program was doing what I was
>  thinking it should.
>  best regards
>  thierry
> 
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[EPEL-devel] Re: EPEL repository corrupted

[Anssi Johansson]

Sandro Bonazzola kirjoitti 11.5.2018 klo 9.43:

Hi,
this morning yum update complains with:

  One of the configured repositories failed (Unknown),
  and yum doesn't have enough cached data to continue. At this point the only
  safe thing yum can do is fail. There are a few ways to work "fix" this:

  1. Contact the upstream for the repository and get them to fix the 
problem.

  2. Reconfigure the baseurl/etc. for the repository, to point to a working
 upstream. This is most often useful if you are using a newer
 distribution release than is supported by the repository (and the
 packages for the previous distribution release still work).

  3. Run the command with the repository temporarily disabled
 yum --disablerepo= ...

  4. Disable the repository permanently, so yum won't use it by default. Yum
 will then just ignore the repository until you permanently enable it
 again or use --enablerepo for temporary usage:

 yum-config-manager --disable 
 or
 subscription-manager repos --disable=

  5. Configure the failing repository to be skipped, if it is unavailable.
 Note that yum will try to contact the repo. when it runs most commands,
 so will have to try and fail each time (and thus. yum will be be much
 slower). If it is a very temporary problem though, this is often a nice
 compromise:

 yum-config-manager --save 
--setopt=.skip_if_unavailable=true

file is encrypted or is not a database


Can you please regenerate metadata?


As far as I can see, this has now been fixed. 
http://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/ has a working 
primary.sqlite.bz2 and it is currently being synced to mirrors. The 
usual "yum clean all" or adjusting baseurl tricks may help in the meantime.

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] EPEL repository corrupted

[Sandro Bonazzola]

Hi,
this morning yum update complains with:

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

 5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

file is encrypted or is not a database


Can you please regenerate metadata?
Thanks
-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

sbona...@redhat.com


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org