[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#725671: marked as done (different source packages, co-ordinated release to jessie)

Your message dated Mon, 7 Oct 2013 10:42:03 +0200
with message-id <20131007084203.GC29992@mraw.org>
and subject line Re: Bug#725671: different source packages, co-ordinated release to jessie
has caused the Debian Bug report #725671,
regarding different source packages, co-ordinated release to jessie
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 owner@bugs.debian.org
immediately.)


-- 
725671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725671
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org


PostBooks has multiple source packages.  Specifically, there is
src:postbooks (the client) and src:postbooks-schema-(empty|quickstart|demo)

The client can only be used with the matching postbooks-schema version

Is there an automated way to ensure these packages (and future updates)
all propagate to jessie together or not at all?

--- End Message ---
--- Begin Message --- 
Daniel Pocock <daniel@pocock.com.au> (2013-10-07):
> PostBooks has multiple source packages.  Specifically, there is
> src:postbooks (the client) and src:postbooks-schema-(empty|quickstart|demo)
> 
> The client can only be used with the matching postbooks-schema version
> 
> Is there an automated way to ensure these packages (and future updates)
> all propagate to jessie together or not at all?

Sure, get your dependencies right…

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: