[Bug 1509104] New: package request for perl-RPM2, or rpm-perl; providing RPM[2].pm

https://bugzilla.redhat.com/show_bug.cgi?id=1509104 Bug ID: 1509104 Summary: package request for perl-RPM2, or rpm-perl; providing RPM[2].pm Product: Fedora EPEL Version: epel7 Component: perl-RPM2 Assignee:

[Test-Announce] Fedora 27 Candidate RC-1.3 Available Now!

According to the schedule [1], Fedora 27 Candidate RC-1.3 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the

Fedora Modular 27 compose report: 20171103.n.0 changes

OLD: Fedora-Modular-27-20171102.n.1 NEW: Fedora-Modular-27-20171103.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 2 Dropped packages:1 Upgraded packages: 8 Downgraded packages: 4 Size of added packages: 5.49 MiB Size of dropped packages

Re: bodhi CLI and USERNAME

On 10/19/2017 04:52 PM, Cole Robinson wrote: > Maybe just switch the stable > branches back to FAS_USERNAME which avoids the GDM issue Thanks for the thougtful reply Cole! I've filed an issue to follow your suggestion here: https://bugzilla.redhat.com/show_bug.cgi?id=1509094 signature.asc

[389-devel] revised: Ticket 48393 - Improve replication configuration validation

https://pagure.io/389-ds-base/issue/raw/files/28c932acf4a8d53b1d29eb40ba83e773d145bcae7f6790ab2dd5b5b6f3fa3a2f-0001-Ticket-48393-Improve-replication-config-validation.patch On 10/31/2017 09:42 AM, Mark Reynolds wrote: > > > > Forwarded Message > Subject: [389-devel]

Re: Minor schedule procedure tweak (rain dates and such)

On Thu, Nov 02, 2017 at 04:40:30PM -0400, John Florian wrote: > Call me crazy, I don't mind, but what about scheduling the release > dates in reverse, using whatever naming scheme? Then as the release is > finalized, we either stick to the last release date if there were lots > of "slips" or we

[EPEL-devel] Re: ansible1.9 package

On 11/02/2017 11:03 AM, Peter Rex wrote: > Thanks for the info, Ricardo. Hadn't found the retirement notice. Security, > I guess. I can't resist saying, though, that I regret using Ansible and my > assumption that one of the Es in EPEL stood for Enterprise. Oh well, live > and learn. Sorry things

Re: Minor schedule procedure tweak (rain dates and such)

Call me crazy, I don't mind, but what about scheduling the release dates in reverse, using whatever naming scheme? Then as the release is finalized, we either stick to the last release date if there were lots of "slips" or we select an earlier release date because things went really well. This

Fedora 27 Server Beta status (4th round) is NO-GO

Due to missing RC for the F27 Server Beta release the release status of the Fedora 27 Server Beta is NO-GO. The next Go/No-Go meeting is planned on Thursday, November 9th. The F27 Server Beta release slips for one week on 2017-Nov-14. The slip also affects the F27 Server GA and it moves to

Fedora 27 Server Beta status (4th round) is NO-GO

Due to missing RC for the F27 Server Beta release the release status of the Fedora 27 Server Beta is NO-GO. The next Go/No-Go meeting is planned on Thursday, November 9th. The F27 Server Beta release slips for one week on 2017-Nov-14. The slip also affects the F27 Server GA and it moves to

Minor schedule procedure tweak (rain dates and such)

It turns out that the "Rain Date" concept is confusing to some people (particularly where that idiom is not familiar). I propose that for F28 and onward, we keep the basic concept, but ditch that term. Instead, we use: * Release Date Target 1 * Release Date Target 2 (a week later). As now, these

Re: Schedule for Friday's FESCo Meeting (2017-11-03)

There is one more issue I would like to ask FESCo to review: #topic Proposal for 3 week freeze .fesco 1790 https://pagure.io/fesco/issue/1790 Thanks, Jan On Thu, Nov 2, 2017 at 8:28 PM, Adam Miller wrote: > Following is the list of topics that will be discussed

[EPEL-devel] Re: ansible1.9 package

El Jueves 02/11/2017 a las 15:03, Peter Rex escribió: > Thanks for the info, Ricardo. Hadn't found the retirement notice. Security, > I guess. I can't resist saying, though, that I regret using Ansible and my > assumption that one of the Es in EPEL stood for Enterprise. Oh well, live > and learn.

Schedule for Friday's FESCo Meeting (2017-11-03)

Following is the list of topics that will be discussed in the FESCo meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2017-11-03 16:00 UTC' Links to all issues below

Fedora 27-20171102.n.0 compose check report

Missing expected images: Workstation live i386 Kde live i386 Failed openQA tests: 10/137 (x86_64), 1/22 (i386), 1/2 (arm) New failures (same test did not fail in 27-20171101.n.0): ID: 164735 Test: x86_64 Workstation Ostree-dvd_ostree-iso desktop_browser URL:

Fedora Rawhide-20171102.n.0 compose check report

Missing expected images: Server dvd i386 Workstation live i386 Server boot i386 Kde live i386 Failed openQA tests: 15/128 (x86_64), 1/2 (arm) New failures (same test did not fail in Rawhide-20171101.n.2): ID: 164516 Test: x86_64 Server-dvd-iso server_cockpit_basic URL:

[EPEL-devel] Re: ansible1.9 package

On 2 November 2017 at 14:03, Peter Rex wrote: > Thanks for the info, Ricardo. Hadn't found the retirement notice. Security, > I guess. I can't resist saying, though, that I regret using Ansible and my > assumption that one of the Es in EPEL stood for Enterprise. Oh well, live

Fedora Modular bikeshed compose report: 20171026.n.0 changes

OLD: Fedora-Modular-Bikeshed-20171026.n.0 NEW: Fedora-Modular-Bikeshed-20171026.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0.00 B Size of dropped

[EPEL-devel] Re: ansible1.9 package

Thanks for the info, Ricardo. Hadn't found the retirement notice. Security, I guess. I can't resist saying, though, that I regret using Ansible and my assumption that one of the Es in EPEL stood for Enterprise. Oh well, live and learn. On Thu, Nov 2, 2017 at 9:28 AM, Ricardo J. Barberis

No vtkGUISupportQtOpenGL in fedora?

Dear all, I was wondering if anyone knows why vtkGUISupportQtOpenGL is not included in packaged vtk. Other classes with opengl(2) are available. Thanks and regards, Mario ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

Re: [HEADS-UP] cryptsetup-2.0.0-rc1 - libcryptsetup soname bump

Most of the below packages are mine. I'm fine with this rebuild. I will retire deo as upstream (me) is dead. On Thu, Nov 2, 2017 at 6:17 AM, Ondrej Kozina wrote: > Hi again, > > just brief update with some tests before the soname bump takes effect. > > I've tested rebuilds of

[389-devel] please review: Ticket 49439 - cleanallruv task is not logging information

https://pagure.io/389-ds-base/issue/49439 https://pagure.io/389-ds-base/issue/raw/files/f8ce257c8c7e5f03b6b4dafb127ec86eba88dc9d9d387e35866c9144182abc1e-0001-Ticket-49439-cleanallruv-is-not-logging-information.patch ___ 389-devel mailing list --

Fedora Modular 27 compose report: 20171102.n.1 changes

OLD: Fedora-Modular-27-20171102.n.0 NEW: Fedora-Modular-27-20171102.n.1 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0.00 B Size of dropped packages

Re: Broken dependencies: rubygem-elasticsearch

Dne 2.11.2017 v 16:59 Sandro Bonazzola napsal(a): > > > 2017-11-02 16:55 GMT+01:00 Vít Ondruch >: > > It seem your package requires 2.0.2 version of > elasticsearch-transport, while in F28, there is >

Re: Broken dependencies: rubygem-elasticsearch

2017-11-02 16:55 GMT+01:00 Vít Ondruch : > It seem your package requires 2.0.2 version of elasticsearch-transport, > while in F28, there is rubygem-elasticsearch-transport-5.0.4-1.fc28 > > The question is how to solve it. I'd start by trying to relax the > dependnecy using

Re: Broken dependencies: rubygem-elasticsearch

It seem your package requires 2.0.2 version of elasticsearch-transport, while in F28, there is rubygem-elasticsearch-transport-5.0.4-1.fc28 The question is how to solve it. I'd start by trying to relax the dependnecy using %gemspec_remove_dep and %gemspec_add_dep macros. Vít Dne 2.11.2017 v

Re: Broken dependencies: rubygem-elasticsearch

2017-11-02 14:16 GMT+01:00 : I built the new version 5.0.4 this morning[1], any idea on why this is still failing? I tried un-tagging the previous build just in case it was the root issue but didn't work: $ koji untag-build f28 rubygem-elasticsearch-2.0.2-1.fc28

[EPEL-devel] Re: ansible1.9 package

El Miércoles 01/11/2017 a las 23:58, Peter Rex escribió: > Is gone. Any particular reason? Yep, mostly security vulnerabilities and 2.x being available, check out these threads for more info:

Re: Building of OkHttp 3.9.0 fails

%pom_disable_plugin isn't a existing command, but %pom_remove_plugin is a existing macro, that i have already in the spec file. %pom_remove_plugin org.codehaus.mojo:animal-sniffer-maven-plugin ___ devel mailing list -- devel@lists.fedoraproject.org To

Re: [HEADS-UP] unannounced libfastjson ABI change breaks rsyslog

On Thu, Nov 02, 2017 at 07:52:25AM +, Radovan Sroka wrote: > Hi Guys, > > libfastjson is rsyslog specific library. So it should break anything else. > I did a mistake because I didn't group updates for libfastjson and for > rsyslog. Rsyslog was broken yesterday on fedora 26 but now it should

Re: Building of OkHttp 3.9.0 fails

i added the mentioned line, but the compilation fails. # Plugin prevents build /usr/bin/python3 /usr/share/java-utils/pom_editor.py pom_remove_plugin org.codehaus.mojo:animal-sniffer-maven-plugin # disabling animal-sniffer %pom_disable_plugin :animal-sniffer-maven-plugin ...

Fedora rawhide compose report: 20171102.n.0 changes

OLD: Fedora-Rawhide-20171101.n.2 NEW: Fedora-Rawhide-20171102.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 0 Dropped packages:1 Upgraded packages: 45 Downgraded packages: 0 Size of added packages: 0.00 B Size of dropped packages:123.49

Re: Review Swaps

Can I swap you for this one (R colourscheme generator): R-RColorBrewer - Provides color schemes for maps (and other graphics) https://bugzilla.redhat.com/show_bug.cgi?id=1504825 On 1 November 2017 at 15:55, Richard Shaw wrote: > I have a few simple C++ based review

Re: Building of OkHttp 3.9.0 fails

On 11/02/2017 01:33 PM, Martin Gansser wrote: > maybe i'am wrong, i have added this 3 lines to delete the sample modules. > > %pom_disable_module guide samples > %pom_disable_module simple-client samples > %pom_disable_module slack samples > > the package build breaking at the end ... > [1]

Re: Building of OkHttp 3.9.0 fails

maybe i'am wrong, i have added this 3 lines to delete the sample modules. %pom_disable_module guide samples %pom_disable_module simple-client samples %pom_disable_module slack samples the package build breaking at the end ... [1] https://martinkg.fedorapeople.org/Packages/okhttp3/okhttp.spec [2]

[Bug 1508865] New: perl-Log-Report-1.23 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1508865 Bug ID: 1508865 Summary: perl-Log-Report-1.23 is available Product: Fedora Version: rawhide Component: perl-Log-Report Keywords: FutureFeature, Triaged Assignee:

Re: [HEADS-UP] unannounced libfastjson ABI change breaks rsyslog

On Thursday, 02 November 2017 at 08:52, Radovan Sroka wrote: [...] > libfastjson is rsyslog specific library. So it shouldn't break anything else. A quick repoquery reveals one more consumer at least on F26: # dnf repoquery --whatrequires "libfastjson.so.4()(64bit)"

Re: [HEADS-UP] unannounced libfastjson ABI change breaks rsyslog

On Thursday, 02 November 2017 at 04:36, Troy Curtis Jr wrote: [...] > I'm not sure if it is a real issue or not. A user in #fedora got bit by > this where his rsyslog was upgraded but not his libfastjson. Updating to > libfastjson-0.99.7 allowed rsyslog to startup and begin logging. But it >

Re: Building of OkHttp 3.9.0 fails

On 11/02/2017 10:31 AM, Martin Gansser wrote: > Hi, > > i just took the old patch from okhttp2 and port it to okhttp3. Then it makes sense, looks like Platform.java was splitted into several smaller files. > Now i have updated okio to 1.13.0 on my local machine and took your patch. > > the

Re: [HEADS-UP] cryptsetup-2.0.0-rc1 - libcryptsetup soname bump

Hi again, just brief update with some tests before the soname bump takes effect. I've tested rebuilds of packages depending on libcryptsetup with following results. Basically there's only volume_key package that breaks: clevis-udisks2-0:6-3.fc27.x86_64 Rebuild passed with no issues.

Re: Building of OkHttp 3.9.0 fails

Hi, i just took the old patch from okhttp2 and port it to okhttp3. Now i have updated okio to 1.13.0 on my local machine and took your patch. the compilation breaks now at Sample: Guide [1] https://martinkg.fedorapeople.org/Packages/okhttp3/okhttp.spec [2]

[Bug 1508765] New: perl-XML-Atom-SimpleFeed-0.902 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1508765 Bug ID: 1508765 Summary: perl-XML-Atom-SimpleFeed-0.902 is available Product: Fedora Version: rawhide Component: perl-XML-Atom-SimpleFeed Keywords: FutureFeature, Triaged

Re: [HEADS-UP] unannounced libfastjson ABI change breaks rsyslog

"So it shouldn't break anything else." On Thu, Nov 2, 2017 at 8:52 AM Radovan Sroka wrote: > Hi Guys, > > libfastjson is rsyslog specific library. So it should break anything else. > I did a mistake because I didn't group updates for libfastjson and for > rsyslog. Rsyslog was

Re: [HEADS-UP] unannounced libfastjson ABI change breaks rsyslog

Hi Guys, libfastjson is rsyslog specific library. So it should break anything else. I did a mistake because I didn't group updates for libfastjson and for rsyslog. Rsyslog was broken yesterday on fedora 26 but now it should be everything OK. I will be really careful with other branches and also

Re: Remove old GPG keys?

On 11/01/2017 10:37 PM, Kevin Fenzi wrote: On 11/01/2017 01:07 PM, Christopher wrote: On Wed, Nov 1, 2017 at 3:26 PM Kevin Fenzi wrote: On 10/31/2017 01:08 PM, Christopher wrote: [...] I personally don't see much advantage in expiring old keys or the like. The only attack