Hi lumin,
2016-12-02 14:36 GMT-02:00 lumin :
> Hi mentors,
>
> I need advise on the way maintaining symbols control file when
> the mangled C++ symbols are unstable.
>
> I'm maintaining a package named "Caffe". I migrated the same
> source from experimental
On 02/12/16 18:11, Jérémy Lal wrote:
2016-12-02 18:08 GMT+01:00 Ghislain Vaillant :
On 02/12/16 16:36, lumin wrote:
Hi mentors,
I need advise on the way maintaining symbols control file when
the mangled C++ symbols are unstable.
I'm maintaining a package named "Caffe". I mi
Hi,
>I need advise on the way maintaining symbols control file when
>the mangled C++ symbols are unstable.
maintaining symbols on C++ projects is a nightmare.
and do subsequent uploads is done also by qt* folks
(see e.g. qtbase uploads).
You can consider however some things, e.g. m
2016-12-02 18:08 GMT+01:00 Ghislain Vaillant :
> On 02/12/16 16:36, lumin wrote:
>>
>> Hi mentors,
>>
>> I need advise on the way maintaining symbols control file when
>> the mangled C++ symbols are unstable.
>>
>> I'm maintaining a package
On 02/12/16 16:36, lumin wrote:
Hi mentors,
I need advise on the way maintaining symbols control file when
the mangled C++ symbols are unstable.
I'm maintaining a package named "Caffe". I migrated the same
source from experimental to unstable, and it FTBFS'ed as you
se
Hi mentors,
I need advise on the way maintaining symbols control file when
the mangled C++ symbols are unstable.
I'm maintaining a package named "Caffe". I migrated the same
source from experimental to unstable, and it FTBFS'ed as you
see at [0], due to the mangled C++ symb
Thank you for advise, Russ Allbery and Paul Wise.
I'll try it later :)
--
Regards,
C.D.Luminate
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1423134462.2546.1
On Wed, Feb 4, 2015 at 12:37 PM, lumin wrote:
> This is the 1.10's changelog part:
> 1 fortune-zh (1.10) unstable; urgency=low
> 2
> 3 * QA upload.
...
> 12 -- Emanuele Rocca Mon, 20 Jan 2014
> 23:14:42 +0100
As it was a QA upload and Emanuele R
lumin writes:
> I'm a very newbie trying to adopt a package, according to the Debian new
> maintainer's guide. My target package is now "fortune-zh", as it seems
> to be very simple to work with (to fix chinese character typo that I
> noticed).
> In the 1.10 version (jessie, unstable) of fortun
Hi,
I'm a very newbie trying to adopt a package, according to the Debian new
maintainer's guide.
My target package is now "fortune-zh", as it seems to be very simple to
work with (to fix chinese character typo that I noticed).
In the 1.10 version (jessie, unstable) of fortune-zh, I found this lin
On Sat, Jan 04, 2014 at 10:22:29PM +, T o n g wrote:
> Hi,
>
> > "pkg-has-shlibs-control-file-but-no-actual-shared-libs is sometimes
> triggered for packages with a private shared library due to a bug in
> Debhelper"
>
> That seems to have bitten me.
Hi,
> "pkg-has-shlibs-control-file-but-no-actual-shared-libs is sometimes
triggered for packages with a private shared library due to a bug in
Debhelper"
That seems to have bitten me.
E: zh-autoconvert: pkg-has-shlibs-control-file-but-no-actual-shared-libs
W: zh-autoconvert:
Hi,
I'd like to rephrase this question a bit (and also fixed the spacing of
my quote in my example query below a bit which was somehow spoiled a
bit). We found a way to create a set of debian/control. files.
What would you consider the best way to make sure to bring the correct
control file
metapackages for Blends and
thus now we have to deal me the syntax of the debian/control file. Here is
the part of the discussion[2]:
> On Fri, Jun 21, 2013 at 10:15 AM, Andreas Tille wrote:
>
> >
> > --architecture: This is more complex. Finally we want to build *one*
> >
Hi,
I'm unsure whether this might be the proper mailing list to ask
questions like this - but I have no better idea.
I intend to parse some machine readable files in some team maintained
packages. When trying something like
ctrl = open('debian/control','r')
for ctrlstanza in deb822.Packag
Tony Houghton writes:
> I'm a bit confused about the Vcs fields in Control files. Many projects
> have the upstream code and debian packaging maintained separately and
> I'm not entirely sure what you're supposed to do with the Vcs fields in
> that case. Should they point to upstream or the packa
On Fri, Oct 21, 2011 at 03:10:06PM +0100, Tony Houghton wrote:
> I'm a bit confused about the Vcs fields in Control files. Many projects
> have the upstream code and debian packaging maintained separately and
> I'm not entirely sure what you're supposed to do with the Vcs fields in
> that case. Sho
I'm a bit confused about the Vcs fields in Control files. Many projects
have the upstream code and debian packaging maintained separately and
I'm not entirely sure what you're supposed to do with the Vcs fields in
that case. Should they point to upstream or the packaging? How can
tools, such as deb
Hi,
I have a compiled kernel module for the specific kernel version and I want to
create a deb package for it. I want to run "depmod -aeF /boot/System.map-$kvers
$kvers" in postinst script. How can I define kvers in control file and access
it in postinst script? I am using cons to c
On Sun, Dec 12, 2010 at 01:21:20AM +0100, Emmanuel Kasper wrote:
> Hello
> With a couple of other folks following ITP #424905, I am trying to
> get a newer version of MAME, the arcade emulator in debian. We have
> now a working package and I am trying to understand how to properly
> create virtual
Hello
With a couple of other folks following ITP #424905, I am trying to get a
newer version of MAME, the arcade emulator in debian. We have now a
working package and I am trying to understand how to properly create
virtual package since we have to deal with a rename in upstream ( The
Unix Por
Goswin von Brederlow wrote:
> Thomas Goirand writes:
>
>
>
> Srpm does have Build-Depends, right?
>
> MfG
> Goswin
>
>
Sure! It's called BuildRequires: in the spec files.
Thomas
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe".
Thomas Goirand writes:
> - Original message -
>> We were talking about dpkg-parsechangelog.
>>
>> MfG
>>Â Â Â Â Â Â Â Â Goswin
>
> Are you saying that dpkg-parsechangelog must also be available in RedHat like
> distros? Sorry, I didn't get it, but now I think you are quite right.
nd say: can you make this easier to do cross-platform work with both
> these package systems like linux filesystem standard?
>
> DEBIAN is roughly equivalent to SPECS: change to a common third like PACK.
> SOURCES is practically the same as the root of DEBIAN, change to a
> common sch
- Original message -
> We were talking about dpkg-parsechangelog.
>
> MfG
> Goswin
Are you saying that dpkg-parsechangelog must also be available in RedHat like
distros? Sorry, I didn't get it, but now I think you are quite right.
Thomas
--
To UNSUBSCRIBE, email to debi
Thomas Goirand writes:
> Goswin von Brederlow wrote:
>> Then change that. :)
>>
>> We have rpm in Debian. Let them have dpkg.
>>
>> MfG
>> Goswin
>
> As much as I know, dpkg and debootstrap are both available as RPM
> packages for CentOS. But that doesn't mean you can use dpkg to instal
Goswin von Brederlow wrote:
> Then change that. :)
>
> We have rpm in Debian. Let them have dpkg.
>
> MfG
> Goswin
As much as I know, dpkg and debootstrap are both available as RPM
packages for CentOS. But that doesn't mean you can use dpkg to install
stuffs on your system. RPM and dpkg
Thomas Goirand writes:
> Russ Allbery wrote:
>
> Thomas Goirand writes:
>
>
>
> then in your debian/rules build rule, you can do something like:
>
>
>
>
> MY_VERS=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
> cut -d'-' -f1`
> MY_DEB_REL=`head
Russ Allbery wrote:
Thomas Goirand writes:
then in your debian/rules build rule, you can do something like:
MY_VERS=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
cut -d'-' -f1`
MY_DEB_REL=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')'
Thomas Goirand writes:
> then in your debian/rules build rule, you can do something like:
> MY_VERS=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
> cut -d'-' -f1`
> MY_DEB_REL=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
> cut -d'-' -f2`
> MY_PKGNAME=`head -n 1 d
.
Unify control file and spec header names they are practically the same thing.
-- IV
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.
ause it can access the spec file header information this is
> pretty easy to do. For deb this looks like I am going to have to parse
> the control file to get this information out. Is there any bash
> control file parsers out there?
>
No, parsing the control file might be dangerous, there&#x
within the instance
directory tree in a known location in order to facilitate recovery and
maintenance (this last part is already worked out).
rpm because it can access the spec file header information this is
pretty easy to do. For deb this looks like I am going to have to parse
the control file
On Friday 30 April 2010 11:12:57 Ignacio Valdes wrote:
> So I am gathering that whereas it is repugnant to the dpkg design
> scheme to do it, but for the sake of rpm reconciliation the thread
> subject question: accessing control file values in postinst is not
> simple to do other tha
Ignacio Valdes wrote:
> rpm doesn't. I am going through the joy of trying to reconcile the two
> systems so as to not have two divergent code bases as much as
> possible.
>
> -- IV
>
And I can't believe that any policy for any RPM based distro is advising to
print such useless information. IMHO,
* Ignacio Valdes [100430 18:04]:
> rpm doesn't. I am going through the joy of trying to reconcile the two
> systems so as to not have two divergent code bases as much as
> possible.
Sorry to say it that harsh: I doubt anyone here will be able to help
you. We are focused on doing high-quality Debi
So I am gathering that whereas it is repugnant to the dpkg design
scheme to do it, but for the sake of rpm reconciliation the thread
subject question: accessing control file values in postinst is not
simple to do other than with major changes like sed pre-processing and
such?
Is that the
rpm doesn't. I am going through the joy of trying to reconcile the two
systems so as to not have two divergent code bases as much as
possible.
-- IV
On Fri, Apr 30, 2010 at 9:57 AM, Goswin von Brederlow wrote:
>>
>> echo "The package: %{Package}-%{Version} is now installed."
>>
>> How would one
Ignacio Valdes wrote:
Required to produce versions for both rpm and deb. No introspection
means not easy to convert this from rpm to deb which is where this
started. This would make it much easier to produce both deb and rpm
versions if it has the ability to introspect those variables.
If all
d want to factor things a bit. Maybe you could
>> suggest some modifications to the maintainer of the RPM package so you
>> can share changes with him later on.
>
> That is pretty much what I have been doing. But how about something as
> simple as accomplishing this in postinst
On Friday 30 April 2010 07:48:59 Ignacio Valdes wrote:
> That is pretty much what I have been doing. But how about something as
> simple as accomplishing this in postinst using the control file
> variables?
>
> echo "The package: %{Package}-%{Version} is now installed.
> suggest some modifications to the maintainer of the RPM package so you
> can share changes with him later on.
That is pretty much what I have been doing. But how about something as
simple as accomplishing this in postinst using the control file
variables?
echo "The package: %{Package}-%{
Ignacio Valdes wrote:
On Thu, Apr 29, 2010 at 9:03 PM, Thomas Goirand wrote:
Ignacio Valdes wrote:
It is a very complex, large package.
Does anyone know the mechanics of doing introspection in postinst for
the control file defined variables
Ignacio Valdes writes:
> So there is no cross-compatibility between debian control file and rpm
> spec file for introspecting their respective package variables?
There is no cross-compatibility between Debian package building and RPMs
at all. They are not even remotely similar systems
So there is no cross-compatibility between debian control file and rpm
spec file for introspecting their respective package variables? -- IV
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o
On Thu, Apr 29, 2010 at 9:03 PM, Thomas Goirand wrote:
> Ignacio Valdes wrote:
>> It is a very complex, large package.
>> Does anyone know the mechanics of doing introspection in postinst for
>> the control file defined variables?
>>
> Exactly why the postinst g
Ignacio Valdes wrote:
> It is a very complex, large package.
> Does anyone know the mechanics of doing introspection in postinst for
> the control file defined variables?
>
Exactly why the postinst generation method that has been given as a
(pretty good) solution would not w
On Thu, Apr 29, 2010 at 5:11 PM, Russ Allbery wrote:
> Ignacio Valdes writes:
>> On Thu, Apr 29, 2010 at 3:55 PM, Russ Allbery wrote:
>>> Ignacio Valdes writes:
>
>>>> So what is the usual method of accessing control file values such as
>>>> Pac
Ignacio Valdes writes:
> On Thu, Apr 29, 2010 at 3:55 PM, Russ Allbery wrote:
>> Ignacio Valdes writes:
>>> So what is the usual method of accessing control file values such as
>>> Package: in postinst?
>> Generally, you don't, since generally there'
On Thu, Apr 29, 2010 at 3:55 PM, Russ Allbery wrote:
> Ignacio Valdes writes:
>
>> So what is the usual method of accessing control file values such as
>> Package: in postinst?
>
> Generally, you don't, since generally there's no reason to do so. I can't
Ignacio Valdes writes:
> So what is the usual method of accessing control file values such as
> Package: in postinst?
Generally, you don't, since generally there's no reason to do so. I can't
say I've ever had any reason to want to do that in any of the Debian
packa
So what is the usual method of accessing control file values such as
Package: in postinst?
What is the usual method of accessing user-defined control file values
such as XC-branding in postinst?
I would have presume that using variables such as %{Package} or
%{branding} in postinst would have
Ignacio Valdes writes:
> Hi, I want to define a variable such as package_initials in control
> file and be able to access %{package_initials} in postinst file. Do I
> define it in control file as:
>
> XC-package_initials: the_initials
>
> or some other way?
>
> -- IV
Have to package two .deb flavors as well as two .rpm versions. Can do
this with rpm using .rpmmacros but looking for the equivalent in .deb.
Is this not possible? The manuals seem to indicate that it is but not
exactly how. -- IV
On Sat, Apr 24, 2010 at 10:37 PM, Paul Wise wrote:
> Why do you wa
Why do you want to do this?
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/r2ke13a36b31004242037j5fcea87r1cb00d808f
Hi, I want to define a variable such as package_initials in control
file and be able to access %{package_initials} in postinst file. Do I
define it in control file as:
XC-package_initials: the_initials
or some other way?
-- IV
--
To UNSUBSCRIBE, email to debian-mentors-requ
Paul Wise wrote:
> On Thu, Apr 9, 2009 at 7:16 PM, Jaromír Mikeš wrote:
>
>> X: slv2: spelling-error-in-binary ./usr/bin/lv2_jack_host succesfully
>> successfully
>> X: slv2: spelling-error-in-binary ./usr/bin/lv2_simple_jack_host succesfully
>> successfully
>
> These two you need to tell upstr
> Od: Paul Wise
> You should only run that manually to create the initial symbols file,
> dh_makeshlibs should take care of running the right dpkg-gensymbols
> call during the build process.
> In addition you generally need to strip the Debian version from each
> symbol as explained by the linti
On Fri, Apr 10, 2009 at 9:27 PM, Jaromír Mikeš wrote:
> I put this line to my debian/rules:
>
> dpkg-gensymbols -plibslv2-9 -Olibslv2-9.symbols
You should only run that manually to create the initial symbols file,
dh_makeshlibs should take care of running the right dpkg-gensymbols
call during the
> Od: Paul Wise
> > I: libslv2-9: no-symbols-control-file usr/lib/libslv2.so.9.1.1
> >
> > Can someone advice me please how satisfied lintian?
>
> First, make sure you have read and understood libpkg-guide:
>
> http://www.netfort.gr.jp/~dancer/column/libpkg-gu
eir spelling error.
Patching the source code for this is optional since it is such a minor
issue, if you wanted to be pro-active you could make a patch and send
it upstream.
> I: libslv2-9: no-symbols-control-file usr/lib/libslv2.so.9.1.1
>
> Can someone advice me please how satisfied linti
Hello mentors,
I have this output for lintian -IE
X: slv2: spelling-error-in-binary ./usr/bin/lv2_jack_host succesfully
successfully
X: slv2: spelling-error-in-binary ./usr/bin/lv2_simple_jack_host succesfully
successfully
I: libslv2-9: no-symbols-control-file usr/lib/libslv2.so.9.1.1
Can
Am Mittwoch, 6. Juli 2005 11:57 schrieb Adeodato Simó:
> * Markus Schulz [Wed, 06 Jul 2005 11:48:01 +0200]:
> > Depends: other-packages-from-source-pckg (>=replace current version
> > variable)
>
>(>= ${Source-Version})
thanks, works fine.
Markus Schulz
* Markus Schulz [Wed, 06 Jul 2005 11:48:01 +0200]:
> Depends: other-packages-from-source-pckg (>=replace current version variable)
(>= ${Source-Version})
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
The easy way is the wrong way, an
Hello,
i want to use the current version number in package build process replaced in
my control file. Is this possible?
I have 10 packages build from my source package and one of them is an meta
package which installs most of the other packages cause of Depends on them.
Now i want to integrate
Zeno Davatz (2002-10-04 11:13:59 +0200) :
> On 2.10.2002 19:28 Uhr, "Simon Richter" <[EMAIL PROTECTED]> wrote:
>
>> The "i" in front of the comma.
>>
>> Simon
> Thanks. Do you have an idea why my Debian still wants to install
> apache-common when I make apt-get install php4?
Maybe because php
Zeno Davatz (2002-10-04 11:13:59 +0200) :
> On 2.10.2002 19:28 Uhr, "Simon Richter" <[EMAIL PROTECTED]> wrote:
>
>> The "i" in front of the comma.
>>
>> Simon
> Thanks. Do you have an idea why my Debian still wants to install
> apache-common when I make apt-get install php4?
Maybe because ph
On 2.10.2002 19:28 Uhr, "Simon Richter" <[EMAIL PROTECTED]> wrote:
> The "i" in front of the comma.
>
> Simon
Thanks. Do you have an idea why my Debian still wants to install
apache-common when I make apt-get install php4?
My control file is now (sorry the
On 2.10.2002 19:28 Uhr, "Simon Richter" <[EMAIL PROTECTED]> wrote:
> The "i" in front of the comma.
>
> Simon
Thanks. Do you have an idea why my Debian still wants to install
apache-common when I make apt-get install php4?
My control file is now (sorry the
On 2.10.2002 19:28 Uhr, "Simon Richter" <[EMAIL PROTECTED]> wrote:
> The "i" in front of the comma.
>
> Simon
Thanks. Do you have an idea why my Debian still wants to install
apache-common when I make apt-get install php4?
My control file is now:
Sou
On 2.10.2002 19:28 Uhr, "Simon Richter" <[EMAIL PROTECTED]> wrote:
> The "i" in front of the comma.
>
> Simon
Thanks. Do you have an idea why my Debian still wants to install
apache-common when I make apt-get install php4?
My control file is now:
Sou
Zeno,
On Thu, Oct 03, 2002 at 08:05:32PM +0200, Zeno Davatz wrote:
> > Watch out for syntax errors happening by using vi. :-)
> Sorry I am a newbie. Where are they?
The "i" in front of the comma.
Simon
--
GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD ADC6 18A0 CC8D 5706 A4B4
pgpsGxM16bNno.pg
Zeno,
On Thu, Oct 03, 2002 at 05:56:33PM +0200, Zeno Davatz wrote:
> Source: apache-ssl-ywesee
> Section: web
> Priority: optional
> Maintainer: ywesee <[EMAIL PROTECTED]>
> Build-Depends: debhelper (>> 3.0.0)i, libncurses5 (>= 5.2.20020112a-7 ),
> libssl0.9.6 (>= 0.9.6c-2.woody.1 ), openssl (>= 0
Hi,
Sven LUTHER:
> Mmm, is Provides a superset of Replaces, or do you have to specify both
They simply have different semantics. It's better not to conflate them.
--
Matthias Urlichs | noris network AG | http://smurf.noris.de/
On Thursday 03 October 2002 11:05, Zeno Davatz wrote:
>
> If I do apt-get install php4
>
> My Debian still asks me to install apache-common - Why?
>
> Thanks for your help.
>
> Zeno
Because php4 depends on a version of apache-common and Provides does not help
with version depends.
As I commented
rovides says "for
all intents and purposes treat me as this other package when doing depends
checks".
So if package foo has file /etc/bar which used to be in package bar you say
Replaces: bar. If package foo or package bar can be installed to satisfy the
same depends you put a Provide
;. The "Replaces" is not needed.
Did not work: my control file is now:
Source: apache-ssl-ywesee
Section: web
Priority: optional
Maintainer: ywesee <[EMAIL PROTECTED]>
Build-Depends: debhelper (>> 3.0.0)i, libncurses5 (>= 5.2.20020112a-7 ),
libssl0.9.6 (>= 0.9.6c-2.wo
On Thu, Oct 03, 2002 at 06:29:46PM +0100, David Given wrote:
> On Thu, 2002-10-03 at 16:56, Zeno Davatz wrote:
> [...]
> > Why do the dependency-manager not know that I already got apache-ssl
> > installed. I wrote in my control file that apache-ssl-ywesee replaces
> &g
On Thursday 03 October 2002 08:56, Zeno Davatz wrote:
>
> My Debian tells me that I need to install apache-common.
>
> Why do the dependency-manager not know that I already got apache-ssl
> installed. I wrote in my control file that apache-ssl-ywesee replaces
> apache, apache-
On Thu, 2002-10-03 at 16:56, Zeno Davatz wrote:
[...]
> Why do the dependency-manager not know that I already got apache-ssl
> installed. I wrote in my control file that apache-ssl-ywesee replaces
> apache, apache-common, apache-ssl
All Replaces: does is ensure that if you install a
Zeno,
On Thu, Oct 03, 2002 at 08:05:32PM +0200, Zeno Davatz wrote:
> > Watch out for syntax errors happening by using vi. :-)
> Sorry I am a newbie. Where are they?
The "i" in front of the comma.
Simon
--
GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD ADC6 18A0 CC8D 5706 A4B4
msg07391/pgp00
Zeno,
On Thu, Oct 03, 2002 at 05:56:33PM +0200, Zeno Davatz wrote:
> Source: apache-ssl-ywesee
> Section: web
> Priority: optional
> Maintainer: ywesee <[EMAIL PROTECTED]>
> Build-Depends: debhelper (>> 3.0.0)i, libncurses5 (>= 5.2.20020112a-7 ),
> libssl0.9.6 (>= 0.9.6c-2.woody.1 ), openssl (>=
Hi,
Sven LUTHER:
> Mmm, is Provides a superset of Replaces, or do you have to specify both
They simply have different semantics. It's better not to conflate them.
--
Matthias Urlichs | noris network AG | http://smurf.noris.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
On Thursday 03 October 2002 11:05, Zeno Davatz wrote:
>
> If I do apt-get install php4
>
> My Debian still asks me to install apache-common - Why?
>
> Thanks for your help.
>
> Zeno
Because php4 depends on a version of apache-common and Provides does not help
with version depends.
As I commente
rovides says "for
all intents and purposes treat me as this other package when doing depends
checks".
So if package foo has file /etc/bar which used to be in package bar you say
Replaces: bar. If package foo or package bar can be installed to satisfy the
same depends you put a Provide
Hi List
My control file for our Apache-SSL-ywesee looks like this:
Source: apache-ssl-ywesee
Section: web
Priority: optional
Maintainer: ywesee <[EMAIL PROTECTED]>
Build-Depends: debhelper (>> 3.0.0)i, libncurses5 (>= 5.2.20020112a-7 ),
libssl0.9.6 (>= 0.9.6c-2.woody.1 ), op
;. The "Replaces" is not needed.
Did not work: my control file is now:
Source: apache-ssl-ywesee
Section: web
Priority: optional
Maintainer: ywesee <[EMAIL PROTECTED]>
Build-Depends: debhelper (>> 3.0.0)i, libncurses5 (>= 5.2.20020112a-7 ),
libssl0.9.6 (>= 0.9.6c-2.wo
On Thu, Oct 03, 2002 at 06:29:46PM +0100, David Given wrote:
> On Thu, 2002-10-03 at 16:56, Zeno Davatz wrote:
> [...]
> > Why do the dependency-manager not know that I already got apache-ssl
> > installed. I wrote in my control file that apache-ssl-ywesee replaces
> &g
On Thursday 03 October 2002 08:56, Zeno Davatz wrote:
>
> My Debian tells me that I need to install apache-common.
>
> Why do the dependency-manager not know that I already got apache-ssl
> installed. I wrote in my control file that apache-ssl-ywesee replaces
> apache, apache-
On Thu, 2002-10-03 at 16:56, Zeno Davatz wrote:
[...]
> Why do the dependency-manager not know that I already got apache-ssl
> installed. I wrote in my control file that apache-ssl-ywesee replaces
> apache, apache-common, apache-ssl
All Replaces: does is ensure that if you install a
Hi List
My control file for our Apache-SSL-ywesee looks like this:
Source: apache-ssl-ywesee
Section: web
Priority: optional
Maintainer: ywesee <[EMAIL PROTECTED]>
Build-Depends: debhelper (>> 3.0.0)i, libncurses5 (>= 5.2.20020112a-7 ),
libssl0.9.6 (>= 0.9.6c-2.woody.1 ), op
On Sat, Apr 13, 2002 at 07:46:44PM +0200, Daniel Lutz wrote:
> Well, this is actually a bug in dpkg-gencontrol. This bug was reported
> as #56056 and then closed, but it seems that this bug appeared again
> in a newer version of dpkg-dev.
Thanks. I'll file in a new bug report on dpkg-dev.
Alexa
On Sat, Apr 13, 2002 at 07:46:44PM +0200, Daniel Lutz wrote:
> Well, this is actually a bug in dpkg-gencontrol. This bug was reported
> as #56056 and then closed, but it seems that this bug appeared again
> in a newer version of dpkg-dev.
Thanks. I'll file in a new bug report on dpkg-dev.
Alex
s file contains version-independent details about the source
package and about the binary packages it creates.
It is a series of sets of control fields, each syntactically similar
to a binary package control file. The sets are separated by one or
more blank lines. The first set is inform
Well, this is not a question. I've just spent several hours wondering
what the matter was with a package which refused to build. rules was
failing with the following message:
dpkg-gencontrol: error: per-package paragraph 1 in control info file is
missing Package line
I searched the archive, and f
s file contains version-independent details about the source
package and about the binary packages it creates.
It is a series of sets of control fields, each syntactically similar
to a binary package control file. The sets are separated by one or
more blank lines. The first set is inform
Well, this is not a question. I've just spent several hours wondering
what the matter was with a package which refused to build. rules was
failing with the following message:
dpkg-gencontrol: error: per-package paragraph 1 in control info file is
missing Package line
I searched the archive, and
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
> Hi Julian!
>
> > > The problem I have is that I have a library with same host architecture
> > > but
> > > different cross compilation targets, so I have things like:
> >
> > Build-Depends supports an arch specification, like:
>
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
> Hi Julian!
>
> > > The problem I have is that I have a library with same host architecture but
> > > different cross compilation targets, so I have things like:
> >
> > Build-Depends supports an arch specification, like:
> >
>
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
> Hi Julian!
>
> > > The problem I have is that I have a library with same host architecture
> > > but
> > > different cross compilation targets, so I have things like:
> >
> > Build-Depends supports an arch specification, like:
>
1 - 100 of 153 matches
Mail list logo
