On 18/12/22 03:06 AM, Abhijith PA wrote:
> Praveen, mdbilal
>
> On 24/03/21 07:11 PM, Julien Cristau wrote:
>
> ...
>
> > /usr/bin/check seems like an awfully generic program name to be shipped
> > in something like gitlab-shell. Please don't.
>
> I have reported this upstream.
>
Processing commands for cont...@bugs.debian.org:
> tags 1026256 + pending
Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you
"Save" in the admin web console
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> tags 1026256 + fixed-upstream
Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you
"Save" in the admin web console
Added tag(s) fixed-upstream.
> forwarded 1026256 https://github.com/backuppc/backuppc/issues/466
Bug
Source: pytango
Followup-For: Bug #1024078
As a maintenance note: it looks like upstream pytango v9.4.0 should resolve
this; it includes compatibility[1] with Python 3.11.
That release is currently planned[2] for the end of January, 2023.
[1] -
Processing commands for cont...@bugs.debian.org:
> forcemerge 1020018 1025733
Bug #1020018 {Done: Nicolas Boulenguez } [src:libxmlada]
libxmlada: FTBFS: unsatisfiable build-dependency: unicode-data (< 15~) but
15.0.0-1 is to be installed
Bug #1025733 [src:libxmlada] libxmlada: unsatisfiable
forcemerge 1020018 1025733
thanks
This is a duplicate.
1020018 is closed by libxmlada/23.0.0-1 in experimental.
Package: obantoo
Version: 2.1.12+ds1-3
Severity: serious
Justification: rc policy - "packages must be buildable within the same
release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable
obantoo build-depends on libitext5-java-doc which is no longer built
by the libitext5-java
Source: datalad
Version: 0.17.10-1
Severity: serious
Tags: ftbfs
Hi Maintainer
As can be seen on reproducible builds [1], datalad 0.17.10-1 FTBFS
without network access. I've copied what I hope is the relevant part
of a successful build below.
Regards
Graham
[1]
Hi Joachim,
Thank you!
I installed the patched .pm files and retested.
*One error is fixed:*
Can't locate object method "cleanup" via package "File::Temp::Dir" at
/usr/share/perl5/TigerVNC/Wrapper.pm line 1347, line 100.)
*The other error still remains:*
$ x0vncserver -display :0
Processing control commands:
> block 1021542 by -1
Bug #1021542 {Done: Andreas Tille } [src:unifrac] unifrac:
partially taken over by src:unifrac-tools
1021542 was blocked by: 1021378
1021542 was not blocking any bugs.
Added blocking bug(s) of 1021542: 1026297
--
1021542:
Source: unifrac-tools
Version: 1.1.3-1
Severity: serious
Tags: ftbfs patch
Control: block 1021542 by -1
https://tests.reproducible-builds.org/debian/history/unifrac-tools.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/unifrac-tools.html
Your message dated Sat, 17 Dec 2022 23:18:25 +0100
with message-id
and subject line Re: Bug#1026289: surf: The app opens, only displays a blank
page
has caused the Debian Bug report #1026289,
regarding surf: The app opens, only displays a blank page
to be marked as done.
This means that you
Source: vip-manager
Version: 1.0.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
vip-manager is failing to build in a clean sid schroot:
> github.com/cybertec-postgresql/vip-manager/ipmanager
> # github.com/cybertec-postgresql/vip-manager/ipmanager
>
Praveen, mdbilal
On 24/03/21 07:11 PM, Julien Cristau wrote:
...
> /usr/bin/check seems like an awfully generic program name to be shipped
> in something like gitlab-shell. Please don't.
I have reported this upstream.
https://gitlab.com/gitlab-org/gitlab-shell/-/issues/603
For now, this
The modification to fcgiwrap.socket doesn’t appear to use values recognised by
systemd.
I believe the configuration:
Mode=0660
SocketUser=www-data
SockerGroup=www-data
Should actually be:
SocketMode=0660
SocketUser=www-data
SocketGroup=www-data
Processing commands for cont...@bugs.debian.org:
> forwarded 1025326 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819
Bug #1025326 [libgl1-mesa-dri] tigervnc-standalone-server: Upgrade of
libgl1-mesa-dri to 22.3.0 breaks Xvnc
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> fixed 1023239 057+157-2
Bug #1023239 {Done: Thomas Lange } [dracut] dracut:
[regression] missing grep
Marked as fixed in versions dracut/057+157-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1023239:
Your message dated Sat, 17 Dec 2022 20:10:52 +
with message-id <7aa6ad5ad06a51bf99c646cea95a9009fb677df2.ca...@gmail.com>
and subject line Re: [deluge] crashes on load
has caused the Debian Bug report #1026240,
regarding [deluge] crashes on load
to be marked as done.
This means that you claim
Hi Jo,
On Thu, Dec 15, 2022 at 03:04:35PM -0500, Jo Shields wrote:
> What hardware is in the mipsel-osuosl-* machines? Mono has a history of
> triggering hardware bugs in imperfect MIPS implementations, e.g. Loongson 2
They are listed in
https://db.debian.org/machines.cgi?host=mipsel-osuosl-01
Processing commands for cont...@bugs.debian.org:
> found 1025326 22.3.0-1
Bug #1025326 {Done: Joachim Falk } [libgl1-mesa-dri]
tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 22.3.0 breaks Xvnc
Marked as found in versions mesa/22.3.0-1 and reopened.
> fixed 1025326 22.3.0-2
Bug
Processing commands for cont...@bugs.debian.org:
> reassign 1025326 libgl1-mesa-dri
Bug #1025326 {Done: Joachim Falk } [mesa]
tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 22.3.0 breaks Xvnc
Bug reassigned from package 'mesa' to 'libgl1-mesa-dri'.
No longer marked as found in
Package: surf
Version: 2.1+git20221016-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: marathon.duran...@gmail.com
Dear Maintainer,
On startup no content is displayed, simply a white blank window. The
window doesn't accept any mouse input. Error message when launching
Processing commands for cont...@bugs.debian.org:
> reassign 1025326 mesa 22.3.0-1
Bug #1025326 [tigervnc-standalone-server] tigervnc-standalone-server: Upgrade
of libgl1-mesa-dri to 22.3.0 breaks Xvnc
Bug reassigned from package 'tigervnc-standalone-server' to 'mesa'.
No longer marked as found
Package: libxt6
Followup-For: Bug #1005272
X-Debbugs-Cc: mechti...@debian.org
I tried to fix this RC bug. but I can't do it in my build environment.
It isn't buildable with gbp buildpackage. I miss pristine-tar and upstream
branch.
Regards
Mechtilde
-- System Information:
Debian Release:
Package: python3-numba
Version: 0.56.2+dfsg-2
Severity: serious
Hello,
thank you for maintaining python3-numba!
Unfortunately the package is currently uninstallable in sid.
It depends on `python3-numpy (<< 1:1.22), python3-numpy (>= 1:1.20.0)`,
but the version of python3-numpy in sid is
Control: tag -1 pending
Hello,
Bug #1025869 in tigervnc 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 #1025869 [tigervnc-scraping-server] tigervnc-scraping-server: Under
bookworm server fails to start. Gives error in Wrapper.pm
Added tag(s) pending.
--
1025869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025869
Debian Bug Tracking System
Source: ruby-nokogiri
Version: 1.13.7+dfsg-2
Severity: serious
Control: close -1 1.13.8+dfsg-1
Tags: sid bookworm
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
Processing control commands:
> close -1 1.13.8+dfsg-1
Bug #1026285 [src:ruby-nokogiri] src:ruby-nokogiri: fails to migrate to testing
for too long: FTBFS on some arch
Marked as fixed in versions ruby-nokogiri/1.13.8+dfsg-1.
Bug #1026285 [src:ruby-nokogiri] src:ruby-nokogiri: fails to migrate to
Processing control commands:
> close -1 43.2-1
Bug #1026279 [src:mutter] src:mutter: fails to migrate to testing for too long:
autopkgtest regression and FTBFS on armhf
Marked as fixed in versions mutter/43.2-1.
Bug #1026279 [src:mutter] src:mutter: fails to migrate to testing for too long:
Source: mutter
Version: 43.0-2
Severity: serious
Control: close -1 43.2-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1024438
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable
Processing commands for cont...@bugs.debian.org:
> found 1013526 0.12-1
Bug #1013526 [src:libtickit-widget-scrollbox-perl]
libtickit-widget-scrollbox-perl: intermittent memory corruption in
t/02input-key.t and t/03input-mouse.t
The source 'libtickit-widget-scrollbox-perl' and version '0.12-1'
Processing commands for cont...@bugs.debian.org:
> reopen 1023688
Bug #1023688 {Done: Jordi Mallach } [fcgiwrap] improper
permissions on fcgiwrap systemd socket lead to privilege escalation to www-data
under default config
'reopen' may be inappropriate when a bug has been closed with a version;
Processing control commands:
> clone -1 -2
Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you
"Save" in the admin web console
Bug 1026256 cloned as bug 1026270
> severity -1 grave
Bug #1026256 [backuppc] backuppc: BackupPC destroys its configuration when you
"Save"
Your message dated Sat, 17 Dec 2022 15:51:28 +
with message-id
and subject line Bug#1026257: fixed in node-zx 7.1.1+~cs6.7.23-2
has caused the Debian Bug report #1026257,
regarding FTBFS: more network tests in node-zx
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 17 Dec 2022 15:26:39 +
with message-id
and subject line Bug#1026202: Removed package(s) from unstable
has caused the Debian Bug report #999713,
regarding ruby-omniauth-cas3: FTBFS with ruby-omniauth 2.0.x: ERROR: Test
"ruby2.7" failed:
Your message dated Sat, 17 Dec 2022 15:25:38 +
with message-id
and subject line Bug#1026203: Removed package(s) from unstable
has caused the Debian Bug report #999712,
regarding ruby-omniauth-azure-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR:
Test "ruby2.7" failed:
Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1018030,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:23:36 +
with message-id
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #999723,
regarding ruby-omniauth-remote-user: FTBFS with ruby-omniauth 2.0.x: ERROR:
Test "ruby2.7" failed:
Your message dated Sat, 17 Dec 2022 15:23:36 +
with message-id
and subject line Bug#1026135: Removed package(s) from unstable
has caused the Debian Bug report #959557,
regarding ruby-omniauth-remote-user: FTBFS: ERROR: Test "ruby2.7" failed:
NoMethodError: undefined method `strip' for
Your message dated Sat, 17 Dec 2022 15:20:15 +
with message-id
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1022918,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:20:49 +
with message-id
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1022920,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:20:49 +
with message-id
and subject line Bug#1026156: Removed package(s) from unstable
has caused the Debian Bug report #1021574,
regarding haskell-thyme FTBFS: Couldn't match type
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 17 Dec 2022 15:22:06 +
with message-id
and subject line Bug#1026157: Removed package(s) from unstable
has caused the Debian Bug report #1017253,
regarding haskell-uri: FTBFS: hlibrary.setup: Encountered missing or private
dependencies: parsec >=3.0 && <=3.1.11
to be
Your message dated Sat, 17 Dec 2022 15:20:15 +
with message-id
and subject line Bug#1026154: Removed package(s) from unstable
has caused the Debian Bug report #1014001,
regarding haskell-text-format FTBFS: hlibrary.setup: Encountered missing or
private dependencies: base >=4.3 && <4.15
to be
Your message dated Sat, 17 Dec 2022 15:17:49 +
with message-id
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1022913,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:17:10 +
with message-id
and subject line Bug#1026152: Removed package(s) from unstable
has caused the Debian Bug report #1022196,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:17:49 +
with message-id
and subject line Bug#1026153: Removed package(s) from unstable
has caused the Debian Bug report #1015288,
regarding haskell-test-framework-th-prime FTBFS: Couldn't match expected type
‘Maybe Exp’ with actual type ‘Exp’
to be
Your message dated Sat, 17 Dec 2022 15:16:09 +
with message-id
and subject line Bug#1026151: Removed package(s) from unstable
has caused the Debian Bug report #1022194,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:15:14 +
with message-id
and subject line Bug#1026149: Removed package(s) from unstable
has caused the Debian Bug report #1022195,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:15:42 +
with message-id
and subject line Bug#1026150: Removed package(s) from unstable
has caused the Debian Bug report #1022191,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:12:58 +
with message-id
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1022906,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:14:15 +
with message-id
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #103,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:14:15 +
with message-id
and subject line Bug#1026148: Removed package(s) from unstable
has caused the Debian Bug report #1015280,
regarding haskell-pipes-zlib FTBFS: error: Couldn't match type
to be marked as done.
This means that you claim that the
Your message dated Sat, 17 Dec 2022 15:12:58 +
with message-id
and subject line Bug#1026147: Removed package(s) from unstable
has caused the Debian Bug report #1013996,
regarding haskell-monad-unlift FTBFS: error: Couldn't match type
to be marked as done.
This means that you claim that the
Your message dated Sat, 17 Dec 2022 15:11:56 +
with message-id
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1022905,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:11:56 +
with message-id
and subject line Bug#1026146: Removed package(s) from unstable
has caused the Debian Bug report #1013795,
regarding haskell-maths FTBFS: error: Bang pattern in expression context: !j
to be marked as done.
This means that you
Your message dated Sat, 17 Dec 2022 15:10:04 +
with message-id
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1022901,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:08:37 +
with message-id
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1021070,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:09:33 +
with message-id
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1022053,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1020782,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:11:28 +
with message-id
and subject line Bug#1026145: Removed package(s) from unstable
has caused the Debian Bug report #1020252,
regarding libghc-hashmap-doc: Depends: haddock-interface-35 but it is not
installable
to be marked as done.
This means
Your message dated Sat, 17 Dec 2022 15:08:37 +
with message-id
and subject line Bug#1026141: Removed package(s) from unstable
has caused the Debian Bug report #1017242,
regarding haskell-descriptive: FTBFS: • Couldn't match expected type ‘Key’ with
actual type ‘Text’ • In the second argument
Your message dated Sat, 17 Dec 2022 15:10:34 +
with message-id
and subject line Bug#1026144: Removed package(s) from unstable
has caused the Debian Bug report #1018051,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:10:04 +
with message-id
and subject line Bug#1026143: Removed package(s) from unstable
has caused the Debian Bug report #1014021,
regarding haskell-ghc-mtl FTBFS: error: Could not find module
to be marked as done.
This means that you claim that the
Your message dated Sat, 17 Dec 2022 15:09:33 +
with message-id
and subject line Bug#1026142: Removed package(s) from unstable
has caused the Debian Bug report #1014002,
regarding haskell-djinn-ghc FTBFS: error: Could not find module
to be marked as done.
This means that you claim that the
Your message dated Sat, 17 Dec 2022 15:07:55 +
with message-id
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1017011,
regarding Removal notice: obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 17 Dec 2022 15:07:55 +
with message-id
and subject line Bug#1026140: Removed package(s) from unstable
has caused the Debian Bug report #1017207,
regarding haskell-binary-tagged: FTBFS: unsatisfiable build-dependencies:
libghc-aeson-dev (< 1.5),
Source: ormar
Version: 0.12.0-1
Severity: serious
Tag: ftbfs
Dear Maintainer,
ormar currently fails to build from source for two reasons. The first is
several error message like these when running the test suite:
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
Processing control commands:
> severity -1 serious
Bug #1025744 [greetd] greetd - FTBFS with new version of rust-nix.
Severity set to 'serious' from 'important'
--
1025744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: node-zx
Version: 7.1.1+~cs6.7.23-1
Severity: serious
Tag: ftbfs patch
Dear Maintainer,
node-zx currently fails to build with the following error messages:
FAIL deps "installDeps() loader works via JS API"
Cannot find package 'cpy' imported from
On 13 Sep 2022 09:00:07 -0300 Antonio Terceiro wrote:
> Source: ruby-safe-yaml
> Version: 1.0.5-2
> Justification: FTBFS
> Usertags: ruby3.1
>
> We are about to start the ruby3.1 transition in unstable. While trying to
> rebuild ruby-safe-yaml with ruby3.1 enabled, the build failed.
>
>
Processing commands for cont...@bugs.debian.org:
> reassign 1023911 swig
Bug #1023911 [src:xdmf] xdmf FTBFS with SWIG 4.1.0
Bug reassigned from package 'src:xdmf' to 'swig'.
No longer marked as found in versions xdmf/3.0+git20190531-11.
Ignoring request to alter fixed versions of bug #1023911 to
Source: junit5-system-exit
Version: 1.1.2-3
Severity: serious
Tags: ftbfs patch
Dear Maintainer,
junit5-system-exit currently fails to build from source with the
following error message:
Starting process 'command
'/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''. Working directory:
Your message dated Sat, 17 Dec 2022 12:22:32 +
with message-id
and subject line Bug#1026155: fixed in python-trio 0.22.0-0.1
has caused the Debian Bug report #1026155,
regarding python3-trio: MultiError implementation conflicts with
BaseExceptionGroup backport in Python 3.10
to be marked as
Processing commands for cont...@bugs.debian.org:
> forwarded 1013381 https://github.com/buildbot/buildbot/pull/6616
Bug #1013381 [src:buildbot] buildbot: FTBFS with Sphinx 5.0, docutils 0.18:
make[2]: *** [Makefile:67: singlehtml] Error 2
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> affects 1024555 src:xdmf
Bug #1024555 {Done: Jochen Sprickerhof } [swig] xdmf FTBFS
with SWIG 4.1.0
Added indication that 1024555 affects src:xdmf
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024555:
On Sat, Dec 17, 2022 at 07:28:24AM +0100, Jochen Sprickerhof wrote:
> I've prepared an NMU for python-trio (versioned as 0.22.0-0.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
Thank you for working on this! Assuming it builds and passes tests OK,
+1
Your message dated Sat, 17 Dec 2022 11:20:46 +
with message-id
and subject line Bug#1024555: fixed in swig 4.1.0-0.2
has caused the Debian Bug report #1024555,
regarding xdmf FTBFS with SWIG 4.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 17 Dec 2022 11:18:56 +
with message-id
and subject line Bug#1024304: fixed in rust-cargo-outdated 0.11.1-1
has caused the Debian Bug report #1024304,
regarding rust-cargo-outdated - build-depends on obsolete version of rust-cargo.
to be marked as done.
This means that
Your message dated Sat, 17 Dec 2022 11:06:27 +
with message-id
and subject line Bug#1025840: fixed in deepin-log-viewer 5.9.7+ds1-2
has caused the Debian Bug report #1025840,
regarding deepin-log-viewer: build-depends on dropped virtual package
to be marked as done.
This means that you claim
On Sun, Aug 21, 2022 at 12:29:21PM +0200, Gregory Mounie wrote:
> Upgrading to emacs-gtk 28.1 fails with byte co[m]piling elpa-evil*
[...]
> In toplevel form:
> evil.el:133:1: Error: Wrong number of arguments: (3 . 4), 2
> ERROR: install script from elpa-evil package failed
Confirmed, I'm seeing
Processing control commands:
> reassign -1 src:mesa 22.2.4-1
Bug #1025213 [gnome-shell] gnome-shell: Flickering and mangled screens on
wayland if dri driver not available
Bug reassigned from package 'gnome-shell' to 'src:mesa'.
No longer marked as found in versions gnome-shell/43.1-2.
Ignoring
Control: reassign -1 src:mesa 22.2.4-1
Control: severity -1 normal
>From what you've said about the various different drivers in use in
different modes, this looks like a Mesa issue more than a gnome-shell
issue, so I'm reassigning this. It also seems to be hardware-specific
and has a
On Fri, 16 Dec 2022 at 22:40:28 +0100, Gert van de Kraats wrote:
> If the i915 dri driver is present gnome-shell is using the DRM platform
> (not the Wayland platform?) with this driver.
This is expected. gnome-shell acts as the Wayland compositor (the X11
equivalent would be Xorg, window manager
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=460701
Processing control commands:
> forwarded -1 https://bugs.kde.org/show_bug.cgi?id=460701
Bug #1022149 [ktimetracker] ktimetracker total data loss
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=460701'.
--
1022149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022149
87 matches
Mail list logo
