FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 07-06-2011, 11:35 PM
Enrico Zini
 
Default Bug#602511: Fwd: upstart support for nodm

On Tue, Feb 08, 2011 at 11:31:40PM +0530, Joachim Breitner wrote:

> But then I find that dh_installinit would not install the regular init
> script if an upstart job is present, uses a compatibility link
> in /etc/init.d and adds a dependency on upstart-job, which seems to be
> only provided by upstart. I’m not sure if we want to force all users of
> nodm to switch to upstart – or is there an alternative?
>
> Enrico, what is your level of caring about nodm ATM?

It goes in bursts, mainly depending on when I have customers who would
like me to work on it.

I've just finished a rewrite so that nodm is now a real package manager,
tomorrow I'll do some real world testing and if all goes well, an upload
of the new version to unstable.


On Mon, Feb 14, 2011 at 10:06:45AM -0800, Steve Langasek wrote:

> Also, I strongly counsel *against* shipping this, or any, upstart job in a
> Debian package until this policy bug is *fixed*. The conversation is
> ongoing, and deploying such upstart jobs now realistically just runs the
> (very high) risk that you'll have more work to do on your package later once
> the policy interfaces are refined and implemented.

That is fine with me, I'll do that.

I must admit that I've just found myself in a rather intense WTF moment,
after finding out that the nodm package from the master branch was
depending on upstart and not shipping an init.d file.

I'm now going to move the upstart work that has been committed (thank
you for it, though!) to a separate "upstart" branch, and I'll upload
without it for now.


Ciao,

Enrico

--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>
 
Old 07-07-2011, 07:36 AM
Joachim Breitner
 
Default Bug#602511: Fwd: upstart support for nodm

Hi,

Am Donnerstag, den 07.07.2011, 01:35 +0200 schrieb Enrico Zini:
> On Tue, Feb 08, 2011 at 11:31:40PM +0530, Joachim Breitner wrote:
>
> > But then I find that dh_installinit would not install the regular init
> > script if an upstart job is present, uses a compatibility link
> > in /etc/init.d and adds a dependency on upstart-job, which seems to be
> > only provided by upstart. I’m not sure if we want to force all users of
> > nodm to switch to upstart – or is there an alternative?
> >
> > Enrico, what is your level of caring about nodm ATM?
>
> It goes in bursts, mainly depending on when I have customers who would
> like me to work on it.
>
> I've just finished a rewrite so that nodm is now a real package manager,
> tomorrow I'll do some real world testing and if all goes well, an upload
> of the new version to unstable.

Great, I always found nodm a far better approach than dpkg!

(Sorry, CNR ;-))

> On Mon, Feb 14, 2011 at 10:06:45AM -0800, Steve Langasek wrote:
>
> > Also, I strongly counsel *against* shipping this, or any, upstart job in a
> > Debian package until this policy bug is *fixed*. The conversation is
> > ongoing, and deploying such upstart jobs now realistically just runs the
> > (very high) risk that you'll have more work to do on your package later once
> > the policy interfaces are refined and implemented.
>
> That is fine with me, I'll do that.
>
> I must admit that I've just found myself in a rather intense WTF moment,
> after finding out that the nodm package from the master branch was
> depending on upstart and not shipping an init.d file.
>
> I'm now going to move the upstart work that has been committed (thank
> you for it, though!) to a separate "upstart" branch, and I'll upload
> without it for now.

Sounds good to me, and thanks for the ongoing maintenance.

BTW, since I stopped using the Freerunner and, after your rewrite (which
I appreciate!), don’t really know any of the nodm code, would you mind
taking over maintenance completely? I doubt that I add much value here
any more.

Greetings,
Joachim

--
Joachim "nomeata" Breitner
Debian Developer
nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
 
Old 07-07-2011, 04:44 PM
Enrico Zini
 
Default Bug#602511: Fwd: upstart support for nodm

On Thu, Jul 07, 2011 at 09:36:38AM +0200, Joachim Breitner wrote:

> BTW, since I stopped using the Freerunner and, after your rewrite (which
> I appreciate!), don’t really know any of the nodm code, would you mind
> taking over maintenance completely? I doubt that I add much value here
> any more.

I rather you studied the new code and gave a hand :P

It's fine, I don't mind taking over maintenance completely, only it's
going to be in bursts as it's been so far, and having at least a
comaintainer who can look after minor packaging issues or simple BTS
interaction would be a good idea. It doesn't have to be you, of course.


Ciao,

Enrico

--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>
 
Old 07-09-2011, 12:30 AM
 
Default Bug#602511: Fwd: upstart support for nodm

All I know is you fellows broke nodm rather royally for me.
I use nodm on desktops and laptops, with Debian flavor:
deb http://ftp.us.debian.org/debian experimental main contrib non-free
deb http://ftp.us.debian.org/debian unstable main contrib non-free

I did aptitude forbid-version nodm and will stay with
nodm:
Installed: 0.7-1.1
Candidate: 0.8-1
for now. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633089
I fear assisting further test will injure my monitors, judging from how
the multitude of different behaviors observed upon start, no matter the
value of NODM_USER, including root and vanilla test accounts.

The old nodm started right away, no ifs ands or buts. On my three
computers, the new one just sputters along, popping in and out of a
blank screen and then back to the console and back to the blank screen.
Or dying completely. Or getting into X but not reading ~/.Xresources ...
etc. Must be some kind of a race condition, that's all I know. Yes, I
purged and reinstalled. Snap, crackle, pop. No more testing for me lest
I need to go to town to buy a new monitor.

P.S., Upon install we are asked "start at boot...?" Well if we say "no",
we will never be able to start it, and the rest of the configuration is
aborted. That message needs to be updated to sysv-rc-conf(8) era
thinking. Giving more details, for the user who still wants
/etc/init.d/nodm start to work, but not to start at boot. (I start via a
question with countdown in /etc/rc.local myself).


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87aacol2gx.fsf@jidanni.org">http://lists.debian.org/87aacol2gx.fsf@jidanni.org
 

Thread Tools




All times are GMT. The time now is 08:05 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org