[Monotone-debian] Bug#466566: marked as done (upgrade in monotone package zaps /etc/monotone/passphrases)

[Debian Bug Tracking System]

Your message dated Sat, 9 Aug 2008 13:00:01 -0700
with message-id <address@hidden>
and subject line believed fixed in 0.36-1
has caused the Debian Bug report #466566,
regarding upgrade in monotone package zaps /etc/monotone/passphrases
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 address@hidden
immediately.)


-- 
466566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466566
Debian Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> upgrade in monotone package zaps /etc/monotone/passphrases
>
>
>
>
> Date: 
>
> Tue, 19 Feb 2008 15:35:22 +0100
>
>
>
>
> User-agent: 
>
> Thunderbird 2.0.0.6 (X11/20071022)
>
>
>
>
> Package: monotone-server
> Version: 0.35-2
>
> This is a courtesy copy of https://bugs.launchpad.net/bugs/193282
>
> I used to use the monotone packages from the project itself
> http://monotone.ca/downloads/0.34/ because ubuntu was not providing
> recent enough packages to use with openembedded.org. I also have one
> monotone server setup. To my great dismay, I found out that the upgrade
> to monotone and monotone-server version 0.35-2ubuntu2 from ubuntu proper
> zapped /etc/monotone/passphrases. No questions asked, no backup. I was
> lucky enough to find out why all of the sudden the monotone server
> refused to start up and have backup from which to restore the file.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> believed fixed in 0.36-1
>
>
>
>
> Date: 
>
> Sat, 9 Aug 2008 13:00:01 -0700
>
>
>
>
> Version: 0.36-1
>
> I requested additional information on this bug at the beginning of
> February and have not received any.  As I said then, I have reason to
> believe that this bug did exist in the Debian packages but was fixed
> in version 0.36-1, so I am now closing this bug as of that version.
> Much newer packages are now (finally!) available in Debian testing and
> I hope will propagate to Ubuntu soon.
>
> zw
>
>
> --- End Message ---