<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://status.packit.dev"/>
    <title>Downstream Jobs on Packit Service Status</title>
    <link>https://status.packit.dev/affected/downstream-jobs/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2025-11-20T01:00:00+00:00</lastBuildDate>
    <updated>2025-11-20T01:00:00+00:00</updated>
    
    
    
      <atom:link href="https://status.packit.dev/affected/downstream-jobs/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] Fedora Anubis</title>
        <link>https://status.packit.dev/issues/2025-11-20-fedora-anubis/</link>
        <pubDate>Thu, 20 Nov 2025 01:00:00 +0000</pubDate>
        <guid>https://status.packit.dev/issues/2025-11-20-fedora-anubis/</guid>
        <category>2025-12-02T18:00:00&#43;00:00</category>
        <description>Packit downstream jobs may not work as expected due to the new Anubis rules deployed in Fedora Infrastructure. For example, sometimes Packit gets back an HTML page with the Anubis disclaimer instead of the specfile or the packit yaml config. Waiting and retriggering a job could work around the issue.</description>
        <content type="html">&lt;p&gt;Packit downstream jobs may not work as expected due to the new &lt;em&gt;Anubis&lt;/em&gt; rules deployed in Fedora Infrastructure.
For example, sometimes Packit gets back an HTML page with the &lt;em&gt;Anubis&lt;/em&gt; disclaimer instead of the specfile or the packit yaml config.
Waiting and retriggering a job could work around the issue.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
