System update strange thing Dynamic user

Hello Manjaro usres, now i update and see these things, i seem to update as a dynamic user and get all these weird text. can someone help me out here. Thanks in advance. Diaan from the Netherlands

[sudo] password for dian: 
Warning: Building packages as dynamic user
Warning: Setting build directory to /var/cache/pamac
Preparing...
Synchronizing package databases...
Refreshing AUR...                                                                                               
Cloning qt4 build files...                                                                                      
Running as unit: run-u47.service
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 241ms
CPU time consumed: 55ms
Running as unit: run-u48.service; invocation ID: b3906b1a99d047c993aaeeccc40bab4b
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 104ms
CPU time consumed: 55ms
Running as unit: run-u49.service; invocation ID: 4322238acd2a4bf1b889bf36f5be5ffc
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 892ms
CPU time consumed: 221ms
Generating qt4 information...
Running as unit: run-u50.service; invocation ID: 35d964e4d93b47d2b2fb641b11fe2167
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 5.296s
CPU time consumed: 5.361s
Checking qt4 dependencies...
Cloning python2 build files...
Running as unit: run-u51.service
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 55ms
CPU time consumed: 49ms
Running as unit: run-u52.service; invocation ID: 3d257c28e1df45b3870a374aa3f2058e
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 111ms
CPU time consumed: 52ms
Running as unit: run-u53.service; invocation ID: 021339e78e234159a2a4755ecdbcd769
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 585ms
CPU time consumed: 200ms
Generating python2 information...
Running as unit: run-u54.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 4.295s
CPU time consumed: 5.043s
Checking python2 dependencies...
Cloning pyside2 build files...
Running as unit: run-u55.service; invocation ID: 39a2a18debda47c592dfe84a1b22f3a8
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 54ms
CPU time consumed: 49ms
Running as unit: run-u56.service; invocation ID: 329d5e8e6e074dc38f0d308fa98ebb70
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 116ms
CPU time consumed: 54ms
Running as unit: run-u57.service
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Finished with result: success

Goes on with this for a while and this is the end of the text in the terminal

Running as unit: run-u171.service; invocation ID: 8110e3514ecc48ddbebece25ead48a4e
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 2.506s
CPU time consumed: 181ms
Generating sidplay2-libs information...
Running as unit: run-u172.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 6.557s
CPU time consumed: 4.911s
Checking sidplay2-libs dependencies...
Cloning rttr build files...
Running as unit: run-u173.service; invocation ID: e5d68736c5964690a9c3ad55f7eae878
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 68ms
CPU time consumed: 56ms
Running as unit: run-u174.service; invocation ID: 1cc71a8d12f9476c842c43372b3b20e0
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 114ms
CPU time consumed: 58ms
Running as unit: run-u175.service; invocation ID: 839095d0cb5e4857b6f6721af7de94a7
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 3.669s
CPU time consumed: 176ms
Generating rttr information...
Running as unit: run-u176.service; invocation ID: dbd774f2225741208f6c3b62ac4c4eb4
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 4.368s
CPU time consumed: 3.324s
Checking rttr dependencies...
Cloning python2-setuptools build files...
Running as unit: run-u181.service; invocation ID: 11cf84a803384a0b993db6ce270abcd9
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 79ms
CPU time consumed: 55ms
Running as unit: run-u182.service; invocation ID: ebdc7076b3244be6bb58fcfe6e4274e2
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 225ms
CPU time consumed: 61ms
Running as unit: run-u183.service; invocation ID: cc435a2dfd9842e3b9a398cfcb81ad30
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 2.062s
CPU time consumed: 190ms
Generating python2-setuptools information...
Running as unit: run-u184.service; invocation ID: f4c3d238fa2a4452b513d87443392b5c
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 4.124s
CPU time consumed: 2.953s
Checking python2-setuptools dependencies...
Warning: sndio: local (20180120-1) is newer than extra (1.9.0-2)
Resolving dependencies...
Checking inter-conflicts...

To build (35):
  ceph-libs             18.2.2-3                (15.2.14-6)             AUR
  libglade              2.6.4-9                 (2.6.4-7)               AUR
  python2               2.7.18-11               (2.7.18-5)              AUR
  python2-cairo         1.19.1-2                (1.18.2-4)              AUR
  python2-gobject2      2.28.7-7                (2.28.7-6.1)            AUR
  furiusisomount        0.11.3.1-2              (0.11.3.1-1)            AUR
  gconf                 3.2.6+11+g07808097-10   (3.2.6+11+g07808097-8)  AUR
  gnome-icon-theme      3.12.0-7                (3.12.0-6)              AUR
  google-chrome         126.0.6478.126-1        (124.0.6367.60-1)       AUR
  krunner5              5.115.0-4               (5.115.0-1)             AUR
  lha                   1:1.14i-1               (1.17-1)                AUR
  libguess              1.2-5                   (1.2-4)                 AUR
  libmagick6            6.9.13.10-1             (6.9.11.52-1)           AUR
  libquicktime          1.2.4-31                (1.2.4-25)              AUR
  libxxf86dga           1.1.6-1                 (1.1.5-1.1)             AUR
  openssl-1.0           1.0.2.u-6               (1.0.2.u-1)             AUR
  qt4                   4.8.7-36                (4.8.7-29.1)            AUR
  phonon-qt4            4.10.3-1                (4.9.1-4)               AUR
  phonon-qt4-gstreamer  4.9.1-1                 (4.9.0-3)               AUR
  python-shiboken2      5.15.13-2               (5.15.12-1)             AUR
  pyside2               5.15.13-2               (5.15.12-1)             AUR
  python-pep517         0.13.1-2                (0.13.0-1)              AUR
  python-progress       1.6-8                   (1.6-5)                 AUR
  python-sip4           4.19.25-7               (4.19.25-3)             AUR
  python2-setuptools    2:44.1.1-2                                      AUR
  python2-pyxdg         0.28-5                  (0.27-1)                AUR
  qt5-webkit            5.212.0alpha4-24        (5.212.0alpha4-18)      AUR
  rttr                  0.9.6-4                 (0.9.6-3)               AUR
  sidplay2-libs         2.1.1-7                 (2.1.1-1)               AUR
  sip4                  4.19.25-7               (4.19.25-3)             AUR
  sni-qt                0.2.7+17.04.20170112-1  (0.2.6-5)               AUR
  taglib-extras         1.0.1-8                 (1.0.1-7.0)             AUR
  transcode             1.1.7-44                (1.1.7-41)              AUR
  xdg-su                1.2.3-2                 (1.2.3-1)               AUR
  zd1211-firmware       1.5-4                   (1.5-1)                 AUR
To remove (1):
  python-sip4           4.19.25-3                                       AUR

Total removed size: 256,2 kB

Edit build files : [e] 
Apply transaction ? [e/y/N] 

What are you trying to build?
Are you sure you still need these softwares?
qt4 is long dead - sidplay2-libs is an orphaned package
It looks like many of these:

are very old or even not available anymore.

2 Likes

dinosaurs are out :dizzy_face:
Cleaning up orphans is a good idea

I guess, you’re running pamac with sudo. Don’t do this.

2 Likes

From the gigantic list above, about 80% are dead unsupported orphans, the rest is in the repos whit the exception of chrome. So it is actually good that you did not build this mess, to make an even bigger mess of the probably already messy system. You should not use AUR if you have no idea how. Now the solution which we can give you will probably be to clean everything AUR and update the core system and then see if you REALLY miss anything from the removed stuff, like chrome. If you are ok with that…
You can safely start with

sudo pacman-mirrors -f
sudo pacman -Syu
sudo pacman -Rsu $(pacman -Qtdq)

now, if you want to remove all AUR, which may remove stuff you use, like chrome

sudo pacman -Rsu $(pacman -Qm)
sudo pacman -Rsu $(pacman -Qtdq)

Thanks TEO and all the others for the advice and the help, i run Manjaro with the luck there are people who will help others, i realy apriciate that.
I will think this over and let you know if it works and how it works.
I will check out chrome on one firmware-loading-thing for an O_C module but i think i can use the windows, chrome version of that.
I like Manjaro a whole lot, that’s why i use it for years now.
Many thanks, Dian from the Netherlands

1 Like

Hello again, so i get a whole new system with out AUR.
And all the things will work, also pure data and the Arduino ide. These two i use alot and it will be fine if they will work afterworths.
And not, maybe i can reinstall them?
Thanks again. I will do this core system update on monday, i have to work the weekend. Dian

Hello, can someone explain to me please what i did to my system that was ‘not good’
How did i mess is up and just doing some updates and install some programs for the last 5 or 7 years.
And what can i do to prevent this.
And what will happen to my system if i execute the commandsTeo suggested. Just qurious.
Thanks in advance, Dian from the Netherlands

You used pamac with sudo.

Okay thanks mithrial.
What do the commands that Teo suggested mean so i know what i am executing

Refreshing mirrors.
Syncing and updating the core system without aur.
Removing orphans.

Those 3 should be safe on any system. And it is a prerequisite to debug more - the bare minimum is to be up to date. After that you can check if your problems is solved, if not you can ask more or start removing aur stuff one by one but only you know what you use.
If you are really, really stuck, you can delete ALL aur at once with

sudo pacman -Rsu $(pacman -Qm)

which of course will produce new orphans.
Note that this might delete something you actually use, like chrome (if you do not use the logging in in google and syncinc bookmarks with another pc or a mobile phone you can use chromium browser from the repos)

Those commands do all have manual pages, you know? :wink:

man pacman
man pacman-mirrors
man pamac

The syntax “$(some-command-here)” is a command substitution. It means that “$(some-command-here)” will be replaced with the output of some-command-here, which will then be the parameters that the invoking command will work on.

Try it yourself… :point_down:

echo "I am logged in as $(whoami)"

:wink:

1 Like

Thanks to you all, you helped me alot.
I will try this tomorow and let you know.
Dian

Hello, i did the things Teo suggested and the first 3 went on good.
The 4the give this, and after that the 5the gave nothing, but when i ran the 3the command the first time it gave a good result, deleting 313 orphans, huray

[dian@dian-pc ~]$ sudo pacman -Rsu $(pacman -Qm)
[sudo] password for dian: 
error: target not found: 2.5.0-5
error: target not found: 12.2.3-4
error: target not found: 1.7.9-1
error: target not found: 0.11.3.1-1
error: target not found: 3.12.0-6
error: target not found: 3.12.0-6
error: target not found: 124.0.6367.60-1
error: target not found: 5.9.0-1
error: target not found: 1.3-10
error: target not found: 3.1-8
error: target not found: 0.5.1-1
error: target not found: 5.27.11-1
error: target not found: 1.17-1
error: target not found: 0.9.3+16.04.20160218-1
error: target not found: 2.6.4-7
error: target not found: 4.14.280-1
error: target not found: 8.049.02-45
error: target not found: 20181009-1
error: target not found: 20160419-1
error: target not found: 2024.1-2
error: target not found: 1:2.1.2-1
error: target not found: 1.0-7
error: target not found: 018-7
error: target not found: 4.9.1-4
error: target not found: 4.9.0-3
error: target not found: 5.5-2
error: target not found: 5.5-2
error: target not found: 2.24.0-14
error: target not found: 5.15.12-1
error: target not found: 3.5.7-7
error: target not found: 5.15.12-1
error: target not found: 2.7.18-5
error: target not found: 1.18.2-4
error: target not found: 2.28.7-6.1
error: target not found: 4.8.7-29.1
error: target not found: 0.2.6-5
error: target not found: 1.1.7-41
error: target not found: 1.2.3-1
error: target not found: 1.9.0-3
error: target not found: 1.9.3-1
error: target not found: 1.5-1
[dian@dian-pc ~]$ sudo pacman -Rsu $(pacman -Qtdq)
error: no targets specified (use -h for help)

System seems good now, and shall i update with pamac update or with
sudo pacman -Syu the next time
Thanks, Dian

Hello, shall i update with pamac update or with sudo pacman -Syu the next time.
A while ago someone on this forum suggested me to update with pamac and that introduced the AUR things as i remember so it seems beter to me to use the sudo pacman -Syu command for updating.
Thanks for all the comments,
Dian from the Netherlands

start with pacman-mirrors -c Germany
(or another variant of this command - refresh your list of mirrors first is the point of this exercise)
then continue with pacman -Syyu
(the double “y” because you most likely just changed the mirror that you are now using to fetch your packages from)
then you may use pamac with the AUR enabled to take care of any AUR packages you may have

You can do it with pamac only - but in the first round with AUR disabled …
I’d always prefer pacman, though.

Please do not use sudo with pamac. It usually wrecks the permissions on /var/tmp/pamac tree.

With reference to your topic title and the dynamic user.

When building custom packages on an Arch Linux based system - building as root is not allowed.

The main reason is that a custom PKGBUILD is partially a shell script which - if improperly created - may wreck your system completely .

For some reason the pamac developer thought - hey! I can work around that - I create temporary user - switch context - build the package - switch back - and remove the user.

That is what the pamac is doing

  • because you launched pamac as root (usring sudo)
  • pamac need to an unprivileged environment
  • to build a custom package, using an unverified source
  • so pamac creates a temporary user
  • switch context
  • build the package as the user
  • switch back
  • removes the temorary user

So that is what a dynamic user does …

Whether this is good or bad - please leave me out of that discussion - fact is, that is what the dynamic user do.

1 Like

Thanks for all the ideas.
Dian

Hello, i think i will delete all the AUR stuff and then remove the orphans and then do updates with sudo pacman -Syu.
Thanks again to you all.
Dian from the Netherlands