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

Bug#626026: marked as done (Please provide an option to disable use of InRelease files, for use with mirrors using older mirroring scripts)

Your message dated Thu, 13 Aug 2015 23:51:19 +0200
with message-id <20150813215119.GA27834@crossbow>
and subject line Re: Please provide an option to disable use of InRelease files, for use with mirrors using older mirroring scripts
has caused the Debian Bug report #626026,
regarding Please provide an option to disable use of InRelease files, for use with mirrors using older mirroring scripts
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.)


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

As documented in many different places, mirrors that haven't yet
switched to newer mirroring scripts
<http://lists.debian.org/debian-mirrors-announce/2011/02/msg00001.html>
will update the InRelease file at the wrong phase of the mirroring
process, causing the mirror to produce "Hash Sum Mismatch" errors for
long periods of time.  Most mirrors don't seem to have switched to new
mirroring scripts yet.  To work around this, please consider providing
an apt option to disable the use of InRelease files, which would allow
the use of such mirrors without experiencing prolonged brokenness every
day during mirroring.

Thanks,
Josh Triplett

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-rc5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apt depends on:
ii  debian-archive-keyring  2010.08.28       GnuPG archive keys of the Debian a
ii  gnupg                   1.4.11-3         GNU privacy guard - a free PGP rep
ii  libc6                   2.13-2           Embedded GNU C Library: Shared lib
ii  libgcc1                 1:4.6.0-6        GCC support library
ii  libstdc++6              4.6.0-6          The GNU Standard C++ Library v3
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc                     <none>       (no description available)
ii  aptitude                    0.6.3-4      terminal-based package manager (te
ii  bzip2                       1.0.5-6      high-quality block-sorting file co
ii  dpkg-dev                    1.16.0.3     Debian package development tools
pn  lzma                        <none>       (no description available)
ii  python-apt                  0.7.100.3+b1 Python interface to libapt-pkg

-- no debconf information

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

On Sat, May 07, 2011 at 08:18:05PM -0700, Josh Triplett wrote:
> As documented in many different places, mirrors that haven't yet
> switched to newer mirroring scripts
> <http://lists.debian.org/debian-mirrors-announce/2011/02/msg00001.html>
> will update the InRelease file at the wrong phase of the mirroring
> process, causing the mirror to produce "Hash Sum Mismatch" errors for
> long periods of time.  Most mirrors don't seem to have switched to new
> mirroring scripts yet.  To work around this, please consider providing
> an apt option to disable the use of InRelease files, which would allow
> the use of such mirrors without experiencing prolonged brokenness every
> day during mirroring.

Back then similar bugreports were closed under the premise that it effects only
unstable and the mirror team requested to not do this as it would be wrong as
this would remove the incentive to update the mirror scripts…
Seems like this bug was missed.

Anyhow, 4 years later we have all accepted the new world order of InRelease and
the code actually changed in a way which makes it even harder to avoid at least
trying InRelease first, so closing as wontfix.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: