Giters

procount / pinn-os

os-images for PINN

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

partitions.json for batocera has wrong info for all versions plus adding new RPI4 build

nuwonda opened this issue · comments

commented

a couple of lines need updating in the batocera partitions and os json file.

partitions.json

 "label":                     "BATOCERA",

it's not RECALBOX

  "partition_size_nominal":    3096,

1.2GB is not enough space, users will not be able to update batocera. 3GB is minimum.

  "uncompressed_tarball_size": 1602,

310 is not the correct value. 5.26 is 1602

os.json
url for batocera changed to batocera.org (https://batocera-linux.xorhub.com/" is no longer valid)
rpi4 hex revisions added
entry for beta and stable possible
password changed to mirror batocera default password
download size changed to fit 5.26 size

{
"name": "batocera_RPi4",
"version": "5.26",
"release_date": "2020-04-15",
"description": "batocera.linux, the open source retro gaming console",
"url": "https://batocera.org/",
"group": "Games",
"username": "root",
"password": "linux",
"supports_usb_boot": true,
"supports_usb_root": true,
"supports_backup": true,
"download_size": 822813660,
"supported_hex_revisions": "3111,3112",
"supported_models": [
"Pi 4 Model B",
"Pi 4 Model B Rev 1.1"
]
}

for the os list json here's the changes required to add RPI4 beta and stable builds:
beta:

        "tarballs": [
            "https://batocera.org/upgrades/rpi4/beta/last/boot.tar.xz"
        ],

stable (not available yet)
"tarballs": [
"https://batocera.org/upgrades/rpi4/stable/last/boot.tar.xz"
],

I created my own jsons and install went fine, this is just on case you want to update the PINN entries here.

commented

just noticed, wrong place! will do. cheers

commented

this is the problem if OS's don't have their own NOOBS files but do have the correct tarballs.
They can get "out of sync". eg. All the batocera issues were correct at the time of creating the files.

@procount
What would be a good solution for this?
Always host the tarballs ourselves?
So we always need to manually do updates?
That sounds annoying. haha

Also, this looks interesting:
https://downloads.raspberrypi.org/os_list_imagingutility.json

commented

@nuwonda
Want to do a pull request with the fixes to my git?

Fork my pinn-os.
Create new branch "batocera-fix". Make your changes.
Commit them to that branch. Pull request that branch to my master.

commented

@matthuisman sure can do. want me to add rpi4 as well?

commented

Sure, just call it batocera_RPi4 please

commented

What would be a good solution for this?
Always host the tarballs ourselves?
So we always need to manually do updates?
That sounds annoying. haha

There isn't a good solution.
That's why I mostly host them myself on sourceforge.
It's a pita. And why they get a bit out of date sometimes.
I think the only one I have that is like that is Arch, so I have to update the meta files every once in a while to keep them in sync.

Also, this looks interesting:
https://downloads.raspberrypi.org/os_list_imagingutility.json

Yes. Have you not seen this post on the best way to install PINN:
https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=142574&p=1644231#p1638508

commented

i did a push with the changes. the only thing i didnt update is rpi1 and 2 bato folders as I dont download those so I dont have the current sizes. I updates the os lists for all rpi models though to have 3GB nominal partition size, cause it needs it to be able to update. once rpi4 builds are stable, can change the tarball to point to the stable dir. cheers!