Processing control commands:
> reopen -1
Bug #993323 {Done: Florian Schlichting }
[src:libmath-gsl-perl] libmath-gsl-perl: FTBFS: Unsupported GSL version!!! : 2.7
'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-ad
Control: reopen -1
On Sun, Sep 19, 2021 at 05:09:03PM +, Debian Bug Tracking System wrote:
>...
> libmath-gsl-perl (0.43-1) unstable; urgency=medium
>...
>* Import upstream version 0.43 (closes: #993323)
>...
> Checking if x86_64-linux-gnu-gcc supports "-g"...Unsupported GSL version!!!
Processing commands for cont...@bugs.debian.org:
> tags 996756 + sid bookworm
Bug #996756 [src:golang-github-marten-seemann-qtls-go1-15]
golang-github-marten-seemann-qtls-go1-15: FTBFS with golang/1.17: panic:
qtls.ClientHelloInfo doesn't match
Added tag(s) sid and bookworm.
> tags 996757 + sid
Hello, Sean-san
Thank you for your NMU.
I confirmed your patch. This works fine.
Thank you.
--
Regards,
Hajime MIZUNO
Package: tinydns
Version: 1:1.05-13
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU
Processing commands for cont...@bugs.debian.org:
> reassign 996806 mailman3
Bug #996806 [mailman3] mailmain3: Expected test results for arc_validate tests
need updating
Ignoring request to reassign bug #996806 to the same package
> thanks
Stopping processing here.
Please contact me if you need a
Processing control commands:
> reassign -1 mailman3 3.3.3-1
Bug #996806 [mailmain3] mailmain3: Expected test results for arc_validate tests
need updating
Warning: Unknown package 'mailmain3'
Bug reassigned from package 'mailmain3' to 'mailman3'.
No longer marked as found in versions 3.3.3-1.
Igno
Control: reassign -1 mailman3 3.3.3-1
On Ma, 19 oct 21, 01:10:28, Scott Kitterman wrote:
> Package: mailmain3
> Version: 3.3.3-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> mailman3 now fails tests with authheaders 0.14.1
Package: mailmain3
Version: 3.3.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
mailman3 now fails tests with authheaders 0.14.1 since support for
comments in ARC results was added. Although this isn't precisely an
FTBFS, a autopkgt
Your message dated Tue, 19 Oct 2021 02:35:43 +
with message-id
and subject line Bug#996583: fixed in xir 1.4-1
has caused the Debian Bug report #996583,
regarding xir FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 19 Oct 2021 02:35:35 +
with message-id
and subject line Bug#996583: fixed in xir 1.3.2-2
has caused the Debian Bug report #996583,
regarding xir FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is no
Hello Francisco, hello Albert,
this might be the same as in bug #996726
and not directly related to the nvidia driver.
I hit a crash in kwin_x11 with an AMD graphics card
and could workaround by installing
libkdecorations2-5v5_5.21.5-2_amd64.deb like
mentioned in #996726.
Kind regards,
Bernhard
Howdy,
Debian Bug Tracking System, on 2021-10-18:
> Processing control commands:
>
> > tag -1 pending
> Bug #983981 [src:bamtools] bamtools: ftbfs with GCC-11
> Ignoring request to alter tags of bug #983981 to the same tags previously set
Hmm, scratch that, I didn't realize initially that the bu
Your message dated Mon, 18 Oct 2021 22:33:32 +
with message-id
and subject line Bug#994697: fixed in git-annex 8.20211011-2
has caused the Debian Bug report #994697,
regarding libgit-annex-perl: Test failure - autopkgtest and build
to be marked as done.
This means that you claim that the prob
Thank you, Patrick and Bernhard; downgrading worked for me as well.
Very much appreciated.
On Mon, Oct 18, 2021 at 11:24 PM Francisco José Calvo wrote:
>
> Hello Bernhard, yes it is same issue mentioned in #996726, not related to
> nvidia-driver.
>
> Thanks a lot.
>
> El lun., 18 oct. 2021 23:16
Processing control commands:
> tags 995968 + patch
Bug #995968 [gkrellm-leds] gkrellm-leds: This gkrellm plugin does not start,
Error: undefined symbol: XTestFakeKeyEvent
Added tag(s) patch.
> tags 995968 + pending
Bug #995968 [gkrellm-leds] gkrellm-leds: This gkrellm plugin does not start,
Erro
Control: tags 995968 + patch
Control: tags 995968 + pending
Renzo Davoli wrote...
> Bugfix: add --no-as-needed linker option.
Thanks for spotting this and providing a fix.
Dear maintainer,
to resolve this issue, I've prepared a NMU for gkrellm-leds
(versioned as 0.8.0-1.4), upload to DELAYED/
Your message dated Mon, 18 Oct 2021 21:48:55 +
with message-id
and subject line Bug#984045: fixed in dymo-cups-drivers 1.4.0-11
has caused the Debian Bug report #984045,
regarding dymo-cups-drivers: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been de
Source: llvm-toolchain-12
Version: 1:12.0.1-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The restructuring in 1:12.0.1-10 seems to have caused a regression on s390x:
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-12
Processing control commands:
> severity -1 important
Bug #996778 [xymon-client] xymon-client: Disable by default the ability of
logfetch to execute arbitrary code fetched from the Xymon server
Severity set to 'important' from 'grave'
--
996778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Control: severity -1 important
Hi,
Christoph Berg wrote:
> Re: Axel Beckert
> > "critical" is indeed clearly wrong. I'd have rather said "important"
> > only as the claim of being a "root hole" is wrong. But ok.
>
> I only moved it off "critical" which it really is not. If you think
> important
Package: db2twitter
Version: 0.6-1.1
Severity: grave
Tag: patch
Dear maintainer,
db2twitter has become unusable with the new python3-tweepy package
because of an backwards-incompatible API changes in version 4.
I think you'll need to remove the wait_on_rate_limit_notify=True
parameter from the t
Package: retweet
Version: 0.10-1.1
Severity: grave
Tag: patch
Dear maintainer,
retweet has become unusable with the new python3-tweepy package
because of an backwards-incompatible API changes in version 4.
AFAICT you merely need to remove the wait_on_rate_limit_notify=True
parameter from main.py
Hello Bernhard, yes it is same issue mentioned in #996726, not related to
nvidia-driver.
Thanks a lot.
El lun., 18 oct. 2021 23:16, Bernhard Übelacker
escribió:
> Hello Francisco, hello Albert,
> this might be the same as in bug #996726
> and not directly related to the nvidia driver.
>
> I hit
Package: twitterwatch
Version: 0.1-2
Severity: grave
Tag: patch
X-Debbugs-Cc: Boyuan Yang
Dear maintainer,
twitterwatch has become unusable with the new python3-tweepy package
because of backwards-incompatible API changes in version 4.
Attached is an (untested) patch that should make the packag
On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote:
> On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote:
> > Hi,
> >
> > I think the following change might be the relevant one:
> >
> > --- a/update-ca-certificates
> > +++ b/update-ca-certificates
> > @@ -164,8 +
Thank you so much Patrick, yes I'm using testing.
I downgraded libkdecorations2-5v5 and now it works fine.
Kind regards.
On Mon, 18 Oct 2021 22:45:17 +0200 Patrick Franz
wrote:
> Hi,
>
> I assume you're using testing. Unfortunately, Plasma is broken in
> testing at the moment if you have upgr
Source: llvm-toolchain-12
Version: 1:12.0.1-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The restructuring in 1:12.0.1-10 seems to have caused a build regression
on mipsel, which I'm reporting as separate from #996796 because it
do
Processing control commands:
> retitle -1 llvm-toolchain-12: FTBFS on i386|mipsel|powerpc since 1:12.0.1-10:
> undefined reference to `__udivdi3'
Bug #996796 [src:llvm-toolchain-12] llvm-toolchain-12: FTBFS on i386 since
1:12.0.1-10: undefined reference to `__udivdi3'
Changed Bug title to 'llvm-
Control: retitle -1 llvm-toolchain-12: FTBFS on i386|mipsel|powerpc since
1:12.0.1-10: undefined reference to `__udivdi3'
On Mon, 18 Oct 2021 at 21:40:33 +0100, Simon McVittie wrote:
> The restructuring in 1:12.0.1-10 seem to have triggered a FTBFS on i386
...
> Utility.h:56 is dividing a uint64_
Control: tags 996795 + patch
Control: tags 996795 + pending
Dear maintainer,
I've prepared an NMU for silversearcher-ag-el (versioned as 0.48-1.1)
and uploaded it to DELAYED/5. Please feel free to tell me if I should
delay it longer.
Regards.
--
Sean Whitton
diff -Nru silversearcher-ag-el-0.4
Processing control commands:
> tags 996795 + patch
Bug #996795 [elpa-ag] silversearcher-ag-el: should drop dependencies on
elpa-dash-functional
Added tag(s) patch.
> tags 996795 + pending
Bug #996795 [elpa-ag] silversearcher-ag-el: should drop dependencies on
elpa-dash-functional
Added tag(s) pe
Hi,
I assume you're using testing. Unfortunately, Plasma is broken in
testing at the moment if you have upgraded libkdecorations2-5v5 to 5.23.
Could you check that ?
If this is the case, I wrote about a possible solution here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726#10
--
Me
Le lun. 18 oct. 2021 à 22:12, Jérémy Lal a écrit :
> Le lun. 18 oct. 2021 à 16:48, Oliver Schode a
> écrit :
>
> > Package: luarocks
> > Version: 3.7.0+dfsg1-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > Hi,
> >
> > thanks for reviving the package. Now I'm getting thi
Source: llvm-toolchain-12
Version: 1:12.0.1-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The restructuring in 1:12.0.1-10 seem to have triggered a FTBFS on i386,
which breaks multi-arch coinstallability with amd64:
> [1385/1405] :
Hi,
On 18/10/2021 21:55, Axel Beckert wrote:
Hi again,
Christoph Zechner wrote:
Severity: critical
This is clearly not "critical". Myon already fixed that.
Apologies for that, I was not sure how to classify it, but since it was
a security-related issue, I thought it was appropriate.
On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote:
> Hi,
>
> I think the following change might be the relevant one:
>
> --- a/update-ca-certificates
> +++ b/update-ca-certificates
> @@ -164,8 +164,6 @@
>done
> fi
>
> -rm -f "$CERTBUNDLE"
> -
> AD
Hi,
yes, I confirm sobre behaviour as Albert, other environments are working
with no issues, such as LXDE or xfce...but KDE/Plasma available in testing
is currently unusable with latest nvidia-driver.
Thanks.
On Mon, 18 Oct 2021 21:57:43 +0200 Albert Netymk
wrote:
> I had the same problem as F
Le lun. 18 oct. 2021 à 16:48, Oliver Schode a
écrit :
> Package: luarocks
> Version: 3.7.0+dfsg1-1
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> thanks for reviving the package. Now I'm getting this when attempting to
> install however:
>
> Error: Cannot access repos
Re: Axel Beckert
> "critical" is indeed clearly wrong. I'd have rather said "important"
> only as the claim of being a "root hole" is wrong. But ok.
I only moved it off "critical" which it really is not. If you think
important (or wishlist?) makes more sense, go ahead.
> I'm though not sure if th
Hi Christoph,
I admittedly just noticed the severity which the bug reporter set when
seeing this mail:
Debian Bug Tracking System wrote:
> > severity 996778 grave
> Bug #996778 [xymon-client] xymon-client: disable logfetch's ability to
> execute arbitrary code
> Severity set to 'grave' from 'cri
I had the same problem as Francisco reported.
My Nvidia card is NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
kwin-x11: 4:5.21.5-2
nvidia-driver: 470.74-1
linux-image-amd64: 5.14.9-2
I tried to downgrade nvidia-driver, but had problems while installing
the package from stable release, so I w
Hi again,
Christoph Zechner wrote:
> Severity: critical
This is clearly not "critical". Myon already fixed that.
> Justification: root security hole
It is also no root security hole. It gives you access to the xymon
user only. (If the admin configured the xymon user to be able to use
sudo, that
Your message dated Mon, 18 Oct 2021 19:50:07 +
with message-id
and subject line Bug#996561: fixed in qepcad 1.74+ds-3
has caused the Debian Bug report #996561,
regarding qepcad fails autopkgtests on !amd64, !i386
to be marked as done.
This means that you claim that the problem has been dealt
Package: elpa-ag
Version: 0.48-1
Severity: serious
Justification: not installable in sid due to package removal
Hello,
Per [1] dash-functional.el is obsolete and elpa-dash-functional has been
removed from unstable. It should be sufficient simply to patch out any
`require' calls or similar and re
Re: Axel Beckert
> > LOGFETCHOPTS="--noexec"
> >
> > instead.
>
> Hrm. The Debian package for sure will switch that option if upstream
> does.
>
> I'm though currently a bit reluctant to apply this patch and deviate
> from upstream's defaults (even more) since the default settings with
> IP addr
Hi,
I missed this bug report.
I don't have any idea why the tests were failing on a large machine.
I've been building and running the autopkgtests for dask.distributed my
laptop with 2 cores & 16GB of RAM, and it' hasn't hung for me.
I also glanced at the current CI build results and all the ru
Processing control commands:
> retitle -1 xymon-client: Disable by default the ability of logfetch to
> execute arbitrary code fetched from the Xymon server
Bug #996778 [xymon-client] xymon-client: disable logfetch's ability to execute
arbitrary code
Changed Bug title to 'xymon-client: Disable b
Processing control commands:
> tags -1 pending
Bug #996561 [qepcad] qepcad fails autopkgtests on !amd64, !i386
Added tag(s) pending.
--
996561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: retitle -1 xymon-client: Disable by default the ability of logfetch to
execute arbitrary code fetched from the Xymon server
Control: forwarded -1 https://lists.xymon.com/archive/2021-October/047749.html
Control: tag -1 + upstream confirmed
Hi,
Christoph Zechner wrote:
> Package: xymon-c
Control: tags -1 pending
On Fri 15 Oct 2021 01:52:37 PM EDT, Doug Torrance
wrote:
On Fri 15 Oct 2021 10:29:40 AM EDT, Nilesh Patra wrote:
qepcad fails its autopkgtests on every non-x86 arch as seen here.
Can you fix this?
I confirmed that QEPCAD isn't functioning for me locally on an armhf
Processing control commands:
> tag -1 pending
Bug #983981 [src:bamtools] bamtools: ftbfs with GCC-11
Ignoring request to alter tags of bug #983981 to the same tags previously set
--
983981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983981
Debian Bug Tracking System
Contact ow...@bugs.deb
Control: tag -1 pending
Hello,
Bug #983981 in bamtools 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/med-team/bamtools/-/commit/798f6d312609f68af08dfd32e827d0
Chris,
On Mon, Oct 18, 2021 at 03:17:14PM +0200, Chris Hofstaedtler wrote:
> Could you add your Signed-off-by: to the patch, so I can forward it
> upstream? (Or you could send it to util-li...@vger.kernel.org
> directly, too.)
Yes, of course. Attached. I'll leave you to send it upstream, so every
Are these files with global writable permissions perhaps being installed by
the postinst script?
It's not immediately obvious to me where they've come from.
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:fityk
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setti
Your message dated Mon, 18 Oct 2021 17:03:30 +
with message-id
and subject line Bug#996636: fixed in trafficserver 9.1.0+ds-2
has caused the Debian Bug report #996636,
regarding trafficserver FTBFS on 32bit
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 18 Oct 2021 16:48:37 +
with message-id
and subject line Bug#992696: fixed in 389-ds-base 1.4.4.17-1
has caused the Debian Bug report #992696,
regarding 389-ds: 389-DS no longer starts since bullseye due to
libjemalloc.so.2 not found
to be marked as done.
This means th
Your message dated Mon, 18 Oct 2021 16:18:46 +
with message-id
and subject line Bug#996551: fixed in llvm-toolchain-13 1:13.0.0-6
has caused the Debian Bug report #996551,
regarding llvm-13-dev: Missing dependency to libomp-13-dev
to be marked as done.
This means that you claim that the probl
Your message dated Mon, 18 Oct 2021 16:18:46 +
with message-id
and subject line Bug#996551: fixed in llvm-toolchain-13 1:13.0.0-6
has caused the Debian Bug report #996551,
regarding llvm-toolchain-13: autopkgtest failure
to be marked as done.
This means that you claim that the problem has bee
Processing commands for cont...@bugs.debian.org:
> severity 996487 serious
Bug #996487 [nbd-client] nbd-client: connects to localhost instead of the
requested server
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996487
Processing commands for cont...@bugs.debian.org:
> tags 996487 + upstream fixed-upstream
Bug #996487 [nbd-client] nbd-client: connects to localhost instead of the
requested server
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.
Please contact me if you need assistanc
close 996724 3.0.2-5
thanks
Processing commands for cont...@bugs.debian.org:
> close 996724 3.0.2-5
Bug #996724 [src:ruby3.0] ruby3.0: FTBFS on ppc64el: Segmentation fault
Marked as fixed in versions ruby3.0/3.0.2-5.
Bug #996724 [src:ruby3.0] ruby3.0: FTBFS on ppc64el: Segmentation fault
Marked Bug as done
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> severity 981525 grave
Bug #981525 {Done: Hubert Chathi } [nheko] nheko login
crashes client, can't be used, in urgent need of a version update
Severity set to 'grave' from 'normal'
>
End of message, stopping processing here.
Please contact me if
Package: luarocks
Version: 3.7.0+dfsg1-1
Severity: grave
Justification: renders package unusable
Hi,
thanks for reviving the package. Now I'm getting this when attempting to
install however:
Error: Cannot access repository at /root/.luarocks/lib/luarocks/rocks-5.3
dpkg: error processing
Paul, what do you think about Peter's propositoins ?
thanks
S
Le 01/10/2021 à 00:07, peter green a écrit :
>> It passes when run with only packages from testing.
>
> This is not entirely correct, the version of rust-utf-8 in testing
> has no autopkgtests at all. So this is a case of a newly adde
Package: gnome-boxes
Version: 41.1-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: isingasimples...@gmail.com
i use gnome-boxes to run a simple windows 10 session since a few months. i
updated my system from stable to testing last week, and now my system
freeze each time
Processing commands for cont...@bugs.debian.org:
> severity 996778 grave
Bug #996778 [xymon-client] xymon-client: disable logfetch's ability to execute
arbitrary code
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996778:
Package: xymon-client
Severity: critical
Tags: patch security
Justification: root security hole
X-Debbugs-Cc: zech...@vrvis.at, Debian Security Team
The default for logfetch's options (found in /etc/xymon/xymonclient.cfg) is:
LOGFETCHOPTS=""
which enables it to execute arbitrary code [1]. Th
Your message dated Mon, 18 Oct 2021 13:48:33 +
with message-id
and subject line Bug#996060: fixed in gnome-shell-extension-hamster
0.10.0+git20210628-2
has caused the Debian Bug report #996060,
regarding gnome-shell-extension-hamster: does not declare compatibility with
GNOME Shell 41
to be
Hi Raphael,
> Sorry that logidee-tools created issues for you. For the record, I have
Not really issues, therion took longer to get fixed ;-)
And it was quite interesting to find out what was the real problem.
> just requested the removal of that package since I'm no longer using
> it and in fac
Hello,
On Fri, 01 Oct 2021, Norbert Preining wrote:
> The failed autopkgtest can be boiled down to the following example (all
> the code is as taken from the logidee-tools generated code):
Sorry that logidee-tools created issues for you. For the record, I have
just requested the removal of that p
Control: tag -1 pending
Hello,
Bug #996060 in gnome-shell-extension-hamster 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/projecthamster-team/gnome-shell-ext
Processing control commands:
> tag -1 pending
Bug #996060 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: does
not declare compatibility with GNOME Shell 41
Added tag(s) pending.
--
996060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996060
Debian Bug Tracking System
Contac
Processing control commands:
> found -1 2.37.2-1
Bug #996764 [util-linux] FTBFS: test misc/swaplabel failure
Marked as found in versions util-linux/2.37.2-1.
--
996764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: found -1 2.37.2-1
Hello Mark,
* Mark Hindley [211018 12:33]:
[..]
> Whilst building a local version of util-linux 2.37.2-3, the misc/swaplabel
> test
> failed.
>
> I believe this is caused by the change in behaviour of mkswap, which now
> complains on stderr if the provided image cont
Hi,
I think the following change might be the relevant one:
--- a/update-ca-certificates
+++ b/update-ca-certificates
@@ -164,8 +164,6 @@
done
fi
-rm -f "$CERTBUNDLE"
-
ADDED_CNT=$(wc -l < "$ADDED")
REMOVED_CNT=$(wc -l < "$REMOVED")
It triggers this std
Your message dated Mon, 18 Oct 2021 12:33:41 +
with message-id
and subject line Bug#984145: fixed in gatb-core 1.4.2+dfsg-7
has caused the Debian Bug report #984145,
regarding gatb-core: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 18 Oct 2021 12:18:39 +
with message-id
and subject line Bug#984196: fixed in libopendbx 1.4.6-16
has caused the Debian Bug report #984196,
regarding libopendbx: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
On 10/18/21 13:16, Antonio Terceiro wrote:
> I don't think we are on the right track here. I need to read the failing
> test correctly. this "test case" alone is bogus, as
>
> ruby -e 'END {Process.kill :SEGV, $$}'
>
> is _expected_ to segfault, i.e. the process is sending a SEGV signal to
> itse
On Mon, Oct 18, 2021 at 12:59:35PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/18/21 12:51, Antonio Terceiro wrote:
> >> So, we need a backtrace to see where the crash actually happens. I assume
> >> it's in one
> >> of the build dependencies.
> >
> > it happens in glibc:
> >
> > Program rec
Hello Sergei
Thank you for the patch you prepared. It's well done. Feel free to do a NMU.
--
Evgeny
On 10/18/21 12:51, Antonio Terceiro wrote:
>> So, we need a backtrace to see where the crash actually happens. I assume
>> it's in one
>> of the build dependencies.
>
> it happens in glibc:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x77a48f04 in kill () from /lib/powerpc
On Mon, Oct 18, 2021 at 10:00:42AM +0200, John Paul Adrian Glaubitz wrote:
> Hello!
>
> On 10/17/21 21:50, John Paul Adrian Glaubitz wrote:
> > Ah, so the last successful build was 3.0.2-2 and the first failure was in
> > 3.0.2-3,
> > the only difference being the mipsel patch to fix an unaligned
Processing commands for cont...@bugs.debian.org:
> fixed 996571 lutris/0.5.9.1-1
Bug #996571 [lutris] lutris: since the latest update lutris creates a
lutris.log file in $HOME
Marked as fixed in versions lutris/0.5.9.1-1.
> forwarded 996553 https://github.com/jrmadsen/PTL/issues/16
Bug #996553 [s
Package: util-linux
Version: 2.37.2-3
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Chris,
Whilst building a local version of util-linux 2.37.2-3, the misc/swaplabel test
failed.
I believe this is caused by the change in behavi
Package: kwin-x11
Version: 4:5.21.5-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: isop...@gmail.com
Dear Maintainer,
This morning just after applying latest package updates my KDE environment
failed to start due to Kwin crash. This morning updates included a new version
Your message dated Mon, 18 Oct 2021 11:48:13 +0200
with message-id
and subject line Re: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
CVE-2018-12536 CVE-2018-12538
has caused the Debian Bug report #902953,
regarding jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> unarchive 947540
Bug #947540 {Done: Debian FTP Masters }
[src:stardict] stardict: build-depends on deprecated gnome-doc-utils
Unarchived Bug 947540
> reopen 947540 =
Bug #947540 {Done: Debian FTP Masters }
[src:stardict] stardict: build-depends
RAmesh
Processing control commands:
> severity -1 normal
Bug #924005 [jetty9] client certificate verification regression with puppetdb
Severity set to 'normal' from 'grave'
--
924005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: severity -1 normal
On Fri, 8 Mar 2019 09:59:14 +0100 "=?UTF-8?Q?Stefan_B=c3=bchler?="
wrote:
> Package: jetty9
> Version: 9.4.15-1
> Severity: important
>
> Hi.
>
> The update (libjetty9-java and libjetty9-extra-java) to 9.4.15-1 broke
> our puppetdb setup; a downgrade to 9.4.14-1 fix
Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Reassigning to make the RM happen, as announced three months ago.
On Tue, 17 Aug 2021 07:39:54 +0200 Tobias Frost wrote:
> Package: nekobee
> Severity: serious
>
> nekobee is currently RC buggy with 2 RC bugs, (one being a gcc 10 a
Processing control commands:
> reassign -1 ftp.debian.org
Bug #992319 [nekobee] RM: nekobee -- RoQA, unmaintained, RC-buggy,
dead-upstream, python2
Bug reassigned from package 'nekobee' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #992319 to the same values
previously set
Source: openlayer
Severity: serious
The homepage in d/control just leads to berlios.de, dead since many years.
The package looks unmaintained, and upstream dead.
Popcon is at 4.
There are no reverse dependencies.
That makes me wonder if openlayer should be just removed.
If you disagree, just cl
Source: golang-github-lucas-clemente-quic-go
Version: 0.19.3-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org
panic: qtls.ClientHelloInfo doesn't match
goroutine 1 [running]:
github.com/marten-seemann/qtls-go1-15.init.0()
/<>/obj-x86_64-linux-gnu/src/git
Source: golang-github-marten-seemann-qtls-go1-15
Version: 0.1.1-2
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org
dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 12
github.com/marten-seemann/qtls-go1-15
pan
Your message dated Mon, 18 Oct 2021 08:24:04 +
with message-id
and subject line Bug#996618: fixed in libhmsbeagle 3.1.2+dfsg-12
has caused the Debian Bug report #996618,
regarding libhmsbeagle1v5 lists beignet-opencl-icd as first alternative
to be marked as done.
This means that you claim tha
Hello!
On 10/17/21 21:50, John Paul Adrian Glaubitz wrote:
> Ah, so the last successful build was 3.0.2-2 and the first failure was in
> 3.0.2-3,
> the only difference being the mipsel patch to fix an unaligned access.
>
> However, 3.0.2-2 was built with gcc-10:
>
>> https://buildd.debian.org/s
1 - 100 of 102 matches
Mail list logo
