Hi Reinhard,
On Wed, Jul 29, 2020, 14:03 Reinhard Tartler wrote:
> I think I've implemented this feature here:
> https://salsa.debian.org/debian/devscripts/-/merge_requests/189
>
Awesome, that's exactly the functionality that I was looking for! Thanks
for authoring that change!
AFAIUI it needs
Hi Dod and thanks for the suggestion.
On Wed, Jul 29, 2020, 11:08 Dominique Dumont wrote:
> On Wednesday, 22 July 2020 05:58:26 CEST Olek Wojnar wrote:
> > However, upstream also includes a configuration file or two required for
> > Package A in a directory containing several dozen Package B fil
urce tarball for various reasons.
> Excluding a single file or a directory is trivial. Excluding a pattern of
> files (e.g. *.jar) is just as easy. However, I can't figure out how to
> exclude *all* of the files in a directory *except* for one or two that are
> needed.
>
> Use
On Wednesday, 22 July 2020 05:58:26 CEST Olek Wojnar wrote:
> However, upstream also includes a configuration file or two required for
> Package A in a directory containing several dozen Package B files.
In this case, I would politely ask upstream to move the configuration files in
another locati
quot;Files-Excluded:" from the source tarball for various reasons.
Excluding a single file or a directory is trivial. Excluding a pattern of
files (e.g. *.jar) is just as easy. However, I can't figure out how to
exclude *all* of the files in a directory *except* for one or two that are
On Mon, Jun 19, 2017 at 10:34:42PM +0200, Muri Nicanor wrote:
> Thank you Andrey and Mattia, that worked. For the record, I've added the
> files to Files-Excluded, ran mk-origtargz -S +ds1
> ../usbguard_0.7.0.orig.tar.gz and then ran gbp import-orig
> ../usbguard_0.7.0+ds1.orig.tar.gz and used 0.7.
Hi,
On 06/19/2017 06:13 PM, Mattia Rizzolo wrote:
> On Mon, Jun 19, 2017 at 06:43:43PM +0500, Andrey Rahmatullin wrote:
>> On Mon, Jun 19, 2017 at 03:38:24PM +0200, Muri Nicanor wrote:
>>> I've imported a source package into git using gbp import-orig --uscan,
>>> then updated the changelog with gb
On Mon, Jun 19, 2017 at 06:43:43PM +0500, Andrey Rahmatullin wrote:
> On Mon, Jun 19, 2017 at 03:38:24PM +0200, Muri Nicanor wrote:
> > I've imported a source package into git using gbp import-orig --uscan,
> > then updated the changelog with gbp dch and then made a lot of changes
> > (and commited
On Mon, Jun 19, 2017 at 03:38:24PM +0200, Muri Nicanor wrote:
> I've imported a source package into git using gbp import-orig --uscan,
> then updated the changelog with gbp dch and then made a lot of changes
> (and commited them). Now I added a file to Files-Excluded: in
> debian/copyright- but whe
hi list,
I've imported a source package into git using gbp import-orig --uscan,
then updated the changelog with gbp dch and then made a lot of changes
(and commited them). Now I added a file to Files-Excluded: in
debian/copyright- but when I run gbp buildpackage, it still generates a
source-packag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 04/10/2012 23:10, Bas van den Dikkenberg a écrit :
> Maybe of my package burp,
>
> Hurd-i386 and s390x keeps failing.
>
> And can't find the problem
>
Hi,
This is no reason to remove those arches from the list. It's OK to
fail (unless, of cou
Hi Rodolfo,
On Fri, Oct 05, 2012 at 12:23:52AM +0200, Rodolfo García Peñas wrote:
> Do you need the run_test in the package building?
The build may succeed without the test but may produce a package failing on the
aspects that were tested. Needs further investigation. I suggest that Bas
asks he
ht-
> Van: Rodolfo García Peñas [mailto:k...@kix.es]
> Verzonden: donderdag 4 oktober 2012 22:00
> Aan: Bas van den Dikkenberg
> CC: 'debian-mentors@lists.debian.org'
> Onderwerp: Re: exclude
>
> On Thu, 04 Oct 2012, Bas van den Dikkenberg escribió:
>
> >
;
Onderwerp: Re: exclude
On Thu, 04 Oct 2012, Bas van den Dikkenberg escribió:
> How can i exclude hurd-i386 from a build
>
> With kind regards,
>
>
> Bas van den Dikkenberg
>
Hi Bas,
why are you excluding it? do you have problems with it? Can we help you?
Cheers,
kix
On Thu, 04 Oct 2012, Bas van den Dikkenberg escribió:
> How can i exclude hurd-i386 from a build
>
> With kind regards,
>
>
> Bas van den Dikkenberg
>
Hi Bas,
why are you excluding it? do you have problems with it? Can we help you?
Cheers,
kix
--
||// //\\//
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 04/10/2012 16:53, Boris Pek a écrit :
> Hi,
>
>> How can i exclude hurd-i386 from a build
>
> Architecture: linux-any kfreebsd-any
>
> Best wishes, Boris
>
>
Hi,
Please note that it is usually not useful to
Hi,
> How can i exclude hurd-i386 from a build
Architecture: linux-any kfreebsd-any
Best wishes,
Boris
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lis
How can i exclude hurd-i386 from a build
With kind regards,
Bas van den Dikkenberg
Jonas Meurer writes:
> On 02/07/2009 Piotr Ożarowski wrote:
> > PS consider switching to python-support or we'll force you to do
> > this in few months ;-)
>
> thanks for the last suggestion. I finally noticed that python-support
> already supports to exclude
sn't relevant for the
> > functionality of zope itself.
> >
> > Zope2.11.3 still requires python2.4, so when the package is installed,
> > python-central exits with a byte-compiling error, see below.
> >
> > Is there any possiblity to exclude/ignore the mo
> Zope2.11.3 still requires python2.4, so when the package is installed,
> python-central exits with a byte-compiling error, see below.
>
> Is there any possiblity to exclude/ignore the modules in question at
> byte-compilation time? I found -X for dh_pycentral, but that one doesn'
n the package is installed,
python-central exits with a byte-compiling error, see below.
Is there any possiblity to exclude/ignore the modules in question at
byte-compilation time? I found -X for dh_pycentral, but that one doesn't
seem to do what I expected it to do.
Another solution would be to
"Paul Wise" <[EMAIL PROTECTED]> writes:
> You probably want a custom regex in the -i option to dpkg-source.
The biggest problem here is I don't want to lose the effect of the
*existing* buildpackage ignore list that 'dpkg-source' uses. I just
want to ignore an *additional* directory.
So it seems
Ben Finney <[EMAIL PROTECTED]> writes:
> In other words (and thank you for asking questions until I know how
> to ask this): I want an additional directory to be removed from the
> Debian source package, the same way '.bzr/' and '.hg/' and 'CVS/' et
> al are removed when building the Debian source
"Joe Smith" <[EMAIL PROTECTED]> writes:
> "Ben Finney" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
> > It's close. Bugs Everywhere is (like 'ditrack') designed to have
> > the bug database for a project in a DVCS keep its bug database in
> > the version-controlled files. It do
"Ben Finney" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
It's close. Bugs Everywhere is (like 'ditrack') designed to have the
bug database for a project in a DVCS keep its bug database in the
version-controlled files. It does this by maintaining a bug database
in a hidden dir
On Sun, Apr 27, 2008 at 11:57:29PM +1000, Ben Finney wrote:
> Osamu Aoki <[EMAIL PROTECTED]> writes:
>
> > Now that I checked latest command, -i and -I without argument seems
> > to be good enough since current default regexp is very exhaustive.
>
> Okay. In this case, though, I have a directory
Osamu Aoki <[EMAIL PROTECTED]> writes:
> Now that I checked latest command, -i and -I without argument seems
> to be good enough since current default regexp is very exhaustive.
Okay. In this case, though, I have a directory in the working tree
that *isn't* covered by the defaults for those optio
Hi,
On Sun, Apr 27, 2008 at 02:33:44PM +1000, Ben Finney wrote:
> Osamu Aoki <[EMAIL PROTECTED]> writes:
>
> > On Thu, Apr 24, 2008 at 10:31:21PM -0400, Felipe Sateler wrote:
> > > Ben Finney wrote:
> > >
> > > > What would be the best way to kee
Osamu Aoki <[EMAIL PROTECTED]> writes:
> On Thu, Apr 24, 2008 at 10:31:21PM -0400, Felipe Sateler wrote:
> > Ben Finney wrote:
> >
> > > What would be the best way to keep such a directory in place, but
> > > exclude the directory from the Debian source an
Osamu Aoki <[EMAIL PROTECTED]> writes:
> On Thu, Apr 24, 2008 at 10:31:21PM -0400, Felipe Sateler wrote:
> > Ben Finney wrote:
> >
> > > What would be the best way to keep such a directory in place,
> > > but exclude the directory from the Debian source a
On Thu, Apr 24, 2008 at 10:31:21PM -0400, Felipe Sateler wrote:
> Ben Finney wrote:
>
> > What would be the best way to keep such a directory in place, but
> > exclude the directory from the Debian source and binary packages?
>
> dpkg-source -i"regexp"?
I a
Russ Allbery <[EMAIL PROTECTED]> writes:
> Ben Finney <[EMAIL PROTECTED]> writes:
> > They're useful to someone who will be using the VCS to track
> > changes, because they contain bug information that is useful only
> > in the context of that VCS data.
>
> Is this some additional VCS that the de
Ben Finney <[EMAIL PROTECTED]> writes:
> Felipe Sateler <[EMAIL PROTECTED]> writes:
>> BTW, why are there files useful to you but not other developers?
> They're useful to someone who will be using the VCS to track changes,
> because they contain bug information that is useful only in the context
Felipe Sateler <[EMAIL PROTECTED]> writes:
> BTW, why are there files useful to you but not other developers?
They're useful to someone who will be using the VCS to track changes,
because they contain bug information that is useful only in the
context of that VCS data.
They aren't useful to some
Hubert Chathi <[EMAIL PROTECTED]> writes:
> Ben Finney <[EMAIL PROTECTED]> said:
>
> > Yikes. So, in order to filter out an additional pattern, I can't
> > just say "ignore this pattern as well as the defaults". I have to
> > construct a *single* regexp that contains the default pattern
> > *plus
On Fri, 25 Apr 2008 13:34:04 +1000, Ben Finney <[EMAIL PROTECTED]> said:
> However:
> = $ man dpkg-source [...] -i[regexp] You may specify a perl
> regular expression to match files you want filtered out of the list of
> files for the diff. [...] There can only be one active regexp, of
> mu
Ben Finney wrote:
> Felipe Sateler <[EMAIL PROTECTED]> writes:
>
>> Ben Finney wrote:
>>
>> > What would be the best way to keep such a directory in place, but
>> > exclude the directory from the Debian source and binary packages?
>>
>> dp
Felipe Sateler <[EMAIL PROTECTED]> writes:
> Ben Finney wrote:
>
> > What would be the best way to keep such a directory in place, but
> > exclude the directory from the Debian source and binary packages?
>
> dpkg-source -i"regexp"?
Thanks. That lo
Ben Finney wrote:
> What would be the best way to keep such a directory in place, but
> exclude the directory from the Debian source and binary packages?
dpkg-source -i"regexp"?
--
Felipe Sateler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
removed
by the 'debian/rules clean' action; the files need to remain in the
working tree.
What would be the best way to keep such a directory in place, but
exclude the directory from the Debian source and binary packages?
--
\ "If you can do no good, at least do
Am Montag, den 11.02.2008, 19:48 +0100 schrieb Bernhard R. Link:
> * Daniel Leidert <[EMAIL PROTECTED]> [080211 15:21]:
> > If you care
> > and if you want to avoid this: preserve the original config.* scripts
> > and put them back in the clean-target. This increases the whole
> > debian/rules file
* Daniel Leidert <[EMAIL PROTECTED]> [080211 15:21]:
> If you care
> and if you want to avoid this: preserve the original config.* scripts
> and put them back in the clean-target. This increases the whole
> debian/rules file for around 4 lines.
much easier: just delete in the clean target and put
Il giorno Mon, 11 Feb 2008 17:36:03 +0100
Cyril Brulebois <[EMAIL PROTECTED]> ha scritto:
> On 11/02/2008, David Paleino wrote:
> > Not true:
> > [Snip unrelated logic stuff.]
I can't understand how what I wrote is "unrelated", but let's go on.
> [..]
>
> Now, moving that to a Makefile:
> ,
On 11/02/2008, David Paleino wrote:
> Not true:
> [Snip unrelated logic stuff.]
Yes, true. Functionally, you want foo => bar. Check (assuming here foo
is absent):
,
| [EMAIL PROTECTED]:~$ [ ! -f foo ] && echo "Doing bar 1"
| Doing bar 1
| [EMAIL PROTECTED]:~$ [ -f foo ] && echo "Doin
Il giorno Mon, 11 Feb 2008 10:55:04 -0500
Justin Pryzby <[EMAIL PROTECTED]> ha scritto:
> A set -e shell script doesn't terminate if a nonzero return value is a
> part of a conditional/test. However in a makefile, the exit status of
> the shell can be nonzero even if it was a due to a test "faili
On Mon, Feb 11, 2008 at 04:42:34PM +0100, David Paleino wrote:
> Il giorno Mon, 11 Feb 2008 15:19:08 +0100 Daniel Leidert <[EMAIL PROTECTED]>
> ha scritto:
>
> > Copy the config.* scripts after the clean target has been called (e.g.
> > in the config.status target) then they are simply not part o
Il giorno Mon, 11 Feb 2008 16:50:33 +0100
Cyril Brulebois <[EMAIL PROTECTED]> ha scritto:
> On 11/02/2008, David Paleino wrote:
> > This seems to me more hackish than it should; is there a cleaner way
> > to do it (maybe I'm just complicating myself and don't see The Easy
> > Way [1])?
>
> You co
On 11/02/2008, David Paleino wrote:
> This seems to me more hackish than it should; is there a cleaner way
> to do it (maybe I'm just complicating myself and don't see The Easy
> Way [1])?
You could have a look at how cdbs does it, which might help.
> [1] I know that using "[ ! test ] || ..." is
Il giorno Mon, 11 Feb 2008 15:23:46 +0100
Daniel Leidert <[EMAIL PROTECTED]> ha scritto:
> Sorry, I broke the subject with my last post. I wanted to adjust it, but
> forgot finish the subject line. Really sorry.
...and I read this post a second later having sent my reply. Please fix the
subject o
Il giorno Mon, 11 Feb 2008 15:19:08 +0100
Daniel Leidert <[EMAIL PROTECTED]> ha scritto:
> Copy the config.* scripts after the clean target has been called (e.g.
> in the config.status target) then they are simply not part of the
> diff.gz. Of course they would be after a second build run. If you
Sorry, I broke the subject with my last post. I wanted to adjust it, but
forgot finish the subject line. Really sorry.
Regards, Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e they would be after a second build run. If you care
and if you want to avoid this: preserve the original config.* scripts
and put them back in the clean-target. This increases the whole
debian/rules file for around 4 lines.
This *is* much more easier than any other suggestion I read in th
Hello,
many thanks for the suggestions.
Faw helped me to figure out what was wrong.
The (previously) undocumented trick (not at manpages) is that when using
--exclude argument, one MUST completely and explicitly list files to be
installed, and where to.
One must not use dh_install --autodest and
On Tue, Jan 29, 2008 at 12:08:02AM -0200, Andre Felipe Machado wrote:
> many thanks for your suggestions.
> Unfortunately, it did not work as expected.
> Reading the debian/rules file [0] you could see that it is the binary
> target in a multibinary rules file.
>
> It seems
Hello,
many thanks for your suggestions.
Unfortunately, it did not work as expected.
Reading the debian/rules file [0] you could see that it is the binary
target in a multibinary rules file.
It seems that the --exclude argument is simply ignored.
If I use a packagename.install file containing
'-p' or '-N' options to specify packages.
> I tried the following lines:
> dh_install --exclude=JavaBridge.war -a
> dh_install -XJavaBridge.war -a
> dh_install --exclude=war -a
> Without success.
> What am I missing?
> Should I u
Hello,
I am trying to NOT install a file into a multibinary rule [0].
After the building, a given directory contains a file that should be
installed
in another binary package.
I tried the following lines:
dh_install --exclude=JavaBridge.war -a
dh_install -XJavaBridge.war -a
Hello everybody,
I'm after bug #399276, but I'm not able to find a good solution to
exclude some files from byte-compilation to get rid of that error.
Is there any pycentral/pysupport routine to invoke or something? Any
help will be appreciated.
Thank you,
--
Luca
--
To UNSUBSCR
On Sun, Feb 06, 2005 at 11:20:28PM -0400, Maykel Moya wrote:
> I'm building a program which generates some files under usr/include,
> that I don't want inside the package.
>
> What is the recommended way to exclude those packages from being
> packaged ?
Remove the f
I'm building a program which generates some files under usr/include,
that I don't want inside the package.
What is the recommended way to exclude those packages from being
packaged ?
Regards
mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe&quo
ng a multi-binary package, one
> > of whose binary packages won't build on the alpha architecture currently due
> > to a compiler problem. I'd like to build the other packages (which all work
> > fine) for the Alpha, so that they can be uploaded to unstable, and I
ulti-binary package, one
> > of whose binary packages won't build on the alpha architecture currently due
> > to a compiler problem. I'd like to build the other packages (which all work
> > fine) for the Alpha, so that they can be uploaded to unstable, and I'd like
won't build on the alpha architecture currently due
> to a compiler problem. I'd like to build the other packages (which all work
> fine) for the Alpha, so that they can be uploaded to unstable, and I'd like to
> explicitly exclude Alpha for that package so that nothing tries to b
e to build the other packages (which all work
fine) for the Alpha, so that they can be uploaded to unstable, and I'd like to
explicitly exclude Alpha for that package so that nothing tries to build it
until I can find a fix.
Is there a way to say 'all except alpha' on the Architecture: li
won't build on the alpha architecture currently due
> to a compiler problem. I'd like to build the other packages (which all work
> fine) for the Alpha, so that they can be uploaded to unstable, and I'd like to
> explicitly exclude Alpha for that package so that nothing tries to b
e to build the other packages (which all work
fine) for the Alpha, so that they can be uploaded to unstable, and I'd like to
explicitly exclude Alpha for that package so that nothing tries to build it
until I can find a fix.
Is there a way to say 'all except alpha' on the Architectur
Hallo! Du (Domenico Andreoli) hast geschrieben:
>in debian/control you have to put in "Architecture" field all the archs
>but hurd for the package that will not compile unde hurd.
ok. done that already...
>i'll point to the relevant page of the packaging manual, but feel free to
>read it all :)
Hallo! Du (Domenico Andreoli) hast geschrieben:
>in debian/control you have to put in "Architecture" field all the archs
>but hurd for the package that will not compile unde hurd.
ok. done that already...
>i'll point to the relevant page of the packaging manual, but feel free to
>read it all :
On Fri, Dec 22, 2000 at 03:25:54PM +0100, Cord Beermann wrote:
> Hi.
ciao
>
> I've build a package which includes two binaries (jove, an editor with
> a X-Frontend). Now i've found out that i can't build the X-Frontend on
> the Hurd yet (missing xview-dev).
>
> How can i produce a source-packag
Hi.
I've build a package which includes two binaries (jove, an editor with
a X-Frontend). Now i've found out that i can't build the X-Frontend on
the Hurd yet (missing xview-dev).
How can i produce a source-package, that simply builds only the
editor on the hurd, and builds both packages on the
On Fri, Dec 22, 2000 at 03:25:54PM +0100, Cord Beermann wrote:
> Hi.
ciao
>
> I've build a package which includes two binaries (jove, an editor with
> a X-Frontend). Now i've found out that i can't build the X-Frontend on
> the Hurd yet (missing xview-dev).
>
> How can i produce a source-packa
Hi.
I've build a package which includes two binaries (jove, an editor with
a X-Frontend). Now i've found out that i can't build the X-Frontend on
the Hurd yet (missing xview-dev).
How can i produce a source-package, that simply builds only the
editor on the hurd, and builds both packages on the
73 matches
Mail list logo
