smplayer 17.11.2~ds0-1 MIGRATED to testing

[Debian testing watch]

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

  Previous version: 17.8.0~ds0-1
  Current version:  17.11.2~ds0-1

-- 
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

ffdiaporama is marked for autoremoval from testing

[Debian testing autoremoval watch]

ffdiaporama 1.5-5 is marked for autoremoval from testing on 2017-12-17

It is affected by these RC bugs:
873191: ffdiaporama: please switch to ffmpeg


___
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#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

Dear Debian Legal Team,

I've CCed you for my reply to this bug, because I don't have the
experience to be able to tell if Debian implicitly relicensed
Audacious as GPL-3 from 2012-2016, how potentially falling out of
BSD-2-clause license compliance might have affected this, and also how
this should be resolved.  The Debian packaging is GPL-2+, so it's
possible to move to copyright-format/1.0 if that would simplify
things.  Also, please reply to point 2. OTTO "ancient plugins...under
different licenses.  I assume audacious-plugins will also need a
copyright review.  Please CC John and I, Bug #883731, and
debian-legal as appropriate.


Hi John,

On Thu, Dec 07, 2017 at 05:15:53PM -0500, John Lindgren wrote:
> Hi Nicholas,
> 
> > On this topic, would you please update contrib/audacious.appdata.xml
> > to reflect the current Audacious license (GPL3)? It claims the
> > project_license is BSD-2-Clause.
> 
> Sorry if my initial email was unclear.  The current Audacious license *is*
> BSD 2-clause, with some exceptions:

Oh, now I see.  Sorry I wasn't familiar with Audacious' upstream
relicensing, and thank you very much for confirming for the files I
asked about.

> 1. The embedded copy of libguess (which is an external project) is under
>a BSD 3-clause license, with a separate copyright.  I believe this is
>not a problem so long as the libguess license is also included with
>any distribution.
> 2. Some of the more ancient plugins are under different licenses, including
>GPLv2+ and GPLv3.  When we relicensed the main parts of Audacious to BSD
>around 2012, we thought it impractical to contact all of the original
>plugin authors since some of them go back to XMMS days (20 years ago now).
>The plugins are compiled as separate binaries, and Debian has them in a
>separate package (audacious-plugins).
> 
> Our upstream COPYING file makes note of these exceptions, which is one
> reason why it's important for it to be included verbatim, and not replaced
> with generic BSD 2-clause text as it is in the current Debian package.

Both BSD 3-clause and BSD 2-clause allow relicensing as GPL, thus so
long as the licensing terms are complied with correctly BSD code can
perpetually and unidirectionally flow to GPL projects.  So from what I
can tell it's 100% ok for the Debian package (both src and bin) to be
GPL-3 from 2012-to-2016, and both the Debian source packages and
binaries from this time period might actually be implicitly relicensed
as GPL-3.  If so, that's history that can't be changed.  Also, I'm not
sure what debian-legal and ftpmaster's view of #2 will be in light of
the relicensing (and possible implied relicensing back to GPL-3).

On 2016-04-06 06:55:52
(commit@124bf3bdccdac9d0eb78ce65b53c9a4ba128e052)
use-system-licenses.patch might have made Debian's implicit
relicensing invalid, not because of the deduplication patch per-se,
but because /usr/share/common-licenses/BSD is a 3-clause and not a
2-clause one like Audacious uses.  It's the same style, but is a
different license altogether...and yeah, I think one can go
BSD-2-clause to BSD-3-clause to GPL-3, but only if the original
BSD-2-clause bits aren't stripped.  I'm also unsure whether the patch
that changes the user-visible bits and the out-of-date
debian/copyright outweigh the 2-clause license that wasn't stripped
from the headers of various files.  eg: not implicitly relicensed, and
just out of date copyright plus non-compliance with 2-clause BSD.

> Regarding the plugins, I don't know the state of debian/copyright in the
> audacious-plugins package, but my main concern here is that the one in
> audacious is correct.
>
> > Conversely, what I found in debian/copyright was a project license of
> > GPL-3, with notable exceptions. eg: are really translations GPL-1+?
> 
> As I said, debian/copyright is out-of-date.  We relicensed the project
> from GPLv3 to BSD 2-clause back in 2012.  Possibly we didn't make an
> obvious enough announcement back then for Debian to take notice.

I haven't looked at audacious-plugins yet either.  Re: "is correct", I
agree, and I'm hoping the fix will be to simply synchronise with
upstream Audacious' BSD 2-clause.

> Translations are under the same license as the rest of Audacious.

Thank you for the confirmation.

> > To my eyes it looks like the upstream project license needs to be
> > clarified and disambiguated, debian/copyright needs work, and finally
> > that deduplication patch can be dropped.
> 
> Let me know if you think there are still clarifications needed upstream
> given the information I've provided here.  I'd be happy to adjust things
> as necessary.

Well, since the main Audacious project is in fact 2-clause-BSD this
is much clearer now!  Thanks again for the help.  I hope to work on
this Sunday, or after we hear back from debian-legal.

Sincerely,
Nicholas


signature.asc
Description: PGP signature
___
pkg-multimedia-maintainers mailing 

Bug#883834: kmetronome: FTBFS with latest Qt5: does not find Qt5LinguistToolsConfig.cmake

[Andreas Beckmann]

Source: kmetronome
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

kmetronome/experimental recently started to FTBFS with the current Qt5
in sid/experimental:

 debian/rules build
dh build 
   dh_update_autotools_config
   dh_auto_configure
cd obj-x86_64-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACK
AGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-- The C compiler identification is GNU 7.2.1
-- The CXX compiler identification is GNU 7.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Build configuration: None
CMake Error at CMakeLists.txt:40 (find_package):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!


Andreas


kmetronome_1.0.0-1.log.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

Processed: Re: Bug#883731: audacious: Debian packaging has incorrect license

[Debian Bug Tracking System]

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

> # License change happened in 3.3 (about 5 years ago)
> found 883731 3.3.1-1
Bug #883731 [audacious] audacious: Debian packaging has incorrect license
Marked as found in versions audacious/3.3.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
883731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883731
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#883731: audacious: Debian packaging has incorrect license

[John Lindgren]

Hi Nicholas,

> On this topic, would you please update contrib/audacious.appdata.xml
> to reflect the current Audacious license (GPL3)? It claims the
> project_license is BSD-2-Clause.

Sorry if my initial email was unclear.  The current Audacious license *is*
BSD 2-clause, with some exceptions:

1. The embedded copy of libguess (which is an external project) is under
   a BSD 3-clause license, with a separate copyright.  I believe this is
   not a problem so long as the libguess license is also included with
   any distribution.
2. Some of the more ancient plugins are under different licenses, including
   GPLv2+ and GPLv3.  When we relicensed the main parts of Audacious to BSD
   around 2012, we thought it impractical to contact all of the original
   plugin authors since some of them go back to XMMS days (20 years ago now).
   The plugins are compiled as separate binaries, and Debian has them in a
   separate package (audacious-plugins).

Our upstream COPYING file makes note of these exceptions, which is one
reason why it's important for it to be included verbatim, and not replaced
with generic BSD 2-clause text as it is in the current Debian package.

Regarding the plugins, I don't know the state of debian/copyright in the
audacious-plugins package, but my main concern here is that the one in
audacious is correct.

> However, shouldn't it say the following if Audacious' project license
> is GPL-3+ (drop the "any later version" clause for GPL-3 only) ?:

No, see above.

> Also, I found BSD-2-clause here: src/libaudcore/hook.cc,
> src/libaudcore/hook.h, src/libaudcore/output.cc, et al.

Those are correct.

> Conversely, what I found in debian/copyright was a project license of
> GPL-3, with notable exceptions. eg: are really translations GPL-1+?

As I said, debian/copyright is out-of-date.  We relicensed the project
from GPLv3 to BSD 2-clause back in 2012.  Possibly we didn't make an
obvious enough announcement back then for Debian to take notice.

Translations are under the same license as the rest of Audacious.

> To my eyes it looks like the upstream project license needs to be
> clarified and disambiguated, debian/copyright needs work, and finally
> that deduplication patch can be dropped.

Let me know if you think there are still clarifications needed upstream
given the information I've provided here.  I'd be happy to adjust things
as necessary.

Thank you,
John

___
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#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

Hi John,

On Wed, Dec 06, 2017 at 05:08:56PM -0500, John Lindgren wrote:
> 
> Per Debian policy 2.3:
> 
> "Every package must be accompanied by a verbatim copy of its copyright
> information and distribution license in the file 
> /usr/share/doc/package/copyright
> (see Copyright information for further details)."
> 
> The file /usr/share/doc/audacious/copyright shipped in the Debian package
> is out of date and does not match the current Audacious license (GPL3 vs.
> BSD 2-clause).
> 
> Worse, the Debian package patches out[1] the upstream license file which
> is normally installed under /usr/share/audacious/COPYING and visible in
> the "About" window when running Audacious.
> 
> You are currently distributing Audacious in violation both of our license
> and of Debian's own policy.  Please include the original upstream license,
> verbatim, in the Debian package, or stop distributing Audacious.
> 
> Thank you,
> 
> John Lindgren
> Audacious maintainer

I'm not the maintainer of Audacious' Debian package, but I am part of
the Multimedia team, so I took a look at the Debian and upstream
source, because I agree that license problems must be fixed asap.

On this topic, would you please update contrib/audacious.appdata.xml
to reflect the current Audacious license (GPL3)?  It claims the
project_license is BSD-2-Clause.

http://redmine.audacious-media-player.org/projects/audacious/repository/revisions/master/changes/contrib/audacious.appdata.xml

And when I looked up upstream audacious/COPYING here:
http://redmine.audacious-media-player.org/projects/audacious/repository/revisions/master/changes/COPYING

I found this, which also looks like BSD-2-Clause:

LICENSE

Copyright © 2001-2017 Audacious developers and others

(A list of the copyright holders is provided in the AUTHORS file.)

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,
   this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions, and the following disclaimer in the
   documentation provided with the distribution.

This software is provided “as is” and without any warranty, express or
implied.  In no event shall the authors be liable for any damages arising
from the use of this software.
--
However, shouldn't it say the following if Audacious' project license
is GPL-3+ (drop the "any later version" clause for GPL-3 only) ?:

Audacious, an Advanced Audio Player
Copyright (C) 2001-2017 Audacious developers and others

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see .
--

Also, I found BSD-2-clause here: src/libaudcore/hook.cc,
src/libaudcore/hook.h, src/libaudcore/output.cc, et al.

Conversely, what I found in debian/copyright was a project license of
GPL-3, with notable exceptions. eg: are really translations GPL-1+?
Because the project license seems to be BSD-2-Clause, and the
translations have "This file is distributed under the same license as
the Audacious package" I wonder if they're actually BSD-2-Clause.
Would you please provide a citation for the upstream project's
relicensing to GPL-3?

Finally, from what I understand about combining licenses I think the
BSD-2-clause project license (please provide evidence that this isn't
the case), the src/libguess/* BSD-3-clause and the GPL bits can all be
used to produce a GPL-3 binary, so long as the BSD copyright notices
are preserved.

To my eyes it looks like the upstream project license needs to be
clarified and disambiguated, debian/copyright needs work, and finally
that deduplication patch can be dropped.

I'd be happy to take care of the Debian side of things over the
weekend.

Thank you,
Nicholas


signature.asc
Description: PGP 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

Bug#883684: marked as done (fluidsynth: symbols changed on !linux architectures)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 15:05:32 +
with message-id 
and subject line Bug#883684: fixed in fluidsynth 1.1.8-2
has caused the Debian Bug report #883684,
regarding fluidsynth: symbols changed on !linux architectures
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.)


-- 
883684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fluidsynth
Version: 1.1.8-1
Severity: important

Hi,

please update the symbols files for the !linux architectures.

https://buildd.debian.org/status/package.php?p=fluidsynth=sid

I think you can just prefix the missing ones with

  (arch=linux-any)

to restrict them to the linux architectures.


Andreas
--- End Message ---
--- Begin Message ---
Source: fluidsynth
Source-Version: 1.1.8-2

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated fluidsynth 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: SHA512

Format: 1.8
Date: Thu, 07 Dec 2017 15:12:36 +0100
Source: fluidsynth
Binary: fluidsynth libfluidsynth1 libfluidsynth-dev
Architecture: source
Version: 1.1.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 fluidsynth - Real-time MIDI software synthesizer
 libfluidsynth-dev - Real-time MIDI software synthesizer (development files)
 libfluidsynth1 - Real-time MIDI software synthesizer (runtime library)
Closes: 883684
Changes:
 fluidsynth (1.1.8-2) unstable; urgency=medium
 .
   [ Fabian Greffrath ]
   * add Suggests on some common soundfonts to the libfluidsynth1 package
 .
   [ Jaromír Mikeš ]
   * Symbols changed on non-linux archs. (Closes: #883684)
   * Remove trailing whitespace from changelog.
Checksums-Sha1:
 26794aba3e9cde1e9eeaab3958ce0e4babf2d17f 2397 fluidsynth_1.1.8-2.dsc
 327d7b77490bf5219f2069ffe5eb1fdb16275cad 13504 fluidsynth_1.1.8-2.debian.tar.xz
 547e7f1f5491465cb8fc9851343034a4019a99ed 9184 
fluidsynth_1.1.8-2_amd64.buildinfo
Checksums-Sha256:
 ebc07466e6f105bfea1ef176bddb70dbf918839e71ffa78a2596b79bad0046d2 2397 
fluidsynth_1.1.8-2.dsc
 6d41002e2b3f7ee7290b001713b0b5ba291b3d686cff4039d5bd2c798518c28f 13504 
fluidsynth_1.1.8-2.debian.tar.xz
 f0199e654caff07da2be1555ca57e05ad90882740a96c60eca5daf38c0b0aa23 9184 
fluidsynth_1.1.8-2_amd64.buildinfo
Files:
 8781a9a28326540349c5b6177fd95221 2397 sound optional fluidsynth_1.1.8-2.dsc
 7525fabd31b06fa9232db16a50ede0fa 13504 sound optional 
fluidsynth_1.1.8-2.debian.tar.xz
 a106c9dc75b042ee051dfd9c1c5a9e3d 9184 sound optional 
fluidsynth_1.1.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESlQ1E9LfY1GoF46jWwGUVeK4T6UFAlopTT8VHG1pcmEubWlr
ZXNAc2V6bmFtLmN6AAoJEFsBlFXiuE+lxM8P/36lfp0rPhHye2vMjQOA3ORlCxQ9
U4NWePwtwKwUC1AnBCt3oeLksvSpz7ufkKzz8+Xob/UEzQXSDfDocdO4nwocQVY/
+PERPSzghYbFvx9C4jRPaOf1wn1iU9ZK/OkYuVOssYKvXAHYCh4u0Amg/VQrcNGY
Y+cX91QjLw/HSKUG3+BdfEqXbb/QwrIMPfrGgB7qzy/u0qfl9zYdkiToWJx14zJj
Qw9mTg2+F7BXITGDQIYfOKETOYJ7OtNN90g1oAXRK/sN2z6zY1NIEW1Zzhw/S2Uj
ETFzUFLhsBKX21bDDO6ygxkQ/TVZ4+dMb4wzxAb3laa5KiF4AVBiDs0OaD9eJeze
17BMkSyWkpW/qkq/m2mLh0vVDwx351lAMucNwC3BZTHZfRbYCOxQN4fooPE3ZGts
r2bQmm/h7qoZZs8n6MVAkiskzu049TM9BD8ldDMYoUyNA+OWu/Gd9C+EnSefeF1v
hkfUEEuttVrck4CWqvcs7yJBowb3vHWIZ3rv56NIvWD/rG5Fbq0iN/fOyQFmBFBs
V/HI77ztI4cefBCwka3dRa5XRWlXeYX7S37PZfpciTV+hZ5RR46JWsMmNsi3E2Si
GbiYMGwsI3SVzIV1K9xvD6iksl/ve5ZliQyZkZDMtR1ia06FOV+gnrtbsHQVqJZP
ccVb5fkIIQrCFgzp
=rWFW
-END PGP SIGNATURE End Message ---
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

fluidsynth_1.1.8-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2017 15:12:36 +0100
Source: fluidsynth
Binary: fluidsynth libfluidsynth1 libfluidsynth-dev
Architecture: source
Version: 1.1.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 fluidsynth - Real-time MIDI software synthesizer
 libfluidsynth-dev - Real-time MIDI software synthesizer (development files)
 libfluidsynth1 - Real-time MIDI software synthesizer (runtime library)
Closes: 883684
Changes:
 fluidsynth (1.1.8-2) unstable; urgency=medium
 .
   [ Fabian Greffrath ]
   * add Suggests on some common soundfonts to the libfluidsynth1 package
 .
   [ Jaromír Mikeš ]
   * Symbols changed on non-linux archs. (Closes: #883684)
   * Remove trailing whitespace from changelog.
Checksums-Sha1:
 26794aba3e9cde1e9eeaab3958ce0e4babf2d17f 2397 fluidsynth_1.1.8-2.dsc
 327d7b77490bf5219f2069ffe5eb1fdb16275cad 13504 fluidsynth_1.1.8-2.debian.tar.xz
 547e7f1f5491465cb8fc9851343034a4019a99ed 9184 
fluidsynth_1.1.8-2_amd64.buildinfo
Checksums-Sha256:
 ebc07466e6f105bfea1ef176bddb70dbf918839e71ffa78a2596b79bad0046d2 2397 
fluidsynth_1.1.8-2.dsc
 6d41002e2b3f7ee7290b001713b0b5ba291b3d686cff4039d5bd2c798518c28f 13504 
fluidsynth_1.1.8-2.debian.tar.xz
 f0199e654caff07da2be1555ca57e05ad90882740a96c60eca5daf38c0b0aa23 9184 
fluidsynth_1.1.8-2_amd64.buildinfo
Files:
 8781a9a28326540349c5b6177fd95221 2397 sound optional fluidsynth_1.1.8-2.dsc
 7525fabd31b06fa9232db16a50ede0fa 13504 sound optional 
fluidsynth_1.1.8-2.debian.tar.xz
 a106c9dc75b042ee051dfd9c1c5a9e3d 9184 sound optional 
fluidsynth_1.1.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESlQ1E9LfY1GoF46jWwGUVeK4T6UFAlopTT8VHG1pcmEubWlr
ZXNAc2V6bmFtLmN6AAoJEFsBlFXiuE+lxM8P/36lfp0rPhHye2vMjQOA3ORlCxQ9
U4NWePwtwKwUC1AnBCt3oeLksvSpz7ufkKzz8+Xob/UEzQXSDfDocdO4nwocQVY/
+PERPSzghYbFvx9C4jRPaOf1wn1iU9ZK/OkYuVOssYKvXAHYCh4u0Amg/VQrcNGY
Y+cX91QjLw/HSKUG3+BdfEqXbb/QwrIMPfrGgB7qzy/u0qfl9zYdkiToWJx14zJj
Qw9mTg2+F7BXITGDQIYfOKETOYJ7OtNN90g1oAXRK/sN2z6zY1NIEW1Zzhw/S2Uj
ETFzUFLhsBKX21bDDO6ygxkQ/TVZ4+dMb4wzxAb3laa5KiF4AVBiDs0OaD9eJeze
17BMkSyWkpW/qkq/m2mLh0vVDwx351lAMucNwC3BZTHZfRbYCOxQN4fooPE3ZGts
r2bQmm/h7qoZZs8n6MVAkiskzu049TM9BD8ldDMYoUyNA+OWu/Gd9C+EnSefeF1v
hkfUEEuttVrck4CWqvcs7yJBowb3vHWIZ3rv56NIvWD/rG5Fbq0iN/fOyQFmBFBs
V/HI77ztI4cefBCwka3dRa5XRWlXeYX7S37PZfpciTV+hZ5RR46JWsMmNsi3E2Si
GbiYMGwsI3SVzIV1K9xvD6iksl/ve5ZliQyZkZDMtR1ia06FOV+gnrtbsHQVqJZP
ccVb5fkIIQrCFgzp
=rWFW
-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 fluidsynth_1.1.8-2_source.changes

[Debian FTP Masters]

fluidsynth_1.1.8-2_source.changes uploaded successfully to localhost
along with the files:
  fluidsynth_1.1.8-2.dsc
  fluidsynth_1.1.8-2.debian.tar.xz
  fluidsynth_1.1.8-2_amd64.buildinfo

Greetings,

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

Processed: Bug#883684 marked as pending

[Debian Bug Tracking System]

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

> tag 883684 pending
Bug #883684 [src:fluidsynth] fluidsynth: symbols changed on !linux architectures
Added tag(s) pending.
> thanks
Stopping processing here.

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