- User Since
- May 28 2018, 2:46 PM (86 w, 1 d)
Fri, Jan 17
update to 3.2.3
Dec 18 2019
Dec 16 2019
Dec 13 2019
Update to 3.2.2
They did another release 3.2.2
Dec 12 2019
Dec 11 2019
Update to 3.2.1
Duplicate of T8535
Dec 10 2019
Nov 9 2019
remove wget as builddep
Nov 8 2019
added comment about where is original androidfw archive downloaded from
download androidfw archive from getsol.us/sources
Nov 7 2019
Nov 6 2019
This is the buildlog for previous version on our build server: https://build.getsol.us/logs/git-2.23.0-85.log.gz
This is the buildlog from my local build: (i split it into three files so they can be uploaded to termbin.com):
Added comments explaining addition of deployagent.jar, please re-review.
added child revisions in stack
added this as dependency of podman
removed ostree depencency
removed libexec copy of conmon binary
It's a copy and not symlink in libexec, so. I will remove it because it is unnecessary.
it is not required by podman, but it is recommended. Podman will search for conmon first in libexec path, if it doesn't find it there, then it search it in few other predefined locations, and lastly it looks in PATH. So, this is just a bonus, if you think this is unnecessary, can remove 'podman' from %make_install command.
Nov 4 2019
Nov 2 2019
Nov 1 2019
I'm using it on my laptop for several months, went through several kernel upgrades (and downgrades) and it works very well.
My laptop is UEFI without disk encryption.
Oct 31 2019
So, let me write my findings here.
Oct 30 2019
Our version of Visual Studio Code is built from source, specifically, it is built using this respository: https://github.com/microsoft/vscode/
Yep, understood. I use mostly screen and sometimes picocom.
I know this was closed some time ago, but i would like to revisit this decision for inclusion.
Source has been moved here: https://salsa.debian.org/minicom-team/minicom
Some development is happening, although very slow and no new releases since 2.7.1
We can always build from git if they don't plan to make new release soon.
Oct 29 2019
Works now :)
Oct 24 2019
I pinpointed the issue to one of our kernel patches.
What i did was first compiled kernel 5.3.7 with all the patches and kernel config that we used to compile kernel 5.3.1 (R3571:70ca91bdea72)
After that i just recompiled nvidia-glx-driver with new kernel, rebooted and i got the same error as we had on 5.3.1.
Then i removed all the patches by removing line %apply_patches form package.yml
Recompiled the kernel and nvidia driver, rebooted and BINGO, successful boot with normally loaded nvidia drivers, everything working as it should.
Then i checked the list of patches that we have trying to find main suspect for this problem, and this one seemed like the most probable one.
I re-added %apply_patches line to the package.yml and then just removed suspected patch from list of patches (files/series) and did another re-build of kernel and nvidia drivers.
Another successful boot, which means that this patch, when applied to kernel >5.3.x breaks something with IOMMU and only way to boot successfully with that kernel is to turn off IOMMU via kernel parameter.
Oct 20 2019
BTW, i didn't mean to reopen this one myself, i clicked "Add Action" and forgot i did that while posting the comment.
I guess these things are done by core team only, but i'll leave it like this for now, feel free to overrule me.
Reopen? Reconsider adding libfuse 3 because now we have package that explicitly depends on libfuse 3: fuse-overlayfs T8408
New version is out 0.6.5, but i can't package it until T3023 is resolved.
Oct 14 2019
Since I am a maintainer of podman and buildah i will gladly package this if it gets accepted.
Oct 2 2019
Huh, i know this landed already but title and description refers to wrong version (5.2.8 instead of 5.2.18)
Oct 1 2019
Removed /usr/share/doc folder from distribution as requested
fix after review remarks
Update to 29.0.4
Sep 30 2019
@JoshStrobl i updated to latest budgie-desktop and i can say the fix works for me. Previously, every single boot ended up with tray icons rendered on top of each other, now, i tried three reboots and each time tray icons rendered correctly.
I can confirm that OSD now displays correctly.
Sep 28 2019
@kyrios123 this didn't help, still having this problem with Budgie OSD for volume. Tried downgrade of pulseaudio, tried package that is currently in unstable, and tried your package. Same result for all three packages.
@JoshStrobl I don't think pulseaudio is what is causing it for me, it must be something else from GNOME stack upgrade.
Sep 27 2019
Putting iommu=off as kernel parameter, as @DataDrake suggested, i successfully booted into linux kernel 5.3.1
linux kernel 5.2.13:
Found one issue today:
Sep 20 2019
@Girtablulu can you test with custom iso like last time?
Sep 19 2019
Update to version 29.0.3, cleaned up patches
Update to newly released 3.2.0
Re-tested using test plan
@Girtablulu yes i saw that yesterday
Should i update?
Sep 17 2019
Sep 10 2019
Calling @xulongwu4, he did the last change on fzf package.
Fixed after review remarks
Sep 6 2019
aha, i missed the username, yeah, i see it now LOL, anyway i rebuilt it normally myself by not touching anything else but updating tarball and version/release
We do have mame in our repo R3922, and i just tried to build it myself by changing to version you mentioned here 0.213 and everyhing builds no problem.