On Fri, Feb 25, 2022 at 12:51:32AM +0100, Agustin Martin wrote:
> El jue, 24 feb 2022 a las 16:09, Lionel Élie Mamane
> () escribió:
> I have been looking at popcons and seems that regarding ispell dicts
> ifrench-gut is way more popular than ifrench, but on the hunspell side
> the winner is
ok,
after a quick look, issue is Logol is compiled against swi-prolog, and
there is an ABI issue I think, getting error:
incompatible version (file: 67, Prolog: 68)]
Recompiling logol in sid against swi-prolog 8.4.2+dfsg-2 results in correct
execution/tests.
So, 2 things:
* As swi-prolog is
control: forcemerge 1005998 1006408
Thanks Paul. It is a regression since 11.3.0. Fixed in git since last week.
Will upload a new version this weekend. This is the fix:
https://salsa.debian.org/reportbug-team/reportbug/-/commit/929c7066747e48daab84abb79d3c385b6632d763
Processing control commands:
> forcemerge 1005998 1006408
Bug #1005998 [reportbug] reportbug: cli version of reportbug crashes with
Python IndexError
Bug #1006408 [reportbug] reportbug: regression: broken lookup of bugs after
filtering for "listbug" but not "bug"
Severity set to 'important'
Your message dated Fri, 25 Feb 2022 04:03:39 +
with message-id
and subject line Bug#889714: fixed in etcd 3.3.25+dfsg-7
has caused the Debian Bug report #889714,
regarding chmod: cannot access '/var/lib/etcd/': No such file or directory
to be marked as done.
This means that you claim that
Package: reportbug
Version: 11.4.0
Severity: serious
If I `reportbug reportbug` then filter by "listbug" then select item 1,
reportbug looks up bug number #1, which it fails to find, instead of
looking up the first bug, which is #786740, which it finds correctly.
If I `reportbug reportbug` then
Processing control commands:
> tag -1 pending
Bug #889714 [etcd-server] chmod: cannot access '/var/lib/etcd/': No such file
or directory
Added tag(s) pending.
--
889714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #889714 in etcd 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 All,
I investigated debbug 1006374 today and found that revision 16603:ba930c1fc380
of graphicsmagick appears to be causing the regression to ruby-mini-magick. A
rebuild of graphicsmagick minus this commit allows ruby-mini-magick to pass
autopkgtest. I did my testing against Ubuntu but
Your message dated Fri, 25 Feb 2022 01:03:49 +
with message-id
and subject line Bug#904742: fixed in jp 0.1.3-3
has caused the Debian Bug report #904742,
regarding jp: name conflict of /usr/bin/jp with sat-xmpp-jp
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 25 Feb 2022 01:03:49 +
with message-id
and subject line Bug#904742: fixed in jp 0.1.3-3
has caused the Debian Bug report #904742,
regarding jp: name conflict of /usr/bin/jp with sat-xmpp-jp
to be marked as done.
This means that you claim that the problem has been
El jue, 24 feb 2022 a las 16:09, Lionel Élie Mamane
() escribió:
>
> On Thu, Feb 24, 2022 at 01:51:58PM +0100, Agustin Martin wrote:
> > On Sat, Feb 19, 2022 at 05:39:28PM +0100, Mattia Rizzolo wrote:
>
> >> Source: ifrench-gut
>
> > * ispell dictionary hash seems to be in bad format,
> > $
Hello, thanks for the bug report!
Le 2022-02-24 à 11 h 10, Paul Gevers a écrit :
Your package has an autopkgtest, great. However, recently it started
failing in testing.
I don't see the problem when I build on my computer, and I don't know
precisely how to fix it, but the problem comes
Your message dated Thu, 24 Feb 2022 21:49:47 +
with message-id
and subject line Bug#1006356: Removed package(s) from unstable
has caused the Debian Bug report #1002942,
regarding FTBFS with ocaml-migrate-parsetree 2.3.0
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 24 Feb 2022 21:48:27 +
with message-id
and subject line Bug#1006355: Removed package(s) from unstable
has caused the Debian Bug report #1002941,
regarding FTBFS with ocaml-migrate-parsetree 2.3.0
to be marked as done.
This means that you claim that the problem has
Hi,
Logol is not maintained for quite a long time now, i will try to have a
look, but i am ok to get logol removed from testing to avoid blocking swi
prolog
Olivier
Le jeu. 24 févr. 2022, 19:36, Paul Gevers a écrit :
> Source: swi-prolog, logol
> Control: found -1 swi-prolog/8.4.2+dfsg-2
>
Am Thu, Feb 24, 2022 at 01:40:51PM +0100 schrieb Andreas Tille:
>
> On the other hand in the current situation with two open RC bugs all
> other packages are broken anyway and will be removed from testing if
> we do not act upon the issue. So may be we should upload to unstable?
I'm tempted to
Processing commands for cont...@bugs.debian.org:
> found 996747 4.11.2
Bug #996747 [src:debianutils] src:debianutils: fails to migrate to testing for
too long: blocked by sramacher
Marked as found in versions debianutils/4.11.2.
> fixed 996747 5.7-0.1
Bug #996747 [src:debianutils]
Hi,
On Wed, Feb 23, 2022 at 07:44:34PM +0100, Jonas Smedegaard wrote:
> Control: reassign -1 src:expat
> Control: found -1 2.2.6-2+deb10u3
> Control: affects -1 biboumi
>
> Quoting Slavko (2022-02-23 18:57:49)
> > Package: biboumi
> > Severity: serious
> > Version: 8.3-1+b1
> >
> > After
Processing commands for cont...@bugs.debian.org:
> reassign 1006333 biboumi 8.3-1
Bug #1006333 [src:expat] biboumi: fail to start after libexpat1 update
Bug reassigned from package 'src:expat' to 'biboumi'.
No longer marked as found in versions expat/2.2.6-2+deb10u3.
Ignoring request to alter
Source: swi-prolog, logol
Control: found -1 swi-prolog/8.4.2+dfsg-2
Control: found -1 logol/1.7.9+dfsg-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of
Processing control commands:
> found -1 swi-prolog/8.4.2+dfsg-2
Bug #1006384 [src:swi-prolog, src:logol] swi-prolog breaks logol autopkgtest:
Program exited with wrong status code
Marked as found in versions swi-prolog/8.4.2+dfsg-2.
> found -1 logol/1.7.9+dfsg-1
Bug #1006384 [src:swi-prolog,
Processing control commands:
> affects -1 src:pygments
Bug #1006383 [src:mercurial] mercurial: autopkgtest needs update for new
version of pygments: output changed
Added indication that 1006383 affects src:pygments
--
1006383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006383
Debian
Source: mercurial
Version: 6.0.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, pygme...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pygments
Dear maintainer(s),
With a recent upload of pygments the
Source: apbs
Version: 3.0.0+dfsg1-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of you package on amd64
because it showed up as regressions (due to
found 1000230 1.0-2
severity 1000230 normal
--
Got it. Thanks anyway, Georges!
Peter
24.02.2022, 16:56, Georges Khaznadar < mailto:georges.khazna...@orange.fr
georges.khazna...@orange.fr >
Thank you for the bug report, Peter. However, I shall not try to fix it
shortly. I suspect that those
Processing commands for cont...@bugs.debian.org:
> found 1000230 1.0-2
Bug #1000230 [screenruler] screenruler fails to start
Marked as found in versions screenruler/1.0-2.
> severity 1000230 normal
Bug #1000230 [screenruler] screenruler fails to start
Severity set to 'normal' from 'grave'
> --
I am not sure what might have changed to cause
ruby-mini-magick/GraphicsMagick not to cooperate. I selected a sample
JPEG file with EXIF information and did some simple tests with latest
GraphicsMagick code:
% gm convert Sunrise.jpg -format '%[EXIF:ExifVersion]' info:-
0221
% gm convert
Your message dated Thu, 24 Feb 2022 17:34:04 +
with message-id
and subject line Bug#1005725: fixed in gavodachs 2.5.3+dfsg-1
has caused the Debian Bug report #1005725,
regarding gavodachs2-server: fails to install with new python3-twisted.
to be marked as done.
This means that you claim that
Package: python3-mistune0
Version: 0.8.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Your message dated Thu, 24 Feb 2022 16:19:29 +
with message-id
and subject line Bug#1006373: fixed in node-winston 3.3.3-7
has caused the Debian Bug report #1006373,
regarding node-winston: autopkgtest regression: Cannot find module
'cross-spawn-async'
to be marked as done.
This means that
Source: r-cran-tidyr, r-cran-emayili
Control: found -1 r-cran-tidyr/1.2.0-1
Control: found -1 r-cran-emayili/0.7.0-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent
Processing control commands:
> found -1 r-cran-tidyr/1.2.0-1
Bug #1006380 [src:r-cran-tidyr, src:r-cran-emayili] r-cran-tidyr breaks
r-cran-emayili autopkgtest: Input must be a vector, not a object.
Marked as found in versions r-cran-tidyr/1.2.0-1.
> found -1 r-cran-emayili/0.7.0-1
Bug #1006380
Source: libssh2
Version: 1.10.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, recently it started
failing in testing.
More information about this bug and the reason for filing it can be found on
Thank you for the bug report, Peter.
However, I shall not try to fix it shortly.
I suspect that those errors are due to some wrong interaction between
Ruby and Gnome libraries at some point, but I did not find enough
information about those "critical" errors when I tried to fix them in
the past.
Control: tag -1 pending
Hello,
Bug #1006373 in node-winston 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:
Processing control commands:
> tag -1 pending
Bug #1006373 [src:node-winston] node-winston: autopkgtest regression: Cannot
find module 'cross-spawn-async'
Added tag(s) pending.
--
1006373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006373
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> reopen 1000230
Bug #1000230 {Done: Georges Khaznadar } [screenruler]
screenruler fails to start
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug
On Thu, Feb 24, 2022 at 01:51:58PM +0100, Agustin Martin wrote:
> On Sat, Feb 19, 2022 at 05:39:28PM +0100, Mattia Rizzolo wrote:
>> Source: ifrench-gut
> * ispell dictionary hash seems to be in bad format,
> $ ispell -l -d francais /usr/share/doc/ifrench-gut/ALIRE
> Illegal format hash
Source: blasr
Version: 5.3.5+dfsg-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of blasr the autopkgtest of blasr fails in testing
when that autopkgtest is run with the binary packages
Processing control commands:
> found -1 graphicsmagick/1.4+really1.3.37+hg16662-1
Bug #1006374 [src:graphicsmagick, src:ruby-mini-magick] graphicsmagick breaks
ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to
eq "0"
Marked as found in versions
Source: node-winston
Version: 3.3.3-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of node-winston the autopkgtest of node-winston
fails in testing when that autopkgtest is run with the
Source: graphicsmagick, ruby-mini-magick
Control: found -1 graphicsmagick/1.4+really1.3.37+hg16662-1
Control: found -1 ruby-mini-magick/4.11.0-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear
Your message dated Thu, 24 Feb 2022 15:11:36 +0100
with message-id
and subject line Re: Bug#998603: weston: FTBFS: ../meson.build:1:0: ERROR:
Unknown options: "simple-dmabuf-drm"
has caused the Debian Bug report #998603,
regarding weston: FTBFS: ../meson.build:1:0: ERROR: Unknown options:
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
reopen 1000230
found 1000230 1.0-2
thanks
--
1.0-2 works now. Thanks a lot!!! However, some error messages emerge.
1. Starting screenruler and switching four times with Alt-Tab between the
screen ruler and the xterm or gnome-terminal from where the screenruler was
started, I see the following
Your message dated Thu, 24 Feb 2022 13:04:53 +
with message-id
and subject line Bug#999121: fixed in syrep 0.9-5
has caused the Debian Bug report #999121,
regarding syrep: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you claim
Your message dated Thu, 24 Feb 2022 13:04:54 +
with message-id
and subject line Bug#1005980: fixed in syrep 0.9-5
has caused the Debian Bug report #1005980,
regarding Please migrate away from dpatch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
On Sat, Feb 19, 2022 at 05:39:28PM +0100, Mattia Rizzolo wrote:
> Source: ifrench-gut
> Version: 1:1.0-32.1
> Severity: serious
>
> Dear maintainer,
>
> we plan to remove src:myspell really soon, and together with it also
> the package "myspell-tools".
> Your package still depends on it.
>
>
On 2/24/22 6:10 PM, Andreas Tille wrote:
Sorry for dragging you into this - the experimental branch was way
advanced which I learned in bug #995675. This leaves the question how
we can proceed. It makes probably sense to run ratt or something like
this to learn about packages that are broken.
Your message dated Thu, 24 Feb 2022 12:50:02 +
with message-id
and subject line Bug#965883: fixed in xdelta3 3.0.11-dfsg-1.1
has caused the Debian Bug report #965883,
regarding xdelta3: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
On 2/24/22 6:00 PM, Nilesh Patra wrote:
One really odd thing I noticed is that there is no dh_auto_build is overridden
but not triggered inside it again,
and so dh_auto_build happening at all.
^
Wow, in a hurry I wrote really sloppy english there
I meant
Hi Nilesh,
Am Thu, Feb 24, 2022 at 06:00:03PM +0530 schrieb Nilesh Patra:
> On 2/24/22 3:36 PM, Andreas Tille wrote:
> > I tried to follow your suggestion to upgrade rdflib to version 6 in Git.
> > Unfortunately I'm stumbling upon a different issue in the new test
> > suite[1].
>
> One really
On 2/24/22 3:36 PM, Andreas Tille wrote:
Please consider releasing rdflib v6 which in my brief testing is
compatible with pyparser v3.
I tried to follow your suggestion to upgrade rdflib to version 6 in Git.
Unfortunately I'm stumbling upon a different issue in the new test
suite[1].
One
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: retitle -1 elixir-lang: flaky autopkgtest: Cannot allocate 512 bytes
of memory (of type "bpd").
Control: severity -1 important
On Fri, Dec 24, 2021 at 07:52:01AM +0100, Paul Gevers wrote:
> Control: found -1 1.12.2.dfsg-2
>
> On Sun, 24 Oct 2021 22:21:31 +0200 Paul Gevers wrote:
> >
Processing control commands:
> retitle -1 elixir-lang: flaky autopkgtest: Cannot allocate 512 bytes of
> memory (of type "bpd").
Bug #997801 [src:elixir-lang] elixir-lang: autopkgtest fails on armhf: Cannot
allocate 512 bytes of memory (of type "bpd").
Changed Bug title to 'elixir-lang: flaky
Quoting Andreas Tille (2022-02-24 11:06:58)
> Control: tags -1 confirmed
> Control: tags -1 help
>
> Hi Jonas,
>
> > Please consider releasing rdflib v6 which in my brief testing is
> > compatible with pyparser v3.
>
> I tried to follow your suggestion to upgrade rdflib to version 6 in Git.
>
Processing control commands:
> tags -1 confirmed
Bug #1005463 [python3-rdflib] python3-rdflib: incompatible with pyparser v3
Added tag(s) confirmed.
> tags -1 help
Bug #1005463 [python3-rdflib] python3-rdflib: incompatible with pyparser v3
Added tag(s) help.
--
1005463:
Control: tags -1 confirmed
Control: tags -1 help
Hi Jonas,
> Please consider releasing rdflib v6 which in my brief testing is
> compatible with pyparser v3.
I tried to follow your suggestion to upgrade rdflib to version 6 in Git.
Unfortunately I'm stumbling upon a different issue in the new
Processing control commands:
> tags -1 confirmed
Bug #1005459 [src:rdflib] rdflib: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) confirmed.
> tags -1 help
Bug #1005459 [src:rdflib] rdflib: FTBFS: dh_auto_test: error:
Processing commands for cont...@bugs.debian.org:
> severity 1005335 serious
Bug #1005335 [eslint] eslint: Please update to
node-regenerate-unicode-properties 10
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1005335:
Package: node-eslint-utils
Version: 2.1.0-3
Severity: serious
Tags: ftbfs patch
Justification: test fails
Hi,
I just released node-dot-prop 7.2.0. API changed. Here is a trivial
patch that fixes test.
Cheers,
Yadd
diff --git a/debian/control b/debian/control
index a1019eb..67aa29f 100644
---
Processing commands for cont...@bugs.debian.org:
> block 1004915 by 1006352
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was blocked by: 1001217 1005426 1005947 1005448 1006286 1006119
1004915 was not blocking any bugs.
Added blocking bug(s) of 1004915: 1006352
> thanks
Hi Nicholas,
Thanks for reaching out.
On 24-02-2022 06:13, Nicholas D Steeves wrote:
Paul and Debian CI team, do you know if a dummy alsa driver (and dummy
sequencer driver) can be enabled on DebCI systems?
You are in control of your testbed, can't you do this in your test? Or
can you only
65 matches
Mail list logo
