[Touch-packages] [Bug 1571087] Re: apt gets confused about a dependency's version, falls over?

2016-06-20 Thread Hans Joachim Desserud 
This bug report is being closed due to your last comment. For future
reference you can manage the status of your own bugs by clicking on the
current status in the yellow line and then choosing a new status in the
revealed drop down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

** Tags added: xenial

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

Title:
  apt gets confused about a dependency's version, falls over?

Status in apt package in Ubuntu:
  Invalid

Bug description:
  This problem affects today's Xenial release candidate.

  I generated a package with mk-build-deps, and tried installing it.
  Here's its control file:

  Package: foo-blort3.23-build-deps
  Version: 3.23.1-76
  Architecture: all
  Maintainer: Buildus Bottus 
  Installed-Size: 10
  Depends: build-essential:amd64, debhelper (>= 7), autoconf, automake, 
autotools-dev, libasound2-dev, libavahi-client-dev, libfaac-dev, libfaad-dev, 
libffi-dev, libfontconfig1-dev, libfreetype6-dev, libgl1-mesa-dev, 
libglu1-mesa-dev, libicu-dev, libmagick++-dev, libpng12-dev, libselinux1-dev, 
libssl-dev, libtiff4-dev | libtiff5-dev, libudev-dev, libx11-dev, 
libxcomposite-dev, libxml2-dev, libxrender-dev, libyaml-dev, m4, 
mesa-common-dev, foo-decklink-sdk-static, foo-yobuild11-boost, 
foo-yobuild11-cmake, foo-yobuild11-curl | libcurl4-openssl-dev, 
foo-yobuild11-gnutls | libgnutls-dev (>= 3.3), foo-yobuild11-gst-plugins-base, 
foo-yobuild11-gstreamer, foo-yobuild11-libusb | libusb-1.0-0-dev (>= 2:1.0.19), 
foo-yobuild11-nettle | nettle-dev (>= 3.1.1), foo-yobuild11-nettle | 
libtasn1-6-dev, foo-yobuild11-nettle | libp11-kit-dev, foo-yobuild11-vars, ruby 
(>= 1:1.9.3.4) | rubygems, ruby-dev, rubygem-json, ttf-dejavu-extra, 
westar-foo-dev
  Section: devel
  Priority: optional
  Multi-Arch: foreign
  Description: build-dependencies for foo-blort3.23
   Dependency package to build the 'foo-blort3.23' package

  (Ignore all those packages that start with foo-, those are local.)

  This worked fine from ubuntu 10.04 through ubuntu 16.04 beta 2, but when I 
updated to final beta (with apt-get dist-upgrade),
  it failed, with error

  Correcting dependencies...Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) foo-blort3.23-build-deps [ amd64 ] < 3.23.1-76 > ( devel )
  Broken foo-blort3.23-build-deps:amd64 Depends on libssl-dev [ amd64 ] < none 
-> 1.0.2g-1ubuntu3 > ( libdevel )
Considering libssl-dev:amd64 1 as a solution to 
foo-blort3.23-build-deps:amd64 -2
Removing foo-blort3.23-build-deps:amd64 rather than change libssl-dev
  Done
   Done
  Starting pkgProblemResolver with broken count: 0
  Starting 2 pkgProblemResolver with broken count: 0
  Done
  The following packages will be REMOVED:
foo-blort3.23-build-deps

  "apt-cache policy libssl-dev" before the problem reports:

  libssl-dev:
Installed: (none)
Candidate: 1.0.2g-1ubuntu4
Version table:
   1.0.2g-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  There seems to be some confusion about the version of libssl-dev: 1.0
  .2g-1ubuntu3 vs 1.0.2g-1ubuntu4  ?

  Installing libssl-dev before installing the package generated by mk-
  build-deps worked around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1571087/+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 1571087] Re: apt gets confused about a dependency's version, falls over?

2016-04-16 Thread Dan Kegel 
Hah.  Invalid.  The confusion came from another package that had been
built against the earlier ssl.  Rebuilding all old packages built
against the earlier beta seems to have solved things.

So at worst, apt's error messages are hard to decipher... but we already
knew that.

Please close and forget this bug was ever filed :-)

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

Title:
  apt gets confused about a dependency's version, falls over?

Status in apt package in Ubuntu:
  New

Bug description:
  This problem affects today's Xenial release candidate.

  I generated a package with mk-build-deps, and tried installing it.
  Here's its control file:

  Package: foo-blort3.23-build-deps
  Version: 3.23.1-76
  Architecture: all
  Maintainer: Buildus Bottus 
  Installed-Size: 10
  Depends: build-essential:amd64, debhelper (>= 7), autoconf, automake, 
autotools-dev, libasound2-dev, libavahi-client-dev, libfaac-dev, libfaad-dev, 
libffi-dev, libfontconfig1-dev, libfreetype6-dev, libgl1-mesa-dev, 
libglu1-mesa-dev, libicu-dev, libmagick++-dev, libpng12-dev, libselinux1-dev, 
libssl-dev, libtiff4-dev | libtiff5-dev, libudev-dev, libx11-dev, 
libxcomposite-dev, libxml2-dev, libxrender-dev, libyaml-dev, m4, 
mesa-common-dev, foo-decklink-sdk-static, foo-yobuild11-boost, 
foo-yobuild11-cmake, foo-yobuild11-curl | libcurl4-openssl-dev, 
foo-yobuild11-gnutls | libgnutls-dev (>= 3.3), foo-yobuild11-gst-plugins-base, 
foo-yobuild11-gstreamer, foo-yobuild11-libusb | libusb-1.0-0-dev (>= 2:1.0.19), 
foo-yobuild11-nettle | nettle-dev (>= 3.1.1), foo-yobuild11-nettle | 
libtasn1-6-dev, foo-yobuild11-nettle | libp11-kit-dev, foo-yobuild11-vars, ruby 
(>= 1:1.9.3.4) | rubygems, ruby-dev, rubygem-json, ttf-dejavu-extra, 
westar-foo-dev
  Section: devel
  Priority: optional
  Multi-Arch: foreign
  Description: build-dependencies for foo-blort3.23
   Dependency package to build the 'foo-blort3.23' package

  (Ignore all those packages that start with foo-, those are local.)

  This worked fine from ubuntu 10.04 through ubuntu 16.04 beta 2, but when I 
updated to final beta (with apt-get dist-upgrade),
  it failed, with error

  Correcting dependencies...Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) foo-blort3.23-build-deps [ amd64 ] < 3.23.1-76 > ( devel )
  Broken foo-blort3.23-build-deps:amd64 Depends on libssl-dev [ amd64 ] < none 
-> 1.0.2g-1ubuntu3 > ( libdevel )
Considering libssl-dev:amd64 1 as a solution to 
foo-blort3.23-build-deps:amd64 -2
Removing foo-blort3.23-build-deps:amd64 rather than change libssl-dev
  Done
   Done
  Starting pkgProblemResolver with broken count: 0
  Starting 2 pkgProblemResolver with broken count: 0
  Done
  The following packages will be REMOVED:
foo-blort3.23-build-deps

  "apt-cache policy libssl-dev" before the problem reports:

  libssl-dev:
Installed: (none)
Candidate: 1.0.2g-1ubuntu4
Version table:
   1.0.2g-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  There seems to be some confusion about the version of libssl-dev: 1.0
  .2g-1ubuntu3 vs 1.0.2g-1ubuntu4  ?

  Installing libssl-dev before installing the package generated by mk-
  build-deps worked around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1571087/+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 1571087] Re: apt gets confused about a dependency's version, falls over?

2016-04-15 Thread Dan Kegel 
Sorry for the messy bug.  I'll try to narrow it down some more.

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

Title:
  apt gets confused about a dependency's version, falls over?

Status in apt package in Ubuntu:
  New

Bug description:
  This problem affects today's Xenial release candidate.

  I generated a package with mk-build-deps, and tried installing it.
  Here's its control file:

  Package: foo-blort3.23-build-deps
  Version: 3.23.1-76
  Architecture: all
  Maintainer: Buildus Bottus 
  Installed-Size: 10
  Depends: build-essential:amd64, debhelper (>= 7), autoconf, automake, 
autotools-dev, libasound2-dev, libavahi-client-dev, libfaac-dev, libfaad-dev, 
libffi-dev, libfontconfig1-dev, libfreetype6-dev, libgl1-mesa-dev, 
libglu1-mesa-dev, libicu-dev, libmagick++-dev, libpng12-dev, libselinux1-dev, 
libssl-dev, libtiff4-dev | libtiff5-dev, libudev-dev, libx11-dev, 
libxcomposite-dev, libxml2-dev, libxrender-dev, libyaml-dev, m4, 
mesa-common-dev, foo-decklink-sdk-static, foo-yobuild11-boost, 
foo-yobuild11-cmake, foo-yobuild11-curl | libcurl4-openssl-dev, 
foo-yobuild11-gnutls | libgnutls-dev (>= 3.3), foo-yobuild11-gst-plugins-base, 
foo-yobuild11-gstreamer, foo-yobuild11-libusb | libusb-1.0-0-dev (>= 2:1.0.19), 
foo-yobuild11-nettle | nettle-dev (>= 3.1.1), foo-yobuild11-nettle | 
libtasn1-6-dev, foo-yobuild11-nettle | libp11-kit-dev, foo-yobuild11-vars, ruby 
(>= 1:1.9.3.4) | rubygems, ruby-dev, rubygem-json, ttf-dejavu-extra, 
westar-foo-dev
  Section: devel
  Priority: optional
  Multi-Arch: foreign
  Description: build-dependencies for foo-blort3.23
   Dependency package to build the 'foo-blort3.23' package

  (Ignore all those packages that start with foo-, those are local.)

  This worked fine from ubuntu 10.04 through ubuntu 16.04 beta 2, but when I 
updated to final beta (with apt-get dist-upgrade),
  it failed, with error

  Correcting dependencies...Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) foo-blort3.23-build-deps [ amd64 ] < 3.23.1-76 > ( devel )
  Broken foo-blort3.23-build-deps:amd64 Depends on libssl-dev [ amd64 ] < none 
-> 1.0.2g-1ubuntu3 > ( libdevel )
Considering libssl-dev:amd64 1 as a solution to 
foo-blort3.23-build-deps:amd64 -2
Removing foo-blort3.23-build-deps:amd64 rather than change libssl-dev
  Done
   Done
  Starting pkgProblemResolver with broken count: 0
  Starting 2 pkgProblemResolver with broken count: 0
  Done
  The following packages will be REMOVED:
foo-blort3.23-build-deps

  "apt-cache policy libssl-dev" before the problem reports:

  libssl-dev:
Installed: (none)
Candidate: 1.0.2g-1ubuntu4
Version table:
   1.0.2g-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  There seems to be some confusion about the version of libssl-dev: 1.0
  .2g-1ubuntu3 vs 1.0.2g-1ubuntu4  ?

  Installing libssl-dev before installing the package generated by mk-
  build-deps worked around the problem.

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