Hello Breno,
Breno Leitao [2017-02-14 11:14 -0200]:
> Are you going to move systemd to 232-16 or backport the patch to stretch
> 232-15?
Yes, we'll give -18 a few days to settle in unstable, then I'll ask the release
team for letting it in.
Martin
Hello Breno,
Breno Leitao [2017-02-14 11:14 -0200]:
> Are you going to move systemd to 232-16 or backport the patch to stretch
> 232-15?
Yes, we'll give -18 a few days to settle in unstable, then I'll ask the release
team for letting it in.
Martin
Hello Breno,
Breno Leitao [2017-02-14 11:14 -0200]:
> Are you going to move systemd to 232-16 or backport the patch to stretch
> 232-15?
Yes, we'll give -18 a few days to settle in unstable, then I'll ask the release
team for letting it in.
Martin
libsystemd-dev udev libudev1
libudev-dev udev-udeb libudev1-udeb
Architecture: source amd64
Version: 232-18
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Descript
Control: tag -1 pending
Control: severity -1 important
Raphaël Hertzog [2017-02-13 16:39 +0100]:
> Severity: serious
That seems grossly inflated, adjusting.
> Any invocation of "systemctl --user enable/disable" will fail if
> XDG_RUNTIME_DIR is not set while it's strictly not required to do
>
Control: tag -1 pending
Control: severity -1 important
Raphaël Hertzog [2017-02-13 16:39 +0100]:
> Severity: serious
That seems grossly inflated, adjusting.
> Any invocation of "systemctl --user enable/disable" will fail if
> XDG_RUNTIME_DIR is not set while it's strictly not required to do
>
Control: tag -1 pending
Control: severity -1 important
Raphaël Hertzog [2017-02-13 16:39 +0100]:
> Severity: serious
That seems grossly inflated, adjusting.
> Any invocation of "systemctl --user enable/disable" will fail if
> XDG_RUNTIME_DIR is not set while it's strictly not required to do
>
Fixed upstream:
https://github.com/systemd/systemd/commit/e8d23f92b50a97bb3
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Fixed upstream:
https://github.com/systemd/systemd/commit/e8d23f92b50a97bb3
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Fixed upstream:
https://github.com/systemd/systemd/commit/e8d23f92b50a97bb3
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Control: tag -1 pending
Michael Biebl [2017-02-10 19:20 +0100]:
> Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
> >
> > With the update to 232-17, systemd-resolved fails to start with the
> > following error:
> >
>
> > -- The error number returned by this process is 2.
> > Feb 10 17:46:31 test
Control: tag -1 pending
Michael Biebl [2017-02-10 19:20 +0100]:
> Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
> >
> > With the update to 232-17, systemd-resolved fails to start with the
> > following error:
> >
>
> > -- The error number returned by this process is 2.
> > Feb 10 17:46:31 test
libsystemd-dev udev libudev1
libudev-dev udev-udeb libudev1-udeb
Architecture: source amd64
Version: 232-17
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Descript
Bug 1288529 is a more generic approach to this, which doesn't hardcode
knowledge about journals, sosreports, etc. into autopkgtest itself, and
makes it configurable through the CI system.
Please note that when designing this you make sure that you don't
collect large logs for every failure. We
libsystemd-dev udev libudev1
libudev-dev udev-udeb libudev1-udeb
Architecture: source amd64
Version: 232-16
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Descript
I cherry-picked the patches into the Debian packaging branch, so that on
next upload zesty can be synced again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647485
Title:
NVMe symlinks broken by
I cherry-picked the patches into the Debian packaging branch, so that on
next upload zesty can be synced again.
--
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/1647485
Hello,
Stef Walter [2017-02-07 15:49 +0100]:
> It's worth noting that Peter Volpe is moving the libssh code that
> consumes SSH keys ... and I believe he has working code for using
> /etc/ssh/known_hosts.
Noted, I'll coordinate with him.
> > I'd appreciate some feedback about whether this makes
Hello Salvatore,
Salvatore Bonaccorso [2017-01-31 17:15 +0100]:
> This has been assigned CVE-2016-10187, in
Want me to upload the previously sent patch to the queue (with adding the CVE
to the patch/changelog)?
Martin
Hello Salvatore,
Salvatore Bonaccorso [2017-01-31 17:15 +0100]:
> This has been assigned CVE-2016-10187, in
Want me to upload the previously sent patch to the queue (with adding the CVE
to the patch/changelog)?
Martin
,11 @@
+calibre (2.5.0+dfsg-1+deb8u1) stable-security; urgency=medium
+
+ * Add js_no_local_file_access.patch: E-book viewer: Prevent javascript in
+the book from accessing files on the computer using XMLHttpRequest.
+Patch backported from 2.75.1. (CVE--, Closes: #853004)
+
+ --
,11 @@
+calibre (2.5.0+dfsg-1+deb8u1) stable-security; urgency=medium
+
+ * Add js_no_local_file_access.patch: E-book viewer: Prevent javascript in
+the book from accessing files on the computer using XMLHttpRequest.
+Patch backported from 2.75.1. (CVE--, Closes: #853004)
+
+ --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 29 Jan 2017 17:05:17 +0100
Source: umockdev
Binary: umockdev libumockdev0 libumockdev-dev gir1.2-umockdev-1.0
Architecture: source amd64
Version: 0.8.13-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <
Control: notfound -1 2.75.1+dfsg-1
Hello Antoine,
Antoine Beaupre [2017-01-28 15:56 -0500]:
> Someone pointed me to this note in the 2.75.1 changelog:
>
> E-book viewer: Prevent javascript in the book from accessing files
> on the computer using XMLHttpRequest.
I did mention this in
Control: notfound -1 2.75.1+dfsg-1
Hello Antoine,
Antoine Beaupre [2017-01-28 15:56 -0500]:
> Someone pointed me to this note in the 2.75.1 changelog:
>
> E-book viewer: Prevent javascript in the book from accessing files
> on the computer using XMLHttpRequest.
I did mention this in
Hey Barry,
Barry Warsaw [2017-01-24 14:49 -0500]:
> Let's say one of your autopkgtest dependencies (perhaps recursively)
> needs to update a configuration file, i.e. via a conffile. E.g. when
> running the autopkgtests for aptdaemon in an Ubuntu Zesty chroot, the
> netbase package wants to be
Control: tag -1 pending
Hey Barry,
Barry Warsaw [2017-01-24 15:01 -0500]:
> https://code.launchpad.net/~barry/autopkgtest/+git/autopkgtest/+ref/852475
Applied, thanks!
Martin
signature.asc
Description: PGP signature
Hello,
Simon McVittie [2017-01-18 12:56 +]:
> autopkgtest currently has one level of hierarchy: a test is either an
> executable script in debian/tests/ named in debian/tests/control, or a
> command in debian/tests/control.
> There is often a finer-grained result than that available.
Right,
ture it gets treated as
"skipped" instead.
> Something like that, yes; either that, or report EXPECTED-FAIL or similar
> in text, but pretend the test case was skipped when deciding what
> exit-status autopkgtest should have? (So in practice it would exit 2)
Agreed.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=11d05a9ce
** Changed in: autopkgtest (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
string vs. float comparison makes sense indeed. It could also be that by
testpkg-reboot/'s nature, rebooting is pretty much the first thing it
does, so it could happen that the uptime before reboot is even smaller
than the first time we check after reboot -- but that's a bit academic
in practice.
** Changed in: autopkgtest (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654025
Title:
trusty/armhf dkms tests are killing workers
To manage
.
This should take care to not catch kernel warnings or oopses -- when these
happen, the machine should limp on normally, and package tests like kerneloops
even trigger them deliberately.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.
Hello Iain,
your patch had a few tests/pycodestyle errors, and I squashed them
together. However, when testing this I sometimes run into a timeout:
$ runner/autopkgtest tests/testpkg-reboot -- lxd autopkgtest/ubuntu/zesty/amd64
autopkgtest [10:43:57]: git checkout: 77cd1c3
topkgtest/autopkgtest.git/commit/?id=caf8a0239
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
** Also affects: autopkgtest (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654025
Title:
trusty/armhf dkms tests are killing workers
To manage
g/cgit/autopkgtest/autopkgtest.git/commit/?id=ef7574f51
> BTW, git {diff,show} --color-words is one I learned to look at the diff
> for this patch. :)
Oh, nice trick, thanks!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debi
ather
simple.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
is bug:
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=b32d5abb7
Thanks!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
is bug:
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=b32d5abb7
Thanks!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
_
der you make it
for *other people* (i. e. your dependencies) to break your software. The stick
is that you then of course need to make/keep your own tests running so that you
can upload new versions of libfoo yourself.
So IMHO the incentives are quite right here.
Martin
--
Martin Pitt
transitions with confidence and
sort out transitions in unstable *before* landing regressions in testing.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
s of
breaks-testbeds is both hard to maintain in the autopkgtest implementation and
also hard to keep track of for a package maintainer over the history of
changing tests.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debi
d perhaps be run normally, but
> skipped when determining whether a batch of changes would break testing.
I think autopkgtest would show their result as "EXPECTED-FAIL" or so and exit
with 0 (at least for that particular test case)?
Thanks for the suggestion!
Martin
--
Martin Pitt
or QEMU anyway.
Tests could add this to Features: as an indication to human readers, but it has
no consequence to the machinery. IMHO, starting to try and categorize tests
like that would quickly end up in a big pile of tags like "installs-files",
"starts-services", &q
.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: PGP signature
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe a
hanged-By: Martin Pitt <mp...@debian.org>
Description:
autopkgtest - automatic as-installed testing for Debian packages
Closes: 839253 844255 849676
Changes:
autopkgtest (4.3) unstable; urgency=medium
.
[ SZALAY Attila ]
* Respect --shell-on-failure on test dep install failure (Clo
bug -- maybe that functionality even already exists
in networkd/NM and just needs to be wired up to YAML?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
bug -- maybe that functionality even already exists
in networkd/NM and just needs to be wired up to YAML?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
the SysV generator could approximate this a bit better by running
"After=multi-user.target" instead of "Before=multi-user.target", i. e. similar
to Type=idle.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
the SysV generator could approximate this a bit better by running
"After=multi-user.target" instead of "Before=multi-user.target", i. e. similar
to Type=idle.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubu
developers in person. Until then this shouldn't be a blocker, the other cockpit
modules should work fine with udisks.
Thanks,
Martin
[1]
https://lists.freedesktop.org/archives/devkit-devel/2016-November/001764.html
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubun
developers in person. Until then this shouldn't be a blocker, the other cockpit
modules should work fine with udisks.
Thanks,
Martin
[1]
https://lists.freedesktop.org/archives/devkit-devel/2016-November/001764.html
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubun
a user systemd unit for handling ecryptfs mounting seems both unnecessary
(it was never needed in Ubuntu, for example) and actively harmful as it's the
wrong way around IMHO.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Dev
a user systemd unit for handling ecryptfs mounting seems both unnecessary
(it was never needed in Ubuntu, for example) and actively harmful as it's the
wrong way around IMHO.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Dev
on real iron, in particular the test
setup), and containing the entire process in a VM might be a solution to that.
For local development it's usually too much overhead indeed, and it's more
convenient to run them on bare metal instead of mucking around with too many
ssh port forwardings.
Martin
--
6 GiB RAM, 1 GiB will fall over really fast),
lacks all of the build/test deps, and uses F24, so I guess this has only been
used to run cockpit itself, not for running any of its tests?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www
Hello all,
first, a quick intro of myself: I'm Martin Pitt (nicknamed "pitti" on IRC and
IRL) and joined Red Hat's Cockpit team yesterday. Until then I've been a Debian
developer for about 14 years and an Ubuntu developer for about 12½. I've
touched a lot of things over the years
Thanks. OOI, does it really hurt to have the After=systemd-
resolved.service even for cases where it's not strictly needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649453
Title:
systemd
been through about four iterations of this, and the only thing that
actually made sense and works was to clearly separate policy and machinery.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
@Scott:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1=1a190cf17cc02
looks rather complicated and also creates an unmanaged config file. Why
not just always add those After= to the .service? If resolved is not
enabled, then After=systemd-resolved is a no-op (it's only ordering, not
a
@Scott:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1=1a190cf17cc02
looks rather complicated and also creates an unmanaged config file. Why
not just always add those After= to the .service? If resolved is not
enabled, then After=systemd-resolved is a no-op (it's only ordering, not
a
@Scott:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1=1a190cf17cc02
looks rather complicated and also creates an unmanaged config file. Why
not just always add those After= to the .service? If resolved is not
enabled, then After=systemd-resolved is a no-op (it's only ordering, not
a
te
obvious that this should be under the release team's/britney's control -- but
apparently not then. Where would you like this policy/decisions to live?
Thanks, and happy new year!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
ackport the fix once it lands upstream
(https://github.com/systemd/systemd/pull/4991).
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: PGP signature
ackport the fix once it lands upstream
(https://github.com/systemd/systemd/pull/4991).
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description
'll wait a bit more for your
--apt-series changes to land too?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
ic. This would be a nice way to gradually teach people
about the init system neutral APIs, and also find/fix places which hardcode
calling /etc/init.d/.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debia
ic. This would be a nice way to gradually teach people
about the init system neutral APIs, and also find/fix places which hardcode
calling /etc/init.d/.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debia
ic. This would be a nice way to gradually teach people
about the init system neutral APIs, and also find/fix places which hardcode
calling /etc/init.d/.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
hen installing into chroots. It could ship or generate
an ifupdown/netplan/systemd-networkd configuration file, though.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
ubuntu-devel mailing list
ubuntu-d
hanged-By: Martin Pitt <mp...@debian.org>
Description:
calibre- e-book converter and library management
calibre-bin - e-book converter and library management
Changes:
calibre (2.75.1+dfsg-1) unstable; urgency=medium
.
* New upstream release:
- security fix: E-book viewer: Preven
iggers, debci translates them as
autopkgtest --env arguments (--env=ADT_TEST_TRIGGERS=foo/1.0-2 bar/2.0-3):
https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/tree/worker/worker#n327
and these envs ends up in results.tar which britney reads, and with that it can
map a result back t
mful to pretend that this is an interface which is
both safe and sensible to keep for all eternity.. But let's agree to disagree.
:-)
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
_
mful to pretend that this is an interface which is
both safe and sensible to keep for all eternity.. But let's agree to disagree.
:-)
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
mful to pretend that this is an interface which is
both safe and sensible to keep for all eternity.. But let's agree to disagree.
:-)
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
___
uch other bells and whistles aside from busybox and udev) and it
works fine.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
___
systemd-devel mailing lis
rop the systemd integration, and break calling
/etc/init.d/foo directly under systemd. WDYT?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
_
tly covered by the [ $PPID -ne 1 ] test, though. git
archeology shows that commit c04d0f71 introduced the script and both the
SKIP_REDIRECT and the [ $PPID -ne 1 ] were already present, though.
So, I can't think of a good reason to set this either, thanks for dropping it
from master.
Martin
--
Marti
tly covered by the [ $PPID -ne 1 ] test, though. git
archeology shows that commit c04d0f71 introduced the script and both the
SKIP_REDIRECT and the [ $PPID -ne 1 ] were already present, though.
So, I can't think of a good reason to set this either, thanks for dropping it
from master.
Martin
--
Marti
rop the systemd integration, and break calling
/etc/init.d/foo directly under systemd. WDYT?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
The fix landed in master:
https://github.com/systemd/systemd/commit/4050e04b
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-16.12 => None
--
You received this bug notification because you are a member of Ubuntu
The fix landed in master:
https://github.com/systemd/systemd/commit/4050e04b
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-16.12 => None
--
You received this bug notification because you are a member of Ubuntu
Till Kamppeter [2016-12-19 16:48 -]:
> Then edit the file /lib/systemd/system/cups.path adding a line
> "PartOf=cups.service" to the [Unit] section, so that the file looks like
> this:
>
> --
> [Unit]
> Description=CUPS Scheduler
> PartOf=cups.service
I suppose that cups.path is only
Till Kamppeter [2016-12-19 16:48 -]:
> Then edit the file /lib/systemd/system/cups.path adding a line
> "PartOf=cups.service" to the [Unit] section, so that the file looks like
> this:
>
> --
> [Unit]
> Description=CUPS Scheduler
> PartOf=cups.service
I suppose that cups.path is only
Till Kamppeter [2016-12-19 16:48 -]:
> Then edit the file /lib/systemd/system/cups.path adding a line
> "PartOf=cups.service" to the [Unit] section, so that the file looks like
> this:
>
> --
> [Unit]
> Description=CUPS Scheduler
> PartOf=cups.service
I suppose that cups.path is only
See the summary from https://github.com/systemd/systemd/pull/4808: I
can't convince Lennart about falling back to DNS for IPv6 if hosts has
an IPv4 entry -- if hosts has some answer, it should be considered
authoritative, and we should not mix different sources for the same
query. Often /etc/hosts
See the summary from https://github.com/systemd/systemd/pull/4808: I
can't convince Lennart about falling back to DNS for IPv6 if hosts has
an IPv4 entry -- if hosts has some answer, it should be considered
authoritative, and we should not mix different sources for the same
query. Often /etc/hosts
ack, but I don't think this is a sufficient reason to kick it out of
testing.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
ack, but I don't think this is a sufficient reason to kick it out of
testing.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
@Benjamin: Argh, I had to uncommit/recommit these three as the CVE
numbers came in at the last minute, and apparently got the commit
messages the wrong way around (meh @ not having rebase in bzr..) I did
some surgery on the branch and the commit messages are correct now.
When I created the fixes
@Benjamin: Argh, I had to uncommit/recommit these three as the CVE
numbers came in at the last minute, and apparently got the commit
messages the wrong way around (meh @ not having rebase in bzr..) I did
some surgery on the branch and the commit messages are correct now.
When I created the fixes
New upstream release with the fixes:
https://launchpad.net/apport/trunk/2.20.4
Note that Brian committed some changes to trunk in the last 1.5 hours,
so we had some mid-air collection. I force-pushed trunk and will put
back his commits on top.
** Changed in: apport
Status: In Progress =>
New upstream release with the fixes:
https://launchpad.net/apport/trunk/2.20.4
Note that Brian committed some changes to trunk in the last 1.5 hours,
so we had some mid-air collection. I force-pushed trunk and will put
back his commits on top.
** Changed in: apport
Status: In Progress =>
New upstream release with the fixes:
https://launchpad.net/apport/trunk/2.20.4
Note that Brian committed some changes to trunk in the last 1.5 hours,
so we had some mid-air collection. I force-pushed trunk and will put
back his commits on top.
** Changed in: apport
Status: In Progress =>
This is likely fixed in current systemd versions already, but the recent
commit https://github.com/systemd/systemd/commit/ad2706db7cce should fix
the remaining traces of this.
Current systemd package in
https://launchpad.net/~pitti/+archive/ubuntu/systemd contains this
patch, if you want to give
This is likely fixed in current systemd versions already, but the recent
commit https://github.com/systemd/systemd/commit/ad2706db7cce should fix
the remaining traces of this.
Current systemd package in
https://launchpad.net/~pitti/+archive/ubuntu/systemd contains this
patch, if you want to give
ubuntu-mobile-default-settings 0.12 in zesty
ubuntu-mobile-default-settings 0.12 in zesty amd64
ubuntu-mobile-default-settings 0.12 in zesty arm64
ubuntu-mobile-default-settings 0.12 in zesty armhf
ubuntu-mobile-default-settings 0.12
** Tags added: resolve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641328
Title:
Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes
mDNS lookups to fail
To manage
** Tags added: resolve
--
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/1641328
Title:
Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes
mDNS lookups to
1301 - 1400 of 91303 matches
Mail list logo
