From glen at pld-linux.org Tue Oct 1 08:52:31 2013 From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Tue, 01 Oct 2013 09:52:31 +0300 Subject: Package rename In-Reply-To: References: Message-ID: <524A712F.2060203@pld-linux.org> On 30/09/13 20:55, Caleb Maclennan wrote: > Can we rename the terminator package to gnome-terminator? There are > actually two projects by this name and I'd like to introduce the one > we don't have to a couple of my systems. I looked at the upstream > projects and it looks like the one currently in our specs repo is > already partially renamed upstream and is the logical one to get a new > package name on our side. > > http://gnometerminator.blogspot.com/ > https://code.launchpad.net/~gnome-terminator/terminator/trunk > +1 and the command is: $ ssh git at git.pld-linux.org move OLD_PACKAGE NEW_PACKAGE -- glen From caleb at pld-linux.org Thu Oct 10 01:11:27 2013 From: caleb at pld-linux.org (Caleb Maclennan) Date: Wed, 9 Oct 2013 17:11:27 -0600 Subject: CRI images Message-ID: Are there sanely recent CRI images for TH to be had anywhere? Caleb From hawk at pld-linux.org Thu Oct 10 10:44:26 2013 From: hawk at pld-linux.org (Marcin Krol) Date: Thu, 10 Oct 2013 10:44:26 +0200 Subject: CRI images In-Reply-To: References: Message-ID: <525668EA.60906@pld-linux.org> > Are there sanely recent CRI images for TH to be had anywhere? Officially - no. I've recently started developement of completly new version of CRI which will be used as default installer/rescue for TLD, but I'll not be including Th chroots anymore unless someone will create them (including scripting to make them work with CRI) and then maintain them in future. M. From caleb at pld-linux.org Thu Oct 10 18:57:55 2013 From: caleb at pld-linux.org (Caleb Maclennan) Date: Thu, 10 Oct 2013 10:57:55 -0600 Subject: Missing kernel packages from TH repos Message-ID: I tried to do an install via Rescue CD and poldek --root the other day only to discover that apparently a lot of packages (including the kernel) are missing from the current main TH ftp repository. What's the deal with this? How is anybody supposed to get a system up and running without a way to bootstrap (CRI images are hopelessly old) and without a complete current repository to do a full base system install from? Even knowing the system will I can't figure out how I'm supposed to proceed! Sorry this is half a question half a rant. I'm a bit frustrated with half a dozen systems to replace. Caleb From glen at pld-linux.org Thu Oct 10 21:46:07 2013 From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Thu, 10 Oct 2013 22:46:07 +0300 Subject: Missing kernel packages from TH repos In-Reply-To: References: Message-ID: <525703FF.4070907@pld-linux.org> perhaps you did something wrong? the packages are on ftp! send your output and actual errors! and the verbose you get the sooner your get to solution. as for example, you didn't even note which ftp mirror you were using, it could be broken! my random guess is that you selected only noarch repository, this is definitely not complete distribution! On 10/10/13 19:57, Caleb Maclennan wrote: > I tried to do an install via Rescue CD and poldek --root the other day > only to discover that apparently a lot of packages (including the > kernel) are missing from the current main TH ftp repository. > > What's the deal with this? How is anybody supposed to get a system up > and running without a way to bootstrap (CRI images are hopelessly old) > and without a complete current repository to do a full base system > install from? Even knowing the system will I can't figure out how I'm > supposed to proceed! > > Sorry this is half a question half a rant. I'm a bit frustrated with > half a dozen systems to replace. > > Caleb -- glen From hawk at pld-linux.org Fri Oct 11 10:20:53 2013 From: hawk at pld-linux.org (Marcin Krol) Date: Fri, 11 Oct 2013 10:20:53 +0200 Subject: Missing kernel packages from TH repos In-Reply-To: References: Message-ID: <5257B4E5.30100@pld-linux.org> > Sorry this is half a question half a rant. I'm a bit frustrated with > half a dozen systems to replace. I think current PLD status is somehow similar to TLD status. Number of active developers is limited to few persons and they now develop/maintain system for their own needs, not for other users. If someone wishes to still use it he must agree with such policy (and problems it may cause). Things won't get better IMO. Most of user base is already gone and there are no new developers interested in working on PLD. M. From glen at pld-linux.org Fri Oct 11 12:34:37 2013 From: glen at pld-linux.org (=?ISO-8859-1?Q?Elan_Ruusam=E4e?=) Date: Fri, 11 Oct 2013 13:34:37 +0300 Subject: Fwd: Noarch error: perl-MIME-Types-2.04-2.noarch.rpm files differ among builders In-Reply-To: References: Message-ID: <5257D43D.7000104@pld-linux.org> nice. a. why is check relying on order of things in deps b. why would rpm have the order randomized now, i.e over all these years the a) has "just worked" -------- Original Message -------- Subject: Noarch error: perl-MIME-Types-2.04-2.noarch.rpm files differ among builders Date: Fri, 11 Oct 2013 08:10:02 +0200 From: PLD th-ftp AI To: arekm at pld-linux.org CC: pld-logs-th at lists.pld-linux.org, glen at pld-linux.org, baggins at pld-linux.org Difference between x86_64 (currently in test) and i686 REQS @@ -1,3 +1,4 @@ +/usr/share/perl5/vendor_perl perl(Carp) perl(Exporter) perl(File::Basename) @@ -7,4 +8,3 @@ perl(vars) rpmlib(PayloadIsLzma) <= 4.4.6-1 rpmlib(VersionedDependencies) <= 3.0.3-1 -/usr/share/perl5/vendor_perl From draenog at pld-linux.org Fri Oct 11 12:54:41 2013 From: draenog at pld-linux.org (Kacper Kornet) Date: Fri, 11 Oct 2013 12:54:41 +0200 Subject: Fwd: Noarch error: perl-MIME-Types-2.04-2.noarch.rpm files differ among builders In-Reply-To: <5257D43D.7000104@pld-linux.org> References: <5257D43D.7000104@pld-linux.org> Message-ID: <20131011105440.GA7059@camk.edu.pl> On Fri, Oct 11, 2013 at 01:34:37PM +0300, Elan Ruusam?e wrote: > > a. why is check relying on order of things in deps > b. why would rpm have the order randomized now, i.e over all these > years the a) has "just worked" > > > -------- Original Message -------- > Subject: Noarch error: perl-MIME-Types-2.04-2.noarch.rpm files > differ among builders > Date: Fri, 11 Oct 2013 08:10:02 +0200 > From: PLD th-ftp AI > To: arekm at pld-linux.org > CC: pld-logs-th at lists.pld-linux.org, glen at pld-linux.org, > baggins at pld-linux.org > > > > Difference between x86_64 (currently in test) and i686 REQS > @@ -1,3 +1,4 @@ > +/usr/share/perl5/vendor_perl > perl(Carp) > perl(Exporter) > perl(File::Basename) > @@ -7,4 +8,3 @@ > perl(vars) > rpmlib(PayloadIsLzma) <= 4.4.6-1 > rpmlib(VersionedDependencies) <= 3.0.3-1 > -/usr/share/perl5/vendor_perl It looks like the change due to locale. Maybe someone modified the environment in which the script is run? Where is there its source? -- Kacper From qboosh at pld-linux.org Sat Oct 12 22:50:22 2013 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Sat, 12 Oct 2013 22:50:22 +0200 Subject: [packages/syslog-ng] - build with internal libivykis for now, syslog-ng segfaults with devel versions (>0.36.x) In-Reply-To: References: <84eaa58b4007a43e8a0df4a3bb85346d84d99067_refs_heads_master@pld-linux.org> Message-ID: <20131012205022.GA613@mail> On Tue, Oct 08, 2013 at 12:47:32PM +0200, hawk wrote: > commit b2e460d3b1f4db0e32403c23142070319ed7a0cb > Author: Marcin Krol > Date: Tue Oct 8 10:46:08 2013 +0000 > > - build with internal libivykis for now, syslog-ng segfaults with > devel versions (>0.36.x) What configuration (compared to default)? syslog-ng 3.4.3 + libivykis 0.39 works for me, configuration is almost default. Maybe significant change: I'm using syslog-ng built --with dynamic. -- Jakub Bogusz http://qboosh.pl/ From hawk at pld-linux.org Sun Oct 13 15:01:03 2013 From: hawk at pld-linux.org (Marcin Krol) Date: Sun, 13 Oct 2013 15:01:03 +0200 Subject: [packages/syslog-ng] - build with internal libivykis for now, syslog-ng segfaults with devel versions (>0.36.x) In-Reply-To: <20131012205022.GA613@mail> References: <84eaa58b4007a43e8a0df4a3bb85346d84d99067_refs_heads_master@pld-linux.org> <20131012205022.GA613@mail> Message-ID: <525A998F.6010104@pld-linux.org> > What configuration (compared to default)? > > syslog-ng 3.4.3 + libivykis 0.39 works for me, configuration is almost > default. > Maybe significant change: I'm using syslog-ng built --with dynamic. Trited both, my own config and default one installed by package. It segfaults on both. M. From draenog at pld-linux.org Tue Oct 15 00:01:19 2013 From: draenog at pld-linux.org (Kacper Kornet) Date: Tue, 15 Oct 2013 00:01:19 +0200 Subject: [packages/openssh/GIT_-nopass] don't pass and accept GIT_ variables In-Reply-To: <289a902d894a2dc8d78d5e4a762568132f3c8108_refs_heads_GIT_-nopass@pld-linux.org> References: <20131014215632.7961.85687@pld-linux.org> <289a902d894a2dc8d78d5e4a762568132f3c8108_refs_heads_GIT_-nopass@pld-linux.org> Message-ID: <20131014220119.GA987@camk.edu.pl> On Mon, Oct 14, 2013 at 11:56:37PM +0200, Kacper Kornet wrote: > commit 289a902d894a2dc8d78d5e4a762568132f3c8108 > Author: Kacper Kornet > Date: Mon Oct 14 22:52:22 2013 +0100 > don't pass and accept GIT_ variables > Passing GIT_* variables can break some packages. For example gitolite > (see gitolite-env.patch) and gitolite3. Unless someone is against I'm going to merge it to master. On the other hand I don't want to break someone's setups, so if you depend on this feature it is a chance to protest. > openssh-config.patch | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > --- > diff --git a/openssh-config.patch b/openssh-config.patch > index e124f10..5bd317b 100644 > --- a/openssh-config.patch > +++ b/openssh-config.patch > @@ -50,8 +50,8 @@ > # no default banner path > #Banner /some/path > -+# Accept locale-related environment variables, also accept GIT vars > -+AcceptEnv LANG LC_* LANGUAGE TZ GIT_* > ++# Accept locale-related environment variables > ++AcceptEnv LANG LC_* LANGUAGE TZ > + > # override default of no subsystems > Subsystem sftp /usr/libexec/sftp-server > @@ -92,6 +92,6 @@ > + ServerAliveInterval 60 > + ServerAliveCountMax 10 > + TCPKeepAlive no > -+# Send locale-related environment variables, also pass GIT vars > -+ SendEnv LANG LC_* LANGUAGE TZ GIT_* > ++# Send locale-related environment variables > ++ SendEnv LANG LC_* LANGUAGE TZ > + HashKnownHosts yes > ================================================================ > ---- gitweb: > http://git.pld-linux.org/gitweb.cgi/packages/openssh.git/commitdiff/289a902d894a2dc8d78d5e4a762568132f3c8108 > _______________________________________________ > pld-cvs-commit mailing list > pld-cvs-commit at lists.pld-linux.org > http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit -- Kacper Kornet From jajcus at jajcus.net Tue Oct 15 10:15:01 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Tue, 15 Oct 2013 10:15:01 +0200 Subject: [packages/nginx] Provide the vhosts.d and webapps.d directories In-Reply-To: <525C6569.2070103@pld-linux.org> References: <36b3be348a3f1d1e5a7d97de9128a536e0a8d78b_refs_heads_master@pld-linux.org> <525C0718.4060209@pld-linux.org> <20131014191048.4524e8cb@lolek.nigdzie> <525C6569.2070103@pld-linux.org> Message-ID: <20131015101501.13757aeb@jajo.eggsoft> Cc: pld-devel-en, as the discussion may be interesting for others too On Tue, 15 Oct 2013 00:43:05 +0300 Elan Ruusam?e wrote: > On 14/10/13 20:10, Jacek Konieczny wrote: > >> (as you know the "other" webservers are populated with triggers > > What triggers? You mean that '# make sure webapps.d is included' trigger > > in apache.spec? That would be crazy. > no, i mean in web app itself, like phpmyadmin. as a start how to use it. > not all packages of course! > so template-specs/webapp.spec could be updated with samples. I can see that. But there is a problem. This system was designed for one of the most broken HTTP servers (Apache) and it is hard to make it work well with other servers. nginx is a HTTP server/proxy/load-balancer and a good one. Not an application server. Many webapps won't work with nginx alone. And often the webapps would be running on a different server that nginx would run on. When deploying applications under nginx the apps are running under uWSGI or as standalone FastCGI programs. They can be running under a different UID/GID (which is desirable when many different webapps are running on a single server) or on a different machine. The same could be done with lighttpd, but Apache was never really made for such secure, efficient and scalable scenario. And our 'webapps' system is made for those Apache limitations: ? Requires: webserver(*), when the webserver is not needed on the local machine ? drop-in configuration files only for the web server, not any other component (typical Python or CGI webapp deployment with ngix would require both nginx and uWSGI configuration files placed in right places) ? no sane way for privilege separation ? there is no good way to do that for Apache, so no a good generic way to enable this in webapp packages. I don't have time and desire to hack webapps to use nginx our current way or to invent something better (that would probably require a lot of work). But feel free to try it yourself :) Greets, Jacek From glen at pld-linux.org Wed Oct 16 17:15:33 2013 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Wed, 16 Oct 2013 18:15:33 +0300 Subject: [packages/CUnit] - updated to 2.1 - updated curses, libs, FHS patches - separated -libs, -static (base is the developme In-Reply-To: References: <0e2f8d9fbaa6c443650762c6f919fe9c31abc631_refs_heads_master@pld-linux.org> Message-ID: <525EAD95.2020401@pld-linux.org> On 16.10.2013 17:25, qboosh wrote: > diff --git a/CUnit.spec b/CUnit.spec > index bfdfaae..abf907c 100644 > --- a/CUnit.spec > +++ b/CUnit.spec > @@ -1,19 +1,26 @@ > +# NOTE: due to its nature, base package is development tool, so there is no separate -devel > +# i would prefer to omit base package and still create -devel. this way i can easily cleanup machine from development stuff: poldek -e `rpm -qa '*-devel'` -- glen From jajcus at jajcus.net Wed Oct 16 17:46:27 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Wed, 16 Oct 2013 17:46:27 +0200 Subject: [packages/CUnit] - updated to 2.1 - updated curses, libs, FHS patches - separated -libs, -static (base is the developme In-Reply-To: <525EAD95.2020401@pld-linux.org> References: <0e2f8d9fbaa6c443650762c6f919fe9c31abc631_refs_heads_master@pld-linux.org> <525EAD95.2020401@pld-linux.org> Message-ID: <20131016174627.3a87fac9@lolek.nigdzie> On Wed, 16 Oct 2013 18:15:33 +0300 Elan Ruusam?e wrote: > On 16.10.2013 17:25, qboosh wrote: > > diff --git a/CUnit.spec b/CUnit.spec > > index bfdfaae..abf907c 100644 > > --- a/CUnit.spec > > +++ b/CUnit.spec > > @@ -1,19 +1,26 @@ > > +# NOTE: due to its nature, base package is development tool, so > > there is no separate -devel +# > i would prefer to omit base package and still create -devel. > > this way i can easily cleanup machine from development stuff: poldek > -e `rpm -qa '*-devel'` So, should we rename 'gcc' to 'gcc-devel' and 'make' to 'make-devel'? Unless the package contains _only_ header files and libraries (no binaries) keeping -devel only does not make sense to me. Greets, Jacek From jajcus at jajcus.net Wed Oct 23 16:50:06 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Wed, 23 Oct 2013 16:50:06 +0200 Subject: GDM won't work under systemd Message-ID: <20131023165006.364a305a@jajo.eggsoft> Hi, I am trying to install a usable PLD Linux on a laptop. Currently I am stuck at GDM which won't start correctly. The X server is started, but nothing is displayed, but the syslog is flooded with "'/run/user/0/dconf': Permission denied.". It starts like this: > Oct 23 16:36:14 mobik dbus-daemon[1011]: dbus[1011]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.40" (uid=0 pid=1682 comm="") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.41" (uid=0 pid=1686 comm="") > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: DEBUG(+): Enabling debugging > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): Enabling debugging > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. > Oct 23 16:36:15 mobik gnome-session[1710]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): Using systemd for session tracking > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: DEBUG(+): Using systemd for session tracking > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): GsmShell: Not connected to the shell > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): GsmManager: setting client store 0x1000680 > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: DEBUG(+): GsmShell: Not connected to the shell > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: DEBUG(+): GsmManager: setting client store 0x1000680 > Oct 23 16:36:15 mobik /usr/bin/dbus-launch[1710]: gnome-session[1710]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/mobik:@/tmp/.ICE-unix/1710,unix/mobik:/tmp/.ICE-unix/1710 > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/mobik:@/tmp/.ICE-unix/1710,unix/mobik:/tmp/.ICE-unix/1710 > Oct 23 16:36:15 mobik gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): fill: *** Getting session 'gdm-shell' > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): fill: *** Looking if /home/services/xdm/.config/gnome-session/sessions/gdm-shell.session is a valid session file > Oct 23 16:36:15 mobik gnome-session[1710]: DEBUG(+): Cannot use session '/home/services/xdm/.config/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. It looks like GDM has some problems with getting right user id from the systemd-logind or something. Does anybody have any ideas how to debug/fix that? I have tried gdm and systemd packages both from main th and from th-ready. Other than that that is generally a fresh Th install. Currently: [root at mobik ~]# rpm -q gdm systemd dconf gdm-3.10.0.1-1.x86_64 systemd-208-4.x86_64 dconf-0.18.0-1.x86_64 Greets, Jacek From jajcus at jajcus.net Wed Oct 23 19:40:27 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Wed, 23 Oct 2013 19:40:27 +0200 Subject: GDM won't work under systemd In-Reply-To: <20131023165006.364a305a@jajo.eggsoft> References: <20131023165006.364a305a@jajo.eggsoft> Message-ID: <20131023194027.7435082a@lolek.nigdzie> On Wed, 23 Oct 2013 16:50:06 +0200 Jacek Konieczny wrote: > I am trying to install a usable PLD Linux on a laptop. Currently I am > stuck at GDM which won't start correctly. > > The X server is started, but nothing is displayed, but the syslog is > flooded with "'/run/user/0/dconf': Permission denied.". Ok? I have learned a bit by now. The "'/run/user/0/dconf': Permission denied." is a different problem not related to my initial problem of GDM not showing. The initial problem was not Metacity theme installed. As soon as I have installed one the GDM starts properly from systemd. The "'/run/user/0/dconf': Permission denied." and related errors are showing only when I stard GDM manually from the root shell. This is a design 'feature' of pam_systemd ? it always uses the uid of the user who initially logged in. So GDM won't start properly from a user login session. Even if that user is root. Greets, Jacek From baggins at pld-linux.org Wed Oct 23 21:58:46 2013 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Wed, 23 Oct 2013 21:58:46 +0200 Subject: GDM won't work under systemd In-Reply-To: <20131023194027.7435082a@lolek.nigdzie> References: <20131023165006.364a305a@jajo.eggsoft> <20131023194027.7435082a@lolek.nigdzie> Message-ID: <20131023195846.GA1396@home> On Wed, 23 Oct 2013, Jacek Konieczny wrote: > On Wed, 23 Oct 2013 16:50:06 +0200 > Jacek Konieczny wrote: > > I am trying to install a usable PLD Linux on a laptop. Currently I am > > stuck at GDM which won't start correctly. > > > > The X server is started, but nothing is displayed, but the syslog is > > flooded with "'/run/user/0/dconf': Permission denied.". > > Ok? I have learned a bit by now. > > The "'/run/user/0/dconf': Permission denied." is a different problem not > related to my initial problem of GDM not showing. > > The initial problem was not Metacity theme installed. As soon as I have > installed one the GDM starts properly from systemd. Can you add appriopriate deps to gdm package? -- Jan R?korajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsmimuw.edu.pl bagginspld-linux.org From jajcus at jajcus.net Thu Oct 24 08:32:05 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Thu, 24 Oct 2013 08:32:05 +0200 Subject: GDM won't work under systemd In-Reply-To: <20131023195846.GA1396@home> References: <20131023165006.364a305a@jajo.eggsoft> <20131023194027.7435082a@lolek.nigdzie> <20131023195846.GA1396@home> Message-ID: <20131024083205.5a99151f@jajo.eggsoft> On Wed, 23 Oct 2013 21:58:46 +0200 Jan R?korajski wrote: > > The initial problem was not Metacity theme installed. As soon as I have > > installed one the GDM starts properly from systemd. > > Can you add appriopriate deps to gdm package? Those are not direct GDM dependencies, but rather gnome-shell dependencies. And 'Requires: metacity-theme-base' in 'gnome-shell.spec' doesn't look quite right, though it should work. Anybody knows if anything else provides compatible themes? Do we have a virtual provide for that? Greets, Jacek From draenog at pld-linux.org Thu Oct 24 17:13:32 2013 From: draenog at pld-linux.org (Kacper Kornet) Date: Thu, 24 Oct 2013 17:13:32 +0200 Subject: [packages/gtkpod] - updated to 2.1.4 - updated BRs - patches 3 and 4 are applied upstream In-Reply-To: <5a16848fdde49d61bc913455b6509f22e5bd8252_refs_heads_master@pld-linux.org> References: <43d80eec6bed70d08ef30b156d4278d24946c26f_refs_heads_master@pld-linux.org> <5a16848fdde49d61bc913455b6509f22e5bd8252_refs_heads_master@pld-linux.org> Message-ID: <20131024151332.GA28353@camk.edu.pl> On Thu, Oct 24, 2013 at 04:31:25PM +0200, kiesiu wrote: > commit 5a16848fdde49d61bc913455b6509f22e5bd8252 > Author: ?ukasz Kie? > Date: Thu Oct 24 16:29:14 2013 +0200 > - updated to 2.1.4 > - updated BRs > - patches 3 and 4 are applied upstream > gtkpod.spec | 15 ++++++--------- > 1 file changed, 6 insertions(+), 9 deletions(-) I think it would be better if the files with the relevant patches were removed in the same commit. -- Kacper From kiesiu at pld-linux.org Thu Oct 24 17:39:52 2013 From: kiesiu at pld-linux.org (Lukasz Kies) Date: Thu, 24 Oct 2013 17:39:52 +0200 Subject: [packages/gtkpod] - updated to 2.1.4 - updated BRs - patches 3 and 4 are applied upstream In-Reply-To: <20131024151332.GA28353@camk.edu.pl> References: <43d80eec6bed70d08ef30b156d4278d24946c26f_refs_heads_master@pld-linux.org> <5a16848fdde49d61bc913455b6509f22e5bd8252_refs_heads_master@pld-linux.org> <20131024151332.GA28353@camk.edu.pl> Message-ID: 2013/10/24 Kacper Kornet : > On Thu, Oct 24, 2013 at 04:31:25PM +0200, kiesiu wrote: >> commit 5a16848fdde49d61bc913455b6509f22e5bd8252 >> Author: ?ukasz Kie? >> Date: Thu Oct 24 16:29:14 2013 +0200 > >> - updated to 2.1.4 >> - updated BRs >> - patches 3 and 4 are applied upstream > >> gtkpod.spec | 15 ++++++--------- >> 1 file changed, 6 insertions(+), 9 deletions(-) > > I think it would be better if the files with the relevant patches were > removed in the same commit. > Hi, Point taken. Will do next time. -- Regards, Lukasz From kiesiu at pld-linux.org Fri Oct 25 00:31:42 2013 From: kiesiu at pld-linux.org (Lukasz Kies) Date: Fri, 25 Oct 2013 00:31:42 +0200 Subject: [packages/gnome-shell] R: metacity-theme-base In-Reply-To: <82ca6ec58bb122b2c2258e0943f6d061a495ef15_refs_heads_master@pld-linux.org> References: <1eb588b038b82dc62c2588d31ac3fdfb9f7b9866_refs_heads_master@pld-linux.org> <82ca6ec58bb122b2c2258e0943f6d061a495ef15_refs_heads_master@pld-linux.org> Message-ID: 2013/10/24 jajcus : > commit 82ca6ec58bb122b2c2258e0943f6d061a495ef15 > Author: Jacek Konieczny > Date: Thu Oct 24 10:37:33 2013 +0200 > > R: metacity-theme-base > > Without such (or a compatible) theme gnome-shell won't work. In case > of a fresh PLD install with just GDM the symptom is no graphical output > when GDM starts. Hi, I don't believe this is the correct way couse it force user to install a large part of metacity while most probably already another, newer WM is installed (like mutter). GDM cannot start because gnome-session cannot find a "usual theme" from /usr/share/themes: Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: Failed to load theme "Adwaita": Failed to find a valid file for theme Adwaita Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: Failed to load theme "Simple": Failed to find a valid file for theme Simple Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: Failed to load theme "Default": Failed to find a valid file for theme Default Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: Failed to load theme "HighContrast": Failed to find a valid file for theme HighContrast Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: Failed to load theme "Raleigh": Failed to find a valid file for theme Raleigh Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: Failed to load theme "Adwaita": Failed to find a valid file for theme Adwaita Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: Failed to load theme "Emacs": Failed to find a valid file for theme Emacs Oct 24 22:58:38 cassie gnome-session[4799]: Window manager error: Could not find a theme! Be sure /usr/share/themes exists and contains the usual themes. Both Adwaita and HighContrast theme is provided by gnome-themes-standard package. However Simple is a metacity theme. As we require for GDM a virtual gdm-wm (at the moment only gnome-shell and metacity) and metacity already requires metacity-theme-base (Simple theme) in my opinion there should be requirement of gnome-themes-standard in gnome-shell (or maybe os some lover level like gnome-desktop?). Any opinions? -- Regards, Lukasz From jajcus at jajcus.net Fri Oct 25 08:40:16 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Fri, 25 Oct 2013 08:40:16 +0200 Subject: [packages/gnome-shell] R: metacity-theme-base In-Reply-To: References: <1eb588b038b82dc62c2588d31ac3fdfb9f7b9866_refs_heads_master@pld-linux.org> <82ca6ec58bb122b2c2258e0943f6d061a495ef15_refs_heads_master@pld-linux.org> Message-ID: <20131025084016.1d2e3623@jajo.eggsoft> On Fri, 25 Oct 2013 00:31:42 +0200 Lukasz Kies wrote: > 2013/10/24 jajcus : > > commit 82ca6ec58bb122b2c2258e0943f6d061a495ef15 > > Author: Jacek Konieczny > > Date: Thu Oct 24 10:37:33 2013 +0200 > > > > R: metacity-theme-base > > > > Without such (or a compatible) theme gnome-shell won't work. In case > > of a fresh PLD install with just GDM the symptom is no graphical output > > when GDM starts. > Hi, > > I don't believe this is the correct way That what I was worried about - that is why I have asked on the list first? > GDM cannot start because gnome-session cannot find a "usual theme" > from /usr/share/themes: > > Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: > Failed to load theme "Adwaita": Failed to find a valid file for theme > Adwaita > Oct 24 22:58:38 cassie gnome-session[4799]: Window manager warning: > Failed to load theme "Simple": Failed to find a valid file for theme > Simple [...] > Both Adwaita and HighContrast theme is provided by > gnome-themes-standard package. However Simple is a metacity theme. I have stopped at 'Simple' that is why I took metacity. I don't know the GDB mysteries well enough to understand all this. I am not sure if I had gnome-themes-standard package installed or no. > As we require for GDM a virtual gdm-wm (at the moment only gnome-shell > and metacity) and metacity already requires metacity-theme-base > (Simple theme) in my opinion there should be requirement of > gnome-themes-standard in gnome-shell (or maybe os some lover level > like gnome-desktop?). > Any opinions? Sounds good enough for me, if it works. BTW. I have dropped GDM in favour of lxdm. Now the systems boots much faster and I have much less weird error logs in syslog. It looks worse, but is configurable (it is hard to say that about GDM3). Frankly, GDM3 seems like a big piece of crap? Greets, Jacek From glen at pld-linux.org Fri Oct 25 10:07:24 2013 From: glen at pld-linux.org (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Fri, 25 Oct 2013 11:07:24 +0300 Subject: [packages/gnome-shell] R: metacity-theme-base In-Reply-To: <20131025084016.1d2e3623@jajo.eggsoft> References: <1eb588b038b82dc62c2588d31ac3fdfb9f7b9866_refs_heads_master@pld-linux.org> <82ca6ec58bb122b2c2258e0943f6d061a495ef15_refs_heads_master@pld-linux.org> <20131025084016.1d2e3623@jajo.eggsoft> Message-ID: <526A26BC.6000004@pld-linux.org> On 25.10.2013 09:40, Jacek Konieczny wrote: > BTW. I have dropped GDM in favour of lxdm. Now the systems boots much > faster and I have much less weird error logs in syslog. It looks worse, > but is configurable (it is hard to say that about GDM3). Frankly, GDM3 > seems like a big piece of crap? btw, i got lightdm working too finally, icons are still missing, but i can at least log in with it. error was quite stupid, default config specified script ( lightdm-session) that did not exist http://git.pld-linux.org/?p=packages/lightdm.git;a=commitdiff;h=4f2b815393c8b73eda9ab222024d6171d96f72c1 -- glen From jajcus at jajcus.net Sat Oct 26 15:29:39 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Sat, 26 Oct 2013 15:29:39 +0200 Subject: /usr/lib/xorg/modules/dri to filesystem or somewhere else? Message-ID: <20131026152939.54b3f981@lolek.nigdzie> Hi, On every x86_64/i686 (multiarch) PLD desktop system I have the same problem with installing Mesa-driver-dri-* packages: The Mesa-driver-dri-*.i686 packages pull xorg-xserver-server-*.i686 package (because of the /usr/lib/xorg/modules/dri directory), which conflicts with xorg-xserver-server-*.x86_64. This dependency is artificial - the Mesa DRI drivers are used by X clients and do not directly depend on the xserver. I think the /usr/lib/xorg/modules/dri directory should be moved to some other package. Is 'filesystem' ok? Or should I add /usr/lib/xorg/modules/dri to xorg-xserver-server-*.x86_64? This will keep the artificial dependency, but the x86_64 xserver would be enough to satisfy it. Greets, Jacek From baggins at pld-linux.org Sat Oct 26 22:05:06 2013 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Sat, 26 Oct 2013 22:05:06 +0200 Subject: /usr/lib/xorg/modules/dri to filesystem or somewhere else? In-Reply-To: <20131026152939.54b3f981@lolek.nigdzie> References: <20131026152939.54b3f981@lolek.nigdzie> Message-ID: <20131026200506.GB1459@home> On Sat, 26 Oct 2013, Jacek Konieczny wrote: > > Hi, > > On every x86_64/i686 (multiarch) PLD desktop system I have the same > problem with installing Mesa-driver-dri-* packages: > > The Mesa-driver-dri-*.i686 packages pull xorg-xserver-server-*.i686 > package (because of the /usr/lib/xorg/modules/dri directory), which > conflicts with xorg-xserver-server-*.x86_64. > > This dependency is artificial - the Mesa DRI drivers are used by X > clients and do not directly depend on the xserver. I think the > /usr/lib/xorg/modules/dri directory should be moved to some other > package. > > Is 'filesystem' ok? > > Or should I add /usr/lib/xorg/modules/dri to > xorg-xserver-server-*.x86_64? This will keep the artificial dependency, > but the x86_64 xserver would be enough to satisfy it. xorg-xserver-server looks better, it is the xserver that's really required here. And it keeps deps/provs close to where they are. -- Jan R?korajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsmimuw.edu.pl bagginspld-linux.org From jajcus at jajcus.net Sun Oct 27 16:05:19 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Sun, 27 Oct 2013 16:05:19 +0100 Subject: /usr/lib/xorg/modules/dri to filesystem or somewhere else? In-Reply-To: <20131026200506.GB1459@home> References: <20131026152939.54b3f981@lolek.nigdzie> <20131026200506.GB1459@home> Message-ID: <20131027160519.3a3be4f2@lolek.nigdzie> On Sat, 26 Oct 2013 22:05:06 +0200 Jan R?korajski wrote: > xorg-xserver-server looks better, it is the xserver that's really > required here. No, it is not. At least swrastr Mesa driver should be usable without any X server. Probably other DRI drivers could be usable in some way without X11 too. But xorg-xserver-server seems the easiest solution and probably more elegant as long as the drivers are stored under /usr/lib/xorg. I will add it there. Greets, Jacek From draenog at pld-linux.org Mon Oct 28 19:23:53 2013 From: draenog at pld-linux.org (Kacper Kornet) Date: Mon, 28 Oct 2013 19:23:53 +0100 Subject: geninitrd and rc-scripts - migration to git Message-ID: <20131028182353.GA6842@camk.edu.pl> It has been suggested that repositories for rc-scripts and geninitrd should be migrated from subversion to git. So far I have setup two read only repositories: git://git.pld-linux.org/readonly/geninitrd.git git://git.pld-linux.org/readonly/rc-scripts.git 1) So is there anyone who whas objections against the change? 2) Is the anything that should be changed in the repositories? For example the lines git-svn-id: http://svn.pld-linux.org/svn/geninitrd/trunk at 12723 11da6c6d-24c7-0310-97e0-b6d17e038e62 at the end of commit logs are the metadata for git-svn and maybe should be removed (or changed to something else) in final repositories. -- Kacper