drobbins
-
Posts
513 -
Joined
-
Last visited
-
Days Won
282
Content Type
Profiles
Forums
Blogs
Posts posted by drobbins
-
-
Oh, and you also get the QT5-based GUI without having to emerge all of the QT5 libraries. This is very handy for GNOME users. Note that when dropbox is started in GNOME, you will have a little GNOME task icon for dropbox.... It contains dropbox settings...
-
Hi All,
I've just massively reworked the net-misc/dropbox ebuild to provide a much better experience in Funtoo and you should see this showing up in the next few hours. I couldn't get the Gentoo dropbox working reliably. Here is a list of all the changes:
- Updated to dropbox-39.4.49.ebuild
- No longer has an initscript
- It now sets up ~/.dropbox-dist for each user who sets up dropbox (rather than having a system dropbox install)
- You don't need to be in the "dropbox" group to use the dropbox nautilus (gnome file browser) extension
- gnome support is built-in (as long as "gnome" is set in USE, which it is if you are using the GNOME mix-in.)
-
Reworked the python 'dropbox' script to provide a better user experience and be optimal for Funtoo:
- if you start "dropbox" for the first time from GNOME, it will start a GTK+ installer to set up dropbox for you.
- if you don't have a GUI, you can still install dropbox
- The above two features are existing features of dropbox that were somewhat borked in Gentoo.
- At the end of the setup process, you are given instructions on how to enable dropbox on startup.
- dropbox command-line tool is also included.
Please note that if you have nautilus-dropbox installed, you will need to remove it.
This should result in a really nice experience for dropbox users.
Use as follows:
# emerge dropbox (make sure it's 39.4.49 -- this is the new version.) (as regular user:) $ dropbox start -i
This will initialize the ~/.dropbox-dist directory for the user via a command-line or GTK+ interface. Once this is done, dropbox start should be added to your .bash_login and/or .xprofile and can be run immediately to start dropbox in your current session.
Since the ebuild is completely new, the possibility of bugs exist. Please report bugs at https://bugs.funtoo.org . Thanks.
-Daniel
-
I think it could work.
-
I can delete it for you. Send me a PM with details.
-
-
Make sure you enter your username in *lowercase*. See if that helps.
-
Hi All,
ego-2.3.2 has been released and will show up in meta-repo soon. It is keyword-masked and is available for testing. This version has been tested quite a bit by the funtoo dev team so we expect it to be pretty solid but we want to give it a few days of testing by users before unmasking. New features and bug fixes include (please note there is an important one listed below....)
- Robustness fixes for partially-initialized repositories.
- Fix for term sizing
- New 'config' module for reading and setting ego.conf settings from cmdline.
- allow kit_depth to be specified in ego.conf.
- IMPORTANT CHANGE: replace /etc/portage/repos.conf with a real directory, and now ego will generate repos.conf entries for kits and keep them up-to-date for you. All files it manages and creates begin with the "ego-" prefix.
-
Hi All,
Just wanted to let everyone know that keychain 2.8.4 has been released and we have our official development repository for the project hosted on github: https://github.com/funtoo/keychain. Also welcome Ryan Harris @x48rph as the new official maintainer of keychain! This new release has been fixed to work with GPG2 and has various other fixes. You can learn more about keychain on its official landing page: https://www.funtoo.org/Keychain .
Regards,
Daniel
-
Also note that the next release of ego will auto-generate repos.conf entries and automatically convert the symlink to a real directory.
-
Also note that in your /var/git/meta-repo/kits/xorg-kit directory, you will have a README.rst file with the latest info on security fixes in the kit. The 1.19-prime README.rst is also readable here (this is our original source for the README.rst that ends up in your kit): https://github.com/funtoo/kit-fixups/tree/master/xorg-kit/1.19-prime
Also note that if you aren't explicitly specifying a kit for xorg-kit in /etc/ego.conf, your system will automatically switch to using the new kit. If you would like to stick with 1.17-prime for some reason, you can add this to your /etc/ego.conf:
[kits] xorg-kit = 1.17-prime
This is generally not recommended unless you have a specific reason to stick with 1.17-prime. We will continue to maintain 1.17-prime as well.
-
Also note that in your /var/git/meta-repo/kits/xorg-kit directory, you will have a README.rst file with the latest info on security fixes in the kit. The 1.19-prime README.rst is also readable here (this is our original source for the README.rst that ends up in your kit): https://github.com/funtoo/kit-fixups/tree/master/xorg-kit/1.19-prime
-
Hi All,
xorg-kit 1.19-prime will be the default after the next tree update. It includes xorg-server-1.19.3 but with backports of all security fixes through (and including) xorg-server 1.19.5.
-
Welcome back :)
-
Hi All,
Oleg is currently working on getting 1.19-prime ready to be the default xorg-kit, replacing 1.17-prime. We are adding some CVE fixes and mesa has been bumped to a non-release candidate. In the next day or so, if you do not have 1.17-prime specified in /etc/ego.conf, your xorg-kit will automatically switch over to 1.19-prime after ego sync.
-
Excellent! Thanks for taking the time to post here which allowed me to track down the bug in ego.
-
Yes -- the current code is fairly convoluted. It uses a depgraph to build up a dependency tree and then starts with the leaf nodes and works its way up the tree. The source code is here:
https://github.com/gentoo/portage/blob/master/pym/_emerge/depgraph.py
I've begun working on adding clearer documentation to the code but there is a lot more work to do on that front.
-
See this thread:
We found a bug in ego-2.3.0 which was resulting in python USE settings not getting updated properly. Using the version from git as per my instructions will get this working for you so you can run "ego profile update" and get your profiles set up correctly. Or just emerge ego-2.3.1 when it shows up in meta-repo, soon.
-
Ego-2.3.1 has been released, and contains a critical fix -- version 2.3.0 didn't properly update python-kit USE settings in the profile when 'epro update' was run. The new 2.3.1 version will strip old python-related USE settings and add updated settings. This could cause problems on upgrade from a non-kitted system or problems when switching python implementations.
-
I've released ego-2.3.1 so it should be showing up in meta-repo soon. Until then, it is available via git as above.
-
I believe I've identified and fixed the bug in ego's git master. Try this:
# cd /var/tmp # git clone https://github.com/funtoo/ego # cd ego # ./ego profile update
This should result in the profiles being properly updated with python-kit references. This code was lost in the migration to the new profiles API in ego 2.3.0. I'm going to roll this out as ego-2.3.1.
-
I think you may have encountered a bug, as 2.3.0 contains a fresh rewrite of the profile code. Please simply copy and paste all of the lines in my profile that end with "3.6-prime" but change references to "3.4-prime", and then paste them into /etc/portage/make.profile/parent. This will give you the settings you need. I think once they are there, they will not be removed, but they may not be getting added properly. I will investigate. In the meantime, let me know if that makes things start working for you.
-
This means you are running too old a version of ego or it is misbehaving. Ensure you have ego-2.3.0 installed and run 'ego sync; ego update'. You should see something like this in make.profile/parent:
core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit core-kit:funtoo/1.0/linux-gnu/build/current core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-westmere core-kit:funtoo/1.0/linux-gnu/flavor/desktop core-kit:funtoo/1.0/linux-gnu/mix-ins/gnome ruby-kit:funtoo/kits/python-kit/3.6-prime java-kit:funtoo/kits/python-kit/3.6-prime net-kit:funtoo/kits/python-kit/3.6-prime games-kit:funtoo/kits/python-kit/3.6-prime media-kit:funtoo/kits/python-kit/3.6-prime security-kit:funtoo/kits/python-kit/3.6-prime science-kit:funtoo/kits/python-kit/3.6-prime core-kit:funtoo/kits/python-kit/3.6-prime kde-kit:funtoo/kits/python-kit/3.6-prime ml-lang-kit:funtoo/kits/python-kit/3.6-prime xorg-kit:funtoo/kits/python-kit/3.6-prime text-kit:funtoo/kits/python-kit/3.6-prime core-hw-kit:funtoo/kits/python-kit/3.6-prime editors-kit:funtoo/kits/python-kit/3.6-prime php-kit:funtoo/kits/python-kit/3.6-prime dev-kit:funtoo/kits/python-kit/3.6-prime perl-kit:funtoo/kits/python-kit/3.6-prime xfce-kit:funtoo/kits/python-kit/3.6-prime nokit:funtoo/kits/python-kit/3.6-prime gnome-kit:funtoo/kits/python-kit/3.6-prime lisp-scheme-kit:funtoo/kits/python-kit/3.6-prime haskell-kit:funtoo/kits/python-kit/3.6-prime desktop-kit:funtoo/kits/python-kit/3.6-prime python-kit:funtoo/kits/python-kit/3.6-prime
-
This has been added to ego-2.3.0.
-
OK, well in theory that should work. I can't tell you exactly what is going wrong -- sounds like more research is required.
Funtoo improves Dropbox
in News and Announcements
Posted
Note that the original ebuild I wrote had quite a few issues -- all should now be fixed, and the fixes will be showing up in the -r1 version of the ebuild that should be appearing in meta-repo in a bit. Fixes for gnome and non-gnome installs, python fixes, and now should be quite solid. Thanks for the bug reports!