Bug#1070172: Exception when invoked without options

[Guido Günther]

Hi,
On Thu, May 02, 2024 at 03:55:53PM +0200, Guido Günther wrote:
> Hi,
> On Wed, May 01, 2024 at 12:27:41PM +0200, Guido Günther wrote:
> > Package: gcovr
> > Version: 7.2-1
> > Severity: grave
> > 
> > Hi,
> > invoking gcovr 7.2 in an empty directory fails like
> > 
> > $ gcovr 
> > --
> >GCC Code Coverage Report
> > Traceback (most recent call last):
> >   File "/usr/bin/gcovr", line 1972, in 
> > print_text_report(covdata)
> >   File "/usr/bin/gcovr", line 822, in print_text_report
> > OUTPUT.write("Directory: "+options.root+"\n")
> >  ~^
> > TypeError: can only concatenate str (not "NoneType") to str
> > 
> > 
> > This makes meson think gcovr is not available, e.g.:
> > 
> >   
> > https://gitlab.gnome.org/World/Phosh/phosh-mobile-settings/-/jobs/3839480#L3265
> > 
> > I've marked this as grave as it breaks CI pipelines.
> 
> Just had a closer look. It seems verson 3.2 instead of 7.2 got
> imported. I'll propose a fix.

Uploaded to delayed/3. MR is at 
https://salsa.debian.org/debian/gcovr/-/merge_requests/5
Cheers,
 -- Guido
> 
> Cheers,
>  -- Guido
> 
> > 
> > Cheers,
> >  -- Guido
> > 
> > 
> > -- System Information:
> > Debian Release: trixie/sid
> >   APT prefers testing
> >   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
> > 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
> > 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: arm64
> > 
> > Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
> > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE 
> > not set
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> > 
> > Versions of packages gcovr depends on:
> > ii  python33.11.6-1
> > ii  python3-pkg-resources  68.1.2-2
> > 
> > gcovr recommends no packages.
> > 
> > gcovr suggests no packages.
> > 
> > -- no debconf information

Bug#1070172: Exception when invoked without options

[Guido Günther]

Hi,
On Wed, May 01, 2024 at 12:27:41PM +0200, Guido Günther wrote:
> Package: gcovr
> Version: 7.2-1
> Severity: grave
> 
> Hi,
> invoking gcovr 7.2 in an empty directory fails like
> 
> $ gcovr 
> --
>GCC Code Coverage Report
> Traceback (most recent call last):
>   File "/usr/bin/gcovr", line 1972, in 
> print_text_report(covdata)
>   File "/usr/bin/gcovr", line 822, in print_text_report
> OUTPUT.write("Directory: "+options.root+"\n")
>  ~^
> TypeError: can only concatenate str (not "NoneType") to str
> 
> 
> This makes meson think gcovr is not available, e.g.:
> 
>   
> https://gitlab.gnome.org/World/Phosh/phosh-mobile-settings/-/jobs/3839480#L3265
> 
> I've marked this as grave as it breaks CI pipelines.

Just had a closer look. It seems verson 3.2 instead of 7.2 got
imported. I'll propose a fix.

Cheers,
 -- Guido

> 
> Cheers,
>  -- Guido
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
> 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: arm64
> 
> Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages gcovr depends on:
> ii  python33.11.6-1
> ii  python3-pkg-resources  68.1.2-2
> 
> gcovr recommends no packages.
> 
> gcovr suggests no packages.
> 
> -- no debconf information

Bug#1070172: Exception when invoked without options

[Guido Günther]

Package: gcovr
Version: 7.2-1
Severity: grave

Hi,
invoking gcovr 7.2 in an empty directory fails like

$ gcovr 
--
   GCC Code Coverage Report
Traceback (most recent call last):
  File "/usr/bin/gcovr", line 1972, in 
print_text_report(covdata)
  File "/usr/bin/gcovr", line 822, in print_text_report
OUTPUT.write("Directory: "+options.root+"\n")
 ~^
TypeError: can only concatenate str (not "NoneType") to str


This makes meson think gcovr is not available, e.g.:

  
https://gitlab.gnome.org/World/Phosh/phosh-mobile-settings/-/jobs/3839480#L3265

I've marked this as grave as it breaks CI pipelines.

Cheers,
 -- Guido


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcovr depends on:
ii  python33.11.6-1
ii  python3-pkg-resources  68.1.2-2

gcovr recommends no packages.

gcovr suggests no packages.

-- no debconf information

Bug#1068916: marked as pending in phosh

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1068916 in phosh 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/DebianOnMobile-team/phosh/-/commit/4aa47c933c49566e476f006e65348280fe1dcf67


tests: Skip symbol check on some architectures

Closes: #1068916


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068916

Bug#1068916: marked as pending in phosh

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1068916 in phosh 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/DebianOnMobile-team/phosh/-/commit/4aa47c933c49566e476f006e65348280fe1dcf67


tests: Skip symbol check on some architectures

Closes: #1068916


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068916

Bug#1068916: [Debian-on-mobile-maintainers] Bug#1068916: phosh: FTBFS on mips64el, riscv64, s390x: 24/26 phosh:tools / check-exported-symbols FAIL 0.03s exit status 1

[Guido Günther]

Hi Sebastian, Matthias,

On Sat, Apr 13, 2024 at 12:38:59PM +0200, Sebastian Ramacher wrote:
[..snip..]
> 000ec388 gDF .text00a4  Base
> phosh_arrow_get_progress

Thanks for filing this! The failing test is a symbol visibility check to
check that no unwanted symbols are being exported. Basically we check
that we only export the symbols from `phosh-exported-symbols.txt`) which
looks like:

{
   phosh_shell_get_default;

   …

   gtk_filter_list_model_*;
   gtk_sort_list_model_*;
};

Matthias do you have an idea why all the symbols are visible on the
above three architectures but not on others although we don't use
`--export-dynamic`?

This is the relevant linker line from the log at:

https://buildd.debian.org/status/fetch.php?pkg=phosh=mips64el=0.37.1-1=1712010515=0

> [485/1929] cc  -o src/phosh 
> src/phosh.p/meson-generated_.._.._subprojects_libcall-ui_src_cui-enums.c.o 
> src/phosh.p/meson-generated_.._phosh-enums.c.o 
> src/phosh.p/meson-generated_.._phosh-marshalers.c.o 
> src/phosh.p/meson-generated_.._phosh-resources.c.o 
> src/phosh.p/meson-generated_.._dbus_iio-sensor-proxy-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_hostname1-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_portal-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_login1-manager-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_login1-session-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_gsd-color-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_gnome-session-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-gnome-shell-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-display-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-screen-saver-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-screenshot-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-end-session-dialog-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-gtk-mountoperation-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_geoclue-manager-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-wwan-mm-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_calls-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_calls-emergency-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_gnome-session-client-private-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_gnome-session-presence-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_gsd-rfkill-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_mpris-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-wwan-ofono-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-osk0-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_geoclue-agent-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_notify-dbus.c.o 
> src/phosh.p/meson-generated_.._dbus_phosh-idle-dbus.c.o 
> src/phosh.p/meson-generated_.._.._protocol_xdg-shell-protocol.c.o 
> src/phosh.p/meson-generated_.._.._protocol_ext-idle-notify-v1-protocol.c.o 
> src/phosh.p/meson-generated_.._.._protocol_xdg-output-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_input-method-unstable-v2-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_phoc-device-state-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_phoc-layer-shell-effects-unstable-v1-protocol.c.o
>  src/phosh.p/meson-generated_.._.._protocol_phosh-private-protocol.c.o 
> src/phosh.p/meson-generated_.._.._protocol_virtual-keyboard-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_wlr-foreign-toplevel-management-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_wlr-gamma-control-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_wlr-layer-shell-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_wlr-output-management-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_wlr-output-power-management-unstable-v1-protocol.c.o
>  
> src/phosh.p/meson-generated_.._.._protocol_wlr-screencopy-unstable-v1-protocol.c.o
>  src/phosh.p/main.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro 
> -Wl,-z,now -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,--start-group 
> src/libphosh.a src/libphosh-tool.a subprojects/gmobile/src/libgmobile.a 
> subprojects/libcall-ui/src/libcall-ui.a subprojects/gvc/libgvc.a 
> -Wl,--dynamic-list=/<>/src/phosh-exported-symbols.txt 
> /usr/lib/mips64el-linux-gnuabi64/libfribidi.so 
> /usr/lib/mips64el-linux-gnuabi64/libgcr-ui-3.so 
> /usr/lib/mips64el-linux-gnuabi64/libgcr-base-3.so 
> /usr/lib/mips64el-linux-gnuabi64/libgck-1.so 
> /usr/lib/mips64el-linux-gnuabi64/libp11-kit.so 
> /usr/lib/mips64el-linux-gnuabi64/libgtk-3.so 
> /usr/lib/mips64el-linux-gnuabi64/libgdk-3.so 
> /usr/lib/mips64el-linux-gnuabi64/libz.so 
> /usr/lib/mips64el-linux-gnuabi64/libpangocairo-1.0.so 
> /usr/lib/mips64el-linux-gnuabi64/libpango-1.0.so 
> /usr/lib/mips64el-linux-gnuabi64/libharfbuzz.so 
> 

Bug#1068230: [Debian-on-mobile-maintainers] Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Guido Günther]

Hi Praveen,
On Wed, Apr 03, 2024 at 05:58:41PM +0530, Praveen Arimbrathodiyil via 
Debian-on-mobile-maintainers wrote:
> On Tue, 2 Apr 2024 08:04:12 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?=
>  wrote:
> > On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha  
> > wrote:
> > >
> > > On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen  
> > > wrote:
> > > > Recently automatic suspend stopped working. I think this was after 
> > > > gnome settings daemon 46 was available. Some background
> > > > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7
> > > >
> > > > Not sure if phosh needs some adjustments with recent changes in gnome 
> > > > settings daemon. For now assigned to both.
> > >
> > > Do you have phosh 0.37 or higher installed yet?
> > 
> > Correction: Do you have phosh 0.37.0-2 or 3.7.1-1 installed?
> I still have phosh 0.36.0-1 but auto suspend started working again. So it
> was probably fixed in a recent kernel update.

Thanks for checking! Please always make sure you check for inhibitors
(`gnome-session-inhibit -l`, `systemd-inhibit -l`) to make sure nothing
left a suspend/sleep inhibitor blocking this.

Cheers,
 -- Guido

> 
> Closing this.






> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

[Guido Günther]

Hi,
On Tue, Apr 02, 2024 at 02:32:16PM +0530, Pirate Praveen wrote:
> Package: gnome-settings-daemon,phosh
> severity: serious
> 
> Recently automatic suspend stopped working. I think this was after gnome
> settings daemon 46 was available. Some background
> 

Suspends fine here with phosh 0.37.1 (although notching changed in that
area for a while) and g-s-d 46

Cheers,
 -- Guido

> 
> Not sure if phosh needs some adjustments with recent changes in gnome
> settings daemon. For now assigned to both.
> 
> On kde plasma mobile, automatic suspend still works, so this appears to be
> gnome specific regression.
> 

Bug#1068187: Session fails to start with gnome-session >= 46

[Guido Günther]

Package: phosh
Version: 0.37.1
Severity: grave

gnome-session no longer accepts the --systemd or --builtin arguments
which restults in the session failing to start.

This is already fixed in 0.37.0-2. Mostly filing this to get the version
tracking right.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phosh depends on:
ii  dconf-gsettings-backend [gsettings-bac  0.40.0-4+b1
kend]
ii  fonts-lato  2.015-1
ii  gnome-shell-common  44.9-1
ii  gsettings-desktop-schemas   46.0-1
ii  libc6   2.37-15
ii  libcairo2   1.18.0-1+b1
ii  libcallaudio-0-10.1.9-1+b1
ii  libcap2-bin 1:2.66-5
ii  libecal-2.0-2t643.50.3-2.2
ii  libedataserver-1.2-27t643.50.3-2.2
ii  libfeedback-0.0-0   0.2.1-1+b1
ii  libfribidi0 1.0.13-3+b1
ii  libgcr-base-3-1 3.41.2-1
ii  libgcr-ui-3-1   3.41.2-1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1
ii  libglib2.0-0t64 2.78.4-6
ii  libgnome-desktop-3-20t6444.0-5
ii  libgtk-3-0t64   3.24.41-4
ii  libgudev-1.0-0  238-3
ii  libhandy-1-01.8.3-1
ii  libical3t64 3.0.17-1.1
ii  libjson-glib-1.0-0  1.8.0-2
ii  libnm0  1.46.0-1
ii  libpam0g1.5.2-9.1+b1
ii  libpango-1.0-0  1.52.0+ds-1
ii  libpolkit-agent-1-0 124-1
ii  libpolkit-gobject-1-0   124-1
ii  libpulse-mainloop-glib0 16.1+dfsg1-3
ii  libpulse0   16.1+dfsg1-3
ii  libsecret-1-0   0.21.4-1
ii  libsystemd0 255.4-1
ii  libupower-glib3 1.90.2-8
ii  libwayland-client0  1.22.0-2.1+b1
ii  phoc0.37.0+next20240325.1905.b42258fa.1

Versions of packages phosh recommends:
ii  feedbackd  0.2.1-1+b1
ii  fonts-cantarell0.303.1-1
ii  gnome-session-bin  46.0-1
ii  gnome-session-common   46.0-1
ii  gnome-settings-daemon  46~beta-2
ii  iio-sensor-proxy   3.5-1+b1
ii  librsvg2-common2.54.7+dfsg-2
ii  phosh-mobile-tweaks0.37.0-1
hi  phosh-osk-stub 0.35.0
ii  slurp  1.5.0-1
ii  squeekboard1.24.0-1

phosh suggests no packages.

-- no debconf information

Bug#1060658: [Debian-on-mobile-maintainers] Bug#1060658: Bug#1060658: megapixels don't start could not find any config file

[Guido Günther]

Hi,
On Wed, Jan 17, 2024 at 02:17:53PM +0530, Pirate Praveen wrote:
> 
> 
> On 16/01/24 10:01 pm, Arnaud Ferraris wrote:
> > Hi,
> > 
> > Le 12/01/2024 à 10:37, Pirate Praveen a écrit :
> > > Package: megapixels
> > > Version: 1.7.0-1
> > > Severity: grave
> > > 
> > > Running megapixels from commandline on mobian trixie fails with this error
> > > 
> > > /usr/share/megapixels/config/purism,librem5r4.ini not found.
> > 
> > This is expected, megapixels doesn't support the L5 (yet?).
> 
> I was looking at a blog post for QR code readers and mega pixel was
> mentioned
> 
> https://forums.puri.sm/t/qr-code-scanning-via-megapixels/14408
> 
> Found another reference now https://blog.brixit.nl/megapixels-2-0/
> 
> but seems this never finished.

On the L5 you can use millipixels (which is a fork of megapixels) for QR
code scanning. I've filed #1060921 to track L5 support in megapixels.

Cheers,
 -- Guido

> 
> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Bug#1057766: marked as pending in phosh

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1057766 in phosh 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/DebianOnMobile-team/phosh/-/commit/de6aa7ac1e26b9eea7e779f1b43ff76de0ccdcac


osk-manager: Sync initial state

Closes: #1057766
Thanks: Jarrah Gosbell for testing


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057766

Bug#1057766: marked as pending in phosh

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1057766 in phosh 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/DebianOnMobile-team/phosh/-/commit/de6aa7ac1e26b9eea7e779f1b43ff76de0ccdcac


osk-manager: Sync initial state

Closes: #1057766
Thanks: Jarrah Gosbell for testing


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057766

Bug#1057766: Osk button missing after startup

[Guido Günther]

Package: phosh
Version: 0.34.0-1
Severity: grave

There's a regression in phosh 0.34.0 that prevents the button to
manually unfold the OSK after startup. Let's block testing migration
as this makes many apps unusable for some people.

Likely fixed via 
https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/1332

 -- Guido



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.5.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phosh depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  fonts-lato   2.015-1
ii  gnome-shell-common   44.5-2
ii  gsettings-desktop-schemas45.0-2
ii  libc62.37-12
ii  libcairo21.18.0-1
ii  libcallaudio-0-1 0.1.9-1
ii  libecal-2.0-23.50.1-1
ii  libedataserver-1.2-273.50.1-1
ii  libfeedback-0.0-00.2.1-1
ii  libfribidi0  1.0.13-3
ii  libgcr-base-3-1  3.41.1-3
ii  libgcr-ui-3-13.41.1-3
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3
ii  libglib2.0-0 2.78.1-4
ii  libgnome-desktop-3-2044.0-2
ii  libgtk-3-0   3.24.38-6
ii  libgudev-1.0-0   238-3
ii  libhandy-1-0 1.8.2-3
ii  libical3 3.0.17-1
ii  libjson-glib-1.0-0   1.8.0-2
ii  libnm0   1.44.2-3
ii  libpam0g 1.5.2-9.1
ii  libpango-1.0-0   1.51.0+ds-3
ii  libpolkit-agent-1-0  123-3
ii  libpolkit-gobject-1-0123-3
ii  libpulse-mainloop-glib0  16.1+dfsg1-2+b1
ii  libpulse016.1+dfsg1-2+b1
ii  libsecret-1-00.21.1-1
ii  libsystemd0  254.5-1
ii  libupower-glib3  1.90.2-6
ii  libwayland-client0   1.22.0-2.1
ii  phoc 0.34.0~beta1+ds-2~exp1

Versions of packages phosh recommends:
ii  feedbackd  0.2.1-1
ii  gnome-session-bin  45.0-2
ii  gnome-session-common   45.0-2
ii  gnome-settings-daemon  45.0-1
ii  iio-sensor-proxy   3.5-1
ii  phosh-mobile-tweaks0.33.0-1
ii  phosh-osk-stub 0.34.0-1
ii  phosh-plugins  0.34.0-1
ii  slurp  1.4.0-1
ii  squeekboard1.22.0-5

phosh suggests no packages.

-- no debconf information

Bug#1051198: closing 1051198

[Guido Günther]

close 1051198

Let's migrate it to testing.

thanks

Bug#1051198: Fake bug to keep phosh-osk-stub out of testing

[Guido Günther]

Package: phosh-osk-stub
Version: 0.30.0-1
Severity: grave

It's useful for testing so having it in unstable is useful. It's not yet
suitable for stable releases though so lets keep it out of testing.
Cheers,
 -- Guido


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.4.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phosh-osk-stub depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libc62.37-7
ii  libcairo21.16.0-7
ii  libfeedback-0.0-00.2.1-1
ii  libglib2.0-0 2.77.2-1
ii  libgnome-desktop-3-2044.0-2
ii  libgtk-3-0   3.24.37-2
ii  libhandy-1-0 1.8.2-2
ii  libhunspell-1.7-01.7.2+really1.7.2-10
ii  libjson-glib-1.0-0   1.6.6-1
ii  libpango-1.0-0   1.50.14+ds-1
ii  libpangocairo-1.0-0  1.50.14+ds-1
ii  libpresage1v50.9.1-2.5
ii  libsystemd0  254.1-2
ii  libwayland-client0   1.22.0-2
ii  libxkbcommon01.5.0-1

Versions of packages phosh-osk-stub recommends:
ii  fonts-noto-core  20201225-1
ii  hunspell-en-us   1:2020.12.07-2

phosh-osk-stub suggests no packages.

-- no debconf information

Bug#1043121: marked as pending in phoc

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1043121 in phoc 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/DebianOnMobile-team/phoc/-/commit/7a74970c068f47d9f98b29f247807c4e06d15f62


d/control: Add breaks on phosh older than 0.30.0

Phosh itself works but want a session without g-s-d settings.

Closes: #1043121


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1043121

Bug#1043121: Needs breaks phosh << 0.30.0~

[Guido Günther]

Package: phoc
Version: 0.30.0
Severity: critical

We can't run with phosh << 0.30.0 session due to XWayland changes that
crash g-s-d settings. Hence we need the breaks.
Cheers,
 -- Guido


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phoc depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gsettings-desktop-schemas44.0-2
ii  libc62.37-5
ii  libcairo21.16.0-7
ii  libdrm2  2.4.115-1
ii  libegl1  1.6.0-1
ii  libgbm1  22.3.6-1+deb12u1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.76.4-4
ii  libgnome-desktop-3-2044.0-1
ii  libinput10   1.23.0-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libpixman-1-00.42.2-1
ii  libseat1 0.7.0-6
ii  libudev1 252.11-1
ii  libwayland-client0   1.22.0-0.1
ii  libwayland-server0   1.22.0-0.1
ii  libxcb-composite01.15-1
ii  libxcb-dri3-01.15-1
ii  libxcb-icccm40.4.1-1.1
ii  libxcb-present0  1.15-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.15-1
ii  libxcb-res0  1.15-1
ii  libxcb-shm0  1.15-1
ii  libxcb-xfixes0   1.15-1
ii  libxcb-xinput0   1.15-1
ii  libxcb1  1.15-1
ii  libxkbcommon01.5.0-1
ii  mutter-common44.0-2

Versions of packages phoc recommends:
ii  phosh  0.29.0+next20230727.1753.1

phoc suggests no packages.

-- no debconf information

Bug#1030240: wayfire: FTBFS with wlroots 0.16.1

[Guido Günther]

Hi,
On Wed, Feb 01, 2023 at 04:46:14PM +0100, Guido Günther wrote:
> Hi,
> On Wed, Feb 01, 2023 at 04:37:37PM +0100, Andreas Henriksson wrote:
> > On Wed, Feb 01, 2023 at 04:23:00PM +0100, Andreas Henriksson wrote:
> > > On Wed, Feb 01, 2023 at 04:03:47PM +0100, Guido Günther wrote:
> > > > Hi,
> > > > [..snip..]
> > > > > This seems to be caused by wlroots/experimental missing a
> > > > > build-dependency on libvulkan-dev and indeed after installing
> > > > > that package the build works again.
> > > > 
> > > > There is a build-dependency on libvulkan-dev. I think what you mean is
> > > > the lack of a dependency in the libwlroots-dev package?
> > > 
> > > Exactly... I've already retitled the bug report (again) to remove
> > > my incorrect use of build-dep, when what I mean was -dev package
> > > depending on another -dev package.
> > 
> > FWIW here are some examples of autopkgtest for checking if pkg-config
> > works for your own -dev packages:
> > https://sources.debian.org/src/util-linux/2.38.1-4/debian/tests/
> 
> We have tests for that like ages:
> 
>   
> https://salsa.debian.org/swaywm-team/wlroots/-/blob/debian/latest/debian/tests/
> 
> It just won't trigger if you don't need the vulkan renderer. Feel free
> to submit a patch that exercises that as well.

So I looked at the old logs and why the tests passed:
   
Package vulkan was not found in the pkg-config search path.
Perhaps you should add the directory containing `vulkan.pc'
to the PKG_CONFIG_PATH environment variable
Package 'vulkan', required by 'wlroots', not found
gcc  debian/tests/test.c -lwlroots  -lwayland-server
Build test of debian/tests/test.c succeeded

The tests succeeded as the --libs check correctly prints `-lwlroots`
*and* $(shell pkg-config …) in make doesn't fail on errors. Using a
shell script instead

   https://salsa.debian.org/swaywm-team/wlroots/-/merge_requests/19

will guard against that in the future.
Cheers,
 -- Guido

Bug#1030240: wayfire: FTBFS with wlroots 0.16.1

[Guido Günther]

Hi,
On Wed, Feb 01, 2023 at 05:34:16PM +0100, Andreas Henriksson wrote:
> On Wed, Feb 01, 2023 at 04:46:14PM +0100, Guido Günther wrote:
> > Hi,
> > On Wed, Feb 01, 2023 at 04:37:37PM +0100, Andreas Henriksson wrote:
> [...]
> > > FWIW here are some examples of autopkgtest for checking if pkg-config
> > > works for your own -dev packages:
> > > https://sources.debian.org/src/util-linux/2.38.1-4/debian/tests/
> > 
> > We have tests for that like ages:
> > 
> >   
> > https://salsa.debian.org/swaywm-team/wlroots/-/blob/debian/latest/debian/tests/
> > 
> > It just won't trigger if you don't need the vulkan renderer. Feel free
> > to submit a patch that exercises that as well.
> 
> Not sure why your tests doesn't catch this then.
> 
> You can reproduce this as simple as this:
> 
> 1. start with a clean sid chroot (eg. `pbuilder login`)
> 2. add experimental to /etc/apt/sources.list
> 3. apt update
> 4. apt install libwlroots-dev/experimental
> 5. pkg-config --cflags wlroots
> 
> Package vulkan was not found in the pkg-config search path.
> Perhaps you should add the directory containing `vulkan.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'vulkan', required by 'wlroots', not found

I just answered that in another reply to this bug.
 -- Guido

Bug#1030240: wayfire: FTBFS with wlroots 0.16.1

[Guido Günther]

Hi,
On Wed, Feb 01, 2023 at 04:37:37PM +0100, Andreas Henriksson wrote:
> On Wed, Feb 01, 2023 at 04:23:00PM +0100, Andreas Henriksson wrote:
> > On Wed, Feb 01, 2023 at 04:03:47PM +0100, Guido Günther wrote:
> > > Hi,
> > > [..snip..]
> > > > This seems to be caused by wlroots/experimental missing a
> > > > build-dependency on libvulkan-dev and indeed after installing
> > > > that package the build works again.
> > > 
> > > There is a build-dependency on libvulkan-dev. I think what you mean is
> > > the lack of a dependency in the libwlroots-dev package?
> > 
> > Exactly... I've already retitled the bug report (again) to remove
> > my incorrect use of build-dep, when what I mean was -dev package
> > depending on another -dev package.
> 
> FWIW here are some examples of autopkgtest for checking if pkg-config
> works for your own -dev packages:
> https://sources.debian.org/src/util-linux/2.38.1-4/debian/tests/

We have tests for that like ages:

  
https://salsa.debian.org/swaywm-team/wlroots/-/blob/debian/latest/debian/tests/

It just won't trigger if you don't need the vulkan renderer. Feel free
to submit a patch that exercises that as well.
 -- Guido

> Regards,
> Andreas Henriksson
> 

Bug#1030240: wayfire: FTBFS with wlroots 0.16.1

[Guido Günther]

Hi,
[..snip..]
> This seems to be caused by wlroots/experimental missing a
> build-dependency on libvulkan-dev and indeed after installing
> that package the build works again.

There is a build-dependency on libvulkan-dev. I think what you mean is
the lack of a dependency in the libwlroots-dev package?
 -- Guido

> 
> Every package listed in pkg-config .pc files Requires* must be
> available and thus the package holding the .pc file referenced
> must be a build-dependency... otherwise pkg-config will not work.
> 
> Adding autopkgtest to run pkg-config --cflags --libs etc. and maybe
> build a trivial example application is a great way to make sure
> pkg-config is working as expected (because it's easy to forget to check
> every .pc file changes and cross-check which package provides that and
> if it's listed in build-depends on every update).
> 
> Regards,
> Andreas Henriksson
> 

Bug#1030176: marked as pending in libvirt-python

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1030176 in libvirt-python 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/libvirt-team/libvirt-python/-/commit/badae7a2f4585c7c4c7ff951c9cc0ae1b05a2aa9


Depend on setuptools

Closes: #1030176


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030176

Bug#1030176: marked as pending in libvirt-python

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1030176 in libvirt-python 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/libvirt-team/libvirt-python/-/commit/badae7a2f4585c7c4c7ff951c9cc0ae1b05a2aa9


Depend on setuptools

Closes: #1030176


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030176

Bug#1028201: riseup-vpn unable to find a usable polkit agent under phosh

[Guido Günther]

Hi,

On Sun, Jan 08, 2023 at 06:54:17PM +0530, Pirate Praveen wrote:
> Package: riseup-vpn,phosh
> severity: grave
> 
> On mobian under phosh (librem 5), riseup-vpn gives error.
> output of riseup-vpn attached.

I don't think the severity is justified for phosh as it's certianly not
unusable or mostly so. I tihnk the same is true for riseup-net.

Cheers,
 -- Guido

> 
> phosh provides polkit-1-auth-agent
> 
> phosh 0.23
> riseup-vpn 0.21.11+ds1-2+b1
> 

> No systray icon available.
> qml: flavor: riseup-vpn
> QSystemTrayIcon::setVisible: No Icon set
> QObject::connect: No such signal 
> QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
> 2023/01/08 18:44:03 Client expects anon auth
> 2023/01/08 18:44:03 Checking for updates...
> qml: delay...
> 2023/01/08 18:44:14 Get "https://downloads.leap.se/RiseupVPN/linux/lastver": 
> net/http: TLS handshake timeout
> 2023/01/08 18:44:14 Fetching MOTD for riseup.net
> 2023/01/08 18:44:16 There are 4 pending messages
> 2023/01/08 18:44:16 firewall stop
> 2023/01/08 18:44:17 Fetching gateways...
> 2023/01/08 18:44:17 Cannot find any usable polkit
> 2023/01/08 18:44:17 ERROR: no polkit
> qml: errors, setting root.error
> qrc:/components/InitErrors.qml:39: ReferenceError: splashSpinner is not 
> defined
> qrc:/components/InitErrors.qml:38:13: QML PropertyChanges: Cannot assign to 
> non-existent property "visible"
> qml: errors, setting root.error
> qml: errors, setting root.error
> 2023/01/08 18:44:38 Close: cleanup and vpn shutdown...
> 2023/01/08 18:44:38 firewall stop
> 2023/01/08 18:44:38 openvpn stop
> 
> Catched signal(2): quitting

Bug#1027618: phosh-tour: FTBFS: dh_auto_test: error: cd _build && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1

[Guido Günther]

Hi,
On Sun, Jan 01, 2023 at 03:33:59PM +0100, Lucas Nussbaum wrote:
> > --- stdout 
> > ---
> > E: sm.puri.PhoshTour.desktop:25: custom-key-duplicated Purism::form_factor
> > I: sm.puri.PhoshTour.desktop:12: summary-first-word-not-capitalized
> > I: sm.puri.PhoshTour.desktop:8: description-first-para-too-short
> >  This apps introduces you to your device via a small graphical tour.

Fixed upstream at
https://gitlab.gnome.org/guidog/phosh-tour/-/merge_requests/7
about to be release end of month which will then go into Debian. 

Cheers,
 -- Guido

Bug#1024773: libpresage-doc: missing Breaks+Replaces: libpresage-dev (<< 0.9.1-2.4)

[Guido Günther]

control: -1 tags +pending

Hi,
On Sat, Nov 26, 2022 at 06:54:29PM +0100, Guido Günther wrote:
> Hi Andreas,
> On Thu, Nov 24, 2022 at 05:30:16PM +0100, Andreas Beckmann wrote:
> > Package: libpresage-doc
> > Version: 0.9.1-2.4
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: piuparts
> > 
> > Hi,
> > 
> > during a test with piuparts I noticed your package fails to upgrade from
> > 'testing'.
> > It installed fine in 'testing', then the upgrade to 'sid' fails
> > because it tries to overwrite other packages files without declaring a
> > Breaks+Replaces relation.
> > 
> > See policy 7.6 at
> > https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
> > 
> > >From the attached log (scroll to the bottom...):
> > 
> >   Selecting previously unselected package libpresage-dev:amd64.
> >   Preparing to unpack .../libpresage-dev_0.9.1-2.3_amd64.deb ...
> >   Unpacking libpresage-dev:amd64 (0.9.1-2.3) ...
> >   dpkg: error processing archive 
> > /var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb (--unpack):
> >trying to overwrite 
> > '/usr/share/doc/libpresage-dev/getting_started.txt.gz', which is also in 
> > package libpresage-doc 0.9.1-2.4
> >   Errors were encountered while processing:
> >/var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb
> 
> I'll prepare another NMU to fix that.
>  -- Guido

Uploaded to delayed/5 now with the attached diff.
Cheers,
 -- Guido

> 
> > 
> > 
> > cheers,
> > 
> > Andreas
diff --git a/debian/changelog b/debian/changelog
index 2ad7f76..d8ac4d9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,27 @@
+presage (0.9.1-2.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/control: Add missing Breaks/Replaces.
+Thanks to Andreas Beckmann (Closes: #1024773)
+  * text2ngram: Ignore more characters when building models.
+This prevents words ending with e.g. a non-breaking space. Patches were
+cherry-picked from sailfish OSes presage fork which is more active than
+the current upstream we track in Debian.
+  * d/control: Drop build-depends on autoreconf.
+Not needed since debhelper 10
+  * Add lintian override for abbreviation files.
+These are not documentation but data used by the library
+  * d/control: Bump standards version. No changes needed.
+  * d/patches: Mark css patch as forwarded too.
+Also applied to sfos' tree now
+  * d/rules: Enable bindnow hardening.
+Switch to DPKG_EXPORT_BUILDFLAGS for that so we can drop the
+configure dh_auto_configure override.
+  * d/control: Use https URLs
+  * d/gbp.conf: Update syntax
+
+ -- Guido Günther   Sun, 27 Nov 2022 14:02:27 +0100
+
 presage (0.9.1-2.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/debian/control b/debian/control
index 71a6760..597c265 100644
--- a/debian/control
+++ b/debian/control
@@ -3,8 +3,6 @@ Section: devel
 Priority: optional
 Maintainer: Matteo Vescovi 
 Build-Depends: debhelper-compat (= 13),
- autotools-dev,
- dh-autoreconf,
  pkg-config,
  libsqlite3-dev,
  libtinyxml-dev (>= 2.5.3),
@@ -13,10 +11,10 @@ Build-Depends: debhelper-compat (= 13),
  libcppunit-dev (>= 1.9.6) ,
  libgtk2.0-dev (>= 2.12),
 Build-Depends-Indep: doxygen, graphviz
-Standards-Version: 3.9.7
-Homepage: http://presage.sourceforge.net/
-Vcs-Git: git://git.code.sf.net/p/presage/presage-debian
-Vcs-Browser: http://sourceforge.net/p/presage/presage-debian/ci/master/tree/
+Standards-Version: 4.6.1
+Homepage: https://presage.sourceforge.net/
+Vcs-Git: https://git.code.sf.net/p/presage/presage-debian
+Vcs-Browser: https://sourceforge.net/p/presage/presage-debian/ci/master/tree/
 
 Package: presage
 Section: misc
@@ -36,6 +34,8 @@ Section: doc
 Architecture: all
 Depends: libjs-jquery, ${misc:Depends}
 Recommends: presage
+Breaks: libpresage-dev (<< 0.9.1-2.4)
+Replaces: libpresage-dev (<< 0.9.1-2.4)
 Description: intelligent predictive text entry platform (documentation)
  Presage is an intelligent predictive text entry platform.
  .
diff --git a/debian/gbp.conf b/debian/gbp.conf
index b0f498f..2eb755c 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,3 +1,3 @@
-[git-buildpackage]
+[buildpackage]
 # use a build area relative to the git repository
 export-dir=../build-area
diff --git a/debian/libpresage-data.lintian-overrides b/debian/libpresage-data.lintian-overrides
new file mode 100644
index 000..cf1b31d
--- /dev/null
+++ b/debian/libpresage-data.lintian-overrides
@@ -0,0 +1,3 @@
+# Abbreviations files are not documentation
+libpresage-data: package-contains-documentation-outside-usr-share-doc [usr/share/presage/abbreviations_en.txt]
+libpresage-data: package-contains-documentation-outside-usr-share-doc [us

Bug#1024773: libpresage-doc: missing Breaks+Replaces: libpresage-dev (<< 0.9.1-2.4)

[Guido Günther]

Hi Andreas,
On Thu, Nov 24, 2022 at 05:30:16PM +0100, Andreas Beckmann wrote:
> Package: libpresage-doc
> Version: 0.9.1-2.4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
> 
> >From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package libpresage-dev:amd64.
>   Preparing to unpack .../libpresage-dev_0.9.1-2.3_amd64.deb ...
>   Unpacking libpresage-dev:amd64 (0.9.1-2.3) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb (--unpack):
>trying to overwrite 
> '/usr/share/doc/libpresage-dev/getting_started.txt.gz', which is also in 
> package libpresage-doc 0.9.1-2.4
>   Errors were encountered while processing:
>/var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb

I'll prepare another NMU to fix that.
 -- Guido

> 
> 
> cheers,
> 
> Andreas

Bug#1023341: Fails to add any event due to too new python3-tzlocal

[Guido Günther]

Package: khal
Version: 1:0.10.4~ds-4
Severity: grave

Hi,
Adding a any new events on bookworm fails like (example is copied from
the manpage):

$ khal new 18:00 Awesome Event 
/usr/lib/python3/dist-packages/khal/icalendar.py:104: PytzUsageWarning: The 
localize method is no longer necessary, as this time zone supports the fold 
attribute (PEP 495). For more details on migrating to a PEP 495-compliant 
implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  dtstart = timezone.localize(dtstart)
/usr/lib/python3/dist-packages/khal/icalendar.py:105: PytzUsageWarning: The 
localize method is no longer necessary, as this time zone supports the fold 
attribute (PEP 495). For more details on migrating to a PEP 495-compliant 
implementation, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  dtend = timezone.localize(dtend)
/usr/lib/python3/dist-packages/icalendar/parser.py:54: PytzUsageWarning: The 
zone attribute is specific to pytz's interface; please migrate to a new time 
zone provider. For more details on how to do so, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  if hasattr(dt.tzinfo, 'zone'):
/usr/lib/python3/dist-packages/icalendar/parser.py:55: PytzUsageWarning: The 
zone attribute is specific to pytz's interface; please migrate to a new time 
zone provider. For more details on how to do so, see 
https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  tzid = dt.tzinfo.zone  # pytz implementation
Traceback (most recent call last):
  File "/usr/bin/khal", line 5, in 
main_khal()
  File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in 
new_func
return f(get_current_context(), *args, **kwargs)
  File "/usr/lib/python3/dist-packages/khal/cli.py", line 388, in new
new_func(
  File "/usr/lib/python3/dist-packages/khal/controllers.py", line 355, in 
new_from_string
new_from_args(
  File "/usr/lib/python3/dist-packages/khal/controllers.py", line 381, in 
new_from_args
collection.new(event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/khalendar.py", line 208, 
in new
event.href, event.etag = self._storages[calendar].upload(event)
  File "/usr/lib/python3/dist-packages/khal/khalendar/vdir.py", line 212, in 
upload
if not isinstance(item.raw, str):
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 382, in 
raw
timezone = create_timezone(tzinfo, self.start)
  File "/usr/lib/python3/dist-packages/khal/khalendar/event.py", line 858, in 
create_timezone
for one, two in iter(tz._tzinfos.items())
AttributeError: '_PytzShimTimezone' object has no attribute '_tzinfos'

This because khal can't cope with recent python3-tzlocal from bookworm (4.2-1),
downgrading python3-tzlocal (2.1-1) makes adding events work again (Got that
hint https://github.com/pimutils/khal/issues/1092)

As it fails to add any events I've picked grave severity. Please adjust
if you disagree.

Cheers,
  -- Guido


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages khal depends on:
ii  python33.10.6-1
ii  python3-atomicwrites   1.4.1-1
ii  python3-click  8.0.3-1
ii  python3-click-log  0.3.2-1
ii  python3-configobj  5.0.6-5
ii  python3-dateutil   2.8.2-1
ii  python3-icalendar  4.0.3-5
ii  python3-packaging  21.3-1.1
ii  python3-pkg-resources  65.5.0-1
ii  python3-tz 2022.4-1
ii  python3-tzlocal4.2-1
ii  python3-urwid  2.1.2-2+b2
ii  python3-xdg0.27-3

Versions of packages khal recommends:
ii  python3-setproctitle  1.3.1-1

Versions of packages khal suggests:
pn  khal-doc  

-- no debconf information

Bug#1017035: [Pkg-giraffe-maintainers] Bug#1017035: kopano-presence: please migrate from sleekxmpp to slixmpp

[Guido Günther]

Hi,
On Sun, Oct 16, 2022 at 07:23:05PM +, Martin wrote:
> Control: severity -1 serious
> 
> I'll ask for removal of sleekxmpp from Debian before freeze.

Given that kopano hasn't been updated since some time in Debian (it's
neither in testing nor stable) and we certainly don't want to ship a
version that outdated in stable I wonder if this would be a good
opportunity to have kopano removed as well. Carsten?
Cheers,
  -- Guido

> 
> ___
> Pkg-giraffe-maintainers mailing list
> pkg-giraffe-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-giraffe-maintainers
> 

Bug#1020566: git-buildpackage's autopkg tests fail with setuptools 65

[Guido Günther]

Hi Stefano,
On Thu, Sep 29, 2022 at 02:41:33PM +0200, Stefano Rivera wrote:
> Control: tag -1 + patch
> 
> Not quite sure what changed in setuptools here to trigger it, but it
> really seems to be a case of our default install layout breaking
> non-standard build-systems.
> 
> This patchset fixes the FTBFS.

Thanks a lot! Applied and uploaded.
 -- Guido

> 
> SR
> 
> -- 
> Stefano Rivera
>   http://tumbleweed.org.za/
>   +1 415 683 3272

> From e464acae335f3a0c0c2d04d06f8cb1a8f441cb24 Mon Sep 17 00:00:00 2001
> From: Stefano Rivera 
> Date: Thu, 29 Sep 2022 13:10:19 +0200
> Subject: [PATCH 1/2] Specify a sysconfig scheme in smoke-rpm
> 
> Debian uses the posix_local scheme by default, since Python 3.10,
> causing the rpm to be built with the incorrect layout.
> ---
>  debian/tests/smoke-rpm | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/debian/tests/smoke-rpm b/debian/tests/smoke-rpm
> index 90598a28..b7694d1e 100755
> --- a/debian/tests/smoke-rpm
> +++ b/debian/tests/smoke-rpm
> @@ -25,7 +25,7 @@ if python3 -c "import setuptools"; then
> --git-export-dir="$GBP_TEMPDIR" \
> -D'%__python3 /usr/bin/python3' \
> -D'%__python /usr/bin/python3' \
> -   -D'%python_sitelib %(%{__python3} -Ic "from sysconfig 
> import get_path; print(get_path('"'platlib'"'))")' \
> +   -D'%python_sitelib %(%{__python3} -Ic "from sysconfig 
> import get_path; print(get_path('"'platlib'"', '"'posix_prefix'"'))")' \
> -D'%_arch noarch' \
> -bb --nodeps
>  fi
> -- 
> 2.35.1
> 

> From f75321fd63fe294d98f79e28e4891e1ad1f97f6a Mon Sep 17 00:00:00 2001
> From: Stefano Rivera 
> Date: Thu, 29 Sep 2022 13:33:43 +0200
> Subject: [PATCH 2/2] Explicitly use the deb install layout when building our
>  RPM
> 
> Debian defaults to installing to /usr/local, unless told otherwise. This
> is usually done by passing --install-layout=deb to setup.py, when called
> directly. But that's only an option on Debian systems that have this
> patch. Set the environment variable equivalent, instead.
> ---
>  packaging/git-buildpackage.spec | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/packaging/git-buildpackage.spec b/packaging/git-buildpackage.spec
> index 17d6ed44..dbf5567c 100644
> --- a/packaging/git-buildpackage.spec
> +++ b/packaging/git-buildpackage.spec
> @@ -180,7 +180,7 @@ GIT_CEILING_DIRECTORIES=%{_builddir} \
>  
>  %install
>  rm -rf %{buildroot}
> -WITHOUT_NOSETESTS=1 %{__python3} ./setup.py install --root=%{buildroot} 
> --prefix=/usr --install-lib=%{python_sitelib}
> +DEB_PYTHON_INSTALL_LAYOUT=deb_system WITHOUT_NOSETESTS=1 %{__python3} 
> ./setup.py install --root=%{buildroot} --prefix=/usr 
> --install-lib=%{python_sitelib}
>  find %{buildroot} -name __pycache__ | xargs -r rm -r
>  mkdir -p %{buildroot}/usr/share/%{name}
>  mv %{buildroot}/usr/bin/gbp-builder-mock %{buildroot}/usr/share/%{name}/
> -- 
> 2.35.1
> 

Bug#1020024: git-buildpackage: FTBFS: ModuleNotFoundError: No module named 'filelock'

[Guido Günther]

control: reassign -1 src:pydoctor
control: affects -1 src:git-buildpackage

Hi,
as this comes out of pydoctor I'll reassign there but have
added a workaround to git-buildpackage too.
Cheers,
 -- Guido

On Sun, Sep 18, 2022 at 08:00:34AM +0200, Lucas Nussbaum wrote:
> Source: git-buildpackage
> Version: 0.9.28
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220917 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>'
> > mkdir -p build
> > pydoctor -v gbp tests/doctests/
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/cachecontrol/caches/file_cache.py", 
> > line 74, in __init__
> > from filelock import FileLock
> > ModuleNotFoundError: No module named 'filelock'
> > 
> > During handling of the above exception, another exception occurred:
> > 
> > Traceback (most recent call last):
> >   File "/usr/bin/pydoctor", line 8, in 
> > sys.exit(main())
> >   File "/usr/lib/python3/dist-packages/pydoctor/driver.py", line 166, in 
> > main
> > system = get_system(options)
> >   File "/usr/lib/python3/dist-packages/pydoctor/driver.py", line 26, in 
> > get_system
> > cache = prepareCache(clearCache=options.clear_intersphinx_cache,
> >   File "/usr/lib/python3/dist-packages/pydoctor/sphinx.py", line 431, in 
> > prepareCache
> > return IntersphinxCache.fromParameters(
> >   File "/usr/lib/python3/dist-packages/pydoctor/sphinx.py", line 385, in 
> > fromParameters
> > cache=FileCache(cachePath),
> >   File "/usr/lib/python3/dist-packages/cachecontrol/caches/file_cache.py", 
> > line 84, in __init__
> > raise ImportError(notice)
> > ImportError: 
> > NOTE: In order to use the FileCache you must have
> > filelock installed. You can install it via pip:
> >   pip install filelock
> > 
> > make[3]: *** [Makefile:34: apidocs] Error 1
> 
> 
> The full build log is available from:
> http://qa-logs.debian.net/2022/09/17/git-buildpackage_0.9.28_unstable.log
> 
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=lu...@debian.org=1=1=1=1#results
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> If you reassign this bug to another package, please marking it as 
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
> 
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

Bug#1018134: [Debian-on-mobile-maintainers] Bug#1018134: chatty: bump severity to serious for ongoing evolution transitions

[Guido Günther]

Hi,
On Mon, Sep 05, 2022 at 06:15:04PM -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> 
> The evolution-data-server 3.45 transition has begun. Therefore, I'm
> bumping the severity of this bug to Serious. Chatty will be removed
> from Testing soon unless this bug is fixed.

Thanks Jeremy for your work on this huge transition and sorry that
chatty is causing trouble here.

Just so that everybody is on the same page: the next chatty
release switches to libcmatrix and we can then switch to libsoup3
via

  https://source.puri.sm/Librem5/libcmatrix/-/merge_requests/18   

Cheers,
 -- Guido

Bug#1013667: marked as pending in virt-manager

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1013667 in virt-manager 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/libvirt-team/virt-manager/-/commit/d246d203204c598341925384a64a9adfecbb2227


d/patches: add fixes from upstream for FTBFS with libvirt 8.5

- tests: Fix with latest osinfo-db
- tests: Fix with latest argcomplete
- tests: Fix with latest libvirt

Closes: #1013667


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013667

Bug#1013748: [Debian-on-mobile-maintainers] Bug#1013748: src:phosh: fails to migrate to testing for too long: uploader built arch:all binaries

[Guido Günther]

Hi Paul,
On Sat, Jun 25, 2022 at 01:19:51PM +0200, Paul Gevers wrote:
> Your package is only blocked because the arch:all binary package(s) aren't
> built on a buildd. Unfortunately the Debian infrastructure doesn't allow
> arch:all packages to be properly binNMU'ed. Hence, I will shortly do a
> no-changes source-only upload to DELAYED/15, closing this bug. Please let me
> know if I should delay or cancel that upload.

Thanks for handling this, I totally didn't notice that migration was
pending for so long due to me picking the wrong change file on upload it
seems.

Cheers,
 -- Guido

> 
> Paul
> 
> [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
> [2] https://qa.debian.org/excuses.php?package=phosh
> 




> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Bug#1012361: New upstream version 4.2.2

[Guido Günther]

Package: electrum
Version: 4.0.9-1
Severity: critical

Hi,
there's a new upstream version 4.2.2 available:

  https://electrum.org/#download

Would be great to have that in Debian.
Cheers,
 -- Guido

Bug#1010061: git-buildpackage: FTBFS on bookworm and sid: multiple issues

[Guido Günther]

Hi Ian,
On Wed, May 11, 2022 at 12:40:35PM +0100, Ian Jackson wrote:
> Guido:
> > These all make sense. Pushed, thanks!
> 
> Would you mind doing an upload ?  My grep-excuses is warning me about
> autoremovals.
> 
> If you don't have time I would be willing to do it myself from the
> relevant git branch, but I certainly wouldn't want to do that without
> coordinating with you...

Thanks. I did an upload a while back but now dgit's tests fail:

   https://tracker.debian.org/pkg/git-buildpackage
   https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/22182444/log.gz

Maybe you have an idea what has triggered this (not all of them look gbp
related but looking at the tests many of them seem to pull in gbp):

debpolicy-quilt-gbp  FAIL non-zero exit status 16
TEST FAILED
gbp-orig FAIL non-zero exit status 16
TEST FAILED
overwrite-splitbrains FAIL non-zero exit status 16
TEST FAILED
quilt-gbpFAIL non-zero exit status 16
+ echo 'OPERATION FAILED'
TEST FAILED
quilt-gbp-build-modes FAIL non-zero exit status 16
TEST FAILED
quilt-splitbrainsFAIL non-zero exit status 16
TEST FAILED
rpush-quilt  FAIL non-zero exit status 16
baredebian-multitar  FAIL non-zero exit status 16
baredebian-plusgit   FAIL non-zero exit status 16
baredebian-push  FAIL non-zero exit status 16
baredebian-tarball   FAIL non-zero exit status 16
gdr-import-dgit  FAIL non-zero exit status 16
gdr-diverge-nmu  FAIL non-zero exit status 16
gdr-diverge-nmu-dgit FAIL non-zero exit status 16
gdr-editsFAIL non-zero exit status 16
gdr-import-dgitview  FAIL non-zero exit status 16
gdr-makepatches7 FAIL non-zero exit status 16
gdr-subcommands  FAIL non-zero exit status 16
gdr-unprocessableFAIL non-zero exit status 16
gdr-unprocessable-hints FAIL non-zero exit status 16
tagupl-baredebianFAIL non-zero exit status 16
tagupl-gbp   FAIL non-zero exit status 16
debpolicy-quilt-gbp  FAIL non-zero exit status 16
gbp-orig FAIL non-zero exit status 16
overwrite-splitbrains FAIL non-zero exit status 16
quilt-gbpFAIL non-zero exit status 16
quilt-gbp-build-modes FAIL non-zero exit status 16
quilt-splitbrainsFAIL non-zero exit status 16
rpush-quilt  FAIL non-zero exit status 16

Cheers,
 -- Guido
 
> 
> Thanks,
> Ian.
> 
> -- 
> 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.
> 

Bug#1010061: git-buildpackage: FTBFS on bookworm and sid: multiple issues

[Guido Günther]

Hi,
On Sat, Apr 23, 2022 at 10:10:44AM -0300, Antonio Terceiro wrote:
> Source: git-buildpackage
> Version: 0.9.25
> Severity: serious
> Tags: patch ftbfs
> Justification: fails to build from source
> 
> Dear Maintainer,
> 
> git-buildpackage currently fails to build due to a few issues. I tried
> both the source currently in testing/unstable, and the master branch
> from the git repository. There are a few different issues:

These all make sense. Pushed, thanks!
 -- Guido

Bug#1008919: phoc: Qt applications no longer receive any input

[Guido Günther]

control: tags -1 +patch

Hi,
On Mon, Apr 04, 2022 at 10:49:45AM +0200, Salvo 'LtWorf' Tomaselli wrote:
> https://gitlab.gnome.org/World/Phosh/phoc/-/issues/261

The above also links to a patch that fixes this.

Cheers,
 -- Guido

Bug#1008360: [Debian-on-mobile-maintainers] Bug#1008360: phoc: FTBFS: ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’

[Guido Günther]

control: tags -1 +pending

Hi,
On Sat, Mar 26, 2022 at 09:47:37PM +0100, Lucas Nussbaum wrote:
> Source: phoc
> Version: 0.12.0-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220326 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

I'll upload a version that works with wlroots 0.15.1 over the next days.
Upstream MR is here:

   https://gitlab.gnome.org/World/Phosh/phoc/-/merge_requests/329

Cheers,
 -- Guido

> 
> 
> Relevant part (hopefully):
> > cc -Isrc/libphoc.a.p -Isrc -I../src -Iprotocols -I/usr/include/libdrm 
> > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
> > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> > -I/usr/include/gnome-desktop-3.0 -I/usr/include/libxml2 
> > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 
> > -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
> > -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
> > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
> > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
> > -I/usr/include/gsettings-desktop-schemas 
> > -I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always 
> > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0 
> > -DWLR_USE_UNSTABLE -Wcast-align -Wdate-time -Werror=format-security 
> > -Werror=format=2 -Wendif-labels -Werror=incompatible-pointer-types 
> > -Werror=missing-declarations -Werror=overflow -Werror=return-type 
> > -Werror=shift-count-overflow -Werror=shift-overflow=2 
> > -Werror=implicit-fallthrough=3 -Wformat-nonliteral -Wformat-security 
> > -Winit-self -Wmaybe-uninitialized -Wmissing-field-initializers 
> > -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs 
> > -Wno-missing-field-initializers -Wno-sign-compare -Wno-strict-aliasing 
> > -Wno-unused-parameter -Wold-style-definition -Wpointer-arith 
> > -Wredundant-decls -Wshadow -Wstrict-prototypes -Wtype-limits -Wundef 
> > -Wunused-function -Wswitch-default -g -O2 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD 
> > -MQ src/libphoc.a.p/layer_shell.c.o -MF src/libphoc.a.p/layer_shell.c.o.d 
> > -o src/libphoc.a.p/layer_shell.c.o -c ../src/layer_shell.c
> > In file included from ../src/layer_shell.c:15:
> > /usr/include/wlr/types/wlr_box.h:4:2: warning: #warning "wlr_box has been 
> > moved to wlr/util/box.h" [-Wcpp]
> > 4 | #warning "wlr_box has been moved to wlr/util/box.h"
> >   |  ^~~
> > ../src/layer_shell.c: In function ‘arrange_layer’:
> > ../src/layer_shell.c:187:25: warning: implicit declaration of function 
> > ‘wlr_layer_surface_v1_close’; did you mean ‘wlr_layer_surface_v1_destroy’? 
> > [-Wimplicit-function-declaration]
> >   187 | wlr_layer_surface_v1_close(layer);
> >   | ^~
> >   | wlr_layer_surface_v1_destroy
> > ../src/layer_shell.c:187:25: warning: nested extern declaration of 
> > ‘wlr_layer_surface_v1_close’ [-Wnested-externs]
> > ../src/layer_shell.c: In function ‘change_osk’:
> > ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no 
> > member named ‘client_pending’
> >   244 | if (!force_overlay && osk->layer != 
> > osk->surface->layer_surface->client_pending.layer) {
> >   | 
> >^~
> > ../src/layer_shell.c:246:67: error: ‘struct wlr_layer_surface_v1’ has no 
> > member named ‘client_pending’
> >   246 | 
> > wl_list_insert([osk->surface->layer_surface->client_pending.layer], 
> > >surface->link);
> >   |   ^~
> > ../src/layer_shell.c: In function ‘phoc_layer_shell_arrange’:
> > ../src/layer_shell.c:273:53: error: ‘struct wlr_layer_surface_v1’ has no 
> > member named ‘client_pending’
> >   273 |   if (seat->focused_layer && 
> > seat->focused_layer->client_pending.layer >= 
> > osk_place.surface->layer_surface->client_pending.layer) {
> >   | ^~
> > ../src/layer_shell.c:273:111: error: ‘struct wlr_layer_surface_v1’ has no 
> > member named ‘client_pending’
> >   273 |   if (seat->focused_layer && 
> > seat->focused_layer->client_pending.layer >= 
> > osk_place.surface->layer_surface->client_pending.layer) {
> >   | 
> >   ^~
> > ../src/layer_shell.c: In function ‘popup_damage’:
> > ../src/layer_shell.c:436:55: error: ‘struct wlr_xdg_surface’ has no member 
> > named ‘geometry’
> >   436 

Bug#1005671: libvirt-python: FTBFS: ERROR: failed virDomainSetLaunchSecurityState

[Guido Günther]

Hi Fabio,
On Tue, Feb 22, 2022 at 10:15:22AM +0100, Fabio Fantoni wrote:
> Hi, is there someone working on this? if yes let me know please otherwise
> I'll try to do it when I have time

Thanks for the reminder. I just uploaded a new version.
Cheers,
 -- Guido

Bug#997367: marked as pending in virt-manager

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #997367 in virt-manager 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/libvirt-team/virt-manager/-/commit/ee0346769f6b8e3f8667ea9e1a714aa872c97fa6


d/patches: add some fixes from upstream

- virtinst: Fix TOCTOU in domain enumeration
- tests: storage: Fix with latest libvirt XML output
- tests: use different USB device when testing hot-add
- tests: don't add the same USB devices to the guest twice
- tests: Fix hyperv @mode handling on libvirt 8.0.0

Closes: #997367


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997367

Bug#997367: [Pkg-libvirt-maintainers] Bug#997367: virt-manager: FTBFS: AssertionError

[Guido Günther]

Hi Bastian,
On Thu, Feb 17, 2022 at 03:50:37PM +0100, Bastian Germann wrote:
> No team member reacted to Fabio's requests, so I am going to sponsor Fabio's 
> NMU.
> The debdiff is enclosed.

Seems I missed that. Thanks for NMUing.
Cheers,
 -- Guido


> diff -Nru virt-manager-3.2.0/debian/changelog 
> virt-manager-3.2.0/debian/changelog
> --- virt-manager-3.2.0/debian/changelog   2020-12-05 09:36:56.0 
> +0100
> +++ virt-manager-3.2.0/debian/changelog   2022-02-01 18:21:01.0 
> +0100
> @@ -1,3 +1,16 @@
> +virt-manager (1:3.2.0-3.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload
> +  * d/patches: add some fixes from upstream
> +- virtinst: Fix TOCTOU in domain enumeration
> +- tests: storage: Fix with latest libvirt XML output
> +- tests: use different USB device when testing hot-add
> +- tests: don't add the same USB devices to the guest twice
> +- tests: Fix hyperv @mode handling on libvirt 8.0.0
> +(Closes: #997367)
> +
> + -- Fabio Fantoni   Tue, 01 Feb 2022 18:21:01 +0100
> +
>  virt-manager (1:3.2.0-3) unstable; urgency=medium
>  
>* Drop the librsvg2-common dependency from virt-manager, as seems unused
> diff -Nru virt-manager-3.2.0/debian/patches/fix-tests2.patch 
> virt-manager-3.2.0/debian/patches/fix-tests2.patch
> --- virt-manager-3.2.0/debian/patches/fix-tests2.patch1970-01-01 
> 01:00:00.0 +0100
> +++ virt-manager-3.2.0/debian/patches/fix-tests2.patch2022-02-01 
> 18:21:01.0 +0100
> @@ -0,0 +1,107 @@
> +Author: Cole Robinson 
> +Date: Tue, 6 Apr 2021 15:21:00 -0400
> +Description: tests: storage: Fix with latest libvirt XML output
> +
> +Signed-off-by: Cole Robinson 
> +---
> + tests/data/storage/pool-dir-volclone.xml |  2 --
> + tests/data/storage/pool-disk-volclone.xml|  2 --
> + tests/data/storage/pool-fs-volclone.xml  |  2 --
> + tests/data/storage/pool-logical-volclone.xml |  2 --
> + tests/data/storage/pool-netfs-volclone.xml   |  2 --
> + tests/test_storage.py| 11 ++-
> + 6 files changed, 6 insertions(+), 15 deletions(-)
> +
> +diff --git a/tests/data/storage/pool-dir-volclone.xml 
> b/tests/data/storage/pool-dir-volclone.xml
> +index c8bde66fb..16f1e561d 100644
> +--- a/tests/data/storage/pool-dir-volclone.xml
>  b/tests/data/storage/pool-dir-volclone.xml
> +@@ -1,8 +1,6 @@
> + 
> +   pool-dir-volclone
> +   /var/lib/libvirt/images/pool-dir/pool-dir-vol
> +-  
> +-  
> +   10737418240
> +   5368709120
> +   
> +diff --git a/tests/data/storage/pool-disk-volclone.xml 
> b/tests/data/storage/pool-disk-volclone.xml
> +index a4e9c3d12..24f71a1d9 100644
> +--- a/tests/data/storage/pool-disk-volclone.xml
>  b/tests/data/storage/pool-disk-volclone.xml
> +@@ -1,8 +1,6 @@
> + 
> +   pool-disk-volclone
> +   /dev/pool-disk-vol
> +-  
> +-  
> +   10737418240
> +   5368709120
> +   
> +diff --git a/tests/data/storage/pool-fs-volclone.xml 
> b/tests/data/storage/pool-fs-volclone.xml
> +index 34e8cd088..6c7d3b9dd 100644
> +--- a/tests/data/storage/pool-fs-volclone.xml
>  b/tests/data/storage/pool-fs-volclone.xml
> +@@ -1,8 +1,6 @@
> + 
> +   pool-fs-volclone
> +   /var/lib/libvirt/images/pool-fs/pool-fs-vol
> +-  
> +-  
> +   10737418240
> +   5368709120
> +   
> +diff --git a/tests/data/storage/pool-logical-volclone.xml 
> b/tests/data/storage/pool-logical-volclone.xml
> +index c012017ef..8abcfa64c 100644
> +--- a/tests/data/storage/pool-logical-volclone.xml
>  b/tests/data/storage/pool-logical-volclone.xml
> +@@ -1,8 +1,6 @@
> + 
> +   pool-logical-volclone
> +   /dev/pool-logical/pool-logical-vol
> +-  
> +-  
> +   10737418240
> +   10737418240
> +   
> +diff --git a/tests/data/storage/pool-netfs-volclone.xml 
> b/tests/data/storage/pool-netfs-volclone.xml
> +index b6b39f79d..b7fd26507 100644
> +--- a/tests/data/storage/pool-netfs-volclone.xml
>  b/tests/data/storage/pool-netfs-volclone.xml
> +@@ -1,8 +1,6 @@
> + 
> +   pool-netfs-volclone
> +   /var/lib/libvirt/images/pool-netfs/pool-netfs-vol
> +-  
> +-  
> +   10737418240
> +   5368709120
> +   
> +diff --git a/tests/test_storage.py b/tests/test_storage.py
> +index ee33ab32e..ba0e4e711 100644
> +--- a/tests/test_storage.py
>  b/tests/test_storage.py
> +@@ -65,11 +65,6 @@ def createVol(conn, poolobj, volname=None, 
> input_vol=None, clone_vol=None):
> + if volname is None:
> + volname = poolobj.name() + "-vol"
> + 
> +-# Format here depends on libvirt-1.2.0 and later
> +-if clone_vol and conn.local_libvirt_version() < 1002000:
> +-log.debug("skip clone compare")
> +-return
> +-
> + alloc = 5 * 1024 * 1024 * 1024
> + cap = 10 * 1024 * 1024 * 1024
> + vol_inst = StorageVolume(conn)
> +@@ -91,6 +86,12 @@ def createVol(conn, poolobj, volname=None, 
> input_vol=None, clone_vol=None):
> + 
> + vol_inst.validate()
> + filename = os.path.join(BASEPATH, vol_inst.name + ".xml")
> ++
> ++# Format here depends on libvirt-7.2.0 and 

Bug#1005468: git-buildpackage: FTBFS: XXX

[Guido Günther]

control: reassign -1 pydoctor
control: force-merge 1005338 -1
control: affcts -1 git-buildpackage
thanks

Hi Lucas,
> >   Tag <>
> >   File "/usr/lib/python3/dist-packages/twisted/web/_flatten.py", line 321, 
> > in _flattenTree
> > element = next(stack[-1])
> >   File "/usr/lib/python3/dist-packages/twisted/web/_flatten.py", line 237, 
> > in _flattenElement
> > result = renderMethod(request, rootClone)
> >   File 
> > "/usr/lib/python3/dist-packages/pydoctor/templatewriter/pages/functionchild.py",
> >  line 73, in functionBody
> > return self.docgetter.get(self.ob)
> >   File 
> > "/usr/lib/python3/dist-packages/pydoctor/templatewriter/pages/__init__.py", 
> > line 71, in get
> > return epydoc2stan.format_docstring(ob)
> >   File "/usr/lib/python3/dist-packages/pydoctor/epydoc2stan.py", line 744, 
> > in format_docstring
> > fh.handle(Field.from_epydoc(field, source))
> >   File "/usr/lib/python3/dist-packages/pydoctor/epydoc2stan.py", line 600, 
> > in handle
> > m(field)
> >   File "/usr/lib/python3/dist-packages/pydoctor/epydoc2stan.py", line 529, 
> > in handle_type
> > self.types[name] = field.format()
> >   File "/usr/lib/python3/dist-packages/pydoctor/epydoc2stan.py", line 353, 
> > in format
> > return self.body.to_stan(_EpydocLinker(self.source))
> >   File "/usr/lib/python3/dist-packages/pydoctor/epydoc/markup/__init__.py", 
> > line 134, in to_stan
> > self._stan = Tag('', children=node2stan.node2stan(self.to_node(), 
> > docstring_linker).children)
> >   File "/usr/lib/python3/dist-packages/pydoctor/node2stan.py", line 42, in 
> > node2stan
> > return html2stan(''.join(html))
> >   File "/usr/lib/python3/dist-packages/pydoctor/stanutils.py", line 30, in 
> > html2stan
> > stan = XMLString(b'%s' % html).load()[0]
> >   File "/usr/lib/python3/dist-packages/twisted/web/template.py", line 402, 
> > in __init__
> > self._loadedTemplate = _flatsaxParse(NativeStringIO(s))
> >   File "/usr/lib/python3/dist-packages/twisted/web/template.py", line 356, 
> > in _flatsaxParse
> > parser.parse(fl)
> >   File "/usr/lib/python3.9/xml/sax/expatreader.py", line 111, in parse
> > xmlreader.IncrementalParser.parse(self, source)
> >   File "/usr/lib/python3.9/xml/sax/xmlreader.py", line 125, in parse
> > self.feed(buffer)
> >   File "/usr/lib/python3.9/xml/sax/expatreader.py", line 221, in feed
> > self._err_handler.fatalError(exc)
> >   File "/usr/lib/python3.9/xml/sax/handler.py", line 38, in fatalError
> > raise exception
> > SAXParseException: :1:46: undefined entity
> > 
> > make[3]: *** [Makefile:30: apidocs] Error 1

That's a problem in one of the build-deps as far as I can tell.

Cheers,
 -- Guido

Bug#991036: [Debian-on-mobile-maintainers] Bug#991036: libhandy: Should this package be removed in bookworm?

[Guido Günther]

Hi,
On Wed, Feb 09, 2022 at 06:27:50AM +0200, Adrian Bunk wrote:
> Control: severity -1 serious
> 
> libhandy is about to be removed from bookworm due to this,
> gnome-authenticator and gnome-metronome need to be updated.

Just to confirm: I think removal is fine, this API version is
unmaintained upstream and libhandy-1 and libadwaita are in Debian.
Cheers,
 -- Guido

Bug#1001965: Fails to build from source due to outdated symbols file

[Guido Günther]

Source: libdrm
Version: 2.4.109-1
Severity: serious
Tags: patch

Hi,
2.4.109-1 fails to build like:

dpkg-gensymbols: warning: debian/libdrm-amdgpu1/DEBIAN/symbols doesn't match 
completely debian/libdrm-amdgpu1.symbols
--- debian/libdrm-amdgpu1.symbols (libdrm-amdgpu1_2.4.109-1_amd64)
+++ dpkg-gensymbolsRbfBrW   2021-12-18 17:31:37.021023907 +
@@ -53,6 +53,7 @@
  amdgpu_cs_wait_fences@Base 2.4.81
  amdgpu_cs_wait_semaphore@Base 2.4.67
  amdgpu_device_deinitialize@Base 2.4.63
+ amdgpu_device_get_fd@Base 2.4.109-1
  amdgpu_device_initialize@Base 2.4.63
  amdgpu_find_bo_by_cpu_mapping@Base 2.4.94
  amdgpu_get_marketing_name@Base 2.4.73
dh_makeshlibs: error: failing due to earlier errors
make[1]: *** [debian/rules:121: override_dh_makeshlibs] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:141: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2

Full log: 
https://buildd.debian.org/status/fetch.php?pkg=libdrm=amd64=2.4.109-1=1639848700=0

Attached patch fixes that for me and I'm happy to NMU if that looks
correct. The symbol got added in
f70e8ae83590d2a1fb1972dc7e875dd6a9355b77 upstream and looks like a valid new
public symbol.

Cheers,
 -- Guido
 

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 0ecc96a5514e030a91be47d62febf7e656170fff Mon Sep 17 00:00:00 2001
Message-Id: <0ecc96a5514e030a91be47d62febf7e656170fff.1639931516.git@sigxcpu.org>
From: =?UTF-8?q?Guido=20G=C3=BCnther?= 
Date: Sun, 19 Dec 2021 17:22:10 +0100
Subject: [PATCH] Update symbols file

---
 debian/libdrm-amdgpu1.symbols | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/libdrm-amdgpu1.symbols b/debian/libdrm-amdgpu1.symbols
index 6ce3d569..d04300e8 100644
--- a/debian/libdrm-amdgpu1.symbols
+++ b/debian/libdrm-amdgpu1.symbols
@@ -53,6 +53,7 @@ libdrm_amdgpu.so.1 libdrm-amdgpu1 #MINVER#
  amdgpu_cs_wait_fences@Base 2.4.81
  amdgpu_cs_wait_semaphore@Base 2.4.67
  amdgpu_device_deinitialize@Base 2.4.63
+ amdgpu_device_get_fd@Base 2.4.109
  amdgpu_device_initialize@Base 2.4.63
  amdgpu_find_bo_by_cpu_mapping@Base 2.4.94
  amdgpu_get_marketing_name@Base 2.4.73
-- 
2.33.0

Bug#997719: marked as pending in libvirt-python

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #997719 in libvirt-python 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/libvirt-team/libvirt-python/-/commit/f2bb55f50126ba928ee245749d87a06d3ce2e7e7


New upstream release (Closes: #997719)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997719

Bug#998569: marked as pending in phosh

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #998569 in phosh 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/DebianOnMobile-team/phosh/-/commit/7007d29f079678ebc1da228cac7dc49a690c1305


Backport fixes for meson 0.60.0 from phosh 0.14.0

Closes: #998569


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/998569

Bug#998573: [git-buildpackage/master] tests: Make sure DEBEMAIL is set

[Guido Günther]

tag 998573 pending
thanks

Date:   Fri Nov 5 10:12:20 2021 +0100
Author: Guido Günther 
Commit ID: 196a9eec12a5124e9905e01f85d32f45b6e29894
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=196a9eec12a5124e9905e01f85d32f45b6e29894
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=196a9eec12a5124e9905e01f85d32f45b6e29894

tests: Make sure DEBEMAIL is set

Otherwise dch based tests fail

Closes: #998573

  

Bug#998569: [Debian-on-mobile-maintainers] Bug#998569: phosh: FTBFS: ../subprojects/libcall-ui/meson.build:1:0: ERROR: In subproject libcall-ui: Unknown options: "libcall-ui:package_name, libcall-ui:p

[Guido Günther]

control: fixed -1 phosh/0.14.0-1

Hi,
On Thu, Nov 04, 2021 at 08:44:02PM +0100, Lucas Nussbaum wrote:
> Source: phosh
> Version: 0.13.1-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211104 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Triggered by meson 0.60.0. Fixed in 0.14.0 (in experimental).
Cheers,
 -- Guido

> 
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > dh_auto_configure -- -Dphoc_tests=disabled -Dsystemd=false -Dgtk_doc=true
> > cd _build && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload 
> > --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var 
> > --libdir=lib/x86_64-linux-gnu -Dphoc_tests=disabled -Dsystemd=false 
> > -Dgtk_doc=true
> > The Meson build system
> > Version: 0.60.1
> > Source dir: /<>
> > Build dir: /<>/_build
> > Build type: native build
> > Project name: phosh
> > Project version: 0.13.1
> > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) 
> > 11.2.0")
> > C linker for the host machine: cc ld.bfd 2.37
> > Host machine cpu family: x86_64
> > Host machine cpu: x86_64
> > Compiler for C supports arguments -Wcast-align: YES 
> > Compiler for C supports arguments -Wdate-time: YES 
> > Compiler for C supports arguments -Wdeclaration-after-statement: YES 
> > Compiler for C supports arguments -Werror=format-security -Werror=format=2: 
> > YES 
> > Compiler for C supports arguments -Wendif-labels: YES 
> > Compiler for C supports arguments -Werror=incompatible-pointer-types: YES 
> > Compiler for C supports arguments -Werror=missing-declarations: YES 
> > Compiler for C supports arguments -Werror=overflow: YES 
> > Compiler for C supports arguments -Werror=return-type: YES 
> > Compiler for C supports arguments -Werror=shift-count-overflow: YES 
> > Compiler for C supports arguments -Werror=shift-overflow=2: YES 
> > Compiler for C supports arguments -Werror=implicit-fallthrough=3: YES 
> > Compiler for C supports arguments -Wfloat-equal: YES 
> > Compiler for C supports arguments -Wformat-nonliteral: YES 
> > Compiler for C supports arguments -Wformat-security: YES 
> > Compiler for C supports arguments -Winit-self: YES 
> > Compiler for C supports arguments -Wmaybe-uninitialized: YES 
> > Compiler for C supports arguments -Wmissing-field-initializers: YES 
> > Compiler for C supports arguments -Wmissing-include-dirs: YES 
> > Compiler for C supports arguments -Wmissing-noreturn: YES 
> > Compiler for C supports arguments -Wnested-externs: YES 
> > Compiler for C supports arguments -Wno-missing-field-initializers: YES 
> > Compiler for C supports arguments -Wno-sign-compare: YES 
> > Compiler for C supports arguments -Wno-strict-aliasing: YES 
> > Compiler for C supports arguments -Wno-unused-parameter: YES 
> > Compiler for C supports arguments -Wold-style-definition: YES 
> > Compiler for C supports arguments -Wpointer-arith: YES 
> > Compiler for C supports arguments -Wredundant-decls: YES 
> > Compiler for C supports arguments -Wshadow: YES 
> > Compiler for C supports arguments -Wstrict-prototypes: YES 
> > Compiler for C supports arguments -Wswitch-default: YES 
> > Compiler for C supports arguments -Wswitch-enum: YES 
> > Compiler for C supports arguments -Wtype-limits: YES 
> > Compiler for C supports arguments -Wundef: YES 
> > Compiler for C supports arguments -Wunused-function: YES 
> > Configuring run using configuration
> > Found pkg-config: /usr/bin/pkg-config (0.29.2)
> > Run-time dependency gcr-3 found: YES 3.40.0
> > Run-time dependency glib-2.0 found: YES 2.70.0
> > Run-time dependency gio-2.0 found: YES 2.70.0
> > Run-time dependency gobject-2.0 found: YES 2.70.0
> > Run-time dependency gio-unix-2.0 found: YES 2.70.0
> > Run-time dependency gnome-desktop-3.0 found: YES 41.0
> > Run-time dependency gsettings-desktop-schemas found: YES 41.0
> > Run-time dependency gtk+-3.0 found: YES 3.24.30
> > Run-time dependency gtk+-wayland-3.0 found: YES 3.24.30
> > Run-time dependency gudev-1.0 found: YES 237
> > Run-time dependency libfeedback-0.0 found: YES 0.0.0
> > 
> > Executing subproject gvc 
> > 
> > gvc| Project name: gvc
> > gvc| Project version: undefined
> > gvc| C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) 
> > 11.2.0")
> > gvc| C linker for the host machine: cc ld.bfd 2.37
> > gvc| Dependency gio-2.0 found: YES 2.70.0 (cached)
> > gvc| Dependency gobject-2.0 found: YES 2.70.0 (cached)
> > gvc| Run-time dependency libpulse found: YES 15.0
> > gvc| Run-time dependency libpulse-mainloop-glib found: YES 15.0
> > gvc| Configuring config.h using configuration
> > gvc| Build targets in project: 1
> > gvc| Subproject gvc finished.
> > 
> > Run-time dependency libhandy-1 found: YES 1.4.0
> > 
> > Executing subproject libcall-ui 
> > 
> > 
> > ../subprojects/libcall-ui/meson.build:1:0: ERROR: In subproject libcall-ui: 
> > Unknown options: 

Bug#996313: marked as pending in ruby-libvirt

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #996313 in ruby-libvirt 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/libvirt-team/ruby-libvirt/-/commit/197454a43bd8c2c562ba698ed94ab00f76aeaf88


Fix FTBFS with Ruby 3.0

  * d/patches/996313-fix-ext-build-with-ruby3.patch: Add patch.
- Use 'include ' to fix build with Ruby 3 (closes: #996313).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996313

Bug#996500: wlroots FTBFS: error: ‘av_init_packet’ is deprecated [-Werror=deprecated-declarations]

[Guido Günther]

control: -1 fixed wlroots/0.14.1-1

Bug#996500: wlroots FTBFS: error: ‘av_init_packet’ is deprecated [-Werror=deprecated-declarations]

[Guido Günther]

Hi,
This is fixed in experimental which should go to unstable soon.
Otherwise I'll backport upstream commit
6230f7be4f92b83df7ea8e6487410b3b81dd4b1d
Cheers,
 -- Guido

On Thu, Oct 14, 2021 at 07:54:13PM +0200, Helmut Grohne wrote:
> Source: wlroots
> Version: 0.12.0-2
> Severity: serious
> Tags: ftbfs
> 
> wlroots fails to build from source in unstable on amd64. A non-parallel
> build now ends as follows:
> 
> | FAILED: examples/dmabuf-capture.p/dmabuf-capture.c.o
> | cc -Iexamples/dmabuf-capture.p -Iexamples -I../examples -Iprotocol 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libdrm 
> -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
> -Werror -std=c11 -DWLR_USE_UNSTABLE -Wundef -Wlogical-op 
> -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
> -Wstrict-prototypes -Wimplicit-fallthrough=2 -Wendif-labels 
> -Wstrict-aliasing=2 -Woverflow -Wmissing-prototypes -Wno-missing-braces 
> -Wno-missing-field-initializers -Wno-unused-parameter -fmacro-prefix-map=../= 
> -DLIBINPUT_MAJOR=1 -DLIBINPUT_MINOR=19 -DLIBINPUT_PATCH=1 
> '-DICONDIR="/usr/share/icons"' -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -pthread -MD -MQ 
> examples/dmabuf-capture.p/dmabuf-capture.c.o -MF 
> examples/dmabuf-capture.p/dmabuf-capture.c.o.d -o 
> examples/dmabuf-capture.p/dmabuf-capture.c.o -c ../examples/dmabuf-capture.c
> | ../examples/dmabuf-capture.c: In function ‘vid_encode_thread’:
> | ../examples/dmabuf-capture.c:494:25: error: ‘av_init_packet’ is deprecated 
> [-Werror=deprecated-declarations]
> |   494 | av_init_packet();
> |   | ^~
> | In file included from /usr/include/x86_64-linux-gnu/libavcodec/bsf.h:30,
> |  from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:44,
> |  from 
> /usr/include/x86_64-linux-gnu/libavformat/avformat.h:312,
> |  from ../examples/dmabuf-capture.c:2:
> | /usr/include/x86_64-linux-gnu/libavcodec/packet.h:488:6: note: declared here
> |   488 | void av_init_packet(AVPacket *pkt);
> |   |  ^~
> | cc1: all warnings being treated as errors
> | ninja: build stopped: subcommand failed.
> | dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 
> -v returned exit code 1
> | make: *** [debian/rules:7: binary] Error 25
> | dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
> status 2
> 
> Helmut
> 

Bug#991036: [Debian-on-mobile-maintainers] Bug#991036: libhandy: Should this package be removed in bookworm?

[Guido Günther]

Hi,
On Tue, Jul 13, 2021 at 01:36:17PM +0300, Adrian Bunk wrote:
> Source: libhandy
> Version: 0.0.13-3
> Severity: serious
> Tags: bookworm sid
> 
> A more recent version is already available in src:libhandy-1.
> 
> Both versions will be in bullseye, but still shipping both in
> bookworm would feel wrong.
> 
> Please reply in case I am wrong here.

I think you're right. All rdeps should have been migrated by then as
well. I'll recheck once sid sees more updates again past release.
Cheers,
 -- Guido

> 
> ___
> Debian-on-mobile-maintainers mailing list
> debian-on-mobile-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers
> 

Bug#936935: [Pkg-libvirt-maintainers] Bug#936935: libvirt-sandbox: Python2 removal in sid/bullseye

[Guido Günther]

Hi,
On Sat, May 01, 2021 at 03:07:50AM +0200, Christoph Anton Mitterer wrote:
> Hey.
> 
> AFAICS, all python script have been adapted to Python3 upstream (or
> dropped)... so I guess this could be solved by upgrading to the current
> version.

Since upstream is pretty inactive i wonder if we should just drop it, it
won't be in bullseye either and popcon is fairly low:

   https://qa.debian.org/popcon.php?package=libvirt-sandbox

Cheers,
 -- Guido

> 
> 
> Cheers,
> Chris.
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
> 

Bug#982790: wlroots: started transition during soft freeze?

[Guido Günther]

Hi Sebastian,
On Sun, Feb 14, 2021 at 02:49:27PM +0100, Sebastian Ramacher wrote:
> Source: wlroots
> Version: 0.12.0-2
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> 
> The upload of 0.12.0-2 just started a transition. Note that we are in
> soft freeze and hence transitions are no longer acceptable for bullseye.
> The purpose of this bug is to block wlroots from migrating to testing.
> 
> Please either revert to 0.11.0 or keep this bug open until after the
> release of bullseye.

Right, that should have never happened. See my remark here:

  https://salsa.debian.org/swaywm-team/wlroots/-/merge_requests/5#note_227964

I've already contacted nicoo since i have no idea why was the intention here.

Cheers,
 -- Guido
 

> Cheers
> -- 
> Sebastian Ramacher
> 

Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

[Guido Günther]

Hi,
On Sun, Jan 31, 2021 at 11:41:07PM +0100, Jochen Sprickerhof wrote:
> * Guido Günther  [2021-01-31 13:19]:
> > Awesome. I had fixed the rpm parts here already
> > https://github.com/agx/git-buildpackage/tree/rpm but went for your
> > patches so your work is not lost. The reason i wrote 'tip of the
> > iceberg' is that the component tests need fixing as well - that's the bit
> > still missing - so tests still fail when the testdata for the component
> > tests is there (`git submodule update --init --recursive`).
> 
> Ha, I missed those. Attached one patch for GBP
> (gbp-rpm-Fix-tags-in-rpm-spec-files.patch)
> and three for the rpm-testdata repo to make all tests work.

All applied now. Thanks!
 -- Guido

> 
> Cheers Jochen

> From 3da6cd3af18d51cce569f2ee829356c8bbdb9392 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Sun, 31 Jan 2021 22:40:00 +0100
> Subject: [PATCH] rpm: Fix tags in rpm spec files
> 
> ---
>  tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec   |  6 +++---
>  tests/data/rpm/specs/gbp-test2-reference.spec  | 11 +--
>  tests/data/rpm/specs/gbp-test2-reference2.spec | 15 +++
>  tests/data/rpm/specs/gbp-test3.spec|  2 +-
>  4 files changed, 16 insertions(+), 18 deletions(-)
> 
> diff --git a/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec 
> b/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
> index 8a92725..d5b8763 100644
> --- a/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
> +++ b/tests/data/rpm/rpmbuild/SPECS/gbp-test2.spec
> @@ -6,10 +6,10 @@ Release:0
>  Group:  Development/Libraries
>  License:GPLv2
>  Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
> -Source: foo.txt
> +Source0:foo.txt
>  Source20:   bar.tar.gz
> -# Gbp-Ignore-Patches: -1
> -Patch:  my.patch
> +# Gbp-Ignore-Patches: 0
> +Patch0: my.patch
>  Patch10:my2.patch
>  Patch20:my3.patch
>  Packager:   Markus Lehtonen 
> diff --git a/tests/data/rpm/specs/gbp-test2-reference.spec 
> b/tests/data/rpm/specs/gbp-test2-reference.spec
> index 1882131..5e1f176 100644
> --- a/tests/data/rpm/specs/gbp-test2-reference.spec
> +++ b/tests/data/rpm/specs/gbp-test2-reference.spec
> @@ -6,12 +6,12 @@ Release:0
>  Group:  Development/Libraries
>  License:GPLv2
>  Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
> -Source: foo.txt
> +Source0:foo.txt
>  Source20:   bar.tar.gz
> -# Gbp-Ignore-Patches: -1
> -Patch:  my.patch
> +# Gbp-Ignore-Patches: 0
> +Patch0: my.patch
>  # Patches auto-generated by git-buildpackage:
> -Patch0: new.patch
> +Patch1: new.patch
>  Packager:   Markus Lehtonen 
>  
>  %description
> @@ -27,14 +27,13 @@ Empty subpackage for the %{name} test package.
>  %prep
>  %setup -T -n %{name}-%{version} -c -a 10
>  
> -%patch
>  
>  echo "Do things"
>  
>  # Gbp-Patch-Macros
>  # new.patch
>  %if 1
> -%patch0 -p1
> +%patch1 -p1
>  %endif
>  
>  %build
> diff --git a/tests/data/rpm/specs/gbp-test2-reference2.spec 
> b/tests/data/rpm/specs/gbp-test2-reference2.spec
> index d41f450..32bbe97 100644
> --- a/tests/data/rpm/specs/gbp-test2-reference2.spec
> +++ b/tests/data/rpm/specs/gbp-test2-reference2.spec
> @@ -6,13 +6,13 @@ Release:0
>  Group:  Development/Libraries
>  License:GPLv2
>  Source10:   ftp://ftp.host.com/%{name}-%{version}.tar.gz
> -Source: foo.txt
> +Source0:foo.txt
>  Source20:   bar.tar.gz
> -# Gbp-Ignore-Patches: -1
> -Patch:  my.patch
> +# Gbp-Ignore-Patches: 0
> +Patch0: my.patch
>  # Patches auto-generated by git-buildpackage:
> -Patch0: 1.patch
> -Patch1: 2.patch
> +Patch1: 1.patch
> +Patch2: 2.patch
>  Packager:   Markus Lehtonen 
>  VCS:myvcstag
>  
> @@ -29,18 +29,17 @@ Empty subpackage for the %{name} test package.
>  %prep
>  %setup -T -n %{name}-%{version} -c -a 10
>  
> -%patch
>  
>  echo "Do things"
>  
>  # Gbp-Patch-Macros
>  # 1.patch
>  %if true
> -%patch0 -p1
> +%patch1 -p1
>  %endif
>  # 2.patch
>  %ifarch %ix86
> -%patch1 -p1
> +%patch2 -p1
>  %endif
>  
>  %build
> diff --git a/tests/data/rpm/specs/gbp-test3.spec 
> b/tests/data/rpm/specs/gbp-test3.spec
> index c0c20c8..043afec 100644
> --- a/tests/data/rpm/specs/gbp-test3.spec
> +++ b/tests/data/rpm/specs/gbp-test3.spec
> @@ -6,7 +6,7 @@ Group:  Development/Libraries
>  License:GPLv2
>  Source: %{name}-%{version}.tar.gz
>  # Gbp-Ignore-Patches: 10
> -Patch:  my.patch
> +Patch0: my.patch
>  Patch10:my2.patch
>  Patch20:my3.patch
>  
> -- 
> 2.30.0
> 

> From 6753fd1cb848ef

Bug#981435: marked as pending in libvirt

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #981435 in libvirt 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/libvirt-team/libvirt/-/commit/8048eefbdcbeab748a98c636f13fe8e166eec4c2


control: Always use versioned deps for libvirt components

libvirt packaging is fairly modularized because we want users
to be able to tailor the installation to their needs by deciding
which components to include and which ones to leave out, but
mixing and matching different versions is very much not intended
to work.

Right now we're not always enforcing this tight coupling, and
that can result in failures at runtime, especially during
upgrades. Let's address the problem by making sure all
dependencies between libvirt components are versioned.

Closes: #981435


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/981435

Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

[Guido Günther]

Hi,
On Sat, Jan 30, 2021 at 09:13:07PM +0100, Jochen Sprickerhof wrote:
> Control: tags -1 + patch
> 
> Hi Guido,
> 
> * Guido Günther  [2021-01-27 12:08]:
> > Hi,
> > On Wed, Jan 20, 2021 at 09:37:56PM +0100, Lucas Nussbaum wrote:
> > > Source: git-buildpackage
> > > Version: 0.9.21
> > > Severity: serious
> > > Justification: FTBFS on amd64
> > > Tags: bullseye sid ftbfs
> > > Usertags: ftbfs-20210120 ftbfs-bullseye
> > > 
> > > Hi,
> > > 
> > > During a rebuild of all packages in sid, your package failed to build
> > > on amd64.
> > 
> > That is basically the top of the iceberg. Besides lots of places now
> > returning strings instead of bytes rpm became stricter in spec file
> > parsing breaking the test suite (and usage).
> 
> I fixed those in the attached patches.
> Note that I was not able to reproduce #980256 but explicitly tested on armhf
> and added an extra patch, so that bug should be fine.

Awesome. I had fixed the rpm parts here already
https://github.com/agx/git-buildpackage/tree/rpm but went for your
patches so your work is not lost. The reason i wrote 'tip of the
iceberg' is that the component tests need fixing as well - that's the bit
still missing - so tests still fail when the testdata for the component
tests is there (`git submodule update --init --recursive`).

Cheers,
 -- Guido


> IMHO #914314 could be downgraded again, I did not look into fixing it.
> 
> I can do an NMU as well if you are short on time.
> Would be happy to see a new git-buildpackage transition to testing.
> 
> Cheers Jochen

> From bce1d5f6d2e94788aea48731bb0c426e648dd673 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Sat, 30 Jan 2021 15:02:58 +0100
> Subject: [PATCH 1/5] Stop decoding strings (not needed in Python 3)
> 
> ---
>  gbp/rpm/__init__.py | 23 +--
>  1 file changed, 9 insertions(+), 14 deletions(-)
> 
> diff --git a/gbp/rpm/__init__.py b/gbp/rpm/__init__.py
> index 61d9d35..1d7a9ef 100644
> --- a/gbp/rpm/__init__.py
> +++ b/gbp/rpm/__init__.py
> @@ -34,11 +34,6 @@ from gbp.rpm.linkedlist import LinkedList
>  from gbp.rpm.lib_rpm import librpm, get_librpm_log
>  
>  
> -def _decode(s):
> -if s is not None:
> -return s.decode()
> -
> -
>  class NoSpecError(Exception):
>  """Spec file parsing error"""
>  pass
> @@ -79,8 +74,8 @@ class SrcRpmFile(object):
>  @property
>  def version(self):
>  """Get the (downstream) version of the RPM package"""
> -version = 
> dict(upstreamversion=self.rpmhdr[librpm.RPMTAG_VERSION].decode(),
> -   release=self.rpmhdr[librpm.RPMTAG_RELEASE].decode())
> +version = dict(upstreamversion=self.rpmhdr[librpm.RPMTAG_VERSION],
> +   release=self.rpmhdr[librpm.RPMTAG_RELEASE])
>  if self.rpmhdr[librpm.RPMTAG_EPOCH] is not None:
>  version['epoch'] = str(self.rpmhdr[librpm.RPMTAG_EPOCH])
>  return version
> @@ -88,17 +83,17 @@ class SrcRpmFile(object):
>  @property
>  def name(self):
>  """Get the name of the RPM package"""
> -return self.rpmhdr[librpm.RPMTAG_NAME].decode()
> +return self.rpmhdr[librpm.RPMTAG_NAME]
>  
>  @property
>  def upstreamversion(self):
>  """Get the upstream version of the RPM package"""
> -return self.rpmhdr[librpm.RPMTAG_VERSION].decode()
> +return self.rpmhdr[librpm.RPMTAG_VERSION]
>  
>  @property
>  def packager(self):
>  """Get the packager of the RPM package"""
> -return _decode(self.rpmhdr[librpm.RPMTAG_PACKAGER])
> +return self.rpmhdr[librpm.RPMTAG_PACKAGER]
>  
>  def unpack(self, dest_dir):
>  """
> @@ -168,13 +163,13 @@ class SpecFile(object):
>  
>  # Other initializations
>  source_header = self._specinfo.packages[0].header
> -self.name = source_header[librpm.RPMTAG_NAME].decode()
> -self.upstreamversion = source_header[librpm.RPMTAG_VERSION].decode()
> -self.release = source_header[librpm.RPMTAG_RELEASE].decode()
> +self.name = source_header[librpm.RPMTAG_NAME]
> +self.upstreamversion = source_header[librpm.RPMTAG_VERSION]
> +self.release = source_header[librpm.RPMTAG_RELEASE]
>  # rpm-python returns epoch as 'long', convert that to string
>  self.epoch = str(source_header[librpm.RPMTAG_EPOCH]) \
>  if source_header[librpm.RPMTAG_EPOCH] is not Non

Bug#980637: git-buildpackage: FTBFS: AttributeError: 'str' object has no attribute 'decode'

[Guido Günther]

Hi,
On Wed, Jan 20, 2021 at 09:37:56PM +0100, Lucas Nussbaum wrote:
> Source: git-buildpackage
> Version: 0.9.21
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210120 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

That is basically the top of the iceberg. Besides lots of places now
returning strings instead of bytes rpm became stricter in spec file
parsing breaking the test suite (and usage).

> 
> Relevant part (hopefully):
> > make[2]: Entering directory '/<>'
> > flake8 
> > flake8  examples/gbp-add-patch examples/zeitgeist-git.py
> > export GIT_AUTHOR_NAME="Gbp Tests"; \
> > export GIT_AUTHOR_EMAIL=te...@example.com;  \
> > export GIT_COMMITTER_NAME=$GIT_AUTHOR_NAME; \
> > export GIT_COMMITTER_EMAIL=$GIT_AUTHOR_EMAIL;   \
> > PYTHONPATH=.\
> > LC_ALL=C.UTF-8 python3 setup.py nosetests --with-xcoverage
> > running nosetests
> > running egg_info
> > creating gbp.egg-info
> > writing gbp.egg-info/PKG-INFO
> > writing dependency_links to gbp.egg-info/dependency_links.txt
> > writing entry points to gbp.egg-info/entry_points.txt
> > writing requirements to gbp.egg-info/requires.txt
> > writing top-level names to gbp.egg-info/top_level.txt
> > writing manifest file 'gbp.egg-info/SOURCES.txt'
> > reading manifest file 'gbp.egg-info/SOURCES.txt'
> > writing manifest file 'gbp.egg-info/SOURCES.txt'
> > Coverage.py warning: --include is ignored because --source is set 
> > (include-ignored)
> > Doctest: gbp.command_wrappers.Command.__call__ ... ok
> > Doctest: gbp.command_wrappers.Command._f ... ok
> > Doctest: gbp.command_wrappers.Command.call ... ok
> > Doctest: gbp.config.GbpOptionParser._listify ... ok
> > Doctest: gbp.config.GbpOptionParser._name_to_filename ... ok
> > Doctest: gbp.config.GbpOptionParser.get_config_files ... ok
> > Doctest: gbp.deb.format.DebianSourceFormat ... ok
> > Doctest: gbp.deb.format.DebianSourceFormat.parse_file ... ok
> > Doctest: gbp.deb.git.DebianGitRepository._build_legacy_tag ... ok
> > Doctest: gbp.deb.git.DebianGitRepository._mangle_version ... ok
> > Doctest: gbp.deb.git.DebianGitRepository._sanitize_version ... ok
> > Doctest: gbp.deb.git.DebianGitRepository._unsanitize_version ... ok
> > Doctest: gbp.deb.git.DebianGitRepository.tag_to_version ... ok
> > Doctest: gbp.deb.git.DebianGitRepository.version_to_tag ... ok
> > Doctest: gbp.deb.policy.DebianPkgPolicy ... ok
> > Doctest: gbp.deb.policy.DebianPkgPolicy.build_tarball_name ... ok
> > Doctest: gbp.deb.uscan.Uscan._parse ... ok
> > Doctest: gbp.deb.uscan.Uscan._parse_uptodate ... ok
> > Doctest: gbp.deb.uscan.Uscan._raise_error ... ok
> > Doctest: gbp.format.format_b ... ok
> > Doctest: gbp.format.format_str ... ok
> > Doctest: gbp.git.args.GitArgs ... ok
> > Doctest: gbp.git.commit.GitCommit.is_sha1 ... ok
> > Doctest: gbp.git.modifier.GitModifier.get_author_env ... ok
> > Doctest: gbp.git.modifier.GitModifier.get_committer_env ... ok
> > Doctest: gbp.git.repository.GitRepository.strip_sha1 ... ok
> > Doctest: gbp.git.rfc822_date_to_git ... ok
> > Doctest: gbp.patch_series.Patch._get_subject_from_filename ... ok
> > Doctest: gbp.patch_series.PatchSeries._get_topic ... ok
> > Doctest: gbp.patch_series.PatchSeries._parse_line ... ok
> > Doctest: gbp.patch_series.PatchSeries._read_series ... ok
> > Doctest: gbp.patch_series.PatchSeries._split_strip ... ok
> > Doctest: gbp.patch_series.PatchSeries._strip_comment ... ok
> > Doctest: gbp.pkg.archive.Archive.parse_filename ... ok
> > Doctest: gbp.pkg.compressor.Compressor.__repr__ ... ok
> > Doctest: gbp.pkg.compressor.Compressor.cmdline ... ok
> > Doctest: gbp.pkg.git.PkgGitRepository.sanitize_prefix ... ok
> > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.guess_upstream_src_version ... ok
> > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.is_valid_packagename ... ok
> > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.is_valid_upstreamversion ... ok
> > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.version_subst ... ok
> > Doctest: gbp.rpm.git.RpmGitRepository._sanitize_tag ... ok
> > Doctest: gbp.rpm.git.RpmGitRepository.version_to_tag ... ok
> > Doctest: gbp.rpm.linkedlist.LinkedList.append ... ok
> > Doctest: gbp.rpm.linkedlist.LinkedList.delete ... ok
> > Doctest: gbp.rpm.linkedlist.LinkedList.insert_after ... ok
> > Doctest: gbp.rpm.linkedlist.LinkedList.insert_before ... ok
> > Doctest: gbp.rpm.linkedlist.LinkedList.prepend ... ok
> > Doctest: gbp.rpm.linkedlist.LinkedListNode.set_data ... ok
> > Doctest: gbp.rpm.policy.RpmPkgPolicy.is_valid_orig_archive ... ok
> > Doctest: gbp.rpm.compose_version_str ... ok
> > Doctest: gbp.rpm.filter_version ... ok
> > Doctest: gbp.rpm.split_version_str ... ok
> > Doctest: gbp.rpm.string_to_int ... ok
> > Doctest: gbp.scripts.buildpackage.changes_file_suffix ... ok
> > Doctest: gbp.scripts.clone.repo_to_url ... ok
> > Doctest: gbp.scripts.common.pq.is_pq_branch ... ok
> > Doctest: 

Bug#957406: kmscube: ftbfs with GCC-10

[Guido Günther]

Version: kmscube/0.0.0~git20210103-1

Hi,
On Fri, Apr 17, 2020 at 11:03:44AM +, Matthias Klose wrote:
> Package: src:kmscube
> Version: 0.0.0~git20170617-2
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-10>
 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for the buster release.
> 
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc10-20200225/kmscube_0.0.0~git20170617-2_unstable_gcc10.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
> 
>   apt-get -t=experimental install g++ 
> 
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-10/porting_to.html
> 
> [...]
> dh clean
>dh_clean
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
> configure.ac:32: installing 'build-aux/compile'
> configure.ac:30: installing 'build-aux/install-sh'
> configure.ac:30: installing 'build-aux/missing'
> Makefile.am: installing 'build-aux/depcomp'
>dh_auto_configure
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
> --disable-dependency-tracking
> configure: WARNING: unrecognized options: --disable-maintainer-mode
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking whether make supports the include directive... yes (GNU style)
> checking dependency style of gcc... none
> checking whether make supports nested variables... (cached) yes
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for DRM... yes
> checking for GBM... yes
> checking for EGL... yes
> checking for GLES2... yes
> checking for GST... yes
> configure: Building cube-video support
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: executing depfiles commands
> configure: WARNING: unrecognized options: --disable-maintainer-mode
>dh_auto_build
>   make -j4
> make[1]: Entering directory '/<>'
> gcc -DPACKAGE_NAME=\"kmscube\" -DPACKAGE_TARNAME=\"kmscube\" 
> -DPACKAGE_VERSION=\"0.0.1\" -DPACKAGE_STRING=\"kmscube\ 0.0.1\" 
> -DPACKAGE_BUGREPORT=\"https://cgit.freedesktop.org/mesa/kmscube/\; 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"kmscube\" -DVERSION=\"0.0.1\" -DHAVE_GST=1 -I. 
>   -Wdate-time -D_FORTIFY_SOURCE=2 -O0 -g -Wall -Wextra -std=c99 
> -I/usr/include/libdrm-pthread -I/usr/include/gstreamer-1.0 
> -I/usr/include/orc-0.4 -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o kmscube-common.o `test -f 'common.c' || echo 
> './'`common.c
> gcc -DPACKAGE_NAME=\"kmscube\" -DPACKAGE_TARNAME=\"kmscube\" 
> -DPACKAGE_VERSION=\"0.0.1\" -DPACKAGE_STRING=\"kmscube\ 0.0.1\" 
> -DPACKAGE_BUGREPORT=\"https://cgit.freedesktop.org/mesa/kmscube/\; 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"kmscube\" -DVERSION=\"0.0.1\" -DHAVE_GST=1 -I. 
>   -Wdate-time -D_FORTIFY_SOURCE=2 -O0 -g -Wall -Wextra -std=c99 
> -I/usr/include/libdrm-pthread -I/usr/include/gstreamer-1.0 
> -I/usr/include/orc-0.4 

Bug#980256: git-buildpackage: autopkgtest armhf regression: /usr/bin/python: not found

[Guido Günther]

Hi Paul,

On Sat, Jan 16, 2021 at 08:48:19PM +0100, Paul Gevers wrote:
> Source: git-buildpackage
> Version: 0.9.21
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> With a recent upload of git-buildpackage the autopkgtest of
> git-buildpackage fails in testing on armhf when that autopkgtest is run
> with the binary packages of git-buildpackage from unstable. It passes
> when run with only packages from testing. In tabular form:
> 
>passfail
> git-buildpackage   from testing0.9.21
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [0] You can see what packages were added from the second line of the log
> file quoted below. The migration software adds source package from
> unstable to the list if they are needed to install packages from
> git-buildpackage/0.9.21. I.e. due to versioned dependencies or
> breaks/conflicts.
> [1] https://qa.debian.org/excuses.php?package=git-buildpackage
> 
> https://ci.debian.net/data/autopkgtest/testing/armhf/g/git-buildpackage/9735149/log.gz
> 
> + python3 -c import setuptools
> + mktemp -d
> + GBP_TEMPDIR=/tmp/tmp.thAvJcvD7A
> + gbp buildpackage-rpm --git-packaging-dir=packaging/
> --git-export-dir=/tmp/tmp.thAvJcvD7A -D%__python3 /usr/bin/python3
> -D%__python /usr/bin/python3 -bb --nodeps
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> sh: 1: /usr/bin/python: not found
> 

Bug#976914: git-buildpackage: FTBFS on ppc64el (arch:all-only src pkg): AssertionError: GitRepositoryError not raised

[Guido Günther]

Hi,
On Mon, Dec 21, 2020 at 12:00:01AM +0100, nicoo wrote:
> Control: tag -1 + patch
> Control: retitle -1 git-buildpackage FTBFS when /etc/lsb-release does not 
> exist
> 
> Hi,
> 
> On Wed, Dec 09, 2020 at 09:59:23AM +0100, Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build
> > on ppc64el. At the same time, it did not fail on amd64.
> > [...]
> > >  >> begin captured logging << 
> > > gbp: info: Failed to read OS release file /etc/lsb-release: [Errno 2] No 
> > > such file or directory: '/etc/lsb-release'
> > > gbp: debug: ['git', 'rev-parse', '--show-cdup']
> > > - >> end captured logging << -
> > > SKIP: Skipping 'tests.component', since this is not a git checkout.
> > >  >> begin captured logging << 
> 
> I was able to reproduce the issue on amd64, so you might want to remove
> the ftbfs-ppc64 usertag?  It is sufficient for /etc/lsb-release not to exist.
> 
> Please find enclosed 2 patches that solve the issue, at least in my 
> environment.
> You might want to check those on Ubuntu, but I believe it should work
> fine there.

Thanks! I've tweaked the first patch slightly since according to

https://packages.ubuntu.com/groovy/amd64/base-files

Ubuntu has /etc/os-release as well now. Pushed to master.
Cheers,
 -- Guido

> 
> 
> Best,
> 
>   nicoo

> From 21e2cf0c2fd66d2781659bc57b8246faf2a147d7 Mon Sep 17 00:00:00 2001
> From: nicoo 
> Date: Sun, 20 Dec 2020 23:35:57 +0100
> Subject: [PATCH 1/2] tests/11_test_dch_main.py: Don't expect /etc/lsb-release
>  on Debian
> 
> ---
>  tests/11_test_dch_main.py | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/11_test_dch_main.py b/tests/11_test_dch_main.py
> index 14cf593..f88959f 100644
> --- a/tests/11_test_dch_main.py
> +++ b/tests/11_test_dch_main.py
> @@ -9,16 +9,16 @@ from .testutils import (DebianGitTestRepo, OsReleaseFile, 
> skip_without_cmd,
>  from gbp.scripts import dch
>  
>  import os
> +import platform
>  import re
>  
>  # Older dch compatibility
>  default_urgency = get_dch_default_urgency()
>  
>  # For Ubuntu compatibility
> -os_release = OsReleaseFile('/etc/lsb-release')
> -
>  # OS release codename and snapshot of version 0.9-2~1
> -if os_release['DISTRIB_ID'] == 'Ubuntu':
> +if 'Ubuntu' in platform.version():
> +os_release = OsReleaseFile('/etc/lsb-release')
>  os_codename = os_release['DISTRIB_CODENAME']
>  snap_header_0_9 = 
> r'^test-package\s\(0.9-1ubuntu1~1\.gbp([0-9a-f]{6})\)\sUNRELEASED;\surgency=%s'
>  % default_urgency
>  new_version_0_9 = '0.9-1ubuntu1'
> -- 
> 2.29.2
> 

> From 971b0a622dcd1bc5ca5f3b4cd97470ff7799c0bc Mon Sep 17 00:00:00 2001
> From: nicoo 
> Date: Sun, 20 Dec 2020 23:43:27 +0100
> Subject: [PATCH 2/2] doctests/test_Changelog: Don't expect /etc/lsb-release
> 
> See #976914
> ---
>  tests/doctests/test_Changelog.py | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/doctests/test_Changelog.py 
> b/tests/doctests/test_Changelog.py
> index 1fb8a30..a1e4311 100644
> --- a/tests/doctests/test_Changelog.py
> +++ b/tests/doctests/test_Changelog.py
> @@ -262,7 +262,7 @@ def test_add_section():
>  >>> import shutil
>  >>> import gbp.deb.changelog
>  >>> from ..testutils import OsReleaseFile
> ->>> os_release = OsReleaseFile('/etc/lsb-release')
> +>>> os_release = OsReleaseFile()
>  >>> olddir = os.path.abspath(os.path.curdir)
>  >>> testdir = tempfile.mkdtemp(prefix='gbp-test-changelog-')
>  >>> testdebdir = os.path.join(testdir, 'debian')
> @@ -309,7 +309,7 @@ def test_add_entry():
>  >>> import shutil
>  >>> import gbp.deb.changelog
>  >>> from ..testutils import OsReleaseFile
> ->>> os_release = OsReleaseFile('/etc/lsb-release')
> +>>> os_release = OsReleaseFile()
>  >>> olddir = os.path.abspath(os.path.curdir)
>  >>> testdir = tempfile.mkdtemp(prefix='gbp-test-changelog-')
>  >>> testdebdir = os.path.join(testdir, 'debian')
> -- 
> 2.29.2
> 

Bug#974037: Fails to build on mipsel

[Guido Günther]

Package: src:rust-gtk
Version: 0.7.0-1
Severity: serious

rust-gtk fails to build on mipsel like:

https://buildd.debian.org/status/fetch.php?pkg=rust-gtk=mipsel=0.7.0-1=1596355821=0

The relevant bit seems to be

terminate called after throwing an instance of 'std::bad_alloc'
 what():  std::bad_alloc
error: could not compile `gtk`.

So i wonder if that can be handled by a give back on a machine with more
RAM?

Cheers,
 -- Guido


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#974036: Fails to build on mips64el

[Guido Günther]

Package: squeekboard
Version: 1.10.0-1
Severity: serious

squeekboard fails to build on mips64el like:

[16/58] /usr/bin/meson --internal msgfmthelper 
data/sm.puri.Squeekboard.desktop.in data/sm.puri.Squeekboard.desktop desktop 
../data/../po
msgfmt: ../data/../po/LINGUAS does not exist
[54/58] cc -Isrc/squeekboard.p -Isrc -I../src -I. -I.. -I../eek -Idata 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/mips64el-linux-gnuabi64/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/mips64el-linux-gnuabi64/dbus-1.0/include 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/libfeedback-0.0 -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -std=gnu11 -Werror=implicit-function-declaration 
-Werror=implicit-fallthrough=3 -Werror=maybe-uninitialized 
-Werror=missing-field-initializers -Werror=incompatible-pointer-types 
-Werror=int-conversion -Werror=redundant-decls -Werror=parentheses 
-Wformat-nonliteral -Wformat-security -Winit-self -Wmaybe-uninitialized 
-Wold-style-definition -Wredundant-decls -Wstrict-prototypes -Wunused-function 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
'-DTHEMESDIR="/usr/share/squeekboard/themes"' 
'-DKEYBOARDSDIR="/usr/share/squeekboard/keyboards"' -DEEKBOARD_COMPILATION=1 
-DEEK_COMPILATION=1 -MD -MQ src/squeekboard.p/server-main.c.o -MF 
src/squeekboard.p/server-main.c.o.d -o src/squeekboard.p/server-main.c.o -c 
../src/server-main.c
[55/58] /<>/cargo_build.sh --rename test_layout 
tools/squeekboard-test-layout --bin test_layout
   Compiling rs v0.1.0 (/<>/_build)
Finished dev [unoptimized + debuginfo] target(s) in 29.06s
[56/58] /<>/cargo.sh test --no-run
   Compiling rs v0.1.0 (/<>/_build)
Finished test [unoptimized + debuginfo] target(s) in 59.83s
[57/58] cc  -o src/squeekboard 
src/squeekboard.p/meson-generated_xdg-shell-protocol.c.o 
src/squeekboard.p/meson-generated_wlr-layer-shell-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_virtual-keyboard-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_input-method-unstable-v2-protocol.c.o 
src/squeekboard.p/meson-generated_text-input-unstable-v3-protocol.c.o 
src/squeekboard.p/meson-generated_.._.._data_squeekboard-resources.c.o 
src/squeekboard.p/server-main.c.o -Wl,--as-needed -Wl,--no-undefined -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--start-group 
src/liblibsqueekboard.a src/librs.a 
/usr/lib/mips64el-linux-gnuabi64/libgio-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libgobject-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libglib-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libgnome-desktop-3.so 
/usr/lib/mips64el-linux-gnuabi64/libgtk-3.so 
/usr/lib/mips64el-linux-gnuabi64/libgdk-3.so 
/usr/lib/mips64el-linux-gnuabi64/libpangocairo-1.0.so 
/usr/lib/mips64el-linux-gnuabi64/libpango-1.0.so 
/usr/lib/mips64el-linux-gnuabi64/libharfbuzz.so 
/usr/lib/mips64el-linux-gnuabi64/libatk-1.0.so 
/usr/lib/mips64el-linux-gnuabi64/libcairo-gobject.so 
/usr/lib/mips64el-linux-gnuabi64/libcairo.so 
/usr/lib/mips64el-linux-gnuabi64/libgdk_pixbuf-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libfeedback-0.0.so 
/usr/lib/mips64el-linux-gnuabi64/libwayland-client.so 
/usr/lib/mips64el-linux-gnuabi64/libxkbcommon.so -lm -lrt -ldl -lpthread 
-Wl,--end-group '-Wl,-rpath,$ORIGIN/' 
-Wl,-rpath-link,/<>/_build/src
FAILED: src/squeekboard 
cc  -o src/squeekboard src/squeekboard.p/meson-generated_xdg-shell-protocol.c.o 
src/squeekboard.p/meson-generated_wlr-layer-shell-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_virtual-keyboard-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_input-method-unstable-v2-protocol.c.o 
src/squeekboard.p/meson-generated_text-input-unstable-v3-protocol.c.o 
src/squeekboard.p/meson-generated_.._.._data_squeekboard-resources.c.o 
src/squeekboard.p/server-main.c.o -Wl,--as-needed -Wl,--no-undefined -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--start-group 
src/liblibsqueekboard.a src/librs.a 
/usr/lib/mips64el-linux-gnuabi64/libgio-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libgobject-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libglib-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libgnome-desktop-3.so 
/usr/lib/mips64el-linux-gnuabi64/libgtk-3.so 
/usr/lib/mips64el-linux-gnuabi64/libgdk-3.so 
/usr/lib/mips64el-linux-gnuabi64/libpangocairo-1.0.so 
/usr/lib/mips64el-linux-gnuabi64/libpango-1.0.so 

Bug#973350: Fails to start due to lack of dependency on gnome-shell-common

[Guido Günther]

Package: phosh
Version: 0.4.5
Severity: grave
Tags: patch

We use a setting from gnome-session so we need to depend on the schema:

Fix is at
https://source.puri.sm/Librem5/phosh/-/merge_requests/648

Cheers,
 -- Guido


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages phosh depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  fonts-lato   2.0-2
ii  gsettings-desktop-schemas3.38.0-2
ii  libc62.30-8
ii  libcairo21.16.0-4
ii  libfeedback-0.0-00.0.0+git20200726-1
ii  libgcr-base-3-1  3.38.0-1
ii  libgcr-ui-3-13.38.0-1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libglib2.0-0 2.66.0-2
ii  libgnome-desktop-3-193.38.0-2
ii  libgtk-3-0   3.24.23-2
ii  libhandy-1-0 1.0.0-2
ii  libnm0   1.26.2-1
ii  libpam0g 1.3.1-5
ii  libpango-1.0-0   1.46.2-1
ii  libpolkit-agent-1-0  0.105-29
ii  libpolkit-gobject-1-00.105-29
ii  libpulse-mainloop-glib0  13.0-5
ii  libpulse013.0-5
ii  libsecret-1-00.20.3-1
ii  libupower-glib3  0.99.11-2
ii  libwayland-client0   1.18.0-2~exp1.1
ii  phoc 0.4.4~1.gbp5fd950

Versions of packages phosh recommends:
ii  feedbackd 0.0.0+git20200726-1
ii  gnome-session 3.38.0-2
ii  iio-sensor-proxy  3.0-1

phosh suggests no packages.

-- no debconf information

Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: phosh: Shell doesn't start

[Guido Günther]

Hi,
On Sat, Aug 08, 2020 at 08:09:24PM +0200, Michel Le Bihan via 
Debian-on-mobile-maintainers wrote:
> Package: phosh
> Version: 0.4.3-1
> Severity: grave
> Justification: renders package unusable
> 
> Hello,
> 
> On a freshly created Debian sid live system:
> ```
> sudo mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video-
> all,phosh --arch amd64 sid debian-live-root http://ftp.pl.debian.org/debian/
> sudo chroot debian-live-root passwd
> sudo chroot debian-live-root useradd -m -s /bin/bash -p $(openssl passwd -1
> 123456) user
> sudo chroot debian-live-root systemctl enable phosh
> cp debian-live-root/vmlinuz .; cp debian-live-root/initrd.img .
> sudo mksquashfs debian-live-root root.squashfs -comp lz4
> python3 -m http.server -b localhost 8080
> qemu-system-x86_64 -machine accel=kvm -m 4G -device virtio-net-pci,netdev=net0
> -serial stdio -monitor vc -netdev
> user,id=net0,hostfwd=tcp::-:22,guestfwd=tcp:10.0.2.252:8080-tcp:localhost:8080,hostname=debian-
> live -kernel ./vmlinuz -initrd ./initrd.img -append "console=ttyS0
> ip=frommedia boot=live nopersistence
> fetch=http://10.0.2.252:8080/root.squashfs;
> ```
> (last command is to start the test VM)
> 
> Phosh doesn't start. On the console I see:
> ```
> traps: phoc[362] trap int3 ip:7f684a6d9585 sp:7ffccc2cfe90 error:0 in
> libglib-2.0.so.0.6400.4[7f684a69f000+81000]
> ```

Your VM likely DRM capable GPU (see e.g. drm_info).
 -- Guido

Bug#967153: krb5-auth-dialog: Unversioned Python removal in sid/bullseye

[Guido Günther]

Hi,
On Tue, Aug 04, 2020 at 09:28:15AM +, Matthias Klose wrote:
> Package: src:krb5-auth-dialog
> Version: 3.26.1-3
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2unversioned
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> We will keep some Python2 package as discussed in
> https://lists.debian.org/debian-python/2020/07/msg00039.html
> but removing the unversioned python packages python-minimal, python,
> python-dev, python-dbg, python-doc.
> 
> Your package either build-depends, depends on one of those packages.
> Please either convert these packages to Python3, or if that is not
> possible, replaces the dependencies on the unversioned Python
> packages with one of the python2 dependencies (python2, python2-dev,
> python2-dbg, python2-doc).
> 
> Please check for dependencies, build dependencies AND autopkg tests.

Can you say how the list was generated? krb5-auth-dialog does not seem
to depend on any of these.
Cheers,
 -- Guido

> 
> If there are questions, please refer to the wiki page for the removal:
> https://wiki.debian.org/Python/2Removal, or ask for help on IRC
> #debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#964040: [git-buildpackage/master] Make flake8 E741 happy

[Guido Günther]

tag 964040 pending
thanks

Date:   Wed Jul 1 14:46:11 2020 +0200
Author: Guido Günther 
Commit ID: 0bc42b4b0312fc965881409e619093cd0fb077f9
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=0bc42b4b0312fc965881409e619093cd0fb077f9
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=0bc42b4b0312fc965881409e619093cd0fb077f9

Make flake8 E741 happy

Closes: #964040

  

Bug#960762: [Pkg-libvirt-maintainers] Bug#960762: libvirt: random (?) test hangs

[Guido Günther]

Hi,
On Tue, Jun 30, 2020 at 09:28:34PM +0200, Andrea Bolognani wrote:
> On Sat, May 16, 2020 at 03:00:46PM +0300, Adrian Bunk wrote:
> > Source: libvirt
> > Version: 6.0.0-7
> > Severity: serious
> > Tags: ftbfs
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=libvirt=all=6.0.0-7=1589452859=0
> > https://buildd.debian.org/status/fetch.php?pkg=libvirt=i386=6.0.0-7=1589494701=0
> > 
> > ...
> > make  check-TESTS
> > make[4]: Entering directory '/<>/debian/build/tests'
> > make[5]: Entering directory '/<>/debian/build/tests'
> > PASS: sockettest
> > PASS: virbuftest
> > PASS: virhostcputest
> [...]
> > PASS: virsh-vcpupin
> > PASS: virsh-optparse
> > PASS: virt-aa-helper-test
> > E: Build killed with signal TERM after 150 minutes of inactivity
> 
> Has anyone managed to reproduce this? I've built 6.0.0-7 from source
> in a tight loop 100 times, both in a sid:i386 chroot via cowbuilder
> and in a sid:i386 VM, without encountering a single failure.

I tried to reproduce too when this came in and couldn't.
 -- Guido

> 
> The latest build attempt on i386 also failed:
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=libvirt=i386=6.4.0-1=1593097042=0
> 
> However, the failure in this case was not limited to i386 and the
> error was completely different, caused this time by
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963704
> 
> All I can think of at this point is a temporary glitch of the
> buildd. In a couple of weeks, when we upload 6.5.0, we'll hopefully
> see that build fine on all architectures, i386 included...
> 
> Does anyone have any better theories? Or a way to dig further?
> 
> -- 
> Andrea Bolognani 
> Resistance is futile, you will be garbage collected.



> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#948295: python-dateutils's autopkg tests fail / Update to 2.8.1 for Python 3.8

[Guido Günther]

Hi,
On Tue, Mar 31, 2020 at 03:59:28PM +0200, Thomas Goirand wrote:
> Hi!
> 
> Please accept and upload the merge request over her adressing this bug:
> 
> https://salsa.debian.org/agx/python-dateutil/-/merge_requests/1

That one would not build for me since the patches weren't rebased and the
so i just fixed it up myself. Uploaded now, sorry for the delay.
 -- Guido

> 
> Alternatively, ping me to NMU.
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 

Bug#955490: [Pkg-libvirt-maintainers] Bug#955490: libvirt-daemon: ERROR internal error: child reported (status=125): Kernel does not provide mount namespace: Permission denied

[Guido Günther]

control: severity -1 normal

Hi,
On Wed, Apr 01, 2020 at 04:39:34PM +0200, usuario wrote:
> Package: libvirt-daemon
> Version: 6.0.0-4
> Severity: grave
> Tags: a11y
> Justification: renders package unusable

certainly not unusable since others ore running just fine.
 -- Guido

> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> sudo virt-install \
> -n vm1 \
> -r 512 \
> --vcpus=2 \
> --os-variant=debiantesting \
> --disk /var/lib/libvirt/images/vm1.img,size=2 \
> --nographics \
> -l http://ftp.debian.org/debian/dists/testing/main/installer-amd64/ \
> -x console=ttyS0,115200
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Launch above command
> 
>* What was the outcome of this action?
> 
> Below error:
> 
> ERRORinternal error: child reported (status=125): Kernel does not provide 
> mount namespace: Permission denied
> 
>* What outcome did you expect instead?
> 
> A success message confirming I'm able to install the Virtual Machine
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libvirt-daemon depends on:
> ii  libblkid1   2.34-0.1
> ii  libc6   2.30-2
> ii  libcap-ng0  0.7.9-2.1+b2
> ii  libdbus-1-3 1.12.16-2
> ii  libdevmapper1.02.1  2:1.02.167-1+b1
> ii  libfuse22.9.9-3
> ii  libgcc-s1   10-20200324-1
> ii  libglib2.0-02.64.1-1
> ii  libnetcf1   1:0.2.8-1+b3
> ii  libparted2  3.3-4
> ii  libpcap0.8  1.9.1-2
> ii  libpciaccess0   0.14-1
> ii  libselinux1 3.0-1+b1
> ii  libudev1244.3-1
> ii  libvirt-daemon-driver-qemu  6.0.0-4
> ii  libvirt06.0.0-4
> ii  libxml2 2.9.10+dfsg-4
> 
> Versions of packages libvirt-daemon recommends:
> ii  libvirt-daemon-driver-lxc   6.0.0-4
> ii  libvirt-daemon-driver-vbox  6.0.0-4
> ii  libvirt-daemon-driver-xen   6.0.0-4
> ii  libxml2-utils   2.9.10+dfsg-4
> ii  netcat-openbsd  1.206-1
> ii  qemu-kvm1:4.2-3
> 
> Versions of packages libvirt-daemon suggests:
> pn  libvirt-daemon-driver-storage-gluster  
> pn  libvirt-daemon-driver-storage-rbd  
> pn  libvirt-daemon-driver-storage-zfs  
> ii  libvirt-daemon-system  6.0.0-4
> pn  numad  
> 
> -- debconf-show failed
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#954291: [Pkg-libvirt-maintainers] Bug#954291: libvirt-daemon-system-sysv: upgrading kills VMs

[Guido Günther]

Hi,
On Thu, Mar 19, 2020 at 08:18:04PM +0100, Thorsten Glaser wrote:
> Package: libvirt-daemon-system-sysv
> Version: 6.0.0-3
> Severity: critical
> Justification: causes serious data loss
> 
> Just a regular dist-upgrade doing this:
> 
> 
> Unpacking libvirt-daemon-system-sysv (6.0.0-3) over (6.0.0-1) ...
> […]
> Setting up libvirt-daemon-system-sysv (6.0.0-3) ...
> Restarting libvirt logging daemon: /usr/sbin/virtlogd.
> Restarting libvirt management daemon: /usr/sbin/libvirtd.
> 
> Running guests on default URI: MirBSD
> Shutting down guests on default URI...
> Starting shutdown on guest: MirBSD
> Waiting for guest MirBSD to shut down, 300 seconds left

Looks like a regression from the sysv split since this worked before,
could you check if this fixes it:

   
https://salsa.debian.org/libvirt-team/libvirt/-/commit/d7df842ce8649d88c9b242b9f4866c43016554b7

Cheers,
 -- Guido

> […]
> 
> 
> It’s inacceptable for a regular package upgrade to shut down
> any running VMs without warning. The VMs may be necessary, or
> might need to be shut down manually (qemu’s guest agent still
> doesn’t work without native virtio in the guest even though a
> serial (IIRC) control channel is specified), and killing such
> a VM will introduce guest filesystem corruption.
> 
> At least issue a debconf thing like glibc does when you want
> to upgrade from 2.29 to 2.30, which offers me some time to
> shut down the VM manually or abort the upgrade.
> 
> 
> To add insult to injury, it didn’t even shut it down cleanly:
> 
> tglase@tglase:~ $ virsh -c qemu:///system list
>  Id   Name State
> 
>  3MirBSD   in shutdown
> 
> 
> “virsh destroy 3” to the “rescue”…
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unreleased
>   APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 
> 'unstable'), (100, 'experimental')
> Architecture: x32 (x86_64)
> Foreign Architectures: i386, amd64
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
> Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/lksh
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages libvirt-daemon-system-sysv depends on:
> ii  init-system-helpers  1.57
> ii  lsb-base 11.1.0
> 
> libvirt-daemon-system-sysv recommends no packages.
> 
> libvirt-daemon-system-sysv suggests no packages.
> 
> -- no debconf information
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#953894: [Pkg-libvirt-maintainers] Bug#953894: libvirt-daemon: hangs on update, file conflicts

[Guido Günther]

Hi,
On Mon, Mar 16, 2020 at 04:54:22PM +0900, Norbert Preining wrote:
> Hi Guido,
> 
> thanks for your answer.
> 
> On Mon, 16 Mar 2020, Guido Günther wrote:
> > There should be somethin in the journal about the above error, could you
> > add that to the bug report?
> 
> Looking at the logs it looks like the missing replace/conflicts are the
> problem:
> 
> libvirtd[1429970]: internal error: Failed to load module 
> '/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_libxl.so':
>  /usr/lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_PRIVATE_5.6.0' not 
> found (required by 
> /usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_libxl.so)
> Failed to start Virtualization daemon.

Seems it tries to pick up the old .so due to the upgrade failure. Thanks
for following up!
 -- Guido

> 
> Best
> 
> Norbert
> 
> --
> PREINING Norbert  https://www.preining.info
> Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
> 

Bug#939983: closed by Thorsten Glaser (Re: [Pkg-libvirt-maintainers] Bug#939983: error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers')

[Guido Günther]

Hi,
On Mon, Mar 16, 2020 at 12:45:05AM +, Debian Bug Tracking System wrote:
[..snip..]

> Now in sid, thanks! (The NEWS entry comes too late btw — after apt
> first had tried to remove elogind entirely, until one things of just
> running a-g i libvirt0… might wish to add to the release notes for
> bullseye…)

yes, this needs to go into the release notes too.
Cheers,
 -- Guido

Bug#953894: [Pkg-libvirt-maintainers] Bug#953894: libvirt-daemon: hangs on update, file conflicts

[Guido Günther]

Hi,
On Sun, Mar 15, 2020 at 12:41:26AM +0900, Norbert Preining wrote:
> Package: libvirt-daemon
> Version: 6.0.0-2
> Severity: grave
> Justification: renders package unusable
> 
> Updating to 6.0.0-2 hangs indefinitely:
> ...
> Setting up libvirt-daemon-system (6.0.0-2) ...
> Installing new version of config file 
> /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper ...
> Installing new version of config file /etc/libvirt/libvirtd.conf ...
> Installing new version of config file /etc/libvirt/qemu.conf ...
> Installing new version of config file /etc/libvirt/virtlockd.conf ...
> Installing new version of config file /etc/libvirt/virtlogd.conf ...
> Job failed. See "journalctl -xe" for details.
> Job for libvirtd.service failed because the control process exited
> with error code.

There should be somethin in the journal about the above error, could you
add that to the bug report?

> See "systemctl status libvirtd.service" and "journalctl -xe" for details.
> virtlockd.service is a disabled or a static unit not running, not starting it.
> virtlogd.service is a disabled or a static unit not running, not starting it.
> 
> 
> 
> no reaction after this for long time. 
> 
> It seems that
>   virsh connect
> is running but never actually succeeds.
> 
> No further updates or configuration is done.
> 
> 
> Furthermore, during update, you have some missing file
> replace/breaks/...
> 
> Unpacking libvirt-daemon-driver-lxc (6.0.0-2) over (5.6.0-3) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-nxkUMr/10-libvirt-daemon-driver-lxc_6.0.0-2_amd64.deb 
> (--unpack):
>  trying to overwrite '/usr/share/augeas/lenses/libvirtd_lxc.aug', which is 
> also in package libvirt-daemon 5.6.0-3
> Preparing to unpack .../11-libvirt-daemon-driver-xen_6.0.0-2_amd64.deb ...
> Unpacking libvirt-daemon-driver-xen (6.0.0-2) over (5.6.0-3) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-nxkUMr/11-libvirt-daemon-driver-xen_6.0.0-2_amd64.deb 
> (--unpack):
>  trying to overwrite '/usr/share/augeas/lenses/libvirtd_libxl.aug', which is 
> also in package libvirt-daemon 5.6.0-3
> Preparing to unpack .../12-libvirt-daemon-driver-vbox_6.0.0-2_amd64.deb ...
> Unpacking libvirt-daemon-driver-vbox (6.0.0-2) over (5.6.0-3) ...
> Preparing to unpack .../13-libvirt-daemon-driver-qemu_6.0.0-2_amd64.deb ...
> Unpacking libvirt-daemon-driver-qemu (6.0.0-2) over (5.6.0-3) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-nxkUMr/13-libvirt-daemon-driver-qemu_6.0.0-2_amd64.deb 
> (--unpack):
>  trying to overwrite '/usr/share/augeas/lenses/libvirtd_qemu.aug', which is 
> also in package libvirt-daemon 5.6.0-3
> Preparing to unpack .../14-libvirt-daemon-system_6.0.0-2_amd64.deb ...
> 
> 
> Best
> 
> Norbert
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (200, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.5.9 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages libvirt-daemon depends on:
> ii  libblkid1   2.34-0.1
> ii  libc6   2.30-2
> ii  libcap-ng0  0.7.9-2.1+b2
> ii  libdbus-1-3 1.12.16-2
> ii  libdevmapper1.02.1  2:1.02.167-1+b1
> ii  libfuse22.9.9-3
> ii  libgcc-s1   10-20200304-1
> ii  libglib2.0-02.64.0-2
> ii  libnetcf1   1:0.2.8-1+b3
> ii  libparted2  3.3-4
> ii  libpcap0.8  1.9.1-2
> ii  libpciaccess0   0.14-1
> ii  libselinux1 3.0-1+b1
> ii  libudev1245-2
> ii  libvirt-daemon-driver-qemu  5.6.0-3
> iu  libvirt06.0.0-2
> ii  libxml2 2.9.10+dfsg-4
> 
> Versions of packages libvirt-daemon recommends:
> ii  libvirt-daemon-driver-lxc   5.6.0-3
> iu  libvirt-daemon-driver-vbox  6.0.0-2
> ii  libvirt-daemon-driver-xen   5.6.0-3
> ii  libxml2-utils   2.9.10+dfsg-4
> ii  netcat-openbsd  1.206-1
> ii  qemu-kvm1:4.2-3
> 
> Versions of packages libvirt-daemon suggests:
> pn  libvirt-daemon-driver-storage-gluster  
> pn  libvirt-daemon-driver-storage-rbd  
> pn  libvirt-daemon-driver-storage-zfs  
> iu  libvirt-daemon-system  6.0.0-2
> pn  numad  
> 
> -- no debconf information
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#947006: marked as pending in libvirt

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #947006 in libvirt 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/libvirt-team/libvirt/commit/c19d230d6d633f552adf21f826872ee2e758c0ab


autopkg tests: Use isolation-machine

This avoids running under debian ci since libvirt-lxc in lxc
doesn't work there.

Closes: #947006


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947006

Bug#947006: [Pkg-libvirt-maintainers] Bug#947006: libvirt: autopkgtest always fails and now started to time out regularly

[Guido Günther]

Hi Paul,
thanks for the notification!

On Thu, Dec 19, 2019 at 12:28:34PM +0100, Paul Gevers wrote:
> Source: libvirt
> Version: 5.6.0-3
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: timeout flaky
> 
> Dear maintainers,
> 
> Your package has an autopkgtest, great. However, I noticed that it
> always fails, which nowadays is considered RC. However, on top of that,
> with version 5.6.0-3 your package started to time out regularly on
> ci.debian.net (after 2:50 h).
> 
> I wonder if the smoke-lxc test is suitable to test *inside* an lxc as
> your using virsh. I am not enough into this, but it smells a bit like
> you want an "isolation-machine" restriction for that test.
> 
> Can you please investigate the situation? Don't hesitate to ask for help
> from the Debian CI team (in X-Debbugs-CC) if you need help solving this
> issue.
> 
> To avoid wasting lots of time on the ci.debian.net infrastructure, I
> have blacklisted your package. If needed, please ping me to try any
> uploads you make that should fix the issue if you are unsure and don't
> want to close this bug until verified.

What would be the right way to detect that the test should be skipped -
just checking we're running inside lxc? virt-what uses this

```
# Check for LXC containers
# http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
# Added by Marc Fournier

if [ -e "${root}/proc/1/environ" ] &&
cat "${root}/proc/1/environ" | tr '\000' '\n' | grep -Eiq '^container='; 
then
echo lxc
fi
```

Cheers,
 -- Guido

> 
> Paul
> 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/libv/libvirt/3677408/log.gz
> 
> autopkgtest [18:02:42]: test smoke-lxc: [---
> + virt-host-validate lxc
>LXC: Checking for Linux >= 2.6.26
>  : PASS
>LXC: Checking for namespace ipc
>  : PASS
>LXC: Checking for namespace mnt
>  : PASS
>LXC: Checking for namespace pid
>  : PASS
>LXC: Checking for namespace uts
>  : PASS
>LXC: Checking for namespace net
>  : PASS
>LXC: Checking for namespace user
>  : PASS
>LXC: Checking for cgroup 'cpu' controller support
>  : PASS
>LXC: Checking for cgroup 'cpuacct' controller support
>  : PASS
>LXC: Checking for cgroup 'cpuset' controller support
>  : PASS
>LXC: Checking for cgroup 'memory' controller support
>  : PASS
>LXC: Checking for cgroup 'devices' controller support
>  : PASS
>LXC: Checking for cgroup 'freezer' controller support
>  : PASS
>LXC: Checking for cgroup 'blkio' controller support
>  : PASS
>LXC: Checking if device /sys/fs/fuse/connections exists
>  : PASS
> + virsh capabilities
> autopkgtest [20:49:22]: ERROR: timed out on command "su -s /bin/bash
> root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
> true;  . ~/.profile >/dev/null 2>&1 || true;
> buildtree="/tmp/autopkgtest-lxc.g55a6fi0/downtmp/build.mXC/src"; mkdir
> -p -m 1777 --
> "/tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-artifacts"; export
> AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-artifacts";
> export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
> "/tmp/autopkgtest-lxc.g55a6fi0/downtmp/autopkgtest_tmp"; export
> AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.g55a6fi0/downtmp/autopkgtest_tmp";
> export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
> export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
> LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
> LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
> LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
> $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
> /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export
> AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x
> /tmp/autopkgtest-lxc.g55a6fi0/downtmp/build.mXC/src/debian/tests/smoke-lxc;
> touch /tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stdout
> /tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stderr;
> /tmp/autopkgtest-lxc.g55a6fi0/downtmp/build.mXC/src/debian/tests/smoke-lxc
> 2> >(tee -a /tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stderr >&2)
> > >(tee -a /tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stdout);"
> (kind: test)
> autopkgtest [20:49:22]: test smoke-lxc: ---]
> 




> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#941249: [Pkg-libvirt-maintainers] Bug#941249: virt-manager: Can not open detail of connection and detail or console of a VM

[Guido Günther]

Hi,
On Fri, Sep 27, 2019 at 07:59:16AM +0200, Sebastien Helleu wrote:
> Package: virt-manager
> Version: 1:2.2.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After upgrade from virt-manager 2.0.0 to 2.2.1, I can not open any more 
> detail of connection, or detail/console of a VM, no window is open when I 
> click or if I select Open in the menu.
> 
> Here's the output of virt-manager --debug --no-fork:
> 
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (cli:208) Launched 
> with command line: /usr/share/virt-manager/virt-manager --debug --no-fork
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:223) 
> virt-manager version: 2.2.1
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:224) 
> virtManager import:  '/usr/share/virt-manager/virtManager/__init__.py'>
> 
> (virt-manager:2944): dbind-WARNING **: 07:56:10.508: Couldn't connect to 
> accessibility bus: Failed to connect to socket /tmp/dbus-0YN5eotkNt: 
> Connexion refusée
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:274) 
> PyGObject version: 3.34.0
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:278) GTK 
> version: 3.24.11
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (systray:213) Showing 
> systray: False
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (inspection:41) python 
> guestfs is not installed
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:116) Loading 
> stored URIs:
> qemu+ssh://shelleu@10.10.43.16/system  
> qemu:///system
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:537) 
> processing cli command uri= show_window=manager domain=
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:539) No cli 
> action requested, launching default window
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (manager:184) Showing 
> manager
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:391) window 
> counter incremented to 1
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:285) Initial 
> gtkapplication activated
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:533) 
> conn=qemu:///system changed to state=Connexion
> [ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:946) 
> Scheduling background open thread for qemu:///system
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:986) 
> libvirt version=5006000
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:988) 
> daemon version=5006000
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:989) conn 
> version=4001000
> [ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:991) 
> qemu:///system capabilities:
> 
> 
>   
> eef59000-6784---
> 
>   x86_64
>   Westmere
>   Intel
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> 
>   
>   
>   
> 
> 
> 
>   
>   
> tcp
> rdma
>   
> 
> 
>   
> 
>   3959980
>   989995
>   0
>   0
>   
> 
>   
>   
> 
> 
> 
> 
>   
> 
>   
> 
> 
>   
> 
> 
>   none
>   0
> 
> 
>   dac
>   0
>   +101:+112
>   +101:+112
> 
>   
> 
>   
> hvm
> 
>   64
>   /usr/bin/qemu-system-alpha
>   clipper
>   
> 
> 
>   
>   
>   
> 
>   
> 
>   
> hvm
> 
>   32
>   /usr/bin/qemu-system-arm
>   integratorcp
>   versatileab
>   smdkc210
>   nuri
>   palmetto-bmc
>   microbit
>   mainstone
>   canon-a1100
>   terrier
>   n800
>   verdex
>   kzm
>   versatilepb
>   midway
>   virt-2.7
>   emcraft-sf2
>   mcimx7d-sabre
>   highbank
>   imx25-pdk
>   n810
>   virt-2.11
>   realview-pbx-a9
>   tosa
>   sx1-v1
>   swift-bmc
>   mps2-an511
>   musca-a
>   realview-pb-a8
>   sabrelite
>   akita
>   cubieboard
>   virt-2.9
>   xilinx-zynq-a9
>   virt-3.1
>   vexpress-a15
>   virt-4.1
>   virt
>   musca-b1
>   mps2-an521
>   realview-eb
>   cheetah
>   vexpress-a9
>   virt-2.6
>   mps2-an505
>   spitz
>   netduino2
>   lm3s6965evb
>   virt-2.10
>   lm3s811evb
>   z2
>   raspi2
>   connex
>   borzoi
>   mcimx6ul-evk
>   

Bug#941249: marked as pending in virt-manager

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #941249 in virt-manager 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/libvirt-team/virt-manager/commit/667db917a46e88d56249b43b58248f8e5c764118


d/control: Depend on gir1.2-gtksource-4

Closes: #941249


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941249

Bug#939648: git-buildpackage: FTBFS in unstable: flake8: E117 over-indented

[Guido Günther]

Hi,
On Sat, Sep 07, 2019 at 10:29:08AM +0100, Simon McVittie wrote:
> Package: git-buildpackage
> Version: 0.9.14
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> During test-builds to evaluate whether the new version of gtk-doc-tools is
> ready for upload to unstable, git-buildpackage failed to build. I can
> reproduce the build failure in a pure unstable sbuild environment:
> 
> >debian/rules override_dh_auto_test
> > make[1]: Entering directory '/<>'
> > make
> > make[2]: Entering directory '/<>'
> > flake8
> > ./gbp/patch_series.py:148:17: E117 over-indented
> > ./gbp/scripts/buildpackage.py:333:13: E117 over-indented
> > ./gbp/scripts/import_orig.py:82:17: E117 over-indented
> > ./gbp/scripts/common/import_orig.py:71:13: E117 over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/patch_series.py:148:17: E117 over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/scripts/buildpackage.py:333:13: E117 
> > over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/scripts/import_orig.py:82:17: E117 
> > over-indented
> > ./.pybuild/cpython3_3.7/build/gbp/scripts/common/import_orig.py:71:13: E117 
> > over-indented
> > make[2]: *** [Makefile:20: syntax-check] Error 1

Fixed in git 78f8759a3d8e52e63aa3ec4dc2212989ae836494 since some time,
i'll roll that into a release.

> 
> Full build log attached.
> 
> I would recommend skipping stylistic/non-functional checks like this one,
> or making them only produce warnings, when "official" packages are built
> in a Debian environment (the style checks can still be fatal when run as
> part of `make check` during development, of course). Perhaps something
> like this:
> 
> # in debian/rules
> export IGNORE_STYLE_CHECKS = 1
> 
> # in the tests, replacing the flake8 invocation
> flake8 || [ -n "$IGNORE_STYLE_CHECKS" ]

I somewhat fear that they will slip then but i'll give it some
consideration.
thanks!
 -- Guido

> 
> Regards,
> smcv

Bug#935883: marked as pending in libvirt

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #935883 in libvirt 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/libvirt-team/libvirt/commit/4dcbe933607f0ef228d3f89be7eb024857213fb2


Revert "Disable libvirtd socket activation" (Closes: #935883)

Turns out socket activation for libvirtd actually works fine, and
furthermore not having it enabled along with the default timeout
for libvirtd now being 120 seconds results in clients no longer
being able to use libvirt two short minutes after boot.

This reverts commit b8e92da4ff0af742f5de055ace97503c778a8484.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935883

Bug#932584: Please help fix pydoctor

[Guido Günther]

Hi,
On Sun, Jul 28, 2019 at 02:00:56PM +0100, Ian Jackson wrote:
> Hi, Python folks.
> 
> I think help is needed regarding
> 
>   #932584  python-pydoctor: Epydoc will be removed
> 
> It seems to be languishing rather.  What I don't understand is why
> pydoctor depends on epydoc given that, in the words of the
> Description:
> 
>   [Pydoctor] was written primarily to replace epydoc ...
> 
> I had a quick look through the source but I don't know enough about
> pydoctor to make immediate sense of the results of my grep.  Maybe
> some person who knows more about pydoctor can help ?
> 
> (I'm CCing this to the gbp maintainers because this came to my
> attention due to an autoremoval bug where a package of mine has a
> dependency chain via gbp.)

epydoc only seems to be used for formatting and README.Debian confirms
this:

...and looking at the bug it seems it was already dealt with by dropping
the epydoc dependency. Thanks!
 -- Guido

> 
> Thanks,
> Ian.
> 
> -- 
> Ian JacksonThese opinions are my own.
> 
> If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
> a private address which bypasses my fierce spamfilter.
> 

Bug#930929: [Pkg-libvirt-maintainers] Bug#930929: marked as done (libvirt: is no longer able to use kvm)

[Guido Günther]

Hi,
On Sat, Jun 22, 2019 at 08:15:06PM +, Debian Bug Tracking System wrote:
> Your message dated Sat, 22 Jun 2019 22:10:34 +0200
> with message-id <20190622201034.ga4...@home.ouaza.com>
> and subject line Re: Bug#930929: libvirt: is no longer able to use kvm
> has caused the Debian Bug report #930929,
> regarding libvirt: is no longer able to use kvm
> 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 responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.
> 
> (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.)
> 
> 
> -- 
> 930929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930929
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> From: Raphaël Hertzog 
> To: Debian Bug Tracking System 
> Date: Sat, 22 Jun 2019 19:17:15 +0200
> Subject: libvirt: is no longer able to use kvm
> X-Spam-Level: 
> X-Spam-Status: No, score=-35.3 required=4.0 tests=BAYES_00,FOURLA,
>  FROMDEVELOPER,SPF_HELO_PASS,SPF_NONE,TXREP,XMAILER_REPORTBUG, X_DEBBUGS_CC
>  autolearn=ham autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02
> Message-ID: 
> <156122383595.4344.5739740357131736912.report...@x260-buxy.home.ouaza.com>
> 
> Source: libvirt
> Version: 5.0.0-4
> Severity: serious
> 
> For a few days/weeks (I'm not sure when it started exactly), I can no
> longer run my VM with virt-manager.
> 
> On startup of libvirtd I have many messages like this one (one for each VM
> I guess):
> libvirtd[8281]: invalid argument: could not find capabilities for arch=x86_64 
> domaintype=kvm 
> 
> When I try to start a VM I see this in the logs of libvirtd:
> libvirtd[12569]: Unable to read from monitor: Connexion ré-initialisée par le 
> correspondant
> libvirtd[12569]: internal error: qemu unexpectedly closed the monitor: Could 
> not access KVM kernel module: Permission denied
>  2019-06-22T17:07:23.635870Z qemu-system-x86_64: failed to 
> initialize KVM: Permission denied
> libvirtd[12569]: internal error: process exited while connecting to monitor: 
> Could not access KVM kernel module: Permission denied
>  2019-06-22T17:07:23.635870Z qemu-system-x86_64: failed to 
> initialize KVM: Permission denied
> 
> But I do have /dev/kvm and I have hardware virtualization enabled in the
> BIOS.
> 
> $ ls -al /dev/kvm
> crw-rw+ 1 root root 10, 232 juin  22 19:07 /dev/kvm
> $ getfacl /dev/kvm
> # file: dev/kvm
> # owner: root
> # group: root
> user::rw-
> user:rhertzog:rw-
> group::---
> mask::rw-
> other::---
> 
> And I do have the required kernel modules:
> $ lsmod|grep kvm
> kvm_intel 245760  0
> kvm   724992  1 kvm_intel
> irqbypass  16384  1 kvm
> 
> I also have qemu-kvm installed:
> $ dpkg -l qemu*|grep ^ii
> ii  qemu-kvm   1:3.1+dfsg-8 amd64QEMU Full virtualization on 
> x86 hardware
> ii  qemu-system-common 1:3.1+dfsg-8 amd64QEMU full system emulation 
> binaries (common files)
> ii  qemu-system-data   1:3.1+dfsg-8 all  QEMU full system emulation 
> (data files)
> ii  qemu-system-gui1:3.1+dfsg-8 amd64QEMU full system emulation 
> binaries (user interface and audio support)
> ii  qemu-system-x861:3.1+dfsg-8 amd64QEMU full system emulation 
> binaries (x86)
> ii  qemu-user  1:3.1+dfsg-8 amd64QEMU user mode emulation 
> binaries
> ii  qemu-user-static   1:3.1+dfsg-8 amd64QEMU user mode emulation 
> binaries (static version)
> ii  qemu-utils 1:3.1+dfsg-8 amd64QEMU utilities
> 
> I removed virtualbox and rebooted to make sure it's not a bad interaction but 
> it did not help.
> I don't know what else I should look into.
> 
> -- System Information:
> Debian Release: 10.0
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
> 'oldstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
> LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

> From: Raphael Hertzog 
> To: 930929-d...@bugs.debian.org
> Date: Sat, 22 Jun 2019 22:10:34 +0200
> Subject: Re: Bug#930929: libvirt: is no longer able to use kvm
> X-Spam-Level: 
> X-Spam-Status: No, score=-19.8 required=4.0 tests=BAYES_00,FROMDEVELOPER,
>  HAS_BUG_NUMBER,HEADER_FROM_DIFFERENT_DOMAINS,SPF_HELO_PASS,SPF_PASS, TXREP
>  autolearn=ham autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02
> Message-ID: <20190622201034.ga4...@home.ouaza.com>
> 
> On Sat, 22 Jun 2019, Raphael Hertzog wrote:
> > Still I confirm that the 

Bug#930929: [Pkg-libvirt-maintainers] Bug#930929: libvirt: is no longer able to use kvm

[Guido Günther]

Hi,
On Sat, Jun 22, 2019 at 07:17:15PM +0200, Raphaël Hertzog wrote:
> Source: libvirt
> Version: 5.0.0-4
> Severity: serious
> 
> For a few days/weeks (I'm not sure when it started exactly), I can no
> longer run my VM with virt-manager.
> 
> On startup of libvirtd I have many messages like this one (one for each VM
> I guess):
> libvirtd[8281]: invalid argument: could not find capabilities for arch=x86_64 
> domaintype=kvm 
> 
> When I try to start a VM I see this in the logs of libvirtd:
> libvirtd[12569]: Unable to read from monitor: Connexion ré-initialisée par le 
> correspondant
> libvirtd[12569]: internal error: qemu unexpectedly closed the monitor: Could 
> not access KVM kernel module: Permission denied
>  2019-06-22T17:07:23.635870Z qemu-system-x86_64: failed to 
> initialize KVM: Permission denied
> libvirtd[12569]: internal error: process exited while connecting to monitor: 
> Could not access KVM kernel module: Permission denied
>  2019-06-22T17:07:23.635870Z qemu-system-x86_64: failed to 
> initialize KVM: Permission denied
> 
> But I do have /dev/kvm and I have hardware virtualization enabled in the
> BIOS.

Is that qemu://session or qemu://system? If one doesn't work, does the
other?

Output of

- id libvirt-qemu
- getfacl /dev/kvm
- id

please. The later is mostly relevant for qemu://session.

Cheers,
 -- Guido

Bug#908678: Update on the security-tracker git discussion

[Guido Günther]

Hi Salvatore,
On Sat, Jun 08, 2019 at 06:29:24PM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Thu, Jun 06, 2019 at 06:11:53PM +0200, Salvatore Bonaccorso wrote:
> > Hi Daniel,
> > 
> > On Thu, Jun 06, 2019 at 08:35:47AM +0200, Daniel Lange wrote:
> > > Am 06.06.19 um 07:31 schrieb Salvatore Bonaccorso:
> > > > Could you again point me to your splitted up variant mirror?
> > > 
> > > https://git.faster-it.de/debian_security_security-tracker_split_files/
> > 
> > Thanks!
> > 
> > While starting to look at it, could you change the splitting to
> > $year.list instead of list.$year? I know this comes from the initial
> > script which was commited. It is though more intuitive working with
> > $work.something than something.$year in this context.
> 
> Thanks to Daniel for providing the converted repository (with list
> named as well the other way around as $year.list, which is more
> intuitive, and looks saner (to me)) which get updated regularly, this
> helps as a extremly good basis.
> 
> Below are some thoughs which I started thinking of during the last few
> days, please not it might not yet be complete. Please as well try to
> not push/force us too much -- whilst we understand the issue, and see
> that something whatever the solution is (split, move somewhere else)
> -- we have regularly more serious issues popping up we want and need
> to look at those. But we acknowledge and see als well salsa admin
> point of view.
> 
> That said, here is what I have at the moment, some are easy, some
> will/might be more involving.
> 
> Notes on possible CVE/list splits
> -
> 
> - workflows on files itself by most active users. Often kept open
>   cross-checking issues all issues in one file. But this will "just"
>   need other ways to deal with the situation by the persons working
>   most on it.
> - Code of security-tracker service and python modules itself which
>   currently rely on the data/*/list formats (DSA, DLA, CVE, ...) This
>   could probably be split up and use data/*/*.list
> - Externally called but included in code: update script which fetches
>   MITRE list and integrates all needed changes (see further below).
> - bin/bts-update (called from scripts/update-CVE-assignments in cron of
>   the securiy-tracker-services) operates based on data/CVE/list and
>   keeps track of the already tagged bugs by comparing with an 'oldlist'.
>   The oldlist is copied on a run on soriano.debian.org as 'state' file
>   similar to logroate's statefile (cron).
> - bin/check-new-issues: parsing of TODO and checks for the new issues is
>   as well based on 'data/CVE/list' existence and parsing. After a split
>   up the interactive commands should still be able to navigate trough
>   the items.
> - bin/check-syntax: Check syntax of the various lists based on the security-
>   tracker parser for the lists. make check-syntax from the Makefile, pre-
>   commit hook or C/I tests are all using this script for syntax check.
>   Depends on CVEfile as well from python/bugs.py. Relevant here is the
>   check-syntax target from the Makefile. At SVN times this was actually
>   only testing the syntax of the changed files, but now it just runs
>   make check-syntax.
> - bin/compare-nvd-cve reads from data/CVE/list and this is probably
>   easier to adapt and it's used basically in a "experimental" target in
>   Makefile for update-compare-nvd target. AFAICS this is just reading
>   the information should be easy to adapt to any split up setup.
> - bin/gen-{DSA,DLA}: Used the data/CVE/list for sanity check for
>   presence of the CVE.
> - bin/get-todo-items (this script is currently not working correctly and
>   it's implemented already via the webview, so need to consider if we
>   actually still need it).
> - bin/inject-embedded-code-copies (experimental script, not
>   actively used)
> - bin/rejected-with-info relies on data/CVE/list directly, but will be
>   potentially easily adaptable in a splited setup.
> - bin/setup-repo: checks for data/CVE/list just to make sure it's the
>   right repo.
> - bin/report-vuln uses CVEFile (from python/bugs.py).
> - bin/update and bin/updatelist: Parses DSA/DTSA/DLA list and
>   data/CVE/list adding new entries from MITRE feed and crossreferences
>   for the DSA/DLA's to a new data/CVE/list which then in the cronjob on
>   soriano will be committed. That is one processing those files in a
>   splitted setup this will need continue to work.
> - bin/update-db (Used triggered by Makefile target to update security.db
>   sqlite database).
> - bin/update-nvd (possibly dependency on the CVE lists via the used
>   modules but not directly).
> - data/config.json contains the sources for CVE, DSA, DLA and extended
>   lists. Currently path thus will be a path component starting from
>   data, e.g. for CVE files path is '/CVE/list'. See as well "Setting up
>   an extended instance" in the documentation.
> - lib/python/bugs.py contains the classes CVEFile, DSAFile,
>   

Bug#927310: marked as pending in libvirt

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #927310 in libvirt 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/libvirt-team/libvirt/commit/ea7a491c3adcc0fc4f79a21fbc4b9d49aec179b2


lxc: Fix container shutdown and host reboot

Closes: #927310, #897394


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/927310

Bug#929334: marked as pending in libvirt

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #929334 in libvirt 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/libvirt-team/libvirt/commit/6bc6e60d903933fe231d834d9d9296b4258c0981


CVE-2019-10132: Fix vir{lock,log}d socket access

All patches were cherry-picked from upstream's v5.0-maint branch.

Closes: #929334


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/929334

Bug#929154: [Pkg-libvirt-maintainers] Bug#929154: libvirt: cpu_map: Define md-clear CPUID bit (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091)

[Guido Günther]

Hi,
On Sun, May 19, 2019 at 01:49:54PM +0200, Salvatore Bonaccorso wrote:
> Hi Guido,
> 
> On Sun, May 19, 2019 at 01:32:48PM +0200, Guido Günther wrote:
> > Hi Salvatore,
> > On Sat, May 18, 2019 at 03:31:36PM +0200, Salvatore Bonaccorso wrote:
> > > hi
> > > 
> > > Merge Request for sid/buster at
> > > https://salsa.debian.org/libvirt-team/libvirt/merge_requests/27
> > 
> > Thanks! If you want to do the NMU please make sure to pull in the two
> > topmost commits from debian/sid as well. Otherwise I can handle it but I
> > won't get around to it before mid week.
> 
> Looking at those they should be as well okay indeed for the release
> team :)
> 
> Yes I can go ahead then rebasing my proposed NMU on top of it instead
> of the tagged version.
> 
> I will rebase the merge request then and as you seen okay with my
> proposed change upload without delaying queue.

Absolutely. Thanks for handing this!
 -- Guido

Bug#929154: [Pkg-libvirt-maintainers] Bug#929154: libvirt: cpu_map: Define md-clear CPUID bit (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091)

[Guido Günther]

Hi Salvatore,
On Sat, May 18, 2019 at 03:31:36PM +0200, Salvatore Bonaccorso wrote:
> hi
> 
> Merge Request for sid/buster at
> https://salsa.debian.org/libvirt-team/libvirt/merge_requests/27

Thanks! If you want to do the NMU please make sure to pull in the two
topmost commits from debian/sid as well. Otherwise I can handle it but I
won't get around to it before mid week.
Cheers,
 -- Guido


> 
> Regards,
> Salvatore
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#905772: libvirtd upgrade broken stretch->buster

[Guido Günther]

Hi,
On Wed, Apr 17, 2019 at 02:47:41PM -0400, Sam Hartman wrote:
> but I haven't been able to reproduce on a clean install.
> It's frustrating: on my machines where I really want the upgrade to be
> smoothe this bit me, but on all my toy tests, it didn't happen.
> What I think may be necessary is for virtlogd to be active.
> So it may be necessary to actually get libvirtd running and actually
> running a VM to use the socket before the issue comes up.

That's possible.

> Alternatively, it's possible some other change has fixed this in the
> last month.

We did not change anything in that area so it's likely hidden (e.g. only
happening when running a VM) - I'll check that.


> I'll certainly say that a month ago ran into this on two different VM
> servers.

That's an important data point. Thanks
 -- Guido

Bug#905772: libvirtd upgrade broken stretch->buster

[Guido Günther]

Hi,
On Mon, Apr 15, 2019 at 02:38:27PM -0400, Sam Hartman wrote:
> control: severity -1 serious
> 
> justification: libvirtd upgrades from stretch to buster break causing
> apt to fail and requiring the admin to get the systemd units into a
> consistent state before things can continue
> 
> 
> Unfortunately based on discussion so far this is a complex bug to fix.
> Ubuntu's solution is to drop the sysv scripts and to drop  Also= lines
> in some of the units.

Did you reproduce this bug on a stretch->buster upgrade? Cause I just
did that and didn't encounter any errors.

Cheers,
 -- Guido

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

[Guido Günther]

Hi,
On Mon, Apr 15, 2019 at 10:18:18PM +0200, Michael Biebl wrote:
> Hi Sam
> 
> Am 15.04.2019 um 20:38 schrieb Sam Hartman:
> > control: severity -1 serious
> > 
> > justification: libvirtd upgrades from stretch to buster break causing
> > apt to fail and requiring the admin to get the systemd units into a
> > consistent state before things can continue
> > 
> > 
> > Unfortunately based on discussion so far this is a complex bug to fix.
> > Ubuntu's solution is to drop the sysv scripts and to drop  Also= lines
> > in some of the units.
> > 
> > The systemd maintainers proposed that dropping Also as well as some
> > changes to move toward dh_systemd_start being used even when sysvinit
> > scripts are present would help this situation.  Unfortunately it at
> > least doesn't look like those changes are in debhelper for buster.
> > Systemd folks, do you have any suggestions  on how to approach this for
> > buster?
> 
> Using debhelper compat level 12, you are able to completely decouple
> dh_installinit and dh_installsystemd which would give you the ability to
> implement what you want afaics.

So let's move libvirt from 8 to 12 for stretch? I'm all for it but it'll
be a couple of days until I can set time aside for this.
cheers,
 -- Guido

> 
> Regards,
> Michael
> 
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 




> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#919486: osinfo-db: diff for NMU version 0.20181120-1.1

[Guido Günther]

Hi,
On Fri, Apr 05, 2019 at 05:36:49PM +, z...@debian.org wrote:
> Control: tags 919486 + patch
> Control: tags 919486 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for osinfo-db (versioned as 0.20181120-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Thanks for looking into this!

The reason I've not dealt with that yet is that the links are all dead
atm. This will trigger frustration for people using this.

Also it'd be as important to have osinfodb support in stretch so people
building new buster VMs on our current stable can do so.

So what would be better here is to follow RCs like we did for stretch:

https://salsa.debian.org/libvirt-team/osinfo-db/commit/f34951d8f47fb6ec6546c8630c34c1365b825a02
https://salsa.debian.org/libvirt-team/osinfo-db/commit/efcfeb9c9420448c2d85f16560b70910b12f40b9

If we had stable links for CD images (3813797) this would be different
but I did not get around to look into this yet so help there would be
appreciated and would make this fixable for real.

For now it would be cool if you could cancel the NMU.
Cheers,
 -- Guido

Bug#925202: Keep calypso out of testing/buster

[Guido Günther]

Hi Ivo,
On Sat, Mar 30, 2019 at 05:06:22PM +0100, Ivo De Decker wrote:
> Control: found -1 1.5
> 
> Hi,
> 
> On Thu, Mar 21, 2019 at 09:02:13AM +0100, Guido Günther wrote:
> > Package: calypso
> > Version: 1.5-5
> > Severity: grave
> > 
> > Calypso has not seen much attention recently so it's likely better to
> > not ship it in a stable release. It wasn't in stretch either so this
> > will not affect current users.
> > Cheers,
> >  -- Guido
> 
> I added a removal hint to get it out of testing.

Thanks! 

> However, please note that there was a new upload in unstable. The history for
> that version doesn't include the history for 1.5-1 to 1.5-5. I don't know if
> that was intentional. I updated the metadata for this bug to make sure it
> affects both. I might be good to consolidate the history of the package.

Thanks for noticing! It seems this somewhat got forgotten on the 2.0
branch. Keith moved things to salsa

https://salsa.debian.org/debian/calypso/

and I'm sure we can sort that out there.
Cheers,
 -- Guido

Bug#909417: [Pkg-libvirt-maintainers] Bug#909417: gtk-vnc: FTBFS randomly (vncconnectiontest fails with "assertion failed")

[Guido Günther]

Hi,
On Thu, Mar 21, 2019 at 12:33:58AM +0100, Steinar H. Gunderson wrote:
> On Sat, Mar 09, 2019 at 07:26:52PM +0100, Santiago Vila wrote:
> > Whoever wants to reproduce this (and possibly debug it), *please*
> > contact me privately and I will gladly provide ssh access to a machine
> > where it happens very often.
> 
> I've looked briefly into this.
> 
> First, to reproduce this reliably, simply restrict it to one core
> (taskset -c 0 /build/gtk3/src/vncconnectiontest). The reason will be fairly
> clear from the text below.
> 
> As far as I can see, this test simulates a broken VNC server (to test the
> client's robustness). It says it's got a 100x100 true color display, but then
> goes on and starts sending a color map.
> 
> As soon as the client receives the information about the color map,
> it realizes something is wrong, and a race starts. Now the client wants to
> close the connection at the same time as the fake server wants to keep
> sending the cmap data. If you've got two cores, the server just keeps on
> sending data happily; by the time it's noticed that the client is gone,
> the test has passed and all is fine. But if you've only got one, then the
> first byte of the cmap causes a context switch over to the client, which then
> gets ample time to read the data and close the socket before the server gets
> to send the next byte. The server thus gets EPIPE, and test_send_u16()
> breaks.
> 
> I believe the right fix is to send every byte after the first “set color map”
> byte using a non-asserting send. When we've done something invalid, we'd
> better be ready for sending data to fail.
> 
> Please try the attached diff; it fixes the problem for me. I can NMU if the
> maintainers want.

I wouldn't mind an NMU.
 -- Guido
> 
> /* Steinar */
> -- 
> Homepage: https://www.sesse.net/

> Index: gtk-vnc-0.9.0/src/vncconnectiontest.c
> ===
> --- gtk-vnc-0.9.0.orig/src/vncconnectiontest.c
> +++ gtk-vnc-0.9.0/src/vncconnectiontest.c
> @@ -56,12 +56,23 @@ static void test_send_u8(GOutputStream *
>  g_assert(g_output_stream_write_all(os, , 1, NULL, NULL, NULL));
>  }
>  
> +static void send_u8(GOutputStream *os, guint8 v)
> +{
> +g_output_stream_write_all(os, , 1, NULL, NULL, NULL);
> +}
> +
>  static void test_send_u16(GOutputStream *os, guint16 v)
>  {
>  v = GUINT16_TO_BE(v);
>  g_assert(g_output_stream_write_all(os, , 2, NULL, NULL, NULL));
>  }
>  
> +static void send_u16(GOutputStream *os, guint16 v)
> +{
> +v = GUINT16_TO_BE(v);
> +g_output_stream_write_all(os, , 2, NULL, NULL, NULL);
> +}
> +
>  static void test_send_u32(GOutputStream *os, guint32 v)
>  {
>  v = GUINT32_TO_BE(v);
> @@ -429,18 +440,18 @@ static void test_unexpected_cmap_server(
>  test_recv_u16(is, 100);
>  test_recv_u16(is, 100);
>  
> -/* set color map */
> +/* set color map -- after this, the client may close the connection at 
> any time */
>  test_send_u8(os, 1);
>  /* pad */
> -test_send_u8(os, 0);
> +send_u8(os, 0);
>  /* first color, ncolors */
> -test_send_u16(os, 0);
> -test_send_u16(os, 1);
> +send_u16(os, 0);
> +send_u16(os, 1);
>  
>  /* r,g,b */
> -test_send_u16(os, 128);
> -test_send_u16(os, 128);
> -test_send_u16(os, 128);
> +send_u16(os, 128);
> +send_u16(os, 128);
> +send_u16(os, 128);
>  }
>  
>  
> @@ -505,11 +516,13 @@ static void test_overflow_cmap_server(GI
>  test_send_u16(os, 65535);
>  test_send_u16(os, 2);
>  
> +/* after this, the client may close the connection at any time */
> +
>  /* r,g,b */
>  for (int i = 0 ; i < 2; i++) {
> -test_send_u16(os, i);
> -test_send_u16(os, i);
> -test_send_u16(os, i);
> +send_u16(os, i);
> +send_u16(os, i);
> +send_u16(os, i);
>  }
>  }
>  

> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Bug#925202: Keep calypso out of testing/buster

[Guido Günther]

Package: calypso
Version: 1.5-5
Severity: grave

Calypso has not seen much attention recently so it's likely better to
not ship it in a stable release. It wasn't in stretch either so this
will not affect current users.
Cheers,
 -- Guido

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages calypso depends on:
ii  git  1:2.20.1-2
ii  python   2.7.15-4
ii  python-daemon2.2.3-1
ii  python-lockfile  1:0.12.2-2
ii  python-vobject   0.9.6.1-0.1

calypso recommends no packages.

calypso suggests no packages.

Bug#899662: *prod* Please fix pykerberos bug #899662?

[Guido Günther]

Hi,
On Sun, Mar 10, 2019 at 02:11:38PM +, Steve McIntyre wrote:
> Hi guys,
> 
> I don't know if you've even seen this RC bug. Could you please update
> the maintainer address to point to something that works?

I wasn't. I can do so next week.
 -- Guido

Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Guido Günther]

Hi,
On Mon, Feb 25, 2019 at 02:25:57PM +0100, Ralf Jung wrote:
> Package: libvirt0
> Version: 5.0.0-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After a recent upgrade, IPv6 communication between a virtual router and 
> another
> virtual client over an isolated network stopped working. I am seeing the 
> rotuer
> advertisments sent by the router on vnet0, which is attached to the bridge
> virbr1, but when I capture packages on the bridge, the IPv6 traffic is gone.  
> It
> just took me several hours of debugging to realize that the reason for this is
> that /proc/sys/net/ipv6/conf/virbr1/disable_ipv6 is set to 1.  After setting 
> it
> to 0, IPv6 is working as expected now.
> 
> This is a regression, IPv6 used to work between virtual clients just fine
> without having to manually fiddle with the network configuration.

I'm not near a ipv6 setup atm but according to the git logs nothing
changed in that area for quite some time. Please indicate which version
you updated from so it's easier to check for related changes and also
provide details about your setup (preferably network XML and domain XML).

There were some ipv6 related changes with firewalld though which might be worth
investigating.
 -- Guido

Bug#921884: wlroots: ABI break between 0.2 and 0.3

[Guido Günther]

Hi,
On Sat, Feb 09, 2019 at 11:02:01PM +0100, Mattia Rizzolo wrote:
> On Sat, Feb 09, 2019 at 10:35:22PM +0100, Guido Günther wrote:
> > This is well known to the users of wlroots and the reason why we did not
> > upload to unstable yet but it's good to have a bug tracking that.
> 
> ahem… but that's not common knowledge outside that circle...
> 
> Can I ask you at least try to minimize the disruption until a stable ABI
> comes around (hopefully soon…) by:
> * mentioning this fact in the package description
> * still adding a .symbols file so a diff of the gone symbols is available
> * bumping shlibs every time the ABI changes (you should do this regardless)
> * adding Breaks against everything in the archive that any random upload
>   breaks

I've intend to add breaks for reverse deps once they enter the archive
but currently there are none that I know of.
 -- Guido

Bug#921884: wlroots: ABI break between 0.2 and 0.3

[Guido Günther]

retitle: -1 no stable ABI

Hi,
On Sat, Feb 09, 2019 at 10:08:02PM +0100, Mattia Rizzolo wrote:
> Source: wlroots
> Version: 0.3-1
> Severity: serious
> 
> 0.3 changed many symbols.
> A full diff is below.  As you can see manny symbols were added (alright,
> that means you should have bumped shlibs, which you didn't), but also
> several were renamed, which means a real full ABI break happened, but
> the SONAME wasn't changed.
> 
> I'm afraid this also means upstream is not good at proper ABI hygiene,
> so you should be extra careful, starting by adding a .symbols file
> (which is very easy since this is a C library!).
> 
> 
> At the very least, this caused headaches while packaging sway, see
> #821397.

This is well known to the users of wlroots and the reason why we did not
upload to unstable yet but it's good to have a bug tracking that.

Cheers,
 -- Guido