sabayon / community-repositories Goto Github PK

Raising an issue after discussing with @geaaru in #sabayon-dev, Community images are growing excessively. Pre-mottainai we had weekly squashes which would flatten the docker image layers (reducing churn), and monthly cache_clean jobs which would end the chains. Under mottainain, I don't think we have either of these, and images are growing unbounded.

We could schedule a mottanai plan which runs the cache_clean job again, but as there's no locking support that I'm aware of, we could easily get into a race condition where the results of the long-running clean-plus-full-rebuild job get replaced by the next execution of the normal job. I think some locking support in mottainai is needed?

I'd expect the package search in https://sabayon.github.io/community-website/ to be sticky. That is, visible even after scrolling down.

Background:
After reading Start to search on the top bar in Website usage I wondered which search. It was out of my viewport at this point.

Ideally the search would be contained in the main navigation. I'll investigate that.

@optiz0r said on IRC that he would the search bar to give some feedback visually when she's in progress.

The location should be updated with an fragment, like #app-misc/example-search and be cached for subsequent requests.

Some questions come to my mind here:

• When to start querying the backend (how many characters need to got typed in? Should the next one be delayed? Imagine users correcting them or typing in quickly)
• For how long should the result be cached? What invalidates it? How is the client/browser informed about the invalidation?
• How should the feedback look like? Can we estimate the time to an reply? (Probably not due to network latency)

Hey team, I'm not sure if this is the right place to report this. If not, I hope someone can point me in the direction of the maintainers of the cinnamon package.

The cinnamon desktop environment is not longer working on Sabayon. This can be demonstrated by installing from the latest gnome ISO (18.05), upgrading all the packages / kernel, then trying to install cinnamon. After install and upon logging into the session, you'll immediately be greeted with a "cinnamon has crashed, would you like to restart?" message. If you attempt to restart, it'll just show up again.

I'm having some trouble finding relevant logs on the system that could point to exactly why this is broken. I've experimented with different versions of python but haven't been able to get it working again.

Anyone have any thoughts or experience here?

Why not Package Sublime Text2/3 for Sabayon?

Hello

I would like to learn the correct way, via the route of least resistance, of safely installing a package from Portage in Sabayon, in such a way that it would be possible to easily update it (i.e. grab latest git code and recompile) either manually or automatically. Specifically: GIMP (=media-gfx/gimp-9999), GEGL and BABL.

While searching for correct ways of doing this, I found conflicting information, and when I check the documentation edit history to get an idea of how relevant it is today vs advice I get in IRC or find in forums, the documentation seems possibly outdated. Well, it leaves me uncertain at best.

I reported this problem in IRC and was asked to open an issue here.

• https://wiki.sabayon.org/index.php?title=En:HOWTO:_The_Complete_Portage_Guide
  This, from 2012, basically says "use portage". No mention of sabayon-devkit, docker or other.
• https://wiki.sabayon.org/index.php?title=HOWTO:_Safely_mix_Entropy_and_Portage
  This, also from 2012 but with minor updates and unsafe shell snippets, basically says "use devkit".
• I also read or was told somewhere to use Docker.

It would be great if someone knowledgeable found the time to merge these articles into one, clear, up-to-date article on how to install a program from Portage in Sabayon, assuming the package in Portage is known to work well in Gentoo.

A few weeks ago, I was surprised that Telegram (an instant messenger) was removed from the repositories.

This evening, @optiz0r told me that it moved to SCR.

I would expect to get an info after the next equo update. @joostruis offered to put a notice on the blackboard if someone else writes the text.

>>> Emerging x11-misc/xneur-0.20.0::sabayon
 * xneur_0.20.0.orig.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                       [ ok ]
>>> Unpacking source...
>>> Unpacking xneur_0.20.0.orig.tar.gz to /var/calculate/tmp/portage/x11-misc/xneur-0.20.0/work
>>> Source unpacked in /var/calculate/tmp/portage/x11-misc/xneur-0.20.0/work
>>> Preparing source in /var/calculate/tmp/portage/x11-misc/xneur-0.20.0/work/xneur-0.20.0 ...
 * Running eautoreconf in '/var/calculate/tmp/portage/x11-misc/xneur-0.20.0/work/xneur-0.20.0' ...
 * Running glib-gettextize --copy --force ...                                                                                                          [ ok ]
 * Running intltoolize --automake --copy --force ...                                                                                                   [ !! ]

 * Failed Running intltoolize !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/calculate/tmp/portage/x11-misc/xneur-0.20.0/temp/intltoolize.out

 * ERROR: x11-misc/xneur-0.20.0::sabayon failed (prepare phase):
 *   Failed Running intltoolize !
 * 
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 1512:  Called eautoreconf
 *   environment, line  786:  Called autotools_run_tool 'intltoolize' '--automake' '--copy' '--force'
 *   environment, line  516:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of `emerge --info '=x11-misc/xneur-0.20.0::sabayon'`,
 * the complete build log and the output of `emerge -pqv '=x11-misc/xneur-0.20.0::sabayon'`.
 * The complete build log is located at '/var/calculate/tmp/portage/x11-misc/xneur-0.20.0/temp/build.log'.
 * The ebuild environment file is located at '/var/calculate/tmp/portage/x11-misc/xneur-0.20.0/temp/environment'.
 * Working directory: '/var/calculate/tmp/portage/x11-misc/xneur-0.20.0/work/xneur-0.20.0'
 * S: '/var/calculate/tmp/portage/x11-misc/xneur-0.20.0/work/xneur-0.20.0'

>>> Failed to emerge x11-misc/xneur-0.20.0, Log file:

>>>  '/var/calculate/tmp/portage/x11-misc/xneur-0.20.0/temp/build.log'

Добавьте зависимость: (Add a dependency:)

dev-util/intltool
    Доступные версии:      0.51.0-r1 ~0.51.0-r2
    Домашняя страница:     https://launchpad.net/intltool/
    Описание:              Internationalization Tool Collection