public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: bobwxc <bobwxc@88.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] State of emergency is now in effect.
Date: Sat, 30 Jan 2021 21:33:57 +0800	[thread overview]
Message-ID: <95daaf7d-d734-88ed-af86-dbf51a97f01b@88.com> (raw)
In-Reply-To: <140f70da-4daf-238d-bb29-f31abcd3a154@verizon.net>


[-- Attachment #1.1: Type: text/plain, Size: 1946 bytes --]

在 2021/1/30 下午5:37, Alan Grimes 写道:
> On one terminal I have this bullshit going on, at this pace it will take
> longer than my natural lifespan to clear this nonsense:
> fuckit, I'm adding this shit to the goddamned, cock-sucking make.conf
> and there's nothing you can do to stop me!!! Why for fuck's sake do I
> have to fix this shit at 4:30 am and can't get it all done in the middle
> of the afternoon when I started???
>
> Why am I required to manually update a dozen config files just to get
> things moving each time I do this?? Is it really impossible to just keep
> doing what I set up last time?, you know the time when I stopped messing
> with it because it was working???
>
>
> Do you have any idea how broken it is right now? It will look like it's
> emerging stuff, then start no processes, decompress any files, compile
> any code, or anything, just tick through as if it were working very very
> very slowly but not actually do anything...
>
> So this version of portage is the first one I've seen that is literally
> incapable of emerging a pacakge!   Unbelievable, a package manager
> incapable of performing its primary function...
>
> I have no idea how I'm going to fix this mess this time, I'm going to
> have to mask the current version of portage and get a binary of one that
> is capable of emerging and put that in.
>
> How did you break it this bad, HOW????
>
> All you had to do was nothing and it would still be working!!!
>
>
  _ _
| | __ _ _ __   __ _ _   _  __ _  __ _  ___  | |
| |/ _` | '_ \ / _` | | | |/ _` |/ _` |/ _ \ | |
| | (_| | | | | (_| | |_| | (_| | (_| |  __/ |_|
|_|\__,_|_| |_|\__, |\__,_|\__,_|\__, |\___| (_)
                |___/             |___/
Please pay attention to your words and don't yell in the list to vent 
your emotions.


-- 
bobwxc
F645 5C7A 08E8 A637 24C6  D59E 36E9 4EAB B53E 516B



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2021-01-30 13:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <140f70da-4daf-238d-bb29-f31abcd3a154.ref@verizon.net>
2021-01-30  9:37 ` [gentoo-user] State of emergency is now in effect Alan Grimes
2021-01-30 10:48   ` Michael
2021-01-30 14:58     ` Dr Rainer Woitok
2021-01-30 15:20       ` Arve Barsnes
2021-01-30 15:38         ` Michael
2021-01-30 16:21         ` Dr Rainer Woitok
2021-01-30 16:55           ` Arve Barsnes
2021-01-30 17:07             ` Neil Bothwick
2021-01-30 15:28       ` Alexey Mishustin
2021-01-30 15:34         ` [gentoo-user] " Grant Edwards
2021-01-30 16:30         ` [gentoo-user] " Dr Rainer Woitok
2021-02-04 18:43     ` antlists
2021-01-30 13:33   ` bobwxc [this message]
2021-01-30 14:34   ` Neil Bothwick
2021-01-31 14:10   ` Alessandro Barbieri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95daaf7d-d734-88ed-af86-dbf51a97f01b@88.com \
    --to=bobwxc@88.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox