On Wed, Jun 26, 2013 at 06:59:41AM BST, Petter Reinholdtsen wrote: > Hi. Very glad to hear you tested isenkram. :)
Your blog post prompted me to do so :^) > > New version of the package (0.4) is impossible to install due to error > > in dependencies: > > > > dep: python (<< 2.7) > > > > However, version of Python available in unstable is 2.7.5-2. > > Obs. My mistake. I forgot to build it using pbuilder. If you > rebuild the source, it should work fine. I'll reupload with fixed > dependencies. The package work fine with any python, but the build > system insert specific versions as dependencies. OK, it makes sense now. No worries. What if after the upload, the package only gets added to the repository after its dependencies are met? That would eliminate a number of bugs like this one, i.e. unable to install due to unmet dependencies. The upload queue could be set to an arbitrary number/time after which, if the dependencies have not been resolved [0] it drops the package from the queue. That would help with the errors mentioned above but also aid with transitions and possibly with a situation when a package is being removed from a pool for a specific release and other ones, which depend on it, are then "hidden" from the pool and their maintainers informed (this should be handled with care as we wouldn't like a situation where a major chunk of the repository disappears). Recently, after unstable thaw(?), I had all of the above happen to me. I have filed a couple of bugs because of it but it would be nice if that was done automatically... Just a thought :^) Thanks a lot for a prompt response. Cheers, Raf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
