Accepted ppx-here 0.16.0-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Sep 2023 06:18:09 +0200 Source: ppx-here Architecture: source Version: 0.16.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Changes: ppx-here (0.16.0-4

Accepted haskell-here 1.2.14-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Sep 2023 19:41:27 -0400 Source: haskell-here Architecture: source Version: 1.2.14-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Clint Adams Changes: haskell-here (1.2.14-1

Accepted ppx-here 0.16.0-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Aug 2023 07:57:01 +0200 Source: ppx-here Architecture: source Version: 0.16.0-3 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Changes: ppx-here (0.16.0-3

Accepted ppx-here 0.16.0-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Jul 2023 11:07:52 +0200 Source: ppx-here Architecture: source Version: 0.16.0-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Changes: ppx-here (0.16.0-2) unstable

Accepted ppx-here 0.16.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Jul 2023 11:24:00 +0200 Source: ppx-here Architecture: source Version: 0.16.0-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Changes: ppx-here (0.16.0-1) unstable

Accepted ppx-here 0.15.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 01 Feb 2023 12:52:46 +0100 Source: ppx-here Architecture: source Version: 0.15.0-1 Distribution: unstable Urgency: low Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Changes: ppx-here (0.15.0-1) unstable

Accepted haskell-here 1.2.13-6 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 Jul 2022 09:31:56 +0300 Source: haskell-here Architecture: source Version: 1.2.13-6 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Changes: haskell-here (1.2.13-6

Accepted r-cran-here 1.0.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 06 Sep 2021 13:19:15 +0200 Source: r-cran-here Architecture: source Version: 1.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Changes: r-cran-here (1.0.1-2

Accepted r-cran-here 1.0.1-1 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 May 2021 09:04:29 +0200 Source: r-cran-here Binary: r-cran-here Architecture: source all Version: 1.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille

Accepted ppx-here 0.14.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Jul 2020 10:58:21 +0200 Source: ppx-here Architecture: source Version: 0.14.0-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Changes: ppx-here (0.14.0-1

Accepted haskell-here 1.2.13-5 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 14 Jun 2020 13:39:57 +0300 Source: haskell-here Architecture: source Version: 1.2.13-5 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Changes: haskell-here (1.2.13-5

Accepted ppx-here 0.13.0-1 (source amd64) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 13 Feb 2020 05:01:46 +0100 Source: ppx-here Binary: libppx-here-ocaml libppx-here-ocaml-dbgsym libppx-here-ocaml-dev libppx-here-ocaml-dev-dbgsym Architecture: source amd64 Version: 0.13.0-1 Distribution: unstable Urgency

Bug#951240: ITP: ppx-here -- ppx rewriter that defines an extension node whose value is its source position

Package: wnpp Severity: wishlist Owner: Stéphane Glondu * Package name: ppx-here Version : 0.13.0 Upstream Author : Jane Street Group, LLC * URL : https://github.com/janestreet/ppx_here * License : MIT Programming Lang: OCaml Description : extension

Accepted haskell-here 1.2.13-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Oct 2018 12:06:12 +0300 Source: haskell-here Binary: libghc-here-dev libghc-here-prof libghc-here-doc Architecture: source Version: 1.2.13-4 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed

Accepted haskell-here 1.2.13-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 01 Oct 2018 13:33:27 +0300 Source: haskell-here Binary: libghc-here-dev libghc-here-prof libghc-here-doc Architecture: source Version: 1.2.13-3 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed

Accepted haskell-here 1.2.13-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 30 Sep 2018 21:10:51 +0300 Source: haskell-here Binary: libghc-here-dev libghc-here-prof libghc-here-doc Architecture: source Version: 1.2.13-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed

Re: When pkg-foo is not at all involved here

t, as the control@ output is the only one of the mails that they will have received. (Ideally debbugs would do so itself, but it doesn't, and making our colleagues' lives easier here is trivial.) Regards, Adam

When pkg-foo is not at all involved here

ertainly not, as network-manager-gnome is not at all involved here. > Yeah, that is where the pain is, the spot that needs improvement. I think we have all been there: Encounters with a software bug, feeling the need to report it, but not knowning _how and where_ to report. We shall

Accepted haskell-here 1.2.13-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 Apr 2018 16:06:34 -0400 Source: haskell-here Binary: libghc-here-dev libghc-here-prof libghc-here-doc Architecture: source Version: 1.2.13-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group <

Accepted haskell-here 1.2.12-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jan 2018 15:03:42 -0500 Source: haskell-here Binary: libghc-here-dev libghc-here-prof libghc-here-doc Architecture: source Version: 1.2.12-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group <

Accepted haskell-here 1.2.11-1 (source amd64 all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 27 Oct 2017 16:59:06 +0300 Source: haskell-here Binary: libghc-here-dev libghc-here-prof libghc-here-doc Architecture: source amd64 all Version: 1.2.11-1 Distribution: unstable Urgency: low Maintainer: Debian Haskell Group

Bug#879834: ITP: haskell-here -- Here documents and interpolated strings via quasiquotation

Package: wnpp Severity: wishlist Owner: Ilias Tsitsimpis <ilias...@debian.org> * Package name: haskell-here Version : 1.2.11 Upstream Author : Taylor M. Hedberg <t...@tmh.cc> * URL : https://hackage.haskell.org/package/here * License :

Bug#855683: ITP: golang-github-makenowjust-heredoc -- Convert strings to here documents in Go

itsune * URL : https://github.com/MakeNowJust/heredoc * License : Expat Programming Lang: Go Description : Convert strings to here documents in Go Here documents allow text files or other data to be embedded in source files. The heredoc library implements the whit

Bug#842162: ITP: anything-sync-daemon -- Anything-sync-daemon (asd) is a tiny pseudo-daemon designed to manage user specified directories referred to as sync targets from here on out, in tmpfs and to

: Expat Programming Lang: Bash Description : Sync user specified directories into RAM Anything-sync-daemon (asd) is a tiny pseudo-daemon designed to manage user specified directories referred to as sync targets from here on out, in tmpfs and to periodically sync them back to the physical d

Re: Is the reason for closing the bug 837459 appropriate here?

Quoting Henrique de Moraes Holschuh <h...@debian.org>: On Wed, 21 Sep 2016, john.k...@vfemail.net wrote: Is the reason for closing the bug 837459 appropriate here? The bug is still here and no backported version. I believe it was appropriately closed, yes. #837459 is not a r

Re: Is the reason for closing the bug 837459 appropriate here?

On Wed, 21 Sep 2016, Henrique de Moraes Holschuh wrote: > for that backport, and refering to bug #836459... Typo. Make that bug #837459... -- Henrique Holschuh

Re: Is the reason for closing the bug 837459 appropriate here?

On Wed, 21 Sep 2016, john.k...@vfemail.net wrote: > Is the reason for closing the bug 837459 appropriate here? The bug is still > here and no backported version. I believe it was appropriately closed, yes. #837459 is not a request for a backport. Instead, it is a bug about som

Re: Is the reason for closing the bug 837459 appropriate here?

On Wed, 21 Sep 2016, john.k...@vfemail.net wrote: > Is the reason for closing the bug 837459 appropriate here? The bug is still > here and no backported version. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837459 This bug is fixed in unstable and testing, but is curr

Is the reason for closing the bug 837459 appropriate here?

Hello, Is the reason for closing the bug 837459 appropriate here? The bug is still here and no backported version. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837459 Best wishes, John - ONLY AT VFEmail! - Use our Metadata Mitigator

Re: Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list!

;> 2015-12-10 13:42 GMT-02:00 françai s <romaper...@gmail.com>: >> >> > Administrators and moderators of ubuntu-devel list, please erase all the >> > messages that I not should have posted here in debian-devel list. >> > >> > I ask this because I pr

Re: Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list!

l list, please erase all the > messages that I not should have posted here in debian-devel list. > > I ask this because I probably be in future a good programmer famous and I > do not want to talk about the topics that I should not have posted here in > debian-devel list. > > I decided preven

Re: Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list!

; > > Administrators and moderators of ubuntu-devel list, please erase all the > > messages that I not should have posted here in debian-devel list. > > > > I ask this because I probably be in future a good programmer famous and I > > do not want to talk about the

Re: Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list!

can simply ignore it. >> >> ¹ http://mail.9fans.net/private/9fans/2015-December/034480.html > Err sorry I posted link to private list archives. Here is the link for public list archive. ¹ Sorry for the noise :-) ¹ http://marc.info/?l=9fans=144975913529020=2

Re: Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list!

Vasudev Kamath writes: > > I think the original message was a troll message :-). I saw the same message > with similar > subject on a different list to ¹. So I think you can simply ignore it. > > ¹ http://mail.9fans.net/private/9fans/2015-December/034480.html Err sorry I

Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list!

Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list. I ask this because I probably be in future a good programmer famous and I do not want to talk about the topics that I should not have posted here in debian

S-D is like a cold vastness. (Song included here)

https://www.youtube.com/watch?v=tRvf9LauZIMlist=UUpfKI2v7BTPBrx6HWvEx1Lw [ Instruments: Analogue Synth: MicroBRUTE Software Synth Organ: ZynAddSubFX ] Synth and organ in the cold infinite vastness. As if abandoned. Seeing bright lights, but feeling no warmth. Kind of like what old-guard

Re: GR - collecting proposals (was Re: systemd is here to stay, get over it now)

t...@debian.org wrote: Steve McIntyre wrote: with this constant bickering and sniping. If you must do it, start the GR and see how that goes. I even offer to second it just to help get Can you help formulate? I do not feel my English skills are up to that. I'm sorry, I don't really have time to

Re: GR - collecting proposals (was Re: systemd is here to stay, get over it now)

On Fri, Jul 4, 2014 at 3:28 PM, Thorsten Glaser t...@debian.org wrote: - existing installations of older (pre-jessie) Debian may be upgraded to our new standard init system systemd, but only after the user has been suitably warned, e.g. via a debconf propmpt at priority

Re: GR - collecting proposals (was Re: systemd is here to stay, get over it now)

On Jul 09, Alessio Treglia ales...@debian.org wrote: I think that it would be valuable for our users to keep the non-default init system working on Jessie for those who do neither intend nor need to switch to systemd. I suggest less thinking and more coding then, because an updated

Re: GR - collecting proposals (was Re: systemd is here to stay, get over it now)

Quoting Marco d'Itri (m...@linux.it): On Jul 09, Alessio Treglia ales...@debian.org wrote: I think that it would be valuable for our users to keep the non-default init system working on Jessie for those who do neither intend nor need to switch to systemd. I suggest less thinking and more

Re: systemd is here to stay, get over it now

Norbert Preining wrote: On Mon, 07 Jul 2014, Josselin Mouette wrote: If they don’t need any of the systemd features, I guess they don’t need any of its reverse dependencies either. Rubbish. I want network-manager, but I don't want systemd. I don’t, but I want most KDE packages, so I

Re: systemd is here to stay, get over it now

Le mardi 08 juillet 2014 à 08:13 +0900, Norbert Preining a écrit : On Mon, 07 Jul 2014, Josselin Mouette wrote: If they don’t need any of the systemd features, I guess they don’t need any of its reverse dependencies either. Rubbish. I want network-manager, but I don't want systemd. NM

Re: systemd is here to stay, get over it now

Le vendredi 04 juillet 2014 à 15:09 +0200, Stephan Seitz a écrit : But if they don’t want the systemd features why should they write software to replace systemd? If they don’t need any of the systemd features, I guess they don’t need any of its reverse dependencies either. So why do they

Re: systemd is here to stay, get over it now

On Mon, 07 Jul 2014, Josselin Mouette wrote: If they don’t need any of the systemd features, I guess they don’t need any of its reverse dependencies either. Rubbish. I want network-manager, but I don't want systemd. NM was working long time without systemd. Don't spread wrong information.

Re: GR - collecting proposals (was Re: systemd is here to stay, get over it now)

On 07/04/2014 10:28 PM, Thorsten Glaser wrote: 4) all init systems currently in Debian are supported in jessie; We don't need a GR to support this option. Of course, all init systems are supported, to the best of our efforts, and I don't see why someone would refuse a patch. I haven't seen such

Re: systemd is here to stay, get over it now

* Juliusz Chroboczek j...@pps.univ-paris-diderot.fr [140704 23:00]: (I did find his comment funny -- actually, I find the CoC ifself pretty funny --, but I realise that this is an international mailing list and that Austrian-Japanese humour is not necessarily obvious to everyone.) I'd suggest

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

The Wanderer dijo [Thu, Jul 03, 2014 at 11:18:12PM -0400]: It must work without systemd well enough to be able to cleanly reboot the system from the GUI, after upgrading. Anything beyond that is nice-to-have, but definitely NOT required. I, for one, would be highly displeased if a

Re: systemd is here to stay, get over it now

me: (I did find his comment funny -- actually, I find the CoC ifself pretty funny --, but I realise that this is an international mailing list and that Austrian-Japanese humour is not necessarily obvious to everyone.) Tollef Fog Heen: Humour [...] does not work very well on large lists.

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

The Wanderer wande...@fastmail.fm writes: ... particularly because I use rather fewer things than many other people, and don't use most fancy GUI elements. (For example, I don't have a graphical power button at all; I shut down by exiting my window manager, logging out of the console where I

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

On Thu, Jul 3, 2014, at 16:59, Thorsten Glaser wrote: Besides, it’s not that the TC made a decision. Rather, the TC was split, and the chairman threw in his weight. This is absolutely not what I’d call a project(!) decision. No! The TC has made the decision with full adherence to Debian

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

not been any challenge that met the form and other requirements… and I am at a bit of loss at what to do here. Besides, it’s not that the TC made a decision. Rather, the TC was split, and the chairman threw in his weight. Sorry, but this is plain wrong (and you know it); the TC followed its

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

In other news for Thu, Jul 03, 2014 at 04:59:25PM +0200, Thorsten Glaser has been seen typing: No, there just has not been any challenge that met the form and other requirements… and I am at a bit of loss at what to do here. Besides, it’s not that the TC made a decision. Rather, the TC

Re: systemd is here to stay, get over it now

OdyX wrote: all means, go for it. That said, as far as I remember, the latest GR proposal [4] on this subject failed to gather the mandatory K seconds though. For me, this indicates that not even K=5 DDs were interested in I was not even aware of that proposal. This may also indicate lack of,

Re: systemd is here to stay, get over it now

The problem is that some people bitch endlessly abut how evil systemd is _instead_of_ producing software (not just patches) to replace what systemd offers. Abstracting away from your somewhat offensive choice of language, that's a good point. As far as I'm aware, the only major distribution

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/04/2014 04:52 AM, Philip Hands wrote: The Wanderer wande...@fastmail.fm writes: ... particularly because I use rather fewer things than many other people, and don't use most fancy GUI elements. (For example, I don't have a graphical

Re: systemd is here to stay, get over it now

Hi, Thorsten Glaser: systemd is a backdoor in that, like the availability of Steam games for DDs, it has a chance to hinder the progress of all projects done in the spare time of the people affected. Yeah. It has a chance. It also has a chance to give people a big chunk of spare time back,

Re: systemd is here to stay, get over it now

Juliusz Chroboczek wrote: The problem is that some people bitch endlessly abut how evil systemd is _instead_of_ producing software (not just patches) to replace what systemd offers. Abstracting away from your somewhat offensive choice of language, that's a good point. As far as I'm aware, the

Re: systemd is here to stay, get over it now

Dominik George dixit: systemd, in its nature as an init system, starts what you tell it to start. There is nothing that can prevent it from starting openntpd if you want that. If you through a service file at it, or even an LSB init script, then systemd has no choice but to start it. No, this is

Re: systemd is here to stay, get over it now

Hi Thorsten, while I tend to basically acknowledge your points here, there is still one thing you obviously did not get until now, if I followed along correctly. For example, systemd has support for its own (S)NTP client, but also supports xntpd (rudely leaving OpenNTPD out already). The commit

Re: systemd is here to stay, get over it now

On Thu, Jul 03, 2014 at 08:40:59PM +0200, Matthias Urlichs wrote: The problem is that some people bitch endlessly abut how evil systemd is _instead_of_ producing software (not just patches) to replace what systemd offers. But if they don’t want the systemd features why should they write

Re: systemd is here to stay, get over it now

On Fri, 04 Jul 2014, Matthias Urlichs wrote: Then shut up and help with the work required to get there, Please stop this inpoliteness, or I request a ban on all mailing lists due to permanent breaking of Code of Conduct. (Long live the CoC - I am *so* happy to have it!! - hope someone got

Re: systemd is here to stay, get over it now

Thorsten Glaser wrote: You know, backdoors are not only code vulnerabilities. systemd is a backdoor in that, like the availability of Steam games for DDs, it has a chance to hinder the progress of all projects done in the spare time of the people affected. Thorsten, you're too late. The

Re: systemd is here to stay, get over it now

, I do not wish to discuss this here - there are more suitable places/threads.) systemd is a backdoor in that, by means of vendor lock-in Which vendor are you talking about, exactly? vendor lock-in is an atomic expression, meaning the mechanism to have one thing from vendor X depend on one other

Re: systemd is here to stay, get over it now

Hi, Norbert Preining: Then shut up and help with the work required to get there, Please stop this inpoliteness, or I request a ban on all mailing lists due to permanent breaking of Code of Conduct. *what* Seriously?!? One of us seems to harbor a severe misconception or two about what kind

GR - collecting proposals (was Re: systemd is here to stay, get over it now)

Steve McIntyre wrote: with this constant bickering and sniping. If you must do it, start the GR and see how that goes. I even offer to second it just to help get Can you help formulate? I do not feel my English skills are up to that. Also, what options do we need? 1) systemd is the only init

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote: So, let me get this straight: You're saying that if, having decided to postpone rebooting after an upgrade where any reasonable person would expect to reboot This is Debian, not Windows or Red Hat, forced reboots are not

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

On Fri, Jul 4, 2014, at 16:42, Adam Borowski wrote: On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote: So, let me get this straight: You're saying that if, having decided to postpone rebooting after an upgrade where any reasonable person would expect to reboot This is

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/04/2014 10:42 AM, Adam Borowski wrote: On Fri, Jul 04, 2014 at 09:52:07AM +0100, Philip Hands wrote: So, let me get this straight: You're saying that if, having decided to postpone rebooting after an upgrade where any reasonable

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

, that's not the problem. The problem is that along with systemd we're changing a lot of the supporting infrastructure (we here is Upstream, for the most part). Keeping old low-level interfaces around just to avoid logging out or rebooting may or may not be something we can do easily. While I'll

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

this is going. systemd and its components can re-exec themselves, that's not the problem. The problem is that along with systemd we're changing a lot of the supporting infrastructure (we here is Upstream, for the most part). Upstream of what? Keeping old low-level interfaces around just to avoid

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

on a repeated basis, I don't like where this is going. systemd and its components can re-exec themselves, that's not the problem. The problem is that along with systemd we're changing a lot of the supporting infrastructure (we here is Upstream, for the most part). Keeping old low-level interfaces

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

On Jul 04, The Wanderer wande...@fastmail.fm wrote: This part is precisely what I'm objecting to. I don't consider being expected to reboot *in order to maintain existing functionality* after an upgrade to be reasonable. Tough luck for you then, I fear that this is a perception issue. At the

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

* The Wanderer wande...@fastmail.fm, 2014-07-04, 12:00: Zurg (Jessie+1), Has that name actually been formalized in any way? No. But no worries, if RT chooses a different name, we'll have a GR to override them. :-P -- Jakub Wilk -- To UNSUBSCRIBE, email to

Re: systemd is here to stay, get over it now

Matthias, On Fri, Jul 04, 2014 at 04:02:38PM +0200, Matthias Urlichs wrote: Norbert Preining: Then shut up and help with the work required to get there, Please stop this inpoliteness, or I request a ban on all mailing lists due to permanent breaking of Code of Conduct. *what*

Re: systemd is here to stay, get over it now

While I have no interest in joining Norbert in calling for your ban, Having had the pleasure to meet Norbert in person, I have no doubt that he was joking when appealing to the CoC. (I did find his comment funny -- actually, I find the CoC ifself pretty funny --, but I realise that this is an

Re: systemd is here to stay, get over it now

read. Humour, except when accompanied with explicit tags of HERE BE HUMOUR does not work very well on large lists. I have good hope that the systemd maintainers will take this minority of users into account in their further development. I (and I believe I speak for all the systemd maintainers

Re: sysvinit is still here, and here to stay for jessie

Matthias Urlichs wrote: For Zurg (Jessie+1), we're likely to switch to Wayland. How do you plan to We're *what*? (Says someone who uses X11 forwarding, VNC in, VNC out, and all that on an almost-, if not daily, basis.) OT: prevent-systemd-*_9_all.deb are in my repo. Wookey, feel free to

Re: systemd is here to stay, get over it now

I have yet to find mr Preining funny in any of his mails sent to any of the lists I read. Humour, except when accompanied with explicit tags of HERE BE HUMOUR does not work very well on large lists. Well, because I don't write WARNING HUMOUR COMING and then some people don't get it bad

Re: systemd is here to stay, get over it now

Tollef Fog Heen tfh...@err.no wrote: I [...] will try to avoid breaking stuff I expect no less from a Debian Developer. but it's also a use case we don't hit, so breakage there is less likely to be seen by us. We'll do our best to fix it when reported, of course. That is good to hear. It

Re: systemd is here to stay, get over it now

Hi, Steve Langasek: While I have no interest in joining Norbert in calling for your ban, I would like to ask you to consider taking a step back from this thread, and evaluating whether such messages are actually contributing to bringing these discussions to a conclusion. Thanks for the

Re: systemd is here to stay, get over it now

Juliusz Chroboczek j...@pps.univ-paris-diderot.fr writes: I'll remind you that this thread started with systemd breaking my system, and a systemd maintainer summarily closing my bug report. Not once, but twice. Because the bug was already fixed in a newer version of systemd. While we're

Re: systemd is here to stay, get over it now

also sprach Stephan Seitz stse+deb...@fsing.rootsland.net [2014-07-04 15:09 +0200]: But if they don’t want the systemd features why should they write software to replace systemd? Because there are better ways to implement it, including more granular approaches and less of a desktop focus. And

systemd is here to stay, get over it now (was: Re: Pinning vs. conflicting)

desktop environments (fact which is rightfully reflected in our dependencies tree). Many of the interfaces of systemd are here to stay and will make their way through our stack (like it or not); fact is they already made it quite far in at least Gnome and KDE. As developers of Debian (which this list

sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

a decision which stayed unchallenged (so far), I've now come to think that No, there just has not been any challenge that met the form and other requirements… and I am at a bit of loss at what to do here. Besides, it’s not that the TC made a decision. Rather, the TC was split, and the chairman threw

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

Hi, Thorsten Glaser: A lot of Debian systems even run without dbus! Yeah. So? systemd doesn't force you to run a dbus daemon. No, there just has not been any challenge that met the form and other requirements… and I am at a bit of loss at what to do here. You get to do the same thing

Re: systemd is here to stay, get over it now (was: Re: Pinning vs. conflicting)

Didier, Hello. The proper solution is to stop trying to hide ourselves from to the fact that some sort of systemd interfaces have been made unavoidable in modern desktop environments (fact which is rightfully reflected in our dependencies tree). Can we get over this now and start making

Re: systemd is here to stay, get over it now

Alexander Pushkin alex904...@mail.ru writes: For some of us there will never be an awesome Debian release that at it's core contains systemd. It's core developers, Lennart Poettering and Kay Sievers, work for a company that has multi-billion dollar contracts with NSA. It is your choice to

Re: systemd is here to stay, get over it now (was: Re: Pinning vs. conflicting)

art so possessed with murderous hate, Three words do come to mind … which I'll not write down here, in order not to escalate this discussion. You may mail me your guesses privately. ;-) -- -- Matthias Urlichs -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject

Re: systemd is here to stay, get over it now

On Thu, Jul 03, 2014 at 11:25:36AM -0700, Russ Allbery wrote: [snip] If the NSA are going to hide back-doors in open source projects (a rather dubious idea to start with, given how difficult it is and how much social blowback there would be when such a thing was inevitably discovered), they

Re: systemd is here to stay, get over it now (was: Re: Pinning vs. conflicting)

Hi, Matthias Urlichs matth...@urlichs.de writes: Please respect our decision to stay away from systemd and still be Debian users. If possible, please, don't resist changes that make our lives easier. *Sigh*. The problem is not that anybody resists such changes. I disagree. People *do* in

Re: systemd is here to stay, get over it now

On 03/07/14 22:50, David Weinehall wrote: Why would the NSA take even the slightest risk of discovery when they could put a backdoor in a driver for a piece of hardware that has full access to your system? Or on the firmware of your HDD/SDD: http://s3.eurecom.fr/~zaddach/docs/Recon14_HDD.pdf

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/03/2014 01:40 PM, Matthias Urlichs wrote: Hi, Thorsten Glaser: Can we get over this now and start making Jessie the most awesome stable release we've ever prepared together? To do that, it MUST work without systemd, if alone for

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

The Wanderer wande...@fastmail.fm writes: I, for one, would be highly displeased if a routine dist-upgrade to testing required me to reboot to avoid having things break. I generally dist-upgrade my primary computer to testing about once a week, give or take, but I don't reboot it more often

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

Hi, The Wanderer: I, for one, would be highly displeased if a routine dist-upgrade to testing required me to reboot to avoid having things break. We're talking about an upgrade from one release to the other here, with many intrusive changes (not just systemd). If you do that upgrade

Re: sysvinit is still here, and here to stay for jessie (was Re: systemd is here to stay, get over it now)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/03/2014 11:53 PM, Russ Allbery wrote: The Wanderer wande...@fastmail.fm writes: I, for one, would be highly displeased if a routine dist-upgrade to testing required me to reboot to avoid having things break. I generally dist-upgrade

Bike Week Starts Here at Space Coast Harley-Davidson!

View this message in a browser. http://archives.subscribermail.com/msg/e06249d1cc5c4fa4a8bceb6f30de375e.htm To view this message in a browser. Copy and Paste the following URL in your web address bar: http://www.spacecoastharley.com/default.asp?page=e-blast

Hello, I have a problem with CPP here

, this can not passed with CPP, but I need this logical here. Generally, the problem comes from #define ser_field(type, var) \ ser_new_field(tra, #type, #var, offsetof(struct_type, var)) I do not want another additional parameter in this macro like #define ser_field(type,var,struct_type), and I

Re: Hello, I have a problem with CPP here

taozhijiang taozhiji...@gmail.com writes: I want to using #define / #undef, and want to put them in a single macro, some thing like: #define DECALRE_TYPE(type) \ { #undef __curr_type; #define _curr_type type; } as we know, this can not passed with CPP, but I need this logical here. I'm

Bug#620333: ITP: naspro-bridge-it -- library to develop insert-your-API-here to LV2 bridges

Programming Lang: C Description : library to develop API-to-LV2 bridges NASPRO Bridge it is a little helper library to develop insert-your-API-here to LV2 bridges. . As of now, it basically offers a few utility functions and Turtle/RDF serialization for LV2 dynamic manifest generation, supporting

Free content available here

Hi All, urgently need poker links. interested please do not hesitate to contact me back Jon Peter

  1   2   3   >