** Changed in: krb5 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: krb5 (Ubuntu)
Milestone: ubuntu-22.01 => ubuntu-22.02
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in
Public bug reported:
Debian is shipping nss 3.73.1, but that is not an ESR release. Ubuntu is
on 3.68, which is ESR, but two releases behind: upstream has 3.68.2.
Here are upstream's release notes:
3.68.1: https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/jFIuiWbCphk
Changes:
- Bug 173
Public bug reported:
We went ahead of debian because of openssl3:
krb5 (1.19.2-0ubuntu1) jammy; urgency=medium
[ Sam Hartman ]
* New Upstream version
* Depend on tex-gyre, Closes: #997407
[Simon Chopin]
* d/p/0012-Fix-softpkcs11-build-issues-with-openssl-3.0.patch:
Cherry-picked fr
This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-3
---
cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium
[ Andreas Hasenack ]
* Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152)
-- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100
** Changed in
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1957076
Title:
sync cyrus-sasl2 2.1.27+dfsg2-3
** Changed in: cyrus-sasl2 (Ubuntu)
Milestone: None => ubuntu-22.01
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1957076
Title:
sync cyrus-sasl2 2.1.27+dfsg2-3
We were recently hit by bug #1956833, where GSS-SPNEGO was suddenly
disabled and nobody noticed until an app tried to use it.
For that case, I'm thinking about a very simple test that would be like
this:
for algo in $ALGORITHMS; do
saslpluginviewer -m $algo > /dev/null || {
echo "Algorithm
Public bug reported:
It has the fix for bug #1956833, which is our only delta presently.
** Affects: cyrus-sasl2 (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: Triaged
** Tags: needs-merge
--
You received this bug notification because you are
** Bug watch added: Debian Bug tracker #1003355
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003355
** Also affects: cyrus-sasl2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003355
Importance: Unknown
Status: Unknown
--
You received this bug notification
ance: Undecided => High
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => In Progress
** Changed in: cyrus-sasl2 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
In the jammy build log
(https://launchpadlibrarian.net/570726294/buildlog_ubuntu-jammy-
amd64.cyrus-sasl2_2.1.27+dfsg2-2build1_BUILDING.txt.gz), we have this
error which is not present in the impish build for example:
checking for SPNEGO support in GSSAPI libraries... ../configure: line 18854:
ac
Impish also works:
root@i1:~# saslpluginviewer | head | grep SPNEGO
SCRAM-SHA-1 SCRAM-SHA-256 GS2-IAKERB GS2-KRB5 GSSAPI GSS-SPNEGO DIGEST-MD5
EXTERNAL CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS
SCRAM-SHA-1 SCRAM-SHA-256 GS2-IAKERB GS2-KRB5 GSSAPI GSS-SPNEGO DIGEST-MD5
CRAM-MD5 NTLM PLAIN LOGIN ANO
Public bug reported:
In jammy:
root@j1:~# saslpluginviewer | head | grep SPNEGO
root@j1:~#
Confirming against a windows 2016 active directory server, fully patched:
root@j1:~# ldapwhoami -Y GSS-SPNEGO
ldap_sasl_interactive_bind: Unknown authentication method (-6)
additional info: SASL(-4
Maybe https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101346 ?
** Also affects: gcc-11 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: GCC Bugzilla #101346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101346
--
You received this bug notification because you are a member
Actually, this may be an ICE. Further up in the logs we see:
[ 37%] Building CXX object
src/client/lttng/CMakeFiles/mirclientlttng-static.dir/input_receiver_report.cpp.o
cd /<>/build-amd64/src/client/lttng && /usr/bin/c++
-DCLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" -DEGL_NO_X11 -DLOG_NDEB
Fix was merged usptream, and 2.13.1 contains it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
https://bugs.launchpad.net/bugs/1953065
Title:
2.13.0 FTBFS
Status in LTTng-UST:
Unknown
Status in ust packa
Disco is EOL, and the package builds fine in current devel release.
Closing the bug.
** Changed in: heimdal (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
ht
** Changed in: heimdal (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/1946860
Title:
Merge heimdal from Debian unstable for 22.0
** Changed in: heimdal (Ubuntu)
Milestone: ubuntu-21.11 => ubuntu-21.12
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/1946860
Title:
Merge heimdal from Debian unstabl
** Tags removed: update-excuses
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1953200
Title:
[jammy] FTBFS with boost
Status in mir package in U
Public bug reported:
https://launchpad.net/ubuntu/+source/mir/2.4.1-0ubuntu3
[ 38%] Building CXX object
src/client/CMakeFiles/mirclientobjects.dir/event_printer.cpp.o
cd /<>/build-amd64/src/client && /usr/bin/c++
-DCLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" -DEGL_NO_X11 -DLOG_NDEBUG=1
-
** Changed in: ust (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: ust (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
Public bug reported:
I tried to merge ust from debian into ubuntu, to fix a build-time
dependency, but stumbled on an FTBFS with that version.
I filed upstream bug at https://bugs.lttng.org/issues/1337
It basically happens in some new test cases that were added in 2.13.0
and crash when we build
tatus: New => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/195
Public bug reported:
dh_missing is flagging some profiles that are installed by the Makefile,
but not included in debs:
$ cat ../build.log | grep dh_missing | grep -v /local/ | grep etc/apparmor\\.d
dh_missing: warning: etc/apparmor.d/php-fpm exists in debian/tmp but is not
installed to anywher
I'm having to add the following just to allow samba to be started by systemd,
and I'm still missing net_admin capa, which I'm reluctant to add:
--- a/profiles/apparmor.d/usr.sbin.smbd
+++ b/profiles/apparmor.d/usr.sbin.smbd
@@ -24,12 +24,22 @@
capability sys_resource,
capability sys_tty_conf
Related: https://gitlab.com/apparmor/apparmor/-/issues/203
** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #203
https://gitlab.com/apparmor/apparmor/-/issues/203
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ap
Public bug reported:
ubuntu jammy
apparmor-profiles 3.0.3-0ubuntu3
samba 2:4.13.5+dfsg-2ubuntu3
smbd:
Nov 25 14:59:56 jammy-samba-apparmor systemd[1]: Starting Samba SMB Daemon...
Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.586080] audit: type=1400
audit(1637852396.969:77):
> Our kernel ships wireguard modules by default anyway, and one can
configure wireguard via networkd and soon via netplan. Which is our
default tooling to interact with the wireguard kernel module.
How should we generate the wireguard keys without `wg`? openssl? It's a
significant deviation from u
Public bug reported:
Before trying to delete a user, userdel checks if the user exists. The
problem is that this check is done using getpwnam(), which will query
all nss sources from /etc/nsswitch.conf.
If a system has, for example, LDAP enabled, and userdel is called with
the name of a user that
** Changed in: heimdal (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/1946860
Title:
Merge heim
Do we even know for sure this krb5-k5tls is enough for fips compliance,
and that it replaces *all* crypto code in kerberos with openssl calls?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launch
For backports, a straight build of 1.6.2 would perhaps be enough. Might
not seem a version change big enough for backports, but as we have seen,
it does introduce a change of behavior that impacts existing firewall
scripts.
--
You received this bug notification because you are a member of Ubuntu
l)
Status: In Progress => Confirmed
** Changed in: base-files (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in: base-files (Ubuntu Focal)
Status: In Progress => Confirmed
** Changed in: base-files (Ubuntu Xenial)
Assignee: Andreas Hasena
I tested this last change, and it does exactly what we wanted for
iptables, the tool. And since that behavior is shared with all tools of
the iptables suite, it means iptables-restore got that fix too (good!),
but it also introduces a change in behavior for iptables-restore (bad!).
When compared t
Excellent progress Eric, thanks!
I'll give it a try.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
Status in iptab
Thanks for the b3 version!
It restores the bionic implicit lock behavior (as if -w was given), but
when given a specific value, in the end it ignores that it couldn't
acquire the lock and moves on:
In all these tests, I have a lock held.
We have a chain called "andreas". See how -L waits 1 seco
+1 for a backport, I don't think 1.6.2 is suitable for an SRU,
specifically about one change I noticed with test packages that I think
can break existing firewall scripts.
The locking code is shared between tools, so in 1.6.2, not only do we
get iptables-{save,restore} with -w support, but iptable
yeah, it's specifically restart that we want to check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1913810
Title:
restart doesn't test for syntax errors
Status in opens
Actually, Christian didn't explicitly ack the stable releases in that
comment (but he did in the MPs I raised for the seed changes). I'll ask
him tomorrow to flip the statuses.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to r
Given Christian's comments in comment #6, and the fact that the seed
changes were done, I'm going to mark the tasks for the stable releases
as "fix committed"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Meeting minutes: https://new.ubottu.com/meetingology/logs/ubuntu-
meeting/2021/ubuntu-meeting.2021-03-25-15.00.moin.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/388605
I'll provide MPs for bionic, focal and groovy to change the seeds to
pull rsyslog-gnutls into main, as discussed in #ubuntu-meeting with
Foundations today, and then ping an archive admin.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
We would like to retroactively promote rsyslog-gnutls, a binary package
built from src:rsyslog (subject of this completed MIR), into main.
rsyslog-gnutls provides a gnutls plugin which allows rsyslog to encrypt
the data it sends to log servers. We believe this is a common scenario,
and very much n
** Also affects: rsyslog (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Hirsute)
Importance: Undecided
Assignee: Kees Cook (kees)
Status: Fix Released
postgresql-common amd64 and i386: passed after a retry
ubuntu-fan: see previous comment, known flaky test, and analysis of the test
output shows that the test actually passed. I retried both amd64 and s390x, but
I ask the SRU team to consider those runs green if they failed again (update:
amd64
ubuntu-fan dep8 failures are due to
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1830180. It
was fixed in focal+, but in bionic it remains flaky. Explanation is in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-
fan/+bug/1830180/comments/1
I'll retry it once or twice, but we can see
Public bug reported:
Tested openssh on bionic and groovy, same issue.
The switch to systemd lost the ability to do a sanity check on the
config file (via sshd -t) before attempting to restart sshd. This was
originally bug #624361 in the SySV days, fixed in the initscript back
then.
The sysv scri
Just saw this in bionic, I guess it's not important enough for an SRU?
# apparmor_parser -r -T -W --Complain /etc/apparmor.d/pam_roles
/etc/apparmor.d/usr.sbin.sshd
Warning failed to create cache: pam_roles
Warning failed to create cache: usr.sbin.sshd
--
You received this bug notification beca
TL;DR verification-succeeded
Ok, so here are the details.
I have two vms: one called orig-audit-bionic, the other called sru-
audit-bionic, where I ran the script from comment #23 over the weekend
in multiple scenarios. With auditd-1:2.8.2-1ubuntu1, the bug is
reproduced after a few hours, wherea
I prepared two bionic instances to run over the weekend.
One is running auditd from bionic, and the other is running the SRU
proposed package.
I have auditd being restarted via this script in both (just the email message
is different, to say which package it was):
#!/bin/bash
result=0
while /b
Dr. Harbott, would you be able to test the new audit packages in bionic-
proposed? The SRU team is reluctant to approve this update without some
sort of confirmation that it fixes the bug, and I haven't been able to
reproduce it myself.
--
You received this bug notification because you are a memb
Since it's difficult to reproduce the bug, what I'm going to do is setup
a system with the previous auditd, setup some rules, confirm they are
working, then upgrade, and confirm it keeps working, also after a
reboot.
# Bionic verification
auditd from bionic:
auditd:
Installed: 1:2.8.2-1ubuntu1
All regressions have been resolved after some retries.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330
Title:
Installing auditd sometimes fails in post-inst
Status i
I'm going over the DEP8 failures
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330
Title:
Installing auditd sometimes fails in post-inst
Status in audit package in Ubu
Package uploaded to the SRU queue
** Changed in: audit (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330
Title:
Instal
** Description changed:
[Impact]
Sometimes, auditd will get stuck when starting up, causing systemd to
kill it after a while since it (systemd) never got the start
notification.
Upstream troubleshooted this to be caused by calling a syslog() function
inside a signal handler.
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ Sometimes, auditd will get stuck when starting up, causing systemd to
+ kill it after a while since it (systemd) never got the start
+ notification.
- * justification for backporting the fix to t
Yikes @Kodiak, sounds painful :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1848330
Title:
Installing auditd sometimes fails in post-inst
Status in audit package in Ubu
** Description changed:
- This happens sometimes when installing auditd on Ubuntu 18.04.2, most
- installations work successfully, though. Re-running the install also
- fixes the issue, but the failure breaks our automation. The log from the
- failure looks like this:
+ [Impact]
+
+ * An explana
I'm having difficulties reproducing the bug, to validate the patch. I
build bionic test packages with the patch mentioned earlier, if someone
wants to test: https://launchpad.net/~ahasenack/+archive/ubuntu/audit-
startup-hang-1848330
--
You received this bug notification because you are a member
correct source package name is audit, not auditd (apparently we have/had
both)
** Changed in: auditd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Bug watch added: Debian Bug tracker #962451
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962451
** Also affe
Public bug reported:
This basically the same bug as #1894907, but there I decided to disable
docs rebuilding, after checking that none of the patches were against
the docs source.
Furthermore, we should probably fix these lintian issues:
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file
usr
I filed https://bugs.launchpad.net/ubuntu/+source/cyrus-
sasl2/+bug/1898593 to properly fix the doc building with sphinx.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1
I got as far as this collection of patches:
https://paste.ubuntu.com/p/wvRzpByDXT/ :
--- a/docsrc/exts/sphinxlocal/writers/manpage.py
+++ b/docsrc/exts/sphinxlocal/writers/manpage.py
@@ -14,7 +14,6 @@
from docutils import nodes
from sphinx.writers.manpage import (
-MACRO_DEF,
ManualPa
I think the remaining scenario is (b) (look up in the bug description),
and (c) is just a wildcard scenario ("anything else I didn't think of").
For (b), I think the more likely case would be another base-files SRU without
the fix from this bug here, and where the user would have:
- base-files in
I meant, see *also* https://bugs.launchpad.net/bugs/1895302, no idea yet
if it's related.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1888575
Title:
Split motd-news
ecided; assignee=andr...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=focal;
> sourcepackage=livecd-rootfs; component=main; status=Invalid;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=focal;
> sourcepackage=ubuntu-meta; compon
root@xenial-base-files:~# apt-cache policy ubuntu-server
ubuntu-server:
Installed: 1.361.6
Candidate: 1.361.6
Version table:
*** 1.361.6 500
500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64
Packages
100 /var/lib/dpkg/status
1.361.5 500
500 http
Sorry again, I jumped he gun. I don't know how to do k-ii and k-iii, I
thought (k) was one of the original test cases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/18885
Sorry, I wasn't clear. I'll re-run (k) with ubuntu-meta from xenial
proposed now, with base-files from xenial-updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/18885
I have another upload for base-files, for bug #1895302 (see comment
#23). I can re-run the (k) test case, and of course the testcase for
that bug specifically.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubun
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
eant to be enabled on a server.
** Also affects: base-files (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: base-files (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: base-files (Ubuntu Xenial)
Assignee: (unassigned) => Andreas Hasenack (ahas
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
- A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
** Description changed:
[Impact]
+ A fresh install of base-files, like done when using debootstrap, using the
base-files from the -updates repository (in the case of ubuntu stable
releases), will leave an empty /etc/default/motd-news.wasremoved file. This
file is an artifact of the mechanism
atus: New
** Changed in: base-files (Ubuntu Focal)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: base-files (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/390766
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/
Thanks for the review laney
I did run the sssd dep8 tests, which exercise openldap, but not a
replication.
So I followed the server guide on setting up replication with TLS
(https://ubuntu.com/server/docs/service-ldap-replication and
https://ubuntu.com/server/docs/service-ldap-with-tls) and confi
Nor the upgrade after that, ugh. Fixing.
** Changed in: base-files (Ubuntu)
Importance: Undecided => High
** Changed in: base-files (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: base-files (Ubuntu)
Status: New => In Progress
--
You rece
I filed https://bugs.launchpad.net/ubuntu/+source/base-
files/+bug/1895302 for that. Do you happen to know a good way to test
the first-time installation of base-files with debootstrap? It would be
awesome if I could give it a ppa to consider, in addition to the
archive, and it would then just pick
I think this postinst bit never considered the fresh install case:
# special case of having /etc/default/motd-news removed by hand
# signal the motd-news-config package that this happened, so that
# it does not put back the file with default contents which would
# re-enable motd-news
motd_news_con
** Summary changed:
- FTBFS with sphinx 2.4: cannot import name 'NoUri'
+ FTBFS with sphinx 2.4
** Description changed:
- Getting this failure to build on groovy:
+ cyrus-sasl2 ships with a sphinx extension to build its documentation,
+ and this extension was based on a very old sphinx version.
*** This bug is a duplicate of bug 1894907 ***
https://bugs.launchpad.net/bugs/1894907
** This bug has been marked a duplicate of bug 1894907
FTBFS with sphinx 2.4: cannot import name 'NoUri'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Public bug reported:
When debootstrapping groovy, we see an empty /etc/default/motd-
news.wasremoved file.
- groovy: base-files 11ubuntu12
-rw-r--r-- 1 root root 0 set 11 10:20 /etc/default/motd-news.wasremoved
If motd-news-config is later installed, maybe via ubuntu-server, then
the presence of
Switched bug to "New" so it can be considered by the release team.
** Changed in: openldap (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.
Public bug reported:
sed -e 's,[@]LIB_DOOR[@],,g' -e 's,[@]SASL_DL_LIB[@],-ldl,g' -e
's,[@]LIBS[@],-lresolv ,g' -e 's,[@]VERSION[@],2.1.27,g' -e
's,[@]libdir[@],/usr/lib/x86_64-linux-gnu,g' -e 's,[@]prefix[@],/usr,g' -e
's,[@]exec_prefix[@],/usr,g' -e 's,[@]includedir[@],/usr/include,g' <
../l
** Bug watch added: Debian Bug tracker #955095
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955095
** Also affects: cyrus-sasl2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955095
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
Hmm, the impact of having that file there in this situation is that if
you *then* install the motd-news-config package, it will see that file,
remove it, and install /etc/default/motd-news with ENABLED=0 instead of
ENABLED=1.
Can you easily remove /etc/default/motd-news.wasremoved manually in your
The sssd DEP8 tests, which exercise the ldap server a bit, passed
locally:
...
autopkgtest [09:48:35]: summary
ldap-user-group-ldap-auth PASS
ldap-user-group-krb5-auth PASS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
Getting this failure to build on groovy:
Extension error:
Could not import extension sphinxlocal.builders.manpage (exception: cannot
import name 'NoUri' from 'sphinx.environment'
(/usr/lib/python3/dist-packages/sphinx/environment/__init__.py))
make[2]: *** [Makefile:1166: m
** Description changed:
- To be filled
+ Groovy has openldap 2.4.51
+
+ Upstream made two quick new releases after that: 2.4.52 and 2.4.53. A
+ crash was reported in the mailing list:
https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/thread/NKOM6DI7RQY6FDLRZGSGYJS
Public bug reported:
To be filled
https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/thread/NKOM6DI7RQY6FDLRZGSGYJSGONKIRFEP/
** Affects: openldap (Ubuntu)
Importance: High
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Description
Xenial verification
Versions we are handling:
base-files 9.4ubuntu4.12 -> 9.4ubuntu4.13
ubuntu-server 1.361.4-> 1.361.5
motd-news-config n/a -> 9.4ubuntu4.13
Note that in xenial, at the moment, ubuntu-server is not pre-installed
in the images.
This verification is quite long, given the a
For the focal verification, I added a secondary test (j2) like I did for
bionic, and that is a release upgrade from an updated focal non-server
system to groovy, using the base-files package from focal-proposed, thus
simulating the release upgrade once this SRU is complete.
Result is correct as we
Bionic verification
This verification is quite long, given the amount of tests involved.
TL;DR All tests from (a) to (j) passed as required.
bionic verification succeeded.
Latest updates from bionic:
base-files:
*** 10.1ubuntu2.9 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updat
Focal verification
This verification is quite long, given the amount of tests involved.
TL;DR All tests from (a) to (j) passed as required.
focal verification succeeded.
Details below.
a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
apt install base-files
- upgrade
601 - 700 of 1317 matches
Mail list logo
