Bug#747250: marked as done (nmu: ppl_1:1.1-2)
Your message dated Fri, 13 Jun 2014 10:54:25 +0200 with message-id 539abc41.7030...@debian.org and subject line Re: Bug#747250: nmu: ppl_1:1.1-2 has caused the Debian Bug report #747250, regarding nmu: ppl_1:1.1-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.) -- 747250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747250 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 Please rebuild ppl against new swi-prolog, it's needed beacuse of library soname change. nmu ppl_1:1.1-2 . ALL . -m rebuild against swi-prolog 6.6.5 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On 12/06/14 23:29, Євгеній Мещеряков wrote: 12 червня 2014 о 18:14 +0200 Julien Cristau написав(-ла): What library changed its SONAME? I suspect the issue is: That's right. libppl-swi/i386 unsatisfiable Depends: swi-prolog-nox ( 6.6.3.0~) libppl-swi/amd64 unsatisfiable Depends: swi-prolog-nox ( 6.6.3.0~) libppl-swi/armel unsatisfiable Depends: swi-prolog-nox ( 6.6.4.0~) libppl-swi/armhf unsatisfiable Depends: swi-prolog-nox ( 6.6.4.0~) libppl-swi/kfreebsd-amd64 unsatisfiable Depends: swi-prolog-nox ( 6.6.3.0~) libppl-swi/kfreebsd-i386 unsatisfiable Depends: swi-prolog-nox ( 6.6.3.0~) libppl-swi/mips unsatisfiable Depends: swi-prolog-nox ( 6.6.4.0~) libppl-swi/mipsel unsatisfiable Depends: swi-prolog-nox ( 6.6.4.0~) libppl-swi/powerpc unsatisfiable Depends: swi-prolog-nox ( 6.6.3.0~) libppl-swi/s390x unsatisfiable Depends: swi-prolog-nox ( 6.6.3.0~) And: Files in second .deb but not in first - -rw-r--r-- root/root /usr/lib/libswipl.so.6.6.6 lrwxrwxrwx root/root /usr/lib/libswipl.so - libswipl.so.6.6.6 Files in first .deb but not in second - -rw-r--r-- root/root /usr/lib/libswipl.so.6.6.5 lrwxrwxrwx root/root /usr/lib/libswipl.so - libswipl.so.6.6.5 Євгеній, libswipl should really be its own split out binary package. And change package names when its SONAME changes. I was thinking about it but, that library changes soname with every new upstream release. Additionaly I'll have to make the library package to depend on exact version of swi-prolog-nox package, because the library uses prolog parts. This will mean that different library packages will not be coinstallable. So I don't see that there will be any advantages from changing the package name for swi-prolog, unlike for normal libraries. The only difference is requiring new processing for every upstream release. And still asking for bin-NMUs after that. Alright, scheduled. Regards, Emilio---End Message---
Bug#750399: marked as done (nmu: pyzmq_14.3.0-1)
Your message dated Fri, 13 Jun 2014 11:32:27 +0200 with message-id 539ac52b.4010...@debian.org and subject line Re: Bug#750399: nmu: pyzmq_14.3.0-1 has caused the Debian Bug report #750399, regarding nmu: pyzmq_14.3.0-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.) -- 750399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750399 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 pyzmq_14.3.0-1 . ALL . -m rebuild against pypy 2.3+dfsg-3 pypy-zmq currently depends on pypy (2.3), hence is not installable in sid. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On 03/06/14 08:50, Ralf Treinen wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu pyzmq_14.3.0-1 . ALL . -m rebuild against pypy 2.3+dfsg-3 pypy-zmq currently depends on pypy (2.3), hence is not installable in sid. Package: pypy-zmq Version: 14.3.0-1+b1 Depends: gcc, libzmq3-dev, pypy (= 2.2), pypy ( 2.4), libc6 (= 2.14), libzmq3 (= 4.0.1+dfsg) Looks good to me now. It may not be fine on kfreebsd-* and mips* where it failed to build, but binnmus there won't help... you need to investigate and fix the issue. Regards, Emilio---End Message---
Bug#751477: wheezy-pu: package squid3/3.1.20-2.2+deb7u1 (NMU)
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-CC: Luigi Gangitano lu...@debian.org
Dear release team,
I intend to NMU squid3/3.1.20-2.2+deb7u1 to stable to fix #712754. The
bug is about squid3 occasionally dieing from an assertion failure. The
bug is hard to trigger and the only parameter that is known to have an
influence is load. After the main squid worker dies it is automatically
restarted by its supervisor process. Still this bug causes pages to be
truncated when squid crashes.
Please find the proposed .debdiff attached. I am running it on my
wheezy/amd64 server for testing and did not observe similar crashes or
regressions since switching to the patched package.
Can I go ahead an upload the fixed package?
Helmut
diff -Nru squid3-3.1.20/debian/changelog squid3-3.1.20/debian/changelog
--- squid3-3.1.20/debian/changelog 2013-02-23 15:07:26.0 +0100
+++ squid3-3.1.20/debian/changelog 2014-06-12 23:21:22.0 +0200
@@ -1,3 +1,11 @@
+squid3 (3.1.20-2.2+deb7u1) stable-proposed-updates; urgency=medium
+
+ * Non-maintainer upload.
+ * Add fix-712754-assertion-failure-commHandleRead.patch. Fix sporadic
+assertion failure under high load. (Closes: #712754)
+
+ -- Helmut Grohne hel...@subdivi.de Thu, 12 Jun 2014 23:02:19 +0200
+
squid3 (3.1.20-2.2) unstable; urgency=low
* Non-maintainer upload.
diff -Nru
squid3-3.1.20/debian/patches/fix-712754-assertion-failure-commHandleRead.patch
squid3-3.1.20/debian/patches/fix-712754-assertion-failure-commHandleRead.patch
---
squid3-3.1.20/debian/patches/fix-712754-assertion-failure-commHandleRead.patch
1970-01-01 01:00:00.0 +0100
+++
squid3-3.1.20/debian/patches/fix-712754-assertion-failure-commHandleRead.patch
2014-06-12 22:59:34.0 +0200
@@ -0,0 +1,36 @@
+Description: fix assertion failure in commHandleRead
+Origin: upstream, http://bugs.squid-cache.org/attachment.cgi?id=2276
+Bug: http://bugs.squid-cache.org/show_bug.cgi?id=3048
+Bug-Debian: http://bugs.debian.org/712754
+Author: Alex Rousskov
+Last-Update: 2014-06-12
+Applied-Upstream: yes
+
+Fix for comm.cc:322 commio_has_callback(fd, IOCB_READ, ccb) assertion
+may also be applicable to a similar IOCB_WITE assertion.
+
+When we start closing a descriptor, we call commio_finish_callback() to remove
+I/O callbacks. If this is not done from commHandleRead or commHandleWrite,
+then select(2) structures may still have our descriptor registration and will
+call Comm back to read or write before the descriptor is closed for good. This
+will trigger a commio_has_callback() assertion.
+
+=== modified file 'src/comm.cc'
+--- a/src/comm.cc 2010-05-06 05:01:14 +
b/src/comm.cc 2010-05-09 21:32:23 +
+@@ -1635,11 +1635,13 @@
+ commStopHalfClosedMonitor(fd);
+ commSetTimeout(fd, -1, NULL, NULL);
+
+-// notify read/write handlers
++// notify read/write handlers after canceling select reservations, if any
+ if (commio_has_callback(fd, IOCB_WRITE, COMMIO_FD_WRITECB(fd))) {
++commSetSelect(fd, COMM_SELECT_WRITE, NULL, NULL, 0);
+ commio_finish_callback(fd, COMMIO_FD_WRITECB(fd), COMM_ERR_CLOSING,
errno);
+ }
+ if (commio_has_callback(fd, IOCB_READ, COMMIO_FD_READCB(fd))) {
++commSetSelect(fd, COMM_SELECT_READ, NULL, NULL, 0);
+ commio_finish_callback(fd, COMMIO_FD_READCB(fd), COMM_ERR_CLOSING,
errno);
+ }
+
+
diff -Nru squid3-3.1.20/debian/patches/series
squid3-3.1.20/debian/patches/series
--- squid3-3.1.20/debian/patches/series 2013-02-23 15:07:26.0 +0100
+++ squid3-3.1.20/debian/patches/series 2014-06-12 22:56:57.0 +0200
@@ -4,3 +4,4 @@
20-ipv6-fix
30-CVE-2012-5643-CVE-2013-0189.patch
fix-701123-regression-in-cachemgr.patch
+fix-712754-assertion-failure-commHandleRead.patch
Bug#751477: wheezy-pu: package squid3/3.1.20-2.2+deb7u1 (NMU)
Hi, Thanks Helmut for taking care of this bug. Release Team, I support this upload from Helmut. Best regards, L Il giorno 13/giu/2014, alle ore 13:18, Helmut Grohne hel...@subdivi.de ha scritto: Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu X-Debbugs-CC: Luigi Gangitano lu...@debian.org Dear release team, I intend to NMU squid3/3.1.20-2.2+deb7u1 to stable to fix #712754. The bug is about squid3 occasionally dieing from an assertion failure. The bug is hard to trigger and the only parameter that is known to have an influence is load. After the main squid worker dies it is automatically restarted by its supervisor process. Still this bug causes pages to be truncated when squid crashes. Please find the proposed .debdiff attached. I am running it on my wheezy/amd64 server for testing and did not observe similar crashes or regressions since switching to the patched package. Can I go ahead an upload the fixed package? Helmut squid3_3.1.20-2.2+deb7u1.debdiff -- Luigi Gangitano -- lu...@debian.org -- gangit...@lugroma3.org GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5 0F6D 0284 F20C 2BA9 7CED -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/77cbecce-b7a2-42fa-b758-631ef4656...@debian.org
Processed: Re: Bug#746805: transition: gfortran module version changing from 10 to 12
Processing commands for cont...@bugs.debian.org: tags 746805 confirmed pending Bug #746805 [release.debian.org] transition: gfortran module version changing from 10 to 12 Added tag(s) confirmed and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 746805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746805 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: https://lists.debian.org/handler.s.c.140267189729414.transcr...@bugs.debian.org
Processed: Re: Bug#749276: wheezy-pu: package openchange/1:1.0-3
Processing control commands: tags -1 + moreinfo Bug #749276 [release.debian.org] wheezy-pu: package openchange/1:1.0-3 Added tag(s) moreinfo. -- 749276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749276 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: https://lists.debian.org/handler.s.b749276.140267184629223.transcr...@bugs.debian.org
Bug#749276: wheezy-pu: package openchange/1:1.0-3
Control: tags -1 + moreinfo
On Sun, 2014-05-25 at 22:27 +0200, Jelmer Vernooij wrote:
As discussed previously, I'd like to upload a change to the openchange
package in stable that removes the openchangeserver and openchangeproxy
binary packages.
These binary packages are no longer installable after the removal of the
'samba4' server binary package. (bug 744711)
Sorry for the delay in getting back to you on this.
The diff also removes a few of the library packages; I assume the
rationale is that they were only shipped to support
openchange{proxy,server}?
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1402671836.28245.20.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#751115: transition: wxsvg
Processing commands for cont...@bugs.debian.org: tags 751115 confirmed pending Bug #751115 [release.debian.org] transition: wxsvg Added tag(s) confirmed and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 751115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751115 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: https://lists.debian.org/handler.s.c.140267192529533.transcr...@bugs.debian.org
Bug#749276: wheezy-pu: package openchange/1:1.0-3
On Fri, Jun 13, 2014 at 04:03:56PM +0100, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
On Sun, 2014-05-25 at 22:27 +0200, Jelmer Vernooij wrote:
As discussed previously, I'd like to upload a change to the openchange
package in stable that removes the openchangeserver and openchangeproxy
binary packages.
These binary packages are no longer installable after the removal of the
'samba4' server binary package. (bug 744711)
Sorry for the delay in getting back to you on this.
The diff also removes a few of the library packages; I assume the
rationale is that they were only shipped to support
openchange{proxy,server}?
Yes, they are only used by the server packages and not useful without them.
Cheers,
Jelmer
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140613152221.ga5...@vernstok.nl
Bug#751420: pu: package intel-microcode/1.20140430.1
Control: tags -1 + confirmed On Thu, 2014-06-12 at 15:08 -0300, Henrique de Moraes Holschuh wrote: I'd like to update the intel-microcode package in stable non-free with the current version of the intel-microcode. There is no regression risk, as no microcodes were removed and all other changes are to documentation (changelogs). The new microcode has been in unstable since 2014-05-03, and in testing and wheezy-backports since 2014-05-14, without any bug reports. As usual, we don't know what fixes were made by Intel. The new release of the microcode updates two recent Intel server CPUs: Xeon E5-v2 and Xeon E7-v2. Please go ahead; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402673417.28245.21.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#749276: wheezy-pu: package openchange/1:1.0-3
Processing control commands: tags -1 + confirmed - moreinfo Bug #749276 [release.debian.org] wheezy-pu: package openchange/1:1.0-3 Added tag(s) confirmed. Bug #749276 [release.debian.org] wheezy-pu: package openchange/1:1.0-3 Removed tag(s) moreinfo. -- 749276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749276 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: https://lists.debian.org/handler.s.b749276.14026735398016.transcr...@bugs.debian.org
NEW changes in stable-new
Processing changes file: duo-unix_1.8.1-1~deb7u1_armhf.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wvua7-0007o9...@franck.debian.org
Bug#751525: transition: poppler 0.26
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: block -1 by 751432 Hi, I would like to ask a slot for a Poppler 0.26.x transition. Currently there is Poppler 0.26.1 in experimental already. This transition impacts the existing poppler libraries in the following ways: - libpoppler44 → libpoppler46 - libpoppler-glib8 -- BC with 0.24 (with few new symbols) - libpoppler-qt4-4 -- BC with 0.24 (with one new symbol) - libpoppler-qt5-1 -- BC with 0.24 (with one new symbol) Below it is a list of sources which are touched by the transition, and their situation, sorted by solutions: Sources that compile fine, and can be binNMU'ed: calligra cups-filters gambas3 gdal inkscape libreoffice pdf2djvu pdftoipe popplerkit.framework texlive-bin texworks (has a spurious dependency on libpoppler, handling it upstream and then to Debian) xpdf Sources that currently FTBFS: * gdcm Compatibility with Poppler 0.26.x fixed upstream, asked to backport the patches in #751432. Other cases: * derivations This source builds a libpoppler-based utility application which is only used during the build to generate other data, and no trace of that application are left in the resulting arch:all package. I grouped all the bugs mentioned above (even the solved ones) with the following usertag: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=p...@debian.org;tag=poppler-0.26 A ben tracker for poppler would have: title = poppler 0.26; is_affected = .build-depends ~ libpoppler-private-dev | .source ~ /texworks/; is_good = .depends ~ libpoppler46; is_bad = .depends ~ libpoppler44; Thanks, -- Pino -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140613184151.13530.70779.reportbug@drak
Processed: transition: poppler 0.26
Processing control commands: block -1 by 751432 Bug #751525 [release.debian.org] transition: poppler 0.26 751525 was not blocked by any bugs. 751525 was not blocking any bugs. Added blocking bug(s) of 751525: 751432 -- 751525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751525 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: https://lists.debian.org/handler.s.b.140268492315208.transcr...@bugs.debian.org
Bug#751527: wheezy-pu: package libdbi-perl/1.622-1+deb7u1
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
Hi Release Team
Cc'ing also Moritz Mühlenhoff and the debian-perl list.
libplrpc-perl was removed from the archive for unstable[1] as it uses
Storable in an unsafe way, leading to a remote code execution
vulnerability. The idea is to also drop libplrpc-perl from wheezy and
squeeze if possible.
As first step toward this goal I propose to drop the dependency from
libdbi-perl package. Note: There is no real code change in wheezy to
unstable in the corresponding module part, altough in the Debian
package itself libplrpc-perl moved from Depends to Suggests following
upstream recommentation (in version 1.627-1).
[1] https://bugs.debian.org/734789
https://bugs.debian.org/745477
For the debdiff: I removed the dependency (as done for unstable, added
a patch to add a Security notice in the Proxy modules, and also
removed installation of the dbiproxy script).
Does this look safe enough?
Regards,
Salvatore
diff -Nru libdbi-perl-1.622/debian/changelog libdbi-perl-1.622/debian/changelog
--- libdbi-perl-1.622/debian/changelog 2012-06-07 12:46:26.0 +0200
+++ libdbi-perl-1.622/debian/changelog 2014-06-13 18:24:52.0 +0200
@@ -1,3 +1,15 @@
+libdbi-perl (1.622-1+deb7u1) wheezy; urgency=low
+
+ * Team upload.
+ * Remove libplrpc-perl from Build-Depends and Depends (Closes: #745427)
+ * warn users of DBI::Proxy about its unsafe usage of Storable
+patch by Petr Písař from
+https://rt.cpan.org/Public/Bug/Display.html?id=90475
+ * Add dont-install-dbiproxy-script.patch patch.
+Don't install dbiproxy script into /usr/bin.
+
+ -- Salvatore Bonaccorso car...@debian.org Tue, 10 Jun 2014 09:05:28 +0200
+
libdbi-perl (1.622-1) unstable; urgency=low
* New upstream release
diff -Nru libdbi-perl-1.622/debian/control libdbi-perl-1.622/debian/control
--- libdbi-perl-1.622/debian/control 2012-06-07 12:46:26.0 +0200
+++ libdbi-perl-1.622/debian/control 2014-06-13 18:24:52.0 +0200
@@ -9,7 +9,6 @@
Nicholas Bamber nicho...@periapt.co.uk,
Alessandro Ghedini gh...@debian.org
Build-Depends: perl, debhelper (= 9),
- libplrpc-perl,
libtest-pod-coverage-perl,
libtest-pod-perl,
perl (= 5.10.1) | libtest-simple-perl (= 0.90)
@@ -20,7 +19,7 @@
Package: libdbi-perl
Architecture: any
-Depends: ${misc:Depends}, ${perl:Depends}, ${shlibs:Depends}, libplrpc-perl
+Depends: ${misc:Depends}, ${perl:Depends}, ${shlibs:Depends}
Provides: perl-dbdabi-${perl-dbdabi-version}
Breaks: libdbd-anydata-perl ( 0.09+),
libdbd-csv-perl ( 0.3000),
diff -Nru libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch
--- libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch 1970-01-01 01:00:00.0 +0100
+++ libdbi-perl-1.622/debian/patches/Security-notice-for-Proxy.patch 2014-06-13 18:24:52.0 +0200
@@ -0,0 +1,56 @@
+From cd8fcbbf402e1d70c9f325f8b0fcd99e02cf14be Mon Sep 17 00:00:00 2001
+From: Petr Písař ppi...@redhat.com
+Date: Mon, 18 Nov 2013 12:52:09 +0100
+Subject: [PATCH] Security notice for Proxy
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+Bug: https://rt.cpan.org/Public/Bug/Display.html?id=90475
+
+PlRPC is not secure due to Storable. Warn Proxy users about it.
+
+Signed-off-by: Petr Písař ppi...@redhat.com
+---
+ lib/DBD/Proxy.pm | 7 +++
+ lib/DBI/ProxyServer.pm | 7 +++
+ 2 files changed, 14 insertions(+)
+
+diff --git a/lib/DBD/Proxy.pm b/lib/DBD/Proxy.pm
+index 287b2dc..5948255 100644
+--- a/lib/DBD/Proxy.pm
b/lib/DBD/Proxy.pm
+@@ -974,6 +974,13 @@ The workaround is storing the modified local copy back to the server:
+ $dbh-{csv_tables} = $tables;
+
+
++=head1 SECURITY WARNING
++
++LRPC::PlClient used underneath is not secure due to serializing and
++deserializing data with LStorable module. Use the proxy driver only in
++trusted environment.
++
++
+ =head1 AUTHOR AND COPYRIGHT
+
+ This module is Copyright (c) 1997, 1998
+diff --git a/lib/DBI/ProxyServer.pm b/lib/DBI/ProxyServer.pm
+index 68ad4af..78a0d78 100644
+--- a/lib/DBI/ProxyServer.pm
b/lib/DBI/ProxyServer.pm
+@@ -867,6 +867,13 @@ Don't try to put parameters into the sql-query like this:
+ =back
+
+
++=head1 SECURITY WARNING
++
++LRPC::PlServer used underneath is not secure due to serializing and
++deserializing data with LStorable module. Use the proxy driver only in
++trusted environment.
++
++
+ =head1 AUTHOR
+
+ Copyright (c) 1997Jochen Wiedmann
+--
+1.8.3.1
+
diff -Nru libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch
--- libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch 1970-01-01 01:00:00.0 +0100
+++ libdbi-perl-1.622/debian/patches/dont-install-dbiproxy-script.patch 2014-06-13 18:24:52.0 +0200
@@ -0,0
NEW changes in stable-new
Processing changes file: clamav_0.98.1+dfsg-1+deb7u4_mips.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wvwjl-0003mk...@franck.debian.org
Bug#750575: Stuff still needing doing for python3.3 removal
Checking reverse dependencies... # Broken Depends: bpython: bpython3 cherrypy3: python3-cherrypy3 doit: python3-doit libpeas: libpeas-1.0-0 [hurd-i386] morse-simulator: python3-morse-simulator [kfreebsd-i386] pystache: python3-pystache python-json-patch: python3-jsonpatch retext: retext upstart: upstart-monitor uwsgi: uwsgi-plugin-python3 [sparc] zope.testrunner: python3-zope.testrunner # Broken Build-Depends: morse-simulator: python3.3-dev I'll investigate these later. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/21928962.PRuxiCe177@scott-latitude-e6320
Bug#750575: Stuff still needing doing for python3.3 removal
Not sure if the following is going to help but since I had some spare minutes… TL;DR: look at upstart and morse-simulator. Scott Kitterman deb...@kitterman.com (2014-06-13): Checking reverse dependencies... # Broken Depends: bpython: bpython3 arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4. cherrypy3: python3-cherrypy3 arch:all but a simple rebuild seems to make it switch from 3.3 to 3. doit: python3-doit arch:all but a simple rebuild seems to make it switch from 3.3 to 3. libpeas: libpeas-1.0-0 [hurd-i386] hurd, shrug. morse-simulator: python3-morse-simulator [kfreebsd-i386] build-attempted, 3 times. pystache: python3-pystache arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4. python-json-patch: python3-jsonpatch arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4. retext: retext arch:all but a simple rebuild seems to make it switch away from 3.3. upstart: upstart-monitor arch:all and a simple rebuild does NOT make it switch away from 3.3. I suspect this is due to the following line in debian/control: | X-Python3-Version: 3.3 uwsgi: uwsgi-plugin-python3 [sparc] sparc, shrug. zope.testrunner: python3-zope.testrunner arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4. # Broken Build-Depends: morse-simulator: python3.3-dev From the changelog, not sure what happened to your changes to switch away from 3.x specifics, maybe some mismerge at some point? Better talk to the maintainer directly I guess. Mraw, KiBi. signature.asc Description: Digital signature
Bug#751420: pu: package intel-microcode/1.20140430.1
On Fri, 13 Jun 2014, Adam D. Barratt wrote: Control: tags -1 + confirmed On Thu, 2014-06-12 at 15:08 -0300, Henrique de Moraes Holschuh wrote: I'd like to update the intel-microcode package in stable non-free with the current version of the intel-microcode. There is no regression risk, as no microcodes were removed and all other changes are to documentation (changelogs). The new microcode has been in unstable since 2014-05-03, and in testing and wheezy-backports since 2014-05-14, without any bug reports. As usual, we don't know what fixes were made by Intel. The new release of the microcode updates two recent Intel server CPUs: Xeon E5-v2 and Xeon E7-v2. Please go ahead; thanks. Thank you! I've just uploaded the package. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140613232829.ga16...@khazad-dum.debian.net
Bug#750575: Stuff still needing doing for python3.3 removal
On 14/06/14 01:24, Cyril Brulebois wrote: morse-simulator: python3-morse-simulator [kfreebsd-i386] build-attempted, 3 times. This was because of the /dev/shm issue on kbsd, leading to no multiprocessing module in python3.4. That's fixed, and I just gave back morse-simulator. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539b9c6f.8070...@debian.org
Bug#750026: marked as done (transition: qtbase-opensource-src)
Your message dated Sat, 14 Jun 2014 02:50:15 +0200 with message-id 539b9c47.4070...@debian.org and subject line Re: Bug#750026: transition: qtbase-opensource-src has caused the Debian Bug report #750026, regarding transition: qtbase-opensource-src 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.) -- 750026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750026 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: transition Hi Release Team! We are ready to go with the private stuff transition for Qt 5.3.0. The external (non Qt-stack) packages related are: fcitx-qt5 gammaray pyqt5 qtcreator (this last might get a sourcefull upload, I'm working on it). Packages are already being built in experimental. Thanks in advance, Lisandro. Ben file: title = Qt 5.3.0 private symbols transition; is_affected = .depends ~/qtbase-abi-5-2-1/ | .depends ~/qtdeclarative-abi-5-2-1/ | .depends ~/qtbase-abi-5-3-0/ | .depends ~/qtdeclarative-abi-5-3-0/; is_good = .depends ~/qtbase-abi-5-3-0/ | .depends ~/qtdeclarative-abi-5-3-0/; is_bad = .depends ~/qtbase-abi-5-2-1/ | .depends ~/qtdeclarative-abi-5-2-1/; -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On 04/06/14 18:51, Emilio Pozuelo Monfort wrote: Control: forwarded -1 https://release.debian.org/transitions/html/qtbase-abi-5-3-0.html Control: tags -1 confirmed On 31/05/14 22:20, Lisandro Damián Nicanor Pérez Meyer wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi Release Team! We are ready to go with the private stuff transition for Qt 5.3.0. Go ahead. And it is in! Regards, Emilio---End Message---
Bug#750575: Stuff still needing doing for python3.3 removal
Am 14.06.2014 02:50, schrieb Emilio Pozuelo Monfort: On 14/06/14 01:24, Cyril Brulebois wrote: morse-simulator: python3-morse-simulator [kfreebsd-i386] build-attempted, 3 times. This was because of the /dev/shm issue on kbsd, leading to no multiprocessing module in python3.4. That's fixed, and I just gave back morse-simulator. will that help? or will that need a python3.4 binNMU on kfreebsd first? -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539b9e43.9050...@debian.org
Bug#750575: Stuff still needing doing for python3.3 removal
On 14/06/14 02:58, Matthias Klose wrote: Am 14.06.2014 02:50, schrieb Emilio Pozuelo Monfort: On 14/06/14 01:24, Cyril Brulebois wrote: morse-simulator: python3-morse-simulator [kfreebsd-i386] build-attempted, 3 times. This was because of the /dev/shm issue on kbsd, leading to no multiprocessing module in python3.4. That's fixed, and I just gave back morse-simulator. will that help? or will that need a python3.4 binNMU on kfreebsd first? The latter, but I already did that two or three hours ago. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539ba00a.3020...@debian.org
