Your message dated Tue, 26 Nov 2013 05:18:39 +0100 with message-id <1385439519.2203.25.camel@localhost> and subject line Re: Bug#729681: globus-core: should not migrate yet has caused the Debian Bug report #729681, regarding globus-core: should not migrate yet to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 729681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: globus-core Version: 8.16-1 Severity: serious The full Globus Toolkit 5.2.5 should migrate to testing together. However many of the updated packages got diverted to the new queue due to package splits/renames done in order to support Multi-Arch. This bug is filed to prevent the migration of globus-core before the packages diverted to the new queue are ready to migrate. Mattias
smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---notfound 729681 globus-core/8.16-1 thanks mån 2013-11-25 klockan 20:30 +0000 skrev peter green: > > > > The full Globus Toolkit 5.2.5 should migrate to testing together. > > However many of the updated packages got diverted to the new queue due > > to package splits/renames done in order to support Multi-Arch. > > > > This bug is filed to prevent the migration of globus-core before the > > packages diverted to the new queue are ready to migrate > It seems a load of globus related packages just migrated and now have > uninstallable build-dependencies in testing because globus-core is > blocked from testing migration by this bug (and by being too young). > > globus-xioperf globus-gram-job-manager-sge > globus-gram-job-manager-pbs globus-gram-job-manager-lsf > globus-gass-cache-program You are correct. My intention with this bug was to block the migration of these packages. But apparently unfulfilled build dependencies do not block migration as I expected it would have done. Is there a reason why only unfulfilled runtime dependencies block migration and not unfulfilled build dependencies? I did not expect this. My plan was to wait until all the packages (there are 56 packages that build requires globus-core (>= 8.16)) had stayed the required 10 days in unstable and were ready to migrate and then remove this blocking bug and have all the packages move together. But since missing build dependencies did not block migration as I expected this did not work. There really is no point to have this bug any more, since the broken build dependencies I was trying to avoid happened anyway. Mattias
Description: This is a digitally signed message part
--- End Message ---
