A group that committers can join (opt-in to) to be notified of revisions created by contributors (non-committers).
Perfect for grooming and teaching proactive contributors for future mentorship.
A group that committers can join (opt-in to) to be notified of revisions created by contributors (non-committers).
Perfect for grooming and teaching proactive contributors for future mentorship.
update
Fix commit log and pkg-descr
@contact_shiori.com.br Sorry for taking this so long. If you still want to get this in and will maintain the port, I'll push it to the tree.
I'll look into this after dealing with bug 272216 and bug 276478.
In D43478#991623, @arrowd wrote:I pushed this version of pyinstaller-hooks-contrib into the main tree. Christopher, if you think anything should be done differently please provide a patch and I will push it ASAP.
Thanks Alastair for picking this up and sorry Christopher for this taking so long to push.
Pushed in, thank you for your contribution.
I pushed this version of pyinstaller-hooks-contrib into the main tree. Christopher, if you think anything should be done differently please provide a patch and I will push it ASAP.
Move pytest from ${USES} to ${USE_PYTHON}
Move pytest from ${USES} to ${USE_PYTHON}
Move pytest from ${USES} to ${USE_PYTHON} for real this time.
Move pytest from ${USES} to ${USE_PYTHON}
This one seems to be commited, should the revision be abandoned?
Fixed pkg-plist
Currently building and will test on a few boards just to be sure, will commit after.
Additionally, when my usb keyboard (Corsair K65 RGB) is connected my raspberry pi during boot, the boot process becomes really slow especially when loading kernel. I don't know if this problem only occurs only on the 8GB rpi4 though.
Fixed build error on sysutils/rockpro64
In D41193#938512, @manu wrote:In D41193#938505, @minsoochoo0122_proton.me wrote:u-boot-rockpro64 build fails.
# make install ===> Building for u-boot-rockpro64-2023.07.02 gmake[1]: Entering directory '/usr/ports/sysutils/u-boot-rockpro64/work/u-boot-2023.07.02' ENVC include/generated/env.txt UPD include/generated/timestamp_autogenerated.h ENVP include/generated/env.in ENVT include/generated/environment.h CC cmd/version.o CC env/common.o AR cmd/built-in.o CC lib/efi_loader/dtbdump.o CC lib/efi_loader/initrddump.o AR env/built-in.o LD lib/efi_loader/initrddump_efi.so aarch64-none-elf-ld.bfd: warning: -z norelro ignored OBJCOPY lib/efi_loader/initrddump.efi LD lib/efi_loader/dtbdump_efi.so aarch64-none-elf-ld.bfd: warning: -z norelro ignored OBJCOPY lib/efi_loader/dtbdump.efi KSL keep-syms-lto.c /bin/sh: ./scripts/gen_ll_addressable_symbols.sh: not found gmake[1]: *** [Makefile:1718: keep-syms-lto.c] Error 127 gmake[1]: *** Deleting file 'keep-syms-lto.c' gmake[1]: Leaving directory '/usr/ports/sysutils/u-boot-rockpro64/work/u-boot-2023.07.02' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/sysutils/u-boot-rockpro64although scripts/gen_ll_addressable_symbols.sh exists.
I couldn't find any solutions on the internet. Can this be fixed by modifying u-boot-master/Makefile or should I report this to u-boot project?
Likely because of https://github.com/u-boot/u-boot/blob/master/scripts/gen_ll_addressable_symbols.sh#L1
Check if that can be patched to be /bin/sh, if not we need to add bash to the build depends and add a BINARY_ALIAS for it to be in /bin/
In D41193#938505, @minsoochoo0122_proton.me wrote:u-boot-rockpro64 build fails.
# make install ===> Building for u-boot-rockpro64-2023.07.02 gmake[1]: Entering directory '/usr/ports/sysutils/u-boot-rockpro64/work/u-boot-2023.07.02' ENVC include/generated/env.txt UPD include/generated/timestamp_autogenerated.h ENVP include/generated/env.in ENVT include/generated/environment.h CC cmd/version.o CC env/common.o AR cmd/built-in.o CC lib/efi_loader/dtbdump.o CC lib/efi_loader/initrddump.o AR env/built-in.o LD lib/efi_loader/initrddump_efi.so aarch64-none-elf-ld.bfd: warning: -z norelro ignored OBJCOPY lib/efi_loader/initrddump.efi LD lib/efi_loader/dtbdump_efi.so aarch64-none-elf-ld.bfd: warning: -z norelro ignored OBJCOPY lib/efi_loader/dtbdump.efi KSL keep-syms-lto.c /bin/sh: ./scripts/gen_ll_addressable_symbols.sh: not found gmake[1]: *** [Makefile:1718: keep-syms-lto.c] Error 127 gmake[1]: *** Deleting file 'keep-syms-lto.c' gmake[1]: Leaving directory '/usr/ports/sysutils/u-boot-rockpro64/work/u-boot-2023.07.02' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/sysutils/u-boot-rockpro64although scripts/gen_ll_addressable_symbols.sh exists.
I couldn't find any solutions on the internet. Can this be fixed by modifying u-boot-master/Makefile or should I report this to u-boot project?
u-boot-rockpro64 build fails.
# make install ===> Building for u-boot-rockpro64-2023.07.02 gmake[1]: Entering directory '/usr/ports/sysutils/u-boot-rockpro64/work/u-boot-2023.07.02' ENVC include/generated/env.txt UPD include/generated/timestamp_autogenerated.h ENVP include/generated/env.in ENVT include/generated/environment.h CC cmd/version.o CC env/common.o AR cmd/built-in.o CC lib/efi_loader/dtbdump.o CC lib/efi_loader/initrddump.o AR env/built-in.o LD lib/efi_loader/initrddump_efi.so aarch64-none-elf-ld.bfd: warning: -z norelro ignored OBJCOPY lib/efi_loader/initrddump.efi LD lib/efi_loader/dtbdump_efi.so aarch64-none-elf-ld.bfd: warning: -z norelro ignored OBJCOPY lib/efi_loader/dtbdump.efi KSL keep-syms-lto.c /bin/sh: ./scripts/gen_ll_addressable_symbols.sh: not found gmake[1]: *** [Makefile:1718: keep-syms-lto.c] Error 127 gmake[1]: *** Deleting file 'keep-syms-lto.c' gmake[1]: Leaving directory '/usr/ports/sysutils/u-boot-rockpro64/work/u-boot-2023.07.02' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1
In D41192#938225, @manu wrote:On what RPI model have this been tested ? Because updating rpi-firmware sometimes break some models.
Don't see any problems with that patch but I want to test it on different boards just in case, will try to find time this weekend.
On what RPI model have this been tested ? Because updating rpi-firmware sometimes break some models.