ran pro collect-logs
** Attachment added: "pro client logs"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2087544/+attachment/5835645/+files/pro_logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
This is right after do-release-upgrade completed, before reboot.
Since it disabled third party (like chrome) I wanted to look at ESM PPAs.
$ pro status
No Ubuntu Pro services are available to this system.
For a list of all Ubuntu Pro services, run 'pro status --all'
Enable
** Tags removed: server-triage-discuss
** Changed in: unixodbc (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2082608
Title:
22.04.5 to 24.04.1 sets /etc/samba/smb.conf to default
To manage notifications about this bug go
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086736
Title:
AppArmor profile needs to allow access to /var/tmp
To manage notifications about this bug go to:
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077725
Title:
CIFS cl
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084459
Title:
Wind
** Changed in: dpdk (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085228
Title:
Merge dpdk from Debian unstable for plucky
** Changed in: pollen (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085269
Title:
Merge pollen from Debian unstable for plucky
To m
** Changed in: rdma-core (Ubuntu)
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085278
Title:
Merge rdma-core from Debian unstable for plucky
** Changed in: sg3-utils (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/2085291
Title:
Merge sg3-utils from Debian unstable
** Changed in: ssl-cert (Ubuntu)
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085295
Title:
Merge ssl-cert from Debian unstable for plucky
T
** Changed in: w3m (Ubuntu)
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085308
Title:
Merge w3m from Debian unstable for plucky
To manage n
** Changed in: simplestreams (Ubuntu)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085292
Title:
Merge simplestreams from Debian unstable f
** Changed in: apr (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085215
Title:
Merge apr from Debian unstable for plucky
To man
** Changed in: python-botocore (Ubuntu)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085272
Title:
Merge python-botocore from Debian unstab
** Changed in: python-boto3 (Ubuntu)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085271
Title:
Merge python-boto3 from Debian unstable for
** Changed in: squid (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085293
Title:
Merge squid from Debian unstable for plucky
To man
** Changed in: python-s3transfer (Ubuntu)
Assignee: (unassigned) => Thomas Bechtold (toabctl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085274
Title:
Merge python-s3transfer from Debian un
** Changed in: virglrenderer (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085305
Title:
Merge virglrenderer from Debian uns
** Changed in: sysstat (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/2085298
Title:
Merge sysstat from Debian unstable
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085296
Title:
Merge sssd from Debian unstable for plucky
** Changed in: libslirp (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085245
Title:
Merge libslirp from Debian unstable for
While there is nothing yet, let me grab the spot for planning purpose.
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: multipath-tools (Ubuntu)
Milestone: None => ubuntu-25.02
--
You received this bug notification b
While there is nothing yet, let me grab the spot for planning purpose.
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: open-iscsi (Ubuntu)
Milestone: None => ubuntu-25.02
--
You received this bug notification because you
Thanks for confirming,
I think we need to find a bit of time to find or bisect what in between the
versions 10.0 ->10.6 has fixed it. And once we know the change needed start
considering a fix/backport.
I've tagged it to come up in the next team bug sessions, but we are
currently all travelling
In the guest log that libvirt creates you'd find how it started
virtiofsd for you, for example in my working case:
Noble:
$ sudo grep virtiofs /var/log/libvirt/qemu/j-vfs.log
2024-10-10 06:19:17.362+: Starting external device: virtiofsd
/usr/libexec/virtiofsd --fd=34 -o source=/var/guests/j-v
I had used a Noble guest again even when trying the Jammy host,
so as next theory I thought it might be the guest driver for virtiofs so I
tried a jammy guest - but it also worked.
I've also split the virtiofsd log entries up into phases for you to
better compare:
1. start the guest (= libvirt g
Also works on Jammy for me, again sharing the XML representing the guest
so you can compare.
n-guest
a06f0cc8-1a5b-41f8-a4ad-a7ce7151325a
https://launchpad.net/uvtool/libvirt/1";>ssh-rsa
B3NzaC1yc2EDAQABAAABgQDOndm3a1HCdkmMh1YUhZ7S2fwIB+nd5ehdLROwhelQn4juWkODm4/GaWAbI1ahdN9EGr
I was re-checking this so you have something to compare to - for a start
on Noble as that is what I had around right away.
Creating a new guest and then adding the entries outlined in [1], which
AFAICS are the same or close to what you use, worked for me. The biggest
difference might be that I cre
Hi Rick
> I expected sharing filesystem between guest and host would work.
Yeah, it does in my experience since 20.10 got easier in 21.04 and
should therefore be fine in 22.04 and later. But I've explicitly only
used it on the former two versions and then again on 24.04, so it could
be in Jammy i
Well,
the error indicated that it would be kylin.
And the installation media in the log says:
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
Just to be sure, could you report here what the output of these to is:
$ uname -a
$ cat /etc/os-release
$ cat /etc/lsb-rele
Due to rpds-py bug 2072621 not being ready this had moved back again.
That changed, now the full chain of:
- new version of python-jsonschema in main
-> python-jsonschema-specifications (bug 2072619)
-> referencing (bug 2072620)
-> rpds-py (bug 2072621)
is ready.
Promoting all
Due to rpds-py bug 2072621 not being ready this had moved back again.
That changed, now the full chain of:
- new version of python-jsonschema in main
-> python-jsonschema-specifications (bug 2072619)
-> referencing (bug 2072620)
-> rpds-py (bug 2072621)
is ready.
Promoting all
Due to rpds-py bug 2072621 not being ready this had moved back again.
That changed, now the full chain of:
- new version of python-jsonschema in main
-> python-jsonschema-specifications (bug 2072619)
-> referencing (bug 2072620)
-> rpds-py (bug 2072621)
is ready.
Promoting all
it shows in mismatches state is Fix
committed.
** Changed in: rpds-py (Ubuntu)
Status: New => Fix Committed
** Changed in: rpds-py (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
> Bug 2062951 is also likely to affect this machine, and may cause
relevant side effects here.
I've not seen the flickering, but thanks for the info.
> The most relevant log messages I can see are:
> Cursor update failed: drmModeAtomicCommit: Invalid argument
Ah, that explains why I see it "of
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2083479/+attachment/5824067/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2083479/+attachment/5824066/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083479
Public bug reported:
Hi,
I considered it a one off, but it now happened a second time so I thought it
might be worth to report so you can match against anything else you might get
reported.
## Setup
- Ubuntu 24.04 with mostly defaults (I config a few things but e.g. do
not install a massive am
You asked for drm_info which I had to install first, so this is taken after the
last reboot.
This mostly looks like HW/SW inventory, I doubt but let me know if it is
helpful to re-run that next time it happens again.
** Attachment added: "drm_info after fresh boot"
https://bugs.launchpad.net
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2083479/+attachment/5824068/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083479
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2083479/+attachment/5824069/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083479
** Attachment added: "journal of the system until it happened the second time
(ends with hard power the next morning)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2083479/+attachment/5824065/+files/report-frozen-screen-second-occurance.txt.gz
** Tags added: apport-collected nob
** Attachment added: "journal of the system until it happened (ends with hard
power off shortly after the issue triggered)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2083479/+attachment/5824064/+files/report-frozen-screen-first-occurance.txt.gz
--
You received this bug notif
** Changed in: rpds-py (Ubuntu)
Assignee: Lukas Märdian (slyon) => 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/2072621
Title:
[MIR] rpds-py
To man
Greta, this seems ready but as discussed
[16:40] Desktop won't be promoting jpeg-xl/highway until 25.04 cycle
[16:41] thank you
[16:41] I'd assign to you until all is in place then?
[16:41] ok
ready then soon
** Changed in: highway (Ubuntu)
Assignee: (unassigned) => Jeremy Bícha (jbicha
So we have a pre-ack under conditions and a security ack.
That means you'd have to look at the required and recommended tasks to get this
fully approved.
Marking incomplete again and assigning back to the reporter to handle
this.
(Reminder: the agreement was that the initial getting it ready wou
** Changed in: rpds-py (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072621
Title:
[MIR] rpds-py
To manage notifications about this bu
Also trying to answer the questions of Juerg which all were good ones.
> Why is the size problematic?
On one hand the derivative bugs Rolf already quoted like bug 1951422 and
bug 1951423.
But disk space is only a small aspect of it as of today IMHO.
Where density matters (virtual systems) firmwa
The binaries all got built and are in as well by now, ready for the
validation from proposed.
Thank you Andreas for the SRU tagging and post.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081000
Tit
Confirming the fix to tests and watch in valkey/7.2.5+dfsg1-2ubuntu4~24.04.1
The new 7.2.5+dfsg1-2ubuntu4~24.04.1 is again just the backport version change.
Former Ack still applies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
I thought this might not even need to wait for the meeting if these additions
are sufficient.
But only today did I find some time to go a bit deeper on it and check for that.
I like it, even overwriting base pythons rules to inherit the wsdd profile,
LGTM.
The fact that you followed up due to te
Thank you so much, I didn't re-check for that and failed to see it mentioned
here.
Awesome that you already covered that too.
It will definitely help to move this over the "OK" line in the meeting on Tue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
In regard to the AA new queue check this seems fine:
- same content as in Oracular (as expected, only diff is the backport in
changelog)
- Thereby the same ok for the License
- And the same ok for no namespace clash
I pondered for a bit between
7.2.5+dfsg1-2ubuntu3~24.04 (proposed)
And
7
Thanks for the security review, rechecking the open asks we had to check
if we are fully ready.
A lot has been addressed already:
- #1 Better testing
I see a discovery test (the main use case) and a run of the regression suite.
Thanks for adding that!
- #2 d/watch file
Added, thanks!
- #4
Indeed, both are fully in oracular
ruby3.2 | 3.2.3-1ubuntu1 | oracular | source, amd64, arm64, armhf, i386,
ppc64el, riscv64, s390x
ruby3.3 | 3.3.4-2ubuntu5 | oracular | source, amd64, arm64, armhf, i386,
ppc64el, riscv64, s390x
And as you've shown no dependencies left on ruby3.2
Beta freeze
Thanks for confirming, reported to https://github.com/canonical/Ubuntu-
Sans-fonts/issues/123
** Bug watch added: github.com/canonical/Ubuntu-Sans-fonts/issues #123
https://github.com/canonical/Ubuntu-Sans-fonts/issues/123
--
You received this bug notification because you are a member of Ubun
Thanks for doing that and thanks for the little session reminding me
again of the extra-removals I've forgotten about. Totally applies in
this case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/207272
Short, simple and correct.
And also stuck at 3.1.2.. since forever due to the same reason.
Thanks for already providing all the references!
it still is in unstable though
And https://tracker.debian.org/pkg/cryptojs points to the new 4.2 version
(which still is discontinued upstream).
It is right
Ack to the case.
It is indeed the same code, but src:swig is evolving and on 4.2.1.
Yes, nothing is depending on swig3.0 anymore.
It is indeed removed in Debian oldstable and later and only bit-rotting
without a use case in Ubuntu.
Removing packages from oracular:
swig3.0 3.0.12-2.2ubunt
FYI: Only waiting on the package subscription to promote this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078827
Title:
[MIR] luit
To manage notifications about this bug go to:
https://bugs.lau
A quick packaging check seems fine (this isn't a full review as it was in main
already).
d/watch present, d/rules reasonable and lintian sort of happy.
A few like:
W: luit source: build-depends-on-obsolete-package Build-Depends: pkg-config =>
pkgconf
But that isn't a blocker.
The only CVE is sup
Thank you Nathan, if it is really "the same broken out and continued in
a different place" that should be fine.
But we found in yesterdays MIR meeting that the changelog says "Removed
luit, which is now packaged separately with a different upstream".
This wording is ambiguous, it could mean:
a)
Public bug reported:
#Stub#
This is broken out of x11-utils and thereby should be ok to go to main,
but it actually isn't
part of the same in Jammy:
https://launchpadlibrarian.net/592958282/buildlog_ubuntu-jammy-
amd64.x11-utils_7.7+5build2_BUILDING.txt.gz
recommends in Noble and later:
https:/
clearing the simple old cases after done with the new:
pngphoon | 1.3-3build2 | noble/universe| source, amd64, arm64, ppc64el,
riscv64, s390x
pngphoon | 1.3-3build2 | oracular/universe | source, amd64, arm64, ppc64el,
riscv64, s390x
There is no armhf left as of today, so let me mark it co
You are right, that is just what I see and confirm. In excuses [1] it is
blocked for missing the s390x build which in 0.3.2-2 [2] Build-Depends
on adb now. And both are in proposed with the old unusable s390x build
holding it back.
librust-spytrap-adb-dev | 0.3.2-1 | oracular-proposed/universe |
Even in Ubuntu it failed back then [1] already.
Then it didn't even try to build riscv pst focal and until Oracular [2].
Not only did it never build on Debian, whenever it failed on Debian or
on Ubuntu it was different issued. From test failures to even segfaults
while building.
While the last fa
FYI I summoned Utkarsh, thanks for having a release team POV.
Accepted now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078327
Title:
[needs-packaging] vision-drivers
To manage notifications abo
FYI I summoned Utkarsh, thanks for having a release team POV.
Accepted now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078326
Title:
[needs-packaging] ipu7-drivers
To manage notifications about
Simple and straight forward - thanks.
Ack to the case:
Removing packages from oracular:
libzmat-dev 0.9.8+ds-8 in oracular s390x
libzmat1 0.9.8+ds-8 in oracular s390x
octave-zmat 0.9.8+ds-8 in oracular s390x
Comment: Build-depends on libblosc2-dev which is not available on
While primarily being removed related to fastapi I agree that it is
FTBFS on its own tests and the same block other things like mypy.
Without reverse dependencies it can go away and is ok to come back once
it does so from being removed in unstable.
Ack to the case
Removing packages from oracular:
Thanks for linking to the changelog, indeed intentional and controlled.
Gladly those metapackage dependencies are only recommends.
But will they be cleaned up one day?
Probably not too important, certainly not to block on.
Ack to the case.
Removing packages from oracular:
digikam 4:8.3.0
Thanks for clarifying why we still have ipu6-drivers!
All that was said on bug 2078327 still applies.
And Timo also has uploaded this one.
Checking and accepting if it goes just as well ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
You are confirming on the version what I derived from looking at it -
thanks!
So VCS will be eventually be the normal git Ubuntu link - I'm ok with
that.
In the meantime Timo has uploaded the few small fixes we needed to go on.
Accepting ...
--
You received this bug notification because you are
Ack, this is explicit and intentional in [1].
Removing packages from oracular:
libopenfoam 1912.200626-2build3 in oracular armhf
openfoam 1912.200626-2build3 in oracular armhf
Comment: No more builds on armhf (LP: #2078566)
Remove [y|N]? y
2 packages successfully removed.
[1]: htt
More and more packages go the no 32bit (and especially armhf) way...
Ack to the case
Removing packages from oracular-proposed:
gpaw 24.1.0-1build2 in oracular armhf
Comment: No more builds on armhf (LP: #2078567)
Remove [y|N]? y
1 package successfully removed.
Removing packages from oracu
Hi Julian,
AFAICS that isn't even intentional anymore.
Just the auto-rescue from src:gcc-1[34] being in main.
[11]:
libgo-13-dev | gcc-13 | Rescued from gcc-13
libgo-14-dev | gcc-14 | Rescued from gcc-14
The rest then is a long list of things libgo-13-dev and libgo-14-d
Different but related topic
Speaking of updates, obviously looking at ipu7-drivers made me look at
ipu6-drivers.
That was back then needed when not provided by the kernel yet, just like this
time ipu7-drivers.
But AFAICS the kernel in Oracular now has it all:
root@o:~# apt-cache show linux-modu
Timo sponsored and asked for a New queue review:
# Managing the package namespace
src:ipu7-drivers
bin:intel-ipu7-dkms
Not too short and following the usual model for intel drivers that is already
used.
In fact it is the natural continuation of the former ipu7-drivers
=> OK
- Ensuring c
Timo sponsored and asked for a New queue review:
# Managing the package namespace
src:vision-drivers
bin:intel-vision-dkms
Not too short and following the usual model for intel drivers that is already
used.
=> OK
- Ensuring compliance with the software license
- The project itself is GPL
I see https://launchpad.net/ubuntu/+source/astroquery/0.4.7+dfsg-1
Which migrated just fine.
None of the astro* left in excuses.
\o/
Thank you so much @Ole!
** Changed in: astropy (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
B
This one is also ready for promotion, while unblocking component
mismatches for James I also looked at this one.
While the "no need for security nor test" is a bold call, you gladly outlined
the reasons why you think so.
And it is not "no test" just no autopkgtest (the tests run at build at least
This one is also ready for promotion, while unblocking component
mismatches for James I also looked at this one.
Override component to main
referencing 0.35.1-1ubuntu1 in oracular: universe/misc -> main
python3-referencing 0.35.1-1ubuntu1 in oracular amd64:
universe/python/optional/100% -> main
p
Override component to main
python-typeguard 4.3.0-1 in oracular: universe/misc -> main
python3-typeguard 4.3.0-1 in oracular amd64: universe/python/optional/100% ->
main
python3-typeguard 4.3.0-1 in oracular arm64: universe/python/optional/100% ->
main
python3-typeguard 4.3.0-1 in oracular armhf:
FYI Removed from Jammy-proposed to unblock bug 2076929.
This isn't permanent - it can re-enter jammy-proposed when being re-uploaded in
the future.
Removing packages from jammy-proposed:
grub2-unsigned 2.06-2ubuntu14.5 in jammy
grub-efi-amd64 2.06-2ubuntu14.5 in jammy amd6
As outlined in the discussion above, I removed grub2-unsigned
grub2-signed from jammy-proposed to unblock you.
Removing packages from jammy-proposed:
grub2-unsigned 2.06-2ubuntu14.5 in jammy
grub-efi-amd64 2.06-2ubuntu14.5 in jammy amd64
grub-efi-amd64 2.06-
Thanks for the clarifying MM/IRC discussions Mate!
The case is indeed clear once one cleared the view of all the different grub*
things that play into this and are much more clear to you than to anyone just
coming by :-).
To summarize my understanding:
- bug 2043084 brought us
- https://launc
Thank you for confirming, I merged the MR of Lucas.
And then removed it:
Removing packages from oracular:
dmraid 1.0.0.rc16-12ubuntu4 in oracular
dmraid 1.0.0.rc16-12ubuntu4 in oracular amd64
dmraid 1.0.0.rc16-12ubuntu4 in oracular arm64
dmra
** Changed in: badger (Ubuntu)
Status: In Progress => 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/2078313
Title:
Remove badger on ppc64el from oracular
To manage notifications
Removing packages from oracular:
badger 2.2007.2-3build1 in oracular ppc64el
Comment: FTBFS on ppc64el blocking golang grpc transition (LP: #2078313)
Remove [y|N]? y
1 package successfully removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
@zhjs
A few questions to further complete my understanding of potential ripple
effects in the go model, these thoughts are no priority, just for my
curiosity.
While the -dev is arch:all would, due to the problem any ppc64el build
depending on golang-github-dgraph-io-badger-dev also fail if we'd r
Thank you zhjs for the discussion on IRC btw!
This is a positive aspect of golang builds that I did not yet formerly connect
the dots about.
Thanks for you patience with my silly questions there, this morning I have a
few more minutes for this and it makes sense now :-)
Due to the actual builds
Thank you all - This was extensively verified by now, making it verified
Also see comment #34
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy verification-needed-noble
verification-needed-xenial
** Tags added: verification-done
Hi,
I didn't have much time atm, but will look at it again.
Until then please cahse down that you asked for just badger (which has no
reverse dependencies), but there are other binaries of that source which are
depended on:
root@o-prop:~# reverse-depends -r oracular -b src:badger
Reverse-Build-D
Nothing in proposed
rmadison -u ubuntu -s oracular,oracular-proposed astroquery
astroquery | 0.4.6+dfsg-4 | oracular/universe | source
Yet the main reason to for this to be a removal is that it also blocks astropy.
But that migrated or was cancelled
rmadison -u ubuntu -s oracular,oracular-propo
Ack on FTBFS [1] and being removed from Testing.
Since there is no way it can resolve without a new upload and at the
same time blocks other things from migrating I think removing is better
than pushing it back to -proposed.
Dependencies indeed are "only" recommends which do not block the removal
I think someone acted and resolved this without updating the bug:
Nothing in excuses about osmo and oracular seems to have no armhf of it
anymore.
$ rmadison -u ubuntu -s oracular,oracular-proposed libosmo-sccp
libosmo-sccp-dev libosmo-sigtran7 libosmo-sigtran-doc libosmo-sigtran-dev
libosmoscc
Hey Ravi,
thanks for driving this!
We see progress on the meta packages \o/.
Furthermore I was able to process many but not all of the related removals.
Therefore it might be time to re-check, summarize and double down on the
few tasks that are left to make it in time for beta freeze?
--
You re
For full transparency, this is not only abandoned - it also is part of
the removal of the very outdated wireless-tools via bug 2068612
This certainly is not a very often used component, but removing it would
essentially remove all of the matchbox ecosystem which might be a bit
too much or is that
1 - 100 of 2112 matches
Mail list logo
