Re: [gentoo-dev] Re: [RFC] Improve policy of stabilizations
On 07-11-2009 17:54:25 +0300, Peter Volkov wrote: > > > Sounds like we could benefit from the "noarch" approach known in the RPM > > > world, such that all these packages can also be immediately keyworded > > > and stabilised for all arches. Would greatly simplify things for a > > > great deal of packages, maybe? > > > > We could introduce "noarch" and "~noarch" KEYWORDS, add "noarch" to > > the default ACCEPT_KEYWORDS setting for all profiles, and instruct > > unstable users to add "~noarch" to ACCEPT_KEYWORDS. > > Looks like this will not work for all noarch packages. Stardict > dictionary itself is noarch, but it RDEPENDS on stardict package which > is keyworded only on some archs. So we'll be forced either to keyword > stardict on all archs or we need to introduce some new way to work with > such situations. Would it be reasonable to just mask in such case? Resolution would eventually just hit the masked stardict dictionary and display the reason why it's masked (stardict doesn't compile, not yet looked into keywording: please try, etc.) -- Fabian Groffen Gentoo on a different level
Re: [gentoo-dev] a pragmatic approach to FEATURES [was FEATURES use or misuse?]
[snip] > I understand PMS/paludis wishing to duck the vars existance to make it > go away, but I don't think it's a tenuable approach- as you yourself > said above, in trying to do this cleanup you recognized that sometimes > there was no alternative. yes - however, there not being an alternative at the moment does not automatically mean that FEATURES is a good or the best approach. A more clean approach still needs to be proposed. [snip] > > Rather then letting the problem persist, I'd rather see folk take a > look at FEATURES/PMS and identify what needs to be pushed in to take > care of the cases where there is no alternative to 'hasq some-feature > $FEATURES' rather then us just collectively sticking our heads in the > sand. yes - exactly. so which FEATURES are absolutely required in ebuilds / eclasses for which an alternative must be developed? > thanks for your input, BTW signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [RFC] Improve policy of stabilizations
Nirbheek Chauhan wrote: > On Sun, Nov 8, 2009 at 2:19 AM, Zac Medico wrote: >> Peter Volkov wrote: >>> Looks like this will not work for all noarch packages. Stardict >>> dictionary itself is noarch, but it RDEPENDS on stardict package which >>> is keyworded only on some archs. So we'll be forced either to keyword >>> stardict on all archs or we need to introduce some new way to work with >>> such situations. >> Keywording stardict on all archs doesn't sound reasonable, so I >> guess we just need to make sure that repoman will allow the noarch >> keyword even though the dependencies aren't keyworded on all >> architectures. > > I think we're going a little far trying to solve a management problem > with technology. If a herd thinks that a particular package can be > safely keyworded (or stabilized) other arches (it just dumps data, is > a simple python module, etc); they should make the call and just do > it. > But we should still have a way to express this in package metadata in some way so it's clear that this is that kind of a package. What zmedico suggested does this nicely but other ways can be used too. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] QA: package.mask policies
В Сбт, 07/11/2009 в 18:24 +0100, Tomáš Chvátal пишет: > * Masking beta... > This masks are good if the software release is KNOWN to break previous > behaviour or degrade user experience. Otherwise the software should not be > masked (its TESTING for purpose, not stable). God no! If we'll start to do this way we'll loose a way to test packages that are supposed to go stable. It was told many times that testing branch is for testing ebuilds, not for packages and if upstream conciders them beta mask them. Or do you want Gentoo to have upstream suggested _only for testers_ versions end in stable tree? > Also the maintainer should watch if the testing branch is still relevant (why > on earth we have masked 4.0.3_p20070403 version of screen when newer 4.3 is > stable ;]) and remove the branch+mask when needed. Yup, such things happen, but this does not mean we should stop using package.mask for beta software. -- Peter.
Re: [gentoo-dev] Re: [RFC] Improve policy of stabilizations
В Вск, 08/11/2009 в 10:05 +0100, Fabian Groffen пишет: > On 07-11-2009 17:54:25 +0300, Peter Volkov wrote: > > > We could introduce "noarch" and "~noarch" KEYWORDS, add "noarch" to > > > the default ACCEPT_KEYWORDS setting for all profiles, and instruct > > > unstable users to add "~noarch" to ACCEPT_KEYWORDS. > > > > Looks like this will not work for all noarch packages. Stardict > > dictionary itself is noarch, but it RDEPENDS on stardict package which > > is keyworded only on some archs. So we'll be forced either to keyword > > stardict on all archs or we need to introduce some new way to work with > > such situations. > > Would it be reasonable to just mask in such case? Resolution would > eventually just hit the masked stardict dictionary and display the > reason why it's masked (stardict doesn't compile, not yet looked into > keywording: please try, etc.) As I understand: absense of ~arch keyword means package is masked on ~arch since nobody yet looked at this package. I was asking here: since noarch is allowed on all archs, how this noarch over arch KEYWORD stacking may work? -- Peter.
Re: [gentoo-dev] Re: [RFC] Improve policy of stabilizations
В Сбт, 07/11/2009 в 12:49 -0800, Zac Medico пишет: > Peter Volkov wrote: > >> We could introduce "noarch" and "~noarch" KEYWORDS, add "noarch" to > >> the default ACCEPT_KEYWORDS setting for all profiles, and instruct > >> unstable users to add "~noarch" to ACCEPT_KEYWORDS. > > > > Looks like this will not work for all noarch packages. Stardict > > dictionary itself is noarch, but it RDEPENDS on stardict package which > > is keyworded only on some archs. So we'll be forced either to keyword > > stardict on all archs or we need to introduce some new way to work with > > such situations. > > Keywording stardict on all archs doesn't sound reasonable, so I > guess we just need to make sure that repoman will allow the noarch > keyword even though the dependencies aren't keyworded on all > architectures. But how will portage handle such situations? Will it allow installation of noarch package and pull in *DEPEND only if possible, or will it prohibit installation of noarch pkgs with unsatisfied deps? The latter will make life harder for tools like eix, I guess. -- Peter.
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
Samuli Suominen wrote: > Joe Sapp (nixphoeni) wrote: >> nixphoeni09/10/27 11:21:25 >> >> Log: Directory /var/cvsroot/gentoo-x86/x11-plugins/desklet-Mouse added to >> the repository >> > > Since when did we start adding "big letters" to other than perl > -categories? > > *Very* ugly. Sorry about that, I thought it was a valid package name. I did it because it better reflects the upstream naming schemes. I suppose I could stop and move the few I've done so far back to all lowercase if there's enough consensus. Joe signature.asc Description: OpenPGP digital signature
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
В Вск, 08/11/2009 в 11:56 +, Patrick Lauer (patrick) пишет:
> patrick 09/11/08 11:56:46
> Log:
> Bump
> file :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-forensics/foremost/foremost-1.5.6.ebuild?rev=1.1&view=markup
> Index: foremost-1.5.6.ebuild
> ===
> inherit eutils toolchain-funcs
>
> DESCRIPTION="A console program to recover files based on their headers and
> footers"
> HOMEPAGE="http://foremost.sourceforge.net/";
> #SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
> # starting to hate sf.net ...
> SRC_URI="http://foremost.sourceforge.net/pkg/foremost-1.5.6.tar.gz";
Patrick, do you remember the answer on question number 1 in end-quiz?
> KEYWORDS="~ppc ~x86 ~amd64"
> src_install() {
> dobin foremost
This question did not existed in end-quiz at times you were mentored,
but still you are supposed to follow gentoo development and you are
supposed to know the answers on quizzes. Please check question 15 of
end-quiz.
--
Peter.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
On Sunday 08 November 2009 08:35:10 Joe Sapp wrote: > Samuli Suominen wrote: > > Joe Sapp (nixphoeni) wrote: > >> nixphoeni09/10/27 11:21:25 > >> > >> Log: Directory /var/cvsroot/gentoo-x86/x11-plugins/desklet-Mouse added > >> to the repository > > > > Since when did we start adding "big letters" to other than perl > > -categories? > > > > *Very* ugly. > > Sorry about that, I thought it was a valid package name. I did it because > it better reflects the upstream naming schemes. I suppose I could stop > and move the few I've done so far back to all lowercase if there's enough > consensus. it is a valid package name. if it makes your life easier, you're allowed to use the name. some people prefer to normalize everything lowercase -- if they're maintaining the package, they're free to do that. -mike signature.asc Description: This is a digitally signed message part.
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 15:21:18 Peter Volkov wrote:
> В Вск, 08/11/2009 в 11:56 +, Patrick Lauer (patrick) пишет:
> > patrick 09/11/08 11:56:46
> > Log:
> > Bump
> >
> > file :
> > http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-forensics/foremost/fo
> >remost-1.5.6.ebuild?rev=1.1&view=markup
> >
> > Index: foremost-1.5.6.ebuild
> > ===
> >
> > inherit eutils toolchain-funcs
> >
> > DESCRIPTION="A console program to recover files based on their headers
> > and footers" HOMEPAGE="http://foremost.sourceforge.net/";
> > #SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
> > # starting to hate sf.net ...
> > SRC_URI="http://foremost.sourceforge.net/pkg/foremost-1.5.6.tar.gz";
>
> Patrick, do you remember the answer on question number 1 in end-quiz?
>
Yeah, and if sf.net would even tangentially try to work I might care.
Took me long enough to get a file out of it, and if I feel like it I might
even fix that SRC_URI to make people happy.
Ah well. Since they love changing paths around it won't work for the next bump
anyway ...
> > KEYWORDS="~ppc ~x86 ~amd64"
> >
> > src_install() {
> > dobin foremost
>
> This question did not existed in end-quiz at times you were mentored,
> but still you are supposed to follow gentoo development and you are
> supposed to know the answers on quizzes. Please check question 15 of
> end-quiz.
Please check history of the ebuilds. It's been like this since 2004 in
foremost. I don't intend to clean up every ebuild I touch.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Patrick Lauer wrote:
> On Sunday 08 November 2009 15:21:18 Peter Volkov wrote:
>> В Вск, 08/11/2009 в 11:56 +, Patrick Lauer (patrick) пишет:
>>> patrick 09/11/08 11:56:46
>>> Log:
>>> Bump
>>>
>>> file :
>>> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-forensics/foremost/fo
>>> remost-1.5.6.ebuild?rev=1.1&view=markup
>>>
>>> Index: foremost-1.5.6.ebuild
>>> ===
>>>
>>> inherit eutils toolchain-funcs
>>>
>>> DESCRIPTION="A console program to recover files based on their headers
>>> and footers" HOMEPAGE="http://foremost.sourceforge.net/";
>>> #SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
>>> # starting to hate sf.net ...
>>> SRC_URI="http://foremost.sourceforge.net/pkg/foremost-1.5.6.tar.gz";
>> Patrick, do you remember the answer on question number 1 in end-quiz?
>>
> Yeah, and if sf.net would even tangentially try to work I might care.
> Took me long enough to get a file out of it, and if I feel like it I might
> even fix that SRC_URI to make people happy.
> Ah well. Since they love changing paths around it won't work for the next
> bump
> anyway ...
>
The filename that violates our policies hasn't changed between the new
and old SRC_URI.
Regards,
Petteri
signature.asc
Description: OpenPGP digital signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 15:56:24 Petteri Räty wrote:
> Patrick Lauer wrote:
> > On Sunday 08 November 2009 15:21:18 Peter Volkov wrote:
> >> В Вск, 08/11/2009 в 11:56 +, Patrick Lauer (patrick) пишет:
> >>> patrick 09/11/08 11:56:46
> >>> Log:
> >>> Bump
> >>>
> >>> file :
> >>> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-forensics/foremost/
> >>>fo remost-1.5.6.ebuild?rev=1.1&view=markup
> >>>
> >>> Index: foremost-1.5.6.ebuild
> >>> ===
> >>>
> >>> inherit eutils toolchain-funcs
> >>>
> >>> DESCRIPTION="A console program to recover files based on their headers
> >>> and footers" HOMEPAGE="http://foremost.sourceforge.net/";
> >>> #SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
> >>> # starting to hate sf.net ...
> >>> SRC_URI="http://foremost.sourceforge.net/pkg/foremost-1.5.6.tar.gz";
> >>
> >> Patrick, do you remember the answer on question number 1 in end-quiz?
> >
> > Yeah, and if sf.net would even tangentially try to work I might care.
> > Took me long enough to get a file out of it, and if I feel like it I
> > might even fix that SRC_URI to make people happy.
> > Ah well. Since they love changing paths around it won't work for the next
> > bump anyway ...
>
> The filename that violates our policies hasn't changed between the new
> and old SRC_URI.
>
Correct. Just the PATH. Which is not the filename.
And because I'm a lazy bum I copypasta'ed it out of the mess the sourceforge
people call a website. And then I even managed to fetch that file after 3 or 4
tries, so I was happy to have gotten it and cared more to see if it works.
So I'd appreciate if y'all stopped obsessing about such details and just fix
it instead of whining at me until my motivation takes a long walk on the beach
and doesn't return for quite some time. At least I'm trying to keep these
packages alive, which noone else seems to do.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On 08-11-2009 16:06:58 +0100, Patrick Lauer wrote: > So I'd appreciate if y'all stopped obsessing about such details and > just fix it instead of whining at me until my motivation takes a long +1 > walk on the beach and don't return for quite some time. At least I'm > trying to keep these packages alive, which noone else seems to do. thanks -- Fabian Groffen Gentoo on a different level
[gentoo-dev] Re: QA: package.mask policies
Hi, Duncan <1i5t5.dun...@cox.net>: > 1) Users using ** in their package.keywords file should know enough > about what they're doing to use their own package.mask, as well. If > they're using ** in the keywords file, they're /saying/ they're > reading to handle such things, after all, why shouldn't we let them? They do it, because they don't know what they are doing. Just seen it somewhere, heard about it. During LinuxTag the question why ** unmasks some live ebuilds occured at least three times. V-Li -- Christian Faulhammer, Gentoo Lisp project http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode http://gentoo.faulhammer.org/> signature.asc Description: PGP signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Patrick Lauer wrote: > So I'd appreciate if y'all stopped obsessing about such details and just fix > it instead of whining at me until my motivation takes a long walk on the > beach > and doesn't return for quite some time. At least I'm trying to keep these > packages alive, which noone else seems to do. In the long time more time is spent in total if you do a crappy job and others clean up after you. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
В Вск, 08/11/2009 в 09:40 -0500, Mike Frysinger пишет: > On Sunday 08 November 2009 08:35:10 Joe Sapp wrote: > > Samuli Suominen wrote: > > > Joe Sapp (nixphoeni) wrote: > > >> nixphoeni09/10/27 11:21:25 > > >> > > >> Log: Directory /var/cvsroot/gentoo-x86/x11-plugins/desklet-Mouse added > > >> to the repository > > > > > > Since when did we start adding "big letters" to other than perl > > > -categories? > > > > > > *Very* ugly. > > > > Sorry about that, I thought it was a valid package name. I did it because > > it better reflects the upstream naming schemes. I suppose I could stop > > and move the few I've done so far back to all lowercase if there's enough > > consensus. > > it is a valid package name. if it makes your life easier, you're allowed to > use the name. some people prefer to normalize everything lowercase -- if > they're maintaining the package, they're free to do that. Until it was decided differently, no, it's not: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap3 "The first subsection, pkg, is the package name, which should only contain lowercase letters, the digits 0-9, and any number of single hyphen (-), underscore (_) or plus (+) characters." -- Peter.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 10:06:58 Patrick Lauer wrote: > So I'd appreciate if y'all stopped obsessing about such details and just > fix it instead of whining at me until my motivation takes a long walk on > the beach and doesn't return for quite some time. At least I'm trying to > keep these packages alive, which noone else seems to do. if you're introducing crap into the tree, then it is better if you took that long walk -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrick Lauer wrote: > At least I'm trying to keep these > packages alive, which noone else seems to do. If you spot that a new version is available, you're more than welcome to post a version bump bug assigned to the appropriate herd and developer (forensics and me, in this instance). I don't necessarily have time to stayed glued to exactly when new versions of a package come out, but that doesn't mean I'm not willing to spend the time to keep it up to date once I'm aware a new version's come out. If nobody tells me, it'll have to wait until I spot it myself. Foremost has a single bug open against it, which is a stabilization bug, that means it still compiles, and works, or that no one's bothered to complain about it. So I'd class the package as far from dead. Please don't claim no one else wants to keep the package alive, when you don't afford them the opportunity to demonstrate that they do. If you take responsibility for bumping a package from the appropriate maintainer, you can't then turn around and claim you're allowed to cut corners because no one was maintaining it. It's quite rude to the people who are willing to look after it... Mike 5:) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.13 (GNU/Linux) iEYEARECAAYFAkr25AYACgkQu7rWomwgFXrIxQCgnVdigpUJZnaW28HcJ2U8qQZy b9IAoJc2Afv0UfrrYu7xe7EdP1DCP2Ze =m8Os -END PGP SIGNATURE-
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
On Sunday 08 November 2009 10:25:56 Peter Volkov wrote: > В Вск, 08/11/2009 в 09:40 -0500, Mike Frysinger пишет: > > On Sunday 08 November 2009 08:35:10 Joe Sapp wrote: > > > Samuli Suominen wrote: > > > > Joe Sapp (nixphoeni) wrote: > > > >> nixphoeni09/10/27 11:21:25 > > > >> > > > >> Log: Directory /var/cvsroot/gentoo-x86/x11-plugins/desklet-Mouse > > > >> added to the repository > > > > > > > > Since when did we start adding "big letters" to other than perl > > > > -categories? > > > > > > > > *Very* ugly. > > > > > > Sorry about that, I thought it was a valid package name. I did it > > > because it better reflects the upstream naming schemes. I suppose I > > > could stop and move the few I've done so far back to all lowercase if > > > there's enough consensus. > > > > it is a valid package name. if it makes your life easier, you're allowed > > to use the name. some people prefer to normalize everything lowercase -- > > if they're maintaining the package, they're free to do that. > > Until it was decided differently, no, it's not: > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#do > c_chap3 > > "The first subsection, pkg, is the package name, which should only > contain lowercase letters, the digits 0-9, and any number of single > hyphen (-), underscore (_) or plus (+) characters." try quoting from the PMS which has been council approved -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
Mike Frysinger wrote: > On Sunday 08 November 2009 10:25:56 Peter Volkov wrote: >> В Вск, 08/11/2009 в 09:40 -0500, Mike Frysinger пишет: >>> On Sunday 08 November 2009 08:35:10 Joe Sapp wrote: Samuli Suominen wrote: > Joe Sapp (nixphoeni) wrote: >> nixphoeni09/10/27 11:21:25 >> >> Log: Directory /var/cvsroot/gentoo-x86/x11-plugins/desklet-Mouse >> added to the repository > Since when did we start adding "big letters" to other than perl > -categories? > > *Very* ugly. Sorry about that, I thought it was a valid package name. I did it because it better reflects the upstream naming schemes. I suppose I could stop and move the few I've done so far back to all lowercase if there's enough consensus. >>> it is a valid package name. if it makes your life easier, you're allowed >>> to use the name. some people prefer to normalize everything lowercase -- >>> if they're maintaining the package, they're free to do that. >> Until it was decided differently, no, it's not: >> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#do >> c_chap3 >> >> "The first subsection, pkg, is the package name, which should only >> contain lowercase letters, the digits 0-9, and any number of single >> hyphen (-), underscore (_) or plus (+) characters." > > try quoting from the PMS which has been council approved > -mike For EAPI 0 there's only an approved draft but nothing final. But even as a draft it's more accurate than devrel handbook that in all reality should loose all the technical stuff in favor of devmanual. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
> On Sun, 8 Nov 2009, Mike Frysinger wrote: >> "The first subsection, pkg, is the package name, which should only >> contain lowercase letters, the digits 0-9, and any number of single >> hyphen (-), underscore (_) or plus (+) characters." > try quoting from the PMS which has been council approved That's not a contradiction. There are several places where the devmanual is more restrictive than PMS. Of course the package manager must accept capital letters in names. That doesn't necessarily imply that they should be used all over the tree. Ulrich
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
On Sunday 08 November 2009 11:42:31 Ulrich Mueller wrote: > > On Sun, 8 Nov 2009, Mike Frysinger wrote: > >> "The first subsection, pkg, is the package name, which should only > >> contain lowercase letters, the digits 0-9, and any number of single > >> hyphen (-), underscore (_) or plus (+) characters." > > > > try quoting from the PMS which has been council approved > > That's not a contradiction. > > There are several places where the devmanual is more restrictive than > PMS. and in this case, the devmanual is irrelevant and should be deleted > Of course the package manager must accept capital letters in > names. right, because we've always had mixed case in the tree and anything that parses the tree/ebuilds must support both if it has any chance of working. this isnt going to change. > That doesn't necessarily imply that they should be used all > over the tree. if it makes maintaining a package easier (as appears to be the case for Joe), then there's no technical reason whatsoever to tell him otherwise. if you dislike mixed case, then dont use it. but Joe is free to do so. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] QA: package.mask policies
On Sat, 7 Nov 2009 18:24:10 +0100 Tomáš Chvátal wrote: > * Masking beta... > This masks are good if the software release is KNOWN to break > previous behaviour or degrade user experience. Otherwise the software > should not be masked (its TESTING for purpose, not stable). > Also the maintainer should watch if the testing branch is still > relevant (why on earth we have masked 4.0.3_p20070403 version of > screen when newer 4.3 is stable ;]) and remove the branch+mask when > needed. I agree with your criticism (i.e. that the mask should not be there, especially not for "testing" as what the mask does is *prevent* testing instead of enabling it), but must note that your version sorting algorithm appears to be flawed: pkg-vX_pY (for patch level) is always greater than pkg-vX. Regards, jer
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
> On Sun, 8 Nov 2009, Mike Frysinger wrote: > [...] we've always had mixed case in the tree and anything that > parses the tree/ebuilds must support both if it has any chance of > working. this isnt going to change. I think everyone agrees on this one. >> That doesn't necessarily imply that they should be used all over >> the tree. > if it makes maintaining a package easier (as appears to be the case > for Joe), then there's no technical reason whatsoever to tell him > otherwise. if you dislike mixed case, then dont use it. but Joe is > free to do so. Shouldn't the rationale be to make it easy for users, not for maintainers? Ulrich
Re: [gentoo-dev] QA: package.mask policies
Dne neděle 08 Listopad 2009 17:57:10 Jeroen Roovers napsal(a): > On Sat, 7 Nov 2009 18:24:10 +0100 > > Tomáš Chvátal wrote: > > * Masking beta... > > This masks are good if the software release is KNOWN to break > > previous behaviour or degrade user experience. Otherwise the software > > should not be masked (its TESTING for purpose, not stable). > > Also the maintainer should watch if the testing branch is still > > relevant (why on earth we have masked 4.0.3_p20070403 version of > > screen when newer 4.3 is stable ;]) and remove the branch+mask when > > needed. > > I agree with your criticism (i.e. that the mask should not be there, > especially not for "testing" as what the mask does is *prevent* testing > instead of enabling it), but must note that your version sorting > algorithm appears to be flawed: pkg-vX_pY (for patch level) is always > greater than pkg-vX. > > > Regards, > jer > I agree that _p is newer than that. But if we look on tag of screen-4.0.3 or its release: screen-4.0.2.tar.gz27-Jan-2004 05:46 821K screen-4.0.2.tar.gz.sig27-Jan-2004 05:47 65 screen-4.0.3.tar.gz07-Aug-2008 06:30 821K screen-4.0.3.tar.gz.sig07-Aug-2008 06:30 65 You see the pattern? It is 1 year newer than it. Tomas signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
On Sunday 08 November 2009 12:15:44 Ulrich Mueller wrote: > > On Sun, 8 Nov 2009, Mike Frysinger wrote: > >> That doesn't necessarily imply that they should be used all over > >> the tree. > > > > if it makes maintaining a package easier (as appears to be the case > > for Joe), then there's no technical reason whatsoever to tell him > > otherwise. if you dislike mixed case, then dont use it. but Joe is > > free to do so. > > Shouldn't the rationale be to make it easy for users, not for > maintainers? of course -- fix the package manager to do a case insensitive search when someone says `emerge foo` but the package is actually "Foo". -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
В Вск, 08/11/2009 в 16:06 +0100, Patrick Lauer пишет: > And because I'm a lazy > I'd appreciate if y'all stopped obsessing about such details and just fix > it instead Do you mean that whatever you commit to the tree is not your responsibility? Sorry but it's your job. Also it's nice to see how you touch packages without even minimal negotiation with maintainers and at the same time you are not subscribed to bug mail of relevant herds and you do not add yourself into metadata.xml. Such behaviour is prohibited. Please, stop doing that. -- Peter.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-plugins/desklet-Mouse: - New directory
Mike Frysinger wrote: > if it makes maintaining a package easier (as appears to be the case for Joe), > then there's no technical reason whatsoever to tell him otherwise. if you > dislike mixed case, then dont use it. but Joe is free to do so. For what it's worth, this is exactly the reason. The eclass can use a trivial bash substitution to access the package name (for SRC_URI, for example) instead of requiring each ebuild to set a variable specifying how the information in the ebuild name should be capitalized. Joe signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 18:37:10 Peter Volkov wrote: > В Вск, 08/11/2009 в 16:06 +0100, Patrick Lauer пишет: > > And because I'm a lazy > > > > I'd appreciate if y'all stopped obsessing about such details and just fix > > it instead > > Do you mean that whatever you commit to the tree is not your > responsibility? Sorry but it's your job. I make things work. Cosmetics are quite low on my list of priorities. Feel free to fix such things. All "my" packages are free for all to bump, fix and extend, as long as whoever touched it is willing to fix any issues that happen from it. > > Also it's nice to see how you touch packages without even minimal > negotiation with maintainers and at the same time you are not subscribed > to bug mail of relevant herds and you do not add yourself into > metadata.xml. Such behaviour is prohibited. Please, stop doing that. I'm the only person in the benchmarks herd and with dragonheart the only one in forensics herd. What's the exact problem here? Also, if I break anything ... assign the bugs to me. I'll unbreak it. Easy as that. And if you're rude enough I'll avoid touching your packages in the future and yell at you when things don't get fixed in a reasonable time. Have fun, Patrick
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 13:10:34 Patrick Lauer wrote: > On Sunday 08 November 2009 18:37:10 Peter Volkov wrote: > > В Вск, 08/11/2009 в 16:06 +0100, Patrick Lauer пишет: > > > And because I'm a lazy > > > > > > I'd appreciate if y'all stopped obsessing about such details and just > > > fix it instead > > > > Do you mean that whatever you commit to the tree is not your > > responsibility? Sorry but it's your job. > > I make things work. Cosmetics are quite low on my list of priorities. > Feel free to fix such things. > All "my" packages are free for all to bump, fix and extend, as long as > whoever touched it is willing to fix any issues that happen from it. using this definition of "correct" (the package installs w/out failure and it seems to work), there is a lot of crap that could be in the tree. that doesnt mean the ebuild should be in the tree. this kind of work and opinion belongs in sunrise, not the main tree. we dont have a QA team to fix installed packages; they're here to maintain the *quality* of the tree. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 19:24:47 Mike Frysinger wrote: > On Sunday 08 November 2009 13:10:34 Patrick Lauer wrote: > > On Sunday 08 November 2009 18:37:10 Peter Volkov wrote: > > > В Вск, 08/11/2009 в 16:06 +0100, Patrick Lauer пишет: > > > > And because I'm a lazy > > > > > > > > I'd appreciate if y'all stopped obsessing about such details and just > > > > fix it instead > > > > > > Do you mean that whatever you commit to the tree is not your > > > responsibility? Sorry but it's your job. > > > > I make things work. Cosmetics are quite low on my list of priorities. > > Feel free to fix such things. > > All "my" packages are free for all to bump, fix and extend, as long as > > whoever touched it is willing to fix any issues that happen from it. > > using this definition of "correct" (the package installs w/out failure and > it seems to work), there is a lot of crap that could be in the tree. that > doesnt mean the ebuild should be in the tree. this kind of work and > opinion belongs in sunrise, not the main tree. I hope you realize what percentage of packages are completely unmaintained or only tangentially maintained. By that reasoning we better cut out everything apart from the base system, xorg, kde and gnome. Oh, and python. (If I missed anyone here, please don't take this personal. It's a reductio ad absurdum I'm doing here, so it better be absurd!) If you haven't noticed (here's a really hilarious one!) ... We currently do not have anyone seriously maintaining all the perl bits. There's, uhm, ... err ... there used to be Tove, who did an awesome job. I took over benchmark and forensics herd because they were empty, not because I care about those packages. sgml and ha-cluster herds are quite vacant as far as I can tell. bugwranglers are understaffed and can barely keep up with the current flood from our motivated and skillfull bug-finding users. So maybe now you understand my mentality of just fixing whatever bugs I encounter. I don't care at all about your idealistic views of how we were to do things if everything worked. Reality doesn't tolerate it well. Bugs happen, and we better start fixing them. > we dont have a QA team to > fix installed packages; they're here to maintain the *quality* of the > tree. That's good. So start fixing stuff. Maybe take over the empty herds until you manage to recruit some replacements. If you feel you have too much time you could search on bugzilla for "patch" and start fixing those bugs. "Bump" is also a funny search. Or if you don't know what else to do, there's this nice "Bug Wranglers" search at the bottom of the bugzilla pages. Click on it and get the amount of bugs in the bugwrangler queue under 100 if you can! Once you've done that for 3 months we can renegotiate cosmetic bugs and QA. Kthxbai, Patrick
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Patrick Lauer said: > If you feel you have too much time you could search on bugzilla for "patch" > and start fixing those bugs. "Bump" is also a funny search. If you are just bumping random packages and applying patches when you have no idea how the package works, we have a problem on our hands. Please don't do that, you are only making more work for others. Perhaps some of the things that are not maintained should go away. > Once you've done that for 3 months we can renegotiate cosmetic bugs and QA. Renegotiate QA? Do not commit anything to the tree that doesn't comply to QA standards. Its really that simple. Don't be lazy and do things the right way, or don't do them at all. > Kthxbai, Also, please learn how to communicate in a manner that is constructive instead of acting like a dick at every opportunity. -- Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com pgpgRzcnPXpT9.pgp Description: PGP signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Mike Frysinger schrieb: > On Sunday 08 November 2009 13:10:34 Patrick Lauer wrote: >> On Sunday 08 November 2009 18:37:10 Peter Volkov wrote: >>> В Вск, 08/11/2009 в 16:06 +0100, Patrick Lauer пишет: And because I'm a lazy I'd appreciate if y'all stopped obsessing about such details and just fix it instead >>> Do you mean that whatever you commit to the tree is not your >>> responsibility? Sorry but it's your job. >> I make things work. Cosmetics are quite low on my list of priorities. >> Feel free to fix such things. >> All "my" packages are free for all to bump, fix and extend, as long as >> whoever touched it is willing to fix any issues that happen from it. > > using this definition of "correct" (the package installs w/out failure and it > seems to work), there is a lot of crap that could be in the tree. that > doesnt > mean the ebuild should be in the tree. this kind of work and opinion belongs > in sunrise, not the main tree. we dont have a QA team to fix installed > packages; they're here to maintain the *quality* of the tree. > -mike Please stop such comments. Sunrise really isnt a place, where you can drop anything in without any quality check. Join the sunrise team, do our work for some months, then tell me, where it lacks quality checks or anything else. -- Thomas Sachau Gentoo Linux Developer signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 20:27:23 Mark Loeser wrote: > Patrick Lauer said: > > If you feel you have too much time you could search on bugzilla for > > "patch" and start fixing those bugs. "Bump" is also a funny search. > > If you are just bumping random packages and applying patches when you > have no idea how the package works, we have a problem on our hands. > Please don't do that, you are only making more work for others. Perhaps > some of the things that are not maintained should go away. Like Perl? I like your plan already. > > Once you've done that for 3 months we can renegotiate cosmetic bugs and > > QA. > > Renegotiate QA? Do not commit anything to the tree that doesn't comply > to QA standards. Its really that simple. Don't be lazy and do things > the right way, or don't do them at all. That is an interesting opinion. But I doubt we're in a position to demand such things - I did point at a few minor issues in my last email, none of which you responded to in any way. So I guess you prefer things being unmaintained and rotting away so our users have the shittiest user experience possible instead of people trying to make things better. Now if you really were interested in QA you might want to do some things - like help bugwranglers. With the current amount of people available (not enough) and the influx of bugs (100-200 a day) we have a latency of worst case a few days until a bugwrangler looks at it. (Average case is much better). That is time the maintainers are not informed of a bug, which means we delay fixing it. Sucks from a QA point of view. Things like that would be good to have, but instead y'all spend lots of time discussing on mailinglists and not helping there. (Ok, we're all volunteers, we all have limited time, etc. etc.) So I find it a bit hard to care about your academic discussion of how to handle things when I haven't heard any idea of a solution to the problems I mentioned earlier. Head-in-the-sand is not going to work. And again, start at the basics. You can't build a tower without a solid foundation. "Does it compile" is more important than "does it respect as- needed" or "is indentation beautiful", so prioritize a bit and focus on getting the big problems resolved. Take care, Patrick
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
2009/11/8 Mark Loeser : > Also, please learn how to communicate in a manner that is constructive > instead of acting like a dick at every opportunity. Looks to me this should be applied to some others in this thread first. Really, aren't there more constructive ways to communicate your (meaning all of you in this thread) concerns, without demotivating the person who does so much work for Gentoo? Cheers, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) __
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Ben de Groot said: > 2009/11/8 Mark Loeser : > > Also, please learn how to communicate in a manner that is constructive > > instead of acting like a dick at every opportunity. > > Looks to me this should be applied to some others in this thread first. > Really, aren't there more constructive ways to communicate your (meaning > all of you in this thread) concerns, without demotivating the person who > does so much work for Gentoo? If the person doing said work does not care about abiding by QA standards, then that person shouldn't be touching the tree to begin with. -- Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com pgpv1uG57G78X.pgp Description: PGP signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
2009/11/8 Mark Loeser : > Ben de Groot said: >> Really, aren't there more constructive ways to communicate your (meaning >> all of you in this thread) concerns, without demotivating the person who >> does so much work for Gentoo? > > If the person doing said work does not care about abiding by QA > standards, then that person shouldn't be touching the tree to begin > with. So, you didn't get my point. It must be true then, what they say about geeks and social skills... Cheers, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) __
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-benchmarks/bonnie++: bonnie++-1.96.ebuild ChangeLog bonnie++-1.93c.ebuild
This removed the only stable version of bonnie++ from the tree. I have
just added it back to the tree.
Everyone, please be careful when you are pruning old ebuilds.
Thanks,
Mark
"Patrick Lauer (patrick)" said:
> patrick 09/11/08 12:26:16
>
> Modified: ChangeLog
> Added:bonnie++-1.96.ebuild
> Removed: bonnie++-1.93c.ebuild
> Log:
> Bump, remove old
> (Portage version: 2.2_rc49/cvs/Linux x86_64)
>
> Revision ChangesPath
> 1.28 app-benchmarks/bonnie++/ChangeLog
>
> file :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-benchmarks/bonnie++/ChangeLog?rev=1.28&view=markup
> plain:
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-benchmarks/bonnie++/ChangeLog?rev=1.28&content-type=text/plain
> diff :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-benchmarks/bonnie++/ChangeLog?r1=1.27&r2=1.28
>
> Index: ChangeLog
> ===
> RCS file: /var/cvsroot/gentoo-x86/app-benchmarks/bonnie++/ChangeLog,v
> retrieving revision 1.27
> retrieving revision 1.28
> diff -u -r1.27 -r1.28
> --- ChangeLog 16 Jun 2009 14:38:12 - 1.27
> +++ ChangeLog 8 Nov 2009 12:26:15 - 1.28
> @@ -1,6 +1,12 @@
> # ChangeLog for app-benchmarks/bonnie++
> # Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
> -# $Header: /var/cvsroot/gentoo-x86/app-benchmarks/bonnie++/ChangeLog,v 1.27
> 2009/06/16 14:38:12 jer Exp $
> +# $Header: /var/cvsroot/gentoo-x86/app-benchmarks/bonnie++/ChangeLog,v 1.28
> 2009/11/08 12:26:15 patrick Exp $
> +
> +*bonnie++-1.96 (08 Nov 2009)
> +
> + 08 Nov 2009; Patrick Lauer -bonnie++-1.93c.ebuild,
> + +bonnie++-1.96.ebuild:
> + Bump, remove old
>
>16 Jun 2009; Jeroen Roovers bonnie++-1.95.ebuild:
>Marked ~hppa too.
>
>
>
> 1.1 app-benchmarks/bonnie++/bonnie++-1.96.ebuild
>
> file :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-benchmarks/bonnie++/bonnie++-1.96.ebuild?rev=1.1&view=markup
> plain:
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-benchmarks/bonnie++/bonnie++-1.96.ebuild?rev=1.1&content-type=text/plain
>
> Index: bonnie++-1.96.ebuild
> ===
> # Copyright 1999-2009 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
> # $Header:
> /var/cvsroot/gentoo-x86/app-benchmarks/bonnie++/bonnie++-1.96.ebuild,v 1.1
> 2009/11/08 12:26:15 patrick Exp $
>
> inherit eutils
>
> DESCRIPTION="Hard drive bottleneck testing benchmark suite."
> HOMEPAGE="http://www.coker.com.au/bonnie++/";
> SRC_URI="http://www.coker.com.au/bonnie++/experimental/${P}.tgz";
>
> LICENSE="GPL-2"
> SLOT="0"
> KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
> IUSE="debug"
>
> DEPEND=""
> RDEPEND=""
>
> src_compile() {
> econf \
> $(use_with debug) \
> --disable-stripping \
> || die
> emake || die "emake failed"
> emake zcav || die "emake zcav failed" # see #9073
> }
>
> src_install() {
> dosbin bonnie++ zcav || die
> dobin bon_csv2html bon_csv2txt || die
> doman bon_csv2html.1 bon_csv2txt.1 bonnie++.8 zcav.8
> dohtml readme.html
> dodoc changelog.txt credits.txt
> }
>
>
>
>
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
pgpoFIU5ZXEXR.pgp
Description: PGP signature
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 14:46:34 Thomas Sachau wrote: > Mike Frysinger schrieb: > > On Sunday 08 November 2009 13:10:34 Patrick Lauer wrote: > >> On Sunday 08 November 2009 18:37:10 Peter Volkov wrote: > >>> В Вск, 08/11/2009 в 16:06 +0100, Patrick Lauer пишет: > And because I'm a lazy > > I'd appreciate if y'all stopped obsessing about such details and just > fix it instead > >>> > >>> Do you mean that whatever you commit to the tree is not your > >>> responsibility? Sorry but it's your job. > >> > >> I make things work. Cosmetics are quite low on my list of priorities. > >> Feel free to fix such things. > >> All "my" packages are free for all to bump, fix and extend, as long as > >> whoever touched it is willing to fix any issues that happen from it. > > > > using this definition of "correct" (the package installs w/out failure > > and it seems to work), there is a lot of crap that could be in the tree. > > that doesnt mean the ebuild should be in the tree. this kind of work and > > opinion belongs in sunrise, not the main tree. we dont have a QA team to > > fix installed packages; they're here to maintain the *quality* of the > > tree. > > Please stop such comments. Sunrise really isnt a place, where you can drop > anything in without any quality check. Join the sunrise team, do our work > for some months, then tell me, where it lacks quality checks or anything > else. you misinterpreted my post. sunrise has built in processes to get the quality up past crap. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
On Sunday 08 November 2009 15:22:19 Ben de Groot wrote: > 2009/11/8 Mark Loeser : > > Ben de Groot said: > >> Really, aren't there more constructive ways to communicate your (meaning > >> all of you in this thread) concerns, without demotivating the person who > >> does so much work for Gentoo? > > > > If the person doing said work does not care about abiding by QA > > standards, then that person shouldn't be touching the tree to begin > > with. > > So, you didn't get my point. It must be true then, what they say about > geeks and social skills... i dont think your point is relevant to this thread -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
none of your points here are relevant to the original issue at hand. like Mark said, if you cant be bothered to do it right in the first place, then dont do it at all. if that means packages get removed from the tree, then so be it. it isnt that hard to do it right in the first place, so stop bemoaning the point. people have done volumes of work in the past to update random packages and didnt have trouble tackling the basics. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: QA: package.mask policies
Duncan wrote: In theory that's what those stupid version string thingys are for, but it's s much easier just to forget one! =:^[ Maybe something about this should go in the handbook -- a suggestion that if one is going to use a package.unmask entry, that they copy the package.mask entry over, thus at least letting the devs minimize the version spread damage with their package.mask entries. That's what I've started doing, and it works surprisingly well, as I have right there the comment on why it was masked (and add a comment on why I'm unmasking, when I think I might wonder, later), and it's the exact same versions the devs masked in the first place, so I don't have to worry so much about unintended version spread -- at least as long as the devs doing the masking worried about it then. =:^) What do you devs think? Would that be a practical hint for the handbook? Would it be helpful in allowing /you/ to control the version spread of the unmask, by consequence of your control of the version spread on the mask in the first place? Hi, handbook is one thing, but maybe portage could make it more prominent when it displays the packages to be merged, so that the users hopefuly notice? - visibly distinguish (red color and stuff?) packages that are to be installed thanks to package.unmask or ** keyword - print extra warnings about those entries in package.unmask and ** keywords that are not version restricted, if they contain the packages to be merged. This could follow the suggestion above - aside from the distinguished packages, below the list and above the yes/no (if --ask is used) there would be "Warning: the following packages have broad unmasks, you sure you want these versions?" and the list. Vlastimil
[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2009-11-08 23h59 UTC
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2009-11-08 23h59 UTC. Removals: media-plugins/mythdvd 2009-11-02 01:46:02 cardoe net-misc/asterisk-app_rtxfax2009-11-02 15:56:58 volkmar net-misc/asterisk-chan_unicall 2009-11-02 15:59:00 volkmar net-libs/libmfcr2 2009-11-02 16:00:11 volkmar media-libs/libsupertone 2009-11-02 16:01:47 volkmar net-libs/libunicall 2009-11-02 16:05:48 volkmar games-action/astromenace-bin2009-11-02 16:08:08 mr_bones_ net-irc/quirc 2009-11-02 23:13:57 vostorga sys-apps/sreadahead 2009-11-02 23:21:49 vostorga dev-perl/Gtk2-PodViewer 2009-11-03 11:45:30 tove dev-perl/aww2009-11-03 11:45:31 tove dev-perl/perlsieve 2009-11-03 11:45:31 tove dev-perl/perlrapi 2009-11-03 11:45:32 tove dev-perl/Gtk2-Html2 2009-11-03 11:45:32 tove media-libs/freeimage2009-11-05 01:34:59 nyhm sci-biology/dotur 2009-11-06 17:38:34 weaver sci-biology/dialign-t 2009-11-06 20:05:03 weaver app-shells/sandboxshell 2009-11-06 23:03:29 vapier kde-base/kde-menu 2009-11-08 23:52:05 abcd kde-base/kde-menu-icons 2009-11-08 23:52:05 abcd kde-base/kde-wallpapers 2009-11-08 23:52:06 abcd Additions: dev-python/kaa-display 2009-11-02 06:14:02 arfrever games-mud/kildclient2009-11-02 23:03:24 mr_bones_ kde-misc/gx-mail-notify 2009-11-03 13:03:41 ssuominen kde-misc/kio_gopher 2009-11-03 13:30:12 ssuominen media-sound/kaudiocreator 2009-11-03 13:57:23 ssuominen media-gfx/qvv 2009-11-03 16:09:57 ssuominen net-irc/irssi-xmpp 2009-11-03 17:49:04 dertobi123 games-puzzle/pipepanic 2009-11-03 19:45:44 mr_bones_ games-puzzle/freesweep 2009-11-04 05:08:35 mr_bones_ kde-misc/plasma-indicatordisplay2009-11-04 15:59:36 scarabeus app-editors/znotes 2009-11-04 18:26:50 yngwin x11-misc/basqet 2009-11-04 19:28:20 yngwin kde-misc/ktrafficanalyzer 2009-11-05 08:51:29 ssuominen x11-drivers/xf86-input-wacom2009-11-05 12:02:20 remi kde-misc/qtrans 2009-11-05 12:28:23 ssuominen kde-misc/kdmthemegenerator 2009-11-05 12:54:39 ssuominen media-video/videocut2009-11-05 13:34:48 ssuominen games-puzzle/biniax22009-11-05 18:31:24 nyhm games-board/capitalism 2009-11-05 18:53:37 ssuominen sci-chemistry/icm-browser 2009-11-05 20:55:12 alexxy sci-chemistry/icm 2009-11-05 20:59:05 alexxy x11-themes/nitrogen 2009-11-06 19:35:29 ssuominen x11-themes/dekorator2009-11-06 19:54:27 ssuominen sci-biology/dialign-tx 2009-11-06 19:58:46 weaver app-i18n/ibus-sunpinyin 2009-11-08 03:49:53 matsuu net-print/xerox-drivers 2009-11-08 11:19:44 elvanor x11-misc/piedock2009-11-08 15:00:12 ssuominen media-sound/kmidimon2009-11-08 16:49:55 ssuominen net-nntp/kwooty 2009-11-08 21:47:14 ssuominen net-nntp/nzb2009-11-08 22:00:04 ssuominen -- Robin Hugh Johnson Gentoo Linux Developer E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 Removed Packages: media-plugins/mythdvd,removed,cardoe,2009-11-02 01:46:02 net-misc/asterisk-app_rtxfax,removed,volkmar,2009-11-02 15:56:58 net-misc/asterisk-chan_unicall,removed,volkmar,2009-11-02 15:59:00 net-libs/libmfcr2,removed,volkmar,2009-11-02 16:00:11 media-libs/libsupertone,removed,volkmar,2009-11-02 16:01:47 net-libs/libunicall,removed,volkmar,2009-11-02 16:05:48 games-action/astromenace-bin,removed,mr_bones_,2009-11-02 16:08:08 net-irc/quirc,removed,vostorga,2009-11-02 23:13:57 sys-apps/sreadahead,removed,vostorga,2009-11-02 23:21:49 dev-perl/Gtk2-PodViewer,removed,tove,2009-11-03 11:45:30 dev-perl/aww,removed,tove,2009-11-03 11:45:31 dev-perl/perlsieve,removed,tove,2009-11-03 11:45:31 dev-perl/perlrapi,removed,tove,2009-11-03 11:45:32 dev-perl/Gtk2-Html2,removed,tove,2009-11-03 11:45:32 media-libs/freeimage,removed,nyhm,2009-11-05 01:34:59 sci-biology/dotur,removed,weaver,2009-11-06 17:38:34 sci-biology/dialign-t,removed,weaver,2009-11-06 20:05:03 app-shells/sandboxshell,removed,vapier,2009-11-06 23:03:
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Petteri Räty wrote:
#SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
# starting to hate sf.net ...
SRC_URI="http://foremost.sourceforge.net/pkg/foremost-1.5.6.tar.gz";
The filename that violates our policies hasn't changed between the new
and old SRC_URI.
Is this policy actually written down someplace? Sure, having the
SRC_URI pick up the package version automatically is good practice and
all, but does this actually rise to the level of a QA policy violation?
To me the word "policy violation" means more than just something that
could have been done better. It means that someplace there is an
official rule in writing that wasn't followed, and that rule was
endorsed by some official body recognized by gentoo. I don't think
quizzes can be considered policy since by design their answers aren't
written anywhere.
The only downside to not being clever with the SRC_URI is that to bump
the package you'd need to edit the URL. That isn't exactly the end of
the world, and while this is a trivial one to fix I've certainly seen a
few that are quite messy to automate.
Now, if there were no version in the filename I'd consider that a policy
issue as it would mean that the distfiles would get confused rather
quickly. However, not every lack of ideality is a policy violation
worthy of a 30-post -dev thread.
Even so, it doesn't hurt to point out non-idealities so that they can be
corrected. Let's just try not to treat them the same as if somebody had
keyworded something that breaks stable systems...
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Ben de Groot wrote: 2009/11/8 Mark Loeser : Also, please learn how to communicate in a manner that is constructive instead of acting like a dick at every opportunity. Looks to me this should be applied to some others in this thread first. Really, aren't there more constructive ways to communicate your (meaning all of you in this thread) concerns, without demotivating the person who does so much work for Gentoo? Cheers, I totally agree. And I must say it started with the very first mail of pva. Accusing of not knowing quizzes was totally uncalled for. As patrick said, the SRC_URI thing was simply forgot to be polished after testing, and the dobin thing he didn't even touch. Who remembers what everything should have || die or not from the top of his head and spots it immediatelly? And this offensive tone just provoked adequate reaction and here we are, useless flame. People can sometimes commit much worse stuff by mistake, this didn't break anything. If the first mail was just a 'hey this should bw changed to X and Y', that could be it. It's great that somebody cares to fix stuff, it's also great that somebody watches the commits for mistakes, but let's be civilized about it. Vlastimil
Re: [gentoo-dev] Re: [RFC] Improve policy of stabilizations
Peter Volkov wrote: > В Сбт, 07/11/2009 в 12:49 -0800, Zac Medico пишет: >> Peter Volkov wrote: We could introduce "noarch" and "~noarch" KEYWORDS, add "noarch" to the default ACCEPT_KEYWORDS setting for all profiles, and instruct unstable users to add "~noarch" to ACCEPT_KEYWORDS. >>> Looks like this will not work for all noarch packages. Stardict >>> dictionary itself is noarch, but it RDEPENDS on stardict package which >>> is keyworded only on some archs. So we'll be forced either to keyword >>> stardict on all archs or we need to introduce some new way to work with >>> such situations. >> Keywording stardict on all archs doesn't sound reasonable, so I >> guess we just need to make sure that repoman will allow the noarch >> keyword even though the dependencies aren't keyworded on all >> architectures. > > But how will portage handle such situations? Will it allow installation > of noarch package and pull in *DEPEND only if possible, or will it > prohibit installation of noarch pkgs with unsatisfied deps? The latter > will make life harder for tools like eix, I guess. It should prohibit installation if there are unsatisfied deps. If you want "optional" dependencies then that will require a syntax extension with an EAPI bump. -- Thanks, Zac
