New version 1.1.1 was released recently, so i will try to package it.

I volunteer as Maintainer.

I volunteer as Maintainer.

Here it is: D6505

@xulongwu4, thanks for the tip, i wasn't aware of this option, it works now.
I just need to cleanup a bit and i will submit the patch when i'm done.

Yes, tried to update package.yml and then i realized that ipscan changed the way it builds. Now it uses gradle (gradle wrapper) to build.
There are a couple of problems with new build system.
Gradle wrapper doesn't work at all inside solbuild, having some network issues, not being able to download gradle zip.

https://gitlab.gnome.org/GNOME/mutter/merge_requests/600

I have the exact same issue. It started happening after GNOME stack update to 3.32. The problem is with compositor which we use: Mutter, which is also a Window Manager for both GNOME and Budgie.

No worries. I will continue to contribute whenever i can

I see that this was replaced with D6328, so we can close this one.

Bumping version 3.6.2 -> 3.6.3

hmmmm, i can see that this can be installed from third party repository already.
https://github.com/getsolus/3rd-party/tree/master/programming/tools/android-tools

You should include udev rules for android usb devices, so you don't have to use sudo to execute adb command or fastboot command.
You can find udev file here: https://github.com/snowdream/51-android
Ubuntu package for android-tools already contains that udev.rules file (contained it package android-sdk-platform-tools-common)
You can put it in files/ or download it from git and install it using package.yml on correct location /usr/lib/udev/rules.d

Bumping version 3.6.1 -> 3.6.2

Bumped to new release version 3.6.1

What about summary and changelog, should i just link to github releases changelog, because now we jump by two release versions?

in the meantime, new version came out 3.6.0 so i can repackage it
What to do now with this revision? Abandon it and make new one for 3.6.0 or just update this one?

I also see that there is newer version available, so i will try to update it to 3.5.5 and submit patch

I volunteer as maintainer.

try running clear-boot-manager command like this

Updated summary

Can you try to edit kernel options from bootloader? Select kernel and press 'e' (instead of enter) and then delete following from kernel options: 'quiet loglevel=3 splash systemd.show_status=false' and then boot by pressing enter. See what systemd prints out during boot.

Added missing multilib support, tested by building QMK firmware and flashing it on keyboard. Now everything works as expected.

Added missing multilib support

It seems i will have to do some additional work here. I just realized that qmk firmware compiled with this compiler doesn't work on keyboard when flashed. Something is wrong and i need to investigate further.
Also noticed the difference in size for resulting .bin file between using this compiler (101KB) and using precompiled arm compiler binaries from ARM website (83KB).

Create package request and if it gets accepted for inclusion i can help you with packaging.

Looks really useful

Why did you create three identical issues for the same package request?

cleaned up builddeps and rundeps

This strange bug in Guake was fixed in Guake itself in the meantime and new version of Guake was released (3.5.0).
I repackaged Guake for new version myself, see D5924, but nonetheless libvte should be upgraded and it's good that it is put in plan together with GNOME stack update.

Aha, well it's my first patch updating existing package. I will keep it in mind for future package updates.

Fixes T7810

Cleaned up dependencies and reworded some comments in package.yml

Removed arm-none-eabi-gcc as builddep so to avoid circular dependency
Now building barebone gcc compiler inside arm-none-eabi-newlib package
just for needs of compiling newlib without including it in final package.

I'm already working on solution to build gcc inside newlib package.

Yes, i can build gcc barebone when building newlib, but bootstrapping is only needed for this first release, because next time those packages will already be present in repos.

Here we have circular dependency. Package arm-none-eabi-newlib depends on package arm-none-eabi-gcc to be able to build it. Package arm-none-eabi-gcc also depends on arm-none-eabi-newlib. To circumvent this problem on initial build, we need to first build barebone gcc cross-compiler without newlib support and use it to build initial build of arm-none-eabi-newlib package, which can then be used as dependency to build full gcc cross-compiler. Then we have both packages built and we can use them to build final versions of packages with correct dependencies set. We can also use pre-built gcc cross-compiler (or whole toolchain for that matter) to build initial arm-none-eabi-newlib package.

changed component

I have it covered, both for avr and arm.

@BearzR I still have some things to resolve before i submit patch. I talked with @DataDrake on #Solus-Dev channel on freenode.net about some details, and i'm working on improvements.

Previously closed Tasks that relate to this one: T1747, T1748, T1749, T5282

Optional package for debugging - avr-gdb, also standard gnu gcc debugger, usually needs backend for remote target simulavr or avarice.
Here is the tarball: https://ftp.gnu.org/gnu/gdb/gdb-8.2.1.tar.xz
just needs to be built for different target also.

Yeah, seems that way, but there is really no alternative to this kind of software, and it's de-facto standard.

I made a git repo with these package definitions, here it is: https://github.com/chax/solus_pkgs
For now i didn't upload built .eopkg files.

Guys, i managed to build all four packages using Solus packaging system, all from their respective sources.
I might volunteer to be maintainer for those, and also for AVR toolchain (similar to ARM but different arch target).
I just had one problem while building these packages, because we have circular dependency.
I will try to explain it here.

They released new version
https://www.winehq.org/announce/4.3

What's new in this release:

I'm just wondering what's the status of this. Will this be merged/released soon?