Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: vilde on 2014/04/13, 11:00:14
-
On d-u today sidu-base causes problem. sorry for not being able to exactly tell what happen, but doing d-u init 3 makes me not being able to copy what happen.
Anyway, I did apt-get -f install and then apt-get dist-upgrade again, failed, so I removed sidu-base and then sidu-manual and sidu-disc-center and one more package was removed.
Then d-u and again it failed, apt-get -f install, failed because of missing sidu-base
I Installed sidu-base, sidu-manual and sidu-disc-center , the "one more package" which was removed above was also pulled in by apt
d-u again and now it worked
(xfce 32 bit)
-
sidu-base here also gave an error but I just did "apt-get install sidu-base" and everything was ok. I don't have sidu-disk-center and sidu-manual installed.
-
there was a heavy rebuild of sidu-base, we had short sidu-base-systemd introduced. it may be that we should add a some breaks/replaces - we will look at the code todays evening. If someone can provide a _full_ output, we would be happy.
-
Here is what mine said:
Preparing to unpack .../sidu-base_2014.04.13_all.deb ...
Unpacking sidu-base (2014.04.13) over (2014.04.10) ...
dpkg: error processing archive /var/cache/apt/archives/sidu-base_2014.04.13_all.deb (--unpack):
trying to overwrite '/etc/sudoers.d/sidu-control', which is also in package pywwetha 2014.04.10
Preparing to unpack .../sidu-manual-data_2014.04.11_all.deb ...
Unpacking sidu-manual-data (2014.04.11) over (2014.04.10) ...
Processing triggers for udev (204-8) ...
Processing triggers for initramfs-tools (0.115) ...
update-initramfs: Generating /boot/initrd.img-3.14-0.towo.4-siduction-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for siduction-dynamic-dms (0.3) ...
Errors were encountered while processing:
/var/cache/apt/archives/sidu-base_2014.04.13_all.deb
Tim
-
I am getting similar error as timc, on both of my siduction installations.
Preparing to unpack .../sidu-base_2014.04.12_all.deb ...
Unpacking sidu-base (2014.04.12) over (2014.04.07) ...
dpkg: error processing archive /var/cache/apt/archives/sidu-base_2014.04.12_all.deb (--unpack):
trying to overwrite '/etc/bin/sidu-control', which is also in package pywwetha 2014.04.10
Can I assume removing the pywwetha package will resolve the issue? I am hesitant to do that because I am not sure what it does.
-
Here's what /var/log/dpkg.log says:
2014-04-13 15:25:53 status unpacked ntfs-3g:amd64 1:2014.2.15AR.1-1
2014-04-13 15:25:54 upgrade sidu-base:all 2014.04.07 2014.04.13
2014-04-13 15:25:54 status half-configured sidu-base:all 2014.04.07
2014-04-13 15:25:54 status unpacked sidu-base:all 2014.04.07
2014-04-13 15:25:54 status half-installed sidu-base:all 2014.04.07
2014-04-13 15:25:54 status half-installed sidu-base:all 2014.04.07
2014-04-13 15:25:54 status unpacked sidu-base:all 2014.04.07
2014-04-13 15:25:54 status triggers-awaited sidu-base:all 2014.04.07
2014-04-13 15:25:54 upgrade sidu-manual-data:all 2014.03.07 2014.04.11
2014-04-13 15:25:54 status half-configured sidu-manual-data:all 2014.03.07
2014-04-13 15:25:54 status unpacked sidu-manual-data:all 2014.03.07
2014-04-13 15:25:54 status half-installed sidu-manual-data:all 2014.03.07
2014-04-13 15:25:55 status half-installed sidu-manual-data:all 2014.03.07
2014-04-13 15:25:55 status unpacked sidu-manual-data:all 2014.04.11
2014-04-13 15:25:55 status unpacked sidu-manual-data:all 2014.04.11
2014-04-13 15:25:55 trigproc man-db:amd64 2.6.7.1-1 2.6.7.1-1
2014-04-13 15:25:55 status half-configured man-db:amd64 2.6.7.1-1
2014-04-13 15:25:57 status installed man-db:amd64 2.6.7.1-1
The log at /var/log/apt/history.log only shows that dpkg returned an error code (1).
-
just wait or take a german mirror - we think that the problem is solved with
* pywwetha 2014.04.12
* sidu-base 2014.04.13
if not, please use a paste service an provide a link to the log. Thanks
-
just wait or take a german mirror - we think that the problem is solved with
* pywwetha 2014.04.12
* sidu-base 2014.04.13
if not, please use a paste service an provide a link to the log. Thanks
I dis a d-u now and among some others the above packages installed without problems.
Can someone explain to me how to supply a report of from a d-u I have done in init 3 so I can provide a better and more useful information next time if I find something wrong?
-
On my system, just a couple of minutes ago: http://pastie.org/9078340
It says it is installing sidu-base all 2014.04.13 and pywwetha all 2014.04.12
Tim
-
Same here but I still could not dist-upgrade, it would complain. So I had to do the following, first manually try to update pywwetha, and that would throw up and error that was fixed by doing a -f install, and that installed sidu-base. Once that was out of the way I could finish up the d-u.
apt-get install pywwetha
apt-get -f install
-
ok, in that case the break was not forceful enough, i will change that today evening into a conflict.