Re: [DNG] Extreme mail delay

2017-07-20 Thread golinux

On 2017-07-21 00:03, Joachim Fahrner wrote:

Since a few days I'm getting very old mails from this list. Below is
an example Header of such a mail. Someone should have a look at the
mail queue at tupac2.dyne.org.



[cut]


___



Again  . . . those mails were received in a timely manner but stuck in 
'moderation' that hadn't been checked in maybe 8 months.  We're just now 
getting to the end of it.


golinux

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


Re: [DNG] Extreme mail delay

2017-07-20 Thread KatolaZ
On Fri, Jul 21, 2017 at 07:03:08AM +0200, Joachim Fahrner wrote:
> Since a few days I'm getting very old mails from this list. Below is an
> example Header of such a mail. Someone should have a look at the mail
> queue at tupac2.dyne.org.
> 

golinux has replied already on this point: those must be emails which
have been held by mailman, e.g., because the sender address was not
among the ML subscribers.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


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


[DNG] Extreme mail delay

2017-07-20 Thread Joachim Fahrner
Since a few days I'm getting very old mails from this list. Below is an
example Header of such a mail. Someone should have a look at the mail
queue at tupac2.dyne.org.

Received by tupac2.dyne.org (Postfix) with ESMTPS id 42FD118AB89
 for ; Tue, 25 APR 2017 14:08:05 + (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
by tupac2.dyne.org (Postfix) with ESMTP id A231418F1E1;
Thu, 20 JUL 2017 22:20:26 + (UTC)

===

Return-Path: 
Authentication-Results: server.fahrner.name;
dkim=fail reason="signature verification failed" (2048-bit key;
unprotected) header.d=na-work-com.20150623.gappssmtp.com
header.i=@na-work-com.20150623.gappssmtp.com header.b=QfFbUmio;
dkim-adsp=none (unprotected policy); dkim-atps=neutral
X-policyd-weight: using cached result; rate:hard: -6.1
Received: from tupac2.dyne.org (tupac2.dyne.org [178.62.188.7])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits))
(No client certificate requested)
by server.fahrner.name (Postfix) with ESMTPS id BB4C9100DE3
for ; Fri, 21 Jul 2017 00:20:29 +0200 (CEST)
Received: from [127.0.1.1] (localhost [127.0.0.1])
by tupac2.dyne.org (Postfix) with ESMTP id A231418F1E1;
Thu, 20 Jul 2017 22:20:26 + (UTC)
Authentication-Results: tupac2.dyne.org; dkim=fail
reason="verification failed; unprotected key"
header.d=na-work-com.20150623.gappssmtp.com
header.i=@na-work-com.20150623.gappssmtp.com
header.b=QfFbUmio; dkim-adsp=none (unprotected policy);
dkim-atps=neutral
X-Original-To: dng@lists.dyne.org
Delivered-To: dng@lists.dyne.org
Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com
[74.125.82.54])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by tupac2.dyne.org (Postfix) with ESMTPS id 42FD118AB89
 for ; Tue, 25 Apr 2017 14:08:05 + (UTC)
Received: by mail-wm0-f54.google.com with SMTP id w64so23960645wma.0
 for ; Tue, 25 Apr 2017 07:08:05 -0700 (PDT)___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Ansible and Devuan (bug or feature?)

2017-07-20 Thread golinux

On 2017-07-20 17:51, Didier Kryn wrote:

Le 25/04/2017 à 16:08, Emilien Mantel a écrit :

Hi,


Emilien, the date of your mail appears in my browser to be the 25
of April. I cannot believe it has taken 3 months to reach the server
at dng :-) Could you please find the reason and improve on that?

Thanks in advance.

Didier




I can.  No one had moderated the list since late last year.  The recent 
dust up reminded us of that.   ;)


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


Re: [DNG] Ansible and Devuan (bug or feature?)

2017-07-20 Thread Adam Borowski
On Fri, Jul 21, 2017 at 12:51:39AM +0200, Didier Kryn wrote:
> Emilien, the date of your mail appears in my browser to be the 25 of
> April. I cannot believe it has taken 3 months to reach the server at dng :-)
> Could you please find the reason and improve on that?

There's been over ten other mails from January and later received today,
from various authors.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Ansible and Devuan (bug or feature?)

2017-07-20 Thread Didier Kryn

Le 25/04/2017 à 16:08, Emilien Mantel a écrit :

Hi,

Emilien, the date of your mail appears in my browser to be the 25 
of April. I cannot believe it has taken 3 months to reach the server at 
dng :-) Could you please find the reason and improve on that?


Thanks in advance.

Didier


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


Re: [DNG] Install tomcat on devuan

2017-07-20 Thread alberto.se...@tin.it

Yes, I have tried , it's all Ok


Thanks

Alberto


Il 20/07/2017 02:46, Tom Cassidy ha scritto:

There is a tomcat8 package in the repositories. Have you tried that?


On 21 Apr 2017, at 06:22, "alberto.se...@tin.it"  wrote:

Hi to all,

Is it possible install Apache Tomcat on Devuan ?

Alberto Senni

---
Questa e-mail è stata controllata per individuare virus con Avast antivirus.
https://www.avast.com/antivirus

___
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


[DNG] Ansible and Devuan (bug or feature?)

2017-07-20 Thread Emilien Mantel

Hi,

I'm working to adapt my (debian) ansible roles with devuan.

However, i have some problems with facts (setup module).


In Debian Jessie:

"ansible_distribution": "Debian",
"ansible_distribution_major_version": "8",
"ansible_distribution_release": "jessie",
"ansible_distribution_version": "8.7"
"ansible_os_family": "Debian"

In Ubuntu:

"ansible_distribution": "Ubuntu",
"ansible_distribution_major_version": "16",
"ansible_distribution_release": "xenial",
"ansible_distribution_version": "16.04"
"ansible_os_family": "Debian"

In Devuan Jessie (1.0 RC) with vagrant:

"ansible_distribution": "Devuan GNU/Linux",
"ansible_distribution_major_version": "NA",
"ansible_distribution_release": "NA",
"ansible_distribution_version": "1 (jessie)",
"ansible_os_family": "Devuan GNU/Linux"

In Devuan, IMHO should be:

"ansible_distribution": "Devuan",
"ansible_distribution_major_version": "1",
"ansible_distribution_release": jessie",
"ansible_distribution_version": "1.0",
"ansible_os_family": "Debian"


Ansible parses /etc/os-release (see: 
https://github.com/ansible/ansible/blob/5bbf0d9cb679d803072535b9c1d9e0db680633ac/lib/ansible/module_utils/facts.py)


I think, we should update this file?

Are you OK with that?

Cheers,

Emilien

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


Re: [DNG] VBScript Injection via GNOME Thumbnailer

2017-07-20 Thread Adam Borowski
On Tue, Jul 18, 2017 at 08:06:12AM +0200, Joachim Fahrner wrote:
> Another nice bug in Gnome:
> http://news.dieweltistgarnichtso.net/posts/gnome-thumbnailer-msi-fail.html

Actually, it turns out it's not a Gnome component:
Maintainer: Debian Wine Party 
Current upstream: https://github.com/gnome-exe-thumbnailer/gnome-exe-thumbnailer
Original upstream: https://wiki.ubuntu.com/karmic-wine-integration

So the blame is misplaced.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] WICD & DNS & IPv6

2017-07-20 Thread Tom Cassidy


> On 20 Jul 2017, at 18:44, Yevgeny Kosarzhevsky  wrote:
> 
> Hello,
> 
> which connection manager can also work with 3/4g equipment?

NetworkManager offers a GUI for this. Otherwise, wvdial is a console-based 
utility that will connect to USB 3/4g modems.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] [OT] setnet.sh version 0.2.1 released

2017-07-20 Thread Alessandro Selli
On Sun, 8 Jan 2017 at 00:38:45 +
KatolaZ  wrote:

[...]

>   - added a manpage

  Love this.


  Bye,


-- 
Alessandro Selli http://alessandro.route-add.net
VOIP SIP: dhatarat...@ekiga.net
Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] VBScript Injection via GNOME Thumbnailer

2017-07-20 Thread Olaf Meeuwissen
Hi,

Adam Borowski writes:

> On Wed, Jul 19, 2017 at 08:28:25PM +0900, Olaf Meeuwissen wrote:
>> Adam Borowski writes:
>> > On Tue, Jul 18, 2017 at 10:07:35PM +0200, Adam Borowski wrote:
>> >> Actually, imagemagick is one of worst offenders here.  The version in 
>> >> Jessie
>> >> is at deb8u9, and every security update tends to mention ~20 CVEs.
>> >
>> > ... nd, just hours later, here comes deb8u10:
>> >
>> > # Package: imagemagick
>> > # CVE ID : CVE-2017-9439 CVE-2017-9440 CVE-2017-9500 CVE-2017-9501
>> > #  CVE-2017-10928 CVE-2017-11141 CVE-2017-11170
>> > #  CVE-2017-11360 CVE-2017-11188
>> > # Debian Bug : 863126 867367 867778 867721 864273 864274 867806 868264
>> > #  868184 867810 867808 867811 867812 867896 867798 867821
>> > #  867824 867825 867826 867893 867823 867894 867897
>>
>> Totally untested, but you might try to replace imagemagick with
>> graphicsmagick.  It's at deb8u ;-)

My bad, graphicsmagick is at deb8u2.  Are the security conscious just
picking on imagemagick or graphicsmagick is less susceptible?  Dunno.

> It's a fork, so it suffers from same vulnerabilities as imagemagick.  It
> might get better only after someone rewrites everything from scratch (in
> which case there'll be a whole new set of bugs).

Devuan is a fork of Debian.  I think we both agree that the former
suffers at least one problem less than the latter ;-)

By the same or at least a very similar token, I would hope that perhaps
graphicsmagick suffers from a few less vulnerabilities than imagemagick.
True, I have no hard data to back that up.  It was just a suggestion.

I've used the CLI and library C/C++ APIs of both in the past, and
through that have developed a better opinion of graphicsmagick.  It was
forked 15(!) years ago.  ImageMagick has had a reputation of willy-nilly
changing CLI and library APIs as well as image processing results
between versions.  GraphicsMagick has on the whole been a lot more
stable in that respect so I would *guess* that its developers have been
able to shake out most vulnerabilities over the years without
introducing many new ones.

Just a thought,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
  Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] WICD & DNS & IPv6

2017-07-20 Thread Alessandro Selli
On Wed, 19 Jul 2017 at 20:41:25 +0200
Joachim Fahrner  wrote:

> Hi,
> since Gnome network manager depends on systemd, I have to use wicd on my 
> notebook. And since my internet provider does not allow to change dns 
> setting on their router, I only can change it on my notebook.
> But wicd does not accept ipv6 addresses in the dns fields. Is there some 
> other way to supersede the dhclient dns settings on Devuan?

  You can set name servers by hand in /etc/dhcp/dhclient.conf.
Would you want to prevent the DHCP daemon to set them, you could set a line
like:

request subnet-mask, broadcast-address, time-offset, routers,
domain-name, host-name;

(that is, you leave out "domain-name-servers") and then you can set your own
resolvers with:

append domain-name-servers ::ip:address:dns1, ::ip:address:dns2;

Or you could take the DHCPD's server and prepend your own with a line like
the abose with "prepend" instead of "append".  I hope it's going to work with
IPv6 addresses too, I never tried it with those.


  Bye,


-- 
Alessandro Selli http://alessandro.route-add.net
VOIP SIP: dhatarat...@ekiga.net
Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Motion to moderate

2017-07-20 Thread Alessandro Selli
On Wed, 19 Jul 2017 at 20:24:59 +0200 (CEST)
 wrote:

[...]

> ps -- I'm starting to wonder what you guys do here...
>

  Practising my Del-key kung-fu master expertize.


  Greetz,


-- 
Alessandro Selli http://alessandro.route-add.net
VOIP SIP: dhatarat...@ekiga.net
Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] WICD & DNS & IPv6

2017-07-20 Thread Yevgeny Kosarzhevsky
Hello,

which connection manager can also work with 3/4g equipment?

On 20 July 2017 at 16:24, Antony Stone 
wrote:

> On Thursday 20 July 2017 at 07:18:34, Joachim Fahrner wrote:
>
> > Am 2017-07-19 22:21, schrieb Antony Stone:
> > > Also, "some network problems" is not a very helpful bug report :)
> > >
> > > If you're going to say that something doesn't work properly, please at
> > > least say *how* it doesn't work properly...
> >
> > I'm sorry, but I did not have the time to investigate this further.
> > There were intermittent connectivity problems. Since they never happened
> > with wicd, the easiest way was to switch back to wicd. Intermittent
> > connectivity problems are extremely difficult to analyze, because you
> > cannot reproduce them on demand. So how would you describe them for a
> > bug report?
>
> Well, "intermittent connectivity" is a good start :)
>
> "Some network problems" could mean anything - connectivity, latency,
> bandwidth, CPU usage, changing IP addresses... the list goes on.
>
> Any detail at all is better than no detail.
>
>
> Antony.
>
> --
> "this restriction will not apply in the event of the occurrence (certified
> by
> the United States Centers for Disease Control or successor body) of a
> widespread viral infection transmitted via bites or contact with bodily
> fluids
> that causes human corpses to reanimate and seek to consume living human
> flesh,
> blood, brain or nerve tissue and is likely to result in the fall of
> organized
> civilization."
>
>  - https://aws.amazon.com/service-terms/ paragraph 57.10
>
>Please reply to the
> list;
>  please *don't* CC
> me.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>



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


Re: [DNG] virtualbox-dkms fails to build on Devuan

2017-07-20 Thread KatolaZ
On Thu, Jul 20, 2017 at 09:22:24AM +0200, Jaromil wrote:

[cut]

> 
> the we-are-not-so-sure solution is to add to our base-files package
> this symlink OR an additional /etc/debian_release containing the
> corresponding base distro we use, OR something else we may come up
> with.
> 

This could work on new installs, but must be done with care on systems
which have been upgraded form Debian, since they already have
debian_release. 

My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


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


Re: [DNG] Install tomcat on devuan

2017-07-20 Thread Jaromil
On Thu, 20 Apr 2017, alberto.se...@tin.it wrote:

> Hi to all,
> 
> Is it possible install Apache Tomcat on Devuan ?

yes, the same instructions to install Tomcat on Debian should apply
just fine. if they refer to systemd then just pick an older guide.

ciao

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


Re: [DNG] virtualbox-dkms fails to build on Devuan

2017-07-20 Thread Jaromil

dear Thaddeus,

On Sat, 25 Mar 2017, Thaddeus Nielsen wrote:

>   Greetings!  I have been using Devuan Jessie 1.0 Beta2 for nearly
> two months.  I regularly update the system.  Once I had virtualbox
> running fine but then removed it.  Since then the kernel has been
> upgraded at least twice.  I have reinstalled virtualbox and all the
> components are working except virtualbox-dkms fails to build.

this is due to the fact virtualbox has introduced new distro checks
that are ignoring the existance of devuan.

the quick solution is

# ln -s /etc/devuan_version /etc/debian_version

the lenghty solution is to send a patch to virtualbox developers
adding devuan to the check right before or after debian.

the we-are-not-so-sure solution is to add to our base-files package
this symlink OR an additional /etc/debian_release containing the
corresponding base distro we use, OR something else we may come up
with.

If there are expert opinions on this issue, I'd like to debate the
third solution and perhaps act upon it since this problem does affects
also other packages.

ciao




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


Re: [DNG] WICD & DNS & IPv6

2017-07-20 Thread KatolaZ
On Thu, Jul 20, 2017 at 09:06:17AM +0200, Didier Kryn wrote:
> Le 19/07/2017 à 20:41, Joachim Fahrner a écrit :
> >Hi,
> >since Gnome network manager depends on systemd, I have to use wicd on my
> >notebook. And since my internet provider does not allow to change dns
> >setting on their router, I only can change it on my notebook.
> >But wicd does not accept ipv6 addresses in the dns fields. Is there some
> >other way to supersede the dhclient dns settings on Devuan?
> 
> Jochen,
> 
> I just suggest you google (or duckduck) about how to configure
> wpa-supplicant for roaming, and install wpa-gui. Get rid of both
> network-manager and wicd. You don't need them.
> 


Or, maybe, just give a go to setnet:

  http://kalos.mine.nu/setnet/

It's in the Devuan experimental repo as well.

My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


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


Re: [DNG] WICD & DNS & IPv6

2017-07-20 Thread Didier Kryn

Le 19/07/2017 à 20:41, Joachim Fahrner a écrit :

Hi,
since Gnome network manager depends on systemd, I have to use wicd on 
my notebook. And since my internet provider does not allow to change 
dns setting on their router, I only can change it on my notebook.
But wicd does not accept ipv6 addresses in the dns fields. Is there 
some other way to supersede the dhclient dns settings on Devuan?


Jochen,

I just suggest you google (or duckduck) about how to configure 
wpa-supplicant for roaming, and install wpa-gui. Get rid of both 
network-manager and wicd. You don't need them.


 Didier

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


Re: [DNG] Hello says 'idonis'

2017-07-20 Thread Dave Turner

On 20/07/17 05:45, KatolaZ wrote:

On Wed, Jul 19, 2017 at 09:12:11PM -0400, Steve Litt wrote:

[cut]


Ismael was first asked to fill out a bug report, without the added text
"at bugs.devuan.org". Sounds simple to you, but an unnecessary time
waster for him. Those four words should be included with every request
for bug tracking.

Hi Steve,

I don't know where you picked this from. Every time I ask anybody to
file a bug, I always say: "Please file a bug report at
http://bugs.devuan.org, i.e. by using the 'reportbug' tool".

[cut]


You know, I've had situations where I found a bug, asked a few
questions, solved the bug, wrote the solution on the mailing list,
marked it , and was then asked to jump through a bugtracker's
hoops to re-record it. I went on to other things.


Steve, has this ever happened to you in Devuan? The answer is: NO. So
please, do not bring here your past bad experience with other
communities, mixing it with unrelated comments about other bad
experiences in unrelated contexts :)

We are here to try to solve Devuan's problems, not to overburden the
users with rants about how that specific developer harassed me when I
failed to specify in my bug report that I was using X,Y,Z.

Reporting bugs, and keeping bug reports tidy, is vital to solving
bugs, like it or not. People keep asking what they can do in practice
for Devuan if they can't develop new things, or maintain packages. The
one thing I can suggest is:


  ** learn how to report bugs, report as many bugs as possible, help
  ** with triaging them, help with solving them if you can, help other
  ** people who are venturing on the same path.


The problem with reporting bugs in a ML like DNG, which has an average
of 6000+ messages per year, is that they simply get *lost*.

And acknowledging a bug report on a ML like DNG is useless, since
users will think that they have successfully helped Devuan, only to
discover that their bug was not solved in the end, just because it got
forgotten among 500 other emails about how to cook a perfect goulash
or how to shoot a woodpecker from a 100ft distance.

Helping a community costs some effort, because "helping" is just about
doing some work yourself on behalf of somebody else.


[cutting-40-lines-of-unrelated-rant-about-BTSs...]


To summarize: Many people use ten or twenty different pieces of Free
Software. Each piece has its own "bug tracker" with its own URL and
rules and demanded info. Some even refuse to go farther if something
isn't put in: It's like "ha ha sucker, we wasted your time. Wanna go
double or nothing?" I think the Free Software world will be much more
efficient if the User is thanked for submitting a good and complete
symptom description, without having to know project specific
information.
  

A good and complete symptom description *is* a bug report. But
anything like "UTF does not work in Devuan under X" is neither a
complete symptom description nor a bug report. It's just a rant. And
we don't need rants, because we have already plenty of them and rants
have no solutions. We need bug reports, since we have a lot of bugs
and bugs usually do have solutions.

My2Cents

KatolaZ



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


Steve may have wittered on a bit but the point he makes is correct. Most 
of the users of devuan are not sad techie geeks. What seems normal and 
natural and easy to you is firmly in 'WTF' territory for normal people.


I have made bug reports for other distributions both linux and BSD, 
dashed hard work! Handling it through careful questioning on a mailing 
list is by far the best way to get to the root cause of the problem so 
it can be passed on to someone who can deal with it.


But anything like "UTF does not work in Devuan under X" is neither a complete symptom description nor a bug report. 


True, it is the starting point for careful questioning. OpenBSD always 
asks for the complete dmesg to be posted.


DaveT

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


Re: [DNG] WICD & DNS & IPv6

2017-07-20 Thread Joachim Fahrner

Am 2017-07-19 22:21, schrieb Antony Stone:


Also, "some network problems" is not a very helpful bug report :)

If you're going to say that something doesn't work properly, please at 
least

say *how* it doesn't work properly...


I'm sorry, but I did not have the time to investigate this further. 
There were intermittent connectivity problems. Since they never happened 
with wicd, the easiest way was to switch back to wicd. Intermittent 
connectivity problems are extremely difficult to analyze, because you 
cannot reproduce them on demand. So how would you describe them for a 
bug report?


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