sig_altarch/meta
14
0
Issues 24 Pull requests Projects Wiki Activity

Package Update: rocky-release-rpi #19

New issue
Open
opened 2024-10-18 14:25:10 +00:00 by codedude · 1 comment
codedude commented 2024-10-18 14:25:10 +00:00
Owner
Copy link

mentioned in the altarch channel, here

update rootfs-expand to include nvme. description on which package and structure from Skip is here

I've tested this and it works great! submitting this here for tracking

mentioned in the altarch channel, [here](https://chat.rockylinux.org/rocky-linux/pl/7x7gpo96uif75pnpxw1q87niyr) update rootfs-expand to include nvme. description on which package and structure from Skip is [here](https://chat.rockylinux.org/rocky-linux/pl/bqodoo3fatyb58e6hxz9z4y1ca) I've tested this and it works great! submitting this here for tracking
codedude changed title from Package Update: to Package Update: rocky-release-rpi 2024-10-18 14:25:36 +00:00
neil added this to the SIG/AltArch Generic Board Support project 2024-12-12 02:18:20 +00:00
codedude modified the project from SIG/AltArch Generic Board Support to SIG/AltArch 2024-12-20 20:23:47 +00:00
codedude added the
discussion
 label 2024-12-20 20:25:45 +00:00
nezsez was assigned by codedude 2024-12-20 20:26:06 +00:00
sherif was assigned by codedude 2024-12-20 20:26:06 +00:00
thefossguy was assigned by codedude 2024-12-20 20:26:23 +00:00
neil was assigned by codedude 2024-12-20 20:26:33 +00:00
skip was assigned by codedude 2024-12-20 20:26:44 +00:00
codedude commented 2024-12-20 20:28:52 +00:00
Author
Owner
Copy link

currently, the "rootfs-expand" script is being added to the raspberry pi image via multiple methods.

  1. via the raspberry-pi release package
  2. via the kiwi descriptions.

I can see benefits to both methods, however, i can see how maintaining it via a package would make it easier if it needs an update(which is currently the case).

Which method do we as a SIG think is best or which method do we want to maintain?

All comments/feedback welcome

currently, the "rootfs-expand" script is being added to the raspberry pi image via multiple methods. 1. via the raspberry-pi release package 2. via the kiwi descriptions. I can see benefits to both methods, however, i can see how maintaining it via a package would make it easier if it needs an update(which is currently the case). Which method do we as a SIG think is best or which method do we want to maintain? All comments/feedback welcome
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
discussion

   
documentation

   
duplicate

This issue or pull request already exists

  
enhancement

New feature request

  
help wanted

Need some help

  
new_sbc

   
package_request

   
peridot

   
question

More information is needed

  
rpi5
No labels
discussion
documentation
duplicate
enhancement
help wanted
new_sbc
package_request
peridot
question
rpi5
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
SIG/AltArch
Assignees
Clear assignees
No assignees
nezsez
sherif
thefossguy
neil
skip
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sig_altarch/meta#19
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?