Uploaded image for project: 'Funtoo Linux'
  1. Funtoo Linux
  2. FL-10288

next: w3m autogen failing

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical (Application) Critical (Application)
    • None
    • None
    • None
    • Blocks multiple applications that depend on www-client/w3m.
    • Missing www-client/w3m ebuild.
    • Hide
      Example of blocked app:

      $ emerge -av neofetch

      These are the packages that would be merged, in order:

      Calculating dependencies... done!

      emerge: there are no ebuilds to satisfy "www-client/w3m[imlib]".
      (dependency required by "app-misc/neofetch-7.1.0::dev-kit[X]" [ebuild])
      (dependency required by "neofetch" [argument])
      Show
      Example of blocked app: $ emerge -av neofetch These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds to satisfy "www-client/w3m[imlib]". (dependency required by "app-misc/neofetch-7.1.0::dev-kit[X]" [ebuild]) (dependency required by "neofetch" [argument])

      It looks like the original Gentoo snapshot had 3 w3m related ebuilds:

      www-client/w3m
      www-client/w3mmee
      virtual/w3m

      Funtoo next at this moment has 2 of those:

      www-client/w3mmee
      virtual/w3m

      I assume there has been some reason to 'beard trim' out www-client/w3m, but if that was the intention, then we don't need virtual/w3m anymore and the ebuilds that depended both on www-client/w3m and virutal/w3m need to be edited to now depend on www-client/w3mmee.

      One example of such ebuild is app-misc/neofetch.

      It looks like, in the end, the best way to solve this is to just keep the original 3 ebuilds, in which case this bug would be resolved by just adding back www-client/w3m .

            drobbins drobbins
            adbosco adbosco
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: