[SOLVED] circular blockages

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Dear Folks,

I have what looks to be a couple of circular blocked packages:

djt /etc/portage # emerge --backtrack=50 --ask --newuse @preserved-rebuild

Josef.95 · Advocate Joined: 03 Sep 2007 Posts: 4554 Location: Germany

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Many thanks for the help again here.

I have made the following changes based on a search of every instance of systemd I could find in the package.use file:

Hu · Moderator Joined: 06 Mar 2007 Posts: 21633

You are using a directory for package.use. Every file in that directory is considered part of your per-package USE changes. What is the output of grep -rn systemd /etc/portage/package.use? My guess is you will find a file that is lexicographically later than package.use that enables this flag on dbus.

In my opinion, if you do not want systemd installed, you should locally mask it so that Portage is forced to pick the non-systemd solution to every question, or fail out when no such solution is available. (Likewise, if you are a systemd user, mask the non-systemd solutions.)

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Many thanks for your advice here.

I ran the command you suggested:

Mr. T. · Guru Joined: 26 Dec 2016 Posts: 477

Mr. T. · Guru Joined: 26 Dec 2016 Posts: 477

mikefot, you should use euse (gentoolkit).

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Many thanks for the advice.

Here is the output of the euse command:

asturm · Developer Joined: 05 Apr 2007 Posts: 8936

*headache* There is no need to pollute your package.use file like this. systemd flag should be switched on or off in ONE place only, and that is make.conf (if not already by profile).

Mr. T. · Guru Joined: 26 Dec 2016 Posts: 477

mikefot, the system must be updated after a profile change.

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Thanks again for the comments and suggestions.

I tried to run the world update but it the blockage is preventing this.

So perhaps the systemd purge it would create itself has not occurred completely so we are relying on other fixes at present.

Maybe the package mask idea is the best one at present.

If it worked then I could delete the lines in the package.use file dealing with systemd or whatever other suggestion you might have to remove them.

Cheers

MF

Hu · Moderator Joined: 06 Mar 2007 Posts: 21633

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Many thanks again here.

So the problem was caused by me using emacs to look at the package.use file and the editor creating a backup file which it is wont to do from time to time....

That was very perceptive.

I checked the directory and it is correct. There is a tilda copy of the package.use file.

I have deleted it and ran the emerge command again but it the blockage is still there.

Naib · Posted: Sun Jan 28, 2018 7:19 pm Post subject:

Mr. T. · Guru Joined: 26 Dec 2016 Posts: 477

@Hu: I'm sorry, I was misleaded by the mitigating circumstances! :mrgreen:

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Dear All,

I am now trying a world update after the dbus fix.

Sadly a new set of blockages has appeared.

I ran emerge with the -v option which I think is verbose.

The output is here:

https://pastebin.com/nphp4EU5

The blocks do include a clash between sysvinit and systemd:

asturm · Developer Joined: 05 Apr 2007 Posts: 8936

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Many thanks for the comments and suggestions.

Do I have to use the emerge deselect command to remove the kde-apps/kde4-l10n package from the world file or do I use another method?

Thanks

Regds

MF

PS I have posted the emerge -v --info here:

https://pastebin.com/vpLJBQDJ

Naib · Posted: Sun Jan 28, 2018 8:22 pm Post subject:

ok step back... lots going on & when this happens with me I revert to the lowest common emerge command.

My standard emerge command is: emerge -auNDv @world --complete-graph --with-bdeps=y --keep-going --verbose-conflicts --backtrack=30

if this fails and it isn't obvious why I simplify

1) emerge -auNDv @world --complete-graph --with-bdeps=y --keep-going --verbose-conflicts --backtrack=30
becomes
2) emerge -auNv @world
becomes
3) emerge -auv @world
THEN
4) emerge -auNDv @system
becomes
5) emerge -auNv @system
becomes
6) emerge -auv @system

once you get to a step that will resolve and build its working to the previous to whittle down the total number of packages. I had to follow this process this weekend as my home NAS hasn't been updated in like 6months... now emerge -auNDv @world --complete-graph --with-bdeps=y --keep-going --verbose-conflicts --backtrack=30 is running perfectly fine once I was able to build what was resolvable and then deal with perl...

So ... follow a similar methodology, determine the smallest set portage command that will resolve & build. Post which one & equally let it build. The try again to reduce the actual number of packages listed.

The fact systemd is there means @system could also be an issue
_________________

mikefot · l33t Joined: 19 Nov 2014 Posts: 709

Dear All,

The blockage is a pain at present. I will continue massaging it with the various suggestions
that have been provided.

I am posting the latest make.conf here:

https://pastebin.com/1vcVX4g1

Cheers

MF

PS I have looked at the package mask page. I have a package mask file ready to use.

The sample command on the page is: