Bug#779377: RFS: classified-ads/0.03-1 / ITP
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tobias Frost writes:
> Control: owner -1 !
> Control: tags -1 pending
Aye, best aprils fool's prank for some time :)
> Debian sees the (high-res image) as part of the source code, the
> preferred form of the source actually. So you should include it into
> your tarball and create the actual bitmaps at build-time.
Hmm, I could do something like introducing a build-time dependency to
imagemagick (I think I crafted the lower-resolution bitmaps with gimp by
hand) and try to do the format+size conversion tricks with that?
Isn't imagemagick a bit huge and unconventional build-dependency?
> Sure, just follow the ITa procedure. (I will also sponsor you on this)
...
> Its just a git repository ;-) No big risk to ruin everything.
> You could also move the repository somewhere else, if you don't like
> collab-maint.
Yes, this was actually my question ; is it ok for me to fork the
collab-maint repo of qemuctl to some other place (say, github) and
make the changelog-change from there and reference that in ITA-ticket?
Or is getting write permission to repository in collab-maint a
difficult process? Anything goes, my primary interface is anyway git
and the address of remote repository is not much an issue..
> For the upload procedure:
> In short-term, yes: You need a sponsor for upload.
> Mid-Terms: You can become a Debian Maintainer with upload rights
> for your packages (https://wiki.debian.org/DebianMaintainer)
> Long-Term: You join the project as Debian Developer
Ok, I've read through https://wiki.debian.org/DebianMaintainer
and https://wiki.debian.org/DebianMaintainer/Tutorial and feel ok with
privileges and responsibilities regarding becoming a maintainer. This
anyway looks like the way of least hassle for keeping my packages
up-to-date.
I'll write about this to debian-devel-announce.
But here I need advice as https://wiki.debian.org/DebianMaintainer
says I'll need a PGP-key with at least 2k key length.
The key I used at https://mentors.debian.net/my was my pgp key that I
normally use. I don't consider it compromised, it is from year 2000
and has 1k key len -> do I fullfill the requirement if I add
additional longer encryption key into my current key and replace the
key in mentors ; the key in there still has no signatures from any
party relevant in this debian process..
And it there any (documented? where? )process for .. situation that a
maintainer might face, like
1. notification a new bug report
2. creation of patch
3. ???
4. upload to ftp.upload.debian.org
especially the step three there is interesting..
In long term I can consider trying to become DD too. But lets start
with small amount of packages..
> I saw that debian/source/format is missing in the repository.
Ahem. Not any more.
- --
Antti
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAlUcTCEACgkQUTdja+nNMWNAgQCdGEHMEYi46hA7ugWAUQYxYMKZ
cG8AnR8YeSh6jXiwCig7rlH2NSvZH/q4
=MObn
-----END PGP SIGNATURE-----
Reply to: