output) using /bin/dash.
# -Ian! D. Allen - idal...@idallen.ca - www.idallen.com
a=''
{
echo correct $a # correct empty output line
echo correct $a$a # correct empty output line
echo correct $a$a$a # correct empty output line
echo XwrongX
Public bug reported:
Shouldn't these give the same results in dash, i.e. "/root"?
They give the same output in bash.
$ dash
$ var=~root
$ echo "$var"
/root
$ export var=~root
$ echo "$var"
~root
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: dash 0.5.10.2-6
ProcVersionSignature: Ubuntu
Public bug reported:
The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname. Details follow:
Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):
if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
I am not arguing about the behaviour, which is correct and apparently hasn't
changed.
I'm complaining about the unannounced change in message from "is uptodate" to
"is newer".
Three problems:
1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is
Public bug reported:
rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be "is
Public bug reported:
I'm running Ubuntu 20.04 on my desktop. I SSH into my laptop running
22.04:
desktop$ ssh laptop
laptop$ sudo -sE
laptop#
If I now run most any X11 client applications (e.g. xload, xterm)
using this laptop SSH command line, they correctly open windows on my
The laptop is logged in and running Wayland: /usr/bin/Xwayland :0
My desktop is running X11: /usr/lib/xorg/Xorg -nolisten tcp :0
When I SSH into the laptop from the desktop, my DISPLAY is set to
"localhost:10".
When I start an xterm in the SSH session (running xterm on the laptop),
the xterm
I knew nothing about your SRU process until now; the man page for
`ubuntu-bug` makes no mention of it. Who fills out the SRU Bug Template
and makes the fix actually happen? Is there anything more I need to do
here?
--
You received this bug notification because you are a member of Ubuntu
Touch
The problem was marked as Confirmed by Paride back on March 17.
Then today it gets marked Invalid.
Then later today it gets marked Confirmed again.
I don't understand your process.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Your incorrect statement "seems the issue does not actually exist" is
wrong. I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release. I gave you the link to the upstream bug that Wayne
fixed over two years ago. This two-year-old bug does exist and it
exists in your
I'm not familiar with your SRU process, debdiff, dput, the "General
Requirements" document, the "security policy document", or your upload
process, and I'm not into learning about all that and filling out your
special form and making your special upload when there is no guarantee
that Ubuntu will
** Description changed:
rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be
Hey Ubuntu - I see now that this bug was reported and fixed at source in
September 2020, over two years ago. The real bug is: "Why didn't Ubuntu
apply the fix to the supported Ubuntu releases?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Your incorrect statement "seems the issue does not actually exist" is
wrong. I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release. You were also given the link to the upstream bug
that Wayne fixed over two years ago. This two-year-old bug does exist
and it exists
14 matches
Mail list logo
