From: Danni@hyperspace.vogon.gov.invalid   
      
   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.  I applied the same updates yesterday on the main   
   >> system but without complaints.  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   
   >   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))   
      
   This is still on my test machine.  Ignoring mozilla-test and packman,   
   all of the repos I have enabled are the ones inserted by that strange   
   process.  The URLs are identical to the now-disabled originals, except   
   these ones all have "?mediahandler=curl2" tacked on the end.   
      
   The complete list of updates + patches which were to be installed is:   
   > The following 22 packages are going to be upgraded:   
   >   cups cups-client cups-config glib2-lang glib2-tools kmod kmo   
   -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 open   
   USE-SLE-15.6-2025-4303   
   >   openSUSE-SLE-15.6-2025-4308   
      
   I have just updated the same packages (+ openSUSE-SLE-15.6-2025-4297) on   
   this "main" machine, using the same command and without complaint.  I'm   
   wondering when this machine is going to throw up the same error.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)