Bug#1064973: diffoscope fails with struct.error: unpack requires a buffer of 4 bytes

On Thu, Feb 29, 2024 at 11:19:50AM +, Chris Lamb wrote: > The traceback/error is fixed in Git, pending upload: > > https://salsa.debian.org/reproducible-builds/diffoscope/commit/466523ac6fbd1437635f8393fb93c37ff59341b3 Thanks!

Bug#1064973: diffoscope fails with struct.error: unpack requires a buffer of 4 bytes

Package: diffoscope Version: 257 Severity: normal The package is really diffoscope-257-1.fc40.x86_64. $ diffoscope cache/rpms/meson-1.3.2-1.fc41/meson-1.3.2-1.fc41.noarch.rpm cache/build/meson-1.3.2-1.fc41/rebuild/meson-1.3.2-1.fc41.noarch.rpm ... Traceback (most recent call last): File

Bug#954490: systemd: resolved.conf "allow-downgrade" doesn't work

On Sat, Apr 04, 2020 at 10:41:31AM +0300, Fanis Dokianakis wrote: > I confirm that this bug exists after upgrading systemd. Systemd-resolved > *sometimes* does not downgrade and SERVERFAILS on all domains that do not > have a signature dns record. That's not what "allow-downgrade" means. The

Bug#946456: systemd: Provide systemd-sysusers as an independent package

On Thu, Jan 30, 2020 at 11:51:48PM -0300, Felipe Sateler wrote: > On Thu, Jan 30, 2020 at 6:40 PM Michael Biebl wrote: > > > Hi Felipe > > > > Am 30.01.20 um 22:30 schrieb Felipe Sateler: > > > > > > > > > On Thu, Jan 30, 2020 at 1:39 PM Michael Biebl > > > wrote: > > >

Bug#947935: ITP: opentmpfiles -- standalone utility written to process systemd-style tmpfiles.d files

[resend] On Thu, Jan 02, 2020 at 01:35:26PM +0100, Thomas Goirand wrote: > * URL : https://github.com/OpenRC/opentmpfiles I had a quick look at the repo. This is not a comprehensive review, just a quick list of the most obvious items: opentmpfiles doesn't implement quite a few

Bug#947935: ITP: opentmpfiles -- standalone utility written to process systemd-style tmpfiles.d files

On Thu, Jan 02, 2020 at 01:35:26PM +0100, Thomas Goirand wrote: > * URL : https://github.com/OpenRC/opentmpfiles I had a quick look at the repo. This is not a comprehensive review, just a quick list of the most obvious items: opentmpfiles doesn't implement quite a few options:

Bug#891903: diffoscope: programming error in except clause

Package: diffoscope Version: 91 Severity: normal Dear Maintainer, I'm trying to update diffoscope to version 91 in Fedora rawhide, and the tests failing for reasons I haven't diagnosed yet (it builds fine locally, but fails on an s390x builder). When the tests are failing, a try..except clause

Bug#808151: pr submitted

https://github.com/systemd/systemd/pull/6316

Bug#865528: don't escape dash (\x2d) when logging

On Thu, Jun 22, 2017 at 11:21:08PM +0200, Michael Biebl wrote: > Am 22.06.2017 um 16:34 schrieb 積丹尼 Dan Jacobson: > > Well > > $ systemctl status AA.device > > ● AA.device > >Loaded: loaded > >Active: inactive (dead) > > if the user doesn't carefully replace \ with \\ he will get the dead

Bug#856447: diffoscope: test_icc::test_diff fails due to locale difference in output

On Fri, Mar 03, 2017 at 04:11:57PM +0800, Chris Lamb wrote: > https://bugs.debian.org/847595 > > https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=fcbcafa1b1cefb08a7ffbd8936f22c5bc6849991 Cool, thanks! I added a note to our spec file, and we'll just wait for the fixes to

Bug#817193: diffoscope: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

On Sun, Feb 26, 2017 at 05:37:51PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Feb 23, 2017 at 05:48:14PM +0800, Chris Lamb wrote: > > tags 817193 + unreproducible > > thanks > > > > Chris Lamb wrote: > > > > > Are you still any of th

Bug#817193: diffoscope: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

On Thu, Feb 23, 2017 at 05:48:14PM +0800, Chris Lamb wrote: > tags 817193 + unreproducible > thanks > > Chris Lamb wrote: > > > Are you still any of these test failures with a recent diffoscope > > version? We have made a few locale changes recently so its likely > > that at least some of these

Bug#854515: submitting enjarify man page upstream

Package: enjarify Version: 1:1.0.3-3 Hi, I'm working on a Fedora package for enjarify [1], and I want to include the man page [2] that Debian provides. We could pull it directly from the Debian repo, but it'd be nice to have it "official". Could you submit the man page upstream? Thanks, Zbyszek

Bug#817193: failing tests with v62: test_listing, test_diff test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

I noticed that I was missing ppudmp from my installation, so tests were skipped. Once it is installed, the ppu tests also fail. Looks like a programming error, PpuFile is File, not FilesystemFile from a quick look. === FAILURES ===

Bug#817193: failing tests with v62: test_listing, test_diff test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

=== FAILURES === _ test_listing _ differences = [, ] @skip_unless_tools_exist('cbfstool') def test_listing(differences): expected_diff =

Bug#832010: Please enable LZ4 compression

On Thu, Jul 21, 2016 at 07:28:26PM +0200, Yuri D'Elia wrote: > On Thu, Jul 21 2016, Michael Biebl wrote: > > And in Debian we build against libxz, so xz compression is used for core > > files. > > Indeed, and it's pretty slow. > > > What would we gain by switching from xz to

Bug#839224: python-systemd: "undefined symbol" error on armhf

Oops, I forgot I fixed this in git after tagging v232 (commit 8024fc6171). I now added -Werror=implicit-function-declaration to compile flags so the compilation should actually fail instead of just emitted a warning if the same problem occurs hain. You probably want to pull in most of those: *

Bug#839224: python-systemd: "undefined symbol" error on armhf

On Fri, Sep 30, 2016 at 02:24:57PM +0200, Michael Biebl wrote: > Am 30.09.2016 um 12:39 schrieb Patrick Scharrenberg: > > Package: python-systemd > > Version: 232-1~bpo8+1 > > Severity: normal > > > > Dear Maintainer, > > > > when trying to import JournalHandler on arm architecture I get the >

Bug#817193: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

On Mon, Aug 15, 2016 at 09:07:03PM +0100, Chris Lamb wrote: > Zbigniew Jędrzejewski-Szmek wrote: > > > I invoke the tests as "PYTHONPATH=. py.test-3 . -vv" locally. Above output > > is from that. > > Hm, cannot seem to reproduce. > > Are you building in

Bug#817193: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

On Mon, Aug 15, 2016 at 11:24:05AM +0100, Chris Lamb wrote: > Hi Zbigniew, > > > > https://kojipkgs.fedoraproject.org//work/tasks/890/13300890/build.log > [..] > > https://kojipkgs.fedoraproject.org//work/tasks/2994/13312994/build.log > [..] > >

Bug#817193: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

I "enabled" the cbfs tests by installing the appropriate dependency (coreboot-utils), and one more test starting failing: === FAILURES === _ test_listing _ differences

Bug#820631: [Reproducible-builds] Bug#820631: support for concatenated cpio archives

On Sun, Apr 10, 2016 at 10:34:59PM +0200, Reiner Herrmann wrote: > Hi Zbigniew, > > thanks for the report! > I just had a short look at this issue. > The problem why diffoscope doesn't see this change is that the initramfs > contains actually multiple cpio archives, but diffoscope treats > the

Bug#820631: (no subject)

Subject: diffoscope: wrongly reports "No differences found inside, yet data differs" Package: diffoscope Version: 51 Severity: normal Dear Maintainer, when comparing two initramfs images [1,2], diffoscope reports: [1] http://in.waw.pl/~zbyszek/diffoscope/initramfs-4.5.0-302.fc24.x86_64.img [2]

Bug#817193: [Reproducible-builds] Bug#817193: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

On Fri, Mar 11, 2016 at 03:03:28PM +, Zbigniew Jędrzejewski-Szmek wrote: > > On Mittwoch, 9. März 2016, Zbigniew Jędrzejewski-Szmek wrote: > > > I'll be able link to build logs in koji (the Fedora build system) once > > > python-libarchive-c passes review and I can bui

Bug#817193: [Reproducible-builds] Bug#817193: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

> On Mittwoch, 9. März 2016, Zbigniew Jędrzejewski-Szmek wrote: > > I'll be able link to build logs in koji (the Fedora build system) once > > python-libarchive-c passes review and I can build against it. Example of full test suite failing: https://kojipkgs.fedoraproject.org/

Bug#817193: [Reproducible-builds] Bug#817193: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

On Wed, Mar 09, 2016 at 03:03:53PM +0100, Holger Levsen wrote: > control: reopen -1 > > Hi, > > On Mittwoch, 9. März 2016, Zbigniew Jędrzejewski-Szmek wrote: > > The tests still fail with v. 51: > > ok, reopening, thanks for confirming! > > > If I set

Bug#817248: [Reproducible-builds] Bug#817248: diffoscope 51 not uploaded to pypi

On Wed, Mar 09, 2016 at 01:07:13PM +, Mattia Rizzolo wrote: > http://pypi.debian.net/diffoscope should be better > http://ftp.debian.org/debian/pool/main/d/diffoscope/ Thanks. Both seem to work indeed (apart from pypi missing some tarballs of course). Zbyszek

Bug#817248: diffoscope 51 not uploaded to pypi

On Wed, Mar 09, 2016 at 01:09:17PM +0100, Holger Levsen wrote: > package: diffoscope > version: 51 > severity: minor > x-debbugs-cc: "Zbigniew Jędrzejewski-Szmek" <zbys...@in.waw.pl> > > Hi, > > thanks for making us aware of this issue! > > On Mittw

Bug#817193: failing tests: test_gzip.py::test_metadata, test_ipk.py::test_metadata, test_java.py::test_diff

Package: diffoscope Version: 48 Hi, I'm trying to package diffoscope for Fedora and the tests listed in $subject are failing. Seems to be some timezone issue: = FAILURES ==

Bug#807458: :807: warning [p 10, 2.8i, div `3tbd1, 1', 1.2i]: can't break line

On Fri, Jan 29, 2016 at 04:43:56PM +0100, Michael Biebl wrote: > Control: severity -1 minor > Control: tags -1 = confirmed > > On Tue, 05 Jan 2016 05:11:54 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson > wrote: > > # su - nobody > > No directory, logging in with HOME=/ > >

Bug#807458: :807: warning [p 10, 2.8i, div `3tbd1, 1', 1.2i]: can't break line

On Sat, Jan 30, 2016 at 08:36:04AM +0800, 積丹尼 Dan Jacobson wrote: > It would be best to just reengineer your table not to generate the errors. It's the output of an actual command, and the values in the columns simply need that much space. Zbyszek

Bug#806291: systemd: systemctl status ignores -n argument

On Sun, Dec 20, 2015 at 02:52:49PM +0100, Eduard Bloch wrote: > Hallo, > * Zbigniew Jędrzejewski-Szmek [Mon, Nov 30 2015, 01:25:49AM]: > > > > [Service] > > > Type=notify > > > Restart=on-failure > > > ExecStart=/bin/sh -c "echo OMG THEY

Bug#806291: systemd: systemctl status ignores -n argument

On Sat, Nov 28, 2015 at 11:37:55AM +0100, Eduard Bloch wrote: > Hallo, > * Michael Biebl [Thu, Nov 26 2015, 04:32:43PM]: > > Am 26.11.2015 um 15:59 schrieb Michael Biebl: > > > Works here. But I actually need a service which produces more then 10 > > > lines of output when started. > > > > To

Bug#782426: unblock: systemd/215-15

On Mon, Apr 13, 2015 at 10:56:45PM +0200, Michael Biebl wrote: Hi Julien, Am 13.04.2015 um 22:18 schrieb Julien Cristau: On Mon, Apr 13, 2015 at 22:03:51 +0200, Michael Biebl wrote: ++static int manager_dispatch_ask_password_fd(sd_event_source *source, ++

Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)

On Tue, Jan 06, 2015 at 06:56:11PM +0100, Tomas Pospisek wrote: Hello Zbigniew, I was told on IRC in #debian-systemd: mbiebl_ tpo, I remember Zbigniew had a patch without wanting to stress anybody: could you maybe tell me what the status of that patch is? Are you considering it ready

Bug#772182: systemd: Systemd tries to mount swap partition twice at the same time

On Fri, Dec 05, 2014 at 02:41:59PM -0800, Benjamin Xiao wrote: Systemd tries to mount my swap partition twice at the same time. One of the mount attempts is triggered by systemd-fstab-generator and the other attempt is triggered by systemd-gpt-auto-generator. There is a race condition and one

Bug#771397: v217: systemd-delta says diff failed with error code 1.

On Sat, Nov 29, 2014 at 08:35:16AM +0100, Alexandre Detiste wrote: Package: systemd Version: 217-1 Severity: minor Dear Maintainer, Hi, I'm testing v217 in experimental. systemd-delta inserts diff failed with error code 1 in it's output after each diff. Fixed upstream in

Bug#771172: systemd-sysv-generator does not generate

On Thu, Nov 27, 2014 at 09:06:11PM +0100, Salvo Tomaselli wrote: Running systemctl daemon-reload is sufficient to run the generator. You don't need to run it by hand and copying the files around. I wasn't even aware there was such a thing. rantI thought systemd was supposed to be a drop in

Bug#770504: systemd: log all members of cyclic dependencies (loops)

On Sat, Nov 22, 2014 at 01:20:13AM +0200, Uoti Urpala wrote: On Fri, 21 Nov 2014 20:20:45 + Simon McVittie s...@debian.org wrote: dependency: systemd logs that there was a loop, and which arbitrary point it tried to use to break it. However, it does not log (an example of) the whole

Bug#767267: systemctl --failed not documented

http://cgit.freedesktop.org/systemd/systemd/commit/?id=599b6322f1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768178: systemd: sysvinit wrapper breaks newly-installed services

On Thu, Nov 06, 2014 at 01:25:32PM -0800, Josh Triplett wrote: On Wed, 5 Nov 2014 20:20:27 -0500 Zbigniew =?utf-8?Q?J=C4=99drzejewski-Szmek?= zjedr...@gmu.edu wrote: On Wed, Nov 05, 2014 at 07:31:32PM +0100, Michael Biebl wrote: The default for sysv init scripts is RemainAfterExit=true

Bug#768178: systemd: sysvinit wrapper breaks newly-installed services

On Wed, Nov 05, 2014 at 08:12:39PM +, Ximin Luo wrote: All I care is that service x start works. It does not. This is correctly called systemd breaks existing software - it is breaking the sysvinit behaviour. Let's look what LSB says:

Bug#768178: systemd: sysvinit wrapper breaks newly-installed services

On Wed, Nov 05, 2014 at 07:31:32PM +0100, Michael Biebl wrote: The default for sysv init scripts is RemainAfterExit=true [0], so even if there are no running processes, the service is marked as active. This is because systemd doesn't know, if the sysv init script is supposed to start a long

Bug#767893: systemd cannot mount zfs filesystems from fstab

On Mon, Nov 03, 2014 at 05:51:57AM -0500, John Holland wrote: I created luks volumes, installed zfsonlinux.org packages, created a zpool out of the luks volumes. When ZFS is managing the mounting of the fs's it works. If I put a zfs filesystem in /etc/fstab the prompts to enter passwords

Bug#767893: systemd cannot mount zfs filesystems from fstab

On Mon, Nov 03, 2014 at 03:36:49PM +0100, Michael Biebl wrote: http://changelog.complete.org/archives/9241-update-on-the-systemd-issue might be relevant for you. Yeah, this might be relevant. When I read that ZFS has init scripts with carefully-planned dependencies, I shudder. They clearly have

Bug#767350: journald: does not respect carriage return

On Fri, Oct 31, 2014 at 01:26:32PM -0700, Josh Triplett wrote: Avoid emitting incremental progress messages when not outputting to a terminal. Exactly. Zbyszek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#767350: journald: does not respect carriage return

On Thu, Oct 30, 2014 at 06:49:32PM +0100, Andreas Cadhalpun wrote: Control: retitle -1 journald: does not respect carriage return Control: reassign -1 systemd 215-5+b1 Hi Santiago, On 30.10.2014 13:12, Santiago Vila wrote: freshclam[7495]: Downloading daily-19559.cdiff [

Bug#766598: systemd: help for journalctl --until option is misleading

Thanks, patch applied upstream as http://cgit.freedesktop.org/systemd/systemd/commit/?id=7558251eef. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766050: systemd: Please look at a read-only implementation of debug-shell.service

On Mon, Oct 20, 2014 at 11:01:08PM +0200, Richard Hartmann wrote: On Mon, Oct 20, 2014 at 9:01 PM, Martin Pitt mp...@debian.org wrote: Perhaps a better thing would be to always log systemd events/changes to tty9? There is no scrollback buffer while its logging in the background (i. e. you

Bug#766039: please document debug-shell.service in README.Debian

On Mon, Oct 20, 2014 at 01:02:25PM +0200, Stefano Zacchiroli wrote: Package: systemd Version: 215-5+b1 Severity: wishlist Please document in README.Debian information about how to enable the debug-shell service for debugging bootup/shutdown problems. Something like the following (credit:

Bug#759607: netfilter-persistent: contains invalid dependency in unit file

Package: netfilter-persistent Version: 1.0.1 Severity: normal systemd[1]: [/lib/systemd/system/netfilter-persistent.service:5] Failed to add dependency on systemd-modules-load, ignoring: Invalid argument systemd[1]: [/lib/systemd/system/netfilter-persistent.service:6] Failed to add dependency

Bug#759607: netfilter-persistent: contains invalid dependency in unit file

On Fri, Aug 29, 2014 at 12:39:37AM +0200, Zbigniew Jędrzejewski-Szmek wrote: systemd[1]: [/lib/systemd/system/netfilter-persistent.service:5] Failed to add dependency on systemd-modules-load, ignoring: Invalid argument systemd[1]: [/lib/systemd/system/netfilter-persistent.service:6] Failed

Bug#756903: systemd: Boot hangs if filesystems unavailable

On Tue, Aug 26, 2014 at 12:44:07AM -0400, Stefan Monnier wrote: Exactly. I hope the reasoning behind current defaults has been explained adequately. Not sure what you mean by adequately. I understand your argument, but I disagree with it. Do you understand my argument? Yes, I understand

Bug#756903: systemd: Boot hangs if filesystems unavailable

On Sat, Aug 23, 2014 at 09:33:56AM -0400, Stefan Monnier wrote: Yes, you can configure such behaviour. I already have plenty of ways to configure the behavior I need. This discussion is about the default behavior. Exactly. I hope the reasoning behind current defaults has been explained

Bug#759020: python-llvm: version string contains 'tag: '

Package: python-llvm Version: 0.12.6-2 Severity: normal Tags: sid It seems that __version__ string contains 'tag: ' prefix by mistake. At least numba is tripped up by this, since it expects the normal major.minor.micro sequence. import llvm llvm.__version__ 'tag: 0.12.6' $ dpkg -l

Bug#759021: python-llvm: please add support for python 3

Package: python-llvm Version: 0.12.6-2 Severity: normal Tags: sid Upstream supports Python 3 (3.3 and 3.4 are listed in setup.py). It would be great to have python3-llvm subpackage. -- System Information: Debian Release: 6.0.9 APT prefers oldstable APT policy: (990, 'oldstable'), (500,

Bug#756903: systemd: Boot hangs if filesystems unavailable

On Fri, Aug 22, 2014 at 10:30:47AM -0400, Stefan Monnier wrote: - If a mount fails, keep on booting. And then do your best to try and bring this problem to the attention of someone (mentioning the nofail option in that same message). Only stop the boot if the partition is explicitly

Bug#758902: systemd: Please make ^C interrupt systemd-fsck

On Fri, Aug 22, 2014 at 07:09:56PM +0200, Alberto Fuentes wrote: Package: systemd Version: 208-6 Severity: important Please consider adding ctrl + C or whatever other means to cancel fsck during startup... http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562 Zbyszek -- To

Bug#756903: systemd: Boot hangs if filesystems unavailable

On Fri, Aug 22, 2014 at 01:51:56PM -0400, Stefan Monnier wrote: In which way is it safe and correct to interrupt the boot in this case? In the way that missing some mounts may indicate a serious problem and could lead to incorrect behaviour or data loss. Haven't heard many complaints

Bug#756903: systemd: Boot hangs if filesystems unavailable

On Sat, Aug 09, 2014 at 04:36:50PM -0400, Stefan Monnier wrote: Well, I consider the sysvinit behaviour buggy and unfortunately this lead to broken fstab configurations in the past. There are 2 changes here: 1- systemd seems to *wait* for the device to be available, whereas the old

Bug#754340: Unable to run fsck manually when instructed to do so

On Fri, Jul 18, 2014 at 06:18:28PM +0200, Bas Wijnen wrote: When booting into single user mode, things worked as expected. I was unable to remount the fs read-only; the logs you requested are attached. (The mei_me messages have always been there, also with sysv init; I don't think they are

Bug#749832: systemd: ignores /run/do-not-hibernate, hibernates after kernel update

On Fri, May 30, 2014 at 09:00:12PM -0700, Nikolaus Rath wrote: On 05/30/2014 10:46 AM, Michael Biebl wrote: Am 30.05.2014 18:34, schrieb Nikolaus Rath: The problem with simply doing nothing on hibernate when /run/do-not-hibernate exists, is that this is also not visible to the user

Bug#727708: init system discussion status

On Sun, Jan 05, 2014 at 12:16:58AM +0100, Zbigniew Jędrzejewski-Szmek wrote: git notes are used to mark backport-worthy commits. See http://lists.freedesktop.org/archives/systemd-devel/2013-September/013188.html. We currently mark patches as bugfixes (which includes fixes for bugs present

Bug#738316: [Pkg-systemd-maintainers] Bug#738316: Bug#738316: Bug#738316: systemd-inhibit(1) links to wrong man page

On Sun, Feb 09, 2014 at 11:08:41AM +0100, Michael Stapelberg wrote: control: tag -1 + pending Hi Zbigniew, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl writes: Thanks, fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=07b4b9b. You missed one instance of “systemd

Bug#738316: [Pkg-systemd-maintainers] Bug#738316: systemd-inhibit(1) links to wrong man page

Thanks, fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=07b4b9b. Zbyszek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#738207: [Pkg-systemd-maintainers] Bug#738207: Bug#738207: systemd-sysv: sockets are not removed after being stopped

See also https://bugzilla.redhat.com/show_bug.cgi?id=802748. Zbyszek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737264: /usr/share/man/man7/systemd.directives.7.gz: systemd.directives(7) is empty

On Mon, Feb 03, 2014 at 02:55:41PM +0100, Michael Biebl wrote: Am 03.02.2014 12:42, schrieb Michael Biebl: Am 02.02.2014 23:23, schrieb Sam Morris: Hm, I think we disagree on the desired results. :) I don't mean that the man page is absolutely empty... I'm referring to the actaul list of

Bug#727708: multiple init systems - formal resolution proposal

On Sat, Feb 01, 2014 at 11:25:01AM -0500, Steve Langasek wrote: Josselin has asserted not only that he considers systemd-as-init a hard dependency for GNOME in jessie, but that he expects the release team to side with him over the Technical Committee if the TC does not agree with him. This is

Bug#727708: call for votes on default Linux init system for jessie

On Tue, Jan 28, 2014 at 11:23:11AM -0800, Don Armstrong wrote: On Tue, 28 Jan 2014, Neil McGovern wrote: On Tue, Jan 28, 2014 at 11:05:18AM -0800, Don Armstrong wrote: Where feasible, software should interoperate with non-default init systems; maintainers are encouraged to accept

Bug#719945: [Pkg-systemd-maintainers] Bug#719945: Bug#719945: systemd: Hangs during shutdown (likely NFS-related)

On Sun, Jan 26, 2014 at 07:44:29PM +0100, Zbigniew Jędrzejewski-Szmek wrote: On Tue, Aug 20, 2013 at 11:30:25AM +0200, Michael Biebl wrote: Am 20.08.2013 01:14, schrieb Andreas Kloeckner: No idea, up to you. Specifying _netdev for an NFS mount feels a bit redundant. It's also a regression

Bug#719945: [Pkg-systemd-maintainers] Bug#719945: Bug#719945: systemd: Hangs during shutdown (likely NFS-related)

On Tue, Aug 20, 2013 at 11:30:25AM +0200, Michael Biebl wrote: Am 20.08.2013 01:14, schrieb Andreas Kloeckner: No idea, up to you. Specifying _netdev for an NFS mount feels a bit redundant. It's also a regression of sorts, since sysvinit appears to handle this ok. sysvinit (or rather

Bug#719945: [Pkg-systemd-maintainers] Bug#719945: systemd: Hangs during shutdown (likely NFS-related)

On Wed, Jan 22, 2014 at 11:59:27AM +, Sam Morris wrote: Package: systemd Version: 204-6 Followup-For: Bug #719945 I'm seeing this bug. Adding _netdev to the fstab entry doesn't help. I'm able to fiddle with configuration if you need my help to debug this further. /etc/fstab:

Bug#727708: init system discussion status

On Sat, Jan 04, 2014 at 06:59:46PM +, Dimitri John Ledkov wrote: Also it is sad that systemd upstream is actively promoting for everyone to execute runtime checks of is systemd-init pid1,... This is done public systemd libraries to become NOPs if not running on or not compiled for systemd,

Bug#727708: init system discussion status

On Sun, Jan 05, 2014 at 12:54:04AM +, Dimitri John Ledkov wrote: So components inside systemd-source tree do not follow what's advised to all other projects: e.g. link or statically include sd_* helper files, and perform runtime checks? The advice for other projects assumes that systemd is

Bug#727708: init system discussion status

On Sun, Jan 05, 2014 at 02:11:41AM +, Dimitri John Ledkov wrote: Were you unable to find http://pkgs.fedoraproject.org/cgit/systemd.git/log/?h=f19 ? It's where Fedora has all of their packaging.. As explained by Zbigniew Jędrzejewski-Szmek, that is not actually where that happens. Hm

Bug#727708: requirement of non-forking startup protocol

| 8. Policy rules for support for init systems must: | |(a) Specify the use of a non-forking startup protocol (for |upstart and systemd), I'm not sure about upstart, but systemd is perfectly happy with daemons which double fork (Type=forking in systemd parlance). It is mildly

Bug#727708: requirement of non-forking startup protocol

On Thu, Jan 02, 2014 at 10:04:12PM +, Ian Jackson wrote: Zbigniew Jędrzejewski-Szmek writes (Bug#727708: requirement of non-forking startup protocol): | 8. Policy rules for support for init systems must: | |(a) Specify the use of a non-forking startup protocol

Bug#727708: Info received (Bug#727708: requirement of non-forking startup protocol)

Yeah, most daemons that write external PID files have issues with external PID files left from other running instances of the same daemon. (I assume that's what you're talking about.) It's probably possible to avoid that with judicious use of file locking, but that's not common and is more

Bug#727708: requires in systemd

As I understand, a systemd unit with Requires=jobTwo will not start without jobTwo running. If you request the start of jobOne, without jobTwo running, systemd will start jobTwo in addition to jobOne. There's also a Requisite= dependency, where if jobTwo isn't runnning, starting jobOne will

Bug#727708: socket activation

Steve Langasek vor...@debian.org wrote: However, I think this gets to the heart of why upstart upstream has avoided ever recommending the use of socket-based activation. There are some fairly fundamental problems that basically halted development of socket-based activation in upstart, and a

Bug#731387: [systemd-ui] Bug#731387: workaround for systemadm crashes

Can you instead try systemd-ui-3, recompiled with a recent vala? With vala 0.22 it doesn't seem to crash (or at least not that much, I haven't given it much testing). Also valgrind doesn't complain, except about un-freed memory during exit. Zbyszek -- To UNSUBSCRIBE, email to

Bug#727708: [PATCH] systemctl: allow globbing in commands which take multiple unit names

As discussed on IRC, here's a patch which takes the simple approach of allowing globbing on loaded unit names in various (almost all :)) systemctl commands. Comments? (There were some preperatory patches which I'm not posting here. Please fetch from

Bug#727708: [PATCH] systemctl: allow globbing in commands which take multiple unit names

On Thu, Dec 26, 2013 at 09:41:42PM +0100, Lennart Poettering wrote: On Thu, 26.12.13 10:09, Russ Allbery (r...@debian.org) wrote: What I've switched to instead is using tiny enums for this purpose. So: enum mangle_type { MANGLE_NOGLOB = 0, MANGLE_GLOB = 1

Bug#727708: [PATCH] systemctl: allow globbing in commands which take multiple unit names

On Thu, Dec 26, 2013 at 06:49:31PM +0100, Lennart Poettering wrote: Looks good. But maybe an additional warning should be printed if people use globs on the systemctl start command line? Some shorter version of the blurb you added to the man page? i am pretty sure people will run into this

Bug#727708: init multiple instances of a daemon

On Sun, Dec 22, 2013 at 03:56:04PM -0800, Russ Allbery wrote: Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl writes: But this should be safe for instance units, so I'd like to see 'systemctl stop/status/... server@*.service' implemented. That would be very useful for distribution

Bug#727708: init multiple instances of a daemon

On Sun, Dec 22, 2013 at 12:48:47PM -0800, Russ Allbery wrote: upstart calls this instances and systemd calls this unit templates. We too call them instances: an instance is created from a template. Daniel Pocock dan...@pocock.com.au writes: Just to clarify: does this mean systemd and

Bug#732798: [Pkg-systemd-maintainers] Bug#732798: document --full as an option for status

On Sat, Dec 21, 2013 at 10:32:46PM +0100, Michael Stapelberg wrote: Russ Allbery r...@debian.org writes: systemctl status service truncates log messages from the journal to 80 columns by default. Some experimentation revealed that --full will prevent this and show the full log message, but

Bug#732603: ITP: python-daemonize -- Python module for writing system daemons

On Thu, Dec 19, 2013 at 10:19:55AM +, Neil Williams wrote: On Thu, 19 Dec 2013 10:46:02 +0100 Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Package: wnpp Severity: wishlist Owner: Mike Gabriel mike.gabr...@das-netzwerkteam.de * Package name: python-daemonize

Bug#732157: [Pkg-systemd-maintainers] Bug#732157: Notification in non-C programs

On Tue, Dec 17, 2013 at 06:51:19PM -0800, Nikolaus Rath wrote: A nice thing about the SIGSTOP mechanism is that it can trivially be used even in programs not written in C. Any Perl or Python script (and there are plenty of daemons written in these languages) can send itself SIGSTOP. Using

Bug#732156: [Pkg-systemd-maintainers] Bug#732156: Bug#732156: Precise documentation for ExecStart command syntax

On Sat, Dec 14, 2013 at 11:18:55PM +0100, Michael Stapelberg wrote: Hi Ian, Ian Jackson ijack...@chiark.greenend.org.uk writes: Reading systemd.service(5), I'm confused about the exact syntax and quoting for the ExecStart= directive. I've now pushed a patch which expands this section and

Bug#725422: [Pkg-systemd-maintainers] Bug#725422: Bug#725422: Bug#725422: systemd set kernel.sysrq=16

Hi Goffredo, On Thu, Nov 28, 2013 at 10:19:41PM +0100, Goffredo Baroncelli wrote: Hi Michael, On 2013-11-28 21:51, Michael Stapelberg wrote: Hi Goffredo, Goffredo Baroncelli kreij...@inwind.it writes: Systemd has as main target Fedora. Debian is different from Fedora, so Nope.

Bug#725422: [Pkg-systemd-maintainers] Bug#725422: Bug#725422: systemd set kernel.sysrq=16

On Thu, Nov 28, 2013 at 08:50:03AM +0100, Goffredo Baroncelli wrote: [1] I repeat I am not arguing about the values, I am arguing that a package which aim to replace the init must change a setting which aren't related to the package functionality. Hi Goffredo, upstream value for the sysrq

Bug#725422: [Pkg-systemd-maintainers] Bug#725422: Bug#725422: systemd set kernel.sysrq=16

So we're in agreement, except for this last point... On Thu, Nov 28, 2013 at 07:27:34PM +0100, Goffredo Baroncelli wrote: This is the point where we have a totally different opinion: - is job of systemd to set the sysctl values ? Yes. - is job of systemd decide *which values* have to be set ?

Bug#727708: tech-ctte: Decide which init system to default to in Debian.

On Wed, Oct 30, 2013 at 03:10:16PM +0100, Helmut Grohne wrote: The interfaces of all init systems (except sysvinit, but are we really considering that one?) still are somewhat in flux, so this is the point where we can still influence and shape them. dream Imagine a world where upstart and

Bug#727708: tech-ctte: Decide which init system to default to in Debian.

On Wed, Oct 30, 2013 at 09:50:53PM -0400, Theodore Ts'o wrote: On Wed, Oct 30, 2013 at 06:18:29PM -0700, Russ Allbery wrote: I suspect you and I have a root disagreement over the utility of exposing some of those degrees of freedom to every init script author, but if you have some more

Bug#725815: [Pkg-systemd-maintainers] Bug#725815: [systemd-sysv] CIFS-mounts in fstab with comment=x-systemd and automount delay shutdown

On Tue, Oct 08, 2013 at 11:49:48PM +0200, Michael Biebl wrote: Am 08.10.2013 22:23, schrieb Silvério Santos: Is it possible that the network is torn down before the unmount happens? Fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=77009452cf.

Bug#718592: [Pkg-systemd-maintainers] Bug#718592: Handle shipping .socket files

On Fri, Aug 02, 2013 at 07:04:49PM +0200, Michael Stapelberg wrote: Package: dh-systemd Version: 1.7 Severity: normal Hi, as discussed at http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2013-August/000328.html, it would be good for dh-systemd to be able to ship .socket

Bug#717491: [Pkg-systemd-maintainers] Bug#717491: documentation: file references all point to /usr/lib

On Sun, Jul 21, 2013 at 02:59:14PM +0200, Michael Biebl wrote: But since we already do XSL transformations, we can just use xslt to do the processing for us. There's a list of replacements called $(substitutions) in Makefile.am, which can be used to insert configure variables into the .c sources

Bug#716369: fixed upstream

http://cgit.freedesktop.org/systemd/systemd-ui/commit/?id=7245ad7 Zbyszek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#714202: [Pkg-systemd-maintainers] Bug#714202: puppet: [PATCH] improve systemd packaging, use dh-systemd

On Wed, Jun 26, 2013 at 08:59:38PM +0200, Michael Stapelberg wrote: diff --git a/debian/puppet.service b/debian/puppet.service index a168128..1607745 100644 --- a/debian/puppet.service +++ b/debian/puppet.service @@ -6,7 +6,6 @@ After=basic.target [Service] Type=forking

  1   2   >