Hi developers,
How to restart New Member Process?
I have had New Member Process in the past.
But It's canceled, because I had not a good response to it.
https://nm.debian.org/public/process/13039
Now, I would like to dput packages for ATS2 language.
http://www.ats-lang.org/
https://bugs.debian
Hi,
Steve Langasek:
> And yes, there are PHP extensions that are not distributable in binary form
> because of this license. But relicensing *the extension* changes nothing
> about this, they are *still* not redistributable as part of Debian because
> they're linking GPL code into PHP which is an
Hi,
Clint Byrum:
> That's quite the opposite of what I would suggest. Such distributions
> may actually feel that they can withstand any damages that PHP/Zend can
> claim against them, and their brands depend on them taking care of their
> end users, but even if they didn't, they could also absorb
Package: wnpp
Severity: wishlist
Owner: Rene Engelhard
* Package name: ucpp
Version : 1.3.2
* URL : Thomas Pornin
* License : BSD
Programming Lang: C
Description : embeddable, quick and light C preprocessor
A C preprocessor designed to be embeddable, qu
On Tue, Jul 1, 2014, at 10:17, Matthias Urlichs wrote:
> (C) Bite the bullet and admit that when everybody else calls a color
> "light blue" which we consider to be "cyan", we might as well docuent
> that fact instead of trying to convince everybody else that they're
> wrong, even if th
On Tue, Jul 1, 2014, at 08:15, Stefano Rivera wrote:
> Hi Matthias (2014.06.26_08:38:09_+0200)
> > Of these, roughly 20% have switched to systemd. And they apparently did not
> > and do not have any problem with it, otherwise we'd hear about it. Here and
> > other places. Quite loudly.
>
> Not nec
On 30/06/14 23:47, Marco d'Itri wrote:
>> Unless I'm mistaken, the wording in the PHP license makes it invalid for
>> > anybody that isn't actually the PHP project to use without making a
>> > false claim that "THIS SOFTWARE IS PROVIDED BY THE PHP DEVELOPMENT
>> > TEAM".
> The fact that ~nobody els
On Tue, 2014-07-01 at 13:01, Ondřej Surý wrote:
> On Tue, Jul 1, 2014, at 08:15, Stefano Rivera wrote:
> > Hi Matthias (2014.06.26_08:38:09_+0200)
> > > Of these, roughly 20% have switched to systemd. And they apparently did
> > > not
> > > and do not have any problem with it, otherwise we'd hear
Dear all,
A few days ago, after a routine upgrade from testing, the power button on
my laptop ceased functioning. I was busy at the time, so I lived with
having to remember to type "sudo shutdown -h now" for a few days; yesterday,
I finally took the time to debug the issue.
I started with "strac
On Tue, Jul 01, 2014 at 03:25:36PM +0200, Juliusz Chroboczek wrote:
> Dear all,
>
> A few days ago, after a routine upgrade from testing, the power button on
> my laptop ceased functioning. I was busy at the time, so I lived with
> having to remember to type "sudo shutdown -h now" for a few days;
1. Could some competent person tell me the right way to tell apt that
it
should fail an upgrade rather than installing systemd? I guess
I could make a dummy package that conflicts with systemd, but I'm
sure there's a better way.
I think you can just put
Package: systemd
Pin:
❦ 1 juillet 2014 15:25 +0200, Juliusz Chroboczek
:
> A few days ago, after a routine upgrade from testing, the power button on
> my laptop ceased functioning. I was busy at the time, so I lived with
> having to remember to type "sudo shutdown -h now" for a few days; yesterday,
> I finally too
On Tue, July 1, 2014 15:25, Juliusz Chroboczek wrote:
> 2. Could some kind soul explain to the systemd maintainers that gentle
> persuasion, while not always the most efficient way to take over the
> world, is more in line with point 4 of the Debian Social Contract
> than alternati
Juliusz Chroboczek wrote:
>So I'm turning to this list for help:
>
> 1. Could some competent person tell me the right way to tell apt that it
> should fail an upgrade rather than installing systemd? I guess
> I could make a dummy package that conflicts with systemd, but I'm
I made such
On Tue, 01 Jul 2014 18:26:53 +0400
vita...@yourcmc.ru wrote:
> > 1. Could some competent person tell me the right way to tell apt
> > that it
> > should fail an upgrade rather than installing systemd? I guess
> > I could make a dummy package that conflicts with systemd, but
> > I'm su
On Tue, Jul 01, 2014 at 04:38:16PM +0200, Thijs Kinkhorst wrote:
> The responses from the systemd maintainers are indeed on the terse side,
> but I can imagine that your style of bug reporting does not invite our
> volunteers to spend more time on it.
This is not a question of spending time. An up
+++ Thorsten Glaser [2014-07-01 14:45 +]:
> Juliusz Chroboczek wrote:
>
> >So I'm turning to this list for help:
> >
> > 1. Could some competent person tell me the right way to tell apt that it
> > should fail an upgrade rather than installing systemd? I guess
> > I could make a dumm
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: openstack-doc-tools
Version : 0.15
Upstream Author : OpenStack Development Mailing List
* URL : https://github.com/openstack/openstack-doc-tools
* License : Apache-2.0
Programming Lang:
>> gentle persuasion [...] is more in line with point 4 of the Debian
>> Social Contract than [...] bullying?
> May I suggest that you treat others the way you want to be treated?
I am not a Debian Developer. I am not bound by the Social Contract.
Are we to expect a higher standard of behaviour
Am 01.07.2014 17:20, schrieb Thomas Weber:
> Or, taking a different perspective: now that the issue is known, what is
> done to prevent another user from hitting the very same issue in the
> future?
Install systemd-sysv for systemd-shim.
The libpam-systemd package in 204-9 ensures that either of t
On 01/07/14 17:20, Thomas Weber wrote:
> Or, taking a different perspective: now that the issue is known, what is
> done to prevent another user from hitting the very same issue in the
> future?
I think that a critical debconf warning should be in place to avoid
replacing the init system of users
Package: wnpp
Severity: wishlist
Owner: Andrew Kelley
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-chalk
Version : 0.4.0
Upstream Author : Sindre Sorhus (
http://sindresorhus.com)
* URL : https://github.com/sindresorhus/chalk
* License : Ex
On 06/30/2014 05:43 PM, Stefano Zacchiroli wrote:
> On Mon, Jun 30, 2014 at 10:27:49AM +0100, Lars Wirzenius wrote:
>> On Mon, Jun 30, 2014 at 10:42:09AM +0200, Tollef Fog Heen wrote:
>>> ]] Thomas Goirand
+1 for keeping the name which is funny
>
> What's funny about an OS stating publicly th
Am 01.07.2014 17:35, schrieb Juliusz Chroboczek:
>
> I am not a Debian Developer. I am not bound by the Social Contract.
>
I may remind you about [1] then. If you feel like you need to rant or
vent, please do it someplace else or expect a terse answer like the one
you got.
[1] https://www.deb
* Juliusz Chroboczek , 2014-07-01, 15:25:
I filed bug 753357
Why is this bug marked as fixed in systemd/204-9?
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.
Matthias Urlichs writes:
> (C) Bite the bullet and admit that when everybody else calls a color
> "light blue" which we consider to be "cyan", we might as well docuent
> that fact instead of trying to convince everybody else that they're
> wrong, even if they are, from our PoV. After
Michael Biebl made an argument from authority:
Am 01.07.2014 17:35, schrieb Juliusz Chroboczek:
I am not a Debian Developer. I am not bound by the Social Contract.
I may remind you about [1] then. If you feel like you need to rant or
vent, please do it someplace else or expect a terse ans
Thijs Kinkhorst wrote:
The responses from the systemd maintainers are indeed on the terse
side,
but I can imagine that your style of bug reporting does not invite our
volunteers to spend more time on it.
The replies were not just terse, the replies were downright rude.
Can we perhaps agree t
On 01/07/14, 05:35pm, Juliusz Chroboczek wrote:
> >> gentle persuasion [...] is more in line with point 4 of the Debian
> >> Social Contract than [...] bullying?
>
> > May I suggest that you treat others the way you want to be treated?
>
> I am not a Debian Developer. I am not bound by the Socia
On Tue, July 1, 2014 17:35, Juliusz Chroboczek wrote:
>>> gentle persuasion [...] is more in line with point 4 of the Debian
>>> Social Contract than [...] bullying?
>
>> May I suggest that you treat others the way you want to be treated?
>
> I am not a Debian Developer. I am not bound by the Soci
On Tue, Jul 1, 2014, at 17:20, Thomas Weber wrote:
> On Tue, Jul 01, 2014 at 04:38:16PM +0200, Thijs Kinkhorst wrote:
> > The responses from the systemd maintainers are indeed on the terse side,
> > but I can imagine that your style of bug reporting does not invite our
> > volunteers to spend more
On Tue, Jul 1, 2014, at 18:03, Jakub Wilk wrote:
> * Juliusz Chroboczek , 2014-07-01, 15:25:
> >I filed bug 753357
>
> Why is this bug marked as fixed in systemd/204-9?
I suggest to reassign this bug to acpi-support-base and stop this
yet-another-senseless-flamewar-about-systemd in the beginning
Package: wnpp
Severity: wishlist
Owner: Andrew Kelley
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-jsondiffpatch
Version : 0.1.7
Upstream Author : Benjamin Eidelman
* URL : https://github.com/benjamine/jsondiffpatch
* License : Expat
Prog
On Jul 01, Carlos Alberto Lopez Perez wrote:
> I think that a critical debconf warning should be in place to avoid
> replacing the init system of users without prior explicit consent.
I think that this would be an annoying waste of time for most users,
since only a few people care so much about
Am 01.07.2014 18:28, schrieb Ondřej Surý:
> On Tue, Jul 1, 2014, at 18:03, Jakub Wilk wrote:
>> * Juliusz Chroboczek , 2014-07-01, 15:25:
>>> I filed bug 753357
>>
>> Why is this bug marked as fixed in systemd/204-9?
>
> I suggest to reassign this bug to acpi-support-base and stop this
> yet-anoth
> The replies were not just terse, the replies were downright rude.
That's hardly the main problem with Michael's behaviour.
I reported an actual bug, including conclusions that I got from fourty
minutes of tracing the ACPI scripts. Michael closed it straight away,
without investigating the issu
On Tue, Jul 1, 2014, at 18:09, Marco d'Itri wrote:
> On Jul 01, Carlos Alberto Lopez Perez wrote:
>
> > I think that a critical debconf warning should be in place to avoid
> > replacing the init system of users without prior explicit consent.
> I think that this would be an annoying waste of time
Am 01.07.2014 18:53, schrieb Juliusz Chroboczek:
> Michael closed it straight away,
> without investigating the issue.
Oh, I did. That's why I told you to install systemd-shim.
It would be great if you can dial down your accusations a little.
--
Why is it that all of the instruments seeking int
On 01/07/14 18:09, Marco d'Itri wrote:
> On Jul 01, Carlos Alberto Lopez Perez wrote:
>
>> I think that a critical debconf warning should be in place to avoid
>> replacing the init system of users without prior explicit consent.
> I think that this would be an annoying waste of time for most user
On Tue, Jul 01, 2014 at 04:23:01PM +0100, Wookey wrote:
> You get a choice of 'prevent-systemd' which stops it running as init
> but allows the -shim and libpam packages so that logind and the like
> will work. Or 'systemd-must-die' which conflicts with everything
> systemdish.
Wookey,
Please ren
I think that this would be an annoying waste of time for most users,
since only a few people care so much about not being tainted by systemd
I do not care being tainted by systemd when it works. Actually on two
very different machines it means no audio for me.
On a NAS it means no boot(probab
Package: wnpp
Severity: wishlist
Owner: Andrew Kelley
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-zip-stream
Version : 0.3.5
Upstream Author : Chris Talkington (http://christalkington.com/)
* URL : https://github.com/ctalkington/node-zip-stream
* L
On Tue, Jul 01, 2014 at 06:09:08PM +0200, Marco d'Itri wrote:
> On Jul 01, Carlos Alberto Lopez Perez wrote:
> > I think that a critical debconf warning should be in place to avoid
> > replacing the init system of users without prior explicit consent.
> I think that this would be an annoying wast
2014-07-01 19:38 GMT+02:00 Eric Valette :
>> I think that this would be an annoying waste of time for most users,
>> since only a few people care so much about not being tainted by systemd
>
>
> I do not care being tainted by systemd when it works. Actually on two very
> different machines it means
On 2014-07-01, Carlos Alberto Lopez Perez wrote:
> Maybe desktops user don't care much about the init system as long as
> they can boot to the desktop.
They care as long as everything works. And for "everything works" to
keep on happening, we need a effective migration to systemd, or a army
of de
On Tue, Jul 01, 2014 at 06:53:27PM +0200, Juliusz Chroboczek wrote:
> > The replies were not just terse, the replies were downright rude.
>
> That's hardly the main problem with Michael's behaviour.
I stand by what I said yesterday, in a different thread, but the same
mailing list:
# When a proj
Package: wnpp
Severity: wishlist
Owner: Andrew Kelley
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-archiver
Version : 0.10.1
Upstream Author : Chris Talkington (http://christalkington.com/)
* URL : https://github.com/ctalkington/node-archiver
* Lice
Am 01.07.2014 19:38, schrieb Eric Valette:
>> I think that this would be an annoying waste of time for most users,
>> since only a few people care so much about not being tainted by systemd
>
> I do not care being tainted by systemd when it works. Actually on two
> very different machines it means
Miroslaw,
unless you offer to ack as a front desk for bugs in systemd, then
please go with your judgments elsewhere. Your judgmental
comments are neither helpful nor welcome here.
Thanks,
Ondrej
On Tue, Jul 1, 2014, at 18:17, Mirosław Baran wrote:
> Michael Biebl made an argument from authority:
Michael,
On Tue, Jul 1, 2014, at 18:51, Michael Biebl wrote:
> > Install systemd-sysv for systemd-shim.
> > The libpam-systemd package in 204-9 ensures that either of the two is
> > installed.
>
> The behaviour of acpi-support-base is correct, there shouldn't be any
> bug filed against it.
pleas
On Tue, Jul 1, 2014, at 20:18, Ondřej Surý wrote:
> Michael,
>
> On Tue, Jul 1, 2014, at 18:51, Michael Biebl wrote:
> > > Install systemd-sysv for systemd-shim.
> > > The libpam-systemd package in 204-9 ensures that either of the two is
> > > installed.
> >
> > The behaviour of acpi-support-base
❦ 1 juillet 2014 10:53 -0700, Steve Langasek :
> - hold systemd back at 204 until systemd-shim is updated
The way user sessions work is quite different between 204 and 208. I
would hope that Jessie will come with 208 for this reason. Holding
systemd until systemd-shim is ready may prevent tha
>> Michael closed it straight away, without investigating the issue.
> Oh, I did. That's why I told you to install systemd-shim.
Now could you please reopen bug 753357, or at least allow me to do it?
-- Juliusz
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject o
On 01/07/2014 19:59, Matthias Klumpp wrote:
These are valid points, and thank you for reporting bugs! However, as
unstable user, some breakage can be expected, and the point for
transitioning early in unstable is to make the transition as smooth as
possible when someone uprades Debian stable, wh
On 1 July 2014 19:15:32 IST, "Ondřej Surý" wrote:
>unless you offer to ack as a front desk for bugs in systemd, then
>please go with your judgments elsewhere. Your judgmental
>comments are neither helpful nor welcome here.
My comment was factual and polite, thank you very much.
Being a DD is
Am 01.07.2014 20:21, schrieb Ondřej Surý:
> On Tue, Jul 1, 2014, at 20:18, Ondřej Surý wrote:
>> Michael,
>>
>> On Tue, Jul 1, 2014, at 18:51, Michael Biebl wrote:
Install systemd-sysv for systemd-shim.
The libpam-systemd package in 204-9 ensures that either of the two is
installed.
Which bug report is that?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748651
I will try to add the requested debug log ASAP. Dunno where I got the
initial bogus trace command from. Probably not invented it.
--eric
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
w
On Tue, 01 Jul 2014 20:08:35 +0200, Michael Biebl wrote:
> Am 01.07.2014 19:38, schrieb Eric Valette:
>>> I think that this would be an annoying waste of time for most users,
>>> since only a few people care so much about not being tainted by
>>> systemd
>>
>> I do not care being tainted by syste
On Tue, Jul 01, 2014 at 08:23:09PM +0200, Vincent Bernat wrote:
> ❦ 1 juillet 2014 10:53 -0700, Steve Langasek :
> > - hold systemd back at 204 until systemd-shim is updated
> The way user sessions work is quite different between 204 and 208. I
> would hope that Jessie will come with 208 for
Am 01.07.2014 19:53, schrieb Steve Langasek:
> new init. But the systemd maintainers are anxious to update to a newer
> version in unstable, and while there are plans in Ubuntu to make
> systemd-shim support the interfaces needed for newer logind, this isn't
> ready yet.
This issue has been known
Hi Michael,
On Tue, Jul 01, 2014 at 05:37:55PM +0200, Michael Biebl wrote:
> Am 01.07.2014 17:20, schrieb Thomas Weber:
> > Or, taking a different perspective: now that the issue is known, what is
> > done to prevent another user from hitting the very same issue in the
> > future?
> Install syste
Am 01.07.2014 21:06, schrieb Eric Valette:
>> Which bug report is that?
>
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748651
Ok, thanks for sharing.
As for the issue you encountered on your NAS using RAID10: Please do
file a bug report and we will follow up there
Michael
--
Why is
Am 01.07.2014 21:33, schrieb Steve Langasek:
> Ok, thanks for this clarification. I didn't realize this dependency had not
> yet made it into testing.
>
> FWIW, from reading the bug log, it was not clear to me that you were taking
> responsibility for this bug and stating that it had been fixed
Am 01.07.2014 21:34, schrieb Michael Biebl:
> Indeed, I take the blame for my verbosity here.
Or non-verbosity, if you so wish.
I do have to add that the tone of the bug report didn't really inspire
me to write paragraphs of explanations.
You know, I'm also just a human.
--
Why is it that all
On Tue, Jul 01, 2014 at 08:57:37PM +0200, Michael Biebl wrote:
> Am 01.07.2014 20:21, schrieb Ondřej Surý:
> > On Tue, Jul 1, 2014, at 20:18, Ondřej Surý wrote:
> >> Michael,
> >> On Tue, Jul 1, 2014, at 18:51, Michael Biebl wrote:
> Install systemd-sysv for systemd-shim.
> The libpam-sy
On 2014-07-01, Steve Langasek wrote:
> The question is which of these is a worse outcome for the jessie release. I
> come down firmly on the side that breaking desktops on upgrade is a worse
> outcome than being behind on the latest and greatest user session interface=
> s.
We already have broke
> Juliusz, can you please paste your apt logs showing what pulled systemd
> in on the system?
Sent by private mail. If anyone else wants a copy, please drop me a note.
-- Juliusz
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
]] Michael Biebl
> Am 01.07.2014 19:53, schrieb Steve Langasek:
> > new init. But the systemd maintainers are anxious to update to a newer
> > version in unstable, and while there are plans in Ubuntu to make
> > systemd-shim support the interfaces needed for newer logind, this isn't
> > ready ye
On 13624 March 1977, Lars Wirzenius wrote:
>> You get a choice of 'prevent-systemd' which stops it running as init
>> but allows the -shim and libpam packages so that logind and the like
>> will work. Or 'systemd-must-die' which conflicts with everything
>> systemdish.
> Please rename the systemd-
Package: wnpp
Severity: wishlist
Owner: Andrew Kelley
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-lastfm
Version : 0.9.0
Upstream Author : James Scott
* URL : https://github.com/jammus/lastfm-node
* License : Expat
Programming Lang: Java
On Tue, Jul 01, 2014 at 07:47:36PM +, Sune Vuorela wrote:
> On 2014-07-01, Steve Langasek wrote:
> > The question is which of these is a worse outcome for the jessie release. I
> > come down firmly on the side that breaking desktops on upgrade is a worse
> > outcome than being behind on the l
On Tue, 2014-07-01 at 22:09 +0200, Joerg Jaspert wrote:
> On 13624 March 1977, Lars Wirzenius wrote:
>
> >> You get a choice of 'prevent-systemd' which stops it running as init
> >> but allows the -shim and libpam packages so that logind and the like
> >> will work. Or 'systemd-must-die' which con
On 2014-07-01, Steve Langasek wrote:
> https://bugs.debian.org/src:systemd-shim
>
> Show me a bug report, not FUD.
I'd rather point to the likely-faulty code.
it is likely in or around
src:kde-workspace/powerdevil/daemon/backends/upower/powerdevilupowerbackend.cpp
when checking for suspend c
On Tue, Jul 1, 2014 at 9:59 PM, Tollef Fog Heen wrote:
> ]] Michael Biebl
>
>> Am 01.07.2014 19:53, schrieb Steve Langasek:
>> > new init. But the systemd maintainers are anxious to update to a newer
>> > version in unstable, and while there are plans in Ubuntu to make
>> > systemd-shim support t
On Wed, 02 Jul 2014, Thomas Goirand wrote:
> I don't think so. I think it encourages to be more easy going, and have
> fun, but never mind. Let's keep Debian boring^W^Wportland weird. :)
+1
Fun is missing, humour even more.
Norbert
---
Am 02.07.2014 00:09, schrieb Tshepang Lekhonkhobe:
> On Tue, Jul 1, 2014 at 9:59 PM, Tollef Fog Heen wrote:
>> Just as a heads-up: We're planning on making 208 hit unstable once 204-9
>> is in testing, and then follow up with newer versions once we deem they
>> are ready.
>
> Do you mean 204-14?
+++ Lars Wirzenius [2014-07-01 18:34 +0100]:
> On Tue, Jul 01, 2014 at 04:23:01PM +0100, Wookey wrote:
> > You get a choice of 'prevent-systemd' which stops it running as init
> > but allows the -shim and libpam packages so that logind and the like
> > will work. Or 'systemd-must-die' which conflic
Steve Langasek writes:
>> Also, post-upgrade-pre-reboot systems has had issues since forever,
>
> No. There have been very few instances in which the system was left in an
> unusable state after a dist-upgrade, even for desktops.
On desktops, upgrades of iceweasel and icedove regularly break
cur
Svante Signell writes:
> What about systemd-nogo or nogo-systemd, alternately just no-systemd?
I have a ‘no-mono’ package (not hosted anywhere; I welcome contact from
anyone who wants to upload it).
I would expect ‘prevent-…’ or ‘no-…’ as the name of such packages.
--
\ “I used to think
+1 :)
On Jul 1, 2014 6:39 PM, "Norbert Preining" wrote:
> On Wed, 02 Jul 2014, Thomas Goirand wrote:
> > I don't think so. I think it encourages to be more easy going, and have
> > fun, but never mind. Let's keep Debian boring^W^Wportland weird. :)
>
> +1
>
> Fun is missing, humour even more.
>
>
+++ Stefano Zacchiroli [2014-06-30 11:43 +0200]:
> On Mon, Jun 30, 2014 at 10:27:49AM +0100, Lars Wirzenius wrote:
> > On Mon, Jun 30, 2014 at 10:42:09AM +0200, Tollef Fog Heen wrote:
> > > ]] Thomas Goirand
> > > > +1 for keeping the name which is funny
>
> What's funny about an OS stating public
On Wed, Jul 02, 2014 at 01:53:06AM +0100, Wookey wrote:
> But OK. I get it - this is still too contentious to have any room for
> this sort of foolishness and if it's to exist at all it'll have to be
> called something boring. That's a little sad, but we'll all
> survive. This isn't supposed to be
On Tue, Jul 1, 2014 at 5:53 PM, Wookey wrote:
> +++ Stefano Zacchiroli [2014-06-30 11:43 +0200]:
>> On Mon, Jun 30, 2014 at 10:27:49AM +0100, Lars Wirzenius wrote:
>> > On Mon, Jun 30, 2014 at 10:42:09AM +0200, Tollef Fog Heen wrote:
>> > > ]] Thomas Goirand
>> > > > +1 for keeping the name which
Carlos Alberto Lopez Perez writes:
> But I think that many sysadmins that are going to upgrade their servers
> from wheezy to jessie care about this.
Indeed. I care very much about ensuring that systemd is installed on my
servers, as I think the benefits for servers are at least as substantial
Nikolaus Rath writes:
> Steve Langasek writes:
>>> Also, post-upgrade-pre-reboot systems has had issues since forever,
>> No. There have been very few instances in which the system was left in
>> an unusable state after a dist-upgrade, even for desktops.
> On desktops, upgrades of iceweasel a
On 1. Juli 2014 09:41:17 MESZ, Kiwamu Okabe wrote:
>Hi developers,
>
>How to restart New Member Process?
>
>I have had New Member Process in the past.
>But It's canceled, because I had not a good response to it.
>
>https://nm.debian.org/public/process/13039
>
>Now, I would like to dput packages fo
On Lu, 30 iun 14, 01:56:20, Thomas Goirand wrote:
> >
> > You're not seriously suggesting dpkg would "sneak" a package on your
> > system behind your back, do you?
>
> I believe he's only suggesting that having a package installed with a
> Conflict: is harder to break (even by mistake) than just
Your message dated Wed, 2 Jul 2014 09:27:57 +0300
with message-id <20140702062757.GB1546@sid.nuvreauspam>
and subject line Re: Bug#753367: general: usb drives automatically mount but
user permission is ro
has caused the Debian Bug report #753367,
regarding general: usb drives automatically mount b
On Ma, 01 iul 14, 09:34:58, Eugene Zhukov wrote:
> Hello,
>
> I know this question probably doesn't belong to this list, and I tried
> debian-user@ first, but didn't get a single response.
> I'm trying to create a VM with Windows 7. Is there a way to do that
> from USB stick? It is a ~10GB corpora
On Ma, 01 iul 14, 15:57:41, Neil Williams wrote:
> On Tue, 01 Jul 2014 18:26:53 +0400
> vita...@yourcmc.ru wrote:
> >
> > I think you can just put
> >
> > Package: systemd
> > Pin: origin ""
> > Pin-Priority: -1
>
> If what you actually intend is to retain sysvinit-core, it would need
> to be s
90 matches
Mail list logo
