[Touch-packages] [Bug 1819589] Re: Ubuntu CI is broken

Should be fixed with https://salsa.debian.org/systemd- team/systemd/commit/bd89a706b18796074d50bcf2a0cbd29de56ac542 . I'll close this once the retried PRs go green. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: systemd (Ubuntu)

[Bug 1819589] Re: Ubuntu CI is broken

Should be fixed with https://salsa.debian.org/systemd- team/systemd/commit/bd89a706b18796074d50bcf2a0cbd29de56ac542 . I'll close this once the retried PRs go green. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: systemd (Ubuntu)

Re: [systemd-devel] Permanently Ban for Dovecot

Hello Onno, Onno Verbeek [2019-03-10 14:52 +0100]: > I’ve setup my firewalls pretty tight, I just run into a problem with the > firewall for dovecot. > When someone is trying to login, they get blocked after 5 try’s. I would like > to ban the ip permanently, for now the ban seems to be cancelled

Accepted cockpit 189-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Mar 2019 15:51:24 + Source: cockpit Architecture: source Version: 189-1 Distribution: experimental Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Changes: cockpit (189-1) experimental

Accepted cockpit 189-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Mar 2019 15:51:24 + Source: cockpit Architecture: source Version: 189-1 Distribution: experimental Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Changes: cockpit (189-1) experimental

Bug#919387: autopkgtest: missing build dependency on sysvinit-utils

Control: tag -1 moreinfo Hello Ritesh, Ritesh Raj Sarraf [2019-01-15 18:15 +0530]: > One of the build time test cases make a call to the pidof command. > This command is provided through the sysvinit-utils package. > > So, either the sysvinit-utils package needs to be added as a dependency > or

Bug#911408: dnsmasq breaks systemd autopkgtest

Hello all, Paul Gevers [2018-10-19 21:07 +0200]: > With a recent upload of dnsmasq the autopkgtest of systemd fails in > testing when that autopkgtest is run with the binary packages of dnsmasq > from unstable. I fixed (or rather, worked around) this recently in https://github.com/systemd/systemd

Bug#911408: dnsmasq breaks systemd autopkgtest

Hello all, Paul Gevers [2018-10-19 21:07 +0200]: > With a recent upload of dnsmasq the autopkgtest of systemd fails in > testing when that autopkgtest is run with the binary packages of dnsmasq > from unstable. I fixed (or rather, worked around) this recently in https://github.com/systemd/systemd

[Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

Thanks Iain! I'll keep an eye on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817344 Title: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results To ma

[Touch-packages] [Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

Thanks Iain! I'll keep an eye on this. -- 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 autopkgtest for systemd on GitHub repo

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

This happens in about half of the xenial semaphoreci.com instances as well: $ uname -a Linux semaphore-light-1809b 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, whi

[Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

This happens in about half of the xenial semaphoreci.com instances as well: $ uname -a Linux semaphore-light-1809b 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which i

[Touch-packages] [Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

Another example: https://github.com/systemd/systemd/pull/11802 refers to the correct amd64 log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/amd64/s /systemd-upstream/20190222_161608_7fe1f@/log.gz

[Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

Another example: https://github.com/systemd/systemd/pull/11802 refers to the correct amd64 log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/amd64/s /systemd-upstream/20190222_161608_7fe1f@/log.gz

Bug#917128: Bug

Control: found -1 241-1 Wolfgang Walter [2019-02-23 11:39 +0100]: > The bug is back again: 241-1 again has this problem. So this broke again due to https://github.com/systemd/systemd/commit/3907446f02 or https://github.com/systemd/systemd/commit/73d2bb08816 , i. e. as part of https://github.com/

Bug#917128: Bug

Control: found -1 241-1 Wolfgang Walter [2019-02-23 11:39 +0100]: > The bug is back again: 241-1 again has this problem. So this broke again due to https://github.com/systemd/systemd/commit/3907446f02 or https://github.com/systemd/systemd/commit/73d2bb08816 , i. e. as part of https://github.com/

[Touch-packages] [Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

It seems to me that the logs are internally consistent, i. e. the mentioned UPSTREAM_PULL_REQUEST in the log does match the test results. But they get sent to the wrong PR, i. e. to the wrong statuses API. E. g. https://api.github.com/repos/systemd/systemd/commits/99894b867f1293f56d181d62f5015c5a0

[Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

It seems to me that the logs are internally consistent, i. e. the mentioned UPSTREAM_PULL_REQUEST in the log does match the test results. But they get sent to the wrong PR, i. e. to the wrong statuses API. E. g. https://api.github.com/repos/systemd/systemd/commits/99894b867f1293f56d181d62f5015c5a0

Accepted upower 0.99.10-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 24 Feb 2019 07:23:30 + Source: upower Architecture: source Version: 0.99.10-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Changes: upower (0.99.10-1) unstable

Bug#923082: can't disable systemd-resolved

Control: tag -1 moreinfo Hello Toni, Toni [2019-02-23 23:05 +]: > I can't disable systemd-resolved, which prevents me from running my own > DNS setup: systemd-resolved.service is not enabled by default in Debian. If you enabled it, what prevents you from disabling it again? (systemctl disabl

Bug#923082: can't disable systemd-resolved

Control: tag -1 moreinfo Hello Toni, Toni [2019-02-23 23:05 +]: > I can't disable systemd-resolved, which prevents me from running my own > DNS setup: systemd-resolved.service is not enabled by default in Debian. If you enabled it, what prevents you from disabling it again? (systemctl disabl

Accepted python-dbusmock 0.18.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Feb 2019 12:45:09 + Source: python-dbusmock Architecture: source Version: 0.18.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Martin Pitt Changes: python-dbusmock

Accepted cockpit 188-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 20 Feb 2019 16:22:20 + Source: cockpit Architecture: source Version: 188-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Changes: cockpit (188-1) unstable; urgency

Cockpit 188 released

/cockpit-project/cockpit/releases/tag/188 Take care, Martin Pitt ___ cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org To unsubscribe send an email to cockpit-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org

Bug#922501: ERROR: No runner implements step with keys grub, root-part, device, console, root-fs

Hello Antonio, Antonio Terceiro [2019-02-18 22:44 -0300]: > The vmdb2 usage changed brutally, and broke the specification file > produced by autopkgtest-build-qemu. I don't think this can't really be > fixed in vmdb2 at this point, not only because this makes the > specification format a lot bette

Bug#922671: autopkgtest-build-qemu image does not boot due to wrong root device

Package: autopkgtest Version: 5.9 Even after fixing #916407 and #922501, these images still don't work: # autopkgtest-build-qemu stretch /tmp/s.img http://ftp.de.debian.org/debian This succeeds, and gives me an image. But trying to boot it fails: | Booting a command list | | Loading Linux

Bug#915407: what's with logind?

Control: tag -1 pending Hello Adam, Adam Borowski [2019-02-18 22:50 +0100]: > You just made an upload of src:systemd, without the fix for libpam-systemd > alternative. Right, sorry for the bad timing. This was an urgent embargoed security fix. Last time I looked at this, the new package names

Bug#915407: what's with logind?

Control: tag -1 pending Hello Adam, Adam Borowski [2019-02-18 22:50 +0100]: > You just made an upload of src:systemd, without the fix for libpam-systemd > alternative. Right, sorry for the bad timing. This was an urgent embargoed security fix. Last time I looked at this, the new package names

Accepted systemd 240-6 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Feb 2019 13:54:04 + Source: systemd Architecture: source Version: 240-6 Distribution: unstable Urgency: high Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Closes: 918764 919206 Changes: systemd (240

Bug#922501: ERROR: No runner implements step with keys grub, root-part, device, console, root-fs

Package: vmdb2 Version: 0.13.2+git20190215-1 I'm trying to build a stretch VM image using autopkgtest's tool: autopkgtest-build-qemu stretch /tmp/autopkgtest-stretch-amd64.qcow2 which under the hood calls vmdb2 --verbose --image=/tmp/autopkgtest-stretch-amd64.qcow2.raw /tmp/config I'm a

Accepted libssh 0.8.6-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Feb 2019 20:43:44 + Source: libssh Architecture: source Version: 0.8.6-3 Distribution: unstable Urgency: medium Maintainer: Laurent Bigonville Changed-By: Martin Pitt Closes: 922073 Changes: libssh (0.8.6-3) unstable

Bug#922073: libssh autopkgtest is flaky due to test service startup race

Control: tag -1 pending Hello Steve, Steve Langasek [2019-02-11 10:58 -0800]: > The libssh 'libssh-server' autopkgtest is badly racy Whoops, sorry for the blunder. Thanks for the report! > A more correct fix would be to run the server in the foreground, let it > background itself once it's list

Bug#919206: please apply upstream fix from pull #11417

Control: tag -1 pending Hello Rob, Rob J. Epping [2019-02-07 16:12 +0100]: > The patch in [1] is simple and solves the issue also in the current version. > > [1] Cherry-picked, thanks! Martin ___ Pkg-s

Bug#919206: please apply upstream fix from pull #11417

Control: tag -1 pending Hello Rob, Rob J. Epping [2019-02-07 16:12 +0100]: > The patch in [1] is simple and solves the issue also in the current version. > > [1] Cherry-picked, thanks! Martin

Accepted cockpit 187-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Feb 2019 13:27:11 + Source: cockpit Architecture: source Version: 187-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Changes: cockpit (187-1) unstable; urgency

Re: Different cockpit versions between RHEL & CentOS 7.6

Hello Yigal, Yigal Korman [2019-02-06 8:32 +0200]: > Anyone knows why RHEL 7.6 provides v173.1 while CentOS has a newer v176? > Usually packages have the same version on both... They do, but you have to consider Base vs. Extras. Both RHEL 7.6 and CentOS 7.3 have Cockpit 173 in base http://mir

Accepted systemd 240-5 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 27 Jan 2019 21:33:07 + Source: systemd Architecture: source Version: 240-5 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Closes: 919390 920018 Changes: systemd

Re: systemd_240-5_source.changes REJECTED

Hello systemd team, Debian FTP Masters [2019-01-28 11:05 +]: > systemd_240-5.dsc: Invalid size hash for systemd_240.orig.tar.gz: > According to the control file the size hash should be 7581986, > but systemd_240.orig.tar.gz has 7582001. OK, so our pristine-tar in git is clearly not matching t

Bug#919390: Bug #919390 in systemd marked as pending

Control: tag -1 pending Hello, Bug #919390 in systemd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/systemd-team/systemd/commit/40df7df1f6c4812fa7b074c5d48dcf

Bug#920018: Bug #920018 in systemd marked as pending

Control: tag -1 pending Hello, Bug #920018 in systemd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/systemd-team/systemd/commit/59be1833846225c29a5241fdc63e02

Bug#920018: Please give this bug attention.

Hello Nye, Nye Liu [2019-01-23 14:16 -0800]: > Please apply https://github.com/systemd/systemd/pull/11527 It's in the pipeline now, I need to sort out some git paperwork issue with Felipe. But either way, I'll upload the fix tomorrow. (Sorry, just back from meeting/devconf.cz week with essential

Bug#920018: Please give this bug attention.

Hello Nye, Nye Liu [2019-01-23 14:16 -0800]: > Please apply https://github.com/systemd/systemd/pull/11527 It's in the pipeline now, I need to sort out some git paperwork issue with Felipe. But either way, I'll upload the fix tomorrow. (Sorry, just back from meeting/devconf.cz week with essential

Bug#920018: Please give this bug attention.

Hello Nye, Nye Liu [2019-01-23 14:16 -0800]: > Please apply https://github.com/systemd/systemd/pull/11527 It's in the pipeline now, I need to sort out some git paperwork issue with Felipe. But either way, I'll upload the fix tomorrow. (Sorry, just back from meeting/devconf.cz week with essential

Bug#919390: Bug #919390 in systemd marked as pending

Hello Felipe, Felipe Sateler [2019-01-26 0:04 +]: > Bug #919390 in systemd reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/systemd-team/systemd/comm

Accepted cockpit 186-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Jan 2019 16:25:51 + Source: cockpit Architecture: source Version: 186-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Changes: cockpit (186-1) unstable; urgency

Accepted media-player-info 24-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 20 Jan 2019 14:39:01 + Source: media-player-info Binary: media-player-info Architecture: source Version: 24-2 Distribution: unstable Urgency: medium Maintainer: Martin Pitt Changed-By: Martin Pitt Description: media

Accepted editmoin 1.17-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 20 Jan 2019 14:46:38 + Source: editmoin Binary: editmoin Architecture: source Version: 1.17-4 Distribution: unstable Urgency: medium Maintainer: Martin Pitt Changed-By: Martin Pitt Description: editmoin - edit

Accepted python-distutils-extra 2.42 (source) into unstable

Changed-By: Martin Pitt Description: python-distutils-extra - enhancements to the Python build system python3-distutils-extra - enhancements to the Python3 build system Closes: 862182 894897 909992 912859 Changes: python-distutils-extra (2.42) unstable; urgency=medium . [ Ondřej Nový

Accepted umockdev 0.12.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 20 Jan 2019 10:18:27 + Source: umockdev Binary: umockdev libumockdev0 libumockdev-dev gir1.2-umockdev-1.0 Architecture: source Version: 0.12.1-2 Distribution: unstable Urgency: medium Maintainer: Martin Pitt Changed-By

Bug#919799: cockpit: FTBFS (failing tests)

Control: retitle -1 FTBFS without a loopback inet device Control: severity -1 normal Hello Santiago, Santiago Vila [2019-01-19 17:35 +]: > I tried to build this package in buster but it failed: This fails a lot of tests like this: | cockpit-protocol:ERROR:src/common/test-webserver.c:57:setup

Bug#919799: cockpit: FTBFS (failing tests)

Control: retitle -1 FTBFS without a loopback inet device Control: severity -1 normal Hello Santiago, Santiago Vila [2019-01-19 17:35 +]: > I tried to build this package in buster but it failed: This fails a lot of tests like this: | cockpit-protocol:ERROR:src/common/test-webserver.c:57:setup

[Pkg-utopia-maintainers] Bug#919799: cockpit: FTBFS (failing tests)

Control: retitle -1 FTBFS without a loopback inet device Control: severity -1 normal Hello Santiago, Santiago Vila [2019-01-19 17:35 +]: > I tried to build this package in buster but it failed: This fails a lot of tests like this: | cockpit-protocol:ERROR:src/common/test-webserver.c:57:setup

Accepted cssutils 1.0.2-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 19 Jan 2019 09:35:18 + Source: cssutils Binary: python-cssutils python3-cssutils Architecture: source Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Martin Pitt

cssutils salsa PR review or permission update

Hello Pythoneers, The other day I worked a bit on the cssutils package (I'm a co-maintainer). But then I noticed that since the salsa migration I can't commit to the official packaging git any more, so I sent a PR instead: https://salsa.debian.org/python-team/modules/cssutils/merge_requests/1/c

Accepted cockpit 185-1 (source) into unstable

cockpit-tests cockpit-ws Architecture: source Version: 185-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Description: cockpit- Web Console for Linux servers cockpit-bridge - Cockpit bridge server-side component cockpit-dashboard

Bug#908796: udev 240-2: failed to connect to udev daemon (on boot)

Hello js jb, js jb [2019-01-16 0:27 +]: > Is 240-4 slated to get to the testing distribution soon? If nothing unforeseen comes in between (like finding another RC bug that got introduced into -3 or -4), it should enter testing in two days: https://tracker.debian.org/pkg/systemd → look at

Bug#908796: udev 240-2: failed to connect to udev daemon (on boot)

Hello js jb, js jb [2019-01-16 0:27 +]: > Is 240-4 slated to get to the testing distribution soon? If nothing unforeseen comes in between (like finding another RC bug that got introduced into -3 or -4), it should enter testing in two days: https://tracker.debian.org/pkg/systemd → look at

Accepted libssh 0.8.6-2 (source) into unstable

Changed-By: Martin Pitt Description: libssh-4 - tiny C SSH library (OpenSSL flavor) libssh-dev - tiny C SSH library - Development files (OpenSSL flavor) libssh-doc - tiny C SSH library - Documentation files libssh-gcrypt-4 - tiny C SSH library (gcrypt flavor) libssh-gcrypt-dev - tiny C SSH

Accepted policykit-1 0.105-24 (source) into unstable

-polkit-1.0 Architecture: source Version: 0.105-24 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Description: gir1.2-polkit-1.0 - GObject introspection data for PolicyKit libpolkit-agent-1-0 - PolicyKit Authentication Agent API libpolkit

Cockpit/Composer hackfest on Devconf.cz

with your own Cockpit UI, set up your own project [1], discuss some Cockpit or Composer improvement or your pet bug, or just say hello, please stop by! See you next week, The Cockpit team Martin Pitt [1] in that case, you may also be interested in "Your turn-key Cockpit UI in a C

Accepted fatrace 0.13-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Jan 2019 12:46:59 + Source: fatrace Binary: fatrace Architecture: source Version: 0.13-2 Distribution: unstable Urgency: medium Maintainer: Martin Pitt Changed-By: Martin Pitt Description: fatrace- report system

Bug#918439: cockpit: FTBFS (failing tests)

Hello Santiago, Santiago Vila [2019-01-13 13:37 +0100]: > > Indeed, this points out a broken build environment that doesn't have a > > loopback > > device. [...] > > No, not the case. This used to build ok in the past in my autobuilders: The loopback issue does not affect *your* builds. E. g. h

Bug#918439: cockpit: FTBFS (failing tests)

Hello Santiago, Santiago Vila [2019-01-13 13:37 +0100]: > > Indeed, this points out a broken build environment that doesn't have a > > loopback > > device. [...] > > No, not the case. This used to build ok in the past in my autobuilders: The loopback issue does not affect *your* builds. E. g. h

[Pkg-utopia-maintainers] Bug#918439: cockpit: FTBFS (failing tests)

Hello Santiago, Santiago Vila [2019-01-13 13:37 +0100]: > > Indeed, this points out a broken build environment that doesn't have a > > loopback > > device. [...] > > No, not the case. This used to build ok in the past in my autobuilders: The loopback issue does not affect *your* builds. E. g. h

Bug#918439: cockpit: FTBFS (failing tests)

Control: block -1 by bug 918892 Hello Santiago, Andreas, Andreas Henriksson [2019-01-12 21:41 +0100]: > > # FAIL: 31 > > Lots of failing tests there Right, but they have two different root causes. The first is bug 918892, a recent regression in libssh 0.8.6, which causes all the cockpit-ss

Bug#918439: cockpit: FTBFS (failing tests)

Control: block -1 by bug 918892 Hello Santiago, Andreas, Andreas Henriksson [2019-01-12 21:41 +0100]: > > # FAIL: 31 > > Lots of failing tests there Right, but they have two different root causes. The first is bug 918892, a recent regression in libssh 0.8.6, which causes all the cockpit-ss

[Pkg-utopia-maintainers] Bug#918439: cockpit: FTBFS (failing tests)

Control: block -1 by bug 918892 Hello Santiago, Andreas, Andreas Henriksson [2019-01-12 21:41 +0100]: > > # FAIL: 31 > > Lots of failing tests there Right, but they have two different root causes. The first is bug 918892, a recent regression in libssh 0.8.6, which causes all the cockpit-ss

Accepted scour 0.37-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Jan 2019 12:01:02 + Source: scour Binary: python-scour python3-scour scour Architecture: source Version: 0.37-2 Distribution: unstable Urgency: medium Maintainer: Martin Pitt Changed-By: Martin Pitt Description

Bug#918892: libssh-4: 0.8.6 breaks server-side host key algorithm negotiation

Control: severity -1 serious Control: tag -1 fixed-upstream patch Hello, Sanne Raymakers [2019-01-10 6:27 -0500]: > Server-side libssh-0.8.6 breaks cockpit unit tests by not negotiating a host > key algo. This causes packages depending on libssh to malfunction and FTBFS, thus bumping priority

Re: cockpit.spawn() - how to wait for finish?

Hello Magic, . [2019-01-11 20:44 +0100]: > Thank you very much for the answer! Unfortunately I'm still stuck :-( > Please take a look at the following code and tell me why it's still > asynchronous. It display properly messages: "testFunct" and then "end of > testFunct", but it never reach the .th

Re: Login access for users without password, without password - maybe a breach?

Hello Daniel, Daniel. [2019-01-10 23:26 -0200]: > I just installed cockpit in a server that I have access exclusively with > ssh keys, my surprise is that the user hasn't a password and installing > cockpit make possible to login without password opening a breach. *Never* have users with an empty

Re: Track github issue cleanup progress

Martin Pitt [2019-01-10 10:59 +0100]: > Let's use "review-2019-01" for a bit more clarity, and 90 days. I sent a PR > for > such a script here: https://github.com/cockpit-project/cockpit/pull/10941 As discussed in the standup, I now ran this script: https://github.com

Re: Track github issue cleanup progress

Hello all, Martin Pitt [2019-01-10 9:45 +0100]: > My idea: > > * With a script, add a "triage-201901" label to all issues which didn't get >any comment in more than one month. Let's use "review-2019-01" for a bit more clarity, and 90 days.

Track github issue cleanup progress

Hello all, as discussed in yesterday's meeting, we want to do a collective effort in cleaning up our issues [1]. I just did a few, but this bears the question how we track which issues have been looked at and which still need to be re-triaged? A lot of issues will still be current, after all. My

Re: cockpit.spawn() - how to wait for finish?

Hello Magik, . [2019-01-09 21:51 +0100]: > I'm C programmer learning now Cockpit. My problem is as follows: for some > of the operation I must use external helper and I must wait for it output. > The cockpit.spawn() function returns the promise, which is non-blocking > operation (as expected). How

Accepted cockpit 184-1 (source) into unstable

cockpit-tests cockpit-ws Architecture: source Version: 184-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Description: cockpit- Web Console for Linux servers cockpit-bridge - Cockpit bridge server-side component cockpit-dashboard

Bug#915913: autopkgtest: please document what the syntax of the Features field is

Hello Josch, Johannes 'josch' Schauer [2018-12-07 23:11 +0100]: > Unfortunately under "Test-Command" it also says "This is mutually > exclusive with the ``Tests:`` field". Is there a practical reason why > these fields are mutually exclusive? Naively, I would've expected, that > when Test-Command

Bug#914840: umockdev FTBFS on hppa architecture

Control: tag -1 fixed-upstream pending Hello Helge, Helge Deller [2018-11-27 21:40 +0100]: > umockdev fails to build quite often on the hppa architecture, as can be seen > here: > https://buildd.debian.org/status/logs.php?pkg=umockdev&arch=hppa > > I did some testing, and I think it fails becau

[Bug 1787396] Re: ss crashes when using --no-header

I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is fixed in 18.10 (cosmic) with 4.18.0-1ubuntu2. ** Also affects: iproute2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: iproute2

[Kernel-packages] [Bug 1787396] Re: ss crashes when using --no-header

I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is fixed in 18.10 (cosmic) with 4.18.0-1ubuntu2. ** Also affects: iproute2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: iproute2

[Touch-packages] [Bug 1787396] Re: ss crashes when using --no-header

I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is fixed in 18.10 (cosmic) with 4.18.0-1ubuntu2. ** Also affects: iproute2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: iproute2

[Desktop-packages] [Bug 1805348] Re: Recent security update broke server-side keyboard-interactive authentication

Wow, thanks Marc, this was super-fast! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1805348 Title: Recent security update broke server-side keyboard-interactive authentication Sta

[Bug 1805348] Re: Recent security update broke server-side keyboard-interactive authentication

Wow, thanks Marc, this was super-fast! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805348 Title: Recent security update broke server-side keyboard-interactive authentication To manage notifica

Accepted cockpit 183-1 (source) into unstable

cockpit-tests cockpit-ws Architecture: source Version: 183-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Description: cockpit- Web Console for Linux servers cockpit-bridge - Cockpit bridge server-side component cockpit-dashboard

Cockpit 183 released

: https://github.com/cockpit-project/cockpit/releases/tag/183 Take care, Martin Pitt signature.asc Description: PGP signature ___ cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org To unsubscribe send an email to cockpit-devel-le

[Desktop-packages] [Bug 1805348] [NEW] Recent security update broke server-side keyboard-interactive authentication

Public bug reported: 0.8.4 and the backported fixes for CVE-2018-10933 cause server-side keyboard-interactive authentication to completely break. See https://bugs.libssh.org/T117 for details and a reproducer. This was fixed upstream as part of the 0.8.5 release, so disco is fine. For 16.04/18.04/

[Group.of.nepali.translators] [Bug 1805348] [NEW] Recent security update broke server-side keyboard-interactive authentication

Public bug reported: 0.8.4 and the backported fixes for CVE-2018-10933 cause server-side keyboard-interactive authentication to completely break. See https://bugs.libssh.org/T117 for details and a reproducer. This was fixed upstream as part of the 0.8.5 release, so disco is fine. For 16.04/18.04/

[Bug 1805348] [NEW] Recent security update broke server-side keyboard-interactive authentication

Public bug reported: 0.8.4 and the backported fixes for CVE-2018-10933 cause server-side keyboard-interactive authentication to completely break. See https://bugs.libssh.org/T117 for details and a reproducer. This was fixed upstream as part of the 0.8.5 release, so disco is fine. For 16.04/18.04/

Bug#914694: [Pkg-utopia-maintainers] Bug#914694: firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT, OUTPUT}

Hello Eric, Eric Garver [2018-11-26 10:20 -0500]: > No. As far as I can tell, firewalld never uses iptables -R (rule > replace) option. It's possible this is being triggered by something > external via the direct/passthrough interface (e.g. docker, libvirt). I collected some more info here: ht

[Pkg-utopia-maintainers] Bug#914694: Bug#914694: firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT, OUTPUT}

Hello Eric, Eric Garver [2018-11-26 10:20 -0500]: > No. As far as I can tell, firewalld never uses iptables -R (rule > replace) option. It's possible this is being triggered by something > external via the direct/passthrough interface (e.g. docker, libvirt). I collected some more info here: ht

Bug#914694: firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT,OUTPUT}

Hello again, another observation: In Fedora 29, firewalld also defaults to the iptables backend, and I get the same error noise in "systemctl status firewalld". But "--reload" works. The main differences that I can see is: * kernel: 4.18 on Debian unstable, 4.19.2 on Fedora 29 * iptables: 1.8.

[Pkg-utopia-maintainers] Bug#914694: firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT, OUTPUT}

Hello again, another observation: In Fedora 29, firewalld also defaults to the iptables backend, and I get the same error noise in "systemctl status firewalld". But "--reload" works. The main differences that I can see is: * kernel: 4.18 on Debian unstable, 4.19.2 on Fedora 29 * iptables: 1.8.

Bug#914694: Acknowledgement (firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT,OUTPUT})

Hello again, I now downloaded our previous debian-testing image, where the failure does not happen. This has the same kernel, docker, and libvirt version, and firewalld 0.6.3-1. Upgrading just firewalld to 0.6.3-3 introduces this regression. Presumably upstream now only tests with nftables, and th

[Pkg-utopia-maintainers] Bug#914694: Acknowledgement (firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT, OUTPUT})

Hello again, I now downloaded our previous debian-testing image, where the failure does not happen. This has the same kernel, docker, and libvirt version, and firewalld 0.6.3-1. Upgrading just firewalld to 0.6.3-3 introduces this regression. Presumably upstream now only tests with nftables, and th

Bug#914694: firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT,OUTPUT}

Package: firewalld Version: 0.6.3-3 Severity: important A recent regression in Debian testing broke firewalld. This is on a stock Debian-testing system, without a custom kernel, custom firewall configs, etc. -- just a plain "apt install firewalld". However, it does have libvirt and docker.io insta

[Pkg-utopia-maintainers] Bug#914694: firewall-cmd --reload fails: RULE_REPLACE failed (No such file or directory): rule in chain {INPUT, OUTPUT}

Package: firewalld Version: 0.6.3-3 Severity: important A recent regression in Debian testing broke firewalld. This is on a stock Debian-testing system, without a custom kernel, custom firewall configs, etc. -- just a plain "apt install firewalld". However, it does have libvirt and docker.io insta

Bug#911963: qemu build fails with proxy_cmd: parameter not set

Control: tag -1 pending Hello Antoine, Antoine Beaupre [2018-10-26 13:46 -0400]: > There seems to be some sort of interoperability issue between > autopkgtest and recent versions of APT which leads the build to > completely fail: > > $ sudo autopkgtest-build-qemu stretch autopkgtest-stretch.qcow

Accepted umockdev 0.12.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 18 Nov 2018 20:29:42 + Source: umockdev Binary: umockdev libumockdev0 libumockdev-dev gir1.2-umockdev-1.0 Architecture: source Version: 0.12.1-1 Distribution: unstable Urgency: medium Maintainer: Martin Pitt Changed-By

Bug#913082: autopkgtest: support multi-arch test dependencies

Hello Paul, Paul Gevers [2018-11-18 21:32 +0100]: > If I understand correctly, your fix for this bug only enables pulling > packages from foreign architectures if those architectures are otherwise > enabled in the testbed. Correct. That's all that there's to it -- autopkgtest itself is not suppos

Bug#913082: autopkgtest: support multi-arch test dependencies

Hello Paul, Paul Gevers [2018-11-18 19:48 +0100]: > I wonder if this is enough for what Alexandre is looking for. With this > change one can run ones own autopkgtest with the right options set (like > in the test case) but this isn't enough to work in frameworks like > ci.d.n IIUC. E.g. I think if

<    3   4   5   6   7   8   9   10   11   12   >