Re: Unresponsive Maintainer: python-ldap3
Sorry, I have no interest in EPEL packages, so I didn't respond. If you would like to maintain it, I will happily add you as comaintainer. On Fri, Dec 14, 2018, 16:11 Avram Lubkin I've been trying to reach the maintainers for python-ldap3 > (ignatenkobrain, mcyprian) for the last month. I've sent multiple emails, > submitted pull requests[1] [2], and a bug [3]. fedora_active_user.py shows > occasional activity for ignatenkobrain. Does anyone know how to contact > either maintainer? > > Thanks, > > Avram > > [1] https://src.fedoraproject.org/rpms/python-ldap3/pull-request/1 > [2] https://src.fedoraproject.org/rpms/python-ldap3/pull-request/2 > [3] https://bugzilla.redhat.com/show_bug.cgi?id=1653732 > ___ 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: Issue building modules with package branches
git commit -m "rebuild" --allow-empty On Sat, Dec 15, 2018, 23:10 Orion Poplawski I'm trying to build some modules that specify the branch for the package > to use, e.g.: > >components: > rpms: >openmpi: > rationale: The core package > ref: 2.1 > buildorder: 10 > > My first builds failed because I had failed to push the proper commits > to the new branches. I believe that I have fixed that: > > https://src.fedoraproject.org/rpms/openmpi/tree/2.1 > > But now when I resubmit the builds they still fail and are checking out > the initial commit of the branch rather than the head. > > https://koji.fedoraproject.org/koji/taskinfo?taskID=31480566 > > BuildError: No spec file found > > $ git clone -n https://src.fedoraproject.org/rpms/openmpi > > /var/lib/mock/module-openmpi-2.1-20181215203040-a5b0195c-build-14631915-1044824/root/chroot_tmpdir/scmroot/openmpi > Cloning into > > '/var/lib/mock/module-openmpi-2.1-20181215203040-a5b0195c-build-14631915-1044824/root/chroot_tmpdir/scmroot/openmpi'... > $ git reset --hard ca31ec8a6a62a2fa9f10e35814c2d0b1725ef40d > HEAD is now at ca31ec8 Setup of module openmpi > > Out of desperation I checked in a small change to the module file and > now it works - apparently the commits are collected during the initial > macros build? Is there any other way to deal with this in the future if > needed? > > > -- > 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 > ___ 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: How to resubmit a module build
Afaik expanded builds can't be resubmitted, the good news is that if you make empty commit and run build again it will be less painful because it will reuse components for successful build. ___ 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
[389-devel] 389 DS nightly 2018-12-16 - 90% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2018/12/16/report-389-ds-base-1.4.0.20-20181216git174c468.fc29.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
[Bug 1547165] perl-ExtUtils-CBuilder should require gcc
https://bugzilla.redhat.com/show_bug.cgi?id=1547165 Fedora Update System changed: What|Removed |Added Resolution|RAWHIDE |ERRATA --- Comment #13 from Fedora Update System --- perl-Net-IDN-Encode-2.400-7.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 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
How to resubmit a module build
Module build number 2628 failed due to what appears to have been a koji issue: https://koji.fedoraproject.org/koji/taskinfo?taskID=31483290 : deadlock detected DETAIL: Process 31743 waits for ShareLock on transaction 4127247553; blocked by process 17714. Process 17714 waits for ShareLock on transaction 4127247628; blocked by process 31743. HINT: See server log for query details. The other builds (f29, f28) succeeded. Is there a way to re-submit just this build? -- 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
[Test-Announce] 2018-12-17 @ ** 17:00 ** UTC - Fedora 30 Blocker Review Meeting
# F30 Blocker Review meeting # Date: 2018-12-17 # Time: ** 17:00 ** UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 4 proposed Beta blockers and 3 proposed Final blockers to review, so let's have the first Fedora 30 blocker review meeting on Monday! Note that clocks went back in areas that observe DST since the last blocker review meeting, so the meeting is now at 17:00 UTC. 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
[Test-Announce] Proposal to CANCEL: 2018-12-17 Fedora QA Meeting
Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have anything urgent for the agenda. Note that would mean we probably won't meet till the New Year, due to the holidays and the Red Hat shutdown, so please speak up if you think we need to discuss anything before then. If you're aware of anything important we have to discuss this week, please do reply to this mail and we can go ahead and run the meeting. Happy holidays, everyone! -- 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
Orphaned python-dropbox
JFYI I have just orphaned python-dropbox. I no longer use it for several years and I don't really care about it. python2-dropbox is required by duplicity. -- 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
Issue building modules with package branches
I'm trying to build some modules that specify the branch for the package to use, e.g.: components: rpms: openmpi: rationale: The core package ref: 2.1 buildorder: 10 My first builds failed because I had failed to push the proper commits to the new branches. I believe that I have fixed that: https://src.fedoraproject.org/rpms/openmpi/tree/2.1 But now when I resubmit the builds they still fail and are checking out the initial commit of the branch rather than the head. https://koji.fedoraproject.org/koji/taskinfo?taskID=31480566 BuildError: No spec file found $ git clone -n https://src.fedoraproject.org/rpms/openmpi /var/lib/mock/module-openmpi-2.1-20181215203040-a5b0195c-build-14631915-1044824/root/chroot_tmpdir/scmroot/openmpi Cloning into '/var/lib/mock/module-openmpi-2.1-20181215203040-a5b0195c-build-14631915-1044824/root/chroot_tmpdir/scmroot/openmpi'... $ git reset --hard ca31ec8a6a62a2fa9f10e35814c2d0b1725ef40d HEAD is now at ca31ec8 Setup of module openmpi Out of desperation I checked in a small change to the module file and now it works - apparently the commits are collected during the initial macros build? Is there any other way to deal with this in the future if needed? -- 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
Need help with illegal instruction errors in COPR
I'm testing out rebuilding packages with openmpi 3.1 in COPR: https://copr.fedorainfracloud.org/coprs/g/scitech/openmpi3.1/builds/ A number of packages are failing running tests only on Fedora Rawhide x86_64 with processes killed with signal 4 (Illegal instruction). For example: + PYTHONPATH=/builddir/build/BUILDROOT/mpi4py-3.0.0-6.git39ca78422646.fc30.x86_64/usr/lib64/python2.7/site-packages/openmpi + mpiexec -n 1 python2 test/runtests.py -v --no-builddir --thread-level=serialized -e spawn BUILDSTDERR: -- BUILDSTDERR: Primary job terminated normally, but 1 process returned BUILDSTDERR: a non-zero exit code. Per user-direction, the job has been aborted. BUILDSTDERR: -- BUILDSTDERR: -- BUILDSTDERR: mpiexec noticed that process rank 0 with PID 0 on node 656ae442c6bf45fe9b45c5481f41bc45 exited on signal 4 (Illegal instruction). BUILDSTDERR: -- Unfortunately I have been unable to reproduce this in any local mock builds. So I'm left wondering if this is some kind of peculiarity with the COPR builders or if there is a real problem with openmpi. Any suggestions for how to further debug this would be greatly appreciated. (PID 0 seems very odd) - Orion -- 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: Anthony McInerney
- Original Message - > From: "Anthony F McInerney" > To: devel@lists.fedoraproject.org > Sent: Friday, December 14, 2018 6:00:52 PM > Subject: Self Introduction: Anthony McInerney > > Hi All, as per the packaging guidelines i'm just touching base to say hello. > I'm hoping to get cockpit-composer into fedora, and willing to triage > bugs etc as required. > Need a sponsor. > https://bugzilla.redhat.com/show_bug.cgi?id=1659556 > I have previously packaged for debian, and have been using fedora for > quite some time now. (home and work) > the copr is managed directly by the cockpit/welder-web team. > thanks. > ___ > 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 > Hello Anthony and welcome! -- Regards, Charalampos Stratakis Software Engineer Python Maintenance Team, 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: Problems building a module
Also, probably would be good to mention modulemd-validator somewhere on https://docs.fedoraproject.org/en-US/modularity/ On 12/15/18 11:27 AM, Orion Poplawski wrote: Thanks, that pointed out the problem (I had profile instead of profiles). This is https://src.fedoraproject.org/modules/octave/blob/4.4/f/octave.yaml On 12/15/18 1:37 AM, Igor Gnatenko wrote: You can use modulemd-validator. Where can I find your modulemd? On Sat, Dec 15, 2018 at 3:10 AM Orion Poplawski wrote: I'm trying to build a module, and it's failing without much useful information: octave (4.4)]$ fedpkg module-build Submitting the module build... Could not execute module_build: The build failed with: The following invalid modulemd was encountered: /tmp/tmpCyuFOY/octave/octave.yaml So something presumably is wrong with my modulemd file - but how can I figure out what? Thanks. -- 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 ___ 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 -- 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: Problems building a module
Thanks, that pointed out the problem (I had profile instead of profiles). This is https://src.fedoraproject.org/modules/octave/blob/4.4/f/octave.yaml On 12/15/18 1:37 AM, Igor Gnatenko wrote: You can use modulemd-validator. Where can I find your modulemd? On Sat, Dec 15, 2018 at 3:10 AM Orion Poplawski wrote: I'm trying to build a module, and it's failing without much useful information: octave (4.4)]$ fedpkg module-build Submitting the module build... Could not execute module_build: The build failed with: The following invalid modulemd was encountered: /tmp/tmpCyuFOY/octave/octave.yaml So something presumably is wrong with my modulemd file - but how can I figure out what? Thanks. -- 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 ___ 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 -- 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
[HEADS UP] Teeworlds update & license change
teeworlds / teeworlds should have been always "Teeworlds and zlib", because it bundles some md5 code which is zlib-licensed. teeworlds-data was supposed to be CC-BY-SA, but it was not marked this way. Now to the real changes, since 0.7 it bundles json-parser (unbundle will come within next few days) which is BSD licensed, so teeworlds (not -server) will have "and BSD". Once I will unbundle it, I will remove this part again. Thanks for attention! ___ 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: Qt 5.11.3 coming to rawhide
Rex Dieter wrote: > I ran into a aarch64 FTBFS situation during some testing with > qt5-qtwebengine (see https://bugreports.qt.io/browse/QTBUG-72289 ), so I'm > going to hold off on this for now. This work was completed in a side tag, and is awaiting move/tagging into rawhide now, https://pagure.io/releng/issue/7966 -- Rex ___ 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: fedora-rawhide-kernel-nodebug is not getting updates
On Wed, Dec 12, 2018 at 12:37:24 -0600, Bruno Wolff III wrote: On Thu, Dec 06, 2018 at 14:29:15 +, "Richard W.M. Jones" wrote: Anyway it seems like Rawhide isn't getting new nodebug kernels. - Latest nodebug kernel: kernel-4.20.0-0.rc1.git4.2.fc30.x86_64.rpm (https://dl.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/x86_64/) - Latest Rawhide kernel: kernel-4.20.0-0.rc5.git2.1.fc30 (https://koji.fedoraproject.org/koji/packageinfo?packageID=8) Something weird is going on. The git0.1 kernels make it in, but the other gitX.2 kernels don't. It keeps reverting to 4.20.0-0.rc1.git4.2. It reverted again today. Is this issue being tracked somewhere? If not, where is the correct place to report it? ___ 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: OUTAGE: Bugzilla outage today
On Sat, Dec 15, 2018, 11:17 Raphael Groner > I hope to one day add a true task working system to Bodhi that allows > failed tasks to be automatically retried so that it can automatically > recover from situations like this > > Well, I'm not sure if I understand your issue correctly but did you try to > implement anything like continuous delivery? Maybe take a look into Koschei > or Copr if not done already. > If I understand it correctly, the problem is that bodhi obviously can't edit bugs if bugzilla is offline, and failed requests are just discarded - so the changes are lost. That has nothing to do with packaging, only with a missing "retry queue" in bodhi itself. Fabio ___ > 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
Re: OUTAGE: Bugzilla outage today
> I hope to one day add a true task working system to Bodhi that allows failed > tasks to be automatically retried so that it can automatically recover from > situations like this Well, I'm not sure if I understand your issue correctly but did you try to implement anything like continuous delivery? Maybe take a look into Koschei or Copr if not done already. ___ 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: desktop-file-validate fails with error: file contains group "Catia Shortcut Group", but groups extending the format should start with "X-"
Thanks for your statement. Martin ___ 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: Broken el7 ppc64 koji
On Fri, 14 Dec 2018 17:26:39 -0700 Orion Poplawski wrote: > On 12/14/18 7:41 AM, Dan Horák wrote: > > On Fri, 14 Dec 2018 09:29:26 -0500 > > Stephen John Smoogen wrote: > > > >> On Fri, 14 Dec 2018 at 08:53, Vascom wrote: > >>> > >>> But it was here in previous build few months ago. > >>> https://kojipkgs.fedoraproject.org//packages/mediainfo/18.08.1/1.el7/data/logs/ppc64/root.log > >> > >> OK.. yeah my fault for not looking closer than the koji package > >> sets currently available. So there was a newer version in EPEL > >> when you built this months ago. > >> > >> DEBUG util.py:439: libmspack ppc64 > >> 0.7-0.1.alpha.el7 build 75 k > >> > >> and then RHEL added it to all architectures other than ppc64 as > >> libmspack-0.5-0.6.alpha.el7.x86_64.rpm > >> > >> since EPEL has a rule to not over-ride RHEL packages since that > >> causes user problems.. it got pulled out of epel. However that > >> means you can't build this for ppc64 anymore. The two options > >> would be to contact sharkcz and have him see if he wants to > >> rebuild that old version for ppc64 or exclusivearch and exclude > >> ppc64. > > > > I would welcome a co-maintainer for mspack as I'm already at my > > capacity :-) > > > > > > Dan > > > > I've got an update for this ready to get pushed to git. But we need > to get that branch unretired first. Dan - can you add me (orion) to > the package: > > https://src.fedoraproject.org/rpms/libmspack done > perhaps you can reactivate the branch there too. can't see a way how to do that in pagure, IIRC we need a releng ticket Dan ___ 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: Problems building a module
You can use modulemd-validator. Where can I find your modulemd? On Sat, Dec 15, 2018 at 3:10 AM Orion Poplawski wrote: > > I'm trying to build a module, and it's failing without much useful > information: > > octave (4.4)]$ fedpkg module-build > Submitting the module build... > Could not execute module_build: The build failed with: > The following invalid modulemd was encountered: > /tmp/tmpCyuFOY/octave/octave.yaml > > So something presumably is wrong with my modulemd file - but how can I > figure out what? > > Thanks. > > -- > 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 ___ 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
