we need this easy fix : 

diff --git a/po-debconf.spec b/po-debconf.spec
index 17bd1f4..a20bb6f 100644
--- a/po-debconf.spec
+++ b/po-debconf.spec
@@ -26,7 +26,7 @@ Patch0:               po-debconf-1.0.16-fix-prefix.patch
 BuildArch:     noarch
 
 BuildRequires: po4a
-BuildRequires: dpkg-devel
+BuildRequires: dpkg-dev
 
 # Needed for check
 %if %{with check}

Thanks (I mixed it with the debconf FTBFS that has to do with perl...)

* Built:
  https://koji.fedoraproject.org/koji/buildinfo?buildID=455023
* Will merge this fix to F19, F18.

Hi Oron, 
The Fedora rules says that you should use: git merge master, unless you have a good reason to not do it which isn't the case :

I see in 
http://pkgs.fedoraproject.org/cgit/po-debconf.git/

that F19 enter in other way ... 

typically I use:

fedpkg pull
fedpkg switch-branch master
edit spec
fedpkg mockbuild (test it)
fedpkg new-sources something.tar.bz2
fedpkg clog 
fedpkg commit -F clog
fedpkg push
fedpkg build

for next branch I do , (and you should do it also) 
fedpkg switch-branch f19; git merge master; fedpkg push
fedpkg build
fedpkg update

For F18 again:
fedpkg switch-branch f18; git merge master; fedpkg push
fedpkg build; fedpkg update

(In reply to comment #3)

I cherry-picked the commit from master to f19, because
the previous commit was about perl-5.18 build which isn't relevant to f18-f19.
As a result, the release number was 2 and not 3.

I could have done complete merge, as this previous commit only
contained a comment and not functional change -- however, I thought
this would be misleading.

Now I merged f19 into f18 -- they are identical.

po-debconf-1.0.16-2.nmu2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/po-debconf-1.0.16-2.nmu2.fc18

po-debconf-1.0.16-2.nmu2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/po-debconf-1.0.16-2.nmu2.fc19

(In reply to Oron Peled from comment #4)
> (In reply to comment #3)
> 
> I cherry-picked the commit from master to f19, because
> the previous commit was about perl-5.18 build which isn't relevant to
> f18-f19.
> As a result, the release number was 2 and not 3.
> 
> I could have done complete merge, as this previous commit only
> contained a comment and not functional change -- however, I thought
> this would be misleading.
> 
> Now I merged f19 into f18 -- they are identical.

The code is the same, the package is the same, the source of f20 should be the same, only when we have different versions like kernel, x11-xorg-server or gnome.
But you could ask on devel mailing list , I convinced that you should use git merge master , instead of cherry pick  .

and releases we should be: 
po-debconf-1.0.16-3.nmu2.fc20
po-debconf-1.0.16-3.nmu2.fc19
po-debconf-1.0.16-3.nmu2.fc18 

and miss : 
po-debconf-1.0.16-2.nmu2.fc18 	
po-debconf-1.0.16-2.nmu2.fc19
because perl rebuild was for -2 and we not rebuilt for f18 and f19

Hi, Oron you could give me commit permissions on 

https://admin.fedoraproject.org/pkgdb/acls/name/po-debconf 

and

https://admin.fedoraproject.org/pkgdb/acls/name/debhelper

Package po-debconf-1.0.16-2.nmu2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing po-debconf-1.0.16-2.nmu2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-14450/po-debconf-1.0.16-2.nmu2.fc18
then log in and leave karma (feedback).

po-debconf-1.0.16-2.nmu2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

po-debconf-1.0.16-2.nmu2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.