Hi Tsu Jan, inkscape can be installed in sid without any issues:
# apt update Hit http://http.debian.net sid InRelease Hit http://http.debian.net sid/main Sources Hit http://http.debian.net sid/main amd64 Packages Hit http://http.debian.net sid/main Translation-en Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. # apt install inkscape Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: gawk gconf-service gconf2 gconf2-common gnome-mime-data libatkmm-1.6-1v5 libavahi-glib1 libcairomm-1.0-1v5 libcdr-0.1-1 libgc1c2 libgconf-2-4 libglibmm-2.4-1v5 libgnomevfs2-0 libgnomevfs2-common libgnomevfs2-extra libgsl0ldbl libgtkmm-2.4-1v5 libgtkspell0 libimage-magick-perl libimage-magick-q16-perl libpangomm-1.4-1v5 libperl5.20 libpoppler-glib8 librevenge-0.0-0 libsigsegv2 libvisio-0.1-1 libwmf-bin libwpd-0.10-10 libwpg-0.3-3 python-bs4 python-lxml transfig Suggested packages: gawk-doc gconf-defaults-service dia dia-gnome libsvg-perl libxml-xql-perl python-uniconvertor libgnomevfs2-bin gsl-ref-psdoc gsl-doc-pdf gsl-doc-info gsl-ref-html imagemagick-doc python-lxml-dbg python-lxml-doc xfig The following NEW packages will be installed: gawk gconf-service gconf2 gconf2-common gnome-mime-data inkscape libatkmm-1.6-1v5 libavahi-glib1 libcairomm-1.0-1v5 libcdr-0.1-1 libgc1c2 libgconf-2-4 libglibmm-2.4-1v5 libgnomevfs2-0 libgnomevfs2-common libgnomevfs2-extra libgsl0ldbl libgtkmm-2.4-1v5 libgtkspell0 libimage-magick-perl libimage-magick-q16-perl libpangomm-1.4-1v5 libperl5.20 libpoppler-glib8 librevenge-0.0-0 libsigsegv2 libvisio-0.1-1 libwmf-bin libwpd-0.10-10 libwpg-0.3-3 python-bs4 python-lxml transfig 0 upgraded, 33 newly installed, 0 to remove and 0 not upgraded. Need to get 20.2 MB/27.4 MB of archives. After this operation, 151 MB of additional disk space will be used. Do you want to continue? [Y/n] That you currently cannot do so indicates that you have packages installed that you should not have installed. * Have you done an upgrade and dist-upgrade recently? * Have you taken the opportunity to remove packages that are no longer installable? There's a chance that you have old libraries around that you no longer need. (apt-get autoremove can help with this). * Have you actually removed the packages from deb-multimedia? You said earlier that you removed that entry from your sources.list but that is not the same thing as removing the problematic packages. The output of "aptitude search ~o" or "aptitude search ~Vdmo" might help find them. > If this is a real question, you could ask Manjaro's maintainers. The > same "transition" happened there and I didn't even notice it. Not a > single broken package! Or is Manjaro sh*t too, as Matteo believed about > deb-multimedia.org? This is precisely the sort of problems that having packages from deb- multimedia.org installed causes. (Those packages are also good at causing random crashes that are very hard to debug -- it's not hard to see why maintainers aren't interested in bug reports from systems that have these packages installed). cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
