[Bug 1845018] Re: SIMD broken in 0.8.1 please backport fix, like Debian

2019-10-13 Thread Andreas Hasenack
Yeah, on eoan I get:
$ cat /proc/spl/kstat/zfs/fletcher_4_bench
0 0 0x01 -1 0 4250112835 2191051355493
implementation   native byteswap   
scalar   7121128976 5682673600 
superscalar  9132158207 6984205638 
superscalar4 8279361738 6770847284 
fastest  superscalarsuperscalar

The same machine on bionic gets:
0 0 0x01 -1 0 67628130770 127422129063
implementation   native byteswap   
scalar   7105261516 5016484387 
superscalar  9725496554 7224297957 
superscalar4 8153749237 6904111964 
sse2 163259291409147142980 
ssse31601095195714542922899
avx2 2437961704023016231817
fastest  avx2   avx2   

Bionic's algorithm using avx2 is 2.6x faster.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845018

Title:
  SIMD broken in 0.8.1 please backport fix, like Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1845018/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-10 Thread Andreas Hasenack
** Description changed:

  [Impact]
  To do almost anything in the ACME protocol used by Let's Encrypt and Certbot 
including obtaining and revoking certificates, you need to first create an 
account with the ACME server. Starting in November, Certbot will no longer be 
able to do that with its default configuration. This is because as part of 
pushing people towards the standardized version of the protocol, Let's Encrypt 
is no longer letting people create new accounts on their ACMEv1 endpoint. More 
details about this change can be found at 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430.
  
  What this means for Ubuntu users is that new Certbot installations on
  affected systems would need to be given the URL of an alternative ACME
  server in order to work. Existing installations would be unaffected for
  now as long as they don't deactivate their account or delete its
  credentials. They will have additional problems in the future due to the
  additional deprecations described in the link above.
  
  To solve this problem, I recommend backporting the Certbot packages from
  Cosmic to Bionic and Xenial. There are no breaking changes to the public
  interfaces between versions and I think this results in the smallest
  change to the packages that would resolve this problem while sticking to
  well tested packages.
  
  [Test Case]
  The test case will be about requesting a real certificate from Let's Encrypt. 
You need to make sure the host where you are running these instructions:
  - is reachable from the internet on port 80
  - has a public IP
  - said public IP has a valid DNS record under a public domain name
  
  * install certbot with the apache plugin:
  sudo apt install python-certbot-apache certbot
  
  * run the certbot command:
  sudo certbot run
  
  * After the question about your email address, it will initiate a connection 
to an ACME server. The old packages will use a V1 server, like this:
  Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
  
  * The new packages will use a v2 server, like this:
  Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
  
  The above (use a v2 server) is the SRU verification in a nutshell. Of
  course, obtaining the certificate at the end should still work, but we
  want to verify with this update that the v2 server was used.
  
  Depending on the date this test is run, the acme v1 server might have been 
deactivated, in which case you will get this error (with the old packages):
  Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
  An unexpected error occurred:
  The client lacks sufficient authorization :: Account creation on ACMEv1 is 
disabled. Please upgrade your ACME client to a version that supports ACMEv2 / 
RFC 8555. See 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for 
details.
  Please see the logfiles in /var/log/letsencrypt for more details.
  
  * To complete the test, let's test renewing the certificate, and then revoke 
it:
  sudo certbot --dry-run renew
  
  * list certificates, taking note of the certificate path:
  sudo certbot certificate
  
  * revoke the certificate, using the certificate path obtained in the previous 
step:
  sudo certbot --cert-path  revoke
  
  * As a final testing step, list the systemd timers, to make sure the certbot 
one is active:
  $ sudo systemctl list-timers
  NEXT LEFT LAST PASSED 
 UNIT ACTIVATES
  Fri 2019-10-11 04:38:08 UTC  8h left  Thu 2019-10-10 19:24:55 UTC  1h 1min 
ago certbot.timercertbot.service
  ...
  
  [Regression Potential]
- The fix adopted for this bug is a backport from a newer package (cosmic). No 
changes at all for bionic, but xenial needed some:
- - no python3 in xenial, so I had to go back to py2. Upstream gave us their ok 
(see comment #8)
+ The fix adopted for this bug is a backport from a newer package (cosmic). I 
included a fix that was found in debian's 0.28 package, but xenial needed more 
changes:
+ - not all python3 deps are in xenial, so I had to go back to py2. Upstream 
gave us their ok (see comment #8)
  - debhelper 9 instead of 11, that required some changes too, specially around 
systemd
  - build-depends on sphinx >= 1.6 had to be removed, and was done following 
upstream's guidance (see comment #6)
  
  [Other Info]
  This SRU depends on bug #1836823 being released first, as the newer 
python-acme is required.
- 
  
  [Original Description]
  
  This bug affects the python-certbot packages in Xenial and Bionic.
  Cosmic and newer is unaffected.
  
  To do almost anything in the ACME protocol used by Let's Encrypt and
  Certbot including obtaining and revoking certificates, you need to first
  create an account with the ACME server. Starting in November, Certbot
  will no longer be able to do that with its default configuration. This
  is because as part of pushing people towards 

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-10 Thread Andreas Hasenack
** Description changed:

  [Impact]
  To do almost anything in the ACME protocol used by Let's Encrypt and Certbot 
including obtaining and revoking certificates, you need to first create an 
account with the ACME server. Starting in November, Certbot will no longer be 
able to do that with its default configuration. This is because as part of 
pushing people towards the standardized version of the protocol, Let's Encrypt 
is no longer letting people create new accounts on their ACMEv1 endpoint. More 
details about this change can be found at 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430.
  
  What this means for Ubuntu users is that new Certbot installations on
  affected systems would need to be given the URL of an alternative ACME
  server in order to work. Existing installations would be unaffected for
  now as long as they don't deactivate their account or delete its
  credentials. They will have additional problems in the future due to the
  additional deprecations described in the link above.
  
  To solve this problem, I recommend backporting the Certbot packages from
  Cosmic to Bionic and Xenial. There are no breaking changes to the public
  interfaces between versions and I think this results in the smallest
  change to the packages that would resolve this problem while sticking to
  well tested packages.
  
  [Test Case]
  The test case will be about requesting a real certificate from Let's Encrypt. 
You need to make sure the host where you are running these instructions:
  - is reachable from the internet on port 80
  - has a public IP
  - said public IP has a valid DNS record under a public domain name
  
  * install certbot with the apache plugin:
  sudo apt install python-certbot-apache certbot
  
  * run the certbot command:
  sudo certbot run
  
  * After the question about your email address, it will initiate a connection 
to an ACME server. The old packages will use a V1 server, like this:
  Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
  
  * The new packages will use a v2 server, like this:
  Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
  
  The above (use a v2 server) is the SRU verification in a nutshell. Of
  course, obtaining the certificate at the end should still work, but we
  want to verify with this update that the v2 server was used.
  
  Depending on the date this test is run, the acme v1 server might have been 
deactivated, in which case you will get this error (with the old packages):
  Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
  An unexpected error occurred:
  The client lacks sufficient authorization :: Account creation on ACMEv1 is 
disabled. Please upgrade your ACME client to a version that supports ACMEv2 / 
RFC 8555. See 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for 
details.
  Please see the logfiles in /var/log/letsencrypt for more details.
  
  * To complete the test, let's test renewing the certificate, and then revoke 
it:
  sudo certbot --dry-run renew
  
  * list certificates, taking note of the certificate path:
  sudo certbot certificate
  
  * revoke the certificate, using the certificate path obtained in the previous 
step:
  sudo certbot --cert-path  revoke
  
  * As a final testing step, list the systemd timers, to make sure the certbot 
one is active:
  $ sudo systemctl list-timers
  NEXT LEFT LAST PASSED 
 UNIT ACTIVATES
  Fri 2019-10-11 04:38:08 UTC  8h left  Thu 2019-10-10 19:24:55 UTC  1h 1min 
ago certbot.timercertbot.service
  ...
  
- 
  [Regression Potential]
  The fix adopted for this bug is a backport from a newer package (cosmic). No 
changes at all for bionic, but xenial needed some:
  - no python3 in xenial, so I had to go back to py2. Upstream gave us their ok 
(see comment #8)
  - debhelper 9 instead of 11, that required some changes too, specially around 
systemd
  - build-depends on sphinx >= 1.6 had to be removed, and was done following 
upstream's guidance (see comment #6)
  
  [Other Info]
+ This SRU depends on bug #1836823 being released first, as the newer 
python-acme is required.
  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
  
  [Original Description]
  
  This bug affects the python-certbot packages in Xenial and Bionic.
  Cosmic and newer is unaffected.
  
  To do almost anything in the ACME protocol used by Let's Encrypt and
  Certbot including obtaining and revoking certificates, you need to first
  create an account with the ACME server. Starting in November, Certbot
  will no longer be able to do that with its default configuration. This
  is because as part of pushing people towards the standardized version of
  the protocol, Let's Encrypt is no longer letting people 

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-10 Thread Andreas Hasenack
** Description changed:

  [Impact]
  To do almost anything in the ACME protocol used by Let's Encrypt and Certbot 
including obtaining and revoking certificates, you need to first create an 
account with the ACME server. Starting in November, Certbot will no longer be 
able to do that with its default configuration. This is because as part of 
pushing people towards the standardized version of the protocol, Let's Encrypt 
is no longer letting people create new accounts on their ACMEv1 endpoint. More 
details about this change can be found at 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430.
  
  What this means for Ubuntu users is that new Certbot installations on
  affected systems would need to be given the URL of an alternative ACME
  server in order to work. Existing installations would be unaffected for
  now as long as they don't deactivate their account or delete its
  credentials. They will have additional problems in the future due to the
  additional deprecations described in the link above.
  
  To solve this problem, I recommend backporting the Certbot packages from
  Cosmic to Bionic and Xenial. There are no breaking changes to the public
  interfaces between versions and I think this results in the smallest
  change to the packages that would resolve this problem while sticking to
  well tested packages.
  
  [Test Case]
+ The test case will be about requesting a real certificate from Let's Encrypt. 
You need to make sure the host where you are running these instructions:
+ - is reachable from the internet on port 80
+ - has a public IP
+ - said public IP has a valid DNS record under a public domain name
  
-  * detailed instructions how to reproduce the bug
+ * install certbot with the apache plugin:
+ sudo apt install python-certbot-apache certbot
  
-  * these should allow someone who is not familiar with the affected
-    package to reproduce the bug and verify that the updated package fixes
-    the problem.
+ * run the certbot command:
+ sudo certbot run
+ 
+ * After the question about your email address, it will initiate a connection 
to an ACME server. The old packages will use a V1 server, like this:
+ Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
+ 
+ * The new packages will use a v2 server, like this:
+ Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
+ 
+ The above (use a v2 server) is the SRU verification in a nutshell. Of
+ course, obtaining the certificate at the end should still work, but we
+ want to verify with this update that the v2 server was used.
+ 
+ Depending on the date this test is run, the acme v1 server might have been 
deactivated, in which case you will get this error (with the old packages):
+ Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
+ An unexpected error occurred:
+ The client lacks sufficient authorization :: Account creation on ACMEv1 is 
disabled. Please upgrade your ACME client to a version that supports ACMEv2 / 
RFC 8555. See 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for 
details.
+ Please see the logfiles in /var/log/letsencrypt for more details.
+ 
  
  [Regression Potential]
  
   * discussion of how regressions are most likely to manifest as a result
  of this change.
  
   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.
  
   * This both shows the SRU team that the risks have been considered,
     and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
  
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance
  
  [Original Description]
  
  This bug affects the python-certbot packages in Xenial and Bionic.
  Cosmic and newer is unaffected.
  
  To do almost anything in the ACME protocol used by Let's Encrypt and
  Certbot including obtaining and revoking certificates, you need to first
  create an account with the ACME server. Starting in November, Certbot
  will no longer be able to do that with its default configuration. This
  is because as part of pushing people towards the standardized version of
  the protocol, Let's Encrypt is no longer letting people create new
  accounts on their ACMEv1 endpoint. More details about this change can be
  found at https://community.letsencrypt.org/t/end-of-life-plan-for-
  acmev1/88430.
  
  What this means for Ubuntu users is that new Certbot installations on
  affected systems would need to be given the URL of an alternative ACME
  server in order to work. Existing installations would be unaffected for
  now as long as they don't deactivate their account or delete its
  credentials. They will have additional problems in the future due to the
  additional 

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-10 Thread Andreas Hasenack
** Changed in: python-certbot (Ubuntu Xenial)
 Assignee: James Hebden (ec0) => Andreas Hasenack (ahasenack)

** Changed in: python-certbot (Ubuntu Bionic)
 Assignee: James Hebden (ec0) => Andreas Hasenack (ahasenack)

** Changed in: python-certbot (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: python-certbot (Ubuntu Bionic)
   Status: Triaged => In Progress

** Description changed:

+ [Impact]
+ 
+  * An explanation of the effects of the bug on users and
+ 
+  * justification for backporting the fix to the stable release.
+ 
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [Test Case]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+ [Regression Potential]
+ 
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ 
+ [Original Description]
+ 
  This bug affects the python-certbot packages in Xenial and Bionic.
  Cosmic and newer is unaffected.
  
  To do almost anything in the ACME protocol used by Let's Encrypt and
  Certbot including obtaining and revoking certificates, you need to first
  create an account with the ACME server. Starting in November, Certbot
  will no longer be able to do that with its default configuration. This
  is because as part of pushing people towards the standardized version of
  the protocol, Let's Encrypt is no longer letting people create new
  accounts on their ACMEv1 endpoint. More details about this change can be
  found at https://community.letsencrypt.org/t/end-of-life-plan-for-
  acmev1/88430.
  
  What this means for Ubuntu users is that new Certbot installations on
  affected systems would need to be given the URL of an alternative ACME
  server in order to work. Existing installations would be unaffected for
  now as long as they don't deactivate their account or delete its
  credentials. They will have additional problems in the future due to the
  additional deprecations described in the link above.
  
  To solve this problem, I recommend backporting the Certbot packages from
  Cosmic to Bionic and Xenial. There are no breaking changes to the public
  interfaces between versions and I think this results in the smallest
  change to the packages that would resolve this problem while sticking to
  well tested packages.

** Description changed:

  [Impact]
+ To do almost anything in the ACME protocol used by Let's Encrypt and Certbot 
including obtaining and revoking certificates, you need to first create an 
account with the ACME server. Starting in November, Certbot will no longer be 
able to do that with its default configuration. This is because as part of 
pushing people towards the standardized version of the protocol, Let's Encrypt 
is no longer letting people create new accounts on their ACMEv1 endpoint. More 
details about this change can be found at 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430.
  
-  * An explanation of the effects of the bug on users and
+ What this means for Ubuntu users is that new Certbot installations on
+ affected systems would need to be given the URL of an alternative ACME
+ server in order to work. Existing installations would be unaffected for
+ now as long as they don't deactivate their account or delete its
+ credentials. They will have additional problems in the future due to the
+ additional deprecations described in the link above.
  
-  * justification for backporting the fix to the stable release.
- 
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ To solve this problem, I recommend backporting the Certbot packages from
+ Cosmic to Bionic and Xenial. There are no breaking changes to the public
+ interfaces between versions and I think this results in the smallest
+ change to the packages that would resolve this problem while sticking to
+ well tested packages.
  
  [Test Case]
  
-  * detailed instructions how to reproduce the bug
+  * detailed instructions how to reproduce the bug
  
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the upd

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-10 Thread Andreas Hasenack
Ok, this ppa is ready for testing:

https://launchpad.net/~ahasenack/+archive/ubuntu/october-certbot-sru/

Or:

sudo add-apt-repository ppa:ahasenack/october-certbot-sru

I was able to verify today that the existing xenial client indeed stopped 
working (we are in the first brown-out day):
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
An unexpected error occurred:
The client lacks sufficient authorization :: Account creation on ACMEv1 is 
disabled. Please upgrade your ACME client to a version that supports ACMEv2 / 
RFC 8555. See 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for 
details.
Please see the logfiles in /var/log/letsencrypt for more details.

I then upgraded to the packages from the ppa, re-ran "certbot run", and
then it used the acmev2 endpoint and worked.

For the actual sru verification I'll just have the verifier check the
url that is used, as the v1 endpoint will probably be active by then
again (unless this update misses the deadline).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-10 Thread Andreas Hasenack
Ok, this ppa is ready for testing:

https://launchpad.net/~ahasenack/+archive/ubuntu/october-certbot-sru/

Or:

sudo add-apt-repository ppa:ahasenack/october-certbot-sru

I was able to verify today that the existing xenial client indeed stopped 
working (we are in the first brown-out day):
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
An unexpected error occurred:
The client lacks sufficient authorization :: Account creation on ACMEv1 is 
disabled. Please upgrade your ACME client to a version that supports ACMEv2 / 
RFC 8555. See 
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for 
details.
Please see the logfiles in /var/log/letsencrypt for more details.

I then upgraded to the packages from the ppa, re-ran "certbot run", and
then it used the acmev2 endpoint and worked.

For the actual sru verification I'll just have the verifier check the
url that is used, as the v1 endpoint will probably be active by then
again (unless this update misses the deadline).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673

Title:
  Certbot will be unable to create new ACME accounts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846506] Re: autopkgtest fail in Eoan

2019-10-09 Thread Andreas Hasenack
The python-azure test failed in bileto in the same way, so it can be
used to further troubleshoot this issue. My first attempt would be to
unset the http_proxy variable, or set it to localhost so connections
fail, and see what happens.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846506

Title:
  autopkgtest fail in Eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846506] Re: autopkgtest fail in Eoan

2019-10-09 Thread Andreas Hasenack
The python-azure test failed in bileto in the same way, so it can be
used to further troubleshoot this issue. My first attempt would be to
unset the http_proxy variable, or set it to localhost so connections
fail, and see what happens.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1846506

Title:
  autopkgtest fail in Eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1846506] Re: autopkgtest fail in Eoan

2019-10-08 Thread Andreas Hasenack
Given the tests pass locally in a container (autopkgtest ... -- lxd
ubuntu-daily;eoan), I'm trying a bileto run
(https://bileto.ubuntu.com/#/ticket/3818) to see if that reproduces the
test failure. If yes, then I can use that platform for troubleshooting.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1846506

Title:
  autopkgtest fail in Eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1846506] Re: autopkgtest fail in Eoan

2019-10-08 Thread Andreas Hasenack
Given the tests pass locally in a container (autopkgtest ... -- lxd
ubuntu-daily;eoan), I'm trying a bileto run
(https://bileto.ubuntu.com/#/ticket/3818) to see if that reproduces the
test failure. If yes, then I can use that platform for troubleshooting.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846506

Title:
  autopkgtest fail in Eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846237] Re: Kernel Panic while virsh dump of Guest with 300G RAM is triggered.

2019-10-08 Thread Andreas Hasenack
comment #4 suggested that the panic only happened because
kernel.softlockup_panic was set to 1, was that verified?

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1846237

Title:
  Kernel Panic while virsh dump of Guest with 300G RAM is triggered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1846237/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1846237] Re: Kernel Panic while virsh dump of Guest with 300G RAM is triggered.

2019-10-08 Thread Andreas Hasenack
comment #4 suggested that the panic only happened because
kernel.softlockup_panic was set to 1, was that verified?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846237

Title:
  Kernel Panic while virsh dump of Guest with 300G RAM is triggered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1846237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647285] Re: SSL trust not system-wide

2019-10-08 Thread Andreas Hasenack
This isn't "just" a bug, it's a roadmap item in my view, as many
products are affected. It needs a spec, like in the fedora case. I agree
that it would be awesome to have this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647285

Title:
  SSL trust not system-wide

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1647285] Re: SSL trust not system-wide

2019-10-08 Thread Andreas Hasenack
This isn't "just" a bug, it's a roadmap item in my view, as many
products are affected. It needs a spec, like in the fedora case. I agree
that it would be awesome to have this.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1647285

Title:
  SSL trust not system-wide

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1847157] Re: memory leaks in open-vm-tools

2019-10-08 Thread Andreas Hasenack
Thanks for this. Will there be a new 10.3.x release with these fixes?

Are these the 3 fixes that should be applied?

26b9edbe (HEAD -> stable-10.3.10-vix-memory-leaks, 
origin/stable-10.3.10-vix-memory-leaks) Fix leaks in ListAliases and 
ListMappedAliases (9bc72f0b09702754b429115658a85223cb3058bd from devel)
7b874f37 End VGAuth impersonation in the case of error.
015db4c0 Fix memory leaks in 'vix' tools plugin.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847157

Title:
  memory leaks in open-vm-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1847157/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845652] Re: rsync sends everything, not just changes

2019-10-08 Thread Andreas Hasenack
When using vfat and running rsync twice, this is the diff in the stats output:
--- log1.vfat   2019-10-08 11:43:04.381667860 -0300
+++ log2.vfat   2019-10-08 11:43:17.609728451 -0300
@@ -1,5 +1,5 @@
 Number of files: 78 (reg: 77, dir: 1)
-Number of created files: 77 (reg: 77)
+Number of created files: 0
 Number of deleted files: 0
 Number of regular files transferred: 77
 Total file size: 3,990,531 bytes
@@ -12,6 +12,6 @@
 Total bytes sent: 3,996,271
 Total bytes received: 8,830
 
-sent 3,996,271 bytes  received 8,830 bytes  534,013.47 bytes/sec
+sent 3,996,271 bytes  received 8,830 bytes  2,670,067.33 bytes/sec
 total size is 3,990,531  speedup is 1.00
 rsync error: some files/attrs were not transferred (see previous errors) (code 
23) at main.c(1196) [sender=3.1.2]

As expected, the files are transferred again, because rsync couldn't set
the permissions or ownership. These concepts don't exist in vfat.

When using ext4, the same rsync command, the diff between the two runs shows a 
different story:
--- log1.ext4   2019-10-08 11:49:01.687411326 -0300
+++ log2.ext4   2019-10-08 11:49:11.795461543 -0300
@@ -1,16 +1,16 @@
 Number of files: 78 (reg: 77, dir: 1)
-Number of created files: 77 (reg: 77)
-Number of deleted files: 1 (dir: 1)
-Number of regular files transferred: 77
+Number of created files: 0
+Number of deleted files: 0
+Number of regular files transferred: 0
 Total file size: 3,990,531 bytes
-Total transferred file size: 3,990,531 bytes
-Literal data: 3,990,531 bytes
+Total transferred file size: 0 bytes
+Literal data: 0 bytes
 Matched data: 0 bytes
 File list size: 0
 File list generation time: 0.001 seconds
 File list transfer time: 0.000 seconds
-Total bytes sent: 3,996,271
-Total bytes received: 1,504
+Total bytes sent: 1,598
+Total bytes received: 19

-sent 3,996,271 bytes  received 1,504 bytes  7,995,550.00 bytes/sec
-total size is 3,990,531  speedup is 1.00
+sent 1,598 bytes  received 19 bytes  3,234.00 bytes/sec
+total size is 3,990,531  speedup is 2,467.86


The rsync command I used was:
rsync -v -a -r -W -p -o -g -t --delete --stats /testdata/ 
/media/andreas/dataext4/

/testdata was populated with a copy of all files in /usr/bin that start
with "b*". I don't think the --exclusion parameters you used play a
factor here.

Can you please verify the target filesystem in your test case, and if
rsync reported errors? And there are other scenarios, like outlined in
comment #2.

I guess, to summarize, we need a testcase. I showed you two cases with
pendrives (vfat, and ext4), where what you describe does NOT happen.

** Changed in: rsync (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845652

Title:
  rsync sends everything, not just changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845652] Re: rsync sends everything, not just changes

2019-10-08 Thread Andreas Hasenack
When using vfat and running rsync twice, this is the diff in the stats output:
--- log1.vfat   2019-10-08 11:43:04.381667860 -0300
+++ log2.vfat   2019-10-08 11:43:17.609728451 -0300
@@ -1,5 +1,5 @@
 Number of files: 78 (reg: 77, dir: 1)
-Number of created files: 77 (reg: 77)
+Number of created files: 0
 Number of deleted files: 0
 Number of regular files transferred: 77
 Total file size: 3,990,531 bytes
@@ -12,6 +12,6 @@
 Total bytes sent: 3,996,271
 Total bytes received: 8,830
 
-sent 3,996,271 bytes  received 8,830 bytes  534,013.47 bytes/sec
+sent 3,996,271 bytes  received 8,830 bytes  2,670,067.33 bytes/sec
 total size is 3,990,531  speedup is 1.00
 rsync error: some files/attrs were not transferred (see previous errors) (code 
23) at main.c(1196) [sender=3.1.2]

As expected, the files are transferred again, because rsync couldn't set
the permissions or ownership. These concepts don't exist in vfat.

When using ext4, the same rsync command, the diff between the two runs shows a 
different story:
--- log1.ext4   2019-10-08 11:49:01.687411326 -0300
+++ log2.ext4   2019-10-08 11:49:11.795461543 -0300
@@ -1,16 +1,16 @@
 Number of files: 78 (reg: 77, dir: 1)
-Number of created files: 77 (reg: 77)
-Number of deleted files: 1 (dir: 1)
-Number of regular files transferred: 77
+Number of created files: 0
+Number of deleted files: 0
+Number of regular files transferred: 0
 Total file size: 3,990,531 bytes
-Total transferred file size: 3,990,531 bytes
-Literal data: 3,990,531 bytes
+Total transferred file size: 0 bytes
+Literal data: 0 bytes
 Matched data: 0 bytes
 File list size: 0
 File list generation time: 0.001 seconds
 File list transfer time: 0.000 seconds
-Total bytes sent: 3,996,271
-Total bytes received: 1,504
+Total bytes sent: 1,598
+Total bytes received: 19

-sent 3,996,271 bytes  received 1,504 bytes  7,995,550.00 bytes/sec
-total size is 3,990,531  speedup is 1.00
+sent 1,598 bytes  received 19 bytes  3,234.00 bytes/sec
+total size is 3,990,531  speedup is 2,467.86


The rsync command I used was:
rsync -v -a -r -W -p -o -g -t --delete --stats /testdata/ 
/media/andreas/dataext4/

/testdata was populated with a copy of all files in /usr/bin that start
with "b*". I don't think the --exclusion parameters you used play a
factor here.

Can you please verify the target filesystem in your test case, and if
rsync reported errors? And there are other scenarios, like outlined in
comment #2.

I guess, to summarize, we need a testcase. I showed you two cases with
pendrives (vfat, and ext4), where what you describe does NOT happen.

** Changed in: rsync (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845652

Title:
  rsync sends everything, not just changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1845765] Re: asterisk-modules package built without amr_codec.so

2019-10-08 Thread Andreas Hasenack
** Changed in: asterisk (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845765

Title:
  asterisk-modules package built without amr_codec.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1845765] Re: asterisk-modules package built without amr_codec.so

2019-10-08 Thread Andreas Hasenack
** Changed in: asterisk (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845765

Title:
  asterisk-modules package built without amr_codec.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847255] Re: zfs setup, whole disk, crashed

2019-10-08 Thread Andreas Hasenack
In this state, as I still have a shell in the live environment:
root@ubuntu:~# zpool status
  pool: bpool
 state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
pool will no longer be accessible on software that does not support
feature flags.
  scan: none requested
config:

NAMESTATE READ WRITE CKSUM
bpool   ONLINE   0 0 0
  sda3  ONLINE   0 0 0

errors: No known data errors

  pool: rpool
 state: ONLINE
  scan: none requested
config:

NAMESTATE READ WRITE CKSUM
rpool   ONLINE   0 0 0
  sda4  ONLINE   0 0 0

errors: No known data errors


root@ubuntu:~# zfs list
NAME   USED  AVAIL REFER  
MOUNTPOINT
bpool 92.2M  1.66G  176K  
/target/boot
bpool/BOOT91.4M  1.66G  176K  none
bpool/BOOT/ubuntu_t62i31  91.2M  1.66G 91.2M  
/target/boot
rpool 5.44G   425G   96K  
/target
rpool/ROOT3.31G   425G   96K  none
rpool/ROOT/ubuntu_t62i31  3.31G   425G 2.83G  
/target
rpool/ROOT/ubuntu_t62i31/srv96K   425G   96K  
/target/srv
rpool/ROOT/ubuntu_t62i31/usr   200K   425G   96K  
/target/usr
rpool/ROOT/ubuntu_t62i31/usr/local 104K   425G  104K  
/target/usr/local
rpool/ROOT/ubuntu_t62i31/var   493M   425G   96K  
/target/var
rpool/ROOT/ubuntu_t62i31/var/games  96K   425G   96K  
/target/var/games
rpool/ROOT/ubuntu_t62i31/var/lib   492M   425G  376M  
/target/var/lib
rpool/ROOT/ubuntu_t62i31/var/lib/AccountServices96K   425G   96K  
/target/var/lib/AccountServices
rpool/ROOT/ubuntu_t62i31/var/lib/NetworkManager 96K   425G   96K  
/target/var/lib/NetworkManager
rpool/ROOT/ubuntu_t62i31/var/lib/apt  72.7M   425G 72.7M  
/target/var/lib/apt
rpool/ROOT/ubuntu_t62i31/var/lib/dpkg 42.6M   425G 42.6M  
/target/var/lib/dpkg
rpool/ROOT/ubuntu_t62i31/var/log   448K   425G  448K  
/target/var/log
rpool/ROOT/ubuntu_t62i31/var/mail   96K   425G   96K  
/target/var/mail
rpool/ROOT/ubuntu_t62i31/var/snap   96K   425G   96K  
/target/var/snap
rpool/ROOT/ubuntu_t62i31/var/spool 112K   425G  112K  
/target/var/spool
rpool/ROOT/ubuntu_t62i31/var/www96K   425G   96K  
/target/var/www
rpool/USERDATA 332K   425G   96K  
/target
rpool/USERDATA/andreas_ecfd2e  124K   425G  124K  
/target/home/andreas
rpool/USERDATA/root_ecfd2e 112K   425G  112K  
/target/root
rpool/swap2.13G   427G   56K  -


root@ubuntu:~# mount -t zfs
rpool/ROOT/ubuntu_t62i31 on /target type zfs (rw,relatime,xattr,posixacl)
bpool/BOOT/ubuntu_t62i31 on /target/boot type zfs 
(rw,nodev,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/lib on /target/var/lib type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/lib/AccountServices on 
/target/var/lib/AccountServices type zfs (rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/lib/apt on /target/var/lib/apt type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/lib/dpkg on /target/var/lib/dpkg type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/lib/NetworkManager on 
/target/var/lib/NetworkManager type zfs (rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/srv on /target/srv type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/usr/local on /target/usr/local type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/games on /target/var/games type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/log on /target/var/log type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/mail on /target/var/mail type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/snap on /target/var/snap type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/spool on /target/var/spool type zfs 
(rw,relatime,xattr,posixacl)
rpool/ROOT/ubuntu_t62i31/var/www on /target/var/www type zfs 
(rw,relatime,xattr,posixacl)
rpool/USERDATA/andreas_ecfd2e on /target/home/andreas type zfs 
(rw,relatime,xattr,posixacl)
rpool/USERDATA/root_ecfd2e on /target/root type zfs (rw,relatime,xattr,posixacl)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

[Bug 1847255] [NEW] zfs setup, whole disk, crashed

2019-10-08 Thread Andreas Hasenack
Public bug reported:

Was trying out the zfs setup with whole disk. No download of updates
during install. Enabled universe beforehand, and installed zsys in the
live session, wondering if that would make a change. Then got the popup
about a crash. As I write this, I haven't looked at the logs yet, so I
don't know what happened.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.15
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Tue Oct  8 09:49:39 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
quiet splash ---
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan ubiquity-19.10.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847255

Title:
  zfs setup, whole disk, crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847255/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847216] Re: motd-news only works with one URL even though docs say mutiple URLs can be configured

2019-10-08 Thread Andreas Hasenack
** Changed in: base-files (Ubuntu)
   Status: New => Triaged

** Changed in: base-files (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847216

Title:
  motd-news only works with one URL even though docs say mutiple URLs
  can be configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1847216/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847105] Re: very slow disk creation, snapshotting

2019-10-08 Thread Andreas Hasenack
I mentioned this only in the bug title, let me clarify a bit.
Snapshotting that machine (via virt-manager again) also takes over a
minute.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847105

Title:
  very slow disk creation, snapshotting

To manage notifications about this bug go to:
https://bugs.launchpad.net/virt-manager/+bug/1847105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-07 Thread Andreas Hasenack
py2 build updated and uploaded to the ppa

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673

Title:
  Certbot will be unable to create new ACME accounts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846506] Re: autopkgtest fail in Eoan

2019-10-07 Thread Andreas Hasenack
Adding a task for python-cryptography so this bug shows up in the
excuses page, even though it's not a bug in python-cryptography itself.

** Also affects: python-cryptography (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1846506

Title:
  autopkgtest fail in Eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1846506] Re: autopkgtest fail in Eoan

2019-10-07 Thread Andreas Hasenack
I suspect the test might require internet access, but it's not clear why
it worked before, since the last pass was the same exact package:

E   vcr.errors.CannotOverwriteExistingCassetteException: No
match for the request (https://squid.internal:3128/----/services/webspaces//eastuswebspace/sites>)
was found. Can't overwrite existing cassette
('/tmp/autopkgtest.STWYRh/autopkgtest_tmp/tests/recordings/test_legacy_mgmt_website.test_get_web_site.yaml')
in your current record mode ('none').

Locally in lxd, and also on diglett, the dep8 tests passed, using eoan-
proposed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846506

Title:
  autopkgtest fail in Eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846506] Re: autopkgtest fail in Eoan

2019-10-07 Thread Andreas Hasenack
Adding a task for python-cryptography so this bug shows up in the
excuses page, even though it's not a bug in python-cryptography itself.

** Also affects: python-cryptography (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846506

Title:
  autopkgtest fail in Eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845765] Re: asterisk-modules package built without amr_codec.so

2019-10-07 Thread Andreas Hasenack
In bionic, that codec was added by a debian patch:
debian/patches/amr.patch
Description: Add AMR and AMR-WB codec modules supporting transcoding

That patch is present in disco and eoan, but neither have the
codec_arm.so file shipped, nor is codec_amr.c mentioned in their
respective build logs.

There is this difference in the build's configure output:

bionic (with codec):
checking for Encoder_Interface_init in -lopencore-amrnb... yes
checking opencore-amrnb/interf_enc.h usability... yes
checking opencore-amrnb/interf_enc.h presence... yes
checking for opencore-amrnb/interf_enc.h... yes
checking for D_IF_init in -lopencore-amrwb... yes
checking opencore-amrwb/dec_if.h usability... yes
checking opencore-amrwb/dec_if.h presence... yes
checking for opencore-amrwb/dec_if.h... yes
checking for E_IF_init in -lvo-amrwbenc... yes
checking vo-amrwbenc/enc_if.h usability... yes
checking vo-amrwbenc/enc_if.h presence... yes
checking for vo-amrwbenc/enc_if.h... yes

Disco (without):
checking for Encoder_Interface_init in -lopencore-amrnb... yes
checking opencore-amrnb/interf_enc.h usability... yes
checking opencore-amrnb/interf_enc.h presence... yes
checking for opencore-amrnb/interf_enc.h... yes
checking for D_IF_init in -lopencore-amrwb... yes
checking opencore-amrwb/dec_if.h usability... yes
checking opencore-amrwb/dec_if.h presence... yes
checking for opencore-amrwb/dec_if.h... yes
checking for E_IF_init in -lvo-amrwbenc... no


The file codec_amr.so is also not present in the debian buster package: 
https://packages.debian.org/buster/amd64/asterisk-modules/filelist

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845765

Title:
  asterisk-modules package built without amr_codec.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1845765] Re: asterisk-modules package built without amr_codec.so

2019-10-07 Thread Andreas Hasenack
In bionic, that codec was added by a debian patch:
debian/patches/amr.patch
Description: Add AMR and AMR-WB codec modules supporting transcoding

That patch is present in disco and eoan, but neither have the
codec_arm.so file shipped, nor is codec_amr.c mentioned in their
respective build logs.

There is this difference in the build's configure output:

bionic (with codec):
checking for Encoder_Interface_init in -lopencore-amrnb... yes
checking opencore-amrnb/interf_enc.h usability... yes
checking opencore-amrnb/interf_enc.h presence... yes
checking for opencore-amrnb/interf_enc.h... yes
checking for D_IF_init in -lopencore-amrwb... yes
checking opencore-amrwb/dec_if.h usability... yes
checking opencore-amrwb/dec_if.h presence... yes
checking for opencore-amrwb/dec_if.h... yes
checking for E_IF_init in -lvo-amrwbenc... yes
checking vo-amrwbenc/enc_if.h usability... yes
checking vo-amrwbenc/enc_if.h presence... yes
checking for vo-amrwbenc/enc_if.h... yes

Disco (without):
checking for Encoder_Interface_init in -lopencore-amrnb... yes
checking opencore-amrnb/interf_enc.h usability... yes
checking opencore-amrnb/interf_enc.h presence... yes
checking for opencore-amrnb/interf_enc.h... yes
checking for D_IF_init in -lopencore-amrwb... yes
checking opencore-amrwb/dec_if.h usability... yes
checking opencore-amrwb/dec_if.h presence... yes
checking for opencore-amrwb/dec_if.h... yes
checking for E_IF_init in -lvo-amrwbenc... no


The file codec_amr.so is also not present in the debian buster package: 
https://packages.debian.org/buster/amd64/asterisk-modules/filelist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845765

Title:
  asterisk-modules package built without amr_codec.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845652] Re: rsync sends everything, not just changes

2019-10-07 Thread Andreas Hasenack
What's the filesystem on the target? If the target is vfat, for example,
setting ownership and permissions won't work, and -W tells rsync to
transfer the whole file.

** Changed in: rsync (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845652

Title:
  rsync sends everything, not just changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845652] Re: rsync sends everything, not just changes

2019-10-07 Thread Andreas Hasenack
What's the filesystem on the target? If the target is vfat, for example,
setting ownership and permissions won't work, and -W tells rsync to
transfer the whole file.

** Changed in: rsync (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845652

Title:
  rsync sends everything, not just changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1843729] Re: byobu ftbfs in eoan

2019-10-07 Thread Andreas Hasenack
@cosmos-door, thanks for that merge request against upstream. We are
just a few days away from Final Freeze, though. Would you perhaps be
able to make a merge proposal against the packaging, with a quilt patch?
That would be the ubuntu/devel branch, if you clone the repository
according to the instructions in
https://code.launchpad.net/ubuntu/+source/byobu

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1843729

Title:
  byobu ftbfs in eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1843729] Re: byobu ftbfs in eoan

2019-10-07 Thread Andreas Hasenack
@cosmos-door, thanks for that merge request against upstream. We are
just a few days away from Final Freeze, though. Would you perhaps be
able to make a merge proposal against the packaging, with a quilt patch?
That would be the ubuntu/devel branch, if you clone the repository
according to the instructions in
https://code.launchpad.net/ubuntu/+source/byobu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843729

Title:
  byobu ftbfs in eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847105] [NEW] very slow disk creation, snapshotting

2019-10-07 Thread Andreas Hasenack
Public bug reported:

This is a regression in eoan for me. I use virt-manager to create vms,
and I noticed that creating one now takes more than a minute.

Looking at the process listing while the backing disk is being created, I see 
this qemu-img command line:
15658 ?Ssl0:00 /usr/sbin/libvirtd
23726 ?Sl 0:04  \_ /usr/bin/qemu-img create -f qcow2 -o 
preallocation=falloc,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/live-server.qcow2 41943040K

If I run qemu-img with that preallocation parameter set, even on bionic,
then it also takes a very long time.

On eoan, for comparison:
andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 lazy_refcounts=off refcount_bits=16

real0m0,016s
user0m0,010s
sys 0m0,006s
andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 
image: no-prealloc-image.qcow2
file format: qcow2
virtual size: 40G (42949672960 bytes)
disk size: 17K
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 
17K no-prealloc-image.qcow2
andreas@nsn7:~$ 


and now with preallocation=falloc:
andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc 
with-prealloc-image.qcow2 40G
Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16

real1m43,196s
user0m3,564s
sys 1m26,720s
andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 
image: with-prealloc-image.qcow2
file format: qcow2
virtual size: 40G (42949672960 bytes)
disk size: 2.7M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 
2,8Mwith-prealloc-image.qcow2
andreas@nsn7:~$

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libvirt-daemon 5.4.0-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Mon Oct  7 11:36:03 2019
InstallationDate: Installed on 2019-10-07 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006)
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml']
modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml']
modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml']
modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml']
modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml']
modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml']
modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml']
modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml']
modified.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-mac-broadcast.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-broadcast.xml']
modified.conffile..etc.libvirt.nwfilter.no-mac-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-other-l2-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-other-l2-traffic.xml']
modified.conffile..etc.libvirt.nwfilter.no-other-rarp-traffic.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-other-rarp-traffic.xml']

[Bug 1847105] [NEW] very slow disk creation, snapshotting

2019-10-07 Thread Andreas Hasenack
Public bug reported:

This is a regression in eoan for me. I use virt-manager to create vms,
and I noticed that creating one now takes more than a minute.

Looking at the process listing while the backing disk is being created, I see 
this qemu-img command line:
15658 ?Ssl0:00 /usr/sbin/libvirtd
23726 ?Sl 0:04  \_ /usr/bin/qemu-img create -f qcow2 -o 
preallocation=falloc,compat=1.1,lazy_refcounts 
/var/lib/libvirt/images/live-server.qcow2 41943040K

If I run qemu-img with that preallocation parameter set, even on bionic,
then it also takes a very long time.

On eoan, for comparison:
andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G
Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 lazy_refcounts=off refcount_bits=16

real0m0,016s
user0m0,010s
sys 0m0,006s
andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 
image: no-prealloc-image.qcow2
file format: qcow2
virtual size: 40G (42949672960 bytes)
disk size: 17K
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 
17K no-prealloc-image.qcow2
andreas@nsn7:~$ 


and now with preallocation=falloc:
andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc 
with-prealloc-image.qcow2 40G
Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 
cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16

real1m43,196s
user0m3,564s
sys 1m26,720s
andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 
image: with-prealloc-image.qcow2
file format: qcow2
virtual size: 40G (42949672960 bytes)
disk size: 2.7M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 
2,8Mwith-prealloc-image.qcow2
andreas@nsn7:~$

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libvirt-daemon 5.4.0-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Mon Oct  7 11:36:03 2019
InstallationDate: Installed on 2019-10-07 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006)
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml']
modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml']
modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml']
modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml']
modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 
13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml']
modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/clean-traffic-gateway.xml']
modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml']
modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml']
modified.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-mac-broadcast.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-broadcast.xml']
modified.conffile..etc.libvirt.nwfilter.no-mac-spoofing.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-spoofing.xml']
modified.conffile..etc.libvirt.nwfilter.no-other-l2-traffic.xml: [inaccessible: 
[Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-other-l2-traffic.xml']
modified.conffile..etc.libvirt.nwfilter.no-other-rarp-traffic.xml: 
[inaccessible: [Errno 13] Permission denied: 
'/etc/libvirt/nwfilter/no-other-rarp-traffic.xml']

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-07 Thread Andreas Hasenack
Hi James,

thanks for working on this.

I think you made a mistake in your last commit to the xenial branch:
https://salsa.debian.org/ec0-guest/acme/commit/8346b60b7550b26c8ae0d57a17558fe7c9f64c69

It says one thing, but the actual change has much more. In fact, it's
touching the upstream source code. The package shouldn't even build like
this, given the source won't match the orig tarball.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates

2019-10-07 Thread Andreas Hasenack
** Changed in: haproxy (Ubuntu)
   Status: Expired => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828496

Title:
  service haproxy reload sometimes fails to pick up new TLS certificates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates

2019-10-07 Thread Andreas Hasenack
** Changed in: haproxy (Ubuntu)
   Status: Expired => New

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1828496

Title:
  service haproxy reload sometimes fails to pick up new TLS certificates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-04 Thread Andreas Hasenack
There are other changes needed in the backport from cosmic.
Specifically, python3 support.

The xenial certbot packages are py2 currently, and not all py3
dependencies needed by the cosmic package are available in xenial. These
two are missing:

- python3-parsedatetime
- python3-repoze.sphinx.autointerface

Their py2 counterparts are of course available, but this means we won't
be producing python3-certbot packages, just python-certbot (if 0.27.0
works with py2, that is).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673

Title:
  Certbot will be unable to create new ACME accounts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131

2019-10-04 Thread Andreas Hasenack
Xenial verification

No warnings or errors during upgrade:
Get:1 http://azure.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
base-files amd64 9.4ubuntu4.11 [67.5 kB]
Fetched 67.5 kB in 0s (1,082 kB/s)
(Reading database ... 78928 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu4.11_amd64.deb ...
Unpacking base-files (9.4ubuntu4.11) over (9.4ubuntu4.8) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.5) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.15) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-1060-azure
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Setting up base-files (9.4ubuntu4.11) ...


The motd-news.timer is installed and will run in 7h:
ubuntu@xenial-motd:~$ systemctl list-timers
NEXT LEFT LAST PASSED   
UNIT ACTIVATES
Sat 2019-10-05 02:13:08 UTC  7h left  n/a  n/a  
motd-news.timer  motd-news.service
Sat 2019-10-05 06:01:07 UTC  11h left n/a  n/a  
apt-daily.timer  apt-daily.service
Sat 2019-10-05 06:35:02 UTC  12h left n/a  n/a  
apt-daily-upgrade.timer  apt-daily-upgrade.service
Sat 2019-10-05 18:14:55 UTC  23h left Fri 2019-10-04 18:14:55 UTC  6min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

4 timers listed.
Pass --all to see loaded but inactive timers, too.


motd message is now displayed:
ubuntu@xenial-motd:~$ sudo sh /etc/update-motd.d/50-motd-news --force

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes


Confirmed upon logging in:
andreas@nsnx:~$ ssh ubuntu@13.90.92.78
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.15.0-1057-azure x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes

26 packages can be updated.
0 updates are security updates.

New release '18.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.


*** System restart required ***
Last login: Fri Oct  4 18:15:19 2019 from 187.107.24.4


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836236

Title:
  9.4ubuntu4.9: Broken package because of missing "#" @
  /var/lib/dpkg/info/base-files.postinst +131

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840946] Re: Include cloud-id in user-agent string

2019-10-04 Thread Andreas Hasenack
Bionic verification: passed

Summary of tests:
a) motd message still displayed
b) cloud_id set to $cloudname in user-agent

Tested on: lxd, aws, gce, azure

Using package base-files 10.1ubuntu2.7 from bionic-proposed

Detailed test logs attached.

** Attachment added: "bionic-verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+attachment/5294435/+files/bionic-verification.txt

** Tags removed: verification-needed-bionic
** Tags added: 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/1840946

Title:
  Include cloud-id in user-agent string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840946] Re: Include cloud-id in user-agent string

2019-10-04 Thread Andreas Hasenack
Xenial verification: passed

Summary of tests:
No errors or warnings during package upgrade
a) motd message is now displayed
a.1) motd message displayed on login
b) cloud_id set to $cloudname in user-agent
c) motd-news.timer scheduled to run

Tested on: lxd, aws, gce, azure

Using package base-files 9.4ubuntu4.11 from xenial-proposed

Detailed test logs attached.

** Attachment added: "xenial-verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+attachment/5294436/+files/xenial-verification.txt

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840946

Title:
  Include cloud-id in user-agent string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840946] Re: Include cloud-id in user-agent string

2019-10-04 Thread Andreas Hasenack
Disco verification: passed

Summary of tests:
a) motd message still displayed
b) cloud_id set to $cloudname in user-agent

Tested on: lxd, aws, gce, azure

Using package base-files 10.1ubuntu9.2 from disco-proposed

Detailed test logs attached.

** Attachment added: "disco-verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+attachment/5294434/+files/disco-verification.txt

** Tags removed: verification-needed-disco
** Tags added: verification-done-disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840946

Title:
  Include cloud-id in user-agent string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637800] Re: add a motd script for news

2019-10-04 Thread Andreas Hasenack
Xenial verification

No warnings or errors during upgrade:
Get:1 http://azure.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
base-files amd64 9.4ubuntu4.11 [67.5 kB]
Fetched 67.5 kB in 0s (1,082 kB/s)
(Reading database ... 78928 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu4.11_amd64.deb ...
Unpacking base-files (9.4ubuntu4.11) over (9.4ubuntu4.8) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.5) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.15) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-1060-azure
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Setting up base-files (9.4ubuntu4.11) ...


motd message is now displayed:
ubuntu@xenial-motd:~$ sudo sh /etc/update-motd.d/50-motd-news --force

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes



Confirmed upon logging in:
andreas@nsnx:~$ ssh ubuntu@13.90.92.78
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.15.0-1057-azure x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

 * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

 https://ubuntu.com/kubernetes/docs/release-notes

26 packages can be updated.
0 updates are security updates.

New release '18.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.


*** System restart required ***
Last login: Fri Oct  4 18:15:19 2019 from 187.107.24.4


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637800

Title:
  add a motd script for news

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840946] Re: Include cloud-id in user-agent string

2019-10-04 Thread Andreas Hasenack
The verification log is quite extensive and verbose, since it's about 3
ubuntu releases and on 4 clouds: lxd, aws, gce, azure. I'll post a
summary and an attachment with the detailed log for each.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840946

Title:
  Include cloud-id in user-agent string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826158] Re: Failed to install guestOS ubuntu-19.04-live-server-amd64.iso(GA) in ESXi with new installer subiquity 19.04.5 when create VM with NVME disk

2019-10-03 Thread Andreas Hasenack
So, on the GA iso, one cannot get to the step where the installer is
updated. Do you get at least to the language selection prompt, i.e.,
does the installer at least stop somewhere asking you a question? You
say:

"4. We get a continuous flash at early install stage."

I ask because if you are able to switch to another console, you can
update the installer manually with a command like:

sudo snap refresh subiquity

But if you can't get that far with the GA iso, then I think just an iso
respin would fix this.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826158

Title:
  Failed to install guestOS ubuntu-19.04-live-server-amd64.iso(GA) in
  ESXi with new installer subiquity 19.04.5 when create VM with NVME
  disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1826158/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1826158] Re: Failed to install guestOS ubuntu-19.04-live-server-amd64.iso(GA) in ESXi with new installer subiquity 19.04.5 when create VM with NVME disk

2019-10-03 Thread Andreas Hasenack
So, on the GA iso, one cannot get to the step where the installer is
updated. Do you get at least to the language selection prompt, i.e.,
does the installer at least stop somewhere asking you a question? You
say:

"4. We get a continuous flash at early install stage."

I ask because if you are able to switch to another console, you can
update the installer manually with a command like:

sudo snap refresh subiquity

But if you can't get that far with the GA iso, then I think just an iso
respin would fix this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826158

Title:
  Failed to install guestOS ubuntu-19.04-live-server-amd64.iso(GA) in
  ESXi with new installer subiquity 19.04.5 when create VM with NVME
  disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1826158/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638210] Re: saidar segmentation fault

2019-10-03 Thread Andreas Hasenack
This may be tricky to reproduce reliably on a test machine, unless you
own a system where it is already happening.

In the upstream bug at
https://github.com/libstatgrab/libstatgrab/issues/102, there is a hint
that
https://github.com/libstatgrab/libstatgrab/commit/84fd8c38ee4feb0117ed22ab56f6b46661411ec6
might fix the problem. For SRU purposes, we need a verification step.
Would people affected by this be able to test a package from a ppa with
that patch to see if it fixes the problem?

** Bug watch added: github.com/libstatgrab/libstatgrab/issues #102
   https://github.com/libstatgrab/libstatgrab/issues/102

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1638210

Title:
  saidar segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libstatgrab/+bug/1638210/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1638210] Re: saidar segmentation fault

2019-10-03 Thread Andreas Hasenack
This may be tricky to reproduce reliably on a test machine, unless you
own a system where it is already happening.

In the upstream bug at
https://github.com/libstatgrab/libstatgrab/issues/102, there is a hint
that
https://github.com/libstatgrab/libstatgrab/commit/84fd8c38ee4feb0117ed22ab56f6b46661411ec6
might fix the problem. For SRU purposes, we need a verification step.
Would people affected by this be able to test a package from a ppa with
that patch to see if it fixes the problem?

** Bug watch added: github.com/libstatgrab/libstatgrab/issues #102
   https://github.com/libstatgrab/libstatgrab/issues/102

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638210

Title:
  saidar segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libstatgrab/+bug/1638210/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-03 Thread Andreas Hasenack
PPA with test packages: https://launchpad.net/~ahasenack/+archive/ubuntu
/october-certbot-sru/

I reverted the debhelper changes mentioned above in these ppa builds

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-03 Thread Andreas Hasenack
PPA with test packages (still building certbot for bionic atm):
https://launchpad.net/~ahasenack/+archive/ubuntu/october-certbot-sru/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673

Title:
  Certbot will be unable to create new ACME accounts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837673] Re: Certbot will be unable to create new ACME accounts

2019-10-03 Thread Andreas Hasenack
> To solve this problem, I recommend backporting the Certbot packages from 
> Cosmic to Bionic
> and Xenial.

Cosmic, which is EOL now, had 0.27.0-1:

python-certbot (0.27.0-1) unstable; urgency=medium

  * New upstream version 0.27.0
  * Refresh patch after upstream migration to codecov
  * Bump python-sphinx requirement defensively; bump S-V with no changes
  * Bump dep on python-acme to 0.26.0~

 -- Harlan Lieberman-Berg   Wed, 05 Sep 2018
20:29:44 -0400

Noted the python-acme >= 0.26.0~ requirement. B and X have
0.22.2-1something, and also as noted, but #1836823 is bumping that to
0.31.0-2.


** Also affects: python-certbot (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: python-certbot (Ubuntu Eoan)
   Importance: Undecided
 Assignee: James Hebden (ec0)
   Status: New

** Changed in: python-certbot (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: python-certbot (Ubuntu Eoan)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673

Title:
  Certbot will be unable to create new ACME accounts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-03 Thread Andreas Hasenack
Same thing for bionic, which also has debhelper 11 out of the box, and
the existing bionic package (0.22.2-1ubuntu0.1) is using that level.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-03 Thread Andreas Hasenack
@ec0 sorry if this was discussed before, but I don't see it here in the
bug. Why did you downgrade the debhelper version in the disco branch?

The current package in disco, 0.31.0-1, is using debhelper 11, but your
commit ca2913310288b2bb72976cce29b383d52e233ac0 changes that to 10, and
build-depends on debhelper >= 9~ even. Maybe you just wanted to have the
source package the same as in xenial, which is at debhelper 9 level?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-03 Thread Andreas Hasenack
This isn't building on xenial, due to unsatisfied build-depends:
The following packages have unmet dependencies:
 builddeps:./ : Depends: python-cryptography (>= 1.3.4) but 1.2.3-1ubuntu0.2 is 
to be installed
Depends: python-idna (>= 2.5) but 2.0-3 is to be installed
Depends: python3-cryptography (>= 1.3.4) but 1.2.3-1ubuntu0.2 
is to be installed
Depends: python3-idna (>= 2.5) but 2.0-3 is to be installed

xenial has:
python-cryptography{,3} 1.2.3-1ubuntu0.2
python-idna{,3} 2.0-3

@ec0 how did you build and test this updated package on xenial? Did you
have something installed from outside of the ubuntu archive, or did you
backport those dependencies as well?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-03 Thread Andreas Hasenack
I'm doing the second review and will handle uploading/sponsoring.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836823] Re: python-acme will break on November 1st

2019-10-02 Thread Andreas Hasenack
Due to bug #1837673, we will also want to update the certbot packages.
The ones available in disco, 0.31.0, seem like a good candidate, since
they match the 0.31.0 version for python-acme we want here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836823

Title:
  python-acme will break on November 1st

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838525] Re: LVM setup fails to install grub on virtio storage

2019-10-01 Thread Andreas Hasenack
The lvm with virtio and a serial number case worked, i.e, the
installation finished, and grub was installed on /dev/vda.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838525

Title:
  LVM setup fails to install grub on virtio storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838525] Re: LVM setup fails to install grub on virtio storage

2019-10-01 Thread Andreas Hasenack
/dev/disk/by-id contents in three cases: lvm without virtio, lvm with
virtio, and lvm with virtio and a serial number for vda

** Attachment added: "disk-by-id.png"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+attachment/5293325/+files/disk-by-id.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838525

Title:
  LVM setup fails to install grub on virtio storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838525] Re: LVM setup fails to install grub on virtio storage

2019-10-01 Thread Andreas Hasenack
Looks like we are narrowing this down to a virtio device with no serial
number. On a bionic host, if I manually add a serial number to the
virtio device (in virt-manager, just before starting the installation,
for example) then this works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838525

Title:
  LVM setup fails to install grub on virtio storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838525] Re: LVM setup fails to install grub on virtio storage

2019-10-01 Thread Andreas Hasenack
boot device prompt in three cases: lvm without virtio, lvm with virtio,
and lvm with virtio and a serial number for vda


** Attachment added: "which-dev-is-first.png"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+attachment/5293326/+files/which-dev-is-first.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838525

Title:
  LVM setup fails to install grub on virtio storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637800] Re: add a motd script for news

2019-09-30 Thread Andreas Hasenack
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373411

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637800

Title:
  add a motd script for news

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840946] Re: Include cloud-id in user-agent string

2019-09-30 Thread Andreas Hasenack
** Description changed:

  [Impact]
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
+ [Test Case]
+ a) confirm that the motd message is still displayed:
+ $ sudo sh /etc/update-motd.d/50-motd-news --force
  
- [Test Case]
+  * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
+Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.
  
-  * detailed instructions how to reproduce the bug
+  https://ubuntu.com/kubernetes/docs/release-notes
  
-  * these should allow someone who is not familiar with the affected
-    package to reproduce the bug and verify that the updated package fixes
-    the problem.
+ b) confirm that cloud_id is set in the user-agent. This should be tested
+ in lxd, gce, aws, and azure. Here is an example for lxd:
+ 
+ $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
+ + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com
+ 
+ For each of the mentioned clouds, we expect cloud_id to be set to their
+ short names: aws, gce, azure.
  
  [Regression Potential]
+ This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
+ - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
+ - sanitize the output of cloud-id, and truncate it to a maximum length
+ - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.
  
-  * discussion of how regressions are most likely to manifest as a result
- of this change.
- 
-  * It is assumed that any SRU candidate patch is well-tested before
-    upload and has a low overall risk of regression, but it's important
-    to make the effort to think about what ''could'' happen in the
-    event of a regression.
- 
-  * This both shows the SRU team that the risks have been considered,
-    and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
- 
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.
  
  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

** Description changed:

  [Impact]
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force
  
-  * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
-Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.
+  * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
+    Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.
  
-  https://ubuntu.com/kubernetes/docs/release-notes
+  https://ubuntu.com/kubernetes/docs/release-notes
  
  b) confirm that cloud_id is set in the user-agent. This should be tested
  in lxd, gce, aws, and azure. Here is an example for lxd:
  
  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 

[Bug 1840946] Re: [FFe] include cloud-id in user-agent string

2019-09-30 Thread Andreas Hasenack
** Description changed:

- I'm preemptively filing this bug in case this isn't uploaded before the
- feature freeze.
+ [Impact]
+ 
+  * An explanation of the effects of the bug on users and
+ 
+  * justification for backporting the fix to the stable release.
+ 
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [Test Case]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+ [Regression Potential]
+ 
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ [Original Description]
+ I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

** Summary changed:

- [FFe] include cloud-id in user-agent string
+ Include cloud-id in user-agent string

** Description changed:

  [Impact]
  
-  * An explanation of the effects of the bug on users and
+ We would like to include a cloud_id/$name parameter to the user-agent
+ string that is sent to https://motd.ubuntu.com. This will allow the
+ server part of motd.ubuntu.com to serve cloud-specific content if one is
+ available.
  
-  * justification for backporting the fix to the stable release.
- 
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
  
  [Test Case]
  
-  * detailed instructions how to reproduce the bug
+  * detailed instructions how to reproduce the bug
  
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+  * these should allow someone who is not familiar with the affected
+    package to reproduce the bug and verify that the updated package fixes
+    the problem.
  
  [Regression Potential]
  
-  * discussion of how regressions are most likely to manifest as a result
+  * discussion of how regressions are most likely to manifest as a result
  of this change.
  
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
  
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ 
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
  
  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840946

Title:
  Include cloud-id in user-agent string

To manage 

[Bug 1637800] Re: add a motd script for news

2019-09-27 Thread Andreas Hasenack
I'm addressing this in a new upload.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637800

Title:
  add a motd script for news

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637800] Re: add a motd script for news

2019-09-27 Thread Andreas Hasenack
+ [ -d /run/systemd/system ]
+ systemctl --system daemon-reload
+ deb-systemd-invoke start motd-news.service
motd-news.service is a disabled or a static unit, not starting it.
+ [ -d /run/systemd/system ]
+ systemctl --system daemon-reload
+ deb-systemd-invoke start motd-news.timer
motd-news.timer is a disabled or a static unit, not starting it.

The xenial package is not using debhelper, and the manual entries in
postinst do not enable it, just try to start it.

This is the bit that dh_systemd_enable adds to postinst in bionic, for example:
# Automatically added by dh_systemd_enable/11.1.6ubuntu2
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
# This will only remove masks created by d-s-h on package removal.
deb-systemd-helper unmask 'motd-news.timer' >/dev/null || true

# was-enabled defaults to true, so new installations run enable.
if deb-systemd-helper --quiet was-enabled 'motd-news.timer'; then
# Enables the unit on first installation, creates new
# symlinks on upgrades if the unit file has changed.
deb-systemd-helper enable 'motd-news.timer' >/dev/null || true
else
# Update the statefile to add new symlinks (if any), which need 
to be
# cleaned up on purge. Also remove old symlinks.
deb-systemd-helper update-state 'motd-news.timer' >/dev/null || 
true
fi
fi

And then come the deb-systemd-invoke start bits that were added manually
to the xenial package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637800

Title:
  add a motd script for news

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840946] Re: [FFe] include cloud-id in user-agent string

2019-09-27 Thread Andreas Hasenack
** Also affects: base-files (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: base-files (Ubuntu Xenial)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: base-files (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: base-files (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: base-files (Ubuntu Disco)
   Status: New => In Progress

** Changed in: base-files (Ubuntu Disco)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: base-files (Ubuntu Bionic)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Description changed:

  I'm preemptively filing this bug in case this isn't uploaded before the
  feature freeze.
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370
- 
- That MP is also fixing a bug where curl would not return a failure if
- the server status is not 200.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840946

Title:
  [FFe] include cloud-id in user-agent string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840946] Re: [FFe] include cloud-id in user-agent string

2019-09-27 Thread Andreas Hasenack
** Also affects: base-files (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: base-files (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840946

Title:
  [FFe] include cloud-id in user-agent string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838525] Re: LVM setup fails to install grub on virtio storage

2019-09-27 Thread Andreas Hasenack
set -x of grub-installer in the virtio (failing) case

** Attachment added: "grub-install-virtio-case.log"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+attachment/5291785/+files/grub-install-virtio-case.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838525

Title:
  LVM setup fails to install grub on virtio storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838525] Re: LVM setup fails to install grub on virtio storage

2019-09-27 Thread Andreas Hasenack
set -x of grub-installer in the non-virtio (working) case

** Attachment added: "grub-install-novirtio-case.log"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+attachment/5291786/+files/grub-install-novirtio-case.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838525

Title:
  LVM setup fails to install grub on virtio storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838525] Re: LVM setup fails to install grub on virtio storage

2019-09-27 Thread Andreas Hasenack
Do we have a sh -x run of grub-installer with lvm + virtio and lvm +
sata?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838525

Title:
  LVM setup fails to install grub on virtio storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842701] Re: Apache2 Balancer Manager mod_proxy_balancer not working after Update

2019-09-26 Thread Andreas Hasenack
** Bug watch added: Debian Bug tracker #941202
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202

** Also affects: apache2 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842701

Title:
  Apache2 Balancer Manager mod_proxy_balancer not working after Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1842701/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1842701] Re: Apache2 Balancer Manager mod_proxy_balancer not working after Update

2019-09-26 Thread Andreas Hasenack
** Bug watch added: Debian Bug tracker #941202
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202

** Also affects: apache2 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842701

Title:
  Apache2 Balancer Manager mod_proxy_balancer not working after Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1842701/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845335] [NEW] Update DEP8 tests to python3

2019-09-25 Thread Andreas Hasenack
Public bug reported:

d/t/test-squid.py should be updated to python3

** Affects: squid (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: dep8

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/1845335

Title:
  Update DEP8 tests to python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1845335/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1845335] Re: Update DEP8 tests to python3

2019-09-25 Thread Andreas Hasenack
According to git log, https://git.launchpad.net/qa-regression-
testing/tree/scripts/test-squid.py already got some changes to work with
py3.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845335

Title:
  Update DEP8 tests to python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1845335/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1845335] Re: Update DEP8 tests to python3

2019-09-25 Thread Andreas Hasenack
According to git log, https://git.launchpad.net/qa-regression-
testing/tree/scripts/test-squid.py already got some changes to work with
py3.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845335

Title:
  Update DEP8 tests to python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1845335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845335] [NEW] Update DEP8 tests to python3

2019-09-25 Thread Andreas Hasenack
Public bug reported:

d/t/test-squid.py should be updated to python3

** Affects: squid (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: dep8

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845335

Title:
  Update DEP8 tests to python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1845335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845334] [NEW] Update DEP8 test to python3

2019-09-25 Thread Andreas Hasenack
Public bug reported:

The postfix dep8 tests[1][2] should be updated to python3.

Some work about this was already done in the qa-regression-testing[3][4]
repository, which is where this test came from originally, so it should
hopefully just be a matter of cherry-picking the needed fixes. We could
also take the opportunity to update the script with new tests that have
been added.

Since postfix is a sync from debian, once we know the updated tests work
with py3 on both debian and ubuntu, the changes should be proposed to
Debian via salsa at https://salsa.debian.org/postfix-team/postfix-dev

1. https://git.launchpad.net/ubuntu/+source/postfix/tree/debian/tests/testlib.py
2. 
https://git.launchpad.net/ubuntu/+source/postfix/tree/debian/tests/test-postfix.py
3. https://git.launchpad.net/qa-regression-testing/tree/scripts/testlib.py
4. https://git.launchpad.net/qa-regression-testing/tree/scripts/test-postfix.py

** Affects: postfix (Ubuntu)
 Importance: Undecided
 Assignee: Andreas Hasenack (ahasenack)
 Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845334

Title:
  Update DEP8 test to python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845334] [NEW] Update DEP8 test to python3

2019-09-25 Thread Andreas Hasenack
Public bug reported:

The postfix dep8 tests[1][2] should be updated to python3.

Some work about this was already done in the qa-regression-testing[3][4]
repository, which is where this test came from originally, so it should
hopefully just be a matter of cherry-picking the needed fixes. We could
also take the opportunity to update the script with new tests that have
been added.

Since postfix is a sync from debian, once we know the updated tests work
with py3 on both debian and ubuntu, the changes should be proposed to
Debian via salsa at https://salsa.debian.org/postfix-team/postfix-dev

1. https://git.launchpad.net/ubuntu/+source/postfix/tree/debian/tests/testlib.py
2. 
https://git.launchpad.net/ubuntu/+source/postfix/tree/debian/tests/test-postfix.py
3. https://git.launchpad.net/qa-regression-testing/tree/scripts/testlib.py
4. https://git.launchpad.net/qa-regression-testing/tree/scripts/test-postfix.py

** Affects: postfix (Ubuntu)
 Importance: Undecided
 Assignee: Andreas Hasenack (ahasenack)
 Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1845334

Title:
  Update DEP8 test to python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1842428] Re: [FFe] Version 1.5.2 needed for kernels >= 5.1

2019-09-20 Thread Andreas Hasenack
** Changed in: pmdk-convert (Ubuntu)
   Status: Triaged => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842428

Title:
  [FFe] Version 1.5.2 needed for kernels >= 5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pmdk-convert/+bug/1842428/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844521] Re: DEP8 test reaches out to demo.wireguard.com

2019-09-19 Thread Andreas Hasenack
** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844521

Title:
  DEP8 test reaches out to demo.wireguard.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1844521/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843804] Re: DEP8 segfault on arm64

2019-09-19 Thread Andreas Hasenack
By blocking the ruby2.5 migration this also affects ruby2.5 (for
tracking)

** Also affects: ruby2.5 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.5 in Ubuntu.
https://bugs.launchpad.net/bugs/1843804

Title:
  DEP8 segfault on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1843804/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1843804] Re: DEP8 segfault on arm64

2019-09-19 Thread Andreas Hasenack
By blocking the ruby2.5 migration this also affects ruby2.5 (for
tracking)

** Also affects: ruby2.5 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804

Title:
  DEP8 segfault on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1843804/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1810827] Re: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

2019-09-19 Thread Andreas Hasenack
There is a fix available, but is not frequent enough and there is a
simple workaround: restart instead of reload. Also only that specific
"force group" config change is affected.

** Tags removed: server-next

** Also affects: samba (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: samba (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: samba (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: samba (Ubuntu Bionic)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810827

Title:
  
/usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1810827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1810827] Re: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

2019-09-19 Thread Andreas Hasenack
I mean the crash is not frequent enough.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810827

Title:
  
/usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1810827/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1810827] Re: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

2019-09-19 Thread Andreas Hasenack
I mean the crash is not frequent enough.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810827

Title:
  
/usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1810827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1810827] Re: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

2019-09-19 Thread Andreas Hasenack
There is a fix available, but is not frequent enough and there is a
simple workaround: restart instead of reload. Also only that specific
"force group" config change is affected.

** Tags removed: server-next

** Also affects: samba (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: samba (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: samba (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: samba (Ubuntu Bionic)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810827

Title:
  
/usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1810827/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1843804] Re: DEP8 segfault on arm64

2019-09-19 Thread Andreas Hasenack
** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804

Title:
  DEP8 segfault on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-ferret/+bug/1843804/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10

2019-09-18 Thread Andreas Hasenack
** Changed in: nagios-plugins (Ubuntu)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Tags removed: server-next

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516451

Title:
  check_disk plugin broken after upgrade to 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1516451/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10

2019-09-18 Thread Andreas Hasenack
** Changed in: nagios-plugins (Ubuntu)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Tags removed: server-next

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1516451

Title:
  check_disk plugin broken after upgrade to 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1516451/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1844521] [NEW] DEP8 test reaches out to demo.wireguard.com

2019-09-18 Thread Andreas Hasenack
Public bug reported:

The DEP8 test of wireguard reaches out to demo.wireguard.com. Internet
access at large like this is blocked in the Ubuntu autopkgtest
environment, and this test therefore fails:

autopkgtest [20:25:56]: test ncat-client: [---
Verifying that the existing network does not already use 192.168.4.1 ...
Loading wireguard configuration to demo server...
/usr/share/doc/wireguard-tools/examples/ncat-client-server/client.sh: connect: 
Connection timed out
/usr/share/doc/wireguard-tools/examples/ncat-client-server/client.sh: line 8: 
/dev/tcp/demo.wireguard.com/42912: Connection timed out

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


** Tags: dep8

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844521

Title:
  DEP8 test reaches out to demo.wireguard.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1844521/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842428] Re: Version 1.5.2 needed for kernels >= 5.1

2019-09-13 Thread Andreas Hasenack
** Description changed:

  https://github.com/pmem/pmdk-convert/releases/tag/1.5.2
  
  Eoan has kernel 5.2
  
  Debian just uploaded 1.5.2: https://tracker.debian.org/news/1061139
  /accepted-pmdk-convert-152-1-source-into-unstable/
  
  This is the diff the pmdk-convert itself:
  1.5.1..1.5.2 diff:
  https://github.com/pmem/pmdk-convert/compare/1.5.1...1.5.2
  
  This is the source package diff (there are no ubuntu changes):
  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/pmdk-convert/commit/?id=ae70671e4ae6ef1d0fd0da611e2e2ad88d3ffafc
  
  Mostly test fixes, but the detail is in this commit, shown in the diff above 
as well:
  
https://github.com/pmem/pmdk-convert/commit/0dbf1d98c353ec91aa9a9944e2ecb6595a5019ae
  
  That tells the build system to fetch the latest pmdk versions of each
  pmdk release. The debian package has these in a separate orig tarball.
  
  Specifically, we are getting the following pmdk updates, when compared
  with the pmdk-convert package we currently have in eoan:
  
  https://github.com/pmem/pmdk/compare/1.5.1...1.5.2
  https://github.com/pmem/pmdk/compare/1.4.2...1.4.3
  https://github.com/pmem/pmdk/compare/1.3.1...1.3.3
  https://github.com/pmem/pmdk/compare/1.2.3...1.2.4
  
  I believe this to not be that relevant, because they are used only for
  conversion tasks from old pool formats. The actual pmdk package, which
  is at 1.6.1 in eoan, is what matters for day-to-day operations, and it
  is not being changed.
  
  In the comments below you can see I tried inspecting all the changes
  listed above and to see if I needed a feature freeze exception, and I
  think I do, so I stopped. But as I said, these updates are only used in
  conversion tasks.
  
  PPA build, with eoan-proposed enabled, and both supported arches as well: 
amd64 and arm64
  https://launchpad.net/~ahasenack/+archive/ubuntu/pmdk-convert-ffe/+packages
  
  Here is a simple test. I created this pool using pmdk from bionic (version 
1.4):
- $ pmdk-convert --to=1.5 pools-old/pool-obj
+ multipass@e1:~/test$ pmempool info old.pool |grep ^Major
+ Major: 4
+ multipass@e1:~/test$ pmdk-convert old.pool
  This tool will update the pool to the specified layout version.
  This process is NOT fail-safe.
  Proceed only if the pool has been backed up or
  the risks are fully understood and acceptable.
  Hit Ctrl-C now if you want to stop or Enter to continue.
  
  Starting conversion from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)
  Converting from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)... Done
+ multipass@e1:~/test$ pmempool info old.pool |grep ^Major
+ Major: 5
+ 
+ 
+ I used pmdk-convert from the PPA:
+ $ apt-cache policy pmdk-convert
+ multipass@e1:~/test$ apt-cache policy pmdk-convert
+ pmdk-convert:
+   Installed: 1.5.2-1build1~ppa1
+   Candidate: 1.5.2-1build1~ppa1
+   Version table:
+  *** 1.5.2-1build1~ppa1 500
+ 500 http://ppa.launchpad.net/ahasenack/pmdk-convert-ffe/ubuntu 
eoan/main amd64 Packages
+ 
+ Running kernel:
+ multipass@e1:~/test$ uname -a
+ Linux e1 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  
  v5 is also the format used by pmdk 1.6.x:
- ubuntu@eoan-pmdk-convert:~/test$ pmempool create obj pool-with-pmdk-1.6.1.pool
- ubuntu@eoan-pmdk-convert:~/test$ pmempool info pool-with-pmdk-1.6.1.pool 
|grep ^Major
+ multipass@e1:~/test$ pmempool create obj pool-with-pmdk-1.6.1.pool
+ multipass@e1:~/test$ pmempool info pool-with-pmdk-1.6.1.pool |grep ^Major
  Major: 5
+ 
+ I also ran the above tests with the bionic kernel:
+ 4.15.0-62-generic #69

** Summary changed:

- Version 1.5.2 needed for kernels >= 5.1
+ [FFe] Version 1.5.2 needed for kernels >= 5.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842428

Title:
  [FFe] Version 1.5.2 needed for kernels >= 5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pmdk-convert/+bug/1842428/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842428] Re: Version 1.5.2 needed for kernels >= 5.1

2019-09-13 Thread Andreas Hasenack
** Description changed:

  https://github.com/pmem/pmdk-convert/releases/tag/1.5.2
  
  Eoan has kernel 5.2
  
  Debian just uploaded 1.5.2: https://tracker.debian.org/news/1061139
  /accepted-pmdk-convert-152-1-source-into-unstable/
  
  We should check the diff and sync it if no FFe is deemed necessary.
  
  This is the diff the pmdk-convert itself:
  1.5.1..1.5.2 diff:
  https://github.com/pmem/pmdk-convert/compare/1.5.1...1.5.2
  
  Mostly test fixes, but the detail is in this commit, shown in the diff above 
as well:
  
https://github.com/pmem/pmdk-convert/commit/0dbf1d98c353ec91aa9a9944e2ecb6595a5019ae
  
  That tells the build system to fetch the latest pmdk versions of each
  pmdk release. The debian package has these in a separate orig tarball.
  
  Specifically, we are getting the following pmdk updates, when compared
  with the pmdk-convert package we currently have in eoan:
  
  https://github.com/pmem/pmdk/compare/1.5.1...1.5.2
  https://github.com/pmem/pmdk/compare/1.4.2...1.4.3
  https://github.com/pmem/pmdk/compare/1.3.1...1.3.3
  https://github.com/pmem/pmdk/compare/1.2.3...1.2.4
  
  I believe this to not be that relevant, because they are used only for
  conversion tasks from old pool formats. The actual pmdk package, which
  is at 1.6.1 in eoan, is what matters for day-to-day operations, and it
  is not being changed.
  
  In the comments below you can see I tried inspecting all the changes
  listed above and to see if I needed a feature freeze exception, and I
  think I do, so I stopped. But as I said, these updates are only used in
  conversion tasks.
  
  PPA build, with eoan-proposed enabled, and both supported arches as well: 
amd64 and arm64
  https://launchpad.net/~ahasenack/+archive/ubuntu/pmdk-convert-ffe/+packages
+ 
+ Here is a simple test. I created this pool using pmdk from bionic (version 
1.4):
+ $ pmdk-convert --to=1.5 pools-old/pool-obj 
+ This tool will update the pool to the specified layout version.
+ This process is NOT fail-safe.
+ Proceed only if the pool has been backed up or
+ the risks are fully understood and acceptable.
+ Hit Ctrl-C now if you want to stop or Enter to continue.
+ 
+ Starting conversion from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)
+ Converting from v4 (PMDK 1.3, PMDK 1.4) to v5 (PMDK 1.5)... Done
+ 
+ v5 is also the format used by pmdk 1.6.x:
+ ubuntu@eoan-pmdk-convert:~/test$ pmempool create obj pool-with-pmdk-1.6.1.pool
+ ubuntu@eoan-pmdk-convert:~/test$ pmempool info pool-with-pmdk-1.6.1.pool 
|grep ^Major
+ Major: 5

** Description changed:

  https://github.com/pmem/pmdk-convert/releases/tag/1.5.2
  
  Eoan has kernel 5.2
  
  Debian just uploaded 1.5.2: https://tracker.debian.org/news/1061139
  /accepted-pmdk-convert-152-1-source-into-unstable/
  
- We should check the diff and sync it if no FFe is deemed necessary.
- 
  This is the diff the pmdk-convert itself:
  1.5.1..1.5.2 diff:
  https://github.com/pmem/pmdk-convert/compare/1.5.1...1.5.2
+ 
+ This is the source package diff (there are no ubuntu changes):
+ 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/pmdk-convert/commit/?id=ae70671e4ae6ef1d0fd0da611e2e2ad88d3ffafc
  
  Mostly test fixes, but the detail is in this commit, shown in the diff above 
as well:
  
https://github.com/pmem/pmdk-convert/commit/0dbf1d98c353ec91aa9a9944e2ecb6595a5019ae
  
  That tells the build system to fetch the latest pmdk versions of each
  pmdk release. The debian package has these in a separate orig tarball.
  
  Specifically, we are getting the following pmdk updates, when compared
  with the pmdk-convert package we currently have in eoan:
  
  https://github.com/pmem/pmdk/compare/1.5.1...1.5.2
  https://github.com/pmem/pmdk/compare/1.4.2...1.4.3
  https://github.com/pmem/pmdk/compare/1.3.1...1.3.3
  https://github.com/pmem/pmdk/compare/1.2.3...1.2.4
  
  I believe this to not be that relevant, because they are used only for
  conversion tasks from old pool formats. The actual pmdk package, which
  is at 1.6.1 in eoan, is what matters for day-to-day operations, and it
  is not being changed.
  
  In the comments below you can see I tried inspecting all the changes
  listed above and to see if I needed a feature freeze exception, and I
  think I do, so I stopped. But as I said, these updates are only used in
  conversion tasks.
  
  PPA build, with eoan-proposed enabled, and both supported arches as well: 
amd64 and arm64
  https://launchpad.net/~ahasenack/+archive/ubuntu/pmdk-convert-ffe/+packages
  
  Here is a simple test. I created this pool using pmdk from bionic (version 
1.4):
- $ pmdk-convert --to=1.5 pools-old/pool-obj 
+ $ pmdk-convert --to=1.5 pools-old/pool-obj
  This tool will update the pool to the specified layout version.
  This process is NOT fail-safe.
  Proceed only if the pool has been backed up or
  the risks are fully understood and acceptable.
  Hit Ctrl-C now if you want to stop or Enter to continue.
  
  Starting conversion from v4 (PMDK 1.3, 

[Bug 1842428] Re: Version 1.5.2 needed for kernels >= 5.1

2019-09-13 Thread Andreas Hasenack
** Description changed:

  https://github.com/pmem/pmdk-convert/releases/tag/1.5.2
  
  Eoan has kernel 5.2
  
  Debian just uploaded 1.5.2: https://tracker.debian.org/news/1061139
  /accepted-pmdk-convert-152-1-source-into-unstable/
  
  We should check the diff and sync it if no FFe is deemed necessary.
+ 
+ This is the diff the pmdk-convert itself:
+ 1.5.1..1.5.2 diff:
+ https://github.com/pmem/pmdk-convert/compare/1.5.1...1.5.2
+ 
+ Mostly test fixes, but the detail is in this commit, shown in the diff above 
as well:
+ 
https://github.com/pmem/pmdk-convert/commit/0dbf1d98c353ec91aa9a9944e2ecb6595a5019ae
+ 
+ That tells the build system to fetch the latest pmdk versions of each
+ pmdk release. The debian package has these in a separate orig tarball.
+ 
+ Specifically, we are getting the following pmdk updates, when compared
+ with the pmdk-convert package we currently have in eoan:
+ 
+ https://github.com/pmem/pmdk/compare/1.5.1...1.5.2
+ https://github.com/pmem/pmdk/compare/1.4.2...1.4.3
+ https://github.com/pmem/pmdk/compare/1.3.1...1.3.3
+ https://github.com/pmem/pmdk/compare/1.2.3...1.2.4
+ 
+ I believe this to not be that relevant, because they are used only for
+ conversion tasks from old pool formats. The actual pmdk package, which
+ is at 1.6.1 in eoan, is what matters for day-to-day operations, and it
+ is not being changed.
+ 
+ In the comments below you can see I tried inspecting all the changes
+ listed above and to see if I needed a feature freeze exception, and I
+ think I do, so I stopped. But as I said, these updates are only used in
+ conversion tasks.

** Description changed:

  https://github.com/pmem/pmdk-convert/releases/tag/1.5.2
  
  Eoan has kernel 5.2
  
  Debian just uploaded 1.5.2: https://tracker.debian.org/news/1061139
  /accepted-pmdk-convert-152-1-source-into-unstable/
  
  We should check the diff and sync it if no FFe is deemed necessary.
  
  This is the diff the pmdk-convert itself:
  1.5.1..1.5.2 diff:
  https://github.com/pmem/pmdk-convert/compare/1.5.1...1.5.2
  
  Mostly test fixes, but the detail is in this commit, shown in the diff above 
as well:
  
https://github.com/pmem/pmdk-convert/commit/0dbf1d98c353ec91aa9a9944e2ecb6595a5019ae
  
  That tells the build system to fetch the latest pmdk versions of each
  pmdk release. The debian package has these in a separate orig tarball.
  
  Specifically, we are getting the following pmdk updates, when compared
  with the pmdk-convert package we currently have in eoan:
  
  https://github.com/pmem/pmdk/compare/1.5.1...1.5.2
  https://github.com/pmem/pmdk/compare/1.4.2...1.4.3
  https://github.com/pmem/pmdk/compare/1.3.1...1.3.3
  https://github.com/pmem/pmdk/compare/1.2.3...1.2.4
  
  I believe this to not be that relevant, because they are used only for
  conversion tasks from old pool formats. The actual pmdk package, which
  is at 1.6.1 in eoan, is what matters for day-to-day operations, and it
  is not being changed.
  
  In the comments below you can see I tried inspecting all the changes
  listed above and to see if I needed a feature freeze exception, and I
  think I do, so I stopped. But as I said, these updates are only used in
  conversion tasks.
+ 
+ PPA build, with eoan-proposed enabled, and both supported arches as well: 
amd64 and arm64
+ https://launchpad.net/~ahasenack/+archive/ubuntu/pmdk-convert-ffe/+packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842428

Title:
  Version 1.5.2 needed for kernels >= 5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pmdk-convert/+bug/1842428/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804542] Re: [SRU] Multiple intermittent socket failures during name resolutions

2019-09-13 Thread Andreas Hasenack
Bryce, I think this can perhaps be proposed and uploaded, given the
previous comments. For the actual [test] section of the sru, perhaps
point at the comments above.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1804542

Title:
  [SRU] Multiple intermittent socket failures during name resolutions

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1804542/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1804542] Re: [SRU] Multiple intermittent socket failures during name resolutions

2019-09-13 Thread Andreas Hasenack
Bryce, I think this can perhaps be proposed and uploaded, given the
previous comments. For the actual [test] section of the sru, perhaps
point at the comments above.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542

Title:
  [SRU] Multiple intermittent socket failures during name resolutions

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1804542/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843806] Re: Please build with DNSTAP

2019-09-12 Thread Andreas Hasenack
It's part of our delta. If you clone bind9, you'll see the commit disabling it:
commit 27364096b130d52beef7aaacfa5c824e3968a66d
Author: Andreas Hasenack 
Date:   Fri Jul 27 14:16:35 2018 -0300

- Don't build dnstap as it depends on universe packages:
  + d/control: drop build-depends on libfstrm-dev, libprotobuf-c-dev and
protobuf-c-compiler (universe packages)
  + d/dnsutils.install: don't install dnstap
  + d/libdns1104.symbols: don't include dnstap symbols
  + d/rules: don't build dnstap nor install dnstap.proto

You can just revert that to enable it iirc.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1843806

Title:
  Please build with DNSTAP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1843806/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1843806] Re: Please build with DNSTAP

2019-09-12 Thread Andreas Hasenack
hm, I'm sorry, I may be mixing things up. The lmdb commit is another one:
commit 4f9a9b60845feb1202020ec71bd6a9e7298e6e19
Author: Andreas Hasenack 
Date:   Wed Jun 20 17:28:42 2018 -0300

- Build without lmdb support as that package is in Universe

I don't remember now if lmdb was related to dnstap or not, I'm a bit
confused.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843806

Title:
  Please build with DNSTAP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1843806/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843806] Re: Please build with DNSTAP

2019-09-12 Thread Andreas Hasenack
It's part of our delta. If you clone bind9, you'll see the commit disabling it:
commit 27364096b130d52beef7aaacfa5c824e3968a66d
Author: Andreas Hasenack 
Date:   Fri Jul 27 14:16:35 2018 -0300

- Don't build dnstap as it depends on universe packages:
  + d/control: drop build-depends on libfstrm-dev, libprotobuf-c-dev and
protobuf-c-compiler (universe packages)
  + d/dnsutils.install: don't install dnstap
  + d/libdns1104.symbols: don't include dnstap symbols
  + d/rules: don't build dnstap nor install dnstap.proto

You can just revert that to enable it iirc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843806

Title:
  Please build with DNSTAP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1843806/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >