On Mon, Dec 27, 2021 at 1:15 PM Krzysztof Gajda
<1770...@bugs.launchpad.net> wrote:
>
> Hi.
>
> This is real issue, because DKIM signing doesn't work without this fix
> (and amavisd-new marks incorrectly outbound emails as RelayedOpenRelay).
>
> Any chance to include this patch in LTS18 current
https://github.com/acassen/keepalived/commit/8f658000ff9fa8b67a81d29b4a73c6a3c1fc2c2b
was accepted upstream and is in
keepalived | 1:2.2.4-0.2 | jammy| source, amd64,
arm64, armhf, ppc64el, riscv64, s390x
I do not think this needs backports, setting fix released.
**
** Changed in: mailman (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777349
Title:
Broken encoding in Russian-translated HTML templates
To manage
@stgraber - since this is lx[cd] and you still usually do the uploads.
Do you have insight or opinion about this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947811
Title:
cgroups broken in
Hi Billy,
you did not attach the error logs of mysql nor the logs of the apt terminal
output (both would by default be provided by apport). Without those no one is
able to act and try to understand what happened to your install/upgrade of
mysql.
Is that issue persistent throughout a
Hi,
thanks for your report and your help to make Ubuntu better.
Services have to be restarted on upgrades to pick up the new code.
In your case from your log it seems that mysql started, but was unable to
stop/restart well:
Error: Unable to shut down server with process id 15798
Sadly the
I'm marking this incomplete waiting for feedback on the suggested
options or a discussion why this really should be an error to be fixed
in the source (instead of configuration).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I'm not 100% sure but to me that is a setup and configuration issue with the
new version being a bit more insisting that it can read/access paths it is
supposed to back up.
The new behavior can be disabled with --ignore-errors, but I'm tempted
to consider this dangerous as you could have
That would then be part of 4.15.3
Thanks Stefan, linking the upstream bug ...
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=14882
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Indeed fixed in the referred version
https://salsa.debian.org/ssh-team/openssh/-/blob/master/debian/changelog#L4
Debian Bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002803
This is already in jammy-proposed
openssh-client | 1:8.7p1-4 | jammy-proposed | amd64, arm64, armhf,
This is accepted in Debian now and works fine on a test build.
The former upload is still stuck in proposed anyway:
breezy | 3.2.1-1ubuntu1 | jammy-proposed/universe | source
I synced the new version as it can replace the one in proposed without a
drawback and keeps auto-syncing from there.
** Tags added: 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/1956166
Title:
Ubuntu 22.04 doesn't boot with xen
To manage notifications about this bug go to:
Thanks for the report Belgarath.
Do happen to already know the commit(s) that added this to 4.15 and have
a link?
Assigning to smb for xen opinions ...
@smb - not for updating to 4.15 (violating the SRU policy) but maybe for
identifying the fix and backporting it at least to Focal?
@smb - And
As the intended fix for the update-regression by this security fix was
now multiple times reported to not help (thanks David and Richard) I
have assigned the security-team to have another look and tagged it as
regression-update.
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Ubuntu
Thanks for the info Michael,
without steps to reproduce I see two paths from here.
## #1 trying different versions
As Paride asked it might be worth to check different versions.
There is no super-convenient way to downgrade bind9
You can add all of Bionics (or any other release in between
Thank you Scott!
As reference, that mentioned change is [1] and not yet part of a Debian
upload to sync/merge.
[1]: https://salsa.debian.org/postfix-team/postfix-
dev/-/commit/01fb7f1b307fb9bbc025d90dd404c9bff89f76ff
** Tags added: server-todo
--
You received this bug notification because you
FYI - The recent re-open by upstream is about a non fatal alert AH02808.
It would be a new Ubuntu bug to fix that as well (once the dicussion by
upstream settled and it is accepted there). TL;DR when injecting a lot of proxy
conf it can exceed the space it has and then trigger this.
--
You
Hi Walter,
that is a default behavior of launchpad since the bug was on "expired" for too
long it was auto-closed.
The last few week was the Christmas shutdown period and even before a lot of
things were busy.
I'm sure Sergio or someone else will have a deeper look at your new logs
provided in
Thank you Frank for that extra confirmation,
by now also all the blockers on the other bug fixed are good. I expect this to
be released as soon as the SRU Team is back from the Christmas shutdown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
There was one bad old tag left, fixed that.
Once the SRU Team is back for action this should be released.
** Tags removed: block-proposed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929926
Hi James,
I did a recheck but the repositories look fine to me here.
On a system with -release, -updates, -security pockets and a PPA I see
all of them are available.
root@f:~# apt-cache policy libvirt-dev libvirt0
libvirt-dev:
Installed: (none)
Candidate: 6.0.0-0ubuntu8.15
Version table:
Proposed fix.
** Patch added:
"0001-ALSA-hda-cs8409-Increase-delay-during-jack-detection.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950900/+attachment/5550496/+files/0001-ALSA-hda-cs8409-Increase-delay-during-jack-detection.patch
--
You received this bug notification
Propsed fix is here:
https://lore.kernel.org/all/20211231131221.itwotyfk5qomn...@cae.in-
ulm.de/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950900
Title:
Internal Speakers on DELL Inspirion
Could someone please finally fix this on 20.04 LTS? I imagine it should
be trivial, but I don't have the knowledge/skill at this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868517
Title:
Could someone please fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868517
Title:
Stray /usr/.crates2.json file
To manage notifications about this bug go to:
Hi Sam and Alan,
> Christian> Reproducible in local autopkgtest
>
> Let me make sure I'm understanding.
> You are saying that prior to penssl 3, the test works, but with
> openssl3, the test fails?
Yes that is correct
> What is the ssl version in the successful test
** Attachment added: "freeradius-moonshot.bad.log"
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1955009/+attachment/5548178/+files/freeradius-moonshot.bad.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "freeradius-moonshot.good.log"
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1955009/+attachment/5548177/+files/freeradius-moonshot.good.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Corey for picking this up so quickly. Do you mind sharing a link to
where/what was changed?
Will there be any backporting for packaged of current OpenStack releases if I
may ask?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- Init script for glance-api ignores any additional config files
+ Init script for glance-api ignores additional config files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955022
MR approved and uploaded to Jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950028
Title:
FTBFS against g++ 11
To manage notifications about this bug go to:
in: thin-provisioning-tools (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/1950028
Title:
FTBFS against g++ 11
To man
There is some test delta, but for boost and I'd not see an immediate
conenction to our FTBFS fails we see.
But what I was able to confirm was that setting it back to use gcc-10 for now
works.
The following gets the build in Jammy working.
diff --git a/debian/control b/debian/control
index
I was able to reproduce it in sbuild locally.
But reproducing it from upstream git did not work well.
Neither with libgmock-dev from the package
$ ./configure --enable-testing
$ make
$ apt install libgmock-dev
# that is version 1.11.0-3
$ make unit-test
Nor using upstreams
Public bug reported:
The init script at /etc/init.d/glance-api (likely created by the
openstack-pkg-tools) uses the
```
PROJECT_NAME=glance
NAME=${PROJECT_NAME}-api
CONFIG_FILE=/etc/${PROJECT_NAME}/${NAME}.conf
```
to later add the daemon-arg ``--config-file /etc/glance/glance-
api.conf``
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/1955006
Title:
static libssl1.1 depends blocks openssl removal
To manage noti
Reproducible in local autopkgtest
Good:
### gss_eap_shib_attr_provider::init(): Initializing ShibResolver library
### finalize_class::finalize_class(): Constructing
Sending init_sec_context token (size=81)...continue needed...
Sending init_sec_context token (size=50)...continue needed...
Sending
Public bug reported:
As part of the openssl3 transition [1] built fine.
But it got stuck in proposed due to the test of moonshot-gss-eap failing on all
architectures [2].
Note: ssl deps worked find
Depends: libc6 (>= 2.34), libcap2 (>= 1:2.10), libpcap0.8 (>= 1.0.0),
libpcre3, libssl3 (>=
Public bug reported:
d/control of memcached has this
18 Package: memcached
...
22 Depends:
23 adduser,
FYI the release of this is slowed down by the slow verification of bug
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1929926
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749393
Title:
Hello,
the slow verification of this blocks the more important/urgent fix of bug
1749393 that we'd really would want to get released before Christmas. I know
that FHeimes has coordinated this to be tested within IBM - any chance to get
this completed in the next few days?
--
You received this
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953128
Title:
GCC ICE: in create_fix_barrier, at config/arm/arm.c:17891
To manage notifications about this bug go to:
** Changed in: unbound (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/1946217
Title:
unbound: Fail to build against OpenSSL 3.0
, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case
(not user visible)?
Problems: None
** Changed in: libio-interactive-perl (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: li
Reviewed, approved and showing up in component mismatches.
I set it to "Fix Committed" and subscribed ubuntu-archive admins to
handle the promotion of the package to main.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: glusterfs (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/1950321
Title:
[MIR] glusterfs
To manage notifications about
** Changed in: libio-interactive-perl (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/1951067
Title:
[MIR] libio-interact
Great,
all seems to be in place then, pelase:
1. get Desktop to subscribe to the PKG
2. set it to Fix Committed
3. subscribe and get in touch with an AA to promote it
Assigning to Lukas to do that
** Changed in: dh-elpa (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You
This is in component mismatches again in Jammy.
This time from dnspython (foundations).
As discussed in the MIR Team meeting the openstack team is ok to re-
promote this in Jammy as-is and continue to own it.
James Page agreed but wanted to do a quick hygene check on it.
Assigning to him.
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?
** Changed in: ledmon (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Foundations Bugs
(foundations-bugs)
** Changed in: ledmon (Ubuntu)
Status: Confirmed => In
As planned https://launchpad.net/ubuntu/+source/postgresql-mysql-fdw/2.7.0-1
migrated and thereby postgresql-13-mysql-fdw is superseded (it might be in the
NBS list now).
But by that we are ready.
@Ubuntu-archive - please remove src:postgresql-13 and src:glom as
outlined in detail above.
**
The hint with the MP was merged, waiting for the next britney run.
If all works out just the two removals are left to be done.
** Description changed:
With the postgresql-14 transition in bug 1949579 done we want to clean
up the remainders of the former version.
- Steps from here:
+ Steps
Thanks Łukasz for clarifying that!
Comments:
- #4 was almost an MIR Ack
- #9 confirmed that a security review should not be needed.
All this happened long time in the past, I'm rechecking the state as of
today but most likely we will approve this rather soon.
--
You received this bug
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954465
Title:
KVM AIA User IPI
To manage notifications about this bug go to:
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954464
Title:
kvm SPR support for AMX
To manage notifications about this bug go to:
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954466
Title:
KVM Protection Keys for Supervisor Pages (PKS)
To manage notifications about this bug go to:
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954468
Title:
KVM Architectural LBRs
To manage notifications about this bug go to:
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954473
Title:
KVM Shared Virtual Memory (SVM)
To manage notifications about this bug go to:
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954472
Title:
KVM Scalable I/O Virtualization
To manage notifications about this bug go to:
** Tags added: intel-bug-december-2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954474
Title:
KVM notify VM Exit
To manage notifications about this bug go to:
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Summary for postgresql-mysql-fdw:
1. mysql-fdw needs >=2.7 for compatibility with postgresql-14 [1].
2. The new version adds tests (independent to PG-14) that fail on 32 bit
platforms like armhf [2][3]
3. Currently these test issues block proposed migration of the new version
Right now upstream
Reminder: It's been over 18 months since I reported this bug. python3
3.6.7-1~18.04 (bionic) and python3 3.8.2-0ubuntu2 (focal) are still not
fixed. The bugfix is a trivial one-line change, which I mentioned in
comment #1 over 13 months ago.
--
You received this bug notification because you are
Hi,
yes the security fixes in
https://launchpad.net/ubuntu/+source/samba/2:4.7.6+dfsg~ubuntu-0ubuntu2.26
might have affected that. Thanks Lorenzo for already identifying a candidate
and a config based workaround.
Assigning to security-team to have a look (as usual) at update
regressions.
**
I was happy for a second as I thought I found a related case, but this
is the very same case on askubuntu [1], so no more insights from there.
[1]: https://askubuntu.com/questions/1377700/ubuntu-20-04-3-nginx-
crashes-with-segfault
--
You received this bug notification because you are a member
Hi Bernd,
For your issues with apport-retrace, yes it should download the files it needs,
but in your case seems to fail for permission issues. Could you mabe just try
it with sudo and rebuild instead of a direct binary path like:
$ sudo apport-retrace --sandbox system --rebuild-package-info
Summary on postgresql-13
reverse dependencies are a bit tricky as some binary names transition to the
new source (like libpq-dev, libpq5) while others get new versioned names like
postgresql-13 -> postgresql-14.
Out of the following we can derive the list of binary packages we need to check:
apport information
** Attachment added: "Package.txt"
https://bugs.launchpad.net/bugs/1954596/+attachment/5547212/+files/Package.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954596
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1954596/+attachment/5547213/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected focal third-party-packages
** Description changed:
Table "groups" in otrs is now a reserved word for mysql 8, so upgrading from
ubuntu 18.04 to 20.04 "dies" in the middle of the process because otrs package
cannot update its tables.
This
I have experimented with glom a bit and the summary for now is:
1. it also fails in Debian, I filed bug [3]
2. it is a FTBFS regression in release independent to postgres
3. The newer glom 1.32 fails as well, Desktop let me know that it would need
the not yet packaged libxml++3.0
4. In a
Public bug reported:
Table "groups" in otrs is now a reserved word for mysql 8, so upgrading from
ubuntu 18.04 to 20.04 "dies" in the middle of the process because otrs package
cannot update its tables.
This bug is related to bug 1953033
There is a workaround though that has been filed here:
** Description changed:
- Table "groups" in otrs is now a reserved word for mysql 8, so upgrading
- from ubuntu 18.04 to 20.04 "dies" in the middle of the process because
- otrs package cannot update its tables.
+ Table "groups" in otrs is now a reserved word for mysql 8, so upgrading from
Thanks Sebastien for getting back to me.
Tools like arping are used as helpers within other tools or scripts. A very
important point of integration is the return code. Something returning non-zero
is considered to have failed.
It's simply not an option to sell people to add multiple lines of
Hi Bert,
thanks for the extra info.
I'm still confused by "Ubuntu 21.10+Virtualbox 6.1.30 run on the bare metal a
Ryzen 3 2200G" vs "highest level is always Ubuntu 14.04". Probably a
terminology thing what in virtualization is up and down :-)
Let me try to make sense of it :-)
So are we
Public bug reported:
With the postgresql-14 transition in bug 1949579 done we want to clean
up the remainders of the former version.
Once things are ready I'll update this and ask the AAs for the removals,
for now this tracks the effort to resolve the last few steps needed for
that.
TODO:
- get
postgresql-14 | 14.1-1ubuntu1 | jammy | source, amd64, arm64, armhf, ppc64el,
riscv64, s390x
postgresql-common | 234 | jammy | source, all
This is complete.
The cleanup will be getting glom to build as then we can remove
src:postgresql-13 tracked in bug 1954374
** Changed
Status => Incomplete until the agreed required TODOs are resolved.
Then ready for promotion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951066
Title:
[MIR] dh-elpa
To manage notifications
of the UI for extra checks
- no translation present, but none needed for this case (dev only)
** Changed in: dh-elpa (Ubuntu)
Status: New => Incomplete
** Changed in: dh-elpa (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification becau
pgsql-ogr-fdw@amd64 migration-reference/0 (was auto-scheduled it seems) is bad
as expected.
That should (tm) have been the last blocker.
Maybe I need to check installability in update_output after the next
run, I didn't do so so far ...
--
You received this bug notification because you are a
FYI: The debdiff really LGTM to resolve most of the weak points
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951066
Title:
[MIR] dh-elpa
To manage notifications about this bug go to:
python-sqlalchemy-utils fully resolved now
Now excuses lists the amd64 variant of pgsql-ogr-fdw as failing (it didn't
before)
https://autopkgtest.ubuntu.com/packages/p/pgsql-ogr-fdw/jammy/amd64
Here (as on the other architectures) a migration-reference run is running,
assuming that fails like
FYI: Pulling also dh-elpa would trigger a bunch of further dependencies
in universe, so this really is a no.go: libdebian-source-perl, dh-make-
perl, emacs-nox, libarray-utils-perl, libconfig-tiny-perl
But since you already said dh-elpa-helper is enough I'll focus on that
--
You received this
- no translation present, but none needed for this case
** Changed in: python-asgiref (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 subscrib
Thanks to RAOF the postgresql-server-dev-1 -> llvm issue is resolved.
python-sqlalchemy-utils was a test on an old version 0.36.8-2ubuntu2 failing
when openssl3 migrated. There now is a merge of the new version 0.37.8-1ubuntu1
with new tests.
Migration reference runs with that new version
Hi,
so to be sure to get it right. This is:
slow: BareMetal -> Ubuntu ??.?? -> Virtualbox -> Ubuntu 22.04
fast: BareMetal -> Ubuntu ??.?? -> Virtualbox -> Ubuntu before 22.04
That matches the screenshots, but not the description you gave.
So there must be something wrong here - I fail to see in
python-sqlalchemy-utils was not shown before, but now is a test fail for
postgresql-common
About the dependency to llvm-11-dev, clang-11.
Two things to know here, first of all that will sooner or later be llvm-13 due
to [1].
But right now there is an issue around s390x that blocks this:
Thank you,
it seems its llvm-11 dependency (incompatible with 13 on s390x, being worked on
in Debian) still prevents migration to -release. I'll have a more detailed look
tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1548486
Title:
Sleep hook in a subdirectory ignored but causes double execution of
previous hook
To manage
sqlalchemy worked out as expected, some tests are still in the queue but
others completed.
** No longer affects: sqlalchemy-i18n (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949579
All other entries on the transition tracker that are left are false
positives AFAICS.
Thereby all that is left I'm aware of is glom, which I found to be an FTBFS
(independent to postgresql-14). The work on glom can continue after
postgresql-14 migrates as we do not immediately remove
901 - 1000 of 23108 matches
Mail list logo
