dpkg: serious warning: files list .......

Hi, I succeeded in building my first .deb package.
I created the control file and friends manually, I looked at
the source of maemopadplus for "inspiration".

Using the "Application manager" the package
installs and uninstalls without any problems.
But when I use dpkg I get the following message:

dpkg -i n770-fire_0.1_armel.deb 
Selecting previously deselected package n770-fire.
(Reading database ... 
dpkg: serious warning: files list file for package `armel'
missing, assuming package has no files currently installed.
12900 files and directories currently installed.)
Unpacking n770-fire (from n770-fire_0.1_armel.deb) ...
Setting up n770-fire (0.1) ...


"dpkg-buildpackage -rfakeroot" creates a
debian/files file containing:
n770-fire_1.2_armel.deb user/games optional

I was wondering if anyone knows which newbie mistake I
made?
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Sun, Feb 18, 2007 at 09:18:34PM +0100, Visti Andresen
wrote:
> Hi, I succeeded in building my first .deb package.
> I created the control file and friends manually, I
looked at the source of maemopadplus for
"inspiration".
> 
> Using the "Application manager" the package
installs and uninstalls without any problems.
> But when I use dpkg I get the following message:
> 
> dpkg -i n770-fire_0.1_armel.deb 
> Selecting previously deselected package n770-fire.
> (Reading database ... 
> dpkg: serious warning: files list file for package
`armel' missing, assuming package has no files currently
installed.

That's not good.

> 12900 files and directories currently installed.)
> Unpacking n770-fire (from n770-fire_0.1_armel.deb) ...
> Setting up n770-fire (0.1) ...
> 
> 
> "dpkg-buildpackage -rfakeroot" creates a
debian/files file containing:
> n770-fire_1.2_armel.deb user/games optional

That's not good either.

> I was wondering if anyone knows which newbie mistake I
made?

We can't tell without looking at your source code
(especially the
debian/ directory).

Marius Gedminas
-- 
Never trust a smiling Gates.

_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Mon, 19 Feb 2007 19:04:34 +0200
Marius Gedminas <mariuspov.lt> wrote:

> On Sun, Feb 18, 2007 at 09:18:34PM +0100, Visti
Andresen wrote:
> > Hi, I succeeded in building my first .deb
package.
> > I created the control file and friends manually, I
looked at the source of maemopadplus for
"inspiration".
> > 
> > Using the "Application manager" the
package installs and uninstalls without any problems.
> > But when I use dpkg I get the following message:
> > 
> > dpkg -i n770-fire_0.1_armel.deb 
> > Selecting previously deselected package
n770-fire.
> > (Reading database ... 
> > dpkg: serious warning: files list file for package
`armel' missing, assuming package has no files currently
installed.
> 
> That's not good.
Serious warnings seldom are...

> 
> > 12900 files and directories currently installed.)
> > Unpacking n770-fire (from n770-fire_0.1_armel.deb)
...
> > Setting up n770-fire (0.1) ...
> > 
> > 
> > "dpkg-buildpackage -rfakeroot" creates a
debian/files file containing:
> > n770-fire_1.2_armel.deb user/games optional
> 
> That's not good either.
Any idea what this file should contain?
And how make it contain the proper content, as it seem to be
auto generated.

> 
> > I was wondering if anyone knows which newbie
mistake I made?
> 
> We can't tell without looking at your source code
(especially the
> debian/ directory).

Ups probably should have written this yesterday: 
Sources are available though "svn checkout https://
garage.maemo.org/svn/n770demos"

The debian directory is located under packages/fire/

I use a rather non standard build system (buildpp.pl)
And I additionally have to build multiple packages from the
same set of sources...


> 
> Marius Gedminas
> -- 
> Never trust a smiling Gates.
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Mon, 19 Feb 2007 19:15:31 +0100
Visti Andresen <talpagalnet.dk> wrote:


> > > 
> > > 
> > > "dpkg-buildpackage -rfakeroot"
creates a debian/files file
containing:
> > > n770-fire_1.2_armel.deb user/games optional
> > 
> > That's not good either.
> Any idea what this file should contain?
> And how make it contain the proper content, as it seem
to be auto
generated.

from "man dpkg-buildpackage"

debian/files
  The list of generated files which are part of the  upload 
being
  prepared.  dpkg-gencontrol adds the presumed filenames of
binary
  packages whose control files it generates here;
dpkg-distaddfile
  can  be used to add additional files.  dpkg-genchanges
reads the
  data here when producing a .changes file.


dpkg-DISTADDFILE ARGUMENTS
       dpkg-distaddfile does not take any non-common
options. It takes
three non-option arguments, the filename and the section and
priority
for the .changes file.

       The filename should be specified relative to the
directory where
dpkg-genchanges will expect to find the files, usually ..,
rather than
being a pathname relative to the current directory when
dpkg-distaddfile
is run.

Still not quite sure what dpkg-buildpackage would like me to
add to the files list.
Or when in the rules(makefile) to add them.
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Sun, 2007-02-18 at 21:18:34 +0100, ext Visti Andresen
wrote:
> Hi, I succeeded in building my first .deb package.
> I created the control file and friends manually, I
looked at the
> source of maemopadplus for "inspiration".

I still wonder why the tutorials lead people to build
packages by
hand...

> Using the "Application manager" the package
installs and uninstalls
> without any problems.

You probably have those messages as well if you ask for the
output
log.

> But when I use dpkg I get the following message:
> 
> dpkg -i n770-fire_0.1_armel.deb 
> Selecting previously deselected package n770-fire.
> (Reading database ... 
> dpkg: serious warning: files list file for package
`armel' missing,
> assuming package has no files currently installed.
> 12900 files and directories currently installed.)

This is saying that there's an installed package called
«armel» which
does not have the corresponding
«/var/lib/dpkg/info/armel.list» file.
So you got such package installed somehow and dpkg is
complaining.

> Unpacking n770-fire (from n770-fire_0.1_armel.deb) ...
> Setting up n770-fire (0.1) ...

And the warning message should be unrelated to this
package.

> "dpkg-buildpackage -rfakeroot" creates a
debian/files file containing:
> n770-fire_1.2_armel.deb user/games optional

This file does not have anything to do with the one dpkg is
complaining about, the former being binary package related
the latter
being source package related.

regards,
guillem
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Mon, 2007-02-19 at 19:15:31 +0100, ext Visti Andresen
wrote:
> On Mon, 19 Feb 2007 19:04:34 +0200 Marius Gedminas
wrote:
> > On Sun, Feb 18, 2007 at 09:18:34PM +0100, Visti
Andresen wrote:
> > > "dpkg-buildpackage -rfakeroot"
creates a debian/files file containing:
> > > n770-fire_1.2_armel.deb user/games optional
> >
> > That's not good either.
>
> Any idea what this file should contain?
> And how make it contain the proper content, as it seem
to be auto
> generated.

No, that file is fine.

> > > I was wondering if anyone knows which newbie
mistake I made?
> > 
> > We can't tell without looking at your source code
(especially the
> > debian/ directory).
> 
> Ups probably should have written this yesterday: 
> Sources are available though "svn checkout https://
garage.maemo.org/svn/n770demos"
> 
> The debian directory is located under packages/fire/

There's several problems with your package:

* Do not hardcode the Depends for shared libraries, use a
substvar.
* Why are you using a Pre-Depends?

* You should move the contents of the binary target to
binary-arch, and
  make binary depend on binary-arch and binary-indep.
* You could use a n770-fire.install file istead of the
install calls in
  debian/rules.

* This package will not build when provided as a source
package as it's
  not self contained, you are ascending two dirs up the
hierarchy,
  outside of what's provided in it.

regards,
guillem
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Mon, 2007-02-19 at 21:37:58 +0200, ext Guillem Jover
wrote:
> On Sun, 2007-02-18 at 21:18:34 +0100, ext Visti
Andresen wrote:
> > Hi, I succeeded in building my first .deb
package.
> > I created the control file and friends manually, I
looked at the
> > source of maemopadplus for
"inspiration".
> 
> I still wonder why the tutorials lead people to build
packages by
> hand...

Hmm, what Visti meant with creating the files manually is
different
than the package being built by hand (as in ar + tar + cp,
etc ;).
But I still think there's some tutorial around pointing
people to
use the latter.

regards,
guillem
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Mon, 19 Feb 2007 21:37:58 +0200
Guillem Jover <guillem.jovernokia.com> wrote:

> > But when I use dpkg I get the following message:
> > 
> > dpkg -i n770-fire_0.1_armel.deb 
> > Selecting previously deselected package
n770-fire.
> > (Reading database ... 
> > dpkg: serious warning: files list file for package
`armel' missing,
> > assuming package has no files currently
installed.
> > 12900 files and directories currently installed.)
> 
> This is saying that there's an installed package called
«armel» which
> does not have the corresponding
«/var/lib/dpkg/info/armel.list» file.
> So you got such package installed somehow and dpkg is
complaining.

Indeed, thank you!!!
Don't know why I missed that bit about "for package
`armel'".


Since the package didn't contain any files I asked dpkg to
remove it.
(asked "dpkg -L armel" as well, better safe that
reflashing)
Seems to have fixed my dpkg issue 
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

On Mon, 19 Feb 2007 21:55:52 +0200
Guillem Jover <guillem.jovernokia.com> wrote:

> There's several problems with your package:
> 
> * Do not hardcode the Depends for shared libraries, use
a substvar.

I will have to look into what "substvar" is and
how to use it.
But I remember seeing in a doc somewhere, so I'll go RTFM
ing.

"man dpkg-buildpackage" seams helpful, looks like

dpkg-shlibdeps is useful...
And in the control file I should write  Depends:
${shlibsepends}

It seems that I should still specify the Build-Depends
manually?

> * Why are you using a Pre-Depends?

maemopadplus used it... 
I did notice the "Read: don't use it at all."
warning in DNMG
(Debian New Maintainers' Guide) regarding Pre-Depends.
However as it looked like a package that would enable the
user to select the location,
I thought it might be necessary to have it as a
"Pre-Depends"

Moving it to a Depends?
Will the Application manager handle a missing/unconfigured
package 
and just not ask to a menu location (once I persuades it to
actually ask)?

> 
> * You should move the contents of the binary target to
binary-arch, and
>   make binary depend on binary-arch and binary-indep.

I just created a empty file and filled in the rules that
dpkg-buildpackage
seemed to want, I will move the binary to binary-arch.
This seems to be "the Debian way":
http://www.debian.org/doc/manuals/maint-gui
de/ch-dreq.en.html#s-rules


> * You could use a n770-fire.install file istead of the
install calls in
>   debian/rules.

I will have to read up on that one as well.

> 
> * This package will not build when provided as a source
package as it's
>   not self contained, you are ascending two dirs up the
hierarchy,
>   outside of what's provided in it.

The sources are located two levels up.
But I really should try to generate a multi-binary package.
I hear (from DNMG) that the vim source package is a good
example of 
such a package. I still need to understand the actual way it
works.
But it should allow me to have just one debian directory

At least this should allow the source package that
dpkg-buildpackage creates to be more that just empty.

> 
> regards,
> guillem


Thank you for your time, it has been most helpful.
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers

"ext Guillem Jover" <guillem.jovernokia.com> writes:

> * Why are you using a Pre-Depends?

He is using this pre-depends:

    Pre-Depends: maemo-select-menu-location

This one ultimately comes from the "How to make a
package for the
Application Manager" document here:

    http://maemo.org/pl
atform/docs/howtos/howto_making_an_application_package_bora.
html#utilities

The maemo-select-menu-location utility is supposed to be
used from
maintainer scripts, and I thought that you should pre-depend
on
packages providing these utilities in this case.  Not true?

However, the "fire" package doesn't actually call
maemo-select-menu-location as far as I can see, so this
pre-depend is
unnecessary.
_______________________________________________
maemo-developers mailing list
maemo-developersmaemo.org
h
ttps://maemo.org/mailman/listinfo/maemo-developers