Patrick Schleizer:
> I am maintaining two Debian derivatives distributions, Whonix and
> Kicksecure. (Open Source) I hope you don't mind my question.
>
> I am trying to build a custom meta package with 'Architecture: all' that
> has an architecture specific dependency:
> hardened-malloc [amd64]
A
On 13/10/15 18:08, Aaron M. Ucko wrote:
Ghislain Vaillant writes:
So the final solution is to manually list all supported architectures
in d/control (same one as libfftw3-double3) and use your patch for
d/rules?
You can leave Architecture: any in d/control; dpkg-genchanges will warn
about th
Ghislain Vaillant writes:
> So the final solution is to manually list all supported architectures
> in d/control (same one as libfftw3-double3) and use your patch for
> d/rules?
You can leave Architecture: any in d/control; dpkg-genchanges will warn
about the discrepancy, but proceed anyway.
--
On 13/10/15 17:15, Aaron M. Ucko wrote:
"Aaron M. Ucko" writes:
I am testing these changes now (against a checkout of your experimental
branch) and will follow up with a full patch if they work.
I meant
$(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
and
ifeq "" "$(SKIP_NFFTL)"
Hav
"Aaron M. Ucko" writes:
> I am testing these changes now (against a checkout of your experimental
> branch) and will follow up with a full patch if they work.
I meant
$(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
and
ifeq "" "$(SKIP_NFFTL)"
Having fixed those typos, I produced the atta
Ghislain Vaillant writes:
> Architecture: ${libfftw3-long3:Architecture}
Alas, this won't work -- that information isn't available here, and I
don't think substitutions work in the Architecture field anyway.
However, debian/rules can conditionally invoke dh with a suitable -N
flag. I believe i
On Sat, 22 Sep 2012 18:18:06 -0400, Michael Gilbert
wrote:
> I think it would be more appropriate to just close the bug with a
> message indicating that the package should be built on a system with
> multiarch enabled; where the wine-bin dependency would be satisfied
> via wine-bin:i386. Lucas's
On Sat, Sep 22, 2012 at 3:53 PM, Stephen Kitt wrote:
> Dear mentors,
>
> I maintain the wine-gecko package (wine-gecko-1.4), which is in an
> interesting situation because its build-dependencies can't be satisfied on all
> architectures, but it builds an "Architecture: all" package. Something
> sim
Thanks for explenation
-Oorspronkelijk bericht-
Van: Gergely Nagy [mailto:alger...@balabit.hu]
Verzonden: donderdag 31 mei 2012 14:45
Aan: debian-mentors@lists.debian.org
Onderwerp: Re: Architecture dependensie
Bas van den Dikkenberg writes:
> Hello,
>
> I am trying to make
Bas van den Dikkenberg writes:
> Hello,
>
> I am trying to make burp work on HPPA and powerpcspe architectures and
> there for I want to specify witch version of debhelper he must juse.
You're trying to do the wrong thing: debhelper is arch:all, so it will
be the same across architectures. If yo
On Tue, 19 May 2009 14:03:43 +0800, Paul Wise wrote:
> On Tue, May 19, 2009 at 12:43 PM, Laurent Guignard
> wrote:
> > On Thu, 14 May 2009 19:25:46 +0200, Salvatore Bonaccorso wrote:
> >> btw, what "p-a-s" mean in this context?
> >
> > p-a-s : dict say "Publicly Available Specifications (ISO)"
> >
Hi
Ok, p-a-s means Packages-arch-specific, as Paul Wise explained.
On Tue, May 19, 2009 at 06:43:19AM +0200, Laurent Guignard wrote:
> On Thu, 14 May 2009 19:25:46 +0200, Salvatore Bonaccorso wrote:
> > On Thu, May 14, 2009 at 04:26:56PM +0200, Cyril Brulebois wrote:
> > > brian m. carlson (14/0
On Tue, May 19, 2009 at 12:43 PM, Laurent Guignard
wrote:
> On Thu, 14 May 2009 19:25:46 +0200, Salvatore Bonaccorso wrote:
>> btw, what "p-a-s" mean in this context?
>
> p-a-s : dict say "Publicly Available Specifications (ISO)"
> I think this is the correct signification but i am not sure...
Th
Hello Salvatore,
On Thu, 14 May 2009 19:25:46 +0200, Salvatore Bonaccorso wrote:
> Dear reader of debian-mentors,
>
> I read the following, following a discussion on debian-devel, which I
> do not understand.
>
> On Thu, May 14, 2009 at 04:26:56PM +0200, Cyril Brulebois wrote:
> > brian m. carls
Dear reader of debian-mentors,
I read the following, following a discussion on debian-devel, which I
do not understand.
On Thu, May 14, 2009 at 04:26:56PM +0200, Cyril Brulebois wrote:
> brian m. carlson (14/05/2009):
> > I've worked on FTBFS-with-new-GCC bugs before, and realized only after
> >
On 20040927T192545-0400, Hubert Chan wrote:
> In order to compile these properly, I need to detect what architecture
> I am compiling under. What is the suggested/easiest/best/proper/Debian
> way to do this?
I assume what yuo really want to know is what architecture you are
compiling _for_ instea
On 20040927T192545-0400, Hubert Chan wrote:
> In order to compile these properly, I need to detect what architecture
> I am compiling under. What is the suggested/easiest/best/proper/Debian
> way to do this?
I assume what yuo really want to know is what architecture you are
compiling _for_ instea
Hello Hubert,
On Tue, Sep 28, 2004 at 09:32:50AM +1000, Matthew Palmer wrote:
> On Mon, Sep 27, 2004 at 07:25:45PM -0400, Hubert Chan wrote:
> > I am compiling under. What is the suggested/easiest/best/proper/Debian
> > way to do this?
>
> dpkg --print-architecture.
Actually, I think the more p
Hello Hubert,
On Tue, Sep 28, 2004 at 09:32:50AM +1000, Matthew Palmer wrote:
> On Mon, Sep 27, 2004 at 07:25:45PM -0400, Hubert Chan wrote:
> > I am compiling under. What is the suggested/easiest/best/proper/Debian
> > way to do this?
>
> dpkg --print-architecture.
Actually, I think the more p
On Mon, Sep 27, 2004 at 07:25:45PM -0400, Hubert Chan wrote:
> I maintain the hashcash package. Recent upstream versions have
> included optimized assembly routines for MMX (x86) and Altivec (PPC).
> In order to compile these properly, I need to detect what architecture
> I am compiling under. Wh
On Mon, Sep 27, 2004 at 07:25:45PM -0400, Hubert Chan wrote:
> I maintain the hashcash package. Recent upstream versions have
> included optimized assembly routines for MMX (x86) and Altivec (PPC).
> In order to compile these properly, I need to detect what architecture
> I am compiling under. Wh
On Mon, Apr 07, 2003 at 01:13:02PM -0400, Matt Zimmerman wrote:
> On Mon, Apr 07, 2003 at 02:58:16PM +0100, Pete Ryland wrote:
>
> > I get this same error with a .so symlink in a -dev package, which is clearly
> > architecture-independent and definitely belongs in the -dev under /usr/lib/.
>
> Wh
On Mon, Apr 07, 2003 at 01:13:02PM -0400, Matt Zimmerman wrote:
> On Mon, Apr 07, 2003 at 02:58:16PM +0100, Pete Ryland wrote:
> > I get this same error with a .so symlink in a -dev package, which is
> > clearly architecture-independent and definitely belongs in the -dev
> > under /usr/lib/.
>
> W
On Mon, Apr 07, 2003 at 02:58:16PM +0100, Pete Ryland wrote:
> I get this same error with a .so symlink in a -dev package, which is clearly
> architecture-independent and definitely belongs in the -dev under /usr/lib/.
What sort of -dev package is architecture-independent? These are supposed
to
On Mon, Apr 07, 2003 at 10:53:28AM +0800, Federico Sevilla III wrote:
> While checking my package before sending it to my sponsor for uploading,
> I got the following message from linda 0.2.8:
>
> E: zopeedit; File /usr/lib/mime/packages/zopeedit contained in
> /usr/lib of Architecture: al
On Sun, Aug 25, 2002 at 01:12:00AM +0200, Josip Rodin wrote:
> > Are arch-independent packages built sent to the buildd machines for
> > every architecture, then?
>
> Of course not, why would they be?
Er, originally I had it in mind that I'd seen per-arch changes files
propagated into the package
On Sat, Aug 24, 2002 at 04:01:16PM -0700, Devin Carraway wrote:
> > It just uses your build machine's architecture string, but it doesn't affect
> > anything. You might as well replace the arch string with foo in the file
> > name, it wouldn't make a difference, I don't think :)
>
> Are arch-indep
On Sun, Aug 25, 2002 at 12:07:04AM +0200, Josip Rodin wrote:
> It just uses your build machine's architecture string, but it doesn't affect
> anything. You might as well replace the arch string with foo in the file
> name, it wouldn't make a difference, I don't think :)
Are arch-independent packag
On Sat, Aug 24, 2002 at 02:49:31PM -0700, Devin Carraway wrote:
> Something that's been vaguely prodding at me for a while -- when I build
> an architecture-all package, the .deb produced is named
> packagename_v-r_all.deb as I'd expect, but the build also makes a
> packagename_v-r_{arch}.changes f
On Sun, Aug 18, 2002 at 07:10:54PM -0700, Ian Zimmerman wrote:
> Hmmm. My package has actually been Architecture: any from the start.
> Why'd you guys assume otherwise?
Because it's surprising to ship files that are only needed on some
architectures and not to use the normal mechanisms for handli
On Sun, Aug 18, 2002 at 07:10:54PM -0700, Ian Zimmerman wrote:
> Hmmm. My package has actually been Architecture: any from the start.
> Why'd you guys assume otherwise?
Because it's surprising to ship files that are only needed on some
architectures and not to use the normal mechanisms for handl
itz> The package uses a generic name for one of its configuration
itz> files. I want to create a symlink from the generic name to the
itz> correct (architecture-dependent) one.
Matt> So the package is architecture: all, but uses different
Matt> configuration files for different architectures? W
On Sat, Aug 17, 2002 at 11:49:24PM -0700, Ian Zimmerman wrote:
> Matt> Your question has already been answered, but why do you need
> Matt> this information in a maintainer script?
>
> The package uses a generic name for one of its configuration files. I
> want to create a symlink from the gener
itz> The package uses a generic name for one of its configuration
itz> files. I want to create a symlink from the generic name to the
itz> correct (architecture-dependent) one.
Matt> So the package is architecture: all, but uses different
Matt> configuration files for different architectures?
On Sat, Aug 17, 2002 at 11:49:24PM -0700, Ian Zimmerman wrote:
> Matt> Your question has already been answered, but why do you need
> Matt> this information in a maintainer script?
>
> The package uses a generic name for one of its configuration files. I
> want to create a symlink from the gene
At 16:14 +0200 8/18/02, Ian Zimmerman wrote:
>itz> The package uses a generic name for one of its configuration
>itz> files. I >want to create a symlink from the generic name to the
>itz> correct (architecture-dependent) one.
>
>Geert> Could you tell us that makes sence?
Could you tell us t
On Sun, Aug 18, 2002 at 07:14:18AM -0700, Ian Zimmerman wrote:
> Colin> It makes perfect sense if the package he's talking about is
> Colin> Architecture: all.
>
> Colin> Personally I might be inclined to make the package
> Colin> Architecture: any in this case, though.
>
> I assume by this you m
itz> The package uses a generic name for one of its configuration
itz> files. I >want to create a symlink from the generic name to the
itz> correct (architecture-dependent) one.
Geert> Could you tell us that makes sence?
Colin> It makes perfect sense if the package he's talking about is
Colin>
At 16:14 +0200 8/18/02, Ian Zimmerman wrote:
>itz> The package uses a generic name for one of its configuration
>itz> files. I >want to create a symlink from the generic name to the
>itz> correct (architecture-dependent) one.
>
>Geert> Could you tell us that makes sence?
Could you tell us
On Sun, Aug 18, 2002 at 07:14:18AM -0700, Ian Zimmerman wrote:
> Colin> It makes perfect sense if the package he's talking about is
> Colin> Architecture: all.
>
> Colin> Personally I might be inclined to make the package
> Colin> Architecture: any in this case, though.
>
> I assume by this you
itz> The package uses a generic name for one of its configuration
itz> files. I >want to create a symlink from the generic name to the
itz> correct (architecture-dependent) one.
Geert> Could you tell us that makes sence?
Colin> It makes perfect sense if the package he's talking about is
Colin>
On Sun, Aug 18, 2002 at 11:02:44AM +0200, Geert Stappers wrote:
> At 8:49 +0200 8/18/02, Ian Zimmerman wrote:
> >The package uses a generic name for one of its configuration files. I
> >want to create a symlink from the generic name to the correct
> >(architecture-dependent) one.
>
> Could you te
At 8:49 +0200 8/18/02, Ian Zimmerman wrote:
>itz> Hi, how can I easily determine the host architecture string in a
>itz> maintainer script? dpkg-architecture is in the dpkg-dev package,
>itz> which I obviously cannot depend on. I could massage the output
>itz> of uname or arch, but that seems too
On Sun, Aug 18, 2002 at 11:02:44AM +0200, Geert Stappers wrote:
> At 8:49 +0200 8/18/02, Ian Zimmerman wrote:
> >The package uses a generic name for one of its configuration files. I
> >want to create a symlink from the generic name to the correct
> >(architecture-dependent) one.
>
> Could you t
itz> Hi, how can I easily determine the host architecture string in a
itz> maintainer script? dpkg-architecture is in the dpkg-dev package,
itz> which I obviously cannot depend on. I could massage the output
itz> of uname or arch, but that seems too ugly (and I don't even know
itz> what all the
At 8:49 +0200 8/18/02, Ian Zimmerman wrote:
>itz> Hi, how can I easily determine the host architecture string in a
>itz> maintainer script? dpkg-architecture is in the dpkg-dev package,
>itz> which I obviously cannot depend on. I could massage the output
>itz> of uname or arch, but that seems to
itz> Hi, how can I easily determine the host architecture string in a
itz> maintainer script? dpkg-architecture is in the dpkg-dev package,
itz> which I obviously cannot depend on. I could massage the output
itz> of uname or arch, but that seems too ugly (and I don't even know
itz> what all the
On Fri, Aug 16, 2002 at 04:28:53PM -0700, Ian Zimmerman wrote:
> Hi, how can I easily determine the host architecture string in a
> maintainer script? dpkg-architecture is in the dpkg-dev package, which I
> obviously cannot depend on. I could massage the output of uname or arch,
> but that seems
On Fri, Aug 16, 2002 at 04:28:53PM -0700, Ian Zimmerman wrote:
> Hi, how can I easily determine the host architecture string in a
> maintainer script? dpkg-architecture is in the dpkg-dev package, which I
> obviously cannot depend on. I could massage the output of uname or arch,
> but that seem
On Fri, Aug 16, 2002 at 04:28:53PM -0700, Ian Zimmerman wrote:
> Hi, how can I easily determine the host architecture string in a
> maintainer script?
'dpkg --print-installation-architecture' should do it.
--
Colin Watson [EMAIL PROTECTED]
On Fri, Aug 16, 2002 at 04:28:53PM -0700, Ian Zimmerman wrote:
> Hi, how can I easily determine the host architecture string in a
> maintainer script?
'dpkg --print-installation-architecture' should do it.
--
Colin Watson [[EMAIL PROTECTED]]
--
To UNSUBSCRIBE
Hi Robert!
> > For instance, I have a package that can only build on the following
> > architectures:
> >
> > i386 alpha arm powerpc sparc mips mipsel
>
> #104688 states that hppa has failed. How do you know that sh can't
> build it, though? Or hurd-386[1]? Or an architecture that is not even
>
Robert Bihlmeyer <[EMAIL PROTECTED]> writes:
> #104688 states that hppa has failed. How do you know that sh can't
> build it, though? Or hurd-386[1]? Or an architecture that is not even
> known yet?
The package in question is a libc implementation. I think in this
case, it is reasonable to expec
Abraham vd Merwe <[EMAIL PROTECTED]> writes:
> For instance, I have a package that can only build on the following
> architectures:
>
> i386 alpha arm powerpc sparc mips mipsel
#104688 states that hppa has failed. How do you know that sh can't
build it, though? Or hurd-386[1]? Or an architecture
Hi Robert!
> > For instance, I have a package that can only build on the following
> > architectures:
> >
> > i386 alpha arm powerpc sparc mips mipsel
>
> #104688 states that hppa has failed. How do you know that sh can't
> build it, though? Or hurd-386[1]? Or an architecture that is not even
>
Robert Bihlmeyer <[EMAIL PROTECTED]> writes:
> #104688 states that hppa has failed. How do you know that sh can't
> build it, though? Or hurd-386[1]? Or an architecture that is not even
> known yet?
The package in question is a libc implementation. I think in this
case, it is reasonable to expe
Abraham vd Merwe <[EMAIL PROTECTED]> writes:
> For instance, I have a package that can only build on the following
> architectures:
>
> i386 alpha arm powerpc sparc mips mipsel
#104688 states that hppa has failed. How do you know that sh can't
build it, though? Or hurd-386[1]? Or an architectur
On Wed, Aug 01, 2001 at 06:45:16PM +0200, Abraham vd Merwe wrote:
> Hi!
>
> How do I specify all the architectures a package can build on? For instance,
> I have a package that can only build on the following architectures:
>
> i386 alpha arm powerpc sparc mips mipsel
>
> Now, first of all, I'm
On Wed, Aug 01, 2001 at 06:45:16PM +0200, Abraham vd Merwe wrote:
> Hi!
>
> How do I specify all the architectures a package can build on? For instance,
> I have a package that can only build on the following architectures:
>
> i386 alpha arm powerpc sparc mips mipsel
>
> Now, first of all, I'm
[EMAIL PROTECTED] wrote:
>Matt Zimmerman <[EMAIL PROTECTED]> writes:
>> Take a look at dh_make, in the dh-make package, and debhelper, in the package
>> of the same name.
>
>That helped. Thanks. Now I'm working on the control file. I notice
>that jserv's control file sets the architecture to "an
[EMAIL PROTECTED] wrote:
>Now I'm working on the control file. I notice
> that jserv's control file sets the architecture to "any", even though
> the deb-control man page only mentions architecture "all". Which should
> I use?
Use "any" if you are uploading an arch-spe
On 12 Sep 2000 [EMAIL PROTECTED] wrote:
> > Take a look at dh_make, in the dh-make package, and debhelper, in the
> > package
> > of the same name.
>
> That helped. Thanks. Now I'm working on the control file. I notice
> that jserv's control file sets the architecture to "any", even though
>
[EMAIL PROTECTED] wrote:
>Matt Zimmerman <[EMAIL PROTECTED]> writes:
>> Take a look at dh_make, in the dh-make package, and debhelper, in the package
>> of the same name.
>
>That helped. Thanks. Now I'm working on the control file. I notice
>that jserv's control file sets the architecture to "a
[EMAIL PROTECTED] wrote:
>Now I'm working on the control file. I notice
> that jserv's control file sets the architecture to "any", even though
> the deb-control man page only mentions architecture "all". Which should
> I use?
Use "any" if you are uploading an arch-sp
On 12 Sep 2000 [EMAIL PROTECTED] wrote:
> > Take a look at dh_make, in the dh-make package, and debhelper, in the package
> > of the same name.
>
> That helped. Thanks. Now I'm working on the control file. I notice
> that jserv's control file sets the architecture to "any", even though
> the
65 matches
Mail list logo
