[DNG] Thanks for your help

[emninger]

Hi all!

I wanted to say thank you to you all for patience and your help. I've
finished now, more or less, my installation with a "custom made" jwm
desktop. So far, so fine.

The remaining logout problem, seems to be solved by the installation of
lxdm (which is not that much bigger than slim; i also had a look at
mdm, but it's enormous, in comparison). With lxdm, my logouts go back
to the login like they are expected to do; with slim and with lightdm i
always ended in dead screen with underline cursor, inactive, up left.
Apparently like the shutdown xserver was unable to pass back to the
login manager (also true when i killed the xserver with Ctrl-Alt-Bksp).
This did *NOT* happen when i started without login manager (by startx).

Now, my ~/.xsessionrc looks like this, it's very primitive, i know:

---
#!/bin/bash
xrdb -merge .Xresources
setxkbmap -option terminate:ctrl_alt_bksp
exec jwm
exit 0
---

In lxdm, beside some "artwork", i set this options:

---
[server]
## arg used to start xserver, not fully function
arg=/usr/bin/X -background vt1
# uncomment this if you really want xserver listen to tcp
# tcp_listen=1
# uncoment this if you want reset the xserver after logout
# reset=1


By default, all were commented out, but i thought the first one might
be useful to avoid my ugly logout problem (??)

It seems to me, lxdm does not look into /usr/share/xsessions but reads
by default this file (when i took out the "exec jwm") lxdm did not
start anything although it recignized there are also lxde and openbox
(in /usr/share/xsessions), i'd like to know, if there is a way to state
in .xsessionrc, that there are other sessions which could be started if
chosen in lxdm (with jwm in any case as default)? Then it would be
perfect :) 


As for the rest, "my" desktop consists in a relative elaborated
configuration which for the most part i stole from Manjaro OpenRC JWM +
pcmanfm. If one would like, pcmanfm could even put the trash, devices
and other icons on the desktop. Plus a Plank starterbar at the bottom.

(Plank and lxdm, i got from the ascii repositories; jwm is the jessie
default one). If you'd like i could post somewhere a screenshot, so you
can see that it's not "debianized" :)

Cheers.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Logout problem

[emninger]

Some time ago Ozi Traveller helped me out for my logout problem sending
me 2 desktop environment independent logout tools (cb-exit and
oblogout, which essentially do the same, only oblogout is a bit more
eye candy). I had some problems with them but solved by changing the
localauthority settings of polkit.

Now, i have the chance to access my manjaro-openrc machine and i see
they do use oblogout in a slightly different manner: For them, oblogout
works as a kind of skin over a script called "fluxboxexit" (which
adresses both, systemd and openrc. For those interested, you can look
at it here: http://hastebin.com/ufeluvobiw.rb). The /etc/oblogout.conf
then look like this:

---
[settings]
usehal = false

[looks]
opacity = 40
bgcolor = black
# buttontheme = 
buttontheme = foom
buttons = lock, logout, switch, suspend, hibernate, restart, shutdown,
cancel

[shortcuts]
lock = K
logout = L
switch = W
suspend = U
hibernate = H
restart = R
shutdown = S
cancel = Escape

[commands]
lock = ob_blurlock
logout = fluxboxexit logout
switch = dm-tool switch-to-greeter
suspend = fluxboxexit suspend
hibernate = fluxboxexit hibernate
restart = fluxboxexit reboot
shutdown = fluxboxexit shutdown
---

May be it's not that bad as an idea?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OpenRC: Was: Re: Dng Digest, Vol 20, Issue 138

[Steve Litt]

On Thu, 26 May 2016 12:50:19 +0200
Svante Signell  wrote:

> On Thu, 2016-05-26 at 11:28 +0200, emnin...@riseup.net wrote:
> 
> Please keep the subject, even if you are reading the mails via the
> Digest service!

In addition, if you respond to a digest subjected email, please change
the subject back to the original, like Svante just did. If that's too
much trouble, just don't reply. My opinion: if somebody isn't willing to
take the time to MAKE ABSOLUTELY SURE he has the right subject, he
doesn't deserve a reply.

I think the "convenience" of getting email via digest implies the
*responsibility* of the extra work in fixing the subject and deleting
all extraneous body. That's why I never use a digest: by the time you
do what's right, it's not convenient anymore.
 
SteveT

Steve Litt 
May 2016 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OpenRC

[Steve Litt]

On Thu, 26 May 2016 01:53:07 +0200
Dragan FOSS  wrote:

> On 05/26/2016 01:23 AM, Steve Litt wrote:
> > capability of respawning daemons that crash? OpenRC can't do that.  
> 
> OpenRC *can* do that:
> 
> ---
> Automatic respawning crashed services
> ---
> 
> https://wiki.gentoo.org/wiki/OpenRC


Thanks Dragan FOSS!

I've been saying that OpenRC can't respawn ever since the people on
Freenode's #openrc answered my question "How do you respawn in OpenRC
rather than sysvinit's inittab?" with "You can't and you wouldn't want
to." I've been saying this for a year, and nobody ever said "oh yes you
can" til you just did.

So I'll need to quit saying that until I can lay down Manjaro-OpenRC on
a VM, do what the link you supplied says to do, and try it myself. At
which time I'll either continue saying it, or issue a whole bunch of
retractions.

Thanks,
 
SteveT

Steve Litt 
May 2016 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Evince

[Haines Brown]

On Thu, May 26, 2016 at 02:03:26PM +0200, emnin...@riseup.net wrote:
> I do not find the msg, but someone here suggested to use xpdf, possibly
> with a more esthetic skin. 
> 
> I for one, would love that, since i find xpdf really very functional
> and with acceptable print options too.

I used xpdf for years because of its simplicity. However, recently (with
Wheezy?), it sometimes cannot print a PDF. Blank pages come out of the
printer. I've had to resort to $ lpr to print.

Printing is about all I need from a PDF viewer. Mupdf is appealing, but
I have yet to find any way to get it to print. I like qpdfview beause it
is simple and prints, but I find that I one can't select text with a
mouse for pasting elsewhere, which is crucial for me.  I can select text
in evince, and so installed atril. At this point it seems it is my only
choice if I want to avoid dragging a lot of garbage in (okular).

Haines Brown
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Evince

[Paweł Cholewiński]

W dniu 26.05.2016 o 14:03, emnin...@riseup.net pisze:
> 
> I for one, would love that, since i find xpdf really very functional
> and with acceptable print options too.

I don't like scrolbar, button and menu graphics in xpdf. Is it changeable?


Paweł




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Evince

[emninger]

I do not find the msg, but someone here suggested to use xpdf, possibly
with a more esthetic skin. 

I for one, would love that, since i find xpdf really very functional
and with acceptable print options too.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OpenRC: Was: Re: Dng Digest, Vol 20, Issue 138

[emninger]

Am Thu, 26 May 2016 12:50:19 +0200
schrieb Svante Signell :

> On Thu, 2016-05-26 at 11:28 +0200, emnin...@riseup.net wrote:
> 
> Please keep the subject, even if you are reading the mails via the
> Digest service!

You're right! Sorry about that, i was too fast :-( Btw, could that be
corrected ex post, by the administrator(s)? 

Eventually bringing back the correct subjectline or simply by bouncing
back the entire mail (with a reason) giving the chance to the author to
correct the subjectline?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Install a new kernel

[Rainer Weikusat]

Didier Kryn  writes:
> Le 25/05/2016 18:55, Rainer Weikusat a écrit :
>> Linux has the nice policy of never changing a public ABI, hence, there's
>> no problem in this respect
>
> Good to know. Although this is not true for kernel internals (if
> you write or maintain a driver) and it obviously cannot apply to new
> features.
>
> Actually I've never been so afraid about that and often ran libcs
> compiled matching kernel versions newer or older than the running
> one. This was just a warning.

In order to avoid problems in this respect, the running kernel version
needs to be >= the kernel version the C library was compiled (and
written) for and application using 'linux headers' need to be compiled
with the same set of linux headers the C library was compiled with.
This way, it's ascertained that the running kernel supports all features
the C library uses and supports them in a way compatible with it and
that applications and C library agree on how to use a certain kernel
feature.

As 'kernel updates' will usually be updates, ie, use a newer kernel than
the one shipped with the distribution, there's no reason to worry about
any of this on a post-libc5 system: Compiling and installing a new
kernel should 'just work', it just (obviously) won't enable the C
library to take advantage of newer features. If this is an issue, a
newer C library can be installed from source in addition[*] to the
system-provided one and applications can be compiled/ linked such that
they use the newer library.

[*] BIG FAT WARNING: Do not ever try to update the system C library to a
newer version by doing a 'make install' after compiling that unless
you're curious and don't really need to use the system in question
for anything.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] OpenRC: Was: Re: Dng Digest, Vol 20, Issue 138

[Svante Signell]

On Thu, 2016-05-26 at 11:28 +0200, emnin...@riseup.net wrote:

Please keep the subject, even if you are reading the mails via the
Digest service!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Install a new kernel

[Antonio Trkdz.tab]

I have managed to compile and package the 4.4.11 kernel following Katolaz
instructions (thank you!).
It took ages to compileand I knew I would forgot to create a initrd for
it: kernel panic at first boot!

And yet today I saw...

>Lazier:
  apt-get -t jessie-backports install linux-image-4.5.0...

New kernel in 1 minutebatteries included (thank you fsr).
...my bad I didn't investigate more the backports options... looking at the
bright side, though, now I learned the task.

Nouveau driver is now working, but they are buggy (some characters missing
from panel and windows titles in XFCE) and when I start steam X freezes so
badly that I have to ssh reboot it.

On a laptop with an older nvidia card and fresh installation steam worked
flawlessly on nouveau driver
On the same laptop I tried also the latest KubuntuD and it sucked all the
way obliging to install nvidia proprietary driver for steam to work

Just an update on my mouse wheel running
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Dng Digest, Vol 20, Issue 138

[Irrwahn]

On Thu, 26 May 2016 11:28:49 +0200, Emninger wrote:
[...] 
> First, a question: sysvinit does
> respawning?
> 
> Personally, i'd like to *NOT* have it: I think it's better to restart a
> crashed service manually. 
[...]

KatolaZ already replied; I just like to add:
It depends on context:  E.g. for an off-site server I'd 
rather not lose the ability to remote login due to a 
crashed ssh server not being respawned.

Regards
Urban

 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Dng Digest, Vol 20, Issue 138

[KatolaZ]

On Thu, May 26, 2016 at 11:28:49AM +0200, emnin...@riseup.net wrote:
> Am Thu, 26 May 2016 06:38:05 +
> schrieb Steve Litt :
> 
> > Before you do this, allow me to ask you this question: Do you want the
> > capability of respawning daemons that crash? OpenRC can't do that. If
> > you prefer respawning, consider using s3, daemontools-encore or even
> > Runit to manage your daemons.
> 
> Hi Steve, thanks for the explanation.
> 
> First, a question: sysvinit does
> respawning?
> 

Yes, sysvinit does respawn. It has always been able to respawn. This
is actually why you get back again to the login prompt after you have
logged out from a console. Simply, the just-killed "getty" process
(which execv-ed into your login shell after you provided correct login
credentials) gets respawned by init.

  $ man 5 inittab


> Personally, i'd like to *NOT* have it: I think it's better to restart a
> crashed service manually. Let's think of some bad configuration of a
> service/daemon, for example, in Void it would endlessly try to restart
> and fail ... (without automatic respawning one could leave the service
> there and try to reconfiugure it correctly).

sysvinit can also block a service from respawning too often. The
problem is that control over this policy is not so granular.

  $ man 8 init

HND

KatolaZ

-- 
[ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ]
[ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ]
[ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ]
[ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Dng Digest, Vol 20, Issue 138

[emninger]

Am Thu, 26 May 2016 06:38:05 +
schrieb Steve Litt :

> Before you do this, allow me to ask you this question: Do you want the
> capability of respawning daemons that crash? OpenRC can't do that. If
> you prefer respawning, consider using s3, daemontools-encore or even
> Runit to manage your daemons.

Hi Steve, thanks for the explanation.

First, a question: sysvinit does
respawning?

Personally, i'd like to *NOT* have it: I think it's better to restart a
crashed service manually. Let's think of some bad configuration of a
service/daemon, for example, in Void it would endlessly try to restart
and fail ... (without automatic respawning one could leave the service
there and try to reconfiugure it correctly).
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Please excuse me for using a wrong smtp server

[emninger]

Please excuse me for using - sometimes - a wrong (not subscribed) smtp
server. Using several mail services for different purposes, soemtimes i
was too hasty sending a mail out. So, sorry for that. (I hoped, being
not registered with that account, the mails wouldn't be accepted ;) ).

Cheers!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OpenRC

[Didier Kryn]

Le 26/05/2016 01:23, Steve Litt a écrit :

Many people feel that respawning is a pact with the devil: If something
crashes, it should stay crashed for further investigation rather than
"painting over it" with a respawn. If you feel that way, OpenRC is a
good bet.


The arguments pro and cons are all sensible. I think the good 
decision depends on the case.


I'm the admin of a dozen servers in a remote site visited one day 
every two weeks by people with no computing expertise. I would like the 
ssh servers be supervised. In general I think the syslog server should 
be supervised as well. Of course I don't want the ssh server to be 
supervised on my laptop  - in particular because I know how to restart it.


Didier

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] git buildpackage simple-netaid-lightweight ERROR

[aitor_czr]

Hi Edward,

El 26/05/16 a las 09:34, Edward Bartolo escribió:

Hi,

While running 'git buildpackage' to test building a .deb package for
simple-netaid-lightweight I am receiving this error:

Error:
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libfreetype.so.6 (it uses none of the library's symbols)

The complete command output is the following:

--
edbarx@edbarx-pc:~/simple-netaid-lightweight$ git buildpackage --git-ignore-new
  dpkg-buildpackage -rfakeroot -D -us -uc -i -I
dpkg-buildpackage: source package simple-netaid-lightweight
dpkg-buildpackage: source version 0.1.1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by edbarx
  dpkg-source -i -I --before-build simple-netaid-lightweight
dpkg-buildpackage: host architecture amd64
  fakeroot debian/rules clean
dh clean
dh_testdir
dh_auto_clean
make[1]: Entering directory '/home/edbarx/simple-netaid-lightweight'
rm -f sn-lightweight
rm -rf obj
make[1]: Leaving directory '/home/edbarx/simple-netaid-lightweight'
dh_clean
  dpkg-source -i -I -b simple-netaid-lightweight
dpkg-source: info: using source format `3.0 (native)'
dpkg-source: info: building simple-netaid-lightweight in
simple-netaid-lightweight_0.1.1.tar.xz
dpkg-source: info: building simple-netaid-lightweight in
simple-netaid-lightweight_0.1.1.dsc
  debian/rules build
dh build
dh_testdir
dh_auto_configure
dh_auto_build
make[1]: Entering directory '/home/edbarx/simple-netaid-lightweight'
rm -f sn-lightweight
rm -rf obj
gcc -Iinclude `pkg-config --libs --cflags gtk+-2.0` -c
src/auxiliaries.c src/signal_functions.c src/main_gui.c
src/dialog_gui.c src/sn-lightweight.c
mkdir obj
mv *.o obj/
gcc -Iinclude `pkg-config --libs --cflags gtk+-2.0` -o sn-lightweight
obj/auxiliaries.o obj/signal_functions.o obj/main_gui.o
obj/dialog_gui.o obj/sn-lightweight.o
make[1]: Leaving directory '/home/edbarx/simple-netaid-lightweight'
dh_auto_test
  fakeroot debian/rules binary
dh binary
dh_testroot
dh_prep
dh_auto_install
dh_install
dh_installdocs
dh_installchangelogs
dh_perl
dh_link
dh_compress
dh_fixperms
dh_strip
dh_makeshlibs
dh_shlibdeps
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libfreetype.so.6 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libcairo.so.2 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libpangoft2-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libatk-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libpangocairo-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libgdk_pixbuf-2.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libfontconfig.so.1 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libpango-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libgdk-x11-2.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libgio-2.0.so.0 (it uses none of the library's symbols)
dh_installdeb
dh_gencontrol
dh_md5sums
dh_builddeb
dpkg-deb: building package `simple-netaid-lightweight' in
`../simple-netaid-lightweight_0.1.1_amd64.deb'.
  dpkg-genchanges  >../simple-netaid-lightweight_0.1.1_amd64.changes
dpkg-genchanges: including full source code in upload
  dpkg-source -i -I --after-build simple-netaid-lightweight
dpkg-buildpackage: full upload; Debian-native package (full source is included)
Now running lintian...
Could not find a profile matching "{VENDOR}/main" for vendor devuan at
/usr/bin/lintian line 979.

Re: [DNG] git buildpackage simple-netaid-lightweight ERROR

[Paweł Cholewiński]

W dniu 26.05.2016 o 09:34, Edward Bartolo pisze:
> Hi,
> 
> While running 'git buildpackage' to test building a .deb package for
> simple-netaid-lightweight I am receiving this error:
> 
> Error:
> dpkg-shlibdeps: warning: package could avoid a useless dependency if
> debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
> against libfreetype.so.6 (it uses none of the library's symbols)
> 
> The complete command output is the following:
> 
[..]

Hi,
in general is good to use issues on gitlab for reports and most
importantly to look if an issue exists already.

Regards
Paweł



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Making sense of C pointer syntax.

[Edward Bartolo]

Hi,

Thanks for the feedback. I applied the suggested changes to Makefile
and git push-ed to repository. There is still a non-fatal error about
linking against unnecessary libraries that has to be debugged. I will
git push as soon as I find a solution.

Edward

On 25/05/2016, aitor_czr  wrote:
>
> El 25/05/16 a las 10:50, aitor_czr escribió:
>> Hi Edward,
>>
>> El 29/03/16 a las 00:58, Edward Bartolo  escribió:
>>> I found using the return value of a function makes code much more
>>> >readable and probably more reliable. Multiple return values can be
>>> >encapsulated inside a structure which would be returned by a function.
>>> >I used this construct in simple-netaid-lightweight which avoids the
>>> >use of GtkBuilder.
>>> >
>>> >Edward
>>
>> Building your simple-netaid-lightweight, this is what i get:
>>
>>
>> aitor@localhost:~/simple-netaid-lightweight$ make
>> rm -f sn-lightweight
>> gcc -Iinclude `pkg-config --libs --cflags gtk+-2.0` -c
>> src/auxiliaries.c src/signal_functions.c src/main_gui.c
>> src/dialog_gui.c rc/sn-lightweight.c
>> mv *.o obj/
>> mv: el objetivo «obj/» no es un directorio
>> Makefile:16: recipe for target 'compile-objs' failed
>> make: *** [compile-objs] Error 1
>>
>>
>>
>> So, you need to modify the Makefile to something like this:
>>
>> CC=gcc
>> CFLAGS=-Iinclude
>> GTK2FLAGS=`pkg-config --libs --cflags gtk+-2.0`
>> D=src
>> OBJ=obj
>>
>> src0=auxiliaries.c signal_functions.c main_gui.c
>> src1=dialog_gui.c sn-lightweight.c
>>
>> SOURCEFILES=$(addprefix $(D)/, $(src0) $(src1))
>> OBJFILES=$(addprefix $(OBJ)/, $(src0:.c=.o) $(src1:.c=.o))
>>
>> all: clean compile-objs sn-lightweight
>>
>> compile-objs:
>> $(CC) $(CFLAGS) $(GTK2FLAGS) -c $(SOURCEFILES)
>> mkdir obj
>> mv *.o obj/
>>
>> sn-lightweight:
>> $(CC) $(CFLAGS) $(GTK2FLAGS) -o sn-lightweight $(OBJFILES)
>>
>> clean:
>> rm -f sn-lightweight
>>
>> After doing this change, it works :)
>>
>> Cheers,
>>
>>   Aitor.
>>
>> [*] Added "mkdir obj" line.
>>
>
> You must also include:
>
> rm -rf obj
>
> at the end of the Makefile.
>
>Aitor.
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] git buildpackage simple-netaid-lightweight ERROR

[Edward Bartolo]

Hi,

While running 'git buildpackage' to test building a .deb package for
simple-netaid-lightweight I am receiving this error:

Error:
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libfreetype.so.6 (it uses none of the library's symbols)

The complete command output is the following:

--
edbarx@edbarx-pc:~/simple-netaid-lightweight$ git buildpackage --git-ignore-new
 dpkg-buildpackage -rfakeroot -D -us -uc -i -I
dpkg-buildpackage: source package simple-netaid-lightweight
dpkg-buildpackage: source version 0.1.1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by edbarx 
 dpkg-source -i -I --before-build simple-netaid-lightweight
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
make[1]: Entering directory '/home/edbarx/simple-netaid-lightweight'
rm -f sn-lightweight
rm -rf obj
make[1]: Leaving directory '/home/edbarx/simple-netaid-lightweight'
   dh_clean
 dpkg-source -i -I -b simple-netaid-lightweight
dpkg-source: info: using source format `3.0 (native)'
dpkg-source: info: building simple-netaid-lightweight in
simple-netaid-lightweight_0.1.1.tar.xz
dpkg-source: info: building simple-netaid-lightweight in
simple-netaid-lightweight_0.1.1.dsc
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   dh_auto_build
make[1]: Entering directory '/home/edbarx/simple-netaid-lightweight'
rm -f sn-lightweight
rm -rf obj
gcc -Iinclude `pkg-config --libs --cflags gtk+-2.0` -c
src/auxiliaries.c src/signal_functions.c src/main_gui.c
src/dialog_gui.c src/sn-lightweight.c
mkdir obj
mv *.o obj/
gcc -Iinclude `pkg-config --libs --cflags gtk+-2.0` -o sn-lightweight
obj/auxiliaries.o obj/signal_functions.o obj/main_gui.o
obj/dialog_gui.o obj/sn-lightweight.o
make[1]: Leaving directory '/home/edbarx/simple-netaid-lightweight'
   dh_auto_test
 fakeroot debian/rules binary
dh binary
   dh_testroot
   dh_prep
   dh_auto_install
   dh_install
   dh_installdocs
   dh_installchangelogs
   dh_perl
   dh_link
   dh_compress
   dh_fixperms
   dh_strip
   dh_makeshlibs
   dh_shlibdeps
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libfreetype.so.6 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libcairo.so.2 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libpangoft2-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libatk-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libpangocairo-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libgdk_pixbuf-2.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libfontconfig.so.1 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libpango-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libgdk-x11-2.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/simple-netaid-lightweight/usr/bin/sn-lightweight was not linked
against libgio-2.0.so.0 (it uses none of the library's symbols)
   dh_installdeb
   dh_gencontrol
   dh_md5sums
   dh_builddeb
dpkg-deb: building package `simple-netaid-lightweight' in
`../simple-netaid-lightweight_0.1.1_amd64.deb'.
 dpkg-genchanges  >../simple-netaid-lightweight_0.1.1_amd64.changes
dpkg-genchanges: including full source code in upload
 dpkg-source -i -I --after-build simple-netaid-lightweight
dpkg-buildpackage: full upload; Debian-native package (full source is included)
Now running lintian...
Could not find a profile matching "{VENDOR}/main" for vendor devuan at
/usr/bin/lintian line 979.
Finished running lintian.
Now signing changes and any dsc files...
 signfile 

Re: [DNG] Request for Removal of slim package from Devuan

[KatolaZ]

On Thu, May 26, 2016 at 08:56:03AM +0200, Edward Bartolo wrote:
> Hi,
> 
> I am a user of SLIM. What is wrong with it? I read that it is not
> being actively developed. Does it mean a project has to be
> continuously developed to be used? Aren't bug reports and bug fixes
> NOT enough?
> 
> Software development is like a developing animal. While growing an
> animal is in rapid development but eventually it matures and
> development ceases. The same thing can be said about software
> development. Both a multicellular animal and software are complex and
> far from perfection as BOTH suffer from imperfections and both are on
> the way of continuous development.
> 

and both software and animals will eventually die, if humans, or
nature, or the environment does not cater for them

My2Cents

KatolaZ

-- 
[ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ]
[ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ]
[ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ]
[ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Request for Removal of slim package from Devuan

[Edward Bartolo]

Hi,

I am a user of SLIM. What is wrong with it? I read that it is not
being actively developed. Does it mean a project has to be
continuously developed to be used? Aren't bug reports and bug fixes
NOT enough?

Software development is like a developing animal. While growing an
animal is in rapid development but eventually it matures and
development ceases. The same thing can be said about software
development. Both a multicellular animal and software are complex and
far from perfection as BOTH suffer from imperfections and both are on
the way of continuous development.

Edward

On 25/05/2016, Jaromil  wrote:
> On Wed, 25 May 2016, Dima Krasner wrote:
>
>>slim is far from perfect, that's true. However, "it works" and
>>LightDM can use both ConsoleKit and logind in the version
>>packaged in Jessie, but prefers logind. Other DMs have a hard
>>dependency on logind, or will in the future. We cannot rely on
>>LightDM, in the long term.  Currently, I don't see a longterm
>>solution to this problem, other than maintaining slim or
>>switching to MDM.
>
> ok. well MDM seems very good and Clement was with us back in the early
> days, for sure he is not a systemd fanatic, I doubt he will put an
> hard dependency on it.
>
> worth trying and perhaps maintaining https://github.com/linuxmint/mdm
>
>
> ciao
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng