[gentoo-dev] Last rites: sci-mathematics/xmds

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only, bump required and very involved buildsystem,
# has QA issues, bug #598840. Removal in 30 days.
sci-mathematics/xmds


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Last rites: sci-mathematics/factmsieve

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only, upstream HOMEPAGE gone.
# Removal in 30 days.
sci-mathematics/factmsieve


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Last rites: sci-mathematics/snns

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only, upstream dead, last release in 2011.
# file collisions with sci-chemistry/tinker, bug #597702.
# Removal in 30 days.
sci-mathematics/snns


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Last rites: sci-mathematics/Macaulay2

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only, bump required and very involved and messy
# buildsystem, tons of QA issues.
# Bug #345233, #459640, #474782, #474784, #474788, #474790, #474792,
# #620942, #631876, #671130. Removal in 30 days.
sci-mathematics/Macaulay2


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Last rites: sci-mathematics/p9m4

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only, last release in 2008. Removal in 30 days.
sci-mathematics/p9m4


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Last rites: sci-mathematics/nusmv

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only, last release in 2015, lots of QA issues.
# Bug #343743, #347928, #451394, #547714, #623756, #697562.
# Removal in 30 days.
sci-mathematics/nusmv




[gentoo-dev] Last rites: sci-mathematics/mlpy

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# Yet another NIH machine learning package in python. Last release in
# 2012, no revdeps, py2 only. Removal in 30 days.
sci-mathematics/mlpy




[gentoo-dev] Last rites: sci-mathematics/lybniz

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only, upstream HOMEPAGE gone, last release in 2007.
# Removal in 30 days.
sci-mathematics/lybniz


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Last rites: sci-mathematics/pymc

2019-12-07 Thread David Seifert
# David Seifert  (2019-12-08)
# No revdeps, py2 only (the py3 targets don't work properly), last
# release in 2015. Use sci-mathematics/pymc3 as modern replacement.
# Removal in 30 days.
sci-mathematics/pymc


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] Last rites: x11-misc/calise

2019-12-07 Thread Andreas Sturmlechner
# Andreas Sturmlechner  (2019-12-07)
# Runtime errors/segfaults, ancient, depends on py27.
# Bug 590986, removal in 30 days.
x11-misc/calise


signature.asc
Description: This is a digitally signed message part.


[gentoo-dev] Last rites: app-text/wklej (with immediate removal)

2019-12-07 Thread aidecoe
Service doesn't work, nobody complained, nobody is using it anymore.

-- aidecoe


signature.asc
Description: PGP signature


[gentoo-dev] Last rites: sci-astronomy/casacore

2019-12-07 Thread Andreas Sturmlechner
# Andreas Sturmlechner  (2019-12-07)
# Fails to build against dev-libs/boost-1.71.0, depends on py27.
# Bug 624222, removal in 30 days.
sci-astronomy/casacore


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.

2019-12-07 Thread Ulrich Mueller
> On Sat, 07 Dec 2019, Thomas Deutschmann wrote:

> just wondering if you have seen https://bugs.gentoo.org/532264#c24.
> If this is still valid, is your change really needed?

I have. IIUC it is a special case for one ebuild and cannot be
generalised.

Ulrich


signature.asc
Description: PGP signature


Re: [gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.

2019-12-07 Thread Thomas Deutschmann
Hi,

just wondering if you have seen https://bugs.gentoo.org/532264#c24. If
this is still valid, is your change really needed?


-- 
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] [PATCH] package.deprecated: Create initial template

2019-12-07 Thread Joonas Niilola

>>> repoman would be more useful for this
>> I wouldn't stop pkgcheck from supporting this, but repoman should as
>> well.
>>
>>
>>
> of course, that's what i meant ;)



Looks like it does now,

https://bugs.gentoo.org/702100

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bb5d7b074164ceae5f03ddfb40881a7cc6f12dd

(didn't see a reply in this thread about this update)




signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] [PATCH] cargo.eclass: use verbose cargo invocations

2019-12-07 Thread Kent Fredric
On Fri,  6 Dec 2019 12:09:31 -0800
Georgy Yakovlev  wrote:

> Default output just prints crate name.
> With -vv we can see all cargo options and rustc args.

On the overlay with rust-crate.eclass, I've not found the verbose
output very helpful for anything.

I would probably ask for a knob to tweak that disabled this.



...

ECARGO_OPTS=(
   -j $(makeopts_jobs)
   "${ECARGO_OPTS[@]}"
)
if [ "${ECARGO_VERBOSE:-1}" == 1 ]; then
  ECARGO_OPTS+=( -vv )
fi

...

cargo build "${ECARGO_OPTS[@]}" ... 


or something along those lines.

I've also (often) had to invoke stuff like:

src_test() {
   RUSTFLAGS="${RUSTFLAGS} --cap-lints warn" rust-crate_src_test
}

Because well, upstream.

But I'm not entirely fond of that syntax.


pgpDgKtQkdfkU.pgp
Description: OpenPGP digital signature


Re: [gentoo-dev] [PATCH] package.deprecated: Create initial template

2019-12-07 Thread Kent Fredric
On Fri, 06 Dec 2019 10:03:23 +0100
Alexis Ballier  wrote:

> (*) and force the use of some handy git options like only commit paths
> starting from cwd even if other files had been git added, which i never
> remember what is the git cli option for this

There isn't so much a CLI option, more, there's a parameter that "git
commit" takes which allows you to enumerate which paths to commit.

So:

  git commit

Commits everything staged.

  git commit .

Commits only CWD

But, with one important caveat:

  git commit

Will only commit changes previously added with "git add" or whatever to
the index.

  git commit .

Will commit *any* changes to anything in "." as long as they're
"tracked" by git.

But this is what repoman does anyway ;)

The doc line for this in "git help commit" is:

   3. by listing files as arguments to the commit command (without
   --interactive or --patch switch), in which case the commit will
   ignore changes staged in the index, and instead record the current
   content of the listed files (which must already be known to Git);



pgpBfsc68hFk_.pgp
Description: OpenPGP digital signature


Re: [gentoo-dev] [PATCH] package.deprecated: Create initial template

2019-12-07 Thread Kent Fredric
On Fri, 6 Dec 2019 12:58:47 -0500
Michael Orlitzky  wrote:

>   $ git rebase -i 
> 
> to do a rebase starting at the one you'd like to fix.


Or, if you know the hash of the faulty commit, you can do:

$ git rebase -i DEADBEEF^1

( 1st parent of commit DEADBEEF )

Which absolves you from needing to determine the parent commit manually.

I believe 

$ git rebase -i DEADBEEF~24

Is also valid for "24th ancestor of commit DEADBEEF"



pgpC7qvoUt8UH.pgp
Description: OpenPGP digital signature


[gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.

2019-12-07 Thread Ulrich Müller
The eclass failed to remount a read-only mounted /boot, because package
collision sanity checks in recent Portage versions prevented it from
reaching pkg_preinst() at all. Furthermore, with the "mount-sandbox"
feature enabled, the mount won't be propagated past pkg_preinst() and
installed files would end up under the (shadowed) mount point.

Therefore don't even attempt to mount /boot ourselves, but error out
if it isn't mounted read/write and ask the user to mount /boot.

Also clean up and simplify. (For example, awk is a grown-up program
which doesn't need any help from egrep or sed. :-)

Closes: https://bugs.gentoo.org/532264
See-also: https://bugs.gentoo.org/274130#c5
Signed-off-by: Ulrich Müller 
---
v3: Exit awk commands on first match.

v4: Added die statements after awk commands
Fixed typo in mount-boot_is_disabled function documentation
Reverted renaming of I_KNOW_WHAT_I_AM_DOING variable

 eclass/mount-boot.eclass | 144 +--
 1 file changed, 48 insertions(+), 96 deletions(-)

diff --git a/eclass/mount-boot.eclass b/eclass/mount-boot.eclass
index 938df6732f43..ca27aca7efbd 100644
--- a/eclass/mount-boot.eclass
+++ b/eclass/mount-boot.eclass
@@ -1,156 +1,108 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 # @ECLASS: mount-boot.eclass
 # @MAINTAINER:
 # base-sys...@gentoo.org
 # @BLURB: functions for packages that install files into /boot
 # @DESCRIPTION:
 # This eclass is really only useful for bootloaders.
 #
 # If the live system has a separate /boot partition configured, then this
 # function tries to ensure that it's mounted in rw mode, exiting with an
-# error if it can't. It does nothing if /boot isn't a separate partition.
+# error if it can't.  It does nothing if /boot isn't a separate partition.
+
+case ${EAPI:-0} in
+   4|5|6|7) ;;
+   *) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
+esac
 
 EXPORT_FUNCTIONS pkg_pretend pkg_preinst pkg_postinst pkg_prerm pkg_postrm
 
-# @FUNCTION: mount-boot_disabled
+# @FUNCTION: mount-boot_is_disabled
 # @INTERNAL
 # @DESCRIPTION:
 # Detect whether the current environment/build settings are such that we do not
 # want to mess with any mounts.
 mount-boot_is_disabled() {
-   # Since this eclass only deals with /boot, skip things when ROOT is 
active.
-   if [[ "${ROOT:-/}" != "/" ]] ; then
+   # Since this eclass only deals with /boot, skip things when EROOT is 
active.
+   if [[ ${EROOT:-/} != / ]] ; then
return 0
fi
 
# If we're only building a package, then there's no need to check 
things.
-   if [[ "${MERGE_TYPE}" == "buildonly" ]] ; then
+   if [[ ${MERGE_TYPE} == buildonly ]] ; then
return 0
fi
 
# The user wants us to leave things be.
if [[ -n ${DONT_MOUNT_BOOT} ]] ; then
return 0
fi
 
# OK, we want to handle things ourselves.
return 1
 }
 
 # @FUNCTION: mount-boot_check_status
 # @INTERNAL
 # @DESCRIPTION:
-# Figure out what kind of work we need to do in order to have /boot be sane.
-# Return values are:
-# 0 - Do nothing at all!
-# 1 - It's mounted, but is currently ro, so need to remount rw.
-# 2 - It's not mounted, so need to mount it rw.
+# Check if /boot is sane, i.e., mounted read/write if on a separate
+# partition.  Die if conditions are not fulfilled.
 mount-boot_check_status() {
# Get out fast if possible.
-   mount-boot_is_disabled && return 0
+   mount-boot_is_disabled && return
 
# note that /dev/BOOT is in the Gentoo default /etc/fstab file
-   local fstabstate=$(awk '!/^#|^[[:blank:]]+#|^\/dev\/BOOT/ {print $2}' 
/etc/fstab | egrep "^/boot$" )
-   local procstate=$(awk '$2 ~ /^\/boot$/ {print $2}' /proc/mounts)
-   local proc_ro=$(awk '{ print $2 " ," $4 "," }' /proc/mounts | sed -n 
'/^\/boot .*,ro,/p')
-
-   if [ -n "${fstabstate}" ] && [ -n "${procstate}" ] ; then
-   if [ -n "${proc_ro}" ] ; then
-   echo
-   einfo "Your boot partition, detected as being mounted 
at /boot, is read-only."
-   einfo "It will be remounted in read-write mode 
temporarily."
-   return 1
-   else
-   echo
-   einfo "Your boot partition was detected as being 
mounted at /boot."
-   einfo "Files will be installed there for ${PN} to 
function correctly."
-   return 0
-   fi
-   elif [ -n "${fstabstate}" ] && [ -z "${procstate}" ] ; then
-   echo
-   einfo "Your boot partition was not mounted at /boot, so it will 
be automounted for you."
-   einfo "Files will be installed there for ${PN} to function 
correctly."
-   return 2
-   else
-   echo
+   local 

Re: [gentoo-dev] [PATCH v3] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.

2019-12-07 Thread Sergei Trofimovich
On Sat, 07 Dec 2019 06:44:21 +0100
Ulrich Mueller  wrote:

> > On Sat, 07 Dec 2019, Sergei Trofimovich wrote:  
> 
> >># The user wants us to leave things be.
> >> -  if [[ -n ${DONT_MOUNT_BOOT} ]] ; then
> >> +  if [[ -n ${I_KNOW_WHAT_I_AM_DOING} ]] ; then
> >>return 0
> >>fi  
> 
> > The rest of patch looks ok but I find I_KNOW_WHAT_I_AM_DOING
> > proliferation worrying. Having enough eclasses guard things on it I
> > don't really know what I am doing :)  
> 
> > For example developer profile sets it on by default and disables perl
> > error checks. I don't think it's intentional.  
> 
> Oh, I forgot that it is set globally in the developer profile (and I
> think that's a stupid idea). Indeed we should use a different variable
> then.
> 
> > I suggest giving this variable a unique specific name.  
> 
> Would it be acceptable to leave DONT_MOUNT_BOOT in place? It would have
> the advantage that users won't have to update their config.

Sounds good.

> > And phase out ${I_KNOW_WHAT_I_AM_DOING} uses from tree completely.  
> 
> That's a separate discussion.

Sure. As long as we don't add extra uses.


-- 

  Sergei


pgpYQCLmDsRHx.pgp
Description: Цифровая подпись OpenPGP


Re: [gentoo-dev] [PATCH] cargo.eclass: use verbose cargo invocations

2019-12-07 Thread Sergei Trofimovich
On Fri, 06 Dec 2019 16:16:32 -0800
Georgy Yakovlev  wrote:

> On Friday, December 6, 2019 3:44:38 PM PST Sergei Trofimovich wrote:
> > On Fri,  6 Dec 2019 12:09:31 -0800
> > 
> > Georgy Yakovlev  wrote:  
> > > Default output just prints crate name.
> > > With -vv we can see all cargo options and rustc args.
> > > 
> > > Signed-off-by: Georgy Yakovlev 
> > > ---  
> > 
> > Looks good!
> > 
> > I had to do an equivalent locally at least a few times.  
> Pushed!
> > 
> > While at it I also suggest adding equivalent of
> > econf's/emake's ${EXTRA_ECONF} and ${EXTRA_EMAKE}
> > to allow users to inject arbitrary stuff. For example
> > to sneak in '-Z' options globally.
> > 
> > Say, ${CARGO_BUILD_EXTRA},  ${CARGO_INSTALL_EXTRA},
> > ${CARGO_TEST_EXTRA}.
> >   
> 
> Yeah, it's on my to-do list for this eclass.
> 1 question tho, should it come after "$@" or before? Do you use it?
> I know cargo can be picky about order and some ebuilds rely on passing params 
> in phase funcs.

I don't use it frequently for carge.eclass but use it extensively for
./configure and haskell-cabal.eclass. I'd say variables are designed to
override everything else (eclass defaults and ebuild values) and thus
should come after "$@":
econf() { ... "$@" "${EXTRA_ECONF[@]}" }
${MAKE:-make} ${MAKEOPTS} "$@" ${EXTRA_EMAKE}

-- 

  Sergei



Re: [gentoo-dev] [PATCH] cargo.eclass: use verbose cargo invocations

2019-12-07 Thread Haelwenn (lanodan) Monnier
[2019-12-06 16:16:32-0800] Georgy Yakovlev:
> On Friday, December 6, 2019 3:44:38 PM PST Sergei Trofimovich wrote:
> > On Fri,  6 Dec 2019 12:09:31 -0800
> > Georgy Yakovlev  wrote:
> > > Default output just prints crate name.
> > > With -vv we can see all cargo options and rustc args.
> > > 
> > > Signed-off-by: Georgy Yakovlev 
> > > ---
> > 
> > While at it I also suggest adding equivalent of
> > econf's/emake's ${EXTRA_ECONF} and ${EXTRA_EMAKE}
> > to allow users to inject arbitrary stuff. For example
> > to sneak in '-Z' options globally.
> > 
> > Say, ${CARGO_BUILD_EXTRA},  ${CARGO_INSTALL_EXTRA},
> > ${CARGO_TEST_EXTRA}.
> > 
> 
> Yeah, it's on my to-do list for this eclass.
> 1 question tho, should it come after "$@" or before? Do you use it?
> I know cargo can be picky about order and some ebuilds rely on passing params 
> in phase funcs.

I think it should go after `cargo {build,install,test}` and before any 
non-option argument, similar to how POSIX getopt(3) behaves (but that GNU 
breaks without setting POSIXLY_CORRECT=1).



Re: [gentoo-dev] unsanctioned python 2.7 crusade

2019-12-07 Thread Kent Fredric
On Fri, 06 Dec 2019 21:10:12 +0100
Andreas Sturmlechner  wrote:

> Calculating dependencies... done!
> 
> Total: 0 packages, Size of downloads: 0 KiB
> 
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
> 
> dev-python/sphinx:0
> 
>   (dev-python/sphinx-2.0.1:0/0::gentoo, ebuild scheduled for merge)
> conflicts with


This IME is more an argument that "portage is shit", not so much an
argument that "we need to nuke old pythons"

If this problem was a valid impetus for this removal, we'd have banned
PYTHON_TARGETS entirely a long time ago, and we'd have culled literally
everything that doesn't work on the latest python.

But I don't favour that outcome at all.

I'd rather favour an outcome where portage responds to this scenario in
a useful way that makes coherent sense to users.





pgpd0lZq4Ejef.pgp
Description: OpenPGP digital signature