kodi-pvr-njoy is marked for autoremoval from testing

[Debian testing autoremoval watch]

kodi-pvr-njoy 1.11.9+git20160210-1 is marked for autoremoval from testing on 
2016-12-18

It is affected by these RC bugs:
844969: kodi-pvr-njoy: FTBFS: dh_auto_configure: cmake .. 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1 
-DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu/kodi -DUSE_LTO=1 returned exit 
code 1


___
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: Bug#843144 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 843144 pending
Bug #843144 [ffmpeg] recoded videos are too short
Ignoring request to alter tags of bug #843144 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
843144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843144
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

Re: hydrogen packaging

[Jaromír Mikeš]

2016-11-27 1:33 GMT+01:00 James Cowgill :
> On 26/11/16 13:39, Jaromír Mikeš wrote:
>> 2016-11-26 13:44 GMT+01:00 James Cowgill :
>>> On 26/11/16 02:02, Jaromír Mikeš wrote:
 2016-11-26 0:15 GMT+01:00 James Cowgill :
> On 25/11/16 17:15, Jaromír Mikeš wrote:
>> 2016-11-25 17:13 GMT+01:00 James Cowgill :
>>> -- d/hydrogen.install
 usr/share/hydrogen/data/img
>>> It seems that the only reason for putting this in hydrogen instead of
>>> hydrogen-data is the SVG icon?
>>
>> Yes
>
> I don't think you should ship the entire data/img directory in the
> hydrogen package just for this. Either only install that one svg and
> move everything over to the -data package, or duplicate the svg since
> it's only 9kB.

 Ok ... I thought that icon make sense to be installed in binary package
 but as hydrogen package can't be installed without hydrogen-data package
 all img dir is now moved to -data package.
>>>
>>> I agree that putting the icon in the main package does make sense - it
>>> just seemed like a lot of other stuff could have gone in the data
>>> package. One thing is that appstream (ie GNOME software center) requires
>>> the icon to be in the main package so hydrogen won't show up at the moment.
>>
>> Done ;)
>
> What you've done won't work - you've installed the same file into two
> separate packages which have to be installed together.

Now h2-icon.svg file excluded from hydrogen-data package and installed
only in hydrogen package.

mira

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

Re: libgig 4.0.0 qsampler 4.2.0 gigedit 1.0.0

[Jaromír Mikeš]

2016-11-26 16:17 GMT+01:00 Jaromír Mikeš :
> 2016-11-26 13:33 GMT+01:00 James Cowgill :
>> On 26/11/16 01:44, Jaromír Mikeš wrote:
>>> 2016-11-25 17:36 GMT+01:00 James Cowgill :
>
 All headers in /usr/include/libgig, all references loose the 'libgig/'
 and -I/usr/include/libgig is added to the pkg-config file.
>
> Option 3 has been selected by upstream ...

Option 3 is selected by upstream and I have tuned our packaging accordingly.
qsampler 0.4.2 and gigedit 1.0.0 now build fine with libgig 4.0.0

best regards

mira

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

Re: hydrogen packaging

[James Cowgill]

On 26/11/16 13:39, Jaromír Mikeš wrote:
> 2016-11-26 13:44 GMT+01:00 James Cowgill :
>> On 26/11/16 02:02, Jaromír Mikeš wrote:
>>> 2016-11-26 0:15 GMT+01:00 James Cowgill :
 On 25/11/16 17:15, Jaromír Mikeš wrote:
> 2016-11-25 17:13 GMT+01:00 James Cowgill :
>> -- d/hydrogen.install
>>> usr/share/hydrogen/data/img
>> It seems that the only reason for putting this in hydrogen instead of
>> hydrogen-data is the SVG icon?
>
> Yes

 I don't think you should ship the entire data/img directory in the
 hydrogen package just for this. Either only install that one svg and
 move everything over to the -data package, or duplicate the svg since
 it's only 9kB.
>>>
>>> Ok ... I thought that icon make sense to be installed in binary package
>>> but as hydrogen package can't be installed without hydrogen-data package
>>> all img dir is now moved to -data package.
>>
>> I agree that putting the icon in the main package does make sense - it
>> just seemed like a lot of other stuff could have gone in the data
>> package. One thing is that appstream (ie GNOME software center) requires
>> the icon to be in the main package so hydrogen won't show up at the moment.
> 
> Done ;)

What you've done won't work - you've installed the same file into two
separate packages which have to be installed together.

James



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

Re: mixxx1.8 but tittle says its 2.0 !!!

[James Cowgill]

Hi,

On 26/11/16 20:31, James Cowgill wrote:
> Hi,
> 
> Again, please CC the multimedia team on everything.
> 
> On 26/11/16 14:58, snipe wrote:
>> Like i told it says 2.0 in the terminal ,
>>
>> now take a look inside 2nd ss
> 
> In the previous emails, I was expecting you to run the commands _after_
> installing mixxx 2.0 from jessie-backports. If you'd have done that the
> bug would have become obvious. Note that for the future: jessie and
> jessie-backports are not the same thing.
> 
> I've managed to reproduce the bug - mixxx from jessie-backports claims
> to be version '1.8' although it clearly is 2.0 (has the same SVN
> revision as mixxx in unstable).

So on closer inspection, it seems that soundtouch 1.8.0 from jessie
leaks a #define VERSION (and some other things it should not be
defining) which conflicts with mixxx's VERSION #define.

Probably the simplest fix is to #undef VERSION at the top of
src/defs_version.h in the backported package.

James



signature.asc
Description: OpenPGP digital signature
___
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: Re: Bug#845859: kodi: switch to build depend on the metapackage default-libmysqlclient-dev

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 17.0~beta3+dfsg1-1
Bug #845859 [kodi] kodi: switch to build depend on the metapackage 
default-libmysqlclient-dev
Marked as fixed in versions kodi/17.0~beta3+dfsg1-1.

-- 
845859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845859
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#845859: kodi: switch to build depend on the metapackage default-libmysqlclient-dev

[Bálint Réczey]

Control: fixed -1 17.0~beta3+dfsg1-1

Hi Otto,

2016-11-26 23:08 GMT+01:00  :
> Package: kodi
> Severity: important
>
> Hi!
>
> This package build depends on libmysqlclient-dev. It should instead
> build-depend on default-libmysqlclient-dev metapackage, and end up
> having the run-time dependency of the libmysqlclient implementation
> Debian has chosen to use, currently MariaDB instead of Oracle MySQL.
>
> Announcement of new default-mysql-* metapackages:
> https://lists.debian.org/debian-devel-announce/2016/09/msg0.html
>
> Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server
>
> MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html
>
> Please update the depencies accordingly. In most cases the required
> change is:
>
> * BEFORE: Build-Depends: libmysqlclient-dev
>
> * AFTER: Build-Depends: default-libmysqlclient-dev

This looks fixed for some time.

Cheers,
Balint

___
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#845859: marked as done (kodi: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Sun, 27 Nov 2016 00:38:55 +0100
with message-id 

Hello

[Mrs. Rosemary]

We offer Business Loans Personal from $ 15,000 to  $ 1,500,000 @ 2% contact us 
now.

___
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#845874: mediatomb: switch to build depend on the metapackage default-libmysqlclient-dev

[otto]

Package: mediatomb
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 

___
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#845859: kodi: switch to build depend on the metapackage default-libmysqlclient-dev

[otto]

Package: kodi
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 

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

Re: mixxx1.8 but tittle says its 2.0 !!!

[James Cowgill]

Hi,

Again, please CC the multimedia team on everything.

On 26/11/16 14:58, snipe wrote:
> Like i told it says 2.0 in the terminal ,
> 
> now take a look inside 2nd ss

In the previous emails, I was expecting you to run the commands _after_
installing mixxx 2.0 from jessie-backports. If you'd have done that the
bug would have become obvious. Note that for the future: jessie and
jessie-backports are not the same thing.

I've managed to reproduce the bug - mixxx from jessie-backports claims
to be version '1.8' although it clearly is 2.0 (has the same SVN
revision as mixxx in unstable).

And thanks for pointing out the bug,
James



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

qsampler 0.4.2-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the qsampler source package
in Debian's testing distribution has changed.

  Previous version: 0.4.2-1
  Current version:  0.4.2-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

qxgedit 0.4.2-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the qxgedit source package
in Debian's testing distribution has changed.

  Previous version: 0.4.2-1
  Current version:  0.4.2-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

qmidinet 0.4.2-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the qmidinet source package
in Debian's testing distribution has changed.

  Previous version: 0.4.2-1
  Current version:  0.4.2-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

qsynth 0.4.3-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the qsynth source package
in Debian's testing distribution has changed.

  Previous version: 0.4.3-1
  Current version:  0.4.3-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

lakai 0.1-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the lakai source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  0.1-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

Re: libgig 4.0.0 qsampler 4.2.0 gigedit 1.0.0

[Jaromír Mikeš]

2016-11-26 13:33 GMT+01:00 James Cowgill :
> On 26/11/16 01:44, Jaromír Mikeš wrote:
>> 2016-11-25 17:36 GMT+01:00 James Cowgill :

>>> All headers in /usr/include/libgig, all references loose the 'libgig/'
>>> and -I/usr/include/libgig is added to the pkg-config file.

Option 3 has been selected by upstream ...

>> What would be best from debian point of view?
>>
>> /usr/include/libgig4/gig.h or /usr/include/libgig7/gig.h
>>
>> to reflect rather soname than release?
>
> Usually the header location does not change with the soname / ABI. Most
> libraries that do change the header path frequently do it because the
> API changes a lot (eg LLVM).
>
>> Or just /usr/include/gig.h and not allow two versions installed together?
>>
>> your opinion James?
>
> I think one of the 3 options I gave should be used, but I don't mind
> which one. Given that programs seem to be using headers without the
> 'libgig/' prefix already, the middle options seems the least desirable
> but if upstream wants to update all the headers for that option then it can.
>
> As to installing -dev packages together - upstream would also have to
> rename the libgig.so symlink as well as installing headers in a
> different place. I'm not sure it's worth it.

Quoting upstream answer
--
However my original suggestion for changing /usr/include/libgig to
/usr/include/libgig4 might still make sense. Since all applications linking
against libgig are calling pkg-config, they would still compile to that new
headers location without any changes to those app's source code or configure
scripts. Do your Debian friends over there have any profound reasons against
this naming scheme (with the lib's major number included)?

But just to make this clear: libgig is also one of the libraries which was and
will change its API frequently becoming incompatible with previous versions.
That's mainly because we decided that preserving backward compatibility for a
long time would mean to much work overhead for us, with probably no relevant
advantage for users in practice.
---

James can comment this please?

best regards

mira

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

Re: libgig 4.0.0 qsampler 4.2.0 gigedit 1.0.0

[James Cowgill]

Hi,

On 26/11/16 01:44, Jaromír Mikeš wrote:
> 2016-11-25 17:36 GMT+01:00 James Cowgill :
>> OK I've had another look and I think I understand the confusion here:
>> upstream have decided to move the headers from /usr/include to
>> /usr/include/libgig without adjusting anything else to cope with that.
>>
>> Your method would work here, but I think you should ask upstream what
>> they want here since changing it later is a PITA. The options are:
>>
>> All headers in /usr/include, all references to them loose the 'libgig/'
>> prefix.
>>
>> All headers in /usr/include/libgig, all references must have a 'libgig/'
>> prefix (including the headers themselves).
>>
>> All headers in /usr/include/libgig, all references loose the 'libgig/'
>> and -I/usr/include/libgig is added to the pkg-config file.
> 
> Answer somehow came from upstream itself before posting to him ...
> as he reviewed my patch 05-fix-include-dir.patch
> 
>> as far as I remember the previous Debian maintainer of libgig, I think he 
>> said
>> the header files should be bundled in a subdirectory according to Debian
>> policies, and the the subdirectory name should reflect the library version
>> (i.e. /usr/include/libgig4/gig.h, etc.). The motivation was to be able to
>> install i.e. two different versions of the same library (i.e. in this case
>> i.e. libgig3-dev, libgig4-dev) which would otherwise cause a file conflict.
>> But obviously I am not up to date regarding latest Debian policies.
> 
> What would be best from debian point of view?
> 
> /usr/include/libgig4/gig.h or /usr/include/libgig7/gig.h
> 
> to reflect rather soname than release?

Usually the header location does not change with the soname / ABI. Most
libraries that do change the header path frequently do it because the
API changes a lot (eg LLVM).

> Or just /usr/include/gig.h and not allow two versions installed together?
> 
> your opinion James?

I think one of the 3 options I gave should be used, but I don't mind
which one. Given that programs seem to be using headers without the
'libgig/' prefix already, the middle options seems the least desirable
but if upstream wants to update all the headers for that option then it can.

As to installing -dev packages together - upstream would also have to
rename the libgig.so symlink as well as installing headers in a
different place. I'm not sure it's worth it.

Thanks,
James



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

Mein lieber Freund !!!

[Herr Ortega Navas]

Mein lieber Freund,

Ich moechte mich erstmals gerne vorstellen. Mein Name ist Herr Ortega Navas die 
persoenliche Investment Berater und Vermoegensverwalterin meines verstorbenen 
Mandanten, der ihre familienname tragt. Er war als privater Geschaeftsmann im 
internationalen Bereich taetig. Im Jahr 2008 starb mein Mandant an einen 
schweren Herzinfarkt. Mein Mandant war ledig und kinderlos.

Er hinterliess ein Vermoegen im Wert von 10.500.000 (Zehn Millionen 
fuenfhunderttausend Euro), das sich in einer Bank in Spanien befindet.  Die 
Bank liess mir zukommen, dass ich einen Erbberechtigen, Beguenstigten 
vorstellen muss.

Nach mehreren Recherchen erhielt ich keine weiteren hilfreichen Informationen, 
über die  Verwandten meines verstorbenen Mandanten. Aus diesem Grund schrieb 
ich Sie an, da Sie den gleichen Nachnamen haben. Ich benoetige Ihre Zustimmung 
und Ihre Kooperation um Sie als den Beguenstigten vorzustellen. Alle meine 
Bemuehungen Verwandte meines verstorbenen Mandanten zu finden, waren erfolglos. 
Infolgedessen wuerde ich vorschlagen das Vermoegen aufzuteilen, Sie erhalten 
45% Prozent des Anteils und  45% Prozent wuerde mir dann zustehen. 10% Prozent 
werden an Gemeinnützige Organisationen gespendet.

Alle notwendigen Dokumente beinhalten sinngemaess auch das Ursprungszeugnis, um 
demnach  Fragen von der zustaendigen Bank zu vermeiden. Die beantragten 
Dokumente, die Sie fuer das Verfahren benoetigen, sind legal und beglaubigt. 
Das Vermoegen enthaelt kein kriminellen Ursprung. Das Verfahren wird 
einwandfrei ohne Komplikationen erfolgen,  die Geldueberweisung wird rechts 
gemaess abgeschlossen. Alles was ich von Ihnen benoetige  ist Ihr Vertrauen und 
eine gute Zusammenarbeit.

Kontaktieren Sie mich bitte unter der privaten Fax: 00 34 917 692 656, oder 
meine private E-Mail i...@navaschambers.es Die geplante Transaktion wird  durch 
legale Rechtsmitteln fuer Ihren rechtlichen Schutz gefuehrt. Bitte senden Sie 
mir auch mit Ihrem direkten Telefonnummer fuer einfache Kommunikation

Mit freundlichen Grussen
Dipl.finanzfachanwalt
Abogado Ortega Navas

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