reassign 1026652 ruby-asciidoctor-pdf 2.3.4-2
affects 1026652 src:nickle
close 1026652 2.3.4-3
reassign 1026700 ruby-asciidoctor-pdf 2.3.4-2
affects 1026700 src:snek
close 1026700 2.3.4-3
thanks
Processing commands for cont...@bugs.debian.org:
> reassign 1026652 ruby-asciidoctor-pdf 2.3.4-2
Bug #1026652 {Done: Keith Packard } [src:nickle] nickle:
FTBFS: make[4]: *** [Makefile:490: nickle-tutorial.pdf] Error 1
Bug reassigned from package 'src:nickle' to 'ruby-asciidoctor-pdf'.
No longer m
close 1026020 0.12.0-2
thanks
Processing commands for cont...@bugs.debian.org:
> close 1026020 0.12.0-2
Bug #1026020 {Done: Sandro Tosi } [ormar] python3-starlette:
starlette.testclient requires module httpx
There is no source info for the package 'ormar' at version '0.12.0-2' with
architecture ''
Unable to make a source ver
Processing commands for cont...@bugs.debian.org:
> # This fix was adopted in Fedora:
> #
> https://src.fedoraproject.org/rpms/python-kafka/c/8c19be70ae51e7?branch=rawhide
> forwarded 1026497 https://github.com/dpkp/kafka-python/pull/2318
Bug #1026497 [src:python-kafka] python-kafka: FTBFS: failed
Your message dated Thu, 29 Dec 2022 07:20:27 +
with message-id
and subject line Bug#1025757: fixed in dyssol 1.1.0+ds1-1
has caused the Debian Bug report #1025757,
regarding dyssol FTBFS with sundials 6.4.1
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> reassign 1026020 ormar 0.12.0-1
Bug #1026020 {Done: Sandro Tosi } [python3-starlette]
python3-starlette: starlette.testclient requires module httpx
Bug reassigned from package 'python3-starlette' to 'ormar'.
No longer marked as found in versions
Processing control commands:
> close -1 6.7.2-1
Bug #1027261 [src:cl-sql] src:cl-sql: fails to migrate to testing for too long:
uploader built arch:all binaries
Marked as fixed in versions cl-sql/6.7.2-1.
Bug #1027261 [src:cl-sql] src:cl-sql: fails to migrate to testing for too long:
uploader bu
Source: cl-sql
Version: 6.7.1-3
Severity: serious
Control: close -1 6.7.2-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 da
Hi.
On Wed, Dec 28, 2022 at 03:21:05PM -0800, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
> > On 2022-08-20, Vagrant Cascadian wrote:
> >> On 2022-08-10, Vagrant Cascadian wrote:
> >>> This bug is just to delay migration to testing while more platforms get
> >>> test
Sadly, my sheevaplug was not revivable. I have a couple of OpenRD boxes and a
couple of CUBox-i boxes I can test for you, as well as a RaspberryPi-4B and a
couple of Orange-Pi boxes that can also be tested. I'll send results as I get
to them.
BTW, are there directions for installing and conf
Here's another Cubox-i. This one's running Bookworm.
shows a surprising number of u-boot-
packages installed, ( = exynos, imx, omap, sunxi) as well as plain
"u-boot". All of them are version 2022.04+dfsg-2+b1.
Rebooting while watching the serial console output says "U-Boot SPL
2016.05-rc2+d
A Cubox-i running Debian bullseye (11.6). According to It
has "u-boot-tools" (version 2021.01+dfsg-5) installed, but none of the
u-boot- packages installed.
If I reboot it and watch the serial console, I see it showing "U-boot
2021.01-dfsg-5" so that version must have gotten into the firmwar
Raspberry Pi 4B (8GB) running bullseye, but does not seem to have any version
of u-boot installed. Weird?
Running tells me that the following (among
lots of others) versions are available. Should I install one of them and see
what happens?
Package u-boot-rpi:
p 2021.01+dfsg-5 stable 500
P
Processing commands for cont...@bugs.debian.org:
> retitle 1026469 metakernel: FTBFS: FAILED
> metakernel/magics/tests/test_parallel_magic.py::test_parallel_magic
Bug #1026469 [src:metakernel] metakernel: FTBFS: mkdir: cannot create directory
‘/<>/.pytest-cache’: File exists
Changed Bug title to
Processing control commands:
> notfound -1 dgit/10.2
Bug #1027186 [dgit] Need to insist on policy query for tainted objects check
Ignoring request to alter found versions of bug #1027186 to the same values
previously set
> fixed -1 dgit/10.2
Bug #1027186 [dgit] Need to insist on policy query for
Control: notfound -1 dgit/10.2
Control: fixed -1 dgit/10.2
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Processing control commands:
> severity -1 serious
Bug #1027186 [dgit] Need to insist on policy query for tainted objects check
Severity set to 'serious' from 'normal'
> found -1 dgit/10.3
Bug #1027186 [dgit] Need to insist on policy query for tainted objects check
The source dgit and version 10.3
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
Your message dated Thu, 29 Dec 2022 00:34:43 +
with message-id
and subject line Bug#1027115: fixed in gobgp 3.9.0-1
has caused the Debian Bug report #1027115,
regarding gobgp: FTBFS: unknown error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 29 Dec 2022 00:34:43 +
with message-id
and subject line Bug#1026137: fixed in gobgp 3.9.0-1
has caused the Debian Bug report #1026137,
regarding gobgp: switch B-D to golang-github-golang-protobuf-1-5-dev
to be marked as done.
This means that you claim that the problem
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On Thursday, 29 December 2022 00:21:05 CET Vagrant Cascadian wrote:
> debian stable (2021.01*), testing (2022.04*), unstable (2022.10*)
> and experimental (2023.01-rc*)
>
> # arm64
> ...
> rock64-rk3328
I don't recall ever having issues with u-boot on my Rock64's, so for me
2022.04 - 2022.10 sure
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
Your message dated Thu, 29 Dec 2022 00:16:10 +0100
with message-id <871qojnmpx@msgid.hilluzination.de>
and subject line Re: Bug#1027119: yara: FTBFS: FAIL: test-magic
has caused the Debian Bug report #1027119,
regarding yara: FTBFS: FAIL: test-magic
to be marked as done.
This means that you cl
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On Fri, 23 Dec 2022 14:53:02 +0100 Fabio Pedretti
wrote:
> Is this still an issue with 22.3.1-1?
If that helps, I have one Intel laptop with Haswell GPU and it works fine
with Mesa 22.3.1
(KDE Plasma).
Shmerl.
On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms get
tested. If you have a relevent board, please con
On 2022-12-22, Vagrant Cascadian wrote:
> On 2022-08-20, Vagrant Cascadian wrote:
>> On 2022-08-10, Vagrant Cascadian wrote:
>>> This bug is just to delay migration to testing while more platforms get
>>> tested. If you have a relevent board, please consider testing and
>>> reporting the status:
>>
Control: reassign 1026705 src:python-kajiki 0.9.1-1
Control: affects 1026705 src:python-pecan
* Lucas Nussbaum [2022-12-20 18:42]:
=== FAILURES ===
___ TestEngines.test_kajiki
s
Processing control commands:
> reassign 1026705 src:python-kajiki 0.9.1-1
Bug #1026705 [src:python-pecan] python-pecan: FTBFS: E AttributeError:
'code' object has no attribute 'co_endlinetable'
Bug reassigned from package 'src:python-pecan' to 'src:python-kajiki'.
No longer marked as found
Processing control commands:
> close -1
Bug #1026523 [src:mir] mir: FTBFS: make[5]: ***
[CMakeFiles/ptest.dir/build.make:73: CMakeFiles/ptest] Error 1
Marked Bug as done
> fixed -1 1.8.2+dfsg-5
Bug #1026523 {Done: Mike Gabriel } [src:mir]
mir: FTBFS: make[5]: *** [CMakeFiles/ptest.dir/build.make
Your message dated Thu, 29 Dec 2022 00:29:02 +0200
with message-id
and subject line Re: Bug#1025063: gnomekiss FTBFS: Makefile:262: *** missing
separator. Stop.
has caused the Debian Bug report #1025063,
regarding gnomekiss FTBFS: Makefile:262: *** missing separator. Stop.
to be marked as done.
Your message dated Wed, 28 Dec 2022 22:20:25 +
with message-id
and subject line Bug#1026675: fixed in jabref 3.8.2+ds-17
has caused the Debian Bug report #1026675,
regarding jabref: FTBFS: make: *** [debian/rules:6: binary] Error 25
to be marked as done.
This means that you claim that the pro
Wow, for once an email from Bugs.Debian mailing list was sorted to the correct
folder!
> We will assist and supply the code to run on your side.
Why not just send off a message to the Konqueror Development lists to pull a
Google on that browser, but, also nail Desktop/device integration?
Kind
Control: tag -1 pending
Hello,
Bug #1026675 in jabref 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:
https://salsa.debian.org/java-team/jabref/-/commit/60c9f47d74f2404009cda98801c24d85
Processing control commands:
> tag -1 pending
Bug #1026675 [src:jabref] jabref: FTBFS: make: *** [debian/rules:6: binary]
Error 25
Added tag(s) pending.
--
1026675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> retitle -1 libapache-poi-java needs updates for newer xmlbeans
Bug #1012016 [libapache-poi-java] libapache-poi-java breaks octave-io
autopkgtest: assert (size (d) == [1001, 2]) failed
Changed Bug title to 'libapache-poi-java needs updates for newer xmlbeans' from
'
Control: retitle -1 libapache-poi-java needs updates for newer xmlbeans
On Fri, 24 Jun 2022 09:54:32 +0200 =?ISO-8859-1?Q?S=E9bastien?= Villemot
wrote:
octave-io’s upstream
thinks that the problem comes from an incorrect combination of versions
between libapache-poi-java and xmlbeans. That see
Hi,
On Thu, 26 May 2022 08:40:07 +0200 Lucas Nussbaum wrote:
Source: libspring-java
Version: 4.3.30-1
During a rebuild of all packages in sid, your package failed to build
on amd64.
This seems related to the new upstream version of xmlbeans earlier this
year. It seems to me that also libs
Hi Ryan,
On Fri, 6 May 2022 13:04:54 -0700 Ryan Tandy wrote:
However I'm not comfortable proposing changes to the script if I can't
validate them.
Then not running the script at all is an improvement over the current
situation. Flaky tests are bad. Until a better solution is found, how
abou
Your message dated Wed, 28 Dec 2022 21:22:21 +
with message-id
and subject line Bug#1026760: fixed in libhttp-daemon-ssl-perl 1.05-01-4
has caused the Debian Bug report #1026760,
regarding libhttp-daemon-ssl-perl: FTBFS: dh_auto_test: error: make -j8 test
TEST_VERBOSE=1 returned exit code 2
t
Processing control commands:
> tags -1 patch pending
Bug #1005628 [src:ruby-turbolinks-source] ruby-turbolinks-source: FTBFS:
installing symlink lib/assets/javascripts/turbolinks.js pointing to parent path
/usr/share/javascript/turbolinks/turbolinks.js ... is not allowed
Added tag(s) patch and p
Control: tags -1 patch pending
On Sun, 13 Feb 2022 09:00:06 +0100 Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build
on amd64.
I have uploaded a workaround to DELAYED/5. The upload is available at
https://salsa.debian.org/ruby-team/ruby-turbolinks-sou
Processing control commands:
> block 1016963 by -1
Bug #1016963 [src:u-boot] u-boot: delay migration to testing to test more
platforms
1016963 was not blocked by any bugs.
1016963 was blocking: 1021559
Added blocking bug(s) of 1016963: 1027176
--
1016963: https://bugs.debian.org/cgi-bin/bugrepo
Processing commands for cont...@bugs.debian.org:
> found 1027166 247.3-7+deb11u1
Bug #1027166 [systemd] rc.local should NOT depend on network-online or anything
else
Marked as found in versions systemd/247.3-7+deb11u1.
> found 1027166 220-4
Bug #1027166 [systemd] rc.local should NOT depend on net
Your message dated Wed, 28 Dec 2022 20:41:30 +
with message-id
and subject line Bug#1027063: fixed in ormar 0.12.0-3
has caused the Debian Bug report #1027063,
regarding python3-ormar uninstallable with current sqlalchemy in unstable
to be marked as done.
This means that you claim that the pr
Your message dated Wed, 28 Dec 2022 20:40:02 +
with message-id
and subject line Bug#1025262: fixed in mir 1.8.2+dfsg-5
has caused the Debian Bug report #1025262,
regarding mir FTBFS, symbols files issues.
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 28 Dec 2022 20:35:55 +
with message-id
and subject line Bug#999143: fixed in dns-browse 1.9-8.2
has caused the Debian Bug report #999143,
regarding dns-browse: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that yo
Your message dated Wed, 28 Dec 2022 20:35:55 +
with message-id
and subject line Bug#965494: fixed in dns-browse 1.9-8.2
has caused the Debian Bug report #965494,
regarding dns-browse: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> retitle 1027143 penimageio: CVE-2022-36354 CVE-2022-38143 CVE-2022-43592
> CVE-2022-43593 CVE-2022-43594 CVE-2022-43595 CVE-2022-43596 CVE-2022-43597
> CVE-2022-43598 CVE-2022-43599 CVE-2022-43600 CVE-2022-43601 CVE-2022-43602
> CVE-2022-41639
Control: tag -1 pending
Hello,
Bug #1026760 in libhttp-daemon-ssl-perl 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:
https://salsa.debian.org/perl-team/modules/packages/libhttp-daemon
Processing control commands:
> tag -1 pending
Bug #1026760 [src:libhttp-daemon-ssl-perl] libhttp-daemon-ssl-perl: FTBFS:
dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) pending.
--
1026760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026760
Debian Bug
Your message dated Wed, 28 Dec 2022 20:22:33 +
with message-id
<20221228202233.horde.wfkzmbb2zd8vcnkyu3ss...@mail.das-netzwerkteam.de>
and subject line Resolved via 1.8.2+dfsg-5
has caused the Debian Bug report #1025262,
regarding mir FTBFS, symbols files issues.
to be marked as done.
This me
Source: ceph
Version: 16.2.10+ds-4
Severity: serious
Justification: Policy 7.2. Binary Dependencies
X-Debbugs-Cc: car...@debian.org
Hi
cephadm and ceph-common use adduser in postinst script but do not
declare a Depends on adduser.
There is as well a respective piuparts report uncovering this, cf
Control: fixed -1 1.8.2+dfsg-5
On Do 01 Dez 2022 18:12:16 CET, Peter Green wrote:
Source: mir
Version: 1.8.2+dfsg-3
Severity: serious
Tags: ftbfs
mir FTBFS on all architectures with symbols files issues
(there was previously a bug report for hppa, but since it now fails
on release
architec
Processing control commands:
> fixed -1 1.8.2+dfsg-5
Bug #1025262 [src:mir] mir FTBFS, symbols files issues.
The source 'mir' and version '1.8.2+dfsg-5' do not appear to match any binary
packages
Marked as fixed in versions mir/1.8.2+dfsg-5.
--
1025262: https://bugs.debian.org/cgi-bin/bugreport
Processing commands for cont...@bugs.debian.org:
> found 1027163 3.1.27-1
Bug #1027163 [src:python-git] python-git: CVE-2022-24439
Ignoring request to alter found versions of bug #1027163 to the same values
previously set
> found 1027163 3.1.14-1
Bug #1027163 [src:python-git] python-git: CVE-2022
Processing commands for cont...@bugs.debian.org:
> found 1027163 3.1.27-1
Bug #1027163 [src:python-git] python-git: CVE-2022-24439
Marked as found in versions python-git/3.1.27-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027163: https://bugs.debian.org/cgi
1 - 100 of 160 matches
Mail list logo