Weird update behavior today, should I be worried?

General system Pacman
1

Hello World,

So I updated today and decided to clean build, everything worked fine until it got to the part pasted below at which point it got suck on a loop for a good 10 minutes or more with that amd package.

Finally it progressed and went on to update brave and other stuff, but after a bit it came back to that amd package and again got stuck on a loop doing that over and over again for a few minutes, after which it finally continued normally with updating everything.

Restarted my pc, been using it for half on hour or so and so far I’m not noticing any(new) weird behavior, so should I be worried or not?

Thanks.

Cloning into 'mesa'...
done.
Updating files: 100% (10420/10420), done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> Sources are ready.
 -> lib32-mesa-amdonly-gaming-git-24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 already made -- skipping build
==> Making package: lib32-mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 (Vi 13 sep 2024 12:30:01 +0300)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Sources are ready.
==> Making package: mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 (Vi 13 sep 2024 12:30:07 +0300)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating mesa git repo...
remote: Enumerating objects: 219, done.
remote: Counting objects: 100% (194/194), done.
remote: Compressing objects: 100% (46/46), done.
remote: Total 115 (delta 100), reused 80 (delta 69), pack-reused 0 (from 0)
Receiving objects: 100% (115/115), 15.98 KiB | 15.98 MiB/s, done.
Resolving deltas: 100% (100/100), completed with 42 local objects.
From https://gitlab.freedesktop.org/mesa/mesa
 + 90a2c3038c6...cc244712a5b refs/merge-requests/26031/merge -> refs/merge-requests/26031/merge  (forced update)
 + dd8598cce12...03f843a8b79 refs/merge-requests/29552/merge -> refs/merge-requests/29552/merge  (forced update)
 + 6668ae13d70...65b6b9837b1 refs/merge-requests/30967/merge -> refs/merge-requests/30967/merge  (forced update)
 + 56eb20dab73...cbc55cb64c6 refs/merge-requests/31048/merge -> refs/merge-requests/31048/merge  (forced update)
 * [new ref]                 refs/pipelines/1270326          -> refs/pipelines/1270326
 * [new ref]                 refs/pipelines/1270430          -> refs/pipelines/1270430
  -> Found LICENSE
==> Validating source files with b2sums...
    mesa ... Skipped
    LICENSE ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of mesa git repo...
Cloning into 'mesa'...
done.
Updating files: 100% (10420/10420), done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> Sources are ready.
 -> mesa-amdonly-gaming-git-24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 already made -- skipping build
==> Making package: mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 (Vi 13 sep 2024 12:30:27 +0300)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Sources are ready.
==> Making package: lib32-mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 (Vi 13 sep 2024 12:30:33 +0300)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating mesa git repo...
  -> Found LICENSE
==> Validating source files with b2sums...
    mesa ... Skipped
    LICENSE ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of mesa git repo...
Cloning into 'mesa'...
done.
Updating files: 100% (10420/10420), done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> Sources are ready.
 -> lib32-mesa-amdonly-gaming-git-24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 already made -- skipping build
==> Making package: lib32-mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 (Vi 13 sep 2024 12:30:49 +0300)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Sources are ready.
==> Making package: mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 (Vi 13 sep 2024 12:30:55 +0300)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating mesa git repo...
  -> Found LICENSE
==> Validating source files with b2sums...
    mesa ... Skipped
    LICENSE ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of mesa git repo...
Cloning into 'mesa'...
done.
Updating files: 100% (10420/10420), done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> Sources are ready.
 -> mesa-amdonly-gaming-git-24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 already made -- skipping build
==> Making package: mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 (Vi 13 sep 2024 12:31:15 +0300)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Sources are ready.
2

That doesn’t look like a loop. It looks like you have installed multiple mesa related packages from AUR.

Since mesa was updated, it was going through and building each one from source which takes time.

If you look at the output, you can see it was building lib32-mesa-amdonly-gaming-git and mesa-amdonly-gaming-git

3

Oh trust me, it was a loop, it’s just that I copied and pasted only a tiny bit of it, and with my newbness maybe I c&p’ed the wrong part. :face_with_diagonal_mouth:
But I did sit there forever watching it skip
lib32-mesa-amdonly-gaming-git 24.3.0_devel.194752.bacf9752f4d.d41d8cd-1 over and over and over and over and over…

4

Can you share the whole thing? If it is too big, use a pastebin site.

5

Not unless by default the terminal saves a log somewhere of the last usage that persists after closing the terminal and restarting the computer…

6

It is pretty hard to say what happened without being able to see it.

If it happens again, save the output before rebooting.

7

Yeap, will surely do if it happens again, thanks anyway. :wink:

1 Like
8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.