This bug was fixed in the package libzen - 0.4.32-1
---
libzen (0.4.32-1) unstable; urgency=medium
* [1ff9bdc] Update debian/watch
* [0fca616] Imported Upstream version 0.4.32
* [a824eea] Drop patch, upstreamed
-- Chow Loong Jin Fri, 06 Nov 2015
On Thu, Jan 08, 2015 at 08:45:32AM -, Ivan Romanov wrote:
Look at package in Fedora
http://pkgs.fedoraproject.org/cgit/libzen.git/tree/?id=de88f55ad00bef4c79595f69c8e71066cfc20eff
You can use the same patch.
Hmm, could you forward it upstream if you haven't done so already?
Thanks.
--
On Thu, Jan 08, 2015 at 03:14:02PM +0800, Chow Loong Jin wrote:
On Wed, Jan 07, 2015 at 08:08:15AM -, Ivan Romanov wrote:
Was:
libzen.so - libzen.so.0.0.0
libzen.so.0 - libzen.so.0.0.0
libzen.so.0.0.0
Now:
libzen.so - libzen.so.0
libzen.so.0 - libzen.so.0.4.30
Look at package in Fedora
http://pkgs.fedoraproject.org/cgit/libzen.git/tree/?id=de88f55ad00bef4c79595f69c8e71066cfc20eff
You can use the same patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
It's upsteamed. ZenLib author just forgot to add new files to sources
tarball. But in really these files there are in git repository.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
Was:
libzen.so - libzen.so.0.0.0
libzen.so.0 - libzen.so.0.0.0
libzen.so.0.0.0
Now:
libzen.so - libzen.so.0
libzen.so.0 - libzen.so.0.4.30
libzen.so.0.4.30
Do you want to see zeroes instead of actually version? Or missed
symbolic link with minor version (libzen.so.0.4 - libzen.so.0.4.30)
--
On Wed, Jan 07, 2015 at 08:08:15AM -, Ivan Romanov wrote:
Was:
libzen.so - libzen.so.0.0.0
libzen.so.0 - libzen.so.0.0.0
libzen.so.0.0.0
Now:
libzen.so - libzen.so.0
libzen.so.0 - libzen.so.0.4.30
libzen.so.0.4.30
Oh, it actually did that? Hmm, let me give it another go.
--
Kind
On Sun, Dec 21, 2014 at 07:50:32PM -, Ivan Romanov wrote:
I would say that it's very very strange ))).
Thanks for explanations. I will do.
No, don't bother. I'm the Debian maintainer, and have seen this bug.
In fact, I saw this bug before making the zenlib update, but decided against
it doesn't handle the library SOVERSIOn properly.
How do it properly? I can fix if there are some issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1401238
Title:
Is there web-interface to send bugreport?
I'm sorry, I don't think there is one.
It's a bit strange the first time, but it actually isn't that hard to submit
bug reports to the Debian BTS. I think all it really requires is that you put
the package name and version number where the bug occurs
I would say that it's very very strange ))).
Thanks for explanations. I will do.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1401238
Title:
bump to new 0.4.30 version
I see that libzen 0.4.30 has been packaged for Debian experimental
(https://tracker.debian.org/pkg/libzen), but it doesn't seem to be using
cmake for building. You may want to discuss this with the Debian
maintainer.
** Tags added: patch upgrade-software-version
--
You received this bug
Is there web-interface to send bugreport? I nevere saw before that I
must use e-mail or special progrum to make bugreport.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
13 matches
Mail list logo