ANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libigdgmm12 depends on:
ii libc6 2.33-7
ii libgcc-s1 12-20220319-1
ii libstdc++6 12-20220319-1
libigdgmm12 recommends no packages.
libigdgmm12 suggests no packages.
-- no debconf information
Your message dated Sun, 20 Mar 2022 00:34:01 +
with message-id
and subject line Bug#996098: fixed in libxsmm 1.17-1
has caused the Debian Bug report #996098,
regarding libxsmm: CVE-2021-39535 CVE-2021-39536
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 20 Mar 2022 00:34:01 +
with message-id
and subject line Bug#917526: fixed in libxsmm 1.17-1
has caused the Debian Bug report #917526,
regarding libxsmm: CVE-2018-20541 CVE-2018-20542
to be marked as done.
This means that you claim that the problem has been dealt with.
On vrijdag 18 maart 2022 23:28:33 CET Diederik de Haas wrote:
> And indeed I do not have a /run/samba/ directory on my Bookworm
> system/server.
After I manually created /run/samba/, the installation succeeded.
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 pending
Hello,
Bug #1007929 in netcfg 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 #1007929 [src:netcfg] netcfg: FTBFS on s390x
Ignoring request to alter tags of bug #1007929 to the same tags previously set
--
1007929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007929
Debian Bug Tracking System
Contact
Control: tags -1 + pending
Hello,
Cyril Brulebois, le sam. 19 mars 2022 16:32:06 +0100, a ecrit:
> > Running suite(s): inet_mton
> > 95%: Checks: 24, Failures: 1, Errors: 0
> > test/test_netcfg_gateway_reachable.c:94:F:netcfg_gateway_reachable:test_netcfg_gateway_reachable_v6_fe80:0:
> >
Processing control commands:
> tags -1 + pending
Bug #1007929 [src:netcfg] netcfg: FTBFS on s390x
Added tag(s) pending.
--
1007929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
We are in the process of updating all the packages that use lttoolbox, so
this is fully expected.
-- Tino Didriksen
On Sat, 19 Mar 2022 at 23:03, Sebastian Ramacher
wrote:
> Source: apertium-lex-tools
> Version: 0.2.7-1
> Severity: serious
> Tags: ftbfs sid bookworm
> X-Debbugs-Cc:
In my opinion, this issue could be closed.
These are reasons.
1) It is not wpa_supplicant issue but AP issue.
2) Users affected by this issue have some workarounds.
Details of the 1)
The investigation has revealed that the AP is in violation of "2.3
WPA3-Personal transition mode" of the "WPA3
Am 19.03.22 um 22:30 schrieb Andrej Shadura:
Hi,
Michael, Masashi, what’s your opinion, what should I do as the maintainer of
wpa in Debian?
I can still reproduce the problem.
If more debugging is needed, please let me know. I'll try to help as
much as I can.
Michael
OpenPGP_signature
On Sat, Mar 19, 2022 at 10:37 PM Rebecca N. Palmer
wrote:
>
> Control: reassign -1 python3-nbclient, src:theano
> Control: tags -1 patch
>
> This looks like a missing dependency on python3-ipython-genutils, though
> I haven't actually tested adding that. (That package was installed when
>
Source: apertium-lex-tools
Version: 0.2.7-1
Severity: serious
Tags: ftbfs sid bookworm
X-Debbugs-Cc: sramac...@debian.org
g++ -DPACKAGE_NAME=\"apertium-lex-tools\"
-DPACKAGE_TARNAME=\"apertium-lex-tools\" -DPACKAGE_VERSION=\"0.2.7\"
-DPACKAGE_STRING=\"apertium-lex-tools\ 0.2.7\"
Processing control commands:
> reassign -1 python3-nbclient, src:theano
Bug #1007890 [src:theano] FTBFS: No module named 'ipython_genutils'
Bug reassigned from package 'src:theano' to 'python3-nbclient,src:theano'.
No longer marked as found in versions theano/1.0.5+dfsg-4.
Ignoring request to
Processing control commands:
> found -1 node-puppeteer/13.1.0+dfsg-6
Bug #1007983 [src:node-puppeteer] node-puppeteer: broken autopkgtest keeping
chromium from migrating to testing
Marked as found in versions node-puppeteer/13.1.0+dfsg-6.
> affects -1 chromium
Bug #1007983 [src:node-puppeteer]
Source: node-puppeteer
Control: found -1 node-puppeteer/13.1.0+dfsg-6
Control: affects -1 chromium
Severity: serious
Tags: sid bookworm
node-puppeteer is keeping chromium from migrating; as
https://tracker.debian.org/pkg/chromium describes,
"Issues preventing migration:
∙ ∙ autopkgtest for
Hi,
Michael, Masashi, what’s your opinion, what should I do as the maintainer of
wpa in Debian?
--
Cheers,
Andrej
Processing control commands:
> close -1 1:2.22.1-1
Bug #1007980 [src:flint-arb] src:flint-arb: fails to migrate to testing for too
long: FTBFS on mips64el
Marked as fixed in versions flint-arb/1:2.22.1-1.
Bug #1007980 [src:flint-arb] src:flint-arb: fails to migrate to testing for too
long:
Source: flint-arb
Version: 1:2.21.1-2
Severity: serious
Control: close -1 1:2.22.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1006779
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
Processing control commands:
> close -1 2:2.10-2
Bug #1007979 [src:wpa] src:wpa: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions wpa/2:2.10-2.
Bug #1007979 [src:wpa] src:wpa: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
>
Source: wpa
Version: 2:2.9.0-23
Severity: serious
Control: close -1 2:2.10-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1003907
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Package: android-platform-system-core
Version: 1:10.0.0+r36-9
Severity: serious
The android-platform-system-core source package builds the adb and fastboot
binary packages which are also built (with a higher version number) by
android-platform-tools, I belive this is what lead to the rejection
Source: polyml
Version: 5.7.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, somewhere between 05
July 2021 and 12 July 2021 it regressed in testing on amd64 [1]
I copied some of the output of a
Processing commands for cont...@bugs.debian.org:
> reassign 1007739 src:curl 7.82.0-1
Bug #1007739 {Done: Samuel Henrique } [src:curl,
src:stenographer] curl breaks stenographer autopkgtest: curl: (27) Out of memory
Bug reassigned from package 'src:curl, src:stenographer' to 'src:curl'.
No
Hi,
On 19-03-2022 14:48, Nilesh Patra wrote:
For avoidance of doubt, the canonical definition lives in the autopkgtest
package:
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst
I usually refer /usr/share/doc/autopkgtest/README.package-tests.rst.gz in
Processing commands for cont...@bugs.debian.org:
> tags 1005981 + pending
Bug #1005981 [src:redet] Please migrate away from dpatch
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1005981:
Hello,
On Thu, 10 Mar 2022 07:55:19 +0100 Julien Puydt wrote:
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
sadly,
Hi Paul,
Paul Gevers (2022-03-18):
> Source: netcfg
> Version: 1.177
> Severity: serious
> Tags: ftbfs
Thanks for the report.
> Dear maintainer,
>
> Your package failed to migrate for 60 days, hence I spotted it. It
> fails to build from source on s390x. I hit the giveback button once
>
Processing commands for cont...@bugs.debian.org:
> found 1005473 7
Bug #1005473 [src:gcc-11-cross-ports] gcc-11-cross-ports: FTBFS:
s-tsmona.adb:160: undefined reference to `dladdr'
Marked as found in versions gcc-11-cross-ports/7.
> thanks
Stopping processing here.
Please contact me if you
Hi!
Thanks for looking into this. Can you elaborate why you filed this on
26.4.8 and not latest 26.4.10?
Builds are passing. Thus tests indicate that there is no issue. What is the
broken thing exactly and since tests are passing, how will we verify that
the broken thing is fixed or still
Source: sslsplit
Version: 0.5.0+dfsg-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=sslsplit=amd64=0.5.5-2=1640486198=0
...
Running suite(s):
main
opts
Cannot resolve address '127.0.0.1' port '10443': Name or service not known
Cannot resolve address '127.0.0.1'
Your message dated Sat, 19 Mar 2022 14:49:48 +
with message-id
and subject line Bug#1007739: fixed in curl 7.82.0-2
has caused the Debian Bug report #1007739,
regarding curl breaks stenographer autopkgtest: curl: (27) Out of memory
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Mar 2022 14:49:48 +
with message-id
and subject line Bug#1007740: fixed in curl 7.82.0-2
has caused the Debian Bug report #1007740,
regarding curl breaks xmltooling autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hello,
I've uploaded 7.82.0-2 with upstream's patch, hopefully fixing these issues.
Thank you to everyone who helped!
--
Samuel Henrique
On Sat, Mar 19, 2022 at 02:32:12PM +0100, Paul Gevers wrote:
> > [1] https://people.debian.org/~eriberto/README.package-tests.html
>
> For avoidance of doubt, the canonical definition lives in the autopkgtest
> package:
>
Processing commands for cont...@bugs.debian.org:
> reassign 1007823 src:dune-common 2.8.0-3
Bug #1007823 {Done: Drew Parsons } [src:scotch,
src:opm-grid] scotch breaks opm-grid autopkgtest: Failed to build
dune-autopkgtest
Bug reassigned from package 'src:scotch, src:opm-grid' to
Hi,
On 19-03-2022 09:26, Sascha Steinbiss wrote:
Would it be possible to add a hint to ignore arm64 autopkgtest suite?
BTW I think this is possible already in the autopkgtest definition [1] by
adding an Architecture: section and leaving out arm64 in the list of archs you
list in there — if
Your message dated Sat, 19 Mar 2022 13:03:56 +
with message-id
and subject line Bug#1007823: fixed in dune-common 2.8.0-4
has caused the Debian Bug report #1007823,
regarding scotch breaks opm-grid autopkgtest: Failed to build dune-autopkgtest
to be marked as done.
This means that you claim
Your message dated Sat, 19 Mar 2022 11:47:18 +
with message-id
and subject line Bug#993578: fixed in gnupg2 2.2.27-2+deb11u1
has caused the Debian Bug report #993578,
regarding 90gpg-agent generator: `gpgconf --check-programs` can hang
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Mar 2022 11:47:19 +
with message-id
and subject line Bug#992065: fixed in mpich 3.4.1-5~deb11u1
has caused the Debian Bug report #992065,
regarding mpich: libhdf5-mpich-dev upgrade problems if libmpich1.0-dev is still
installed
to be marked as done.
This means
Your message dated Sat, 19 Mar 2022 11:34:01 +
with message-id
and subject line Bug#1003801: fixed in why3 1.4.1-1
has caused the Debian Bug report #1003801,
regarding why3 FTBFS: Error: File graph.cmo not found
to be marked as done.
This means that you claim that the problem has been dealt
Source: galera-4
Version: 26.4.8-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=galera-4=amd64
https://buildd.debian.org/status/logs.php?pkg=galera-4=armel
https://buildd.debian.org/status/logs.php?pkg=galera-4=i386
...
Running suite(s): gu::asio
terminate called
Your message dated Sat, 19 Mar 2022 10:02:09 +
with message-id
and subject line Bug#998008: fixed in glibc 2.31-13+deb11u3
has caused the Debian Bug report #998008,
regarding libc-bin: postinst makes a working NIS system not to work anymore at
every point release
to be marked as done.
This
Your message dated Sat, 19 Mar 2022 10:02:08 +
with message-id
and subject line Bug#996807: fixed in djbdns 1:1.05-13+deb11u1
has caused the Debian Bug report #996807,
regarding tinydns stops replying to queries after a few hours
to be marked as done.
This means that you claim that the
Your message dated Sat, 19 Mar 2022 10:02:09 +
with message-id
and subject line Bug#1001610: fixed in gbonds 2.0.3-16+deb11u1
has caused the Debian Bug report #1001610,
regarding GBonds Unable to Update Redemption Tables
to be marked as done.
This means that you claim that the problem has
Control: tags 978882 + patch
Control: tags 978882 + pending
Dear maintainer,
I've prepared an NMU for pike8.0 (versioned as 8.0.1116-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru pike8.0-8.0.1116/debian/changelog
Processing control commands:
> tags 978882 + patch
Bug #978882 [src:pike8.0] pike8.0: ftbfs with autoconf 2.70
Added tag(s) patch.
> tags 978882 + pending
Bug #978882 [src:pike8.0] pike8.0: ftbfs with autoconf 2.70
Added tag(s) pending.
--
978882:
On 19 March 2022 1:56:17 pm IST, Sascha Steinbiss wrote:
>Hi Nilesh,
>
>[…]
>> Would it be possible to add a hint to ignore arm64 autopkgtest suite?
>
>BTW I think this is possible already in the autopkgtest definition [1] by
>adding an Architecture: section and leaving out arm64 in the list
Your message dated Sat, 19 Mar 2022 11:15:12 +0200
with message-id <20220319091512.GI4190@localhost>
and subject line Fixed in 1:1.48.0-2
has caused the Debian Bug report #1004562,
regarding libguestfs: autopkgtest regression
to be marked as done.
This means that you claim that the problem has
Hi Nilesh,
[…]
> Would it be possible to add a hint to ignore arm64 autopkgtest suite?
BTW I think this is possible already in the autopkgtest definition [1] by
adding an Architecture: section and leaving out arm64 in the list of archs you
list in there — if that is what you mean.
Cheers
Processing commands for cont...@bugs.debian.org:
> block 1005747 with 1007013
Bug #1005747 {Done: Steffen Moeller } [src:freecad]
freecad: CVE-2021-45844 - Improper sanitization in the invocation of ODA File
Converter
1005747 was not blocked by any bugs.
1005747 was not blocking any bugs.
Added
51 matches
Mail list logo
