[Bug 1724169] Missing MPLv2.0 in License

https://bugzilla.redhat.com/show_bug.cgi?id=1724169 Petr Pisar changed: What|Removed |Added Blocks|1632600 | -- You are receiving this mail

[Bug 1724169] Missing MPLv2.0 in License

https://bugzilla.redhat.com/show_bug.cgi?id=1724169 --- Comment #2 from Petr Pisar --- > -# openssl for Test-client-performs-Post-Handshake-Authentication.patch > -BuildRequires: openssl This was there because of /usr/bin/openssl tool. I can see you already have had "openssl >= 0.9.8". Should

Re: wpa supplicant using /dev/random

On Thu, Jun 6, 2019 at 4:03 AM Tomas Mraz wrote: > > On Wed, 2019-06-05 at 16:38 -0600, Chris Murphy wrote: > > Jun 05 15:53:25 fmac.local kernel: random: crng init done > > Jun 05 15:53:25 fmac.local kernel: random: 7 urandom warning(s) > > missed > > due to ratelimiting > > Jun 05 15:53:25

[Bug 1723904] perl-FFI-CheckLib-0.25 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1723904 --- Comment #5 from Fedora Update System --- perl-FFI-CheckLib-0.25-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See

[389-devel] 389 DS nightly 2019-06-27 - 96% PASS

https://fedorapeople.org/groups/389ds/ci/nightly/2019/06/27/report-389-ds-base-1.4.1.4-20190626git71138c0.fc30.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

[Bug 1723904] perl-FFI-CheckLib-0.25 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1723904 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #4 from

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

The following Fedora EPEL 7 Security updates need testing: Age URL 316 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 91 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294 cinnamon-3.6.7-5.el7 84

[Bug 1721217] perl-String-Compare-ConstantTime-0.321 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1721217 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In

Re: Fedora 31 System-Wide Change proposal: Python means Python3

On Wed, 2019-06-26 at 21:13 +0100, José Abílio Matos wrote: > On Wednesday, 26 June 2019 19.07.27 WEST Adam Williamson wrote: > > Oh, man. I thought we'd decided against this in the past? I'm worried > > about the cost/benefit ratio on such a change. > > If this were only related with python I

Re: [HEADS UP] Unannounced soname bump of qrencode

mcatanz...@gnome.org wrote: > > Let's ensure this at least doesn't happen for the same library again > and again. > > In [1], change SHOULD NOT -> MUST NOT. > > Require maintainers (or provenpackagers) to fix violations like [2] > when unannounced soname bumps occur. Then may be worth

always update the bootloader during major upgrades

Hi, This is not a formal proposal, this is for discussion and identifying liabilities. This email has an x86 GRUB bias only because that's the bootloader regime I'm most familiar with. I think it should apply to other archs as well, i.e. their bootloaders shouldn't be permitted to become stale.

Re: Fedora 31 System-Wide Change proposal: Python means Python3

On Wednesday, 26 June 2019 19.07.27 WEST Adam Williamson wrote: > Oh, man. I thought we'd decided against this in the past? I'm worried > about the cost/benefit ratio on such a change. If this were only related with python I would agree with you. Yet this also applies to lots of other tools like

Re: Fedora 31 System-Wide Change proposal: Python means Python3

On Wed, 2019-06-26 at 13:57 -0400, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/Python_means_Python3 > > == Summary == > In package and command names, "Python" will mean "Python 3". > > Users installing and running Python or Python packages without > specifying a version will get

Fedora 31 System-Wide Change proposal: Python means Python3

https://fedoraproject.org/wiki/Changes/Python_means_Python3 == Summary == In package and command names, "Python" will mean "Python 3". Users installing and running Python or Python packages without specifying a version will get Python 3. Running python will run python3. Running pytest will run

Fedora 31 System-Wide Change proposal: Python means Python3

https://fedoraproject.org/wiki/Changes/Python_means_Python3 == Summary == In package and command names, "Python" will mean "Python 3". Users installing and running Python or Python packages without specifying a version will get Python 3. Running python will run python3. Running pytest will run

Planned Outage - fedoraproject.org/wiki - 2019-06-27 21:00 UTC

Planned Outage - fedoraproject.org/wiki - 2019-06-27 21:00 UTC There will be an outage starting at 2019-06-27 21:00 UTC , which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-06-27

Planned Outage - fedoraproject.org/wiki - 2019-06-27 21:00 UTC

Planned Outage - fedoraproject.org/wiki - 2019-06-27 21:00 UTC There will be an outage starting at 2019-06-27 21:00 UTC , which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-06-27

Re: Fedora 31 Self-Contained Change proposal: Include several modules in the EFI build of Grub2 for security use-cases

Hi all, I've written some scripts to help with the signature verification aspect of this change. I've attempted to have them seamlessly handle different environments, but please let me know if you observe any misbehaviour. I'd particularly like to get input on the second script. The first can

Re: adding speech installation to fedora network installation image

On Wed, 26 Jun 2019 14:26:14 +0200 Mmobilea wrote: > Hello, > I’m new blind user of fedora 30. I couldn’t find where to post this > request. I have small pendrive, and I must use network installer. > Howewer orca or speakup doesn’t run on it. Could you add speech to > the installer? Sorry for my

Final reminder: F31 Change proposals that require infra changes due today

If you have a Change proposal that requires changes to Infrastructure, those proposals must be submitted (i.e. in ChangeReadyForWrangler category) today, 26 June. Other deadlines approaching: * 2019-07-02 — Changes requiring mass rebuild * 2019-07-02 — System-Wide changes * 2019-07-23 —

Final reminder: F31 Change proposals that require infra changes due today

If you have a Change proposal that requires changes to Infrastructure, those proposals must be submitted (i.e. in ChangeReadyForWrangler category) today, 26 June. Other deadlines approaching: * 2019-07-02 — Changes requiring mass rebuild * 2019-07-02 — System-Wide changes * 2019-07-23 —

Re: Bootstrapped Packages

Thank you all for your offers of help. I got pinged on IRC and got help from besser82 which when combined with what I've heard from churchyard in the past and the commits that Vit cited made it make sense. I've submitted a PR https://pagure.io/packaging-committee/pull-request/910 to the

[Bug 1724169] Missing MPLv2.0 in License

https://bugzilla.redhat.com/show_bug.cgi?id=1724169 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version|

Re: [HEADS UP] Unannounced soname bump of qrencode

On Wed, 26 Jun 2019 at 11:02, Jerry James wrote: > On Wed, Jun 26, 2019 at 4:01 AM Miro Hrončok wrote: > > $ rg -lF '.so*' rpm-specs/ | env LANG=en_US.utf8 sort > > [snip] > > > rpm-specs/coin-or-Ipopt.spec > > I am planning to fix this one soon as part of a general revamping of > all of the

Re: [HEADS UP] Unannounced soname bump of qrencode

On Wed, Jun 26, 2019 at 04:34:00PM +0200, Miro Hrončok wrote: > On 26. 06. 19 16:16, Jerry James wrote: > >On Wed, Jun 26, 2019 at 4:01 AM Miro Hrončok wrote: > >>$ rg -lF '.so*' rpm-specs/ | env LANG=en_US.utf8 sort > > > >[snip] > > > >>rpm-specs/coin-or-Ipopt.spec > > > >I am planning to fix

Re: [HEADS UP] Unannounced soname bump of qrencode

On 26. 06. 19 16:16, Jerry James wrote: On Wed, Jun 26, 2019 at 4:01 AM Miro Hrončok wrote: $ rg -lF '.so*' rpm-specs/ | env LANG=en_US.utf8 sort [snip] rpm-specs/coin-or-Ipopt.spec I am planning to fix this one soon as part of a general revamping of all of the coin-or-* packages. But

Re: Fedora 31 System-Wide Change proposal: No More i686 Kernels

Le 2019-06-26 16:07, Josh Boyer a écrit : On Wed, Jun 26, 2019 at 9:24 AM Roberto Ragusa wrote: On 6/26/19 2:34 AM, Michal Schorm wrote: > I - and a people around me - have plenty of 32-bit hardware. Just for the record, I've got a couple of AMD XP2400+, AMD XP2000+ machines, updated to

Re: Please update form pep8 to pycodestyle

On Wednesday, 26 June 2019 13.03.44 WEST Vít Ondruch wrote: > I agree with the "# Stop linting code in %%check and measuring coverage, > this is upstream's business" reasoning. Shouldn't we mention that > somewhere in guidelines? > > > Vít The funny part is that this consideration applies to

Re: [HEADS UP] Unannounced soname bump of qrencode

On Wed, Jun 26, 2019 at 4:01 AM Miro Hrončok wrote: > $ rg -lF '.so*' rpm-specs/ | env LANG=en_US.utf8 sort [snip] > rpm-specs/coin-or-Ipopt.spec I am planning to fix this one soon as part of a general revamping of all of the coin-or-* packages. But I'm curious. Why is this the only one to

Re: Fedora 31 System-Wide Change proposal: No More i686 Kernels

On Wed, Jun 26, 2019 at 9:24 AM Roberto Ragusa wrote: > > On 6/26/19 2:34 AM, Michal Schorm wrote: > > I - and a people around me - have plenty of 32-bit hardware. > > Just for the record, I've got a couple of AMD XP2400+, AMD XP2000+ machines, > updated to recent Fedora versions and still

Re: HEADS UP: DynamicBuildRequires are available

Le 2019-06-26 15:39, Richard W.M. Jones a écrit : On Tue, Jun 18, 2019 at 03:27:41AM +0200, Igor Gnatenko wrote: as of today, builders have been updated (thanks to Kevin) and DynamicBuildRequires finally work in Rawhide. Change Page:

Re: Disappearing pagure key

On Wed, Jun 26, 2019 at 07:03:52AM -0600, Jerry James wrote: > I generated a new API key on June 16, and used it. Just now, I tried > to do a fedpkg operation that resulted in the error: > > Could not execute request_repo: The following error occurred while > creating a new issue in Pagure:

Re: HEADS UP: DynamicBuildRequires are available

Dne 26. 06. 19 v 15:39 Richard W.M. Jones napsal(a): > On Tue, Jun 18, 2019 at 03:27:41AM +0200, Igor Gnatenko wrote: >> Hi folks, >> >> as of today, builders have been updated (thanks to Kevin) and >> DynamicBuildRequires finally work in Rawhide. >> >> Change Page:

Re: HEADS UP: DynamicBuildRequires are available

On Tue, Jun 18, 2019 at 03:27:41AM +0200, Igor Gnatenko wrote: > Hi folks, > > as of today, builders have been updated (thanks to Kevin) and > DynamicBuildRequires finally work in Rawhide. > > Change Page: https://fedoraproject.org/wiki/Changes/DynamicBuildRequires I'm curious why the

Re: Please update form pep8 to pycodestyle

On 26. 06. 19 14:03, Vít Ondruch wrote: Dne 26. 06. 19 v 13:23 Miro Hrončok napsal(a): On 26. 06. 19 13:12, Miro Hrončok wrote: This is a not that python-pep8 is dead upstream and changed to python-pycodestyle. We want to get rid of python-pep8:

Re: Fedora Rawhide-20190625.n.0 compose check report

On 6/25/19 6:32 PM, Adam Williamson wrote: > On Tue, 2019-06-25 at 17:45 +, Fedora compose checker wrote: >> Missing expected images: >> >> Atomichost raw-xz x86_64 >> Atomichost qcow2 x86_64 >> >> Compose FAILS proposed Rawhide gating check! >> 3 of 47 required tests failed, 4 results

Disappearing pagure key

I generated a new API key on June 16, and used it. Just now, I tried to do a fedpkg operation that resulted in the error: Could not execute request_repo: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://pagure.io/settings#api-keys

[Bug 1723300] Upgrade perl-Promises to 1.02

https://bugzilla.redhat.com/show_bug.cgi?id=1723300 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version|

Re: Fedora 31 System-Wide Change proposal: No More i686 Kernels

On 6/26/19 2:34 AM, Michal Schorm wrote: I - and a people around me - have plenty of 32-bit hardware. Just for the record, I've got a couple of AMD XP2400+, AMD XP2000+ machines, updated to recent Fedora versions and still usable. Regards. -- Roberto Ragusamail at robertoragusa.it

adding speech installation to fedora network installation image

Hello, I’m new blind user of fedora 30. I couldn’t find where to post this request. I have small pendrive, and I must use network installer. Howewer orca or speakup doesn’t run on it. Could you add speech to the installer? Sorry for my English, i’m from Poland

Re: Please update form pep8 to pycodestyle

Dne 26. 06. 19 v 13:23 Miro Hrončok napsal(a): > On 26. 06. 19 13:12, Miro Hrončok wrote: >> This is a not that python-pep8 is dead upstream and changed to >> python-pycodestyle. >> >> We want to get rid of python-pep8: >> https://bugzilla.redhat.com/show_bug.cgi?id=1667200 >> >> Please migrate

Re: Bootstrapped Packages

Dne 26. 06. 19 v 13:11 Miroslav Suchý napsal(a): > Dne 26. 06. 19 v 12:53 Brian (bex) Exelbierd napsal(a): >> Can someone point me at step by step instructions for how to handle >> new packages that require bootstrapping because of a circular >> depedency? >

[Bug 1724169] Missing MPLv2.0 in License

https://bugzilla.redhat.com/show_bug.cgi?id=1724169 Petr Pisar changed: What|Removed |Added Blocks||1632600 -- You are receiving this mail

[Bug 1724169] New: Missing MPLv2.0 in License

https://bugzilla.redhat.com/show_bug.cgi?id=1724169 Bug ID: 1724169 Summary: Missing MPLv2.0 in License Product: Fedora Version: rawhide Status: NEW Component: perl-IO-Socket-SSL Assignee: p...@city-fan.org

Re: Bootstrapped Packages

Am Mittwoch, den 26.06.2019, 12:53 +0200 schrieb Brian (bex) Exelbierd: > Hi, > > Can someone point me at step by step instructions for how to handle > new packages that require bootstrapping because of a circular > depedency? > > I am about to request the first of the repos and want to make

Re: [HEADS UP] Unannounced soname bump of qrencode

On 26. 06. 19 13:34, Martin Kolman wrote: On Tue, 2019-06-25 at 16:30 -0500, mcatanz...@gnome.org wrote: Let's ensure this at least doesn't happen for the same library again and again. In [1], change SHOULD NOT -> MUST NOT. Require maintainers (or provenpackagers) to fix violations like [2]

Re: [HEADS UP] Unannounced soname bump of qrencode

On Tue, 2019-06-25 at 16:30 -0500, mcatanz...@gnome.org wrote: > Let's ensure this at least doesn't happen for the same library again > and again. > > In [1], change SHOULD NOT -> MUST NOT. > > Require maintainers (or provenpackagers) to fix violations like [2] > when unannounced soname bumps

Re: Please update form pep8 to pycodestyle

On 26. 06. 19 13:12, Miro Hrončok wrote: This is a not that python-pep8 is dead upstream and changed to python-pycodestyle. We want to get rid of python-pep8: https://bugzilla.redhat.com/show_bug.cgi?id=1667200 Please migrate your package away from python-pep8 / python-pytest-pep8 to

[Bug 1723962] perl-Test-Refcount-0.10 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1723962 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-Test-Refcount-0.09 is |perl-Test-Refcount-0.10

Please update form pep8 to pycodestyle

This is a not that python-pep8 is dead upstream and changed to python-pycodestyle. We want to get rid of python-pep8: https://bugzilla.redhat.com/show_bug.cgi?id=1667200 Please migrate your package away from python-pep8 / python-pytest-pep8 to python-pycodestyle / python-pytest-pycodestyle

Re: Bootstrapped Packages

Dne 26. 06. 19 v 12:53 Brian (bex) Exelbierd napsal(a): > Can someone point me at step by step instructions for how to handle > new packages that require bootstrapping because of a circular > depedency? https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping -- Miroslav Suchy,

Re: Bootstrapped Packages

On 26. 06. 19 12:53, Brian (bex) Exelbierd wrote: Hi, Can someone point me at step by step instructions for how to handle new packages that require bootstrapping because of a circular depedency? I don't know about any, but if you'd like, I can talk to you over audio chat or IRC/Telegram and

Bootstrapped Packages

Hi, Can someone point me at step by step instructions for how to handle new packages that require bootstrapping because of a circular depedency? I am about to request the first of the repos and want to make sure I follow the process correctly. My goal is to wind up with both packages built

Re: gcc/g++ compiler memory exhaustion on build vms

On 6/26/19 3:25 AM, Philip Kovacs via devel wrote: I am finding that one of my c++ packages has compilation units that generate very large assembly (.s) files -- so large that any attempt to build them in memory (e.g. with -pipe) causes memory exhaustion. The only way I have found to reliably

Re: [HEADS UP] Unannounced soname bump of qrencode

On 26. 06. 19 12:25, Neal Gompa wrote: On Wed, Jun 26, 2019 at 6:01 AM Miro Hrončok wrote: On 26. 06. 19 10:59, Bob Mauchin wrote: At least this is enforced for any new package, I make sure of it. But for existing ones, we can maybe grep .so* to fix them. $ rg -lF '.so*' rpm-specs/ | env

Re: [HEADS UP] Unannounced soname bump of qrencode

On Wed, Jun 26, 2019 at 6:01 AM Miro Hrončok wrote: > > On 26. 06. 19 10:59, Bob Mauchin wrote: > > > > At least this is enforced for any new package, I make sure of it. But for > > existing ones, we can maybe grep .so* to fix them. > > $ rg -lF '.so*' rpm-specs/ | env LANG=en_US.utf8 sort >

Re: [HEADS UP] Unannounced soname bump of qrencode

Hi, On Wed, 2019-06-26 at 11:11 +0200, Miro Hrončok wrote: > $ rg -lF '.so*' rpm-specs/ | env LANG=en_US.utf8 sort > > rpm-specs/evolution.spec that's a false positive, the only occurrence of ".so*" in that file is in the %changelog section, namely: * Tue May 17 2011 x -

Re: [HEADS UP] Unannounced soname bump of qrencode

On 26. 06. 19 10:59, Bob Mauchin wrote: On Wed, Jun 26, 2019, 00:21 Fabio Valentini > wrote: On Tue, Jun 25, 2019 at 11:21 PM Miro Hrončok mailto:mhron...@redhat.com>> wrote: > > qrencode was bumped from 3.4.4 to 4.0.2. > > It has a bumped

[HEADS UP] Sphinx updated to 2.1

I've just pushed and built python-sphinx-2.1.2-1.fc31 for rawhide. I don't anticipate any breakage. In case unexpected breakage happens, let me know. https://src.fedoraproject.org/rpms/python-sphinx/pull-request/12 https://bugzilla.redhat.com/show_bug.cgi?id=1716158 Thanks, -- Miro Hrončok --

[HEADS UP] Sphinx updated to 2.1

I've just pushed and built python-sphinx-2.1.2-1.fc31 for rawhide. I don't anticipate any breakage. In case unexpected breakage happens, let me know. https://src.fedoraproject.org/rpms/python-sphinx/pull-request/12 https://bugzilla.redhat.com/show_bug.cgi?id=1716158 Thanks, -- Miro Hrončok --

Re: [HEADS UP] Unannounced soname bump of qrencode

On Wed, Jun 26, 2019, 00:21 Fabio Valentini wrote: > On Tue, Jun 25, 2019 at 11:21 PM Miro Hrončok wrote: > > > > qrencode was bumped from 3.4.4 to 4.0.2. > > > > It has a bumped soname from libqrencode.so.3 to libqrencode.so.4. > > This might be a good time to remind people that globbing out

Re: Modularity vs. libgit

On 2019-06-25, Adam Williamson wrote: > So I'm still not confident about the story here. Let's take something > that does follow semver: it's not going to change API compatibility as > *often* as libgit2, but ultimately it's gonna happen. And in Rawhide, > presumably, when a new major version

[EPEL-devel] knot / knot-resolver package rebase

Hi, I'd like to rebase knot and knot-resolver packages to their latest upstream versions (Knot DNS 2.8.2, Knot Resolver 4.0.0) in EPEL 7. Reasons --- - upstream of Knot DNS supports only 2.7 and 2.8; the knot version in EPEL 7 (2.6.9) is unsupported and will not receive any more security or

Re: gcc/g++ compiler memory exhaustion on build vms

> On Wednesday, June 26, 2019, 02:42:29 AM EDT, Dan Horák wrote:> > what package is it? fastbit.   This evening I retired it in master since no upstream updates have been issued since 02/2016. https://src.fedoraproject.org/rpms/fastbit The build problems are completely recent, nothing

Re: gcc/g++ compiler memory exhaustion on build vms

On Wed, 26 Jun 2019 05:33:24 + (UTC) Philip Kovacs via devel wrote: > > On Wednesday, June 26, 2019, 01:05:13 AM EDT, John Reiser > > wrote: > > > Please quantify: What is the byte size of the .s file? > > > First hint: give the virtual machine enough resources! > > Either RAM, or