Your message dated Wed, 22 Jun 2022 04:35:37 +
with message-id
and subject line Bug#970109: fixed in rust-derive-builder 0.9.0-4
has caused the Debian Bug report #970109,
regarding rust-derive-builder has unsatisfiable dependency on non-existent
rust-compiletest-rs
to be marked as done.
Hi,
On Tuesday, 21 June 2022 22:31:45 CEST Paul Gevers wrote:
> On 21-06-2022 22:07, Diederik de Haas wrote:
>
> > Do these errors still occur? Still with 5.10.103-1 or a later one?
>
> The last occurrence of a machine hang I had is from 5 May 2022, but I'm
> not sure if I checked if it was
Hi Diederik,
On 21-06-2022 22:07, Diederik de Haas wrote:
Do these errors still occur? Still with 5.10.103-1 or a later one?
The last occurrence of a machine hang I had is from 5 May 2022, but I'm
not sure if I checked if it was this same issue. Normally our kernels
are up-to-date, but I
Processing control commands:
> found -1 linux/5.10.103-1
Bug #1001001 [src:linux] linux-image-5.10.0-9-arm64: kernel BUG at
include/linux/swapops.h:204!
Marked as found in versions linux/5.10.103-1.
--
1001001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001001
Debian Bug Tracking
Control: found -1 linux/5.10.103-1
Hi Paul,
On Tuesday, 29 March 2022 20:58:59 CEST Paul Gevers wrote:
> On 20-02-2022 13:44, Paul Gevers wrote:
>
> > Sad to say, but this week we had two hangs again.
>
> And this week another two.
>
> ci-worker-arm64-07 ==
>
> Mar
On Sat, Jun 18, 2022 at 10:15:02AM +0200, Florian Schlichting wrote:
> On Thu, Jun 09, 2022 at 09:54:38PM +0200, Marc Haber wrote:
> > Package: yubikey-manager
> > Version: 4.0.7-1
> > Severity: serious
> >
> > Justification: Policy 2.3, Policy 4.4
> >
> > /usr/share/doc/yubikey-manager is
Your message dated Tue, 21 Jun 2022 19:24:15 +
with message-id
and subject line Bug#1008703: Removed package(s) from unstable
has caused the Debian Bug report #938516,
regarding sortsmill-tools: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 21 Jun 2022 19:25:28 +
with message-id
and subject line Bug#1008704: Removed package(s) from unstable
has caused the Debian Bug report #936159,
regarding astk: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 21 Jun 2022 19:24:15 +
with message-id
and subject line Bug#1008703: Removed package(s) from unstable
has caused the Debian Bug report #938516,
regarding sortsmill-tools: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that
Your message dated Tue, 21 Jun 2022 19:25:28 +
with message-id
and subject line Bug#1008704: Removed package(s) from unstable
has caused the Debian Bug report #936159,
regarding astk: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 21 Jun 2022 19:22:07 +
with message-id
and subject line Bug#1008500: Removed package(s) from unstable
has caused the Debian Bug report #938754,
regarding undertaker: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Tue, 21 Jun 2022 19:23:13 +
with message-id
and subject line Bug#1008702: Removed package(s) from unstable
has caused the Debian Bug report #936785,
regarding ketchup: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 21 Jun 2022 19:22:07 +
with message-id
and subject line Bug#1008500: Removed package(s) from unstable
has caused the Debian Bug report #938754,
regarding undertaker: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 21 Jun 2022 19:20:28 +
with message-id
and subject line Bug#1008274: Removed package(s) from unstable
has caused the Debian Bug report #938432,
regarding sandsifter: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Tue, 21 Jun 2022 19:20:28 +
with message-id
and subject line Bug#1008274: Removed package(s) from unstable
has caused the Debian Bug report #938432,
regarding sandsifter: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 21 Jun 2022 19:19:13 +
with message-id
and subject line Bug#1008499: Removed package(s) from unstable
has caused the Debian Bug report #937125,
regarding neard: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 21 Jun 2022 19:19:46 +
with message-id
and subject line Bug#1001317: fixed in pocl 3.0-4
has caused the Debian Bug report #1001317,
regarding pocl: Please upgrade to llvm-toolchain-13 or 14
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> tags 1013129 + fixed-upstream
Bug #1013129 {Done: Yves-Alexis Perez } [src:exo] exo:
CVE-2022-32278
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013129:
Processing commands for cont...@bugs.debian.org:
> found 1013129 4.16.0-1
Bug #1013129 {Done: Yves-Alexis Perez } [src:exo] exo:
CVE-2022-32278
Marked as found in versions exo/4.16.0-1.
> found 1013129 0.12.4-1
Bug #1013129 {Done: Yves-Alexis Perez } [src:exo] exo:
CVE-2022-32278
Marked as
Your message dated Tue, 21 Jun 2022 19:30:51 +0200
with message-id <10827438.T7Z3S40VBb@delta-one>
and subject line Re: plasma-desktop: Plasma upgrade removed almost ALL KDE
packages
has caused the Debian Bug report #1013322,
regarding plasma-desktop: Plasma upgrade removed almost ALL KDE
Diederik de Haas dixit:
>I'm talking here about 4.9, not 4.19 ...
Ah sorry, I can’t keep them distinguished in my head apparently, or
it’s too hot…
>> $ git tag --contains 92833e8b5db6
>> v4.19.221
>> […]
>
>Thanks for that command :-) I usually went through several manual steps to
>figure out
LC_ALL=C sudo apt install plasma-desktop
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some
Processing commands for cont...@bugs.debian.org:
> close 1009444
Bug #1009444 [src:lomiri-ui-toolkit] lomiri-ui-toolkit: FTBFS: QWARN :
components::UnknownTestFunc()
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtTest/SignalSpy.qml:258: Error:
Invalid write to global property "qtest_count"
Marked
Purge: libkf5kipi-data:amd64 (4:21.12.3-1),
qml-module-org-kde-kquickcontrols:amd64 (5.94.0-1), liblensfun1:amd64
(0.3.3-1), qml-module-org-kde-kcoreaddons:amd64 (5.94.0-1),
libkf5plotting5:amd64 (5.94.0-1), libxcb-composite0:amd64 (1.14-3),
libkf5parts-data:amd64 (5.94.0-1),
Your message dated Tue, 21 Jun 2022 16:48:56 +
with message-id
and subject line Bug#965603: fixed in jcal 0.4.1-2.1
has caused the Debian Bug report #965603,
regarding jcal: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the
Your message dated Tue, 21 Jun 2022 16:48:50 +
with message-id
and subject line Bug#965488: fixed in dis51 0.5-1.2
has caused the Debian Bug report #965488,
regarding dis51: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the
Upgrade: libqt5webengine-data:amd64 (5.15.8+dfsg-1, 5.15.10+dfsg-1),
qtspeech5-flite-plugin:amd64 (5.15.2-2, 5.15.4-2), libcurl4:amd64
(7.83.1-1+b1, 7.83.1-2), libqt5websockets5:amd64 (5.15.2
-2, 5.15.4-2), udev:amd64 (250.4-1, 251.2-5), libcurl3-gnutls:amd64
(7.83.1-1+b1,
7.83.1-2),
Remove: libkf5alarmcalendar5abi1:amd64 (4:21.12.3-2), libkf5konq6:amd64
(4:21.12.3-1), breeze:amd64 (4:5.24.5-1), libkf5mailtransportakonadi5:amd64
(21.12.3-2), plasma-runners-addons:amd64 (4:5.24.5-1),
libkf5kdelibs4support5-bin:amd64 (5.94.0-1),
kde-config-telepathy-accounts:amd64
I use a script to automatically do the following :
apt-get update
apt-get dist-upgrade
apt-get autoremove --purge
deborphan | apt-get remove --purge
Purge: signon-ui-service:amd64 (0.17+16.04.20151125-1),
libstellarsolver2:amd64 (2.3-2), libkf5dav-data:amd64 (1:5.94.0-1),
Package: plasma-desktop
Version: Plasma upgrade removes ALL KDE
Severity: grave
Justification: renders package unusable
I filled this bug against plasma-desktop because I don't know which
package upgrade cause the error. However monday I upgraded my plasma
desktop and it removed almost all of
Your message dated Tue, 21 Jun 2022 16:33:55 +
with message-id
and subject line Bug#1009888: fixed in rust-h2 0.3.13-1
has caused the Debian Bug report #1009888,
regarding rust-h2, existing version is badly broken, new upstream needs new
package
to be marked as done.
This means that you
On 21/06/2022 14:39, Jonas Smedegaard wrote:
Quoting Peter Green (2022-06-21 15:35:59)
What is status of this bug?
Status is that h2 still needs tower-service, Fabian prepared it but noone
got around to sponsoring it. I've just updated and uploaded it. Now it
needs to get through NEW.
Thanks!
On Tuesday, 21 June 2022 15:34:12 CEST Thorsten Glaser wrote:
> >In branch 'linux-4.9.y' there is no qdisc_put function, so the above check
> >seems rightly in qdisc_destroy there.
I'm talking here about 4.9, not 4.19 ...
> Not any more. Since…
>
> $ git tag --contains 92833e8b5db6
> v4.19.221
Diederik de Haas dixit:
>In branch 'linux-4.9.y' there is no qdisc_put function, so the above check
>seems rightly in qdisc_destroy there.
Not any more. Since…
$ git tag --contains 92833e8b5db6
v4.19.221
[…]
… qdisc_destroy was renamed to qdisc_put in 4.19, breaking modules (grr).
So yes,
Processing commands for cont...@bugs.debian.org:
> retitle 1000927 creduce: Please upgrade to llvm-toolchain-13 or 14
Bug #1000927 [src:creduce] Please upgrade to llvm-toolchain-13 or 14
Changed Bug title to 'creduce: Please upgrade to llvm-toolchain-13 or 14' from
'Please upgrade to
Processing control commands:
> tag -1 help
Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in
qdisc_put() due to missing backport
Added tag(s) help.
--
1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299
Debian Bug Tracking System
Contact
Control: tag -1 help
On Tuesday, 21 June 2022 13:35:09 CEST Thorsten Glaser wrote:
> >So I'm inclined to think that 92833e8b5db6c209e9311ac8c6a44d3bf1856659 is
> >the commit which brought the bug back.
>
> Yes, definitely. The lines…
>
> if (!qdisc)
> return;
>
> … from
Control: tag -1 - moreinfo
Diederik de Haas dixit:
>In Debian, the release before 4.19.235-1 was 4.19.232-1 which should also have
>this bug. The release before that was 4.19.208-1, which shouldn't.
>Can you verify that?
Not easily any more, but I know it worked some weeks ago, and I *think*
I
Processing control commands:
> tag -1 - moreinfo
Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in
qdisc_put() due to missing backport
Removed tag(s) moreinfo.
--
1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299
Debian Bug Tracking System
Contact
Diederik de Haas dixit:
>It's a bit 'above my paygrade', but if qdisk_put() can accept a NULL pointer
>then I'm curious whether that would be allowed for other functions in that file
>as well ... there are several having "struct Qdisc *qdisc" as (only)
>parameter, but only qdisk_put() checks for
What is status of this bug?
Reading backlog it seems there was progress, but conversation when quiet
more than a month ago...
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ]
Source: jsonnet
Version: 0.18.0+ds-1
Severity: serious
Justification: FTBFS regression
Tags: ftbfs
jsonnet does not build on several release architecture due to:
/<>/third_party/rapidyaml/rapidyaml/ext/c4core/src/c4/ext/debugbreak/debugbreak.h: In function ‘void
debug_break()’:
Your message dated Tue, 21 Jun 2022 10:49:11 +
with message-id
and subject line Bug#1006981: fixed in rails 2:6.1.4.7+dfsg-2
has caused the Debian Bug report #1006981,
regarding rails: flaky autopkgtest on some ci.d.n architectures
to be marked as done.
This means that you claim that the
On dinsdag 21 juni 2022 11:49:26 CEST you wrote:
> https://lore.kernel.org/all/20190921063607.ga1083...@kroah.com/ is about the
> 4.19.75 release and that contains that change in commit
> 7a1bad565cebfbf6956f9bb36dba734a48fa31d4 titled "net_sched: let qdisc_put()
> accept NULL pointer" which
Control: tag -1 moreinfo
On Tuesday, 21 June 2022 08:10:54 CEST Thorsten Glaser wrote:
> Package: src:linux
> Version: 4.19.235-1
> Severity: critical
> Tags: upstream
> Justification: breaks the whole system
>
> A recent upstream “stable” upgrade backported the removal of the
> qdisc_destroy()
Processing control commands:
> tag -1 moreinfo
Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in
qdisc_put() due to missing backport
Added tag(s) moreinfo.
--
1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299
Debian Bug Tracking System
Contact
Package: ntopng
Version: 5.2.1+dfsg1-1
Severity: serious
It seems that ntopng recently started failing to build, I first noticed this on
a Raspbian
autobuilder, but it's also happening on the reproducible builds test
infrastructure so it's
not a raspbian specific issue.
Your message dated Tue, 21 Jun 2022 07:04:24 +
with message-id
and subject line Bug#1000922: fixed in llvmlite 0.38.1-2
has caused the Debian Bug report #1000922,
regarding Please upgrade to llvm-toolchain-13 or 14
to be marked as done.
This means that you claim that the problem has been
Package: src:linux
Version: 4.19.235-1
Severity: critical
Tags: upstream
Justification: breaks the whole system
A recent upstream “stable” upgrade backported the removal of the
qdisc_destroy() function (which, in itself, is questionable enough
already and caused no small amount of fun) using
49 matches
Mail list logo
