lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: portmap (Ubuntu Lucid)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Branch linked: lp:ubuntu/lucid-proposed/portmap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be restarted
To manage notifications about this bug go to:
https
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be restarted
To manage notifications about
Thanks will get this fixed up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be restarted
To manage notifications about this bug go to:
https://bugs.launchpad.net
Adam,
On Mon, Dec 10, 2012 at 10:11:52PM -, Adam Stokes wrote:
> I wasn't aware of the specifics wrt to the maintainer script before
> changing hands to me so I based my conclusion on
>
https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/comments/9
> If this is not the case and we
I wasn't aware of the specifics wrt to the maintainer script before
changing hands to me so I based my conclusion on
https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/comments/9
If this is not the case and we need to extend the timeout (I assume
greater than 30 seconds?) We need to in
On Mon, Dec 10, 2012 at 08:34:05PM -, Steve Atwell wrote:
> portmap 6.0.0-1ubuntu2.3 restarts correctly even with open connections.
> However, when upgrading to portmap 6.0.0-1ubuntu2.3 from
> 6.0.0-1ubuntu2.2, portmap fails to restart if there's an open
> connection. (Because the old version
portmap 6.0.0-1ubuntu2.3 restarts correctly even with open connections.
However, when upgrading to portmap 6.0.0-1ubuntu2.3 from
6.0.0-1ubuntu2.2, portmap fails to restart if there's an open
connection. (Because the old version wasn't using SO_REUSEADDR, the new
version can't take over the port.)
Steve/Goswin,
Were either of you able to test that this package resolves your issue?
Thanks
Adam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be restarted
To
portmap doesn't exist beyond lucid, unsetting all those tasks.
** Changed in: portmap (Ubuntu Maverick)
Status: Triaged => Invalid
** Changed in: portmap (Ubuntu Natty)
Status: Triaged => Invalid
** Changed in: portmap (Ubuntu Oneiric)
Status: Triaged => Invalid
** Changed
Uploaded into lucid-proposed. Currently in the unapproved queue. You can
check the status here:
https://launchpad.net/ubuntu/lucid/+queue?queue_state=1&queue_text=
Unsubscribing ubuntu-sponsors. Please subscribe again if you want to SRU
this change into other releases.
--
You received this bug
Steve,
Assuming no blockers are present with this please wait until it is
released into -proposed and if you have extra cycles to re-test this
that would be greatly appreciated.
Thanks
Adam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Patch removed: "portmap_lp688550_lucid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+attachment/2725043/+files/portmap_lp688550_lucid.debdiff
** Patch added: "portmap_6.0.0-1ubuntu2.1.lucid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/
** Changed in: portmap (Ubuntu Lucid)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be restarted
To manage notifications about this
** Changed in: portmap (Ubuntu Lucid)
Assignee: (unassigned) => Adam Stokes (adam-stokes)
** Changed in: portmap (Ubuntu Maverick)
Assignee: (unassigned) => Adam Stokes (adam-stokes)
** Changed in: portmap (Ubuntu Oneiric)
Assignee: (unassigned) => Adam Stokes (adam-stokes)
** Cha
** Changed in: portmap (Ubuntu)
Assignee: Chris J Arges (christopherarges) => Adam Stokes (adam-stokes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be rest
Tested portmap 6.0.0-1ubuntu3~lp688550 on Lucid and verified that it can
restart after being stopped with an active connection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/st
This patch backports the patch 06-615641-reuse-socket.diff from debian
experimental.
I have built a test package for verification on lucid:
http://people.canonical.com/~arges/lp688550/
Thanks
** Patch added: "portmap_lp688550_lucid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/portmap/+
** Changed in: portmap (Ubuntu)
Status: Triaged => Won't Fix
** Also affects: portmap (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: portmap (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: portmap (Ubuntu Natty)
Importance: Un
I agree, this should be an SRU. Currently lucid is being targeted, but
this is fairly small fix and thus we could apply to lucid-oneiric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
Note that portmap has been dropped from precise as obsolete, entirely
superseded by rpcbind. We should probably target this bug at the
releases you are considering SRUs for (lucid-oneiric?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Changed in: portmap (Ubuntu)
Assignee: (unassigned) => Chris J Arges (christopherarges)
** Changed in: portmap (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Debian package portmap 6.0.0-5 in experimental has patch 06-615642
-reuse-socket.diff that makes portmap set SO_REUSEADDR. I do not
understand what the LOOPBACK_SETUNSET #define actually do, but it
basically removes it.
It's also worth noting that rpcbind suffers from bug #924593, which is
quite
This happens every time that portmap is stopped while something has a
connection open to it. The problem can be reliably reproduced like
this:
# nc localhost sunrpc &
[1] 14894
# stop portmap
[1] + done nc localhost sunrpc
portmap stop/waiting
# start portmap
start: Job failed to start
Yo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: portmap (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
por
This problem does not allways occur. Sometimes portmap starts up just
fine right after being stoped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be restarted
-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688550
Title:
portmap/statd can not be restarted
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
27 matches
Mail list logo
