Copied to -updates.
** Changed in: popfile (Ubuntu Feisty)
Status: Fix Committed = Fix Released
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Tested successfully on Feisty.
Tagging verification-motu-done as per
https://wiki.ubuntu.com/StableReleaseUpdates.
** Tags added: verification-motu-done
** Tags removed: verification-motu-needed
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
Works for me
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Accepted into feisty-proposed, please test.
** Changed in: popfile (Ubuntu Feisty)
Status: In Progress = Fix Committed
** Tags added: verification-motu-needed
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You received this bug
popfile (0.22.4-1ubuntu0.1) feisty-proposed; urgency=low
* Made sure that /var/run/popfile exists in init.d script
(LP: #126894)
* Changed maintainer according to
https://wiki.ubuntu.com/DebianMaintainerField
-- dAniel hAhler [EMAIL PROTECTED] Mon, 30 Jul 2007 23:58:33 +0200
**
dAniel hAhler please send out the mail to the motu list asking for
verification testing. That's the next step.
** Changed in: popfile (Ubuntu Feisty)
Status: Fix Released = Fix Committed
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You
As discussed on IRC, I've only included the fix for init.d and the
maintainer change now.
** Attachment added: popfile_0.22.4-1ubuntu0.1.dsc.diff (feisty-proposed)
http://launchpadlibrarian.net/8614981/popfile_0.22.4-1ubuntu0.1.dsc.diff
--
/var/run/popfile does not get re-created after
** Changed in: popfile (Ubuntu Feisty)
Assignee: dAniel hAhler = Scott Kitterman
Status: Confirmed = In Progress
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: popfile (Ubuntu)
Assignee: (unassigned) = Scott Kitterman
Status: Triaged = In Progress
** Changed in: popfile (Ubuntu Feisty)
Status: New = Confirmed
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You received
popfile (0.22.4-1ubuntu1) gutsy; urgency=low
* Made sure that /var/run/popfile exists in init.d script
(LP: #126894)
* Changed chown separator from '.' to ':'
* Changed maintainer according to
https://wiki.ubuntu.com/DebianMaintainerField
* Standards-Version: 3.7.2
* Changed
Fix uploaded to Gutsy. Thank you for your contribution to Ubuntu.
Please prepare a new debiff for feisty-proposed with just the init,
postints, and maintainer changes and appropriate changelog entries.
** Changed in: popfile (Ubuntu)
Assignee: Scott Kitterman = (unassigned)
Status:
** Changed in: popfile (Ubuntu)
Status: Fix Committed = Fix Released
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Updated diff to not build-depend on po-debconf to have only the minimal
fix for backporting.
** Attachment added: popfile_0.22.4-1ubuntu1.dsc.diff (gutsy)
http://launchpadlibrarian.net/8592613/popfile_0.22.4-1ubuntu1.dsc.diff
** Attachment removed: popfile_0.22.4-1ubuntu1.dsc.diff (gutsy)
I've used Scott's advice and created a new debdiff, for gutsy.
Please note, that I've removed the part for
popfile-0.22.4/debian/po/templates.pot from the debdiff, because I think
it's not relevant, is it?
** Attachment added: popfile_0.22.4-1ubuntu1.dsc.diff (gutsy)
Needs to be fixed in Gutsy before an SRU is proposed. The cleanest
approach I've seen for this is to do something like:
+if [ ! -d ${RUNDIR} ] ; then
+ install -o ${USER} -g ${GROUP} -m 755 -d ${RUNDIR} || return 2
+fi
+
This checks first if the directory exists (you don't want to
Unsubbed UUS as there is nothing to upload yet.
** Changed in: popfile (Ubuntu)
Importance: Undecided = Medium
Status: New = Triaged
--
/var/run/popfile does not get re-created after reboot
https://bugs.launchpad.net/bugs/126894
You received this bug notification because you are a
debdiff for feisty-proposed.
Should I add the same debdiff (with changed changelog) for Gutsy?
Debian does not use tmpfs for /var/run, therefor this fix is Ubuntu
specific anyway.
** Attachment added: debdiff for feisty
http://launchpadlibrarian.net/8545404/popfile_0.22.4-1ubuntu1.dsc.diff
I see that I should not use dpatch to change a file in debian/, but I
still think that using $PIDFILE to create the needed directory makes a
lot of sense: it's a environment variable and therefor might get
changed. It does no harm to be on the safe side here, does it?
I've taken the chown line
Actually, it isn't an environment variable, it's just a variable in the
script, it just happens to be that the variable name is in all
uppercase.
Changing the postinst would be good too, yes.
Well, we can make the change in Ubuntu and wait for Debian to include
it, or you can wait for Debian to
Please find a fix for this attached.
I'm not providing a debdiff yet, because I'm not sure this is the
correct way to fix this.
Basically, it adds the following lines to the beginning of the init script:
mkdir -p `dirname $PIDFILE`
chown -R popfile.popfile `dirname $PIDFILE`
** Attachment
I agree with you, in that it isn't the correct way to fix this. Since
you're editing a file provided for packaging, as opposed to upstream. I
also disagree with using `dirname $PIDFILE`, since the directory the pid
file is going to be stored in won't change often, if at all. Secondly,
don't use .
21 matches
Mail list logo
