** Summary changed:

- postrm fails if first source is cdrom
+ postinst fails if first source is cdrom

** Description changed:

  Binary package hint: apt-file
  
- While investigating bug #176753 I inspected the postrm file in the apt-
- file package.  That was not the cause for my problem, but it seems that
- it would fail to fetch the update if the first source in the file is a
- cdrom: location, as typically it is, unless you explicitly disable it.
+ While investigating bug #176753 I inspected the postinst file in the
+ apt-file package.  That was not the cause for my problem, but it seems
+ that it would fail to fetch the update if the first source in the file
+ is a cdrom: location, as typically it is, unless you explicitly disable
+ it.
  
  vnix$ grep ^deb\  /tmp/sources.list | head -1 | cut -s -d\  -f2 | cut -d/ -f3
  cdrom:[Ubuntu
  
  I had disabled mine, so /tmp/sources.list is a copy where I have
  uncommented the cdrom: entry again.
  
  (Shell programming style gag reflex suppressed.)
  
  In the light of bug #74097 vs bug #154180 as well as
  http://bugs.debian.org/405927 it would perhaps be better if apt-file
  could install a cron job which updates the files.  On Ubuntu, the
  regular update manager already fetches files periodically, so it should
  hopefully not be impossible to piggyback on that.  Then you should also
  block most of the error reports regarding having to run apt-file update
  as root, remember to run it, run it under a sensible umask, etc.  (See
  upstream's bug reports for a good sample of these.)
  
  As a quick fix in the meantime, how about
  
  perl -lne 'if (m%^deb\s+(?:https?|ftp)://([^\s/]+)/.*%) { print $1; last
  }' /etc/apt/sources.list
  
  This restricts matching to only http, https, and ftp sources.  (Still
  not sure the overall logic is sound, though.)

** Summary changed:

- postinst fails if first source is cdrom
+ Update in postinst fails if first source is cdrom

-- 
Update in postinst fails if first source is cdrom
https://bugs.launchpad.net/bugs/176757
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to