Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    14380

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor
    Anyone reading this volunteer in helping us getting together some article we can ship to some a bit serious magazines. Equally useful if someone knows someone that this might be interesting topic to cover? Technical article about changes, improvements and benefits https://armbian.atlassian.net/browse/AR-1497
  2. Igor
    "I looked several days and find nothing - this is how software development looks like". Of i didn't, as in exchange for coffee, I simply can't afford that, nor nobody else can. I am running this place and this place helps you in any case and that is my 2c. That it helps you in best effort manner? That you find people sharing your problems? That we try to work on problems together? That you have opportunity to help? In case you want that driver is fixed, report it here https://bugzilla.kernel.org/ In open source software sometimes this takes months, sometimes years, sometimes its never resolved. If you want that it is fixed, hire someone to fix it for you. You need this fixed. If we would be able to, we would, but with coffee cash this is mission impossible. Auto login / random feature in images? Download a tool https://github.com/armbian/build, read documentation and do whatever you want. Remember we are drinking coffee 24/7 not just when you find a problem in software we didn't make, but we help you make it usable.
  3. Igor
    https://github.com/armbian/community/commit/2dc0a364c8a31e11d708885e0622f1be30402de1
  4. Igor
    How? This way?
  5. Igor
    Update has been initiated. 24 - 48h until it shows up in CDN.
  6. Igor
    You need to download sources, not headers.
  7. Igor
    I think we don't need armhf support.
  8. Igor
    We are running semi automated tests on real hardware (probably the only Linux distribution that do that) and it shows no problems with latest builds, similar to community: https://github.com/armbian/build/actions/workflows/smoke-tests.yml Try bad / another SD card. Armbian works.
  9. Igor
    We are unable to keep this complex install script updated. But I think official install script is now in pretty decent state: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/ I haven't try but it looks like its well maintained.
  10. Igor
    Try this way: https://pivpn.io/
  11. Igor
    At least this part is relatively easy - generate a PR in similar fashion: https://github.com/armbian/build/pull/4611
  12. Igor
  13. Igor
    Indeed. I would bet we have some undetected error in CI build process ... We are putting hopes to bring up armbian-next up as soon as possible as this will also give improved error detection and logging. In case you manage, welcome. Thank you for your input.
  14. Igor
    https://github.com/armbian/build/blob/master/CONTRIBUTING.md#generate-new-patch-template
  15. Igor
    6.1 is currently available only in beta / nightly repo. Switch there first, then you will be able to chose 6.1.y.
  16. Igor
    Event -> Video (with transcripts and comments) 1. Merging NEXT (Jira tickets / updated slides) We discussed progress and problems. Help is needed with: enabling CI developer perspective testing -> test all boot loader, old boot loaders, especially armhf images: cubox-i, odroids, clearfog, ... user perspective testing desktop (currently is broken?) 2. Encourage end-users to open bugs to Jira? Replacing https://www.armbian.com/bugs/ with instructions how to add a bug to Jira seems like a good idea. But this will be community managed without any obligation from Armbian team. Basically introducing a proper bug tracker. Existing AR-XXXX issues that are hardware specific should be moved there. If we have a consensus on that, we have to make a plan, write proper instructions and launch it ... or forget about. 3. Move developers forums to GitHub We were weighting idea to try to encourage more discussion on GitHub and have forum more users oriented. For start, we can try to enable Action - if label discussion is raised, it automatically creates a topic on GitHub discussions. Or similar. If we do that, we should first deal with hardware related bugs. For 2 and 3 we didn't come to any common conclusions except that communication is fragmented around forum, git, irc / discord, emails, PMs ... Comments on all topics are welcome! @Contributor/Maintainer
  17. Igor
    I am open for this idea - one of you needs to take responsibility to make it happen - I'll just run the build once is in the system. Can be discussed on regular developers meetings.
  18. Igor
    until
    This week meeting topics: 1. Checking the progress of Armbian-next 2. Providing stable builds for main TV box image? 3. General goal of weekly meetings: To discuss the three (3) issues of the week Discussions will be documented to respective Jira tickets so they can be tracked Three (3) new issues will be selected from Jira for the next meeting The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. Since meetings are held in public, any registered community member can join and listen. If you want to suggest issues for the next week, you have to be recognized Armbian contributor. If you want to become one, resolve at least one intermediate level issue and tell us something about you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer @MattWestB @jock @SteeMan
  19. Igor
    This was most likely solved by now, but don't have a device to test. @monkaBlyat @Yakov
  20. Igor
    Armbian 22.11 Bullseye / Jammy Kernel 4.9.318 or 6.1.4 Release date: Jan 10, 2023 Legacy kernel has more or less full hardware support, while mainline lack functions such is wireless, HDMI, ... https://www.armbian.com/orange-pi-zero-2/ Looking for maintainer!
  21. Igor
    I forgot sorry. Then Git. For kernel sources it makes - as we make changes to it. Main distributions changes kernel a lot less then we do and they all provide source packages of that modified kernel. If we are talking about https://github.com/armbian/build/tree/master/packages/extras-buildpkgs then this is optional. I don't think anyone would seek source package for those few things we are building there.
  22. Igor
    I also see this concern. Proceeding too strict could backfire in this regard. Build framework (master) is already too advanced for average Joe. Default build process has to remain looking simple. Also regarding patches - we have to expect users will throw in all sorts of garbage patches (exclude sanity check from /userpatches perhaps?) and we have to accept even not formed completely in order. Only we and pro users needs that we are reminded patches are not formed well, others not. Something that should be behind "EXPERT=yes"?
  23. Igor
    Some people had troubles, indeed. Images were replaced today and they have been tested. Try. (download might be slow / not synced to all servers yet / use torrent or retry if you are going to try within next couple of hours)
  24. Igor
    We have to leave personal preferences and grunches behind. The tool should be developed into the direction that this doesn't represent a problem. Since this tool was developed "as it goes", naturally, it has many design flaws. Which resulted in strange decisions. Lets remember that compromises were made out of necessity, lack of time, ... We have to be constructive, improve communication, planning & coordination, ... @balbes150 If a major redesign is needed on top of NEXT, we might need to deal with it later as otherwise we can't bring this in. If a design problem is recognised, open a Jira ticket and describe why you think this or that implementation is bad. If its a small change and if we are united, we will rework it at once, otherwise this will be put into back log. Someone has a better idea?
  25. Igor
    I agree. I am trying to enforce needed coordination and structure by at least organising meetings, shuffling Jira tickets (this should be done by more people) provide tooling and am available for anyone from the team at any moment. At the same time I am trying to recognise / define our limits and scale it into the frame that is controllable. As too small resources provoke stress. Oleg builds his things on arm64, but we have to cover more, perhaps some stupid things for legacy reasons. We can't cut off blindly. I am totally aware that we are dragging 3/4 of those without any point, but someone has to remove them and be sure nothing is broken ... but since this falls off with the NEXT, why wasting time dealing with that? Lets focus into seeking for solutions. And compromises. I am sure we will need to make some - our common goal is have the tool maintainable and modernised. And this is not a fixed thing - when better ways are found and if most of us agree that something can be removed, we remove. If not, its better to stay. There are people out there, that are using this build framework. We don't want to cause stress to them.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept