Bug#777500: RFS: birdie/1.1-1 [ITP]
Am Samstag, den 28.02.2015, 14:11 +0100 schrieb Kay Abendroth:
> Hello,
>
> these are my questions regarding your feedback. Question 1 to 4 refer to
> http://mentors.debian.net/package/birdie.
>
> 1. Warning "Package uploaded for the unreleased distribution":
>
> How do I fix that? Right now I'm using Jessie on my laptop already.
> Can I tell the build tool to build it for Wheezy?
no, packages are always built for sid (unstable).
So you always* write unstable as target in your changelog.
* except some special case which I wo not want to elaborate now to avoid
confusting you; most noteworthy is "experimental". See the Policy and
the Developers Reference for details.
You can build for sid using pbuilder or pull yourself a sid chroot
(using debootstrap), without interfering your installation.
(You *should* at least once build with pbuilder, as pbuilder catches
missing dependencies better)
>
> 2. Lintian warning "no-upstream-changelog":
>
> Upstream version 1.1 doesn't provide a Changelog. Can I overwrite
> this warning?
That's only a pedantic message, no warning ;-)
Therefore just ignore it.
> 3. Warning ""Maintainer" email is the same as the uploader":
>
> Why is this a warning? How do I fix it?
It's no warning. (its "green" on the mentors interface)
> 4. Warning "Package is not native":
>
> What does that mean and how do I fix it?
It's no warning. (its "green" on the mentors interface)
Non-native package is usually that what you want.
For more details:
https://wiki.debian.org/DebianMentorsFaq#What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F
> 5. Your comment "the files in the dir cmake are not documented":
>
> I guess you mean the files from upstream. There is no more
> documentation provided by upstream. I use the package "as is."
I meant copyright documentation (in d/copyright), if I recall correctly.
> 6. Your comment "did not try: are the icons regnerated at build time?
> There is also an oddity: icons/128x128/apps has the svg in it, also
> other dirs have the svg":
>
> I didn't understand what you mean. How do I check the "regeneration"?
> What do you mean with the icon-oddity?
In Debian, everything must be built from source. Also the icons. They
need to be created at built time (e.g from the svg)
The oddity I found is that there are svg files in the directory 128x128,
where usually a image (e.g png) with the size of 128x128 px is expected.
>
> 7. Regarding the VCS-field:
>
> I'd gladly maintain the package via Git for example. Is there a naming
> convention for the repository I can follow? I could imagine naming it
> 'debian-package-birdie'.
Names are not so important, you can choose this or birdie-debian.
The best place would be alioth.debian.org (and put it under collab-maint
[1] ), but you need to apply for an account; there you would name it
birdie. Therefore, I suggest to start e.g. at github with
debian-package-birdie (or birdie-debian) or like and later move it to
collab-maint)
I recommend using the tool git-buildpackage [2] and [3] has more on the
topic. Please use pristine-tar.
[1] https://wiki.debian.org/Teams/CollabMaint
[2] https://wiki.debian.org/PackagingWithGit
[3]
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
> Regards,
> Kay
>
>
--
tobi
Reply to: