Tested openssh-client/bionic-proposed,now 1:7.6p1-4ubuntu0.7 and
confirmed that group's and others' read permissions are now preserved.
Write and execute permissions are still removed, that is, a umask of
0133 seems to be applied.
** Tags removed: verification-needed-bionic
** Tags added: verifica
Thanks a lot! 0644 are really the important bits, so while the behavior
is still "user-surprising" it shouldn't cause any practical problems for
us.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bu
Public bug reported:
When I use ssh-keygen -R to remove a host from known_hosts it changes
permissions on the file. This causes problems particularly when used on
the global known hosts file (/etc/ssh/ssh_known_hosts), because then
only root can read it. Programs running non-interactively as non-r
Public bug reported:
1
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: avahi-utils 0.7-4ubuntu7.1
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
AptOrder
@xnox,
I think for bionic it may be possible to port changes from
https://github.com/xapienz/curl-debian-scripts (branch ppa_bionic) into
upstream ubuntu (currently debs are in PPA
https://launchpad.net/~xapienz/+archive/ubuntu/curl34). I can't
guarantee that such constructed binaries will work fo
*** This bug is a duplicate of bug 1683383 ***
https://bugs.launchpad.net/bugs/1683383
Same with Kubuntu 20.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1720364
Title:
Okay, this happens. But I can't help but wonder why it wasn't deprecated
first and why it still present in public headers then?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/188
nm -D -C libapt-pkg.so.5.0 | grep MMap (Ubuntu 18.04)
...
000c97d0 T MMap::Map(FileFd&)
000c9e10 T MMap::Sync(unsigned long, unsigned long)
000c9b80 T MMap::Sync()
000c9c20 T MMap::Close(bool)
000c97a0 T MMap::MMap(unsigned long)
000c9b40 T MMap::MMa
Public bug reported:
The "MMap::MMap(FileFd&, unsigned long)" function is missing in libapt-
pkg.so.6.0.0.
nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap
001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&,
OpProgress*, MMap**, bool)
0016e9c0 T pkgC
cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https:
Today on GitHub a ppc64el webhook was turned on for the systemd project. The
fuzzers (built with ASan) crashed there as soon as they started with something
like
```
757/758 fuzz-varlink:oss-fuzz-14708:address FAIL 0.02 s (exit status 1)
--- command ---
/usr/bin/env
/tmp/autopkgtest.vdKh
> it looks like @laney is listed there, which is probably appropriate
(he has admin access to the test systems, while I don't)
My understanding is that @laney can help with the infrastructure where
the tests are run. What usually happens on Ubuntu CI for the most part
has nothing to do with the in
By the way, @ddstreet would it be OK to mention that you maintain Ubuntu
CI at https://www.freedesktop.org/wiki/Software/systemd/autopkgtest/?
Currently it's almost impossible to figure out who is responsible for
it. At some point I assumed it was @xnox but it doesn't seem the case so
I don't even
Regarding i386, I downloaded the log and took a look at what failed
there. Turns out all the tests except for TEST-34-DYNAMICUSERMIGRATE,
where the global timeout kicked in, passed. Apparently, to judge from
https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/upstream, on Ubuntu
> Opened MR to blacklist TEST-15 and TEST-22
That PR on GitHub hasn't been merged yet so I think it's too soon to
turn those tests off.
> ah, ok - so I did look into this, or at least some failures really
similar to this, a while back, for bug 1831468.
As far as I can tell, several tests failed
Just to clarify, I think that it would be better to turn off the test
globally because we know it's flaky and unstable and we generally never
roll out globally flaky tests so as not to annoy contributors (I'm not
sure why Ubuntu CI should be different from any other CI system we use
upstream). And
Regarding the blacklist, we started to work on it in
https://github.com/systemd/systemd/issues/11195 (which was initially
about merging PRs where bugs were caught by Travis CI but ignored
because everybody was used to Ubuntu CI failing more often than not) and
ended up with a list of test I suggest
I agree ideally the test should be fixed but it's been flaky for a
couple of years and I didn't notice anyone who would be willing to try
to figure it out. I think it's time to admit nobody cares. Even if I'm
totally wrong and someone is interested in getting it to work on Ubuntu
CI, it should be p
In the meantime, I brought arm64 back almost as soon as
https://salsa.debian.org/systemd-team/systemd/merge_requests/34 was
merged. It looks promising except that the "upstream" test is flaky
there as well. It'd be great to turn it off on Ubuntu CI.
--
You received this bug notification because y
Good to know! Thank you!
Would it also be possible to mark the "upstream" test
(https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/control#L113) "flaky" or turn it
off altogether? We run it on CentOS and Arch anyway so it should be
safe. On Ubuntu CI it's particularly flaky an
> looks like this has been fixed already upstream
Yes. I merged the PR (created by @yuwata) fixing that this morning.
> looks like someone stopped that; it's only running tests for 12888,
12897, and 12899 currently.
In
https://github.com/systemd/systemd/issues/12891#issuecomment-506093934 I
aske
By the way, judging by http://autopkgtest.ubuntu.com/running#pkg-
systemd-upstream, it seems Ubuntu CI keeps running the tests for PR
12618, which was merged about a month ago.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
Anyway, as I said in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/comments/3,
I don't think Ubuntu CI in its current form is suitable for CI so I'll
just turn it off as soon as it starts failing again. I'm afraid I don't
have time for keeping an eye on it and reporting whatever co
I turned on bionic-amd64 and bionic-i386 yesterday. VMs no longer fail
to boot but apparently something else was broken on bionic-i386 while it
was off: https://github.com/systemd/systemd/issues/12891.
In https://github.com/systemd/systemd/pull/12861#issuecomment-506025351
both bionic-amd64 and bi
I'd add that it seems to me the "upstream" mode of Ubuntu CI doesn't
seem to be actively maintained because unlike the other CI systems used
upstream (which are usually fixed almost immediately), it can be broken
for weeks (or sometimes even months) which isn't suitable for CI. In
principle, if nob
That's correct. The assertion is at https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/boot-and-services#L421.
Regarding which release of Ubuntu is affected, I have to say I don't
know. The issue is mostly about "upstream" mode of Ubuntu CI, which can
be detected by checking a
Public bug reported:
Since https://github.com/systemd/systemd/pull/12430 was merged and
libsecomp was updated the test has been failing on Ubuntu CI:
https://github.com/systemd/systemd/issues/12709. By analogy with
https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9
To judge from
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/i386/s/systemd-upstream/20190521_185445_b37c3@/log.gz,
VMs seems to also be throwing kernel panics:
```
[0.894903] BIOS EDD facility
@pitti would it be possible to temporarily skip the tests where VMs are
rebooted to reduce the blast radius so to speak? I really don't want to
turn Ubuntu CI off completely.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
Public bug reported:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
Public bug reported:
Since
https://salsa.debian.org/systemd-team/systemd/commit/8d810fda9a640a932d6e7b32afd958fe75e36f5b
was merged Ubuntu CI has been failing with
```
Investigating (0) udev:amd64 < 237-3ubuntu10.13 -> 241-608-gfd541a5f08-0 @ii
pumU Ib >
Broken udev:amd64 Depends on dpkg:amd64
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817344
Title:
Ubuntu CI that runs tests via a
Hi Mark,
The problem is a little more complex.
For example, let's take package virtualbox-5.2 from official virtualbox repo
(https://download.virtualbox.org/virtualbox/debian/).
1. Deb package depends on libcurl3.
2. Its binary is linked to library with name 'libcurl.so.4'.
3. Its binary requires
I think Canonical should implement some solution like in #47 to support
both ABIs and keep it supported for some time, because all other apps
need some time to upgrade to libcurl4 (18.04 is LTS, so it looks like it
shouldn't have been upgraded to libcurl4 until 18.10).
--
You received this bug no
Hello César Bento Freire,
This is not related to libcurl.
But I would suggest you to download libxerces-c3.1 from ubuntu 17.10
repository and try to install it:
https://packages.ubuntu.com/artful/libxerces-c3.1
amd64:
http://mirrors.kernel.org/ubuntu/pool/universe/x/xerces-c/libxerces-c3.1_3.1.4
Public bug reported:
Hi.
My computer:
(Lubuntu):
evg@evg-Parallels-Virtual-Platform:$ uname -a
Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP
Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux
(Ubuntu):
Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon D
Public bug reported:
OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard
ssh-keygen -v -D /usr/lib/libeTPkcs11.so
debug1: manufacturerID cryptokiVersion 2.20 libraryDescription
libraryVersion 9.1
debug1: label manufacturerID model
serial <> flags 0x60d
C_GetAttributeVal
I have the same problem & don't know what to do.
Linux Mint 18.1
Kodi version: 2:17.0~git20170210.1529-final-0xenial
Trying to get in third-party repo. Kodi's flooding into file /var/log/syslog
>30gb of two strings:
extern "Python": function Cryptography_rand_bytes() called, but
@ffi.def_extern(
I have simmilar bug when exiting fullscreen mode on youtube. Everything
freezes, but I still can move mouse and do ctrl+alt+f1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
** Changed in: python3.4 (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/python3.4/+question/270210
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in
libboost compilation failed because of a lack of libpython3.4.so
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1482990
Title:
ld -lpython3.4 failed
Status in python3.4
Public bug reported:
#ld -lpython3.4 --verbose
attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.so failed
attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.a failed
attempt to open //usr/local/lib32/libpython3.4.so failed
attempt to open //usr/local/lib32/libpython3.4.a failed
attempt t
Public bug reported:
# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
# apt-cache policy systemd-services
systemd-services:
Installed: 204-5ubuntu20.13
Candidate: 204-5ubuntu20.13
Version table:
*** 204-5ubuntu20.13 0
500 http://archive.ubuntu.com/ubuntu/
Public bug reported:
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt:
Installed: 1.0.1ubuntu2.10
apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
7A82B743B9B8E46F12C733FA4759FA960E27C0A6
apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here
apt-k
44 matches
Mail list logo