
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Fri, 14 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/reposync/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-14-rhel-airgap-download-with-dependencies.en</guid>
    <title>Downloading on the Outside for an Air-Gapped Transfer — dnf download, reposync, and yumdownloader Solve Different Problems</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-14-rhel-airgap-download-with-dependencies.en</link>
    <description>A command-by-command walkthrough of the real procedure for pulling RHEL packages, dependencies and all, on an internet-connected machine so the result can be carried into an air-gapped network. It covers exactly what --resolve and --alldeps do differently in dnf download, why dependencies quietly go missing because of packages that are already installed on the download host, and how creating an empty root with --installroot removes that trap, quoting the official documentation directly. It also covers the fact that in an empty installroot the release version is not derived from the rpmdb, so the transaction fails unless --releasever is passed, and that modular systems additionally need module_platform_id set. It then organises the options of dnf reposync, which clones a repository wholesale, around --download-metadata, --newest-only, --gpgcheck, and --delete, explains when yumdownloader is the right call, and finishes with how to verify that what you downloaded is dependency-complete using dnf repoclosure. A table compares the option names that change under dnf5 on RHEL 10.</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>linux</category><category>rhel</category><category>air-gap</category><category>dnf</category><category>rpm</category><category>reposync</category><category>package-management</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-14-rhel-airgap-download-with-dependencies.ja</guid>
    <title>閉域網への持ち込みのために外側で受け取る — dnf download、reposync、yumdownloader はそれぞれ別の問題を解きます</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-14-rhel-airgap-download-with-dependencies.ja</link>
    <description>インターネットに接続された機材で RHEL パッケージを依存関係ごとまとめて受け取り、閉域網へ持ち込むための実際の手順をコマンド単位で整理します。dnf download の --resolve と --alldeps が正確に何を変えるのか、なぜすでにインストール済みのパッケージのせいで依存関係が静かに抜け落ちるのか、そして --installroot で空のルートを作ってその落とし穴をなくす方法を、公式ドキュメントの文章とともに扱います。空の installroot では releasever が rpmdb から導出されずトランザクションが失敗するため --releasever を必ず渡さなければならないこと、モジュラーシステムでは module_platform_id まで指定しなければならないことも押さえます。続いてリポジトリ全体を複製する dnf reposync のオプションを --download-metadata、--newest-only、--gpgcheck、--delete を中心に整理し、yumdownloader をいつ使うのか、受け取った結果が依存関係の面で完全かどうかを dnf repoclosure でどう検証するのかまでつなげます。RHEL 10 の dnf5 でオプション名が変わる部分も表で比較します。</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>linux</category><category>rhel</category><category>air-gap</category><category>dnf</category><category>rpm</category><category>reposync</category><category>package-management</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-14-rhel-airgap-download-with-dependencies</guid>
    <title>폐쇄망 반입을 위해 밖에서 받기 — dnf download, reposync, yumdownloader는 서로 다른 문제를 풉니다</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-14-rhel-airgap-download-with-dependencies</link>
    <description>인터넷이 연결된 장비에서 RHEL 패키지를 의존성까지 통째로 받아 폐쇄망에 반입하는 실제 절차를 명령 단위로 정리합니다. dnf download의 --resolve와 --alldeps가 정확히 무엇을 다르게 하는지, 왜 이미 설치된 패키지 때문에 의존성이 조용히 빠지는지, 그리고 --installroot로 빈 루트를 만들어 그 함정을 없애는 방법을 공식 문서 문장과 함께 다룹니다. 빈 installroot에서는 releasever가 rpmdb에서 유도되지 않아 트랜잭션이 실패하므로 --releasever를 반드시 넘겨야 한다는 점, 모듈러 시스템에서는 module_platform_id까지 지정해야 한다는 점도 함께 짚습니다. 이어서 저장소 전체를 복제하는 dnf reposync의 옵션을 --download-metadata, --newest-only, --gpgcheck, --delete 중심으로 정리하고, yumdownloader를 언제 쓰는지, 받은 결과가 의존성 측면에서 완전한지 dnf repoclosure로 어떻게 검증하는지까지 이어갑니다. RHEL 10의 dnf5에서 옵션 이름이 달라지는 부분도 표로 비교합니다.</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>linux</category><category>rhel</category><category>air-gap</category><category>dnf</category><category>rpm</category><category>reposync</category><category>package-management</category>
  </item>

    </channel>
  </rss>
