Bug#949867: Patch to support overriding default SOAP location

2021-07-29 Thread Mark Hindley
Control: tags -1 patch Bastian, Attached is a patch to implement this which I hope you will find useful. Thanks for considering including it. Mark >From e5ac80638456ca5cf5da69a1699d016b380ab0a0 Mon Sep 17 00:00:00 2001 From: Mark Hindley Date: Thu, 29 Jul 2021 17:59:09 +0100 Subject: [PA

Bug#976048: ITP: seatd -- Minimal user, seat and session?? management daemon

2021-05-19 Thread Mark Hindley
On Wed, May 19, 2021 at 03:30:56PM +0200, deb...@nilux.be wrote: > > I have addressed most of these, however I don't have any systems with > > systemd > > on. If you would like to write and send me a service file, I will > > happily > > include it. > > > > Looking at the git repo, it seems that

Bug#976048: ITP: seatd -- Minimal user, seat and session?? management daemon

2021-05-19 Thread Mark Hindley
On Wed, May 19, 2021 at 01:30:42PM +0200, deb...@nilux.be wrote: > I built it locally, there are few lintian messages (at first look, they seem > to be relevant), see: https://paste.debian.net/1198090/ I have addressed most of these, however I don't have any systems with systemd on. If you would

Bug#976048: ITP: seatd -- Minimal user, seat and session management daemon

2021-05-19 Thread Mark Hindley
On Tue, May 18, 2021 at 07:11:54PM +0200, deb...@nilux.be wrote: > > I also work on Devuan and already have seatd packaged there[1]. I have > > just > > updated it to version 0.5.0. I was planning on uploading to Debian once > > Bullseye > > is released. > > Actually, it would be great if it

Bug#976048: ITP: seatd -- Minimal user, seat and session management daemon

2021-05-17 Thread Mark Hindley
Henry-Nicolas, Thanks for following up with this. On Mon, May 17, 2021 at 04:26:58PM +0200, Henry-Nicolas Tourneur wrote: > Hello Mark, > > libseat will become a dependency for wlroots as of version 0.14.0 of the > latter. > Would you need any help working on this package? I also work on

Bug#986838: unblock: openrc/0.42-2.1

2021-04-12 Thread Mark Hindley
). + + -- Mark Hindley Fri, 02 Apr 2021 11:16:00 +0100 + openrc (0.42-2) unstable; urgency=medium * Team upload. diff -Nru openrc-0.42/debian/libeinfo-dev.links.in openrc-0.42/debian/libeinfo-dev.links.in --- openrc-0.42/debian/libeinfo-dev.links.in1970-01-01 01:00:00.0 +0100 +++ openrc

Bug#985509: openrc: diff for NMU version 0.42-2.1

2021-04-02 Thread Mark Hindley
package symlinks in /usr/lib target shared libraries in +/lib. (Closes: #985509). + + -- Mark Hindley Fri, 02 Apr 2021 11:16:00 +0100 + openrc (0.42-2) unstable; urgency=medium * Team upload. diff -Nru openrc-0.42/debian/libeinfo-dev.links.in openrc-0.42/debian/libeinfo-dev.links.in

Bug#980898: elogind: reduce Build-Depends

2021-02-10 Thread Mark Hindley
Control: tags -1 pending Helmut, Many thanks for this. Queued for the next upload. Mark

Bug#980898: elogind: reduce Build-Depends

2021-01-25 Thread Mark Hindley
Helmut, Thanks for this. On Sat, Jan 23, 2021 at 07:11:01PM +0100, Helmut Grohne wrote: > Source: elogind > Version: 246.9.1-1+debian1 > Tags: patch > User: helm...@debian.org > Usertags: rebootstrap > > elogind participates in dependency loops relevant to architecture > bootstrap. Instead of

Bug#980077: apt-cacher: please recognize new pdiff name format by default

2021-01-14 Thread Mark Hindley
On Thu, Jan 14, 2021 at 08:49:36AM -0500, Aaron M. Ucko wrote: > Mark Hindley writes: > > > pdiff_files_regexp = (?:^|[/-])2\d{3}-\d{2}-\d{2}-\d{4}\.\d{2}\.gz$ > > Yeah, that may well suffice after all; I just threw together a quick > tweak on the basis of aptitude's t

Bug#980077: apt-cacher: please recognize new pdiff name format by default

2021-01-14 Thread Mark Hindley
Aaron, On Thu, Jan 14, 2021 at 11:05:52AM +, Mark Hindley wrote: > > pdiff_files_regexp = > > (?:^|[/-])2\d{3}-\d{2}-\d{2}-\d{4}\.\d{2}\.(?:gz|pdiff.*)$ > > Looks reasonable to me. Thanks for the suggestion. Actually shouldn't it be pdiff_files_regexp = (?:^|[/-])2\d

Bug#980077: apt-cacher: please recognize new pdiff name format by default

2021-01-14 Thread Mark Hindley
Control: tags -1 pending Aaron, On Wed, Jan 13, 2021 at 09:33:40PM -0500, Aaron M. Ucko wrote: > Package: apt-cacher > Version: 1.7.21+nmu1 > Severity: normal > > AFAICT, metadata deltas now have filenames along the lines of > T-2021-01-13-2000.21-F-2021-01-13-2000.21.pdiff, which don't match >

Bug#975075: tech-ctte: non-systemd dependencies in non-NM packages

2021-01-11 Thread Mark Hindley
Simon, On Sun, Jan 10, 2021 at 08:03:18PM +, Simon McVittie wrote: > I wouldn't want to give a ruling that would be interpreted as precedent to > (effectively) overrule multiple maintainer decisions (whether they're > decisions by a single maintainer in multiple packages, or multiple >

Bug#923198: would it work with elogind?

2021-01-02 Thread Mark Hindley
Sven, Sorry about the slow reply with this. On Mon, Sep 30, 2019 at 08:41:41PM +0200, Sven Joachim wrote: > > But, instead of removing, you can change: > > Recommends: libpam-systemd > > to > > Recommends: default-logind | logind > > > > which works nicely with elogind. > > Makes sense.

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-23 Thread Mark Hindley
Elana, Thanks for passing this on. On Mon, Dec 21, 2020 at 03:36:45PM -0800, Elana Hashman wrote: > Less than 1% of users are installing sysvinit-core, with a steady > downward trend.[1] I accept that the number of users is small, although the figures referenced omit users of openrc and runit.

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-15 Thread Mark Hindley
Sean and Simon, On Mon, Dec 14, 2020 at 01:17:30PM -0700, Sean Whitton wrote: > > In the cases where the regression was accidental, ideally, the answer > > would be someone calmly and politely offering a tested patch, but it > > sadly seems equally likely to result in hostility, and I think it's

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-15 Thread Mark Hindley
On Tue, Dec 15, 2020 at 09:51:56AM +, Simon McVittie wrote: > On Mon, 14 Dec 2020 at 22:56:57 +0100, Philip Hands wrote: > > Could I just check if there's a point of common acceptability which both > > sides of this discussion could live with? > > > > libpam-systemd |

Bug#976868: libelogind-dev: does not provide libsystemd-dev

2020-12-08 Thread Mark Hindley
Control: tags -1 wontfix Maxim, Thanks for this. On Tue, Dec 08, 2020 at 08:00:53PM +, Maxim Chintalov wrote: > Package: libelogind-dev > Version: 243.7-1+debian1 > Severity: normal > X-Debbugs-Cc: maximchinta...@mail.ru > > Dear Maintainer, > > I am attempting to install

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-12-01 Thread Mark Hindley
Josh, On Mon, Nov 30, 2020 at 04:24:28PM -0800, Josh Triplett wrote: > If (hypothetically) network-manager upstream > decided to remove those legacy fallbacks, the maintainer would then be > in a position of either: But that is not what this particular discussion is about. Personally, I have no

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-30 Thread Mark Hindley
Simon, Thanks for your clear and insightful comments. On Sun, Nov 29, 2020 at 11:58:15PM +, Simon McVittie wrote: > On Wed, 18 Nov 2020 at 17:33:26 +, Matthew Vernon wrote: > > #921012 is about changing network-manager to Depend upon "default-logind | > > logind" rather than

Bug#976048: ITP: seatd -- Minimal user, seat and session management daemon

2020-11-28 Thread Mark Hindley
Package: wnpp Severity: wishlist Owner: Mark Hindley * Package name: seatd Version : 0.4.0 Upstream Author : Kenny Levinsen * URL : https://git.sr.ht/~kennylevinsen/seatd * License : Expat Programming Lang: C Description : Flexible user, seat

Bug#974651: libelogind0 incompatibel with rsyslog

2020-11-21 Thread Mark Hindley
Lorenzo, On Sat, Nov 14, 2020 at 04:30:08PM +, Mark Hindley wrote: > > However in the log I see > >  /etc/elogind/logind.conf:14: Unknown section 'Login'. Ignoring. > >  /etc/elogind/logind.conf:38: Unknown section 'Sleep'. Ignoring. > > > > Not sure if it's

Bug#974651: libelogind0 incompatibel with rsyslog

2020-11-14 Thread Mark Hindley
Thanks everybody for testing and reporting back. Lorenzo, On Sat, Nov 14, 2020 at 04:52:23PM +0100, Lorenzo wrote: > * no longer sends log to the kernel ring buffer (#964006) > > However in the log I see >  /etc/elogind/logind.conf:14: Unknown section 'Login'. Ignoring. >  

Bug#974651: libelogind0 incompatibel with rsyslog

2020-11-13 Thread Mark Hindley
Joerg, On Fri, Nov 13, 2020 at 12:42:32PM +0100, Joerg Dorchain wrote: > I'd be able and willing to test it, even experimental builds. Thanks. I have just built 246.0~rc2-1 for Devuan experimental[1]. The dependencies in Devuan are slightly different, but I think it should install and work in

Bug#974651: libelogind0 incompatibel with rsyslog

2020-11-13 Thread Mark Hindley
Control: forcemerge 968379 -1 Joerg, On Fri, Nov 13, 2020 at 11:59:05AM +0100, Joerg Dorchain wrote: > Package: libelogind0 > Version: 243.7-1+debian1 > > Hello, > > since rsyslog Version 8.2010.0-1 has a versioned dependency on libsystemd0 > (>= 246), I cannot install it and the current

Bug#974089: Acknowledgement (colord: FTBFS i386: colord-test-private ABRT)

2020-11-09 Thread Mark Hindley
Control: reassign -1 src:colord 1.4.5-1 Of course this would be better assigned to the source package. Mark

Bug#974089: colord: FTBFS i386: colord-test-private ABRT

2020-11-09 Thread Mark Hindley
Package: colord Version: 1.4.5-1 Severity: serious Justification: FTBFS Dear Maintainer, colord 1.4.5-1 fails to build from source on (at least) i386. Summary of Failures: 1/4 colord-test-private FAIL 2.94s (killed by signal 6 SIGABRT) Thanks. Mark

Bug#971644: [elogind/elogind] System crashed on suspend/hibernate failure (#177)

2020-11-07 Thread Mark Hindley
On Sat, Nov 07, 2020 at 06:05:18PM +0100, Trek wrote: > searching for info, I found this assertion, that made me think the > issue could be outside of elogind: > > This appears to be that Debian in user space tries to trigger the > resume when the system is falling to hibernation. >

Bug#971644: [elogind/elogind] System crashed on suspend/hibernate failure (#177)

2020-11-06 Thread Mark Hindley
Thorsten, On Fri, Nov 06, 2020 at 12:03:36AM -0800, Sven Eden wrote: >However, the behavior reported when the user hit the Hibernate key is >absolutely unsuspected. >"PM: Image not found (code -22)" sounds like the kernel tried to >hibernate, but whatever was configured, or deemed

Bug#973354: src:apt-cacher: fails to migrate to testing for too long: maintainer built arch:all binaries

2020-10-29 Thread Mark Hindley
Paul, Many thanks for this. On Thu, Oct 29, 2020 at 11:51:18AM +0100, Paul Gevers wrote: > Your package is only blocked because the arch:all binary package(s) > aren't built on a buildd. Unfortunately the Debian infrastructure > doesn't allow arch:all packages to be properly binNMU'ed. Hence, I

Bug#971644: elogind: accidentally hitting Fn-F12 crashes the system (dirty filesystem)

2020-10-04 Thread Mark Hindley
Control: forwarded -1 https://github.com/elogind/elogind/issues/177 Thorsten, Many thanks for this. On Sun, Oct 04, 2020 at 01:30:53AM +0200, Thorsten Glaser wrote: > Package: elogind > Version: 243.7-1+debian1 > Severity: critical > Justification: causes serious data loss > X-Debbugs-Cc:

Bug#959920: systemctl,elogind: No more co-installable

2020-09-03 Thread Mark Hindley
Dmitry, With the upload of systemctl/1.4.4181-1.1, this issue is no longer evident. Are you happy for me to reassign #959920 to systemctl so it can be closed with the appropriate fixed version? Thanks Mark

Bug#964006: elogind: writes to kernel log

2020-08-17 Thread Mark Hindley
Control: tags -1 fixed-upstream On Tue, Jun 30, 2020 at 10:09:01AM +0100, Mark Hindley wrote: > Control: forwarded -1 https://github.com/elogind/elogind/issues/168 > > On Tue, Jun 30, 2020 at 10:35:46AM +0200, Thorsten Glaser wrote: > > Package: elogind > > Version: 243.7-1

Bug#968425: mount cgroupv2 by default, similar to systemd

2020-08-15 Thread Mark Hindley
Harald, On Sat, Aug 15, 2020 at 07:53:13AM +0200, Harald Dunkel wrote: > Package: initscripts > Version: 2.96-4 > Severity: wishlist > > To reduce friction between systemd and "non-systemd" systems I > would suggest to mount croupv2 very early at boot time, similar > to systemd. > > Could be

Bug#968379: wireshark-common: versioned dependency on libsystemd0 breaks installability with elogind

2020-08-14 Thread Mark Hindley
Control: forwarded -1 https://github.com/elogind/elogind/issues/170 Balint and Thorsten, On Fri, Aug 14, 2020 at 08:43:31AM +0200, Balint Reczey wrote: […] > libelogind0 provides only libsystemd0 (= 243.7) which I understand > since keeping up with systemd upstream is hard, but other packages

Bug#966343: bug#498: libc6: Permission denied, intermittent in execve

2020-07-27 Thread Mark Hindley
On Mon, Jul 27, 2020 at 11:47:34AM +0200, Alessandro Vesely wrote: > > However, one thought that occurs to me is whether apparmor is causing this? > > Does > > disabling it[1] restore predictable behaviour? > > Bingo! > > Jul 27 09:47:25 pcale kernel: [ 1569.887279] audit: type=1400 >

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-03 Thread Mark Hindley
Control: reassign -1 apt-cudf Dear apt-cudf maintainers, On Tue, Jun 30, 2020 at 07:43:52PM +0200, Ansgar wrote: > On Tue, 2020-06-30 at 17:45 +0100, Mark Hindley wrote: > > I am struggling to understand how libelogind0 came to be installed in the > > build > > in the firs

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-02 Thread Mark Hindley
Control: tags -1 moreinfo On Thu, Jul 02, 2020 at 04:33:36PM +0200, Thorsten Glaser wrote: > On Thu, 2 Jul 2020, Ansgar wrote: > > > package), so the problem might also be the `Provides: logind` in > > libpam-elogind. > > Shouldn’t the package dependencies on default-logind | logind > handle

Bug#921012: Not resolved. logind dependencies still require updating.

2020-07-02 Thread Mark Hindley
Michael, These dependencies are not updated. Please don't close and archive unresolved bugs without notification or explanation. Mark

Bug#964139: network-manager: Please restore removed init script.

2020-07-02 Thread Mark Hindley
Package: network-manager Version: 1.25.91-1 Severity: important Dear Michael, I notice that today's upload of network-manager has had the init script removed. I understand that you do not use it your self and do not want to have it around, but other users do. Active removal of working scripts

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-02 Thread Mark Hindley
Control: tags -1 moreinfo On Wed, Jul 01, 2020 at 12:35:18PM +0200, Axel Beckert wrote: > Is it still the case that the buildds use aptitude for resolving > dependencies on experimental builds? Because aptitude might be even > more "creative" than apt in that regards. Thanks. That is one for

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-07-01 Thread Mark Hindley
Ansgar, On Tue, Jun 30, 2020 at 07:43:52PM +0200, Ansgar wrote: > On Tue, 2020-06-30 at 17:45 +0100, Mark Hindley wrote: > > I am struggling to understand how libelogind0 came to be installed in the > > build > > in the first place. Can you help me understand that? > &

Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

2020-06-30 Thread Mark Hindley
Ansgar, Thanks for this. On Tue, Jun 30, 2020 at 06:27:20PM +0200, Ansgar wrote: > Package: libelogind0 > Version: 243.7-1+debian1 > Severity: serious > > libelogind0's `Provides: libsystemd0` causes unrelated packages to > fail to build due to unmet dependencies. See [1] for an example. > >

Bug#964006: elogind: writes to kernel log

2020-06-30 Thread Mark Hindley
Control: forwarded -1 https://github.com/elogind/elogind/issues/168 On Tue, Jun 30, 2020 at 10:35:46AM +0200, Thorsten Glaser wrote: > Package: elogind > Version: 243.7-1+debian1 > Severity: normal > > elogind pretends it’s the kernel. It must log to syslog instead. Thorsten, Thanks for this.

Bug#962466: dbus: system-bus autopackage test fails when not run under systemd

2020-06-13 Thread Mark Hindley
On Thu, Jun 11, 2020 at 05:10:24PM +0100, Simon McVittie wrote: > On Mon, 08 Jun 2020 at 14:20:47 +0100, Mark Hindley wrote: > > A patch with the required changes is attached for your consideration. > > Thanks, I'll apply this. Thank you. > > The test attempts to d

Bug#962466: dbus: system-bus autopackage test fails when not run under systemd

2020-06-08 Thread Mark Hindley
rom 949b271aa5ab0f4bec6afc9c8eed21fa668b059f Mon Sep 17 00:00:00 2001 From: Mark Hindley Date: Mon, 8 Jun 2020 11:58:58 +0100 Subject: [PATCH] Fix system-bus autopackage test detection of systemd as PID1 --- debian/tests/system-bus | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/te

Bug#962214: Needles dependencies to policykit

2020-06-04 Thread Mark Hindley
On Thu, 4 Jun 2020 16:00:17 +0100 Klaus Ethgen wrote: > Source: gparted > Version: 1.0.0-0.1 > Severity: normal I tried this version of gparted this morning. I have a practical suggestion of a way to resolve this. gprted works fine running in a terminal as a normal user using sudo for

Bug#961393: pulseaudio,elogind: Can't install both

2020-05-24 Thread Mark Hindley
Matti, Thanks for this. Certainly pulseaudio does work with elogind. libelogind0 provides libsystemd0 so the dependencies do work: > dpkg -l|egrep 'pulse|logind' ii elogind 241.3-1+debian3 amd64user, seat and session management daemon

Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

2020-05-13 Thread Mark Hindley
some more work on it and come up with attached. It seems more likely to be portable to me. What do you think? Best wishes Mark >From 18b33cd84862f453fca8b71450d36f58cd8b141e Mon Sep 17 00:00:00 2001 From: Mark Hindley Date: Wed, 13 May 2020 10:29:10 +0100 Subject: [PATCH] Fix mountpoint

Bug#959920: systemctl,elogind: No more co-installable

2020-05-07 Thread Mark Hindley
Dimitry, On Thu, May 07, 2020 at 09:52:18AM +0100, Mark Hindley wrote: > However, that does not help in this case. elogind has to conflict with systemd > as they include some duplicate files. I have to admit to being less convinced > by > the systemctl Provides: systemd. I underst

Bug#959920: systemctl,elogind: No more co-installable

2020-05-07 Thread Mark Hindley
Axelm, Thanks for this. I haven't used systemctl myself, but it clearly has similar usage case to elogind so it would be ideal if they were coinstallable. I am very happy to work to find a solution that provides that. On Thu, May 07, 2020 at 04:38:26AM +0200, Axel Beckert wrote: > Hi, > > Axel

Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

2020-05-05 Thread Mark Hindley
rk >From b4f6561938e5920d3b72788937242d1fc9d7c448 Mon Sep 17 00:00:00 2001 From: Mark Hindley Date: Tue, 5 May 2020 15:01:35 +0100 Subject: [PATCH] Fix for misc/fallocate test build failure. This was already a known possible failure case. However, in the migration to a clearer separation of

Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

2020-05-05 Thread Mark Hindley
Source: util-linux Version: 2.35.1-1 Severity: serious Justification: FTBFS Tags: patch Dear Maintainer, Thanks for packaging the new version of util-linux. Unfortunately the testsuite fails when building in a pbuilder/cowbuilder chroot. In particular misc/fallocate and misc/mountpoint. The

Bug#950986: uninstalling cgroupfs-mount wails about sys/fs/cgroup/elogind

2020-04-25 Thread Mark Hindley
Control: tags -1 patch On Sat, Apr 25, 2020 at 10:09:29AM +0100, Mark Hindley wrote: > The solution would seem to me for cgroupfs-umount to only try to unmount the > mountpoints it created, ie those derived from /proc/cgroups. This patch fixes the issue for me. Mark diff -u /usr/bin/cg

Bug#950986: uninstalling cgroupfs-mount wails about sys/fs/cgroup/elogind

2020-04-25 Thread Mark Hindley
Tianon, I bumped into this issue recently. The problem appears to be that cgroupfs-umount tries to unmount all /sys/fs/cgroup subdirectories, even if the mount wasn't originally created by cgroupfs-mount. elogind mounts /sys/fs/cgroup/{elogind,unified} and is still using them. The solution

Bug#932047: lightdm: greeter session support for elogind

2020-04-05 Thread Mark Hindley
Hello, Just a gentle nudge on this. On Sun, 14 Jul 2019 12:59:32 +0100 Mark Hindley wrote: > Patches implementing both of these approaches are attached. I would be grateful if you could adopt one or other of these so that they can be more widely tested well in advance of the freeze. Tha

Bug#952679: lxsession-logout: Recommends should be on logind | default-logind

2020-02-27 Thread Mark Hindley
Package: lxsession-logout Version: 0.5.4-1 Severity: important Dear Maintainer, Hello, lxsession-logout currently Recommends consolekit | systemd. According to the git commit[1], the systemd recommendation was introduced to close bug #764305. However, that bug asked for a dependency on

Bug#949867: python3-debianbts: Please make BTS URL configurable

2020-01-26 Thread Mark Hindley
Package: python3-debianbts Severity: normal Version: 3.0.2 Bastian, Whilst reportbug can already be used with different debbugs installations, python3-debianbts has a hardcoded URL to Debian's soap.cgi. It would be very useful to make the SOAP URL configurable so that python3-debianbts could

Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout

2020-01-23 Thread Mark Hindley
Control: severity -1 important Thorsten, On Thu, Jan 23, 2020 at 10:10:03PM +0100, Thorsten Glaser wrote: > > This behaviour is configurable via RemoveIPC in /etc/elogind/logind.conf. > > See > > > Perhaps you could confirm that this configuration change provides the > > behaviour > > you

Bug#949698: elogind: deletes users’ files under /dev/shm/ on logout

2020-01-23 Thread Mark Hindley
On Thu, Jan 23, 2020 at 08:32:46PM +0100, Thorsten Glaser wrote: > Package: elogind > Version: 241.3-1+debian2 > Severity: critical > Justification: breaks unrelated software > > I’m using a scheme in which I store ssh-agent and gpg-agent information > across all logins (local X session or ssh or

Bug#644242: debbugs pkg: debbugs-upgradestatus does not work

2020-01-13 Thread Mark Hindley
Control: tag -1 patch

Bug#644242: debbugs pkg: debbugs-upgradestatus does not work

2020-01-13 Thread Mark Hindley
Package: debbugs Version: 2.6.0 Followup-For: Bug #644242 Don, As we discussed recently on #debbugs I have just been bitten by the original issue reported here (that debbugs-upgradestatus does not work). However, the bug report rather drifted away from that topic! The issue appears to be that

Bug#944190: release.debian.org: Allow britney to consider installability of dependencies of essential packages

2019-11-11 Thread Mark Hindley
Niels, Thanks for working on this so swiftly. On Sun, Nov 10, 2019 at 11:25:00PM +, Niels Thykier wrote: > I have attached the following patch that passes the provided test and > (AFAICT) does what we want. Please feel free to review it; I will come > back to this in a few days. I have

Bug#944190: release.debian.org: Allow britney to consider installability of dependencies of essential packages

2019-11-10 Thread Mark Hindley
rom src:elogind are manually installable into bullseye and satisfy the necessary dependencies of essential packages. Thanks very much for looking at this. Let me know if there is anything else I can do to help. Mark >From e7e78b251beaba5182377a15f6af226ccf950710 Mon Sep 17 00:00:00 2001 From

Bug#944190: release.debian.org: Allow britney to consider installability of dependencies of essential packages

2019-11-08 Thread Mark Hindley
Neils, On Fri, Nov 08, 2019 at 07:03:00AM +, Niels Thykier wrote: > Hi Mark > > Thanks for the investigative work and the patch. > > I have not had time to review the patch yet in details and hope to have > a look this weekend. Thanks. > Could I convince you to add a small test case for

Bug#944190: release.debian.org: Allow britney to consider installability of dependencies of essential packages

2019-11-05 Thread Mark Hindley
: sysvinit (via /sbin/init) >From d910a47311ba001976f90c5add8dcd0b518ccad7 Mon Sep 17 00:00:00 2001 From: Mark Hindley Date: Mon, 4 Nov 2019 12:35:57 + Subject: [PATCH] Only block negative dependencies of essential packages themselves. The behaviour of _check_inst() to exclude considerat

Bug#942503: libpoppler46: New jessie-security version causes xpdf segfault

2019-10-18 Thread Mark Hindley
On Fri, Oct 18, 2019 at 04:37:00PM +1100, Brian May wrote: > Mark Hindley writes: > > > Since this upload was an LTS NMU, I should have copied you in. > > Thanks for the report. It looks like the fix for CVE-2019-10871 might be > broken, and I might have to revert this chan

Bug#942503: libpoppler46: New jessie-security version causes xpdf segfault

2019-10-17 Thread Mark Hindley
Package: libpoppler46 Version: 0.26.5-2+deb8u12 Severity: grave Justification: renders package unusable Dear Maintainer, I have just upgraded to libpoppler46 version 0.26.5-2+deb8u12 (from +deb8u11) which has just appeared in jessie-security. The new version causes xpdf to segfault. Starting

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-10-16 Thread Mark Hindley
Simon, On Tue, Aug 27, 2019 at 05:46:32PM +0100, Mark Hindley wrote: > Simon, > > I think I have finally got to the bottom of this. As you suspected it is apt's > invocation of dpkg. See #935910. This is now resolved in apt version 1.8.4 which is in both sid and bullseye. I c

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-29 Thread Mark Hindley
Cristian, On Sat, Sep 28, 2019 at 11:41:56AM +0200, Thorsten Glaser wrote: > On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote: > > > 1. install sysvinit-core; that removes systemd-sysv but nothing else > >systemd related > > > Souldn't that work? > > It would, if but for libpam-systemd

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-28 Thread Mark Hindley
On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote: > On Fri, Sep 27, 2019 at 09:19:10AM -0400, Sam Hartman wrote: > So one thing I think we should ensure is we don't end up uninstalling > systemd without an explicit user choice. Julien, I appreciate that you are suggesting some

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-27 Thread Mark Hindley
Julien, On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote: > So one thing I think we should ensure is we don't end up uninstalling > systemd without an explicit user choice. > > The "init" package has the "Important: yes" control field which as I > understand it tells apt to behave

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-27 Thread Mark Hindley
Sam, On Fri, Sep 27, 2019 at 09:19:10AM -0400, Sam Hartman wrote: > >>>>> "Mark" == Mark Hindley writes: > > Mark> Sam, Since I cannot get a working and robust dpkg-divert > Mark> solution, I feel the need to revisit the validity of these >

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-26 Thread Mark Hindley
On Thu, Sep 26, 2019 at 12:52:27PM +0200, Thorsten Glaser wrote: > On Thu, 26 Sep 2019, Mark Hindley wrote: > > > It is possible to get APT to attempt a solution by specifically requesting > > 'apt > > install libelogind0 sysvinit-core'. This removes systemd-sysv and t

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-26 Thread Mark Hindley
Sam, Since I cannot get a working and robust dpkg-divert solution, I feel the need to revisit the validity of these concerns. On Mon, Sep 23, 2019 at 03:03:57PM -0400, Sam Hartman wrote: > >>>>> "Mark" == Mark Hindley writes: > >> If we are going to use

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-25 Thread Mark Hindley
On Thu, Sep 26, 2019 at 12:11:47AM +0200, Thorsten Glaser wrote: > On Wed, 25 Sep 2019, Mark Hindley wrote: > > > Thanks. Triggers may be an answer to the libsystemd soversion issue. > > Mind that anything that runs between unpacking the new libsystemd0 > and running

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-25 Thread Mark Hindley
On Wed, Sep 25, 2019 at 10:09:15PM +0200, Thorsten Glaser wrote: > On Wed, 25 Sep 2019, Mark Hindley wrote: > > > libelogind0 can be coninstalled with libsystemd0. However, it is fragile > > because > > the file that needs to be diverted out of the way

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-25 Thread Mark Hindley
On Mon, Sep 23, 2019 at 04:16:05PM -0400, Sam Hartman wrote: > Mark> Anyway, I am happy to try to work up a dpkg-divert solution if > Mark> that is likely to be more acceptable. > > I don't know if it will be. > I'm trying to be a facilitator here and make sure all sides understand > each

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-24 Thread Mark Hindley
Ian, Thanks for this. On Tue, Sep 24, 2019 at 07:28:29AM +0800, Ian Campbell wrote: > On Fri, 2019-09-20 at 10:16 +0100, Mark Hindley wrote: > Would it be any help at all of the "dbus client-ish" bits and the > "direct API-ish" bits of the two libraries were

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-23 Thread Mark Hindley
On Mon, Sep 23, 2019 at 03:34:50PM -0400, Sam Hartman wrote: > Hi. > I've looked a bit at the systemd code as compared to the elogind code. > > One of the major reasons that libsystemd0 cannot be used as a > replacement for libelogind0 is that elogind does not have compatible > cgroup naming. >

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-23 Thread Mark Hindley
On Mon, Sep 23, 2019 at 03:03:57PM -0400, Sam Hartman wrote: > Foo-package depends on the latest libsystemd0. I'm running unstable or > testing. The latest libsystemd0 isn't building on my arch yet. But > elogind is simpler and has build fine on my arch. I install foo-package > and suddenly

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-23 Thread Mark Hindley
Sam, Many thanks for this. On Mon, Sep 23, 2019 at 11:58:18AM -0400, Sam Hartman wrote: Mark> I have tried the approach suggested by Laurent of using Mark> elogind with libsystemd0 and I could not get the sd-*(3) APIs Mark> to function correctly. > What trouble did you run into? That

Bug#940971: init script takes 90 seconds

2019-09-22 Thread Mark Hindley
Simon, On Sun, Sep 22, 2019 at 09:05:32PM +0200, Simon Richter wrote: > Package: dbus > Version: 1.12.16-1 > Severity: important > > Hi, > > /etc/init.d/dbus is hanging pretty much exactly 90 seconds on either boot > or manual start: [snip] > Init: sysvinit (via /sbin/init) [snip] > ii

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-21 Thread Mark Hindley
On Sat, Sep 21, 2019 at 06:51:16PM +0200, Cristian Ionescu-Idbohrn wrote: > > Would you, please, start a new bug for this unless you really think > > it is the same issue (apt being broken by continuing to uninstall > > libsystemd0 after systemd prerm fails) and I will be happy to help. > > I

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-21 Thread Mark Hindley
Cristian, On Sat, Sep 21, 2019 at 04:35:39PM +0200, Cristian Ionescu-Idbohrn wrote: > I'm interested in this, but my systems (unstable and testing) are in a > slightly different state. Let's take unstable, for example: Thanks for this. However, I really don't see it as relating to Simon's

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-21 Thread Mark Hindley
Control: tags -1 - pending On Fri, Sep 20, 2019 at 04:30:00PM +0200, Thorsten Glaser wrote: > On Thu, 19 Sep 2019, Mark Hindley wrote: > > > On irc he also said there was little point in adding the Breaks: as apt > > doesn't > > rexec itself. > > Yes, even a

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-21 Thread Mark Hindley
Julian, On Wed, Sep 11, 2019 at 02:28:55PM +0100, Mark Hindley wrote: > > I don't think it's reasonable to ship this package with C/R/P > > libsystemd0. > > I understand that you don't like it. However, for libelogind0 to export the > same > symbols as libsystemd

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-21 Thread Mark Hindley
Laurent, On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote: > Hello, > > When I looked I elogind a while back I was able to build a package without > having a public libelogind0, I basically had that in my debian/rules file: > > # We only build the libelogind0 and

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-20 Thread Mark Hindley
Laurent, On Fri, Sep 20, 2019 at 01:29:43PM +0200, Laurent Bigonville wrote: > Can't this be stubbed or mocked on the elogind side? I presume you mean slices here? (I am not sure that slices are the only difference in implementation, but let's ignore that for now). To be honest, I am not sure.

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-20 Thread Mark Hindley
On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote: > Hello, > > When I looked I elogind a while back I was able to build a package without > having a public libelogind0, I basically had that in my debian/rules file: > > # We only build the libelogind0 and libelogind-dev if we

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-19 Thread Mark Hindley
On Thu, Sep 19, 2019 at 08:36:53PM +0100, Mark Hindley wrote: > Control: tags -1 pending > > Simon, > > On Tue, Aug 27, 2019 at 05:46:32PM +0100, Mark Hindley wrote: > > I think I have finally got to the bottom of this. As you suspected it is > > apt's > >

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

2019-09-19 Thread Mark Hindley
Control: tags -1 pending Simon, On Tue, Aug 27, 2019 at 05:46:32PM +0100, Mark Hindley wrote: > I think I have finally got to the bottom of this. As you suspected it is apt's > invocation of dpkg. See #935910. This has now been fixed in apt 1.9.4 (experimental). I propose to add Break

Bug#940681: elogind: Should only build-depend on libseccomp-dev on architectures supporting it

2019-09-18 Thread Mark Hindley
Control: tags -1 pending Adrian, On Thu, Sep 19, 2019 at 01:13:20AM +0200, John Paul Adrian Glaubitz wrote: > Source: elogind > Severity: normal > > Hello! > > Currently, elogind unconditionally build-depends on libseccomp-dev despite > the fact > that not all supported architectures in

Bug#940034: elogind and the release team block

2019-09-11 Thread Mark Hindley
Julien, On Wed, Sep 11, 2019 at 03:07:51PM +0100, Mark Hindley wrote: > I would hope we can all accept those. If so, there is no requirement for a > manual block: at the moment there are RC bugs which prevent migration. If or > when they are resolved migration can occur based on the rele

Bug#940034: elogind and the release team block

2019-09-11 Thread Mark Hindley
Sam, Thanks On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote: > I reached out to jcristau to talk about his block hint. > Based on our IRC discussion, it sounds like he was having trouble > bringing himself to remove the hint presumably because he doesn't think > the broader issue was

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

2019-09-11 Thread Mark Hindley
Julien, Thank you. On Wed, Sep 11, 2019 at 02:48:19PM +0200, Julien Cristau wrote: > -UID: 41176 > > Package: libelogind0 > Version: 241.3-1+debian1 > Severity: serious > > I wrote this in #934132 but that is being ignored so I'll repeat here.

Bug#935304: Please reconsider. Thanks

2019-09-11 Thread Mark Hindley
On Tue, Sep 10, 2019 at 11:10:52AM +0200, Michael Biebl wrote: > Anyway, I marked this wishlist, wontfix as the dependency is there for a > reason. libpam-systemd is non-functional without systemd as PID 1, so > this dependency will stay and is not optional (recommends) Michael, I would like to

Bug#939970: lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out with elogind

2019-09-10 Thread Mark Hindley
On Tue, Sep 10, 2019 at 05:03:37PM +0200, Vincent Lefevre wrote: > Package: lightdm > Version: 1.26.0-5 > Severity: important > > I have a machine still using sysvinit, and systemd-shim has been > replaced by elogind for such machines. The dependencies have been > updated in lightdm 1.26.0-4. But

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-10 Thread Mark Hindley
On Thu, Sep 05, 2019 at 06:44:26PM +0100, Mark Hindley wrote: > Julien, > > On Tue, Sep 03, 2019 at 09:03:42PM +0100, Mark Hindley wrote: > > Control: severity 934491 serious > > > > On Tue, Sep 03, 2019 at 09:34:51PM +0200, Julien Cristau wrote: > > > An

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-05 Thread Mark Hindley
Julien, On Tue, Sep 03, 2019 at 09:03:42PM +0100, Mark Hindley wrote: > Control: severity 934491 serious > > On Tue, Sep 03, 2019 at 09:34:51PM +0200, Julien Cristau wrote: > > Anyway, I guess if #934491 is upgraded to RC then I can drop the block > > hint. #934491 is now

<    1   2   3   4   5   6   7   8   >