-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux Mint 17 fails update #63
Comments
@ShvonderSiN Even Customizer is no longer active in development, we can at least provide you a workaround (whenever possible). Without any useful information, we cannot do anything for you. If you want a help to solve this issue, please follow our submission guide. |
I myself did not understand seek help or is it just a comment. |
i'm not test with LinuxMint17, but have same problem with Ubuntu 14.04... (with host Ubuntu 12.10) in chroot before you run apt-get upgrade run this: and after apt-get upgrade finish unhold back with this before rebuild iso: if you plane use customized iso with preseeding installation, is also need hold kernel packages, hold before upgrade: unhold after upgrade: |
@k3dar same problem with ubuntu 14.04 32bit for me. solved with hold libpam-systemd befor upgrading but i made an experiment :) i tried to upgrade the same iso with ubuntu-builder without holding nothing and the process works fine and end fine...the problem seems to appear only with customizer (4.1 and 3.2.3 too) |
Which flavour of Linux Mint 17 are we talking about? What architecture? |
both linux mint 17 (32 and 64), same problem |
It's a packaging issue:
|
@fluxer but in your opinion why upgrading with ubuntu-builder there are not problems to do apt-get upgrade? using the same iso naturally... |
Gambas2 is not even available for Ubuntu 14.04 release so there is no |
ok thanks ;) |
as bad as this change can be, if /sbin/init is diverted upgrading packages that rely on initctl fail (e.g. systemd-services). On the other hand if initctl is not diverted host services may be affected from the chroot (upstart uses D-Bus, and access to it is granted for the nested X-session). Upstart has a container feature but I'm afraid to tell it that it is in container as it uses file in /run and /var/run (symlink to /run) is bind mounted for the nested X-session too. In any case, do not blame me when your host starts to behave strange after upgrading chroot.
crashes error about the update.. nothing helps, even synaptic, in the end, you can make a distro without updates...With the previous version Mint had no such problems.
The text was updated successfully, but these errors were encountered: