Summary: | www-client/httrack-[3.45.4,3.46.1]: Collision with /usr/share/httrack/html belonging to earlier 3.44.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Manfred Knick <Manfred.Knick> |
Component: | Current packages | Assignee: | Sebastian Pipping <sping> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | cickumqt, luksan, Manfred.Knick |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | .../httrack-3.45.4/temp/build.log |
Description
Manfred Knick
2012-10-15 17:45:13 UTC
Hello Manfred, installing httrack 3.45.4 and then 3.46.1 works well for me. If you use the emerge(1) command (rather than the ebuild(1) command) a package should never collide on files with itself. If it does (as in your case) you should probably: a) switch to command emerge if you currently use command ebuild b) upgrade portage if it isn't at the latest version c) report a bug against portage with a detailed recipe on reproduction if you use the emerge command and the latest portage I see no way this could be a bug about httrack in particular so I am closing the bug as "works for me". I hope that's okay with you. (In reply to comment #1) Please, _read_ before guessing wildly ... cite: "Steps to Reproduce:" "1. emerge -auDN" > If you use the > emerge(1) command (rather than the ebuild(1) command) a package should ... Agreed: "should" ! > I see no way this could be a bug about httrack in particular Well, the fact that _you_ can't see it doesn't prove anything. The fact that _only_ httrack throws this problem on my box sounds not like a very strong indication for blaming portage in excuse. > so I am closing > the bug as "works for me". > I hope that's okay with you. NO. To-day, "emerge -auDN --jobs=8 --load-average=16.0 --keep-going system world" still results in the same reported behavior. THUS: RE-OPEN. Thanks. P.S.: As always, I am prepared to provide more detailed information as being requested precisely and politely. (In reply to comment #2) > (In reply to comment #1) > > Please, _read_ before guessing wildly ... I did miss the version number of portage in your post, that's correct. However, portage for a reason was not a wild guess. There is no need for shouting in here. Please attach the full build logs from running $ sudo emerge -1 =www-client/httrack-3.44.5 $ sudo emerge -1 =www-client/httrack-3.45.4 to this bug. Thanks. (In reply to comment #3) > I did miss the version number of portage in your post, that's correct. Again: The point was "use command ebuild" - but let's forget about it. > Please attach the full build logs from running > > $ sudo emerge -1 =www-client/httrack-3.44.5 Just simply works and installs. > $ sudo emerge -1 =www-client/httrack-3.45.4 fails. /var/tmp/portage/www-client/httrack-3.45.4/temp/build.log will follow as an attatchment. > to this bug. Thanks. Created attachment 327176 [details]
.../httrack-3.45.4/temp/build.log
httrack-3.45.4 build.log : COLLISION
# emerge -aC httrack : removes /usr/share/httrack/html # emerge httrack : successfully installs : # equery list httrack ... [IP-] [ ] www-client/httrack-3.45.4:0 Thanks. unmasking : "<=www-client/httrack-3.46.99 ~amd64" , # emerge -auDN successfully upgrades to # equery list -p httrack ... [IP-] [ ] www-client/httrack-3.46.1:0 Thanks. Works for me too. Thanks. But it is strange to be obliged to emerge -C before. Closing as obsolete. Please re-open as needed. (In reply to Sebastian Pipping from comment #9) > Closing as _obsolete_ . Please re-open as needed. Confirmation: Since that one-time-"emerge -C" (c.f. comments 4 and 6), the conflict never re-appeared again. equery list httrack [IP-] [ ] www-client/httrack-3.48.22:0 @ Sebastian: Thanks! |