Bug#942106: (some kind of) transition: add python3.8 as a supported python3 version

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Please setup a tracker to add python3.8 as a supported python3 version. This is non-blocking, as packages can migrate on their own once built. I'm not yet starting this, just want to h

Bug#942095: nmu: rebuild packages for binutils 2.33

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please binNMU these packages for the binutils 2.33 upload to unstable: naev 0.7.0-2 wcc 0.0.2+dfsg-3 (amd64 only) looking-glass 0+b1-1 kcov 36+dfsg-1 also, binutils-mingw64 might need a so

Re: Bug#941263: gcc-9: ICE in mips_split_move when compiling qtwebengine-opensource-src on mipsel

On 27.09.19 12:48, Dmitry Shachnev wrote: It looks like it is already fixed upstream: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=273174 So please backport that change to the Debian package. The Debian MIPS maintainers should get this backported upstream, then it get's updated in

Bug#940004: nmu: isl

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please binNMU these packages for the recent isl upload to unstable: that only affects various gcc packages. the native and cross compilers are uploaded, the -mipsen packages are in unstabl

Bug#940003: nmu: rebuild packages for binutils 2.32.51.x

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please binNMU these packages for the recent binutils upload to unstable: naev 0.7.0-2 wcc 0.0.2+dfsg-3 (amd64 only) looking-glass 0+b1-1

Re: stop building the mipsel and mips64el cross compilers

On 05.09.19 11:41, YunQiang Su wrote: Matthias Klose 于2019年9月4日周三 下午1:46写道： Hi, I will stop building the mipsel and mips64el cross packages from the binutils, gcc-8-cross, gcc-9-cross, gcc-defaults, cross-toolchain-base packages. There is Thank you for your great work on cross toolchains

stop building the mipsel and mips64el cross compilers

Hi, I will stop building the mipsel and mips64el cross packages from the binutils, gcc-8-cross, gcc-9-cross, gcc-defaults, cross-toolchain-base packages. There is infrastructure to build these cross compilers from the binutils-mipsen, gcc-8-cross-mipsen, gcc-9-cross-mipsen, gcc-defaults-mipse

Bug#939048: transition: glibc

On 31.08.19 16:12, Aurelien Jarno wrote: - gcc-9 - gcc-snapshot I'll take care of these with regular uploads.

Bug#931659: transition: rm python2

On 21.08.19 21:40, Matthias Klose wrote: > On 09.07.19 17:50, Matthias Klose wrote: >> On 09.07.19 00:31, Scott Kitterman wrote: > > could somebody fix the py2-removal tracker again? replacing the terminating \b > chars with \s (4 times)? currently it matches all pytho

Re: [Cross-toolchain-base-devs] Testing migration of linux

On 23.08.19 17:41, Ben Hutchings wrote: > We now have a version of linux (5.2.9-2) that builds on all release > architectures and doesn't seem to cause build regressions for other > packages. I think that this should migrate to testing soon, as the > version in testing is missing important securit

Bug#931659: transition: rm python2

On 09.07.19 17:50, Matthias Klose wrote: > On 09.07.19 00:31, Scott Kitterman wrote: could somebody fix the py2-removal tracker again? replacing the terminating \b chars with \s (4 times)? currently it matches all python-* (python-gi-dev, python-*-doc, ...) I think we are better with a smal

Re: Dropping mips architecture for bullseye and sid

On 20.08.19 15:17, Aurelien Jarno wrote: > Dear release team, > > On 2019-07-20 12:46, Aurelien Jarno wrote: >> Dear all, >> >> The mips architecture, supporting 32-bit big-endian MIPS CPUs, has >> been supported in Debian for more than 15 years. Due to the limited 2GB >> virtual address space and

Bug#934967: nmu: rebuild packages for binutils 2.32.51.x

On 17.08.19 15:32, Matthias Klose wrote: > Please binNUM these packages for the recent binutils upload to unstable: > > naev 0.7.0-2 > wcc 0.0.2+dfsg-3 (amd64 only) looking-glass 0+b1-1 is needed too.

Bug#934967: nmu: rebuild packages for binutils 2.32.51.x

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please binNUM these packages for the recent binutils upload to unstable: naev 0.7.0-2 wcc 0.0.2+dfsg-3 (amd64 only)

Same procedure as every year: GCC defaults change (GCC 9)

GCC 9 was released earlier this year, it is now available in Debian testing/unstable. I am planning to do the defaults change in mid August, around the time of the expected first GCC 9 point release (9.2.0). There are only soname changes for rather unused shared libraries (libgo) involved, and the

Bug#919641: transition: readline (7 -> 8)

On 26.07.19 20:17, Jonathan Wiltshire wrote: > Control: tag -1 pending > > On Fri, Jan 18, 2019 at 08:45:38AM +0100, Matthias Klose wrote: >> readline is in experimental for some time, the changes are API compatible, >> and >> afaics there are no build failures cause

Bug#931629: nmu: rebuild packages for binutils 2.32.51.x

On 15.07.19 16:36, Paul Gevers wrote: > Hi Matthias, > > On 08-07-2019 14:57, Matthias Klose wrote: >> Please binNUM these packages for the recent binutils upload to unstable: >> >> boinc-app-eah-brp 0.20170426+dfsg-10 >> naev 0.7.0-2 >> tulip 4.8.

Bug#931659: transition: rm python2

On 09.07.19 00:31, Scott Kitterman wrote: > Ben file: > > title = "python-defaults"; > is_affected = .depends ~ > /python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-doc|python-dbg|libpython-dbg|python-all|python-all-dev|python-all-dbg|libpython-all-dev|libpython-all-dbg|pytho

Bug#931659: transition: rm python2

On 09.07.19 00:31, Scott Kitterman wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > The Debian Python teams are working to push early for reduction/removal > of our python(2) packages with the goal of releasing bullse

Re: Bits from the Release Team: ride like the wind, Bullseye!

> No binary maintainer uploads for bullseye > = > > The release of buster also means the bullseye release cycle is about to begin. > From now on, we will no longer allow binaries uploaded by maintainers to > migrate to testing. This means that you will need

Bug#931629: nmu: rebuild packages for binutils 2.32.51.x

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please binNUM these packages for the recent binutils upload to unstable: boinc-app-eah-brp 0.20170426+dfsg-10 naev 0.7.0-2 tulip 4.8.0dfsg-2 wcc 0.0.2+dfsg-3 (amd64 only)

Bug#926780: unblock gcc-8/8.3.0-7 and updated cross builds

Control: tags -1 - wontfix Control: reopen -1 On 20.06.19 13:54, Paul Gevers wrote: > Control: tags -1 wontfix > Control: close -1 > > Hi Matthias, > > On 06-06-2019 12:01, Paul Gevers wrote:> doko, I know you are > maintaining quite some key packages, so extra work> is probably not what > you a

Bug#929637: unblock: cross-toolchain-base{,-ports,-mipsen} - rebuilt using glibc 2.28-10

Control: tags -1 - moreinfo On 09.06.19 21:58, Paul Gevers wrote: > Control: tags -1 moreinfo > > Hi Matthias, > > On Mon, 27 May 2019 20:32:48 +0200 Matthias Klose wrote: >> please unblock the three cross-toolchain-base* packages, rebuilt using glibc >> 2.28-10, whi

Bug#928185: unblock: openjdk-11/11.0.3+7-4

On 19.06.19 22:03, Paul Gevers wrote: > Hi Tony, > > On 18-06-2019 22:14, tony mancill wrote: >> Things are looking good so far with 11.0.4+4+really11.0.3+7 in unstable, >> and so I would like to prepare the t-p-u upload. At the moment, the >> version I have is 11.0.3+7-5, since that would have b

Bug#928185: unblock: openjdk-11/11.0.3+7-4

On 12.06.19 00:37, Moritz Mühlenhoff wrote: > On Mon, Jun 10, 2019 at 09:46:41PM -0700, tony mancill wrote: >> I am not a member of the OpenJDK team and contributed far less to the >> JDK 8 -> 11 transition than Emmanuel has. If he and Matthias are in >> agreement and the plan is palatable to the

Bug#928185: unblock: openjdk-11/11.0.3+7-4

On 12.06.19 20:38, Paul Gevers wrote: > Hi Matthias, > > On 12-06-2019 10:33, Emmanuel Bourg wrote: >> I talked to Matthias on IRC yesterday, he was ok with the +really >> version in unstable only as a testbed for a tpu upload with a sane version. > > Can you explain why, please? because we had

Bug#928185: unblock: openjdk-11/11.0.3+7-4

On 29.05.19 00:23, Sam Hartman wrote: >> "Emmanuel" == Emmanuel Bourg writes: > > I'm not on the release team and cannot authorize a TPU. > > > As an interested bystander I'd ask that you make sure any TPU contains a > fix for the serious accessibility issue in > https://bugs.debian.org/cgi

Bug#929637: unblock: cross-toolchain-base{,-ports,-mipsen} - rebuilt using glibc 2.28-10

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock please unblock the three cross-toolchain-base* packages, rebuilt using glibc 2.28-10, which was already accepted for testing. cross-toolchain-base 35 cross-toolchain-base-ports 29 cross-too

Bug#926778: unblock: python3.7 3.7.3 packages

On 11.05.19 18:56, Paul Gevers wrote: > Control: tags -1 moreinfo > > Hi doko, > > On Wed, 10 Apr 2019 10:23:15 +0200 Matthias Klose wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags:

Bug#928185: unblock: openjdk-11/11.0.3+7-4

Control: tag -1 - moreinfo On 02.05.19 10:30, Julien Cristau wrote: > Control: tag -1 moreinfo > > Hi Matthias, > > On Mon, Apr 29, 2019 at 06:12:36PM +0200, Matthias Klose wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian...

Bug#928185: unblock: openjdk-11/11.0.3+7-4

Control: tags -1 - moreinfo Control: tags -1 + wontfix On 02.05.19 10:30, Julien Cristau wrote: > Control: tag -1 moreinfo > > Hi Matthias, > > On Mon, Apr 29, 2019 at 06:12:36PM +0200, Matthias Klose wrote: >> Package: release.debian.org >> Severity: nor

Bug#928188: unblock gcc-8/8.3.0-7 and updated cross builds

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock gcc-8/8.3.0-7 and updated cross builds. This includes upstream backports to around the date of the GCC 9.1 release. this includes gcc-8/8.3.0-7 gcc-8-cross/28 gcc-8-cross-p

Bug#928186: unblock: gcc-7/7.4.0-9

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock: gcc-7/7.4.0-9, some packaging and upstream backports to around the state of the GCC 9.1 release. If we ship gcc-7, please consider shipping -9 instead of -6. The removal of

Bug#928185: unblock: openjdk-11/11.0.3+7-4

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock openjdk-11/11.0.3+7-4. That's the quarterly security update and should be released with buster. No more updates planned until the next security update in July.

Bug#926774: unblock: binutils/2.31.1/16

Control: tags -1 - moreinfo On 21.04.19 15:16, Paul Gevers wrote: > Control: tags -1 moreinfo > > Hi doko, > > On Wed, 10 Apr 2019 10:15:40 +0200 Matthias Klose wrote: >> binutils (2.31.1-16) unstable; urgency=medium >> . >>* Snapshot, taken from the 2.31

Bug#926780: unblock: gcc-7/7.4.0-8

ng the gcc-hppa64 package. -- Matthias Klose Tue, 26 Mar 2019 13:21:53 +0100 gcc-7 (7.4.0-7) unstable; urgency=medium * Update to SVN 20190308 (r269489) from the gcc-7-branch. - Fix PR target/89397 (x86), PR ada/81956, PR fortran/72714, PR fortran/77583, PR fortran/87689. * Fix PR

Bug#926779: unblock: python2.7/2.7.16-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock python2.7, fixing two CVEs, and fixing a potential upgrade issue with partial upgrades: Changes: python2.7 (2.7.16-2) unstable; urgency=high . [ Matthias Klose

Bug#926778: unblock: python3.7 3.7.3 packages

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock python3.7, python3-stdlib-extensions and python3-defaults, bumping the version to the final 3.7.3 release, and fixing a bus error on armhf, and avoiding unaligned memory acces

Bug#926775: unblock: pygccjit/0.4-8

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock please unblock pygccjit, built using GCC 8 instead of GCC 7.

Bug#926774: unblock: binutils/2.31.1/16

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Changes: binutils (2.31.1-16) unstable; urgency=medium . * Snapshot, taken from the 2.31 branch (20190321). - Fix PR ld/24355, segfault in function called from ppc_finish_symbols.

Bug#926773: unblock: bash/5.0-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking bash, adding one upstream issue, and fixing the clear_console utility. Changes: bash (5.0-3) unstable; urgency=medium . * Apply upstream patch 003. * Fix

Bug#926747: unblock: adacontrol/1.20r7-2

On 10.04.19 02:55, Nicolas Boulenguez wrote: > override_dh_auto_test-arch: >ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS) $(DEB_BUILD_PROFILES))) > - cd test && sh run.sh > +# Disable build-time tests so that the severity of #924835 can be > +# lowered and the package accepted into buster.

Bug#924340: unblock: python2.7/2.7.16-1 python-stdlib-extensions/2.7.16-1 python-defaults/2.7.16-1

Control: tag -1 - moreinfo On 17.03.19 17:05, Jonathan Wiltshire wrote: > Control: tag -1 moreinfo > > On Mon, Mar 11, 2019 at 08:31:28PM +0100, Matthias Klose wrote: >> Please consider unblocking the python2 packages to the final 2.7.16 release, >> basically bumping the ve

Bug#924772: unblock: lxml/4.3.2-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock lxml, fixing exactly one segfault. The diff is large because upstream rebuilt with a new cython version. == lxml changelog == 4.3.2 (2019-02-29) ===

Bug#924771: unblock: gcc-python-plugin/0.17-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock gcc-python-plugin, just a rebuild for GCC 8.

Bug#924340: unblock: python2.7/2.7.16-1 python-stdlib-extensions/2.7.16-1 python-defaults/2.7.16-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking the python2 packages to the final 2.7.16 release, basically bumping the version and reporting a final release number in sys.version.

Bug#924338: unblock: binutils-/gcc -mipsen packages

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking binutils-mipsen, gcc-8-cross-mipsen, gcc-defaults-mipsen (the gcc-* packages are not yet in testing). the mips64 packages were removed from the -ports packages, a

Bug#919641: transition: readline (7 -> 8)

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition readline is in experimental for some time, the changes are API compatible, and afaics there are no build failures caused by readline. I filed some RC issues for unrelated ftbfs. A handfu

Bug#916817: transition: remove python3.6

On 19.12.18 04:54, Matthias Klose wrote: > that's what I used for Ubuntu: > > title = "Drop Python3.6 compiled extensions"; > is_affected = .build-depends ~ > /python3(-all)?-dev|python3|python3.6|python3.7/; > is_good = .depends ~ /python3 \(>= 3

Bug#916817: transition: remove python3.6

that's what I used for Ubuntu: title = "Drop Python3.6 compiled extensions"; is_affected = .build-depends ~ /python3(-all)?-dev|python3|python3.6|python3.7/; is_good = .depends ~ /python3 \(>= 3\.7\~\)/ | .depends ~ /libpython3\.7/ | .depends ~ /python3\.7/; is_bad = .depends ~ /python3 \(>= 3\.6

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

On 07.07.18 17:24, YunQiang Su wrote: > Niels Thykier 于2018年6月28日周四 上午4:06写道： >> List of concerns for architectures >> == >> >> The following is a summary from the current architecture qualification >> table. >> >> * Concern for ppc64el and s390x: we are dependent

Re: Are we ready to block on autopkgtest regressions?

On 23.09.2018 13:31, Graham Inggs wrote: > Hi Niels > > On 23 September 2018 at 13:00, Niels Thykier wrote: >> I intend to submit this next week and make 29-30/9 the first weekend to >> have the increased delay assuming there is consensus. > ... >> At the moment, I have no plans to change the urg

Bug#904273: nmu: openmpi_3.1.1.real-4 mpich_3.3~b2-7

On 22.07.2018 20:57, Mattia Rizzolo wrote: > On Sun, Jul 22, 2018 at 08:18:38PM +0200, Matthias Klose wrote: >> On 22.07.2018 16:24, Gilles Filippini wrote: >>> Now that gcc-8 is the default on most architectures, please trigger a binnmu >>> for openmpi and mpich: &g

Bug#904273: nmu: openmpi_3.1.1.real-4 mpich_3.3~b2-7

On 22.07.2018 16:24, Gilles Filippini wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi, > > Now that gcc-8 is the default on most architectures, please trigger a binnmu > for openmpi and mpich: > > nmu openmpi_3.1.1.

Bug#904190: binNMU needed for eclipse-titan (upper dependency on gcc)

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu a binNMU is needed for eclipse-titan (upper dependency on gcc).

Bug#904092: transition: libgfortran (GCC 8)

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition GCC 8 bumps the libgfortran ABI from 4 to 5, please schedule binNMUs with an added build dependency: gfortran (>= 4:8.1). tracker at https://release.debian.org/transitions/html/libgfortr

GCC and binutils updates for buster

GCC 8 is available in testing/unstable, and upstream is approaching the first point release. I am planning to make GCC 8 the default at the end of the week (gdc and gccgo already point to GCC 8). Most runtime libraries built from GCC are already used in the version built from GCC 8, so I don't ex

Bug#902582: (some kind of) transition: add python3.7 as a supported python3 version

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Please setup a tracker to add python3.7 as a supported python3 version. This is non-blocking, as packages can migrate on their own once built. is_affected = .build-depends ~ /python3-

preparing for binutils-2.31

According to [1], binutils 2.31 (currently in experimental) will branch in about a week, and I'll plan to upload the branch version to unstable. Test results are reported to [2], these look reasonable, except for the various mips targets, however as seen in the past, it doesn't make a differenc

Bug#901546: transition: libcdio

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition libcdio 2.0 in experimental changes the API slightly again. All packages build, except for - vcdimager (new upstream required, in experimental) - libdevice-cdio-perl (new upstream

Bug#894721: nmu: octave - record changed jvm path

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu octave needs a rebuild to record the changed jvm path with OpenJDK 9.

Bug#894210: libisl transition

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Not really a transition, but binNMUs for two packages should be done: gcc-arm-none-eabi gcc-mingw-w64

Bug#870258: GCC 7 related library transitions

On 13.03.2018 09:38, Emilio Pozuelo Monfort wrote: > On 03/03/18 10:59, Emilio Pozuelo Monfort wrote: >> As you can see it's a bunch of packages building with gcc-6 & g++-6. They >> probably >> need new upstream versions that support GCC 7. The only exception is >> libpam-script >> build-dependin

Bug#890101: transition: libopenraw

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition libopenraw is now uploaded to unstable. The only package needing a binNMU is tumbler.

Bug#889069: binutils related binNMUs

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu please binNMU boinc-app-eah-brp and wcc for the upper dependencies on binutils.

Bug#883921: transition: libical

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Please setup a libical transition tracker. title = "libical 3.0.0"; is_affected = .depends ~ /libical2|libical3/; is_good = .depends ~ /libical3/; is_bad = .depends ~ /libical2/; The ne

Bug#881718: transition: libcdio / libcdio-paranoia

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-CC: nboul...@debian.org libcdio / libcdio-paranoia from experimental are needed to fix th GCC 7 build failure. There is a fix in the bug report, however it changes the ABI as w

Bug#880523: remove python3.5 from the archive

Package: release.debian.org python3.6 is now the default python3 version. python3.5 needs to be dropped and removed. Please schedule binNMUs to drop 3.5 as a supported python3 version. See https://release.debian.org/transitions/html/python3.5-rm.html

Bug#875859: nmu: julia_0.4.7-7

On 15.09.2017 12:04, Graham Inggs wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > X-Debbugs-Cc: pkg-julia-de...@lists.alioth.debian.org > > Dear Release Team > > Openblas recently switched to multiarch and Julia needs to

Bug#874413: nmu: binNMUs needed for dropping the _pyfpe extension

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu some binNMUs are needed for dropping the _pyfpe extension. See the list in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873791#115

Bug#871395: transition: qtbase-opensource-src

On 20.08.2017 23:37, Dmitry Shachnev wrote: > Hi, > > On Fri, Aug 18, 2017 at 10:07:03AM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: >> FWIW: we are currently waiting for a reply on >> >> >> >> Ideally the binutils bug should b

Bug#870258: GCC 7 related library transitions

On 15.08.2017 22:05, Emilio Pozuelo Monfort wrote: > Control: forwarded -1 > https://release.debian.org/transitions/html/libgfortran4.html > > Hi Matthias, > > On 31/07/17 13:42, Matthias Klose wrote: >> Package: release.debian.org >> Severity:

Bug#866335: Python3.6 blocker: automake

On 13.08.2017 23:47, Bastien ROUCARIES wrote: > control: block -1 by 872052 > control: affects 872052 src:imagemagick > > > Hi, > > I have found why phythonmagick fail: automake is at fault > > automake does not support python3.6... > > I have made a patch and I plan to NMU if you are ok ASAP

Bug#870774: nmu: mpich 3.2-7

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please binNMU mpich on all architectures building with GCC 7 as the default (the header files unfortunately encode the GCC version).

Bug#870277: nmu: packages with upper dependency on binutils

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu please binNMU packages with an upper dependency on binutils (<< 2.29). afaics these are: tulip, boinc-app-eah-brp and lush.

Bug#870258: GCC 7 related library transitions

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Bumping the GCC default to GCC 7 triggers some GCC library transitions. - libgfortran3 -> libgfortran4 - libgphobos68 -> libgphobos71 - libgo7 -> libgo9 - libasan3 -> libasan4 Afaic

Bug#866335: transition: python3-defaults

On 28.06.2017 23:46, Scott Kitterman wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > We would like to add python3.6 as a supported python3 version along with > python3.5. This is not exactly like a normal transition

Bug#863099: unblock: openjdk-8/8u131-b11-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock openjdk-8/8u131-b11-2, tightening a dependency (#862508 was considered RC).

Bug#862984: unblock: gcc-6-cross*

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock gcc-6 already has an unblock request by nthykier, which needs to be updated to -18. The corresponding gcc-6-cross and gcc-6-cross-ports uploads should be unblocked as well.

Bug#862865: unblock: cross-toolchain-base*

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock cross-toolchain-base/18 and cross-toolchain-base-ports/11, fixing a build error on i386. The packages are built using gcc-6 6.3.0-18, which is not yet in testing, however they

Bug#862783: unblock: readline/7.0-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking readline/7.0-3, applying two upstream updates, fixing RC issue #852750 by one of them.

Bug#862773: unblock: bash/4.4-5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking bash, applying one upstream patch, fixing: When -N is used, the input is not supposed to be split using $IFS, but leading and trailing IFS whitespace was still re

Bug#862492: unblock: binutils/2.28-5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking binutils/2.28-5. - low priority security updates - one fix for mips* targets - all other updates are for non-release architectures

Bug#861891: unblock: gcc-6* packages

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock gcc-6 already has an unblock request by nthykier, which needs to be updated to -16. The corresponding gcc-6-cross and gcc-6-cross-ports uploads should be unblocked as well.

Re: [Pkg-rust-maintainers] rustc/cargo in stretch

On 03.05.2017 17:04, Luca BRUNO wrote: > On Wednesday, May 3, 2017 12:09:11 PM UTC Julien Cristau wrote: > >>> So I think we should remove both packages from stretch and avoid painting >>> ourselves into a corner. Thoughts? > > Can you elaborate a bit more on the "paint ourself in a corner"? >

Bug#861733: unblock: openjdk-8/8u131-b11-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock openjdk-8/8u131-b11-1, the quarterly security update by upstream.

Bug#860127: unblock gcc packages

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock gcc-6/6.3.0-12 already is unblocked. Please unblock as well: gcc-6-cross/21 gcc-6-cross-ports/19 gcc-defaults-ports/1.168

Bug#858052: unblock: python-reportlab/3.3.0-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking python-reportlab/3.3.0-2: * Honour SOURCE_DATE_EPOCH environment variable. Closes: #828756. It makes the build reproducible, and possibly makes other builds b

Bug#856541: unblock: cross-toolchain-base/17, cross-toolchain-base-ports/10, gcc-6-cross/18 gcc-6-cross-ports/16

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock please unblock cross-toolchain-base/17, cross-toolchain-base-ports/10, gcc-6-cross/18 gcc-6-cross-ports/16. The packages these are built from are already unblocked.

Bug#851871: RM: remove gcc-5 from stretch

Package: release.debian.org Tags: stretch Please remove gcc-5, gcc-5-cross and gcc-5-cross-ports from testing. Now that the linux source is built using gcc-6, the list of packages also needing removal are acoording to [1]: - nvida-cuda-toolkit - starpu-contrib - boost1.58 - linux-grsec (whic

Re: Do we know the last binutils version it used to work?

On 08.01.2017 14:29, Lisandro Damián Nicanor Pérez Meyer wrote: > Matthias: this bug is stopping a lot of packages from migrating and in doing > so near the freeze is hurting many teams (and their users!) like the Qt/KDE > one, so I'm planning to NMU it to the last working version. > > Do we kno

Bug#850287: RM: readline6 -- remove from testing

Package: release.debian.org According to #840397, readline6 can now be removed from testing.

Re: Enabling PIE by default for Stretch

[CCing porters, please also leave feedback in #835148 for non-release architectures] On 29.09.2016 21:39, Niels Thykier wrote: > Hi, > > As brought up on the meeting last night, I think we should try to go for > PIE by default in Stretch on all release architectures! > * It is a substantial har

Re: Porter roll call for Debian Stretch

On 20.09.2016 23:46, John Paul Adrian Glaubitz wrote: > On 09/20/2016 11:16 PM, Niels Thykier wrote: >>- powerpc: No porter (RM blocker) > > I'd be happy to pick up powerpc to keep it for Stretch. I'm already > maintaining powerpcspe which is very similar to powerpc. No, you are not maintaini

Bug#838234: transition: readline/readline6

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition readline 7.0 is now released, changing the soversion. The idea is to upload the readline package from experimental (plus providing the libreadline*6-dev packages), and stop building the -

Re: The (uncalled for) toolchain maintainers roll call for stretch

On 15.09.2016 22:43, Helge Deller wrote: > Hi Matthias, > > On 10.09.2016 00:48, Matthias Klose wrote: >> While the Debian Release team has some citation about the quality of the >> toolchain on their status page, it is not one of the release criteria >> documented &

The (uncalled for) toolchain maintainers roll call for stretch

While the Debian Release team has some citation about the quality of the toolchain on their status page, it is not one of the release criteria documented by the release team. I'd like to document the status how I do understand it for some of the toolchains available in Debian. I appreciate that t

Re: FTBFS with PIE & bindnow (was: Re: Porter roll call for Debian Stretch)

Hi, thanks for the work on this. I'd like to defer the final decision to the release team, however I'm not keen on having these defaults turned on architectures which already have enough issues on their own. In the recent porters call people claim that turning on these "should not be a problem"

Bug#833747: nmu: binutils (<< 2.27) dependencies

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu please binNMU binutils (<< 2.27) dependencies: eztrace lush tulip, building with binutils (>= 2.27).

Bug#833689: nmu: pdftk

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu please binNMU pdftk to build with gcj-6.

<    1   2   3   4   5   6   7   8   >