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

Re: Request for sponsoring upload of probabel-0.4.4



Hi Andreas,

Thanks for having a look at my request.

On 10-11-14 14:45, Andreas Tille wrote:
> Hi Lennart,
> 
> could you please commit the pristine-tar branch as per Debian Med policy?

Done. My apologies for forgetting that, I'm still struggling a bit with
git. I did the following:
 git checkout pristine-tar

Since it turned out that there were merge conflicts when I did a regular
'git pull' I ran:
 git pull -X theirs
 git push

Is this (checkout, pull, push) the correct way to do it? Or should I
have run `gbp-pull` to get all branches in and then run `git push --all
--tags` to push everything?

In fact, when I run `git push --tags` I get the following error:

To git+ssh://git.debian.org/git/debian-med/probabel.git
 ! [rejected]        upstream/0.4.2 -> upstream/0.4.2 (already exists)
error: failed to push some refs to
'git+ssh://git.debian.org/git/debian-med/probabel.git'
hint: Updates were rejected because the tag already exists in the remote.

Is there a way to sync the tags (or to let my copy accept the one on
git.debian.org?


> 
> Please also note that the upload will be happen to experimental instead
> of unstable since we are in Freeze (feel free to ask if you do not
> understand this).

I've read about the Freeze (and unfortunately couldn't get the fix done
in time). Since v0.4.4 fixes an important bug (which rendered one third
of the package useless) I was wondering about how to get a freeze
exception. Reading https://release.debian.org/jessie/freeze_policy.html
it seems to me that bug fix like this can be considered under:

ii. fixes for severity: important bugs in packages of priority: optional
or extra, only when this can be done via unstable (until the 5th of
December 2014);

However, when I read the section 'How to get an unblock' I'm wondering
if this applies to bugs in the software or bugs in the packaging (i.e.
where it says: "Only make changes that are necessary to fix the bug".

Any suggestions as to how to move forward (if this is possible at all)?

Thanks a lot,

Lennart.

> 
> Kind regards
> 
>         Andreas.
> 
> On Mon, Nov 10, 2014 at 10:09:12AM +0100, L.C. Karssen wrote:
>> Dear list,
>>
>> I've packaged the latest version of ProbABEL (see the git repo [1]),
>> which is a bugfix release. On the Debian side of things I've also fixed
>> the 'compiler flags hidden' warning [2].
>>
>> Could one of you please upload it?
>>
>>
>> Thanks,
>>
>> Lennart.
>>
>> [1] git://anonscm.debian.org/debian-med/probabel.git
>> [2] http://qa.debian.org/bls/packages/p/probabel.html
>> -- 
>> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>> L.C. Karssen
>> Utrecht
>> The Netherlands
>>
>> lennart@karssen.org
>> http://blog.karssen.org
>> GPG key ID: A88F554A
>> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>>
> 
> 
> 

-- 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
L.C. Karssen
Utrecht
The Netherlands

lennart@karssen.org
http://blog.karssen.org
GPG key ID: A88F554A
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: