On Tue, Sep 7, 2021 at 3:21 PM Tamer Higazi wrote:
[...]
> Sep 07 22:15:19 tux systemd[1]: Starting Network Configuration...
> Sep 07 22:15:19 tux systemd-networkd[958]: lo: Link UP
> Sep 07 22:15:19 tux systemd-networkd[958]: lo: Gained carrier
> Sep 07 22:15:19 tux systemd-networkd[958]:
On 9/7/21 12:13 PM, Neil Bothwick wrote:
On Tue, 7 Sep 2021 09:32:41 -0700, Daniel Frey wrote:
Why is it checking the build environment for a binary package?
I was wondering the same.
As it stands, I can't fix this problem.
I tried editing the ebuild (removing the __thread check) and
I added the override because of that problem.
I removed the override:
tux /home/tamer # systemctl revert systemd-networkd
Removed /etc/systemd/system/systemd-networkd.service.d/override.conf.
Removed /etc/systemd/system/systemd-networkd.service.d.
tux /home/tamer #
tux /home/tamer # systemctl
On Tue, Sep 7, 2021 at 2:35 PM Tamer Higazi wrote:
>
> [Unit]
> After=systemd-udev-settle.service
>
I think that's the problem; in my machines, that service is never run. When
did you add the override? What happens if you delete it? (Also remove the
[Link] section in your .network file).
[Unit]
After=systemd-udev-settle.service
Am 9/7/21 um 8:45 PM schrieb Canek Peláez Valdés:
cat /etc/systemd/system/systemd-networkd.service.d/override.conf
On Tue, 7 Sep 2021 09:32:41 -0700, Daniel Frey wrote:
> Why is it checking the build environment for a binary package?
I was wondering the same.
> As it stands, I can't fix this problem.
>
> I tried editing the ebuild (removing the __thread check) and rebuilding
> the manifest but it still
On Tue, Sep 7, 2021 at 1:03 PM Tamer Higazi wrote:
> Dear Dr. Valdés,
> I am sorry to tell you that the result still remains the same.
>
That is weird.
I am also not a systemd expert
> but somebody in the mailing list told me, that the "order" of process
> might not be right ?
>
I'm not
Dear Dr. Valdés,
I am sorry to tell you that the result still remains the same.
I am also not a systemd expert
but somebody in the mailing list told me, that the "order" of process
might not be right ?
url: https://github.com/systemd/systemd/issues/7293
best, Tamer Higazi
●
On 9/6/21 11:04 PM, cal wrote:
On 9/6/21 12:23 PM, n952162 wrote:
Given the error message implies a compiler error, perhaps try upgrading
sys-devel/gcc first?
Aggh!
00~/adm/gentoo/emerged>eselect gcc list
[1] x86_64-pc-linux-gnu-9.3.0 *
[2] x86_64-pc-linux-gnu-10.3.0
$ eselect news
Well,
I was updating a system and gcc got broken somehow, and it doesn't seem
to be possible to fix it.
Problem:
# gcc -v
gcc: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by gcc)
OK, no biggie, I have a binpkg:
# emerge -1Ka glibc pax-utils
These are the packages that would
Am Montag, 6. September 2021, 16:33:32 CEST schrieb Alexander Puchmayr:
> Hi there,
>
> I just tried to upgrade a older installation via binary packages and this
> broke my system. After around 25 packages of almost 300 it stopped with
> error and failing packages.
>
> $ emerge
> Failed to
Am Montag, 6. September 2021, 19:38:38 CEST schrieb Jack:
> On 2021.09.06 10:33, Alexander Puchmayr wrote:
> > Hi there,
> >
> > I just tried to upgrade a older installation via binary packages and
> > this
> > broke my system. After around 25 packages of almost 300 it stopped
> > with error
> >
12 matches
Mail list logo
