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

Ubuntu PPA out of date #3923

Closed
shaicoleman opened this issue Sep 2, 2019 · 21 comments
Closed

Ubuntu PPA out of date #3923

shaicoleman opened this issue Sep 2, 2019 · 21 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. Packaging Bug is in a Podman package

Comments

@shaicoleman
Copy link

shaicoleman commented Sep 2, 2019

/kind bug

Description

The Ubuntu PPA is out of date. The latest version is 1.5.1, while the latest version on the PPA is 1.5.0

Would be great if the PPA would automatically be update whenever there's a new release.

It would save everybody time not having to deal with bugs that have already been fixed in newer versions.

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 2, 2019
@mheon mheon added the ubuntu label Sep 2, 2019
@mheon
Copy link
Member

mheon commented Sep 2, 2019

@lsm5 PTAL

@lsm5
Copy link
Member

lsm5 commented Sep 2, 2019

@mheon @shaicoleman yup, I had disabled autorebuild on podman cause of #3838 (sorry I felt it was troublesome). Let me re-enable it given the issue is fixed.

@lsm5 lsm5 self-assigned this Sep 2, 2019
@lsm5 lsm5 added the Packaging Bug is in a Podman package label Sep 2, 2019
@lsm5
Copy link
Member

lsm5 commented Sep 2, 2019

packages built at https://launchpad.net/~projectatomic/+archive/ubuntu/ppa/+packages ... taking a while to publish though, no idea why, should be done in sometime I hope. @shaicoleman please close this once you see the new builds on your env, thanks.

@shaicoleman
Copy link
Author

They are updated now, thanks!

@shaicoleman
Copy link
Author

@lsm5 , can you into why the v1.6.0-rc1 package wasn't generated?

@lsm5
Copy link
Member

lsm5 commented Sep 17, 2019

@lsm5 , can you into why the v1.6.0-rc1 package wasn't generated?

it wasn't cause I disabled the autobuilder job for a bit. @mheon are we good to have rc tags built and pushed to ppa?

@mheon
Copy link
Member

mheon commented Sep 17, 2019

Uhm. I'm a little iffy on this - I kind of feel they should be opt-in.

I wish there was a way to mark them as pre-release, similar to Fedora's updates-testing channel.

@lsm5
Copy link
Member

lsm5 commented Sep 17, 2019

Uhm. I'm a little iffy on this - I kind of feel they should be opt-in.

I wish there was a way to mark them as pre-release, similar to Fedora's updates-testing channel.

afaik, ppa doesn't/can't provide separate channels. If you suspect things would break, maybe it's best to not build RCs at all.

@lsm5
Copy link
Member

lsm5 commented Sep 17, 2019

What I could do is maybe create a separate ppa itself and build latest commit hourly. Similar to what's done for rawhide. People can use it at their own risk then?

@shaicoleman
Copy link
Author

@lsm5 , Yes, you could have several PPAs (e.g. beta/dev/stable),
See for example: https://launchpad.net/~chromium-team

@lsm5
Copy link
Member

lsm5 commented Sep 17, 2019

@lsm5 , Yes, you could have several PPAs (e.g. beta/dev/stable),
See for example: https://launchpad.net/~chromium-team

So, if I'm reading that right, that's just separate PPAs and no in-built separation like updates-testing and updates on Fedora, yes?

@shaicoleman
Copy link
Author

@lsm5 , yes, exactly.
Just make sure that when you release a stable version, to release it to the beta channel as well, so it isn't behind stable.

@baude
Copy link
Member

baude commented Sep 17, 2019

imho, i would keep things as is ... rc's are not needed in the ppa. ideally we want podman in ubuntu proper ... and if that were to happen, then rcs in the ppas would make perfect sense. i really dont want bug reports on two different repos.

thoughts?

@lsm5
Copy link
Member

lsm5 commented Sep 17, 2019

imho, i would keep things as is ... rc's are not needed in the ppa. ideally we want podman in ubuntu proper ... and if that were to happen, then rcs in the ppas would make perfect sense. i really dont want bug reports on two different repos.

thoughts?

I'd love that :D .. that'd mean less work for me :) . But, shouldn't be too expensive to have a rawhide-esque ppa (I'm thinking upstream master branch) if it helps the adventurous users.

@lsm5
Copy link
Member

lsm5 commented Sep 17, 2019

@baude so, remind me, are the RCs gonna be a regular thing now?

@shaicoleman
Copy link
Author

shaicoleman commented Sep 17, 2019

@lsm5, ideally there should 3 PPAs:

  • Dev (hourly/nightly)
  • Beta (which would include any tagged release, e.g. beta and RC)
  • Stable

@baude
Copy link
Member

baude commented Sep 17, 2019

rcs will be regular. and imho, stable should be part of ubuntu ideally fwiw. anyways, dealers choice here.

@rhatdan
Copy link
Member

rhatdan commented Sep 17, 2019

I would say have three. RCs should only be available for a week or so. We just want to make sure we don't have a regression before we release.

@shaicoleman
Copy link
Author

I've opened a new issue #4099 , as this issue is closed

@shaicoleman
Copy link
Author

1.6.2 is out, while 1.6.1 is the latest in PPA. Reopening

@shaicoleman shaicoleman reopened this Oct 21, 2019
@shaicoleman
Copy link
Author

PPA updated, closing

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. Packaging Bug is in a Podman package
Projects
None yet
Development

No branches or pull requests

6 participants