hi
Hallo Jeg er veldig glad for å møte deg, Jeg så profilen din på (facebook) og noe som motiverte meg til å kontakte deg, My Dear i god tid kan det behager deg til å skrive meg tilbake slik at jeg vil også fortelle deg grunnen til at jeg kontaktet dere. Prøv og se at du svarer til meg som jeg venter på respons. takk og vennlig hilsen, Linda. - Hello I'm very happy to meet you, i saw your profile at (facebook) and something motivated me to contact you, My Dear in your good time may it pleases you to write me back So that i will also tell you the reason why i contacted you. Please try and see that you respond to me as i wait your response. thanks and best regards, Linda.___ 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: lame_3.98.4+repack1-1_amd64.changes is NEW
Andres, interesting repackaging work, but wouldn't it have been sufficient for most of the changes that you apply to just grab a recent VCS snapshot and package that? - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
lame_3.98.4+repack1-1_amd64.changes REJECTED
Dear Maintainer,
I'm going to REJECT this package as this license is non-free due to the fact
that it doesn't explicitly permit modification:
Files: frontend/portableio.{c,h}
Copyright: (c) 1988-1991, Apple Computer, Inc
License: other
Warranty Information
Even though Apple has reviewed this software, Apple makes no warranty
or representation, either express or implied, with respect to this
software, its quality, accuracy, merchantability, or fitness for a
particular purpose. As a result, this software is provided as is,
and you, its user, are assuming the entire risk as to its quality
and accuracy.
.
This code may be used and freely distributed as long as it includes
this copyright notice and the warranty information.
Thanks,
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
___
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#591570: marked as done (libxvidcore not linked against libpthread)
Your message dated Wed, 27 Jul 2011 10:38:46 +0200 with message-id 4e2fce96.3090...@greffrath.com and subject line Re: Bug#591570: libxvidcore not linked against libpthread has caused the Debian Bug report #591570, regarding libxvidcore not linked against libpthread 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.) -- 591570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xvidcore Version: 2:1.2.2+debian-2 Severity: important When built, xvidcore checks to see whether libpthread and pthread.h are available. Due to the build system update patch, this check fails, due to a compilation error, shown in config.log. The result is that libxvidcore gets built, with calls to libpthread functions included. When an application that uses the libxvidcore library attempts to link against libxvidcore, the link fails, due to unresolvable symbols in libxvidcore. It is worth noting that sometimes when one cleans the package, the configure process successfully locates libpthread, likely due to the build system update patch being removed. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-13-generic (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Surprise, surprise, xvidcore is now in Debian. However, we do not apply any build system update patch anymore and the library is indeed linked against libpthread. - Fabian ---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
xjadeo 0.6.1-1 MIGRATED to testing
FYI: The status of the xjadeo source package in Debian's testing distribution has changed. Previous version: 0.6.0~rc7-3 Current version: 0.6.1-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 http://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: [Lame-dev] New lame upstream release?
Dear people,
I'm in the middle of a power outage right now, using the last few
drops of energy of notebook battery and a 3G connection, so I will be
brief. (Oh, please keep in the CC'ies to me).
On Tue, Jul 26, 2011 at 14:41, Andres Mejia mcita...@gmail.com wrote:
On Jul 26, 2011 12:49 PM, robert robert.hegem...@gmx.de wrote:
Hi Rogério.
Am 26.07.2011, 16:24 Uhr, schrieb Rogério Brito rbr...@ime.usp.br:
We're just waiting for a new release of lame with all the license
clarification changes before uploading lame to Debian. :-)
I don't think that we will be able to release anything in time for
DebConf,
as LAME is just beginning to get into the beta stage.
What time frame are we talking about?
From my point of view, there may be some small patches to apply
and then release 3.99:
1 - pending LGPL patch
2 - eventually changing default behaviour for ID3v2 unicode tags.
What do the others think?
Robert, it seems that Andres just adopted the suggestion that I gave
him of backporting some changes. Regarding a new release, I think that
we may need to include one extra thing in our TODO list. See below.
I was simply going to backport the lgpl patches and upload the last release.
I suppose there's no need to wait for a new release now.
Andres, I just saw that LAME was rejected by the FTP masters:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2011-July/020498.html
That part is only used if we use lame's internal IO routines. Just rip
that apart and link with libsndfile and we're done. Please reupload
that...
I am motivated enough to get LAME into Debian that I am *seriously*
planning to rewrite that portion of the code for the next stable
release, implementing just the bare minimum that is needed for LAME to
work (and, of course, not reproducing Erik Castro's work with
sndfile).
Most of the functions in portableio.[ch] are quite trivial, anyway...
You can tell that I *badly* want LAME in Debian, can't you?
(Especially now that it seems that the FTP masters are convinced that
such software is Free Software).
Oh, hint, hint for the multimedia maintainers: what about uploading my
already packaged mp3packer from my launchpad PPA? [0]
[0]:
https://launchpad.net/~rbrito/+archive/ppa/+files/mp3packer_1.20-1~ubuntu1.dsc
OK, the battery of my laptop is running out... :-(
Regards,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
___
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: your mail
Processing commands for cont...@bugs.debian.org: close 635399 Bug#635399: mpd segfaults when building the database 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Michael Gibbs upsilon.al...@gmail.com -- Stopping processing here. Please contact me if you need assistance. -- 635399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635399 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: [Lame-dev] New lame upstream release?
On Jul 27, 2011 1:48 PM, Rogério Brito rbr...@ime.usp.br wrote:
Dear people,
I'm in the middle of a power outage right now, using the last few
drops of energy of notebook battery and a 3G connection, so I will be
brief. (Oh, please keep in the CC'ies to me).
On Tue, Jul 26, 2011 at 14:41, Andres Mejia mcita...@gmail.com wrote:
On Jul 26, 2011 12:49 PM, robert robert.hegem...@gmx.de wrote:
Hi Rogério.
Am 26.07.2011, 16:24 Uhr, schrieb Rogério Brito rbr...@ime.usp.br:
We're just waiting for a new release of lame with all the license
clarification changes before uploading lame to Debian. :-)
I don't think that we will be able to release anything in time for
DebConf,
as LAME is just beginning to get into the beta stage.
What time frame are we talking about?
From my point of view, there may be some small patches to apply
and then release 3.99:
1 - pending LGPL patch
2 - eventually changing default behaviour for ID3v2 unicode tags.
What do the others think?
Robert, it seems that Andres just adopted the suggestion that I gave
him of backporting some changes. Regarding a new release, I think that
we may need to include one extra thing in our TODO list. See below.
I was simply going to backport the lgpl patches and upload the last
release.
I suppose there's no need to wait for a new release now.
Andres, I just saw that LAME was rejected by the FTP masters:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2011-July/020498.html
That part is only used if we use lame's internal IO routines. Just rip
that apart and link with libsndfile and we're done. Please reupload
that...
I am motivated enough to get LAME into Debian that I am *seriously*
planning to rewrite that portion of the code for the next stable
release, implementing just the bare minimum that is needed for LAME to
work (and, of course, not reproducing Erik Castro's work with
sndfile).
Most of the functions in portableio.[ch] are quite trivial, anyway...
You can tell that I *badly* want LAME in Debian, can't you?
(Especially now that it seems that the FTP masters are convinced that
such software is Free Software).
Oh, hint, hint for the multimedia maintainers: what about uploading my
already packaged mp3packer from my launchpad PPA? [0]
[0]:
https://launchpad.net/~rbrito/+archive/ppa/+files/mp3packer_1.20-1~ubuntu1.dsc
OK, the battery of my laptop is running out... :-(
Regards,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
I was going to replace that code myself actually. I had the idea of using
only portableio.h with inline functions and removing portableio.c.
Also, i've had a problem before with using sndfile with lame and k3b. Not
sure if that's been resolved by 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
Re: [Lame-dev] New lame upstream release?
On Wed, Jul 27, 2011 at 19:48:05 (CEST), Rogério Brito wrote: Dear people, I'm in the middle of a power outage right now, using the last few drops of energy of notebook battery and a 3G connection, so I will be brief. (Oh, please keep in the CC'ies to me). On Tue, Jul 26, 2011 at 14:41, Andres Mejia mcita...@gmail.com wrote: On Jul 26, 2011 12:49 PM, robert robert.hegem...@gmx.de wrote: Hi Rogério. Am 26.07.2011, 16:24 Uhr, schrieb Rogério Brito rbr...@ime.usp.br: We're just waiting for a new release of lame with all the license clarification changes before uploading lame to Debian. :-) I don't think that we will be able to release anything in time for DebConf, as LAME is just beginning to get into the beta stage. What time frame are we talking about? From my point of view, there may be some small patches to apply and then release 3.99: 1 - pending LGPL patch 2 - eventually changing default behaviour for ID3v2 unicode tags. What do the others think? Robert, it seems that Andres just adopted the suggestion that I gave him of backporting some changes. Regarding a new release, I think that we may need to include one extra thing in our TODO list. See below. Andres, may I suggest that instead of placing patches inline in debian/lame-get-orig-source.sh, we create an 'upstream-dfsg' branch, do modifications there directly and roll tarballs from that? I was simply going to backport the lgpl patches and upload the last release. I suppose there's no need to wait for a new release now. Andres, I just saw that LAME was rejected by the FTP masters: http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2011-July/020498.html That part is only used if we use lame's internal IO routines. Just rip that apart and link with libsndfile and we're done. Please reupload that... Unforunately, this won't work easily because frontend/main.c uses functions from portableio.h unconditionally. We'd therefore need some more patches. Anyone familiar with the codebase and willing to contribute that patch? I am motivated enough to get LAME into Debian that I am *seriously* planning to rewrite that portion of the code for the next stable release, implementing just the bare minimum that is needed for LAME to work (and, of course, not reproducing Erik Castro's work with sndfile). Most of the functions in portableio.[ch] are quite trivial, anyway... You can tell that I *badly* want LAME in Debian, can't you? (Especially now that it seems that the FTP masters are convinced that such software is Free Software). Oh, hint, hint for the multimedia maintainers: what about uploading my already packaged mp3packer from my launchpad PPA? [0] [0]: https://launchpad.net/~rbrito/+archive/ppa/+files/mp3packer_1.20-1~ubuntu1.dsc OK, the battery of my laptop is running out... :-( Doesn't the package lack a dependency on lame? AFAIUI it is a tool to reencode .mp3 files. I persume that it uses lame for that, but the documentatin isn't entirely clear on that. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ 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: [Lame-dev] New lame upstream release?
Hi, Reinhard.
I hope that you're having a good DebConf... I miss chatting with you...
On 2011-07-27, at 16:22, Reinhard Tartler wrote:
On Wed, Jul 27, 2011 at 19:48:05 (CEST), Rogério Brito wrote:
I'm in the middle of a power outage right now, using the last few
drops of energy of notebook battery and a 3G connection, so I will be
brief. (Oh, please keep in the CC'ies to me).
The energy just came back and I'm taking that time to charge my
battery, but I won't be able to compile stuff here.
On Tue, Jul 26, 2011 at 14:41, Andres Mejia mcita...@gmail.com
wrote:
On Jul 26, 2011 12:49 PM, robert robert.hegem...@gmx.de wrote:
From my point of view, there may be some small patches to apply
and then release 3.99:
1 - pending LGPL patch
2 - eventually changing default behaviour for ID3v2 unicode tags.
Robert, it seems that Andres just adopted the suggestion that I gave
him of backporting some changes. Regarding a new release, I think
that
we may need to include one extra thing in our TODO list. See below.
Andres, may I suggest that instead of placing patches inline in
debian/lame-get-orig-source.sh, we create an 'upstream-dfsg'
branch, do
modifications there directly and roll tarballs from that?
I would like to take a peek at how you guys are packaging it... Will
do as soon as the power is back.
Andres, I just saw that LAME was rejected by the FTP masters:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-
maintainers/2011-July/020498.html
That part is only used if we use lame's internal IO routines. Just
rip
that apart and link with libsndfile and we're done. Please reupload
that...
Unforunately, this won't work easily because frontend/main.c uses
functions from portableio.h unconditionally. We'd therefore need some
more patches. Anyone familiar with the codebase and willing to
contribute that patch?
Oh, shit. I'll take a look at that... I thought that the code were
ifdef'ed... Isn't it?
Most of the functions in portableio.[ch] are quite trivial, anyway...
You can tell that I *badly* want LAME in Debian, can't you?
(Especially now that it seems that the FTP masters are convinced that
such software is Free Software).
Oh, hint, hint for the multimedia maintainers: what about
uploading my
already packaged mp3packer from my launchpad PPA? [0]
[0]: https://launchpad.net/~rbrito/+archive/ppa/+files/
mp3packer_1.20-1~ubuntu1.dsc
OK, the battery of my laptop is running out... :-(
Doesn't the package lack a dependency on lame?
No, absolutely *no* dependency on LAME.
AFAIUI it is a tool to
reencode .mp3 files. I persume that it uses lame for that, but the
documentatin isn't entirely clear on that.
It doesn't reencode. It only rearranges the frames in a lossless
manner. Like, for instance, getting the bits that are already
produced by an MP3 encoder (any one) and putting them in bins so as
to make the files smaller (taking a better advantage of the bit
reservoir, etc).
The program is so darned cool... The best thing with this MP3 thing
is that even though you already have a file that is encoded by
anyone, it is possible to a great extent to manipulate it losslessly:
* mp3gain, to avoid clipping while decoding (of course, clipping
before encoding is not remediable);
* mp3packer, to squeeze some extra bits and make the files smaller
(reduding the bitrate).
In my very humble opinion, the combo (mp3packer, LAME) breathes at
least a little bit of life in a format that many already thought that
was dead, while still being, say, universally compatible... With
them, you can raise the bitrate of your encodes a notch to get better
sound and then losslessly rearrange the file to a lower bitrate...
A side effect of it is that it also fixes many old VBR files that may
have incorrect lengths reported (and, thus, renders my package vbrfix
obsolete).
OK, enough blurb. The packaging of mp3packer is really trivial (as
you can see) and I would volunteer to maintain it under the pkg-
multimedia umbrella.
Regards,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
___
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: [Lame-dev] New lame upstream release?
2011/7/27 Rogério Brito rbr...@ime.usp.br:
Hi, Reinhard.
I hope that you're having a good DebConf... I miss chatting with you...
On 2011-07-27, at 16:22, Reinhard Tartler wrote:
On Wed, Jul 27, 2011 at 19:48:05 (CEST), Rogério Brito wrote:
I'm in the middle of a power outage right now, using the last few
drops of energy of notebook battery and a 3G connection, so I will be
brief. (Oh, please keep in the CC'ies to me).
The energy just came back and I'm taking that time to charge my battery, but
I won't be able to compile stuff here.
On Tue, Jul 26, 2011 at 14:41, Andres Mejia mcita...@gmail.com wrote:
On Jul 26, 2011 12:49 PM, robert robert.hegem...@gmx.de wrote:
From my point of view, there may be some small patches to apply
and then release 3.99:
1 - pending LGPL patch
2 - eventually changing default behaviour for ID3v2 unicode tags.
Robert, it seems that Andres just adopted the suggestion that I gave
him of backporting some changes. Regarding a new release, I think that
we may need to include one extra thing in our TODO list. See below.
Andres, may I suggest that instead of placing patches inline in
debian/lame-get-orig-source.sh, we create an 'upstream-dfsg' branch, do
modifications there directly and roll tarballs from that?
I would like to take a peek at how you guys are packaging it... Will do as
soon as the power is back.
Andres, I just saw that LAME was rejected by the FTP masters:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2011-July/020498.html
That part is only used if we use lame's internal IO routines. Just rip
that apart and link with libsndfile and we're done. Please reupload
that...
Unforunately, this won't work easily because frontend/main.c uses
functions from portableio.h unconditionally. We'd therefore need some
more patches. Anyone familiar with the codebase and willing to
contribute that patch?
Oh, shit. I'll take a look at that... I thought that the code were
ifdef'ed... Isn't it?
Most of the functions in portableio.[ch] are quite trivial, anyway...
You can tell that I *badly* want LAME in Debian, can't you?
(Especially now that it seems that the FTP masters are convinced that
such software is Free Software).
Oh, hint, hint for the multimedia maintainers: what about uploading my
already packaged mp3packer from my launchpad PPA? [0]
[0]:
https://launchpad.net/~rbrito/+archive/ppa/+files/mp3packer_1.20-1~ubuntu1.dsc
OK, the battery of my laptop is running out... :-(
Doesn't the package lack a dependency on lame?
No, absolutely *no* dependency on LAME.
AFAIUI it is a tool to
reencode .mp3 files. I persume that it uses lame for that, but the
documentatin isn't entirely clear on that.
It doesn't reencode. It only rearranges the frames in a lossless manner.
Like, for instance, getting the bits that are already produced by an MP3
encoder (any one) and putting them in bins so as to make the files smaller
(taking a better advantage of the bit reservoir, etc).
The program is so darned cool... The best thing with this MP3 thing is that
even though you already have a file that is encoded by anyone, it is
possible to a great extent to manipulate it losslessly:
* mp3gain, to avoid clipping while decoding (of course, clipping before
encoding is not remediable);
* mp3packer, to squeeze some extra bits and make the files smaller (reduding
the bitrate).
In my very humble opinion, the combo (mp3packer, LAME) breathes at least a
little bit of life in a format that many already thought that was dead,
while still being, say, universally compatible... With them, you can raise
the bitrate of your encodes a notch to get better sound and then losslessly
rearrange the file to a lower bitrate...
A side effect of it is that it also fixes many old VBR files that may have
incorrect lengths reported (and, thus, renders my package vbrfix obsolete).
OK, enough blurb. The packaging of mp3packer is really trivial (as you can
see) and I would volunteer to maintain it under the pkg-multimedia umbrella.
Regards,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
Hi Rogério,
I have a patch here with some changes we do to the build system.
We outright disable the use of the GTK frontend, since it requires a
very old version of GTK. I think there are better tools out now
(audacity maybe). Perhaps the GTK frontend should be removed from lame
entirely.
The other change simply changes how the debian directory is included
in the generated tarball. The debian directory still gets included,
but there's no need to have any Makefile* files in the debian
directory. This would remove our need to patch the build system for
each release of lame.
Index: configure.in
===
RCS
Bug#635662: xvidcore: FTBFS on hurd-i386: unrecognized platform
Package: xvidcore Version: 2:1.3.2-3 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd Hi, currently[1], xvidcore does not compile on hurd-i386. The problem is the lack of support for GNU/Hurd in configure; the attached patch (which requires autoreconf) provides it. [1] https://buildd.debian.org/status/fetch.php?pkg=xvidcorearch=hurd-i386ver=2%3A1.3.2-3stamp=1311723618 Thanks, -- Pino --- a/build/generic/configure.in +++ b/build/generic/configure.in @@ -237,7 +237,7 @@ STATIC_EXTENSION= OBJECT_EXTENSION= case $target_os in - *bsd*|linux*|beos|irix*|solaris*) + *bsd*|linux*|beos|irix*|solaris*|gnu*) AC_MSG_RESULT([.so .a .o]) STATIC_EXTENSION=a SHARED_EXTENSION=so @@ -281,7 +281,7 @@ ALTIVEC_CFLAGS= PRE_SHARED_LIB= case $target_os in - linux*|solaris*) + linux*|solaris*|gnu*) AC_MSG_RESULT([ok]) STATIC_LIB=libxvidcore.\$(STATIC_EXTENSION) SHARED_LIB=libxvidcore.\$(SHARED_EXTENSION).\$(API_MAJOR).\$(API_MINOR) @@ -419,7 +419,7 @@ if test $found_nasm_comp_prog = yes ; then AC_MSG_CHECKING([for asm object format]) case $target_os in - *bsd*|linux*|beos|irix*|solaris*) + *bsd*|linux*|beos|irix*|solaris*|gnu*) if test $ARCHITECTURE = X86_64 ; then AC_MSG_RESULT([elf64]) NASM_FORMAT=elf64 ___ 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: severity of 635119 is serious, severity of 635122 is serious, severity of 635121 is serious ...
Processing commands for cont...@bugs.debian.org: severity 635119 serious Bug #635119 [gedit-latex-plugin] gedit-latex-plugin: Please update for gedit 3.0 plugin path changes Severity set to 'serious' from 'important' severity 635122 serious Bug #635122 [gedit-valencia-plugin] gedit-valencia-plugin: Please update for gedit 3.0 plugin path changes Severity set to 'serious' from 'important' severity 635121 serious Bug #635121 [gedit-valatoys-plugin] gedit-valatoys-plugin: Please update for gedit 3.0 plugin path changes Severity set to 'serious' from 'important' severity 635120 serious Bug #635120 [gedit-r-plugin] gedit-r-plugin: Please update for gedit 3.0 plugin path changes Severity set to 'serious' from 'important' severity 635124 serious Bug #635124 [seahorse-plugins] seahorse-plugins: Please update for gedit 3.0 plugin path changes Severity set to 'serious' from 'important' severity 635118 serious Bug #635118 [supercollider-gedit] supercollider-gedit: Please update for gedit 3.0 plugin path changes Severity set to 'serious' from 'important' severity 635123 serious Bug #635123 [rabbitvcs-gedit] rabbitvcs-gedit: Please update for gedit 3.0 plugin path changes Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 635123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635123 635124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635124 635119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635119 635122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635122 635118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635118 635121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635121 635120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635120 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: [Lame-dev] New lame upstream release?
On Wed, Jul 27, 2011 at 23:48:26 (CEST), Andres Mejia wrote: Andres, may I suggest that instead of placing patches inline in debian/lame-get-orig-source.sh, we create an 'upstream-dfsg' branch, do modifications there directly and roll tarballs from that? I suppose this can be done, though once all licensing related problems are resolved upstream, there would be little use for this branch. I created the script to be (hopefully) a one time fix for the last stable release of lame. Yes, I didn't mean to imply to maintain that branch indefinitely, but only until all changes have been merged upstream. Ideally this happens before the next upstream release, but as we have learned, we cannot expect this to happen (really) soon from now. Until then, it will be easier for lame upstream to review your/our changes in the gitweb on git.debian.org and incorporate them in the upstream CVS repository. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
