I would like to see testing and feedbacks from others now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
Title:
[sync][sru] sos upstream 4.0
To manage notifications about this bug go to:
[VERIFICATION FOCAL] [PART 2]
No ERROR nor WARNING found during my testing on container, VM and
physical machine (laptop/workstation)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
Title:
** Changed in: sosreport (Ubuntu Bionic)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Xenial)
Status: New => In Progress
** Changed in: sosreport (Ubun
Reimiging the install media worked for me. Other than that, I regret my
lack of knowledge.
Good luck, and please stay safe.
On Thu, Aug 27, 2020, 3:20 PM Arpit Kumar <1874...@bugs.launchpad.net>
wrote:
> how to fix this bug?
>
> --
> You received this bug notification because you are subscribed
** Description changed:
[Impact]
The sos team is pleased to announce the release of sos-4.0. This is a major
version release that represents a significant change to the sos project, new
features, and bug fixes.
https://github.com/sosreport/sos/releases/tag/4.0
[Test Case]
*
2 splitting things
out.
After a discussion with sil2100 (to get a neutral opinion) he agreed
with the above statement.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
Title:
[sync][sr
As discussed the above proposal might require a meta package call
'sosreport4' in Groovy to ease the upgrade path.
Again let's wait for a Ubuntu archive admin to look at this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's also going to involve more package work:
* Does sosreport and sosreport4 needs to break/conflict ? or can co-exist ?
I think it would make more sense to have one or the other.
* Make sure sosreport and sosreport4 follow the same upgrade path if one
upgrade from focal to groovy. Note that
@arif-ali,
I like the idea.
Let me talk with an Ubuntu archive admin.
Most likely sosreport4 would have to go in universe at first and then go
over the MIR process if need be.
I also like to have sosreport4 in Universe and sosreport in Main, since
sosreport4 is still experimental ish.
Let's
sosreport4 would also have to Conflicts with sosreport and vice versa
since they share same file and binaries name/location.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
Title:
[sync][sru]
@arif-ali,
I like the idea.
@arif-ali,
I like the idea.
Let me talk with a Ubuntu archive admin.
Most likely sosreport4 would have to go in universe at first and then go
over the MIR process if we go that route.
Let me talk with an Ubuntu archive admin.
Most likely sosreport4 would have to
I think we could go that route starting focal and downward, but groovy
would have sosreport only which would be 4.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
Title:
[sync][sru] sos
@arif-ali,
I like the idea.
Let me talk with a Ubuntu archive admin.
Most likely sosreport4 would have to go in universe at first and then go
over the MIR process if we go that route.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
"4.0-1~ubuntu0.20.04.1" has been uploaded in the focal upload queue,
waiting for approval to start building in focal-proposed where more
verification will happen across Canonical support team.
- Eric
** Also affects: sosreport (Ubuntu Bionic)
Importance: Undecided
Status: Ne
** Description changed:
[Impact]
The sos team is pleased to announce the relase of sos-4.0. This is a major
version release that represents a significant change to the sos project, new
features, and bug fixes.
https://github.com/sosreport/sos/releases/tag/4.0
[Test Case]
*
** Description changed:
+ [Impact]
+
+ [Test Case]
+ * Install sosreport 4.0-1* package
+ ** Test new main binary 'sos' and it's former binary still present
'sosreport' (e.g. sosreport -a --all-logs & sos report -a --all-logs)
+ ** Test new features:
+ *** sos-collect (Collect sosreport
signee: (unassigned) => Eric Desrochers (slashd)
** Summary changed:
- [sync] sos upstream 4.0
+ [sync][sru] sos upstream 4.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
Title:
[sync]
This bug was fixed in the package sosreport - 4.0-1
Sponsored for Eric Desrochers (slashd)
---
sosreport (4.0-1) unstable; urgency=medium
* New 4.0 upstream release.
Release information and tarballs are available at:
- https://github.com/sosreport/sos/releases/tag/4.0
@Richard @Ryan,
Thanks, much appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
Curtin doesn't handle type:mount entries without 'path' element
To manage notifications
@ryan,
Are you planning to SRU it ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892242
Title:
Curtin doesn't handle type:mount entries without 'path' element
To manage notifications about this
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Bionic)
** Summary changed:
- upstream 4.0 is out
+ sync | sos upstream 4.0
** Summary changed:
- sync | sos upstream 4.0
+ [sync] sos upstream 4.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
During the Debian packaging, I found a bug that I fixed in:
https://github.com/sosreport/sos/commit/1d7bab6c7ce3f78758113ca3cdf3e9fa1762df24
I also divert from upstream by instructing sos.conf to save sosreport
contents into /tmp instead of now enforce location /var/tmp in order to
keep same
During the Debian packaging, I found a bug that I fixed in:
https://github.com/sosreport/sos/commit/1d7bab6c7ce3f78758113ca3cdf3e9fa1762df24
I also divert from upstream by instructing sos.conf to save sosreport
contents into /tmp instead of now enforce location /var/tmp in order to
keep same
Importance: Unknown
Status: Unknown
** Affects: sosreport (Ubuntu)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Tags: seg sts
** Tags added: seg sts
** Bug watch added: Debian Bug tracker #968690
https://bugs.debian.org/cgi-bin
Public bug reported:
Probably error in cache:
2020-08-18 13:59:05,049 DEBUG running doUpdate() (showErrors=False)
2020-08-18 13:59:15,107 ERROR IOError/SystemError in cache.update(): ''.
Retrying (currentRetry: 0)
2020-08-18 13:59:15,108 ERROR doUpdate() failed completely
2020-08-18 13:59:15,108
** Also affects: sosreport (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: sosreport (Ubuntu Groovy)
Importance: Undecided
Assignee: Nicolas Bock (nicolasbock)
Status: New
** Also affects: sosreport (Ubuntu Xenial)
Importance: Undecided
ond on an ASRock
X99 Extreme based build (6 Core Intel server CPU, 64 Gb error correcting
memory). Perhaps the install simply needed more memory, though I cannot see
why.
Thank you so much.
-- Eric
On Wed, Aug 12, 2020 at 8:31 AM MADUPOJU SANJAY KUMAR <
1874...@bugs.launchpad.net> wrote:
>
https://github.com/sshuttle/sshuttle/issues/503
** Bug watch added: github.com/sshuttle/sshuttle/issues #503
https://github.com/sshuttle/sshuttle/issues/503
** Also affects: sshuttle via
https://github.com/sshuttle/sshuttle/issues/503
Importance: Unknown
Status: Unknown
--
You
Public bug reported:
I have installed from this CD before, and everything went smoothly. The
prior install was against an internal SSD.
I am now installing on a USB stick, and had to remove /usr/lib/ubuquity
/apt-setup/generators/40cdrom to fix a previous failure. (I actually
moved the file
Happened in 20.04 LTS as well. I have removed usr/lib/ubiquity/apt-
setup/generators/40cdrom (actually created ~/RemovedFiles and saved it
there) and will try again.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890177
Title:
rsyslogd: file
@zack
You could wait until the logrotate happen and restart rsyslog or you
could simply do manual restart using 'systemctl restart rsyslog' and
then look in /var/log/syslog.
What triggers the error is at rsyslog startup from what I have notice
during my test.
- Eric
--
You received this bug
@zack
You could wait until the logrotate happen that will then restart rsyslog
itself or you could simply do a manual restart using 'systemctl restart
rsyslog' and then look in /var/log/syslog.
What triggers the error is at rsyslog startup from what I have notice
during my test.
- Eric
--
You
The apport (2.20.11-0ubuntu27.6) security channel build haven't been caught in
that FTBFS situation because it was tested against the former pycodestyle
package:
Get:310 http://ftpmaster.internal/ubuntu focal/universe amd64 pycodestyle all
2.5.0-2 [5092 B]
--
You received this bug
[sts-sponsor note]
Package doesn't build due to new pycodestyle (2.6.0-1~20.04.1) found in
focal-proposed as opposed to its former version (2.5.0-2) that now
detects the following during the test:
Running pycodestyle...
./setup.py:78:33: E741 ambiguous variable name 'l'
[sts-sponsor note]
Package doesn't build due to new pycodestyle (2.6.0-1~20.04.1) found in
focal-proposed as opposed to its former version (2.5.0-2) that now
detects the following during the test:
Running pycodestyle...
./setup.py:78:33: E741 ambiguous variable name 'l'
I have retry the test, it is failing on 'systemd-fsckd'.
Let's see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890177
Title:
rsyslogd: file '/dev/console': open error: Permission denied
To
I have retried the autpkgtest test on ppc64el. It is failing on
'systemd-fsckd'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890177
Title:
rsyslogd: file '/dev/console': open error: Permission
** Description changed:
[Impact]
At the moment rsyslog cannot have access /dev/console due to a mismatch
permission/ownership between '/dev/console' and the Privilege Drop User
and Group 'syslog' in rsyslog.
[Test Case]
- * Deploy focal/20.04LTS
+ * Deploy focal/20.04LTS
Thanks @sil2100 for your pre-approval comment.
I have uploaded it into focal upload queue.
It is now waiting for the official SRU team approval in order to start building
in focal-proposed for the verification test phase.
- Eric
--
You received this bug notification because you are a member
** Description changed:
+ [Impact]
+
+ At the moment rsyslog cannot have access /dev/console due to a mismatch
+ permission/ownership between '/dev/console' and the Privilege Drop User
+ and Group 'syslog' in rsyslog.
+
+ [Test Case]
+
+ * Deploy focal/20.04LTS
+ * Install rsyslog
+ *
** Changed in: rsyslog (Ubuntu Focal)
Status: New => In Progress
** Changed in: rsyslog (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: rsyslog (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification be
One easy fix would possibly be the following:
# debian/rsyslog.postinst
case "$1" in
configure)
adduser --system --group --no-create-home --quiet syslog || true
adduser syslog adm || true
+adduser syslog tty || true
I have tested it in a PPA, and it works just fine:
https://wiki.debian.org/SystemGroups
tty: TTY devices are owned by this group. This is used by write and wall
to enable them to write to other people's TTYs, but it is not intended
to be used directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
One easy fix would possibly be the following:
# debian/rsyslog.postinst
case "$1" in
configure)
adduser --system --group --no-create-home --quiet syslog || true
adduser syslog adm || true
+adduser syslog tty || true
I'll give it a try and test.
--
You received this
Public bug reported:
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to
'syslog' for the user and group, and don't match the
ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open
error: Permission denied
** Bug watch added: Debian Bug tracker #966621
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621
Importance: Unknown
Status: Unknown
--
You received this bug notification
[sts-sponsor]
Sponsored for Xenial. It is now waiting for the SRU team approval to
start building in xenial-proposed pocket.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886491
Title
[sts-sponsor]
Sponsored in active development release (groovy)
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881976
[sts-sponsor]
@dgadomski
I don't think you can add a runtime dependency from universe to a
package found in main
apport-gtk | 2.20.11-0ubuntu42 | groovy
konsole | 4:20.04.3-0ubuntu1 | groovy/universe
This would most likely require an MIR for konsole first.
IMO, we should not assume that upstream cared or not about py < 3.5.
As William and I pointed out, we will most likely have to carry the patch to
future release due to ESM.
I think that opening the discussion upstream to get their official
position on this might be insightful, and then we can
@scott,
Would it be worth submitting it upstream for them to stay backward
compatible within the python3 series ?
That way we won't have to carry the patch over and over, if this become
part of the upstream code.
- Eric
--
You received this bug notification because you are a member of Ubuntu
dpdk-init=true
** Changed in: sosreport (Ubuntu Focal)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug not
** Changed in: sosreport (Ubuntu Focal)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification be
** Description changed:
- Backport OVS changes into sosreport (ubuntu) ?
+ Backport OVS changes into sosreport (ubuntu)
c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports
96c69385 [openvswitch] pull cfm, qos, and bond info
4703cbaa [openvswitch] Add LACP stats
27ef2569
** Changed in: sosreport (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/154
Title:
update ovs plugin
To manage notifications about this bug go to:
This is on 18.04.4 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888962
Title:
development is misspelled in prompt for lts
To manage notifications about this bug go to:
Public bug reported:
When trying to upgrade using do-release-upgrade from an lts version, one
gets:
There is no development version of an LTS available.
To upgrade to the latest non-LTS develoment release
set Prompt=normal in /etc/update-manager/release-upgrades.
"develoment" should be
** Changed in: sosreport (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I wrote to sil2100 (SRU verification team member)
He'll take a look at it when time permit, and he should update the bug
anytime soon with his 2 cents about the current situation.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
[Impact]
sosreport is in constant development, and since 3.9.1 got released a few
plugin updates, adds, ... has been merged upstream (Some of the changes
has been reported and/or submitted by Canonical employees). Some changes
will be beneficial for the
The above is under evaluation/investigation.
** Description changed:
+ Backport OVS changes into sosreport (ubuntu) ?
+
c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports
96c69385 [openvswitch] pull cfm, qos, and bond info
4703cbaa [openvswitch] Add LACP stats
27ef2569
Public bug reported:
Backport OVS changes into sosreport (ubuntu) ?
c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports
96c69385 [openvswitch] pull cfm, qos, and bond info
4703cbaa [openvswitch] Add LACP stats
27ef2569 [openvswitch] List important dpdk related directories
bc0c0245
Thanks Chris ! Will ping SRU team to release it sometime this or next
week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
** Description changed:
[Impact]
sosreport is in constant development, and since 3.9.1 got released a few
- plugin updates, adds, ... happened. Some changes will be benefit the
- Canonical support team in troubleshooting UA customer and may also serve
- for other 3rd party vendor.
+ plugin
** Description changed:
+ [Impact]
+
+ sosreport is in constant development, and since 3.9.1 got released a few
+ plugin updates, adds, ... happens. Those change will be useful for
+ Canonical support in troubleshooting UA customer and may also server
+ other 3rd party vendor.
+
+
+ [Test
deployments
b34edec3 [pacemaker] Fix scrubbing when password contains an equal sign
** Affects: sosreport (Ubuntu)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Affects: sosreport (Ubuntu Xenial)
Importance: Undecided
Status: New
[VERIFICATION XENIAL]
I have reviewed all ARCHes under http://autopkgtest.ubuntu.com/
and they all passed
# For instance here's the XENIAL for amd64 architecture:
http://autopkgtest.ubuntu.com/packages/s/sosreport/xenial/amd64
# Log also confirm the success:
Everything worked!
autopkgtest
Thanks for your testing nspmangalore, much appreciated !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886548
Title:
setcifsacl: fix adding ACE when owner sid in unexpected location
To manage
ek for its release.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886548
Title:
setcifsacl: fix adding ACE when owner sid in unexpected location
To manage notifications about this bug go
[VERIFICATION XENIAL]
Test with sosreport: 3.9.1-1ubuntu0.16.04.1
* Running sosreport from for instance an LXD container, no longer reveal
KVM details from its host as it was previously (if KVM was installed at
the host level):
** ls -altr sos_commands/kvm
ls: cannot access 'sos_commands/kvm':
[VERIFICATION XENIAL]
This has been tested running sosreport (3.9.1-1ubuntu0.16.04.1)
# sos_logs/sos.log revealed that the MAAS plugin has been exercised on a
MAAS snap install as expected.
# No errors found.
# Logs
sos.log:2020-07-16 15:27:10,001 INFO: [plugin:maas] added cmd output
'
Permission denied
Nothing to worry about here.
** ls sos_logs/
sos.log ui.log
No Stack Trace file found.
* No non-legit 0 size files found.
* Commonly used parameter all works as expected.
* --upload work and got uploaded into our FTP uploads/ folder.
- Eric
** Tags removed: verification-needed
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886548
Title:
setcifsacl:
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874526
Title:
[landscape] Substitute oidc c
@gpiccoli,
One is the bug itself and the other one is the backport request "paperwork".
I guess we duplicate to kind of link them together.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827367
@gpiccoli,
One is the bug itself and the other one is the backport request "paperwork".
I guess we could mark them as duplicate to kind of link them together.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sosreport (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883320
Title:
[kvm] change check_enabled to /dev/kvm
To manage
** Changed in: sosreport (Ubuntu Xenial)
Status: Won't Fix => In Progress
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: sosreport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: sosreport (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (
** Changed in: sosreport (Ubuntu Xenial)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sosreport (Ubuntu Xenial)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884293
Title:
Update to maintenance release v3.9.1
To manage
** Description changed:
[Impact]
Endpoints that have been updated with python 3.8 seem to cause issues
with sshuttle.
[Test Case]
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
** Tags removed: sts-sponsor-slashd
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage
y
(python-pytest-runner, python-pytest-cov
- Added a DEP3 header in the quilt patch.
- Slighly modified d/changelog to reflect the minor changes.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug go
** Changed in: sshuttle (Ubuntu Focal)
Assignee: Dan Hill (hillpd) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect
Public bug reported:
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
screenfetch
./+o+- @BazUbu
y- -yy+ OS: Ubuntu 18.04 bionic
** Description changed:
+ [Impact]
+
+ [Test Case]
+
+ [Regression Potential]
+
+ [Other Info]
+
+ [Original Description]
+
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
- $ apt-cache policy
@freyes
Do you have your focal debdiff handy still ?
I'll be happy to sponsor the work you did for sshuttle focal.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle
Next step is to introduce the fix through SRU into sshuttle version
"0.78.5-1".
** Changed in: sshuttle (Ubuntu Groovy)
Assignee: Dan Hill (hillpd) => (unassigned)
** Changed in: sshuttle (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because
[Groovy]
# Launchpad
https://launchpad.net/ubuntu/+source/sshuttle
# rmadison
sshuttle | 1.0.3-1 | groovy/universe | source, all
# changelog
sshuttle (1.0.3-1) unstable; urgency=medium
[ Brian May ]
* Update to latest upstream version. Closes: #953621.
* Upstream has
@smoser,
Not for focal, but for the active development release and debian
unstable I suggest we bump to 1.0.2.
As part of the SRU, just cherry-pick the desired fix.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
[Autopkgtest regression report (sosreport/3.9.1-1ubuntu0.2]
Regression PASSED at 3rd attempts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886494
Title:
sosreport does not correctly enable the
rn dh compat
version, ...
* (B) Cherry-pick the 3.8 fix[0] into Debian so that Ubuntu can then
follows.
- Eric
** Bug watch added: Debian Bug tracker #953621
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953621
** Also affects: sshuttle (Debian) via
https://bugs.debian.org/cgi-bin/bugr
/comments/6
It is just a matter of retrying the job until it passes. I'm on it.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886494
Title:
sosreport does not correctly enable the maas plugin
Public bug reported:
Two-finger scrolling works fine on boot, but on my Thinkpad T440s after
I resume from suspend, two-finger scrolling no longer works. Touchpad
still works to move the mouse and click, but two-finger scrolling does
not.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
[VERIFICATION FOCAL]
This has been tested running sosreport (3.9.1-1ubuntu0.20.04.2)
# sos_logs/sos.log revealed that the MAAS plugin has been exercised on a
MAAS snap install as expected.
# No errors found.
# Logs
sos.log:2020-07-09 15:18:38,105 INFO: [plugin:maas] added cmd output 'systemctl
[VERIFICATION BIONIC]
This has been tested running sosreport (3.9.1-1ubuntu0.18.04.2)
# sos_logs/sos.log revealed that the MAAS plugin has been exercised on a
MAAS snap install as expected.
# No errors found.
# Logs
sos.log:2020-07-09 15:12:01,034 INFO: [plugin:maas] added cmd output
701 - 800 of 10775 matches
Mail list logo
