Re: php.ini ignored

[Peter Wiersig]

Andrew Wood  writes:
> Configuration File (php.ini) Path /etc/php/7.0/apache2
> Loaded Configuration File /etc/php/7.0/apache2/php.ini
> Scan this dir for additional .ini files   /etc/php/7.0/apache2/conf.d

IIRC the latter files override the main config file. So if your changes
in apache2/php.ini are ignored, check if they are in any of the conf.d
files.

Peter

Re: Solved, maybe (was: Re: Help updating a Jessie installation to Jessie LTS)

[David]

On Mon, 1 Apr 2019 at 09:56, David Wright  wrote:
>
> I hit this bizarre page that has a comparable multitude of possibilities.
> https://stackoverflow.com/questions/212466/what-is-a-bus-error

The "bizarre" that I'm seeing on that page is probably due to
today's date being April 1st in some parts of the world.

Re: Installing Debian root on ZFS mirror NetBoot

[Matthew Crews]

On 3/31/19 3:12 PM, David Christensen wrote:
> On 3/31/19 12:45 AM, Mimiko wrote:
>> Hello.
>>
>> I know that ZFS is not well supported as MD raids. All I've found on
>> internet on installing Debian on ZFS is using a live disk.
>>
>> My goal is to boot from network and install Debian root on ZFS raid
>> mirror. I can do this using MD raid. I am searching for suggestions of
>> how to enable ZFS during installing from network and partition disks
>> using ZFS.
>>
>> Any suggestion and ideas a welcome.
> 
> I migrated my SOHO file server to FreeBSD specifically for ZFS.  While
> FreeBSD rocks as a server OS, I find that graphical desktops are better
> on Debian.  On Debian, I use BTRFS.  I also use only one device for the
> system drive, and keep it small (16 GB SSD and USB flash drives) to
> facilitate taking, storing, and restoring images.
> 
> 
> David
> 

Step-by-step instructions are found here:

https://github.com/zfsonlinux/zfs/wiki/Debian-Stretch-Root-on-ZFS

Fwd: FISL - Fórum Internacional Software Livre

[José de Figueiredo]

Pesquisa sobre FISL. pode ser interessante contribuir !

abraços.



 Mensagem encaminhada 
Assunto:FISL - Fórum Internacional Software Livre
Data:   Sun, 31 Mar 2019 22:01:18 +
De: pesqu...@softwarelivre.org via SurveyMonkey

Responder a:"pesqu...@softwarelivre.org"@passofundo.ifsul.edu.br
Para:   jose.figueir...@passofundo.ifsul.edu.br



 
        FISL - Fórum Internacional Software Livre        
 
 
    

Este é um questionário de pesquisa e sua participação é importante.
Responda abaixo. Agradecemos sua participação!

 
 

Você já esteve no FISL como público, palestrante, visitante,
patrocinador, expositor ou grupo de usuários, nos últimos 10 anos ? 
 
◯

Sim



 
◯

Não



 
    

Não encaminhe este email, pois este link de questionário é exclusivo
para a sua conta.
Privacidade  |
Cancelar assinatura


 
 
Desenvolvido pela   SurveyMonkey Logo

 

<>

Nettoyage du spam : mars 2019

[Jean-Pierre Giraud]

Bonjour,
Comme nous sommes en avril, il est désormais possible de
traiter les archives du mois de mars 2019 des listes francophones.

N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs
pour que nous sachions où nous en sommes.

Détails du processus de nettoyage du spam sur :

https://wiki.debian.org/I18n/FrenchSpamClean

Re: Solved, maybe (was: Re: Help updating a Jessie installation to Jessie LTS)

[David Wright]

On Sun 31 Mar 2019 at 16:35:44 (-0400), rhkra...@gmail.com wrote:
> On Saturday, March 30, 2019 04:12:05 PM rh kramer wrote:
> > I already made an attempt, and I'm a little worried that I may have messed
> > things up -- I'd like to try to recover and get back to a reliable Jessie
> > system.

Saw your post too late to help much.

> Things might be OK.  Things I did:
> 
>* googled for errorackage -- found some pages but not much help -- some 
> pages gave long lists of instructions to try, but it sounded more like a 
> shotgun approach than any real knowledge based thing.  Some people thought it 
> meant a hardware bus error, some thought some kind of memory problem 
> (hardware 
> or not), others just suggested commands to try -- maybe there is a better 
> page 
> out there that I didn't find

I hit this bizarre page that has a comparable multitude of possibilities.
https://stackoverflow.com/questions/212466/what-is-a-bus-error

>* Aside: what the heck does errorackage mean / stand for and what is it 
> telling me?  Who came up with that "word"?

In school arithmetical notation:

Reading package lists... 89%+
Bus error

Bus errorackage lists... 89%
===-

>* I edited sources.list to get rid of the jessie-updates (I don't think 
> that did anything significant with respect to the errorackage error)
> 
>* I did a df and found /boot and /var close to full, I examined /var 
> expecting to find a lot of space used for the apt archives, but instead there 
> was a bunch of stuff (in /var/tmp as opposed to /var/cache/apt/archives) 
> related to mkinit... (I'm writing from a different computer, so I couldn't 
> copy 
> and paste) -- something like over 1.5 GB -- deleted all that, then did:

Yes, that's one of the options in that page, but the link to the
report is broken:

for me the partition containing /var/cache was simply full
https://askubuntu.com/a/915520/493379

> apt-get update
> 
> apt-get upgrade
> 
> That seemed to work pretty well, I mean, it seemed to install everything 
> except the new linux kernel which was held back.
> 
> tried:
> 
> apt-get dist-upgrade
> 
> Found a message in there that said a partition / filesystem was out of space 
> -- 
> /var looked ok, so cleared out some space in /boot by deleting an old kernel 
> (something like n.n.n -04)
> 
> tried 
> 
> apt-get dist-upgrade 
> 
> This time saw a message that it didn't work and suggested that I try  apt-get 
> -f install 
> 
> instead, I tried
> 
> apt-get -f dist-upgrade
> 
> That seemed to work, so things may be ok -- I guess I'll have to watch the 
> system for a while and think about rebooting (to put the new kernel in 
> service).

> > What I did and why:
> > 
> > I understood from some other posts on the list that the mirrored
> > repositories for Wheezy and Jessie went away in early March, so (for
> > Jessie) I found a post that told me what the content of
> > /etc/apt/sources.list should be for Jessie LTS.

Yes, on my two legacy jessie systems, I cut sources.list down to:

# this was wheezy and was upgraded to jessie
#deb cdrom:[Debian GNU/Linux 7.1.0 _Wheezy_ - Official i386 NETINST Binary-1 
20130615-21:53]/ wheezy main
deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free

I figured that sources were of no use to me.

I also took out all the backports packages because, for example,
I no longer do video manipulation with ffmpeg on these machines.
After finding which packages with apt-show-versions, I reinstalled
them with
# apt-get -s -o Acquire::http::Proxy="http://192.168.1.17:3142/; install 
foo=1.2.3
using the -s option at first to make sure I grouped their removal
where necessary.

So now my jessie systems are clean apart from xtoolwait from squeeze
and fonts-hack-ttf from stretch, both with no dependencies.

> > Oh, an extra credit question: are there mirrors I can use for Jessie LTS or
> > must I use debian.org?  If there are mirrors I can use, where would I find
> > those?

ftp.us.debian.org has always worked for me (eg wheezy until late last year).

Cheers,
David.

Re: Solved, maybe (was: Re: Help updating a Jessie installation to Jessie LTS)

[Andy Smith]

Hello,

On Sun, Mar 31, 2019 at 04:35:44PM -0400, rhkra...@gmail.com wrote:
>* Aside: what the heck does errorackage mean / stand for and what is it 
> telling me?  Who came up with that "word"?

Ah, I thought you were aware of what it was printing. It was printing
"Bus error" over the top of its normal output, which was presumably
something about "Package". Hence "Bus errorackage".

If everything works now then it seems quite likely that apt was
getting a bus error because of your filesystem(s) being full. That's
a pleasing outcome since now you don't have to test your memory,
power supply, etc etc!

If you can reproduce that i think it would be worth a bug report,
because it's really not nice to see "bus error".

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: debian packes broken

[Andy Smith]

Hi Manikanta,

On Sun, Mar 31, 2019 at 09:51:32PM +0530, manikanta bandaru wrote:
> Err http://deb.debian.org jessie-updates/main amd64 Packages

jessie-updates doesn't exist any more; remove any lines referring to
"jessie-updates" (NOT "jessie/updates") from your
/etc/apt/sources.list and do "apt update", and think about when you
are going to upgrade. :)

This message hints that there will be no further uploads to
jessie-updates:

https://lists.debian.org/debian-announce/2018/msg2.html

though it does not come out and say it explicitly. Unfortunately the
only explicit official announcement of the removal I saw was at:

https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

which is probably not a mailing list that too many users subscribe
to.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Help updating a Jessie installation to Jessie LTS

[Andy Smith]

Hi,

On Sat, Mar 30, 2019 at 04:12:05PM -0400, rh kramer wrote:
> I found a post that told me what the content of
> /etc/apt/sources.list should be for Jessie LTS.

LTS updates (for a limited set of architectures) make their way into
the /updates suite that is found on
security.debian.org, just like the normal security updates used to.
Therefore you do not need to change your /etc/apt/sources.list just
to use LTS.

You *may* need to modify sources.list to remove references to
-updates (note the '-', not a '/') as that suite was
used to contain packages for point releases, and is removed when the
distribution is no longer being updated by Debian.

When that suite is removed, all of its contents have already been
put into the regular  suite at the last point release
of that distribution.

There is some talk of in future not entirely deleting the
-updates directory from the mirrors, but instead
leaving it present and empty. This would be to prevent error
messages in apt clients doing an update and finding the directory no
longer present. It would have no functional effect as all the
packages from that suite would already be in the 
suite.

Eventually when the distribution is long out of support, it is
entirely deleted from the main Debian mirrors and only becomes
available from archive.debian.org.

> I think I need to remove the references to jessie-updates from the
> sources.list file.  But, I'm fairly sure that won't solve what
> looks to me like the bigger problem:
> 
> root@s31:~# apt-get upgrade
> Bus errorackage lists... 1%

That looks very bad and is indicative of a serious software error or
hardware problem.

I doubt that has anything to do with your use of "jessie-updates" in
your sources.list, even though the "jessie-updates" lines shouldn't
be there any more.

When did this start happening?

Can you think of anything you may have done that alters the
"apt-get" binary?

Does it still happen when you use just "apt" or "aptitude"?

> Oh, an extra credit question: are there mirrors I can use for Jessie LTS or
> must I use debian.org?  If there are mirrors I can use, where would I find
> those?

Since LTS packages end up in /updates, you can use the
normal Debian mirror network for security. So that's
security.debian.org or the equivalent as listed by
http://deb.debian.org/

> Here is what I put in the sources.list file:

Looks correct except remove the "jessie-updates" lines.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Installing Debian root on ZFS mirror NetBoot

[David Christensen]

On 3/31/19 12:45 AM, Mimiko wrote:

Hello.

I know that ZFS is not well supported as MD raids. All I've found on 
internet on installing Debian on ZFS is using a live disk.


My goal is to boot from network and install Debian root on ZFS raid 
mirror. I can do this using MD raid. I am searching for suggestions of 
how to enable ZFS during installing from network and partition disks 
using ZFS.


Any suggestion and ideas a welcome.


I migrated my SOHO file server to FreeBSD specifically for ZFS.  While 
FreeBSD rocks as a server OS, I find that graphical desktops are better 
on Debian.  On Debian, I use BTRFS.  I also use only one device for the 
system drive, and keep it small (16 GB SSD and USB flash drives) to 
facilitate taking, storing, and restoring images.



David

Solved, maybe (was: Re: Help updating a Jessie installation to Jessie LTS)

[rhkramer]

On Saturday, March 30, 2019 04:12:05 PM rh kramer wrote:
> I already made an attempt, and I'm a little worried that I may have messed
> things up -- I'd like to try to recover and get back to a reliable Jessie
> system.

Things might be OK.  Things I did:

   * googled for errorackage -- found some pages but not much help -- some 
pages gave long lists of instructions to try, but it sounded more like a 
shotgun approach than any real knowledge based thing.  Some people thought it 
meant a hardware bus error, some thought some kind of memory problem (hardware 
or not), others just suggested commands to try -- maybe there is a better page 
out there that I didn't find

   * Aside: what the heck does errorackage mean / stand for and what is it 
telling me?  Who came up with that "word"?

   * I edited sources.list to get rid of the jessie-updates (I don't think 
that did anything significant with respect to the errorackage error)

   * I did a df and found /boot and /var close to full, I examined /var 
expecting to find a lot of space used for the apt archives, but instead there 
was a bunch of stuff (in /var/tmp as opposed to /var/cache/apt/archives) 
related to mkinit... (I'm writing from a different computer, so I couldn't copy 
and paste) -- something like over 1.5 GB -- deleted all that, then did:

apt-get update

apt-get upgrade

That seemed to work pretty well, I mean, it seemed to install everything 
except the new linux kernel which was held back.

tried:

apt-get dist-upgrade

Found a message in there that said a partition / filesystem was out of space -- 
/var looked ok, so cleared out some space in /boot by deleting an old kernel 
(something like n.n.n -04)

tried 

apt-get dist-upgrade 

This time saw a message that it didn't work and suggested that I try  apt-get 
-f install 

instead, I tried

apt-get -f dist-upgrade

That seemed to work, so things may be ok -- I guess I'll have to watch the 
system for a while and think about rebooting (to put the new kernel in 
service).

> 
> What I did and why:
> 
> I understood from some other posts on the list that the mirrored
> repositories for Wheezy and Jessie went away in early March, so (for
> Jessie) I found a post that told me what the content of
> /etc/apt/sources.list should be for Jessie LTS.
> 
> I then ran apt-get update and apt-get upgrade below are the results.
> 
> I think I know how to fix one part of the problem -- I think I need to
> remove the references to jessie-updates from the sources.list file.  But,
> I'm fairly sure that won't solve what looks to me like the bigger problem:
> 
> root@s31:~# apt-get upgrade
> Bus errorackage lists... 1%
> root@s31:~#
> 
> Oh, an extra credit question: are there mirrors I can use for Jessie LTS or
> must I use debian.org?  If there are mirrors I can use, where would I find
> those?
> 
> Here is what I put in the sources.list file:
> 
> from an email: On 2019-03-26, Pierre Fourès 
> wrote: ...
> 
> For Jessie LTS "/etc/apt/sources.list should look like this one:"
> 
>  deb http://deb.debian.org/debian/ jessie main contrib non-free
>  deb-src http://deb.debian.org/debian/ jessie main contrib non-free
> 
>  deb http://security.debian.org/ jessie/updates main contrib non-free
>  deb-src http://security.debian.org/ jessie/updates main contrib non-free
> 
>  deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
>  deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
> 
> Here are the results I got from running apt-get update and then apt-get
> upgrade:
> 
> 
> root@s31:~# apt-get update
> Ign http://deb.debian.org jessie
> InRelease
> Hit http://security.debian.org jessie/updates
> InRelease
> Ign http://deb.debian.org jessie-updates InRelease
> Get:1 http://deb.debian.org jessie Release.gpg [2,420 B]
> Ign http://deb.debian.org jessie-updates Release.gpg
> Get:2 http://security.debian.org jessie/updates/main Sources [305 kB]
> Get:3 http://deb.debian.org jessie Release [148
> kB]
> Hit http://security.debian.org jessie/updates/contrib Sources
> Hit http://security.debian.org jessie/updates/non-free Sources
> Get:4 http://security.debian.org jessie/updates/main amd64 Packages [664
> kB] Ign http://deb.debian.org jessie-updates
> Release
> Get:5 http://deb.debian.org jessie/main Sources [7,063 kB]
> Hit http://security.debian.org jessie/updates/contrib amd64
> Packages
> Hit http://security.debian.org jessie/updates/non-free amd64
> Packages
> Hit http://security.debian.org jessie/updates/contrib
> Translation-en
> Get:6 http://security.debian.org jessie/updates/main Translation-en [335
> kB]
> Hit http://security.debian.org jessie/updates/non-free
> Translation-en
> Get:7 http://deb.debian.org jessie/contrib Sources [50.4
> kB]
> Get:8 http://deb.debian.org jessie/non-free Sources [99.2
> kB]
> Get:9 http://deb.debian.org jessie/main amd64 Packages [6,818
> kB]
> Get:10 http://deb.debian.org jessie/contrib amd64 Packages [49.8
> kB]
> Get:11 http://deb.debian.org 

Re: php.ini ignored

[Andrew Wood]

On 31/03/2019 20:56, Sven Hartge wrote:



Are using libapache2-mod-php7.0 or are you using php7.0-cgi or
php7.0-fpm?

Depending on the way PHP is executed, different php.ini-files are used.

Grüße,
S!


mod_php


Server API  Apache 2.0 Handler
Virtual Directory Support   disabled
Configuration File (php.ini) Path   /etc/php/7.0/apache2
Loaded Configuration File   /etc/php/7.0/apache2/php.ini
Scan this dir for additional .ini files /etc/php/7.0/apache2/conf.d
Additional .ini files parsed 
/etc/php/7.0/apache2/conf.d/10-mysqlnd.ini, 
/etc/php/7.0/apache2/conf.d/10-opcache.ini, 
/etc/php/7.0/apache2/conf.d/10-pdo.ini, 
/etc/php/7.0/apache2/conf.d/15-xml.ini, 
/etc/php/7.0/apache2/conf.d/20-calendar.ini, 
/etc/php/7.0/apache2/conf.d/20-ctype.ini, 
/etc/php/7.0/apache2/conf.d/20-dom.ini, 
/etc/php/7.0/apache2/conf.d/20-exif.ini, 
/etc/php/7.0/apache2/conf.d/20-fileinfo.ini, 
/etc/php/7.0/apache2/conf.d/20-ftp.ini, 
/etc/php/7.0/apache2/conf.d/20-gettext.ini, 
/etc/php/7.0/apache2/conf.d/20-iconv.ini, 
/etc/php/7.0/apache2/conf.d/20-imagick.ini, 
/etc/php/7.0/apache2/conf.d/20-json.ini, 
/etc/php/7.0/apache2/conf.d/20-mbstring.ini, 
/etc/php/7.0/apache2/conf.d/20-mysqli.ini, 
/etc/php/7.0/apache2/conf.d/20-pdo_mysql.ini, 
/etc/php/7.0/apache2/conf.d/20-phar.ini, 
/etc/php/7.0/apache2/conf.d/20-posix.ini, 
/etc/php/7.0/apache2/conf.d/20-readline.ini, 
/etc/php/7.0/apache2/conf.d/20-shmop.ini, 
/etc/php/7.0/apache2/conf.d/20-simplexml.ini, 
/etc/php/7.0/apache2/conf.d/20-sockets.ini, 
/etc/php/7.0/apache2/conf.d/20-sysvmsg.ini, 
/etc/php/7.0/apache2/conf.d/20-sysvsem.ini, 
/etc/php/7.0/apache2/conf.d/20-sysvshm.ini, 
/etc/php/7.0/apache2/conf.d/20-tokenizer.ini, 
/etc/php/7.0/apache2/conf.d/20-wddx.ini, 
/etc/php/7.0/apache2/conf.d/20-xmlreader.ini, 
/etc/php/7.0/apache2/conf.d/20-xmlwriter.ini, 
/etc/php/7.0/apache2/conf.d/20-xsl.ini

Re: php.ini ignored

[Sven Hartge]

Andrew Wood  wrote:

> Im using PHP 7 with Apache on Stretch. According to phpinfo() the ini
> file is /etc/php/7.0/apache2/php.ini but changes to this file are not
> reflected in the output of phpinfo() (I am restarting Apache).

> Ive even tried creating a synax error in there and it didnt complain.

Are using libapache2-mod-php7.0 or are you using php7.0-cgi or
php7.0-fpm?

Depending on the way PHP is executed, different php.ini-files are used.

Grüße,
S!

-- 
Sigmentation fault. Core dumped.

php.ini ignored

[Andrew Wood]

Im using PHP 7 with Apache on Stretch. According to phpinfo() the ini 
file is /etc/php/7.0/apache2/php.ini but changes to this file are not 
reflected in the output of phpinfo() (I am restarting Apache).


Ive even tried creating a synax error in there and it didnt complain.

Any ideas?

Re: mutt imap_headers [solved]

[Jochen Spieker]

Nick:
> On 2019-03-31 17:07 BST, Nick wrote:
>> 
>> The not so good: no marker appears until I open messages.  I
>> had expected that my imap_headers setting would cause the marker to
>> appear on all the qualifying messages in the index.  How can I make
>> that happen?
> 
> Solved: close mutt, delete .hcache files under ~/.mutt/cache, reopen
> mutt.  Thanks to kevin8t8 in freenode #mutt.

Thanks! Now that you mention it, I think I was bitten by this earlier in
a similar context.

J.
-- 
The news at ten makes me peevish but animal hospital makes me cry.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: mutt imap_headers [solved]

[Nick]

On 2019-03-31 17:07 BST, Nick wrote:
> The not so good: no marker appears until I open messages.  I
> had expected that my imap_headers setting would cause the marker to
> appear on all the qualifying messages in the index.  How can I make
> that happen?

Solved: close mutt, delete .hcache files under ~/.mutt/cache, reopen
mutt.  Thanks to kevin8t8 in freenode #mutt.
-- 
Nick

debian packes broken

[manikanta bandaru]

Hi,

Please see broken packages mirror list:

root@13c65d59e924:/#  apt-get update
Ign http://deb.debian.org jessie InRelease
Ign http://deb.debian.org jessie-updates InRelease
Hit http://deb.debian.org jessie Release.gpg
Hit http://security.debian.org jessie/updates InRelease
Ign http://deb.debian.org jessie-updates Release.gpg
Hit http://deb.debian.org jessie Release
Ign http://deb.debian.org jessie-updates Release
Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages

Err http://deb.debian.org jessie-updates/main amd64 Packages
  404  Not Found
Get:1 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Get:2 http://security.debian.org jessie/updates/main amd64 Packages [825 kB]
Fetched 9923 kB in 38s (259 kB/s)
W: Failed to fetch
http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages
404  Not Found

E: Some index files failed to download. They have been ignored, or old ones
used instead.

-- 

*Regards*
*Manikanta Bandaru*
*http://in.linkedin.com/pub/manikanta-bandaru/1a/b09/4bb/
*

Re: python 3 : error with lib scipy

[tomas]

On Sun, Mar 31, 2019 at 06:29:20PM +0200, Laurent Debian wrote:
> Hi,
> Le dim. 31 mars 2019 à 16:01,  a écrit :

[...]

> > Are you sure you've got python3-numpy installed?
> >
> yes and I can load numpy  perfectly well
> as well as scipy by the way but not scipy.misc
> which seems really odd for me but i don't know much about library and
> subpart of library...

Well, was worth a try. I'm not that much "into" numpy, so this is
where my "expertise" ends, sorry...

Cheers
-- t


signature.asc
Description: Digital signature

Re: python 3 : error with lib scipy

[Laurent Debian]

Hi,
Le dim. 31 mars 2019 à 16:01,  a écrit :

> On Sun, Mar 31, 2019 at 03:22:22PM +0200, Laurent Debian wrote:
> > Hi all,
> > On debian-sid  with python 3, I got this error (below) when trying to
> load
> > scipy.
> > No error with python 2, (and yes numpy is installed correctly)
>
>  [ No module named 'numpy.core._multiarray_umath' ]
>
> Hm. Note that there are separate numpy packages for Python and Python 3:
> Are you sure you've got python3-numpy installed?
>
yes and I can load numpy  perfectly well
as well as scipy by the way but not scipy.misc
which seems really odd for me but i don't know much about library and
subpart of library...

Cheers,

>
> Cheers
> -- t
>

Re: Liveusb w/ persistent data

[Brian]

On Sun 31 Mar 2019 at 15:00:52 +0100, Paul Sutton wrote:

> 
> On 31/03/2019 12:24, Brian wrote:
> > On Sun 31 Mar 2019 at 09:02:15 +0100, Paul Sutton wrote:
> >
> >> Not sure if this is the right solution.  However when booting and
> >> installing from a flash disk, I get the option to install to either hdd
> >> or flash disk (as this device is detected),  I also get the choose where
> >> to install the boot loader.
> >>
> >> The same applies if I have 2 or more physical hard disks in a system, it
> >> will give me the option as to where to install.
> >>
> >> Would plugging in a 2nd flash disk and then installing to that work,
> >> then tell the bootloader to install to that device.
> >>
> >> Comments welcome on this.
> > That would work. What to install to the flash drive would depend on the
> > thought Joe B has put into what goes on the drive. Terminal only? A DE?
> > An archive? Hardware compatibility and portability are considerations.
> >
> > "Liveusb w/ persistent data" doesn't appear to have the edge over this
> > method.
> >
> 
> Hi
> 
> Not sure if this is significant, just doing the EdX intro to Linux
> course (free route, so no certificate), it says the following regarding
> file systems
> 
> Conventional disk filesystems: ext2, ext3, ext4, XFS, Btrfs, JFS, NTFS, etc.
> Flash storage filesystems: ubifs, JFFS2, YAFFS, etc.
> 
> Would it need a different file system for Flash storage systems ? Or as
> this is being used as bootable system with persistence would you just
> stick with for example a conventional system despite being on a flash disk.

I do not know about "need". I just went with ext3 and set up things to
do as little writing to the drive (e.g. logs are in memory) as possible.
The stick isn't used very intensively but it has lasted five years up
to now.

-- 
Brian.

mutt imap_headers

[Nick]

A question about mutt over imap in stretch.  In my .muttrc (what I
think are the relevant lines),

   set imap_headers = "X-SPAM-STATUS"
   set index_format="%H %Z %d %-15.15F %s"
   spam "X-Spam-Status: Yes" "spam"

The good part: when I open a message having the header "X-Spam-Status:
Yes", the "spam" marker appears in the index in place of "%H".

The not so good: no marker appears until I open messages.  I
had expected that my imap_headers setting would cause the marker to
appear on all the qualifying messages in the index.  How can I make
that happen?

Thanks
-- 
Nick

Re: python 3 : error with lib scipy

[Michael Lange]

On Sun, 31 Mar 2019 16:01:15 +0200
 wrote:

> On Sun, Mar 31, 2019 at 03:22:22PM +0200, Laurent Debian wrote:
> > Hi all,
> > On debian-sid  with python 3, I got this error (below) when trying to
> > load scipy.
> > No error with python 2, (and yes numpy is installed correctly)
> 
>  [ No module named 'numpy.core._multiarray_umath' ]
> 
> Hm. Note that there are separate numpy packages for Python and Python 3:
> Are you sure you've got python3-numpy installed?
> 

Of course I don't know for sure, but python3-numpy is in python3-scipy's
dependencies (at least on Stretch), so I believe it should be.

Regards

Michael

> Cheers
> -- t



.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Oh, that sound of male ego.  You travel halfway across the galaxy and
it's still the same song.
-- Eve McHuron, "Mudd's Women", stardate 1330.1

Re: python 3 : error with lib scipy

[Michael Lange]

Hi,

On Sun, 31 Mar 2019 15:22:22 +0200
Laurent Debian  wrote:

> Hi all,
> On debian-sid  with python 3, I got this error (below) when trying to
> load scipy.
> No error with python 2, (and yes numpy is installed correctly)
> 
> Every python packages seems up to date to me.
> Is this a bug ?
> 

it seems to be.
Here (Stretch) the import works.
It is just a guess, but the offending line in your traceback:

>  66 from numpy import who as _who, source as _source, info as _info

looks different here (here it is line 50):

from numpy import who, source, info as _info

so I think the problem might be that something went wrong when scipy
changed their internal module alias names.

Regards

Michael


> Cheers
> 
> LB
> 
> ===
> :>  import scipy.misc
> 
> ---ModuleNotFoundError
>   Traceback (most recent call
> last)ModuleNotFoundError: No module named
> 'numpy.core._multiarray_umath'
> 
> 
> ---ImportError
>   Traceback (most recent call
> last) in ()> 1 import
> scipy.misc
> /usr/lib/python3/dist-packages/scipy/misc/__init__.py in ()
>  66 from numpy import who as _who, source as _source, info as _info
>  67 import numpy as np---> 68 from scipy.interpolate._pade import pade
> as _pade 69 from scipy.special import (comb as _comb, logsumexp as
> _lsm, 70 factorial as _fact, factorial2 as _fact2,
> factorialk as _factk)
> /usr/lib/python3/dist-packages/scipy/interpolate/__init__.py in
> ()173 from __future__ import division, print_function,
> absolute_import174 --> 175 from .interpolate import *176 from
> .fitpack import *177
> /usr/lib/python3/dist-packages/scipy/interpolate/interpolate.py in
> () 18dot, ravel, poly1d, asarray,
> intp) 19 ---> 20 import scipy.linalg 21 import scipy.special
> as spec 22 from scipy.special import comb
> /usr/lib/python3/dist-packages/scipy/linalg/__init__.py in ()
>   188 from .linalg_version import linalg_version as __version__189
> --> 190 from .misc import *191 from .basic import *192 from
> .decomp import *
> /usr/lib/python3/dist-packages/scipy/linalg/misc.py in ()
> 3 import numpy as np  4 from numpy.linalg import LinAlgError>
> 5 from .blas import get_blas_funcs  6 from .lapack import
> get_lapack_funcs  7
> /usr/lib/python3/dist-packages/scipy/linalg/blas.py in ()
> 212 import numpy as _np213 --> 214 from scipy.linalg import _fblas
>215 try:216 from scipy.linalg import _cblas
> ImportError: numpy.core.multiarray failed to import



.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Violence in reality is quite different from theory.
-- Spock, "The Cloud Minders", stardate 5818.4

Re: python 3 : error with lib scipy

[tomas]

On Sun, Mar 31, 2019 at 03:22:22PM +0200, Laurent Debian wrote:
> Hi all,
> On debian-sid  with python 3, I got this error (below) when trying to load
> scipy.
> No error with python 2, (and yes numpy is installed correctly)

 [ No module named 'numpy.core._multiarray_umath' ]

Hm. Note that there are separate numpy packages for Python and Python 3:
Are you sure you've got python3-numpy installed?

Cheers
-- t


signature.asc
Description: Digital signature

Re: Liveusb w/ persistent data

[Paul Sutton]

On 31/03/2019 12:24, Brian wrote:
> On Sun 31 Mar 2019 at 09:02:15 +0100, Paul Sutton wrote:
>
>> Not sure if this is the right solution.  However when booting and
>> installing from a flash disk, I get the option to install to either hdd
>> or flash disk (as this device is detected),  I also get the choose where
>> to install the boot loader.
>>
>> The same applies if I have 2 or more physical hard disks in a system, it
>> will give me the option as to where to install.
>>
>> Would plugging in a 2nd flash disk and then installing to that work,
>> then tell the bootloader to install to that device.
>>
>> Comments welcome on this.
> That would work. What to install to the flash drive would depend on the
> thought Joe B has put into what goes on the drive. Terminal only? A DE?
> An archive? Hardware compatibility and portability are considerations.
>
> "Liveusb w/ persistent data" doesn't appear to have the edge over this
> method.
>

Hi

Not sure if this is significant, just doing the EdX intro to Linux
course (free route, so no certificate), it says the following regarding
file systems

Conventional disk filesystems: ext2, ext3, ext4, XFS, Btrfs, JFS, NTFS, etc.
Flash storage filesystems: ubifs, JFFS2, YAFFS, etc.

Would it need a different file system for Flash storage systems ? Or as
this is being used as bootable system with persistence would you just
stick with for example a conventional system despite being on a flash disk.

Regards

Paul


-- 
Paul Sutton
http://www.zleap.net
https://www.linkedin.com/in/zleap/
gnupg : 7D6D B682 F351 8D08 1893  1E16 F086 5537 D066 302D

BUSTER install - CATCH-22

[Richard Owlett]

I wish to install Buster on a machine with essentially *NO* internet 
connectivity.
I downloaded the DVD1 ISO on my primary machine [creates secondary 
problem of being up against data cap].
The installation, having put the DVD1 ISO on a flash drive, encountered 
no problems


*HOWEVER* I need several packages [gparted, tcl, tk] which are in the 
DVD image.


Synaptic is unable to install them:
  1. sources.list refers to a non-existent physical DVD.
  2. the default installation has no way of informing Synaptic
 that it should look for an alternate iso image.
  3. modifying sources.list was unsuccessful

I added the line

deb "file:/media/richard/Debian testing amd64 1/debian" buster contrib main


to the beginning of sources.list .

The Synaptic error message when attempting
   Edit --> Reload Package Information
was
 > Download is performed unsandboxed as root as file 
'/media/richard/Debian testing amd64 1/debian/dists/buster/InRelease' 
couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission 
denied)The repository 'cdrom://[Debian GNU/Linux testing _Buster_ - 
Official Snapshot amd64 DVD Binary-1 20190327-09:46] buster Release' 
does not have a Release file.Updating from such a repository can't be 
done securely, and is therefore disabled by default.See apt-secure(8) 
manpage for repository creation and user configuration details.The 
repository 'file:/media/richard/Debian testing amd64 1/debian buster 
Release' is not signed.


This is unacceptable when installation via an iso image on a flash drive 
is becoming more and more common.


What package(s) to file bug(s) against?
Was the syntax of the line added to sources.list correct?
How to work around the permission issues in the error message?
   Ran into something similar when Squeeze was current.
   I haven't found my correspondence from that time to
   see if it covers current situation.

TIA

python 3 : error with lib scipy

[Laurent Debian]

Hi all,
On debian-sid  with python 3, I got this error (below) when trying to load
scipy.
No error with python 2, (and yes numpy is installed correctly)

Every python packages seems up to date to me.
Is this a bug ?

Cheers

LB

===
:>  import scipy.misc

---ModuleNotFoundError
  Traceback (most recent call
last)ModuleNotFoundError: No module named
'numpy.core._multiarray_umath'


---ImportError
  Traceback (most recent call
last) in ()> 1 import
scipy.misc
/usr/lib/python3/dist-packages/scipy/misc/__init__.py in ()
 66 from numpy import who as _who, source as _source, info as _info
 67 import numpy as np---> 68 from scipy.interpolate._pade import pade
as _pade 69 from scipy.special import (comb as _comb, logsumexp as
_lsm, 70 factorial as _fact, factorial2 as _fact2,
factorialk as _factk)
/usr/lib/python3/dist-packages/scipy/interpolate/__init__.py in
()173 from __future__ import division, print_function,
absolute_import174 --> 175 from .interpolate import *176 from
.fitpack import *177
/usr/lib/python3/dist-packages/scipy/interpolate/interpolate.py in
() 18dot, ravel, poly1d, asarray,
intp) 19 ---> 20 import scipy.linalg 21 import scipy.special
as spec 22 from scipy.special import comb
/usr/lib/python3/dist-packages/scipy/linalg/__init__.py in ()
  188 from .linalg_version import linalg_version as __version__189
--> 190 from .misc import *191 from .basic import *192 from
.decomp import *
/usr/lib/python3/dist-packages/scipy/linalg/misc.py in ()
3 import numpy as np  4 from numpy.linalg import LinAlgError>
5 from .blas import get_blas_funcs  6 from .lapack import
get_lapack_funcs  7
/usr/lib/python3/dist-packages/scipy/linalg/blas.py in ()
212 import numpy as _np213 --> 214 from scipy.linalg import _fblas
   215 try:216 from scipy.linalg import _cblas
ImportError: numpy.core.multiarray failed to import

Re: After upgrading to stretch, a package refuses to purge or upgrade

[Roberto C . Sánchez]

On Sun, Mar 31, 2019 at 07:04:08AM -0500, Martin McCormick wrote:
> Charlie Kravetz  writes:
> > You may have to remove Orca and all associated programs before you can
> > remove espeakup.
> 
>   Thanks and you are correct but orca is not installed on
> either of the two systems so thankfully, that won't be necessary
> 
> > Other than that, someone much wiser than myself will step in and help
> > out.
> 
>   I feel kind of ashamed at a time like this as I have been
> working in the unix world for 30 years this year and the one
> thing I do know is that one must be very careful to first do no
> harm.  I will see if I can purge each of the packages that
> apt-get autoremove says can be safely removed and do this one at
> a time since apt-get autoremove just tries and complains if you
> do it as a batch.
> 
Sadly, this sort of breakage happens from time to time.  I downloaded
the espeakup binary package and found that the pre-removal script
contents are as follows:

#!/bin/sh
set -e
# Automatically added by dh_installinit
if [ -x "/etc/init.d/espeakup" ]; then
invoke-rc.d espeakup stop || exit $?
fi
# End automatically added section


I the espeakup is really not running and you don't need to worry about
stopping it, then a simple 'sudo chmod a-x /etc/init.d/espeakup' will
prevent the prerm script from trying to stop the service.

That should let you get past the error and continue with the removals
and installations.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: After upgrading to stretch, a package refuses to purge or upgrade

[Martin McCormick]

Charlie Kravetz  writes:
> You may have to remove Orca and all associated programs before you can
> remove espeakup.

Thanks and you are correct but orca is not installed on
either of the two systems so thankfully, that won't be necessary

> Other than that, someone much wiser than myself will step in and help
> out.

I feel kind of ashamed at a time like this as I have been
working in the unix world for 30 years this year and the one
thing I do know is that one must be very careful to first do no
harm.  I will see if I can purge each of the packages that
apt-get autoremove says can be safely removed and do this one at
a time since apt-get autoremove just tries and complains if you
do it as a batch.

Martin

Re: Liveusb w/ persistent data

[Brian]

On Sun 31 Mar 2019 at 09:02:15 +0100, Paul Sutton wrote:

> Not sure if this is the right solution.  However when booting and
> installing from a flash disk, I get the option to install to either hdd
> or flash disk (as this device is detected),  I also get the choose where
> to install the boot loader.
> 
> The same applies if I have 2 or more physical hard disks in a system, it
> will give me the option as to where to install.
> 
> Would plugging in a 2nd flash disk and then installing to that work,
> then tell the bootloader to install to that device.
> 
> Comments welcome on this.

That would work. What to install to the flash drive would depend on the
thought Joe B has put into what goes on the drive. Terminal only? A DE?
An archive? Hardware compatibility and portability are considerations.

"Liveusb w/ persistent data" doesn't appear to have the edge over this
method.

-- 
Brian.

Re: troubleshooting nfs-kernel-server on Raspbian Jessie

[Darac Marjal]

On 30/03/2019 02:20, Jason wrote:
> I am trying to set up an NFS export on a Ras Pi (Raspbian Jessie). 
> Something seems to be missing and I need help troubleshooting it.
>
> At first the NFS port 2049 was not even being opened. After much futzing 
> around I discovered that if I manually start rpcbind with
>
> $ sudo /etc/init.d/rpcbind start

This starts the service manually, but doesn't mark it for automatic
start. To do that, try:

$ systemctl enable --now rpcbind

> then restart the nfs-kernel-server I can get it to work, but only if I 
> spell out the full ip address of the client. For instance if I put this 
> in /etc/exports it works:
>
> /srv/export 192.168.1.1(rw,sync)
>
> but not if I change it to this to allow other machines on the LAN to 
> mount (I get: mount.nfs: access denied by server while mounting 
> 192.168.1.15:/srv/export):
>
> /srv/export 192.168.1.*(rw,sync)7

Are you running "exportfs -rav" or similar after editing that file?

>
> So I have two questions:
> 1) Why does rpcbind not start automatically on boot?
>
> 2) Why can I not specify a range of client addresses in /etc/exports  ?
>
> Thanks,

Re: Liveusb w/ persistent data

[deloptes]

Joe B wrote:

> I want to make a bootable buster with persistent data so it saves my
> settings whenever I reboot.

Which settings - the user settings from the desktop? If so, which desktop?

Re: Tri des résultats de "du"

[Alban Vidal]

Bonjour,

En effet ncdu est plutôt sympa et très "user friendly", après tout déprend le 
contexte d'utilisation.

Par exemple, avec ncdu je ne sais pas si on peut exclure des répertoires (mais 
je n'ai pas cherché non plus), ce qui est très pratique avec l'option " 
--exclude [répertoire] " de la commande du.

Alban

Le 30 mars 2019 23:47:54 GMT+01:00, Quentin  a écrit :
>Je te conseille le paquet ncdu
>
>Le 30 mars 2019 23:39:53 GMT+01:00, Alban Vidal
> a écrit :
>>Bonsoir,
>>
>>Par exemple quand je  veux voir dans le /var je fais la commande
>>suivante :
>>du -hsc /var/*|sort -h
>>
>>J'espère que ça pourra t'aider.
>>
>>Alban
>>
>>Le 30 mars 2019 23:30:28 GMT+01:00, philolilou  a
>>écrit :
>>>Bonjour,
>>>
>>>je vous sollicite car j'aimerai trier les résultats de la commande
>>>"du".
>>>
>>>J'utilise occasionnellement cette commande de cette manière: du 
>>>--max-depth=1 -h
>>>
>>>Par contre, en consultant le man, je n'ai pas trouvé d'option qui
>>>permet 
>>>de faire un tri sur les  tailles croissant ou décroissant des
>dossiers
>>
>>>listés.
>>>
>>>Auriez-vous une idée de comment faire pour trier le résultat de la 
>>>commande "du" suivant la taille qu'il affiche?
>>>
>>>Je vous remercie d'avance de votre aide.
>>
>>-- Envoyé de /e/ Mail.
>
>-- 
>Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser
>ma brièveté.

-- Envoyé de /e/ Mail.

Re: Tri des résultats de "du"

[Pascal Hambourg]

Le 31/03/2019 à 00:27, philolilou a écrit :


Après quelques essais d'après vos suggestions, ce qui fonctionne pour 
mon utilisation de 'du' semble être ceci:


pour un tri croissant de la taille des dossiers:

du --max-depth=1 -h | sort -h

du --max-depth=1 -h | sort -n

pour un tri décroissant de la taille des dossiers:

du --max-depth=1 -h | sort -nr


Non, l'option -n de sort ne prend pas le préfixe multiplicateur en 
compte et donc trie pas correctement la sortie de du avec l'option -h.

Re: Liveusb w/ persistent data

[Paul Sutton]

Hi

Not sure if this is the right solution.  However when booting and
installing from a flash disk, I get the option to install to either hdd
or flash disk (as this device is detected),  I also get the choose where
to install the boot loader.

The same applies if I have 2 or more physical hard disks in a system, it
will give me the option as to where to install.

Would plugging in a 2nd flash disk and then installing to that work,
then tell the bootloader to install to that device.

Comments welcome on this.

Regards

Paul


On 31/03/2019 05:47, Joe B wrote:
> Hello,
> 
> I’ve asked this on irc a number of times but links and answers I try are
> usually outdated or simply don’t work
> 
> I want to make a bootable buster with persistent data so it saves my
> settings whenever I reboot.
> 
> Looking for links I haven’t tried or steps that could help out.
> 
> Any help is appreciated
> 
> Thanks
> 

-- 
Paul Sutton
http://www.zleap.net
https://www.linkedin.com/in/zleap/
gnupg : 7D6D B682 F351 8D08 1893  1E16 F086 5537 D066 302D

Installing Debian root on ZFS mirror NetBoot

[Mimiko]

Hello.

I know that ZFS is not well supported as MD raids. All I've found on internet 
on installing Debian on ZFS is using a live disk.

My goal is to boot from network and install Debian root on ZFS raid mirror. I can do this using MD raid. I am searching for suggestions of how to 
enable ZFS during installing from network and partition disks using ZFS.


Any suggestion and ideas a welcome.