[Touch-packages] [Bug 1989545] [NEW] ubuntu-bug fails when run via remote SSH login
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 desktop X11 display, not on my laptop, using the DISPLAY variable set to localhost:10.0. But ubuntu-bug does not do this when I run it on the laptop: laptop# ubuntu-bug /etc/network/if-up.d/resolved At this point, the laptop display incorrectly has the apport X11 window open. The apport window does not open on my desktop, like any other X11 application would. It appears to ignore my DISPLAY variable. If I go over to the laptop and try to continue with the bug report, everything falls apart when it tries to start up a web browser. I get all these error messages on my SSH terminal screen: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): not a directory update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": permission denied /home/username/Music was removed, reassigning MUSIC to homedir X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. Error: cannot open display: localhost:10.0 X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. If ubuntu-bug cannot work over SSH with DISPLAY=localhost:10.0, it should detect this and not even try. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 02:33:18 2022 InstallationDate: Installed on 2020-09-08 (735 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to jammy on 2022-04-04 (162 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989545 Title: ubuntu-bug fails when run via remote SSH login Status in apport package in Ubuntu: New Bug description: 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 desktop X11 display, not on my laptop, using the DISPLAY variable set to localhost:10.0. But ubuntu-bug does not do this when I run it on the laptop: laptop# ubuntu-bug /etc/network/if-up.d/resolved At this point, the laptop display incorrectly has the apport X11 window open. The apport window does not open on my desktop, like any other X11 application would. It appears to ignore my DISPLAY variable. If I go over to the laptop and try to continue with the bug report, everything falls apart when it tries to start up a web browser. I get all these error messages on my SSH terminal screen: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): not a directory update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": permission denied /home/username/Music was removed, reassigning MUSIC to homedir X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. Error: cannot open display: localhost:10.0 X11 connection rejected because of
[Touch-packages] [Bug 1989545] Re: ubuntu-bug fails when run via remote SSH login
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 window opens correctly on the desktop X11, not on the laptop. Inside that xterm, when I type "ubuntu-bug" (running ubuntu-bug on the laptop), ubuntu-bug incorrectly opens a window on the laptop, not on the desktop. Typing "/usr/share/apport/apport-gtk alskdjflkj" also incorrectly opens a window on the laptop, not the desktop. I don't have /usr/share/apport/apport-kde installed, but I could install it and see what happens if that would be helpful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989545 Title: ubuntu-bug fails when run via remote SSH login Status in apport package in Ubuntu: New Bug description: 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 desktop X11 display, not on my laptop, using the DISPLAY variable set to localhost:10.0. But ubuntu-bug does not do this when I run it on the laptop: laptop# ubuntu-bug /etc/network/if-up.d/resolved At this point, the laptop display incorrectly has the apport X11 window open. The apport window does not open on my desktop, like any other X11 application would. It appears to ignore my DISPLAY variable. If I go over to the laptop and try to continue with the bug report, everything falls apart when it tries to start up a web browser. I get all these error messages on my SSH terminal screen: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): not a directory update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": permission denied /home/username/Music was removed, reassigning MUSIC to homedir X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. Error: cannot open display: localhost:10.0 X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. If ubuntu-bug cannot work over SSH with DISPLAY=localhost:10.0, it should detect this and not even try. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 02:33:18 2022 InstallationDate: Installed on 2020-09-08 (735 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to jammy on 2022-04-04 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1989545/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
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 is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Confirmed Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
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 in your most recent Ubuntu 22.04.1 LTS release. Here's another way to show the bug: $ touch foo $ rsync --update --info=skip foo foo foo is newer Obviously a file should not be listed as newer than itself. This rsync is broken. The real bug appears to be that Ubuntu is shipping a broken two-year-old year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't update it to get rid of the bug. All my scripts that depend on an accurate "is newer" indicator from rsync are broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Invalid Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
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 most recent Ubuntu 22.04.1 LTS release. Here's another way to show the bug: $ touch foo $ rsync --update --info=skip foo foo foo is newer Obviously a file should not be listed as newer than itself. This rsync is broken. The real bug appears to be that Ubuntu is shipping a broken two-year-old year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't update it to get rid of the bug. I've added a comment to the github bug number 98 warning people about the broken Ubuntu LTS. All my scripts that depend on an accurate "is newer" indicator from rsync are broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Invalid Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
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 to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Confirmed Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
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 seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Confirmed Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
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 actually fix the problem. If all the info you need for your SRU process isn't already in this bug report (or in the bug report upstream linked above), I don't know what else to say. I certainly don't have the experience to answer "Where problems could occur" in a Ubuntu package management context, other than to say the obvious "people may have already written scripts that depend on the buggy behaviour". You're already running a fixed version of rsync in Kinetic, so at some level someone at Ubuntu already approved of a much more modern rsync (3.2.5 was released August 14 2022) -- please use it. I've documented the bug; someone else found the upstream fix; your Ubuntu internals of adopting the fix are more reading than I want to do. I will download the current source and update my own rsync -- I know how to do that and I know it will solve the problem for me. I hope Ubuntu solves the problem for everyone else. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Confirmed Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
** 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 "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. + + $ touch foo + $ rsync --update --info=skip foo foo + foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. + + Obviously a file should not be listed as newer than itself. Another + way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** 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 "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. + The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Unknown Status in rsync package in Ubuntu: Confirmed Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file c
[Touch-packages] [Bug 1908025] [NEW] export var=~root does not expand ~root to /root
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 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 00:14:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (67 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1908025 Title: export var=~root does not expand ~root to /root Status in dash package in Ubuntu: New Bug description: 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 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 00:14:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-07 (67 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1908025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958005] [NEW] rsyslogd mishandles startswith_i against $programname
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
stop
}
Restart rsyslog:
# /etc/init.d/rsyslog restart
Run these four tests:
$ logger -t 'test' "This is: test"
$ logger -t 'foo' "This is: foo"
$ logger -t 'FOO' "This is: FOO"
$ logger -t '/junk' "This is /junk"
Expected and correct result:
The file /var/log/syslog contains three lines (correct):
Jan 14 23:08:09 ubuntu20 test: This is: test
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk
The file /var/log/idallen-cron.log contains just one line (correct):
Jan 14 23:08:09 ubuntu20 foo: This is: foo
Now make this change: In the 10-idallen.conf file change "startswith"
to "startswith_i". Restart rsyslog. Run the four tests. Here are the
unexpected and incorrect results:
The file /var/log/syslog contains just one line (should be two):
Jan 14 23:08:09 ubuntu20 test: This is: test
The file /var/log/idallen-cron.log contains three lines (should be two):
Jan 14 23:08:09 ubuntu20 foo: This is: foo
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE
The '/junk' line should *NOT* be matched using "startswith_i 'foo'".
The same bug happens using '[junk' as the tag. Any number of blanks
may precede the / or the [ character and still cause the bug.
$ logger -t ' /anything' "This also triggers the bug."
$ logger -t ' [anything' "This also triggers the bug."
The bug did not appear when matching against $syslogtag:
# This does not show the bug:
if ( $syslogtag startswith_i 'foo' ) then {
/var/log/idallen-cron.log
stop
}
I tried to use "startswith" and "startswith_i" to match against the
"$msg" instead of against "$programname" or "$syslogtag" but could not
get any match at all no matter what I used as my logger message text:
# This never matches anything:
if ( $msg startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rsyslog 8.2001.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan 15 02:02:24 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (464 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logrotate.d.rsyslog: [modified]
mtime.conffile..etc.logrotate.d.rsyslog: 2020-12-27T12:21:35.307395
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1958005
Title:
rsyslogd mishandles startswith_i against $programname
Status in rsyslog package in Ubuntu:
New
Bug description:
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
stop
}
Restart rsyslog:
# /etc/init.d/rsyslog restart
Run these four tests:
$ logger -t 'test' "This is: test"
$ logger -t 'foo' "This is: foo"
$ logger -t 'FOO' "This is: FOO"
$ logger -t '/junk' "This is /junk"
Expected and correct result:
The file /var/log/syslog contains three lines (correct):
Jan 14 23:08:09 ubuntu20 test: This is: test
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk
The file /var/log/idallen-cron.log contains just one line (correct):
Jan 14 23:08:09 ubuntu20 foo: This is: foo
Now make this change: In the 10-idallen.conf file change "startswith"
to "startswith_i". Restart rsyslog. Run the four tests. Here are the
unexpected and incorrect results:
The file /var/log/syslog contains just one line (should be two):
Jan 14 23:08:09 ubuntu20 test: This is: test
The file /var/log/idallen-cron.log contains three lines (should be
two):
Jan 14 23:08:09 ubuntu20 foo: This is: foo
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE
The '/junk' line should *NOT* be matched using "startswith_i 'foo'".
The same bug happens using '[junk' as the tag
[Touch-packages] [Bug 1965076] [NEW] rsync --update incorrectly reports file "is newer" than itself
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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: New Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
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 uptodate". My scripts that look for "is newer" are all broken, because now every file is flagged as newer, even when the file is not newer. 2. I expect that a name flagged as "is newer" will be transferred when I remove the --update option, and that does not happen because the file is *NOT* newer; the message is wrong and no transfer happens. 3. The message changes with and without the --update option. If rsync says "is uptodate" without the --update option, why does that change to "is newer" when you add the option? Either the file is newer *OR* it is uptodate; it can't be both. Adding the --update option should not change "is uptodate" to "is newer". It is not newer; don't say it is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Incomplete Bug description: 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 uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1045072] Re: bash generates spurious DEL on empty variable interpolation
This bug is gone in Ubuntu 12.04 using bash 4.2.25(1)-release
** Changed in: bash (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1045072
Title:
bash generates spurious DEL on empty variable interpolation
Status in bash package in Ubuntu:
Fix Released
Bug description:
#!/bin/bash -u
# BASH BUG: spurious DEL characters appear on empty variable interpolation.
# BASH 4.2.8(1)-release
# Script works fine (expected 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 "$a""$a""$a""$a" # spurious two DEL chars appear at line end
echo correct a"$a" # correct single "a" on line
echo XwrongX a"$a""$a" # spurious DEL char appears at line end
echo correct a"$a$a"# correct single "a" on line
echo correct a"$a$a$a$a"# correct single "a" on line
} | cat -v
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bash 4.2-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-15.66-generic 2.6.38.8
Uname: Linux 2.6.38-15-generic x86_64
Architecture: amd64
Date: Sun Sep 2 15:36:55 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: bash
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1045072/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
