Hi,
Le jeudi 09 mai 2024 à 09:45 +0200, Gianfranco Costamagna a écrit :
> Source: coq-corn
> Version: 8.19.0-1
> Severity: serious
>
> Hello, looks like there are at least two issues:
> 1) fta directory was stripped on tarball import, not sure how and
> why, because the upstream repo still
Hi,
I can just confirm that whatever was done breaks usage of gbp import-
orig --uscan.
Cheers,
J.Puydt
Package: context
Version: 2023.05.05.20230730+dfsg-2
Severity: critical
since a few days, I saw a configuration issue with the tex-common
package. (What I don't get is why it actually needs configuration since
I don't see uploads since months.)
I finally found the time to investigate and report.
Hi,
I just compiled the package without any issue.
A case of eigenbug where you compile three times and it only fails one?
Cheers,
J.Puydt
Hi,
Le lundi 29 janvier 2024 à 09:39 +, Debian Bug Tracking System a
écrit :
> Your message dated Mon, 29 Jan 2024 09:35:04 +
> with message-id
> and subject line Bug#1060988: fixed in mathcomp-analysis 1.0.0-1
> has caused the Debian Bug report #1060988,
> regarding mathcomp-analysis:
Hi,
Le dimanche 28 janvier 2024 à 08:17 +0100, Andreas Tille a écrit :
> Hi Jullien,
>
> upstream page[1] says:
>
> This package is in maintenance-only mode. New code should use the
> importlib.metadata module in the Python standard library to find
> and load entry points.
>
> So it seems
tests)
Author: Julien Puydt
Forwarded: not needed
--- entrypoints.orig/tests/test_entrypoints.py
+++ entrypoints/tests/test_entrypoints.py
@@ -19,31 +19,31 @@
def test_iter_files_distros():
result = entrypoints.iter_files_distros(path=sample_path)
-# the sample_path has 4 unique items so
Hi,
Le dimanche 21 janvier 2024 à 21:38 +0100, Paul Gevers a écrit :
> Hi,
>
> On 21-01-2024 21:06, julien.pu...@gmail.com wrote:
> > Would kicking the mathcomp-analysis package out of testing allow
> > the
> > migration of the rest of the Coq-related packages and at least give
> > a
> >
Hi,
Le dimanche 21 janvier 2024 à 08:42 +0100, Paul Gevers a écrit :
> Source: coq
> Version: 8.17.0+dfsg-1
> Severity: serious
> Control: close -1 8.18.0+dfsg-1
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
> Dear maintainer(s),
>
> The Release
Hi,
can you tell me why you declared coq package's version 8.18.0+dfsg-1 is
still affected by the issue? Your message was less than informative!
Cheers,
J.Puydt
Control: tag -1 pending
Hello,
Bug #1055732 in fpylll reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
Le mercredi 22 novembre 2023 à 18:48 +0100, Gianfranco Costamagna a
écrit :
> control: tags -1 patch
>
> Hello, not sure why and how, but this upstream commit
> fbe9e28b667e795a5ceb41bd7784bd2ea7ab10bf
>
>
Hi,
Le jeudi 16 novembre 2023 à 16:45 +0100, Gianfranco Costamagna a
écrit :
> Source: coq
> Version: 8.17.0+dfsg-1
> Severity: serious
>
> Hello,
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/coq.html
>
> As said here, there is a build failure due to probably new dune
Le mercredi 23 août 2023 à 09:07 +0100, Simon McVittie a écrit :
> On Wed, 23 Aug 2023 at 08:41:44 +0200, julien.pu...@gmail.com wrote:
> > let's lower the severity to avoid blocking migration during the
> > discussion -- after all the Breaks already avoids the file conflict
> > issue.
>
> Sorry,
Control: severity -1 normal
Hi,
let's lower the severity to avoid blocking migration during the
discussion -- after all the Breaks already avoids the file conflict
issue.
Cheers,
J.Puydt
Le mardi 22 août 2023 à 08:34 +0200, Stéphane Glondu a écrit :
>
> This situation is explicitly covered in Policy 7.3 and 7.6.1.
Section 7.3 explains why the Breaks is needed when there are file
conflicts ; we agree on that point and hence 0.6.4-2 got it.
Section 7.6 is about partial and
Le samedi 19 août 2023 à 20:58 +0200, Helmut Grohne a écrit :
> Control: reopen -1
> Control: found -1 mathcomp-analysis/0.6.4-2
>
> On Sat, Aug 19, 2023 at 05:33:11PM +, Debian Bug Tracking System
> wrote:
> > It has been closed by Debian FTP Masters
> &
Package: utop
Version: 2.13.1
Severity: serious
After I made utop run by itself (report #1042749), I tried to run it
through "dune utop" and found liblambda-term-ocaml-dev is needed for
this to work.
Cheers,
J
Package: utop
Version: 2.13.1-1
Severity: grave
Installing the utop package leads to a non-working utop executable,
because it needs xdg. The libdune-ocaml-dev package provides xdg.
Installing the libdune-ocaml-dev package makes utop fail with:
Fatal error: exception
Le mercredi 21 juin 2023 à 22:56 +0200, Adrien Nader a écrit :
> On Wed, Jun 21, 2023, julien.pu...@gmail.com wrote:
> > Le mardi 20 juin 2023 à 22:38 +0200, Adrien Nader a écrit :
> > >
> > >
> > > The patch seems to fix the issue. I say "seem" because the build
> > > compiled the file that was
Le mardi 20 juin 2023 à 22:38 +0200, Adrien Nader a écrit :
>
>
> The patch seems to fix the issue. I say "seem" because the build
> compiled the file that was failing to build but the build is not done
> yet: emulated armhf isn't fast. :)
>
> But since I reprocued the build failure before, I
Hi,
Le mardi 20 juin 2023 à 15:35 +0200, Adrien Nader a écrit :
> I was looking at the migration for coq on Ubuntu and a build failure
> on armhf is preventing it.
>
> I expect that this issue is fixed by the following commit:
>
>
Le dimanche 13 novembre 2022 à 19:08 +0100, Paul Gevers a écrit :
> Source: elpi
> Version: 1.16.5-1
> Severity: serious
> Control: close -1 1.16.7-2
> Tags: sid bookworm
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
> Dear maintainer(s),
>
> The Release Team considers
Package: pyzo
Version: 4.11.2-1
Severity: grave
Launching pyzo displays the normal window, but the shell never comes up
and the editor pane never gets a prompt ; starting from a terminal
makes the following messages fly by continuously:
QBackingStore::endPaint() called with active painter; did
Control: tag -1 pending
Hello,
Bug #1023040 in nbconvert reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le lundi 05 septembre 2022 à 08:28 +1000, Brian May a écrit :
> On Wed, Aug 03, 2022 at 12:22:32PM +0200,
> julien.pu...@gmail.com wrote:
> > I'm sorry, but I don't see why you think this is a problem with
> > setuptools-scm.
> >
> > sshuttle's debian/rules asks setuptools-scm to generate a
Control: tag -1 pending
Hello,
Bug #1018228 in jupyterlab-pygments reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
I'm sorry, but I don't see why you think this is a problem with
setuptools-scm.
sshuttle's debian/rules asks setuptools-scm to generate a version file
in its clean target. So setuptools-scm does so, and it doesn't look
invalid.
But it doesn't not correspond to the version file as shipped,
Control: tag -1 pending
Hello,
Bug #1013362 in alt-ergo reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1011964 in ipykernel reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
it is in fact a curl issue :
https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1975527
This report is a duplicate of #1011696.
I thought I had already reported to the curl maintainers, but the
corresponding curl bug is #1012263, very recent and hasn't the right
priority.
Control: tag -1 pending
Hello,
Bug #1010822 in jupyter-client reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1006816 in python-anyio reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1000271 in jupyter-client reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: pitivi
Version: 2021.05-1
Severity: grave
Just launching it after install gives:
Missing soft dependency:
- GSound not found on the system
-> enables sound notifications when rendering is complete
Traceback (most recent call last):
File
Package: openshot-qt
Version: 2.6.1+dfsg1-1
Severity: grave
I just installed the software, launched "openshot-qt" and got a crash.
I'll put the result of "openshot-qt 2>&1 |tee /tmp/log" at the end of
this mail.
Cheers,
J.Puydt
Here is /tmp/log:
Warning: Ignoring XDG_SESSION_TYPE=wayland on
Package: node-immutable
Version: 4.0.0-2
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, I get the following
failure:
+ NODE_PATH=node_modules:/usr/share/nodejs jest --ci
__tests__/ArraySeq.ts
Error
at Function.missingTransform
Package: node-ignore
Version: 5.2.0-1
Severity: serious
Tags: ftbfs
Building the package in an unstable sbuild, I get:
ERROR: Coverage for lines (92.3%) does not meet global threshold (100%)
ERROR: Coverage for functions (91.66%) does not meet global threshold
(100%)
ERROR: Coverage for branches
Package: node-https-proxy-agent
Version: 5.0.0+~cs8.0.0-3
Severity: serious
Tags: ftbfs
Trying to rebuild the package in an unstable sbuild gives the following
failure in upstream test suite:
1) HttpsProxyAgent
"http" module
should receive the 407 authorization code on the
Package: node-configurable-http-proxy
Version: 4.5.0+~cs15.1.4-3
Severity: serious
Tags: ftbfs
Building the package in an unstable sbuild, I get failures:
Randomized with seed 97263
Started
..F...06:23:50.587 [ConfigProxy]
ESC[31merrorESC[39m: 404 GET /nope
06:23:50.860
Package: node-base64url
Version: 3.0.1-7
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, the upstream test
suite fails because it doesn't find a 100% coverage:
ERROR: Coverage for lines (97.22%) does not meet global threshold
(100%)
ERROR: Coverage for branches
Package: node-config
Version: 3.3.7-1
Severity: serious
Tags: ftbfs
While rebuilding your package with an unstable sbuild, it failed at six
points in the upstream test suite, with the same error:
» An unexpected error was caught: TypeError: Cannot set
property offset of [object Object]
Hi,
I forwarded the bug to
upstream: https://github.com/agronholm/anyio/issues/417
Here is the commit upstream would like feedback about:
https://github.com/agronholm/anyio/commit/184744ca291d426dd278f697c3637623eb9de0ed
Can you check?
Thanks!
J.Puydt
Hi,
Le mercredi 23 février 2022 à 13:21 +0100, Andreas Beckmann a écrit :
> With all these B-D added, the build fails for me now with
>
> Not sure what exactly causes the failure ...
It's an heisenbug:
- I added a patch to get more log ;
- I tried to build the package: success ;
- I tried
Le mercredi 23 février 2022 à 13:21 +0100, Andreas Beckmann a écrit :
> With all these B-D added, the build fails for me now with
>
> Running[3870]: (cd _build/default/doc && /usr/bin/env sphinx-build -q
> -W -b html sphinx refman-html)
> Command [3870] exited with code 2:
> $ (cd
Control: tag -1 pending
Hello,
Bug #1005920 in coq-doc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
I was looking around at all coq-related packages and found this poor
thing, which seems pretty dead.
I propose to ask for its removal ; I'll proceed in a few weeks if
nobody objects.
Cheers,
J.Puydt
Control: tag -1 pending
Hello,
Bug #1005920 in coq-doc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1005852 in ssreflect reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le jeudi 10 février 2022 à 16:20 +0100, Yadd a écrit :
> On 10/02/2022 15:38, Yadd wrote:
> > Package: node-csstype
> > Version: 3.0.10-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > debian/rules launches `ts-node --files build.ts --start` which
> > (only)
> > modifies
Control: tag -1 pending
Hello,
Bug #1005254 in ssreflect reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1003539 in coq-doc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
now camlp5 8.* is in unstable the problem occurs ; I'm just waiting for
the other b-deps to be available, but I have a commit ready.
Cheers,
J.Puydt
Hi,
upstream didn't release a new version with support for camlp5 8.* ; but
they have a patch here:
https://github.com/LPCIC/elpi/pull/110/commits/f58341831b56ccfe5f2f49158c600e4e36bcb9b5
so I should be able to fix the problem as soon as it actually occurs.
Cheers,
J.Puydt
Control: tag -1 pending
Hello,
Bug #1003797 in ssreflect reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1002745 in minetest-mod-protector reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: dh-python
Version: 5.20211217
Severity: grave
python-anyio package is supposedly broken (bug #1002179), but the build
log makes me think it's a problem with dh-python:
>dh_python3 -O--buildsystem=pybuild
> I: dh_python3 pydist:313: Cannot find package that provides
contextvars.
Control: tag -1 pending
Hello,
Bug #1002197 in entrypoints reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1000701 in node-css-tree reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: haxe
Version: 1:4.1.5-1
Severity: grave
I was checking whether a recent dune would break any package, and my
test failed because Base64 was an unbound module -- it's a missing
build-dep on libbase64-ocaml-dev, so it should be pretty
straightforward to fix.
Cheers,
J.Puydt
Package: coq
Version: 8.14.0+dfsg-6
Severity: grave
X-Debbugs-CC: debian-ocaml-ma...@lists.debian.org
Don't migrate to testing until the bytecode architectures' situation is
cleared.
Cheers,
J. Puydt
Package: python3-zmq
Version: 22.3.0-1
Severity: grave
I have issues updating packages nbconvert and jupyterlab-server, both
of which because of autopkgtest failures, with the similar-looking
backtrace:
autopkgtest [08:13:59]: test autodep8-python3: [---
Testing with
Control: tag -1 pending
Hello,
Bug #999651 in coq reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #998712 in irrlicht reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #997206 in irrlicht reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #984238 in minetest reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
I reported upstream, a fix was found -- 2.21.1 should be out in a few
days.
Cheers,
J.Puydt
Hi,
I just tried to rebuild jupyterlab-server in my unstable sbuild, and
could check that it used the jupyter-server you complain about, and
passes the tests.
I suspect the problem is that the latest version of python3-anyio
doesn't migrate to testing (blocked by pytest).
Cheers,
J.Puydt
Hi,
after more poking around, there were two issues:
1) the smaller one was that TypeScript >= 4.4 breaks upstream, but I
could write a patch (and forward it) ;
2) the bigger one is that we need a more recent node-tslib, which is
only in experimental at the moment, so I'm only uploading the
Control: tag -1 pending
Hello,
Bug #994545 in lumino reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
updating to a newer version will probably make that issue go away ; I'm
expecting an answer to https://github.com/jupyterlab/lumino/issues/235
before going forward.
Cheers,
J.Puydt
Hi
Le dim. 12 sept. 2021 à 17:49, Gilles Filippini a écrit :
>
> Patch proposal attached.
>
Excellent! Please commit to salsa but don't upload yet: I have other things
to do (though lacking time I might still end up uploading with only this).
Thanks!
J. Puydt
>
Package: webpack
Version: 5.6.0+~cs6.4.0-1~exp2
Severity: grave
I was trying to update another js-team package and couldn't understand
what was wrong until I tried to just run webpack by itself in another
directory:
$ webpack
[webpack-cli] ReferenceError: options is not defined
at
Control: tag -1 pending
Hello,
Bug #993167 in node-strip-json-comments reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: node-strip-json-comments
Version: 4.0.0-1
Severity: serious
I have to drop dont_be_a_module.patch ; it's too dirty. I'll do it
later today, but still want to prevent any migration to testing.
J.Puydt
Hi,
Le mardi 08 juin 2021 à 14:58 +0200, Jochen Sprickerhof a écrit :
>
> friendly ping on the sagemath issue as it will be dropped from
> testing
> on the 18., otherwise.
> As far as I read there are a number of proposals (downgrade, ignore
> test
> results..) besides fixing the tests. I'm
retitle #986527 Testsuite is too fragile - FTBFS randomly
thanks
Now I get the point and I have to agree ; let me retitle this report so
it states the actual problem.
Cheers,
JP
Control: tag -1 pending
Hello,
Bug #988654 in node-es6-shim reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
Le mardi 18 mai 2021 à 15:31 +0200, Jochen Sprickerhof a écrit :
>
> * Julien Puydt [2021-05-18 07:56]:
> > 1) Upstream itself uses the testsuite in the sense of "shouldn't
> > have
> > too many failing tests", and it still allows to detect when a buil
Hi,
Le lundi 17 mai 2021 à 15:20 +0200, Jochen Sprickerhof a écrit :
> Hi Julien,
>
> * Julien Puydt [2021-05-17 09:01]:
> > I tried to create a testing sbuild and compile sagemath 9.2-2 with
> > it,
> > and it worked so unless I made a mistake in my setup, somethi
Hi,
I tried to create a testing sbuild and compile sagemath 9.2-2 with it,
and it worked so unless I made a mistake in my setup, something made
that bug go away...
Can someone independently give it a try?
JP
Hi,
I had a look:
- sagemath build-depends on cython3
- /usr/bin/cython is in cython
- /usr/bin/cython3 is in cython3
so I see two ways out :
(1) change the b-dep to cython (from cython3) [and cython-dbg from
cython3-dbg, I guess] ;
(2) make so cython is called as cython3.
I can't give it a
Control: tag -1 pending
Hello,
Bug #976778 in fpylll reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #976619 in ts-node reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: python3-pytest
Version: 4.6.11-1
Severity: grave
I was trying to update another package in the Debian Python Team, and
couldn't understand why its testsuite failed with the above error.
After some failed poking around, I put the following in a file named
test_foo.py:
def test_foo():
Hi,
here is the upstream patch fixing the issue :
https://github.com/fplll/fpylll/commit/ede1e459f0662a0940dca6366aba20d47183a4a0
I tought they'd have already released the new version with this in, but
I should have waited until that was done...
And since this patch needs other changes to
Control: tag -1 pending
Hello,
Bug #975241 in terminado reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
please push your commit but don't upload :
- I'll report upstream and forward your patch ;
- I'll take the occasion to do some little things on the package, so
I'll upload when I'll be done (probably before next monday).
Thanks!
JP
Le jeudi 05 novembre 2020 à 19:12 +0100, Bill Allombert a écrit :
> On Mon, Nov 02, 2020 at 09:57:07AM +0100, Bill Allombert wrote:
> > This means 512000 is not sufficient. This is a fatal error.
> > The test cannot pass.
>
> Would you mind uploading giac with PARI_SIZE=1024000 so that we can
>
Package: libpari-dev
Version: 2.13.0-2
Severity: grave
The last pari upload broke giac on amd64, arm64 and mipsel :
https://buildd.debian.org/status/fetch.php?pkg=giac=amd64=1.6.0.25%2Bdfsg1-2%2Bb1=1604135053=0
The failing test on amd64 is a segfault. I could check that running the
failing
Control: tag -1 pending
Hello,
Bug #971108 in python-tornado reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #957229 in freedroidrpg reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
Le mardi 04 août 2020 à 07:49 -0500, Dirk Eddelbuettel a écrit :
> Hi doko and Python folks,
>
> I am lost.
>
I suggest to check the shebangs.
Cheers,
JP
Hi,
I just had a look in d/control, and didn't see where the Python 2 dep
could come from...
If you have a clue, that would help...
JP
Hi
Le dim. 26 juil. 2020 à 20:15, Sandro Tosi a écrit :
> Source: mnemosyne
> Version: 2.7.2+ds1-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
I'll take care of this next week.
Cheers,
JP
>
Hi,
I reported the issue to upstream 11 days ago :
https://github.com/wbhart/flint2/issues/771
JP
Hi,
sorry I didn't find the time to answer faster.
Le mardi 09 juin 2020 à 15:35 -0400, Boyuan Yang a écrit :
> During a local rebuild of your package, it seems that package scilab
> currently FTBFS against new version of libicu library:
>
> ==
> In file included from
Hi,
do you have any reason for not filing a RM bug request to the ftp-
master team?
If it's an old fork with no rdepends, that looks like a good candidate.
Cheers,
JP
Le samedi 23 mai 2020 à 22:37 +0300, Adrian Bunk a écrit :
> On Fri, May 22, 2020 at 04:13:02PM +0200, Julien Puydt wrote:
> > I don't understand why you report a bug on 1.5.0.87+dfsg1-1 on the
> > 20th
> > of may when testing has 1.5.0.87+dfsg1-4 since the 9th of march,
>
Hi,
I don't understand why you report a bug on 1.5.0.87+dfsg1-1 on the 20th
of may when testing has 1.5.0.87+dfsg1-4 since the 9th of march, and
unstable had it since the 4th of march.
Isn't the problem history already?
JP
1 - 100 of 221 matches
Mail list logo
