• Content Count

  • Joined

  • Last visited

About going

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Redesigned the branch packaging. 'NEWPKG', 'FORCE_CHECKOUT' and 'IGNORE_UPDATES' variables is no longer used. Added a new ability to work offline. ./compile.sh OFFLINE_WORK=yes and sources will simply return to their original state without checking on the Internet.
  2. As of today, may 11, the following packages are being built, installed, and uninstalled without errors: 43K - armbian-config_20.05.0-trunk_all.deb 6,2M - armbian-firmware_20.05.0-trunk_all.deb 101M - armbian-firmware-full_20.05.0-trunk_all.deb 56K - linux-dtb-current-sunxi64_20.05.0-trunk_arm64.deb 11M - linux-headers-current-sunxi64_20.05.0-trunk_arm64.deb 29M - linux-image-current-sunxi64_20.05.0-trunk_arm64.deb 1,1M - linux-libc-dev-current-sunxi64_20.05.0-trunk_arm64.deb 123M - linux-source-current-sunxi64_20.05.0-trunk_all.deb 269K - linux-u-boot-current-orangepipc2_20.05.0-trunk_arm64.deb The disk image has been assembled, and the locale with native languages is working. 1000M - Armbian_20.05.0-trunk_Orangepipc2_bionic_current_5.4.38_minimal.img Started checking the health of packages on the Board - linux-source, linux-libc-dev, linux-headers
  3. For the past 10 years, I have been moving evenly and rectilinearly in an inertial frame of reference called OpenSUSE. I had to first read about creating Debian packages and look here: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/ Both Ubuntu and OpenSUSE distributions start with the kernel source package, which contains a set of scripts and rules for further build. This has a sacred meaning. To get started, I took two scripts from the v5.7-rcX core as a basis and put them in packages/armbian/builddeb packages/armbian/mkdebian checked the build process for bionic current core v5.4.y This initial state can serve as a starting point. How it works? In armbian/build git remote add armbian-build https://github.com/The-going/armbian-build.git git fetch armbian-build packaging git checkout -b packaging armbian-build/packaging ./compile.sh NEWPKG="true" NEWPKG="true" - no longer used This repository branch changes its commit history by following the flight of thought and eliminating garbage. Update it with the -f, --force key git pull -f armbian-build packaging Please test and write your wishes and thoughts here. At this stage, we can opt out of general-packaging-5.X.X.patch
  4. Sorry, colleagues. Work in progress. I have a number of problems and can't allocate enough time to finish.
  5. An option that works but needs to be tested: https://github.com/The-going/armbian-build/tree/packaging I didn't do PR, I want You to look at it.
  6. In the continuation of the conversation: PR #1836
  7. I have a great desire to get this package starting from version 5.4. and so on. I can make corrections for this if YOU give the green light. Most probably ... What are the artefacts left ? symbolic link ? It doesn 't really matter what changes occurred in the target directory after the package was installed. A simple prerm script that simply clears the target directory will solve the problem . To make corrections?
  8. Two questions about this patch. 1 - we add a line to the scripts/package/builddeb file +libc_headers_packagename=linux-libc-dev-"$BRANCH$LOCALVERSION", but we don't actually build this package. That's how it should be, or it's just not finished. 2 - the postinstall script in the linux-headers package performs actions in the installation directory. Therefore, the package cannot be deleted cleanly using the standard 'dpkg -r' method. Perhaps the work is not finished here either. If you need to modify it, I can offer my own version.
  9. I apologize if I seem rude. I use automatic translation. Sometimes the meaning can turn over. And thank you. I started working with github. Now I understand why you don't accept the patches as a patch file
  10. Igor, let's try to open the eyes of users. Please apply these two patches. 0001-Correction-stderror-to-file.patch 0002-Install-to-see-the-status.patch
  11. Thanks. I saw the applied patches for testing. I read your links and realized that it is customary to make changes in a separate branch and then pull request. Of course, first we need to discuss with the community the need to develop new functionality. I will do so in the future. I'm currently laying out a number of patches that I think are the most important. Although it is not a tradition. You can apply them on your own behalf, after testing, if you see them reasonable. I don't claim authorship. Thank you for your understanding.