oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: nis (Ubuntu Oneiric)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
The version of nis in oneiric-proposed has been removed as the bugs it
was fixing (including this one) were not verified in a timely fashion.
** Changed in: nis (Ubuntu Oneiric)
Status: Fix Committed = Triaged
** Tags removed: verification-needed
** Tags removed: removal-candidate
--
** Tags added: removal-candidate
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage notifications about this bug go to:
** Changed in: nis (Ubuntu Natty)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To
Seems like it's without controversy to release the lucid SRU, so I've
done that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
This bug was fixed in the package nis - 3.17-31ubuntu0.10.04.3
---
nis (3.17-31ubuntu0.10.04.3) lucid-proposed; urgency=low
* debian/nis.ypbind.upstart: don't try to start ypserv if
NISSERVER=false.
nis (3.17-31ubuntu0.10.04.2) lucid-proposed; urgency=low
* Drop the upstart
Thanks Ernst. I'll take that as a verification for lucid. This should
progress to lucid-updates soon.
** Tags added: verification-done verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
I'm marking this verification-failed on account of bug #993291, which is
fixed in precise and quantal but which is still present in the version
of the nis package in the -proposed queue.
** Tags removed: verification-done verification-needed
** Tags added: verification-failed
--
You received
Since bug #993291 only affects the upgrade path from a previous SRUed
version to a later version that includes this bug fix, it should only
impact the following upgrades:
lucid-precise
natty-oneiric
oneiric-precise
So the only supported upgrade path from lucid is the one to precise, and
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage
just to add a data point: starting 2012-04-19 my lucid machine is
working with 3.17-31ubuntu0.10.04.3 from proposed with. A few nis
accounts are being used regularly. There have been a large number of
suspend resume cycles and various reboots without any nis related
problems.
--
You received
Unfortunately I lost access to the box I had been using for testing and
I haven't been able to bring up a similar box to run the test on. To
make matters worse, I've now left the job that this was all for :(
I had really hoped to test this before my last day but the stars never
quite aligned. I
Jeremy, any word on testing this nis SRU?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage notifications about this bug
I have installed 3.17-31ubuntu0.10.04.3 on lucid after purging the previous
version including our hand crafted upstart configuration.
- Installation went fine
- I have tested the function as a NIS client successfully
- starting after reboot works, it also survives a suspend/resume cycle
But I
The host I had been testing on has died a horrible death. I'm trying to
find a new place to test this. On the bright side, the new host won't
have ever had the old -proposed package to interfere with the upgrade,
so if that was my problem, it should just work.
Fingers crossed.
--
You received
Thanks for the testing, Ernst.
I think (but I am no sure) that you would see more output with the
current stock nis package.
Yes, that's true, because the output from init scripts is sent to the
console at boot time. But I don't think that's something that should be
a blocker for this SRU,
Jeremy,
On Fri, Mar 30, 2012 at 06:11:04PM -, Jeremy Yoder wrote:
I'm having numerous problems installing the -proposed package on Lucid.
Sometimes the upgrade succeeds, sometimes it fails. I haven't been able
to figure out why yet (I think I'm starting from the same state each
time,
Hello harald, or anyone else affected,
Accepted nis into natty-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
I'm having numerous problems installing the -proposed package on Lucid.
Sometimes the upgrade succeeds, sometimes it fails. I haven't been able
to figure out why yet (I think I'm starting from the same state each
time, but maybe there's a file somewhere I'm not considering).
If the package
Hello harald, or anyone else affected,
Accepted nis into oneiric-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
Hello harald, or anyone else affected,
Accepted nis into lucid-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
A user has contacted me privately to report a regression with the
package in -proposed:
I think I updated the nis package yesterday through the ubuntu update
process.
This morning nis did not work anymore. The solution was that
/etc/init/ypbind.conf
is waiting for a local server which is
** Changed in: nis (Ubuntu Lucid)
Status: Fix Committed = In Progress
** Changed in: nis (Ubuntu Oneiric)
Status: Fix Committed = In Progress
** Changed in: nis (Ubuntu Natty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of
Is that what broke? I tried it Monday and my NIS broke and reverting
didn't fix it. I never checked the configs though. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Hello harald, or anyone else affected,
Accepted nis into lucid-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
Steve/Martin:
I'm not seeing the updated nis package in lucid-proposed. Should I be?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency
On Tue, Mar 20, 2012 at 03:25:13PM -, Jeremy Yoder wrote:
I'm not seeing the updated nis package in lucid-proposed. Should I be?
The package has not yet been accepted into lucid-proposed, sorry. It'll
have to wait for the next SRU team processing run.
--
Steve Langasek
Is it in a PPA somewhere I can try it? If getting into -proposed is
hard, seems like it should be tested first :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS
On Tue, Mar 20, 2012 at 04:12:24PM -, Jeremy Yoder wrote:
Is it in a PPA somewhere I can try it? If getting into -proposed is
hard, seems like it should be tested first :)
No, but you can grab it from the queue and build from source if you want
to:
Tested the proposed package in Lucid and it appears to depend on Upstart
0.9.7-2 but Lucid only has 0.6.5-8. So trying to upgrade marks nis as
broken and wants to remove it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in
I confirm nis from lucid-proposed is uninstallable due to dependency on
upstart (= 0.9.7-2) and probably same problem will occurs on natty
since natty has upstart 0.9.7-1 and 0.9.7-1.1 in natty-proposed
marking as verification-failed
** Tags removed: verification-needed
** Tags added:
I removed the lucid-proposed package again, and reset the verification
tags for oneiric/natty.
2012-03-15 17:53:55 INFORemoving candidates:
2012-03-15 17:53:55 INFOnis 3.17-31ubuntu0.10.04.1 in lucid
2012-03-15 17:53:55 INFOnis 3.17-31ubuntu0.10.04.1 in lucid amd64
2012-03-15
2012-03-15 17:56:08 INFORemoving candidates:
2012-03-15 17:56:08 INFOnis 3.17-31ubuntu0.11.04.1 in natty
2012-03-15 17:56:08 INFOnis 3.17-31ubuntu0.11.04.1 in natty amd64
2012-03-15 17:56:08 INFOnis 3.17-31ubuntu0.11.04.1 in natty armel
2012-03-15 17:56:08 INFO
yep, sorry about that. Packages reuploaded for lucid and natty with the
dependency relaxed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken
Hello harald, or anyone else affected,
Accepted nis into lucid-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
Hello harald, or anyone else affected,
Accepted nis into natty-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
** Branch linked: lp:ubuntu/natty-proposed/nis
** Branch linked: lp:ubuntu/oneiric-proposed/nis
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency
** Branch linked: lp:ubuntu/lucid-proposed/nis
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage notifications about this
** Changed in: nis (Ubuntu Lucid)
Status: Triaged = In Progress
** Changed in: nis (Ubuntu Natty)
Status: Triaged = In Progress
** Changed in: nis (Ubuntu Oneiric)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server
Is that change to CRON backported to Lucid? I'm guessing not, but that
would be nice.
As for gdm/lightdm/atd I think the crucial one there is atd. The login
stuff probably takes long enough to start that NIS will be up by then
(plus that's nowhere near an exhaustive list of *dm's and adding all
** Changed in: nis (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
** Branch linked: lp:ubuntu/nis
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage notifications about this bug go to:
I've taken on the task of trying to get this fixed for precise using
native and idiomatic upstart jobs for each of the services. It's not
directly backportable to lucid, as it depends on upstart's wait-for-
state generic helper instead of doing things directly in the nis-wait
job, adds a
Note that this implementation only has 'start on starting autofs or
starting am-utils', because these are the only packages in Debian
unstable whose init scripts declare a 'Should-Start: ypbind' except for
cron, and cron has been fixed to now be able to pick up new NSS
information after startup.
** Also affects: nis (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: nis (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: nis (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Changed in: nis (Ubuntu Lucid)
Importance:
This bug was fixed in the package nis - 3.17-32ubuntu2
---
nis (3.17-32ubuntu2) precise; urgency=low
* Convert to native upstart jobs, with a versioned dependency on
upstart (= 0.9.7-2) because we use the wait-for-state job. LP: #569757.
* Depend on rpcbind (=
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage notifications about this bug go to:
Excerpts from Jeremy Yoder's message of Fri Jan 27 17:22:47 UTC 2012:
Thanks for working on this! Once you get Oneiric/Precise working, are
you planning to fix this in Lucid? Lucid is still going to be around
for a few more years :)
I will discuss it with my fellow SRU team members. I
Thanks for working on this! Once you get Oneiric/Precise working, are
you planning to fix this in Lucid? Lucid is still going to be around
for a few more years :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
Twbecker, thank you! Bug found.. new packages pushed to my PPA (they
will take a while to build), the version should be
3.17-32ubuntu2~oneiric1~ppa2
If those look good (they tested fine here) then this should be ready for
upload to precise.
--
You received this bug notification because you are
...and still in oneiric. What is it going to take to get this fixed?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage
Twbecker, can you try the packages in my PPA on oneiric? The postinst
seems to be failing for people, but I need some help debugging it as it
works fine for me. It appears to fail when trying to start the service,
so the output of 'start nis' would be particularly useful after the
failure.
--
I have a colleague that ran into the issue on Oneiric, I don't have a
box handy to test it on. I'll relay this request to him though. My
real interest is getting this fixed for 12.04, which I and several other
colleagues are planning on moving to when it's released.
--
You received this bug
From my colleague:
“start nis” didn’t produce any errors, so I re-ran the install with a
set –x added to the script. It hit problems in invoke-rc.d, so I ran
that standalone with set –x. Results:
# apt-get install nis
Reading package lists... Done
Building dependency tree
Reading state
For the installation error try to remove /var/lib/dpkg/info/nis.postinst
to avoid the error condition.
** Tags added: natty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
The problem is still in in natty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
To manage notifications about this bug go to:
Could this be targeted for 10.04.3? This is really a pretty bad problem
with 10.04, and the 10.04.x releases are going to get further apart
after 10.04.3.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
Jeremy, this needs to be fixed in Oneiric before we can backport the fix
to Lucid. 10.04.3 is coming in just a few weeks, so I'm not sure we'll
be able to get it up in time even if the fixed packages for Oneiric and
lucid-proposed were uploaded tomorrow.. they'd still need verification.
That
I'm using a slightly modified version of the ypbind file posted in
comment 5 on my diskless clients and it's working fine. The modification
is around the starting condition:
# XXX: the original file checks if net-device-up IFACE=!lo, but I can't
# get that to work. And this seems to race a bit
Clint,
My attached files based on your original suggestion of two new upstart
jobs should do the trick as far as a minimally invasive fix for many
users. Anything more substantial would probably be hard to get approved
for a point release right?
It looks (from Christian's latest comment) like
** Summary changed:
- NIS upstart dependancy broken for lucid
+ NIS upstart dependency broken for lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart
61 matches
Mail list logo
