- User Since
- May 28 2018, 2:46 PM (72 w, 6 d)
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.
Mon, Oct 14
Since I am a maintainer of podman and buildah i will gladly package this if it gets accepted.
Wed, Oct 2
Huh, i know this landed already but title and description refers to wrong version (5.2.8 instead of 5.2.18)
Tue, Oct 1
Removed /usr/share/doc folder from distribution as requested
fix after review remarks
Update to 29.0.4
Mon, Sep 30
@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.
Sat, Sep 28
@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.
Fri, Sep 27
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.
Sep 4 2019
silly little comment on silly little task
Sep 2 2019
I like the fact that it will be re-written in go. I will try to use those two functions more from now on.
Yep, i know it is mentioned in packaging docs, but i assumed as i've been maintaining few more complex packages that others do it manually like me, because it's easier to manually increment release number than call ybump and fix broken yaml afterwards. Most probably the rewrite should remove ruamel-yaml as dependency so you can also deprecate that package from repo because nothing else depends on it.
Now, there is one other thing that i would like to point out, and that is that in some cases both ybump and yupdate sometimes break package.yml.
For example, if source item is long line, ybump will break that line into two lines and produce invalid yaml.
Another example is if you have multiple sources and use yupdate, it will delete all the other sources and update only one of the sources with "new version".
So, i did a bit of testing and source code inspection of ypkg from https://github.com/getsolus/ypkg
It appears that ruamel_yaml is used only in ybump and yupdate.
I did few tests with both ybump and yupdate on few of package.yml files.
Then i upgraded ruamel-yaml using pip2 and did those tests again on same package.yml files.
Not only that it worked with newer version of ruamel-yaml, but it worked identically, that is, result was the same.
Aug 30 2019
Yep, i will try to test it and check where it used in ypkg source. I will write my findings here.
While you updated software center and site help center, 3rd-party repo still contains android-tools.
I know that this 3rd-party repo is planned to be completely removed some time in the future, but since some people do in fact still use eopkg3p tool to upgrade 3rd-party packages through terminal, it will overwrite installed version (from main repo) of android-tools and replace it with 3rd-party version because of greater release number. I can make pull request to 3rd-party github repo, but i was thinking that this would be done by someone with direct access to this github repo, so i just left it.
git commit author update
Updated package.yml with correct licence and component, added more detailed testplan
Aug 29 2019
git commit author update
You need to run make. That way you will get changes on those files. But first you need to setup local environment for solbuild.
Read articles that i linked in original issue. Start with this one: https://getsol.us/articles/packaging/building-a-package/en/
Why did you open new task when you were the one that opened original task T8268.
As someone who opened original task you should've got notifications that it is resolved.
For existing package, you must find its repo and clone it locally instead of creating new dir as packaging tutorial explains it.
Since you've come this far, why don't you try to update/fix it yourself and then submit patch. It shouldn't be to hard.
Set https instead of http for fetching tarball
Aug 28 2019
Aug 27 2019
If this gets accepted for inclusion, i volunteer as maintainer.
I already successfully packaged it locally because it's very simple, but we need to include another library as dependency (ucl compression library).
Ok, so i'm not alone.
Can somebody else test this on their laptop?
Aug 26 2019
Those two Dim options work for me no problem, they dim my external display, and i don't get asked for superuser authentication.
Actually i just realized that this Dim label is actually a button and you can select different output. This way i can dim my laptop screen also.
But using this "Light" slider is what asks me for superuser authentication. Clicking on Light label gives me only one option "nvidia_0".
Opening Settings->Power and changing Screen brightness slider value from there works normally but changes it only for my laptop screen.
What is the status of this? Should @Staudey remove it from 3rd party repo now?
Aug 24 2019
Aug 23 2019
Cleaned up builddeps and rundeps, fixed make_install for correct libdir
Cleaned up builddeps and rundeps
Aug 22 2019
I might need to add runc as rundep
Hmm i might need to add runc as rundep
Aug 21 2019
Aug 20 2019
Removed all the files from $pkgfiles fetching them now from upstream
cleaned up package.yml
cleaned up package.yml
removed unnecessary builddep
removed unnecessary %configure
Those are config files and their manpages explaining how to configure them. I think they are not part of the upstream git repository because i couldn't find them there, but i found them both in fedora package and arch package (that's where i got them from). I just noticed that seccomp.json is also provided by podman package (but on different path) so i will see if i can remove it. I know that registries.conf is definitely needed but we probably don't need manpage for it. I will dig a bit more about what we must keep and what i can just remove.