Re: HFS/HFS+ are insecure

Hi Marco, hi, Marco d'Itri - 21.07.23, 10:55:39 CEST: > On Jul 21, Matthew Garrett wrote: > > > You are totally correct. > > > Kernel team, please blacklist HFS/HFS+ for automounting. > > > > Isn't this a userland policy decision? udisks will happily trigger a > > module load for hfsplus if

Re: Heads up: persistent journal has been enabled in systemd

Sam Hartman - 06.02.20, 17:11:20 CET: > >>>>> "Martin" == Martin Steigerwald writes: > Martin> Well, that is *exactly* why I thought the GR is not going > to Martin> be helpful. > > Martin> Cause in *no way* it appeared t

Re: Heads up: persistent journal has been enabled in systemd

Martin Steigerwald - 06.02.20, 14:32:57 CET: > Ansgar - 06.02.20, 13:25:06 CET: > > On Thu, 2020-02-06 at 12:30 +0100, Martin Steigerwald wrote: > > > Especially as I found that I did not use journalctl in my daily > > > practice anyway. > > > > Given you w

Re: Heads up: persistent journal has been enabled in systemd

Ansgar - 06.02.20, 13:25:06 CET: > On Thu, 2020-02-06 at 12:30 +0100, Martin Steigerwald wrote: > > Especially as I found that I did not use journalctl in my daily > > practice anyway. > > Given you wrote earlier that you moved all but one of your machines > away from

Re: Heads up: persistent journal has been enabled in systemd

Martin Steigerwald - 06.02.20, 12:26:32 CET: > Vincent Bernat - 06.02.20, 07:58:32 CET: > > ❦ 6 février 2020 09:50 +11, Dmitry Smirnov : > > >> and 2) continuing to use rsyslog isn't an option if the default > > >> changes.> > > > > > > N

Re: Heads up: persistent journal has been enabled in systemd

Vincent Bernat - 06.02.20, 07:58:32 CET: > ❦ 6 février 2020 09:50 +11, Dmitry Smirnov : > >> and 2) continuing to use rsyslog isn't an option if the default > >> changes.> > > No. I just don't want default to change. IMHO rationale for this is > > weak but everybody keeps arguing that it would

Re: Heads up: persistent journal has been enabled in systemd

Scott Kitterman - 06.02.20, 06:27:44 CET: > >Are you suggesting that voters fully understood the implications? > >Is this OK now to replace everything with systemd counterparts? > > > >I certainly voted with considerations for _init_ system. > > > >If I recall correctly, no GR option suggested to

Re: Heads up: persistent journal has been enabled in systemd

Andrey Rahmatullin - 05.02.20, 22:17:14 CET: > On Thu, Feb 06, 2020 at 07:44:43AM +1100, Dmitry Smirnov wrote: > > > We just had a GR where the project voted it was just fine to > > > systemd all the things, so this sort of thing is to be expected. > > > > Are you suggesting that voters fully

Re: Be nice to your fellow Debian colleagues

Dear Andrej, dear Andrew, Andrej Shadura - 01.01.20, 13:02:00 CET: > On Wed, 1 Jan 2020 at 12:40, Andrew McGlashan > > wrote: > > reasonable stakeholders, it is very limited to a small group of > > Debian users known collectively as DDs .. the current "gods" of > > Debian whom have ultimate

Re: Be nice to your fellow Debian colleagues

Dear Ondřej, Ondřej Surý - 01.01.20, 09:39:35 CET: > Andrew, > > look at the subject, then look at what you wrote. If you can’t find > enough kindness in the situation and you are angry then it might be > better to not write anything at all. If one outcome of the GR is to ask people to shut up…

Re: difficulty in understanding options in init-system-GR

Marco d'Itri - 07.12.19, 11:45:36 CET: > On Dec 07, Mo Zhou wrote: > > The rest options, i.e. B A D H G, look nearly the same to me: > > "first tier support for systemd, second tier for others" > > > > The only difference I noted is the bug severity for non-systemd > > support. > > > > In

Re: Integration with systemd

Martin Steigerwald - 01.11.19, 09:25:07 CET: > Adam D. Barratt - 01.11.19, 07:47:48 CET: > > On Fri, 2019-11-01 at 00:54 +0100, Svante Signell wrote: > > > On Thu, 2019-10-31 at 22:40 +0100, Marco d'Itri wrote: > > > > On Oct 31, Svante Signell wrote: > &g

Re: Integration with systemd

Adam D. Barratt - 01.11.19, 07:47:48 CET: > On Fri, 2019-11-01 at 00:54 +0100, Svante Signell wrote: > > On Thu, 2019-10-31 at 22:40 +0100, Marco d'Itri wrote: > > > On Oct 31, Svante Signell wrote: > > > > When elogind enters testing there would be many more people > > > > running > > > > Debian

Re: "the" cloud [Integration with systemd]

Hi Thomas, Thomas Goirand - 01.11.19, 01:26:58 CET: > On 10/31/19 5:13 PM, Martin Steigerwald wrote: > > It is similar with "the" cloud. > > Why is there quotes around "the", and why do you think there's only a > single instance of a cloud o

Re: Integration with systemd

Marco d'Itri - 31.10.19, 15:45:47 CET: > On Oct 31, Simon Richter wrote: […] > > The freedom to configure a system without things I do not want is > > one of the main reasons that made me switch over from Windows to > > Debian, a bit more than twenty years ago. > >

Re: Integration with systemd

Theodore Y. Ts'o - 31.10.19, 16:03:29 CET: > On Thu, Oct 31, 2019 at 01:19:56PM +0100, Martin Steigerwald wrote: > > alienate me away from Debian. This laptop, for the sake of packaging > > flexible I/O tester, is the last of my machines still running on > > Debian. All t

Re: Integration with systemd

Martin Steigerwald - 31.10.19, 13:19:56 CET: > While I do not expect maintainers of Debian packages to implement > support for alternate init systems themselves, I still believe if > someone works constructively and consistently on making such support > available in Debian, it w

Re: Integration with systemd

Hi! I thought about just silently unsubscribing from debian-devel… but as I got the impression that almost no one argues for the freedom to choose the init system here in this thread, I decided to speak up: Theodore Y. Ts'o - 31.10.19, 00:57:48 CET: > And if we do this in core Debian

Re: Bits from the DPL (August 2019)

Dear Mo. Mo Zhou - 24.09.19, 04:58:06 CEST: > For desktop users, non-systemd init plus a mordern desktop environment > such as Plasma or Gnome would be impossible on Debian, as they depend > on systemd. Some other distro such as Gentoo and FreeBSD have somehow > removed the systemd dependency for

Re: Bits from the DPL (August 2019)

Hi Sam! I took long time to write this even on still recovering from a pace in my life that feels too quick for me. But I intended this to be carefully worded in order to not hurt anyone. I hope I succeeded. My invitation: Before taking anything personal and making the choice to feel hurt

Re: Please stop hating on sysvinit

Ian Jackson - 09.08.19, 11:27:31 CEST: > Ondřej Surý writes ("Re: Please stop hating on sysvinit"): > > On 9 Aug 2019, at 09:22, Martin Steigerwald > > wrote: > > > Actually as a user of my services I do not even notice any > > > difference,

Re: Please stop hating on sysvinit

Vincent Bernat - 09.08.19, 07:00:41 CEST: > ❦ 8 août 2019 21:47 +02, Simon Richter : > >> inetd performance is very low because it needs to spawn one > >> instance for each connection. systemd socket activation has > >> absolutely 0 overhead except on the first connection (where > >> systemd

Re: Please stop hating on sysvinit, systemd… and let go of the hating anyway (was Re: do packages depend on lexical order or {daily,weekly,monthly} cron jobs?)

Russ Allbery - 08.08.19, 20:33:58 CEST: > Ondřej Surý writes: > > So, just to clarify… so, it’s ok to hate systemd, but it’s not ok > > to > > hate sysvinit (spaghetti of shell scripts)? > > Personally, I'd be happy if people would just stop hating on any free > software in general. Even buggy

Re: Please stop hating on sysvinit (was Re: do packages depend on lexical order or {daily,weekly,monthly} cron jobs?)

Philipp Kern - 08.08.19, 14:48:48 CEST: > On 2019-08-08 14:43, Holger Levsen wrote: > > On Thu, Aug 08, 2019 at 02:35:13PM +0200, Ondřej Surý wrote: > >> And there’s the problem. If we keep with sysvinit as a baseline of > >> features provided by the init, we end up with just every init > >>

Re: systemd services that are not equivalent to LSB init scripts

Hello. Theodore Ts'o - 14.07.19, 22:07: > So requiring support of non-systemd ecosystems is in general, going to > require extra testing. In the case of cron/systemd.timers, this > means testing and/or careful code inspection to make sure the > following cases work: > > * systemd &&

Re: Debian, so ugly and unwieldy!

Adam Borowski - 07.06.19, 21:09: > On Fri, Jun 07, 2019 at 11:24:03AM -0700, James Lu wrote: […] > > > * default font is ugly and poorly hinted -- the latter is > > > especially jarring> > > > > on a low-resolution screen I'm at right now, the former still > > > applies to one's proper

Re: Debian, so ugly and unwieldy!

Adam Borowski - 07.06.19, 17:24: > This is about GUI appearance and ergonomy. > > I'll concentrate at XFCE, as I consider GNOME3's UI a lost cause, thus > I'd find it hard to bring constructive arguments there. Similar to you I do not "get" GNOME 3. I have no idea why I would like to use it.

Re: Debian, so ugly and unwieldy!

Bjørn Mork - 07.06.19, 19:22: > Adam Borowski writes: > > => Install gtk3-nocsd by default in all desktop tasks but Gnome. > > It's not> > > perfect but it helps. > > That's nice. Thanks for the tip. I enjoy nice tools like eog and > evince, but have always been annoyed by the

Re: .deb format: let's use 0.939, zstd, drop bzip2

Adrian Bunk - 08.05.19, 21:45: > On Wed, May 08, 2019 at 07:38:26PM +0200, Adam Borowski wrote: > >... > > > > So let's pick compressors to enable. For compression ratio, xz > > still wins (at least among popular compressors). But there's a > > thing to say about zstd: firefox.deb zstd -19 takes

Accepted fsmark 3.3-3 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Feb 2019 13:28:59 +0100 Source: fsmark Binary: fsmark fsmark-dbgsym Architecture: source amd64 Version: 3.3-3 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald Changed-By: Martin Steigerwald

Accepted fio 3.12-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 21 Jan 2019 09:29:38 +0100 Source: fio Binary: fio gfio Architecture: source Version: 3.12-2 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald Changed-By: Martin Steigerwald Closes: 919670 Description

Re: usrmerge -- plan B?

Marco d'Itri - 23.12.18, 22:30: > On Dec 23, Martin Steigerwald wrote: > > I think I have seen this with either SLES or RHEL that they created > > symlinks for every binary in /bin and /sbin, pointing to the binary > > in /usr/bin and /usr/sbin. I did not understand why a

Re: usrmerge -- plan B?

Guillem Jover - 23.12.18, 17:17: > On Sun, 2018-12-23 at 16:45:28 +0100, Guillem Jover wrote: > > On Sun, 2018-12-23 at 04:06:14 +0100, Guillem Jover wrote: > > > […] They also imply to permanently suffer the aliasing problems. > > > > To expand and clarify a bit on this. We have aliasing in

Accepted fio 3.12-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Nov 2018 16:47:49 +0100 Source: fio Binary: fio gfio Architecture: source Version: 3.12-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald Changed-By: Martin Steigerwald Description: fio

Re: Debian Buster release to partially drop non-systemd support

Bastian Blank - 19.10.18, 12:25: > On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote: > > So Devuan almost doubles the percentage of sysvinit-core > > installations. > Devuan is _not_ Debian. They forked it, with the full knowledge that > they might ha

Re: Debian Buster release to partially drop non-systemd support

Holger Levsen - 19.10.18, 12:02: > On Fri, Oct 19, 2018 at 11:35:54AM +0200, Martin Steigerwald wrote: > > A minority? Yes. But a sizable one. > > It doesn't matter how many people use it, if noone is willing to > maintain it. *If* people are maintaining it, it also doesnt

Re: Debian Buster release to partially drop non-systemd support

Martin Steigerwald - 19.10.18, 10:57: > That written, I estimate or guess that the people preferring to use > another initialization system than the initialization system in > Systemd are in the minority. Yet, this minority might be larger than > you think. Especially as popularity

Re: Debian Buster release to partially drop non-systemd support

dropping debian-hurd Bernd Zeimetz - 18.10.18, 22:07: > - the typical package maintainer won't test initscripts I am not typical then. > After using a lot of systemd now I will never go back to init scripts. > Systemd comes with a steep learning curve, but one you've stated > using its features

Re: Debian Buster release to partially drop non-systemd support

Michael Biebl - 16.10.18, 22:08: > Am 16.10.18 um 21:36 schrieb Adam Borowski: > > Systemd's algorithm for btrfs RAID is: > So your complaint is specific to btrfs RAID which afaik is still > considered unstable? Certain BTRFS RAID like RAID 1 and RAID 10 levels are considered stable by upstream

Re: Debian Buster release to partially drop non-systemd support

Matthew Vernon - 16.10.18, 13:27: > Ian Jackson writes: > > Also we are hampered by the lack of a safe space to communicate and > > coordinate. I looked at some of the technical work done in other > > distros to try to make desktoppy stuff continue to work well, and it > > generally seems sane.

Re: Debian Buster release to partially drop non-systemd support

KatolaZ - 16.10.18, 13:39: > On Tue, Oct 16, 2018 at 12:38:19PM +0200, Michael Biebl wrote: > > [cut] > > > What you say is obviously wrong, and you should know that if you > > follow devuan. > > > > Even the founder of Devuan regularly uses exactly the words Ansgar > > described. > > Chris

Re: Debian Buster release to partially drop non-systemd support

200, Martin Steigerwald wrote: > > Ansgar Burchardt - 16.10.18, 08:53: > > > If some people consistently call others a "cancer", accuse them of > > > "vandalizing" open source, spread obvious FUD and so on, then I > > > don't > > >

Re: Debian Buster release to partially drop non-systemd support

Ansgar Burchardt - 16.10.18, 08:53: > If some people consistently call others a "cancer", accuse them of > "vandalizing" open source, spread obvious FUD and so on, then I don't > think they would fit in well in Debian's culture where they would have > to accept that packages such as systemd exist.

Re: Debian Buster release to partially drop non-systemd support

Ian, cc'ing you to make you aware of this discussion, in case you aren't, and give you an opportunity to comment on your aim to adopt sysvinit package from some time ago. KatolaZ, Ian feel free to drop Cc's again, I won't be offended :) Alessio Treglia - 16.10.18, 07:31: > On Mon, Oct 15, 2018

Re: Debian Buster release to partially drop non-systemd support

Martin Steigerwald - 15.10.18, 17:56: > Anyway, I will make Devuan people aware of this discussion. Let's see > whether someone likes to cooperate. As Evilham also pointed out, Devuan people are aware of this discussion already: [devuan-dev] sysvinit in debian is under threat of being d

Re: Debian Buster release to partially drop non-systemd support

Ansgar Burchardt - 15.10.18, 16:03: > On Mon, 2018-10-15 at 14:20 +0100, Jonathan Dowland wrote: > > On Mon, Oct 15, 2018 at 06:56:50AM +0200, Petter Reinholdtsen wrote: > > > I believe Andreas Henriksson is right, the packages are going to > > > be > > > removed unless someone with time and

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

Sean Whitton - 08.09.18, 21:03: > My understanding is that there are quite deep social reasons for the > current policy (please note, though, that I was not involved in Debian > when this piece of policy was created; neither was I involved during > the nodejs TC decision). > > The current policy

Accepted fio 3.8-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Aug 2018 16:19:28 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 3.8-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald Changed-By: Martin Steigerwald Description: fio

Re: Should the weboob package stay in Debian?

Stephan Seitz - 26.07.18, 11:10: > On Do, Jul 26, 2018 at 09:32:34 +0200, Martin Steigerwald wrote: > >Adam Borowski - 26.07.18, 03:09: > >> I for one don't protest inclusion of the Bible in Debian, despite > >> that text having been the cause of 100M deaths, nor

Re: Should the weboob package stay in Debian?

Adam Borowski - 26.07.18, 03:09: > On Thu, Jul 26, 2018 at 12:55:50AM +0200, gregor herrmann wrote: > > On Wed, 25 Jul 2018 21:56:10 +0200, Adam Borowski wrote: > > > On Wed, Jul 25, 2018 at 12:18:53PM -0700, Steve Langasek wrote: > > > > It is covered. We explicitly list a number of things that

Re: Should the weboob package stay in Debian?

Adam Borowski - 25.07.18, 21:56: > On Wed, Jul 25, 2018 at 12:18:53PM -0700, Steve Langasek wrote: > > On Wed, Jul 25, 2018 at 07:05:33PM +0200, Marc Haber wrote: > > > Staying compatible with the rest of the world is not covered by > > > our > > > core principles? > > > > It is covered. We

Re: Should the weboob package stay in Debian?

No need to cc me. I am subscribed to the list. I proofread this message several times as it is important to me to make it clear as best I can. It may still have typos or syntax mistakes. Ian Jackson - 23.07.18, 20:43: > Martin Steigerwald writes ("Re: Should the weboob package stay in

Re: Should the weboob package stay in Debian?

Miriam Ruiz - 23.07.18, 12:10: > 2018-07-23 8:23 GMT+02:00 Martin Steigerwald : > > Ben Hutchings - 23.07.18, 02:34: > >> On Sun, 2018-07-22 at 23:34 +0200, Romain Bignon wrote: > >> > On 22/Jul - 13:14, Geoffrey Thomas wrote: > >> > > And, as far as

Re: Should the weboob package stay in Debian?

Ben Hutchings - 23.07.18, 02:34: > On Sun, 2018-07-22 at 23:34 +0200, Romain Bignon wrote: > > On 22/Jul - 13:14, Geoffrey Thomas wrote: > > > And, as far as I know, everyone who's replied on this thread > > > (myself > > > included) is a man - so I think we should be particularly careful > > >

Re: make compilation not so gray

Guus Sliepen - 25.05.18, 21:46: > On Fri, May 25, 2018 at 02:21:34PM +0200, Adam Borowski wrote: > > I propose to add a new flag: DEB_BUILD_OPTIONS=color. […] > That would be very helpful. > > Even more helpful would be to NOT display anything irrelevant. When a > package fails to build, I am

Accepted fio 3.6-4 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 May 2018 11:24:41 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 3.6-4 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@proact.de> Changed-By:

Accepted fio 3.6-3 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 15 May 2018 14:04:56 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 3.6-3 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@proact.de> Changed-By:

Accepted fio 3.6-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 15 May 2018 10:21:30 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 3.6-2 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@proact.de> Changed-By:

Accepted fio 3.6-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 09 May 2018 08:55:08 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 3.6-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@proact.de> Changed-By:

Re: RFC: Support for zstd in .deb packages?

Hi Guillem. I have no real opinion on this. Guillem Jover - 27.04.18, 07:02: […] > In 2016 Paul Wise mentioned the Zstandard compressor on IRC [Z], > and I briefly checked it out as a potential candidate for dpkg > (while also mentioning it to Julian Andres Klode who was considering > adding lz4

Re: problems in gjots2 and Debian

Hi Andrey. Andrey Rahmatullin - 18.04.18, 11:55: > On Wed, Apr 18, 2018 at 11:23:23AM +0200, Martin Steigerwald wrote: > > As just someone who mostly maintains one package (fio - flexible I/O > > tester) I can certainly understand how you feel about that Lucas > > remove

Re: problems in gjots2 and Debian

Dear Rolf. Rolf Leggewie - 18.04.18, 07:19: […] > @ALL, it seems like no matter what I say, no matter how I explain my > reasons, I cannot convince quite a number of people. So, I plan not > to waste my time on trying anymore. Steve is much better of getting > to the relevant points anyhow. I

Re: ed25519 keys and mentors.d.n

Ian Jackson - 09.04.18, 15:45: > I would be quite happy to rewrite all of my call sites to use a > different program or a different library or whatever. Unfortunately > the one project I'm aware of that sets out to compete with gnupg2 > (https://neopg.io/) doesn't look like it will provide what

Accepted fio 3.5-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 09 Apr 2018 13:45:59 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 3.5-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@proact.de> Changed-By:

Accepted fio 3.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 24 Oct 2017 09:47:45 +0200 Source: fio Binary: fio gfio Architecture: source Version: 3.1-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@proact.de> Changed-By: Martin Steig

Re: Alioth: the future of mailing lists

Alexander Wirt - 19.09.17, 10:17: > On Tue, 19 Sep 2017, Marc Haber wrote: > > On Mon, 18 Sep 2017 21:53:43 +0200, Alexander Wirt > > > > wrote: > > >On Mon, 18 Sep 2017, Dominic Hargreaves wrote: > > >> I have managed mailman installations for some time so I'm fairly > >

Re: Call for volunteers: FTP Team

Luca Filipozzi - 18.08.17, 13:57: > On Fri, Aug 18, 2017 at 03:54:55PM +0200, Bjørn Mork wrote: > > Abou Al Montacir writes: > > > On Fri, 2017-08-18 at 08:24 -0500, Matt Zagrabelny wrote: > > >> > If someone hypothetically joins, are they allowed to rename the FTP > > >>

Re: apt-get dist-upgrade uninstalled most of KDE

Martin Steigerwald - 16.08.17, 23:43: > There is no automatic way to undo the action. I suggest you install again > by using metapackages like > > - plasma-desktop > - kde-standard > - kde-full > > depending on the amount of packages you want to have installed. > &g

Re: apt-get dist-upgrade uninstalled most of KDE

Hello Marco. Please use a mailinglist for user support. This mailing list is for development topics. For Plasma/KDE related questions I suggest debian-kde mailinglist. Cc´d. Please drop Cc to debian-devel on your answer. nob...@gmail.com - 16.08.17, 12:56: > I just upgraded my system (Debian

Re: Bits from the 10th Debian Groupware Meeting

Hi. Christian Seiler - 03.08.17, 17:34: > On 08/03/2017 03:21 PM, Rainer Dorsch wrote: > > thank you for all the links. My main question was why it is not listed at > > all in the groupware wiki, you could easily list nextcloud/owncloud in > > the section "Groupware projects not currently

Re: Bits from the 10th Debian Groupware Meeting

Hello Rainer. Rainer Dorsch - 03.08.17, 13:12: > Hi Guido, > > just wondering, did you consider nextcloud as groupware? Owncloud has been in Debian… and its past maintainers gave up on maintaining it. For a part of the discussion see: Debian Bug report logs - #822681 RM: owncloud -- ROM;

wrong recipient, please ignore (was: Re: Eingangskorb:[…] Re: Accepted weresync…)

Martin Steigerwald - 20.07.17, 21:28: > Daniel Manila - 20.07.17, 19:00: > > Format: 1.8 > > Date: Fri, 30 Jun 2017 12:20:41 +0600 > > Source: weresync Sorry, this obviously shouldn´t have gone to debian-devel. -- Martin

Eingangskorb: Linux Storage blockbasiertes Backup, inkrementell, NDMP-like? Re: Accepted weresync 1.0.7-1 (source all) into unstable, unstable

Daniel Manila - 20.07.17, 19:00: > Format: 1.8 > Date: Fri, 30 Jun 2017 12:20:41 +0600 > Source: weresync > Binary: weresync weresync-doc > Architecture: source all > Version: 1.0.7-1 > Distribution: unstable > Urgency: low > Maintainer: Python Applications Packaging Team >

Naming of network devices (was: Re: Debian 9 in a VM with Proxmox 5 system)

Hola. Adam Borowski - 10.07.17, 18:22: > On Mon, Jul 10, 2017 at 03:47:14PM +0200, Guus Sliepen wrote: > > On Mon, Jul 10, 2017 at 01:57:08PM +0200, Rene Engelhard wrote: > > > eth0 will be kept on upgrades, but new installs get new interface names > > > (that is good, that removed

Re: What's a safe way to have extensions in chromium in Debian?

Am Montag, 10. April 2017, 01:58:29 CEST schrieb Andrey Rahmatullin: > On Sat, Apr 08, 2017 at 08:28:38AM +0200, Enrico Weigelt, metux IT consult wrote: > > > > > > could anyone please give me some insight, was the security problems > > are here exactly ? > > Extension auto-updating is

Accepted fio 2.16-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 23 Dec 2016 17:09:43 +0100 Source: fio Binary: fio gfio Architecture: source amd64 Version: 2.16-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@teamix.de> Changed-By:

Accepted fio 2.15-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 19 Dec 2016 16:02:52 +0100 Source: fio Binary: fio gfio Architecture: source amd64 Version: 2.15-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@teamix.de> Changed-By:

Accepted fio 2.10-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 24 May 2016 12:33:25 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 2.10-2 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@teamix.de> Changed-By:

Accepted fio 2.10-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 May 2016 16:28:16 +0200 Source: fio Binary: fio gfio Architecture: source amd64 Version: 2.10-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@teamix.de> Changed-By:

Accepted fio 2.6-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 24 Feb 2016 10:47:40 +0100 Source: fio Binary: fio gfio Architecture: source amd64 Version: 2.6-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@teamix.de> Changed-By:

Accepted fio 2.2.10-1 (source amd64) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Nov 2015 10:00:35 +0100 Source: fio Binary: fio gfio Architecture: source amd64 Version: 2.2.10-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald <martin.steigerw...@teamix.de> Changed-By:

Re: Technical committee acting in gross violation of the Debian constitution

Am Sonntag, 30. November 2014, 18:05:54 schrieb Neil Williams: On Sun, 30 Nov 2014 15:59:06 + Noel Torres env...@rolamasao.org wrote: […] Debian: If you want to help our users, you can contribute to debianfork, or you can improve your packages in Debian. But spreading your

Re: Technical committee acting in gross violation of the Debian constitution

Am Sonntag, 30. November 2014, 21:54:09 schrieb Josselin Mouette: Le dimanche 30 novembre 2014 à 19:59 +0100, Martin Steigerwald a écrit : You complain about people blaming Debian, or more exactly Debian technical committee and GR decisions, for their decision to leave. Yes, it is anyone´s

I am at least pausing my work on fio, fsmark, filebench and atop packaging

Hello! I am at least pausing my work on fio, fsmark, as well as unreleased filebench and atop 2.1 packaging work as I do not want to waste my energy with working in what I perceive as a hostile environment. I have been told to stop posting here and have even been moderated by a listmaster for

Re: splitting source packages

Am Donnerstag, 27. November 2014, 16:50:12 schrieb Neil Williams: On Thu, 27 Nov 2014 16:24:12 +0100 Matthias Urlichs matth...@urlichs.de wrote: Hi, Neil Williams: By having separate source packages, a stable API becomes mandatory. You're correct in that it is easier to keep an

Re: Technical committee acting in gross violation of the Debian constitution

Am Samstag, 29. November 2014, 01:32:22 schrieb Zbigniew Jędrzejewski-Szmek: On Thu, Nov 27, 2014 at 10:02:06PM +0100, Martin Steigerwald wrote: And well, I also wonder why systemd --user functionality is in the *same* binary than the PID 1 stuff… but well… I brought this upstream

Re: splitting source packages

Am Samstag, 29. November 2014, 10:49:34 schrieb Martin Steigerwald: Am Donnerstag, 27. November 2014, 16:50:12 schrieb Neil Williams: On Thu, 27 Nov 2014 16:24:12 +0100 Matthias Urlichs matth...@urlichs.de wrote: Hi, Neil Williams: By having separate source packages, a stable

Re: Technical committee acting in gross violation of the Debian constitution

Am Samstag, 29. November 2014, 20:30:07 schrieb Svante Signell: On Sat, 2014-11-29 at 19:12 +0100, Zbigniew Jędrzejewski-Szmek wrote: On Sat, Nov 29, 2014 at 11:51:56AM +0100, Martin Steigerwald wrote: Am Samstag, 29. November 2014, 01:32:22 schrieb Zbigniew Jędrzejewski- Szmek: New dbus

Re: Technical committee acting in gross violation of the Debian constitution

Am Freitag, 28. November 2014, 09:28:39 schrieb Matthias Urlichs: Hi, Martin Steigerwald: Am Donnerstag, 27. November 2014, 22:30:15 schrieb Vincent Bernat: ❦ 27 novembre 2014 22:02 +0100, Martin Steigerwald mar...@lichtvoll.de : And well, I also wonder why systemd --user

Re: Technical committee acting in gross violation of the Debian constitution

Am Donnerstag, 27. November 2014, 01:19:14 schrieb Josselin Mouette: Le mercredi 26 novembre 2014 à 16:05 -0800, Russ Allbery a écrit : And many of us who actually *are* Debian server administrators have said repeatedly that your gut is wrong, in the innumerable versions of this

Re: Technical committee acting in gross violation of the Debian constitution

Am Donnerstag, 27. November 2014, 11:53:18 schrieb Matthias Urlichs: Hi, Hi Matthias, Martin Steigerwald: Desktops (not only GNOME) use a very tiny bit of systemd, interfaces that could be provided elsewhere. The real purpose of systemd is to provide a modern init system. I still

Re: Technical committee acting in gross violation of the Debian constitution

Am Donnerstag, 27. November 2014, 14:28:01 schrieb Matthias Urlichs: Martin Steigerwald: But I think for most of the people that dislike systemd this is the main concern: systemd is a lot of system building blocks in *one* repository and *one* debian package and while they may

Re: Technical committee acting in gross violation of the Debian constitution

Am Donnerstag, 27. November 2014, 21:29:40 schrieb Marc Haber: On Thu, 27 Nov 2014 01:19:14 +0100, Josselin Mouette j...@debian.org wrote: Desktops (not only GNOME) use a very tiny bit of systemd, interfaces that could be provided elsewhere. The real purpose of systemd is to provide a

Re: Technical committee acting in gross violation of the Debian constitution

Am Donnerstag, 27. November 2014, 22:30:15 schrieb Vincent Bernat: ❦ 27 novembre 2014 22:02 +0100, Martin Steigerwald mar...@lichtvoll.de : And well, I also wonder why systemd --user functionality is in the *same* binary than the PID 1 stuff… but well… Wild guess: because it manages

Re: init system policy

Am Dienstag, 18. November 2014, 23:31:53 schrieb Steve Langasek: On Tue, Nov 18, 2014 at 07:47:59PM +0100, Matthias Urlichs wrote: Your specific package may well have different and non-general requirements, in which case ExecStart=sudo -u $USER_MINIDLNA -g GROUP_MINIDLNA

Re: so long and thanks for all the fish

Joey, Am Freitag, 7. November 2014, 17:04:10 schrieb Joey Hess: It's become abundantly clear that this is no longer the project I originally joined in 1996. We've made some good things, and I wish everyone well, but I'm out. I am sad from reading this. I do not know you as a person, except

Re: so long and thanks for all the fish

Am Samstag, 8. November 2014, 10:19:02 schrieb Martin Steigerwald: Joey, Am Freitag, 7. November 2014, 17:04:10 schrieb Joey Hess: It's become abundantly clear that this is no longer the project I originally joined in 1996. We've made some good things, and I wish everyone well, but I'm

Re: Hurra for an efficient ftpmaster team!

Am Donnerstag, 23. Oktober 2014, 11:59:14 schrieb Thibaut Paumard: Le 22/10/2014 19:04, Jonas Smedegaard a écrit : Hurra for the ftmaster team! +1 \o/ and a standing ovation So far I just had a few packages sponsored into Debian, but I just see it on the daily apt-get dist-upgrade on my

Accepted fio 2.1.11-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Sep 2014 15:37:28 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 2.1.11-2 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Re: systemd now appears to be only possible init system in testing

Am Dienstag, 22. Juli 2014, 22:54:55 schrieb Julian Gilbey: For me, this is a killer, as I still do not know how to solve the problem I asked a while back on debian-user (https://lists.debian.org/debian-user/2014/04/msg01286.html): in summary, I need to unlock an encrypted filesystem during

  1   2   >