Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

RSS Bot

Bot
  • Joined

  • Last visited

    Never

Everything posted by RSS Bot

  1. Bump oras-project/oras from 0.16.0 to 1.2.0 by bumping ORAS_VERSION in lib/functions/general/oci-oras.sh. Release notes Sourced from oras-project/oras's releases. Please note that this only shows the release notes for the latest release. New Features oras is compliant with OCI image-spec v1.1.0 and distribution-spec v1.1.0 Introduce brand-new default terminal experience Show live progress for the following commands: oras copy oras pull oras push oras attach oras blob fetch oras blob push The new terminal experience can be turned off via the preview flag --no-tty Support deletion of manifests and blobs in OCI image layout Support X.509 mTLS authentication with OCI registries Preview Features BREAKING CHANGE Registries supporting Referrers API prior to distribution-spec v1.1.0-rc4 will fall back to Referrers tag schema, causing unexpected results of oras attach and oras discover commands Introduce --platform to oras attach for better multi-arch attaching experience, which allows adding referrer artifact to a specific sub-platform Re-purpose the flag --recursive of oras cp from extended copy to copy an artifact or a multi-arch image and its referrers Promote --image-spec to a preview flag from experimental Experimental Features BREAKING CHANGE oras discover shows tree view output by default Introduce formatted output via --format by implementing the specification Formatted output is available to the following commands: oras pull oras push oras attach oras discover oras manifest fetch Examples: --format json to print operation result as a JSON object --format "go-template={{ .digest }}" to print the digest of the manifest using Go template Template can also be specified by --template Introduce oras resolve to get the digest of an artifact Deprecation oras discover: --output is marked as deprecated and succeeded by --format Bug Fixes Fix oras-project/oras#1079: Snaps build cannot read default credentials file Fix oras-project/oras#1096: Mixed request number in the debug mode Fix oras-project/oras#1106: Flag --plain-http=false does not work for local registries Fix oras-project/oras#1129: oras cp -r fails if index has a child manifest as subject Minor fixes Other Changes Improve UX oras discover: show placeholder when artifactType is not presented in an index referrer oras push: show artifact type when pushing files Improve error message based on ORAS CLI error handling guildline Improve identity token input by a new flag --identity-token to replace --password without --username Improve performance Reduce authentication request count fororas copy, oras manifest delete, and oras blob delete Support blob mounting across repositories in the same registry for oras copy Update dependencies Update to Golang 1.22.3 Minor security enhancements What's Changed Since RC.1 Other Changes Improve documentation Update dependencies Detailed Commits bump: tag and release ORAS CLI v1.2.0-rc.1 by @qweeah in https://redirect.github.com/oras-project/oras/pull/1381 fix: remove non-classic snap plugins by @qweeah in https://redirect.github.com/oras-project/oras/pull/1383 fix: oras cp documentation by @TerryHowe in https://redirect.github.com/oras-project/oras/pull/1384 build(deps): bump actions/checkout from 3 to 4 by @dependabot in https://redirect.github.com/oras-project/oras/pull/1385 refactor: Get rid of deprecated PrintStatus method by @TerryHowe in https://redirect.github.com/oras-project/oras/pull/1378 build(deps): bump github.com/onsi/ginkgo/v2 from 2.17.3 to 2.18.0 in /test/e2e by @dependabot in https://redirect.github.com/oras-project/oras/pull/1388 build(deps): bump github.com/onsi/ginkgo/v2 from 2.18.0 to 2.19.0 in /test/e2e by @dependabot in https://redirect.github.com/oras-project/oras/pull/1390 chore: Remove deprecated PrintStatus method by @TerryHowe in https://redirect.github.com/oras-project/oras/pull/1389 doc: verify local files by @qweeah in https://redirect.github.com/oras-project/oras/pull/1386 fix: remove call to deprecated print by @TerryHowe in https://redirect.github.com/oras-project/oras/pull/1392 Full Changelog: https://redirect.github.com/oras-project/oras/compare/v1.2.0-rc.1...v1.2.0 Notes This release was signed with 46D3 369B 393F 6F82 71FD 1CE8 F86E C70D 2B0C 404F (@qweeah's GPG key) which can be found here. View the full article
  2. Description Before, the string would look like this and fails since it's not a valid JSON: {%0A "after": "f6ddb25e6d6affbfdd92b4cd33a9b874254b4a09",%0A "base_ref": null,%0A "before": "0000000000000000000000000000000000000000",%0A "commits": [%0A {%0A "author": ... After, the JSON gets correctly parsed: { "after": "090850f02e35af562dd5adc39c23d423be6bfe15", "base_ref": null, "before": "0000000000000000000000000000000000000000", "commits": [ { "author": { ... Escaping multiline strings is not needed anymore with GITHUB_OUTPUT. See https://github.com/orgs/community/discussions/26288#discussioncomment-3876281 Instead, use the toJSON function that Actions offers to convert the event object to JSON. How Has This Been Tested? [x] Run the fixed workflow once Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings View the full article
  3. Description Fixes https://github.com/armbian/build/pull/6819, see https://github.com/armbian/build/pull/6819#discussion_r1681548553 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings View the full article
  4. Description Budgie desktop packages deprecation fixes. How Has This Been Tested? [x] CI Checklist: [x] My changes generate no new warnings View the full article
  5. Before merging please test. ____ ____ _ _____ _____ | __ )| _ \(_) | ___|___ / | _ \| |_) | | | |_ |_ \ | |_) | __/| | | _| ___) | |____/|_| |_| |_| |____/ Welcome to Armbian-unofficial 24.8.0-trunk Trixie with Linux 6.1.15-legacy-spacemit No end-user support: built from trunk & unsupported (trixie) userspace! System load: 25% Up time: 2 minLocal users: 2 Memory usage: 6% of 3.59G IP: 10.0.0.244 CPU temp: 42°C Usage of /: 10% of 15G patrick@bananapif3:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk2 179:0 0 14.6G 0 disk └─mmcblk2p1 179:1 0 14.4G 0 part /var/log.hdd / mmcblk2boot0 179:8 0 4M 1 disk mmcblk2boot1 179:16 0 4M 1 disk zram0 250:0 0 1.8G 0 disk [SWAP] zram1 250:1 0 50M 0 disk /var/log zram2 250:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk ├─nvme0n1p1 259:1 0 508M 0 part └─nvme0n1p2 259:2 0 238G 0 part View the full article
  6. CONFIG_RTW_DEBUG = n Remove RTW_WARN_LMT Fix aes_encrypt() redefinition errors View the full article
  7. Description The u-boot was tied to a specific tag. Now I am setting it to branch so that updates can be directly pulled into Armbian as well. Also removed a patch that since has been merged into the upstream repository and rebased the patches. The compilation of u-boot used to crash the docker desktop on my macbook, so included a fix for that as well. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh BOARD=khadas-vim4 BRANCH=legacy u-boot Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  8. Legacy: use TAG instead of BRANCH (gives us more control) Current: update DTS files Current: add needed patches up to v1.0.8 Fixup bluetooth node and disable by default (half broke anyway) Misc fixups to bananapif3.wip and spacemit.conf file View the full article
  9. A boot.cmd file still needs to be created, but this is functional. Overlay support is now baked into the syslinux patch. View the full article
  10. Description Alta tested OK, Solitude not tested (hence "WIP") Documentation summary for feature / change Add Libre Computer A311D and S905D3 boards Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article
  11. Description dockerproxy.com is not avaiable from China mainland, but there are many alternative mirrors, for example we can deploy one to cloudflare: https://github.com/ciiiii/cloudflare-docker-proxy I have deployed mine: ghcr.haguro.top Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer: [x] short description: customized GHCR_MIRROR_ADDRESS [x] summary: Default mirror address for ghcr.io set by GHCR_MIRROR=dockerproxy is ghcr.dockerproxy.com. When this address is not availabe, we can set an alternative address with GHCR_MIRROR_ADDRESS. [x] example of usage: ./compile.sh GHCR_MIRROR=dockerproxy GHCR_MIRROR_ADDRESS=ghcr.libcuda.so How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh BOARD=rock-5b BRANCH=edge BUILD_MINIMAL=no DEB_COMPRESS=xz DOWNLOAD_MIRROR=china KERNEL_CONFIGURE=no RELEASE=bookworm BUILD_DESKTOP=yes DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base GHCR_MIRROR_ADDRESS=ghcr.haguro.top GHCR_MIRROR=dockerproxy Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  12. Bumps setuptools from 70.2.0 to 70.3.0. Changelog Sourced from setuptools's changelog. v70.3.0 Features Support for loading distutils from the standard library is now deprecated, including use of SETUPTOOLS_USE_DISTUTILS=stdlib and importing distutils before importing setuptools. (#4137) Bugfixes pypa/distutils#268 Commits 356e9a0 Bump version: 70.2.0 → 70.3.0 822280b Merge pull request #4463 from pypa/bugfix/distutils-34f9518ef c4e64c1 Add news fragment. b01183c Merge https://github.com/pypa/distutils into bugfix/distutils-34f9518ef e221581 Merge pull request pypa/distutils#267 from msys2-contrib/customize_compiler_m... 34f9518 Merge pull request #4410 from pypa/debt/4137-deprecate-distutils-stdlib bacd9c6 sysconfig: skip customize_compiler() with MSVC Python again 4a3406b CI: also set CC/CXX when pip installing with mingw+clang e9f0be9 Merge pull request #4453 from pypa/drop-gitignore 70cda3d Use '.yml' for consistency. Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article
  13. The Panthor kernel driver and Mesa Panfrost driver have passed numerous test cases to achieve official conformance for OpenGL ES 3.1 on the Mali-G610 chip, ensuring reliable performance for users on Mesa version 24.1.1. View the full article
  14. My precious! How Has This Been Tested? Daily Driving Checklist: Please delete options that are not relevant. [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [X] My changes generate no new warnings [X] Any dependent changes have been merged and published in downstream modules [X] Blood Donated [X] Tears produced [X] Contract with the devil signed View the full article
  15. Description enable CONFIG_RTW89_8852BE=m to take advantage of https://github.com/armbian/linux-rockchip/pull/192 GitHub issue reference: https://github.com/armbian/linux-rockchip/pull/192 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] built kernel&image for opi5plus - 8852BE chipset and bluetooth are recognized and working OOB Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article
  16. Description Fix boot from btrfs fs in uboot 2024.07 (backport patch from uboot.next https://github.com/u-boot/u-boot/commit/ee1941e4fec601a8444f49c7dad04ad700d501a6) How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Compile image and boot from (zstd-compressed) btrfs sole rootfs/bootfs partition Checklist: [x] I have performed a self-review of my own code View the full article
  17. Description Reverse commit 75317a0 since this is a special case. Eliminate the real reason for the inability to boot the kernel. Linux kernel hangs in early boot on 32-bit ARM platform, when ftrace 4-byte "mcount" function call location for "_raw_spin_unlock_irqrestore" function straddles icache lines. The problem is present for (cross-compiler) GCC 10, 11, 12. It does not happen when the kernel is compiled with GCC 9, even when condition (1) is satisfied. Detailed description: https://forum.armbian.com/topic/41339-linux-image-legacy-sunxi2451-kernel-6192-is-broken-stuck-at-starting-kernel/?do=findComment&comment=196528 How Has This Been Tested? [x] Test build for sunxi [x] Test work on board BPI-m3 View the full article
  18. Description This patch has been mainlined in the kernel for both v6.6.37 and somewhere in v6.9.y branch too.. There are several reports that it broke rk3328 pinctrl and, as the worst side effect, eMMC controller does not work anymore on rk3318/rk3328 (reports on the forums: this, this and this) I identified the single line that is causing the issue; reverting the single change fixes the bad pinctrl behaviour in my case. How Has This Been Tested? [x] built and tested kernel 6.6.37 on live system [x] built and tested kernel 6.9.9 on live system Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article
  19. Bump u-boot to v2024.07 View the full article
  20. Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. GitHub issue reference: #6940 Jira reference number AR-2419 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Test A create /root/.not_logged_in_yet as noted in #6940 notice the errors disappear Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article
  21. Description sunxi-6.9: Add megous patches and switch EDGE to tag:v6.9.9 How Has This Been Tested? [x] Test build for armhf [x] Test work on BPI-m3 View the full article
  22. Description Follow-up to #6927 Bind mount /dev into the container Remove previous attempt via MKNOD capability which actually didn't affect the issue GitHub issue reference: #6568 Jira reference number AR-2132 Documentation summary for feature / change The issue has been found in other projects as well, and they end up bind mounting /dev into the container: https://github.com/moby/moby/issues/27886 https://github.com/moby/moby/issues/16160 The issues have a lot of discussion on the various aspects of the problem and solutions. The most accepted one is binding /dev into the container. The MKNOD capability doesn't solve the issue, as it turns out. Testing in #6927 was faulty, as the device is available by the next launch, and the most reliable way to remove it that I've found is to reboot the machine. How Has This Been Tested? Fresh system boot, run ./compile.sh build BOARD=odroidm1 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm PREFER_DOCKER=yes Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  23. mainline-kernel: bump to 6.10-rc7 mainline-kernel: bump to 6.10-rc7 just rockchip-rk3588 for now rockchip-rk3588 / edge: rebase onto 6.10-rc7 win: notice how one can actually spot relevant changes now case in point, 1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch -- will drop it in separate commit rockchip-rk3588 / edge: drop patch that landed in 6.10-rc7 1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch landed https://github.com/torvalds/linux/commit/d05f7aff7ac23884ed9103a876325047ff9049aa View the full article
  24. thinkpad-x13s: bump to jhovold's wip/sc8280xp-6.10-rc7 thinkpad-x13s: bump to jhovold's wip/sc8280xp-6.10-rc7 View the full article
  25. Description Each family should build the same kernel. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh kernel BOARD=armsom-sige5 BRANCH=vendor DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.