kodi is marked for autoremoval from testing

2016-08-24 Thread Debian testing autoremoval watch 
kodi 16.1+dfsg1-2 is marked for autoremoval from testing on 2016-09-09

It is affected by these RC bugs:
818201: kodi: Jasper removal


___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Silver Sea Cruise Job Openings (Apply now)

2016-08-24 Thread Silver Sea Career 



	
	





                                                              SILVER SEA CRUISE
INTERNATIONAL

Gildo Pastor Center 7, Rue DU
Gabian MC 98000 Monaco®
silver.sea...@desilver.com 
Tel: Toll-free (877)215-9986
Skype chats: Silver.sea71 

JOB ID: SCI/EU/CC/842-25/16 

Dear Friends,  


The Silver Sea Cruise Line recruitment team is looking for new staffs to fill
the available positions at the Company headquarters in Monaco. 

Silver Sea policy is not to discriminate against any employee or
candidates for employment because of RACE, COLOR, RELIGION, SEX, NATIONAL ORIGIN, AGE, DISABILITY, MARITAL OR VETERAN STATUS.

Do you have a dream to work with the best Cruise award winner in
2015 SILVER SEA CRUISE LINE? We have more than 75 different positions available.

 Interested should forward their RESUME/CV or application letter to Mrs. Charlotte Wolfe via email on (silver.sea...@desilver.com) and you will receive our letter if your application is found in
other.
 
PLEASE NOTE THESE FOLLOWING:




 
  
  
   


EMPLOYMENT TYPE:  FULL-TIME/PART-TIME
SALARY:  EURO £45,000/ EURO £125,000 PER ANNUAL
PREFERRED LANGUAGE OF RESUME/APPLICATION:  ENGLISH
TYPE OF WORK:PERMANENT / TEMPORARY
STATUS:   ALL VACANCIES
JOB LOCATION:MONACO, FRANCE WESTERN EUROPE
CONTRACT PERIOD:   6 MONTHS, 1 YEAR, 2 YEARS AND 3 YEARS
VISA TYPE: TWO OR THREE YEARS VISA/WORK PERMIT
MINIMUM AGE:    18 YEARS & ABOVE


   
  
  
 




 
Applicants from all over the world can apply, Please spread our vacancy info to
more than 500 friends and have a chance of winning 7 Nights Cruise for your
Family members.

Silver
Sea Company will secure an AIR TICKET, VISA FEE, COMFORTABLE ACCOMMODATION & 3 SQUARE MEALS
DAILY for any
qualified candidate.


 
  
Regards,
Management/Silver Sea Cruise Line®
Email: silverrecruitm...@post.com

 









 			  


 

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: Change submitter

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

> submitter 664822 !
Bug #664822 [dpkg] dpkg: incomplete cleanup of empty directories
Bug #316521 [dpkg] dpkg: incomplete cleanup of empty directories
Bug #348133 [dpkg] dpkg: incomplete cleanup of empty directories
Bug #538429 [dpkg] dpkg: incomplete cleanup of empty directories
Bug #625241 [dpkg] dpkg: stale directories when packages install conffiles to 
subsubdirectories of /etc
Changed Bug submitter to 'David Steele ' from 'Dave Steele 
'.
> submitter 715066 !
Bug #715066 [libindicate-gtk3-dev] Broken library symlink detected in 
libindicate-gtk3-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715077 !
Bug #715077 [libdmraid-dev] Broken library symlink detected in libdmraid-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715078 !
Bug #715078 [libelk0-dev] Broken library symlink detected in libelk0-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715083 !
Bug #715083 [libgrok-dev] Broken library symlink detected in libgrok-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715085 !
Bug #715085 [libibdm-dev] Broken library symlink detected in libibdm-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715088 !
Bug #715088 [libjack-jackd2-dev] Broken library symlink detected in 
libjack-jackd2-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715091 !
Bug #715091 [libm17n-im-config-dev] Broken library symlink detected in 
libm17n-im-config-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715092 !
Bug #715092 [libmp3splt-dev] Broken library symlink detected in libmp3splt-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715099 !
Bug #715099 [libpacparser-dev] Broken library symlink detected in 
libpacparser-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715106 !
Bug #715106 [libpoco-dev] Broken library symlink detected in libpoco-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715107 !
Bug #715107 [libptscotch-dev] Broken library symlink detected in libptscotch-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715112 !
Bug #715112 [libscotchmetis-dev] Broken library symlink detected in 
libscotchmetis-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715124 !
Bug #715124 [libwaei-dev] Broken library symlink detected in libwaei-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715125 !
Bug #715125 [libwcat1-dev] Broken library symlink detected in libwcat1-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 800163 !
Bug #800163 [release.debian.org] jessie-pu: package cloudprint/0.11-5
Changed Bug submitter to 'David Steele ' from 'Dave Steele 
'.
> submitter 699059 !
Bug #699059 [piuparts.debian.org] divide dangling symlinks in meaningful 
problems and noise
Bug #615034 [piuparts.debian.org] divide dangling symlinks in meaningful 
problems and noise
Changed Bug submitter to 'David Steele ' from 'Dave Steele 
'.
> submitter 711814 !
Bug #711814 [wnpp] RFP: python-pygsear -- a Pygame Framework with Examples
Changed Bug submitter to 'David Steele ' from 'Dave Steele 
'.
> submitter 796581 !
Bug #796581 [wnpp] ITP: splitcpy -- Copy a file over the network using multiple 
streams
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715087 !
Bug #715087 [libjack-dev] Broken library symlink detected in libjack-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> submitter 715093 !
Bug #715093 [src:mpich] Broken library symlink detected in libmpich-shmem1.0-dev
Changed Bug submitter to 'David Steele ' from 'David Steele 
'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
316521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316521
348133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348133
538429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538429
615034:

Bug#820416: kodi: FTBFS in testing (Segmentation fault)

2016-08-24 Thread Santiago Vila 
On Wed, Aug 24, 2016 at 11:43:54PM +0200, Bálint Réczey wrote:

> I don't like having this bug, but if a program fails to build 50% of
> the time but runs fine it can be released IMO since users are not
> affected.

You seem to imply that our "output" as package distributors is just
the set of binary packages. That's not the case. We provide source
packages and binary packages. If a user can't build a source
package that we provide then he/she is affected as well, because
taking the source package and building it (possibly with modifications)
is also a way of "using" it.


In either case, it is not the severity definitions what we have to
consider here, but release policy.

Release policy says "packages must autobuild".

If policy said "packages must autobuild most of the time", then yes,
we could maybe have packages which only build ok most of the time.

But that's not what release policy says, and that's why FTBFS bugs are
usually reported as serious regardless of the "frequency" of the
failure.


In practice this is not as difficult to achieve as one might think,
because it often happens that it's the tests who made the build to fail.

If a test fails very often but does not mean that the package is "bad",
the logical thing to do until somebody has the time to investigate it
is to just disable it (as you have just done with kodi, thanks a lot).

Thanks.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

pd-cyclone_0.2~beta2-1_amd64.changes ACCEPTED into unstable

2016-08-24 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Aug 2016 22:01:50 +0200
Source: pd-cyclone
Binary: pd-cyclone cyclist
Architecture: source
Version: 0.2~beta2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 cyclist- Utility for converting Max/MSP binary patches to text
 pd-cyclone - Pd library of clones of Max/MSP 4.5 objects
Changes:
 pd-cyclone (0.2~beta2-1) unstable; urgency=medium
 .
   * New upstream version 0.2~beta2
 .
   [ IOhannes m zmölnig ]
   * Dropped patches applied upstream.
   * Bumped standards version to 3.9.8
 .
   [ Felipe Sateler ]
   * Dropped myself from uploaders.
Checksums-Sha1:
 5af99d3e09d00ab8383a51dfd03e20d93827863c 2228 pd-cyclone_0.2~beta2-1.dsc
 b39aa4bda356e416088a8b936dc6490444a557b7 670556 
pd-cyclone_0.2~beta2.orig.tar.gz
 934103bf33fc59e55faa12010463c08ae859dec2 7764 
pd-cyclone_0.2~beta2-1.debian.tar.xz
Checksums-Sha256:
 f21de20c0ec95e9e27f9c65d8331729718a03babaebb4d80876398c9edf4ef26 2228 
pd-cyclone_0.2~beta2-1.dsc
 9ea160cc28fdb80df0b75a818cc54cdcf42db29c69d41e948c650fae782fa791 670556 
pd-cyclone_0.2~beta2.orig.tar.gz
 5f199030580a6dcfa5bf741d5443eb0c4c0083116ae146d5bb6f4c9f24c04328 7764 
pd-cyclone_0.2~beta2-1.debian.tar.xz
Files:
 6d53736dae450a3fec40d5c4df1fe87e 2228 sound optional pd-cyclone_0.2~beta2-1.dsc
 238fa3309e64ddb21dafb8028fc7db35 670556 sound optional 
pd-cyclone_0.2~beta2.orig.tar.gz
 7ada3ffe0cd3abd618f1a38ad32df88f 7764 sound optional 
pd-cyclone_0.2~beta2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXvf5TAAoJELZQGcR/ejb4ooMP/0F5o9f8pZzptuGxRu4fOtNl
ljS6w7/7kTIiJN1xFgj+BnrwywaaDgGjDKliGD88oXC+ovllcLMl5DlcVeLTV4n7
Nkxn29YbYcQi/Q3IOSHgsxx1+eE+OeFIYcXiBzlro/6pGIXPhP5+S7uDeV4be6on
VCeKntHsKlWIAE/ZgW/exE8mOPrsW0XHt5WlVBcsvGMxXoJ3eXSFiQpD1jgJXcvq
kdP0l43gA/oo3j8eOXprWqYlURB20hYTSS3e7dGLbrfQ3X7kyCQsAw0gpy80z9JX
tgNQ3vvN2BFA3uhHUL4VRkGgd2KrtUo+hr7I83bp9qJf5xNbDV1i+p1kYGEUJ21j
G76KUwHhE7myPN3aJgwdABdJ6E9d5T6g6r0k9sGYuHtob3WUbIWdsiHznaGAodrG
cChHAI0NGJLNvWGR7nmYDM0dx/SwZ9ivV4WbPLnq0m3oA/VCLRE29Ch/jNHJ3w1G
sy3IY1ejluZfUudLI8shdVI+l03o74qwlvjYamKKpbkfL3iL7qtvObpHdsGervr/
ba647zW5TcJceFDiod3/G0p8wGR5J5ZRJnq0Zgr0WHaptbQ3KFld/h03ZMWkJWay
sratRXvByXekrBC0JdTRAC7f18Urq6kVRpr0VZsFXJnGQBmrvccrHDQsB1Nt7eu7
KBoR1Hzz5RSluIXPzNLD
=InKT
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#820416: kodi: FTBFS in testing (Segmentation fault)

2016-08-24 Thread Bálint Réczey 
Hi Santiago,

2016-08-24 17:36 GMT+02:00 Santiago Vila :
> Hi.
>
> Any progress on this? This is still reproducible. I'm attaching a
> build log for the version which has just entered testing.

I have uploaded a new version to experimental with two related changes.

One is not failing the build when the test fails. This is not nice,
but the tests
were completely broken while kodi ran fine on my test system.

The second is running the tests with Valgrind when it is installed to have
better chance at finding allocation errors. I also proposed the change at
upstream listing an error which could mess up mutex handling:
https://github.com/xbmc/xbmc/pull/10334

>
> On Sun, 17 Apr 2016, Balint Reczey wrote:
>
>> It suggests there is something wrong with the mutex handling and TSAN seems 
>> to confirm that:
>> [...]
>> I need to test if the problem still exists in upstream master and verify if
>> it is not a false positive TSAN warning and the root cause is indeed here.
>
> Could you translate that into a language that a non-programmer
> could understand?
>
>> I'm setting the bug's severity to normal because while it is reproducible
>> the FTBFS does not happen on Debian's buildds [...]
>
> Hmm. I'm not going to enter into a severity war, but you should be
> aware that the theory that a FTBFS is not RC because "it does not
> happen" in Debian's buildds has many flaws.
>
> For example, for a package which FTBFS randomly, it is completely
> useless, as a successful build just means that we were lucky that
> time.

I'm trying to apply definitions from here:
https://www.debian.org/Bugs/Developer#severities

I don't like having this bug, but if a program fails to build 50% of
the time but runs fine it can be released IMO since users are not
affected.

>
> We should better not care too much about what happened in the
> autobuilders the last time it was tried, we should care more about
> what could happen the next time.
>
> I'm using sbuild and the autobuilders are using sbuild as well
> (or a variant of it).
>
> If you think this may not happen in official autobuilders, could you
> please explain why?

I don't think that it may not happen, but I say that it did not seem to
happen so far which makes me think it won't happen often and when
it happens autobuilders will try again anyway.

I understand that having this issue is painful for people like you doing the
hard work of rebuilding many packages and I'm trying to help.

Starting with 17.x the tests won't make the build fail until they run
reliably thus
you'll be able to rebuild kodi. Valgrind will also help upstream in catching
bugs earlier.

>
> (Because my machine does not have enough memory? How would I know that
> in advance when we don't have a Build-Memory control field?)
>
>> thus does not prevent rebuilding the package when needed.
>
> It does prevent me from rebuilding the package, which makes the
> software non-free for me and apparently anybody who does not have a
> machine with 32 GB of RAM (which is still a lot of people).

I guess you can build it with "DEB_BUILD_OPTIONS=nocheck", thus
this seems to be a bit of exaggeration.

>
> I would say that would deserve important severity at least.

I think the bug does not fit "important"'s definition [1] but feel free
to raise it.
I agree with you on this bug being valid and needs to be fixed
no matter what the severity is.

Cheers,
Balint

>
> (I said 32 GB just as an example, but if that's a more or less
> accurate summary of this bug, I'd like to know the exact figure).
>
> Thanks.


[1] "important: a bug which has a major effect on the usability of a
package, without rendering it completely unusable to everyone."

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: .

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

> tags 820416 confirmed upstream
Bug #820416 [src:kodi] kodi: FTBFS in testing (Segmentation fault)
Ignoring request to alter tags of bug #820416 to the same tags previously set
> forwarded 820416 https://github.com/xbmc/xbmc/pull/10334
Bug #820416 [src:kodi] kodi: FTBFS in testing (Segmentation fault)
Set Bug forwarded-to-address to 'https://github.com/xbmc/xbmc/pull/10334'.
> thanks
Stopping processing here.

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

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#831591: ffmpeg: kodi crash

2016-08-24 Thread Carl Eugen Hoyos 
Hi!

First, please understand that so far, no ABI breakage between 
FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of 
non-public api (that we decided to work-around for 3.1.1).

Am I correct that no backtrace was provided for this issue?
But even with a backtrace, I fear a bisect may be necessary.

Sorry, Carl Eugen 

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processing of pd-cyclone_0.2~beta2-1_amd64.changes

2016-08-24 Thread Debian FTP Masters 
pd-cyclone_0.2~beta2-1_amd64.changes uploaded successfully to localhost
along with the files:
  pd-cyclone_0.2~beta2-1.dsc
  pd-cyclone_0.2~beta2.orig.tar.gz
  pd-cyclone_0.2~beta2-1.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

kodi 16.1+dfsg1-2 MIGRATED to testing

2016-08-24 Thread Debian testing watch 
FYI: The status of the kodi source package
in Debian's testing distribution has changed.

  Previous version: 16.1+dfsg1-1
  Current version:  16.1+dfsg1-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#820416: kodi: FTBFS in testing (Segmentation fault)

2016-08-24 Thread Santiago Vila 
Hi.

Any progress on this? This is still reproducible. I'm attaching a
build log for the version which has just entered testing.

On Sun, 17 Apr 2016, Balint Reczey wrote:

> It suggests there is something wrong with the mutex handling and TSAN seems 
> to confirm that:
> [...]
> I need to test if the problem still exists in upstream master and verify if
> it is not a false positive TSAN warning and the root cause is indeed here.

Could you translate that into a language that a non-programmer
could understand?

> I'm setting the bug's severity to normal because while it is reproducible
> the FTBFS does not happen on Debian's buildds [...]

Hmm. I'm not going to enter into a severity war, but you should be
aware that the theory that a FTBFS is not RC because "it does not
happen" in Debian's buildds has many flaws.

For example, for a package which FTBFS randomly, it is completely
useless, as a successful build just means that we were lucky that
time.

We should better not care too much about what happened in the
autobuilders the last time it was tried, we should care more about
what could happen the next time.

I'm using sbuild and the autobuilders are using sbuild as well
(or a variant of it).

If you think this may not happen in official autobuilders, could you
please explain why?

(Because my machine does not have enough memory? How would I know that
in advance when we don't have a Build-Memory control field?)

> thus does not prevent rebuilding the package when needed.

It does prevent me from rebuilding the package, which makes the
software non-free for me and apparently anybody who does not have a
machine with 32 GB of RAM (which is still a lot of people).

I would say that would deserve important severity at least.

(I said 32 GB just as an example, but if that's a more or less
accurate summary of this bug, I'd like to know the exact figure).

Thanks.

kodi_16.1+dfsg1-2_amd64-20160824T064358Z.gz
Description: application/gzip
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#834180: Fix for the bristol FTBFS

2016-08-24 Thread Adrian Bunk 
tags 834180 +patch
thanks

A fix for the bristol FTBFS is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Description: Stop using alsa/iatomic.h
 Technically this is an API breakage in libasound 1.1.2,
 but it makes sense to me that this header was removed
 by ALSA upstream.
 .
 bristol was the only user in Debian, and even here the
 code that once used it was already commented out.
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/834180
Forwarded: no

--- bristol-0.60.11.orig/libbristolaudio/audioEngineJack.c
+++ bristol-0.60.11/libbristolaudio/audioEngineJack.c
@@ -39,7 +39,7 @@
 
 #ifdef _BRISTOL_JACK
 #if (BRISTOL_HAS_ALSA == 1)
-#include 
+//#include 
 #endif
 
 /*
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: Fix for the bristol FTBFS

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

> tags 834180 +patch
Bug #834180 [src:bristol] bristol: FTBFS: audioEngineJack.c:42:26: fatal error: 
alsa/iatomic.h: No such file or directory
Added tag(s) patch.
> thanks
Stopping processing here.

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

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers