On 2/19/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/2/19, Dan McGee <dpmcgee@gmail.com>:
To put this in context for those on the list, Roman reported this possible bug on IRC: <http://pastebin.archlinux.org/1559>.
I couldn't duplicate it with some test packages I developed specifically to test it. If anyone else has seen something like this come up with pacman3, be sure to post it here. The basic summary of the bug is this: (at least) two files moved from one package to another, and they were incorrectly identified as conflicts, even though they were only present in one package to be installed.
I didn't update my system due to these conflicts, so I can reproduce it again. I can also send you my local and unstable db snapshots, old beryl packages and --debug=3, whatever you want. As soon as I get back home I'll send output from the latest CVS version of pacman (that includes "improved debug output to file conflict checking"), maybe this will help to spot issue
I'd appreciate you running it with my new debug output, that should be helpful. How about the following (if you want to just send it to me and not clog the list with attachments, that is fine): 1. (CVS version) pacman3 -Su --debug > output.txt 2. (CVS version) pacman3 -Su --debug=3 > output3.txt 3. The filelists from the old bery packages with significance (whichever packages had the files that changed hands, beryl-plugins-svn and beryl-plugins-unsupported-svn) I am going to be a bit busy early this week with schoolwork, but hopefully this will get resolved in the near future. -Dan