Your message dated Sun, 23 Nov 2014 00:19:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#770406: libv8-3.14.5: Add libv8 virtual package with
dep on latest libv8-#.#.#.
has caused the Debian Bug report #770406,
regarding libv8-3.14.5: Add libv8 virtual package with dep on latest
libv8-#.#.#.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
770406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770406
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libv8-3.14.5
Version: 3.14.5.8-8
Severity: normal
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libv8-3.14.5 depends on:
ii libc6 2.19-10
ii libgcc1 1:4.9.1-12
ii libstdc++6 4.9.1-12
libv8-3.14.5 recommends no packages.
libv8-3.14.5 suggests no packages.
-- no debconf information
Adding a virtual package named libv8 will make it much easier to create
packages which depend on libv8.
I'm having a problem with a binary package I've created which depends on libv8.
If I specify a dependency on
libv8-3.14.5 directly then my package wont install on some systems. If I leave
out the dep then my software
wont run with out the user manually searching for the latest version of libv8
and installing it.
Please help.
--- End Message ---
--- Begin Message ---
Le samedi 22 novembre 2014 à 15:11 -0800, Joseph Coffland a écrit :
> Jérémy,
>
> So you don't want to provide the virtual package because packages which
> depend on it will likely break? I know in at least one case the portion
> of the API that my package used worked with multiple versions of libv8 but
> the package naming issue forced my users to install libv8 manually.
>
> Actually, what I really need to do is get my source package into the
> Debian system. I have a fairly popular and mature Open-Source project but
> I've been overwhelmed by the Debian package submission process and still
> don't fully grock it.
All right,
If you want to use the latest available, just Build-Depend on libv8-dev.
This is the answer closing the bug.
Because libv8 api breaks in unforeseeable ways, it isn't updated to new
branches very often, even in debian/unstable.
In the future, we'll have smooth transitions with libv8-3.26 coexisting
with libv8-3.14 until all software are ported to the new version.
Debian is currently debugging the "jessie" release - you will have a
hard(er) time getting a package uploaded in NEW - and a long time before
it is accepted in the archive. We call that status "freeze".
That doesn't forbid starting to work on the package... what's your
software ? i'm usually curious about software using libv8.
Jérémy.
--- End Message ---
_______________________________________________
Pkg-javascript-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
