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

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

apt-get changelog is unsuccessful, but changelog exists

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

Contents

  apt-get changelog is unsuccessful, but changelog exists davidson@freevolt.org - 2016-11-05 20:10 +0100
    Re: apt-get changelog is unsuccessful, but changelog exists davidson@freevolt.org - 2016-11-05 20:30 +0100
    Re: apt-get changelog is unsuccessful, but changelog exists Brian <ad44@cityscape.co.uk> - 2016-11-05 20:40 +0100
      Re: apt-get changelog is unsuccessful, but changelog exists Jochen Spieker <ml@well-adjusted.de> - 2016-11-05 21:00 +0100
        Re: apt-get changelog is unsuccessful, but changelog exists Brian <ad44@cityscape.co.uk> - 2016-11-05 21:40 +0100
      Re: apt-get changelog is unsuccessful, but changelog exists davidson@freevolt.org - 2016-11-05 21:30 +0100
        Re: apt-get changelog is unsuccessful, but changelog exists Greg Wooledge <wooledg@eeg.ccf.org> - 2016-11-07 14:20 +0100
          Re: apt-get changelog is unsuccessful, but changelog exists Brian <ad44@cityscape.co.uk> - 2016-11-07 20:50 +0100
            Re: apt-get changelog is unsuccessful, but changelog exists David Wright <deblis@lionunicorn.co.uk> - 2016-11-07 21:30 +0100
              Re: apt-get changelog is unsuccessful, but changelog exists Brian <ad44@cityscape.co.uk> - 2016-11-08 00:30 +0100
                Re: apt-get changelog is unsuccessful, but changelog exists David Wright <deblis@lionunicorn.co.uk> - 2016-11-08 01:20 +0100
                  Re: apt-get changelog is unsuccessful, but changelog exists Brian <ad44@cityscape.co.uk> - 2016-11-08 20:20 +0100
                    Re: apt-get changelog is unsuccessful, but changelog exists davidson@freevolt.org - 2016-11-13 22:30 +0100

#174204 — apt-get changelog is unsuccessful, but changelog exists

Running...

   $ apt-get changelog UPGRADEABLE_PACKAGE

...on a wheezy system pointed at these sources...

   $ grep '^deb ' /etc/apt/sources.list
   deb http://debian.univ-lorraine.fr/debian/ wheezy-updates main
   deb http://debian.univ-lorraine.fr/debian/ wheezy main
   deb http://debian.univ-lorraine.fr/debian/ wheezy-backports main
   deb http://security.debian.org/ wheezy/updates main

...frequently fails to do what I expect.

A recent example:

   $ apt-get changelog libxslt1.1
   Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2/changelog)
     404  Not Found [IP: 5.153.231.3 80]
   Err Changelog for libxslt1.1 (http://security.debian.org/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2.changelog)
     404  Not Found [IP: 128.31.0.63 80]
   E: changelog download failed

In the example above, I sought to read a description of the differences
between my currently installed libxslt1.1 package, and the more recent
available version.

Instead, to obtain changelogs, the 8-step workflow outlined below is
typical for me. It seems to work fine, but I am curious why steps 1--4
alone do not suffice.

If anyone can give me a clue here, I would be grateful.

WORKFLOW

Since I like to do some reading about packages, and (at least) review
changelogs, before I upgrade them, instead of simply doing...

   # apt-get update && apt-get upgrade

...I follow the template below:

1. Retrieve information about new/updated packages.

   # apt-get update

2. Simulate an upgrade, to see what can be upgraded.

   # apt-get -s upgrade

3. For each upgradeable package, review its description.

   $ apt-cache --no-all-versions show UPGRADEABLE_PACKAGE |sed -n '/^Description-en/,/^[^[:blank:]]/ p'

4. Attempt to review the changelog for that package.

   $ apt-get changelog UPGRADEABLE_PACKAGE

When step 4 fails, I continue as follows:

5. Get the diff from the source archive.

   $ apt-get --diff-only source UPGRADEABLE_PACKAGE

6. Decompress and unpack the diff.

   $ gunzip SOURCE_VERSION.debian.tar.gz && tar xf SOURCE_VERSION.debian.tar

7. See what files I've just unpacked.

   $ ls debian/

8. Look at most recent entry in the changelog, which is what I was
after in step 4.

   $ sed -n '1,/^[^[:blank:]]/ p' debian/changelog

(And then of course, after I've finished reading about what it will
do, I eventually run apt-get upgrade.)

-- 

MS CLINTON: If you google up what the Chinese claim is, it's the entire South China sea...
MR BLANKFEIN: An unfortunate name.
MS CLINTON: Which one?
MR BLANKFEIN: The South China sea.
MS CLINTON: Yes, it is.

https://wikileaks.org/podesta-emails/fileid/11011/2873

[toc] | [next] | [standalone]

#174205

On Sat, 5 Nov 2016, davidson@freevolt.org wrote:
[snip]
> In the example above, I sought to read a description of the differences
> between my currently installed libxslt1.1 package, and the more recent
> available version.
>
> Instead, to obtain changelogs, the 8-step workflow outlined below is
> typical for me. It seems to work fine, but I am curious why steps 1--4
> alone do not suffice.
>
> If anyone can give me a clue here, I would be grateful.
>
> WORKFLOW
[snap]

In case it helps clarify what is going on, here is example output from
that workflow:

# apt-get update # STEP 1
[Copious output about gets and hits, which i did not capture. Sorry.]
Fetched [xyz] kB in [u]s ([pqr] kB/s)
Reading package lists... Done

# apt-get -s upgrade # STEP 2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
   libxslt1.1
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Inst libxslt1.1 [1.1.26-14.1+deb7u1] (1.1.26-14.1+deb7u2 Debian-Security:7.0/oldstable [i386])
Conf libxslt1.1 (1.1.26-14.1+deb7u1 Debian-Security:7.0/oldstable [i386])

$ apt-cache --no-all-versions show libxslt1.1 |sed -n '/^Description-en/,/^[^[:blank:]]/ p' # STEP 3
Description-en: XSLT 1.0 processing library - runtime library
  XSLT is an XML language for defining transformations of XML files from
  XML to some other arbitrary format, such as XML, HTML, plain text, etc.
  using standard XSLT stylesheets. libxslt is a C library which
  implements XSLT version 1.0.
  .
  This package contains the libxslt library used by applications for XSLT
  transformations.
Homepage: http://xmlsoft.org/xslt/

$ apt-get changelog libxslt1.1 # STEP 4
Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2/changelog)
   404  Not Found [IP: 5.153.231.3 80]
Err Changelog for libxslt1.1 (http://security.debian.org/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2.changelog)
   404  Not Found [IP: 128.31.0.63 80]
E: changelog download failed

$ apt-get --diff-only source libxslt1.1 # STEP 5
Reading package lists...
Building dependency tree...
Reading state information...
Picking 'libxslt' as source package instead of 'libxslt1.1'
NOTICE: 'libxslt' packaging is maintained in the 'Git' version control system at:
git://git.debian.org/debian-xml-sgml/libxslt.git
Need to get 47.0 kB of source archives.
Get:1 http://security.debian.org/ wheezy/updates/main libxslt 1.1.26-14.1+deb7u2 (diff) [47.0 kB]
Fetched 47.0 kB in 0s (91.1 kB/s)

$ gunzip libxslt_1.1.26-14.1+deb7u2.debian.tar.gz && tar xf libxslt_1.1.26-14.1+deb7u2.debian.tar # STEP 6

$ ls debian/ # STEP 7
changelog
compat
control
copyright
libxslt1.1.install
libxslt1.1.lintian-overrides
libxslt1.1.symbols
libxslt1-dev.doc-base
libxslt1-dev.install
libxslt1-dev.manpages
patches
python-libxslt1-dbg.install
python-libxslt1-dbg.lintian-overrides
python-libxslt1-dbg.preinst
python-libxslt1.examples
python-libxslt1.install
README.Debian
rules
source
TODO
watch
xslt-config.1
xsltproc.install
xsltproc.manpages

$ sed -n '1,/^[^[:blank:]]/ p' debian/changelog # STEP 8
libxslt (1.1.26-14.1+deb7u2) wheezy-security; urgency=medium

   * Non-maintainer upload by the LTS team.
   * 0019-Fix-heap-overread-in-xsltFormatNumberConversion.patch:
     + CVE-2016-4738: Patch from upstream to fix a potential heap overread
       that can cause arbitrary code execution or denial of service.
       Closes: #842570.

  -- Emilio Pozuelo Monfort <pochu@debian.org>  Sat, 05 Nov 2016 11:26:56 +0100

libxslt (1.1.26-14.1+deb7u1) wheezy-security; urgency=medium

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

#174207

On Sat 05 Nov 2016 at 19:06:49 +0000, davidson@freevolt.org wrote:

> Running...
> 
>   $ apt-get changelog UPGRADEABLE_PACKAGE
> 
> ...on a wheezy system pointed at these sources...
> 
>   $ grep '^deb ' /etc/apt/sources.list
>   deb http://debian.univ-lorraine.fr/debian/ wheezy-updates main
>   deb http://debian.univ-lorraine.fr/debian/ wheezy main
>   deb http://debian.univ-lorraine.fr/debian/ wheezy-backports main
>   deb http://security.debian.org/ wheezy/updates main
> 
> ...frequently fails to do what I expect.
> 
> A recent example:

[Snipped]

It's quite amazing what people expect to be supported on this list.
Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
Irrespective of whether it was thought to be wonderful in its day it is
now moribund apart from LTS. Discard it; let it disappear into history.

Now, if the OP had said "I observe the same behaviour on jessie and
stretch" that might be interesting. If he doesn't, it drops off the
radar. We are at the beginning of a freeze. Those who expect support
for Wheezy are pushing the envelope.

  apt-get changelog mutt

works very nicely on jessie, incidentally.

-- 
Brian.

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

#174208

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

Brian:
> 
> It's quite amazing what people expect to be supported on this list.
> Wheezy is an unsupported distribution, just like hamm, etch, potato etc.

That's not entirely true:

https://www.debian.org/releases/wheezy/

Wheezy is still in LTS support until end of May 2018. I don't know
whether it solves the OP's problem but I think
https://wiki.debian.org/LTS is worth a look in any case.

J.
-- 
I am not scared of death but terrified of people in Tommy Hilfiger
sweatshirts.
[Agree]   [Disagree]
                 <http://archive.slowlydownward.com/NODATA/data_enter2.html>

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

#174211

On Sat 05 Nov 2016 at 20:53:47 +0100, Jochen Spieker wrote:

> Brian:
> > 
> > It's quite amazing what people expect to be supported on this list.
> > Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> 
> That's not entirely true:
> 
> https://www.debian.org/releases/wheezy/

It's entirely true. From the web page you quoted;

  > Debian 7.0 has been superseded by Debian 8.0 ("jessie"). 
 
> Wheezy is still in LTS support until end of May 2018. I don't know
> whether it solves the OP's problem but I think
> https://wiki.debian.org/LTS is worth a look in any case.

You'll notice; I mentioned LTS. It is for security support, isn't it? A
worthy objective. That does does not imply it will clear up each and
every glitch Wheezy has.

There are enough people on this list who are still using Wheezy. They
are the ones to test the OP's command. The rest of us stick with Jessie
and hope not to have deal with problems on Bo.

-- 
Brian.

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

#174210

On Sat, 5 Nov 2016, Brian wrote:
> On Sat 05 Nov 2016 at 19:06:49 +0000, davidson@freevolt.org wrote:
>
>> Running...
>>
>>   $ apt-get changelog UPGRADEABLE_PACKAGE
>>
>> ...on a wheezy system pointed at these sources...
>>
>>   $ grep '^deb ' /etc/apt/sources.list
>>   deb http://debian.univ-lorraine.fr/debian/ wheezy-updates main
>>   deb http://debian.univ-lorraine.fr/debian/ wheezy main
>>   deb http://debian.univ-lorraine.fr/debian/ wheezy-backports main
>>   deb http://security.debian.org/ wheezy/updates main
>>
>> ...frequently fails to do what I expect.
>>
>> A recent example:
>
> [Snipped]
>
> It's quite amazing what people expect to be supported on this list.

The occasional surprise keeps the humors in balance. Happy to help.

> Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> Irrespective of whether it was thought to be wonderful in its day it is
> now moribund apart from LTS.

We seem to have different understandings of what LTS stands for.

Interesting.

> Discard it; let it disappear into history.

No thank you. Asking questions is something I like to do from time to
time. Formulating them in the first place helps me to identify what I
have learned, and what I remain ignorant of.

Answers, when available, are icing on the cake.

(Also, would it not be a shame if there were no users to enjoy the
fruits of the debian LTS team's continuing efforts?)

> Now, if the OP had said "I observe the same behaviour on jessie and
> stretch" that might be interesting.

I maintain a jessie system as well, and I do not recall observing this
behavior there.

I find the difference interesting. To each his own.

> If he doesn't, it drops off the radar. We are at the beginning of a
> freeze. Those who expect support for Wheezy are pushing the
> envelope.

I've made no demands; I've registered curiosity. I expect replies only
from those who wish to satisfy it.

It is not inconcievable to me that some subscribers to this list might
be willing and able to do so.

One way or another, we will find out.

>  apt-get changelog mutt
>
> works very nicely on jessie, incidentally.

Yes, that is my experience as well.

I remain curious about the behavior on wheezy.

Take care, Brian.

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

#174287

On Sat, Nov 05, 2016 at 08:25:02PM +0000, davidson@freevolt.org wrote:
> On Sat, 5 Nov 2016, Brian wrote:
> >Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> >Irrespective of whether it was thought to be wonderful in its day it is
> >now moribund apart from LTS.
> 
> We seem to have different understandings of what LTS stands for.
> 
> Interesting.

At least remember what the "S" stands for (Brian).

There are plenty of people still running wheezy, and there will be for
many years to come (long after wheezy LTS is discontinued).  If you don't
wish to support it, that's fine -- you can simply not reply.

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

#174325

On Mon 07 Nov 2016 at 08:18:17 -0500, Greg Wooledge wrote:

> On Sat, Nov 05, 2016 at 08:25:02PM +0000, davidson@freevolt.org wrote:
> > On Sat, 5 Nov 2016, Brian wrote:
> > >Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> > >Irrespective of whether it was thought to be wonderful in its day it is
> > >now moribund apart from LTS.
> > 
> > We seem to have different understandings of what LTS stands for.
> > 
> > Interesting.
> 
> At least remember what the "S" stands for (Brian).

Noted. Also note that support from all those Wheezy users here wasn't
exactly rampant.

> There are plenty of people still running wheezy, and there will be for
> many years to come (long after wheezy LTS is discontinued).  If you don't
> wish to support it, that's fine -- you can simply not reply.

The last bit is excellent advice; I wish someone had been around at the
time to advise me. :) 

I've stopped thinking about Lenny and Potato, too.

-- 
Brian.

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

#174327

On Mon 07 Nov 2016 at 19:40:00 (+0000), Brian wrote:
> On Mon 07 Nov 2016 at 08:18:17 -0500, Greg Wooledge wrote:
> 
> > On Sat, Nov 05, 2016 at 08:25:02PM +0000, davidson@freevolt.org wrote:
> > > On Sat, 5 Nov 2016, Brian wrote:
> > > >Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> > > >Irrespective of whether it was thought to be wonderful in its day it is
> > > >now moribund apart from LTS.
> > > 
> > > We seem to have different understandings of what LTS stands for.
> > > 
> > > Interesting.
> > 
> > At least remember what the "S" stands for (Brian).
> 
> Noted. Also note that support from all those Wheezy users here wasn't
> exactly rampant.

What are we to get rampant about? The OP posted a workaround right
there in the OP, and glossed it in a follow-up.

Most of the thread appears to have discussed the opinion expressed in
your first paragraph.

> I've stopped thinking about Lenny and Potato, too.

So have I, but currently I get a fully automatic bluetooth service for
my mobiles from wheezy which I have not managed to translate to jessie.

If stretch is going into freeze, then I'll probably skip bothering
about bluetooth on jessie.

Cheers,
David.

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

#174328

On Mon 07 Nov 2016 at 14:20:57 -0600, David Wright wrote:

> On Mon 07 Nov 2016 at 19:40:00 (+0000), Brian wrote:
> > On Mon 07 Nov 2016 at 08:18:17 -0500, Greg Wooledge wrote:
> > 
> > > On Sat, Nov 05, 2016 at 08:25:02PM +0000, davidson@freevolt.org wrote:
> > > > On Sat, 5 Nov 2016, Brian wrote:
> > > > >Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> > > > >Irrespective of whether it was thought to be wonderful in its day it is
> > > > >now moribund apart from LTS.
> > > > 
> > > > We seem to have different understandings of what LTS stands for.
> > > > 
> > > > Interesting.
> > > 
> > > At least remember what the "S" stands for (Brian).
> > 
> > Noted. Also note that support from all those Wheezy users here wasn't
> > exactly rampant.
> 
> What are we to get rampant about? The OP posted a workaround right
> there in the OP, and glossed it in a follow-up.
> 
> Most of the thread appears to have discussed the opinion expressed in
> your first paragraph.

Something for people to get their teeth into. From the first post:

 > apt-get changelog libxslt1.1
 > Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2/changelog)
 > 404  Not Found [IP: 5.153.231.3 80]

On my machine:

 brian@desktop:~$ lynx http://packages.debian.org/changelogs/pool/updates/main/
                  The requested URL /changelogs/updates/main was not found on this server.

What does the workabout compensate for?

-- 
Brian.

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

#174331

On Mon 07 Nov 2016 at 23:24:31 (+0000), Brian wrote:
> On Mon 07 Nov 2016 at 14:20:57 -0600, David Wright wrote:
> 
> > On Mon 07 Nov 2016 at 19:40:00 (+0000), Brian wrote:
> > > On Mon 07 Nov 2016 at 08:18:17 -0500, Greg Wooledge wrote:
> > > 
> > > > On Sat, Nov 05, 2016 at 08:25:02PM +0000, davidson@freevolt.org wrote:
> > > > > On Sat, 5 Nov 2016, Brian wrote:
> > > > > >Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> > > > > >Irrespective of whether it was thought to be wonderful in its day it is
> > > > > >now moribund apart from LTS.
> > > > > 
> > > > > We seem to have different understandings of what LTS stands for.
> > > > > 
> > > > > Interesting.
> > > > 
> > > > At least remember what the "S" stands for (Brian).
> > > 
> > > Noted. Also note that support from all those Wheezy users here wasn't
> > > exactly rampant.
> > 
> > What are we to get rampant about? The OP posted a workaround right
> > there in the OP, and glossed it in a follow-up.
> > 
> > Most of the thread appears to have discussed the opinion expressed in
> > your first paragraph.
> 
> Something for people to get their teeth into. From the first post:
> 
>  > apt-get changelog libxslt1.1
>  > Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2/changelog)
>  > 404  Not Found [IP: 5.153.231.3 80]
> 
> On my machine:
> 
>  brian@desktop:~$ lynx http://packages.debian.org/changelogs/pool/updates/main/
>                   The requested URL /changelogs/updates/main was not found on this server.
> 
> What does the workabout compensate for?

The 404. https://lists.debian.org/debian-user/2016/11/msg00098.html step 8.

Cheers,
David.

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

#174367

On Mon 07 Nov 2016 at 18:17:05 -0600, David Wright wrote:

> On Mon 07 Nov 2016 at 23:24:31 (+0000), Brian wrote:
> > On Mon 07 Nov 2016 at 14:20:57 -0600, David Wright wrote:
> > 
> > > On Mon 07 Nov 2016 at 19:40:00 (+0000), Brian wrote:
> > > > On Mon 07 Nov 2016 at 08:18:17 -0500, Greg Wooledge wrote:
> > > > 
> > > > > On Sat, Nov 05, 2016 at 08:25:02PM +0000, davidson@freevolt.org wrote:
> > > > > > On Sat, 5 Nov 2016, Brian wrote:
> > > > > > >Wheezy is an unsupported distribution, just like hamm, etch, potato etc.
> > > > > > >Irrespective of whether it was thought to be wonderful in its day it is
> > > > > > >now moribund apart from LTS.
> > > > > > 
> > > > > > We seem to have different understandings of what LTS stands for.
> > > > > > 
> > > > > > Interesting.
> > > > > 
> > > > > At least remember what the "S" stands for (Brian).
> > > > 
> > > > Noted. Also note that support from all those Wheezy users here wasn't
> > > > exactly rampant.
> > > 
> > > What are we to get rampant about? The OP posted a workaround right
> > > there in the OP, and glossed it in a follow-up.
> > > 
> > > Most of the thread appears to have discussed the opinion expressed in
> > > your first paragraph.
> > 
> > Something for people to get their teeth into. From the first post:
> > 
> >  > apt-get changelog libxslt1.1
> >  > Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2/changelog)
> >  > 404  Not Found [IP: 5.153.231.3 80]
> > 
> > On my machine:
> > 
> >  brian@desktop:~$ lynx http://packages.debian.org/changelogs/pool/updates/main/
> >                   The requested URL /changelogs/updates/main was not found on this server.
> > 
> > What does the workabout compensate for?
> 
> The 404. https://lists.debian.org/debian-user/2016/11/msg00098.html step 8.

The idea of a workabout getting a file which doesn't exist is an
interesting one. :)

Leaving that aside, what 'apt-get changelog' is doing and why is also
interesting. Commenting out the "security" line could have a different
outcome. (Wheezy or not).

-- 
Brian.


> 
> Cheers,
> David.
> 

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

#174670

On Tue, 8 Nov 2016, Brian wrote:
> On Mon 07 Nov 2016 at 18:17:05 -0600, David Wright wrote:
>> On Mon 07 Nov 2016 at 23:24:31 (+0000), Brian wrote:
>>>
>>> Something for people to get their teeth into. From the first post:
>>>
>>> > apt-get changelog libxslt1.1
>>> > Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2/changelog)
>>> > 404  Not Found [IP: 5.153.231.3 80]
>>>
>>> On my machine:
>>>
>>>  brian@desktop:~$ lynx http://packages.debian.org/changelogs/pool/updates/main/
>>>                   The requested URL /changelogs/updates/main was not found on this server.
>>>
>>> What does the workabout compensate for?
>>
>> The 404. https://lists.debian.org/debian-user/2016/11/msg00098.html step 8.
>
> The idea of a workabout getting a file which doesn't exist is an
> interesting one. :)

With the workaround, I get the changelog for the most recent
installable version from the package sources, since it appears not to
be present wherever apt-get changelog is looking.

> Leaving that aside, what 'apt-get changelog' is doing and why is
> also interesting.  Commenting out the "security" line could have a
> different outcome. (Wheezy or not).

For the curious, I ran that experiment.

Output from when the security repo lines are commented out is below
(followed by output from when the same lines are re-enabled).

With

  deb http://security.debian.org/ wheezy/updates main
  deb-src http://security.debian.org/ wheezy/updates main

commented out in /etc/apt/sources.list:

  # apt-get update
  [output not captured]

  # apt-get -s upgrade
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages have been kept back:
    libpoppler-glib8 libsmbclient libswscale2 openssh-client openssh-server
    poppler-utils suckless-tools
  The following packages will be upgraded:
    file libmagic1 libpostproc52 libwbclient0 linux-libc-dev tar
  6 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
  Inst tar [1.26+dfsg-0.1+deb7u1] (1.27.1-1~bpo70+1 Debian Backports:/wheezy-backports [i386])
  Conf tar (1.27.1-1~bpo70+1 Debian Backports:/wheezy-backports [i386])
  Inst file [5.11-2+deb7u9] (1:5.22+15-2~bpo7+1 Debian Backports:/wheezy-backports [i386]) []
  Inst libmagic1 [5.11-2+deb7u9] (1:5.22+15-2~bpo7+1 Debian Backports:/wheezy-backports [i386])
  Inst libwbclient0 [2:3.6.6-6+deb7u10] (2:4.1.17+dfsg-1~bpo70+1 Debian Backports:/wheezy-backports [i386])
  Inst libpostproc52 [6:0.8.18-0+deb7u1] (6:0.git20120821-4~bpo70+1 Debian Backports:/wheezy-backports [i386])
  Inst linux-libc-dev [3.2.82-1] (3.16.36-1+deb8u2~bpo70+1 Debian Backports:/wheezy-backports [i386])
  Conf libmagic1 (1:5.22+15-2~bpo7+1 Debian Backports:/wheezy-backports [i386])
  Conf file (1:5.22+15-2~bpo7+1 Debian Backports:/wheezy-backports [i386])
  Conf libwbclient0 (2:4.1.17+dfsg-1~bpo70+1 Debian Backports:/wheezy-backports [i386])
  Conf libpostproc52 (6:0.git20120821-4~bpo70+1 Debian Backports:/wheezy-backports [i386])
  Conf linux-libc-dev (3.16.36-1+deb8u2~bpo70+1 Debian Backports:/wheezy-backports [i386])

  $ apt-get changelog libxslt1.1
  Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/./libxslt_1.1.26-14.1+deb7u1/changelog)
    404  Not Found [IP: 128.31.0.51 80]
  E: changelog download failed

Same sequence of commands, but with

  deb http://security.debian.org/ wheezy/updates main
  deb-src http://security.debian.org/ wheezy/updates main

re-enabled in /etc/apt/sources.list:

  # apt-get update
  [output not captured]

  # apt-get -s upgrade
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
    libxslt1.1 tzdata
  2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Inst libxslt1.1 [1.1.26-14.1+deb7u1] (1.1.26-14.1+deb7u2 Debian-Security:7.0/oldstable [i386])
  Inst tzdata [2016h-0+deb7u1] (2016i-0+deb7u1 Debian-Security:7.0/oldstable [all])
  Conf tzdata (2016i-0+deb7u1 Debian-Security:7.0/oldstable [all])
  Conf libxslt1.1 (1.1.26-14.1+deb7u2 Debian-Security:7.0/oldstable [i386])

  $ apt-get changelog libxslt1.1
  Err Changelog for libxslt1.1 (http://packages.debian.org/changelogs/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2/changelog)
    404  Not Found [IP: 128.31.0.51 80]
  Err Changelog for libxslt1.1 (http://security.debian.org/pool/updates/main/libx/libxslt/libxslt_1.1.26-14.1+deb7u2.changelog)
    404  Not Found [IP: 128.31.0.63 80]
  E: changelog download failed

[toc] | [prev] | [standalone]

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

csiph-web