[gentoo-user] Re: SMTP on Kmail-4.14.10 does not work without kde-apps/kwalletd-16.04.3-r1

[Jörg Schaible]

Mick wrote:

> On Tuesday 06 Jun 2017 16:35:40 you wrote:
>> Hi All,
>> 
>> I've updated a number of kde (plasma) packages, including kde-
>> frameworks/kwallet-5.34.0-r1.  A depclean action wanted to remove
>> kde-apps/kwalletd-16.04.3-r1 and I let it do its tha'ng.
>> 
>> Following a new login I discovered that *every* time I wanted to send a
>> message I was being asked for the SMTP password.  For some users with 6
>> or
>> more email accounts this soon became tiresome.  The pop up advises that
>> the password should be saved in kwallet and offers the choice to save it
>> in ...
>> the configuration file!  It also advises that although it will be
>> obfuscated
>> it will not be safe in the configuration file.  There are two buttons,
>> one to save the password in the configuration file and another to not
>> save it (at all).
>> 
>> So to retain what sanity I may have left, I had to re-install kde-
>> apps/kwalletd-16.04.3-r1, which appears to be able to manage SMTP
>> passwords without asking each time the user.
>> 
>> Have you noticed the same?  Is there a fix or workaround for this?
> 
> Just to clarify, there doesn't seem to be a problem with IMAP4 passwords,
> only with SMTP.
> 
> When updating to kde-frameworks/kwallet-5.34.0-r1 I noticed this elog
> message, which implies I should no longer need the old kwalletd4:
> 
> "LOG: postinst
> Starting with 5.34.0-r1, kwallet is able to serve applications
> that still require old kwalletd4. After migration has finished,
> kde-apps/kwalletd can be removed."
> 
> So, do I have to wait for Kmail:4 to be updated to Kmail:5 before I give
> up on kwalletd4 despite the above message?

I had the same problem. But event if kwalletd is installed, it was no longer 
started. After some time I remembered that I changed the password for my 
mail account. However, that was after the "automated conversion" of the 
wallet from kwallet 4 to 5. So, when I updated my credentials in KMail at 
that time, the old wallet was updated. However, the latest update of kwallet 
seems to take over the APIs of kwallet 4 and redirect them to kwallet 5 
implementation. But that wallet still kept my old password of my mail 
account that was valid at conversion time. All I had to do was to reenter my 
new password in the KMail setup for this mail account.

Note, you should install knotify:4 if you want notifications about failed 
mail delivery from KMail. That was removed for me in an dependency clean-up, 
because I had no entry for it in world.

Cheers,
Jörg

[gentoo-user] Ended up buying Brother HL-3140CW [WAS: Samsung Xpress C430W with Gentoo]

[Mick]

On Monday 05 Jun 2017 13:18:29 Mick wrote:
> Hi All,
> 
> I'm about to buy a new printer but before I jump in with both feet, do you
> have any experience of getting the above laser printer to work with Gentoo?
> 
> Samsung provide a Unified Linux Driver here:
> 
> http://downloadcenter.samsung.com/content/DR/201507/20150708141746407/ULD_v1
> .00.35.tar.gz
> 
> and there is also the Samsung Printer Language driver in portage:
> 
> $ eix -l splix
> * net-print/splix
>  Available versions:
> 2.0.0_p20111206   [+jbig]
>~2.0.0_p20130826   [+jbig]
>  Homepage:http://splix.sourceforge.net/
>  Description: A set of CUPS printer drivers for SPL (Samsung
> Printer Language) printers
> 
> but I don't know if the C430W will work with the splix driver - it is not
> listed here:
> 
> http://splix.sourceforge.net/


At the end I decided to buy a brother laser printer.  I used the brother-
overlay and installed net-print/brother-hl3140cw-bin, which works fine so far.
-- 
Regards,
Mick

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

Re: [gentoo-user] how to get started with automated update world

[Mick]

On Wednesday 07 Jun 2017 16:35:02 Rich Freeman wrote:
> On Wed, Jun 7, 2017 at 4:26 PM, Harry Putnam  wrote:
> > Maybe some of you can steer me toward some documentation or tools etc
> > that help a gentoo user to do automated updates.
> 
> Unmonitored updates sounds like a recipe for problems.  However, I do
> have a cron job that does a --sync and then builds binary packages for
> everything, and it emails me the emerge -pu output.  Then if I'm happy
> with it I can just install the binary packages.
> 
> To build everything (this could be cleaned up a bit or parallelized,
> and I stole it off of the lists):
> #!/bin/sh
> 
> LIST=$(mktemp);
> 
> emerge -puD --changed-use --color=n --columns --quiet=y --changed-deps
> --with-bdeps=n --backtrack=100 world | awk '{print $2}' > ${LIST};
> 
> for PACKAGE in $(cat ${LIST});
> do
>   printf "Building binary package for ${PACKAGE}... "
>   emerge -uN --quiet-build --quiet=y --buildpkgonly ${PACKAGE};
>   if [[ $? -eq 0 ]];
>   then
> echo "ok";
>   else
> echo "failed";
>   fi
> done
> 
> To install the packages you built:
> ionice -c 3 nice -n 15 emerge -uDkv --changed-use --keep-going
> --with-bdeps=n --changed-deps --binpkg-changed-deps=y --backtrack=100
> world
> 
> Note that binary packages can only be built one level of dependencies
> deep, so if you're doing something like a kde update you'll still end
> up doing a LOT of building.  Then again, it often takes care of some
> pretty big first-level dependencies like kdelibs.  Typically over 80%
> of my package installs end up being from binaries, and often the stuff
> that isn't is small.  If somebody triggers a rebuild of chromium then
> that is a different story, but most chromium updates get built
> overnight.

I have stayed away from automating updates because every now and then there 
are profile changes, which add or remove USE flags.  I prefer to consider 
these, rather than have them applied automatically.  I may also decide to hold 
back some package updates for a while.
-- 
Regards,
Mick

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

Re: [gentoo-user] how to get started with automated update world

[Rich Freeman]

On Wed, Jun 7, 2017 at 4:26 PM, Harry Putnam  wrote:
>
> Maybe some of you can steer me toward some documentation or tools etc
> that help a gentoo user to do automated updates.
>

Unmonitored updates sounds like a recipe for problems.  However, I do
have a cron job that does a --sync and then builds binary packages for
everything, and it emails me the emerge -pu output.  Then if I'm happy
with it I can just install the binary packages.

To build everything (this could be cleaned up a bit or parallelized,
and I stole it off of the lists):
#!/bin/sh

LIST=$(mktemp);

emerge -puD --changed-use --color=n --columns --quiet=y --changed-deps
--with-bdeps=n --backtrack=100 world | awk '{print $2}' > ${LIST};

for PACKAGE in $(cat ${LIST});
do
  printf "Building binary package for ${PACKAGE}... "
  emerge -uN --quiet-build --quiet=y --buildpkgonly ${PACKAGE};
  if [[ $? -eq 0 ]];
  then
echo "ok";
  else
echo "failed";
  fi
done

To install the packages you built:
ionice -c 3 nice -n 15 emerge -uDkv --changed-use --keep-going
--with-bdeps=n --changed-deps --binpkg-changed-deps=y --backtrack=100
world

Note that binary packages can only be built one level of dependencies
deep, so if you're doing something like a kde update you'll still end
up doing a LOT of building.  Then again, it often takes care of some
pretty big first-level dependencies like kdelibs.  Typically over 80%
of my package installs end up being from binaries, and often the stuff
that isn't is small.  If somebody triggers a rebuild of chromium then
that is a different story, but most chromium updates get built
overnight.


-- 
Rich

[gentoo-user] how to get started with automated update world

[Harry Putnam]

I imagine automating updates  has come up a few times here... I
personally never have noticed it.. but haven't followed the group as
close as I once did, and never really considered automating updates.

Is that something better left to experts?  Or are there some tried and
true tools available that mean a semi-dense gentoo practitioner like
myself might be able to get it going?

Maybe some of you can steer me toward some documentation or tools etc
that help a gentoo user to do automated updates.