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

Bug#958859: marked as done (approx update disabled because it can't be updated securely)

Your message dated Fri, 07 Jun 2024 21:55:13 +0700
with message-id <6c60619028a58bb980f9832833051d94.arnaudr@kali.org>
and subject line 
has caused the Debian Bug report #958859,
regarding approx update disabled because it can't be updated securely
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.)


-- 
958859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958859
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: approx
Version: 5.10-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I was attempting to update as usual using approx

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

My approx repositories all returned errors.

   * What was the outcome of this action?

I had to update my machine directly without approx.

   * What outcome did you expect instead?

To update and upgrade normally using approx.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.3
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages approx depends on:
ii  adduser                      3.118
ii  bzip2                        1.0.6-9.2~deb10u1
ii  curl                         7.64.0-4+deb10u1
ii  init-system-helpers          1.56+nmu1
ii  libc6                        2.28-10
ii  libpcre3                     2:8.39-12
ii  rsyslog [system-log-daemon]  8.1901.0-1
ii  xz-utils                     5.2.4-1

approx recommends no packages.

Versions of packages approx suggests:
pn  libconfig-model-approx-perl  <none>

-- Configuration Files:
/etc/approx/approx.conf changed [not included]

-- debconf information:
  approx/port: 9999

Dear maintaner,

I failed to update normally from approx this morning, I don't know if it is some type of temporary glitch.  Here is a snippet from my 'apt update' command:

  404  Not Found [IP: 192.168.22.22 9999]
Err:13 http://server:9999/security buster/updates Release     
  404  Not Found [IP: 192.168.22.22 9999]
Err:14 http://server:9999/debian buster-updates Release
  404  Not Found [IP: 192.168.22.22 9999]

At the end of the output I got a bit of this:

E: The repository 'http://server:9999/debian buster Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://server:9999/security buster/updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

I'd enabled logging in my /etc/approx/approx.conf so here is a snippet of my daemon.log:

4/25/20 3:06 PM	server	systemd[1]	Started caching proxy server for Debian archive files (192.168.22.22:39730).
4/25/20 3:06 PM	server	approx[4760]	Connection from ::ffff:192.168.22.22 port 39730
4/25/20 3:06 PM	server	approx[4760]	Request: GET /debian/dists/buster/InRelease
4/25/20 3:06 PM	server	approx[4760]	  Host: server:9999
4/25/20 3:06 PM	server	approx[4760]	  Cache-Control: max-age=0
4/25/20 3:06 PM	server	approx[4760]	  Accept: text/*
4/25/20 3:06 PM	server	approx[4760]	  User-Agent: Debian APT-HTTP/1.3 (1.8.2)
4/25/20 3:06 PM	server	approx[4760]	  last modified: Sat, 08 Feb 2020 11:10:51 GMT
4/25/20 3:06 PM	server	approx[4760]	  last verified: Fri, 24 Apr 2020 07:05:35 GMT
4/25/20 3:06 PM	server	approx[4760]	  => cache miss
4/25/20 3:06 PM	server	approx[4760]	open: Permission denied (debian/dists/buster/InRelease.hint)
4/25/20 3:06 PM	server	approx[4760]	http://mirrors.kernel.org/debian//dists/buster/InRelease: download error
4/25/20 3:06 PM	server	approx[4760]	Connection from ::ffff:192.168.22.22 port 39730
4/25/20 3:06 PM	server	approx[4760]	Request: GET /security/dists/buster/updates/InRelease
4/25/20 3:06 PM	server	approx[4760]	  Host: server:9999
4/25/20 3:06 PM	server	approx[4760]	  Cache-Control: max-age=0
4/25/20 3:06 PM	server	approx[4760]	  Accept: text/*
4/25/20 3:06 PM	server	approx[4760]	  User-Agent: Debian APT-HTTP/1.3 (1.8.2)
4/25/20 3:06 PM	server	approx[4760]	  last modified: Tue, 21 Apr 2020 13:44:35 GMT
4/25/20 3:06 PM	server	approx[4760]	  last verified: Fri, 24 Apr 2020 07:05:35 GMT
4/25/20 3:06 PM	server	approx[4760]	  => cache miss
4/25/20 3:06 PM	server	approx[4760]	open: Permission denied (security/dists/buster/updates/InRelease.hint)
4/25/20 3:06 PM	server	approx[4760]	http://security.debian.org/debian-security/dists/buster/updates/InRelease: download error

Hopefully it is a temporary artifact caused by some sort of syncing going on somewhere, has anyone else had a similar issue?

Fealty,

--- End Message ---
--- Begin Message --- 
The approx cache is cleaned weekly via /etc/cron.weekly/approx. It's a simple 'find' command, you can run it manually with a different value for max_age if you need to save space. I'm closing the bug, since it was just a question.

--- End Message ---
Reply to: