On 2020-06-15 16:20, J. Roeleveld wrote:
On Monday, June 15, 2020 1:26:06 PM CEST n952162 wrote:
Thank you for the response. Unfortunately it didn't work. The logs are
attached (tgt=portage, system, world) and summarized below.
Perl keeps coming up as a problem, so, as an example, I tried to
On Monday, June 15, 2020 1:26:06 PM CEST n952162 wrote:
> Thank you for the response. Unfortunately it didn't work. The logs are
> attached (tgt=portage, system, world) and summarized below.
>
> Perl keeps coming up as a problem, so, as an example, I tried to build
> perl, including all the
On Sun, 14 Jun 2020 22:07:20 +0200, n952162 wrote:
> I see that there are new lines in the dependencies table that I've never
> encountered before:
>
> [blocks B ] (" x11-base/xorg-proto-2019.2)
>
> I get these (using the emerge from the git repository) for all of
> @world, @system,
On 2020-06-14 10:23, n952162 wrote:
On 2020-06-14 00:05, n952162 wrote:
cool! I'll give that a try tomorrow.
Thank you.
On 2020-06-13 21:42, Andreas K. Hüttel wrote:
Am Donnerstag, 11. Juni 2020, 09:47:50 EEST schrieb n952162:
I haven't clue what to do here. Can somebody supply a good URL
I took the plunge and changed from NAT to "bridged adapter" and I was
able to ssh in - thank you for giving me the impetus.
There are consequences of that change, I'm not sure what they all are
... so I won't leave it like this, but in order to figure out how to get
my system up-to-date, it'll
On 14/06/2020 08:01, n952162 wrote:
I think the problem is, vbox's NAT interface acts as a router, but only
uni-directionally. That means, it will establish a "connection" for
VM-initiated sessions, but there's no mechanism for establishing a
session for external-initiated sessions.
Somebody,
On 2020-06-12 00:43, Jack wrote:
On 2020.06.11 18:05, n952162 wrote:
On 2020-06-11 23:59, Jack wrote:
On 2020.06.11 17:22, n952162 wrote:
On 2020-06-11 23:10, n952162 wrote:
On 2020-06-11 23:05, Jack wrote:
It would really help if you get rid of lots of extraneous
messages in the emerge
On 2020-06-12 00:43, Jack wrote:
That was just after letting "eselect news read" run through.
That sounds like a permission problem, which may end up having an
effect on your other efforts. In my case, it is
/usr/portage/metadata/news, and everything there is root:root and the
actual news
cool! I'll give that a try tomorrow.
Thank you.
On 2020-06-13 21:42, Andreas K. Hüttel wrote:
Am Donnerstag, 11. Juni 2020, 09:47:50 EEST schrieb n952162:
I haven't clue what to do here. Can somebody supply a good URL or
explanation?
In the meantime a new ebuild format version (EAPI) has
Am Donnerstag, 11. Juni 2020, 09:47:50 EEST schrieb n952162:
> I haven't clue what to do here. Can somebody supply a good URL or
> explanation?
>
In the meantime a new ebuild format version (EAPI) has been introduced; your
old portage can't process that, and as a result doesnt understand many
On Friday, 12 June 2020 15:52:50 BST Michael wrote:
> On Friday, 12 June 2020 15:44:05 BST n952162 wrote:
> > And, BTW, is there a reason to do @system if that's a subset of @world?
>
> To rebuild with the latest gcc and work through any convoluted dependencies
> cutting across into world. It
On Friday, 12 June 2020 16:05:04 BST Jack wrote:
> On 2020.06.12 10:38, Michael wrote:
> > On Friday, 12 June 2020 15:00:25 BST Jack wrote:
> >> What about some sort of tagging? Not bundling or packaging, just
> >> occasional (quarterly?) labels, with a matrix indicating how
> >> difficult it
On 2020.06.12 10:38, Michael wrote:
On Friday, 12 June 2020 15:00:25 BST Jack wrote:
What about some sort of tagging? Not bundling or packaging, just
occasional (quarterly?) labels, with a matrix indicating how
difficult it would be to upgrade. A hint to folks who tend to
update less
On Fri, Jun 12, 2020 at 10:48 AM n952162 wrote:
>
> On 2020-06-12 16:42, J. Roeleveld wrote:
> > On 12 June 2020 16:38:28 CEST, Michael wrote:
> >>
> >> Perhaps I misunderstand this, but isn't it as simple as booting off a
> >> LiveCD/
> >> USB, chrooting, changing profiles, cleaning up world
On Friday, 12 June 2020 15:44:05 BST n952162 wrote:
> On 2020-06-12 16:38, Michael wrote:
> > On Friday, 12 June 2020 15:00:25 BST Jack wrote:
> >> On 6/12/20 9:49 AM, Rich Freeman wrote:
> >>> On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
> On 2020-06-12 08:40, n952162 wrote:
> >> BTW,
On Fri, Jun 12, 2020 at 10:38 AM Michael wrote:
>
> On Friday, 12 June 2020 15:00:25 BST Jack wrote:
> > On 6/12/20 9:49 AM, Rich Freeman wrote:
> > >
> > > Ultimately if there was enough interest in something like this the
> > > solution would probably be another distro that just repackages
On Friday, 12 June 2020 15:42:52 BST J. Roeleveld wrote:
> On 12 June 2020 16:38:28 CEST, Michael wrote:
> >On Friday, 12 June 2020 15:00:25 BST Jack wrote:
> >> On 6/12/20 9:49 AM, Rich Freeman wrote:
> >> > On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
> >> >> On 2020-06-12 08:40, n952162
On 2020-06-12 16:38, Michael wrote:
On Friday, 12 June 2020 15:00:25 BST Jack wrote:
On 6/12/20 9:49 AM, Rich Freeman wrote:
On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
On 2020-06-12 08:40, n952162 wrote:
BTW, is it becoming clear why it is best to update Gentoo at least
ever few
On 2020-06-12 16:42, J. Roeleveld wrote:
On 12 June 2020 16:38:28 CEST, Michael wrote:
Perhaps I misunderstand this, but isn't it as simple as booting off a
LiveCD/
USB, chrooting, changing profiles, cleaning up world file and letting
rip with
a full 'emerge -e' @system, followed by @world
On 12 June 2020 16:38:28 CEST, Michael wrote:
>On Friday, 12 June 2020 15:00:25 BST Jack wrote:
>> On 6/12/20 9:49 AM, Rich Freeman wrote:
>> > On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
>> >> On 2020-06-12 08:40, n952162 wrote:
>> BTW, is it becoming clear why it is best to update
On Friday, 12 June 2020 15:00:25 BST Jack wrote:
> On 6/12/20 9:49 AM, Rich Freeman wrote:
> > On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
> >> On 2020-06-12 08:40, n952162 wrote:
> BTW, is it becoming clear why it is best to update Gentoo at least
> ever few months? :)
> >>>
> >>>
On 6/12/20 9:49 AM, Rich Freeman wrote:
On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
On 2020-06-12 08:40, n952162 wrote:
BTW, is it becoming clear why it is best to update Gentoo at least
ever few months? :)
Well, yes, but it's really pretty onerous. If you have gentoo in
embedded
On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote:
>
> On 2020-06-12 08:40, n952162 wrote:
> >
> >>
> >> BTW, is it becoming clear why it is best to update Gentoo at least
> >> ever few months? :)
> >
> >
> > Well, yes, but it's really pretty onerous. If you have gentoo in
> > embedded systems,
On Fri, Jun 12, 2020 at 2:40 AM n952162 wrote:
>
> Presumably, 13.0, unless some process had already made the 13.0 -> 17.0
> jump without my knowledge.
Ok, you're in fairly uncharted waters. The impact is mainly to gcc so
if you haven't updated that then most likely nothing is broken yet,
and
On 2020-06-12 08:40, n952162 wrote:
BTW, is it becoming clear why it is best to update Gentoo at least
ever few months? :)
Well, yes, but it's really pretty onerous. If you have gentoo in
embedded systems, you've got to spend considerable administrative effort
in each one just
On 2020-06-12 01:09, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 5:45 PM n952162 wrote:
* portage-2.3.89-bug-718578.patch BLAKE2B SHA512 size ;-)
... [ ok ]
* Please follow the instructions in the news item:
* 2019-06-05-amd64-17-1-profiles-are-now-stable
* or choose the
On Thu, Jun 11, 2020 at 5:45 PM n952162 wrote:
>
>
> * portage-2.3.89-bug-718578.patch BLAKE2B SHA512 size ;-)
> ... [ ok ]
> * Please follow the instructions in the news item:
> * 2019-06-05-amd64-17-1-profiles-are-now-stable
> * or choose the 17.0 profile.
> * ERROR:
On 2020.06.11 18:05, n952162 wrote:
On 2020-06-11 23:59, Jack wrote:
On 2020.06.11 17:22, n952162 wrote:
On 2020-06-11 23:10, n952162 wrote:
On 2020-06-11 23:05, Jack wrote:
It would really help if you get rid of lots of extraneous
messages in the emerge output by reading all the new news
On 2020-06-11 23:59, Jack wrote:
On 2020.06.11 17:22, n952162 wrote:
On 2020-06-11 23:10, n952162 wrote:
On 2020-06-11 23:05, Jack wrote:
It would really help if you get rid of lots of extraneous messages
in the emerge output by reading all the new news items (even if you
already read them
On 2020-06-11 23:45, n952162 wrote:
On 2020-06-11 23:20, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:43 PM n952162 wrote:
On 2020-06-11 22:35, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:28 PM n952162 wrote:
On 2020-06-11 22:01, Rich Freeman wrote:
Try:
USE="python_targets_python3_6
On 2020.06.11 17:22, n952162 wrote:
On 2020-06-11 23:10, n952162 wrote:
On 2020-06-11 23:05, Jack wrote:
It would really help if you get rid of lots of extraneous messages
in the emerge output by reading all the new news items (even if you
already read them elsewhere) and finish updating
On 2020-06-11 23:20, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:43 PM n952162 wrote:
On 2020-06-11 22:35, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:28 PM n952162 wrote:
On 2020-06-11 22:01, Rich Freeman wrote:
Try:
USE="python_targets_python3_6 -python_targets_python3_7
On 2020-06-11 23:06, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:10 PM n952162 wrote:
On 2020-06-11 22:01, Rich Freeman 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.
(dependency required
On 2020-06-11 23:10, n952162 wrote:
On 2020-06-11 23:05, Jack wrote:
It would really help if you get rid of lots of extraneous messages in
the emerge output by reading all the new news items (even if you
already read them elsewhere) and finish updating your config files (or
deleting the update
On Thu, Jun 11, 2020 at 4:43 PM n952162 wrote:
>
> On 2020-06-11 22:35, Rich Freeman wrote:
> > On Thu, Jun 11, 2020 at 4:28 PM n952162 wrote:
> >> On 2020-06-11 22:01, Rich Freeman wrote:
> >>> Try:
> >>> USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
> >>> emerge -p1v
On 2020-06-11 23:05, Jack wrote:
It would really help if you get rid of lots of extraneous messages in
the emerge output by reading all the new news items (even if you
already read them elsewhere) and finish updating your config files (or
deleting the update files if you already updated the
On 2020-06-11 22:35, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:28 PM n952162 wrote:
On 2020-06-11 22:01, Rich Freeman wrote:
Try:
USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
emerge -p1v =sys-apps/portage-2.3.99-r2
Sorry, try again.
* IMPORTANT: 2 config
On Thu, Jun 11, 2020 at 4:10 PM n952162 wrote:
>
> On 2020-06-11 22:01, Rich Freeman 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.
> >> (dependency required by
> >>
It would really help if you get rid of lots of extraneous messages in
the emerge output by reading all the new news items (even if you
already read them elsewhere) and finish updating your config files (or
deleting the update files if you already updated the actual config
files.) The more
On 2020-06-11 22:01, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 3:36 PM n952162 wrote:
On 2020-06-11 14:47, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick wrote:
Most likely what you're probably going to end up wanting to try is:
USE="python_targets_python3_6
On Thu, Jun 11, 2020 at 4:28 PM n952162 wrote:
>
> On 2020-06-11 22:01, Rich Freeman wrote:
> > Try:
> > USE="python_targets_python3_6 -python_targets_python3_7 -rsync-verify"
> > emerge -p1v =sys-apps/portage-2.3.99-r2
> >
>
> Sorry, try again.
>
> * IMPORTANT: 2 config files in '/etc/portage'
On 2020-06-11 22:01, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 3:36 PM n952162 wrote:
On 2020-06-11 14:47, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick wrote:
Most likely what you're probably going to end up wanting to try is:
USE="python_targets_python3_6
On Thu, Jun 11, 2020 at 3:36 PM n952162 wrote:
>
> On 2020-06-11 14:47, Rich Freeman wrote:
> > On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick wrote:
> >
> > Most likely what you're probably going to end up wanting to try is:
> > USE="python_targets_python3_6 -python_targets_python3_7" emerge
On 2020-06-11 14:47, Rich Freeman wrote:
On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick wrote:
sudo emerge -vauU portage 2>&1 | tee -a portage.200611
!!! The following update has been skipped due to unsatisfied
dependencies:
sys-apps/portage:0
selected:
On 2020-06-11 10:10, Neil Bothwick wrote:
On Thu, 11 Jun 2020 08:47:50 +0200, n952162 wrote:
I haven't clue what to do here. Can somebody supply a good URL or
explanation?
The emerge(1) man page says:
EAPI The EAPI variable in an ebuild(5) file is used to mask
packages that are
On Thu, Jun 11, 2020 at 4:10 AM Neil Bothwick wrote:
>
> >
> > sudo emerge -vauU portage 2>&1 | tee -a portage.200611
> >
> > !!! The following update has been skipped due to unsatisfied
> > dependencies:
> >
> > sys-apps/portage:0
> >
> >selected:
On Thu, 11 Jun 2020 08:47:50 +0200, n952162 wrote:
> I haven't clue what to do here. Can somebody supply a good URL or
> explanation?
>
> The emerge(1) man page says:
>
> EAPI The EAPI variable in an ebuild(5) file is used to mask
> packages that are not
> supported
I haven't clue what to do here. Can somebody supply a good URL or
explanation?
The emerge(1) man page says:
EAPI The EAPI variable in an ebuild(5) file is used to mask
packages that are not
supported by the current version of portage. Packages
masked by EAPI can
48 matches
Mail list logo
