Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 11 May 2013 01:21:18 +0200
Source: cmus
Binary: cmus cmus-plugin-ffmpeg
Architecture: source amd64
Version: 2.5.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
Changed-By: Alessi
cmus_2.5.0-2_amd64.changes uploaded successfully to localhost
along with the files:
cmus_2.5.0-2.dsc
cmus_2.5.0-2.debian.tar.gz
cmus_2.5.0-2_amd64.deb
cmus-plugin-ffmpeg_2.5.0-2_amd64.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Package: libsoundtouch-dev
Version: 1.7.1-2
User: multiarch-de...@lists.alioth.debian.org
Usertags: multiarch
libsoundtouch-dev is marked as "Multi-Arch: same", but the following
file is architecture-dependent:
/usr/include/soundtouch/soundtouch_config.h
The MD5 sums are:
04533428a780c45b104
Package: mixxx
Version: 1.10.1~dfsg0-1
Severity: wishlist
Mixxx 1.11.0 is out:
http://mixxxblog.blogspot.fr/2013/05/mixxx-1110-is-here.html
Would it be possible to upload it into Debian?
Thank you very much
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy:
On Fri, May 10, 2013 at 4:35 PM, Reinhard Tartler wrote:
> multimedia-blends:
> - Looks OK to me, Felipe, I wonder why you haven't uploaded it yet?
I've been a bit short on time lately, I plan to upload this weekend.
Also, as per the rules of the team, I need a second uploader. Anybody
wants to
Nothing particular about this commit or package, but...
The new workflow of importing upstream git history has the side effect
of drastically raising the commits list volume. What can we do about
this? Could it be possible to only send the mail out when the commit
touches the debian/ subdir?
--
On Thu, May 9, 2013 at 9:48 PM, Reinhard Tartler wrote:
> Hi,
>
> I've noticed that on http://pet.debian.net/pkg-multimedia/pet.cgi,
> there are currently 16 packages in the "Ready to upload" category.
> [...]
Next four packages:
mma:
- lintian warnings:
W: mma source: out-of-date-standards-vers
On Fri, May 10, 2013 at 1:28 PM, Carlos Alberto Lopez Perez
wrote:
> On 10/05/13 07:41, Arto Jantunen wrote:
>> The difference between the GPL and the LGPL does solve the problem if
>> the program you are developing wants to link to both LGPL licensed and
>> GPL incompatible libraries, assuming th
Quoting Carlos Alberto Lopez Perez (2013-05-10 13:28:20)
> On 10/05/13 07:41, Arto Jantunen wrote:
> > The difference between the GPL and the LGPL does solve the problem
> > if the program you are developing wants to link to both LGPL
> > licensed and GPL incompatible libraries, assuming that the
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 10 May 2013 17:27:44 +0200
Source: jalv
Binary: jalv
Architecture: source amd64
Version: 1.2.0~dfsg0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
Changed-By: Alessio Treglia
De
jalv_1.2.0~dfsg0-2_amd64.changes uploaded successfully to localhost
along with the files:
jalv_1.2.0~dfsg0-2.dsc
jalv_1.2.0~dfsg0-2.debian.tar.gz
jalv_1.2.0~dfsg0-2_amd64.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
___
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 05 May 2013 19:49:35 +0200
Source: liblivemedia
Binary: liblivemedia-dev libbasicusageenvironment0 libgroupsock0 liblivemedia7
libusageenvironment0 livemedia-utils
Architecture: source amd64
Version: 2013.04.30-1
Carlos Alberto Lopez Perez writes:
> On 10/05/13 07:41, Arto Jantunen wrote:
>> The difference between the GPL and the LGPL does solve the problem if
>> the program you are developing wants to link to both LGPL licensed and
>> GPL incompatible libraries, assuming that the license of the program
>
On 10/05/13 07:41, Arto Jantunen wrote:
> The difference between the GPL and the LGPL does solve the problem if
> the program you are developing wants to link to both LGPL licensed and
> GPL incompatible libraries, assuming that the license of the program
> itself is not either GPL or LGPL. Parts o
14 matches
Mail list logo
