[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL

2022-04-02 Thread iBug
Reported to WSL: https://github.com/microsoft/WSL/issues/8219

** Bug watch added: github.com/microsoft/WSL/issues #8219
   https://github.com/microsoft/WSL/issues/8219

** Also affects: gzip via
   https://github.com/microsoft/WSL/issues/8219
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1966849

Title:
  gzip exec format error under WSL

Status in gzip:
  Unknown
Status in gzip package in Ubuntu:
  Confirmed

Bug description:
  gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows
  19044.1620, making WSL pretty much unusable.

  bash: /usr/bin/gzip: cannot execute binary file: Exec format error

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gzip 1.10-4ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar 29 06:40:33 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gzip/+bug/1966849/+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 1966849] Re: gzip exec format error under WSL

2022-04-02 Thread iBug
Note that only 1.10-4ubuntu3 is affected, so users can install gzip
1.10-4ubuntu1 and set the package on hold for the time being, until the
issue is resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1966849

Title:
  gzip exec format error under WSL

Status in gzip:
  Unknown
Status in gzip package in Ubuntu:
  Confirmed

Bug description:
  gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows
  19044.1620, making WSL pretty much unusable.

  bash: /usr/bin/gzip: cannot execute binary file: Exec format error

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gzip 1.10-4ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar 29 06:40:33 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gzip/+bug/1966849/+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 1966849] Re: gzip exec format error under WSL

2022-04-09 Thread iBug
Also affects: gzip (=1.10-4ubuntu4)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1966849

Title:
  gzip exec format error under WSL

Status in gzip:
  New
Status in gzip package in Ubuntu:
  Confirmed

Bug description:
  gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows
  19044.1620, making WSL pretty much unusable.

  bash: /usr/bin/gzip: cannot execute binary file: Exec format error

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gzip 1.10-4ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar 29 06:40:33 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gzip/+bug/1966849/+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 1947318] [NEW] ip xfrm policy help gives invalid output

2021-10-15 Thread iBug
Public bug reported:

On Ubuntu Focal, the `ip x p h` command from iproute2 (5.5.0-1ubuntu1)
gives the following output:

UPSPEC := proto { { tcp | tcp | tcp | tcp } [ sport PORT ] [ dport PORT ] |
  { icmp | icmp | icmp } [ type NUMBER ] [ code NUMBER ] |
  gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }

I don't think the proto is intended to be "{ tcp | tcp | tcp | tcp }" or
"{ icmp | icmp | icmp }"

The same command provided by iproute2 in Debian Buster
(4.20.0-2+deb10u1), Bullseye (5.10.0-4) and Ubuntu Groovy
(5.7.0-1ubuntu1) generates the following output, which looks like
intended.

UPSPEC := proto { { tcp | udp | sctp | dccp } [ sport PORT ] [ dport PORT ] 
|
  { icmp | ipv6-icmp | mobility-header } [ type NUMBER ] [ 
code NUMBER ] |
  gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }

It certainly makes more sense that proto may be one of "{ tcp | udp |
sctp | dccp }" than "{ tcp | tcp | tcp | tcp }".

Should any relevant fix be ported to the LTS version, Focal, too?

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1947318

Title:
  ip xfrm policy help gives invalid output

Status in iproute2 package in Ubuntu:
  New

Bug description:
  On Ubuntu Focal, the `ip x p h` command from iproute2 (5.5.0-1ubuntu1)
  gives the following output:

  UPSPEC := proto { { tcp | tcp | tcp | tcp } [ sport PORT ] [ dport PORT ] 
|
{ icmp | icmp | icmp } [ type NUMBER ] [ code NUMBER ] |
gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }

  I don't think the proto is intended to be "{ tcp | tcp | tcp | tcp }"
  or "{ icmp | icmp | icmp }"

  The same command provided by iproute2 in Debian Buster
  (4.20.0-2+deb10u1), Bullseye (5.10.0-4) and Ubuntu Groovy
  (5.7.0-1ubuntu1) generates the following output, which looks like
  intended.

  UPSPEC := proto { { tcp | udp | sctp | dccp } [ sport PORT ] [ dport PORT 
] |
{ icmp | ipv6-icmp | mobility-header } [ type NUMBER ] 
[ code NUMBER ] |
gre [ key { DOTTED-QUAD | NUMBER } ] | PROTO }

  It certainly makes more sense that proto may be one of "{ tcp | udp |
  sctp | dccp }" than "{ tcp | tcp | tcp | tcp }".

  Should any relevant fix be ported to the LTS version, Focal, too?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1947318/+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 1871465] [NEW] ssh_config(5) contains outdated information

2020-04-07 Thread iBug
Public bug reported:

The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
of CACertificateAlgorithms. However the latest `openssh-client` still
ships the man page for ssh_config(5) that contains the following
description:

 CASignatureAlgorithms
 Specifies which algorithms are allowed for signing of certificates 
 by certificate authorities (CAs).  The default is:

   ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
   ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

 ssh(1) will not accept host certificates signed using algorithms 
 other than those specified.

As far as I am concerned, `ssh-rsa` should be dropped from the list so
as to match the behavior of ssh(1).

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: manpage

** Description changed:

  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:
  
-  CASignatureAlgorithms
-  Specifies which algorithms are allowed for signing of 
certificates by certificate authorities (CAs).  The default is:
+  CASignatureAlgorithms
+  Specifies which algorithms are allowed for signing of 
certificates 
+  by certificate authorities (CAs).  The default is:
  
-
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
-ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
+    
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
+    ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  
-  ssh(1) will not accept host certificates signed using
- algorithms other than those specified.
+  ssh(1) will not accept host certificates signed using algorithms 
+  other than those specified.
  
  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  New

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1871465/+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