Bekijk hier de nieuwste gadgets

2018-01-16 Thread Ester | HiepHiepKado.be

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://ymlpsend4.com/zGiNK7



Weet u al hoe u in 2018 de aandacht trekt met uw organisatie?  Bekijk
de nieuwsbrief in de browser ( http://ymlpsend4.com/zGiNK7 )

Weet u al hoe u in 2018 de aandacht trekt met uw organisatie? Het
nieuwe jaar biedt weer volop leuke gadgets en give aways ter promotie
van uw merk. De trends voor 2018? Fun, functionaliteit en veiligheid.
Ludieke gadgets met een hoge entertainment waarde, maar ook items die
zeer functioneel zijn en bijvoorbeeld de verkeersveiligheid
bevorderen, een belangrijk topic ook in het nieuwe jaar. Of u nu gaat
voor een kleine giveaway of een luxe geschenk, één ding is zeker:
met onze promo items trekt u zeker de aandacht. Bekijk hier (
https://www.hiephiepkado.be/themas/promo-items-2018/?source=mailing16012018
) onze nieuwste items.

 

HiepHiepKado · Maastrichterstraat 71 · 3500 Hasselt · België

Contact opnemen ( https://www.hiephiepkado.be/contact.php )

 

_
Uitschrijven / Gegevens wijzigen: 
http://ymlpsend4.com/ughymwuwgsgjbmjegebyggusqqb
Powered door YourMailingListProvider



Bug#887427: stretch-pu: package buildbot/0.8.12-3.2

2018-01-16 Thread Alexander GQ Gerasiov
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hello there,

In Stretch we have buildbot package version 0.8.12-3.2 (abandoned by 
maintainer).
Unfortunately it's unusable, because of hardcoded versioned dependence on
sqlalchemy with version lesser than one in stretch.

Piotr Ozarowski  tried to fix this, removing dependence from control,
but this is not enough (package builds, installs but not work at all), see 
#867588

This could be easy fixed by removing versioned runtime dependencies:

diff --git a/setup.py b/setup.py
index e70ab16..2f9f716 100755
--- a/setup.py
+++ b/setup.py
@@ -381,11 +381,8 @@ else:
 ]
 
 setup_args['install_requires'] += [
-# sqlalchemy-0.8 betas show issues with sqlalchemy-0.7.2, so stick to 
0.7.10
-'sqlalchemy >= 0.6, <= 0.7.10',
-# buildbot depends on sqlalchemy internals, and this is the tested
-# version.
-'sqlalchemy-migrate==0.7.2',
+'sqlalchemy >= 0.6',
+'sqlalchemy-migrate>=0.7.2',
 'python-dateutil>=1.5',
 ]
 setup_args['tests_require'] = [

After that package could be installed and used in Debian Stretch release. (At 
least
autotests pass and buildbot works as expected.)

Waiting for approve to do NMU to stretch-proposed-updates.



-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (670, 'stable-updates'), (670, 'stable'), (630, 'testing'), (600, 
'unstable'), (550, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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



Bug#887233: libploop-dev should depend on e2fsprogs explicitly

2018-01-16 Thread Andreas Henriksson
Control: tags -1 + wontfix

On Sun, Jan 14, 2018 at 08:07:05PM +0100, Helmut Grohne wrote:
[...]
> /usr/lib/x86_64-linux-gnu/libploop.a contains dumpe2fs, e2fsck, e4defrag, 
> filefrag, fsck.ext4, resize2fs and tune2fs. According to file it is a current 
> ar archive
[...]

I've investigated libploop which indeed has code to run commands from
e2fsprogs. For the case of dynamic linking dependencies should be
added, see #887298. This particular bug report is about the *static*
library shipped in the -dev package though, and I don't think any
changes should be done here for the following reason:

* e2fsprogs is not needed at *build*-time (only runtime).
* e2fsprogs will be needed by the application that (statically)
  links to libploop.a (at runtime), and there's no way for the
  libploop-dev to 'transfer' the correct dependencies.
* There's no reason to expect the libploop-dev package be
  installed on users systems running the applications that
  have statically linked to libploop.a

(Please also note that Debian normally avoids using static linking so
this would mainly affect third party applications not shipped in
debian.)

I'm thus tagging this bug report wontfix.

(And alternative approach might be to stop shipping libploop.a at all.)

Regards,
Andreas Henriksson



Processed: Re: libploop-dev should depend on e2fsprogs explicitly

2018-01-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + wontfix
Bug #887233 [libploop-dev] libploop-dev should depend on e2fsprogs explicitly
Added tag(s) wontfix.

-- 
887233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems