[Pkg-giraffe-discuss] z-push packages ready for uploading to NEW?

[Roel van Meer]

Carsten Schoenert writes:

> I think we can go into possible final needed small modifications to
> prepare the z-push packages for a upload to NEW.

Great!


> > root at x260:/build/z-push-2.3.7# lintian -IE
> > warning: the authors of lintian do not recommend running it with root  
> privileges!
> > W: z-push source: newer-standards-version 4.0.1 (current is 4.0.0)
> > I: z-push source: testsuite-autopkgtest-missing
> > N: 3 tags overridden (2 warnings, 1 info)
>
> The (new?) remaining warning comes from a not complete up2date lintian
> which probably currently doesn't know about the released policy version
> 4.0.1.
> But the ftp-masters of course know about the new release.
> So could you please check (again) if any points are left while going
> though the list of changes?
>
> https://www.debian.org/doc/debian-policy/upgrading-checklist.html#s-4.0.1

Yes, the update would require some small changes. I'll commit those.


> You could also use the following checklist for z-push.
>
> https://wiki.debian.org/LucaFalavigna/NEWChecklist
>
> We also have three overridden tags and two of them are warnings which
> typically the ftp-masters will look into.
>
> > root at x260:/build/z-push-2.3.7# lintian -o --suppress-tags newer-standards- 
> version
> > warning: the authors of lintian do not recommend running it with root  
> privileges!
> > W: z-push-common: non-standard-apache2-configuration-name z-push- 
> autodiscover.conf != z-push-common.conf
> > W: z-push-common: non-standard-apache2-configuration-name z-push.conf != z- 
> push-common.con

> This two overridden warnings could be explained why the override was done.
> I"d write some explanation into README.Debian, z-push-common comes with
> two needed webserver config files for Apache2 and by this the suggestion
> by the lintian warning can't be used. I also would point in
> z-pus-common.install and *.lintian-overrides to the created section in
> README.Debian then.

Well, we could of course rename the z-push file to z-push-common. That would  
avoid one of the warnings (but it might make it harder to switch from the  
"offical" Z-push packages to the Debian z-push packages).
I'd rather have an extra lintian warning than stuff breaking whenever you  
switch, so I'll document both of them. 


> The file README.source is definitely out of date and needs some actual
> data. Please prepare some information as content, e.g we use
> git-buildpackage for maintenance.
> Policy 4.14 will guide you what's expected here.
>
> https://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource

Okay, can do.


> Roel, and one more really important point, Guido and me too are don't
> familiar with z-push in deep.
> We happily will sponsor a upload but if any bug report or user questions
> will appear it mostly will need a person that has enough knowledge (and
> time!) to answer such questions or act on bug solving! Are you aware
> that this person will and can be currently you?

Well, although I do know my way around a PHP project, I'm not intimitely  
familiar with Z-push's internals either. If users have problems or questions  
pertaining to specific use-cases, I will have to rely on the Z-push devs.
So if bugs are specific to Debian or related to packaging, I can fix them,  
but if they are unrelated to either (e.g. they are issues with Z-push itself)
I will have to forward them to the Z-push bug tracker, most likely.
 
Releasing new packages and backporting of bugfixes is not a problem of course.

So, that's the level of commitment I can offer. If the Z-push devs are  
committed to fixing actual Z-push bugs reported by Debian users in the  
Debian bugtracker, I think we have all bases covered. But I cannot speak for  
them, of course..


> If you are not feeling able to do this we should not upload z-push to
> Debian. For the technically packaging Guido and myself will of course
> stay on your side and we'd be happy if you step in as a package
> maintainer and so far I can see you are really qualified from the point
> of knowing the source for this!

Well, thanks! You've been a great help in getting things done properly.

With that, I have one last question. Where do I push new work? In my own  
github repo? In yours? Or do we work directly on the Alioth z-push repo now?

Thanks,

Roel