Hi Ben, hi Trent,
On Thu, 20.08.2009 at 17:30:40 +0100, Ben Wheeler <[email protected]> wrote: > This may be a kind of duplicate of #542585 but I wanted to make the points > that (a) it still affects 1.4.9-2, and (b) it affects fresh installations, > not just upgrades (so for clarity I think if they are the same bug, #542585 > should be marked a duplicate of this one rather than the other way around, > or the title of the former bug changed.) I must confirm that the problem also occurs on a fresh install, but I need to look into this a bit more because there is no mentioning of /build in either postinst or md5sums, or anything. IOW, I think that something in the Python packages tool chain seems to have changed quite a bit, because I didn't change the packaging except for deleting the bogus /build directory. # dpkg -i roundup_1.4.9-0_all.deb (Reading database ... 42384 files and directories currently installed.) Preparing to replace roundup 1.4.9-0 (using roundup_1.4.9-0_all.deb) ... Stopping Roundup HTTP-Server: roundup-server. Unpacking replacement roundup ... Setting up roundup (1.4.9-0) ... Service roundup already added. Starting Roundup HTTP-Server: roundup-server. Processing triggers for man-db ... # ls / bin build dev home initrd.img lib64 media opt root selinux sys usr vmlinuz boot cdrom etc initrd lib lost+found mnt proc sbin srv tmp var Please note the (imho) bogus /build directory, which gives rise to a lot of lintian warnings. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
