log 2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog 2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+ * Add 0001-ssh-Use-valid-host-name-in-test-sshbridge.patch:
+Use valid host name in tes
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/216
Control: tag -1 upstream pending
Hello all,
Thorsten Glaser [2024-03-20 3:05 +]:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed
> only with _FILE_OFFSET_BITS=64"
>26 | # error
Control: severity 1061370 grave
Control: forcemerge -1 1061370
Matthias Klose [2024-02-01 8:30 +0100]:
> please don't file duplicate reports, see #1061370
Ah, sorry -- it wasn't clear from the title that it was about this problem, nor
was it RC. Marking a duplicate, so that it's easier to find.
Package: libatomic1
Version: 14-20240127-1
Severity: grave
Justification: breaks a lot of unrelated packages
Hello,
yesterday's cockpit armel build failed [1] on armel like this in the
./configure test for the PCP library:
| configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2
: #1058214)
+
+ -- Martin Pitt Wed, 10 Jan 2024 08:16:54 +0100
+
sosreport (4.0-2) unstable; urgency=medium
* d/p/0003-systemd-prefer-resolvectl-over-systemd-resolve.patch:
diff -Nru sosreport-4.0/debian/patches/0004-unittest-assertEquals.patch
sosreport-4.0/debian/patches/0004-unittest
Control: forwarded -1 https://github.com/sosreport/sos/pull/3467
Control: tag -1 upstream pending
Hello Lucas and Eric,
I sent an upstream fix for this to the PR above. Their CI didn't even spot that
error yet (argh big testing gaps).
This has been open for a month now. As this threatens to
Control: reassign -1 upower 1.90.2-7
Control: tag -1 fixed-upstream pending
The upower test adjustment landed upstream, I'll cherry-pick it into Debian.
Martin
Control: tag -1 upstream
Control: forwarded -1
https://gitlab.freedesktop.org/upower/upower/-/merge_requests/207
Hello Luca,
Luca Boccassi [2023-12-26 12:46 +0100]:
> Not sure whether it was a legitimate change and upower's tests need an
> update, or if it is a new bug, but 0.30.1-1 causes
Control: tag -1 pending
Hello,
Bug #1057148 in python-dbusmock 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:
Hello Santiago,
Santiago Vila [2023-02-18 0:26 +0100]:
> Martin Pitt wrote:
> > The "flock: not found" is #1014662, but that is already present in our
> > current
> > image with cloud-initramfs-tools 0.18.debian8, and does not seem fatal. So
> > far
>
Control: tag -1 fixed-upstream pending
Hello again,
Martin Pitt [2022-10-26 6:04 +0200]:
> Argh, this keeps haunting us. We already tried to fix that in [1] and [2], but
> no way. Why must glib be so unpredictable?
> [2] https://github.com/cockpit-project/cockpit/pull/17755
Never
Hello Michael, hello Lis,
Michael Biebl [2022-10-26 1:41 +0200]:
> cockpit seems to fail its test suite on the aforementioned architectures
Thanks for the report!
> on armel:
> ~
> Bail out! GLib-FATAL-WARNING: GChildWatchSource: Exit status of a child
> process was requested but
Martin Pitt [2022-07-26 11:58 +0200]:
> A fresh installation of rpcbind fails to start the service:
This can also be seen on package installation [1]:
Setting up rpcbind (1.2.6-5) ...
/usr/lib/tmpfiles.d/rpcbind.conf:2: Failed to resolve user '_rpc': No such
process
Martin
[1] ht
Package: rpcbind
Version: 1.2.6-4
Severity: serious
A fresh installation of rpcbind fails to start the service:
systemd[1]: Starting RPC bind portmap service...
rpcbind[314]: cannot get uid of '_rpc': Success
systemd[1]: rpcbind.service: Main process exited, code=exited,
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/martinpitt/python-dbusmock/pull/139
Ça va Lucas,
Lucas Nussbaum [2022-07-16 15:32 +0200]:
> > ==
> > FAIL: test_options
Control: reassign -1 openssl 3.0.2-1
Control: affects -1 sscg 3.0.2-1
Control: tag -1 fixed-upstream
Kurt Roeckx [2022-05-15 23:05 +0200]:
> It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247
Indeed, thank you! Updating bug status.
I see openssl 3.0.3-4 is supposed to
Control: tag -1 upstream confirmed
Control: retitle -1 sscg FTBFS with OpenSSL 3.0.3
Adrian Bunk [2022-05-14 9:48 +0300]:
> https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1
>
> ...
> 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11
> SIGSEGV
> 04:32:21
Control: tag -1 pending
Hello,
Bug #1006465 in python-dbusmock 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:
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/16928
I sent an upstream PR to add the missing node_modules/ copyrights. If there is
anything else wrong, I'll need more information (see my previous reply).
Thanks!
Martin
tag -1 moreinfo
Hallo Thorsten,
Thorsten Alteholz [2022-02-05 9:40 +]:
> please rework your debian/copyright. Especially everything from node_modules
> seems to be missing. Please also check other releases.
The webpack bits in dist/ are autogenerated, and we have spent quite some
effort to
Control: severity -1 normal
Control: tag -1 unreproducible moreinfo
Hello Friedemann,
Friedemann Schorer [2021-10-03 23:40 +0200]:
> Severity: serious
That feels inflated to me. The package builds fine in official buildds [1], in
upstream CI (which uses pbuilder) and locally in a debian-sid
Control: tag -1 pending
Paul Gevers [2021-03-27 21:43 +0100]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/f/fatrace/11288159/log.gz
>
> autopkgtest [23:08:44]: test fatrace-currentmount: [---
> ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not
>
Control: reassign -1 network-manager 1.29.90-1
Control: tag -1 upstream fixed-upstream
Control: forwarded -1
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662
This eventually *did* turn out to be a bug in NetworkManager itself, and only
became visible now because of the
Martin Pitt [2021-02-14 11:41 +0100]:
> So this is some weird NM build system issue that breaks something for any tag
> (i.e. minor/micro version in configure.ac) >= 1.28.0. Note that the 1.28-rc*
> tags
> have version 1.27.x.
I checked out tag 1.30-rc1 (aka version 1.29.
Hello all,
CC'ing Thomas, maybe he has some idea about this. Thomas, please see [0] for
the python-dbusmock failure that triggered this bug report.
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
>
Control: reassign -1 0.22.0-1
Control: affects -1 network-manager
Adrian Bunk [2021-02-12 16:22 +0200]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/10412779/log.gz
> test_one_wifi_with_accesspoints (__main__.TestNetworkManager) ... **
>
Control: tag -1 fixed-upstream pending
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/115
Hello Lucas,
Lucas Nussbaum [2020-12-26 22:57 +0100]:
> > Bail out! ERROR:../tests/test-umockdev.c:1135:t_testbed_usb_lsusb:
> > assertion failed (exit_status == 0): (256 == 0)
I
Package: pcp
Version: 5.2.1-1
Severity: serious
Tags: patch
The recent 5.2.1-1 upload made a dependency change to pcp:
Package: pcp
-Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl,
python3-pcp, python3, libpcp-web1
+Depends: ${shlibs:Depends}, ${misc:Depends},
Package: podman
Version: 2.0.3+dfsg1-1
Severity: serious
Tags: upsteam fixed-upstream
Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman and
any other API user. This is tracked here:
https://github.com/containers/podman/issues/7078
This has been fixed upstream and will
Control: retitle -1 FTBFS on IPv6-only hosts
Control: found -1 188-1
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/14098
Control: tag -1 patch upstream
Hello Aurelien,
Aurelien Jarno [2020-05-16 19:27 +0200]:
> This is an IPv6 host only,
Ah! This explains the issue
Michael Biebl [2020-05-16 12:39 +0200]:
> Source: cockpit
> Version: 219-1
> Severity: serious
>
> Hi Martin,
>
> looks like the latest release reliably triggers a FTBFS on arch-all:
>
> https://buildd.debian.org/status/logs.php?pkg=cockpit=219-1=all
>
> The relevant part from the build log
>
Hello Paul,
Paul Gevers [2020-04-12 20:35 +0200]:
> As recently announced [1], the Release Team now considers packages that
> are out-of-sync between testing and unstable for more than 60 days as
> having a Release Critical bug in testing. Your package src:umockdev in
> its current version in
Control: tag -1 fixed-upstream pending
Hello Matthias,
Matthias Klose [2020-02-11 11:45 +0100]:
> autopkgtest [17:12:07]: test upstream: ---]
> autopkgtest [17:12:07]: test upstream: - - - - - - - - - - results - - - - -
> -
> - - - -
> upstream FAIL stderr:
>
Hello Michael and Thomas,
Michael Biebl [2020-01-08 19:42 +0100]:
> > The latest update of network-manager causes an autopkgtest regression in
> > python-dbusmock.
> >
> > https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/3793816/log.gz
> >
> >
Hello Nathan,
Nathan Scott [2020-01-07 11:18 +1100]:
> Thanks for looking into this issue while we were all off, Martin and Sunil!
>
> To summarise where I understand things are at now: Martin's uploaded
> a pcp package for rebuild which drops the python2 build steps. I think
> this is fine and
Control: tag -1 pending
Hello again,
Martin Pitt [2020-01-05 10:54 +0100]:
> > I ran into similar issue when attempting to build with multiple parallel
> > tasks with DEB_BUILD_OPTIONS=parallel=8 or with -j8. If you have this
> > turned on, please try disabling it.
>
>
Hello Sunil,
Sunil Mohan Adapa [2020-01-04 12:15 -0800]:
> > This file doesn't exist anywhere -- apparently src/include/builddefs.install
> > builds it, but at this point this is pretty deeply woven into the build
> > system.
> > Curiously, resuming the build with "make" and "dpkg-buildpackage
.2/debian/changelog 2020-01-04 09:58:40.0 +
@@ -1,3 +1,11 @@
+pcp (5.0.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop remaining python2 build commands (closes: #947916)
+ * Build-depend on python3-all-dev for the py3 extension build.
+
+ -- Martin Pitt Sat,
Hello Nathan,
Nathan Scott [2019-12-02 10:51 +1100]:
> Thanks! I've updated the PCP deb builds in the upstream PCP repo and plan
> to close this issue out with the pcp-5.0.2 release (scheduled for Wed 11th).
> If
> you need the fix sooner though, feel free to NMU.
Nice, thanks! That's soon
Hello,
I just checked that python-pcp has zero reverse build and binary dependencies,
so it's fine to just drop it and thus fix this RC bug. If you don't have time,
I'm happy to do an NMU for this (as cockpit maintainer I don't want cockpit to
get dropped from testing due to pcp disappearing).
Hello Jussi, Olly,
Olly Betts [2019-10-27 11:52 +1300]:
> However, then the build fails for me running tests using ccache - the
> problem is that $HOME is /sbuild-nonexistent under sbuild, which
> doesn't exist, and cache tries to create its cache under $HOME/.ccache
> by default.
I don't have
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:
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:
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
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:
>
>
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:
|
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.
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
Control: tag -1 fixed-upstream
Hello Paul and Jeremy,
Thanks for the report and the reminder.
Indeed I investigated this problem a while ago and fixed it upstream:
https://github.com/martinpitt/umockdev/commit/a95afb886945c2df
https://github.com/martinpitt/umockdev/commit/45b6dc5d1d5db
I
Package: libssh-dev
Version: 0.8.0-1
Severity: serious
The new libssh's pkg-config file is broken, it has an empty version:
| $ pkg-config --modversion libssh
| $ grep Version /usr/lib/x86_64-linux-gnu/pkgconfig/libssh.pc
| Version:
The previous version, still in testing, is correct:
| $
Control: tag -1 moreinfo
Hello Thomas,
Thomas Goirand [2018-04-18 9:36 +0200]:
> Package: systemd
> Version: 232-25+deb9u2
> Severity: serious
What is the rationale for this being release-critical?
> Doing my everyday $work, I found that a machine had systemd-timesyncd
> installed. To the
Control: tag -1 -buster
bi...@debian.org [2017-05-31 9:24 +0200]:
> Source: policykit-1
> Version: 0.113-2
> Severity: normal
> Tags: sid buster
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs mozjs185
>
> Dear maintainer,
>
> Your package is depending against mozjs
Adrian Bunk [2018-01-23 16:53 +0200]:
> > ... so that after
> > the buster release I can remove the python-scour → scour dependency again.
>
> Nitpick:
> After buster python-scour will be removed (no Python 2 in bullseye).
So much the better! /me starts sharpening the knife :-)
Martin
Control: tag -1 pending
Hello Adrian and all,
Adrian Bunk [2018-01-23 7:54 +0200]:
> This is actually a bug in scour, where the scour binary and debhelper
> addon moved from python-scour to python3-scour.
>
> Neither is the right place.
>
> scour should go into an own binary package of the
Control: tag -1 pending fixed-upstream
Control: forwarded -1
https://github.com/martinpitt/umockdev/commit/33ef8438abd779
Lucas Nussbaum [2017-08-06 18:08 -0400]:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> >
Hey Chris,
Chris Lamb [2017-07-28 7:56 +0100]:
> > That's only for the bundled JavaScript modules.
>
> I don't have the package in front of me right now but I think
> the other issue was that d/copyright was mentioning .JS but in
> the wrong location (node_modules/ vs. dist/ IIRC). Again this
>
Control: found -1 146-1
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/7397
Hello Chris,
Chris Lamb [2017-07-27 21:11 +0100]:
> I just ACCEPTed cockpit from NEW but noticed it was missing
> attribution in debian/copyright for at least Nokia in mock-io-stream.c.
Thanks
Hello Manolo,
Manolo Díaz [2017-07-16 18:36 +0200]:
> > So calibre should clean up *.pyc files (probably from ancient
> > installations) in /usr/lib/calibre.
> > Cheers,
> > -- Guido
>
> It would help, but I think it isn't enough. Given the following
> sequence calibre would have failed to
Control: tag -1 pending
dmm [2017-06-27 21:21 +1000]:
> I recently upgraded from calibre 2.75 to 3.1.1, after the upgrade
> calibre-server would not run.
>
> Appears there was a missing dependancy, fixed with
>
> # apt-get install python-msgpack
Whoops, sorry about that! Fixed in git, will
Andreas Henriksson [2017-04-19 14:48 +0200]:
> I've tried to reproduce this but failed. I'm using an amd64 stretch
> install as a base, with a newly debootstrapped --arch=i386
> --variant=minbase chroot where I installed mkosi build-deps, fetched
> mkosi sources and ran debian/rules binary.
> I've
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
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
>
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)
+
+ --
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
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)
Hello again,
Martin Pitt [2016-11-09 10:24 +0100]:
> I pushed the fix now:
>
>
> https://anonscm.debian.org/cgit/collab-maint/json-c.git/commit/?id=bf85685a69
>
> (without changelog as you apparently do that on release time).
>
> > (I'd also fix the broken
Control: tag -1 pending
Hello again,
Martin Pitt [2016-11-07 23:22 +0100]:
> # head /lib/x86_64-linux-gnu/libjson-c.so.3
> head: cannot open '/lib/x86_64-linux-gnu/libjson-c.so.3' for reading: Too
> many levels of symbolic links
>
> Thus bumping severity. I'm happy to do an N
can't support ancient kernels
forever.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Control: reassign -1 python3-wand
Control: forcemerge 841653 -1
Martin Pitt [2016-10-21 20:22 +0200]:
> | File "/tmp/autopkgtest.2SwpBj/build.7IV/real-tree/debian/tests/t", line 2,
> in
> | from wand.image import Image
> | File
> "/tmp/autopkgtest.2S
the last
upload.
Thanks for considering,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
found
So it looks like imagemagic changed recently, so at first sight I'll
just need to adjust the test case to that.
I'll look into this ASAP, thanks for the report!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
r side yet).
Don't worry, I'm still eager to find out what's happening here; I'll
look at your logs as soon as possible.
Martin
[1] https://www.debian.org/Bugs/Developer#severities
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian
debugging for networkd with
mkdir -p /etc/systemd/system/systemd-networkd.service.d/
printf '[Service]\nEnvironment=SYSTEMD_LOG_LEVEL=debug' >
/etc/systemd/system/systemd-networkd.service.d/debug.conf
and reboot. If you catch the bug, please attach "journalctl -b".
Thanks,
Mar
[1]. Could
> someone try to reproduce this with this patch reverted?
I did, and that indeed fixes it. Thanks for digging this out! Revert
pushed to packaging git. I suppose we should upload this ASAP?
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubu
ur system
as well.
The various test_tmp_install*() test cases also download some packages
with "apt-get download", so these would need to be skipped as well if
this is really to be considered a policy violation.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
t
> obsolete. Upstream still ships busname units.
Agreed, sorry about that. Done in packaging git.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: PGP signature
runlevel`.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
>From 08d6d3ce4d3bf2c3428d40e6a33665aba7270f59 Mon Sep 17 00:00:00 2001
From: Martin Pitt <martin.p...@ubuntu.com>
Date: Thu, 14 Jul
it and voilà, /usr is mounted.
Haha, glad you solved the mystery! :-)
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
ut shared object,
> booted with sysvinit and found it. I suspect the bug is true even with an
> initrd this time. Maybe analysing the initrd could tell us.
That's strange indeed. Mind booting with "debug" and attaching
/run/initramfs/initramfs.debug?
Thanks,
Martin
--
Martin Pitt
systemd.git/commit/?id=24b267b53
[2] https://bugs.debian.org/771652
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: PGP signature
Control: reassign -1 libaudit1
Control: forcemerge 828991 -1
Hello Chris,
Chris Lamb [2016-06-30 16:53 +0100]:
> systemd fails to build from source in unstable/amd64:
This is known, due to yesterday's libaudit. Merging/linking bugs.
Thanks,
Martin
--
Martin P
'
Does that happen for any kind of book? What's your desktop
environment?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
ebian.org/771652
https://bugs.debian.org/771723
https://bugs.debian.org/788913
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
ble plus a local apt
repo without the Breaks: works fine, so I committed this:
http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=f1acba82
I'll 0-day NMU this now, as it got introduced by my previous NMU and
fixes an RC bug.
Thanks and sorry for the trouble,
Martin
--
Martin P
ackage with tighter dependency uploaded, thanks for the report!
I tested this again with a local apt-ftparchive, the tight dependency
doesn't seem to cause any trouble.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
radar
I NMUed this change together with #826205 and #825937 to DELAYED/5.
I'll push the corresponding release commit/tags if/when this lands.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Hello again,
Martin Pitt [2016-04-06 14:55 +0200]:
> norwegian still FTBFS in current sid:
>
> | sed -e 's/stringchar *� *�//' -e 's/[��]//g' nb.aff.in > nb.aff.new && \
> | mv nb.aff.new nb.aff
> | cat forkort-nb.txt munched.B munched.A munched.N munched.M munche
; comp1.tmp
| Makefile:517: recipe for target 'nb.mch' failed
| make[2]: *** [nb.mch] Error 1
| make[2]: Leaving directory '/<>'
So it's not exactly the same error any more, but still an FTBFS RC bug.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
and cleanup
containers, and saves quite some disk space too.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: PGP signature
Control: tag -1 pending
Hey all,
Martin Pitt [2016-02-27 12:24 +0100]:
> So I think I'll revert the second hunk of the above commit for now to
> get things back to normal. To avoid breaking systemd-coredump, which
> now looks at the process' RLIMIT_CORE (which is IMHO wrong), we need
&g
is IMHO wrong), we need
to adjust https://github.com/systemd/systemd/commit/bdfd7b2c63
accordingly.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signed bugs to the
init-system-helpers package as update-rc.d, service, and invoke-rc.d
moved there yesterday.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Control: tag -1 pending
Martin Michlmayr [2016-01-16 0:11 -0800]:
> plr fails to build in unstable:
This is waiting in NEW:
https://ftp-master.debian.org/new/plr_1:8.3.0.16-1.html
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Deb
tretch, so britney
should not hold back -4 because of that.
TBH, I don't see what we can do about that in ifupdown.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
udev versions, so that got dropped as
a workaround. (See #809658, #809743).
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
.
I'm cloning to udev (keeping RC) to put back the helper for the time
being, and cloning the bug some more about eliminiating its usage from
the other packages.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debi
stamps are guaranteed to be different. This makes the tests a tad
slower, but would at least fix this RC bug for the time being.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
-mscriptsinstact
the error unwinding is to call the old version's postinst, which
doesn't help us.
But maybe I'm missing something?
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Desc
1/
You can use that as an apt source by adding
deb [trusted=yes] http://people.debian.org/~mpitt/tmp/systemd-808151/ /
to /etc/apt/sources.list (or sources.list.d/pitti.list or similar),
then running "apt update" and "apt upgrade".
Thanks,
Martin
--
Martin Pitt
1 - 100 of 533 matches
Mail list logo
