Have puppet generate a list of packages along with the bug links that go with them maybe? I don't care how you go about it as long as it's automated. If there's a manual process it's not an acceptable solution.
On Thu, Nov 14, 2013 at 12:48 AM, Petr Bena <[email protected]> wrote: > at least it would be a list where I can press ctrl +f in my browser in > figure out if package X is supported within 2 seconds, unlike the > other mentioned solutions which may take several hours > > On Thu, Nov 14, 2013 at 9:47 AM, Petr Bena <[email protected]> wrote: > > But aren't some packages in other classes too? I thought that lot of > > packages are inherited from other classes and these can't be in puppet > > on multiple places, or can they be? If literally all packages that are > > installed on exec nodes were in exec manifest, that would be a perfect > > list > > > > On Thu, Nov 14, 2013 at 2:59 AM, Marc-André Pelletier > > <[email protected]> wrote: > >> On 11/13/2013 05:37 PM, Brad Jorsch (Anomie) wrote: > >>> Sure there is: look in bugzilla for an existing bug requesting the > package. > >> > >> For that matter, the authoritative list is the actual exec_environ > >> manifest in puppet and additions to it stemming from bugzilla'd requests > >> are commented accordingly. > >> > >> -- Marc > >> > >> > >> _______________________________________________ > >> Labs-l mailing list > >> [email protected] > >> https://lists.wikimedia.org/mailman/listinfo/labs-l > > _______________________________________________ > Labs-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/labs-l >
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
