[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#690053: marked as done (Don't try to download Translations files if repository doesn't contain such files)



Your message dated Thu, 11 Oct 2012 14:11:25 +0200
with message-id <CAAZ6_fBoU6DpWLxMbnc-nqHWh246Tri-jDtzsdyrc49cjMpCJA@mail.gmail.com>
and subject line Re: Bug#690053: Don't try to download Translations files if repository doesn't contain such files
has caused the Debian Bug report #690053,
regarding Don't try to download Translations files if repository doesn't contain such files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
690053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690053
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.9.7.5
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm running a private repository. Its error logs are filled with entries like this:

File does not exist: [..]/dists/[..]/i18n

making these files incredibly large (several dozens MB) and unreadable.
It would be nice if apt would honor a flag or even the _non-existence_
of hashsums of Translation-* files in the repository "Release" file and
stop trying to download Translation-* files - note that I'm not speaking
about Acquire::Translations on the users side.

Even security.debian.org doesn't provide Translations and could benefit
from such a behaviour/flag too, decreasing the number of file accesses
and the resulting work load for the server.

Regards, Daniel



- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (850, 'unstable'), (700, 'testing'), (560, 'stable'), (110, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt depends on:
ii  debian-archive-keyring  2012.4
ii  gnupg                   1.4.12-5
ii  libapt-pkg4.12          0.9.7.5
ii  libc6                   2.13-35
ii  libgcc1                 1:4.7.2-3
ii  libstdc++6              4.7.2-3

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc     <none>
ii  aptitude    0.6.8.1-2
ii  dpkg-dev    1.16.8
ii  python-apt  0.8.7
ii  synaptic    0.75.13
ii  xz-utils    5.1.1alpha+20120614-1

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlB0KccACgkQm0bx+wiPa4y4aQCg2EjTRWuY/Y8kKzoiFvtFaIMT
630AoJ9+vDzfZfmPgP71xqpAAHs+5odk
=FFXL
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Hi,

On Tue, Oct 9, 2012 at 3:42 PM, Daniel Leidert <daniel.leidert@wgdd.de> wrote:
> It would be nice if apt would honor a flag or even the _non-existence_
> of hashsums of Translation-* files in the repository "Release" file and
> stop trying to download Translation-* files - note that I'm not speaking
> about Acquire::Translations on the users side.

The problem with Translation-* files is that they weren't previously included
in the Release file, so we have to try even if they are not.

On the other hand, if you have at least one Translation-* file in the Release
file APT will assume that you have included all and checks for availability
with it.

So I am closing this bugreport with the strong suggestion to split long
descriptions out into Translation-en. This will be a win-win: for all
your users with enabled MultiArch and you (and a tiny bit for all users).
Alternatively create an empty Translation-fake file and regenerate your
Release file - no benefit for MultiArchers, but for the rest fine as well.


Best regards

David Kalnischkies

--- End Message ---

Reply to: