emd
> does
> in this regard and if necessary make the necessary changes to elogind so it
> can
> be built on architectures without libseccomp support?
Thanks for the pointer on this.
Yes, happily.
I have made the changes in git and it will be in the next upload.
Thanks.
Mark
signature.asc
Description: Digital signature
2 (2019-08-28) x86_64
> GNU/Linux
> ls -l /lib/*/libc.so.6
> lrwxrwxrwx 1 root root 12 Mai 1 19:24 /lib/x86_64-linux-gnu/libc.so.6 ->
> libc-2.28.so
The machine in question runs in a VirtualBox VM.
Best regards,
Mark Weyer
ade the nx-libs
packages (libnx-x11-6, libxcomp3, libxcompshad3, nx-x11-common, nxagent,
nxproxy) to the earlier version (you can grab them from
snapshot.debian.org if necessary).
Thanks,
Mark
--
Mark Hymers
have spoken to the maintainer and
he is happy for me to upload this.
Debdiff attached for approval.
Thanks,
Mark
diff -Nru quota-4.04/debian/changelog quota-4.04/debian/changelog
--- quota-4.04/debian/changelog 2018-02-01 11:53:43.0 +
+++ quota-4.04/debian/changelog 2019-09-11 20:07
point that nxagent was exiting almost immediately in the broken
version.
We have a test VM where we can run any possible test patches if
available. Please keep myself and Joe (CC'd) in the CC list.
Thanks,
Mark
--
Mark Hymers
signature.asc
Description: PGP signature
I've just hit this bug in buster and tested the patch and it works. I'd
like to prepare an update for stable (as it's already fixed in 4.05 in
unstable), would that be ok?
Thanks,
Mark
--
Mark Hymers
signature.asc
Description: PGP signature
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
its users and for
people who choose not to use it.
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 release teams policy in
effect at that time.
Does that seem reasonable?
Mark
tant. That choice is precious and can be exercised in many ways. Most
importantly, you are free to choose not to use something that you don't like or
don't want.
Best wishes
Mark
nits does not impact libpam-systemd functionality until after a reboot.
Thank you for reconsidering.
Mark
d in lightdm 1.26.0-4. But after the upgrade (which did not
> output any warning about a regression), Restart, Suspend, Hibernate,
> Shut Down are now all greyed out.
Vincent,
I believe this is the same as the bug I submitted #932047.
You might like to try the pam configuration fix I have there?
Thanks
Mark
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
Can your check if zone->rss_newver or ((dns_zone_t
*)(event->ev_arg))->rss_newver is set in frame #5 (setnsec3param) on thread #1.
I believe I know the cause this will confirm it.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2
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
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.
Thank you.
Best wishes
Mark
he
Release Team to remove the manual migration block. That way, once all RC bugs
are satisfactorily resolved, normal migration can take place.
Thanks
Mark
can be sure there is no
problem with elogind once #935910 is fixed.
Best wishes
Mark
ing.
Thank you.
Mark
Control: tags -1 - sid
Andreas,
On Mon, Sep 02, 2019 at 05:21:13PM +0200, Andreas Beckmann wrote:
> tags 939101 + sid bullseye
Actually, this isn't present in sid AFAICS.
Thanks
Mark
On Sun, Sep 01, 2019 at 11:33:55AM +0100, Mark Hindley wrote:
> The issue appears to be the STRING_FOREACH macro and was fixed in
> systemd in v241:
Sorry, that should be FOREACH_STRING macro.
Mark
of elogind 241.3-1+debian1 to bullseye is
currently blocked (see #934132). When it is unblocked it should resolve
this issue.
Mark
ibsystemd0) if the prerm fails. Or the
default for --abort-after (currently 50) is wrong; perhaps it should be 1 when
dpkg is being invoked by APT?
Looking at the changelog the default for --abort-after was fixed in February
1999 (https://bugs.debian.org/22940) when APT was barely out of experimental.
Mark
Control: block -1 935910
On Thu, Aug 15, 2019 at 08:42:35PM +0100, Mark Hindley wrote:
> > > Unsure if that’s apt or dpkg. Plus, the failing prerm is in systemd,
> > > not in libsystemd0.
> >
> > I think this is probably dpkg, but it's dpkg being told what to do by
am-elogind
sysvinit-core
no longer breaks a sid systemd system. This means that dpkg exits immediately
after the systemd prerm fails and libsystemd0 remains installed. The
dependencies can then be fixed with apt.
I suggest that --abort-after=1 should be apt's default when forcing package
removal.
Thanks
Mark
,
I've tested and this bug was definitely fixed in the Debian pyglet
upload 1.3.0-1, so I'm going to mark it as fixed in this version.
Thanks,
Mark
--
Mark Hymers
"The older I grow, the more I distrust the familiar doctrine that age
brings wisdom."
H.L. Mencken
signature.asc
Description: PGP signature
On Wed, Aug 21, 2019 at 03:52:23PM +0200, Thorsten Glaser wrote:
> On Wed, 21 Aug 2019, Mark Hindley wrote:
>
> > You need xss-lock to join logind to xscreensaver:
> >
> > xss-lock -- xscreensaver-command -lock &
> > loginctl lock-session
> >
> >
the init in grub
menu. So the dependency fails to ensure systemd is PID 1.
I suggest that Recommends would be a more suitable relationship.
Thanks
Mark
On Wed, Aug 21, 2019 at 12:36:48PM +0100, Mark Hindley wrote:
> On Tue, Aug 20, 2019 at 11:19:30PM +0200, Thorsten Glaser wrote:
> > >I think you might need
> > >
> > >HandleLidSwitch=lock
> > >
> > >in /etc/elogind/logind.conf for that behaviour
ff installed.
I don't have any suitable hardware to test this directly, but
loginctl lock-session
doesn't work for me either.
I will take this upstream.
Thanks
Mark
le nor under X11.
I think you might need
HandleLidSwitch=lock
in /etc/elogind/logind.conf for that behaviour.
Mark
On Thu, Aug 15, 2019 at 08:02:51PM +0100, Simon McVittie wrote:
> On Thu, 15 Aug 2019 at 18:33:20 +0200, Thorsten Glaser wrote:
> > On Thu, 15 Aug 2019, Mark Hindley wrote:
> > > At this point apt has failed to remove systemd/241-7 which depends on
> > > libsys
and remove the systemd
dependency? libelogind0 provides libsystemd0 (=241.3) so could never satisfy
that requirement.
> * libsystemd0 is removed anyway
That is wrong and breaks systemd, never mind apt…
Am I missing something?
Mark
init-core, I wonder if this is really possible any
> more and, if not, why not… packages are not supposed to depend on
> systemd-sysv… (but, ouch, libpam-systemd does).
Can you point me to any official documentation that says packages should not
depend on systemd-sysv?
Thanks.
Mark
On Tue, Aug 13, 2019 at 07:58:09PM +0100, Mark Hindley wrote:
> Thorsten,
>
> Thanks for this.
>
> On Tue, Aug 13, 2019 at 04:46:32PM +0200, Thorsten Glaser wrote:
> > On Sun, 11 Aug 2019, Simon McVittie wrote:
> >
> > > Found while preparing a t
On Wed, Aug 14, 2019 at 07:22:47PM +0100, Jonathan Wiltshire wrote:
> On Sat, Aug 10, 2019 at 10:55:39AM +0100, Mark Hindley wrote:
> > On Fri, Aug 09, 2019 at 02:05:52PM +0100, Jonathan Wiltshire wrote:
> > > For the time being, yes, and for the reasons outlined in the initia
ny Conflict with
libelogind, but by the removal of libsystemd0 *before* replacing it with
libelogind0.
So far, I haven't discovered a way to mitigate or preempt that.
I would also add that it surprises me that apt requires symbols from
libsystemd.so. I haven't yet investigated what functionality that is. But that
is a side issue.
Mark
Hello Marc,
I can't reproduce this error anymore. The system was running untouched after
this Bug appeared. There was no software install reboot or anything done, Not
even the local terminal was closed. Now it works just fine using the same
conditions as before. As you mentioned that
m have not implemented it -- to
avoid the librt dependency.
Mark
eculating...)
These are useful, thank you. I will experiment and see.
Mark
ble as a standalone
> implementation of things like the LISTEN_FDS protocol.
Yes. I will add that to the description. The one exception is sd_is_mq() as
upstream has excluded POSIX message queues from the implementation.
Mark
On Sat, Aug 10, 2019 at 10:50:18AM +0100, Mark Hindley wrote:
> > When a bug is reported in policykit-1 on a system that is using elogind,
> > does the reportbug-generated message template indicate that? Is there
> > someone among the elogind maintainers who can h
Control: tags -1 - moreinfo
Simon,
Many thanks for this.
On Fri, Aug 09, 2019 at 02:35:13PM +0100, Simon McVittie wrote:
> Control: tags -1 + moreinfo
>
> On Mon, 25 Feb 2019 at 10:58:49 +0000, Mark Hindley wrote:
> > For desktops to be installable on such systems, policykit-1
items in detail and explain why they
were not of sufficient concern to warrant a block. Are there still outstanding
concerns?
Thanks.
Mark
amon, mate and budgie and there are reports of gnome working too.
Thank you for your consideration.
Mark
Package: gtkperf
Version: 0.40+ds-2+b2
Severity: normal
Dear Maintainer,
By default gtkperf uses 100 rounds.
If you change this to 1000, gtkperf crashes with:
GtkPerf 0.40 - Starting testing: Fri Aug 2 14:23:40 2019
GtkEntry - time: 0.17
GtkComboBox - time: 9.35
GtkComboBoxEntry - [xcb]
’ that
there might not be a routable IPv6 address. But I get why it’s a harder sell.
Mark Schouten
> Op 26 jul. 2019 om 10:39 heeft Chris Hofstaedtler het
> volgende geschreven:
>
> * Mark Schouten [190717 10:09]:
>> 2: set local-address to 127.0.0.1, [::1] to enable listeni
/6d351831be705cc26d897db44f878a978f4138fc
Mark
> On Jul 19, 2019, at 9:53 AM, David Fifield wrote:
>
> On Fri, Jul 19, 2019 at 08:30:32AM +0900, Mike Hommey wrote:
>> Download
>> http://ftp.mozilla.org/pub/firefox/releases/68.0.1/linux-x86_64/en-US/firefox-68.0.1.tar.bz2
>>
uly disconnect for some time and cause the
volume to be marked as RO.
> I agree that this could probably be replicated on any virtualization
platform. I'll test on virtualbox and KVM and let you know if anything is
different there.
Thanks, let me know if I can answer any questions.
-Mark
nother, but secretly holds on to the IP.
The DHCP server logs will show a final DHCPDECLINE after the ACK, and mark
the address as abandoned. The VM will still have the address leased
however. After a period of time VMware's guest tools will show all the
consumed IP's belonging to that MAC add
nother, but secretly holds on to the IP.
The DHCP server logs will show a final DHCPDECLINE after the ACK, and mark
the address as abandoned. The VM will still have the address leased
however. After a period of time VMware's guest tools will show all the
consumed IP's belonging to that MAC add
Package: postgresql-11-postgis-2.5-scripts
Version: 2.5.2+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The first symptom I noticed was in psql, complaining that
> create extension postgis;
ERROR: could not open extension control file
Package: general
Severity: important
Tags: l10n
Dear Maintainer,
While doing unrelated storage testing for our VMware integrated product, we
purposefully recreated
a storage outage by removing the iSCSI initiators from the backing array
hosting the vmdk disk
images for the virtual machine.
On Wed, Jul 17, 2019 at 08:09:05AM +, Debian Bug Tracking System wrote:
> You can follow progress on this Bug here: 932267:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932267.
Please see attached patch.
--
Mark Schouten | Tuxis B.V.
KvK: 74698818 | http://www.tuxis
Package: pdns-recursor
Version: 4.1.11-1+b10
Severity: normal
Tags: ipv6
PDNS recursor disables all IPv6 features by default. Debian resolves
localhost to ::1, so in a default setup, dig @localhost does not work.
I will include a patch that will do the following:
1: Enable
invalid is also unfortunate and
inefficient, since compression is kinda the point of the zip format.
Mark
> On Jul 12, 2019, at 8:23 PM, Adler, Mark wrote:
>
> Ben,
>
> Ah, no, I did not test the jar files. I just did, and indeed I am seeing the
> reported zip bomb detec
and perhaps better for the future, whichever logind
implementation is enabled through pam-auth could be used by sourcing the PAM
common-session.
Patches implementing both of these approaches are attached.
Many thanks,
Mark
1 file changed, 5 insertions(+)
debian/patches/05_debianize-pam
Ben,
Ah, no, I did not test the jar files. I just did, and indeed I am seeing the
reported zip bomb detections.
Thanks. I’ll look into it.
Mark
> On Jul 12, 2019, at 3:22 PM, Ben Caradoc-Davies wrote:
>
> On 13/07/2019 04:32, Adler, Mark wrote:
>> I downloaded the four fal
On Jul 12, 2019, at 9:43 AM, Santiago Vila wrote:
> I applied the commits I believed to be the fix for the zipbomb issue, i.e.
> these two:
>
> commit 41beb477c5744bc396fa1162ee0c14218ec12213
> Fix bug in undefer_input() that misplaced the input state.
> commit
a commit?
Mark
> On Jul 12, 2019, at 12:41 AM, Santiago Vila wrote:
>
> Hello.
>
> I applied your fix for the zip bomb issue to the Debian unzip package
> and shortly afterwards I received this bug report from one of our users
> (Ben Caradoc-Davies, in the Cc).
>
&
On Thu, Jul 11, 2019 at 05:48:33AM -0700, Felix Lechner wrote:
> On Thu, Jul 11, 2019 at 3:09 AM Mark Hindley wrote:
> >
> > I think lintian should differentiate between 'debian' in the upstream
> > version
> > (before the hyphen) and the packaging version (after
Package: src:linux
Version: 5.0.2-1~exp1
Severity: important
Screen flickers even before I've entered the password to decrypt the disk.
Reverting to the latest stable (4.19.x) does not show the problem with the same
severity.
-- Package-specific info:
** Version:
Linux version
number has +debianN appended, for
example 241.3-1+debian1.
I think lintian should differentiate between 'debian' in the upstream version
(before the hyphen) and the packaging version (after the hyphen). In the latter
case watch file mangling is not required.
Thanks.
Mark
ldbot:
https://builder.wildebeest.org/buildbot/#/builders?tags=bzip2
To make sure we didn't overlook any other issues.
We are now looking at better integration with some fuzzers to catch any
other issues.
Expect a 1.0.8 release soon (days, not weeks) with the patch and some
other small fixes.
Cheers,
Mark
of this.
The severity is critical (and if the bug is confirmed, I understand
that's *critical*), but I don't understand if I can upgrade or not.
I don't see "movement" in the thread since some months, and the bug just
"lies here".
Thanks in advance,
Mark
signature.asc
Descript
On Thu, Jul 04, 2019 at 05:09:08PM +0200, Michael Biebl wrote:
> Am 04.07.19 um 16:14 schrieb Mark Brown:
> > I actually see the same behaviour with the CLI and TUI as I do
> > with the GNOME settings stuff - there's nothing obvious that
> > suggests that the two con
Package: network-manager
Version: 1.14.6-2
Severity: normal
On a system with multiple wired networks Network Manager displays
them separately (eg, in the system settings app I see two network
connections listed with separate settings buttons and on/off
toggles) but in actual fact there is only a
other collection of .bz2 files.
It does already contain a testcase that still fails with the proposed
patch. It is a really odd corner case, but since we accepted it in the
past, we should really make sure it works in the future too.
I'll discuss an alternative patch upstream.
Cheers,
Mark
See the upstream discussion on the bzip2-devel mailinglist:
https://sourceware.org/ml/bzip2-devel/2019-q2/msg00024.html
In particular this workaround patch for some (buggy lbzip2 compressed)
files that bzip2 1.0.6 could decompress, but 1.0.7 (with the CVE-2019-
12900 hardening patch) cannot:
high scores file to the user's home
directory?
Thank you for your work on Debian!
Kind regards,
Mark
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable'), (101, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux
Package: libfluidsynth1
Version: 1.1.6-4
Severity: normal
Tags: patch
When recording, I run JACK with a 192kHz sample rate, to match my audio
interface, so as to minimize the cumulative errors through the audio
processing chain. Fluidsynth-based instruments appear to work, but
produce
Dear Michael
Am 05.05.19 um 21:06 schrieb Michael Biebl:
Am 05.05.2019 um 21:03 schrieb Michael Biebl:
Am 05.05.2019 um 16:23 schrieb Mark Szentes-Wanner:
Package: rsyslog
Version: 8.24.0-1
Severity: normal
Dear Michael,
I recently opened up a search query in KDE Dolphin and left the window
top.DBus" (uid=1000 pid=14887 comm="filenamesearch.so [kdeinit5]
filenamesearch local:")
I expected rsyslog to recognize repetitions of the same line and just post "the
previous message repeated 1 times". Please improve the recognition of
repetitions. I attached a few s
On 24/04/2019 21:30, Frank Scheiner wrote:
> On 4/24/19 22:07, John Paul Adrian Glaubitz wrote:
>> On 4/24/19 9:46 PM, Mark Cave-Ayland wrote:
>>> For reference the CHRP bootinfo.txt isn't a configuration file, but is
>>> actually
>>> parsed by CHRP-compl
> Adrian
Hi Adrian,
For reference the CHRP bootinfo.txt isn't a configuration file, but is actually
parsed by CHRP-compliant open firmwares directly - SPARC firmwares, including
OpenBIOS don't support them. Can you explain why grub on SPARC is trying to
access
this file?
ATB,
Mark.
Just found that systemd thought networking.service was having trouble on my
machine.
When I checked "journalctl -xe" I found the following:
ifup[18149]: run-parts: /etc/network/if-pre-up.d/whereami exited with return
code 1
ifup[18149]: ifup: pre-up script failed
systemd[1]:
Package: wnpp
Owner: Mark A. Hershberger
Severity: wishlist
Package name: python3-git-archive-all
Version : 1.19.4
Upstream Author : Ilya Kulakov
URL or Web page : https://github.com/Kentzo/git-archive-all
License : MIT
Description : Archive repository with all its
tests and therefore I'd like
> to see it fixed for buster.
Version 241.1-1 isn't in buster and I am not sure if it will make it in as there
is no sign of movement in the unblock request (#925489). But I am happy to fix
it in unstable.
Thanks
Mark
orted". I've attached a
screenshot, which you can view here: imgur.com/5drZIUB
- Mark
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8
Does this mean you're leaving stable stuck with the version broken by
the update (after applying the first patch but not the followup)? ):
-- Mark
The University of Dundee is a registered Scottish Charity, No: SC015096
.
Mark
-- System Information:
Debian Release: 8.11
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-7-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
control: tags -1 pending
out. Just so we don't have to revisit it again in the
future, how far back do you think this needs to go? lenny? earlier?
Mark
On Sat, Mar 23, 2019 at 02:39:41PM +, Mark Hindley wrote:
> Control: reopen -1
>
> On Tue, Feb 26, 2019 at 07:08:33PM +0100, Michael Biebl wrote:
> > On Thu, 31 Jan 2019 10:38:07 -0500 Dolphin Oracle
> > wrote:
> > > Package: network-manager
> > > Vers
budgie is that it
functions correctly.
If network-manager limits itself to libpam-systemd, many desktops are not
installable on non-systemd systems even though the are/could be functional.
Thanks for thinking again.
Mark
.
Patch below.
Thanks
Mark
commit 7a3084d2ba52f8aa0a01114de45d257e1feb4fe2
Author: Mark Hindley
Date: Sat Mar 23 12:35:26 2019 +
Use new logind virtual packages instead of libpam-systemd.
diff --git a/debian/control b/debian/control
index 9b1c85f..3cfb08a 100644
Mark
commit 80ee2cdafa9415a0625be129331cb5fd6636920f
Author: Mark Hindley
Date: Sat Mar 23 12:10:14 2019 +
Use new logind virtual packages for xfce4-power-manager Recommends.
diff --git a/debian/control b/debian/control
index 5a382e9..27c1d41 100644
--- a/debian/control
+++ b/debian
is no longer in the archive and the
unnecessary reference to systemd-sysv.
Patch below.
Thanks
Mark
commit 7f6e2c337fa07ae45405e4bdc743f248b2851469
Author: Mark Hindley
Date: Sat Mar 23 11:40:05 2019 +
Use new virtual logind packages for xfce4-session Recommends. Also remove
and default-logind virtual packages have been seconded for inclusion
in Debian Policy (see #917431) and libpam-elogind and libpam-systemd providing
these have been uploaded.
Patch below.
Thanks
Mark
.
The logind and default-logind virtual packages have been seconded for inclusion
in Debian Policy (see #917431) and libpam-elogind and libpam-systemd providing
these have been uploaded.
Patch below.
Thanks
Mark
commit eed2be11423b87a09badac2304a00f5c113e2612
Author: Mark Hindley
Date: Sat Mar
and default-logind virtual packages have been seconded for inclusion
in Debian Policy (see #917431) and libpam-elogind and libpam-systemd providing
these have been uploaded.
Patch below.
Thanks
Mark
On Fri, Mar 22, 2019 at 07:44:21PM +, Torrance, Douglas wrote:
> Thanks for the report! This has now been fixed in git [1].
>
> [1] https://salsa.debian.org/wmaker-team/wmshutdown/commit/4dec776
Many thanks for the quick response.
Mark
packages have been seconded for inclusion
in Debian Policy (see #917431) and libpam-elogind and libpam-systemd providing
these have been uploaded.
Patches below.
Thanks
Mark
Against unstable:
commit 8185af2138e3df094b87e7e6f7f4245b7c4afe2c
Author: Mark Hindley
Date: Fri Mar 22 18:45:04 2019
packages have been seconded for inclusion
in Debian Policy (see #917431) and libpam-elogind and libpam-systemd providing
these have been uploaded.
Patch below.
Thanks
Mark
commit
Tags: moreinfo
On Sat, Jan 19, 2019 at 10:34:02AM +, Mark Hindley wrote:
> One issue I will pass upstream is why the Docked status is taking so long to
> update. Once docked elogind should be ignoring lid events by default. (I know
> this doesn't address the underlying issue in
s not match that
> file's license in debian/copyright. The latter file is therefore
> incomplete, rather than the package not being legally distributable.
>
> Hope that makes sense.
Yes, thanks.
Sorry for my misunderstanding.
Feel free to close.
Mark
.
Surely having a more permissive license for AppStream metadata is not a problem?
Thanks
Mark
that too. However, as
elogind upstream have committed to maintaining ABI compatibility and if we do a
versioned provides, I can't come up with a breakage scenario.
> So I'd like the input from other pkg-utopia/pkg-systemd maintainers,
> especially Martin and Felipe.
Yes, me too. Thanks.
Mark
On Tue, Mar 05, 2019 at 05:58:30PM +0100, Michael Biebl wrote:
> Am 05.03.19 um 15:34 schrieb Mark Hindley:
> >
> > reassign -1 elogind
> > retitle -1 Make libelogind0 ABI compatible with libsystemd0
> > tags -1 + pending
> > thanks
> >
> > On Wed, F
ges.
Thanks
Mark
reassign -1 elogind
retitle -1 Make libelogind0 ABI compatible with libsystemd0
tags -1 + pending
thanks
On Wed, Feb 27, 2019 at 05:12:50PM +, Mark Hindley wrote:
> We are currently liasing with elogind upstream who are making libelogind ABI
> compatible with libsystemd. See
501 - 600 of 6077 matches
Mail list logo
