On Wednesday, 27. February 2008 20:15:55 Pascal Bleser wrote:

Personally, I think Bugzilla is the best place to report it. The problem is finding the relation package->packager, to know whom to assign the request.

Just file it, BNC team will care about assigning it to the package maintainer. Bye, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

On Thu, 28 Feb 2008 18:15:58 +0100, Bernhard Walle wrote:

Which is a waste of time IMO.

Seconded.

If we already _know_ the package, then there should be a field "package" n Bugzilla where the assignment gets done automatically.

Sigh, the good old SuSE times when Klaas AFAIR hacked Bugzilla and misused the keywords feature to give us exactly that: you entered the package name and it automatically looked up the maintainer and assigned the bug to her/him. Being the default assignee for the development component I sure would rejoice having that feature back :) Philipp --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

2008/2/27, Dirk Mueller :
> On Wednesday 27 February 2008, Christian Morales Vega wrote:
>
>  > If the packager doesn't knows about the new version he can leave the
>  > package outdated for a long time. So would be good that, at some time,
>  > if an user finds the problem he reports it. But, how should be
>  > reported? There is any feature planned in the OBS to help with this?
>
>
> I think the proposed way should be:
>
>  a) fork the package and update the version
>  b) the OBS should make it obvious for maintainers of a package that their
>  package got forked and notice it then and merge back the change.
Not a bad solution
- Even if the packager is busy users have a "backup" copy updated meanwhile.
- You are giving the needed corrections, not just complaining.
but don't call it "fork", people doesn't likes forks ;-) Shouldn't
just "links" be expanded to allow more changes than they allow right
now?

And, is a feature that "makes it obvious for maintainers of a package
that their package got forked" already planned? (I have no idea about
the OBS roadmap) If no, it could take some time, what should be done
meanwhile?

Anyway the users of the Build Service will be always a subset of the
users that report bugs. There is also the need of a solution for
"normal" users.

>
>  Other than that, I guess a bugzilla entry is the most obvious solution. but we
>  do create the buildservice to make it possible for people to participate
>  actively :)
>
>
>  --
>  RPMLINT information under http://en.opensuse.org/Packaging/RpmLint
>
> ---------------------------------------------------------------------
>  To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org
>  For additional commands, e-mail: opensuse-project+help@opensuse.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-project+help@opensuse.org

Le mercredi 27 février 2008 à 15:51 -0500, JP Rosevear a écrit :

On Wed, 2008-02-27 at 19:46 +0100, Christian Morales Vega wrote:

...

If the packager doesn't knows about the new version he can leave the package outdated for a long time. So would be good that, at some time, if an user finds the problem he reports it. But, how should be reported? There is any feature planned in the OBS to help with this?

For specifically learning about the new version, Marcus Meissner has some code that crawls for version updates, maybe we could turn that into a system on opensuse.org that you can subscribe to somehow for notifications.

FWIW, at the GNOME level, we were asked by Debian and Gentoo packagers to provide a single file containing the latest versions for all stable/unstable modules. This would make life easier for them since they wouldn't have to crawl the FTP many times. Also, it'd be possible to push the information to openSUSE when we upload a new tarball on the GNOME FTP. I guess other big projects could do the same (one file for all tarballs, and pushing the information). If there's interest for this, I can put people in contact with the relevant GNOME people... Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Le jeudi 28 février 2008 à 10:51 +0100, Marcus Meissner a écrit :

On Wed, Feb 27, 2008 at 10:01:52PM +0100, Vincent Untz wrote:

...

FWIW, at the GNOME level, we were asked by Debian and Gentoo packagers to provide a single file containing the latest versions for all stable/unstable modules. This would make life easier for them since they wouldn't have to crawl the FTP many times.

Also, it'd be possible to push the information to openSUSE when we upload a new tarball on the GNOME FTP.

My scripts read the GNOME RSS feed. Wonder why you do not put it there.

Well, an RSS feed is still the pull model on the openSUSE side. But it works, yes :-) We might want to have a feed with more items, though (you can miss some tarballs on release days if many maintainers upload at the same time). It seems some of the packagers in other distros also like to have the complete current state, and not just updates, that's why such a file would be useful for them. (still the pull model, and not push model, though) Anyway, if you need improvements on the GNOME side for this, I can help with that. Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org