Re: [gentoo-user] glibc-2.24-r2 failed (install phase)

[tuxic]

On 06/15 05:56, tu...@posteo.de wrote:
> Hi,
> 
> While updateing glibc-2.24-r2 failed to install.
> 
> These are the last few lines of that process:
> 
> 
> al/execinfo.c.texi 
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/add.c.texi
>  
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/summary.texi
>  
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/pkgvers.texi
>  | sort;\
>  echo "@end direntry") > 
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi.new
> mv -f 
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi.new
>  
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi
> LANGUAGE=C LC_ALL=C makeinfo -P 
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/
>  
> --output=/var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/libc.info
>  libc.texinfo
> libc.texinfo:6: warning: @codequotebacktick should only appear at the 
> beginning of a line
> libc.texinfo:6: warning: @codequoteundirected should only appear at the 
> beginning of a line
> libc.texinfo:6: warning: @codequoteundirected should not appear in 
> @codequotebacktick
> libc.texinfo:6: expected @codequoteundirected on or off, not `on' require'
> libc.texinfo:6: superfluous argument to @codequotebacktick
> libc.texinfo:6: expected @codequotebacktick on or off, not `on' and ''
> make[2]: *** [Makefile:144: 
> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/libc.info]
>  Error 1
> make[2]: Leaving directory 
> '/var/tmp/portage/sys-libs/glibc-2.24-r2/work/glibc-2.24/manual'
> make[1]: *** [Makefile:215: manual/subdir_install] Error 2
> make[1]: Leaving directory 
> '/var/tmp/portage/sys-libs/glibc-2.24-r2/work/glibc-2.24'
> make: *** [Makefile:12: install] Error 2
>  * ERROR: sys-libs/glibc-2.24-r2::gentoo failed (install phase):
>  *   emake failed
>  * 
> 
> If anything more is wanted, I will be happy to post the wanted logs.
> But I want to prevent to logbomnb the mailinglist in beforehand... ;)
> 
> Cheers
> Meino
> 

Hi,

Is there any solution for this problem ?
Does anyone else has the same or similiar problems with this system
update?

Cheers
Meino

Re: [gentoo-user] Re: KDE 5 MTP failure

[Walter Dnes]

On Mon, Jun 19, 2017 at 01:19:58AM +0100, Peter Humphrey wrote
> On Sunday 18 Jun 2017 14:11:02 Walter Dnes wrote:
> 
> > An extra bit of debugging...
> > 
> > * switch to message log console (tty12) with {CTRL}{ALT}{F12}
> > 
> > * attach device
> > 
> > * note the output
> 
> USB device detected, using xhci-hcd.

  YIKES 

* Connect your device again

* As root, execute "fdisk -l"

* If you see an unexpected partion, e.g. /dev/sdb1, as root
  "mount -t auto /dev/sdb1 $HOME/nexus"

* "cd $HOME/nexus" and "ls -al".  Do you see anything?

  If that works, you've mounted it just like a USB key.  Make sure that
you "cd" away from the device, and "umount $HOME/nexus".

  Check you device's mounting options.  I've seen devices that have
options to mount as...
  - regular USB devices
  - MTP devices
  - PTP (direct photo-to-printer) devices

  Select the mount option most convenient for you.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Re: KDE 5 MTP failure

[Peter Humphrey]

On Sunday 18 Jun 2017 14:11:02 Walter Dnes wrote:
> On Sun, Jun 18, 2017 at 04:04:11PM +0100, Peter Humphrey wrote
> 
>   Did you "emerge sys-fs/fuse"?  The default /etc/fuse.conf is OK.

Yes, as I said.

>   "Troubleshooting" instructions in https://wiki.gentoo.org/wiki/MTP say
> that some devices must be turned on and have the active screen; i.e. do
> not allow screensaver/screenlock.

Yes, I've tried that.

> An extra bit of debugging...
> 
> * switch to message log console (tty12) with {CTRL}{ALT}{F12}
> 
> * attach device
> 
> * note the output

USB device detected, using xhci-hcd.

> * remove device
> 
> * note output

USB disconnect.

> * switch back to X (usually) {CTRL}{ALT}{F7}

 not necessary in a VT.

USB seems to be working okay, but either fuse or mtpfs isn't. I also tried 
the kio-mtp method, but that didn't show anything either.

-- 
Regards
Peter

Re: [gentoo-user] Re: KDE 5 MTP failure

[Walter Dnes]

On Sun, Jun 18, 2017 at 04:04:11PM +0100, Peter Humphrey wrote

  Did you "emerge sys-fs/fuse"?  The default /etc/fuse.conf is OK.

  "Troubleshooting" instructions in https://wiki.gentoo.org/wiki/MTP say
that some devices must be turned on and have the active screen; i.e. do
not allow screensaver/screenlock.  An extra bit of debugging...

* switch to message log console (tty12) with {CTRL}{ALT}{F12}

* attach device

* note the output

* remove device

* note output

* switch back to X (usually) {CTRL}{ALT}{F7}

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Re: KDE 5 MTP failure

[Peter Humphrey]

On Friday 16 Jun 2017 14:35:21 Walter Dnes wrote:
> On Fri, Jun 16, 2017 at 08:23:42AM -0700, Ian Zimmerman wrote
> 
> > On 2017-06-16 14:23, Grant Edwards wrote:
> > > This is not the first time I've seen somebody mention this "songs and
> > > pictures" stuff. I don't understand.  When I use mtpfs to mount my
> > > Android devices, a "file-level view" is exactly what I get: I see the
> > > device's root directory and everything underneath it the exact same
> > > way I would if it were a USB-storage device.
> > 
> > The last time I tried MTP was on Debian maybe 2 years ago or 3 years,
> > using the jmtpfs package.  IIRC this was what happened; yes, I could see
> > individual files, but only certain types, and only in certain
> > directories.
> 
>   That package is currently keyworded.  Use sys-fs/simple-mtpfs instead.
> It simply works; and it works simply.  From the command line

Thanks for the instructions, Walter.

> 1) create a working mount directory, e.g. $HOME/tablet

$ mkdir ~/nexus

> 2) attach smartphone/tablet/whatever to USB port
> 
> 3) sudo simple-mtpfs -o allow_other $HOME/tablet

$ sudo modprobe fuse
$ sudo simple-mtpfs -o allow_other ~/nexus
Device 0 (VID=18d1 and PID=4ee1) is a Google Inc (for LG 
Electronics/Samsung) Nexus 4/5/7/10 (MTP).
Android device detected, assigning default bug flags

(Actually it's a Nexus 6P phone.)

> 4) cd $HOME/tablet

$ ls -la
total 8.0K
drwxr-xr-x  2 prh prh 4.0K Jun 18 15:05 .
drwxr-xr-x 36 prh prh 4.0K Jun 18 15:05 ..

> 5) do whatever
> 
> 6) cd
> 
> 7) sudo fusermount -u $HOME/tablet

$ sudo fusermount -u nexus
fusermount: failed to unmount /home/prh/nexus: Invalid argument

...because it was never mounted - or if it was it was dropped immediately. 
Dmesg has no record of anything being mounted.

I've tried two cables and both USB-2 and USB-3 ports on this box, and I've 
tried fuse as a module and built in. I have the sys-fs/fuse package 
installed.

I also tried an older Nexus-7 with the same result, but when I tried a 
Samsung Galaxy Tab S I got this (as root):

# simple-mtpfs -o allow_other /home/prh/nexus
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:3

Well, Samsung do like to do their own thing.

What else might I be missing? I'm not so bothered about the two tablets, but 
it would be good to be able to connect the phone and play with it.

> 8) dettach smartphone/tablet/whatever from USB port

-- 
Regards
Peter

Re: [gentoo-user] texlive-core dependency conflict

[Alexander Kapshuk]

On Sun, Jun 18, 2017 at 3:09 AM, Lasse Pouru
 wrote:
> Any way to get around this? I've already tried removing both the cjk and
> xetex USE flags, running emerge -c, unmerging and remerging texlive-core
> etc. I do actually want both the cjk and the xetex packages installed,
> and this seems to be mostly an aesthetic issue since the version of
> texlive-core I have installed is the latest (2016-r5).
>
> I guess I'm really just wondering if my LaTeX installation is messed up
> somehow and if there's something I could do to prevent errors like this
> in the future.
>
> Here's the error message:
>
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
>
> app-text/texlive-core:0
>
>   (app-text/texlive-core-2016-r5:0/0::gentoo, ebuild scheduled for
>   merge) conflicts with
> >=app-text/texlive-core-2010[cjk] required by
>  ^^^
>   (dev-texlive/texlive-langcjk-2016:0/0::gentoo, installed)
>
> >=app-text/texlive-core-2010[xetex] required by
>  ^
>   (dev-texlive/texlive-xetex-2016:0/0::gentoo, installed)
>
> - Lasse
>

Please search this mailing list's archive. This issue has recently
been discussed and a few solutions suggested.

[gentoo-user] Re: ntp Vs openntp vis a vis Plasma desktop

[Michael Palimaka]

On 06/18/2017 08:34 PM, Tom H wrote:
> On Sat, Jun 17, 2017 at 1:46 PM, Walter Dnes  wrote:
>> On Fri, Jun 16, 2017 at 09:44:27PM +1000, Michael Palimaka wrote
>>>
>>> Someone raised the issue that the "time server" option in the date
>>> and time applet was greyed out on their system. It turns out that
>>> this occurs if neither ntpdate nor rdate binaries are present, so I
>>> added the dep. There's been some pushback on this so maybe it'll be
>>> reverted or maybe not. It's being tracked in bug #621754 for anyone
>>> who wants to chime in.
>>
>> 1) If you don't have a time server, you don't have a time server. Why
>> is that a problem? Remember that Gentoo is about choice. An "ewarn"
>> message might be appropriate about "missing functionality", but that's
>> about it.
> 
> Given that the binaries that it looks for are ntpdate and rdate, it's
> about having an ntp client. It's strange that chronyd isn't one of
> these binaries, especially since, IIRC, ntpdate and rdate are
> deprecated.
> 
> 

Unfortunately upstream doesn't care about anything except systemd. It's
possible a patch adding support for other time clients might be
accepted, but looking at the commit adding systemd support[1], I wonder
how long it is until "legacy" support for this sort of thing is dropped
entirely.

1:
https://cgit.kde.org/plasma-desktop.git/commit/kcms/dateandtime/dtime.cpp?id=b6ae01ca8ea776c97cc57836401ca9696e2529e8

Re: [gentoo-user] Re: ntp Vs openntp vis a vis Plasma desktop

[Tom H]

On Sat, Jun 17, 2017 at 1:46 PM, Walter Dnes  wrote:
> On Fri, Jun 16, 2017 at 09:44:27PM +1000, Michael Palimaka wrote
>>
>> Someone raised the issue that the "time server" option in the date
>> and time applet was greyed out on their system. It turns out that
>> this occurs if neither ntpdate nor rdate binaries are present, so I
>> added the dep. There's been some pushback on this so maybe it'll be
>> reverted or maybe not. It's being tracked in bug #621754 for anyone
>> who wants to chime in.
>
> 1) If you don't have a time server, you don't have a time server. Why
> is that a problem? Remember that Gentoo is about choice. An "ewarn"
> message might be appropriate about "missing functionality", but that's
> about it.

Given that the binaries that it looks for are ntpdate and rdate, it's
about having an ntp client. It's strange that chronyd isn't one of
these binaries, especially since, IIRC, ntpdate and rdate are
deprecated.