You are not logged in.

#1 2022-10-03 06:14:53

860lacov
Member
Registered: 2020-05-02
Posts: 342

[SOLVED] How to remove testing repositories?

I wanted to test new KDE Plasma so I tried with kde unstable + arch testing repos.

I wanted to rollback as in:
Disabling testing repositories

But when I do pacman -Syuu I get:

error: failed to commit transaction (conflicting files)
pipewire: /etc/alsa/conf.d/50-pipewire.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-cat exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-dsdplay exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-loopback exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-mididump exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-midiplay exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-midirecord exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-play exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/pw-record exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/spa-acp-tool exists in filesystem (owned by pipewire-audio)
pipewire: /usr/bin/spa-resample exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/alsa-lib/libasound_module_ctl_pipewire.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/alsa-lib/libasound_module_pcm_pipewire.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-echo-cancel.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-fallback-sink.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-filter-chain.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-loopback.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-pipe-tunnel.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-protocol-simple.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/aec/libspa-aec-null.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/aec/libspa-aec-webrtc.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/alsa/libspa-alsa.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/audioconvert/libspa-audioconvert.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/audiomixer/libspa-audiomixer.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/audiotestsrc/libspa-audiotestsrc.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/bluez5/libspa-bluez5.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/bluez5/libspa-codec-bluez5-aac.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/bluez5/libspa-codec-bluez5-aptx.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/bluez5/libspa-codec-bluez5-faststream.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/bluez5/libspa-codec-bluez5-ldac.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/bluez5/libspa-codec-bluez5-opus.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/bluez5/libspa-codec-bluez5-sbc.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/spa-0.2/volume/libspa-volume.so exists in filesystem (owned by pipewire-audio)
pipewire: /usr/lib/systemd/user/filter-chain.service exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/alsa/alsa.conf.d/50-pipewire.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/alsa/alsa.conf.d/99-pipewire-default.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/man/man1/pw-cat.1.gz exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/man/man1/pw-mididump.1.gz exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/demonic.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/sink-dolby-surround.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/sink-eq6.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/sink-make-LFE.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/sink-matrix-spatialiser.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/sink-mix-FL-FR.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/sink-virtual-surround-5.1-kemar.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/sink-virtual-surround-7.1-hesuvi.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/source-duplicate-FL.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/pipewire/filter-chain/source-rnnoise.conf exists in filesystem (owned by pipewire-audio)
pipewire: /usr/share/spa-0.2/bluez5/bluez-hardware.conf exists in filesystem (owned by pipewire-audio)
ruby: /usr/lib/ruby/3.0.0/racc.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/compat.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/debugflags.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/exception.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/grammar.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/grammarfileparser.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/info.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/iset.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/logfilegenerator.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/parser-text.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/parser.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/parserfilegenerator.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/sourcetext.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/state.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/statetransitiontable.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/racc/static.rb exists in filesystem (owned by ruby-racc)
ruby: /usr/lib/ruby/3.0.0/x86_64-linux/racc/cparse.so exists in filesystem (owned by ruby-racc)
Errors occurred, no packages were upgraded.

Last edited by 860lacov (2022-10-03 21:06:40)

Offline

#2 2022-10-03 06:36:36

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,232
Website

Re: [SOLVED] How to remove testing repositories?

Looks like some packages have been split in testing.  You can probably do...

pacman -R pipewire-audio ruby-racc
pacman -Syuu

If the -R does not work due to dependency issues, you can add a "-dd" to ignore these.

Offline

#3 2022-10-03 14:56:43

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 10,946
Website

Re: [SOLVED] How to remove testing repositories?

Mod note: Moving to Testing.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#4 2022-10-03 20:42:24

860lacov
Member
Registered: 2020-05-02
Posts: 342

Re: [SOLVED] How to remove testing repositories?

Allan wrote:

Looks like some packages have been split in testing.  You can probably do...

pacman -R pipewire-audio ruby-racc
pacman -Syuu

If the -R does not work due to dependency issues, you can add a "-dd" to ignore these.


After metasploit removal, I was able to easily remove ruby (it was removed with metasploit).
But pipewire-audio is requied by pipewire-pulse, pipewire-pulse is required by plasma applet and some other packages. And those packages require another packages.

Thank you, but I'll probably wait on testing. It is working. It's stable. I'm not sure how -dd will end, so I don't want to risk.
But still. Thank you.

Offline

#5 2022-10-03 20:56:38

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 27,576
Website

Re: [SOLVED] How to remove testing repositories?

There really isn't any risk if used as specified (i.e., given you complete the downgrade right after).  You could ease your own mind by double-checking right after that with the following

pacman -Qqn | pacman -S -

This will "reinstall" all packages and if there are any missing dependencies (there wouldn't / shouldn't be) they'd be pulled back in.  But again, if you only use -Rdd specific to [testing] this would be unneeded.

Last edited by Trilby (2022-10-03 20:57:26)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#6 2022-10-03 21:06:19

860lacov
Member
Registered: 2020-05-02
Posts: 342

Re: [SOLVED] How to remove testing repositories?

Trilby wrote:

There really isn't any risk if used as specified (i.e., given you complete the downgrade right after).  You could ease your own mind by double-checking right after that with the following

pacman -Qqn | pacman -S -

This will "reinstall" all packages and if there are any missing dependencies (there wouldn't / shouldn't be) they'd be pulled back in.  But again, if you only use -Rdd specific to [testing] this would be unneeded.

I'll try next time.

I did pacman -Rsn pipewire-audio pipewire-pulse plasma-pa
And after that I was able to do pacman -Syuu

I had to install pipewire, but it seems that it works.

Offline

Board footer

Powered by FluxBB