Problems with big December package update

Message

#11 Post by **Jerry3904** » Fri Dec 14, 2018 5:09 pm

We should be clear that the grub problem came from Debian's update, not MX's

#12 Post by **turtlebay777** » Fri Dec 14, 2018 5:10 pm

Wherever it came from it was forced on us.

#13 Post by **Adrian** » Fri Dec 14, 2018 5:46 pm

turtlebay777 wrote: ↑Fri Dec 14, 2018 5:10 pm Wherever it came from it was forced on us.

Nothing was forced on you, there's a reason we don't ship with automatic updates enabled by default, you probably set it up for automatic updates -- in my opinion it doesn't mean "forced on you" when you say "give me all automatically". If you did the update manually it's even less forced on you, you can choose to install an upgrade or not.

#14 Post by **Eadwine Rose** » Fri Dec 14, 2018 5:52 pm

Exactly.. I am one of those people who said Nuh uh!! when I saw the bunch coming at me. Knowing that at the end of the year a new MX comes out I decided to just hold off, and wait for the new release. So.. I just cherry pick right now (things like Chrome and such do get updated), and all the other 80some packages can stay nicely where they are *pat pat* and not update.

#15 Post by **Stevo** » Fri Dec 14, 2018 6:13 pm

We're also thinking about rolling the latest HPLIP 3.18.10 into the main repo in order to support newer HP printers out of the box, since the version we have now dates back to 2016. But those type of upgrades have been going smoothly in the past.

#16 Post by **fehlix** » Fri Dec 14, 2018 7:01 pm

turtlebay777 wrote: ↑Fri Dec 14, 2018 4:58 pm because after a previous disastrous bunch of updates - the one with the update of grub - I no longer do any updates.

Please do re-think you comments and wording: The grub-ugrade came with clearly displayed instructions and help-information what to do during the upgrade what the user shall do. Even navigation with tab-key for the cursor based dialog was explained. If a user does not read the instructions or does not understand the user should not blame others if something did not go well. User who have asked in the forum for help got explained what to do.
Thanks

#17 Post by **Eadwine Rose** » Fri Dec 14, 2018 7:04 pm

Fehlix: don't forget there were a number of users who upgraded before any of the instructions came out.

#18 Post by **richb** » Fri Dec 14, 2018 7:09 pm

Eadwine Rose wrote: ↑Fri Dec 14, 2018 7:04 pm Fehlix: don't forget there were a number of users who upgraded before any of the instructions came out.

True, but instructions for a fix was posted shortly thereafter.

#19 Post by **dolphin_oracle** » Fri Dec 14, 2018 7:13 pm

It was pretty tricky. We didnt' have any advance warning it was coming.

#20 Post by **newguy** » Fri Dec 14, 2018 7:23 pm

Stevo wrote: ↑Fri Dec 14, 2018 3:39 pm Whoops, we have 2.10.X compatible versions of gimp-plugin-registry and gimp-gmic in the test repo that we need to move to main.

Thanks for catching that!

Thank you, muchly. That will be a big help to my workflow.

MX Linux Forum

Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update

Re: Problems with big December package update