Re: [gentoo-user] Portage+gentoolkit blockage
On Mon, Oct 28, 2019 at 03:36:00PM +1100, Adam Carter wrote > On Mon, Oct 28, 2019 at 3:23 PM Walter Dnes wrote: > > > I went 41 days without emerging (yeah, I know). Anyhow, emerge first > > wants me to update portage, but I run into problems. Can I safely > > unmerge gentoolkit and re-emerge it afterwards? > > Its not part of @system, so should be fine. Thanks. I unmerged gentoolkit (0.4.6), updated portage, and re-emerged gentoolkit (0.4.6). Wierd that it comes back with the same version, but portage can't be updated when it's present. > Whenever i'm not sure I just quickpkg first so get it back with tar > if need be. That prompted me to dig deeper. According to https://wiki.gentoo.org/wiki/System_set_%28Portage%29 you can gat a listing of the system set with either of... emerge --pretend @system eix -c --system -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Portage+gentoolkit blockage
On Mon, Oct 28, 2019 at 3:23 PM Walter Dnes wrote: > I went 41 days without emerging (yeah, I know). Anyhow, emerge first > wants me to update portage, but I run into problems. Can I safely > unmerge gentoolkit and re-emerge it afterwards? > Its not part of @system, so should be fine. Whenever i'm not sure I just quickpkg first so get it back with tar if need be.
[gentoo-user] Portage+gentoolkit blockage
I went 41 days without emerging (yeah, I know). Anyhow, emerge first wants me to update portage, but I run into problems. Can I safely unmerge gentoolkit and re-emerge it afterwards? = [i660][root][~] emerge --oneshot portage Calculating dependencies... done! [ebuild U ] sys-apps/portage-2.3.76 [2.3.69] [blocks B ] https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages = -- Walter Dnes I don't run "desktop environments"; I run useful applications
[gentoo-user] Consolekit and elogind switch questions
Howdy, I subscribe to -dev and read things to get a heads up mostly. I noticed a news item being started concerning consolekit and switching to elogind. From my understanding it is similar to the difference of udev and eudev in that it just pulls the code needed when not using systemd and friends. I do have consolekit here and since the news item and the migration guide mentions removing consolekit, I'm pretty sure the news item has my name all over it and I'm about to switch. Given the outdated nature of consolekit, may be a good thing. Before I start down this road, I have questions. What exactly is it? Is it the screen that pops up when X starts and asks for my login? Is it something inside KDE itself that manages the Desktop itself? I think the first one is sddm. So I'm suspecting it is the later one. Or is it something that I won't even notice the change in? Something that runs in the background and I don't see? Just trying to figure out exactly what it is I'm changing, not that I'm against it because it seems it is needed. Has anyone already switched and if so, was it fairly straight forward and easy or did it require something outside the norm, like shutting down X and doing from a console? I generally update etc from a Konsole inside KDE. One of the things mentioned something about a session becoming corrupted during this is one reason I ask. This comment: "Migration is easy, but if run from within a consolekit session that session may become broken." I'm not sure but I think Konsole uses consolekit. Heck, console itself may use it too. If someone has a screenshot that shows the difference, I'd love to see it. Post a link to a pic hosting site, send it off list or whatever works. I tried to google for screenshots but most mention Gnome and I use KDE. I also poked around Gentoo but it seems to be Gnome as well. Add in that I'm not sure what I'm looking for, I may not know it when I see it anyway. LOL Also, are there any other options to elogind? Is that the only option when using KDE? Thanks to anyone who can clear up some of this confusion on my part. Dale :-) :-)
Bouncing messages from gentoo-user@lists.gentoo.org
Some messages to you could not be delivered. If you're seeing this message it means things are back to normal, and it's merely for your information. Here is the list of the bounced messages: - 188350
Re: [gentoo-user] Udev and eudev clash. Something wants to remove eudev and install udev.
[2019-10-27 18:47] Dale > > part text/plain 30K > Howdy, Hi, > I'm trying to do my weekly update. I use eudev but something seems to > want plain udev and to remove eudev while at it. I have udev masked so > emerge knows not to install it. This is what emerge spits out with the > -t option in use. Keep in mind, some options are in make.conf but the > output should show the needed results. [..] > The following mask changes are necessary to proceed: > (see "package.unmask" in the portage(5) man page for more details) > # required by virtual/libudev-232-r1::gentoo[-systemd] > # required by dev-libs/libgudev-233-r1::gentoo > # required by xfce-base/thunar-1.8.9::gentoo[udisks] > # required by xfce-base/xfce4-meta-4.14-r1::gentoo > # required by @selected > # required by @world (argument) > # /etc/portage/package.mask/package.mask: > =sys-fs/udev-242 eudev was forgotten in the deps for virtual/libudev-232-r1, there should be a fixed virtual/libudev-232-r2 in the tree already. Resync and it should (hopefully) just work™. [..] -- Simon Thelen
[gentoo-user] Udev and eudev clash. Something wants to remove eudev and install udev.
Howdy, I'm trying to do my weekly update. I use eudev but something seems to want plain udev and to remove eudev while at it. I have udev masked so emerge knows not to install it. This is what emerge spits out with the -t option in use. Keep in mind, some options are in make.conf but the output should show the needed results. root@fireball / # emerge -uvaDN world -t These are the packages that would be merged: Calculating dependencies... done! [nomerge ] kde-frameworks/plasma-5.63.0:5/5.63::gentoo USE="X -debug -doc (-gles2) -test -wayland" [nomerge ] dev-qt/qtquickcontrols-5.12.5:5/5.12::gentoo USE="widgets -debug -test" [nomerge ] dev-qt/qtwidgets-5.12.5-r1:5/5.12::gentoo USE="gtk png xcb -debug (-gles2) -test" [nomerge ] dev-qt/qtgui-5.12.5:5/5.12::gentoo USE="dbus egl evdev gif jpeg libinput png udev xcb -accessibility -debug -eglfs (-gles2) -ibus -test -tslib -tuio -vnc -wayland" [nomerge ] x11-libs/xcb-util-wm-0.4.1-r2::gentoo USE="-doc -static-libs -test" ABI_X86="(64) -32 (-x32)" [nomerge ] x11-libs/libxcb-1.13.1:0/1.12::gentoo USE="xkb -doc (-selinux) -static-libs -test" ABI_X86="32 (64) (-x32)" [nomerge ] dev-lang/python-3.6.9:3.6/3.6m::gentoo USE="gdbm ipv6 ncurses readline sqlite ssl (threads) xml -bluetooth -build -examples -hardened -libressl -test -tk -wininst" [nomerge ] app-eselect/eselect-python-20171204::gentoo [nomerge ] app-admin/eselect-1.4.15::gentoo USE="-doc -emacs -vim-syntax" [nomerge ] sys-apps/sed-4.5::gentoo USE="nls -acl -forced-sandbox (-selinux) -static" [nomerge ] sys-devel/gettext-0.19.8.1::gentoo USE="java ncurses nls openmp -acl -cvs -cxx -doc -emacs -git -static-libs" ABI_X86="32 (64) (-x32)" [nomerge ] dev-java/java-config-2.2.0-r4:2::gentoo USE="-test" PYTHON_TARGETS="python2_7 python3_6 -python3_5 (-python3_7)" [nomerge ] sys-apps/portage-2.3.76::gentoo USE="(ipc) native-extensions rsync-verify -build -doc -epydoc -gentoo-dev (-selinux) -xattr" PYTHON_TARGETS="python2_7 python3_6 (-pypy) -python3_5 (-python3_7)" [nomerge ] sys-apps/coreutils-8.30::gentoo USE="nls (split-usr) xattr -acl -caps -gmp -hostname -kill -multicall (-selinux) -static -test -vanilla" [nomerge ] sys-apps/attr-2.4.47-r2::gentoo USE="nls (split-usr) -static-libs" ABI_X86="32 (64) (-x32)" [nomerge ] sys-devel/autoconf-2.69-r4:2.69::gentoo USE="-emacs" [nomerge ] dev-lang/perl-5.28.2-r1:0/5.28::gentoo USE="berkdb gdbm -debug -doc -ithreads" [nomerge ] app-admin/perl-cleaner-2.27::gentoo [nomerge ] app-portage/portage-utils-0.80::gentoo USE="nls openmp qmanifest qtegrity -libressl -static" [nomerge ] app-crypt/libb2-0.98.1-r1::gentoo USE="openmp -native-cflags -static-libs" [nomerge ] sys-devel/gcc-8.3.0-r1:8.3.0::gentoo USE="(cxx) fortran (multilib) nls nptl openmp pch (pie) sanitize ssp vtv (-altivec) -debug -doc (-fixed-point) -go -graphite (-hardened) (-jit) (-libssp) -mpx -objc -objc++ -objc-gc -pgo -systemtap -test -vanilla" [nomerge ] sys-devel/bison-3.1::gentoo USE="nls -examples -static -test" [ebuild R ] sys-devel/flex-2.6.4-r1::gentoo USE="nls -static -test" ABI_X86="32* (64) (-x32)" 0 KiB [nomerge ] sys-libs/glibc-2.29-r2:2.2::gentoo USE="multiarch (multilib) (split-usr) ssp -audit -caps (-cet) (-compile-locales) -doc -gd -headers-only -nscd -profile (-selinux) -suid -systemtap -test (-vanilla)" [nomerge ] virtual/pkgconfig-1::gentoo ABI_X86="32 (64) (-x32)" [nomerge ] dev-util/pkgconfig-0.29.2::gentoo USE="-hardened -internal-glib" ABI_X86="32 (64) (-x32)" [nomerge ] dev-libs/glib-2.60.6:2::gentoo USE="dbus (mime) -debug (-fam) -gtk-doc (-selinux) -static-libs -systemtap -test -utils -xattr" ABI_X86="32 (64) (-x32)" [nomerge ] gnome-base/dconf-0.30.1::gentoo USE="-gtk-doc -test" [nomerge ] sys-apps/dbus-1.12.16::gentoo USE="X -debug -doc -elogind (-selinux) -static-libs -systemd -test -user-session" ABI_X86="32 (64) (-x32)" [nomerge ] app-text/xmlto-0.0.28-r1::gentoo USE="text -latex" [nomerge ] app-text/docbook-xsl-stylesheets-1.79.1-r2::gentoo USE="-ruby" [nomerge ] app-text/build-docbook-catalog-1.21::gentoo [nomerge ] sys-apps/util-linux-2.33.2::gentoo USE="cramfs ncurses nls pam readline (split-usr) suid udev unicode -build -caps -fdformat -kill -python (-selinux) -slang -static-libs -systemd -test -tty-helpers" ABI_X86="32 (64) (-x32)"
Re: [gentoo-user] per package parallel build
Mick wrote:
> On Friday, 25 October 2019 18:01:57 BST Dale wrote:
>> Mick wrote:
>>> PS. In an ideal AI world, portage would know how much memory is necessary
>>> for a given package and would auto-adjust the number of jobs to minimise
>>> swapping given any amount of RAM. In an even more ideal world, it would
>>> be able to do this in real time. :-)
>> I agree that it would be nice if emerge could do that automatically,
>> although I have no clue how to do that or even if it can be done at
>> all. Back when I had less memory, I could let FF, LOo or another
>> package run at full speed but only if it was only one of those packages
>> at a time. Thing is, on occasion two or more of those updates would hit
>> and due to the long compile times, end up compiling at the same time.
>> Do you think there is a way for the devs to set up a method to tell
>> emerge not to emerge certain packages at the same time? In other words,
>> if Firefox is emerging, LOo is held until it is done or vice versa.
>> Maybe even have it so others can be listed. The list of large packages
>> are likely small but they can have a huge impact on systems with less
>> memory.
>>
>> You think that a feature worth asking the devs about? Maybe they can
>> figure out a way to implement that??
>>
>> Dale
>>
>> :-) :-)
> Well, ebuilds with known large compiles have specific tests at present, e.g.
> chromium, FF, et al., run checks on available disk space for /var/tmp/portage
> and warn the user accordingly. In firefox-70.0.ebuild we see this:
>
> ...
> pkg_pretend() {
> # Ensure we have enough disk space to compile
> if use pgo || use lto || use debug || use test ; then
> CHECKREQS_DISK_BUILD="8G"
> else
> CHECKREQS_DISK_BUILD="4G"
> fi
>
> check-reqs_pkg_setup
> }
>
> I guess a lot can be included in such checks, but I have no idea how to do
> it,
> or how complicated an ebuild would get as a result. The problem with RAM
> usage is that it changes continuously. You open a browser, or some large
> PDF,
> or LO and more RAM is being used, just at the moment an ebuild decides to run
> a check on available RAM. It can't guess if you will shut down your
> applications and log out of your desktop the next moment to free up more
> memory, if you will shut down web servers, databases or whatever else you may
> be running in the background and drop to a console. For this reason I assume
> such a measure won't be implemented in rush and even if it did, it would
> annoy
> people, especially if they are asked to add USE="I-really-know-what-I-am-
> doing" to allow the compile to start.
I was hoping for something more simple. Nothing in the ebuild just a
list of packages that emerge won't run at the same time. Let's say the
big ones are included in the list, Seamonkey, Firefox, LOo and maybe a
couple others. When emerge is run, Firefox and LOo is to be updated.
Emerge itself knows not to update both so if one is updating and the
other is next in line, then it waits until the other is finished before
starting the next big one. I would think the code should be in emerge
itself not the ebuild. That way the user can determine what their
particular machine can handle.
Like you, I'm not sure how to code that. Of course, I've read about the
devs doing some complicated things that I don't grasp. After all, it
calculates dependencies a lot faster than I could do on paper. lol
Dale
:-) :-)
Re: [gentoo-user] issues.
On Sun, 27 Oct 2019 11:20:20 -0400, Alan Grimes wrote: > 1. Grub2 menu DOES NOT ACCEPT KEYBOARD INPUT! > > -- Upgraded my ram to 64gb, couldn't run memtest because grub2 is > broken. Try toggling the legacy USB setting in BIOS. > > > 2. My current combination of Linux-Headers-5.2, kernel 5.2 and nvidia > drivers is UNSTABLE and crashes X11 to command line when the steam > client updates itself, breaking my long running number theory code, lost > about 2 days of work so far. Can't you run the code in screen or tmux? -- Neil Bothwick The horizon of many people is a circle with a radius of zero. They call this their point of view. -- Albert Einstein pgpvkqASiBrNK.pgp Description: OpenPGP digital signature
Re: [gentoo-user] why can't I emerge portage-2.3.67?
On Sun, 27 Oct 2019 17:37:53 +0100, n952162 wrote: > Okay, I'm working on that, but apparently, the *emerge --sync* I did a > few minutes ago left this link dangling: > > lrwxrwxrwx 1 root root 59 Jan 23 2018 make.profile -> > ../../usr/portage/profiles/default/linux/amd64/13.0/desktop Use eselect profile to select a current profile, but first read the news item relating to the 17.0 profile switch with eselect news. -- Neil Bothwick Why do kamikaze pilots wear helmets? pgpMsjotnFqfj.pgp Description: OpenPGP digital signature
Re: [gentoo-user] why can't I emerge portage-2.3.67?
Okay, I'm working on that, but apparently, the *emerge --sync* I did a few minutes ago left this link dangling: lrwxrwxrwx 1 root root 59 Jan 23 2018 make.profile -> ../../usr/portage/profiles/default/linux/amd64/13.0/desktop The contents of //usr/portage/profiles/default/linux/amd64is now: $ lf /usr/portage/profiles/default/linux/amd64/ 17.0/ 17.1/ eapi package.use.mask parent Is my system now killed? On 10/27/19 15:10, Mick wrote: On Sunday, 27 October 2019 16:02:53 GMT n952162 wrote: But ~amd64 means that it's unstable. I want to use a stable version of portage. That's why I went to 2.3.69 I beg your pardon, I copied the portage version from the title of your post erroneously. Let me start again: sys-apps/portage-2.3.76 is the *current* stable version of portage, irrespective of what your present state of portage tree, which is out of sync with the mirrors, thinks. The way forward is to mark sys-apps/portage-2.3.76 as ~amd64 *temporarily* only, then emerge it, then re-sync and finally unmark sys-apps/portage-2.3.76 as ~amd64 in your /etc. Following a resync your local tree will be brought up to date and portage will no longer require further updates, since you will have installed the latest stable version (as of this morning at least). (Sorry, Mick, for the private msg - I always forget that thunderbird replies directly, and that I have to re-enter the list every time) No problem. :-)
[gentoo-user] issues.
Here are the issues I'm currently having. 1. Grub2 menu DOES NOT ACCEPT KEYBOARD INPUT! -- Upgraded my ram to 64gb, couldn't run memtest because grub2 is broken. 2. My current combination of Linux-Headers-5.2, kernel 5.2 and nvidia drivers is UNSTABLE and crashes X11 to command line when the steam client updates itself, breaking my long running number theory code, lost about 2 days of work so far. Actually, when this happens the command line is garbled and I have to issue "reset" to gain control again. (current status: 0x1b39b150 2201021200121101001110012211022102200202121120120220200020102012221201200221211022200210212_3 ) When either of those numbers rolls over, the program will leave the inner loop and the outer loop will increment, the problem essentially grows exponentially and will run very fast for small i, but when it gets up to 49 well it takes many months...) A threadripper might be able to handle the i=50 block, I don't expect to find a number until the i=51 block... The last number I found is: 24014998963383302600955162866787153652444049 The weird thing is that all the numbers this code has found were done with a Phenom II, 1090T. My Ryzen 1800x hasn't found a single new number despite being 3x faster. -- Clowns feed off of funny money; Funny money comes from the FED so NO FED -> NO CLOWNS!!! Powers are not rights.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
Please don't top-post in this group.
On Sunday, 27 October 2019 16:44:28 GMT n952162 wrote:
> On 10/27/19 15:40, Peter Humphrey wrote:
> > On Sunday, 27 October 2019 16:03:45 GMT n952162 wrote:
> >> On 10/27/19 14:21, Peter Humphrey wrote:
> >>> What does eix tell you after 'emerge --sync && eix-update'?
> >>>
> >>* To update portage, run 'emerge --oneshot portage' now.
> >
> > No, that's not from eix; it's from portage.
> >
> > Now that you've updated eix, what does 'eix -e portage' tell you?
>
> $ eix -e portage
> [?] sys-apps/portage
> Available versions: *2.3.6 *2.3.8 ~*2.3.13 *2.3.13-r1 ~*2.3.14
> ~*2.3.16 *2.3.19-r1 ~*2.3.20 ** {build doc epydoc +ipc
> +native-extensions python_targets_pypy python_targets_python2_7
> python_targets_python3_4 python_targets_python3_5
> python_targets_python3_6 selinux xattr}
> Installed versions: 2.3.13-r1(00:36:49 01/08/18)(ipc
> native-extensions python_targets_python2_7 python_targets_python3_5
> xattr -build -doc -epydoc -python_targets_pypy -python_targets_python3_4
> -python_targets_python3_6 -selinux)
> Homepage: https://wiki.gentoo.org/wiki/Project:Portage
> Description: Portage is the package management and
> distribution system for Gentoo
That tells me you haven't updated portage since 01/08/18. No wonder you have
problems. Is it true? If so, you have a big job on your hands, and it may be
quicker and easier just to wipe and reinstall.
But, assuming you really have run eix-update today, eix should be showing
this:
Available versions: 2.3.66-r1 2.3.69{tbz2} [m]2.3.76 ~2.3.77-r1 ~2.3.78-r1
***l {build doc epydoc gentoo-dev +ipc +native-extensions +rsync-verify
selinux xattr KERNEL="linux" PYTHON_TARGETS="pypy python2_7 python3_5
python3_6 python3_7"}
--
Regards,
Peter.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
$ eix -e portage
[?] sys-apps/portage
Available versions: *2.3.6 *2.3.8 ~*2.3.13 *2.3.13-r1 ~*2.3.14
~*2.3.16 *2.3.19-r1 ~*2.3.20 ** {build doc epydoc +ipc
+native-extensions python_targets_pypy python_targets_python2_7
python_targets_python3_4 python_targets_python3_5
python_targets_python3_6 selinux xattr}
Installed versions: 2.3.13-r1(00:36:49 01/08/18)(ipc
native-extensions python_targets_python2_7 python_targets_python3_5
xattr -build -doc -epydoc -python_targets_pypy -python_targets_python3_4
-python_targets_python3_6 -selinux)
Homepage: https://wiki.gentoo.org/wiki/Project:Portage
Description: Portage is the package management and
distribution system for Gentoo
On 10/27/19 15:40, Peter Humphrey wrote:
On Sunday, 27 October 2019 16:03:45 GMT n952162 wrote:
On 10/27/19 14:21, Peter Humphrey wrote:
What does eix tell you after 'emerge --sync && eix-update'?
* To update portage, run 'emerge --oneshot portage' now.
No, that's not from eix; it's from portage.
Now that you've updated eix, what does 'eix -e portage' tell you?
Re: [gentoo-user] why can't I emerge portage-2.3.67?
On Sunday, 27 October 2019 16:03:45 GMT n952162 wrote: > On 10/27/19 14:21, Peter Humphrey wrote: > > What does eix tell you after 'emerge --sync && eix-update'? > > * To update portage, run 'emerge --oneshot portage' now. No, that's not from eix; it's from portage. Now that you've updated eix, what does 'eix -e portage' tell you? -- Regards, Peter.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
On 10/27/19 14:21, Peter Humphrey wrote: What does eix tell you after 'emerge --sync && eix-update'? * To update portage, run 'emerge --oneshot portage' now.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
Right. But I can't --sync. But beyond that, why does emerge say there are no ebuilds when there are? On 10/27/19 14:32, Mick wrote: On Sunday, 27 October 2019 13:21:04 GMT Peter Humphrey wrote: On Sunday, 27 October 2019 15:11:56 GMT n952162 wrote: When I enter: sudo emerge =sys-apps/portage-2.3.69 I get the response: emerge: there are no ebuilds to satisfy "=sys-apps/portage-2.3.69". but this version is listed on packages.gentoo.org/packages/sys-apps/portage as being an available Version https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2. 3. 69.ebuild I'm trying to emerge 2.3.69 because when I don't specify any version, emerge gives me this: The following keyword changes are necessary to proceed: ... =sys-apps/portage-2.3.67 ~amd64 and 2.3.67 isn't even listed as being available. What does eix tell you after 'emerge --sync && eix-update'? I sync'ed this morning and sys-apps/portage-2.3.76 is the current stable version. A re-sync as Peter suggests ought to fix this problem.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
On Sunday, 27 October 2019 16:02:53 GMT n952162 wrote: > But ~amd64 means that it's unstable. I want to use a stable version of > portage. > > That's why I went to 2.3.69 I beg your pardon, I copied the portage version from the title of your post erroneously. Let me start again: sys-apps/portage-2.3.76 is the *current* stable version of portage, irrespective of what your present state of portage tree, which is out of sync with the mirrors, thinks. The way forward is to mark sys-apps/portage-2.3.76 as ~amd64 *temporarily* only, then emerge it, then re-sync and finally unmark sys-apps/portage-2.3.76 as ~amd64 in your /etc. Following a resync your local tree will be brought up to date and portage will no longer require further updates, since you will have installed the latest stable version (as of this morning at least). > (Sorry, Mick, for the private msg - I always forget that thunderbird > replies directly, and that I have to re-enter the list every time) No problem. :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
But ~amd64 means that it's unstable. I want to use a stable version of portage. That's why I went to 2.3.69 (Sorry, Mick, for the private msg - I always forget that thunderbird replies directly, and that I have to re-enter the list every time) On 10/27/19 14:48, Mick wrote: On Sunday, 27 October 2019 15:44:16 GMT you wrote: oh, you're saying that it *should* allow me to find portage-2.3.69, but because something is screwed up in my configuration, that's not working properly? If your portage was in sync with a mirror it would report version 2.3.67 as stable and allow you to upgrade to it. Since it is not in sync, it reports 2.3.67 as ~amd64. So set it as such in / etc/portage/package.accept_keywords and emerge it. Then sync.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
On Sunday, 27 October 2019 13:21:04 GMT Peter Humphrey wrote: > On Sunday, 27 October 2019 15:11:56 GMT n952162 wrote: > > When I enter: > >sudo emerge =sys-apps/portage-2.3.69 > > > > I get the response: > >emerge: there are no ebuilds to satisfy "=sys-apps/portage-2.3.69". > > > > but this version is listed on > > packages.gentoo.org/packages/sys-apps/portage as being an available > > Version > > > > https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2. > > 3. 69.ebuild > > > > I'm trying to emerge 2.3.69 because when I don't specify any version, > > emerge gives me this: > > > > The following keyword changes are necessary to proceed: > > ... > > > > =sys-apps/portage-2.3.67 ~amd64 > > > > and 2.3.67 isn't even listed as being available. > > What does eix tell you after 'emerge --sync && eix-update'? I sync'ed this morning and sys-apps/portage-2.3.76 is the current stable version. A re-sync as Peter suggests ought to fix this problem. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] why can't I emerge portage-2.3.67?
On Sunday, 27 October 2019 15:11:56 GMT n952162 wrote: > When I enter: > >sudo emerge =sys-apps/portage-2.3.69 > > I get the response: > >emerge: there are no ebuilds to satisfy "=sys-apps/portage-2.3.69". > > but this version is listed on > packages.gentoo.org/packages/sys-apps/portage as being an available Version > > https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3. > 69.ebuild > > I'm trying to emerge 2.3.69 because when I don't specify any version, > emerge gives me this: > > The following keyword changes are necessary to proceed: > ... > =sys-apps/portage-2.3.67 ~amd64 > > and 2.3.67 isn't even listed as being available. What does eix tell you after 'emerge --sync && eix-update'? -- Regards, Peter.
[gentoo-user] why can't I emerge portage-2.3.67?
When I enter: sudo emerge =sys-apps/portage-2.3.69 I get the response: emerge: there are no ebuilds to satisfy "=sys-apps/portage-2.3.69". but this version is listed on packages.gentoo.org/packages/sys-apps/portage as being an available Version https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.69.ebuild I'm trying to emerge 2.3.69 because when I don't specify any version, emerge gives me this: The following keyword changes are necessary to proceed: ... =sys-apps/portage-2.3.67 ~amd64 and 2.3.67 isn't even listed as being available.
