> For an SRU it needs someone to investigate the status on each affected > release and document what is needed for each and come up with a plan.
Can I find documentation somewhere what kind of information is needed, and how to obtain it? I found [1] but there is no mention of dependencies of the SRU package there. I am willing to help, I guess I could try and build fpc on all the previous Ubuntu releases, as well as the rdependent packages? Is this best done after it is synced in Jaunty? I have problems with building lazarus in a pdebuild environment, because the clean rule that is run before the package is put in the jail involves too much for my system. Is there a better approach than using pdebuild? Does anybody see any problem with the licenses mentioned in a previous comment [2]? Is there a good example of an SRU bug which involved as much as this bug, so that I have an idea of how this should be handled? [1] https://wiki.kubuntu.org/DistributedDevelopment/Requirements/SRU [2] https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/275688/comments/22 Kind regards, Paul -- Please sync fpc 2.2.2-4 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/275688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
