Surely we need a regression testing system that can pick up bugs like this?
Perhaps a script could install from a collection of packages and run each associated executable, expecting the program to remain running for a certain amount of time. Programs which require interaction should not ordinarily exit immediately, so you could detect if something has gone wrong. Another way would be to get a list of /usr/lib/* from apt-file for Breezy and compare that to /usr/lib/* for Gutsy. That's potentially a quick list of libraries that might have fallen off the bus. Of course, apt-file itself fell off the bus in Gutsy since there's no Contents.i386 file on the CDROM. -- smc - Secret Maryo Chronicles - unmet dependency in Gutsy https://bugs.launchpad.net/bugs/136435 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
