(Solved) Challenge ... What is this?

[VastOne]

In the build processes of VSIDO this is the most frustrating part...

Take a look at the dist-upgrade below

Where does these new packages come from? Why are these packages suddenly needed and were not before? ... These new packages (the 89.1 MB of additional disk space will be used) translates to a 20 MB raise in the ISO from 380 to 400MB... I would like to know why and get thoughts from the brilliant minds we have here

I think it is a transitional phase between kernels perhaps? ... Thoughts please! 

Code Select Expand

The following packages will be REMOVED:
  spacefm-common
The following NEW packages will be installed:
  gir1.2-gtk-2.0 libatk1.0-dev libcairo-script-interpreter2 libcairo2-dev
  libdrm-dev libegl1-mesa-dev libexpat1-dev libfontconfig1-dev
  libfreetype6-dev libgdk-pixbuf2.0-dev libgl1-mesa-dev libgtk2.0-dev
  libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0 libice-dev libicu52
  libpango1.0-dev libpixman-1-dev libpng12-dev libpthread-stubs0-dev libsm-dev
  libx11-dev libx11-doc libx11-xcb-dev libxau-dev libxcb-dri2-0-dev
  libxcb-glx0-dev libxcb-render0-dev libxcb-shm0-dev libxcb1-dev
  libxcomposite-dev libxcursor-dev libxdamage-dev libxdmcp-dev libxext-dev
  libxfixes-dev libxft-dev libxi-dev libxinerama-dev libxrandr-dev
  libxrender-dev libxxf86vm-dev mesa-common-dev x11proto-composite-dev
  x11proto-core-dev x11proto-damage-dev x11proto-dri2-dev x11proto-fixes-dev
  x11proto-gl-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev
  x11proto-render-dev x11proto-xext-dev x11proto-xf86vidmode-dev
  x11proto-xinerama-dev xorg-sgml-doctools xtrans-dev
The following packages will be upgraded:
  acpid autopoint base-passwd colord cpp cpp-4.8 dictionaries-common dpkg
  dpkg-dev ffmpeg g++ g++-4.8 gcc gcc-4.8 gcc-4.8-base gettext gettext-base
  libasan0 libasprintf-dev libasprintf0c2 libatomic1 libaudit-common libaudit1
  libav-tools libavcodec55 libavdevice55 libavfilter3 libavformat55
  libavresample1 libavutil52 libbluray1 libcolord1 libcolorhug1 libcups2
  libdpkg-perl libffi6 libgcc-4.8-dev libgcc1 libgettextpo-dev libgettextpo0
  libgfortran3 libgomp1 libio-socket-ssl-perl libitm1 libnss-mdns
  libpam-modules libpam-modules-bin libpam-runtime libpam0g libperl5.18
  libportaudio2 libpostproc52 libquadmath0 libstdc++-4.8-dev libstdc++6
  libswresample0 libswscale2 libthai-data libthai0 libtsan0 logrotate lynx
  lynx-cur manpages manpages-dev perl perl-base perl-modules spacefm sudo
70 upgraded, 59 newly installed, 1 to remove and 0 not upgraded.
Need to get 72.6 MB of archives.
After this operation, 89.1 MB of additional disk space will be used.
Do you want to continue? [Y/n]

[lwfitz]

My first question would be (and you probably checked this already), did all the repositories hit as they were supposed too? Or is an error there causing this error?

Why is spacefm being removed by dist-upgrade and not being reinstalled? I think it's a conspiracy.

[VastOne]

^ Yes ... I triple checked that, making sure there was nothing included or excluded

The spacefm-common is removed and replaced as the new one comes in for the build process of spacefm

[PackRat]

Looks like X may be in the process of getting upgraded.

There are a lot of -dev listed, do you build some apps from source that require those? Maybe dependencies for the spacefm build process?

[VastOne]

^ Yes, there are dependencies for spacefm, but they are always there ... nothing new is added for it.

It all looks like X things to me and I would think that once the upgrade is done, the older files will be safely removed then

[VastOne]

^^ Turns out you are right Rat Man...

I put a hold on spacefm and then reran the update with these results:

Code Select Expand

The following packages have been kept back:
  spacefm
The following packages will be upgraded:
  acpid autopoint base-passwd colord cpp cpp-4.8 dictionaries-common dpkg
  dpkg-dev ffmpeg g++ g++-4.8 gcc gcc-4.7-base gcc-4.8 gcc-4.8-base gettext
  gettext-base grep iceweasel libasan0 libasprintf-dev libasprintf0c2
  libatomic1 libaudit-common libaudit1 libav-tools libavcodec55 libavdevice55
  libavfilter3 libavformat55 libavresample1 libavutil52 libbluray1 libcolord1
  libcolorhug1 libcups2 libdpkg-perl libdvdnav4 libffi6 libgcc-4.8-dev libgcc1
  libgettextpo-dev libgettextpo0 libgfortran3 libgomp1 libio-socket-ip-perl
  libio-socket-ssl-perl libitm1 libmozjs28d libnet-ssleay-perl libnss-mdns
  libp11-kit0 libpam-modules libpam-modules-bin libpam-runtime libpam0g
  libperl5.18 libportaudio2 libpostproc52 libpython2.7 libpython2.7-minimal
  libpython2.7-stdlib libqt4-network libqt4-xml libqtcore4 libqtdbus4
  libqtgui4 libquadmath0 libraptor2-0 libsane libsane-common libselinux1
  libstdc++-4.8-dev libstdc++6 libswresample0 libswscale2 libthai-data
  libthai0 libtsan0 libv4l-0 libv4lconvert0 libwrap0 libxft2 libxmmsclient6
  logrotate lynx lynx-cur manpages manpages-dev nfs-common p11-kit perl
  perl-base perl-modules python2.7 python2.7-minimal qtcore4-l10n sane-utils
  sudo tcpd whois xulrunner-28
103 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 89.6 MB of archives.
After this operation, 2,255 kB of additional disk space will be used.
Do you want to continue? [Y/n]

I will look into getting the package from the debian repos as they become available... I am pretty sure there is a spacefm package built fairly quickly

I am marking this as closed

Appreciate all the help

[VastOne]

As a follow up to this, the spacefm 9.3 update hit the Debian SID repo approximately 48 hours after IgnorantGuru released it to his repo...

I can live with that!

[Digit]

apt-get autoremove

does that provide some remedy?