update-manager-core should use ~/.config to store it's configs

Bug #474025 reported by Oleksij Rempel
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

according to "XDG Base Directory Specification" update-manager should store the configs to ~/.config/update-manager-core . And this will make home folder clear.

see:
XDG Base Directory Specification
http://standards.freedesktop.org/basedir-spec/latest/ar01s03.html
$XDG_CONFIG_HOME defines the base directory relative to which user specific configuration files should be stored. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used.

ProblemType: Bug
Architecture: i386
Date: Wed Nov 4 11:41:55 2009
DistroRelease: Ubuntu 9.10
Package: update-manager-core 1:0.126.6.1
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: update-manager
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Oleksij Rempel (olerem) wrote :
Revision history for this message
Robert Roth (evfool) wrote :

What files do you see that are update-manager-core config files and are not stored in the XDG-compliant config directory? I haven't found anything that update-managar stores in the home directory. (even the cache is stored in an XDG compliant way.)

Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Mechanical snail (replicator-snail) wrote :

I still have a ~/.update-manager-core directory, on a system upgraded through several Ubuntu versions. It contains 2 files, "meta-release" and "meta-release-development". The files were last modified in 2010, suggesting they are no longer used (presumably the migration failed to remove the obsolete config).

Changed in update-manager (Ubuntu):
status: Expired → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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