Ubuntu
pnopaste package

problem with the cronjob : Can't locate conf/debiandb.pm in @INC

Bug #771421 reported by Bruno Bigras on 2011-04-26

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
pnopaste (Ubuntu)	Fix Released	Undecided	Unassigned
Lucid	Fix Released	Low	Unassigned	Ubuntu lucid-updates
Oneiric	Fix Released	Undecided	Unassigned

Bug Description

Binary package hint: pnopaste

/etc/cron.d/pnopaste doesn't have read access to conf/debiandb.pm while running as 'nobody'.

3. Procedure, point '2'
1. Impact: This bug prevent entries from expiring in the database. It also cause annoying emails every 30 minutes to be sent to nobody since the cron scripts is outputting errors.
2. The has been fixed in Oneiric by the same way. http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/pnopaste/oneiric/revision/7#debian/pnopaste.cron.d . 1 package affected.
3. Patch fixing this is attached
4. TEST CASE: sudo -u nobody /usr/share/pnopaste/bin/expired_delete.pl (The commande works when using the user 'www-data').
5. The regression potential is considered low because only the user to run the cron job as has been changed.

Can't locate conf/debiandb.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl . /usr/share/pnopaste/bin/../) at /usr/share/pnopaste/bin/..//conf/SQL_Access.pm line 5.
BEGIN failed--compilation aborted at /usr/share/pnopaste/bin/..//conf/SQL_Access.pm line 5.
Compilation failed in require at /usr/share/pnopaste/bin/..//lib/Database.pm line 15.
BEGIN failed--compilation aborted at /usr/share/pnopaste/bin/..//lib/Database.pm line 15.
Compilation failed in require at /usr/share/pnopaste/bin/..//lib/Expire.pm line 13.
BEGIN failed--compilation aborted at /usr/share/pnopaste/bin/..//lib/Expire.pm line 13.
Compilation failed in require at /usr/share/pnopaste/bin/expired_delete.pl line 21.
BEGIN failed--compilation aborted at /usr/share/pnopaste/bin/expired_delete.pl line 21.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pnopaste 1.3-2
ProcVersionSignature: Ubuntu 2.6.32-30.59-generic-pae 2.6.32.29+drm33.13
Uname: Linux 2.6.32-30-generic-pae i686
Architecture: i386
Date: Tue Apr 26 14:46:07 2011
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
PackageArchitecture: all
ProcEnviron:
LANG=fr_CA.UTF-8
SHELL=/bin/bash
SourcePackage: pnopaste

See original description

Tags:

Related branches

lp://staging/~brunoqc/ubuntu/lucid/pnopaste/lucid-fix-771421

Merged into lp://staging/ubuntu/lucid/pnopaste

Ubuntu Development Team: Pending requested 2011-05-02

lp://staging/ubuntu/lucid-proposed/pnopaste

Revision history for this message

Bruno Bigras (brunoqc) wrote on 2011-04-26:

Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Bruno Bigras (brunoqc) wrote on 2011-05-02:

pnopaste_1.3-2ubuntu1.diff Edit (915 bytes, text/plain)

Here's a debdiff that fix my problem.

Bruno Bigras (brunoqc) on 2011-05-02

description:

updated

Brian Murray (brian-murray) on 2011-05-03

tags:

added: patch

Jamie Strandboge (jdstrand) on 2011-05-04

Changed in pnopaste (Ubuntu Oneiric):
status:	New → Invalid

Revision history for this message

Jamie Strandboge (jdstrand) wrote on 2011-05-04:

Thanks for the patch! The code change looks fine. The suggested change is the same one for Debian bug 582764, so that is fine. This bug does not affect 1.4.-1 and later (ie, maverick and later).

Bruno contacted on IRC and would like to pursue an SRU (stable release update). I have reviewed the packaging changes and they look fine with the following exceptions:
1. since this is going to be an SRU, it needs to use 'lucid-proposed' as the distribution name, not 'lucid'
2. the version should be 1.3-2ubuntu0.1, not 1.3-2ubuntu1 (again, since this is for SRU)

I have made these changes and uploaded to lucid-proposed.

@Bruno, can you review https://wiki.ubuntu.com/StableReleaseUpdates and afterward follow the 'Procedure' there, updating this bug so that it can be processed by a member of the SRU team. Thanks again!

Changed in pnopaste (Ubuntu Lucid):
importance:	Undecided → Low
milestone:	none → lucid-updates
status:	New → Triaged
status:	Triaged → Fix Committed

Bruno Bigras (brunoqc) on 2011-05-04

description:

updated

Jamie Strandboge (jdstrand) on 2011-05-04

Changed in pnopaste (Ubuntu Oneiric):
status:	Invalid → Fix Released

Bruno Bigras (brunoqc) on 2011-05-04

description:

updated

Revision history for this message

Clint Byrum (clint-fewbar) wrote on 2011-05-16: Please test proposed package

Accepted pnopaste 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!

tags:

added: verification-needed

Revision history for this message

Bruno Bigras (brunoqc) wrote on 2011-05-18:

I just tested and can confirm that pnopaste 1.3-2ubuntu0.1 from lucid-proposed fixes the error in the cron scripts and makes the expiration of entries in the database working again.

Jean-Baptiste Lallement (jibel) on 2011-05-18

tags:

added: verification-done
removed: verification-needed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-05-23:

This bug was fixed in the package pnopaste - 1.3-2ubuntu0.1

---------------
pnopaste (1.3-2ubuntu0.1) lucid-proposed; urgency=low

* Fix a permission error with the cron job (LP: #771421)
-- Bruno Bigras <email address hidden> Mon, 02 May 2011 14:45:09 -0400