I get the following:

qaa% svn st
M       config.dat
M       dpkg-l
M       grub.cfg
M       mutt-v
M       postconf
M       selections
M       version.out
qaa% svn pl -v etc/apache2/mods-available/dnssd.conf
Properties on 'etc/apache2/mods-available/dnssd.conf':
  source
    qaa:/etc/apache2/mods-available/dnssd.conf
  svn:mime-type
    text/plain
qaa% svn diff etc/apache2/mods-available/dnssd.conf
qaa% svn revert -R .
Reverted 'selections'
Reverted 'version.out'
Reverted 'postconf'
Reverted 'etc/apache2/conf-available/javascript-common.conf'
Reverted 'etc/apache2/mods-available/dnssd.load'
Reverted 'etc/apache2/mods-available/dnssd.conf'
Reverted 'mutt-v'
Reverted 'config.dat'
Reverted 'grub.cfg'
Reverted 'dpkg-l'
qaa% svn pl -v etc/apache2/mods-available/dnssd.conf
Properties on 'etc/apache2/mods-available/dnssd.conf':
  source
    qaa:/etc/apache2/mods-available/dnssd.conf
  svn:mime-type
    text/plain
qaa%

I don't see why etc/apache2/mods-available/dnssd.conf is signaled
as reverted. Is there some data corruption somewhere?

This seems reproducible.

But see also the following thread I've started:
https://lists.apache.org/thread/p1ky889bxwy8okqly7h1lgckxfpldnxs

There are actually 2 related issues:

1. "svn revert" wants to set the write permission (even if there
   are no changes), and if the file was regarded as read-only, a
   confusing "Reverted" message is output.

2. The consequence of 1 is possibly repeated "Reverted" messages
   if the file belongs to a different user.

In my case, the cause was that the concerned files were belonging to
root (this was a mistake). So this was issue 2 (and partially 1).

The upstream bug currently corresponds to issue 2 only.

But I think that issue 1 should also be regarded as a bug, unless
there is a good reason for "svn revert" to set the write permission
(to be discussed upstream). In case the behavior will not change,
the output message would need a clarification.

Let's have a bug title with more details...