Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added specfile for Mote 0.7.0 release #161

Closed
wants to merge 1 commit into from
Closed

Added specfile for Mote 0.7.0 release #161

wants to merge 1 commit into from

Conversation

gridhead
Copy link
Member

I have packaged it temporarily in https://copr.fedorainfracloud.org/coprs/t0xic0der/mote/.

Here's the build status for Build No. 2184771.

image

It fails on EPEL8 due to the absence of fedmsg package - I believe a blind replacement of fedmsg with fedora-messaging should work if both are cross-compatible.

Signed-off-by: Akashdeep Dhar akashdeep.dhar@gmail.com

Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
@gridhead gridhead self-assigned this May 14, 2021
@nirik
Copy link
Member

nirik commented May 16, 2021

I don't think you can just change fedmsg to fedora-messaging, there's a bit of porting likely I think.
Perhaps @pypingou or @abompard could comment on that?

And many many thanks for working on this packaging. :)

@gridhead
Copy link
Member Author

I don't think you can just change fedmsg to fedora-messaging, there's a bit of porting likely I think.
Perhaps @pypingou or @abompard could comment on that?

And many many thanks for working on this packaging. :)

Yes, I got in touch with @siddharthvipul and @mscherer regarding the schema of fedora-messaging and got to know that fedmsg and fedora-messaging are not cross-compatible and it seems that there would be some codelevel change required before replacing the dependencies. The schema is something to work on, so I thought that the best way forward would be to, first fix the CI here, then ship this version of the package (with Python 3 updates and fedmsg) as-is for now and come back to porting support with fedora-messaging later.

According to this, fedmsg is no longer packaged on EPEL8 and due to the fact that it is one of the dependencies for Mote, my build fails on EPEL8 chroot. Would it be correct to reach out to the current maintainer of fedmsg to include support for EPEL8 or do we make do with a rendition of the fedmsg package maintained at COPR?

@pypingou
Copy link
Member

We purposedly do not want to maintain fedmsg in epel8, porting to fedora-messaging isn't really hard and the schema, while necessary, can be done in a second step, which would unblock you.

https://fedora-messaging.readthedocs.io/en/stable/tutorial/conversion.html has some good doc on converting fedmsg applications to fedora-messaging :)

@gridhead
Copy link
Member Author

@pypingou Thanks for linking in the documentation.

The fedmsg_consumer.py file is predominantly a consumer and not a publisher, which checks for meetings that have recently finished every after 2 seconds and then executes gathering of the meeting information from the datagrepper with soke.py. Unfortunately, the documentation does not (yet) cover the consumer side of porting from fedmsg to fedora-messaging. Could you please link me to some examples for them?

@pypingou
Copy link
Member

If you are not a publisher it will make things even easier as there will be no need for message schemas.

As for consuming messages the docs is: https://fedora-messaging.readthedocs.io/en/stable/consuming.html

@gridhead gridhead deleted the branch fedora-infra:master September 30, 2021 10:14
@gridhead gridhead closed this Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants