y to upgrade glibc to get the issue fixed.
Installation of util-linux 2.40.1-1 (and accompanied libmount1,
libuuid1, libblkid1, libsmartcols1 of the same version) solves
the problem, output of "last" is correct.
Thank you, guys!
--
Eugene Berdnikov
: Shared libraries
--
Eugene Berdnikov
lt/exim4
%
As a result, definitions from generated /etc/default/exim are ignored.
--
Eugene Berdnikov
- ( sign_req "$crt_type" "$name" batch ) || {
+ ( sign_req "$crt_type" "$name" ${ssl_batch+ batch} ) || {
rm -f "$req_out" "$key_out"
die "Failed to sign '$name' - See error messages above for
details."
}
--
Eugene Berdnikov
to absence of @.service unit file.
If unit files ssh.socket and ssh@.service are taken from old package,
all works right as expected.
--
Eugene Berdnikov
Hi.
On Fri, Oct 22, 2021 at 01:44:38AM +0200, Florian Schlichting wrote:
> On Thu, Oct 21, 2021 at 04:25:28PM +0300, Eugene Berdnikov wrote:
> > Hi Florian.
> >
> > On Thu, Oct 21, 2021 at 03:11:41PM +0200, Florian Schlichting wrote:
> > > I've just upl
amd64GRand Unified Bootloader (Legacy
version)
ii grub-common2.04-20 amd64GRand Unified Bootloader (common
files)
ii libc6-i386 2.33-1 amd64GNU C Library: 32-bit shared
libraries for AMD64
Debian version: Debian GNU/Linux bookworm/sid (64bit)
--
Eugene Berdnikov
of package for download?
--
Eugene Berdnikov
%\0\1\0", iov_len=4}, {iov_base=NULL, iov_len=0},
{iov_base="", iov_len=0}], 3) = 4
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily
unavailable)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV +++
I'll return to 64-bit workstation in several hours.
--
Eugene Berdnikov
Do you have an Xpdf*font: resource (or something similar) set on your
> display?
% xrdb -query | fgrep -i xpdf
Xpdf*fileFilterStyle: filter_hidden_files
It is definitely loaded from /etc/X11/Xresources/xpdf
(part of Debian xpdf package).
--
Eugene Berdnikov
ym:amd64 1:1.2.0-1
amd64debug symbols for libxt6
ii libxm4:amd64 2.3.8-3
amd64Motif - X/Motif shared library
ii libxm4-dbgsym:amd64 2.3.8-3
amd64debug symbols for libxm4
ii libxt6:amd64 1:1.2.0-1
amd64X11 toolkit intrinsics library
% uname -rv
5.8.0-2-amd64 #1 SMP Debian 5.8.10-1 (2020-09-19)
--
Eugene Berdnikov
libgnutls30:amd64 3.7.2-2 amd64
ii libgssapi-krb5-2:amd641.18.3-7amd64
ii libldap-2.4-2:amd64 2.4.59+dfsg-1 amd64
ii libltdl7:amd642.4.6-15amd64
ii libnetfilter-conntrack3:amd64 1.0.8-3 amd64
ii libnettle8:amd64 3.7.3-1 amd64
ii libpam0g:amd641.4.0-10amd64
ii libsasl2-2:amd64 2.1.27+dfsg-2.1 amd64
ii libstdc++6:amd64 11.2.0-7amd64
ii libsystemd0:amd64 247.9-1 amd64
ii libtdb1:amd64 1.3.18-2amd64
ii libxml2:amd64 2.9.12+dfsg-5 amd64
ii logrotate 3.18.1-2amd64
ii lsb-base 11.1.0 all
ii netbase 6.3 all
ii squid-common 5.1-2 all
ii squid-dbgsym 5.1-2 amd64
--
Eugene Berdnikov
t
(for arch:amd64, please). I can provide access to my LXC environment:
just send me your ssh public key, and I'll create an entry for you.
> Just a small correction, I see you mentioned lchown, but the issue is
> related to lchmod.
Yes, it should be read "lchown" (lchmod was mentioned by mistake).
--
Eugene Berdnikov
d new releases to
> backports. I also think that there's a chance rsync's upstream solves
> the new regression soon (if confirmed), which would deem the version
> bump unneeded.
>
> What do you think?
OK, I expressed my thoughts, technical problem is clear, so
it's left for you and upstream to find the best and right solution.
Thank you for support, Samuel.
--
Eugene Berdnikov
oblem (and should not be a problem) if binary API
is compatible and all package dependences are correct.
--
Eugene Berdnikov
olves the problem.
I suspect that lchmod() function appears in libc6-2.31 (or in some other
library), but dependency list for rsync mentions "libc6 (>= 2.15)".
Probably it should be corrected.
--
Eugene Berdnikov
Hello.
I confirm the existance of this bug in 1.1.20001007-8.1,
in particular for xfonts-bolkhov-misc package.
Rollback to 1.1.20001007-8 fixes the issue.
--
Eugene Berdnikov
pn zenity
Versions of packages geeqie suggests:
pn geeqie-dbg
pn gimp
pn libjpeg-progs
pn ufraw
ii xpaint 2.9.1.4-3.2+b1
-- no debconf information
--
Eugene Berdnikov
Hi.
On Wed, Jun 03, 2020 at 02:01:33PM +0200, Benedikt Spranger wrote:
> Hi,
>
> are there any updates or is more help needed?
Unfortunately, this package seems to be not maintained.
--
Eugene Berdnikov
I can't start even a priveleged container (under root).
Kernel: 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux
Problem was solved by downgrade to lxc/liblxc1 1:3.1.0+really3.0.3-8.
Example of debug log in attachement.
--
Eugene Berdnikov
lxc-start i
ar/log/dpkg.log, those lines
2018-10-25 13:06:19 status half-installed syslog-ng:all 3.13.2-4.1
2018-10-25 13:06:20 status unpacked syslog-ng:all 3.13.2-5
mean that version 3.13.2-4.1 was upgraded to 3.13.2-5.
>--
>Kokan
>On Wed, 14 Nov 2018 at 21:21 Eugene Berdnikov <
l
blocks until entropy is collected by kernel from device drivers.
Previous versions of syslog-ng do not hang.
--
Eugene Berdnikov
Hi, Bernard.
> On Mon, Jul 09, 2018 at 05:41:45PM +0300, Eugene Berdnikov wrote:
> I built probematic grub-legacy 0.97-73 debian package with you patch,
Qualification: built with gcc-7.3.0 and gcc-8.1.0 compilers.
Tested run of /usr/sbin/grub for both, MBR installation + boot for
much!
Waiting for updated version in Debian repository.
--
Eugene Berdnikov
egfaults are on amd64 and i386 platforms, and also in 0.97-72+b1.
Downgrade to grub-legacy 0.97-72 resolves the problem.
--
Eugene Berdnikov
d, SOL_SOCKET, SO_BINDTODEVICE,
device, strlen(device)+1);
disable_capability_raw();
if (rc == -1) {
--
Eugene Berdnikov
> > Expunge Both
> >
> > Channel is_spam
> > Master :rdtex:"is_spam"
> > Slave :local:"Mail/is_spam"
> >
> Master :rdtex:"is_spam"
> Slave :local:"is_spam"
>
> > Expunge Both
Yes! It works correctly with both boxes.
Hope this wrapper bug be fixed in some future.
Thank you very much, Oswald.
--
Eugene Berdnikov
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Fri, Feb 07, 2014 at 08:15:39AM +0100, Oswald Buddenhagen wrote:
> On Fri, Feb 07, 2014 at 10:54:12AM +0400, Eugene Berdnikov wrote:
> > On Wed, Feb 05, 2014 at 12:44:01PM +0100, Oswald Buddenhagen wrote:
> > > this appears to be an upstream bug in the compatibility wrapper
"isync -w" from 1.1.0-1 package.
Resultimg .mbsyncrc does not contain dots in file paths.
However, running "mbsync -a" on it gives the same result
(errors messages about broken file paths).
Change paths in .mbsyncrc to absolute does not help.
--
Eugene Berdnikov
wever, there are numerous legacy configurations around a world,
they should be kept reliable as far as possible...
--
Eugene Berdnikov
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi, Laurence.
On Tue, Aug 06, 2013 at 10:55:10AM -0400, Laurence J. Lane wrote:
> tag 718810 moreinfo
> severity 718810 normal
> thanks
>
> On Tue, Aug 6, 2013 at 12:46 AM, Eugene Berdnikov wrote:
>
> > I have such behaviour on several hosts running debian/testing.
&g
On Mon, Aug 05, 2013 at 05:06:07PM -0400, Laurence J. Lane wrote:
> That doesn't happen on my systems, but I'll look into it.
I have such behaviour on several hosts running debian/testing.
Downgrade to iptables-1.4.14 solves the problem.
--
Eugene Berdnikov
--
To UNSUBSCR
Package: iptables
Version: 1.4.19.1-1
Severity: important
Justification: critical
Dear Maintainer,
utility "iptables-save" from package 1.4.19.1-1 is broken:
it does not list states for module "state" (keyword "--state"
and its value are missing), so saved configuration
is NOT loadable via iptable
6)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash
--
Eugene Berdnikov
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ozen for a reason and thawing often results in new freeze again.
Freezing may be caused by the DNS failure or some other result of
network inaccessibility. It's good if such mail takes chance to be
delivered, and IMHO there is no more trouble if some broken mail
became frozen again.
Hi, MartМn.
The fix for an UDP timeout handling bug is in a patch below.
It was compiled with lzo1 and verified on Debian/testing.
Version of VTUN was incremented to 3.0.2.
In next mail I'll return to the discussion and answer questions.
--
Eugene Berd
On Wed, Oct 17, 2007 at 10:57:19AM -0300, MartМn Ferrari wrote:
> On 10/17/07, Eugene Berdnikov <[EMAIL PROTECTED]> wrote:
> > Where is 3.01? Page http://vtun.sourceforge.net/download.html have only
> > references for 3.0.0, that's why I did not submit this patch again.
be able to generate a set of patches from 301.
Where is 3.01? Page http://vtun.sourceforge.net/download.html have only
references for 3.0.0, that's why I did not submit this patch again.
--
Eugene Berdnikov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
38 matches
Mail list logo
