On 12 December 2017 at 22:46, Daniel Campbell wrote:
>
> The following packages are in need of a maintainer:
>
> dev-util/astyle
> net-im/toxic
> x11-misc/alock
> x11-misc/ktsuss
> x11-misc/spacefm
Hi!
I've been interested in getting more involved with Gentoo - would
package maintenance be a goo
On 2017-12-12 19:24, Rich Freeman wrote:
> As far as I'm aware the standing policy already exists that
> maintainers can stabilize their own packages on amd64.
That's right but keep in mind that nevertheless you need a stable
system. Marking a package stable because it works on your ~arch box you
Hi Thomas,
> I've been interested in getting more involved with Gentoo - would
> package maintenance be a good place to start?
You can fix bugs for many packages, but you should only assign your self
to a package, if you want to take care for bug reports in a long term.
I suggest to make small fi
On Wed, Dec 13, 2017 at 01:22:04PM +0100, Thomas Deutschmann wrote:
> On 2017-12-12 19:24, Rich Freeman wrote:
> > As far as I'm aware the standing policy already exists that
> > maintainers can stabilize their own packages on amd64.
>
> That's right but keep in mind that nevertheless you need a s
> In my discussions with other developers, I've found that this is the
>
biggest concern. Most devs are runnning ~amd64, so they don't feel that
>
they can mark things stable.
W
hat about running a stable chroot? Are there any tools that can be used
to automate this process?
On Wed, Dec
On 2017-12-13 13:20, Lucas Ramage wrote:
> > In my discussions with other developers, I've found that this is the
> >
> biggest concern. Most devs are runnning ~amd64, so they don't feel that
> >
> they can mark things stable.
>
> W
> hat about running a stable chroot? Are there any tools
I see, well I can setup buildbot to do that. Is there some place in
particular that I should send my test results?
On Wed, Dec 13, 2017 at 1:28 PM, Aaron W. Swenson
wrote:
> On 2017-12-13 13:20, Lucas Ramage wrote:
> > > In my discussions with other developers, I've found that this is the
> >
On 2017-12-13 18:51, William Hubbs wrote:
> In theory, this is correct. However, when maintainers don't stabilize
> packages and no one else does either, our stable tree suffers.
I agree but we have to pay attention that we don't stabilize packages at
all costs because otherwise they would never g
Hello,
I'm using oracle jdk as default jvm, but when I review java-config
result after setting oracle-jdk-bin as prefered jvm, javaws continues to
start icedtea version.
Analysing the script /usr/libexec/eselect-java/run-java-tool.bash I
realised that itweb-javaws is hardcoded:
> if [ "${tool}"
On Wed, 13 Dec 2017 22:25:51 +
Samuel Bernardo wrote:
> I'm using oracle jdk as default jvm, but when I review java-config
> result after setting oracle-jdk-bin as prefered jvm, javaws continues to
> start icedtea version.
Disable the webstart flag against icedtea(-bin) and unmerge
dev-java/
On Wed, 13 Dec 2017 21:58:05 +0100
Thomas Deutschmann wrote:
> b) Because not all devs care about stable Gentoo, I would recommend
> auto-stabilization: I.e. if a package is in the repository for x days
> build bot would try to build the package and mark the package stable
> if everything passes.
11 matches
Mail list logo
