Generic usb-modeswitch petbuild
Closed this issue · 10 comments
From http://www.murga-linux.com/puppy/viewtopic.php?p=992872&sid=089dd409d2e185f8840d93fe257b9361#992872
Ok it's clear upup bionic and xenialpup should use the deb packages.
But here's a pet pkg compiled a bit differently, it's supposed to update older wce pups, however you might want to test it in a pristine install of upup bb, forcing this pet pkg into the system...
If the new pet works what are the needed changes and do you think it would it be feasible to add the changes to the common builds?
https://github.com/woodenshoe-wi/common32
https://github.com/woodenshoe-wi/common64
Feel free to fork if you want, the only reason the common builds should not be in woof-CE is because they are very cut down and will not boot.
Oops i was not aware of this issue, i actually don't receive emails anymore, so i have to check the github page. I accidentally saw this after clicking a link i posted in puppylinux-woof-CE/woof-CE#1207
The fix is in
0e9b6bf
But it must be tested, this is something i can't test atm, so i was thinking of just editing the pkgs specs to use the deb pkgs.. in fact the change is done but it's not 'committed'
By the way, the raspup stuff needs some cleanup, many pet pkgs are too old, including usb-modeswitch
The first static app to be added to the common repos and raspup is busybox 1.28.3, but not this week.
Well, I can compile but I don't have the hardware to test...
Because "BUILD=" was not incremented in the petbuild the names are the same, but here are the recompiled pets:
https://gitlab.com/woodenshoe-wi/petbuilds-out/raw/2b0e31701c8fe99aff29d51e2c905d05a31408cf/puppylinux/pet_packages-common32/usb-modeswitch-2.5.2-i686_common32.pet
https://gitlab.com/woodenshoe-wi/petbuilds-out/raw/2b0e31701c8fe99aff29d51e2c905d05a31408cf/puppylinux/pet_packages-common64/usb-modeswitch-2.5.2-x86_64_common64.pet
The changes to the compiling logs can be viewed at https://gitlab.com/woodenshoe-wi/petbuilds-out/commit/2b0e31701c8fe99aff29d51e2c905d05a31408cf
Although I do receive emails from GitHub whenever I am @ mentioned or there are pull requests or issues opened for the woof-CE repo, I do not receive emails when changes are made to the petbuilds generic branch. I am guessing it is because the generic branch is not the default branch. If you don't receive emails when an issue is opened then I guess that won't work as a workaround either.
Feel free to use whatever solution works best, if that is using distro pkgs that is fine too. I am just trying to keep the pets in sync with the petbuilds.
If you can run a 64 bit kernel you might be able to compile common64 pets from your favorite 32 bit distro using petbuilds-run_woof.sh
Instructions are at https://github.com/puppylinux-woof-CE/petbuilds/blob/generic/README.md
On the subject of raspup, it was never my intention to make and maintain a release (zip file download of a finished woof-CE build) but I figured if Raspberry Pi build broken #1 no one else could either.
I can't make a commitment to always fix things immediately, only when I have time, and if no one else steps up to make a raspup release I don't want to clutter up the ibiblio repo with pets that might never be used. This didn't help either... puppylinux-woof-CE/woof-CE#1147 (comment)
There is still don570's Fatdog Arm for Raspberry Pi 3 and BarryK 's Quirky Xerus 8.1.4 for Raspberry Pi2 and 3
The only advantage that raspup would have other than being a "Puppy" (which may or may not be an advantage... 😉) is that it should theoretically run on a Pi Zero (I only have a Pi 1 to test which has the same CPU chip).
The current usb-modeswitch package in common* is broken. woodenshoe-wi uploaded the patched version months ago.
This file
should be uploaded to: to http://distro.ibiblio.org/puppylinux/pet_packages-common32/
This file
should be uploaded to: to http://distro.ibiblio.org/puppylinux/pet_packages-common64/
I had not asked peabee to upload the pets because I didn't have the hardware to test them and I didn't know if the distro pkgs were going to be used instead.
If they work and don't need any additional changes, then yes, they should be uploaded.
Uploaded - but is numbering scheme right? -2 should be _2 and should leave common32 as last part of name....?? Also no _DOC ??
You might be right that the dash "-" should be an underscore "_" but the "common32" part is only there when no build number is specified to keep the petbuild scripts happy.
As for the _DOC pet, the old one should still be valid because the version has not changed, only one of the build options.
I could easily add the build number to the petbuild and re-run the build scripts. Is that what you would prefer?
Done - though pets with name ....fd64 look odd in noarch....