Bug#680596: Unblock imview
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package imview The package was removed from unstable due to RC-bugs (#634418 and #664943). They are all fixed in version 1.1.9c-9. Revert-depends are only: imview-doc science-viewing (metapackage) med-imaging (metapackage) unblock imview/1.1.9c-9 Thanks Anton -- 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/calf6qjnb+bwuoiuxe83yvfkce2d5aqytdilvff6rb50v376...@mail.gmail.com
Bug#680600: unblock: kiwix/0.9~beta6.8-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package kiwix Previously kiwix was an candidate for wheezy and had an unblock request by Freeze-exception. We had a RC bug [1] and we had to upload a new upstream version with proper fixes to RC bug and several other bugs related to this which upstream found after RC bug report. Hence version is changed to 0.9~beta6.8-1. Now PTS shows unblock request is ignored due to version mismatch. Hence filing this bug report. Please consider unblocking kiwix. Kiwix is a good addition to Debian-Edu aka Skolelinux Wheezy version. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679945 unblock kiwix/0.9~beta6.8-1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) -- 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/20120707072024.29526.74038.reportbug@copyninja
Bug#678806: pu: package yaws/1.88-2+squeeze1
On Sat, Jul 7, 2012 at 12:41 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Then the changelog shouldn't say stable-security... With that changed, please go ahead. Done. -- Sergei Golovan -- 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/CAOq2pXFmfnkiKGRoRR=4rzrz5snjjyos8f-e06s1jkz4cng...@mail.gmail.com
Re: Freeze exception for colorhug-client 0.1.11
Michal Čihař mic...@cihar.com (04/07/2012): Okay, attaching filtered diff without translations. Thanks, doesn't look too huge or insane, so please go ahead with an upload to unstable. I guess letting it spend 15 days in unstable instead of the usual 10 days would let users catch any regression. Mraw, KiBi. signature.asc Description: Digital signature
Re: Freeze exception for exactimage (adopt+bugfixes; through unstable)
Hello, Sven Eckelmann s...@narfation.org (01/07/2012): A possible solution is a planned freeze exception for exactimage. I've prepared an upload to mentors [1] that could be used as start of an discussion about what would be seen as acceptable by the release team. All cleanup or refactoring changes were removed and only the adopt change, the program behavior bug fixes and the libpng transition were included. Even lintian warnings about the policy changes were not fixed (3.9.2 - 3.9.3). thanks, appreciated. Most of the patches are relative small and easy to understand with a little bit knowledge of the code. The only big thing standing out is the libjpeg8_compat.patch . It replaces some libjpeg62 specific files (from the libjpeg62 orig tarball) with the same files from libjpeg8 (from the libjpeg8 orig tarball) to fix the hiccups/crashes in the jpeg code related to the abi changes. It is necessary because it is not possible to build exactimage against libjpeg62-dev after the transition of libevas-dev to libjpeg-dev because this virtual package is not provided anymore by libjpeg62-dev. The libjpeg8-dev package also conflicts with libjpeg62-dev (and would create even more problems during runtime after linking both). I guess that'll be fixable for real after wheezy is released (moving everyone to $defaultlibjpeg), but I guess what you did will do for now. Please upload to unstable. I'm a bit worried about those files getting copied over, though. What if some security fix is needed in libjpeg? Maybe get that new exactimage version listed in ECC[1]? 1. http://wiki.debian.org/EmbeddedCodeCopies I would like to get feedback from the release team before I decide how to continue with the upload. exactimage (0.8.5-5) unstable; urgency=low * debian/control: - Add Daniel Stender and Sven Eckelmann as new maintainer (Closes: #587062) - Depend on libpng-dev instead of libpng12-dev (Closes: #662317) - Depend on libjpeg8-dev to avoid hiccups with other libjpeg versions * debian/patches: - Add edentify_tga_mismatch.patch, Fix misidentification of PNM as TGA (Closes: #575324) - missing_include_vector.patch, Add missing includes for std::vector - Add libjpeg8_compat.patch, Build jpeg functionality for libjpeg8 to avoid crashes and other hiccups (Closes: #679775) - Add optimize2bw_denoise.patch, Fix optimize2bw denoise crash on 64-bit systems (Closes: #679772) Given the changes, it might make sense to leave it for a longer time than usual in unstable, maybe 15-20 days. Mraw, KiBi. signature.asc Description: Digital signature
Re: Preparation for d-i beta 1
Cyril Brulebois k...@debian.org (25/06/2012): - 1st d-i upload less than 12 hours from now. - udeb freeze. Done. - 2nd upload when the kernel is ready, hopefully some time next week. I have to review a few packages we might want to get into testing soon, that should happen during this weekend. As for the kernel, linux can't migrate on its own, packages would become uninstallable. linux-latest is needed but is missing its s390 build (hence the poke on IRC and the extra Cc now). I've checked with force/force-hint that there shouldn't be any other issues once linux-latest is a candidate. Once the kernel is in testing and other udebs unblocked, there should be a new debian-installer upload early next week, which might become beta1. Mraw, KiBi. signature.asc Description: Digital signature
Bug#679816: unblock: kyotocabinet/1.2.76-2
On Sun, Jul 1, 2012 at 12:43:26 -0700, shawn wrote: If the default behavior is to not have kyotocabinet in wheezy, then I am OK with that. I think this is the way to go. Cheers, Julien signature.asc Description: Digital signature
Processed: closing 679816
Processing commands for cont...@bugs.debian.org: close 679816 Bug #679816 [release.debian.org] unblock: kyotocabinet/1.2.76-2 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 679816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679816 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.134166089418940.transcr...@bugs.debian.org
Please unblock ttf-wqy-microhei/0.2.0-beta-1.1
Hi, Could you please unblock ttf-wqy-microhei/0.2.0-beta-1.1? In this version we've got x-ttcidfont-conf removed, effectively avoids defoma for ordinary users who install Recommends by default. Also the maintainer scripts are removed to avoid possible breakage when configuring the package. I've added the maintainer Zhengpeng to CC, who has acked this NMU prior to my upload. -- 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=8w7j411-umysren-u37qn0xudx9phhb0bhkjtagfvv7...@mail.gmail.com
Re: Pre-approval request for upload of shorewall-* packages
On Fri, Jul 06, 2012 at 02:15:19PM +0200, Mehdi Dogguy wrote: Why do they _need_ to stay in sync apart the fact that upstream wants that? are there any checks performed? That is a good question. I will investigate that. Please see the attached debdiff for the proposed changes. The debdiffs look okay. Thanks. I have gone ahead and uploaded. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: [Pkg-xfce-devel] Bug#668806: Bug#668806: Bug#668806: Bits from the Release Team: Freeze approaching!
On dim., 2012-07-01 at 22:30 +0200, Yves-Alexis Perez wrote: (sorry, the --parallel was present at that time, I didn't bother to change it). I think binNMUs can be scheduled, then I'll transform this bug into an unblock request (but I'll do that at the end of the 10 days period anyway, there's no rush). Is there something preventing the binNMUs to be scheduled? There's no rush since they won't migrate anyway and maybe you want to spend time on more important post-freeze issue, but I'd appreciate a comment from the RT :) Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#680622: unblock: goobox/3.0.1-4
Package: release.debian.org User: release.debian@packages.debian.org Usertags: freeze-exception Severity: normal Please unblock package goobox Essentially 3.0.1-4 is 3.0.1-1 (from April 20th) with a few translation fixes applied. However, the road was a little bumpy, thus 3.0.1-4 closes an RC bug (namely #679554). It has (finally) build on all architectures. The long history: *) 3.0.1-1.1 was an NMU which did not work *) 3.0.2 reverted the NMU, updated a few translations and run into a FTBS on mipsel (679552). *) 3.0.3 avoided the FTBS by pregenerating the man pages on mipsl, however, the FTBS now appears on ia64 and amd64 as well *) 3.0.4 avoided those FTBS by pregenerating the man pages on all architectures except the uploading one. The full changelog of these versions (3.0.2 was before the freeze, but I include it nevertheless): goobox (3.0.1-4) unstable; urgency=high * Urgency high due to RC fix (2nd try) * Until sp is fixed generate man pages only on build machine (currently i386 chroot) and ship pregenerated ones otherwise. closes: #679554. -- Helge Kreutzmann deb...@helgefjell.de Fri, 06 Jul 2012 19:05:12 +0200 goobox (3.0.1-3) unstable; urgency=high * Urgency high due to RC fix * Until sp is fixed on mipsel (see 679552), ship pregenerated translated man pages for mipsel, closes: #679554. -- Helge Kreutzmann deb...@helgefjell.de Thu, 05 Jul 2012 19:46:19 +0200 goobox (3.0.1-2) unstable; urgency=medium * Revert broken NMU, closes: #679313. * This reopens: #677246. Since no bug report until just before the release happend, people requiring this fix will need to backport goobox after the release of Wheezy. Sorry. * po/fr.po updated from upstream git with msgcat. * help/es/es.po updated from upstream git with msgcat. * po/es.po updated from upstream git with msgcat. * po/pl.po updated from upstream git with msgcat. * po/sl.po updated from upstream git with msgcat. -- Helge Kreutzmann deb...@helgefjell.de Fri, 29 Jun 2012 10:35:53 +0200 unblock goobox/3.0.1-4 -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#680633: unblock: tcpreplay/3.4.4-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package tcpreplay Fixes RC bug#634538 unblock tcpreplay/3.4.4-1 -- 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/20120707140718.18642.24863.report...@thinker.domain.lan
Bug#680622: unblock: goobox/3.0.1-4
On Sat, Jul 07, 2012 at 02:45:43PM +0200, Helge Kreutzmann wrote: However, the road was a little bumpy, thus 3.0.1-4 closes an RC bug (namely #679554). It has (finally) build on all architectures. | + # Due to bug #679554 / 679552 | +ifeq ($(DEB_HOST_ARCH),i386) | + docbook-to-man $(MANDIR)/goobox.en.sgml debian/goobox/usr/share/man/man1/goobox.1 | po4a -v -f debian/po4a.cfg | # po4a-translate is broken, c.f. #280882 | perl -i -p -e 's# refentrytitle\dhucpackage;#\dhucpackage;#ms' $(MANDIR)/goobox.de.sgml | perl -i -p -e 's#^\s*/refentrytitle##' $(MANDIR)/goobox.de.sgml | docbook-to-man $(MANDIR)/goobox.de.sgml debian/goobox/usr/share/man/de/man1/goobox.1 | recode latin1..utf8 debian/goobox/usr/share/man/de/man1/goobox.1 | +else | + cp -iv debian/pregenerated/goobox.1 debian/goobox/usr/share/man/man1/goobox.1 | + cp -iv debian/pregenerated/goobox.1.de debian/goobox/usr/share/man/de/man1/goobox.1 | +endif What kind of fix is that? If it builds on your machine use docbook-to-man, on the buildds use pregenerated stuff? Sorry, but no. As you said it's probably not goobox's fault so it needs to be fixed somewhere else. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#680622: unblock: goobox/3.0.1-4
Hello Philipp, On Sat, Jul 07, 2012 at 08:15:17AM -0600, Philipp Kern wrote: On Sat, Jul 07, 2012 at 02:45:43PM +0200, Helge Kreutzmann wrote: However, the road was a little bumpy, thus 3.0.1-4 closes an RC bug (namely #679554). It has (finally) build on all architectures. | + # Due to bug #679554 / 679552 | +ifeq ($(DEB_HOST_ARCH),i386) | + docbook-to-man $(MANDIR)/goobox.en.sgml debian/goobox/usr/share/man/man1/goobox.1 | po4a -v -f debian/po4a.cfg | # po4a-translate is broken, c.f. #280882 | perl -i -p -e 's# refentrytitle\dhucpackage;#\dhucpackage;#ms' $(MANDIR)/goobox.de.sgml | perl -i -p -e 's#^\s*/refentrytitle##' $(MANDIR)/goobox.de.sgml | docbook-to-man $(MANDIR)/goobox.de.sgml debian/goobox/usr/share/man/de/man1/goobox.1 | recode latin1..utf8 debian/goobox/usr/share/man/de/man1/goobox.1 | +else | + cp -iv debian/pregenerated/goobox.1 debian/goobox/usr/share/man/man1/goobox.1 | + cp -iv debian/pregenerated/goobox.1.de debian/goobox/usr/share/man/de/man1/goobox.1 | +endif What kind of fix is that? If it builds on your machine use docbook-to-man, on the buildds use pregenerated stuff? Sorry, but no. As you said it's probably not goobox's fault so it needs to be fixed somewhere else. That would be sp, where I reported this as #679552. Would this bug than be serious? (Though the last maintainer upload of sp happend in 2006). Unfortunately on my systems (testing amd64 and sid i386 chroot) this bug does not occure, making it hard for me to debug. Also please note that we are talking about (translated) man pages here, not about a FTBS in the code of the program itself. Thanks! Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#680647: unblock: binutils-mingw-w64/2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package binutils-mingw-w64: it drops a erroneous
Conflicts relationship with mingw32-binutils, which is required to
allow mingw32-ocaml upgrades from squeeze using apt-get (see #662746
for details).
The diff is as follows:
diff --git a/debian/changelog b/debian/changelog
index e6866ff..056d74d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+binutils-mingw-w64 (2) unstable; urgency=low
+
+ * binutils-mingw-w64 doesn't conflict with mingw32-binutils so remove
+the relationship (helps with #662746).
+
+ -- Stephen Kitt st...@sk2.org Wed, 04 Jul 2012 22:54:01 +0200
+
binutils-mingw-w64 (1) unstable; urgency=low
[ Stephen Kitt ]
diff --git a/debian/control b/debian/control
index 9ec7885..39dcbab 100644
--- a/debian/control
+++ b/debian/control
@@ -13,7 +13,6 @@ Package: binutils-mingw-w64
Architecture: all
Depends: ${misc:Depends}, binutils-mingw-w64-i686, binutils-mingw-w64-x86-64
Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
Description: Cross-binutils for Win32 and Win64 using MinGW-w64
MinGW-w64 provides a development and runtime environment for 32- and
64-bit (x86 and x64) Windows applications using the Windows API and
@@ -25,7 +24,6 @@ Package: binutils-mingw-w64-i686
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, binutils (= ${local:Version})
Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
Breaks: binutils-mingw-w64 ( 2.22-1+1)
Replaces: binutils-mingw-w64 ( 2.22-1+1)
Description: Cross-binutils for Win32 (x86) using MinGW-w64
@@ -39,7 +37,6 @@ Package: binutils-mingw-w64-x86-64
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, binutils (= ${local:Version})
Built-Using: binutils (= ${binutils:Version})
-Conflicts: mingw32-binutils
Breaks: binutils-mingw-w64 ( 2.22-1+1)
Replaces: binutils-mingw-w64 ( 2.22-1+1)
Description: Cross-binutils for Win64 (x64) using MinGW-w64
unblock binutils-mingw-w64/2
Regards,
Stephen
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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/20120707163215.31509.76559.report...@heffalump.sk2.org
Processed: block 662746 with 680647
Processing commands for cont...@bugs.debian.org: block 662746 with 680647 Bug #662746 [mingw32-ocaml] mingw32-ocaml: fails to upgrade from squeeze 662746 was not blocked by any bugs. 662746 was not blocking any bugs. Added blocking bug(s) of 662746: 680647 thanks Stopping processing here. Please contact me if you need assistance. -- 662746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662746 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.13416831639953.transcr...@bugs.debian.org
Re: Bug#679816: unblock: kyotocabinet/1.2.76-2
On Sat, 2012-07-07 at 13:34 +0200, Julien Cristau wrote:
On Sun, Jul 1, 2012 at 12:43:26 -0700, shawn wrote:
If the default behavior is to not have kyotocabinet in wheezy, then I am
OK with that.
I think this is the way to go.
This has not changed, however, a positive review from Bart Martens led
me to ask again.
debdiff:
diff -Nru kyotocabinet-1.2.76/debian/changelog
kyotocabinet-1.2.76/debian/changelog
--- kyotocabinet-1.2.76/debian/changelog 2012-06-17 03:09:08.0
-0700
+++ kyotocabinet-1.2.76/debian/changelog 2012-07-06 10:17:54.0
-0700
@@ -1,3 +1,30 @@
+kyotocabinet (1.2.76-4) unstable; urgency=low
+
+ * use breaks/replaces for smooth upgrades following man page move
+ from -doc - -utils
+ * do not unconditionally use -m64 when available (Closes: #680058)
+ * link with --as-needed on GNU/kFreeBSD as well as Linux
+
+ -- Shawn Landden shawnland...@gmail.com Fri, 06 Jul 2012 09:33:36
-0700
+
+kyotocabinet (1.2.76-3) unstable; urgency=low
+
+ * workaround for dh_installdoc leaving empty folder is not necessary
+ on buildds
+
+ -- Shawn Landden shawnland...@gmail.com Sun, 01 Jul 2012 18:50:23
-0700
+
+kyotocabinet (1.2.76-2) unstable; urgency=low
+
+ * include static library (libkyotocabinet.a) in -dev deb per §8.3
+ * consolidate and clean up docs
+- fixed api/index.html link to work without a web server
+ * include examples in doc package
+ * improve test for atomics to remove special casing, could be
prettier however
+- fixes FTBFS on 32-bit powerpc
+
+ -- Shawn Landden shawnland...@gmail.com Sat, 30 Jun 2012 10:39:24
-0700
+
kyotocabinet (1.2.76-1) unstable; urgency=low
* Initial release. (Closes: #613450)
diff -Nru kyotocabinet-1.2.76/debian/control
kyotocabinet-1.2.76/debian/control
--- kyotocabinet-1.2.76/debian/control 2012-06-17 05:00:39.0
-0700
+++ kyotocabinet-1.2.76/debian/control 2012-07-06 21:10:33.0
-0700
@@ -35,8 +35,7 @@
Section: debug
Architecture: any
Priority: extra
-Depends: libkyotocabinet16 (= ${binary:Version}), ${shlibs:Depends},
- ${misc:Depends}
+Depends: libkyotocabinet16 (= ${binary:Version}), ${misc:Depends}
Multi-Arch: same
Description: Straightforward implementation of DBM - debugging symbols
Kyoto Cabinet is a library of routines for managing a database. The
@@ -51,7 +50,10 @@
Package: kyotocabinet-utils
Architecture: any
-Depends: kyotocabinet-doc, ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Replaces: kyotocabinet-doc ( 1.2.76-2)
+Breaks: kyotocabinet-doc ( 1.2.76-2)
+Recommends: kyotocabinet-doc
Multi-Arch: foreign
Description: Straightforward implementation of DBM - utilities
Kyoto Cabinet is a library of routines for managing a database. The
@@ -62,13 +64,15 @@
concept of data tables nor data types. Records are organized in
hash table or B+ tree.
.
- This package contains the test utilities.
+ This package contains the kcutilmgr tool, used to compile kyotocabinet
+ language bindings without Debian patches applied, and well as testing
+ and debugging utilities.
Package: kyotocabinet-doc
Section: doc
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}
-Multi-Arch: foreign
+Suggests: libkyotocabinet-dev
Description: Straightforward implementation of DBM - docs
Kyoto Cabinet is a library of routines for managing a database. The
database is a simple data file containing records, each is a pair of
@@ -95,7 +99,7 @@
Section: libdevel
Multi-Arch: same
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: libkyotocabinet16 (= ${binary:Version}), ${misc:Depends}
Description: Straightforward implementation of DBM - development headers
Kyoto Cabinet is a library of routines for managing a database. The
database is a simple data file containing records, each is a pair of
diff -Nru kyotocabinet-1.2.76/debian/copyright
kyotocabinet-1.2.76/debian/copyright
--- kyotocabinet-1.2.76/debian/copyright 2012-06-17 03:08:27.0
-0700
+++ kyotocabinet-1.2.76/debian/copyright 2012-07-06 10:17:54.0
-0700
@@ -2,8 +2,18 @@
Source: http://fallabs.com/kyotocabinet/
Files: *
-Copyright: Copyright (C) 2009-2011 FAL Labs
-License: GPL-3+ with link and FOSS exceptions
+Copyright: Copyright © 2009-2011 FAL Labs
+License: GPL-3+ or FOSS Exception or Link Exception
+
+Files: debian/*
+Copyright: Copyright © 2012 Shawn Landden shawnland...@gmail.com
+License: GPL-3+ or FOSS Exception or Link Exception
+Comment:
+ If you modify this program, you may extend the link and/or FOSS
exceptions to
+ your version, but you are not obligated to do so. If you do not wish
to do so,
+ delete one or both exception statements and/or files from your
version.
+
+License: GPL-3+
This program is free software; you can redistribute it
and/or modify it under the terms of the GNU General Public
License as published by the Free Software Foundation; either
@@ -21,8 +31,8 @@
.
On Debian GNU/Linux systems, the complete text of the GNU General
Re: Please unblock scim-chewing
Dear release team, Sorry, I didn't notice that the scim package has been built with gtk3 when I fixing the FTBFS problem for scim-chewing earlier. Please let me know if I may do another upload to make it build with gtk3. The debdiff attached which make it build against gtk3 and fixing lintien warnings. Best regards, -Andrew 2012/7/6 Luk Claes l...@debian.org: On 07/05/2012 10:06 PM, Andrew Lee wrote: Dear release team, Please unblock scim-chewing 0.3.4-2 which has fixed a FTBFS problem #676009 without other changes. unblocked Cheers Luk -- 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/4ff647fb.7050...@debian.org -- -Andrew scim-chewing.debdiff Description: Binary data
Re: CD sizes again (and BoF reminder!)
On Sun, Jul 08, 2012 at 12:03:44AM +0200, Cyril Brulebois wrote:
Ansgar Burchardt ans...@debian.org (07/07/2012):
Another question is if the release team would consider unblocking
updated packages (with just the switch to xz for binaries). I think
it would be nice to be able to get a useful desktop system using just
the first CD, but I'm not sure if they would make an exception for
this.
You may want to actually ask the release team at some point, if you want
to know. Just saying…
Thanks for the brilliant idea! :-)
Oh all mighty release team,
Ansgar has been experimenting with .deb sizes to make the packages
needed for a minimal desktop installation fit in the first CD. It looks
like that's doable by switching to xz compression for the involved
binaries. Would you grant freeze exceptions for packages that only
changes that?
See attached email and the corresponding thread on -devel for more info.
Thanks!
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences .. http://upsilon.cc/zack .. . . o
Debian Project Leader... @zack on identi.ca ...o o o
« the first rule of tautology club is the first rule of tautology club »
---BeginMessage---
Steve McIntyre st...@einval.com writes:
On Fri, Jul 06, 2012 at 09:00:32PM -0600, Ansgar Burchardt wrote:
I tried recompressing all packages in wheezy with xz. The total size
for all amd64+all packages was reduced from 42GB to 33 GB (about 20%).
A per-package listing is available from [1]
[1] http://people.debian.org/~ansgar/wheezy-20120706-with-xz.txt.gz
Would this be enough to make GNOME and/or KDE installable from a single
CD image?
Using rough calculation:
* For GNOME, it takes about 185MB out of the space used to get up to
task-gnome-desktop. Instead of being ~90MB into CD#2, that's ~100MB
inside CD#1.
* For KDE, it takes about 170MB out of the space used to get up to
task-kde-desktop. Instead of being ~70MB into CD#2, that's ~100MB
inside CD#1.
So, yes - looks like xz will make a difference here for the wheezy
release, for amd64 at least. It's enough that we'd probably even have
space for the installation manual and release notes to fit \o/.
i386 is still worse off (2 kernels instead of 1), but I don't have the
exact figures to hand.
We need a safety margin as the base system must continue to use gzip
compression. But my feelings say that 100 MB should be enough for that.
Another question is if the release team would consider unblocking
updated packages (with just the switch to xz for binaries). I think it
would be nice to be able to get a useful desktop system using just the
first CD, but I'm not sure if they would make an exception for this.
Ansgar
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87r4snohc6@marvin.43-1.org
---End Message---
signature.asc
Description: Digital signature
Bug#680674: transition: leptonlib
Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition Tags: wheezy X-Debbugs-Cc: lepton...@packages.debian.org, tesser...@packages.debian.org Hi release team, This is a request to start a small transition for wheezy. Please don't shoot me. The current leptonlib packaging ships liblept.so.3 in a package with the same name (libleptonica) as the package shipping liblept.so.1 in squeeze. That is problematic for a few reasons: 1. Upgrading libleptonica causes liblept.so.1 to be removed, breaking leptonica-progs and tesseract-ocr from squeeze, but this dependency is not declared. 2. tesseract-ocr from wheezy requires liblept.so.3, but libleptonica's shlibs file doesn't create an appropriate dependency for that. So a versioned dependency on libleptonica was hardcoded in 3.02.01-4, which will only make for trouble in future library transitions. 3. There is no reason not to allow liblept.so.1 and liblept.so.3 to be installed at the same time for a smoother upgrade, but using the same package name prevents that (policy §8.1). Therefore I would like to see libleptonica renamed to liblept3 in wheezy, so the usual shlibs and upgrade mechanisms can Just Work™. leptonlib has one reverse dependency: tesseract. That means a tiny transition: 1. fix the package name in leptonlib (bug#664176) 2. fix the hardcoded dependency in tesseract and rebuild against new leptonlib (bug#680598) 3. let both migrate to wheezy Ben file: title = leptonlib; is_affected = .depends ~ libleptonica | .depends ~ liblept3; is_good = .depends ~ liblept3; is_bad = .depends ~ libleptonica; I realize this is very late, but I think it's important, hence the request. If there's some better way to go about this, I'd be happy to hear about it. Other thoughts welcome, too. Thanks for your work, 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/20120707223645.GA3391@burratino
Bug#680676: unblock: busybox/1:1.20.0-5
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please unblock package busybox There are two goals here. First, this release updates busybox to be the same as the current upstream _bugfix_ release, adding another bugfix (more about it below), renaming a patch accepted upstream, and bumping minor version number. And second, there are 2 serious bugfixes, one of which was quite difficult to debug and affects external users. While at it, I'm also fixing a small bug in the d-i environment. This is a summary, detailed below. The bugs in question are: #679377 - http://bugs.debian.org/679377 busybox awk segfaults when called from ash and no PATH set (eg initramfs /init) This one was difficult to debug, it is about busybox awk segfaulting in unusual environment. Currently it affects various live distributions and may affect some packages which adds initramfs hooks (so the bug may made the system unbootable). The cause of this bug, and the fix, are both rather obscure, but it is the best I can do now. Full details are in the patch description (shell-ash-export-HOME.patch), together with the details about original issue, reasons why it is fixed this way and comments about the future. #680342 - http://bugs.debian.org/679377 xargs applet does not implement basic POSIX-specified features This bug is filed by me when I discovered that random scripts provided by Debian fails randomly when busybox ash is used to run them (and ash executes busybox applets directly instead of searching utils in $PATH, so most commands are from busybox). For example, invoke-rc.d fails because it uses xargs to strip ouble quotes from lists of filenames, this is one of basic POSIX requiriments, but I forgot to enable this option in busybox. The same is true for a very commonly used xargs -0, which I also forgot to enable when enabled the obvious cousin of it, find -print0. Now, the nature of busybox is such that it is easy to en/disable options like this - it affects only the applet in question and no other applet is affected. The resulting xargs applet passes all tests in busybox itself and a few external testsuites, except of a few other, more obscure, options also specified by POSIX. #406114 - http://bugs.debian.org/406114 d-i: having a tool like ping This is a wishlist bug. The change merely enables ping applet (adding 613 bytes to the executable) for Debian Installer environment. Since network install is very important, and since nowadays people often have some obscure environments to install (eg, installing over a wireless connection, or using a network card which needs a firmware, etc), at least some minimal/basic network debugging tool is desirable. This is exactly what this change does. This bugreport is here since Jan-2008, ie, for 4.5 years already. Again, it is easy in busybox to enable/disable applets without affecting other functionality. Ping applet itself is enabled in regular busybox build since forever. Now, while I was at vacation, upstream released another bugfix or stable version of busybox, numbered 1.20.2. It is the same as was in debian package 1.20.0-4, except of 3 differences: 1. Upstream applied a patch I sent them, and added it to be applied to 1.20.1 version, but the filename of the patch is different. In 1.20.0-4 Debian package, it was named ps-get-uptime.patch, upstream name is busybox-1.20.1-ps.patch, as shown at http://busybox.net/downloads/fixes-1.20.1/ . The content of the two patches is the same, with the minor difference in line offsets. 2. Upstream added another patch, fixing mke2fs utility. The upstream commit is here: http://git.busybox.net/busybox/commit/?id=c9a13116a4497f4597ad5db6eb3cac9680fd6fc4 and http://busybox.net/downloads/fixes-1.20.1/busybox-1.20.1-mke2fs.patch (the same patch, for stable series). There's a bug in busybox mke2fs utility, so that current ext4 driver in kernel does not accept filesystems created by busybox. mke2fs applet is only enabled in busybox static build, so the whole issue is not that important, but it'd be a shame to ship a known-buggy version. Also, since this applet is only shipped in busybox static build, this is a low-risk change. There's no bug for this filed against Debian, but I can do that since the bug is real and the fix actually fixes it. 3. With the two changes above, plus a few other bugfixes from upstream 1.20.1 stable series (http://busybox.net/downloads/fixes-1.20.1/ ), the resulting Debian busybox package is the same as upstream 1.20.2 stable/bugfix release, with all patches for it taken directly from upstream, with only one trivial change left: the minor version number. This set of changes - to include all changes in upstream stable/bugfix 1.20.2 release - is more cosmetic (except of the mkfs patch which fixes actual bug), but is very small and does not affect anything. The whole debdiff between current version in
openswan freeze exception
Dear release team, Unfortunately, we (Harald Jenny, the real maintainer of openswan for the past 6 months or so, and me, the one who is only doing uploads) missed the freeze deadline due to various issues. However, we feel that the version of openswan that is now in experimental (and which we plan to upload to unstable as soon as you agree to it) is indeed needed in Wheezy, because it fixes a few important bugs concerning compatibility with mobile clients such as iOS and Android devices particularly in combination with NAT traversal (which most mobile devices will have to go through). Unfortunately, fixing these bugs requires a new upstream version with a few cherry-picked patches. Internal testing indicates that it is stable and does not introduce any regressions. Would you consider openswan for a freeze exception at this time? best regards, Rene -- 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/4ff8c6fc.4040...@debian.org
Bug#680693: unblock: qemu-kvm/1.1.0+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package qemu-kvm. Please note that the package has already been uploaded to unstable, because I incorrectly assumed it is the way to go during the freeze time. Please excuse me for that, it was made due to my lack of understanding of the process. As I wrote in email on Jul-14 4fd9fc84.3050...@msgid.tls.msk.ru, https://lists.debian.org/debian-release/2012/06/msg00370.html , upstream delayed the final release of next stable qemu-kvm version due to a few last-minute regressions found there. The actual release happened 2 Jul, ie, after the wheezy freeze. I managed to upload a prerelease of the package before freeze, numbered 1.1~z0+dfsg-1 -- in last 40 minutes before freeze, when I returned from my vacation. However, this was based on a prerelease (which happened to become a release 2 days later), and it had a few glitches which are now sorted. The new uploaded package is based on the actual 1.1.0 upstream tarball, which is different from the fake upstream tarball I had previously only in one file, KVM_VERSION, -- previous version had an -rc4 in it, new version has proper 1.1.0. So the current orig.tar didn't really changed. This Debian release of the package includes fixes of a number of bugs too. These are: #679788 - http://bugs.debian.org/679788 (serious) kvm-1.0 segfaults with -M pc-1.0 (and older) and vhost-net (and a few others merged with it) Another rather trivial regression found - trivial to fix but affecting many users already, I've got 3 separate bugreports for it. Fixed by 2 patches applied to upstream master and stable branches: qemu-kvm-Add-missing-default-machine-options.patch qemu-kvm-virtio-Do-not-register-mask-notifiers-witho.patch This is the most important change in this release. #680609 - http://bugs.debian.org/680609 wrong cpus-x86_64.conf file location This is a mistake on my part. When packaging 1.1 version, I placed upstream file with various x86 CPU definitions to a wrong directory -- to /etc/kvm/ instead of /usr/share/kvm/. The resulting conffile (in dpkg terms) has never been used by this package, and is very unlikely to exists (or be modified) on any system. This release of the package puts this file into proper location, and removes the leftover from /etc/kvm/ if it is there and if we're upgrading from qemu-kvm older than 1.1.0~. There were just 2 releases (one in experimental and one in unstable) which shipped that file. #677528 - http://bugs.debian.org/677528 qemu-kvm: KVM internal error for some values of -m kvm guest segfaults during boot (in bios) when specified amount of guest memory (-m xxx) is not a multiple of page size. The fix - till upstream will find a more generic way (ie, working for all the different platforms and architectures qemu emulates - this does not affect qemu-kvm since it is x86-only) - is to truncate the amount of guest memory to a multiple of 8192 (as per upstream suggestion), and print a warning if such a truncation actually happened. This is in the patch align-ram_size-to-8k-boundary.patch the check is performed while parsing the command line, so it does not affect anything else. #680551 - http://bugs.debian.org/680551 (important) Hotplugging CPU causes kvm/qemu process (and guest) to crash kvm process segfaults when attempting to hotplug a virtual CPU. The CPU hotplug has never really worked in qemu-kvm. The patch (taken from Ubuntu) merely disables the feature when it is used, printing a warning saying just that, instead of segfaulting. Also I mentioned closure of more bugs in the changelog -- bugs which were closed by 1.1 version. Each change has been extensively tested to not cause regressions, on a set of various guest images. Each code patch presented here is either a clear bugfix, or a non-working feature removal (cpu hotplug), or an enforcer of something which is assumed but not enforced (the memsize change). Please consider unblocking. And please excuse me for doing it wrong - uploading before asking - it happened solely because I didn't understand the procedure, and now I do. The debdiff is below. unblock qemu-kvm/1.1.0+dfsg-1 Thank you! /mjt debdiff diff -Nru qemu-kvm-1.1~z0+dfsg/debian/changelog qemu-kvm-1.1.0+dfsg/debian/changelog --- qemu-kvm-1.1~z0+dfsg/debian/changelog 2012-06-30 23:21:49.0 +0400 +++ qemu-kvm-1.1.0+dfsg/debian/changelog2012-07-07 16:15:07.0 +0400 @@ -1,3 +1,22 @@ +qemu-kvm (1.1.0+dfsg-1) unstable; urgency=low + + * 1.1.0 upstream release, finally. No changes from the previous source. + * added two patches from upstream qemu-kvm/stable-1.1 branch: + qemu-kvm-Add-missing-default-machine-options.patch + qemu-kvm-virtio-Do-not-register-mask-notifiers-witho.patch + (Closes: #679788) + * mention closing of #640139, #672112 by 1.1 + * store cpus-x86_64.conf in /usr/share/kvm not /etc/kvm (Closes:
Possible testing-proposed-updates upload for circuits 1.6-1?
(Please Cc me on replies, I'm not subscribed) Hello Release-Team, I had read your freeze policy document for Wheezy[¹] and I would like to ask if circuits 1.6-1[²] can be accepted into testing-proposed-updates (I refer to rule #5, if I understood it correctly). At the time when I sent manpages for CLI tools provided by circuits, upstream, beyond accepting them, told me he was releasing a new version (1.7) soon. So I waited, but the only result for my decision was that circuits 1.6-1 entered the NEW Queue on 30th of June. I would like to have circuit 1.6-1 in Wheeze because of (beyond many upstream enhancements: currently in testing we have circuits 1.2.1-1): 1) it fix 2 important bug: #634153 and #671077 2) it add full support for Python3 Of course debdiff is *huge*, very huge, due to several upstream release from which we have on testing: $ wc -l circuits_1.6.diff 68507 circuits_1.6.diff I will upload somewhere if it's worth. Do you think it will be possible to upload circuits 1.6-1 on testing- proposed-updates? Many thanks in advance! Kind regards, [¹] http://release.debian.org/wheezy/freeze_policy.html [²] http://packages.qa.debian.org/c/circuits/news/20120703T214725Z.html -- Daniele Tricoli 'Eriol' http://mornie.org signature.asc Description: This is a digitally signed message part.
Bug#680699: unblock: flash-kernel/3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package flash-kernel Hello, flash-kernel/3.1 adds device tree support for Dreamplug device (used by freedombox). Dreamplug support has been backported into linux/3.2.21-1, which we expect it to get into wheezy sometime. Therefore, it would be really nice if we can get flash-kernel/3.1 in wheezy. unblock flash-kernel/3.1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.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/20120708011641.8776.88163.report...@polynomio.collabora.co.uk
Bug#680703: unblock: qpdfview/0.3.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock qpdfview/0.3.1-1, which is the first upstream stable release in Debian. Previous uploads are beta, and unfortunately upstream haven't made the final release in time of the freeze. -- 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=8w6qVKGCHmxS=zhk0lssqq-q-zfbg2pg6vtfx2gahmb...@mail.gmail.com
Re: Please unblock scim-chewing
Hi Ok, so that's basically changing build dependencies and a few minor fixes which I got confirmed got thorough testing, so unblocked. Cheers Luk On 07/07/2012 10:43 PM, Andrew Lee wrote: Dear release team, Sorry, I didn't notice that the scim package has been built with gtk3 when I fixing the FTBFS problem for scim-chewing earlier. Please let me know if I may do another upload to make it build with gtk3. The debdiff attached which make it build against gtk3 and fixing lintien warnings. Best regards, -Andrew 2012/7/6 Luk Claes l...@debian.org: On 07/05/2012 10:06 PM, Andrew Lee wrote: Dear release team, Please unblock scim-chewing 0.3.4-2 which has fixed a FTBFS problem #676009 without other changes. unblocked Cheers Luk -- 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/4ff647fb.7050...@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/4ff8f0ad.9060...@debian.org
Re: RM: clojure1.3/testing -- ROM; obsolete; newer version in the archive
On Mon, Jun 4, 2012 at 6:35 AM, Cyril Brulebois k...@debian.org wrote: Daigo Moriwaki da...@debian.org (03/06/2012): I have uploaded the Clojure1.4 package, which obsoletes the previous version Clojure1.3. Could you remove Clojure1.3 from testing and unstable? get it removed from unstable, that'll propagate to testing: http://wiki.debian.org/ftpmaster_Removals The clojure1.3 package still exists in unstable and testing: http://packages.qa.debian.org/c/clojure1.3.html Could you please see that again? Regards, Daigo -- Daigo Moriwaki daigo at debian dot 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/CAH79Gv8xtY8qKZcsDMMT-=osnzs9gzps189cjfxvxwrnrwg...@mail.gmail.com
Bug#680699: unblock: flash-kernel/3.1
Hi, On Sun, Jul 08, 2012 at 03:16:41AM +0200, Hector Oron wrote: Please unblock package flash-kernel Hello, flash-kernel/3.1 adds device tree support for Dreamplug device (used by freedombox). Dreamplug support has been backported into linux/3.2.21-1, which we expect it to get into wheezy sometime. Therefore, it would be really nice if we can get flash-kernel/3.1 in wheezy. unblock flash-kernel/3.1 my only concern is that /proc/device-tree/model takes precedence over /proc/cpuinfo in any case with no fallback to the latter. So if any ARM SoC gets device-tree enabled by a backport it might potentially need a change to flash-kernel, if the Hardware string does not match up with what the model file delivers. Bdale argues that the device-tree changes could potentially incur other changes so an update of flash-kernel makes sense instead of the fallback solution. @debian-boot: Is it ok to unblock flash-kernel at this point or should that be done post-beta1? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#680713: unblock: libunwind/1.0.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libunwind
The version 1.0.1-2 in unstable fixes the following bugs, which would be of
use for users and us.
* 20120707_ia64_FTBFS.patch:
- Cherry pick patch from upstream to fix FTBFS on ia64 (Closes: #680623).
[ Daigo Moriwaki ]
* debian/control: Removes libunwind8's Conflicts and Replaces with
libunwind7. (Closes: #670957)
* Imports Ubuntu's patch, supporting the armhf architecture.
Thanks to James Page james.p...@ubuntu.com. (Closes: 680308)
- 20120704_fix_arm_ftbfs.patch
- debian/control:
+ Supports armhf.
+ libatomic-ops-dev is no longer required for Build-Depends.
Regards,
Daigo
unblock libunwind/1.0.1-2
-- System Information:
Debian Release: 6.0.5
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-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
diff -Nru libunwind-1.0.1/debian/changelog libunwind-1.0.1/debian/changelog
--- libunwind-1.0.1/debian/changelog 2012-04-28 15:55:53.0 +0900
+++ libunwind-1.0.1/debian/changelog 2012-07-08 13:42:16.0 +0900
@@ -1,3 +1,21 @@
+libunwind (1.0.1-2) unstable; urgency=low
+
+ [ Luca Falavigna ]
+ * 20120707_ia64_FTBFS.patch:
+- Cherry pick patch from upstream to fix FTBFS on ia64 (Closes: #680623).
+
+ [ Daigo Moriwaki ]
+ * debian/control: Removes libunwind8's Conflicts and Replaces with
+libunwind7. (Closes: #670957)
+ * Imports Ubuntu's patch, supporting the armhf architecture.
+Thanks to James Page james.p...@ubuntu.com. (Closes: 680308)
+- 20120704_fix_arm_ftbfs.patch
+- debian/control:
+ + Supports armhf.
+ + libatomic-ops-dev is no longer required for Build-Depends.
+
+ -- Daigo Moriwaki da...@debian.org Sun, 08 Jul 2012 13:13:11 +0900
+
libunwind (1.0.1-1) unstable; urgency=low
[ Jari Aalto ]
diff -Nru libunwind-1.0.1/debian/control libunwind-1.0.1/debian/control
--- libunwind-1.0.1/debian/control 2012-04-28 15:55:53.0 +0900
+++ libunwind-1.0.1/debian/control 2012-07-08 13:42:16.0 +0900
@@ -3,7 +3,7 @@
Section: libs
Maintainer: Daigo Moriwaki da...@debian.org
Uploaders: Matthieu Delahaye matth...@debian.org, Al Stone a...@debian.org
-Build-Depends: debhelper (= 9), libatomic-ops-dev ( 0.5.1), autoconf, automake, libtool, autotools-dev
+Build-Depends: debhelper (= 9), autoconf, automake, libtool, autotools-dev
Standards-Version: 3.9.3
Homepage: http://www.nongnu.org/libunwind
Vcs-Git: git://git.debian.org/git/collab-maint/libunwind.git
@@ -12,7 +12,7 @@
Package: libunwind8-dev
Section: libdevel
-Architecture: ia64 i386 amd64 ppc64 powerpc armel
+Architecture: ia64 i386 amd64 ppc64 powerpc armel armhf
Depends: ${misc:Depends}, libunwind8 (= ${binary:Version})
Conflicts: libunwind1-dev, libunwind7-dev
Replaces: libunwind7-dev
@@ -28,10 +28,10 @@
This package includes the development support files.
Package: libunwind8
-Architecture: ia64 i386 amd64 ppc64 powerpc armel
+Architecture: ia64 i386 amd64 ppc64 powerpc armel armhf
Depends: ${misc:Depends}, ${shlibs:Depends}
-Conflicts: libunwind1-dev, libunwind7
-Replaces: libgcc1 ( 1:4.0.0-2), libunwind7
+Conflicts: libunwind1-dev
+Replaces: libgcc1 ( 1:4.0.0-2)
Description: library to determine the call-chain of a program - runtime
The primary goal of this project is to define a portable and efficient C
programming interface (API) to determine the call-chain of a program.
@@ -45,7 +45,7 @@
Package: libunwind-setjmp0-dev
Section: libdevel
-Architecture: ia64 i386 amd64 ppc64 powerpc armel
+Architecture: ia64 i386 amd64 ppc64 powerpc armel armhf
Depends: ${misc:Depends}, libunwind8-dev (= ${binary:Version}), libunwind-setjmp0 (= ${binary:Version})
Description: libunwind-based non local goto - development
The unwind-setjmp library offers a libunwind-based implementation of
@@ -57,7 +57,7 @@
This package includes the development support files
Package: libunwind-setjmp0
-Architecture: ia64 i386 amd64 ppc64 powerpc armel
+Architecture: ia64 i386 amd64 ppc64 powerpc armel armhf
Depends: ${misc:Depends}, ${shlibs:Depends}
Description: libunwind-based non local goto - runtime
The unwind-setjmp library offers a libunwind-based implementation of
diff -Nru libunwind-1.0.1/debian/patches/20120704_fix_arm_ftbfs.patch libunwind-1.0.1/debian/patches/20120704_fix_arm_ftbfs.patch
--- libunwind-1.0.1/debian/patches/20120704_fix_arm_ftbfs.patch 1970-01-01 09:00:00.0 +0900
+++ libunwind-1.0.1/debian/patches/20120704_fix_arm_ftbfs.patch 2012-07-08 13:42:16.0 +0900
@@ -0,0 +1,307 @@
+Description: Fix FTBFS on ARM based architectures
+Origin: http://git.savannah.gnu.org/gitweb/?p=libunwind.git;a=commitdiff;h=0eba2169fb19ef0707a2c96201e33769001b5f11
+
+Index:
