Ubuntu
resolvconf package

patch to close 33362 not applied to edgy release

Bug #61310 reported by nick materer on 2006-09-19

Affects		Status	Importance	Assigned to	Milestone
	resolvconf (Ubuntu)	Fix Released	Undecided	William Grant

Bug Description

The resolvconf 1.36 uses /dev/shm and fails during startup. A patch to fix this problem by using /var/run was submitted by Sebastian Kapferthe and applied to the dapper release. The dapper resolvconf package works fine.

Revision history for this message

William Grant (wgrant) wrote on 2006-09-19:

debdiff to fix the problem Edit (3.4 KiB, text/plain)

Here I've attached a debdiff for a new version which readds those changes. I am wondering why the sync of 1.36 was performed in the first place, as the package had Ubuntu changes.

Changed in resolvconf:
assignee:	nobody → fujitsu
status:	Unconfirmed → In Progress

Revision history for this message

Daniel T Chen (crimsun) wrote on 2006-09-20:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 20 Sep 2006 03:12:20 -0400
Source: resolvconf
Binary: resolvconf
Architecture: source
Version: 1.36ubuntu1
Distribution: edgy
Urgency: low
Maintainer: resolvconf maintainers <email address hidden>
Changed-By: Daniel T Chen <email address hidden>
Description:
resolvconf - nameserver information handler
Changes:
resolvconf (1.36ubuntu1) edgy; urgency=low
.
   [ William Alexander Grant ]
   * Readded patch to use /var/run rather than /dev/shm (it was lost in a sync
     a while back)
   (Closes Ubuntu: #61310).
.
   [ Daniel T. Chen ]
   * debian/rules: Follow multiuser semantics for dh_installinit(1) --
     that is, we don't need to save anything for runlevels 0 or 6, so
     don't create those symlinks.
Files:
e2e5db83de94bf7559802b2fa42848c6 750 net optional resolvconf_1.36ubuntu1.dsc
01dfe295f5cd9299fd8e6956d2592a5c 67840 net optional resolvconf_1.36ubuntu1.tar.
gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFEO0Re9GwFciKvaMRAhxPAJsFbSh0Wa0MgKMcmEwXH6htstve+gCfWLFb
7cvqe4hsxFLQYvw2AxfkUn4=
=4vxu
-----END PGP SIGNATURE-----