Pages

Sunday, October 1, 2017

Debian pkg-perl related package updates

Worked on the following Debian packages today, all of which are under the auspices of the Debian pkg-perl team but which I added to Debian because they are dependencies of the packaging for LedgerSMB.

libmoosex-param-perl - This one has not had a new upstream release since 2007, but has had changes commited by pkg-perl team members which have not yet been released.  This might better have been done last year but taking care of this today with the release and upload to Debian Unstable (Sid) of version 0.02-3 of the Debian package.

libpgobject-perl -  Package updated for a new upstream release and uploaded  Debian Unstable as version 2.000002-1.

libpgobject-type-datetime-perl -  Package updated for a new upstream release and uploaded  to Debian Unstable as version 2.000001-1,

libtemplate-plugin-latex-perl - This one was updated for a new upstream version, 3.12-1, but has since been pending followups about which Debian package for it to Build-Depend on for testing before being released.  Sent another followup email about it.

Monday, July 10, 2017

Debian Perl package updates

Now that Stretch has been released, the Perl modules that I am an uploader for and for which there have been version updates waiting to be packaged can now be worked on, either by me or by others of the Debian pkg-perl team.  This included the following 9 packages:

libpgobject-perl   
libpgobject-simple-perl     
libpgobject-simple-role-perl   
libpgobject-type-bigfloat-perl 
libpgobject-type-bytestring-perl
libpgobject-type-datetime-perl 
libpgobject-type-json-perl 
libpgobject-util-dbmethod-perl  
libtemplate-plugin-latex-perl     

 Checked the debian-policy package again on 20 June & found that 4.0.0-1 is now in unstable, so will be updating that in the packages I do.

Noted during a pkg-perl LHF (Low-hanging fruits) session in IRC debian-perl that both the Standards version up to 4.0.0  as well as debhelper to version 10, were getting updated.  Checked the debhelper package in Debian and Ubuntu;  10.x is in stretch as well as jessie-backports (but not jessie itself as it only has 9.2x), as well as yakkety (16.10) and xenial-backports (but not xenial itself as that only has 9.2x).  All in all; it looks like it's better to also move them to debhelper 10, and if there are any issues with building for older distributions it just won't be able to do a no-change backport to them.


Friday, July 7, 2017

Update libpgobject-type-bigfloat-perl package in Debian

Besides that there is a new upstream and so the package needs updating in any case, there's also that it is showing up with a "fail" in the CI (Continous Integration) reference at my Packages overview where the package is listed: "This package is failing and has previously passed." Several of the other modules have had similar problems although they also had FTBFS (Failed To Build From Source) issues. Found that it was failing tests, possibly because of things like the upgrade to use Perl 5.24 where the tests are running?  Will see if the issue is still present after the update to the new upstream.

In order to use the command 'dpt orig-import'  (one of the pkg-perl tools) well, it likes to have the upstream git repository URL, looking for entries for it in debian/copyright or an 'upstream-repo' remote setting in the git config, or the information being in a debian/upstream/metadata file. The one other time I tried it I added the 'upstream-repo' remote setting manually. That worked but also ended up adding  upstream tags because it also set up an upstream-repo branch where it brought the tags from upstream in order to check for what is the most recent.  Will have to use something like the 'git push --follow-tags' command (which also only require the one command) instead of the using 'git push -tags' command after pushing the commits like I've in the habit of doing.

This package hasn't had the metadata file yet because the necessary information hasn't been in the distribution archive where it could be referenced.  It is in the new upstream, so downloaded the new upstream archive manually in order to verify the information, then added a metadata file as the file debian/upstream/metadata. Imported the new upstream version, using the 'dpt import-orig' command.  Updated the packaging. Then pushed the commits for the release. And the new package version has been uploaded to Debian.



Sunday, June 25, 2017

LedgerSMB 1.5.8 released

Version 1.5.8 of LedgerSMB has been released:

Changelog for 1.5.8
  • Fix printing of AR/AP transactions results in JavaScript error (Erik H)
  • Fix ODS output appearing on 'Title page' instead of 'Search results' (Erik H)
  • Fix Edit Vendor address misses 'Save' button (Erik H, #2709)
  • Fix Recurring Transactions screen fails on second access (Erik H, #2888)
  • Fix 'On Hand' goods search filter not being applied (Erik H, #2584)
  • Clean up issues found by Debian's 'lintian' (Erik H, Robert C)
  • Fix layout regression of 1.5 in single payment screen (Erik H, #1917)
  • Fix 'Update' on Assembly page resetting BOM count to 1 (Erik H, #2835)
  • Fix 'Update' on Assembly page requiring all BOM lines filled (Erik H, #2835)
  • New 'Welcome' screen after login, helping people find help (Erik H)
  • Updated Indonesian translation (LedgerSMB Transifex Indonesian group)

Erik H is Erik Huelsmann
Robert C is Robert James Clay
Note also that the project is no longer hosted at SourceForge but rather has entirely moved to GitHub and separate hosting for the mailing lists and other resources.




Saturday, June 17, 2017

Monday, June 12, 2017

Packaging Plack::Builder::Conditionals for Debian

  I had been working on updating the dependencies  for the LedgerSMB package in Debian which I am in the process of transitioning to the 1.5.x series and also the ledgersmb-1.5 package and it seems I missed that there is still a Perl module required for it that is not yet packaged for Debian:  Plack::Builder::Conditionals.  (At least, I hadn't yet been able to find it in Debian.)

  Working on taking care of that, I created the ITP (Intend To Package) Debian bug to track it: #863454

I was able to get the initial package completed but some issues were found with it. I corrected all of those and it was then uploaded to the Debian New queue.  It was then accepted into unstable as the package libplack-builder-conditionals-perl.  It was also then made available at the LedgerSMB Ubuntu PPA as well as will be made available at the apt.ledgersmb.org package repository as necessary.

Saturday, December 26, 2015

My packages with an 'outdated' package style

'Lucas Nussbaum' posted a message to the debian-devel mailing list about "Packages with /outdated/ packaging style" where one of my packages are listed.  Reference also:

  • https://lists.debian.org/debian-devel/2015/12/msg00383.html
  • http://www.lucas-nussbaum.net/blog/?p=904

The associated blog post  for the post as well as an older blog post on the same issue

  • http://www.lucas-nussbaum.net/blog/?p=891
  • https://www.lucas-nussbaum.net/blog/?p=751


Running the command noted in the post found that my 'postnews' package is listed:
$ ssh alioth.debian.org 'grep -A 2 Clay ~lucas/qa-20151226/*ddlist'
/srv/home/users/lucas/qa-20151226/merged.ddlist:Robert James Clay <jame@rocasa.us>
/srv/home/users/lucas/qa-20151226/merged.ddlist-   postnews
/srv/home/users/lucas/qa-20151226/merged.ddlist-
--
/srv/home/users/lucas/qa-20151226/qa-helper_classic_debhelper.txt.ddlist:Robert James Clay <jame@rocasa.us>
/srv/home/users/lucas/qa-20151226/qa-helper_classic_debhelper.txt.ddlist-   postnews
/srv/home/users/lucas/qa-20151226/qa-helper_classic_debhelper.txt.ddlist-

A comment by Lucas to the earlier blog post clarifies that, noting the following:
Lucas says:
March 4, 2013 at 4:12 pm
@Marcus: by “dh”, I mean “debhelper7″, or “the dh command”. “debhelper”
is “old-style debhelper packaging, with dh_* commands”

I haven't explicitly created a tickit for it but it is already on my TODO list, to have debian/rules use the dh command instead of using the 'dh_*' commands like it is currently.  Plan to make that change with the next upload, which will likely be which package the next upstream version.