Comments

• 

  6 months ago by dpock | Reply

  The first thing I've learned about OBS revolves around the way packages are maintained and delivered. And unfortunately, that lesson largely causes the rest of the "exciting" parts of this hack week project to fizzle away.

  I assumed that because I couldn't do: zypper in k9s On the BCI images that this would work for all architectures after adding the right repo. This may still be partially possible, however the architecture for packages may cause the source to vary.

  For instance the k9s package for ARM on factor can be found here: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/k9s

×
Edit Comment 8821
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
The first thing I've learned about OBS revolves around the way packages are maintained and delivered. And unfortunately, that lesson largely causes the rest of the "exciting" parts of this hack week project to fizzle away. I assumed that because I couldn't do: ``` zypper in k9s ``` On the BCI images that this would work for all architectures after adding the right repo. This may still be partially possible, however the architecture for packages may cause the source to vary. For instance the k9s package for ARM on factor can be found here: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/k9s
 
×
Reply to dpock
The first thing I've learned about OBS revolves around the way packages are maintained and delivered. And unfortunately, that lesson largely causes the rest of the "exciting" parts of this hack week project to fizzle away.
I assumed that because I couldn't do: zypper in k9s On the BCI images that this would work for all architectures after adding the right repo. This may still be partially possible, however the architecture for packages may cause the source to vary.
For instance the k9s package for ARM on factor can be found here: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/k9s
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  6 months ago by dpock | Reply

  In my testing to learn OBS, I enabled my project to have ARM published on 15.6 and 15.7. Then enabled the repo to build for those and it gave me the desired results: https://build.opensuse.org/package/show/home:dpock:branches:devel:kubic/k9s

  However, even this isn't strictly necessary as I once suspected. Since ARM builds/packages exist in a dedicated repo. So for the intent of my downstream project, we just add both repos into the image. The ARM ones will be used on arm and ignored on non-arm.

×
Edit Comment 8824
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
In my testing to learn OBS, I enabled my project to have ARM published on 15.6 and 15.7. Then enabled the repo to build for those and it gave me the desired results: https://build.opensuse.org/package/show/home:dpock:branches:devel:kubic/k9s However, even this isn't strictly necessary as I once suspected. Since ARM builds/packages exist in a dedicated repo. So for the intent of my downstream project, we just add both repos into the image. The ARM ones will be used on arm and ignored on non-arm.
 
×
Reply to dpock
In my testing to learn OBS, I enabled my project to have ARM published on 15.6 and 15.7. Then enabled the repo to build for those and it gave me the desired results: https://build.opensuse.org/package/show/home:dpock:branches:devel:kubic/k9s
However, even this isn't strictly necessary as I once suspected. Since ARM builds/packages exist in a dedicated repo. So for the intent of my downstream project, we just add both repos into the image. The ARM ones will be used on arm and ignored on non-arm.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  6 months ago by dpock | Reply

  Ultimately it seems like the k9s package -which was the biggest concern- is ready to use. No notes needed to shift over to use that in our image. However, kustomize binary is very old so needs to be updated.

×
Edit Comment 8827
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Ultimately it seems like the `k9s` package -which was the biggest concern- is ready to use. No notes needed to shift over to use that in our image. However, `kustomize` binary is very old so needs to be updated.
 
×
Reply to dpock
Ultimately it seems like the k9s package -which was the biggest concern- is ready to use. No notes needed to shift over to use that in our image. However, kustomize binary is very old so needs to be updated.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  6 months ago by dpock | Reply

  I've created an initial PR to switch k9s to this source for shell: https://github.com/rancher/shell/pull/294

×
Edit Comment 8836
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
I've created an initial PR to switch k9s to this source for shell: https://github.com/rancher/shell/pull/294
 
×
Reply to dpock
I've created an initial PR to switch k9s to this source for shell: https://github.com/rancher/shell/pull/294
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  6 months ago by dpock | Reply

  I must admit - this project is a bit of a bust at this point.

  In hindsight, it was created with a clear assumption that "SLES is missing these packages due to missing repo sources". From my previous comments it should be fairly clear that this assumption was incorrect. There are multiple community-maintained packages that can be sourced for the development package, which in turn can feed into the repo which could be used in SLES (and there by BCI images).

  That said, the difficulties I found accessing these binaries via BCL images are more reflective of openSUSE/SLES packaging practices. To solve for that may still be possible, however it's not going to be a technical focused solution as I assumed I could attempt here.

×
Edit Comment 8962
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
I must admit - this project is a bit of a bust at this point. In hindsight, it was created with a clear assumption that "SLES is missing these packages due to missing repo sources". From my previous comments it should be fairly clear that this assumption was incorrect. There are multiple community-maintained packages that can be sourced for the development package, which in turn can feed into the repo which could be used in SLES (and there by BCI images). That said, the difficulties I found accessing these binaries via BCL images are more reflective of openSUSE/SLES packaging practices. To solve for that may still be possible, however it's not going to be a technical focused solution as I assumed I could attempt here.
 
×
Reply to dpock
I must admit - this project is a bit of a bust at this point.
In hindsight, it was created with a clear assumption that "SLES is missing these packages due to missing repo sources". From my previous comments it should be fairly clear that this assumption was incorrect. There are multiple community-maintained packages that can be sourced for the development package, which in turn can feed into the repo which could be used in SLES (and there by BCI images).
That said, the difficulties I found accessing these binaries via BCL images are more reflective of openSUSE/SLES packaging practices. To solve for that may still be possible, however it's not going to be a technical focused solution as I assumed I could attempt here.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview