[Touch-packages] [Bug 1748956] Re: replace uses of net-tools with iproute2

2018-08-12 Thread Dustin Kirkland
** Changed in: byobu
   Status: New => Fix Committed

** Changed in: byobu (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: byobu
   Importance: Undecided => Medium

** Changed in: byobu (Ubuntu)
   Importance: Wishlist => Medium

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

Title:
  replace uses of net-tools with iproute2

Status in byobu:
  Fix Committed
Status in byobu package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  As ubuntu goes forward, net-tools is looking to be dropped.

  Byobu currently depends on net-tools.  That code should be replaced by
  iproute2.

  
  Related bugs:
   * bug 925145: cloud-init  Use ip instead of ifconfig and route

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: byobu 5.124-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 12 13:34:27 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (935 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: byobu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773687] Re: [bionic] no unattended installation

2018-05-27 Thread Dustin Kirkland
** Changed in: tzdata (Ubuntu)
   Importance: Undecided => High

** Changed in: tzdata (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:17:42 2018
  InstallationDate: Installed on 2017-12-31 (147 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

2017-06-29 Thread Dustin Kirkland
Regarding the "sometimes the news is just a fun fact"...

Do you get similarly annoyed when the Google logo on the homepage is
replaced with a Google Doodle?

https://www.google.com/doodles

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

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

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

2017-06-29 Thread Dustin Kirkland
Regarding the User Agent -- this is exactly equivalent to the USER AGENT
string your browser (Chrome, Chromium, Firefox, Safari, curl, wget)
sends to every website in the world.  Curious?  Install apache2 on
localhost, tail -f /var/log/apache2/access.log, and hit
http://localhost/ with a web browser.  Here, I've just done it for you:

127.0.0.1 - - [29/Jun/2017:17:55:20 -0500] "GET / HTTP/1.1" 200 777 "-"
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/59.0.3071.104 Safari/537.36"

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

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

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

2017-06-29 Thread Dustin Kirkland
This comment is mainly for Tim and Andrew (of Digital Ocean), who seem
offended by this behavior.

I just captured this snapshot in my Chrome browser, searching for
"Docker Cloud".  The top results of that search are not actually the
organic docker.com results, but rather a Google Ad for Digital Ocean
services.

Moreover, the HBO link wasn't even an advertisement!  It was an
interesting piece of news from this week, a blog post of an interesting
developer who did something fun on top of Ubuntu.  And we celebrated
that achievement.

** Attachment added: "Screenshot from 2017-06-29 17-36-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+attachment/4906069/+files/Screenshot%20from%202017-06-29%2017-36-58.png

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

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

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

2017-06-29 Thread Dustin Kirkland
** Changed in: base-files (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: base-files (Ubuntu)
   Status: Triaged => Opinion

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

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

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

2017-06-29 Thread Dustin Kirkland
Howdy!  I'm the author of the motd-news code, as well as the story in
the subject of this bug.

Note that motd.ubuntu.com has been updated to say:

" * Ubuntu 16.10 will reach end of life on Wednesday, July 20th"

It may be useful to explain a bit of the design of motd-news.  Note that
much of this was copied over from my comment on the Hacker News thread:
https://news.ycombinator.com/edit?id=14663947

By design:

- Asynchronously, about 60 seconds after boot, a systemd timer fires
which runs "/etc/update-motd.d/50-motd-news --force"

- It sources 3 admin-editable config variables in /etc/default/motd-
news.  The defaults are: ENABLED=1, URLS="https://motd.ubuntu.com;,
WAIT="5"

- The admin can disable it entirely (ENABLED=0), change or add other
MOTD news sources (your corporate IT team could run its own), and change
the wait time in seconds

- If it's enabled, that systemd timer job will loop over each of the
URLS (note, that it's important that these should be https with valid
SSL certificates), trim them to 80 characters per line, and a maximum of
10 lines, and concatenate them to a cache file in /var/cache/motd-news

- Every ~12 hours thereafter (with a little bit of random timer
fuzzing), this systemd timer job will re-run and update the /var/cache
/motd-news

- Upon login, the contents of /var/cache/motd-news is just printed to
screen.  There was a bug (fixed now, working its way through the Ubuntu
update process), in that an empty cache file was not getting, if the
fetch failed, so the fetch was retried every time (and failed every
time, with the $WAIT delay of 5 seconds).  Obviously, it was a simple
fix.

As I am generally responsible for this feature in Ubuntu (as the Ubuntu
Product Manager for the design, and the Ubuntu Core Developer for the
implementation) I'll also respond to the discussion about this feature
being included in Ubuntu at all...

- Back in 2009, Ubuntu was the first distribution to add the concept of
a "dynamic MOTD", by introducing the /etc/update-motd.d/* structure of
scripts.  I originally implemented it for Landscape (a commercial
package management system by Canonical), but it has since also been
adopted by Debian, Amazon Linux, and others.

- It's a flexible framework that enables distro packages or
administrators to add executable scripts in /etc/update-motd.d/* to
generate informative, interesting messages displayed at login.

- This was quite interesting, in that for almost 40 years of Linux/UNIX,
the "Message of the Day" was anything but that...  It was a message that
was created at one point in time, when the distro released, and that's
about it.  And we managed to change that.

- If you look in your Ubuntu's /etc/update-motd.d/, you'll see a set of
scripts.  One prints the generic "welcome" banner.  The next one prints
3 links, as to where to find help.  You'll also find one that counts and
displays the number of package updates available for the local system.
Another tells you if a reboot is required.

- All of these are locally generated, based on local information
available on the system.

- In Ubuntu 17.04, we added /etc/update-motd.d/50-motd-news.  This is
the script who's design is described above.  The motivation is
threefold:

* Sometimes, there's critical information that either we, the distro, or
perhaps even the local IT administrator of a fleet of systems needs to
communicate to users at login.  Think, "ShellShock", "Heartbleed",
"StackClash".  This seems to happen every few months, in the current
state of the world.

* Other times, we need to communicate something about the distribution.
EoL messages, new feature availability, etc.

* And sometimes, it's just a matter of presenting a fun fact.  News from
the world of Ubuntu.  Or even your own IT department.  Such was the case
with the Silicon Valley / HBO message.  It was just an interesting
tidbit of potpourri from the world of Ubuntu.  Last week's message
actually announced an Ubuntu conference in Latin America.  The week
before, we linked to an article asking for feedback on Kubuntu.  Before
that, we announced the availability of Extended Security Maintenance
updates for 12.04.  And so on.

- There is a team of engineering managers at Canonical (the ~ubuntu-motd
team in Launchpad), all of who have shared write access to the source
code repository (lp:ubuntu-motd in Launchpad).  Going forward, we're
going to review one another's proposed message merges.  In fact, that's
an open source repository.  You're welcome to propose your own messages
for merging, if you have a well formatted, informative message for
Ubuntu users.  We'll be happy to review and include them in the future.

As always, I'm impressed with the critical analysis of the Ubuntu
community.  We, the Ubuntu ecosystem, are held by the Ubuntu community
to a very high standard, and we're quite humbled by that.  Thank you for
the continued feedback and response.

Cheers,
Dustin

-- 
You received this bug notification because you are a member 

[Touch-packages] [Bug 1691901] Re: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-29 Thread Dustin Kirkland
** Description changed:

  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.
  
  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com
  
  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.
- 
  
  === SRU ===
  
  [ IMPACT ]
  
  This bug affects Ubuntu 17.04 systems which cannot reach the internet
  (more specifically, https://motd.ubuntu.com).  There is a bug in the
  implementation of /etc/update-motd.d/50-news whereby the failure of the
  curl fetch of the motd news causes a 5-second delay.  This should not be
  the case.  By design, the motd is fetched in the background, by a
  systemd timer, and refreshed every ~12 hours, also in the background.
  On login, the script should just cat the cache file.  If the cache file
  isn't found, then it will try to fetch a new motd.  In the firewalled
  system case, the background fetch failed, AND didn't create an empty
  file.  The fix as attached simply ensures that an empty file is created
  if the curl fetch fails.  This eliminates the login delay and solves the
  bug.  Every 12 hours, the curl will be retried, quietly in the
  background, so if the curl failure happened for temporary reasons, it'll
  recover, gracefully, eventually.
  
  [ TEST CASE ]
  
  You can either test this on a firewalled system.  Or, if you can hack an
  entry in your local /etc/hosts for motd.ubuntu.com for an invalid IP
  address.  Without the fix, you'll experience a 5 second delay on login.
  With the fix, you'll login immediately.
  
  Failure case:
  
  $ lxc launch ubuntu:17.04 LP1691901
  $ lxc exec LP1691901 bash
  # ssh-import-id kirkland
  # echo 192.168.0.0 motd.ubuntu.com >> /etc/hosts
  # rm -f /var/cache/motd-news
  # exit
  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m5.333s
  user0m0.016s
  sys 0m0.000s
  
- Apply the fix.  Note that it'll take one run (might be a login, a
- reboot, or the 12-hourly timer) to create the file:
+ Apply the fix.
  
- $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
- real0m5.357s
- user0m0.016s
- sys 0m0.004s
  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m0.316s
  user0m0.008s
  sys 0m0.008s
  
  [ REGRESSION ]
  
- This is a super simple, safe, 2-line fix with minimal regression
- potential:
+ This is a simple, safe fix with minimal regression potential:
  
- diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news 
base-files-9.6ubuntu13.1/update-motd.d/50-motd-news
- --- base-files-9.6ubuntu13/update-motd.d/50-motd-news 2017-02-15 
13:54:04.0 -0600
- +++ base-files-9.6ubuntu13.1/update-motd.d/50-motd-news   2017-06-29 
09:22:31.0 -0500
- @@ -111,6 +111,8 @@
-   safe_print "$NEWS"
-   # Try to update the cache
-   safe_print "$NEWS" 2>/dev/null >$CACHE || true
- + else
- + : > "$CACHE"
-   fi
+ diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news 
base-files-9.6ubuntu13.2/update-motd.d/50-motd-news
+ --- base-files-9.6ubuntu13/update-motd.d/50-motd-news   2017-02-15 
13:54:04.0 -0600
+ +++ base-files-9.6ubuntu13.2/update-motd.d/50-motd-news 2017-06-29 
10:43:05.0 -0500
+ @@ -51,9 +51,13 @@
+  # If we're not forcing an update, and we have a cached motd-news file,
+  # then just print it and exit as quickly as possible, for login performance.
+  # Note that systemd should keep this cache file up to date, asynchronously
+ -if [ "$FORCED" != "1" ]  && [ -r $CACHE ]; then
+ -   echo
+ -   safe_print $CACHE
+ +if [ "$FORCED" != "1" ]; then
+ +   if [ -r $CACHE ]; then
+ +   echo
+ +   safe_print $CACHE
+ +   else
+ +   : > $CACHE
+ +   fi
+ exit 0
+  fi
+  
+ @@ -111,7 +115,9 @@
+ safe_print "$NEWS"
+ # Try to update the cache
+ safe_print "$NEWS" 2>/dev/null >$CACHE || true
+ -   fi
+ +   else
+ +   : > "$CACHE"
+ +   fi
   done
   rm -f "$NEWS" "$NEWS.err"
- 
+  exit 0
  
  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  

[Touch-packages] [Bug 1691901] Re: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-29 Thread Dustin Kirkland
** Description changed:

  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.
  
  In line 108 [1] it does something like:
-  curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com
+  curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com
  
  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.
+ 
+ 
+ === SRU ===
+ 
+ [ IMPACT ]
+ 
+ This bug affects Ubuntu 17.04 systems which cannot reach the internet
+ (more specifically, https://motd.ubuntu.com).  There is a bug in the
+ implementation of /etc/update-motd.d/50-news whereby the failure of the
+ curl fetch of the motd news causes a 5-second delay.  This should not be
+ the case.  By design, the motd is fetched in the background, by a
+ systemd timer, and refreshed every ~12 hours, also in the background.
+ On login, the script should just cat the cache file.  If the cache file
+ isn't found, then it will try to fetch a new motd.  In the firewalled
+ system case, the background fetch failed, AND didn't create an empty
+ file.  The fix as attached simply ensures that an empty file is created
+ if the curl fetch fails.  This eliminates the login delay and solves the
+ bug.  Every 12 hours, the curl will be retried, quietly in the
+ background, so if the curl failure happened for temporary reasons, it'll
+ recover, gracefully, eventually.
+ 
+ [ TEST CASE ]
+ 
+ You can either test this on a firewalled system.  Or, if you can hack an
+ entry in your local /etc/hosts for motd.ubuntu.com for an invalid IP
+ address.  Without the fix, you'll experience a 5 second delay on login.
+ With the fix, you'll login immediately.
+ 
+ Failure case:
+ 
+ $ lxc launch ubuntu:17.04 LP1691901
+ $ lxc exec LP1691901 bash
+ # ssh-import-id kirkland
+ # echo 192.168.0.0 motd.ubuntu.com >> /etc/hosts
+ # rm -f /var/cache/motd-news
+ # exit
+ $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
+ real0m5.333s
+ user0m0.016s
+ sys 0m0.000s
+ 
+ Apply the fix.  Note that it'll take one run (might be a login, a
+ reboot, or the 12-hourly timer) to create the file:
+ 
+ $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
+ real0m5.357s
+ user0m0.016s
+ sys 0m0.004s
+ $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
+ real0m0.316s
+ user0m0.008s
+ sys 0m0.008s
+ 
+ [ REGRESSION ]
+ 
+ This is a super simple, safe, 2-line fix with minimal regression
+ potential:
+ 
+ diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news 
base-files-9.6ubuntu13.1/update-motd.d/50-motd-news
+ --- base-files-9.6ubuntu13/update-motd.d/50-motd-news 2017-02-15 
13:54:04.0 -0600
+ +++ base-files-9.6ubuntu13.1/update-motd.d/50-motd-news   2017-06-29 
09:22:31.0 -0500
+ @@ -111,6 +111,8 @@
+   safe_print "$NEWS"
+   # Try to update the cache
+   safe_print "$NEWS" 2>/dev/null >$CACHE || true
+ + else
+ + : > "$CACHE"
+   fi
+  done
+  rm -f "$NEWS" "$NEWS.err"
+ 
  
  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

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

Title:
  [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Fix Committed
Status in base-files source package in Zesty:
  Fix Committed
Status in base-files source package in Artful:
  Fix Committed

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  

[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-29 Thread Dustin Kirkland
** Changed in: base-files (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Changed in: base-files (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Summary changed:

- 50-motd-news costs 5 seconds every login on firewalled systems
+ [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

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

Title:
  [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Fix Committed
Status in base-files source package in Zesty:
  Fix Committed
Status in base-files source package in Artful:
  Fix Committed

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-27 Thread Dustin Kirkland
** Also affects: base-files (Ubuntu Artful)
   Importance: High
 Assignee: Dustin Kirkland  (kirkland)
   Status: In Progress

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

** Changed in: base-files (Ubuntu Zesty)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

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

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

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  In Progress
Status in base-files source package in Zesty:
  In Progress
Status in base-files source package in Artful:
  In Progress

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-27 Thread Dustin Kirkland
** Changed in: base-files (Ubuntu)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

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

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  In Progress
Status in base-files source package in Zesty:
  In Progress
Status in base-files source package in Artful:
  In Progress

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1694730] Re: /etc/update-motd.d/50-motd-news calls home on each ssh connection

2017-06-27 Thread Dustin Kirkland
Hi there.  By design, it does not fetch motd.ubuntu.com with every ssh
session.

Rather, there's a systemd timer that runs, asynchronously once about a
minute after boot, and then every 12 hours (plus/minus a random interval
up to an hour).  That systemd timer updates a cache file,
/var/cache/motd, in the background.

At login, it just concatenates the /var/cache/motd file.

Note that it's easy to disable, or change to a different MOTD server, by
editing /etc/default/motd-news.

** Changed in: base-files (Ubuntu)
   Status: Triaged => Opinion

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

Title:
  /etc/update-motd.d/50-motd-news calls home on each ssh connection

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  This happens since Ubuntu 17.04 (Zesty)

  Why is /etc/update-motd.d/50-motd-news hitting https://motd.ubuntu.com
  each time I create a SSH connection?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-27 Thread Dustin Kirkland
You can also edit /etc/default/motd-news and:

 a) set ENABLED=0

 b) changed the URL to a custom one that does resolve or work for you

 c) change the time to wait

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-27 Thread Dustin Kirkland
By design, the cache file, /var/cache/motd-news, should be populated in
the background by a systemd timer that runs roughly once a day.

If that file is populated, then there should be zero impact on login.

Perhaps the background cache population should create an empty file, if
it can't reach the $URL?

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-27 Thread Dustin Kirkland
** Changed in: base-files (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

2017-05-26 Thread Dustin Kirkland
This is great, Trent!

Andres, could you get someone to look at this and merge it upstream?

Thanks!
Dustin

** Changed in: avahi (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  In Progress
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  The bug, and workaround, are clearly described in this mailing list
  thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2017-05-23 Thread Dustin Kirkland
** Changed in: base-files (Ubuntu Xenial)
 Assignee: Dustin Kirkland  (kirkland) => Steve Langasek (vorlon)

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

2017-03-22 Thread Dustin Kirkland
This needs to be urgently fixed for 12.04, as this bug is blocking
upgrades of 12.04 to 14.04 succeeding.

** Also affects: makedev (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: makedev (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: makedev (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: makedev (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedev (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: makedev (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: makedev (Ubuntu Precise)
   Importance: Undecided => Critical

** Changed in: makedev (Ubuntu Trusty)
   Importance: Undecided => Critical

** Changed in: makedev (Ubuntu Vivid)
   Importance: Undecided => Critical

** Changed in: makedev (Ubuntu Precise)
   Importance: Critical => High

** Changed in: makedev (Ubuntu Trusty)
   Importance: Critical => High

** Changed in: makedev (Ubuntu Vivid)
   Importance: Critical => High

** Changed in: makedev (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: makedev (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: makedev (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: makedev (Ubuntu Precise)
   Status: New => Triaged

** Changed in: makedev (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: makedev (Ubuntu Vivid)
   Status: New => Triaged

** Changed in: makedev (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: makedev (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: makedev (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: makedev (Ubuntu Precise)
Milestone: None => precise-updates

** Changed in: makedev (Ubuntu Trusty)
Milestone: None => trusty-updates

** Changed in: makedev (Ubuntu Vivid)
Milestone: None => vivid-updates

** Changed in: makedev (Ubuntu Xenial)
Milestone: None => xenial-updates

** Changed in: makedev (Ubuntu Yakkety)
Milestone: None => yakkety-updates

** Changed in: makedev (Ubuntu Zesty)
Milestone: None => ubuntu-17.04

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Triaged
Status in makedev source package in Precise:
  Triaged
Status in makedev source package in Trusty:
  Triaged
Status in makedev source package in Xenial:
  Triaged
Status in makedev source package in Yakkety:
  Triaged
Status in makedev source package in Zesty:
  Triaged

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1664748] Re: wifi connection drops, reconnects every 10 minutes

2017-02-17 Thread Dustin Kirkland
So I tried all three of those sysctl's and the problem is still
manifesting itself (every 10 minutes, Network Mananger pops up a
disconnected/reconnected message.

Moreover, I'll not that this problem does NOT exist in 14.04 (tested
with the same hardware, same wifi+ethernet, using a 14.04.5 LiveISO,
which uses the Xenial kernel (very close to the kernel I'm running here
on 16.04).

I really believe this problem is likely in Network Manager itself.  I'm
reopening that task for now.

** Changed in: network-manager (Ubuntu)
   Status: Invalid => New

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  wifi connection drops, reconnects every 10 minutes

Status in maas package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New

Bug description:
  I recently moved my home DHCP and DNS server over to MAAS (2.1.3 from
  xenial-updates).

  Since doing so, I've noticed that my wifi connection drops and
  reconnects (with corresponding Unity pop-up notifications) exactly
  every 10 minutes.

  I suppose this is due to the fact that MAAS sets DHCP leases to 10
  minutes by default?

  Has anyone else noticed this behavior?

  Is there a suitable workaround?  Increasing the DHCP lease time?
  Using static addresses?  Something else?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2017-02-14 Thread Dustin Kirkland
As with any user agent string sent by any web browser, the intention is
such that the server can customize the response appropriately for user.

e.g. There may be a bug that affects ARM64 users, but not any other
architecture.  There might be a kernel vulnerability that is only
exploitable machines that have been running a long time, or perhaps
machines which are definitely not vulnerable to a regression, if they've
been running for longer than the regression.  In this way, the news
server can generate the most relevant message-of-the-day for a given
system.

Or, hopefully, everything is hunky dory, and then we can wish Grace
Hopper or Alan Turing a happy birthday (a la Google Doodle) in your
Ubuntu system's MOTD :-)

Moreover, it's always easy to disable or customize the urls to the local
user or administrator's liking, or firewall it off entirely.

The goal is useful, helpful, tailored information in the MOTD.  To
actually make the "message of the day", a dynamically and informative
"message of the day".

Cheers!
Dustin

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1664748] Re: wifi connection drops, reconnects every 10 minutes

2017-02-14 Thread Dustin Kirkland
** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  wifi connection drops, reconnects every 10 minutes

Status in maas package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I recently moved my home DHCP and DNS server over to MAAS (2.1.3 from
  xenial-updates).

  Since doing so, I've noticed that my wifi connection drops and
  reconnects (with corresponding Unity pop-up notifications) exactly
  every 10 minutes.

  I suppose this is due to the fact that MAAS sets DHCP leases to 10
  minutes by default?

  Has anyone else noticed this behavior?

  Is there a suitable workaround?  Increasing the DHCP lease time?
  Using static addresses?  Something else?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1661869] [NEW] maas install fails inside of a 16.04 lxd container due to avahi problems

2017-02-04 Thread Dustin Kirkland
Public bug reported:

The bug, and workaround, are clearly described in this mailing list
thread:

https://lists.linuxcontainers.org/pipermail/lxc-
users/2016-January/010791.html

I'm trying to install MAAS in a LXD container, but that's failing due to
avahi package install problems.  I'm tagging all packages here.

** Affects: maas
 Importance: Undecided
 Status: New

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

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


** Tags: maas-at-home

** Also affects: lxd (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: avahi (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: maas-at-home

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

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  New
Status in avahi package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New

Bug description:
  The bug, and workaround, are clearly described in this mailing list
  thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2017-01-21 Thread Dustin Kirkland
Okay, reworked as a systemd timer.  Tested here in a zesty LXD
container, working well.

** Patch added: "out.patch"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+attachment/4807148/+files/out.patch

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-12-17 Thread Dustin Kirkland
@xnox:

Totally agreed on https.  I just uploaded that fix to zesty, defaulting
to https://motd.ubuntu.com (which exists now, it didn't at the time),
and enforcing that all URLs should start with https://.

The .timer systemd unit + caching + periodic refresh is interesting,
indeed.  I'll look into a rewrite of update-motd to do it this way.
What minimum version of systemd would I need for it to work this way?

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1649352] Re: http direct to terminals?

2016-12-16 Thread Dustin Kirkland
** Changed in: base-files (Ubuntu)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

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

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

Title:
  http direct to terminals?

Status in base-files package in Ubuntu:
  In Progress

Bug description:
  Hi Dustin,

  Some recent changes introduced what looks to be a serious problem:

  http://launchpadlibrarian.net/296647523/base-
  files_9.6ubuntu7_9.6ubuntu8.diff.gz

  -SERVER="https://motd.ubuntu.com;
  +# White space separated list of 0 to many news services
  +SERVER="http://motd.ubuntu.com;
  [...]
  + if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" 
-o- "$s" >"$NEWS" 2>"$ERR"; then
  + echo
  + # At most, 2 lines of at most 80 characters
  + cat "$NEWS" | tail -n 2 | cut -c -80

  This allows any network man-in-the-middle attacker, DNS response
  forger, or BGP forger, to write 160 raw bytes directly to terminals.

  The previous version wasn't good (open for abuse by anyone who could
  trick one of the myriad x.509 Certificate Authorities to mis-issue a
  certificate) but this version is open for abuse by significantly more
  attackers.

  While most terminals are reasonably safe against outright
  maliciousness this has been a recurring exploitation theme for twenty
  years, and even what is "safe" for them to display could be wildly
  confusing to users unfamiliar with maliciously controlled terminals.
  (And users have wide tastes in terminals, some are fairly brittle.)

  cat(1) does not do any filtering for 'safe' display of arbitrary
  inputs. less(1) does, assuming -r is not in LESS environment variable
  or the less(1) command line. If you wish to keep the pipeline, perhaps
  tr(1)'s -d flag could be useful.

  On a related note, is there a reason why the motd.ubuntu.com server
  can't do HTTPS?

  Thanks

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-10-30 Thread Dustin Kirkland
** Description changed:

  Add a new update-motd script for printing news and/or important notices.
+ 
+ == SRU ==
+ 
+ [IMPACT]
+ We should add important security messages or other news to the MOTD.
+ 
+ [TEST CASE]
+ Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.
+ 
+ [REGRESSION POTENTIAL]
+ No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Invalid
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-10-30 Thread Dustin Kirkland
** Patch added: "1637800.patch"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+attachment/4769667/+files/1637800.patch

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Invalid
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1637800] [NEW] add a motd script for news

2016-10-30 Thread Dustin Kirkland
Public bug reported:

Add a new update-motd script for printing news and/or important notices.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: base-files (Ubuntu Xenial)
 Importance: Low
 Assignee: Dustin Kirkland  (kirkland)
 Status: In Progress

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

** Changed in: base-files (Ubuntu)
   Status: New => Invalid

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

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

** Changed in: base-files (Ubuntu Xenial)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Invalid
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1592386] Re: add links for obtaining management and support in 10-help-text

2016-06-14 Thread Dustin Kirkland
The landscape-client package should consider remove the "  Graph this
data and manage this system at: https://landscape.canonical.com/;
message, now that the landscape link is handled in base-files /etc
/update-motd.d/10-help-text

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

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

** Changed in: base-files (Ubuntu)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

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

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

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

** Changed in: base-files (Ubuntu Xenial)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

** Changed in: base-files (Ubuntu Xenial)
Milestone: None => xenial-updates

** Summary changed:

- add links for obtaining management and support in 10-help-text
+ [SRU] add links for obtaining management and support, fix documentation link 
in 10-help-text

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

** Changed in: base-files (Ubuntu)
   Status: In Progress => Fix Committed

** Description changed:

  Add links for obtaining management and support in 10-help-text, and fix
  the documentation link.  Should look very simple, concise, and clean,
  like this:
  
-  * Documentation:  https://help.ubuntu.com
-  * Management: https://landscape.canonical.com
-  * Support:https://ubuntu.com/advantage
+  * Documentation:  https://help.ubuntu.com
+  * Management: https://landscape.canonical.com
+  * Support:https://ubuntu.com/advantage
+ 
+ == SRU ==
+ 
+ [Impact]
+ 
+ This impacts command line users of Ubuntu server (and desktop) systems.
+ When logging into an Ubuntu console (tty, ssh), pam displays a
+ dynamically generated MOTD (message of the day).  The current message of
+ the day on Ubuntu servers has a broken link for documentation.  We need
+ to fix that.  We should also add simple, clean, friendly links on how to
+ obtain support and remotely manage the system.
+ 
+ [Test Case]
+ 
+ Upgrade the base-files package, and then regenerate the MOTD using 'sudo
+ update-motd'.  The new motd should be printed to screen.
+ 
+ [Regression Potential]
+ 
+ None.  This change affects one simple shell script in /etc/update-
+ motd.d/10-help-text

** Also affects: landscape-client (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: landscape-client (Ubuntu)
   Importance: Undecided => Medium

** Changed in: landscape-client (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: landscape-client (Ubuntu)
   Status: New => Triaged

** Changed in: landscape-client (Ubuntu Xenial)
   Status: New => Triaged

** No longer affects: landscape-client (Ubuntu Xenial)

** No longer affects: landscape-client (Ubuntu)

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

Title:
  [SRU] add links for obtaining management and support, fix
  documentation link in 10-help-text

Status in base-files package in Ubuntu:
  Fix Committed
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add links for obtaining management and support in 10-help-text, and
  fix the documentation link.  Should look very simple, concise, and
  clean, like this:

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

  == SRU ==

  [Impact]

  This impacts command line users of Ubuntu server (and desktop)
  systems.  When logging into an Ubuntu console (tty, ssh), pam displays
  a dynamically generated MOTD (message of the day).  The current
  message of the day on Ubuntu servers has a broken link for
  documentation.  We need to fix that.  We should also add simple,
  clean, friendly links on how to obtain support and remotely manage the
  system.

  [Test Case]

  Upgrade the base-files package, and then regenerate the MOTD using
  'sudo update-motd'.  The new motd should be printed to screen.

  [Regression Potential]

  None.  This change affects one simple shell script in /etc/update-
  motd.d/10-help-text

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 771395] Re: update-motd.d/10-help-text has an incomplete check for ubuntu server systems

2016-06-14 Thread Dustin Kirkland
*** This bug is a duplicate of bug 1592386 ***
https://bugs.launchpad.net/bugs/1592386

This bug should be closed (obsoleted) by the fix to Bug #1592386

** This bug has been marked a duplicate of bug 1592386
   add links for obtaining management and support in 10-help-text

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

Title:
  update-motd.d/10-help-text has an incomplete check for ubuntu server
  systems

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: base-files

  I'd just finished installing ubuntu-server i386 and was surprised to
  discover that after logging in I was presented with a link to
  help.ubuntu.com instead of www.ubuntu.com/server.  This is because the
  help text script is just looking for '-server' in the output of uname
  and there is no -server kernel for i386.

  From 10-help-text:

  URL="https://help.ubuntu.com/;
  if uname -r | grep -qs "\-server"; then
URL="http://www.ubuntu.com/server/doc;
  fi

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1592386] [NEW] [SRU] add links for obtaining management and support, fix documentation link in 10-help-text

2016-06-14 Thread Dustin Kirkland
Public bug reported:

Add links for obtaining management and support in 10-help-text, and fix
the documentation link.  Should look very simple, concise, and clean,
like this:

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

** Affects: base-files (Ubuntu)
 Importance: Medium
 Assignee: Dustin Kirkland  (kirkland)
 Status: Fix Committed

** Affects: base-files (Ubuntu Xenial)
 Importance: Medium
 Assignee: Dustin Kirkland  (kirkland)
 Status: Fix Committed

** Description changed:

- Add links for obtaining management and support in 10-help-text.
+ Add links for obtaining management and support in 10-help-text, and fix
+ the documentation link.  Should look very simple, concise, and clean,
+ like this:
+ 
+  * Documentation:  https://help.ubuntu.com
+  * Management: https://landscape.canonical.com
+  * Support:https://ubuntu.com/advantage

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

Title:
  [SRU] add links for obtaining management and support, fix
  documentation link in 10-help-text

Status in base-files package in Ubuntu:
  Fix Committed
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add links for obtaining management and support in 10-help-text, and
  fix the documentation link.  Should look very simple, concise, and
  clean, like this:

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

2016-04-12 Thread Dustin Kirkland
I am reopening the Trusty task, as I've re-confirmed this bug in 14.04
chroot.  apt upgrading will fail on libpam-systemd:

root@x250:/# apt dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libfreetype6 os-prober
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
E: Can not write log (Is /dev/pts mounted?) - openpty (2: No such file or 
directory)
Setting up libpam-systemd:amd64 (204-5ubuntu20.19) ...
initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
runlevel:/var/run/utmp: No such file or directory
dpkg: error processing package libpam-systemd:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
 libpam-systemd:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Note that I can work around this by disabling policy-rc.d and initctl as
such:

#!/bin/sh

# Ensure that apt upgrades work in Ubuntu on Windows
# environments, which do not use Ubuntu's /sbin/init
# Install a dummy, exit-non-zero policy-rc.d
cat >/usr/sbin/policy-rc.d < Confirmed

** Changed in: systemd (Ubuntu Trusty)
   Importance: Undecided => High

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

Title:
  failure to update libpam-systemd in 14.04 due to missing logind init
  script

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Utopic:
  Fix Released

Bug description:
  Hi,

  while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
  systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
  state. 'apt-get -f install' from within the chroot will not fix it,
  but if the build is made bootable and put into a iso/VM you can
  recover that way in a live session.

  the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm 
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind 
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't 
exist) and not /etc/init/systemd-logind.conf (does exist).
  ?

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
libpam-systemd
  1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/25.2 kB of archives.
  After this operation, 1024 B of additional disk space will be used.
  (Reading database ... 113986 files and directories currently installed.)
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg: trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Our build logs available upon request, but the scripts to setup the chroot to 
recreate it are here:

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh

  
  In a web-search I notice a few others running into the same bug,

  chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
  /%23ubuntu-devel.txt

  someone else's build log:
  https://launchpad.net/~qutim/+archive/qutim/+build/6039800

  launchpad bug #1323575 seems to be a duplicate of this one.

  
  perhaps related to older launchpad bug #1305395 ?

  note we are also suffering from a failure with update-initramfs, not sure of 
the root cause of that one but I thought I'd mention it in case they were 
related, since they both started happening about the same time, a couple weeks 
ago. (launchpad bug #1317602)
  It all worked ok after the inital releases of 14.04, so 

[Touch-packages] [Bug 1563026] Re: LXC/LXD installed by default on Ubuntu server

2016-04-05 Thread Dustin Kirkland
Indeed, LXD was added to the default Ubuntu server seed in the 15.10
cycle, so this has been the case for at least 6 months.

LXD is extremely important to the Ubuntu server.  Basically, every
Ubuntu server can now be 100x more Ubuntu (or other Linux) servers!

This is an important and key concept to Ubuntu as a scale out platform.

Note that LXD images are *not* downloaded until you use them for the
first time, so those aren't included in the base image.

Thanks!
Dustin

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Opinion

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

Title:
  LXC/LXD installed by default on Ubuntu server

Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  When performing a new installation of Ubuntu server 16.04 Beta 2, LXC
  and LXD are included in the default packages even when "Virtual
  Server" is not selected as an installation task. This brings in all of
  the required dependencies as well, obviously, which seems like it is
  not the best default behavior to have.

  When installing from a non-UEFI boot, the user may select "minimal
  install" from the "F4" menu. This menu is not available from the UEFI
  grub environment, making it apparently impossible to select an
  installation that does not include the LXC and LXD suite by default.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1563026] Re: LXC/LXD installed by default on Ubuntu server

2016-04-05 Thread Dustin Kirkland
** Changed in: ubuntu-meta (Ubuntu)
 Assignee: Canonical Server Team (canonical-server) => Dustin Kirkland  
(kirkland)

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  LXC/LXD installed by default on Ubuntu server

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When performing a new installation of Ubuntu server 16.04 Beta 2, LXC
  and LXD are included in the default packages even when "Virtual
  Server" is not selected as an installation task. This brings in all of
  the required dependencies as well, obviously, which seems like it is
  not the best default behavior to have.

  When installing from a non-UEFI boot, the user may select "minimal
  install" from the "F4" menu. This menu is not available from the UEFI
  grub environment, making it apparently impossible to select an
  installation that does not include the LXC and LXD suite by default.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 831487] Re: Dependency on package unattended-upgrades on Ubuntu Server

2016-03-08 Thread Dustin Kirkland
@racb, who's going to fix the GUI?

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

Title:
  Dependency on package unattended-upgrades on Ubuntu Server

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Xenial:
  Triaged

Bug description:
  The package, which includes the always-useful add-apt-repository,
  depends on package unattended-upgrades. This is not good on servers,
  as you may want to add PPAs with the convenience of add-apt-repository
  but still want to control everything that gets upgraded on the
  machine.

  Tested on both Ubuntu 10.04 LTS and 11.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/831487/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 831487] Re: Dependency on package unattended-upgrades on Ubuntu Server

2016-03-08 Thread Dustin Kirkland
Patch attached.

** Patch added: "831487.patch"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/831487/+attachment/4592638/+files/831487.patch

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

Title:
  Dependency on package unattended-upgrades on Ubuntu Server

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Xenial:
  Triaged

Bug description:
  The package, which includes the always-useful add-apt-repository,
  depends on package unattended-upgrades. This is not good on servers,
  as you may want to add PPAs with the convenience of add-apt-repository
  but still want to control everything that gets upgraded on the
  machine.

  Tested on both Ubuntu 10.04 LTS and 11.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/831487/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 831487] Re: Dependency on package unattended-upgrades on Ubuntu Server

2016-03-08 Thread Dustin Kirkland
I agree, would be nice if unattended-upgrades could be removed, without
affecting anything else.

** Also affects: software-properties (Ubuntu Xenial)
   Importance: High
   Status: Triaged

** Changed in: software-properties (Ubuntu Xenial)
 Assignee: (unassigned) => Michael Vogt (mvo)

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

Title:
  Dependency on package unattended-upgrades on Ubuntu Server

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Xenial:
  Triaged

Bug description:
  The package, which includes the always-useful add-apt-repository,
  depends on package unattended-upgrades. This is not good on servers,
  as you may want to add PPAs with the convenience of add-apt-repository
  but still want to control everything that gets upgraded on the
  machine.

  Tested on both Ubuntu 10.04 LTS and 11.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/831487/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1537528] Re: byobu-config segfault with screen backend

2016-02-28 Thread Dustin Kirkland
** Also affects: newt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  byobu-config segfault with screen backend

Status in byobu package in Ubuntu:
  In Progress
Status in newt package in Ubuntu:
  New
Status in byobu package in Debian:
  New

Bug description:
  When running byobu with the screen backend byobu-config segfaults when
  trying to open it by pressing F9.

  Steps to reproduce.

  1. Configure byobu to use screen for the backend
  2. Press F9 to open the configuration menu
  3. The console flashes then returns to your shell window.

  Running byobu-config manually within a byobu screen session shows it's
  segfaulting. It does not crash running it outside of screen.

  byobu:
Installed: 5.101-0ubuntu1~wily
Candidate: 5.101-0ubuntu1~wily
Version table:
   *** 5.101-0ubuntu1~wily 0
  500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.97-0ubuntu1 0
  500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1547893] [NEW] Sync unattended-upgrades 0.90 (main) from Debian unstable (main)

2016-02-22 Thread Dustin Kirkland
Public bug reported:

Please sync unattended-upgrades 0.90 (main) from Debian unstable (main)

Changelog entries since current xenial version 0.89.1:

unattended-upgrades (0.90) unstable; urgency=medium

  [ Alexandre Detiste ]
  * tweak a bit the French translations

  [ Michael Vogt ]
  * debian/templates: set unattended-upgrades/enable_auto_updates to
"true" (Closes: #707055)
  * debian/config: set debconf questions about origin/enable to low

 -- Michael Vogt   Thu, 18 Feb 2016 14:05:58 -0800

** Affects: unattended-upgrades (Ubuntu)
 Importance: High
 Status: Confirmed

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Wishlist => High

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

Title:
  Sync unattended-upgrades 0.90 (main) from Debian unstable (main)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Please sync unattended-upgrades 0.90 (main) from Debian unstable
  (main)

  Changelog entries since current xenial version 0.89.1:

  unattended-upgrades (0.90) unstable; urgency=medium

[ Alexandre Detiste ]
* tweak a bit the French translations

[ Michael Vogt ]
* debian/templates: set unattended-upgrades/enable_auto_updates to
  "true" (Closes: #707055)
* debian/config: set debconf questions about origin/enable to low

   -- Michael Vogt   Thu, 18 Feb 2016 14:05:58 -0800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1547893/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-23 Thread Dustin Kirkland
** Changed in: lxc (Ubuntu)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  [Problem]
  The released wily image preinstalls lxc, which breaks the assumption that 
lxc's preinst packaging script makes:

  It inspects the network to try to pick a 10.0.N.0 network that isn't
  being used, with N starting at 3, so this appears to have picked
  10.0.3.0 when it was installed on whatever system was generating the
  image.

  When a container is started, it will dhcp on eth0 and get 10.0.3.X as
  expected.  The problem comes when the lxc-net service that is already
  installed in that container starts and configures *its* lxcbr0 with
  10.0.3.X.  The networking inside the container is broken at that
  point.

  This affects LXC containers, and should affect LXD containers but
  doesn't currently, as the metadata used for lxd images is still
  pointing to a beta2 release (bug 1509390).

  The easiest way to reproduce this is to use the ubuntu-cloud lxc
  template on a wily host.

  [Test Case]

  1.) Verify expectation for each image
     - -disk1.img cloud image, check for file
     - -root.tar.xz image (used by lxd) and check for file
     - -root.tar.gz image (used by lxc)

     For each of those images, verify:
     a.) A cloud image should not have /etc/default/lxc-net
     b.) lxd should be installed (dpkg-query --show | grep lxd)

  2.) Start instance from updated image and start instance in lxc inside
     launch instance on openstack or kvm or other
     verify lxcbr0 bridge exists
     lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily
     # wait until lxc-ls --fancy shows 'running'
     lxc-attach -n bugcheck wget http://ubuntu.com

  3.) Start instance from updated image and start instance in lxd inside
     launch instance on openstack or kvm or other
     verify lxcbr0 bridge exists
     lxd import-images ubuntu wily
     lxc launch ubuntu
     # wait some amount
     lxc attach bugcheck wget http://ubuntu.com

  [Regression Potentional]
  The highest chance for fallout is a change in the /16 network that is chosen 
conflicting with some existing service.

  [Other Info]
  Default apt install of lxc has always picked some 10.0.X.0/16 network to use 
for its lxcbr0 bridge.  That network (often 10.0.3.0/16) would then be 
unreachable from the host.  The same behavior occurs with libvirt-bin and many 
other such services.

  We are moving that logic to happen the first time that 'lxc-net'
  service starts.

  This means first boot for a cloud instance rather than cloud-image
  build time.

  [Work around]
  To patch / fix an existing cloud image to make lxc and lxd guests start 
simply change the config of /etc/default/lxc-net to have something other than 
10.0.3.0.

  sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' 
/etc/default/lxc-net &&
  sudo service lxc-net stop &&
  sudo service lxc-net start

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1503418] [NEW] [REGRESSION] launching byobu from unity uses the terminal icon rather than the application icon

2015-10-06 Thread Dustin Kirkland
Public bug reported:

I just upgraded to Wily yesterday, and it seems this regression has
crept up again (it happened around the Utopic timeframe too).

Install Byobu.

sudo apt-get install byobu

Open from the Unity Launcher.  Press Windows icon.  Type 'byobu'.  Click
on the Ubuntu terminal icon.  Byobu open in the default terminal (as
specified in the byobu.desktop file), but the icon on the left in the
unity bar is the Terminal icon, not the Byobu one.

** Affects: byobu (Ubuntu)
 Importance: Medium
 Assignee: Dustin Kirkland  (kirkland)
 Status: Invalid

** Affects: unity (Ubuntu)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New

** Also affects: byobu (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: byobu (Ubuntu)
   Status: New => Invalid

** Changed in: byobu (Ubuntu)
   Importance: Undecided => Medium

** Changed in: byobu (Ubuntu)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

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

Title:
  [REGRESSION] launching byobu from unity uses the terminal icon rather
  than the application icon

Status in byobu package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  New

Bug description:
  I just upgraded to Wily yesterday, and it seems this regression has
  crept up again (it happened around the Utopic timeframe too).

  Install Byobu.

  sudo apt-get install byobu

  Open from the Unity Launcher.  Press Windows icon.  Type 'byobu'.
  Click on the Ubuntu terminal icon.  Byobu open in the default terminal
  (as specified in the byobu.desktop file), but the icon on the left in
  the unity bar is the Terminal icon, not the Byobu one.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1438510] [NEW] [REGRESSION] bluetooth headset no longer supports a2dp

2015-03-30 Thread Dustin Kirkland
Public bug reported:

Just installed 15.04 fresh from the latest ISO (beta2).

I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to
have regressed in functionality.

In 14.10, I was able to set the output profile either to a2dp or hsp/hfp
(telephony duplex).

In 15.04, it only works in telephony duplex mode.  I can't get high
fidelity sound playback to work at all.

This thread seems to be related, though the workaround within did not solve the 
problem for me:
https://bbs.archlinux.org/viewtopic.php?id=194006

** Affects: bluez (Ubuntu)
 Importance: High
 Status: New

** Affects: pulseaudio (Ubuntu)
 Importance: High
 Status: New

** Affects: bluez (Ubuntu Vivid)
 Importance: High
 Status: New

** Affects: pulseaudio (Ubuntu Vivid)
 Importance: High
 Status: New


** Tags: regression-proposed

** Changed in: bluez (Ubuntu)
   Importance: Undecided = High

** Also affects: bluez (Ubuntu Vivid)
   Importance: High
   Status: New

** Changed in: bluez (Ubuntu Vivid)
Milestone: None = ubuntu-15.04

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Vivid)
   Importance: Undecided = High

** Changed in: pulseaudio (Ubuntu Vivid)
Milestone: None = ubuntu-15.04

** Tags added: regression-proposed

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in bluez source package in Vivid:
  New
Status in pulseaudio source package in Vivid:
  New

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp