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

Try to onboard package(s) of FAS user jplesnik for Fedora downstream automation #2280

Closed
3 of 6 tasks
Tracked by #2204
lbarcziova opened this issue Dec 11, 2023 · 8 comments
Closed
3 of 6 tasks
Tracked by #2204
Assignees
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/other Other kind than the specified ones.

Comments

@lbarcziova
Copy link
Member

lbarcziova commented Dec 11, 2023

Followup of #2227

  • check whether the maintainer already uses Packit, if yes, contact them and ask about the feedback, offer help with setting up Packit for their other packages

If no:

  • contact the maintainer (Matrix/Slack/email), introduce Packit downstream automation and ask if you could create a PR with Packit config for one of their packages (you can ask whether they have access to the upstream repos or would be interested in having the config only in dist-git)

After an agreement:

  • check this spreadsheet for the list of packages and choose one (ideally with pending release to rebase, having Git upstream, easy to configure),
    • the spreadsheet should be updated accordingly, make sure that the package was not onboarded already (there is overlap of the packages since they can have multiple maintainers)
  • create a Packit configuration setting up the Fedora downstream automation (for syncing start with one branch to not spam)
  • optionally test the syncing locally (see comment)
  • create a PR, try to do a test run (/packit pull-from-upstream --with-pr-config) and communicate further with the maintainer the follow-up steps (e.g. create issues if some functionality is missing, setup on more of their packages)

Part of #2204 epic

@lbarcziova lbarcziova added area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. impact/low This issue impacts only a few users. gain/high This brings a lot of value to (not strictly a lot of) users. kind/other Other kind than the specified ones. labels Dec 11, 2023
@lbarcziova lbarcziova moved this from new to backlog in Packit Kanban Board Dec 11, 2023
@xsuchy xsuchy self-assigned this Jan 15, 2024
@xsuchy
Copy link
Contributor

xsuchy commented Jan 15, 2024

Jitka is using a packit for a package she inherited https://src.fedoraproject.org/rpms/perl-Date-Manip and claims that it likely did not get filed PR despite recent release. Going to check.
I explained packit configs and pull-from upstream, provided two templates. And after a discussion opened two RFEs:
packit/packit#2196
packit/packit#2195

@xsuchy xsuchy moved this from backlog to in-progress in Packit Kanban Board Jan 15, 2024
@xsuchy
Copy link
Contributor

xsuchy commented Jan 15, 2024

Hmm seems Anitya config is correct https://release-monitoring.org/project/2785/
New upstream release happened a week ago https://github.com/SBECK-github/Date-Manip/tags
But no PR in https://src.fedoraproject.org/rpms/perl-Date-Manip

@xsuchy
Copy link
Contributor

xsuchy commented Jan 15, 2024

Oh, the job failed https://dashboard.packit.dev/results/pull-from-upstream/5892 (BTW it is painful to find result of older jobs).

@xsuchy
Copy link
Contributor

xsuchy commented Jan 15, 2024

Ouch it failed to download tarball from https://cpan.metacpan.org/authors/id/S/SB/SBECK/Date-Manip-6.94.tar.gz
It exists now. I guess the timeflow was:

  1. create a release on GitHub
  2. Anitya noticed that, Packit was triggered, download failed
  3. upstream uploaded tarball to cpan

this whole may happened in 5 minutes :(

@xsuchy
Copy link
Contributor

xsuchy commented Jan 15, 2024

I opened packit/packit#2197

@xsuchy
Copy link
Contributor

xsuchy commented Jan 16, 2024

I am moving this to backlog. Until the packit/packit#1954 is resolved I really cannot continue with onboarding of Jitka as all her packages are perl-* and will likely hit the same bug again and again.

@xsuchy xsuchy moved this from in-progress to backlog in Packit Kanban Board Jan 16, 2024
@lbarcziova lbarcziova moved this from backlog to priority-backlog in Packit Kanban Board Feb 1, 2024
@lbarcziova
Copy link
Member Author

The blocking issue is resolved now, we retry the downloading up to 1 hour.

@lachmanfrantisek lachmanfrantisek moved this from priority-backlog to in-progress in Packit Kanban Board Feb 22, 2024
@lbarcziova
Copy link
Member Author

This should be done.

@github-project-automation github-project-automation bot moved this from in-progress to done in Packit Kanban Board Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/other Other kind than the specified ones.
Projects
Archived in project
Development

No branches or pull requests

2 participants