[gentoo-user] abendbrot overlay missing?

2019-12-18 Thread Ilya Trukhanov
Seems to be gone from:
https://github.com/gentoo-mirror/abendbrot
https://qa-reports.gentoo.org/output/repos/

Anyone knows what happened to it? And any way to learn about this in
advance? Doesn't look like repositories.xml is version controlled, couldn't
find anything in the mailing lists, either.



Re: [gentoo-user] trying to upgrade some old, never upgraded image for an embedded system …

2019-12-18 Thread Ilya Trukhanov
On Sun, Dec 15, 2019 at 07:01:15PM +0100, Thomas Schweikle wrote:
> The current version of portage supports EAPI '6'. You must upgrade to a
> newer version of portage before EAPI masked packages can be installed.

The message is pretty clear. You need to upgrade portage first. Try
`emerge -1 portage`. This should take care of the EAPI message.

Good luck with the 17.1 profile migration. Though if the system is not
amd64, you should have nothing to worry about.



Re: [gentoo-user] Packages failed to build during 17.0 -> 17.1 migration

2019-06-07 Thread Ilya Trukhanov
On Fri, Jun 07, 2019 at 08:03:30AM +0100, Sergei Trofimovich wrote:
> On Thu, 06 Jun 2019 18:49:48 -0400
> Jack  wrote:
> 
> > On 2019.06.06 18:38, Ilya Trukhanov wrote:
> > > Namely x11-libs/libX11 and dev-libs/glib:
> > > 
> > > - libX11 failed during configure because it couldn't find xcb;
> > > - glib failed during configure because it couldn't find libmount.
> > > 
> > > Looks like it is an order issue, because after rebuilding
> > > x11-libs/libxcb and sys-apps/util-linux, both libX11 and glib built  
> > > just
> > > fine.
> > > 
> > > Should I report bugs for these? The news item says:
> > >   
> > > >If you have any problems with the new profiles or the migration
> > > >procedure, please report a bug and make it block the tracker.  
> > > 
> > > But I'm a little reluctant to do so for various reasons.
> > >   
> > I'm in the same situation.  I've had several rebuild failures that  
> > succeeded after re-emerging one/some of what they depend on, although I  
> > would have expected those to also be rebuilt.
> > 
> > I wonder if the instructions should be "emerge -1 --deep /lib32  
> > /usr/lib32" ?  I'll have to try it once I'm done with the current set  
> > of emerges.
> > 
> > Anyway - it probably does make sense to file the bug - the worst they  
> > will do is close it as not a bug, and hopefully at least tell you what  
> > you should have done to avoid the problem.
> > 
> 
> I think the emerge command as stated in the news item is incomplete
> as emerge does not pick correct rebuild order (it assumes all packages
> are installed and in order, thus picks arbitrary rebuild order).
> 
> Try to add --complete-graph to it:
> emerge -1 --deep --complete-graph /lib32 /usr/lib32
> 
> -- 
> 
>   Sergei
> 

Unfortunately this still doesn't guarantee the correct build order for
me. I wonder if running emerge with --keep-going a few times would work in
this situation?

It might be a good idea to mention this issue somewhere on the wiki or in a
follow-up news item. I doubt we're the last to face this problem now
that 17.1 profiles are stable.


signature.asc
Description: Digital signature


[gentoo-user] Packages failed to build during 17.0 -> 17.1 migration

2019-06-06 Thread Ilya Trukhanov
Namely x11-libs/libX11 and dev-libs/glib:

- libX11 failed during configure because it couldn't find xcb;
- glib failed during configure because it couldn't find libmount.

Looks like it is an order issue, because after rebuilding
x11-libs/libxcb and sys-apps/util-linux, both libX11 and glib built just
fine.

Should I report bugs for these? The news item says:

>If you have any problems with the new profiles or the migration
>procedure, please report a bug and make it block the tracker.

But I'm a little reluctant to do so for various reasons.


signature.asc
Description: Digital signature


Re: [gentoo-user] Re: Hostile takeover of our github mirror. Don't use ebuild from there until new warning!

2018-07-01 Thread Ilya Trukhanov




On 06/29/2018 10:47 AM, Ivan J. wrote:

On Fri, Jun 29, 2018 at 03:12:15AM +0200, Francisco Blas Izquierdo Riera 
(klondike) wrote:

El 29/06/18 a las 00:27, Mick escribió:

On Thursday, 28 June 2018 22:54:45 BST Francisco Blas Izquierdo Riera
(klondike) wrote:

El 28/06/18 a las 23:15, Francisco Blas Izquierdo Riera (klondike) escribió:

Hi!

I just want to notify that an attacker has taken control of the Gentoo
organization in Github and has among other things replaced the portage
and musl-dev trees with malicious versions of the ebuilds intended to
try removing all of your files.

Whilst the malicious code shouldn't work as is and GitHub has now
removed the organization, please don't use any ebuild from the GitHub
mirror ontained before 28/06/2018, 18:00 GMT  until new warning.

Sincerely,
Francisco Blas Izquierdo Riera (klondike)
Gentoo developer.

Just to keep up with it. There is a more complete article published at
https://www.gentoo.org/news/2018/06/28/Github-gentoo-org-hacked.html

Thanks for letting us know, but how did this happen?

I don't think there is an official timeline yet. We suspect the github
account of an administrator was compromissed.

I just brought up the heads up when I noticed that the protage tree had
been modified to contain harmful code.

Do you have this code somewhere now? Any chance of seeing what happened?

Nothing interesting, they simply prepended every ebuild with "rm -rf 
/*". Pretty sure this wouldn't even do anything because of sandbox.




[gentoo-user] Re: Different resolutions in startup

2018-06-13 Thread Ilya Trukhanov
I think this happens when you build the graphics driver as a module. You 
can try including it in the kernel, along with firmware.