So to conclude your questions: during the backporters meeting we decided
that
(for now, of course things might change going forward if/when there is a
need for them to change)
* about assigning to somebody/someteam when it's ready for review: not
required, as we just follow all bugs we are
** Changed in: sdbus-cpp (Ubuntu Focal)
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/1916068
Title:
[BPO] Please backport sdbus-cpp 0.8.3-4 (universe)
> Assigning back to ddstreet - what would be the right assignee now,
~ubuntu-backporters, no-one, ... ?
I added a discussion item for the next backporters meeting for this:
https://wiki.ubuntu.com/UbuntuBackports/Agenda#Discussion
> And out of curiosity - would that now show up in [1] or does
It seems it appeared here:
https://launchpad.net/ubuntu/focal/+queue?queue_state=0_text=
Thank you for your work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916068
Title:
[BPO] Please backport
FYI: I see it in the NEW queue, which seems to be kind of usual/as-
expected. But would -unapproved be the next queue then?
** Description changed:
[Impact]
There is an upcoming Azure-related project that would like to support
Ubuntu 20.04 LTS out of the box, and one of the requirements
After review testing and preparing the backport-process details (in the
bug description) I've sponsored this to focal-backports.
Assigning back to ddstreet - what would be the right assignee now,
~ubuntu-backporters, no-one, ... ? And out of curiosity - would that now show
up in [1] or does
test install from PPA:
root@f:~# apt install libsdbus-c++-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libsdbus-c++-bin libsdbus-c++0
The following NEW packages will be installed:
Hopefully this is enough reg. testing: newer releases have an "examples"
directory upstream. I've cloned the repository on Focal, added the
package via my PPA, and built the examples locally (and stripped rpath
to ensure they are using the system lib). The examples are working fine:
** Description changed:
[Impact]
There is an upcoming Azure-related project that would like to support
Ubuntu 20.04 LTS out of the box, and one of the requirements is the
sdbus-cpp library.
The library is available in hirsute and bullseye, but not in focal.
It would be great if it
** Description changed:
[Impact]
- There is an upcoming Azure-related project that would like to support Ubuntu
- 20.04 LTS out of the box, and one of the requirements is the sdbus-cpp
library.
+ There is an upcoming Azure-related project that would like to support
+ Ubuntu 20.04 LTS out of
I (and the team) am only around helping Luca on this. It would be someone under
Eric, but TBH pinging and finding this someone might add more stall to
something already taking (too) long.
I'll use it as an exercise of the new backport process for myself.
--
You received this bug notification
ack, i'll assign this to Christian then, he can delegate it if he wants,
as his team is assigned this elsewhere i believe, and they'll need to
use the proper new backports process
** Changed in: sdbus-cpp (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received
> Do you have upload rights to upload the backported package, or is a
sponsor going to prepare and upload for you? I think @paelzer's team is
doing the work for you right?
That's right - I do not have uploaders rights, so I just pushed to the
linked PPA to show it works
** No longer affects:
> I can't click on reopen for some reason
that's ok, we don't use the 'focal-backports' task anymore, the
backports process just uses the ubuntu package for tracking now; since
the bug is also (already) open against the sdbus-cpp package it's good.
Do you have upload rights to upload the
14 matches
Mail list logo
