[Touch-packages] [Bug 2008088] [NEW] Update motd/00-header to use os-release

2023-02-22 Thread Corentin Noël
Public bug reported:

The now recommended way to specify an OS version is in /usr/lib/os-release that 
is shipped with Ubuntu since a while now.
The lsb-release utility has now long switched to using os-release files 
https://salsa.debian.org/debian/lsb/-/commit/b05d8b6b70e5af820ddb4e651868488ed9257c17

It would be better for the motd header to look like this:

```
[ -r /usr/lib/os-release ] && . /usr/lib/os-release

if [ -z "$PRETTY_NAME" ] && [ -x /usr/bin/lsb_release ]; then
 # Fall back to using the very slow lsb_release utility
 PRETTY_NAME=$(lsb_release -s -d)
fi

printf "Welcome to %s (%s %s %s)\n" "$PRETTY_NAME" "$(uname -o)" "$(uname -r)" 
"$(uname -m)"
```

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

** Description changed:

  The now recommended way to specify an OS version is in /usr/lib/os-release 
that is shipped with Ubuntu since a while now.
  The lsb-release utility has now long switched to using os-release files 
https://salsa.debian.org/debian/lsb/-/commit/b05d8b6b70e5af820ddb4e651868488ed9257c17
  
  It would be better for the motd header to look like this:
  
  ```
- [ -r /usr/bin/os-release ] && . /usr/bin/os-release
+ [ -r /usr/lib/os-release ] && . /usr/lib/os-release
  
  if [ -z "$PRETTY_NAME" ] && [ -x /usr/bin/lsb_release ]; then
-   # Fall back to using the very slow lsb_release utility
-   PRETTY_NAME=$(lsb_release -s -d)
+  # Fall back to using the very slow lsb_release utility
+  PRETTY_NAME=$(lsb_release -s -d)
  fi
  
  printf "Welcome to %s (%s %s %s)\n" "$PRETTY_NAME" "$(uname -o)" "$(uname 
-r)" "$(uname -m)"
  ```

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

Title:
  Update motd/00-header to use os-release

Status in base-files package in Ubuntu:
  New

Bug description:
  The now recommended way to specify an OS version is in /usr/lib/os-release 
that is shipped with Ubuntu since a while now.
  The lsb-release utility has now long switched to using os-release files 
https://salsa.debian.org/debian/lsb/-/commit/b05d8b6b70e5af820ddb4e651868488ed9257c17

  It would be better for the motd header to look like this:

  ```
  [ -r /usr/lib/os-release ] && . /usr/lib/os-release

  if [ -z "$PRETTY_NAME" ] && [ -x /usr/bin/lsb_release ]; then
   # Fall back to using the very slow lsb_release utility
   PRETTY_NAME=$(lsb_release -s -d)
  fi

  printf "Welcome to %s (%s %s %s)\n" "$PRETTY_NAME" "$(uname -o)" "$(uname 
-r)" "$(uname -m)"
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2008088/+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 1952107] Re: Google Contacts API Deprecated

2022-04-21 Thread Corentin Noël
Fit it to work on Focal, one has to also backport this commit in EDS
https://gitlab.gnome.org/GNOME/evolution-data-
server/-/commit/adbd6fc07033b639a990467009bce416b87ef855

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : 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 found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1875558] Re: [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

2020-06-05 Thread Corentin Noël
@seb128 Tested it since it is available in focal-proposed and it solved
the issue for me. I haven't noticed any issue so far.

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

Title:
  [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

Status in libproxy package in Ubuntu:
  Fix Released
Status in libproxy source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * The proxy configuration from GSettings is not getting exported and
  thus is not used by libproxy-enabled applications.

   * Many GLib applications are now throwing critical messages in the
  logs when running. This is escpecially true for WebKitGtk applications
  which are throwing one message by subprocess.

  [Test Case]

   * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
  terminal and see the critical messages

  GLib-GObject-WARNING **: 09:00:09.217:
  ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for
  instance '0x55b923a6b430' of type 'GSettings'

  [Regression Potential]

   * No regression is to expect from this patch

  [Other Info]
   
   * The patch is already in debian experimental and is available since 
0.4.15-12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1875558/+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 1875558] Re: libproxy1-plugin-gsettings triggers a lot of warnings

2020-05-19 Thread Corentin Noël
** Description changed:

- I am getting a lot of:
- GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617: 
signal 'changed::' is invalid for instance '0x55b923a6b430' of type 'GSettings'
+ [Impact]
  
- This is especially visible with Webkit2Gtk applications such as GNOME
- Web.
+  * The proxy configuration from GSettings is not getting exported and
+ thus is not used by libproxy-enabled applications.
  
- A fix has landed upstream and I've prepared a patch here
- https://salsa.debian.org/gnome-team/libproxy/-/merge_requests/2
+  * Many GLib applications are now throwing critical messages in the logs
+ when running. This is escpecially true for WebKitGtk applications which
+ are throwing one message by subprocess.
+ 
+ [Test Case]
+ 
+  * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
+ terminal and see the critical messages
+ 
+ GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617:
+ signal 'changed::' is invalid for instance '0x55b923a6b430' of type
+ 'GSettings'
+ 
+ [Regression Potential]
+ 
+  * No regression is to expect from this patch
+ 
+ [Other Info]
+  
+  * The patch is already in debian experimental and is available since 
0.4.15-12

** Summary changed:

- libproxy1-plugin-gsettings triggers a lot of warnings
+ [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

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

Title:
  [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

Status in libproxy package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * The proxy configuration from GSettings is not getting exported and
  thus is not used by libproxy-enabled applications.

   * Many GLib applications are now throwing critical messages in the
  logs when running. This is escpecially true for WebKitGtk applications
  which are throwing one message by subprocess.

  [Test Case]

   * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
  terminal and see the critical messages

  GLib-GObject-WARNING **: 09:00:09.217:
  ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for
  instance '0x55b923a6b430' of type 'GSettings'

  [Regression Potential]

   * No regression is to expect from this patch

  [Other Info]
   
   * The patch is already in debian experimental and is available since 
0.4.15-12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1875558/+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 1875558] [NEW] libproxy1-plugin-gsettings triggers a lot of warnings

2020-04-28 Thread Corentin Noël
Public bug reported:

I am getting a lot of:
GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617: signal 
'changed::' is invalid for instance '0x55b923a6b430' of type 'GSettings'

This is especially visible with Webkit2Gtk applications such as GNOME
Web.

A fix has landed upstream and I've prepared a patch here
https://salsa.debian.org/gnome-team/libproxy/-/merge_requests/2

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

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

Title:
  libproxy1-plugin-gsettings triggers a lot of warnings

Status in libproxy package in Ubuntu:
  New

Bug description:
  I am getting a lot of:
  GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617: 
signal 'changed::' is invalid for instance '0x55b923a6b430' of type 'GSettings'

  This is especially visible with Webkit2Gtk applications such as GNOME
  Web.

  A fix has landed upstream and I've prepared a patch here
  https://salsa.debian.org/gnome-team/libproxy/-/merge_requests/2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1875558/+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 1762384] [NEW] libgpgme-dev installs libgpgme-pthread.so in /usr/lib/${DEB_HOST_MULTIARCH}, literally

2018-04-09 Thread Corentin Noël
Public bug reported:

In Bionic, libgpgme-pthread.so it is installed in
/usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu (the
variable is not replaced)

** Affects: gpgme1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  libgpgme-dev installs libgpgme-pthread.so in
  /usr/lib/${DEB_HOST_MULTIARCH}, literally

Status in gpgme1.0 package in Ubuntu:
  New

Bug description:
  In Bionic, libgpgme-pthread.so it is installed in
  /usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu
  (the variable is not replaced)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1762384/+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 1701688] [NEW] Remove patch that disables Cork plugin

2017-06-30 Thread Corentin Noël
Public bug reported:

According to the patch comment, the cork module is disabled to serve the
phone. It should now be enabled by removing the patch, 0005-dont-load-
cork-music-on-phone.patch.

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

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

Title:
  Remove patch that disables Cork plugin

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  According to the patch comment, the cork module is disabled to serve
  the phone. It should now be enabled by removing the patch, 0005-dont-
  load-cork-music-on-phone.patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1701688/+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 1650972] [NEW] No .vapi in Zesty

2016-12-18 Thread Corentin Noël
Public bug reported:

The .vapi file is missing from the packaging in the Zesty version.
This triggers some build to fail in elementary for example.

** 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/1650972

Title:
  No .vapi in Zesty

Status in network-manager package in Ubuntu:
  New

Bug description:
  The .vapi file is missing from the packaging in the Zesty version.
  This triggers some build to fail in elementary for example.

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