Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts

2020-08-15

Absurd dependencies

Writing something in texinfo, it happens that I can’t use @subentry for the index. It seems Ubuntu 19.10 has an old texinfo. So I downloaded the latest and wanted to purge the old one. But:

$ sudo apt-get remove texinfo
[sudo] password for user: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
...
The following packages will be REMOVED:
  cantor-backend-octave dynare liboctave-dev lilypond lilypond-data matlab2tikz octave octave-bim octave-biosig octave-bsltl
  octave-cgi octave-communications octave-communications-common octave-control octave-data-smoothing octave-dataframe octave-dicom
  octave-divand octave-doctest octave-econometrics octave-financial octave-fits octave-fpl octave-fuzzy-logic-toolkit octave-ga
  octave-gdf octave-general octave-geometry octave-gsl octave-image octave-image-acquisition octave-instrument-control octave-interval
  octave-io octave-level-set octave-linear-algebra octave-lssa octave-ltfat octave-ltfat-common octave-mapping octave-miscellaneous
  octave-missing-functions octave-mpi octave-msh octave-mvn octave-nan octave-ncarray octave-netcdf octave-nlopt octave-nurbs
  octave-octclip octave-octproj octave-openems octave-optics octave-optim octave-optiminterp octave-parallel octave-pfstools
  octave-plplot octave-psychtoolbox-3 octave-quaternion octave-queueing octave-secs1d octave-secs2d octave-secs3d octave-signal
  octave-sockets octave-sparsersb octave-specfun octave-splines octave-statistics octave-stk octave-strings octave-struct
  octave-symbolic octave-tsa octave-vibes octave-vlfeat octave-vrml octave-zenity octave-zeromq texinfo texlive-full

Why? Why removing texinfo should bring down the whole texlive-full and whole pieces of octave and… WTF. Idiotic, nonsense dependencies.

So I will keep that old texinfo. And Ubuntu has one more angle to push me towards their personal nightmare (I mean, snaps).

2020-05-10

Annoying Ubuntu

Ubuntu is getting more annoying. Recently — I can’t remember exactly when — I’ve got a forced update which could not be interrupted. Very microsoftwindowish.

Now, it’s trying to make me upgrade the system to Ubuntu 20.04 LTS. The LTS bit almost got me, so maybe I’ve a little bit of peace.

But it told me it could take several hours. This made me think and check what’s in this 20.04, codenamed Focal fossa.

And I decided to stop the process and well, think to switch again away from this canonical monster — it’s nice and everything, but I can’t stand this microsoftish attitude and, more importantly, the very concept of updating regularly a system experimenting “new” features which smell a little (snaps what?).

Then, the only update I expect is about bug fixes. Moreover, we don’t need to ride the versions-wave of every software, unless we need that very brand new feature it hadn’t or that didn’t work so well in the current version.

I’m starting to believe that the package system and its dependency handling is broken, after all. Not as “technology” per se, but because of how packages were created — I remember vaguely to have stumbled upon a package which wanted its documentation, and so I couldn’t install it without that unnecessary burden. Maybe I don’t remember well and the dependency wasn’t with the doc package… anyway a dependecy oddness of sort happened and pissed me off.

Now, Ubuntu 20.04 LTS, … codenamed Focal Fossa…

Please, STOP referring to Ubuntu versions using their code name!

This is one thing which is very annoying. Shame on all authors who like to do so. With a version number, I know what comes first and what comes later. With a silly name, I can’t.

So, please, stop referring to Ubuntu versions using their code name.

Snaps?

Ok, the trend is to use container, and whatever. Snaps look like that to me. Replacing the Debian packaging with these snap scares me. If I need containers, I think I would use docker — in fact I’ve installed it already. Normally, I don’t need snaps and all the new things needed to make them work.

It’s just crap. Moreover it is Canonical behaving like Microsoff, pushing a “new” technology which they made when other solutions already existed.

It is even worse than the introduction of that crappy thing which luckly died away; how did they call it? I think it was upstart. It had been talked about as if it were a great thing. It wasn’t.

Not that I am the “if it works, keep it” kind of guy all the time. But there are stupid attempts at innovation — innovation is the word used to say that there’s a change and to present that change as a good thing, when indeed nobody has really considered if it is good for the average of the users.

If then changes create new problems which need to be solved by experienced people, who are few because the “innovation” is new too, … well. Very few people — i.e., no one — need to have always the last version, the last software, the last innovation.

I think snaps’ destiny is to fail, but it will be harder to go back for adopters, and so that failure will survive longer than it could be.

My suggestion is to drop snaps: do not use them, hence do not use Ubuntu anymore until it will be back on its track.

Let me say it again:

Do not use Ubuntu anymore until they “park” snaps

About me… It is always hard to reinstall everything, to start over with a new distro — not all distro have all the packages, few programs could be missing… After years of “tuning”, it will be very upsetting. I fear the moment when it will be necessary: for now, I will continue to use Ubuntu 19.10 as I have it on my machine.

P.S.:

When I was about to upgrade I had also a list of package the upgrade would have removed. Among these now I remember only coccinelle.

Why they removed it?

Maybe I don’t need Coccinelle in particular, but there where hundreds of packages to be removed. Not supported anymore? Why? I don’t want to go and check what an upgrade will uninstall without a reason, and wonder why they decided to remove the package. If I have it on my system, I want it on my system also after upgrade. Linking problems with new library, nobody cared to recompile something successfully with the library versions? Make a static package with old library version, maybe — no, do not think about snaps to solve this.

Conclusion

Suggestion to abandon Ubuntu towards… Debian again? I installed Ubuntu in this new laptop of mine hoping for a better hardware support, in particular for the graphics card… but I could just hope in the latest nvidia driver, and that’s all — also considering that for most of the time I don’t use the nvidia card — also, last time I messed with prime, bublebee, and whatever, and now I can’t even remember if I can switch to the nvidia card successfully…

Another anti-snaps detail

Those shitty idiotic snaps are polluting the mount points, so that when I do mount, I get a list longer than it should be, in my case, even if I hadn’t upgraded, 26 snaps

26 snaps!

26 snaps were pushed in my throat without even being notified. There are gnome components, gtk-common, and few more thing, e.g. “core” which appears four times.

/var/lib/snapd/snaps/core18_1754.snap on /snap/core18/1754 ...
/var/lib/snapd/snaps/core_9066.snap on /snap/core/9066 ...
/var/lib/snapd/snaps/core_8935.snap on /snap/core/8935 ...
/var/lib/snapd/snaps/core18_1705.snap on /snap/core18/1705 ...

And those are polluting my mount result. And they are using /dev/loopN more than usual. And they appear also when I do df -h, so that I need to filter them out. This is more than simply annoying… I feel like I need to metaphorically head-bang the Canonical guys responsible for this.

Please, please, don’t tell me you like this. It also looks very microsofterish to me, again. They are ruining things, and to push a technology which already existed — thinking of flatpak, AppImage, and alike.

Snaps, go to heck.

2010-11-13

Drop a drop

Finally my badly over-tweaked "old" Mandriva's got wiped out by a fresh brand new Ubuntu 10.10. With the advent of a bit more of memory (from 256M to 1G!) I've decided to try again a full featured modern desktop and accept all the comforts of the defaults, though a little bit too much windowsish and even though accepting defaults is usually a bad idea. There will be time to tweak this system too and make it usable just by me...

In the meantime I was disappointed by a really annoying bug I've noticed while watching a flash video on YT. At first the guilty, to me, was the flash player... But soon I've discovered it was not. Submitted a bug report for "choppy audio", ... but recently I've realized it was not about it. The bug is bigger: the whole system is stuck "occasionally".

Today, I've timed the choppiness and surprise, it's very regular: one "stuck" every ten seconds. I've searched the net simply with "ubuntu stuck every ten seconds" and found this link very useful. Then I tried the nomodeset and woah now it is ok. On an Ubuntu wiki I've found how to disable permanently it by adding a file in /etc/modprobe.d containing simply an option for the i915 driver: options i915 modeset=0. Indeed I've not restarted the system yet... however, if the boot option worked, the permanent solution should too.

This is however still an annoying bug. I don't know if KMS is really good, but its problem with Intel chipset should be fixed.

Another thing I did on Mandriva was to kill the tslash from the key t, and put in its place the þ. I don't know way in the "latin" layout (type) for danish, norwegian (etc) the þ is where it should be, while otherwise it is bound graphically (instead of phonetically) to the p key.

After reading here and there about how to use xmodmap, and the .Xmodmap file in the home, I've decided to fix it my way, as I did in Mandriva: editing the file /usr/share/X11/xkb/symbols/latin (maybe on Mandriva was located elsewhere, I can't remember). Did it and now that I've mapped (this time using the provided configuration tool) the Menu key to the Multi key and the unuseful Windows key to Meta key, I feel better.

The next step will be to fix a bit Nautilus: I don't like the Windows-like behaviour when you double-click on files it "does not know". I was used to be able to open all files (known or not) with a text editor (Emacs usually) or an hex editor (ghex2), but it seems that I have to pass to the "windows-steps" to do it: if a filetype is unknown, pick a program from a list, remember the association (no, never!) and of course if the file is "known", the context menu will show the item to open it with the program that "understands" it. It can be ok, but I want also always the items to open it with an editor (text and hex). How do I do it?

From the packages point of view, I was able to install everything I needed; in particular I was worried about interpreters/compilers I had installed on Mandriva. Luckly I was able to install maybe all what I had, from C (of course!) to Algol 68 Genie, with apt-get or compiling it (MMIX, MMIXX and Algol 68G only, currently, while the rest was all found in .debs in the repo or on the net). Rebol being proprietary is still not installed, but I will; and also fasm (flat assembler) is missing (but of course there's nasm).