-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Brian Hall wrote:
|On Wed, Mar 23, 2005 at 04:01:15PM +0000, Simon Stelling wrote: | |>Hi Brian, |> |>Brian Hall wrote: |> |>>I often submit bug reports to indicate that a package works |>>~amd64; what is the procedure (or is there one) for indicating |>>that the next version of a package of an existing ~amd64 |>>package works (version bump) ? |> |>Normally, when a package is bumped, all existing arches change to ~arch, |>but it shouldn't get lost, so it would be necessary to notify us. When |>the keyword gets lost and there's nothing in ChangeLog and/or bugs.g.o, |>however, you could ask the maintainer why he took the keyword out. |> |>Greetings, |> |>blubb | | |OK. So, for example, I noticed that fluxconf had an available 0.9.8 |version, but portage only went up to 0.9.7. So, I copied/renamed the |ebuild file so I could easily emerge the new version (I'm a freshmeat |addict, can't help it). | |So in these cases, I shouldn't do any sort of bug report or anything, |just wait for the maintainer to update?
You should normally give the maintainer a while to update the ebuild, but if he doesn't then you can report a version bump bug, including the category and name of the application and that it worked by renaming the existing ebuild. If you have to modify the ebuild then you should provide a diff attached to the bug to the last ebuild.
Maintainers usually keep on top of new releases, but they can sometimes be busy, or don't notice for some reason and then they usually appreciate a polite prod ;) Although opening a bug the day after release is a little excessive - I think a week is a reasonable time to wait normally. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCQYsbzgRsaX1BF70RAsMsAJ9DCWqZrIXI2m4MdKpSaXWLNjB9JACfaNDy Jr6KFjB8ytwNIVQNRjsxt+Y= =yP/o -----END PGP SIGNATURE-----
-- gentoo-amd64@gentoo.org mailing list
