Bug#689825: unblock: pymongo/2.2-2
Hi Federico, On Sat, Oct 06, 2012 at 07:48:17PM +0100, Federico Ceratto wrote: Please unblock package pymongo Version 2.2-2 is affected by bug #689283 and #688040 Version 2.2-3, currently in Unstable, fixes those two bugs (and has no other changes) Thanks! You probably meant to ask an unblock for 2.2-3, not 2.2-2. I have reopened bug 689283, because the bug is not fully solved in 2.2-3. So I suggest debian-release to wait with the unblock for now. Regards, Bart Martens -- 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/20121007083852.gb21...@master.debian.org
Bug#689853: nmu: libfiu_0.91-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu libfiu wasn't built in an up-to-date sid environment: python-fiu on i386 has unsatisfiable dependency on python ( 2.7). nmu libfiu_0.91-1 . i386 . -m Rebuild in an up-to-date sid environment. -- Jakub Wilk -- 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/20121007084035.ga7...@jwilk.net
Bug#689814: unblock: gnuradio/3.6.1-1
On 06/10/2012 17:54, A. Maitland Bottoms wrote: The gnuradio 3.6.1-1 source was accepted into unstable on 12 June 2012: http://packages.qa.debian.org/g/gnuradio/news/20120612T181727Z.html Since that was before the Wheezy freeze, this should apply: Any packages in unstable before the 19:52 dinstall begins on that day will be given automatic freeze exceptions (for the specific version in unstable). Automatic freeze exceptions are granted for one month. If the package didn't migrate within that duration, the freeze exception is dropped. All other architectures built before the freeze, the ia64 binaries only recently have been uploaded. (Subject: gnuradio_3.6.1-1_ia64.changes ACCEPTED into unstable Date: Sat, 06 Oct 2012 04:17:55 +) It would be good to release Wheezy with gnuradio 3.6.1 It is a pity that the package didn't migrate due to a transient build failure, but it is not an argument to unblock it. Besides, the diff between testing's and sid's gnuradio looks rather large… and sid's version doesn't (according to the BTS) fix any serious issues. Do you have in mind some very important fixes that you'd like to see in Wheezy? If not, we'd prefer to keep 3.6.1-1 out of Wheezy. Regards, -- Mehdi Dogguy مهدي الدڤي -- 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/50715857.5080...@dogguy.org
Bug#689839: marked as done (unblock: ruby1.9.1/1.9.3.194-2)
Your message dated Sun, 07 Oct 2012 12:29:44 +0200
with message-id 50715998.9050...@dogguy.org
and subject line Re: Bug#689839: unblock: ruby1.9.1/1.9.3.194-2
has caused the Debian Bug report #689839,
regarding unblock: ruby1.9.1/1.9.3.194-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.)
--
689839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689839
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 ruby1.9.1
I've just uploaded ruby1.9.1/1.9.3.194-2 to unstable. It contains a
security fix for CVE-2011-1005, which closes Debian bug #689075.
Attached you will find a debdiff against the version currently in
wheezy.
unblock ruby1.9.1/1.9.3.194-2
-- 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=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Antonio Terceiro terce...@debian.org
diff -Nru ruby1.9.1-1.9.3.194/debian/changelog ruby1.9.1-1.9.3.194/debian/changelog
--- ruby1.9.1-1.9.3.194/debian/changelog 2012-06-02 08:10:26.0 -0300
+++ ruby1.9.1-1.9.3.194/debian/changelog 2012-10-06 16:29:43.0 -0300
@@ -1,3 +1,12 @@
+ruby1.9.1 (1.9.3.194-2) unstable; urgency=low
+
+ * debian/patches/20120927-cve_2011_1005.patch: patch sent by upstream;
+fixes CVE-2011-1005 which was thought of as not affecting the Ruby 1.9.x
+series (Closes: #689075). Thanks to Tyler Hicks tyhi...@canonical.com
+for reporting the issue.
+
+ -- Antonio Terceiro terce...@debian.org Sat, 06 Oct 2012 16:29:42 -0300
+
ruby1.9.1 (1.9.3.194-1) unstable; urgency=low
[ Lucas Nussbaum ]
diff -Nru ruby1.9.1-1.9.3.194/debian/patches/20120927-cve_2011_1005.patch ruby1.9.1-1.9.3.194/debian/patches/20120927-cve_2011_1005.patch
--- ruby1.9.1-1.9.3.194/debian/patches/20120927-cve_2011_1005.patch 1969-12-31 21:00:00.0 -0300
+++ ruby1.9.1-1.9.3.194/debian/patches/20120927-cve_2011_1005.patch 2012-10-02 10:06:08.0 -0300
@@ -0,0 +1,93 @@
+Description: Prevent untainted strings from being incorrectly tainted
+ This flaw allowed untainted strings to be tainted and modified, even in
+ safe level 4.
+Origin: upstream
+--- a/error.c
b/error.c
+@@ -569,7 +569,6 @@ exc_to_s(VALUE exc)
+
+ if (NIL_P(mesg)) return rb_class_name(CLASS_OF(exc));
+ r = rb_String(mesg);
+-OBJ_INFECT(r, exc);
+ return r;
+ }
+
+@@ -853,11 +852,7 @@ name_err_to_s(VALUE exc)
+
+ if (NIL_P(mesg)) return rb_class_name(CLASS_OF(exc));
+ StringValue(str);
+-if (str != mesg) {
+- rb_iv_set(exc, mesg, mesg = str);
+-}
+-OBJ_INFECT(mesg, exc);
+-return mesg;
++return str;
+ }
+
+ /*
+@@ -988,7 +983,6 @@ name_err_mesg_to_str(VALUE obj)
+ args[2] = d;
+ mesg = rb_f_sprintf(NAME_ERR_MESG_COUNT, args);
+ }
+-OBJ_INFECT(mesg, obj);
+ return mesg;
+ }
+
+--- a/test/ruby/test_exception.rb
b/test/ruby/test_exception.rb
+@@ -333,4 +333,55 @@ end.join
+ load(t.path)
+ end
+ end
++
++ def test_to_s_taintness_propagation
++for exc in [Exception, NameError]
++ m = abcdefg
++ e = exc.new(m)
++ e.taint
++ s = e.to_s
++ assert_equal(false, m.tainted?,
++ #{exc}#to_s should not propagate taintness)
++ assert_equal(false, s.tainted?,
++ #{exc}#to_s should not propagate taintness)
++end
++
++o = Object.new
++def o.to_str
++ foo
++end
++o.taint
++e = NameError.new(o)
++s = e.to_s
++assert_equal(false, s.tainted?)
++ end
++
++ # CVE-2011-1005
++ def test_exception_to_s_should_not_propagate_untrustedness
++favorite_lang = Ruby
++
++for exc in [Exception, NameError]
++ assert_raise(SecurityError) do
++lambda {
++ $SAFE = 4
++ exc.new(favorite_lang).to_s
++ favorite_lang.replace(Python)
++}.call
++ end
++end
++
++assert_raise(SecurityError) do
++ lambda {
++$SAFE = 4
++o = Object.new
++o.singleton_class.send(:define_method, :to_str) {
++ favorite_lang
++}
++NameError.new(o).to_s
++favorite_lang.replace(Python)
++ }.call
++end
++
++assert_equal(Ruby, favorite_lang)
++ end
+ end
diff -Nru ruby1.9.1-1.9.3.194/debian/patches/series ruby1.9.1-1.9.3.194/debian/patches/series
---
Bug#689853: marked as done (nmu: libfiu_0.91-1)
Your message dated Sun, 07 Oct 2012 12:30:42 +0200 with message-id 507159d2.9020...@dogguy.org and subject line Re: Bug#689853: nmu: libfiu_0.91-1 has caused the Debian Bug report #689853, regarding nmu: libfiu_0.91-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.) -- 689853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689853 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: binnmu libfiu wasn't built in an up-to-date sid environment: python-fiu on i386 has unsatisfiable dependency on python ( 2.7). nmu libfiu_0.91-1 . i386 . -m Rebuild in an up-to-date sid environment. -- Jakub Wilk ---End Message--- ---BeginMessage--- On 07/10/2012 10:40, Jakub Wilk wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu libfiu wasn't built in an up-to-date sid environment: python-fiu on i386 has unsatisfiable dependency on python ( 2.7). nmu libfiu_0.91-1 . i386 . -m Rebuild in an up-to-date sid environment. Scheduled. Cheers. -- Mehdi Dogguy مهدي الدڤي---End Message---
Bug#689800: marked as done (nmu: olsrd_0.6.3-5)
Your message dated Sun, 07 Oct 2012 12:32:42 +0200 with message-id 50715a4a.80...@dogguy.org and subject line Re: Bug#689800: nmu: olsrd_0.6.3-5 has caused the Debian Bug report #689800, regarding nmu: olsrd_0.6.3-5 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.) -- 689800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689800 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: binnmu nmu olsrd_0.6.3-5 . amd64 . -m Rebuild in a clean sid environment. olsrd/amd64 was not built in a Debian sid environment and has a unsatisfiable Depends: libc6 (= 2.15) that can be solved by rebuilding in sid. Andreas ---End Message--- ---BeginMessage--- On 06/10/2012 14:21, Andreas Beckmann wrote: nmu olsrd_0.6.3-5 . amd64 . -m Rebuild in a clean sid environment. Scheduled. Cheers. -- Mehdi Dogguy مهدي الدڤي---End Message---
Bug#686702: unblock: gcc-4.6/4.6.3-9
On 05.10.2012 09:59, Julien Cristau wrote: On Tue, Sep 4, 2012 at 23:10:16 +0200, Matthias Klose wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock this should go to wheezy, because - wrong code gen fixes - the ARM vector alignment fix - some fixes for cross builds please ignore the Linaro changes, these are not used for the Debian ARM builds. Unfortunately, 4.6.3-10 failed to build on kfreebsd-amd64 and mipsen, so this can't go to wheezy yet. Any idea what's going on there? disabled in -11 the libstdc++ testsuite for mips*, as already done in 4.7. the kfreebsd build failure is not reproducible on the porter box asdfasdf.debian.net, this pops up in various builds, same for the current gnat-4.6 upload. now building again manually, as already done with -9. -- 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/50715ce7.9000...@debian.org
Re: Getting Trac 0.12.4 into wheezy?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2012 23:19, Arthur de Jong wrote: What is the release team's opinion on this? First, we will need a debdiff between testing's version and the one you want to upload, please. Kind Regards, - -- Mehdi Dogguy مهدي الدڤي -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQcWSTAAoJEDe1GR0FRlJo77QH/RXmF6wnmBpd1XeYqzNpkeL1 GvxvQspip/XaYMymYOkLohqm6s0VzAy3VIdfjqkndEDFQ0FEwDJKfsd20N3nmH/u SAVfm9coMPSgyWWUXkqnmHVPOpbnCPLDo4q0ziyZAoBRv7lNYwJKE61ht8O73NLT hA35zSQYwvTK6jJY4rqfBLaEn9E5KvM35t13MtAUS3mGEoA1cOU+CRpA3pI5/kg8 ePIpuurdDH08c7Pywx3FJ5ecpxYPq/GmRZAPwMs+NbKGEdk9NkQlpxd6bFFXbPw7 Xmgr8KiMldhHHAJgl5LEcWA3yYKTvjYnMVOfQBvtLHlJZ9L+lxUt9UpRX/bzNzc= =XmbY -END PGP SIGNATURE- -- 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/50716498.6020...@dogguy.org
Re: Bug#629125: New version 0.29-1 of ensymble (fixes: #616799, #629125)
Hi Debian Release, A small summary of current situation: - ensymble is in RFA since Jan 2011 (#611552) - ensymble upstream released 0.29 in May 2010 (http://code.google.com/p/ensymble/downloads/list) - new upstream 0.29 also fixes #629125 - debian currently has 0.28-2 in sid and wheezy - 0.28-2 uses the deprecated py_central (#616799) - Dominic has made most of the work for the preparation of 0.29-1 and published it in a git repo - I cloned his repo and provided a fix for #616799 targeting for 0.29-1 - I am not a DD or DM, nor do I have the time to adopt ensymble (but I would like to see 0.29 in wheezy) Please also see comments below and advice on the preferred course of action. 2012/10/7 Dominic Hargreaves d...@earth.li: On Sat, Oct 06, 2012 at 08:25:43PM +0300, Eddy Petrișor wrote: Attached there is a complete 0.29-1 package version based on Dominic's master version from his git repo, with the necessary changes made to fix bug #616799 (python-central is deprecated) and the bug #629125 (sha module is deprecated). Thanks! The 0.28 branch in git should probably be merged (at least the changelog) before upload. I merged it. There were no changes in the packaging except: - merged the 0.28-2 changelog entry - the X-Python-Version changed from 2.6 (as on master) to all (as on 0.28-2 - the version from sid) - The debian/ensymble.links file in 0.28-2 was removed since there is no /usr/share/ensymble/cmdmain.py anymore These changes can be pulled from my git repo of ensymble (based on Dominic's repo): http://anonscm.debian.org/gitweb/?p=users/eddyp-guest/ensymble.git The package ensymbe is alreaby in RFA state for some time (#611552), he already pre-approved a NMU for this version, as seen from his personal repo in the master branch: http://anonscm.debian.org/gitweb/?p=users/dom/ensymble.git;a=blob;f=debian/changelog;h=bffeebf79a250b500fc1b319d2267db78e5d17b8;hb=master For the avoidance of doubt, the file you've pointed to does not pre-approve any NMU; Acknowledge NMU means that the maintainer has noticed a *previous* NMU. However I do not object to another NMU if someone feels that's appropriate. Oh, my bad. It's been so much time since I've worked in Debian that I forgot these things. I am sorry if I seemed pushy or rude with my misunderstanding. I cannot promise any timescale for reviewing/applying these changes, so an NMU is absolutely fine, but please let me if you (generic) plan on doing so. I will keep this on my radar in the meantime. I am not a DD nor a DM, so I don't have any upload rights. I was hoping somebody with such rights would sponsor the upload. Not sure if debian-release has an attachment size-based filter, so I'll send the updated package to the BRs in a separate mail to make sure the message arrives in debian-release. So, in my opinion, this new version can be uploaded to the archive to ease up the deprecation of python-central. If release managers think a new upstream version is too much, maybe it can be blocked from transitioning, until the new version gets enough testing in sid. If you think a 0.28 version should be provided, please tell me, so I can provide a version based on 0.28. If you would like to see these changes in wheezy I recommend that you talk directly to the release team (please CC these bugs). Added debian-release in CC. Release team, is a new upstream version appropriate, taking into account the following? - the upstream version was released in 2010 (no other releases since then), - and the new version also fixes #629125 If not, do you advice for a 0.28-3 version with only the fix for the py_central deprecation (and maybe a patch for 629125)? You can pull my changes if you add my repo as a remote then pull and merge. git remote add -f eddy git://anonscm.debian.org/users/eddyp-guest/ensymble.git git co upstream git merge eddy/upstream git co pristine-tar git merge eddy/pristine-tar git checkout master git merge eddy/master I also fixed the layout of the files in the upstream branch which should contain what was in 'upsteam/current'. (it seems in the SVN to git transition the different upstream branches were not treated as such, but the entire upstream directory was considered a single branch). Thanks :) NP. The new changes are published in my repo. P.S.: I added myself to Uploaders, but I am not sure if this is necessary since I don't intend to take over the package myself (and I forgot some of the packaging stuff I once knew). If this is wrong, please remove the line. It sounds like it shouldn't be there then. Removed. -- Regards, EddyP = The universe is not required to be in perfect harmony with human ambition. - Carl Sagan -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:
Bug#689262: marked as done (unblock: xchat/2.8.8-7)
Your message dated Sun, 07 Oct 2012 13:45:24 +0200
with message-id 50716b54.1040...@dogguy.org
and subject line Re: Bug#689262: unblock: xchat/2.8.8-7
has caused the Debian Bug report #689262,
regarding unblock: xchat/2.8.8-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
689262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
Hello,
Please unblock xchat 2.8.8-7. It fixes grave bug 147832 about loss of data
when the disk is full. Debdiff attached. It's basically ten times the same
approach like I did for bug 463072.
Regards,
Bart Martens
diff -Nru xchat-2.8.8/debian/changelog xchat-2.8.8/debian/changelog
--- xchat-2.8.8/debian/changelog 2012-06-13 18:07:56.0 +
+++ xchat-2.8.8/debian/changelog 2012-09-30 15:19:00.0 +
@@ -1,3 +1,20 @@
+xchat (2.8.8-7) unstable; urgency=low
+
+ * The Just Married release.
+ * debian/patches/56_save_servlist.patch: Added. Closes: #147832.
+Added more similar patches :
+debian/patches/57_save_url.patch
+debian/patches/58_save_notify.patch
+debian/patches/59_save_colors.patch
+debian/patches/60_save_chanlist.patch
+debian/patches/61_save_editlist.patch
+debian/patches/62_save_chanopt.patch
+debian/patches/63_save_keybindings.patch
+debian/patches/64_save_pevents.patch
+debian/patches/65_save_sound.patch
+
+ -- Bart Martens ba...@debian.org Sun, 30 Sep 2012 08:57:19 +
+
xchat (2.8.8-6) unstable; urgency=high
* The Euro 2012 release.
diff -Nru xchat-2.8.8/debian/patches/56_save_servlist.patch xchat-2.8.8/debian/patches/56_save_servlist.patch
--- xchat-2.8.8/debian/patches/56_save_servlist.patch 1970-01-01 00:00:00.0 +
+++ xchat-2.8.8/debian/patches/56_save_servlist.patch 2012-09-30 15:21:39.0 +
@@ -0,0 +1,129 @@
+Write to temporary file and then rename.
+Same approach like I did for bug 463072.
+Fixes loss of data when disk is full.
+Closes: #147832.
+
+Index: xchat-2.8.8/src/common/servlist.c
+===
+--- xchat-2.8.8.orig/src/common/servlist.c 2012-09-30 12:23:53.0 +
xchat-2.8.8/src/common/servlist.c 2012-09-30 12:23:55.0 +
+@@ -1072,6 +1072,7 @@
+ servlist_save (void)
+ {
+ FILE *fp;
++ int nb;
+ char buf[256];
+ ircnet *net;
+ ircserver *serv;
+@@ -1080,12 +1081,12 @@
+ #ifndef WIN32
+ int first = FALSE;
+
+- snprintf (buf, sizeof (buf), %s/servlist_.conf, get_xdir_fs ());
++ snprintf (buf, sizeof (buf), %s/servlist_.conf.bug147832, get_xdir_fs ());
+ if (access (buf, F_OK) != 0)
+ first = TRUE;
+ #endif
+
+- fp = xchat_fopen_file (servlist_.conf, w, 0);
++ fp = xchat_fopen_file (servlist_.conf.bug147832, w, 0);
+ if (!fp)
+ return FALSE;
+
+@@ -1093,32 +1094,32 @@
+ if (first)
+ chmod (buf, 0600);
+ #endif
+- fprintf (fp, v=PACKAGE_VERSION\n\n);
++ nb = fprintf (fp, v=PACKAGE_VERSION\n\n);
+
+ list = network_list;
+ while (list)
+ {
+ net = list-data;
+
+- fprintf (fp, N=%s\n, net-name);
++ if( nb 0 ) nb = fprintf (fp, N=%s\n, net-name);
+ if (net-nick)
+- fprintf (fp, I=%s\n, net-nick);
++ if( nb 0 ) nb = fprintf (fp, I=%s\n, net-nick);
+ if (net-nick2)
+- fprintf (fp, i=%s\n, net-nick2);
++ if( nb 0 ) nb = fprintf (fp, i=%s\n, net-nick2);
+ if (net-user)
+- fprintf (fp, U=%s\n, net-user);
++ if( nb 0 ) nb = fprintf (fp, U=%s\n, net-user);
+ if (net-real)
+- fprintf (fp, R=%s\n, net-real);
++ if( nb 0 ) nb = fprintf (fp, R=%s\n, net-real);
+ if (net-pass)
+- fprintf (fp, P=%s\n, net-pass);
++ if( nb 0 ) nb = fprintf (fp, P=%s\n, net-pass);
+ if (net-autojoin)
+- fprintf (fp, J=%s\n, net-autojoin);
++ if( nb 0 ) nb = fprintf (fp, J=%s\n, net-autojoin);
+ if (net-nickserv)
+- fprintf (fp, B=%s\n, net-nickserv);
++ if( nb 0 ) nb = fprintf (fp, B=%s\n, net-nickserv);
+ if (net-encoding strcasecmp (net-encoding, System)
+ strcasecmp (net-encoding, System default))
+ {
+- fprintf (fp, E=%s\n, net-encoding);
++ if( nb 0 ) nb = fprintf (fp, E=%s\n, net-encoding);
+ if (!servlist_check_encoding (net-encoding))
+ {
+ snprintf (buf, sizeof (buf), _(Warning: \%s\ character set is unknown. No conversion will be applied for network %s.),
+@@ -1128,28 +1129,44 @@
+ }
+
+ if (net-command)
+- token_foreach (net-command, '\n', servlist_write_ccmd, fp);
++ if( nb 0 )
++if( token_foreach (net-command, '\n',
Bug#689158: marked as done (unblock: tomcat7/7.0.28-3)
Your message dated Sun, 07 Oct 2012 13:48:50 +0200
with message-id 50716c22.6050...@dogguy.org
and subject line Re: Bug#689158: unblock: tomcat7/7.0.28-3
has caused the Debian Bug report #689158,
regarding unblock: tomcat7/7.0.28-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.)
--
689158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689158
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
Dear Release Maintainers:
Please unblock package tomcat7.
The upload of tomcat7-7.0.28-3 addresses bug #688936 (tomcat7 modifies
conffile /etc/logrotate.d/tomcat7 in postinst). The unblock request
for wheezy is because the bug is a policy violation.
The debdiff between this version and the package currently in wheezy is
attached. Thank you for your consideration.
Regards,
tony
unblock tomcat7/7.0.28-3
diff -Nru tomcat7-7.0.28/debian/changelog tomcat7-7.0.28/debian/changelog
--- tomcat7-7.0.28/debian/changelog 2012-07-10 22:13:47.0 -0700
+++ tomcat7-7.0.28/debian/changelog 2012-09-27 14:16:09.0 -0700
@@ -1,3 +1,14 @@
+tomcat7 (7.0.28-3) unstable; urgency=low
+
+ [ Miguel Landaeta ]
+ * Fix small typo in README.Debian.
+
+ [ tony mancill ]
+ * Use ucf and a template for /etc/logrotate.d/tomcat6 file to avoid
+updating the shipped conffile. (Closes: #688936)
+
+ -- tony mancill tmanc...@debian.org Thu, 27 Sep 2012 10:55:35 -0700
+
tomcat7 (7.0.28-2) unstable; urgency=low
[ Jakub Adam ]
diff -Nru tomcat7-7.0.28/debian/logrotate tomcat7-7.0.28/debian/logrotate
--- tomcat7-7.0.28/debian/logrotate 2012-07-10 22:13:47.0 -0700
+++ tomcat7-7.0.28/debian/logrotate 1969-12-31 16:00:00.0 -0800
@@ -1,8 +0,0 @@
-/var/log/tomcat7/catalina.out {
- copytruncate
- weekly
- rotate 52
- compress
- missingok
- create 640 @@@TOMCAT7USER@@@ adm
-}
diff -Nru tomcat7-7.0.28/debian/logrotate.md5sum tomcat7-7.0.28/debian/logrotate.md5sum
--- tomcat7-7.0.28/debian/logrotate.md5sum 1969-12-31 16:00:00.0 -0800
+++ tomcat7-7.0.28/debian/logrotate.md5sum 2012-09-27 14:16:09.0 -0700
@@ -0,0 +1 @@
+9e56464a7cc25288a994171d0e303ba6 logrotate.template
diff -Nru tomcat7-7.0.28/debian/logrotate.template tomcat7-7.0.28/debian/logrotate.template
--- tomcat7-7.0.28/debian/logrotate.template 1969-12-31 16:00:00.0 -0800
+++ tomcat7-7.0.28/debian/logrotate.template 2012-09-27 14:16:09.0 -0700
@@ -0,0 +1,8 @@
+/var/log/tomcat7/catalina.out {
+ copytruncate
+ weekly
+ rotate 52
+ compress
+ missingok
+ create 640 tomcat7 adm
+}
diff -Nru tomcat7-7.0.28/debian/README.Debian tomcat7-7.0.28/debian/README.Debian
--- tomcat7-7.0.28/debian/README.Debian 2012-07-10 22:13:47.0 -0700
+++ tomcat7-7.0.28/debian/README.Debian 2012-09-27 14:16:09.0 -0700
@@ -28,7 +28,7 @@
Deviations from upstream's tomcat7:
* In order to prevent library duplication, this version of tomcat
-does provide tomcat-dbcp.jar. Instead, it uses commons-dbcp.jar
+does not provide tomcat-dbcp.jar. Instead, it uses commons-dbcp.jar
from the libcommons-dbcp-java package. This also means that
libtomcat7-java does not provide the tomcat-dbcp.pom for the
local maven-repo. For more information and rationale, see:
diff -Nru tomcat7-7.0.28/debian/rules tomcat7-7.0.28/debian/rules
--- tomcat7-7.0.28/debian/rules 2012-07-10 22:13:47.0 -0700
+++ tomcat7-7.0.28/debian/rules 2012-09-27 14:16:09.0 -0700
@@ -85,7 +85,6 @@
dh_testroot
dh_prep
dh_installdirs
- cp debian/logrotate debian/tomcat7/etc/logrotate.d/tomcat7
binary-indep: build install
dh_testdir
diff -Nru tomcat7-7.0.28/debian/tomcat7.install tomcat7-7.0.28/debian/tomcat7.install
--- tomcat7-7.0.28/debian/tomcat7.install 2012-07-10 22:13:47.0 -0700
+++ tomcat7-7.0.28/debian/tomcat7.install 2012-09-27 14:16:09.0 -0700
@@ -5,3 +5,5 @@
debian/default_root /usr/share/tomcat7-root/
debian/defaults.template /usr/share/tomcat7/
debian/defaults.md5sum /usr/share/tomcat7/
+debian/logrotate.template /usr/share/tomcat7/
+debian/logrotate.md5sum /usr/share/tomcat7/
diff -Nru tomcat7-7.0.28/debian/tomcat7.postinst tomcat7-7.0.28/debian/tomcat7.postinst
--- tomcat7-7.0.28/debian/tomcat7.postinst 2012-07-10 22:13:47.0 -0700
+++ tomcat7-7.0.28/debian/tomcat7.postinst 2012-09-27 14:16:09.0 -0700
@@ -4,6 +4,8 @@
. /usr/share/debconf/confmodule
TEMPLATE=/usr/share/tomcat7/defaults.template
CONFFILE=/etc/default/tomcat7
Bug#688928: marked as done (unblock: rsyslog/5.8.11-2)
Your message dated Sun, 07 Oct 2012 13:33:43 +0200
with message-id 50716897@dogguy.org
and subject line Re: Bug#688928: unblock: rsyslog/5.8.11-2
has caused the Debian Bug report #688928,
regarding unblock: rsyslog/5.8.11-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.)
--
688928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688928
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 rsyslog
The changelog reads:
* Disable omstdout module again. Upstream doesn't consider it viable for
production use but mainly for the internal testbench.
* debian/patches/03-fix_relp_dns_resolution.patch: When using RELP for
remote logging, correctly resolve the client hostname if the fromhost
property contains the client IP. (Closes: #682529)
Thanks to Apollon Oikonomopoulos for the patch.
Especially, the first point, dropping the omstdout plugin, is important.
I accidentally had that enabled in my last upload, but talking with
upstream it quickly became clear that this module should not be shipped
in our next Debian release.
Full debdiff attached.
Thanks for your great work,
Michael
unblock rsyslog/5.8.11-2
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index 849126e..ff6eca0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+rsyslog (5.8.11-2) unstable; urgency=low
+
+ * Disable omstdout module again. Upstream doesn't consider it viable for
+production use but mainly for the internal testbench.
+ * debian/patches/03-fix_relp_dns_resolution.patch: When using RELP for
+remote logging, correctly resolve the client hostname if the fromhost
+property contains the client IP. (Closes: #682529)
+Thanks to Apollon Oikonomopoulos for the patch.
+
+ -- Michael Biebl bi...@debian.org Wed, 26 Sep 2012 20:36:09 +0200
+
rsyslog (5.8.11-1) unstable; urgency=low
* New upstream release.
diff --git a/debian/patches/03-fix_relp_dns_resolution.patch b/debian/patches/03-fix_relp_dns_resolution.patch
new file mode 100644
index 000..b3dfeab
--- /dev/null
+++ b/debian/patches/03-fix_relp_dns_resolution.patch
@@ -0,0 +1,44 @@
+--- a/plugins/imrelp/imrelp.c
b/plugins/imrelp/imrelp.c
+@@ -44,6 +44,7 @@
+ #include msg.h
+ #include unicode-helper.h
+ #include prop.h
++#include glbl.h
+
+ MODULE_TYPE_INPUT
+ MODULE_TYPE_NOKEEP
+@@ -52,6 +53,7 @@
+ DEF_IMOD_STATIC_DATA
+ DEFobjCurrIf(net)
+ DEFobjCurrIf(prop)
++DEFobjCurrIf(glbl)
+
+ /* Module static data */
+ static relpEngine_t *pRelpEngine; /* our relp engine */
+@@ -104,6 +106,9 @@
+ CHKiRet(relpEngineSetDbgprint(pRelpEngine, dbgprintf));
+ CHKiRet(relpEngineSetEnableCmd(pRelpEngine, (uchar*) syslog, eRelpCmdState_Required));
+ CHKiRet(relpEngineSetSyslogRcv(pRelpEngine, onSyslogRcv));
++ if (!glbl.GetDisableDNS()) {
++ CHKiRet(relpEngineSetDnsLookupMode(pRelpEngine, 1));
++ }
+ }
+
+ CHKiRet(relpEngineAddListner(pRelpEngine, pNewVal));
+@@ -162,6 +167,7 @@
+ iRet = relpEngineDestruct(pRelpEngine);
+
+ /* release objects we used */
++ objRelease(glbl, CORE_COMPONENT);
+ objRelease(prop, CORE_COMPONENT);
+ objRelease(net, LM_NET_FILENAME);
+ ENDmodExit
+@@ -187,6 +193,7 @@
+ CODEmodInit_QueryRegCFSLineHdlr
+ pRelpEngine = NULL;
+ /* request objects we use */
++ CHKiRet(objUse(glbl, CORE_COMPONENT));
+ CHKiRet(objUse(prop, CORE_COMPONENT));
+ CHKiRet(objUse(net, LM_NET_FILENAME));
+
diff --git a/debian/patches/series b/debian/patches/series
index c92adc9..d985f46 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
# Debian patches for rsyslog
01-dont_create_db.patch
02-path_max.patch
+03-fix_relp_dns_resolution.patch
diff --git a/debian/rsyslog.install b/debian/rsyslog.install
index a538bfc..6c4248e 100644
--- a/debian/rsyslog.install
+++ b/debian/rsyslog.install
@@ -19,7 +19,6 @@ usr/lib/rsyslog/lmtcpsrv.so
usr/lib/rsyslog/lmzlibw.so
usr/lib/rsyslog/ommail.so
usr/lib/rsyslog/omprog.so
-usr/lib/rsyslog/omstdout.so
usr/lib/rsyslog/omuxsock.so
usr/lib/rsyslog/omruleset.so
usr/lib/rsyslog/pm*.so
diff --git a/debian/rules b/debian/rules
index 21e4367..c04f837 100755
--- a/debian/rules
Re: request freeze exception for slony1-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/09/2012 04:58, Peter Eisentraut wrote: According to bug #678979 [0], which was submitted by the lead upstream developer, slony 2.0 does not work well with postgresql 9.1. Therefore, we had to resolve to making an upgrade to slony version 2.1, and I request that that be allowed into wheezy now. To be precise: The source package name is slony1-2. Unfortunately, we are not able to accept such large changes at this stage of the freeze. [2] Since slony in Debian have little popcon, does it make sense to skip the Wheezy release? iow, remove slony from wheezy (since it doesn't work and we are not able to accept the new one). Alternatively, we could very well accept a targeted fix based on current Wheezy's version… (correct me if I'm wrong), the discussion in #678979 made me think that it was not possible to extract a minimal patch. Besides, once Wheezy is released, you may upload sid's version to wheezy-backports so that wheezy users can enjoy it as well. You'll also be able to update it more often than you might do in a stable release. [2] 333 files changed, 49485 insertions(+), 13745 deletions(-) [0]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678979 [1]: http://packages.qa.debian.org/s/slony1-2.html Kind regards, - -- Mehdi Dogguy مهدي الدڤي -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQcXXvAAoJEDe1GR0FRlJoCZIH/2NVSzPWb6Nl+6IWG4aq8aRz E/syjXfLbdIkAljxWrEgLbUHIgZiiHKQhWfhRR3oyvpvCfZ7/ak1QaK8YGy1tj6b FwkOVzcLPjPmQXoYtyhMtbOnTPFkb9F/V6auROLQ/NyJMro1FAT+Y0/6gnDVRZ69 CPN6iVFwVxiWzNVK9SqMyKanwj+6u0lhBU7rzqjXgnD403Hl6a8G7KbLp1PGW+bk tsLYSMjCq3gQrvn2CqiuP/GSpW1Qz30o7OF3HzRltlfy/SM5ebN3XZBzyixRrUhk 8Y/415uIHP37ULAUc+OeFKLu+Bx9xP0hdQcb85X+h+cmCvKcZeyfWqwLxqLwrbs= =irBk -END PGP SIGNATURE- -- 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/507175f4.30...@dogguy.org
Bug#688980: unblock: r-cran-pscl/1.03.10-1.1
On 27/09/2012 21:34, Sébastien Villemot wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock In order to fix #684823, which solution does the Release Team prefer: - unblock r-cran-pscl/1.03.10-1.1 which is currently in sid and contains the fix, - or me making an upload to t-p-u, with the attached patch? I think the best way forwad would be to upload a targeted fix to t-p-u. Please go ahead and thanks for your work! Regards, -- Mehdi Dogguy مهدي الدڤي -- 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/50717772.5040...@dogguy.org
Bug#688887: marked as done (unblock: fcitx/1:4.2.4.1-7)
Your message dated Sun, 07 Oct 2012 14:38:57 +0200
with message-id 507177e1.6030...@dogguy.org
and subject line Re: Bug#67: unblock: fcitx/1:4.2.4.1-7
has caused the Debian Bug report #67,
regarding unblock: fcitx/1:4.2.4.1-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
67: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=67
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
This is the follow up improvement of the fix intended for RC bug
#684245. This patch avoids all situations that may be encountered to
trigger the bug in gnumeric, fix for that bug has been submitted and
applied to gnumeric upstream repository. More information can be found
at http://bugs.debian.org/687729 and
https://bugzilla.gnome.org/show_bug.cgi?id=684511
unblock: fcitx/1:4.2.4.1-7
diff -Nru fcitx-4.2.4.1/debian/changelog fcitx-4.2.4.1/debian/changelog
--- fcitx-4.2.4.1/debian/changelog 2012-09-15 19:51:00.0 +
+++ fcitx-4.2.4.1/debian/changelog 2012-09-26 16:23:05.0 +
@@ -1,3 +1,10 @@
+fcitx (1:4.2.4.1-7) unstable; urgency=low
+
+ * improve 0009-gnumeric_cursor_keys_edit.patch to fix bug
+completely.
+
+ -- YunQiang Su wzss...@gmail.com Wed, 26 Sep 2012 22:08:29 +0800
+
fcitx (1:4.2.4.1-6) unstable; urgency=low
* add gbp.conf for wheezy
diff -Nru fcitx-4.2.4.1/debian/patches/0009-gnumeric_cursor_keys_edit.patch
fcitx-4.2.4.1/debian/patches/0009-gnumeric_cursor_keys_edit.patch
--- fcitx-4.2.4.1/debian/patches/0009-gnumeric_cursor_keys_edit.patch
2012-09-15
18:40:35.0 +
+++ fcitx-4.2.4.1/debian/patches/0009-gnumeric_cursor_keys_edit.patch
2012-09-26
16:23:05.0 +
@@ -1,8 +1,8 @@
-diff --git a/src/frontend/ipc/ipc.c b/src/frontend/ipc/ipc.c
-index 1d57567..67261fe 100644
a/src/frontend/ipc/ipc.c
-+++ b/src/frontend/ipc/ipc.c
-@@ -43,6 +43,7 @@ typedef struct _FcitxIPCIC {
+Index: fcitx/src/frontend/ipc/ipc.c
+===
+--- fcitx.orig/src/frontend/ipc/ipc.c 2012-09-26 22:01:16.354865405 +0800
fcitx/src/frontend/ipc/ipc.c 2012-09-26 22:02:26.979215609 +0800
+@@ -43,6 +43,7 @@
char* surroundingText;
unsigned int anchor;
unsigned int cursor;
@@ -10,7 +10,7 @@
} FcitxIPCIC;
typedef struct _FcitxIPCFrontend {
-@@ -349,6 +350,7 @@ void IPCCreateIC(void* arg, FcitxInputContext*
context, void* priv)
+@@ -349,6 +350,7 @@
ipcic-id = ipc-maxid;
ipc-maxid ++;
@@ -18,7 +18,7 @@
sprintf(ipcic-path, FCITX_IC_DBUS_PATH, ipcic-id);
uint32_t arg1, arg2, arg3, arg4;
-@@ -930,6 +932,23 @@ static void IPCICSetCursorRect(FcitxIPCFrontend*
ipc, FcitxInputContext* ic, int
+@@ -930,6 +932,23 @@
void IPCUpdatePreedit(void* arg, FcitxInputContext* ic)
{
@@ -42,3 +42,56 @@
if (ic-contextCaps CAPACITY_FORMATTED_PREEDIT) {
FcitxIPCFrontend* ipc = (FcitxIPCFrontend*) arg;
dbus_uint32_t serial = 0; // unique number to associate
replies with requests
+Index: fcitx/data/script/fcitx-configtool
+===
+--- fcitx.orig/data/script/fcitx-configtool2012-09-26 22:01:57.235068121
+0800
fcitx/data/script/fcitx-configtool 2012-09-26 22:03:16.283460099 +0800
+@@ -32,7 +32,7 @@
+ exec $command kcm_fcitx
+ fi
+ else
+-run_gtk $1
++run_gtk3 $1
+ fi
+ }
+
+Index: fcitx/src/frontend/gtk2/fcitximcontext.c
+===
+--- fcitx.orig/src/frontend/gtk2/fcitximcontext.c 2012-09-26
22:01:57.235068121 +0800
fcitx/src/frontend/gtk2/fcitximcontext.c 2012-09-26
22:03:16.287460117 +0800
+@@ -465,7 +465,7 @@
+
+ /* set_cursor_location_internal() will get origin from X server,
+ * it blocks UI. So delay it to idle callback. */
+-g_idle_add_full(G_PRIORITY_DEFAULT_IDLE,
++gdk_threads_add_idle_full(G_PRIORITY_DEFAULT_IDLE,
+ (GSourceFunc) _set_cursor_location_internal,
+ g_object_ref(fcitxcontext),
+ (GDestroyNotify) g_object_unref);
+@@ -584,8 +584,6 @@
+ /* do nothing */
+ }
+ }
+-
+-g_signal_emit(context, _signal_preedit_changed_id, 0);
+ }
+
+ static void
+@@ -695,8 +693,6 @@
+ /* do nothing */
+ }
+ }
+-
+-g_signal_emit(context, _signal_preedit_changed_id,
Bug#689869: unblock: gtk+3.0/3.4.2-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package gtk+3.0
It fixes an annoying bug where the F10 key is not properly handled but
treated like Shift+F10.
Full debdiff is attached.
unblock gtk+3.0/3.4.2-4
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru gtk+3.0-3.4.2/debian/changelog gtk+3.0-3.4.2/debian/changelog
--- gtk+3.0-3.4.2/debian/changelog 2012-08-06 22:07:47.0 +0200
+++ gtk+3.0-3.4.2/debian/changelog 2012-09-21 18:30:43.0 +0200
@@ -1,3 +1,11 @@
+gtk+3.0 (3.4.2-4) unstable; urgency=low
+
+ * debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch:
+With xkb-data 2.5.1-2.1 preserving the Shift modifier, GTK+ can properly
+map F10 and Shift-F10 to different key bindings. Closes: #658392
+
+ -- Michael Biebl bi...@debian.org Fri, 21 Sep 2012 18:30:41 +0200
+
gtk+3.0 (3.4.2-3) unstable; urgency=low
[ Josselin Mouette ]
diff -Nru gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch
--- gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch 1970-01-01 01:00:00.0 +0100
+++ gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch 2012-09-04 03:06:32.0 +0200
@@ -0,0 +1,69 @@
+From 314b6abbe8d8daae1e2de50b15cc9b6553af1f3d Mon Sep 17 00:00:00 2001
+From: Matthias Clasen mcla...@redhat.com
+Date: Sat, 1 Sep 2012 22:51:18 -0400
+Subject: [PATCH] Try harder to discriminate Shift-F10 and F10
+
+A change in xkeyboard-config 2.4.1 made it so that function keys
+now have a shift level which has the same symbol, but 'eats' the
+shift modifier. This would ordinarily make it impossible for us
+to discriminate between these key combinations.
+
+This commit tries harder to discriminate in 2 ways:
+- XKB has a mechanism to tell us when a modifier should not be
+ consumed even though it was used in determining the level.
+ We now respect such 'preserved' modifiers. This does not fix
+ the Shift-F10 vs F10 problem yet, since xkeyboard-config does
+ not currently mark Shift as preserved for function keys.
+- Don't consume modifiers that do not change the symbol. For
+ the function keys, the symbol on the shift level is the same
+ as the base level, so we don't consider Shift consumed.
+
+For more background on the xkeyboard-config change, see
+https://bugs.freedesktop.org/show_bug.cgi?id=45008
+
+https://bugzilla.gnome.org/show_bug.cgi?id=661973
+---
+ gdk/x11/gdkkeys-x11.c | 20 +++-
+ 1 file changed, 15 insertions(+), 5 deletions(-)
+
+Index: gtk+-3.4.2/gdk/x11/gdkkeys-x11.c
+===
+--- gtk+-3.4.2.orig/gdk/x11/gdkkeys-x11.c 2012-05-02 14:05:07.0 +0200
gtk+-3.4.2/gdk/x11/gdkkeys-x11.c 2012-09-04 03:05:24.621782410 +0200
+@@ -1113,6 +1113,8 @@
+ int found = 0;
+
+ for (i=0,entry=type-map;itype-map_count;i++,entry++) {
++if (!entry-active)
++ continue;
+ if (mods_rtrn) {
+ int bits = 0;
+ unsigned long tmp = entry-mods.mask;
+@@ -1123,14 +1125,22 @@
+ }
+ /* We always add one-modifiers levels to mods_rtrn since
+ * they can't wipe out bits in the state unless the
+- * level would be triggered. But return other modifiers
+- *
++ * level would be triggered. But not if they don't change
++ * the symbol (otherwise we can't discriminate Shift-F10
++ * and F10 anymore). And don't add modifiers that are
++ * explicitly marked as preserved, either.
+ */
+-if (bits == 1 || (modstype-mods.mask)==entry-mods.mask)
+-*mods_rtrn |= entry-mods.mask;
++if ((bits == 1 syms[col+entry-level] != syms[col]) ||
++(modstype-mods.mask) == entry-mods.mask)
++ {
++if (type-preserve)
++ *mods_rtrn |= (entry-mods.mask ~type-preserve[i].mask);
++else
++ *mods_rtrn |= entry-mods.mask;
++ }
+ }
+
+-if (!foundentry-active((modstype-mods.mask)==entry-mods.mask)) {
++if (!found((modstype-mods.mask)==entry-mods.mask)) {
+ col+= entry-level;
+ if (type-preserve)
+ preserve= type-preserve[i].mask;
diff -Nru gtk+3.0-3.4.2/debian/patches/series
Bug#689871: unblock: notification-daemon/0.7.6-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package notification-daemon
Version 0.7.6 contains a single bug fix and translation updates only.
It has been in unstable for 8 days without any new bug reports.
Debdiff (minus autotools garbage) is attached.
Cheers,
Michael
unblock notification-daemon/0.7.6-1
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/NEWS b/NEWS
index a41d1b4..dff69c1 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,8 @@
+NEW in 0.7.6:
+==
+- Fix a wrong loop condition
+- Translation updates (Marathi)
+
NEW in 0.7.5:
==
- Translation updates (Hindi, Catalan)
diff --git a/configure.ac b/configure.ac
index a942c69..2bf86f7 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3,7 +3,7 @@ dnl Process this file with autoconf to create configure.
dnl
dnl # Initialize autoconf
dnl
-AC_INIT([notification-daemon],[0.7.5],[https://bugzilla.gnome.org/enter_bug.cgi?product=notification-daemon],[notification-daemon])
+AC_INIT([notification-daemon],[0.7.6],[https://bugzilla.gnome.org/enter_bug.cgi?product=notification-daemon],[notification-daemon])
AC_PREREQ(2.63)
AC_CONFIG_HEADERS([config.h])
@@ -15,7 +15,7 @@ dnl # Version information
dnl
NOTIFICATION_DAEMON_MAJOR_VERSION=0
NOTIFICATION_DAEMON_MINOR_VERSION=7
-NOTIFICATION_DAEMON_MICRO_VERSION=5
+NOTIFICATION_DAEMON_MICRO_VERSION=6
NOTIFICATION_DAEMON_DEVEL_VERSION=0
NOTIFICATION_DAEMON_VERSION=$NOTIFICATION_DAEMON_MAJOR_VERSION.$NOTIFICATION_DAEMON_MINOR_VERSION.$NOTIFICATION_DAEMON_MICRO_VERSION
diff --git a/po/LINGUAS b/po/LINGUAS
index dec82d8..8d4c086 100644
--- a/po/LINGUAS
+++ b/po/LINGUAS
@@ -35,6 +35,7 @@ kn
ko
lt
lv
+mr
ms
nb
nl
diff --git a/po/mr.po b/po/mr.po
new file mode 100644
index 000..4f98754
--- /dev/null
+++ b/po/mr.po
@@ -0,0 +1,49 @@
+# Marathi translation for notification-daemon.
+# Copyright (C) 2012 notification-daemon's COPYRIGHT HOLDER
+# This file is distributed under the same license as the notification-daemon package.
+#
+# Sandeep Shedmake sshed...@redhat.com, 2012.
+msgid
+msgstr
+Project-Id-Version: notification-daemon master\n
+Report-Msgid-Bugs-To: http://bugzilla.gnome.org/enter_bug.cgi?;
+product=notification-daemonkeywords=I18N+L10Ncomponent=general\n
+POT-Creation-Date: 2012-07-07 17:05+\n
+PO-Revision-Date: 2012-08-14 14:28+0530\n
+Last-Translator: Sandeep Shedmake sshed...@redhat.com\n
+Language-Team: Marathi m...@li.org\n
+Language: mr\n
+MIME-Version: 1.0\n
+Content-Type: text/plain; charset=UTF-8\n
+Content-Transfer-Encoding: 8bit\n
+Plural-Forms: nplurals=2; plural=n != 1;\n
+X-Generator: Lokalize 1.4\n
+
+#: ../src/daemon.c:188
+msgid Exceeded maximum number of notifications
+msgstr सूचनांची कमाल संख्या वाढवले
+
+#: ../src/daemon.c:251
+msgid Invalid notification identifier
+msgstr अवैध सूचना ओळखकर्ता
+
+#: ../src/nd-queue.c:472
+msgid Clear all notifications
+msgstr सर्व सूचना नष्ट करा
+
+#: ../src/nd-queue.c:883
+msgid Notifications
+msgstr सूचना
+
+#: ../src/sound.c:35
+msgid Notification
+msgstr सूचना
+
+#: ../data/notification-daemon.desktop.in.in.h:1
+msgid Notification Daemon
+msgstr सूचना डिमन
+
+#: ../data/notification-daemon.desktop.in.in.h:2
+msgid Display notifications
+msgstr डिस्पले सूचना
+
diff --git a/src/nd-queue.c b/src/nd-queue.c
index 3675fca..de73940 100644
--- a/src/nd-queue.c
+++ b/src/nd-queue.c
@@ -507,7 +507,7 @@ destroy_screens (NdQueue *queue)
gdkwindow = gdk_screen_get_root_window (screen);
gdk_window_remove_filter (gdkwindow, (GdkFilterFunc) screen_xevent_filter, queue-priv-screens[i]);
-for (j = 0; i queue-priv-screens[i]-n_stacks; j++) {
+for (j = 0; j queue-priv-screens[i]-n_stacks; j++) {
g_object_unref (queue-priv-screens[i]-stacks[j]);
queue-priv-screens[i]-stacks[j] = NULL;
}
Bug#687779: unblock: ksh/93u+20120628-1
On 15/09/2012 19:51, Oliver Kiddle wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Hi, Please unblock package ksh/93u+20120628-1 which fixes #679966 (severity grave). Frankly it would be better to exclude ksh from the next Debian release than include it with this bug because it breaks very basic functionality in the shell. The fix was done upstream so I don't really know the details. So intead of reverting a patch [1] and re-open a severity normal bug, you uploaded a new upstream release [2] ? [1] 1 file changed, 11 insertions(+) [2] 232 files changed, 4897 insertions(+), 2082 deletions(-) Regards, -- Mehdi Dogguy مهدي الدڤي -- 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/50718038.8090...@dogguy.org
Bug#689869: marked as done (unblock: gtk+3.0/3.4.2-4)
Your message dated Sun, 07 Oct 2012 15:19:06 +0200
with message-id 5071814a.2070...@dogguy.org
and subject line Re: Bug#689869: unblock: gtk+3.0/3.4.2-4
has caused the Debian Bug report #689869,
regarding unblock: gtk+3.0/3.4.2-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.)
--
689869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689869
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 gtk+3.0
It fixes an annoying bug where the F10 key is not properly handled but
treated like Shift+F10.
Full debdiff is attached.
unblock gtk+3.0/3.4.2-4
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru gtk+3.0-3.4.2/debian/changelog gtk+3.0-3.4.2/debian/changelog
--- gtk+3.0-3.4.2/debian/changelog 2012-08-06 22:07:47.0 +0200
+++ gtk+3.0-3.4.2/debian/changelog 2012-09-21 18:30:43.0 +0200
@@ -1,3 +1,11 @@
+gtk+3.0 (3.4.2-4) unstable; urgency=low
+
+ * debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch:
+With xkb-data 2.5.1-2.1 preserving the Shift modifier, GTK+ can properly
+map F10 and Shift-F10 to different key bindings. Closes: #658392
+
+ -- Michael Biebl bi...@debian.org Fri, 21 Sep 2012 18:30:41 +0200
+
gtk+3.0 (3.4.2-3) unstable; urgency=low
[ Josselin Mouette ]
diff -Nru gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch
--- gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch 1970-01-01 01:00:00.0 +0100
+++ gtk+3.0-3.4.2/debian/patches/074_try-harder-to-discriminate-Shift-F10-and-F10.patch 2012-09-04 03:06:32.0 +0200
@@ -0,0 +1,69 @@
+From 314b6abbe8d8daae1e2de50b15cc9b6553af1f3d Mon Sep 17 00:00:00 2001
+From: Matthias Clasen mcla...@redhat.com
+Date: Sat, 1 Sep 2012 22:51:18 -0400
+Subject: [PATCH] Try harder to discriminate Shift-F10 and F10
+
+A change in xkeyboard-config 2.4.1 made it so that function keys
+now have a shift level which has the same symbol, but 'eats' the
+shift modifier. This would ordinarily make it impossible for us
+to discriminate between these key combinations.
+
+This commit tries harder to discriminate in 2 ways:
+- XKB has a mechanism to tell us when a modifier should not be
+ consumed even though it was used in determining the level.
+ We now respect such 'preserved' modifiers. This does not fix
+ the Shift-F10 vs F10 problem yet, since xkeyboard-config does
+ not currently mark Shift as preserved for function keys.
+- Don't consume modifiers that do not change the symbol. For
+ the function keys, the symbol on the shift level is the same
+ as the base level, so we don't consider Shift consumed.
+
+For more background on the xkeyboard-config change, see
+https://bugs.freedesktop.org/show_bug.cgi?id=45008
+
+https://bugzilla.gnome.org/show_bug.cgi?id=661973
+---
+ gdk/x11/gdkkeys-x11.c | 20 +++-
+ 1 file changed, 15 insertions(+), 5 deletions(-)
+
+Index: gtk+-3.4.2/gdk/x11/gdkkeys-x11.c
+===
+--- gtk+-3.4.2.orig/gdk/x11/gdkkeys-x11.c 2012-05-02 14:05:07.0 +0200
gtk+-3.4.2/gdk/x11/gdkkeys-x11.c 2012-09-04 03:05:24.621782410 +0200
+@@ -1113,6 +1113,8 @@
+ int found = 0;
+
+ for (i=0,entry=type-map;itype-map_count;i++,entry++) {
++if (!entry-active)
++ continue;
+ if (mods_rtrn) {
+ int bits = 0;
+ unsigned long tmp = entry-mods.mask;
+@@ -1123,14 +1125,22 @@
+ }
+ /* We always add one-modifiers levels to mods_rtrn since
+ * they can't wipe out bits in the state unless the
+- * level would be triggered. But return other modifiers
+- *
++ * level would be triggered. But not if they don't change
++ * the symbol (otherwise we can't discriminate Shift-F10
++ * and F10 anymore). And don't add modifiers that are
++ * explicitly marked as preserved, either.
+ */
+-if (bits == 1 ||
Bug#689871: marked as done (unblock: notification-daemon/0.7.6-1)
Your message dated Sun, 07 Oct 2012 15:17:22 +0200 with message-id 507180e2.9010...@dogguy.org and subject line Re: Bug#689871: unblock: notification-daemon/0.7.6-1 has caused the Debian Bug report #689871, regarding unblock: notification-daemon/0.7.6-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.) -- 689871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689871 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 notification-daemon Version 0.7.6 contains a single bug fix and translation updates only. It has been in unstable for 8 days without any new bug reports. Debdiff (minus autotools garbage) is attached. Cheers, Michael unblock notification-daemon/0.7.6-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/NEWS b/NEWS index a41d1b4..dff69c1 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,8 @@ +NEW in 0.7.6: +== +- Fix a wrong loop condition +- Translation updates (Marathi) + NEW in 0.7.5: == - Translation updates (Hindi, Catalan) diff --git a/configure.ac b/configure.ac index a942c69..2bf86f7 100644 --- a/configure.ac +++ b/configure.ac @@ -3,7 +3,7 @@ dnl Process this file with autoconf to create configure. dnl dnl # Initialize autoconf dnl -AC_INIT([notification-daemon],[0.7.5],[https://bugzilla.gnome.org/enter_bug.cgi?product=notification-daemon],[notification-daemon]) +AC_INIT([notification-daemon],[0.7.6],[https://bugzilla.gnome.org/enter_bug.cgi?product=notification-daemon],[notification-daemon]) AC_PREREQ(2.63) AC_CONFIG_HEADERS([config.h]) @@ -15,7 +15,7 @@ dnl # Version information dnl NOTIFICATION_DAEMON_MAJOR_VERSION=0 NOTIFICATION_DAEMON_MINOR_VERSION=7 -NOTIFICATION_DAEMON_MICRO_VERSION=5 +NOTIFICATION_DAEMON_MICRO_VERSION=6 NOTIFICATION_DAEMON_DEVEL_VERSION=0 NOTIFICATION_DAEMON_VERSION=$NOTIFICATION_DAEMON_MAJOR_VERSION.$NOTIFICATION_DAEMON_MINOR_VERSION.$NOTIFICATION_DAEMON_MICRO_VERSION diff --git a/po/LINGUAS b/po/LINGUAS index dec82d8..8d4c086 100644 --- a/po/LINGUAS +++ b/po/LINGUAS @@ -35,6 +35,7 @@ kn ko lt lv +mr ms nb nl diff --git a/po/mr.po b/po/mr.po new file mode 100644 index 000..4f98754 --- /dev/null +++ b/po/mr.po @@ -0,0 +1,49 @@ +# Marathi translation for notification-daemon. +# Copyright (C) 2012 notification-daemon's COPYRIGHT HOLDER +# This file is distributed under the same license as the notification-daemon package. +# +# Sandeep Shedmake sshed...@redhat.com, 2012. +msgid +msgstr +Project-Id-Version: notification-daemon master\n +Report-Msgid-Bugs-To: http://bugzilla.gnome.org/enter_bug.cgi?; +product=notification-daemonkeywords=I18N+L10Ncomponent=general\n +POT-Creation-Date: 2012-07-07 17:05+\n +PO-Revision-Date: 2012-08-14 14:28+0530\n +Last-Translator: Sandeep Shedmake sshed...@redhat.com\n +Language-Team: Marathi m...@li.org\n +Language: mr\n +MIME-Version: 1.0\n +Content-Type: text/plain; charset=UTF-8\n +Content-Transfer-Encoding: 8bit\n +Plural-Forms: nplurals=2; plural=n != 1;\n +X-Generator: Lokalize 1.4\n + +#: ../src/daemon.c:188 +msgid Exceeded maximum number of notifications +msgstr सूचनांची कमाल संख्या वाढवले + +#: ../src/daemon.c:251 +msgid Invalid notification identifier +msgstr अवैध सूचना ओळखकर्ता + +#: ../src/nd-queue.c:472 +msgid Clear all notifications +msgstr सर्व सूचना नष्ट करा + +#: ../src/nd-queue.c:883 +msgid Notifications +msgstr सूचना + +#: ../src/sound.c:35 +msgid Notification +msgstr सूचना + +#: ../data/notification-daemon.desktop.in.in.h:1 +msgid Notification Daemon +msgstr सूचना डिमन + +#: ../data/notification-daemon.desktop.in.in.h:2 +msgid Display notifications +msgstr डिस्पले सूचना + diff --git a/src/nd-queue.c b/src/nd-queue.c index 3675fca..de73940 100644 --- a/src/nd-queue.c +++ b/src/nd-queue.c @@ -507,7 +507,7 @@ destroy_screens (NdQueue *queue) gdkwindow = gdk_screen_get_root_window (screen); gdk_window_remove_filter (gdkwindow, (GdkFilterFunc) screen_xevent_filter, queue-priv-screens[i]); -for (j
Bug#687587: marked as done (unblock: mozc/1.5.1090.102-3)
Your message dated Sun, 07 Oct 2012 15:29:01 +0200
with message-id 5071839d.1040...@dogguy.org
and subject line Re: Bug#687587: unblock: mozc/1.5.1090.102-3
has caused the Debian Bug report #687587,
regarding unblock: mozc/1.5.1090.102-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.)
--
687587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687587
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
Dear release team,
Please unblock mozc/1.5.1090.102-3.
This version enabled hardening.
And when hardening was enabled, the link error of the library occurred.
This version also fixed this problem.
mozc (1.5.1090.102-3) unstable; urgency=low
.
* Update debian/rules.
- Enable hardening.
* Fix linking library of scim.
Add patches/scim-libs.patch.
unblock mozc/1.5.1090.102-3
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
mozc-1.5.1090.102-3.debdiff
Description: Binary data
---End Message---
---BeginMessage---
On 14/09/2012 02:39, Nobuhiro Iwamatsu wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Please unblock mozc/1.5.1090.102-3.
Unblocked.
Regards,
--
Mehdi Dogguy مهدي الدڤي---End Message---
Bug#687616: unblock php-apc/3.1.13-1
On 14/09/2012 11:52, Lior Kaplan wrote: Package: release.debian.org http://release.debian.org/ Severity: normal User: release.debian@packages.debian.org mailto:release.debian@packages.debian.org Usertags: unblock Please unblock package php-apc The current verson of php-apc in testing (3.1.10-1) was a major release (although that doesn't appear in the version itself) to support PHP 5.4. This current version in unstable (3.1.13-1) is a minor release for bug fixes, which I think we'll benefit from in the long run for Debian stable. I couldn't judge by looking at the diff because the top-directory in the sources is versioned :/ Could you please provide a sensible diff between the two version (patches applied)? Regards, -- Mehdi Dogguy مهدي الدڤي -- 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/50718502.8000...@dogguy.org
Processed: retitle 689765 to [pre-approval request] unblock: libio-socket-ssl-perl/1.76-2
Processing commands for cont...@bugs.debian.org: retitle 689765 [pre-approval request] unblock: libio-socket-ssl-perl/1.76-2 Bug #689765 [release.debian.org] unblock: libio-socket-ssl-perl/1.76-2 Changed Bug title to '[pre-approval request] unblock: libio-socket-ssl-perl/1.76-2' from 'unblock: libio-socket-ssl-perl/1.76-2' thanks Stopping processing here. Please contact me if you need assistance. -- 689765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689765 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.134961964929785.transcr...@bugs.debian.org
Bug#687616: unblock php-apc/3.1.13-1
On Sun, Oct 7, 2012 at 3:34 PM, Mehdi Dogguy me...@dogguy.org wrote: I couldn't judge by looking at the diff because the top-directory in the sources is versioned :/ Could you please provide a sensible diff between the two version (patches applied)? I haven't applied any patches of my own, just took upstream maintenance releases. Regarding the Debian package, only the changelog was chnaged: $ debdiff php-apc_3.1.10-1.dsc php-apc_3.1.13-1.dsc | grep +++ | grep debian +++ php-apc-3.1.13/debian/changelog2012-09-04 20:01:26.0 +0300 Regarding upstream, see the attached diff between 3.1.10 to 3.1.13. Kaplan apc_3.1.10_to_3.1.13.diff.gz Description: GNU Zip compressed data
Processed (with 1 errors): Re: Bug#683004: FTBFS on kfreebsd-*: Internal error: abort in get_output_file_with_visibility
Processing commands for cont...@bugs.debian.org:
unarchive 637809
Bug #637809 {Done: Julien Cristau jcris...@debian.org} [release.debian.org]
transition: perl 5.14
Unarchived Bug 637809
unblock 637809 by 637236
Bug #637809 {Done: Julien Cristau jcris...@debian.org} [release.debian.org]
transition: perl 5.14
637809 was blocked by: 628499 628500 628501 628503 628505 628507 629255 634141
634531 636132 636651 636656 636762 637602 638367 638894 639677 640346 640347
642146 643038 646286 646295 646297 646299 647120 648839 648842 648858 648954
649006 649055 649058 649059 649060 649061 649062 649063 649117 649180 649302
649306 649307 652638
637809 was not blocking any bugs.
Removed blocking bug(s) of 637809: 637236 and 649307
merge 683004 637236
Bug #683004 [src:gcc-4.6] FTBFS on kfreebsd-*: Internal error: abort in
get_output_file_with_visibility
Unable to merge bugs because:
affects of #637236 is 'src:gnat-4.6,gnat-4.6,src:gcc-mingw-w64,gcc-mingw-w64'
not 'src:gnat-4.6,gnat-4.6,gcc-mingw-w64,src:gcc-mingw-w64'
affects of #649307 is 'src:gnat-4.6,gnat-4.6,src:gcc-mingw-w64,gcc-mingw-w64'
not 'src:gnat-4.6,gnat-4.6,gcc-mingw-w64,src:gcc-mingw-w64'
Failed to merge 683004: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x18860a0)',
'requester', 'Steven Chamberlain ste...@pyro.eu.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '50719027.4010...@pyro.eu.org',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 536
Debbugs::Control::Service::control_line('line', 'merge 683004 637236',
'clonebugs', 'HASH(0x17fa3f8)', 'limit', 'HASH(0x17f98d8)',
'common_control_options', 'ARRAY(0x17f9920)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
637236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637236
637809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637809
649307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649307
683004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683004
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.134961976030884.transcr...@bugs.debian.org
Bug#685905: unblock: cmake/2.8.9-1
Quoting Modestas Vainius (mo...@debian.org): Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello, I would like to ask for unblock of 2.8.9-1 for wheezy. Wheezy currently has 2.8.9~rc1 which is a feature complete release candidate of 2.8.9. So far, about 6 weeks later, nothing happened. And, as it has been stressed out later by Nicholas Breen, this version fixes a regression that affect other packages (such as gromacs). So, well: - either the release team has no time to review the whole diff and therefore will not unblock this package - either they don't accept it - either they accept it latebut that requires a very big investment from them In all 3 cases, I think that uploading a package with a fix for #681428 *only* would not hurt.and would anyway fix the induced bugs such as #680825 Could it be considered? I think that relying everything on an unblock for cmake 2.8.9-1 is too optimistic. I understand you may have gazillion of arguments to avoid providing an RC release in wheezybut, that had to happen before the freeze if you wanted to be sure it happens (yeah, I know, maybe upstream released after the freeze, dunnoIn Such case, this is just bad luck) PS: I know nothing about all this stuff. I went on this while randomly going through RC bugs. signature.asc Description: Digital signature
Re: Bug#675971: patches for fixing RC bug, intent to upload NMU
On Thu, 04 Oct 2012 21:33:07 -0400, Chris Knadle wrote: CCing the tech-ctte and release-team, as the intent is to coordinate with both for approval to upload this NMU. [..] I contacted Gregor Hermann and with his help we created a minimal diff for a new upload targeted for Wheezy, as requested in TC #682010. I'm posting it here to give you a chance to review it if you wish. Unless you wish to discuss it, this will be uploaded soon to a DELAYED/XX queue at which time there will be an additional notification posted here. Three patches attached: mumble-celt.diff-- the fix for #675971 I'm willing to upload Chris' patch as an NMU in case Ron and Thorvald don't get around to doing a maintainer upload. Still, I'd appreciate a quick look by a CTTE member to check if this implements their decision correctly, and especially a pre-approval of the RT, since this is targetted at wheezy (please note that the versions in wheezy and sid are already different, and this patch applies on top of the version in sid). -- Thanks in advance! Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Carole King: Eventually signature.asc Description: Digital signature
Bug#689890: unblock: emdebian-crush/2.2.19
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package emdebian-crush
This fixes RC bug 688912. There are po and POT line
number changes but the debdiff comparede to testing
is the same as the one attached to the bug report.
unblock emdebian-crush/2.2.19
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armel
i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Index: debian/changelog
===
--- debian/changelog (working copy)
+++ debian/changelog (working copy)
@@ -1,3 +1,13 @@
+emdebian-crush (2.2.19) unstable; urgency=low
+
+ * Check for MultiArch support in dpkg and force the multiarch
+support in dpkg-cross if the requested architecture is in the
+list of dpkg foreign architectures. (Closes: #688912)
+ * Limit installation to only packages successfully converted using
+dpkg-cross.
+
+ -- Neil Williams codeh...@debian.org Wed, 26 Sep 2012 22:16:57 +0100
+
emdebian-crush (2.2.18) unstable; urgency=low
* Implement the new lintian profile support
Index: xapt/xapt
===
--- xapt/xapt (working copy)
+++ xapt/xapt (working copy)
@@ -203,6 +203,27 @@
$config_str .= -o Dir::State::Status=${dpkgdir}status;
$config_str .= -o Dir::Cache=${dir};
+# use dpkg --print-foreign-architectures dpkg = 1.16.2
+my $cmd = 'dpkg-query -W -f \'${Version}\' dpkg';
+$installed = `$cmd 2/dev/null`;
+my $res = system (dpkg --compare-versions $installed '=' 1.16.2);
+$res = 8;
+if (($res == 0) and (not defined $multiarch)) {
+ $res = system(dpkg --print-foreign-architectures | grep $arch /dev/null);
+ $res = 8;
+ if ($res == 0) {
+ $cmd = 'dpkg-query -W -f \'${Version}\' dpkg-cross';
+ $installed = `$cmd 2/dev/null`;
+ $res = system (dpkg --compare-versions $installed '=' $minver);
+ $res = 8;
+ if ($res != 0) {
+ die (Unsupported combination of old dpkg-cross and new dpkg!\n);
+ }
+ $multiarch++;
+ warn (Warning: Multi-Arch support has been enabled.\n);
+ }
+}
+
print apt-get $config_str update\n;
system (apt-get $config_str update 2/dev/null);
my $str = join ( , @files);
@@ -256,7 +277,7 @@
@list = grep(/\.deb$/, readdir DEBS);
closedir (DEBS);
}
-system (dpkg -i ${dir}output/*.deb)
+system (dpkg -i ${dir}output/*${arch}-cross*.deb)
if ((scalar @list 0) and (not defined $build) and ($host ne $arch));
system (rm -rf ${dir}*) if (not defined $preserve);
Bug#689814: unblock: gnuradio/3.6.1-1
Mehdi Dogguy me...@dogguy.org writes: It is a pity that the package didn't migrate due to a transient build failure, but it is not an argument to unblock it. Besides, the diff between testing's and sid's gnuradio looks rather large
Bug#689814: unblock: gnuradio/3.6.1-1
Mehdi Dogguy me...@dogguy.org writes: It is a pity that the package didn't migrate due to a transient build failure, but it is not an argument to unblock it. Besides, the diff between testing's and sid's gnuradio looks rather large and sid's version doesn't (according to the BTS) fix any serious issues. The gnuradio community has been trained to avoid Debian packages, so they are not using them or posting bugs to the BTS. That said, I am trying to change that. Do you have in mind some very important fixes that you'd like to see in Wheezy? If not, we'd prefer to keep 3.6.1-1 out of Wheezy. Upstream changelogs: http://gnuradio.org/redmine/projects/gnuradio/wiki/ChangeLogV3_6_1 http://gnuradio.org/redmine/projects/gnuradio/wiki/ChangeLogV3_6_0 --- The one that will lead to the most user comments if Debian doesn't have it: Allow left click in FFT display to set a GRC variable While it's a fairly minor feature, it allows click to tune to work. For software defined radio applications this is a compelling human-machine interface feature. The FFT display shows a band of radio frequencies, and the user just clicks on an interesting peak in the visualization of the FFT display and the radio receiving parts of the application tune to demodulate it - which often leads to hearing a human voice. See - Click - Listen. Also avoids having less-intuitive coarse frquency tuning slider bars in the GUI. --- The polyphase filterbank support is quite likely to be useful, http://www.trondeau.com/blog/2012/2/24/some-really-cool-dsp.html and the gr-digital and gr-filter blocks are an important addition. To be sure, gnuradio developers will charge ahead with new ABIs and APIs, and I intend to package up newer versions for wheezey-backports in the future. But the person who discovers gnuradio by finding it in Wheezy will be better served by starting to work with the 3.6.1 version rather than the 3.5.3.2 version. I've been using Wheezy and gnuradio 3.6 to follow along the fun people were having with the DVB-T dongles: http://sdr.osmocom.org/trac/wiki/rtl-sdr Since I didn't have to wait for 3.6.1 on my Wheezy boxes, I've been using it - and my Debian packages have worked well with scripts and extensions written by others. --- Upstream gnuradio developers would like to see gnuradio 3.6.1 in Wheezy. At the end of September I attended the conference http://www.trondeau.com/gnu-radio-conference-2012/ The increased use of VOLK makes gnuradio 3.6.1 run faster. Even with the perspective of a few months of time passing, the gnuradio 3.6.1-1 package uploaded in June still looks like a good candidate for inclusion in Wheezy. -Maitland -- 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/20593.41728.725253.397...@airborne.nrl.navy.mil
Bug#687616: unblock php-apc/3.1.13-1
On 07/10/2012 16:25, Lior Kaplan wrote: On Sun, Oct 7, 2012 at 3:34 PM, Mehdi Dogguy me...@dogguy.org mailto:me...@dogguy.org wrote: I couldn't judge by looking at the diff because the top-directory in the sources is versioned :/ Could you please provide a sensible diff between the two version (patches applied)? I haven't applied any patches of my own, just took upstream maintenance releases. Regarding the Debian package, only the changelog was chnaged: $ debdiff php-apc_3.1.10-1.dsc php-apc_3.1.13-1.dsc | grep +++ | grep debian +++ php-apc-3.1.13/debian/changelog2012-09-04 20:01:26.0 +0300 Regarding upstream, see the attached diff between 3.1.10 to 3.1.13. Thanks. Looking at the provided diff, I've found for example: +#ifdef ZEND_ENGINE_2_4 +case IS_CALLABLE: +/* XXX implement this */ +assert(0); +break; +#endif I'd rather avoid it. Moreover, most changes are put under an #ifdef ZEND_ENGINE_2_4 while php5-dev (afaics) defines ZEND_ENGINE_2. So, as far as I can tell, this release won't add much for Debian. (Please tell me if I got something wrong). Based on that, I'd prefer to keep current wheezy's version unchanged. Instead of accepting php-apc/3.1.13-1, did you want to include targeted fixes in Wheezy? If not, I think I'd close this bugreport. Regards and thanks for your work! -- Mehdi Dogguy مهدي الدڤي -- 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/5071a357.8050...@dogguy.org
Bug#689814: unblock: gnuradio/3.6.1-1
On 07/10/2012 17:27, A. Maitland Bottoms wrote: Mehdi Dogguy me...@dogguy.org writes: It is a pity that the package didn't migrate due to a transient build failure, but it is not an argument to unblock it. Besides, the diff between testing's and sid's gnuradio looks rather large$,1s� and sid's version doesn't (according to the BTS) fix any serious issues. The gnuradio community has been trained to avoid Debian packages, so they are not using them or posting bugs to the BTS. That said, I am trying to change that. Do you have in mind some very important fixes that you'd like to see in Wheezy? If not, we'd prefer to keep 3.6.1-1 out of Wheezy. Upstream changelogs: http://gnuradio.org/redmine/projects/gnuradio/wiki/ChangeLogV3_6_1 http://gnuradio.org/redmine/projects/gnuradio/wiki/ChangeLogV3_6_0 Sorry if this wasn't clear but I meant targeted patches. In order to evaluate the request, we'd like to see concrete minimal patches to fix issues (and an explanation about its importance). At this point of the freeze, we are not going to accept 3.6.1, sorry. Regards, -- Mehdi Dogguy مهدي الدڤي -- 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/5071a4b0.2040...@dogguy.org
Bug#689911: unblock: libxml2/2.8.0+dfsg1-6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libxml2/2.8.0+dfsg1-6
This version fixes RC bug #676210 by cherry picking an upstream post
release commit.
diff -Nru libxml2-2.8.0+dfsg1/debian/changelog
libxml2-2.8.0+dfsg1/debian/changelog
--- libxml2-2.8.0+dfsg1/debian/changelog2012-07-22 20:48:05.0
+0800
+++ libxml2-2.8.0+dfsg1/debian/changelog2012-10-07 14:20:32.0
+0800
@@ -1,3 +1,14 @@
+libxml2 (2.8.0+dfsg1-6) unstable; urgency=low
+
+ [ Daniel Veillard ]
+ * Fix a failure to report xmlreader parsing failures
+ Closes: #676210.
+
+ [ Aron Xu ]
+ * Add gbp.conf for wheezy branch.
+
+ -- Aron Xu a...@debian.org Sun, 07 Oct 2012 14:18:59 +0800
+
libxml2 (2.8.0+dfsg1-5) unstable; urgency=low
[ Daniel Veillard ]
diff -Nru libxml2-2.8.0+dfsg1/debian/gbp.conf
libxml2-2.8.0+dfsg1/debian/gbp.conf
--- libxml2-2.8.0+dfsg1/debian/gbp.conf 1970-01-01 08:00:00.0 +0800
+++ libxml2-2.8.0+dfsg1/debian/gbp.conf 2012-10-07 14:17:51.0 +0800
@@ -0,0 +1,4 @@
+[DEFAULT]
+upstream-branch = upstream
+debian-branch = wheezy
+upstream-tag = %(version)s
diff -Nru
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
---
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
1970-01-01
08:00:00.0 +0800
+++
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
2012-10-07
14:16:14.0 +0800
@@ -0,0 +1,29 @@
+From: Daniel Veillard veill...@redhat.com
+Date: Wed, 18 Jul 2012 17:39:56 +0800
+Subject: Fix a failure to report xmlreader parsing failures
+
+Related to https://bugzilla.gnome.org/show_bug.cgi?id=654567
+the problem is that the provided patch failed to raise an error
+on xmlTextReaderRead() return when an actual parsing error occured
+---
+ xmlreader.c |5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/xmlreader.c b/xmlreader.c
+index 77ac71b..10417ee 100644
+--- a/xmlreader.c
b/xmlreader.c
+@@ -907,8 +907,11 @@ xmlTextReaderPushData(xmlTextReaderPtr reader) {
+ }
+ }
+ reader-state = oldstate;
+-if (reader-ctxt-wellFormed == 0)
++if (reader-ctxt-wellFormed == 0) {
+ reader-mode = XML_TEXTREADER_MODE_EOF;
++return(-1);
++}
++
+ return(0);
+ }
+
+--
diff -Nru libxml2-2.8.0+dfsg1/debian/patches/series
libxml2-2.8.0+dfsg1/debian/patches/series
--- libxml2-2.8.0+dfsg1/debian/patches/series 2012-07-22
20:48:05.0 +0800
+++ libxml2-2.8.0+dfsg1/debian/patches/series 2012-10-07
14:16:14.0 +0800
@@ -2,3 +2,4 @@
0002-modify-xml2-config-and-pkgconfig-behaviour.patch
0003-Fix-parser-local-buffers-size-problems.patch
0004-Fix-entities-local-buffers-size-problems.patch
+0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
--
Regards,
Aron Xu
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMr=8w41ARpKaGJuq_a3=1dvnvb7mjudqtbcahzy9in0nb8...@mail.gmail.com
Bug#689911: marked as done (unblock: libxml2/2.8.0+dfsg1-6)
Your message dated Sun, 07 Oct 2012 18:21:43 +0200
with message-id 5071ac17.3070...@dogguy.org
and subject line Re: Bug#689911: unblock: libxml2/2.8.0+dfsg1-6
has caused the Debian Bug report #689911,
regarding unblock: libxml2/2.8.0+dfsg1-6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
689911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689911
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 libxml2/2.8.0+dfsg1-6
This version fixes RC bug #676210 by cherry picking an upstream post
release commit.
diff -Nru libxml2-2.8.0+dfsg1/debian/changelog
libxml2-2.8.0+dfsg1/debian/changelog
--- libxml2-2.8.0+dfsg1/debian/changelog2012-07-22 20:48:05.0
+0800
+++ libxml2-2.8.0+dfsg1/debian/changelog2012-10-07 14:20:32.0
+0800
@@ -1,3 +1,14 @@
+libxml2 (2.8.0+dfsg1-6) unstable; urgency=low
+
+ [ Daniel Veillard ]
+ * Fix a failure to report xmlreader parsing failures
+ Closes: #676210.
+
+ [ Aron Xu ]
+ * Add gbp.conf for wheezy branch.
+
+ -- Aron Xu a...@debian.org Sun, 07 Oct 2012 14:18:59 +0800
+
libxml2 (2.8.0+dfsg1-5) unstable; urgency=low
[ Daniel Veillard ]
diff -Nru libxml2-2.8.0+dfsg1/debian/gbp.conf
libxml2-2.8.0+dfsg1/debian/gbp.conf
--- libxml2-2.8.0+dfsg1/debian/gbp.conf 1970-01-01 08:00:00.0 +0800
+++ libxml2-2.8.0+dfsg1/debian/gbp.conf 2012-10-07 14:17:51.0 +0800
@@ -0,0 +1,4 @@
+[DEFAULT]
+upstream-branch = upstream
+debian-branch = wheezy
+upstream-tag = %(version)s
diff -Nru
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
---
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
1970-01-01
08:00:00.0 +0800
+++
libxml2-2.8.0+dfsg1/debian/patches/0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
2012-10-07
14:16:14.0 +0800
@@ -0,0 +1,29 @@
+From: Daniel Veillard veill...@redhat.com
+Date: Wed, 18 Jul 2012 17:39:56 +0800
+Subject: Fix a failure to report xmlreader parsing failures
+
+Related to https://bugzilla.gnome.org/show_bug.cgi?id=654567
+the problem is that the provided patch failed to raise an error
+on xmlTextReaderRead() return when an actual parsing error occured
+---
+ xmlreader.c |5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/xmlreader.c b/xmlreader.c
+index 77ac71b..10417ee 100644
+--- a/xmlreader.c
b/xmlreader.c
+@@ -907,8 +907,11 @@ xmlTextReaderPushData(xmlTextReaderPtr reader) {
+ }
+ }
+ reader-state = oldstate;
+-if (reader-ctxt-wellFormed == 0)
++if (reader-ctxt-wellFormed == 0) {
+ reader-mode = XML_TEXTREADER_MODE_EOF;
++return(-1);
++}
++
+ return(0);
+ }
+
+--
diff -Nru libxml2-2.8.0+dfsg1/debian/patches/series
libxml2-2.8.0+dfsg1/debian/patches/series
--- libxml2-2.8.0+dfsg1/debian/patches/series 2012-07-22
20:48:05.0 +0800
+++ libxml2-2.8.0+dfsg1/debian/patches/series 2012-10-07
14:16:14.0 +0800
@@ -2,3 +2,4 @@
0002-modify-xml2-config-and-pkgconfig-behaviour.patch
0003-Fix-parser-local-buffers-size-problems.patch
0004-Fix-entities-local-buffers-size-problems.patch
+0005-Fix-a-failure-to-report-xmlreader-parsing-failures.patch
--
Regards,
Aron Xu
---End Message---
---BeginMessage---
On 07/10/2012 18:07, Aron Xu wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libxml2/2.8.0+dfsg1-6
This version fixes RC bug #676210 by cherry picking an upstream post
release commit.
Unblocked.
Thanks for your work!
--
Mehdi Dogguy مهدي الدڤي---End Message---
Bug#689890: marked as done (unblock: emdebian-crush/2.2.19)
Your message dated Sun, 07 Oct 2012 18:39:38 +0200
with message-id 5071b04a.7080...@dogguy.org
and subject line Re: Bug#689890: unblock: emdebian-crush/2.2.19
has caused the Debian Bug report #689890,
regarding unblock: emdebian-crush/2.2.19
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.)
--
689890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689890
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 emdebian-crush
This fixes RC bug 688912. There are po and POT line
number changes but the debdiff comparede to testing
is the same as the one attached to the bug report.
unblock emdebian-crush/2.2.19
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armel
i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Index: debian/changelog
===
--- debian/changelog (working copy)
+++ debian/changelog (working copy)
@@ -1,3 +1,13 @@
+emdebian-crush (2.2.19) unstable; urgency=low
+
+ * Check for MultiArch support in dpkg and force the multiarch
+support in dpkg-cross if the requested architecture is in the
+list of dpkg foreign architectures. (Closes: #688912)
+ * Limit installation to only packages successfully converted using
+dpkg-cross.
+
+ -- Neil Williams codeh...@debian.org Wed, 26 Sep 2012 22:16:57 +0100
+
emdebian-crush (2.2.18) unstable; urgency=low
* Implement the new lintian profile support
Index: xapt/xapt
===
--- xapt/xapt (working copy)
+++ xapt/xapt (working copy)
@@ -203,6 +203,27 @@
$config_str .= -o Dir::State::Status=${dpkgdir}status;
$config_str .= -o Dir::Cache=${dir};
+# use dpkg --print-foreign-architectures dpkg = 1.16.2
+my $cmd = 'dpkg-query -W -f \'${Version}\' dpkg';
+$installed = `$cmd 2/dev/null`;
+my $res = system (dpkg --compare-versions $installed '=' 1.16.2);
+$res = 8;
+if (($res == 0) and (not defined $multiarch)) {
+ $res = system(dpkg --print-foreign-architectures | grep $arch /dev/null);
+ $res = 8;
+ if ($res == 0) {
+ $cmd = 'dpkg-query -W -f \'${Version}\' dpkg-cross';
+ $installed = `$cmd 2/dev/null`;
+ $res = system (dpkg --compare-versions $installed '=' $minver);
+ $res = 8;
+ if ($res != 0) {
+ die (Unsupported combination of old dpkg-cross and new dpkg!\n);
+ }
+ $multiarch++;
+ warn (Warning: Multi-Arch support has been enabled.\n);
+ }
+}
+
print apt-get $config_str update\n;
system (apt-get $config_str update 2/dev/null);
my $str = join ( , @files);
@@ -256,7 +277,7 @@
@list = grep(/\.deb$/, readdir DEBS);
closedir (DEBS);
}
-system (dpkg -i ${dir}output/*.deb)
+system (dpkg -i ${dir}output/*${arch}-cross*.deb)
if ((scalar @list 0) and (not defined $build) and ($host ne $arch));
system (rm -rf ${dir}*) if (not defined $preserve);
---End Message---
---BeginMessage---
On 07/10/2012 17:03, Neil Williams wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package emdebian-crush
Unblocked.
Regards,
--
Mehdi Dogguy مهدي الدڤي---End Message---
Please unblock/unblock-udeb/urgent netcfg/1.98
Hi folks, we delayed d-i wheezy beta 3 because of that nasty netcfg bug, and we had some buildd fun on powerpc; builds are here now, so please review push it to wheezy ASAP. Once that's done (and dinstall has run, and mirror pulse has happened) I'll probably binNMU debian-installer so that it picks a fixed netcfg package. We only have this staged in the git repository, and I think it can wait… $ git diff 20120930.. --stat doc/i18n/languages.xml | 215 ++-- 1 file changed, 98 insertions(+), 117 deletions(-) There are many udebs waiting for an unblock, but since there were many :slN: (po sublevels) changes, I don't feel too comfy about unblocking those this late… Mraw, KiBi. signature.asc Description: Digital signature
Bug#686702: marked as done (unblock: gcc-4.6/4.6.3-9)
Your message dated Sun, 7 Oct 2012 19:07:39 +0200 with message-id 20121007170739.gi31...@radis.cristau.org and subject line Re: Bug#686702: unblock: gcc-4.6/4.6.3-9 has caused the Debian Bug report #686702, regarding unblock: gcc-4.6/4.6.3-9 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.) -- 686702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686702 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 this should go to wheezy, because - wrong code gen fixes - the ARM vector alignment fix - some fixes for cross builds please ignore the Linaro changes, these are not used for the Debian ARM builds. Matthias gcc-4.6 (4.6.3-9) unstable; urgency=medium * Update to SVN 20120820 (r190530) from the gcc-4_6-branch. - ARM: Set vector type alignment to 8 bytes. - Fix PR target/33135 (SH), PR rtl-optimization/53908 (wrong code), PR middle-end/53433, PR middle-end/38474, PR middle-end/53790, PR c++/52988 (wrong code), PR fortran/51758. [ Aurelien Jarno ] * Add patches/ada-ppc64.diff to fix GNAT build on ppc64. * powerpc64: fix non-multilib builds. [ Matthias Klose ] * Update the Linaro support to the 4.6-2012.08 release. * spu build: Move static libraries to version specific directories. Closes: #680022. [ Thibaut Girka ] * Fix cross compilers for 64bit architectures when using DEB_CROSS_NO_BIARCH. ---End Message--- ---BeginMessage--- On Sun, Oct 7, 2012 at 12:43:51 +0200, Matthias Klose wrote: disabled in -11 the libstdc++ testsuite for mips*, as already done in 4.7. the kfreebsd build failure is not reproducible on the porter box asdfasdf.debian.net, this pops up in various builds, same for the current gnat-4.6 upload. now building again manually, as already done with -9. -11 unblocked, armhf and mips* seem to still be building, we'll see what that says. Thanks. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Re: Please unblock/unblock-udeb/urgent netcfg/1.98
On 07/10/2012 18:58, Cyril Brulebois wrote: Hi folks, we delayed d-i wheezy beta 3 because of that nasty netcfg bug, and we had some buildd fun on powerpc; builds are here now, so please review push it to wheezy ASAP. Done. Cheers. -- Mehdi Dogguy مهدي الدڤي -- 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/5071bad5.1020...@dogguy.org
Bug#684117: unblock: fex/20120718-4
Hi Philipp, since F*EX is now re-added as non-free with Perl Artistic license I herewith renew my request to allow the fex package to proceed to testing and thus allowing users of squeeze an upgrade path. Cheers, Kilian signature.asc Description: Digital signature
Bug#684117: unblock: fex/20120718-4
Hi, On Sun, Oct 07, 2012 at 07:35:09PM +0200, Kilian Krause wrote: since F*EX is now re-added as non-free with Perl Artistic license I herewith renew my request to allow the fex package to proceed to testing and thus allowing users of squeeze an upgrade path. did you submit the filtered diff Adam requested? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#687616: unblock php-apc/3.1.13-1
On Sun, Oct 7, 2012 at 5:44 PM, Mehdi Dogguy me...@dogguy.org wrote: Looking at the provided diff, I've found for example: +#ifdef ZEND_ENGINE_2_4 +case IS_CALLABLE: +/* XXX implement this */ +assert(0); +break; +#endif I'd rather avoid it. I'm not a C programmer so I can't comment on that otherwise than this is also the default for the switch (looks a few line bellow that section in apc_compile.c). default: assert(0); So basically this only adds support for a new object type changed in PHP 5.4 (due to changes in Closures and addition of Traits, AFAIK). Moreover, most changes are put under an #ifdef ZEND_ENGINE_2_4 while php5-dev (afaics) defines ZEND_ENGINE_2. So, as far as I can tell, this release won't add much for Debian. (Please tell me if I got something wrong). Based on that, I'd prefer to keep current wheezy's version unchanged. Indeed PHP only defines ZEND_ENGINE_2, but apc defines ZEND_ENGINE_2_4 for anything which is PHP 5.4 by checking for ZEND_MODULE_API_NO (at apc_php.h): #if ZEND_MODULE_API_NO = 20100409 #define ZEND_ENGINE_2_4 #endif #if ZEND_MODULE_API_NO 20060613 #define ZEND_ENGINE_2_3 #endif PHP 5.3 has 20090626, PHP 5.4 has 20100525 PHP 5.3: http://git.php.net/?p=php-src.git;a=commitdiff;h=4b4283bdc0c578971f863a2a53b8a95c59cfc2d0 Two changes for 5.4 http://git.php.net/?p=php-src.git;a=commitdiff;h=7f18561bdce9ca7228c2ca7104b30371ca1575f5 http://git.php.net/?p=php-src.git;a=commitdiff;h=f7ce69585c0809a40ff79ebc2d429720aadd4534 Instead of accepting php-apc/3.1.13-1, did you want to include targeted fixes in Wheezy? If not, I think I'd close this bugreport. Nope, I want to include 3.1.13, as it offers better PHP 5.4 support. I don't want people to encounter all the memory leaks and crashes fixed since the initial PHP 5.4 support for APC ( = version 3.1.10). See http://pecl.php.net/package-changelog.php?package=APC Regards and thanks for your work! Gladly, thanks for reviewing this seriously. Kaplan
Bug#687779: unblock: ksh/93u+20120628-1
Mehdi Dogguy wrote: So intead of reverting a patch [1] and re-open a severity normal bug, you uploaded a new upstream release [2] ? I would have classified the original bug as grave too. The upstream release is a bug fix release: they didn't even change the version number hence the appended date. And it seemed to be the approach that would best limit the number of times I'd need to bother my sponsor. Oliver -- 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/23003.1349640...@thecus.kiddle.eu
Bug#683847: unblock: sgml-base/1.26+nmu4
On Wed, Oct 03, 2012 at 06:23:17PM +0200, Julien Cristau wrote: Can you provide a pointer to the dpkg pre-dependency discussion? To comply with the Debian policy I asked[33] about the pre-dependency on debian-devel@l.d.o and Ian Jackson suggested[38] that this should be fixed in dpkg instead. I therefore pulled[43] in debian-dpkg@l.d.o as the maintainer address for dpkg. I never saw an answer nor any follow up question from a dpkg maintainer. Given that dpkg is highly critical infrastructure and the freeze I concluded that the dpkg maintainers would not be able to implement the necessary changes in a timely manner. In addition a number of people on #-mentors suggested that a Pre-Dependency on dpkg shouldn't be too bad since dpkg should be upgraded early in any case. The desktop-base package was given as an example for adding that pre-dependency without discussion. Helmut [33] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678902#33 [38] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678902#38 [43] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678902#43 -- 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/20121007202053.ga4...@alf.mars
Re: Bug#689583: swi-prolog-nox depends on libncursesw5 on amd64, but not on proper -dev package
It seems I've sent this message to an incorrect address first time. Resending now. 4 жовтня 2012 о 20:55 +0200 Eugeniy Meshcheryakov написав(-ла): 4 жовтня 2012 о 09:39 +0100 Michael Tautschnig написав(-ла): Package: swi-prolog-nox Version: 5.10.4-3 Severity: serious Justification: breaks build of other packages swi-prolog-nox lists as dependencies: libncursesw5 (= 5.6+20070908) [amd64] libncurses5 (= 5.5-5~) [not amd64] libncurses5-dev This breaks any build using swipl-ld on *amd64* as libncursesw5.so will not be available. The problem is caused by swi-prolog autodetecting libraries and trying ncursesw first, and it was installed on my machine when I was building the package. The least intrusive solution IMHO would be to just Build-Conflict with libncursesw5-dev. Will release team accept unblock request for package with such change? Regards, Eugeniy Meshcheryakov signature.asc Description: Digital signature
Bug#687616: marked as done (unblock php-apc/3.1.13-1)
Your message dated Sun, 07 Oct 2012 23:04:28 +0200 with message-id 5071ee5c.1080...@dogguy.org and subject line Re: Bug#687616: unblock php-apc/3.1.13-1 has caused the Debian Bug report #687616, regarding unblock php-apc/3.1.13-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.) -- 687616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687616 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 php-apc The current verson of php-apc in testing (3.1.10-1) was a major release (although that doesn't appear in the version itself) to support PHP 5.4. This current version in unstable (3.1.13-1) is a minor release for bug fixes, which I think we'll benefit from in the long run for Debian stable. I've waited with this request until some reported bugs in Debian were fixed upstream (e.g. #685893), and now I think the package status is OK for migration to testing. See changelog at http://pecl.php.net/package-changelog.php?package=APC Thanks. unblock php-apc/3.1.13-1 ---End Message--- ---BeginMessage--- On 07/10/2012 21:02, Lior Kaplan wrote: Indeed PHP only defines ZEND_ENGINE_2, but apc defines ZEND_ENGINE_2_4 for anything which is PHP 5.4 by checking for ZEND_MODULE_API_NO (at apc_php.h). Right. I knew I got something wrong. Thanks for spotting it. Ok, based on the different fixes present in the diff, I've unblocked the package. Kind Regards, -- Mehdi Dogguy مهدي الدڤي---End Message---
Bug#689393: marked as done (unblock: libmtp/1.1.3-35-g0ece104-4)
Your message dated Sun, 07 Oct 2012 23:09:39 +0200
with message-id 5071ef93.2000...@dogguy.org
and subject line Re: Bug#689393: unblock: libmtp/1.1.3-35-g0ece104-4
has caused the Debian Bug report #689393,
regarding unblock: libmtp/1.1.3-35-g0ece104-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.)
--
689393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689393
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 libmtp 1.1.3-35-g0ece104-4, it contains a minimalistic
patch to fix #687004.
The debdiff is attached, thanks for considering.
unblock libmtp/1.1.3-35-g0ece104-4
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-updates
APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-31-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru libmtp-1.1.3-35-g0ece104/debian/changelog libmtp-1.1.3-35-g0ece104/debian/changelog
--- libmtp-1.1.3-35-g0ece104/debian/changelog 2012-08-29 23:33:30.0 +0100
+++ libmtp-1.1.3-35-g0ece104/debian/changelog 2012-09-30 17:33:20.0 +0100
@@ -1,3 +1,10 @@
+libmtp (1.1.3-35-g0ece104-4) unstable; urgency=low
+
+ * Blacklist Canon EOS 3D for now as it leads to a SIGSEGV in
+libc. (Closes: #687004)
+
+ -- Alessio Treglia ales...@debian.org Sun, 30 Sep 2012 17:32:59 +0100
+
libmtp (1.1.3-35-g0ece104-3) unstable; urgency=low
* Add Sony Tablet P1 support. (Closes: #683637)
diff -Nru libmtp-1.1.3-35-g0ece104/debian/patches/0002-udev_blacklist.patch libmtp-1.1.3-35-g0ece104/debian/patches/0002-udev_blacklist.patch
--- libmtp-1.1.3-35-g0ece104/debian/patches/0002-udev_blacklist.patch 1970-01-01 01:00:00.0 +0100
+++ libmtp-1.1.3-35-g0ece104/debian/patches/0002-udev_blacklist.patch 2012-09-10 15:28:44.0 +0100
@@ -0,0 +1,18 @@
+Description: Blacklist Canon EOS 3D for now, it leads to a SIGSEGV in libc.
+Author: Alessio Treglia ales...@debian.org
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687004
+---
+ util/mtp-hotplug.c |2 ++
+ 1 file changed, 2 insertions(+)
+
+--- libmtp.orig/util/mtp-hotplug.c
libmtp/util/mtp-hotplug.c
+@@ -148,6 +148,8 @@ int main (int argc, char **argv)
+ printf(ATTR{idVendor}==\0971\, GOTO=\libmtp_rules_end\\n);
+ printf(# Canon scanners that look like MTP devices (PID 0x22nn)\n);
+ printf(ATTR{idVendor}==\04a9\, ATTR{idProduct}==\22*\, GOTO=\libmtp_rules_end\\n);
++ printf(# Canon digital camera (EOS 3D) that looks like MTP device (PID 0x3113)\n);
++ printf(ATTR{idVendor}==\04a9\, ATTR{idProduct}==\3113\, GOTO=\libmtp_rules_end\\n);
+ printf(# Sensitive Atheros devices that look like MTP devices\n);
+ printf(ATTR{idVendor}==\0cf3\, GOTO=\libmtp_rules_end\\n);
+ printf(# Sensitive Atmel JTAG programmers\n);
diff -Nru libmtp-1.1.3-35-g0ece104/debian/patches/series libmtp-1.1.3-35-g0ece104/debian/patches/series
--- libmtp-1.1.3-35-g0ece104/debian/patches/series 2012-08-29 23:24:11.0 +0100
+++ libmtp-1.1.3-35-g0ece104/debian/patches/series 2012-09-10 15:19:22.0 +0100
@@ -1,2 +1,3 @@
0001-devicedb_updates.patch
+0002-udev_blacklist.patch
1002-udev_rules.patch
---End Message---
---BeginMessage---
On 02/10/2012 10:15, Alessio Treglia wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libmtp 1.1.3-35-g0ece104-4, it contains a minimalistic
patch to fix #687004.
The debdiff is attached, thanks for considering.
unblock libmtp/1.1.3-35-g0ece104-4
Unblocked.
Regards,
--
Mehdi Dogguy مهدي الدڤي---End Message---
Bug#689264: marked as done (unblock: refpolicy/2:2.20110726-11)
Your message dated Sun, 07 Oct 2012 23:14:11 +0200 with message-id 5071f0a3.7060...@dogguy.org and subject line Re: Bug#689264: unblock: refpolicy/2:2.20110726-11 has caused the Debian Bug report #689264, regarding unblock: refpolicy/2:2.20110726-11 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.) -- 689264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689264 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 Dear Release Team, Please unblock package refpolicy version 2:2.20110726-11, changes since version -9 (which is in testing atm) are: * Fix #683756 (selinux in permissive mode breaks gdm and X) The problem arouse due to debian specific gdm3 locations. In version 2:2.20110726-10 a patch to fix this was introduced, but it was incomplete (fixed only some contexts, not all) and therefore in version -11 it was replaced by a correct patch, which is also already accepted upstream. The bug is only severity: normal in the BTS, but as installing and enabling selinux in permissive mode completely breaks the ability to log in via gdm I'd consider it important, at least. Regressions are very unlikely as this patch only touches file context definitions, no code. * Update the Vcs-* fields The Vcs-* fields in d/control were pointing to an old location, which doesn't work anymore. * Fix #686670 (Cannot load alsa.pp module) debian/patches/0048-Alsa-debian-locations.patch had been merged upstream but weren't dropped, leading to duplication and breaking the alsa module loading. Dropping the patch fixes this. * Drop debian/patches/0079-Allow-iptables_t-to-do-module_request.patch As in the previous fix, the code present in this one-line patch had already been introduced upstream. Dropping the patch removes duplicates and thereby avoids problems. * Fix watch file uversionmangle in debian/watch. Diffstat of the sources (patches applied) ignoring d/changelog: debian/control|4 ++-- debian/patches/series |3 +-- debian/watch |5 + policy/modules/admin/alsa.fc | 14 -- policy/modules/kernel/corecommands.fc |1 + policy/modules/services/xserver.fc| 20 +++- policy/modules/system/iptables.te |1 - 7 files changed, 20 insertions(+), 28 deletions(-) The debdiff is attached. unblock refpolicy/2.20110726-11 Thanks for your work + cheers, Mika diff -Nru refpolicy-2.20110726/debian/changelog refpolicy-2.20110726/debian/changelog --- refpolicy-2.20110726/debian/changelog 2012-06-30 11:42:53.0 +0200 +++ refpolicy-2.20110726/debian/changelog 2012-09-30 22:47:31.0 +0200 @@ -1,3 +1,30 @@ +refpolicy (2:2.20110726-11) unstable; urgency=low + + * Team upload + [ Mika Pflüger ] + * Drop incomplete patch adding debian specific gdm3 locations and +cherry-pick Laurent's complete patch from upstream instead. Slightly +edit the patch to work around an issue in file context ordering. + + -- Laurent Bigonville bi...@debian.org Sun, 30 Sep 2012 22:43:12 +0200 + +refpolicy (2:2.20110726-10) unstable; urgency=low + + * Team upload. + [ Mika Pflüger ] + * xserver.fc: Add debian specific /usr/sbin/gdm3 as a location for gdm3. +Closes: #683756 + * debian/control: Update Vcs-* fields. + + [ Laurent Bigonville ] + * d/p/0079-Allow-iptables_t-to-do-module_request.patch: Dropped, the code +present in this patch was already present later in the code. + * d/p/0048-Alsa-debian-locations.patch: Dropped, changes merged upstream, +and was breaking module loading due to duplicate paths (Closes: #686670) + * debian/watch: Fix watch file uversionmangle + + -- Laurent Bigonville bi...@debian.org Fri, 07 Sep 2012 17:51:13 +0200 + refpolicy (2:2.20110726-9) unstable; urgency=high * Enable UBAC as roles aren't useful. I recommend using only roles user_r @@ -10,8 +37,8 @@ * Change readahead policy to support memlockd. * Allow devicekit_power_t, devicekit_disk_t, kerneloops_t, and policykit_t to send dbus messages to users. - * Grant systemd utilities access to selinuxfs so they can correctly label directories -Closes: #678392 + * Grant systemd utilities access to selinuxfs so they can correctly label +directories. Closes: #678392 * Assigned type consolekit_var_run_t to /var/run/console(/.*)? because it's created and managed by consolekit nowadays. * Created tunable
Bug#686503: marked as done (unblock: ruby-compass/0.12.2~dfsg-2)
Your message dated Sun, 07 Oct 2012 23:22:36 +0200 with message-id 5071f29c.9030...@dogguy.org and subject line Re: Bug#686503: unblock: ruby-compass/0.12.2~dfsg-2 has caused the Debian Bug report #686503, regarding unblock: ruby-compass/0.12.2~dfsg-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 686503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686503 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 ruby-compass The version just uploaded to unstable fixes RC bug #680846. A git diff between the version in testing and this version is attached. unblock ruby-compass/0.12.2~dfsg-2 -- 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=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Antonio Terceiro terce...@debian.org diff --git a/debian/changelog b/debian/changelog index d84552a..00c6921 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +ruby-compass (0.12.2~dfsg-2) unstable; urgency=low + + * Team upload. + * debian/require-rubygems.overrides: instruct dh_ruby to ignore what seems +to be justifiable Rubygems usage and don't break the build +(Closes: #680846) + + -- Antonio Terceiro terce...@debian.org Sun, 02 Sep 2012 10:13:52 -0300 + ruby-compass (0.12.2~dfsg-1) unstable; urgency=low * New upstream release. diff --git a/debian/require-rubygems.overrides b/debian/require-rubygems.overrides new file mode 100644 index 000..30f7178 --- /dev/null +++ b/debian/require-rubygems.overrides @@ -0,0 +1,4 @@ +--- +- debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/validator.rb +- debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/dependencies.rb +- debian/ruby-compass/usr/lib/ruby/vendor_ruby/compass/commands/extension_command.rb signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- On 02/09/2012 15:31, Antonio Terceiro wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ruby-compass The version just uploaded to unstable fixes RC bug #680846. A git diff between the version in testing and this version is attached. unblock ruby-compass/0.12.2~dfsg-2 This bug was left unanswered but the package (-2) was unblocked. Regards, -- Mehdi Dogguy مهدي الدڤي---End Message---
