Your message dated Sun, 23 Sep 2012 19:10:07 -0500
with message-id <[email protected]>
and subject line Re: oddity in upgrading
has caused the Debian Bug report #660085,
regarding oddity in upgrading
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
660085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660085
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libboost
Version: 1.48.0.2
File: boost-default
Apparently, current package in sid cannot be dist-upgraded without pre-removing
another package.
That should be fixed to allow a smooth dist-upgrade instead, IMHO. That could
be due to defects in default package boost-default.
See below:
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libboost-dev libboost-filesystem-dev libboost-iostreams-dev
libboost-program-options-dev libboost-python-dev libboost-regex-dev
libboost-system-dev
libboost-thread-dev
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
frankie@blegrez:~
$ sudo apt-get install libboost-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libboost-serialization1.46.1 libboost-date-time1.46.1 libboost-iostreams1.46.1
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
libboost-date-time1.48-dev libboost-filesystem-dev
libboost-filesystem1.48-dev libboost-iostreams-dev libboost-iostreams1.48-dev
libboost-program-options-dev libboost-program-options1.48-dev
libboost-python-dev libboost-python1.48-dev libboost-regex-dev
libboost-regex1.48-dev
libboost-serialization1.48-dev libboost-system-dev libboost-system1.48-dev
libboost-thread-dev libboost-thread1.48-dev libboost1.48-dev
Suggested packages:
libboost-doc libboost1.48-doc libboost-chrono1.48-dev
libboost-graph-parallel1.48-dev libboost-graph1.48-dev libboost-locale1.48-dev
libboost-math1.48-dev libboost-mpi1.48-dev libboost-random1.48-dev
libboost-signals1.48-dev libboost-test1.48-dev libboost-timer1.48-dev
libboost-wave1.48-dev
The following packages will be REMOVED:
libboost-date-time1.46-dev libboost-filesystem1.46-dev
libboost-iostreams1.46-dev libboost-program-options1.46-dev
libboost-python1.46-dev
libboost-regex1.46-dev libboost-serialization1.46-dev libboost-system1.46-dev
libboost-thread1.46-dev libboost1.46-dev
The following NEW packages will be installed:
libboost-date-time1.48-dev libboost-filesystem1.48-dev
libboost-iostreams1.48-dev libboost-program-options1.48-dev
libboost-python1.48-dev
libboost-regex1.48-dev libboost-serialization1.48-dev libboost-system1.48-dev
libboost-thread1.48-dev libboost1.48-dev
The following packages will be upgraded:
libboost-dev libboost-filesystem-dev libboost-iostreams-dev
libboost-program-options-dev libboost-python-dev libboost-regex-dev
libboost-system-dev
libboost-thread-dev
8 upgraded, 10 newly installed, 10 to remove and 0 not upgraded.
Need to get 11.0 MB of archives.
After this operation, 33.6 MB of additional disk space will be used.
Do you want to continue [Y/n]? n
Abort.
frankie@blegrez:~
$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
libboost-date-time1.48.0 libboost-python1.48.0 libboost-serialization1.48.0
<------ HERE
0 upgraded, 0 newly installed, 3 to remove and 8 not upgraded.
After this operation, 1873 kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 382338 files and directories currently installed.)
Removing libboost-date-time1.48.0 ...
Removing libboost-python1.48.0 ...
Removing libboost-serialization1.48.0 ...
frankie@blegrez:~
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
libboost-date-time1.48.0 libboost-python1.48.0 libboost-serialization1.48.0
The following packages have been kept back:
libboost-dev libboost-filesystem-dev libboost-iostreams-dev
libboost-program-options-dev libboost-python-dev libboost-regex-dev
libboost-system-dev
libboost-thread-dev
0 upgraded, 3 newly installed, 0 to remove and 8 not upgraded.
Need to get 0 B/614 kB of archives.
After this operation, 1873 kB of additional disk space will be used.
Do you want to continue [Y/n]?
[...]
Here dist-upgrade succeed.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Sun, Apr 01, 2012 at 08:23:46PM -0500, Steve M. Robbins wrote:
> I know version 1.48.0.2 suffered from bug #666239, which is now fixed.
> So the problem may be gone. I'd appreciate it if you could re-try and
> let me know if the problem still exists.
I have just verified that the upgrade from stable
(i.e. libboost-all-dev, version 1.42.0.1) upgrades properly to current
'sid'. Closing this bug.
-Steve
signature.asc
Description: Digital signature
--- End Message ---
