Re: [sabayon-dev] GCC-5.x Migration
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 <joost.r...@sabayon.org> 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 <joost.r...@sabayon.org> 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 <piroisl...@gmail.com> >>>> 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 <gea...@gmail.com> 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 <gea...@gmail.com> 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" <mitch.har...@sabayonlinux.org> >>>>>> 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 >> >> >> >> >> > > > > -- Fabio Erculiani
Re: [sabayon-dev] GCC-5.x Migration
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 <piroisl...@gmail.com> 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 <gea...@gmail.com> 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 <gea...@gmail.com> 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" <mitch.har...@sabayonlinux.org> >> 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] Anaconda - python breakage?
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 <piroisl...@gmail.com> 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] ZFS support on ISO image
It boils down to the fact that you cannot have two packages on a system
that own, say, /lib/foobar.so.1 -- which is what you get if you want to
provide external drivers for multiple kernels.
On Thu, Nov 24, 2016 at 11:58 PM, Francesco Ferretti <skullbo...@sabayon.org
> wrote:
> But here the point is that even upstream in portage zfs is split in two
> packages and the difference between our zfs-kmod and the Gentoo one is only
> that we install zfs-kmod and spl using the same ebuild. So could this
> create any mess in our chroot?
>
> And about nvidia, why using the upstream version without split could lead
> us to a maintenance mess? I'm really curious about this because I cant
> understand well why that split is there.
>
> On Thu, Nov 24, 2016 at 10:53 PM Fabio Erculiani <
> fabio.erculi...@gmail.com> wrote:
>
>> The problem is not really between zfs-kmod and spl, but between zfs and
>> zfs-kmod. zfs in fact is also shipping userspace tools, and you cannot
>> really make it work across multiple kernels without separating the
>> userspace part (zfs in our case) from the kernel module part (zfs-kmod). In
>> our build chroot we support several kernels at the same time, so merging
>> the two packages together is just going to create a wonderful maintenance
>> mess. This is the same reason why we have nvidia-drivers and
>> nvidia-userspace.
>>
>> Furthermore, having these separate packages allows us to support, even on
>> the user systems' side, multiple kernels at the same time, thus a smoother
>> upgrade path from an older kernel to the new one, because you can have the
>> pkg installed for the old and new kernel.
>>
>> Remember that there is usually a reason why certain decisions were made
>> in the past, but you need to ask or dig a little bit here and there.
>>
>> On Thu, Nov 24, 2016 at 3:02 PM, Francesco Ferretti <
>> skullbo...@sabayon.org> wrote:
>>
>> Ok I bumped our zfs-kmod fork to the last version available on portage
>> and injected it for every kernel versions we ship, let me know if all works
>> for you.
>> However I agree with Ben about the fact that if you are using zfs, you're
>> enough expert to manage the zfs, zfs-kmod, spl package version
>> consistency.
>>
>> About versions of zfs, I currently compiled the gentoo version of the
>> ebuild since practically don't have difference between our version and the
>> upstream one as you can see from the following diff:
>> --- /var/lib/layman/sabayon/sys-fs/zfs/zfs-0.6.5.6.ebuild 2016-05-05
>> 19:50:38.300440904 +0200
>> +++ /usr/portage/sys-fs/zfs/zfs-0.6.5.6.ebuild 2016-11-06
>> 05:00:39.0 +0100
>> @@ -3,7 +3,7 @@
>> # $Id$
>>
>> EAPI="5"
>> -PYTHON_COMPAT=( python{2_7,3_3,3_4,3_5} )
>> +PYTHON_COMPAT=( python{2_7,3_4,3_5} )
>>
>> if [ ${PV} == "" ] ; then
>> inherit git-r3 linux-mod
>> @@ -11,7 +11,7 @@ if [ ${PV} == "" ] ; then
>> EGIT_REPO_URI="git://github.com/zfsonlinux/${PN}.git
>> <http://github.com/zfsonlinux/$%7BPN%7D.git>"
>> else
>> SRC_URI="https://github.com/zfsonlinux/${PN}/releases/
>> download/${P}/${P}.tar.gz"
>> - KEYWORDS="~amd64"
>> + KEYWORDS=" ~amd64"
>> fi
>>
>> inherit autotools-utils bash-completion-r1 flag-o-matic linux-info
>> python-r1 systemd toolchain-funcs udev
>>
>> If it's ok I will drop at least this atom from our for-gentoo overlay.
>>
>> On Fri, Nov 18, 2016 at 11:16 AM Ben Roberts <opti...@sabayonlinux.org>
>> wrote:
>>
>> We had a conversation about this in IRC the other week. 0.6.5.8 is in the
>> portage tree but not yet marked as stable. There's also maintenance
>> overhead because the sabayon ebuild is forked and merges the gentoo spl
>> package into the zfs binary package. I don't know who currently maintains
>> this.
>>
>> I think the reason for the split was to make it easier to install, but
>> IMHO anyone using zfs is probably tech savvy enough to manage the zfs,
>> zfs-kmod, spl package version consistency, so to get faster updates we
>> should could drop the split and take upstreams ebuilds as-is, if possible.
>>
>> I'm also using zfs extensively and my file server is stuck running 4.4
>> LTS as a result, so I too would like to see faster updates.
>>
>> Whether or not to ship upstream unstable zfs versions is another matter.
>> If we are to use upstream ebuilds, we can try adding the newest versions to
>> the SCR.
>>
>> On 18 Nov 2016 9:41 am, &qu
Re: [sabayon-dev] ZFS support on ISO image
Too late, I'd like to see same-day patch releases. On Fri, Nov 18, 2016 at 10:37 AM, Geaaru <gea...@gmail.com> wrote: > Yes, I agree. But I think that will be always a delay between zfs and > kernel until zfs will be integrate inside vanilla kernel if this will be > possible. > > I see now that v.0.6.5.8 support kernel 4.8. > > Thanks > G. > > On Fri, 2016-11-18 at 10:26 +0100, Fabio Erculiani wrote: > > I would rather like to see the ZFS On Linux people keeping up with kernel > releases. > > On Fri, Nov 18, 2016 at 10:19 AM, Geaaru <gea...@gmail.com> wrote: > > Hi guys, > > I just used last sabayon ISO image (Gnome) to recover a server but I > see that use kernel-4.8 where currently doesn't support ZFS. > > So, could be possible create ISO image with last kernel (4.8) and a > kernel with ZFS support (like 4.4.x)? From boot menu I can then select > eventually a kernel with ZFS support. > > Is ISO image it is used for recover disaster or broken filesystem could > be helpful have ZFS support inside ISO image? > > WDYT ? > > Thanks in advance for any comments. > > Bye > G. > > > > > > -- > Fabio Erculiani > > > > > -- Fabio Erculiani
Re: [sabayon-dev] ZFS support on ISO image
I would rather like to see the ZFS On Linux people keeping up with kernel releases. On Fri, Nov 18, 2016 at 10:19 AM, Geaaru <gea...@gmail.com> wrote: > Hi guys, > > I just used last sabayon ISO image (Gnome) to recover a server but I > see that use kernel-4.8 where currently doesn't support ZFS. > > So, could be possible create ISO image with last kernel (4.8) and a > kernel with ZFS support (like 4.4.x)? From boot menu I can then select > eventually a kernel with ZFS support. > > Is ISO image it is used for recover disaster or broken filesystem could > be helpful have ZFS support inside ISO image? > > WDYT ? > > Thanks in advance for any comments. > > Bye > G. > > -- Fabio Erculiani
Re: [sabayon-dev] Wiki Broke When Requesting New Account
Fixed, thanks for reporting. On Wed, Aug 24, 2016 at 7:39 PM, Drew Kelling <akell...@gmail.com> wrote: > Greetings, > > There seems to be an issue with the Wiki when you try to Request Account. > Below is the the error she spits out. > > *Catchable fatal error*: Argument 1 passed to ReCaptcha::getForm() must > be an instance of OutputPage, none given, called in > /sabayon/git_ro/infra/server/www.sabayon.org/image/sabayon. > www/wiki.sabayon.org/extensions/ConfirmAccount/ > frontend/specialpages/actions/RequestAccount_body.php on line 231 and > defined > in*/sabayon/git_ro/infra/server/www.sabayon.org/image/sabayon.www/wiki.sabayon.org/extensions/ConfirmEdit/ReCaptcha/ReCaptcha.class.php > <http://www.sabayon.org/image/sabayon.www/wiki.sabayon.org/extensions/ConfirmEdit/ReCaptcha/ReCaptcha.class.php>* > on line *12* > > Thanks, > Andrew > > > > -- Fabio Erculiani
Re: [sabayon-dev] ISO testing - Release blockers
Ettore, can you try to reproduce the issue by removing str() in /usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py at line 2633 ? On Thu, Aug 18, 2016 at 12:55 PM, Ettore Di Giacinto < mud...@sabayonlinux.org> wrote: > 2016-08-18: Custom partitioning / Install View, installation breaks with > https://pastebin.sabayon.org/pastie/17866 when clicking on the Yellow bar > on the bottom > > Il giorno lun 15 ago 2016 alle ore 11:12 sabayonino <sabayon...@gmail.com> > ha scritto: > >> >> >> > That's odd, can you list your system HW specs? >> I attached cookbug report in my previous message :) >> >> >> >> > Is that a skylake cpu? It is known to have issues, should be fixed >> > with 4.8 kernel >> No it isn't. It's a broadwell laptop with HD Graphics 5500 + Nvidia >> Geforce 920M >> >> I've a skylake cpu to another pc-desktop no tested yet :D >> >> Both video cards are recognized and work >> >> http://www.notebookcheck.it/Intel-HD-Graphics-5500.138189.0.html >> (Italian) >> http://laptoping.com/gpus/product/intel-hd-5500- >> graphics-reviews-and-specs/ >> >> see lspci and lshw attachment >> >> >> According with gentoo wiki https://wiki.gentoo.org/wiki/Intel >> HD5500 drivers should be i965 instead i915 >> >> VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) >> Subsystem: Lenovo HD Graphics 5500 >> Kernel driver in use: i915 >> Kernel modules: i915 >> >> Regards >> >> >> >> >> >> >> >> >> -- > > Regards, > Ettore Di Giacinto - Sabayon Project Lead > > > > > -- Fabio Erculiani
Re: [sabayon-dev] Some release blockers
Fixed: commit c54438859af767f51e1677990ccd3b9fceac675e Author: Fabio Erculiani <lx...@sabayon.org> Date: Fri Aug 12 22:58:13 2016 +0200 Decode the bytestring coming from pwquality to unicode before using it. diff --git a/pyanaconda/ui/gui/spokes/lib/passphrase.py b/pyanaconda/ui/gui/spokes/lib/passphrase.py index c104194..377f6ed 100644 --- a/pyanaconda/ui/gui/spokes/lib/passphrase.py +++ b/pyanaconda/ui/gui/spokes/lib/passphrase.py @@ -21,6 +21,7 @@ from gi.repository import Gtk +import locale import pwquality from pyanaconda.ui.helpers import InputCheck @@ -118,7 +119,7 @@ class PassphraseDialog(GUIObject, GUIInputCheckHandler): try: strength = self._pwq.check(passphrase, None, None) except pwquality.PWQError as e: -self._pwq_error = e.args[1] +self._pwq_error = e.args[1].decode(locale.nl_langinfo(locale.CODESET)) if strength < 50: val = 1 On Thu, Aug 11, 2016 at 2:25 PM, Ettore Di Giacinto <mud...@sabayonlinux.org > wrote: > Ok, that fixed the specific issue. I tested today the KDE-dev (2016-08-10) > and i got another new issue (but it is the same bug looking at the > stacktrace): > I selected Manual partitioning -> checked encryption, and it appeared the > window asking the encryption password, but as soon as i start typing few > character, the bug window appear: > > stacktrace: https://pastebin.sabayon.org/pastie/17854 > > screenshot: https://pastebin.sabayon.org/pastie/17855 > > > > > Il giorno dom 7 ago 2016 alle ore 17:36 Fabio Erculiani < > fabio.erculi...@gmail.com> ha scritto: > >> Pushed commit d36eca97f529cad6ed98020cd8f80a8863eab9ef which should fix >> the unicode issue >> >> On Sat, Aug 6, 2016 at 10:10 PM, Fabio Erculiani < >> fabio.erculi...@gmail.com> wrote: >> >>> I'll take a look asap, sounds like the typical utf-8 issues with Python. >>> >>> On Fri, Aug 5, 2016 at 3:53 PM, Ettore Di Giacinto < >>> mud...@sabayonlinux.org> wrote: >>> >>>> KDE-dev 2016-08-04: >>>> >>>> Selected IT language from boot. >>>> After boot, double-clicked on the icon on the desktop, the anconda >>>> screen was black for a long time, then i minimized-maximixed the windows, >>>> and the anaconda bug report window showed up with this content: >>>> https://pastebin.sabayon.org/pastie/17838, couldn't install so far (in >>>> a virtualbox instance). Locales was there, tried also to regenerate them >>>> on-place but didn't worked. Screen: https://pastebin. >>>> sabayon.org/pastie/17839 >>>> >>>> >>>> Il giorno ven 5 ago 2016 alle ore 08:34 Joost Ruis < >>>> joost.r...@sabayon.org> ha scritto: >>>> >>>>> +1 for creating a (well designed!) welcome screen. >>>>> >>>>> On Fri, Aug 5, 2016 at 12:50 AM, Francesco Ferretti < >>>>> skullbo...@sabayon.org> 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 <joost.r...@sabayon.org> >>>>>> 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 aga
Re: [sabayon-dev] Latest Mate DEV : 02locale is not set properly
That file should be a symlink to locale.conf: ~ $ file /etc/env.d/02locale /etc/env.d/02locale: symbolic link to ../locale.conf It looks like there have been attempts to remove these two files (especially the symlink) from the images. I do not understand why. I should have fixed it now in the buld scripts: commit 53a0ab8f48d50bc1f923cd240d343d766182bbe2 Author: Fabio Erculiani <lx...@sabayon.org> Date: Fri Aug 12 22:33:34 2016 +0200 [scripts] make sure to only write /etc/locale.conf and force 02locale as symlink. This fixes locale config after install. commit fadf05624a1c6149a09977a06bb22f46b70261af Author: Fabio Erculiani <lx...@sabayon.org> Date: Fri Aug 12 22:28:53 2016 +0200 Do not remove /etc/locale.conf and /etc/env.d/02locale WE NEED THEM! ESPECIALLY THE 02locale SYMLINK! On Fri, Aug 12, 2016 at 6:27 PM, sabayonino <sabayon...@gmail.com> wrote: > Hi, another issue for MATE DEV (I think for all ISO's) > > Installation was fine but language was not set properly > > During installation I choosed Italian language. > > System has kept US-English language > > localectl is set to it_IT UTF-8 (ok) > > but /etc/env.d/02locale is set to: > LANG=us_US.UTF-8 > LANGUAGE=us_US.UTF-8 > LC_ALL=us_US.UTF-8 > > > solved with : > LANG=it_IT.UTF-8 > LANGUAGE=it_IT.UTF-8 > LC_ALL=it_IT.UTF-8 > > > cheers :) > > > -- Fabio Erculiani
Re: [sabayon-dev] Fwd: KDE Daily Build Broken: Sabayon20160728
Well, the attached logs report the same issue that you reported before and that I already fixed. How does that look better then? On Mon, Aug 1, 2016 at 6:05 PM, Drew Kelling <akell...@gmail.com> wrote: > Looks better on the KDE end but still having issues with Anaconda crashing > as soon as I click the Install Icon on the desktop. I have attached all the > logs that where in /tmp. > > On Sun, Jul 31, 2016 at 11:58 PM, Fabio Erculiani < > fabio.erculi...@gmail.com> wrote: > >> Fixed in git: >> >> commit 2639d6f42b8a04fee057ff6f3bf4ed67cbd14d86 >> Author: Fabio Erculiani <lx...@sabayon.org> >> Date: Mon Aug 1 07:58:12 2016 +0200 >> >> Fix startup with KDE 5, drop KDE 4 support. >> >> >> On Mon, Aug 1, 2016 at 7:40 AM, Fabio Erculiani < >> fabio.erculi...@gmail.com> wrote: >> >>> Or the Sabayon payload does not load, can you attach here all the >>> /tmp/*.log files after the anaconda crash? >>> >>> On Mon, Aug 1, 2016 at 7:36 AM, Fabio Erculiani < >>> fabio.erculi...@gmail.com> wrote: >>> >>>> Hi Drew, >>>> how do you start anaconda? >>>> >>>> You are hitting an unsupported codepath, I guess that you're calling >>>> anaconda directly? (thus without the correct args) >>>> >>>> On Mon, Aug 1, 2016 at 12:08 AM, Drew Kelling <akell...@gmail.com> >>>> wrote: >>>> >>>>> >>>>> -- Forwarded message - >>>>> From: Drew Kelling <akell...@gmail.com> >>>>> Date: Thu, Jul 28, 2016 at 15:12 >>>>> Subject: KDE Daily Build Broken: Sabayon20160728 >>>>> To: sabayon-dev <devel@lists.sabayon.org> >>>>> >>>>> >>>>> Hi all, >>>>> >>>>> I am getting the following errors trying to install from the daily >>>>> build of KDE(Sabayon20160728) >>>>> >>>>> I am seeing in issue on initial load of the iso where KDE just loads >>>>> into a black screen on today's build. Which I did not see on release a few >>>>> days ago. A quick restart of lightdm does correct this issue though. >>>>> >>>>> I am seeing the following error from Anaconda on both builds: >>>>> Traceback (most recent call last): >>>>> File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", >>>>> line 244, in run >>>>> threading.Thread.run(self, *args, **kwargs) >>>>> File "/usr/lib64/python2.7/threading.py", line 763, in run >>>>> self.__target(*self.__args, **self.__kwargs) >>>>> File >>>>> "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", >>>>> line 1233, in _runThread >>>>> payload.setup(storage, instClass) >>>>> File >>>>> "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", >>>>> line 78, in setup >>>>> if not stat.S_ISBLK(os.stat(osimg.path)[stat.ST_MODE]): >>>>> AttributeError: 'NoneType' object has no attribute 'path' >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Fabio Erculiani >>>> >>> >>> >>> >>> -- >>> Fabio Erculiani >>> >> >> >> >> -- >> Fabio Erculiani >> >> >> >> > > > > -- Fabio Erculiani
Re: [sabayon-dev] Fwd: KDE Daily Build Broken: Sabayon20160728
I just fixed the unicode issue. About the text install, it actually tells you that you did not complete all steps. On Sat, Aug 6, 2016 at 2:16 PM, sabayonino <sabayon...@gmail.com> wrote: > I send a prev bug report but it is waiting for devs approval :O > > > > So I tried to update anaconda from live environment (latest MATE DAILY > > version) > > Install was successfully. > > > > I tried again new installation with the same steps but something's wrong > > > > Anaconda Welcome message was broken. > > http://imageshack.com/a/img924/6841/6sPusr.png > > > > Tried to update anaconda . No install now. > > > > I tried "anaconda -C" (text-installer) also . It crashed > > > > See log attachments. > > > > (No virtualbox) > > > > Tnx :) > > > > -- Fabio Erculiani
Re: [sabayon-dev] Some release blockers
Pushed commit d36eca97f529cad6ed98020cd8f80a8863eab9ef which should fix the unicode issue On Sat, Aug 6, 2016 at 10:10 PM, Fabio Erculiani <fabio.erculi...@gmail.com> wrote: > I'll take a look asap, sounds like the typical utf-8 issues with Python. > > On Fri, Aug 5, 2016 at 3:53 PM, Ettore Di Giacinto < > mud...@sabayonlinux.org> wrote: > >> KDE-dev 2016-08-04: >> >> Selected IT language from boot. >> After boot, double-clicked on the icon on the desktop, the anconda screen >> was black for a long time, then i minimized-maximixed the windows, and the >> anaconda bug report window showed up with this content: >> https://pastebin.sabayon.org/pastie/17838, couldn't install so far (in a >> virtualbox instance). Locales was there, tried also to regenerate them >> on-place but didn't worked. Screen: https://pastebin.sabay >> on.org/pastie/17839 >> >> >> Il giorno ven 5 ago 2016 alle ore 08:34 Joost Ruis < >> joost.r...@sabayon.org> ha scritto: >> >>> +1 for creating a (well designed!) welcome screen. >>> >>> On Fri, Aug 5, 2016 at 12:50 AM, Francesco Ferretti < >>> skullbo...@sabayon.org> 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 <joost.r...@sabayon.org> >>>> 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 <joost.r...@sabayon.org> 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 < >>>>>>>> mud...@sabayonlinux.org> 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
Re: [sabayon-dev] Some release blockers
I'll take a look asap, sounds like the typical utf-8 issues with Python. On Fri, Aug 5, 2016 at 3:53 PM, Ettore Di Giacinto <mud...@sabayonlinux.org> wrote: > KDE-dev 2016-08-04: > > Selected IT language from boot. > After boot, double-clicked on the icon on the desktop, the anconda screen > was black for a long time, then i minimized-maximixed the windows, and the > anaconda bug report window showed up with this content: > https://pastebin.sabayon.org/pastie/17838, couldn't install so far (in a > virtualbox instance). Locales was there, tried also to regenerate them > on-place but didn't worked. Screen: https://pastebin. > sabayon.org/pastie/17839 > > > Il giorno ven 5 ago 2016 alle ore 08:34 Joost Ruis <joost.r...@sabayon.org> > ha scritto: > >> +1 for creating a (well designed!) welcome screen. >> >> On Fri, Aug 5, 2016 at 12:50 AM, Francesco Ferretti < >> skullbo...@sabayon.org> 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 <joost.r...@sabayon.org> >>> 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 <joost.r...@sabayon.org> 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 <mud...@sabayonlinux.org> >>>>>>> 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). >>>>>>>>
[sabayon-dev] Some release blockers
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
Re: [sabayon-dev] Fwd: KDE Daily Build Broken: Sabayon20160728
Fixed in git: commit 2639d6f42b8a04fee057ff6f3bf4ed67cbd14d86 Author: Fabio Erculiani <lx...@sabayon.org> Date: Mon Aug 1 07:58:12 2016 +0200 Fix startup with KDE 5, drop KDE 4 support. On Mon, Aug 1, 2016 at 7:40 AM, Fabio Erculiani <fabio.erculi...@gmail.com> wrote: > Or the Sabayon payload does not load, can you attach here all the > /tmp/*.log files after the anaconda crash? > > On Mon, Aug 1, 2016 at 7:36 AM, Fabio Erculiani <fabio.erculi...@gmail.com > > wrote: > >> Hi Drew, >> how do you start anaconda? >> >> You are hitting an unsupported codepath, I guess that you're calling >> anaconda directly? (thus without the correct args) >> >> On Mon, Aug 1, 2016 at 12:08 AM, Drew Kelling <akell...@gmail.com> wrote: >> >>> >>> -- Forwarded message - >>> From: Drew Kelling <akell...@gmail.com> >>> Date: Thu, Jul 28, 2016 at 15:12 >>> Subject: KDE Daily Build Broken: Sabayon20160728 >>> To: sabayon-dev <devel@lists.sabayon.org> >>> >>> >>> Hi all, >>> >>> I am getting the following errors trying to install from the daily build >>> of KDE(Sabayon20160728) >>> >>> I am seeing in issue on initial load of the iso where KDE just loads >>> into a black screen on today's build. Which I did not see on release a few >>> days ago. A quick restart of lightdm does correct this issue though. >>> >>> I am seeing the following error from Anaconda on both builds: >>> Traceback (most recent call last): >>> File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line >>> 244, in run >>> threading.Thread.run(self, *args, **kwargs) >>> File "/usr/lib64/python2.7/threading.py", line 763, in run >>> self.__target(*self.__args, **self.__kwargs) >>> File >>> "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line >>> 1233, in _runThread >>> payload.setup(storage, instClass) >>> File >>> "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", >>> line 78, in setup >>> if not stat.S_ISBLK(os.stat(osimg.path)[stat.ST_MODE]): >>> AttributeError: 'NoneType' object has no attribute 'path' >>> >>> >>> >>> >>> >>> >>> >> >> >> -- >> Fabio Erculiani >> > > > > -- > Fabio Erculiani > -- Fabio Erculiani
Re: [sabayon-dev] Fwd: KDE Daily Build Broken: Sabayon20160728
Or the Sabayon payload does not load, can you attach here all the /tmp/*.log files after the anaconda crash? On Mon, Aug 1, 2016 at 7:36 AM, Fabio Erculiani <fabio.erculi...@gmail.com> wrote: > Hi Drew, > how do you start anaconda? > > You are hitting an unsupported codepath, I guess that you're calling > anaconda directly? (thus without the correct args) > > On Mon, Aug 1, 2016 at 12:08 AM, Drew Kelling <akell...@gmail.com> wrote: > >> >> -- Forwarded message - >> From: Drew Kelling <akell...@gmail.com> >> Date: Thu, Jul 28, 2016 at 15:12 >> Subject: KDE Daily Build Broken: Sabayon20160728 >> To: sabayon-dev <devel@lists.sabayon.org> >> >> >> Hi all, >> >> I am getting the following errors trying to install from the daily build >> of KDE(Sabayon20160728) >> >> I am seeing in issue on initial load of the iso where KDE just loads into >> a black screen on today's build. Which I did not see on release a few days >> ago. A quick restart of lightdm does correct this issue though. >> >> I am seeing the following error from Anaconda on both builds: >> Traceback (most recent call last): >> File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line >> 244, in run >> threading.Thread.run(self, *args, **kwargs) >> File "/usr/lib64/python2.7/threading.py", line 763, in run >> self.__target(*self.__args, **self.__kwargs) >> File >> "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line >> 1233, in _runThread >> payload.setup(storage, instClass) >> File >> "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", >> line 78, in setup >> if not stat.S_ISBLK(os.stat(osimg.path)[stat.ST_MODE]): >> AttributeError: 'NoneType' object has no attribute 'path' >> >> >> >> >> >> >> > > > -- > Fabio Erculiani > -- Fabio Erculiani
Re: [sabayon-dev] Fwd: KDE Daily Build Broken: Sabayon20160728
Hi Drew, how do you start anaconda? You are hitting an unsupported codepath, I guess that you're calling anaconda directly? (thus without the correct args) On Mon, Aug 1, 2016 at 12:08 AM, Drew Kelling <akell...@gmail.com> wrote: > > -- Forwarded message - > From: Drew Kelling <akell...@gmail.com> > Date: Thu, Jul 28, 2016 at 15:12 > Subject: KDE Daily Build Broken: Sabayon20160728 > To: sabayon-dev <devel@lists.sabayon.org> > > > Hi all, > > I am getting the following errors trying to install from the daily build > of KDE(Sabayon20160728) > > I am seeing in issue on initial load of the iso where KDE just loads into > a black screen on today's build. Which I did not see on release a few days > ago. A quick restart of lightdm does correct this issue though. > > I am seeing the following error from Anaconda on both builds: > Traceback (most recent call last): > File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line > 244, in run > threading.Thread.run(self, *args, **kwargs) > File "/usr/lib64/python2.7/threading.py", line 763, in run > self.__target(*self.__args, **self.__kwargs) > File > "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line > 1233, in _runThread > payload.setup(storage, instClass) > File > "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", > line 78, in setup > if not stat.S_ISBLK(os.stat(osimg.path)[stat.ST_MODE]): > AttributeError: 'NoneType' object has no attribute 'path' > > > > > > > -- Fabio Erculiani
[sabayon-dev] eselect opengl set nvidia
I had to do a manual: eselect opengl set nvidia after the installation because the current opengl setup seemed to be wonky. Are we doing this in the installer after the chroot is configured? This used to be spawned by anaconda as well. -- Fabio Erculiani
[sabayon-dev] virtual/man should be always installed
I think we should install virtual/man by default on our images. -- Fabio Erculiani
Re: [sabayon-dev] Chroot + Genkernel-next
You need to allow the chroot environment to issue mknod() syscalls. If you google a bit, it's a well known thing. Especially if you are using some kind of containerization. On Tue, Apr 21, 2015 at 7:32 PM, mudler mud...@dark-lab.net wrote: Personally i think this is an unwanted feature, but i actually don't know, in my case i felt i was doing a quick and dirty hack. Fabio, can you put some light on this? For the docs: Maybe should be documented in the wiki as caveats/hack. Il 21 aprile 2015 17:44:49 CEST, Steven Cristian stefan.crist...@best.eu.org ha scritto: Can I haz some tech details on that? And can we document it somewhere :D ? On Tue, Apr 21, 2015 at 6:41 PM, mudler mud...@dark-lab.net wrote: Yep, had similar issues, compiling the kernel from emerge. putting for debug an id call inside genkernel scripts revealed that the building process was with the portage user, so i solved allowing mknode to portage Il 21 aprile 2015 17:00:14 CEST, Steven Cristian stefan.crist...@best.eu.org ha scritto: Anyone had problems with mknod not having permission within chroot (while using genkernel-next) ? * initramfs: Initializing... * Appending base_layout cpio data... mknod: 'console': Operation not permitted * ERROR: cannot mknod * * -- Grepping log... -- -- Main OS Architect at Project RoGentos (Romanian Gentoo Operating Systems) Group. Based on Sabayon and Gentoo Linux, Kogaion GNU/Linux and Argent GNU/Linux tends to offer support mainly for all Romanian Linux users and entrepreneurs which seek to learn an open and free system based on true values :) http://rogentos.ro www.facebook.com/RogentosLinux https://plus.google.com/106559511636021124919/ Google+ -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità. -- Main OS Architect at Project RoGentos (Romanian Gentoo Operating Systems) Group. Based on Sabayon and Gentoo Linux, Kogaion GNU/Linux and Argent GNU/Linux tends to offer support mainly for all Romanian Linux users and entrepreneurs which seek to learn an open and free system based on true values :) http://rogentos.ro www.facebook.com/RogentosLinux https://plus.google.com/106559511636021124919/ Google+ -- Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità. -- Fabio Erculiani
Re: [sabayon-dev] app-admin/eselect-* - app-eselect/eselect
On Fri, Apr 3, 2015 at 8:44 PM, Joost Ruis joost.r...@sabayon.org wrote: 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. Just update the deps... Cheers! -- Fabio Erculiani
Re: [sabayon-dev] app-emulation/emul-linux*
I think it's very easy to do for *userspace ebuilds, just look at the new deps in upstream ebuilds (*drivers) and update accordingly. On Sun, Mar 8, 2015 at 12:32 PM, Joost Ruis joost.r...@sabayon.org wrote: 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 -- Fabio Erculiani
Re: [sabayon-dev] Install Error on Sabayon_Linux_DAILY_amd64_MATE-dev
I also increased the frequency of the images push from twice a week to once every two days. On Fri, Jan 23, 2015 at 7:44 AM, Fabio Erculiani lx...@sabayon.org 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 mitch.har...@sabayonlinux.org 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 module from blivet import StorageDiscoveryConfig File /usr/lib64/python2.7/site-packages/blivet/__init__.py, line 62, in module import parted File /usr/lib64/python2.7/site-packages/parted/__init__.py, line 62, in module from parted.partition import Partition File /usr/lib64/python2.7/site-packages/parted/partition.py, line 266, in module 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 module from pyanaconda import geoloc File /usr/lib64/python2.7/site-packages/pyanaconda/geoloc.py, line 109, in module from pyanaconda import network File /usr/lib64/python2.7/site-packages/pyanaconda/network.py, line 41, in module from blivet.devices import FcoeDiskDevice, iScsiDiskDevice File /usr/lib64/python2.7/site-packages/blivet/__init__.py, line 62, in module import parted File /usr/lib64/python2.7/site-packages/parted/__init__.py, line 62, in module from parted.partition import Partition File /usr/lib64/python2.7/site-packages/parted/partition.py, line 266, in module 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 module from blivet import StorageDiscoveryConfig File /usr/lib64/python2.7/site-packages/blivet/__init__.py, line 62, in module import parted File /usr/lib64/python2.7/site-packages/parted/__init__.py, line 62, in module from parted.partition import Partition File /usr/lib64/python2.7/site-packages/parted/partition.py, line 266, in module partitionFlag[__flag] = _ped.partition_flag_get_name(__flag) ValueError: Invalid flag provided. /usr/sbin/setenforce: SELinux is disabled -- Fabio Erculiani -- Fabio Erculiani
Re: [sabayon-dev] BTRFS multiple devices for root fs
--btrfs is now enabled through USE=btrfs for our kernels. I then made USE=btrfs enabled by default. This means that btrfs support will start working for real. -- Fabio Erculiani
Re: [sabayon-dev] New Sabayon daily images, with sabayon-limbo enabled will start being built
We will have both regular and dev images in the same daily/ folder. The dev images will be suffixed with -dev. On Sun, Nov 30, 2014 at 7:30 PM, Wolfden wolf...@gmail.com wrote: I assume these will be in their own folder on the mirrors than or is this replacing the Daily's? On Sun, Nov 30, 2014 at 10:14 AM, Fabio Erculiani fabio.erculi...@gmail.com wrote: Molecule (which got moved to andromeda), will start building -dev ISO images (that will be uploaded to mirrors every 3 days) for every DAILY image we currently support. Those -dev ISO images will be built with sabayon-limbo enabled. This will hopefully help us catching issues before limbo packages hit the main repo. -- Fabio Erculiani -- KJS ~wolfden~ -- Fabio Erculiani
Re: [sabayon-dev] sabayon-steambox and metacity
Any replacement window manager? Perhaps one from the XFCE land? On Fri, Nov 7, 2014 at 11:47 PM, Sławomir Nizio slawomir.ni...@sabayon.org wrote: Hi, Does app-misc/sabayon-steambox need to depend on Metacity? Metacity is being removed from Portage. -- Fabio Erculiani
Re: [sabayon-dev] equo upgrade --ask throws exception no such table: neededreference
Sorry about that, I am fixing this. In the meantime you can just do (for other repos as well): sqlite3 /var/lib/entropy/client/database/amd64/sabayonlinux.org/standard/amd64/5/packages.db 'CREATE TABLE neededreference ( idneeded INTEGER PRIMARY KEY AUTOINCREMENT, library VARCHAR );' and then update sys-apps/entropy On Mon, Oct 20, 2014 at 6:24 PM, pierigno pieri...@gmail.com wrote: hi, I'm getting the attached error log from equo upgrade --ask after a succesful equo update. also, manually install some random package works for some (xbmc, @gnome, @lxde) while not for others ( firefox, chromium). I'm running sabayon-limbo and sabayonlinux.org repositories. -- Fabio Erculiani
Re: [sabayon-dev] something like --depclean for equo
Cool! I've already one or two comments, but it does not seem to be too bad. I can review the pull request if you send one. On Fri, Sep 5, 2014 at 10:28 PM, Sławomir Nizio slawomir.ni...@sabayon.org wrote: Hello, There is 'equo unused' and it works, but I was thinking of making something that works more like emerge --depclean (if I understand correctly how it works). I have forked the git repository of Entropy and made such a change. It can be found here: https://github.com/Enlik/entropy/commits/master. [entropy.client] equo unused that works more like emerge --depclean It's more like a draft. It works, it prints packages that might be uninstalled, but several options are ignored, etc. to test: git clone…; cd client; equo unused The change is simple, but treat it as experimental (no guarantees!). I don't know the Entropy code base well (heck, I barely do), and I didn't spend much time on looking how things work, but anyway - what's important: - the dependency calculation doesn't seem to be costly! I may have oversimplified something, though; - it seems to work quite well in terms on what is printed (except that maybe spm-installed packages should be treated as installed by user). It works this way: select all packages that are marked as being installed by user, collect their dependencies recursively, and print packages that are installed but not on that collection. I am curious on what you think. Fabio: maybe you would be interested in this as well. -- Fabio Erculiani
Re: [sabayon-dev] possible change to the bug tracker
Done. The hardware field now defaults to Unspecified. On Wed, Apr 23, 2014 at 11:59 AM, Sławomir Nizio slawomir.ni...@sabayon.org wrote: Hi, Something to consider: adding unspecified to Hardware field and making it default, so it's possible to tell when someone didn't mark the architecture. I don't know if it's possible to do differently than just adding another selection. -- Fabio Erculiani
Re: [sabayon-dev] Entropy-274 : quickpkg problem
I am unable to reproduce it. Can you try to use entropy from git? # cd client/ # python equo.py pkg generate firefox It that doesn't work, you should open client/solo/commands/pkg.py, locate the _generate(self, ...): method and attach the debugger there (simplest way: add a line import pdb; pdb.set_trace()). -- Fabio Erculiani
Re: [sabayon-dev] Entropy-274 : quickpkg problem
Do you have that problem with the latest version as well?
Re: [sabayon-dev] Sabayon fails to boot after last update (Limbo)
I will fix it in a bunch of hours. I will create a compat eselect-init that deals with that case.
Re: [sabayon-dev] Sabayon fails to boot after last update (Limbo)
I should have fixed the issue in the repositories. There are now new systemd (from sabayon-distro instead of systemd-love overlay) and systemd-sysv-utils (this one blocks eselect-init). -- Fabio Erculiani
Re: [sabayon-dev] Sabayon fails to boot after last update (Limbo)
The fix was not supposed to solve the problem of already broken systems. However, reinstalling systemd-sysv-utils should always bring back a correct /sbin/init (which is a symlink). /usr/lib has always been a symlink to lib64 (and /lib is a symlink to lib64). On Wed, Mar 26, 2014 at 6:20 PM, pierigno pieri...@gmail.com wrote: still no luck. eselect-init was already removed by last update. my grub menu entry has init=/linuxrc but the error message says it cannot find valid init at /sbin/init init=/linuxrc can be safely removed (genkernel ignores it, actually). If /sbin/init is correctly configured and you don't have a separate /usr (or genkernel is correctly mounting it for you), then the problem is elsewhere and not related to the last changes implemented in systemd. After equo install systemd-sysvinit-utils-208 I get: # ls -al /sbin/init lrwxrwxrwx 1 root root 24 26 mar 13.43 /sbin/init - ../usr/lib/systemd/systemd Yes, this is correct. This leads me to believe that the problem is elsewhere. Also, I saw in your logs that you have anaconda installed on your system, this looks completely wrong, how did you get that system installed? # ls -al /usr/lib lrwxrwxrwx 1 root root 11 29 gen 2012 /usr/lib - /usr/lib64/ Maybe /usr/lib should link to ../usr/lib64 also? I don't have a virtual machine at the moment to test it though 2014-03-26 13:11 GMT+00:00 Fabio Erculiani lx...@sabayon.org: I should have fixed the issue in the repositories. There are now new systemd (from sabayon-distro instead of systemd-love overlay) and systemd-sysv-utils (this one blocks eselect-init). -- Fabio Erculiani -- Fabio Erculiani
Re: [sabayon-dev] Cinnamon question
The ebuilds are in this Gentoo overlay: https://github.com/Sabayon/for-gentoo You need to be able to deal with Gentoo ebuilds (bumping, testing, updating dependencies) maintenance. Furthermore, you need to know how to use git and how to send pull requests via GitHub. Once new ebuilds are in, packages will be bumped automatically (weekly). -- Fabio Erculiani
Re: [sabayon-dev] ModemManager1.service
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] How does equo fetch files?
Basically, because you're doing something that's not really supported (copy a snapshot of the repo and rename it). In order to support shadow repositories, like sabayon-weekly, where the only content that differ from the original sabayonlinux.org is the database/ directory, the original repository identifier from where a package comes from is recorded into the sqlite3 database itself (packages.db) the EntropyRepository.getInstalledPackageRepository() method. See https://github.com/Sabayon/entropy/blob/master/lib/entropy/client/interfaces/package.py#L547 However, it should try both the original and the current repo paths. I am not sure, but changing the product information in entropy config files (/etc/entropy), and renaming the directory remotely might be a better solution (if it works for you). -- Fabio Erculiani
Re: [sabayon-dev] This is kinda annoying
https://github.com/Sabayon/entropy/commit/594656e03d929d656a55af51314740d35d67c872 -- Fabio Erculiani
Re: [sabayon-dev] Contribution
solo is the internal name of the equo commands library. -- Fabio Erculiani
Re: [sabayon-dev] Contribution
The best way to start contributing is: 1) hang around on IRC (#sabayon-dev) 2) learn how to write ebuilds (sooner or later you will need to) 3) study Gentoo internals, we're a Gentoo based distro after all 4) mess around with stuff by cloning our github repos and sending pull requests Most of our tools are written in Python and Bash. Our default Python version is 2.7, I am not personally interested in moving to 3.x yet, even though someday in the far future it will have to happen. Maybe a good way to get familiar with one of the tools is porting and testing (including writing unit tests) our code, like for instance entropy.git (or even anaconda.git or molecule.git) to Python 3.3. -- Fabio Erculiani
Re: [sabayon-dev] Sabayon Xfce daily (7.08.2013) permissions problem
This should make it, genkernel-next.git, initramfs (hopefully):
commit 1b282a7c9fdd0423c9b6365c0a1eec2a6e34db5c
Author: Fabio Erculiani lx...@sabayon.org
Date: Sun Aug 11 10:01:00 2013 +0200
initrd.scripts: mount livecd / tmpfs with mode=0755 (instead of 0777)
diff --git a/defaults/initrd.scripts b/defaults/initrd.scripts
index 2bd86d7..1f67740 100644
--- a/defaults/initrd.scripts
+++ b/defaults/initrd.scripts
@@ -1557,7 +1557,7 @@ setup_squashfs_aufs() {
livecd_init() {
good_msg Making tmpfs for ${NEW_ROOT}
- mount -n -t tmpfs tmpfs ${NEW_ROOT}
+ mount -n -t tmpfs -o mode=0755 tmpfs ${NEW_ROOT}
local dirs=
--
Fabio Erculiani
Re: [sabayon-dev] Bumblebee + Systemd
3.10 is a work in progress. -- Fabio Erculiani
Re: [sabayon-dev] Bumblebee + Systemd
sys-power/bbswitch-0.7 will be in sabayon-limbo soon -- Fabio Erculiani
Re: [sabayon-dev] What package do i need install ? Thanks!
# equo install sabayon-sources-kernel version -- Fabio Erculiani
Re: [sabayon-dev] [systemd] reading values from /etc/conf.d/ config files.
File a bug at bugs.gentoo.org (search if a bug has been filed already, first). -- Fabio Erculiani
Re: [sabayon-dev] armv6 Raspberry Pi image
On Wed, Jun 19, 2013 at 12:05 AM, Joost Ruis joost.r...@sabayon.org 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
Re: [sabayon-dev] xfce still not booting to desktop
What ISO image are you trying? -- Fabio Erculiani
Re: [sabayon-dev] Daily XFCE boots to XDM
On Thu, Jun 6, 2013 at 9:34 AM, Andre Jaenisch andrejaeni...@googlemail.com wrote: 2013/6/5 Fabio Erculiani lx...@sabayon.org: You don't want to edit files, you want to systemctl enable lxdm and systemctl start lxdm. Is that worthy writing down in our wiki? I couldn't test systemd yet, so no experience. You can play with systemd by just downloading one of the latest daily images (or monthly 13.06). basically we have lxdm, kdm, gdm, lightdm, xdm (what else?) services. -- Fabio Erculiani
Re: [sabayon-dev] Daily XFCE boots to XDM
On Wed, Jun 5, 2013 at 9:49 AM, Wolfden wolf...@gmail.com wrote: The daily XFCE hasn't boot properly in the last 3 weeks. I figured as we switched over to systemd it would work out eventually, but posting anyway. XFCE boots up to the XMD login box, which is a weird looking box, I don't recall ever seeing this. I check the /etc/conf.d/xdm and display manager is set to xdm I believe it should be set to gdm since that is what is installed. I change to gdm than issue systemctl stop xdm systemctl status xdm and it reports it dead systemctl start xdm and I am brought back to the xdm login box, as if systemd doesn't use the /etc/conf.d/xdm file. I have no idea if it does or doesn't as I a noob to systemd. systemd does not use the braindead /etc/conf.d/xdm. So hoping to look at log files and apparently systemd don't make the log files? I can't find /var/log/messages or /var/log/dmesg A side note, I have to edit the grub line and remove all that fancy graphical commands to get display to work. If I leave the default grub line as is, my monitor goes to sleep and I can't do a thing to get it to display. ctrl alt f1 does nothing. If I remove everything starting with splash to --quiet in grub I get my display. Intel graphics - I can maybe get more info once the xdm issue is solved. What is best way to get info on the xdm issue? -- KJS ~wolfden~ -- Fabio Erculiani
Re: [sabayon-dev] Daily XFCE boots to XDM
I will have a look at this as soon as possible. I am busy until after the 6th. You don't want to edit files, you want to systemctl enable lxdm and systemctl start lxdm. -- Fabio Erculiani
Re: [sabayon-dev] root on USB no longer bootable
I will try to reproduce it and prepare a fix, if possible. -- Fabio Erculiani
Re: [sabayon-dev] root on USB no longer bootable
The new code is more aggressive but it is supposed to wait for at most 10 seconds if the root device doesn't show up immediately. Have you tried adding rootwait to the command line? (instead of scandelay=n). Also, can you remove the quiet argument from the cmdline (as well as scandelay=n) and paste here a screenshot of the boot messages? I may be able to improve the code. -- Fabio Erculiani
Re: [sabayon-dev] 13.06 ISO KDE
The cookbug is useless because when you collected it the system was booted in safe mode, thus nvidia-drivers was not configured. -- Fabio Erculiani
Re: [sabayon-dev] 13.06 ISO KDE
On Sun, Jun 2, 2013 at 10:13 PM, Danilo Pianini danilo.pian...@gmail.com wrote: Anything useful I can provide? Consider that the system hangs when booting normally, no way to use it. So I am limited to things doable within the safe env. Boot with gentoo=nox and run cookbug + gpu-configuration --dry-run If the system hangs, it means that something is really screwed. (but you may be able to ssh into it once you started sshd using gentoo=nox). -- Fabio Erculiani
Re: [sabayon-dev] Sabayon 13.04 KDE installer
Of course not. Can you try with the latest daily? I wonder if it's time to remove that boot option and have people install the distro through the desktop icon (in the case of graphical images) -- Fabio Erculiani
Re: [sabayon-dev] root on USB no longer bootable
What is your kernel boot command line? -- Fabio Erculiani
Re: [sabayon-dev] root on USB no longer bootable
I think that you did not report the error correctly and you are not probably using scandelay=5 (where 5 is just a namber in the Z set 2^32-1 maybe). There isn't much we can do to cope with different usb storage timings. -- Fabio Erculiani
Re: [sabayon-dev] Drop i810 support from kernel?
On Tue, May 14, 2013 at 8:35 PM, Joost Ruis joost.r...@sabayon.org wrote: 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, You are wrong. i810 drm driver != i810 chipset. 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 -- Fabio Erculiani
Re: [sabayon-dev] Drop i810 support from kernel?
A. Introduction This is a framebuffer driver for various Intel 810/815 compatible graphics devices. These include: Intel 810 Intel 810E Intel 810-DC100 Intel 815 Internal graphics only, 100Mhz FSB Intel 815 Internal graphics only Intel 815 Internal graphics and AGP Mmh. I may consider to move it to M, next time I'm on kernel stuff. -- Fabio Erculiani
Re: [sabayon-dev] Drop i810 support from kernel?
https://github.com/Sabayon/kernel/commit/c249cb52d52855f24c9847e7d5590c367ea4c222 -- Fabio Erculiani
Re: [sabayon-dev] apache2 and systemd
It seems that our apache isn't compiled with systemd support or systemd is not correctly detected at runtime. Type=notify in the unity requires the process to call sd_notify() when it's done setting up the sockets. Can you try changing it to Type=simple and do: # systemctl daemon-reload # systemctl restart apache2 The unit is at /usr/lib/systemd/system/apache2.service -- Fabio Erculiani
Re: [sabayon-dev] apache2 and systemd
It needs to be fixed, actually. -- Fabio Erculiani
Re: [sabayon-dev] systemd bug reports
I think I just fixed it. See bugzilla and systemd-love overlay git activity -- Fabio Erculiani
Re: [sabayon-dev] NetworkManager Error
This is related to the consolekit issues I fixed today. Make sure to install all the updates if you're using the sabayonlinux.org repo, or just wait a couple of days if you're with sabayon-weekly. -- Fabio Erculiani
Re: [sabayon-dev] systemd bug reports
Are you using KDM? If so, I have committed a fixed package in limbo yesterday. -- Fabio Erculiani
Re: [sabayon-dev] [RFC] Ending 32bit support?
Let me clarify: I wrote that we will re-discuss all this in a year. This is different from I am going to drop x86 support in a year. -- Fabio Erculiani
Re: [sabayon-dev] [RFC] Ending 32bit support?
It looks like there are still a lot of people using i686. So, I'd rather postpone the decision for one more year, sigh. -- Fabio Erculiani
[sabayon-dev] git.sabayon.org is no more
All the development repositories have been moved to GitHub [1]. If you want to contribute to the development of Sabayon, you don't need to be a trusted developer anymore, but just send pull requests ;-) Have fun! [1] https://github.com/Sabayon -- Fabio Erculiani
Re: [sabayon-dev] Multiple monitor issues on nVidia
I am bumping nvidia-drivers, all of them. -- Fabio Erculiani
Re: [sabayon-dev] virtual/ffmpeg dependency if wrong
Is that a dep-rewrite? Maybe we should just drop it and fix the virtual/ffmpeg ebuild if needed (still needed by the way?). -- Fabio Erculiani
Re: [sabayon-dev] Multiple monitor issues on nVidia
Please detail the issue. -- Fabio Erculiani
Re: [sabayon-dev] Multiple monitor issues on nVidia
Logs or die, please. -- Fabio Erculiani
Re: [sabayon-dev] virtual/ffmpeg dependency if wrong
On Sat, Apr 27, 2013 at 5:05 PM, Sławomir Nizio slawomir.ni...@sabayon.org wrote: Oh good you are back to this. Is that a dep-rewrite? yes Maybe we should just drop it and fix the virtual/ffmpeg ebuild if needed (still needed by the way?). It would work, but in my opinion a solution that is cheaper is to fix the rewrite. Is it possible to remove ffmpeg from the Entropy virtual using the same method? I don't see any problem with that. -- Fabio Erculiani
Re: [sabayon-dev] virtual/ffmpeg dependency if wrong
On Sat, Apr 27, 2013 at 5:05 PM, Sławomir Nizio slawomir.ni...@sabayon.org wrote: Oh good you are back to this. Is that a dep-rewrite? yes Maybe we should just drop it and fix the virtual/ffmpeg ebuild if needed (still needed by the way?). It would work, but in my opinion a solution that is cheaper is to fix the rewrite. Is it possible to remove ffmpeg from the Entropy virtual using the same method? I don't see any problem with that. -- Fabio Erculiani
Re: [sabayon-dev] sys-kernel/linux-server-3.8.5 on daily builds
Fixed in molecules.git -- Fabio Erculiani
Re: [sabayon-dev] Observations with latest
On Fri, Apr 12, 2013 at 12:32 PM, Steven Cristian stefan.crist...@best.eu.org wrote: If upgrading makes it possible to survive after upgrade ... Then so be it. No, usually we intentionally break systems (sarcasm intended) -- Fabio Erculiani
Re: [sabayon-dev] Rolling with monthly images
On Sat, Apr 6, 2013 at 10:45 AM, Andre Jaenisch andrejaeni...@googlemail.com wrote: 2013/4/6 Daniel Neilson daniel.neilso...@gmail.com: Would it be possible, or desirable, to have the release and monthly torrents on different pages? Or maybe have different tabs on the page to separate monthlies from the regular releases? Just to tidy things up and make it look a little more organized and simpler. Two different headers for two two tables could do it, too … And this can also be generated automatically ;-) At this time, I prefer not to hack net-p2p/bittorrent python code further. If you are interested, feel free to do it. Ryuno-Ki -- Fabio Erculiani
Re: [sabayon-dev] Rolling with monthly images
On Sat, Apr 6, 2013 at 10:51 AM, Andre Jaenisch andrejaeni...@googlemail.com wrote: 2013/4/6 Fabio Erculiani lx...@sabayon.org: At this time, I prefer not to hack net-p2p/bittorrent python code further. If you are interested, feel free to do it. I am. But I have no guess, where you store the code to generate this HTML source code. Would be a nice exercise for BeautifulSoup … Maybe I should have a closer look to the drupal branch on git … to include it in Drupal (with header and such). # equo install net-p2p/bittorrent code: /usr/lib/python2.7/site-packages/BitTorrent/tracker.py -- Fabio Erculiani
Re: [sabayon-dev] Bumping GCC to 4.7.2
# equo install sys-devel/gcc:4.7 Our gcc is split into base-gcc (containing libgcc and friends) and the actual compiler. -- Fabio Erculiani
Re: [sabayon-dev] Rolling with monthly images
http://torrents.sabayon.org/ now listed. However, monthly images haven't been sponsored much yet. Something I will be doing in a month or so... -- Fabio Erculiani
[sabayon-dev] Rolling with monthly images
Hello, besides the current dailys, we now have monthly images. You can find them on our mirrors, inside the iso/monthly/ directory. There is also a ChangeLogs subdir containing changelogs of our main git repos. Images will be updated at the end of the month. Older images will be kept on the mirrors one more month (so each monthly image is going to last at most 2 months). For instance, next month we will have 13.05 and 13.04 into that directory, while in June 13.04 will be dropped and 13.06 will be added. As you have realized, the versioning schema for monthly images is YY.MM. All this is brought to you automatically ;-) Cheers, -- Fabio Erculiani
Re: [sabayon-dev] Dailys Don't Boot
What kernel are they running? Can you point me to the exact iso image on mirrors? -- Fabio Erculiani
Re: [sabayon-dev] Dailys Don't Boot
I read that the build date for them is still: 16-Mar-2013 13:31 Let me see -- Fabio Erculiani
Re: [sabayon-dev] Dailys Don't Boot
ISO images haven't been pushed to mirror since March 20, and the working XfceForensic build is =March 23. I will fix this. -- Fabio Erculiani
Re: [sabayon-dev] NetworkManager script
No, see git log
Re: [sabayon-dev] NetworkManager script
That has nothing to do with it. Fix your setup, read documentation
Re: [sabayon-dev] Bumping GCC to 4.7.2
Brace yourself, the GCC 4.7.2 upgrade is in progress. -- Fabio Erculiani
[sabayon-dev] Bumping GCC to 4.7.2
I was thinking about dev-lang/{base-,}gcc to 4.7.2 this or the next week.
It looks like there are packages that do not build (or fail at runtime
-- one), still [1].
But we may just build these using 4.6.3 and move on.
What do you think?
[1] https://bugs.gentoo.org/show_bug.cgi?id=gcc-4.7
--
Fabio Erculiani
Re: [sabayon-dev] Bumping GCC to 4.7.2
Do not hijack this discussion with your problems. -- Fabio Erculiani
Re: [sabayon-dev] again issues with packages to remove?
Then a package bump should fix this. -- Fabio Erculiani
[sabayon-dev] How to Report Bugs Effectively
I just discovered this (stupid me): http://www.chiark.greenend.org.uk/~sgtatham/bugs.html And I think it should be placed somewhere at bugs.sabayon.org. Ideas? -- Fabio Erculiani
Re: [sabayon-dev] package revisions
This is needed in order to get sabayon-weekly package tarballs working
Re: [sabayon-dev] package revisions
I will try to find a better way to fix weekly without causing all that noise
Re: [sabayon-dev] package revisions
The idea I have in mind is to replace the revision in the file name with the actual md5 or sha1 of the tarball. That would fix the problem of overlapping tarball file names with different hash. -- Fabio Erculiani
Re: [sabayon-dev] Dailys Don't Boot
It is definitely a kernel bug, I'm quite sure. And, I also think it's related to the USB subsystem. Could you try to burn the ISO image to a DVD disc and boot off it? Going to do the same here -- Fabio Erculiani
Re: [sabayon-dev] Dailys Don't Boot
I am pushing Linux 3.8.3 directly to main right now (repo revision 2878). I will test is as soon as it is available, more or less. -- Fabio Erculiani
Re: [sabayon-dev] Dailys Don't Boot
The new kernel works! -- Fabio Erculiani
Re: [sabayon-dev] Dailys Don't Boot
No, I am afraid to say that the problem is not solved yet. I am still working on it, I restricted the area to the USB controller driver ehci-hcd. -- Fabio Erculiani
Re: [sabayon-dev] Problem with new Xorg and possible fglrx
I can't say anything without logs capturing the problem. You can try ati-drivers-13.2_beta7 that is in Portage, or try the previous kernel (3.7). I gave a final rebuild to all the ati-drivers in repos before moving to main, however. -- Fabio Erculiani
