Re: systemd-nspawn and /run/resolvconf/resolv.conf
On Sun, Sep 20, 2015 at 1:11 PM, Ralf Mardorf wrote: > > by default Wily's /etc/resolv.conf is a link against > ../run/resolvconf/resolv.conf. If you want to maintain Wily from another > install in a systemd-nspawn container, the link needs to be replaced by a > file /etc/resolv.conf. Since Wily is based on systemd by itself, it IMO > should care about systemd-nspawn compatibility and by default not link > against /run. > > Assumed nobody should be aware about a reason that a link is a better > solution, I would report it as a bug. If you were to set up the "full systemd upstream experience", you'd be using systemd-resolved and "/etc/resolv.conf" would be a symlink to "/run/systemd/resolve/resolv.conf", so there's no reason why Ubuntu's default resolvconf setup shouldn't work, at least when using "systemd-nspawn -bD ...". -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: qt5ct for Wily
Thank you,
On Mon, 21 Sep 2015 13:40:37 +0300, Timo Jyrinki wrote:
>> [weremouse@moonstudio qt5ct-0.17]$ qtchooser -qt=5 -run-tool=qmake
>> PREFIX=/usr/local
>
>Just use export QT_SELECT=5 (or export QT_SELECT := 5 in debian/rules)
>and run qmake normally.
I already tried this too and it doesn't change anything.
>> main.cpp:29:38: fatal error: qpa/qplatformthemeplugin.h: No such
>> file or directory
>
>That's in qtbase5-private-dev since it's a private header that normal
>apps should not be using.
Yes, the problem is the qt4 path.
On Arch Linux just qmake is selected and it seems to work:
$ grep build -A4 /mnt/archlinux/var/abs/community/qt5ct/PKGBUILD
build() {
cd $pkgname-$pkgver
qmake-qt5 $pkgname.pro
make
}
However, on Arch I didn't build it, I just installed the binary package.
Perhaps there's a reason that qt5ct isn't provided by the Ubuntu
repositories and there's another solution already provided to select
theme and fonts, when not using KDE.
It might be related:
Maybe something is broken for my Ubuntu openbox install, e.g. font
sizes selected by .gtkrc-2.0 doesn't affect the menu bar of GTK2 apps
such as spacefm. I don't experience such issues for my Arch install.
For Ubuntu I need to start sessions with export XDG_CONFIG_DIRS=""
to avoid unwanted autostarts, IOW Ubuntu handles a lot of things in a
different way, compared to the way I know. To handle things in
different ways is ok, unfortunately I can't find links were those
things are documented.
Regards,
Ralf
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: qt5ct for Wily
2015-09-20 12:24 GMT+03:00 Ralf Mardorf : > does somebody know a link that introduces how to build qt5 applications > for Wily? The closest might be http://pkg-kde.alioth.debian.org/packagingqtstuff.html > [weremouse@moonstudio qt5ct-0.17]$ qtchooser -qt=5 -run-tool=qmake > PREFIX=/usr/local Just use export QT_SELECT=5 (or export QT_SELECT := 5 in debian/rules) and run qmake normally. > main.cpp:29:38: fatal error: qpa/qplatformthemeplugin.h: No such file or > directory That's in qtbase5-private-dev since it's a private header that normal apps should not be using. > I wonder why the include paths are qt4. Possibly since you were only specifying the Qt version to use for the single tool, and the default fallback is Qt 4. That is, Qt 4 applications don't need to know about different Qt versions, but Qt 5 applications need to for example set that environment variable. -Timo -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
