> and git is distributed anyway, so even if they immediately changed
> things, we have what we need to move elsewhere.
Kind reminder: GH is not only about .git. (No I'm not suggesting anything.)
> For me, let's go with Kanban board!
\o/
>* enhancement of sark crc hashing algorithm and check (i'm
> working on this) to avoid i/o intensive disk operations
> and fix check on python packages
It has nothing to do with making a new release so I'd skip that. OK, it
does
> I agreed with your post link. It'is important trace and organize
> activities and in general there two types of process to handle:
These can be valid ideas, but my mail will be about the board to track
issues related to making a release which is my main concern.
Everyone who expressed their
Please confirm the status of this. I suppose package flow can go as
normal now, right?
https://www.sabayon.org/download/
(Desktop edition only for now)
https://www.sabayon.org/latest/
Enjoy!
(Reminder: as Sabayon is a rolling release distribution, there is no
need to reinstall the OS or do any special action to be up to date.)
On 09.04.2018 20:44, KJS wrote:
> Yea i didn't mean it had to be implemented right now, sorry if it came
> across that way.
Quick review :)
s1.png: sabayon → Sabayon; s3: LTSI → LTS; s6: IRC:f… IRC: f… (space)
> After the last batch of testing, I think it might be time to change our
> slide show that is presented in the installer as it's installing. I
> feel it's a bit dated and blah compared to some of the slides I have
> seen with other distros.
>
> I created some new ones found:
>
> Hi there,
>
> so on https://github.com/Sabayon/sabayon-website-next/pull/75/
> I've added links to stable ISOs, but they point to 17.03 - can somebody push
> the 18.04 ones? I didn't found newer ones on the German mirror.
For actually doing the release, AFAIK we're waiting for Ettore.
Maybe
> 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.
I removed this part and made further changes.
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
Hi,
Jerrod, is it good to go?
André, are you around to finish up with the notes?
It's being uploaded to sabayonlinux.org after a test, and hopefully gets
to the release:
[app-admin/anaconda] move dev-util/glade to common deps.
/usr/lib64/libAnacondaWidgets.so.2.1.0 -> libgladeui-2.so.6 which is
provided by dev-util/glade:3.10.
[app-admin/anaconda] switch
I had a chat with mudler and the idea is:
- test this, if all fine it could go (Geaaru is helping with testing <3),
- otherwise it can be worked on and applied later.
>> * Anaconda Crashes when pressing F12 during install phase
>> o Solution: Unknown. Plan is to eventually migrate away from
>> unmaintained Anaconda and move to Calamares, but due to
>> Calamares being incomplete at this point in time, and testing
>> will be
> Yep we got it.
\o/
> 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
> I like the plank dock so after doing a fresh install of Gnome-dev I
> installed plank and went to fire it up with error:
>
> GSettingsSchema 'net.launchpad.plank.dock.settings' not found
>
> solution is:
> sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
>
> plank now starts fine after
> * Anaconda Crashes when pressing F12 during install phase
> o Solution: Unknown. Plan is to eventually migrate away from
> unmaintained Anaconda and move to Calamares, but due to
> Calamares being incomplete at this point in time, and testing
> will be required
> Elementary icon theme is very outdated:
Fixed in overlay, and Joost will build that:
[x11-themes/elementary-icon-theme] version bump to 4.3.1
M x11-themes/elementary-icon-theme/Manifest
D x11-themes/elementary-icon-theme/elementary-icon-theme-2.7.1.ebuild
A
> I have to disagree with that attitude. If we can't get the cosmetics to
> look good, what are people gonna think of for the rest of the build? If
> I were to boot up a stable release of any operating system and the icons
> were all goofy and messed up, I'd be moving on to something else for
>
Nice list!
> * Icons are not uniform. Icons aren't right size in XFCE.
> o Solution: Switch default icons to Obisidian for all spins.
> Obisdian works in XFCE, MATE, GNOME, and KDE. Obsidian is the
> up-to-date version of Faenza (current MATE icons).
One of the icon
I propose to keep it as simple as possible and think of extending that
as needed.
> For those links: I personally prefer the issues view.
Hopefully also the Kanban board!
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"
Hello,
There are quite a few factors related to making a release, and I believe
it's useful that each one knows what's going on, what else is required
and what is the overall progress.
Example being recent "question mark" about the status which was resolved
quickly on IRC, but until then it
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
> If anybody is not happy with being mentioned in the logs, ping me.
(This mail doesn't mean "no" when it comes to me)
Well, in general, IRC is something that works best "live," and parts
outside the context can be misunderstood.
Consider writing a summary; or making some edits (marking them)
Hi!
In general, if you are dealing with broken manifests, please don't just
update Manifest files blindly because the checksums give also some
security benefit.
Some comments for sabayon-distro:
app-office/libreoffice-l10n-* for 5.4.0.3: old version, can be ignored
or removed completely;
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
> I was hoping we were going to finish all our major upgrades before
> performing a release. So GCC, python, etc. Are all the major upgrades
> complete and considered stable?
I think all besides GCC is there. Personally I wouldn't wait any
further: there are no estimates, no advanced progress yet
Hello,
https://www.sabayon.org/desktop/ links to 16.11. Can it be updated?
> Hello,
>
> In bug 5480, enabling this flag on layman was requested.
> I saw that enabling it does not only provide the laymansync plugin, but
> also makes it so that newly added overlays have auto-sync = Yes in
> portage/repos.conf/layman.conf.
>
> "As a result of the default auto-sync =
app-crypt/libu2f-host provides /lib/udev/rules.d/70-u2f.rules. Is that
what you need?
Hello,
In bug 5480, enabling this flag on layman was requested.
I saw that enabling it does not only provide the laymansync plugin, but
also makes it so that newly added overlays have auto-sync = Yes in
portage/repos.conf/layman.conf.
"As a result of the default auto-sync = True/Yes setting,
> PR still open, got comments, need to be taken care of. Low priority IMO.
I moved it forward :)
Hello,
In sabayon-limbo there are packages like in title. They are masked in
Gentoo but in Sabayon I made them available because this version allows
for "support qt4, qt5 or both" instead of "support either qt4 or qt5."
Especially, Octave could not be bumped without this (requires qt5 support).
> So to recap whats left:
>
> Our new hardware needs (HDD space, SSDs) : *Was this taken care of Fabio?*
>
A server was provided for a backup, so as far as I know this should not
be an issue anymore (in the context of gcc bump).
>
> Bugzilla improvements: *Bug Bankruptcy may assist in removing
>
> I agree with this, how long do we think is 'fair' before resolving a bug
> due to abandonment? 6months?
There are 409 bugs open.
73 have been changed within the last 6 months,
36 within the previous 6 months (that is, starting from July 4th, 2016),
31 since 2016-01-09,
44 since 2015-07-01,
36
> Here are the notes from the meeting today and then some. If you would
> like to elaborate or ask questions please do so here.
>
> Our new hardware needs (HDD space, SSDs)
>
> *
>
> Fabio handling this? Is he aware of everything we need?
>
>
>
> Bugzilla improvements
>
> *
>
> Too
Hello,
> If Bugzilla is too complicated, maybe it's time for another tool?
The point was how Bugzilla is configured, not the tool itself.
>
> Where do you get topics for blogging? Our forums? What about other blogs?
> Facebook? Google+?
>
> As far as I understood, there are some changes
I will not be available for a few days but don't let that delay the
meeting unnecessarily. I elaborate on my points below.
Thanks Jerrod for including them.
> There are some topics we should go over to level the knowledge for team.
> I'm curious when the team is most available.
> I'm currently
Silence here, so let me share the status: it's still undecided, and the
discussion can continue when /some guy/ can fully participate (goes from
semi-away which is due to technical problems).
> We are one of the few distributions (actually i'm not aware of others)
> that support libav out of the box, and i'm proud of it. What i would
> propose instead is trying to push upstream projects that misses libav
> support and/or helping libav providing support to them.
Volunteers? :)
One of
> It would be awesome for the users to have the choice, actually. ,-)
It could be useful only in limited number of cases I think, and neither
Debian, Gentoo nor Arch do it, from what I can see.
(Gentoo provides the choice, but they can't co-exist, and switching
requires rebuilding many
> 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 read it really does not compile with libav.
> I'm not technically up to date, but if libav is indeed
> breaking away with
> 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.
I believe only ffmpeg with the stable keyword would be used.
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
Guys,
Could you tell me where is the place that removes packages from target
system after installation?
I looked in molecules.git and "packages_to_remove" was empty or almost
empty, and PACKAGES_TO_REMOVE in scripts/inner_source_chroot_update.sh
contains only translated manual packages.
Discussed on IRC, this will be disabled, and can be enabled when
cleaning Anaconda dependencies cruft is made/improved.
> "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
> 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
> 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.
Hello,
I bumped apache in overlay for
https://bugs.gentoo.org/show_bug.cgi?id=603130. I can't test it right
now, and I wouldn't be able to in the following days, so please take
care of it further.
I wish you all warm and joyful Christmas!
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.
Hello,
I can see people on the IRC channel asking how to start Rigo and stating
something about an not authorized message.
Is there any regression?
We have split ebuilds of poppler. Upstream supports qt4 and qt5; we have
only poppler-qt4. Providing -qt5 is not a problem; the problem is
something else.
(Currently qt5 on the poppler meta package is disabled; but I think
it's time to think about providing -qt5 - for new Calibre for example.)
Hello,
Your shell history, /var/log/entropy/entropy.log, *possibly* timestamp
of files under /var/db/pkg or equo.sh from https://github.com/Enlik/misc.
Any replacement window manager? Perhaps one from the XFCE land?
(I don't know if the package has special requirements.)
- Openbox - small, looks good, but provides its own menu (right and
middle click on the desktop) which may be unwanted here. (Disabling the
menu in skel would be even more so.
Hi,
Does app-misc/sabayon-steambox need to depend on Metacity? Metacity is
being removed from Portage.
W dniu 10.09.2014 o 19:12, Jerrod Frost pisze:
Wow! thats nice! Can we integrate this into equo?
I don't think we should. They two projects serve different purpose (in
general, equo uses the local database; querypkg queries the remote
server), they are written in different languages (equo -
W dniu 10.09.2014 o 03:28, Steven Cristian pisze:
did you devise a schema for all the
'unused' deps?
There are some unused deps which other deps of other programs are
directly or indirectly dependent on.
If some package is used (directly or indirectly) only by a package
installed by user, it
W dniu 07.09.2014 o 21:35, Fabio Erculiani pisze:
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.
Great, I will! Perhaps I will fix the obvious things first, though.
Hi,
(Easy downloading of Entropy packages, from any repository and for any
architecture.)
Some of you may have heard about app-misc/querypkg. It's a tool to make
queries to display information about Sabayon packages (it retrieves data
from packages.sabayon.org using its API). Version 2.2 has a
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:
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
W dniu 31.07.2014 23:16, pierigno pisze:
2014-07-31 20:34 GMT+02:00 Sławomir Nizio slawomir.ni...@sabayon.org:
Top posting is not usually seen well on such lists. :P
I see, thanks for letting me know, I'm posting from gmail and it
automatically put quoted text in the bottom part
W dniu 31.07.2014 13:50, pierigno pisze:
any chance to see gstreamer support enabled?
https://bugs.sabayon.org/show_bug.cgi?id=4080
2014-07-31 8:13 GMT+02:00 Sławomir Nizio slawomir.ni...@sabayon.org:
Hello,
Please note that, starting from Firefox 31.0 (now in the testing
repository
W dniu 31.07.2014 13:50, pierigno pisze:
any chance to see gstreamer support enabled?
https://bugs.sabayon.org/show_bug.cgi?id=4080
2014-07-31 8:13 GMT+02:00 Sławomir Nizio slawomir.ni...@sabayon.org:
Hello,
Please note that, starting from Firefox 31.0 (now in the testing
repository
Hello,
Now main.html doesn't show any ISO files:
http://mirror.de.sabayon.org/iso/main.html because there are none.
There are only daily and monthly ones.
I can see that generation of the file has been disabled, but it seems
that the file main.html should also be deleted manually.
By the way:
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.
Hi all,
Just a note in case you are affected by this bug (I didn't have it on my
system, but it was mentioned on IRC):
https://bugs.gentoo.org/show_bug.cgi?id=506608
[app-office/akonadi-server-1.12.0: Unable to initialize database.
Column 'name' cannot be null QMYSQL3]
this is fixed in
Thanks - now it will be more clear.
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
Hi,
one question came recently in my mind: Where to fill bug reports now?
We had a little issue (missing dep) with Mate from 13.04 ISO yesterday.
I asked in #mate on Freenode and it was fixed almost immediately. For
the sake of documentation I filled a bug report on GitHub
So, x86_64 is more than 10 years old now, and it's time to think again
about the i686 architecture.
I am proposing to gradually drop support for x86 32bit by the end of
2013 (the how would deserve a separate discussion).
Is there any serious reason not to kill 32bit? Maintaining it takes
50%
partially as a question for an idea/confirmation and FYI to avoid it in the
future:
1. Remove libav.
2. # equo install -p virtual/ffmpeg
3. # Not found:
=media-video/libav-0.10.3[X,encode,gsm,mp3,sdl,speex,theora,threads,truetype,vaapi,vdpau,x264]
It is most likely caused by:
# We provide
Since it is not deployed via git I cannot provide a patch.
diff -u old.py new.py track.py.patch
Fabio Erculiani wrote:
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
Also,
[scripts] gen_html: add support for monthly ISOs
Additionally, daily.tmpl skips
Hello all,
As you may know, Sabayon uses git for its repositories.
It is a good version control system: it is fast, has
really good support for branching, support for rewriting
history (which has good use cases) and is pretty well
known among VCSs).
However, there is nothing without
On Mon, 1 Apr 2013 18:36:04 +0200
Danilo Pianini danilo.pian...@gmail.com wrote:
Agree. We could adopt as a rule to leave a comment when changing something,
and just use a FTP server.
I disagree: CVS provides history for free anyway* so it's not a big deal;
and it is easier to collaborate this
On Sat, 16 Mar 2013 08:13:51 +
Ian Whyman v00...@v00d00.net wrote:
To be honest I think it looked nicer before.
On 15 Mar 2013 22:52, Andre Jaenisch andrejaeni...@googlemail.com wrote:
It could be tweaked more, but I like the consistency with main/daily.html
(and one of them will link to
Portage has such a FEATURE:
compressdebug
Compress the debug sections in the split debug files with
zlib to save space.
Make sure you have built both binutils and gdb with
USE=zlib support for this
to work. See
On Thu, 21 Feb 2013 14:25:16 +
Fabio Erculiani lx...@sabayon.org wrote:
We will probably hold LibreOffice in limbo until 4.0.1 then.
Our current version is 4.0.0.3 though.
What about masking it in Entropy, double checking it's masked
and pushing with current LibreOffice 3?
On Thu, 21 Feb 2013 14:25:16 +
Fabio Erculiani lx...@sabayon.org wrote:
We will probably hold LibreOffice in limbo until 4.0.1 then.
Our current version is 4.0.0.3 though.
What do you think about pushing it as masked (without removing
LibreOffice 3 of course)?
It would be cool for
Argh, two similar mails from me. I thought the first
one didn't get there due to an error that appeared.
/me blames his mail client
On Fri, 15 Feb 2013 00:20:40 +0100
Sławomir Nizio slawomir.ni...@sabayon.org wrote:
On Thu, 14 Feb 2013 22:04:26 +0100
Andre Jaenisch wrote:
$ transmission-cli
http://static.sabayon.org/sabayon/torrents/Sabayon_Linux_CoreCDX_11_x86.iso.torrent
transmission-cli 2.76 (13786)
[21:39
Update!
sys-apps/kbd-1.15.5-r1 has a fix for 1.15.5, and we'll have this update soon.
In case anyone has still the problem, let me know here or on bug 3872. Thanks!
On Thu, 17 Jan 2013 15:59:10 +0100
Danilo Pianini danilo.pian...@gmail.com wrote:
Thinking about priorities, I agree with Ian: the installer deserves
our attention before the ARM support.
+
Given that, ARM is going to be more and more important in near future,
so I see favourably the
take a look at https://github.com/Enlik/misc/blob/master/entropy-by-size.pl
*Note* that it got broken with new equo (one that doesn't print options
recursively
with equo --help*), but it should work for your purposes when you have your
ancient
one. (Also, note I will break it for you and make
As I've seen on IRC, Firefox 18 has the some problem as Chromium had [1].
It seems to require jpeg-turbo [2] which may be the reason.
So, if you update to Firefox 18, which is currently in the testing repository:
$ querypkg firefox --repo limbo
@@ Please wait, downloading data...
@@
Hello,
Do we have a full system/world SL image that has been compiled with the
Linaro GCC toolchain? (x86_64 Arch)
n
If not, is there a possibility that we will have one?
Very unlikely.
Nice to see you like Sabayon. I want to clarify one thing.
openrc and systemd only if you choose it and likely to the end of time.
Sabayon doesn't provide systemd but you should be able to install it from
Portage if you know what you're doing (ie. probably better to use an older
version
Btw.
You may find further knowledge on GIT matter on
It's git not GIT. :)
I don't see much of a problem with that question here, to the extent
where do I find the git repositories and the answer to that is:
git.sabayon.org - click one you want and look for the clone link.
Dnia 12.05.2012 o 18:01 Joost Ruis joost.r...@sabayonlinux.org
napisał(a):
I noticed that gnumeric wasn't working:
sabayonuser@localhost ~ $ gnumeric
gnumeric: error while loading shared libraries: libORBit-2.so.0:
cannot open shared object file: No such file or directory
hello,
some time ago I provided by means of bugzilla two ebuilds for the
latest versions of nvidia-cuda-sdk and nvidia-cuda-tooklit
(https://bugs.sabayon.org/show_bug.cgi?id=3371 and
https://bugs.sabayon.org/show_bug.cgi?id=3372).
I didn't get any feedback so I'm wondering if I did something
Dnia 11.06.2012 o 16:56 Joost Ruis joost.r...@sabayonlinux.org
napisał(a):
Would it be smart to enable the use of static-libs on certain packages?
Or should it be considered as bloat in Gentoo/Sabayon?
How I see it:
At compile time if you enable static-libs it will copy all the needed
Usually it's better to post such stuff on the bug tracker,
because they can get lost easily otherwise…
By the way if one day GRUB is updated, it'll stop reading
info from /proc/cmdline during grub-mkconfig (due to a commit
in a Sabayon overlay which gets rid of it). I consider it
(ie. the fact
It's dev-util/bsdiff, not shipped by defauilt indeed.
Hello,
I have disabled dev-haskell particle because it seems to introduce
too many problems.
See for example bug 3310 and also refer to particle's logs, grepping
for dev-haskell.
Hi,
Inspired by bug 3240 I've looked for injected packages with broken linkage
and rebuilt them (and a few others linking to libbfd-2.20.1.20100303.so).
To find a broken library I've used qfile to see if any package provides
a file with such name.
Is there a better way with eit, something like
Do you think we could add some kind of QA script for this?
Maybe we could daily check for library linkage sanity of injected
packages via cron?
Daily would be probably too often. Once a week, perhaps,
a more detailed test could be run.
Some check is already done during push:
no missing
1 - 100 of 123 matches
Mail list logo
