Re: Bluetooth: hardware detected but no device

[deloptes]

Markos wrote:

> The system detect the hardware on boot:
> 
> dmesg | grep -i blue
> [ 9.685735] Bluetooth: Core ver 2.19
> [ 9.685759] Bluetooth: HCI device and connection manager initialized
> [ 9.685770] Bluetooth: HCI socket layer initialized
> [ 9.685773] Bluetooth: L2CAP socket layer initialized
> [ 9.685787] Bluetooth: SCO socket layer initialized
> [ 20.010114] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 20.010119] Bluetooth: BNEP filters: protocol multicast
> [ 20.010135] Bluetooth: BNEP socket layer initialized

this is false statement

it means it has initialized the BT subsystem(s)

try bluetoothctl
list
devices

check if the rfkill switch is enabled
try rfkill all
rfkill bluetooth

on my older D530 it was ALT+F2 or F5 (cant recall) to enable disable the
wireless (wlan/BT)

I hope this helps

regards

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Andy Smith]

Hello,

On Mon, Mar 07, 2016 at 03:39:26AM +, Andy Smith wrote:
> As per
> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
> I wrote an ISO of the current amd64 netinst including non-free
> firmware to a USB and booted from it.
> 
> At no point does it tell me that it requires additional firmware. It
> also does not load iwlwifi or any of the associated wifi modules.

An off-list response said they had more success with a daily
installer image.

I tried out:


http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/stretch_di_alpha5/amd64/iso-cd/

and indeed this now correctly says it requires firmware. It finds and
configures the wlan device and is able to download things through
wifi.

Unfortunately this of course attempts to install stretch. That
wouldn't be so bad but this fails during "Select and install
software" with:

pkgsel: checking for (security) updates to the base system
in-target: Reading package lists...
in-target:
in-target: Building dependency tree...
in-target:
in-target: reading state information...
in-target: You might want to run 'apt-get -f install' to correct these.
in-target: The following packages have unmet dependencies:
in-target:  ifupdown : Breaks: systemd (< 228-3~) but 228-2+b1 is installed
in-target:  systemd : Depends: libsystemd0 (= 228-2+b1) but 229-2 is installed
in-target: E: Unmet dependencies. Try using -f.
in-target: dpkg: dependency problems prevent configuration of systemd:
in-target:  systemd depends on libsystemd0 (= 228-2+b1); however:
in-target:   Version of libsystemd0:amd64 on system is 229-2.
in-target:  ifupdown (0.8.10) breaks systemd (<< 228-3~) and is installed.
in-target:   Version of systemd to be configured is 228-2+b1.

I don't fancy unpicking problems like this on testing, so for now I
think I'll go back and see if there are any daily installer images
for jessie that work with regard to wifi firmware.

At least I know now that it is possible.

Cheers,
Andy

Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Andy Smith]

Hi,

I've got a ThinkPad X1 Carbon gen 4 which I'd like to try installing
Debian on. Preferably stable, but I'll try with testing if
necessary.

The machine has an Intel 8260 wifi which will require non-free
firmware. Although it has an eth0 (e1000e), physically using that
requires an adaptor, so that is not an option.

As per
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
I wrote an ISO of the current amd64 netinst including non-free
firmware to a USB and booted from it.

At no point does it tell me that it requires additional firmware. It
also does not load iwlwifi or any of the associated wifi modules.

So, given this is a netinst installer I am unable to proceed.

I tried dropping to a shell and doing "modprobe iwlwifi". Although
this appeared to load the module without error (lsmod shows it), it
did not result in a wlan0 network device appearing.

Is there any way to force the debian-installer to realise it needs
to load firmware for this wifi device? I have a feeling that it is
seeing there is an eth0 and giving up at that point, assuming that
is good enough.

All of my online research so far just shows instructions that say
that the installer will ask for firmware if it thinks it needs it.

Is it even possible to do a Debian install over wifi alone?

I've booted an Ubuntu live environment and the wifi does work there,
so am pretty sure it's just a driver/firmware issue.

Cheers,
Andy

Re: boot problem

[Thiago]

Hi, you can open the Terminal and type:
# grub-install /dev/sda1

And
# update-grub2

This will do what you need.

Em 06-03-2016 03:55, lina escreveu:
> Hi,
>
> After install the debian,
>
> it goes to debian OS system directly, without showing me the option of
> start Mac OS or debian OS.
>
> Any suggestions, thanks,
>

Cannot Load Changelogs!

[maddonkeykong]

In Synaptic, I can't load any Changelogs, it gives this message:

This change is not coming from a source that supports changelogs.

Failed to fetch the changelog for cpio

URI was: 
http://packages.debian.org/changelogs/pool/main/c/cpio/cpio_2.11+dfsg-4.1+deb8u1/changelog

[apt-get changelog package] -> this fails too!

#

- What works:

in Tor Browser, going to:

http://metadata.ftp-master.debian.org/changelogs/main/c/cpio/cpio_2.11+dfsg-4.1+deb8u1_changelog

#

Where in Synaptic can I make a change to properly load Changelogs and is there 
a system wide setting so I can use apt-get's changelog feature? I don't and 
won't use aptitude. Thank you.

Re: What else must I do to avoid installing "suggests"? Was: How to get a "minimal font set"?

[Patrick Bartek]

On Sun, 06 Mar 2016, Kynn Jones wrote:

> Thank you for all your comments and suggestions.
> 
> My interest in this question stems from the fact that I'm getting
> ready to do a full reinstallation of my system, and I don't want to
> repeat my previous mistakes.
> 
> My concern is that the unwanted packages could have landed in my hard
> drive when the system was first installed, even though I kept my
> choices at the time very minimalistic.  (E.g. whatever the Debian
> installer uses for installing packages has the equivalent of
> `APT::Install-Suggests "1"` or `APT::Install-Recommends "1"`.)
> 
> [snip]

To achieve a minimal system to build off of:

1.  Choose Expert Mode
2.  Install ONLY the Base System (terminal only) -- no X or GUI, etc.--
to begin with.

This should get you a terminal only set up with networking, apt-get
plus minimal repo sources list, and only a basic screen font package.
Also, only dependencies and not recommends or suggests should be
installed by default.

3. Install additionally what you need -- piece by piece.

Keep detailed notes of what you did and what was installed, and
what was suggested or recommended in case you later want to install them.

4. Don't use meta-packages to install stuff.  They install a lot more
than is really needed, particularly if used to install a desktop
GUI.  Find the properly named package(s) to install it, and only its
dependencies.

However, be aware that some packages like LibreOffice or games install
font packages specific to those apps.  They may not be
"dependencies" in the true sense of the word, but those fonts are
needed for the proper operation of the app.  Usually, you can specify
they or some NOT be installed or uninstall them later.

The above is the basic outline I used to install my minimal Wheezy
system and window manager set up.  If you want more detailed
instructions of what I did, let me know and I will email them to you.

Good luck.

B  

Re: binary-i386 packages missing in Release file

[Haines Brown]

On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> Correct syntax is:
> 
> --
> deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> --
> 
> On 6 March 2016 at 20:10, Haines Brown  wrote:
> 
> On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> >       Hi.
> >
> > On Sun, 6 Mar 2016 14:34:25 -0500
> > Haines Brown  wrote:
> >
> > > I have jessie installed on an AMD64 machine, which lacks any desktop
> > > environment.
> > >
> > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > installed by running dpkg -i on it. It works OK. But now I want to add
> > > flashplugin-nonfree for it or, if that fails to use it for my
> > > iceweasel. In order to install flashplugin-nonfree I added contrib to
> > > the sources.list.
> > >
> > > When I do aptitude update, the contrib it hit, but the update fails
> > > because:
> > >
> > > > W: Failed to fetch
> > > > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable 
> to
> > > > find expected entry 'main/binary-i386/Packages' in file
> >
> > 1) Locate the line like this in a file inside /etc/apt/sources.list.d:
> >
> > deb http://dl.google.com/linux/chrome/deb/
> >
> > 2) Change it to:
> >
> > deb [amd64] http://dl.google.com/linux/chrome/deb/
> >
> > This warning should go away.
> >
> > Reco
> 
> Reco, your suggestion didn't work. When I do an update I get
> 
> > E: Malformed line 14 in source list /etc/apt/sources.list ([amd64] is
> > not an assignment)
> 
> I did not have the dl.google.com line to start with. When I removed the
> amd, and the line still malformed. When I comment the line altogether,
> I get failed to fetch because there no 'main/binary-i386/Pakages in
> release file. Why does it look for dl.google.com? The line is not in
> sources.list.
>
> Haines

Progress, but not there yet. In sources.list I have the line:

  deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main 

When I do # aptitude update, it starts with a warning:

 W: Duplicate sources.list entry
 http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
 (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
 main_binary-amd64_packages)

 W: You may want to update the packages lists to correct these
 missing files

then there are hits and gets and then 100% [working]. However, this
is followed by a warning and errors:

 W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/ \
 stable/Release: Unable to find expected entry `main/binary-i386/ \
 Packages' in Release file (Wrong sources.list entry or malformed
 file)

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

 E: Couldn't rebuild package cache.

This didn't stop me from installing the flashplugin-nonfree, but with
aptitude update I still get more or less the same warnings and errors.

Haines

Re: binary-i386 packages missing in Release file

[Martinx - ジェームズ]

Correct syntax is:

--
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
--

On 6 March 2016 at 20:10, Haines Brown  wrote:

> On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> >   Hi.
> >
> > On Sun, 6 Mar 2016 14:34:25 -0500
> > Haines Brown  wrote:
> >
> > > I have jessie installed on an AMD64 machine, which lacks any desktop
> > > environment.
> > >
> > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > installed by running dpkg -i on it. It works OK. But now I want to add
> > > flashplugin-nonfree for it or, if that fails to use it for my
> > > iceweasel. In order to install flashplugin-nonfree I added contrib to
> > > the sources.list.
> > >
> > > When I do aptitude update, the contrib it hit, but the update fails
> > > because:
> > >
> > > > W: Failed to fetch
> > > > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable
> to
> > > > find expected entry 'main/binary-i386/Packages' in file
> >
> > 1) Locate the line like this in a file inside /etc/apt/sources.list.d:
> >
> > deb http://dl.google.com/linux/chrome/deb/
> >
> > 2) Change it to:
> >
> > deb [amd64] http://dl.google.com/linux/chrome/deb/
> >
> > This warning should go away.
> >
> > Reco
>
> Reco, your suggestion didn't work. When I do an update I get
>
> > E: Malformed line 14 in source list /etc/apt/sources.list ([amd64] is
> > not an assignment)
>
> I did not have the dl.google.com line to start with. When I removed the
> amd, and the line still malformed. When I comment the line altogether,
> I get failed to fetch because there no 'main/binary-i386/Pakages in
> release file. Why does it look for dl.google.com? The line is not in
> sources.list.
>
> Haines
>
>

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Pascal Hambourg]

Le 06/03/2016 23:35, Randy11 a écrit :


On 06/03/2016 13:01, Pascal Hambourg wrote:


- Créer une petite partition (5 Mo devraient suffire) formatée en ext2 à
monter sur /boot/grub, ce qui au mieux réduira suffisamment la taille de
l'image core pour qu'elle contienne dans l'espace post-MBR en évitant
l'intégration du module lvm, et au pire permettra à grub-install avec
l'option --force d'utiliser les listes de blocs.

(...)

J'ai créer une partition en etx2 /dev/sda6 en réduisant la taille de
mon volume groupe qui prenait toute la partition /dev/sda5.


Il n'était pas nécessaire que la partition contienne tout /boot ; 
/boot/grub suffisait et nécessitait une taille plus modeste.



C'est bien, mais le problème est que mes partitions cryptées qui doivent
correspondre à "/home" et "/swap" ne sont pas utilisées.


Le paquet cryptsetup est-il installé ?
As-tu essayé d'ouvrir les volumes chiffrés avec cryptsetup luksOpen... ?
Si cela fonctionne, tu pourras les ajouter au fichier /etc/crypttab (à 
moins que tu aies conservé celui de Wheezy) pour les ouvrir 
automatiquement au démarrage.

Recherche DSI

[MENGUAL Jean-Philippe]

Bonjour,

Une commune de proche-banlieue parisienne cherche un DSI pour
accompagner son plan de migration au logiciel libre. Budget de 5
millions d'euros à gérer, personne pragmatique mais connaissant le
libre. L'élu en charge du numérique souhaite migrer vers libreoffice,
Zimbra, puis les serveurs. Une connaissance de Windows et une approche
du libre pragmatique est souhaitée. Salaire substantiel attendu.

N'hésitez pas à me répondre en privé avec vos coordonnées tél si vous
êtes intéressé.

Cordialement,

-- 

Jean-Philippe MENGUAL

HYPRA, progressons ensemble

Tél.: 01 84 73 06 61
Mail: cont...@hypra.fr

Site Web: http://hypra.fr

Re: binary-i386 packages missing in Release file

[Haines Brown]

On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
>   Hi.
> 
> On Sun, 6 Mar 2016 14:34:25 -0500
> Haines Brown  wrote:
> 
> > I have jessie installed on an AMD64 machine, which lacks any desktop
> > environment.
> > 
> > I downloaded google-chrome AMD64 deb from the Chrome website and
> > installed by running dpkg -i on it. It works OK. But now I want to add
> > flashplugin-nonfree for it or, if that fails to use it for my
> > iceweasel. In order to install flashplugin-nonfree I added contrib to
> > the sources.list.
> > 
> > When I do aptitude update, the contrib it hit, but the update fails
> > because:
> > 
> > > W: Failed to fetch
> > > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable to
> > > find expected entry 'main/binary-i386/Packages' in file
> 
> 1) Locate the line like this in a file inside /etc/apt/sources.list.d:
> 
> deb http://dl.google.com/linux/chrome/deb/
> 
> 2) Change it to:
> 
> deb [amd64] http://dl.google.com/linux/chrome/deb/
> 
> This warning should go away.
> 
> Reco

Reco, your suggestion didn't work. When I do an update I get

> E: Malformed line 14 in source list /etc/apt/sources.list ([amd64] is
> not an assignment)

I did not have the dl.google.com line to start with. When I removed the
amd, and the line still malformed. When I comment the line altogether,
I get failed to fetch because there no 'main/binary-i386/Pakages in
release file. Why does it look for dl.google.com? The line is not in
sources.list.

Haines

Re: boot problem

[Keith Bainbridge]

Good morning Lina

I don't get that the partitions aren't showing sda1 to sda15.  I would expect 
osx to be on sda3 or sda4 from memory.  And my version of osx didn't have a 
separate swap partition. So what are the other missing partitions? 

Are there any  other partitions listed in the devices section of your file 
manager that didn't mount? I haven't had a dual boot system for so long I don't 
recall the names, but you will recognise the names from your osx install. 

Failing that have you checked what gparted lists. 

What is /etc/fstab listing?   I think the osx partitions will be listed as not 
auto mounting. 


I did think later last night, when I said hold the alt key, I meant hold it 
from when the boot process starts (power button on cold start) until you get 
the menu of icons. This feels like forever on my 2008 macbook. I trust it is 
getting quicker.  And you will get a menu. 


 Original Message 
From: lina 
Sent: Mon Mar 07 01:01:31 AEDT 2016
To: Keith Bainbridge 
Cc: Debian Lists 
Subject: Re: boot problem

df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda4   641M  235M  360M  40% /
udev 10M 0   10M   0% /dev
tmpfs   1.6G  9.1M  1.6G   1% /run
/dev/sda819G  3.6G   14G  21% /usr
tmpfs   3.9G   68K  3.9G   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
/dev/sda13  181M   32M  136M  20% /boot
/dev/sda11  547M  720K  507M   1% /tmp
/dev/sda715G  1.2G   13G   9% /home
/dev/sda12  3.7G  7.6M  3.4G   1% /usr/local
/dev/sda9   3.7G 1010M  2.5G  29% /var
/dev/sda10  6.3G   15M  6.0G   1% /var/local
/dev/sda1   197M   16M  182M   8% /boot/efi
/dev/sda15  393G   71M  373G   1% /scratch
tmpfs   788M  4.0K  788M   1% /run/user/116
tmpfs   788M  8.0K  788M   1% /run/user/1000

On Sun, Mar 6, 2016 at 3:56 PM, Keith Bainbridge
 wrote:
> Good afternoon Lina
>
> Try holding the alt key as you boot.  You should get a few icons to choose 
> osx or linux.
>
>
> If not, please send us output of command df -h
>
>
>  Original Message 
> From: lina 
> Sent: Sun Mar 06 17:55:17 AEDT 2016
> To: Debian Lists 
> Subject: boot problem
>
> Hi,
>
> After install the debian,
>
> it goes to debian OS system directly, without showing me the option of
> start Mac OS or debian OS.
>
> Any suggestions, thanks,
>
>
> Keith Bainbridge
>
> 0447 667 468
>
> keithrbaugro...@gmail.com
>
> Sent from my APad

Keith Bainbridge

0447 667 468 

keithrbaugro...@gmail.com 

Sent from my APad 

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Randy11]

On 06/03/2016 13:01, Pascal Hambourg wrote:

Randy11 a écrit :

On 05/03/2016 22:48, Pascal Hambourg wrote:

Randy11 a écrit :

Pour installer Jessie, j'ai seulement pris :
- lv--01 pour /
- lv--05 pour /var
- lv--08 pour swap

Avis personnel : donner des noms génériques aux volumes logiques
constitue une négation d'un des avantages de LVM, à savoir de pouvoir
donner aux volumes logiques des noms signifiants et non de simples
numéros comme les partitions.

Bonne remarque. C'est une habitude d'un collègue que j'ai reprise. Je aivais
choisi ces noms pour avoir le moins de partitons facilement identifiables
puisque j'ai certaines sont chiffrées : ne pas faciliter les choses.

C'est un point de vue. Mais ne pas faciliter les choses pour qui ? Pour
un administrateur que cela ne va pas aider à s'y retrouver, c'est sûr.
Pour un éventuel attaquant qui peut de toute façon assez facilement
savoir ce que contiennent les volumes, sur quoi ils sont montés et à
quoi ils servent, j'ai des doutes. On n'est pas loin de la sécurité par
l'obscurité.


Soit, j'en tiendrais compte pour la suite ;-)


L'installation date de la première version de Wheezy.

L'installateur de Wheezy créait déjà des partitions alignées sur des
blocs de 1 Mio (2048 secteurs de 512 octets). D'ailleurs on voit bien
que le début de la partition LVM est aligné sur cette taille.

Par contre ce n'est pas le cas des partitions NTFS et FAT qui sont
alignées "à l'ancienne" sur des pistes ou cylindres (63 secteurs/piste
pour la première, multiples de 255 têtes x 63 secteurs/piste pour les
deux suivantes). Comment ont-elles été créées ? Sauf erreur,
l'installateur de Windows Vista applique aussi l'alignement "moderne".


Le partionnement a été fait lors de l'installation d'un WindowsXP... 
c'est vieux. J'ai gardé
du Windows pour deux raisons : l'acquisition vidéo avec une carte 
Hauppauge et la
récupérations de mes parcours enregistrés sur mon GPS Garmin Zumo 350LM. 
Le GPS

est la dernière raison pour garder un Windows.



Solutions possibles :
- Créer une petite partition (5 Mo devraient suffire) formatée en ext2 à
monter sur /boot/grub, ce qui au mieux réduira suffisamment la taille de
l'image core pour qu'elle contienne dans l'espace post-MBR en évitant
l'intégration du module lvm, et au pire permettra à grub-install avec
l'option --force d'utiliser les listes de blocs.

J'ai déjà 3 partitions Windows et 1 "extended"/LVM. Si les choses n'ont
pas trop évoluées, il je ne peux plus créer de 4ème partition
primaire.

La partition n° 4 est une partition étendue qui contient actuellement
uniquement la partition logique n° 5 servant de PV LVM, mais elle peut
contenir un nombre arbitraire de partitions logiques. Il suffit qu'il
reste un tout petit peu d'espace non alloué, même non aligné, à la fin
du disque ou au début de la partition étendue.

Dans le cas contraire, tu dois bien pouvoir réduire un poil le PV LVM et
la partition logique n° 5 qui le contient.


J'ai créer une partition en etx2 /dev/sda6 en réduisant la taille de
mon volume groupe qui prenait toute la partition /dev/sda5.
J'ai sauvegardé toutes les étapes,
je les donnerais après.


Avec la netinstall, j'ai tenté de réinstaller Grub : reinstallation 
éffectuée sans

plainte. Au reboot le menu Grub avec les OS à démarrer est présent, mais
message d'erreur :
/boot/vmliuz... non trouvé ???


Les contenu de la partition /boot est :
system.map-3.16.0-4-amd64
config-3.16.0-4-amd64
initrd.img-3.16.0-4-amd64
vmlinuz-3.16.0-4-amd64
grub/
lost+found/

La ligne pour /boot dans /etc/fstab est :
/dev/sda6 /boot ext2 defaults 0 2

Cette fois-ci reprise de l'installation de Grub par "chroot /target" 
après le lancement d'un shell.


mount /var
update-grub
Création du fichier de configuration GRUB...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Image Linux trouvée : /boot/vmlinuz-3.16.0-4-amd64
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-4-amd64
Wintwos NT/2000/XOP trouvé sur /dev/sda1
fait


Redémarrage, on progresse. Le début de démarrage se fait, mais finit en
échec avec le message :
Welcome to emergency mode ! ... "journalctl -xb"..."systemctl reboot"...
"systemctl default"
...
Give root password for maintenance :

Les dernières étapes en échec sont :
[DEPEND] Dependency failed for /mnt
[DEPEND] Dependency failed for Local File System
[DEPEND] Dependency failed for File System Check on 
/dev/mapper/vg-lv--03_crypt
[ TIME ] Timed out waiting for device 
dev-mapper-vg\x2dlv\x2d\x2d02_crypt.device.

[DEPEND]Dependency failed for /dev/mapper/vg-lv--02_crypt
[DEPEND]Dependency failed for Swap


J'ai viré les partitions cryptées du fstab, refait une installation de 
Grub et rédémarré.


J'ai récupéré une Jessie fonctionnelle ! :-)


C'est bien, mais le problème est que mes partitions cryptées qui doivent 
correspondre

à "/home" et "/swap" ne sont pas utilisées.

Y-a-t-il une bonne âme pour m'aider ?

Merci par avance.

P.S.: je vais mettre en forme les infos pour 

Bluetooth: hardware detected but no device

[Markos]

Hi,

I'm using Jessie with a Dell laptop Latitude D430.

The system detect the hardware on boot:

dmesg | grep -i blue
[9.685735] Bluetooth: Core ver 2.19
[9.685759] Bluetooth: HCI device and connection manager initialized
[9.685770] Bluetooth: HCI socket layer initialized
[9.685773] Bluetooth: L2CAP socket layer initialized
[9.685787] Bluetooth: SCO socket layer initialized
[   20.010114] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   20.010119] Bluetooth: BNEP filters: protocol multicast
[   20.010135] Bluetooth: BNEP socket layer initialized


But don't create a devide:

# hcitool dev
Devices:

The bluetooth service is running:

/etc/init.d/bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Dom 2016-03-06 18:25:33 UTC; 10min ago
 Docs: man:bluetoothd(8)
 Main PID: 1594 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
   └─1594 /usr/lib/bluetooth/bluetoothd

Mar 06 18:25:33 localhost bluetoothd[1594]: Bluetooth daemon 5.23
Mar 06 18:25:33 localhost bluetoothd[1594]: Starting SDP server
Mar 06 18:25:33 localhost bluetoothd[1594]: Bluetooth management interface 1.6 
initialized

I restarted the bluetooth service:

# /etc/init.d/bluetooth restart
[ ok ] Restarting bluetooth (via systemctl): bluetooth.service.

But the command hcitool dev returns nothing:

# hcitool dev
Devices:

And nothing from hciconfig
# hciconfig
#

There are some bluetooth module loaded:

# lsmod | grep bluetooth
bluetooth 340064  6 bnep,btusb
6lowpan_iphc   16548  1 bluetooth
rfkill 18387  5 cfg80211,bluetooth,dell_laptop
crc16  12327  2 ext4,bluetooth

Any tip?

Thanks,
Markos

Re: which files took the space

[Pascal Hambourg]

David Wright a écrit :
> On Sat 05 Mar 2016 at 21:18:55 (+0100), Pascal Hambourg wrote:
>> David Wright a écrit :
>>> You can't create files on an unmounted filesystem.
>> Of course you can, with the adequate tools. For instance mtools for FAT,
>> e2tools for ext2, ntfs-3g (previoulsy ntfsprogs) for NTFS.
> 
> Thank you for taking that sentence completely out of context.

This sentence does not need any context. It is either right or wrong by
itself.

> The tools you mention manipulate devices or images just as any
> program might manipulate a device/file whose structure it is
> familiar with, and not through the operating system.

So what ?
After you mount the filesystem, the file you created with such a tool is
visible. It's just a regular file like any other.

> So those
> "files" are irrelevant to a discussion of mount points and
> visibility

Your sentence was as irrelevant.

> (I wasn't aware that ntfs-3g worked that way: I thought it just
> mounted NTFS filesystems like any other.)

Actually the tools which were previously packaged in ntfsprogs have been
included into ntfs-3g, but I don't think they are used by the ntfs-3g
filesystem.

Re: KVM Bridge wlan0

[Pascal Hambourg]

Hello,

timothy.marion@marion.systems a écrit :
> 
> I am to stupid to figure out how to setup a bridge using wlan0.

No, you're not. You're just ignorant of an important fact : bridging of
a wireless interface in managed (asociated) or adhoc mode has been
disabled for some time now, because, by design, it just can't work.
Bridging requires to send and receive frames with a different MAC
address, but the wireless frame format prevents an interface in managed
mod from doing this. Only an interface in master (access point) mode can
do this.

Re: binary-i386 packages missing in Release file

[Sven Hartge]

Reco  wrote:

> 1) Locate the line like this in a file inside /etc/apt/sources.list.d:

> deb http://dl.google.com/linux/chrome/deb/

> 2) Change it to:

> deb [amd64] http://dl.google.com/linux/chrome/deb/

> This warning should go away.

This will only be a temporary fix as the google-chrome package installs
a cron-job to verfiy the content of the source.list file and replace it
with a pristine copy if it has been changed.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Fwd: KVM Bridge wlan0

[Timothy Marion]

I have a laptop with an wireless adapter. I would like to run KVM with virtual 
machines. I would like to be able to access the internet from the virtual 
machine. Can anybody tell me how that is done using the wireless adapter?




> Begin forwarded message:
> 
> From: Reco 
> Subject: Re: KVM Bridge wlan0
> Date: March 6, 2016 at 2:42:42 PM EST
> To: debian-user@lists.debian.org
> Resent-From: debian-user@lists.debian.org
> 
>   Hi.
> 
> Please refrain from top-posting.
> Please do not CC me, I'm subscribed to the list.
> 
> On Sun, 6 Mar 2016 14:05:32 -0500
> Timothy Marion  wrote:
> 
>> I do not know that I want to bridge eth0 to wlan0.
> 
> You have it anyway in the current configuration.
> 
> 
>> I have one working interface on my computer wlan0. 
> 
> Er, your 'ifconfig' list says otherwise. At the very least you have a
> wired interface called eth0. It's irrelevant to the current problem,
> though.
> 
> 
>> I want a virtual machine using KVM to be able to communicate to the
> internet using wlan0. 
> 
> There are multiple ways of doing it. Bridge, NAT, tunnels, you name it.
> 
> 
>> All documentation I can find indicates that is done with a bridge. 
> 
> Because it's the simpliest way to accomplish such connectivity. But
> about the only *real* need to use a bridge arises if you need the
> outside world to communicate with your VM. As in - you need someone to
> establish inbound connections to your VM with the minimal hassle.
> 
> 
>> All documentation I can find indicates you do this
> with eth0. I do not use eth0. I have wlan0.
> 
> Got it.
> 
> 
>> good new! I now have br0 with eth0 and wlan0.
> 
> Just as planned.
> 
> 
>> bad new! now the laptop no longer has any internet connectivity.
> 
> Which is clearly shown by this (note NO-CARRIER):
> 
>> 2: eth0:  mtu 1500 qdisc pfifo_fast 
>> master br0 state DOWN mode DEFAULT group default qlen 1000
>>link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
>> 3: wlan0:  mtu 1500 qdisc mq master br0 
>> state DOWN mode DORMANT group default qlen 1000
>>link/ether ac:b5:7d:3d:18:df brd ff:ff:ff:ff:ff:ff
>> 4: br0:  mtu 1500 qdisc noqueue state 
>> DOWN mode DEFAULT group default 
>>link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
> 
> So, disregarding eth0. Do you have wpa_supplicant running? Does wpa_cli
> show successful association with your AP?
> 
> Reco
> 

Re: binary-i386 packages missing in Release file

[Reco]

Hi.

On Sun, 6 Mar 2016 14:34:25 -0500
Haines Brown  wrote:

> I have jessie installed on an AMD64 machine, which lacks any desktop
> environment.
> 
> I downloaded google-chrome AMD64 deb from the Chrome website and
> installed by running dpkg -i on it. It works OK. But now I want to add
> flashplugin-nonfree for it or, if that fails to use it for my
> iceweasel. In order to install flashplugin-nonfree I added contrib to
> the sources.list.
> 
> When I do aptitude update, the contrib it hit, but the update fails
> because:
> 
> > W: Failed to fetch
> > http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable to
> > find expected entry 'main/binary-i386/Packages' in file

1) Locate the line like this in a file inside /etc/apt/sources.list.d:

deb http://dl.google.com/linux/chrome/deb/

2) Change it to:

deb [amd64] http://dl.google.com/linux/chrome/deb/

This warning should go away.

Reco

Re: binary-i386 packages missing in Release file

[Sven Hartge]

Haines Brown  wrote:

> I have jessie installed on an AMD64 machine, which lacks any desktop
> environment.

> I downloaded google-chrome AMD64 deb from the Chrome website and
> installed by running dpkg -i on it. It works OK. But now I want to add
> flashplugin-nonfree for it or, if that fails to use it for my
> iceweasel. In order to install flashplugin-nonfree I added contrib to
> the sources.list.

> When I do aptitude update, the contrib it hit, but the update fails
> because:

>> W: Failed to fetch 
>> http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable to find 
>> expected entry 'main/binary-i386/Packages' in file

Google stopped supporting Chrome on 32bit Linux. There is no more Google
Chrome for i386.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: KVM Bridge wlan0

[Reco]

Hi.

Please refrain from top-posting.
Please do not CC me, I'm subscribed to the list.

On Sun, 6 Mar 2016 14:05:32 -0500
Timothy Marion  wrote:

> I do not know that I want to bridge eth0 to wlan0.

You have it anyway in the current configuration.


> I have one working interface on my computer wlan0. 

Er, your 'ifconfig' list says otherwise. At the very least you have a
wired interface called eth0. It's irrelevant to the current problem,
though.


> I want a virtual machine using KVM to be able to communicate to the
internet using wlan0. 

There are multiple ways of doing it. Bridge, NAT, tunnels, you name it.


> All documentation I can find indicates that is done with a bridge. 

Because it's the simpliest way to accomplish such connectivity. But
about the only *real* need to use a bridge arises if you need the
outside world to communicate with your VM. As in - you need someone to
establish inbound connections to your VM with the minimal hassle.


> All documentation I can find indicates you do this
with eth0. I do not use eth0. I have wlan0.

Got it.


> good new! I now have br0 with eth0 and wlan0.

Just as planned.


> bad new! now the laptop no longer has any internet connectivity.

Which is clearly shown by this (note NO-CARRIER):

> 2: eth0:  mtu 1500 qdisc pfifo_fast master 
> br0 state DOWN mode DEFAULT group default qlen 1000
> link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
> 3: wlan0:  mtu 1500 qdisc mq master br0 
> state DOWN mode DORMANT group default qlen 1000
> link/ether ac:b5:7d:3d:18:df brd ff:ff:ff:ff:ff:ff
> 4: br0:  mtu 1500 qdisc noqueue state DOWN 
> mode DEFAULT group default 
> link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff

So, disregarding eth0. Do you have wpa_supplicant running? Does wpa_cli
show successful association with your AP?

Reco

binary-i386 packages missing in Release file

[Haines Brown]

I have jessie installed on an AMD64 machine, which lacks any desktop
environment.

I downloaded google-chrome AMD64 deb from the Chrome website and
installed by running dpkg -i on it. It works OK. But now I want to add
flashplugin-nonfree for it or, if that fails to use it for my
iceweasel. In order to install flashplugin-nonfree I added contrib to
the sources.list.

When I do aptitude update, the contrib it hit, but the update fails
because:

> W: Failed to fetch
> http://dl.google.com/linux/chrome/deb/dists/stable/Release: Unable to
> find expected entry 'main/binary-i386/Packages' in file



 

Re: KVM Bridge wlan0

[Timothy Marion]

Different config similar result

did not email actual ssid, psk. I’m a idiot not a moron.

I do not know that I want to bridge eth0 to wlan0.

I have one working interface on my computer wlan0. I want a virtual machine 
using KVM to be able to communicate to the internet using wlan0. All 
documentation I can find indicates that is done with a bridge. All 
documentation I can find indicates you do this with eth0. I do not use eth0. I 
have wlan0. 

changed /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


# manual wifi configuration
# using wpa_pashphrase to generate wpa-psk string
auto wlan0
iface wlan0 inet manual
wpa_ssidX
wpa-psk x
pre-up /sbin/iw dev wlan0 set 4addr on

auto br0
iface br0 inet static
address 192.168.1.100
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 199.231.188.115
dns-nameservers 128.199.172.116
bridge_ports eth0 wlan0
bridge_stp off
bridge_fd 0
bridge_maxwait 0


good new! I now have br0 with eth0 and wlan0.

bad new! now the laptop no longer has any internet connectivity.


ifconfig

br0   Link encap:Ethernet  HWaddr 2c:60:0c:2f:be:18  
  inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0  Link encap:Ethernet  HWaddr 2c:60:0c:2f:be:18  
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:93 errors:0 dropped:0 overruns:0 frame:0
  TX packets:93 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:9015 (8.8 KiB)  TX bytes:9015 (8.8 KiB)

wlan0 Link encap:Ethernet  HWaddr ac:b5:7d:3d:18:df  
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:36 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:4068 (3.9 KiB)  TX bytes:0 (0.0 B)


ip link

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 1500 qdisc pfifo_fast master 
br0 state DOWN mode DEFAULT group default qlen 1000
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc mq master br0 
state DOWN mode DORMANT group default qlen 1000
link/ether ac:b5:7d:3d:18:df brd ff:ff:ff:ff:ff:ff
4: br0:  mtu 1500 qdisc noqueue state DOWN 
mode DEFAULT group default 
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff


ip addr

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast master 
br0 state DOWN group default qlen 1000
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc mq master br0 
state DOWN group default qlen 1000
link/ether ac:b5:7d:3d:18:df brd ff:ff:ff:ff:ff:ff
4: br0:  mtu 1500 qdisc noqueue state DOWN 
group default 
link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.100/24 brd 192.168.1.255 scope global br0
   valid_lft forever preferred_lft forever





> On Mar 6, 2016, at 12:53 PM, Reco  wrote:
> 
>   Hi.
> 
> On Sun, 06 Mar 2016 12:33:57 -0500
> timothy.marion@marion.systems wrote:
> 
>> I can only find 1 reference to using wlan0 for bridging.
>> https://wiki.debian.org/BridgeNetworkConnections This WEB Site and it
>> talks about using ebtable. Is ebtable the only way to have a bridge for
>> KVM with wlan0 ?
> 
> No. ebtables come after the bridge is set up. Consider ebtables a form
> of access control. It's not mandatory to use them by any means.
> 
> 
>> I refuse to believe I am the 

Re: GLPI - extjs: sous-répertoire manquant

[Ph. Gras]

Le 6 mars 2016 à 17:58, Jean-Marc  a écrit :

> salut la liste,
> 
> J'ai récemment posté et reçu de l'aide pour installer et configurer GLPI 
> grâce à nginx.
> 
> Mes premiers essais se heurtent à un soucis :
> 2016/03/06 17:37:37 [error] 19156#0: *10229 open() 
> "/usr/share/glpi/lib/extjs/locale/ext-lang-en.js" failed (2: No such file or 
> directory), client: 192.168.x.x, server: _, request: "GET 
> /glpi/lib/extjs/locale/ext-lang-en.js HTTP/1.1", host: "x.localdomain", 
> referrer: "http://x.localdomain/glpi/login.php;
> 
> Normal, dans le répertoire extjs, pas de sous-répertoire locale.
> 
> Et c'est repris comme un bug :
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766744
> 
> Apparemment, l'absence de ce sous-répertoire ne pose pas de soucis à GLPI et 
> pas de soucis non plus à certains web serveur comme Apache qui ont l'air plus 
> souples (mis à part les nombreux messages d'erreur).
> 
> Mais nginx semble moins tolérant.
> 
> Des idées / suggestions ?

Je galère aussi en ce moment avec Mailman (Répertoire factice /cgi-bin/mailman) 
+ NginX

La documentation est là :
http://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rewrite
http://nginx.org/en/docs/http/ngx_http_core_module.html#location
http://nginx.org/en/docs/http/ngx_http_core_module.html#root

Mais c'est clair comme du jus de chique, j'essaye de comprendre depuis un bail 
:-(

Des idées / suggestions ?

Ph. Gras
> 
> 
> Jean-Marc 

Re: Problemas con la conexión inalámbrica en la instalación

[Pablo Villacorta Pérez]

He pasado de configurar la conexión inalambrica durante la instalación y
ahora me da otro error: "The 'grub-pc' package failed to install into
/target/".
¿Cómo instalo el paquete?

El 6 de marzo de 2016, 18:54, Camaleón  escribió:

> El Sun, 06 Mar 2016 18:14:50 +0100, Pablo Villacorta Pérez escribió:
>
> (ese formato...)
>
> > Buenas Tardes:
> >
> > Os escribo para ver si me podéis solucionar un problema que estoy
> > teniendo al instalar Debian Jessie.
> > Al probar el sistema operativo si instalarlo en la versión Live me
> > conecto correctamente a mi red inalámbrica, pero cuando comienzo la
> > instalación y elijo la red a la que me quiero conectar me arroja el
> > error "Failure of key exchange and association" aún cuando la clave WPA
> > es correcta.
>
> No te recomiendo usar wifi en la instalación porque dependiendo del tipo
> de adaptador de red que tengas necesitarás cargar algún firmware
> adicional y el instalador no es un lugar "cómodo" para hacerlo :-)
>
> Aún así, si quieres seguir por ese camino salta a una consola de
> depuración cuando estés configurando la red vía wifi para ver qué te
> dicen los registros.
>
> > He buscado en Google y no soy el único al que le ha sucedido esto, pero
> > en ningún sitio encuentro una solución. ¿A alguién más le ha sucedido lo
> > mismo o sabe cómo solucionarlo?
>
> Es un problema habitual. De hecho, ese escenario no estaba soportado
> hasta hace poco, es decir, era habitual que fallara (y que lo siga
> haciendo). Yo siempre uso la mini ISO y una conexión de red cableada o el
> primer DVD como fuente de datos de la instalación.
>
> Saludos,
>
> --
> Camaleón
>
>

Re: Problemas con la conexión inalámbrica en la instalación

[Camaleón]

El Sun, 06 Mar 2016 18:14:50 +0100, Pablo Villacorta Pérez escribió:

(ese formato...)

> Buenas Tardes:
> 
> Os escribo para ver si me podéis solucionar un problema que estoy
> teniendo al instalar Debian Jessie.
> Al probar el sistema operativo si instalarlo en la versión Live me
> conecto correctamente a mi red inalámbrica, pero cuando comienzo la
> instalación y elijo la red a la que me quiero conectar me arroja el
> error "Failure of key exchange and association" aún cuando la clave WPA
> es correcta.

No te recomiendo usar wifi en la instalación porque dependiendo del tipo 
de adaptador de red que tengas necesitarás cargar algún firmware 
adicional y el instalador no es un lugar "cómodo" para hacerlo :-)

Aún así, si quieres seguir por ese camino salta a una consola de 
depuración cuando estés configurando la red vía wifi para ver qué te 
dicen los registros.

> He buscado en Google y no soy el único al que le ha sucedido esto, pero
> en ningún sitio encuentro una solución. ¿A alguién más le ha sucedido lo
> mismo o sabe cómo solucionarlo?
 
Es un problema habitual. De hecho, ese escenario no estaba soportado 
hasta hace poco, es decir, era habitual que fallara (y que lo siga 
haciendo). Yo siempre uso la mini ISO y una conexión de red cableada o el 
primer DVD como fuente de datos de la instalación.

Saludos,

-- 
Camaleón

Re: KVM Bridge wlan0

[Reco]

Hi.

On Sun, 06 Mar 2016 12:33:57 -0500
timothy.marion@marion.systems wrote:

> I can only find 1 reference to using wlan0 for bridging.
> https://wiki.debian.org/BridgeNetworkConnections This WEB Site and it
> talks about using ebtable. Is ebtable the only way to have a bridge for
> KVM with wlan0 ?

No. ebtables come after the bridge is set up. Consider ebtables a form
of access control. It's not mandatory to use them by any means.


> I refuse to believe I am the only human on earth trying to do KVM on a
> laptop with wlan0. Somebody must have done this already. I cannot be 
> the first person to want to bridge an wlan0 interface.

Of course you're not the first. So...


> wpa-psk   

First, I suggest you to change your WPA authentication right away, as
you've just shared your WPA key with all the world.

Second,


> auto br0
> iface br0 inet static

>   bridge_ports eth0

This part is wrong. You want to bridge some interfaces to wlan0 via
br0, yet you don't include wlan0 into the bridge.
The correct way of doing this should be:

bridge_ports eth0 wlan0

Assuming, of course, that you'll never want to have different IPs on
eth0 and wlan0.


Third, 

> Mar 06 12:08:43 beeker networking[2344]: Configuring network
> interfaces...can't add wlan0 to bridge br0: Operation not supported

something strange goes here. You've told interfaces(5) not to add wlan0
to br0, yet there's someone who tries to do it. Is it the manual
invocation of "brctl addif"?

"can't add wlan0 to bridge br0: Operation not supported" should be
easily defeated with good old:

iw dev wlan0 set 4addr on

I.e. edit your /etc/network/interfaces like this:

auto wlan0
iface wlan0 inet manual
  wpa_ssid  XXX
  wpa-psk   YYY
  pre-up /sbin/iw dev wlan0 set 4addr on

Reco

Re: What else must I do to avoid installing "suggests"? Was: How to get a "minimal font set"?

[Linux-Fan]

[Sun, 6 Mar 2016 12:12:20 -0500] Kynn Jones  wrote:
> Thank you for all your comments and suggestions.
> 
> My interest in this question stems from the fact that I'm getting
> ready to do a full reinstallation of my system, and I don't want to
> repeat my previous mistakes.
> 
> My concern is that the unwanted packages could have landed in my hard
> drive when the system was first installed, even though I kept my
> choices at the time very minimalistic.  (E.g. whatever the Debian
> installer uses for installing packages has the equivalent of
> `APT::Install-Suggests "1"` or `APT::Install-Recommends "1"`.)

One of the most minimal installations can be archieved using
`debootstrap`. I am sure, one can also configure to disable Recommends
when using `debootstrap` (I do not know how, sorry).

Even if that is not possible, a `debootstrap`-created installation is
very minimal (likely not to contain /any/ fonts :) ).

[...]

> The config for recommends looks like one of the holes I need to plug.

[...]

Many people performing more or less minimal installations do this. I
believe it is not generally a good idea, as ``Recommends'' ... to quote
http://www.debian.org/doc/debian-policy/ch-relationships.html

This declares a strong, but not absolute, dependency.
The Recommends field should list packages that would be found
together with this one in all but unusual installations.

Think of a network-analyisis tool which does not require network access
to be started. Installing it should probably not depend on components
required to perform live analysis as we can imagine use cases where
only offline opening of captures is necessary. Still, I would expect
the tool to be able to perform live analysis when I install it, thus the
network functionality should be a ``Recommends''. At least, this is
how far I understand Debian dependencies.

> The packages that `aptitude why` shows as being installed due to
> chains containing suggests remain a mystery.  It could be a quirk (or
> bug) in `aptitude why` (e.g. for those packages there may be *other*
> reasons for their being installed that are based solely on
> recommends).

[...]

As I already wrote, I have also seen this behaviour. `aptitude why`
sometimes reports Suggests while stronger dependencies (like
Recommends) are the real reason.

HTH
Linux-Fan

-- 
http://masysma.lima-city.de/


pgpfPrQ_1AFPr.pgp
Description: OpenPGP digital signature

KVM Bridge wlan0

[timothy . marion]

Hi All,

I have a laptop with a wireless interface.

I would like to use kvm.

I am to stupid to figure out how to setup a bridge using wlan0.

yes I am a idiot. Yes I need someone who can spell it out character by
character for me.

I can find many, many, many, many, many , how many do you need examples
of setting up a bridge with eth0.

I can only find 1 reference to using wlan0 for bridging.
https://wiki.debian.org/BridgeNetworkConnections This WEB Site and it
talks about using ebtable. Is ebtable the only way to have a bridge for
KVM with wlan0 ?

I refuse to believe I am the only human on earth trying to do KVM on a
laptop with wlan0. Somebody must have done this already. I cannot be 
the

first person to want to bridge an wlan0 interface.

root@beeker:/etc/network# uname -a
Linux beeker 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4
(2016-02-29) x86_64 GNU/Linux

root@beeker:/etc/network# brctl show
bridge name bridge id   STP enabled interfaces
br0 8000.   no
root@beeker:/etc/network# brctl addif br0 wlan0
can't add wlan0 to bridge br0: Operation not supported


root@beeker:/etc/network# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


# manual wifi configuration
# using wpa_pashphrase to generate wpa-psk string
auto wlan0
iface wlan0 inet manual
 wpa_ssid   KxxxF

wpa-psk 5303080c4418c4a7123456789031a23218fb70525ab238f71eafe99edfe05104

auto br0
iface br0 inet static
 address 192.168.1.100
 network 192.168.1.0
 netmask 255.255.255.0
 broadcast 192.168.1.255
 gateway 192.168.1.1
 dns-nameservers 199.231.188.115
 dns-nameservers 128.199.172.116
 bridge_ports eth0
 bridge_stp off
 bridge_fd 0
 bridge_maxwait 0

root@beeker:/etc/network# sudo systemctl status networking
● networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
   Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
 /lib/systemd/system/networking.service.d
└─network-pre.conf
Active: inactive (dead) since Sun 2016-03-06 12:07:53 EST; 30s ago
   Process: 2331 ExecStop=/etc/init.d/networking stop (code=exited,
status=0/SUCCESS)
   Process: 1829 ExecStart=/etc/init.d/networking start (code=exited,
status=0/SUCCESS)

Mar 06 11:06:47 beeker networking[1829]: Configuring network
interfaces...RTNETLINK answers: File exists
Mar 06 11:06:47 beeker networking[1829]: Failed to bring up br0.
Mar 06 11:06:48 beeker networking[1829]: done.
Mar 06 11:57:31 beeker wpa_supplicant[535]: wlan0: WPA: Group rekeying
completed with 18:1b:eb:78:d9:2e [GTK=CCMP]
Mar 06 12:07:53 beeker networking[2331]: not deconfiguring network
interfaces: network file systems still mounted. ... (warning).
root@beeker:/etc/network# sudo systemctl start networking
root@beeker:/etc/network# sudo systemctl status networking
● networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
   Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
 /lib/systemd/system/networking.service.d
└─network-pre.conf
Active: active (running) since Sun 2016-03-06 12:08:43 EST; 15s ago
   Process: 2331 ExecStop=/etc/init.d/networking stop (code=exited,
status=0/SUCCESS)
   Process: 2344 ExecStart=/etc/init.d/networking start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/networking.service
├─535 /sbin/wpa_supplicant -s -B -P
/run/wpa_supplicant.wlan0.pid -i wlan0 -D nl80211,wext -C
/run/wpa_supplicant
└─583 dhclient -v -pf /run/dhclient.wlan0.pid -lf
/var/lib/dhcp/dhclient.wlan0.leases wlan0

Mar 06 12:08:43 beeker networking[2344]: Configuring network
interfaces...can't add wlan0 to bridge br0: Operation not supported
Mar 06 12:08:43 beeker networking[2344]: RTNETLINK answers: File exists
Mar 06 12:08:43 beeker networking[2344]: Failed to bring up br0.
Mar 06 12:08:43 beeker networking[2344]: done.
root@beeker:/etc/network# ip address
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
 link/ether 2c:60:0c:2f:be:18 brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc mq state UP
group default qlen 1000
 link/ether ac:b5:7d:3d:18:df brd ff:ff:ff:ff:ff:ff
 inet 192.168.1.2/24 brd 192.168.1.255 scope global wlan0
valid_lft forever preferred_lft 

Re: GLPI - extjs: sous-répertoire manquant

[Bernard Schoenacker]

Le Sun, 6 Mar 2016 17:58:55 +0100,
Jean-Marc  a écrit :

> salut la liste,
> 
> J'ai récemment posté et reçu de l'aide pour installer et configurer
> GLPI grâce à nginx.
> 
> Mes premiers essais se heurtent à un soucis :
> 2016/03/06 17:37:37 [error] 19156#0: *10229 open()
> "/usr/share/glpi/lib/extjs/locale/ext-lang-en.js" failed (2: No such
> file or directory), client: 192.168.x.x, server: _, request:
> "GET /glpi/lib/extjs/locale/ext-lang-en.js HTTP/1.1", host:
> "x.localdomain", referrer: "http://x.localdomain/glpi/login.php;
> 
> Normal, dans le répertoire extjs, pas de sous-répertoire locale.
> 
> Et c'est repris comme un bug :
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766744
> 
> Apparemment, l'absence de ce sous-répertoire ne pose pas de soucis à
> GLPI et pas de soucis non plus à certains web serveur comme Apache
> qui ont l'air plus souples (mis à part les nombreux messages
> d'erreur).
> 
> Mais nginx semble moins tolérant.
> 
> Des idées / suggestions ?
> 
> 
> Jean-Marc 

bonjour,

serait il possible de comparer avec ce tuto :

https://support.rackspace.com/how-to/installing-nginx-and-php-fpm-setup-for-nginx/
https://www.digitalocean.com/community/tutorials/how-to-install-an-nginx-mysql-and-php-femp-stack-on-freebsd-10-1
https://memo-linux.com/installation-pas-a-pas-de-glpi-sous-un-serveur-linux/


slt
bernard

GLPI - extjs: sous-répertoire manquant

[Jean-Marc]

salut la liste,

J'ai récemment posté et reçu de l'aide pour installer et configurer GLPI grâce 
à nginx.

Mes premiers essais se heurtent à un soucis :
2016/03/06 17:37:37 [error] 19156#0: *10229 open() 
"/usr/share/glpi/lib/extjs/locale/ext-lang-en.js" failed (2: No such file or 
directory), client: 192.168.x.x, server: _, request: "GET 
/glpi/lib/extjs/locale/ext-lang-en.js HTTP/1.1", host: "x.localdomain", 
referrer: "http://x.localdomain/glpi/login.php;

Normal, dans le répertoire extjs, pas de sous-répertoire locale.

Et c'est repris comme un bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766744

Apparemment, l'absence de ce sous-répertoire ne pose pas de soucis à GLPI et 
pas de soucis non plus à certains web serveur comme Apache qui ont l'air plus 
souples (mis à part les nombreux messages d'erreur).

Mais nginx semble moins tolérant.

Des idées / suggestions ?


Jean-Marc 


pgpZpKoMPBo6P.pgp
Description: PGP signature

Problemas con la conexión inalámbrica en la instalación

[Pablo Villacorta Pérez]

Buenas Tardes:

Os escribo para ver si me podéis solucionar un problema que estoy teniendo
al instalar Debian Jessie.
Al probar el sistema operativo si instalarlo en la versión Live me conecto
correctamente a mi red inalámbrica, pero cuando comienzo la instalación y
elijo la red a la que me quiero conectar me arroja el error "Failure of key
exchange and association" aún cuando la clave WPA es correcta.
He buscado en Google y no soy el único al que le ha sucedido esto, pero en
ningún sitio encuentro una solución. ¿A alguién más le ha sucedido lo mismo
o sabe cómo solucionarlo?


Gracias a todos

Re: What else must I do to avoid installing "suggests"? Was: How to get a "minimal font set"?

[Kynn Jones]

Thank you for all your comments and suggestions.

My interest in this question stems from the fact that I'm getting
ready to do a full reinstallation of my system, and I don't want to
repeat my previous mistakes.

My concern is that the unwanted packages could have landed in my hard
drive when the system was first installed, even though I kept my
choices at the time very minimalistic.  (E.g. whatever the Debian
installer uses for installing packages has the equivalent of
`APT::Install-Suggests "1"` or `APT::Install-Recommends "1"`.)

On closer inspection, the fraction of unwanted fonts that I got
through chains of recommends is more substantial than that for chains
containing suggests.  And

% apt-config dump | grep -i -e suggest -e recommend
APT::Install-Recommends "1";
APT::Install-Suggests "0";

The config for recommends looks like one of the holes I need to plug.
(I'm not sure where it's coming from; I certainly did not set it
explicitly.  I suppose I can negate it through /etc/apt/apt.conf.)

The packages that `aptitude why` shows as being installed due to
chains containing suggests remain a mystery.  It could be a quirk (or
bug) in `aptitude why` (e.g. for those packages there may be *other*
reasons for their being installed that are based solely on
recommends).

Thank you all again!

kj

Re: debian amd64, testing, gnome: stabilisé ?

[Alban Gruin]

Bonjour,

>Peut-on raisonnablement recommander testing actuellement ?
Ça dépend de ton usage. La FAQ peut t'aider à ce sujet (cf. [1] et [2]).

>La route semble sûre?
Pour l'instant testing n'est pas encore en gel de paquets. Il vaut donc
mieux éviter de s'attendre à de la stabilité sur cette version pour le
moment, tout peut casser et ne pas avoir de correctif avant un certain
temps (cf. [3] et [4]). Ceci dit, si le statut est assez élevé, le
risque de mésaventure ne devrait pas être trop fort (mais garre à une
grosse upgrade !)

[1] https://www.debian.org/doc/manuals/debian-faq/ch-choosing.fr.html#s3.1
[2] https://www.debian.org/doc/manuals/debian-faq/ch-choosing.fr.html#s3.1.5
[3] https://www.debian.org/doc/manuals/debian-faq/ch-choosing.fr.html#s3.1.6
[4] https://www.debian.org/doc/manuals/debian-faq/ch-choosing.fr.html#s3.1.7

Bonne fin de journée.
-- 
   Alban Gruin


signature.asc
Description: PGP signature

debian amd64, testing, gnome: stabilisé ?

[Ralf]

Bonjour,

J'utilise Debian / Jessie sur un portable amd64, i915, ssd pour 
bureautique, media, serveur local, usage privé 
et professionnel.

Les dose-tools (ex debian-weather) indiquent un beau fixe en 
testing pour l'architecture amd64 en main, contrib, tant qu'on n'a pas 
besoin de compiler, ce qui est mon cas ; le "Status of GNOME 3.18 in Debian" 
est donné up-to-date dans testing à presque 100%.

Je souhaiterais passer sous Gnome 3.18, donc testing ; pour les progrès 
accomplis dans les GOA, dont les services Google et le Drive.

La route semble sûre? Point de migration vers 3.20 en vue 
avant la prochaine stable ? Peut-on raisonnablement recommander 
testing actuellement ? 

NB: Un système ne se réduit pas au bureau, 
mais il n'y a plus guère de gros couacs ...? ;)


Merci la liste :)

Ralf

Re: help using apt-build

[Javi Barroso]

Hello,

El 6 de marzo de 2016 15:14:12 CET, Michael Fothergill 
 escribió:
>On 6 March 2016 at 11:06, Javier Barroso  wrote:
>
>> Hello  Michael,
>>
>> On Sun, Mar 6, 2016 at 11:42 AM, Michael Fothergill
>>  wrote:
>> >
>> >
>> > On 5 March 2016 at 20:00, Javier Barroso 
>wrote:
>> >>
>> >> Hello,
>> >>
>> >> On Sat, Mar 5, 2016 at 3:48 PM, Michael Fothergill
>> >>  wrote:
>> >> >
>> >> >
>> >> > On 23 February 2016 at 18:46, Javi Barroso
>
>> >> > wrote:
>> >> >>
>> >> >> Hello,
>> >> >>
>> >> >> El 23 de febrero de 2016 18:08:32 CET, Michael Fothergill
>> >> >>  escribió:
>> >> >> >Dear Folks,
>> >> >> >
>> >> >> >I tried using apt-build to install a source file:
>> >> >> >
>> >> >> >root@rhubarb:/home/michaelmikef/Downloads# ls -l adun*
>> >> >> >
>> >> >> >-rw-r--r-- 1 michaelmikef michaelmikef 1395 Feb 23 16:36
>> >> >> >adun.app_0.81-6.dsc
>> >> >> >
>> >> >> >root@rhubarb:/home/michaelmikef/Downloads# apt-build install
>> >> >> >adun.app_0.81-6.dsc
>> >> >> >
>> >> >> >W: Unable to locate package adun.app_0.81-6.dsc
>> >> >> >Unable to find source candidate for adun.app_0.81-6.dsc
>> >> >> >
>> >> >> >What am I doing wrong here?
>> >> >>
>> >> >> I think you need add deb-src line to your apt source list, so
>it can
>> >> >> download from internet (I think you need the name of the
>package and
>> >> >> not the
>> >> >> name of the file) and then build the package
>> >> >>
>> >> >> Maybe you can use --source to tell apt-build to not download
>the
>> >> >> source.
>> >> >> See the man page and its sinopsis
>> >> >
>> >> >
>> >> > I couldn't make apt-build work but the apt build dep command did
>work
>> >> > -however I think that some dependencies are missing in stretch
>that
>> >> > would be
>> >> > there in jessie
>> >> >
>> >> > I have a jessie install and I will use that instead for this.
>> >>
>> >> Hello,
>> >>
>> >> At debian sid apt-build is working:
>> >>
>> >> # apt update
>> >> # apt-build source-build adun.app
>> >> # ls /var/cache/apt-build/repository/
>> >> adun.app_0.81-7+aptbuild1_amd64.deb
>> >> adun-core_0.81-7+aptbuild1_amd64.deb Packages.gz
>> >> adun.app-dbg_0.81-7+aptbuild1_amd64.deb  dists/
>> >>Release
>> >>
>> >> Build directory on /var/cache/apt-build/build
>> >
>> >
>> > I did apt update:
>> >
>> > It worked OK except for a gripe about some i386 packages -
>> >
>> > Reading package lists... Done
>> > N: Skipping acquire of configured file 'main/binary-i386/Packages'
>as
>> > repository 'http://dl.google.com/linux/chrome/deb stable InRelease'
>> doesn't
>> > support architecture 'i386'
>>
>> To fix it, you need to change
>> /etc/apt/sources.list.d/google-chrome.list to read:
>>
>> deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
>>
>>
>> > W: Failed to fetch
>> >
>>
>file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
>> > File not found -
>> >
>/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
>> > (2: No such file or directory)
>> > E: Some index files failed to download. They have been ignored, or
>old
>> ones
>> > used instead.
>> >
>> > I then checked the repository directory:
>> >
>> > root@rhubarb:/var/cache/apt-build/build# ls
>> /var/cache/apt-build/repository
>> >
>> > dists  Packages.gz  Release
>> >
>> > I then tried the command
>> >
>> > root@rhubarb:/var/cache/apt-build/build# apt-build build-source
>adun.app
>> > E: Unable to find a source package for adun.app
>> > Some error occured building package
>> >
>> > What I am doing wrong here?
>>
>> Seems like adun.app was removed from stretch [1], but that it is on
>> sid [2] but cannot be installed/migrated on/to stretch [3]
>>
>> Maybe you can try to add deb-src unstable (sid) line to sources.list
>> and try again (not sure if all build depends will be on stretch).
>>
>
>​I changed the deb-src entry to unstable from stretch​
>
>​Then I tried the apt-build command:​
>
>root@rhubarb:/var/cache/apt-build/build# apt-build build-source
>adun.app
>Building the following packages from source:
>-> Installing build dependencies (for adun.app=(none)) <-
>sh: 1: Syntax error: "(" unexpected
>-> Updating package lists <-
>Get:1 file:/var/cache/apt-build/repository apt-build InRelease
>Ign:1 file:/var/cache/apt-build/repository apt-build InRelease
>Get:2 file:/var/cache/apt-build/repository apt-build Release [107 B]
>Get:2 file:/var/cache/apt-build/repository apt-build Release [107 B]
>Get:3 file:/var/cache/apt-build/repository apt-build Release.gpg
>Ign:3 file:/var/cache/apt-build/repository apt-build Release.gpg
>Get:4 file:/var/cache/apt-build/repository apt-build/main amd64
>Packages
>Ign:4 file:/var/cache/apt-build/repository apt-build/main amd64
>Packages
>Get:5 file:/var/cache/apt-build/repository 

Re: Problemas con WiFi luego de hacer Upgrade de Wheezy a Jessie

[Camaleón]

El Sat, 05 Mar 2016 19:07:27 -0600, Carlos Carcamo escribió:

> Saludos lista,
> 
> Tengo un pequeño problemita que no se como solucionar, tal vez me
> puedan asistir un poco.
> 
> Sucede que hice un dist-upgrade de wheezy a jessie, todo anda bien
> excepto por 3 cosas, 1. el grub no me reconoció una partición con
> Fedora, 

Esto lo puedes arreglar manualmente (editando el archivo de configuración 
del menú de grub y corrigiendo -añadiendo o editando- la entrada para 
cargar fedora) o mejor dejando que primero intente arreglarlo la rutina 
de configuración del cargador automáticamente por medio de "os-
prober" (consulta la FAQ para saber los pasos exactos que tienes que dar).

When I upgraded from GRUB to GRUB2 I lost an entry to XP/WP7 , how can I 
recover the menu entry to boot there?
https://wiki.debian.org/Grub#FAQ

> 2. gdm3 no funciona y 

Bueno, como ya has instalado KDE pues nada que decir sobre ésto salvo que 
seguramente con reinstalar el paquete hubiera bastado :-)

> 3. El wifi no parece encontrar redes disponibles.

Eso te pasa por cambiar a KDE, ahora Network Manager se habrá hecho un 
lío :-P

> Para el problema 1 luego voy a googlear jajaja, el 2 no pude
> solucionarlo así que cambie gnome por KDE, el 3 es el que más me
> interesa solucionar.
> 
> dejo un poco de info:
> 
> # rfkill list all
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 
> # ifconfig
> ...
> wlan0 Link encap:Ethernet  HWaddr a4:db:30:3f:d6:f1
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> wlan0:avahi Link encap:Ethernet  HWaddr a4:db:30:3f:d6:f1
>   inet addr:169.254.11.6  Bcast:169.254.255.255 
> Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
> 
> $ lspci | grep Wireless
> 02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network
> Adapter (rev 01)

Te está cargando la IP "de pega" (avahi zeroconf), seguramente porque no 
encuentre ningún servidor DHCP desde donde obtener los datos de la 
tarjeta wifi. A malas, prueba configurando los datos manualmente, es 
decir, especificando una IP/máscara de red, pasarela, DNS, etc... para 
forzar al adaptador wifi a usar esa configuración y descartar así un 
problema de comunicación con el AP.

> $ cat /etc/network/interfaces
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> allow-hotplug eth0
> iface eth0 inet dhcp
> 
> allow-hotplug wlan0
> iface wlan0 inet dhcp
> 
> Según veo el sistema me reconoce el hardware pero por algún motivo el
> network-manager no me muestra ninguna de las redes wifi disponibles y
> no puedo conectarme a ninguna.
> 
> Alguna idea de que puede estar pasando?

Revisa el registro "/var/log/syslog" para ver qué te va diciendo. Quizá 
te falte algún firmware aunque no es probable porque el controlador de 
ese adaptador usa "ath9k" que es libre.

Saludos,

-- 
Camaleón

Re: help using apt-build

[Michael Fothergill]

On 6 March 2016 at 11:06, Javier Barroso  wrote:

> Hello  Michael,
>
> On Sun, Mar 6, 2016 at 11:42 AM, Michael Fothergill
>  wrote:
> >
> >
> > On 5 March 2016 at 20:00, Javier Barroso  wrote:
> >>
> >> Hello,
> >>
> >> On Sat, Mar 5, 2016 at 3:48 PM, Michael Fothergill
> >>  wrote:
> >> >
> >> >
> >> > On 23 February 2016 at 18:46, Javi Barroso 
> >> > wrote:
> >> >>
> >> >> Hello,
> >> >>
> >> >> El 23 de febrero de 2016 18:08:32 CET, Michael Fothergill
> >> >>  escribió:
> >> >> >Dear Folks,
> >> >> >
> >> >> >I tried using apt-build to install a source file:
> >> >> >
> >> >> >root@rhubarb:/home/michaelmikef/Downloads# ls -l adun*
> >> >> >
> >> >> >-rw-r--r-- 1 michaelmikef michaelmikef 1395 Feb 23 16:36
> >> >> >adun.app_0.81-6.dsc
> >> >> >
> >> >> >root@rhubarb:/home/michaelmikef/Downloads# apt-build install
> >> >> >adun.app_0.81-6.dsc
> >> >> >
> >> >> >W: Unable to locate package adun.app_0.81-6.dsc
> >> >> >Unable to find source candidate for adun.app_0.81-6.dsc
> >> >> >
> >> >> >What am I doing wrong here?
> >> >>
> >> >> I think you need add deb-src line to your apt source list, so it can
> >> >> download from internet (I think you need the name of the package and
> >> >> not the
> >> >> name of the file) and then build the package
> >> >>
> >> >> Maybe you can use --source to tell apt-build to not download the
> >> >> source.
> >> >> See the man page and its sinopsis
> >> >
> >> >
> >> > I couldn't make apt-build work but the apt build dep command did work
> >> > -however I think that some dependencies are missing in stretch that
> >> > would be
> >> > there in jessie
> >> >
> >> > I have a jessie install and I will use that instead for this.
> >>
> >> Hello,
> >>
> >> At debian sid apt-build is working:
> >>
> >> # apt update
> >> # apt-build source-build adun.app
> >> # ls /var/cache/apt-build/repository/
> >> adun.app_0.81-7+aptbuild1_amd64.deb
> >> adun-core_0.81-7+aptbuild1_amd64.deb Packages.gz
> >> adun.app-dbg_0.81-7+aptbuild1_amd64.deb  dists/
> >>Release
> >>
> >> Build directory on /var/cache/apt-build/build
> >
> >
> > I did apt update:
> >
> > It worked OK except for a gripe about some i386 packages -
> >
> > Reading package lists... Done
> > N: Skipping acquire of configured file 'main/binary-i386/Packages' as
> > repository 'http://dl.google.com/linux/chrome/deb stable InRelease'
> doesn't
> > support architecture 'i386'
>
> To fix it, you need to change
> /etc/apt/sources.list.d/google-chrome.list to read:
>
> deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
>
>
> > W: Failed to fetch
> >
> file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
> > File not found -
> > /var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
> > (2: No such file or directory)
> > E: Some index files failed to download. They have been ignored, or old
> ones
> > used instead.
> >
> > I then checked the repository directory:
> >
> > root@rhubarb:/var/cache/apt-build/build# ls
> /var/cache/apt-build/repository
> >
> > dists  Packages.gz  Release
> >
> > I then tried the command
> >
> > root@rhubarb:/var/cache/apt-build/build# apt-build build-source adun.app
> > E: Unable to find a source package for adun.app
> > Some error occured building package
> >
> > What I am doing wrong here?
>
> Seems like adun.app was removed from stretch [1], but that it is on
> sid [2] but cannot be installed/migrated on/to stretch [3]
>
> Maybe you can try to add deb-src unstable (sid) line to sources.list
> and try again (not sure if all build depends will be on stretch).
>

​I changed the deb-src entry to unstable from stretch​

​Then I tried the apt-build command:​

 root@rhubarb:/var/cache/apt-build/build# apt-build build-source adun.app
Building the following packages from source:
-> Installing build dependencies (for adun.app=(none)) <-
sh: 1: Syntax error: "(" unexpected
-> Updating package lists <-
Get:1 file:/var/cache/apt-build/repository apt-build InRelease
Ign:1 file:/var/cache/apt-build/repository apt-build InRelease
Get:2 file:/var/cache/apt-build/repository apt-build Release [107 B]
Get:2 file:/var/cache/apt-build/repository apt-build Release [107 B]
Get:3 file:/var/cache/apt-build/repository apt-build Release.gpg
Ign:3 file:/var/cache/apt-build/repository apt-build Release.gpg
Get:4 file:/var/cache/apt-build/repository apt-build/main amd64 Packages
Ign:4 file:/var/cache/apt-build/repository apt-build/main amd64 Packages
Get:5 file:/var/cache/apt-build/repository apt-build/main i386 Packages
Ign:5 file:/var/cache/apt-build/repository apt-build/main i386 Packages
Get:6 file:/var/cache/apt-build/repository apt-build/main all Packages
Ign:6 file:/var/cache/apt-build/repository apt-build/main all Packages
Get:7 

Re: boot problem

[lina]

df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda4   641M  235M  360M  40% /
udev 10M 0   10M   0% /dev
tmpfs   1.6G  9.1M  1.6G   1% /run
/dev/sda819G  3.6G   14G  21% /usr
tmpfs   3.9G   68K  3.9G   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
/dev/sda13  181M   32M  136M  20% /boot
/dev/sda11  547M  720K  507M   1% /tmp
/dev/sda715G  1.2G   13G   9% /home
/dev/sda12  3.7G  7.6M  3.4G   1% /usr/local
/dev/sda9   3.7G 1010M  2.5G  29% /var
/dev/sda10  6.3G   15M  6.0G   1% /var/local
/dev/sda1   197M   16M  182M   8% /boot/efi
/dev/sda15  393G   71M  373G   1% /scratch
tmpfs   788M  4.0K  788M   1% /run/user/116
tmpfs   788M  8.0K  788M   1% /run/user/1000

On Sun, Mar 6, 2016 at 3:56 PM, Keith Bainbridge
 wrote:
> Good afternoon Lina
>
> Try holding the alt key as you boot.  You should get a few icons to choose 
> osx or linux.
>
>
> If not, please send us output of command df -h
>
>
>  Original Message 
> From: lina 
> Sent: Sun Mar 06 17:55:17 AEDT 2016
> To: Debian Lists 
> Subject: boot problem
>
> Hi,
>
> After install the debian,
>
> it goes to debian OS system directly, without showing me the option of
> start Mac OS or debian OS.
>
> Any suggestions, thanks,
>
>
> Keith Bainbridge
>
> 0447 667 468
>
> keithrbaugro...@gmail.com
>
> Sent from my APad

Gnome GUI: status line issue

[Miroslav Skoric]

Hi,

I am not sure now how that has happened, but probably somewhere during 
the system upgrade from squeeze to wheezy (the upgrade done from within 
GUI), one of my machines somehow lost the ability of the status line in 
Gnome GUI to show icons of active program windows, either normal or 
[minimized]. What to do to recover that ability? (Now in the status 
line, there are only four boxes on the right for Workspaces 1-4. All the 
remaining of the line is empty black.)

Re: trying to optimize find's searches ...

[Javier Barroso]

Hello Albretch,

On Sat, Mar 5, 2016 at 6:23 AM, Albretch Mueller  wrote:
> find works significantly faster when you bag various search patterns á la:
>
> -iname '*.ko' -or -iname '*.bin' -or -iname '*.txt'
>
> but, how could you do that using a batch strategy and setting a
> variable with many "-[i]name ... -or -[i]name ..." cases?
>
> line-by-line strategies are too slow

I'm not sure what are you saying, but maybe you can play with locate
and updatedb commands (from mlocate package)

See:

$ function clean { sudo sync; echo 3 | sudo tee
/proc/sys/vm/drop_caches &> /dev/null ; } # so cache fs not count on
your test

$ clean ; time locate --regex '\.(ko|bin|txt)$' &> /dev/null

real 0m1.666s
user 0m0.592s
sys 0m0.164s

$ clean; time ( sudo find  / -iname '*.ko' -or -iname '*.bin' -or
-iname '*.txt' &> /dev/null)

real 0m57.579s
user 0m11.264s
sys 0m11.000s

See "man updatedb locate" and /etc/cron.daily/mlocate

Regards,

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Pascal Hambourg]

Randy11 a écrit :
> On 05/03/2016 22:48, Pascal Hambourg wrote:
>> Randy11 a écrit :
>>>
>>> Pour installer Jessie, j'ai seulement pris :
>>> - lv--01 pour /
>>> - lv--05 pour /var
>>> - lv--08 pour swap
>>
>> Avis personnel : donner des noms génériques aux volumes logiques
>> constitue une négation d'un des avantages de LVM, à savoir de pouvoir
>> donner aux volumes logiques des noms signifiants et non de simples
>> numéros comme les partitions.
>
> Bonne remarque. C'est une habitude d'un collègue que j'ai reprise. Je aivais
> choisi ces noms pour avoir le moins de partitons facilement identifiables
> puisque j'ai certaines sont chiffrées : ne pas faciliter les choses.

C'est un point de vue. Mais ne pas faciliter les choses pour qui ? Pour
un administrateur que cela ne va pas aider à s'y retrouver, c'est sûr.
Pour un éventuel attaquant qui peut de toute façon assez facilement
savoir ce que contiennent les volumes, sur quoi ils sont montés et à
quoi ils servent, j'ai des doutes. On n'est pas loin de la sécurité par
l'obscurité.

> L'installation date de la première version de Wheezy.

L'installateur de Wheezy créait déjà des partitions alignées sur des
blocs de 1 Mio (2048 secteurs de 512 octets). D'ailleurs on voit bien
que le début de la partition LVM est aligné sur cette taille.

Par contre ce n'est pas le cas des partitions NTFS et FAT qui sont
alignées "à l'ancienne" sur des pistes ou cylindres (63 secteurs/piste
pour la première, multiples de 255 têtes x 63 secteurs/piste pour les
deux suivantes). Comment ont-elles été créées ? Sauf erreur,
l'installateur de Windows Vista applique aussi l'alignement "moderne".

>> Solutions possibles :
>> - Créer une petite partition (5 Mo devraient suffire) formatée en ext2 à
>> monter sur /boot/grub, ce qui au mieux réduira suffisamment la taille de
>> l'image core pour qu'elle contienne dans l'espace post-MBR en évitant
>> l'intégration du module lvm, et au pire permettra à grub-install avec
>> l'option --force d'utiliser les listes de blocs.
>
> J'ai déjà 3 partitions Windows et 1 "extended"/LVM. Si les choses n'ont
> pas trop évoluées, il je ne peux plus créer de 4ème partition
> primaire.

La partition n° 4 est une partition étendue qui contient actuellement
uniquement la partition logique n° 5 servant de PV LVM, mais elle peut
contenir un nombre arbitraire de partitions logiques. Il suffit qu'il
reste un tout petit peu d'espace non alloué, même non aligné, à la fin
du disque ou au début de la partition étendue.

Dans le cas contraire, tu dois bien pouvoir réduire un poil le PV LVM et
la partition logique n° 5 qui le contient.

>> - Convertir la table de partition au format GPT avec gdisk et créer une
>> petite partition (1 Mo) de type "BIOS boot" où grub-install pourra
>> installer l'image core. Mais si le disque contient une installation de
>> Windows, ce dernier ne pourra plus démarrer. Ce problème peut néanmoins
>> être contourné avec un MBR hybride créé au moyen de gdisk.
>
> Je n'ai pas encore regarder GPT et gdisk en détail, mais est-ce compatible
> avec les partions actuelles

GPT est compatible avec tout type de partition. Il y a suffisamment
d'espace au début du disque pour y loger une table de partition GPT
standard (34 secteurs). Par contre C'est l'amorçage du Windows installé
qui ne sera pas compatible avec GPT.

> Et si après je veux changer de version de Windows comment les choses
> se passeront ?

Dans l'état actuel, Windows ne peut démarrer depuis un disque au format
GPT qu'en mode UEFI, et doit avoir été installé pour cela. D'où la
suggestion du MBR hybride qui contient une table de partition au format
MSDOS traditionnel.

>> - Si la machine a un firmware UEFI, activer l'amorçage en mode UEFI,
>> créer une partition système EFI (500 Mo recommandés, mais 5 Mo
>> suffisent) formatée en FAT à monter sur /boot/efi, installer
>> grub-efi-amd64 pour un firmware 64 bits ou grub-efi-ia32 pour un
>> firmware 32 bits. Exécuter "grub-install --removable" si nécessaire.
>> Mais à nouveau, une installation de Windows ne pourra plus démarrer en
>> dual boot avec Debian. Il faudra restaurer l'amorce de Windows dans le
>> MBR et sélectionner l'OS via le mode d'amorçage du firmware, UEFI pour
>> Debian et legacy pour Windows.
>>
> La partition EFI, peut-elle être prise sur la partie en LVM ?

Non. Les firmwares UEFI ne comprennent pas le format LVM de Linux, il ne
faut pas rêver.

J'ai mentionné les deux dernières solutions pour être complet, mais je
pense que la première est la plus simple, sûre et adaptée à la situation.

Re: help using apt-build

[Javier Barroso]

Hello  Michael,

On Sun, Mar 6, 2016 at 11:42 AM, Michael Fothergill
 wrote:
>
>
> On 5 March 2016 at 20:00, Javier Barroso  wrote:
>>
>> Hello,
>>
>> On Sat, Mar 5, 2016 at 3:48 PM, Michael Fothergill
>>  wrote:
>> >
>> >
>> > On 23 February 2016 at 18:46, Javi Barroso 
>> > wrote:
>> >>
>> >> Hello,
>> >>
>> >> El 23 de febrero de 2016 18:08:32 CET, Michael Fothergill
>> >>  escribió:
>> >> >Dear Folks,
>> >> >
>> >> >I tried using apt-build to install a source file:
>> >> >
>> >> >root@rhubarb:/home/michaelmikef/Downloads# ls -l adun*
>> >> >
>> >> >-rw-r--r-- 1 michaelmikef michaelmikef 1395 Feb 23 16:36
>> >> >adun.app_0.81-6.dsc
>> >> >
>> >> >root@rhubarb:/home/michaelmikef/Downloads# apt-build install
>> >> >adun.app_0.81-6.dsc
>> >> >
>> >> >W: Unable to locate package adun.app_0.81-6.dsc
>> >> >Unable to find source candidate for adun.app_0.81-6.dsc
>> >> >
>> >> >What am I doing wrong here?
>> >>
>> >> I think you need add deb-src line to your apt source list, so it can
>> >> download from internet (I think you need the name of the package and
>> >> not the
>> >> name of the file) and then build the package
>> >>
>> >> Maybe you can use --source to tell apt-build to not download the
>> >> source.
>> >> See the man page and its sinopsis
>> >
>> >
>> > I couldn't make apt-build work but the apt build dep command did work
>> > -however I think that some dependencies are missing in stretch that
>> > would be
>> > there in jessie
>> >
>> > I have a jessie install and I will use that instead for this.
>>
>> Hello,
>>
>> At debian sid apt-build is working:
>>
>> # apt update
>> # apt-build source-build adun.app
>> # ls /var/cache/apt-build/repository/
>> adun.app_0.81-7+aptbuild1_amd64.deb
>> adun-core_0.81-7+aptbuild1_amd64.deb Packages.gz
>> adun.app-dbg_0.81-7+aptbuild1_amd64.deb  dists/
>>Release
>>
>> Build directory on /var/cache/apt-build/build
>
>
> I did apt update:
>
> It worked OK except for a gripe about some i386 packages -
>
> Reading package lists... Done
> N: Skipping acquire of configured file 'main/binary-i386/Packages' as
> repository 'http://dl.google.com/linux/chrome/deb stable InRelease' doesn't
> support architecture 'i386'

To fix it, you need to change
/etc/apt/sources.list.d/google-chrome.list to read:

deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main


> W: Failed to fetch
> file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
> File not found -
> /var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
> (2: No such file or directory)
> E: Some index files failed to download. They have been ignored, or old ones
> used instead.
>
> I then checked the repository directory:
>
> root@rhubarb:/var/cache/apt-build/build# ls /var/cache/apt-build/repository
>
> dists  Packages.gz  Release
>
> I then tried the command
>
> root@rhubarb:/var/cache/apt-build/build# apt-build build-source adun.app
> E: Unable to find a source package for adun.app
> Some error occured building package
>
> What I am doing wrong here?

Seems like adun.app was removed from stretch [1], but that it is on
sid [2] but cannot be installed/migrated on/to stretch [3]

Maybe you can try to add deb-src unstable (sid) line to sources.list
and try again (not sure if all build depends will be on stretch).

I hope that help

Regards,

[1]  https://packages.qa.debian.org/a/adun.app/news/20150711T163912Z.html
[2] https://packages.debian.org/sid/adun.app
[3] https://release.debian.org/migration/testing.pl?package=adun.app

Re: help using apt-build

[Michael Fothergill]

On 5 March 2016 at 20:00, Javier Barroso  wrote:

> Hello,
>
> On Sat, Mar 5, 2016 at 3:48 PM, Michael Fothergill
>  wrote:
> >
> >
> > On 23 February 2016 at 18:46, Javi Barroso 
> wrote:
> >>
> >> Hello,
> >>
> >> El 23 de febrero de 2016 18:08:32 CET, Michael Fothergill
> >>  escribió:
> >> >Dear Folks,
> >> >
> >> >I tried using apt-build to install a source file:
> >> >
> >> >root@rhubarb:/home/michaelmikef/Downloads# ls -l adun*
> >> >
> >> >-rw-r--r-- 1 michaelmikef michaelmikef 1395 Feb 23 16:36
> >> >adun.app_0.81-6.dsc
> >> >
> >> >root@rhubarb:/home/michaelmikef/Downloads# apt-build install
> >> >adun.app_0.81-6.dsc
> >> >
> >> >W: Unable to locate package adun.app_0.81-6.dsc
> >> >Unable to find source candidate for adun.app_0.81-6.dsc
> >> >
> >> >What am I doing wrong here?
> >>
> >> I think you need add deb-src line to your apt source list, so it can
> >> download from internet (I think you need the name of the package and
> not the
> >> name of the file) and then build the package
> >>
> >> Maybe you can use --source to tell apt-build to not download the source.
> >> See the man page and its sinopsis
> >
> >
> > I couldn't make apt-build work but the apt build dep command did work
> > -however I think that some dependencies are missing in stretch that
> would be
> > there in jessie
> >
> > I have a jessie install and I will use that instead for this.
>
> Hello,
>
> At debian sid apt-build is working:
>
> # apt update
> # apt-build source-build adun.app
> # ls /var/cache/apt-build/repository/
> adun.app_0.81-7+aptbuild1_amd64.deb
> adun-core_0.81-7+aptbuild1_amd64.deb Packages.gz
> adun.app-dbg_0.81-7+aptbuild1_amd64.deb  dists/
>Release
>
> Build directory on /var/cache/apt-build/build
>

​I did apt update:

It worked OK except for a gripe about some i386 packages -

​Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i386/Packages' as
repository 'http://dl.google.com/linux/chrome/deb stable InRelease' doesn't
support architecture 'i386'
W: Failed to fetch
file:/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
 File not found -
/var/cache/apt-build/repository/dists/apt-build/main/binary-i386/Packages
(2: No such file or directory)
E: Some index files failed to download. They have been ignored, or old ones
used instead.

I then checked the repository directory:

root@rhubarb:/var/cache/apt-build/build# ls /var/cache/apt-build/repository

dists  Packages.gz  Release

I then tried the command

root@rhubarb:/var/cache/apt-build/build# apt-build build-source adun.app
E: Unable to find a source package for adun.app
Some error occured building package

What I am doing wrong here?

Regds

MF











>
> Regards,
> PD: apt-build need love :(
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365427
>
>

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Randy11]

On 05/03/2016 22:48, Pascal Hambourg wrote:

Randy11 a écrit :

À partir d'une configuration avec Wheezy qui comporte des partions
Windows et LVM dont 2 partitions LVM chiffrées, j'ai voulu passer de
Wheezy à Jessie par une installation complète de Jessie et non une mise
à jour - ma config Wheezy avait été un trop bricolée.

Disque /dev/sda :
/dev/sda1 100G NTFS
/dev/sda2 250G NTFS
/dev/sda3 30.3G FAT32
/dev/sda4 1.5T Extended
/dev/sda5 1.5T Linux LVM

Dans /dev/sda5, il y a 8 partitions LVM.

(...)

Pour installer Jessie, j'ai seulement pris :
- lv--01 pour /
- lv--05 pour /var
- lv--08 pour swap

Avis personnel : donner des noms génériques aux volumes logiques
constitue une négation d'un des avantages de LVM, à savoir de pouvoir
donner aux volumes logiques des noms signifiants et non de simples
numéros comme les partitions.

Bonne remarque. C'est une habitude d'un collègue que j'ai reprise. Je aivais
choisi ces noms pour avoir le moins de partitons facilement identifiables
puisque j'ai certaines sont chiffrées : ne pas faciliter les choses.


En mode "rescue", message d'erreur en faisant un "chroot" avec lv--01
montée et avec un "update-grub" suivi d'un "grub-install" :
grub-install: info:  Scanning for lvm device on distk hostdisk://dev/sda
grub-install: info:  no LVM signature found.
grub-install: info:  Scanning for DISKFILTER device on disk
hostdisk//dev/sda
grub-install: info:  Partition 0 starts from 63.
grub-install: info:  Partition 1 start from 209728575.
grub-install: info:  Partition 2 start from 734025915.
grub-install: info:  Partition 4 start from 797515776
grub-install: info:  guess root_dev `lvmid/.././' from dir
`/boot/grub/i386-pc'
grub-install: info:  setting the root device to `lvmid/.../.../'.
grub-install: info:  warning: your core.img is unusually large. It won't
fit in the embedding area.
grub-install: info:  error: embedding is not possible, but this is
required for RAID and LVM install

En clair :

Le contenu de /boot est dans un volume logique LVM, ce qui induit deux
contraintes contradictoires sur l'image core de GRUB :
1) Elle doit intégrer le module lvm lui permettant de lire le LV, ce qui
augmente sa taille.
2) Elle doit être installée dans l'espace réservé entre le MBR et la
première partition, les listes de blocs n'étant pas utilisables avec LVM.

Or cet espace est très réduit sur ton disque puisque la première
partition commence au secteur 63, ce qui laisse 62*512=31744 octets ou
31 Kio.

A noter que depuis un certain temps les programmes de partitionnement
actuels, y compris l'installateur Debian, ont déplacé à 2048 secteurs (1
Mio) le début de la première partition pour d'autres raison (alignement
avec les tailles de blocs des disques durs au format avancé et des SSD).
Le partitionnement de ce disque a donc dû être fait avec un programme de
partitionnement assez ancien, ce qui est contradictoire avec sa capacité
respectable d'au moins 2 To.

C'est ce dont je me suis apperçu, voir ma réponse envoyée hier soir,
mais seulement à Philippe MERLIN et non à toute la liste, voir ci-dessous.

L'installation date de la première version de Wheezy.


Et comme tout logiciel, GRUB a tendance à grossir au fur et à mesure des
versions. Je viens de regarder sur un disque avec LVM contenant à la
fois Wheezy et Jessie :
- sur Wheezy, /boot/grub/core.img = 28779 octets
- sur Jessie, /boot/grub/i386-pc/core.img = 31956 octets, soit
légèrement plus que l'intervalle post-MBR de ton disque.

Dans ces conditions, l'image core de GRUB ne peut plus être installée
sur ton disque.


(...)

Normal, c'est l'image core de GRUB de Wheezy qui est encore présente,
qui se lance et ne trouve plus ses fichiers dans le LV racine.

Solutions possibles :
- Créer une petite partition (5 Mo devraient suffire) formatée en ext2 à
monter sur /boot/grub, ce qui au mieux réduira suffisamment la taille de
l'image core pour qu'elle contienne dans l'espace post-MBR en évitant
l'intégration du module lvm, et au pire permettra à grub-install avec
l'option --force d'utiliser les listes de blocs.

J'ai déjà 3 partitions Windows et 1 "extended"/LVM. Si les choses n'ont
pas trop évoluées, il je ne peux plus créer de 4ème partition
primaire.

Je peux supprimer la dernière, et la basculer en ext2 ou ext3 comme partion
de boot - dev/sda3.
Est-ce que cela peut sauver la situation ?



- Convertir la table de partition au format GPT avec gdisk et créer une
petite partition (1 Mo) de type "BIOS boot" où grub-install pourra
installer l'image core. Mais si le disque contient une installation de
Windows, ce dernier ne pourra plus démarrer. Ce problème peut néanmoins
être contourné avec un MBR hybride créé au moyen de gdisk.

Je n'ai pas encore regarder GPT et gdisk en détail, mais est-ce compatible
avec les partions actuelles ou devrais-je sacrifer /dev/sda3 qui est en 
FAT32

ou pire exploser la Windows installé ?

Et si après je veux changer de version de Windows comment les choses
se passeront ?



- Si la machine a un 

Re: Neteja de SPAM

[Oscar Osta Pueyo]

Hola,
Gràcies a tots
El dia 06/03/2016 9:10 a. m., "Robert Marsellés" 
va escriure:

> Hola,
>
> On 05/03/16 21:57, Oscar Osta Pueyo wrote:
> >
> > L'equip de neteja de SPAM necessitem una mica d'ajuda, hem de tancar els
> > messos de gener i febrer 2016, falten tres revisions.
> >
>
> Fet. Ja estan totes les "estrelletes" marcades!
>
> Salut i peles,
>
> robert
>
>

Re: Neteja de SPAM

[Robert Marsellés]

Hola,

On 05/03/16 21:57, Oscar Osta Pueyo wrote:
> 
> L'equip de neteja de SPAM necessitem una mica d'ajuda, hem de tancar els
> messos de gener i febrer 2016, falten tres revisions.
> 

Fet. Ja estan totes les "estrelletes" marcades!

Salut i peles,

robert