Your message dated Sat, 8 Mar 2008 01:10:30 +0100
with message-id <[EMAIL PROTECTED]>
and subject line closing, as upgrades from sarge are not interesting anymore
has caused the Debian Bug report #386741,
regarding piuparts: need to redo apt-get update after apt is upgraded from sarge
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
386741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386741
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: piuparts
Version: 0.19-1

Hello Lars,

I am back using piuparts and I am performing Sarge to Etch upgrades.
When I try to do 'piuparts -a gnupg openoffice.org' it fails in the
last step because apt was upgraded but 'apt-get update' was not
peformed. piuparts to fail with:

  WARNING: The following packages cannot be authenticated!
    openoffice.org-l10n-en-us openoffice.org-common openoffice.org-core
    python-uno openoffice.org-writer openoffice.org-calc openoffice.org-draw
    openoffice.org-impress openoffice.org-math openoffice.org-java-common
    openoffice.org-base openoffice.org
  E: There are problems and -y was used without --force-yes

Eventually it might considered as a bug in apt:

Etch version requires extra files from the server (Release.gpg I guess)
that were not downloaded by Sarge 'apt-get update'. Further
installations/upgrades will fail until 'apt-get update' is performed
again.

Could piuparts work-around that ?

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


--- End Message ---
--- Begin Message ---
Hi,

sarge has reach end of life, so ugrade testing from sarge is not that 
interesting, so let's close this bug.

(Also there is #466043 open, which basically requests a similar feature, more 
hooks, and which I'll plan to fix soonish, so that in future those 
workarounds should be easily possible. But for sarge, its pointless :)


regards,
        Holger

Attachment: pgpr0EyQ9UhaH.pgp
Description: PGP signature


--- End Message ---

Reply via email to