Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #209829 > unrolled thread

Output from apt-get update.

Started bypeter@easthope.ca
First post2019-06-12 05:10 +0200
Last post2019-06-12 13:00 +0200
Articles 10 — 6 participants

Back to article view | Back to linux.debian.user

Contents

  Output from apt-get update. peter@easthope.ca - 2019-06-12 05:10 +0200
    Re: Output from apt-get update. Matthew Crews <mailinglists@mattcrews.com> - 2019-06-12 06:10 +0200
      Re: Output from apt-get update. Francisco M Neto <fmneto@fmneto.com.br> - 2019-06-12 13:20 +0200
        Re: Output from apt-get update. peter@easthope.ca - 2019-07-03 03:00 +0200
          Re: Output from apt-get update. Matthew Crews <mailinglists@mattcrews.com> - 2019-07-03 04:30 +0200
          Re: Output from apt-get update. Dan Ritter <dsr@randomstring.org> - 2019-07-03 13:10 +0200
        Correct: Re: Output from apt-get update. peter@easthope.ca - 2019-07-03 04:50 +0200
      Re: Output from apt-get update. peter@easthope.ca - 2019-07-03 00:50 +0200
        Re: Output from apt-get update. Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-03 14:30 +0200
    Re: Output from apt-get update. Andy Smith <andy@strugglers.net> - 2019-06-12 13:00 +0200

#209829 — Output from apt-get update.

Frompeter@easthope.ca
Date2019-06-12 05:10 +0200
SubjectOutput from apt-get update.
Message-ID<y81O9-28E-1@gated-at.bofh.it>
On my workstation, apt-get echoes the locations from which package 
information is retrieved.  No problems evident.
root@dalton:/home/peter# apt-get update
Ign:1 http://137.82.116.42/debian stretch InRelease
Hit:2 http://137.82.116.42/debian stretch-updates InRelease
Hit:3 http://security.debian.org stretch/updates InRelease
Hit:4 http://137.82.116.42/debian stretch-backports InRelease
Hit:5 http://137.82.116.42/debian stretch Release
Reading package lists... Done
root@dalton:/home/peter# 

Another machine gives this output.
root@imager:/home/peter# apt-get update
Get:1 file:/full/path/to/build/packaging/deb ./ InRelease
Ign:1 file:/full/path/to/build/packaging/deb ./ InRelease
Get:2 file:/full/path/to/build/packaging/deb ./ Release
Ign:2 file:/full/path/to/build/packaging/deb ./ Release
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:5 http://137.82.116.42/debian stretch InRelease
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages           
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages           
Hit:7 http://137.82.116.42/debian stretch-updates InRelease        
Hit:8 http://security.debian.org stretch/updates InRelease                     
Hit:9 http://137.82.116.42/debian stretch-backports InRelease                  
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US              
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US              
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en                 
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Hit:10 http://137.82.116.42/debian stretch Release 
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Err:3 file:/full/path/to/build/packaging/deb ./ Packages
  File not found - /full/path/to/build/packaging/deb/./Packages (2: No such file or directory)
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Reading package lists... Done
E: Failed to fetch file:/full/path/to/build/packaging/deb/./Packages  File not found - /full/path/to/build/packaging/deb/./Packages (2: No such file or directory)
E: Some index files failed to download. They have been ignored, or old ones used instead.
root@imager:/home/peter# 

The last two lines, "E: ...", appear to be error messages.  The two 
systems have the same /etc/apt/sources.list.  Any ideas about the 
difficulty in imager?

Thanks,                             ... Peter E.

-- 
Composed and transmitted by software designed to avoid the 
complication and vulnerability of antivirus software.
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [next] | [standalone]

#209830

FromMatthew Crews <mailinglists@mattcrews.com>
Date2019-06-12 06:10 +0200
Message-ID<y82Kd-2Gu-1@gated-at.bofh.it>
In reply to#209829

[Multipart message — attachments visible in raw view] — view raw

On 6/11/19 7:28 PM, peter@easthope.ca wrote:
**SNIP*

What does your "/etc/apt/sources.list" file look like on your two machines?

Its unusual to directly point to an IP address for the Debian repos, as
opposed to point to the domain name.

[toc] | [prev] | [next] | [standalone]

#209838

FromFrancisco M Neto <fmneto@fmneto.com.br>
Date2019-06-12 13:20 +0200
Message-ID<y89sl-6FR-3@gated-at.bofh.it>
In reply to#209830

[Multipart message — attachments visible in raw view] — view raw

On Wed, 2019-06-12 at 06:00 +0200, Matthew Crews wrote:
> On 6/11/19 7:28 PM, peter@easthope.ca wrote:
> **SNIP*
> 
> What does your "/etc/apt/sources.list" file look like on your two
> machines?
> 
> Its unusual to directly point to an IP address for the Debian repos,
> as opposed to point to the domain name.

It's also worth checking if there's anything under
/etc/apt/sources.list.d/

-- 
[]'s,

Francisco M Neto <fmneto@fmneto.com.br>

GPG: 4096R/D692FBF0

[toc] | [prev] | [next] | [standalone]

#210625

Frompeter@easthope.ca
Date2019-07-03 03:00 +0200
Message-ID<yfBMR-7qp-1@gated-at.bofh.it>
In reply to#209838
    From: Francisco M Neto <fmneto@fmneto.com.br>
    Date: Wed, 12 Jun 2019 07:27:28 -0300
> It's also worth checking if there's anything under
> /etc/apt/sources.list.d/

peter@dalton:/etc/apt$ ls /etc/apt/sources.list.d/*
ls: cannot access '/etc/apt/sources.list.d/*': No such file or directory
peter@dalton:/etc/apt$

peter@imager:~$ ls /etc/apt/sources.list.d/*
/etc/apt/sources.list.d/mythtv.list
peter@imager:~$

With any luck, mythtv.list isn't involved in this conundrum.

The mainboard interface appears as eth0.
"ip link show" reports eth0 is up.
"ip addr show" reports an IPv6 address for eth0.  No IPv4 address.

ping to a neighbour reports 
  connect: network is unreachable
  
Is IPv6 the default now?  Shorewall configuration needs updating?

Online documentation still has numerous mentions of ifconfig.
https://wiki.debian.org/NetworkConfiguration is a prime example.

Here and there a remark that ip is the new tool replacing ifconfig and 
etc.  Difficult for a non-expert to decide when to use and old command 
and when a shiney new one.   8~(

Any further ideas?

Thanks,                        ... P.



-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#210626

FromMatthew Crews <mailinglists@mattcrews.com>
Date2019-07-03 04:30 +0200
Message-ID<yfDbY-8sS-1@gated-at.bofh.it>
In reply to#210625

[Multipart message — attachments visible in raw view] — view raw

On 7/2/19 5:18 PM, peter@easthope.ca wrote:
>     From: Francisco M Neto <fmneto@fmneto.com.br>
>     Date: Wed, 12 Jun 2019 07:27:28 -0300
>> It's also worth checking if there's anything under
>> /etc/apt/sources.list.d/
> peter@imager:~$ ls /etc/apt/sources.list.d/*
> /etc/apt/sources.list.d/mythtv.list
> peter@imager:~$
> 
> With any luck, mythtv.list isn't involved in this conundrum.

Something tells me that it is worth a look. What are the contents of
/etc/apt/sources.list.d/mythtv.list ?

-Matt

[toc] | [prev] | [next] | [standalone]

#210640

FromDan Ritter <dsr@randomstring.org>
Date2019-07-03 13:10 +0200
Message-ID<yfLjb-52Z-9@gated-at.bofh.it>
In reply to#210625
peter@easthope.ca wrote: 
> 
> The mainboard interface appears as eth0.
> "ip link show" reports eth0 is up.
> "ip addr show" reports an IPv6 address for eth0.  No IPv4 address.
> 
> ping to a neighbour reports 
>   connect: network is unreachable
>   
> Is IPv6 the default now?  Shorewall configuration needs updating?
> 

On a default Debian install, both IPv4 and IPv6 addresses will
be configured if detected: a DHCP request will be sent to obtain
an IPv4 address, and SLAAC will be used to get an IPv6 address.

It's normal for ip addr show eth0 to give you something like:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP group default qlen 1000
    link/ether fc:ab:14:a9:92:db brd ff:ff:ff:ff:ff:ff
    inet 10.2.0.2/16 brd 10.2.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::feaa:14ff:fea9:92db/64 scope link 
       valid_lft forever preferred_lft forever

which shows both IPv4 and IPv6 addresses assigned to eth0.

-dsr-

[toc] | [prev] | [next] | [standalone]

#210629 — Correct: Re: Output from apt-get update.

Frompeter@easthope.ca
Date2019-07-03 04:50 +0200
SubjectCorrect: Re: Output from apt-get update.
Message-ID<yfDvj-8j-1@gated-at.bofh.it>
In reply to#209838
    From: Francisco M Neto <fmneto@fmneto.com.br>
    Date: Wed, 12 Jun 2019 07:27:28 -0300
> It's also worth checking if there's anything under
> /etc/apt/sources.list.d/

You're right.  If /etc/apt/sources.list.d/mythtv.list is disabled, 
apt-get update doesn't produce obscure complaints.  The complaints 
from apt-get could help by identifying the bad repository.

A D-link card gives a network connection.  The mainboard NIC alone is 
problematic.  ??

So the system working again, more or less.  I'm still wondering about 
IPv4 vs. IPv6 and ip vs. other stuff.

Thanks for the help,                      ... P.


-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#210621

Frompeter@easthope.ca
Date2019-07-03 00:50 +0200
Message-ID<yfzL3-6gE-1@gated-at.bofh.it>
In reply to#209830
    From: Matthew Crews <mailinglists@mattcrews.com>
    Date: Wed, 12 Jun 2019 06:00:26 +0200 (CEST)
> What does your "/etc/apt/sources.list" file look like on your two machines?

Here they are.

# imager:/etc/apt/sources.list
# Security updates
deb     http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free
# mirror.it.ubc.ca = 137.82.116.42
deb     http://137.82.116.42/debian stretch main contrib non-free
deb-src http://137.82.116.42/debian stretch main contrib non-free
# stretch-updates, previously known as 'volatile'
deb     http://137.82.116.42/debian stretch-updates main contrib non-free
deb-src http://137.82.116.42/debian stretch-updates main contrib non-free
# stretch backports
deb     http://137.82.116.42/debian stretch-backports main contrib non-free
deb-src http://137.82.116.42/debian stretch-backports main contrib non-free

# dalton:/etc/apt/sources.list
# Security updates
deb     http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free
# mirror.it.ubc.ca = 137.82.116.42
deb     http://137.82.116.42/debian stretch main contrib non-free
deb-src http://137.82.116.42/debian stretch main contrib non-free
# debian.oregonstate.edu = 140.211.166.134
#deb     http://140.211.166.141/debian jessie main contrib non-free
#deb-src http://140.211.166.141/debian jessie main contrib non-free
# Stable updates
deb     http://137.82.116.42/debian stretch-updates main contrib non-free
deb-src http://137.82.116.42/debian stretch-updates main contrib non-free
# Stable backports
deb     http://137.82.116.42/debian stretch-backports main contrib non-free
deb-src http://137.82.116.42/debian stretch-backports main contrib non-free

As I see, sources.list from the two systems are identical, except for comments.

> Its unusual to directly point to an IP address for the Debian repos, as
> opposed to point to the domain name.

dalton has dnsmasq.  From distant recollection, name resolution failed when 
the system was running and dnsmasq was not.  That motivated direct reference 
to IP addresses.  To the best of my knowledge, an IP address should suffice to 
identify a server or possibly a cluster of them. 

I don't understand the intent or meaning of the hypothetical long path cited 
repeatedly.  Eg.
root@imager:/home/peter# apt-get update
Get:1 file:/full/path/to/build/packaging/deb ./ InRelease
Ign:1 file:/full/path/to/build/packaging/deb ./ InRelease
Get:2 file:/full/path/to/build/packaging/deb ./ Release
Ign:2 file:/full/path/to/build/packaging/deb ./ Release
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
  ...

Whereas dalton just confirms the sources.list
root@dalton:/home/peter# apt-get update
Ign:1 http://137.82.116.42/debian stretch InRelease
Hit:2 http://137.82.116.42/debian stretch-updates InRelease
Hit:3 http://137.82.116.42/debian stretch-backports InRelease
Hit:4 http://137.82.116.42/debian stretch Release
Hit:5 http://security.debian.org stretch/updates InRelease
Reading package lists... Done
root@dalton:/home/peter# 

Any ideas about that?  Incidentally, what is "Ign"?

Thanks,                        ... P.



-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#210648

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-07-03 14:30 +0200
Message-ID<yfMyB-5HZ-3@gated-at.bofh.it>
In reply to#210621
On Tue, Jul 02, 2019 at 03:10:06PM -0700, peter@easthope.ca wrote:
> dalton has dnsmasq.  From distant recollection, name resolution failed when 
> the system was running and dnsmasq was not.  That motivated direct reference 
> to IP addresses.  To the best of my knowledge, an IP address should suffice to 
> identify a server or possibly a cluster of them. 

An entry in /etc/hosts would probably be a better choice.  In the case
of HTTP requests, the hostname needs to be sent inside the request to
identify the correct virtual host.

(Now, maybe that particular mirror isn't on a virtual host, but in
general, most HTTP requests *should* be treated as virtual hosts.  Using a
raw IP address in the URL typically won't get you the right result.)

[toc] | [prev] | [next] | [standalone]

#209837

FromAndy Smith <andy@strugglers.net>
Date2019-06-12 13:00 +0200
Message-ID<y898Z-6kc-1@gated-at.bofh.it>
In reply to#209829
Hi Peter,

On Tue, Jun 11, 2019 at 07:28:12PM -0700, peter@easthope.ca wrote:
> E: Failed to fetch file:/full/path/to/build/packaging/deb/./Packages  File not found - /full/path/to/build/packaging/deb/./Packages (2: No such file or directory)
> E: Some index files failed to download. They have been ignored, or old ones used instead.
> root@imager:/home/peter# 
> 
> The last two lines, "E: ...", appear to be error messages.  The two 
> systems have the same /etc/apt/sources.list.  Any ideas about the 
> difficulty in imager?

The second machine seems to have additional sources. They may be in
a file under /etc/apt/sources.list.d/ rather than in
/etc/apt/sources.list itself.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web