Re: RFS: oggfix
Hi, Gunter Königsmann writes: > Did try to change the version number to 0.9.1-1 - which sounded great > for a non-native debian package. But this meant running into all kinds > of warnings. (debuild claims my native package has a version number > that contains a dash!) You probably forgot to provide a oggfix_0.9.1.orig.tar.*. The old source format will happily create a native package if it is missing, with 3.0 (quilt) you would get an error instead. Regards, Ansgar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874nxet5wb@deep-thought.43-1.org
Re: RFS: oggfix
On 27.06.2011 11:31, Michael Tautschnig wrote: Hi, [...] Ok, I wouldn't bother much about the above, but one thing does stop me from uploading: why are you setting the version number in such a way that Debian is upstream? This doesn't seem to be accurate. IMHO you should be using 0.9.1-1 as version number!? Never found out what the version number ought to be. 0.9.1-1 sounds exactly right. Thanks for that, too! This is explained in full detail in the Debian Policy [1]. Hope this helps, Michael [1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version Did try to change the version number to 0.9.1-1 - which sounded great for a non-native debian package. But this meant running into all kinds of warnings. (debuild claims my native package has a version number that contains a dash!) As far as I understand the Debian Policy states that if a package is deemed to be "native" depends on the version number. But it seems like there has to be another criterion, too. Do you know what this criterion would be? I did try to read the Policy and experimented for a long time before another urgent project started keeping me constantly busy for months - so this time I have to say sorry for the delay. In the meantime parts of the Debian Policy has changed and I have altered the package again as to no more get lintian or other warnings except that I have the wrong version number. As soon as the version number is fixed I can upload the package again with the new standards version and all. Thanks a lot, and kind regards, Gunter. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eddc9d1.4060...@peterpall.de
Re: RFS: oggfix
Hi, [...] > > > > Ok, I wouldn't bother much about the above, but one thing does stop me from > > uploading: why are you setting the version number in such a way that Debian > > is > > upstream? This doesn't seem to be accurate. IMHO you should be using 0.9.1-1 > > as > > version number!? > >Never found out what the version number ought to be. > 0.9.1-1 sounds exactly right. Thanks for that, too! > This is explained in full detail in the Debian Policy [1]. Hope this helps, Michael [1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version pgpjqeXLda4PY.pgp Description: PGP signature
Re: RFS: oggfix
Hi,> > Hmm, mind re-reading it? There's also this bit with > > > Copyright (C) > > in there... :-) >Will do that as soon as my ecryptfs is working again - that currently won't let >me access my home directory. > > --- > > > > Uploaded the new version of the file to mentors.debian.net. > > > > Ok, I wouldn't bother much about the above, but one thing does stop me from > uploading: why are you setting the version number in such a way that Debian is > upstream? This doesn't seem to be accurate. IMHO you should be using 0.9.1-1 > as > version number!? >Never found out what the version number ought to be. 0.9.1-1 sounds exactly right. Thanks for that, too! Gunter.
Re: RFS: oggfix
Hi, I'm sorry for the huge wait... > > As you claim it is GPL, you should familiarize yourself with its use: > > > > http://www.gnu.org/licenses/gpl-howto.html > > > > Well, at least you should have fully read the license text. The last > > section is > > titled "How to Apply These Terms to Your New Programs." Please re-read that > > part. > > > Cool! Did actually never do that. > Hmm, mind re-reading it? There's also this bit with Copyright (C) in there... :-) > --- > > Uploaded the new version of the file to mentors.debian.net. > Ok, I wouldn't bother much about the above, but one thing does stop me from uploading: why are you setting the version number in such a way that Debian is upstream? This doesn't seem to be accurate. IMHO you should be using 0.9.1-1 as version number!? Thanks a lot, Michael pgpka9XCteVHj.pgp Description: PGP signature
Re: RFS: oggfix
> As you claim it is GPL, you should familiarize yourself with its use: > > http://www.gnu.org/licenses/gpl-howto.html > > Well, at least you should have fully read the license text. The last section > is > titled "How to Apply These Terms to Your New Programs." Please re-read that > part. > Cool! Did actually never do that. --- Uploaded the new version of the file to mentors.debian.net. Thanks a lot, and kind regards, Gunter Königsmann. signature.asc Description: This is a digitally signed message part
Re: RFS: oggfix
On Monday 09 May 2011 09:27:49 Gunter Königsmann wrote: > > - No copyright and license information in source files. > > Is there any fixed or recommended format for doing this? You should contact upstream and ask them to clarify copyright and license. Ideally, this info should be somewhere in upstream source. But a mail from the author can be enough to clarify. Once you have this updated info, you can update debian/copyright file. Hope this helps Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105101152.26372.d...@komarr.gre.hp.com
Re: RFS: oggfix
Hi again, [...] > > - No copyright and license information in source files. > Is there any fixed or recommended format for doing this? [...] > > - It sounds weird that gnome-common is needed to build a command-line > > utility > > for ogg files!? > Will fix that before re-uploading the file: The only thing I did use > from this package was the autogen.sh from gnome. > > > > Please address these issues and re-upload. > > > Will upload the package as soon as you tell me which format the > copyright information in the source files has to be in. > As you claim it is GPL, you should familiarize yourself with its use: http://www.gnu.org/licenses/gpl-howto.html Well, at least you should have fully read the license text. The last section is titled "How to Apply These Terms to Your New Programs." Please re-read that part. Best regards, Michael pgpSNAqS8rTRq.pgp Description: PGP signature
Re: RFS: oggfix
On So, 2011-05-01 at 18:09 +0100, Michael Tautschnig wrote:
> Hi,
>
> > I am looking for a sponsor for my package "oggfix".
> >
> > * Package name: oggfix
> > Version : 0.9.0
> > Upstream Author : Gunter Königsmann
> > * URL : http://launchpad.net/oggfix
> > * License : GPL V3+
> > Section : sound
> >
> > It builds these binary packages:
> > oggfix - Command-line-utility that fixes broken ogg vorbis files
> >
> > The package appears to be lintian clean.
> ^
>
> No, that can't be true.
>
> - Depends lacks ${shlibs:Depends}
Fixed that on my computer.
> - No copyright and license information in source files.
Is there any fixed or recommended format for doing this?
> - debian/copyright should be DEP-5 formatted (see
> http://dep.debian.net/deps/dep5/)
Fixed that on my computer.
> - Build-Depends should not include build-essential packages.
Fixed that on my computer.
> - It sounds weird that gnome-common is needed to build a command-line utility
> for ogg files!?
Will fix that before re-uploading the file: The only thing I did use
from this package was the autogen.sh from gnome.
>
> Please address these issues and re-upload.
>
Will upload the package as soon as you tell me which format the
copyright information in the source files has to be in.
Kind regards,
Gunter.
signature.asc
Description: This is a digitally signed message part
Re: RFS: oggfix
Hi,
> I am looking for a sponsor for my package "oggfix".
>
> * Package name: oggfix
> Version : 0.9.0
> Upstream Author : Gunter Königsmann
> * URL : http://launchpad.net/oggfix
> * License : GPL V3+
> Section : sound
>
> It builds these binary packages:
> oggfix - Command-line-utility that fixes broken ogg vorbis files
>
> The package appears to be lintian clean.
^
No, that can't be true.
- Depends lacks ${shlibs:Depends}
- No copyright and license information in source files.
- debian/copyright should be DEP-5 formatted (see
http://dep.debian.net/deps/dep5/)
- Build-Depends should not include build-essential packages.
- It sounds weird that gnome-common is needed to build a command-line utility
for ogg files!?
Please address these issues and re-upload.
Thanks a lot,
Michael
pgp6uudKt1aiW.pgp
Description: PGP signature
RFS: oggfix
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package "oggfix". * Package name: oggfix Version : 0.9.0 Upstream Author : Gunter Königsmann * URL : http://launchpad.net/oggfix * License : GPL V3+ Section : sound It builds these binary packages: oggfix - Command-line-utility that fixes broken ogg vorbis files The package appears to be lintian clean. My motivation for maintaining this package is: Problems with broken ogg files nobody seemed to offer a solution for. The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/o/oggfix - - Source repository: deb-src http://mentors.debian.net/debian unstable contrib - - dget http://mentors.debian.net/debian/pool/main/o/oggfix/oggfix_0.9.0.dsc I would be glad if someone uploaded this package for me. Kind regards Gunter Königsmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJNYDBGAAoJEFyGwOQhHVuOeaoP/2Msrsbcq+fhuAx8ZZDDowK+ 4Vif9aD36jYGUsBzENeH67kMSQ2y+m1omJd+vmHJaQ+EBm8GJ7H0MkBSJCqbr4Cl e16+w/wtg188lyETe9jWgpkDWy4wnZfwnFYpWts2AYvwipK+OmHaljtabhPUpQy3 sqqF+7oliTEveYxB5d74gz9OntB3uYhAgz3u9LUeizJiQVVdZs+sgEuhQrX2ty3E is99Bt1PbHVDdBZrEdHaKBng7Fi+SFlA1ZHxFZm0PC23y0omfkCOeczexNmcWs9z GtfXHsXDXTnZEALvvtnJ20MveaBOxFz/D1CJBGydJlomnpkgaMxSVYsPQr4NfiHx r4O/uAjdxV0Gs6xOEjdIlKd0+JB/vNsr2p5OHb93SMkf9xYu/2e2G2PRR+byyWuf aCakkCJsF5ZdleLVx422TIuHbDHuEieWlXLgEH0NPCUuL7whI/8R3E/ib3Djr5Uh 6GOblzGKWzudrOh7iR6hH4n44Armz+k8IL4qLz9j5Kv2Ok3uxtu1yEHwdDkm7K+a fh7AN0pB83E6ufhWSvo+6ns3nFW52Qns1fSmew1lj3cO/LR2DBNKOWdKteTN0yvX sAFQ4T//BIbzYPrGAEq8nhafC4mPcKCwNH3YbnCY4HBkTjMh0xfENAzG8H25G9/C Et5p0l4z5nlOVqNbdAng =vVYG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d60304a.3030...@peterpall.de
