Hugo Vanwoerkom wrote:
Hi,
I am trying to build a deb with Architecture: i386 on a system that runs
amd64.
Funny thing is I did it on Dec.18:
http://lists.debian.org/debian-user/2012/12/msg00795.html
But I cannot repeat it! As soon as I put Architecture: i386 in the file
he says
he builds t
Ricardo Lima wrote:
Hi,
I have already solved my problem.
I am going to try to explain what I did.
1 - Downloaded, compiled and installed xfree86 4.4.0
2 - Discovered all the packages .deb made from xfree86 sources ->
http://ftp.debian.org/debian/pool/main/x/xfree86/
3 - With grep and a script, I c
Hi,
I have already solved my problem.
I am going to try to explain what I did.
1 - Downloaded, compiled and installed xfree86 4.4.0
2 - Discovered all the packages .deb made from xfree86 sources ->
http://ftp.debian.org/debian/pool/main/x/xfree86/
3 - With grep and a script, I created automatically
Hi,
I have already solved my problem.
I am going to try to explain what I did.
1 - Downloaded, compiled and installed xfree86 4.4.0
2 - Discovered all the packages .deb made from xfree86 sources ->
http://ftp.debian.org/debian/pool/main/x/xfree86/
3 - With grep and a script, I created automatical
Arnt Karlsen wrote:
On Mon, 08 Mar 2004 16:03:34 +,
Ricardo Lima <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
Hi,
I am trying to install the xfree86 4.4.0 from sources in a debian
testing machine running kernel 2.6.3.
I was able to compile xfree86 and install it.
Now I would li
On Mon, 08 Mar 2004 16:03:34 +,
Ricardo Lima <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
>
> Hi,
> I am trying to install the xfree86 4.4.0 from sources in a debian
> testing machine running kernel 2.6.3.
> I was able to compile xfree86 and install it.
> Now I would like to us
Hello
Piero wrote:
> I have just (re)installed the whole of Debian Woody and I'm confronted
> with a problem I encoutered when I first installed it. My video card is
> a Radeon 9000, not recognised by the X server (and may-be by the X
> libraries) belonging to the Debian distributions. The other
[EMAIL PROTECTED] wrote:
>At the beginning of May, Colin Watson kindly gave me the following
>advice to solve a problem I then had. I changed my whole approach to
>an email setup and did not use his advice. Now, having again 'changed
>direction', I need to change 'postfix' for 'nullmailer'. ( I ha
adding the source and change the package line has fixed it,
thanks for the fast response
Neil
- Original Message -
From: "Colin Watson" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, February 20, 2001 10:58 AM
Subject: Re: equivs errors
> "Neil Grant" <[
"Neil Grant" <[EMAIL PROTECTED]> wrote:
>I am trying to create a dumby package for qmail, I have created a ctl file
>from the template (the attached file),
[...]
>parsechangelog/debian: error: badly formatted heading line, at changelog
>line 1
You need a "Source:" line in the first block of the co
Hi,
Brien> Maintainer: [EMAIL PROTECTED]
This has to be:
Maintainer: Michael O'Brien <[EMAIL PROTECTED]>
Ciao,
Martin
Hola~
I've attached the file. I've tried equivs-build with a blank Changelog: line,
without a Changelog: line, and with an empty Changelog file.
MO
>-- On Sat, Jul 08, 2000 at 09:53:45AM +0200, % wrote:
> Hi,
>
> Brien> dh_installchangelogs
> Brien> parsechangelog/debian: error: badly formatted
Hi,
Brien> dh_installchangelogs
Brien> parsechangelog/debian: error: badly formatted trailer line, at changelog
line 5
Brien> dh_installchangelogs: changelog parse failure
Brien> make: *** [binary-arch] Error 1
Brien> Error during the build process: Illegal seek at /usr/bin/equivs-build
line 162
On Sun, Oct 03, 1999 at 07:18:23PM -, Pollywog wrote:
> BTW the error seems to be "Standards-Version:" should be just "Version:"
Standards-Version specifies which version of the policy document the
package complies with. Version specifies the version of the package.
--
Mark Brown mailto:[
On 03-Oct-99 Pollywog wrote:
>
> On 03-Oct-99 Pollywog wrote:
>>
>> On 03-Oct-99 Mark Brown wrote:
>>> This package has no epoch number, so its version number less than that
>>> of the official package. If you add an epoch to your fake package
>>> everything should work as planned.
>>
>> Thank
On 03-Oct-99 Pollywog wrote:
>
> On 03-Oct-99 Mark Brown wrote:
>> This package has no epoch number, so its version number less than that
>> of the official package. If you add an epoch to your fake package
>> everything should work as planned.
>
> Thanks, I am beginning to remember about the e
On 03-Oct-99 Mark Brown wrote:
> This package has no epoch number, so its version number less than that
> of the official package. If you add an epoch to your fake package
> everything should work as planned.
Thanks, I am beginning to remember about the epoch now. I tried to add one
but it did
On Sun, Oct 03, 1999 at 04:56:16PM -, Pollywog wrote:
> I am trying to install some new deb packages and I am using a *fake* qt1g
> package which I made with the equivs utility. Geheimnis will not upgrade
> because the version of qt I have (the fake) is too new. I have never seen
> this probl
* "Werner" == Werner Reisberger <[EMAIL PROTECTED]> wrote:
Werner> I doesn't help me since perl (the interpreter) is one of the
Werner> packages I have to fake. Maybe I could replace my perl with
Werner> perl5 (if this has support for the Berkeley DB > 2.0) but I
Werner> wasn't able to find this
On Sun, Aug 08, 1999 at 04:10:27PM +0200, Martin Bialasinski wrote:
> Werner> I tried to use the latest unstable version of equivs but this
> Werner> version depends on a debian perl package and that is exactly
> Werner> one of the packages I would like to fake with equivs.
>
> equivs 1.999.9 depe
* "Pollywog" == Pollywog <[EMAIL PROTECTED]> wrote:
Pollywog> I don't see the problem, and I was able to install a newer
Pollywog> kcrontabs package with no problem. The older kcrontabs
Pollywog> package was looking for an older kdelibs version, kdelibs0 I
Pollywog> believe it was.
Your fake p
On 08-Aug-99 Martin Bialasinski wrote:
>
> Maybe it depended on a specific verision you did not provide or
> such. Checking dpkg -s your-fake-package and dpkg --info
> problematic-package.deb should show why it doesn't work.
Unfortunately, I forgot to keep the package that I installed (the fake
* "Pollywog" == Pollywog <[EMAIL PROTECTED]> wrote:
Pollywog> It worked for me, though I did have a problem with one
Pollywog> package (kcrontab I believe) when I tried to install it. It
Pollywog> would not see my fake kdelibs, if I recall correctly.
Maybe it depended on a specific verision yo
On 08-Aug-99 Martin Bialasinski wrote:
>
> Werner> I tried to use the latest unstable version of equivs but this
> Werner> version depends on a debian perl package and that is exactly
> Werner> one of the packages I would like to fake with equivs.
>
> equivs 1.999.9 depends on perl | perl5, so t
* "Werner" == Werner Reisberger <[EMAIL PROTECTED]> wrote:
Werner> I installed equivs (stable version) and put the line perl,
Werner> perl5 into /etc/equivs.conf but the installation of sysutils
Werner> still fails complaining about a not installed perl5 package
Werner> (btw searching for a perl5
>> "LC" == Lex Chive <[EMAIL PROTECTED]> writes:
LC> So, did I miss something? How am I supposed to use equivs, I just
LC> put the package name in /etc/equivs.conf and run debian/rules
LC> binary, right?
The equivs package in slink doesn't work with apt too well. You would
have to bump up the ve
>> "DM" == Damon Muller <[EMAIL PROTECTED]> writes:
DM> Why am I getting all those unresolved dependencies? I thought that
DM> was what equivs was for?
The version in slink does not work well with apt. You installed a new
equivs package with different dependencies, but there is a equivs with
th
27 matches
Mail list logo
