Bug#837469: nmu: dose3_5.0.1-1
Hi, Quoting Emilio Pozuelo Monfort (2016-09-14 00:47:01) > On 11/09/16 22:04, Johannes Schauer wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: binnmu > > > > nmu dose3_5.0.1-1 . ANY . unstable . -m "rebuild for camlzip 1.06-1" > > Can you explain why this is needed? We don't like to blindly binNMU stuff, so > a little explanation is always helpful. When src:dose3 (= 5.0.1-1) was originally built, it was built with src:camlzip (= 1.05-3) in the archive. This means that src:dose3 built libdose3-ocaml with a dependency on the virtual package libzip-ocaml-8wtm6 on amd64 which was provided by libzip-ocaml (= 1.05-3). Building the new src:camlzip release 1.06-1, replaced that libzip-ocaml package by a new version which now provides libzip-ocaml-4m8e9 on amd64. As a result, no package provides libzip-ocaml-8wtm6 anymore and libdose3-ocaml ocaml become uninstallable. You can verify this situation here: https://packages.debian.org/sid/libdose3-ocaml (it says Package not available next to libzip-ocaml-8wtm6) and here: https://qa.debian.org/dose/debcheck/unstable_main/1473742805/packages/libdose3-ocaml.html The situation is analogous on all other architectures than amd64. The situation arises because OCaml packages are statically linked and rebuilding a library requires a rebuild of all its reverse dependencies. I was told in #debian-ocaml that usually Stéphane Glondu would schedule OCaml binNMUs but he hasn't been on IRC for 3 days, so Mehdi Dogguy advised me to ask the release team to schedule the required binNMU of src:dose3. One practical consequence of libdose3-ocaml not being installable right now is, that src:botch is currently bd-uninstallable: https://buildd.debian.org/status/package.php?p=botch Thank you! cheers, josch signature.asc Description: signature
Bug#837412: transition: liblouis
Hello, Emilio Pozuelo Monfort, on Wed 14 Sep 2016 00:42:45 +0200, wrote: > On 11/09/16 13:55, Samuel Thibault wrote: > > liblouis 3.0.0 bumped ABI and thus soname, there are only two packages > > that need a rebuild: liblouixml and liblouisutdml, > Go ahead. liblouis 3.0.0-3 is now in sid, binNMUs can be scheduled with --extra-depends "liblouis-dev (>= 3.0.0)" Thanks, Samuel
Bug#837728: RM: heimdal/1.7~git20150920+dfsg-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the heimdal source package from testing. As maintainers, we believe that Heimdal is not in a good enough state to be included in a stable release. There is still some activity in the upstream Git master branch. However: * The last regular release (1.5) was in 2011, last RC was in 2012 * No security releases since Jan 2012, despite various recent security releases for MIT Kerberos since and occasional security releases while Heimdal was active * There is no noticeable QA happening upstream. Tests fail on 32 bit, regressions have been introduced. * Nobody upstream is interested in release management; we have asked about this on the development list multiple times. I have filed bugs against the packages that depend on Heimdal to either switch to building against Heimdal OR MIT or to drop their Heimdal dependencies altogether. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#837529: marked as done (nmu: ocserv)
Your message dated Wed, 14 Sep 2016 00:46:06 +0200 with message-id <209cd2e4-37e4-8463-e9f0-2b21a6b2f...@debian.org> and subject line Re: Bug#837529: nmu: ocserv has caused the Debian Bug report #837529, regarding nmu: ocserv 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.) -- 837529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi, With radcli/1.2.6-3 upload, radcli ships the pkgconfig file, so that ocserv needs a rebuild to pick up proper radius support to close #820894. nmu ocserv_0.11.4-1 . ANY . unstable . -m "Rebuild with radcli_1.2.6-3" Regards, Aron --- End Message --- --- Begin Message --- On 12/09/16 10:37, Aron Xu wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi, > > With radcli/1.2.6-3 upload, radcli ships the pkgconfig file, so that > ocserv needs a rebuild to pick up proper radius support to close > #820894. > > nmu ocserv_0.11.4-1 . ANY . unstable . -m "Rebuild with radcli_1.2.6-3" Scheduled. Emilio--- End Message ---
Bug#837469: nmu: dose3_5.0.1-1
Hi, On 11/09/16 22:04, Johannes Schauer wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu dose3_5.0.1-1 . ANY . unstable . -m "rebuild for camlzip 1.06-1" Can you explain why this is needed? We don't like to blindly binNMU stuff, so a little explanation is always helpful. Cheers, Emilio
Bug#836952: marked as done (nmu: pymol_1.8.2.1+dfsg-1.2)
Your message dated Wed, 14 Sep 2016 00:44:29 +0200 with message-idand subject line Re: Bug#836952: nmu: pymol_1.8.2.1+dfsg-1.2 has caused the Debian Bug report #836952, regarding nmu: pymol_1.8.2.1+dfsg-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.) -- 836952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu pymol_1.8.2.1+dfsg-1.2 . amd64 . unstable . -m "Rebuild against libpng1.6" maintainer uploaded binaries were built against libpng12-0 Andreas --- End Message --- --- Begin Message --- On 07/09/16 16:04, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu pymol_1.8.2.1+dfsg-1.2 . amd64 . unstable . -m "Rebuild against libpng1.6" > > maintainer uploaded binaries were built against libpng12-0 Scheduled. Emilio--- End Message ---
Bug#836976: marked as done (nmu: tvc_5.0.3+dfsg-1)
Your message dated Wed, 14 Sep 2016 00:44:53 +0200 with message-idand subject line Re: Bug#836976: nmu: tvc_5.0.3+dfsg-1 has caused the Debian Bug report #836976, regarding nmu: tvc_5.0.3+dfsg-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 836976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu tvc_5.0.3+dfsg-1 . ANY . experimental . -m "Rebuild against libjsoncpp1" to finish the transition in experimental, too Andreas --- End Message --- --- Begin Message --- On 07/09/16 20:04, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu tvc_5.0.3+dfsg-1 . ANY . experimental . -m "Rebuild against libjsoncpp1" > > to finish the transition in experimental, too Scheduled. Emilio--- End Message ---
Bug#836977: marked as done (nmu: saods9_7.5~b4+repack-1)
Your message dated Wed, 14 Sep 2016 00:45:34 +0200 with message-idand subject line Re: Bug#836977: nmu: saods9_7.5~b4+repack-1 has caused the Debian Bug report #836977, regarding nmu: saods9_7.5~b4+repack-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.) -- 836977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu saods9_7.5~b4+repack-1 . ANY . experimental . -m "Rebuild against libwcstools1" to finish the transition in experimental, too Andreas --- End Message --- --- Begin Message --- On 07/09/16 20:06, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu saods9_7.5~b4+repack-1 . ANY . experimental . -m "Rebuild against > libwcstools1" > > to finish the transition in experimental, too Scheduled. Emilio--- End Message ---
Bug#836946: marked as done (nmu: python-cutadapt_1.11-1)
Your message dated Wed, 14 Sep 2016 00:44:04 +0200 with message-idand subject line Re: Bug#836946: nmu: python-cutadapt_1.11-1 has caused the Debian Bug report #836946, regarding nmu: python-cutadapt_1.11-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.) -- 836946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu python-cutadapt_1.11-1 . amd64 . unstable . -m "Rebuild against python 3.5" Maintainer uploaded package built on stable or outdated stretch/sid. Andreas --- End Message --- --- Begin Message --- On 07/09/16 15:32, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu python-cutadapt_1.11-1 . amd64 . unstable . -m "Rebuild against python > 3.5" > > Maintainer uploaded package built on stable or outdated stretch/sid. Scheduled. Emilio--- End Message ---
Bug#837199: transition: armadillo
On 13/09/16 20:12, Sebastiaan Couwenberg wrote: > On 09/13/2016 07:51 PM, Emilio Pozuelo Monfort wrote: >> On 10/09/16 11:35, Sebastiaan Couwenberg wrote: >>> On 09/10/2016 02:11 AM, Kumar Appaiah wrote: armadillo has already been uploaded to unstable. While the reverse dependencies should build with a binNMU, I have not tested them and will test it in the next couple of days. >>> >>> Because gdal needs to be rebuilt for the armadillo transition to unblock >>> the vtk6 rebuild for the openmpi transition, I've also done a round of >>> rebuilds to assess the impact. >>> >>> Fortunately the number of reverse dependencies for armadillo is limited, >>> and all packages rebuilt successfully: >>> >>> gdal (2.1.1+dfsg-4) OK >>> gnss-sdr (0.0.8-1) OK >>> mlpack (2.0.2-1) OK >>> seer (1.1.1-2) OK >>> >>> pktools (2.6.7-2) OK >>> >>> I'd like to have gdal (2.1.1+dfsg-4) migrate to testing to get the two >>> RC bugfixes into stretch, before binNMUs for the armadillo rdeps are >>> scheduled. >> >> I scheduled everything but gdal. Let's see if gdal migrates tonight once >> perl is >> old enough. > > Thanks for waiting with the gdal binNMU, I appreciate that a lot. > > I really hope having perl migrate will be sufficient, the gdal situation > in testing has caused several RC bugs and a thread on -devel :-( It just went in. I have now nmu'ed it for the armadillo transition. Cheers, Emilio
Bug#837412: transition: liblouis
Control: tags -1 confirmed On 11/09/16 13:55, Samuel Thibault wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hello, > > liblouis 3.0.0 bumped ABI and thus soname, there are only two packages > that need a rebuild: liblouixml and liblouisutdml, both of which rebuild > fine with liblouis 3.0.0. I have already uploaded it to experimental, > it builds fine on all archs (I just had to do it by hand on a porterbox > for mipsel, because the experimental apt resolver (apt-cudf) on the > mipsel buildds seems to be broken and aba didn't answer about it yet, it > will not be a problem in sid anyway) Go ahead. Cheers, Emilio
Processed: Re: Bug#837412: transition: liblouis
Processing control commands: > tags -1 confirmed Bug #837412 [release.debian.org] transition: liblouis Added tag(s) confirmed. -- 837412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836592: jessie-pu: package gdcm/2.4.4-3
On Sun, 2016-09-11 at 20:41 +0200, Julien Cristau wrote: > On Fri, Sep 9, 2016 at 17:33:08 +0100, Adam D. Barratt wrote: > > > On Fri, 2016-09-09 at 17:08 +0200, Gert Wollny wrote: [...] > > > At the beginning of the build log one can even see that the library is > > > correctly detected in the JRE ppc64el sub-directory, but later it wants > > > ppc64 only and I can't find the according code in the gdcm VTK java > > > module definition. > > > > I was wondering if this might be a similar issue to javatool's #833572 > > (now fixed in p-u), but I don't know either gdcm or Java packaging in > > general well enough to immediately point to a solution I'm afraid. > > > After apt-get build-dep gdcm: > > (jessie_ppc64el-dchroot)jcristau@plummer:~$ rgrep ppc64/libjawt /usr/lib/ > /usr/lib/vtk-5.8/VTKTargets-release.cmake: > IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE > "vtkGraphics;vtkFilteringJava;/usr/lib/jvm/default-java/jre/lib/ppc64/libjawt.so" > /usr/lib/vtk-5.8/VTKTargets-release.cmake: > IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE > "vtkRendering;vtkGraphicsJava;vtkImagingJava;/usr/lib/jvm/default-java/jre/lib/ppc64/libjawt.so" > /usr/lib/vtk-5.8/VTKTargets-release.cmake: > IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE > "vtkCharts;vtkViewsJava;/usr/lib/jvm/default-java/jre/lib/ppc64/libjawt.so" > /usr/lib/vtk-5.8/VTKConfig-Java.cmake:SET(VTK_JAVA_AWT_LIBRARY > "/usr/lib/jvm/default-java/jre/lib/ppc64/libjawt.so") A test build of vtk on a porter box results in the correct paths, so I've scheduled a binNMU. Then we can try rebuilding gdcm against that. Regards, Adam
Processed: block 830200 with 837719
Processing commands for cont...@bugs.debian.org: > # assuming ppc64el missing binaries currently block testing migration > block 830200 with 837719 Bug #830200 [release.debian.org] transition: perl 830200 was blocked by: 834795 825611 825609 836162 834796 836636 825014 825231 834799 834797 825524 825012 825762 834798 834800 830200 was not blocking any bugs. Added blocking bug(s) of 830200: 837719 > thanks Stopping processing here. Please contact me if you need assistance. -- 830200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836941: marked as done (nmu: shibboleth-sp2_2.6.0+dfsg1-3)
Your message dated Tue, 13 Sep 2016 20:07:09 +0200 with message-idand subject line Re: Bug#836941: Acknowledgement (nmu: shibboleth-sp2_2.6.0+dfsg1-3) has caused the Debian Bug report #836941, regarding nmu: shibboleth-sp2_2.6.0+dfsg1-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.) -- 836941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hello, A recenty reported bug in shibboleth-sp2 turned out to be two identical problems in the pkg-config files shipped by xmltooling and opensaml2. Since it breaks upgrades, I decided to fix this even though it delays the testing migration for transition #836370. xmltooling_1.6.0-3 and opensaml2_2.6.0-4 is already "Installed" on all testing arches; please rebuild shibboleth-sp2 against these fixed versions. nmu shibboleth-sp2_2.6.0+dfsg1-3 . ALL . -m "Rebuild against fixed xmltooling (#836898) and opensaml2 (#836921)" Thanks. --- End Message --- --- Begin Message --- On 11/09/16 15:37, Ferenc Wágner wrote: > Shall I file a serious bug against libshibsp7 to keep it out of testing > until these binNMUs are scheduled? Scheduled. Emilio--- End Message ---
Bug#837199: transition: armadillo
On 09/13/2016 07:51 PM, Emilio Pozuelo Monfort wrote: > On 10/09/16 11:35, Sebastiaan Couwenberg wrote: >> On 09/10/2016 02:11 AM, Kumar Appaiah wrote: >>> armadillo has already been uploaded to unstable. While the reverse >>> dependencies should build with a binNMU, I have not tested them and >>> will test it in the next couple of days. >> >> Because gdal needs to be rebuilt for the armadillo transition to unblock >> the vtk6 rebuild for the openmpi transition, I've also done a round of >> rebuilds to assess the impact. >> >> Fortunately the number of reverse dependencies for armadillo is limited, >> and all packages rebuilt successfully: >> >> gdal (2.1.1+dfsg-4) OK >> gnss-sdr (0.0.8-1) OK >> mlpack (2.0.2-1) OK >> seer (1.1.1-2) OK >> >> pktools (2.6.7-2) OK >> >> I'd like to have gdal (2.1.1+dfsg-4) migrate to testing to get the two >> RC bugfixes into stretch, before binNMUs for the armadillo rdeps are >> scheduled. > > I scheduled everything but gdal. Let's see if gdal migrates tonight once perl > is > old enough. Thanks for waiting with the gdal binNMU, I appreciate that a lot. I really hope having perl migrate will be sufficient, the gdal situation in testing has caused several RC bugs and a thread on -devel :-( Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#836917: transition: openmpi
On 12/09/16 17:52, Alastair McKinstry wrote: > I've NMU'd libint2 to fix the FTBFS with mpqc3, below. However it takes > ~6 hours to compile on my decent laptop, and has been failing to build > on build systems, typically terminating with memory exhaustion. > > What, if anything, can be done to fix this? RC bug and testing removal. Cheers, Emilio
Bug#837199: transition: armadillo
On 10/09/16 11:35, Sebastiaan Couwenberg wrote: > On 09/10/2016 02:11 AM, Kumar Appaiah wrote: >> armadillo has already been uploaded to unstable. While the reverse >> dependencies should build with a binNMU, I have not tested them and >> will test it in the next couple of days. > > Because gdal needs to be rebuilt for the armadillo transition to unblock > the vtk6 rebuild for the openmpi transition, I've also done a round of > rebuilds to assess the impact. > > Fortunately the number of reverse dependencies for armadillo is limited, > and all packages rebuilt successfully: > > gdal (2.1.1+dfsg-4) OK > gnss-sdr (0.0.8-1) OK > mlpack (2.0.2-1) OK > seer (1.1.1-2) OK > > pktools (2.6.7-2) OK > > I'd like to have gdal (2.1.1+dfsg-4) migrate to testing to get the two > RC bugfixes into stretch, before binNMUs for the armadillo rdeps are > scheduled. I scheduled everything but gdal. Let's see if gdal migrates tonight once perl is old enough. Emilio
Bug#837688: marked as done (nmu: mpi4py_2.0.0-2)
Your message dated Tue, 13 Sep 2016 19:44:50 +0200 with message-idand subject line Re: Bug#837688: nmu: mpi4py_2.0.0-2 has caused the Debian Bug report #837688, regarding nmu: mpi4py_2.0.0-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 837688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mpi4py_2.0.0-2 . ANY . unstable . -m "Rebuild against libopenmpi2" Should resolve #837633 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- On 13/09/16 16:25, Yaroslav Halchenko wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu mpi4py_2.0.0-2 . ANY . unstable . -m "Rebuild against libopenmpi2" > > Should resolve #837633 This needed a give back, which I had already scheduled. Emilio--- End Message ---
Solicitud de Información
Estimados Srs. Quisieramos entrar en contacto con la persona encarga de compras de servicios de Transporte de Carga de su organización, nos gustaría ofrecerles nuestros servicios, por lo que agradecemos cualquier información que nos pueda facilitar de contacto de la misma. Puede ver nuestra nueva presentación comercial [1] DESCARGAR Reciban un cordial saludo, quedo a la espera de sus comentarios, Atentamente, Luis Arriaga Gerente Comercial [2] ven...@transmaquina.com.ve 0424-1361299 [3] www.transmaquina.com.ve This message was sent to t...@test.com by Gerencia Comercial Caracas Unsubscribe| Manage Subscription| Forward Email| Report Abuse References: 1. http://attachment.benchmarkemail.com/c464851/TransMaquina-Presentación-Comercial-2016.pdf 2. mailto:ven...@transmaquina.com.ve 3. http://benchemail.bmetrack.com/c/l?u=5F05768=8EA96C=717D3=1=3hZXdo9tE%2FWpG1lt0VIgVKHLBhtVN81S79F%2FXN9Dq84%3D=1 This message was sent to debian-release@lists.debian.org by vent...@transmaquina.com.ve You can modify/update your subscription via the link below. Unsubscribe from all mailings http://benchemail.bmetrack.com/c/su?e=9FFE9C=717D3=F60F9F1=KpA9FlxWrSfLA9U2H%2FV%2B3L%2FeNWSbTFLphENb71UYrR8%3D=A0B111B Manage Subscription http://benchemail.bmetrack.com/c/s?e=9FFE9C=717D3=F60F9F1=KpA9FlxWrSfLA9U2H%2FV%2B3L%2FeNWSbTFLphENb71UYrR8%3D=A0B111B Forward Email http://benchemail.bmetrack.com/c/f?e=9FFE9C=717D3=F60F9F1=KpA9FlxWrSfLA9U2H%2FV%2B3L%2FeNWSbTFLphENb71UYrR8%3D=A0B111B Report Abuse http://benchemail.bmetrack.com/Abuse?e=9FFE9C=717D3=F60F9F1=KpA9FlxWrSfLA9U2H%2FV%2B3L%2FeNWSbTFLphENb71UYrR8%3D=A0B111B Caracas Email Marketing BenchmarkEmail.com [http://benchemail.bmetrack.com]
Bug#837688: nmu: mpi4py_2.0.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mpi4py_2.0.0-2 . ANY . unstable . -m "Rebuild against libopenmpi2" Should resolve #837633 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
NMU of abyss for FTBFS
Hi, I have NMU's abyss 1.9.0 to DELAYED/5, to fix the FTBFS that is blocking openmpi2. The debdiff is attached for your review, Best regards Alastair McKinstry -- Alastair McKinstry,, , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered. diff -Nru abyss-1.9.0/debian/changelog abyss-1.9.0/debian/changelog --- abyss-1.9.0/debian/changelog2016-09-13 09:03:05.0 +0100 +++ abyss-1.9.0/debian/changelog2015-07-16 10:28:54.0 +0100 @@ -1,10 +1,3 @@ -abyss (1.9.0-1.1) unstable; urgency=medium - - * Non-maintainer upload. - * Fix for FTBFS in g++6 : tuple now in std::tuple. Closes: #837059 - - -- Alastair McKinstry Tue, 13 Sep 2016 09:03:05 +0100 - abyss (1.9.0-1) unstable; urgency=medium * New upstream version diff -Nru abyss-1.9.0/debian/patches/tr_tuple.patch abyss-1.9.0/debian/patches/tr_tuple.patch --- abyss-1.9.0/debian/patches/tr_tuple.patch 2016-09-13 09:03:05.0 +0100 +++ abyss-1.9.0/debian/patches/tr_tuple.patch 2015-07-16 10:28:54.0 +0100 @@ -1,8 +1,29 @@ -Description: Fix FTBFS on new g++ (6.2). Closes: #837059. +Description: + TODO: Put a short summary on the line above and replace this paragraph + with a longer explanation of this change. Complete the meta-information + with other relevant fields (see below for details). To make it easier, the + information below has been extracted from the changelog. Adjust it or drop + it. + . + abyss (1.9.0-1.1) unstable; urgency=medium + . + * Non-maintainer upload. + * Fix FTBFS on new g++ (6.2). Closes: #837059. Author: Alastair McKinstry Bug-Debian: https://bugs.debian.org/837059 -Last-Updated: 2016-09-13 -Forwarded: no + +--- +The information above should follow the Patch Tagging Guidelines, please +checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here +are templates for supplementary fields that you might want to add: + +Origin: , +Bug: +Bug-Debian: https://bugs.debian.org/ +Bug-Ubuntu: https://launchpad.net/bugs/ +Forwarded: +Reviewed-By: +Last-Update: 2016-09-13 --- abyss-1.9.0.orig/lib/gtest-1.7.0/include/gtest/gtest-printers.h +++ abyss-1.9.0/lib/gtest-1.7.0/include/gtest/gtest-printers.h signature.asc Description: OpenPGP digital signature
NMU for mpqc (openmpi2 transition)
Hi, I have uploaded an NMU for mpqc to DELAYED/5. mpqc was FTBFS on g++6 changes, and blocking the openmpi2 transition. The debdiff is attached for your review, Best regards Alastair McKinstry -- Alastair McKinstry,, , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered. diff -Nru mpqc-2.3.1/debian/changelog mpqc-2.3.1/debian/changelog --- mpqc-2.3.1/debian/changelog 2015-08-16 22:33:03.0 +0100 +++ mpqc-2.3.1/debian/changelog 2016-09-13 06:00:11.0 +0100 @@ -1,3 +1,10 @@ +mpqc (2.3.1-16.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS on g++6 transition (Closes: #812036) + + -- Alastair McKinstry Tue, 13 Sep 2016 06:00:11 +0100 + mpqc (2.3.1-16.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru mpqc-2.3.1/debian/patches/g++6-constexpr.patch mpqc-2.3.1/debian/patches/g++6-constexpr.patch --- mpqc-2.3.1/debian/patches/g++6-constexpr.patch 1970-01-01 01:00:00.0 +0100 +++ mpqc-2.3.1/debian/patches/g++6-constexpr.patch 2016-09-13 06:00:11.0 +0100 @@ -0,0 +1,19 @@ +Author: Alastair McKinstry +Description: constexpr needed in g++6 (c++11) +Last-Updated: 2016-09-13 +Forwarded: no +Bug-Origin: https://bugs.debian.org/812036 + +Index: mpqc-2.3.1/src/lib/chemistry/qc/mbptr12/transform_tbint.h +=== +--- mpqc-2.3.1.orig/src/lib/chemistry/qc/mbptr12/transform_tbint.h mpqc-2.3.1/src/lib/chemistry/qc/mbptr12/transform_tbint.h +@@ -61,7 +61,7 @@ class TwoBodyMOIntsTransform : virtual p + protected: + /** By default, integrals smaller than zero_integral are considered zero. + This constant is only used in checking integrals, not computing them. */ +- static const double zero_integral = 1.0e-12; ++ static constexpr double zero_integral = 1.0e-12; + /// Predefined enumerated type for the MO spaces + typedef struct { + enum {Space1, Space2, Space3, Space4}; diff -Nru mpqc-2.3.1/debian/patches/series mpqc-2.3.1/debian/patches/series --- mpqc-2.3.1/debian/patches/series2013-11-26 22:40:51.0 + +++ mpqc-2.3.1/debian/patches/series2016-09-13 06:00:11.0 +0100 @@ -7,3 +7,4 @@ 14_sc-config_sclibs.patch 15_sc_config_omit_external_libs.patch 16_format-security.patch +g++6-constexpr.patch signature.asc Description: OpenPGP digital signature
Re: Bug#836917: transition: openmpi
On 09/12/2016 05:52 PM, Alastair McKinstry wrote: > I've NMU'd libint2 to fix the FTBFS with mpqc3, below. However it takes > ~6 hours to compile on my decent laptop, and has been failing to build > on build systems, typically terminating with memory exhaustion. > > What, if anything, can be done to fix this? blacklist the packages all but the most powerful buildds I guess. > mpi4py was also failing to build with openmpi-2.0.1 due to hangs in the > test suite; I've just uploaded 2.0.1-5 which includes a fix for this. > mpi4py will need to be rebuilt (there is an older RC bug due to FTBFS on > 1.10.3, which is now obsolete). I've confirmed that the test failures due to timeouts have been fixed with openmpi (2.0.1-5), retrying its rebuilds on the buildds should let it build successfully now, and unblock the builds of its reverse dependencies. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 signature.asc Description: OpenPGP digital signature
Re: libgnupg-interface-perl not migrating to testing
On Mon, Sep 12, 2016 at 23:32:50 +0200, gregor herrmann wrote: > And gnupg 2.x doesn't migrate because of #836259. > And libgnupg-interface-perl is about to be removed from testing > because of #834281 -- but, I think, this bug doesn't affect testing > since there's gnupg 1.4.x. So removing the stretch tag might already > help? > No, all bugs tagged sid should also be tagged stretch. Cheers, Julien
Bug#834854: jessie-pu: package charybdis/3.4.2-5~deb8u1
On Sun, Sep 11, 2016 at 16:58:34 -0400, Antoine Beaupré wrote: > 1. ignore the above two extra issues and simply add the patch for #215 > to the pile of patches in jessie > 2. import the new gnutls.c module from an eventual new 3.5 release > upstream directly in jessie - this may be difficult because of internal > API changes > 3. import 3.5.x directly in jessie > > I would like to have feedback from the release team as to which approach > to take forward. > I don't think 3 is a reasonable option. The rest will depend on specifics. Cheers, Julien
Bug#836910: jessie-pu: package kamailio/4.2.0-2+deb8u1
On Sun, Sep 11, 2016 at 20:48:07 +0200, Julien Cristau wrote: > > +diff --git a/modules/tls/tls_init.c b/modules/tls/tls_init.c > > +index a381be1..7bfc10f 100644 > > +--- a/modules/tls/tls_init.c > > b/modules/tls/tls_init.c > > +@@ -543,8 +543,10 @@ int init_tls_h(void) > > + #endif > > + ssl_version=SSLeay(); > > + /* check if version have the same major minor and fix level > > +- * (e.g. 0.9.8a & 0.9.8c are ok, but 0.9.8 and 0.9.9x are not) */ > > +- if ((ssl_version>>8)!=(OPENSSL_VERSION_NUMBER>>8)){ > > ++ * (e.g. 0.9.8a & 0.9.8c are ok, but 0.9.8 and 0.9.9x are not) > > ++ * - values is represented as 0xMMNNFFPPS: major minor fix patch status > > ++ * 0x00090705f == 0.9.7e release */ > > ++ if ((ssl_version>>12)!=(OPENSSL_VERSION_NUMBER>>12)){ > > + LOG(L_CRIT, "ERROR: tls: init_tls_h: installed openssl library " > > + "version is too different from the library the > > ser tls module " > > + "was compiled with: installed \"%s\" (0x%08lx), > > compiled " > > TBH, this seems just as wrong; libssl has a SONAME for a reason, no need > to reinvent broken checks in each user. > If I'm reading it right, the new check will still be unhappy with libssl1.0.0 1.0.2h-1~bpo8+2 from jessie-backports, whereas that should be ABI-compatible with libssl1.0.0 1.0.1t-1+deb8u2 from stable. Cheers, Julien
Bug#837427: wheezy-pu: package libphp-adodb/5.15-1
Adam D. Barratt wrote: > > Surely wheezy-pu doesn't even exist anymore…? > > In practical terms, indeed not. Then let's close this bug then (in bcc) and not distract the release team any more :) > fwiw, the original bug report doesn't appear to have made it to > debian-release, so I assume the diff is reasonably large. Good to know, thanks. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#837427: wheezy-pu: package libphp-adodb/5.15-1
On 2016-09-13 8:46, Chris Lamb wrote: Hi Jean, wheezy-pu: package libphp-adodb/5.15-1 I currently have the soft "lock" on this package in data/dla-needed.txt. Would you like me to upload this to LTS? Surely wheezy-pu doesn't even exist anymore…? In practical terms, indeed not. fwiw, the original bug report doesn't appear to have made it to debian-release, so I assume the diff is reasonably large. Regards, Adam
Bug#837427: wheezy-pu: package libphp-adodb/5.15-1
Hi Jean, > wheezy-pu: package libphp-adodb/5.15-1 I currently have the soft "lock" on this package in data/dla-needed.txt. Would you like me to upload this to LTS? Surely wheezy-pu doesn't even exist anymore…? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-