+PzE9OncPIgEzmN1ph9u4dfB90kzl64OjPviL5xcazDTBj5wVUmzks3R6RlhV42
plFZhxs8Mhz2aCXfmlMZYKlDbvVtBEdd55CL/c9u1M5XOwSbpRyHzeqsOUcONgWD
Lz9s4f2pvNmyPT+VDhsZ3SrPJTFd5MB4CCx4fQWEf34DL3NoEsE=
=JnJj
-END PGP SIGNATURE-
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
Package: minissdpd
Version: 1.6.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Looks like bugs #890584 and #901605 are back again. I'm getting lots
of "minissdpd[810]: peer xxx.xxx.xxx.xxx:y is not from a LAN"
messages in my syslog. The "peer" involved is my WiFi
I’ll try that later tonight.-- Ron Murray <r...@rjmx.net>PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761On 24 Oct 2023, at 15:28, Martin-Éric Racine wrote:Next, try what's in Testing.On Tue, Oct 24, 2023 at 10:15 PM Ron Murray wrote:It’s still happening. Currently r
It’s still happening. Currently running version 1:9.4.1-24~deb12u2. …..Ron-- Ron Murray <r...@rjmx.net>PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761On 9 Oct 2023, at 10:02, Martin-Éric Racine wrote:Noted. If that still doesn't fix it, the next step is to try
Package: rsync
Version: 3.2.7-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
Please add support for specifying an SSH port other than 22 for SSH
transfers. The "--port=xxx" option only seems to affect rsync transfers.
- -- System Information:
Debian
Package: dhcpcd-base
Version: 9.4.1-22
Severity: normal
Dear Maintainer,
dhcpcd stops listening on udp port 68 after several days. Still
listening on raw port 17. I've tried re-installing the package and I
still get the same result.
-- System Information:
Debian Release: 12.1
APT prefers
Package: tripwire
Version: 2.4.3.7-4+b9
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
The latest version of tripwire segfaults during a run. I've taken an
strace, but it's over a Gb lond, and still over 100 Mb when tarred and
feathered. I'll try and attach
Package: gm2-13
Version: 13.2.0-4
Severity: important
X-Debbugs-Cc: ron163...@startmail.com
Dear Maintainer,
Since the upgrade from gm2-12 to gm2-13, the link step fails:
/usr/bin/gm2 -fpim -flibs=m2pim,m2cor,m2iso -o topsort_m2 ../topsort.mod
FAILED: topsort_m2
/usr/bin/gm2 -fpim
Package: emacs-common
Version: 1:29.1+1-5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
It looks like Bug #477136 is back again.
I was updating emacs when I got these errors:
Performing actions...
(Reading database ... 2432913 files and
ces.list.d/rjmx.sources': Unable
to parse section data
noprog: command not found
- -
Thus it looks like command-not-found doesn't understand the deb822
format for files in sources.list.
.Ron
- -- System Information:
Debian Release: trixie/sid
APT prefers testing
galternatives could
be modified to fix it, or perhaps a new application is in
order. Another alternative would be to install gnome-control-center at
all times, and provide instructions to use it if needed. (I don't
recommend this: the thing's ugly).
.Ron Murray
- -- System Information:
Debian
Should have said Arch Linux Issue 75727.
On Sun, Oct 16, 2022 at 5:20 PM Ron Lovell wrote:
> Same issue as Arch issue 279267?
>
> --
> James Ronald Lovell
> Huntsville, AL, USA
>
>
--
James Ronald Lovell
Huntsville, AL, USA
Same issue as Arch issue 279267?
--
James Ronald Lovell
Huntsville, AL, USA
patch sets the pinentry mode to "default" when we're decrypting or
signing, which should cause the normal pinentry dialog to be
displayed.
Tags: Patch provided
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
When decrypting or signing a file,
udiskie's "--verbose" mode helped solve this.
You can close this bug now.
Thanks,
.Ron
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
: missing files, aborting
make: *** [debian/rules:13: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
- -------
.Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT polic
---
> write(2, "Software interrupt forced exit: "..., 51Software interrupt forced
> exit: Segmentation Fault
> ) = 51
> exit_group(8) = ?
> +++ exited with 8 +++
.Ron Murray
- --
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
- --
ed
against the behaviour and code of _AC_PROG_CC_STDC_EDITION_TRY where the
analogous variable is ac_cv_prog_cc_c$1 and which does work correctly
out of the box when the default (or explicitly set by CFLAGS) compiler
standard is something earlier than C11 ...
Cheers,
Ron
--- c.m4.orig 2022-0
= /var/lib/gnunet/
GNUNET_DATA_HOME = /var/lib/gnunet/data/
GNUNET_RUNTIME_DIR = /var/run/gnunet/
[arm]
START_SYSTEM_SERVICES = YES
START_USER_SERVICES = NO
OPTIONS = -l /var/log/gnunet/gnunet.log
gnunet starts up fine.
.Ron Murray
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B
rrived a week or two back, so perhaps
the problem lies in that.
Thanks,
.Ron Murray
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.15.khufu (SMP w/8
don't see anything related to
collecting pass phrases for secret keys, but it's possible that I
missed it. Please let me know if that's the case.
.Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_6
You're right, of course.
However, I'm the only user of this box, and I'd never heard of systemd
timers, or even plocate, until yesterday. I certainly don't recall
disabling it. Strange.
Anyway, let's see if it runs tonight, and if it does, we can close this
bug.
Thanks,
.Ron
--
Ron
tive (dead)
Trigger: n/a
Triggers: ● plocate-updatedb.service
We'll see how it goes tonight.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
On Mon, 2022-04-18 at 20:49 +0200, Steinar H. Gunderson wrote:
> On Mon, Apr 18, 2022 at 02:34:22PM -0400, Ron
) in journalctl.
It seems, then, that systemctl isn't running this job for some
reason, but not logging any errors.
.Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel
Yes. Once I've figured out what the problem is, I'll file another bug
report.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
On Sun, 2022-04-17 at 23:27 +0200, Steinar H. Gunderson wrote:
> On Sun, Apr 17, 2022 at 04:39:30PM -0400, Ron Murray wr
Ah.
Sorry, perhaps I wasn’t too clear. Running updatedb manually works fine. I
just had to do it again. I think the only issue is the auto update.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
> On Apr 17, 2022, at 16:14, Steinar H. Gunderson wr
I think the problem is that the cron.daily plocate job isn't being run.
I'd suspect the systemd timer doesn't work, but I'm not sure. I'll hack
the cron.daily/plocate script to save some diagnostic information, and
perhaps that'll help.
Thanks,
.Ron
--
Ron Murray
PGP Fingerprint: 4D99
Package: caffeine
Version: 2.9.10-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
caffeine does't come up when I try to start it. Here's what happens
when I try to start it from the command line:
- ---
ron@khufu:~$ caffeine
Gtk-Message
-updatedb.timer file in
/lib/systemd/system/plocate-updatedb.timer, echoed in other places.
I also note that there's still a 'locate' in /etc/cron.daily, which
runs '/usr/bin/updatedb.findutils'. Should these be still on the
sysytem? Could they be interfering with plocate?
Thanks,
.Ron
I have the same problem here. Removing lmms and fluidsynth-dssi made no
difference.
I did a debug build and ran it with gdb. The resullt is attached.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
Copyright (C
Thanks for your work. I’m able to activate containers from within a script
run at boot time. The update did the trick.
Ron.
Ron Fox
Senior Scientist
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824, USA
Tel. 517-908-7349
Email: f
We just got it Friday I'll test this tomorrow thanks.
Ron
On Feb 27, 2022 01:54, Nilesh Patra wrote:
[EXTERNAL] This email originated from outside of FRIB
On Wed, Feb 23, 2022 at 11:50:30PM +, Fox, Ron wrote:
> Thank you we'll give it a try as soon as it migrates out to our inter
Thank you we'll give it a try as soon as it migrates out to our internal
mirrors.
RF
On Feb 23, 2022 14:12, Nilesh Patra wrote:
[EXTERNAL] This email originated from outside of FRIB
On Wed, 16 Feb 2022 12:58:57 + "Fox, Ron" wrote:
> On Debian 11 note this comes from de
ve
fixed the problem.
You can probably close this bug.
Thanks,
.Ron
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
signature.asc
Description: This is a digitally signed message part
out eventually, so importing keys is still
(vaguely) possible, so I'm leaving this report marked as "normal".
Thanks,
.Ron
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architect
sleep 3 # Let the port manager start.
}
Note that I have attempted to do the same thing after converting the container
image to a .sif file and that too failed with essentially the same result.
Thank you for any help you might be able to provide. I'd be happy to provide any
additional information.
Ron.
portmanager
Description: portmanager
Hi Guido,
On Wed, Nov 03, 2021 at 07:15:37PM +0100, Guido Günther wrote:
> Hi Ron,
>
> Sorry for the broken boot. That's always annoying.
Thanks for looking at the details. I filed these bugs because even
though I can step around the problem in the permutation that involves
so
On Tue, 02 Nov 2021 15:34:01 +0100 Michael Biebl wrote:
> I tried to explain this to Ron on IRC, but he decided to ignore my advice.
Oh Please Michael, now you're just sounding like a child whose lolly has
fallen in the dirt ...
I did run the issue with (some) socket units and circu
of the problem stuck to each of them!
Cheers,
Ron
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads)
Loc
o Bullseye upgrades).
As a side note to all that, the TimeoutSec=180 in ifupdown-pre
is a bit misleading, as udevadm settle will itself time out in
120 seconds unless it is told to do otherwise.
Cheers,
Ron
As a postscript for anyone who might be interested, here is the
details of the parti
Problem was caused by there being no entry for "bookworm" in
/usr/share/live/build/data/debian-cd. Fixed by
# cd /usr/share/live/build/data/debian-cd
# ln -s squeeze bookworm
This bug can now be closed.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
Package: tripwire
Version: 2.4.3.7-3+b3
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
I've been using tripwire for several years now, and never had troubles
with it until this morning (perhaps [not] coincidentally with
pts20210124.1
ii vim-tiny 2:8.2.2434-3
Cheers,
Ron
On Tue, Aug 03, 2021 at 10:08:42PM +0200, Aurelien Jarno wrote:
> On 2021-08-01 00:05, Ron wrote:
> >
> > Unpacking openssh-sftp-server (1:8.4p1-5) over (1:7.9p1-10+deb10u2) ...
> > Preparing to unpack .../openssh-client_1%3a8.4p1-5_amd64.deb ...
> > Unpacking openssh
is included below - I'm not sure
offhand exactly how the libc restart logic is coded, but at first blush
I'd note the new openssh-server is unpacked but not set up at the time
the libc service restart takes place ...
Cheers,
Ron
Unpacking openssh-sftp-server (1:8.4p1-5) over (1:7.9p1-10+deb10u2
abort the encoding as a whole, or skip that particular
encode, or perhaps ask the user?
Thanks,
.....Ron
- -- System Information:
Debian Release: 11.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Never mind. I thought I'd point out a deficiency, but you seem to be
more interested in how I found it than the deficiency itself.
On Sun, 2021-04-18 at 18:32 +0200, Yves-Alexis Perez wrote:
> On Fri, 2021-04-02 at 00:57 -0400, Ron Murray wrote:
> >
> > I noticed &quo
it myself.
Thanks,
.Ron
On Wed, 2021-04-07 at 22:07 +0200, Chris Hofstaedtler wrote:
Hello Ron,
* Ron Murray [210407 20:05]:
> I'm not going to supply a patch because I feel that this should be
> the decision of the maintainer.
There is no maintainer.
> PS FFS, this bug is *1
parser generator files.
2. Only allow 'none' to be selected as the parser generator when using
c++.
I'm not going to supply a patch because I feel that this should be
the decision of the maintainer.
.Ron
PS FFS, this bug is *18* *years* *old*.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317
Package: xfce4-appfinder
Version: 4.16.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
I noticed "Application Finder" in a Debian Live build I'd made, and
wondered why I'd never seen it on my normal Debian box. So I tried to
add it with xfce4's "Add New
On Mon, Nov 23, 2020 at 07:59:52PM +0100, Diederik de Haas wrote:
> On Sat, 24 Jan 2015 20:46:02 +1030 Ron wrote:
> > Tags: patch
> >
> > And if reportbug --attach actually worked, the git-format-patch export
> > should be included in this mail. There's a full
e a more long-term viable way forward on
this one to you? It is the nature of this game for people's needs
with packages like this one to be cyclical, and I'll guess it will
be no different for you once your immediate need is scratched as
well.
Cheers,
Ron
Package: live-build
Version: 1:20191221
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
Build for bullseye with security=false works fine.
Build for security=true fails with:
> E: The repository 'http://security.debian.org bullseye/updates Release'
> does not
, if
at all, to
make someone aware of it is not by creating logrotate failures.
On Tuesday, April 14, 2020, 10:45:15 AM GMT+1, Sylvestre Ledru
wrote:
Hello
Thanks for your patch!
Le 14/04/2020 à 11:30, Ron Varburg a écrit :
> Package: fail2ban
> Version: 0.10.2-2.1
> Severit
Update 4.6.3-3 adds a depends for python3-distutils. Thank for the quick
fix!
--
James Ronald Lovell
Huntsville, AL, USA
I checked a couple of other distros I run. In Arch Linux distutils/util.py
is provided by the base "python" pkg. In openSUSE Tumbleweed it is provided
by python3-base. So among my installations, Debian Buster and Sid are the
odd ducks in that they require an optional pkg installation to provide
Probably "what's different" is just that I decided to test qtconsole on by
Sid guest VM. I would normally run qtconsole on my host Buster system,
where jupyter_core/paths.py does not import from distutils.util, and
besides python3-distutils is already installed since it's needed by other
things I
With the latest python3-talloc update, the upgrade to python3 3.8.2
completed on my Sid host. I temporarily removed python3-distutils to verify
the situation has not changed: "juypter qtconsole" still requires
python3-distutils, and nothing brought it in as a dependency.
--
James Ronald Lovell
> Should I have python3 installed?
Meant: Should I have python3-all installed?
--
James Ronald Lovell
Huntsville, AL, USA
Package: python3-jupyter-core
Version: 4.6.3-2
Severity: important
After recent updates to the jupyter packages and for the Python
3.8 tranision in Sid, I decided to give qtconsole a spin just to
see how it's working. It's not able to load:
$ jupyter qtconsole
Traceback (most recent call last):
Package: python3-pyqt5
Version: 5.13.2+dfsg-1
Severity: important
Currently in Sid the python3-pyqt5 package has deps:
libqt5gui5 (>= 5.1.0)
libqt5gui5 (>= 5.12.2) | libqt5qui5-gles (>= 5.12.2)
I recently performed the tranition from libqt5gui5 to the -gles variant
just to try it out. I
I noticed that libopenmpi-dev 4.0.2-3 now depends on libevent-dev. Thanks!
--
James Ronald Lovell
Huntsville, AL, USA
Wow, that was fast! The Open MPI 4.0.2-3 updates appear to resolve the
issue. I say "appear" because I can't really reproduce an upgrade from
3.1.3 to 4.0.2-3.
Upgrading from 4.0.2-2 to 4.0.2-3 worked fine.
In order to test a new installation of Open MPI, I removed all Open MPI and
OpenCoarrays
Package: libopenmpi-dev
Version: 4.0.2-2
Severity: normal
While testing the newly upgraded Open MPI 4.0.2-2 packages in Sid I
found that builds with mpicc etc. will be expecting libevent.so and
libevent_pthreads.so, which are provided by libevent-dev.
Starting with 4.0.x, shouldn't
Package: libopenmpi-dev
Version: 4.0.2-2
Severity: important
Dear Maintainer,
The upgrade of Open MPI components from 3.1.3 to 4.0.2-2 did not
complete successfully. During upgrade I got these warnings:
Setting up libopenmpi-dev:amd64 (4.0.2-2) ...
update-alternatives: warning: forcing
Although I can no longer install flang-7 on my Sid host since the upgrades
to LLVM 8 and now non-default LLVM 9, the general situation described still
applies to libomp-9-dev. If a user compiles with the -fopenmp= option
(instead of simply -fopenmp), it's much better if doesn't change from
On 7/30/19 4:14 PM, Andreas Beckmann wrote:
> Hi Ron,
>
> On 21/07/2019 05.42, Ron Murray wrote:
>> On upgrade to buster, sendmail upgrade failed with this message:
>>
>>> start-stop-daemon: matching only on non-root pidfile
>>> /var/run/sendmail/mt
Patrice, thanks for filing the bug report. I was just looking at that bug
myself. The definition of g_tclextlib at line 41 is in new code added since
the version 4.2.2 that's in Buster.
I'm NOT a Tcl programmer or Modules guru. But is "prefix" something that
should be compiled into the modules at
Sorry, that comment was intended for Bug #933782. Pls disregard.
On Sat, Aug 3, 2019 at 9:13 AM Ron Lovell wrote:
> Patrice, thanks for filing the bug report. I was just looking at that bug
> myself. The definition of g_tclextlib at line 41 is in new code added
> since the version 4.2
Patrice, thanks for filing the bug report. I was just looking at that bug
myself. The definition of g_tclextlib at line 41 is in new code added since
the version 4.2.2 that's in Buster.
I'm NOT a Tcl programmer or Modules guru. But is "prefix" something that
should be compiled into the modules at
/mta/sendmail.pid
as well.
Note:
Although probably not a sendmail problem (start-stop daemon?), it
might be advisable to re-word the error message. "matching only on
non-root pidfile xxx.pid is insecure" is rather cryptic, and does not
point the way to fixing the problem.
.Ron Murray
-
If anyone happened to have used my workaround of installed a temporary
symlink flang-mod-33 -> flang-mode-34, be sure the remove that symlink
before doing the update.
--
James Ronald Lovell
Huntsville, AL, USA
Yep, update 20190329-2 fixes the issue on my system. Thanks for the great
work!
--
James Ronald Lovell
Huntsville, AL, USA
Another workaround is to install a symlink:
/usr/lib/x86_64-linux-gnu/fortran/flang-mod-33 -> flang-mod-34
That's easier since it doesn't require changing my build specs.
--
James Ronald Lovell
Huntsville, AL, USA
Package: flang-7
Version: 20190329-1
Severity: important
Dear Maintainer,
A program which uses iso_fortran_env fails to compile using the
20190329-1 build of flang-7 because flang cannot find the module:
flang -Ifortran_characters@exe -I. -I.. -Xclang -fcolor-diagnostics -pipe
I just filed Bug #927291 against fuse3 to suggest making fuse and fuse3
co-installable. I recommend the Arch Linux approach of adding a fuse-common
file to supply mount.fuse and fuse.conf for both fuse and fuse3.
--
James Ronald Lovell
Huntsville, AL, USA
In the leading paragraph, that should have been:
Currently on Buster and Sid the installation of fuse3 requires removal of
fuse.
--
James Ronald Lovell
Huntsville, AL, USA
Package: fuse3
Version: 3.4.1-1
Severity: wishlist
Dear Maintainer,
Currently on Buster and Sid the installation of fuse requires removal of
fuse. It would be better if they were co-installable, as is the case on
other distros I run.
Currently pkg fuse3 has to have a "breaks" on fuse because
Apologies, that msg was intended for #912528. Pls disregard.
Pls see Bug #927221 against gvfs-fuse, in particular Mr. Simon McVittie's
comments. For fuse and fuse3 to be co-installable, changes need to be made
to handle the file conflicts for mount.fuse, fusermount, and fuse.conf.
Pls see my comments on how Arch and openSUSE have handled that so that
I really should learn to look before I speak. I just checked Buster, and
ntfs-3g and exfat-fuse don't require a version of fuse and should coexist
with fuse3. (I have exfat-fuse installed with fuse3 on Sid). Current
gvfs-fuse has a versioned requirement; the update to close #927221 changes
that to
Several of the dependent packages including ones you listed could coexist
with fuse3 if the fuse3 package provided a versioned "fuse" instead of the
unversioned "fuse" it provides in 3.4.1-1. Pls see Bug #927221, where
gvfs-fuse is changed to require simply "fuse", but that's the hard way to
do
Correction: On Tumbleweed, pkg fuse3 supplies mount.fuse3, not mount.fuse.
On Tue, Apr 16, 2019 at 9:14 PM Ron Lovell wrote:
> Wow, that was quick.
>
> As a sanity check, I took a look at my Arch Linux and openSUSE Tumbleweed
> installations. Each has both fuse[2] and fuse3 install
Wow, that was quick.
As a sanity check, I took a look at my Arch Linux and openSUSE Tumbleweed
installations. Each has both fuse[2] and fuse3 installed, each has the
corresponding library installed.
For Arch, a fuse-common pkg supplies /usr/bin/mount.fuse, which happens to
be dyn linked to
Then I know I can test fuse-
exfat, the existing sshfs 2, and set up a Samba server.
Thanks for your very informative replay.
Best regards,
Ron
I should have mentioned that I've sidestepped the whole topic of
co-installability of pkgs fuse and fuse3. Despite closure of # 912528, on
my Sid system fuse3 3.4.1-1 has an explicit "breaks" on pkg fuse. At least,
that appears to be why installing fuse3 requires removing fuse. I could be
missing
Package: gvfs-fuse
Version: 1.38.1-3
Severity: important
Dear Maintainer,
Basically this regards the transition from fuse to fuse3, my primary
motivation being to make the (Debian) world safe for a modern sshfs
(3.5+). As others have pointed out (g.e. Bug #918984), trying to replace
fuse with
Or alternatively have /usr/lib//libomp.so point to libomp5.so so it
won't have to changed with LLVM version. The libomp5.so symlink is already
maintained by libomp-dev, so it will be updated with the libomp-dev release
updates.
--
James Ronald Lovell
Huntsville, AL, USA
On Wed, Mar 06, 2019 at 03:15:40AM +0100, Elimar Riesebieter wrote:
> Hi all,
>
> did someone checked
>
> https://git.xiph.org/?p=libao.git;a=commit;h=d5221655dfd1a2156aa6be83b5aadea7c1e0f5bd
>
You mean the commit which has :?
authorRon Sat, 13 Jan 2018 09:49:20
Package: libomp-7-dev
Version: 1:7.0.1-6
Severity: wishlist
Dear Maintainer,
While testing flang-7 for OpenMP programs, I noticed that 'flang
-fopenmp=libomp' doesn't know to link libomp. (clang -fopenmp=libomp
has no problem.) It's easy enough to work around that by using linker
option
Package: wnpp
Severity: wishlist
Owner: Ron
* Package name: libopusenc
Version : 0.2.1
Upstream Author : Xiph.Org
* URL : http://opus-codec.org/development/
* License : BSD
Programming Lang: C
Description : High-level API for encoding Ogg Opus audio
My MPI issues were resolved by 3.1.2-2.
Great work, guys.
--
James Ronald Lovell
Huntsville, AL, USA
The libpmix2 update causes my MPI programs compiled with
gcc/gfortran/clang to fail at runtime with the same messages.
--
James Ronald Lovell
Source: mesa
Version: 18.2.8-1
Severity: normal
Dear Maintainer,
After upgrading to the Mesa 18.2.8-1 packages, glxinfo(1) still reports
the previous version:
lovelld@ron5sid:~$ glxinfo | grep OpenGL
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: SVGA3D; build: RELEASE; LLVM;
package to see if it helped. It did not.
Currentlt the problem can be fixed by uninstalling
xserver-xorg-core and its dependencies (uninstall any nvidia drivers
first), check that the directory /usr/lib/xorg/modules/extensions/ is
non-existent, or at least empty. Then reinstall xserver-xorg-core an
May 2018.
Ron
Oops. Last one should be:
[ -d path ] && [ ! -L path ]
--
James Ronald Lovell
I still remember the first time that one bit me: "[ -e path]" fails if path
is a dead symlink. There are other pitfalls testing symlinks. Some idioms
I use:
Does path exist?
[ -e path ] || [ -L path ]
Is path really a regular file?
[ -f path ] && [ ! -L path ]
A directory?
[ -d path ] && [ !
The delays and warning messages for my MPI programs on Sid were resolved by
the workaround fix in libpsm2 11.2.68-2. You can close this one as far as
I'm concerned.
Thanks,
Ron
--
James Ronald Lovell
Huntsville, AL, USA
A distributed system is one in which the failure of a computer you
didn't
That should be libpsm2-2 11.2.68-1, not .78.
On Mon, Oct 8, 2018 at 1:39 PM Ron Lovell wrote:
> Alastair,
>
> Thanks for the quick update. I see that I upgraded to libpsm2-2 11.2.78-1
> on 01 Oct 2018, so the timing fits.
>
> Thanks,
> Ron
> --
> James Ronald Lo
1 - 100 of 1289 matches
Mail list logo
