Versions of packages podman suggests:
ii containers-storage 1.43.0+ds1-8+b2
pn docker-compose
ii iptables1.8.9-2
-- no debconf information
>From 8792c6130ab99e055f1317ff6bdabc9a57162716 Mon Sep 17 00:00:00 2001
From: Lorenz Schori
Date: Wed, 5 Feb 2025 14:25:06 +0100
Su
he bookworm branch yourself if you want to deploy the fix sooner:
https://salsa.debian.org/nagios-team/icinga2/-/tree/bookworm?ref_type=heads
Kind Regards,
Bas
Kind regards
Lorenz Kästle
[0] https://icinga.com/blog/critical-icinga-2-security-releases-2-14-3/
[1]
https://icinga.com/blog/uncovering-a-
nd. The attached patch should fix this and
work with both old and new Singular versions.
Best,
Benjamin
commit 4ce0549f510d246c8f69c85c509fc2d13d882442
Author: Benjamin Lorenz
Date: Thu Nov 9 11:15:06 2023 +0100
singular: support new return types for saturation command
This was cha
Dear David,
we have now managed to work around the perl changes and released
polymake version 4.11 which restores compatibility with perl 5.38.
Among various other adjustments the workaround relies on an
auto-generated perl source file that was is now copied into the polymake
source.
This me
On 02/10/2023 08.46, Joachim Zobel wrote:
Am Sonntag, dem 01.10.2023 um 15:30 -0300 schrieb David Bremner:
I'm currently waiting to see what happens with
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042521
before putting much effort into debugging polymake issues.
The discussion d
Package: barrier
Version: 2.4.0+dfsg-2+b1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
The debian package tracking system can not determine the upstream
version of this software. This is like relat
Hi,
the attached patch should fix the build with perl 5.36:
- adapt to renamed HVhek_UNSHARED
- adjust for changes in the complement operation
Best,
Benjamin Lorenz
On 03/07/2022 16.33, Niko Tyni wrote:
Source: polymake
Version: 4.6-3
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags
On 21/12/2021 17.49, Lucas Nussbaum wrote:
[ /polytope/objects/Polytope/properties/Geometry/SLACK_IDEAL ] 1 ? cannot
open `standard.lib`
// ** Could not get 'Singular'.
// ** Either set environment variable 'SINGULAR_EXECUTABLE' to 'Singular',
// ** or make sure that 'Singular' is at "/usr/S
On 31/08/2021 17.29, David Bremner wrote:
This package fails to build from source with Perl 5.34 (currently
in experimental). I don't presently understand why; I'm not aware of
changes to Perl_pp_keys or Perl_pp_rv2hv. So the root issue might also
be on the Perl side. At least it seems to reliabl
Package: samba
Version: 2:4.13.5+dfsg-2
Severity: normal
Dear Maintainer,
After upstream commit 43c808f2ff907497dfff0988ff90a48fdcfc16ef any
attempt to change a password over IPv6 fails on the server side. Samba
generates the following log entries (on the domain controller):
Starting GENSEC
Package: sympa
Version: 6.2.40~dfsg-1+deb10u1
Severity: normal
Dear Maintainer,
After installing Sympa 6.2.40 as Debian package on a Debian 10
machine,Sympa does not start correctly after reboot of the maschine.
Acoortding to the log eentries, Sympa cannot access the database
(mariaDB).
The https
Dear Joachim,
thanks for the report,
F12 displays a warning
"THREE.OrbitControls: As part of the transition to ES6 Modules, the files in
'examples/js' were deprecated in May 2020 (r117) and will be deleted in
December 2020 (r124)...
these warnings can be ignored as we ship pre-r124 versions
Fix submitted via MR in salsa:
https://salsa.debian.org/go-team/packages/golang-github-containers-dnsname/-/merge_requests/2
pgpOadshxzZGM.pgp
Description: OpenPGP digital signature
Fix submitted via MR in salsa:
https://salsa.debian.org/go-team/packages/golang-github-containers-dnsname/-/merge_requests/1
pgpbDiVKdCHTu.pgp
Description: OpenPGP digital signature
Fix submitted via MR in salsa:
https://salsa.debian.org/go-team/packages/golang-github-containers-dnsname/-/merge_requests/1
pgpydNCx3xkYF.pgp
Description: OpenPGP digital signature
round this it is enough to symlink the binary into the
correct location:
ln -s /usr/lib/dnsname /usr/lib/cni/dnsname
Cheers,
Lorenz
-- System Information:
Debian Release: 10.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (90, &
Package: golang-github-containers-dnsname
Version: 1.1.1+ds1-4
Severity: normal
Dear Maintainer,
The dnsname cni plugin requires dnsmasq in order to work properly. Thus
golang-github-containers-dnsname should depend on dnsmasq-base.
-- System Information:
Debian Release: 10.8
APT prefers stabl
Hello David,
On 28/01/2021 12.59, David Bremner wrote:
The relevant output from the tests seems to be
[ /polytope/objects/Polytope/properties/Triangulation and volume/RELATIVE_VOLUME ] 1polymake:
WARNING: rule RELATIVE_VOLUME : SQUARED_RELATIVE_VOLUMES failed: Undefined subroutine
&Polymak
Hello,
I can reproduce the problem as well.
My plasma/breeze window decorations are gone. Yesterday the following
packages were upgraded to 4:5.19.5-3:
libkdecorations2private7
libkdecorations2-5v5
libkf5screen-bin
libkf5screen7
If I try to open the window decoration settings dialog, the who
On 13/02/2020 16.53, Benjamin Lorenz wrote:
> On 13/02/2020 13.18, David Bremner wrote:
>> Benjamin Lorenz writes:
>>>> It looks like it's flint related?
>>>
>>> Yes, I think this is a bug in flint and for now I suggest disabling the
>>>
On 13/02/2020 13.18, David Bremner wrote:
> Benjamin Lorenz writes:
>
>>
>>> It looks like it's flint related?
>>
>> Yes, I think this is a bug in flint and for now I suggest disabling the
>> flint-interface of polymake with the configure option --with
On 11/02/2020 16.22, Gianfranco Costamagna wrote:
> Hello, looks like with TERM=unknown the testsuite fails:
>
> *** Failed tests ***
>
> /<>/apps/common/rules/functions_help.rules:248: testcase 1
> expected: regular return
> got: EXCEPTION: Can't find a valid termcap file at
> /<>/perllib/
=...)
at ./include/core/polymake/FlintPolynomial.h:689
#8 pm::FlintPolynomial::xgcd (p2=..., p1=..., t=..., s=..., g=...)
at ./include/core/polymake/FlintPolynomial.h:685
...
I have tried to create a flint-only testcase for this which is attached
and gives on debian amd64:
lorenz@debian
the german text for --no-minimal-
upgrade-steps would be correct for --minimal-upgrade-steps but is -- as i
strongly assume -- wrong for --no-minimal-upgrade-steps.
kind regards & hope this helps
Lorenz Wenner
-- System Information:
Debian Release: bullseye/sid
APT prefers testin
> Thomas Goirand writes:
>
> So, my proposal is to get rid of sysv-rc provided by sysvinit, in the
favor of
> OpenRC, so that developers can start replacing their init scripts by
superior
> runscripts.
Please don't: runit uses sysvinit scripts as a fallback for a missing
runscript (with
runs
On 26/11/2019 01.51, Andreas Beckmann wrote:
> On 26/11/2019 00.00, Benjamin Lorenz wrote:
>> tldr: please rebuild normaliz and then try polymake again.
>
> Thanks for the analysis. binNMU of normaliz requested: #945504
Thanks.
>> This is very weird but after some diggi
On 23/11/2019 20.30, Andreas Beckmann wrote:
> Control: affects 941933 + src:polymake
> Control: retitle -1 polymake: FTBFS with normaliz 3.8.1: segfaults during
> tests
>
> On 23/11/2019 10.45, Benjamin Lorenz wrote:
>> On 22/11/2019 22.06, Andreas Beckmann wrote:
>&
On 22/11/2019 22.06, Andreas Beckmann wrote:
> polymake FTBFS against perl 5.30:
> https://buildd.debian.org/status/package.php?p=polymake&suite=unstable
>
> *** Summary ***
>
> *** Failed tests ***
>
> /<>/apps/polytope/src/gc_closure.cc:173: testcase 1
> expected: regular return
> got: EX
/x86_64-linux-gnu/openmpi/include because link group
mpi-x86_64-linux-gnu is broken
The second time around, the /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so
symlink exists and everything works. I'm not sure when exactly that is created,
but like Ron, I suspect that it's too late.
Cheers,
Lorenz
as I can tell the source of the problem is a SONAME tracking issue in
libusbmuxd: https://github.com/libimobiledevice/libusbmuxd/issues/81 which
breaks something in libimobiledevice which then causes upower to crash.
Cheers,
Lorenz
On Sun, 10 Nov 2019, at 15:34, Michael Biebl wrote:
> Am 10.11.
"g_thread_proxy"
> #6 0x77baafb7 in start_thread (arg=) at
pthread_create.c:486
> ret =
> pd =
> now =
> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737338115840,
-1214051612260060498, 140737488344782, 140737488344783
Il giorno dom 3 nov 2019 alle ore 05:55 Dmitry Bogatov
ha scritto:
> Do you want me to upload #943395 and #942320 right now, or wait for
> dh-runit and git-daemon?
I think it's better to wait.
For git-daemon-run I already have the patch but i'm not able to test it
because git
fails to build for
Il giorno dom 20 ott 2019 alle ore 22:06 Dmitry Bogatov
ha scritto:
> Sorry, don't follow. Previously no link in /etc/service was created if
> dh-runit decides that service should not be enabled, now hidden link is
> created instead. How it is more confusing?
OK, from existing users there are no
On 10/7/19 8:30 PM, Niko Tyni wrote:
> On Mon, Oct 07, 2019 at 08:59:47PM +0300, Niko Tyni wrote:
>> Source: polymake
>> Version: 3.2r4-4
>> Severity: serious
>> Tags: ftbfs
>> Control: block 935737 with -1
>>
>> This package failed to build in sid when rebuilding against Perl 5.30.
>>
>> Looking a
Il giorno dom 8 set 2019 alle ore 21:17 Dmitry Bogatov
ha scritto:
> > +# don't restart anacron when it's done
> Why? Will it work correctly on machine that is up for 24/7?
When anacron is done with its jobs it exit and when restarted, if it
detects that
there are no job to run it exits again.
Il giorno dom 1 set 2019 alle ore 15:25 Dmitry Bogatov
ha scritto:
> > > * please do not print "Starting $NAME". It goes to log, quite
> > > pointless and may confuse scripts/tools that want to analyze log.
> > [ ...]
> I have two ideas:
>
> * Check for $VERBOSE variable. If you have issues w
Source: xorg-server
Version: 2:1.20.4-1
Severity: normal
Dear Maintainer,
I'm not really sure if this is the right package to report this bug to,
bus as xwayland is built from it, I guess I'm right ...
Since a recent update to my system it defaults to wayland instead of
xorg. From that moment on
Package: gnome-common
Version: 3.18.0-4
Severity: normal
File: gnome
Dear Maintainer,
in recent versions of gnome I found, that the file-chooser dialog is
somhow inconsistent...
## Steps to reproduce
1. use whichever gnome software you want
2. open the file chooser either to load or to save a
Package: python3-ldap3
Version: 2.4.1-1
Severity: normal
Tags: patch
Dear Maintainer,
My usecase is the creation of new accounts within a windows active directory
enviroment.
The new account gets a one-time password which has to be changed on first login.
To use this functionality, the "pwdLastSe
Il giorno ven 23 ago 2019 alle ore 13:22 Dmitry Bogatov
ha scritto:
> [...]What about making
> in postinst symlink
>
>/run/runit/supervise/foo -> /lib/runit/supervise/foo
>
> if latter exists? It should resolve problem with overwriting symlink of
> running process.
It's ok for me, thanks
>>if test ! -h "$svdir"/supervise; then
>> rm -rf "$svdir"/supervise
>> -ln -s /var/lib/runit/supervise/"$sv" "$svdir"/supervise
>> +ln -s /run/runit/supervise/"$sv" "$svdir"/supervise
>
>Will it handle both /var/lib and /run/runit location?
Mmm.. No
In my system i
Il giorno mer 14 ago 2019 alle ore 21:22 Dmitry Bogatov
ha scritto:
>Yes, I go this way.
Ok.
in commit d07519ae you already create /run/runit/supervise directory,
but the directory for the appendant log of 'foo' service will be
/run/runit/log/supervise/foo
or
/run/runit/supervise/foo.log ?
Lore
Il giorno dom 11 ago 2019 alle ore 19:48 Dmitry Bogatov
ha scritto:
> The simpliest fix is revert of #924903. More attractive way is to move
> supervise directories into /run.
The permission issue is not essential to me, but i prefer to move supervise
directories into /run.
I don't see a strong
Hi Dmitry, thanx for this, i'm testing right now.
Il giorno ven 26 lug 2019 alle ore 15:30 Dmitry Bogatov
ha scritto:
> Here I request review. Is this feature really needed. Is timestamp file
> needed? Maybe there are simplier ways to implement it?
Gerrit Pape said he is collecting patches to do
Control: severity -1 normal
Ok, here is what I've found out; to reproduce the issue you need to
disable with update-rc.d a script that has an empty ' Default-Stop: ' field
in the LSB header.
# update-rc.d ssh disable
insserv: warning: current start runlevel(s) (empty) of script `ssh'
overrides LS
Il giorno mar 9 lug 2019 alle ore 01:52 Colin Watson
ha scritto:
>Is this just another instance of problems with your virtual machine not
>having enough entropy (#912616 etc.)?
It looks you are right, thanks for the tip!
Dmitry, I can pass the test that include openssh-server with a command like
atov
ha scritto:
>
> [2019-07-03 02:36] Lorenz
> > Dmitry,
> > sorry it took so long to send the patches,
>
> No need to be sorry :) You are doing awesome job at tasks I do not dare
> to tackle.
>
> > but while updating the test i run into several issues i'
Dmitry,
sorry it took so long to send the patches, but while updating the test i
run into
several issues i'm not able to solve by myself:
* I try to include openssh into the test but it makes the test fail because
ssh get stuck
at boot (same issue as reported by Martin Pitt in #838480 message #4
Hi,
> Why are these 'service' calls? Do 'service' support runit already?
No, not yet. I'm using 'service' script to test if those services, started
as sysv scripts,
are up. According to my testing, rsyslog, cron, udev and dbus are
installed and running in
the systemd testbed, so it make sense to
90C4:SSL routines:func(169):reason(196)
I believe that this means that transgui is built against an older version of
OpenSSL, and that rebuilding the package would fix it?
Cheers,
Lorenz
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'
Sure, here is the link
https://salsa.debian.org/debian/init-system-helpers/merge_requests/10
Thanks
Il giorno ven 24 mag 2019 alle ore 19:59 Felipe Sateler
ha scritto:
> Hi Lorenz
>
> On Tue, May 21, 2019, 11:42 Lorenzo Puliti wrote:
>
>> Control: reassign 924132 i
Hi,
> True. Here are patches. What do you think?
I haven't had time to test but the patch looks good to me, just an
observation:
to my experience
/etc/init.d/${service} status
is not always reliable in term of both results and exit codes, we will have
the
chance to fix a certain number of sysv
Hi Felipe,
Felipe Sateler wrote:
> > > Upstream asks if cgroup is in v2-mode in the affected systems.
> With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cgroup
> or cgroup2 filesystems.
root@lorenz:~# findmnt -R /sys/fs/cgroup
TARGET
Hi Felipe,
thanks for looking into this.
I've made a very quick test of the patch you provided this morning,
patching systemd 240-5 source
and rebuilding the whole thing.
It works for me.
Lorenz
in
the code
since at least systemd v232-15.
According to my experiments, the culprit is the following:
>when udevd is run in background and it's not detached with it's own
'--daemon' option,
>then a udevadm command is enough to kill everything.
It does not make any sense to me, but that's it.
Regards,
Lorenz
phic
> session and prompt a udevadm command from there, it's the VT session that
get crashed.
Actually I'm wrong on this, it looks like switching from VT to Graphic
session (and vice versa)
with systemd trigger the restart of udev and this is enough to crash the
session, no need to
to prompt any 'udeadm' command in this case.
Regards,
Lorenz
some other adjustments are nedded to the script)
Be aware that in both case this will reintroduce bug #791944
Dear Systemd Maintainers,
still you can't reproduce this? Can you please say something?
Lorenz
Il giorno gio 24 gen 2019 alle ore 08:36 Gedalya ha
scritto:
> Hi,
>
>
, i suspect you need also one (or more than one) of
the following:
* no systemd installed
* mdadm installed
* a RAID setup (althought i'm not sure this one is feasible in virtualbox)
Anything else i can do to help solving this?
Thanks,
Lorenz
Il giorno mer 16 gen 2019 alle ore 15:49 Dmitry B
On Thu, 20 Dec 2018 18:04:25 + Dmitry Bogatov
wrote:
> ... What do you think about state of
> salsa:runit-team/runit, commit a8d698d? I am considering uploading it to
> unstable.
Wait, when I proposed you to move the start of sysv scripts to stage 2 I
completely
forgot about runit-sysv and ru
On Thu, 20 Dec 2018 18:04:25 + Dmitry Bogatov
wrote:
> ... What do you think about state of
> salsa:runit-team/runit, commit a8d698d? I am considering uploading it to
> unstable.
It should solve this bug, and also having a 90 sec timeout looks like a
final
solution to any misbehaving daemon
Hi !
We are approaching the freeze, and I think that the state of runit about
'sulogin' is
acceptable but not optimal: there are two minor issues unresolved
[2018-11-09 01:09] alecfeld...@disroot.org
> Glancing over the changes, changing the runsvdir is a bad idea, since
> now stage 3 won't stop
experience with container, so can't tell if the logic is
backwards,
it looks to me that /sys directory is read/execute only in my Debian, but
'test -w' performed by root exit 0..
# cat /home/ombra/udevtest.txt
Script started on 2018-12-02 14:36:45+01:00
root@lorenz:~# ls -l / | gr
On Thu, 15 Nov 2018 20:31:21 +0100
> On Thu, 15 Nov 2018, Dmitry Bogatov wrote:
>>...
> > Please create new mailing list.
>>
> > Currently I do maintain runit init system and related tools {dh-runit
> > and *-run packages} myself, but as contributors appear, there is need
> > in coordinatin
Hi,
thanks for the report! We already have a patch included in polymake
3.2r3 and 3.2r4 that fixes the build error and keeps compatibility with
older boost versions. (And also added another change there to avoid a
depreciation warning for math::lcm)
I have tried updating the package here:
https:/
Hi,
this comes from a different output order produced by cdd version 0.94j
(probably caused by https://github.com/cddlib/cddlib/pull/10 ).
We have disabled this test in polymake 3.2r4. I have tried updating the
package and created a pull request here:
https://salsa.debian.org/bremner/polymake/mer
On Thu, 20 Sep 2018 18:44:16 + Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:
> Hi Ian,
>
> On Do 20 Sep 2018 16:45:41 CEST, Ian Jackson wrote:
>
> > Mike Gabriel writes ("Re: Bug#909192: mate-desktop-environment:
> > Installing sysvinit-core removes mate-desktop-environment"):
> >> m
upstream version 0.13 does work with Thunderbird 60,
see also https://github.com/swick/mozilla-gnome-keyring/pull/56.
Please consider updating the package instead of removing it.
Cheers,
Lorenz
Hello,
this bug still exists in console-setup version 1.184.
It also makes 'update-initramfs' very noisy, as 'setupcon --save-keyboard
$destination' prints the same 976 lines for each installed kernel version.
Cheers,
Lorenz
Dear Maintainer,
the issue is gone since some days.
In the last days there were several updates in testing that might have
delivered the
fix, e.g. mount, util-linux, mdadm, plymouth. I haven't further analysed it.
works for me ;-)
Originally I intended to post this issue as addition for #8980
Package: src:linux
Version: 4.16.5-1
Severity: important
Dear Maintainer,
I have the same issue on my ThinkPad X220.
After grub, the linux-image-4.16.0-1-amd64 is loading and remains in a state
with black screen and blinking cursor only. After about 2 minutes the boot
continues with the plymouth
Dear Lev,
It seems a fix for this bug was merged into the upstream stable
repository some time ago:
https://github.com/SWI-Prolog/swipl/commit/3923765d56e5
I have an unstable i386 VM where I could reproduce these memory errors
and adding this to the patches resolves it.
Since there is still no n
Thanks! I'm not very familiar with Debian policy, so I can't really comment on
what kind of a dependency it should be. But it does seem inconsistent to have a
"Depends: libgstreamer1.0-0 "but "Recommends: gstreamer1.0-gtk3", given that
both are required to play video.
Do you have the package gstreamer1.0-gtk3 installed? This fixes movie playback
for me. It seems like pdfpc should at least have a 'Recommends' dependency on
it.
You can increase the verbosity of gstreamer in pdfpc by setting the GST_DEBUG
environment variable to, e.g., 4.
Cheers,
Lorenz
created a pull request to for this:
https://github.com/SWI-Prolog/packages-jpl/pull/8
I have tried this on i386 and the package now compiles but make check
then fails with the same errors as in #887155.
Regards,
Benjamin Lorenz
Package: bugs.debian.org
Severity: important
Tags: upstream
Dear Maintainers,
because the kernel logs show clock errors for amdgpu and segfaults in the gnome
shell, I'm not sure which package I have to refer to. Please feel free to ask
for other log files or hardware configurations that might be
On 01/06/2018 08:08 PM, Niko Tyni wrote:
> Running polymake currently fails with
>
> $ polymake
> Can't locate loadable object for module Polymake::Ext in @INC
>
> Apparently this is because it was built with Perl 5.26.0, but
> we've since moved to 5.26.1.
>
> I see two better alternatives:
>
>
Package: pyspread
Version: 1.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
With the latest apt-get upgrade, the spreadsheet canvas of pyspread will
no longer show, instead it's just a white box without the grid. This
makes the pyspread package unusable. The consol
>And why should this be a bug in lxqt-qtplugin?
Feel free to reassign if you know which package is responsible for this; I
have a problem with a plugin in lxqt-panel, but that package hasn't been
upgraded, so i searched the apt logs and found out that the only lxqt
package that has been upgraded is
First patch rewrites the URLs and updates debian/watch, second one
replaces the libxml dependency with expat.
https://libvips.blogspot.ch/2016/09/whats-new-in-84.htmlFrom f48c214aa77cf64adffc71ee81ecee07a3d4475c Mon Sep 17 00:00:00 2001
From: Lorenz Schori
Date: Sat, 9 Sep 2017 16:09:13 +0200
Source: vips
Severity: normal
Dear Maintainer,
A new major version (8.5) is available on the relocated project page:
https://jcupitt.github.io/libvips/
Regrettably the old wiki/website neither mentions the new release nor
redirects users to the new site. That also applies to the old release
dire
n for others or would you rather close it?
Cheers,
Lorenz
(Xwayland) window (e.g. chromium) is active. Are there any plans to support
wayland?
Cheers,
Lorenz
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel:
Package: sympa
Version: 6.1.23~dfsg-2+deb8u1
Severity: normal
Dear Maintainer,
when directly loading the URL of an email in the archive the user is requested
to click the button "I am not a spammer" and after doing that the user is
redirected to the main archiv page of the list instead of the o
lists.)
Could you please fix this error if you can reproduce the error?
Best regards,
Sabine Lorenz
-- System Information:
Debian Release: 8.7
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh link
structions.
src/CMakeFiles/raft.dir/build.make:86: recipe for target
'src/CMakeFiles/raft.dir/allocate.cpp.o' failed
Didn't get a coredump despite them being enabled, but don't have time to figure
out what's going on with that right now, sorry.
Cheers,
Lorenz
[1] https://gi
On 25/08/16 19:59, David Bremner wrote:
> Dominic Hargreaves writes:
>
>>
>> This bug will become RC when the perl package change removing '.' from
>> @INC by default is uploaded to unstable, expected in a week or two.
>>
>> By the way, when preparing this patch I found that the git repository
>>
Awesome - thank you very much! I must confess that I'm not very
proficient in Debian packaging and the package build process. I'll have
to change that some day ;)
Best,
Lorenz
On Mon, 8 Aug 2016, at 18:40, Sylvestre Ledru wrote:
> I think I found the fix. So, don't bother :)
&g
Dear maintainer,
this issue is still present in version 1:3.8.1-8. According to
http://llvm.org/docs/GoldPlugin.html the fix should be quite simple. I'd
really appreciate it if you could bring back LLVMgold.so in 3.8.
Best,
Lorenz
On Sat, 26 Mar 2016 23:10:18 +0100 Steffen Weinhart
in /etc/ldap.conf
Anything I can do to help fix this?
Best,
Lorenz
On Sun, 19 Jul 2015 15:03:53 -0300 Felipe Sateler
wrote:
> On 17 July 2015 at 18:44, Daniel Schepler wrote:
> > On Wed, Jul 15, 2015 at 12:30 PM, Felipe Sateler
> > wrote:
> >>
> >> On 15 Ju
Package: xul-ext-pwdhash
Version: 1.7-13
--- Please enter the report below this line. ---
i also upgraded from iceweasel 38 to 45.2.0esr-1~deb8u1 and found the
pwdhash-addon to be deactivated although depending on the new version of
firefox/iceweasel
as suggested in the previous mail i inves
Package: xul-ext-pwdhash
Version: 1.7-13
--- Please enter the report below this line. ---
i also upgrade from iceweasel 38 to 45.2.0esr-1~deb8u1 and found the
pwdhash-addon to be deactivated although depending on the new version of
firefox/iceweasel
as suggested in the previous mail i invest
Package: dpkg
Version: 1.17.27
--- Please enter the report below this line. ---
i think this bug can be closed because dpkg doesn't have the
--reconfigure option any more. i don't know since which version.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64
De
Package: dpkg
Version: 1.17.27
--- Please enter the report below this line. ---
dpkg -l
lists only installed packages. i did not find out that you would have to
do to get a list of all available packages.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64
Deb
Package: dpkg
Version: 1.17.27
--- Please enter the report below this line. ---
i think this is the same as #30126 which i found to be fixed, since
dpkg-divert puts out the info that directories are not supported.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-am
Package: dpkg
Version: 1.17.27
--- Please enter the report below this line. ---
when i type
dpkg-divert --rename /usr/include/linux
i get
dpkg-divert: error: cannot divert directories
Use --help for help about diverting files.
so i think this is fixed. i also think this the is same as bug #
Yes, it's fixed. Thanks a lot.
Lorenz
Yes, that certainly seems possible as I mentioned in my initial
report. However, I can exclude the possibility of it being a duplicate
of #813687 after the upgrade to mutter 3.18.3.
0):
> failed to set mode: Permission denied [13]
> Mar 01 11:53:03 i10pc82 gnome-session[989]: Window manager warning:
> Configuring CRTC 64 with mode 72 (1920 x 1080 @ 60.00) at position 1920,
> 0 and transform 1 failed
> Mar 01 11:53:03 i10pc82 gnome-session[989]: (gnome-settings-daemon:1069):
> color-plugin-WARNING **: failed to create device: failed to obtain
> org.freedesktop.color-manager.create-device auth
is this in any way helpful? Should it be reassigned to gnome-shell?
Could it be related to #813687? I have a dual-monitor setup if that
makes a difference.
Cheers,
Lorenz
Sounds like a duplicate of #815581 (fixed / pending) to me
Cheers
Lorenz
-display-server" (wayland). Maybe these can be
of help?
Cheers
Lorenz
On Tue, Feb 23, 2016 at 2:35 PM, Lorenz Hübschle-Schneider
wrote:
> Package: xwayland
> Version: 2:1.18.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> sinc
1 - 100 of 233 matches
Mail list logo
