Built a package for fio

/ Hendrik feel free to use or disregard as much of my efforts as you like ;-). I know I didn't ask before, but I would have done it anyway for gaining some experience and now that I have done it I can as well share my results. Thus I wouldn't upload it even if I were a DD. Ciao, -- Martin

Bug#655222: ITP: filebench -- ITP: filebench - file system and storage benchmark with flexible workload specification

Package: wnpp Severity: wishlist Owner: Martin Steigerwald m...@teamix.de * Package name: filebench Version : 1.4.9.1 Upstream Author : Vasily Tarasov (v...@fsl.cs.sunysb.edu) and others * URL : http://sourceforge.net/projects/filebench/ * License : CDDL 1.0

Bug#655224: ITP: fsmark -- ITP: fs_mark - benchmark for simulating synchronous write workloads

Package: wnpp Severity: wishlist Owner: Martin Steigerwald m...@teamix.de * Package name: fsmark Version : 3.3 Upstream Author : Ric Wheeler r...@emc.com * URL : http://sourceforge.net/projects/fsmark/ * License : GPL v2 or later Programming Lang: C

Re: Proposal: switch init system to systemd or upstart

Am Freitag, 25. Oktober 2013, 14:29:54 schrieb Marco d'Itri: It is more and more obvious that modern software needs an event-based init system. Pros: - more features - stable support for advanced boot/SAN environments - being more similar to one of the other relevant distributions (RHEL or

Re: Proposal: switch default desktop to xfce

Am Freitag, 25. Oktober 2013, 17:32:30 schrieb Sune Vuorela: On 2013-10-25, Neil Williams codeh...@debian.org wrote: Other desktop environments have similar features without requiring a change of init system. It was a choice by GNOME upstream and a choice Other desktop environments either

Re: systemd-fsck?

Am Freitag, 9. Mai 2014, 20:30:22 schrieb Michael Biebl: Am 09.05.2014 19:56, schrieb Steve Langasek: I don't think systemd integration is in a state today that this is ready to become the default. What are you missing? Suitable explaination and reaction to bug reports like:

Re: systemd-fsck?

[I kept your Cc, I don´t need to be Cc´d tough as I am subscribed to the list.) Am Samstag, 10. Mai 2014, 21:21:30 schrieb Norbert Preining: Hi Martin, hi all, being told Go away just doesn´t match the responsibility for dealing with issues with something that is a default for all users

Re: systemd-fsck?

Am Samstag, 10. Mai 2014, 15:36:26 schrieben Sie: Martin Steigerwald wrote: Am Freitag, 9. Mai 2014, 20:30:22 schrieb Michael Biebl: Am 09.05.2014 19:56, schrieb Steve Langasek: I don't think systemd integration is in a state today that this is ready to become the default

Re: systemd-fsck?

Am Samstag, 10. Mai 2014, 18:00:02 schrieb Laurent Bigonville: Le Sat, 10 May 2014 16:00:39 +0200, Martin Steigerwald mar...@lichtvoll.de a écrit : [...] Thats exactly the kind of reaction I meant: Frankly, I just *don´t* care where it is fixed. If its in dirmngr, fine

Re: systemd-fsck?

Am Samstag, 10. Mai 2014, 19:13:01 schrieb Matthias Urlichs: Hi, Martin Steigerwald: Yet: I do think its about high time systemd developers and packagers adopt an attitude of never break userspace like the kernel developers do. I beg to differ. At least in this case. su does a bunch

Re: systemd-fsck?

Am Sonntag, 11. Mai 2014, 08:57:29 schrieb Marc Haber: IMVHO opening a PAM session in an initscript is a bad idea from day one, as you don't know which modules are being called, as it can create bogus audit trails or cause other subtile issues. Just curious as the maintainer of another

Re: systemd-fsck?

Am Samstag, 10. Mai 2014, 21:36:42 schrieb Laurent Bigonville: Le Sat, 10 May 2014 19:13:01 +0200, Matthias Urlichs matth...@urlichs.de a écrit : Hi, [...] Telling Go away, the bug is elsewhere is just not an approbiate reaction for developers of a low level system component.

Re: systemd-fsck?

Am Samstag, 10. Mai 2014, 15:38:24 schrieb Steve Langasek: On Sat, May 10, 2014 at 04:00:39PM +0200, Martin Steigerwald wrote: The root cause of this bug is in the initscript of dirmngr that us using su instead of start-stop-daemon. su is starting a PAM session which then call

Re: systemd-fsck?

Am Sonntag, 11. Mai 2014, 00:55:43 schrieb Kevin Chadwick: previously on this list Steve Langasek contributed: Using systemd breaks something that worked for probably a decade or longer before however long that su is in that init script. So on what account do you call calling su

Re: systemd-fsck?

Am Sonntag, 11. Mai 2014, 09:13:09 schrieb Marc Haber: On Sat, 10 May 2014 16:27:00 +0200, Bas Wijnen wij...@debian.org wrote: This is the part you should _NEVER_ do. It is YOUR responsibitiliy, as a maintainer (you are the maintainer, right?), to make sure that a bug that is reported in

Re: systemd-fsck?

Am Sonntag, 11. Mai 2014, 12:53:39 schrieb Marc Haber: On Sun, 11 May 2014 10:04:15 +0200, Cyril Brulebois k...@debian.org wrote: Marc Haber mh+debian-de...@zugschlus.de (2014-05-11): Just curious as the maintainer of another package using su in an init script since 2001, how am I

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

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

Am Freitag, 25. Juli 2014, 10:23:02 schrieb Steve Langasek: On Fri, Jul 25, 2014 at 06:56:06PM +0200, Tollef Fog Heen wrote: ]] Martin Steigerwald Sure I can go through setting up chroot for that, yet I really think if my work requires changes in other packages and the recent

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

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: 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: 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: 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: 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 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

Accepted fio 1.36-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Feb 2010 15:17:22 +0100 Source: fio Binary: fio Architecture: source amd64 Version: 1.36-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 1.38-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Apr 2010 18:23:14 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 1.38-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 1.50-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Feb 2011 11:57:56 +0100 Source: fio Binary: fio Architecture: source amd64 Version: 1.50-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 1.57-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 03 Aug 2011 14:05:33 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 1.57-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 1.59-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 10 Oct 2011 17:19:00 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 1.59-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 1.32-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 13 Aug 2009 08:22:40 +0200 Source: fio Binary: fio Architecture: source i386 Version: 1.32-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 1.33.1-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 10 Sep 2009 11:37:00 +0200 Source: fio Binary: fio Architecture: source i386 Version: 1.33.1-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fsmark 3.3-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 26 Apr 2012 16:53:00 +0200 Source: fsmark Binary: fsmark Architecture: source amd64 Version: 3.3-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 2.0.8-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Jun 2012 09:28:22 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 2.0.8-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 2.0.8-2 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 27 Jun 2012 09:25:49 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 2.0.8-2 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 2.1.3-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Oct 2013 11:53:41 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 2.1.3-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fsmark 3.3-2 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 08 Oct 2013 10:03:22 +0200 Source: fsmark Binary: fsmark Architecture: source amd64 Version: 3.3-2 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 2.1.1-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 05 Aug 2013 16:47:21 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 2.1.1-1 Distribution: unstable Urgency: low Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

Accepted fio 2.1.11-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 21 Jul 2014 15:53:36 +0200 Source: fio Binary: fio Architecture: source amd64 Version: 2.1.11-1 Distribution: unstable Urgency: medium Maintainer: Martin Steigerwald m...@teamix.de Changed-By: Martin Steigerwald m...@teamix.de

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

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:

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.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.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.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.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:

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

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: 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

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

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 >

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

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;

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: 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: 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 > >

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

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-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-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:

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.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: 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?

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?

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

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?

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?

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?

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: 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.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:

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

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: 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

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

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

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

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: 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

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

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

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

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

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

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

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?

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

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

  1   2   >