[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Questions before my first upload attempt



Hi,

i wrote:
> >   $ gpg --verify ../libisoburn_1.4.0-1.1_source.changes
> >   ...
> >   gpg: WARNING: This key is not certified with a trusted signature!

Johan Van de Wauw wrote:
> This indicates that you have not set a trust level for that key. If you run
> gpg --edit-key  ABC0A854
> type "trust" and set to: I trust fully (or whatever you trust yourself :-))

The warning vanished only after i set trust to
"5 = I trust ultimately".


> >   W: libburn4: hardening-no-relro usr/lib/libburn.so.4.93.0
> What debhelper version are you using (check debian/compat). 

Was 8.
Inherited from Debian packages libburn_1.3.2-1.1,
libisofs_1.3.2-1.1, libisoburn_1.3.2-1.1.

With 9, the warning changes to

  W: libburn source: package-needs-versioned-debhelper-build-depends 9

I assume because of debian/control line

  Build-Depends: dh-autoreconf, pkg-config, debhelper (>= 8), libcam-dev [kfreebsd-any]

Changing to "(>= 9)" silences the warning of debuild -S.

But now debuild -b fails until i revert the change in
debian/compat. I.e. back to 8.
With 9, debuild -b ends by:

  dh_install: libburn4 missing files (debian/tmp/usr/lib/libburn.so.4*), aborting
  debian/rules:5: recipe for target 'binary' failed
  make: *** [binary] Error 2

Further above i see no problem messages which would deviate
from those of the successful run with compat 8.

We will have to postpone this problem until i succeeded
with uploading.

-----------------------------------------------------------
http://mentors.debian.net/intro-maintainers

The proposed line

  dput mentors your_sourcepackage_1.0.changes

does not really match my two candidates

  libburn_1.4.0-1.1_amd64.changes
  libburn_1.4.0-1.1_source.changes

but i guess it's

  $ dput mentors libburn_1.4.0-1.1_source.changes
  ...
  Good signature on /home/thomas/projekte/debian_dir/libburn_1.4.0-1.1.dsc.
  Uploading to mentors (via http to mentors.debian.net):
    Uploading libburn_1.4.0-1.1.dsc: done.
    Uploading libburn_1.4.0.orig.tar.gz: done.    
    Uploading libburn_1.4.0-1.1.debian.tar.xz: done.
    Uploading libburn_1.4.0-1.1_source.changes: done.
  Successfully uploaded packages.

Confirmation mail arrived:

http://mentors.debian.net/package/libburn
http://mentors.debian.net/debian/pool/main/libb/libburn/libburn_1.4.0-1.1.dsc

I do not yet flag it as seeking a sponsor.
Firstly, because i want to polish it and upload its
two mates libisofs and libisoburn.
Secondly because i already got two offers on debian-user
and will probably approach directly the maintainer team of
dvd+rw-tools, which already accepted one of my patches.

I am not sure whether any of them will have time to be
my mentor, besides the minimum checks needed to authorize
my uploads.

So please help me to thoroughly polish the packages.
I'll apply changes to all three and will upload the other
two when libburn is neatly shining.

-------------------------------------------------------
Glimpse on http://mentors.debian.net/package/libburn :

Looks like i need to re-assign some bugs first.
My changelogs close them where they belong, not where
they have been reported to.

"Debhelper compatibility level 9" is not entirely true,
i fear. See above.

vcs-field-not-canonical looks like the tail tip of the
big problem to take care of debian-specific repositories.

"The uploader is not in the package's "Maintainer" or
 "Uploaders" fields":
I do not feel authorized to add me to any of those fields.


Have a nice day :)

Thomas


Reply to: