FEDORA-2019-b55ed79892 ejected from the push
Hi guys, can someone please tell me what's going on? https://bodhi.fedoraproject.org/updates/FEDORA-2019-b55ed79892 Thanks! Andrea ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to reuild wdune ?
$ fedpkg build --target f31 https://koji.fedoraproject.org/koji/taskinfo?taskID=39903543 Result BuildError: package wdune not in list for tag f31-updates-candidate What has to be done, to bring wdune to fedora 31 ? so long MUFTI ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to reuild wdune ?
> $ fedpkg build --target f31 > > https://koji.fedoraproject.org/koji/taskinfo?taskID=39903543 > > Result > > BuildError: package wdune not in list for tag f31-updates-candidate > > > What has to be done, to bring wdune to fedora 31 ? > Try reading https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/WHP6UKNKFX7RY7Y22CNNGWWKBBJX3JI6/ fedpkg request-branch --repo wdune f31 fedpkg request-branch --repo wdune f30 > so long > MUFTI ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
Hi, $ fedpkg build --target f32 was successfull. # lsb_release -a | grep Release Release: 32 # yum search wdune Last metadata expiration check: 1:42:31 ago on Tue 24 Dec 2019 06:59:24 AM CET. No matches found. What is needed to add wdune to fedora 32 ? so long MUFTI ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
On 24/12/2019 07:45, J. Scheurich wrote: $ fedpkg build --target f32 was successfull. # lsb_release -a | grep Release Release: 32 # yum search wdune Last metadata expiration check: 1:42:31 ago on Tue 24 Dec 2019 06:59:24 AM CET. No matches found. What is needed to add wdune to fedora 32 ? A successful build would be a good start. The only build on koji at the moment is a failed one: https://koji.fedoraproject.org/koji/buildinfo?buildID=1424721 Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora Packager Dashboard mockups
Hi Miro, I like your packaging dashboard a lot, I think this a good idea and an improvement for the packaging experience! (Further replies below.) Miro Hrončok writes: > While I love the concepts of Rust, I don't think there are that many benefits > when mostly talking to HTTP or calling dnf/libsolv API. I wanted to learn > some > Rust via https://adventofcode.com/2019 but I have failed to delicate some > time > to that, nerdslipping and procrastinating differently :D Unless you are already quite proficient in Rust, it is probably more pragmatic to just use Python. > > I was actually thinking Python + asyncio to collect the data + something like > Angular to present them. However I'd rather go back and do adventofcode in > Ook! > than writing the JS frontend myself ;) I've gathered a bit of experience with Typescript at $dayjob over the past months (unfortunately not with browsers and thus not actual frontend stuff), so if you're patient with me (and my limited time), I'd be willing to help out. Cheers, Dan signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
How do I add bohdi revelant tag?
I wish to push pycxx for epel7 how do I add a the epel7 tags? The following comment has been added to the python-pycxx-7.1.3-5.el7 update: bodhi - 2019-12-24 07:04:49.655106 (karma: 0) FEDORA-EPEL-2019-476f0d3c08 ejected from the push because "Cannot find relevant tag for python-pycxx-7.1.3-5.el7. None of ['epel7', 'epel7-pending', 'epel7-override'] are in ['dist-6E-epel-testing', 'epel7-testing', 'dist-5E-epel-testing', 'f27-modular-updates-testing', 'f30-modular-updates-testing', 'f30-container-updates-testing', 'f30-flatpak-updates-testing', 'f28-modular-updates-testing', 'f28-container-updates-testing', 'epel8-testing', 'f31-modular-updates-testing', 'f32-container-updates-testing', 'f31-container-updates-testing', 'f31-flatpak-updates-testing', 'f29-modular-updates-testing', 'f29-container-updates-testing', 'f29-flatpak-updates-testing', 'f22-updates-testing', 'f21-updates-testing', 'f25-updates-testing', 'f24-updates-testing', 'f23-updates-testing', 'f26-updates-testing', 'f27-updates-testing', 'f30-updates-testing', 'f28-updates-testing', 'f31-updates-testing', 'f32-updates-testing', 'f29-updates-testing', 'epel8-modular-updates-testing']." https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-476f0d3c08 Barry ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How do I add bohdi revelant tag?
On Tue, Dec 24, 2019, 09:51 Barry Scott wrote: > I wish to push pycxx for epel7 how do I add a the epel7 tags? > > The following comment has been added to the python-pycxx-7.1.3-5.el7 > update: > > bodhi - 2019-12-24 07:04:49.655106 (karma: 0) > FEDORA-EPEL-2019-476f0d3c08 ejected from the push because "Cannot find > relevant tag for python-pycxx-7.1.3-5.el7. None of ['epel7', > 'epel7-pending', 'epel7-override'] are in ['dist-6E-epel-testing', > 'epel7-testing', 'dist-5E-epel-testing', 'f27-modular-updates-testing', > 'f30-modular-updates-testing', 'f30-container-updates-testing', > 'f30-flatpak-updates-testing', 'f28-modular-updates-testing', > 'f28-container-updates-testing', 'epel8-testing', > 'f31-modular-updates-testing', 'f32-container-updates-testing', > 'f31-container-updates-testing', 'f31-flatpak-updates-testing', > 'f29-modular-updates-testing', 'f29-container-updates-testing', > 'f29-flatpak-updates-testing', 'f22-updates-testing', > 'f21-updates-testing', 'f25-updates-testing', 'f24-updates-testing', > 'f23-updates-testing', 'f26-updates-testing', 'f27-updates-testing', > 'f30-updates-testing', 'f28-updates-testing', 'f31-updates-testing', > 'f32-updates-testing', 'f29-updates-testing', > 'epel8-modular-updates-testing']." > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-476f0d3c08 You don't have to do anything, this is an issue in fedora infrastructure. There's some ongoing issues with bodhi and / or the fedora message queue so that some messages don't get passed around and then don't trigger the necessary actions in koji/bodhi. If you look at, for example, the updates for rawhide (which should get created and pushed to stable and testing automatically), you'll see that for two days, things have not been working as they should, with most things still stuck in the pending state: https://bodhi.fedoraproject.org/releases/F32 This is also the reason why there were no updates-testing composes for 30 and 31 since then. I think this is the relevant infra Ticket: https://pagure.io/fedora-infrastructure/issue/8477#comment-617932 Fabio > > Barry > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > 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://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
Hi, | fedpkg request-branch --repo wdune f31 | fedpkg request-branch --repo wdune f30 $ fedpkg request-branch --repo wdune f31 Could not execute request_branch: Missing a Pagure token. Refer to "fedpkg request-repo -h" to set atoken in your user configuration. I created a new token at https://pagure.io/settings/token/new and inserted it in ~/.config/rpkg/fedpkg.conf ??? so long MUFTI ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
> Hi, > > | fedpkg request-branch --repo wdune f31 > | fedpkg request-branch --repo wdune f30 > > $ fedpkg request-branch --repo wdune f31 > Could not execute request_branch: Missing a Pagure token. Refer to > "fedpkg request-repo -h" to set atoken in your user configuration. > > I created a new token at https://pagure.io/settings/token/new and > inserted it in ~/.config/rpkg/fedpkg.conf > > ??? > > so long > > MUFTI Try ticking all the ACLs boxes when you create the Pagure token ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
Hi, $ fedpkg request-branch --repo wdune f31 Could not execute request_branch: Missing a Pagure token. Refer to "fedpkg request-repo -h" to set atoken in your user configuration. $ fedpkg request-repo wdune Could not execute request_repo: A Bugzilla bug is required on new repository requests $ I adeded it a dummy bug https://bugzilla.redhat.com/show_bug.cgi?id=1786307 but no effect 8-( so long MUFTI ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
The correct bug would be this, I think: https://bugzilla.redhat.com/show_bug.cgi?id=1658153 > $ fedpkg request-repo wdune > Could not execute request_repo: A Bugzilla bug is required on new > repository requests > $ > > I adeded it a dummy bug > > https://bugzilla.redhat.com/show_bug.cgi?id=1786307 > > but no effect 8-( > - Thomas ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
* J. Scheurich [24/12/2019 10:42] : > > $ fedpkg request-branch --repo wdune f31 > Could not execute request_branch: Missing a Pagure token. Refer to > "fedpkg request-repo -h" to set atoken in your user configuration. You need to get a new token. Go to https://src.fedoraproject.org/settings/token/new Click the "Toggle all" button then the "Create button" and copy-paste the resulting API key in .config/rpkg/fedpkg.conf Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: This update's test gating status has been changed to, 'greenwave_failed'.
On Mon, Oct 7, 2019 at 9:44 AM Pierre-Yves Chibon wrote: > > It likely was. Bodhi called greenwave to ask about a status of the builds > in an > update, greenwave calls Koji for more information, that calls returned an > error. > Greenwave's request returns an error as well. > Bodhi is not able to distinguish where the error is coming from and thus > set the > status to "greenwave_failed". > So, this mean Bodhi will reject to move the package to updates or not? :-? It's happening to me too[1]. [1] https://bodhi.fedoraproject.org/updates/FEDORA-2019-d9a4a2d770 -- Ismael Olea http://olea.org/diario/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
https://koji.fedoraproject.org/koji/packageinfo?tagOrder=extra_arches&packageID=30158&buildOrder=-completion_time&buildStart=0#taglist ** | Information for package wdune | f32 releng yes Maybe this could be a problem ? so long MUFTI ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
On 24.12.2019 12:00, Emmanuel wrote: > Click the "Toggle all" button then the "Create button" You need only "Create a new issue" permission. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Final fedora distribution Was: How to reuild wdune ?
On Tue, Dec 24, 2019 at 11:43 AM J. Scheurich wrote: > > Hi, > > $ fedpkg request-branch --repo wdune f31 > Could not execute request_branch: Missing a Pagure token. Refer to > "fedpkg request-repo -h" to set atoken in your user configuration. > $ fedpkg request-repo wdune > Could not execute request_repo: A Bugzilla bug is required on new > repository requests > $ > > I adeded it a dummy bug > > https://bugzilla.redhat.com/show_bug.cgi?id=1786307 > > but no effect 8-( Why are you trying to create the repo again? You already have it: https://src.fedoraproject.org/rpms/wdune And from the looks of it, you have not even attempted to read the documentation we pointed you to ... 1. First, you imported the exploded upstream tarball into dist-git 2. you removed them (which is good) 3. then you reimported all the sources (BUT WHY) and removed the .spec file from the repo (uhm ...?) 4. with the next commit you added back the .spec file but also committed some temporary (config.*) files that are spit out by the build (??) 5. and with the last commit you removed the BuildRequires that aren't available in koji yet, because you haven't built them first (that won't help you to get this building ...) and even committed the bodhi update template ... So, to summarize: Please just STOP what you're doing right now, and wait (possibly until after the holidays) until your sponsor can help you get this sorted out. If you continue like this, you won't get anywhere. We've been trying to help you, but clearly it's not working out. Fabio > so long > MUFTI > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > 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://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
fedora infrastructure issues: don't panic, it's not your fault
Hi all, There have been some reports that multiple fedora services are currently not working. It might be a good idea to post this to devel as a new thread to make sure more people see it and don't start panicking because their builds are failing or bodhi sends them cryptic error messages. - This issue is already being tracked: https://status.fedoraproject.org/ - It looks like the fedora message queues arent working correctly: https://pagure.io/fedora-infrastructure/issue/8477 This is affecting bodhi (updates are not getting pushed to the correct tags and repos) and koji (builds are not moved to the correct tags, probably because bodhi doesn't tell it to, and there are no new composes of updates-testing), greenwave started to fail, and I think it's even starting to affect COPR builds from what I've read. So don't panic if your build fails or doesn't get pushed to -testing or rawhide. It's not a problem with your package / build, but fedora infrastructure seems to suffer from cookie coma. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: FEDORA-2019-b55ed79892 ejected from the push
On Tue, Dec 24, 2019, 09:23 Andrea Musuruane wrote: > Hi guys, > can someone please tell me what's going on? > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-b55ed79892 > > Thanks! > Hi the infra is experiencing some issue [0] which I think is the root cause of this problem. Long story short, your update builds should be available in the updates-testing repo and I have fixed the update this morning so that it shows the correct status (testing). Let us know if you have any more troubles. [0] - https://pagure.io/fedora-infrastructure/issue/8477 > Andrea > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > 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://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: FEDORA-2019-b55ed79892 ejected from the push
On Tue, 2019-12-24 at 15:05 +0100, Clement Verna wrote: > On Tue, Dec 24, 2019, 09:23 Andrea Musuruane > wrote: > > Hi guys, > > can someone please tell me what's going on? > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-b55ed79892 > > > > Thanks! > > Hi the infra is experiencing some issue [0] which I think is the root > cause of this problem. > > Long story short, your update builds should be available in the > updates-testing repo and I have fixed the update this morning so that > it shows the correct status (testing). > > Let us know if you have any more troubles. https://koji.fedoraproject.org/koji/taskinfo?taskID=39905462 Result GenericError: cannot update build 1424768, state: COMPLETE this build is marked as sucefull , but didn't send the build to bodhi , what should I do now ? fedpkg build --skip-nvr-check ? > [0] - https://pagure.io/fedora-infrastructure/issue/8477 > > > Andrea > > > > > > ___ > > > > devel mailing list -- devel@lists.fedoraproject.org > > > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > > 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://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaned packages looking for new maintainers
Pardon the top posting. I am on the road with only my phone, no Fedora devices anywhere. I have been thinking about trying to get Facebook's Infer tool into Fedora. Several of its dependencies are on this list, but I won't be able to take them until I get home, after they are retired. The ocaml packages, at least, have some serious dependency issues, as I recall, but I would like to see if they can be fixed. Can someone please assign the following packages to me? After I return I will fix them if I can & retire them if I cannot. jackson ocaml-bin-prot ocaml-deriving ocaml-sexplib My FAS name is jjames. Thanks! On Mon, Dec 23, 2019, 2:02 AM Miro Hrončok wrote: > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you know for > sure > that the package should be retired, please do so now with a proper reason: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > Note: If you received this mail directly you (co)maintain one of the > affected > packages or a package that depends on one. Please adopt the affected > package or > retire your depending package to avoid broken dependencies, otherwise your > package will be retired when the affected package gets retired. > > Request package ownership via the *Take* button in he left column on > https://src.fedoraproject.org/rpms/ > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2019-12-23.txt > grep it for your FAS username and follow the dependency chain. > > Package (co)maintainers Status > Change > > > ExchangeIRorphan 5 weeks > ago > MochiKit orphan 1 weeks > ago > apache-logging-parent mizdebsk, orphan 5 weeks > ago > apachetop orphan, robert 1 weeks > ago > apt-cacher-ng orphan 5 weeks > ago > archaius orphan 5 weeks > ago > archmage lbazan, orphan 4 weeks > ago > audit-viewer mitr, orphan 4 weeks > ago > avalon-logkit jerboaa, mizdebsk, orphan4 weeks > ago > binclock lbalhar, orphan 1 weeks > ago > buildnumber-maven-plugin orphan 4 weeks > ago > camotics orphan 5 weeks > ago > cduce orphan 5 weeks > ago > clapham orphan 5 weeks > ago > csstidy orphan 5 weeks > ago > delve go-sig, orphan 5 weeks > ago > dzen2 bstinson, dcantrel, fale,3 weeks > ago >lupinix, orphan > eclipse-anyedit eclipse-sig, orphan, swagiaal5 weeks > ago > eclipse-checkstyleakurtakov, eclipse-sig, orphan 5 weeks > ago > eclipse-color-theme eclipse-sig, orphan 5 weeks > ago > eclipse-dltk akurtakov, eclipse-sig, 5 weeks > ago >kdaniel, orphan, rgrunber > eclipse-epic eclipse-sig, orphan 5 weeks > ago > eclipse-m2e-antlr eclipse-sig, mizdebsk, orphan5 weeks > ago > eclipse-m2e-cxf eclipse-sig, mizdebsk, orphan5 weeks > ago > eclipse-m2e-maven-dependency- mizdebsk, orphan 5 weeks > ago > plugin > eclipse-m2e-modello eclipse-sig, mizdebsk, orphan5 weeks > ago > eclipse-m2e-plexuseclipse-sig, mizdebsk, orphan5 weeks > ago > eclipse-m2e-sisu eclipse-sig, mizdebsk, orphan5 weeks > ago > eclipse-m2e-takarimizdebsk, orphan 5 weeks > ago > eclipse-nls orphan 5 weeks > ago > eclipse-pdt eclipse-sig, orphan 5 weeks > ago > eclipse-quickrex eclipse-sig, orphan 5 weeks > ago > eclipse-sgx orphan 5 weeks > ago > exercism go-sig, orphan 0 weeks > ago > fabricorphan 5 weeks > ago > ferm orphan, slankes 5 weeks > ago > giis orphan 5 weeks > ago > gipfelorphan 5 weeks
Re: FEDORA-2019-b55ed79892 ejected from the push
On Tue, Dec 24, 2019 at 02:15:55PM +, Sérgio Basto wrote: > On Tue, 2019-12-24 at 15:05 +0100, Clement Verna wrote: > > On Tue, Dec 24, 2019, 09:23 Andrea Musuruane > > wrote: > > > Hi guys, > > > can someone please tell me what's going on? > > > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-b55ed79892 > > > > > > Thanks! > > > > Hi the infra is experiencing some issue [0] which I think is the root > > cause of this problem. > > > > Long story short, your update builds should be available in the > > updates-testing repo and I have fixed the update this morning so that > > it shows the correct status (testing). > > > > Let us know if you have any more troubles. > > https://koji.fedoraproject.org/koji/taskinfo?taskID=39905462 > Result > > > GenericError: cannot update build 1424768, state: COMPLETE > this build is marked as sucefull , but didn't send the build to bodhi , > what should I do now ? > > fedpkg build --skip-nvr-check ? No. I'd just bump release and build a new one. I have no idea yet whats causing this error... kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaned packages looking for new maintainers
Hi Jerry, Jerry James writes: > Pardon the top posting. I am on the road with only my phone, no Fedora > devices anywhere. I have been thinking about trying to get Facebook's Infer > tool into Fedora. Several of its dependencies are on this list, but I won't > be able to take them until I get home, after they are retired. The ocaml > packages, at least, have some serious dependency issues, as I recall, but I > would like to see if they can be fixed. Can someone please assign the > following packages to me? After I return I will fix them if I can & retire > them if I cannot. > > jackson > ocaml-bin-prot > ocaml-deriving > ocaml-sexplib Since I'd also like to package infer for Fedora, I've taken the ocaml packages and made you an admin of them too. Unfortunately, jackson has already been retired, but since it's a Java package and I have zero experience with that, I have not filed a releng ticket for that. Feel free to contact me when you get back home & enjoy your trip in the meantime! Cheers, Dan signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: FEDORA-2019-b55ed79892 ejected from the push
On Tue, 2019-12-24 at 13:33 -0800, Kevin Fenzi wrote: > On Tue, Dec 24, 2019 at 02:15:55PM +, Sérgio Basto wrote: > > On Tue, 2019-12-24 at 15:05 +0100, Clement Verna wrote: > > > On Tue, Dec 24, 2019, 09:23 Andrea Musuruane > > > wrote: > > > > Hi guys, > > > > can someone please tell me what's going on? > > > > > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-b55ed79892 > > > > > > > > Thanks! > > > > > > Hi the infra is experiencing some issue [0] which I think is the > > > root > > > cause of this problem. > > > > > > Long story short, your update builds should be available in the > > > updates-testing repo and I have fixed the update this morning so > > > that > > > it shows the correct status (testing). > > > > > > Let us know if you have any more troubles. > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=39905462 > > Result > > > > > > GenericError: cannot update build 1424768, state: COMPLETE > > this build is marked as sucefull , but didn't send the build to > > bodhi , > > what should I do now ? > > > > fedpkg build --skip-nvr-check ? > > No. > > I'd just bump release and build a new one. Ok, no problem. Another solution that I thought, but didn't work, was "Create new update" on bodhi (for the fc32 package). Happy christmas > I have no idea yet whats causing this error... > kevin > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
