[Touch-packages] [Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

2022-10-28 Thread Guy Rouillier
Lukas Märdian (slyon): "NetworkManager should automatically detect sd-
resolved and integrate nicely"

Thank you for this guidance, Lukas.  I had disabled NetworkManager on
this system because it wasn't configuring my network connections as I
needed them.  I had moved my home LAN onto a separate subnet -
192.168.2.* - as my provider is Verizon FIOS, and it controls
192.168.1.*.  Even though I put specific manual settings into
NetworkManager to tell it to use 192.168.2.*, it was still picking DNS
servers on 192.168.1.*.

But your post encouraged me to try again (2 years later) and this time I
got NetworkManager working with Manual configuration.  So, I now have
everything configured as default with stub-resolv.conf and
NetworkManager enabled, and it's all working correctly.  The only place
I have DNS servers specified is in NetworkManager, separately for each
interface ("Wired connection 1" and "docker0").  I'm providing these
details in case someone finds this report via search.

-- 
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/1774632

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When using nslookup for local machine names, the local DNS was being
  ignored (not queried) and none of the local machines could be found.

  After much research and digging, it was discovered that the cause was
  the incorrect symbolic link /etc/resolv.conf file.

  The default install caused systemd-resolve to configure the link to point to 
the stub file:
  /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  Reomving that link and pointing it to the correct file solved the DNS lookup 
issue. The correct link looks like this:
  /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

  
  Steps used to test the bug before fixing the link is to perform an nslookup 
on a local (non FQDN) machine that is in your local DNS (my router is my DNS 
server for this case) Here is an example of the incorrect output:

  $ nslookup web1

  Server: 127.0.0.53
  Address:127.0.0.53#53

  ** server can't find web1: SERVFAIL

  
  Switching the symbolic link solves the problem. Here is my solution:

  $ sudo rm -f /etc/resolv.conf
  $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  
  After switching the symbolic link, the nslookup functions properly.

  $ nslookup web1

  Server: 192.168.1.1
  Address:192.168.1.1#53

  Name:   web1
  Address: 192.168.1.107

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 05:28:41 2018
  InstallationDate: Installed on 2018-01-20 (131 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5755
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0VY15F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5755
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+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 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

2022-10-25 Thread Guy Rouillier
I just encountered this issue upgrading Ubuntu MATE from 22.04 to 22.10.
After the update, I had no network connectivity, and /etc/resolv.conf
was symlinked to /run/systemd/resolve/stub-resolv.conf.  I changed that
to /run/systemd/resolve/resolve.conf, and my system is able to make
connections once again.  My system is running NetworkManager, and the
only active connection is Docker0.

/run/systemd/resolve/stub-resolv.conf:

nameserver 127.0.0.53
options edns0 trust-ad
search DOMAINS

/run/systemd/resolve/resolv.conf

nameserver 192.168.2.1
nameserver 1.1.1.1
nameserver 1.0.0.1
search DOMAINS

-- 
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/1774632

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When using nslookup for local machine names, the local DNS was being
  ignored (not queried) and none of the local machines could be found.

  After much research and digging, it was discovered that the cause was
  the incorrect symbolic link /etc/resolv.conf file.

  The default install caused systemd-resolve to configure the link to point to 
the stub file:
  /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  Reomving that link and pointing it to the correct file solved the DNS lookup 
issue. The correct link looks like this:
  /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

  
  Steps used to test the bug before fixing the link is to perform an nslookup 
on a local (non FQDN) machine that is in your local DNS (my router is my DNS 
server for this case) Here is an example of the incorrect output:

  $ nslookup web1

  Server: 127.0.0.53
  Address:127.0.0.53#53

  ** server can't find web1: SERVFAIL

  
  Switching the symbolic link solves the problem. Here is my solution:

  $ sudo rm -f /etc/resolv.conf
  $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  
  After switching the symbolic link, the nslookup functions properly.

  $ nslookup web1

  Server: 192.168.1.1
  Address:192.168.1.1#53

  Name:   web1
  Address: 192.168.1.107

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 05:28:41 2018
  InstallationDate: Installed on 2018-01-20 (131 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5755
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0VY15F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5755
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

2022-01-29 Thread Guy Rouillier
Norbert, thank you for the quick response. I'm very impressed with
apport automatically updating this bug report with requested info!

I will try the FlatPak version when I have some time, since the next LTS
release isn't until April 2022.

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

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959473] ProcEnviron.txt

2022-01-29 Thread Guy Rouillier
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1959473/+attachment/5558143/+files/ProcEnviron.txt

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

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959473] ProcCpuinfoMinimal.txt

2022-01-29 Thread Guy Rouillier
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1959473/+attachment/5558142/+files/ProcCpuinfoMinimal.txt

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

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.

2022-01-29 Thread Guy Rouillier
apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I use
  Evolution for email and calendar.  Tonight I got this message:
  
  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”
  
  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==
  
  I went to report this on the GNOME bug tracker and found this existing
  issue:
  
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655
  
  That issue was closed with this comment:
  ==
  "Andre Klapper
  
  Issue found on latest Evolution in Debian 11 (3.38.3-1)
  
  That version is ancient and not maintained anymore by GNOME developers.
  Feel free to file a bug report in your distribution's issue tracker."
  
  The version in MATE is even older: 3.36.5-0ubuntu1
  
- So apparently Evolution in MATE is currently not functional.  We need to
- update to a later release.  I will update to the newer LTS of MATE when
- it is released.
+ So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2018-10-05 (1212 days ago)
+ InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ Package: evolution-data-server
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
+ Tags: third-party-packages focal
+ Uname: Linux 5.4.0-92-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1959473/+attachment/5558141/+files/Dependencies.txt

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

Title:
  Evolution: Migrate to People API to retain programmatic access to
  Google Contacts.

Status in Evolution:
  Unknown
Status in Ubuntu MATE:
  New
Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 20.04; I stick with LTS for this system.  I
  use Evolution for email and calendar.  Tonight I got this message:

  =
  Failed to connect address book “guy.rouill...@gmail.com : Contacts”

  Invalid request URI or header, or unsupported nonstandard parameter: Contacts 
API is being deprecated. Migrate to People API to retain programmatic access to 
Google Contacts. See 
https://developers.google.com/people/contacts-api-migration.
  ==

  I went to report this on the GNOME bug tracker and found this existing
  issue:

  https://gitlab.gnome.org/GNOME/evolution/-/issues/1655

  That issue was closed with this comment:
  ==
  "Andre Klapper

  Issue found on latest Evolution in Debian 11 (3.38.3-1)

  That version is ancient and not maintained anymore by GNOME
  developers. Feel free to file a bug report in your distribution's
  issue tracker."

  The version in MATE is even older: 3.36.5-0ubuntu1

  So apparently Evolution in MATE is currently not functional.  We need to 
update to a later release.  I will update to the newer LTS of MATE when it is 
released.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-10-05 (1212 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: evolution-data-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1959473/+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 1483975] Re: update-initramfs complains about missing /sbin/fsck.btrfs

2020-12-22 Thread Guy Rouillier
I'm still seeing this message in Ubuntu Mate 20.04 on December 22,2020:

"W: /sbin/fsck.btrfs doesn't exist, can't install to initramfs"

Has the released fix just not been incorporated into the distros after
18 months?

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

Title:
  update-initramfs complains about missing /sbin/fsck.btrfs

Status in btrfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in btrfs-tools package in Debian:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  /sbin/fsck.btrfs moved to /bin/fsck.btrfs with btrfs-tools 4.0-2
  (http://bugs.debian.org/784234), which causes

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
  Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.

  I assume this means that fsck won’t run on a btrfs /, which seems bad.

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