kodi-visualization-spectrum is marked for autoremoval from testing

2017-02-22 Thread Debian testing autoremoval watch
kodi-visualization-spectrum 1.1.1-1 is marked for autoremoval from testing on 2017-03-28 It (build-)depends on packages with these RC bugs: 854985: kodi: kodi.service spamming the logs due to xinit being missing ___ pkg-multimedia-maintainers mailing

Bug#855117: vlc: Please disable OpenGL ES 1 support

2017-02-22 Thread Matthias Heinz
Hello, thank you all for clearifing this. I will create my own vlc package then to test Mesa 17. Best Matthias On Montag, 20. Februar 2017 23:13:37 CET Mateusz Lukasik wrote: > Hi, > > Check my next changes. ___ pkg-multimedia-maintainers mailing

Bug#854985: marked as done (kodi.service spamming the logs due to xinit being missing)

2017-02-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Feb 2017 16:49:31 + with message-id and subject line Bug#854985: fixed in kodi 2:17.0+dfsg1-3 has caused the Debian Bug report #854985, regarding kodi.service spamming the logs due to xinit being missing to be marked as done.

Bug#801886: marked as done (xbmc: systemd support)

2017-02-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Feb 2017 16:49:31 + with message-id and subject line Bug#801886: fixed in kodi 2:17.0+dfsg1-3 has caused the Debian Bug report #801886, regarding xbmc: systemd support to be marked as done. This means that you claim that the

kodi_17.0+dfsg1-3_source.changes ACCEPTED into unstable

2017-02-22 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 22 Feb 2017 01:28:43 +0100 Source: kodi Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev kodi-eventclients-wiiremote kodi-eventclients-ps3 kodi-eventclients-kodi-send

Processing of kodi_17.0+dfsg1-3_source.changes

2017-02-22 Thread Debian FTP Masters
kodi_17.0+dfsg1-3_source.changes uploaded successfully to localhost along with the files: kodi_17.0+dfsg1-3.dsc kodi_17.0+dfsg1-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

re

2017-02-22 Thread Christopher Kim
I have a proposal for you email me at mrshung7...@gmail.com Yours Faithfully Mrs Hung ___

!! GREETINGS !!!

2017-02-22 Thread hassan karam
Hello I am Mr. Hassan Karam, from Syria due to brutal civil war in my country, I am seeking your partnership in going into a private investment venture. I am interested in investing in your country, so I will like us to begin our acquaintance through this medium so we can deliberate more.I

Bug#855834: linuxptp: default startup argument "-i eth0" should be removed

2017-02-22 Thread Tino Mettler
On Wed, Feb 22, 2017 at 13:44:43 +, Lange Norbert wrote: > Hello, > > ptp4l can find the fitting ptp device (without eth tool), this doesnt seem to > be a problem. You are the second person stating this today, but I still think it is a misunderstanding regarding the network interface (like

Bug#855834: linuxptp: default startup argument "-i eth0" should be removed

2017-02-22 Thread Lange Norbert
Hello, ptp4l can find the fitting ptp device (without eth tool), this doesnt seem to be a problem. The only time where you don`t have to specify a ethernet device might be if you have only one (cant test this now). I can attest that it will complain if you have a single one that would be PTP

Bug#855834: linuxptp: default startup argument "-i eth0" should be removed

2017-02-22 Thread Felipe Sateler
On Wed, Feb 22, 2017 at 10:31 AM, Tino Mettler wrote: > On Wed, Feb 22, 2017 at 09:51:25 -0300, Felipe Sateler wrote: > > [...] > >> The readme suggests ptp4l can detect appropiate devices by itself. If >> that is true, then there is no problem to be solved :). > > Hi, > >

Bug#855834: linuxptp: default startup argument "-i eth0" should be removed

2017-02-22 Thread Tino Mettler
On Wed, Feb 22, 2017 at 09:51:25 -0300, Felipe Sateler wrote: [...] > The readme suggests ptp4l can detect appropiate devices by itself. If > that is true, then there is no problem to be solved :). Hi, do you mean this? -

Bug#855834: linuxptp: default startup argument "-i eth0" should be removed

2017-02-22 Thread Felipe Sateler
Hi On Wed, Feb 22, 2017 at 7:36 AM, Tino Mettler wrote: > On Wed, Feb 22, 2017 at 10:59:08 +0100, Norbert Lange wrote: > > [...] > >> I would recommend removing the argument, and add a section for the device in >> the >> configuration file. can be a placeholder like

Von Frau ANITA BAMBA

2017-02-22 Thread anitabamba
Lieber, pls Ihre Aufmerksamkeit Nachfrage nach Partnerschaft Von Frau ANITA BAMBA Bitte hilf mir Ich möchte mich für mein Eindringen in Ihre Privatsphäre entschuldigen, Erlauben Sie mir, Sie über meinen Wunsch zu informieren, in die Geschäftsbeziehung mit Ihnen zu gehen. Nachdem ich durch dein

Bug#855834: linuxptp: default startup argument "-i eth0" should be removed

2017-02-22 Thread Tino Mettler
On Wed, Feb 22, 2017 at 10:59:08 +0100, Norbert Lange wrote: [...] > I would recommend removing the argument, and add a section for the device in > the > configuration file. can be a placeholder like [eth0], I would not know > of a good default name that would fit most systems. Hi, thanks for

Bug#855834: linuxptp: default startup argument "-i eth0" should be removed

2017-02-22 Thread Norbert Lange
Package: linuxptp Version: 1.8-1 Severity: normal Dear Maintainer, a default installation of debian stretch will not use eth0 as ethernet device name anymore, also see [1]. using this as commandline argument when starting this service is troublesome, as it can`t be undone. The documention