public inbox for gentoo-binhost-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: binhost@demeter.amd64.dev.gentoo.org
To: gentoo-binhost-autobuilds@lists.gentoo.org
Subject: [gentoo-binhost-autobuilds] [binhost amd64-default-17.1] Update succeeded
Date: Sat, 31 Dec 2022 23:38:07 +0000 (UTC)	[thread overview]
Message-ID: <20221231233807.4F3F926808B@demeter.amd64.dev.gentoo.org> (raw)

Binhost amd64-default-17.1 update succeeded


 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'app-alternatives/sh-0' merged despite file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.
 * Messages for package app-alternatives/awk-4:
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/bin/awk
 * 	/bin/awk
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'app-alternatives/awk-4' merged despite file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.
 * Messages for package dev-lang/perl-5.36.0-r1:
 * UPDATE THE PERL MODULES:
 * After updating dev-lang/perl the installed Perl modules
 * have to be re-installed. In most cases, this is done automatically
 * by the package manager, but subsequent steps are still recommended
 * to ensure system consistency.
 * 
 * You should start with a depclean to remove any unused perl dependencies
 * that may confuse portage in future. Regular depcleans are also encouraged
 * as part of your regular update cycle, as that will keep perl upgrades working.
 * Recommended: emerge --depclean -va
 * 
 * You should then call perl-cleaner to clean up any old files and trigger any
 * remaining rebuilds portage may have missed.
 * Use: perl-cleaner --all
 * Messages for package sys-libs/pam-1.5.2-r3:
 * Some software with pre-loaded PAM libraries might experience
 * warnings or failures related to missing symbols and/or versions
 * after any update. While unfortunate this is a limit of the
 * implementation of PAM and the software, and it requires you to
 * restart the software manually after the update.
 * 
 * You can get a list of such software running a command like
 *   lsof / | grep -E -i 'del.*libpam\.so'
 * 
 * Alternatively, simply reboot your system.
 * Messages for package app-alternatives/bc-0:
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/bin/bc
 * 	/usr/bin/dc
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'app-alternatives/bc-0' merged despite file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.
 * Messages for package dev-lang/rust-1.65.0:
 * Rust installs a helper script for calling GDB and LLDB,
 * for your convenience it is installed under /usr/bin/rust-{gdb,lldb}-1.65.0.
 * Messages for package www-servers/apache-2.4.54-r6:
 * 
 * Selected default MPM: prefork
 * 
 * Please note that you need SysV IPC support in your kernel.
 * Make sure CONFIG_SYSVIPC=y is set.
 * 
 * Attention: cgi and cgid modules are now handled via APACHE2_MODULES flags
 * in make.conf. Make sure to enable those in order to compile them.
 * In general, you should use 'cgid' with threaded MPMs and 'cgi' otherwise.
 * Messages for package dev-python/lxml-4.9.1:
 * Install additional packages for optional runtime features:
 *   dev-python/beautifulsoup4 for Support for BeautifulSoup as a parser backend
 * Messages for package app-text/asciidoc-10.2.0:
 * Install additional packages for optional runtime features:
 *   media-sound/lilypond and virtual/imagemagick-tools for music filter support
 *   dev-util/source-highlight and dev-python/pygments and app-text/highlight for source filter support
 *   media-gfx/graphviz for graphviz filter support
 * Messages for package dev-python/jinja-3.1.2:
 * For i18n support, please emerge dev-python/Babel.
 * Messages for package dev-libs/glib-2.74.4:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Messages for package app-alternatives/lex-0-r1:
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/bin/lex
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'app-alternatives/lex-0-r1' merged despite file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.
 * Messages for package app-alternatives/yacc-1-r2:
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/bin/yacc
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'app-alternatives/yacc-1-r2' merged despite file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.
 * Messages for package sys-devel/llvm-15.0.6:
 * You can find additional opt-viewer utility scripts in:
 *   /usr/lib/llvm/15/share/opt-viewer
 * To use these scripts, you will need Python along with the following
 * packages:
 *   dev-python/pygments (for opt-viewer)
 *   dev-python/pyyaml (for all of them)
 * Messages for package sys-devel/clang-15.0.6:
 * You can find additional utility scripts in:
 *   /usr/lib/llvm/15/share/clang
 * Some of them are vim integration scripts (with instructions inside).
 * The run-clang-tidy.py script requires the following additional package:
 *   dev-python/pyyaml
 * Messages for package net-fs/cifs-utils-6.15-r1:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * setuid use flag was dropped due to multiple security implications
 * such as CVE-2009-2948, CVE-2011-3585 and CVE-2012-1586
 * You are free to set setuid flags by yourself
 * Messages for package app-misc/tracker-3.4.2:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Messages for package perl-core/Encode-3.120.0:
 * Unable to establish //usr/bin/encguess symlink
 * Unable to establish //usr/share/man/man1/encguess.1.bz2 symlink
 * Messages for package perl-core/CPAN-2.290.0-r1:
 * Removing dead symlink //usr/bin/cpan-mirrors
 * Removing dead symlink //usr/share/man/man1/cpan-mirrors.1.bz2
 * Messages for package dev-vcs/git-2.38.2:
 * Some scripts require additional dependencies:
 *   dev-util/quilt for git-quiltimport
 * Messages for package sys-apps/portage-3.0.41-r2:
 * Unable to find kernel sources at /usr/src/linux
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Messages for package media-sound/pulseaudio-daemon-16.1-r3:
 * You have enabled bluetooth USE flag for pulseaudio. Daemon will now handle
 * bluetooth Headset (HSP HS and HSP AG) and Handsfree (HFP HF) profiles using
 * native headset backend by default. This can be selectively disabled
 * via runtime configuration arguments to module-bluetooth-discover
 * in /etc/pulse/default.pa
 * To disable HFP HF append enable_native_hfp_hf=false
 * To disable HSP HS append enable_native_hsp_hs=false
 * To disable HSP AG append headset=auto or headset=ofono
 * (note this does NOT require enabling USE ofono)
 * 
 * GStreamer-based RTP implementation modile enabled.
 * To use OPUS payload install media-plugins/gst-plugins-opus
 * and add enable_opus=1 argument to module-rtp-send
 * 
 * Pulseaudio autospawn by client library is no longer enabled when systemd is available.
 * It's recommended to start pulseaudio via its systemd user units:
 * 
 *   systemctl --user enable pulseaudio.service pulseaudio.socket
 * 
 * Root user can change system default configuration for all users:
 * 
 *   systemctl --global enable pulseaudio.service pulseaudio.socket
 * 
 * If you would like to enable autospawn by client library, edit autospawn flag in /etc/pulse/client.conf like this:
 * 
 *   autospawn = yes
 * 
 * The change from autospawn to user units will take effect after restarting.
 * 
 * PulseAudio can be enhanced by installing the following:
 *   sys-auth/rtkit for restricted realtime capabilities via D-Bus
 * Messages for package app-text/texlive-core-2021-r5:
 * 
 * If you have configuration files in /etc/texmf to merge,
 * please update them and run /usr/sbin/texmf-update.
 * 
 * If you are migrating from an older TeX distribution
 * Please make sure you have read:
 * https://wiki.gentoo.org/wiki/Project:TeX/Tex_Live_Migration_Guide
 * in order to avoid possible problems
 * Messages for package media-libs/gegl-0.4.38-r1:
 * Install additional packages for optional runtime features:
 *   media-gfx/graphviz for 'Show Image Graph' under GIMP[debug] menu 'File - Debug'





































































 * Regenerating GNU info directory index...
 * Processed 133 info files.

 * IMPORTANT: 4 config files in '/etc' need updating.

!!! existing preserved libs:
>>> package: gnome-base/nautilus-43.1
 *  - /usr/lib64/libnautilus-extension.so.1
 *  - /usr/lib64/libnautilus-extension.so.1.5.0
 *      used by /usr/lib64/nautilus/extensions-3.0/libnautilus-brasero-extension.so (app-cdr/brasero-3.12.3)
Use emerge @preserved-rebuild to rebuild packages using these libraries
 * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
 * sections of the emerge man page to learn how to update config files.

 * IMPORTANT: 24 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence of this, it often becomes necessary to run 
 * `emerge --update --newuse --deep @world` prior to depclean.

Calculating dependencies  .\b\b... done!
>>> Calculating removal order...

 net-libs/libgrss
    selected: 0.7.0 
   protected: none 
     omitted: none 

 net-libs/rest
    selected: 0.8.1-r1 
   protected: none 
     omitted: 0.9.1 

 sys-devel/clang-runtime
    selected: 15.0.5 
   protected: none 
     omitted: 15.0.6 

 gnome-extra/gnome-browser-connector
    selected: 42.1 
   protected: none 
     omitted: none 

 sys-devel/binutils
    selected: 2.38-r2 
   protected: none 
     omitted: 2.39-r4 

 app-accessibility/at-spi2-atk
    selected: 2.46.0 
   protected: none 
     omitted: none 

 dev-lang/spidermonkey
    selected: 91.13.0-r1 
   protected: none 
     omitted: 102.6.0 

 sys-libs/compiler-rt
    selected: 15.0.5 
   protected: none 
     omitted: 15.0.6 

 sys-libs/compiler-rt-sanitizers
    selected: 15.0.5 
   protected: none 
     omitted: 15.0.6 

 media-video/wireplumber
    selected: 0.4.12-r1 
   protected: none 
     omitted: none 

 dev-lang/lua
    selected: 5.4.4-r103 
   protected: none 
     omitted: none 

 media-video/pipewire
    selected: 0.3.61 
   protected: none 
     omitted: none 

 media-libs/fdk-aac
    selected: 2.0.2 
   protected: none 
     omitted: none 

 media-libs/libldac
    selected: 2.0.2.3-r1 
   protected: none 
     omitted: none 

 media-libs/libfreeaptx
    selected: 0.1.1-r1 
   protected: none 
     omitted: none 

 app-eselect/eselect-lua
    selected: 4-r1 
   protected: none 
     omitted: none 

 net-im/telepathy-mission-control
    selected: 5.16.6 
   protected: none 
     omitted: none 

 net-libs/telepathy-glib
    selected: 0.24.2 
   protected: none 
     omitted: none 

All selected packages: =app-eselect/eselect-lua-4-r1 =sys-devel/binutils-2.38-r2 =media-video/pipewire-0.3.61 =media-libs/libldac-2.0.2.3-r1 =dev-lang/spidermonkey-91.13.0-r1 =net-libs/rest-0.8.1-r1 =app-accessibility/at-spi2-atk-2.46.0 =sys-libs/compiler-rt-15.0.5 =media-video/wireplumber-0.4.12-r1 =sys-libs/compiler-rt-sanitizers-15.0.5 =dev-lang/lua-5.4.4-r103 =net-libs/libgrss-0.7.0 =media-libs/libfreeaptx-0.1.1-r1 =net-libs/telepathy-glib-0.24.2 =sys-devel/clang-runtime-15.0.5 =gnome-extra/gnome-browser-connector-42.1 =media-libs/fdk-aac-2.0.2 =net-im/telepathy-mission-control-5.16.6

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging (1 of 18) net-libs/libgrss-0.7.0...
>>> Unmerging (2 of 18) net-libs/rest-0.8.1-r1...
>>> Unmerging (3 of 18) sys-devel/clang-runtime-15.0.5...
>>> Unmerging (4 of 18) gnome-extra/gnome-browser-connector-42.1...
>>> Unmerging (5 of 18) sys-devel/binutils-2.38-r2...
>>> Unmerging (6 of 18) app-accessibility/at-spi2-atk-2.46.0...
>>> Unmerging (7 of 18) dev-lang/spidermonkey-91.13.0-r1...
>>> Unmerging (8 of 18) sys-libs/compiler-rt-15.0.5...
>>> Unmerging (9 of 18) sys-libs/compiler-rt-sanitizers-15.0.5...
>>> Unmerging (10 of 18) media-video/wireplumber-0.4.12-r1...
>>> Unmerging (11 of 18) dev-lang/lua-5.4.4-r103...
>>> Unmerging (12 of 18) media-video/pipewire-0.3.61...
>>> Unmerging (13 of 18) media-libs/fdk-aac-2.0.2...
>>> Unmerging (14 of 18) media-libs/libldac-2.0.2.3-r1...
>>> Unmerging (15 of 18) media-libs/libfreeaptx-0.1.1-r1...
>>> Unmerging (16 of 18) app-eselect/eselect-lua-4-r1...
>>> Unmerging (17 of 18) net-im/telepathy-mission-control-5.16.6...
>>> Unmerging (18 of 18) net-libs/telepathy-glib-0.24.2...
Packages installed:   1138
Packages in world:    27
Packages in system:   48
Required packages:    1138
Number removed:       18

 * Regenerating GNU info directory index...
 * Processed 6 info files.

!!! existing preserved libs:
>>> package: gnome-base/nautilus-43.1
 *  - /usr/lib64/libnautilus-extension.so.1
 *  - /usr/lib64/libnautilus-extension.so.1.5.0
 *      used by /usr/lib64/nautilus/extensions-3.0/libnautilus-brasero-extension.so (app-cdr/brasero-3.12.3)
Use emerge @preserved-rebuild to rebuild packages using these libraries

 * IMPORTANT: 4 config files in '/etc' need updating.
 * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
 * sections of the emerge man page to learn how to update config files.

 * IMPORTANT: 24 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

Container binhost-amd64-x86-64-gnome exited successfully.



Full build log at /root/.tmp-binhost-amd64-default-17.1-update-1672481821


             reply	other threads:[~2022-12-31 23:38 UTC|newest]

Thread overview: 526+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 23:38 binhost [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-05 10:19 [gentoo-binhost-autobuilds] [binhost amd64-default-17.1] Update succeeded binhost
2023-08-04 10:37 binhost
2023-08-03 10:24 binhost
2023-08-02 10:19 binhost
2023-08-01 10:20 binhost
2023-07-31 10:24 binhost
2023-07-30 10:19 binhost
2023-07-29 10:19 binhost
2023-07-28 10:18 binhost
2023-07-27 10:20 binhost
2023-07-26 10:20 binhost
2023-07-25 10:28 binhost
2023-07-24 11:33 binhost
2023-07-23 10:21 binhost
2023-07-22 10:20 binhost
2023-07-21 10:20 binhost
2023-07-20 10:20 binhost
2023-07-19 10:22 binhost
2023-07-18 14:29 binhost
2023-07-02 10:22 binhost
2023-07-01 10:23 binhost
2023-06-30 10:23 binhost
2023-06-29 10:28 binhost
2023-06-28 10:25 binhost
2023-06-27 11:00 binhost
2023-06-26 10:24 binhost
2023-06-25 10:19 binhost
2023-06-24 10:22 binhost
2023-06-23 10:20 binhost
2023-06-22 11:10 binhost
2023-06-21 10:20 binhost
2023-06-20 10:19 binhost
2023-06-19 10:20 binhost
2023-06-18 10:59 binhost
2023-06-17 10:26 binhost
2023-06-16 10:20 binhost
2023-06-15 10:20 binhost
2023-06-14 10:20 binhost
2023-06-13 10:23 binhost
2023-06-12 10:36 binhost
2023-06-11 10:33 binhost
2023-06-10 11:27 binhost
2023-06-09 10:21 binhost
2023-06-08 10:23 binhost
2023-06-07 10:19 binhost
2023-06-06 10:21 binhost
2023-06-05 10:28 binhost
2023-06-04 10:27 binhost
2023-06-04  0:41 binhost
2023-06-02 10:24 binhost
2023-06-01 10:26 binhost
2023-05-31 10:23 binhost
2023-05-30 21:53 binhost
2023-05-29 10:20 binhost
2023-05-28 11:24 binhost
2023-05-27 10:21 binhost
2023-05-26 10:22 binhost
2023-05-25 10:40 binhost
2023-05-24 10:21 binhost
2023-05-23 11:39 binhost
2023-05-22 11:48 binhost
2023-05-21 10:19 binhost
2023-05-20 10:21 binhost
2023-05-19 11:20 binhost
2023-05-18 10:26 binhost
2023-05-17 10:22 binhost
2023-05-16 10:21 binhost
2023-05-15 10:24 binhost
2023-05-14 10:34 binhost
2023-05-13 10:25 binhost
2023-05-12 10:26 binhost
2023-05-11 10:20 binhost
2023-05-10 10:19 binhost
2023-05-09 10:19 binhost
2023-05-08 10:19 binhost
2023-05-07 10:21 binhost
2023-05-06 10:58 binhost
2023-05-05 10:40 binhost
2023-05-04 10:21 binhost
2023-05-03 10:29 binhost
2023-05-03  1:35 binhost
2023-05-01 19:02 binhost
2023-04-30 10:49 binhost
2023-04-29 11:54 binhost
2023-04-28 10:22 binhost
2023-04-27 10:46 binhost
2023-04-26 10:20 binhost
2023-04-25 10:21 binhost
2023-04-24 13:00 binhost
2023-04-23 11:08 binhost
2023-04-22 10:22 binhost
2023-04-21 10:24 binhost
2023-04-20 10:19 binhost
2023-04-19 10:21 binhost
2023-04-18 10:21 binhost
2023-04-17 10:19 binhost
2023-04-16 11:21 binhost
2023-04-15 11:57 binhost
2023-04-14 10:21 binhost
2023-04-13 10:29 binhost
2023-04-12 10:20 binhost
2023-04-11 10:21 binhost
2023-04-10 11:30 binhost
2023-04-09 11:15 binhost
2023-04-08 10:20 binhost
2023-04-07 10:21 binhost
2023-04-06 10:24 binhost
2023-04-05 10:30 binhost
2023-04-04 10:20 binhost
2023-04-03 10:20 binhost
2023-04-02 11:10 binhost
2023-04-01 10:24 binhost
2023-03-31 11:42 binhost
2023-03-30 10:46 binhost
2023-03-29 10:19 binhost
2023-03-28 10:18 binhost
2023-03-27 10:20 binhost
2023-03-26 10:21 binhost
2023-03-25 10:24 binhost
2023-03-24 10:19 binhost
2023-03-23 10:21 binhost
2023-03-22 10:25 binhost
2023-03-21 10:19 binhost
2023-03-20 10:20 binhost
2023-03-19 10:23 binhost
2023-03-18 10:22 binhost
2023-03-17 10:22 binhost
2023-03-16 10:20 binhost
2023-03-15 10:38 binhost
2023-03-14 10:21 binhost
2023-03-13 10:30 binhost
2023-03-12 10:23 binhost
2023-03-11 10:49 binhost
2023-03-10 11:08 binhost
2023-03-09 10:23 binhost
2023-03-08 10:27 binhost
2023-03-07 10:19 binhost
2023-03-06 10:19 binhost
2023-03-05 10:22 binhost
2023-03-04 10:43 binhost
2023-03-03 10:20 binhost
2023-03-02 10:21 binhost
2023-03-01 10:21 binhost
2023-02-28 11:17 binhost
2023-02-27 10:21 binhost
2023-02-26 10:19 binhost
2023-02-25 10:21 binhost
2023-02-24 10:30 binhost
2023-02-23 10:22 binhost
2023-02-22 10:19 binhost
2023-02-21 10:21 binhost
2023-02-20 10:23 binhost
2023-02-19 10:42 binhost
2023-02-18 10:19 binhost
2023-02-17 10:45 binhost
2023-02-16 10:20 binhost
2023-02-15 10:23 binhost
2023-02-14 10:21 binhost
2023-02-13 10:20 binhost
2023-02-12 10:19 binhost
2023-02-11 10:19 binhost
2023-02-10 10:30 binhost
2023-02-09 10:19 binhost
2023-02-08 16:13 binhost
2023-02-07 10:19 binhost
2023-02-06 10:19 binhost
2023-02-05 11:21 binhost
2023-02-04 10:30 binhost
2023-02-03 10:23 binhost
2023-02-02 10:20 binhost
2023-02-01 10:45 binhost
2023-01-31 10:29 binhost
2023-01-30 10:20 binhost
2023-01-29 10:45 binhost
2023-01-28 10:41 binhost
2023-01-27 10:31 binhost
2023-01-26 11:32 binhost
2023-01-25 10:25 binhost
2023-01-24 10:19 binhost
2023-01-23 11:21 binhost
2023-01-22 15:06 binhost
2023-01-15 15:11 binhost
2023-01-14 10:22 binhost
2023-01-13 10:23 binhost
2023-01-12 10:51 binhost
2023-01-11 10:21 binhost
2023-01-10 10:21 binhost
2023-01-09 10:43 binhost
2023-01-08 10:21 binhost
2023-01-07 11:17 binhost
2023-01-06 10:20 binhost
2023-01-05 10:19 binhost
2023-01-04 10:22 binhost
2023-01-03 11:17 binhost
2023-01-02 10:31 binhost
2023-01-01 10:23 binhost
2022-12-14 10:21 binhost
2022-12-13 10:19 binhost
2022-12-12 10:20 binhost
2022-12-11 10:27 binhost
2022-12-10 10:37 binhost
2022-12-09 10:20 binhost
2022-12-08 10:37 binhost
2022-12-07 10:24 binhost
2022-12-06 11:11 binhost
2022-12-05 10:19 binhost
2022-12-04 11:09 binhost
2022-12-03 10:22 binhost
2022-12-02 12:26 binhost
2022-12-01 10:21 binhost
2022-11-30 10:19 binhost
2022-11-29 10:27 binhost
2022-11-28 10:23 binhost
2022-11-27 20:22 binhost
2022-11-26 11:05 binhost
2022-11-25 12:24 binhost
2022-11-24 10:46 binhost
2022-11-23 19:21 binhost
2022-11-22 10:20 binhost
2022-11-21 10:20 binhost
2022-11-20 10:25 binhost
2022-11-19 10:20 binhost
2022-11-18 10:46 binhost
2022-11-17 10:27 binhost
2022-11-16 10:20 binhost
2022-11-15 10:20 binhost
2022-11-14 10:20 binhost
2022-11-13 10:19 binhost
2022-11-12 10:37 binhost
2022-11-11 10:20 binhost
2022-11-10 10:22 binhost
2022-11-09 10:21 binhost
2022-11-08 10:21 binhost
2022-11-07 11:18 binhost
2022-11-06 11:44 binhost
2022-11-05 10:21 binhost
2022-11-04 10:27 binhost
2022-11-03 10:25 binhost
2022-11-02 10:20 binhost
2022-11-01 10:36 binhost
2022-10-31 10:22 binhost
2022-10-30 10:28 binhost
2022-10-29 10:31 binhost
2022-10-28 10:23 binhost
2022-10-27 10:25 binhost
2022-10-26 10:22 binhost
2022-10-25 10:21 binhost
2022-10-24 10:21 binhost
2022-10-23 10:23 binhost
2022-10-22 10:22 binhost
2022-10-21 10:46 binhost
2022-10-20 10:21 binhost
2022-10-19 10:21 binhost
2022-10-18 10:22 binhost
2022-10-17 10:21 binhost
2022-10-16 10:19 binhost
2022-10-15 10:26 binhost
2022-10-14 10:23 binhost
2022-10-13 11:02 binhost
2022-10-12 12:36 binhost
2022-10-11 10:25 binhost
2022-10-10 10:23 binhost
2022-10-09 12:05 binhost
2022-10-08 10:27 binhost
2022-10-07 10:33 binhost
2022-10-06 10:38 binhost
2022-10-05 10:19 binhost
2022-10-04 10:28 binhost
2022-10-03 10:21 binhost
2022-10-02 10:30 binhost
2022-10-01 10:31 binhost
2022-09-30 10:34 binhost
2022-09-29 10:19 binhost
2022-09-28 10:22 binhost
2022-09-27 10:22 binhost
2022-09-26 10:21 binhost
2022-09-25 12:15 binhost
2022-09-24 10:29 binhost
2022-09-23 10:25 binhost
2022-09-22 10:22 binhost
2022-09-21 10:19 binhost
2022-09-20 10:21 binhost
2022-09-19 10:20 binhost
2022-09-18 10:20 binhost
2022-09-17 12:18 binhost
2022-09-16 11:47 binhost
2022-09-15 10:25 binhost
2022-09-14 10:32 binhost
2022-09-13 10:31 binhost
2022-09-12 10:23 binhost
2022-09-11 10:20 binhost
2022-09-10 10:35 binhost
2022-09-09 10:22 binhost
2022-09-08 10:20 binhost
2022-09-07 10:31 binhost
2022-09-06 10:20 binhost
2022-09-05 11:55 binhost
2022-09-04 10:24 binhost
2022-09-03 10:24 binhost
2022-09-02 10:20 binhost
2022-09-01 10:49 binhost
2022-08-31 10:36 binhost
2022-08-30 10:33 binhost
2022-08-29 10:21 binhost
2022-08-28 10:22 binhost
2022-08-27 11:22 binhost
2022-08-26 10:21 binhost
2022-08-25 10:26 binhost
2022-08-24 11:20 binhost
2022-08-23 10:19 binhost
2022-08-22 10:21 binhost
2022-08-21 10:22 binhost
2022-08-20 10:20 binhost
2022-08-19 10:20 binhost
2022-08-18 10:21 binhost
2022-08-17 10:49 binhost
2022-08-16 11:27 binhost
2022-08-15 10:20 binhost
2022-08-14 10:20 binhost
2022-08-13 10:27 binhost
2022-08-12 10:20 binhost
2022-08-11 10:21 binhost
2022-08-10 10:20 binhost
2022-08-09 10:21 binhost
2022-08-08 10:20 binhost
2022-08-07 10:31 binhost
2022-08-06 10:42 binhost
2022-08-05 10:43 binhost
2022-08-04 11:09 binhost
2022-08-03 10:20 binhost
2022-08-02 10:41 binhost
2022-08-01 10:21 binhost
2022-07-31 10:26 binhost
2022-07-30 10:56 binhost
2022-07-29 10:34 binhost
2022-07-28 10:20 binhost
2022-07-27 11:07 binhost
2022-07-26 11:35 binhost
2022-07-25 10:51 binhost
2022-07-24 10:21 binhost
2022-07-23 10:22 binhost
2022-07-22 10:19 binhost
2022-07-21 10:25 binhost
2022-07-20 11:14 binhost
2022-07-19 10:20 binhost
2022-07-18 21:42 binhost
2022-06-03 10:22 binhost
2022-06-02 10:23 binhost
2022-06-01 10:43 binhost
2022-05-31 10:26 binhost
2022-05-30 10:48 binhost
2022-05-29 10:20 binhost
2022-05-28 11:13 binhost
2022-05-27 10:21 binhost
2022-05-26 10:22 binhost
2022-05-25 10:21 binhost
2022-05-24 10:21 binhost
2022-05-23 10:21 binhost
2022-05-22 10:24 binhost
2022-05-21 10:19 binhost
2022-05-20 10:20 binhost
2022-05-19 10:20 binhost
2022-05-18 10:21 binhost
2022-05-17 10:37 binhost
2022-05-16 10:19 binhost
2022-05-15 10:20 binhost
2022-05-14 10:26 binhost
2022-05-13 10:19 binhost
2022-05-12 10:19 binhost
2022-05-11 10:28 binhost
2022-05-10 10:21 binhost
2022-05-09 11:04 binhost
2022-05-08 10:28 binhost
2022-05-07 10:22 binhost
2022-05-06 10:20 binhost
2022-05-05 10:20 binhost
2022-05-04 10:25 binhost
2022-05-03 10:21 binhost
2022-05-02 10:25 binhost
2022-05-01 10:20 binhost
2022-04-30 11:02 binhost
2022-04-29 10:25 binhost
2022-04-28 10:19 binhost
2022-04-27 10:21 binhost
2022-04-26 10:27 binhost
2022-04-25 10:27 binhost
2022-04-24 10:25 binhost
2022-04-23 10:29 binhost
2022-04-22 10:45 binhost
2022-04-21 10:20 binhost
2022-04-20 10:47 binhost
2022-04-19 10:26 binhost
2022-04-18 11:35 binhost
2022-04-17 10:26 binhost
2022-04-16 13:25 binhost
2022-04-15 10:22 binhost
2022-04-14 10:22 binhost
2022-04-13 12:19 binhost
2022-04-12 10:22 binhost
2022-04-11 10:21 binhost
2022-04-10 10:21 binhost
2022-04-09 10:20 binhost
2022-04-08 11:17 binhost
2022-04-07 10:29 binhost
2022-04-06 10:23 binhost
2022-04-05 10:22 binhost
2022-04-04 10:21 binhost
2022-04-03 10:29 binhost
2022-04-02 10:23 binhost
2022-04-01 10:25 binhost
2022-03-31 10:21 binhost
2022-03-30 10:19 binhost
2022-03-29 10:22 binhost
2022-03-28 10:22 binhost
2022-03-27 10:25 binhost
2022-03-26 10:24 binhost
2022-03-25 10:21 binhost
2022-03-24 10:22 binhost
2022-03-23 11:57 binhost
2022-03-22 10:24 binhost
2022-03-21 10:21 binhost
2022-03-20 10:19 binhost
2022-03-19 10:19 binhost
2022-03-18 10:20 binhost
2022-03-17 11:06 binhost
2022-03-16 10:24 binhost
2022-03-15 10:20 binhost
2022-03-14 10:23 binhost
2022-03-13 10:20 binhost
2022-03-12 10:22 binhost
2022-03-11 10:20 binhost
2022-03-10 10:22 binhost
2022-03-09 10:20 binhost
2022-03-08 19:22 binhost
2022-03-08 10:18 binhost
2022-03-07 10:19 binhost
2022-03-06 10:23 binhost
2022-03-05 10:20 binhost
2022-03-04 10:20 binhost
2022-03-03 10:20 binhost
2022-03-02 10:22 binhost
2022-03-01 10:20 binhost
2022-02-28 10:40 binhost
2022-02-27 10:20 binhost
2022-02-26 10:21 binhost
2022-02-25 10:23 binhost
2022-02-24 10:19 binhost
2022-02-23 10:41 binhost
2022-02-22 10:21 binhost
2022-02-21 10:20 binhost
2022-02-20 11:28 binhost
2022-02-19 10:26 binhost
2022-02-18 11:28 binhost
2022-02-17 10:21 binhost
2022-02-16 10:19 binhost
2022-02-15 10:23 binhost
2022-02-14 10:20 binhost
2022-02-13 10:42 binhost
2022-02-12 10:20 binhost
2022-02-11 10:22 binhost
2022-02-10 10:20 binhost
2022-02-09 10:44 binhost
2022-02-08 10:26 binhost
2022-02-07 10:40 binhost
2022-02-06 10:26 binhost
2022-02-05 10:21 binhost
2022-02-04 10:20 binhost
2022-02-03 13:26 binhost
2022-02-02 10:21 binhost
2022-02-01 10:20 binhost
2022-01-31 10:20 binhost
2022-01-30 10:22 binhost
2022-01-29 10:21 binhost
2022-01-28 10:24 binhost
2022-01-27 10:19 binhost
2022-01-26 10:22 binhost
2022-01-25 10:20 binhost
2022-01-24 10:39 binhost
2022-01-23 12:40 binhost
2022-01-22 21:38 binhost
2022-01-22 10:26 binhost
2022-01-21 11:10 binhost
2022-01-20 10:22 binhost
2022-01-19 10:51 binhost
2022-01-18 10:20 binhost
2022-01-17 10:22 binhost
2022-01-16 10:22 binhost
2022-01-15 10:23 binhost
2022-01-14 10:21 binhost
2022-01-13 10:25 binhost
2022-01-12 10:20 binhost
2022-01-11 10:20 binhost
2022-01-10 10:21 binhost
2022-01-09 14:37 binhost
2022-01-08 10:29 binhost
2022-01-07 11:02 binhost
2022-01-06 10:22 binhost
2022-01-05 10:41 binhost
2022-01-04 10:27 binhost
2022-01-03 11:30 binhost
2022-01-02 10:23 binhost
2022-01-01 10:28 binhost
2021-12-31 10:26 binhost
2021-12-30 10:20 binhost
2021-12-29 10:22 binhost
2021-12-28 10:22 binhost
2021-12-27 10:22 binhost
2021-12-26 11:23 binhost
2021-12-25 10:24 binhost
2021-12-24 10:22 binhost
2021-12-23 10:20 binhost
2021-12-22 10:20 binhost
2021-12-21 10:21 binhost
2021-12-20 10:25 binhost
2021-12-19 10:30 binhost
2021-12-18 10:24 binhost
2021-12-17 10:25 binhost
2021-12-16 10:41 binhost
2021-12-15 10:29 binhost
2021-12-14 10:20 binhost
2021-12-13 10:50 binhost
2021-12-12 10:21 binhost
2021-12-11 10:43 binhost
2021-12-10 10:22 binhost
2021-12-09 10:20 binhost

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221231233807.4F3F926808B@demeter.amd64.dev.gentoo.org \
    --to=binhost@demeter.amd64.dev.gentoo.org \
    --cc=gentoo-binhost-autobuilds@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox