LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-29-2019, 11:44 PM   #1
ScrambledLogic
LQ Newbie
 
Registered: Aug 2015
Distribution: Slackware
Posts: 13

Rep: Reputation: 0
Question Problems with slackrepo after recent -current updates


Having a weird issue with slackrepo after recent updates to slackware64-current and a kernel upgrade. When I run
Code:
sudo slackrepo update
or
Code:
sudo slackrepo build PACKAGE
I get the following:
Code:
mount: /tmp/slackrepo.XXXXXX/chrootdir: mount(2) system call failed: Too many levels of symbolic links.
ERROR: Failed to mount /tmp/slackrepo.XXXXXX/chrootdir/
where "XXXXXX" are random characters that as I understand it are normal in this sort of operation. This seems to happen regardless of package or operation.

I'm experiencing the same problem on two different systems, a desktop and a laptop. The laptop I upgraded from kernel 4.19.13 to 4.19.61, the desktop from 4.19.19 to 4.19.61. I build my own kernel, always using the current slackware64-current kernel config and making only one change: enabling automatic process group scheduling. I would have tried booting to the old kernel version to see if that solved the issue, however, another problem has appeared; now, regardless of the kernel version I choose in grub, I always boot to 4.19.61. I haven't changed anything about the slackware update process I've used since late last year. Slackrepo has not been upgraded or the config changed since late last year.

Each PC has its own repo for slackrepo, I don't use a vm for slackrepo (I realize this might be considered bad practice by slackrepo's author, but I haven't had any problems like this in all the time I've had this setup), I do have it set to use chroot. I've checked to make sure that /tmp didn't somehow become symlinked, as well as the path to the slackrepos on both PC's. No symlinks in sight there.

I'm trying to figure out if this is due to my bad habits using slackrepo, some change in the kernel or something gone awry during the kernel upgrade, a config file I may have overwritten (during slackware upgrade I always use the prompt option and check each config file change, could have easily missed something though), a package upgrade, or something simple I overlooked or did that would have affected both systems at the same time. Some research online seems to suggest that this problem can be caused by circular symlinks, but I haven't found anything that would suggest that this is the root cause.

Note: I do have ~/.config symlinked to a syncthing Sync folder for backup, but as far as I can tell everything in there is user-specific and has nothing to do with slackrepo.

Other possibly relevant info:
I use the i3-gaps window manager, launched using .xinitrc when I log in with tty, no login manager.
I use multilib, installed and managed with slackpackage+.
Most other packages are installed using slapt-get pointed to slackrepo's repo (I do not install using slackrepo itself, it's only used for building packages.)
Slackrepo points to ponce's repo on both systems, with a few of my own custom hint files.
I have a few other minor things as non-root AppImages or non-root builds/scripts thrown into a ~/bin directory that is in my $PATH

ETA: Correction, I'm using a ~/bin directory, not ~/builds, in my $PATH for custom scripts/binaries. Also corrected time period, haven't been back on Slack for quite a year yet.

Last edited by ScrambledLogic; 07-30-2019 at 12:31 AM. Reason: Correction
 
Old 08-04-2019, 10:07 AM   #2
hadack
LQ Newbie
 
Registered: Jun 2006
Posts: 22

Rep: Reputation: 4
Hi, I have the same issue and I am running slackrepo in a vm. I did not really investigate the issue, but disabling chroot in the config file works around it.

Greetings, hadack
 
1 members found this post helpful.
Old 09-11-2019, 03:35 PM   #3
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 932

Rep: Reputation: Disabled
I just fired up current again and seeing this as well.

Thanks for the tip @hadack.
 
  


Reply

Tags
chroot, current, mount, slackrepo, symlinks


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Backspace produces ^H after running slackrepo slalik Slackware 28 05-28-2017 04:22 AM
(SOLVED) Unable to send mail with Mutt after recent Slackware Current updates frankbell Slackware 4 08-28-2015 12:19 AM
Recent - current libelf updates wildwizard Slackware 3 05-17-2014 01:54 PM
Sound issues in -current since recent updates rpedrica Slackware 1 08-02-2012 01:10 AM
puppy thoughts after having a recent look see -- given recent developments .. jonyo Puppy 0 11-29-2011 08:45 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:43 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration