Re: xine-lib transition: packages must depend on libxine1-x or libxine1-console, as needed

2009-03-23 Thread Josselin Mouette
Le lundi 23 mars 2009 à 16:44 +, Darren Salt a écrit :
 Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org
totem (U)

Fixed in the svn.

-- 
 .''`.  Debian 5.0 Lenny has been released!
: :' :
`. `'   Last night, Darth Vader came down from planet Vulcan and told
  `-me that if you don't install Lenny, he'd melt your brain.


signature.asc
Description: Ceci est une partie de message	numériquement signée


Re: xine-lib transition: packages must depend on libxine1-x or libxine1-console, as needed

2009-03-23 Thread Sandro Tosi
On Mon, Mar 23, 2009 at 17:44, Darren Salt
li...@youmustbejoking.demon.co.uk wrote:
 Debian Python Modules Team python-modules-t...@lists.alioth.debian.org
   pyxine
...
 Sandro Tosi mo...@debian.org
   pyxine (U)

We only build-dep on libxine-dev and depends are brought in by
substvar, so a binNMU should be enough to update dependencies. Feel
free to coordinate this with release team and others who need them.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: xine-lib transition: packages must depend on libxine1-x or libxine1-console, as needed

2009-03-23 Thread Darren Salt
I demand that Sandro Tosi may or may not have written...

 On Mon, Mar 23, 2009 at 17:44, Darren Salt
li...@youmustbejoking.demon.co.uk wrote:
 Debian Python Modules Team python-modules-t...@lists.alioth.debian.org
   pyxine
 ...
 Sandro Tosi mo...@debian.org
   pyxine (U)

 We only build-dep on libxine-dev and depends are brought in by substvar,
 so a binNMU should be enough to update dependencies.

No; you need to explicitly depend on libxine1-x or libxine1-console, or
packages which depend on python-pyxine must depend on one of these. This
can't be brought in by substvar via binNMU because nothing in libxine-dev can
know or determine whether $source_package requires X output plugins or
console output plugins.

We could use substvars, but they'd have to be used to differentiate not
between libxine1-console and libxine1-x but between libxine1-* and
libxine2-*. I'll see what can be done; for now, just saying libxine1-x or
libxine1-console in the appropriate Depends header is fine, and won't break
things unless you try to build using xine-lib-1.2 (which won't be uploaded to
unstable before we've done an upstream release).

 Feel free to coordinate this with release team and others who need them.

As and when it becomes necessary to do so to get this done in time for the
release of squeeze. Adding a dependency on either of libxine1-{x,console}
won't affect things since the dependency is currently indirectly there
anyway; it's more a matter of not having packages pull in console- or
X-related packages if they're not needed, and so long as these dependencies
remain in libxine1{,-plugins}, this isn't a disruptive change which requires
coordination other than just making sure that all affected packages are
updated first.

I intend to wait until all listed packages which need to be updated are
updated and the updated versions present in testing before completing this
transition; there's nothing that I can see in it which will block migration
if it's completed as part of normal uploads.

-- 
| Darren Salt| linux or ds at  | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Buy less and make it last longer. INDUSTRY CAUSES GLOBAL WARMING.

Even the boldest zebra fears the hungry lion.


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: xine-lib transition: packages must depend on libxine1-x or libxine1-console, as needed

2009-03-23 Thread Adeodato Simó
* Darren Salt [Mon, 23 Mar 2009 18:01:15 +]:

  Debian Python Modules Team python-modules-t...@lists.alioth.debian.org
    pyxine

  We only build-dep on libxine-dev and depends are brought in by substvar,
  so a binNMU should be enough to update dependencies.

 No; you need to explicitly depend on libxine1-x or libxine1-console, or
 packages which depend on python-pyxine must depend on one of these.

I think, if pyxine are just Python bindings for libxine, that it’s
appropriate for it not to depend on either flavour, and indeed expect
that packages using pyxine will add the appropriate flavoured
dependency.

Cheers,

-- 
- Are you sure we're good?
- Always.
-- Rory and Lorelai


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org