Re: new version of package 'crtmpserver' was prepared

2012-03-22 Thread Andriy Beregovenko
Hi Andres,

Thank you.

On Wed, Mar 21, 2012 at 09:31:48PM -0400, Andres Mejia wrote:
 2012/3/21 Andriy Beregovenko j...@jet.kiev.ua:
  Hi,
 
  I finished update package 'crtmpserver'.
  This is major update from the point of view of upstream update, but
  debian package changes are insignificant.
 
  So, please, upload updated version of package.
  --
  Best regards,
  Andriy
  0xBDDBDAE3
 
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.4.10 (GNU/Linux)
 
  iQIcBAEBAgAGBQJPalsqAAoJEDajjCG929rjtDwP/1P3zn2r6VyKMA4LIx9h4OK9
  JUyaf67iumAURLoY6Ndl7mxHdUexk8GMI5cTPrGwiQNY4TqzU8BxSoOaBdoWrbPZ
  kfDx5R0yhL3bT8xRRqOSxckV5Qvy/lStn/SyFmUN1WQ5GpMqv8Uss528yiPbuIhg
  jNm45XrzCmPNf9m3jNRtAIkA8YyVxiIFnBEvczXP5e//N8kQ2lmHGF8i8SKJi/gU
  cKiDvbmGYEhJjnHfO7XOOJk5R6YPJMF/Hf3D3q5avkdojUx+zbgJCY6AD5BJzqGM
  AehVHD8QK/YnToP3WGeXwIIVCaO6eVLxSkRzqwvdxJbmyPnYSnlVOm0Vgt3WRxkR
  lY8xtXXwZi24XOVfdWEShYjioMFdwwXPmpRYESjU2g3PpKaKG+NXWhhjjyqqxYfe
  pr6Fb5Pl6lGnxbkVpIL+Mb3n5sOOPvMh+MgJXy6kWuDmgS8ssn2M+/xtRd0jFAaa
  zJYipwSVJYsWj1TsMNC8ptCcDM2l81cLUMwbWSQQpjcUDHMhfOPJ4TPr1Ncz6kPM
  DjqVi1sZoXSBmlxHh1xwWUXDdenZfwFHlD5SmgdkTE3sJhjk1v7y60/J4XOcFv4U
  waXS6kLL2ZcE3tlDEWeznUOqkKMvaY7WogCspMSRyrO2IGAsLRaLzkmyBs6utDNC
  PI/5g3UYIjevkrBa28vL
  =a6DZ
  -END 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
 
 Ok, uploaded.
 
 -- 
 ~ Andres

-- 
Best regards,
Andriy
0xBDDBDAE3


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

Hi! I am Charity!

2012-03-22 Thread charity enoch
Hi! I am Charity!
how are you! hope you are fine and in perfect condition of health. I went
through your profile and i read it and took intersest in it,if you don't
mind i will like you to write me on this ID (charity23en...@ymail.com) hope
to hear from you soon, I will be waiting for your mail because i have
something VERY important to tell you.
Lots of love Charity!


Message sent using enet Mail 1.0.0



___
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: Duplicate Packages from Debian archive in DMO

2012-03-22 Thread Stuart Prescott
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Andres,

 Thanks. This really helps.

glad to be of assistance :)

 I was going to ask, could you do a query on sid showing the source
 packages available in dmo only and in both debian and dmo? I'm still
 waiting on the import of the udd to my system.

The naive answer to this question would turn up source package names that 
are different between the Debian and dmo archives as dmo has been adding -
dmo to source packages to distinguish them from the Debian variant. There 
would also be libav vs ffmpeg differences.

So, I've not actually answered that question directly but instead some 
slightly different ones that I hope are what you really wanted to know:

* What packages are in Debian and dmo that have the same name or have 
-'dmo added to them? (Note that ffmpeg-dmo and xbmc-dmo both exist without 
a non--dmo source package existing in Debian)

* What source packages in dmo are building binary packages with the same 
package names as binary packages in Debian?

* What source packages in dmo are building binary packages that are not in 
Debian?

The third of these questions turns up:

* packages like acroread that I guess will never be in Debian

* various multimedia packages that might one day be in Debian

* variations on multimedia packages that introduce extra binary packages (I 
guess ffmpeg-dmo producing libswresample* and mp4v2-dmo producing mp4-utils 
packages perhaps fall into this category)

* boring soname changes on libraries like x264-dmo producing libx264-122

I suspect that sifting through these different cases probably requires a 
person with knowledge of the Debian packages rather than more SQL.

Results (and SQL) attached. Let me know if there are further queries I can 
help with.

cheers
Stuart

- -- 
Stuart Prescott www.nanoNANOnano.net
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk9rLPgACgkQn+i4zXHF0ait8ACdH1ufHnTR5X9v2GZp5NoMqGkZ
BIMAn04BPp6WB/4tR6Rx/HGnbiXfyyXT
=wYRo
-END PGP SIGNATURE-
## Source packages that are in both archives with same name

  source  | debian_version | dmm_version
--++-
 rar  | 2:4.0.b3-1 | 2.80-2.1
 xvidcore | 2:1.3.2-8  | 3:1.3.2-0.4
 xvidcore | 2:1.3.2-9  | 3:1.3.2-0.4
(3 rows)


## Source packages that are in both archives with a *-dmo variant

source|   debian_version   | dmm_version
--++-
 gpac | 0.4.5+svn3462~dfsg0-1  | 1:0.4.6~svn20120228-0.0
 gstreamer0.10-ffmpeg | 0.10.13-2  | 1:0.10.13-0.2
 icecast2 | 2.3.2-9| 1:2.3.2kh31-0.0
 ices2| 2.0.1-10   | 1:2.0kh60a-0.1
 kdenlive | 0.8.2.1-2  | 1:0.8.2.1-0.0
 lame | 3.99.5+repack1-3   | 1:3.99.5-0.0
 mlt  | 0.7.8-2| 1:0.7.8-0.1
 mp4v2| 1.9.1+svn479~dfsg0-3   | 2:1.9.1-0.9
 mplayer  | 2:1.0~rc4.dfsg1+svn34540-1 | 3:1.0~rc4+svn20120313-0.0
 mplayer2 | 2.0-426-gc32b3ed-2 | 1:2.0~git20120313-0.1
 transcode| 3:1.1.7-2  | 4:1.1.7-0.3
 vlc  | 2.0.0-6| 1:2.0.1-0.0
 x264 | 2:0.120.2171+git01f7a33-3  | 3:0.122.2184+git5c85e0a-0.0
 xine-lib | 1.1.20.1-3 | 1:1.1.20.1-0.1
 xine-lib-1.2 | 1.2.1-1| 1:1.2.1-0.1
(15 rows)



## Source packages in dmo that build binary packages with the same name as 
Debian packages

debian_source |dmm_source|debian_version
 | dmm_version |
package_overlap
--+--+---+-+---
 gpac | gpac-dmo | 0.4.5+svn3462~dfsg0-1
 | 1:0.4.6~svn20120228-0.0 | libgpac-dev,gpac,libgpac1
 gstreamer0.10-ffmpeg | gstreamer0.10-ffmpeg-dmo | 0.10.13-2
 | 1:0.10.13-0.2   | gstreamer0.10-ffmpeg,gstreamer0.10-ffmpeg-dbg
 gtkpod   | gtkpod-aac   | 2.1.1-1  
 | 1:2.1.1-0.1 | libgtkpod-dev,libgtkpod1
 icecast2 | icecast2-dmo | 2.3.2-9  
 | 1:2.3.2kh31-0.0 | icecast2
 ices2| ices2-dmo| 2.0.1-10 
 | 1:2.0kh60a-0.1  | ices2
 kdenlive | kdenlive-dmo   

mudita24 1.0.3+svn13-4 MIGRATED to testing

2012-03-22 Thread Debian testing watch
FYI: The status of the mudita24 source package
in Debian's testing distribution has changed.

  Previous version: 1.0.3+svn13-3
  Current version:  1.0.3+svn13-4

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


Processed: tagging 661605

2012-03-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 661605 + pending fixed-upstream
Bug #661605 [idjc] FTBFS
Added tag(s) fixed-upstream and pending.
 thanks
Stopping processing here.

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


Processing of idjc_0.8.7-2_amd64.changes

2012-03-22 Thread Debian FTP Masters
idjc_0.8.7-2_amd64.changes uploaded successfully to localhost
along with the files:
  idjc_0.8.7-2.dsc
  idjc_0.8.7-2.debian.tar.gz
  idjc_0.8.7-2_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


idjc_0.8.7-2_amd64.changes ACCEPTED into unstable

2012-03-22 Thread Debian FTP Masters



Accepted:
idjc_0.8.7-2.debian.tar.gz
  to main/i/idjc/idjc_0.8.7-2.debian.tar.gz
idjc_0.8.7-2.dsc
  to main/i/idjc/idjc_0.8.7-2.dsc
idjc_0.8.7-2_amd64.deb
  to main/i/idjc/idjc_0.8.7-2_amd64.deb


Changes:
idjc (0.8.7-2) unstable; urgency=low
 .
  * Enable parallel builds.
  * Bump debhelper requirement to 7.4.10.
  * Depends on python-dbus.
  * Depends on python-gobject.
  * Update repackaging mechanism to strip the libshout/ directory.
  * Cherry-pick patch from upstream SCM to fix FTBFS. (Closes: #661605)
Also fixes LP: #935507
  * Update debian/copyright.
  * Bump Standards.


Override entries for your package:
idjc_0.8.7-2.dsc - source sound
idjc_0.8.7-2_amd64.deb - optional sound

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 661605 


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


Bug#661605: marked as done (FTBFS)

2012-03-22 Thread Debian Bug Tracking System
Your message dated Thu, 22 Mar 2012 18:48:13 +
with message-id e1san3v-000407...@franck.debian.org
and subject line Bug#661605: fixed in idjc 0.8.7-2
has caused the Debian Bug report #661605,
regarding FTBFS
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.)


-- 
661605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: idjc
Version: 0.8.7-1
Severity: serious

Your package fails to build from source:

make[3]: Entering directory `/home/jmm/idjc-0.8.7/python'
Making install in prelims
make[4]: Entering directory `/home/jmm/idjc-0.8.7/python/prelims'
make[5]: Entering directory `/home/jmm/idjc-0.8.7/python/prelims'
make[5]: Für das Ziel »install-exec-am« ist nichts zu tun.
test -z /usr/lib/python2.7/dist-packages/idjc/prelims || /bin/mkdir -p 
/home/jmm/idjc-0.8.7/debian/idjc/usr/lib/python2.7/dist-packages/idjc/prelims
 /usr/bin/install -c -m 644 __init__.py profiledialog.py 
'/home/jmm/idjc-0.8.7/debian/idjc/usr/lib/python2.7/dist-packages/idjc/prelims'
Byte-compiling python modules...
__init__.pyprofiledialog.py
Byte-compiling python modules (optimized versions) ...
__init__.pyprofiledialog.py
make[5]: Leaving directory `/home/jmm/idjc-0.8.7/python/prelims'
make[4]: Leaving directory `/home/jmm/idjc-0.8.7/python/prelims'
make[4]: Entering directory `/home/jmm/idjc-0.8.7/python'
make[5]: Entering directory `/home/jmm/idjc-0.8.7/python'
make[5]: Für das Ziel »install-exec-am« ist nichts zu tun.
sed -e 's|${pkgdatadir}|/usr/share/idjc|' -e 's|${exec_prefix}|/usr|' -e 
's|${prefix}|/usr|' __init__.py.in __init__.py
test -z /usr/lib/python2.7/dist-packages/idjc || /bin/mkdir -p 
/home/jmm/idjc-0.8.7/debian/idjc/usr/lib/python2.7/dist-packages/idjc
 /usr/bin/install -c -m 644 __init__.py 
'/home/jmm/idjc-0.8.7/debian/idjc/usr/lib/python2.7/dist-packages/idjc'
/bin/bash: Zeile 15: --destdir: Kommando nicht gefunden.
make[5]: *** [install-nodist_pkgpythonPYTHON] Fehler 127
make[5]: Leaving directory `/home/jmm/idjc-0.8.7/python'
make[4]: *** [install-am] Fehler 2
make[4]: Leaving directory `/home/jmm/idjc-0.8.7/python'
make[3]: *** [install-recursive] Fehler 1
make[3]: Leaving directory `/home/jmm/idjc-0.8.7/python'
make[2]: *** [install-recursive] Fehler 1
make[2]: Leaving directory `/home/jmm/idjc-0.8.7'
dh_auto_install: make -j1 install DESTDIR=/home/jmm/idjc-0.8.7/debian/idjc 
returned exit code 2
make[1]: *** [override_dh_auto_install] Fehler 29
make[1]: Leaving directory `/home/jmm/idjc-0.8.7'
make: *** [binary] Fehler 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von fakeroot debian/rules binary 
war 2


---End Message---
---BeginMessage---
Source: idjc
Source-Version: 0.8.7-2

We believe that the bug you reported is fixed in the latest version of
idjc, which is due to be installed in the Debian FTP archive:

idjc_0.8.7-2.debian.tar.gz
  to main/i/idjc/idjc_0.8.7-2.debian.tar.gz
idjc_0.8.7-2.dsc
  to main/i/idjc/idjc_0.8.7-2.dsc
idjc_0.8.7-2_amd64.deb
  to main/i/idjc/idjc_0.8.7-2_amd64.deb



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 661...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessio Treglia ales...@debian.org (supplier of updated idjc 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 22 Mar 2012 19:31:31 +0100
Source: idjc
Binary: idjc
Architecture: source amd64
Version: 0.8.7-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintainers@lists.alioth.debian.org
Changed-By: Alessio Treglia ales...@debian.org
Description: 
 idjc   - graphical shoutcast/icecast client
Closes: 661605
Changes: 
 idjc (0.8.7-2) unstable; urgency=low
 .
   * Enable parallel builds.
   * Bump debhelper requirement to 7.4.10.
   * Depends on python-dbus.
   * Depends on python-gobject.
   * Update repackaging mechanism to strip the libshout/ directory.
   * Cherry-pick patch from upstream SCM to fix FTBFS. (Closes: #661605)
 Also fixes LP: #935507
   * Update debian/copyright.
   * Bump Standards.
Checksums-Sha1: 
 dc6321fb7d5fd92d1fdc7089f7a3e6f2de23f204  idjc_0.8.7-2.dsc
 db619118fe350866ef462e58afec3dbff8e6d7e6 9347 idjc_0.8.7-2.debian.tar.gz
 

Re: d-m.o dependency tree

2012-03-22 Thread Andres Mejia
2012/2/10 Fabian Greffrath fab...@greffrath.com:
 Am 09.02.2012 16:49, schrieb Sebastian Dröge:

 Not obsoleted (yet). faac supports 1-6 channels and the main, lc, ssr
 and ltp profiles. vo-aacenc only supports 1-2 channels and the lc
 profile.


 OK, so it's good enough for the usual CD ripping.

 The current gnome-media-profiles still uses the faac plugin, right?


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

Whatever became of this? Should faac be uploaded to non-free at least for now?

-- 
~ Andres

___
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: Duplicate Packages from Debian archive in DMO

2012-03-22 Thread Andres Mejia
On Mar 22, 2012 11:29 AM, Christian Marillat maril...@free.fr wrote:

 Andres Mejia amejia...@gmail.com writes:

  On Mar 21, 2012 2:26 AM, Christian Marillat maril...@free.fr wrote:
 
  Andres Mejia amejia...@gmail.com writes:

 [...]

  Also I upload my packages more quickly than Debian. 3.99.0, 3.99.1
  3.99.2 lame version have never been packaged by Debian.
 
  Ok. Why not directly upload these packages to Debian then? You are still a 
  Debian
  developer right?
 
  In case you didn't know, I'm part of the team packaging multimedia related 
  software
  for Debian. I'm also a DD. I help maintain lame, x264, and a list of other 
  packages
  in Debian.
 
  I could use help in keeping lame and other packages up to date. I don't 
  have time to
  upload new releases right when they're released. Would you be willing to 
  help
  maintain packages in Debian?

 This isn't possible to change the soname library monthly because the
 release team will probably reject monthly new soname.

 Also a new soname mean to rebuild all package who depends on the new
 soname library because the old soname packages are removed in Debian.

We request library transitions in this case. Usually, the release team
grants us these requests within a reasonable time frame.

 Here, I can keep more than one soname library.

 A nice example is Debian released a new -120 package the same day I did
 a -124 package.

For x264, we're tracking the stable branch, currently at commit
01f7a33... You must be tracking master. In any case, Debian has
experimental for these cases (providing a stable library package and
an experimental one). You could be helping maintain x264 via unstable
and experimental.

 [...]

  Also some pakcages like vlc or xine are in my repository because Debian
  added a conflicts against libavutil51 from my repository.

 [...]

  I looked at the packaging for vlc and xine-lib. I don't see a place where a
  conflicts to any libav/ffmpeg libraries was added.

 ,
 | $ apt-cache show libpostproc52
 | Package: libpostproc52
 | Source: libav
 | Version: 4:0.8.1-1
 | Installed-Size: 403
 | Maintainer: Debian Multimedia Maintainers 
 pkg-multimedia-maintainers@lists.alioth.debian.org
 | Architecture: i386
 | Depends: libavutil51 (= 4:0.8.1-1) | libavutil-extra-51 (= 4:0.8.1), 
 libavutil51 ( 4:0.8.1-99) | libavutil-extra-51 ( 4:0.8.1.99), libc6 (= 
 2.4)
 `

 Could you explain the libavutil51 ( 4:0.8.1-99) | libavutil-extra-51 ( 
 4:0.8.1.99)
  in Depends field ?

You're looking at the strict dependencies set only for the libav
packages. The shlibs is generated again so that the Depends field
above does not apply to any packages depending on the libav libraries.
See vlc for example.

$ apt-cache show vlc
Package: vlc
Version: 2.0.0-6
Installed-Size: 3459
Maintainer: Debian Multimedia Maintainers
pkg-multimedia-maintainers@lists.alioth.debian.org
Architecture: amd64
Replaces: vlc-nox ( 1.1.5-1)
Provides: mp3-decoder
Depends: ttf-freefont, vlc-nox (= 2.0.0-6), libaa1 (= 1.4p5),
libavcodec53 (= 4:0.8-1~) | libavcodec-extra-53 (= 4:0.8-1~),
libavutil51 (= 4:0.8-1~) | libavutil-extra-51 (= 4:0.8-1~), libc6
(= 2.8), libfreetype6 (= 2.2.1), libfribidi0 (= 0.19.2), libgcc1
(= 1:4.1.1), libgl1-mesa-glx | libgl1, libice6 (= 1:1.0.0),
libqtcore4 (= 4:4.7.0~beta1), libqtgui4 (= 4:4.7.0~beta1),
libsdl-image1.2 (= 1.2.10), libsdl1.2debian (= 1.2.11), libsm6,
libstdc++6 (= 4.6), libtar0, libva-x11-1 ( 1.0.14~), libva1 (
1.0.14~), libvlccore5 (= 2.0.0), libx11-6, libxcb-composite0,
libxcb-keysyms1 (= 0.3.8), libxcb-randr0 (= 1.1), libxcb-render0,
libxcb-shape0, libxcb-shm0, libxcb-xfixes0, libxcb-xv0 (= 1.2),
libxcb1 (= 1.6), libxext6, libxinerama1, libxpm4, zlib1g (=
1:1.2.3.3)
Recommends: vlc-plugin-notify (= 2.0.0-6), vlc-plugin-pulse (=
2.0.0-6), xdg-utils
Suggests: videolan-doc
Breaks: vlc-nox ( 1.1.5-1)
Description-en: multimedia player and streamer
---

  Speaking of libav/ffmpeg, the Debian archive has libav and not ffmpeg. I 
  see that
  DMO is the reverse, shipping ffmpeg instead of libav. This of course 
  resulted in
  many breakages between packages in Debian and packages in DMO.

 Which breakage ? Tell me what is exactly broken.

Here are some of the more recent reported problems with using dmo.

1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663893
2. http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-March/025352.html
# read the quoted message
3. http://lists.debian.org/debian-devel/2012/03/msg00129.html

About 2 and 3, I can personally attest that this kind of breakage with
using dmo does happen. Years ago when I first switched to Debian, I
too thought that using dmo would be alright, seeing that it should
only provide missing codecs and other software not available in Debian
at the time. Long story short, after certain packages were upgraded
because of dmo being activated on my system, I was left with numerous
package conflicts and a missing desktop environment (in my case, kde).
It was 

Bug#665323: crtmpserver: CPPFLAGS hardening flags missing

2012-03-22 Thread Simon Ruderich
Package: crtmpserver
Version: 1.0~dfsg-1
Severity: important
Tags: patch

Dear Maintainer,

The CPPFLAGS hardening flags are missing because CMake ignores
them by default.

The following patch fixes the issue by adding them to
CFLAGS/CXXFLAGS. For more hardening information please have a
look at [1], [2] and [3].

The -O2 removal is not necessary as gcc uses the last flag, which
is -O3 as set by CMake. compat=9 automatically exports the flags
so it's not necessary to pass them configure manually.

diff -Nru crtmpserver-1.0~dfsg/debian/rules crtmpserver-1.0~dfsg/debian/rules
--- crtmpserver-1.0~dfsg/debian/rules   2012-03-22 01:52:51.0 +0100
+++ crtmpserver-1.0~dfsg/debian/rules   2012-03-23 02:53:16.0 +0100
@@ -2,16 +2,17 @@
 
 #export DH_VERBOSE=1
 
-CFLAGS = $(shell dpkg-buildflags --get CFLAGS 2/dev/null | sed -e 's/-O2//g')
-CXXFLAGS = $(shell dpkg-buildflags --get CXXFLAGS 2/dev/null | sed -e 
's/-O2//g')
+# CMake doesn't use CPPFLAGS, pass them to CFLAGS/CXXFLAGS to enable the
+# missing (hardening) flags.
+export DEB_CFLAGS_MAINT_APPEND   = $(shell dpkg-buildflags --get CPPFLAGS)
+export DEB_CXXFLAGS_MAINT_APPEND = $(shell dpkg-buildflags --get CPPFLAGS)
+
 DEB_BUILDDIR = obj-$(DEB_BUILD_GNU_TYPE)
 DEB_PACKAGE_VERSION  := $(shell dpkg-parsechangelog | awk '/^Version/ {print 
$$2}')
 DEB_UPSTREAM_VERSION := $(shell echo $(DEB_PACKAGE_VERSION) | cut -d '-' -f 1 
| sed s,~,_, )
 DEB_CONFIGURE_FLAGS = \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_VERBOSE_MAKEFILE=ON \
-   -DCMAKE_C_FLAGS=$(CFLAGS) \
-   -DCMAKE_CXX_FLAGS=$(CXXFLAGS) \
-DCRTMPSERVER_INSTALL_PREFIX=/usr \
-DTEMP_FRAMEWORK_VER=$(DEB_UPSTREAM_VERSION) \
-DCRTMPSERVER_SOURCES_ROOT=$(CURDIR) \

To check if all flags were correctly enabled you can use
`hardening-check` from the hardening-includes package and check
the build log (hardening-check doesn't catch everything):

$ hardening-check /usr/sbin/crtmpserver /usr/lib/crtmpserver/libthelib.so 
/usr/lib/crtmpserver/libcommon.so ...
/usr/sbin/crtmpserver:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: unknown, no protectable libc functions used
 Read-only relocations: yes
 Immediate binding: no not found!
/usr/lib/crtmpserver/libthelib.so:
 Position Independent Executable: no, regular shared library (ignored)
 Stack protected: yes
 Fortify Source functions: no, only unprotected functions found!
 Read-only relocations: yes
 Immediate binding: no not found!
/usr/lib/crtmpserver/libcommon.so:
 Position Independent Executable: no, regular shared library (ignored)
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no not found!
...

(Position Independent Executable and Immediate binding is not
enabled by default.)

Use find -type f \( -executable -o -name \*.so\* \) -exec
hardening-check {} + on the build result to check all files.

Regards,
Simon

[1]: https://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags
[2]: https://wiki.debian.org/HardeningWalkthrough
[3]: https://wiki.debian.org/Hardening
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


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

Processing of faac_1.28-4_amd64.changes

2012-03-22 Thread Debian FTP Masters
faac_1.28-4_amd64.changes uploaded successfully to localhost
along with the files:
  faac_1.28-4.dsc
  faac_1.28.orig.tar.gz
  faac_1.28-4.debian.tar.gz
  faac_1.28-4_amd64.deb
  libfaac0_1.28-4_amd64.deb
  libfaac-dev_1.28-4_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 crtmpserver_1.0~dfsg-2_amd64.changes

2012-03-22 Thread Debian FTP Masters
crtmpserver_1.0~dfsg-2_amd64.changes uploaded successfully to localhost
along with the files:
  crtmpserver_1.0~dfsg-2.dsc
  crtmpserver_1.0~dfsg-2.debian.tar.gz
  crtmpserver_1.0~dfsg-2_amd64.deb
  crtmpserver-libs_1.0~dfsg-2_amd64.deb
  crtmpserver-apps_1.0~dfsg-2_amd64.deb
  crtmpserver-dev_1.0~dfsg-2_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


crtmpserver_1.0~dfsg-2_amd64.changes ACCEPTED into unstable

2012-03-22 Thread Debian FTP Masters



Accepted:
crtmpserver-apps_1.0~dfsg-2_amd64.deb
  to main/c/crtmpserver/crtmpserver-apps_1.0~dfsg-2_amd64.deb
crtmpserver-dev_1.0~dfsg-2_amd64.deb
  to main/c/crtmpserver/crtmpserver-dev_1.0~dfsg-2_amd64.deb
crtmpserver-libs_1.0~dfsg-2_amd64.deb
  to main/c/crtmpserver/crtmpserver-libs_1.0~dfsg-2_amd64.deb
crtmpserver_1.0~dfsg-2.debian.tar.gz
  to main/c/crtmpserver/crtmpserver_1.0~dfsg-2.debian.tar.gz
crtmpserver_1.0~dfsg-2.dsc
  to main/c/crtmpserver/crtmpserver_1.0~dfsg-2.dsc
crtmpserver_1.0~dfsg-2_amd64.deb
  to main/c/crtmpserver/crtmpserver_1.0~dfsg-2_amd64.deb


Changes:
crtmpserver (1.0~dfsg-2) unstable; urgency=low
 .
  * Enable hardened CPPFLAGS. (Closes: #665323)
  * Add myself to Uploaders field.


Override entries for your package:
crtmpserver-apps_1.0~dfsg-2_amd64.deb - optional video
crtmpserver-dev_1.0~dfsg-2_amd64.deb - optional video
crtmpserver-libs_1.0~dfsg-2_amd64.deb - optional video
crtmpserver_1.0~dfsg-2.dsc - source video
crtmpserver_1.0~dfsg-2_amd64.deb - optional video

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 665323 


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


Bug#665323: marked as done (crtmpserver: CPPFLAGS hardening flags missing)

2012-03-22 Thread Debian Bug Tracking System
Your message dated Fri, 23 Mar 2012 02:47:21 +
with message-id e1sauxb-0006qs...@franck.debian.org
and subject line Bug#665323: fixed in crtmpserver 1.0~dfsg-2
has caused the Debian Bug report #665323,
regarding crtmpserver: CPPFLAGS hardening flags missing
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.)


-- 
665323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: crtmpserver
Version: 1.0~dfsg-1
Severity: important
Tags: patch

Dear Maintainer,

The CPPFLAGS hardening flags are missing because CMake ignores
them by default.

The following patch fixes the issue by adding them to
CFLAGS/CXXFLAGS. For more hardening information please have a
look at [1], [2] and [3].

The -O2 removal is not necessary as gcc uses the last flag, which
is -O3 as set by CMake. compat=9 automatically exports the flags
so it's not necessary to pass them configure manually.

diff -Nru crtmpserver-1.0~dfsg/debian/rules crtmpserver-1.0~dfsg/debian/rules
--- crtmpserver-1.0~dfsg/debian/rules   2012-03-22 01:52:51.0 +0100
+++ crtmpserver-1.0~dfsg/debian/rules   2012-03-23 02:53:16.0 +0100
@@ -2,16 +2,17 @@
 
 #export DH_VERBOSE=1
 
-CFLAGS = $(shell dpkg-buildflags --get CFLAGS 2/dev/null | sed -e 's/-O2//g')
-CXXFLAGS = $(shell dpkg-buildflags --get CXXFLAGS 2/dev/null | sed -e 
's/-O2//g')
+# CMake doesn't use CPPFLAGS, pass them to CFLAGS/CXXFLAGS to enable the
+# missing (hardening) flags.
+export DEB_CFLAGS_MAINT_APPEND   = $(shell dpkg-buildflags --get CPPFLAGS)
+export DEB_CXXFLAGS_MAINT_APPEND = $(shell dpkg-buildflags --get CPPFLAGS)
+
 DEB_BUILDDIR = obj-$(DEB_BUILD_GNU_TYPE)
 DEB_PACKAGE_VERSION  := $(shell dpkg-parsechangelog | awk '/^Version/ {print 
$$2}')
 DEB_UPSTREAM_VERSION := $(shell echo $(DEB_PACKAGE_VERSION) | cut -d '-' -f 1 
| sed s,~,_, )
 DEB_CONFIGURE_FLAGS = \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_VERBOSE_MAKEFILE=ON \
-   -DCMAKE_C_FLAGS=$(CFLAGS) \
-   -DCMAKE_CXX_FLAGS=$(CXXFLAGS) \
-DCRTMPSERVER_INSTALL_PREFIX=/usr \
-DTEMP_FRAMEWORK_VER=$(DEB_UPSTREAM_VERSION) \
-DCRTMPSERVER_SOURCES_ROOT=$(CURDIR) \

To check if all flags were correctly enabled you can use
`hardening-check` from the hardening-includes package and check
the build log (hardening-check doesn't catch everything):

$ hardening-check /usr/sbin/crtmpserver /usr/lib/crtmpserver/libthelib.so 
/usr/lib/crtmpserver/libcommon.so ...
/usr/sbin/crtmpserver:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: unknown, no protectable libc functions used
 Read-only relocations: yes
 Immediate binding: no not found!
/usr/lib/crtmpserver/libthelib.so:
 Position Independent Executable: no, regular shared library (ignored)
 Stack protected: yes
 Fortify Source functions: no, only unprotected functions found!
 Read-only relocations: yes
 Immediate binding: no not found!
/usr/lib/crtmpserver/libcommon.so:
 Position Independent Executable: no, regular shared library (ignored)
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no not found!
...

(Position Independent Executable and Immediate binding is not
enabled by default.)

Use find -type f \( -executable -o -name \*.so\* \) -exec
hardening-check {} + on the build result to check all files.

Regards,
Simon

[1]: https://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags
[2]: https://wiki.debian.org/HardeningWalkthrough
[3]: https://wiki.debian.org/Hardening
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: crtmpserver
Source-Version: 1.0~dfsg-2

We believe that the bug you reported is fixed in the latest version of
crtmpserver, which is due to be installed in the Debian FTP archive:

crtmpserver-apps_1.0~dfsg-2_amd64.deb
  to main/c/crtmpserver/crtmpserver-apps_1.0~dfsg-2_amd64.deb
crtmpserver-dev_1.0~dfsg-2_amd64.deb
  to main/c/crtmpserver/crtmpserver-dev_1.0~dfsg-2_amd64.deb
crtmpserver-libs_1.0~dfsg-2_amd64.deb
  to main/c/crtmpserver/crtmpserver-libs_1.0~dfsg-2_amd64.deb
crtmpserver_1.0~dfsg-2.debian.tar.gz
  to main/c/crtmpserver/crtmpserver_1.0~dfsg-2.debian.tar.gz
crtmpserver_1.0~dfsg-2.dsc
  

Re: Duplicate Packages from Debian archive in DMO

2012-03-22 Thread Andres Mejia
On Thu, Mar 22, 2012 at 9:45 AM, Stuart Prescott
stu...@nanonanonano.net wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi Andres,

 Thanks. This really helps.

 glad to be of assistance :)

 I was going to ask, could you do a query on sid showing the source
 packages available in dmo only and in both debian and dmo? I'm still
 waiting on the import of the udd to my system.

 The naive answer to this question would turn up source package names that
 are different between the Debian and dmo archives as dmo has been adding -
 dmo to source packages to distinguish them from the Debian variant. There
 would also be libav vs ffmpeg differences.

 So, I've not actually answered that question directly but instead some
 slightly different ones that I hope are what you really wanted to know:

 * What packages are in Debian and dmo that have the same name or have
 -'dmo added to them? (Note that ffmpeg-dmo and xbmc-dmo both exist without
 a non--dmo source package existing in Debian)

Yes, this is what I wanted to know.

 * What source packages in dmo are building binary packages with the same
 package names as binary packages in Debian?

 * What source packages in dmo are building binary packages that are not in
 Debian?

 The third of these questions turns up:

 * packages like acroread that I guess will never be in Debian

 * various multimedia packages that might one day be in Debian

 * variations on multimedia packages that introduce extra binary packages (I
 guess ffmpeg-dmo producing libswresample* and mp4v2-dmo producing mp4-utils
 packages perhaps fall into this category)

 * boring soname changes on libraries like x264-dmo producing libx264-122

 I suspect that sifting through these different cases probably requires a
 person with knowledge of the Debian packages rather than more SQL.

 Results (and SQL) attached. Let me know if there are further queries I can
 help with.

 cheers
 Stuart

Thank you.

 - --
 Stuart Prescott                 www.nanoNANOnano.net
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)

 iEYEARECAAYFAk9rLPgACgkQn+i4zXHF0ait8ACdH1ufHnTR5X9v2GZp5NoMqGkZ
 BIMAn04BPp6WB/4tR6Rx/HGnbiXfyyXT
 =wYRo
 -END 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



-- 
~ Andres

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