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

questions before uploading libdbd-oracle-perl



Hi,
this is the first time I have to upload something to Debian
archive (I have some previous experience with Launchpad PPAs)
and I'd like to understand the whole process, so I read the
New Maintainers' Guide[0] and now I have a few questions:

* I built the amd64 package only since it took me a long while
  to get Oracle 12 running on unstable. Can I upload amd64 now
  and i386 later if I manage to eventually build it too? How
  should I document that only amd64 is available right now?
  Please, note that it was removed[1] from testing on Aug 2014
  so I feel like having amd64 at least would improve the current
  statu quo.

* Would it be better to upload to experimental first? No tests
  failed in DBD::Oracle, some were skipped though.

* Should I add myself to Uploaders in d/control or there's no
  need since the current maintainer is our team and I'm going
  to make a team upload anyway?

* NMG says[2] that "urgency shouldn't be changed to anything
  higher than low." but d/changelog already has urgency=medium.
  Should I lower it or keep it at medium?

* I guess that it doesn't make sense to enable autopkgtest in
  libdbd-oracle-perl since it has a Depends that's not in the
  archive (oracle-instantclient12.1-basic or basiclite).

* Finally, bug 759324[3] is about this package having conflicts
  with perl 5.20. I suppose I should not close that bug and
  eventually make a backport of the package to jessie, which
  still uses perl 5.20 and we'll be around for a while?

Thanks a lot,
Alex

[0] https://www.debian.org/doc/manuals/maint-guide/
[1] https://tracker.debian.org/news/565367
[2] https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#changelog
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759324


Reply to: