On 2014-10-29 17:57, Ian Jackson wrote: > [...] > > I therefore propose to upload a test package. That is, a package > whose only purpose is infrastructure testing. Its contents aren't > very important (but it would obviously be dfsg-free). Such a package > should probably be normally uploaded to experimental, but might need > to be uploaded to unstable on rare occasions. > > The test package obviously ought not to propagate to testing, even if > (accidentally or deliberately) uploaded to unstable. This could be > achieved by filing an RC bug and/or by adding dependencies which will > never be satisfied. > > [...] > > Thanks, > Ian. > >
Hi Ian, Assuming the package never reaches (or never intend to reach) testing, I believe it falls outside our jurisdiction to decide whether such a package should be allowed in unstable/on our infrastructure. It should definitely not reach testing as it will never belong in a stable release. An RC bug should work for that purpose. For an added "safety", feel free to add a Breaks/Conflicts with an (pseudo-)essential package like bash or dpkg. Though, from a personal point of view, it sounds like we are missing a "test" infrastructure, where you could do this kind of upload/testing instead of abusing the main archive. I believe the idea establishing of such a test infrastructure was brought up at DebConf14 during the talk about how to introduce things a la build-profiles. ~Niels -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
