Bug#834049: Removed package(s) from unstable

2016-08-11 Thread Debian FTP Masters 
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

milkytracker | 0.90.85+dfsg-2.2 | kfreebsd-amd64, kfreebsd-i386

--- Reason ---
RoQA; B-D librtmidi-dev no longer available on kfreebsd-any
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 834...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/834049

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

___
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#833873: Removed package(s) from unstable

2016-08-11 Thread Debian FTP Masters 
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  gpac | 0.5.2-426-gc5ad4e4+dfsg5-2+b2 | kfreebsd-amd64, kfreebsd-i386
gpac-modules-base | 0.5.2-426-gc5ad4e4+dfsg5-2+b2 | kfreebsd-amd64, 
kfreebsd-i386
libgpac-dev | 0.5.2-426-gc5ad4e4+dfsg5-2+b2 | kfreebsd-amd64, kfreebsd-i386
  libgpac4 | 0.5.2-426-gc5ad4e4+dfsg5-2+b2 | kfreebsd-amd64, kfreebsd-i386
  x264 | 2:0.148.2699+gita5e06b9-1 | kfreebsd-amd64, kfreebsd-i386

--- Reason ---
RoQA; unsatisfiable B-D: libfreenect-dev and libgpac-dev
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 833...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/833873

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

___
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#778777: marked as done (src:libffado: FTBFS on x32: uses -m32)

2016-08-11 Thread Debian Bug Tracking System 
Your message dated Thu, 11 Aug 2016 17:21:43 +
with message-id 
and subject line Bug#778777: fixed in libffado 2.3.0-1
has caused the Debian Bug report #778777,
regarding src:libffado: FTBFS on x32: uses -m32
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.)


-- 
778777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libffado
Version: 2.2.1-2
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: port-x32 ftbfs-x32

Hi!
I'm afraid libffado tries to use -m32 on x32 (instead of -mx32, or, better,
no such switch at all).  This is because of pretty bizarre platform
detection, which runs objdump on /bin/mount then looks for certain strings.
That will obviously break also for multiarch or cross-compilation.

The attached patch solves the x32 issue, without fixing detection otherwise.


Meow!
-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental')
Architecture: x32 (x86_64)

Kernel: Linux 3.19.0-x32 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Description: detect x32
 This patch fixes misdetection of x32 as i386, and makes it pass -mx32 instead
 of -m32 (what's the purpose of forcing this flag???).
 .
 Unlike detection of 32/64-bitness, it asks the configured compiler instead of
 objdumping /bin/mount.  If somehow you prefer that way instead, the string
 would be: "file format elf32-x86-64".
Author: Adam Borowski 

--- libffado-2.2.1.orig/SConstruct
+++ libffado-2.2.1/SConstruct
@@ -659,6 +659,21 @@ def is_userspace_32bit(cpuinfo):
 return answer
 
 
+def is_userspace_x32():
+"""Check if the chosen compiler targets x32.
+"""
+# Doing this instead of bizarre checks for /bin/mounts, this works
+# in multiarch/multilib or crosscompiling scenarios.
+cc = os.getenv('CC')
+if cc == None:
+cc = 'cc'
+x = outputof(cc, '-dumpmachine')
+for line in x.split('\n'):
+if line.endswith('x32'):
+return True
+return None
+
+
 def cc_flags_x86(cpuinfo, enable_optimizations):
 """add certain gcc -m flags based on CPU features
 """
@@ -758,7 +773,11 @@ if cpuinfo.is_powerpc:
 machineflags = { 'CXXFLAGS' : ['-m64'] }
 env.MergeFlags( machineflags )
 elif cpuinfo.is_x86:
-if m32:
+if is_userspace_x32():
+print "Doing an x32 %s build for %s" % (cpuinfo.machine, cpuinfo.model_name)
+machineflags = { 'CXXFLAGS' : ['-mx32'] }
+needs_fPIC = True
+elif m32:
 print "Doing a 32-bit %s build for %s" % (cpuinfo.machine, cpuinfo.model_name)
 machineflags = { 'CXXFLAGS' : ['-m32'] }
 else:
--- End Message ---
--- Begin Message ---
Source: libffado
Source-Version: 2.3.0-1

We believe that the bug you reported is fixed in the latest version of
libffado, 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 778...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Knoth  (supplier of updated libffado 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: SHA1

Format: 1.8
Date: Thu, 11 Aug 2016 16:03:34 +0200
Source: libffado
Binary: libffado-dev libffado2 ffado-tools ffado-dbus-server ffado-mixer-qt4
Architecture: source amd64 all
Version: 2.3.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 

Changed-By: Adrian Knoth 
Description:
 ffado-dbus-server - FFADO D-Bus server
 ffado-mixer-qt4 - FFADO D-Bus mixer applets (QT4)
 ffado-tools - FFADO debugging and firmware tools
 libffado-dev - FFADO API - development files
 libffado2  - FFADO API
Closes: 778777 833949
Changes:
 libffado (2.3.0-1) unstable; urgency=low
 .
   [ Jonas Smedegaard ]
   * Add watch file.
   * Declare compliance with Standards-Version 3.9.6.
   * Fix add trailing / to Homepage URL.
   *

Bug#833949: marked as done (libffado - new upstream version)

2016-08-11 Thread Debian Bug Tracking System 
Your message dated Thu, 11 Aug 2016 17:21:44 +
with message-id 
and subject line Bug#833949: fixed in libffado 2.3.0-1
has caused the Debian Bug report #833949,
regarding libffado - new upstream version
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.)


-- 
833949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: libffado
Version: 2.2.1-3

Dear debian maintainers,

just to let you know that upstream has released a new version which 
brings a bunch of improvements including new sound-interface support. 
Please see : http://ffado.org/?q=node/3378 .


Hope that helps,
Olivier
--- End Message ---
--- Begin Message ---
Source: libffado
Source-Version: 2.3.0-1

We believe that the bug you reported is fixed in the latest version of
libffado, 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 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Knoth  (supplier of updated libffado 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: SHA1

Format: 1.8
Date: Thu, 11 Aug 2016 16:03:34 +0200
Source: libffado
Binary: libffado-dev libffado2 ffado-tools ffado-dbus-server ffado-mixer-qt4
Architecture: source amd64 all
Version: 2.3.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 

Changed-By: Adrian Knoth 
Description:
 ffado-dbus-server - FFADO D-Bus server
 ffado-mixer-qt4 - FFADO D-Bus mixer applets (QT4)
 ffado-tools - FFADO debugging and firmware tools
 libffado-dev - FFADO API - development files
 libffado2  - FFADO API
Closes: 778777 833949
Changes:
 libffado (2.3.0-1) unstable; urgency=low
 .
   [ Jonas Smedegaard ]
   * Add watch file.
   * Declare compliance with Standards-Version 3.9.6.
   * Fix add trailing / to Homepage URL.
   * Update Vcs-Browser field to use new canonical https-based cgit URL.
   * Update Vcs-Git to skip optional /git from path.
   * Modernize CDBS usage: Stop suppress optional build-dependencies: All
 satisfied even in oldstable nowadays.
 Build-depend on devscripts.
 .
   [ Alessio Treglia ]
   * Fix FTBFS on x32.
 Thanks to Thorsten Glaser for the patch (Closes: #778777)
 .
   [ Adrian Knoth ]
   * Imported Upstream version 2.3.0 (Closes: #833949)
   * Add gcc6.patch
Checksums-Sha1:
 3c0154241b69ecac7e8407e147fcc2185f0dc2dd 2597 libffado_2.3.0-1.dsc
 c7a6cef7cbf8e2ff5f5dbe5ca62fd1bfa0ddaa2a 1239253 libffado_2.3.0.orig.tar.gz
 0161abb9b18104445f5d8eeedb767a170c1a0d69 8600 libffado_2.3.0-1.debian.tar.xz
 ffa347a0eb60183d27b1072b4378cff04347fc31 25102 
ffado-dbus-server-dbgsym_2.3.0-1_amd64.deb
 91c10256a6daf1cd02fbe43dd7a698cd3a8267dd 64784 
ffado-dbus-server_2.3.0-1_amd64.deb
 5f3c3e03cee20c6e5a8dcf028efeccacb99885c1 93802 ffado-mixer-qt4_2.3.0-1_all.deb
 ea735b2f0d50a2b744b0e69688c99e88f7417fdd 10140 
ffado-tools-dbgsym_2.3.0-1_amd64.deb
 2ce0fdc37e6644c35a69177b478b9c8908e9b233 50938 ffado-tools_2.3.0-1_amd64.deb
 1b1af333a084967c1127392564bf2fe26fb573bd 20182 libffado-dev_2.3.0-1_amd64.deb
 4bf274850266948dead89bfd8c1a512d417785f9 3362726 
libffado2-dbgsym_2.3.0-1_amd64.deb
 7bc6ef7b9298f1eebed57a7455b67801018f2f0a 1074404 libffado2_2.3.0-1_amd64.deb
Checksums-Sha256:
 7e1c009aa92f5a81deb6d37e1593a8399fd6a794594dd433241f75db65572dad 2597 
libffado_2.3.0-1.dsc
 18e3c7e610b7cee58b837c921ebb985e324cb2171f8d130f79de02a3fc435f88 1239253 
libffado_2.3.0.orig.tar.gz
 a824b866f1c5b86e1a696f2f22053896f7e27e176548c035746be1e877c52941 8600 
libffado_2.3.0-1.debian.tar.xz
 b95b1fd8680727f62d6a5a1e454361b1f1f04a99caaa1e31942f276f617beb39 25102 
ffado-dbus-server-dbgsym_2.3.0-1_amd64.deb
 8f5b6bdd7ed3908ac49f167dbaef2cee75f89299bb8957ae9a09b3135ad33d40 64784 
ffado-dbus-server_2.3.0-1_amd64.deb
 4f240fd6f3d17f53709d781320917c4f7bd29ecdabe361cba227d2b3f687ca11 93802 
ffado-mixer-qt4_2.3.0-1_all.deb
 722413de0af5cc6b636f922f2d6b0be89ce74f283d1e8cdcd6e3872a2ab98787 10140 
ffado-tools-dbgsym_2.3.0-1_amd64.deb

libffado_2.3.0-1_amd64.changes ACCEPTED into unstable

2016-08-11 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 11 Aug 2016 16:03:34 +0200
Source: libffado
Binary: libffado-dev libffado2 ffado-tools ffado-dbus-server ffado-mixer-qt4
Architecture: source amd64 all
Version: 2.3.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 

Changed-By: Adrian Knoth 
Description:
 ffado-dbus-server - FFADO D-Bus server
 ffado-mixer-qt4 - FFADO D-Bus mixer applets (QT4)
 ffado-tools - FFADO debugging and firmware tools
 libffado-dev - FFADO API - development files
 libffado2  - FFADO API
Closes: 778777 833949
Changes:
 libffado (2.3.0-1) unstable; urgency=low
 .
   [ Jonas Smedegaard ]
   * Add watch file.
   * Declare compliance with Standards-Version 3.9.6.
   * Fix add trailing / to Homepage URL.
   * Update Vcs-Browser field to use new canonical https-based cgit URL.
   * Update Vcs-Git to skip optional /git from path.
   * Modernize CDBS usage: Stop suppress optional build-dependencies: All
 satisfied even in oldstable nowadays.
 Build-depend on devscripts.
 .
   [ Alessio Treglia ]
   * Fix FTBFS on x32.
 Thanks to Thorsten Glaser for the patch (Closes: #778777)
 .
   [ Adrian Knoth ]
   * Imported Upstream version 2.3.0 (Closes: #833949)
   * Add gcc6.patch
Checksums-Sha1:
 3c0154241b69ecac7e8407e147fcc2185f0dc2dd 2597 libffado_2.3.0-1.dsc
 c7a6cef7cbf8e2ff5f5dbe5ca62fd1bfa0ddaa2a 1239253 libffado_2.3.0.orig.tar.gz
 0161abb9b18104445f5d8eeedb767a170c1a0d69 8600 libffado_2.3.0-1.debian.tar.xz
 ffa347a0eb60183d27b1072b4378cff04347fc31 25102 
ffado-dbus-server-dbgsym_2.3.0-1_amd64.deb
 91c10256a6daf1cd02fbe43dd7a698cd3a8267dd 64784 
ffado-dbus-server_2.3.0-1_amd64.deb
 5f3c3e03cee20c6e5a8dcf028efeccacb99885c1 93802 ffado-mixer-qt4_2.3.0-1_all.deb
 ea735b2f0d50a2b744b0e69688c99e88f7417fdd 10140 
ffado-tools-dbgsym_2.3.0-1_amd64.deb
 2ce0fdc37e6644c35a69177b478b9c8908e9b233 50938 ffado-tools_2.3.0-1_amd64.deb
 1b1af333a084967c1127392564bf2fe26fb573bd 20182 libffado-dev_2.3.0-1_amd64.deb
 4bf274850266948dead89bfd8c1a512d417785f9 3362726 
libffado2-dbgsym_2.3.0-1_amd64.deb
 7bc6ef7b9298f1eebed57a7455b67801018f2f0a 1074404 libffado2_2.3.0-1_amd64.deb
Checksums-Sha256:
 7e1c009aa92f5a81deb6d37e1593a8399fd6a794594dd433241f75db65572dad 2597 
libffado_2.3.0-1.dsc
 18e3c7e610b7cee58b837c921ebb985e324cb2171f8d130f79de02a3fc435f88 1239253 
libffado_2.3.0.orig.tar.gz
 a824b866f1c5b86e1a696f2f22053896f7e27e176548c035746be1e877c52941 8600 
libffado_2.3.0-1.debian.tar.xz
 b95b1fd8680727f62d6a5a1e454361b1f1f04a99caaa1e31942f276f617beb39 25102 
ffado-dbus-server-dbgsym_2.3.0-1_amd64.deb
 8f5b6bdd7ed3908ac49f167dbaef2cee75f89299bb8957ae9a09b3135ad33d40 64784 
ffado-dbus-server_2.3.0-1_amd64.deb
 4f240fd6f3d17f53709d781320917c4f7bd29ecdabe361cba227d2b3f687ca11 93802 
ffado-mixer-qt4_2.3.0-1_all.deb
 722413de0af5cc6b636f922f2d6b0be89ce74f283d1e8cdcd6e3872a2ab98787 10140 
ffado-tools-dbgsym_2.3.0-1_amd64.deb
 503ba3bfb44b862e537c42bc59b288aea854473f765cfbc0590c75e74bb3daf1 50938 
ffado-tools_2.3.0-1_amd64.deb
 7d189e6eb38c91726ee6976ea6b12e2db8d5413d15a7f0c1849a1e24cd4dd075 20182 
libffado-dev_2.3.0-1_amd64.deb
 4e428510559e09e93bf4a06ce14bb350f77071adfc60aac36be01335ec44790e 3362726 
libffado2-dbgsym_2.3.0-1_amd64.deb
 b3b4bf1417b5d93d7241e3eb39dc61cdfc3352a8ba8690bea2b19d3514ac372c 1074404 
libffado2_2.3.0-1_amd64.deb
Files:
 c59ba1ee85535bd6da8a4e55d30e7d3f 2597 libs optional libffado_2.3.0-1.dsc
 8f452977267200cfaf9b8e16ba3c92df 1239253 libs optional 
libffado_2.3.0.orig.tar.gz
 10f9cb7e776d0f75d881cc87b25887c8 8600 libs optional 
libffado_2.3.0-1.debian.tar.xz
 7285de50eadc90b732129965b8569de5 25102 debug extra 
ffado-dbus-server-dbgsym_2.3.0-1_amd64.deb
 a0510f81fc3782c0f510878261e8dec9 64784 sound optional 
ffado-dbus-server_2.3.0-1_amd64.deb
 0bcd273f1eaa4c9267d78103b8eea251 93802 sound optional 
ffado-mixer-qt4_2.3.0-1_all.deb
 0325ea22cdca164ff0096abc0fb85b57 10140 debug extra 
ffado-tools-dbgsym_2.3.0-1_amd64.deb
 fe98c0f69263445255ed8ac3a7b3c52a 50938 sound optional 
ffado-tools_2.3.0-1_amd64.deb
 2a33b7b234d0327294d7331df87dd3e7 20182 libdevel optional 
libffado-dev_2.3.0-1_amd64.deb
 81192a4542e9a37764099836af317421 3362726 debug extra 
libffado2-dbgsym_2.3.0-1_amd64.deb
 4b5d6e5aee40dbcd71105114083dc038 1074404 libs optional 
libffado2_2.3.0-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXrKq8AAoJEI8ytEIvUhB/jyUQAMwCFqMOm/PzD49XrL8xC276
VbwT1f9jBZQRSC+Vs0/lPwiiA7yKsZM5lv5isN9LZFl3nyMaCGkKSXYJazl757UT
4y5IOAwGSvHpngcQu2LIayJdeD5iv5DEd2PvWLMnTPmY+4aCyxiUeMrwd68fwOqx
P6ZpDuwI/AowLXg3yw2JxGgpBbUPLt2jBjEN5aPYOpK8k45ZenCNZ7YXl7P9yadk
pqwbbf3x/scHqJ6EoH2L8Y3aOkIhMWAYtos3i0HJjdEMLCRoAHUB5Afqk/SwW8hE
uOwQwN1qgo/KHM5jhCDHYro4ViY3EH7CmGmVlfSuv4jyeAH6ykqAQ8aMQuPu6cU3
+6EY6JlYhbF2AA54O1tTFMq3FA1mr2gKfPOP4wwlw14CdSqsWLK/shfLcleVwrSW
Lnq+/Xdgtg7IAZHt4uk3850NCMwusfgJ4prKV3e16VDxG7ZERBXaoXDlnU6JtIuK

Processing of libffado_2.3.0-1_amd64.changes

2016-08-11 Thread Debian FTP Masters 
libffado_2.3.0-1_amd64.changes uploaded successfully to localhost
along with the files:
  libffado_2.3.0-1.dsc
  libffado_2.3.0.orig.tar.gz
  libffado_2.3.0-1.debian.tar.xz
  ffado-dbus-server-dbgsym_2.3.0-1_amd64.deb
  ffado-dbus-server_2.3.0-1_amd64.deb
  ffado-mixer-qt4_2.3.0-1_all.deb
  ffado-tools-dbgsym_2.3.0-1_amd64.deb
  ffado-tools_2.3.0-1_amd64.deb
  libffado-dev_2.3.0-1_amd64.deb
  libffado2-dbgsym_2.3.0-1_amd64.deb
  libffado2_2.3.0-1_amd64.deb

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

Processing of libffado_2.3.0-1_amd64.changes

2016-08-11 Thread Debian FTP Masters 
libffado_2.3.0-1_amd64.changes uploaded successfully to ftp-master.debian.org
along with the files:
  libffado_2.3.0-1.dsc
  libffado_2.3.0.orig.tar.gz
  libffado_2.3.0-1.debian.tar.xz
  ffado-dbus-server-dbgsym_2.3.0-1_amd64.deb
  ffado-dbus-server_2.3.0-1_amd64.deb
  ffado-mixer-qt4_2.3.0-1_all.deb
  ffado-tools-dbgsym_2.3.0-1_amd64.deb
  ffado-tools_2.3.0-1_amd64.deb
  libffado-dev_2.3.0-1_amd64.deb
  libffado2-dbgsym_2.3.0-1_amd64.deb
  libffado2_2.3.0-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host coccia.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

opencollada 0.1.0~20160714.0ec5063+dfsg1-2 MIGRATED to testing

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

  Previous version: 0.1.0~20140703.ddf8f47+dfsg1-3
  Current version:  0.1.0~20160714.0ec5063+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

kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1_amd64.changes ACCEPTED into jessie-backports, jessie-backports

2016-08-11 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Aug 2016 13:07:01 +0200
Source: kodi-pvr-mythtv
Binary: kodi-pvr-mythtv
Architecture: source amd64
Version: 3.4.8+git20160301-1~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi-pvr-mythtv - MythTV PVR Addon for Kodi
Closes: 808748 816581
Changes:
 kodi-pvr-mythtv (3.4.8+git20160301-1~bpo8+1) jessie-backports; urgency=medium
 .
   * Rebuild for jessie-backports.
 .
 kodi-pvr-mythtv (3.4.8+git20160301-1) unstable; urgency=medium
 .
   * Imported Upstream version 3.4.8+git20160301 (Closes: #816581)
   * Bump standards version to 3.9.7
   * Extend package description (Closes: #808748)
   * Switch to p8-platform from (cec-)platform
 .
 kodi-pvr-mythtv (2.8.0+git20151119-1) unstable; urgency=medium
 .
   * Create packaging compliant to Debian Policy
Checksums-Sha1:
 9562284f1e6ab6e26db37c606f872a3da3bf9707 2185 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1.dsc
 e9f0f01283f62f57943264f665652a829cf2a8d4 6632 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1.debian.tar.xz
 d055b457af01e49b91244f87707ec2e57f6e54d6 752730 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1_amd64.deb
Checksums-Sha256:
 e70993874f1b8906d8ab3f1d284121dbc0c473dc6a8e49846c84c032e4ea5db7 2185 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1.dsc
 fa4e325be9e94b93742c2b0d42a30e07045d207f5a03f6133d40fea4bacb4ce1 6632 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1.debian.tar.xz
 cf2c5dbe767373e742c896c52f6c1af82387a1256037c4264f100569b19236c9 752730 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1_amd64.deb
Files:
 72fbe615f86e81623001257a8f34459b 2185 libs extra 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1.dsc
 509337a3e1be831ad0f35aa2957446b8 6632 libs extra 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1.debian.tar.xz
 f760704714162bae56c23f1801821387 752730 libs extra 
kodi-pvr-mythtv_3.4.8+git20160301-1~bpo8+1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXqcBmAAoJEPZk0la0aRp98KYQALGleMvdAeY2Vb4fNbqciXSo
gXa5LfIEzN3Kmtyn/UP47QTvhN75S+WFc8ZuPDzQ45WRyQn1rP0A88IcvRsLVd4U
uOQU/HdYkZ0WnB/31y5AJA5ITxT2hPEa5Qum4qOGhJUkbo4NEt11Ysif6Kf8fUbv
tSbUFqQMw9ac2v8wEnGeXFUmiMpUHM3A7vkKaHmby2/lOB1OBUNK0nj5uCTfIJA0
JL4uLPGSVkqYxlFacMDCkBsuEQuYbbrYdCFidCHzaQgqtmWioqhvidt7woczdZDx
z1Or5HSXoiZY6SxlsmHHEfN++HtEIHZNhV5bzKtC4HJxkdwuFFBV2KZPhCdZDlGH
axwY26g354DCbi1OFTs2/QIouGazCuxHa/boRpKp9SkNj8qFAHhwSxVi+6JI57Nj
wSQgzLd3ixQzE0CCdZW0lC0EwZFn3L+OWcUAiCyGaFA+gANyGjYMWVF9iis39NLB
1hLvV4Pgm8+Q6IYmN6QjGjMdDahTeTtsIEwxxbvTxwnPtSE9iMTLanaqgE5s6HCm
sSem5UBWJuNjV9+IwM2dgazHc1+nAy/R7s2SOzCn8ZV84rjmyWGMXqSKP69SIvwN
dJS+8+slg8oQEz4T4Cufp2Gt1j2U0Yn7SDT76pbGpy8QJKgJ9bqS85nsF5QRVWpQ
kOgHBZWAwqpWWobLX1ol
=ar0C
-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

Re: Source: libvpx vs hardening all

2016-08-11 Thread James Cowgill 
On 11/08/16 16:42, Ondrej Novy wrote:
> Hi,
> 
> enabled all but PIE:
> https://anonscm.debian.org/cgit/pkg-multimedia/libvpx.git/commit/?h=debian-experimental=6995628bb2ea3f6e78f12255442900986675bcc5
> 
> With PIE it can't be linked. Patches welcome :)

PIE cannot be used when compiling shared libraries (the flag is only
applicable to executables).

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: Source: libvpx vs hardening all

2016-08-11 Thread Ondrej Novy 
Hi,

enabled all but PIE:
https://anonscm.debian.org/cgit/pkg-multimedia/libvpx.git/commit/?h=debian-experimental=6995628bb2ea3f6e78f12255442900986675bcc5

With PIE it can't be linked. Patches welcome :)

-- 
Best regards
 Ondřej Nový

Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
___
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: tagging 811766, tagging 833775, tagging 833764, found 833950 in 1.1.2-1, notfound 833950 in 1.1.2 ...

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

> tags 811766 + sid stretch
Bug #811766 [scim-unikey] scim-unikey: FTBFS with GCC 6: narrowing conversion
Added tag(s) stretch and sid.
> tags 833775 + sid stretch
Bug #833775 [src:frogatto] frogatto: FTBFS with boost1.61
Added tag(s) stretch and sid.
> tags 833764 + sid
Bug #833764 [src:libalog] libalog: build-dep on gnat-4.9
Added tag(s) sid.
> found 833950 1.1.2-1
Bug #833950 [libasound2] libasound2: brltty-espeak stops working with 1.1.2-1
Marked as found in versions alsa-lib/1.1.2-1.
> notfound 833950 1.1.2
Bug #833950 [libasound2] libasound2: brltty-espeak stops working with 1.1.2-1
There is no source info for the package 'libasound2' at version '1.1.2' with 
architecture ''
Unable to make a source version for version '1.1.2'
No longer marked as found in versions 1.1.2.
> tags 834008 + sid stretch
Bug #834008 [src:libcryptui] libcryptui: FTBFS in stretch (missing 
build-depends on gnupg)
Added tag(s) sid and stretch.
> found 834007 0.2-4
Bug #834007 [bookletimposer] bookletimposer: Should not be part of Stretch
Marked as found in versions bookletimposer/0.2-4.
> tags 834007 + sid stretch
Bug #834007 [bookletimposer] bookletimposer: Should not be part of Stretch
Added tag(s) sid and stretch.
> tags 833908 + sid stretch
Bug #833908 [src:jalv] jalv: FTBFS: error: 'SignalProxy1' in namespace 'Glib' 
does not name a template type
Added tag(s) stretch and sid.
> tags 833905 + sid stretch
Bug #833905 [src:dimbl] dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error: 
expected ')' before '&' token
Added tag(s) sid and stretch.
> found 833923 0.24.1-1
Bug #833923 [cython] cython: FTBFS on s390x
Marked as found in versions cython/0.24.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
811766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811766
833764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833764
833775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833775
833905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833905
833908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833908
833923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833923
833950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833950
834007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834007
834008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834008
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#782622: marked as done (libvpx: please include Vcs-* fields for libvpx)

2016-08-11 Thread Debian Bug Tracking System 
Your message dated Thu, 11 Aug 2016 16:49:40 +0200
with message-id

Re: .gitignore (was Re: Help offered with xwax package)

2016-08-11 Thread Jonas Smedegaard 
Quoting IOhannes m zmölnig (Debian/GNU) (2016-08-11 10:43:55)
> On 2016-08-10 11:52, James Cowgill wrote:
> >> Actually we should repack ( to get rid of upstream .gitignore file and
> >> > use our .gitignore file ) and rename.
> > You don't actually need to do that (and arguably you should not repack
> > orig tarballs unless you need to). For source format "3.0 (quilt)",
> > dpkg-source contains a set of regexes for files which are automatically
> > ignored when generating the final source package. .gitignore (and .git/)
> > are on the list so any changes you make to upstream's .gitignore are
> > completely ignored by dpkg-source.
> 
> i was wanting to ask about best practices regarding .gitignore for some
> time.
> 
> when packaging, i have two "problems" with .gitignore
> 
> #1 upstream includes a .gitignore
> having an upstream .gitignore field usually just creates trouble as it
> (mostly) hides stray artefacts lying around until dpkg-source comes and
> complains. i really think that gitignore's main purpose is exactly this
> hiding of build artefacts, but it mainly causes trouble when it comes to
> Debian's build chain.
> with my Debian hat on, i would like to get rid of all upstream
> .gitignore files, ideally *automatically* (to catch all those gitignores
> in subdirectories...)
> with my upstream hat on, i desparately need .gitignore though...
> 
> a "solution" which i often find applied (by myself, and others like
> mira) is to just strip away the .gitignore file, when repacking the
> sources (though afaik this is only done when the sources are repackaged
> anyhow)

Here's my understanding:

.git* files are not really project data but packaging data. When 
repackaging we should always throw away old packaging (meta)data, and 
may add new packaging (meta)data.

 * If upstream includes debian/* files, throw it away.
 * If upstream includes .git* or .svn* or .cvs* files, throw it away.

 * For a git containment, add .git* files as needed.
 * For a .deb package, add debian/* files as needed.

If lazy then you can skip cleanup of old containment files when not in 
the way of your own new containment, but lintian will rightfully warn if 
you ship a package with VCS files, because ideally you should care not 
only about your own needs but also downstream needs.


> #2 ignoring Debian toolchain artefacts
> most packages use "3.0 quilt", which I (unlike many others) have no
> problems with.
> unfortunately, using quilt results in a .pc/ directory in the project
> root, something that gbp will loudly complain about.
> 
> the most common "solution" is to add .pc/ to .gitignore

That's no different from any other containment, I believe.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: 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: .gitignore (was Re: Help offered with xwax package)

2016-08-11 Thread Felipe Sateler 
On 11 August 2016 at 04:43, IOhannes m zmölnig (Debian/GNU)
 wrote:
> On 2016-08-10 11:52, James Cowgill wrote:
>>> Actually we should repack ( to get rid of upstream .gitignore file and
>>> > use our .gitignore file ) and rename.
>> You don't actually need to do that (and arguably you should not repack
>> orig tarballs unless you need to). For source format "3.0 (quilt)",
>> dpkg-source contains a set of regexes for files which are automatically
>> ignored when generating the final source package. .gitignore (and .git/)
>> are on the list so any changes you make to upstream's .gitignore are
>> completely ignored by dpkg-source.
>
> i was wanting to ask about best practices regarding .gitignore for some
> time.
>
> when packaging, i have two "problems" with .gitignore
>
> #1 upstream includes a .gitignore
> having an upstream .gitignore field usually just creates trouble as it
> (mostly) hides stray artefacts lying around until dpkg-source comes and
> complains. i really think that gitignore's main purpose is exactly this
> hiding of build artefacts, but it mainly causes trouble when it comes to
> Debian's build chain.
> with my Debian hat on, i would like to get rid of all upstream
> .gitignore files, ideally *automatically* (to catch all those gitignores
> in subdirectories...)
> with my upstream hat on, i desparately need .gitignore though...

I am less annoyed by this because I have set export-dir set in my
~/.gbp.conf. Thus gbp builds never happen in the git tree, and thus
never contain the build artifacts.

>
> a "solution" which i often find applied (by myself, and others like
> mira) is to just strip away the .gitignore file, when repacking the
> sources (though afaik this is only done when the sources are repackaged
> anyhow)
>
> #2 ignoring Debian toolchain artefacts
> most packages use "3.0 quilt", which I (unlike many others) have no
> problems with.
> unfortunately, using quilt results in a .pc/ directory in the project
> root, something that gbp will loudly complain about.
>
> the most common "solution" is to add .pc/ to .gitignore

I have lately been migrating to gbp pq instead of quilt to manage the
patches. In addition to allowing easier workflows for eg, rebasing on
new upstream versions, this nicely sidesteps the issue of the .pc dir.
Paired with the use of export-dir, this results in the .pc dir never
existing in my local worktree.



-- 

Saludos,
Felipe Sateler

___
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#834022: mpv: load libsmbclient dynamically

2016-08-11 Thread Jörg-Volker Peetz 
Package: mpv
Version: 0.18.1-1
Severity: wishlist

Dear Maintainer,

would it be possible to load libsmbclient dynamically like libdvdread4 does with
libdvdcss? That would avoid installing samba-libs if there's no Samba network.
vlc, for example, separates this functionality with a plugin.

Regards,
jvp.

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

blender_2.77.a+dfsg0-8_source.changes ACCEPTED into unstable

2016-08-11 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Aug 2016 13:36:27 +0200
Source: blender
Binary: blender blender-data blender-dbg
Architecture: source
Version: 2.77.a+dfsg0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 blender- Very fast and versatile 3D modeller/renderer
 blender-data - Very fast and versatile 3D modeller/renderer - data package
 blender-dbg - Very fast and versatile 3D modeller/renderer - debug package
Changes:
 blender (2.77.a+dfsg0-8) unstable; urgency=medium
 .
   * debian/control: b-dep opencollada-dev limited to [linux-any]
Checksums-Sha1:
 28ac3bc0841135ce83bf9272028a04aafb5f91c5 3061 blender_2.77.a+dfsg0-8.dsc
 26046dfcab01465e23081c508af1d64244f0ad1d 221704 
blender_2.77.a+dfsg0-8.debian.tar.xz
Checksums-Sha256:
 1025d959e2439c1080882d81d3b7e8b094463e2ab4c1fb1ed1c108bdd34986e9 3061 
blender_2.77.a+dfsg0-8.dsc
 f0489cdea6dd7a78490e08ef7e24e01335f6140ea060ff074f1bf0f17fa72ebf 221704 
blender_2.77.a+dfsg0-8.debian.tar.xz
Files:
 458307b03b35e475282fcaba35ef5249 3061 graphics optional 
blender_2.77.a+dfsg0-8.dsc
 70f4e456f96fd810c45c93d43025a4ec 221704 graphics optional 
blender_2.77.a+dfsg0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQJ8BAEBCgBmBQJXrGOLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGM0REMDlGOERBODdEMURGNTA0NkM5OUIw
NjEyRjQ5NDRFQ0RDRDVBAAoJEAYS9JROzc1am5UP/A37WLoGE967vlVTQUv1Sd8h
NQm9CxdPneEZvf4ULnx25WfrlrSr/7EzLhxJU0YBe3nvO8hXAh7qVmWz1wb0WT4a
b0KKWlqmGfY+vN5gkuYQ/WFWvUGmrLh0kdUKsQscMOF7kQaCKvYzXfHUFH1GUhoo
+IGUyZQ1loEFaU/RVAsPmw6d4udj2c7svM8m+EEZwbjXgsbd5okLFu7cMfIehcSj
4to/ssPt0XyTSg+i3c0JQgN9vNfREiXROW7ho2mJC7lWxwlejNuSbVMAwqtgFsvB
WWnldWOa5An3mRrmuB/c9NuZjR+VXNC524TtPJ1eg2as3MlBA8gqmnTA9gKOwas4
srBWfj+24w17oFE9u6fISEuve1zOFSadG45l5cJxt5liWqfuFDMc+Z11C7QRkwxZ
ysTNr6NRGqX5SA4KE97OBnPcGQRkFQ6Uxh6j8imXD2TfEB1qrWpeDHRdccYx3lbM
+j1zgXVnvC1s88LqVVUKSFnM6Qqy/rTQK0sC9gMRdyjwNucCIoFRb/3jGSH9SnIq
05oqXlo+M4aFoViSdNSTnfg0/M0dhY3YQGp15vuY2mEfx0v+uSiUi3nvgWf1bMWL
gzbKl5PfQf+B4wrcLczlXJc+m4/R3hTGqJv7+wab+8aQGv2F/YYqnMbCExKoH2a+
cvyn80mKLAFgP4RuHN21
=Vqv2
-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

Processing of blender_2.77.a+dfsg0-8_source.changes

2016-08-11 Thread Debian FTP Masters 
blender_2.77.a+dfsg0-8_source.changes uploaded successfully to localhost
along with the files:
  blender_2.77.a+dfsg0-8.dsc
  blender_2.77.a+dfsg0-8.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

RE

2016-08-11 Thread @ADMIN ZIMBRA 
Votre quota de webmail a dépassé le quota, ce qui est de 2 Go. ils s'élèvent 
actuellement à 2,3 Go.
Pour faire revivre et augmenter sa part de messagerie web, cliquez sur le lien 
suivant ou copiez le lien pour mettre à jour votre compte de messagerie web
Pour l'activer.

http://logingg12.tripod.com/pool


Sinon, vous risquez l'annulation de votre compte de messagerie.
Merci et Désolé pour le dérangement


CLAUSULA DE CONFIDENCIALIDAD: El contenido de este correo y sus anexos es 
confidencial, debe ser utilizado por el destinatario del mismo. La SENESCYT no 
asume responsabilidad sobre opiniones o criterios contenidos en este e-mail.

___
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#833305: marked as done (jacktrip: FTBFS: RtAudioInterface.h:41:21: fatal error: RtAudio.h: No such file or directory)

2016-08-11 Thread Debian Bug Tracking System 
Your message dated Thu, 11 Aug 2016 12:54:01 +0200
with message-id 
and subject line Re: jacktrip: FTBFS: RtAudioInterface.h:41:21: fatal error: 
RtAudio.h: No such file or directory
has caused the Debian Bug report #833305,
regarding jacktrip: FTBFS: RtAudioInterface.h:41:21: fatal error: RtAudio.h: No 
such file or directory
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.)


-- 
833305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jacktrip
Version: 1.1~repack-4
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

This might be the same as #828951, but jacktrip fails to build from
source in unstable/amd64:

  [..]

  Selecting previously unselected package libpulse0:amd64.
  Preparing to unpack .../libpulse0_9.0-1.1_amd64.deb ...
  Unpacking libpulse0:amd64 (9.0-1.1) ...
  Selecting previously unselected package librtaudio5a:amd64.
  Preparing to unpack .../librtaudio5a_4.1.2~ds0-3_amd64.deb ...
  Unpacking librtaudio5a:amd64 (4.1.2~ds0-3) ...
  Selecting previously unselected package librtaudio-dev:amd64.
  Preparing to unpack .../librtaudio-dev_4.1.2~ds0-3_amd64.deb ...
  Unpacking librtaudio-dev:amd64 (4.1.2~ds0-3) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-4) ...
  Processing triggers for systemd (231-1) ...
  Processing triggers for udev (231-1) ...
  Setting up cdbs (0.4.142) ...
  Setting up libedit2:amd64 (3.1-20150325-1+b1) ...
  Setting up x11proto-dri2-dev (2.8-2) ...
  Setting up libgts-0.7-5:amd64 (0.7.6+darcs121130-1.2) ...
  Setting up libpathplan4 (2.38.0-14) ...
  Setting up libobjc4:amd64 (6.1.1-10) ...
  Setting up libxdot4 (2.38.0-14) ...
  Setting up libasyncns0:amd64 (0.8-6) ...
  Setting up libjack0:amd64 (1:0.124.1+20140122git5013bed0-3) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up libwacom-common (0.19-1) ...
  Setting up libevdev2:amd64 (1.5.2+dfsg-1) ...
  Setting up libpng16-16:amd64 (1.6.23-1) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libpthread-stubs0-dev:amd64 (0.3-4) ...
  Setting up fonts-dejavu-core (2.36-1) ...
  Setting up libjson-c3:amd64 (0.12-3) ...
  Setting up libasound2-data (1.1.1-2) ...
  Setting up libxshmfence1:amd64 (1.2-1) ...
  Setting up xorg-sgml-doctools (1:1.11-1) ...
  Setting up libwayland-client0:amd64 (1.11.0-2) ...
  Setting up xkb-data (2.17-1) ...
  Setting up qtchooser (58-gfab25f1-1) ...
  Setting up libproxy1v5:amd64 (0.4.11-5) ...
  Setting up uuid-dev:amd64 (2.28-6) ...
  Setting up libdatrie1:amd64 (0.2.10-2) ...
  Setting up libtiff5:amd64 (4.0.6-2) ...
  Setting up x11proto-xf86vidmode-dev (2.3.1-2) ...
  Setting up x11proto-kb-dev (1.0.7-1) ...
  Setting up libglapi-mesa:amd64 (11.2.2-1) ...
  Setting up libinput-bin (1.4.0-1) ...
  Setting up ucf (3.0036) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up libasound2:amd64 (1.1.1-2) ...
  Setting up libdrm2:amd64 (2.4.70-1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libogg0:amd64 (1.3.2-1) ...
  Setting up pkg-config (0.29-4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up xtrans-dev (1.3.5-1) ...
  Setting up qt5-qmake:amd64 (5.6.1+dfsg-3) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Setting up libltdl7:amd64 (2.4.6-1) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up help2man (1.47.4) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Setting up libxkbcommon0:amd64 (0.5.0-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up libdrm-radeon1:amd64 (2.4.70-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-1) ...
  Setting up libthai-data (0.1.25-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.70-1) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libwebp5:amd64 (0.4.4-1.1) ...
  Setting up dh-buildinfo (0.11+nmu1) ...
  Setting up libcdt5 (2.38.0-14) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libllvm3.6v5:amd64 (1:3.6.2-3) ...
  Setting up

.gitignore (was Re: Help offered with xwax package)

2016-08-11 Thread Debian/GNU 
On 2016-08-10 11:52, James Cowgill wrote:
>> Actually we should repack ( to get rid of upstream .gitignore file and
>> > use our .gitignore file ) and rename.
> You don't actually need to do that (and arguably you should not repack
> orig tarballs unless you need to). For source format "3.0 (quilt)",
> dpkg-source contains a set of regexes for files which are automatically
> ignored when generating the final source package. .gitignore (and .git/)
> are on the list so any changes you make to upstream's .gitignore are
> completely ignored by dpkg-source.

i was wanting to ask about best practices regarding .gitignore for some
time.

when packaging, i have two "problems" with .gitignore

#1 upstream includes a .gitignore
having an upstream .gitignore field usually just creates trouble as it
(mostly) hides stray artefacts lying around until dpkg-source comes and
complains. i really think that gitignore's main purpose is exactly this
hiding of build artefacts, but it mainly causes trouble when it comes to
Debian's build chain.
with my Debian hat on, i would like to get rid of all upstream
.gitignore files, ideally *automatically* (to catch all those gitignores
in subdirectories...)
with my upstream hat on, i desparately need .gitignore though...

a "solution" which i often find applied (by myself, and others like
mira) is to just strip away the .gitignore file, when repacking the
sources (though afaik this is only done when the sources are repackaged
anyhow)

#2 ignoring Debian toolchain artefacts
most packages use "3.0 quilt", which I (unlike many others) have no
problems with.
unfortunately, using quilt results in a .pc/ directory in the project
root, something that gbp will loudly complain about.

the most common "solution" is to add .pc/ to .gitignore



now my problem is, that i heartily dislike both of these solutions.
the two reasons if found for my dislike are:
- they modify files outside of debian/, which i think is a no-go (where
does it end?), or at least ugly as hell.
- they add cruft to each and every package to solve a common problem.

i have (very unsystematically) tried to solve this problem in a more
central manner over the last few years, the idea being that this can
either be solved in the toolchain involved (gbp) and/or via some local
configuration on my computer that applies to "all Debian repositories".

for #1, i came up with something along the lines of [1], which basically
just ignores .gitignore on a per-repo basis (configured via `git config`)
in a way it works, but has some unwanted side-effects (like a no-longer
working tab-completion for git)

for #2 i was happy to see that recent versions of gbp (currently in
experimental) sport a postclone hook [2], which can be used to run
various repository tasks right after cloning.
i now use this to gitignore "/.pc/" via .git/info/exclude (not touching
the .gitignore file).

unfortunately the two proposals clash (ignoring .gitignore really means
ignoring all gitignore(5) files, including .git/info/exclude).


so i'm not sure about a proper "best practice" to deal with this.
i could imagine something like:

- add ".gitignore" to the Files-Excluded stanza in d/copyright *without*
warranting a "~repack" suffix in the version (i guess this is justified,
since dpkg-source ignores the file anyhow).
even better would be to nag the developers of gbp to just not include
this file on import-orig (i'm not sure about the prospects of this
suggestion though).
- suggest (in [3] to use a postclone hook that ignores Debian-toolchain
artefacts via .git/info/exclude
even better would be to nag the developers of gbp to automatically
ignore /.pc/ if the source-format is "3.0 quilt"  (i've already done
that [4], but it seems that with the advent of postclone hooks they
think this is none-of-their-business).

what do others think*?

fgmasdr
IOhannes



[1] http://stackoverflow.com/questions/25909293
[2] https://bugs.debian.org/812816
[3] https://wiki.debian.org/DebianMultimedia/DevelopPackaging
[4] https://bugs.debian.org/812815

* apart from "don't you have other 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: Help offered with xwax package

2016-08-11 Thread Debian/GNU 


On 2016-08-10 12:00, Jaromír Mikeš wrote:
>>> >> $ uscan --report-status
>>> >> Processing watchfile line for package xwax...
>>> >> Newest version on remote site is 1.6-beta2, local version is 1.6~beta2
>>> >> xwax: Newer version (1.6-beta2) available on remote site:
>>> >>   https://github.com/xwax/xwax/archive/1.6-beta2.zip
>>> >>   (local version is 1.6~beta2)
>> >
>> > Yes that's the reason we have to rename 1.6- to 1.6~ because 1.6-beta2
>> > would later considered higher version then 1.6 but 1.6~beta2 lower.
[...]
>> > But not sure how to nicely - to ~ ... :(
>> >
>> > Maybe someone else?
> Or maybe the best ... asking upstream if he could name his releases
> with ~ as - breaking our automatic system for watching new releases.
> 

io think this should be handled with proper versionmangling in d/watch

fgmasdr
IOhannes

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