From 2f06ce98647b19a3bc67a348ff97f53be394f48c Mon Sep 17 00:00:00 2001
From: arcan1s <esalexeev@gmail.com>
Date: Fri, 1 Aug 2014 23:06:00 +0400
Subject: [PATCH] fix 404

---
 _posts/2014-03-23-creating-custom-repo.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_posts/2014-03-23-creating-custom-repo.html b/_posts/2014-03-23-creating-custom-repo.html
index 24577cb..c3104f1 100644
--- a/_posts/2014-03-23-creating-custom-repo.html
+++ b/_posts/2014-03-23-creating-custom-repo.html
@@ -58,7 +58,7 @@ fi
 <p><code>${REPODIR}/{i686,x86_64}</code> are directories for repository, <code>${PREPAREDIR}</code> is directory where compiled packages will be stored, <code>${STAGINGDIR}</code> is one where packages will be built.</p>
 
 <h2><a href="#theory" class="anchor" name="theory"><span class="octicon octicon-link"></span></a>A bit of theory</h2>
-<p>Create directory, share it (using <a href="/2014/03/06/site-changes/" title="Site changes paper">ftp</a>, for example). It has two subdirectories - <code>i686</code> and <code>x86_64</code> - for each architecture respectively. And fill them with a set of packages.</p>
+<p>Create directory, share it (using <a href="/en/2014/03/06/site-changes/" title="Site changes paper">ftp</a>, for example). It has two subdirectories - <code>i686</code> and <code>x86_64</code> - for each architecture respectively. And fill them with a set of packages.</p>
 
 <p>Updating repository may be split into the following steps:</p>
 <ol>