[Debian-med-packaging] Bug#777791: [PATCH] ball: ftbfs with GCC-5

[Andreas Tille]

Hi Danny,

On Mon, Apr 11, 2016 at 08:03:19PM +0200, Danny Edel wrote:
> > git://anonscm.debian.org/debian-med/ball.git
> 
> sorry for the miswording -- I did use the git repository at the
> specified location, not collab-maint.  If the patch didn't apply cleanly
> I can't say why.

> > since I tried to
> > 
> > git am 0001-Rework-patches-for-sid.patch
> > 
> > which resulted in several conflicts.  I wonder whether you could 
> > rather commit to the official packaging repository.  To enable you 
> > doing this I've added you to the Debian Med team.
> 
> Thanks!  I will submit there as soon as the group membership is through.
>  I can already see that I'm added in the alioth webinterface, but
> "groups" on git.debian.org doesn't yet include scm_debian-med.
> 
> Trying to push anyway gives:
> 
> danny at debwork ~/git/debian-med/ball $ git push -v
> Pushing to git.debian.org:/git/debian-med/ball.git
> Counting objects: 13, done.
> Delta compression using up to 2 threads.
> Compressing objects: 100% (13/13), done.
> Writing objects: 100% (13/13), 6.09 KiB | 0 bytes/s, done.
> Total 13 (delta 4), reused 0 (delta 0)
> 
> remote: error: insufficient permission for adding an object to
> repository database ./objects
> 
> remote: fatal: failed to write object
> 
> error: unpack failed: unpack-objects abnormal exit
> 
> To git.debian.org:/git/debian-med/ball.git
>  = [up to date]      pristine-tar -> pristine-tar
>  = [up to date]      upstream -> upstream
>  ! [remote rejected] master -> master (unpacker error)
> updating local tracking ref 'refs/remotes/origin/pristine-tar'
> updating local tracking ref 'refs/remotes/origin/upstream'
> error: failed to push some refs to 'git.debian.org:/git/debian-med/ball.git'
> 
> I will try to push again later tonight or tomorrow.  I'm sure this is
> just an issue about the group membership update script not run yet.

Sounds convincing.

Thanks a lot for your patience

       Andreas.

PS: The private CC I used bounced.  May be you check the logs of your
mailserver. 



-- 
http://fam-tille.de