pacman error: mtree specification has different type

trusktr · 2015-03-13 05:59:57

I'm running pacman -Syu on a system last upgraded on Nov 9th, 2013 (I know, I know). It's resulting in some mtree errors as seen in the next screenshot, and there's not much info I can find after searching.

http://50.116.4.56/~/img/pacman-mtree-errors.png

What might the errors mean and how might one proceed?

Last edited by trusktr (2015-03-25 07:11:37)

Trilby · 2015-03-13 10:16:05

Post the actual output: https://wiki.archlinux.org/index.php/Fo … s_and_code

Also include the full command and output, not just the tail end.

Further, explain why your package cache is in /home/ - this is most likely the cause of the problem, but it is hard to tell as you haven't given us any details of your non-standard setup.

trusktr · 2015-03-25 05:25:36

@Trilby Thanks so much for your reply.

I'm not sure how to get the output in a linux terminal (the native linux terminal). Is it stored in the filesystem somewhere?

I can't solve this issue yet because I've gotten blocked by another problem: https://bbs.archlinux.org/viewtopic.php?pid=1514016

My package cache is in /home/pacman and /etc/pacman.conf reflects this settings. I haven't had a problem with it in the past. I'll try moving it back to /var/cache once I get past the live media always crashing.

Regarding trying to get terminal output, I was trying to install neovim in the live media because neovim now has an (asynchronously rendered) builtin terminal feature, so it'd be super easy to open a terminal in a window split, then in NORMAL mode copy the contents, or save it to a file, etc, and I could curl that to some paste bin... but the live media keeps burning to the ground on me! hehe

Last edited by trusktr (2015-03-25 05:33:10)

jasonwryan · 2015-03-25 06:10:04

Not a Pacman issue, moving to NC...

apg · 2015-03-25 08:20:09

The error has nothing to do with the cache. You clearly upgraded pacman since 2013 without upgrading the rest of your system at the same time, so you still have an old version of libarchive missing a necessary patch.

trusktr · 2015-04-08 06:21:08

@apg I was chrooting into the old root of the old system, and using that system's pacman, so I don't think that libarchive can be newer. When chrooted, I checked /var/log/pacman.log and it showed the last system upgrade (which would include libarchive) in Nov 2013.

Or does chrooting do some magic I didn't know about and it's using libarchive from the system I ran chroot in?

Anyway, I'm still blocked by https://bbs.archlinux.org/viewtopic.php?pid=1514016. I tried this month's live media with no luck yet in order to troubleshoot this thread's issue.

Last edited by trusktr (2015-04-08 06:22:21)

apg · 2015-04-08 06:50:04

trusktr wrote:

@apg I was chrooting into the old root of the old system, and using that system's pacman, so I don't think that libarchive can be newer. When chrooted, I checked /var/log/pacman.log and it showed the last system upgrade (which would include libarchive) in Nov 2013.
Or does chrooting do some magic I didn't know about and it's using libarchive from the system I ran chroot in?
Anyway, I'm still blocked by https://bbs.archlinux.org/viewtopic.php?pid=1514016. I tried this month's live media with no luck yet in order to troubleshoot this thread's issue.

I said pacman is newer, not libarchive. The error message you presented was added in pacman 4.2.0 which is only a few months old. Run pacman from somewhere other than the installation root.

trusktr · 2015-04-08 06:52:25

@apg I don't understand how it can be that when I chroot into a system from 2013 it will have pacman from a few months ago when I haven't updated that system. What detail am I missing here?

trusktr · 2015-04-08 07:05:19

Well, actually, I believe I arch-chrooted into it. Does arch-chroot replace the target pacman with the outer system's pacman?

trusktr · 2015-04-08 07:53:06

Hang on a second! What the heck. I meant to say that I used systemd-nspawn, NOT arch-chroot!

Last edited by trusktr (2015-04-08 07:54:40)

Spider.007 · 2015-04-08 12:06:06

Pacman probably prompted you it wanted to upgrade itself first, which you did. I'm not sure where the current list of packages comes from but they aren't all the latest, (for example, btrfs-progs is on 3.19 since 2015-03-12); what command did you enter to get this list? Might you be using an out-of-date mirror?

trusktr · 2015-04-08 17:28:04

@Spider.007 I'll check as soon as I get unblocked from my other problem. I normally have kernel.org and other good ones at the top of mirrorlist. I wonder if you're right, that pacman updated itself first causing problems with old packages? Maybe arch-chroot will work better. I'll try it when I'm unblocked from the other issue.

Arch Linux

#1 2015-03-13 05:59:57

pacman error: mtree specification has different type

#2 2015-03-13 10:16:05

Re: pacman error: mtree specification has different type

#3 2015-03-25 05:25:36

Re: pacman error: mtree specification has different type

#4 2015-03-25 06:10:04

Re: pacman error: mtree specification has different type

#5 2015-03-25 08:20:09

Re: pacman error: mtree specification has different type

#6 2015-04-08 06:21:08

Re: pacman error: mtree specification has different type

#7 2015-04-08 06:50:04

Re: pacman error: mtree specification has different type

#8 2015-04-08 06:52:25

Re: pacman error: mtree specification has different type

#9 2015-04-08 07:05:19

Re: pacman error: mtree specification has different type

#10 2015-04-08 07:53:06

Re: pacman error: mtree specification has different type

#11 2015-04-08 12:06:06

Re: pacman error: mtree specification has different type

#12 2015-04-08 17:28:04

Re: pacman error: mtree specification has different type

Board footer