[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

[Kyle Fazzari]

@tjaalton, looks like 6.8 is discovered last by /etc/grub.d/10_linux,
thus ending up at the bottom of the grub menu, under the "advanced"
menu. The first boot option is still using 6.5.0-1027-oem, (i.e. the one
selected with the default /etc/default/grub that uses GRUB_DEFAULT=0).
Looks like folks will still be booting into 6.5 by default unless those
kernels are automatically removed (something I disabled so I could stay
on 1023). That was a bit surprising to me, is that intentional?

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

Title:
  [amdgpu] Graphics driver issue: Display goes black for a second at
  random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR*
  link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

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


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

[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

[Kyle Fazzari]

@anthonywong, does that mean the OEM-6.5 kernel will see a new release,
then? Or is it still dead?

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

Title:
  [amdgpu] Graphics driver issue: Display goes black for a second at
  random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR*
  link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

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


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

[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

[Kyle Fazzari]

Timo, does that also contain the fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069416 ?

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

Title:
  [amdgpu] Graphics driver issue: Display goes black for a second at
  random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR*
  link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

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


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

[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

[Kyle Fazzari]

Hey folks, I'm still locked on 6.5.0-1023-oem, which is working
perfectly. Any ETA for a fix so I can actually receive kernel updates?
Doesn't Canonical have a QA process for certified machines? How did this
break and how has it remained broken for so long?

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

Title:
  [amdgpu] Graphics driver issue: Display goes black for a second at
  random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR*
  link_enc_cfg_validate: Invalid link encoder assignments - 0x1c

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


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

[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random

[Kyle Fazzari]

Daniel, I'm seeing this same issue on the Lenovo Z13 gen2, which is
certified by Canonical to work with 22.04 (and that is indeed what I'm
running):

https://ubuntu.com/certified/202310-32232

I logged a dupe at https://bugs.launchpad.net/ubuntu/+source/linux-
signed-oem-6.5/+bug/2070960 before Mark caught it (thanks Mark). Note
that this does not appear to be happening with 6.5.0-1023-oem, so it
appears that 6.5.0-1024-oem introduced this issue.

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

Title:
  [amdgpu] Graphics driver issue: Display goes black for a second at
  random

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


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

[Bug 2070960] Re: Screen flashes black every few minutes on Lenovo Z13

[Kyle Fazzari]

I just rolled back to 6.5.0-1023-oem and it appears to work just fine.
This appears to have been introduced by 6.5.0-1024-oem.

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

Title:
  Screen flashes black every few minutes on Lenovo Z13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2070960/+subscriptions


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

[Bug 2070960] Re: Screen flashes black every few minutes on Lenovo Z13

[Kyle Fazzari]

Hey Mark, yes this looks like a dupe! Glad to see someone else appears
to be having this issue.

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

Title:
  Screen flashes black every few minutes on Lenovo Z13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2070960/+subscriptions


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

[Bug 2070960] [NEW] Screen flashes black every few minutes on Lenovo Z13

[Kyle Fazzari]

Public bug reported:

Every few minutes (every 30 seconds or so if I'm watching a video on
youtube), the built-in display of my Lenovo z13 flashes black for about
three seconds before coming back. The syslog when this happens looks
like this:

Jun 26 14:02:09 pandora kernel: [476340.039050] [drm:link_enc_cfg_validate 
[amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c
Jun 26 14:02:05 pandora rtkit-daemon[2007]: Supervising 2 threads of 2 
processes of 1 users.
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: Overwriting 
existing binding of keysym 39 with keysym 39 (keycode 12).

This started happening several days ago, but it worked perfectly fine
before that. I generally apply updates when they're available, so I
suspect a recent update has caused this.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-1024-oem 6.5.0-1024.25
ProcVersionSignature: Ubuntu 6.5.0-1024.25-oem 6.5.13
Uname: Linux 6.5.0-1024-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 26 07:07:50 2024
InstallationDate: Installed on 2024-03-26 (92 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-oem-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-oem-6.5 (Ubuntu)
 Importance: Undecided
 Status: New


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

** Description changed:

  Every few minutes (every 30 seconds or so if I'm watching a video on
  youtube), the built-in display of my Lenovo z13 flashes black. The
- syslog entry when this happens looks like this:
+ syslog when this happens looks like this:
  
  Jun 26 14:02:09 pandora kernel: [476340.039050] [drm:link_enc_cfg_validate 
[amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c
  Jun 26 14:02:05 pandora rtkit-daemon[2007]: Supervising 2 threads of 2 
processes of 1 users.
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Jun 26 14:02:10 pandora gnome-shell[3528]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-1024-oem 6.5.0-1024.25
  ProcVersionSignature: Ubuntu 6.5.0-1024.25-oem 6.5.13
  Uname: Linux 6.5.0-1024-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 07:07:50 2024
  InstallationDate: Installed on 2024-03-26 (92 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64

[Bug 1587455] Re: error message is unclear when the right side of files is empty

[Kyle Fazzari]

** Changed in: snapcraft (Ubuntu)
 Assignee: Kyle Fazzari (kyrofa) => (unassigned)

** Changed in: snapcraft (Ubuntu)
   Status: In Progress => New

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

Title:
  error message is unclear when the right side of files is empty

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

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

[Bug 1906277] Re: PCL armhf FTBFS

[Kyle Fazzari]

Phew, thanks Marc.

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

Title:
  PCL armhf FTBFS

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

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

[Bug 1906277] Re: PCL armhf FTBFS

[Kyle Fazzari]

Note that this failed to build on ppc64el:

powerpc64le-linux-gnu-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
recognition/CMakeFiles/pcl_recognition.dir/build.make:281: recipe for target 
'recognition/CMakeFiles/pcl_recognition.dir/src/cg/geometric_consistency.cpp.o' 
failed

That actually looks like it ran out of RAM. This patch should have made
this effectively a no-change rebuild for ppc64el. It looks like it needs
to be built again.

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

Title:
  PCL armhf FTBFS

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

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

[Bug 1906277] Re: PCL armhf FTBFS

[Kyle Fazzari]

Verified: I can actually install pcl-dev on armhf now. I tested it using
https://github.com/kyrofa/pcl-sru-test which is (mostly) taken from
https://pcl.readthedocs.io/en/latest/using_pcl_pcl_config.html#using-
pcl-pcl-config:

$ git clone https://github.com/kyrofa/pcl-sru-test.git
$ cd pcl-sru-test
$ mkdir build
$ cd build
$ cmake .. && make
$ ./pcd_write_test 
Saved 5 data points to test_pcd.pcd.
0.35 -0.151883 -0.106395
-0.397406 -0.473106 0.292602
-0.731898 0.667105 0.441304
-0.734766 0.854581 -0.0361733
-0.4607 -0.277468 -0.916762

Looks good!

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  PCL armhf FTBFS

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

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

[Bug 1596296] Re: CeresConfig.cmake is not installed

[Kyle Fazzari]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  CeresConfig.cmake is not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1596296/+subscriptions

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

[Bug 1906277] Re: PCL armhf FTBFS

[Kyle Fazzari]

Thank you, Marc!

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

Title:
  PCL armhf FTBFS

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

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

[Bug 1906277] Re: PCL armhf FTBFS

[Kyle Fazzari]

Here is a patch for Xenial. It's mostly a backport of the upstream
Debian patch (https://salsa.debian.org/science-
team/pcl/-/commit/f559d014ee8960f84100d6b6cd8e7372de15fbb4), but opts
not to completely remove the dependency on Qt4 to ensure no changes on
other architectures.

** Patch added: "pcl-armhf-fix.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/1906277/+attachment/5439673/+files/pcl-armhf-fix.debdiff

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

Title:
  PCL armhf FTBFS

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

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

[Bug 1906277] Re: PCL armhf FTBFS

[Kyle Fazzari]

** Summary changed:

- PCL is not available on armhf
+ PCL armhf FTBFS

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

Title:
  PCL armhf FTBFS

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

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

[Bug 1906277] [NEW] PCL is not available on armhf

[Kyle Fazzari]

Public bug reported:

[Impact]

 * PCL fails to build on armhf in Xenial due to https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=835292

 * The patch fixes this issue by backporting the fix from Debian:
https://salsa.debian.org/science-
team/pcl/-/commit/f559d014ee8960f84100d6b6cd8e7372de15fbb4 (with a
slight tweak to keep things safer)

[Test Case]

 * Build PCL on armhf, note that it fails to build with opengl-related
errors (see this build log as an example:
https://launchpadlibrarian.net/508382337/buildlog_ubuntu-xenial-
armhf.pcl_1.7.2-14build1.1_BUILDING.txt.gz)

 * Apply this patch and build PCL again, note that it succeeds because
Qt (the package that is including gles on armhf only) is not installed

[Where problems could occur]

 * This is fixing a failure to build on armhf: no one can possibly be
currently using it, and the fix is armhf-specific. Regression potential
is low unless a typo is made in the patch.

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

** Affects: pcl (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Kyle Fazzari (kyrofa)
 Status: In Progress

** Affects: pcl (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Also affects: pcl (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: pcl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pcl (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: pcl (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: pcl (Ubuntu Xenial)
 Assignee: (unassigned) => Kyle Fazzari (kyrofa)

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

Title:
  PCL is not available on armhf

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

Note that armhf is not building. It already wasn't in the Xenial archive
actually due to this bug, but now that this bug is fixed it still isn't
building due to this Debian bug: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=798408 . I'll SRU a fix for that separately.

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

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

Tested this using both the basic test case above using
https://github.com/kyrofa/pcl-sru-test as well as the much-more-involved
https://github.com/ros-perception/perception_pcl .

Using version 6.2.0+dfsg1-10build1 of libvtk6-dev and version
1.7.2-14build1 of libpcl-dev, both the basic test case as well as
perception_pcl fail attempting to link to the system libproj. The error
from the latter looks like:

$ make[2]: *** No rule to make target '/usr/lib/x86_64-linux-
gnu/libproj.so', needed by
'/home/ubuntu/ws/devel_isolated/pcl_ros/lib/libpcl_ros_surface.so'.
Stop.

When I install version 6.2.0+dfsg1-10ubuntu0.1 of libvtk6-dev and
version 1.7.2-14build1.1 of libpcl-dev from xenial-proposed, libvtk6-dev
also installs libproj-dev and both projects successfully link and build.
Marking verification done.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
  missing dependency) and one for pcl (a no-change rebuild using the
  earlier patch for vtk6). As a result, they cannot be uploaded into
  -proposed at the same time. vtk6 must happen first, and pcl only once
  vtk6 has been built.
  
  [Test Case]
  
   * apt install libvtk6-dev libpcl-dev
-  * git clone https://github.com/kyrofa/pcl-sru-test.git
-  * cd pcl-sru-test
-  * cmake .
-  * make
+  * git clone https://github.com/kyrofa/pcl-sru-test.git
+  * cd pcl-sru-test
+  * cmake .
+  * make
  
  * You'll first note that it fails to build because it needs libproj-dev
  installed. Apply the first patch (to vtk) in this SRU, rebuild and
  install that version of vtk.
  
  * Build again, and you'll note that it fails to link to vtkproj4. This
- is libproj that was vendored by vtk, but should not be used at all in
- Xenial (it's actually building against the system libproj). This is
+ is the libproj that was vendored by vtk, but should not be used at all
+ in Xenial (it's actually building against the system libproj). This is
  fixed by the second patch (to pcl) in this SRU, a no-change rebuild that
  causes the cmake config to be regenerated to properly link to the system
  libproj instead of the vtk-vendored libproj. Rebuild and install that
  version of pcl.
  
   * Finally, the build should succeed.
  
  [Where problems could occur]
  
   * This patch doesn't change ABI or API, but does add a dependency
  
   * Problems could potentially occur if clients worked around this issue
  by hacking their projects to link to vtkproj, but known users (ROS) have
  vendored Debian's fix into their repos as opposed to working around the
  bug, thus regressions seem unlikely

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
  missing dependency) and one for pcl (a no-change rebuild using the
  earlier patch for vtk6). As a result, they cannot be uploaded into
  -proposed at the same time. vtk6 must happen first, and pcl only once
  vtk6 has been built.
  
  [Test Case]
  
-  * Build software that uses PCL (e.g. https://github.com/ros-
- perception/perception_pcl) and watch it fail
+  * Install vtk6-dev and libpcl-dev from Xenial
  
-  * Apply this patch, build and install vtk6-dev, then rebuild PCL using
- it. Then watch your previous build failure succeed.
+  * Use them to build this project: https://github.com/kyrofa/pcl-sru-
+ test (borrowed from the bug referenced above) .
+ 
+ * You'll first note that it fails to build because it needs libproj-dev
+ installed. Apply the first patch (to vtk) in this SRU, rebuild and
+ install that version of vtk.
+ 
+ * Build again, and you'll note that it fails to link to vtkproj4. This
+ is libproj that was vendored by vtk, but should not be used at all in
+ Xenial (it's actually building against the system libproj). This is
+ fixed by the second patch (to pcl) in this SRU, a no-change rebuild that
+ causes the cmake config to be regenerated to properly link to the system
+ libproj instead of the vtk-vendored libproj. Rebuild and install that
+ version of pcl.
+ 
+  * Finally, the build should succeed.
  
  [Where problems could occur]
  
   * This patch doesn't change ABI or API, but does add a dependency
  
   * Problems could potentially occur if clients worked around this issue
  by hacking their projects to link to vtkproj, but known users (ROS) have
  vendored Debian's fix into their repos as opposed to working around the
  bug, thus regressions seem unlikely

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

Thank you, Marc!

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
-  * This has been fixed in Debian
+  * This has been fixed in Debian, but in a way that breaks ABI
  
-  * The attached debdiff is based on the upstream Debian fix
- (https://salsa.debian.org/science-
- team/vtk6/-/commit/7fd27ac6bf33c05b1ec11a8ee2a17ecb525978b0)
+  * See this change through all the way by adding libproj-dev as a
+ dependency to libvtk6-dev, and rebuild pcl such that it uses the system
+ libproj instead of the vtk-vendored libproj
+ 
+  * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
+ build dependency) and one for pcl (a no-change rebuild using the earlier
+ patch for vtk6). As a result, they cannot be uploaded into -proposed as
+ the same time. vtk6 must happen first, and pcl only once vtk6 has been
+ built.
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
-  * Apply this patch, and watch it succeed
+  * Apply this patch, build and install vtk6-dev, then rebuild PCL using
+ it. Then watch your previous build failure succeed.
  
  [Where problems could occur]
  
-  * This patch seems tiny, but given that part of it is disabling a patch
- that is currently applied in Xenial (102_enable_system_proj4_lib.patch)
- it is larger than it first appears
+  * This patch doesn't change ABI or API
  
-  * This could use a double check from a more experienced eye, I'm
- concerned this may break ABI
+  * Problems could potentially occur if clients worked around this issue
+ by hacking their projects to link to vtkproj, but known users (ROS) have
+ vendored Debian's fix into their repos as opposed to working around the
+ bug, thus regressions seem unlikely

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
-  * See this change through all the way by adding libproj-dev as a
+  * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
-  * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
- build dependency) and one for pcl (a no-change rebuild using the earlier
- patch for vtk6). As a result, they cannot be uploaded into -proposed as
- the same time. vtk6 must happen first, and pcl only once vtk6 has been
+  * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
+ dependency) and one for pcl (a no-change rebuild using the earlier patch
+ for vtk6). As a result, they cannot be uploaded into -proposed as the
+ same time. vtk6 must happen first, and pcl only once vtk6 has been
  built.
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
   * Apply this patch, build and install vtk6-dev, then rebuild PCL using
  it. Then watch your previous build failure succeed.
  
  [Where problems could occur]
  
   * This patch doesn't change ABI or API
  
-  * Problems could potentially occur if clients worked around this issue
+  * Problems could potentially occur if clients worked around this issue
  by hacking their projects to link to vtkproj, but known users (ROS) have
  vendored Debian's fix into their repos as opposed to working around the
  bug, thus regressions seem unlikely

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
- dependency) and one for pcl (a no-change rebuild using the earlier patch
- for vtk6). As a result, they cannot be uploaded into -proposed as the
- same time. vtk6 must happen first, and pcl only once vtk6 has been
- built.
+ missing dependency) and one for pcl (a no-change rebuild using the
+ earlier patch for vtk6). As a result, they cannot be uploaded into
+ -proposed as the same time. vtk6 must happen first, and pcl only once
+ vtk6 has been built.
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
   * Apply this patch, build and install vtk6-dev, 

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

Here's a better, less risky patch for vtk6. It requires a no-change
rebuild of pcl though in order to properly work.

** Patch removed: "libproj-fix.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/vtk6/+bug/1573234/+attachment/5432746/+files/libproj-fix.debdiff

** Patch added: "add-build-dep.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/vtk6/+bug/1573234/+attachment/5435348/+files/add-build-dep.debdiff

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

** Changed in: pcl (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: pcl (Ubuntu Xenial)
     Assignee: (unassigned) => Kyle Fazzari (kyrofa)

** Changed in: pcl (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

Here's the patch required for pcl (no-change rebuild). It must happen
only after vtk6 has been built with the above patch.

** Patch added: "pcl-rebuild.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/1573234/+attachment/5435349/+files/pcl-rebuild.debdiff

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1596296] Re: CeresConfig.cmake is not installed

[Kyle Fazzari]

** Also affects: ceres-solver (Ubuntu Xenial)
   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/1596296

Title:
  CeresConfig.cmake is not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1596296/+subscriptions

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

[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers

[Kyle Fazzari]

Note that upgrades to a given release uses the upgrader from that
release. As a result, there's no need to SRU this to Xenial, since
Xenial-to-Bionic upgrades will use the one from Bionic.

** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

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

Title:
  Can't upgrade from a release if ros packages are  installed from ROS
  servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian
  
   * The attached debdiff is based on the upstream Debian fix
  (https://salsa.debian.org/science-
  team/vtk6/-/commit/7fd27ac6bf33c05b1ec11a8ee2a17ecb525978b0)
  
  [Test Case]
  
   * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
   * Apply this patch, and watch it succeed
  
  [Where problems could occur]
  
   * This patch seems tiny, but given that part of it is disabling a patch
  that is currently applied in Xenial (102_enable_system_proj4_lib.patch)
  it is larger than it first appears
  
-  * I believe the change introduced is backward compatible, but it could
- use a double check from a more experienced eye
+  * This could use a double check from a more experienced eye, I'm
+ concerned this may break ABI

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

  [Impact]
  
-  * Any code that links to libraries provided by libpcl1.7 (which depends
+  * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
-  * This has been fixed in Debian
+  * This has been fixed in Debian
  
-  * The attached debdiff is simply an SRU of the upstream Debian fix
+  * The attached debdiff is based on the upstream Debian fix
+ (https://salsa.debian.org/science-
+ team/vtk6/-/commit/7fd27ac6bf33c05b1ec11a8ee2a17ecb525978b0)
  
  [Test Case]
  
-  * Build software that uses PCL (e.g. https://github.com/ros-
+  * Build software that uses PCL (e.g. https://github.com/ros-
  perception/perception_pcl) and watch it fail
  
-  * Apply this patch, and watch it succeed
+  * Apply this patch, and watch it succeed
  
  [Where problems could occur]
  
-  * This patch seems tiny, but given that part of it is disabling a patch that 
is currently applied in Xenial (102_enable_system_proj4_lib.patch) it is larger 
than it first appears
-  
-  * I believe the change introduced is backward compatible, but it could use a 
double check from a more experienced eye
+  * This patch seems tiny, but given that part of it is disabling a patch
+ that is currently applied in Xenial (102_enable_system_proj4_lib.patch)
+ it is larger than it first appears
+ 
+  * I believe the change introduced is backward compatible, but it could
+ use a double check from a more experienced eye

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

- This issue has been reported and fixed in Debian:
+ [Impact]
  
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819741
+  * Any code that links to libraries provided by libpcl1.7 (which depends
+ on vtk6) fails to link because it cannot find vtkproj4 (see
+ https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
- Currently any code that links to libraries provided by libpcl1.7 (which
- depends on vtk6) fails to link because it cannot find vtkproj4.
+  * This has been fixed in Debian
  
- An example of affected downstream code is available here:
- https://github.com/PointCloudLibrary/pcl/issues/1594
+  * The attached debdiff is simply an SRU of the upstream Debian fix
  
- Please sync with vtk6 version 6.2.0+dfsg1-11 so that downstream code can
- link to libraries provided by vtk6.
+ [Test Case]
+ 
+  * Build software that uses PCL (e.g. https://github.com/ros-
+ perception/perception_pcl) and watch it fail
+ 
+  * Apply this patch, and watch it succeed
+ 
+ [Where problems could occur]
+ 
+  * This patch seems tiny, but given that part of it is disabling a patch that 
is currently applied in Xenial (102_enable_system_proj4_lib.patch) it is larger 
than it first appears
+  
+  * I believe the change introduced is backward compatible, but it could use a 
double check from a more experienced eye

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

Here's a patch that fixes this issue in Xenial

** Patch added: "libproj-fix.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/vtk6/+bug/1573234/+attachment/5432746/+files/libproj-fix.debdiff

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Changed in: vtk6 (Ubuntu Xenial)
 Assignee: (unassigned) => Kyle Fazzari (kyrofa)

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Also affects: vtk6 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: vtk6 (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  unable to link: cannot find libvtkproj4

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

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

[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers

[Kyle Fazzari]

Here's the patch for Bionic.

** Patch added: "debdiff containing bionic patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+attachment/5427593/+files/18.04.41.debdiff

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

Title:
  Can't upgrade from a release if ros packages are  installed from ROS
  servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions

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

[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers

[Kyle Fazzari]

** Description changed:

- This message was appear when upgrade
+ [Impact]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
- Package: ubuntu-release-upgrader-core 1:0.220.8
- ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
- Uname: Linux 3.19.0-66-generic x86_64
- NonfreeKernelModules: nvidia
- ApportVersion: 2.14.1-0ubuntu3.21
- Architecture: amd64
- CrashDB: ubuntu
- CurrentDesktop: Unity
- Date: Wed Aug 10 18:41:24 2016
- InstallationDate: Installed on 2015-09-08 (336 days ago)
- InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
- PackageArchitecture: all
- SourcePackage: ubuntu-release-upgrader
- UpgradeStatus: Upgraded to trusty on 2016-08-10 (0 days ago)
+  * ROS releases are strict about the Ubuntu releases they support. These
+ days a given ROS release only supports one Ubuntu LTS.
+ 
+  * Attempting to upgrade Ubuntu beyond that supported release at best
+ results in an unsupported situation, and at worst is known to break the
+ upgrade process as it's possible to get apt into an unrecoverable
+ situation.
+ 
+  * The fix for this issue is to detect if ROS is installed and make sure
+ the user is aware that this may not succeed.
+ 
+ [Test Case]
+ 
+  * The dependency problems that lead to apt breakage is very deep and
+ hard to duplicate, but to paint with a broad brush: if a ROS package is
+ installed, extreme caution should be exercised when upgrading as it's
+ very likely that it's not supported.
+ 
+  * To install ROS, follow the proper tutorial for your Ubuntu version, and 
install the "ros-base" metapackage:
+- Xenial: https://wiki.ros.org/kinetic/Installation/Ubuntu
+- Bionic: https://wiki.ros.org/melodic/Installation/Ubuntu
+- Focal: https://wiki.ros.org/noetic/Installation/Ubuntu
+ 
+  * Now use ubuntu-release-upgrader to upgrade to the next Ubuntu
+ release. Such a thing should not happen without prompting the user that
+ ROS is installed and that this may lead to problems.
+ 
+ [Regression Potential]
+ 
+  * Detecting that ROS is installed is done with a package name
+ heuristic, which isn't perfect. We look for a set of base ROS
+ dependencies using a pattern that is unlikely to clash with a non-ROS-
+ related package, but it's possible for this to result in a false
+ positive. Worst case, the user will be warned that ROS is installed when
+ in fact it isn't, but they'll still be able to continue the upgrade.

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

Title:
  Can't upgrade from a release if ros packages are  installed from ROS
  servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions

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

[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers

[Kyle Fazzari]

** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-release-upgrader (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Kyle Fazzari (kyrofa)
   Status: In Progress

** Also affects: ubuntu-release-upgrader (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

Title:
  Can't upgrade from a release if ros packages are  installed from ROS
  servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions

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

[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers

[Kyle Fazzari]

Proposed a (hopefully) helpful warning here:
https://code.launchpad.net/~kyrofa/ubuntu-release-upgrader/+git/ubuntu-
release-upgrader/+merge/388145

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => 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/1611737

Title:
  Can't upgrade from a release if ros packages are  installed from ROS
  servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions

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

[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers

[Kyle Fazzari]

** Changed in: ubuntu-release-upgrader (Ubuntu)
 Assignee: (unassigned) => Kyle Fazzari (kyrofa)

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

Title:
  Can't upgrade from a release if ros packages are  installed from ROS
  servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

Tested using upstream ceres-solver's helloworld.cc example[1].

Unable to test for regressions on arm64 because the package wasn't
available there before -proposed:

$ sudo apt install libceres-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package libceres-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libceres-dev' has no installation candidate


Alright, testing 1.14.0-4ubuntu1.1 from -proposed:

$ g++ helloworld.cc -lceres -I /usr/include/eigen3 -lglog
ubuntu@arm64-test:~/ceres-solver/examples$ ./a.out 
iter  cost  cost_change  |gradient|   |step|tr_ratio  tr_radius  
ls_iter  iter_time  total_time
   0  4.512500e+010.00e+009.50e+00   0.00e+00   0.00e+00  1.00e+04  
  01.32e-045.72e-04
   1  4.511598e-074.51e+019.50e-04   9.50e+00   1.00e+00  3.00e+04  
  12.02e-049.69e-04
   2  5.012552e-164.51e-073.17e-08   9.50e-04   1.00e+00  9.00e+04  
  15.43e-051.12e-03
Ceres Solver Report: Iterations: 3, Initial cost: 4.512500e+01, Final cost: 
5.012552e-16, Termination: CONVERGENCE
x : 0.5 -> 10


Looks great there. Moving on to regression testing on amd64, with version 
1.14.0-4ubuntu1:

$ g++ helloworld.cc -lceres -I /usr/include/eigen3 -lglog
$ ./a.out 
iter  cost  cost_change  |gradient|   |step|tr_ratio  tr_radius  
ls_iter  iter_time  total_time
   0  4.512500e+010.00e+009.50e+00   0.00e+00   0.00e+00  1.00e+04  
  07.41e-057.69e-04
   1  4.511598e-074.51e+019.50e-04   9.50e+00   1.00e+00  3.00e+04  
  11.34e-041.03e-03
   2  5.012552e-164.51e-073.17e-08   9.50e-04   1.00e+00  9.00e+04  
  19.05e-061.04e-03
Ceres Solver Report: Iterations: 3, Initial cost: 4.512500e+01, Final cost: 
5.012552e-16, Termination: CONVERGENCE
x : 0.5 -> 10


Now amd64, with version 1.14.0-4ubuntu1.1 from -proposed:

$ g++ helloworld.cc -lceres -I /usr/include/eigen3 -lglog
$ ./a.out 
iter  cost  cost_change  |gradient|   |step|tr_ratio  tr_radius  
ls_iter  iter_time  total_time
   0  4.512500e+010.00e+009.50e+00   0.00e+00   0.00e+00  1.00e+04  
  05.90e-054.02e-04
   1  4.511598e-074.51e+019.50e-04   9.50e+00   1.00e+00  3.00e+04  
  11.72e-046.28e-04
   2  5.012552e-164.51e-073.17e-08   9.50e-04   1.00e+00  9.00e+04  
  12.24e-056.74e-04
Ceres Solver Report: Iterations: 3, Initial cost: 4.512500e+01, Final cost: 
5.012552e-16, Termination: CONVERGENCE
x : 0.5 -> 10

Time is of course a smidge different, but results are the same, across
architectures and package versions. This looks good to me, thanks Brian!

[1]: https://github.com/ceres-solver/ceres-
solver/blob/master/examples/helloworld.cc

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

Thank you, Marc!

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

** Attachment removed: "New debdiff with proper patch tags"
   
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5383012/+files/debdiff_with_tagged_patch

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

Sorry, last debdiff got garbled.

** Attachment added: "Real patch"
   
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5383038/+files/debdiff

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

** Attachment added: "New debdiff with proper patch tags"
   
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5383012/+files/debdiff_with_tagged_patch

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

Attached is the debdiff of the patch for this issue.

** Patch added: "debdiff of patch"
   
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5382703/+files/reduce-minimizer-iterations.debdiff

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

** Description changed:

+ [Impact]
+ 
+ * ceres-solver's binary packages are not available on arm64 in Ubuntu
+ Focal
+ 
+ * tests seem to be failing on arm64:
  https://launchpad.net/ubuntu/+source/ceres-
  solver/1.14.0-4ubuntu1/+build/19091179
  
- Trying to install libceres-dev after upgrading system from Bionic to
- Focal, but the arm64 build is failing
+ * libceres is critical for robotics SLAM applications on Ubuntu, and
+ arm64 is a very popular architecture for robotics
  
- I have also reported here https://github.com/ceres-solver/ceres-
- solver/issues/599 - but not sure which is more appropriate (I don't know
- if that GitHub project maintains the debian packaging builds)
+ [Test Case]
  
- It appears to be a single test failure that blocks the build
+ * Simply run the existing test cases on arm64 and you'll see
+ evaluation_callback_test fail just like in the above log
  
- ```
- 99% tests passed, 1 tests failed out of 127
+ [Regression Potential]
  
- Total Test time (real) = 267.25 sec
+ * libceres isn't on arm64 at all, so the regression potential there is
+ nil
  
- The following tests FAILED:
-30 - evaluation_callback_test (Failed)
- ```
+ * This is a test-only change, thus the only regression possible on other
+ architectures is that the tests don't pass and the package doesn't build
+ as a result

** Description changed:

  [Impact]
  
  * ceres-solver's binary packages are not available on arm64 in Ubuntu
  Focal
  
  * tests seem to be failing on arm64:
  https://launchpad.net/ubuntu/+source/ceres-
  solver/1.14.0-4ubuntu1/+build/19091179
  
  * libceres is critical for robotics SLAM applications on Ubuntu, and
  arm64 is a very popular architecture for robotics
  
  [Test Case]
  
  * Simply run the existing test cases on arm64 and you'll see
  evaluation_callback_test fail just like in the above log
  
  [Regression Potential]
  
  * libceres isn't on arm64 at all, so the regression potential there is
  nil
  
  * This is a test-only change, thus the only regression possible on other
  architectures is that the tests don't pass and the package doesn't build
- as a result
+ as a result (although note that tests pass locally just fine)

** Description changed:

  [Impact]
  
  * ceres-solver's binary packages are not available on arm64 in Ubuntu
  Focal
  
  * tests seem to be failing on arm64:
  https://launchpad.net/ubuntu/+source/ceres-
  solver/1.14.0-4ubuntu1/+build/19091179
  
  * libceres is critical for robotics SLAM applications on Ubuntu, and
  arm64 is a very popular architecture for robotics
  
  [Test Case]
  
  * Simply run the existing test cases on arm64 and you'll see
  evaluation_callback_test fail just like in the above log
  
  [Regression Potential]
  
  * libceres isn't on arm64 at all, so the regression potential there is
  nil
  
  * This is a test-only change, thus the only regression possible on other
  architectures is that the tests don't pass and the package doesn't build
- as a result (although note that tests pass locally just fine)
+ as a result (although note that tests pass locally just fine on amd64 at
+ least)

** Description changed:

  [Impact]
  
  * ceres-solver's binary packages are not available on arm64 in Ubuntu
  Focal
  
  * tests seem to be failing on arm64:
  https://launchpad.net/ubuntu/+source/ceres-
  solver/1.14.0-4ubuntu1/+build/19091179
  
  * libceres is critical for robotics SLAM applications on Ubuntu, and
  arm64 is a very popular architecture for robotics
  
  [Test Case]
  
  * Simply run the existing test cases on arm64 and you'll see
  evaluation_callback_test fail just like in the above log
  
  [Regression Potential]
  
  * libceres isn't on arm64 at all, so the regression potential there is
  nil
  
  * This is a test-only change, thus the only regression possible on other
  architectures is that the tests don't pass and the package doesn't build
- as a result (although note that tests pass locally just fine on amd64 at
- least)
+ as a result (although note that tests pass locally just fine on amd64)

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

** Changed in: ceres-solver (Ubuntu Focal)
 Assignee: (unassigned) => Kyle Fazzari (kyrofa)

** Changed in: ceres-solver (Ubuntu Focal)
   Importance: Undecided => High

** Also affects: ceres-solver (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: ceres-solver (Ubuntu Groovy)
   Status: New => 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/1882626

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1882626] Re: libceres-dev Focal arm64 build failing with failed test

[Kyle Fazzari]

Note that libceres1 is present on arm64 in Groovy
(https://packages.ubuntu.com/groovy/libceres1)-- this only effects
Focal.

** Also affects: ceres-solver (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: ceres-solver (Ubuntu Focal)
   Status: New => Confirmed

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

Title:
  libceres-dev Focal arm64 build failing with failed test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+subscriptions

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

[Bug 1877708] Re: i want to update my software

[Kyle Fazzari]

*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737

To clarify: if you want to upgrade to to 18.04, I'm afraid you'll need
to remove ROS Kinetic first.

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

Title:
  i want to update my software

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

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

[Bug 1877708] Re: i want to update my software

[Kyle Fazzari]

*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737

The problem here is that you have ROS Kinetic installed, which only
supports Ubuntu 16.04: it doesn't support the upgrade. We're working on
a nicer error for exactly this situation.

** This bug has been marked a duplicate of bug 1611737
   Can't upgrade from a release if ros packages are  installed from ROS servers

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

Title:
  i want to update my software

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

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

[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers

[Kyle Fazzari]

> This makes some upgrades technically not possible since there could
not be packages in the ROS repositories available for the new
distribution in an upgrade process. For example, there is no a single
ROS Release that support 14.04 and 16.04. I can not see a
safe/straightforward upgrade path.

Jose hit this on the head. This is explicitly not supported by ROS. The
problem is, Ubuntu doesn't really have a way of knowing that. I think
the best solution to this issue is a nice error message from the
upgrader. We can detect that ROS is installed, mention that an upgrade
isn't supported, and suggest removing the ROS distro before proceeding.

That said, I'm not familiar with the upgrader. Is there supported way we
could hook such logic in?

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

Title:
  Can't upgrade from a release if ros packages are  installed from ROS
  servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions

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

[Bug 1817595] Re: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers

[Kyle Fazzari]

Thanks for testing, Simon!

> I was not able to find any fields where I could set "verification-
done-bionic"

Right under the bug description you'll see a set of tags that you can
edit.

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

Title:
  [SRU] urdfdom-headers and urdfdom should not use locale dependent
  parsing for floating point numbers

To manage notifications about this bug go to:
https://bugs.launchpad.net/urdfdom-headers/+bug/1817595/+subscriptions

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

[Bug 1817595] Re: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers

[Kyle Fazzari]

This patch is complex enough to make folks a little uncomfortable with
the SRU. Beyond Julian's suggestions (thanks Julian), Jose, are you
willing to commit to thoroughly testing this and resolving any
autopkgtest regressions?

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

Title:
  [SRU] urdfdom-headers and urdfdom should not use locale dependent
  parsing for floating point numbers

To manage notifications about this bug go to:
https://bugs.launchpad.net/urdfdom-headers/+bug/1817595/+subscriptions

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

Just finished taking this for a spin, both on armhf (to ensure it now
works) and amd64 (to smoke test for no regressions).

Here is an up-to-date amd64 using 1.4~rc1-1build2:

$ cat << EOF >> test.py
> #!/usr/bin/env python3
> 
> import pygraphviz
> 
> graph = pygraphviz.AGraph()
> graph.add_node('foo')
> graph.add_node('bar')
> graph.add_edge('foo', 'bar')
> print('success!')
> EOF
$ chmod a+x test.py
$ ./test.py 
success!


After installing 1.4~rc1-1build2.1 the results are unchanged-- it continues 
working:

$ sudo apt install python3-pygraphviz/bionic-proposed

Setting up python3-pygraphviz (1.4~rc1-1build2.1) ...
$ ./test.py 
success!


Now, here is an up-to-date armhf using 1.4~rc1-1build2:

$ cat << EOF >> test.py
> #!/usr/bin/env python3
> 
> import pygraphviz
> 
> graph = pygraphviz.AGraph()
> graph.add_node('foo')
> graph.add_node('bar')
> graph.add_edge('foo', 'bar')
> print('success!')
> EOF
$ chmod a+x test.py
$ ./test.py 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1561, in 
__new__
nh = gv.agnode(graph.handle, n.encode(graph.encoding), _Action.find)
KeyError: 'agnode: no key'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "./test.py", line 8, in 
graph.add_edge('foo', 'bar')
  File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 478, in 
add_edge
e = Edge(self, eh=eh)
  File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1625, in 
__new__
s = Node(graph, nh=source)
  File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1563, in 
__new__
raise KeyError("Node %s not in graph." % n)
KeyError: 'Node None not in graph.'


Broken, as mentioned in the bug report. Now with 1.4~rc1-1build2.1:

$ sudo apt install python3-pygraphviz/bionic-proposed

Setting up python3-pygraphviz (1.4~rc1-1build2.1) ...
$ ./test.py 
success!

Fixed! Marking verification done.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

I've confirmed that this issue is only present in Bionic.

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

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

** Changed in: python-pygraphviz (Ubuntu Eoan)
   Status: New => 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/1834379

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

** Changed in: python-pygraphviz (Ubuntu Disco)
   Status: New => 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/1834379

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

** Changed in: python-pygraphviz (Ubuntu Cosmic)
   Status: New => 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/1834379

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

** Changed in: python-pygraphviz (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

** Description changed:

  [Impact]
  
  python3-pygraphviz does not work for even simple use cases on armhf
  Bionic. See error output in Test Case section from adding an edge to a
  graph.
  
  This package is currently being used as a dependency of ROS2, which is
  now including armhf as a target platform. The functionality that depends
  on this package fails to run.
  
  Conclusion from below testing is that the current package is somehow
  corrupted.
  
  A no-change rebuild in ppa:emersonknapp/ppa works properly on armhf.
  
  [Test Case]
  
  Using the following test file, and running python3 test.py, the program
  raises an error. However program exits with no output as expected on
  x86_64 and aarch64
  
  ```
  # test.py
  #!/usr/bin/env python3
  
  import pygraphviz
  
  graph = pygraphviz.AGraph()
  graph.add_node('foo')
  graph.add_node('bar')
  graph.add_edge('foo', 'bar')
  ```
  
  Error seen
  
  ```
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1561, in 
__new__
  nh = gv.agnode(graph.handle, n.encode(graph.encoding), _Action.find)
  KeyError: 'agnode: no key'
  
  During handling of the above exception, another exception occurred:
  
  Traceback (most recent call last):
    File "test.py", line 8, in 
  graph.add_edge('foo', 'bar')
    File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 478, in 
add_edge
  e = Edge(self, eh=eh)
    File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1625, in 
__new__
  s = Node(graph, nh=source)
    File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1563, in 
__new__
  raise KeyError("Node %s not in graph." % n)
  KeyError: 'Node None not in graph.'
  ```
  
- 
  [Regression Potential]
  
- This package doesn't currently seem to work at all, so I don't see how
- it could get worse.
+ This is a no-change rebuild, regression potential is very low.
  
  [Other Info]
  
  If I upgrade to 1.5 via pip after installing the apt dependency
  libgraphviz-dev, this same snippet works on all of these platforms.
  
  It also works if I install pygraphviz 1.4rc1 from pip. Also, it seems to
  work with the debian package python3-pygraphviz 1.4 from cosmic. As far
  as I can tell, there are no differences between the cosmic and the
  bionic packages, other than it was rebuilt for Python 3.7.
  
  Here's a summary:
  
  Bionic1.4~rc1 Debian  Broken
  Cosmic1.4~rc1 Debian  Works
  Disco 1.5 Debian  Works
  Bionic1.4~rc1 pip Works
  Bionic1.5 pip Works
  
  And one more data point; if I pull down the debian sources (apt-get
  source python3-pygraphviz ; apt-get build-dep python3-pygraphviz), build
  with no modifications (debuild -uc -us), and then install (dpkg -i
  python3-pygraphviz_1.4~rc1-1build2_armhf.deb), it works just fine.
  
  From all of this, I can only conclude that the Ubuntu Bionic armhf
  debian package is somehow corrupt. Perhaps a rebuild of the package
  would solve the problem.
  
- 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-pygraphviz 1.4~rc1-1build2
  ProcVersionSignature: Ubuntu 4.15.0-1041.43-aws 4.15.18
  Uname: Linux 4.15.0-1041-aws aarch64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: armhf
  Date: Wed Jun 26 22:23:47 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: python-pygraphviz
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case

[Kyle Fazzari]

Can you try getting a no-change rebuild in a PPA?

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

Title:
  armhf Bionic python3-pygraphviz package errors for simple use case

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

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

[Bug 1738164] Re: [snap] U2F doesn't work with yubikey

[Kyle Fazzari]

jdstrand, I've added those rules, and the denials go away, but I'm
afraid it still doesn't work. There doesn't seem to be any denials, but
it's like chrome just doesn't see it.

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

Title:
  [snap] U2F doesn't work with yubikey

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions

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

[Bug 1768855] Re: ufraw-batch in bionic segfault

[Kyle Fazzari]

I'm hitting this in 18.04 as well, trying to use ufraw-batch for my .CR2
thumbnails.

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

Title:
  ufraw-batch in bionic segfault

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

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

[Bug 1663247] Re: Conflicts even if organize is used when both parts are built in the same run

[Kyle Fazzari]

*** This bug is a duplicate of bug 1628098 ***
https://bugs.launchpad.net/bugs/1628098

** This bug has been marked a duplicate of bug 1628098
   organize needs to run after build in stage

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

Title:
  Conflicts even if organize is used when both parts are built in the
  same run

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

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

[Bug 1759700] Re: Add a which-part-provided command or output (behind a flag)

[Kyle Fazzari]

** Package changed: snapcraft (Ubuntu) => snapcraft

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

Title:
  Add a which-part-provided command or output (behind a flag)

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

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

[Bug 1754744] [NEW] Launching any electron app crashes Xorg

[Kyle Fazzari]

Public bug reported:

If I dare to launch any electron-based app (chrome, spotify, atom,
vscode, etc.) there's roughly an 80% chance that it kills X (bringing me
back to the login screen). This doesn't _always_ happen. Note that I
have a 4k laptop, with a 4k external screen. Things seem to have a
better chance of succeeding if I disconnect the external display before
launching the electron app. Once it launches successfully things seem to
be stable, even after re-connecting the external display.

I SSHd into this machine from another, and connected to X from gdb, then
opened vscode to cause the crash. Here is the backtrace I got from that
session (this is easy to reproduce, happy to provide any requested
info):

root@Pandora:~# gdb /usr/bin/Xorg $(pidof Xorg)
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 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"...
"/usr/bin/Xorg": not in executable format: File format not recognized
Attaching to process 2325
[New LWP 2480]
[New LWP 2481]
[New LWP 2482]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f3302ea95d3 in select () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) cont
Continuing.

Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
0x55f7cbb6f650 in ?? ()
(gdb) bt f
#0  0x55f7cbb6f650 in ?? ()
No symbol table info available.
#1  0x55f7ca8ec6dc in ProcVidModeGetModeLine (client=0x55f7cc218ee0) at 
../../Xext/vidmode.c:255
stuff = 
rep = {type = 1 '\001', pad1 = 0 '\000', sequenceNumber = 254, length = 
5, dotclock = 0, hdisplay = 0, hsyncstart = 0, hsyncend = 0, 
  htotal = 0, hskew = 0, vdisplay = 0, vsyncstart = 0, vsyncend = 0, 
vtotal = 0, pad2 = 0, flags = 0, reserved1 = 0, reserved2 = 0, 
  reserved3 = 0, privsize = 0}
pScreen = 
mode = 0x7ffd64d56e20
dotClock = 32765
#2  0x55f7ca77ad9f in Dispatch () at ../../dix/dispatch.c:430
clientReady = 0x55f7cbf9c780
result = 
client = 0x55f7cc218ee0
nready = 0
icheck = 0x55f7cab7b130 
start_tick = 12090
#3  0x55f7ca77ee13 in dix_main (argc=11, argv=0x7ffd64d57018, 
envp=) at ../../dix/main.c:300
i = 
alwaysCheckForInput = {0, 1}
#4  0x7f3302dcc830 in __libc_start_main (main=0x55f7ca769030 , 
argc=11, argv=0x7ffd64d57018, init=, 
fini=, rtld_fini=, stack_end=0x7ffd64d57008) 
at ../csu/libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -792397858051174054, 
94522742050880, 140726295162896, 0, 0, -6839407696988057254, 
-687903866822310}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0xb, 0x55f7ca769030 }, data = {prev = 0x0, 
  cleanup = 0x0, canceltype = 11}}}
not_first_call = 
#5  0x55f7ca769069 in _start ()
No symbol table info available.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Mar  9 12:09:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
InstallationDate: Installed on 2016-08-01 (585 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Dell Precision M3800
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=53750055-6616-428b-88f9-c6c555f8c31d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: Dell Pre

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

With those last few PRs applied:

$ git-ubuntu.self-test 
pylint passed!
= test session starts 
=
platform linux -- Python 3.6.3, pytest-3.1.3, py-1.5.2, pluggy-0.4.0
rootdir: /snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu, inifile:
plugins: cov-2.5.1
collected 165 items 

../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/apt_repo_test.py
 ...
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/build.py 

../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/git_repository.py
 
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/lint.py 
..
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/repo_builder.py
 ..
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/scriptutils_test.py
 ..
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/source_builder_test.py
 
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/test_git_repository.py
 ...
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/test_importer.py
 ...
../../../snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/versioning.py 
..

--- coverage: platform linux, python 3.6.3-final-0 ---
Name
   Stmts   Miss  Cover
--
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/__init__.py   
   0  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/__main__.py   
  86 7612%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/apt_repo.py   
  97  199%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/apt_repo_test.py  
  74  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/build.py  
 45137617%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/buildsource.py
  36 2531%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/cache.py  
   1  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/clone.py  
  75 5625%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/dsc.py
  65 4531%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/exportorig.py 
  53 4025%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/git_repository.py 
104161341%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/importer.py   
 57249214%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/importlocal.py
 15213312%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/importppa.py  
 100 8020%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/lint.py   
 36627724%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/logging.py
   8  450%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/merge.py  
 22019312%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/queue.py  
 17414815%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/remote.py 
 100 8515%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/repo_builder.py   
 193  398%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/review.py 
  82 6620%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/run.py
  90 3858%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/scriptutils.py
  96 5345%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/scriptutils_test.py   
   4  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/source_builder.py 
  83  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/source_builder_test.py
  60  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/source_information.py 
 29520630%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/submit.py 
 109 8918%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/tag.py
  76 6811%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/test_fixtures.py  
  10  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/test_git_repository.py
 156  0   100%
/snap/git-ubuntu/x1/lib/python3.6/site-packages/gitubuntu/test_importer.py  
   6  0   100%
/snap/git-ubuntu/

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

Fix for that last bit about the cache:
https://github.com/snapcore/snapcraft/pull/1980

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

(note that we already reset the cache for each part, but only for libs
that weren't found)

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

We probably need the cache to be either per-part, or do the rpath
patching after all parts have been primed.

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

Got it. Hello global state!

The problem is that dpkg is a prerequisite of xz-utils, but _also_
requires liblzma. As a result, when priming them one after the other, we
cache the lookup result for dpkg, and re-use it when priming xz-utils:

https://github.com/snapcore/snapcraft/blob/master/snapcraft/internal/elf.py#L118

When running them one after the other, the cache is cleared, and the
libs are properly found.

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

Or perhaps it's not properly setting rpaths for libraries coming from
the same part unless those directories already exist.

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

Okay check this out. I removes all parts from the project except dpkg
and xz-utils to speed things up.

If I have a clean tree and run `snapcraft prime` this is what I end up
with:

$ ldd prime/usr/bin/xz
prime/usr/bin/xz: /lib/x86_64-linux-gnu/liblzma.so.5: version `XZ_5.2' not 
found (required by prime/usr/bin/xz)
linux-vdso.so.1 =>  (0x7ffcfebf4000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fbb73c45000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbb73a28000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fbb7365e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbb7345a000)
/snap/core/current/lib64/../lib/x86_64-linux-gnu/ld-2.23.so => 
/lib64/ld-linux-x86-64.so.2 (0x7fbb73e67000)

Bad. If I clean the tree and now run `snapcraft prime dpkg` followed by
`snapcraft prime xz-utils` I get this:

$ ldd prime/usr/bin/xz
linux-vdso.so.1 =>  (0x7ffc261ea000)
liblzma.so.5 => 
/home/ubuntu/usd-importer/prime/usr/bin/../lib/liblzma.so.5 (0x7fae8bbdb000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fae8b9be000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fae8b5f4000)
/snap/core/current/lib64/../lib/x86_64-linux-gnu/ld-2.23.so => 
/lib64/ld-linux-x86-64.so.2 (0x7fae8be11000)

Good! I suspect this is Snapcraft not properly re-evaluating its
environment as it executes its lifecycle.

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

Try ppa:kyrofa/1752481. With that I get:

$ ldd /snap/git-ubuntu/x1/usr/bin/gpgv
linux-vdso.so.1 =>  (0x7ffd40d56000)
libz.so.1 => /snap/core/current/lib/x86_64-linux-gnu/libz.so.1 
(0x7fcb20e93000)
libbz2.so.1.0 => /snap/core/current/lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fcb20c83000)
libgcrypt.so.20 => /snap/git-ubuntu/x1/usr/bin/../lib/libgcrypt.so.20 
(0x7fcb2092)
libgpg-error.so.0 => 
/snap/git-ubuntu/x1/usr/bin/../lib/libgpg-error.so.0 (0x7fcb20707000)
libc.so.6 => /snap/core/current/lib/x86_64-linux-gnu/libc.so.6 
(0x7fcb2033d000)
/snap/core/current/lib64/../lib/x86_64-linux-gnu/ld-2.23.so => 
/lib64/ld-linux-x86-64.so.2 (0x7fcb210ad000)

However, the selftest still fails because xz is looking on the system
for lzma for some reason:

$ ldd $(which xz)
/snap/git-ubuntu/x1/usr/bin/xz: /lib/x86_64-linux-gnu/liblzma.so.5: version 
`XZ_5.2' not found (required by /snap/git-ubuntu/x1/usr/bin/xz)
linux-vdso.so.1 =>  (0x7ffc17177000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fc7ffc2e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc7ffa11000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc7ff647000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc7ff443000)
/snap/core/current/lib64/../lib/x86_64-linux-gnu/ld-2.23.so => 
/lib64/ld-linux-x86-64.so.2 (0x7fc7ffe5)

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1752481] Re: Regressions in 2.39.2 in xenial-updates in classic snaps (relative to 2.35)

[Kyle Fazzari]

Note that I've noticed the same issue with mksquashfs in snapcraft
itself, LP: #1752964.

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

Title:
  Regressions in 2.39.2 in xenial-updates in classic snaps (relative to
  2.35)

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

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

[Bug 1626121] Re: strict mode snaps crash with Segmentation fault on 16.10

[Kyle Fazzari]

Invalidating the Snapcraft task since it's fixed everywhere else.

** Changed in: snapcraft
   Status: New => Invalid

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

Title:
  strict mode snaps crash with Segmentation fault on 16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1626121/+subscriptions

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

[Bug 1727695] Re: snap linker/libs problem with 17.10

[Kyle Fazzari]

Would you mind trying the snapcraft from edge, please?

sudo snap install --classic --edge snapcraft

That has a fix that may help.

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

Title:
  snap linker/libs problem with 17.10

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

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

[Bug 1725198] Re: snap's naming scheme for executables breaks functionality and state of aliases is unclear

[Kyle Fazzari]

Indeed, specifying the aliases in the YAML no longer does anything, more
information on this is here:

https://forum.snapcraft.io/t/improving-the-aliases-implementation/18

However, specifying the aliases in the YAML never had anything to do
with automatically connected them, that always has been handled via an
assertion in the store, and it still is.

Simply request automatic aliases by creating a new forum post in the
"store" category.

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

Title:
  snap's naming scheme for executables breaks functionality and state of
  aliases is unclear

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

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

[Bug 1672407] Re: Adding a scriptlet doesn't mark a part as dirty

[Kyle Fazzari]

Fix here: https://github.com/snapcore/snapcraft/pull/1618

** Changed in: snapcraft
   Status: Triaged => In Progress

** Changed in: snapcraft
 Assignee: (unassigned) => Kyle Fazzari (kyrofa)

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

Title:
  Adding a scriptlet doesn't mark a part as dirty

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

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

[Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Kyle Fazzari]

Thanks for the update, Tyler. I know this has been a long road, but the
cumulative effect of everyone's hard work on this particular front will
be huge. I'm very much looking forward to this.

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

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

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

[Bug 1555569] Re: Use 'title' field for snap apps

[Kyle Fazzari]

Sergio, what is the snapcraft solution to this? I'm still under the
impression the title (and license) need to go into the snap.yaml, but
you seemed to think it was only out-of-band to the store. Did we get
that resolved?

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

Title:
  Use 'title' field for snap apps

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

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

[Bug 1694945] Re: setuptools v36.0.0 breaks the python plugin

[Kyle Fazzari]

** Changed in: snapcraft
   Status: In Progress => Fix Committed

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

Title:
  setuptools v36.0.0 breaks the python plugin

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

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

[Bug 1694496] Re: ubuntu/i915: incompatible pointer types

[Kyle Fazzari]

** Description changed:

  The ubuntu-xenial kernel doesn't compile if you use -Werror
  =incompatible-pointer-types. This seems to be due to ubuntu/i915, though
  it's possible there are others. For example, in
  ubuntu/i915/i915_gem_dmabuf.c, the signatures of the functions handed
  off to dma_buf_ops's begin_cpu_access and end_cpu_access don't match
  those expected in the struct. This seems like a recipe for undefined
  behavior.
+ 
+ Actually using -Werror=incompatible-pointer-types to build our kernel
+ seems like a good idea. Is there a reason we're not doing it?

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

Title:
  ubuntu/i915: incompatible pointer types

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

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

[Bug 1694496] [NEW] ubuntu/i915: incompatible pointer types

[Kyle Fazzari]

Public bug reported:

The ubuntu-xenial kernel doesn't compile if you use -Werror
=incompatible-pointer-types. This seems to be due to ubuntu/i915, though
it's possible there are others. For example, in
ubuntu/i915/i915_gem_dmabuf.c, the signatures of the functions handed
off to dma_buf_ops's begin_cpu_access and end_cpu_access don't match
those expected in the struct. This seems like a recipe for undefined
behavior.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

Title:
  ubuntu/i915: incompatible pointer types

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

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

[Bug 1617765] Re: Connections reset when downloading snaps from CDN

[Kyle Fazzari]

This is better: http://pastebin.ubuntu.com/24402954/

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

Title:
  Connections reset when downloading snaps from CDN

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

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

[Bug 1617765] Re: Connections reset when downloading snaps from CDN

[Kyle Fazzari]

Oh my. That looks dreadful.

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

Title:
  Connections reset when downloading snaps from CDN

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

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

[Bug 1617765] Re: Connections reset when downloading snaps from CDN

[Kyle Fazzari]

Just got this twice from an lxc container here. It succeeded the third
time. The mtr report to one of the failed IP addresses looks like this:


$ mtr --report 64.94.115.6
Start: Mon Apr 17 20:10:51 2017
HOST: growing-urchin  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.218.103.1   0.0%100.1   0.1   0.1   0.2   0.0
  2.|-- router.asus.com0.0%100.9   1.0   0.9   1.8   0.0
  3.|-- ???   100.0100.0   0.0   0.0   0.0   0.0
  4.|-- dtr01wlwlwa-tge-0-2-0-0.w  0.0%10   11.5  13.4   8.5  37.3   8.5
  5.|-- dtr04knwcwa-bue-1.knwc.wa 10.0%10   20.1  12.3  10.0  20.1   3.0
  6.|-- dtr03knwcwa-bue-2.knwc.wa  0.0%10   10.9  11.7  10.1  15.2   1.5
  7.|-- 96-34-111-218.static.unas  0.0%10   15.6  14.4  12.9  16.1   0.9
  8.|-- 96-34-108-178.static.unas  0.0%10   19.8  18.4  13.5  22.3   3.1
  9.|-- bbr01sttlwa-tge-0-1-0-4.s  0.0%10   33.6  23.2  17.3  33.6   5.7
 10.|-- prr01sttlwa-bue-1.sttl.wa  0.0%10   17.2  17.8  15.3  25.2   2.7
 11.|-- seattle-ix.pnap.net0.0%10   17.7  16.1  15.2  17.9   0.8
 12.|-- core1.po2.inapvox-31.sea.  0.0%10   17.4  19.2  17.4  22.5   1.6
 13.|-- border2.ae1-bbnet1.sef.pn  0.0%10   20.9  19.9  17.3  27.6   2.9
 14.|-- cdn-gw1.ve2.sef004.intern  0.0%10   15.7  16.8  15.7  18.0   0.6
 15.|-- cdce.sef004.internap.com   0.0%10   17.9  19.0  16.9  21.7   1.1

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

Title:
  Connections reset when downloading snaps from CDN

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

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

[Bug 1674484] Re: snap install core failure: permission denied (apparmor)

[Kyle Fazzari]

** Also affects: snapd
   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/1674484

Title:
  snap install core failure: permission denied (apparmor)

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

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

[Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Kyle Fazzari]

** Changed in: nextcloud-snap
   Importance: Unknown => High

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Bug 1621127] Re: snap-confine doesn't work with new snap-run/snap-exec flow

[Kyle Fazzari]

I assume this was actually released into xenial?

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

Title:
  snap-confine doesn't work with new snap-run/snap-exec flow

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1621127/+subscriptions

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

[Bug 1650207] Re: original lsb-release file should be preserved for classic mode

[Kyle Fazzari]

I've not tested anywhere else, but this bug is _not_ fixed on arm64,
running core from edge:

$ snap --version
snap2.23~201702241616.git.9d8157d~ubuntu16.04.1
snapd   2.23~201702241616.git.9d8157d~ubuntu16.04.1
series  16
kernel  4.4.0-1032-snapdragon

$ snap list
NameVersion   Rev   Developer  Notes
classic 16.04 17canonical  devmode
core16-2  1316  canonical  -
dragonboard 16.04-0.1824canonical  -
dragonboard-kernel  4.4.0-1032-3  16canonical  -

(classic)kyrofa@localhost:~$ cat /etc/os-release 
NAME="Ubuntu Core"
VERSION="16"
ID=ubuntu-core
PRETTY_NAME="Ubuntu Core 16"
VERSION_ID="16""
HOME_URL="http://www.snapcraft.io/";
BUG_REPORT_URL="http://bugs.launchpad.net/snappy/";

** Changed in: livecd-rootfs (Ubuntu)
   Status: Fix Committed => Confirmed

** Changed in: snappy
   Status: Fix Committed => Confirmed

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

Title:
  original lsb-release file should be preserved for classic mode

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

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

[Bug 1666873] Re: Snap icon is not visible when called from terminal but it does when called from dash

[Kyle Fazzari]

I think this really comes down to: when you run the snapped application
via .desktop file, you get an icon (since the icon is specified in the
.desktop file). When you run the application directly in the terminal,
there's no icon as the icon is only specified in the .desktop file.

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

Title:
  Snap icon is not visible when called from terminal but it does when
  called from dash

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

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

[Bug 1665126] Re: snap not listed in categories

[Kyle Fazzari]

** Description changed:

  1- I uploaded a snap on myapps.developer.ubuntu.com
  2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
  3- Default type: ? (I choose application, but not sure what it does exactly)
  4- Opening Ubuntu Software on Ubuntu 16.04 I can find and install it when 
using the search bar
  5- BUT my application is not listed in any categories, not even in Games - All
  6- After installing the application, I can see it listed in Games - Kids 
(because the .desktop file have this entry Categories=Game;KidsGame?)
  
- Looks like only .deb are listed in the Ubuntu Software?
+ Looks like only .deb are listed in categories within Ubuntu Software?

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

Title:
  snap not listed in categories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1665126/+subscriptions

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

[Bug 1560942] Re: Support swap

[Kyle Fazzari]

Good point, thanks ogra. Sorry for the noise!

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

Title:
  Support swap

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

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

[Bug 1560942] Re: Support swap

[Kyle Fazzari]

Note that this was assigned to snapd as the mailing list discussion led
me to believe this would be implemented via the gadget snap, which is
something snapd would need to support no?

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

Title:
  Support swap

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

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

[Bug 1576411] Re: UTF-8 is not very well supported inside snaps

[Kyle Fazzari]

** Also affects: snapd
   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/1576411

Title:
  UTF-8 is not very well supported inside snaps

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

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

[Bug 1636934] Re: snapctl seem to cache values even if snap is removed and then installed again

[Kyle Fazzari]

** Package changed: snapd (Ubuntu) => snapd

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

Title:
  snapctl seem to cache values even if snap is removed and then
  installed again

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

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

[Bug 1661126] Re: Add One-shot Install/Uninstall Hook

[Kyle Fazzari]

** Package changed: snapd (Ubuntu) => snapd

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

Title:
  Add One-shot Install/Uninstall Hook

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

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

[Bug 1586400] Re: Snap type: change from "os" to "core"

[Kyle Fazzari]

** Also affects: snapd
   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/1586400

Title:
  Snap type: change from "os" to "core"

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1586400/+subscriptions

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

[Bug 1599620] Re: SNAP_REEXEC doesn't cover snap-exec

[Kyle Fazzari]

** Package changed: snapd (Ubuntu) => snapd

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

Title:
  SNAP_REEXEC doesn't cover snap-exec

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

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

[Bug 1636633] Re: Content interface supports multiple sources, but only one destination

[Kyle Fazzari]

** Package changed: snapd (Ubuntu) => snapd

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

Title:
  Content interface supports multiple sources, but only one destination

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

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