[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

2023-11-17 Thread Luca Boccassi
** Changed in: libsolv (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  Fix Released
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  Fix Released
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  Invalid
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not affected, just documentation
  eccodes - skip, just orig-data.tar.xz
  eckit   - skip, just ...orig-dat

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

2023-11-15 Thread Luca Boccassi
SUSE and Fedora have started to compress repodata with zstd, so it is now 
impossible to bootstrap those distributions from Ubuntu via dnf/zypper due to 
the lack of zstd support in libsolve. This affects my CI jobs running in Jammy.
The fix is trivial as the version already supports it, but it needs to 
build-depend on libzstd and enable the build config flag for it. I will prepare 
SRUs for mantic/lunar/jammy. It will be fixed in noble with the next sync from 
Debian unstable, at version 0.7.26-2.

** Changed in: libsolv (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  Fix Released
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  Confirmed
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  Invalid
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates p

[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2022-03-11 Thread Luca Boccassi
Fixed also in systemd v250.4 and v249.11

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  New
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  New
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: r

[Desktop-packages] [Bug 1961610] Re: i386: seed inclusion for libfakechroot

2022-02-23 Thread Luca Boccassi
Bug against fakechroot:
https://bugs.launchpad.net/ubuntu/+source/fakechroot/+bug/1875298

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

Title:
  i386: seed inclusion for libfakechroot

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As per instructions on https://wiki.ubuntu.com/i386

  fakechroot (arch: all) requires libfakechroot, but this is not built
  for i386: https://packages.ubuntu.com/jammy/libfakechroot

  init-system-helpers, which builds a package allow-listed for i386
  builds, now build-depends on fakechroot for build-time unit tests, but
  given libfakechroot is not available for i386, the i386 build cannot
  start and thus migration from proposed is held back:

  https://launchpad.net/ubuntu/+source/init-system-helpers
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  init-system-helpers (1.61 to 1.62)
  Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
  Issues preventing migration:
  missing build on i386: init (from 1.61)

  Please enable the libfakechroot i386 build. Thank you!

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


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


[Desktop-packages] [Bug 1961610] Re: i386: seed inclusion for libfakechroot

2022-02-23 Thread Luca Boccassi
Note that the only dependency is libjemalloc, whicih already has an i386
build, so there would be no other new i386 builds apart from
libfakechroot itself.

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

Title:
  i386: seed inclusion for libfakechroot

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As per instructions on https://wiki.ubuntu.com/i386

  fakechroot (arch: all) requires libfakechroot, but this is not built
  for i386: https://packages.ubuntu.com/jammy/libfakechroot

  init-system-helpers, which builds a package allow-listed for i386
  builds, now build-depends on fakechroot for build-time unit tests, but
  given libfakechroot is not available for i386, the i386 build cannot
  start and thus migration from proposed is held back:

  https://launchpad.net/ubuntu/+source/init-system-helpers
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  init-system-helpers (1.61 to 1.62)
  Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
  Issues preventing migration:
  missing build on i386: init (from 1.61)

  Please enable the libfakechroot i386 build. Thank you!

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


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


[Desktop-packages] [Bug 1961610] [NEW] i386: seed inclusion for libfakechroot

2022-02-21 Thread Luca Boccassi
Public bug reported:

As per instructions on https://wiki.ubuntu.com/i386

fakechroot (arch: all) requires libfakechroot, but this is not built for
i386: https://packages.ubuntu.com/jammy/libfakechroot

init-system-helpers, which builds a package allow-listed for i386
builds, now build-depends on fakechroot for build-time unit tests, but
given libfakechroot is not available for i386, the i386 build cannot
start and thus migration from proposed is held back:

https://launchpad.net/ubuntu/+source/init-system-helpers
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

init-system-helpers (1.61 to 1.62)
Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
missing build on i386: init (from 1.61)

Please enable the libfakechroot i386 build. Thank you!

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  i386: seed inclusion for libfakechroot

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As per instructions on https://wiki.ubuntu.com/i386

  fakechroot (arch: all) requires libfakechroot, but this is not built
  for i386: https://packages.ubuntu.com/jammy/libfakechroot

  init-system-helpers, which builds a package allow-listed for i386
  builds, now build-depends on fakechroot for build-time unit tests, but
  given libfakechroot is not available for i386, the i386 build cannot
  start and thus migration from proposed is held back:

  https://launchpad.net/ubuntu/+source/init-system-helpers
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  init-system-helpers (1.61 to 1.62)
  Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
  Issues preventing migration:
  missing build on i386: init (from 1.61)

  Please enable the libfakechroot i386 build. Thank you!

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


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


[Desktop-packages] [Bug 1602900] Re: libzmq3 crashes when 'getifaddrs()' is unavailable

2018-03-28 Thread Luca Boccassi
This is fixed since upstream version 4.2.0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1602900

Title:
  libzmq3 crashes when 'getifaddrs()' is unavailable

Status in IPython:
  New
Status in zeromq3 package in Ubuntu:
  Confirmed

Bug description:
  libzmq3 crashes when used on a computer where the kernel is unable to
  provide any information about network-device addresses.

  This is uncommon with normal Ubuntu configurations.  But is currently
  always the case with Ubuntu as run under the new Windows Subsystem for
  Linux.

  This has already been diagnosed and fixed upstream:
  https://github.com/jupyter/notebook/issues/1331

  I have backported the fix; an updated package (based on the stock Ubuntu 
14.04 package but with the backport as an added patch) is available in this PPA:
  https://launchpad.net/~aseering/+archive/ubuntu/wsl

  This has been reported in a couple other bugtrackers.  Even with the fix in a 
PPA, there's still some amount of user confusion:
  https://github.com/jupyter/notebook/issues/1331
  https://github.com/Microsoft/BashOnWindows/issues/185

  It would be great if this fix could be pulled into Ubuntu 14.04
  directly, so that people stop hitting this bug.

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

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


[Desktop-packages] [Bug 1623792] Re: possible sigbus

2017-12-28 Thread Luca Boccassi
The fix was released in version 4.2.0 last year and is available in
Ubuntu since Zesty.

** Changed in: zeromq3 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1623792

Title:
  possible sigbus

Status in zeromq3 package in Ubuntu:
  Fix Released

Bug description:
  The following function looks like it will access a 32-bit data element
  that is improperly aligned:

  void zmq::socket_base_t::monitor_event (int event_, int value_, const 
std::string &addr_)
  {
  if (monitor_socket) {
  //  Send event in first frame
  zmq_msg_t msg;
  zmq_msg_init_size (&msg, 6);
  uint8_t *data = (uint8_t *) zmq_msg_data (&msg);
  *(uint16_t *) (data + 0) = (uint16_t) event_;
  *(uint32_t *) (data + 2) = (uint32_t) value_;
  zmq_sendmsg (monitor_socket, &msg, ZMQ_SNDMORE);
  
  //  Send address in second frame
  zmq_msg_init_size (&msg, addr_.size());
  memcpy (zmq_msg_data (&msg), addr_.c_str (), addr_.size ());
  zmq_sendmsg (monitor_socket, &msg, 0);
  }   
  }  

  On many platforms this will cause a SIGBUS.

  It looks like upstream has already fixed this issue:

  https://github.com/zeromq/libzmq/blob/master/src/socket_base.cpp#L1683

  The current code looks like:

  void zmq::socket_base_t::monitor_event (int event_, intptr_t value_, const 
std::string &addr_)
  {
  if (monitor_socket) {
  //  Send event in first frame
  zmq_msg_t msg;
  zmq_msg_init_size (&msg, 6);
  uint8_t *data = (uint8_t *) zmq_msg_data (&msg);
  //  Avoid dereferencing uint32_t on unaligned address
  uint16_t event = (uint16_t) event_;
  uint32_t value = (uint32_t) value_;
  memcpy (data + 0, &event, sizeof(event));
  memcpy (data + 2, &value, sizeof(value));
  zmq_sendmsg (monitor_socket, &msg, ZMQ_SNDMORE);

  //  Send address in second frame
  zmq_msg_init_size (&msg, addr_.size());
  memcpy (zmq_msg_data (&msg), addr_.c_str (), addr_.size ());
  zmq_sendmsg (monitor_socket, &msg, 0);
  }
  }

  Thanks

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

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


[Desktop-packages] [Bug 1718253] Re: dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial

2017-12-28 Thread Luca Boccassi
libzmq5-dev is a virtual package. libzmq5 is the correct dependency, and
it is in Xenial: https://packages.ubuntu.com/xenial/libzmq5

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1718253

Title:
  dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial

Status in zeromq3 package in Ubuntu:
  Invalid

Bug description:
  Trying to install libzmq5-dev instead selects libzmq3-dev. libzmq3-dev
  then has an incorrect dependency on libzmq5 instead of libzmq3, the
  latter of which is not available in the repos for Xenial.

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

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


[Desktop-packages] [Bug 1612240] Re: [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

2016-11-04 Thread Luca Boccassi
Hello,

Just found this discussion. We just released 4.2.0, sorry it took a while, 
difficult times.
I hope the delay didn't cause you guys too much trouble.

The patch to use dynamic ports in the test looks very interesting, it's
something I wanted to fix for a while but never had to the time, so if
you want to push it up to Github we'd have a look, although it has to
work on Windows too (I see there's some pthread use). Also at least one
should use the hard-coded port, to test that code path, but it can be a
separate individual unit test.

Thanks for your work!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1612240

Title:
  [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zmqpp package in Ubuntu:
  Fix Released

Bug description:
  Please update zmqpp to version 4.1.2 with the following patch that I proposed 
upstream (it got merged into their "develop" branch):
  https://github.com/zeromq/zmqpp/pull/167/files

  (alternatively, use master + my patch or develop branch of zmqpp).

  This will require the current git snapshot of the zmq library (which
  will be version 4.2 when it's released) -
  https://github.com/zeromq/libzmq

  All the above is needed to support the new USE_FD socket option, which
  will probably be critical for scopes as snaps.

  == Feature Freeze Exception details ==

  These packages are required by the ongoing work of the unity scopes
  for snappy. Due to unrelated to zeromq issues (unity-scopes-api unit-
  test issues on arm64, possibly due to recent toolchain changes) we did
  not make it in time before Feature Freeze. The packages have been
  prepared and tested in:

  https://launchpad.net/~ci-train-ppa-
  
service/+archive/ubuntu/landing-005/+packages?field.name_filter=&field.status_filter=published&field.series_filter=yakkety

  There is no ABI breakage in zeromq3 so no reverse-depends rebuilds are
  required. The zmqpp package does break ABI so a so bump and rebuild of
  rev-deps was needed, but the currently only consumer of the zmqpp
  packages is unity-scopes-api. The new release of zeromq3 is based on a
  git snapshot as a new stable release of this project is planned in the
  nearest future, so a bit too late for the current plans. Some reverse-
  depends of zeromq3 have been tested to work fine with the new package
  as is.

  We kindly request a FFe for this very particular case.

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

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


[Desktop-packages] [Bug 1622073] Re: zmq::mechanism_t::socket_type_string off-by-one

2016-11-04 Thread Luca Boccassi
Hi,

Good catch!

This is fixed in 4.2.0 already, and I will fix it for the next 4.1
stable release (4.1.7).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1622073

Title:
  zmq::mechanism_t::socket_type_string off-by-one

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  Hello, the zmq::mechanism_t::socket_type_string function in
  ./src/mechanism.cpp appears to have an off-by-one mistake:

  const char *zmq::mechanism_t::socket_type_string (int socket_type) const 
  {   
  static const char *names [] = {"PAIR", "PUB", "SUB", "REQ", "REP",
 "DEALER", "ROUTER", "PULL", "PUSH",
 "XPUB", "XSUB", "STREAM"};
  zmq_assert (socket_type >= 0 && socket_type <= 10);
  return names [socket_type];
  }   

  names[11] is "STREAM" but that triggers the assert.

  Thanks

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

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


[Desktop-packages] [Bug 75850] Re: Pidgin should support OS keyrings

2015-06-13 Thread Luca Boccassi
Hello,

The third-party plugin for Pidgin 2.x mentioned earlier, pidgin-gnome-
keyring by Ali Ebrahim[1], is now packaged and published in Debian (Sid
and Stretch, maintained by me) [2] and Ubuntu (Wily, auto-imported from
Sid) [3].

This version uses Freedesktop's Secret Service API via libsecret, so for
now only Gnome Keyring supports it, as KDE Wallet has not yet been
updated to use libsecret, although I believe it is on the roadmap.

Would this be enough to mark this bug as fixed, pending 15.10 release?

Kind regards,
Luca Boccassi

[1] https://github.com/aebrahim/pidgin-gnome-keyring
[2] https://packages.debian.org/stretch/pidgin-gnome-keyring
[3] https://launchpad.net/ubuntu/+source/pidgin-gnome-keyring

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/75850

Title:
  Pidgin should support OS keyrings

Status in Gaim:
  Won't Fix
Status in Pidgin:
  New
Status in gaim package in Ubuntu:
  Invalid
Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Pidgin should support GNOME Keyring, KWallet, etc.

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

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