<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.pld-linux.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://www.pld-linux.org/feed.php">
        <title>PLD Linux Distribution todo</title>
        <description></description>
        <link>https://www.pld-linux.org/</link>
        <image rdf:resource="https://www.pld-linux.org/_media/favicon.ico" />
       <dc:date>2026-04-14T15:35:21+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://www.pld-linux.org/todo/builderinfrastructure?rev=1217713139&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.pld-linux.org/todo/ftpinfrastructure?rev=1217713115&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://www.pld-linux.org/_media/favicon.ico">
        <title>PLD Linux Distribution</title>
        <link>https://www.pld-linux.org/</link>
        <url>https://www.pld-linux.org/_media/favicon.ico</url>
    </image>
    <item rdf:about="https://www.pld-linux.org/todo/builderinfrastructure?rev=1217713139&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-08-02T23:38:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>todo:builderinfrastructure</title>
        <link>https://www.pld-linux.org/todo/builderinfrastructure?rev=1217713139&amp;do=diff</link>
        <description>Builder Infrastructure TODO List

It is advisable to read up on how the builder infrastructure works before diving into this text. 

Note: the whole system is written in python. 

Atomic upgrades across builders

Currently automatic upgrades on builders work like this -- if a package is built successfully and the request has the 'upgrade' flag set, the newly built packages get upgraded over what was previously installed on a given builder. The status of an upgrade (OK/FAILED) gets mailed to the …</description>
    </item>
    <item rdf:about="https://www.pld-linux.org/todo/ftpinfrastructure?rev=1217713115&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-08-02T23:38:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>todo:ftpinfrastructure</title>
        <link>https://www.pld-linux.org/todo/ftpinfrastructure?rev=1217713115&amp;do=diff</link>
        <description>FTP Infrastructure TODO List

Note: the whole system is written in python. 

Add &quot;ignore removed arch&quot; to mvpkgs

The title says it all. A quickie. 

Make mvpkgs and testmvpkgs handle duplicates given as arguments

Running the scripts with wildcards (as in</description>
    </item>
</rdf:RDF>
