Assuming I have patched a package in universe to fix a bug, and have
also created a package for the bugfix, where is the best place to put
it to get someone to check and upload it?
REVU?
sponsors-queue?
Assuming you just want the .diff.gz, would you want to see the source
directly patched, or would you prefer to use quilt or dpatch or the
like?
Regards
Jeff
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
02-07-2008, 09:15 AM
Luca Falavigna
Patches
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Jeffrey,
Jeffrey Ratcliffe ha scritto:
> Assuming I have patched a package in universe to fix a bug, and have
> also created a package for the bugfix, where is the best place to put
> it to get someone to check and upload it?
>
> REVU?
> sponsors-queue?
Is your package a new upstream revision? If so, you should publish new
.diff.gz file for review, otherwise a debdiff between current Ubuntu
version and yours is fine.
> Assuming you just want the .diff.gz, would you want to see the source
> directly patched, or would you prefer to use quilt or dpatch or the
> like?
If changes you introduce touch files provided upstream, adopting a patch
system is advisable, no need of it if changes are limited to debian/
directory.
Regards,
- --
Luca Falavigna
Ubuntu MOTU Developer
GPG Key: 0x86BC2A50
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
02-07-2008, 09:29 AM
"Jeffrey Ratcliffe"
Patches
On 07/02/2008, Luca Falavigna <dktrkranz@ubuntu.com> wrote:
> Is your package a new upstream revision? If so, you should publish new
> .diff.gz file for review, otherwise a debdiff between current Ubuntu
> version and yours is fine.
For my information - for both cases:
1. in case of a new upstream version, where do I post the diff.gz?
2. otherwise, where do I post the debdiff?
Thanks!
Jeff
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
02-07-2008, 09:32 AM
Stefan Potyra
Patches
Hi,
Am Donnerstag, 7. Februar 2008 11:15 schrieb Luca Falavigna:
[..]
>
> If changes you introduce touch files provided upstream, adopting a patch
> system is advisable, no need of it if changes are limited to debian/
> directory.
Just for clarification: If the package you touch comes from debian, and there
is no patch system present in the debian version, please don't start to
introduce one. This will make future merges more easy (valid in both
directions).
Cheers,
Stefan.
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
02-07-2008, 09:34 AM
Luca Falavigna
Patches
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeffrey Ratcliffe ha scritto:
> For my information - for both cases:
> 1. in case of a new upstream version, where do I post the diff.gz?
> 2. otherwise, where do I post the debdiff?
You can file a new bug in Launchpad [1] or attach diff.gz/debdiff to
existing bug reports [2], if your patch fixes some of them.
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
02-07-2008, 10:41 AM
"Jeffrey Ratcliffe"
Patches
On 07/02/2008, Stefan Potyra <stefan.potyra@informatik.uni-erlangen.de> wrote:
> Just for clarification: If the package you touch comes from debian, and there
> is no patch system present in the debian version, please don't start to
> introduce one. This will make future merges more easy (valid in both
> directions).
So in this case, I should patch the upstream source directly?
Regards
Jeff
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
02-07-2008, 10:47 AM
Stefan Potyra
Patches
Hi,
Am Donnerstag, 7. Februar 2008 12:41 schrieb Jeffrey Ratcliffe:
> On 07/02/2008, Stefan Potyra <stefan.potyra@informatik.uni-erlangen.de>
wrote:
> > Just for clarification: If the package you touch comes from debian, and
> > there is no patch system present in the debian version, please don't
> > start to introduce one. This will make future merges more easy (valid in
> > both directions).
>
> So in this case, I should patch the upstream source directly?
If the package has a patch system already, please don't directly patch the
source, but use the patch system instead.
If not, please patch the source directly.
Cheers,
Stefan.
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
02-07-2008, 11:04 AM
"Jeffrey Ratcliffe"
Patches
On 07/02/2008, Luca Falavigna <dktrkranz@ubuntu.com> wrote:
> You can file a new bug in Launchpad [1] or attach diff.gz/debdiff to
> existing bug reports [2], if your patch fixes some of them.
>
> [1] https://launchpad.net/ubuntu/+source/packagename/+filebug
> [2] https://launchpad.net/ubuntu/+source/packagename/+bugs
Thanks!
Jeff
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
06-25-2010, 12:00 AM
David Cantrell
patches
1) Make sure dhclient*conf goes to /etc/dhcp
2) Reduce the rd_DASD parameter to exclude default values.
--
David Cantrell <dcantrell@redhat.com>
Red Hat / Honolulu, HI
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
06-25-2010, 06:22 AM
Hans de Goede
patches
Ack fro both patches.
On 06/25/2010 02:00 AM, David Cantrell wrote:
1) Make sure dhclient*conf goes to /etc/dhcp
2) Reduce the rd_DASD parameter to exclude default values.
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
Patches
