Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfsonar-archive missing from .deb repository?

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfsonar-archive missing from .deb repository?


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Jarett DeAngelis <>, "" <>
  • Subject: Re: [perfsonar-user] perfsonar-archive missing from .deb repository?
  • Date: Fri, 17 Mar 2023 18:46:43 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=EQmoKcVF0h/IWf/7iNQOAWrZwHC2Zauk0GlTgn1mTPg=; b=OL4bXx/hx4FRtz9h3h4U+i+KQUADTT3hFo+4hYYF8CYlwnaXGNbd4yalRme8eAX2kufD6c2Q2cb31pSU/T6NIrDpSlQNYTMT2Oqts3VcXmE+KYos11MZd3v0/9/Aqia4DXLjApFG0TXSihRi63Ll1h05myV8EXaggn9BQZhNwi/5LyzOXVkkJk95nD+bpUeJgkjneWX3W+malEnZARz5/PNbQ4JtlnWr5CVxEUD0epzepwE4LMFMjuHYr69NePaL8Zo6M4dEwnU90SSsOLxD2bzaO39L60c/BxdZ1jUTCkIfHZ26mv2EMqhib2E+G7eKcbVtaLThCZfoUU+px5CIlw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=a6XKKWISJZE4+WhoBm+WEeXGbOow27fxHU6mPqJvTknnYWZ78ACdldMCIAuih0yZ+PoCqLuscv7FlvjDO+QWnoTkmP72+dLYaV3pNAPQYXpvFtc8GWk6fOqsUKCqnPZn24V6UTtt0EqjUYXL1F1WUXztaDpW/FduG8HGvMV2KwLpQeGngnFv0g4KEgSz+V2Ppb3dmvufbe3K2y1Rs6ATRKCXQzGozOuwl0BXf4VjAjnVKbbOt2e2RyQ06ODUYFBs28MlZKjgnXXhx4uio+NRZaAK2SSxc/iWoRKxh2oX85eCf4ndsRgaQh0ABidRCtjzZ5ApH1leVYSxtRukhpQSsg==

Jarett DeAngelis writes:


I am currently trying out the ansible playbook published on the perfsonar github and it's telling me there is no "perfsonar-archive" package, which I figured must have been some misconfiguration but it really does appear not to exist?

 

Is this a bug or intentional?

 

It’s a little of both.  The Ansible playbooks haven’t been brought into the branching scheme we use during development and some 5.0-isms slipped in.

 

I’ll poke the responsible parties.

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page