Cyrus Jones wrote: > Not uploading wesnoth-tools is a relatively simple fix, as it is not a > required dependency.
You don't upload binary packages. You upload source packages, and the binaries specified in debian/control are built in the buildds. So you will need to undo the changes or use the current 1.4-1 packaging). > And yes, there are a number of packaging changes. But the upstream > release (not Debian) is a simple bugfix release, so it would be good if > 1.4.1 could be used. Using the current debian directory is a > possibility, but not good when it comes to compatibility with Debian > (will make syncing with Debian more difficult). It will make it impossible *for hardy-updates*. For Intrepid, it will be automatically synced. So I can't see a big issue here. > If this bug won't be fixed due to these changes in packaging, I think > Won't Fix status would be a better choice for this bug report (rather > than Invalid). Otherwise, it should be marked as New if the new package > has some chance of succeeding in hardy-updates or possibly hardy- > backports (then this bug report would need to be changed). It's not a very good candidate for hardy-updates, read the https://wiki.ubuntu.com/StableReleaseUpdates, which says that the changes must be minimal ("A minimal patch") And for a backport, we need a hardy-backports product task, but first we need to get 1.4.1 in Intrepid! :) Cheers -- Please sync wesnoth 1:1.4.1-2 (universe) from Debian unstable (main). https://bugs.launchpad.net/bugs/220723 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
