I will wait until the official instructions to update will be available. We must be patient...woodsman wrote: More than a month since the official LMDE 2 ISO release, pushing three weeks since Jessie was released, and no official LMDE 1 update path.
So it breaks right after you run this ^ command?woodsman wrote:I am still stuck running apt-get -f install like this:
Code: Select all
apt-get install sysvinit-core adwaita-icon-theme libgtk-3-0 libgtk-3-bin libgtk-3-common
Clem almost finished the official tutorial. I'm sending him the feedback from this thread and from my own upgrade experience.xfrank wrote:I will wait until the official instructions to update will be available. We must be patient...woodsman wrote: More than a month since the official LMDE 2 ISO release, pushing three weeks since Jessie was released, and no official LMDE 1 update path.
Since last summer I think LMDE users have been more than patient.We must be patient...
Yes, I am instructed by apt to use apt-get -f dist-upgrade, which fails to complete fully with the infamous libgtk-3-common dependency breakage. I always end up needing to run apt-get -f install.So it breaks right after you run this ^ command?
While I have been long prepared for that, the people I support are perturbed the update is not point-and-click and requires my help.I can already tell you the official upgrade path will be quite similar to what me and woodsman posted here.
The official tutorial should be posted somewhere so we can beta test. As I mentioned previously, I suspect one or more of the additional apps I have installed is causing some kind of edge case breakage that a stock LMDE 1 install doesn't see.If we won't be able to solve it in a few days we'll just post the official tutorial as is and add the note about using "apt install -f" if the upgrade breaks.
Glad I didn't wait - I've been running a fully updated LMDE2 for several weeks now.axisofevil wrote:Well - I gave up.
I installed LMDE2 over / (and used my separate /home directory).
It appeared to go well (NOT)!!!!!!!!!!!
The install appeared to treat my /home very well - but
It appeared to attempt to set up GRUB to boot to a 32 bit partition as a MBR boot!!
(It should have done a 64 bit UEFI boot).
Obviously a failed boot ensued.
Luckily I had a super-boot DVD to hand.
This allowed me to boot into LMDE2 successfully.
I then ran these commands:-I then rebooted and all was well.Code: Select all
sudo apt-get install --reinstall grub-efi sudo update-grub
I am now loading several hundred extra packages...
Thanks for all your work on this Monsta. I've decided to wait for the offical tutorial also, but am not surprised it's similar to what has been discussed here.Monsta wrote:Clem almost finished the official tutorial. I'm sending him the feedback from this thread and from my own upgrade experience.xfrank wrote:I will wait until the official instructions to update will be available. We must be patient...woodsman wrote: More than a month since the official LMDE 2 ISO release, pushing three weeks since Jessie was released, and no official LMDE 1 update path.
I can already tell you the official upgrade path will be quite similar to what me and woodsman posted here.
Basically, what holds us back is the weird breakage that woodsman still gets. If we won't be able to solve it in a few days we'll just post the official tutorial as is and add the note about using "apt install -f" if the upgrade breaks.
Can you explain more what that means? What are package actualizations?py-thon wrote:I hope LMDE-users will also be warned in the tutorial that LMDE 2 contains a constrained Synaptic (package actualizations are not possible) and tell them how to get the full functionality back.
Maybe they are simply called updates in english, I don't know. It means to replace an installed package with its current (more recent) version.cb474 wrote:What are package actualizations?
That topic was discussed earlier in this thread.To make things worse the former (i.e. LMDE's) possibility to tell mintupdate to wait x seconds after startup before checking for available updates
I support people who do not use their computers much. The changes in the Updater design affects them. These users do not have high speed connections, about 1 Mbps max. They have bandwidth caps, although I doubt any of them come close to reaching those caps. I am resolving the problem by leaving the Updater set to check every 24 hours but in rc.local run an apt-get update, delayed by 5 minutes. The Updater's new design indicates that developers presume users have a 24/7 high speed connection and no bandwidth caps. The previous design made more sense. I do not understand the obsession to check for updates more than once every 24 hours. 
Why wouldn't you be more complete and explain also why it was removed?py-thon wrote: LMDE 2 has taken away the update/actualization functionality. You can only use Synaptic to check what packages are available/installed and to install or uninstall packages.
Thanks for the explanation. That does seem odd for Synaptic to be limited in that way. I wonder if that was a deliberate change or a bug. Perhaps you should file a bug report on that.py-thon wrote:Maybe they are simply called updates in english, I don't know. It means to replace an installed package with its current (more recent) version.cb474 wrote:What are package actualizations?
The most important positions in Synaptic's context menu for packages are to mark for "install", "update", "uninstall", "complete uninstall" (probably the correct english wording is slightly different). LMDE 2 has taken away the update/actualization functionality. You can only use Synaptic to check what packages are available/installed and to install or uninstall packages.
To make things worse the former (i.e. LMDE's) possibility to tell mintupdate to wait x seconds after startup before checking for available updates (for those people who are not constantly online) is no longer existent (at least I didn't find it anymore in mintupdate's GUI), so you have to trigger the repository check manually or set the frequency at short intervals (default is 30 minutes, which in my opinion is a stupid setting for a distribution based on Debian Stable and an expensive setting for those using mobile connections).
http://forums.linuxmint.com/viewtopic.p ... 73#p872138cb474 wrote:Thanks for the explanation. That does seem odd for Synaptic to be limited in that way. I wonder if that was a deliberate change or a bug. Perhaps you should file a bug report on that.
Can you post the full apt-get output - from the start to the breakage?woodsman wrote:Yes, I am instructed by apt to use apt-get -f dist-upgrade, which fails to complete fully with the infamous libgtk-3-common dependency breakage. I always end up needing to run apt-get -f install.So it breaks right after you run this ^ command?
Default should be keep. The default answer is No (keep, not replace). And that's what you should answer.mike77 wrote: On the few occasions I was asked whether or not I wanted to overwrite certain files, I accepted the default (overwrite), no problems there.
Yes, you're right, and I was talking rubbishkiller de bug wrote:Default should be keep. The default answer is No (keep, not replace). And that's what you should answer.mike77 wrote: On the few occasions I was asked whether or not I wanted to overwrite certain files, I accepted the default (overwrite), no problems there.
