User Details
- User Since
- Aug 3 2016, 2:19 AM (357 w, 2 h)
Mar 31 2018
Aug 20 2017
Added features and fixes from this release
Aug 18 2017
This fixes T4321
Works correctly on Fedora 26 Gnome fresh install with updates, running Epiphany 3.24.3
Diff between the schema I pulled from Solus (first input file) and the local one on the Fedora VM:
diff org.gnome.epiphany.gschema.xml /usr/share/glib-2.0/schemas/org.gnome.epiphany.gschema.xml 135c135 < <schema path="/org/gnome/epiphany/web/" id="org.gnome.Epiphany.web"> --- > <schema id="org.gnome.Epiphany.web">
Jun 26 2017
Packaging Changes
Jun 18 2017
Fixed:
- component to programming.library
- removed %configure step as %autogen takes care of that
- use --disable-static instead of manually removing the static library file
- run libtool --finish %libdir% after install to satisfy the libtool warning about it
May 29 2017
Looks like this project doesn't have real released versions and instead has zip archives using the commit hash. How should the version be entered in the package.yml for this?
Looks like this needs dbus-c++ to build, but it hasn't been updated since 2012, does that make it a non-starter for inclusion in the repos?
May 19 2017
Sorry, got ahead of myself. I'll make sure they're accepted from now on.
May 18 2017
I'm working on packaging T3684: pylint and many of the python packages it depends on can use tox to run tests so I figured I'd package D139: Initial commit of python-tox while I'm at it.
Sorry, forgot to git pull. I made the changes and messed up the edit and ended up submitting a new request at
Jan 31 2017
Nov 20 2016
Oct 30 2016
Pull request is here: https://github.com/solus-project/3rd-party/pull/73
Here's what I've come up with for getting insync working:
I built the eopkg using sudo eopkg build pspec.xml and installed it and it seems to be working, the tray icon works as it did in Fedora and is downloading files correctly for now.
Let me know if they look alright, and is there anything I should be doing to generate the pspec.xml file? I hand edited the pspec.xml (and actions.py) based off of ones used for a program in the 3rd party repo already. Likewise I'm not sure if there are any guidelines on where the files should be installed specifically.
Let me know if I missed anything.
Thanks!
Oct 26 2016
Sep 17 2016
Sep 12 2016
Aug 30 2016
Aug 21 2016
Aug 16 2016
Sorry for my late response on this, thanks for taking a look at my patch.
Aug 9 2016
It runs fine if you just extract the Linux zip file and double click the museeks executable
Aug 8 2016
Good to hear! Glad I could help, and I've said it already but thanks again for your help through this tougher patch, I would've been totally lost otherwise.
Sorry about that, I'll clone and make the changes from that, and fix the whitespace!
@ikey submitted it as T100: kodi patch task, was that correct or should I have appended it to this one?
Gah, almost had it. I'll submit a patch task here soon.
I'm trying to build it now, hopefully have enough disk space. The most recent one disables the building shared libraries and enables libbluray support.
Awesome! Was that with the most recent package.yml I had attached?
Thanks! I'm rebuilding now with the shared ffmpeg and disabled static.
Looks like there's a configure option --with-ffmpeg that has some options, it defaults to building its own though so I'm working on that.
@ikey Perfect, that worked like a charm, thanks!
Here's a highly work-in-progress package.yml that I've made so far. Right now I'm having issues with the configure step linking to libcrossguid with any combination of --enable-static and --enable-shared.
Aug 7 2016
Aug 6 2016
Aug 4 2016
If it helps, I found this guide to be really useful:
I believe so, btrfs-progs is supposed to be more or less kernel independent. If there is a feature that's not supported by the kernel, the command just exits with an error.