On 15.05.24 11:14, Emilio Pozuelo Monfort wrote:
Hi Matthias,
On 20/01/2024 15:41, Matthias Klose wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Please setup a tracker for the python3-defaults transition, making
3.12
Package: release.debian.org
X-Debbugs-CC: Nicolas Boulenguez
when preparing GCC packages for time_t64, I noticed that we'll have an
ABI change for libgnat as well. Instead of doing a gnat 12 -> 12+t64
transition, let's do a gnat 12 -> 13+t64 transition instead. According
to Nicolas,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Please setup a tracker for the python3-defaults transition, making 3.12
the default Python version.
wait until 3.12.1 is in the archive. 3.12.0+ isn't well handled as a
version by some third party libraries.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-CC: debian-pyt...@lists.debian.org
Please setup a tracker to add python3.12 as a supported python3 version. This is
non-blocking, as packages can migrate on their own once
uploaded
On 01.07.23 16:55, Aurelien Jarno wrote:
Hi Matthias,
On 2023-07-01 14:16, Aurelien Jarno wrote:
On 2023-07-01 10:14, Sebastian Ramacher wrote:
Control: forwarded -1
https://release.debian.org/transitions/html/glibc-2.37.html
Control: tags -1 confirmed
On 2023-06-21 20:53:54
.
- Emit a proper error when users try to use venv
without having it installed.
- Documentation and lintian cleanups.
python3.11 (3.11.2-6) unstable; urgency=high
[ Stefano Rivera ]
* Explain more ways to pass --break-system-packages to pip.
[ Matthias Klose ]
* Fix syntax error
while we have not an 100% agreement to go ahead, I think we should aim for 3.11.
The following steps would be:
- accept the current python3-defaults into
testing (adding 3.11 as supported)
- ask for a transition slot to upload (see #1026825)
python3-defaults with 3.11 as the default
-
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-CC: debian-pyt...@lists.debian.org
Please setup a transition window for python 3.11 as the default python3 version.
A tracker is setup at
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Please setup a tracker to add python3.11 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
On 18.03.22 17:38, László Böszörményi (GCS) wrote:
Hi all,
On Fri, Mar 18, 2022 at 1:42 PM Sebastian Ramacher wrote:
On 2022-03-18 13:06:13, Jérémy Lal wrote:
FYI same here, i had to fallback to nodejs 14 instead of 16 because of that.
Last time I asked, icu maintainer had issues fixing icu
On 13.03.22 21:59, M. Zhou wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi release team,
This involves an upstream source name change (from tbb to onetbb),
as well as SOVERSION bump (from 2 to 12), along with a major API
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-CC: debian-pyt...@lists.debian.org
Please setup a transition window for python 3.10 as the default python3 version.
A tracker is setup at
On 2/10/22 11:26, Moritz Mühlenhoff wrote:
> Am Thu, Feb 03, 2022 at 03:59:00PM +0100 schrieb Thorsten Glaser:
>> Hi Holger,
>>
>>> and filed against src:debian-security-support, as openjdk-17 seems to be
>>> supported and src:debian-security-support's purpose is to documented what's
>>
>> no, 11
On 11/18/21 06:51, Sebastiaan Couwenberg wrote:
> On 11/16/21 14:23, Matthias Klose wrote:
>> I'm planning to upload python3-defaults later tonight, adding 3.10 as a
>> supported Python version. Packages are able to migrate on their own, there
>> are
>> no bl
I'm planning to upload python3-defaults later tonight, adding 3.10 as a
supported Python version. Packages are able to migrate on their own, there are
no blockages introduced on other transitions.
We have most packages ready to build for 3.10, and around 70 leaf packages still
needing some work.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Please setup a tracker to add python3.10 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
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
please binNMU packages for the (non-blocking) libgphobos transition, triggered
by the GCC defaults change (dub and cheesecutter are ftbfs, bug reports are
already filed):
Reverse
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Update libffi to version 3.4.2. The transition was done for Ubuntu, a handful
of bugs regarding build failures (mostly due to GCC 11) are filed in Debian. I
would like to get this done
* OpenJDK 17 snapshot, build 33.
* Regenerate the control file.
-- Matthias Klose Fri, 30 Jul 2021 14:48:42 +0200
openjdk-17 (17~32ea-1) unstable; urgency=high
* OpenJDK 17 snapshot, build 32.
* Security fixes:
- JDK-8256157: Improve bytecode assembly.
- JDK-8256491: Better HTTP
-2021-2388: Enhance compiler validation.
- JDK-8264079: Improve abstractions.
- JDK-8264460: Improve NTLM support.
* Encode the early-access status into the package version. LP: #1934895.
-- Matthias Klose Wed, 21 Jul 2021 09:03:54 +0200
openjdk-11 (11.0.12+6-1) unstable; urgency
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: Andreas Beckmann
Please unblock python2.7/2.7.18-8, just adding some breaks for smoother upgrades
as requested in #990520. No code changes. The debdiff is in the bug
On 5/5/21 8:51 PM, Niko Tyni wrote:
> On Fri, Apr 16, 2021 at 08:29:52PM +0200, Bastian Blank wrote:
>> On Fri, Apr 16, 2021 at 05:04:03PM +0200, Marco d'Itri wrote:
>
>>> And then all the packages currently depending on libdb5.3 will need to
>>> implement, or at least document, a transition
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock the openjdk-11 and openjdk-17 packages. For openjdk-11, it's the
quaterly security release, and for openjdk-17 it's the next snapshot made after
including the security fixes
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python2.7. No code changes, just adding a breaks for
upgrades, see #987661 for the issue and the diff for the fix.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
please unblock python3-defaults/3.9.2-3.
* Ship index.html to unbreak links in python-policy.html. Closes: #985313.
* Don't ship html policy links in the python3.9 doc directory.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
please unblock what-is-python.
* Update package descriptions for the Debian 11 (bullseye) release.
* Bump package versions and provides.
* Provide pdb symlinks in the -dev packages.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
please unblock gcc-9-cross and gcc-9-cross-ports, no-change rebuilds using the
gcc-9 version as found in bullseye.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
please unblock cross-toolchain-base-ports/45, same rationale as given for
cross-toolchain-base in #985363
On 4/7/21 4:12 PM, Sebastian Ramacher wrote:
> Control: tags -1 + moreinfo
>
> On 2021-04-07 18:26:47, YunQiang Su wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: unblock
>>
>> Please unblock package binutils-mipsen/7+c2
>>
>>
linkchecker is fixed in 10.0.1-2
Control: reopen -1
there are more packages to fix/unblock:
- b-d on python-dev,
#942912, bagel, has a fix in the VCS
- #942960, announced NMU, but never NMU'd
now fixed in catch/1.12.1-1.1
- #936950, link-checker, reopened
- apertium-arg-cat, filed new #984785
fixed in 0.2.0-2
On 3/4/21 9:58 AM, Paul Gevers wrote:
> Control: tag -1 moreinfo
>
> Hi Stefano,
>
> On 25-02-2021 07:17, Stefano Rivera wrote:
>> Please unblock package python3-defaults and python3.9
>
> The python3-defaults package is currently blocked by autopkgtest
> regressions. As usual, I suspect these
Package: release.debian.org
X-Debbugs-CC: Stefano Rivera
please unblock: setuptools/52.0.0-3, fixing the same issue #982921 as fixed in
python-packaging in
https://tracker.debian.org/news/1232090/accepted-python-packaging-209-2-source-into-unstable/
and already migrated to testing.
Discussed
Package: release.debian.org
we don't want to ship packages in bullseye still referencing the unversioned
python packages in build dependencies, dependencies and recommendations.
Graham Inggs and I were looking for those, and identified at least yasm and
zziplib, fixed in
yasm/1.3.0-2.1
Hi,
I never got feedback on the binutils/GCC plans outlined last July
https://lists.debian.org/debian-release/2020/07/msg8.html
At this point, I don't think another gcc-10 upload is needed, as people can work
around existing issues by using gcc-9, which still is used as a build
dependency.
On 2/25/21 7:41 PM, Moritz Muehlenhoff wrote:
> + * CVE-2021-3177
are all the ctypes tests passing with this patch? See #983516.
Matthias
y,
but that's what is now tested in experimental.
Matthias
python3.9 (3.9.2-1) unstable; urgency=medium
* Python 3.9.2 release. No changes since 3.9.2~rc1-1.
* Build idlelib/help.html from source, don't ship the pre-generated file.
-- Matthias Klose Sat, 20 Feb 2021 12:05:08 +0100
pyth
On 2/1/21 7:57 PM, Paul Gevers wrote:
> Hi
>
> On 29-01-2021 12:13, Matthias Klose wrote:
>>> We would be happy with either of the following:
>>> 1) upload to unstable with PR27218 only
>>> 2) upload to experimental first (with a 2.36+really2.35.2 version)
Package: release.debian.org
Severity: important
Tags: sid bullseye
As seen with glibc autopkg tests [1], the Debian CI infrastructure doesn't store
complete build logs, cutting these to 20MB (uncompressed), resulting in ~450k
compressed logs. This might not be important for successful tests, but
[please ignore this thread started by Adrian; he's making statements on behalf
of other teams, which are not correct. Also he "forgot" to CC the security team
and the package maintainers. The issue is handled in #975016.]
On 2/6/21 11:47 PM, Emmanuel Bourg wrote:
> Le 02/02/2021 à 19:04, Adrian
On 1/28/21 8:36 PM, Paul Gevers wrote:
> Hi Matthias,
>
> On 27-01-2021 22:42, Matthias Klose wrote:
>> I have been following the way the linux source package was uploaded.
>> Apparently
>> the package entered unstable with just an announcement like this. An
On 1/27/21 9:47 PM, Paul Gevers wrote:
> Hi Matthias,
>
> On 26-01-2021 18:57, Matthias Klose wrote:
>> I would like to upload binutils version 2.5.2-1 to unstable later this week.
>> The
>> 2.25.2 release is announced for this weekend ([1]). It imports fixes towards
On 1/26/21 6:53 PM, Holger Levsen wrote:
> On Tue, Jan 26, 2021 at 06:30:25PM +0100, Matthias Klose wrote:
>> On 1/26/21 5:55 PM, Holger Levsen wrote:
>>> On Tue, Jan 26, 2021 at 04:36:13PM +0100, Matthias Klose wrote:
>>>>>> :) note however that "#9750
Hi
I would like to upload binutils version 2.5.2-1 to unstable later this week. The
2.25.2 release is announced for this weekend ([1]). It imports fixes towards
the next stable version.
The pending fixes in the package are:
* PR27218, memory access violation in dwarf2dbg.c
* PR
On 1/26/21 5:55 PM, Holger Levsen wrote:
> On Tue, Jan 26, 2021 at 04:36:13PM +0100, Matthias Klose wrote:
>>>> :) note however that "#975016: OpenJDK 15 support state for Bullseye" is
>>>> still
>>> ping, has there been any progress on this?
>
On 12/2/20 5:42 PM, Holger Levsen wrote:
> On Fri, Nov 20, 2020 at 08:40:22AM +, Holger Levsen wrote:
>>> Thanks for the upload.
>> :) note however that "#975016: OpenJDK 15 support state for Bullseye" is
>> still
>> open...
>
> ping, has there been any progress on this?
chatting with
Package: release.debian.org
openjdk-N (non-default) should not trigger autopkg tests. All these don't make
any sense, as the tests are always run using the default JRE/JDK.
E.g. for 13, these were triggered today:
autopkgtest for airport-utils: amd64: Test in progress, arm64: Test in progress,
On 12/1/20 5:02 AM, YunQiang Su wrote:
> I am sorry for the later response.
>Hi,
>
> I am an active porter for the following architectures and I intend
> to continue this for the lifetime of the Bullseye release (est. end
> of 2024):
>
> For mipsel and mips64el, I
> - test most
On 11/20/20 9:33 PM, Matthias Klose wrote:
> On 11/20/20 9:13 PM, Mathieu Parent wrote:
>> Hi,
>>
>> It looks like samba was forgotten by the binNMU request.
>>
>> See https://bugs.debian.org/975330
>>
>> Can you schedule that?
>
> no, accordi
On 11/20/20 9:13 PM, Mathieu Parent wrote:
> Hi,
>
> It looks like samba was forgotten by the binNMU request.
>
> See https://bugs.debian.org/975330
>
> Can you schedule that?
no, according to
https://release.debian.org/transitions/html/python3.9-default.html
ldb ftbfs on s390x.
On 11/18/20 8:03 PM, Adrian Bunk wrote:
> On Wed, Nov 18, 2020 at 12:20:37PM +0100, Matthias Klose wrote:
>> For OpenJDK there are two other possibilities, which would require approval
>> by
>> release managers / stable release managers.
>>
>> - openjdk-16 will
On 11/18/20 7:46 PM, Moritz Muehlenhoff wrote:
> On Wed, Nov 18, 2020 at 12:20:37PM +0100, Matthias Klose wrote:
>> [removed the Python 2 bits]
>>
>> On 11/17/20 11:08 PM, Moritz Muehlenhoff wrote:
>>> Package: debian-security-support
>>> Severity: norm
On 11/18/20 1:36 PM, Florian Weimer wrote:
> * Matthias Klose:
>
>> As background: OpenJDK 12 can only be built with 11, 13 with 12, 14 with 13,
>> 15
>> with 14, 16 with 15. Only having 11 in bullseye would make backports more
>> "interesting".
>
[removed the Python 2 bits]
On 11/17/20 11:08 PM, Moritz Muehlenhoff wrote:
> Package: debian-security-support
> Severity: normal
> X-Debbugs-Cc: d...@debian.org, t...@security.debian.org
> openjdk-15 will be included, but not covered by support
> (as it's only needed to bootstrap openjdk-16 and
as outlined in
https://lists.debian.org/debian-python/2020/07/msg00023.html
it's now time to go ahead with the 3.9 defaults change.
https://lists.debian.org/debian-python/2020/11/msg00012.html
has a status update about outstanding issues, focusing on the key packages.
While not every fix is
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
While we are still in the first phase, adding 3.9 as a supported python3
version, please setup a tracker for 3.9 as the default python3 version, re-using
the tracker for 3.8 as the
status update:
https://lists.debian.org/debian-python/2020/10/msg00033.html
On 9/12/20 8:55 AM, Vasyl Gello wrote:
> Hi Matthias!
>
> On Fri, 11 Sep 2020 12:50:33 +0200 Matthias Klose wrote:
>> Control: severity -1 important
>>
>> lowering the severity, please use the BFD linker if possible, CCing to the
>> mips
>> porters.
&g
On 8/14/20 11:33 AM, Matthias Klose wrote:
> I'm now NMUing both guile-2.2 and guile-3.0 to just ignore the test results on
> ppc64el, without closing the bug reports. It's blocking the gcc-10 migration
> to
> testing.
now, the NMUs fail with the same OOM error on armhf (3.0) an
I'm now NMUing both guile-2.2 and guile-3.0 to just ignore the test results on
ppc64el, without closing the bug reports. It's blocking the gcc-10 migration to
testing.
gt;>
>> On 2020-07-15 12:14:06 +0200, Matthias Klose wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian@packages.debian.org
>>> Usertags: transition
>>>
>>> Packages build ok with the libgc from experimen
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Please setup a tracker to add python3.9 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
On 7/21/20 7:16 PM, Matthias Klose wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> These packages need rebuilding for gdc-10. Maybe it's safe to add an extra
> b-d
> on gdc (&g
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Two packages are built using the address sanitzer, the binNMUs should be done
with an extra b-d on gcc (>= 4:10.1).
wlcs
goxel
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Two packages are built using gccgo, the binNMUs should be done with an extra b-d
on gccgo (>= 4:10.1).
uswgi
gitbrute
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
These packages need rebuilding for gdc-10. Maybe it's safe to add an extra b-d
on gdc (>= 1:10.1) for the binNMUs.
a7xpg
cheesecutter
dub
dustmite
gunroar
ii-esu
mu-cade
parsec47
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Packages build ok with the libgc from experimental, except for guile. Filed
patches to fix the guile builds with make 4.3, however guile-2.0 fails tests on
amd64. guile-2.0 could be
On 7/8/20 9:21 PM, Paul Gevers wrote:
> Hi,
>
> [Note, this e-mail may look familiar as it is mostly copied over from
> the buster call, not much has changed, AFAICT].
>
> As part of the interim architecture qualification for bullseye, we
> request that DSA, the security team, Wanna build, and
Debian bullseye will be based on a gcc-10 package taken from the gcc-10 upstream
branch, and binutils based on a binutils package taken from the 2.35 branch.
I'm planning to make gcc-10 the default after gcc-10 (10.2.0) is available
(upstream targets mid July). binutils will be updated before
On 6/4/20 2:05 PM, Aurelien Jarno wrote:
> On 2020-06-04 13:06, Matthias Klose wrote:
>> On 5/21/20 11:39 AM, Aurelien Jarno wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian@packages.debian.org
>>> Usertags: tr
On 6/4/20 1:06 PM, Matthias Klose wrote:
> On 5/21/20 11:39 AM, Aurelien Jarno wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> Dear release team,
>>
>> I
On 5/21/20 11:39 AM, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Dear release team,
>
> I would like to get a transition slot for glibc 2.31. It is available in
> experimental for more than 2
On 5/7/20 9:41 PM, Paul Gevers wrote:
> Hi
>
> On 02-05-2020 21:53, Paul Gevers wrote:
>> I don't think anybody likes to do it, but we have to discuss the
>> architectures that will be part of bullseye. In the before last IRC
>> meeting I promised I would send this mail, so here we go. Let's see
On 2/3/20 8:22 PM, Simon McVittie wrote:
> On Sun, 02 Feb 2020 at 09:35:04 +0100, Matthias Klose wrote:
>> I think this is now in shape to be started.
>
> Please can this wait until the remaining bits of the libffi7 transition
> and the restructuring of the libgcc_s packaging
On 2/2/20 5:53 PM, Rene Engelhard wrote:
> On Sun, Feb 02, 2020 at 09:35:04AM +0100, Matthias Klose wrote:
>>> On 17-01-2020 23:28, Matthias Klose wrote:
>>>> Please add a transition tracker to switch the python3 default to 3.8.
>>>> It's not
>>>
Control: tags -1 - moreinfo
On 1/18/20 9:30 PM, Paul Gevers wrote:
> Control: tags -1 moreinfo
>
> Hi Matthias,
>
> On 17-01-2020 23:28, Matthias Klose wrote:
>> Please add a transition tracker to switch the python3 default to 3.8. It's
>> not
>> yet ready
On 19.01.20 09:40, Graham Inggs wrote:
> Control: forwarded -1
> https://release.debian.org/transitions/html/auto-libffi.html
> Control: tags -1 + moreinfo
>
> On Fri, 17 Jan 2020 at 23:33, Matthias Klose wrote:
>> libffi is finally released. There are two packages needing
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Please add a transition tracker to switch the python3 default to 3.8. It's not
yet ready, however it would be good to see affected packages. Please copy it
from the 3.7 defaults change
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
libffi is finally released. There are two packages needing patches:
ecl
polyml
and three packages already ftbfs in unstable:
bustle
uuagc
haskell-stack
I had done a test
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Not really a transition, but a binNMU for one package should be done:
gcc-mingw-w64
Not asking for any -mipsen package, because these are not in testing.
On 02.12.19 20:28, Paul Gevers wrote:
> Hi all,
>
> On 01-12-2019 22:45, Sandro Tosi wrote:
>> Paul, this is the thread i was talking about.
>>
>> you were copied in the original email:
>> https://lists.debian.org/debian-python/2019/10/msg00098.html
>>
>> if there is something the RT wants to
On 12.11.19 23:39, Matthias Klose wrote:
> On 07.11.19 15:08, Matthias Klose wrote:
>> This weekend, I am planning to upload python3-defaults, adding python3.8 as a
>> supported Python3 version. This may introduce some churn in unstable until
>> the
>> basic bi
On 07.11.19 15:08, Matthias Klose wrote:
> This weekend, I am planning to upload python3-defaults, adding python3.8 as a
> supported Python3 version. This may introduce some churn in unstable until
> the
> basic binNMUs are available as well.
>
> Details for the addition
On 10.11.19 14:46, Rebecca N. Palmer wrote:
mdp isn't in testing either, but if you're using a policy of "no py2removals
that break packages in testing", tnseq-transit (Depends: statsmodels) and
possibly stimfit (Recommends: pandas) need to be done as well. Those are both
thought to need new
On 10.11.19 14:22, Matthias Klose wrote:
patsy is a leaf package, no problem.
scikit-learn, needs mdp, pymvpa2, I think that's manageable, so I'm volunteering
to do the NMUs, preferably with a 0 or 1 day delay.
PyMVPA has other RC issues, is removed from testing, so ignore it for now
[CCing debian-science]
On 10.11.19 13:18, Rebecca N. Palmer wrote:
Matthias Klose wrote:
yes, please do [raise pandas 0.25 blocking bugs to "important"]
Done, but only 2 of them have been fixed since.
This leaves 13:
has patch or Ubuntu fix: matplotlib2 patsy python-apptools sc
Package: release.debian.org
Severity: wishlist
User: release.debian@packages.debian.org
Usertags: britney
Library packages still have ABI differences despite the best effort to track
them, and often migrate undetected. Reasons for that might be
- No symbols files provided in the
Package: release.debian.org
Severity: important
User: release.debian@packages.debian.org
Usertags: britney
britney doesn't run autopkg tests for binNMUs. E.g. for a library transition,
britney only runs the tests triggered by the library package, it doesn't run the
autopkg tests for all
This weekend, I am planning to upload python3-defaults, adding python3.8 as a
supported Python3 version. This may introduce some churn in unstable until the
basic binNMUs are available as well.
Details for the addition can be found at [1], known issues and patches are filed
[2]. There was
15:33, rene.engelh...@mailbox.org wrote:
Hi,
Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose :
And afaik there was no test rebuild for
bullseye
either.
Accepted cppunit 1.14.0-4 (source) into unstable
On July 26:
https://tracker.debian.org/news/1049803/accepted-cppunit-1140-4-source-into
On 29.10.19 15:09, Vincent Lefevre wrote:
On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre :
In case makefile magic triggers some rebuild, you can also run the
generated executable directly (with the right environment
On 28.10.19 22:17, Paul Gevers wrote:
Dear all,
The visible progress on this bug report stopped several days ago. I'd
like to try an get it a bit further. I'm expecting frustration on all
sides,
yes, and side note that I will use the same terms of "several days ago" for a
three day silence
On 26.10.19 22:09, Rebecca N. Palmer wrote:
What should be done with modules where Python 3.8 compatibility requires moving
to a new upstream release that doesn't support Python 2, but the Python 2
package still has dependencies (so can't be removed yet under existing rules)?
- Split them
On 11.10.19 18:46, Paul Gevers wrote:
Hi Matthias,
On 10-10-2019 15:06, Matthias Klose wrote:
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 have an overview
On 25.10.19 18:09, Rene Engelhard wrote:
Hi,
On Fri, Oct 25, 2019 at 05:59:53PM +0200, Rene Engelhard wrote:
OK, thanks, reassigning to src:gcc-9 (libstdc++6 for now) then.
no. based on what rationale?
And to prevent said gcc-9 version from migrating, to not break something
else (no idea
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
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
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=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 the
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
1 - 100 of 711 matches
Mail list logo
