I've been using
-a-a zypper patch --with-update
to maintain my system for a couple of years now.-a Starting a few weeks
ago I occasionally get error messages such as:
************************ start of paste ********************************
Checking for file
conflicts: ......................................................................[error]
Detected 1 file conflict:
File /sbin/init
-a from install of
-a-a-a-a systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
-a conflicts with file
-a-a-a-a /usr/sbin/init
-a from install of
-a-a-a-a systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
File conflicts happen when two packages attempt to install files with
the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no):
*************************** end of paste ************************
There are obviously two other ways I can go forward from this,
- Yast2 Online Update (I can't remember if I've tried that, but I think
I have)
- the standard kde tool for applying updates, the one normally set up to
run every 24 hours.-a That works without complaint.
Any suggestions as to why this is happening?
It happens on two systems, one of them is the one I updated to 16.0
before "updating" back to 15.6.-a The other one has been on 15.6 since I updated from 15.5 some time ago.
I've tried "zypper patch", no change.
I've tried "zypper update", no change.
Obviously I'm running zypper as root, either via sudo (one system) or
via ssh root@<hostname> (second system).
I do not have any machine currently running 15.6 which does not have
this problem.
I've been using
zypper patch --with-update
to maintain my system for a couple of years now. Starting a few
weeks ago I occasionally get error messages such as:
************************ start of paste
********************************
Checking for file conflicts: ......................................................................[error] Detected 1 file conflict:
File /sbin/init
from install of
systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
conflicts with file
/usr/sbin/init
from install of
systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
File conflicts happen when two packages attempt to install files with
the same name but different contents. If you continue, conflicting
files will be replaced losing the previous content.
Continue? [yes/no] (no):
*************************** end of paste ************************
There are obviously two other ways I can go forward from this,
- Yast2 Online Update (I can't remember if I've tried that, but I
think I have)
- the standard kde tool for applying updates, the one normally set up
to run every 24 hours. That works without complaint.
Any suggestions as to why this is happening?
It happens on two systems, one of them is the one I updated to 16.0
before "updating" back to 15.6. The other one has been on 15.6 since
I updated from 15.5 some time ago.
I've tried "zypper patch", no change.
I've tried "zypper update", no change.
Obviously I'm running zypper as root, either via sudo (one system) or
via ssh root@<hostname> (second system).
I do not have any machine currently running 15.6 which does not have
this problem.
On Wed, 19 Nov 2025 18:04:10 +0100
R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> wrote:
I've been using
zypper patch --with-update
to maintain my system for a couple of years now. Starting a few
weeks ago I occasionally get error messages such as:
************************ start of paste
********************************
Checking for file conflicts:
......................................................................[error]
Detected 1 file conflict:
File /sbin/init
from install of
systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
conflicts with file
/usr/sbin/init
from install of
systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
File conflicts happen when two packages attempt to install files with
the same name but different contents. If you continue, conflicting
files will be replaced losing the previous content.
Continue? [yes/no] (no):
*************************** end of paste ************************
There are obviously two other ways I can go forward from this,
- Yast2 Online Update (I can't remember if I've tried that, but I
think I have)
- the standard kde tool for applying updates, the one normally set up
to run every 24 hours. That works without complaint.
Any suggestions as to why this is happening?
It happens on two systems, one of them is the one I updated to 16.0
before "updating" back to 15.6. The other one has been on 15.6 since
I updated from 15.5 some time ago.
I've tried "zypper patch", no change.
I've tried "zypper update", no change.
Obviously I'm running zypper as root, either via sudo (one system) or
via ssh root@<hostname> (second system).
I do not have any machine currently running 15.6 which does not have
this problem.
AFAIK it appears to be a update bug... <https://forums.opensuse.org/t/update-error-systemd-network/189826>
<https://en.opensuse.org/openSUSE:Submitting_bug_reports> or check
in case a bug is already reported.
On 2025-11-19 18:04, R Daneel Olivaw wrote:
I've been using
-a-a-a zypper patch --with-update
to maintain my system for a couple of years now.-a Starting a few weeks
ago I occasionally get error messages such as:
************************ start of paste ********************************
Checking for file conflicts:
......................................................................[error]
Detected 1 file conflict:
File /sbin/init
-a-a from install of
-a-a-a-a-a systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
-a-a conflicts with file
-a-a-a-a-a /usr/sbin/init
-a-a from install of
-a-a-a-a-a systemd-254.27-150600.4.46.2.x86_64 (update-sle (15.6))
File conflicts happen when two packages attempt to install files with
the same name but different contents. If you continue, conflicting
files will be replaced losing the previous content.
Continue? [yes/no] (no):
*************************** end of paste ************************
There are obviously two other ways I can go forward from this,
- Yast2 Online Update (I can't remember if I've tried that, but I
think I have)
- the standard kde tool for applying updates, the one normally set up
to run every 24 hours.-a That works without complaint.
Any suggestions as to why this is happening?
It happens on two systems, one of them is the one I updated to 16.0
before "updating" back to 15.6.-a The other one has been on 15.6 since
I updated from 15.5 some time ago.
I've tried "zypper patch", no change.
I've tried "zypper update", no change.
Obviously I'm running zypper as root, either via sudo (one system) or
via ssh root@<hostname> (second system).
I do not have any machine currently running 15.6 which does not have
this problem.
The problem should happen no matter the tool you use, as long as you ask
the same thing of them.
What I have never seen is a conflict with files from the same patch as appears you get. Maybe you have some repo defined twice. You could post
the result of "zypper lr --details" trying to avoid line wrap.
Otherwise, ask in the mail list.
Carlos E.R. wrote:
On 2025-11-19 18:04, R Daneel Olivaw wrote:
The problem should happen no matter the tool you use, as long as you
ask the same thing of them.
What I have never seen is a conflict with files from the same patch as
appears you get. Maybe you have some repo defined twice. You could
post the result of "zypper lr --details" trying to avoid line wrap.
Otherwise, ask in the mail list.
This is a tough one - avoiding the line wrap on "zypper lr --details" is extremely difficult, but I have a good guess as to what I'm going to see (YaST2 shows me what Repos I have, but not in a "text" form).
The system where this happened yesterday does have some repos defined
twice, that came from my upgrade to Leap 16.0 followed by an "upgrade"
to 15.6 a few days later.-a There is some 16.0 process which adds repos
if it thinks they are missing and several are in there twice - one
"natural" and one from this process.-a Deleting the extra ones does no
good, the process shows up and enters them again.-a Maybe I should delete the "natural" ones.
On the other hand, this also happens on my main system, and that one
never saw 16.0.-a I applied the same updates yesterday on the main system but without complaints.-a This problem does occur on that system, just
not yesterday.
On 2025-11-20 13:25, R Daneel Olivaw wrote:
Carlos E.R. wrote:
On 2025-11-19 18:04, R Daneel Olivaw wrote:
The problem should happen no matter the tool you use, as long as you
ask the same thing of them.
What I have never seen is a conflict with files from the same patch
as appears you get. Maybe you have some repo defined twice. You could
post the result of "zypper lr --details" trying to avoid line wrap.
Otherwise, ask in the mail list.
This is a tough one - avoiding the line wrap on "zypper lr --details"
is extremely difficult, but I have a good guess as to what I'm going
to see (YaST2 shows me what Repos I have, but not in a "text" form).
Your post had no line wrap :-)
I use an addon on Thunderbird that can disable or enable line wrap on
the current post being edited.
The system where this happened yesterday does have some repos defined
twice, that came from my upgrade to Leap 16.0 followed by an "upgrade"
to 15.6 a few days later.-a There is some 16.0 process which adds repos
if it thinks they are missing and several are in there twice - one
"natural" and one from this process.-a Deleting the extra ones does no
good, the process shows up and enters them again.-a Maybe I should
delete the "natural" ones.
Ah, you have to find and remove that process. The description rings a
bell, but I don't remember what it is.
On the other hand, this also happens on my main system, and that one
never saw 16.0.-a I applied the same updates yesterday on the main
system but without complaints.-a This problem does occur on that
system, just not yesterday.
I can try updating my laptop, see if there is something. This desktop
was updated four days ago, no issues. But I use YaST.
The system where this happened yesterday does have some repos defined
twice, that came from my upgrade to Leap 16.0 followed by an "upgrade"
to 15.6 a few days later.-a There is some 16.0 process which adds repos
if it thinks they are missing and several are in there twice - one
"natural" and one from this process.-a Deleting the extra ones does no
good, the process shows up and enters them again.-a Maybe I should
delete the "natural" ones.
Ah, you have to find and remove that process. The description rings a
bell, but I don't remember what it is.
On 2025-11-20 13:54, Carlos E.R. wrote:
The system where this happened yesterday does have some repos defined
twice, that came from my upgrade to Leap 16.0 followed by an
"upgrade" to 15.6 a few days later.-a There is some 16.0 process which
adds repos if it thinks they are missing and several are in there
twice - one "natural" and one from this process.-a Deleting the extra
ones does no good, the process shows up and enters them again.-a Maybe
I should delete the "natural" ones.
Ah, you have to find and remove that process. The description rings a
bell, but I don't remember what it is.
I have to stress this, as that process might be restoring 16.0 repos.
Find that process and remove it.
On 2025-11-20 13:25, R Daneel Olivaw wrote:
Carlos E.R. wrote:
On 2025-11-19 18:04, R Daneel Olivaw wrote:
On the other hand, this also happens on my main system, and that one
never saw 16.0.-a I applied the same updates yesterday on the main
system but without complaints.-a This problem does occur on that
system, just not yesterday.
File /sbin/insmod
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
conflicts with file
/usr/sbin/insmod
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
File /sbin/modinfo
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
conflicts with file
/usr/sbin/modinfo
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
File /sbin/modprobe
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
conflicts with file
/usr/sbin/modprobe
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
File /sbin/rmmod
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
conflicts with file
/usr/sbin/rmmod
from install of
kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
The following 22 packages are going to be upgraded:
cups cups-client cups-config glib2-lang glib2-tools kmod kmod-bash-completion libcups2 libcupscgi1
libcupsimage2 libcupsmime1 libcupsppdc1 libgio-2_0-0 libglib-2_0-0 libgmodule-2_0-0 libgobject-2_0-0
libgpgme11 libgpgmepp6 libgthread-2_0-0 libkmod2 libqgpgme15 libqgpgmeqt6-15
The following 4 NEW patches are going to be installed:
openSUSE-SLE-15.6-2025-4290 openSUSE-SLE-15.6-2025-4293 openSUSE-SLE-15.6-2025-4303
openSUSE-SLE-15.6-2025-4308
Carlos E.R. wrote:
On 2025-11-20 13:25, R Daneel Olivaw wrote:
Carlos E.R. wrote:
On 2025-11-19 18:04, R Daneel Olivaw wrote:
On the other hand, this also happens on my main system, and that one
never saw 16.0.-a I applied the same updates yesterday on the main
system but without complaints.-a This problem does occur on that
system, just not yesterday.
Ok, a week later and it's happening again, big time, 4 "products".
File /sbin/insmod
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
-a conflicts with file
-a-a-a-a /usr/sbin/insmod
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
File /sbin/modinfo
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
-a conflicts with file
-a-a-a-a /usr/sbin/modinfo
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
File /sbin/modprobe
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
-a conflicts with file
-a-a-a-a /usr/sbin/modprobe
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
File /sbin/rmmod
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
-a conflicts with file
-a-a-a-a /usr/sbin/rmmod
-a from install of
-a-a-a-a kmod-29-150600.13.3.1.x86_64 (update-sle (15.6))
This is still on my test machine.-a Ignoring mozilla-test and packman,
all of the repos I have enabled are the ones inserted by that strange process.-a The URLs are identical to the now-disabled originals, except these ones all have "?mediahandler=curl2" tacked on the end.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 20:59:07 |
| Calls: | 742 |
| Files: | 1,218 |
| D/L today: |
6 files (8,794K bytes) |
| Messages: | 185,811 |
| Posted today: | 1 |