Need to convert the issue into an SRU now that Noble is out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063359
Title:
[FFe] Use of NDEBUG in d/rules for 2.3.3+dfsg-0ubuntu2 on Noble
generates
The Gazebo simulator running on a Noble container :)
** Attachment added: "Image of Gazebo Harmonic on Noble"
https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/2063359/+attachment/5770080/+files/Screenshot%20from%202024-04-24%2018-36-29.png
** Description changed:
Version bump for
Public bug reported:
Revision bump for current ogre on Noble
- Tested on PPA with version: ogre-next -
2.3.3+dfsg-6~202404240955~ubuntu24.04.1
https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe/+packages
- MR:
The ogre-next update was released and ignition-cmake was removed in
https://bugs.launchpad.net/ubuntu/+source/ros-catkin/+bug/2063103. I've
updated the statuses. All done here.
** Changed in: ogre-next (Ubuntu)
Status: Triaged => Fix Released
** Changed in: ignition-cmake (Ubuntu)
The ignition-common and ignition-physics packages has be removed from
Ubuntu in https://bugs.launchpad.net/ubuntu/+source/ros-
catkin/+bug/2063103 yesterday.
It can be totally omitted totally. I'm going to close the MR and edit
the description.
** Summary changed:
- [FFe] Update urdfdom, dart
Thanks Utkarsh!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058279
Title:
[FFe] Sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental
(main)
To manage notifications about this bug go to:
I'm afraid that we are stuck in transitioning https://ubuntu-archive-
team.ubuntu.com/proposed-migration/update_excuses.html#ogre-next because
there is a problem with autopkgtest. Sorry for that.
I've created a new merge-request to solve the problem
Friendly ping.
I've created the three merge request for trying to move this forward and
make it easier for reviewers. Let me know what else needs to be done
more to help the testing. Thanks!
** Merge proposal linked:
** Merge proposal linked:
https://code.launchpad.net/~j-rivero/ubuntu/+source/urdfdom/+git/urdfdom/+merge/464439
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053254
Title:
[FFe] Update
python-flake8 7.0.0 is no Noble (main repo).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058914
Title:
[FFe] python-pytest-flake8 FTBFS against python-flake8 7
To manage notifications about
Given that the solution proposed is to ship a custom patch, I'm going to
bump this to a FFe to get acceptance of the release-team and also
unblock the excuses transition in existing Noble development cycle.
* Merge request:
** Merge proposal linked:
https://code.launchpad.net/~j-rivero/ubuntu/+source/python-pytest-flake8/+git/python-pytest-flake8/+merge/464197
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058914
In coordination with Scott, we have raised this to be a FFe since the
package is severity damaged as it is now and probably unusable for any
use case that is not completely trivial.
I've created and linked the merge-request with the bumped version
against ubuntu/devel and testing the package.
**
** Merge proposal linked:
https://code.launchpad.net/~j-rivero/ubuntu/+source/ros2-colcon-core/+git/ros2-colcon-core/+merge/464037
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060717
Title:
> Not sure what would be best, if RM the package or invest time into
patching it.
Since no action happened last week, my teammate Chris Lalancette patched
the existing version to work with current flake8 on noble-proposed
7.0.0. I have updated the upstream PR with the information
** Description changed:
Trying to compile weechat from source:
-
+
root@voltron ~/weechat/build # cmake .. -DCMAKE_BUILD_TYPE=Debug
-- Checking for one of the modules 'php8;php7'
-- Configuring done
-- Generating done
-- Build files have been written to: /root/weechat/build
Public bug reported:
Trying to compile weechat from source:
root@voltron ~/weechat/build # cmake .. -DCMAKE_BUILD_TYPE=Debug
-- Checking for one of the modules 'php8;php7'
-- Configuring done
-- Generating done
-- Build files have been written to: /root/weechat/build
Public bug reported:
When I'm asked for the password to encrypt, and I type the password and click
Next, it briefly loads and the Enter password box appears again.
However, the password is correct, because I can restore a backup. Only the test
doesn't work.
lsb_release -rd
Description:
I think I've answered the feedback in the last 5 commits and the MR is ready:
https://code.launchpad.net/~j-rivero/ubuntu/+source/lcm/+git/lcm/+merge/463155
P.D: Vladimir I added you as a reviewer, I hope it is fine for you.
--
You received this bug notification because you are a member of
Thanks Andres, Vladimir. I'll try to get the merge request ready in the
next couple of days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053256
Title:
[FFe] Update lcm to 1.5 for Noble
To
We (at the Open Robotics Foundation Alliance) are interested in helping
with the transition of python-flake8 from noble-proposed to noble and
have been monitoring the transition for some weeks.
There is an attempt of fixing the code in
https://github.com/tholo/pytest-flake8/pull/96 that we can
Thanks for the info Andreas!
Update: yesterday ignition-rendering was removed from Noble in
https://bugs.launchpad.net/ubuntu/+source/ignition-
rendering/+bug/2058851. I'm going to update the description to remove
the references to ignition-rendering.
** Changed in: ignition-rendering (Ubuntu)
Thanks Utkarsh!
The pcl package does not have autopkgtest itself, but the ros-perception-pcl
has a large set of them. I ran them in a noble docker image, seems fine to me
(selected output):
autopkgtest [19:37:43]: starting date and time: 2024-03-22 19:37:43+0100
autopkgtest [19:37:43]:
Upstream fix was merged and released in 5.5.0. Noble is shipping this
patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2033518
Title:
spyder 5.4.4+ds-1 autopkgtest fails
To manage
Changelog from existing version on Noble
** Attachment added: "changelog_dart"
https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+attachment/5757532/+files/changelog_dart.txt
** Description changed:
Versions bump for the Open Robotics Community packages:
- urdfdom to
** Description changed:
Versions bump for the Open Robotics Community packages:
- urdfdom to 4.0.0-0ubuntu1
+(Imported from https://salsa.debian.org/science-team/urdfdom)
- dart to 6.13.1+ds-0ubuntu2
+https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel
The PPA now has the s390x package of dart finally.
Answering the issues that Lucas found in the packaging:
> And FWIW, we are using git to maintain ubuntu package (using git-ubuntu), bzr
> has not been used for packages for a while AFAIK. But if it is easier for you
> to provide the packages in
Public bug reported:
Please sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main)
Changelog entries since current noble version 1.13.0+dfsg-4build2:
pcl (1.14.0+dfsg-1) experimental; urgency=medium
* Update Files-Excluded to drop zlib sources
* New upstream version 1.14.0+dfsg
Thanks Benjamin. I've been working on Lucas comments during the last week and
hope to have ready the changes in this week. Yesterday upstream releases a new
version that fixes all the compiler warnings for GCC-13 and I want to include
it so we don't need to disable them:
Thanks Steve for the approval.
> I'm not sure why there's an ignition-cmake task here, please clarify.
ignition-cmake are a set of CMake helpers used by the ignition/gazebo
family but can also be used alone. One of the helpers is a Find module
for ogre-next (also named Ogre2)
** Description changed:
- Version bump for ogre-next to version 2.3.1, well tested by Open
+ Version bump for ogre-next to version 2.3.3, well tested by Open
Robotics under the Gazebo simulator.
- * Package PPA:
- - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe
-
** Summary changed:
- Update ogre-next to 2.3.1 for Noble
+ Update ogre-next to 2.3.3 for Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054477
Title:
Update ogre-next to 2.3.3 for Noble
To
> Regarding how you are providing the package to be sponsored, I
personally would prefer a git branch against pkg/ubuntu/devel. For these
cases where we go ahead of debian, what I would do is have the first
commit on top of pkg/ubuntu/devel be the new upstream version, and then
whatever changes
Diff of upstream changes from version 1.3.1 to 1.5.0
** Description changed:
Version bump for the lcm package to latest version 1.5.0+repack-0ubuntu1
Package PPA:
- - https://launchpad.net/~j-rivero/+archive/ubuntu/lcm-1.5
- (let me know if you prefer a Bzr branch)
+ -
Now in Noble/Universe. Fix Released.
** Changed in: http-relay (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054151
Title:
New http_relay
It is now on noble proposed https://launchpad.net/ubuntu/+source/http-
relay/2.1.3-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054151
Title:
New http_relay package for Noble (for Robotics
The package has been uploaded in Debian to the NEW queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054151
Title:
New http_relay package for Noble (for Robotics community)
To manage
*** This bug is a duplicate of bug 1973167 ***
https://bugs.launchpad.net/bugs/1973167
Same problem with on Dell XPS 13 with Linux Ubuntu 18.04.6 LTS
Unfortunately the same issue with linux-image-4.15.0-180-generic.
--
You received this bug notification because you are a member of Ubuntu
Fixed based on
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1927192
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927192
Title:
gdb ftbfs on armhf, testsuite timeouts
To manage
It feels pretty sluggish to use. Not sure if it's a packaging issue or
chromium issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To
It works for me on 102.0.5005.40 (latest/beta channel) but with the
following GPU error messages:
```
[2005781:2005781:0506/130903.210912:ERROR:gpu_init.cc(481)] Passthrough is not
supported, GL is egl, ANGLE is
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
In the Xorg session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970279
Title:
[amdgpu] My monitor image turned yellow.
To manage notifications about this bug go to:
Public bug reported:
I had to switch from Wayland to Xorg on the login screen, and after
login the screen had a yellow filter.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic
I upgraded the following to 3.44.0-1ubuntu1 from jammy-proposed:
evolution evolution-common evolution-plugin-bogofilter evolution-plugin-
pstimport evolution-plugins libevolution
I can also confirm I can compose messages and replies.
--
You received this bug notification because you are a
Thanks so much Graham! I was testing the installation and the simulator
and seems to work fine. There is a minor inconvenient for users that is
trivial to fix: https://bugs.launchpad.net/ubuntu/+source/ignition-
gazebo/+bug/1969803.
--
You received this bug notification because you are a member
are unusual.
Attached is the debdiff against current version.
** Affects: ignition-gazebo (Ubuntu)
Importance: Undecided
Assignee: Jose Luis Rivero (j-rivero)
Status: New
** Tags: jammy
** Patch added: "ignition-gazebo_recommends_tools.debdiff"
https://bugs.launchpa
Ubuntu 22.04
Evolution 3.44.0-1
Sway 1.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969584
Title:
Evolution does not allow editing email content on Wayland
To manage notifications about this
Same issue. Screenshot attached is a reply to an email.
Blank window happens with:
* HTML
* Plain text
Workaround: switch to any of the Markdown options when composing a
message.
** Attachment added: "2022-04-20T09:36:05,423753999+01:00.png"
I think I have it. I added more details in the commit to bzr and in the
patch description according to DEP-3. In summary:
The test is failing due to a problem in ignition-tools version 1.4.1 (coming
from Debian). It does
not include libignition-tools-backward lib due to a bug in Debian packaging
Looking at it now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960940
Title:
[needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
To manage notifications about this bug go to:
> We just need a couple of small patches:
> - ignition-physics for amd64
> https://bugs.launchpad.net/ubuntu/+source/ignition-physics/+bug/1965064
> - ignition-rendering
> https://bugs.launchpad.net/ubuntu/+source/ignition-rendering/+bug/1967888
These open bugs are now fixed. We should be in a
Hello Łukasz:
I think we did a good work with versioning and the upload should have
gone just fine. In fact, I was able to test Gazebo 11.10.2+dfsg-1
directly from Jammy repositories and works like a charm. It does not
conflict anymore with opencv.
Thanks so much for the review and upload!
--
** Changed in: gazebo (Ubuntu)
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/1773811
Title:
[SRU] Missing static libs in the -dev package metadata
To manage
Hello Łukasz:
Is there anything more I can do to help with these two remaining packages? We
have been tested ignition-gazebo simulator on Jammy and it works great. We just
need a couple of small patches:
- ignition-physics for amd64
** Patch added: "ignition-rendering_6.1.0+ds-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ignition-rendering/+bug/1967888/+attachment/5577343/+files/ignition-rendering_6.1.0+ds-0ubuntu2.debdiff
** Changed in: ignition-rendering (Ubuntu)
Assignee: (unassigned) =&
Luis Rivero (j-rivero)
Status: New
** Tags: jammy
** Description changed:
Current version of ign-rendering on Jammy 6.1.0+ds-0ubuntu1 lack of some
basic linking on ogre-next to make the software really usable, otherwise
the loader fails to find the needed ogre2 symbols. On top
** Summary changed:
- Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main)
+ [needs-sponsor] Sync gazebo 11.10.2+dfsg-1 (universe) from Debian
experimental (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Added `gnome-control-center` to affected - GNOME online accounts
requires a web browsing session to auth into some services.
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
`WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution` works around the issue for
me on a Sway wayland session and running evolution in native wayland
mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "eglinfo"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+attachment/5572891/+files/eglinfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966418
Title:
I get the same from es2_info and eglinfo
** Attachment added: "es2_info"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+attachment/5572890/+files/es2_info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The tooltip comes from hovering with the mouse pointer over an
(invisible) link on the email. Not sure why the pointer wasn't captured.
** Attachment added: "2022-03-25T10:58:57,801723903+00:00.png"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966418
Title:
[jammy regression] Evolution does not display message content anymore
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966418
Title:
[jammy regression] Evolution does not display message content anymore
To manage notifications about this bug go to:
** Attachment removed: "Screenshot of evolution showing no message contents"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+attachment/5572860/+files/2022-03-25T10%3A58%3A57%2C801723903+00%3A00.png
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Evolution has suddenly stopped displaying message contents on the last
24h. Starting it up from the command line shows this output:
```
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
```
I don't
Confirmed issues with 5.13.0-37 with 2i2 2nd Gen with either pulse or
alsa. Sound is slower, chopped with jack started, like a very lower
quality and has lower pitch. However 5.13.0-35 works perfectly. Let's
try edit /etc/pulse/daemon.conf.
--
You received this bug notification because you are a
This currently breaks Vagrant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964025
Title:
Do not support OpenSSL 3
To manage notifications about this bug go to:
I can confirm 2.04-1ubuntu26.15 from focal-proposed fixes it. Thank you
Lukasz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840560
Title:
"error: can't find command hwmatch" during grub
To
to avoid installing ruby.
* Target experimental to test tbb/onetbb transition #1007222
11.10.2 upstream source should be ready for it.
-- Jose Luis Rivero Sat, 19 Mar 2022
19:58:37 +
I've tested this new version on Jammy under my PPA (Gazebo is amd64 only):
https://launchpad.net/~j
Public bug reported:
After updates I applied last friday, my onboard audio has ceased to
function. No audio comes out the laptop speakers and no audio goes in
the internal microphone (built in audio).
If I connect my bluetooth headset (Bose NC700) the audio works, but only
ever in mono. I cannot
> keep an eye on the builds and always available to provide patches as
needed.
I just checked that ignition-gui, ignition-rendering and ignition-
sensors have been built just fine in amd64, arm64, armhf, ppc64el and
riscv64. The only remaining problem would be s390x but the issue is the
lack of
> I have sponsored the rendering packages from the other bug. Not sure
if I'll have the cycles to sponsor/review the others today.
No worries Łukasz. I've been using these last days to check that all
pieces are in place and found a weird bug on ignition-physics amd64
(which is a dependency of
Attached is the debdiff that solves the problem for the amd64 build by
filtering out the flto=auto -ffat-lto-objects.
The patch also includes a fix for the ppc64 build now that we are at it.
Both changes are reflected in the Changelog and tested in my PPA:
* amd64
Public bug reported:
Current ignition-physics version 5.1.0+ds1-4 fails on amd64 with segfaults in
some of the tests:
https://launchpadlibrarian.net/589246385/buildlog_ubuntu-jammy-amd64.ignition-physics_5.1.0+ds1-4_BUILDING.txt.gz
The situation was unusual since the same version imported from
I can confirm "20220314.gitcd01f857-0ubuntu2" from proposed fixes the
problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964814
Title:
linux-firmware fails to upgrade to
Thanks so much Łukasz for reviews and comment.
> why is NEWS excluded from the ingnition-rendering tarball? It's just
an URL. Basically I'd normally not repack the tarball and exclude
sources unless really necessary (like when for instance upstream ships
something bad in the tarball, like
Forgot to add. Chromium is from the edge channel, at version
101.0.4919.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To manage
It still fails to start (sway 1.7):
~ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[278662:278662:0310/100635.924517:ERROR:wayland_connection.cc(209)] Failed to
connect to Wayland display
[278662:278662:0310/100635.924552:ERROR:ozone_platform_wayland.cc(226)] Failed
to
Public bug reported:
When a program is running in an overlayfs, /proc/self/maps reports the
wrong path. Notably, it lacks a prefix equal to the mountpoint of the
overlayfs. This only happens on linux-gcp-5.13, it does not reproduce on
non-gcp kernels.
Small repro:
cat > repro.sh <
LANG=C.UTF-8
Thank you, I was plagued by this issue on my Bose NC700 cans. In my case
bluetoothd isn't crashing btw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962542
Title:
[jammy] Bluetooth headphones
** Summary changed:
- [needs-packaging] Include ignition rendering packages in Ubuntu Jammy
+ [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- [needs-packaging] Include ignition-gazebo simulator in Ubuntu Jammy
+ [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963583
Title:
Needs rebuild in Jammy for python3.10
To manage notifications about this bug go to:
Hello Mathew:
Please note that the software is already packaged and can be found in:
PPA:
https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages
Bzr:
* https://code.launchpad.net/~j-rivero/+junk/ignition-gazebo
* https://code.launchpad.net/~j-rivero/+junk/ignition-launch
Could we
Hello Mathew:
Please note that I've already packaged the software and it is ready for
review. You can access to via:
PPA:
* https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages
Bzr:
* https://code.launchpad.net/~j-rivero/+junk/ignition-rendering
*
Thanks Łukasz!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961319
Title:
ogre-next SMID fix for ppc64el, riscv64, s390x
To manage notifications about this bug go to:
I think I solved it. Attached is the debdiff with the pacth to d/rules
and the bump to d/changelog.
I tested it in all the arches in
https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-
jammy/+packages (bump there from 0ubuntu2 to 0ubuntu2.1 was nothing but
rebuild with all arches enabled
> Okay, the bad news is: it looks like the ogre-next source package
FTBFS on ppc64el and s390x. Can you take a look at the build logs and
see if this is something that can be fixed with a follow-up upload?
Ouk, trivial to fix if I'm not wrong.
> I'd recommend a separate bug for that then.
Here
D.
Build Ogre without OGRE_USE_SIMD"
| ^
"""
The reason is that the configuration leave enabled the OGRE_USE_SIMD for
anything but arm*. The logic should be reverted and only enable it on
x64.
** Affects: ogre-next (Ubuntu)
Importance: Undecided
Assignee: Jose Luis Rivero (j-r
Thanks for review Łukasz.
Fixes and comments inline. With the requested change in the version
number, I'm using a different PPA to upload the version since it is
lower than the one in jammy-package PPA. New one is:
https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-jammy
> Remark re: the
.
** Affects: ubuntu
Importance: Undecided
Assignee: Jose Luis Rivero (j-rivero)
Status: New
** Tags: jammy
** Description changed:
Please include the ignition-gazebo Simulator in Ubuntu Jammy. Ignition
Gazebo is the successor of Gazebo and would be a very valuable addition
** Tags removed: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960260
Title:
[needs sponsor] Include ignition rendering packages in Ubuntu Jammy
To manage notifications about this
** Description changed:
- Please include the software ignition-rendering in Ubuntu Jammy. It will
- require ogre-next to work, in
+ Please include the ignition rendering stack, composed by three packages
+ ignition-rendering, ignition-gui and ignition-sensors.
+
+ It will require ogre-next to
> I'll look into this in a moment, thank you for preparing the packages
in the PPA.
Thanks Łukasz. Let me know if I can help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960149
Title:
Include
** Summary changed:
- [needs-packaging] Include ignition-rendering in Ubuntu Jammy
+ [needs-packaging] Include ignition rendering stack in Ubuntu Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1957948 ***
https://bugs.launchpad.net/bugs/1957948
Issue also present in Impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958022
Title:
fish
Thanks so much Sebastien!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960266
Title:
[needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies
(DART, ignitions) from Debian Unstable
To
Thanks Sebastien for the comment. I was checking my Debian QA page
https://qa.debian.org/developer.php?login=jriv...@osrfoundation.org and
did not check the -proposed pocket, I see now that the packages are
there using rmadison (not sure if there is a better dashboard for the
check).
I'm
I added packaging in:
* 2.2.5 in PPA
https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+packages
(amd64, arm64, armhf).
* I've also updated to bzr https://code.launchpad.net/~j-rivero/+junk/ogre-next
** Description changed:
Please include the software ogre-next in Ubuntu Jammy.
1 - 100 of 6890 matches
Mail list logo
