, Bastian Neuburger wrote:
Hi Carsten,
I forgot to report back, but I also created Upstream bug 1510212
(https://bugzilla.mozilla.org/show_bug.cgi?id=1510212). As I stated
there it might take a while until I can test migration again, since I
reinstalled my test machine with Buster and thus have
with Jessie or Stretch right now.
I'll report back to upstream how this goes.
Cheers,
Bastian
On 11/30/18 6:50 AM, Carsten Schoenert wrote:
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1505038
Hello Bastian,
Am 20.11.18 um 17:44 schrieb Bastian Neuburger:
Hi,
I have
Hi,
I have however not yet tested what happens if you start thunderbird
aftter the upgrade and close it right away (i.e. not trying to sign
anything but also not entering the master password). I will try to test
this later but now I need a working mail client.
I also tested this variant
Hi,
> this is not differing between the Debian releases(, unfortunately).
> Debian hasn't touched any code here.
>
...
> First we/you need to check please if this behavior is also existing in
> the upstream binaries. To check this you can simply download the
> pre-compiled binary and start the
severity: critical
Dear Maintainer,
since I had an oldstable system with a key3.db around I also checked the
behaviour there.
I upgraded from
thunderbird:amd64 (52.9.1-1~deb8u1, 60.3.0-1~deb8u1)
and encountered the same situation:
I couldn't decrypt messages anymore.
Before trying to
Package: thunderbird
Version: 1:60.3.0-1~deb9u1
Two coworkers experienced the following problem on Debian Stretch after
upgrading from 1:60.2.1-2~deb9u1 to 1:60.3.0-1~deb9u1:
After upgrading they no longer had their X509 certificate for signing
and encryption listed in the "Your
Source: shorewall6
Severity: minor
DUCK reported a problem with the Vcs-Git URL set in the source packages
control file (c.f. http://duck.debian.net/sp/s/shorewall6.html).
Currently it points to
git://shorewall.git.sourceforge.net/gitroot/shorewall/shorewall/debian
However it seems that this
Source: golang-xmpp-dev
Severity: minor
DUCK reported a problem with the homepage set in the source packages
control file.
Currently it points to https://www.github.com/agl/xmpp
However it seems that this code was moved to
https://www.github.com/agl/xmpp-client as noted in [1], thus the
Source: gnome-doc-utils
Severity: minor
DUCK reported a problem with the homepage set in the source packages
control file.
Currently it points to https://live.gnome.org/GnomeDocUtils however it
seems that live.gnome.org was discontinued. The new homepage for the
Gnome Doc Utils should
Source: gnome-video-effects
Severity: minor
DUCK reported a problem with the homepage set in the source packages
control file.
Currently it points to https://wiki.gnome.org/GnomeVideoEffects however
it seems to have moved to
Hi,
I experienced the same thing.
When first registering the client/node at the chef-server chef-client
runs fine, but each chef run afterwards, it fails.
The reason is that the data structure sent by the chef-server to the
node was parsed as an object of class Chef::Node with ruby-json
Hi,
by replacing the file /usr/lib/ruby/vendor_ruby/chef/json_compat.rb,
which is part of the chef package, with the one at
https://github.com/opscode/chef/blob/834d814400a8a23ee8d865fa9d48e3f71895cd42/chef/lib/chef/json_compat.rb
I could get chef-client to work with the ruby-json 1.7.3-3.
. you fixed this in fix_paths.patch, but for ksh this
is missing. The attached patch should fix the problem.
From: Bastian Neuburger b.neubur...@gsi.de
Date: Tue, 8 Jan 2013 14:36:21 +0100
Subject: fix_ksh_path
---
init/ksh.in |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff
Package: chef-solr
Version: 10.12.0+dfsg-1
Severity: minor
Dear maintainer,
after installing chef-expander from package on Wheezy and starting it, I
get the following warning:
[Fri, 04 Jan 2013 10:51:20 +0100] WARN: You seem to have a legacy
setting for solr_url: did you mean
Hi,
I forgot to mention that I changed that line to the one that was
recommended in the warning message, so now it says:
solr_urlhttp://localhost:8983/solr;
Cheers,
Bastian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Hi,
I can confirm the problems described. The symlink allows solr to start.
However there seem to be some more problems regarding indexing. I will
try to figure out what is wrong and create a separate bug report.
Cheers,
Bastian
--
To UNSUBSCRIBE, email to
Hi Andreas,
the difference between running
git clone --branch master git://gitserver/fai.git
/var/lib/fai/config
from a normal shell and the script included with FAI is that this script
uses 2 git related environment variables:
export GIT_WORK_TREE=$FAI
export GIT_DIR=$FAI/.git
So to
Hi,
On Donnerstag, 19. Juli 2012, Bastian Neuburger wrote:
When I use a git repository as config source for a FAI network install,
FAI exits after trying to setup the config space from git.
Inside /var/lib/fai there were not only the files I checked into the git
repo but also the git control
Hi,
I finally got a working NFS-Root/initrd/Kernel with the second patch.
Don't know where the problem was, might have to do with outdated
packages (e.g. 3.2.0-2 Kernel instead of the current 3.2.0-3 Kernel) on
my FAI-Server that I upgraded before trying again.
Just wanted to let you know.
Package: fai-client
Version: 4.0.3
Tags: patch
When I use a git repository as config source for a FAI network install,
FAI exits after trying to setup the config space from git.
Inside /var/lib/fai there were not only the files I checked into the git
repo but also the git control files (e.g.
Confirmed.
I have a wheezy amd63 VM on which I successfully created a nfsroot with
the example config just 10 days ago. With the resulting nfsroot, kernel
and initrd I could successfully install clients.
Now when repeating the same steps (i.e. running fai-setup with the
example config) on a
21 matches
Mail list logo
