From: maximilian attems <max@stro.at>
To: "Martin-Éric Racine" <martin-eric.racine@iki.fi>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: [PATCH] scripts/package/builddeb: upgrade to current practices
Date: Tue, 17 Jul 2012 21:23:05 +0000 [thread overview]
Message-ID: <20120717212305.GV28778@vostochny.stro.at> (raw)
In-Reply-To: <CAPZXPQc02=6FnTb_RmgfpW+A4=N_huZW1FUYdjJ=Nt0Y3pqZ+A@mail.gmail.com>
On Tue, Jul 17, 2012 at 10:46:23PM +0300, Martin-Éric Racine wrote:
> 2012/7/17 Jonathan Nieder <jrnieder@gmail.com>:
> >>
> >> Package: $fwpackagename
> >> Architecture: all
> >> +Conflicts: firmware-linux-free, firmware-linux-nonfree
> >> +Provides: firmware-linux-free, firmware-linux-nonfree
> >> +Replaces: firmware-linux-free, firmware-linux-nonfree
> >
> > I assume you mean Breaks+Replaces. Do the files actually overlap,
> > or is this change being overly cautious? I would expect the files
> > not to overlap because the package build with deb-pkg puts firmware
> > in a versioned subdirectory "/lib/firmware/<version>".
>
> AFAIK they would overlap, hence the Conflicts.
This is wrong and properly fixed in -next.
--
maks
next prev parent reply other threads:[~2012-07-17 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 17:57 [PATCH] scripts/package/builddeb: upgrade to current practices Martin-Éric Racine
2012-07-17 19:39 ` Jonathan Nieder
2012-07-17 19:46 ` Martin-Éric Racine
2012-07-17 21:23 ` maximilian attems [this message]
2012-07-17 23:19 ` Martin-Éric Racine
2012-07-17 23:27 ` Jonathan Nieder
2012-07-18 6:56 ` maximilian attems
2012-07-18 7:21 ` Martin-Éric Racine
2012-07-18 8:05 ` Bjørn Mork
2012-07-18 7:47 ` Bjørn Mork
2012-08-14 15:46 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120717212305.GV28778@vostochny.stro.at \
--to=max@stro.at \
--cc=debian-kernel@lists.debian.org \
--cc=jrnieder@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin-eric.racine@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.