Re: Repository Problem

[john doe]

On 8/20/2018 2:54 PM, Greg Wooledge wrote:

On Fri, Aug 17, 2018 at 10:32:39PM +0100, Brian wrote:

On Fri 17 Aug 2018 at 21:49:53 +0200, john doe wrote:


As an aside, you should consider using 'apt' and not 'apt-get'.


Why? What functional difference is there between 'apt-get upgrade' and
'apt-get install' and the apt equivalents?




See below.


I don't agree with john doe's assertion; I'm just answering the literal
question.



Reading Debian wiki 'apt-get' is no longer the recommended way to manage 
pkgs:


https://wiki.debian.org/DebianPackageManagement


"apt upgrade" will install new packages, if necessary, to satisfy the
upgrade dependencies; "apt-get upgrade" will not.  This is quite visible
every time there's a new kernel ABI bump.



This behavior is expected if you read apt(8):

https://manpages.debian.org/stretch/apt/apt.8.en.html

--
John Doe

Re: Repository Problem

[Greg Wooledge]

On Fri, Aug 17, 2018 at 10:32:39PM +0100, Brian wrote:
> On Fri 17 Aug 2018 at 21:49:53 +0200, john doe wrote:
> 
> > As an aside, you should consider using 'apt' and not 'apt-get'.
> 
> Why? What functional difference is there between 'apt-get upgrade' and
> 'apt-get install' and the apt equivalents?

I don't agree with john doe's assertion; I'm just answering the literal
question.

"apt upgrade" will install new packages, if necessary, to satisfy the
upgrade dependencies; "apt-get upgrade" will not.  This is quite visible
every time there's a new kernel ABI bump.

"apt upgrade" or "apt install ..." will remove the *.deb files that
it downloads into /var/cache/apt/archives on this particular run, but
not any pre-existing files there.  "apt-get" will not.

"apt" uses yellow text that is virtually unreadable on a white terminal
background.  "apt-get" does not; it doesn't use ANY colors.

Re: Repository Problem

[Stephen P. Molnar]

On 08/19/2018 08:21 AM, Freek de Kruijf wrote:

Op zaterdag 18 augustus 2018 20:50:34 CEST schreef Stephen P. Molnar:

root@AbNormal:/home/comp# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
2: enp2s0:  mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
  link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.123/24 brd 192.168.1.255 scope global dynamic enp2s0
 valid_lft 86368sec preferred_lft 86368sec
  inet6 2600:1700:4280:3690::33/128 scope global dynamic
 valid_lft 1209566sec preferred_lft 1209566sec
  inet6 2600:1700:4280:3690:f15f:a615:62e3:1b2d/64 scope global
temporary dynamic
 valid_lft 604766sec preferred_lft 85961sec
  inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global
mngtmpaddr noprefixroute dynamic
 valid_lft 1209598sec preferred_lft 1209598sec
  inet6 fe80::beee:7bff:fe5e:8336/64 scope link
 valid_lft forever preferred_lft forever
root@AbNormal:/home/comp#

This means you get an IPv6 address, but using it needs also a proper default
gateway or router address. So what is the output of:

ip -6 r


root@AbNormal:/home/comp# ip -6 r
2600:1700:4280:3690::33 dev enp2s0 proto kernel metric 256  expires 
1209559sec pref medium

2600:1700:4280:3690::/64 dev enp2s0 proto ra metric 100  pref medium
2600:1700:4280:3690::/60 via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto 
ra metric 100  pref medium

fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 100  pref medium
fe80::/64 dev enp2s0 proto kernel metric 256  pref medium
default via fe80::3e04:61ff:feb3:3c20 dev enp2s0 proto static metric 
100  pref medium

root@AbNormal:/home/comp#

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Repository Problem

[Stephen P. Molnar]

On 08/18/2018 11:59 PM, mick crane wrote:

On 2018-08-19 02:37, Cindy-Sue Causey wrote:

On 8/18/18, Stephen P. Molnar  wrote:


On 08/18/2018 01:54 PM, Brian wrote:

What does 'ip a' give you? And 'ping -cwww.debian.org?


   Thanksfot the reply.

root@AbNormal:/home/comp# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0:  mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
 link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
 inet 192.168.1.123/24 brd 192.168.1.255 scope global dynamic 
enp2s0

valid_lft 86368sec preferred_lft 86368sec
 inet6 2600:1700:4280:3690::33/128 scope global dynamic
valid_lft 1209566sec preferred_lft 1209566sec
 inet6 2600:1700:4280:3690:f15f:a615:62e3:1b2d/64 scope global
temporary dynamic
valid_lft 604766sec preferred_lft 85961sec
 inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global
mngtmpaddr noprefixroute dynamic
valid_lft 1209598sec preferred_lft 1209598sec
 inet6 fe80::beee:7bff:fe5e:8336/64 scope link
valid_lft forever preferred_lft forever
root@AbNormal:/home/comp#

root@AbNormal:/home/comp# ping -c www.debian.org

but, without the -c switch:

PING www.debian.org(mirror-isc3.debian.org (2001:4f8:1:c::15)) 56 data
bytes
^C
--- www.debian.org ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11266ms

root@AbNormal:/home/comp#

ping: bad number of packets to transmit. ping -cwww.debian.org
root@AbNormal:/home/comp#



I tried this, too, while lurking along. Received the same "bad number
of packets" *abrupt retort* to "ping -c". I didn't want to
interject/bother anyone here so I searched the Net instead.

Only 175 pages pulled up when that advisement is enclosed in quotation
marks. A slightly wider search with 'ping "bad number of packets"'
only raised it to 360 pages.

That seems curiously small. Does it mean it's something that people
pretty much don't need and/or just don't know they could address
somehow?

Two for two of us here tried it and received that message so that's
why I decided to put this out here. Are we the only two in the World
with this... no, surely not...

And ultimately does it matter enough that it could maybe use some,
e.g. Publicity Team, airtime now that it has come up in a very
informative way?

It's the first time I've ever done the "ping -c", I always just ping
because I never thought about taking it any further than just making
sure I was connected to the Net... to which I am so am off to search
for answers. :)

Cindy :)

I think you are supposed to put a number after -c
man ping

mick

Absolutely, correct.

root@AbNormal:/home/comp# ping -c 4 www.debian.org
PING www.debian.org (128.31.0.62) 56(84) bytes of data.
64 bytes from mirror-csail.debian.org (128.31.0.62): icmp_seq=1 ttl=46 
time=29.2 ms
64 bytes from mirror-csail.debian.org (128.31.0.62): icmp_seq=2 ttl=46 
time=29.1 ms
64 bytes from mirror-csail.debian.org (128.31.0.62): icmp_seq=3 ttl=46 
time=29.0 ms
64 bytes from mirror-csail.debian.org (128.31.0.62): icmp_seq=4 ttl=46 
time=29.2 ms


--- www.debian.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 29.046/29.165/29.266/0.193 ms
root@AbNormal:/home/comp#

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Repository Problem

[Freek de Kruijf]

Op zaterdag 18 augustus 2018 20:50:34 CEST schreef Stephen P. Molnar:
> root@AbNormal:/home/comp# ip a
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
>  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>  inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
>  inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp2s0:  mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
>  link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
>  inet 192.168.1.123/24 brd 192.168.1.255 scope global dynamic enp2s0
> valid_lft 86368sec preferred_lft 86368sec
>  inet6 2600:1700:4280:3690::33/128 scope global dynamic
> valid_lft 1209566sec preferred_lft 1209566sec
>  inet6 2600:1700:4280:3690:f15f:a615:62e3:1b2d/64 scope global
> temporary dynamic
> valid_lft 604766sec preferred_lft 85961sec
>  inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global
> mngtmpaddr noprefixroute dynamic
> valid_lft 1209598sec preferred_lft 1209598sec
>  inet6 fe80::beee:7bff:fe5e:8336/64 scope link
> valid_lft forever preferred_lft forever
> root@AbNormal:/home/comp#

This means you get an IPv6 address, but using it needs also a proper default 
gateway or router address. So what is the output of:

ip -6 r

-- 
fr.gr.

Freek de Kruijf

Re: Repository Problem

[mick crane]

On 2018-08-19 02:37, Cindy-Sue Causey wrote:

On 8/18/18, Stephen P. Molnar  wrote:


On 08/18/2018 01:54 PM, Brian wrote:

What does 'ip a' give you? And 'ping -cwww.debian.org?


   Thanksfot the reply.

root@AbNormal:/home/comp# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0:  mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
 link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
 inet 192.168.1.123/24 brd 192.168.1.255 scope global dynamic 
enp2s0

valid_lft 86368sec preferred_lft 86368sec
 inet6 2600:1700:4280:3690::33/128 scope global dynamic
valid_lft 1209566sec preferred_lft 1209566sec
 inet6 2600:1700:4280:3690:f15f:a615:62e3:1b2d/64 scope global
temporary dynamic
valid_lft 604766sec preferred_lft 85961sec
 inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global
mngtmpaddr noprefixroute dynamic
valid_lft 1209598sec preferred_lft 1209598sec
 inet6 fe80::beee:7bff:fe5e:8336/64 scope link
valid_lft forever preferred_lft forever
root@AbNormal:/home/comp#

root@AbNormal:/home/comp# ping -c www.debian.org

but, without the -c switch:

PING www.debian.org(mirror-isc3.debian.org (2001:4f8:1:c::15)) 56 data
bytes
^C
--- www.debian.org ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11266ms

root@AbNormal:/home/comp#

ping: bad number of packets to transmit.
root@AbNormal:/home/comp#



I tried this, too, while lurking along. Received the same "bad number
of packets" *abrupt retort* to "ping -c". I didn't want to
interject/bother anyone here so I searched the Net instead.

Only 175 pages pulled up when that advisement is enclosed in quotation
marks. A slightly wider search with 'ping "bad number of packets"'
only raised it to 360 pages.

That seems curiously small. Does it mean it's something that people
pretty much don't need and/or just don't know they could address
somehow?

Two for two of us here tried it and received that message so that's
why I decided to put this out here. Are we the only two in the World
with this... no, surely not...

And ultimately does it matter enough that it could maybe use some,
e.g. Publicity Team, airtime now that it has come up in a very
informative way?

It's the first time I've ever done the "ping -c", I always just ping
because I never thought about taking it any further than just making
sure I was connected to the Net... to which I am so am off to search
for answers. :)

Cindy :)

I think you are supposed to put a number after -c
man ping

mick
--
Key ID4BFEBB31

Re: Repository Problem

[Cindy-Sue Causey]

On 8/18/18, Stephen P. Molnar  wrote:
>
> On 08/18/2018 01:54 PM, Brian wrote:
>> What does 'ip a' give you? And 'ping -cwww.debian.org?
>>
>Thanksfot the reply.
>
> root@AbNormal:/home/comp# ip a
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
>  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>  inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
>  inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp2s0:  mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
>  link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
>  inet 192.168.1.123/24 brd 192.168.1.255 scope global dynamic enp2s0
> valid_lft 86368sec preferred_lft 86368sec
>  inet6 2600:1700:4280:3690::33/128 scope global dynamic
> valid_lft 1209566sec preferred_lft 1209566sec
>  inet6 2600:1700:4280:3690:f15f:a615:62e3:1b2d/64 scope global
> temporary dynamic
> valid_lft 604766sec preferred_lft 85961sec
>  inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global
> mngtmpaddr noprefixroute dynamic
> valid_lft 1209598sec preferred_lft 1209598sec
>  inet6 fe80::beee:7bff:fe5e:8336/64 scope link
> valid_lft forever preferred_lft forever
> root@AbNormal:/home/comp#
>
> root@AbNormal:/home/comp# ping -c www.debian.org
>
> but, without the -c switch:
>
> PING www.debian.org(mirror-isc3.debian.org (2001:4f8:1:c::15)) 56 data
> bytes
> ^C
> --- www.debian.org ping statistics ---
> 12 packets transmitted, 0 received, 100% packet loss, time 11266ms
>
> root@AbNormal:/home/comp#
>
> ping: bad number of packets to transmit.
> root@AbNormal:/home/comp#


I tried this, too, while lurking along. Received the same "bad number
of packets" *abrupt retort* to "ping -c". I didn't want to
interject/bother anyone here so I searched the Net instead.

Only 175 pages pulled up when that advisement is enclosed in quotation
marks. A slightly wider search with 'ping "bad number of packets"'
only raised it to 360 pages.

That seems curiously small. Does it mean it's something that people
pretty much don't need and/or just don't know they could address
somehow?

Two for two of us here tried it and received that message so that's
why I decided to put this out here. Are we the only two in the World
with this... no, surely not...

And ultimately does it matter enough that it could maybe use some,
e.g. Publicity Team, airtime now that it has come up in a very
informative way?

It's the first time I've ever done the "ping -c", I always just ping
because I never thought about taking it any further than just making
sure I was connected to the Net... to which I am so am off to search
for answers. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Repository Problem

[Reco]

Hi.

On Sat, Aug 18, 2018 at 01:46:31PM -0400, Stephen P. Molnar wrote:
> 
> 
> On 08/18/2018 11:51 AM, Reco wrote:
> > Hi.
> > 
> > On Sat, Aug 18, 2018 at 11:13:04AM -0400, Stephen P. Molnar wrote:
> > > 
> > > On 08/18/2018 10:20 AM, Dan Ritter wrote:
> > > > On Sat, Aug 18, 2018 at 08:15:12PM +1000, David wrote:
> > > > > On 18 August 2018 at 05:00, Stephen P. Molnar 
> > > > >  wrote:
> > > > > > I have just installed Stretch on a new SSD on my platform.
> > > > > > 
> > > > > > During the installation I selected the University of Chicago mirror 
> > > > > > and
> > > > > > accepted the defaults plus backports.
> > > > > > 
> > > > > > When I fun apt-get install Thunderbird apt-get tries to log on to
> > > > > > prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't 
> > > > > > find that
> > > > > > address anywhere in /etc/apt.  Why am I getting this behavior?
> > > > > As explained at [1], the debian-security repo [2] might be provided to
> > > > > you by fastly.net.
> > > > > 
> > > > > Access to the debian-security repo is important because it is the 
> > > > > method
> > > > > by which your system will receive future security updates.
> > > > > 
> > > > > > Even more
> > > > > > important, how do I get rid of  the problem?
> > > > > If by "the problem" you mean the "hang", then you need to investigate 
> > > > > why
> > > > > that is occurring.
> > > > Two cents says that he doesn't have upstream IPv6 connectivity.
> > > > 
> > > > If ping6 fails for both prod.debian.map.fastly.net and
> > > > www.google.com, that's a decent indicator I'm right.
> > > > 
> > > > Then the question is whether he expects to have IPv6
> > > > connectivity (and so it's broken) or whether he doesn't (and we
> > > > should tell Debian to stop using it).
> > > > 
> > > Thank for the reply.
> > > 
> > > Where can I send the two cents?  It looks as if that's correct.
> > > 
> > > The installer installed ipv6 without giving me any choice about the 
> > > matter.
> > Don't blame the installer for that. The way IPv6 is provided there's
> > nothing to configure on your host (and there's nothing to blame here 
> > either).
> > You network hardware (aka router), on the other hand, most surely
> > advertizes IPv6 prefix. So put the blame there or on your ISP.
> > 
> > > How do I get rid of ipv6 and replace it WITH ipv4?
> > 1) Delicate way of doing it (apply after each boot):
> > 
> > ip6tables -I INPUT ! -o lo -p icmp6 --icmpv6-type 134 -j DROP
> > 
> > 2) Hardcore way of doing it (ditto):
> > 
> > sysctl -qw net.ipv6.conf.all.disable_ipv6=1
> > 
> > 3) Right way of doing things:
> > 
> > Fix your router.
> > 
> > Reco
> > 
> > 
> 
> According to my AT BGW210 Router both ipv4 amd 1pv6 are active

And AT is known to have strange views on IPv6 (works for some, broken
for most).
Unless IPv6 is something that you just cannot live with - disable IPv6
advertizing on a router.

I.e. - locate a page looking like [1] and set Off all three knobs.

Reco

[1] http://setuprouter.com/router/arris/bgw210-700-att/ipv6-86430-large.htm

Re: Repository Problem

[Stephen P. Molnar]

On 08/18/2018 01:54 PM, Brian wrote:

On Sat 18 Aug 2018 at 13:46:31 -0400, Stephen P. Molnar wrote:


On 08/18/2018 11:51 AM, Reco wrote:

Hi.

On Sat, Aug 18, 2018 at 11:13:04AM -0400, Stephen P. Molnar wrote:

On 08/18/2018 10:20 AM, Dan Ritter wrote:

On Sat, Aug 18, 2018 at 08:15:12PM +1000, David wrote:

On 18 August 2018 at 05:00, Stephen P. Molnar  wrote:

I have just installed Stretch on a new SSD on my platform.

During the installation I selected the University of Chicago mirror and
accepted the defaults plus backports.

When I fun apt-get install Thunderbird apt-get tries to log on to
prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
address anywhere in /etc/apt.  Why am I getting this behavior?

As explained at [1], the debian-security repo [2] might be provided to
you by fastly.net.

Access to the debian-security repo is important because it is the method
by which your system will receive future security updates.


Even more
important, how do I get rid of  the problem?

If by "the problem" you mean the "hang", then you need to investigate why
that is occurring.

Two cents says that he doesn't have upstream IPv6 connectivity.

If ping6 fails for both prod.debian.map.fastly.net and
www.google.com, that's a decent indicator I'm right.

Then the question is whether he expects to have IPv6
connectivity (and so it's broken) or whether he doesn't (and we
should tell Debian to stop using it).


Thank for the reply.

Where can I send the two cents?  It looks as if that's correct.

The installer installed ipv6 without giving me any choice about the matter.

Don't blame the installer for that. The way IPv6 is provided there's
nothing to configure on your host (and there's nothing to blame here either).
You network hardware (aka router), on the other hand, most surely
advertizes IPv6 prefix. So put the blame there or on your ISP.


How do I get rid of ipv6 and replace it WITH ipv4?

1) Delicate way of doing it (apply after each boot):

ip6tables -I INPUT ! -o lo -p icmp6 --icmpv6-type 134 -j DROP

2) Hardcore way of doing it (ditto):

sysctl -qw net.ipv6.conf.all.disable_ipv6=1

3) Right way of doing things:

Fix your router.

Reco



According to my AT BGW210 Router both ipv4 amd 1pv6 are active

What does 'ip a' give you? And 'ping -cwww.debian.org?


  Thanksfot the reply.

root@AbNormal:/home/comp# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp2s0:  mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000

link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.123/24 brd 192.168.1.255 scope global dynamic enp2s0
   valid_lft 86368sec preferred_lft 86368sec
inet6 2600:1700:4280:3690::33/128 scope global dynamic
   valid_lft 1209566sec preferred_lft 1209566sec
inet6 2600:1700:4280:3690:f15f:a615:62e3:1b2d/64 scope global 
temporary dynamic

   valid_lft 604766sec preferred_lft 85961sec
inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global 
mngtmpaddr noprefixroute dynamic

   valid_lft 1209598sec preferred_lft 1209598sec
inet6 fe80::beee:7bff:fe5e:8336/64 scope link
   valid_lft forever preferred_lft forever
root@AbNormal:/home/comp#


root@AbNormal:/home/comp# ping -c www.debian.org

but, without the -c switch:

PING www.debian.org(mirror-isc3.debian.org (2001:4f8:1:c::15)) 56 data bytes
^C
--- www.debian.org ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 11266ms

root@AbNormal:/home/comp#

ping: bad number of packets to transmit.
root@AbNormal:/home/comp#

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Repository Problem

[Curt]

On 2018-08-18, Stephen P. Molnar  wrote:
>>
>> Fix your router.
>>
>> Reco
>>
>>
>
> According to my AT BGW210 Router both ipv4 amd 1pv6 are active
>


Maybe you could try  '-o Acquire::ForceIPv4=true' when running apt-get.

I mean, I would try that in the spirit of the groping around in the dark
troubleshooting techniques to which I am constrained by my irremediable
ignorance.

-- 
"She was a blank wall, fresh painted." 
Louise Erdrich, Love Medicine

Re: Repository Problem

[Brian]

On Sat 18 Aug 2018 at 13:46:31 -0400, Stephen P. Molnar wrote:

> 
> 
> On 08/18/2018 11:51 AM, Reco wrote:
> > Hi.
> > 
> > On Sat, Aug 18, 2018 at 11:13:04AM -0400, Stephen P. Molnar wrote:
> > > 
> > > On 08/18/2018 10:20 AM, Dan Ritter wrote:
> > > > On Sat, Aug 18, 2018 at 08:15:12PM +1000, David wrote:
> > > > > On 18 August 2018 at 05:00, Stephen P. Molnar 
> > > > >  wrote:
> > > > > > I have just installed Stretch on a new SSD on my platform.
> > > > > > 
> > > > > > During the installation I selected the University of Chicago mirror 
> > > > > > and
> > > > > > accepted the defaults plus backports.
> > > > > > 
> > > > > > When I fun apt-get install Thunderbird apt-get tries to log on to
> > > > > > prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't 
> > > > > > find that
> > > > > > address anywhere in /etc/apt.  Why am I getting this behavior?
> > > > > As explained at [1], the debian-security repo [2] might be provided to
> > > > > you by fastly.net.
> > > > > 
> > > > > Access to the debian-security repo is important because it is the 
> > > > > method
> > > > > by which your system will receive future security updates.
> > > > > 
> > > > > > Even more
> > > > > > important, how do I get rid of  the problem?
> > > > > If by "the problem" you mean the "hang", then you need to investigate 
> > > > > why
> > > > > that is occurring.
> > > > Two cents says that he doesn't have upstream IPv6 connectivity.
> > > > 
> > > > If ping6 fails for both prod.debian.map.fastly.net and
> > > > www.google.com, that's a decent indicator I'm right.
> > > > 
> > > > Then the question is whether he expects to have IPv6
> > > > connectivity (and so it's broken) or whether he doesn't (and we
> > > > should tell Debian to stop using it).
> > > > 
> > > Thank for the reply.
> > > 
> > > Where can I send the two cents?  It looks as if that's correct.
> > > 
> > > The installer installed ipv6 without giving me any choice about the 
> > > matter.
> > Don't blame the installer for that. The way IPv6 is provided there's
> > nothing to configure on your host (and there's nothing to blame here 
> > either).
> > You network hardware (aka router), on the other hand, most surely
> > advertizes IPv6 prefix. So put the blame there or on your ISP.
> > 
> > > How do I get rid of ipv6 and replace it WITH ipv4?
> > 1) Delicate way of doing it (apply after each boot):
> > 
> > ip6tables -I INPUT ! -o lo -p icmp6 --icmpv6-type 134 -j DROP
> > 
> > 2) Hardcore way of doing it (ditto):
> > 
> > sysctl -qw net.ipv6.conf.all.disable_ipv6=1
> > 
> > 3) Right way of doing things:
> > 
> > Fix your router.
> > 
> > Reco
> > 
> > 
> 
> According to my AT BGW210 Router both ipv4 amd 1pv6 are active

What does 'ip a' give you? And 'ping -c www.debian.org?

-- 
Brian.

Re: Repository Problem

[Stephen P. Molnar]

On 08/18/2018 11:51 AM, Reco wrote:

Hi.

On Sat, Aug 18, 2018 at 11:13:04AM -0400, Stephen P. Molnar wrote:


On 08/18/2018 10:20 AM, Dan Ritter wrote:

On Sat, Aug 18, 2018 at 08:15:12PM +1000, David wrote:

On 18 August 2018 at 05:00, Stephen P. Molnar  wrote:

I have just installed Stretch on a new SSD on my platform.

During the installation I selected the University of Chicago mirror and
accepted the defaults plus backports.

When I fun apt-get install Thunderbird apt-get tries to log on to
prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
address anywhere in /etc/apt.  Why am I getting this behavior?

As explained at [1], the debian-security repo [2] might be provided to
you by fastly.net.

Access to the debian-security repo is important because it is the method
by which your system will receive future security updates.


Even more
important, how do I get rid of  the problem?

If by "the problem" you mean the "hang", then you need to investigate why
that is occurring.

Two cents says that he doesn't have upstream IPv6 connectivity.

If ping6 fails for both prod.debian.map.fastly.net and
www.google.com, that's a decent indicator I'm right.

Then the question is whether he expects to have IPv6
connectivity (and so it's broken) or whether he doesn't (and we
should tell Debian to stop using it).


Thank for the reply.

Where can I send the two cents?  It looks as if that's correct.

The installer installed ipv6 without giving me any choice about the matter.

Don't blame the installer for that. The way IPv6 is provided there's
nothing to configure on your host (and there's nothing to blame here either).
You network hardware (aka router), on the other hand, most surely
advertizes IPv6 prefix. So put the blame there or on your ISP.


How do I get rid of ipv6 and replace it WITH ipv4?

1) Delicate way of doing it (apply after each boot):

ip6tables -I INPUT ! -o lo -p icmp6 --icmpv6-type 134 -j DROP

2) Hardcore way of doing it (ditto):

sysctl -qw net.ipv6.conf.all.disable_ipv6=1

3) Right way of doing things:

Fix your router.

Reco




According to my AT BGW210 Router both ipv4 amd 1pv6 are active

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Repository Problem

[Reco]

Hi.

On Sat, Aug 18, 2018 at 11:13:04AM -0400, Stephen P. Molnar wrote:
> 
> 
> On 08/18/2018 10:20 AM, Dan Ritter wrote:
> > On Sat, Aug 18, 2018 at 08:15:12PM +1000, David wrote:
> > > On 18 August 2018 at 05:00, Stephen P. Molnar  
> > > wrote:
> > > > I have just installed Stretch on a new SSD on my platform.
> > > > 
> > > > During the installation I selected the University of Chicago mirror and
> > > > accepted the defaults plus backports.
> > > > 
> > > > When I fun apt-get install Thunderbird apt-get tries to log on to
> > > > prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find 
> > > > that
> > > > address anywhere in /etc/apt.  Why am I getting this behavior?
> > > As explained at [1], the debian-security repo [2] might be provided to
> > > you by fastly.net.
> > > 
> > > Access to the debian-security repo is important because it is the method
> > > by which your system will receive future security updates.
> > > 
> > > > Even more
> > > > important, how do I get rid of  the problem?
> > > If by "the problem" you mean the "hang", then you need to investigate why
> > > that is occurring.
> > Two cents says that he doesn't have upstream IPv6 connectivity.
> > 
> > If ping6 fails for both prod.debian.map.fastly.net and
> > www.google.com, that's a decent indicator I'm right.
> > 
> > Then the question is whether he expects to have IPv6
> > connectivity (and so it's broken) or whether he doesn't (and we
> > should tell Debian to stop using it).
> > 
> Thank for the reply.
> 
> Where can I send the two cents?  It looks as if that's correct.
> 
> The installer installed ipv6 without giving me any choice about the matter.

Don't blame the installer for that. The way IPv6 is provided there's
nothing to configure on your host (and there's nothing to blame here either).
You network hardware (aka router), on the other hand, most surely
advertizes IPv6 prefix. So put the blame there or on your ISP.

> How do I get rid of ipv9 and replace it WITH ipv4?

1) Delicate way of doing it (apply after each boot):

ip6tables -I INPUT ! -o lo -p icmp6 --icmpv6-type 134 -j DROP

2) Hardcore way of doing it (ditto):

sysctl -qw net.ipv6.conf.all.disable_ipv6=1

3) Right way of doing things:

Fix your router.

Reco

Re: Repository Problem

[Stephen P. Molnar]

On 08/18/2018 10:20 AM, Dan Ritter wrote:

On Sat, Aug 18, 2018 at 08:15:12PM +1000, David wrote:

On 18 August 2018 at 05:00, Stephen P. Molnar  wrote:

I have just installed Stretch on a new SSD on my platform.

During the installation I selected the University of Chicago mirror and
accepted the defaults plus backports.

When I fun apt-get install Thunderbird apt-get tries to log on to
prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
address anywhere in /etc/apt.  Why am I getting this behavior?

As explained at [1], the debian-security repo [2] might be provided to
you by fastly.net.

Access to the debian-security repo is important because it is the method
by which your system will receive future security updates.


Even more
important, how do I get rid of  the problem?

If by "the problem" you mean the "hang", then you need to investigate why
that is occurring.

Two cents says that he doesn't have upstream IPv6 connectivity.

If ping6 fails for both prod.debian.map.fastly.net and
www.google.com, that's a decent indicator I'm right.

Then the question is whether he expects to have IPv6
connectivity (and so it's broken) or whether he doesn't (and we
should tell Debian to stop using it).

-dsr-



Thank for the reply.

Where can I send the two cents?  It looks as if that's correct.

The installer installed ipv6 without giving me any choice about the 
matter.  How do I get rid of ipv9 and replace it WITH ipv4?


--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Repository Problem

[Dan Ritter]

On Sat, Aug 18, 2018 at 08:15:12PM +1000, David wrote:
> On 18 August 2018 at 05:00, Stephen P. Molnar  wrote:
> > I have just installed Stretch on a new SSD on my platform.
> >
> > During the installation I selected the University of Chicago mirror and
> > accepted the defaults plus backports.
> >
> > When I fun apt-get install Thunderbird apt-get tries to log on to
> > prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
> > address anywhere in /etc/apt.  Why am I getting this behavior?
> 
> As explained at [1], the debian-security repo [2] might be provided to
> you by fastly.net.
> 
> Access to the debian-security repo is important because it is the method
> by which your system will receive future security updates.
> 
> > Even more
> > important, how do I get rid of  the problem?
> 
> If by "the problem" you mean the "hang", then you need to investigate why
> that is occurring.

Two cents says that he doesn't have upstream IPv6 connectivity.

If ping6 fails for both prod.debian.map.fastly.net and
www.google.com, that's a decent indicator I'm right.

Then the question is whether he expects to have IPv6
connectivity (and so it's broken) or whether he doesn't (and we
should tell Debian to stop using it).

-dsr-

Re: Repository Problem

[David]

On 18 August 2018 at 05:00, Stephen P. Molnar  wrote:
> I have just installed Stretch on a new SSD on my platform.
>
> During the installation I selected the University of Chicago mirror and
> accepted the defaults plus backports.
>
> When I fun apt-get install Thunderbird apt-get tries to log on to
> prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
> address anywhere in /etc/apt.  Why am I getting this behavior?

As explained at [1], the debian-security repo [2] might be provided to
you by fastly.net.

Access to the debian-security repo is important because it is the method
by which your system will receive future security updates.

> Even more
> important, how do I get rid of  the problem?

If by "the problem" you mean the "hang", then you need to investigate why
that is occurring.

[1] https://deb.debian.org/
[2] specified in your /etc/apt/sources.list file as
http://security.debian.org/debian-security/

Re: Repository Problem

[Brian]

On Fri 17 Aug 2018 at 21:49:53 +0200, john doe wrote:

> As an aside, you should consider using 'apt' and not 'apt-get'.

Why? What functional difference is there between 'apt-get upgrade' and
'apt-get install' and the apt equivalents?

-- 
Brian.

Re: Repository Problem

[Stephen P. Molnar]

Thanks for he reply.

Nothing there.

On 08/17/2018 04:03 PM, Roberto C. S�nchez wrote:

On Fri, Aug 17, 2018 at 08:21:50PM +0100, Brian wrote:

On Fri 17 Aug 2018 at 15:00:09 -0400, Stephen P. Molnar wrote:


I have just installed Stretch on a new SSD on my platform.

During the installation I selected the University of Chicago mirror and
accepted the defaults plus backports.

When I fun apt-get install Thunderbird apt-get tries to log on to
prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
address anywhere in /etc/apt.  Why am I getting this behavior? Even more
important, how do I get rid of  the problem?

It is critical as my wife uses Thunderbird for her email.

Any assistance will be greatly appreciated.

Post your /etc/apt/sources.list


Do you have any files in /etc/apt/sources.list.d/?  If so, post the
contents of those as well.

Regards,

-Roberto



--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Repository Problem

[Roberto C . Sánchez]

On Fri, Aug 17, 2018 at 08:21:50PM +0100, Brian wrote:
> On Fri 17 Aug 2018 at 15:00:09 -0400, Stephen P. Molnar wrote:
> 
> > I have just installed Stretch on a new SSD on my platform.
> > 
> > During the installation I selected the University of Chicago mirror and
> > accepted the defaults plus backports.
> > 
> > When I fun apt-get install Thunderbird apt-get tries to log on to
> > prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
> > address anywhere in /etc/apt.  Why am I getting this behavior? Even more
> > important, how do I get rid of  the problem?
> > 
> > It is critical as my wife uses Thunderbird for her email.
> > 
> > Any assistance will be greatly appreciated.
> 
> Post your /etc/apt/sources.list
> 
Do you have any files in /etc/apt/sources.list.d/?  If so, post the
contents of those as well.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Repository Problem

[Brian]

On Fri 17 Aug 2018 at 15:35:08 -0400, Stephen P. Molnar wrote:

> Thanks for the reply.
> 
> Please see attachemnt.
> 
> On 08/17/2018 03:21 PM, Brian wrote:
> > On Fri 17 Aug 2018 at 15:00:09 -0400, Stephen P. Molnar wrote:
> > 
> > > I have just installed Stretch on a new SSD on my platform.
> > > 
> > > During the installation I selected the University of Chicago mirror and
> > > accepted the defaults plus backports.
> > > 
> > > When I fun apt-get install Thunderbird apt-get tries to log on to
> > > prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find 
> > > that
> > > address anywhere in /etc/apt.  Why am I getting this behavior? Even more
> > > important, how do I get rid of  the problem?
> > > 
> > > It is critical as my wife uses Thunderbird for her email.
> > > 
> > > Any assistance will be greatly appreciated.
> > Post your /etc/apt/sources.list

Comment everything out and put

deb http://deb.debian.org/debian/ stretch main non-free contrib

Go from there.

-- 
Brian.

Re: Repository Problem

[john doe]

On 8/17/2018 9:00 PM, Stephen P. Molnar wrote:

I have just installed Stretch on a new SSD on my platform.

During the installation I selected the University of Chicago mirror and 
accepted the defaults plus backports.


When I fun apt-get install Thunderbird apt-get tries to log on to 
prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find 
that address anywhere in /etc/apt.  Why am I getting this behavior? Even 
more important, how do I get rid of  the problem?


It is critical as my wife uses Thunderbird for her email.

Any assistance will be greatly appreciated.



Here is my '/etc/apt/sources.list' (default after installation):

deb http://ftp.us.debian.org/debian/ stretch main non-free contrib
deb-src http://ftp.us.debian.org/debian/ stretch main non-free contrib

deb http://security.debian.org/debian-security stretch/updates main 
contrib non-free
deb-src http://security.debian.org/debian-security stretch/updates main 
contrib non-free


# stretch-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ stretch-updates main contrib 
non-free


# stretch-backports, previously on backports.debian.org
deb http://ftp.us.debian.org/debian/ stretch-backports main contrib non-free
deb-src http://ftp.us.debian.org/debian/ stretch-backports main contrib 
non-free


As an aside, you should consider using 'apt' and not 'apt-get'.

Note that this e-mail is folded by my mailer.

--
John Doe

Re: Repository Problem

[Stephen P. Molnar]

Thanks for the reply.

Please see attachemnt.

On 08/17/2018 03:21 PM, Brian wrote:

On Fri 17 Aug 2018 at 15:00:09 -0400, Stephen P. Molnar wrote:


I have just installed Stretch on a new SSD on my platform.

During the installation I selected the University of Chicago mirror and
accepted the defaults plus backports.

When I fun apt-get install Thunderbird apt-get tries to log on to
prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
address anywhere in /etc/apt.  Why am I getting this behavior? Even more
important, how do I get rid of  the problem?

It is critical as my wife uses Thunderbird for her email.

Any assistance will be greatly appreciated.

Post your /etc/apt/sources.list





# deb cdrom:[Debian GNU/Linux 9.5.0 _Stretch_ - Official amd64 DVD Binary-1 
20180714-10:25]/ stretch contrib main 

# deb cdrom:[Debian GNU/Linux 9.5.0 _Stretch_ - Official amd64 DVD Binary-1 
20180714-10:25]/ stretch main contrib  

deb http://debian.uchicago.edu/debian/ stretch main non-free contrib 
deb-src http://debian.uchicago.edu/debian/ stretch main non-free contrib 

deb http://security.debian.org/debian-security/ stretch/updates main contrib 
non-free 
deb-src http://security.debian.org/debian-security/ stretch/updates main 
contrib non-free 

# stretch-updates, previously known as 'volatile'
deb http://debian.uchicago.edu/debian/ stretch-updates main contrib non-free 
deb-src http://debian.uchicago.edu/debian/ stretch-updates main contrib 
non-free 

# stretch-backports, previously on backports.debian.org
deb http://debian.uchicago.edu/debian/ stretch-backports main contrib non-free 
deb-src http://debian.uchicago.edu/debian/ stretch-backports main contrib 
non-free 

Re: Repository Problem

[Brian]

On Fri 17 Aug 2018 at 15:00:09 -0400, Stephen P. Molnar wrote:

> I have just installed Stretch on a new SSD on my platform.
> 
> During the installation I selected the University of Chicago mirror and
> accepted the defaults plus backports.
> 
> When I fun apt-get install Thunderbird apt-get tries to log on to
> prod.debian.map.fastly.net (2a04:4E42:2c::2040 and hangs. I can't find that
> address anywhere in /etc/apt.  Why am I getting this behavior? Even more
> important, how do I get rid of  the problem?
> 
> It is critical as my wife uses Thunderbird for her email.
> 
> Any assistance will be greatly appreciated.

Post your /etc/apt/sources.list

-- 
Brian.

Re: Repository problem

[J Mo]

I was having some similar problems the other day. It cleared up after 
awhile.




On 05/21/2016 12:00 AM, Hans wrote:

Dear debian-team,

I suppose there is a problem with one of your repos. Please take a look:

  LANG=C aptitude update
.
..
Hit ftp://ftp.de.debian.org/debian stable Release
Get: 2 ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata [1657
kB]
Err ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata
   Hash Sum mismatch
Err ftp://ftp.de.debian.org/debian testing/main DEP-11 64x64 Icons
Fetched 1425 kB in 5s (239 kB/s)
W: Failed to fetch
ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/Components-amd64.yml.xz:
 Hash Sum mismatch
W: Failed to fetch
ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/icons-64x64.tar.gz:
E: Some index files failed to download. They have been ignored, or old ones
used instead.

.


Aptitude is telling me, that the indexfile of 64x64 Icons shall 20,2 TB(!!!)
big, which might cause other problems, too.

You might want to take a look at it.

Happy weekend

Hans

Re: Repository problem

[Hans]

Am Samstag, 21. Mai 2016, 09:00:03 schrieben Sie:
> Dear debian-team,
> 
> I suppose there is a problem with one of your repos. Please take a look:
> 
>  LANG=C aptitude update
> .
> ..
> Hit ftp://ftp.de.debian.org/debian stable Release
> Get: 2 ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata
> [1657 kB]
> Err ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata
>   Hash Sum mismatch
> Err ftp://ftp.de.debian.org/debian testing/main DEP-11 64x64 Icons
> Fetched 1425 kB in 5s (239 kB/s)
Hi all, 

it is fixed now.

Thank you for this fast action!

Best

Hans

> W: Failed to fetch
> ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/Components-amd64.yml
> .xz: Hash Sum mismatch W: Failed to fetch
> ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/icons-64x64.tar.gz:
> E: Some index files failed to download. They have been ignored, or old ones
> used instead.
> 
> .
> 
> 
> Aptitude is telling me, that the indexfile of 64x64 Icons shall 20,2 TB(!!!)
> big, which might cause other problems, too.
> 
> You might want to take a look at it.
> 
> Happy weekend
> 
> Hans

Re: Repository problem

[Lisi Reisz]

On Saturday 21 May 2016 08:00:03 Hans wrote:
> Dear debian-team,
>
> I suppose there is a problem with one of your repos.

Probably just that mirror.  Try a different mirror.

Lisi

> Please take a look: 

>
>  LANG=C aptitude update
> .
> ..
> Hit ftp://ftp.de.debian.org/debian stable Release
> Get: 2 ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata
> [1657 kB]
> Err ftp://ftp.de.debian.org/debian testing/main amd64 DEP-11 Metadata
>   Hash Sum mismatch
> Err ftp://ftp.de.debian.org/debian testing/main DEP-11 64x64 Icons
> Fetched 1425 kB in 5s (239 kB/s)
> W: Failed to fetch
> ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/Components-amd64.ym
>l.xz: Hash Sum mismatch W: Failed to fetch
> ftp://ftp.de.debian.org/debian/dists/testing/main/dep11/icons-64x64.tar.gz:
> E: Some index files failed to download. They have been ignored, or old ones
> used instead.
> 
> .
>
>
> Aptitude is telling me, that the indexfile of 64x64 Icons shall 20,2
> TB(!!!) big, which might cause other problems, too.
>
> You might want to take a look at it.
>
> Happy weekend
>
> Hans

Re: Repository Problem

[Stephen P. Molnar]

On 04/16/2016 06:15 PM, Jeremy Nicoll wrote:

On Sat, 16 Apr 2016, at 22:42, Stephen P. Molnar wrote:

On 04/16/2016 10:12 AM, Sven Hartge wrote:

All of his sources.list lines are using http://http.us.debian.org.
The issue is that
http://http.us.debian.org/debian/dists/wheezy/updates does not exist.
A casual look with a browser reveals this.

Exactly.

S°


Just how doers this contribute to a solution of the problem?

Because it's an easy way for you to have seen that the URLs you defined
for
Debian to use must have been wrong.  Didn't someone further up this
thread
point out a very subtle difference between the URLs you were using and
the
ones you should have been using?  I have a feeling you didn't get the
subtlety.

OTOH if those wrong URLs were installed by Debian itself, I agree that
that is
a problem in itself.


Then it is a problem, as I did nothing to edit the sources.list entries.

--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.Molecular-Modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Shyoe:  smolnar1

Re: Repository Problem

[Jeremy Nicoll]

On Sat, 16 Apr 2016, at 22:42, Stephen P. Molnar wrote:
> 
> On 04/16/2016 10:12 AM, Sven Hartge wrote:

> >> All of his sources.list lines are using http://http.us.debian.org.
> >> The issue is that
> >> http://http.us.debian.org/debian/dists/wheezy/updates does not exist.
> >> A casual look with a browser reveals this.
> > Exactly.
> >
> > S°
> >
> Just how doers this contribute to a solution of the problem?

Because it's an easy way for you to have seen that the URLs you defined
for
Debian to use must have been wrong.  Didn't someone further up this
thread
point out a very subtle difference between the URLs you were using and
the
ones you should have been using?  I have a feeling you didn't get the
subtlety.

OTOH if those wrong URLs were installed by Debian itself, I agree that
that is
a problem in itself.

-- 
Jeremy Nicoll - my opinions are my own.

Re: Repository Problem

[Stephen P. Molnar]

On 04/16/2016 10:12 AM, Sven Hartge wrote:

Michael Milliman  wrote:

On 04/15/2016 03:18 PM, Sven Hartge wrote:

Dan Ritter  wrote:

On Fri, Apr 15, 2016 at 01:06:18PM -0400, Stephen P. Molnar wrote:

I just had a catastrophic crash which necessitated reinstalling
Debian.  I had been running v-7.2,but decided to upgrade to v-7.10
with a complete install.

Now when I update the repositories, regardless of the tool, Synaptic
or Aptitude, I get the following errors:

W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 404  
Not Found [IP: 2610:148:1f10:3::89 80]
I do not get these errors if I comment out the deb-src lines in the
sources.list.

Those are IPv6 addresses. I would guess that you don't have an
IPv6 connection available to you, or it's misconfigured.

He then would get a timeout or host unreachable and not a 404 HTTP error
code.

What it looks like is this: he has URLs for the sources of security
updates (wheezy/updates) configured for the wrong host, because
debian.gtisc.gatech.edu does not carry those.

debian.gtisc.gatech.edu??? None of the information in the OPs query
mentions this host.

2610:148:1f10:3::89 -> debian.gtisc.gatech.edu


All of his sources.list lines are using http://http.us.debian.org.
The issue is that
http://http.us.debian.org/debian/dists/wheezy/updates does not exist.
A casual look with a browser reveals this.

Exactly.

S°


Just how doers this contribute to a solution of the problem?

--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.Molecular-Modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Shyoe:  smolnar1

Re: Repository Problem

[Sven Hartge]

Michael Milliman  wrote:
> On 04/15/2016 03:18 PM, Sven Hartge wrote:
>> Dan Ritter  wrote:
>>> On Fri, Apr 15, 2016 at 01:06:18PM -0400, Stephen P. Molnar wrote:

 I just had a catastrophic crash which necessitated reinstalling
 Debian.  I had been running v-7.2,but decided to upgrade to v-7.10
 with a complete install.

 Now when I update the repositories, regardless of the tool, Synaptic
 or Aptitude, I get the following errors:

 W: Failed to fetch 
 http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 
 404  Not Found [IP: 2610:148:1f10:3::89 80]
 I do not get these errors if I comment out the deb-src lines in the
 sources.list.
>>> Those are IPv6 addresses. I would guess that you don't have an
>>> IPv6 connection available to you, or it's misconfigured.
>> He then would get a timeout or host unreachable and not a 404 HTTP error
>> code.
>>
>> What it looks like is this: he has URLs for the sources of security
>> updates (wheezy/updates) configured for the wrong host, because
>> debian.gtisc.gatech.edu does not carry those.
> debian.gtisc.gatech.edu??? None of the information in the OPs query 
> mentions this host.

2610:148:1f10:3::89 -> debian.gtisc.gatech.edu

> All of his sources.list lines are using http://http.us.debian.org.
> The issue is that
> http://http.us.debian.org/debian/dists/wheezy/updates does not exist.
> A casual look with a browser reveals this.

Exactly.

S°

-- 
Sigmentation fault. Core dumped.

RE: Repository Problem - SOLVED

[Stephen P. Molnar]

 

 

From: Stephen P. Molnar [mailto:s.mol...@sbcglobal.net] 
Sent: Saturday, April 16, 2016 6:37 AM
To: 'Michael Milliman'; debian-user@lists.debian.org
Subject: RE: Repository Problem

 

 

 

From: Michael Milliman [mailto:michael.e.milli...@gmail.com] 
Sent: Friday, April 15, 2016 11:27 PM
To: debian-user@lists.debian.org
Subject: Re: Repository Problem

 

 

On 04/15/2016 12:06 PM, Stephen P. Molnar wrote:

I just had a catastrophic crash which necessitated reinstalling Debian.  I had 
been running v-7.2,but decided to upgrade to v-7.10 with a complete install.

Now when I update the repositories, regardless of the tool, Synaptic or 
Aptitude, I get the following errors:

W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 404  
Not Found [IP: 2610:148:1f10:3::89 80]
W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/contrib/source/Sources: 
404  Not Found [IP: 2610:148:1f10:3::89 80]
W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/non-free/source/Sources: 
404  Not Found [IP: 2610:148:1f10:3::89 80]
E: Some index files failed to download. They have been ignored, or old ones 
used instead.
E: Couldn't rebuild package cache

Your deb-src lines should read as follows:

deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/main/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/contrib/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/non-free/source/Sources

Note that you have .../dists/wheezy/updates/... in your sources.list file 
instead of the correct .../dists/wheezy-updates/...



I do not get these errors if I comment out the deb-src lines in the 
sources.list.

Now, I know that it has to be a problem with the new install as I have 
installed v-7.10 in a VMware Workstation 12 Player on my laptop as a test bed 
and do not get any errors.

I would greatly appreciate help resolving this issue,.

Thanks in  advance.

-- 
Stephen P. Molnar, Ph.D.   Life is a fuzzy set
www.Molecular-Modeling.net Stochastic and multivariate
(614)312-7528 (c)
Shyoe:  smolnar1

 

-- 
Mike
 
Thanks for the suggestion.
 
The new error message is a malformation at the first line f the suggested 
solution.
 
There are several additional points to be made:
 
1.I get the same error when the repository is “devbain.uchicago.edu’
And, most  importantly,
 
2.   The errors arise from sources.list entries made by the Debian 
installer, not by my editing the file.
 
I am, however, most appreciative of the support that I am receiving from the 
members of the mailing list.
 

 

Stephen P. Molnar, Ph.D.   Life is a fuzzy set

www.molecular-modeling.net Stochastic and Multivariate

s.mol...@sbcglobal.net

(614)312-7528(c)

Skype:  smolnar1

 

Still don’t know why the problem, but a field expedient has made the problem 
redundant.
 
I am running the same version of Debian n my laptop in a VM as a test bed.  
There is no problem with the sources. List on that computer.  I ported the file 
over to the computer with the problem is gone.
 
Many thanks to the members of the list who responded to my cry in the 
wilderness.

 

Stephen P. Molnar, Ph.D.   Life is a fuzzy set

www.molecular-modeling.net Stochastic and Multivariate

s.mol...@sbcglobal.net

(614)312-7528(c)

Skype:  smolnar1

 

 
 

RE: Repository Problem

[Stephen P. Molnar]

 

 

From: Michael Milliman [mailto:michael.e.milli...@gmail.com] 
Sent: Friday, April 15, 2016 11:27 PM
To: debian-user@lists.debian.org
Subject: Re: Repository Problem

 

 

On 04/15/2016 12:06 PM, Stephen P. Molnar wrote:

I just had a catastrophic crash which necessitated reinstalling Debian.  I had 
been running v-7.2,but decided to upgrade to v-7.10 with a complete install.

Now when I update the repositories, regardless of the tool, Synaptic or 
Aptitude, I get the following errors:

W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 404  
Not Found [IP: 2610:148:1f10:3::89 80]
W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/contrib/source/Sources: 
404  Not Found [IP: 2610:148:1f10:3::89 80]
W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/non-free/source/Sources: 
404  Not Found [IP: 2610:148:1f10:3::89 80]
E: Some index files failed to download. They have been ignored, or old ones 
used instead.
E: Couldn't rebuild package cache

Your deb-src lines should read as follows:

deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/main/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/contrib/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/non-free/source/Sources

Note that you have .../dists/wheezy/updates/... in your sources.list file 
instead of the correct .../dists/wheezy-updates/...




I do not get these errors if I comment out the deb-src lines in the 
sources.list.

Now, I know that it has to be a problem with the new install as I have 
installed v-7.10 in a VMware Workstation 12 Player on my laptop as a test bed 
and do not get any errors.

I would greatly appreciate help resolving this issue,.

Thanks in  advance.



-- 
Stephen P. Molnar, Ph.D.   Life is a fuzzy set
www.Molecular-Modeling.net Stochastic and multivariate
(614)312-7528 (c)
Shyoe:  smolnar1





-- 
Mike
 
Thanks for the suggestion.
 
The new error message is a malformation at the first line f the suggested 
solution.
 
There are several additional points to be made:
 
1.I get the same error when the repository is “devbain.uchicago.edu’
And, most  importantly,
 
2.   The errors arise from sources.list entries made by the Debian 
installer, not by my editing the file.
 
I am, however, most appreciative of the support that I am receiving from the 
members of the mailing list.
 

 

Stephen P. Molnar, Ph.D.   Life is a fuzzy set

www.molecular-modeling.net Stochastic and Multivariate

s.mol...@sbcglobal.net

(614)312-7528(c)

Skype:  smolnar1

 

 
 
 

Re: Repository Problem

[Michael Milliman]

On 04/15/2016 12:06 PM, Stephen P. Molnar wrote:
I just had a catastrophic crash which necessitated reinstalling 
Debian.  I had been running v-7.2,but decided to upgrade to v-7.10 
with a complete install.


Now when I update the repositories, regardless of the tool, Synaptic 
or Aptitude, I get the following errors:


W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 
404  Not Found [IP: 2610:148:1f10:3::89 80]
W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/contrib/source/Sources: 
404  Not Found [IP: 2610:148:1f10:3::89 80]
W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/non-free/source/Sources: 
404  Not Found [IP: 2610:148:1f10:3::89 80]
E: Some index files failed to download. They have been ignored, or old 
ones used instead.

E: Couldn't rebuild package cache


Your deb-src lines should read as follows:

deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/main/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/contrib/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/non-free/source/Sources


Note that you have .../dists/wheezy/updates/... in your sources.list 
file instead of the correct .../dists/wheezy-updates/...


I do not get these errors if I comment out the deb-src lines in the 
sources.list.


Now, I know that it has to be a problem with the new install as I have 
installed v-7.10 in a VMware Workstation 12 Player on my laptop as a 
test bed and do not get any errors.


I would greatly appreciate help resolving this issue,.

Thanks in  advance.
-- Stephen P. Molnar, Ph.D. Life is a fuzzy set 
www.Molecular-Modeling.net	Stochastic and multivariate (614)312-7528 
(c) Shyoe: smolnar1


--
Mike

Re: Repository Problem

[Michael Milliman]

On 04/15/2016 03:18 PM, Sven Hartge wrote:

Dan Ritter  wrote:

On Fri, Apr 15, 2016 at 01:06:18PM -0400, Stephen P. Molnar wrote:

I just had a catastrophic crash which necessitated reinstalling
Debian.  I had been running v-7.2,but decided to upgrade to v-7.10
with a complete install.

Now when I update the repositories, regardless of the tool, Synaptic
or Aptitude, I get the following errors:

W: Failed to fetch 
http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 404  
Not Found [IP: 2610:148:1f10:3::89 80]
I do not get these errors if I comment out the deb-src lines in the
sources.list.

Those are IPv6 addresses. I would guess that you don't have an
IPv6 connection available to you, or it's misconfigured.

He then would get a timeout or host unreachable and not a 404 HTTP error
code.

What it looks like is this: he has URLs for the sources of security
updates (wheezy/updates) configured for the wrong host, because
debian.gtisc.gatech.edu does not carry those.
debian.gtisc.gatech.edu??? None of the information in the OPs query 
mentions this host.  All of his sources.list lines are using 
http://http.us.debian.org.  The issue is that 
http://http.us.debian.org/debian/dists/wheezy/updates does not exist.  A 
casual look with a browser reveals this.


Here is the lines that should be in the sources.list file

deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/main/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/contrib/source/Sources
deb-src 
http://http.us.debian.org/debian/dists/wheezy-updates/non-free/source/Sources


The OP has mistakenly .../wheezy/updates/... instead of 
/wheezy-updates/... in his deb-src lines



Grüße,
Sven.



--
Mike

Re: Repository Problem

[Sven Hartge]

Dan Ritter  wrote:
> On Fri, Apr 15, 2016 at 01:06:18PM -0400, Stephen P. Molnar wrote:

>> I just had a catastrophic crash which necessitated reinstalling
>> Debian.  I had been running v-7.2,but decided to upgrade to v-7.10
>> with a complete install.
>> 
>> Now when I update the repositories, regardless of the tool, Synaptic
>> or Aptitude, I get the following errors:
>> 
>> W: Failed to fetch 
>> http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 
>> 404  Not Found [IP: 2610:148:1f10:3::89 80]

>> I do not get these errors if I comment out the deb-src lines in the
>> sources.list.

> Those are IPv6 addresses. I would guess that you don't have an
> IPv6 connection available to you, or it's misconfigured.

He then would get a timeout or host unreachable and not a 404 HTTP error
code. 

What it looks like is this: he has URLs for the sources of security
updates (wheezy/updates) configured for the wrong host, because
debian.gtisc.gatech.edu does not carry those.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Repository Problem

[Dan Ritter]

On Fri, Apr 15, 2016 at 01:06:18PM -0400, Stephen P. Molnar wrote:
> I just had a catastrophic crash which necessitated reinstalling Debian.  I
> had been running v-7.2,but decided to upgrade to v-7.10 with a complete
> install.
> 
> Now when I update the repositories, regardless of the tool, Synaptic or
> Aptitude, I get the following errors:
> 
> W: Failed to fetch
> http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources:
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> W: Failed to fetch
> http://http.us.debian.org/debian/dists/wheezy/updates/contrib/source/Sources:
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> W: Failed to fetch 
> http://http.us.debian.org/debian/dists/wheezy/updates/non-free/source/Sources:
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> E: Some index files failed to download. They have been ignored, or old ones
> used instead.
> E: Couldn't rebuild package cache
> 
> I do not get these errors if I comment out the deb-src lines in the
> sources.list.

Those are IPv6 addresses. I would guess that you don't have an
IPv6 connection available to you, or it's misconfigured.

in /etc/gai.conf, uncomment this line

#precedence :::0:0/96  100

And your system will prefer IPv4 addressing.

-dsr-

Re: Repository Problem

[Jeremy Nicoll]

On Fri, 15 Apr 2016, at 18:06, Stephen P. Molnar wrote:
> I just had a catastrophic crash which necessitated reinstalling Debian.  

I've been hunting around for a distro to use and am  basing a lot of my
decision on 
the typical traffic of each distro's users' mail list.  So far I'm
getting the impression 
that Debian users & I would see eye-to-eye about a lot of things...

Anyway...If you don't mind me asking, what sort of catastrophe was this? 

-- 
Jeremy Nicoll - my opinions are my own.

Re: Repository Problem

[Patrick Bartek]

On Fri, 15 Apr 2016, Stephen P. Molnar wrote:

> I just had a catastrophic crash which necessitated reinstalling
> Debian. I had been running v-7.2,but decided to upgrade to v-7.10
> with a complete install.
> 
> Now when I update the repositories, regardless of the tool, Synaptic
> or Aptitude, I get the following errors:
> 
> W: Failed to fetch 
> http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> W: Failed to fetch 
> http://http.us.debian.org/debian/dists/wheezy/updates/contrib/source/Sources: 
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> W: Failed to fetch 
> http://http.us.debian.org/debian/dists/wheezy/updates/non-free/source/Sources:
>  
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> E: Some index files failed to download. They have been ignored, or
> old ones used instead.
> E: Couldn't rebuild package cache
> 
> I do not get these errors if I comment out the deb-src lines in the 
> sources.list.
> 
> Now, I know that it has to be a problem with the new install as I
> have installed v-7.10 in a VMware Workstation 12 Player on my laptop
> as a test bed and do not get any errors.
> 
> I would greatly appreciate help resolving this issue,.
> 
> Thanks in  advance.

In /etc/apt/sources.list, substiute ftp.us.debian.org for all
occurences of http.us.debian.org That's the way the installer
set it up on my Wheezy 7.10.

B

Re: Repository Problem

[Jordi Dalmau]

Hi,

You can try to replace in /etc/apt/sources.list or using Synaptic
changing distribution in Settings/Repositories

wheezy/updates 
by 
wheezy

Remember, you can see in a browser that the following URL
http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources
doesn't exists.  

Once you had done the change execute
apt-get update 
or 
press Reload in Synaptic

Good luck
Regards

On Fri, 2016-04-15 at 13:06 -0400, Stephen P. Molnar wrote:
> I just had a catastrophic crash which necessitated reinstalling
> Debian.  I had been running v-7.2,but decided to upgrade to v-7.10
> with a complete install.
> 
> Now when I update the repositories, regardless of the tool, Synaptic
> or Aptitude, I get the following errors:
> 
> W: Failed to fetch
> http://http.us.debian.org/debian/dists/wheezy/updates/main/source/Sources: 
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> W: Failed to fetch
> http://http.us.debian.org/debian/dists/wheezy/updates/contrib/source/Sources: 
> 404  Not Found [IP: 2610:148:1f10:3::89 80]
> W: Failed to fetch
> http://http.us.debian.org/debian/dists/wheezy/updates/non-free/source/Sources:
>  404  Not Found [IP: 2610:148:1f10:3::89 80]
> E: Some index files failed to download. They have been ignored, or old
> ones used instead.
> E: Couldn't rebuild package cache
> 
> I do not get these errors if I comment out the deb-src lines in the
> sources.list.
> 
> Now, I know that it has to be a problem with the new install as I have
> installed v-7.10 in a VMware Workstation 12 Player on my laptop as a
> test bed and do not get any errors.
> 
> I would greatly appreciate help resolving this issue,.
> 
> Thanks in  advance.
> -- 
> Stephen P. Molnar, Ph.D.  Life is a fuzzy set
> www.Molecular-Modeling.netStochastic and multivariate
> (614)312-7528 (c)
> Shyoe:  smolnar1

Re: Repository Problem

[Stephen P. Molnar]

On 04/15/2016 01:19 PM, John Conover wrote:

Stephen P. Molnar writes:

I just had a catastrophic crash which necessitated reinstalling Debian.
I had been running v-7.2,but decided to upgrade to v-7.10 with a
complete install.

Now when I update the repositories, regardless of the tool, Synaptic or
Aptitude, I get the following errors:


Hi Stephen.

in /etc/apt/sources.list, try commenting out:

 # deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot i386 
LIVE/INSTALL Binary 20140723-18:21]/ wheezy main

 John



There is no such line in sources.list.  I have attained the file,

--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.Molecular-Modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Shyoe:  smolnar1

# 

# deb cdrom:[Debian GNU/Linux 7.10.0 _Wheezy_ - Official amd64 DVD Binary-1 
20160403-10:50]/ wheezy contrib main

# deb cdrom:[Debian GNU/Linux 7.10.0 _Wheezy_ - Official amd64 DVD Binary-1 
20160403-10:50]/ wheezy contrib main

deb http://http.us.debian.org/debian/ wheezy main non-free contrib
# deb-src http://http.us.debian.org/debian/ wheezy main non-free contrib

deb http://security.debian.org/ wheezy/updates main contrib non-free
# deb-src http://http.us.debian.org/debian/ wheezy/updates main contrib non-free

# wheezy-updates, previously known as 'volatile'
deb http://http.us.debian.org/debian/ wheezy-updates main contrib non-free
# deb-src http://http.us.debian.org/debian/ wheezy-updates main contrib non-free

deb http://packages.linuxmint.com debian import

deb http://www.deb-multimedia.org wheezy main non-free

Re: Repository-problem

[Paul van der Vlis]

Osamu Aoki schreef:
 On Wed, Sep 10, 2008 at 11:25:38AM +0200, Paul van der Vlis wrote:
 Hello,

 I have a very simple test-repository:
 deb http://www.vandervlis.nl/debian/ ./
 
 I suspect this old simple repository is not compatible with secure apt.
  
 It works, but it was not signed. Now I try to get the signing OK, but
 when I do an apt-get update I get this error:

 Failed to fetch http://www.vandervlis.nl/debian/./Release  Unable to
 find expected entry  Packages in Meta-index file (malformed Release file?)

 What will be wrong?
 Please take a look to my Release-file:
 http://www.vandervlis.nl/debian/Release

 The code is only Perl and bash, so I can use it for all architectures.
 
 There are 2 Release file with different purpose.  With secure APT, you
 need particular one.
   
 Please read new Debian Reference package in lenny or:
 in http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html there
 are few interesting parts for you:
 
  
 http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#toplevelreleasefeandauthenticity
  
 http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#archivelevelreleasefiles
  
 http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#smallpublicpackagearchive

Thanks for your help Osamu!

With regards,
Paul van der Vlis.




-- 
http://www.vandervlis.nl/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Repository-problem

[Osamu Aoki]

On Wed, Sep 10, 2008 at 11:25:38AM +0200, Paul van der Vlis wrote:
 Hello,
 
 I have a very simple test-repository:
 deb http://www.vandervlis.nl/debian/ ./

I suspect this old simple repository is not compatible with secure apt.
 
 It works, but it was not signed. Now I try to get the signing OK, but
 when I do an apt-get update I get this error:
 
 Failed to fetch http://www.vandervlis.nl/debian/./Release  Unable to
 find expected entry  Packages in Meta-index file (malformed Release file?)
 
 What will be wrong?
 Please take a look to my Release-file:
 http://www.vandervlis.nl/debian/Release
 
 The code is only Perl and bash, so I can use it for all architectures.

There are 2 Release file with different purpose.  With secure APT, you
need particular one.
  
Please read new Debian Reference package in lenny or:
in http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html there
are few interesting parts for you:

 
http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#toplevelreleasefeandauthenticity
 
http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#archivelevelreleasefiles
 
http://people.debian.org/~osamu/pub/getwiki/html/ch03.en.html#smallpublicpackagearchive

Osamu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]