Jump to content
Funtoo Newsletter -- March 2023 -- Metatools and CDN ×
  • 0

Windowmaker removed from Funtoo?


heebs

Question

Hi,

I have been a user for quite a while but my server was down for a while, so when I got it back online and started updates, it doesn't find Windowmaker anymore.  I am on 1.4, but just played with the next  on the live install and see the same. I see it upstream in the Gentoo packages. Is there a reason for it being omitted or am I doing something not quite right?  I prefer not to find a different distro as this has been a great ride after coming here from Gentoo to easily keep systemd out of my machine.

 

That being said, maybe there is a way to slurp it in without breaking stuff on my side that I have not explored yet? Since I thought that maybe  my older system without updates may have caused some of the issue, since I can't even remember how long I have been over to Funtoo.... I also bet I dragged in some old Gentoo stuff/behaviors/configurations.

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

Windowmaker will build on 1.4-release by temporarily switching the desktop-kit to 1.3-release branch.

This method only works if 1.3-release branch still exists on desktop-kit from an in-place 1.3 to 1.4 release upgrade. 

# cd /var/git/meta-repo/kits/desktop-kit/
# git checkout 1.3-release

Follow directions in output for dubious owner error:

funtoo /var/git/meta-repo/kits/desktop-kit # git checkout 1.3-release
fatal: detected dubious ownership in repository at '/var/git/meta-repo/kits/desktop-kit'
To add an exception for this directory, call:

	git config --global --add safe.directory /var/git/meta-repo/kits/desktop-kit
funtoo /var/git/meta-repo/kits/desktop-kit # git config --global --add safe.directory /var/git/meta-repo/kits/desktop-kit
funtoo /var/git/meta-repo/kits/desktop-kit # git checkout 1.3-release
Switched to branch '1.3-release'

Verify Windowmaker is available and emerge:

funtoo /var/git/meta-repo/kits/desktop-kit # ego query v windowmaker
 x11-wm/windowmaker| slot|                    repo
-------------------+-----+------------------------
             0.95.7|    0| desktop-kit/1.4-release
          0.95.8-r1|     | desktop-kit/1.4-release
               9999|     | desktop-kit/1.4-release

funtoo /var/git/meta-repo/kits/desktop-kit # emerge -av windowmaker
Calculating dependencies... done!
[ebuild  N     ] x11-wm/windowmaker-0.95.8-r1::desktop-kit  USE="gif jpeg nls png tiff webp xinerama xpm -imagemagick -modelock -xrandr" 3,410 KiB

Total: 1 package (1 new), Size of downloads: 3,410 KiB

Would you like to merge these packages? [Yes/No] 

After emerge completes:

funtoo /var/git/meta-repo/kits/desktop-kit # git checkout 1.4-release 
Switched to branch '1.4-release'

If modified or un-tracked files prevent the checkout to 1.4-release the easiest solution is to delete desktop-kit.

Running ego sync will download a clean replacement that only includes the 1.4-release branch.

Attempting to emerge windowmaker on Next release would begin with importing x11-wm/windowmaker from 1.3-release desktop-kit into a local overlay

Edited by cardinal
Possible issues with 'git checkout 1.4-release'
Link to comment
Share on other sites

  • 0
Cardinal,
Thank you very much for the detailed response. I will post how things ended up working for others, as I have had it installed for quite a while and was causing updating issues.
I may have to go the new install route and go for the local overlay.
Link to comment
Share on other sites

  • 0

So, I finally got some other project downtime and spent time looking into this fun. I was testing an install on the side and started getting  emerge errors when I added the local overlay of the desktop-kit-1.3. I assumed it was an issue with trying to have 2 desktop-kit repos in the mix. I then painfully gutted cruft from my running instance and fixed bum USE flags to get my server up and fully updated on the next branch, but for windowmaker itself. 

I then went back at it to work on the local overlay as you suggested and ended up stripping it down to the bare minimum.  I am still getting errors with emerge when I have the repo file in /etc/portage/repos.conf.  I figured I may as well just grab the latest ebuild from gentoo since I'm already doing something out of the ordinary and it seemed a harmless change.

Here is the error I get when I run emerge:

 emerge --verbose-conflicts -aDNv --with-bdeps=y --backtrack=200 windowmaker
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.7/emerge", line 51, in <module>
    retval = emerge_main()
  File "/usr/lib/python3.7/site-packages/_emerge/main.py", line 1293, in emerge_main
    action=myaction, args=myfiles, opts=myopts)
  File "/usr/lib/python3.7/site-packages/portage/proxy/objectproxy.py", line 30, in __call__
    return result(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/_emerge/actions.py", line 2507, in load_emerge_config
    **kwargs)
  File "/usr/lib/python3.7/site-packages/portage/__init__.py", line 555, in create_trees
    env=env, sysroot=sysroot, eprefix=eprefix)
  File "/usr/lib/python3.7/site-packages/portage/package/ebuild/config.py", line 547, in __init__
    self.repositories = load_repository_config(self)
  File "/usr/lib/python3.7/site-packages/portage/repository/config.py", line 1110, in load_repository_config
    return RepoConfigLoader(repoconfigpaths, settings)
  File "/usr/lib/python3.7/site-packages/portage/repository/config.py", line 788, in __init__
    if repo_name not in repo.aliases:
TypeError: argument of type 'NoneType' is not iterable

 

Here is the output of ego query:

ego query v windowmaker 
 x11-wm/windowmaker| slot|              repo
-------------------+-----+------------------
        - 0.95.8-r1|    0|  desktop-kit/next
          0.95.9-r4|     | windowmaker-local

Here is the  repo file:

cat /etc/portage/repos.conf/windowmaker
[windowmaker-local]
location = /home/overlays/windowmaker-local
auto-sync = no
priority = 10

 

Here are the contents of the overly directory:

 ls -l windowmaker-local/*  windowmaker-local/x11-wm/*
windowmaker-local/metadata:
total 4
-rw-r--r-- 1 portage portage 146 May  9 07:47 layout.conf

windowmaker-local/profiles:
total 4
-rw-r--r-- 1 portage portage 11 May  9 07:47 repo_name

windowmaker-local/x11-wm:
total 0
drwxr-xr-x 2 portage portage 96 May  9 07:42 windowmaker

windowmaker-local/x11-wm/windowmaker:
total 4
-rw-r--r-- 1 portage portage 3218 May  9 07:42 windowmaker-0.95.9-r4.ebuild

 

Here are the files for the overlay:

root@jonesin|/home/overlays/windowmaker-local> cat profiles/repo_name
windomaker-local
root@jonesin|/home/overlays/windowmaker-local> cat metadata/layout.conf
repo-name = windomaker-local
thin-manifests = true
sign-manifests = false
profile-formats = portage-2
cache-formats = md5-dict
masters = core-kit

 

 

Did I miss something along the way or have I found an odd bug?
 

Link to comment
Share on other sites

  • 0

 

The name [windowmaker-local] in this file:

/etc/portage/repos.conf/windowmaker

is different than the name windomaker-local in the profiles/repo_name and metadata/layout.conf in /home/overlays/windowmaker-local

The reference name must be identical in all configuration files for the specific overlay.

Edited by cardinal
Remove bold from square brackets.
Link to comment
Share on other sites

  • 0

Let me say that I must have stared at that over and over and my dumb ass brain filled in the missing w in the lines. I feel extra stupid this day, and that is saying something......

 

 

I super appreciate all your patience and help with this.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...