Bug#787406: libavcodec-extra-56: arch-dependent file in "Multi-Arch: same" package

Package: libavcodec-extra-56 Version: 6:11.4-1 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch libavcodec-extra-56 is marked as "Multi-Arch: same", but the following file is architecture-dependent: /usr/share/lintian/overrides/libavcodec-extra-56 An examp

Bug#787406: libavcodec-extra-56: arch-dependent file in "Multi-Arch: same" package

* Jakub Wilk , 2015-06-01, 10:28: diff -ur libavcodec-extra-56_11.4-1_i386/usr/share/lintian/overrides/libavcodec-extra-56 libavcodec-extra-56_11.4-1_amd64/usr/share/lintian/overrides/libavcodec-extra-56 --- libavcodec-extra-56_11.4-1_i386/usr/share/lintian/overrides/libavcodec-extra-56 2

Bug#787406: libavcodec-extra-56: arch-dependent file in "Multi-Arch: same" package

On 2015-06-01 10:28:44, Jakub Wilk wrote: > Package: libavcodec-extra-56 > Version: 6:11.4-1 > Severity: important > User: multiarch-de...@lists.alioth.debian.org > Usertags: multiarch > > libavcodec-extra-56 is marked as "Multi-Arch: same", but the following file > is architecture-dependent: > >

Processed: limit source to libav, tagging 787406

Processing commands for cont...@bugs.debian.org: > limit source libav Limiting to bugs with field 'source' containing at least one of 'libav' Limit currently set to 'source':'libav' > tags 787406 + pending Bug #787406 [libavcodec-extra-56] libavcodec-extra-56: arch-dependent file in "Multi-Arch:

Re: multiple uploaders

On 31 May 2015 at 19:36, Reinhard Tartler wrote: > IMO, if there is no need for team commitment, then there is no need > for the package to be under team maintenance in the first place. In > this case, it really doesn't matter if the package has a dedicated > maintainer or a team with a single upl

Re: Select provider of libav* libraries

On 2015-05-30 17:54:46, Reinhard Tartler wrote: > - Sebastian, you made the most recent uploads of the Libav package > where I handed off upstream releases to you, but I don't recall you > participating in this thread. I also know that you have been > interacting with Libav upstream in the past. I

Re: Select provider of libav* libraries

Hi Alessio, On 01.06.2015 08:49, Alessio Treglia wrote: > On Sun, May 31, 2015 at 1:25 PM, Jonas Smedegaard wrote: >> No, neither the new input in the past couple weeks nor repition of old >> input have made me change opinion on the matter. > > Not mine, either. > > However, > > It seems prett

Re: Seeking for sponsorship for linuxptp (PTP/IEEE1588 implementation)

On 2015-05-27 12:59, Tino Mettler wrote: > I hope you are ok withe the current state of the package. so lintian stil gives me one error and a couple of informational warnings. the error *must* be fixed before we can upload it, the informational tags should be fixed (and are really mostly no-braine

Re: Seeking for sponsorship for linuxptp (PTP/IEEE1588 implementation)

hi, @tino: did you get this email? On 2015-05-27 12:59, Tino Mettler wrote: > How will maintainership within the debian-multimedia team work? please read [1], esp. the "FAQ" and "Join" pages, if you haven't done so already. esp. please subscribe to the pkg-multimedia-maintainers mailinglist, so

Re: Select provider of libav* libraries

On Mon, Jun 1, 2015 at 3:49 PM, Andreas Cadhalpun wrote: > Does someone know what would be the best way to move the repository? Just move the directory? Or add a new remote and push everything to it. I'd also suggest to ask for the removal of the old one - to save disk space. -- Alessio Treglia

Re: Select provider of libav* libraries

On 2015-06-01 16:49, Andreas Cadhalpun wrote: > Does someone know what would be the best way to move the repository? > $ cd /git/collab-maint $ mv ffmpeg.git /etc/pkg-multimedia $ ln -s /etc/pkg-multimedia/ffmpeg.git . should I do it? fgasdr IOhannes _

Re: Select provider of libav* libraries

Am Montag, den 01.06.2015, 16:49 +0200 schrieb Andreas Cadhalpun: > Does someone know what would be the best way to move the repository? Don't know of this is the best way, but it's the "hard" way. ssh git.debian.org cd /srv/git.debian.org/git mv collab-maint/ffmpeg.git pkg-multimedia ln -s pkg-

Re: Select provider of libav* libraries

On Mon, Jun 1, 2015 at 3:54 PM, umläute wrote: > On 2015-06-01 16:49, Andreas Cadhalpun wrote: >> Does someone know what would be the best way to move the repository? >> > > $ cd /git/collab-maint > $ mv ffmpeg.git /etc/pkg-multimedia > $ ln -s /etc/pkg-multimedia/ffmpeg.git . > > should I do it?

Re: Select provider of libav* libraries

Hi Sebastian, On 01.06.2015 15:33, Sebastian Ramacher wrote: > On 2015-05-30 17:54:46, Reinhard Tartler wrote: >> - Sebastian, you made the most recent uploads of the Libav package >> where I handed off upstream releases to you, but I don't recall you >> participating in this thread. I also know

Re: Select provider of libav* libraries

Hi Alessio (and all others who were quick to reply :), On 01.06.2015 16:58, Alessio Treglia wrote: > On Mon, Jun 1, 2015 at 3:54 PM, umläute wrote: >> On 2015-06-01 16:49, Andreas Cadhalpun wrote: >>> Does someone know what would be the best way to move the repository? >>> >> >> $ cd /git/collab-

Re: Select provider of libav* libraries

On 1 June 2015 at 12:00, Andreas Cadhalpun wrote: > Hi Alessio (and all others who were quick to reply :), > > On 01.06.2015 16:58, Alessio Treglia wrote: >> On Mon, Jun 1, 2015 at 3:54 PM, umläute wrote: >>> On 2015-06-01 16:49, Andreas Cadhalpun wrote: Does someone know what would be the b

Re: Select provider of libav* libraries

On Mon, Jun 1, 2015 at 4:00 PM, Andreas Cadhalpun wrote: > What about the git hooks sending the commit mails to the list? > I can't imaging it'll just work, or will it? Ah, nice catch. I haven't played too much with the hooks, that's why I'd feel more comfortable in: 1. creating the empty repo

Bug#786438: [Fwd: Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0]

Dear Robert, a bug has been reported against the Debian lame package on arch i386 [1]. The library fails with a SIGSEGV in init_xrpow_core_sse(). As it turns out, this is a general-protection exception triggered by non-aligned memory access. Bernhard Übelacker succeeded to create a patch that forc

Re: Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Trimming cc list because this is only semi-related to the bug, but... On 1 June 2015 at 02:45, Fabian Greffrath wrote: > This is from the diff of both build logs (wheezy and jessie) during > the ./configure phase: > > @@ -440,9 +566,9 @@ > checking sys/time.h presence... yes > checking for sys/ti

Re: Select provider of libav* libraries

On 2015-05-31 13:21:07, Andreas Cadhalpun wrote: > > I'd rather keep the packaging of the package that is currently called > > "libav", because on many architectures, it compiles multiple "flavors" > > with hardware optimized flavors (on i386 for instance, there is a > > flavor without latest SEE,

Re: Select provider of libav* libraries

Hi Andreas On 2015-06-01 16:59:13, Andreas Cadhalpun wrote: > On 01.06.2015 15:33, Sebastian Ramacher wrote: > > On 2015-05-30 17:54:46, Reinhard Tartler wrote: > >> - Sebastian, you made the most recent uploads of the Libav package > >> where I handed off upstream releases to you, but I don't re

Re: Select provider of libav* libraries

Hi Felipe, On 01.06.2015 17:06, Felipe Sateler wrote: > On 1 June 2015 at 12:00, Andreas Cadhalpun >> What about the git hooks sending the commit mails to the list? >> I can't imaging it'll just work, or will it? > > You can check what /git/pkg-multimedia/setup-repository does. Ah, thanks for th

Re: Select provider of libav* libraries

Hi Sebastian, On 01.06.2015 17:18, Sebastian Ramacher wrote: > On 2015-05-31 13:21:07, Andreas Cadhalpun wrote: >>> I'd rather keep the packaging of the package that is currently called >>> "libav", because on many architectures, it compiles multiple "flavors" >>> with hardware optimized flavors (

Re: Select provider of libav* libraries

On 2015-06-01 17:29:13, Sebastian Ramacher wrote: > Hi Andreas > > On 2015-06-01 16:59:13, Andreas Cadhalpun wrote: > > On 01.06.2015 15:33, Sebastian Ramacher wrote: > > > On 2015-05-30 17:54:46, Reinhard Tartler wrote: > > >> - Sebastian, you made the most recent uploads of the Libav package >

Re: Select provider of libav* libraries

Hi Sebastian, 2015-06-01 15:33 GMT+02:00 Sebastian Ramacher : > On 2015-05-30 17:54:46, Reinhard Tartler wrote: >> - Sebastian, you made the most recent uploads of the Libav package >> where I handed off upstream releases to you, but I don't recall you >> participating in this thread. I also know

Re: Select provider of libav* libraries

2015-06-01 17:37 GMT+02:00 Bálint Réczey : > Hi Sebastian, > > 2015-06-01 15:33 GMT+02:00 Sebastian Ramacher : >> On 2015-05-30 17:54:46, Reinhard Tartler wrote: >>> - Sebastian, you made the most recent uploads of the Libav package >>> where I handed off upstream releases to you, but I don't reca

Re: Select provider of libav* libraries

Hi Bálint, On 01.06.2015 17:57, Bálint Réczey wrote: > 2015-06-01 17:45 GMT+02:00 Andreas Cadhalpun > : >> I think having the arguments on the wiki isn't such a bad idea, >> because reading a long mailing list thread (where the arguments tend >> to go around in circles) consumes a lot of time. >>

Re: Select provider of libav* libraries

Hi Sebastian, On 01.06.2015 17:29, Sebastian Ramacher wrote: > On 2015-06-01 16:59:13, Andreas Cadhalpun wrote: >> If you tell me where and how, I can put my arguments on a wiki page. > > I've created [1]. [2] and [3] can be used to list arguments for libav > respectively ffmpeg. > > [1] https:/

Re: Select provider of libav* libraries

On Mon, Jun 1, 2015 at 5:07 PM, Andreas Cadhalpun wrote: > I hope creating these wiki pages won't delay the switch. > And it'll save me from having to explain my point of view another time, > because I can just point to the wiki. We should have created such pages long ago actually. Better late th

Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Hi Bernhard, Am Freitag, den 29.05.2015, 19:02 +0200 schrieb Bernhard Übelacker: > Tried to declare the variable with "__attribute__ ((aligned (16)))" but > did not change anything. I just reset my i386 chroot and don't have enough bandwidth from the train to reconstruct it enough to further deb

Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Hello Fabian, did the test inside the i386 VM. But it did not help either. The "packed" gets ignored. (But I am not sure if I use the __attribute__ the right way?) Kind regards, Bernhard --- const vecfloat_union fabs_mask __attribute__((aligned(16),packed)) = {{ 0x7FFF, 0x7FFF,

Re: Select provider of libav* libraries

Hi Bálint On 2015-06-01 17:37:36, Bálint Réczey wrote: > 2015-06-01 15:33 GMT+02:00 Sebastian Ramacher : > > On 2015-05-30 17:54:46, Reinhard Tartler wrote: > >> - Sebastian, you made the most recent uploads of the Libav package > >> where I handed off upstream releases to you, but I don't recall

Re: Select provider of libav* libraries

Hi Andreas, 2015-06-01 17:45 GMT+02:00 Andreas Cadhalpun : > Hi Bálint, > > On 01.06.2015 17:37, Bálint Réczey wrote: >> 2015-06-01 15:33 GMT+02:00 Sebastian Ramacher : >>> On 2015-05-30 17:54:46, Reinhard Tartler wrote: - Sebastian, you made the most recent uploads of the Libav package

Re: Select provider of libav* libraries

Hi Bálint, On 01.06.2015 17:37, Bálint Réczey wrote: > 2015-06-01 15:33 GMT+02:00 Sebastian Ramacher : >> On 2015-05-30 17:54:46, Reinhard Tartler wrote: >>> - Sebastian, you made the most recent uploads of the Libav package >>> where I handed off upstream releases to you, but I don't recall you

x264 2:0.146.2538+git121396c-2 MIGRATED to testing

FYI: The status of the x264 source package in Debian's testing distribution has changed. Previous version: 2:0.142.2431+gita5831aa-1 Current version: 2:0.146.2538+git121396c-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens mult

Re: multiple uploaders

Hi Reinhard, Just answering this unanswered question from the thread as I have nothing more (worth adding) to the rest. And everyone is probably tired :-) On 06/01/2015 12:36 AM, Reinhard Tartler wrote: >>> Can I suggest that for new packages: >>> 1. the one intending to ITP asks if the

Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Hi again, Am Montag, den 01.06.2015, 18:32 +0200 schrieb Bernhard Übelacker: > did the test inside the i386 VM. > But it did not help either. The "packed" gets ignored. > (But I am not sure if I use the __attribute__ the right way?) I think it should rather go this way: --- a/libmp3lame/vector/

Bug#787436: audacious-plugins: Global Hotkeys only work if focus in same display as audacious

Package: audacious-plugins Version: 3.5-1+b2 Severity: important Dear Maintainer, I have just upgraded the system in question from Debian Wheezy to Debian Jessie. In doing so I did allow systemd, including its init system, to be installed. On Wheezy the Global Hotkeys plugin would detect

Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Hello Fabian, unfortunately this did not work too (with or without "packed"). Kind regards, Bernhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/

Bug#764075: Audacity 2.1.0 released March 29, 2015, please update Debian packages

Audacity 2.1.0 released March 29, 2015, please update Debian packages Lots of new useful features, improvements and bugfixes: Audacity 2.1.0 replaces all previous versions. - For a long time, we have wanted Real-Time Preview for effects. It seemed ne

Fwd: debian-multimedia uploaded to mentors.debian.net

Hi Felipe, I have built a multimedia-blends package and uploaded it to Mentors (see links below). I set the distribution to unstable already, otherwise the package builds with the wrong dependencies. I saw your bug about the "default package | alternative package", but assume from the response th

Processing of debian-multimedia_0.3_amd64.changes

debian-multimedia_0.3_amd64.changes uploaded successfully to localhost along with the files: debian-multimedia_0.3.dsc debian-multimedia_0.3.tar.xz multimedia-ambisonics_0.3_all.deb multimedia-audio-plugins_0.3_all.deb multimedia-devel_0.3_all.deb multimedia-djing_0.3_all.deb multimed

Re: debian-multimedia uploaded to mentors.debian.net

Hi Ross, On 1 June 2015 at 17:35, Ross Gammon wrote: > Hi Felipe, > > I have built a multimedia-blends package and uploaded it to Mentors (see > links below). No need to upload to mentors, I can pull from git ;) > I set the distribution to unstable already, otherwise the > package builds with t

Bug#784796: blender: NDOF using spacenavd driver works in 2.72 (2014-12-03) but not 2.74 after update

Matteo F. Vescovi (m...@debian.org) wrote: > On May 31, 2015 4:45 AM, "Simon Budig" wrote: > > Package: blender > > Version: 2.74+dfsg0-2+b1 > > Followup-For: Bug #784796 > > > > The missing support for spacenaved is most likely related to the package > > being built without WITH_INPUT_NDOF=ON (wh

debian-multimedia_0.3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 Jun 2015 18:01:37 -0300 Source: debian-multimedia Binary: multimedia-tasks multimedia-ambisonics multimedia-audio-plugins multimedia-devel multimedia-djing multimedia-drums multimedia-firewire multimedia-graph

Bug#722256: marked as done (Please update Recommends for ffmpeg)

Your message dated Mon, 01 Jun 2015 22:06:31 + with message-id and subject line Bug#722256: fixed in debian-multimedia 0.3 has caused the Debian Bug report #722256, regarding Please update Recommends for ffmpeg to be marked as done. This means that you claim that the problem has been dealt wi

Bug#766091: marked as done (Update existing ambisonics tasks with the latest information)

Your message dated Mon, 01 Jun 2015 22:06:31 + with message-id and subject line Bug#766091: fixed in debian-multimedia 0.3 has caused the Debian Bug report #766091, regarding Update existing ambisonics tasks with the latest information to be marked as done. This means that you claim that the

Re: multiple uploaders

On Jun 1, 2015 7:11 AM, "Felipe Sateler" wrote: > > On 31 May 2015 at 19:36, Reinhard Tartler wrote: > > IMO, if there is no need for team commitment, then there is no need > > for the package to be under team maintenance in the first place. In > > this case, it really doesn't matter if the packa

Re: multiple uploaders

On Jun 1, 2015 1:35 AM, "Fabian Greffrath" wrote: > And by the current rule, would libav still qualify as being > pkg-multimedia team-maintained? I would say yes: Most recently, Sebastian has not only provided commits, but even uploaded several packages to both unstable and stable-security. So to

Bug#786989: xbmc: Eject/Load fails to eject my DVD

>> Have you tried the solution from #709117? > I already have dev.cdrom.lock=0 in my sysctl, yes. > Also, I don't see anything like >19:33:17 T:140173220951968 DEBUG: ExecuteXBMCAction : Translating > EjectTray() >19:33:17 T:140173220951968 DEBUG: ExecuteXBMCAction : To EjectTray() >

Re: Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Saludos Felipe, Am Montag, den 01.06.2015, 12:12 -0300 schrieb Felipe Sateler: > In general I would strongly advise to specify all the flags you want > to enable and have the build system fail if they cannot be enabled. At > the same time, explicitly disable all flags not used in the debian > pac

Bug#786438: libmp3lame0: general protection error in libmp3lame.so.0.0.0

Am Montag, den 01.06.2015, 20:44 +0200 schrieb Bernhard Übelacker: > unfortunately this did not work too (with or without "packed"). Hm, are we missing a specific compiler flag in addition to -msse or are we probably hunting down a compiler bug here? - Fabian signature.asc Description: This i