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

Publish version 1.11.0 to Ubuntu 18.04 and 19.04 repositories #1918

Closed
Davio opened this issue Oct 15, 2019 · 12 comments
Closed

Publish version 1.11.0 to Ubuntu 18.04 and 19.04 repositories #1918

Davio opened this issue Oct 15, 2019 · 12 comments

Comments

@Davio
Copy link

Davio commented Oct 15, 2019

Looking at https://launchpad.net/~projectatomic/+archive/ubuntu/ppa it seems version 1.11.0 has only been released for Ubuntu 16.04.

Will Buildah be published for 18.04 and 19.04 as well?

@lsm5
Copy link
Member

lsm5 commented Oct 15, 2019

@Davio yes, it will, but some rebase issues in autobuilder. Handling it now..

@TomSweeneyRedHat could you please give me access to assign issues to myself and set labels?

@rhatdan
Copy link
Member

rhatdan commented Oct 15, 2019

@lsm5 I think you should be able to do that now.

@bromaniac
Copy link

Any progress on this?

@FooBarWidget
Copy link

FooBarWidget commented Dec 1, 2019

I would also like to know, would be great if my next project can use Buildah instead of Docker. I need the buildah bud --device option which appeared in v1.11.

@wwilson
Copy link

wwilson commented Jan 4, 2020

Can we get an update on this?

@TomSweeneyRedHat
Copy link
Member

@lsm5 ping!

@wwilson
Copy link

wwilson commented Jan 14, 2020

It's been ~2 months since anything was published to the Project Atomic PPA. Is there something going wrong behind the scenes that me/others in the community can help out with?

@TomSweeneyRedHat
Copy link
Member

The main issue is the person who handles this @lsm5 had a crunch of other high priority work that he undertook before a very long and very well deserved vacation/PTO that started in early December and will be wrapping up in at the end of this month. He's been monitoring mail/GitHub, but hasn't had time to do chunks of work during that time period.

If other folks are able to lend @lsm5 a hand, I'm sure he'd love to take this off his plate.

lsm5 added a commit to lsm5/buildah that referenced this issue Jan 16, 2020
@lsm5
Copy link
Member

lsm5 commented Jan 16, 2020

apologies for the delay everyone, going forward, updates will be going to the Kubic project on OBS instead of PPA.

@jayaddison
Copy link
Contributor

@lsm5 Thanks for the link to the Kubic project builds on https://build.opensuse.org and updating the README documentation to list the Kubic apt repo.

It'd be good to have visibility into changes in buildah's binary packaging; I discovered the spec file here: https://build.opensuse.org/package/view_file/devel:kubic:libcontainers:stable/buildah/_service:obs_scm:buildah.spec?expand=1

Do you know how long it typically takes for diffs to become accessible? It'd be useful for debugging and issue diagnosis to see the change history. Currently there's an error when I try to retrieve a revision diff: https://build.opensuse.org/package/rdiff/devel:kubic:libcontainers:stable/buildah?linkrev=base&rev=246

diff-error

@lsm5
Copy link
Member

lsm5 commented Apr 2, 2020

It'd be good to have visibility into changes in buildah's binary packaging; I discovered the spec file here: https://build.opensuse.org/package/view_file/devel:kubic:libcontainers:stable/buildah/_service:obs_scm:buildah.spec?expand=1

The _service file in the OBS repo mentions the spec file location. Currently, it's at https://gitlab.com/rhcontainerbot/rpms/buildah/-/blob/centos-release/buildah.spec . I use the centos-release branch for stable repo and f31 or the latest fedora stable release branch for the testing repo. This is because we publish RC builds to fedora koji which was ok for OBS testing, but not for OBS stable.

The f31 branch mentioned above is a copy of the canonical fedora source at https://src.fedoraproject.org/rpms/buildah/blob/f31/f/buildah.spec .

The centos-release branch gets all the f31 branch changes only when the latest published buildah tag is a stable tag.

I used a gitlab source to mirror the fedora spec because I had a hard time setting up source services with fedora's own dist-git.

The autobuilder job I use for bumping spec files is at https://gitlab.com/rhcontainerbot/pkg-builder/-/tree/fedora-release .

I can include this info on the OBS page and maybe somewhere in the buildah source as well.

Do you know how long it typically takes for diffs to become accessible? It'd be useful for debugging and issue diagnosis to see the change history. Currently there's an error when I try to retrieve a revision diff: https://build.opensuse.org/package/rdiff/devel:kubic:libcontainers:stable/buildah?linkrev=base&rev=246

Not sure about the diff for spec file since the _service file just fetches the latest spec on every push to dist-git. So, I guess it's best to check the git logs for the repos mentioned above.

@jayaddison
Copy link
Contributor

Thank you for the detailed and thoughtful response with references; I'm glad to see this is all more transparent than I originally realized (if involving one or two more steps, perhaps).

I can include this info on the OBS page and maybe somewhere in the buildah source as well.

That'd be much appreciated when you can; please don't let me distract you from any other priority work though.

We can put a lot of this down to my lack of familiarity with OBS (I've spent more time reading Ubuntu, Debian and Alpine package source builds recently) - but anything to make the package builds easier to discover and trust would help.

Not sure about the diff for spec file since the _service file just fetches the latest spec on every push to dist-git. So, I guess it's best to check the git logs for the repos mentioned above.

Got it, thanks. Some of this may be feedback that I should provide on the OBS project itself, since it may be down to issues rendering empty diffs. I'll do that as soon as I can :)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants