Potential conflict with icu package?

WinFan3672 <winfan3672@xxxxxxxxx> · Sun, 17 Dec 2023 15:46:21 +0000



    Dear all, 

    
    I was recently performing my system's scheduled maintenance and
      went to upgrade my packages, as you do. When I attempted to do so,
      this happened:
    
      $ sudo pacman -Syu

          [sudo] password for winfan3672:

          :: Synchronizing package databases...

          ...

          :: Starting full system upgrade...

          resolving dependencies...

          looking for conflicting packages...

          error: failed to prepare transaction (could not satisfy
          dependencies)

          :: unable to satisfy dependency 'libicuuc.so =73-64' required
          by freerdp

          :: installing icu (74.2-1) breaks dependency
          'libicuuc.so=73-64' required by brltty

          :: installing icu (74.2-1) breaks dependency
          'libicuuc.so=73-64' required by gspell

          :: installing icu (74.2-1) breaks dependency
          'libicuuc.so=73-64' required by harfbuzz-icu

          :: installing icu (74.2-1) breaks dependency
          'libicuuc.so=73-64' required by libphonenumber

          :: installing icu (74.2-1) breaks dependency
          'libicui18n.so=73-64' required by libphonenumber

          :: installing icu (74.2-1) breaks dependency
          'libicuuc.so=73-64' required by raptor

          :: installing icu (74.2-1) breaks dependency
          'libicuuc.so=73-64' required by scribus

          :: installing icu (74.2-1) breaks dependency
          'libicui18n.so=73-64' required by thunderbird

          :: installing icu (74.2-1) breaks dependency
          'libicuuc.so=73-64' required by thunderbird

      
    This piqued my interest as it appears to be a package conflict
      outside of my control. I performed the upgrade excluding the icu
      package, and (almost) everything is fine now.
    However, I would like to know:
    
      Is this an issue with the icu package?
      
        In this case, this is an issue that needs attention and the
          relevant maintainer should probably look into it. 

        
      Is it an issue with me?
      
        If so, what do I do, aside from ignoring it?
      
    
    I look forward to hearing your response(s).
    Yours truly,

    
    -- 
WinFan3672.