TL;DR:
As many I've gone deeper, but none of the times in `stat` nor the
checksums of /usr/lib/systemd/system/hello.service did change.
Turns out this wasn't even about their file states.
And additionally my understanding was wrong, and potentially yours as well.
The state if this is outdated
Final state check:
- FFE was approved as well.
- MIR approved
- Per [2] it seems was consciously (freeze) accepted 15h ago.
- All dependencies are already in main (could have changed)
- Seen in component mismatches due to [2]
- The needed exclude needed is in place [1]
Only one version in noble
In noble we only have one version atm:
aom | 3.8.2-2build1 | noble/universe | source
To promote src:aom bin:libaom3
Override component to main
aom 3.8.2-2build1 in noble: universe/misc -> main
Override [y|N]? y
1 publication overridden.
Override component to main
libaom3 3.8.2-2build1 in noble
In noble we only have one version atm:
libde265 | 1.0.15-1build3 | noble/universe | source
To promote src:libde265 bin:libde265-0
Override component to main
libde265 1.0.15-1build3 in noble: universe/misc -> main
Override [y|N]? y
1 publication overridden.
Override component to main
libde265-0
In noble we only have one version atm:
libheif | 1.17.6-1ubuntu4 | noble/universe | source
To promote src:libheif bin:heif-gdk-pixbuf bin:heif-thumbnailer
bin:libheif-examples bin:libheif-plugin-aomdec bin:libheif-plugin-aomenc
bin:libheif-plugin-libde265 libheif1
Override component to main
Thanks for the updates Lukas
Ok, so the stack around libheif seems to complete just in time.
To summarize the situation:
- MIR-wise all the dependencies are good to go now (libheif 1827442, libde265
2004449, aom 2004442, libyuv 2004516, libwebm 2004523)
- The related FFE (2061090) was granted
-
Ready
Full stack check in
https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442/comments/55
The required exclude is in since https://git.launchpad.net/~ubuntu-core-
dev/ubuntu-
seeds/+git/ubuntu/commit/?id=640c0d5814139575e9839d533f5408e7ac43272a
--
You received this bug notification
Ready
Full stack check in
https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442/comments/55
The dependency tree only needs libaom3, the related auto-includes are
safe (libjs-mathjax and libaom3 are the only dependencies of libaom-doc
libaom-dev).
--
You received this bug notification
Slight change here - this isn't needed for libaom3.
Due to the good use of non-embedded libs we now have correct dependency
tracking.
That shows that only aom-tools would needed it, which isn't pulled in from
libheif.
We could promote it, but if you want that you'd need to seed aom-tools
(if
Slight change here - this isn't needed for libaom3.
Due to the good use of non-embedded libs we now have correct dependency
tracking.
That shows that only aom-tools would needed it, which isn't pulled in from
libheif.
We could promote it, but if you want that you'd need to seed aom-tools
(if
Sorry for the delay, I didn't want to mess this up doing it in between
meetings.
Currently in those releases:
dotnet6 | 6.0.127-0ubuntu1~22.04.1 | jammy-security/universe | source, amd64,
arm64
dotnet6 | 6.0.128-0ubuntu1~22.04.2 | jammy-updates/universe | source, amd64,
arm64
dotnet6 |
Sorry for the delay, I didn't want to mess this up doing it in between
meetings.
Currently in those releases
dotnet8 | 8.0.103-8.0.3-0ubuntu1~22.04.1 | jammy-security/universe | source,
amd64, arm64
dotnet8 | 8.0.103-8.0.3-0ubuntu1~22.04.2 | jammy-updates/universe | source,
amd64, arm64
Builds are all complete, waiting for tests to get run
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060805
Title:
strace fails to build it's tests on arm-linux-gnueabihf with 64bit
time_t
To
Upstreamed via: https://lists.strace.io/pipermail/strace-
devel/2024-April/011415.html
Updated patch header and uploaded
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060805
Title:
strace fails
Also valid for Jammy/Mantic, see [1] for more details.
Promoting ...
[1]:
https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For Mantic I see it is pulled in via the seeds as expected now [1].
For jammy that is not there, but that is because it was not updated for two
months which is a different problem - the change is the very same and is ok.
The case is approved, it was meant to also go back to Jammy and where the
Fix approved, submitted upstream to have a reference. I hope the lists
accepts that without waiting for a moderator. If it takes too long I'll
upload the fix to Ubuntu and mention the upstreaming ref later here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
It has not yet completed build, but seems to have passed the section it failed
before.
Hence opening up for review:
PPA:
https://launchpad.net/~paelzer/+archive/ubuntu/lp-2060805-time-t-conversions/+packages
MR:
Per check in ubuntu-release no one started to look into this so far.
I'm unsure if I can complete it with all the other release related things, but
I'll leave what I've found here.
Strace defines an own time type in [1]
$ cat tests/kernel_old_timespec.h
...
typedef struct {
# if
python-boto3, python-botocore, python-s3transfer promoted to main, which
should unblock [1].
python-boto demoted to universe as it is no more needed (we can't go all
in yet and remove it as there still is heat-cnft).
Override component to universe
python-boto 2.49.0-4.1 in noble: main/python ->
Full stack is ready now
Override component to main
python-boto3 1.34.46+dfsg-1ubuntu1 in noble: universe/misc -> main
python3-boto3 1.34.46+dfsg-1ubuntu1 in noble amd64:
universe/python/optional/100% -> main
python3-boto3 1.34.46+dfsg-1ubuntu1 in noble arm64:
universe/python/optional/100% ->
Full stack is ready now
Override component to main
python-s3transfer 0.10.1-1ubuntu2 in noble: universe/misc -> main
python3-s3transfer 0.10.1-1ubuntu2 in noble amd64:
universe/python/optional/100% -> main
python3-s3transfer 0.10.1-1ubuntu2 in noble arm64:
universe/python/optional/100% -> main
Thanks also for the warning in the package description and rebasing this
onto the fixes in 0.10.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/2061750
Title:
[MIR] python-s3transfer as indirect
Full stack is ready now
Override component to main
python-botocore 1.34.46+repack-1ubuntu1 in noble: universe/misc -> main
python3-botocore 1.34.46+repack-1ubuntu1 in noble amd64:
universe/python/optional/100% -> main
python3-botocore 1.34.46+repack-1ubuntu1 in noble arm64:
An extra word on why this all got so late and lost for too long for full
transparency. Simplestreams is held in main by `platform-git/supported-
maas:53: * python3-simplestreams`. It is per-subscriptions owned by not
one, but two teams (already bad) - server & maas teams for historical
reasons.
[0] has completed, migrated out of proposed. It now runs tests at build
time [2] and via autopkgtest-pkg-python [1].
[0]: https://launchpad.net/ubuntu/+source/python-s3transfer/0.10.1-1ubuntu2
[1]: https://autopkgtest.ubuntu.com/packages/p/python-s3transfer
[2]:
Override component to main
trace-cmd 3.2-1ubuntu2 in noble: universe/devel -> main
libtracecmd-dev 3.2-1ubuntu2 in noble amd64: universe/libdevel/optional/100% ->
main
libtracecmd-dev 3.2-1ubuntu2 in noble arm64: universe/libdevel/optional/100% ->
main
libtracecmd-dev 3.2-1ubuntu2 in noble
Override component to main
libtraceevent 1:1.8.2-1ubuntu2 in noble: universe/misc -> main
libtraceevent-dev 1:1.8.2-1ubuntu2 in noble amd64:
universe/libdevel/optional/100% -> main
libtraceevent-dev 1:1.8.2-1ubuntu2 in noble arm64:
universe/libdevel/optional/100% -> main
libtraceevent-dev
Override component to main
libtracefs 1.8.0-1ubuntu1 in noble: universe/misc -> main
libtracefs-dev 1.8.0-1ubuntu1 in noble amd64: universe/libdevel/optional/100%
-> main
libtracefs-dev 1.8.0-1ubuntu1 in noble arm64: universe/libdevel/optional/100%
-> main
libtracefs-dev 1.8.0-1ubuntu1 in noble
Indeed, I've seen the runs with the results as predicted.
We should not forget about following up on these, so I've filed
- autopkgtests fail on ppc64el -> bug 2062119
- autopkgtests fail on s390x (segfault) -> bug 2062118
for you to follow up, please tag them as needed in foundations to not fall
I'll assign Adrien as the agreement on the MIR was to follow up on
these, but also Frank to sync this with IBM for their input which TBH
could be anything from "here is the fix" to a worse "it will never work
please remove it"
Also there is a sibling of this for s390x in bug 2062118
** Changed
Public bug reported:
As part of the added QA to libtracefs it was found that it triggers issues on
ppc64el.
It is not yet clear if those are just test artifacts or real deeper problems.
Either way, while in the time pressure of the noble release the decision
was simplified like "The tests
Public bug reported:
As part of the added QA to libtracefs it was found that it triggers a segfault
on s390x.
This isn't just a test failing, it seems this is still deeply broken on s390x.
Either way, while in the time pressure of the noble release the decision
was simplified like "The tests
I'll assign Adrien as the agreement on the MIR was to follow up on
these, but also Frank to sync this with IBM for their input which TBH
could be anything from "here is the fix" to a worse "it will never work
please remove it"
Also there is a sibling of this for ppc64el in bug 2062119
** Changed
Removing packages from noble:
telegraf 1.22.3+ds1-0ubuntu2 in noble
telegraf 1.22.3+ds1-0ubuntu2 in noble amd64
telegraf 1.22.3+ds1-0ubuntu2 in noble arm64
telegraf 1.22.3+ds1-0ubuntu2 in noble armhf
telegraf
Agreed, and due to that it gets rather few updates (for example M/N are
the same)
telegraf | 1.21.4+ds1-0ubuntu2 | jammy/universe | source
telegraf | 1.22.3+ds1-0ubuntu2 | mantic/universe | source
telegraf | 1.22.3+ds1-0ubuntu2 | noble/universe | source
But gladly has no reverse
Full stack ready, all dependencies seen in component mismatches, FFE
approved, MIR approved, only the top level change pulling this in is in
-proposed and ready there other than this mismatch -> promoting.
Override component to main
libemail-simple-perl 2.218-1 in noble: universe/perl -> main
Full stack ready, all dependencies seen in component mismatches, FFE
approved, MIR approved, only the top level change pulling this in is in
-proposed and ready there other than this mismatch -> promoting.
Override component to main
libmail-dmarc-perl 1.20230215-1ubuntu1 in noble: universe/misc
Full stack ready, all dependencies seen in component mismatches, FFE
approved, MIR approved, only the top level change pulling this in is in
-proposed and ready there other than this mismatch -> promoting.
Override component to main
libfile-sharedir-perl 1.118-3 in noble: universe/perl -> main
Full stack ready, all dependencies seen in component mismatches, FFE
approved, MIR approved, only the top level change pulling this in is in
-proposed and ready there other than this mismatch -> promoting.
Override component to main
libregexp-common-perl 2017060201-3 in noble: universe/perl ->
Full stack ready, all dependencies seen in component mismatches, FFE
approved, MIR approved, only the top level change pulling this in is in
-proposed and ready there other than this mismatch -> promoting.
Override component to main
libnet-ip-perl 1.26-3 in noble: universe/perl -> main
Full stack ready, all dependencies seen in component mismatches, FFE
approved, MIR approved, only the top level change pulling this in is in
-proposed and ready there other than this mismatch -> promoting.
Override component to main
libclass-inspector-perl 1.36-3 in noble: universe/perl -> main
The list of mismatches in proposed matches the expected set, all of
those cases are ready from the MIR and security POV. Furthermore there
is a FFE approved for the same context.
I've ensured our team subscriptions are complete (they already are) on
each of those.
After the next run of component
** Changed in: python-s3transfer (Ubuntu)
Status: New => 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/2061750
Title:
[MIR] python-s3transfer as indirect dependency of
** Changed in: python-boto3 (Ubuntu)
Status: New => 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/2061217
Title:
[MIR] python-boto3 as a dependency of simplestreams
To manage
** Changed in: python-botocore (Ubuntu)
Status: New => 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/2061751
Title:
[MIR] python-botocore as indirect dependency of
FYI this fell out of main later, re-promoted in 2024 via bug 2039456
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/243276
Title:
MIR for libnet-ip-perl
To manage notifications about this bug go
FYI this fell out of main later, re-promoted in 2024 via bug 2039569
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/522210
Title:
[MIR] libclass-inspector-perl
To manage notifications about this
The rest is ready as well and this shows up in component mismatches,
updating state
** Changed in: libnet-ip-perl (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It is and it is also in component mismatches now, updating state
** Changed in: libemail-simple-perl (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All open requests have been addressed, thank you.
It is also showing up in component mismatches with the unblocking uploads
setting the agreed changes.
Updating state
** Changed in: libfile-sharedir-perl (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification
Thanks for also ensuring an FFE.
All MIR requested modifications have been implemented, thereby this is now
ready to go and seen in component mismatches already.
Updating the state.
** Changed in: libmail-dmarc-perl (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug
Assigning to security
Please see https://bugs.launchpad.net/ubuntu/+source/python-
boto3/+bug/2061217/comments/8 for details on delayed security reviews
and why we want to accept this already.
** Changed in: python-s3transfer (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubu
Review for Source Package: python-s3transfer
[Summary]
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
List of specific binary packages to be promoted to main:
python3-s3transfer
Specific binary
To update everyone on what makes this case special, we discussed this
today in the MIR meeting [1].
While everyone would have appreciated if all of this would just have
happened 2 months ago that is not where we are right now and this isn't
complaining - in fact we thank Alberto and CPC for
Assigning to security
Please see https://bugs.launchpad.net/ubuntu/+source/python-
boto3/+bug/2061217/comments/8 for details on delayed security reviews
and why we want to accept this already.
** Changed in: python-botocore (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubu
Review for Source Package: python-botocore
[Summary]
Being developed in sync with python-boto3 this is almost a copy and paste of
the other review except small changes in a few places.
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a
b only)
Problems: None
** Changed in: python-boto3 (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20612
Needs the changes to be pulled in and a subscriber - other than that it
seems ready
** Changed in: msgraph (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python-boto3 (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061217
Title:
[MIR] python-boto3 as a depende
** Changed in: python-botocore (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061751
Title:
[MIR] python-botocore as indir
** Changed in: python-s3transfer (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061750
Title:
[MIR] python-s3trans
** Description changed:
[Availability]
The packages python-boto3, python-s3transfer and python-botocore are already
in Ubuntu universe.
The packages python-boto3, python-s3transfer and python-botocore build for
the architectures it is designed to work on.
They build amd64 only (but
FYI
Yeah, the problem is that - as so often - "it depends". There are
installations which easily work with 1GB like an x86 KVM with not many
devices.
On the other hand this isn't listed as "minimum", but as
"recommendation" and that could indeed be higher to tolerate more
install environment
** Also affects: mysql-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mysql-shell (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
"now once beta testing is over" :-)
It only just began, but yes we didn't want to disturb getting into the beta in
the first place and it is out now.
Furthermore the FFE is approved
and NEW queue review changes in place.
Furthermore this isn't seeded and thereby has no direct impact to daily
From here we found libs that are even closer, already doing EC handling.
But not yet supporting EVP which is the new high level interface via which
you'd also reach ed25519 - but this still made it much closer.
We drafted a plan how to get started on this based on that and verifying
in C (as
Oh for sure, extending something existing sounds way better than coming
up with our own from scratch.
Not only might it be easier by not doing all the first-time-mistakes, we
also do not want to be a competition to established things. We only want
to be able provide eddsa-25519 with a backend
v6 exists in Jammy, Mantic - promoting it there would be ok, although
for mantic there isn't much time left
For Noble forward we only want v8 IIUC, that seems fine as you need to
let go of the old at some point - or will that change again later?
** Changed in: dotnet6 (Ubuntu Noble)
s: New => In Progress
** Changed in: dotnet8 (Ubuntu Noble)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060056
Title:
[MIR] dotnet
While only being a basic test and you never know if someone else comes later
and says "ah in main, let us use for encoding" as well.
Just as guidance, those tests are never meant to be "you can only add the
minimum" :-)
IMHO given what the lib does it still is fine for now and the infrastructure
Nautilus Problem, möglich.
Kernel problem, halte ich für unwahrscheinlich aber nicht unmöglich.
Sicher ist allerdings das ohne Nachvollziehbare Schritte hier leider
keine weiterhelfen kann.
Ich aktualisiere den Fall dazu passend, aber ohne weitere Info wird
leider nichts mehr passieren.
P.S.
Now that things are frozen (and this isn't seeded nor depended on and
thereby should not cause further issues) the build in -updates could be
removed as well.
Removing packages from noble-updates:
ruby3.1 3.1.2-7ubuntu4 in noble
libruby3.1 3.1.2-7ubuntu4 in noble amd64
Bonus suggestion from standup: since this is hard bound to 8.0 due to
the way versions align, do we need to make the dependencies versioned?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003316
NEW Review for mysql-shell:
After a bit of back and forth in my head I've found that what confused
me at first was that it has a MYSQL_VERSION file and a similar packaging
directory. But it has not full dir copy of mysql like percona had.
# namespace
source: the namespace is good, prefix with
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003316
Title:
[FFe] Please add mysql-shell to ubuntu
To manage notifications about this bug go to:
Thanks - completed
Override component to main
pemmican 1.0.3-0ubuntu1 in noble: universe/python -> main
pemmican-common 1.0.3-0ubuntu1 in noble amd64: universe/python/optional/100% ->
main
pemmican-common 1.0.3-0ubuntu1 in noble arm64: universe/python/optional/100% ->
main
pemmican-common
This bug has lacked quite a few updates.
This is no more incomplete but waiting for a while in the new [1] queue
already.
I've checked the source and it is ok, falling victim to the same that
seems common in anything mysql (percona as well for example, accepted by
Steve in the past and a while
** Summary changed:
- [FFe] [needs-packaging] Please add mysql-shell to ubuntu
+ [FFe] Please add mysql-shell to ubuntu
** Changed in: ubuntu
Assignee: Lena Voytek (lvoytek) => (unassigned)
** Changed in: ubuntu
Importance: Wishlist => High
** Changed in: ubuntu
Status: In
pemmican-common is needed by the two now seeded pemmican-desktop and
pemmican-server
pemmican-doc is auto-included and has only safe dependencies (all in
main) and therefore can be promoted as well.
All looks well, but the team subscription wasn't added before.
Should be OK to go once that is
We landed the seed change in
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-
seeds/+merge/463674
** Changed in: pemmican (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
You'd wonder about freezer itself which is part of the Debian removal
request, but that was handled a while ago already based on the same
Debian bug.
See:
Removal requested on 2024-02-28.
Deleted on 2024-02-28 by Steve Langasek
(From Debian) ROM; unmaintained; Debian bug #1063850
For
Doesn't this also need the one in -updates and -proposed to be moved to
main or it might later fall out of it again when the universe version
migrates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for the check and explanation.
While that is sad for size (80m vs 20m) it makes sense for the purpose.
And this isn't in minimal so it seems sort of ok to me.
Trying to unblock things this seems ready now.
** Changed in: bpfcc (Ubuntu)
Status: Incomplete => In Progress
**
[18:20] vorlon: I saw on
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2052809 you only
promoted -release, but the versions not -updates and -proposed. Would those not
also be needed to not set back the component when it migrates?
[18:20] cpaelzer: -proposed yes, -updates will be
Dependency is shown in mismatches, setting to Fix Committed.
I thought in the current situation we'd need to promote all (-release,
-updates, -proposed), but on bpftrace only -release was moved. Let me
check on that before that might interfere with the current archive
activities.
If anyone else
Clarified, moving -release and -proposed as -updates will be deleted
anyway
Also libbpfcc-dev is an auto-include and has no weird dependencies that
make us need to exclude it.
Override component to main
bpfcc 0.29.1+ds-1ubuntu4 in noble: universe/misc -> main
Override [y|N]? y
1 publication
Thank you for the security review, most of the other open requests are
still open AFAICS (we said in the team meeting that we wanted to re-
check all cases):
Required:
1. Other dependies to MIR:
WIP a. libtracefs -
https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2051925
DONE b.
Thank you for adding all the QA and clarifying more.
When you change dependencies to pull this in (I see Ubuntu-meta already
did change).
This is trying to get the value to the users, but not clutter where possible.
I think we should depend on libbpf-tools instead of the current bpfcc-tools.
I'll not mark it "in progress" yet waiting for the "which -tools" to use.
But it would be ready once you settled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052813
Title:
[MIR] bpfcc
To manage
Thank you Dominik, yes - by that it seems complete now.
Ready for you to change seeds to pull it into main.
** Changed in: dotnet6 (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you, this IMHO is ready then once dependencies are as well
** Changed in: bpftrace (Ubuntu)
Status: Incomplete => 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/2052809
After double checking that we are indeed not (yet) in the freeze I think
it would help to clear that now.
Removing packages from noble-proposed:
ruby3.1 3.1.2-7ubuntu6 in noble
libruby3.1 3.1.2-7ubuntu6 in noble amd64
libruby3.1 3.1.2-7ubuntu6 in noble i386
Interestingly there are three (3) in noble right now:
ruby3.1 | 3.1.2-7ubuntu4 | noble-updates/universe | source, amd64, arm64,
armhf, i386, ppc64el, riscv64, s390x
ruby3.1 | 3.1.2-7ubuntu5 | noble/universe | source, arm64, armhf,
i386, ppc64el, riscv64, s390x
ruby3.1 |
I confirmed that there is no dependency left.
At the same time ruby3.2 is indeed in main and the dependency for all ruby
components.
** Changed in: ruby3.1 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
While the above is needed to change chrony, I further found that
timemaster also has an issue in the default config.
debian/timemaster.conf:14:[chrony.conf]
debian/timemaster.conf:15:include /etc/chrony.conf
That causes the default to behave like:
Mar 22 07:03:49 n chronyd[50428]: Fatal error :
Thanks for the ping on this @ahresse !
Yes, this should be very similar to thew old fix in bug 1771028
It is essentially yet another "chrony works with something else" use case.
There is a section for that in the chrony apparmor rules and we should indeed
add the known default paths (like this)
James did all the uploads AFAIK, once they are all in proposed or
migrated things can be pro-/dem-moted. Changing states accordingly to
reflect that this is ready.
** Changed in: platformdirs (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: platformd
Review for Source Package: platformdirs
This goes a bit of an unusual way ...
[Rationale, Duplication and Ownership]
First of all, what does platformdirs do, according to its description
and interfaces:
Depending on your system (Linux, Mac OS X, or Windows), you have to use
different
Hi,
thank you for filing - but we feel this is a bit immature to already get MIR
approval already.
This should go through normal review & sponsorship into multiverse
first, to give us a chance to see it in action and trigger concerns and
tests in the real place.
It is also rushed as it is late
1 - 100 of 10003 matches
Mail list logo
