Suggestion for a sticky thread on updates and other things

[Richlion]

Hello Guys,

as there already have been a lot of discussion on Sabayon updates breaking the system (a lot of concerns have been expressed by long term SL users) I was wondering if it would be possible for SL developers to create some kind of a sticky thread (just like "News" and "Press Release") in order to inform us that the updates are related to? I've seen some people already suggesting something like this.
After all developers know what's been screwed up and needs fixing and whether updates are related to new development changes that need testing. This would help us make decisions on whether it's important to update now, or maybe there are some new things coming in and actually new updates are not fixes, so it's better to wait or test those updates on another machine some of us have.

Even going further, is it possible to group updates, for example if KDE needs a total upgrade, would it be possible to separate those in the repository from other core system updates? I don't think it is an easy task for developers, but neither it is for us by clicking in Sulfur, as many of us don't know the details of the connections and related updates.

For example today I have 77 updates, some are in dev-libs, dev-perl, HTTP, XML stuff, KDE network frontend, Perl-core, are they critical updates and fixes to bugs? Linux is getting rather very complex and for many of us it's hard to make such decisions just based on the fact that "updated have arrived".

We could also use those threads to post updates on whether they have broken something or not, so if for example I went for installing all updates, I would be willing to test what important for me to work (web browser, email client, multimedia, etc.) and post a short message with a list of applications I have checked. Would it not be beneficial to all of us?

And also on the subject of updating via Equo/Sulfur, I found an option to switch to weekly updates as some of you suggested it's much safer. However if a bug still gets in the way, how do I fix it using Sulfur? Do I switch to daily updates and wait? Or do I report a bug and wait for a manual fix?

Best regards,
Richlion

[newerusebtfrs]

I think this is good idea. Once I even suggest to make "monthly" repo but no one like my idea
Sabayon it's ok but, "we" must do something to make it more stable.

[batvink]

well, there's allready something similar to it.
If you want, you can subscribe to the Sabayon Devel. mailing list,
and actively follow and discuss what's going on.
http://lists.sabayon.org/cgi-bin/mailman/listinfo/devel
Once subscribed, you get once, or twice a week a mail.

example of mail:

Code: Select all

Send devel mailing list submissions to
   devel@lists.sabayon.org

To subscribe or unsubscribe via the World Wide Web, visit
   http://lists.sabayon.org/cgi-bin/mailman/listinfo/devel
or, via email, send a message with subject or body 'help' to
   devel-request@lists.sabayon.org

You can reach the person managing the list at
   devel-owner@lists.sabayon.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of devel digest..."



Today's Topics:

   1. Sabayon Daily K64  20111123 (sabayonino)
   2. Re: Sabayon Daily K64 20111123 (Fabio Erculiani)
   3. Re: net-misc/networkmanagement-0.8.95 in sabayon-limbo
      (Josef Odenthal)


Gedeelte 1.2
Onderwerp:
[sabayon-dev] Sabayon Daily K64 20111123
Van:
sabayonino <sabayonino@gmail.com>
Datum:
Sat, 26 Nov 2011 12:11:36 +0000
Aan:
devel@lists.sabayon.org

Hi

Triyng this live version X-server doesn't start because gcc-config is set to 4.5.3 profile

setting gcc to 4.6.2 solved this.

I think gcc-4.5.3 will be removed (or no ? )

the installation is successful

Regards :)


Gedeelte 1.2
Onderwerp:
Re: [sabayon-dev] Sabayon Daily K64 20111123
Van:
Fabio Erculiani <lxnay@sabayon.org>
Datum:
Sat, 26 Nov 2011 14:13:45 +0100
Aan:
Sabayon public development mailing list <devel@lists.sabayon.org>

Done on chroots.
It will be propagated on the next automatic ISO push.

-- Fabio Erculiani

[batvink]

However if a bug still gets in the way, how do I fix it using Sulfur? Do I switch to daily updates and wait? Or do I report a bug and wait for a manual fix?

There will allways be bugs, in every Distribution., you can't avoid that.
Best way to deal with it, is try to fix it yourself, and when you do, report back to the forum, to inform the others
having the same problem. Otherwise, Drop your problem on the forum, you will be helped.
meanwhile, you can search the internet, if other Distro's have the same problem, and maybe allready have a solution.
Then, also post it on the forum, with the link. If we all work together, first look at the forum, and try to fix it yourself,
do all the above, we help each other. to make this a strong Community.
When installing packages, whether in terminal or Sulfur, read the output of Entropy., scroll back for messages.
When posting your problem, include as much information as you can. read the wiki. etc...

[Richlion]

batvink » Mon Nov 28, 2011 16:56
well, there's allready something similar to it.
If you want, you can subscribe to the Sabayon Devel. mailing list,
and actively follow and discuss what's going on.
http://lists.sabayon.org/cgi-bin/mailman/listinfo/devel
Once subscribed, you get once, or twice a week a mail.

I may subscribe to see how it works, I was thinking more about some kind of a digest, maybe a weekly update on this forum on what's behind the Sulfur updates? And a little bit of human touch, remember, we not all are Gentoo gurus. I realize it may not be doable and too much additional work for our forum admins. If you say "not possible", I'll say ok.
Thanks

[Richlion]

Ok, so my updates I have today via Sulfur:

Code: Select all

>>> Regenerating /etc/ld.so.cache...
   ## SPM: post-install phase
 * Update Parser: add XML::SAX::PurePerl
could not find ParserDetails.ini in /usr/lib64/perl5/vendor_perl/5.12.4/XML/SAX
   ## Cleaning: dev-perl/XML-SAX-0.990.0


Is this what I should report? The problem is the output screen only displays the last, only from package 135 out of 154. Is there a full text log from Sulfur somewhere?

[batvink]

i think you can safely ignore that message., but that is my opinion.
if you don;t trust it, then yeah, post it on the forum.

you can find the log:

Code: Select all

/var/log/entropy/entropy.log

When using emerge:

Code: Select all

/var/log/emerge.log

also portage, gdm, xorg, samba, rc, and kdm logs are available.

when running sulfur, or emerge, you can follow the log,
by opening a new terminal, and as root type:

Code: Select all

tail -f /var/log/entropy/entropy.log

or

Code: Select all

tail -f /var/log/messages

for system wide messages.

i found quadconsole

equo install kde-misc/quadkonsole-0.4.2

a very good candidate for watching those logs....