On 2013-12-22 03:45, T o n g wrote: > Hi, > > I want to adopt the par2cmdline package, but on its QA page, > http://packages.qa.debian.org/p/par2cmdline.html > it says, > > ,----- > | "This package is part of the ongoing testing transition known as > | auto-libunwind. Please avoid uploads unrelated to this > | transition, they would likely delay it and require supplementary > | work from the release managers." > `----- > > what's the impact on me adopting/building/uploading the package? > > Thanks > >
Hi, In the particular case, not much. libunwind is somewhat a special case, which is mostly done except on ia64. On that architecture, pretty much everything depends on libunwind because gcc inserts a dependency when it compiles the binaries. Note that there are currently two trackers for libunwind (and several other transitions actually). A manually set up one[1] and one set up by a new tool we are testing[2]. The latter are prefixed with "auto-" to avoid name clashes with transitions set up manually. ~Niels [1] http://release.debian.org/transitions/html/libunwind.html [2] http://release.debian.org/transitions/html/auto-libunwind.html (also, see the "Notes:") -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
