Ubuntu
etckeeper package

dpkg does not trigger commit

Bug #666491 reported by Rolf Leggewie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
etckeeper (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

Binary package hint: etckeeper

I'm running lucid and "sudo dpkg -i $deb" does not trigger a commit. The changes are only caught and committed during the next scheduled run (usually via cron)

Revision history for this message
Mathias Gug (mathiaz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

This is probably because etckeeper integration is done at the apt level and not the dpkg level.

Changed in etckeeper (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
importance: Medium → Wishlist
Revision history for this message
Angel Abad (angelabad) wrote :

Hi, testing in Lucid initial commit during install works well for me, also installing package with aptitude and with dpkg -i it works well.

Thanks!

Revision history for this message
Dave Walker (davewalker) wrote :

@Angel, I just tried to reproduce this issue and it seems some confusion has been caused. The etckeeper package automatically commits when and apt-get install/remove is performed on a package that modifies /etc/*.

The bug is looking for a commit when a raw dpkg command is performed, such as dpkg -i *.deb.

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.