FreeBSD Foundation Flounders on 15 with Rust, pkgbase, and KDE

Crivens said:
Ahh, you were a cat in your last life? Pushing things ever closer to the edge?

Enough with the Klaus Kinsky channeling.
Click to expand...
Sorry, I didn't meant to provoke you, but trying to make a (bad) joke for you, not on you.
You just seemed to be really pissed, which I can understand, and I thought you might could use a laugh.
Was an error of judgement. Bad choice of words.
Sorry.

To me the overall point of this thread is open to question anyway, especially since the topic was changed, what happened pretty early. But that's not up to me to judge, of course.
Anyway I didn't wanted to participate here in the first place, stopped following it at the second page, and after reading the last couple of posts after I saw your post, to me I seem to be right nothing constructive seems to happen here. But however of course again that's not up to me to judge.
So, I'm out of here.
 
Maturin said:
Sorry, I didn't meant to provoke you, but trying to make a (bad) joke for you, not on you.
Click to expand...
You see, this thread pops up in the "reported items" queue lately, and when it's Sunday morning 6AM when you try to get breakfast going before the kids start roaming around - this is not what you want to spend time on. Yes, I was pissed. And I am not among those who laugh at some final solution. Neither should you, or anyone.

And with that, everyone carry on.
 
RetroComputingCollector said:
What's so concerning is that developers want the installer to install games.
Click to expand...
Its not they specifically want to install games, they basically want to go *back* to the 2012 sysinstall approach so that arbitary packages can be listed and installed at install-time.

It seems a bit pointless personally. Install-time is for getting a basic system up and running, ready to be customized in post install. This is why Windows and macOS don't list every piece of software during the installer.

Linux Distros only do this because they *are* an arbitrary package list by definition. I suspect the two companies behind the FreeBSD Foundation are getting a little muddled in their planning discussions to bring in more users (customers).
 
fmc000 said:
I tend to agree on this despite the second part of the sentence.
Click to expand...
To clarify, I meant optional software that is part of i.e Windows. Not *every* bit of 3rd party software available (that would be impractical).

As an example, you don't see the following list during the installer:

enable_role_upd.png
 
First post here, so a little background: I co-owned a small ISP back in the 90s offering web hosting and colocation as well as dialup and dsl services. I sold my share at the peak of the dot com bubble and went to grad school- now I play with lasers for a living. My homelab (if you could call it that) is in terrible shape... I've just been throwing Microsoft solutions I got for free via MSDNAA at every problem, and my setup is terrible, now.

Kids moving out and going to college has left me with more free time, so I'm burning everything to the ground (not the hardware) and starting fresh. Looking at my options, I have many- Truenas if I don't want to think very hard, Linux if I want a dizzying array of options that all turn out to be kind of the same, or a BSD variant.

FreeBSD won the argument, for now, mostly due to nostalgia. I'm slowly getting back some of my atrophied skills as I make the switch. Getting to the point I'd like to make with this thread- FreeBSD (and the other BSD variants, as far as I can tell) suffers from a lack of approachability. Yes, the handbook exists, but it's dense and not all that helpful to a layperson without a reasonably high level of technical background. Similarly, the forums are full of conversations that offer useful tips, but there's a distinct lack of authoritative how-to articles tailored to a non-expert audience.

Linux, for all its faults and philosophical shortcomings, does have a much lower bar for entry. Noob-focused distros abound, and some even offer entry-level docs that are somewhat helpful (not complete, but helpful). FreeBSD making moves to close this gap seems like a good idea. Since writing for a general audience is perhaps the hardest type of writing, it's easier to cheat- offer a graphical environment during install, and new users can try FreeBSD on a more equal footing with Linux. Freebsd-update is an advantage that shouldn't be abandoned...

In short, approachability could be achieved with more noob-oriented docs and guides (hard to do), or by making the system install to something more familiar and competitive with most Linux distros. Want to attract more developers? Get more users. Want more users? Get off the mountain top and mingle a bit- the unix philosophy doesn't need to be sacrificed, but some change is needed. It's easy to see why the proposed changes are there, and I think they might even make sense.
 
kpedersen said:
Its not they specifically want to install games, they basically want to go *back* to the 2012 sysinstall approach so that arbitary packages can be listed and installed at install-time.
Click to expand...
I vote yes for this at install time personally. I don't see any reason to not offer this.
 
In all honesty, I think that NCurses is not a bad toolkit for programming the installer in. Every single step, every screen can be done with NCurses, and it can actually imitate the functionality of of graphical installers pretty well.

FreeBSD's installer doesn't have every single step written in NCurses, some end up dropping into the shell. And in that regard, I think it would be nice if they could finish that installer, and have every single step implemented with NCurses.

I mean, bsdconfig is not bad, just feels like an unfinished product at times. Just follow the BSD logic and order, except that NCurses will be there to help a newbie.

After all, there's almost no limit to what you can get NCurses to do - all within a CLI.
 
astyle said:
In all honesty, I think that NCurses is not a bad toolkit for programming the installer in. Every single step, every screen can be done with NCurses, and it can actually imitate the functionality of of graphical installers pretty well.

FreeBSD's installer doesn't have every single step written in NCurses, some end up dropping into the shell. And in that regard, I think it would be nice if they could finish that installer, and have every single step implemented with NCurses.

I mean, bsdconfig is not bad, just feels like an unfinished product at times. Just follow the BSD logic and order, except that NCurses will be there to help a newbie.

After all, there's almost no limit to what you can get NCurses to do - all within a CLI.
Click to expand...
I've had issues where going back to change previous install settings on bsdinstall with ncurses, it was requiring reboot or fresh start of bsdinstall.

I don't say it's bad but I don't think there's a need for that, i think current way to dropping to shell is good so you know you should be careful from there.

I don't think we should derail from current freebsd philosopy/unix philosopy just to bring some newbies here. I think that FreeBSD is a professional OS for professionals and/or experienced users like someone from here said, I agree with them.
 
cracauer@ said:
You never had a Debian installation commit suicide in unresolvable dependency messups?
Click to expand...
I never had THAT happen to me - well, that's because I never ran Debian in the first place... but 'unresolvable dependency messup suicide' happens in FreeBSD, as well - esp. if the graphics stack is involved.
 
astyle said:
I never had THAT happen to me - well, that's because I never ran Debian in the first place... but 'unresolvable dependency messup suicide' happens in FreeBSD, as well - esp. if the graphics stack is involved.
Click to expand...

Yes, but in FreeBSD you can just blow away all packages and you have a system left that boots and can install packages from scratch.

In Debian you can't just delete everything as there would be nothing left to start over without reinstalling.
 
cracauer@ said:
Yes, but in FreeBSD you can just blow away all packages and you have a system left that boots and can install packages from scratch.

In Debian you can't just delete everything as there would be nothing left to start over without reinstalling.
Click to expand...
cracauer@ said:
You never had a Debian installation commit suicide in unresolvable dependency messups?
Click to expand...
I had a similar experience with Fedora several years ago. To this day I am always hesitant to do package upgrades on Linux based systems. Especially now a days when you rarely have physical access to the system and the system is just some software running on someone else's hypervisor you have no console access to. It's one of the many reason's I would never keep anything of value on a Linux system.
 
tuaris said:
I had a similar experience with Fedora several years ago. To this day I am always hesitant to do package upgrades on Linux based systems. Especially now a days when you rarely have physical access to the system and the system is just some software running on someone else's hypervisor you have no console access to. It's one of the many reason's I would never keep anything of value on a Linux system.
Click to expand...
Strong argument for investing some time and effort into setting up a backup system that is actually convenient for you to use.
 
The current state pkg just doesn't exactly give the feeling of confidence that's required to manage the base system when you run into stuff like this

Code: 
root@pandora:~ # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01
Fetching data.pkg: 100%   30 KiB  30.8kB/s    00:01
Processing entries: 100%
FreeBSD-kmods repository update completed. 209 packages processed.
Updating Serviio repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01
Fetching data.pkg: 100%  104 KiB 106.5kB/s    00:01
Processing entries: 100%
Serviio repository update completed. 300 packages processed.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pkg: 1.21.3 -> 2.2.2 [FreeBSD]

Number of packages to be upgraded: 1

12 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/1] Fetching pkg-2.2.2.pkg: 100%   12 MiB   2.5MB/s    00:05
Checking integrity... done (0 conflicting)
[1/1] Upgrading pkg from 1.21.3 to 2.2.2...
[1/1] Extracting pkg-2.2.2: 100%
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
FreeBSD-kmods repository is up to date.
Updating Serviio repository catalogue...
Serviio repository is up to date.
All repositories are up to date.
Checking for upgrades (250 candidates): 100%
Processing candidates (250 candidates): 100%
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
pkg: Cannot solve problem using SAT solver
require rule: package ImageMagick6(r) depends on a requirement provided by: libxml2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libwmf(l)libwmf(r)libwmf-nox11(r)libwmf(l)libwmf(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: tiff(l)tiff(r)tiff(r)tiff(l)tiff(r)tiff(r)tiff(l)tiff(r)tiff(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: librsvg2-rust(l)librsvg2-rust(r)librsvg2(r)librsvg2-rust(l)librsvg2-rust(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libraw(l)libraw(r)libraw(l)libraw(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libraqm(l)libraqm(r)libraqm(l)libraqm(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: png(l)png(r)png(r)png(l)png(r)png(r)png(l)png(r)png(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: perl5(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: openjpeg(l)openjpeg(r)openjpeg(l)openjpeg(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libltdl(l)libltdl(r)libltdl(l)libltdl(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: liblqr-1(l)liblqr-1(r)liblqr-1(l)liblqr-1(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: jpeg-turbo(l)jpeg-turbo(r)jpeg-turbo(r)mozjpeg(r)jpeg-turbo(l)jpeg-turbo(r)jp                                                                                    eg-turbo(r)jpeg-turbo(l)jpeg-turbo(r)jpeg-turbo(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: jbigkit(l)jbigkit(r)jbigkit(r)jbigkit(l)jbigkit(r)jbigkit(r)jbigkit(l)jbigkit                                                                                    (r)jbigkit(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: gettext-runtime(l)gettext-runtime(r)gettext-runtime(r)gettext-runtime(l)gette                                                                                    xt-runtime(r)gettext-runtime(r)gettext-runtime(l)gettext-runtime(r)gettext-runtime(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libheif(l)libheif(r)libheif(l)libheif(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: glib(l)glib(r)glib(r)glib(l)glib(r)glib(r)glib-bootstrap(r)glib-bootstrap(r)g                                                                                    lib-bootstrap(r)glib-bootstrap(r)glib(l)glib(r)glib(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: glib(l)glib(r)glib(r)glib(l)glib(r)glib(r)glib-bootstrap(r)glib-bootstrap(r)g                                                                                    lib-bootstrap(r)glib-bootstrap(r)glib(l)glib(r)glib(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: glib(l)glib(r)glib(r)glib(l)glib(r)glib(r)glib-bootstrap(r)glib-bootstrap(r)g                                                                                    lib-bootstrap(r)glib-bootstrap(r)glib(l)glib(r)glib(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: gdk-pixbuf2(l)gdk-pixbuf2(r)gdk-pixbuf2(r)gdk-pixbuf2(l)gdk-pixbuf2(r)gdk-pix                                                                                    buf2(r)gdk-pixbuf2(l)gdk-pixbuf2(r)gdk-pixbuf2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: freetype2(l)freetype2(r)freetype2(r)freetype2(l)freetype2(r)freetype2(r)freet                                                                                    ype2(l)freetype2(r)freetype2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: fontconfig(l)fontconfig(r)fontconfig(r)fontconfig(l)fontconfig(r)fontconfig(r                                                                                    )fontconfig(l)fontconfig(r)fontconfig(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: fftw3(l)fftw3(r)fftw3(l)fftw3(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: cairo(l)cairo(r)cairo(l)cairo(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libXt(l)libXt(r)libXt(r)libXt(l)libXt(r)libXt(r)libXt(l)libXt(r)libXt(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libXext(l)libXext(r)libXext(r)libXext(l)libXext(r)libXext(r)libXext(l)libXext                                                                                    (r)libXext(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libX11(l)libX11(r)libX11(r)libX11(l)libX11(r)libX11(r)libX11(l)libX11(r)libX1                                                                                    1(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libSM(l)libSM(r)libSM(r)libSM(l)libSM(r)libSM(r)libSM(l)libSM(r)libSM(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libICE(l)libICE(r)libICE(r)libICE(l)libICE(r)libICE(r)libICE(l)libICE(r)libIC                                                                                    E(r)
upgrade rule: upgrade local ImageMagick6-6.9.12.77_9,1 to remote ImageMagick6-6.9.13.23_2,1
cannot install package ImageMagick6, remove it from request? [Y/n]:
 
tuaris said:
The current state pkg just doesn't exactly give the feeling of confidence that's required to manage the base system when you run into stuff like this

Code: 
root@pandora:~ # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01
Fetching data.pkg: 100%   30 KiB  30.8kB/s    00:01
Processing entries: 100%
FreeBSD-kmods repository update completed. 209 packages processed.
Updating Serviio repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01
Fetching data.pkg: 100%  104 KiB 106.5kB/s    00:01
Processing entries: 100%
Serviio repository update completed. 300 packages processed.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pkg: 1.21.3 -> 2.2.2 [FreeBSD]

Number of packages to be upgraded: 1

12 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/1] Fetching pkg-2.2.2.pkg: 100%   12 MiB   2.5MB/s    00:05
Checking integrity... done (0 conflicting)
[1/1] Upgrading pkg from 1.21.3 to 2.2.2...
[1/1] Extracting pkg-2.2.2: 100%
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating FreeBSD-kmods repository catalogue...
FreeBSD-kmods repository is up to date.
Updating Serviio repository catalogue...
Serviio repository is up to date.
All repositories are up to date.
Checking for upgrades (250 candidates): 100%
Processing candidates (250 candidates): 100%
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
Cannot solve problem using SAT solver, trying another plan
pkg: Cannot solve problem using SAT solver
require rule: package ImageMagick6(r) depends on a requirement provided by: libxml2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libwmf(l)libwmf(r)libwmf-nox11(r)libwmf(l)libwmf(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)webp(l)webp(r)webp(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: tiff(l)tiff(r)tiff(r)tiff(l)tiff(r)tiff(r)tiff(l)tiff(r)tiff(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: librsvg2-rust(l)librsvg2-rust(r)librsvg2(r)librsvg2-rust(l)librsvg2-rust(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libraw(l)libraw(r)libraw(l)libraw(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libraqm(l)libraqm(r)libraqm(l)libraqm(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: png(l)png(r)png(r)png(l)png(r)png(r)png(l)png(r)png(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: perl5(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: openjpeg(l)openjpeg(r)openjpeg(l)openjpeg(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libltdl(l)libltdl(r)libltdl(l)libltdl(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: liblqr-1(l)liblqr-1(r)liblqr-1(l)liblqr-1(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)lcms2(l)lcms2(r)lcms2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: jpeg-turbo(l)jpeg-turbo(r)jpeg-turbo(r)mozjpeg(r)jpeg-turbo(l)jpeg-turbo(r)jp                                                                                    eg-turbo(r)jpeg-turbo(l)jpeg-turbo(r)jpeg-turbo(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: jbigkit(l)jbigkit(r)jbigkit(r)jbigkit(l)jbigkit(r)jbigkit(r)jbigkit(l)jbigkit                                                                                    (r)jbigkit(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: gettext-runtime(l)gettext-runtime(r)gettext-runtime(r)gettext-runtime(l)gette                                                                                    xt-runtime(r)gettext-runtime(r)gettext-runtime(l)gettext-runtime(r)gettext-runtime(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libheif(l)libheif(r)libheif(l)libheif(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: glib(l)glib(r)glib(r)glib(l)glib(r)glib(r)glib-bootstrap(r)glib-bootstrap(r)g                                                                                    lib-bootstrap(r)glib-bootstrap(r)glib(l)glib(r)glib(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: glib(l)glib(r)glib(r)glib(l)glib(r)glib(r)glib-bootstrap(r)glib-bootstrap(r)g                                                                                    lib-bootstrap(r)glib-bootstrap(r)glib(l)glib(r)glib(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: glib(l)glib(r)glib(r)glib(l)glib(r)glib(r)glib-bootstrap(r)glib-bootstrap(r)g                                                                                    lib-bootstrap(r)glib-bootstrap(r)glib(l)glib(r)glib(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: gdk-pixbuf2(l)gdk-pixbuf2(r)gdk-pixbuf2(r)gdk-pixbuf2(l)gdk-pixbuf2(r)gdk-pix                                                                                    buf2(r)gdk-pixbuf2(l)gdk-pixbuf2(r)gdk-pixbuf2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: freetype2(l)freetype2(r)freetype2(r)freetype2(l)freetype2(r)freetype2(r)freet                                                                                    ype2(l)freetype2(r)freetype2(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: fontconfig(l)fontconfig(r)fontconfig(r)fontconfig(l)fontconfig(r)fontconfig(r                                                                                    )fontconfig(l)fontconfig(r)fontconfig(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: fftw3(l)fftw3(r)fftw3(l)fftw3(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: cairo(l)cairo(r)cairo(l)cairo(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libXt(l)libXt(r)libXt(r)libXt(l)libXt(r)libXt(r)libXt(l)libXt(r)libXt(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libXext(l)libXext(r)libXext(r)libXext(l)libXext(r)libXext(r)libXext(l)libXext                                                                                    (r)libXext(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libX11(l)libX11(r)libX11(r)libX11(l)libX11(r)libX11(r)libX11(l)libX11(r)libX1                                                                                    1(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libSM(l)libSM(r)libSM(r)libSM(l)libSM(r)libSM(r)libSM(l)libSM(r)libSM(r)
require rule: package ImageMagick6(r) depends on a requirement provided by: libICE(l)libICE(r)libICE(r)libICE(l)libICE(r)libICE(r)libICE(l)libICE(r)libIC                                                                                    E(r)
upgrade rule: upgrade local ImageMagick6-6.9.12.77_9,1 to remote ImageMagick6-6.9.13.23_2,1
cannot install package ImageMagick6, remove it from request? [Y/n]:
Click to expand...
Just use ports. I recently had a case where the base system had a more recent version of a lib than what the packages were looking for - and that messed up the graphics stack for me. Symlinking appropriately-named libs did not help in my case. And I'm not looking for help, this is more of a PSA...
 
You must log in or register to reply here.
Back
Top