[Bug 2071717] Re: [MIR] linuxptp

[Alexandre Esse]

This MIR is a joint request with Industrial team (@farshidtz & @jpm)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071717

Title:
  [MIR] linuxptp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linuxptp/+bug/2071717/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071717] [NEW] [MIR] linuxptp

[Alexandre Esse]

Public bug reported:

[MIR] linuxptp

[Availability]
The package linuxptp is already in Ubuntu universe.
The package linuxptp builds and works on all Ubuntu architectures.
Link to package: https://launchpad.net/ubuntu/+source/linuxptp

[Rationale]
Linux PTP is an open-source (GPL-2) software suite that is led by its main 
developer Richard Cochran and is supported by the Network Time Foundation 
(https://nwtime.org/).
The package linuxptp is generally useful for a part of our user base requiring 
a time synchronization of their system clocks in a network since it contains a 
PTP implementation compliant with the IEEE standard 1588. Especially users 
requiring higher precision than the one you can achieve with NTP. PTP is a 
standard synchronization solution that could be applied to systems such as 
automotive, telco, industrial or multimedia systems.

One specific reason for this MIR comes from the requirements of a
commercial partner who would like to offer linuxptp as part of their
user experience on their Ubuntu based SDK images. This partner is
working with the Canonical Partner Engineering team, albeit the
maintenance of linuxptp itself would likely be done by the Industrial
team.

There are some alternatives to linuxptp::
ptpd: https://launchpad.net/ubuntu/+source/ptpd / http://ptpd.sourceforge.net/ 
: package exists but upstream project seems unmaintained (with missing tag on 
last identified version that blocks the package upstream source version update: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934275).
ptpd2: https://sourceforge.net/projects/ptpd2/ : fork of ptpd that also seems 
unmaintained.
ptpv2d: https://code.google.com/archive/p/ptpv2d/ : seems unmaintained.

Overall, linuxptp looks like the current leading solution for Linux PTP
stack. And, there is no other/better way to solve this that is already
in main.

[Security]

* CVE history:
In 2021: 2 High sensitive CVE about out-of-bounds read and write operations 
have been filled for linuxptp version prior to 3.1.1. The version 3.1.1 being 
actually dedicated to the fix of these two CVE only:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3570
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3571

* CVE status:
There is a reference to the fix of these CVE on OpenWall:
https://www.openwall.com/lists/oss-security/2021/07/06/1
As well as on Ubuntu CVE tracker:
https://ubuntu.com/security/cves?package=linuxptp
With the associated Ubuntu Security Notice:
https://ubuntu.com/security/notices/USN-6097-1
And Debian security tracker:
https://security-tracker.debian.org/tracker/source-package/linuxptp

* Project Changelog and associated commits:
```
Version 3.1.1

Fixes:

CVE-2021-3570 linuxptp: missing length check of forwarded messages
CVE-2021-3571 linuxptp: wrong length of one-step follow-up in transparent 
clock
```

https://sourceforge.net/p/linuxptp/code/ci/ce15e4de5926724557e8642ec762a210632f15ca/
https://sourceforge.net/p/linuxptp/code/ci/0b3ab45de6a96ca181a5cf62c3c2b97167e2ed20/

* Launchpad Bugs:
With a quick analysis: There is no Launchpad Bug referring to any security 
issue: https://bugs.launchpad.net/ubuntu/+source/linuxptp

Linked to linuxptp package: There is only one open bug related to the
use of chronyd as the time
backend(https://bugs.launchpad.net/ubuntu/+source/linuxptp/+bug/2068526)
that quickly got a valid proposition to fix here(
https://bugs.launchpad.net/ubuntu/+source/linuxptp/+bug/2032805/comments/11).
This is a chronyd issue.

* Possible security flaws identified in the state of the art:

There are multiple articles about potential security issues while using
PTP that got published (e.g.
https://cybersecurity.springeropen.com/articles/10.1186/s42400-021-00080-y).
A key sensitive point we identify is TLVs authentication that could lead
to some security issues on PTP based stack
(https://cybersecurity.springeropen.com/articles/10.1186/s42400-023-00140-5).

Further analysis should be done by the security team.

* Package content:

There are no SGID/SUID binaries in the current package:

On noble, running: cd /tmp/ && sudo apt download linuxptp && dpkg -c
linuxptp_4.0-1_amd64.deb

Returns:
```
(...)
-rw-r--r-- root/root263 2024-04-02 01:32 
./usr/lib/systemd/system/phc2sys@.service
-rw-r--r-- root/root251 2024-04-02 01:32 
./usr/lib/systemd/system/ptp4l@.service
-rw-r--r-- root/root359 2024-04-02 01:32 
./usr/lib/systemd/system/timemaster.service
(...)
-rwxr-xr-x root/root14640 2024-04-02 01:42 ./usr/sbin/hwstamp_ctl
-rwxr-xr-x root/root83760 2024-04-02 01:42 ./usr/sbin/nsm
-rwxr-xr-x root/root91696 2024-04-02 01:42 ./usr/sbin/phc2sys
-rwxr-xr-x root/root31112 2024-04-02 01:42 ./usr/sbin/phc_ctl
-rwxr-xr-x root/root96640 2024-04-02 01:42 ./usr/sbin/pmc
-rwxr-xr-x root/root182120 2024-04-02 01:42 ./usr/sbin/ptp4l
-rwxr-xr-x root/root43320 2024-04-02 01:42 ./usr/sbin/timemaster
-rwxr-xr-x root/root91616 2024-04-02 01:42 

[Bug 2068078] Re: Fails to start on 24.04 – needs python3-setuptools?

[Alexandre Detiste]

fixed in 0.10.0-4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068078

Title:
  Fails to start on 24.04 – needs python3-setuptools?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whipper/+bug/2068078/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069860] Re: [needs-packaging] cmocka-extensions

[Alexandre Esse]

** Changed in: ubuntu
 Assignee: (unassigned) => Alexandre Esse (ahresse)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069860

Title:
  [needs-packaging] cmocka-extensions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2069860/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069878] [NEW] [needs-packaging] samconf

[Alexandre Esse]

Public bug reported:

Currently working on elos (https://github.com/Elektrobit/elos) software
packaging, the fourth dependency I would like to integrate into Ubuntu
is samconf (https://github.com/Elektrobit/samconf).

samconf is stands for signed and mergable configuration. It is used by
elos. The goal of the library is to manage program configuration options
from various sources including support for verification of the
configuration sources. This package will depend on cmocka-extensions
(https://bugs.launchpad.net/ubuntu/+bug/2069860), cmocka-mocks
(https://bugs.launchpad.net/ubuntu/+bug/2069875) and safu
(https://bugs.launchpad.net/ubuntu/+bug/2069877).

** Affects: ubuntu
 Importance: Undecided
 Assignee: Alexandre Esse (ahresse)
 Status: In Progress

** Changed in: ubuntu
 Assignee: (unassigned) => Alexandre Esse (ahresse)

** Changed in: ubuntu
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069878

Title:
  [needs-packaging] samconf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2069878/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069879] [NEW] [needs-packaging] elos

[Alexandre Esse]

Public bug reported:

Currently working on elos (https://github.com/Elektrobit/elos) software
packaging, I would like to integrate it into Ubuntu.

elos is a tool to collect, store and publish various system events (i.e.
syslogs, core dumps, measurements obtained from proc- and sys-fs, …)
while providing easy access to the collected data. This package will
depend on cmocka-extensions
(https://bugs.launchpad.net/ubuntu/+bug/2069860), cmocka-mocks
(https://bugs.launchpad.net/ubuntu/+bug/2069875), safu
(https://bugs.launchpad.net/ubuntu/+bug/2069877) and samconf
(https://bugs.launchpad.net/ubuntu/+bug/2069878).

** Affects: ubuntu
 Importance: Undecided
 Assignee: Alexandre Esse (ahresse)
 Status: In Progress

** Changed in: ubuntu
 Assignee: (unassigned) => Alexandre Esse (ahresse)

** Changed in: ubuntu
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069879

Title:
  [needs-packaging] elos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2069879/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069877] [NEW] [needs-packaging] safu

[Alexandre Esse]

Public bug reported:

Currently working on elos (https://github.com/Elektrobit/elos) software
packaging, the third dependency I would like to integrate into Ubuntu is
safu (https://github.com/Elektrobit/safu).

safu is a Library of common utility API's used in elos and samconf. This
package will depend on cmocka-extensions
(https://bugs.launchpad.net/ubuntu/+bug/2069860) and cmocka-mocks
(https://bugs.launchpad.net/ubuntu/+bug/2069875).

** Affects: ubuntu
 Importance: Undecided
 Assignee: Alexandre Esse (ahresse)
 Status: In Progress

** Changed in: ubuntu
 Assignee: (unassigned) => Alexandre Esse (ahresse)

** Changed in: ubuntu
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069877

Title:
  [needs-packaging] safu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2069877/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069875] [NEW] [needs-packaging] cmocka-mocks

[Alexandre Esse]

Public bug reported:

Currently working on elos (https://github.com/Elektrobit/elos) software
packaging, the second dependency I would like to integrate into Ubuntu
is cmocka-mocks (https://github.com/Elektrobit/cmocka_mocks).

cmocka-mocks is a library to mock common C functions, like libc and
jsonc, for testing purposes. This collection of ready to use mocks is
based on cmocka_extensions
(https://bugs.launchpad.net/ubuntu/+bug/2069860).

** Affects: ubuntu
 Importance: Undecided
 Assignee: Alexandre Esse (ahresse)
 Status: In Progress

** Changed in: ubuntu
 Assignee: (unassigned) => Alexandre Esse (ahresse)

** Changed in: ubuntu
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069875

Title:
  [needs-packaging] cmocka-mocks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2069875/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069860] [NEW] [needs-packaging] cmocka-extensions

[Alexandre Esse]

Public bug reported:

Currently working on elos (https://github.com/Elektrobit/elos) software
packaging, the first dependency I would like to integrate into Ubuntu is
cmocka-extensions (https://github.com/Elektrobit/cmocka_extensions).

cmocka-extensions are cmocka unit testing framework for C extended
features used by elos and other projects.

This package extends basic cmocka features and intoduces:
 * weak mocking
 * wrap mocking
 * and some definitions to make creating and running the unit tests a bit 
easier that the basic cmocka

** Affects: ubuntu
 Importance: Undecided
 Status: In Progress

** Changed in: ubuntu
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069860

Title:
  [needs-packaging] cmocka-extensions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2069860/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067196] Re: FTBFS gitsome 0.8.0+ds-9 fails to build without python3-six

[Alexandre Detiste]

Nice explanation.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067196

Title:
  FTBFS gitsome 0.8.0+ds-9 fails to build without python3-six

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gitsome/+bug/2067196/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062980] Re: nautilus progress bar on ubuntu dock icon does not update

[Alexandre Hen]

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2062980/+attachment/5771971/+files/Progress%20bar%20not%20working%20in%20ubuntu%20dock.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062980

Title:
  nautilus progress bar on ubuntu dock icon does not update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2062980/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062980] Re: nautilus progress bar on ubuntu dock icon does not update

[Alexandre Hen]

Same problem for me here.

# Rapport d’informations du système
---

## Détails du compte rendu
- **Date de génération :** 2024-04-28 15:57:01

## Informations liées au matériel :
- **Modèle du matériel :** ASRock X570 Taichi
- **Mémoire :**32,0 Gio
- **Processeur :** AMD Ryzen™ 7 5800X3D × 16
- **Carte graphique :**NVIDIA GeForce RTX™ 2080
- **Capacité du disque :** 8,5 To

## Informations liées au logiciel :
- **Version du micrologiciel :**   P5.01
- **Nom du système d’exploitation :**  Ubuntu 24.04 LTS
- **Construction du système d’exploitation :** (null)
- **Type de système d’exploitation :** 64 bits
- **Version de GNOME :**   46
- **Système de fenêtrage :**   X11
- **Version du noyau :**   Linux 6.8.0-31-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062980

Title:
  nautilus progress bar on ubuntu dock icon does not update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2062980/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Alexandre Hen]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+attachment/5771970/+files/dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem

[Alexandre Hen]

I had a lot of performance issues with nvidia-driver-535 and nautilus too 
(installed by default with 24.04 and my RTX 2080 card), but on X11.
Loading /usr/share/ directory could take 10-15 seconds.

Updating manually my drivers to nvidia-driver-550, without using ubuntu-
drivers, seems to have resolved this issue for me for the moment.

# Rapport d’informations du système
---

## Détails du compte rendu
- **Date de génération :** 2024-04-28 15:43:20

## Informations liées au matériel :
- **Modèle du matériel :** ASRock X570 Taichi
- **Mémoire :**32,0 Gio
- **Processeur :** AMD Ryzen™ 7 5800X3D × 16
- **Carte graphique :**NVIDIA GeForce RTX™ 2080
- **Capacité du disque :** 8,5 To

## Informations liées au logiciel :
- **Version du micrologiciel :**   P5.01
- **Nom du système d’exploitation :**  Ubuntu 24.04 LTS
- **Construction du système d’exploitation :** (null)
- **Type de système d’exploitation :** 64 bits
- **Version de GNOME :**   46
- **Système de fenêtrage :**   X11
- **Version du noyau :**   Linux 6.8.0-31-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062082

Title:
  24.04 Wayland vs Nautilus performance problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2062082/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Alexandre Hen]

Same problem for me on Ubuntu 24.04 fresh install on X11.

I tried updating my nvidia driver to nvidia-driver-550, but I keep
getting this "phantom" monitor in Gnome settings.

I have two physical monitors : 
- Main one : AOC 27" AG271QG with G-Sync
- Other one : Dell 25" 

$ find /sys/devices -name "edid"
/sys/devices/platform/simple-framebuffer.0/drm/card0/card0-Unknown-1/edid
/sys/devices/pci:00/:00:03.1/:0e:00.0/drm/card1/card1-HDMI-A-1/edid
/sys/devices/pci:00/:00:03.1/:0e:00.0/drm/card1/card1-DP-2/edid
/sys/devices/pci:00/:00:03.1/:0e:00.0/drm/card1/card1-Unknown-2/edid
/sys/devices/pci:00/:00:03.1/:0e:00.0/drm/card1/card1-DP-3/edid
/sys/devices/pci:00/:00:03.1/:0e:00.0/drm/card1/card1-DP-1/edid


[ Workaround ]
I type in terminal : sudo rm -f /dev/dri/card0

*After relogin : Phantom monitor has disappeared, but I lost my monitors' 
configuration (Main becoming second and vice versa, losing refresh rate too for 
the AOC).
No sign of the phantom screen in Gnome settings.

/dev/dri$ ls -l
total 0
drwxr-xr-x  2 root root100 avril 28 14:52 by-path
crw-rw+ 1 root video  226,   1 avril 28 14:52 card1
crw-rw+ 1 root render 226, 128 avril 28 14:52 renderD128

I set my monitors like before (refresh rate at 144Hz and main monitor
for the AOC), and reboot.

* After rebooting : phantom monitor is there again in Gnome settings. I
kept my monitors' configuration.

/dev/dri$ ls -l
total 0
drwxr-xr-x  2 root root100 avril 28 15:21 by-path
crw-rw+ 1 root video  226,   0 avril 28 15:21 card0
crw-rw+ 1 root video  226,   1 avril 28 15:21 card1
crw-rw+ 1 root render 226, 128 avril 28 15:21 renderD128


Other informations about my PC :

# Rapport d’informations du système
---

## Détails du compte rendu
- **Date de génération :** 2024-04-28 15:07:02

## Informations liées au matériel :
- **Modèle du matériel :** ASRock X570 Taichi
- **Mémoire :**32,0 Gio
- **Processeur :** AMD Ryzen™ 7 5800X3D × 16
- **Carte graphique :**NVIDIA GeForce RTX™ 2080
- **Capacité du disque :** 8,5 To

## Informations liées au logiciel :
- **Version du micrologiciel :**   P5.01
- **Nom du système d’exploitation :**  Ubuntu 24.04 LTS
- **Construction du système d’exploitation :** (null)
- **Type de système d’exploitation :** 64 bits
- **Version de GNOME :**   46
- **Système de fenêtrage :**   X11
- **Version du noyau :**   Linux 6.8.0-31-generic


** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 699847] Re: 2 errors in French translation

[Alexandre Detiste]

fixed in Debian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/699847

Title:
  2 errors in French translation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/699847/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 729433] Re: Does not start due to dependecies

[Alexandre Detiste]

fixed in Debian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729433

Title:
  Does not start due to dependecies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lincity-ng/+bug/729433/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056099] Re: [MIR] tree

[Alexandre Esse]

Here is a proposition of testsuite introduction with
https://gitlab.com/OldManProgrammer/unix-tree/-/merge_requests/19/diffs


** Patch added: "Debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+attachment/5760629/+files/add_tree_testsuite.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056099

Title:
  [MIR] tree

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2032805] Re: Could not open socket /var/run/timemaster/chrony.SOCK0

[Alexandre Esse]

** Also affects: chrony (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805

Title:
  Could not open socket /var/run/timemaster/chrony.SOCK0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2032805/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056099] Re: [MIR] tree

[Alexandre Esse]

Github issue related to this MIR: https://github.com/canonical/ubuntu-
mir/issues/52

** Bug watch added: github.com/canonical/ubuntu-mir/issues #52
   https://github.com/canonical/ubuntu-mir/issues/52

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056099

Title:
  [MIR] tree

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056099] [NEW] [MIR] tree

[Alexandre Esse]

Public bug reported:

[MIR] tree

[Availability]
The package tree is already in Ubuntu universe.
Tree is a general purpose utility that is built and works on all Ubuntu 
architectures.
Link to package https://launchpad.net/ubuntu/+source/tree

[Rationale]
The package tree is generally useful for a large part of our user base using 
the command-line. Tree itself is tiny, but is not currently seeded in our 
official images (albeit it is installed by default on a number of Ubuntu 
derivatives (Lubuntu - 
https://cdimage.ubuntu.com/lubuntu/releases/mantic/release/lubuntu-23.10-desktop-amd64.manifest
 , Xubuntu -  
https://cdimage.ubuntu.com/xubuntu/releases/mantic/release/xubuntu-23.10-desktop-amd64.manifest).
One specific reason for this MIR comes from the requirements of a commercial 
partner who would like to offer the tree command as part of their user 
experience on their Ubuntu based SDK images. This partner is working with the 
Canonical Partner Engineering team, albeit the maintenance of tree itself would 
likely be done by the Foundations team – this has been discussed with the 
Foundations team.
Package tree covers the same use case as ‘ls -lR’ or ‘find’, but is better 
because:
- It is specialized in directories tree rendering for command line interface, 
so it has a fancier output on a terminal.
- It provides machine-friendly output formats notably with its XML/JSON/HTML 
output formats.
- It would be useful to the community and to our partner to have “tree” in 
Ubuntu main, especially for their upcoming noble/24.04 based SDK.

[Security]
- Ubuntu CVE Tracker (https://ubuntu.com/security/cve?package=tree) : 0 results 
as of 2024-03-05.
- Debian Security Tracker: 
https://security-tracker.debian.org/tracker/source-package/tree: No issue as of 
2024-03-05.
- Project Changelog: (CHANGES file: 
http://oldmanprogrammer.net/source.php?dir=projects/tree/CHANGES): No reference 
to any security issue.
- No CVEs/security issues (found) in this software in the past: NB: “tree” is a 
very commonly used keyword, notably in security vulnerabilities, but searching 
the CVE database for software names matching “tree” didn’t yield issues with 
the tree utility itself.
- no `suid` or `sgid` binaries: `find / -perm -u=s -type f 2>/dev/null | grep 
tree` returns nothing – it’s just providing a simple non-privileged command.
- `ls -l /usr/bin/tree` returns: `-rwxr-xr-x 1 root root 85400 Dec 12 16:06 
/usr/bin/tree`.
- no executables in `/sbin` and `/usr/sbin`: `dpkg -L tree | grep sbin` returns 
nothing, it’s really just /usr/bin/tree.
- Package does not install services, timers or recurring jobs.
- Packages does not open privileged ports (ports < 1024).
- Package does not expose any external endpoints.
- I didn't spot any deprecated security algorithm in use.

[Quality assurance - function/usage]
- The package works well right after install and can be used to list the 
contents of directories.

[Quality assurance - maintenance]
The package is maintained well in Debian/Ubuntu/Upstream and does not have too 
many, long-term & critical, open bugs:
- Launchpad Bug Tracker (https://launchpad.net/ubuntu/+source/tree/+bugs): 2 
bugs reported in Ubuntu:
  * One issue seems pretty serious (buffer overflow), and there were fixes in 
the upstream sources that could correspond, however this bug wasn’t forwarded 
back then and there is no data to reproduce it – we’ve pinged the bug to 
request a copy of the data and to try to reproduce with a more recent version.
  * One issue is a feature request
- Debian https://bugs.debian.org/src:tree / 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;package=tree :
  * One resolved serious bug can be found on debian archived bug history.

Releases are relatively regular for a mature utility such as tree. Upstream 
recently changed its home site and seems responsive.
$ grep ^Version CHANGES 
Version 2.1.1 (05/31/2023)
Version 2.1.0 (12/26/2022)
Version 2.0.4 (09/06/2022)
Version 2.0.3 (08/26/2022)
Version 2.0.2 (02/16/2022)
Version 2.0.1 (01/03/2022)

The package does not deal with exotic hardware we cannot support.

[Quality assurance - testing]
There are no unit tests in the sources, and the autopkgtest 
(https://autopkgtest.ubuntu.com/packages/tree) is relatively trivial, but this 
seems adequate given this command-line utility.
A recent amd64 build log shows no warning nor errors: 
https://launchpadlibrarian.net/702286929/buildlog_ubuntu-noble-amd64.tree_2.1.1-2_BUILDING.txt.gz

[Quality assurance - packaging]
- debian/watch is present and works.
- debian/control defines a correct Maintainer field (currently: Florian Ernst 
).
- Running `lintian --pedantic` on tree_2.1.1-2_amd64.deb doesn’t output 
anything.
- This package does not rely on obsolete or about to be demoted packages.
- There is no Debconf questions with this package.
- Packaging and build is easy, (link to debian/rules: 
https://git.launchpad.net/ubuntu/+source/tree/tree/debian/rules?h=applied/ubuntu/noble).

[UI 

[Bug 1516441] Re: *** buffer overflow detected ***: tree terminated

[Alexandre Esse]

Thank you Sudip.

I cannot reproduce on tree package version 2.1.1-2 under Noble.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516441

Title:
  *** buffer overflow detected ***: tree terminated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/1516441/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Alexandre Erwin Ittner]

I got the same issue days ago when debugging a package in s390x, so it
is not architecture-specific.


ubuntu@devnoble1:~/libica-noble/libica-4.3.0$ lintian -I --pedantic  
--tag-display-limit 0
W: libica-utils: groff-message command exited with status 2: 
/usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 
-t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n 
-wmac -Tutf8 [usr/share/man/man1/icainfo-cex.1.gz:2]
W: libica-utils: groff-message command exited with status 2: 
/usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 
-t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n 
-wmac -Tutf8 [usr/share/man/man1/icainfo.1.gz:2]
W: libica-utils: groff-message command exited with status 2: 
/usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 
-t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n 
-wmac -Tutf8 [usr/share/man/man1/icastats.1.gz:2]
W: libica-utils: groff-message error: troff: Segmentation fault (core dumped) 
[usr/share/man/man1/icainfo-cex.1.gz:1]
W: libica-utils: groff-message error: troff: Segmentation fault (core dumped) 
[usr/share/man/man1/icainfo.1.gz:1]
W: libica-utils: groff-message error: troff: Segmentation fault (core dumped) 
[usr/share/man/man1/icastats.1.gz:1]
I: libica4: hardening-no-bindnow [usr/lib/s390x-linux-gnu/libica-cex.so.4.3.0]
I: libica4: hardening-no-bindnow [usr/lib/s390x-linux-gnu/libica.so.4.3.0]
I: libica4: symbols-file-missing-build-depends-package-field libica-cex.so.4 
[symbols]
I: libica4: symbols-file-missing-build-depends-package-field libica.so.4 
[symbols]
I: libica-utils: typo-in-manual-page paramater parameter 
[usr/share/man/man1/icastats.1.gz:76]
I: libica-utils: typo-in-manual-page sucessful successful 
[usr/share/man/man1/icastats.1.gz:126]
P: libica source: silent-on-rules-requiring-root [debian/control]
ubuntu@devnoble1:~/libica-noble/libica-4.3.0$




The apparmor profile issue was a nice catch, I was getting some trouble
to reproduce it in a minimal fashion, but that was because I was leaving
the pipeline just output to stdout.

Should we patch lintian to only write this to /tmp ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055402

Title:
  Though lintian call: error: troff: Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Alexandre Esse]

** Description changed:

  Hello,
  
  I was trying to run lintian on some deb packages an run onto some errors
  messages from groff.
  
  Steps to reproduce:
  
  1. Setup a LXD container with mantic or Noble:
  
  lxc launch ubuntu-daily:noble #or lxc launch ubuntu:mantic
  
- 2. Install lintian
+ 2. After getting connected to the container: Install lintian on it
  
  apt install lintian
  
- 3. Run lintian on some package:
+ 3. Run lintian on some package inside the container:
  
  apt download tree && lintian tree_*.deb
  
  4. Enjoy the groff-message logs:
  
  W: tree: groff-message command exited with status 2: 
/usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 
-t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n 
-wmac -Tutf8 [usr/share/man/man1/tree.1.gz:2]
  W: tree: groff-message error: troff: Segmentation fault (core dumped) 
[usr/share/man/man1/tree.1.gz:1]
  
  * Container infos:
  
  lsb_release -rd
  
  No LSB modules are available.
  Description:Ubuntu Noble Numbat (development branch)
  Release:24.04
  
  * Packages infos:
  
  apt-cache policy groff
  groff:
    Installed: (none)
    Candidate: 1.23.0-3
    Version table:
   1.23.0-3 500
  500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
  
  apt-cache policy lintian
  lintian:
    Installed: 2.117.0ubuntu1
    Candidate: 2.117.0ubuntu1
    Version table:
   *** 2.117.0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
  100 /var/lib/dpkg/status
  
  * Expected output (on Jammy): No segfault and no problem on the tested
  package with lintian (tree_2.1.1-2_amd64.deb)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055402

Title:
  Though lintian call: error: troff: Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault

[Alexandre Esse]

** Description changed:

  Hello,
  
  I was trying to run lintian on some deb packages an run onto some errors
  messages from groff.
  
  Steps to reproduce:
  
  1. Setup a LXD container with mantic or Noble:
  
  lxc launch ubuntu-daily:noble #or lxc launch ubuntu:mantic
  
  2. Install lintian
  
  apt install lintian
  
  3. Run lintian on some package:
  
  apt download tree && lintian tree_*.deb
  
  4. Enjoy the groff-message logs:
  
  W: tree: groff-message command exited with status 2: 
/usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 
-t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n 
-wmac -Tutf8 [usr/share/man/man1/tree.1.gz:2]
  W: tree: groff-message error: troff: Segmentation fault (core dumped) 
[usr/share/man/man1/tree.1.gz:1]
  
- 
  * Container infos:
  
  lsb_release -rd
  
  No LSB modules are available.
  Description:Ubuntu Noble Numbat (development branch)
  Release:24.04
  
  * Packages infos:
  
  apt-cache policy groff
  groff:
-   Installed: (none)
-   Candidate: 1.23.0-3
-   Version table:
-  1.23.0-3 500
- 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
+   Installed: (none)
+   Candidate: 1.23.0-3
+   Version table:
+  1.23.0-3 500
+ 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
  
  apt-cache policy lintian
  lintian:
-   Installed: 2.117.0ubuntu1
-   Candidate: 2.117.0ubuntu1
-   Version table:
-  *** 2.117.0ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2.117.0ubuntu1
+   Candidate: 2.117.0ubuntu1
+   Version table:
+  *** 2.117.0ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  * Expected output (on Jammy): No segfault and no problem on the tested
  package with lintian (tree_2.1.1-2_amd64.deb)
- 
- I set it to security vulnerable because it involves a segfault.

** Information type changed from Private Security to Public

** Also affects: groff (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055402

Title:
  Though lintian call: error: troff: Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1516441] Re: *** buffer overflow detected ***: tree terminated

[Alexandre Esse]

Hello bananenkasper,

There was some updates of tree since you reported this issue. Moreover,
some fix were about buffer overflow (specifically in v1.7.0 and v2.1.1).
Nowadays 2.1.1 is on noble so please, try to reproduce you issue with an
up to date version.

I couldn't reproduce you issue on my side. Can you please provide an
updated link to the material suitable to reproduce this bug? (I wasn't
able to download you file).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516441

Title:
  *** buffer overflow detected ***: tree terminated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/1516441/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Process to update major version of LMOD on LTS?

[Alexandre Strube]

Hi, I am the maintainer of LMOD on Debian.

For a long time we have been pushing for the update of LMOD on all systems.
Turns out that most of the clusters and supercomputers using Ubuntu are on
the LTS releases (20.04 and 22.04).

LMOD on them is a ancient version, prior to my time on Debian (6.x).

Many of the tools which rely on LMOD themselves deprecated support for LMOD
a while ago, or are about to.

In order to overcome that, I have been providing packages for Ubuntu (and
Debian Stable) on my Github repo [1], but I hope there’s a better way of
doing so.

I had a meeting yesterday with LMOD’s author, and he guarantees that this
is a drop-in replacement, and should be done officially.

Is there a way I can do so?


[1] https://github.com/surak/Lmod/releases/
<https://github.com/surak/Lmod/releases/tag/8.7.25>

[]
Alexandre Strube
su...@ubuntu.com
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: [ubuntu-studio-users] Frescobaldi package broken in Jammy

[Alexandre Peccioli]

Frescobaldi is having problems on Ubuntu 22.04, I advise you to install the
flatpak version or upgrade to Ubuntu 22.10.

Em qui., 17 de nov. de 2022 às 12:51, Erich Eickmeyer 
escreveu:

> Hi Viktor,
>
> On Thursday, November 17, 2022 12:57:16 AM PST Viktor Mastoridis wrote:
> > But On Tue Oct 25 2022 at 05:50:44 UTC, Steve Langasek wrote:
> > > I am prepared to argue in this case that a full-upstream update in SRU
> > > would be appropriate on the grounds that the package is completely
> > > unusable
> > > and therefore the regression potential is nil, and has a better chance
> > > of correctness than cherry-picking individual commits and hoping we've
> > > caught all the type errors.
> >
> > This doesn't obviously fix the problem of the missing dependency.  I
> >
> > > will check with the rest of the SRU team how they would want this
> handled.
> >
> > I would like to add my vote to this issue. I am a music teacher relying
> > heavily on Frescobaldi. It was never broken in the last 10 years on UBS
> and
> > this time I was taken by surprise, hoping that I can easily install 3.2
> > from code - but failed miserably and wasted many hours.
> >
> > I understand if nobody has the time to fix this. But I would like to say
> my
> > opinion on the importance of Frescobaldi.
> >
> > Music production, performance and education are closely connected. Many,
> if
> > not most of us musicians teach in addition to music making. *Especially
> > during and after Covid. *
> > In that light, Ubuntu Studio could reconsider the importance of
> > Frescobaldi. It plays a crucial role in music education (alongside
> > Lilypond, of course:-) and should have a status same as Ardour or Jack;
> and
> > not treated as a secondary 'add-on'.
> >
> > Viktor Mastoridis
> > Music producer and educator
>
> Missing context. You appear to have replied to the thread in the wrong
> mailing
> list? I know Steve Langasek but he's not subscribed to this mailing list,
> and
> if your intent was to bring this mailing list into the discussion, it
> would've
> been better to add this mailing list so that there could've been some sort
> of
> trail to follow, i.e. we could've seen the previous messages for some
> context.
>
> That said, I'm at least tangentially aware of the frescobaldi situation.
> Frescobaldi isn't a package we carry in Ubuntu Studio. Ubuntu Studio is
> merely
> a different default installation of Ubuntu, otherwise it's completely
> Ubuntu
> once installed and not a separate distribution. Therefore, there's no need
> to
> go through Ubuntu Studio for the issues you're having. Steve is one of the
> highest-ranking developers in Ubuntu (above even me), so you're already
> talking to the right people.
>
> --
> Erich Eickmeyer
> Project Leader - Ubuntu Studio
> Ubuntu MOTU--
> ubuntu-studio-users mailing list
> ubuntu-studio-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
>
-- 
ubuntu-studio-users mailing list
ubuntu-studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

[Ubuntu-BR] Como resolver a vulnerabilidade TCP Sequence Number Approximation Based Denial of Service

[Thiago Silveira Alexandre]

Bom dia pessoal! Tudo bem?

Preciso de ajuda para resolver a vulnerabilidade "TCP Sequence Number
Approximation Based Denial of Service.
Encontrei o link https://ubuntu.com/security/CVE-2004-0230, mas fiquei em
dúvida. A instalação do Quagga vai resolver a vulnerabilides?

Se alguém tiver alguma outra saída para resolver essa vuln, ficarei muito
grato.

Obrigado.

-- 
Thiago Silveira
-- 
Mais sobre o Ubuntu em português: http://www.ubuntu-br.org/comece

Lista de discussão Ubuntu Brasil
Histórico, descadastramento e outras opções:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-br

Re: systemd-oomd issues on desktop

[Michel Alexandre Salim]

Hi,   


I'm part of the team that worked on the Fedora Change Proposal that   
enabled systemd-oomd by default:
https://fedoraproject.org/wiki/Changes/EnableSystemdOomd  


Joining this discussion late, apologies - I wasn't subscribed to  
ubuntu-devel prior to today, but will try to catch up on the thread on
the archive online.   


I had a discussion about the lack of notification before a kill with  
pabs on the debian-mentors channel recently (while packaging psi-notify
for Debian; Ubuntu PPA is here:   
https://launchpad.net/~michel-slm/+archive/ubuntu/psi-notify) 


(both psi-notify and systemd-oomd act on the same pressure information,
but psi-notify just notifies you when certain thresholds while oomd   
kills the cgroup that causes most of the memory pressure to try and
stop
getting to a situation where the kernel does it, and likely pick a
worse
target).

pabs and I agreed that having an actionable notification prior to the
actual
kill would be an improvement, even if the process likely to be killed 
might differ between the notification and the actual kill, and after  
discussing this with the team, Anita published this RFC last week:


https://github.com/systemd/systemd/issues/23606   


Given that we have two major distributions now shipping oomd (Fedora  
and Ubuntu -- strictly in chronological order, not implying any value 
judgement here), should we discuss any potential tweak / improvement  
either on the GitHub issue and/or on the systemd-devel mailing list?  


https://lists.freedesktop.org/mailman/listinfo/systemd-devel  


It will probably be good to share as much implementation details as   
possible and get them applied upstream.   


Best regards,
   
-- 
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: This is a digitally signed message part
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

[Bug 1976594] [NEW] Detect RAM size automatically and other fixes

[Alexandre Ghiti]

Public bug reported:

[Impact]

We need this new package because it allows to detect memory size at
runtime: if the memory is not discovered automatically, the Nezha can't
boot without an additional memory node in the device tree. The issue is
that the Nezha boards comes now with 2 different amounts of memory, 1GB
or 2GB. So the additional device tree node can't cover both boards.

In addition:
- we fixed the model string which changed in the last DTB from the kernel we'll 
use
- the vendor updated to version 2022.04, which brings more stability
- we added the Built-using field to the package so that we know which opensbi 
version we use

It is essential to backport this fix to Jammy as we intend to provide first 
support for the Nezha board in 22.04.1.
 
[Test Plan]

This package must be tested with the nezha-boot0 package whose SRU can
be found in [1] and the corresponding package in [2]. It also requires a
custom kernel (for now, but the kernel is working on its packaging)
which can be found in [3].

I tested those packages on the Nezha board with 1G of RAM and the
LicheeRV board with 512M of RAM.

[1] https://bugs.launchpad.net/ubuntu/+source/nezha-boot0/+bug/1965260
[2] 
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13653972/+listing-archive-extra
[3] 
https://github.com/AlexGhiti/riscv-linux/tree/int/alex/nezha_Ubuntu-unstable-5.17.0-8.8

[Where problems could occur]

This package was never used before (and should not have been) as we did
not provide any image for Jammy 22.04, the plan is 22.04.1.

[Other Info]

We decided to update the version of the u-boot since the vendor patches
were updated (some added) on this new release only.

** Affects: u-boot-nezha (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976594

Title:
  Detect RAM size automatically and other fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot-nezha/+bug/1976594/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: +1 Maintenance report 23-27 May 2022

[Alexandre Ghiti]

And I forgot to mention:

astroquery


I added a patch to fix the permission denied on accessing files here :
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13638113/+listing-archive-extra
But then autopkgtest fails on armhf
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-alexghiti-riscv/kinetic/armhf/a/astroquery/20220525_104624_1622f@/log.gz
There is no obvious reason in the link above but when launched locally, the
error was not the same and may be more helpful:

vals = ['9048843364125']

def generic_converter(vals):
 > return numpy.array(vals, numpy_type)
E OverflowError: Python int too large to convert to C long

/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:1004: OverflowError

I won't have time to follow up on this though.

Thanks,

Alex

On Mon, May 30, 2022 at 11:54 AM Alexandre Ghiti <
alexandre.gh...@canonical.com> wrote:

> Hi,
>
> I was on +1 maintenance last week, below what I worked on:
>
> netdata
> ==
>
> It was a simple sync since Debian merged the patch that I had added
> previously. This was uploaded by @Graham Inggs .
>
> node-gulp-coffee
> =
>
> node-gulp-coffee timeouts on tests on arm64 only, I increased the timeout
> and the tests passed. This was uploaded by @Graham Inggs .
>
> libgpg-error
> =
>
> It regressed on i386 because debian removed the test directive
> "skip-not-installable". Indeed, Ubuntu i386 autopkgtest runners actually
> run on amd64 and use multi-arch which then used to trigger amd64 tests on
> for i386 builds which then failed. This was fixed by @Lukas Märdian here
> https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673. But
> as explained in the bug report, the i386 test still fails: this is because
> autopkgtest tries to install gcc-mingw-w64-i686:i386 which does not exist,
> gcc-mingw-w64-i686:all does though. Either a fix is needed in autopkgtest
> in order to fallback to :all when :$arch does not, or I was told that this
> package could be missing Multi-Arch: foreign field. *Anyway, I'm still
> working on this.*
>
> aqsis
> 
>
> aqsis FTBFS on armhf because Debian had support for qt5 and armhf qt5
> libraries lack support for some OpenGL functions: indeed, armhf qt5
> libraries use the OpenGL ES 2.0 mode
> (qtbase-opensource-src-5.15.4+dfsg/debian/rules), which is only a subset of
> OpenGL 2.0 and does not contain the missing functions (
> https://www.khronos.org/registry/OpenGL/specs/es/2.0/es_cm_spec_2.0.pdf).
> And it regressed on i386 because the last build for this arch was removed
> from release: I added a Britney hint to make it pass (Thanks @Graham Inggs
>  for this).
>
> This was uploaded by @Graham Inggs .
>
> dropbear
> ===
>
> dropbear regressed on all archs because of the following issues:
>
> - mkdir fail because ~/.ssh already exists => use mkdir -p
> - tests find the installed kernel by matching kernel packages suffixed by
> -$arch (like Debian does) whereas in Ubuntu they are suffixed by -generic
> - mmdebstrap fails because the sources.list was grepped against 'Origin:
> Debian' => change that for 'Origin: Ubuntu'
>
> The package built successfully in my PPA and I locally validated that
> autopkgtest passes on amd64 but I had to increase the memory size of the
> VM, I'll add this package to big_packages too. @Graham Inggs
>  just told me that autopkgtest failed on
> armhf for another reason, I'll fix that and ask for uploading: *I'm still
> working on this*.
>
> That's it,
>
> Thanks,
>
> Alex
>
>
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

+1 Maintenance report 23-27 May 2022

[Alexandre Ghiti]

Hi,

I was on +1 maintenance last week, below what I worked on:

netdata
==

It was a simple sync since Debian merged the patch that I had added
previously. This was uploaded by @Graham Inggs .

node-gulp-coffee
=

node-gulp-coffee timeouts on tests on arm64 only, I increased the timeout
and the tests passed. This was uploaded by @Graham Inggs .

libgpg-error
=

It regressed on i386 because debian removed the test directive
"skip-not-installable". Indeed, Ubuntu i386 autopkgtest runners actually
run on amd64 and use multi-arch which then used to trigger amd64 tests on
for i386 builds which then failed. This was fixed by @Lukas Märdian here
https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673. But as
explained in the bug report, the i386 test still fails: this is because
autopkgtest tries to install gcc-mingw-w64-i686:i386 which does not exist,
gcc-mingw-w64-i686:all does though. Either a fix is needed in autopkgtest
in order to fallback to :all when :$arch does not, or I was told that this
package could be missing Multi-Arch: foreign field. *Anyway, I'm still
working on this.*

aqsis


aqsis FTBFS on armhf because Debian had support for qt5 and armhf qt5
libraries lack support for some OpenGL functions: indeed, armhf qt5
libraries use the OpenGL ES 2.0 mode
(qtbase-opensource-src-5.15.4+dfsg/debian/rules), which is only a subset of
OpenGL 2.0 and does not contain the missing functions (
https://www.khronos.org/registry/OpenGL/specs/es/2.0/es_cm_spec_2.0.pdf).
And it regressed on i386 because the last build for this arch was removed
from release: I added a Britney hint to make it pass (Thanks @Graham Inggs
 for this).

This was uploaded by @Graham Inggs .

dropbear
===

dropbear regressed on all archs because of the following issues:

- mkdir fail because ~/.ssh already exists => use mkdir -p
- tests find the installed kernel by matching kernel packages suffixed by
-$arch (like Debian does) whereas in Ubuntu they are suffixed by -generic
- mmdebstrap fails because the sources.list was grepped against 'Origin:
Debian' => change that for 'Origin: Ubuntu'

The package built successfully in my PPA and I locally validated that
autopkgtest passes on amd64 but I had to increase the memory size of the
VM, I'll add this package to big_packages too. @Graham Inggs
 just told me that autopkgtest failed on armhf
for another reason, I'll fix that and ask for uploading: *I'm still working
on this*.

That's it,

Thanks,

Alex
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

[Bug 1975673] Re: libgpg-error/1.45-2 fails autopkgtest on i386

[Alexandre Ghiti]

I think there's another problem: it fails to install gcc-mingw-w64-i686
because autopkgtest tries to install gcc-mingw-w64-i686:i386 which does
not exist since it only exists as gcc-mingw-w64-i686:all.

I added :all to the test dependency, and then it works, the test passes
correctly on i386 \o/

But I'll come up with the proper patch in autopkgtest: it should try
:$arch first and then :all in case it does not work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975673

Title:
  libgpg-error/1.45-2 fails autopkgtest on i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974438] [NEW] Info segfaults on open when LANG=pt-BR

[Alexandre Pereira Nunes]

Public bug reported:

When using my default locale info segfaults on open:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `info'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140004652754752) 
at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: Arquivo ou diretório inexistente.
(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140004652754752) 
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140004652754752) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=140004652754752, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
#3  0x7f555f9c7476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#4  0x7f555f9ad7f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x55e7b9c13546 in replace_in_documentation (
string=0x7f555fbf61ed "Bem vindo à versão Info %s. Digite 
\\[get-help-window] p/ ajuda,\\[get-inffo-help-node] p/ tutorial.", 
help_is_only_window_p=help_is_only_window_p@entry=0) at ./info/infodoc.c:722
#6  0x55e7b9c068c8 in display_startup_message () at ./info/session.c:187
#7  info_session (error=, user_filename=0x0, 
ref_list=0x55e7ba92b050) at ./info/session.c:208
#8  main (argc=, argv=) at ./info/info.c:1079


if I do LC_ALL=C info then it opens normally. It seems the translation string 
is not matching some positional parameter in the original string, but I didn't 
check that far.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: info 6.8-4build1
ProcVersionSignature: Ubuntu 5.15.0-32.33-lowlatency 5.15.35
Uname: Linux 5.15.0-32-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 20 09:13:44 2022
InstallationDate: Installed on 2019-05-30 (1085 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: texinfo
UpgradeStatus: Upgraded to jammy on 2022-04-30 (19 days ago)

** Affects: texinfo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974438

Title:
  Info segfaults on open when LANG=pt-BR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1974438/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973700] [NEW] Sync opensbi 1.0-4 (main) from Debian unstable (main)

[Alexandre Ghiti]

Public bug reported:

Please sync opensbi 1.0-4 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * debian/patches:
+ Replace update-isa-spec.patch with the upstream variant that allows both
  old toolchains and new toolchains that support the new ISA spec to build
  openSBI
  * debian/control:
+ Update maintainer to Ubuntu developers

The first ubuntu patch was merged in debian, so there isn't any more ubuntu
delta to carry on.

Changelog entries since current kinetic version 1.0-3ubuntu1:

opensbi (1.0-4) unstable; urgency=medium

  * debian/patches: Use upstream patch to fix compatibility with binutils
2.38+.
  * debian/control: Drop versioned Build-Depends on binutils.
  * debian/bin/git-snapshot: Switch to tar.gz format. (Closes: #1003155)

 -- Vagrant Cascadian   Sat, 26 Mar 2022 16:47:21
-0700

** Affects: opensbi (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: fr-2389

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973700

Title:
  Sync opensbi 1.0-4 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/1973700/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973700] Re: Sync opensbi 1.0-4 (main) from Debian unstable (main)

[Alexandre Ghiti]

The synced package built successfully in my PPA [1].

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13619045/+listing-
archive-extra

** Tags added: fr-2389

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973700

Title:
  Sync opensbi 1.0-4 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/1973700/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

[Alexandre Ghiti]

The package successfully built in my PPA [1].

Note that I forgot to replace the changelog signoff with mine, please
use the following:

-- Alexandre Ghiti   Mon, 28 Mar 2022
18:31:38 +

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13619002/+listing-
archive-extra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973607

Title:
  Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973601] Re: Please merge libsigsegv 2.14 (main) from Debian unstable (main)

[Alexandre Ghiti]

Note that I also forgot to replace the changelog signoff with mine,
please use the following:

-- Alexandre Ghiti   Sun, 30 Jan 2022
21:51:59 +

Sorry again, thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973601

Title:
  Please merge libsigsegv 2.14 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973601] Re: Please merge libsigsegv 2.14 (main) from Debian unstable (main)

[Alexandre Ghiti]

The package successfully built in my PPA [1].

Note that I forgot to add the bug number to the changelog, sorry about
that.

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13618940/+listing-
archive-extra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973601

Title:
  Please merge libsigsegv 2.14 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

[Alexandre Ghiti]

Please find attached the debdiff between debian package and the ubuntu
one.

** Patch added: "debdiff_debian_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590044/+files/debdiff_debian_ubuntu.debdiff

** Tags added: fr-2388

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973607

Title:
  Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

[Alexandre Ghiti]

Please find attached the debdiff between old ubuntu version and the new
one.

** Patch added: "debdiff_oldubuntu_newubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590043/+files/debdiff_oldubuntu_newubuntu.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973607

Title:
  Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973607] [NEW] Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

[Alexandre Ghiti]

Public bug reported:

Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

** Affects: logrotate (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973607

Title:
  Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973601] Re: Please merge libsigsegv 2.14 (main) from Debian unstable (main)

[Alexandre Ghiti]

Please find attached the debdiff between the old ubuntu version and the
new one.

** Patch added: "debdiff_oldubuntu_newubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+attachment/5590041/+files/debdiff_oldubuntu_newubuntu.debdiff

** Tags added: fr-2387

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973601

Title:
  Please merge libsigsegv 2.14 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973601] Re: Please merge libsigsegv 2.14 (main) from Debian unstable (main)

[Alexandre Ghiti]

Please find attached the debdiff between debian package and the new
ubuntu one.

** Patch added: "debdiff_debian_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+attachment/5590040/+files/debdiff_debian_ubuntu.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973601

Title:
  Please merge libsigsegv 2.14 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973601] [NEW] Please merge libsigsegv 2.14 (main) from Debian unstable (main)

[Alexandre Ghiti]

Public bug reported:

merge libsigsegv 2.14 (main) from Debian unstable (main)

** Affects: libsigsegv (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973601

Title:
  Please merge libsigsegv 2.14 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsigsegv/+bug/1973601/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965260] Re: FFE: Detect RAM size automatically

[Alexandre Ghiti]

** Description changed:

  https://github.com/smaeul/sun20i_d1_spl/commits/d1-2022-01-22, commit
  525883d3721f4c4d78b498e780b44e85d0676abf contains patches to detect the
  RAM size automatically.
+ 
+ [Impact]
+ 
+ If the memory is not discovered automatically, the Nezha can't boot
+ without an additional memory node in the device tree: the issue is that
+ the Nezha boards comes now with 2 different amounts of memory, 1GB or
+ 2GB. So the additional device tree node can't cover both boards.
+ 
+ It is essential to backport this fix to Jammy as we intend to provide
+ first support for the Nezha board in 22.04.1.
+ 
+ [Test Plan]
+ 
+ To test the fix is correct, one can simply use this nezha-boot0 and
+ check that the next stage bootloader (u-boot-nezha) advertises the right
+ amount of memory for the board, which is displayed at boot right after
+ the banner:
+ 
+ U-Boot 2022.04 (Apr 21 2022 - 09:19:39 +)
+ 
+ DRAM:  1 GiB
+ sunxi_set_gate: (CLK#24) unhandled
+ 
+ [Where problems could occur]
+ 
+ The update will not introduce regressions as this package is *not* used
+ since we did not deliver images for the Nezha board yet, support for
+ this board is an additional feature scheduled for 22.04.1.
+ 
+ [Other Info]
+ 
+ Note that this only fixes the memory detection from boot0 to u-boot,
+ another similar patch is needed for u-boot-nezha to patch the kernel
+ device tree.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965260

Title:
  FFE: Detect RAM size automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nezha-boot0/+bug/1965260/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973168] [NEW] Package still suggests to install crda whereas it was removed

[Alexandre Ghiti]

Public bug reported:

This package still suggests crda to be installed whereas it was removed
from jammy already: simply remove this from debian/control as done in
[1].

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13612257/+listing-
archive-extra

** Affects: wireless-regdb (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973168

Title:
  Package still suggests to install crda whereas it was removed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1973168/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1955042] Re: SBI SRST extension is missing

[Alexandre Ghiti]

This fix was merged in 5.15.0-1005.5.

** Changed in: linux-riscv (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955042

Title:
  SBI SRST extension is missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1955042/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968333] [NEW] FTBFS

[Alexandre Ghiti]

Public bug reported:

All archs have build from 2020, except riscv64 which does not have any
available: I tried to rebuild this package in my PPA [1] and it fails. I
fixed all vala compilation errors that I was seeing locally (but not in
the build logs above) and fixed an outdated path to dconf-service: you
can find the diff attached.

But then tests fail and I fail to fix this:

make  check-TESTS
make[5]: Entering directory 
'/home/ubuntu/indicator-keyboard/indicator-keyboard/tests'
# random seed: R02S17152843af8958ff21f0460bf77a5d11
1..9
# Start of indicator-keyboard-service tests
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service 
name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=96722 comm="gsettings 
set org.gnome.desktop.input-sources curr" label="unconfined")
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 
'ca.desrt.dconf'
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service 
name='com.canonical.indicator.keyboard' requested by ':1.0' (uid=1000 pid=96716 
comm="./indicator-keyboard-tests " label="unconfined")
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service 
name='org.gtk.vfs.Daemon' requested by ':1.4' (uid=1000 pid=96735 
comm="/home/ubuntu/indicator-keyboard/indicator-keyboard" label="unconfined")
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 
'org.gtk.vfs.Daemon'

(indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.004:
ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.005:
ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.005: 
ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 
'com.canonical.indicator.keyboard'
current = 2
output = "uint32 2
"
A connection to the bus can't be made
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
ok 1 /indicator-keyboard-service/activate-input-source
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
dbus-daemon[96761]: [session uid=1000 pid=96761] Activating service 
name='com.canonical.indicator.keyboard' requested by ':1.0' (uid=1000 pid=96716 
comm="./indicator-keyboard-tests " label="unconfined")
dbus-daemon[96761]: [session uid=1000 pid=96761] Activating service 
name='org.gtk.vfs.Daemon' requested by ':1.1' (uid=1000 pid=96763 
comm="/home/ubuntu/indicator-keyboard/indicator-keyboard" label="unconfined")
dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 
'org.gtk.vfs.Daemon'

(indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.792:
ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.793:
ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.793: 
ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed
dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 
'com.canonical.indicator.keyboard'
[Invalid UTF-8] Bail out! GLib-GObject-FATAL-WARNING: g_object_notify: object 
class 'Service' has no property named '\xc0[u\x1d\x9fU'

(./indicator-keyboard-tests:96716): GLib-GObject-WARNING **: 12:09:46.826: 
g_object_notify: object class 'Service' has no property named 
'\xc0[u\u001d\x9fU'
Trace/breakpoint trap (core dumped)

[Bug 1968146] [NEW] unattended-upgrade cancellation does not work

[Alexandre Ghiti]

Public bug reported:

Cancelling the unattended-upgrade at the very end of the installation
process does not seem to work as we can see in the logs that the upgrade
goes on: this issue is particularly visible on riscv where it takes a
very long time.

Attached a targz of /var/log.

** Affects: subiquity (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968146

Title:
  unattended-upgrade cancellation does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1968146/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968146] Re: unattended-upgrade cancellation does not work

[Alexandre Ghiti]

** Attachment added: "log.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1968146/+attachment/5577853/+files/log.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968146

Title:
  unattended-upgrade cancellation does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1968146/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks

[Alexandre Ghiti]

The workaround built successfully in my PPA:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13413205/+listing-
archive-extra

I tested it successfully with the RISC-V live installer (where this
problem was seen).

I did not have time yet to work on the proper fix so I think we should
go for this workaround: @xnox what do you think?

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967130

Title:
  rcu_sched detected stalls on CPUs/tasks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks

[Alexandre Ghiti]

I have a workaround for this:

UBUNTU: SAUCE: riscv: Disable VMAP_STACK since it fails with efi

When VMAP_STACK is enabled, kernel threads have their stacks in the vmalloc
region.

So when The kworker responsible for handling efi work queue (efi_call_rts) 
calls
efi_virtmap_load and then switch_mm, if the stack of the worker is in a 
vmalloc
area not yet synchronized with efi_mm (since RISC-V lazily populates vmalloc
area), an attempt to access this stack will trigger a fault which can't be
resolved since when trying to save the context, a new trap will be 
triggered and
so on.

So disable VMAP_STACK for now until we figure out the correct fix.

And I'm working on the proper fix which consists in synchronizing the
efi page table with the page table of the calling thread before
switching to efi mm.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967130

Title:
  rcu_sched detected stalls on CPUs/tasks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965321] Re: u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

[Alexandre Ghiti]

As reported here, there is an issue with the PCI controller on the
unmatched board that must be fixed in Linux (cf [1]) and u-boot: for
u-boot, the upstream commit a398a51ccc68c0a7aee14f8328dc86a1a4cfba85
("pci: Work around PCIe link training failures") should be cherry-picked
for 22.04.

Thanks

[1] https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796

** Changed in: u-boot (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965321

Title:
  u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1965321/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964796] Re: Fix unmatched ASMedia ASM2824 PCIe link training

[Alexandre Ghiti]

A similar patch that solves the same issue was actually merged for 5.18
[1].

I encountered this bug with our current u-boot (2022.01+dfsg-2ubuntu1)
and linux kernel (5.15.0-1004.4): I applied the patch in [1] on top of
5.15.0-1004.4 successfully and it solved the problem. So as you already
tagged it, this should be cherry-picked for 22.04. A similar patch for
u-boot exists, I'll report a new bug there.

Thanks

[1] https://patchwork.kernel.org/project/linux-
riscv/patch/20220318152430.526320-1-ben.do...@codethink.co.uk/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964796

Title:
  Fix unmatched ASMedia ASM2824 PCIe link training

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: more libs ?

[Alexandre Strube]

Hi Henri,

you can always join the Debian project and make debian packages for those 
softwares. In time, those will be brought to ubuntu.

Or, you know, you can use

pip --user

or use a proper virtual environment.



> On 21. Mar 2022, at 13:37, Henri Girard  wrote:
> 
> Hi,
> 
> I use py3dmol, nglview , ase-notebook( ase is in python-ase) threejs 3dmoljs 
> pytraj ccptraj ... etc, but they aren't easy to install and I don't want to 
> use anaconda which is very sensible with upgrade and env, I use pip but i 
> need it as sudo -H pip et I get messages from a recent times that is not 
> really good to this to avoid mixing ?
> 
> So is someone able to integrate them in ubuntu ?
> 
> Best
> 
> Regards
> 
> Henri
> 
> 
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss



signature.asc
Description: Message signed with OpenPGP
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

[Bug 1965321] Re: u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

[Alexandre Ghiti]

This issue seems to have a fix in Linux, which is nice since it does not
depend on u-boot at all:

https://patchwork.kernel.org/project/linux-
riscv/patch/20220318152430.526320-1-ben.do...@codethink.co.uk/

I'll give it a try.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965321

Title:
  u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1965321/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1946773] Re: "An error occurred. Press enter to start a shell"

[Alexandre Ghiti]

For the record, we fell onto the same issue with the RISC-V live
installer on the SiFive Unmatched board whose logs are attached. In
those logs you'll see a kernel bug that I'm currently investigating
which is likely caused by the md5check job.

Adding fsck.mode=skip to the command line fixed the issue for us.

** Attachment added: "log_fail_cloud_init.tar.gz"
   
https://bugs.launchpad.net/subiquity/+bug/1946773/+attachment/5570361/+files/log_fail_cloud_init.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946773

Title:
  "An error occurred. Press enter to start a shell"

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1946773/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965321] Re: u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

[Alexandre Ghiti]

And:

ubuntu@ubuntu:~$ sudo apt info u-boot-sifive=2021.07+dfsg-0ubuntu10
Package: u-boot-sifive
Version: 2021.07+dfsg-0ubuntu10
Built-Using: opensbi (= 0.9+187.52af6e4b52-0ubuntu1)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965321

Title:
  u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1965321/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965321] Re: u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

[Alexandre Ghiti]

Actually the last assertion is wrong:

ubuntu@ubuntu:~$ sudo apt info u-boot-sifive=2021.07+dfsg-0ubuntu8
Package: u-boot-sifive
Version: 2021.07+dfsg-0ubuntu8
Built-Using: opensbi (= 0.9-2ubuntu2)

ubuntu@ubuntu:~$ sudo apt info u-boot-sifive=2022.01+dfsg-2ubuntu1
Package: u-boot-sifive
Version: 2022.01+dfsg-2ubuntu1
Built-Using: opensbi (= 1.0-3ubuntu1)

One more thing to check on my side.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965321

Title:
  u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1965321/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965321] [NEW] u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

[Alexandre Ghiti]

Public bug reported:

When booting a jammy image on the SiFive Unmatched board, the nvme disk
do not appear whereas by simply replacing u-boot with the previous
version 2021.07+dfsg-0ubuntu8 works fine.

Could be related to upstream commit
a398a51ccc68c0a7aee14f8328dc86a1a4cfba85 ("pci: Work around PCIe link
training failures"), I have to try.

This does not look related to opensbi as both versions were built
against the same opensbi version.

** Affects: u-boot (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965321

Title:
  u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1965321/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961425] Re: 22.04: FTBFS due to test failure

[Alexandre Erwin Ittner]

Just noticed that version 0.8.0-2ubuntu2 (
https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu2 ) landed
at the start of the month. This version has a patch that fixes the
string issue; renameat2 issue remains, but it won't trigger unless
building (and running the unit tests) from a ZFS volume.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961425

Title:
  22.04: FTBFS due to test failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1961425/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962837] Re: netdata: FTBFS on riscv64

[Alexandre Ghiti]

The CI failed upstream with the following patch, but at first sight, it
seems unrelated to this patch (a bit weird though since all other PRs
passed). Anyway, the package built successfully for all archs so I think
we can upload it.

** Patch added: 
"0001-debian-Add-patch-to-unconditionally-link-against-lib.patch"
   
https://bugs.launchpad.net/ubuntu/+source/netdata/+bug/1962837/+attachment/5567916/+files/0001-debian-Add-patch-to-unconditionally-link-against-lib.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962837

Title:
  netdata: FTBFS on riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netdata/+bug/1962837/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962837] Re: netdata: FTBFS on riscv64

[Alexandre Ghiti]

A developer agreed on the fix proposed in [1], so proposed a PR in [2].
Note that the patch in PR was tested successfully against all architectures [3]

[1] https://github.com/netdata/netdata/issues/12319
[2] https://github.com/netdata/netdata/pull/12366
[3] 
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13305735/+listing-archive-extra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962837

Title:
  netdata: FTBFS on riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netdata/+bug/1962837/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962837] Re: netdata: FTBFS on riscv64

[Alexandre Ghiti]

As explained in [1], I have a fix but I wait a few days for upstream to
review it before uploading.

[1] https://github.com/netdata/netdata/issues/12319

** Bug watch added: github.com/netdata/netdata/issues #12319
   https://github.com/netdata/netdata/issues/12319

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962837

Title:
  netdata: FTBFS on riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netdata/+bug/1962837/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951065] Re: [MIR] libio-prompt-tiny-perl

[Alexandre Ghiti]

The following packages would also need an MIR because they are new
dependencies of lintian which is in main. Note that all those packages
are maintained by the Debian Perl Group :

* libsyntax-keyword-try-perl
* libxs-parse-keyword-perl
* libdata-validate-uri-perl
* libdata-validate-ip-perl
* libnet-ipv6addr-perl
* libnet-netmask-perl
* libmath-base85-perl

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951065

Title:
  [MIR] libio-prompt-tiny-perl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdata-validate-ip-perl/+bug/1951065/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951065] Re: [MIR] libio-prompt-tiny-perl

[Alexandre Ghiti]

** Also affects: libsyntax-keyword-try-perl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libxs-parse-keyword-perl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libdata-validate-uri-perl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libdata-validate-ip-perl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libnet-ipv6addr-perl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libnet-netmask-perl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libmath-base85-perl (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951065

Title:
  [MIR] libio-prompt-tiny-perl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdata-validate-ip-perl/+bug/1951065/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957100] Re: Merge lintian 2.114.0 from Debian unstable

[Alexandre Ghiti]

** Attachment added: "debdiff_oldubuntu_newubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+attachment/5563518/+files/debdiff_oldubuntu_newubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957100

Title:
  Merge lintian 2.114.0 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957100] Re: Merge lintian 2.114.0 from Debian unstable

[Alexandre Ghiti]

** Attachment added: "debdiff_oldubuntu_newubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+attachment/5563511/+files/debdiff_oldubuntu_newubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957100

Title:
  Merge lintian 2.114.0 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957100] Re: Merge lintian 2.114.0 from Debian unstable

[Alexandre Ghiti]

** Attachment added: "debdiff_debian_ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+attachment/5563510/+files/debdiff_debian_ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957100

Title:
  Merge lintian 2.114.0 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960088] Re: a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN

[Alexandre Ghiti]

I went ahead and gave master a try here [1] and that locally fixes the 
segfault. I think taking master is ok, there's not much activity in this repo 
which I interpret as master is stable enough.
I versioned this package as 3.6.0 but I'm not sure here.

Thanks xnox,

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13277687/+listing-
archive-extra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960088

Title:
  a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1960088/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961789] [NEW] "ponteiro e tela travaram, não consegui ter acesso a nada do notebook" nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Alexandre Pereira de Souza]

Public bug reported:

Estava acessando o meu endereço de e-mail e havia deixado o visual
studio code e libreOffice Writer em aberto. Quando tentei abrir um
e-mail, travou o ponteiro do mouse e a tela travou juntamente. Não
consegui ter acesso a anda do notebook, não consegui nem desligar ele.
Ficou ligado a noite toda, pela manhã eu vi que ele tinha descarregado e
coloquei na carga e consegui ligar ele, e aparentemente voltou ao
normal.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
Uname: Linux 5.10.0-1057-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.14.0-1024-oem
Date: Tue Feb 22 09:47:57 2022
Dependencies:
 
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
DuplicateSignature: 
dkms:nvidia-kernel-source-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-mm.h:149:45:
 error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2022-02-03 (19 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
PackageVersion: 440.100-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.2
SourcePackage: nvidia-graphics-drivers-440
Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-440 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961789

Title:
  "ponteiro e tela travaram, não consegui ter acesso a nada do notebook"
  nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1961789/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957100] Re: Merge lintian 2.114.0 from Debian unstable

[Alexandre Ghiti]

Attached the updated debdiff against 2.111-0ubuntu3.


** Patch added: "debdiff_oldubuntu_newubuntu.patch"
   
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+attachment/5562436/+files/debdiff_oldubuntu_newubuntu.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957100

Title:
  Merge lintian 2.114.0 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957100] Re: Merge lintian 2.114.0 from Debian unstable

[Alexandre Ghiti]

Attached the updated debdiff against debian version 2.114 with [1] and I
replaced "LP #" into "LP: #" in changelog.

https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1959004

** Patch added: "debdiff_debian_ubuntu.patch"
   
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+attachment/5562434/+files/debdiff_debian_ubuntu.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957100

Title:
  Merge lintian 2.114.0 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957100] Re: Merge lintian 2.114.0 from Debian unstable

[Alexandre Ghiti]

Lintian 2.114 introduces lots of new dependencies which require MIR:

* libdata-validate-uri-perl
  + libdata-validate-ip-perl
 - libnet-ipv6addr-perl
   * libmath-bigint-perl
  + libscalar-list-utils-perl
 - libnet-netmask-perl
* libsyntax-keyword-try-perl
  + libxs-parse-keyword-perl
* libencode-perl
* libhtml-tokeparser-simple-perl
* libwww-mechanize-perl
  + libhttp-server-simple-perl
* plzip

It is not possible to avoid perl5.34-related new dependencies as
perl5.34 landed in Jammy. Other dependencies are not straightforward to
eliminate either.

It's been discussed in the foundations team and it was decided to merge
this version and do the MIR (if needed) after the sprint next week.

FWIW, I have given Simon's patches a new try in my PPA at [1], and it
successfully built.

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/distro/+sourcepub/13273498/+listing-
archive-extra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957100

Title:
  Merge lintian 2.114.0 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1957100/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961425] Re: 22.04: FTBFS due to test failure

[Alexandre Erwin Ittner]

I was looking into this for a few days and failure:

[ TEST ] kj/string-test.c++:31: legacy test: String/Str
kj/string-test.c++:38: failed: expected ("-128 -32768 -2147483648 
-9223372036854775808") == (str((signed char)-128, ' ', (signed short)-32768, ' 
', ((int)-2147483647) - 1, ' ', ((long long)-9223372036854775807ll) - 1)); -128 
-32768 -2147483648 -9223372036854775808; str((signed char)-128, ' ', (signed 
short)-32768, ' ', ((int)-2147483647) - 1, ' ', ((long 
long)-9223372036854775807ll) - 1) = -128 -32768 -214748364( -9223372036854775808
stack: c27f3c60b7b c27f38280d7 764d217568b3 764d216c058f 764d217549e3 
764d2175661f 764d216ef643 764d21701a83 764d216c058f 764d216f568b 764d2175314f 
764d211017a3 764d21101987
[ FAIL ] kj/string-test.c++:31: legacy test: String/Str (85 μs)

... is caused by the code depending on undefined behavior, which happens
to pass on x64 and arm64 but fails on ppc64el. Reducing optimization
level works but I won't count on it to be stable. But since the problem
is already fixed in 0.9.0 (currently on experimental), we can get the
fix when that version is merged.


There are also a different FTBFS caused by a few test cases that fail
when the unit tests are ran from a ZFS volume. I only hit it after
building on a container backed by ZFS storage, btw. It's caused by a
capnproto component using its own wrapper for system call renameat2()
without implementing the fallback for it on unsupported filesystems (as
renameat2 requires collaboration from the FS layer). It is also fixed in
version 0.9.0.


If 0.9.0 does not arrive in time for the merge freeze, I tentatively
backported these two fixes to 0.8.0. A test branch in
https://code.launchpad.net/~aittner/ubuntu/+source/capnproto/+git/capnproto/+ref/backport-
upstream-fixes

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961425

Title:
  22.04: FTBFS due to test failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1961425/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961097] Re: autopackage tests fail against Python 3.10

[Alexandre Ghiti]

The relevant stuff being here
https://github.com/DataBiosphere/toil/pull/3967.

I pinged doko so that he can remove the package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961097

Title:
  autopackage tests fail against Python 3.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/toil/+bug/1961097/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960088] Re: a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN

[Alexandre Ghiti]

I have just asked for help here
https://github.com/grisha/mod_python/issues/113

** Bug watch added: github.com/grisha/mod_python/issues #113
   https://github.com/grisha/mod_python/issues/113

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960088

Title:
  a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1960088/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

[Alexandre Ghiti]

I'm not sure I understand: do I need to enable the sysconfig patch for
python3.10 in addition to your fix?

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960608

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1960608/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

[Alexandre Ghiti]

I talked with doko about that, and he told me to give it a try. The
patch does not apply directly, I had to rebase it: it seems to fix this
issue (i.e.: I can install a package to the right location with my new
python 3.10 package here [1]) but then when installed, it fails to build
python-pip package with the following error:

make[1]: Leaving directory '/tmp/autopkgtest.hzRvXB/build.kr1/real-tree'
   dh_installsystemduser -O--buildsystem=pybuild
   dh_lintian -O--buildsystem=pybuild
   dh_perl -O--buildsystem=pybuild
   dh_usrlocal -O--buildsystem=pybuild
dh_usrlocal: error: debian/python3-pip/usr/local/bin/pip is not a directory
make: *** [debian/rules:8: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
blame: python-pip-22.0.2+dfsg/
badpkg: rules build failed with exit code 2


I attach my rebase that may be wrong if you can take a look.

(I'll send the same info by mail as requested by doko.)

[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13261732/+listing-
archive-extra

** Patch added: "NEW-sysconfig-debian-schemes.diff"
   
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1960608/+attachment/5560804/+files/NEW-sysconfig-debian-schemes.diff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960608

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1960608/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

+1 maintenance report

[Alexandre Ghiti]

Hi,

I was on +1 maintenance last week and I focused on python3-defaults regressions:

libapache2-mod-python
---

This package must be adapted to support python 3.10, patches can be
found here 
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1960088
However, as I explained in the above bug report (and was already
mentioned by the author), a segfault is triggered when we use the
buffer returned by PyArg_ParseTuple.

pytest


Upstream patches were necessary to support 3.10 which allowed
re-enable tests that were removed (thanks to Graham)
Graham uploaded this new version and that fixed autopkgtests.

pytest-mpi
--

No problem with this package, simply a python deprecation warning that
is output to stderr which makes autopkgtest fail: I fixed this warning
in the tox package by simply replacing distutils.sysconfig with
sysconfig.
Graham uploaded this new version and that fixed autopkgtests.

pytest-skip-markers
--

Autopkgtests fails because of pyfakefs usage of _from_parts which
prototype is different in python 3.10: I struggled to cherry-pick
upstream patches to fix in pyfakefs package so I bumped it to version
4.5.4 and that was merged in debian by Graham.
This package synced to Ubuntu and that fixed autopkgtests.

python-dugong


One test timeout on ppc64el: I was able to reproduce the problem
locally in a VM but not to fix it.

python-ml-collection
---

Simple fix to support python 3.10 which consisted in changing
'collections' to 'collections.abc'.
Graham uploaded this new version and that fixed autopkgtests.

python-pip
--

Against python 3.10, python-pip installs packages in the wrong
directory: it is installed
/usr/lib/python3.10/site-packages/world-4.1.1.dist-info whereas it is
expected to be in /usr/local/lib/python3.10/dist-packages/. A bug
report can be found here:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1960608
@stefanor advised to enable a patch that was currently disabled in
python 3.10:  I rebased it and it's currently building in my PPA. I'll
keep @doko and @stefanor posted if that fixes the problem.

q2-demux
--

Simply a retrigger on the new version from debian, thanks Graham.

q2-cli
---

This package is not compatible with python-click >= 8 and was asked
for removal by Graham (it was already removed in debian):
https://bugs.launchpad.net/ubuntu/+source/q2cli/+bug/1960593

shasta
-

New version 0.8.0-1 fails because the autopkgtest VM is too 'small': I
added it to the list of big_packages, it was merged by Brian Murray
and we should retrigger its build soon. But that may not pass since in
Debian, peak memory usage showed > 9GB.
https://ci.debian.net/data/autopkgtest/testing/amd64/s/shasta/19119761/log.gz

toil


upstream toil does not seem to support python 3.10 yet:
https://github.com/DataBiosphere/toil/pull/3967

typer
---

It fails autopkgtest because of DeprecationWarning on stderr from
pytest-sugar: I fixed those warnings in pytest-sugar.
Graham uploaded this new version and that fixed autopkgtests.

unicycler


It fails autopkgtest because of DeprecationWarning on stderr from
spades: I fixed spades but I'm waiting for upstream feedback to make
sure the fix is ok https://github.com/ablab/spades/pull/914

Thanks,

Alex

-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

[Bug 1960088] Re: a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN

[Alexandre Ghiti]

I worked a bit on this package too, here are my findings:

```
Thread 2 "apache2" hit Breakpoint 2, 0x5624ceb81420 in ap_rwrite ()
(gdb) bt
#0  0x5624ceb81420 in ap_rwrite ()
#1  0x7fe7c99bbe72 in req_write (self=0x7fe7c84df700, args=)
at 
/home/ubuntu/libapache2-mod-python/libapache2-mod-python-3.5.0/src/requestobject.c:1590
#2  0x7fe7c9501bce in ?? () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#3  0x7fe7c948be4e in _PyEval_EvalFrameDefault () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#4  0x7fe7c95d7e1f in ?? () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#5  0x7fe7c948a58e in _PyEval_EvalFrameDefault () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#6  0x7fe7c95d7e1f in ?? () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#7  0x7fe7c948a58e in _PyEval_EvalFrameDefault () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#8  0x7fe7c95d7e1f in ?? () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#9  0x7fe7c948a58e in _PyEval_EvalFrameDefault () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#10 0x7fe7c95d7e1f in ?? () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#11 0x7fe7c94f8f48 in ?? () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#12 0x7fe7c94f9143 in ?? () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#13 0x7fe7c94f9825 in _PyObject_CallMethod_SizeT () from 
target:/lib/x86_64-linux-gnu/libpython3.10.so.1.0
#14 0x7fe7c99c505c in python_handler (req=0x7fe7c93740a0, phase=)
at 
/home/ubuntu/libapache2-mod-python/libapache2-mod-python-3.5.0/src/mod_python.c:1535
#15 0x5624ceb8dc08 in ap_run_handler ()
#16 0x5624ceb8faf6 in ap_invoke_handler ()
#17 0x5624cebb6678 in ap_process_async_request ()
#18 0x5624cebb6d1b in ?? ()
#19 0x5624ceba2d68 in ap_run_process_connection ()
#20 0x7fe7c9a1d795 in ?? () from 
target:/usr/lib/apache2/modules/mod_mpm_event.so
#21 0x7fe7c9a1e13c in ?? () from 
target:/usr/lib/apache2/modules/mod_mpm_event.so
#22 0x7fe7c9c05b43 in start_thread (arg=) at 
./nptl/pthread_create.c:442
#23 0x7fe7c9c97b80 in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb) up
#1  0x7fe7c99bbe72 in req_write (self=0x7fe7c84df700, args=)
at 
/home/ubuntu/libapache2-mod-python/libapache2-mod-python-3.5.0/src/requestobject.c:1590
1590rc = ap_rwrite(buff, len, self->request_rec);
(gdb) p/x buff
$1 = 0x7fe7
(gdb) p/x *buff
Cannot access memory at address 0x7fe7
```

And indeed the segfault happens in a lower frame at this same address:

```
Thread 2 "apache2" received signal SIGSEGV, Segmentation fault.
__memmove_sse2_unaligned_erms () at 
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:416
416 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file 
or directory.
(gdb) display /i $pc
1: x/i $pc
=> 0x7fe7c9c35a60 <__memmove_sse2_unaligned_erms+96>:   mov
-0x8(%rsi,%rdx,1),%rcx
(gdb) p/x $rsi
$2 = 0x7fe7
(gdb) p/x $rdx
$3 = 0xe
```

And I can't find this address in /proc/pid/maps, which is weird because
that would mean PyArg_ParseTuple returns a wrong address.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960088

Title:
  a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1960088/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960616] Re: Please merge python-pyxattr 0.7.2-2 (main) from Debian unstable (main)

[Alexandre Ghiti]

python-pyxattr 0.7.2-2ubuntu1 successfully built into my PPA [1] and
locally passed autopkgtest.

[1] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+packages

** Tags added: fr-2046

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960616

Title:
  Please merge python-pyxattr 0.7.2-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyxattr/+bug/1960616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960616] Re: Please merge python-pyxattr 0.7.2-2 (main) from Debian unstable (main)

[Alexandre Ghiti]

** Changed in: python-pyxattr (Ubuntu)
 Assignee: (unassigned) => Alexandre Ghiti (alexghiti)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960616

Title:
  Please merge python-pyxattr 0.7.2-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyxattr/+bug/1960616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960616] [NEW] Please merge python-pyxattr 0.7.2-2 (main) from Debian unstable (main)

[Alexandre Ghiti]

Public bug reported:

Please merge python-pyxattr 0.7.2-2 (main) from Debian unstable (main)

** Affects: python-pyxattr (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960616

Title:
  Please merge python-pyxattr 0.7.2-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyxattr/+bug/1960616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960608] [NEW] python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest

[Alexandre Ghiti]

Public bug reported:

pip3-root.sh expects world package to be installed in
/usr/local/lib/python3.*/dist-packages whereas it is actually installed
into /usr/lib/python3.10/site-packages/.

It even fails to uninstall the package right after installing it:

ubuntu@autopkgtest:~$ sudo python3 -m pip install world
Collecting world
  Using cached world-4.1.1-py3-none-any.whl
Collecting atpublic
  Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
Installing collected packages: atpublic, world
Successfully installed atpublic-3.0.1 world-4.1.1
WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
WARNING: Skipping world as it is not installed.
WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

** Affects: python-pip (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960608

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1960608/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959377] Re: Fix test on python 3.10

[Alexandre Ghiti]

Find attached an updated version of the patch that contains the URL to
the github PR.

** Patch added: "debdiff_python3.10.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gitsome/+bug/1959377/+attachment/5557976/+files/debdiff_python3.10.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959377

Title:
  Fix test on python 3.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gitsome/+bug/1959377/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959377] Re: Fix test on python 3.10

[Alexandre Ghiti]

** Tags added: fr-2012

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959377

Title:
  Fix test on python 3.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gitsome/+bug/1959377/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959377] [NEW] Fix test on python 3.10

[Alexandre Ghiti]

Public bug reported:

As can be seen in [1], gitsome autopkgtests fail against python 3.10
because it uses 'collections' instead of 'collections.abc', that syntax
being deprecated since python 3.3.

You can find attached a patch that fixes this issue: the package
successfully built in my PPA [2] and the autopkgtests passed locally on
an amd64 VM.

[1] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/g/gitsome/20220126_092330_5ad21@/log.gz
[2] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+packages

** Affects: gitsome (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: fr-2012

** Attachment added: "debdiff_python3.10.patch"
   
https://bugs.launchpad.net/bugs/1959377/+attachment/5557913/+files/debdiff_python3.10.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959377

Title:
  Fix test on python 3.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gitsome/+bug/1959377/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)

[Alexandre Ghiti]

New diff that contains the LP bug number in the changelog.

** Patch added: "debdiff_debian_ubuntu.diff"
   
https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/5557899/+files/debdiff_debian_ubuntu.diff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958502

Title:
  Please merge newt 0.52.21-5 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)

[Alexandre Ghiti]

New diff that contains the LP bug number in changelog.

** Patch added: "debdiff_oldubuntu_ubuntu.diff"
   
https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/5557898/+files/debdiff_oldubuntu_ubuntu.diff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958502

Title:
  Please merge newt 0.52.21-5 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959309] [NEW] Slurmd will always fail with PIDFile set on systemd

[Alexandre Otto Strube]

Public bug reported:

I realized that slurmd always shows as failed on ubuntu with a

"Jan 23 18:03:05 c1-compute-1.wehi.edu.au systemd[1]: Can't open PID
file /var/run/slurm/slurmd.pid (yet?) after start: No such file or
directory"


According to https://bugs.schedmd.com/show_bug.cgi?id=8388#c1 , 

This is happening because we create the PID file slightly after systemd
tries to read it.  Commands where systemd needs to know the PID (eg
systemctl restart slurmd.service) it will re-read the file (which
appears to be getting created properly).  From a functional standpoint,
this error shouldn't have any impact on systemd or slurm.


The solution, is to remove the PIDFile line on slurmd.service:, according  to 
upstream https://bugs.schedmd.com/show_bug.cgi?id=8388#c3 :

The quickest workaround you could use is to just comment out "PIDFile=*"
line in the unit file and do a daemon-reload. instead of reading the pid
file we write out, it will "guess" the main pid (and in my tests does so
correctly).

** Affects: slurm-llnl (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959309

Title:
  Slurmd will always fail with PIDFile set on systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/slurm-llnl/+bug/1959309/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958959] Re: pahole v1.22-2 segfaults when building a Linux kernel

[Alexandre Ghiti]

Hi Gianfranco,

dwarves 1.22-2build1 and libbpf 0.5.0-1 still segfaults for me.
On the other hand, the latest version 1.22-2ubuntu1 fixes the issue.

If you need any more testing, do not hesitate.

Thanks,

Alex

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958959

Title:
  pahole v1.22-2 segfaults when building a Linux kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dwarves/+bug/1958959/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942895] Re: Build fails on riscv64 in qemu user emulation

[Alexandre Ghiti]

This patch was merged upstream in 1.8, and currently 1.8-3 built fine,
so this bug is Fix-Released.

** Changed in: pocl (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942895

Title:
  Build fails on riscv64 in qemu user emulation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pocl/+bug/1942895/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1946202] Re: Proposed: testsuite segfaults on ARM64

[Alexandre Ghiti]

Pocl 1.8-3 depends on llvm-toolchain-11, so this bug is not relevant
anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946202

Title:
  Proposed: testsuite segfaults on ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-9/+bug/1946202/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958897] Re: Please merge acpid 2.0.33-1 (main) from Debian unstable (main)

[Alexandre Ghiti]

** Patch added: "debdiff_oldubuntu_newubuntu.patch"
   
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1958897/+attachment/5557344/+files/debdiff_oldubuntu_newubuntu.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958897

Title:
  Please merge acpid 2.0.33-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1958897/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958897] Re: Please merge acpid 2.0.33-1 (main) from Debian unstable (main)

[Alexandre Ghiti]

This package successfully built in my PPA [1].

[1] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+packages

** Changed in: acpid (Ubuntu)
 Assignee: Alexandre Ghiti (alexghiti) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958897

Title:
  Please merge acpid 2.0.33-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1958897/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958897] Re: Please merge acpid 2.0.33-1 (main) from Debian unstable (main)

[Alexandre Ghiti]

** Patch added: "debdiff_debian_ubuntu.patch"
   
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1958897/+attachment/5557343/+files/debdiff_debian_ubuntu.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958897

Title:
  Please merge acpid 2.0.33-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1958897/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958959] Re: pahole v1.22-2 segfaults when building a Linux kernel

[Alexandre Ghiti]

Below the backtrace from the crash file:

$ gdb /home/alex/work/pahole/build/pahole core.pahole.1357462 
GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
/home/alex/.gdbinit:5: Error in sourced command file:
Undefined item: "riscv:rv64".
Reading symbols from /home/alex/work/pahole/build/pahole...
(No debugging symbols found in /home/alex/work/pahole/build/pahole)
[New LWP 1357462]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `pahole -J --btf_gen_floats .tmp_vmlinux.btf'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:105
105 ../sysdeps/x86_64/multiarch/strcmp-avx2.S: No such file or directory.
(gdb) bt
#0  __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:105
#1  0x55f3ba5401c0 in __structures__add ()
#2  0x55f3ba542601 in pahole_stealer ()
#3  0x7ff72faf0883 in cus.finalize () from 
/home/alex/work/pahole/build/libdwarves.so.1
#4  0x7ff72faf3a17 in dwarf_cus.create_and_process_cu () from 
/home/alex/work/pahole/build/libdwarves.so.1
#5  0x7ff72faf445c in cus.load_module () from 
/home/alex/work/pahole/build/libdwarves.so.1
#6  0x7ff72faf4725 in cus.process_dwflmod () from 
/home/alex/work/pahole/build/libdwarves.so.1
#7  0x7ff72f852b51 in dwfl_getmodules () from 
/lib/x86_64-linux-gnu/libdw.so.1
#8  0x7ff72faefab4 in dwarf.load_file () from 
/home/alex/work/pahole/build/libdwarves.so.1
#9  0x7ff72fae7f2f in cus.load_file () from 
/home/alex/work/pahole/build/libdwarves.so.1
#10 0x7ff72fae81b8 in cus.load_files () from 
/home/alex/work/pahole/build/libdwarves.so.1
#11 0x55f3ba53ed09 in main ()

** Bug watch added: Debian Bug tracker #1004311
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311

** Also affects: dwarves (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958959

Title:
  pahole v1.22-2 segfaults when building a Linux kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dwarves/+bug/1958959/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs