** Changed in: ssl-cert (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069330
Title:
make-ssl-cert:
** Changed in: net-snmp (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
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/720638
Title:
snmpd crashes with segfault (libnets
Thank you that satisfies the test case, a few more day of maturing.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
FYI: Uploaded by Lucas but atm stuck in proposed for networking issues
in the test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065423
Title:
Update AppArmor template to allow confined runc to kil
That is awesome, thanks Vincent.
We will pick it up in the subsequent merge of chrony then.
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068526
Title:
apparmor blocks
Sadly the backport seems to be complex per Andreas evaluation.
It is fixed in Noble onwards and the symptom is "only" false positive
notifications.
As-is this seems not to be feasible effort to fix it in Jammy and before.
If someone has a great approach to tackle this more easily we are open to
There are several places in test-logprof.py with a 0.3s timeout. Can you
please show the detailed error message to make it clear where we need a
longer timeout?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Bug watch added: Debian Bug tracker #1071456
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071456
** Changed in: autopkgtest (Debian)
Status: Fix Committed => Unknown
** Changed in: autopkgtest (Debian)
Remote watch: Debian Bug tracker #1068363 => Debian Bug tracker #1071456
-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
To manage notifications about this bug go to:
https://bugs.launchpad
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045297
Title:
file root.hints needs update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Fully complete in Oracular now and DPDK/OVS migrated together
https://launchpad.net/ubuntu/+source/dpdk/23.11.1-1
@Frode - will you prepare an OVS 3.3.1 for Noble so we can do the DPDK
stable update afterwards?
** Also affects: openvswitch (Ubuntu Noble)
Importance: Undecided
Status: Ne
missison.
The only drawback is that therefore the attack severity (if there is one)
is higher.
Gladly for the most likely attack surface (manipulated profile data) there
is no elevated permission needed (that is only for profiling)
** Changed in: sysprof (Ubuntu)
Assignee: Chr
Sorry it took so long from the assignment last week, finally started on this
MIR review.
If I can't complete I'd at least leave you what I found until then so you can
act on these.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
New OVS is in Oracular
https://launchpad.net/ubuntu/+source/openvswitch/3.3.1-1
Some tests already were happy in old runs, ppc64 and arm64 have not run the way
they need to.
I've triggered them with the new DPDK and the new OVS together.
Unless some other, formerly masked, test issue affects t
We found a different solution that fixes even more.
Included as:
commit cc99622485062b902362ffa3a08317dc0f926164
Author: David Marchand
Date: Thu Jun 6 15:11:11 2024 +0200
system-dpdk: Fix socket conflict when starting testpmd.
Which is in upstream stable update v3.3.1
Frode will as usua
oops same issue in 3.4.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059953
Title:
MAAS machine commissioning fails in "20-dhcp-unconfigured-ifaces "
To manage notifications about this bug go to
I have the exact same issue with 3.6 but only when commissioning with
24.04 (noble).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059953
Title:
MAAS machine commissioning fails in "20-dhcp-unconfi
Submitted for upstream discussion:
https://mail.openvswitch.org/pipermail/ovs-dev/2024-June/414484.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067889
Title:
DPDK 23.11.1 / OVS 3.3.0 cause te
Thanks to m4 expansion I had to change it in tests/system-dpdk-testsuite for
retesting.
The real fix would be in ./tests/system-dpdk-macros.at though.
Adding the following to the rules made it work:
/TELEMETRY: Socket write base info to client failed/d
Now the questions is "is this a warning t
With what I know from comment #14 and comment #5 I tried to get deeper
to finally find what actually goes wrong which still eludes me :-/
Env vars that we need:
OVS_RUNDIR=/var/run/openvswitch/
abs_top_srcdir=../_debian/openvswitch/
1. db creation + starting ovsdb with --detach in background +
I checked with my peers and it seems this happens indeed to almost
everyone. The only exceptions are thos that diabled the assistant or not
using gnome in the first place.
@Jorrit
I agree, the folks I checked had various other GPUs - all affected AFAICS.
@Jon
Just like you I usually use just supe
** Changed in: libdex (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: libdex (Ubuntu)
Assignee: Lukas Märdian (slyon) => Ioanna Alifieraki (joalif)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Changed in: libpanel (Ubuntu)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
** Changed in: libpanel (Ubuntu)
Assignee: Ioanna Alifieraki (joalif) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: sysprof (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/2066269
Title:
[MIR] sysprof
To manage notificati
Here the differences I spot on a high level:
4. OVS-DPDK - ping vhost-user ports
- testpmd.log - not much difference
- ovsdb-server.log
ovsdb-server is killed (sig 15) in the bad case 7 seconds after starting
that kill is after the test log ends, so it could be cleanup
- ovs-vswitchd.log
** Attachment added: "Test results on 23.11.1"
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785828/+files/bad-case.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "Test results on 23.11"
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785827/+files/good-case.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
After the setup outlined above I was running the set the autopkgtest identified
(4-5 16-17 20-21
). With that I was able to trigger good/bad case in a reproducible way.
In my repro-environment, test 5 also fails in the good case - which
might just be my test environment's fault. Hence I'm compari
"
As I think creation of intiramfs is part of the distro I address this here.
Please let me know when I am wrong.
Kind regards
Christian Rusa
** Affects: mandos (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Directly running just the failing test (of the 6 I picked the MTU upper
bound that I analyzed above) works like this:
# WIP
apt install ubuntu-dev-tools conntrack curl devscripts dpdk-dev ethtool equivs
net-tools ncat python3-pyftpdlib tcpdump wget
apt-get remove --yes --purge netcat-openbsd
ln
The log message I have seen might be a red herring as well [1] added
that but unless something insists on "non-ERR" that should not be the
reason as it is not changing behavior.
But then, what else am I looking for, Frode confirmed that he will do
some triage and debug from the OVS POV which might
Frode mentioned that OVS 3.3.1 might get some bonus love in regard to DPDK
23.11.1 [1].
In the past that was only ever needed for new features, which the stable update
does not have, but there is a chance that this is just a test bug I do not yet
understand fully - so yeah, giving this a look wi
** Attachment added: "ovs-vswitchd-bad-23.11.1-1.log"
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785493/+files/ovs-vswitchd-bad-23.11.1-1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Attachment added: "ovs-vswitchd-good-23.11-1.log"
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785494/+files/ovs-vswitchd-good-23.11-1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Attachment added: "just the log section of the failures"
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785468/+files/dpdk-ovs-test-fail-log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
The only very unique entry I got here in those logs of the dpdk enabled
openvswitch in the bad case was:
1|dpdk|ERR|TELEMETRY: Socket write base info to client failed
Not sure where to go with that, is that from the switch or the client even?
I might need to reach out if there are any known i
23.11.1-1 console output
root@o-dpdk-ovs:~# systemctl stop openvswitch-switch ovs-vswitchd
root@o-dpdk-ovs:~# rm /var/log/openvswitch/ovs-vswitchd.log
root@o-dpdk-ovs:~# systemctl start openvswitch-switch ovs-vswitchd
root@o-dpdk-ovs:~# ovs-vsctl show
9a966e25-a911-45d1-a5ad-1beeb7c142a1
ovs_v
From here I was capturing full logs of this with DPDK 23.11-1 and
23.11.1-1
23.11-1 console output:
root@o-dpdk-ovs:~# systemctl stop openvswitch-switch ovs-vswitchd
root@o-dpdk-ovs:~# rm /var/log/openvswitch/ovs-vswitchd.log
root@o-dpdk-ovs:~# systemctl start openvswitch-switch ovs-vswitchd
roo
Trying to isolate the commands used in the failing test (works in a not
too small Oracular VM):
0. Prep install and config
apt install openvswitch-switch-dpdk dpdk-dev
echo "NR_2M_PAGES=784" >> /etc/dpdk/dpdk.conf
systemctl restart dpdk
update-alternatives --set ovs-vswitchd
/usr/lib/openvswi
Again, is that the root cause or a symptom of a former failure?
Not all tests are very clear in that regard, but one I liked.
As it fails BEFORE this cleanup phase.
The "MTU upper bound vport port" test is like this:
> 2024-05-31T10:08:28.364Z|00117|netdev_dpdk|WARN|dpdkvhostuserclient0:
> unsup
After that one knows which sub-log to check, for ease of consumption
I've attached the subsection here that talks about the actually failing tests.
Fail #1
/tmpdir/_debian/tests/system-dpdk-testsuite.dir/004/cleanup: line 1: kill:
(275003) - No such process
4. system-dpdk.at:102: 4. OVS-DPDK - pi
One has to realize, even the good path hits the cleanup function, but entered
with rc=0. It then cleans up and exits with the RC it got.
The bad case OTOH seems to do parts of the cleanup function, but not all of it.
It ends the tests, with more successful tests (151) but then enters cleanup
with
Oracular OVS bad test with DPDK 23.11.1-1
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/o/openvswitch/20240531_100906_6f957@/log.gz
5047s 151 tests were successful.
5047s 36 tests were skipped.
5047s + update-alternatives --set ovs-vswitchd
/usr/lib/openvswitch-switch
Public bug reported:
https://autopkgtest.ubuntu.com/packages/o/openvswitch/oracular/amd64
Bad
Oracular OVS test with DPDK 23.11.1-1
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/o/openvswitch/20240531_100906_6f957@/log.gz
Good
Oracular OVS test with DPDK 23.11-1
http
in-progress" to match that.
** Changed in: malcontent (Ubuntu)
Status: New => In Progress
** Changed in: malcontent (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: malcontent (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/1892456
Title:
[MIR] malcontent
To man
** Changed in: provd (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067373
Title:
[MIR] provd
To manage notifications about this bug go
I found the change that caused this regression.
Reported upstream:
https://gitlab.freedesktop.org/drm/nouveau/-/issues/362
** Bug watch added: gitlab.freedesktop.org/drm/nouveau/-/issues #362
https://gitlab.freedesktop.org/drm/nouveau/-/issues/362
--
You received this bug notification becau
** Summary changed:
- Jammy to Noble upgrade lost pivate use area Ubuntu symbol
+ Jammy to Noble upgrade lost private use area Ubuntu symbol
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064576
Titl
The Debian ROCm Team has also seen this in their CI instance. One data
point that might be relevant is that in our case, all our failures were
limited to autopkgtests where there was a reboot between tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I'm afraid apparmor_parser is not fully aware of this restriction.
# cat foo
/usr/bin/foo {
# mount options=(rw, runbindable) / -> /bar, # causes error
mount options=(rw, runbindable) -> /bar, # accepted as valid (as
expected)
mount options=(rw, runbindable) /, # acce
I found that I can install the docker-compose-v2 package (it's in
universe), and then use "docker compose", instead of "docker-compose".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056735
Title:
Public bug reported:
$ grep ^Pr /etc/update-manager/release-upgrades
Prompt=normal
$ sudo do-release-upgrade
[...]
Checking package manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating the changes
Calculating the changes
Could not
Just as @seb128 said in
https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/1993634/comments/5 the GUI part is what is currently
missing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "TestPrivateAreaUbuntuFont.html"
https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+attachment/5774009/+files/TestPrivateAreaUbuntuFont.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Attachment added: "ubuntu-unicode-was-set-jammy.png"
https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+attachment/5774008/+files/ubuntu-unicode-was-set-jammy.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "table-noble.png"
https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+attachment/5774007/+files/table-noble.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
** Attachment added: "ubuntu-unicode-nowFF.png"
https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+attachment/5774005/+files/ubuntu-unicode-nowFF.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Attachment added: "ubuntu-unicode-nowChrome.png"
https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+attachment/5774006/+files/ubuntu-unicode-nowChrome.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Public bug reported:
Hi,
with the Noble upgrade I'm missing the Ubuntu Unicode symbol.
I thought it might have been my setup, but I now have confirmation from 1 other
Noble and 1 other Mantic user that it is missing - while I checked and on Jammy
it is still present as of now.
To re-check you w
Thanks for the great debug work so far already, I think it is "apparmor
or kernel" enough that we should add those packages and subscribe a few
folks we know dealing with those details - I'd start with jjohansen as
he'd be the best to map us to either knowledge or a known case.
** Also affects: ap
Thank you all,
with that I sum up the details here.
- MIR ack with a few requirements
- Security Ack
- From here
1. add the tests you mentioned to the package
2. continue to !try! isolation (2058040)
3. ready for promotion in 24.10
4. SRU the tests to 24.04
5. we consider this even ok to
Hi Jeremy
> I do not understand why bugs like this cannot get fixed even years after
> several people have reported the same issue and the repro steps are clear
I understand this might seem frustrating, but the TL;DR is: Because it
isn't as clear as it might seem
Detail:
As you see throughout t
FYI: Upstream delayed the release of 23.11.1 and therefore this can't be
part of this round of backports. It will be part of the next.
** Changed in: dpdk (Ubuntu Noble)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "/var/log/dist-upgrade/apt.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063360/+attachment/5770091/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
Trying to upgrade from 22.04.4 to 24.04:
$ do-release-upgrade -d
Checking for a new Ubuntu release
= Welcome to Ubuntu 24.04 LTS 'Noble Numbat' =
[...]
Checking package manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Public bug reported:
On Focal, Vagrant cannot connect to a new VM I tried to create (using
debian/bookworm64).
`vagrant up my-bookworm-vm` keeps repeating:
"Warning: Authentication failure. Retrying..."
`vagrant ssh my-bookworm-vm` however works!
The reason is that public-key authentication fa
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 is
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
m
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
lib
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
- T
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 b
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 b
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 it
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 it
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 | 6.
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
d
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 man
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 to
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.
https://bugs.launchpad.net/bugs/20600
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
r
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:
https://code.launchpad.net/~paelzer/ubuntu/+source/strace/+git/strace/+merge/464606
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 SIZEOF_KERNEL_L
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 -> u
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% -> mai
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
p
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 d
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:
universe/python/optio
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. Bu
[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]:
https://launchpadlibrarian.net/725
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 armhf:
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 1:1.8.2
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 a
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 in
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 didn't
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 did
201 - 300 of 7525 matches
Mail list logo
