unblock request: upgrade-system
Greetings, I was wondering why src:upgrade-system hadn't entered Testing after 10 days and only noticed now that we have already entered The Freeze. Hurray! On the other hand, this means that I hereby need to request a freeze unblock for this recent upload. Most changes are mere polishing of what was already started in 1.6.2.0 (cleaning up debian/copyright and using --long-options for everything). There is exactly one new feature in the cron job and even then it's a minor one. Looking forward to the Release Team's response. Best Regards, Martin-Éric -- 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/CAPZXPQeT=sdfkky18z_p4har8gttpdwjtg7vo-_26bbk4m-...@mail.gmail.com
Re: unblock request: upgrade-system
Hello, Martin-Éric Racine martin-eric.rac...@iki.fi (16/07/2012): I was wondering why src:upgrade-system hadn't entered Testing after 10 days and only noticed now that we have already entered The Freeze. … On the other hand, this means that I hereby need to request a freeze unblock for this recent upload. Most changes are mere polishing of what was already started in 1.6.2.0 (cleaning up debian/copyright and using --long-options for everything). There is exactly one new feature in the cron job and even then it's a minor one. even if the diff is indeed tiny, I don't think it matches the rules described at: http://release.debian.org/wheezy/freeze_policy.html (linked from the freeze announcement). Given there's no actual bug fix, I think the current package will stay in unstable. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#681599: vim/python2.7: symbol lookup error: vim: undefined symbol: init_hashlib
Hi James, James McCoy james...@debian.org (15/07/2012): So a simple binNMU won't help because it wouldn't have a tight enough dependency and therefore could transition before python2.7, leaving a broken Vim in Wheezy. you could keep a serious bug open until python2.7 migrates, to solve the issue you're mentioning. That wouldn't help with partial upgrades though (upgrading vim without libpython2.7), so not really a solution. Shall I make a sourceful upload of Vim with a libpython2.7 (= 2.7.3-2) Depends and request it be unblocked or is there another way we should solve this? I think that's a way to go. (Another might be to get python2.7 to bump its shlibs and to get packages rebuilt against it. But really, I don't know anything about the pythonish specifics…) Mraw, KiBi. signature.asc Description: Digital signature
Bug#681764: RM: cdd -- ROM; Outdated and replaced
Package: ftp.debian.org Severity: normal I just got a hint that the source package cdd survived somehow and is keeping the binary package cdd-doc alive[1] (even if the other two binary packages cdd-common and cdd-dev are replaced by convinience upgrade packages created by the source package blends). Please remove cdd source package from testing and unstable because these are outdated and replaced by the blends source package. Kind regards Andreas. [1] http://packages.debian.org/source/testing/cdd -- 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/20120716091712.10150.51147.report...@mail.an3as.eu
Processed (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org: reassign 672749 r-base-core Bug #672749 [src:rquantlib] rquantlib: ftbfs on armel/armhf Bug reassigned from package 'src:rquantlib' to 'r-base-core'. No longer marked as found in versions rquantlib/0.3.8-2. Ignoring request to alter fixed versions of bug #672749 to the same values previously set reassign 677328 r-base-core Bug #677328 [rmysql] FTBS on armel,armhf Bug reassigned from package 'rmysql' to 'r-base-core'. No longer marked as found in versions 0.9-3-1+b1. Ignoring request to alter fixed versions of bug #677328 to the same values previously set forcemerge 679180 672749 677328 Bug #679180 [r-base-core] arm* builds fail: SHLIB_LIBADD: No such file or directory Bug #677328 [r-base-core] FTBS on armel,armhf Severity set to 'serious' from 'important' 671115 was blocked by: 674328 675836 676595 673528 650059 667428 673263 650058 660686 674122 649955 651110 674309 672714 650060 672950 666331 672619 673264 672716 677114 651317 673262 674210 677259 640818 672765 661422 673260 673183 673161 676083 649638 668232 673153 672824 672621 677328 676817 672816 672207 672588 671115 was blocking: 672928 678375 Removed blocking bug(s) of 671115: 677328 Marked as found in versions r-base/2.15.1-1. Added tag(s) patch. Bug #679180 [r-base-core] arm* builds fail: SHLIB_LIBADD: No such file or directory Added tag(s) sid and wheezy. Bug #672749 [r-base-core] rquantlib: ftbfs on armel/armhf Severity set to 'serious' from 'important' Failed to forcibly merge 679180: Not altering archived bugs; see unarchive. End of message, stopping processing here. Please contact me if you need assistance. -- 671115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671115 672749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672749 677328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677328 679180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679180 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.13424409846345.transcr...@bugs.debian.org
Bug#681689: unblock: mpd/0.17-2
On Sun, Jul 15, 2012 at 21:11:22 +0200, Alexander Wirt wrote: Upstream asked me to try so it fixes some bugs and I am at least interested in client-to-client communication and playlists for cue sheets. The former (some bugs) is quite vague, and the latter sound like new features... Cheers, Julien signature.asc Description: Digital signature
Processed: tagging 662513
Processing commands for cont...@bugs.debian.org: tags 662513 + moreinfo Bug #662513 [release.debian.org] RM: emboss/6.3.1-6 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 662513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662513 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.134244264515294.transcr...@bugs.debian.org
Processed: tagging 678178
Processing commands for cont...@bugs.debian.org: tags 678178 + squeeze Bug #678178 [release.debian.org] RM: libtrash/2.4-2 Added tag(s) squeeze. thanks Stopping processing here. Please contact me if you need assistance. -- 678178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678178 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.134244264515296.transcr...@bugs.debian.org
subversion 1.7 vs wheezy
On Sun, Jul 15, 2012 at 21:18:43 +0200, Arthur de Jong wrote: I guess it depends on where you think the subversion package is headed. If 1.7 will will be part of wheezy (1) not much else will need to happen. If it will ship with 1.6, I think either the svn2cl package will have to be removed (2) to avoid user confusion or the svn2cl component would have to be removed from the subversion-tools package (3) in wheezy. My personal preference would be 1, 3, 2 but for all of these input from the release team is needed and at least for option 3 cooperation from the subversion packagers is needed (Cc'd). I'm aware of #678137 and #678559 that are svn 1.7 related and still unfixed in sid. Is there any hope of getting a fix for those soonish? Cheers, Julien signature.asc Description: Digital signature
RM: cdd/testing -- ROM; Outdated and replaced
Hi, reportbug told me to foreward this problem also to debian-release and hereby I'm doing so. Kind regards Andreas. - Forwarded message from Andreas Tille ti...@debian.org - Date: Mon, 16 Jul 2012 11:17:12 +0200 From: Andreas Tille ti...@debian.org To: Debian Bug Tracking System sub...@bugs.debian.org Subject: RM: cdd -- ROM; Outdated and replaced Package: ftp.debian.org Severity: normal I just got a hint that the source package cdd survived somehow and is keeping the binary package cdd-doc alive[1] (even if the other two binary packages cdd-common and cdd-dev are replaced by convinience upgrade packages created by the source package blends). Please remove cdd source package from testing and unstable because these are outdated and replaced by the blends source package. Kind regards Andreas. [1] http://packages.debian.org/source/testing/cdd - End forwarded message - -- http://fam-tille.de -- 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/20120716125302.gk4...@an3as.eu
Bug#681689: marked as done (unblock: mpd/0.17-2)
Your message dated Mon, 16 Jul 2012 14:52:09 +0200 with message-id 20120716125209.gd9...@mraw.org and subject line Re: Bug#681689: unblock: mpd/0.17-2 has caused the Debian Bug report #681689, regarding unblock: mpd/0.17-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.) -- 681689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mpd 0.17 introduced a nasty regression which leads to broken mp3 output for some soundcards (see #679889). Upstream fixed this regression within git and I added the fix to the mpd package. I thought about adding dpatch support, but converting it to 3.0 (quilt) made a smaller diff to review, so I decided to go into that direction. I attached the debdiff, the package is not yet uploaded, so there is room for changes. unblock mpd/0.17-2 Thank for considering Alex -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (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 ---End Message--- ---BeginMessage--- Hello, Alexander Wirt formo...@debian.org (15/07/2012): not my day, this time its attached. per our little IRC discussion, closing this bug report. Mraw, KiBi. signature.asc Description: Digital signature ---End Message---
Re: Communication
On Sun, Jul 15, 2012 at 23:09:41 +0200, Luk Claes wrote: On 07/15/2012 04:59 PM, Cyril Brulebois wrote: Hi Luk, Hi KiBi I would be very pleased if you could communicate a little about your unblocks. Particularly, tasksel is a /slightly/ delicate package as we're trying to get d-i beta 1 out. Unblocking it without talking to anyone about it really isn't appreciated. I unblocked it as it fixes an RC bug and the diff seems reasonable. Should I comment to unblock for now? It's probably ok in this particular case, but it doesn't fit under the RC bug fixes (without other more involved changes) heading you used. Neither do a fair number of your other unblocks. So please ask first next time. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#681599: vim/python2.7: symbol lookup error: vim: undefined symbol: init_hashlib
On Mon, Jul 16, 2012 at 11:28:57 +0200, Cyril Brulebois wrote: Hi James, James McCoy james...@debian.org (15/07/2012): So a simple binNMU won't help because it wouldn't have a tight enough dependency and therefore could transition before python2.7, leaving a broken Vim in Wheezy. you could keep a serious bug open until python2.7 migrates, to solve the issue you're mentioning. That wouldn't help with partial upgrades though (upgrading vim without libpython2.7), so not really a solution. Shall I make a sourceful upload of Vim with a libpython2.7 (= 2.7.3-2) Depends and request it be unblocked or is there another way we should solve this? I think that's a way to go. (Another might be to get python2.7 to bump its shlibs and to get packages rebuilt against it. But really, I don't know anything about the pythonish specifics…) There's not a whole lot python-specific there, it's a plain bug in libpython2.7 AFAICT. Cheers, Julien signature.asc Description: Digital signature
Re: RM: cdd/testing -- ROM; Outdated and replaced
On Mon, 2012-07-16 at 14:53 +0200, Andreas Tille wrote: reportbug told me to foreward this problem also to debian-release and hereby I'm doing so. Only because you asked it to do something unnecessary. :-) [...] Please remove cdd source package from testing and unstable because these are outdated and replaced by the blends source package. Once the package is removed from unstable, britney will automatically try and remove it from testing. There's no need for a separate request for removal from testing. 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/1342443975.533.3.ca...@jacala.jungle.funky-badger.org
Bug#663681: marked as done (RM: python-libtiff/0.3.0~svn78-2)
Your message dated Mon, 16 Jul 2012 17:20:04 +0200 with message-id 20120716152004.gs7...@radis.cristau.org and subject line Re: Bug#663681: RM: python-libtiff/0.3.0~svn78-2 has caused the Debian Bug report #663681, regarding RM: python-libtiff/0.3.0~svn78-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.) -- 663681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm pylibtiff does not support the new tiff5 package. Please remove pylibtiff from testing. See #663490 for information Thanks -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Fri, Mar 30, 2012 at 20:42:22 +0200, Julien Cristau wrote: pylibtiff's code is full of ugly. You're not supposed to use find_library() and you're not supposed to go read a header file. That thing needs a rewrite IMO. I've added a removal hint. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#681788: unblock: ace-of-penguins/1.3-10
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ace-of-penguins
Target bug to fix:
A crash happens for all games when F1 is pressed
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679875
The cause
Happens only on systems where 100dpi font package is not
installed
The Fix
Add required font package to debian/control::Recommends
Also includes compared to 1.3-8
Patch 50: Full hardenining (CPPFLAGS support)
Comment
Changes according to past unblock discussion
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680951
unblock ace-of-penguins/1.3-10
$ cat ace-of-penguins-1.3-8--1.3-10.dsc.deb.diff
diff -Nru ace-of-penguins-1.3/debian/changelog
ace-of-penguins-1.3/debian/changelog
--- ace-of-penguins-1.3/debian/changelog2012-03-23 08:04:24.0
+0200
+++ ace-of-penguins-1.3/debian/changelog2012-07-12 13:35:45.0
+0300
@@ -1,3 +1,25 @@
+ace-of-penguins (1.3-10) unstable; urgency=low
+
+ * debian/series
+- (45): Add libpng 1.5 transition patch. For some reason the line
+ was mistankely deleted in 1.3-9.
+- (50): New. Included in 1.3-9 but not listed in changelog.
+ Enable CPPFLAGS, thus making full use of hardened build flags
+ (hardening=+all) added in 1.3-8. Patch thanks to Simon Ruderich
+ si...@ruderich.org
+
+ -- Jari Aalto jari.aa...@cante.net Thu, 12 Jul 2012 13:35:26 +0300
+
+ace-of-penguins (1.3-9) unstable; urgency=low
+
+ * debian/control
+- (Recommends): Add xfonts-100dpi. This fixes F1 keypress
+ segmentation fault crash on systems which do not already have the font
+ installed (Closes: #679875). Thanks to Lukas Hofmann lhfl...@gmx.de
+ for the patch.
+
+ -- Jari Aalto jari.aa...@cante.net Tue, 10 Jul 2012 12:47:52 +0300
+
ace-of-penguins (1.3-8) unstable; urgency=low
* debian/control
diff -Nru ace-of-penguins-1.3/debian/control ace-of-penguins-1.3/debian/control
--- ace-of-penguins-1.3/debian/control 2012-03-23 08:04:24.0 +0200
+++ ace-of-penguins-1.3/debian/control 2012-07-12 13:35:45.0 +0300
@@ -12,6 +12,7 @@
Architecture: any
Pre-Depends: multiarch-support
Depends: ${misc:PreDepends}, ${misc:Depends}, ${shlibs:Depends}
+Recommends: xfonts-100dpi
Description: penguin-themed solitaire games
The Ace of Penguins is a set of solitaire games inspired by the ones
available for MS Windows, but with a number of enhancements.
@@ -19,3 +20,6 @@
The package consists of the games Canfield, Freecell, Golf,
Mastermind, Merlin, Minesweeper, Pegged, Solitaire, Spider, Taipei
(with a level editor), and Thornq.
+ .
+ NOTE: If you experience problems with the F1 help key, please
+ make sure you have package xfonts-100dpi installed.
diff -Nru ace-of-penguins-1.3/debian/patches/45-libpng15
ace-of-penguins-1.3/debian/patches/45-libpng15
--- ace-of-penguins-1.3/debian/patches/45-libpng15 2012-03-23
08:04:24.0 +0200
+++ ace-of-penguins-1.3/debian/patches/45-libpng15 2012-07-12
13:35:45.0 +0300
@@ -1,5 +1,5 @@
-From: Jari Aalto jari.aa...@cante.net
-Subject: libpng 1.5 transition
+From: Nobuhiro Iwamatsu iwama...@nigauri.org
+Subject: libpng 1.5 transition Bug#635741
--- a/lib/make-imglib.c
+++ b/lib/make-imglib.c
diff -Nru ace-of-penguins-1.3/debian/patches/50-buildflags.patch
ace-of-penguins-1.3/debian/patches/50-buildflags.patch
--- ace-of-penguins-1.3/debian/patches/50-buildflags.patch 1970-01-01
02:00:00.0 +0200
+++ ace-of-penguins-1.3/debian/patches/50-buildflags.patch 2012-07-12
13:35:45.0 +0300
@@ -0,0 +1,31 @@
+From: Simon Ruderich si...@ruderich.org
+Subject: Add dupport for CPPFLAGS
+Last-Update: 2012-03-24
+
+--- ace-of-penguins-1.3.orig/lib/Makefile.in
ace-of-penguins-1.3/lib/Makefile.in
+@@ -565,10 +565,10 @@ images.c : make-imglib Makefile images.i
+ ./make-imglib -n cards -i $(srcdir)/png -d images.d $(srcdir)/images.in
images.c
+
+ make-imglib : make-imglib.c
+- $(BUILD_CC) $(srcdir)/make-imglib.c -o make-imglib -lpng -lz
++ $(BUILD_CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $(srcdir)/make-imglib.c -o
make-imglib -lpng -lz
+
+ text2c : text2c.c
+- $(BUILD_CC) $(srcdir)/text2c.c -o text2c -lpng -lz
++ $(BUILD_CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $(srcdir)/text2c.c -o
text2c -lpng -lz
+
+ # Tell versions [3.59,3.63) of GNU make to not export all variables.
+ # Otherwise a system limit (for SysV at least) may be exceeded.
+--- ace-of-penguins-1.3.orig/lib/Makefile.am
ace-of-penguins-1.3/lib/Makefile.am
+@@ -24,7 +24,7 @@ images.c : make-imglib Makefile images.i
+ ./make-imglib -n cards -i $(srcdir)/png -d images.d $(srcdir)/images.in
images.c
+
+ make-imglib : make-imglib.c
+- $(BUILD_CC) $(srcdir)/make-imglib.c -o make-imglib -lpng -lz
++ $(BUILD_CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS)
Re: unblock request for fcitx
On Fri, Jul 13, 2012 at 12:41 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 12.07.2012 11:24, Aron Xu wrote: I would like to upload an update of fcitx to unstable, applying several of upstream stable branch patches, changes are committed to git: http://anonscm.debian.org/gitweb/?p=pkg-ime/fcitx.git;a=commitdiff;h=7da4de754cafa4c683ba74ebe43e152493369787 Please could we have a full debdiff between the source package currently in testing and the new package you're proposing to upload to unstable? From the above URL, renaming patches as part of an unblock request is also not particularly helpful for review purposes. :( debdiff attached. There is a rename of a patch which I hope it does not hurt, I just want to keep them in consistent... -- Regards, Aron Xu fcitx_4.2.4.1-3.debdiff Description: Binary data
Bug#680256: unblock: liquidsoap/1.0.1-1
Hi, On Wed, 2012-07-04 at 18:34 +0200, Romain Beauxis wrote: Our bugfix release of liquidsoap has been caught in the middle of the freeze.. We had already uploaded ocaml-dtools 0.3.0 and ocaml-flac 0.1.1 when the freeze happened. However, liquidsoap 1.0.0 does not build against ocaml-dtools 0.3.0 That's rather unfortunate and implies that the version of liquidsoap currently in wheezy is RC-buggy, as we can't rebuild it if required for security updates or other post-release fixes. How involved would the changes required for 1.0.0 to be buildable against the new ocaml-dtools be? Liquidsoap 1.0.1 is a bugfix release that we have very carefully crafted to make sure that it would be a backward-compatible stable drop-in replacement for 1.0.0 users. The raw diffstat compared to the package that's currently in wheezy is 282 files changed, 3896 insertions(+), 2060 deletions(-) While that's not the largest we've been requested to review, it is quite large for a package that wasn't uploaded until after the freeze. Looking through the upstream changelog, there's quite a lot of things listed under the new heading, which are generally discouraged during a freeze. Some of the descriptions under fixes sound like unblock material, but I don't know the software well enough to know whether the others are. Given that the previous upstream release was eight months ago and the fact that the freeze would be in June has been known for the past year, would it not have been possible to have got the new version released / uploaded earlier? As it is, we're now in a position where we have to review all of the changes and decide whether they're okay. Therefore, we think it would be fine to unblock and migrate to the current testing distribution. I'd be worried if you didn't think so, given that you requested it. :-) However, at first (and third) glance the overall changes don't obviously appear to fulfil the published unblock criteria, so this is more of a request for an exception to those criteria. 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/1342455846.3728.16.ca...@jacala.jungle.funky-badger.org
Bug#681387: unblock: resiprocate
On Sat, 2012-07-14 at 01:36 +0200, Daniel Pocock wrote: On 14/07/12 01:28, Adam D. Barratt wrote: On 14.07.2012 00:14, Daniel Pocock wrote: On 12/07/12 22:11, Adam D. Barratt wrote: On 12.07.2012 20:39, Daniel Pocock wrote: Short summary of request: please give authorization to a) upload resiprocate 1.8.4-1 source package to unstable b) for unblocking 1.8.4-1 to wheezy Please could you provide a debdiff between the current source package in wheezy and the proposed 1.8.4-1 package? Attached Thanks. I was really after a source debdiff though - i.e. between the old and new .dscs Src debdiff attached It is about 2,500 lines - the biggest change is the addition of a ChangeLog file Thanks. Would it be possible to indicate which of the changes listed are included in 1.8.3 / 1.8.4? Both the changelog and the upstream website only appear to refer to 1.8 in general, with no further division. (FWIW, the upstream site also has 1.8 release now available as a news item from about six weeks /after/ 1.8.2 hit Debian.) 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/1342456700.3728.21.ca...@jacala.jungle.funky-badger.org
Bug#681446: marked as done (unblock: botan1.10/1.10.3-1)
Your message dated Mon, 16 Jul 2012 17:27:52 +0100 with message-id 1342456072.3728.18.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#681446: unblock: botan1.10/1.10.3-1 has caused the Debian Bug report #681446, regarding unblock: botan1.10/1.10.3-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.) -- 681446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package botan1.10 ABI breakage in upstream 1.10.2, see #681066 unblock botan1.10/1.10.3-1 -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 ---End Message--- ---BeginMessage--- On Sat, 2012-07-14 at 14:33 +0200, Ondřej Surý wrote: On Fri, Jul 13, 2012 at 6:45 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On 13.07.2012 09:23, Ondřej Surý wrote: Please unblock package botan1.10 ABI breakage in upstream 1.10.2, see #681066 Do you know if any of the reverse dependencies were built against the broken version and would need rebuilding? Good question. botan1.10 have only two rev B-D and softhsm was uploaded way before 1.10.2 hit the archive. Same applies to monotone. So, I would say none as an answer to your question. Okay, thanks. Unblocked. Regards, Adam---End Message---
Bug#681395: marked as done (unblock smarty-gettext)
Your message dated Mon, 16 Jul 2012 18:04:58 +0100 with message-id 1342458298.3728.26.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#681395: unblock smarty-gettext has caused the Debian Bug report #681395, regarding unblock smarty-gettext 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.) -- 681395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Package smarty-gettext 1.0b1-6 got broken by changing from smarty 3.0 to smarty 3.1. A patch against upstream 1.0b1 has been uploaded to SID with smarty-gettext 1.0b1-7. The fixed bug is documented here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680754 Please unblock transition of smarty-gettext. Thanks a lot for your work, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpqEPJn22BrU.pgp Description: Digitale PGP-Unterschrift ---End Message--- ---BeginMessage--- On Fri, 2012-07-13 at 19:01 +0200, Mike Gabriel wrote: On Do 12 Jul 2012 22:50:23 CEST Adam D. Barratt wrote: Okay, but in that case the changelog is still wrong, as there have been absolutely no changes to debian/install: --- smarty-gettext-1.0b1/debian/install 2012-05-10 18:59:25.0 + +++ smarty-gettext-1.0b1/debian/install 2012-07-08 13:07:48.0 + @@ -1,2 +1,2 @@ block.t.php usr/share/php/smarty3/plugins/ -tsmarty2c.php usr/bin/ +tsmarty2c.php usr/bin/ No newline at end of file Ok, got what you mean. So, what do you want me to do get the unblock? I don't think it's worth another upload just to fix the changelog, so I've unblocked the current package. I'd suggest fixing it in whatever VCS you use though. fwiw, adding the manpage generates new lintian output, albeit only at info level: I: smarty-gettext: hyphen-used-as-minus-sign usr/share/man/man1/tsmarty2c.1.gz:32 The line number suggests that this is due to --add-comments. Regards, Adam---End Message---
Re: Freeze exception for ruby-fast-xs 0.8.0-3
On Wed, 2012-07-11 at 01:02 +0200, Tollef Fog Heen wrote: ]] Adam D. Barratt Fair point. It's still somewhat stretching the edges of the unblock criteria though, given that chef-expander's exception is based purely on the grounds of it being in unstable at the right time (with, as you know, some debate as to whether NEW packages should have been granted an exception even then) and the bug in ruby-hpricot doesn't affect the version of the package in wheezy. Agreed on the stretching part. As for the bug in ruby-hpricot not affecting the package in wheezy, that's debatable, given the package in wheezy has an undeclared conflict with another package in the archive. (Please forgive me if I'm splitting hairs here, but I don't think the criteria has been «in the same suite» in the past, but rather whether it's got an undeclared conflict with any package in the archive. (Not that this helps, given what I want to get transitioned is ruby-fast-xs, though. :-)) It's a reasonable point, but no, it doesn't actually help with the r-f-xs unblock. ;-) On the other hand, I think that not providing chef-expander (but the rest of the chef server stack) in wheezy is providing our users with an inferior experience compared to what I think we can offer them. I've been debating this point over the past few days and under the circumstances I'm prepared to be a little flexible and grant the unblock. Hopefully we won't see any further issues arise with the packages. 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/1342459175.3728.34.ca...@jacala.jungle.funky-badger.org
Bug#681804: unblock: python-pyxattr/0.5.1-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-pyxattr Fixes RC Bug #680859. Currently in delay/2. unblock python-pyxattr/0.5.1-1.1 diff -Nru python-pyxattr-0.5.1/debian/changelog python-pyxattr-0.5.1/debian/changelog --- python-pyxattr-0.5.1/debian/changelog 2012-05-16 15:00:20.0 -0400 +++ python-pyxattr-0.5.1/debian/changelog 2012-07-16 13:32:03.0 -0400 @@ -1,3 +1,13 @@ +python-pyxattr (0.5.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix +FTBFS (Closes: #680859) +- The package only builds and installs html documentation for the python + version anyway, so python3-sphinx as a build-dep is clearly wrong + + -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 13:29:41 -0400 + python-pyxattr (0.5.1-1) unstable; urgency=low * New upstream bug-fix release, fixing reference leaks and potential diff -Nru python-pyxattr-0.5.1/debian/control python-pyxattr-0.5.1/debian/control --- python-pyxattr-0.5.1/debian/control 2012-05-16 15:00:20.0 -0400 +++ python-pyxattr-0.5.1/debian/control 2012-07-16 13:29:34.0 -0400 @@ -6,7 +6,7 @@ python (= 2.6.6-3~), python-all-dev (= 2.6.6-3~), python-all-dbg, python3-all, python3-all-dev, python3-all-dbg, libattr1-dev, python-setuptools, python3-setuptools, - python-sphinx (= 1.0.7+dfsg) | python3-sphinx + python-sphinx (= 1.0.7+dfsg) Standards-Version: 3.9.3 Homepage: http://pyxattr.k1024.org/ Vcs-Browser: http://git.k1024.org/debian-pyxattr.git
Bug#681810: unblock: python-pylibacl/0.5.1-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-pylibacl Fixes RC bug #680858. Package is currently in delay/2. unblock python-pylibacl/0.5.1-1.1 diff -Nru python-pylibacl-0.5.1/debian/changelog python-pylibacl-0.5.1/debian/changelog --- python-pylibacl-0.5.1/debian/changelog 2012-05-13 16:47:19.0 -0400 +++ python-pylibacl-0.5.1/debian/changelog 2012-07-16 14:34:17.0 -0400 @@ -1,3 +1,13 @@ +python-pylibacl (0.5.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix +FTBFS (Closes: #680858) +- The package only builds and installs html documentation for the python + version anyway, so python3-sphinx as a build-dep is clearly wrong + + -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 14:34:07 -0400 + python-pylibacl (0.5.1-1) unstable; urgency=low * New upstream version: bugfixes for refcount leaks and possible diff -Nru python-pylibacl-0.5.1/debian/control python-pylibacl-0.5.1/debian/control --- python-pylibacl-0.5.1/debian/control 2012-05-13 16:47:19.0 -0400 +++ python-pylibacl-0.5.1/debian/control 2012-07-16 14:34:35.0 -0400 @@ -6,7 +6,7 @@ python (= 2.6.6-3~), python-all-dev (= 2.6.6-3~), python-all-dbg, python3-all, python3-all-dev, python3-all-dbg, libacl1-dev, python-setuptools, python3-setuptools, - python-sphinx (= 1.0.7+dfsg) | python3-sphinx + python-sphinx (= 1.0.7+dfsg) Standards-Version: 3.9.3 Homepage: http://pylibacl.k1024.org/ Vcs-Browser: http://git.k1024.org/debian-pylibacl.git
Re: haskell-cryptocipher (+yesod) entangled with pandoc
Hi Jonas, Am Montag, den 09.07.2012, 15:32 +0200 schrieb Joachim Breitner: So we need another pandoc upload removing the use of the threaded runtime (Jonas?), then apply for a freeze exception and then get pandoc _and_ yesod into wheezy. are you reading this? Do you plan to do such a pandoc upload soon? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
NEW changes in proposedupdates
Processing changes file: kfreebsd-8_8.1+dfsg-8+squeeze3_kfreebsd-amd64.changes Rejecting. REJECT -- 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/e1sqqk0-0001tb...@franck.debian.org
Bug#681811: unblock: alembic/0.3.4+ds-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package alembic Fixes RC Bug #680855. unblock alembic/0.3.4+ds-2 diff -ruN export/debian/changelog alembic-0.3.4+ds/debian/changelog --- export/debian/changelog 2012-06-06 11:53:09.53589 -0400 +++ alembic-0.3.4+ds/debian/changelog 2012-07-16 14:52:11.175924802 -0400 @@ -1,3 +1,13 @@ +alembic (0.3.4+ds-2) unstable; urgency=low + + * Team upload + * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix +FTBFS (Closes: #680855 +- The package only builds and installs html documentation for the python + version anyway, so python3-sphinx as a build-dep is clearly wrong + + -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 14:51:28 -0400 + alembic (0.3.4+ds-1) unstable; urgency=low * Initial release. (Closes: #669404) diff -ruN export/debian/control alembic-0.3.4+ds/debian/control --- export/debian/control 2012-05-22 11:19:43.274759000 -0400 +++ alembic-0.3.4+ds/debian/control 2012-07-16 14:52:23.239924446 -0400 @@ -9,7 +9,7 @@ Homepage: http://www.bitbucket.org/zzzeek/alembic Build-Depends: debhelper (= 8), python-all, python-setuptools, python-nose, python-sqlalchemy, python-mako, - python-sphinx (= 1.0.7+dfsg) | python3-sphinx + python-sphinx (= 1.0.7+dfsg) Package: alembic Architecture: all
Bug#681804: unblock: python-pyxattr/0.5.1-1.1
On Mon, Jul 16, 2012 at 01:49:17PM -0400, Scott Kitterman wrote: Fixes RC Bug #680859. Currently in delay/2. Given the maintainer's response in the bug report, I suggest that you reschedule that to 0-days. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#681717: unblock: openjpeg/1.3+dfsg-4.4
On Mon, Jul 16, 2012 at 3:09 PM, Philipp Kern wrote: On Sun, Jul 15, 2012 at 07:05:35PM -0400, Michael Gilbert wrote: We are still in the early freeze where riskier changes are allowable, aren't we? No. There's no such thing as an early freeze that allows riskier changes this cycle. We might be convinced that certain delays in preparing a final package for the next release might have been someone else's fault, but that's no go for risky changes. Riskier may not have been the best qualifier for me to choose to describe this. The right term I should have used is invasive. Is it the release team's opinion that multiarch conversions at this point are invasive (even though multiarch is a release goal)? Best wishes, Mike -- 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/CANTw=moub79m6phfyt7hgxnjxwmrqfaqvuao5o5utc0vbpk...@mail.gmail.com
Bug#681813: unblock: dunst/0.2.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dunst
The only change between 0.2.0-1 (currently in testing) and 0.2.0-2 is
the added Provides: notification-daemon, which fixes bug #681732.
Here is the debdiff:
$ debdiff dunst_0.2.0-1_amd64.deb dunst_0.2.0-2_amd64.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Installed-Size: [-46-] {+47+}
{+Provides: notification-daemon+}
Version: [-0.2.0-1-] {+0.2.0-2+}
unblock dunst/0.2.0-2
--
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/20120716191202.31681.89058.report...@midna.zekjur.net
Bug#681717: unblock: openjpeg/1.3+dfsg-4.4
On Sun, Jul 15, 2012 at 07:05:35PM -0400, Michael Gilbert wrote: We are still in the early freeze where riskier changes are allowable, aren't we? No. There's no such thing as an early freeze that allows riskier changes this cycle. We might be convinced that certain delays in preparing a final package for the next release might have been someone else's fault, but that's no go for risky changes. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#681804: unblock: python-pyxattr/0.5.1-1.1
On Monday, July 16, 2012 08:58:56 PM Philipp Kern wrote: On Mon, Jul 16, 2012 at 01:49:17PM -0400, Scott Kitterman wrote: Fixes RC Bug #680859. Currently in delay/2. Given the maintainer's response in the bug report, I suggest that you reschedule that to 0-days. Done. -- 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/2232384.8txnQ3YLCh@scott-latitude-e6320
Bug#681811: Don't unblock
I didn't notice the second RC bug. I'll fix that one too. -- 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/2822681.yjxeoL54M2@scott-latitude-e6320
Bug#681816: Unblock paraview/3.14.1-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package paraview_3.14.1-7. The version fixes bug #680359 and has some minor fixes, including hardening build-flags. Diff is attached. unblock paraview/3.14.1-7 Thanks. Anton paraview.diff Description: Binary data
Bug#681717: unblock: openjpeg/1.3+dfsg-4.4
On Mon, Jul 16, 2012 at 3:17 PM, Michael Gilbert wrote: On Mon, Jul 16, 2012 at 3:09 PM, Philipp Kern wrote: On Sun, Jul 15, 2012 at 07:05:35PM -0400, Michael Gilbert wrote: We are still in the early freeze where riskier changes are allowable, aren't we? No. There's no such thing as an early freeze that allows riskier changes this cycle. We might be convinced that certain delays in preparing a final package for the next release might have been someone else's fault, but that's no go for risky changes. Riskier may not have been the best qualifier for me to choose to describe this. The right term I should have used is invasive. Is it the release team's opinion that multiarch conversions at this point are invasive (even though multiarch is a release goal)? I'll also plead the case that I did have the work in before the freeze, but was blocked. The original multiarch nmu was uploaded to delayed/5 on June 16th (bug #675773), but it was canceled and blocked shortly thereafter. Then, I didn't get the go ahead to upload again until after the release team made a call on the 1.5 transition. I was busy the following days and didn't get to it again until July 2nd (two days after the freeze) when I uploaded to delayed/5. Best wishes, Mike -- 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/CANTw=MN+B=wj7bvoeha+lk-50_fjatalf3prcum6qwbtwwh...@mail.gmail.com
Bug#681810: Rescheduled
Rescheduled to 0 day based on maintainer feedback. -- 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/2901869.0V85hgD1oZ@scott-latitude-e6320
Bug#681817: Unblock freeglut/2.6.0-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package freeglut_2.6.0-4. The version fixes 2 bugs: #681513 (was introduced by me in the last upload) and #430160 (an old one, the patch appeared in BTS recently). Diff is attached. unblock freeglut/2.6.0-4 Thanks. Anton freeglut.diff Description: Binary data
wmii freeze exception
Hello,
There's a nasty bug in wmii, #628575. It's already fixed upstream, and
it's already packaged by me, but that version is certainly unsuitable
for current release so given short enough timeframe I didn't bother
trying to upload it to unstable via my sponsor. However, I've
backported the patch for this particular bug, so users of 3.9.2 can
have it fixed.
Basically, the fix is to add some NULL pointer checks, plus some
changes in boundaries calculations. It's been tested quite extensively:
I've been using patched wmii every day for a whole year without any
troubles. A debdiff is attached, a .dsc can be found here:
http://mentors.debian.net/debian/pool/main/w/wmii/wmii_3.9.2+debian-4.dsc
Please review it an tell me if it fits to be uploaded to unstable with a
freeze exception for wheezy/testing.
P.S. Please Cc me as I'm not subscribed to this list.
--
WBR, Andrew
diff -Nru wmii-3.9.2+debian/debian/changelog wmii-3.9.2+debian/debian/changelog
--- wmii-3.9.2+debian/debian/changelog 2011-07-06 10:05:26.0 +0200
+++ wmii-3.9.2+debian/debian/changelog 2012-07-16 13:23:38.0 +0200
@@ -1,3 +1,11 @@
+wmii (3.9.2+debian-4) unstable; urgency=low
+
+ * QA upload.
+ * Fix crashes when additional displays are added (backported patch from
+upstream, closes: #628575).
+
+ -- Andrew O. Shadura bugzi...@tut.by Mon, 16 Jul 2012 13:22:40 +0200
+
wmii (3.9.2+debian-3) unstable; urgency=low
* QA upload.
diff -Nru wmii-3.9.2+debian/debian/patches/05-fix-xrandr-crash.patch wmii-3.9.2+debian/debian/patches/05-fix-xrandr-crash.patch
--- wmii-3.9.2+debian/debian/patches/05-fix-xrandr-crash.patch 1970-01-01 01:00:00.0 +0100
+++ wmii-3.9.2+debian/debian/patches/05-fix-xrandr-crash.patch 2012-07-16 13:11:36.0 +0200
@@ -0,0 +1,128 @@
+Description: Fix crash when adding a second display
+Author: Kris Maglione k...@suckless.org
+Author: Andrew O. Shadoura bugzi...@tut.by
+Bug-Debian: http://bugs.debian.org/628575
+
+--- a/cmd/wmii/fns.h
b/cmd/wmii/fns.h
+@@ -22,21 +22,27 @@
+ /* Grotesque, but worth it. */
+
+ #define foreach_area(v, s, a) \
+- with(int, __alive)\
+- with(Area*, __anext) \
+- for(s=0; _cond(s = nscreens, 0); _cont(s++)) \
+- for((a)=(s nscreens ? (v)-areas[s] : v-floating), __anext=(a)-next; _cond(a, 1); _cont(((a)=__anext) (__anext=(a)-next)))
++ with(int, __alive)\
++ with(Area*, __anext)\
++ for(s=0; _cond(s = nscreens, 0); _cont(s++)) \
++ for((a)=(s nscreens ? (v)-areas[s] : v-floating), __anext=((a)?(a)-next:NULL); \
++ _cond(a, 1); \
++ _cont(((a)=__anext) (__anext=(a)-next)))
+
+ #define foreach_column(v, s, a) \
+- with(int, __alive) \
+- with(Area*, __anext) \
+- for(s=0; _cond(s nscreens, 0); _cont(s++)) \
+- for((a)=(v)-areas[s], __anext=(a)-next; _cond(a, 1); _cont(((a)=__anext) (__anext=(a)-next)))
++ with(int, __alive)\
++ with(Area*, __anext)\
++ for(s=0; _cond(s nscreens, 0); _cont(s++)) \
++ for((a)=(v)-areas[s], __anext=((a)?(a)-next:NULL); \
++ _cond(a, 1);\
++ _cont(((a)=__anext) (__anext=(a)-next)))
+
+ #define foreach_frame(v, s, a, f) \
+ with(Frame*, __fnext) \
+ foreach_area(v, s, a) \
+- for((void)(((f)=(a)-frame) (__fnext=(f)-anext)); _cond(f, 2); _cont(((f)=__fnext) (__fnext=(f)-anext)))
++ for((void)(((f)=(a)-frame) (__fnext=(f)?((f)-anext):NULL)); \
++ _cond(f, 2); \
++ _cont(((f)=__fnext) (__fnext=(f)-anext)))
+
+ #define btassert(arg, cond) \
+ (cond ? fprint(1, __FILE__:%d: failed assertion: #cond \n, __LINE__), backtrace(arg), true : false)
+--- a/cmd/wmii/message.c
b/cmd/wmii/message.c
+@@ -505,6 +505,12 @@
+ return nil;
+ }
+
++ if(!strcmp(s, xinerama)) {
++ setenv(XINERAMA_SCREENS, m-pos, 1);
++ init_screens();
++ return nil;
++ }
++
+ switch(getsym(s)) {
+ case LBAR: /* bar on? top | bottom */
+ s = msg_getword(m);
+--- a/cmd/wmii/view.c
b/cmd/wmii/view.c
+@@ -86,7 +86,6 @@
+ for(i=0; i nscreens; i++)
+ view_init(v, i);
+
+-
+ area_focus(v-firstarea);
+
+ v-next = *vp;
+@@ -108,6 +107,7 @@
+ void
+ view_init(View *v, int iscreen) {
+ v-r[iscreen] = screens[iscreen]-r;
++ v-pad[iscreen] = ZR;
+ v-areas[iscreen] = nil;
+ column_new(v, nil, iscreen, 0);
+ }
+@@ -149,6 +149,7 @@
+ }
+ free(v-areas);
+ free(v-r);
++ free(v-pad);
+ free(v);
+ ewmh_updateviews();
+ }
+@@ -207,26 +208,39 @@
+ WMScreen *scrn;
+ Strut *strut;
+ Frame *f;
++ int left, right, top, bottom;
+ int s, i;
+- /* These short variable names are hell, eh? */
+
+ /* XXX:
+ if(v != selview)
+ return false;
+ */
++
++ top = 0;
++ left = 0;
++ right = 0;
++ bottom = 0;
+ vec.n = 0;
+ for(f=v-floating-frame; f; f=f-anext) {
+ strut = f-client-strut;
+ if(!strut)
+ continue;
++ /* Can do better in the future. */
++ top = max(top, strut-top.max.y);
++ left = max(left, strut-left.max.x);
++ right = min(right,
Bug#681813: marked as done (unblock: dunst/0.2.0-2)
Your message dated Mon, 16 Jul 2012 20:45:36 +0100
with message-id 1342467936.3728.35.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#681813: unblock: dunst/0.2.0-2
has caused the Debian Bug report #681813,
regarding unblock: dunst/0.2.0-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.)
--
681813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dunst
The only change between 0.2.0-1 (currently in testing) and 0.2.0-2 is
the added Provides: notification-daemon, which fixes bug #681732.
Here is the debdiff:
$ debdiff dunst_0.2.0-1_amd64.deb dunst_0.2.0-2_amd64.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Installed-Size: [-46-] {+47+}
{+Provides: notification-daemon+}
Version: [-0.2.0-1-] {+0.2.0-2+}
unblock dunst/0.2.0-2
---End Message---
---BeginMessage---
On Mon, 2012-07-16 at 21:12 +0200, Michael Stapelberg wrote:
Please unblock package dunst
The only change between 0.2.0-1 (currently in testing) and 0.2.0-2 is
the added Provides: notification-daemon, which fixes bug #681732.
Here is the debdiff:
$ debdiff dunst_0.2.0-1_amd64.deb dunst_0.2.0-2_amd64.deb
fwiw, when we ask for debdiffs we (almost always) mean between the
source packages, rather than the resulting binaries.
Unblocked; thanks.
Regards,
Adam---End Message---
Bug#681811: marked as done (unblock: alembic/0.3.4+ds-2)
Your message dated Mon, 16 Jul 2012 20:46:34 +0100 with message-id 1342467994.3728.36.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#681811: unblock: alembic/0.3.4+ds-2 has caused the Debian Bug report #681811, regarding unblock: alembic/0.3.4+ds-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.) -- 681811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package alembic Fixes RC Bug #680855. unblock alembic/0.3.4+ds-2 diff -ruN export/debian/changelog alembic-0.3.4+ds/debian/changelog --- export/debian/changelog 2012-06-06 11:53:09.53589 -0400 +++ alembic-0.3.4+ds/debian/changelog 2012-07-16 14:52:11.175924802 -0400 @@ -1,3 +1,13 @@ +alembic (0.3.4+ds-2) unstable; urgency=low + + * Team upload + * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix +FTBFS (Closes: #680855 +- The package only builds and installs html documentation for the python + version anyway, so python3-sphinx as a build-dep is clearly wrong + + -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 14:51:28 -0400 + alembic (0.3.4+ds-1) unstable; urgency=low * Initial release. (Closes: #669404) diff -ruN export/debian/control alembic-0.3.4+ds/debian/control --- export/debian/control 2012-05-22 11:19:43.274759000 -0400 +++ alembic-0.3.4+ds/debian/control 2012-07-16 14:52:23.239924446 -0400 @@ -9,7 +9,7 @@ Homepage: http://www.bitbucket.org/zzzeek/alembic Build-Depends: debhelper (= 8), python-all, python-setuptools, python-nose, python-sqlalchemy, python-mako, - python-sphinx (= 1.0.7+dfsg) | python3-sphinx + python-sphinx (= 1.0.7+dfsg) Package: alembic Architecture: all ---End Message--- ---BeginMessage--- On Mon, 2012-07-16 at 15:05 -0400, Scott Kitterman wrote: Please unblock package alembic Fixes RC Bug #680855. Unblocked; thanks. Regards, Adam---End Message---
Bug#680256: unblock: liquidsoap/1.0.1-1
Hi Adam and thanks for your response, 2012/7/16 Adam D. Barratt a...@adam-barratt.org.uk: On Wed, 2012-07-04 at 18:34 +0200, Romain Beauxis wrote: Our bugfix release of liquidsoap has been caught in the middle of the freeze.. We had already uploaded ocaml-dtools 0.3.0 and ocaml-flac 0.1.1 when the freeze happened. However, liquidsoap 1.0.0 does not build against ocaml-dtools 0.3.0 That's rather unfortunate and implies that the version of liquidsoap currently in wheezy is RC-buggy, as we can't rebuild it if required for security updates or other post-release fixes. How involved would the changes required for 1.0.0 to be buildable against the new ocaml-dtools be? Liquidsoap 1.0.1 is a bugfix release that we have very carefully crafted to make sure that it would be a backward-compatible stable drop-in replacement for 1.0.0 users. The raw diffstat compared to the package that's currently in wheezy is 282 files changed, 3896 insertions(+), 2060 deletions(-) While that's not the largest we've been requested to review, it is quite large for a package that wasn't uploaded until after the freeze. Looking through the upstream changelog, there's quite a lot of things listed under the new heading, which are generally discouraged during a freeze. Some of the descriptions under fixes sound like unblock material, but I don't know the software well enough to know whether the others are. Given that the previous upstream release was eight months ago and the fact that the freeze would be in June has been known for the past year, would it not have been possible to have got the new version released / uploaded earlier? As it is, we're now in a position where we have to review all of the changes and decide whether they're okay. Therefore, we think it would be fine to unblock and migrate to the current testing distribution. I'd be worried if you didn't think so, given that you requested it. :-) However, at first (and third) glance the overall changes don't obviously appear to fulfil the published unblock criteria, so this is more of a request for an exception to those criteria. I understand your concern. It was our initial plan to have a stable release just before the freeze. However, the release itself was delayed in order to make sure that we had properly tested backward compatibility and stability of the new changes, which is why it got stuck in the middle of the actual freeze. As both Debian maintainer of the package and part of the upstream team, I am positively convinced that this release meets the expected stability and functionalities for the next Debian stable release. Finally, since liquidsoap has no packages depending on it, unblocking its migration is of no risk at all for the distribution as a whole. If for any reason, you prefer to go with the current package, then we'll do our best to fix what needs to be fixed directly in the testing distribution. Have a good day, Romain -- 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/CABWZ6OTat8kU6HpuKFfHXVCK5teOjm3s40W2hRB=fu91na0...@mail.gmail.com
Bug#680693: marked as done (unblock: qemu-kvm/1.1.0+dfsg-1)
Your message dated Mon, 16 Jul 2012 22:03:41 +0200 with message-id 20120716200341.ga14...@radis.cristau.org and subject line Re: Bug#680693: unblock: qemu-kvm/1.1.0+dfsg-1 has caused the Debian Bug report #680693, regarding unblock: qemu-kvm/1.1.0+dfsg-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.) -- 680693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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
Bug#681290: marked as done (unblock: spice-gtk/0.12-4)
Your message dated Mon, 16 Jul 2012 22:08:05 +0200
with message-id 20120716200805.ga14...@radis.cristau.org
and subject line Re: Bug#681290: unblock: spice-gtk/0.12-4
has caused the Debian Bug report #681290,
regarding unblock: spice-gtk/0.12-4
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.)
--
681290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock spice-gtk.
I upload 0.12-3 to unstable at 29th Jun, and
find a bug[1] which forbit other package to
compile. Then I uploaded 0.12-4 at 9th July,
and this cause 0.12-3 cannot automatically
migrate to testing
The difference between 0.12-3 and 0.12-4 is slight, just
copy .version and .tarball-version to build directory.
for the build script use the version information in
.tarball-version to determine the version it is building.
The difference between 0.12-3 and 0.12-4 is:
liang@guoliangc:~/opt/src/spice/spice-gtk$ git diff unstable/0.12-3
unstable/0.12-4
diff --git a/debian/changelog b/debian/changelog
index 263fc96..161d6e3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+spice-gtk (0.12-4) unstable; urgency=low
+
+ * Correct version problem in *.pc (Closes: #680290)
+
+ -- Liang Guo guoli...@debian.org Mon, 09 Jul 2012 00:36:14 +0800
+
spice-gtk (0.12-3) unstable; urgency=low
* Add patch make-celt-to-be-optional.patch
diff --git a/debian/rules b/debian/rules
index 94eccd2..29c2b71 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,6 +27,7 @@ build-stamp: build-gtk3-stamp build-gtk2-stamp
build-gtk2-stamp:
mkdir build-gtk2
ls |grep -v debian|grep -v build-gtk2|grep -v build-gtk3|xargs -i cp -r
{} build-gtk2/
+ cp .version .tarball-version build-gtk2/
cd build-gtk2 autoreconf
cd build-gtk2 ./configure --prefix=/usr
--libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
--enable-smartcard=no --with-gtk=2.0 --disable-static \
@@ -39,6 +40,7 @@ build-gtk2-stamp:
build-gtk3-stamp:
mkdir build-gtk3
ls |grep -v debian|grep -v build-gtk2|grep -v build-gtk3|xargs -i cp -r
{} build-gtk3/
+ cp .version .tarball-version build-gtk3/
cd build-gtk3 autoreconf
cd build-gtk3 ./configure --prefix=/usr
--libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
--enable-smartcard=no --with-gtk=3.0 --disable-static \
liang@guoliangc:~/opt/src/spice/spice-gtk$
But current version in testing is 0.12-1, So I
think it is necesary to explain the changes
since 0.12-1.
In the 0.12-2, the primary change is add
support to usb redirect and multiarch support.
The detailed changes are:
liang@guoliangc:~/opt/src/spice/spice-gtk$ git diff unstable/0.12-1
unstable/0.12-2
diff --git a/debian/changelog b/debian/changelog
index 5e42d70..a1952a0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+spice-gtk (0.12-2) unstable; urgency=low
+
+ * Enable usb redirect (Closes: #677662)
+ * Switch to vala 0.16 (Closes: #675665)
+ * Enable multiarch for libspice-client-glib-2.0-1,
+libspice-client-gtk-2.0-1, libspice-client-gtk-3.0-1
+ * Build with hardening flags
+ * Use dpkg-statoverride to handle setuid bits
+
+ -- Liang Guo guoli...@debian.org Fri, 25 May 2012 21:52:45 +0800
+
spice-gtk (0.12-1) unstable; urgency=low
* New upstream release
diff --git a/debian/compat b/debian/compat
index 45a4fb7..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-8
+9
diff --git a/debian/control b/debian/control
index c705d39..583766e 100644
--- a/debian/control
+++ b/debian/control
@@ -1,9 +1,9 @@
Source: spice-gtk
Section: misc
Priority: optional
-Maintainer: Liang Guo bluestonech...@gmail.com
+Maintainer: Liang Guo guoli...@debian.org
Build-Depends:
- debhelper (= 8.0.0),
+ debhelper (= 9),
libspice-protocol-dev (= 0.10.1),
libspice-server-dev,
libpixman-1-dev (= 0.17.7),
@@ -14,8 +14,8 @@ Build-Depends:
libcairo2-dev (= 1.2.0),
libpulse-dev,
libusb-1.0-0-dev,
- valac-0.14,
- libvala-0.14-dev,
+ valac-0.16,
+ libvala-0.16-dev,
python-all,
python-gtk2-dev (= 2.0.0),
python-pyparsing,
@@ -26,6 +26,11 @@ Build-Depends:
libgirepository1.0-dev,
gir1.2-gtk-2.0,
libtext-csv-perl,
+ libusbredirhost-dev,
+ libacl1-dev,
+ libpolkit-agent-1-dev,
+ libpolkit-gobject-1-dev,
+ dpkg-dev (= 1.16.1~),
Standards-Version: 3.9.3
X-Python-Version: = 2.5
Homepage: http://www.spice-space.org/
@@ -46,6 +51,8 @@ Description:
Bug#681822: unblock: alembic/0.3.4+ds-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package alembic
Fixes RC bug #680854. Apologies for two unblock requests on the same
package so close together. I didn't get far enough down on my list before
uploading the last one. Attached debdiff is Wheezy - Sid.
unblock alembic/0.3.4+ds-3
diff -Nru alembic-0.3.4+ds/debian/changelog alembic-0.3.4+ds/debian/changelog
--- alembic-0.3.4+ds/debian/changelog 2012-06-06 17:15:25.0 -0400
+++ alembic-0.3.4+ds/debian/changelog 2012-07-16 16:20:40.0 -0400
@@ -1,3 +1,26 @@
+alembic (0.3.4+ds-3) unstable; urgency=low
+
+ * Team upload
+ * Build-depend on python2.6-argparse to support python2.6 tests
+ (Closes: #680854)
+ * Suggest python2.6-argparse as it is needed to run with python2.6, but
+multiple depends require python2.7 to be installed - running with
+python2.6 should be very unusual and pulling in the non-standard argparse
+on all installations for this is not a good thing
+ * Fix copy/paste error in debian/changelog from previous upload
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 15:42:34 -0400
+
+alembic (0.3.4+ds-2) unstable; urgency=low
+
+ * Team upload
+ * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix
+FTBFS (Closes: #680855
+- The package only has a python version anyway, so python3-sphinx as a
+ build-dep is clearly wrong
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 14:51:28 -0400
+
alembic (0.3.4+ds-1) unstable; urgency=low
* Initial release. (Closes: #669404)
diff -Nru alembic-0.3.4+ds/debian/control alembic-0.3.4+ds/debian/control
--- alembic-0.3.4+ds/debian/control 2012-05-24 16:50:52.0 -0400
+++ alembic-0.3.4+ds/debian/control 2012-07-16 16:19:22.0 -0400
@@ -9,13 +9,14 @@
Homepage: http://www.bitbucket.org/zzzeek/alembic
Build-Depends: debhelper (= 8), python-all, python-setuptools,
python-nose, python-sqlalchemy, python-mako,
- python-sphinx (= 1.0.7+dfsg) | python3-sphinx
+ python2.6-argparse, python-sphinx (= 1.0.7+dfsg)
Package: alembic
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, ${sphinxdoc:Depends},
python-sqlalchemy, python-mako
Recommends: python-pkg-resources
+Suggests: python2.6-argparse
Description: lightweight database migration tool for SQLAlchemy
Alembic is a new database migration tool, written by the author
of SQLAlchemy. A migration tool offers the following functionality:
Re: Using FreeDesktop MIME entries directly in mime-support (Re: Fixing the mime horror ini Debian).
Charles Plessy ple...@debian.org (16/07/2012): If nobody else volunteers, I propose to start a maintenance group for the mime-support package, that I would store in a Git repository on Alioth's collab-maint group. I think that's a perfect use case for collab-maint. László, do you really need a dedicated group for that? Mraw, KiBi. signature.asc Description: Digital signature
Bug#681827: unblock: uwsgi/1.2.3+dfsg-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package uwsgi
In order to fix RC bug #680132 a binary package uwsgi-plugin-luajit had
to be removed. Luajit will not be a part of Wheezy and
uwsgi-plugin-luajit Build-Depends on libluajit-5.1-dev. I also removed
uwsgi-plugin-luajit from dependencies for uwsgi-app-integration-plugins
and all occurrences of luajit in debian/rules.
I have also added an upstream patch for fixing an important memory leak.
I am sending the diff with changes from 1.2.3+dfsg-1 and 1.2.3+dfsg-2
releases.
unblock uwsgi/1.2.3+dfsg-2
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.4-trunk-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 --git a/debian/changelog b/debian/changelog
index ba7fe87..61361fe 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+uwsgi (1.2.3+dfsg-2) unstable; urgency=low
+
+ * Remove uwsgi-plugin-luajit binary package. (Closes: #680132)
+ - Remove libluajit-5.1-dev from Build-Depends.
+ - Remove uwsgi-plugin-luajit from dependencies for
+ uwsgi-app-integration-plugins.
+ - Remove all occurrences of luajit plugin in debian/rules.
+ * Include upstream patch to fix a memory leak in python uwsgi.workers().
+
+ -- Janos Guljas ja...@resenje.org Mon, 09 Jul 2012 03:32:09 +0200
+
uwsgi (1.2.3+dfsg-1) unstable; urgency=low
* New upstream release.
diff --git a/debian/control b/debian/control
index 153d813..029f5f7 100644
--- a/debian/control
+++ b/debian/control
@@ -15,7 +15,6 @@ Build-Depends:
libjansson-dev,
libldap2-dev,
liblua5.1-0-dev,
- libluajit-5.1-dev [i386 amd64 kfreebsd-i386 armel],
libperl-dev,
libpq-dev,
libsqlite3-dev,
@@ -169,7 +168,6 @@ Depends: ${misc:Depends},
uwsgi-plugin-jvm-openjdk-6 (= ${binary:Version}),
uwsgi-plugin-jwsgi-openjdk-6 (= ${binary:Version}),
uwsgi-plugin-lua5.1 (= ${binary:Version}),
- uwsgi-plugin-luajit (= ${binary:Version}) [i386 amd64 kfreebsd-i386 armel],
uwsgi-plugin-psgi (= ${binary:Version}),
uwsgi-plugin-python (= ${binary:Version}),
uwsgi-plugin-python3 (= ${binary:Version}),
@@ -185,7 +183,7 @@ Description: plugins for integration of uWSGI and application
This dependency package provides plugins for integration of uWSGI and
application:
* CGI, Erlang, Java (OpenJDK 6), JWSGI (OpenJDK 6),
- Lua WSAPI (Lua 5.1/LuaJIT), Perl PSGI, Python WSGI (Python/Python 3),
+ Lua WSAPI (Lua 5.1), Perl PSGI, Python WSGI (Python/Python 3),
Rack (Ruby 1.8/Ruby 1.9.1)
Package: uwsgi-plugin-admin
@@ -378,18 +376,6 @@ Description: Lua WSAPI plugin for uWSGI (Lua 5.1)
This package provides Lua WSAPI plugin for uWSGI (linked with Lua 5.1
runtime).
-Package: uwsgi-plugin-luajit
-Architecture: i386 amd64 kfreebsd-i386 armel
-Depends: ${shlibs:Depends}, ${misc:Depends}, uwsgi-core (= ${binary:Version})
-Description: Lua WSAPI plugin for uWSGI (LuaJIT)
- uWSGI presents a complete stack for networked/clustered web applications,
- implementing message/object passing, caching, RPC and process management.
- It is designed to be fully modular. This means that different plugins can be
- used in order to add compatibility with tons of different technology on top of
- the same core.
- .
- This package provides Lua WSAPI plugin for uWSGI (linked with LuaJIT runtime).
-
Package: uwsgi-plugin-nagios
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, uwsgi-core (= ${binary:Version})
diff --git a/debian/patches/fixed-a-leak-in-uwsgi.workers.patch b/debian/patches/fixed-a-leak-in-uwsgi.workers.patch
new file mode 100644
index 000..a6d2d2d
--- /dev/null
+++ b/debian/patches/fixed-a-leak-in-uwsgi.workers.patch
@@ -0,0 +1,72 @@
+From: roberto@quantal64 roberto@quantal64
+Date: Sat, 2 Jun 2012 09:59:21 +0200
+Subject: fixed a leak in uwsgi.workers()
+
+---
+ plugins/python/uwsgi_pymodule.c | 35 ---
+ 1 file changed, 28 insertions(+), 7 deletions(-)
+
+diff --git a/plugins/python/uwsgi_pymodule.c b/plugins/python/uwsgi_pymodule.c
+index 0fe1ce3..2a72aec 100644
+--- a/plugins/python/uwsgi_pymodule.c
b/plugins/python/uwsgi_pymodule.c
+@@ -2492,6 +2492,11 @@ PyObject *py_uwsgi_workers(PyObject * self, PyObject * args) {
+ goto clear;
+ }
+
++ apps_tuple = PyDict_GetItemString(worker_dict, apps);
++ if (apps_tuple) {
++ Py_DECREF(apps_tuple);
++ }
++
+ PyDict_Clear(worker_dict);
+
+ zero = PyInt_FromLong(uwsgi.workers[i + 1].id);
+@@ -2601,21 +2606,37 @@ PyObject *py_uwsgi_workers(PyObject * self, PyObject * args) {
+ apps_dict = PyDict_New();
+ ua = uwsgi.workers[i+1].apps[j];
+
+- PyDict_SetItemString(apps_dict, id, PyInt_FromLong(j));
++ zero =
Bug#681822: marked as done (unblock: alembic/0.3.4+ds-3)
Your message dated Mon, 16 Jul 2012 21:56:05 +0100
with message-id 1342472165.3728.39.ca...@jacala.jungle.funky-badger.org
and subject line Re: Bug#681822: unblock: alembic/0.3.4+ds-3
has caused the Debian Bug report #681822,
regarding unblock: alembic/0.3.4+ds-3
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.)
--
681822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package alembic
Fixes RC bug #680854. Apologies for two unblock requests on the same
package so close together. I didn't get far enough down on my list before
uploading the last one. Attached debdiff is Wheezy - Sid.
unblock alembic/0.3.4+ds-3
diff -Nru alembic-0.3.4+ds/debian/changelog alembic-0.3.4+ds/debian/changelog
--- alembic-0.3.4+ds/debian/changelog 2012-06-06 17:15:25.0 -0400
+++ alembic-0.3.4+ds/debian/changelog 2012-07-16 16:20:40.0 -0400
@@ -1,3 +1,26 @@
+alembic (0.3.4+ds-3) unstable; urgency=low
+
+ * Team upload
+ * Build-depend on python2.6-argparse to support python2.6 tests
+ (Closes: #680854)
+ * Suggest python2.6-argparse as it is needed to run with python2.6, but
+multiple depends require python2.7 to be installed - running with
+python2.6 should be very unusual and pulling in the non-standard argparse
+on all installations for this is not a good thing
+ * Fix copy/paste error in debian/changelog from previous upload
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 15:42:34 -0400
+
+alembic (0.3.4+ds-2) unstable; urgency=low
+
+ * Team upload
+ * Drop python3-sphinx as an alternate build-depend to python-sphinx to fix
+FTBFS (Closes: #680855
+- The package only has a python version anyway, so python3-sphinx as a
+ build-dep is clearly wrong
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 14:51:28 -0400
+
alembic (0.3.4+ds-1) unstable; urgency=low
* Initial release. (Closes: #669404)
diff -Nru alembic-0.3.4+ds/debian/control alembic-0.3.4+ds/debian/control
--- alembic-0.3.4+ds/debian/control 2012-05-24 16:50:52.0 -0400
+++ alembic-0.3.4+ds/debian/control 2012-07-16 16:19:22.0 -0400
@@ -9,13 +9,14 @@
Homepage: http://www.bitbucket.org/zzzeek/alembic
Build-Depends: debhelper (= 8), python-all, python-setuptools,
python-nose, python-sqlalchemy, python-mako,
- python-sphinx (= 1.0.7+dfsg) | python3-sphinx
+ python2.6-argparse, python-sphinx (= 1.0.7+dfsg)
Package: alembic
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, ${sphinxdoc:Depends},
python-sqlalchemy, python-mako
Recommends: python-pkg-resources
+Suggests: python2.6-argparse
Description: lightweight database migration tool for SQLAlchemy
Alembic is a new database migration tool, written by the author
of SQLAlchemy. A migration tool offers the following functionality:
---End Message---
---BeginMessage---
On Mon, 2012-07-16 at 16:34 -0400, Scott Kitterman wrote:
Please unblock package alembic
Fixes RC bug #680854. Apologies for two unblock requests on the same
package so close together. I didn't get far enough down on my list before
uploading the last one. Attached debdiff is Wheezy - Sid.
Hint updated.
Regards,
Adam---End Message---
Re: Requesting freeze exception for uwsgi
Hi Cyril, On Sun, Jul 15, 2012 at 10:35 PM, Cyril Brulebois k...@debian.org wrote: Hello, Janoš Guljaš ja...@resenje.org (09/07/2012): I've prepared a release 1.2.3+dfsg-2 (-1 in testing) but did not upload to unstable as I want to consult about the changes. and thanks for checking with us. To resolve the issue #680132 a binary package uwsgi-plugin-luajit (built from src:uwsgi) must be removed from the archive, as luajit will be removed from the Wheeze. There are no reverse dependencies for wheezy ;) Ups. :) uwsgi-plugin-luajit (except for the meta package uwsgi-app-integration-plugins which will be fixed in the same release). I would like to ask is the procedure of removing a binary package the same during the freeze? Yes, you just need to get the package removed from unstable, following: http://wiki.debian.org/ftpmaster_Removals Thanks. The second change is applying an upstream patch regarding memory leak, which is an important fix. ACK. I am sending the diff for the 1.2.3+dfsg-2. Should I proceed with the upload to unstable and ask for removal from ftpmaster? Looks good to me, even if the changelog could be a bit more descriptive WRT the changes for the removal; I'd suggest mentioning the package removed from build-deps, the package dropped from depends, and that all luajit occurrences were removed from debian/rules. That would make the reviewer more confident about the diff. ;) [ I am currently, but if somebody else ends up reviewing it, that means a bit of time figuring out all changes were intended. ] Thanks for suggestions and help. I uploaded 1.2.3+dfsg-2, requested a RM #681826 and a freeze exception #681827. Mraw, KiBi. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlADKZYACgkQeGfVPHR5Nd2QxACeKWlBYXXItRkuCYLLTZZ6adjz 2jQAn1sthbM2G0zu+RwzyjhFG6eJgYKC =Y/vR -END PGP SIGNATURE- Best regards, Janos -- 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/CAGp=0ymzc8u8bq-oa_tncwbnuz0przvikokqjlpp_aewgti...@mail.gmail.com
Re: Using FreeDesktop MIME entries directly in mime-support (Re: Fixing the mime horror ini Debian).
Laszlo Boszormenyi (GCS) g...@debian.org (16/07/2012): I think that's a perfect use case for collab-maint. László, do you really need a dedicated group for that? My intention was to limit people who can commit to mime-support. It seems there are multiple viewpoints for example about application/x-httpd-* types. One may do more harm with a commit if not consulted by a group of more advanced people. But I'm fine with normal collab-maint as well if you and Charles would like that. As someone processing alioth-related requests, I would find it nice to use collab-maint for such projects; but I'm willing to hear about arguments against that. As a random developer, I would really hate to see people fight through commits. In case that would happen, I think that can be fixed, IIRC collab-maint has some abuse clauses or something similar. (IOW: I'm not convinced you need a dedicated group; quite the contrary.) Mraw, KiBi. signature.asc Description: Digital signature
Re: Using FreeDesktop MIME entries directly in mime-support (Re: Fixing the mime horror ini Debian).
Hi Cyril, On Mon, 2012-07-16 at 22:49 +0200, Cyril Brulebois wrote: Charles Plessy ple...@debian.org (16/07/2012): If nobody else volunteers, I propose to start a maintenance group for the mime-support package, that I would store in a Git repository on Alioth's collab-maint group. Just for the record, Charles has an advanced knowledge regarding MIME in general. Hope we can work together. I think that's a perfect use case for collab-maint. László, do you really need a dedicated group for that? My intention was to limit people who can commit to mime-support. It seems there are multiple viewpoints for example about application/x-httpd-* types. One may do more harm with a commit if not consulted by a group of more advanced people. But I'm fine with normal collab-maint as well if you and Charles would like that. Cheers, Laszlo/GCS signature.asc Description: This is a digitally signed message part
Bug#681831: unblock: xserver-xorg-video-mga/1:1.5.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package xserver-xorg-video-mga Simple patch to avoid conflicting with a KMS driver (one was added for g200se chips in linux 3.5). unblock xserver-xorg-video-mga/1:1.5.0-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#681832: unblock: xserver-xorg-video-cirrus/1:1.4.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package xserver-xorg-video-cirrus Avoids conflicting with the KMS driver added for the qemu-emulated chip in Linux 3.5. Well, explicitly conflict by bailing out instead of having two drivers fighting over the hw. unblock xserver-xorg-video-cirrus/1:1.4.0-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Re: Using FreeDesktop MIME entries directly in mime-support (Re: Fixing the mime horror ini Debian).
On Mon, 2012-07-16 at 23:35 +0200, Cyril Brulebois wrote: Laszlo Boszormenyi (GCS) g...@debian.org (16/07/2012): My intention was to limit people who can commit to mime-support. It seems there are multiple viewpoints for example about application/x-httpd-* types. One may do more harm with a commit if not consulted by a group of more advanced people. But I'm fine with normal collab-maint as well if you and Charles would like that. As someone processing alioth-related requests, I would find it nice to use collab-maint for such projects; but I'm willing to hear about arguments against that. As a random developer, I would really hate to see people fight through commits. In case that would happen, I think that can be fixed, IIRC collab-maint has some abuse clauses or something similar. (IOW: I'm not convinced you need a dedicated group; quite the contrary.) I already wrote my reason and that a normal collab-maint place is fine with me. So I just need to login to git.debian.org and create a repository under /git/collab-maint/ right? Charles, I would add myself as Maintainer and you as an uploader or the vica-versa whichever suits you better. Is this OK with you? Regards, Laszlo/GCS signature.asc Description: This is a digitally signed message part
Bug#681387: unblock: resiprocate
Thanks. Would it be possible to indicate which of the changes listed are included in 1.8.3 / 1.8.4? Both the changelog and the upstream website only appear to refer to 1.8 in general, with no further division. Upstream ChangeLog file summarises all cumulative changes since 1.7, so most of that is not relevant to this unblock request I attach the following: Log of all changes from 1.8.2 up to 1.8.5 svn log -r9715:HEAD https://svn.resiprocate.org/rep/resiprocate/branches/resiprocate-1.8 The changes for 1.8.5 can be ignored, they only impact Windows users You can access coloured diffs using the commit list (everything appears twice because each change is committed on trunk and then backported to the release branch if necessary): http://list.resiprocate.org/archive/resiprocate-commit/ (FWIW, the upstream site also has 1.8 release now available as a news item from about six weeks /after/ 1.8.2 hit Debian.) This was the first release built with autotools and libtool, with SONAME and ABI version data set properly for packaging. Therefore, it wasn't widely promoted for a few weeks while the team upstream verified that everything was OK, and also for users of unstable to verify that upstream has released something that fits within the expectations of the Debian community. You can verify that each release tarball 1.8.* has been announced on the developer list, with a checksum signed by my own key, so we know what has gone into Debian is built from the official upstream tarballs. http://list.resiprocate.org/archive/resiprocate-devel/ r9797 | sgodin | 2012-07-05 17:04:22 +0200 (Thu, 05 Jul 2012) | 1 line -fixed compilation issue in ContactInstanceRecord for some compilers r9795 | dpocock | 2012-06-22 19:00:06 +0200 (Fri, 22 Jun 2012) | 1 line release: update release branch for next in series, 1.8.3 typo 1.8.4!!! r9793 | sgodin | 2012-06-21 17:26:57 +0200 (Thu, 21 Jun 2012) | 5 lines -fixed a bug when using the registration sync mechanism - the ServerRegistration onRefresh callback could be incorrectly generated instead of the onAdd callback when a registration is added, due to the record lingering in memory -updated ChangeLog r9778 | sgodin | 2012-06-14 15:54:55 +0200 (Thu, 14 Jun 2012) | 1 line -fixed bug with message silo, where it would fail to work at all using MySQL as backing store r9763 | dpocock | 2012-06-09 23:33:16 +0200 (Sat, 09 Jun 2012) | 1 line release: backport various fixes relating to the new CADirectory support and apps/sipdial (merge r9748:9762) r9762 | dpocock | 2012-06-09 23:31:04 +0200 (Sat, 09 Jun 2012) | 1 line A bad value was passed to the macro RESIP_HeapCount (merge r9745 onto 1.8) r9761 | dpocock | 2012-06-09 23:25:50 +0200 (Sat, 09 Jun 2012) | 1 line release: Rename ReleaseNotes.txt to ChangeLog so tools will recognise it r9747 | dpocock | 2012-06-07 23:28:05 +0200 (Thu, 07 Jun 2012) | 1 line release: update ReleaseNotes.txt for 1.8 series r9746 | dpocock | 2012-06-07 23:15:49 +0200 (Thu, 07 Jun 2012) | 1 line release: update release branch for next in series, 1.8.3 r9744 | sgodin | 2012-06-01 17:18:58 +0200 (Fri, 01 Jun 2012) | 2 lines -completed ReleaseNotes.txt -added ReleaseNotes.txt to EXTRA_DIST so it's gets included in package r9743 | sgodin | 2012-05-31 23:36:12 +0200 (Thu, 31 May 2012) | 1 line -started release notes - so far done up to (not-including) REVISION 9367 r9742 | sgodin | 2012-05-31 22:20:46 +0200 (Thu, 31 May 2012) | 25 lines Merged changes from main r9741 -repro web interface improvements - display settings in alphabetic order - added display of DNS Cache to settings page - added Clear DNS Cache button to settings page - added Restart Proxy button to settings page (reloads everyt... - r9740 -added an ability to configure a different database instance for some of the repro database tables New configuration file settings, RuntimeMySQLServer and subsetting, were added to facilitate this. - r9739 -fixed a trap during shutdown, due to order of destructed objects - r9738 -fixed a bug where the CSeq
Collaborative maintenance of mime-support (was Re: Using FreeDesktop MIME entries directly in mime-support).
Le Mon, Jul 16, 2012 at 09:48:47PM +, Laszlo Boszormenyi (GCS) a écrit : On Mon, 2012-07-16 at 23:35 +0200, Cyril Brulebois wrote: Laszlo Boszormenyi (GCS) g...@debian.org (16/07/2012): My intention was to limit people who can commit to mime-support. It seems there are multiple viewpoints for example about application/x-httpd-* types. One may do more harm with a commit if not consulted by a group of more advanced people. But I'm fine with normal collab-maint as well if you and Charles would like that. As someone processing alioth-related requests, I would find it nice to use collab-maint for such projects; but I'm willing to hear about arguments against that. As a random developer, I would really hate to see people fight through commits. In case that would happen, I think that can be fixed, IIRC collab-maint has some abuse clauses or something similar. (IOW: I'm not convinced you need a dedicated group; quite the contrary.) I already wrote my reason and that a normal collab-maint place is fine with me. So I just need to login to git.debian.org and create a repository under /git/collab-maint/ right? Charles, I would add myself as Maintainer and you as an uploader or the vica-versa whichever suits you better. Is this OK with you? Hi Laszlo and Brian, how about the following (inspired by http://dep.debian.net/deps/dep2/) Maintainer: mime-supp...@packages.debian.org Uploaders: Laszlo Boszormenyi (GCS) g...@debian.org, Charles Plessy ple...@debian.org, I propose the following action plan. 0) We subscribe to the PTS (done for me). 1) Upload to experimental an adopted package with the updated maintainer and uploaders list, the VCS fields updated, and the patch for #497779 applied. 2) Install in Alioth's collab-maint a git repository made with the --debsnap option of git-import-dscs, unless we try to go deeper in time ? Set up commits emails to go to the PTS. 3) Make crystal clear in the source package's READMEs that uncoordinated commits are an abuse of the collab-maint Alioth group. But perhaps we can allow developers to create topic branches related to bugs in the BTS if they like ? 4) Postpone any other change on the main branch until either #681687 (tech. comittee) is solved or Wheezy released. Lastly, I would like to thank Brian for his impressively 16-years long work on mime-support. Brian, feel free to stay among the uploaders ! 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/20120717002659.ga2...@falafel.plessy.net
Bug#681842: unblock: libaugeas-ruby/0.4.1-1.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libaugeas-ruby
Fixes RC bug #680684.
unblock libaugeas-ruby/0.4.1-1.1
diff -Nru libaugeas-ruby-0.4.1/debian/changelog libaugeas-ruby-0.4.1/debian/changelog
--- libaugeas-ruby-0.4.1/debian/changelog 2012-04-21 08:41:30.0 -0400
+++ libaugeas-ruby-0.4.1/debian/changelog 2012-07-16 22:23:28.0 -0400
@@ -1,3 +1,12 @@
+libaugeas-ruby (0.4.1-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Change libaugeas-ruby depends from ruby1.8 to ruby1.9.1 to match the
+current default ruby and update package description to match
+(Closes: #680684)
+
+ -- Scott Kitterman sc...@kitterman.com Mon, 16 Jul 2012 20:59:26 -0400
+
libaugeas-ruby (0.4.1-1) unstable; urgency=low
* New upstream release. Closes: #665927.
diff -Nru libaugeas-ruby-0.4.1/debian/control libaugeas-ruby-0.4.1/debian/control
--- libaugeas-ruby-0.4.1/debian/control 2012-04-21 08:34:10.0 -0400
+++ libaugeas-ruby-0.4.1/debian/control 2012-07-16 20:24:26.0 -0400
@@ -8,14 +8,14 @@
Package: libaugeas-ruby
Architecture: all
-Depends: libaugeas-ruby1.8, ${misc:Depends}
+Depends: libaugeas-ruby1.9.1, ${misc:Depends}
Description: Augeas bindings for the Ruby language
Augeas is a configuration editing tool. It parses configuration files in their
native formats and transforms them into a tree. Configuration changes are made
by populating this tree and saving it back into native config files.
.
This is a dependency package which depends on Debian's default Ruby version
- (currently 1.8.x).
+ (currently 1.9.1).
Package: libaugeas-ruby1.8
Architecture: any
Re: unblock request: upgrade-system
Hello again, 2012/7/16 Cyril Brulebois k...@debian.org: Martin-Éric Racine martin-eric.rac...@iki.fi (16/07/2012): Most changes are mere polishing of what was already started in 1.6.2.0 (cleaning up debian/copyright and using --long-options for everything). There is exactly one new feature in the cron job and even then it's a minor one. even if the diff is indeed tiny, I don't think it matches the rules described at: http://release.debian.org/wheezy/freeze_policy.html (linked from the freeze announcement). 6. as above, important changes that the maintainer feels are needed before release. Those changes were done with the specific goal of covering oversights from 1.6.2.0 on time for the release, thus why I feel they are needed for Wheezy. Martin-Éric -- 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/capzxpqeajjmbikbo1xcyt0qp1hl5g6zxzttw3vevmptenrr...@mail.gmail.com
Re: Collaborative maintenance of mime-support (was Re: Using FreeDesktop MIME entries directly in mime-support).
On Tue, 2012-07-17 at 09:27 +0900, Charles Plessy wrote: how about the following (inspired by http://dep.debian.net/deps/dep2/) Maintainer: mime-supp...@packages.debian.org Uploaders: Laszlo Boszormenyi (GCS) g...@debian.org, Charles Plessy ple...@debian.org, Hope Brian will also join. May we add you? I propose the following action plan. 0) We subscribe to the PTS (done for me). For me as well, I assume Brian is also subscribed. 1) Upload to experimental an adopted package with the updated maintainer and uploaders list, the VCS fields updated, and the patch for #497779 applied. +1 2) Install in Alioth's collab-maint a git repository made with the --debsnap option of git-import-dscs, unless we try to go deeper in time ? Set up commits emails to go to the PTS. I've created an empty git collab-maint repository on Alioth, still not visible over the web interface. As I know, it just need some time. Made the config to send commits to the PTS. So, how deep should be the package import? The full history from snapshot.debian.org or just the last upload is enough? We will have the file history, but not the comment why happened and what. 3) Make crystal clear in the source package's READMEs that uncoordinated commits are an abuse of the collab-maint Alioth group. But perhaps we can allow developers to create topic branches related to bugs in the BTS if they like ? +1 , but I assume you know that others may create free and public git trees elsewhere, for example on GitHub. They may send a merge request when their work is done. The tree is still visible, separated and can be merged if needed. 4) Postpone any other change on the main branch until either #681687 (tech. comittee) is solved or Wheezy released. +1 Lastly, I would like to thank Brian for his impressively 16-years long work on mime-support. Brian, feel free to stay among the uploaders ! I join as well. Thanks Brian for your previous work! Hope you will be still close to the package and the recent events don't turn you down. Regards, Laszlo/GCS -- 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/1342503504.8460.88.camel@julia
