[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
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 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.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065685] Re: aa-logprof fails with 'runbindable' error
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) /, # accepted as valid, but shouldn't
}
# apparmor_parser -r foo
#
This means a rule with only a source (but no target mountpoint) gets
accepted by the parser and loaded into the kernel, even if it should
raise an error.
.
BTW: The commented-out rule that indeed triggers an error results in a
not-so-useful error message:
Encoding of mount rule failed
ERROR processing policydb rules for profile /usr/bin/foo, failed to load
A more detailed error message that points out the invalid rule would be
nice.
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065685
Title:
aa-logprof fails with 'runbindable' error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056735] Re: docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked'
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: docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/2056735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065608] [NEW] An unresolvable problem occurred while calculating the upgrade
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 calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Mon May 13 17:51:20 2024 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-05-13 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2024-05-13T16:47:29.516789 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065608 Title: An unresolvable problem occurred while calculating the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1993634] Re: network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no option to set suggested --data-ciphers flag instead
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/bugs/1993634 Title: network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no option to set suggested --data-ciphers flag instead To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1993634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064576] Re: Jammy to Noble upgrade lost pivate use area Ubuntu symbol
** 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. https://bugs.launchpad.net/bugs/2064576 Title: Jammy to Noble upgrade lost pivate use area Ubuntu symbol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064576] Re: Jammy to Noble upgrade lost pivate use area Ubuntu symbol
** 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. https://bugs.launchpad.net/bugs/2064576 Title: Jammy to Noble upgrade lost pivate use area Ubuntu symbol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064576] Re: Jammy to Noble upgrade lost pivate use area Ubuntu symbol
** 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/2064576 Title: Jammy to Noble upgrade lost pivate use area Ubuntu symbol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064576] Re: Jammy to Noble upgrade lost pivate use area Ubuntu symbol
** 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.launchpad.net/bugs/2064576 Title: Jammy to Noble upgrade lost pivate use area Ubuntu symbol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064576] Re: Jammy to Noble upgrade lost pivate use area Ubuntu symbol
** 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://bugs.launchpad.net/bugs/2064576 Title: Jammy to Noble upgrade lost pivate use area Ubuntu symbol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064576] [NEW] Jammy to Noble upgrade lost pivate use area Ubuntu symbol
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 want to see F0E0-1F in a ubuntu font for example via 1. go to http://www.tamasoft.co.jp/en/general-info/unicode.html 2. scroll to the line starting with F0E0 3. go into the browsers debugger and change the style to font-family: Ubuntu, "times new roman", times, roman, serif; 4. You will see the symbol in the last column I'll attach a few images showing the problem in Noble as of now. 1. a view of this in Firefox on Noble "ubuntu-unicode-nowFF.png" 2. a view of this in Chrome on Noble "ubuntu-unicode-nowChrome.png" 3. a view of the stripped down table as attached "TestPrivateAreaUbuntuFont.html" rendered as "table-noble.png" And for comparison: 4. the same table line rendered on Jammy with the Ubuntu symbol present in the last column "ubuntu-unicode-was-set-jammy.png" This was using https://en.wikipedia.org/wiki/Private_Use_Areas as discussed in e.g. https://askubuntu.com/questions/144379/ubuntu-logo-into-unicode-table. That is why you'd only see it in the Ubuntu font - which is fine, but why was it lost there? AFAICS the changelog of the package had no mention of this being dropped intentionally. But it had a few "New upstream version", yet checking that was not insightful either to decide if that was intentional. In fact all that 0.869 I can't really track down (0.84 is in development), but that might be my lack of knowing this particular project. P.S. This might have been an intentional change, in that case the bug might still serve as a place to find that information for others. ** Affects: fonts-ubuntu (Ubuntu) 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/2064576 Title: Jammy to Noble upgrade lost pivate use area Ubuntu symbol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2064576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
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: apparmor (Ubuntu) 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/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054480] Re: [MIR] nbd-client
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 promote for 24.04.1 Subscribing Dave to continue on that ** Changed in: nbd (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054480 Title: [MIR] nbd-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: systemd breaks due to old libsecomp libs left on the system
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 the discussions many have tried to recreate it with those steps but it was not triggering for further debugging. Just to be sure I did try to recreate again in a new clean system (this time direct upgrades, no do-release-upgrade) upgrading X-B-F => no issues. I also rechecked the libseccomp.so files - always had only those belonging to the current installed version. As you can see the open question is either: a) find the details to the steps to really recreate this or b) finding out where the older files came from as they have in none of the case been part of the system that was upgraded from but from somewhere further in the past. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: systemd breaks due to old libsecomp libs left on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040463] Re: MRE updates of dpdk in the 24.04 cycle
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040463 Title: MRE updates of dpdk in the 24.04 cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063360] Re: Could not calculate the upgrade
** 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.launchpad.net/bugs/2063360 Title: Could not calculate the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063360] [NEW] Could not calculate the upgrade
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 Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was caused by: * Upgrading to a pre-release version of Ubuntu This is most likely a transient problem, please try again later. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Wed Apr 24 19:28:06 2024 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-04-24 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy ** Attachment added: "/var/log/dist-upgrade/main.log" https://bugs.launchpad.net/bugs/2063360/+attachment/5770081/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063360 Title: Could not calculate the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063339] [NEW] `vagrant up` fails to connect to VM via SSH
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 fails when Vagrant uses ruby-net-ssh internally (it works with /usr/bin/ssh, which `vagrant ssh` is just a wrapper for). The affected versions are: vagrant: 2.2.6+dfsg-2ubuntu3 ruby-net-ssh: 1:5.2.0-1 I installed ruby-net-ssh version 1:7.2.0-1 from Mantic, which fixed the issue. ** Affects: vagrant (Ubuntu) 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/2063339 Title: `vagrant up` fails to connect to VM via SSH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/2063339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
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 not only per service via `struct
UnitStatusInfo`,
but also globally across all services via `struct Manager`.
Snapd's way to enable its mount unit sets that global state and
therefore either needs to change how it enables units or run
a daemon-reload afterwards just like most .deb package installs do.
Details:
First we need to be careful, there are two ambiguous paths here that
can trigger the same message:
a) on service start
start_unit_one
-> if (need_daemon_reload(bus, name) > 0)
-> warn_unit_file_changed(name);
This is a function:
int need_daemon_reload(sd_bus *bus, const char *unit)
It will call out via dbus asking for the attribute NeedDaemonReload
b) on service status
print_status_info
-> if (i->need_daemon_reload)
-> warn_unit_file_changed(i->id);
Also for storage, there are two:
c) `struct Manager` containing `unit_file_state_outdated` which is a global
state for all units in that manager
d) Each `struct UnitStatusInfo` has a field `need_daemon_reload` (yes just
named like the function above) that can flag this per unit.
And (a) isn't even per service.
The value of that can be fetched per service via dbus like:
$ dbus-send --system --print-reply --dest="org.freedesktop.systemd1"
"/org/freedesktop/systemd1/unit/hello_2eservice"
"org.freedesktop.DBus.Properties.Get" "string:org.freedesktop.systemd1.Unit"
"string:NeedDaemonReload"
method return time=1713787033.411485 sender=:1.3 -> destination=:1.19
serial=3833 reply_serial=2
variant boolean false
And the same can be fetched via `systemctl show` as well:
root@test:~# systemctl show hello | grep '^NeedDaemonReload'
NeedDaemonReload=yes
With the above in mind we can see that installing snapd renders ALL of them
as outdated. It was spotted with pro, reproduced with a simple example
and if you check the system it is all of them.
root@test:~# for u in $(systemctl list-units --output json | jq '.[].unit' | tr
-d '"'); do systemctl show $u | grep '^NeedDaemonReload'; done 2>/dev/null |
uniq -c
143 NeedDaemonReload=no
root@test:~# snap install snapd
2024-04-22T12:44:50Z INFO Waiting for automatic snapd restart...
snapd 2.62 from Canonical✓ installed
root@test:~# for u in $(systemctl list-units --output json | jq '.[].unit' | tr
-d '"'); do systemctl show $u | grep '^NeedDaemonReload'; done 2>/dev/null |
uniq -c
144 NeedDaemonReload=yes
Still the question is, which of the two data points is it switching?
It could be the global setting, but as well iterating and setting it per
service.
I found that the global state could get changed in src/core/dbus-manager.c
in very similarly named methods:
- method_add_dependency_unit_files
- method_preset_all_unit_files
- method_revert_unit_files
- method_disable_unit_files_generic
- method_preset_unit_files_with_mode
- method_enable_unit_files_generic
All of them do eventually the same:
m->unit_file_state_outdated = m->unit_file_state_outdated || n_changes > 0;
So it keeps the state or has n_changes applied and then sets it to true.
With GDB I found it happening in `method_enable_unit_files_generic`
of "snap-snapd-21465.mount":
2523r = call(m->runtime_scope, flags, NULL, l, ,
_changes);
2524m->unit_file_state_outdated = m->unit_file_state_outdated ||
n_changes > 0; /* See comments for this variable in manager.h */
(gdb) p m->unit_file_state_outdated
$1 = false
(gdb) n
2525if (r < 0)
(gdb) p m->unit_file_state_outdated
$2 = true
(gdb) p n_changes
$3 = 2
(gdb) p *l
$4 = 0x562ccfe389a0 "snap-snapd-21465.mount"
That "call" reference is in this case:
$1 = {int (RuntimeScope, UnitFileFlags, const char *, char **,
InstallChange **, size_t *)}
0x7e2b6d34dd00
So the way snapd enabled its unit sets the global "out of date" state
for all things. I'm not challenging that, but like package postinst
it means snapd should run the implied daemon-reload to get back to
a stable state- WDYT?
I had a hard time tracking that down, to enter gdb in a somewhat helpful
state you might want to start with these saved breakpoints
root@test:~# cat sd.brk
break ../src/core/dbus-manager.c:2524
commands
printf "Path %s nchanges %ld\n", *l, n_changes
cont
end
break ../src/core/dbus-manager.c:2597
commands
printf "Path %s nchanges %ld\n", *l, n_changes
cont
end
break ../src/core/dbus-manager.c:2651
commands
printf "Path %s nchanges %ld\n", *l, n_changes
cont
end
break ../src/core/dbus-manager.c:2694
commands
printf "Path %s nchanges %ld\n", *l, n_changes
cont
end
break ../src/core/dbus-manager.c:2767
commands
printf "Path %s nchanges %ld\n", *l, n_changes
[Bug 2060035] Re: [MIR] msgraph
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 msgraph | 0.2.1-0ubuntu3 | noble/universe | source Override component to main msgraph 0.2.1-0ubuntu3 in noble: universe/libs -> main Override [y|N]? y 1 publication overridden. Override component to main gir1.2-msg-0 0.2.1-0ubuntu3 in noble amd64: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble arm64: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble armhf: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble i386: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble ppc64el: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble riscv64: universe/introspection/optional/100% -> main gir1.2-msg-0 0.2.1-0ubuntu3 in noble s390x: universe/introspection/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble amd64: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble arm64: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble armhf: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble i386: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble ppc64el: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble riscv64: universe/libs/optional/100% -> main libmsgraph-0-1 0.2.1-0ubuntu3 in noble s390x: universe/libs/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble amd64: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble arm64: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble armhf: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble i386: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble ppc64el: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble riscv64: universe/doc/optional/100% -> main libmsgraph-doc 0.2.1-0ubuntu3 in noble s390x: universe/doc/optional/100% -> main Override [y|N]? y 21 publications overridden. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=d5078daf38e46b458c2d308ae86f6b9630c50102 [2]: https://launchpad.net/ubuntu/+source/gvfs/1.54.0-1ubuntu1 ** Changed in: msgraph (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/2060035 Title: [MIR] msgraph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msgraph/+bug/2060035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004442] Re: [MIR] aom (dependency of libheif)
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 amd64: universe/libs/optional/100% -> main libaom3 3.8.2-2build1 in noble arm64: universe/libs/optional/100% -> main libaom3 3.8.2-2build1 in noble armhf: universe/libs/optional/100% -> main libaom3 3.8.2-2build1 in noble i386: universe/libs/optional/100% -> main libaom3 3.8.2-2build1 in noble ppc64el: universe/libs/optional/100% -> main libaom3 3.8.2-2build1 in noble riscv64: universe/libs/optional/100% -> main libaom3 3.8.2-2build1 in noble s390x: universe/libs/optional/100% -> main Override [y|N]? y 7 publications overridden. ** Changed in: aom (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/2004442 Title: [MIR] aom (dependency of libheif) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aom/+bug/2004442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004449] Re: [MIR] libde265 (dependency of libheif)
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 1.0.15-1build3 in noble amd64: universe/libs/optional/100% -> main libde265-0 1.0.15-1build3 in noble arm64: universe/libs/optional/100% -> main libde265-0 1.0.15-1build3 in noble armhf: universe/libs/optional/100% -> main libde265-0 1.0.15-1build3 in noble i386: universe/libs/optional/100% -> main libde265-0 1.0.15-1build3 in noble ppc64el: universe/libs/optional/100% -> main libde265-0 1.0.15-1build3 in noble riscv64: universe/libs/optional/100% -> main libde265-0 1.0.15-1build3 in noble s390x: universe/libs/optional/100% -> main Override [y|N]? y 7 publications overridden. ** Changed in: libde265 (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/2004449 Title: [MIR] libde265 (dependency of libheif) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libde265/+bug/2004449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827442] Re: [MIR] libheif
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 libheif 1.17.6-1ubuntu4 in noble: universe/misc -> main Override [y|N]? y 1 publication overridden. Override component to main heif-gdk-pixbuf 1.17.6-1ubuntu4 in noble amd64: universe/graphics/optional/100% -> main heif-gdk-pixbuf 1.17.6-1ubuntu4 in noble arm64: universe/graphics/optional/100% -> main heif-gdk-pixbuf 1.17.6-1ubuntu4 in noble armhf: universe/graphics/optional/100% -> main heif-gdk-pixbuf 1.17.6-1ubuntu4 in noble i386: universe/graphics/optional/100% -> main heif-gdk-pixbuf 1.17.6-1ubuntu4 in noble ppc64el: universe/graphics/optional/100% -> main heif-gdk-pixbuf 1.17.6-1ubuntu4 in noble riscv64: universe/graphics/optional/100% -> main heif-gdk-pixbuf 1.17.6-1ubuntu4 in noble s390x: universe/graphics/optional/100% -> main heif-thumbnailer 1.17.6-1ubuntu4 in noble amd64: universe/graphics/optional/100% -> main heif-thumbnailer 1.17.6-1ubuntu4 in noble arm64: universe/graphics/optional/100% -> main heif-thumbnailer 1.17.6-1ubuntu4 in noble armhf: universe/graphics/optional/100% -> main heif-thumbnailer 1.17.6-1ubuntu4 in noble i386: universe/graphics/optional/100% -> main heif-thumbnailer 1.17.6-1ubuntu4 in noble ppc64el: universe/graphics/optional/100% -> main heif-thumbnailer 1.17.6-1ubuntu4 in noble riscv64: universe/graphics/optional/100% -> main heif-thumbnailer 1.17.6-1ubuntu4 in noble s390x: universe/graphics/optional/100% -> main libheif-examples 1.17.6-1ubuntu4 in noble amd64: universe/video/optional/100% -> main libheif-examples 1.17.6-1ubuntu4 in noble arm64: universe/video/optional/100% -> main libheif-examples 1.17.6-1ubuntu4 in noble armhf: universe/video/optional/100% -> main libheif-examples 1.17.6-1ubuntu4 in noble i386: universe/video/optional/100% -> main libheif-examples 1.17.6-1ubuntu4 in noble ppc64el: universe/video/optional/100% -> main libheif-examples 1.17.6-1ubuntu4 in noble riscv64: universe/video/optional/100% -> main libheif-examples 1.17.6-1ubuntu4 in noble s390x: universe/video/optional/100% -> main libheif-plugin-aomdec 1.17.6-1ubuntu4 in noble amd64: universe/libs/optional/100% -> main libheif-plugin-aomdec 1.17.6-1ubuntu4 in noble arm64: universe/libs/optional/100% -> main libheif-plugin-aomdec 1.17.6-1ubuntu4 in noble armhf: universe/libs/optional/100% -> main libheif-plugin-aomdec 1.17.6-1ubuntu4 in noble i386: universe/libs/optional/100% -> main libheif-plugin-aomdec 1.17.6-1ubuntu4 in noble ppc64el: universe/libs/optional/100% -> main libheif-plugin-aomdec 1.17.6-1ubuntu4 in noble riscv64: universe/libs/optional/100% -> main libheif-plugin-aomdec 1.17.6-1ubuntu4 in noble s390x: universe/libs/optional/100% -> main libheif-plugin-aomenc 1.17.6-1ubuntu4 in noble amd64: universe/libs/optional/100% -> main libheif-plugin-aomenc 1.17.6-1ubuntu4 in noble arm64: universe/libs/optional/100% -> main libheif-plugin-aomenc 1.17.6-1ubuntu4 in noble armhf: universe/libs/optional/100% -> main libheif-plugin-aomenc 1.17.6-1ubuntu4 in noble i386: universe/libs/optional/100% -> main libheif-plugin-aomenc 1.17.6-1ubuntu4 in noble ppc64el: universe/libs/optional/100% -> main libheif-plugin-aomenc 1.17.6-1ubuntu4 in noble riscv64: universe/libs/optional/100% -> main libheif-plugin-aomenc 1.17.6-1ubuntu4 in noble s390x: universe/libs/optional/100% -> main libheif-plugin-libde265 1.17.6-1ubuntu4 in noble amd64: universe/libs/optional/100% -> main libheif-plugin-libde265 1.17.6-1ubuntu4 in noble arm64: universe/libs/optional/100% -> main libheif-plugin-libde265 1.17.6-1ubuntu4 in noble armhf: universe/libs/optional/100% -> main libheif-plugin-libde265 1.17.6-1ubuntu4 in noble i386: universe/libs/optional/100% -> main libheif-plugin-libde265 1.17.6-1ubuntu4 in noble ppc64el: universe/libs/optional/100% -> main libheif-plugin-libde265 1.17.6-1ubuntu4 in noble riscv64: universe/libs/optional/100% -> main libheif-plugin-libde265 1.17.6-1ubuntu4 in noble s390x: universe/libs/optional/100% -> main libheif1 1.17.6-1ubuntu4 in noble amd64: universe/libs/optional/100% -> main libheif1 1.17.6-1ubuntu4 in noble arm64: universe/libs/optional/100% -> main libheif1 1.17.6-1ubuntu4 in noble armhf: universe/libs/optional/100% -> main libheif1 1.17.6-1ubuntu4 in noble i386: universe/libs/optional/100% -> main libheif1 1.17.6-1ubuntu4 in noble ppc64el: universe/libs/optional/100% -> main libheif1 1.17.6-1ubuntu4 in noble riscv64: universe/libs/optional/100% -> main libheif1 1.17.6-1ubuntu4 in noble s390x: universe/libs/optional/100% -> main Override [y|N]? y 49 publications overridden. ** Changed in: libheif (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to
[Bug 1827442] Re: [MIR] libheif
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 - The upload to pull it in happened [1] - We are in freeze, but it was accepted by bdmurray 6h ago - It built on all arches, per excuses only the mismatches hold it back - We see it in component mismatches [2] Slight twist here (libyuv 2004516, libwebm 2004523) are not needed atm. They were considered transitive dependencies and as part of the MIR the embedded code was stripped and uses the system libs instead. See "0002-use-system-libyuv.patch" and "0003-use-system-libwebm.patch" [4]. But due to that we now have proper dependency tracking and it turns out that this is only needed for aom-tools which isn't depended on - the usage of libaom3 from heif is not requiring those two. We could promote it, but if you want that you'd need to seed aom-tools in one of the -supported seeds I guess. Therefore it all seems in place including the release team moving it forward despite the freeze which implies this should move (in these days we do not want to unintentionally affect the RC) and can thereby be promoted. [1]: https://launchpad.net/ubuntu/+source/gnome-control-center/1:46.0.1-1ubuntu6 [2]: https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.svg [3]: https://launchpadlibrarian.net/722275883/buildlog_ubuntu-noble-amd64.aom_3.8.2-2build1_BUILDING.txt.gz [4]: https://launchpadlibrarian.net/722275883/buildlog_ubuntu-noble-amd64.aom_3.8.2-2build1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827442 Title: [MIR] libheif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aom/+bug/1827442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004449] Re: [MIR] libde265 (dependency of libheif)
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004449 Title: [MIR] libde265 (dependency of libheif) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libde265/+bug/2004449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004442] Re: [MIR] aom (dependency of libheif)
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004442 Title: [MIR] aom (dependency of libheif) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aom/+bug/2004442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004516] Re: [MIR] libyuv (transitive dependency of libheif)
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 is serving a good purpose) in one of the -supported seeds I guess. A bit more detail in https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442/comments/55 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004516 Title: [MIR] libyuv (transitive dependency of libheif) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libyuv/+bug/2004516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004523] Re: [MIR] libwebm (transitive dependency of libheif)[libheif -> aom -> libwebm]
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 is serving a good purpose) in one of the -supported seeds I guess. A bit more detail in https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442/comments/55 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004523 Title: [MIR] libwebm (transitive dependency of libheif)[libheif -> aom -> libwebm] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebm/+bug/2004523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023531] Re: [MIR] dotnet6
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.0.121-0ubuntu1 | mantic/universe | source, amd64, arm64 dotnet6 | 6.0.127-0ubuntu1~23.10.1 | mantic-security/universe | source, amd64, arm64 dotnet6 | 6.0.128-0ubuntu1~23.10.2 | mantic-updates/universe | source, amd64, arm64 The one in mantic-release is a bit older and misses quite some of the good work done over the last half year. On Jammy (and in general the latest push to -security) is not too old only 2 months ago. For the change that someone only uses -security I think it is fine to promote those two (but not mantic-release). That will also ensure both pockets that will be further changed are on the right component. And from here on any further upload and change will be on top of that latest version anyway. Comparing to the new releases we had no s390x support yet - ok. These older releases did not create -dbg (not -dbgsym, those are there). I found a meant to be new "Added new binary packages for debug symbols." - so that makes sense With all that confirmed it matches the dry-run preview ... Going on: Override component to main dotnet6 6.0.128-0ubuntu1~22.04.2 in jammy: universe/devel -> main aspnetcore-runtime-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-runtime-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-apphost-pack-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-apphost-pack-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-host 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-host 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-hostfxr-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-hostfxr-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-runtime-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-runtime-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-sdk-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-sdk-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-sdk-6.0-source-built-artifacts 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-sdk-6.0-source-built-artifacts 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-targeting-pack-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-targeting-pack-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-templates-6.0 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-templates-6.0 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet6 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet6 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main netstandard-targeting-pack-2.1 6.0.128-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main netstandard-targeting-pack-2.1 6.0.128-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main Override [y|N]? y 25 publications overridden. Override component to main dotnet6 6.0.127-0ubuntu1~22.04.1 in jammy: universe/devel -> main aspnetcore-runtime-6.0 6.0.127-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-runtime-6.0 6.0.127-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-6.0 6.0.127-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-6.0 6.0.127-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main dotnet-apphost-pack-6.0 6.0.127-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main dotnet-apphost-pack-6.0 6.0.127-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main dotnet-host 6.0.127-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main dotnet-host 6.0.127-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main dotnet-hostfxr-6.0 6.0.127-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main dotnet-hostfxr-6.0 6.0.127-0ubuntu1~22.04.1 in jammy arm64:
[Bug 2060056] Re: [MIR] dotnet8
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 dotnet8 | 8.0.100-8.0.0~rc1-0ubuntu1 | mantic/universe | source, amd64, arm64 dotnet8 | 8.0.103-8.0.3-0ubuntu1~23.10.1 | mantic-security/universe | source, amd64, arm64 dotnet8 | 8.0.103-8.0.3-0ubuntu1~23.10.2 | mantic-updates/universe | source, amd64, arm64 The one in mantic-release is a bit older and misses quite some of the good work done over the last half year. On Jammy (and in general the latest push to -security) is not too old only 2 months ago. For the change that someone only uses -security I think it is fine to promote those two (but not mantic-release). That will also ensure both pockets that will be further changed are on the right component. And from here on any further upload and change will be on top of that latest version anyway. Comparing to the new releases we had no s390x support yet - ok. These older releases did not create -dbg (not -dbgsym, those are there). I found a meant to be new "Added new binary packages for debug symbols." - so that makes sense With all that confirmed it matches the dry-run preview ... Going on: Override component to main dotnet8 8.0.103-8.0.3-0ubuntu1~22.04.2 in jammy: universe/devel -> main aspnetcore-runtime-8.0 8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-runtime-8.0 8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-8.0 8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-8.0 8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-apphost-pack-8.0 8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-apphost-pack-8.0 8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-host-8.0 8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-host-8.0 8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-hostfxr-8.0 8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-hostfxr-8.0 8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-runtime-8.0 8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-runtime-8.0 8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-sdk-8.0 8.0.103-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-sdk-8.0 8.0.103-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-sdk-8.0-source-built-artifacts 8.0.103-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-sdk-8.0-source-built-artifacts 8.0.103-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-targeting-pack-8.0 8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-targeting-pack-8.0 8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet-templates-8.0 8.0.103-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet-templates-8.0 8.0.103-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main dotnet8 8.0.103-8.0.3-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main dotnet8 8.0.103-8.0.3-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main netstandard-targeting-pack-2.1-8.0 8.0.103-0ubuntu1~22.04.2 in jammy amd64: universe/devel/optional/100% -> main netstandard-targeting-pack-2.1-8.0 8.0.103-0ubuntu1~22.04.2 in jammy arm64: universe/devel/optional/100% -> main Override [y|N]? y 25 publications overridden. Override component to main dotnet8 8.0.103-8.0.3-0ubuntu1~22.04.1 in jammy: universe/devel -> main aspnetcore-runtime-8.0 8.0.3-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-runtime-8.0 8.0.3-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-8.0 8.0.3-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main aspnetcore-targeting-pack-8.0 8.0.3-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main dotnet-apphost-pack-8.0 8.0.3-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main dotnet-apphost-pack-8.0 8.0.3-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main dotnet-host-8.0 8.0.3-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main dotnet-host-8.0 8.0.3-0ubuntu1~22.04.1 in jammy arm64: universe/devel/optional/100% -> main dotnet-hostfxr-8.0 8.0.3-0ubuntu1~22.04.1 in jammy amd64: universe/devel/optional/100% -> main dotnet-hostfxr-8.0 8.0.3-0ubuntu1~22.04.1
[Bug 2060805] Re: strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t
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 manage notifications about this bug go to: https://bugs.launchpad.net/strace/+bug/2060805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060805] Re: strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t
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 build it's tests on arm-linux-gnueabihf with 64bit time_t To manage notifications about this bug go to: https://bugs.launchpad.net/strace/+bug/2060805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060056] Re: [MIR] dotnet8
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/2060056 Title: [MIR] dotnet8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2060056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023531] Re: [MIR] dotnet6
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 reports run it confirms that the seed changes worked. Promoting ... [1]: https://ubuntu-archive-team.ubuntu.com/germinate- output/ubuntu.mantic/all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023531 Title: [MIR] dotnet6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060805] Re: strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/strace/+bug/2060805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060805] Re: strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t
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 -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/strace/+bug/2060805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060805] Re: strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t
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_LONG_T == 4 || defined LINUX_MIPSN32
int
# else
long long
# endif
tv_sec, tv_nsec;
} kernel_old_timespec_t;
...
The conflict now is that on 32bit that boils down to int on e.g. armhf, but
with 64 bit time_t that no more matches.
Due to that some assignments of ... (time_t) 0x1234LL can break if the static
value is exceeding int.
Many places then later changed in [2] to not use time_t anymore and now
usually make it use typeof.
But the same pattern is yet unfixed in a few more spots in the tests:
tests/mq_sendrecv.c:198: .tv_sec = (time_t) 0xdeadfacebeeff00dLL,
tests/mq_sendrecv.c:202: .tv_sec = (time_t) 0x7ea1fade7e57faceLL,
tests/recvmmsg-timeout.c:60: ts->tv_sec = (time_t) 0xcafef00ddeadbeefLL;
tests/xselect.c:216: tv_in.tv_sec = (time_t) 0xcafef00ddeadbeefLL;
tests/xutimes.c:89: tv[1].tv_sec = (time_t) 0xcafef00ddeadbeefLL;
The first of them in build is in xselect and breaks the build via
../../tests/xselect.c: In function ‘main’:
../../tests/xselect.c:216:24: error: overflow in conversion from ‘long long
int’ to ‘kernel_long_t’ {aka ‘long int’} changes value from
‘-3819351491602432273’ to ‘-559038737’ [-Werror=overflow]
216 | tv_in.tv_sec = (time_t) 0xcafef00ddeadbeefLL;
|^
Without rewriting how time is handled there, and probably failing by not
understanding enough of the intricacies of the program and the tests,
how about just applying the same fix to the other cases that are left.
Trying that as a first angle of attack ...
[1]:
https://github.com/strace/strace/commit/891ab42b7015037520a01042201d4ddc548c266d
[2]:
https://github.com/strace/strace/commit/7178658ead8ccfe196694dc5434f0f37db8746b4
--
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 manage notifications about this bug go to:
https://bugs.launchpad.net/strace/+bug/2060805/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052437] Re: python-boto: obsolete, replaced by python-boto3
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 -> universe python3-boto 2.49.0-4.1 in noble amd64: main/python/optional/100% -> universe python3-boto 2.49.0-4.1 in noble arm64: main/python/optional/100% -> universe python3-boto 2.49.0-4.1 in noble armhf: main/python/optional/100% -> universe python3-boto 2.49.0-4.1 in noble i386: main/python/optional/100% -> universe python3-boto 2.49.0-4.1 in noble ppc64el: main/python/optional/100% -> universe python3-boto 2.49.0-4.1 in noble riscv64: main/python/optional/100% -> universe python3-boto 2.49.0-4.1 in noble s390x: main/python/optional/100% -> universe Override [y|N]? y 8 publications overridden. Once simplestreams is migrating it should close this bug on the next run of proposed migration, rechecking that later. [1]: https://launchpad.net/ubuntu/+source/simplestreams/0.1.0-67-g8497b634-0ubuntu1 ** Changed in: python-boto (Ubuntu) Status: New => Fix Committed ** Changed in: simplestreams (Ubuntu) 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/2052437 Title: python-boto: obsolete, replaced by python-boto3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dask/+bug/2052437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061217] Re: [MIR] python-boto3 as a dependency of simplestreams
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% -> main python3-boto3 1.34.46+dfsg-1ubuntu1 in noble armhf: universe/python/optional/100% -> main python3-boto3 1.34.46+dfsg-1ubuntu1 in noble i386: universe/python/optional/100% -> main python3-boto3 1.34.46+dfsg-1ubuntu1 in noble ppc64el: universe/python/optional/100% -> main python3-boto3 1.34.46+dfsg-1ubuntu1 in noble riscv64: universe/python/optional/100% -> main python3-boto3 1.34.46+dfsg-1ubuntu1 in noble s390x: universe/python/optional/100% -> main Override [y|N]? y 8 publications overridden. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)
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 python3-s3transfer 0.10.1-1ubuntu2 in noble armhf: universe/python/optional/100% -> main python3-s3transfer 0.10.1-1ubuntu2 in noble i386: universe/python/optional/100% -> main python3-s3transfer 0.10.1-1ubuntu2 in noble ppc64el: universe/python/optional/100% -> main python3-s3transfer 0.10.1-1ubuntu2 in noble riscv64: universe/python/optional/100% -> main python3-s3transfer 0.10.1-1ubuntu2 in noble s390x: universe/python/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: python-s3transfer (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/2061750 Title: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)
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 dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061751] Re: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python-botocore)
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/optional/100% -> main python3-botocore 1.34.46+repack-1ubuntu1 in noble armhf: universe/python/optional/100% -> main python3-botocore 1.34.46+repack-1ubuntu1 in noble i386: universe/python/optional/100% -> main python3-botocore 1.34.46+repack-1ubuntu1 in noble ppc64el: universe/python/optional/100% -> main python3-botocore 1.34.46+repack-1ubuntu1 in noble riscv64: universe/python/optional/100% -> main python3-botocore 1.34.46+repack-1ubuntu1 in noble s390x: universe/python/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: python-botocore (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/2061751 Title: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python- botocore) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052437] Re: python-boto: obsolete, replaced by python-boto3
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. But it is actually maintained by Paride (foundations / QA) and code contributions mostly are from CPC which publish into it. Sadly this setup was begging for things top be lost in the mid of shared responsibilities. This needed a lessons learned and discussions happened, the outcome is that CPC will take over ownership in a bit (With some remaining support from Paride in the cases where it is actually about infrastructure issues). Eric has a task to work out that transfer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052437 Title: python-boto: obsolete, replaced by python-boto3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dask/+bug/2052437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)
[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/725135509/buildlog_ubuntu-noble-amd64.python-s3transfer_0.10.1-1ubuntu2_BUILDING.txt.gz -- 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 simplestreams (simplestreams -> python-boto3 -> python-s3transfer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051850] Re: [MIR] trace-cmd
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: universe/libdevel/optional/100% -> main libtracecmd-dev 3.2-1ubuntu2 in noble ppc64el: universe/libdevel/optional/100% -> main libtracecmd-dev 3.2-1ubuntu2 in noble riscv64: universe/libdevel/optional/100% -> main libtracecmd-dev 3.2-1ubuntu2 in noble s390x: universe/libdevel/optional/100% -> main libtracecmd1 3.2-1ubuntu2 in noble amd64: universe/libs/optional/100% -> main libtracecmd1 3.2-1ubuntu2 in noble arm64: universe/libs/optional/100% -> main libtracecmd1 3.2-1ubuntu2 in noble armhf: universe/libs/optional/100% -> main libtracecmd1 3.2-1ubuntu2 in noble ppc64el: universe/libs/optional/100% -> main libtracecmd1 3.2-1ubuntu2 in noble riscv64: universe/libs/optional/100% -> main libtracecmd1 3.2-1ubuntu2 in noble s390x: universe/libs/optional/100% -> main trace-cmd 3.2-1ubuntu2 in noble amd64: universe/devel/optional/100% -> main trace-cmd 3.2-1ubuntu2 in noble arm64: universe/devel/optional/100% -> main trace-cmd 3.2-1ubuntu2 in noble armhf: universe/devel/optional/100% -> main trace-cmd 3.2-1ubuntu2 in noble ppc64el: universe/devel/optional/100% -> main trace-cmd 3.2-1ubuntu2 in noble riscv64: universe/devel/optional/100% -> main trace-cmd 3.2-1ubuntu2 in noble s390x: universe/devel/optional/100% -> main Override [y|N]? y 19 publications overridden. ** Changed in: trace-cmd (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/2051850 Title: [MIR] trace-cmd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/2051850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051916] Re: [MIR] promote libtraceevent as a trace-cmd dependency
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-1ubuntu2 in noble armhf: universe/libdevel/optional/100% -> main libtraceevent-dev 1:1.8.2-1ubuntu2 in noble ppc64el: universe/libdevel/optional/100% -> main libtraceevent-dev 1:1.8.2-1ubuntu2 in noble riscv64: universe/libdevel/optional/100% -> main libtraceevent-dev 1:1.8.2-1ubuntu2 in noble s390x: universe/libdevel/optional/100% -> main libtraceevent-doc 1:1.8.2-1ubuntu2 in noble amd64: universe/doc/optional/100% -> main libtraceevent-doc 1:1.8.2-1ubuntu2 in noble arm64: universe/doc/optional/100% -> main libtraceevent-doc 1:1.8.2-1ubuntu2 in noble armhf: universe/doc/optional/100% -> main libtraceevent-doc 1:1.8.2-1ubuntu2 in noble i386: universe/doc/optional/100% -> main libtraceevent-doc 1:1.8.2-1ubuntu2 in noble ppc64el: universe/doc/optional/100% -> main libtraceevent-doc 1:1.8.2-1ubuntu2 in noble riscv64: universe/doc/optional/100% -> main libtraceevent-doc 1:1.8.2-1ubuntu2 in noble s390x: universe/doc/optional/100% -> main libtraceevent1 1:1.8.2-1ubuntu2 in noble amd64: universe/libs/optional/100% -> main libtraceevent1 1:1.8.2-1ubuntu2 in noble arm64: universe/libs/optional/100% -> main libtraceevent1 1:1.8.2-1ubuntu2 in noble armhf: universe/libs/optional/100% -> main libtraceevent1 1:1.8.2-1ubuntu2 in noble ppc64el: universe/libs/optional/100% -> main libtraceevent1 1:1.8.2-1ubuntu2 in noble riscv64: universe/libs/optional/100% -> main libtraceevent1 1:1.8.2-1ubuntu2 in noble s390x: universe/libs/optional/100% -> main libtraceevent1-plugin 1:1.8.2-1ubuntu2 in noble amd64: universe/libs/optional/100% -> main libtraceevent1-plugin 1:1.8.2-1ubuntu2 in noble arm64: universe/libs/optional/100% -> main libtraceevent1-plugin 1:1.8.2-1ubuntu2 in noble armhf: universe/libs/optional/100% -> main libtraceevent1-plugin 1:1.8.2-1ubuntu2 in noble ppc64el: universe/libs/optional/100% -> main libtraceevent1-plugin 1:1.8.2-1ubuntu2 in noble riscv64: universe/libs/optional/100% -> main libtraceevent1-plugin 1:1.8.2-1ubuntu2 in noble s390x: universe/libs/optional/100% -> main Override [y|N]? y 26 publications overridden. ** Changed in: libtraceevent (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/2051916 Title: [MIR] promote libtraceevent as a trace-cmd dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtraceevent/+bug/2051916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051925] Re: [MIR] promote libtracefs as a trace-cmd dependency
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 armhf: universe/libdevel/optional/100% -> main libtracefs-dev 1.8.0-1ubuntu1 in noble ppc64el: universe/libdevel/optional/100% -> main libtracefs-dev 1.8.0-1ubuntu1 in noble riscv64: universe/libdevel/optional/100% -> main libtracefs-dev 1.8.0-1ubuntu1 in noble s390x: universe/libdevel/optional/100% -> main libtracefs-doc 1.8.0-1ubuntu1 in noble amd64: universe/doc/optional/100% -> main libtracefs-doc 1.8.0-1ubuntu1 in noble arm64: universe/doc/optional/100% -> main libtracefs-doc 1.8.0-1ubuntu1 in noble armhf: universe/doc/optional/100% -> main libtracefs-doc 1.8.0-1ubuntu1 in noble i386: universe/doc/optional/100% -> main libtracefs-doc 1.8.0-1ubuntu1 in noble ppc64el: universe/doc/optional/100% -> main libtracefs-doc 1.8.0-1ubuntu1 in noble riscv64: universe/doc/optional/100% -> main libtracefs-doc 1.8.0-1ubuntu1 in noble s390x: universe/doc/optional/100% -> main libtracefs1 1.8.0-1ubuntu1 in noble amd64: universe/libs/optional/100% -> main libtracefs1 1.8.0-1ubuntu1 in noble arm64: universe/libs/optional/100% -> main libtracefs1 1.8.0-1ubuntu1 in noble armhf: universe/libs/optional/100% -> main libtracefs1 1.8.0-1ubuntu1 in noble ppc64el: universe/libs/optional/100% -> main libtracefs1 1.8.0-1ubuntu1 in noble riscv64: universe/libs/optional/100% -> main libtracefs1 1.8.0-1ubuntu1 in noble s390x: universe/libs/optional/100% -> main Override [y|N]? y 20 publications overridden. ** Changed in: libtracefs (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/2051925 Title: [MIR] promote libtracefs as a trace-cmd dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2051925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051925] Re: [MIR] promote libtracefs as a trace-cmd dependency
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 through the cracks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051925 Title: [MIR] promote libtracefs as a trace-cmd dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2051925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062119] Re: autopkgtests fails on ppc64el
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: libtracefs (Ubuntu) Assignee: (unassigned) => Adrien Nader (adrien-n) ** Summary changed: - autopkgtests fails on ppc64el + autopkgtests fail on ppc64el -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062119 Title: autopkgtests fail on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2062119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062119] [NEW] autopkgtests fail on ppc64el
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 make it worse, just now we know" and continued (To not leave these platforms behind later unable to add it, albeit knowing it is still incomplete for now). It does not mean that we can ignore them for too long and certainly need to work on completing that into being fully functional in tests and real usage. Hence we create this spin off bug from the MIR work in bug 2051925 for tracking the further efforts. Example test log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/libt/libtracefs/20240417_184416_c2b35@/log.gz ** Affects: libtracefs (Ubuntu) Importance: Undecided Assignee: Adrien Nader (adrien-n) 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/2062119 Title: autopkgtests fail on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2062119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062118] [NEW] autopkgtests fail on s390x (segfault)
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 didn't make it worse, just now we know" and continued (To not leave these platforms behind later unable to add it, albeit knowing it is still incomplete for now). It does not mean that we can ignore them for too long and certainly need to work on completing that into being fully functional in tests and real usage. Hence we create this spin off bug from the MIR work in bug 2051925 for tracking the further efforts. Example test log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/libt/libtracefs/20240417_184123_8ab96@/log.gz ** Affects: libtracefs (Ubuntu) Importance: Undecided Assignee: Adrien Nader (adrien-n) 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/2062118 Title: autopkgtests fail on s390x (segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2062118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062118] Re: autopkgtests fail on s390x (segfault)
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 in: libtracefs (Ubuntu) Assignee: (unassigned) => Adrien Nader (adrien-n) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062118 Title: autopkgtests fail on s390x (segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2062118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062013] Re: RM: telegraf from Noble; no longer maintained in Ubuntu
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 1.22.3+ds1-0ubuntu2 in noble ppc64el telegraf 1.22.3+ds1-0ubuntu2 in noble riscv64 telegraf 1.22.3+ds1-0ubuntu2 in noble s390x Comment: Unmaintained in Ubuntu, not in Debian, snap alternative (LP: #2062013) Remove [y|N]? y 1 package successfully removed. ** Changed in: telegraf (Ubuntu) Status: Confirmed => 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/2062013 Title: RM: telegraf from Noble; no longer maintained in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/2062013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062013] Re: RM: telegraf from Noble; no longer maintained in Ubuntu
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 dependencies: $ reverse-depends -r noble --build-depends src:telegraf No reverse dependencies found $ reverse-depends -r noble src:telegraf No reverse dependencies found For what most nodes need - the agent - there is a snap $ snap find telegraf Name Version Publisher NotesSummary telegraf 1.30.0 sajoupaclassic Telegraf agent Or people would often use container images instead. The package as-is without much more investment is really is more misleading than helpful. Agreed to remove. And it is currently no more building from source in noble which is a state cleaned up towards the release. While there would be a fix for the build, the removal seems more appropriate in this case. ** Changed in: telegraf (Ubuntu) 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/2062013 Title: RM: telegraf from Noble; no longer maintained in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/2062013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2031491] Re: [MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail-dmarc-perl dependency)
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 libemail-simple-perl 2.218-1 in noble amd64: universe/perl/optional/100% -> main libemail-simple-perl 2.218-1 in noble arm64: universe/perl/optional/100% -> main libemail-simple-perl 2.218-1 in noble armhf: universe/perl/optional/100% -> main libemail-simple-perl 2.218-1 in noble i386: universe/perl/optional/100% -> main libemail-simple-perl 2.218-1 in noble ppc64el: universe/perl/optional/100% -> main libemail-simple-perl 2.218-1 in noble riscv64: universe/perl/optional/100% -> main libemail-simple-perl 2.218-1 in noble s390x: universe/perl/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: libemail-simple-perl (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/2031491 Title: [MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail- dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libemail-simple-perl/+bug/2031491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-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 libmail-dmarc-perl 1.20230215-1ubuntu1 in noble: universe/misc -> main libmail-dmarc-perl 1.20230215-1ubuntu1 in noble amd64: universe/perl/optional/100% -> main libmail-dmarc-perl 1.20230215-1ubuntu1 in noble arm64: universe/perl/optional/100% -> main libmail-dmarc-perl 1.20230215-1ubuntu1 in noble armhf: universe/perl/optional/100% -> main libmail-dmarc-perl 1.20230215-1ubuntu1 in noble i386: universe/perl/optional/100% -> main libmail-dmarc-perl 1.20230215-1ubuntu1 in noble ppc64el: universe/perl/optional/100% -> main libmail-dmarc-perl 1.20230215-1ubuntu1 in noble riscv64: universe/perl/optional/100% -> main libmail-dmarc-perl 1.20230215-1ubuntu1 in noble s390x: universe/perl/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: libmail-dmarc-perl (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/2023971 Title: [MIR] libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039566] Re: [MIR] libfile-sharedir-perl (as a libmail-dmarc-perl dependency)
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 libfile-sharedir-perl 1.118-3 in noble amd64: universe/perl/optional/100% -> main libfile-sharedir-perl 1.118-3 in noble arm64: universe/perl/optional/100% -> main libfile-sharedir-perl 1.118-3 in noble armhf: universe/perl/optional/100% -> main libfile-sharedir-perl 1.118-3 in noble i386: universe/perl/optional/100% -> main libfile-sharedir-perl 1.118-3 in noble ppc64el: universe/perl/optional/100% -> main libfile-sharedir-perl 1.118-3 in noble riscv64: universe/perl/optional/100% -> main libfile-sharedir-perl 1.118-3 in noble s390x: universe/perl/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: libfile-sharedir-perl (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/2039566 Title: [MIR] libfile-sharedir-perl (as a libmail-dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfile-sharedir-perl/+bug/2039566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039563] Re: [MIR] libregexp-common-perl (as a libmail-dmarc-perl dependency)
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 -> main libregexp-common-perl 2017060201-3 in noble amd64: universe/perl/optional/100% -> main libregexp-common-perl 2017060201-3 in noble arm64: universe/perl/optional/100% -> main libregexp-common-perl 2017060201-3 in noble armhf: universe/perl/optional/100% -> main libregexp-common-perl 2017060201-3 in noble i386: universe/perl/optional/100% -> main libregexp-common-perl 2017060201-3 in noble ppc64el: universe/perl/optional/100% -> main libregexp-common-perl 2017060201-3 in noble riscv64: universe/perl/optional/100% -> main libregexp-common-perl 2017060201-3 in noble s390x: universe/perl/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: libregexp-common-perl (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/2039563 Title: [MIR] libregexp-common-perl (as a libmail-dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libregexp-common-perl/+bug/2039563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039456] Re: [MIR] libnet-ip-perl (as libmail-dmarc-perl dependency)
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 libnet-ip-perl 1.26-3 in noble amd64: universe/perl/optional/100% -> main libnet-ip-perl 1.26-3 in noble arm64: universe/perl/optional/100% -> main libnet-ip-perl 1.26-3 in noble armhf: universe/perl/optional/100% -> main libnet-ip-perl 1.26-3 in noble i386: universe/perl/optional/100% -> main libnet-ip-perl 1.26-3 in noble ppc64el: universe/perl/optional/100% -> main libnet-ip-perl 1.26-3 in noble riscv64: universe/perl/optional/100% -> main libnet-ip-perl 1.26-3 in noble s390x: universe/perl/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: libnet-ip-perl (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/2039456 Title: [MIR] libnet-ip-perl (as libmail-dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnet-ip-perl/+bug/2039456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039569] Re: [MIR] libclass-inspector-perl (libfile-sharedir-perl dependency as libmail-dmarc-perl dependency)
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 libclass-inspector-perl 1.36-3 in noble amd64: universe/perl/optional/100% -> main libclass-inspector-perl 1.36-3 in noble arm64: universe/perl/optional/100% -> main libclass-inspector-perl 1.36-3 in noble armhf: universe/perl/optional/100% -> main libclass-inspector-perl 1.36-3 in noble i386: universe/perl/optional/100% -> main libclass-inspector-perl 1.36-3 in noble ppc64el: universe/perl/optional/100% -> main libclass-inspector-perl 1.36-3 in noble riscv64: universe/perl/optional/100% -> main libclass-inspector-perl 1.36-3 in noble s390x: universe/perl/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: libclass-inspector-perl (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/2039569 Title: [MIR] libclass-inspector-perl (libfile-sharedir-perl dependency as libmail-dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclass-inspector-perl/+bug/2039569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-perl
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 mismatches hopefully confirming all this I will promote them to clear -proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023971 Title: [MIR] libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)
** 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 simplestreams (simplestreams -> python-boto3 -> python-s3transfer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061217] Re: [MIR] python-boto3 as a dependency of simplestreams
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061751] Re: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python-botocore)
** 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 simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python- botocore) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243276] Re: MIR for libnet-ip-perl
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 to: https://bugs.launchpad.net/ubuntu/+source/libnet-ip-perl/+bug/243276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 522210] Re: [MIR] libclass-inspector-perl
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/libclass-inspector-perl/+bug/522210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039456] Re: [MIR] libnet-ip-perl (as libmail-dmarc-perl dependency)
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. https://bugs.launchpad.net/bugs/2039456 Title: [MIR] libnet-ip-perl (as libmail-dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnet-ip-perl/+bug/2039456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2031491] Re: [MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail-dmarc-perl dependency)
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. https://bugs.launchpad.net/bugs/2031491 Title: [MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail- dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libemail-simple-perl/+bug/2031491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039566] Re: [MIR] libfile-sharedir-perl (as a libmail-dmarc-perl dependency)
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039566 Title: [MIR] libfile-sharedir-perl (as a libmail-dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfile-sharedir-perl/+bug/2039566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-perl
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023971 Title: [MIR] libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)
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) => 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/2061750 Title: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)
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 packages built, but NOT to be promoted to main: This does need a security review, so I'll assign ubuntu-security Some special conditions apply, please read bug 2061217 which has all those details. Required TODOs: - #1 please add testing as discussed. Recommended TODOs: - #2 please update to the minor fix in 0.10.1 - #3 please update the package description to include the warning of this being good for use through boto3 but not for direct use. You can grab that from the projects webpage. I've spoken with Alberto and he is already on extending the package to have proper tests as well as considering the two recommended changes. [Rationale, Duplication and Ownership] Out of the stack around boto3 this is the only slight difference. boto already had the boto interface for s3 and boto3 evolved on that. In fact the package even suggests to only ever rely on the s3 interface in boto. So there is another package in main providing the same high functionality: python-boto. And that is what will be replaced via python-boto3 (bug 2061217), But to be able to provide that it needs the low level functions in python-s3transfer. => OK A team is committed to own long term maintenance of this package. => Server, team-subscription already added The rationale given in the report seems valid and useful for Ubuntu, for simplestreams via the dependency as reported and for other of python-boto3. Usually I suggest direct users of the lib as well, but in this case that should be avoided (more on that below). [Dependencies] OK: - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: - No other Dependencies to MIR due to this [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have unexpected Built-Using entries - not a go package, no extra constraints to consider in that regard - not a rust package, no extra constraints to consider in that regard Problems: None [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not expose any external endpoint (port/socket/... or similar) - does not process arbitrary web content - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) - does not deal with cryptography (en-/decryption, certificates, signing, ...) - this makes appropriate (for its exposure) use of established risk mitigation features (being a lib only it can not yet know the use-case and thereby not define profiles) Problems: - does parse data formats in its interaction with the cloud. Since many other things nowadays also provide AWS compatible backends one can not safely assume the source can always be trusted. - does use centralized online accounts to access the privileged AWS resources [Common blockers] OK: - does not FTBFS currently - This does not need special HW for build or test - Python package, but using dh_python I was confused for a moment not seing it in d/rules but it uses the more modern compat >=13 variant of dh-sequence-python3 in d/control. Double checked the build log, and it is in use there. Problems: - does not have a test suite that runs at build time - test suite fails will fail the build upon error. - does not have a non-trivial test suite that runs as autopkgtest [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - debian/watch is present and looks ok - Upstream update history is good - Debian/Ubuntu update history is ok - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - debian/rules is rather clean - It is not on the lto-disabled list Problems: - The current release is not packaged, but we are not much behind. The new only has a small bugfix, worth to give it a try but no hard requirement (0.10.0 -> 0.10.1). [Upstream red flags] OK: - no Errors/warnings during the build - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests) - no use of user nobody (only nfsnobody for actual nfs use) - no use of setuid / setgid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case (lib only) Problems: None -- You received this bug notification because you are a member of Ubuntu Bugs, which is
[Bug 2061217] Re: [MIR] python-boto3 as a dependency of simplestreams
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 picking it up at all. But due to that we are in a special situation where not-accepting it seems worse (due to the old python-boto it replaces being discontinued and outdated and incompatible) than accepting this with the requirements that we can make happen in the next few hours (see the review above). Due to that, while no one was happy or super satisfied - we voted unanimously to allow this to be promoted in noble to demote python-boto in the same action. The security review that we require is not expected to fit in the remaining time before the release and much less before RC images. Therefore it will be scheduled as if there would be no special urgency (usually completing in 2-4 weeks). Thereby it will not be a special urgent "change all other priority to complete it before the release" case which also answers @marks comment #6. No need to bring one more hard to deal with issue to Alex in this case. Waiting with a state-change for the uploads with the tests to be in proposed and then planning a last check with the release team to not interfere with any RC builds (clearing -proposed is always good, but we want to be sure). [1]: https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu- meeting.2024-04-16-14.32.moin.txt -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061751] Re: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python-botocore)
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) => 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/2061751 Title: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python- botocore) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061751] Re: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python-botocore)
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 look at the recommended TODOs. List of specific binary packages to be promoted to main: python3-botocore Specific binary packages built, but NOT to be promoted to main: This does need a security review, so I'll assign ubuntu-security Some special conditions apply, please read bug 2061217 which has all those details. Required TODOs: - #1 please add testing as discussed. I've spoken with Alberto and he is already on extending the package to have proper tests. [Rationale, Duplication and Ownership] There is another package in main providing the same functionality: python-boto. That was split in python-boto3 (bug 2061217) and python-botocore (this). But that alternative is outdated and discontinued and this request is about replacing the unmaintainable (and incompatible with the python in noble) old version with the new one. => OK A team is committed to own long term maintenance of this package. => Server, team-subscription already added The rationale given in the report seems valid and useful for Ubuntu, for simplestreams via the dependency as reported and for other users of the library. [Dependencies] OK: - no -dev/-debug/-doc packages that need exclusion - No dependencies in main that are only superficially tested requiring more tests now. Problems: - other Dependencies to MIR due to this, cases are already open and linked here [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have unexpected Built-Using entries - not a go package, no extra constraints to consider in that regard - not a rust package, no extra constraints to consider in that regard Problems: None [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not expose any external endpoint (port/socket/... or similar) - does not process arbitrary web content - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) - does not deal with cryptography (en-/decryption, certificates, signing, ...) - this makes appropriate (for its exposure) use of established risk mitigation features (being a lib only it can not yet know the use-case and thereby not define profiles) Problems: - does parse data formats in its interaction with the cloud. Since many other things nowadays also provide AWS compatible backends one can not safely assume the source can always be trusted. - does use centralized online accounts to access the privileged AWS resources [Common blockers] OK: - does not FTBFS currently - This does not need special HW for build or test - Python package, but using dh_python Problems: - does not have a test suite that runs at build time - test suite fails will fail the build upon error. - does not have a non-trivial test suite that runs as autopkgtest [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - debian/watch is present and looks ok - Upstream update history is good - Debian/Ubuntu update history is ok - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings The few pedantics you reported are nice to resolve, but not critical - debian/rules is rather clean - It is not on the lto-disabled list Problems: - the current release is not packaged, but that is only the case as upstream has almost daily releases through CI. We are on the right minor version (.34) and subversions are here not that much of a problem. [Upstream red flags] OK: - no Errors/warnings during the build - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody (only nfsnobody for actual nfs use) - no use of setuid / setgid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case (lib only) Problems: None -- 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 simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python- botocore) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061217] Re: [MIR] python-boto3 as a dependency of simplestreams
libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case (lib 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/2061217 Title: [MIR] python-boto3 as a dependency of simplestreams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060035] Re: [MIR] msgraph
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. https://bugs.launchpad.net/bugs/2060035 Title: [MIR] msgraph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msgraph/+bug/2060035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061217] Re: [MIR] python-boto3 as a dependency of simplestreams
** 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 dependency of simplestreams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061751] Re: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python-botocore)
** 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 indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python- botocore) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)
** 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-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061217] Re: [MIR] python-boto3
** 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 binary is arch-all) Link to package: - - https://launchpad.net/ubuntu/+source/python-boto3 - - https://launchpad.net/ubuntu/+source/python-s3transfer - - https://launchpad.net/ubuntu/+source/python-botocore + - https://launchpad.net/ubuntu/+source/python-boto3 + - https://launchpad.net/ubuntu/+source/python-s3transfer + - https://launchpad.net/ubuntu/+source/python-botocore [Rationale] + Simplestreams itself is in main for quite a while since bug 1220427. The package python-boto3 is required in Ubuntu main for simplestreams The package python-boto3 will not generally be useful for a large part of our user base, but is important/helpful still because it is required by simplestreams Additionally new use-cases enabled by this are demoting python-boto to universe because the only reverse depency in main is simplestreams and debian is going to drop support for python-boto, see LP: 2052437 The package python-boto3 is a new runtime dependency of package simplestreams that we already support python-boto is not compatible with python3.12, the only python supported in noble, thus to commit to a long term support of simplestreams, it's better to depend on dependencies that have upstream support The package python-boto3 is required in Ubuntu main no later than noble is released due to being required by a new upload of simplestreams in noble-proposed to make it work on python3.12 and to be able to drop python-boto from noble archives. python-s3transfer is a binary dependency of python-boto3 python-botocore is a binary dependency of python-s3transfer [Security] - No CVEs/security issues in this software in the past: (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-boto3 (0)https://ubuntu.com/security/cves?q==python-boto3=== (0)https://security-tracker.debian.org/tracker/source-package/python-boto3 (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-s3transfer (0)https://security-tracker.debian.org/tracker/source-package/python-s3transfer (0)https://ubuntu.com/security/cves?q==python-s3transfer=== (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-botocore (0)https://security-tracker.debian.org/tracker/source-package/python-botocore (0)https://ubuntu.com/security/cves?q==python-botocore=== No `suid` or `sgid` binaries No executables in `/sbin` and `/usr/sbin` Package does not install services, timers or recurring jobs Packages does not open privileged ports (ports < 1024). Package does not expose any external endpoints Packages does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...) [Quality assurance - function/usage] The package works well right after install. It's a python library. [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does - not have too many, long-term & critical, open bugs - - Ubuntu - - (2)https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug - - (1)https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bugs - - (4)https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bugs - - Debian - - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-boto3 - - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-s3transfer - - (1)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-botocore - - Upstream's bug tracker - - (192)https://github.com/boto/boto3/issues - - (24)https://github.com/boto/s3transfer/issues - - (112)https://github.com/boto/botocore/issues - Looks normal for the age and impact of these libraries + not have too many, long-term & critical, open bugs + - Ubuntu + - (2)https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug + - (1)https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bugs + - (4)https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bugs + - Debian + - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-boto3 + - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-s3transfer + - (1)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-botocore + - Upstream's bug tracker + - (192)https://github.com/boto/boto3/issues + - (24)https://github.com/boto/s3transfer/issues + - (112)https://github.com/boto/botocore/issues + Looks normal for the age and impact of these libraries - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The packages do not run a test at build time because it is not configured to do so, the upstream source
[Bug 2060020] Re: [Ubuntu-24.04]: Unable to bring up a guest with 1GB RAM using virt-install
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 variations at the memory size that is stated as "recommended". The 3GB mentioned here comes from osinfo-db which also has to include e.g. Desktop environments. Thanks Jbicha for providing that in the first place. Let us align what osinfo says here with the docs: - 3GB https://github.com/crobinso/osinfo-db/commit/1de8347e88f8b52849c11da9d0f154663220033d - 1GB https://discourse.ubuntu.com/t/basic-installation/11320 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060020 Title: [Ubuntu-24.04]: Unable to bring up a guest with 1GB RAM using virt- install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003316] Re: [FFe] Please add mysql-shell to ubuntu
** 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, 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: https://bugs.launchpad.net/ubuntu/+bug/2003316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003316] Re: [FFe] Please add mysql-shell to ubuntu
"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 images that follow from now. Accepting the source ... -- 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: https://bugs.launchpad.net/ubuntu/+bug/2003316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046154] Re: [MIR] libcryptx-perl (libmail-dkim-perl dependency)
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 all examples are in that) that we can handle the steps needed in this stack. Then we can try to wrap that through perl and use it from there. Still complex, but much closer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046154 Title: [MIR] libcryptx-perl (libmail-dkim-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcryptx-perl/+bug/2046154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046154] Re: [MIR] libcryptx-perl (libmail-dkim-perl dependency)
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 that seems more maintainable. And yes, already being in main makes it even simpler to the end of it. The question now really is if/how that could be modified and then used from the stack dmarc/dkim stack. Thanks for spotting John, really seems to be worth a try IMHO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046154 Title: [MIR] libcryptx-perl (libmail-dkim-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcryptx-perl/+bug/2046154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023531] Re: [MIR] dotnet6
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) Status: In Progress => Invalid ** Changed in: dotnet6 (Ubuntu Mantic) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu Jammy) Status: New => 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/2023531 Title: [MIR] dotnet6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060056] Re: [MIR] dotnet8
Thank you for the summary of differences - I'd also mention that you now build for s390x. I highly appreciate no more having .git and and generally the cooperation by upstream to our needs. While not being a straight exchange of sources with all else being the same, it is indeed a source rename and then some improvements. I also see regular updates and fixes which makes me consider this healthy in general. No new MIR is needed, and since dotnet6 was approved this is approved under the same terms as well. The jammy versions are straight backports and in the discussions it was considered ok to also promote it there. v8 currently exists in J/M/N, marking the bug as such. ** Changed in: dotnet8 (Ubuntu Noble) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu Mantic) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu Jammy) Status: 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] dotnet8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2060056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004449] Re: [MIR] libde265 (dependency of libheif)
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 to extend it is present. What we now have looks good in https://autopkgtest.ubuntu.com/packages/libd/libde265 for now. This is ok to go AFAIC, but it only makes sense once the rest of the heif dependency tree is ready. Setting the state while we wait for the rest to complete and then a change to pull it in. ** Changed in: libde265 (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/2004449 Title: [MIR] libde265 (dependency of libheif) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libde265/+bug/2004449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060361] Re: Dateisysten
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. Ich halte es auch immer noch für möglich das es eine Unsicherheit/Unklarheit bei der verwendung ist und alles eigentlich OK ist. Doch auch das kann man ohne Nachvollziehbares nicht prüfen. ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: New => Incomplete ** Changed in: cloud-images Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060361 Title: Dateisysten To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2060361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059975] Re: Remove from Noble
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 libruby3.1 3.1.2-7ubuntu4 in noble arm64 libruby3.1 3.1.2-7ubuntu4 in noble armhf libruby3.1 3.1.2-7ubuntu4 in noble i386 libruby3.1 3.1.2-7ubuntu4 in noble ppc64el libruby3.1 3.1.2-7ubuntu4 in noble riscv64 libruby3.1 3.1.2-7ubuntu4 in noble s390x ruby3.1 3.1.2-7ubuntu4 in noble amd64 ruby3.1 3.1.2-7ubuntu4 in noble arm64 ruby3.1 3.1.2-7ubuntu4 in noble armhf ruby3.1 3.1.2-7ubuntu4 in noble i386 ruby3.1 3.1.2-7ubuntu4 in noble ppc64el ruby3.1 3.1.2-7ubuntu4 in noble riscv64 ruby3.1 3.1.2-7ubuntu4 in noble s390x ruby3.1-dev 3.1.2-7ubuntu4 in noble amd64 ruby3.1-dev 3.1.2-7ubuntu4 in noble arm64 ruby3.1-dev 3.1.2-7ubuntu4 in noble armhf ruby3.1-dev 3.1.2-7ubuntu4 in noble i386 ruby3.1-dev 3.1.2-7ubuntu4 in noble ppc64el ruby3.1-dev 3.1.2-7ubuntu4 in noble riscv64 ruby3.1-dev 3.1.2-7ubuntu4 in noble s390x ruby3.1-doc 3.1.2-7ubuntu4 in noble amd64 ruby3.1-doc 3.1.2-7ubuntu4 in noble arm64 ruby3.1-doc 3.1.2-7ubuntu4 in noble armhf ruby3.1-doc 3.1.2-7ubuntu4 in noble i386 ruby3.1-doc 3.1.2-7ubuntu4 in noble ppc64el ruby3.1-doc 3.1.2-7ubuntu4 in noble riscv64 ruby3.1-doc 3.1.2-7ubuntu4 in noble s390x Comment: Transition to ruby3.2 completed (LP: #2059975) Remove [y|N]? y 1 package successfully removed. ** Changed in: ruby3.1 (Ubuntu) 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/2059975 Title: Remove from Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.1/+bug/2059975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003316] Re: [FFe] Please add mysql-shell to ubuntu
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 Title: [FFe] Please add mysql-shell to ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2003316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003316] Re: [FFe] Please add mysql-shell to ubuntu
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 mysql- clearly assigns it to
where it belongs, it is not too short and thereby matches
upstream+project (which is just shell, which would have been conflicting
- but mysql-shell is fine)
binaries: only one also mysql-shell - OK
extracted content:
some of the project defined names are "mysqlsh" instead of mysql-shell, I
like the
longer more descriptive name in the package and do not see it as a conflict
to the extracted files.
At the same time we should not force the binary names names over to be not
the common way
-> OK
# FHS
- Some content in /usr/share/mysqlsh which is ok
- some extra doc content in /usr/share/doc/mysql-shell - ok
- I'm not so sure on the python packaging paths
/usr/lib/mysqlsh/plugins/...
/usr/lib/mysqlsh/python-packages/mysql_gadgets/...
/usr/lib/mysqlsh/python-packages/mysqlsh/...
are not in common paths
You'd usually expect /usr/lib/python3/dist-packages/... for any of that
Like:
/usr/lib/python3/dist-packages/mysqlsh/...
/usr/lib/python3/dist-packages/mysqlsh/plugins/
Yet on the other hand those are not usual python files (libs or programs).
It is (by upstream) meant to go to libdir /usr/lib + name mysqlsh to be used
by their binary when in python scripting mode.
With that design it might be smart to not be in any normal include path.
And since it is only for internal usage by the tool itself, and for that FHS
says
about /usr/lib "Libraries for the binaries in /usr/bin and /usr/sbin."
So that is ok I think.
@anyone else please feel free to chime in and ensure a TIL moment for
me if that assumption is wrong.
# Dependencies
Test install in noble was fine, all dependencies were ok and I saw
nothing suspicious
# copyright
- Debian/* is GPL-3 + Canonical as it should be and it is new, not from
packaging/debian/*
- I did a full scan of copyrights and negative included what was defined, from
there I reduced one by one
and found the following worth a second look (fix it up or please reply where
my check was wrong):
- debian/additions/ConvertUTF*
LLVM is correct, but I think that should be "Copyright © 1991-2015 Unicode"
instead of "2003-2017 University of Illinois at Urbana-Champaign"
- ext/licenses/libssh-0.10.5-license.txt is in itself LGPL-2.1 which needs a
stanza for "1991, 1999
Free Software Foundation, Inc." as it in the source
- cmake/merge_archives_unix.cmake.in
2009 Sun Microsystems, Inc
This isn't generated, so let us list what is there (GPL-2)
- mysqlshdk/libs/utils/dtoa.cc
is "Oracle and/or its affiliates" whcih is the fallback, but also includes
"Copyright (c) 1991, 2000, 2001 by Lucent Technologies"
To be clear - A LOT was already correct, but these are a few easy to fix
improvement on the first upload IMHO.
# Packaging
- you have this as dfsg anyway so you seem to strip
But in ./ext/licenses/libssh-0.10.5/libssh-0.10.5.tar.xz is a non used
libssh.
Should that be removed as well to avoid any later issues?
Build uses libssh-dev in d/control.
Bonus: With that removed you could also drop the d/copyright stanza for
libssh wich is derived from what is in the LICENSES file
- tinyxml2 is in the archvie
tinyxml2 | 10.0.0+dfsg-2 | noble/universe| source
Could we strip ext/tinyxml2 as well and forget about licenses?
If not there are plentry of copyright statements in there missing in the
LICENSE file.
At least add those, but even better use tinyxml2 from the archive.
2 ext/tinyxml2-9.0.0/meson.build:1:# Copyright © 2020 Dylan Baker
3 ext/tinyxml2-9.0.0/docs/search/search.js:6: Copyright (C) 1997-2020 by
Dimitri van Heesch
4 ext/tinyxml2-9.0.0/docs/menu.js:6: Copyright (C) 1997-2020 by Dimitri van
Heesch
5 ext/tinyxml2-9.0.0/docs/jquery.js:6:* Copyright jQuery Foundation and other
contributors; Licensed MIT */
6 ext/tinyxml2-9.0.0/docs/jquery.js:10: * Copyright (c) 2007 Ariel Flesler -
aflesler ○ gmail • com | https://github.com/flesler
7 ext/tinyxml2-9.0.0/docs/jquery.js:19: Copyright (c) 2018 Steven Benner
(http://stevenbenner.com/).
8 ext/tinyxml2-9.0.0/docs/jquery.js:26: * Copyright 2011–2014, Dave Furfero
9 ext/tinyxml2-9.0.0/docs/jquery.js:35: * Copyright Vasil Dinkov, Vadikom Web
Ltd. http://vadikom.com; Licensed MIT */(function(t){"function"==typeof
define&?define(["jquery"],t):"object"==typeof modu
10 ext/tinyxml2-9.0.0/docs/menudata.js:6: Copyright (C) 1997-2020 by Dimitri
van Heesch
11 ext/tinyxml2-9.0.0/meson_options.txt:1:# Copyright © 2020 Dylan Baker
- I'm not too happy about linenoise-ng being embedded (discontinued, but that
is for
[Bug 2003316] Re: [FFe] Please add mysql-shell to ubuntu
-- 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: https://bugs.launchpad.net/ubuntu/+bug/2003316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055434] Re: [MIR] pemmican
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 1.0.3-0ubuntu1 in noble armhf: universe/python/optional/100% -> main pemmican-common 1.0.3-0ubuntu1 in noble i386: universe/python/optional/100% -> main pemmican-common 1.0.3-0ubuntu1 in noble ppc64el: universe/python/optional/100% -> main pemmican-common 1.0.3-0ubuntu1 in noble riscv64: universe/python/optional/100% -> main pemmican-common 1.0.3-0ubuntu1 in noble s390x: universe/python/optional/100% -> main pemmican-desktop 1.0.3-0ubuntu1 in noble amd64: universe/python/optional/100% -> main pemmican-desktop 1.0.3-0ubuntu1 in noble arm64: universe/python/optional/100% -> main pemmican-desktop 1.0.3-0ubuntu1 in noble armhf: universe/python/optional/100% -> main pemmican-desktop 1.0.3-0ubuntu1 in noble i386: universe/python/optional/100% -> main pemmican-desktop 1.0.3-0ubuntu1 in noble ppc64el: universe/python/optional/100% -> main pemmican-desktop 1.0.3-0ubuntu1 in noble riscv64: universe/python/optional/100% -> main pemmican-desktop 1.0.3-0ubuntu1 in noble s390x: universe/python/optional/100% -> main pemmican-doc 1.0.3-0ubuntu1 in noble amd64: universe/doc/optional/100% -> main pemmican-doc 1.0.3-0ubuntu1 in noble arm64: universe/doc/optional/100% -> main pemmican-doc 1.0.3-0ubuntu1 in noble armhf: universe/doc/optional/100% -> main pemmican-doc 1.0.3-0ubuntu1 in noble i386: universe/doc/optional/100% -> main pemmican-doc 1.0.3-0ubuntu1 in noble ppc64el: universe/doc/optional/100% -> main pemmican-doc 1.0.3-0ubuntu1 in noble riscv64: universe/doc/optional/100% -> main pemmican-doc 1.0.3-0ubuntu1 in noble s390x: universe/doc/optional/100% -> main pemmican-server 1.0.3-0ubuntu1 in noble amd64: universe/python/optional/100% -> main pemmican-server 1.0.3-0ubuntu1 in noble arm64: universe/python/optional/100% -> main pemmican-server 1.0.3-0ubuntu1 in noble armhf: universe/python/optional/100% -> main pemmican-server 1.0.3-0ubuntu1 in noble i386: universe/python/optional/100% -> main pemmican-server 1.0.3-0ubuntu1 in noble ppc64el: universe/python/optional/100% -> main pemmican-server 1.0.3-0ubuntu1 in noble riscv64: universe/python/optional/100% -> main pemmican-server 1.0.3-0ubuntu1 in noble s390x: universe/python/optional/100% -> main Override [y|N]? y 29 publications overridden. ** Changed in: pemmican (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/2055434 Title: [MIR] pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2055434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003316] Re: [FFe] Please add mysql-shell to ubuntu
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 ago again after being removed for a few releases) which is the curse of re-shipping the same base-source in multiple source packages. But other than that the use-case, the big benefit to provide that in noble along mysql and the NEW queue check for namespace (it is not too short and using the expected name) and licenses (it is as good or better than mysql [and percona]) as it has mostly the same + modifications. Steps from here: - I'd want to dive even a bit deeper on licenses/copyright just as I did in percona-xtradb. Just to improve if needed before accepting. - Furthermore it is fine, but also huge and I'd not want to throw that potential wrench into the current archive efforts, hence I'm not accepting it yet from NEW anyway. It isn't seeded, but anything that might migrations harder for any reason should hold back a bit I think. I'd propose to do that after the beta images are completed. - Since so much will have changed by then in noble, let us test-rebuild (in the same PPA) it to be sure before accepting from NEW. - But neither of the above two holds back that we'd need an "ok" from the release team in general. Hence I subscribed them and reset the bug to be in new state. If we could have that "ok" now it would be great. [1]: https://launchpad.net/ubuntu/noble/+queue?queue_state=0 -- 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: https://bugs.launchpad.net/ubuntu/+bug/2003316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003316] Re: [FFe] Please add mysql-shell to ubuntu
** 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 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/2003316 Title: [FFe] Please add mysql-shell to ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2003316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055434] Re: [MIR] pemmican
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 done ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055434 Title: [MIR] pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2055434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055434] Re: [MIR] pemmican
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 Ubuntu. https://bugs.launchpad.net/bugs/2055434 Title: [MIR] pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2055434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060205] Re: RM freezer-api
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 freezer-api the reasoning is right, and authoritative as this is an Openstack component and I trust James for that context (as with all else :-) actually ) Being not useful without the base src and causing failing tests removing it will also help to get all other things that might potentially. removed: Removing packages from noble: freezer-api 15.0.0-1 in noble freezer-api 15.0.0-1 in noble amd64 freezer-api 15.0.0-1 in noble arm64 freezer-api 15.0.0-1 in noble armhf freezer-api 15.0.0-1 in noble i386 freezer-api 15.0.0-1 in noble ppc64el freezer-api 15.0.0-1 in noble riscv64 freezer-api 15.0.0-1 in noble s390x freezer-api-doc 15.0.0-1 in noble amd64 freezer-api-doc 15.0.0-1 in noble arm64 freezer-api-doc 15.0.0-1 in noble armhf freezer-api-doc 15.0.0-1 in noble i386 freezer-api-doc 15.0.0-1 in noble ppc64el freezer-api-doc 15.0.0-1 in noble riscv64 freezer-api-doc 15.0.0-1 in noble s390x python3-freezer-api 15.0.0-1 in noble amd64 python3-freezer-api 15.0.0-1 in noble arm64 python3-freezer-api 15.0.0-1 in noble armhf python3-freezer-api 15.0.0-1 in noble i386 python3-freezer-api 15.0.0-1 in noble ppc64el python3-freezer-api 15.0.0-1 in noble riscv64 python3-freezer-api 15.0.0-1 in noble s390x Comment: ROM; unmaintained and breaking tests, LP: #2060205 Debian Bug: #1063850 Remove [y|N]? y 1 package successfully removed. ** Changed in: freezer-api (Ubuntu) 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/2060205 Title: RM freezer-api To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freezer-api/+bug/2060205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
