root@thinkpad:~# LANG=C apt-get update
[...]
Hit http://ftp.debian.org stable-backports Release
[...]
Reading package lists... Done
W: Conflicting distribution: http://ftp.debian.org stable-backports Release (expected stable-backports but got wheezy-backports)
Exit 0

seems out of sync with

root@thinkpad:~# ftp ftp.debian.org
Connected to ftp.debian.org.
220 ftp.debian.org FTP server
Name (ftp.debian.org:root): ftp
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> dir debian/dists/*-backports
200 EPRT command successful. Consider using EPSV.
150 Here comes the directory listing.
drwxr-sr-x    5 1176     1176         4096 Jun 15 21:01 jessie-backports
lrwxrwxrwx    1 1176     1176           16 May 05  2013 stable-backports -> wheezy-backports
drwxr-sr-x    5 1176     1176         4096 Jun 15 21:01 wheezy-backports
226 Directory send OK.
ftp> bye
221 Goodbye.
root@thinkpad:~#

and I would guess this could be fixed along the line

*** ftp.debian.org/debian/dists/stable-updates/main/binary-i386/Release 2014/06/15 19:01:00     1.1
--- ftp.debian.org/debian/dists/stable-updates/main/binary-i386/Release 2014/06/16 00:32:25
***************
*** 1,4 ****
! Archive: wheezy-updates
  Origin: Debian
  Label: Debian
  Component: main
--- 1,5 ----
! Archive: stable-updates
! Codename: wheezy-updates
  Origin: Debian
  Label: Debian
  Component: main

Hi,

(late, but better late than never…)
reassign to the ftpmasters as the archive is their realm rather
than the realm of apt - apt is just a client using it…

This is reported in #509574 (and merges) as well as #714726.
The warning is caused by the content of the 'usual' release
Release files - see these bugs for details.


I leave this bug open for the other issue you reported:

APT isn't using these files. You can 'force' it to do it by using this
directory as a flat-repository. Not a good idea as this would be
unsigned and all, but well your choice. In terms of apt it might be
equally well to drop these files entirely as unsigned flats work "fine"
without a Release file, too – and it looks even more like a bad idea
this way (which is always good).

I don't know about other (non-)users of these Release files through.


Best regards

David Kalnischkies