[Pkg-utopia-maintainers] RFS: dbus-broker/11-1 [ITP] -- Linux D-Bus Message Broker
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my "dbus-broker" package * Package name: dbus-broker Version : 11 Upstream Author : David Herrmannet al. * URL : https://github.com/bus1/dbus-broker/ * License : Apache-2.0 Section : admin Programming Lang: C Description : Linux D-Bus Message Broker It builds those binary packages: dbus-broker - Linux D-Bus Message Broker To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dbus-broker Alternatively, one can download the package with dget: dget -x https://mentors.debian.net/debian/pool/main/d/dbus-broker/dbus-broker_11-1.dsc Or from the repository: https://salsa.debian.org/dnn-guest/dbus-broker Cheers, Dan ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
Re: [Pkg-utopia-maintainers] Systemd user instance equivalent of dh_systemd_enable?
Hi Simon, I'm dropping debian-mentors@d.o from the recipients list as I think it the discussion is not relevant for that list anymore. On 08/04/2018 16:20, Simon McVittie wrote: > On Sun, 08 Apr 2018 at 08:26:13 -0600, Daniele Nicolodi wrote: >> the package is dbus-broker, a replacement for dbus-deamon. You may have >> heard of it: there has been a short exchange about its packaging for >> Debian with its developers with the Debian dbus maintainers in Cc. > > Sorry, I didn't see that conversation until now. Please use the role address > @packages.debian.org if you want to reach package maintainers: Will do, thanks. I thought I added all maintainers individual addresses at some point in the discussion, but probably I didn't... > If dbus-broker is uploaded to Debian as an optional dbus-daemon > replacement, it will definitely need to be coordinated with the dbus > source package. Having the two packages coexist is probably not going to > be straightforward to set up, and if any diversions, alternatives etc. > are going on, all maintainers of the dbus package will need to be aware > of them. I have the package ready, and it works fine without any diversion, alternatives or other trickery. It has been surprisingly easy, indeed. You can get the package here: https://salsa.debian.org/dnn-guest/dbus-broker It works fine minus replacing dbus-deamon for the user bus, which prompted the email at the origin of this thread. It needs to be done manually (see README.Debian) or installing a /etc/systemd/user/dbus.service symlink. I don't know what's the best strategy, yet. I'm happy to work with the dbus maintainers to fix any issue. Incidentally, I will be looking for a sponsor to upload the package to unstable as soon as I figure out how to solve the above minor issue. It would be great if someone among the dbus maintainers could act as sponsor. > I do not expect that dbus-broker will be compatible with every D-Bus > service in Debian. The one incompatibility that I'm reasonably sure exists > is that if the Exec= for an activatable service points to a command that > will fork (background itself) and exit 0, dbus-daemon tolerates this > (at the cost of worse error behaviour because it cannot tell whether > the service subsequently fails), while dbus-broker almost certainly does > not. This is inadvisable behaviour even with the reference dbus-daemon, > so I'd consider it to be a bug in the service, but unfortunately it can't > be detected statically. That would need to be investigated indeed. So far the package works well on a couple of very minimal installs I tried it on. Thanks! Cheers, Dan ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
Re: [Pkg-utopia-maintainers] dbus-broker Debian packaging
Hi David, On 04/03/2018 05:08, David Herrmann wrote: > *) The dbus-broker project uses submodules to link some code > statically. The easiest way to build dbus-broker is using our .tar.xz > tarballs provided with each release [1]. These include *all* source > files, including the right submodule versions. If you want to build > from -git directly, though, I recommend the strategy used by the > arch-linux -git package [2]. They check out all required repositories > and then use git to check out the correct revisions. This is > definitely more flexible than the tarball based approach, but also > needs slightly more maintenance, as you need to stay up-to-date with > the submodules. Debian tooling handles the submodules fine, I just compared the released tarball for v11 with the one generated by the Debian tooling from the git repository and they are substantially identical. However, I noticed that not all the submodules have the same license as dbus-broker, I need to complete the debian/copyright file. Also, I noticed that Red Hat is listed as the copyright holder. Is that true for all contributions? > *) The dbus-broker binary itself is definitely intended to be useful > on its own. However, no such users are known, and so far we have *not* > stabilized its API, yet. Hence, I would not split it apart now, but > leave it for a future extension. That is, something like a > `dbus-broker-core` package, which just contains the broker, but not > the launcher. I think that having `dbus-broker` and `dbus-broker-launcher` packages would be more logical, but I don't see reasons why the split cannot happen when the need will emerge, or when the API will be stable. > *) We are reworking the Fedora package at the moment. I cannot say how > the ultimate solution will look like, but the plan right now is this: > dbus-daemon is split into multiple packages. One packages > (dbus-daemon-utils) provides all the utilities (dbus-send, > dbus-monitor, ...). I would call this `dbus-utils`, but.. bikeshedding. > Another package (dbus-daemon) provides the daemon > binary and its related tools (dbus-daemon, dbus-launch, ...), as well > as a renamed service file `dbus-daemon.service`. > For dbus-broker we provide one package that ships the broker+launcher, > as well as the dbus-broker.service unit file. > Lastly, we intend to recreate the `dbus` package as a simple package > that both dbus-daemon and dbus-broker depend on, and it provides the > daemon-xml files (config and policy). If there is interest for dbus-broker in Debian and the dbus maintainers agree, I can work on patches to do the same for the Debian's dbus package. > Depending on what the default setup for your system should be, you > should run `systemctl enable dbus-{daemon,broker}.service`. They will > then create the dbus.service symlink. Fedora intends to use the > systemd-presets for this. That would need to be done differently on Debian, I guess. I will need to do some reading about what the correct solution would be there. > I hope this information is of help to you! Thank you for the detailed reply, it surely helps. Cheers, Dan ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
Re: [Pkg-utopia-maintainers] dbus-broker Debian packaging
I just pushed the packaging here: https://salsa.debian.org/dnn-guest/dbus-broker Cheers, Dan On 03/03/2018 19:00, Daniele Nicolodi wrote: > Hello Debian dbus maintainers and dbus-broker authors, > > I'm working on packaging dbus-broker for Debian [0]. > > In the packaging, I'm not sure in how many binary packages the project > should be split. I thought asking the authors and the dbus maintainers > could be valuable. > > dbus-broker provides dbus-broker-launcher and systemd unit files that > provide configuration files compatibility with the D-Bus reference > implementation, however dbus-broker can be useful in itself to implement > private buses. > > Should dbus-broker and the launcher (and the systemd unit files) be part > of two separate binary packages? Is the interface between the broker > and the launcher stable? > > Should be the system D-Bus be replaced when dbus-broker is install? > What about the user bus? > > Is the Debian Utopia team interested in team maintenance of the > dbus-broker package? I would also need a sponsor to upload the package. > > Thank you for your time. > > Cheers, > Dan > > > [0] Quoting https://github.com/bus1/dbus-broker/: > > The dbus-broker project is an implementation of a message bus as > defined by the D-Bus specification. Its aim is to provide high > performance and reliability, while keeping compatibility to the D-Bus > reference implementation. It is exclusively written for linux systems, > and makes use of many modern features provided by recent linux kernel > releases. > ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] dbus-broker Debian packaging
Hello Debian dbus maintainers and dbus-broker authors, I'm working on packaging dbus-broker for Debian [0]. In the packaging, I'm not sure in how many binary packages the project should be split. I thought asking the authors and the dbus maintainers could be valuable. dbus-broker provides dbus-broker-launcher and systemd unit files that provide configuration files compatibility with the D-Bus reference implementation, however dbus-broker can be useful in itself to implement private buses. Should dbus-broker and the launcher (and the systemd unit files) be part of two separate binary packages? Is the interface between the broker and the launcher stable? Should be the system D-Bus be replaced when dbus-broker is install? What about the user bus? Is the Debian Utopia team interested in team maintenance of the dbus-broker package? I would also need a sponsor to upload the package. Thank you for your time. Cheers, Dan [0] Quoting https://github.com/bus1/dbus-broker/: The dbus-broker project is an implementation of a message bus as defined by the D-Bus specification. Its aim is to provide high performance and reliability, while keeping compatibility to the D-Bus reference implementation. It is exclusively written for linux systems, and makes use of many modern features provided by recent linux kernel releases. ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers