Bug#682472: unblock: mandos/1.6.0-1

[Teddy Hogeborn]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock


Please unblock package mandos

We released Mandos version 1.6.0 well in advance of the anticipated
Debian freeze, and have been using it ourselves since then, but our
sponsor did not upload it with his usual promptness.  This release has
a very nice labor-saving autodetection feature for the client side
(clients most likely won't need any configuration anymore), and no
other incompatible changes since 1.5.5, but many packaging fixes.
Also, our popcon count is rather low: 11 for mandos and 14 for
mandos-client, and about half of those are our own systems.

Could you *please* consider including this release in wheezy?  We, the
upstream and uploaders of Mandos, feel that we did everything we could
for 1.6.0 to be included in wheezy, and that we are the victims of
circumstances outside our control (viz. that our sponsor, Daniel
Baumann, was late uploading it because of his being traveling due to
Debconf).

This configuration-less client feature is our last nice feature we
once dreamed of being able to provide for our users; future releases
of the package will consist mainly of minor polish to other parts, but
no features are missing.  Please make our dream come true?

unblock mandos/1.6.0-1

-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-bpo.2-amd64 (SMP w/16 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120723064408.8124.44774.report...@tower.recompile.se

Bug#681788: unblock: ace-of-penguins/1.3-10

[jaalto]

On 2012-07-21 19:29, Julien Cristau wrote:
| On Sat, Jul 21, 2012 at 20:00:38 +0300, jaalto wrote:
| 
| > On 2012-07-21 12:39, Julien Cristau wrote:
| > | On Mon, Jul 16, 2012 at 18:47:14 +0300, Jari Aalto wrote:
| > | 
| > | >Add required font package to debian/control::Recommends
| > | > 
| > | Making the software deal sanely with a missing font (where "SIGSEGV"
| > | doesn't count as "sane") is not an option?
| > 
| > The policy says that font packages are not allowed to be listed in
| > debian/control::Depends. If this is permissable to be overridden, I
| > can move it from Recommends to Depends.
| > 
| That's not what I meant.

Given the release time frame, upstream probably is unable to provide
updates on this at code level.

To improve it for release, I'm wondering if it would be more sensible
to play it safe and use:

 debian/controll::Depends

Currenly the measures in 1.3-10 are the ones that are allowed by
policy.

Jari

signature.asc
Description: Digital signature

Re: torcs and torcs-data-*

[Adam D. Barratt]

On Sun, 2012-07-22 at 23:58 -0500, Rudy Godoy wrote:
> Hello, past May torcs-data (1.3.1) was removed from testing 
> automatically. This could probably happened due one RC bug 
> sitting on BTS.

No, it was removed because it no longer produced any binaries
(specifically they've all been taken over by other source packages).
This can be seen by the excuses listing:

* torcs-data has no binaries on any arch

> Since then I've been reworking the packaging bit and improving
> them. By now there's a new upstream version of torcs (1.3.3),
> binaries, already in sid. However the corresponding -data-* 
> packages have never entered testing again.

The source packages haven't, no, but the binaries are now produced by
the "torcs" source package.  As the package maintainer, I'd expect that
you'd know this.  :-)

> So, I ask for allowing torcs-data, torcs-data-tracks and
> torcs-data-cars to enter testing, thus being part of 
> wheezy.
> 
> Changes from 1.3.1 to 1.3.3 include few build bugs and
> upstream including our patches.

$ dak ls -s testing torcs-data-{cars,tracks}
torcs-data-cars |1.3.3-4 |   testing | all
torcs-data-tracks |1.3.3-4 |   testing | all

I'm not sure what you believe needs doing here.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1343020701.13223.196.ca...@jacala.jungle.funky-badger.org

Bug#682468: unblock: python-colorama/0.2.4-1.1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-colorama

Fixes RC bug #681584

unblock python-colorama/0.2.4-1.1
diff -Nru python-colorama-0.2.4/debian/changelog python-colorama-0.2.4/debian/changelog
--- python-colorama-0.2.4/debian/changelog	2012-03-06 13:17:39.0 -0500
+++ python-colorama-0.2.4/debian/changelog	2012-07-23 01:02:44.0 -0400
@@ -1,3 +1,13 @@
+python-colorama (0.2.4-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use dh_python2.
+Build-Depend on python (>= 2.6.6-3~) for that.
+Add python:Depends to Depends.
+Closes: #681584
+
+ -- Evgeni Golov   Tue, 17 Jul 2012 08:52:08 +0200
+
 python-colorama (0.2.4-1) unstable; urgency=low
 
   * Initial release (Closes: #662761)
diff -Nru python-colorama-0.2.4/debian/control python-colorama-0.2.4/debian/control
--- python-colorama-0.2.4/debian/control	2012-03-06 13:17:39.0 -0500
+++ python-colorama-0.2.4/debian/control	2012-07-23 01:01:55.0 -0400
@@ -2,7 +2,7 @@
 Section: python
 Priority: optional
 Maintainer: Khalid El Fathi 
-Build-Depends: debhelper (>= 9.0.0), python
+Build-Depends: debhelper (>= 9.0.0), python (>= 2.6.6-3~)
 Standards-Version: 3.9.3
 Homepage: http://pypi.python.org/pypi/colorama/
 Vcs-Git: git://git.debian.org/collab-maint/python-colorama.git
@@ -11,7 +11,7 @@
 
 Package: python-colorama
 Architecture: all
-Depends: ${misc:Depends}
+Depends: ${python:Depends}, ${misc:Depends}
 Description: Cross-platform colored terminal text in Python
  Python-colorama provides a simple cross-platform API to print colored terminal
  text from Python applications.
diff -Nru python-colorama-0.2.4/debian/rules python-colorama-0.2.4/debian/rules
--- python-colorama-0.2.4/debian/rules	2012-03-06 13:17:39.0 -0500
+++ python-colorama-0.2.4/debian/rules	2012-07-23 01:01:55.0 -0400
@@ -2,7 +2,7 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@ 
+	dh $@ --with=python2
 
 override_dh_installexamples:
 	cp -r $(CURDIR)/demos/* $(CURDIR)/debian/python-colorama/usr/share/doc/python-colorama/examples/

Bug#682467: unblock: blist/1.3.4-2

[Scott Kitterman]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package blist

Fixed RC bug #681583

unblock blist/1.3.4-2
diff -ruN export/debian/changelog blist-1.3.4/debian/changelog
--- export/debian/changelog	2012-07-23 00:29:25.089477000 -0400
+++ blist-1.3.4/debian/changelog	2012-07-23 00:45:37.229289894 -0400
@@ -1,3 +1,20 @@
+blist (1.3.4-2) unstable; urgency=low
+
+  * Team upload
+
+  [ Evgeni Golov ]
+  * Non-maintainer upload.
+  * Use dh_python2.
+  * Add python-all-dev to Build-Depends.
+  * Add python:Depends to Depends.
+  * This all closes: #681583
+
+  [ Scott Kitterman ]
+  * Add python-setuptools to Build-Depends
+  * Add missing Vcs-* to Control
+
+ -- Scott Kitterman   Mon, 23 Jul 2012 00:40:43 -0400
+
 blist (1.3.4-1) unstable; urgency=low
 
   * Initial release.
diff -ruN export/debian/control blist-1.3.4/debian/control
--- export/debian/control	2012-07-23 00:29:25.089477000 -0400
+++ blist-1.3.4/debian/control	2012-07-23 00:45:10.533290680 -0400
@@ -5,15 +5,18 @@
 Uploaders:
  Michael Gilbert 
 Build-Depends:
- debhelper (>= 9)
+ debhelper (>= 9), python-all-dev (>= 2.6.6-3~), python-setuptools
 Standards-Version: 3.9.3
 Homepage: http://pypi.python.org/pypi/blist
+Vcs-Svn: svn://svn.debian.org/python-modules/packages/blist/trunk
+Vcs-Browser: http://svn.debian.org/viewsvn/python-modules/packages/blist/trunk/
 
 Package: python-blist
 Architecture: any
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
+ ${python:Depends}
 Description: List-like type for python with better asymptotic performance
  This package is a drop-in replacement for the Python list the provides better
  performance when modifying large lists. The blist package also provides
diff -ruN export/debian/rules blist-1.3.4/debian/rules
--- export/debian/rules	2012-07-23 00:29:25.089477000 -0400
+++ blist-1.3.4/debian/rules	2012-07-23 00:42:46.077294949 -0400
@@ -9,4 +9,4 @@
 	dh_clean
 
 %:
-	dh $@ 
+	dh $@ --with=python2

torcs and torcs-data-*

[Rudy Godoy]

Hello, past May torcs-data (1.3.1) was removed from testing 
automatically. This could probably happened due one RC bug 
sitting on BTS.

Since then I've been reworking the packaging bit and improving
them. By now there's a new upstream version of torcs (1.3.3),
binaries, already in sid. However the corresponding -data-* 
packages have never entered testing again. Those files are 
required to properly play the game. There are few changes 
since 1.3.1 on the data file, so that you can play the game 
using older -data files. However it suits better to have the
corresponding files.

So, I ask for allowing torcs-data, torcs-data-tracks and
torcs-data-cars to enter testing, thus being part of 
wheezy.

Changes from 1.3.1 to 1.3.3 include few build bugs and
upstream including our patches.

Changes on packaging revisions are basically rework  
and better visibility for artwork's licensing

Thanks.

ps: Please CCme since I'm not subcribed to the list.

-- 
Rudy Godoy
http://stone-head.org


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120723045819.ga2...@silverlight.stone-head.org

Bug#682465: unblock: cmtk/2.2.2-2

[Yaroslav Halchenko]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Please unblock package cmtk

Upstream reported that users reported missing some binaries which were
referenced in a recent paper describing methodologies implemented in cmtk.  The
reason was missing build depends on libfftw3-dev.  -2 revision of the package
just adds those build-depends and adds an explicit cmake option to build with
support for libfftw3 functionality.  As debdiff shows there are additional
patches under debian/patches -- but those are applied only when building
backports for NeuroDebian repository.  I am also attaching debdiff on the
.changes to show now added missing binaries.

unblock cmtk/2.2.2-2

Thanks in advance

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .changes but not in first
-
-rw-r--r--  root/root   /usr/share/doc/cmtk/upstream
-rw-r--r--  root/root   /usr/share/man/man1/cmtk-detect_adni_phantom.1.gz
-rw-r--r--  root/root   
/usr/share/man/man1/cmtk-detect_spheres_matched_filter.1.gz
-rwxr-xr-x  root/root   /usr/lib/cmtk/bin/detect_adni_phantom
-rwxr-xr-x  root/root   /usr/lib/cmtk/bin/detect_spheres_matched_filter

Control files: lines which differ (wdiff format)

Depends: libbz2-1.0, libc6 (>= 2.7), libcharls1, libdcmtk2 (>= 3.6.0), 
{+libfftw3-3,+} libgcc1 (>= 1:4.1.1), libgomp1 (>= 4.2.1), libmxml1, libpng12-0 
(>= 1.2.13-4), libqtcore4 (>= 4:4.6.1), libqtgui4 (>= 4:4.5.3), libsqlite3-0 
(>= 3.5.9), libstdc++6 (>= 4.6), libtiff4 (>> 3.9.5-3~), zlib1g (>= 1:1.1.4)
Installed-Size: [-22969-] {+23343+}
Version: [-2.2.2-1-] {+2.2.2-2+}
diff -Nru cmtk-2.2.2/debian/changelog cmtk-2.2.2/debian/changelog
--- cmtk-2.2.2/debian/changelog	2012-06-18 16:01:56.0 -0400
+++ cmtk-2.2.2/debian/changelog	2012-07-20 09:47:02.0 -0400
@@ -1,3 +1,14 @@
+cmtk (2.2.2-2) unstable; urgency=low
+
+  * Adding libfftw3-dev into build-depends and adding
+CMTK_USE_FFTW:BOOL=ON for cmake.  Should make detect_adni_phantom
+referenced in a publication available.
+- for backports to older releases (e.g. squeeze) compatibility patch
+  up_compat_older_fftw is provided and added to corresponding series
+  * Added debian/upstream with a publication reference (added to debian/docs)
+
+ -- Yaroslav Halchenko   Wed, 18 Jul 2012 13:03:08 -0400
+
 cmtk (2.2.2-1) unstable; urgency=low
 
   * Fresh upstream release
diff -Nru cmtk-2.2.2/debian/control cmtk-2.2.2/debian/control
--- cmtk-2.2.2/debian/control	2012-06-18 16:01:56.0 -0400
+++ cmtk-2.2.2/debian/control	2012-07-20 09:47:02.0 -0400
@@ -10,6 +10,7 @@
zlib1g-dev | libz-dev,
libdcmtk2-dev | libdcmtk1-dev | libdcmtk-dev,
libbz2-dev,
+   libfftw3-dev,
liblzma-dev,
libqt4-dev, qt4-qmake,
libpng-dev,
diff -Nru cmtk-2.2.2/debian/docs cmtk-2.2.2/debian/docs
--- cmtk-2.2.2/debian/docs	2012-06-18 16:01:56.0 -0400
+++ cmtk-2.2.2/debian/docs	2012-07-20 09:47:02.0 -0400
@@ -1 +1,2 @@
 README.txt
+debian/upstream
diff -Nru cmtk-2.2.2/debian/patches/series-lucid cmtk-2.2.2/debian/patches/series-lucid
--- cmtk-2.2.2/debian/patches/series-lucid	1969-12-31 19:00:00.0 -0500
+++ cmtk-2.2.2/debian/patches/series-lucid	2012-07-20 09:47:02.0 -0400
@@ -0,0 +1 @@
+up_compat_older_fftw
diff -Nru cmtk-2.2.2/debian/patches/series-maverick cmtk-2.2.2/debian/patches/series-maverick
--- cmtk-2.2.2/debian/patches/series-maverick	1969-12-31 19:00:00.0 -0500
+++ cmtk-2.2.2/debian/patches/series-maverick	2012-07-20 09:47:02.0 -0400
@@ -0,0 +1 @@
+up_compat_older_fftw
diff -Nru cmtk-2.2.2/debian/patches/series-natty cmtk-2.2.2/debian/patches/series-natty
--- cmtk-2.2.2/debian/patches/series-natty	2012-06-18 16:01:56.0 -0400
+++ cmtk-2.2.2/debian/patches/series-natty	2012-07-20 09:47:02.0 -0400
@@ -1 +1,2 @@
 deb_noCharLS
+up_compat_older_fftw
diff -Nru cmtk-2.2.2/debian/patches/series-oneiric cmtk-2.2.2/debian/patches/series-oneiric
--- cmtk-2.2.2/debian/patches/series-oneiric	2012-06-18 16:01:56.0 -0400
+++ cmtk-2.2.2/debian/patches/series-oneiric	2012-07-20 09:47:02.0 -0400
@@ -1 +1,2 @@
 deb_noCharLS
+up_compat_older_fftw
diff -Nru cmtk-2.2.2/debian/patches/series-squeeze cmtk-2.2.2/debian/patches/series-squeeze
--- cmtk-2.2.2/debian/patches/series-squeeze	1969-12-31 19:00:00.0 -0500
+++ cmtk-2.2.2/debian/patches

Bug#682268: unblock: foremost/1.5.7-4

[Aron Xu]

On Mon, Jul 23, 2012 at 5:35 AM, Adam D. Barratt
 wrote:
> tags 682268 + moreinfo
> thanks
>
> On Sat, 2012-07-21 at 04:28 +0800, Aron Xu wrote:
>> Please unblock the package foremost.
>>
>> The updated version fixed the build on kfreebsd-* (1.5.7-3) and hurd
>> (1.5.7-4). It would be great to have one more software ported to those
>> platform by making simple build system changes.
>
> Wheezy won't include hurd, so having the package built there isn't
> really relevant for an unblock.
>

Sure, it's just a bonus, I guess :)

> Has the package been proved to work (rather than just build) reliably on
> kfreebsd-*?
>

I have tested the program in a kfreebsd-amd64 VM, not extensively but
it looks to have the same behavior as on amd64.

> Regards,
>
> Adam
>



-- 
Regards,
Aron Xu


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMr=8w6ibU=cfgx-n+ns6z_dnthsshogj0jehwjljkqm4mo...@mail.gmail.com

Re: freeze exception qpdf versioned symbols?

[Jay Berkenbilt]

Jonathan Nieder  wrote:

> Hi,
>
> Jay Berkenbilt wrote:
>
>> Okay, I've attached two files here.  The first is a copy of
>> version-symbols.patch with the real changes, so this excludes the
>> changes to the regenerated configure file.  The second file is a source
>> debdiff.
>
> I am not on the release team, so please take anything I say with a
> grain of salt.

The release team decided that they weren't going to accept this, so this
discussion is now academic.  However, you made some interesting points
that I thought were worth responding to.


> [...]
>> --- qpdf-2.3.1/debian/changelog  2012-05-19 09:21:52.0 -0400
>> +++ qpdf-2.3.1/debian/changelog  2012-07-18 10:20:10.0 -0400
>> @@ -1,3 +1,9 @@
>> +qpdf (2.3.1-5) unstable; urgency=low
>> +
>> +  * Enable versioned symbols.
>
> Are the symbol versions used shared with upstream, or is this a
> Debian-specific thing?
>
> *checks*
>
> Looks like these are Debian-private but the patch is based on 92c94e7d
> (Add symbol versioning, 2012-06-20).  Ok.

I am upstream for this.  I enabled versioned symbols for future releases
of qpdf (I will soon be releasing 3.0.0).  This was a debian-specific
backport to 2.3.1 for the old ABI.  qpdf does appear in other
distributions that I am not involved in, and they wouldn't have
versioned symbols.  So actually this is a pretty decent argument for not
doing it anyway.

>> ++# Check if LD supports linker scripts, and define conditional
>> ++# HAVE_LD_VERSION_SCRIPT if so.  This functionality is currently
>> ++# constrained to compilers using GNU ld on ELF systems or systems
>> ++# which provide an adequate emulation thereof.
>> ++AC_ARG_ENABLE([ld-version-script],
>> ++  AS_HELP_STRING([--enable-ld-version-script],
>> ++[enable linker version script (default is disabled)]),
>
> Is the default really --disable?

No, the default is really enable.  I copied this code from something
that had a default of disable, and while I changed the default, I didn't
change the help message.  Thanks for catching it.  I fixed it upstream
now.

>> +@@ -0,0 +1,4 @@
>> ++LIBQPDF_3 {
>> ++  global:
>> ++*;
>> ++};
>
> It would be more comforting to have a list of symbols intended for
> export here, so unintentional ABI changes could be caught more easily.
> Do I understand that that would be hard to make because this is a C++
> library?

It would be hard but not impossible.  qpdf also works on Windows, and
for that, I already have every public API marked, but I don't think the
value for the amount of effort is good enough.

> Thanks and hope that helps,

Yes, your comments were helpful and at least resulted in fixing the
configure help message.  Thanks!

-- 
Jay Berkenbilt 


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722213822.0386649101.qww314159@soup

Re: freeze exception qpdf versioned symbols?

[Jay Berkenbilt]

Julien Cristau  wrote:

> Hi Jay,
>
> with no reverse dependencies for libqpdf3 in the archive at this point,
> I think this can wait until wheezy+1.
>
> Cheers,
> Julien

Okay, works for me.  The next upload will most likely be 3.0.0, which
has versioned symbols.

-- 
Jay Berkenbilt 


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722213146.0386632014.qww314159@soup

Re: Bug#681687: missing mime entry

[Charles Plessy]

> On Sun, 2012-07-22 at 15:24 +0200, Michael Biebl wrote:
> > > [...]
> > >> The new mime support maintainer team, which took over the package just a
> > >> few days ago, did ask the release team, if it would be possible to still
> > >> apply this patch for wheezy [2].
> > > [...]
> > >> [2] https://lists.debian.org/debian-release/2012/07/msg01048.html

Dear all,

about the mail discussed above: while it is addressed to Brian and Laszlo,
I made sure that the release team, the technical comitte and the evince
maintainers get a copy so that they can see that things are moving.  But
before getting Laszlo's and Brian's replies, I did not feel like making
promises.

Nevertheless, earlier in http://bugs.debian.org/658139#117, I also wrote the
following to "everybody", with the release team, the tech. comittee and the
evince maintainers copied:

> Wouldn't one of the following solutions be acceptable for you ?
> 
>  - Add the function to mime-support in Wheezy to update /etc/mailcap using
>the FreeDesktop menu entry files in /usr/share/applications via dpkg
>triggers.
> 
>  - Do this in Sid, and add back the MIME entries in evince in Wheezy as a
>temporary compromise.

To keep both possibilities open - without expressing a particular preference
for one or another - me and Laszlo are limiting ourselves to work on the
conversion from Desktop to mailcap, with exceptions limited to packaging
updates that I hope will not prevent our package to be reviewed by the release
team if the consensus is to update mime-support in Wheezy. 

We are getting ready to upload to experimental; things go a bit slowly because
time zone effects inserts some delays between our email exchanges, but on the
other hand, I think that it is a good thing as mime-support will be the first
time I work on a package of standard priority.  Also, it happens that the
previous and next week-ends I am not avaiable for Debian work, which postpones
more extensive tests on my side, but I think that an upload to experimental
would be appropriate now.  The last piece missing is that we are looking for a
mailing list address for the Maintainer field, as the trick to send messages to
the PTS do not work because it would create loops.  Or perhaps we can enhance
the PTS to not transmit messages to itself...

I intend to announce on debian-devel that the adoption has been completed after
we uploaded to experimental (Laszlo, you are of course free to do so yourself
if you are the one who uploads).  As Steve noted later in this thread, the
package is already in collab-maint, although I would like to keep an option
option just in case until we upload, that in case we find a defect in the
conversion we might reset it.

  http://anonscm.debian.org/gitweb/?p=collab-maint/mime-support.git

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120723005137.ga20...@falafel.plessy.net

Re: Non-evasive patch for SELinux handling suitable for a freeze exception?

[Cyril Brulebois]

Eero Häkkinen  (22/07/2012):
> This seems to be a persistent misunderstanding. As a matter of fact, the 
> -e option does not have an effect on left hand operands of AND (&&) and 
> OR (||) lists just like it does not have an effect on the command used 
> to control if, elif, while and until compound commands.

Probably memories of the dozens of patches sent to fix makefiles which
contained things like “[ -f Makefile ] && $(MAKE) clean” instead of
“[ ! -f Makefile ] || $(MAKE) clean”.

(in addition to sending mails past silly-o'clock…)

Thanks for the heads-up anyway.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#682460: unblock: boost1.50/1.50.0-1

[Steve M. Robbins]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package boost1.50

Given the long lifetime of stable Debian, I expect users would appreciate 
having the latest
Boost available.  This is a leaf package so should have no impact on stability 
of the
archive.

[Testing currently has Boost 1.49 as default and I propose to keep it that way
even if Boost 1.50 is also available.]

unblock boost1.50/1.50.0-1

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722233423.23285.14246.reportbug@localhost

Re: Bug#681687: missing mime entry

[Russ Allbery]

Steve Langasek  writes:

>  - It's not clear what the transitional behavior should be when a package
>includes both a .desktop file and a usr/lib/mime/packages file.  There's
>no reliable way to associate the contents of the two files, so this
>probably ends up with duplicated entries in /etc/mailcap, possibly with
>small variations; just from a quick look on my system, I find that the
>libreoffice .desktop and mime files use quite different program
>invocations.  This is of course exactly why we want to not maintain
>duplicate information in multiple files, but we should have a clear idea
>about which we expect to take precedence, and make sure this is
>implemented, so that users don't wind up with buggy behavior on their
>systems due to random ordering.  If this update-mime change is accepted
>for wheezy, the transition will most definitely be ongoing at release
>time, so we really ought to get this right.

I think the mime/packages file should obviously take precedence for
programs using mailcap, since that's the target of the automated
conversion.  You always want the manually-maintained file to override the
results of any automated conversion, since that way you can work around
any bugs in the conversion (or missing features, like priority) by
providing a manually-maintained file.

> Broadly speaking, I think the correct long-term solution is to first add
> support to update-mime for reading both .desktop files and mime files,
> and then to update policy to tell maintainers to use .desktop files
> instead of mime files.  And I think it's better for Debian if we can get
> the first part done prior to the wheezy release.  But I would like the
> release team to make their own determination of whether the patch that's
> currently up for consideration is of sufficient quality, and
> sufficiently safe, to be granted a freeze exception.

This sounds right to me as well.  I think we should ensure the most
critical media types are working in both systems for the wheezy release
and then aim at removing the requirement to support update-mime for all
packages providing .desktop files for wheezy+1.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87fw8jxupp@windlord.stanford.edu

NEW changes in proposedupdates

[Debian FTP Masters]

Processing changes file: 
debian-archive-keyring_2010.08.28+squeeze1_amd64.changes
  ACCEPT
Processing changes file: kfreebsd-8_8.1+dfsg-8+squeeze3_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: kfreebsd-8_8.1+dfsg-8+squeeze3_kfreebsd-i386.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_amd64.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_armel.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_i386.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_ia64.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_kfreebsd-i386.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_mips.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_mipsel.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_powerpc.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_s390.changes
  ACCEPT
Processing changes file: nsd3_3.2.5-1.squeeze2_sparc.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_amd64.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_armel.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_i386.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_ia64.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_kfreebsd-i386.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_mips.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_mipsel.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_powerpc.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_s390.changes
  ACCEPT
Processing changes file: iceape_2.0.11-14_sparc.changes
  ACCEPT
Processing changes file: libmtp_1.0.3-1+squeeze2_amd64.changes
  ACCEPT


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1st4vb-0006h9...@franck.debian.org

Processed: Re: Bug#677751: pu: package libmtp/1.0.3-1+squeeze1

[Debian Bug Tracking System]

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

> tags 677751 + pending
Bug #677751 [release.debian.org] pu: package libmtp/1.0.3-1+squeeze1
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
677751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.134299661225007.transcr...@bugs.debian.org

Processed: Re: Bug#682314: pu: package debian-archive-keyring/2010.08.28(+squeeze1)

[Debian Bug Tracking System]

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

> tags 682314 + pending
Bug #682314 [release.debian.org] pu: package 
debian-archive-keyring/2010.08.28(+squeeze1)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
682314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.134299658724948.transcr...@bugs.debian.org

Bug#682314: pu: package debian-archive-keyring/2010.08.28(+squeeze1)

[Adam D. Barratt]

tags 682314 + pending
thanks

On Sat, 2012-07-21 at 17:59 +0200, Philipp Kern wrote:
> On Sat, Jul 21, 2012 at 03:14:54PM +0100, Adam D. Barratt wrote:
> > On Sat, 2012-07-21 at 15:04 +0200, Philipp Kern wrote:
> > > I would like to update debian-archive-keyring in stable to add both the 
> > > wheezy
> > > automatic (ftp-master) and wheezy stable (release) keys. The debdiff is
> > > attached. An upgrade to 2012.4 seems to work just fine.
> > Please go ahead; thanks.
> 
> Uploaded.

Flagged for acceptance; thanks.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342996500.13223.189.ca...@jacala.jungle.funky-badger.org

Bug#677751: pu: package libmtp/1.0.3-1+squeeze1

[Adam D. Barratt]

tags 677751 + pending
thanks

On Sat, 2012-07-21 at 18:49 +0100, Adam D. Barratt wrote:
> On Sun, 2012-06-17 at 02:17 +0200, Alessio Treglia wrote:
> > On Sat, Jun 16, 2012 at 11:29 PM, Philipp Kern  wrote:
> > > AFAICS you attached the same file again, which is not a debdiff. ;-)
> > 
> > Indeed, sorry.
> > Debdiff is attached for real now :-)
> 
> Apologies for the delay in getting back to you.  Please go ahead;
> thanks.

For the record, this was uploaded and I've flagged it for acceptance in
to proposed-updates.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342996525.13223.190.ca...@jacala.jungle.funky-badger.org

Re: Freeze exception request for zendframework 1.11.12-1

[Adam D. Barratt]

On Fri, 2012-07-06 at 11:03 +0100, Neil McGovern wrote:
> On Thu, Jul 05, 2012 at 02:21:29PM +0200, Frank Habermann wrote:
> > > 4303 files changed, 43422 insertions(+), 12755 deletions(-)
[...]
> > i could do that. But i would prefer to accapt the hole package.
> > The version 1.11.12 is the last minor bugfix release in the line of
> > version 1.11. So it makes sense to have this version in wheezy.
[...]
> And unfortunately those have also happened too late for us to review
> manually, especially with a patch of that size.
> 
> Can you prepare and upload the specific fix to t-p-u please?

Ping?

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342996458.13223.188.ca...@jacala.jungle.funky-badger.org

Bug#681022: unblock: openacs/5.7.0+dfsg-2

[Adam D. Barratt]

[It appears the original request never reached the debian-release list.
I'm assuming this is due to the (gzipped!) attached debdiff being over
2MB in size]

On Tue, 2012-07-10 at 02:23 +0200, Hector Romojaro wrote:
> Please unblock package openacs. It fixes an RC bug (#663356)

That bug is only marked as found in 5.7.0+dfsg-1, which has never been
in testing.  If that's correct, and it doesn't affect earlier versions,
then I'm afraid that fixing it, whilst appreciated, is not directly
relevant for an unblock request.

> - The new version (5.7.0+dfsg-2) has been delaying the upload and didn't
> make it on time for the freeze. Finally, my uploader did the upload to
> unstable today. I apologize for that.

When was the upload prepared?  The RC bug was reported more than four
months ago.

> - The previous version in unstable (5.7.0+dfsg-1) never reached testing
> because of the previously mentioned RC bug, and it includes a new
> upstream release, so the debdiff between testing (5.5.1+dfsg-2) and
> unstable (5.7.0+dfsg-2) is huge.

Specifically:

 1741 files changed, 113558 insertions(+), 43055 deletions(-)

I'm afraid that's way too large to be reviewed at this point.

> It includes switching to 3.0 package
> format, moving from wwwconfig-common to dbconfig-common, copyright file
> changes, changes on the dependencies...

Those generally sound like things one wouldn't expect to see as part of
a package being considered for unblocking; during a freeze, changes
should be kept minimal, which the above don't qualify as.

It's possible that another team member might have different opinions,
but I'm afraid I'd have to say no at this point.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342993922.13223.187.ca...@jacala.jungle.funky-badger.org

Bug#682307: marked as done (unblock: apt/0.9.7.2)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 22:32:43 +0100
with message-id <1342992763.13223.175.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682307: unblock: apt/0.9.7.2
has caused the Debian Bug report #682307,
regarding unblock: apt/0.9.7.2
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.)


-- 
682307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: de...@lists.debian.org

Please unblock package apt

The diff between 0.9.7.1 and 0.9.7.2 is
(minus translation updates and manually-run testcases):

apt-pkg/cachefilter.cc   |6 --
apt-pkg/clean.cc |5 +++--
apt-pkg/deb/deblistparser.cc |3 ++-
cmdline/apt-mark.cc  |   16 ++--
debian/apt.cron.daily|   14 --
ftparchive/writer.cc |2 +-
6 files changed, 28 insertions(+), 18 deletions(-)

The changes are denoted as follows in the changelog
with some more comments regarding reason and possible regressions:
(tl;dr: good reasons and low regression potential - just unblock ;) )

>  * debian/apt.cron.daily:
>- do not try to backup extended_states file if it doesn't
>  exist (Closes: #680287)

(Technical an RC bug in the cronjob, hard to trigger in real life though.)

>  * ftparchive/writer.cc:
>- handle the APT::FTPArchive::Packages::SHA512 option correctly instead
>  of overriding SHA256, thanks Christian Marillat! (Closes: #680252)

(Classic typo: regression possibility is negative)

>  * cmdline/apt-mark.cc:
>- arch:all packages are treated as arch:native packages, but dpkg
>  expects pkg:all for selections, so use the arch of the installed
>  version instead of the package structure if possible.
>  Thanks to Stepan Golosunov for the report! (Closes: #680041)

APT claimed to be successful in holding the package back,
even through it wasn't as dpkg just ignored the request.
Could be really confusing for users …
(Artefact from the interface changes in dpkg for multi-arch)

>  * apt-pkg/clean.cc:
>- run autoclean against pkg:arch and not always against pkg:native as
>  this removes valid cache entries (Closes: #679371)

Nasty if caches are shared (with network shares for example) or
if autoclean (and downloading) is run by a/our cronjob.
(Incomplete multi-arch awareness)

>  * apt-pkg/deb/deblistparser.cc:
>- negative dependencies need to apply to all architectures,
>  but those with a specific architecture only apply to this one

Specific architecture dependencies were introduced in 0.9.6.
'Conflicts: foo:amd64' would be interpreted as a conflict with package
'foo:amd64' on all configured architectures (=architecture becomes
accidentally part of the name, hence no conflict will be found).

>  * apt-pkg/cachefilter.cc:
>- remove architecture-specific arch to tuple expansion-rules as they lead
>  to the same tuples for different architectures (e.g. linux-arm for arm,
>  armel and armhf) while the dpkg-architecture code uses triples which
>  are different (in the first part, which we omit in our tuples), so e.g.
>  build-dep restrictions for armel ended up effecting armhf as well

This bug effects "apt-get build-dep foo" and is present in squeeze as well.
It was well hidden by the fact that the restrictions it would map together
usually are used together – build-infrastructure has its own build-
dependency resolution and if all else fails dpkg-checkbuilddeps would have
intervened, so regression possibility is low.
(Why these special mappings were in the code is so far unknown.)

This also effects commandline parsing since 0.9.7 - which uncovered it:
"apt-get install foo:armhf" and "apt-get install foo:armel" had the same
result. ("Randomly" foo for armhf or armel, depending on the order of M-A
configuration)



Attached is a more complete diff (but still without translations),
but if you want the complete diff or if you have any additional questions
feel free to ask of course (just keep deity@ cc'ed please).


unblock apt/0.9.7.2


As an aside, a few more translations have lined up and we are working on a few
more targeted fixes, so we will surely annoy you with another request after
this one. (We have also the "problem" that the documentation uses in various
 places the release  codenames as examples [as the usage of the suite is
 potentially dangerous] and while we have a central place to switch the names
 we would need to

Processed: Re: Bug#682268: unblock: foremost/1.5.7-4

[Debian Bug Tracking System]

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

> tags 682268 + moreinfo
Bug #682268 [release.debian.org] unblock: foremost/1.5.7-4
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
682268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.134299303010153.transcr...@bugs.debian.org

Bug#682268: unblock: foremost/1.5.7-4

[Adam D. Barratt]

tags 682268 + moreinfo
thanks

On Sat, 2012-07-21 at 04:28 +0800, Aron Xu wrote:
> Please unblock the package foremost.
> 
> The updated version fixed the build on kfreebsd-* (1.5.7-3) and hurd
> (1.5.7-4). It would be great to have one more software ported to those
> platform by making simple build system changes.

Wheezy won't include hurd, so having the package built there isn't
really relevant for an unblock.

Has the package been proved to work (rather than just build) reliably on
kfreebsd-*?

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342992944.13223.177.ca...@jacala.jungle.funky-badger.org

Bug#682328: marked as done (unblock: yatex/1.76+dfsg1-2)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 22:26:35 +0100
with message-id <1342992395.13223.174.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682328: unblock: yatex/1.76+dfsg1-2
has caused the Debian Bug report #682328,
regarding unblock: yatex/1.76+dfsg1-2
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.)


-- 
682328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package yatex for wheezy. 1.76+dfsg1-1 has a grave bug
to misname elisp coding system, so in many case it is unusable because
of displaying garbled characters.

diffs are below:

diff -Nru yatex-1.76+dfsg1/debian/changelog yatex-1.76+dfsg1/debian/changelog
--- yatex-1.76+dfsg1/debian/changelog   2012-06-15 08:54:03.0 +0900
+++ yatex-1.76+dfsg1/debian/changelog   2012-07-21 11:11:30.0 +0900
@@ -1,3 +1,9 @@
+yatex (1.76+dfsg1-2) unstable; urgency=medium
+
+  * Fix status line garbled by mismatched coding system. (Closes: 681649)
+
+ -- KURASHIKI Satoru   Sat, 21 Jul 2012 11:07:29 +0900
+
 yatex (1.76+dfsg1-1) unstable; urgency=low
  
   * New upstream release.
diff -Nru yatex-1.76+dfsg1/debian/rules yatex-1.76+dfsg1/debian/rules
--- yatex-1.76+dfsg1/debian/rules   2012-07-21 10:54:07.0 +0900
+++ yatex-1.76+dfsg1/debian/rules   2012-07-21 11:07:05.0 +0900
@@ -30,7 +30,7 @@
 
 build/yatex::
for i in $(LISP) $(HELP) $(INFOSRC); do \
-   nkf -d --utf8 $$i | sed -e 's/sjis-dos/utf-8-unix/' -e 
's/sjis/utf-8/' > debian/utf8/$$i; \
+   nkf -d --utf8 $$i | sed -e 's/coding: sjis/coding: utf-8/' > 
debian/utf8/$$i; \
done

cd debian/utf8 && for f in $(INFOSRC); do \

unblock yatex/1.76+dfsg1-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Sun, 2012-07-22 at 01:15 +0900, KURASHIKI Satoru wrote:
> Please unblock package yatex for wheezy. 1.76+dfsg1-1 has a grave bug
> to misname elisp coding system, so in many case it is unusable because
> of displaying garbled characters.

Unblocked; thanks.

Regards,

Adam--- End Message ---

Bug#682204: marked as done (unblock: udisks/1.0.4-7)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 22:24:49 +0100
with message-id <1342992289.13223.173.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682204: unblock: udisks/1.0.4-7
has caused the Debian Bug report #682204,
regarding unblock: udisks/1.0.4-7
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.)


-- 
682204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package udisks

In our effort to shrink CD1 [1], I've uploaded a new version of udisks
to unstable. The changelog reads:

udisks (1.0.4-7) unstable; urgency=low

  * debian/patches/13-dosfslabel.patch: The original reasons why mlabel was
preferred over dosfslabel are no longer true. So switch back to dosfslabel
which is part of dosfstools which we already require for mkfs.vfat and
drop the Recommends on mtools. Fix the maximum length for FAT labels while
at it. (Closes: #680683)

 -- Michael Biebl   Fri, 20 Jul 2012 11:39:01 +0200

Full debdiff is attached.
I've successfully run the internal test-suite with the patch applied and
successfully created new and changed existing FAT partitions.

unblock udisks/1.0.4-7

[1] https://lists.debian.org/debian-devel/2012/07/msg00138.html

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Fri, 2012-07-20 at 11:50 +0200, Michael Biebl wrote:
> Please unblock package udisks
> 
> In our effort to shrink CD1 [1], I've uploaded a new version of udisks
> to unstable. The changelog reads:
> 
> udisks (1.0.4-7) unstable; urgency=low
> 
>   * debian/patches/13-dosfslabel.patch: The original reasons why mlabel was
> preferred over dosfslabel are no longer true. So switch back to dosfslabel
> which is part of dosfstools which we already require for mkfs.vfat and
> drop the Recommends on mtools. Fix the maximum length for FAT labels while
> at it. (Closes: #680683)

Unblocked.

Regards,

Adam--- End Message ---

Bug#682155: marked as done (unblock: datapm/0.10-1.1)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 22:20:15 +0100
with message-id <1342992015.13223.171.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682155: unblock: datapm/0.10-1.1
has caused the Debian Bug report #682155,
regarding unblock: datapm/0.10-1.1
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.)


-- 
682155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package datapm/0.10-1.1.
The NMU fixes one RC and one important bug:
 #681901 datapm: missing dependency on python-pkg-resources
 #682053 FTBFS if built twice in a row

Full debdiff is attached below.

unblock datapm/0.10-1.1

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru datapm-0.10/debian/changelog datapm-0.10/debian/changelog
--- datapm-0.10/debian/changelog	2012-05-31 08:17:34.0 +0200
+++ datapm-0.10/debian/changelog	2012-07-19 22:10:28.0 +0200
@@ -1,3 +1,13 @@
+datapm (0.10-1.1) unstable; urgency=low
+
+  * Non-maintainer upload with maintainer approval.
+  * Add Depends on python-pkg-resources.
+Closes: #681901
+  * Add *.egg-info/* to debian/clean to fix FTBFS if built twice in a row.
+Closes: #682053
+
+ -- Evgeni Golov   Thu, 19 Jul 2012 22:07:11 +0200
+
 datapm (0.10-1) unstable; urgency=low
 
   * Initial release (Closes: #664566)
diff -Nru datapm-0.10/debian/clean datapm-0.10/debian/clean
--- datapm-0.10/debian/clean	1970-01-01 01:00:00.0 +0100
+++ datapm-0.10/debian/clean	2012-07-19 22:08:01.0 +0200
@@ -0,0 +1 @@
+*.egg-info/*
diff -Nru datapm-0.10/debian/control datapm-0.10/debian/control
--- datapm-0.10/debian/control	2012-05-31 08:17:34.0 +0200
+++ datapm-0.10/debian/control	2012-07-19 22:07:09.0 +0200
@@ -16,6 +16,7 @@
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, 
  python-ckanclient (>= 0.3), 
+ python-pkg-resources,
  python-sqlalchemy, 
  python-simplejson, 
  python-sqlite
--- End Message ---
--- Begin Message ---
On Thu, 2012-07-19 at 22:24 +0200, Evgeni Golov wrote:
> Please unblock package datapm/0.10-1.1.
> The NMU fixes one RC and one important bug:
>  #681901 datapm: missing dependency on python-pkg-resources
>  #682053 FTBFS if built twice in a row

Unblocked; thanks.

Regards,

Adam--- End Message ---

Re: freeze exception for tiff3 and tiff for security bugs

[Adam D. Barratt]

On Sat, 2012-07-21 at 21:44 -0400, Jay Berkenbilt wrote:
> I've upload tiff3-3.9.6-7 and tiff-4.0.2-2 with fixes to CVE-2012-3401.
> The patch is as attached to the bug reports, 682195 and 682115.  Please
> unblock so these RC security bug fixes can go in.  No other changes were
> made in these uploads.

Both unblocked; thanks.

> The bug doesn't actually apply to tiff3, but the
> patch should work for the version of tiff in stable.

I'm sure the security team will be glad to hear that. :-)

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342990701.13223.167.ca...@jacala.jungle.funky-badger.org

Re: Bug#681687: missing mime entry

[Steve Langasek]

On Sat, Jul 21, 2012 at 11:12:25PM +0200, Michael Biebl wrote:
> A patch providing this converter has been available for a few months
> [1]. The mime-support maintainer just never got around to upload it or
> even comment on it.

> The new mime support maintainer team, which took over the package just a
> few days ago, did ask the release team, if it would be possible to still
> apply this patch for wheezy [2].
> I think this should be the solution we should aim for and I would
> appreciate if the release team could give the mime-support maintainers a
> green light for the unstable upload.

I agree that we should aim for such an automated, long-term solution.  In
the meantime, I think it's correct to say that evince has a release-critical
bug.

I think that the right thing for the evince maintainers to do is to upload
the package *now* with re-added mime-support handling, and worry about
dropping it only after mime-support .desktop support has proven itself -
knowing that this may not happen in time for the wheezy release.

(And if you disagree, well, it's an RC bug... so someone can upload an NMU
for it...)

> If the converter solution turns out to be too buggy or requires larger
> changes, we have a simple contigency plan, i.e. just drop the converter
> again.

> I would really appreciate if we could try to fix this *whole* issue for
> good for *wheezy*. Re-adding the mime file in evince can still be done
> if the proper mime-support fix has not been done in say a month or two.

>From the discussion so far, there are two issues that in the release
managers' position, I would be concerned about seeing addressed before
endorsing this as a solution for wheezy.

 - The .desktop format does not include an equivalent to the mailcap
   'priority' field; it's not clear what the expected / desirable handling
   is when multiple packages provide .desktop files for the same mime type. 
   The documented default priority is '5', which is probably a reasonable
   starting point, but there's still a loss of expressiveness that seems to
   require an extension of the .desktop file format (especially since
   priority values are meant to be per-mime-type).

 - It's not clear what the transitional behavior should be when a package
   includes both a .desktop file and a usr/lib/mime/packages file.  There's
   no reliable way to associate the contents of the two files, so this
   probably ends up with duplicated entries in /etc/mailcap, possibly with
   small variations; just from a quick look on my system, I find that the
   libreoffice .desktop and mime files use quite different program
   invocations.  This is of course exactly why we want to not maintain
   duplicate information in multiple files, but we should have a clear idea
   about which we expect to take precedence, and make sure this is
   implemented, so that users don't wind up with buggy behavior on their
   systems due to random ordering.  If this update-mime change is accepted
   for wheezy, the transition will most definitely be ongoing at release
   time, so we really ought to get this right.

But that's just my two cents; the release managers may have a different set
of concerns.  Either way, my recommendation to the GNOME maintainers is that
if you think it's important to not have to re-add the mime file to evince
for wheezy, you should participate in finding a solution to these issues and
not regard it as the mime-support maintainer's problem to fix - which I have
the impression has been the general approach up to this point.

On Sun, Jul 22, 2012 at 03:43:10PM +0100, Adam D. Barratt wrote:
> > If Steve and other members of the ctte consider such a tool as an
> > approriate way to solve this bug, would the release team also
> > acknowledge this approach or not?

> If it's the solution that the TC decide on to resolve the issue, it
> sounds like something we could work with, at least imho, from what I've
> seen so far.  I've CCed -release for any further comments, as I don't
> know how many members of the team are following -ctte and/or this bug.

Broadly speaking, I think the correct long-term solution is to first add
support to update-mime for reading both .desktop files and mime files, and
then to update policy to tell maintainers to use .desktop files instead of
mime files.  And I think it's better for Debian if we can get the first part
done prior to the wheezy release.  But I would like the release team to make
their own determination of whether the patch that's currently up for
consideration is of sufficient quality, and sufficiently safe, to be granted
a freeze exception.

> For clarity, the current proposal would be
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=mime-support-desktop.patch;att=1;bug=497779
> , or something similar?

Yes. The nascent mime-support maintenance team has also committed a patch to
the repo at
,
probably best to reference the 

Bug#682448: unblock: exactimage/0.8.5-5

[Sven Eckelmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

exactimage/0.8.5-5 was now sponsored. I would like to request an unblock with 
an extended time in unstable as discussed in
 http://lists.debian.org/debian-release/2012/07/msg00335.html

unblock exactimage/0.8.5-5

signature.asc
Description: This is a digitally signed message part.

Re: Non-evasive patch for SELinux handling suitable for a freeze exception?

[Eero Häkkinen]

Cyril Brulebois wrote on 2012-07-22 04:53:15 +0200:
> (For lazy people following at home, it's about debian/init) The patched
> init script would have:
> | set -e
> | …
> | [ -x /sbin/restorecon ] && /sbin/restorecon $SCREENDIR

Thus the patched init script would work just fine because the restorecon 
list compound-list is not the last command in the init script.

> Meaning you never get to do the clean-up and the chmod dance if the
> policycoreutils package isn't installed.

This seems to be a persistent misunderstanding. As a matter of fact, the 
-e option does not have an effect on left hand operands of AND (&&) and 
OR (||) lists just like it does not have an effect on the command used 
to control if, elif, while and until compound commands.

The root of this misunderstanding is probably the fact that the default 
exit status of a shell is the exit status of the last command and that 
the exit status of an if compound command is 0 if none of the compound 
lists was executed but the exit status of an AND list is the exit status 
of the last command in the list which was executed.

Therefore, the following script will print exit statuses 1 and 0 in that 
order (provided that the file /nonexisting does not exist):
| set -e
| [ -x /nonexisting ] && /nonexisting
| echo $?
| if [ -x /nonexisting ]; then
| /nonexisting
| fi
| echo $?

PS.

To be precise, the list compound-list
 [ -x /sbin/restorecon ] && /sbin/restorecon $SCREENDIR

works fine in all practical situations but not in all imaginable 
situations. If the [ command is not a builtin command (unlike in bash, 
dash and busybox) and the policycoreutils package is installed but the 
external [ command terminates abnormally (due to lack of resources or 
due to a signal, for instance), the abnormal termination remains 
unnoticed, That is, however, a non-issue for normal systems because the 
[ command is a practically always a shell builtin.


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722190002.GA15515@eero.localdomain

Re: [Call for Test] Please test your package with python-svn/experimental (version 1.7.6-0.1)

[dann frazier]

On Thu, Jul 19, 2012 at 06:53:01AM +0900, Hideki Yamane wrote:
> Hi maintainers,
> 
>  I've put pysvn 1.7.6 package to experimental, it is necessary update to put
>  Subversion1.7 to Wheezy. Your package seems to have a dependency for this 
>  python-svn package, so please check it with python-svn_1.7.6-0.1 in 
> experimental.
> 
>  If you have any question, please ask me.
>  Thanks!

Hideki,
 svn-load's test suite passes 100% with python-svn_1.7.6-0.1. Thanks!



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722184755.ga15...@dannf.org

Bug#680901: Would have to be done in Testing now

[Scott Kitterman]

There's been a maintainer upload since this was filed, so the issue can either 
be fixed by a binNMU of rpy in Testing or unblocking the maintainer upload from 
Unstable.


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4464090.ghlr2RRYYv@scott-latitude-e6320

Bug#680343: unblock: trousers/0.3.9-2

[Pierre Chifflier]

On Sat, Jul 21, 2012 at 12:23:03PM +0200, Julien Cristau wrote:
> On Thu, Jul  5, 2012 at 21:25:38 +0200, Pierre Chifflier wrote:
> 
> > +# kill tcsd (and any other process owned by the tss user)
> > +killall -u tss  2>/dev/null || true
> 
> Why is this necessary, and what happens if psmisc isn't installed?
> 

Hi Julien,

This is used to kill the daemon if the process is running, and avoid
that two processes try to access /dev/tpm0 on the next start.
If the command fails, or if psmisc is not installed, the script should
continue to allow the upgrade. The next start of the init script will
run a second daemon, which will stop (EBUSY). A second restart should
work, since the init script will be fixed after.

Cheers,
Pierre


signature.asc
Description: Digital signature

Bug#682421: marked as done (unblock: docsis/0.9.6+git16-g61ee500+dfsg-2)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 17:22:05 +0100
with message-id <1342974125.13223.162.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682421: unblock: docsis/0.9.6+git16-g61ee500+dfsg-2
has caused the Debian Bug report #682421,
regarding unblock: docsis/0.9.6+git16-g61ee500+dfsg-2
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.)


-- 
682421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Please unblock package docsis

This uploads fixes RC bug #682337 with patch send-decode-output-to-stdout.patch.
This bug caused stuff to be outputed to stderr insteadd of stdout, thus mixing
errors with the output.

I also added a second small patch fix-double-use-of-stderr.patch that
fixes double use of stderr in fprintf().

Both patches have already been accepted and applied upstream.

Thanks for your time, Lisandro.

unblock docsis/0.9.6+git16-g61ee500+dfsg-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: mips
i386

Kernel: Linux 3.2.21+edid (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Sun, 2012-07-22 at 12:54 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Please unblock package docsis
> 
> This uploads fixes RC bug #682337 with patch 
> send-decode-output-to-stdout.patch.
> This bug caused stuff to be outputed to stderr insteadd of stdout, thus mixing
> errors with the output.
> 
> I also added a second small patch fix-double-use-of-stderr.patch that
> fixes double use of stderr in fprintf().

Unlocked.

Regards,

Adam--- End Message ---

Bug#682390: unblock: muse/2.0-1

[Adam D. Barratt]

On Sun, 2012-07-22 at 13:21 +0200, Alessio Treglia wrote:
> Please allow muse 2.0-1 to join Debian Wheezy.
> 
> It brings many bugfixes since the latest release candidate currently
> available in testing. Plus, upstream intends to support this release
> on the long term.

It's also basically unreviewable when compared to the rc.  Even dropping
the translations and other obvious documentation stuff leaves

 331 files changed, 16261 insertions(+), 11942 deletions(-)

:-(

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342972534.13223.161.ca...@jacala.jungle.funky-badger.org

Bug#682421: unblock: docsis/0.9.6+git16-g61ee500+dfsg-2

[Lisandro Damián Nicanor Pérez Meyer]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Please unblock package docsis

This uploads fixes RC bug #682337 with patch send-decode-output-to-stdout.patch.
This bug caused stuff to be outputed to stderr insteadd of stdout, thus mixing
errors with the output.

I also added a second small patch fix-double-use-of-stderr.patch that
fixes double use of stderr in fprintf().

Both patches have already been accepted and applied upstream.

Thanks for your time, Lisandro.

unblock docsis/0.9.6+git16-g61ee500+dfsg-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: mips
i386

Kernel: Linux 3.2.21+edid (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120722155459.19121.86860.report...@luna.lisandropm.com.ar

Re: Bug#681687: missing mime entry

[Ian Jackson]

Adam D. Barratt writes ("Bug#681687: missing mime entry"):
> If it's the solution that the TC decide on to resolve the issue, it
> sounds like something we could work with, at least imho, from what I've
> seen so far.  I've CCed -release for any further comments, as I don't
> know how many members of the team are following -ctte and/or this bug.

Right.  So far I think my personal view is that I'm happy for the
release team to carry on doing whatever they think is best, on this
issue.

> For clarity, the current proposal would be
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=mime-support-desktop.patch;att=1;bug=497779
>  , or something similar?

I would be worried that this would make a widespread and radical
change to the behaviour of the mime-support-using packages.  Are we
sure that that's the right thing to do at this stage of the release ?

If we were wanting to do this properly, we would compare the
automatically-generated entires with the previous manually-written
ones, to see what behavioural changes we would expect.

> With my release hat on, it feels like "there's still a while until we
> release" is being used more often recently as a justification for trying
> to get larger scale changes incorporated or fixes delayed.  While I'm
> not implying that's the intention in this case, I do think we need to be
> wary of saying "there'll be plenty of time to fix that still".
> 

I certainly don't think "we failed to get the automatic machinery
deployed and tested properly before the freeze" is a good excuse for
insisting on a freeze exception for it.

I can see why the evince maintainers are reluctant to keep on with an
approach they regard as obsolete and deprecated, but until the
replacement is properly deployed and tested that's what we should do.

Ian.


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20492.6400.872581.996...@chiark.greenend.org.uk

Bug#682393: marked as done (unblock: bindfs/1.10.3-2)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 16:04:32 +0100
with message-id <1342969472.13223.158.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682393: unblock: bindfs/1.10.3-2
has caused the Debian Bug report #682393,
regarding unblock: bindfs/1.10.3-2
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.)


-- 
682393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello, please unblock package bindfs which fixes a grave bug #681647.
Diff attached.


unblock bindfs/1.10.3-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 000..5dde0bf
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,58 @@
+This package uses quilt to manage all modifications to the upstream
+source.  Changes are stored in the source package as diffs in
+debian/patches and applied during the build.
+
+To configure quilt to use debian/patches instead of patches, you want
+either to export QUILT_PATCHES=debian/patches in your environment
+or use this snippet in your ~/.quiltrc:
+
+for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do
+if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then
+export QUILT_PATCHES=debian/patches
+break
+fi
+done
+
+To get the fully patched source after unpacking the source package, cd to
+the root level of the source package and run:
+
+quilt push -a
+
+The last patch listed in debian/patches/series will become the current
+patch.
+
+To add a new set of changes, first run quilt push -a, and then run:
+
+quilt new 
+
+where  is a descriptive name for the patch, used as the filename in
+debian/patches.  Then, for every file that will be modified by this patch,
+run:
+
+quilt add 
+
+before editing those files.  You must tell quilt with quilt add what files
+will be part of the patch before making changes or quilt will not work
+properly.  After editing the files, run:
+
+quilt refresh
+
+to save the results as a patch.
+
+Alternately, if you already have an external patch and you just want to
+add it to the build system, run quilt push -a and then:
+
+quilt import -P  /path/to/patch
+quilt push -a
+
+(add -p 0 to quilt import if needed).  as above is the filename to
+use in debian/patches.  The last quilt push -a will apply the patch to
+make sure it works properly.
+
+To remove an existing patch from the list of patches that will be applied,
+run:
+
+quilt delete 
+
+You may need to run quilt pop -a to unapply patches first before running
+this command.
diff --git a/debian/changelog b/debian/changelog
index 34c18fe..d0ea609 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+bindfs (1.10.3-2) unstable; urgency=medium
+
+  * debian/control:
+- Build-depend on quilt.
+  * debian/rules:
+- Use 'dh --with quilt'.
+  * debian/patches:
+- New patch '010-readdir-pathconf-fix.patch'.
+- New patch '020-usermap-memory-fix.patch'.
+- Two patches above fix serious memory errors. Thanks to
+  Marcelo E. Magallon for the report and upstream for providing directed
+  patches. (Closes: #681647)
+  * debian/README.source:
+- Added with standard quilt intructions.
+
+ -- Eugene V. Lyubimkin   Sun, 15 Jul 2012 13:30:45 +0300
+
 bindfs (1.10.3-1) unstable; urgency=low
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index f9e64fb..c53e07e 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,8 @@ Source: bindfs
 Section: utils
 Priority: optional
 Maintainer: Eugene V. Lyubimkin 
-Build-Depends: debhelper (>= 7.0.50), autotools-dev, libfuse-dev, pkg-config
+Build-Depends: debhelper (>= 7.0.50), autotools-dev, libfuse-dev, pkg-config,
+  quilt (>= 0.46-7)
 Standards-Version: 3.9.3
 Homepage: http://code.google.com/p/bindfs/
 
diff --git a/debian/patches/010-readdir-pathconf-fix.patch b/debian/patches/010-readdir-pathconf-fix.patch
new file mode 100644
index 000..28639ac
--- /dev/null
+++ b/debian/patches/010-readdir-pathconf-fix.patch
@@ -0,0 +1,29 @@
+--- bindfs-1.

Re: Bug#681687: missing mime entry

[Adam D. Barratt]

On Sun, 2012-07-22 at 15:24 +0200, Michael Biebl wrote:
> On 21.07.2012 23:40, Adam D. Barratt wrote:
> > On Sat, 2012-07-21 at 23:12 +0200, Michael Biebl wrote:
> >> On 21.07.2012 09:11, Steve Langasek wrote:
> >>
> >>> Now, I think providing a tool to auto-translate .desktop files into 
> >>> mailcap
> >>> entries is a perfectly appropriate way to go about solving this bug, if
> > [...]
> >> The new mime support maintainer team, which took over the package just a
> >> few days ago, did ask the release team, if it would be possible to still
> >> apply this patch for wheezy [2].
> > [...]
> >> [2] https://lists.debian.org/debian-release/2012/07/msg01048.html
> > 
> > As far as I can tell, that's very much not what that message says.  In
> > fact, it doesn't appear to request anything of the release team at all.
> 
> Well, Charles did not specifically ask the release team, but he CCed the
> release team

Well, he hit "reply all" on a thread that was already CCed to the
release team.  I'm not sure it would otherwise have been copied.

> and his email contains:
> 
> > 4) Postpone any other change on the main branch until either #681687 (tech.
> >comittee) is solved or Wheezy released.
> 
> This reads to me as if Charlees is waiting for a decision from the ctte.

Agreed.  It's still not even implicitly a request for release team
comment on the solution imo, but let's leave that particular horse in
peace before the discussion gets any more circular. :-/

> If Steve and other members of the ctte consider such a tool as an
> approriate way to solve this bug, would the release team also
> acknowledge this approach or not?

If it's the solution that the TC decide on to resolve the issue, it
sounds like something we could work with, at least imho, from what I've
seen so far.  I've CCed -release for any further comments, as I don't
know how many members of the team are following -ctte and/or this bug.

For clarity, the current proposal would be
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=mime-support-desktop.patch;att=1;bug=497779
 , or something similar?

[...]
> From past experience we still have around 5 months until we release.
> This should be enough time to get this ready for wheezy. And as said, if
> unsurmountable problems turn up which can't be addressed within say two
> months, we can simply drop the converter again and then add back the
> evince mime file.

With my release hat on, it feels like "there's still a while until we
release" is being used more often recently as a justification for trying
to get larger scale changes incorporated or fixes delayed.  While I'm
not implying that's the intention in this case, I do think we need to be
wary of saying "there'll be plenty of time to fix that still".


Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342968190.13223.156.ca...@jacala.jungle.funky-badger.org

Bug#682405: unblock: xserver-xorg-input-mouse/1:1.7.2-3

[Petr Salinger]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package xserver-xorg-input-mouse

The current one in testing is completely unuseable on kfreebsd-*.

Changed-By: Cyril Brulebois 
Description:
 xserver-xorg-input-mouse - X.Org X server -- mouse input driver
 xserver-xorg-input-mouse-udeb - X.Org X server -- mouse input driver (udeb)

xserver-xorg-input-mouse (1:1.7.2-3) unstable; urgency=medium
 .
   * Update bsd-array-bounds.diff patch to fix crashes on kfreebsd-*,
 thanks to Petr Salinger (Closes: #681506).


Thanks

Petr


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.lrh.2.02.1207221542410.4...@sci.felk.cvut.cz

Bug#682402: unblock: libxml2/2.8.0+dfsg1-5

[Aron Xu]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock libxml2/2.8.0+dfsg1-5 which fixes CVE-2012-2807, Bug
#679280. Fix for squeeze has been agreed by security team and uploaded
to security-master just now.



-- 
Regards,
Aron Xu


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMr=8w5__t+9snstni-vlghffg3pph-uwzqog5vjvop1q5h...@mail.gmail.com

Bug#682379: unblock: chromium-browser/20.0.1132.57~r145807-1

[Giuseppe Iuculano]

On 07/22/2012 12:20 PM, Julien Cristau wrote:
> And the reason you're not replying to 681719 instead is?

Because I didn't know Michael already opened a bug.


Giuseppe.





signature.asc
Description: OpenPGP digital signature

Bug#682393: unblock: bindfs/1.10.3-2

[Eugene V. Lyubimkin]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello, please unblock package bindfs which fixes a grave bug #681647.
Diff attached.


unblock bindfs/1.10.3-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 000..5dde0bf
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,58 @@
+This package uses quilt to manage all modifications to the upstream
+source.  Changes are stored in the source package as diffs in
+debian/patches and applied during the build.
+
+To configure quilt to use debian/patches instead of patches, you want
+either to export QUILT_PATCHES=debian/patches in your environment
+or use this snippet in your ~/.quiltrc:
+
+for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do
+if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then
+export QUILT_PATCHES=debian/patches
+break
+fi
+done
+
+To get the fully patched source after unpacking the source package, cd to
+the root level of the source package and run:
+
+quilt push -a
+
+The last patch listed in debian/patches/series will become the current
+patch.
+
+To add a new set of changes, first run quilt push -a, and then run:
+
+quilt new 
+
+where  is a descriptive name for the patch, used as the filename in
+debian/patches.  Then, for every file that will be modified by this patch,
+run:
+
+quilt add 
+
+before editing those files.  You must tell quilt with quilt add what files
+will be part of the patch before making changes or quilt will not work
+properly.  After editing the files, run:
+
+quilt refresh
+
+to save the results as a patch.
+
+Alternately, if you already have an external patch and you just want to
+add it to the build system, run quilt push -a and then:
+
+quilt import -P  /path/to/patch
+quilt push -a
+
+(add -p 0 to quilt import if needed).  as above is the filename to
+use in debian/patches.  The last quilt push -a will apply the patch to
+make sure it works properly.
+
+To remove an existing patch from the list of patches that will be applied,
+run:
+
+quilt delete 
+
+You may need to run quilt pop -a to unapply patches first before running
+this command.
diff --git a/debian/changelog b/debian/changelog
index 34c18fe..d0ea609 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+bindfs (1.10.3-2) unstable; urgency=medium
+
+  * debian/control:
+- Build-depend on quilt.
+  * debian/rules:
+- Use 'dh --with quilt'.
+  * debian/patches:
+- New patch '010-readdir-pathconf-fix.patch'.
+- New patch '020-usermap-memory-fix.patch'.
+- Two patches above fix serious memory errors. Thanks to
+  Marcelo E. Magallon for the report and upstream for providing directed
+  patches. (Closes: #681647)
+  * debian/README.source:
+- Added with standard quilt intructions.
+
+ -- Eugene V. Lyubimkin   Sun, 15 Jul 2012 13:30:45 +0300
+
 bindfs (1.10.3-1) unstable; urgency=low
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index f9e64fb..c53e07e 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,8 @@ Source: bindfs
 Section: utils
 Priority: optional
 Maintainer: Eugene V. Lyubimkin 
-Build-Depends: debhelper (>= 7.0.50), autotools-dev, libfuse-dev, pkg-config
+Build-Depends: debhelper (>= 7.0.50), autotools-dev, libfuse-dev, pkg-config,
+  quilt (>= 0.46-7)
 Standards-Version: 3.9.3
 Homepage: http://code.google.com/p/bindfs/
 
diff --git a/debian/patches/010-readdir-pathconf-fix.patch b/debian/patches/010-readdir-pathconf-fix.patch
new file mode 100644
index 000..28639ac
--- /dev/null
+++ b/debian/patches/010-readdir-pathconf-fix.patch
@@ -0,0 +1,29 @@
+--- bindfs-1.10.3/src/bindfs.c	2012-05-18 16:45:33.0 +0300
 bindfs-new/src/bindfs.c	2012-07-15 12:12:39.748468808 +0300
+@@ -54,6 +54,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #ifdef HAVE_SETXATTR
+ #include 
+ #endif
+@@ -399,9 +400,16 @@
+ struct dirent *de;
+ struct stat st;
+ int result = 0;
+-(void) path;
++long pc_ret;
+ 
+-de_buf = malloc(offsetof(struct dirent, d_name) + pathconf(path, _PC_NAME_MAX) + 1);
++path = process_path(path);
++
++pc_ret = pathconf(path, _PC_NAME_MAX);
++if (pc_ret < 0) {
++DPRINTF("pathconf failed: %d", errno);
++pc_ret = NAME_MAX;
++}
++de_buf = malloc(offsetof(struct dirent, d_name) + pc_ret + 1);
+ 
+ seekdir(dp, offset);
+ while (1) {
diff --git a/debian/patches/020-usermap-memory-fix.patch b/debian/patches/020-

Bug#682392: unblock: tap-plugins/0.7.2-1

[Alessio Treglia]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package tap-plugins 0.7.2-1.

I've uploaded the most recent upstream release to unstable in order to fix
an annoying issue encountered when using one of the plugins provided by the
suite:

  - Fix sharp peaks / level jumps in the output when using the Scaling
Limiter plugin.

The debdiff between versions in testing and unstable is attached.
Thanks for considering.

unblock tap-plugins/0.7.2-1

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-26-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru tap-plugins-0.7.1/CREDITS tap-plugins-0.7.2/CREDITS
--- tap-plugins-0.7.1/CREDITS	2009-08-17 13:10:57.0 +0200
+++ tap-plugins-0.7.2/CREDITS	2012-07-08 16:16:01.0 +0200
@@ -58,6 +58,9 @@
 caused problems on 64-bit machines, found uninitialised variables via
 Valgrind, and also pinned down long lurking denormal issues. Thanks!
 
+Taku Yamamoto  investigated a buffer boundary
+related bug in Scaling Limiter and provided a patch solving the problem.
+
 
 And, of course, special thanks to the Ardour [http://ardour.org] and
 JACK [http://jackit.sf.net] development teams for their tireless
diff -Nru tap-plugins-0.7.1/debian/changelog tap-plugins-0.7.2/debian/changelog
--- tap-plugins-0.7.1/debian/changelog	2011-07-01 12:19:13.0 +0200
+++ tap-plugins-0.7.2/debian/changelog	2012-07-18 16:58:26.0 +0200
@@ -1,3 +1,14 @@
+tap-plugins (0.7.2-1) unstable; urgency=low
+
+  * Team upload.
+  * New bugfix release:
+- Fix sharp peaks / level jumps in the output when using the Scaling
+  Limiter plugin.
+  * Update debian/copyright.
+  * Bump Standards.
+
+ -- Alessio Treglia   Wed, 18 Jul 2012 16:56:59 +0200
+
 tap-plugins (0.7.1-2) unstable; urgency=low
 
   * Team upload.
diff -Nru tap-plugins-0.7.1/debian/control tap-plugins-0.7.2/debian/control
--- tap-plugins-0.7.1/debian/control	2011-07-01 12:15:04.0 +0200
+++ tap-plugins-0.7.2/debian/control	2012-07-18 16:56:40.0 +0200
@@ -5,7 +5,7 @@
 Uploaders: Jaromír Mikeš 
 Build-Depends: debhelper (>= 7.0.50~),
  sharutils
-Standards-Version: 3.9.2
+Standards-Version: 3.9.3
 DM-Upload-Allowed: yes
 Vcs-Git: git://git.debian.org/git/pkg-multimedia/tap-plugins.git
 Vcs-Browser: http://git.debian.org/?p=pkg-multimedia/tap-plugins.git
diff -Nru tap-plugins-0.7.1/debian/copyright tap-plugins-0.7.2/debian/copyright
--- tap-plugins-0.7.1/debian/copyright	2011-07-01 12:13:54.0 +0200
+++ tap-plugins-0.7.2/debian/copyright	2012-07-18 16:56:05.0 +0200
@@ -1,4 +1,4 @@
-Format: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=174
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: TAP-plugins
 Upstream-Contact: Tom Szilagyi 
 Source: http://sourceforge.net/projects/tap-plugins/files/
@@ -14,7 +14,7 @@
 
 Files: debian/*
 Copyright:
- 2010 Alessio Treglia 
+ 2010-2012 Alessio Treglia 
  2010 Jaromír Mikeš 
  2004 Anand Kumria 
 License: GPL-2+
@@ -29,9 +29,9 @@
  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.
-Comment: You should have received a copy of the GNU General Public License
- along with this package; if not, write to the Free Software
- Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301 USA
+Comment:
+ You should have received a copy of the GNU General Public License
+ along with this program.  If not, see .
  .
  On Debian systems, the complete text of the GNU General
  Public License can be found in `/usr/share/common-licenses/GPL-2'.
@@ -46,9 +46,9 @@
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
  Lesser General Public License for more details.
-Comment: You should have received a copy of the GNU Lesser General Public
- License along with this library; if not, write to the Free Software
- Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
+Comment:
+ You should have received a copy of the GNU Lesser General Public License
+ along with this program.  If not, see .
  .
- On Debian systems, the complete text of the GNU General
+ On Debian systems, the complete text of the GNU Lesser General
  Public License can be found in `/usr/share/common-licenses/LGPL-2.1'.
diff -Nru tap-plugins-0.7.1/debian/gbp.conf tap-plugins-0.7.2/debian/gbp.conf
--- tap-plugins-0.7.1/debian/gbp.conf	2011-07-01 12:12:46.0 +0200
+++ tap-plugins-0.7.2/debian/gbp.conf	2012-07-18 1

Bug#682391: unblock: wvstreams/4.6.1-5

[Johann Felix Soden]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock wvstreams/4.6.1-5. The QA upload fixes a RC bug and not
yet reported FTBFS.

Changes:

  * Disable some gcc-4.7 optimization flags to fix wrong magic_number bug.
(Closes: #674006) 
  * Disable parallel build.
  * Add Build-Depends: graphviz.

The full debdiff is attached.

unblock wvstreams/4.6.1-5

Thanks!

Regards,
 Johann Felix Soden

diff -Nru wvstreams-4.6.1/debian/changelog wvstreams-4.6.1/debian/changelog
--- wvstreams-4.6.1/debian/changelog	2012-05-18 21:53:09.0 +0200
+++ wvstreams-4.6.1/debian/changelog	2012-07-13 01:22:53.0 +0200
@@ -1,3 +1,13 @@
+wvstreams (4.6.1-5) unstable; urgency=low
+
+  * QA upload.
+  * Disable some gcc-4.7 optimization flags to fix wrong magic_number bug.
+Thanks to Peter Drysdale . (Closes: #674006) 
+  * Disable parallel build.
+  * Add Build-Depends: graphviz.
+
+ -- Johann Felix Soden   Fri, 13 Jul 2012 00:39:24 +0200
+
 wvstreams (4.6.1-4) unstable; urgency=low
 
   * QA upload.
diff -Nru wvstreams-4.6.1/debian/control wvstreams-4.6.1/debian/control
--- wvstreams-4.6.1/debian/control	2012-05-18 21:39:55.0 +0200
+++ wvstreams-4.6.1/debian/control	2012-07-13 00:54:27.0 +0200
@@ -2,7 +2,9 @@
 Section: libs
 Priority: optional
 Maintainer: Debian QA Group 
-Build-Depends: debhelper (>> 5.0.0), autotools-dev, libdb-dev, libpam0g-dev, libssl-dev, libxplc0.3.13-dev, libpopt-dev, zlib1g-dev, doxygen, libdbus-1-dev
+Build-Depends: debhelper (>> 5.0.0), autotools-dev, libdb-dev, libpam0g-dev,
+ libssl-dev, libxplc0.3.13-dev, libpopt-dev, zlib1g-dev, doxygen, libdbus-1-dev,
+ graphviz
 Build-Conflicts: valgrind
 Standards-Version: 3.9.2
 Homepage: http://alumnit.ca
diff -Nru wvstreams-4.6.1/debian/rules wvstreams-4.6.1/debian/rules
--- wvstreams-4.6.1/debian/rules	2012-05-18 21:40:45.0 +0200
+++ wvstreams-4.6.1/debian/rules	2012-07-13 01:04:47.0 +0200
@@ -34,12 +34,14 @@
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
 	CFLAGS += -O0
 else
-	CFLAGS += -O2
+	CFLAGS += -O2 -fno-tree-dce -fno-optimize-sibling-calls
 endif
 ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
 	INSTALL_PROGRAM += -s
 endif
 
+MAKEFLAGS += -j1 # parallel build broken
+
 config.status: configure
 	dh_testdir
 	# Add here commands to configure the package.
@@ -66,7 +68,7 @@
 build-arch-stamp: config.status
 
 	# Add here commands to compile the arch part of the package.
-	$(MAKE) VERBOSE=1 CXXOPTS="-fPIC -DPIC" COPTS="-fPIC -DPIC"
+	$(MAKE) VERBOSE=1 CXXOPTS="-fPIC -DPIC -fno-tree-dce -fno-optimize-sibling-calls" COPTS="-fPIC -DPIC"
 	$(MAKE) VERBOSE=1 CXXOPTS="-fPIC -DPIC" COPTS="-fPIC -DPIC" uniconf/tests/uni
 	touch build-arch-stamp
 


signature.asc
Description: This is a digitally signed message part

Bug#682390: unblock: muse/2.0-1

[Alessio Treglia]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Please allow muse 2.0-1 to join Debian Wheezy.

It brings many bugfixes since the latest release candidate currently
available in testing. Plus, upstream intends to support this release
on the long term.

You may find the debdiff at the following URL:

http://people.debian.org/~alessio/muse.debdiff

Thanks for considering.

unblock muse/2.0-1

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-26-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722112107.9371.12811.reportbug@Aspire-1410

freevo exception

[A Mennucc]

hi,

I just found out I overlooked a RC bug in freevo; I uploaded corrected
version 1.9.2b2-4  ; see attachments; please provide exception.

a.

File lists identical (after any substitutions)

Control files of package freevo: lines which differ (wdiff format)
--
Depends: debconf (>= 0.5) | debconf-2.0, python (>= 2.6.6-7~), python-freevo (= [-1.9.2b2-3),-] {+1.9.2b2-4),+} freevo-data (= [-1.9.2b2-3),-] {+1.9.2b2-4),+} mplayer, lsdvd, console-tools | kbd, debconf, adduser, xinit
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}

Control files of package freevo-data: lines which differ (wdiff format)
---
Recommends: freevo (= [-1.9.2b2-3)-] {+1.9.2b2-4)+}
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}

Control files of package freevo-doc: lines which differ (wdiff format)
--
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}

Control files of package freevo-lirc: lines which differ (wdiff format)
---
Depends: freevo (= [-1.9.2b2-3),-] {+1.9.2b2-4),+} python-pylirc, lirc
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}

Control files of package python-freevo: lines which differ (wdiff format)
-
Recommends: freevo (= [-1.9.2b2-3)-] {+1.9.2b2-4)+}
Version: [-1.9.2b2-3-] {+1.9.2b2-4+}
diff -Nru freevo-1.9.2b2/debian/changelog freevo-1.9.2b2/debian/changelog
--- freevo-1.9.2b2/debian/changelog	2012-03-23 10:47:46.0 +0100
+++ freevo-1.9.2b2/debian/changelog	2012-07-22 09:53:49.0 +0200
@@ -1,3 +1,10 @@
+freevo (1.9.2b2-4) unstable; urgency=low
+
+  * Bug fix: "fails to install due to insserv rejecting the script
+header", thanks to Andreas Beckmann (Closes: #665741).
+
+ -- A Mennucc1   Sun, 22 Jul 2012 09:53:46 +0200
+
 freevo (1.9.2b2-3) unstable; urgency=low
 
   * make sure the recordserver starts after dvbstreamer
diff -Nru freevo-1.9.2b2/debian/freevo.freevo_recordserver.init freevo-1.9.2b2/debian/freevo.freevo_recordserver.init
--- freevo-1.9.2b2/debian/freevo.freevo_recordserver.init	2012-03-17 09:39:54.0 +0100
+++ freevo-1.9.2b2/debian/freevo.freevo_recordserver.init	2012-07-22 09:54:03.0 +0200
@@ -1,10 +1,10 @@
 #! /bin/sh
 ### BEGIN INIT INFO
 # Provides:freevo-recordserver
-# Required-Start:   $remote_fs $time dvbstreamer
-# Required-Stop:$remote_fs $time dvbstreamer
-# Should-Start:
-# Should-Stop:
+# Required-Start:   $remote_fs $time
+# Required-Stop:$remote_fs $time
+# Should-Start:  dvbstreamer
+# Should-Stop:   dvbstreamer
 # Default-Start:   2 3 4 5
 # Default-Stop:		0 1 6
 # Short-Description: Starts the Freevo Home Theatre PC Platform Recordserver


signature.asc
Description: OpenPGP digital signature

Re: Freeze exception request: systemd 44-4

[Adam D. Barratt]

On Sun, 2012-07-22 at 00:33 +0200, Tollef Fog Heen wrote:
> ]] "Adam D. Barratt" 
> 
> > > Ok to upload this?  (I'm using dh-autoreconf, so no need to patch the
> > > Makefile.in file.)
> > 
> > Looks sane enough; please go ahead.
> 
> Thanks, uploading as we speak.

Unblocked; thanks.

Regards,

Adam


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1342953158.13223.136.ca...@jacala.jungle.funky-badger.org

Bug#682379: marked as done (unblock: chromium-browser/20.0.1132.57~r145807-1)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 12:20:20 +0200
with message-id <20120722102019.ge7...@radis.cristau.org>
and subject line Re: Bug#682379: unblock: 
chromium-browser/20.0.1132.57~r145807-1
has caused the Debian Bug report #682379,
regarding unblock: chromium-browser/20.0.1132.57~r145807-1
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.)


-- 
682379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package chromium-browser

chromium-browser (20.0.1132.57~r145807-1) unstable; urgency=medium
 .
   [ Michael Gilbert ]
   * New ustream stable security release:
 - [129898] High CVE-2012-2842: Use-after-free in counter handling.  Credit
   to miaubiz.
 - [130595] High CVE-2012-2843: Use-after-free in layout height tracking.
   Credit to miaubiz.
 - [133450] High CVE-2012-2844: Bad object access with JavaScript in PDF.
   Credit to Alexey Samsonov of Google.
 .
   [ Shawn Landden ]
   * Revert "Do not use binutils-gold in armel and armhf".
   * Update vpx patch to use system headers (Closes: #674728).
   * Fixup skia fixup for --- End Message ---
--- Begin Message ---
On Sun, Jul 22, 2012 at 11:12:26 +0200, Giuseppe Iuculano wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package chromium-browser
> 
And the reason you're not replying to 681719 instead is?

Cheers,
Julien


signature.asc
Description: Digital signature
--- End Message ---

Bug#682385: unblock: mod-gearman/1.3.6-1

[Stig Sandbeck Mathisen]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Please unblock package mod-gearman

#682219 is fixed by this upstream version, and can prevent nagios or
icinga from reporting an increasing amount of false positive
"CRITICALS" as time passes.

In addition, #681775 fixes a "fails to install" RC bug in the postinst
script.

unblock mod-gearman/1.3.6-1

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120722090642.2775.39218.report...@dagon.fnord.no

Bug#682367: marked as done (unblock: tcc/0.9.26~git20120612.ad5f375-6)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jul 2012 11:01:31 +0100
with message-id <1342951291.13223.133.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#682367: unblock: tcc/0.9.26~git20120612.ad5f375-6
has caused the Debian Bug report #682367,
regarding unblock: tcc/0.9.26~git20120612.ad5f375-6
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.)


-- 
682367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Please unblock package tcc

This new version fixes a bug where a long long value is not correctly
read from memory into the registers. This leads to unexpected behavior
of correctly written programs and could have security issue for these
programs. People are warned in tcc's description that the compiler is not
ready for production because it could have security problems but it
would still be good to have a fixed version when a bug is known.

The patch is small and only the fix for the bug has been included in
this upload. The relevant bug number is #681281 and is of severity
important. Attached to this mail the debdiff from the previous version.

unblock tcc/0.9.26~git20120612.ad5f375-6

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 2.6.38-ac2-ac100 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru tcc-0.9.26~git20120612.ad5f375/debian/changelog tcc-0.9.26~git20120612.ad5f375/debian/changelog
--- tcc-0.9.26~git20120612.ad5f375/debian/changelog	2012-07-09 21:30:35.0 +0800
+++ tcc-0.9.26~git20120612.ad5f375/debian/changelog	2012-07-22 00:41:21.0 +0800
@@ -1,3 +1,17 @@
+tcc (0.9.26~git20120612.ad5f375-6) unstable; urgency=low
+
+  [Paul Tagliamonte]
+* Uploading Tom's fixes on his behalf. Although he's signed this upload
+  (he issued a debdiff), I've prepared this upload. Fix verified on
+  i386.
+
+  [Thomas Preud'homme]
+* debian/patches:
+  + Fix incorrect reading of long long values on architecture with 32bits
+registers like i386 and armel (Closes: #681281).
+
+ -- Thomas Preud'homme   Sat, 21 Jul 2012 03:43:35 +0200
+
 tcc (0.9.26~git20120612.ad5f375-5) unstable; urgency=low
 
   * debian/patches:
diff -Nru tcc-0.9.26~git20120612.ad5f375/debian/patches/0006-get_reg-try-to-free-r2-for-an-SValue-first.patch tcc-0.9.26~git20120612.ad5f375/debian/patches/0006-get_reg-try-to-free-r2-for-an-SValue-first.patch
--- tcc-0.9.26~git20120612.ad5f375/debian/patches/0006-get_reg-try-to-free-r2-for-an-SValue-first.patch	1970-01-01 08:00:00.0 +0800
+++ tcc-0.9.26~git20120612.ad5f375/debian/patches/0006-get_reg-try-to-free-r2-for-an-SValue-first.patch	2012-07-22 00:31:29.0 +0800
@@ -0,0 +1,51 @@
+From 315185fe1db1296e511bec15894dad22432c9a7f Mon Sep 17 00:00:00 2001
+From: Thomas Preud'homme 
+Date: Sat, 21 Jul 2012 03:36:51 +0200
+Subject: get_reg(): try to free r2 for an SValue first
+
+To be able to load a long long value correctly on i386, gv() rely on the
+fact that when get_reg() look at an SValue it tries first to free the
+register in r2 and then r. More information about the context can be
+found at
+http://lists.nongnu.org/archive/html/tinycc-devel/2012-06/msg00017.html
+and later at
+http://lists.nongnu.org/archive/html/tinycc-devel/2012-07/msg00021.html
+
+Origin: upstream,http://repo.or.cz/w/tinycc.git/commit/d1694f7d7e6d96f64d1330c9b43491b613272b1e
+Bug-Debian: http://bugs.debian.org/681281
+Forwarded: http://lists.nongnu.org/archive/html/tinycc-devel/2012-06/msg00017.html
+Last-Updated: 2012-07-21
+Applied-Upstream: commit:d1694f7d7e6d96f64d1330c9b43491b613272b1e
+---
+ tccgen.c |9 +
+ 1 file changed, 5 insertions(+), 4 deletions(-)
+
+diff --git a/tccgen.c b/tccgen.c
+index d27bdba..71d0809 100644
+--- a/tccgen.c
 b/tccgen.c
+@@ -589,11 +589,11 @@ ST_FUNC int get_reg(int rc)
+IMPORTANT to start from the bottom to ensure that we don't
+spill registers used in gen_opi()) */
+ for(p=vstack;p<=vtop;p++) {
+-r = p->r & VT_VALMASK;
++/* look at second register (if long long) */
++r = p->r2 & VT_VALMASK;
+ if (r < VT_CONST && (reg_classes[r] & rc))
+ goto save_found;
+-/* also look at second register (if long long) */
+-r = p->r2 & VT_VALMASK;
++r = p->r & VT_VALMASK;
+ if (r < V

Re: freeze exception qpdf versioned symbols?

[Julien Cristau]

On Sat, Jul 14, 2012 at 11:00:26 -0400, Jay Berkenbilt wrote:

> 
> I have added symbol versioning to qpdf (for which I am the maintainer
> and also upstream) in a not-yet-released upstream version.  Sometime
> soon, I will be releasing a new version of qpdf with a few ABI-breaking
> changes in preparation for qpdf becoming a dependency of cups-filters,
> resulting in work being done in a google summer of code project.  While
> there are currently no packages in debian that depend on qpdf, I thought
> it might be nice to get the symbol versions into debian before wheezy
> since the next release will not be binary compatible.  I have no plans
> to make any future ABI-breaking changes as I am committed to ABI
> stability.  In this case, however, it was unavoidable as there were
> functions that took int and needed off_t.  As long as I had to break it
> anyway, I also made one change to significantly simplify one rarely used
> operation for the user.
> 
Hi Jay,

with no reverse dependencies for libqpdf3 in the archive at this point,
I think this can wait until wheezy+1.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#682379: unblock: chromium-browser/20.0.1132.57~r145807-1

[Giuseppe Iuculano]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package chromium-browser

chromium-browser (20.0.1132.57~r145807-1) unstable; urgency=medium
 .
   [ Michael Gilbert ]
   * New ustream stable security release:
 - [129898] High CVE-2012-2842: Use-after-free in counter handling.  Credit
   to miaubiz.
 - [130595] High CVE-2012-2843: Use-after-free in layout height tracking.
   Credit to miaubiz.
 - [133450] High CVE-2012-2844: Bad object access with JavaScript in PDF.
   Credit to Alexey Samsonov of Google.
 .
   [ Shawn Landden ]
   * Revert "Do not use binutils-gold in armel and armhf".
   * Update vpx patch to use system headers (Closes: #674728).
   * Fixup skia fixup for http://lists.debian.org/20120722091226.4449.1325.reportbug@sd6-mobile

Re: Non-evasive patch for SELinux handling suitable for a freeze exception?

[Axel Beckert]

Hi Cyril,

Cyril Brulebois wrote:
> (I guess you meant non-invasive in Subject?)

Ehm, yes.

> (For lazy people following at home, it's about debian/init) The patched
> init script would have:
> | set -e
> | …
> | [ -x /sbin/restorecon ] && /sbin/restorecon $SCREENDIR
> 
> Meaning you never get to do the clean-up and the chmod dance if the
> policycoreutils package isn't installed.

Meh. Thanks for spotting this!

if [ -x /sbin/restorecon ]; then
/sbin/restorecon $SCREENDIR
fi

should be better for "set -e", shouldn't it?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722091402.gf30...@sym.noone.org

Re: freeze exception qpdf versioned symbols?

[Jonathan Nieder]

Hi,

Jay Berkenbilt wrote:

> Okay, I've attached two files here.  The first is a copy of
> version-symbols.patch with the real changes, so this excludes the
> changes to the regenerated configure file.  The second file is a source
> debdiff.

I am not on the release team, so please take anything I say with a
grain of salt.

[...]
> --- qpdf-2.3.1/debian/changelog   2012-05-19 09:21:52.0 -0400
> +++ qpdf-2.3.1/debian/changelog   2012-07-18 10:20:10.0 -0400
> @@ -1,3 +1,9 @@
> +qpdf (2.3.1-5) unstable; urgency=low
> +
> +  * Enable versioned symbols.

Are the symbol versions used shared with upstream, or is this a
Debian-specific thing?

*checks*

Looks like these are Debian-private but the patch is based on 92c94e7d
(Add symbol versioning, 2012-06-20).  Ok.

[...]
> --- qpdf-2.3.1/debian/libqpdf3.shlibs 2012-04-22 10:25:08.0 -0400
> +++ qpdf-2.3.1/debian/libqpdf3.shlibs 2012-07-18 10:20:43.0 -0400
> @@ -1 +1 @@
> -libqpdf 3 libqpdf3 (>= 2.3.0)
> +libqpdf 3 libqpdf3 (>> 2.3.1-5~)

Makes sense, and this doesn't change the squeeze->wheezy upgrade path
because libqdf3/squeeze is already << 2.3.0..

[...]
> --- qpdf-2.3.1/debian/patches/versioned-symbols.patch 1969-12-31 
> 19:00:00.0 -0500
> +++ qpdf-2.3.1/debian/patches/versioned-symbols.patch 2012-07-18 
> 10:08:30.0 -0400
> @@ -0,0 +1,1044 @@
[...]
> ++# Check if LD supports linker scripts, and define conditional
> ++# HAVE_LD_VERSION_SCRIPT if so.  This functionality is currently
> ++# constrained to compilers using GNU ld on ELF systems or systems
> ++# which provide an adequate emulation thereof.
> ++AC_ARG_ENABLE([ld-version-script],
> ++  AS_HELP_STRING([--enable-ld-version-script],
> ++[enable linker version script (default is disabled)]),

Is the default really --disable?

> ++[have_ld_version_script=$enableval], [have_ld_version_script=yes])
> ++if test "$have_ld_version_script" != no; then
> ++  AC_MSG_CHECKING([if LD -Wl,--version-script works])
> ++  save_LDFLAGS="$LDFLAGS"
> ++  LDFLAGS="$LDFLAGS -Wl,--version-script=conftest.map"
> ++  cat > conftest.map < ++VERS_1 {
> ++global: sym;
[...]
> +--- /dev/null1970-01-01 00:00:00.0 +
>  qpdf-2.3.1/libqpdf.map   2012-07-18 10:08:07.677346374 -0400
> +@@ -0,0 +1,4 @@
> ++LIBQPDF_3 {
> ++  global:
> ++*;
> ++};

It would be more comforting to have a list of symbols intended for
export here, so unintentional ABI changes could be caught more easily.
Do I understand that that would be hard to make because this is a C++
library?

[...]
> +--- qpdf-2.3.1.orig/configure2011-12-28 17:20:43.0 -0500
>  qpdf-2.3.1/configure 2012-07-18 10:08:25.257346605 -0400
> +@@ -1,11 +1,9 @@
> + #! /bin/sh
> + # Guess values for system-dependent variables and create Makefiles.
> +-# Generated by GNU Autoconf 2.68 for qpdf 2.3.1.
> ++# Generated by GNU Autoconf 2.69 for qpdf 2.3.1.

Annoying, but I guess switching to running autotools on autobuilders
can wait for wheezy+1.

To sum up: except for the help string for "./configure
--enable-ld-version-script", the patch looks correct and unrisky.  It
would be nice if the changelog were more explicit about the shlibs
bump and the relationship between this and the ABI used elsewhere
(upstream and other distros).

Thanks and hope that helps,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120722071518.GA4749@burratino