Re: [sabayon-dev] ISO Testing Results

[Joost Ruis]

I will bump Samba and put it in Limbo.

On Tue, Jun 19, 2018 at 8:26 PM, Jerrod Frost  wrote:

> Its not the firewall. It works fine from Linux machine to Linux machine.
> Evidently my issue isn't SMBv3 but SMBv3.11 .
>
> On Mon, Jun 18, 2018 at 5:54 PM Joost Ruis  wrote:
>
>> Firewall off?
>>
>> On Mon, Jun 18, 2018 at 6:11 AM, Jerrod Frost 
>> wrote:
>>
>>> Just an update. I've been fiddling with SAMBA and Windows 10 lately and
>>> finding I cannot connect to my Win10 Shares. Evidently this is due to SMB
>>> v3.11 in Windows 10 which isn't fully supported? So I decided to do some
>>> digging. We're currently using an EOL version of SAMBA! 4.5 is Discontinued
>>> and EOL as of 2018-03-13.  Current Stable is 4.8. Is it possible to get a
>>> package bump to stable?
>>>
>>> On Fri, Jun 15, 2018 at 1:33 PM André Jaenisch 
>>> wrote:
>>>
>>>> Hi, Jerrod,
>>>>
>>>> thank you for your efforts.
>>>>
>>>> Patreon / Liberapay will make it on the website as soon as I get
>>>> positive feedback / green light for pushing https://next.sabayon.org/
>>>> to production.
>>>>
>>>> Right now I'm gathering feedback.
>>>>
>>>> Kind regards
>>>>
>>>>
>>>> Ryuno-Ki
>>>>
>>>>
>>>>
>>>>  Ursprüngliche Nachricht 
>>>> Von: Jerrod Frost 
>>>> Gesendet: 15. Juni 2018 05:39:37 MESZ
>>>> An: sabayon-dev 
>>>> Betreff: [sabayon-dev] ISO Testing Results
>>>>
>>>> ###COMMON ISSUES###
>>>>
>>>> Calamares - Encryption is broken. Could we go with FDE and decrypt via
>>>> GRUB2? It seems to be using GRUB to decrypt, but upon booting asks for
>>>> password to mount /dev/mapper/luks-X which doesn't exist?
>>>>
>>>> Still using GRUB 2.02 BETA3. Is there a reason we have not moved to 2.02
>>>> stable?
>>>>
>>>> Donate to Sabayon -> Page missing Patreon/librepay ?
>>>>
>>>> minetest - only the engine is installed, not the game. need to install
>>>> package minetest_game
>>>>
>>>> First set of updates pull in KDE packages for non-KDE spins? This one I
>>>> don't quite understand.
>>>>
>>>> ###WISH LIST ITEMS###
>>>>
>>>> 4.17 kernel not in Repository; I'd like to personally make an
>>>> unsupported
>>>> spin like the forensics edition, but for ryzen APU users as 4.17 is a
>>>> requirement.
>>>>
>>>> Unified Icons? Can we come up with a set of icons that are the same for
>>>> every spin?
>>>>
>>>> Unified LightDM with Slick Greeter? Keeping the same DM across the
>>>> spins.
>>>>
>>>> /etc/lightdm/slick-greeter.conf
>>>> [Greeter]
>>>> background=/usr/share/backgrounds/sabayonlinux.png
>>>> theme-name=Adwaita
>>>> icon-them-name=(unified icon theme?)
>>>>
>>>> Preferably need Graphic Designer with better skills than myself for new
>>>> Wallpaper and Calamares design. I like my wallpaper, but it looks bad on
>>>> 4:3 monitors which never occurred to me. Probably should have made
>>>> something that could fit all ranges from Mobile to desktop ratios. Also
>>>> probably color schemes that are similar across all spins. Not really a
>>>> requirement right now, just a wishlist item :)
>>>>
>>>> I'm sure I'll get some feedback over this, but have we ever thought of
>>>> catering to the simplifying server/service administration for the ease
>>>> of
>>>> use for our userbase?
>>>> http://dalalven.dtdns.net/linux/gadmintools-webpage/
>>>> I know its not the most puritan, or the best way to control services,
>>>> but I can see people liking this and this giving us some wins.
>>>>
>>>> MATE Screensaver seems barren. Screensavers are terrible. Import
>>>> xscreensavers? requires xscreensaver installed and custom .desktop files
>>>> pointing to xscreensaver files, but possible. e.g.
>>>> /usr/share/applications/screensavers/hextstrut.desktop
>>>>
>>>> [Desktop Entry]
>>>> Name=hexstrut
>>>> Exec=/usr/lib64/misc/xscreensaver/hexstrut -root
>>>> TryExec=/usr/lib64/misc/xscreensa

Re: [sabayon-dev] ISO Testing Results

[Joost Ruis]

Firewall off?

On Mon, Jun 18, 2018 at 6:11 AM, Jerrod Frost 
wrote:

> Just an update. I've been fiddling with SAMBA and Windows 10 lately and
> finding I cannot connect to my Win10 Shares. Evidently this is due to SMB
> v3.11 in Windows 10 which isn't fully supported? So I decided to do some
> digging. We're currently using an EOL version of SAMBA! 4.5 is Discontinued
> and EOL as of 2018-03-13.  Current Stable is 4.8. Is it possible to get a
> package bump to stable?
>
> On Fri, Jun 15, 2018 at 1:33 PM André Jaenisch 
> wrote:
>
>> Hi, Jerrod,
>>
>> thank you for your efforts.
>>
>> Patreon / Liberapay will make it on the website as soon as I get positive
>> feedback / green light for pushing https://next.sabayon.org/ to
>> production.
>>
>> Right now I'm gathering feedback.
>>
>> Kind regards
>>
>>
>> Ryuno-Ki
>>
>>
>>
>>  Ursprüngliche Nachricht 
>> Von: Jerrod Frost 
>> Gesendet: 15. Juni 2018 05:39:37 MESZ
>> An: sabayon-dev 
>> Betreff: [sabayon-dev] ISO Testing Results
>>
>> ###COMMON ISSUES###
>>
>> Calamares - Encryption is broken. Could we go with FDE and decrypt via
>> GRUB2? It seems to be using GRUB to decrypt, but upon booting asks for
>> password to mount /dev/mapper/luks-X which doesn't exist?
>>
>> Still using GRUB 2.02 BETA3. Is there a reason we have not moved to 2.02
>> stable?
>>
>> Donate to Sabayon -> Page missing Patreon/librepay ?
>>
>> minetest - only the engine is installed, not the game. need to install
>> package minetest_game
>>
>> First set of updates pull in KDE packages for non-KDE spins? This one I
>> don't quite understand.
>>
>> ###WISH LIST ITEMS###
>>
>> 4.17 kernel not in Repository; I'd like to personally make an unsupported
>> spin like the forensics edition, but for ryzen APU users as 4.17 is a
>> requirement.
>>
>> Unified Icons? Can we come up with a set of icons that are the same for
>> every spin?
>>
>> Unified LightDM with Slick Greeter? Keeping the same DM across the spins.
>>
>> /etc/lightdm/slick-greeter.conf
>> [Greeter]
>> background=/usr/share/backgrounds/sabayonlinux.png
>> theme-name=Adwaita
>> icon-them-name=(unified icon theme?)
>>
>> Preferably need Graphic Designer with better skills than myself for new
>> Wallpaper and Calamares design. I like my wallpaper, but it looks bad on
>> 4:3 monitors which never occurred to me. Probably should have made
>> something that could fit all ranges from Mobile to desktop ratios. Also
>> probably color schemes that are similar across all spins. Not really a
>> requirement right now, just a wishlist item :)
>>
>> I'm sure I'll get some feedback over this, but have we ever thought of
>> catering to the simplifying server/service administration for the ease of
>> use for our userbase?
>> http://dalalven.dtdns.net/linux/gadmintools-webpage/
>> I know its not the most puritan, or the best way to control services,
>> but I can see people liking this and this giving us some wins.
>>
>> MATE Screensaver seems barren. Screensavers are terrible. Import
>> xscreensavers? requires xscreensaver installed and custom .desktop files
>> pointing to xscreensaver files, but possible. e.g.
>> /usr/share/applications/screensavers/hextstrut.desktop
>>
>> [Desktop Entry]
>> Name=hexstrut
>> Exec=/usr/lib64/misc/xscreensaver/hexstrut -root
>> TryExec=/usr/lib64/misc/xscreensaver/hexstrut
>> StartupNotify=false
>> Terminal=false
>> Type=Application
>> Categories=Screensaver;
>> OnlyShowIn=MATE;
>>
>> Then they show up natively in the MATE screensaver control panel.
>>
>> ###XFCE ISSUES###
>>
>> Chrome still set as default browser, but Chrome isn't installed? Firefox
>> appears to be new default. .desktop file needs tweaked to point to firefox
>> instead.
>>
>> ###MATE ISSUES###
>>
>> VLC AND MPV? Are we OK with having both or does that seem bloated?
>>
>>
>> ###GNOME ISSUES###
>>
>> VLC, Totem, and MPV?  Too many or OK? Bloated or fine?
>>
>> GDM depends on brltty and should NOT. (if we don't ditch GDM)
>> brltty is known to hijack USB to Serial adapters. Anyone performing work
>> on
>> networking gear requiring the ability to console in will find they cannot
>> because brltty hijacks the device. uninstalling brltty also removes GDM
>> which leaves you without a display manager. Just need to break off the
>> dependency.
>>
>> Gnome is going to have some trouble with screen locking and screensavers
>> after switching from GDM to LightDM.  Gnome apparently uses GDM also for
>> screen locking. xscreensaver still works, just need to add xscreensaver to
>> autostart by default /etc/xdg/autostart/xscreensaver.desktop
>>
>> [Desktop Entry]
>> Type=Application
>> Name=Screensaver
>> Comment=Launch screensaver and locker program
>> Icon=preferences-desktop-screensaver
>> Exec=xscreensaver
>> TryExec=xscreensaver
>>
>> also edit ~/.config/dconf/user database in /etc/skel to make super+L
>> trigger xscreenlocker-command -lock to lock the screen.
>>
>> edit skel file for ~/.xscreensaver
>> captureStderr:  True should be "False"

Re: [sabayon-dev] ISO Testing Results

[Joost Ruis]

games-action/minetest -> games-action/minetest_game

https://github.com/Sabayon/molecules/commit/1050bc7d2bb22b0bc3c2d3b653ab84f56e346b43

On Fri, Jun 15, 2018 at 5:39 AM, Jerrod Frost 
wrote:

> ###COMMON ISSUES###
>
> Calamares - Encryption is broken. Could we go with FDE and decrypt via
> GRUB2? It seems to be using GRUB to decrypt, but upon booting asks for
> password to mount /dev/mapper/luks-X which doesn't exist?
>
> Still using GRUB 2.02 BETA3. Is there a reason we have not moved to 2.02
> stable?
>
> Donate to Sabayon -> Page missing Patreon/librepay ?
>
> minetest - only the engine is installed, not the game. need to install
> package minetest_game
>
> First set of updates pull in KDE packages for non-KDE spins? This one I
> don't quite understand.
>
> ###WISH LIST ITEMS###
>
> 4.17 kernel not in Repository; I'd like to personally make an unsupported
> spin like the forensics edition, but for ryzen APU users as 4.17 is a
> requirement.
>
> Unified Icons? Can we come up with a set of icons that are the same for
> every spin?
>
> Unified LightDM with Slick Greeter? Keeping the same DM across the spins.
>
> /etc/lightdm/slick-greeter.conf
> [Greeter]
> background=/usr/share/backgrounds/sabayonlinux.png
> theme-name=Adwaita
> icon-them-name=(unified icon theme?)
>
> Preferably need Graphic Designer with better skills than myself for new
> Wallpaper and Calamares design. I like my wallpaper, but it looks bad on
> 4:3 monitors which never occurred to me. Probably should have made
> something that could fit all ranges from Mobile to desktop ratios. Also
> probably color schemes that are similar across all spins. Not really a
> requirement right now, just a wishlist item :)
>
> I'm sure I'll get some feedback over this, but have we ever thought of
> catering to the simplifying server/service administration for the ease of
> use for our userbase?
> http://dalalven.dtdns.net/linux/gadmintools-webpage/
> I know its not the most puritan, or the best way to control services,
> but I can see people liking this and this giving us some wins.
>
> MATE Screensaver seems barren. Screensavers are terrible. Import
> xscreensavers? requires xscreensaver installed and custom .desktop files
> pointing to xscreensaver files, but possible. e.g. /usr/share/applications/
> screensavers/hextstrut.desktop
>
> [Desktop Entry]
> Name=hexstrut
> Exec=/usr/lib64/misc/xscreensaver/hexstrut -root
> TryExec=/usr/lib64/misc/xscreensaver/hexstrut
> StartupNotify=false
> Terminal=false
> Type=Application
> Categories=Screensaver;
> OnlyShowIn=MATE;
>
> Then they show up natively in the MATE screensaver control panel.
>
> ###XFCE ISSUES###
>
> Chrome still set as default browser, but Chrome isn't installed? Firefox
> appears to be new default. .desktop file needs tweaked to point to firefox
> instead.
>
> ###MATE ISSUES###
>
> VLC AND MPV? Are we OK with having both or does that seem bloated?
>
>
> ###GNOME ISSUES###
>
> VLC, Totem, and MPV?  Too many or OK? Bloated or fine?
>
> GDM depends on brltty and should NOT. (if we don't ditch GDM)
> brltty is known to hijack USB to Serial adapters. Anyone performing work
> on networking gear requiring the ability to console in will find they
> cannot because brltty hijacks the device. uninstalling brltty also removes
> GDM which leaves you without a display manager. Just need to break off the
> dependency.
>
> Gnome is going to have some trouble with screen locking and screensavers
> after switching from GDM to LightDM.  Gnome apparently uses GDM also for
> screen locking. xscreensaver still works, just need to add xscreensaver to
> autostart by default /etc/xdg/autostart/xscreensaver.desktop
>
> [Desktop Entry]
> Type=Application
> Name=Screensaver
> Comment=Launch screensaver and locker program
> Icon=preferences-desktop-screensaver
> Exec=xscreensaver
> TryExec=xscreensaver
>
> also edit ~/.config/dconf/user database in /etc/skel to make super+L
> trigger xscreenlocker-command -lock to lock the screen.
>
> edit skel file for ~/.xscreensaver
> captureStderr:  True should be "False" to avoid random complaints of
> missing fonts.
>
>
> ###KDE ISSUES###
>
> Works well! No real issues found other than the common ones that are the
> same in other spins. Screen locker will still work without SDDM so if we
> switch to lightdm w/slick-greeter we don't need a screen locker
> replacement. Kudos!
>
>
>
>

Re: [sabayon-dev] Missing kernel config for PowerTOP utility

[Joost Ruis]

https://salsa.debian.org/kernel-team/linux/blob/master/debian/config/config
As pointed out by samcv on IRC, Debian has this enabled too. I have no
objections here.

Who can make this happen?

On Thu, Apr 19, 2018 at 10:18 PM, Samantha McVey 
wrote:

> Joost said this was a good place to put this:
>
> Seems linux-sabayon doesn't have the following flags which are needed:
>
> CONFIG_TRACEPOINTS
> CONFIG_BLK_DEV_IO_TRACE
> CONFIG_TIMER_STATS
> CONFIG_TRACING
>
> These are mentioned on Gentoo's PowerTOP page[1] and also show up with
> ewarn's
> if you try and emerge PowerTOP without having these flags set. Without
> these
> set PowerTOP won't show the wakup/s and won't show how many events are
> being
> generated by specific processes.
>
> 1: https://wiki.gentoo.org/wiki/PowerTOP#Troubleshooting
>
>
>
>

Re: [sabayon-dev] Default cpupower governor is set to powersafe

[Joost Ruis]

Now looking at my work pc, that is a pretty fresh MATE install, here the
setting is "frequency-set --governor powersave" but it doesn't behave like
it.
So how this works might differ for your hardware.

I'll try to investigate further.

On Wed, Apr 18, 2018 at 12:05 AM, Jerrod Frost  wrote:

> YES! ondemand is the way to go!
>
> On Tue, Apr 17, 2018 at 4:50 PM Joost Ruis  wrote:
>
>> Hi.
>>
>> Today I was looking into why my games underperform so badly in Sabayon
>> Linux compared to Windows 10.
>> Since I bumped kernel to 4.16.2 I was expecting to see at least some
>> improvements.
>>
>> After checking everything was set and installed fine. (amdgpu module
>> loaded, firmware loaded, etc etc) I went and look into the CPU scaling. I
>> discovered that my Intel(R) Core(TM) i5 CPU  @3.20GHz was never touching
>> it's max speed, not even close. So I looked at the cpupower settings and
>> learned it was set to powersave.
>>
>> After changing this on-the-fly, using: cpupower frequency-set -g ondemand
>> games ran WAY better, obviously. So I wondered where this setting came
>> from. Apparently it is set in  /etc/sysconfig/cpupower provided by
>> sys-power/cpupower.
>>
>> I propose we set this to ondemand. (Not sure if we want to fork the
>> ebuild for this)
>>
>> Thoughts?
>>
>>
>>
>
>
>

[sabayon-dev] Default cpupower governor is set to powersafe

[Joost Ruis]

Hi.

Today I was looking into why my games underperform so badly in Sabayon
Linux compared to Windows 10.
Since I bumped kernel to 4.16.2 I was expecting to see at least some
improvements.

After checking everything was set and installed fine. (amdgpu module
loaded, firmware loaded, etc etc) I went and look into the CPU scaling. I
discovered that my Intel(R) Core(TM) i5 CPU  @3.20GHz was never touching
it's max speed, not even close. So I looked at the cpupower settings and
learned it was set to powersave.

After changing this on-the-fly, using: cpupower frequency-set -g ondemand
games ran WAY better, obviously. So I wondered where this setting came
from. Apparently it is set in  /etc/sysconfig/cpupower provided by
sys-power/cpupower.

I propose we set this to ondemand. (Not sure if we want to fork the ebuild
for this)

Thoughts?

Re: [sabayon-dev] ISO Testing Results

[Joost Ruis]

The part in release notes about ARM is not true by the way. I
recompiled/updated almost the entire ARM repo, it is almost good to go.

On Sun, Apr 8, 2018 at 2:27 PM, Sławomir Nizio 
wrote:

> Thanks!
>
> Let's hammer out the release notes document - here's with my changes
> (can be changed/removed further, it's a proposal):
>
> https://github.com/Sabayon/sabayon-website-next/pull/75
>
>

Re: [sabayon-dev] Release Goals?

[Joost Ruis]

Release ASAP.

Do another release later this year.

On Tue, Apr 3, 2018 at 6:56 PM, Sławomir Nizio 
wrote:

> > I'm looking for a discussion on how we feel about releasing. A few
> > options have been presented. We can:
> >
> > 1. Delay Release, make a few package bumps, and polish release with a
> > Goal of 18.05 (mostly remaining frozen)
> > 2. Clean up and Release ASAP with 18.04 (Unfreeze and allow updates to
> flow)
>
> Comment from my side and my point of view is that I avoid doing anything
> with packages and bugs due to the "frozen" status.
>
>

Re: [sabayon-dev] Freeze pending

[Joost Ruis]

We had a problem with our dbus socket:

ExecStartPost pointed to /bin/systemctl  causing that command to fail.
After a remerge it now looks OK:

andromeda ~ # cat /usr/lib/systemd/user/dbus.socket
[Unit]
Description=D-Bus User Message Bus Socket

[Socket]
ListenStream=%t/bus
ExecStartPost=-/usr/bin/systemctl --user set-environment
DBUS_SESSION_BUS_ADDRESS=unix:path=%t/bus

[Install]
WantedBy=sockets.target
Also=dbus.service



On Tue, Mar 20, 2018 at 9:23 AM, Joost Ruis  wrote:

> Just for reference,
>
> ==
> this is the service file we produce now:
> ==
>
> [Unit]
> Description=Simple Desktop Display Manager
> Documentation=man:sddm(1) man:sddm.conf(5)
> Conflicts=getty@tty1.service
> After=systemd-user-sessions.service  systemd-logind.service
>
> [Service]
> ExecStart=/usr/bin/sddm
> Restart=always
> StandardOutput=syslog
> BusName=org.freedesktop.DisplayManager
>
> [Install]
> Alias=display-manager.service
>
> 
> This is the service file as shipped on Archlinux:
> 
>
> [Unit]
> Description=Simple Desktop Display Manager
> Documentation=man:sddm(1) man:sddm.conf(5)
> Conflicts=getty@tty1.service
> After=systemd-user-sessions.service getty@tty1.service
> plymouth-quit.service
>
> [Service]
> ExecStart=/usr/bin/sddm
> Restart=always
>
> [Install]
> Alias=display-manager.service
>
> 
>
> So what is the real difference and let's assume the archlinux file is
> correct.
>
> On Arch they also instruct to start after  getty@tty1.service (I would
> assume setting it in Conflicts would be enough)
> On Arch they don't define BusName=org.freedesktop.DisplayManager.
> On Arch doesn't define StandardOutput. (souldn't affect our issue)
>
>
> On Tue, Mar 20, 2018 at 1:34 AM, Jerrod Frost 
> wrote:
>
>> 3.19.18 KDE-dev.iso
>>
>> SDDM is still broken, now in a different way. SDDM doesn't even load on
>> the live disc on its own anymore.
>>
>> dubs.socket: Failed at step EXEC Spawning /bin/systemctl: no such file or
>> directory
>>
>> what did we change to get this ^
>>
>> after starting sddm manually, everything appears fine, but thats because
>> the race condition didn't occur.
>> and konqueror also appears to be having some strange delimma. open it up,
>> do a google search, press alt+F4 to close. try to open it back up... NOPE.
>> konqueror[3534]: QCommandLineParser: argument list cannot be empty, it
>> should contain at least the executable name
>>
>> to test again, I performed a
>> killall konqueror
>> konqueror
>> ALT+F4
>> (terminal still in use. Konqueror is still running!)
>> Open another terminal
>> konqueror
>> _IceTransSocketUNIXConnect: Cannot connect to non-local host sabayon
>> _IceTransSocketUNIXConnect: Cannot connect to non-local host sabayon
>> Qt: Session management error: Could not open network socket
>>
>> OK, what happens if I just close using the window's close button?
>> Same thing.
>> What about Ctrl+Q (quit)
>> Same issue!
>> What if its not on the live disc?
>> Same issue.
>>
>> My advice? ditch konqueror. its a terrible web browser. we have chrome,
>> then we also have firefox available for install. Nothing I can think of
>> depends on konqueror.
>>
>> On Sun, Mar 11, 2018 at 8:18 PM Jerrod Frost 
>> wrote:
>>
>>> Its testing in general. I don't just test raw images. If I see something
>>> or hear complaints, I test, and file a bug where necessary.
>>> the idea is we're testing all the time, not just ISOs during/after
>>> freeze.
>>>
>>> On Sun, Mar 11, 2018 at 5:56 PM Joost Ruis 
>>> wrote:
>>>
>>>> obs-studio isn't part of the images. What does this have to do with
>>>> image testing?
>>>>
>>>> On Sun, Mar 11, 2018 at 8:11 PM, Jerrod Frost <
>>>> darks...@sabayonlinux.org> wrote:
>>>>
>>>>> As far as testing is concerned, we're testing all the time. We aren't
>>>>> just testing right before or after a freeze :) . I get complaints in 
>>>>> single
>>>>> packages every once in a while and we submit bugzilla bugs to have 
>>>>> packages
>>>>> recompiled or upgraded. I've even gone upstream before if the ebuild 
>>>>> needed
>>>>> updated in portage. obs-studio is a perfect example of this. I req

Re: [sabayon-dev] Freeze pending

[Joost Ruis]

Just for reference,

==
this is the service file we produce now:
==

[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
Conflicts=getty@tty1.service
After=systemd-user-sessions.service  systemd-logind.service

[Service]
ExecStart=/usr/bin/sddm
Restart=always
StandardOutput=syslog
BusName=org.freedesktop.DisplayManager

[Install]
Alias=display-manager.service


This is the service file as shipped on Archlinux:


[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
Conflicts=getty@tty1.service
After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service

[Service]
ExecStart=/usr/bin/sddm
Restart=always

[Install]
Alias=display-manager.service



So what is the real difference and let's assume the archlinux file is
correct.

On Arch they also instruct to start after  getty@tty1.service (I would
assume setting it in Conflicts would be enough)
On Arch they don't define BusName=org.freedesktop.DisplayManager.
On Arch doesn't define StandardOutput. (souldn't affect our issue)


On Tue, Mar 20, 2018 at 1:34 AM, Jerrod Frost 
wrote:

> 3.19.18 KDE-dev.iso
>
> SDDM is still broken, now in a different way. SDDM doesn't even load on
> the live disc on its own anymore.
>
> dubs.socket: Failed at step EXEC Spawning /bin/systemctl: no such file or
> directory
>
> what did we change to get this ^
>
> after starting sddm manually, everything appears fine, but thats because
> the race condition didn't occur.
> and konqueror also appears to be having some strange delimma. open it up,
> do a google search, press alt+F4 to close. try to open it back up... NOPE.
> konqueror[3534]: QCommandLineParser: argument list cannot be empty, it
> should contain at least the executable name
>
> to test again, I performed a
> killall konqueror
> konqueror
> ALT+F4
> (terminal still in use. Konqueror is still running!)
> Open another terminal
> konqueror
> _IceTransSocketUNIXConnect: Cannot connect to non-local host sabayon
> _IceTransSocketUNIXConnect: Cannot connect to non-local host sabayon
> Qt: Session management error: Could not open network socket
>
> OK, what happens if I just close using the window's close button?
> Same thing.
> What about Ctrl+Q (quit)
> Same issue!
> What if its not on the live disc?
> Same issue.
>
> My advice? ditch konqueror. its a terrible web browser. we have chrome,
> then we also have firefox available for install. Nothing I can think of
> depends on konqueror.
>
> On Sun, Mar 11, 2018 at 8:18 PM Jerrod Frost 
> wrote:
>
>> Its testing in general. I don't just test raw images. If I see something
>> or hear complaints, I test, and file a bug where necessary.
>> the idea is we're testing all the time, not just ISOs during/after freeze.
>>
>> On Sun, Mar 11, 2018 at 5:56 PM Joost Ruis 
>> wrote:
>>
>>> obs-studio isn't part of the images. What does this have to do with
>>> image testing?
>>>
>>> On Sun, Mar 11, 2018 at 8:11 PM, Jerrod Frost >> > wrote:
>>>
>>>> As far as testing is concerned, we're testing all the time. We aren't
>>>> just testing right before or after a freeze :) . I get complaints in single
>>>> packages every once in a while and we submit bugzilla bugs to have packages
>>>> recompiled or upgraded. I've even gone upstream before if the ebuild needed
>>>> updated in portage. obs-studio is a perfect example of this. I requested
>>>> the 21.0.2 revision which fixed some audio glitches and tested just bumping
>>>> the build name/version of the ebuild which worked fine. when confirmed they
>>>> quickly updated the ebuild in portage and we now have 21.0.2 in entropy as
>>>> well :)
>>>>
>>>> Right now, we're fairly stable. I wanted to perform a final test after
>>>> freeze to confirm there were no strange quirks that were missed that would
>>>> impact the OOTB experience for our users. we have 1 week (till end of day
>>>> saturday) to finish testing and stamp approval for release.
>>>>
>>>> On Fri, Mar 9, 2018 at 5:36 PM Sławomir Nizio <
>>>> slawomir.ni...@sabayon.org> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> We've been talking on IRC and figured some pieces of information
>>>>> related
>>>>> to actions might be missing here.
>>>>>
>>>>> So,
>>>>>
>>>>> Has testing started?
>>>>> How is it going?
>>>>> Is it blocked by anything? Are you waiting for someone or something?
>>>>> Is there help needed with something?
>>>>>
>>>>> Let's have it straight where's the ball now. :)
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>
>
>

Re: [sabayon-dev] RFC: using GitHub to track ISO releases preparation

[Joost Ruis]

 Kanban board works for me.

On Sun, Mar 11, 2018 at 8:03 PM, Jerrod Frost 
wrote:

> I really like the 1st and 4th views.
>
> On Fri, Mar 9, 2018 at 6:51 PM Sławomir Nizio 
> wrote:
>
>> with a 4th view:
>>
>> - "bare" view with issues (with labels): https://github.com/Enlik/meh/
>> issues
>> - the "new release" milestone: https://github.com/Enlik/meh/milestone/1
>> - as Kanban board (used more or less correctly, but pretty nice):
>> https://github.com/Enlik/meh/projects/1
>> - a simple "Wiki" page(s): https://github.com/Enlik/meh/wiki/x.y-release
>>
>>
>
>
>

Re: [sabayon-dev] Freeze pending

[Joost Ruis]

 obs-studio isn't part of the images. What does this have to do with image
testing?

On Sun, Mar 11, 2018 at 8:11 PM, Jerrod Frost 
wrote:

> As far as testing is concerned, we're testing all the time. We aren't just
> testing right before or after a freeze :) . I get complaints in single
> packages every once in a while and we submit bugzilla bugs to have packages
> recompiled or upgraded. I've even gone upstream before if the ebuild needed
> updated in portage. obs-studio is a perfect example of this. I requested
> the 21.0.2 revision which fixed some audio glitches and tested just bumping
> the build name/version of the ebuild which worked fine. when confirmed they
> quickly updated the ebuild in portage and we now have 21.0.2 in entropy as
> well :)
>
> Right now, we're fairly stable. I wanted to perform a final test after
> freeze to confirm there were no strange quirks that were missed that would
> impact the OOTB experience for our users. we have 1 week (till end of day
> saturday) to finish testing and stamp approval for release.
>
> On Fri, Mar 9, 2018 at 5:36 PM Sławomir Nizio 
> wrote:
>
>> Hello,
>>
>> We've been talking on IRC and figured some pieces of information related
>> to actions might be missing here.
>>
>> So,
>>
>> Has testing started?
>> How is it going?
>> Is it blocked by anything? Are you waiting for someone or something?
>> Is there help needed with something?
>>
>> Let's have it straight where's the ball now. :)
>>
>>
>
>
>

Re: [sabayon-dev] Freeze pending

[Joost Ruis]

You checked for versions without our overlay attached or what?

On Tue, Mar 6, 2018 at 5:03 AM, Jerrod Frost 
wrote:

> We need to bump:
> sys-libs/efivar (currently using .21 which isn't in portage)
> sys-fs/btrfs-progs (currently using 4.12 which isn't in portage)
> sys-boot/grub (currently using 2.02_beta3-r1 which isn't in portage)
> sys-boot/efibootmgr (currently using .12 which isn't in portage)
> sys-boot/plymouth (not sure what to do here? isn't this eventually going
> away? Also using 0.8.9 which isn't in portage)
> sys-apps/systemd (using 233-r3 which isn't in portage. r6 is the minimum.)
> sys-apps/baselayout (using 2.2-r1, not in portage)
>
> x11-drivers/xf86-video-amdgpu-18.0.0 (needs updated, updated ebuild
> already in portage)
>
> https://lists.freedesktop.org/archives/amd-gfx/2018-March/019622.html
>
> Some of the packages above aren't what I'd call crucial. Much of this can
> be updated after install. ISOs are stable enough for freeze.
>
> I'd like to see grub, AMDGPU, and btrfs-progs updated before freeze.
>
> As for the rest, do we have a plan? I can see the rest being updated later
> on.
>
> -Darksurf
>
>
>
>

Re: [sabayon-dev] Fwd: XFCE display issues

[Joost Ruis]

Next daily dev image will have this change.

On Sat, Dec 30, 2017 at 5:34 PM, Jerrod Frost  wrote:

> https://github.com/Sabayon/skel/pull/7
>
> On Sat, Dec 30, 2017 at 10:23 AM Joost Ruis 
> wrote:
>
>> Make a PR on skel.git
>>
>> Op 30 dec. 2017 17:20 schreef "Jerrod Frost" :
>>
>> This is nice find. I don't have anything with an intel GPU. Joost can we
>>> add this tweak by default? vsync is hardly anything risky to have by
>>> default, so I see no reason not to.
>>>
>>> On Sat, Dec 30, 2017 at 6:16 AM sabayonino  wrote:
>>>
>>>>
>>>>
>>>>
>>>>  Messaggio Inoltrato 
>>>> Oggetto: Re: XFCE display issues
>>>> Data: Fri, 29 Dec 2017 22:58:01 +0100
>>>> Mittente: sabayonino 
>>>> A: devel-requ...@lists.sabayon.org
>>>>
>>>>
>>>>
>>>> Il 29/12/2017 13:11, devel-requ...@lists.sabayon.org
>>>>
>>>> >this option can be edited here:
>>>> >
>>>> > ~/.config/xfce4/xfconf/xfce-perchannel-xml
>>>>
>>>> Errata corridge:
>>>>
>>>>  ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml
>>>>
>>>> but I can see that the last 7 lines were added after X11 started and
>>>> differ from xfwm4.xml skel
>>>>
>>>> see
>>>> https://github.com/Sabayon/skel/blob/master/skel/.config/
>>>> xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml
>>>>
>>>> PS : My Integrated Video Card is
>>>> # lshw -class video
>>>>   *-display
>>>>description: VGA compatible controller
>>>>product: 3rd Gen Core processor Graphics Controller
>>>>vendor: Intel Corporation
>>>>physical id: 2
>>>>bus info: pci@:00:02.0
>>>>version: 09
>>>>width: 64 bits
>>>>clock: 33MHz
>>>>capabilities: msi pm vga_controller bus_master cap_list rom
>>>>configuration: driver=i915 latency=0
>>>>resources: irq:27 memory:f640-f67f
>>>> memory:e000-efff ioport:f000(size=64) memory:c-d
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>
>
>

Re: [sabayon-dev] Fwd: XFCE display issues

[Joost Ruis]

Make a PR on skel.git

Op 30 dec. 2017 17:20 schreef "Jerrod Frost" :

> This is nice find. I don't have anything with an intel GPU. Joost can we
> add this tweak by default? vsync is hardly anything risky to have by
> default, so I see no reason not to.
>
> On Sat, Dec 30, 2017 at 6:16 AM sabayonino  wrote:
>
>>
>>
>>
>>  Messaggio Inoltrato 
>> Oggetto: Re: XFCE display issues
>> Data: Fri, 29 Dec 2017 22:58:01 +0100
>> Mittente: sabayonino 
>> A: devel-requ...@lists.sabayon.org
>>
>>
>>
>> Il 29/12/2017 13:11, devel-requ...@lists.sabayon.org
>>
>> >this option can be edited here:
>> >
>> > ~/.config/xfce4/xfconf/xfce-perchannel-xml
>>
>> Errata corridge:
>>
>>  ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml
>>
>> but I can see that the last 7 lines were added after X11 started and
>> differ from xfwm4.xml skel
>>
>> see
>> https://github.com/Sabayon/skel/blob/master/skel/.config/
>> xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml
>>
>> PS : My Integrated Video Card is
>> # lshw -class video
>>   *-display
>>description: VGA compatible controller
>>product: 3rd Gen Core processor Graphics Controller
>>vendor: Intel Corporation
>>physical id: 2
>>bus info: pci@:00:02.0
>>version: 09
>>width: 64 bits
>>clock: 33MHz
>>capabilities: msi pm vga_controller bus_master cap_list rom
>>configuration: driver=i915 latency=0
>>resources: irq:27 memory:f640-f67f
>> memory:e000-efff ioport:f000(size=64) memory:c-d
>>
>>
>>
>>
>>
>>
>
>
>

Re: [sabayon-dev] XFCE display issues

[Joost Ruis]

I noticed 3 bigger icons in the settings menu:
https://image.ibb.co/nGTuMb/Screenshot_2017_12_28_21_14_46.png
But everything else seems to be fine on my end. (tested on baremetal)

https://image.ibb.co/i19OEw/Screenshot_2017_12_28_20_59_04.png

I do notice that XFCE lacks an audio volume applet thingy.

On Thu, Dec 28, 2017 at 2:57 PM, Jerrod Frost  wrote:

> Interesting, which graphics card are you using?
>
> On Wed, Dec 27, 2017, 8:56 PM Svantoviit  wrote:
>
>> Hi,
>>
>> I checked out the latest XFCE daily ISO from 27.12.2017 and experience
>> a couple of issues which makes it almost unusable out of the box (both
>> on a live and an installed system):
>>
>> 1. the panel is flickering and disappearing
>> 2. the application menu is flickering, disappearing or getting grey
>> 3. same applies to any open window
>> 4. icons in the applications menu are not of same size, some of them
>> are much bigger, some icons are not aligned
>>
>> It's possible to stop the flickering by disabling compositing, but other
>> things become ugly then. I have to say that the desktop experience is poor
>> compared to what it used to be.
>>
>> Would it be possible to give the XFCE spin some love again?
>>
>> --
>> SvantoViit
>>
>>
>
>
>

Re: [sabayon-dev] nvidia-drivers missing, other small package updates

[Joost Ruis]

Not if hey are in the same slot as latest drivers. Only option we have is
to downgrade. Personally I'd like to avoid that.

On Tue, Nov 28, 2017 at 5:25 PM, Jerrod Frost  wrote:

> For stability can we get nvidia-drivers-384.98 back in the repo. I'm
> seeing instability (locking and getting kicked out of KDE, games crashing,
> black or non-updating screen)
>
> On Tue, Nov 21, 2017 at 2:19 PM Jerrod Frost  wrote:
>
>> Samba bump, if any, could happen after release. No functional changes
>> really unless we go 4.7, but even those changes are not something a normal
>> user without a domain and controller would run into it seems. 4.7 does try
>> to enforce SMB3 usage and discourages SMB1/CIFS for security reasons.
>>
>> On Tue, Nov 21, 2017, 1:23 PM Joost Ruis  wrote:
>>
>>> I recently bumped nvidia-drivers for Entropy against all kernels and
>>> wasn't aware that 387.XX is actually a beta version. Just followed what was
>>> done on our overlay:
>>>
>>> https://github.com/Sabayon/sabayon-distro/commit/
>>> f79f1cf16b1c4d1be390823271710ed73bdae83c
>>>
>>> @Francesco any thoughts?
>>>
>>> I must say that I didn't have any problems with them on my gaming
>>> laptop.
>>> We hopefully have a newer zfs version available in Entropy, one that
>>> also supports the 4.14 kernel that is currently in Limbo.
>>>
>>> @Ettore should have a say about efivar 0.21 -> 31 && efibootmgr 0.12 ->
>>> 15. I don't touch them. Same goes for sys-boot/grub.
>>>
>>> No opinion about Samba here. If we wanna bump this prior to "the
>>> release" let me know and I will take care off it.
>>>
>>>
>>> On Tue, Nov 21, 2017 at 8:06 PM, Sławomir Nizio <
>>> slawomir.ni...@sabayon.org> wrote:
>>>
>>>> I can comment on this one for sure:
>>>>
>>>> > Samba (not really sure what to do here. CVE-2017-15275,14746,11103,
>>>> list
>>>> > goes on an on) we need to be on 4.5.14, but that doesn't cure all the
>>>> > CVE on samba's page but switching to 4.7.2 is just switching to a list
>>>> > of unknown vulnerabilities. Is it really beneficial to go from 4.5 to
>>>> > 4.7? at the very least we should be 4.5.14, but beyond that I'm not
>>>> sure
>>>> > how we should proceed or the effort it would take to constantly hop as
>>>> > samba updates at a pretty fast pace.. Looking for some insight on this
>>>> > topic.
>>>>
>>>> I'm keeping it in the overlay to fix automatic dependency on Ceph. It
>>>> was fixed in Gentoo in a new version that is not yet stable.
>>>>
>>>> I don't see benefit to switch to unstable (in Gentoo terms) one, unless
>>>> there is a reason to do otherwise, risking the usage of a less tested
>>>> (in theory) version. Also note that in case of a security issue, Gentoo
>>>> would either backport a fix to the older series, or new upstream version
>>>> (in the same "series" or newer) should be stabilized soon enough.
>>>>
>>>> (If there is a version that has a fix on some CVE and is not listed in
>>>> Gentoo bug tracker, it's a good idea to file a bug there.)
>>>>
>>>>
>>>
>>>
>
>
>

Re: [sabayon-dev] nvidia-drivers missing, other small package updates

[Joost Ruis]

I recently bumped nvidia-drivers for Entropy against all kernels and wasn't
aware that 387.XX is actually a beta version. Just followed what was done
on our overlay:

https://github.com/Sabayon/sabayon-distro/commit/f79f1cf16b1c4d1be390823271710ed73bdae83c

@Francesco any thoughts?

I must say that I didn't have any problems with them on my gaming laptop.
We hopefully have a newer zfs version available in Entropy, one that also
supports the 4.14 kernel that is currently in Limbo.

@Ettore should have a say about efivar 0.21 -> 31 && efibootmgr 0.12 -> 15.
I don't touch them. Same goes for sys-boot/grub.

No opinion about Samba here. If we wanna bump this prior to "the release"
let me know and I will take care off it.


On Tue, Nov 21, 2017 at 8:06 PM, Sławomir Nizio 
wrote:

> I can comment on this one for sure:
>
> > Samba (not really sure what to do here. CVE-2017-15275,14746,11103, list
> > goes on an on) we need to be on 4.5.14, but that doesn't cure all the
> > CVE on samba's page but switching to 4.7.2 is just switching to a list
> > of unknown vulnerabilities. Is it really beneficial to go from 4.5 to
> > 4.7? at the very least we should be 4.5.14, but beyond that I'm not sure
> > how we should proceed or the effort it would take to constantly hop as
> > samba updates at a pretty fast pace.. Looking for some insight on this
> > topic.
>
> I'm keeping it in the overlay to fix automatic dependency on Ceph. It
> was fixed in Gentoo in a new version that is not yet stable.
>
> I don't see benefit to switch to unstable (in Gentoo terms) one, unless
> there is a reason to do otherwise, risking the usage of a less tested
> (in theory) version. Also note that in case of a security issue, Gentoo
> would either backport a fix to the older series, or new upstream version
> (in the same "series" or newer) should be stabilized soon enough.
>
> (If there is a version that has a fix on some CVE and is not listed in
> Gentoo bug tracker, it's a good idea to file a bug there.)
>
>

Re: [sabayon-dev] GRUB needs upgraded. Other suggestions...

[Joost Ruis]

"Kernel.org doesn't have 4.11 or 4.12 those are EOL. That's good reason for
those 2."
Yes then they will be dropped sooner or later. It doesn't mean we have to
drop them as soon they are gone from kernel.org. I tend to keep them around
for a while.

"2.02beta isn't even in portage anymore. They have 2.02 stable. We should
at least use packages that exist in portage."
A valid arguement to move to a newer version.

On Mon, Nov 20, 2017 at 4:26 PM, Jerrod Frost  wrote:

> Kernel.org doesn't have 4.11 or 4.12 those are EOL. That's good reason for
> those 2.
>
> 2.02beta isn't even in portage anymore. They have 2.02 stable. We should
> at least use packages that exist in portage. There are also
> changes/bugfixes(GCC, EFI, VMs, etc) between 2.02beta3 (Feb 2016) and
> 2.02(April 2017) stable considering it was released little over a year
> later.
>
> https://fossies.org/linux/grub/ChangeLog
>
> On Mon, Nov 20, 2017, 6:14 AM Joost Ruis  wrote:
>
>> "We are still using grub2.02-beta3. Can we please upgrade to the stable
>> 2.02?"
>> No, without any motivaton why, we are not going to replace something that
>> isn't broken.
>>
>> "Once 4.14 is the status quo release, how do we feel about dropping
>> 4.11. 4.12 and 4.13 kernels from the repository?"
>>
>> Again, why should we? I only drop kernels that are EOL.
>>
>> I did propose to only ship LTS kernels on our iso images. But that is a
>> different discussion.
>>
>> On Mon, Nov 20, 2017 at 10:35 AM, Daniél Lecoq  wrote:
>>
>>> I don't see any point in dropping kernels from the repository, unless
>>> we're running out of space. There is always some peripheral device that
>>> worked better with the "previous kernel".
>>>
>>> On 2017-11-20 03:09, Jerrod Frost wrote:
>>>
>>> We are still using grub2.02-beta3. Can we please upgrade to the stable
>>> 2.02?
>>>
>>> Once 4.14 is the status quo release, how do we feel about dropping 4.11.
>>> 4.12 and 4.13 kernels from the repository?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>

Re: [sabayon-dev] GRUB needs upgraded. Other suggestions...

[Joost Ruis]

"We are still using grub2.02-beta3. Can we please upgrade to the stable
2.02?"
No, without any motivaton why, we are not going to replace something that
isn't broken.

"Once 4.14 is the status quo release, how do we feel about dropping 4.11.
4.12 and 4.13 kernels from the repository?"

Again, why should we? I only drop kernels that are EOL.

I did propose to only ship LTS kernels on our iso images. But that is a
different discussion.

On Mon, Nov 20, 2017 at 10:35 AM, Daniél Lecoq  wrote:

> I don't see any point in dropping kernels from the repository, unless
> we're running out of space. There is always some peripheral device that
> worked better with the "previous kernel".
>
> On 2017-11-20 03:09, Jerrod Frost wrote:
>
> We are still using grub2.02-beta3. Can we please upgrade to the stable
> 2.02?
>
> Once 4.14 is the status quo release, how do we feel about dropping 4.11.
> 4.12 and 4.13 kernels from the repository?
>
>
>
>
>
>
>

Re: [sabayon-dev] Touchpad tapping stop to work after KDE upgrade

[Joost Ruis]

https://github.com/Sabayon/build/commit/4760d0751139bbb39fe9a6330cd3650e53491edf

Done.

On Sun, Oct 15, 2017 at 2:03 PM, sabayonino  wrote:

> Hi
>
> I've upgraded my two laptops and all touchpads stop to work (tracking
> works , only tapping doesn't work anymore).
>
> I think it depends on disabled "touchpad" useflag on
> kde-plasma/plasma-desktop package
>
> Description:  KDE Plasma desktop
> ╠  USE flag: -appstream -debug -gtk2 -gtk3
> ╠-ibus -scim -test -touchpad abi_x86_64
> ╠amd64 big-endian elibc_glibc
> ╠fontconfig handbook kernel_linux
> ╠legacy-systray mouse pulseaudio
> ╠qt4 semantic-desktop userland_GNU
>
>
> there is this old  bug  about this :
> https://bugs.sabayon.org/show_bug.cgi?id=5241
>
> I think the problem is builtin module in kde-desktop to manage touchpad
> tap not about touchpad recognition
>
> USE="touchpad" emerge plasma-desktop
>
> fix the problem
>
> Consider to enable "touchpad" useflag globally or per package
>
> :) Cheers
>
>

Re: [sabayon-dev] sys-boot/plymouth needs a maintainer

[Joost Ruis]

This is a serious problem in a near future guys.
Our kernels depend on this. We actually ship with a plymouth theme.

On Sat, Aug 5, 2017 at 12:26 PM, Joost Ruis  wrote:

> # Michał Górny  (04 Aug 2017)
> # sys-boot/plymouth is unmaintained since Apr 2016. The current version
> # has multiple bugs, including not supporting OpenRC. It really needs
> # an active maintainer. Removal in 30 days. Bug #621470.
>
>
>
>

[sabayon-dev] sys-boot/plymouth needs a maintainer

[Joost Ruis]

# Michał Górny  (04 Aug 2017)
# sys-boot/plymouth is unmaintained since Apr 2016. The current version
# has multiple bugs, including not supporting OpenRC. It really needs
# an active maintainer. Removal in 30 days. Bug #621470.

Re: [sabayon-dev] GCC-5.x Migration

[Joost Ruis]

To ensure the compatibility within chroot AND be able to keep pushing
critical updates to our users we indeed best create a new branch for this.
"add more SSD capacity first" Sure we could do that but looking at the
current state of the donations I wonder who is going to pay for that.

I volunteer to work on this new branch to get it done.

On Wed, Jun 7, 2017 at 6:55 AM, Fabio Erculiani  wrote:

> snapshots are taken at unpredictable intervals, so unless I take one and
> store it to some separate safe place, we should not rely on them for these
> things. Also, this is going to take several weeks, and in the meantime we
> need to keep pushing updates such as security ones.
>
> We also need to keep in mind that we likely need 2x space during this
> period. I need to check how we are doing wrt capacity. If that's not the
> case, we need to add more SSD capacity first ;-)
>
>
> On Tue, May 30, 2017 at 2:13 PM, Joost Ruis 
> wrote:
>
>> Do we keep daily snapshots from the chroot? I mean, can we easily revert
>> if we decide bumping GCC wasn't such a great plan?!
>>
>> On Tue, May 30, 2017 at 2:09 PM, Ettore Di Giacinto <
>> mud...@sabayonlinux.org> wrote:
>>
>>> Before going for that road, I'd like to see the GCC bump using a custom
>>> eclass forked from toolchain one (easier to distinguish changes then)
>>>
>>> Il mar 30 mag 2017, 14:07 Joost Ruis  ha
>>> scritto:
>>>
>>>> @Fabio. Hmm this might be a good idea!
>>>>
>>>> On Tue, May 30, 2017 at 1:10 PM, Fabio Erculiani <
>>>> fabio.erculi...@gmail.com> wrote:
>>>>
>>>>> Should we create a new branch for this? Sounds like a very disruptive
>>>>> change.
>>>>>
>>>>> On Tue, May 30, 2017 at 4:33 AM, Jerrod Frost 
>>>>> wrote:
>>>>>
>>>>>> When is this going to happen? It's like to see this move forward.
>>>>>> Mudler, any objections?
>>>>>>
>>>>>> On Sat, May 6, 2017, 5:50 AM Geaaru  wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I push last fix fo set gcc profile on sys-devel/gcc package. I test
>>>>>>> compilation on a fresh sabayon image and it seems work fine.
>>>>>>>
>>>>>>> Can we proceed with merge pull request and try to start compilation
>>>>>>> of gcc-5.4.0-r3?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>> On Thu, 2017-05-04 at 22:08 +, Jerrod Frost wrote:
>>>>>>>
>>>>>>> I'm prepared for breakage in limbo. When the war begins let me know
>>>>>>> :)
>>>>>>>
>>>>>>> On Thu, May 4, 2017 at 4:54 PM Geaaru  wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I confirm that there is a lot of work on upgrade to gcc-5.4.0 (a lot
>>>>>>> of packages to recompile) but FWIS could optimize a lot of package and
>>>>>>> there are packages like for example mongodb-3.4 that need a >=gcc-5.x.
>>>>>>>
>>>>>>> Gcc-5.4.0 is now stable on gentoo and could be a good idea plan an
>>>>>>> upgrade.
>>>>>>>
>>>>>>> I test compilation of ebuild sys-devel/base-gcc and sys-devel/gcc
>>>>>>> for both amd64 and arm and installation is been complete correctly. I 
>>>>>>> think
>>>>>>> that there is only a fix... avoid set of gcc-5 at the end of base-gcc 
>>>>>>> and
>>>>>>> move it at the end of the installation of sys-devel/gcc.
>>>>>>>
>>>>>>> My cent
>>>>>>> G.
>>>>>>>
>>>>>>> On May 4, 2017 22:15, "Mitch Harder" 
>>>>>>> wrote:
>>>>>>>
>>>>>>> I'm seeing some discussion about updating our Sabayon gcc ebuilds to
>>>>>>> version 5.4.0
>>>>>>>
>>>>>>> You guys probably already knew this, but just in case this slipped
>>>>>>> through the cracks, I want to make sure everyone is fore-warned that
>>>>>>> this will be a really big chunk of work once we start using GCC-5.4.0
>>>>>>>

Re: [sabayon-dev] GCC-5.x Migration

[Joost Ruis]

Do we keep daily snapshots from the chroot? I mean, can we easily revert if
we decide bumping GCC wasn't such a great plan?!

On Tue, May 30, 2017 at 2:09 PM, Ettore Di Giacinto  wrote:

> Before going for that road, I'd like to see the GCC bump using a custom
> eclass forked from toolchain one (easier to distinguish changes then)
>
> Il mar 30 mag 2017, 14:07 Joost Ruis  ha scritto:
>
>> @Fabio. Hmm this might be a good idea!
>>
>> On Tue, May 30, 2017 at 1:10 PM, Fabio Erculiani <
>> fabio.erculi...@gmail.com> wrote:
>>
>>> Should we create a new branch for this? Sounds like a very disruptive
>>> change.
>>>
>>> On Tue, May 30, 2017 at 4:33 AM, Jerrod Frost 
>>> wrote:
>>>
>>>> When is this going to happen? It's like to see this move forward.
>>>> Mudler, any objections?
>>>>
>>>> On Sat, May 6, 2017, 5:50 AM Geaaru  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I push last fix fo set gcc profile on sys-devel/gcc package. I test
>>>>> compilation on a fresh sabayon image and it seems work fine.
>>>>>
>>>>> Can we proceed with merge pull request and try to start compilation of
>>>>> gcc-5.4.0-r3?
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>> On Thu, 2017-05-04 at 22:08 +, Jerrod Frost wrote:
>>>>>
>>>>> I'm prepared for breakage in limbo. When the war begins let me know :)
>>>>>
>>>>> On Thu, May 4, 2017 at 4:54 PM Geaaru  wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I confirm that there is a lot of work on upgrade to gcc-5.4.0 (a lot
>>>>> of packages to recompile) but FWIS could optimize a lot of package and
>>>>> there are packages like for example mongodb-3.4 that need a >=gcc-5.x.
>>>>>
>>>>> Gcc-5.4.0 is now stable on gentoo and could be a good idea plan an
>>>>> upgrade.
>>>>>
>>>>> I test compilation of ebuild sys-devel/base-gcc and sys-devel/gcc for
>>>>> both amd64 and arm and installation is been complete correctly. I think
>>>>> that there is only a fix... avoid set of gcc-5 at the end of base-gcc and
>>>>> move it at the end of the installation of sys-devel/gcc.
>>>>>
>>>>> My cent
>>>>> G.
>>>>>
>>>>> On May 4, 2017 22:15, "Mitch Harder" 
>>>>> wrote:
>>>>>
>>>>> I'm seeing some discussion about updating our Sabayon gcc ebuilds to
>>>>> version 5.4.0
>>>>>
>>>>> You guys probably already knew this, but just in case this slipped
>>>>> through the cracks, I want to make sure everyone is fore-warned that
>>>>> this will be a really big chunk of work once we start using GCC-5.4.0
>>>>> on our packages.
>>>>>
>>>>> At a minimum, we need to rebuild every package that uses C++ since the
>>>>> ABI changes.
>>>>>
>>>>> We may decide to rebuild everything just to insure consistency.
>>>>>
>>>>> Reading some discussions on the Gentoo M/L, mixing GCC 4.9.4 and 5.4.0
>>>>> is discouraged by several developers, but there do seem to be a few
>>>>> who think it can be managed.
>>>>>
>>>>> The Gentoo news item for this upgrade recommends using a
>>>>> revdep-rebuild command to identify the affected C++ packages:
>>>>>
>>>>> revdep-rebuild --library 'libstdc++.so.6'  -- --exclude gcc
>>>>>
>>>>> When I ran this on my systems, I quickly discovered that this method
>>>>> will not discern packages that have already been rebuilt with
>>>>> GCC-5.4.0.  It just gives me the same list every time.
>>>>>
>>>>> So, if we encounter build issues (and we almost certainly will since
>>>>> some packages will attempt to build out of order), we'll have to come
>>>>> up with our own system for keeping up with what's been rebuilt, and
>>>>> what packages remain.
>>>>>
>>>>> I apologize if this has already been discussed, but I hadn't run
>>>>> across any discussion on GCC 5.x, and wanted to make sure.
>>>>>
>>>>> Thanks,
>>>>> Mitch...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>  Fabio Erculiani
>>>
>>>
>>>
>>>
>>
>> --
>
> Regards,
> Ettore Di Giacinto - Sabayon Project Lead
>
>
>
>
>

Re: [sabayon-dev] GCC-5.x Migration

[Joost Ruis]

@Fabio. Hmm this might be a good idea!

On Tue, May 30, 2017 at 1:10 PM, Fabio Erculiani 
wrote:

> Should we create a new branch for this? Sounds like a very disruptive
> change.
>
> On Tue, May 30, 2017 at 4:33 AM, Jerrod Frost 
> wrote:
>
>> When is this going to happen? It's like to see this move forward. Mudler,
>> any objections?
>>
>> On Sat, May 6, 2017, 5:50 AM Geaaru  wrote:
>>
>>> Hi,
>>>
>>> I push last fix fo set gcc profile on sys-devel/gcc package. I test
>>> compilation on a fresh sabayon image and it seems work fine.
>>>
>>> Can we proceed with merge pull request and try to start compilation of
>>> gcc-5.4.0-r3?
>>>
>>> Thanks
>>>
>>>
>>> On Thu, 2017-05-04 at 22:08 +, Jerrod Frost wrote:
>>>
>>> I'm prepared for breakage in limbo. When the war begins let me know :)
>>>
>>> On Thu, May 4, 2017 at 4:54 PM Geaaru  wrote:
>>>
>>> Hi,
>>>
>>> I confirm that there is a lot of work on upgrade to gcc-5.4.0 (a lot of
>>> packages to recompile) but FWIS could optimize a lot of package and there
>>> are packages like for example mongodb-3.4 that need a >=gcc-5.x.
>>>
>>> Gcc-5.4.0 is now stable on gentoo and could be a good idea plan an
>>> upgrade.
>>>
>>> I test compilation of ebuild sys-devel/base-gcc and sys-devel/gcc for
>>> both amd64 and arm and installation is been complete correctly. I think
>>> that there is only a fix... avoid set of gcc-5 at the end of base-gcc and
>>> move it at the end of the installation of sys-devel/gcc.
>>>
>>> My cent
>>> G.
>>>
>>> On May 4, 2017 22:15, "Mitch Harder" 
>>> wrote:
>>>
>>> I'm seeing some discussion about updating our Sabayon gcc ebuilds to
>>> version 5.4.0
>>>
>>> You guys probably already knew this, but just in case this slipped
>>> through the cracks, I want to make sure everyone is fore-warned that
>>> this will be a really big chunk of work once we start using GCC-5.4.0
>>> on our packages.
>>>
>>> At a minimum, we need to rebuild every package that uses C++ since the
>>> ABI changes.
>>>
>>> We may decide to rebuild everything just to insure consistency.
>>>
>>> Reading some discussions on the Gentoo M/L, mixing GCC 4.9.4 and 5.4.0
>>> is discouraged by several developers, but there do seem to be a few
>>> who think it can be managed.
>>>
>>> The Gentoo news item for this upgrade recommends using a
>>> revdep-rebuild command to identify the affected C++ packages:
>>>
>>> revdep-rebuild --library 'libstdc++.so.6'  -- --exclude gcc
>>>
>>> When I ran this on my systems, I quickly discovered that this method
>>> will not discern packages that have already been rebuilt with
>>> GCC-5.4.0.  It just gives me the same list every time.
>>>
>>> So, if we encounter build issues (and we almost certainly will since
>>> some packages will attempt to build out of order), we'll have to come
>>> up with our own system for keeping up with what's been rebuilt, and
>>> what packages remain.
>>>
>>> I apologize if this has already been discussed, but I hadn't run
>>> across any discussion on GCC 5.x, and wanted to make sure.
>>>
>>> Thanks,
>>> Mitch...
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
> --
>  Fabio Erculiani
>
>
>
>

Re: [sabayon-dev] Dealing with our split kde-apps/kde-l10n

[Joost Ruis]

Then I will go ahead and remove split language packages for KDE / Plasma in
Entropy

On Mon, May 15, 2017 at 6:41 PM, Jerrod Frost  wrote:

> I'm for the 250M. Dirty hacks and splitting ebuilds makes me cringe :(
>
> On Mon, May 15, 2017 at 11:28 AM Ettore Di Giacinto <
> mud...@sabayonlinux.org> wrote:
>
>> Sadly the only solution i see is on the Entropy side (but would be a
>> clunky hack anyway). I'd guess 250 MB nowadays is not such a big deal
>>
>> Il lun 15 mag 2017, 11:21 Joost Ruis  ha scritto:
>>
>>> I guess I will just go ahead and see where this ends.
>>>
>>> On Sun, May 14, 2017 at 10:19 PM, Jerrod Frost 
>>> wrote:
>>>
>>>> 250M isn't that bad in my opinion, but I can see this being a pain..
>>>>
>>>> On Sat, May 13, 2017, 3:50 PM Nicolas Sebrecht <
>>>> nicolas.s-...@laposte.net> wrote:
>>>>
>>>>> On Sat, May 13, 2017 at 04:20:42PM +0200, Joost Ruis wrote:
>>>>>
>>>>> >It seems upstream Gentoo dropped the kde-apps/kde-l10n package and
>>>>> >languages are now compiled and installed with the different
>>>>> kde-apps:
>>>>>
>>>>> >[ebuild U  ] kde-apps/akonadi-17.04.1:5::gentoo
>>>>> [16.12.3:5::gentoo]
>>>>> >USE="mysql tools xml -debug -designer -postgres -sqlite {-test}"
>>>>> 1,272 KiB
>>>>> >[uninstall ] kde-apps/kde-l10n-17.04.0:5::sabayon-distro
>>>>> > USE="minimal" LINGUAS="ar bg bs ca cs da de el en_GB es et eu fi
>>>>> fr ga gl
>>>>> >he hi hr hu is it ja kk km ko lt lv nb nds nl nn pa pl pt pt_BR
>>>>> ro ru sk
>>>>> >sl sr sv tr uk zh_CN zh_TW -ia -mr -ug -wa"
>>>>> >[blocks b  ] kde-apps/kde-l10n ("kde-apps/kde-l10n" is
>>>>> blocking
>>>>> >kde-apps/akonadi-17.04.1)
>>>>>
>>>>> >This could easily grow our default KDE installation with 250MB.
>>>>> >How are we going to deal with this issue?
>>>>>
>>>>> Would it be possible to package the i18n files after complilation?
>>>>>
>>>>> --
>>>>> Nicolas Sebrecht
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>
>> Regards,
>> Ettore Di Giacinto - Sabayon Project Lead
>>
>>
>>
>
>
>

Re: [sabayon-dev] Dealing with our split kde-apps/kde-l10n

[Joost Ruis]

I guess I will just go ahead and see where this ends.

On Sun, May 14, 2017 at 10:19 PM, Jerrod Frost  wrote:

> 250M isn't that bad in my opinion, but I can see this being a pain..
>
> On Sat, May 13, 2017, 3:50 PM Nicolas Sebrecht 
> wrote:
>
>> On Sat, May 13, 2017 at 04:20:42PM +0200, Joost Ruis wrote:
>>
>> >It seems upstream Gentoo dropped the kde-apps/kde-l10n package and
>> >languages are now compiled and installed with the different kde-apps:
>>
>> >[ebuild U  ] kde-apps/akonadi-17.04.1:5::gentoo
>> [16.12.3:5::gentoo]
>> >USE="mysql tools xml -debug -designer -postgres -sqlite {-test}"
>> 1,272 KiB
>> >[uninstall ] kde-apps/kde-l10n-17.04.0:5::sabayon-distro
>> > USE="minimal" LINGUAS="ar bg bs ca cs da de el en_GB es et eu fi fr
>> ga gl
>> >he hi hr hu is it ja kk km ko lt lv nb nds nl nn pa pl pt pt_BR ro
>> ru sk
>> >sl sr sv tr uk zh_CN zh_TW -ia -mr -ug -wa"
>> >[blocks b  ] kde-apps/kde-l10n ("kde-apps/kde-l10n" is blocking
>> >kde-apps/akonadi-17.04.1)
>>
>> >This could easily grow our default KDE installation with 250MB.
>> >How are we going to deal with this issue?
>>
>> Would it be possible to package the i18n files after complilation?
>>
>> --
>> Nicolas Sebrecht
>>
>>
>
>
>

[sabayon-dev] Dealing with our split kde-apps/kde-l10n

[Joost Ruis]

It seems upstream Gentoo dropped the kde-apps/kde-l10n package and
languages are now compiled and installed with the different kde-apps:

[ebuild U  ] kde-apps/akonadi-17.04.1:5::gentoo [16.12.3:5::gentoo]
USE="mysql tools xml -debug -designer -postgres -sqlite {-test}" 1,272 KiB
[uninstall ] kde-apps/kde-l10n-17.04.0:5::sabayon-distro  USE="minimal"
LINGUAS="ar bg bs ca cs da de el en_GB es et eu fi fr ga gl he hi hr hu is
it ja kk km ko lt lv nb nds nl nn pa pl pt pt_BR ro ru sk sl sr sv tr uk
zh_CN zh_TW -ia -mr -ug -wa"
[blocks b  ] kde-apps/kde-l10n ("kde-apps/kde-l10n" is blocking
kde-apps/akonadi-17.04.1)

This could easily grow our default KDE installation with 250MB.
How are we going to deal with this issue?

Re: [sabayon-dev] idea: switching back to ffmpeg

[Joost Ruis]

What matters to me is what works best for our users.

The fact that https://gpo.zugaina.org/media-video/obs-studio has a hard dep
on ffmpeg could be because the Gentoo maintainer isn't aware of the virtual
package. I'm not technically up to date, but if libav is indeed breaking
away with ffmpeg compatibility or visa versa we should decide what to use.

Either way I know we have good contacts with upstream libav and we could
get answers there. (Ettore could you investigate?)

Having said this. We are an opensource project and if there are issues with
upstream software we at least investigate and inform upstream about this.

Just my thoughts.

On Tue, Apr 25, 2017 at 11:37 PM, Jerrod Frost  wrote:

> Interesting. LibAV is supposedly cleaner, harder code, but much of libAV
> ends up in ffmpeg anyway from what I'm reading and ffmpeg has more support
> for most other applications etc. Their problem is ffmpeg tends to be more
> bloated and risky about adopting patches and code? As long as we're not
> updating ffmpeg every chance we get and wait for ffmpeg releases to prove
> their stability etc, I think we may be fine. Sticking to libav may prove
> more secure and show support for applications that choose to support libav.
> I'm not for or against this currently.
>
> Does anyone else have any thoughts on this?
>
> On Tue, Apr 25, 2017 at 12:49 PM Sławomir Nizio <
> slawomir.ni...@sabayon.org> wrote:
>
>> Hello,
>>
>> The libav project has served Sabayon well, and the fact it appeared and
>> has been actively developed might have made great impact on the world of
>> audio/video libraries. However, this may be a good time to switch back
>> to ffmpeg. There are references on IRC that it's wanted by users because
>> of projects that work only with ffmpeg.
>>
>> I analysed it and concluded that there should be no big problems about
>> the switch. Here is what I found out. I used 3.2.4 as target, which is
>> the last stable version.
>>
>> No package should be lost after the switch. First of all, it seems that
>> there are no "actual" packages in Gentoo tree that work with libav but
>> not ffmpeg. (I took a simplistic approach for checking this, parsing in
>> a way and comparing reverse dependencies listings from
>> http://qa-reports.gentoo.org/, but it believe it was accurate.) Second,
>> according to bug reports about incompatibilities with ffmpeg 3, packages
>> that Sabayon provides with ffmpeg USE flag enabled have either patches
>> (on BZ or at upstream) or new versions available that should correct the
>> failure. Certainly, I didn't check that patches myself, so there is
>> still a risk, but basing on the whole, it's negligible. It is also
>> possible that a failure has not been reported. Comments on interesting
>> cases I noted down are below.
>>
>> tracker bugs:
>> https://bugs.gentoo.org/show_bug.cgi?id=574788 (ffmpeg-3) - [TRACKER]
>> media-video/ffmpeg-3.0 transition
>> https://bugs.gentoo.org/show_bug.cgi?id=575538 [TRACKER]
>> media-video/ffmpeg-3.0 stabilization
>>
>> not listed above, so I'm listing it here (new version is available):
>> https://bugs.gentoo.org/show_bug.cgi?id=609640
>> media-libs/xine-lib-1.2.6-r2 fails to compile after upgrading to
>> media-video/ffmpeg-3.2.4
>>
>> about to be removed from Gentoo:
>> https://bugs.gentoo.org/show_bug.cgi?id=575824 app-cdr/backlite-1.0.3-r1
>> : src/.../k9avidecode.cpp:241:33: error: ‘PIX_FMT_RGB24’ was not
>> declared in this scope
>>
>> easy workaround is to disable this flag on ffmpeg (not much useful, no
>> reverse dependency problems):
>> https://bugs.gentoo.org/show_bug.cgi?id=598054 =media-video/ffmpeg-3.1.5
>> can't link properly when USE="jpeg2k"
>>
>>
>>
>> I can do the work. Due to a large number of packages to rebuild and the
>> need to handle issues, if any, the work would be spread across a few
>> days, perhaps up to about a week. Until finished, no other package
>> related work could be done in Entropy (!), which means a short freeze.
>>
>> I could start at the end of this week, or even a little earlier, if
>> nobody complains.
>>
>> Is there something I missed that makes the switch not possible?
>>
>>
>
>
>

Re: [sabayon-dev] firewalld +gui flag?

[Joost Ruis]

"Don't only anaconda and fwknop depend on it?"

Yes.

"On your system you probably have anaconda which most users shouldn't"

Nope. But I guess this dep from anaconda was never removed after
installation. (All users have this installed who used Anaconda).
To be clear. This is on a VERY RECENT clean install system where I used
latest and greatest Anaconda version.

On Sun, Apr 9, 2017 at 10:58 AM, Sławomir Nizio 
wrote:

> > I reverted this.
> > https://pastebin.com/raw/wjvV6ijK
> >
> > Too much bloat. If you really want to have this it should be split.
> >
> >   gui? (
> >   x11-libs/gtk+:3
> >   dev-python/PyQt4[${PYTHON_USEDEP}]
> >   )
> >
> >
> > BLOAT FROM HELL!
>
> Don't only anaconda and fwknop depend on it? On your system you probably
> have anaconda which most users shouldn't (I saw several ISOs have it,
> but I guess it might have been fixed with some recent commit I can't find).
>
>

Re: [sabayon-dev] firewalld +gui flag?

[Joost Ruis]

I reverted this.
https://pastebin.com/raw/wjvV6ijK

Too much bloat. If you really want to have this it should be split.

gui? (
x11-libs/gtk+:3
dev-python/PyQt4[${PYTHON_USEDEP}]
)


BLOAT FROM HELL!


On Sat, Apr 8, 2017 at 11:48 AM, Sławomir Nizio 
wrote:

> > https://bugs.sabayon.org/show_bug.cgi?id=5354
> >
> > Can we have someone look into this please?
>
> I took a look; seems fine to enable it, which will be done.
>
>

Re: [sabayon-dev] Anaconda - python breakage?

[Joost Ruis]

I just successfully installed the latest daily MATE -dev spin using updated
Anaconda.

Problems seems resolved.

On Mon, Apr 3, 2017 at 3:40 PM, Joost Ruis  wrote:

> Thanks.
>
> As soon new daily -dev images hit the mirrors I'll give it a try.
>
>
> On Sun, Apr 2, 2017 at 12:57 PM, Fabio Erculiani 
> wrote:
>
>> That has unfortunately nothing to do with the issue.
>> It's just a warning...
>>
>> I am pushing a fixed anaconda version to sabayon-limbo now.
>>
>> The root cause was a change in behavior in the new python-exec Gentoo
>> package in the way it builds python file paths:
>>
>> Example of os.path.dirname(__file__):
>>
>> New (wrong, python-exec output): /usr/lib/python-exec/python2.7
>> /../../../lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes
>> Old (correct, and expected python-exec output):
>> /usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes
>>
>> The fix is:
>>
>> diff --git a/pyanaconda/ui/gui/__init__.py b/pyanaconda/ui/gui/__init__.p
>> y
>> index 71d8926c1..bde074d5f 100644
>> --- a/pyanaconda/ui/gui/__init__.py
>> +++ b/pyanaconda/ui/gui/__init__.py
>> @@ -507,9 +507,9 @@ class GraphicalUserInterface(UserInterface):
>> ANACONDA_WINDOW_GROUP.add_window(self.mainWindow)
>>
>> basemask = "pyanaconda.ui"
>> -basepath = os.path.dirname(__file__)
>> +basepath = os.path.normpath(os.path.dirname(__file__))
>> updatepath = "/tmp/updates/pyanaconda/ui"
>> -sitepackages = [os.path.join(dir, "pyanaconda", "ui")
>> +sitepackages = [os.path.normpath(os.path.join(dir, "pyanaconda",
>> "ui"))
>> for dir in site.getsitepackages()]
>> pathlist = set([updatepath, basepath] + sitepackages)
>>
>>
>> On Tue, Mar 28, 2017 at 3:34 PM, Jerrod Frost 
>> wrote:
>>
>>> I've been discussing an issue with Joost. Something has changed to cause
>>> Anaconda to not want to recognize HDDs/SSDs. I'm assuming the following is
>>> related?
>>>
>>> /usr/lib64/python2.7/blivet/util.py:14: PyGiWarning: BlockDev was
>>> imported without specifying a version first. Use
>>> gi.require_version('BlockDev', '0.1') before import to ensure that the
>>> right version gets loaded from gi.repository import BlockDev as blockdev
>>>
>>> The system itself sees the block devices just fine, and fdisk finds
>>> disks just fine. This is occurring on the latest daily ISO.
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Fabio Erculiani
>>
>>
>>
>>
>

Re: [sabayon-dev] Anaconda - python breakage?

[Joost Ruis]

Thanks.

As soon new daily -dev images hit the mirrors I'll give it a try.


On Sun, Apr 2, 2017 at 12:57 PM, Fabio Erculiani  wrote:

> That has unfortunately nothing to do with the issue.
> It's just a warning...
>
> I am pushing a fixed anaconda version to sabayon-limbo now.
>
> The root cause was a change in behavior in the new python-exec Gentoo
> package in the way it builds python file paths:
>
> Example of os.path.dirname(__file__):
>
> New (wrong, python-exec output): /usr/lib/python-exec/python2.
> 7/../../../lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes
> Old (correct, and expected python-exec output): /usr/lib64/python2.7/site-
> packages/pyanaconda/ui/gui/spokes
>
> The fix is:
>
> diff --git a/pyanaconda/ui/gui/__init__.py b/pyanaconda/ui/gui/__init__.py
> index 71d8926c1..bde074d5f 100644
> --- a/pyanaconda/ui/gui/__init__.py
> +++ b/pyanaconda/ui/gui/__init__.py
> @@ -507,9 +507,9 @@ class GraphicalUserInterface(UserInterface):
> ANACONDA_WINDOW_GROUP.add_window(self.mainWindow)
>
> basemask = "pyanaconda.ui"
> -basepath = os.path.dirname(__file__)
> +basepath = os.path.normpath(os.path.dirname(__file__))
> updatepath = "/tmp/updates/pyanaconda/ui"
> -sitepackages = [os.path.join(dir, "pyanaconda", "ui")
> +sitepackages = [os.path.normpath(os.path.join(dir, "pyanaconda",
> "ui"))
> for dir in site.getsitepackages()]
> pathlist = set([updatepath, basepath] + sitepackages)
>
>
> On Tue, Mar 28, 2017 at 3:34 PM, Jerrod Frost 
> wrote:
>
>> I've been discussing an issue with Joost. Something has changed to cause
>> Anaconda to not want to recognize HDDs/SSDs. I'm assuming the following is
>> related?
>>
>> /usr/lib64/python2.7/blivet/util.py:14: PyGiWarning: BlockDev was
>> imported without specifying a version first. Use
>> gi.require_version('BlockDev', '0.1') before import to ensure that the
>> right version gets loaded from gi.repository import BlockDev as blockdev
>>
>> The system itself sees the block devices just fine, and fdisk finds disks
>> just fine. This is occurring on the latest daily ISO.
>>
>>
>>
>>
>
>
> --
> Fabio Erculiani
>
>
>
>

Re: [sabayon-dev] Anaconda - python breakage?

[Joost Ruis]

Here is /tmp/anaconda.log

Another issue with Anaconda is that it depends on =sys-libs/libsepol-2.3*
that is not in Portage anymore (for a long time).
This all makes me think Anaconda is not being maintained and should be
dropped.



On Tue, Mar 28, 2017 at 5:14 PM, Joost Ruis  wrote:

> I can confirm this with several spins tested on different baremetals.
>
> On Tue, Mar 28, 2017 at 3:34 PM, Jerrod Frost 
> wrote:
>
>> I've been discussing an issue with Joost. Something has changed to cause
>> Anaconda to not want to recognize HDDs/SSDs. I'm assuming the following is
>> related?
>>
>> /usr/lib64/python2.7/blivet/util.py:14: PyGiWarning: BlockDev was
>> imported without specifying a version first. Use
>> gi.require_version('BlockDev', '0.1') before import to ensure that the
>> right version gets loaded from gi.repository import BlockDev as blockdev
>>
>> The system itself sees the block devices just fine, and fdisk finds disks
>> just fine. This is occurring on the latest daily ISO.
>>
>>
>>
>>
>
09:22:56,832 WARN anaconda: /usr/lib64/python2.7/site-packages/blivet/util.py:14: PyGIWarning: BlockDev was imported without specifying a version first. Use gi.require_version('BlockDev', '0.1') before import to ensure that the right version gets loaded.
  from gi.repository import BlockDev as blockdev

09:23:07,508 INFO anaconda: /usr/sbin/anaconda 22.8-1
09:23:08,186 INFO anaconda: created new libuser.conf at /tmp/libuser.bVEbsY with instPath="/mnt/sysimage"
09:23:08,190 INFO anaconda: 3932160 kB (3840 MB) are available
09:23:08,199 INFO anaconda: check_memory(): total:3932160, needed:320, graphical:410
09:23:08,211 INFO anaconda: Unable to connect to DBus session bus: ('Unable to connect to session bus: %s', GLib.Error('The connection is closed', 'g-io-error-quark', 18))
09:23:08,212 INFO anaconda: Not doing 'early exception handler' in live installation
09:23:08,213 INFO anaconda: Not doing 'start audit daemon' in live installation
09:23:08,213 INFO anaconda: anaconda called with cmdline = ['/usr/sbin/anaconda', '--liveinst', '--noselinux', '--method=hd://:///run/install/source', '--lang', 'en_US.UTF-8']
09:23:08,214 INFO anaconda: Default encoding = ascii 
09:23:08,298 INFO anaconda: Parsing kickstart: /usr/share/anaconda/interactive-defaults.ks
09:23:09,182 DEBUG anaconda: network: devices found ['enp5s1', 'bond0']
09:23:09,297 WARN anaconda: Device enp5s1 don't have property PermHwAddress
09:23:09,479 WARN anaconda: Device enp5s1 don't have property PermHwAddress
09:23:09,494 DEBUG anaconda: network: no ifcfg file for enp5s1
09:23:09,506 DEBUG anaconda: network: missing ifcfgs created for devices ['enp5s1']
09:23:09,660 DEBUG anaconda: updating host name sabayon.local
09:23:09,703 INFO anaconda: Running Thread: AnaWaitForConnectingNMThread (139786555750144)
09:23:09,720 WARN anaconda.stdout: Not asking for VNC because we don't have Xvnc
09:23:09,721 INFO anaconda: Display mode = g
09:23:09,723 INFO anaconda: 3932160 kB (3840 MB) are available
09:23:09,734 INFO anaconda: check_memory(): total:3932160, needed:320, graphical:410
09:23:10,017 WARN anaconda: /usr/lib64/python2.7/site-packages/meh/ui/gui.py:23: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk

09:23:10,079 WARN anaconda: /usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/__init__.py:26: PyGIWarning: AnacondaWidgets was imported without specifying a version first. Use gi.require_version('AnacondaWidgets', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gdk, Gtk, AnacondaWidgets, Keybinder, GdkPixbuf, GLib, GObject

09:23:10,087 WARN anaconda: /usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/__init__.py:26: PyGIWarning: Keybinder was imported without specifying a version first. Use gi.require_version('Keybinder', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gdk, Gtk, AnacondaWidgets, Keybinder, GdkPixbuf, GLib, GObject

09:23:10,150 INFO anaconda: got 0 NTP servers from DHCP
09:23:10,151 INFO anaconda: Thread Done: AnaWaitForConnectingNMThread (139786555750144)
09:23:13,968 INFO anaconda: Sabayon Core is the highest priority installclass, using it
09:23:14,139 INFO anaconda: bootloader GRUB2 on X86 platform
09:23:14,141 INFO anaconda: Detected 3.75 GiB of memory
09:23:14,145 INFO anaconda: Suggested swap size (3.75 GiB) exceeds 10 % of disk space, using 10 % of disk space (0.0) instead.
09:23:14,147 

Re: [sabayon-dev] Anaconda - python breakage?

[Joost Ruis]

I can confirm this with several spins tested on different baremetals.

On Tue, Mar 28, 2017 at 3:34 PM, Jerrod Frost  wrote:

> I've been discussing an issue with Joost. Something has changed to cause
> Anaconda to not want to recognize HDDs/SSDs. I'm assuming the following is
> related?
>
> /usr/lib64/python2.7/blivet/util.py:14: PyGiWarning: BlockDev was
> imported without specifying a version first. Use
> gi.require_version('BlockDev', '0.1') before import to ensure that the
> right version gets loaded from gi.repository import BlockDev as blockdev
>
> The system itself sees the block devices just fine, and fdisk finds disks
> just fine. This is occurring on the latest daily ISO.
>
>
>
>

Re: [sabayon-dev] Login manager doesn't start properly and /etc/hosts missed

[Joost Ruis]

I think it is supposed to be like that if you use the text-installer...

On Thu, Feb 16, 2017 at 1:09 PM, sabayonino  wrote:

> Hi guys
>
> I installed SL from tar.bz2 and KDE-DEV via text-installer
>
> everything went well.
>
> I've enabled sddm or lightdm as login manager. (2 different installations)
>
> It didn't start automatically (TTY login appears) . I forced the service
> to start loginmanger
>
> # systemctl restart lightdm|sddm
>
> Similar issue is reported here :
> https://forum.sabayon.org/viewtopic.php?f=90&t=33562
> (Italian shed)
>
> I think that some service is missed and need to start
>
> So I discovered that /etc/hosts file is missing
> restored from another installation
>
> according my running hostname:
> 127.0.0.1   localhost sabayon sabayon-dell  sabayon.local
> ::1 localhost ip6-localhost ip6-loopback sabayon.local
> ff02::1 ip6-allnodes sabayon.local
> ff02::2 ip6-allrouters sabayon.local
>
> see cookbug attachment
>
> Cheers :)
>
>
>
>
>
>
>
>
>

Re: [sabayon-dev] Sabayon integration on LXC project!

[Joost Ruis]

Thanks for the work.
Is there any documentation written for users how to use this?

On Thu, Feb 2, 2017 at 10:52 AM, Geaaru  wrote:

> Hi guys,
>
> i'm happy to announce that I completed integration of lxc-sabayon
> template to LXC project for both armv7 and amd64 arch:
>
> https://github.com/lxc/lxc/pull/1398
>
> Cheers
> G.
>
>
>

Re: [sabayon-dev] Missing guest-additions#4.9.0

[Joost Ruis]

https://bugs.gentoo.org/show_bug.cgi?id=603472

On Fri, Jan 27, 2017 at 2:56 PM, Joost Ruis  wrote:

> We know.
>
> On Thu, Jan 26, 2017 at 11:17 PM, sabayonino  wrote:
>
>> Hi folks :)
>>
>> I've noticed that Vbox guest additions for 4.9.0 kernel is missing
>> (sabayonlinux.org repo)
>>
>> https://packages.sabayon.org/quicksearch?q=guest-addi&x=0&y=0
>>
>> $ equo s guest-add -qv
>> app-emulation/virtualbox-guest-additions-5.1.12#3.10.0-sabayon
>> app-emulation/virtualbox-guest-additions-5.1.12#3.12.0-sabayon
>> app-emulation/virtualbox-guest-additions-5.1.12#3.18.0-sabayon
>> app-emulation/virtualbox-guest-additions-5.1.12#4.1.0-sabayon
>> app-emulation/virtualbox-guest-additions-5.1.12#4.4.0-sabayon
>> app-emulation/virtualbox-guest-additions-5.1.12#4.6.0-sabayon
>> app-emulation/virtualbox-guest-additions-5.1.12#4.7.0-sabayon
>> app-emulation/virtualbox-guest-additions-5.1.12#4.8.0-sabayon
>>
>> $ equo s linux-sabayon -qv
>> sys-kernel/linux-sabayon-3.10.104
>> sys-kernel/linux-sabayon-3.12.69
>> sys-kernel/linux-sabayon-3.18.45
>> sys-kernel/linux-sabayon-4.1.36
>> sys-kernel/linux-sabayon-4.4.44
>> sys-kernel/linux-sabayon-4.6.4
>> sys-kernel/linux-sabayon-4.7.10
>> sys-kernel/linux-sabayon-4.8.17
>> sys-kernel/linux-sabayon-4.9.5
>>
>> Thanks :-)
>>
>> cheers
>>
>>
>

Re: [sabayon-dev] Missing guest-additions#4.9.0

[Joost Ruis]

We know.

On Thu, Jan 26, 2017 at 11:17 PM, sabayonino  wrote:

> Hi folks :)
>
> I've noticed that Vbox guest additions for 4.9.0 kernel is missing
> (sabayonlinux.org repo)
>
> https://packages.sabayon.org/quicksearch?q=guest-addi&x=0&y=0
>
> $ equo s guest-add -qv
> app-emulation/virtualbox-guest-additions-5.1.12#3.10.0-sabayon
> app-emulation/virtualbox-guest-additions-5.1.12#3.12.0-sabayon
> app-emulation/virtualbox-guest-additions-5.1.12#3.18.0-sabayon
> app-emulation/virtualbox-guest-additions-5.1.12#4.1.0-sabayon
> app-emulation/virtualbox-guest-additions-5.1.12#4.4.0-sabayon
> app-emulation/virtualbox-guest-additions-5.1.12#4.6.0-sabayon
> app-emulation/virtualbox-guest-additions-5.1.12#4.7.0-sabayon
> app-emulation/virtualbox-guest-additions-5.1.12#4.8.0-sabayon
>
> $ equo s linux-sabayon -qv
> sys-kernel/linux-sabayon-3.10.104
> sys-kernel/linux-sabayon-3.12.69
> sys-kernel/linux-sabayon-3.18.45
> sys-kernel/linux-sabayon-4.1.36
> sys-kernel/linux-sabayon-4.4.44
> sys-kernel/linux-sabayon-4.6.4
> sys-kernel/linux-sabayon-4.7.10
> sys-kernel/linux-sabayon-4.8.17
> sys-kernel/linux-sabayon-4.9.5
>
> Thanks :-)
>
> cheers
>
>

Re: [sabayon-dev] Missing utilities on XFCE isos

[Joost Ruis]

There is no real reason for this actually. If you suggest packages to add,
we can simply add them.

On Sat, Nov 26, 2016 at 10:23 PM, André Jaenisch 
wrote:

> Hello,
>
> today I was asked, why we ship GIMP, but no calculator, calendar or
> mail client program on XFCE. Looking at
> http://dl.sabayon.org/stable/Sabayon_Linux_16.11_amd64_Xfce.iso.pkglist
> I can confirm that there is GIMP present, but no orange, *calc*,
> thunderbird or Claws Mail (not even mutt).
>
> What are the reasons for it? Can we add them or move some packages off
> instead?
>
> Cheers,
>
>
> André
>
>

Re: [sabayon-dev] TightVNC

[Joost Ruis]

☛  @@ [test] these packages haven't been removed yet:
☛   # [sabayonlinux.org] net-misc/tightvnc-1.3.10-r3
☛ # Needed by:
☛ # app-admin/anaconda-22.8-r2

^^ instant problem here.

On Tue, Oct 11, 2016 at 8:08 PM, Joost Ruis  wrote:

> I'll work on this.
>
> On Tue, Oct 11, 2016 at 5:50 PM, Mitch Harder <
> mitch.har...@sabayonlinux.org> wrote:
>
>> TightVNC has been tree-cleaned from Gentoo's portage tree.
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=368997
>>
>> We bundle TightVNC with nearly every ISO.
>>
>> TigerVNC seems like a good alternative, which is currently unavailable
>> in Entropy.  TigerVNC is a fork of TightVNC that has a better level of
>> developer support.
>>
>> So, we either need to maintain net-misc/tightvnc in our overlay (not
>> very appealing given the outstanding bugs against it) or switch to
>> net-misc/tigervnc (or another option I'm not thinking about).
>>
>>
>

Re: [sabayon-dev] TightVNC

[Joost Ruis]

I'll work on this.

On Tue, Oct 11, 2016 at 5:50 PM, Mitch Harder  wrote:

> TightVNC has been tree-cleaned from Gentoo's portage tree.
>
> https://bugs.gentoo.org/show_bug.cgi?id=368997
>
> We bundle TightVNC with nearly every ISO.
>
> TigerVNC seems like a good alternative, which is currently unavailable
> in Entropy.  TigerVNC is a fork of TightVNC that has a better level of
> developer support.
>
> So, we either need to maintain net-misc/tightvnc in our overlay (not
> very appealing given the outstanding bugs against it) or switch to
> net-misc/tigervnc (or another option I'm not thinking about).
>
>

Re: [sabayon-dev] Monthly

[Joost Ruis]

Agreed.

On Wed, Oct 5, 2016 at 7:18 AM, Ben Roberts 
wrote:

> +1 on this.
>
> IMHO stable and nightly would best fit their intended purpose, and be
> consistent with naming used by other software projects.
>
> On 5 Oct 2016 6:07 am, "André Jaenisch"  wrote:
>
>> What about Rolling (fka Daily) and ... um ... however distros like Mint
>> and Debian are categorized?
>> (I need my morning cup of black tea ...)
>>
>> Cheers, André
>>
>> wolfden schrieb:
>>
>> Since we are getting away from "Monthly" releases we should probably
>> change wording to something like Daily and Stable releases or Daily and
>> Quarterly releases.  Keeping the term Monthly is just going to cause
>> confusion with users and fifty billion questions of why do we have monthly
>> still when we don't have monthy.
>>
>> --
>> Kelly Schwartz
>> ~wolfden~
>>
>>
>>
>>
>>
>
>
>

Re: [sabayon-dev] LXQt ISO Testing - Hang After Loading Initramfs

[Joost Ruis]

I think the "the Sept 24th build" had a kernel + dracut. We were testing
that for a few days.

On Fri, Sep 30, 2016 at 12:28 AM, Mitch Harder <
mitch.har...@sabayonlinux.org> wrote:

> On Thu, Sep 29, 2016 at 1:47 PM, wolfden  wrote:
> > I do notice once logged in, seems the session is not setup properly for
> the
> > user.
> >
> > loginctl list-session
> >
> > shows
> >
> > Session UID USER SEAT
> > 1 0root   seat0
> >
> > So nm-applet fails as it can't find UID 1000 which is sabayonuser.
> >
> > Expect results should be:
> >
> > Session UID   USERSEAT
> >  2  1000  sabayonuser  seat0
> >  1 0root   seat0
> >
> > Issue with login manager I assume
> >
> > On Thu, Sep 29, 2016 at 12:39 PM, KJS  wrote:
> >>
> >> Try the Sept 29th ISO, it boot here for me.  I used dd to create the usb
> >> live stick
> >>
>
> The Sept 29th LXQt-dev iso is working for me.
>
> I'm not sure what was up with the Sept 24th build.  The md5sum
> matched, and I copied it to my USB stick using dd the same way as
> every other image.
>
> I'm also seeing the same results from 'loginctl list-session'.
>
> Also, Calamares is segfaulting for me.
>
>

Re: [sabayon-dev] Some release blockers

[Joost Ruis]

+1 for creating a (well designed!) welcome screen.

On Fri, Aug 5, 2016 at 12:50 AM, Francesco Ferretti 
wrote:

> I think the icons issue is caused by the fact that Gnome is no longer
> designed to support icons on desktop. Even if we fix that we will have some
> other troubles in future.
> My proposal is to completely remove the icons and place instead a welcome
> window like Fedora does on its live CD, so this will make installation more
> immediate and even more understandable by the users.
> So I found the script shipped with anaconda that create the welcome window
> and I was planning to make it compatible with calamares but, since we have
> replaced it with anaconda, I think is even more easy to make it work on our
> distro.
> Tomorrow I will test it on a daily image crossing my fingers.
>
> P.S.
> Excuse me for my delay in my reply but I was really busy during this days.
>
> On Thu, Aug 4, 2016 at 8:49 PM Joost Ruis  wrote:
>
>> Quick tested KDE dev spin (latest build from today) in Vbox.
>> Installer worked, again the mouse theme changed just like on MATE spin,
>> but everything installed it seems.
>>
>> When trying to reboot from live KDE spin, it simply logs into a fresh KDE
>> live session again.
>> After a reboot I notice SDDM being my DM and Kodi is selected as the
>> default session.
>> I select Plasma as my default session and it seems to load up fine.
>>
>> I will now try testing the same spin on a baremetal machine.
>>
>>
>>
>> On Thu, Aug 4, 2016 at 7:50 PM, Ettore Di Giacinto <
>> mud...@sabayonlinux.org> wrote:
>>
>>> Downloaded KDE, i'll try to test it later
>>>
>>> Il gio 4 ago 2016, 19:48 Joost Ruis  ha scritto:
>>>
>>>> Just tested MATE daily dev that was build today and it seems that
>>>> everything works just fine. (Even Grub theme got installed).
>>>> I'll try to find some time to test KDE spin
>>>>
>>>> On Mon, Aug 1, 2016 at 4:26 PM, Ettore Di Giacinto <
>>>> mud...@sabayonlinux.org> wrote:
>>>>
>>>>> About cycle release, soon i'll open up another thread wrt cycle
>>>>> release scheduling. Then main idea is to cut a stable release every 4
>>>>> months.
>>>>>
>>>>> Il lun 1 ago 2016, 15:29 Ettore Di Giacinto 
>>>>> ha scritto:
>>>>>
>>>>>> Indeed i blocked crons and holded monthly automatic releases, i think
>>>>>> thats also the occasion to switch to a "less often" release cycle for
>>>>>> monthly and cutting stable releases instead of automatic ones.
>>>>>>
>>>>>> Dailies will still be there of course, giving us the ability to test
>>>>>> better and having a good release everytime.
>>>>>>
>>>>>> KDE bug showed up since the plasma 5.6.7 bump, i suggest to give sddm
>>>>>> another shot now thlhat we have the occasion (we decided to not use it
>>>>>> because was having major issues with ati video cards).
>>>>>>
>>>>>> For GNOME, Francesco was taking care of it, but he was proposing to
>>>>>> remove icons at all and adding a welcome screen (like fedora/ubuntu and 
>>>>>> so
>>>>>> on) which is more user friendly than the current boot process. Francesco,
>>>>>> can you make a proposal of changes, or write few lines on what you was
>>>>>> thinking of?
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>>
>>>>>>
>>>>>> Il lun 1 ago 2016, 15:17 Fabio Erculiani 
>>>>>> ha scritto:
>>>>>>
>>>>>>> First of all,
>>>>>>> I think I fixed all outstanding anaconda issues (including the grub
>>>>>>> splash) and I am pushing anaconda-22.5 right now.
>>>>>>>
>>>>>>> But I still see at least a couple of major issues with the images I
>>>>>>> tested (GNOME and KDE):
>>>>>>> - GNOME desktop icons are incorrectly positioned, they are one above
>>>>>>> the other.
>>>>>>> - KDE LightDM integration (after install) seems broken, X starts at
>>>>>>> a very low resolution and there is no background (the background is 
>>>>>>> white).
>>>>>>>
>>>>>>> I think we should fix at least these two things before cutting a new
>>>>>>> release.
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>  Fabio Erculiani
>>>>>>>
>>>>>> --
>>>>>>
>>>>>> Regards,
>>>>>> Ettore Di Giacinto - Sabayon Project Lead
>>>>>>
>>>>>> --
>>>>>
>>>>> Regards,
>>>>> Ettore Di Giacinto - Sabayon Project Lead
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>
>>> Regards,
>>> Ettore Di Giacinto - Sabayon Project Lead
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>

Re: [sabayon-dev] Some release blockers

[Joost Ruis]

Quick tested KDE dev spin (latest build from today) in Vbox.
Installer worked, again the mouse theme changed just like on MATE spin, but
everything installed it seems.

When trying to reboot from live KDE spin, it simply logs into a fresh KDE
live session again.
After a reboot I notice SDDM being my DM and Kodi is selected as the
default session.
I select Plasma as my default session and it seems to load up fine.

I will now try testing the same spin on a baremetal machine.



On Thu, Aug 4, 2016 at 7:50 PM, Ettore Di Giacinto 
wrote:

> Downloaded KDE, i'll try to test it later
>
> Il gio 4 ago 2016, 19:48 Joost Ruis  ha scritto:
>
>> Just tested MATE daily dev that was build today and it seems that
>> everything works just fine. (Even Grub theme got installed).
>> I'll try to find some time to test KDE spin
>>
>> On Mon, Aug 1, 2016 at 4:26 PM, Ettore Di Giacinto <
>> mud...@sabayonlinux.org> wrote:
>>
>>> About cycle release, soon i'll open up another thread wrt cycle release
>>> scheduling. Then main idea is to cut a stable release every 4 months.
>>>
>>> Il lun 1 ago 2016, 15:29 Ettore Di Giacinto 
>>> ha scritto:
>>>
>>>> Indeed i blocked crons and holded monthly automatic releases, i think
>>>> thats also the occasion to switch to a "less often" release cycle for
>>>> monthly and cutting stable releases instead of automatic ones.
>>>>
>>>> Dailies will still be there of course, giving us the ability to test
>>>> better and having a good release everytime.
>>>>
>>>> KDE bug showed up since the plasma 5.6.7 bump, i suggest to give sddm
>>>> another shot now thlhat we have the occasion (we decided to not use it
>>>> because was having major issues with ati video cards).
>>>>
>>>> For GNOME, Francesco was taking care of it, but he was proposing to
>>>> remove icons at all and adding a welcome screen (like fedora/ubuntu and so
>>>> on) which is more user friendly than the current boot process. Francesco,
>>>> can you make a proposal of changes, or write few lines on what you was
>>>> thinking of?
>>>>
>>>> Cheers
>>>>
>>>>
>>>>
>>>> Il lun 1 ago 2016, 15:17 Fabio Erculiani 
>>>> ha scritto:
>>>>
>>>>> First of all,
>>>>> I think I fixed all outstanding anaconda issues (including the grub
>>>>> splash) and I am pushing anaconda-22.5 right now.
>>>>>
>>>>> But I still see at least a couple of major issues with the images I
>>>>> tested (GNOME and KDE):
>>>>> - GNOME desktop icons are incorrectly positioned, they are one above
>>>>> the other.
>>>>> - KDE LightDM integration (after install) seems broken, X starts at a
>>>>> very low resolution and there is no background (the background is white).
>>>>>
>>>>> I think we should fix at least these two things before cutting a new
>>>>> release.
>>>>>
>>>>>
>>>>> --
>>>>>  Fabio Erculiani
>>>>>
>>>> --
>>>>
>>>> Regards,
>>>> Ettore Di Giacinto - Sabayon Project Lead
>>>>
>>>> --
>>>
>>> Regards,
>>> Ettore Di Giacinto - Sabayon Project Lead
>>>
>>>
>>>
>>>
>>>
>>
>> --
>
> Regards,
> Ettore Di Giacinto - Sabayon Project Lead
>
>
>
>
>

Re: [sabayon-dev] Some release blockers

[Joost Ruis]

Just tested MATE daily dev that was build today and it seems that
everything works just fine. (Even Grub theme got installed).
I'll try to find some time to test KDE spin

On Mon, Aug 1, 2016 at 4:26 PM, Ettore Di Giacinto 
wrote:

> About cycle release, soon i'll open up another thread wrt cycle release
> scheduling. Then main idea is to cut a stable release every 4 months.
>
> Il lun 1 ago 2016, 15:29 Ettore Di Giacinto  ha
> scritto:
>
>> Indeed i blocked crons and holded monthly automatic releases, i think
>> thats also the occasion to switch to a "less often" release cycle for
>> monthly and cutting stable releases instead of automatic ones.
>>
>> Dailies will still be there of course, giving us the ability to test
>> better and having a good release everytime.
>>
>> KDE bug showed up since the plasma 5.6.7 bump, i suggest to give sddm
>> another shot now thlhat we have the occasion (we decided to not use it
>> because was having major issues with ati video cards).
>>
>> For GNOME, Francesco was taking care of it, but he was proposing to
>> remove icons at all and adding a welcome screen (like fedora/ubuntu and so
>> on) which is more user friendly than the current boot process. Francesco,
>> can you make a proposal of changes, or write few lines on what you was
>> thinking of?
>>
>> Cheers
>>
>>
>>
>> Il lun 1 ago 2016, 15:17 Fabio Erculiani  ha
>> scritto:
>>
>>> First of all,
>>> I think I fixed all outstanding anaconda issues (including the grub
>>> splash) and I am pushing anaconda-22.5 right now.
>>>
>>> But I still see at least a couple of major issues with the images I
>>> tested (GNOME and KDE):
>>> - GNOME desktop icons are incorrectly positioned, they are one above the
>>> other.
>>> - KDE LightDM integration (after install) seems broken, X starts at a
>>> very low resolution and there is no background (the background is white).
>>>
>>> I think we should fix at least these two things before cutting a new
>>> release.
>>>
>>>
>>> --
>>>  Fabio Erculiani
>>>
>> --
>>
>> Regards,
>> Ettore Di Giacinto - Sabayon Project Lead
>>
>> --
>
> Regards,
> Ettore Di Giacinto - Sabayon Project Lead
>
>
>
>
>

[sabayon-dev] Test

[Joost Ruis]

Test!

Re: [sabayon-dev] ISO DAILY 20160430 :Ati-drivers missing

[Joost Ruis]

We stopped shipping them ages ago.

On Mon, May 2, 2016 at 1:38 AM, sabayonino  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi guys , browsing through DAILY ISOs pkglist
> (http://na.mirror.garr.it/mirrors/sabayonlinux/iso/daily/daily.html)
> I noticed that ATI proprietary drivers package is missing
>
> I've checked Xfce ISO and confirm this . ATI-drivers package is missing.
> (I think it is missed for other ISOs also)
>
> Sabayon Xfce-Daily 20160430 running on VirtualBox :
>
> $ equo q installed ati-drivers
> ╠  @@ Cercando...
> ╠   Keyword:  ati-drivers
> ╠   Trovati:  0 voci
>
> Nvidia-drivers is installed.
> $ equo q installed nvidia-drivers -qv
> x11-drivers/nvidia-drivers-358.09#4.5.0-sabayon
>
>
> :) Cheers.
>
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJXJpNtAAoJEPbN17Ml/UPmSj4P/3lnzReuAE58O+e7n36Btc7A
> 7o7NwTWduwNM0ztbvm+KfdRbb9BigLSl1sOXEoljIJCQ8Cs30q0IgBUCMTVyI4Dk
> hq0iEIhFM6YWcv8XwADALdqW2TJZgX0KcagTmzvjEVhZhHZcfiGRpS7J+JT9a3a4
> k6lyrKi+Lpn6UOjol2Ep9IkHU1OJRLus7ZEppJ7Gkb7dAKVoWxyX7gEM/ZrA/8no
> D+cRBsT91jxWDoMDerGMwnnDmg6ZvI4ON21+bOw5F6lUa1gVlR6FsCXBaxzwQIGZ
> qaZxoAy1k5uUoIc5YlTV/kpxUgnfOmfpFc45Cnut8lJ7E9lc15gUsarMrfgF/pku
> VgsfLFvmfCdRXDBCe7Y26658C7P3bmKEqc7KUMw8inpmbeTWk6JxM6DG5n7GM4Qn
> d8UyIp1BX666qAhWP06uixPHW+z8z+RCLFxEzK0FYxpH89HDPBq32woRj6ikKZxY
> hlAAN4AG9aZadr4lWlq1b7LwjtRz2RX9k/8tErw+X7ZtfykD18tbD9ByKa6aLPex
> 1keDkgCJ4CYE4Pwdqu/ulZ4gPXv6oCAjzQHbLg78hGrVzNbsrqxXWPy3y3fqKHMH
> xB+/CfkDDyvkFMp1srGQnv3eDfwUElzh7dF0LavowUnbA0BhnETq77PEHdK9E+5B
> vrq7q705HRFeSDAO8vbv
> =+Th0
> -END PGP SIGNATURE-
>
>

Re: [sabayon-dev] Bots - IRC

[Joost Ruis]

I won't miss them.
Op 29 feb. 2016 19:01 schreef "Drew Kelling" :

> Agreed! There is a lot of noise in #sabayon-dev these days.
>
> On Sat, Feb 27, 2016 at 1:05 PM, Wolfden  wrote:
>
>> I would like to see a change with #sabayon-dev and it's bots.  The bots
>> are great and all, but it's too much.  It makes it difficult to scroll back
>> and follow along in conversation.  I would much prefer have the dev channel
>> for humans to discuss.  How about another channel for the bots?
>>  #sabayon-activity or something.
>>
>> --
>> KJS
>> ~wolfden~
>>
>>
>>
>>
>
>
>
>

Re: [sabayon-dev] Suggestion : systemd log size and cleanup

[Joost Ruis]

If we change this it needs to get documented.Somebody make a pull request
for this at molecules.git so we can review and implement.

On Thu, Feb 18, 2016 at 12:55 PM, Wolfden  wrote:

> Well, like myself, I was totally unaware of this as systemd is new to me
> and so I assume there are many many other peeps out there that don't know
> this either.  It could save a headache for someone down the road.
>
> On Thu, Feb 18, 2016 at 5:51 AM, Joost Ruis 
> wrote:
>
>> We could change the config for our images using molecule. I'm fine with
>> that. Just as long we keep the package (systemd and the config it ships)
>> itself vanilla.
>>
>> /me puts on his party hat.
>>
>> On Thu, Feb 18, 2016 at 12:45 PM, Wolfden  wrote:
>>
>>> party pooper
>>>
>>> On Thu, Feb 18, 2016 at 5:42 AM, Joost Ruis 
>>> wrote:
>>>
>>>> I'd leave it for users to decide.
>>>>
>>>> On Thu, Feb 18, 2016 at 12:41 PM, Wolfden  wrote:
>>>>
>>>>> I think this is a great idea
>>>>>
>>>>> fresh install not to old here
>>>>> spongebob # journalctl --disk-usage
>>>>> Archived and active journals take up 400.0M on disk.
>>>>>
>>>>>
>>>>> On Wed, Feb 17, 2016 at 3:11 PM, sabayonino 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> -BEGIN PGP SIGNED MESSAGE-
>>>>>> Hash: SHA256
>>>>>>
>>>>>> Hi folks :D
>>>>>>
>>>>>> recently I've cleaup over 6Gb of systemd logs  (!!!)
>>>>>>
>>>>>> journalctl --vacuum-time=4weeks
>>>>>>
>>>>>>
>>>>>> /etc/systemd/journald.conf
>>>>>>
>>>>>> this parameter is empty
>>>>>> #SystemMaxUse=
>>>>>> I think 1G or 500M , (depends from root size)  is pretty good
>>>>>>
>>>>>> I suggest to set this variable in our ISOs to prevent fill root
>>>>>> partition over time. A newby can't check this
>>>>>>
>>>>>> If you cant touch journald config , can you add a logrotate rule or
>>>>>> something else to do this.
>>>>>>
>>>>>> Tnx for your attentions :)
>>>>>>
>>>>>> regards
>>>>>>
>>>>>>
>>>>>> -BEGIN PGP SIGNATURE-
>>>>>> Version: GnuPG v2
>>>>>>
>>>>>> iQEcBAEBCAAGBQJWxOH3AAoJEFfOIdEFlHaQa3gH/jF/38MvaV8nti6ugPh6JlUP
>>>>>> e4bz5l6QJVwSNs2oW8lmDHf4VrV6JKM0f9TDpLyaDON9O28yLrqoWW0l0qyi1cz4
>>>>>> JA57GlxXQUTP6ZhReAC5h7bLrJfyqopVAGusLbW3500Iqwp7SNJDnBMgJp06cYXf
>>>>>> gCA0vrOWMUazveHvIq/HAG2S7HaMRACc7GchS3dZCiXhh8aM6YTSzH+sAGSBR3ey
>>>>>> C/gJek92zcXbCslI5T+IVovLIuNISR+NJDH9C6g9nuRJ5vPbAUox2VhcRnxP3TxX
>>>>>> 0cjiX5QwCK/RC6rWBQR3j+DKo0vbBJbbrx5o1elWLUqR/pHGUNtHZb2QruguYPk=
>>>>>> =FCAG
>>>>>> -END PGP SIGNATURE-
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> KJS
>>>>> ~wolfden~
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> KJS
>>> ~wolfden~
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
> --
> KJS
> ~wolfden~
>
>
>
>

Re: [sabayon-dev] Suggestion : systemd log size and cleanup

[Joost Ruis]

We could change the config for our images using molecule. I'm fine with
that. Just as long we keep the package (systemd and the config it ships)
itself vanilla.

/me puts on his party hat.

On Thu, Feb 18, 2016 at 12:45 PM, Wolfden  wrote:

> party pooper
>
> On Thu, Feb 18, 2016 at 5:42 AM, Joost Ruis 
> wrote:
>
>> I'd leave it for users to decide.
>>
>> On Thu, Feb 18, 2016 at 12:41 PM, Wolfden  wrote:
>>
>>> I think this is a great idea
>>>
>>> fresh install not to old here
>>> spongebob # journalctl --disk-usage
>>> Archived and active journals take up 400.0M on disk.
>>>
>>>
>>> On Wed, Feb 17, 2016 at 3:11 PM, sabayonino 
>>> wrote:
>>>
>>>>
>>>> -BEGIN PGP SIGNED MESSAGE-
>>>> Hash: SHA256
>>>>
>>>> Hi folks :D
>>>>
>>>> recently I've cleaup over 6Gb of systemd logs  (!!!)
>>>>
>>>> journalctl --vacuum-time=4weeks
>>>>
>>>>
>>>> /etc/systemd/journald.conf
>>>>
>>>> this parameter is empty
>>>> #SystemMaxUse=
>>>> I think 1G or 500M , (depends from root size)  is pretty good
>>>>
>>>> I suggest to set this variable in our ISOs to prevent fill root
>>>> partition over time. A newby can't check this
>>>>
>>>> If you cant touch journald config , can you add a logrotate rule or
>>>> something else to do this.
>>>>
>>>> Tnx for your attentions :)
>>>>
>>>> regards
>>>>
>>>>
>>>> -BEGIN PGP SIGNATURE-
>>>> Version: GnuPG v2
>>>>
>>>> iQEcBAEBCAAGBQJWxOH3AAoJEFfOIdEFlHaQa3gH/jF/38MvaV8nti6ugPh6JlUP
>>>> e4bz5l6QJVwSNs2oW8lmDHf4VrV6JKM0f9TDpLyaDON9O28yLrqoWW0l0qyi1cz4
>>>> JA57GlxXQUTP6ZhReAC5h7bLrJfyqopVAGusLbW3500Iqwp7SNJDnBMgJp06cYXf
>>>> gCA0vrOWMUazveHvIq/HAG2S7HaMRACc7GchS3dZCiXhh8aM6YTSzH+sAGSBR3ey
>>>> C/gJek92zcXbCslI5T+IVovLIuNISR+NJDH9C6g9nuRJ5vPbAUox2VhcRnxP3TxX
>>>> 0cjiX5QwCK/RC6rWBQR3j+DKo0vbBJbbrx5o1elWLUqR/pHGUNtHZb2QruguYPk=
>>>> =FCAG
>>>> -END PGP SIGNATURE-
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> KJS
>>> ~wolfden~
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
> --
> KJS
> ~wolfden~
>
>
>
>

Re: [sabayon-dev] Suggestion : systemd log size and cleanup

[Joost Ruis]

I'd leave it for users to decide.

On Thu, Feb 18, 2016 at 12:41 PM, Wolfden  wrote:

> I think this is a great idea
>
> fresh install not to old here
> spongebob # journalctl --disk-usage
> Archived and active journals take up 400.0M on disk.
>
>
> On Wed, Feb 17, 2016 at 3:11 PM, sabayonino  wrote:
>
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi folks :D
>>
>> recently I've cleaup over 6Gb of systemd logs  (!!!)
>>
>> journalctl --vacuum-time=4weeks
>>
>>
>> /etc/systemd/journald.conf
>>
>> this parameter is empty
>> #SystemMaxUse=
>> I think 1G or 500M , (depends from root size)  is pretty good
>>
>> I suggest to set this variable in our ISOs to prevent fill root
>> partition over time. A newby can't check this
>>
>> If you cant touch journald config , can you add a logrotate rule or
>> something else to do this.
>>
>> Tnx for your attentions :)
>>
>> regards
>>
>>
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2
>>
>> iQEcBAEBCAAGBQJWxOH3AAoJEFfOIdEFlHaQa3gH/jF/38MvaV8nti6ugPh6JlUP
>> e4bz5l6QJVwSNs2oW8lmDHf4VrV6JKM0f9TDpLyaDON9O28yLrqoWW0l0qyi1cz4
>> JA57GlxXQUTP6ZhReAC5h7bLrJfyqopVAGusLbW3500Iqwp7SNJDnBMgJp06cYXf
>> gCA0vrOWMUazveHvIq/HAG2S7HaMRACc7GchS3dZCiXhh8aM6YTSzH+sAGSBR3ey
>> C/gJek92zcXbCslI5T+IVovLIuNISR+NJDH9C6g9nuRJ5vPbAUox2VhcRnxP3TxX
>> 0cjiX5QwCK/RC6rWBQR3j+DKo0vbBJbbrx5o1elWLUqR/pHGUNtHZb2QruguYPk=
>> =FCAG
>> -END PGP SIGNATURE-
>>
>>
>>
>>
>
>
> --
> KJS
> ~wolfden~
>
>
>
>

Re: [sabayon-dev] Suggestions for sabayon-server release (and sabayon desktop)

[Joost Ruis]

1, 2 and 4 are done.

On Sat, Oct 24, 2015 at 6:34 PM, Ettore Di Giacinto  wrote:

> Hi Geaaru,
>
> First, thank you for the suggestions,
>
> answering in order:
>
> 1) noted, soon will hit entropy
>
> 2) done
> https://github.com/Sabayon/build/commit/f37805526ef0d7cbfacc7764a7ee8b5e3e826ca2
>  ,
> in Entropy soon
>
> 3) the eselect would be a great approach, feel free to do it and open a
> pull request, i'll be happy to review it. Have you tried to blacklist the
> module? zfs is actually handy, dunno if worth deleting the file from the
> packages, this usually means that we must handle then both packages
> manually (in reality, we are already doing that for zfs, but not for xen).
> I try to avoid forks, just when strictly necessary (because requires more
> maintenance)
>
> 4)
> https://github.com/Sabayon/build/commit/1f40f115dde095d97fd38dc1ceec9d4276485a9b
>  ,
> in Entropy soon
>
> 4-bis?) Never experienced that, file a bug with logs /steps to reproduce
>
> 5) noted, but since is not a priority, you could speed up things opening a
> pull request for it
>
> 6) Fabio takes care of the Sabayon kernel, IMO those options sounds good
> to me.
>
> Cheers,
> Ettore
>
>
>
>
> Il giorno ven 23 ott 2015 alle ore 10:49 Geaaru  ha
> scritto:
>
>> Hi guys,
>>
>> hereinafter some useful packages and/or use flag to apply on sabayon
>> server release and on sabayon desktop release for improve :
>>
>> 1) currently sabayon release doesn't provide package about mariadb
>> -galera (an enhancement of mariadb database with support to galera
>> plugin that permit manage of cluster of database with innodb engine). I
>> think that currently mariadb-galera is the best cluster solution for
>> Mysql database and it is an error doesn't provide package about this on
>> sabayon repository above all on sabayon server release.
>>
>> 2) Module app-emulation/qemu doesn't include these use flags:
>>
>> +glusterfs (for add support on directly use glusterfs library for integ
>> ration to glusterfs filesystem. Else it use fuse feature with bad
>> performance)
>>
>> +nfs (add NFS support)
>>
>> +rbd (add support to ceph block filesystem)
>>
>> On openstack platform currenctly I use qemu with gluster and nfs.
>>
>> 3) on sabayon release automatically zfs module is installed inside
>>  /usr/lib/modules-load.d/zfs.conf. I think that this is not useful on
>> sabayon-desktop where often zfs filesystem is not used and also inside
>> sabayon vm. Also, I think that could be correct avoid install of
>> zfs.conf file inside /usr/lib/modules-load/ directory on every upgrade
>> of the syste. Every time I upgrade sabayon vm I need remember to remove
>> or rename zfs.conf to avoid load of zfs kernel module. Same thing for
>> xen modules.
>> Best solution is handle these files under modules-load.d directory
>> through eselect but this require a develop of eselect extension and
>> related ebuild. As first solution could be fine remove automatic
>> install of zfs.conf file.
>>
>> 4) Module app-emulation/libvirt doesn't include these use flags:
>> +glusterfs (support of gluster filesystem)
>>
>> +lxc (support to linux container)
>>
>> +rbd (support to ceph block filesystem)
>>
>> +virtualbox (support to virtualbox)
>>
>> +fuse (support to fuse... this with less priority)
>>
>> I use these flags with openstack platform and on sabayon-server release
>> colud
>>
>> 4) Avoid automatic activation of cronyd daemon. On my sabayon vm I
>> configured systemd-timesyncd or ntpd daemon for time sync but on
>> upgrade vm I see that cronyd is been automatically activated as a
>> service. This avoid then that previous configuration of systemd
>> -timesyncd and ntpd works correctly. Do you think that is correct
>> activate automatically this service on upgrade of the system ?
>>
>> 5) Journald configuration: Default installation of systemd (from gentoo
>> portage) doesn't provide any smart configuration of systemd-journald
>> service because doesn't configure systemd-journald to handle log rotate
>> or something like this. So, if a user doesn't reconfigure this file
>> after some days will optain a disk full. This, is a problem on ebuild
>> but fwik systemd ebuild is been overwrite from sabayon release, so
>> could be fine correct this file at least
>>
>> 6) I could be fine add kernel options:
>> - ipset modules (I currently use ipset with iptables)
>> - nfsv4.1 support
>> - enable CONFIG_NET_CLS_CGROUP
>>
>> For now it is all.
>> Thanks
>>
>> My cent.
>>
>> G.
>>
>>
>>
>
>
>

Re: [sabayon-dev] Missing touchpad useflag in plasma-desktop 5.4.1/5.4.2

[Joost Ruis]

Updated package is in Entropy.

On Tue, Oct 13, 2015 at 7:34 PM, Ettore Di Giacinto  wrote:

> useflag added:
> https://github.com/Sabayon/build/commit/3330489f895b34a93dedb392a92a78b117065c30
>
> Thank you for reporting!
>
>
> Il giorno mar 13 ott 2015 alle ore 13:53 sabayonino 
> ha scritto:
>
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi guys :)
>>
>> Installed latest daily_KDE on my two laptops
>>
>> I can't manage touchpads (synaptics/Elentech) 'cause "touchpad" useflag
>> is disabled in
>>
>> kde-plasma/plasma-desktop-5.4.1
>> 
>> 
>> and
>> kde-plasma/plasma-desktop-5.4.2
>> 
>> 
>>
>>
>> My Gentoo system works fine and touchpad module is in
>> systemsettings/input-device
>>
>> Regards :)
>>
>>
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2
>>
>> iQEcBAEBCAAGBQJWHPCZAAoJEFfOIdEFlHaQMrgH/ifjjpHmzvilPgi5FDfb/mH1
>> qLrWHuU640cNLD+c7DarFwkkENnIDIhPC03iGxAZkrjx2dbUp0nooDT+q4ZfOiGm
>> IyK8/Aw7/hJVy6BzLWEuHBszyrW43fDZBGzNBhyUJyJNfoe0ciSZxAX+dcKSeVum
>> 6aLqxQF5ItPngpUhGGwfPraVfG/jnyIFPIX0ZL+0VimXNHLdpxgtSZYj7Pj1v64i
>> n+g3zKPzdfA9HIvPiacCXXvl47u3Fl/iaUvYHsRBzHsF//Q3KHAEGqfRSeosMdTs
>> RbR65xE68VNw0CoWtBcY/BcIzsGamnQER4BxWUXHrQ/3t8u4SCbkx0IyfeOfhJI=
>> =xm+b
>> -END PGP SIGNATURE-
>>
>>
>>
>
>
>

Re: [sabayon-dev] rigo - not authorized

[Joost Ruis]

The problem might have been caused by Calamares not adding user to Entropy
group. This problem afaik only affected daily dev images. It should be
fixed on the next generated images.
Op 4 aug. 2015 23:04 schreef "Sławomir Nizio" :

> > hmmm, been seeing it on the forum also, I haven't tried it myself yet.
> > I don't use rigo much
>
> Okay, so something is there indeed.
>
> (I'll probably be able to take a look only next week unless someone
> beats me to it…)
>
> In case of problems one can always use equo at least for now.
>
>
>

Re: [sabayon-dev] KDE Plasma5 community repository

[Joost Ruis]

On my system all those packages actually were installed and they are part
of the meta as well.

http://gpo.zugaina.org/kde-plasma/plasma-meta/Dep#ptabs

On Sun, Jul 12, 2015 at 9:22 PM, Stuart Rose 
wrote:

> Ok, here's been my experience thus far.
>
> Installing plasma-meta didn't pull in plasma-desktop, kwin, or
> plasma-workspace packages so I didn't get a working DE just from that.
> Installing plasma-desktop pulled the other 2 in and I could get it.  I had
> already switched to sddm (it was pulled in via plasma-meta), so I can't say
> how well kdm does or doesn't work.
>
> These are the other packages kde related that I noticed weren't install
> via plasma-meta:
> kde-plasma/systemsettings-5.3.2
> kde-plasma/powerdevil-5.3.2
> kde-plasma/kmenuedit-5.3.2
> kde-plasma/kinfocenter-5.3.2
> kde-plasma/khotkeys-5.3.2
>
> all of which I'd consider to be important enough to be a part of the meta
> package, especially considering systemsettings is a shortcut in the menu,
> which lead me to think it was there already.
>
> Other than that, I've had noticed no other issues.
>
> For reference, my PC has an older nvidia card (GTX 250 or something)
> running nvidia 240 drivers, dual monitors.
>
>
>
> On Sat, Jul 11, 2015 at 10:00 AM, Stuart Rose 
> wrote:
>
>> Ahh, I realize that everything will be lost.  I meant more from a
>> technical point of view, seeing entropy remove and replace what it should.
>> For instance, it's my understanding that KDM isn't up to the task and SDDM
>> is the preferred DM for Plasma 5.  I'm also aware that some apps are still
>> the KDE4 version in the plasma 5 environment.  So I'm just curious as to
>> what sort of bumps I might run into.
>>
>> Don't you worry, I am assuredly prepared for the possibility of this
>> going quite badly and I've a good idea of what to expect if it all goes
>> well.
>>
>> I'll try and drop into IRC, as opposed to spamming this mailing list for
>> things I come across, although I have bad luck catching anyone active when
>> I do go.
>>
>> -stupot
>>
>> On Sat, Jul 11, 2015 at 9:53 AM, Joost Ruis 
>> wrote:
>>
>>> Don't see it as an "upgrade" it wasn't designed like that. You in fact
>>> "trade in" KDE4 for PLASMA 5 loosing all your customization. This was a
>>> choice made by KDE.
>>>
>>> On Sat, Jul 11, 2015 at 4:46 PM, Stuart Rose 
>>> wrote:
>>>
>>>> Thanks, that's kind of what I figured.
>>>>
>>>> I'll give it a whirl on my desktop this weekend, upgrading from KDE4
>>>> and I'll report any issues I run into along the way.
>>>>
>>>> On Sat, Jul 11, 2015 at 9:45 AM, Joost Ruis 
>>>> wrote:
>>>>
>>>>> It is there for testing purpose. Since we can't simply add it to our
>>>>> official build chroot without removing KDE4. Best way to test for now is
>>>>> using an external repository.
>>>>>
>>>>> On Sat, Jul 11, 2015 at 4:41 PM, Stuart Rose >>>> > wrote:
>>>>>
>>>>>> Is this set up with the plan to test it here and eventually move it
>>>>>> into limbo/mainline?
>>>>>>
>>>>>> Or did you just want plasma 5 and didn't feel like waiting?  I must
>>>>>> admit, I just installed Arch on a laptop because we didn't have plasma 5
>>>>>> yet and I wanted it for better hiDPI support.
>>>>>>
>>>>>> On Sat, Jul 11, 2015 at 9:38 AM, mud...@sabayonlinux.org <
>>>>>> mud...@sabayonlinux.org> wrote:
>>>>>>
>>>>>>>  I just set up a repo with Plasma 5, if someone feels so brave to
>>>>>>> test, read on:
>>>>>>>
>>>>>>>
>>>>>>> Add in /etc/entropy/repositories.conf.d
>>>>>>>
>>>>>>> the file entropy_plasma5 with the following content:
>>>>>>>
>>>>>>> [plasma5]
>>>>>>> desc = Plasma5 Sabayon repository
>>>>>>> repo=https://mirror.spike-pentesting.org/mirrors/spike/plasma5#bz2
>>>>>>> enabled = true
>>>>>>> pkg = https://mirror.spike-pentesting.org/mirrors/spike/plasma5
>>>>>>>
>>>>>>> Then as usual do an equo up and install the metapackage (equo i
>>>>>>> kde-plasma/plasma-meta).
>>>>>>>
>>>>>>> For network manager you have to install plasma-nm, for having all
>>>>>>> systray working correctly you need also dev-libs/sni-qt (available in
>>>>>>> sabayon-limbo now).
>>>>>>>
>>>>>>> Please keep in mind this is still in testing, for any reference:
>>>>>>> https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade#Missing_systray_icons
>>>>>>> and https://wiki.gentoo.org/wiki/Project:KDE/Frameworks
>>>>>>>
>>>>>>> Cheers
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>
>
>
>

Re: [sabayon-dev] KDE Plasma5 community repository

[Joost Ruis]

Don't see it as an "upgrade" it wasn't designed like that. You in fact
"trade in" KDE4 for PLASMA 5 loosing all your customization. This was a
choice made by KDE.

On Sat, Jul 11, 2015 at 4:46 PM, Stuart Rose 
wrote:

> Thanks, that's kind of what I figured.
>
> I'll give it a whirl on my desktop this weekend, upgrading from KDE4 and
> I'll report any issues I run into along the way.
>
> On Sat, Jul 11, 2015 at 9:45 AM, Joost Ruis 
> wrote:
>
>> It is there for testing purpose. Since we can't simply add it to our
>> official build chroot without removing KDE4. Best way to test for now is
>> using an external repository.
>>
>> On Sat, Jul 11, 2015 at 4:41 PM, Stuart Rose 
>> wrote:
>>
>>> Is this set up with the plan to test it here and eventually move it into
>>> limbo/mainline?
>>>
>>> Or did you just want plasma 5 and didn't feel like waiting?  I must
>>> admit, I just installed Arch on a laptop because we didn't have plasma 5
>>> yet and I wanted it for better hiDPI support.
>>>
>>> On Sat, Jul 11, 2015 at 9:38 AM, mud...@sabayonlinux.org <
>>> mud...@sabayonlinux.org> wrote:
>>>
>>>>  I just set up a repo with Plasma 5, if someone feels so brave to test,
>>>> read on:
>>>>
>>>>
>>>> Add in /etc/entropy/repositories.conf.d
>>>>
>>>> the file entropy_plasma5 with the following content:
>>>>
>>>> [plasma5]
>>>> desc = Plasma5 Sabayon repository
>>>> repo=https://mirror.spike-pentesting.org/mirrors/spike/plasma5#bz2
>>>> enabled = true
>>>> pkg = https://mirror.spike-pentesting.org/mirrors/spike/plasma5
>>>>
>>>> Then as usual do an equo up and install the metapackage (equo i
>>>> kde-plasma/plasma-meta).
>>>>
>>>> For network manager you have to install plasma-nm, for having all
>>>> systray working correctly you need also dev-libs/sni-qt (available in
>>>> sabayon-limbo now).
>>>>
>>>> Please keep in mind this is still in testing, for any reference:
>>>> https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade#Missing_systray_icons
>>>> and https://wiki.gentoo.org/wiki/Project:KDE/Frameworks
>>>>
>>>> Cheers
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>

Re: [sabayon-dev] KDE Plasma5 community repository

[Joost Ruis]

It is there for testing purpose. Since we can't simply add it to our
official build chroot without removing KDE4. Best way to test for now is
using an external repository.

On Sat, Jul 11, 2015 at 4:41 PM, Stuart Rose 
wrote:

> Is this set up with the plan to test it here and eventually move it into
> limbo/mainline?
>
> Or did you just want plasma 5 and didn't feel like waiting?  I must admit,
> I just installed Arch on a laptop because we didn't have plasma 5 yet and I
> wanted it for better hiDPI support.
>
> On Sat, Jul 11, 2015 at 9:38 AM, mud...@sabayonlinux.org <
> mud...@sabayonlinux.org> wrote:
>
>>  I just set up a repo with Plasma 5, if someone feels so brave to test,
>> read on:
>>
>>
>> Add in /etc/entropy/repositories.conf.d
>>
>> the file entropy_plasma5 with the following content:
>>
>> [plasma5]
>> desc = Plasma5 Sabayon repository
>> repo=https://mirror.spike-pentesting.org/mirrors/spike/plasma5#bz2
>> enabled = true
>> pkg = https://mirror.spike-pentesting.org/mirrors/spike/plasma5
>>
>> Then as usual do an equo up and install the metapackage (equo i
>> kde-plasma/plasma-meta).
>>
>> For network manager you have to install plasma-nm, for having all systray
>> working correctly you need also dev-libs/sni-qt (available in sabayon-limbo
>> now).
>>
>> Please keep in mind this is still in testing, for any reference:
>> https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade#Missing_systray_icons
>> and https://wiki.gentoo.org/wiki/Project:KDE/Frameworks
>>
>> Cheers
>>
>>
>>
>>
>
>
>
>

Re: [sabayon-dev] July 6th ISO test of MATE

[Joost Ruis]

https://github.com/Sabayon/molecules/commit/4249704767481186fbc0ac96c0b5959235a07ae9


On Wed, Jul 8, 2015 at 10:50 AM, mud...@sabayonlinux.org <
mud...@sabayonlinux.org> wrote:

>  Fixing that in the docker stage right now
>
>
>
> Il 08/07/2015 10:27, Joost Ruis ha scritto:
>
> "---  No desktop icon for the Installer but is located in system tools menu
> as calamares, which a lot of people are not going to know what that is.  I
> didn't try an install with the new installer, but it launch right up upon
> clicking on it."
>
> This is resolved in -dev builds > 7th july
>
> The bluetooth thingy, seems a simple fix I'll look into that.
>
> @Mudler We might need to fix the missing virtuals thing at the docker stage?
>
> On Wed, Jul 8, 2015 at 10:04 AM, Wolfden  
>  wrote:
>
>
>  Trying out the Mate ISO and some quick findings
>
> ---  No desktop icon for the Installer but is located in system tools menu
> as calamares, which a lot of people are not going to know what that is.  I
> didn't try an install with the new installer, but it launch right up upon
> clicking on it.
>
> --- journalctl -b -p err results in - Jul 10 07:31:31 sabayon
> pulseaudio[2078]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
> org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service fail
>
> ​^^ solution: ​systemctl enable bluetooth
> ​
> --- an immediate deptest provides:
>
>   sabayon sabayonuser # equo deptest --ask
>
> ☛
>
> ☛ Entropy is running off a Live System
>
> ☛ Performance and stability could get severely compromised
>
> ☛
>
> ╠  @@ Running dependency test...
>
> ╠  @@ These are the dependencies not found:
>
> ╠# ~dev-perl/Module-Build-0.400.300
>
> ╠   # Needed by:
>
> ╠   # virtual/perl-Module-Build-0.400.300
>
> Would you like to install the packages ? [Yes/No] No
>
> sabayon sabayonuser # equo install dev-perl/Module-Build
>
> ☛
>
> ☛ Entropy is running off a Live System
>
> ☛ Performance and stability could get severely compromised
>
> ☛
>
> ╠  @@ Calculating dependencies...
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Perl-OSType-1.7.0|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Test-Harness-3.330.0|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-ParseXS-3.240.0|0
>
> ╠  ## [N] [sabayonlinux.org]
> virtual/perl-ExtUtils-CBuilder-0.280.217-r2|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-JSON-PP-2.272.30|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-CPAN-Meta-YAML-0.12.0-r1|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-Command-1.180.0-r2|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-Install-1.670.0|0
>
> ╠  ## [N] [sabayonlinux.org] perl-core/ExtUtils-Manifest-1.700.0|2
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-Manifest-1.700.0-r1|0
>
> ╠  ## [N] [sabayonlinux.org] perl-core/ExtUtils-MakeMaker-7.40.0-r1|2
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Parse-CPAN-Meta-1.441.400-r1|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-version-0.990.900-r2|0
>
> ╠  ## [N] [sabayonlinux.org]
> virtual/perl-CPAN-Meta-Requirements-2.125.0-r1|0
>
> ╠  ## [N] [sabayonlinux.org] perl-core/CPAN-Meta-2.143.240|2
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-CPAN-Meta-2.143.240|1
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Module-Metadata-1.0.19|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Text-ParseWords-3.290.0-r1|3
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-MakeMaker-7.40.0|1
>
> ╠  ## [N] [sabayonlinux.org] dev-perl/Module-Build-0.421.400|0
>
> ╠  @@ Packages needing to be installed/updated/downgraded: 20
>
> ╠  @@ Packages needing to be removed: 0
>
> ╠  @@ Download size: 692.2kB
>
> ╠  @@ Used disk space: 1.3MB
>
> ╠  @@ You need at least: 2.6MB of free space
>
> ╠  @@ You need to accept the licenses below:
>
> ╠ :: License: GPL-1+, needed by:
>
> ╠  # [from:sabayonlinux.org] perl-core/CPAN-Meta-2.143.240
>
> ╠  # [from:sabayonlinux.org] dev-perl/Module-Build-0.421.400
>
> ╠  # [from:sabayonlinux.org] perl-core/ExtUtils-MakeMaker-7.40.0-r1
>
> ╠  # [from:sabayonlinux.org] perl-core/ExtUtils-Manifest-1.700.0
>
> ╠ Please select an option
>
> ╠   (1) Read the license
>
> ╠   (2) Accept the license (I've read it)
>
> ╠   (3) Accept the license and don't ask anymore (I've read it)
>
> ╠   (0) Quit
>
>Your choice (type a number and press enter):​
>
> ​Might have to add package to molecule build list​
>
>
> --
> KJS
> ~wolfden~
>
>
>
>
>
>
>
>
>
>
>
>

Re: [sabayon-dev] July 6th ISO test of MATE

[Joost Ruis]

"---  No desktop icon for the Installer but is located in system tools menu
as calamares, which a lot of people are not going to know what that is.  I
didn't try an install with the new installer, but it launch right up upon
clicking on it."

This is resolved in -dev builds > 7th july

The bluetooth thingy, seems a simple fix I'll look into that.

@Mudler We might need to fix the missing virtuals thing at the docker stage?

On Wed, Jul 8, 2015 at 10:04 AM, Wolfden  wrote:

> Trying out the Mate ISO and some quick findings
>
> ---  No desktop icon for the Installer but is located in system tools menu
> as calamares, which a lot of people are not going to know what that is.  I
> didn't try an install with the new installer, but it launch right up upon
> clicking on it.
>
> --- journalctl -b -p err results in - Jul 10 07:31:31 sabayon
> pulseaudio[2078]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
> org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service fail
>
> ​^^ solution: ​systemctl enable bluetooth
> ​
> --- an immediate deptest provides:
>
>   sabayon sabayonuser # equo deptest --ask
>
> ☛
>
> ☛ Entropy is running off a Live System
>
> ☛ Performance and stability could get severely compromised
>
> ☛
>
> ╠  @@ Running dependency test...
>
> ╠  @@ These are the dependencies not found:
>
> ╠# ~dev-perl/Module-Build-0.400.300
>
> ╠   # Needed by:
>
> ╠   # virtual/perl-Module-Build-0.400.300
>
> Would you like to install the packages ? [Yes/No] No
>
> sabayon sabayonuser # equo install dev-perl/Module-Build
>
> ☛
>
> ☛ Entropy is running off a Live System
>
> ☛ Performance and stability could get severely compromised
>
> ☛
>
> ╠  @@ Calculating dependencies...
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Perl-OSType-1.7.0|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Test-Harness-3.330.0|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-ParseXS-3.240.0|0
>
> ╠  ## [N] [sabayonlinux.org]
> virtual/perl-ExtUtils-CBuilder-0.280.217-r2|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-JSON-PP-2.272.30|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-CPAN-Meta-YAML-0.12.0-r1|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-Command-1.180.0-r2|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-Install-1.670.0|0
>
> ╠  ## [N] [sabayonlinux.org] perl-core/ExtUtils-Manifest-1.700.0|2
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-Manifest-1.700.0-r1|0
>
> ╠  ## [N] [sabayonlinux.org] perl-core/ExtUtils-MakeMaker-7.40.0-r1|2
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Parse-CPAN-Meta-1.441.400-r1|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-version-0.990.900-r2|0
>
> ╠  ## [N] [sabayonlinux.org]
> virtual/perl-CPAN-Meta-Requirements-2.125.0-r1|0
>
> ╠  ## [N] [sabayonlinux.org] perl-core/CPAN-Meta-2.143.240|2
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-CPAN-Meta-2.143.240|1
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Module-Metadata-1.0.19|0
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-Text-ParseWords-3.290.0-r1|3
>
> ╠  ## [N] [sabayonlinux.org] virtual/perl-ExtUtils-MakeMaker-7.40.0|1
>
> ╠  ## [N] [sabayonlinux.org] dev-perl/Module-Build-0.421.400|0
>
> ╠  @@ Packages needing to be installed/updated/downgraded: 20
>
> ╠  @@ Packages needing to be removed: 0
>
> ╠  @@ Download size: 692.2kB
>
> ╠  @@ Used disk space: 1.3MB
>
> ╠  @@ You need at least: 2.6MB of free space
>
> ╠  @@ You need to accept the licenses below:
>
> ╠ :: License: GPL-1+, needed by:
>
> ╠  # [from:sabayonlinux.org] perl-core/CPAN-Meta-2.143.240
>
> ╠  # [from:sabayonlinux.org] dev-perl/Module-Build-0.421.400
>
> ╠  # [from:sabayonlinux.org] perl-core/ExtUtils-MakeMaker-7.40.0-r1
>
> ╠  # [from:sabayonlinux.org] perl-core/ExtUtils-Manifest-1.700.0
>
> ╠ Please select an option
>
> ╠   (1) Read the license
>
> ╠   (2) Accept the license (I've read it)
>
> ╠   (3) Accept the license and don't ask anymore (I've read it)
>
> ╠   (0) Quit
>
>Your choice (type a number and press enter):​
>
> ​Might have to add package to molecule build list​
>
>
> --
> KJS
> ~wolfden~
>
>
>
>

Re: [sabayon-dev] Latest MATE dev iso

[Joost Ruis]

Already fixed, wait for new images.

https://github.com/Sabayon/sabayon-distro/commit/b49b56909c2893f9d925fe7135c6468bba4fad7d

On Tue, May 19, 2015 at 8:15 AM, Wolfden  wrote:

> Booted up to test the dev MATE, when the desktop loads the Sabayon
> wallpaper is not the default wallpaper, some green stripped wallpaper
> is.  The Sabayon wallpapers aren't even in the default selection of
> wallpapers in the Appearance Preferances, one has to click add to see
> the Sabayon wallpapers.
>
> Not sure if this is the desired behavior, but I think the Sabayon
> wallpaper should at least be the default paper one sees when the
> desktop loads.
>
> As far as the Appearance Prefrences selection of wallpapers, no
> biggie, but it would be nice to have the sabayon wallpapers show up
> there.
>
>
> --
> KJS
> ~wolfden~
>
>

[sabayon-dev] app-admin/eselect-* -> app-eselect/eselect

[Joost Ruis]

Hi all,

With the Q2 moves this was 1 big issue to resolve on our overlay.
It seems that in the binary tree (all is in main now) itself everything is
fine now.

If we made some mistake, missed an atom to fix, please let me know!

For the custom eselect modules on for-gentoo overlay we wrote a file to
handle those:
https://github.com/Sabayon/for-gentoo/blob/master/profiles/updates/2Q-2015

Entropy migrated things auto magically thanks to that.

2 known things here:

1. In some ebuilds we refer to !app-admin/eselect-init I think we best keep
that one in place for old systems that actually have this installed.

2. app-misc/sabayon-version still has a gazillion ebuilds with
app-admin/eselect-python, still needs to get fixed.

Cheers!

[sabayon-dev] app-emulation/emul-linux*

[Joost Ruis]

Canz we fix our ebuilds so nothing directly deps on
any app-emulation/emul-linux* ?

e.g. x11-misc/primus or x11-drivers/nvidia-userspace
and x11-drivers/ati-userspace

[sabayon-dev] Orphan lib after installation

[Joost Ruis]

After an installation I notice that there is some broken lib left behind:

sabayon joost # ls -l /usr/lib64/librpm.so.3
lrwxrwxrwx 1 root root 15 Oct  7 19:07 /usr/lib64/librpm.so.3 ->
librpm.so.3.3.1

To resolve this I have to install rpm from Entropy and remove it again.
Anybody has a clue where this orphan is from?

Re: [sabayon-dev] Install Error on Sabayon_Linux_DAILY_amd64_MATE-dev

[Joost Ruis]

https://forum.sabayon.org/viewtopic.php?f=50&t=32242

dev-python/pyparted had to be rebuild. This should be fixed now.

On Fri, Jan 23, 2015 at 8:44 AM, Fabio Erculiani  wrote:

> It looks like this:
> https://bugs.launchpad.net/ubuntu/+source/pyparted/+bug/1350946
>
> Rebuilding should fix it, which is what I did yesterday. Could you
> please re-test this with images dated 2015-01-22 onwards.
>
> On Fri, Jan 23, 2015 at 1:11 AM, Mitch Harder
>  wrote:
> > I'm encountering an installation error on the latest MATE daily (dated
> > 21-Jan-2015).
> >
> > I've tested on a UEFI Laptop and a UEFI desktop.
> >
> > The Desktop is starting correctly, but the installation seems to be
> > failing right away.  The anaconda *.log files in /tmp all have 0 size.
> >
> > Otherwise, the live session seems to be running good.  Thanks for
> > fixing the USB-3.0 issue.
> >
> > Here's the error if I run it from a console (let me know if I should
> > provide other logs or info).
> >
> > sabayonuser@sabayon ~ $ liveinst
> > /usr/sbin/setenforce: SELinux is disabled
> > Traceback (most recent call last):
> >   File "/usr/bin/anaconda-cleanup", line 41, in 
> > from blivet import StorageDiscoveryConfig
> >   File "/usr/lib64/python2.7/site-packages/blivet/__init__.py", line
> > 62, in 
> > import parted
> >   File "/usr/lib64/python2.7/site-packages/parted/__init__.py", line
> > 62, in 
> > from parted.partition import Partition
> >   File "/usr/lib64/python2.7/site-packages/parted/partition.py", line
> > 266, in 
> > partitionFlag[__flag] = _ped.partition_flag_get_name(__flag)
> > ValueError: Invalid flag provided.
> > localuser:root being added to access control list
> > Starting installer, one moment...
> > Traceback (most recent call last):
> >   File "/usr/sbin/anaconda", line 701, in 
> > from pyanaconda import geoloc
> >   File "/usr/lib64/python2.7/site-packages/pyanaconda/geoloc.py", line
> > 109, in 
> > from pyanaconda import network
> >   File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py",
> > line 41, in 
> > from blivet.devices import FcoeDiskDevice, iScsiDiskDevice
> >   File "/usr/lib64/python2.7/site-packages/blivet/__init__.py", line
> > 62, in 
> > import parted
> >   File "/usr/lib64/python2.7/site-packages/parted/__init__.py", line
> > 62, in 
> > from parted.partition import Partition
> >   File "/usr/lib64/python2.7/site-packages/parted/partition.py", line
> > 266, in 
> > partitionFlag[__flag] = _ped.partition_flag_get_name(__flag)
> > ValueError: Invalid flag provided.
> > Traceback (most recent call last):
> >   File "/usr/bin/anaconda-cleanup", line 41, in 
> > from blivet import StorageDiscoveryConfig
> >   File "/usr/lib64/python2.7/site-packages/blivet/__init__.py", line
> > 62, in 
> > import parted
> >   File "/usr/lib64/python2.7/site-packages/parted/__init__.py", line
> > 62, in 
> > from parted.partition import Partition
> >   File "/usr/lib64/python2.7/site-packages/parted/partition.py", line
> > 266, in 
> > partitionFlag[__flag] = _ped.partition_flag_get_name(__flag)
> > ValueError: Invalid flag provided.
> > /usr/sbin/setenforce: SELinux is disabled
> >
>
>
>
> --
> Fabio Erculiani
>
>

Re: [sabayon-dev] Error with msmtp

[Joost Ruis]

I'll recompile it.

Next time use the bugzilla please.

On Fri, Jan 2, 2015 at 12:17 AM, Nicolas Sebrecht  wrote:

>   Hello,
>
> When using msmtp, I get this error:
>
>   # /usr/bin/msmtp: error while loading shared libraries: libgnutls.so.26:
>   cannot open shared object file: No such file or directory
>
> Any idea of why it is looking for library file version .26? I only have
> gnutls v3.3.10.
>
> --
> Nicolas Sebrecht
>
>

Re: [sabayon-dev] [Bug: 4800] Xdmx not available

[Joost Ruis]

Care to give some motivation why we should enable dmx on xorg-server?

On Tue, Sep 16, 2014 at 2:59 AM, Mohan R  wrote:

> Hi,
>
> Xdmx is not available in Sabayon. Kindly build Xdmx with xorg-server
> package.
>
> Thanks,
> Mohan R
>
>
>

Re: [sabayon-dev] Status of ebuilds in Bugzilla

[Joost Ruis]

AFAIK we have kinda frozen x86. I guess we can ignore that arch.

@all thanks.


On Sat, Aug 16, 2014 at 9:40 PM, Sławomir Nizio 
wrote:

> > Thanks Richard.
> >
> > I'll keep an eye on the Entropy package list.  I believe it will get
> > picked up automatically at some point.
> >
>
> Hello,
>
> It will change the "SPM repository" so, depending on the settings, not
> necessarily. I can take care of that, but first, does anyone know if
> pipelight ebuild from Portage works on x86 too?
>
>

Re: [sabayon-dev] Status of ebuilds in Bugzilla

[Joost Ruis]

Yep!


On Wed, Aug 13, 2014 at 5:10 PM, Mitch Harder  wrote:

> If I read that news item correctly, we're just waiting on that new
> version of Chrome to come out.
>
> On Wed, Aug 13, 2014 at 9:27 AM, Joost Ruis 
> wrote:
> > Nah just wait for Netflix to release their HTML5 version.
> >
> http://techreport.com/news/26897/new-chrome-beta-enables-html5-netflix-on-linux
> >
> > (@Mitch: I have an account by the way)
> >
> >
> > On Thu, Jul 24, 2014 at 8:51 PM, NP Hardass 
> wrote:
> >>
> >> Thanks for the prompt response.
> >>
> >> Regarding media-sound/pithos, I haven't tried the version in the main
> >> portage tree because the submitted ebuild has been working quite nicely
> >> without issue.  Since you have migrated to using the ones provided by
> the
> >> main portage tree, I'll submit any further issues to bugs.gentoo.org.
> >>
> >> Regarding pipelight, let me know how it goes.  I thought my new ebuild
> was
> >> superior to the previous because it handles plugins in a more generic
> and
> >> modular fashion.  I have found a slight issue regarding the x64-*
> plugins
> >> and will keep you apprised to the fix for it when I finish talking to
> >> upstream about it.
> >>
> >> Thanks again for your time.
> >>
> >>
> >> On Thu, Jul 24, 2014 at 1:09 AM, Mitch Harder
> >>  wrote:
> >>>
> >>> On Wed, Jul 23, 2014 at 11:11 PM, NP Hardass 
> >>> wrote:
> >>> > I've submitted two ebuilds to the Sabayon bugzilla at this point.
> The
> >>> > first
> >>> > of which has been sitting, without any interaction for around 8
> months.
> >>> > I
> >>> > wanted to find out what is going on.
> >>> >
> >>> >
> https://bugs.sabayon.org/buglist.cgi?email1=np.hardass%40gmail.com&emailassigned_to1=1&emailreporter1=1&emailtype1=substring&order=Importance&query_format=advanced&resolution=---
> >>> >
> >>> > Thanks in advance for your time.
> >>> >
> >>> > --
> >>> > NP-Hardass
> >>> >
> >>> >
> >>> >
> >>>
> >>> I agree, 8 months is too long.
> >>>
> >>> The issue with media-sound/pithos should be solved (I hope).  Fabio
> >>> dropped the Sabayon overlay version in favor of the version now in the
> >>> main Gentoo portage tree.  This just happened a few days ago.  Let us
> >>> know if this solves the problem.
> >>>
> >>> As far as pipelight goes, we'll try to have a look at that one.
> >>>
> >>> At this time, I dont' have a Netflix account, so we'll need to attract
> >>> the attention of a Sabayon developer who does.
> >>>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>

Re: [sabayon-dev] Status of ebuilds in Bugzilla

[Joost Ruis]

Nah just wait for Netflix to release their HTML5 version.
http://techreport.com/news/26897/new-chrome-beta-enables-html5-netflix-on-linux

(@Mitch: I have an account by the way)


On Thu, Jul 24, 2014 at 8:51 PM, NP Hardass  wrote:

> Thanks for the prompt response.
>
> Regarding media-sound/pithos, I haven't tried the version in the main
> portage tree because the submitted ebuild has been working quite nicely
> without issue.  Since you have migrated to using the ones provided by the
> main portage tree, I'll submit any further issues to bugs.gentoo.org.
>
> Regarding pipelight, let me know how it goes.  I thought my new ebuild was
> superior to the previous because it handles plugins in a more generic and
> modular fashion.  I have found a slight issue regarding the x64-* plugins
> and will keep you apprised to the fix for it when I finish talking to
> upstream about it.
>
> Thanks again for your time.
>
>
> On Thu, Jul 24, 2014 at 1:09 AM, Mitch Harder <
> mitch.har...@sabayonlinux.org> wrote:
>
>> On Wed, Jul 23, 2014 at 11:11 PM, NP Hardass 
>> wrote:
>> > I've submitted two ebuilds to the Sabayon bugzilla at this point.  The
>> first
>> > of which has been sitting, without any interaction for around 8 months.
>>  I
>> > wanted to find out what is going on.
>> >
>> https://bugs.sabayon.org/buglist.cgi?email1=np.hardass%40gmail.com&emailassigned_to1=1&emailreporter1=1&emailtype1=substring&order=Importance&query_format=advanced&resolution=---
>> >
>> > Thanks in advance for your time.
>> >
>> > --
>> > NP-Hardass
>> >
>> >
>> >
>>
>> I agree, 8 months is too long.
>>
>> The issue with media-sound/pithos should be solved (I hope).  Fabio
>> dropped the Sabayon overlay version in favor of the version now in the
>> main Gentoo portage tree.  This just happened a few days ago.  Let us
>> know if this solves the problem.
>>
>> As far as pipelight goes, we'll try to have a look at that one.
>>
>> At this time, I dont' have a Netflix account, so we'll need to attract
>> the attention of a Sabayon developer who does.
>>
>>
>
>
>
>

[sabayon-dev] Anaconda not starting

[Joost Ruis]

I grabbed a MATE DAILY from our mirrors today and noticed Anaconda not
starting up.

Here is a hint:


   1.
   Apr 02 18:09:15 sabayon dbus-daemon[2291]: dbus[2291]: [system]
Activating via systemd: service name='org.freedesktop.UDisks'
unit='udisks.service'
   2.
   Apr 02 18:09:15 sabayon dbus[2291]: [system] Activating via
systemd: service name='org.freedesktop.UDisks' unit='udisks.service'
   3.
   Apr 02 18:09:15 sabayon systemd[1]: Starting Disk Manager (legacy version)...
   4.
   Apr 02 18:09:15 sabayon systemd[2929]: Failed at step EXEC spawning
/usr/lib/udisks/udisks-daemon: No such file or directory
   5.
   Apr 02 18:09:15 sabayon systemd[1]: udisks.service: main process
exited, code=exited, status=203/EXEC
   6.
   Apr 02 18:09:15 sabayon systemd[1]: Failed to start Disk Manager
(legacy version).
   7.
   Apr 02 18:09:15 sabayon systemd[1]: Unit udisks.service entered failed state.

Re: [sabayon-dev] Sabayon fails to boot after last update (Limbo)

[Joost Ruis]

"reinstalling systemd-sysv-utils should always bring
back a correct /sbin/init (which is a symlink)."

That is how it got fixed on my end, so confirmed.

Hopefully somebody else can confirm this is fixed.

first --> equo upgrade pulled in systemd revision.
second is -> equo install systemd-sysv-utils

Afterwards:
sabayon joost # ls -l  /sbin/init
lrwxrwxrwx 1 root root 26 Mar 26 19:43 /sbin/init ->
../usr/lib/systemd/systemd

Now the system boots up.

[19:39:50 26/03/2014 CET] INFO: [Package] [client] Installing package:
sys-apps/systemd-208-r3
[19:39:50 26/03/2014 CET] INFO: [Package] [client] WARNING!!! Failed to
handle file protection for: /etc/sysctl.d/99-sysctl.conf, broken symlink in
package
[19:39:57 26/03/2014 CET] INFO: [Trigger] [client] [POST] Running env_update
[19:39:58 26/03/2014 CET] INFO: [Package] [client] Remove old package (spm
data): sys-apps/systemd-208-r3
[19:39:58 26/03/2014 CET] INFO: [Package] [client] Removing from SPM:
sys-apps/systemd-208-r3
[19:39:58 26/03/2014 CET] INFO: [Package] [client] Installing new SPM
entry: sys-apps/systemd-208-r3
[19:40:01 26/03/2014 CET] INFO: [Trigger] [client] [POST] Running env_update
 * Updating systemd journal catalogs ... [
ok ]
 * Running udev control --reload for reloading rules and databases ...   [
ok ]
[19:43:48 26/03/2014 CET] INFO: [Package] [client] Removing package:
sys-apps/sysvinit-2.88-r10
[19:43:50 26/03/2014 CET] INFO: [Trigger] [client] [POST] Running env_update
[19:43:50 26/03/2014 CET] INFO: [Package] [client] Removing from SPM:
sys-apps/sysvinit-2.88-r10
[19:43:50 26/03/2014 CET] INFO: [Package] [client] Unpacking package:
/var/lib/entropy/client/packages/packages/amd64/5/sys-apps/sys-apps:systemd-sysv-utils-208.0c56af60c5f25f0470fc60063f66cd15e3b1bb05~1.tbz2
[19:43:51 26/03/2014 CET] INFO: [Package] [client] Installing package:
sys-apps/systemd-sysv-utils-208
[19:43:51 26/03/2014 CET] INFO: [Package] [client] Installing new SPM
entry: sys-apps/systemd-sysv-utils-208



On Wed, Mar 26, 2014 at 8:45 PM, Fabio Erculiani  wrote:

> I have found another problem. Basically sysvinit is set to be updated in
> spite of the fact that it should be dropped. Fixing it soon.
>
>
>
>

Re: [sabayon-dev] Sabayon fails to boot after last update (Limbo)

[Joost Ruis]

*So I manually created the symlink


On Tue, Mar 25, 2014 at 10:43 PM, Joost Ruis wrote:

>  @Fabio I noticed your commit here:
>
> https://github.com/Sabayon/sabayon-distro/commit/0d25ba5780aa6366fc1d559f6a99f6d8f8cf8113
>
>  To see how it was on my end..
>  sabayon / # ls -l /sbin/init
> ls: cannot access /sbin/init: No such file or directory
>
>  So I manually did:
>
>  sabayon / # ls -l  /sbin/init
> lrwxrwxrwx 1 root root 24 Mar 25 22:28 /sbin/init ->
> /usr/lib/systemd/systemd
>
> Sadly this didn't work. I'm a bit lost here. Hopefully it only affects me.
> (o:
>
>
>  On Tue, Mar 25, 2014 at 11:15 PM, Joost Ruis wrote:
>
>> After my last upgrade today my systems fails to boot unless I instruct to
>> load init=/usr/lib/systemd/systemd directly from the command line.
>>
>>  To me it seems it is a symlink that went /dev/null here.
>>
>>  A snip. from my entropy.log:
>>
>>   * Purging current Entropy cache
>>
>>   * If you want to enable Entropy packages delta download support, please
>>   * install dev-util/bsdiff.
>>
>>  [22:50:25 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
>> /var/lib/entropy/client/packages/packages/amd64/5/sys-apps/sys-apps:systemd-208-r3.69eb7a7bd25d09dcddd0bbc0a4c53eda1bef5cac~3.tbz2
>>  * Determining the location of the kernel source code
>>  * Found kernel source directory:
>>  * /usr/src/linux
>>  * Found sources for kernel version:
>>  * 3.12.0-sabayon
>>   * Checking for suitable kernel configuration options...
>> [ ok ]
>> [22:50:29 25/03/2014 CET] INFO: [Package] [client] Installing package:
>> sys-apps/systemd-208-r3
>> [22:50:29 25/03/2014 CET] INFO: [Package] [client] WARNING!!! Failed to
>> handle file protection for: /etc/sysctl.d/99-sysctl.conf, broken symlink in
>> package
>> Setting the init implementation to systemd
>> [22:50:33 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running
>> env_update
>> !!! Error: Target "systemd" doesn't appear to be valid!
>>  exiting
>> [22:50:34 25/03/2014 CET] INFO: [Package] [client] Remove old package
>> (spm data): sys-apps/systemd-208-r3
>> [22:50:34 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
>> sys-apps/systemd-208-r3
>> [22:50:34 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
>> entry: sys-apps/systemd-208-r3
>> [22:50:35 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running
>> env_update
>>  * Updating systemd journal catalogs ...
>> [ ok ]
>>  * Running udev control --reload for reloading rules and databases ...
>> [ ok ]
>> [22:51:10 25/03/2014 CET] INFO: [Package] [client] Removing package:
>> sys-apps/sysvinit-2.88-r10
>> !!! Error: Target "systemd" doesn't appear to be valid!
>> exiting
>> [22:51:15 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running
>> env_update
>> !!! Error: Target "systemd" doesn't appear to be valid!
>> exiting
>> [22:51:16 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
>> sys-apps/sysvinit-2.88-r10
>> [22:51:16 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
>> /var/lib/entropy/client/packages/packages/amd64/5/sys-apps/sys-apps:systemd-sysv-utils-208.75d36f23df9e16a08f896014956eee0f4eade8e1~0.tbz2
>>  [22:51:16 25/03/2014 CET] INFO: [Package] [client] Installing package:
>> sys-apps/systemd-sysv-utils-208
>> [22:51:17 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
>> entry: sys-apps/systemd-sysv-utils-208
>> [22:51:27 25/03/2014 CET] INFO: [Package] [client] Removing package:
>> app-admin/eselect-init-0.6
>> [22:51:28 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
>> app-admin/eselect-init-0.6
>> [22:51:28 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
>> /var/lib/entropy/client/packages/packages/amd64/5/app-misc/app-misc:sabayon-version-14.04-r2.14860fc183ded0b12aee1fac793a3ea7c5fe3ae5~0.tbz2
>> [22:51:28 25/03/2014 CET] INFO: [Package] [client] Installing package:
>> app-misc/sabayon-version-14.04-r2
>> [22:51:29 25/03/2014 CET] INFO: [Package] [client] Remove old package
>> (spm data): app-misc/sabayon-version-14.04
>> [22:51:29 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
>> app-misc/sabayon-version-14.04
>> [22:51:29 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
>> entry: app-misc/sabayon-version-14.04-r2
>> [22:52:19 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
>> /var/lib/entropy/client/packages/packages/amd64/5/sys-kernel/sys-kernel:dracut-037.69b2206b913ace722401c876f8606e02457f578e~0.tbz2
>> [22:52:22 25/03/2014 CET] INFO: [Package] [client] Installing package:
>> sys-kernel/dracut-037
>> [22:52:23 25/03/2014 CET] INFO: [Package] [client] Remove old package
>> (spm data): sys-kernel/dracut-036-r4
>> [22:52:23 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
>> sys-kernel/dracut-036-r4
>> [22:52:23 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
>> entry: sys-kernel/dracut-037
>>
>>
>

Re: [sabayon-dev] Sabayon fails to boot after last update (Limbo)

[Joost Ruis]

@Fabio I noticed your commit here:
https://github.com/Sabayon/sabayon-distro/commit/0d25ba5780aa6366fc1d559f6a99f6d8f8cf8113

To see how it was on my end..
sabayon / # ls -l /sbin/init
ls: cannot access /sbin/init: No such file or directory

So I manually did:

sabayon / # ls -l  /sbin/init
lrwxrwxrwx 1 root root 24 Mar 25 22:28 /sbin/init ->
/usr/lib/systemd/systemd

Sadly this didn't work. I'm a bit lost here. Hopefully it only affects
me. (o:


On Tue, Mar 25, 2014 at 11:15 PM, Joost Ruis mailto:joost.r...@sabayon.org>> wrote:

After my last upgrade today my systems fails to boot unless I
instruct to load init=/usr/lib/systemd/systemd directly from the
command line.

To me it seems it is a symlink that went /dev/null here.

A snip. from my entropy.log:

 * Purging current Entropy cache

 * If you want to enable Entropy packages delta download support, please
 * install dev-util/bsdiff.

[22:50:25 25/03/2014 CET] INFO: [Package] [client] Unpacking
package:

/var/lib/entropy/client/packages/packages/amd64/5/sys-apps/sys-apps:systemd-208-r3.69eb7a7bd25d09dcddd0bbc0a4c53eda1bef5cac~3.tbz2
 * Determining the location of the kernel source code
 * Found kernel source directory:
 * /usr/src/linux
 * Found sources for kernel version:
 * 3.12.0-sabayon
 * Checking for suitable kernel configuration options...
[ ok ]
[22:50:29 25/03/2014 CET] INFO: [Package] [client] Installing
package: sys-apps/systemd-208-r3
[22:50:29 25/03/2014 CET] INFO: [Package] [client] WARNING!!! Failed
to handle file protection for: /etc/sysctl.d/99-sysctl.conf, broken
symlink in package
Setting the init implementation to systemd
[22:50:33 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running
env_update
!!! Error: Target "systemd" doesn't appear to be valid!
exiting
[22:50:34 25/03/2014 CET] INFO: [Package] [client] Remove old
package (spm data): sys-apps/systemd-208-r3
[22:50:34 25/03/2014 CET] INFO: [Package] [client] Removing from
SPM: sys-apps/systemd-208-r3
[22:50:34 25/03/2014 CET] INFO: [Package] [client] Installing new
SPM entry: sys-apps/systemd-208-r3
[22:50:35 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running
env_update
 * Updating systemd journal catalogs ...
[ ok ]
 * Running udev control --reload for reloading rules and databases
...   [ ok ]
[22:51:10 25/03/2014 CET] INFO: [Package] [client] Removing package:
sys-apps/sysvinit-2.88-r10
!!! Error: Target "systemd" doesn't appear to be valid!
exiting
[22:51:15 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running
env_update
!!! Error: Target "systemd" doesn't appear to be valid!
exiting
[22:51:16 25/03/2014 CET] INFO: [Package] [client] Removing from
SPM: sys-apps/sysvinit-2.88-r10
[22:51:16 25/03/2014 CET] INFO: [Package] [client] Unpacking
package:

/var/lib/entropy/client/packages/packages/amd64/5/sys-apps/sys-apps:systemd-sysv-utils-208.75d36f23df9e16a08f896014956eee0f4eade8e1~0.tbz2
[22:51:16 25/03/2014 CET] INFO: [Package] [client] Installing
package: sys-apps/systemd-sysv-utils-208
[22:51:17 25/03/2014 CET] INFO: [Package] [client] Installing new
SPM entry: sys-apps/systemd-sysv-utils-208
[22:51:27 25/03/2014 CET] INFO: [Package] [client] Removing package:
app-admin/eselect-init-0.6
[22:51:28 25/03/2014 CET] INFO: [Package] [client] Removing from
SPM: app-admin/eselect-init-0.6
[22:51:28 25/03/2014 CET] INFO: [Package] [client] Unpacking
package:

/var/lib/entropy/client/packages/packages/amd64/5/app-misc/app-misc:sabayon-version-14.04-r2.14860fc183ded0b12aee1fac793a3ea7c5fe3ae5~0.tbz2
[22:51:28 25/03/2014 CET] INFO: [Package] [client] Installing
package: app-misc/sabayon-version-14.04-r2
[22:51:29 25/03/2014 CET] INFO: [Package] [client] Remove old
package (spm data): app-misc/sabayon-version-14.04
[22:51:29 25/03/2014 CET] INFO: [Package] [client] Removing from
SPM: app-misc/sabayon-version-14.04
[22:51:29 25/03/2014 CET] INFO: [Package] [client] Installing new
SPM entry: app-misc/sabayon-version-14.04-r2
[22:52:19 25/03/2014 CET] INFO: [Package] [client] Unpacking
package:

/var/lib/entropy/client/packages/packages/amd64/5/sys-kernel/sys-kernel:dracut-037.69b2206b913ace722401c876f8606e02457f578e~0.tbz2
[22:52:22 25/03/2014 CET] INFO: [Package] [client] Installing
package: sys-kernel/dracut-037
[22:52:23 25/03/2014 CET] INFO: [Package] [client] Remove old
package (spm data): sys-kernel/dracut-036-r4
[22:52:23 25/03/2014 CET] INFO: [Package] [client] Removing from
SPM: sys-kernel/dracut-036-r4
[22:52:23 25/03/2014 CET] INFO: [Package] [client] Installing new
SPM entry: sys-kernel/dracut-037

[sabayon-dev] Sabayon fails to boot after last update (Limbo)

[Joost Ruis]

After my last upgrade today my systems fails to boot unless I instruct to
load init=/usr/lib/systemd/systemd directly from the command line.

To me it seems it is a symlink that went /dev/null here.

A snip. from my entropy.log:

 * Purging current Entropy cache

 * If you want to enable Entropy packages delta download support, please
 * install dev-util/bsdiff.

[22:50:25 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
/var/lib/entropy/client/packages/packages/amd64/5/sys-apps/sys-apps:systemd-208-r3.69eb7a7bd25d09dcddd0bbc0a4c53eda1bef5cac~3.tbz2
 * Determining the location of the kernel source code
 * Found kernel source directory:
 * /usr/src/linux
 * Found sources for kernel version:
 * 3.12.0-sabayon
 * Checking for suitable kernel configuration options... [
ok ]
[22:50:29 25/03/2014 CET] INFO: [Package] [client] Installing package:
sys-apps/systemd-208-r3
[22:50:29 25/03/2014 CET] INFO: [Package] [client] WARNING!!! Failed to
handle file protection for: /etc/sysctl.d/99-sysctl.conf, broken symlink in
package
Setting the init implementation to systemd
[22:50:33 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running env_update
!!! Error: Target "systemd" doesn't appear to be valid!
exiting
[22:50:34 25/03/2014 CET] INFO: [Package] [client] Remove old package (spm
data): sys-apps/systemd-208-r3
[22:50:34 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
sys-apps/systemd-208-r3
[22:50:34 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
entry: sys-apps/systemd-208-r3
[22:50:35 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running env_update
 * Updating systemd journal catalogs ... [
ok ]
 * Running udev control --reload for reloading rules and databases ...   [
ok ]
[22:51:10 25/03/2014 CET] INFO: [Package] [client] Removing package:
sys-apps/sysvinit-2.88-r10
!!! Error: Target "systemd" doesn't appear to be valid!
exiting
[22:51:15 25/03/2014 CET] INFO: [Trigger] [client] [POST] Running env_update
!!! Error: Target "systemd" doesn't appear to be valid!
exiting
[22:51:16 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
sys-apps/sysvinit-2.88-r10
[22:51:16 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
/var/lib/entropy/client/packages/packages/amd64/5/sys-apps/sys-apps:systemd-sysv-utils-208.75d36f23df9e16a08f896014956eee0f4eade8e1~0.tbz2
[22:51:16 25/03/2014 CET] INFO: [Package] [client] Installing package:
sys-apps/systemd-sysv-utils-208
[22:51:17 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
entry: sys-apps/systemd-sysv-utils-208
[22:51:27 25/03/2014 CET] INFO: [Package] [client] Removing package:
app-admin/eselect-init-0.6
[22:51:28 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
app-admin/eselect-init-0.6
[22:51:28 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
/var/lib/entropy/client/packages/packages/amd64/5/app-misc/app-misc:sabayon-version-14.04-r2.14860fc183ded0b12aee1fac793a3ea7c5fe3ae5~0.tbz2
[22:51:28 25/03/2014 CET] INFO: [Package] [client] Installing package:
app-misc/sabayon-version-14.04-r2
[22:51:29 25/03/2014 CET] INFO: [Package] [client] Remove old package (spm
data): app-misc/sabayon-version-14.04
[22:51:29 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
app-misc/sabayon-version-14.04
[22:51:29 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
entry: app-misc/sabayon-version-14.04-r2
[22:52:19 25/03/2014 CET] INFO: [Package] [client] Unpacking package:
/var/lib/entropy/client/packages/packages/amd64/5/sys-kernel/sys-kernel:dracut-037.69b2206b913ace722401c876f8606e02457f578e~0.tbz2
[22:52:22 25/03/2014 CET] INFO: [Package] [client] Installing package:
sys-kernel/dracut-037
[22:52:23 25/03/2014 CET] INFO: [Package] [client] Remove old package (spm
data): sys-kernel/dracut-036-r4
[22:52:23 25/03/2014 CET] INFO: [Package] [client] Removing from SPM:
sys-kernel/dracut-036-r4
[22:52:23 25/03/2014 CET] INFO: [Package] [client] Installing new SPM
entry: sys-kernel/dracut-037

[sabayon-dev] Fast TSC calibration failed

[Joost Ruis]

Hi,

I noticed that a kernel error line was flashing on my screen while booting.
This made the transition from plymouth to KDM (or whatever DM) a bit ugly.
A short black screen flicker with this message printed.

To resolve this I found this:
http://penguintengil.wordpress.com/2012/11/03/solving-error-0-00-fast-tsc-calibration-failed-when-booting-in-fedora-16/

What I did was edit /etc/default/grub and add clocksource=acpi_pm to
the GRUB_CMDLINE_LINUX="" var. and regenerated my grub.cfg

This resolved it for me

Am I the only one who noticed/suffers from this? Is this something to perm
include in our boot line?

Cheers.

Re: [sabayon-dev] ModemManager1.service

[Joost Ruis]

Whatever. Not that I really care too much about it.

After manually loading the service:

xbox-360 joost # systemctl status ModemManager.service


ModemManager.service - Modem Manager


   Loaded: loaded (/usr/lib64/systemd/system/ModemManager.service; enabled)
   Active: active (running) since Thu 2014-02-13 23:15:42 CET; 1min 30s ago
 Main PID: 16875 (ModemManager)
   CGroup: name=systemd:/system/ModemManager.service
   └─16875 /usr/sbin/ModemManager

I was under impression that whenever some dep was needed systemd would load
it, I guess I'm wrong there..??
This solved the endless error spam in my /var/log/messages

So perhaps enable it by default.


On Thu, Feb 13, 2014 at 8:10 AM, Fabio Erculiani  wrote:

> How about using google, you'd have found (easily) that the solution is
> simple and that there's also an open bug upstream.
>
> --
> Fabio Erculiani
>
>
>
>

Re: [sabayon-dev] ModemManager1.service

[Joost Ruis]

Yes. It gets pulled in by NM as a dep.


On Wed, Feb 12, 2014 at 8:50 AM, Ian Whyman  wrote:

> Install modemmanager?
> On 11 Feb 2014 23:07, "Joost Ruis"  wrote:
>
>> On a tail -f /var/log/messages I keep seeying this (for a while now)
>>
>> Feb 12 00:04:56 localhost dbus[3151]: [system] Activating via systemd:
>> service name='org.freedesktop.ModemManager1'
>> unit='dbus-org.freedesktop.ModemManager1.service'
>> Feb 12 00:04:56 localhost dbus[3151]: [system] Activation via systemd
>> failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit
>> dbus-org.freedesktop.ModemManager1.service failed to load: No such file or
>> directory. See system logs and 'systemctl status
>> dbus-org.freedesktop.ModemManager1.service' for details.
>> Feb 12 00:04:56 localhost dbus-daemon[3151]: dbus[3151]: [system]
>> Activation via systemd failed for unit
>> 'dbus-org.freedesktop.ModemManager1.service': Unit
>> dbus-org.freedesktop.ModemManager1.service failed to load: No such file or
>> directory. See system logs and 'systemctl status
>> dbus-org.freedesktop.ModemManager1.service' for details.
>>
>> Any idea how to get this one fixed?
>>
>>
>>
>>
>
>
>

[sabayon-dev] ModemManager1.service

[Joost Ruis]

On a tail -f /var/log/messages I keep seeying this (for a while now)

Feb 12 00:04:56 localhost dbus[3151]: [system] Activating via systemd:
service name='org.freedesktop.ModemManager1'
unit='dbus-org.freedesktop.ModemManager1.service'
Feb 12 00:04:56 localhost dbus[3151]: [system] Activation via systemd
failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit
dbus-org.freedesktop.ModemManager1.service failed to load: No such file or
directory. See system logs and 'systemctl status
dbus-org.freedesktop.ModemManager1.service' for details.
Feb 12 00:04:56 localhost dbus-daemon[3151]: dbus[3151]: [system]
Activation via systemd failed for unit
'dbus-org.freedesktop.ModemManager1.service': Unit
dbus-org.freedesktop.ModemManager1.service failed to load: No such file or
directory. See system logs and 'systemctl status
dbus-org.freedesktop.ModemManager1.service' for details.

Any idea how to get this one fixed?

Re: [sabayon-dev] Testing Report: Sabayon Mate x86_64 Daily 20140115

[Joost Ruis]

"Can gnome-disk-utility resize partitions?"
That I'm not sure about, I rarely resize partitions.

You can find gnome-disk-utility in the menu under Applications ->
Accessoires -> Disks




On Sun, Jan 19, 2014 at 7:36 PM, Mitch Harder  wrote:

> On Sun, Jan 19, 2014 at 12:14 PM, Joost Ruis 
> wrote:
> > My 2 cents here.
> >
> > By coincidence I test installed the same Daily on an atom netbook
> yesterday
> > (32bits).
> > I had no issues with it. (installed from scratch twice)
> >
> > @Mitch
> > - MATE iso ships with sys-apps/gnome-disk-utility that is imho superior
> to
> > gparted.
>
> Can gnome-disk-utility resize partitions?
> Perhaps we should just add it to the menu.  I did not realize it was there.
>
> > - RE: /etc/init.d/xdm stop.. I guess the command you should use is
> systemctl
> > restart lightdm
> >
>
> Yeah, I realized the stupid mistake I made about a minute after I hit
> 'send'.  :)
>
>

Re: [sabayon-dev] Testing Report: Sabayon Mate x86_64 Daily 20140115

[Joost Ruis]

My 2 cents here.

By coincidence I test installed the same Daily on an atom netbook yesterday
(32bits).
I had no issues with it. (installed from scratch twice)

@Mitch
- MATE iso ships with sys-apps/gnome-disk-utility that is imho superior to
gparted.
- RE: /etc/init.d/xdm stop.. I guess the command you should use is
systemctl restart lightdm

Cheers



On Sun, Jan 19, 2014 at 7:03 PM, Mitch Harder  wrote:

> I've been testing the Sabayon Mate 20140115 x86_64 daily.
>
> I needed to recover my ability to boot Linux after the Windows 8.1
> upgrade on my laptop somehow made all my Linux boot options disappear.
>
> I made an UEFI install to this laptop, and didn't encounter any
> problems except for the lack of gparted.  Dual booting in UEFI mode
> with Windows 8.1 and Sabayon Mate is working fine.
>
> I would recommend gparted be added to the Sabayon Mate edition.  There
> were only two small dependency issues (hfsutils and some other minor
> package), so there were no Gnome or KDE dependency bombs.
>
> I also made an install to one of my Desktop boxes (Dell Optiplex 745).
>  In particular I wanted to test the new version of btrfs-progs.  I had
> no issues installing to a partition previously formated for btrfs
> (which used to cause problems in an unpatched version of the old
> btrfs-progs).
>
> I only had two minor problems.  I may have inadvertently caused both
> problems, but I haven't tracked down the causes yet.
>
> First, the resolution of the installed version was very low.  The live
> session worked fine in detecting and configuring my i915 intel video
> card and monitor.  But something didn't work right on the installed
> version with respect to monitor resolution.
>
> Second, I ran into some minor issues trying to restart light_dm.  It
> wasn't responding to '/etc/init.d/xdm stop'.
>
> But all in all, this Sabayon Mate edition was working well.
>
> Regards,
> Mitch.
>
>

Re: [sabayon-dev] fglrx with latest Live iso (August 1st 2013 taken from rsync)

[Joost Ruis]

Today I switched to the 3.11 kernel. (and skipped the 3.10 kernel)

xbox-360 joost # uname -r && lsmod | grep fglrx
3.11.0-sabayon
fglrx6831209  75
agpgart22168  5 drm,ttm,fglrx,intel_agp,intel_gtt

All seems fine. This monologue can be marked solved.


On Sat, Sep 7, 2013 at 11:09 PM, Joost Ruis  wrote:

> I noticed 13.8 Beta driver hit Limbo so I went testing.
> Using the 3.9 kernel the system boots up fine. I did notice that after
> upgrading my opengl profile was set to x11 rather then ati. Before
> rebooting I manually corrected this.
>
>
>
>
> On Tue, Aug 27, 2013 at 11:15 PM, Joost Ruis wrote:
>
>> With all good will in the world after installing those drivers I've been
>> unable to boot my 3.10 or even 3.9 kernel using all possible boot flags.
>> (gentoo=nox disable splash etc etc I tried all)
>> A nogo thus far. )o;
>>
>> Trying to undo it all...
>>
>>
>> On Tue, Aug 27, 2013 at 10:14 PM, Joost Ruis wrote:
>>
>>> http://data.gpo.zugaina.org/gentoo/x11-drivers/ati-drivers/ChangeLog
>>>
>>> In Portage now, I'll go try test them against our 3.10 kernel.
>>>
>>>
>>> On Tue, Aug 6, 2013 at 8:05 PM, Joost Ruis wrote:
>>>
>>>> I guess bumping ati-drivers resolves all issues.
>>>>
>>>>
>>>> http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-8LINBetaDriver.aspx
>>>>
>>>> *Highlights of the AMD Catalyst™ 13.8 Beta Driver for Linux:*
>>>>
>>>> This release of AMD Catalyst™ Linux introduces support for the
>>>> following new features:
>>>>
>>>>- OpenGL 4.3 support
>>>>- Dynamic primary surface resizing
>>>>- *Kernel 3.10 support*
>>>>- SLED 11 SP3 support
>>>>
>>>>
>>>>
>>>> On Fri, Aug 2, 2013 at 7:28 PM, Joost Ruis wrote:
>>>>
>>>>> A quick followup on this, testing on my 2nd ATI/AMD system:
>>>>>
>>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee
>>>>> ATI RV770 [Radeon HD 4850]
>>>>>
>>>>> In this case KMS also kicks in, but now the FOSS driver is being used
>>>>> it seems, all is well.
>>>>>
>>>>>
>>>>> On Fri, Aug 2, 2013 at 5:22 PM, Joost Ruis wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I tested the latest amd64 MATE daily iso.
>>>>>> On all Intel graphics systems there was no issue, but on my AMD/ATI
>>>>>> PC there was.
>>>>>>
>>>>>> I had to explicitly set nomodeset on boot in order to get it running.
>>>>>> Without that KMS kicks in and the system freezes up.
>>>>>>
>>>>>> The system has this card:
>>>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee
>>>>>> ATI Cypress PRO [Radeon HD 5850]
>>>>>>
>>>>>> - If we are going to release the next release like this, and I guess
>>>>>> we are, perhaps add a note about it to the release notes. It is fairly
>>>>>> simple (Press F5 and check nomodeset).
>>>>>>
>>>>>> - If we are not going to release with a problem like this, what can I
>>>>>> do to help tackle this problem? Is there some bug in the detection tools
>>>>>> perhaps?
>>>>>>
>>>>>> - Also consider to not release with FGLRX preinstalled at all?
>>>>>>
>>>>>> Cheers.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [sabayon-dev] fglrx with latest Live iso (August 1st 2013 taken from rsync)

[Joost Ruis]

I noticed 13.8 Beta driver hit Limbo so I went testing.
Using the 3.9 kernel the system boots up fine. I did notice that after
upgrading my opengl profile was set to x11 rather then ati. Before
rebooting I manually corrected this.




On Tue, Aug 27, 2013 at 11:15 PM, Joost Ruis  wrote:

> With all good will in the world after installing those drivers I've been
> unable to boot my 3.10 or even 3.9 kernel using all possible boot flags.
> (gentoo=nox disable splash etc etc I tried all)
> A nogo thus far. )o;
>
> Trying to undo it all...
>
>
> On Tue, Aug 27, 2013 at 10:14 PM, Joost Ruis wrote:
>
>> http://data.gpo.zugaina.org/gentoo/x11-drivers/ati-drivers/ChangeLog
>>
>> In Portage now, I'll go try test them against our 3.10 kernel.
>>
>>
>> On Tue, Aug 6, 2013 at 8:05 PM, Joost Ruis wrote:
>>
>>> I guess bumping ati-drivers resolves all issues.
>>>
>>>
>>> http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-8LINBetaDriver.aspx
>>>
>>> *Highlights of the AMD Catalyst™ 13.8 Beta Driver for Linux:*
>>>
>>> This release of AMD Catalyst™ Linux introduces support for the following
>>> new features:
>>>
>>>- OpenGL 4.3 support
>>>- Dynamic primary surface resizing
>>>- *Kernel 3.10 support*
>>>- SLED 11 SP3 support
>>>
>>>
>>>
>>> On Fri, Aug 2, 2013 at 7:28 PM, Joost Ruis wrote:
>>>
>>>> A quick followup on this, testing on my 2nd ATI/AMD system:
>>>>
>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
>>>> RV770 [Radeon HD 4850]
>>>>
>>>> In this case KMS also kicks in, but now the FOSS driver is being used
>>>> it seems, all is well.
>>>>
>>>>
>>>> On Fri, Aug 2, 2013 at 5:22 PM, Joost Ruis wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I tested the latest amd64 MATE daily iso.
>>>>> On all Intel graphics systems there was no issue, but on my AMD/ATI PC
>>>>> there was.
>>>>>
>>>>> I had to explicitly set nomodeset on boot in order to get it running.
>>>>> Without that KMS kicks in and the system freezes up.
>>>>>
>>>>> The system has this card:
>>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee
>>>>> ATI Cypress PRO [Radeon HD 5850]
>>>>>
>>>>> - If we are going to release the next release like this, and I guess
>>>>> we are, perhaps add a note about it to the release notes. It is fairly
>>>>> simple (Press F5 and check nomodeset).
>>>>>
>>>>> - If we are not going to release with a problem like this, what can I
>>>>> do to help tackle this problem? Is there some bug in the detection tools
>>>>> perhaps?
>>>>>
>>>>> - Also consider to not release with FGLRX preinstalled at all?
>>>>>
>>>>> Cheers.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [sabayon-dev] fglrx with latest Live iso (August 1st 2013 taken from rsync)

[Joost Ruis]

With all good will in the world after installing those drivers I've been
unable to boot my 3.10 or even 3.9 kernel using all possible boot flags.
(gentoo=nox disable splash etc etc I tried all)
A nogo thus far. )o;

Trying to undo it all...


On Tue, Aug 27, 2013 at 10:14 PM, Joost Ruis  wrote:

> http://data.gpo.zugaina.org/gentoo/x11-drivers/ati-drivers/ChangeLog
>
> In Portage now, I'll go try test them against our 3.10 kernel.
>
>
> On Tue, Aug 6, 2013 at 8:05 PM, Joost Ruis  wrote:
>
>> I guess bumping ati-drivers resolves all issues.
>>
>>
>> http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-8LINBetaDriver.aspx
>>
>> *Highlights of the AMD Catalyst™ 13.8 Beta Driver for Linux:*
>>
>> This release of AMD Catalyst™ Linux introduces support for the following
>> new features:
>>
>>- OpenGL 4.3 support
>>- Dynamic primary surface resizing
>>    - *Kernel 3.10 support*
>>- SLED 11 SP3 support
>>
>>
>>
>> On Fri, Aug 2, 2013 at 7:28 PM, Joost Ruis wrote:
>>
>>> A quick followup on this, testing on my 2nd ATI/AMD system:
>>>
>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
>>> RV770 [Radeon HD 4850]
>>>
>>> In this case KMS also kicks in, but now the FOSS driver is being used it
>>> seems, all is well.
>>>
>>>
>>> On Fri, Aug 2, 2013 at 5:22 PM, Joost Ruis wrote:
>>>
>>>> Hi all,
>>>>
>>>> I tested the latest amd64 MATE daily iso.
>>>> On all Intel graphics systems there was no issue, but on my AMD/ATI PC
>>>> there was.
>>>>
>>>> I had to explicitly set nomodeset on boot in order to get it running.
>>>> Without that KMS kicks in and the system freezes up.
>>>>
>>>> The system has this card:
>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
>>>> Cypress PRO [Radeon HD 5850]
>>>>
>>>> - If we are going to release the next release like this, and I guess we
>>>> are, perhaps add a note about it to the release notes. It is fairly simple
>>>> (Press F5 and check nomodeset).
>>>>
>>>> - If we are not going to release with a problem like this, what can I
>>>> do to help tackle this problem? Is there some bug in the detection tools
>>>> perhaps?
>>>>
>>>> - Also consider to not release with FGLRX preinstalled at all?
>>>>
>>>> Cheers.
>>>>
>>>>
>>>>
>>>>
>>>
>>
>

Re: [sabayon-dev] fglrx with latest Live iso (August 1st 2013 taken from rsync)

[Joost Ruis]

http://data.gpo.zugaina.org/gentoo/x11-drivers/ati-drivers/ChangeLog

In Portage now, I'll go try test them against our 3.10 kernel.


On Tue, Aug 6, 2013 at 8:05 PM, Joost Ruis  wrote:

> I guess bumping ati-drivers resolves all issues.
>
>
> http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-8LINBetaDriver.aspx
>
> *Highlights of the AMD Catalyst™ 13.8 Beta Driver for Linux:*
>
> This release of AMD Catalyst™ Linux introduces support for the following
> new features:
>
>- OpenGL 4.3 support
>- Dynamic primary surface resizing
>- *Kernel 3.10 support*
>- SLED 11 SP3 support
>
>
>
> On Fri, Aug 2, 2013 at 7:28 PM, Joost Ruis  wrote:
>
>> A quick followup on this, testing on my 2nd ATI/AMD system:
>>
>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
>> RV770 [Radeon HD 4850]
>>
>> In this case KMS also kicks in, but now the FOSS driver is being used it
>> seems, all is well.
>>
>>
>> On Fri, Aug 2, 2013 at 5:22 PM, Joost Ruis wrote:
>>
>>> Hi all,
>>>
>>> I tested the latest amd64 MATE daily iso.
>>> On all Intel graphics systems there was no issue, but on my AMD/ATI PC
>>> there was.
>>>
>>> I had to explicitly set nomodeset on boot in order to get it running.
>>> Without that KMS kicks in and the system freezes up.
>>>
>>> The system has this card:
>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
>>> Cypress PRO [Radeon HD 5850]
>>>
>>> - If we are going to release the next release like this, and I guess we
>>> are, perhaps add a note about it to the release notes. It is fairly simple
>>> (Press F5 and check nomodeset).
>>>
>>> - If we are not going to release with a problem like this, what can I do
>>> to help tackle this problem? Is there some bug in the detection tools
>>> perhaps?
>>>
>>> - Also consider to not release with FGLRX preinstalled at all?
>>>
>>> Cheers.
>>>
>>>
>>>
>>>
>>
>

Re: [sabayon-dev] fglrx with latest Live iso (August 1st 2013 taken from rsync)

[Joost Ruis]

I guess bumping ati-drivers resolves all issues.

http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-8LINBetaDriver.aspx

*Highlights of the AMD Catalyst™ 13.8 Beta Driver for Linux:*

This release of AMD Catalyst™ Linux introduces support for the following
new features:

   - OpenGL 4.3 support
   - Dynamic primary surface resizing
   - *Kernel 3.10 support*
   - SLED 11 SP3 support



On Fri, Aug 2, 2013 at 7:28 PM, Joost Ruis  wrote:

> A quick followup on this, testing on my 2nd ATI/AMD system:
>
> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
> RV770 [Radeon HD 4850]
>
> In this case KMS also kicks in, but now the FOSS driver is being used it
> seems, all is well.
>
>
> On Fri, Aug 2, 2013 at 5:22 PM, Joost Ruis  wrote:
>
>> Hi all,
>>
>> I tested the latest amd64 MATE daily iso.
>> On all Intel graphics systems there was no issue, but on my AMD/ATI PC
>> there was.
>>
>> I had to explicitly set nomodeset on boot in order to get it running.
>> Without that KMS kicks in and the system freezes up.
>>
>> The system has this card:
>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
>> Cypress PRO [Radeon HD 5850]
>>
>> - If we are going to release the next release like this, and I guess we
>> are, perhaps add a note about it to the release notes. It is fairly simple
>> (Press F5 and check nomodeset).
>>
>> - If we are not going to release with a problem like this, what can I do
>> to help tackle this problem? Is there some bug in the detection tools
>> perhaps?
>>
>> - Also consider to not release with FGLRX preinstalled at all?
>>
>> Cheers.
>>
>>
>>
>>
>

Re: [sabayon-dev] fglrx with latest Live iso (August 1st 2013 taken from rsync)

[Joost Ruis]

A quick followup on this, testing on my 2nd ATI/AMD system:

01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
RV770 [Radeon HD 4850]

In this case KMS also kicks in, but now the FOSS driver is being used it
seems, all is well.


On Fri, Aug 2, 2013 at 5:22 PM, Joost Ruis  wrote:

> Hi all,
>
> I tested the latest amd64 MATE daily iso.
> On all Intel graphics systems there was no issue, but on my AMD/ATI PC
> there was.
>
> I had to explicitly set nomodeset on boot in order to get it running.
> Without that KMS kicks in and the system freezes up.
>
> The system has this card:
> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
> Cypress PRO [Radeon HD 5850]
>
> - If we are going to release the next release like this, and I guess we
> are, perhaps add a note about it to the release notes. It is fairly simple
> (Press F5 and check nomodeset).
>
> - If we are not going to release with a problem like this, what can I do
> to help tackle this problem? Is there some bug in the detection tools
> perhaps?
>
> - Also consider to not release with FGLRX preinstalled at all?
>
> Cheers.
>
>
>
>

[sabayon-dev] fglrx with latest Live iso (August 1st 2013 taken from rsync)

[Joost Ruis]

Hi all,

I tested the latest amd64 MATE daily iso.
On all Intel graphics systems there was no issue, but on my AMD/ATI PC
there was.

I had to explicitly set nomodeset on boot in order to get it running.
Without that KMS kicks in and the system freezes up.

The system has this card:
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
Cypress PRO [Radeon HD 5850]

- If we are going to release the next release like this, and I guess we
are, perhaps add a note about it to the release notes. It is fairly simple
(Press F5 and check nomodeset).

- If we are not going to release with a problem like this, what can I do to
help tackle this problem? Is there some bug in the detection tools perhaps?

- Also consider to not release with FGLRX preinstalled at all?

Cheers.

Re: [sabayon-dev] armv6 Raspberry Pi image

[Joost Ruis]

Ok today I tried the latest Image and:

- I can now use network directly on the first run, great!
- The keyboard issue I had could indeed have todo with the USB keyboard i
used (it has backlight and stuff) Using a more simple USB keyboard no
issues.
- screen -ls is now clean!

There still remains a tiny issue, on each package install I get warns about
having 2 make.conf files.

I noticed I have /etc/make.conf AND /etc/portage/make.conf, here is the diff

localhost ~ # diff -Nurp /etc/make.conf /etc/portage/make.conf
--- /etc/make.conf  2013-06-20 12:29:47.0 +
+++ /etc/portage/make.conf  2013-05-28 16:46:57.0 +
@@ -12,23 +12,24 @@ MAKEOPTS="-j6 -s"
 CCACHE_SIZE="5G"
 CCACHE_DIR="/var/ccache"
 # Global USE flags
-USE="cpudetection cups goom joystick jpeg png theora truetype xvid"
+USE="cpudetection cups goom joystick theora truetype xvid"
 # Sound USE flags
 USE="${USE} pulseaudio alsa flac mp3 vorbis ogg"
 # System USE flags
-USE="${USE} dbus introspection logind perl policykit python systemd
threads udev xattr"
+USE="${USE} dbus introspection logind policykit systemd threads xattr"
 # Video OpenGL stuff
 # Note: GLES2 is disabled globally atm. mesa-9.1.2 has bugs if both gl,
and gles2 are enabled.
 # The bug is in the GL{ES2,} headers (name clash), and gnome-shell fails
to build because of that.
 USE="${USE} -gles2"

-LINGUAS="en en_US af ar az bg bn br bs ca cs cy da de el en_GB eo es et eu
fa fi fr"
-LINGUAS="${LINGUAS} fy ga gl he hi hr hu is it ja kk km ko lt lv mk mn ms
nb nds nl"
-LINGUAS="${LINGUAS} nn pa pl pt pt_BR ro ru rw se sk sl sr sr@Latn ss sv
ta tg tr uk"
-LINGUAS="${LINGUAS} uz vi zh_CN zh_TW es_AR es_ES fy_NL ga_IE gu gu_IN
nb_NO nn_NO pt_PT sv_SE zh"
-
 # distcc configuration
-DISTCC_HOSTS="localhost/1 172.16.255.1/5"
+# DISTCC_SSH="/etc/distcc/distcc-ssh"
+# /
+# Works with QEMU warnings (damn)
+# DISTCC_HOSTS="localhost/1 distcc@localhost/15,lzo,cpp"
+# Works
+# DISTCC_HOSTS="localhost/1 127.0.0.1/15,lzo,cpp"
+DISTCC_HOSTS="localhost/1 192.168.1.2/8"
 # DISTCC_VERBOSE=1

 # Package specific configuration


On Wed, Jun 19, 2013 at 3:16 PM, Alessandro Renzi wrote:

> > When working on the Pi directly using my USB keyboard, the key stroke
> > registration seems a bit messy. Sometimes I lack some chars, sometimes
> some
> > keystroke seems to hang and spits a zillion chars on my shell. Not sure
> why
> > that happens yet. (Running a "reset" command didn't cure it either)
>
> I had the same behavior on my desktop pc when the signal of the wireless
> keyboard was too low.
> What is the max current of your power supply?
>
>
> 2013/6/19 Fabio Erculiani 
>
>> On Wed, Jun 19, 2013 at 12:05 AM, Joost Ruis 
>> wrote:
>> > Hi list.
>> >
>> > I grabbed the Pi image from a mirror, put it on a SD and here are my
>> > findings.
>> >
>> > Once I got the network going (using ifconfig..) I ran equo update and
>> > decided to install networkmanager. While installing on each package I
>> get
>> > this message:
>> >
>> > !!! Found 2 make.conf files, using both '/etc/make.conf' and
>> > '/etc/portage/make.conf'
>>
>> Fixed. NetworkManager is installed by default now.
>>
>> >
>> > -
>> >
>> > I noticed there was a dead screen session left behind, just a minor
>> issue
>> > ofcourse.
>> >
>> > localhost ~ # screen -ls
>> > There is a screen on:
>> > 25362.pts-7.armbuild(Dead ???)
>>
>> Fixed.
>>
>> >
>> > -
>> >
>> > When working on the Pi directly using my USB keyboard, the key stroke
>> > registration seems a bit messy. Sometimes I lack some chars, sometimes
>> some
>> > keystroke seems to hang and spits a zillion chars on my shell. Not sure
>> why
>> > that happens yet. (Running a "reset" command didn't cure it either)
>>
>> Maybe you're missing a bit more power on the USB.
>>
>> >
>> > ---
>> >
>> > Overall not bad for an initial release, well done Fabio!
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Fabio Erculiani
>>
>>
>
>
>
>

[sabayon-dev] armv6 Raspberry Pi image

[Joost Ruis]

Hi list.

I grabbed the Pi image from a mirror, put it on a SD and here are my
findings.

Once I got the network going (using ifconfig..) I ran equo update and
decided to install networkmanager. While installing on each package I get
this message:

!!! Found 2 make.conf files, using both '/etc/make.conf' and
'/etc/portage/make.conf'

-

I noticed there was a dead screen session left behind, just a minor issue
ofcourse.

localhost ~ # screen -ls
There is a screen on:
25362.pts-7.armbuild(Dead ???)

-

When working on the Pi directly using my USB keyboard, the key stroke
registration seems a bit messy. Sometimes I lack some chars, sometimes some
keystroke seems to hang and spits a zillion chars on my shell. Not sure why
that happens yet. (Running a "reset" command didn't cure it either)

---

Overall not bad for an initial release, well done Fabio!

[sabayon-dev] Drop i810 support from kernel?

[Joost Ruis]

xbox-360 src # cat /proc/config.gz | gunzip | grep 810
CONFIG_DRM_I810=y

I wonder if we could set this to "m"

I think it prevents this message at boot:
May 14 20:04:59 sabayon kernel: drm/i810 does not support SMP

At least on my systems (all of them) this message causes an annoying screen
flicker at boot.

I might be totally wrong here, but after some short research I came to
believe that this is only needed for very old systems.

http://en.wikipedia.org/wiki/Intel_810

Re: [sabayon-dev] recent limbo update broke lightdm

[Joost Ruis]

Oops nevermind.

Issue caused by eselect opengl set to xorg-X11 instead of ati.
(Wonder why that happened though)




On Fri, May 3, 2013 at 8:22 PM, Joost Ruis  wrote:

> journalctl -b
>
> https://pastebin.sabayon.org/pastie/12572
>

[sabayon-dev] recent limbo update broke lightdm

[Joost Ruis]

journalctl -b

https://pastebin.sabayon.org/pastie/12572

[sabayon-dev] sys-kernel/linux-server-3.8.5 on daily builds

[Joost Ruis]

Something must be pulling in sys-kernel/linux-server-3.8.5

Also noticed it on my system being present and here too:

https://forum.sabayon.org/viewtopic.php?f=57&t=29554&p=161406&hilit=&sid=76b0c31a2e42c442806c79221adfd1b7#p161406

And on my very own laptop I never noticed it but:
sabayon joost # uname -a
Linux sabayon 3.8.0-server #1 SMP Fri Mar 29 13:28:38 UTC 2013 x86_64
Intel(R) Core(TM)2 Duo CPU T6570 @ 2.10GHz GenuineIntel GNU/Linux

Re: [sabayon-dev] Observations with latest

[Joost Ruis]

If correct Fabio fixed this just yesterday.


On Fri, Apr 12, 2013 at 11:41 AM, Wolfden  wrote:

> I took last live build of Sabayon Forensics x86_64, added limbo and
> installed MATE 1.6 to see how well it worked.  I know limbo is testing now,
> just want to point out something
>
> equo install @mate
>
> At the installation of app-admin/eselect-sysvinit, sys-fs/udev is
> uninstalled.  A equo deptest pulls it back.
>
> After install and deptest, MATE loads fine, but checking
>
> sabayonx86-64 sabayonuser # eselect settingsd list
> Available settingsd implementations:
>   [1]   systemd
> sabayonx86-64 sabayonuser # eselect sysvinit list
> Available sysvinit implementations:
>   [1]   systemd
> sabayonx86-64 sabayonuser #
>
> I see joost posted:
> xbox-360 joost # eselect sysvinit list
> Available sysvinit implementations:
>   [1]   systemd *
>   [2]   sysvinit
>
> Seems I missing sysvinit option.  Not sure if this is relevant, just
> wanted to bring it up is all.
>
> Oh yea, like mva in irc I hit http://paste.pirate-party.ru/1b84ebc2.txt with
> installation of sys-apps/systemd.  Entropy log attached for reference
>
> --
> KJS
> ~wolfden~
>
>
>
>

Re: [sabayon-dev] NetworkManager script

[Joost Ruis]

The result is that now NOTHING auto mounts.
You have to toss in a mount -a on each boot (or on each IP renewal).

Not sure if https://bugs.sabayon.org/show_bug.cgi?id=4008 actually
fixes a problem here.

On Tue, Mar 26, 2013 at 9:14 AM, Fabio Erculiani  wrote:
> No, see git log
>
>
>
>

Re: [sabayon-dev] NetworkManager script

[Joost Ruis]

this:

http://git.sabayon.org/overlays/sabayon.git/diff/net-misc/networkmanager/files/01-netmount-up-down.rc?id=dd9a3f4fd747a27c4fe12d6270f5bdb26719b223

On Tue, Mar 26, 2013 at 8:59 AM, Joost Ruis  wrote:
> We used to have a script in /etc/NetworkManager/dispatcher.d that took
> care of networkmounts on connect.
> Since NM got "cleaned && bumped" on overlay this script is missing in action.
>
> Please add it back!

[sabayon-dev] NetworkManager script

[Joost Ruis]

We used to have a script in /etc/NetworkManager/dispatcher.d that took
care of networkmounts on connect.
Since NM got "cleaned && bumped" on overlay this script is missing in action.

Please add it back!