Proc0ver

A set of scripts to enable running packages hosted on the procursus repo to run on unc0ver based jailbreaks.

It does this by converting the deb compression from zst to bzip since the DPKG version that comes with unc0ver does not support the zst compression and attempting to upgrade it causes unc0ver to stall during the jailbreak process.

Creating repo:

• Optionally,
  • set the rootDir in change.js to your repo's root directory
  • change the "debs" folder (by default it is rootDir/debs)
• Initialize app by running npm i
• Run by running node change.js (Note first time setups take 3-4 hours due to how many packages there are [4gb>])

Files:

• 'change.js' - primary script for donwloading, upgrading, syncing and converting packages
• 'change.sh' - bash script to change deb compression type
• 'package.js' - standalone script to initialize/update Packages file
• 'debug.sh' - script to start up in debuging mode (Dangerous deletes 'debs' folder)
• 'printErrors.sh' - script to display errors

Sync & conversion process:

• Download page listing all the packages in the procursus repo
• Scrape package links and date of last update
• Filter packages which are already present on disk by comparing their update/upload date to the last update date stored on disk
• Download the packages file from the server and read from disk
• Compare the two packages file, filtering any discrepencies from the packages read fromm disk and updating descriptions and other information
• For each new package,
  • Download it to disk
  • Extract it, remove liblzma dependency and convert compression
  • Recompress it and store new file sizes, hashes and path
  • Add these details (or edit a preexisting entry) to the new packages file
• Write packages file to disk and compress it
• Write any errors to disk and update "lastupdated" file
• Clean up

Note(s):

• By default the scripts downlaod the repository files to the root folder, you can change this by setting the "rootDir" variable in change.js to the full (ideally not relative) path.
• I catch all possible errors, so do not mistake any errors output to stdout as the program failing - you can see these errors after completion in the "errors" file