[pkg-go] Various problems with packages in the group

[Martín Ferrari]

On 14/09/15 13:07, Dmitry Smirnov wrote:

> However most of Perl packages are superior to Golang packages. The latter 
> bundle build-dependencies very often while Perl packages rarely need to 
> undergo DFSG-repackaging. Almost all Perl packages (I can't recall even a 
> single exception) have formal version, probably because CPAN require modules 
> to be versioned. Packaging Perl software is usually easier and takes less 
> maintenance effort.
> 
> Golang software exhibit bad practices all over as far as I can tell...
> Unfortunately this have implications to our workflows because of frequent 
> version mocking and DFSG cleanup.

That's true. CPAN upstreams are the best! Still, go packaging is not as
bad as -say- java or the likes. Basically the biggest hurdle is
repackaging, and that does not need to affect our workflow much (see my
other mail).

> I've already experienced permissions problem twice and I wonder if we can ask 
> admins (whom specifically?) to fix this problem for all repositories...

I asked in #alioth, but got no answer so far. In the meantime I worked
around the issue by copying the repos with my UID, and fixing
permissions. The old repos are still there, with a '_perm_problems'
suffix, until they can be removed.

>> S: Always use debcommit -r, which will create the tag automatically,
>> when the package is about to be uploaded.
> 
> What do you suggest to do with tag if package is rejected?

If you reupload, just force push a new tag. Otherwise, remove the tag.

> I've made it a personal policy to tag only once package is accepted...

It is not a big issue, but it means it is more difficult to track
packages that need to be sponsored. There are a few non-DDs in the team,
and I would like to make it easier for them to work on packages, and for
DDs to sponsor them.

-- 
Martín Ferrari (Tincho)