Control: tags -1 + fixed-upstream patch
This was fixed upstream [1] by the following patch:
--- a/gdb/completer.c
+++ b/gdb/completer.c
@@ -36,7 +36,7 @@
calling a hook instead so we eliminate the CLI dependency. */
#include "gdbcmd.h"
-/* Needed for rl_completer_word_break_characters()
I suspect this failure is related to r-cran-rcppparallel and onetbb.
See the previously closed bug #1012141 and the similar bug filed
againstr-cran-lamw, #1012142.
It seems that all packages depending on r-cran-rcppparallel need to be
rebuilt since the change to onetbb and should depend on the
Hi Bas
On Sun, 4 Sept 2022 at 14:20, Sebastiaan Couwenberg wrote:
> Since no one cares enough about netcdf-fortran, I'll go an have it
> removed from the archive as I'm not willing to spend time on issues like
> these.
I'm sure you are aware, but we have a process [1] for passing packages
on to
Control: reassign -1 src:netcdf-fortran 4.6.0+ds-1
Control: affects -1 src:abinit
Hi Bas
You wrote:
> No other netcdf-fortran rdeps have shown issues which leads me to
> suspect it is an issue in abinit.
Only abinit has a comprehensive autopkgtest. The other reverse
dependencies, cdftools,
Source: r-bioc-dada2
Version: 1.24.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime between 2022-06-15 and 2022-06-22, r-bioc-dada2's regressed
in testing [1]. I've copied what I hope is the relevant part of the
log below.
Regards
Graham
Source: recoll
Version: 1.32.5-1
Severity: serious
Tags: patch
Hi Maintainer
As can be seen on reproducible builds [1], if systemd is present in
the build environment, the build fails with the following output:
dh_missing: warning: lib/systemd/system/recollindex@.service exists in
debian/tmp
Control: severity -1 important
juman 7.0-3.5 build successfully on the buildds with GCC 12.
Therefore I am lowering the severity of this bug.
Source: txt2regex
Version: 0.9-4
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Since the upload of bash 5.2~rc2-2 to unstable, txt2regex's
autopkgtests have been failing [1]. I've copied what I hope is the
relevant part of the log below.
Control: reassign -1 src:python-xarray 0.21.0-1
Hopefully assigning back to src:python-xarray now.
If you have reason to believe this issue is caused by a bug in pandas,
then please file a bug against pandas with the relevant details and
mark that it blocks this bug.
Source: busco
Version: 5.4.3-1
Severity: serious
Hi Maintainer
Busco is unable to migrate to testing due to an unsatisfiable
dependency on arm64. Britney only checks installability of arch:all
packages on amd64 and arm64, so other architectures may also be
affected.
I noticed that the busco
Hi Rebecca, Alastair
I triggered python-xarray's autopkgtest on s390x against pandas from
experimental [1]. See the test results from 2022-08-29 12:40:12 UTC.
I think the intended packages were tested together, based on seeing
the following files fetched in the log:
Get:28
Control: reopen -1
The tests on i386 [1] are still failing in the same way.
[1] https://ci.debian.net/packages/p/python-xarray/unstable/i386/
Hi Alastair
On Sat, 13 Aug 2022 at 21:39, Paul Gevers wrote:
> But the log [1] that was generated by the migration trial run has the
> output below and the runs in unstable fail too (so no missing
> *versioned* items).
Please drop the unnecessary versioned build-dependency on
python3-scipy to
Source: jupyterlab-pygments
Version: 0.2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
The autopkgtests of jupyterlab-pygments recently regressed in testing
[1]. I've copied what I hope is
Hi Tobi
On Wed, 24 Aug 2022 at 11:42, Tobias Frost wrote:
> Maybe it would be a good idea to revert pmix to 4.1.2 ? (e.g
> pmix-4.2.0+really-4.1.2-1) be uploaded and then
> do a proper transistion?
That would be appreciated by the release team.
Regards
Graham
On Wed, 24 Aug 2022 at 07:26, Diane Trout wrote:
> Hopefully working around the 32-bit test failures is enough to resolve
> the problems for scipy?
Well, dask's 32-bit tests are no longer failing on armhf and i386, so
that's enough for dask to migrate.
Scipy may still have other issues.
I
Hi Drew
On Sun, 21 Aug 2022 at 19:08, Drew Parsons wrote:
> In regards to bug severity, the dask debci failures are now marked as
> "Not a regression" so they won't hold up migration of dask.
Dask's autopkgtests are failing in testing since the removal of
scikit-learn. I raised the severity of
Hi Andrius
This is due to the bad upload of pmix, see #1017107 and #1017356.
Regards
Graham
Hi Drew
> This is pmix bug#1017356, hopefully fixed in pmix 4.2.0~rc2-1 (not clear
> why the pmix upload did not close the bug).
I don't believe it is. The FTBFS on mips64el [1] started before the
pmix upload.
Regards
Graham
[1]
Source: q2-feature-table
Version: 2022.2.0+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Since the upload of python-biom-format/2.1.12-1, the autopkgtests of
q2-feature-table have been failing [1]. I've copied the short test
summary below.
Source: q2-types
Version: 2022.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
Hi Maintainer
Since the upload of python-biom-format/2.1.12-1, the autopkgtests of
q2-types have been failing [1]. I've copied the short test summary
below.
Regards
Graham
[1]
Control: tags -1 + fixed-upstream patch
There's already an upstream commit [1] that fixes this issue.
[1]
https://git.savannah.gnu.org/cgit/src-highlite.git/commit/?id=ab9fe5cb9b85c5afab94f2a7f4b6d7d473c14ee9
Source: fenics-dolfinx
Version: 1:0.4.1-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
Your package FTBFS on mips64el during the recent rebuilds for Python
3.10 [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Source: tinyarray
Version: 1.2.3-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
Your package FTBFS on i386 during the recent rebuilds for Python 3.10
[1]. I've copied what I hope is the relevant part of the log below.
Regards
Graham
Source: gyoto
Version: 1.4.4-7
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
Your package FTBFS on arm64, mipsel and s390x during the recent
rebuilds for Python 3.10 [1]. I've copied what I hope is the relevant
part of the logs below. It
Source: python-autobahn
Version: 22.1.1+dfsg1-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
Your package has a (generated) dependency on python3.9 which is being
removed. Your package is arch:all and so cannot be binNMU'd. Please
do a source-only
Source: dh-virtualenv
Version: 1.2.2-1.1
Severity: serious
Tags: bookworm sid
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
Your package has a (generated) dependency on python3.9-venv and
python3.9 is being removed. Your package is arch:all and so cannot be
binNMU'd.
Source: librecast
Version: 0.5.1-2
Severity: serious
Hi Maintainer
debian/control contains:
Section: unknown
Regards
Graham
Source: ceph
Version: 16.2.7+ds-4
Severity: serious
Hi Maintainer
The binary package ceph-mgr-diskprediction-local has a dependency on
python3-sklearn, which is built from source package scikit-learn.
Scikit-learn is in bad shape; failing to build from source on most
architectures since the
Source: yade
Version: 2022.01a-9
Severity: serious
Tags: ftbfs
Hi Maintainer
yade currently FTBFS in unstable and testing. The failure [1] was
picked up during the onetbb transition, but might not be related as
yade was test built before the transition was started.
I've copied what I hope is
Source: r-cran-rstantools
Version: 2.2.0-1
Severity: serious
Hi Maintainer
Since the upload of r-cran-rcppparallel 5.1.5+dfsg-2, the autopkgtests
of r-cran-rstantools have been failing [1]. I've copied what I hope
is the relevant part of the log below.
Regards
Graham
[1]
Source: python-bids-validator
Version: 1.9.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2021-12-22, python-bids-validator's autopkgtests regressed in
testing [1]. I've copied what I hope is the relevant part of the log below.
Regards
Source: intel-mkl
Version: 2020.4.304-2
Severity: serious
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2021-02-17, intel-mkl's autopkgtests regressed in
testing [1]. I've copied what I hope is the relevant part of the log below.
Regards
com/imageio/imageio/pull/775
Bug-Debian: https://bugs.debian.org/1009431
Author: Graham Inggs
Last-Update: 2022-06-08
--- a/skimage/io/_plugins/pil_plugin.py
+++ b/skimage/io/_plugins/pil_plugin.py
@@ -160,7 +160,8 @@
if pil_image.mode != 'P':
raise ValueError('pil_image.mode must be eq
Source: plastimatch
Version: 1.9.3+dfsg.1-3
Severity: serious
Tags: ftbfs
Hi Maintainer
plastimatch was recently binNMU'd for the libdcmtk17 transition, but
it FTBFS. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1]
Control: tags -1 + fixed-upstream ftbfs
Control: unblock -1 by 1010595
Fixed by the following commit, not in 0.19.2 release:
https://github.com/scikit-image/scikit-image/commit/6c4294c76ab1dcbd230d3c71414761248a83bce0
Control: retitle -1 trilinos: FTBFS with onetbb 2021.5.0
Control: severity -1 important
Control: tags -1 + ftbfs
Hi
On Mon, 30 May 2022 at 13:02, Graham Inggs wrote:
> To be clear, does this failure only happen with libtbb-dev/experimental?
Assuming so.
I have tested building trili
Source: python-tornado
Version: 6.1.0-3
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2022-05-08, python-tornado's autopkgtests regressed in
testing [1].
I've copied what I hope is the relevant part below.
The package also now
This looks like fallout from #1011416.
Hi
To be clear, does this failure only happen with libtbb-dev/experimental?
I didn't see this failure while building trilinos locally with sbuild
in unstable, and it still builds (when it doesn't time out) on
reproducible builds [1].
Regards
Graham
[1]
Source: r-bioc-scater
Version: 1.18.3+ds-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2021-09-23, r-bioc-scater's autopkgtests regressed in
testing [1].
I've copied, from a current log of 1.22.0+ds-2 in unstable, what I
hope is the
Source: esys-particle
Version: 2.3.5+dfsg2-4
Severity: serious
Tags: ftbfs
Hi Maintainer
Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing esys-particle to FTBFS. Please switch the
build-depends to the unversioned libltdl-dev.
Regards
Graham
Source: dico
Version: 2.10-1
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing dico to FTBFS. Please switch the build-depends to
the unversioned libltdl-dev.
Regards
Graham
Source: newmat
Version: 1.10.4-8
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing newmat to FTBFS. Please switch the build-depends to
the unversioned libltdl-dev.
Regards
Graham
Source: mercurial
Version: 6.1-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
As can be seen on reproducible builds [1], mercurial FTBFS with Python
3.10 as the default version. I've copied what I hope is the relevant
part of the log
Source: mrgingham
Version: 1.20-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
As can be seen on reproducible builds [1], mrgingham FTBFS with Python
3.10 as the default version. I've copied what I hope is the relevant
part of the log
Source: nipy
Version: 0.5.0-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
As can be seen on reproducible builds [1], nipy FTBFS with Python 3.10
as the default version. I've copied what I hope is the relevant part
of the log below.
minor version
Author: Graham Inggs
Last-Update: 2022-03-31
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@
BUILD_ARGS ?=
SPHINX ?= sphinx-build
DOCS_OUTPUT=docs/
-PYTHON_BUILD_DIR:=$(shell $(PYTHON) -c "import distutils.util; import sys; print(distutils.util.get_platform() + '-' + sys.vers
Source: python-kyotocabinet
Version: 1.23-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
As can be seen on reproducible builds [1], python-kyotocabinet FTBFS
with Python 3.10 as the default version. I've copied what I hope is
the relevant
Source: python-clickhouse-driver
Version: 0.2.3-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
As can be seen on reproducible builds [1], python-clickhouse-driver
FTBFS with Python 3.10 as the default version. I've copied what I
hope is
Source: python-pcl
Version: 0.3.0~rc1+dfsg-11
Severity: serious
Tags: ftbfs
Hi Maintainer
Since sometime around the end of January, python-pcl started to FTBFS
in unstable and testing [1]. I've copied what I hope is the relevant
part of the log below.
Regards
Graham
[1]
Control: tags -1 + patch
Patch available in ubuntu [1].
scikit-fmm (2019.1.30-1ubuntu1) jammy; urgency=medium
* Cythonize at build time to fix FTBFS with Python 3.10
* Call dh --with numpy3 to pick up dependency on numpy-abi
-- Graham Inggs Mon, 31 Jan 2022 13:30:41 +
[1] https
Source: kdevelop-python
Version: 5.6.2-2
Severity: serious
Tags: ftbfs
Forwarded: https://bugs.kde.org/show_bug.cgi?id=438206
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
kdevelop-python has a hardcoded build-dependency on python3.9-dev.
Changing this to the generic
ON 1.7.3)
make[2]: *** [Makefile:122: html-build] Error 2
Description: Ignore distutils deprecation warnings in doc build
Author: Graham Inggs
Last-Update: 2022-03-30
--- a/doc/source/conf.py
+++ b/doc/source/conf.py
@@ -149,6 +149,7 @@
r"OpenSSL\.rand is deprecated", # OpenSSL package in
Source: mypy
Version: 0.931-1
Severity: serious
Tags: ftbfs
Hi Maintainer
Since sometime around mid-March, mypy started to FTBFS in unstable and
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1]
Source: salmon
Version: 1.6.0+ds1-1
Severity: serious
Tags: ftbfs
Hi Maintainer
Since sometime around the end of January, salmon started to FTBFS in
unstable and testing [1]. I've copied what I hope is the relevant
part of the log below.
Regards
Graham
[1]
Hi Rajendra
On Sun, 6 Mar 2022 at 12:42, Rajendra Kharat1 wrote:
> Could you please share the steps to reproduce the issue.
> As when I am trying to reproduce I ran into different problem of segmentation
> fault.
> Below are the steps that I followed.
> 1. Install python3-xarray on debian on
Source: python-confluent-kafka
Version: 1.7.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: debian-s...@lists.debian.org, ol...@debian.org
Hi Maintainer
Since the upload of 1.7.0-1, python-confluent-kafka FTBFS on s390x and
some other big-endian architectures (e.g. powerpc, ppc64) [1]. I've
Hi Diane
On Mon, 21 Feb 2022 at 05:39, Diane Trout wrote:
> It would... except numpy 1.22 just hit experimental on the 18th. and
> numba isn't compatible with numpy 1.22. I tried adding this to
> d/control,
>
> python3-numpy (<< 1.22),
>
> but my sbuild resolver still picked up numpy from
Source: dask
Version: 2021.09.1+dfsg-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:python-sparse
Hi Maintainer
Python-sparse was removed from testing in order to advance the Python
3.10 transition (#996584). Dask has a build-dependency on
python3-sparse, so currently FTBFS in
Hi Rajendra
Thanks for taking a look!
Unfortunately, that cannot be the solution, as that commit is already
present in the version of pandas in the archive [1].
Regards
Graham
[1]
https://salsa.debian.org/science-team/pandas/-/blob/debian/pandas/core/arrays/datetimelike.py#L462
On Sun, 13
Dear MIPS Porters
Could somebody take a look a this issue please?
> Hi YunQiang,
>
> On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers wrote:
> > Your package src:gcc-defaults-mipsen has been trying to
> > migrate for 62 days [2]. Hence, I am filing this bug.
>
> Any progress? It has been 1.5
Dear Arm Porters
Is anyone able to help with the bus error on armhf please?
On Wed, 16 Feb 2022 at 09:33, Andreas Tille wrote:
>
> Control: tags -1 upstream
> Control: forwarded -1
> https://github.com/scikit-learn/scikit-learn/issues/22503
> also sent another bug report
>
Source: python-xarray
Version: 0.21.0-1
X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
python-xarray's autopkgtests are failing on the big-endian s390x
architecture [1].
I've copied what
Source: python-xarray
Version: 0.21.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
python-xarray's autopkgtests are failing on the i386 architecture [1].
I've copied what I hope is the relevant part of the log
Source: opentsne
Version: 0.6.1-2
Severity: serious
Tags: ftbfs
Hi Maintainer
opentsne FTBFS on i386 [1] and this currently blocks migration to
testing. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1]
Source: libtorrent-rasterbar
Version: 2.0.5-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This is
Control: reopen -1
debian/tests/control still contains:
Test-Command: set -efu
; cp -r tests examples "$AUTOPKGTEST_TMP"
; for py in $(py3versions -r 2>/dev/null)
; do cd "$AUTOPKGTEST_TMP"
; echo "Testing with $py:"
; $py -m unittest discover -s tests -v
; done
...and the test still
Source: tkrzw-python
Version: 0.1.28-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
tkrzw-python only builds for the default python3 version, but then
attempts to run atuopkgtests against all versions.
Regards
Graham
[1]
Source: pitivi
Version: 2020.09.2-3
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since sometime around January 15, pitivi started to FTBFS in unstable [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
Source: glade
Version: 3.38.2-6
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since sometime around January 13, glade started to FTBFS in unstable [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
Source: pytorch
Version: 1.8.1-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This is seen
on the
On Sat, 22 Jan 2022 at 10:45, YunQiang Su wrote:
> Sure. I will.
Thank you!
On Sat, 22 Jan 2022 at 10:12, YunQiang Su wrote:
> Let's have a try to build matplotlib with -O3, and try to build hkl with it.
> If it works, we can workaround it for now.
> I will continue to dig the real problem of gcc (maybe).
To be clear, will you try building matplotlib with -O3 and if it
Hi YunQiang Su
Have you been able to make any progress with this issue?
If not, then we should consider asking ftp-master for temporary
removal of the affected mips64el packages from testing. We'd like to
move the python3-defaults transition along.
Regards
Graham
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
401 - 500 of 1178 matches
Mail list logo