FS#9267 - Inconsistency in mkarchroot/makechrootpkg package db

Attached to Project: Pacman
Opened by Jaroslaw Swierczynski (swiergot) - Saturday, 19 January 2008, 20:54 GMT
Last edited by Dan McGee (toofishes) - Thursday, 07 February 2008, 04:40 GMT
Task Type Bug Report
Category Scripts & Tools
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture All
Severity Medium
Priority Normal
Reported Version 3.1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Let's assume we create a chroot with base and base-devel groups. Then we use makechrootpkg to build a package that depends on not installed package so this package gets installed in the union fs. Then, trying to update the chroot, pacman doesn't see any package that was installed by makechrootpkg.

I've stumbled upon this situation with qt. I changed a dependency of a package from qt to qt3 and wanted to rebuild it, makechrootpkg tried to install qt3 but it got file-exists-in-filesystem errors (of course prior 'mkarchroot -u' didn't replace qt with qt3 as it didn't see it installed).

A possible solution would be to create union fs in mkarchroot instead of makechrootpkg. I'd be happy to provide a patch but right now I don't have time. I'll do it next week unless someone does it first.
This task depends upon

Closed by  Dan McGee (toofishes)
Thursday, 07 February 2008, 04:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in devtools-0.5. Please file any bug reports one per report, I think everything here was fixed.
Comment by Jaroslaw Swierczynski (swiergot) - Saturday, 19 January 2008, 21:03 GMT
Oh and by the way, those /srcdest and /pkgdest directories, they are not chowned nobody like /build is.
Comment by Jaroslaw Swierczynski (swiergot) - Saturday, 19 January 2008, 21:15 GMT
Also, in makechrootpkg:

clean_first=""

should be:

clean_first="0"

and:

cp "$basef" "$uniondir/build/"

should be:

cp "$basef" "$uniondir/srcdest/"
Comment by Aaron Griffin (phrakture) - Tuesday, 22 January 2008, 00:57 GMT
This is by design. The readonly chroot is to be managed separately from the rw portion. The rw portion should be cleaned by the user, and dep packages should be removed after build.

Regarding the other bugs here, could we please keep one bug report per bug, I have too much to organize as is, and adding in "oh yeah there's two more bugs in the comments here" is just asking for trouble.
Comment by Dan McGee (toofishes) - Tuesday, 22 January 2008, 01:01 GMT
This is a GIT repository- patches to fix these problems would get applied MUCH quicker then us going in and fixing them ourselves, even though the patches are trivial.
Comment by Aaron Griffin (phrakture) - Wednesday, 23 January 2008, 17:37 GMT
Is this sufficient?
http://code.phraktured.net/?p=devtools.git;a=commitdiff;h=912fe3dcd1f9acead96ad8edf3d848bc30f21ba0
Comment by Jaroslaw Swierczynski (swiergot) - Wednesday, 23 January 2008, 17:57 GMT
Seems ok. As for the original problem, ok, it's by design, so how about clearing the rw portion automatically or at least give user a warning if it's not cleared.
Comment by Aaron Griffin (phrakture) - Wednesday, 23 January 2008, 21:30 GMT
Oh, huh the default args need -r too, that's the issue. I changed it on my machine, not in git 8)
Comment by Jaroslaw Swierczynski (swiergot) - Saturday, 26 January 2008, 12:55 GMT
Just to make sure this doesn't get lost, I still don't see -r in your git repository.
Comment by Dan McGee (toofishes) - Thursday, 07 February 2008, 04:40 GMT
http://projects.archlinux.org/git/?p=devtools.git;a=commit;h=0410fb0a2f2bdaf3d127e54ec232eddbfc0f70dd

Loading...