summaryrefslogtreecommitdiff
path: root/pcr
AgeCommit message (Collapse)Author
2022-04-27pcr: imx_usb_loader-git: relicense under CC0Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-27pcr: guix-installer: relicense under CC0Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-27pcr: simtrace2: relicense under CC0Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-27pcr: fomu-verilog-blink: relicense under CC0Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-27pcr: simtrace: relicense under CC0Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-27pcr: python-bundlewrap: relicense as CC0Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-27pcr: remove log4j-1.2Denis 'GNUtoo' Carikli
The 1.2 version of log4j is not only unmaintained / End of life, but it also has lot of security vulnerabilities[1] including at least one critical CVE, 4 high CVEs and 1 moderate CVE. [1]https://logging.apache.org/log4j/1.2/ Link: https://labs.parabola.nu/issues/3261 Reported-by: gap Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-24Move nvramtool from libre to PCRDenis 'GNUtoo' Carikli
Despite what its name suggest, the PCR repository is not only for PKGBUILDs that come from AUR. In the Parabola wiki[1], there is the criteria for packages meant to go in PCR, and we can deduce from what is written there that PCR is for packages that both: * "are not included on official repos of Arch Linux"[1] * "are not considered to be essential enough for the base system."[1] So here even if the nvramtool PKGBUILD doesn't come from AUR, it is meant to go in PCR. [1]https://wiki.parabola.nu/Repositories#.5Bpcr.5D Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-13aur: armv7h: add dosfstoolsDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-12[gmid]: add packagebill-auger
2022-04-12[coreboot-util]: add package (i686 FTBS)bill-auger
2022-04-12[phc-intel]: add packagebill-auger
2022-04-08pcr: armv7h: update android-tools to 31.0.3-3 by syncing with communityDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-04-03[xen]: avoid publishing 'any' docs package to 32-bit reposbill-auger
2022-04-03[xen]: upgrade to v4.16.0bill-auger
2022-04-03[i2p]: upgrade to v1.7.0bill-auger
2022-03-31treewide: Maintainer: GNUtoo: clarify the maintainer situationDenis 'GNUtoo' Carikli
The status quo is that any Parabola hacker is expected to (be able to) modify any packages, and having a single maintainer of a package discourages that practice as people would typically send a patch to the maintainer instead of pushing it directly. So for a start we can add common maintainership on package lacking any "Maintainer: " header for packages in repositories that are supposed to be maintained. As for finding who worked on a given package (in case it could be needed), the git log should have all the information. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-03-31treewide: clarify the maintainer situation on packages lacking oneDenis 'GNUtoo' Carikli
The status quo is that any Parabola hacker is expected to (be able to) modify any packages, and having a single maintainer of a package discourages that practice as people would typically send a patch to the maintainer instead of pushing it directly. So for a start we can add common maintainership on package lacking any "Maintainer: " header for packages in repositories that are supposed to be maintained. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-03-30pcr: remove endless-skyDenis 'GNUtoo' Carikli
Not only it is already in community, but it also needs to be removed (along with the community version) due to licensing issue: some artworks are under a CC-BY-NC license. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-03-02pcr: remove ruby-asciidoctorDenis 'GNUtoo' Carikli
asciidoctor is already in Arch Linux community, and it is more recent. On armv7h we have: community/asciidoctor 2.0.17-1 An implementation of AsciiDoc in Ruby and on i686 we have: community/asciidoctor 2.0.17-1.0 [installed] An implementation of AsciiDoc in Ruby and on x86_64 we have: community/asciidoctor 2.0.17-1 An implementation of AsciiDoc in Ruby So we don't need the pakcage from pcr anymore. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-02-11[tomb]: upgrade to v2.9bill-auger
2022-01-30[secp256k1-git]: remove packagebill-auger
same software is in [community]
2022-01-28[initify]: re-work patchesbill-auger
2022-01-27pcr: libosmocore: fix libremakepkg build due to missing libusbDenis 'GNUtoo' Carikli
Without that fix it builds fine with makepkg if you have libusb installed but it fails with libremakepkg with the following error: | checking for LIBUSB... no | configure: error: Package requirements (libusb-1.0) were not met: | | Package 'libusb-1.0', required by 'virtual:world', not found | | Consider adjusting the PKG_CONFIG_PATH environment variable if you | installed software in a non-standard prefix. | | Alternatively, you may set the environment variables LIBUSB_CFLAGS | and LIBUSB_LIBS to avoid the need to call pkg-config. | See the pkg-config man page for more details. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-01-27pcr: simtrace2: update to 0.8.1 by syncing with AURDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-01-27pcr: simtrace: update to 1.5 by syncing with AURDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-01-27Revert "aur: simtrace: update from AUR"Denis 'GNUtoo' Carikli
In the commit a15f2642006a122148c28e2f9d1032b07c8d082d (aur: simtrace: update from AUR) I accidentally ovewrote the simtrace PKGBUILD with the simtrace 2 one. Both are different software projects meant for two different sim tracer hardware generations. The simtrace software supports only one device named simtrace which uses an AT91SAM7S microcontroller. The simtrace 2 software supports the simtrace 2 hardware that use a SAM3S microcontroller, and it also supports other hardware like the sysmoQMOD that have the same SAM3S microcontroller. This reverts commit a15f2642006a122148c28e2f9d1032b07c8d082d.
2022-01-27pcr: libosmocore: update to 1.6.0 by syncing with AurDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-01-27[initify]: add pkgbill-auger
2022-01-27[pciutils-staticlibs]: upgrade to v3.7.0bill-auger
2022-01-23reset to 648d7822bbill-auger
revert several WIP commits, published accidentally
2022-01-23[mirror-sync]: wip - add pkgbill-auger
2022-01-20pcr: python-redmine: actually make it architecture specificDenis 'GNUtoo' Carikli
In the previous commit, I forgot to actually do the change. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-01-19pcr: python-redmine: make it architecture specificDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-01-19pcr: python-redmine: rebuild for python 3.10Denis 'GNUtoo' Carikli
On Parabola x86_64 we currently have python 3.10: $ pacman -sS ^python$ core/python 3.10.1-2 [installed] Next generation of the python high-level scripting language and python-redmine 2.3.0: $ pacman -sS python-redmine pcr/python-redmine 2.3.0-1 [installed] Python library for communicating with a Redmine project management application but if we try to import redmine in python3 it fails: $ python3 Python 3.10.1 (main, Dec 18 2021, 23:53:45) [GCC 11.1.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import redmine Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'redmine' This is because python-redmine has been built against python 3.9: $ pacman -Q -l python-redmine python-redmine /usr/ python-redmine /usr/lib/ python-redmine /usr/lib/python3.9/ [...] so rebuilding it should normally fix this issue. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-01-19pcr/python-pypump: rebuilt and dropped python2-pypump split package because ↵Andreas Grapentin
upstream depends are gone
2022-01-19pcr/python-hypersocial: rebuiltAndreas Grapentin
2022-01-19pcr/python-efl: updated to 1.25.0, removed python2-efl split package because ↵Andreas Grapentin
upstream dependencies are gone
2021-12-09pcr: Add obfsproxy 0.0.11 from AurDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-12-02Update [pcr/12p] to 1.6.1Freemor
2021-11-12octopi-0.12.0-1.parabola1: updating versionOmar Vega Ramos
2021-10-01pcr: Add abootimg 0.6 from AurDenis 'GNUtoo' Carikli
The Aur package is based on the abootimg-git, Guix and Debian packages. While abootimg only supports old Android images format and its git repository[1] doesn't have new commits since 2012, the abootimg program is used by diffoscope to produce more fine grained diffs between two Android boot images. Without it you end up with a hexdump based diff which isn't very useful. With abootimg you can really debug and fix reproducibility issues when creating Android boot images. Here's what you get between two boot images whose only difference is due to the timestamps in the gzip command used to build the images[2]: --- tests/recovery-i9300-with-root.img +++ tests/recovery-i9300-with-root.img.1 ├── abootimg -i {} │ @@ -13,9 +13,9 @@ │ * load addresses: │ kernel: 0x40008000 │ ramdisk: 0x41000000 │ tags: 0x40000100 │ │ * cmdline = console=ttySAC2,115200 │ │ -* id = 0xa1891d8e 0xdfc327bf 0xe9dc0add 0xb1b7ba27 0x4c251f7d 0x00000000 0x00000000 0x00000000 │ +* id = 0xbd8bda50 0x69a5cbc5 0x9f4e7867 0x3853557e 0x888ff90a 0x00000000 0x00000000 0x00000000 ├── initrd.img │ ├── filetype from file(1) │ │ @@ -1 +1 @@ │ │ -gzip compressed data, was "ramdisk.cpio", last modified: Thu Sep 30 23:04:41 2021, from Unix │ │ +gzip compressed data, was "ramdisk.cpio", last modified: Thu Sep 30 23:02:44 2021, from Unix And without abootimg you have the following instead: --- tests/recovery-i9300-with-root.img +++ tests/recovery-i9300-with-root.img.1 │┄ 'abootimg' not available in path. Falling back to binary comparison. @@ -30,16 +30,16 @@ 000001d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000200: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000210: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000220: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000230: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -00000240: 8e1d 89a1 bf27 c3df dd0a dce9 27ba b7b1 .....'......'... -00000250: 7d1f 254c 0000 0000 0000 0000 0000 0000 }.%L............ +00000240: 50da 8bbd c5cb a569 6778 4e9f 7e55 5338 P......igxN.~US8 +00000250: 0af9 8f88 0000 0000 0000 0000 0000 0000 ................ 00000260: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000270: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000280: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000290: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000002a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000002b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000002c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ @@ -212218,15 +212218,15 @@ 0033cf90: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0033cfa0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0033cfb0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0033cfc0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0033cfd0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0033cfe0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0033cff0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -0033d000: 1f8b 0808 8942 5661 0003 7261 6d64 6973 .....BVa..ramdis +0033d000: 1f8b 0808 1442 5661 0003 7261 6d64 6973 .....BVa..ramdis 0033d010: 6b2e 6370 696f 00b4 5b7b 77db b692 cfbf k.cpio..[{w..... 0033d020: d6a7 c0b1 7dea 3c4c 5292 653b 76cb b6b9 ....}.<LR.e;v... 0033d030: 8d6f 93de a4ce 899d bddd 4db2 3c10 094a .o........M.<..J 0033d040: bc22 0916 0065 298f fdec 3b03 5212 1fa0 ."...e)...;.R... 0033d050: ac74 f7fa b48e 35f8 cd60 30c0 bc40 aa7f .t....5..`0..@.. 0033d060: de3f ef0f fafd fee8 e284 f5f1 870e e8a8 .?.............. 0033d070: 6ffe 1934 3e07 1db8 e6cf d3d5 1ffe 948a o..4>........... And the issue here is not hypothetical as the above show a real bug preventing tests from working in a tool meant to add root access by default in Replicant boot and recovery images. And that bug was really fixed thanks to abootimg. [1]https://github.com/ggrandou/abootimg [2]The ID takes into account the hash of the initrd image. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-09-19[lagrange]: upgrade to v1.6.5bill-auger
2021-09-16pcr: Add android-tools 31.0.2 for armv7hDenis 'GNUtoo' Carikli
The PKGBUILD was taken from the Arch Linux community repository which is at https://github.com/archlinux/svntogit-community as the old URL (git://git.archlinux.org/svntogit/community.git) isn't up to date and according to #archlinux, the migration to gitlab isn't complete yet. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-08-25[pcr/i2p] Keep package Up-To-dateFreemor
2021-08-24pcr: Remove proguardDenis 'GNUtoo' Carikli
The proguard PKGBUILD doesn't provide any source code for proguard, and the Aur package it is based on doesn't either. This is an issue for GPLv2 compliance as well as a practical one: we cannot patch the software if we need to. As for the packages that depend on proguard, the android-sdk package depends on it. However, as far as I know the android-sdk package is a work in progress that didn't progress much since 2018. According to the commit that added it in pcr-testing: commit d424f0813c7bee07cdea2b6863540e1b84abfb0d addpkg: pcr-testing/android-sdk-meta Inspired from https://blog.replicant.us/2017/04/there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better/ I used the Debian sources since they are fully-free, but I still need to add the API level 23 to build an app, and then move this to [pcr] So if someone really wants proguard and/or the android-sdk in Parabola, the solution is to make sure that proguard is built from source somehow. In #parabola in liberachat, bill-auger also agreed with me to the removal of proguard until a way to build it from source is found. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-08-22pcr: python-bundlewrap: bump to 4.7.0 by syncing with AurDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-07-30[lagrange]: add packagebill-auger
2021-07-19[h-client]: wipbill-auger
2021-07-19[mediagoblin]: wipbill-auger
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-25 10:13:37 +0000