kicad-developers team mailing list archive

[Jacob Schmidt <tiger12506@xxxxxxxxx>]

Is this the sort of thing you're looking for Adam?
I'm not familiar with the debian package build process--if this doesn't 
cut it, then it would probably take more time for you to explain it than 
it would for you to do it yourself.

jacob@gap:~/kicad_sources/kicad.bzr$ cat debian/changelog
PACKAGE (VERSION) UNRELEASED; urgency=low


 -- Jacob Schmidt <jacob@gap>  Fri, 23 May 2014 03:14:32 -0400
jacob@gap:~/kicad_sources/kicad.bzr$ ./bzr-dch 4870
parsechangelog/debian: warning:     debian/changelog(l4): found trailer 
where expected start of change data
LINE:  -- Jacob Schmidt <jacob@gap>  Fri, 23 May 2014 03:14:32 -0400
jacob@gap:~/kicad_sources/kicad.bzr$ cat debian/changelog
PACKAGE (VERSION) UNRELEASED; urgency=low

  * 4874: Maciej Suminski 2014-05-20 Fixes the bug that causes pcbnew
    crash, when there are multiple net classes and the plot dialog was
    opened.
  * 4873: Dick Hollenbeck 2014-05-19 fix compiler warnings
  * 4872: jean-pierre charras 2014-05-19 Pcbnew: plot dialog: remove
    obscure and useless option about texts which are not value or
    reference.
  * 4871: Wayne Stambaugh 2014-05-18 Add road map to developer's
    documentation.
  * 4870: Maciej Sumiński 2014-05-18 [merge] Upstream merge.

 -- Jacob Schmidt <jacob@gap>  Fri, 23 May 2014 03:14:57 -0400


jacob@gap:~/kicad_sources/kicad.bzr$ cat bzr-dch
#!/bin/bash

bzr log -r$1.. --line |

while read commit; do
    dch -a $commit
done
jacob@gap:~/kicad_sources/kicad.bzr$



On 05/21/2014 04:37 PM, Adam Wolf wrote:
> bzr-builddeb has severe limitations.  It is what the I used on the 
> previous version of the PPA was built upon, and it literally only 
> added "Autobuild changes" to the dch log.
>
> If this some sort of branch that never got merged in, is there any way 
> to *just* use the dch portion of it?  Is there a reason why it didn't 
> get branched in?
>
> It may be that the answer is to pull most of his code in and write a 
> front end that doesn't do the rest of the builddeb part.  I'm not 
> sure.  I would guess that this entire project would only be an hour or 
> two with Python or bash if written from scratch.
>
> Adam Wolf
> Wayne and Layne, LLC
>
>
> On Wed, May 21, 2014 at 10:40 AM, tiger12506 <tiger12506@xxxxxxxxx 
> <mailto:tiger12506@xxxxxxxxx>> wrote:
>
>
>     On 5/21/2014 9:37 AM, Adam Wolf wrote:
>
>         Hi folks,
>
>         People keep asking about how to help with packaging.
>
>         One of the remaining tasks for the Debian and Ubuntu PPAs for
>         KiCad that needs to be done is a tool that will update the
>         debian changelog file based on the bzr commit log.
>
>         These tools exist for svn and git, but the bzr one just adds
>
>          * Changes
>
>
>     "the bzr one" -- do you have a link? I'm not familiar with the deb
>     making tools, so if that is a stupid question, please say so.
>
>     Sorry if you've already found this, but is there a reason this
>     wouldn't work?
>
>     https://code.launchpad.net/~evgeni/bzr-builddeb/dch
>     <https://code.launchpad.net/%7Eevgeni/bzr-builddeb/dch>
>
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     <https://launchpad.net/%7Ekicad-developers>
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     <https://launchpad.net/%7Ekicad-developers>
>     More help   : https://help.launchpad.net/ListHelp

#!/bin/bash

bzr log -r$1.. --line | 

while read commit; do
    dch -a $commit
done