Haal de warmte in de badkamer met de nieuwe radiatoren van Sanifun! | Un bon radiateur qui réchauffe l'ensemble de la pièce est indispensable

2016-01-25 Thread OnlineSanitair

Deze email nieuwsbrief werd in grafisch HTML formaat verzonden.
Als u deze tekstversie ziet, verkiest uw email programma "gewone tekst" emails.
U kan de originele nieuwsbrief online bekijken:
http://lauca.ens-mail7.net/zfAM5B



Défiler vers le bas pour voir la version Française - Scroll naar
beneden voor de Franse versie

Buiten blijven de temperaturen dalen, waardoor de verwarming in huis
vaak een paar graden warmer wordt gezet. Een goede radiator die de
gehele ruimte goed verwarmd is onmisbaar. Niet alleen in de woonkamer,
maar onder andere ook in de badkamer! Bij Sanifun zijn onlangs
verschillende nieuwe radiatoren in allerlei formaten toegevoegd aan
het assortiment. Hierboven zijn een aantal voorbeelden te vinden van
de nieuwe handdoekradiator Medina flat en design radiator Boston. Kies
bijvoorbeeld voor de handdoekradiator (
https://www.online-sanitair.com/verwarming/badkamer-radiatoren/medina-flat-wit
) die de badkamer verwarmd en tegelijkertijd ruimte biedt om uw
handdoeken op te hangen. Een design radiator (
https://www.online-sanitair.com/verwarming/design-radiator/boston-wit
) is een andere goede optie, die niet alleen de badkamer maar ook
andere delen van de woning kan verwarmen.

Bezoek nu de website van Sanifun! ( https://www.online-sanitair.com )

De elegantie van een waskom in de badkamer

Bij de meeste badkamermeubels is de wastafel voornamelijk opgenomen in
de badkamerkast, waardoor deze bijna niet opvallen. Een waskom wordt
juist vaak op het badkamermeubel geplaatst, waardoor deze goed
zichtbaar is in de badkamer. Een wastafel in de vorm van een waskom
zorgt voor de nodige elegantie in de badkamer. Deze waskommen zijn
onder andere verkrijgbaar in verschillende soorten natuursteen, wat
zorgt voor een extra luxe accent in uw badkamer.

Winnaar van de Sanifun Facebookactie

Op oudjaarsdag hebben wij de winnaar bekend gemaakt van onze
Facebookactie, waarbij de sauna Pantaleone ter waarde van €2995,-
verloot werd.

Marilie was de gelukkige winnaar! Wij wensen u veel plezier van de
comfortabele sauna en complete douchecabine.

Hou de Facebookpagina van Sanifun (
https://www.facebook.com/OnlineSanitair/?ref=bookmarks ) in de gaten
voor nog meer leuke winacties!

Lorsque les températures extérieures ne cessent de chuter, nous
augmentons souvent le chauffage de quelques degrés. Un bon radiateur
qui réchauffe l'ensemble de la pièce est indispensable. Dans le
salon, mais également dans la salle de bains, entre autres! Sanifun a
récemment ajouté à sa gamme différents nouveaux radiateurs dans
divers types de formats. Vous trouverez ci-dessus un certain nombre
d'exemples du nouveau radiateur sèche-serviettes Medina flat et du
radiateur design Boston. Vous pouvez par example opter pour le
radiateur sèche-serviettes (
https://www.online-sanitair.fr/chauffage/radiateur-salle-de-bain ) qui
réchauffe la salle de bains et vous permet également de suspendre
vos serviettes. Un radiateur design (
https://www.online-sanitair.fr/chauffage/radiateur-design )est
également une bonne option: il peut réchauffer la salle de bains
mais également d'autres pièces du logement.

Jetez dès maintenant un coup d'œil au site Web de Sanifun (
https://www.online-sanitair.fr )

L'élégance d'une vasque dans la salle de bains

Le lavabo est généralement intégré au meuble de salle de bains, on
ne le remarque donc quasiment pas. Les vasques sont souvent placées
sur le meuble de salle de bains et restent ainsi bien visibles. Un
lavabo en forme de vasque apporte la touche d'élégance requise à
votre salle de bains. Ces vasques sont notamment disponibles dans
différents types de pierre naturelle, ce qui apporte une touche de
luxe supplémentaire à la salle de bains.

Gagnant de l'offre Sanifun sur Facebook

À la Saint-Sylvestre, nous avons annoncé le nom du gagnant de notre
offre sur Facebook, qui remporte le sauna Pantaleone d'une valeur de 2
995 euros.

Marilie est l'heureuse gagnante! Nous vous souhaitons de bien profiter
de ce confortable sauna équipé d'une cabine de douche complète.

Gardez un œil sur la page Facebook de Sanifun (
https://www.facebook.com/OnlineSanitair/?ref=bookmarks ), nous
organiserons d'autres chouettes concours!

Online Sanitair BVBA
Kalmhoutsesteenweg 197 Bus 3 | 2990 Wuustwezel
Tel: België   +32 (0)3.294.57.83

Nederland:  +31 (0)85.027.00.00E-mail: i...@online-sanitair.com
www.online-sanitair.com | www.online-sanitairkopen.nl

_
Uitschrijven / Abonnement wijzigen: 
http://lauca.ens-mail7.net/ughbwhqwgsgujqbqbgjbhggesqhs



Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

2016-01-25 Thread Michal Suchanek
On 25 January 2016 at 03:05, adrian15  wrote:
> El 24/01/16 a las 16:51, Michal Suchanek escribió:

> What you are describing here is what it's actually implemented in my patch
> (Well, actually the first patch version because the current one enforces
> bootloader roles).

Actually, no.

Nowhere in the description is any bootloader designated primary or
secondary or first or second. On purpose.

> So what about primary and secondary terms? Or first or
> second terms?

Both are broken and confusing.

>
> These terms are used in two places:
> * Internal variables and functions to handle bootloaders
> * Information shown to the final user
>
> I'm most convinced to use the first and non-first notation. So that the old
> code that referred to LB_BOOTLOADER can just refer to: LB_FIRST_BOOTLOADER.

For what piece of code we have does it make sense to reference
LB_FIRST_BOOTLOADER when not also referencing LB_SECOND_BOOTLOADER?
Will that be extended to LB_THIRD_BOOTLOADER once x86 grows support
for coreboot or l-b grows support for some other platform with many
firmware variants?

If you set bootloaders like

LB_BOOTLOADERS="syslinux grub-efi"

then you can just do

for bootloader in $LB_BOOTLOADERS ; do some $bootloader foo

after you check that you have at most two bootloaders and if you have
more than one then only the latter one ends with -efi.

Thanks

Michal



Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

2016-01-25 Thread adrian15



El 25/01/16 a las 16:12, Michal Suchanek escribió:

On 25 January 2016 at 03:05, adrian15  wrote:

El 24/01/16 a las 16:51, Michal Suchanek escribió:



What you are describing here is what it's actually implemented in my patch
(Well, actually the first patch version because the current one enforces
bootloader roles).


Actually, no.

Nowhere in the description is any bootloader designated primary or
secondary or first or second. On purpose.
Neither it is on my patch (initial implementation). Yes, the term 
PRIMARY_BOOTLOADER is used there for reusing old code. But using:


--bootloaders=syslinux,grub-efi

did not enforce syslinux to be in the first place or grub-efi to be in 
the second place.


That's the specific part I meant.




So what about primary and secondary terms? Or first or
second terms?


Both are broken and confusing.

Ok...


These terms are used in two places:
* Internal variables and functions to handle bootloaders
* Information shown to the final user

I'm most convinced to use the first and non-first notation. So that the old
code that referred to LB_BOOTLOADER can just refer to: LB_FIRST_BOOTLOADER.


For what piece of code we have does it make sense to reference
LB_FIRST_BOOTLOADER when not also referencing LB_SECOND_BOOTLOADER?
Will that be extended to LB_THIRD_BOOTLOADER once x86 grows support
for coreboot or l-b grows support for some other platform with many
firmware variants?

If you set bootloaders like

LB_BOOTLOADERS="syslinux grub-efi"

then you can just do

for bootloader in $LB_BOOTLOADERS ; do some $bootloader foo

Mostly what current path does but with commas instead.


after you check that you have at most two bootloaders and if you have
more than one then only the latter one ends with -efi.


This is not a good approach. You are requesting the bootloaders to end 
in "-efi". The current approach is to name them based on the Debian 
package name. These packages do not need to end in "-efi".


My use case is the following one. The final user requests:

--bootloaders=grub-efi,syslinux

so I show him:

"Warning. You are using: syslinux as a non first bootloader. This might 
work but it is not advised."


How do I know that I have to output this message?

Because I compare the internal variable:

LB_FIRST_BOOTLOADER="grub-efi"

with the bootloader name "syslinux" and I see they are not the same one.

So, as you see I need to use:

"non first bootloader" term
and
LB_FIRST_BOOTLOADER variable.

So...

1) I don't mind renaming "non first bootloader" or LB_FIRST_BOOTLOADER 
to another terminology which makes more technical sense.
2) I prefer this approach over yours (Michal) because it's the own 
bootloader which decides if it is more suited for "first bootloader" or 
not. Let's not repeat the current binary_iso design which has many 
references to the different available binary_bootloaders available.




Thanks

Michal


adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/




Processed: Bug#810861 marked as pending

2016-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 810861 pending
Bug #810861 [snd-gtk-pulse] snd-gtk-pulse: Cannot locate libgsl.so.0
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
810861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#810861: marked as done (snd-gtk-pulse: Cannot locate libgsl.so.0)

2016-01-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Jan 2016 22:08:32 +
with message-id 
and subject line Bug#810861: fixed in snd 16.1-1
has caused the Debian Bug report #810861,
regarding snd-gtk-pulse: Cannot locate libgsl.so.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
810861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snd-gtk-pulse
Version: 11.7-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Refuses to start, with the following error:
snd: error while loading shared libraries: libgsl.so.0: cannot open shared 
object file: No such file or directory


*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages snd-gtk-pulse depends on:
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-6
ii  libcairo21.14.4-1
ii  libfftw3-double3 3.3.4-2
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6.1-0.1
ii  libgdk-pixbuf2.0-0   2.32.3-1
ii  libglib2.0-0 2.46.2-3
ii  libgmp10 2:6.1.0+dfsg-2
ii  libgsl2  2.1+dfsg-2
ii  libgtk2.0-0  2.24.29-1
ii  libmpc3  1.0.3-1
ii  libmpfr4 3.1.3-2
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpangoft2-1.0-01.38.1-1
ii  libpulse07.1-2
ii  snd  11.7-5

snd-gtk-pulse recommends no packages.

snd-gtk-pulse suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: snd
Source-Version: 16.1-1

We believe that the bug you reported is fixed in the latest version of
snd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 810...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated snd 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Jan 2016 22:25:00 +0100
Source: snd
Binary: snd snd-doc snd-gtk-jack snd-gtk-pulse snd-nox
Architecture: source
Version: 16.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 snd- Sound file editor
 snd-doc- Sound file editor (documentation)
 snd-gtk-jack - Sound file editor (GTK+ user interface - JACK)
 snd-gtk-pulse - Sound file editor (GTK+ user interface - PulseAudio)
 snd-nox- Sound file editor (without X support)
Closes: 673203 810861
Changes:
 snd (16.1-1) unstable; urgency=medium
 .
   * Imported Upstream version 16.1
 .
   [ Reinhard Tartler ]
   * Easy building with source format 3.0
 .
   [ IOhannes m zmölnig ]
   * Adopting the package (Closes: #673203)
   * Rebuild (Closes: #810861)
   * Refreshed debian/patches
 * Patch to fix typos
   * Don't delete sndlib.h
   * Switched build-system to CDBS
 * Enable CDBS license-check
 * B-D on cdbs
   * Explicitely pass libs for building with pulse-simple
   * Upstream has removed tutorial
   * Made 'snd' Recommend one of the frontends
 * Prevent frontends from being installed in parallel
   * Updated debian/copyright to copyright-format/1.0
 * Resolved non-dfsg issue of 'dlocsig.scm'
   * Moved all shared data to 'snd' package
   * lintian-override of false-positives for typos
   * Bumped standards-version to 3.9.6
Checksums-Sha1:
 d53ae083719492145a43492038f2d1eab056f35b 2320 snd_16.1-1.dsc
 646e8ab35999c394772a8c5bb976321d46d42f4a 14745996 snd_16.1.orig.tar.gz
 3fec86cae64ab1700c345833b5f19c5f

Bug#812709: cvs-switchroot requires /bin/mksh but it is not installed

2016-01-25 Thread James Youngman
Package: cvs
Version: 2:1.12.13+real-15
Severity: normal

The cvs-switchroot program is a script but its interpeter is not
installed.  I assume that a dependency which should exist is simply
missing.


~$  cvs-switchroot 
bash: /usr/bin/cvs-switchroot: /bin/mksh: bad interpreter: No such file or 
directory
~$ type  cvs-switchroot 
cvs-switchroot is hashed (/usr/bin/cvs-switchroot)
~$ head -n 1 /usr/bin/cvs-switchroot
#!/bin/mksh
~$ ls -l /bin/mksh
/bin/ls: cannot access /bin/mksh: No such file or directory


-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cvs depends on:
ii  adduser   3.113+nmu3
ii  dpkg  1.17.26
ii  install-info  5.2.0.dfsg.1-6
ii  libbsd0   0.7.0-2
ii  libc6 2.19-18+deb8u1
ii  libgssapi-krb5-2  1.12.1+dfsg-19+deb8u1
ii  libkrb5-3 1.12.1+dfsg-19+deb8u1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages cvs recommends:
ii  openssh-client  1:6.7p1-5

Versions of packages cvs suggests:
pn  mksh  
ii  rcs   5.9.3-1

-- no debconf information