Re: [DNG] Devuan Jessie 1.0.0 stable release candidate

2017-04-22 Thread メット


On 2017年4月22日 23:26:47 JST, Thaddeus Nielsen  wrote:
>On Fri, 21 Apr 2017 18:14:08 +0200
>Veteran Unix Admins  wrote:
>
>> Dear Init Freedom Lovers,
>> 
>> Once again the Veteran Unix Admins salute you!
>> 
>> Our April 2017 gift to you is the long-awaited release of Devuan
>> Jessie stable release candidate (1.0.0-RC). If all goes as planned,
>> this will be our first Devuan stable release and our first long term
>> support (LTS) release as well.
>> 
>


>Please advise if there is any difference between this release candidate
>and an installed beta release that has been kept up-to-date.
>   RPTN


Thanks a lot for the wonderful work. 
And same question as above.  

Cheers!

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


[DNG] ...

2017-04-22 Thread KatolaZ
https://distrowatch.com/dwres.php?resource=trending

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


Re: [DNG] reportbug, unable to connect to devuan bts

2017-04-22 Thread KatolaZ
On Sat, Apr 22, 2017 at 04:38:06PM -0700, Gregory Nowak wrote:
> Hi all,
> I'm trying to run reportbug, and it tells me it can't connect to
> devuan bts. I can connect to it just fine from the machine in question
> using lynx over http and https. When I run tcpdump while
> running reportbug, I see it's trying to connect to dyne.servus.at over
> https. When I try to connect to https://dyne.servus.at with lynx, I
> get an invalid certificate error, the certificate is for
> bugs.devuan.org. Version of reportbug is 6.6.3+devuan1.3. Thanks.
> 

Hi Greg,

the Devuan version of reportbug is not "complete". It has been
slightly modified to allow sending bug reports to bugs.devuan.org, but
it still lacks some of the functionalities, e.g. looking for existing
reports. In your case, I guess reportbug is trying to retrieve the
reports for the package you specified, and yes, it will fail (I am
still working on that).

You should still be able to send a bug report using reportbug
though. If not, please let me know and we can look at the issue
together.

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


[DNG] reportbug, unable to connect to devuan bts

2017-04-22 Thread Gregory Nowak
Hi all,
I'm trying to run reportbug, and it tells me it can't connect to
devuan bts. I can connect to it just fine from the machine in question
using lynx over http and https. When I run tcpdump while
running reportbug, I see it's trying to connect to dyne.servus.at over
https. When I try to connect to https://dyne.servus.at with lynx, I
get an invalid certificate error, the certificate is for
bugs.devuan.org. Version of reportbug is 6.6.3+devuan1.3. Thanks.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] apulse in experimental

2017-04-22 Thread ael
On Sat, Apr 22, 2017 at 09:10:31PM +0100, KatolaZ wrote:
> On Sat, Apr 22, 2017 at 08:51:30PM +0100, ael wrote:
> 
> [cut]
> 
> > 
> > However, if I use 
> > cmake -DAPULSEPATH=/usr/local/lib/apulse -DCMAKE_INSTALL_PREFIX=/usr 
> > -DCMAKE_BUILD_TYPE=Release ..
> > 
> > then the apulse libraries are properly "hidden" in /usr/local/lib/apulse.
> > 
> > I didn't seem anything like this in the rules for the Devuan package.
> > Did I miss where this is specified?
> >
> 
> it is in debian/rules. 

I thought that I looked there: in the apulse_0.1.9-2.git from the
devuan pool. I didn't see the usual source files there, but maybe I am
out of date.

> 
> > My problems with mpv and mplayer would be explained if this is an
> > oversight in the apulse build. Although it is possible to explicitly
> > specify the audio-device as alsa for these programs, the README.md 
> > file suggests that they should not have tried to use the apulse
> > libraries.
> 
> I still have not understood what is your problem with the apulse
> package (which you said you have not installed). Apulse is not used
> unless you call mpv or mplayer with:

OK. Sorry. As I said earlier, I am still on debian testing. I don't
recall precisely, but I am sure that I just installed the debian apulse
package after someone (you?) posted a note about apulse on this list.
It worked find with firefox, but a day or two later I found the problem
with mpv and mplayer. 

>  $ apulse mpv

As I said, I did *not* use $ apulse mpv, just $ mpv. 

> If your programs experiences problems with pulseaudio, and you have
> not sued the syntax above, the problem is either in your program or in
> pulseadio. 

It was the apulse libraries being dynamically linked by default.

> > Where does the devuan apulse package install 
> > libpulsecommon-5.0.so,libpulse-simple.so,libpulse-simple.so.0,libpulse.sio
> > and libpulse.so.0?
> 
> well, you can find out yourself:
> 
> katolaz@akela:~$ dpkg -L apulse

If I had that package installed :-)

> /usr/lib/x86_64-linux-gnu/apulse
> /usr/lib/x86_64-linux-gnu/apulse/libpulse-simple.so.0
> /usr/lib/x86_64-linux-gnu/apulse/libpulse.so.0
> /usr/lib/x86_64-linux-gnu/apulse/libpulsecommon-5.0.so
> /usr/lib/x86_64-linux-gnu/apulse/libpulse-simple.so
> /usr/lib/x86_64-linux-gnu/apulse/libpulse.so

That looks right. I have done further testing here and mpv does not pick
up the apulse libraries by default in a situation like that.
Maybe the original debian package that I tried was misconfigured. Anyway
Devuan clearly has it right, as usual.

Sorry for the noise.

ael

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


Re: [DNG] apulse in experimental

2017-04-22 Thread KatolaZ
On Sat, Apr 22, 2017 at 08:51:30PM +0100, ael wrote:

[cut]

> 
> However, if I use 
> cmake -DAPULSEPATH=/usr/local/lib/apulse -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=Release ..
> 
> then the apulse libraries are properly "hidden" in /usr/local/lib/apulse.
> 
> I didn't seem anything like this in the rules for the Devuan package.
> Did I miss where this is specified?
>

it is in debian/rules. 

> My problems with mpv and mplayer would be explained if this is an
> oversight in the apulse build. Although it is possible to explicitly
> specify the audio-device as alsa for these programs, the README.md 
> file suggests that they should not have tried to use the apulse
> libraries.

I still have not understood what is your problem with the apulse
package (which you said you have not installed). Apulse is not used
unless you call mpv or mplayer with:

 $ apulse mpv

If your programs experiences problems with pulseaudio, and you have
not sued the syntax above, the problem is either in your program or in
pulseadio. 

> 
> Where does the devuan apulse package install 
> libpulsecommon-5.0.so,libpulse-simple.so,libpulse-simple.so.0,libpulse.sio
> and libpulse.so.0?
> 


well, you can find out yourself:

katolaz@akela:~$ dpkg -L apulse
/.
/usr
/usr/bin
/usr/bin/apulse
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/apulse
/usr/lib/x86_64-linux-gnu/apulse/libpulse-simple.so.0
/usr/lib/x86_64-linux-gnu/apulse/libpulse.so.0
/usr/lib/x86_64-linux-gnu/apulse/libpulsecommon-5.0.so
/usr/share
/usr/share/doc
/usr/share/doc/apulse
/usr/share/doc/apulse/README.Debian
/usr/share/doc/apulse/changelog.Debian.gz
/usr/share/doc/apulse/copyright
/usr/lib/x86_64-linux-gnu/apulse/libpulse-simple.so
/usr/lib/x86_64-linux-gnu/apulse/libpulse.so


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] apulse in experimental

2017-04-22 Thread ael
On Wed, Apr 19, 2017 at 01:08:19PM +0100, KatolaZ wrote:
> On Wed, Apr 19, 2017 at 12:44:32PM +0100, ael wrote:
> 
> [cut]
> > 
> > Unhappily, I am still using debian, and my testing was done on unstable.
> > Obviously I did not invoke mpv (etc) with "apulse mpv", so I was
> > disturbed with it linking to libpulse-simple.so nevertheless.
> > This was on a system with no pulseaudio, only alsa. Maybe putting apulse
> > in its own folder will fix things.
> 
> This is where apulse comes in the scene: if a program requires
> pulseaudio, apulse will lure it into believing that pulseaudio is
> available, but behind the scenes it will use ALSA instead. This is

I have been experimenting with apulse and am confused.

If I build from source using the "default" instructions, the 
libraries seem to be installed in /usr/local/lib/ rather than a
"special hidden" directory. Since /usr/local/lib is specified in
/etc/ld.so.conf.d/libc.conf, this is on the default library path.

However, if I use 
cmake -DAPULSEPATH=/usr/local/lib/apulse -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=Release ..

then the apulse libraries are properly "hidden" in /usr/local/lib/apulse.

I didn't seem anything like this in the rules for the Devuan package.
Did I miss where this is specified?

My problems with mpv and mplayer would be explained if this is an
oversight in the apulse build. Although it is possible to explicitly
specify the audio-device as alsa for these programs, the README.md 
file suggests that they should not have tried to use the apulse
libraries.

Where does the devuan apulse package install 
libpulsecommon-5.0.so,libpulse-simple.so,libpulse-simple.so.0,libpulse.sio
and libpulse.so.0?

Your earlier email suggested that it was somewhere special.

ael

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


Re: [DNG] apulse in experimental

2017-04-22 Thread ael
On Fri, Apr 21, 2017 at 09:28:34AM +1000, Royal Ozma of Oz wrote:
> I think that there is a workaround for mplayer to force it to use ALSA:
> 
> It can be made by adding the file "~/.mplayer/config" with these lines:

I have done a little more investigation. 

First in the apulse source there is a README file which discusses some
of these issues.

Second, I have found that all of mpv, mplayer, vlc and xine have options
to set the audio device to alsa, and they all work with apulse
installed. Those are the only media players that I checked, but probably
many others are similar. ekiga also works with apulse installed.

I compiled from source for these checks: I haven't yet looked at the
package, but I guess the build prefix setting may be important.

ael

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


Re: [DNG] Devuan Jessie 1.0.0 stable release candidate

2017-04-22 Thread Thaddeus Nielsen
On Fri, 21 Apr 2017 18:14:08 +0200
Veteran Unix Admins  wrote:

> Dear Init Freedom Lovers,
> 
> Once again the Veteran Unix Admins salute you!
> 
> Our April 2017 gift to you is the long-awaited release of Devuan
> Jessie stable release candidate (1.0.0-RC). If all goes as planned,
> this will be our first Devuan stable release and our first long term
> support (LTS) release as well.
> 


Please advise if there is any difference between this release candidate
and an installed beta release that has been kept up-to-date.
RPTN

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


Re: [DNG] Devuan Jessie 1.0.0 stable release candidate

2017-04-22 Thread Arnt Karlsen
On Fri, 21 Apr 2017 18:14:08 +0200, Veteran wrote in message 
<20170421161408.ngq4cc7ee2lsy43a@reflex>:

> Official Devuan images are distributed via the website
> (https://files.devuan.org/devuan_jessie_rc/)

..er, try a new upload of devuan_jessie_1.0.0-RC_amd64_DVD.list.gz,
zless output: "
302 Found

302 Found
nginx


devuan_jessie_1.0.0-RC_amd64_DVD.list.gz (END)" and ll sez:
luther@heads /mnt/home/arnt/devuan/installer-iso % ll \
devuan_jessie_1.0.0-RC_*_DVD.list.gz 
-rw-r--r-- 1 luther luther   154 Apr 22 03:48 
devuan_jessie_1.0.0-RC_amd64_DVD.list.gz 
-rw-r--r-- 1 luther luther 42537 Apr 22 03:50 
devuan_jessie_1.0.0-RC_i386_DVD.list.gz




-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng