On 04-12-2021 10:24:23 +0100, Michał Górny wrote:
> On Sat, 2021-12-04 at 10:15 +0100, Fabian Groffen wrote:
> > On 04-12-2021 10:13:09 +0100, Michał Górny wrote:
> > > On Sat, 2021-12-04 at 09:56 +0100, Fabian Groffen wrote:
> > > > Why don't you change your
On 04-12-2021 10:13:09 +0100, Michał Górny wrote:
> On Sat, 2021-12-04 at 09:56 +0100, Fabian Groffen wrote:
> > Why don't you change your color.map instead of changing the default for
> > everyone?
>
> Why should we keep a stupid default? Should we optimize Gentoo for
&g
I"darkblue"\fR
> +\fBPKG_BLOCKER_SATISFIED\fR = \fI"teal"\fR
> Defines color used for satisfied blockers.
> .TP
> \fBPKG_MERGE\fR = \fI"darkgreen"\fR
> @@ -63,10 +63,10 @@ package.
> Defines color used for world packages planned to be merged using a binary
> package.
> .TP
> -\fBPKG_NOMERGE\fR = \fI"darkblue"\fR
> +\fBPKG_NOMERGE\fR = \fI"teal"\fR
> Defines color used for packages not planned to be merged.
> .TP
> -\fBPKG_NOMERGE_SYSTEM\fR = \fI"darkblue"\fR
> +\fBPKG_NOMERGE_SYSTEM\fR = \fI"teal"\fR
> Defines color used for system packages not planned to be merged.
> .TP
> \fBPKG_NOMERGE_WORLD\fR = \fI"blue"\fR
> --
> 2.34.1
>
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ntinued and so on.
>
> WDYT?
>
> --
> Best regards,
> Michał Górny
>
>
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 05-10-2021 09:35:32 +0200, Michał Górny wrote:
> On Thu, 2021-09-30 at 09:18 +0200, Fabian Groffen wrote:
> > > > Final question, am I understanding correctly that normal lines are not
> > > > prefixed with something? Would it be, for consistency, alignment, and
>
ow it was before alignment-wise, but meh at 4 >
> >
> > >>> message
> > QA> not convinced about this one, but throwing it here anyway
> > (other characters could be considered as well)
> >
> > Maybe a poll of some kind may help, personally undecided on what I
> > like better beside agreeing that a change is needed.
>
>
> --
> ionen
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 30-09-2021 08:44:33 +0200, Michał Górny wrote:
> On Thu, 2021-09-30 at 08:40 +0200, Fabian Groffen wrote:
> > Hi,
> >
> > Would it be possible to have some switch (e.g. --style=legacy) that
> > controls this new vs. the old behaviour? Would perhaps allow
> > a
entoo/portage/pull/759
>
> Example screenshot:
> https://user-images.githubusercontent.com/110765/135119090-16e9599d-1b0f-41b8-a965-a55577183ffd.png
>
> --
> Best regards,
> Michał Górny
>
>
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
9.1.11 pkg_postinst
>... immediately after merging the package to the live filesystem. ...
Aha, so does this mean pkg_prerm and pkg_postrm are run with replacing
package in place, e.g. if they refer to scripts installed by the
replaced package they may no longer exist or be the same?
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
gt; > > an old portage to begin with?
> > > Can it be fixed?
> >
> > The error goes away when I do: ED=/ qmerge -OK sys-apps/portage
> > Does that mean that it is qmerge(aka portage-utils) that needs to set ED
> > during merge? which PHASES ?
>
> According to PMS, a package manager must define ED in src_install,
> pkg_preinst, and pkg_postinst.
Perhaps qmerge should use export for these vars. In any case this seems
tracked in bug 792273.
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
# Fabian Groffen (2021-05-24)
# Hack on hack no longer sustainable
# - seemingly dead upstream
# - no (official) Python 3 support
# removal in 30 days, bug: https://bugs.gentoo.org/791613
migrate to something like app-metrics/collectd using the the
write_graphite plugin.
--
Fabian Groffen
however is the solution, how to fix one's configuration.
Luckily it seems people find their way to Exim's bugtracker to get help
there.
Thanks for the suggestion though,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
Title: Exim>=4.94 transports: tainted not permitted
Author: Fabian Groffen
Posted: 2021-05-??
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: mail-mta/exim
The Message Transfer Agent Exim disallows tainted variables in transport
configurations since version 4.94. Existing exim.c
On 02-05-2021 12:23:30 +0200, Ulrich Mueller wrote:
> >>>>> On Sun, 02 May 2021, Fabian Groffen wrote:
>
> > Title: Exim >=4.94 disallows tainted variables in transport configurations
>
> Title is too long (GLEP 42 allows 50 chars max).
ah, missed that
Title: Exim >=4.94 disallows tainted variables in transport configurations
Author: Fabian Groffen
Posted: 2021-05-??
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: mail-mta/exim
Since the release of Exim-4.94, transports refuse to use tainted data in
constructing a delivery locat
Stein wrote:
> > Dear all
> >
> > the following packages are up for grabs after dropping
> > desktop-misc:
> >
> > x11-misc/xbindkeys
> > https://packages.gentoo.org/packages/x11-misc/xbindkeys
> >
> > There is an open PR
> > https://g
Signed-off-by: Fabian Groffen
---
eclass/db.eclass | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/eclass/db.eclass b/eclass/db.eclass
index 9a246d18979..52afe0b765f 100644
--- a/eclass/db.eclass
+++ b/eclass/db.eclass
@@ -23,13 +23,13 @@ db_fix_so
perhaps tinderbox logs or something can reveal /usr/bin/libtool usage
somehow.
Thanks,
Fabian
> [1] https://bugs.gentoo.org/88596
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
o I'd prefer if you waited with that to avoid merge
> conflicts.
Could you please share your intended approach?
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
h open(lock_path, 'a') as f:
> + fcntl.lockf(f.fileno(), fcntl.LOCK_EX|fcntl.LOCK_NB)
> + except EnvironmentError as e:
> + if e.errno == errno.EAGAIN:
> + # Parent process holds lock, as expected.
> + sys.exit(0)
> +
> + # Something went wrong.
> + sys.exit(1)
>
> _open_fds = {}
> _open_inodes = {}
> --
> 2.26.2
>
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
# Fabian Groffen (2020-11-23)
# No longer used, not really functional either, noone should be using
# this, removal in 30 days.
sys-kernel/xnu-headers
sys-libs/darwin-libc-headers
dev-libs/libmissing
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
t; > find the libs in there now).
>
> Yes. Attaching logs.
The logs seem to indicate that it thinks all libs on your systems do not
belong to any package. This suggests the tool cannot locate the VDB or
something, as most of the things in the list are obviously owned by
packages.
Thanks,
Fab
profiles either directly depend on the amd64/17.0 profile, or we use
a sub-profile from amd64/17.0 profile, so if it's going to get removed,
we are having a problem, don't we?
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 10-11-2020 09:34:52 +0100, Michał Górny wrote:
> On Tue, 2020-11-10 at 08:55 +0100, Fabian Groffen wrote:
> > On 09-11-2020 19:38:28 +, Alexey Sokolov wrote:
> > > Hi Fabian
> > > I tried to migrate my prefix to 17.1, and there are issues.
> > >
>
-st.so
> /home/user/gentoo/usr/lib/binutils/x86_64-pc-linux-gnu/2.34/libopcodes-2.34.0.gentoo-sys-devel-binutils-st.so
>
> --
> Best regards,
> Alexey "DarthGandalf" Sokolov
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ate the
> > amd64
> > 17.0 profiles!
> >
>
> Prefix bootstrap script still makes new installations to use it
This should be solved with
b0445c0a8dd6d2f792c5bb088b154aca53868353
a9c478dc881ee18fefc7342da994b00e60eaad8e
on gentoo.git and
0d7f6b6eb00d0f51f35019846b8f79048b3
b.gentoo.org/repo/gentoo.git/commit/?id=ae376c73ef197d6c7aa619e821c436ccab0cd77e
>
> Usage example for app-forensics/honggfuzz:
>
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fd841336dfdefbc14907e2d9b1eb1a1a3f5f8b8e
This is cool, but shouldn't it be something like openmp? (e.g. blocks)
There is no reason blocks have to be used if not on macOS (where system
headers use blocks features).
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
/?p=glibc.git;a=blob;f=string/strcasestr.c;h=d2964c5548b9ea7a68fc5b18b25ddfe7ddd6835c;hb=HEAD#l45
> [6] http://git.suugaku.co.uk/ash-euses/tree/
> [7] http://git.suugaku.co.uk/ash-euses/snapshot/ash-euses-0.3.tar.gz
>
> --
>
> Ashley Dixon
> suugaku.co.uk
>
> 2A9A 4117
> DA96 D18A
> 8A7B B0D2
> A30E BF25
> F290 A8AA
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 30-06-2020 13:13:29 -0500, Sid Spry wrote:
> On Tue, Jun 30, 2020, at 1:20 AM, Fabian Groffen wrote:
> > Hi,
> >
> > On 29-06-2020 21:13:43 -0500, Sid Spry wrote:
> > > Hello,
> > >
> > > I have some runnable pseudocode outlining a faster tr
r i in range(0, 160, 5):
> byte = i // 8
> offset = i - byte * 8
> # offset | bits remaining in k+1 | right-shift k+1
> # 3 | 0 | x
> # 4 | 1 | 7
> # 5 | 2 | 6
> # 6 | 3 | 5
> # 7 | 4 | 4
> if offset < 4:
> n = (b[byte] >> (3 - offset))
> else:
> n = (b[byte] << (offset - 3)) + (b[byte + 1] >> (11 - offset))
>
> ret += zb32[n & 0b1]
> return ret
>
> def build_web_key_uri(address: str) -> str:
> local, remote = address.split('@')
> local = hash_localpart(local.encode('utf-8'))
> return 'https://' + remote + '/.well-known/openpgpkey/hu/' + \
> local
>
> def stream_to_file(uri: str, fname: str) -> None:
> with requests.get(uri, verify=True, stream=True) as r:
> from pprint import pprint
> pprint(r.headers)
> with open(fname, 'wb') as f:
> shutil.copyfileobj(r.raw, f)
> ```
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
please
> let me know if any changes are necessary.
This sounds like a good job to me! Do you have any idea what the added
memory pressure for these changes are?
Thanks,
Fabian
>
> Thanks,
> Chun-Yu
>
>
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
roblem is already solved, why do you need these shebangs
changed?
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
uld have direct access to compilers, but it's easy enough to
add the compilers to PATH if really necessary.
I guess what I'm trying to say is: you can hide effect of the setup for
users if you'd like. That is, after we had buildbots point out the bulk
of packages that are wrong of course.
of your genuine objectives with the service. If
it is, I can see why you fear spam so much.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
f dealing with spam -- require every new system
> identifier to be confirmed by solving a CAPTCHA (or a few identifiers
> for one CAPTCHA).
>
> The advantage of this method is that it requires a real human work to be
> performed, effectively limiting the ability to submit spam
f other accounts in the IDP remains to be
> seem.
>
>
> References
>1. http://id.gentoo.org
>2. http://id.gentoo.org
>3. http://gentoo.org
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
r help on them:
> equery -h
> equery hasuse -h
> enalyze -h
> enalyze a -h
In addition to these great tools, portage-utils' quse might also be
useful:
% quse python2_7
...
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
d doesn't do parallel good. If we want to change
> this, we should go for something cool like zstd that scales better.
I'd go for zstd too. It seems to be the best of both worlds, good
compression at a good speed.
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
his isn't treated as an error?
Thanks,
Fabian
> + fi
> +
> # Process the user options first.
> local owner='root'
> local group='0'
> --
> 2.25.0
>
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
erested to hear what kind of things you're thinking about here.
I feel it would help if we would have the ability to at least
compile/test ebuilds automatically. Not sure how helpful qemu could be
there, but I know things like compiling for things like arm (RPi) works
reasonably well.
Thanks,
Fabian
On 13-12-2019 14:24:33 -0500, Michael Orlitzky wrote:
> On 12/13/19 9:28 AM, Fabian Groffen wrote:
> >
> > We are providing those patches, maybe. In reality very often the
> > patches originate from somewhere else though. And you don't want to
> > have to respi
provide.
We are providing those patches, maybe. In reality very often the
patches originate from somewhere else though. And you don't want to
have to respin all of those just because. At least that's what I feel.
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 29-10-2019 15:45:34 +0100, Michał Górny wrote:
> On Tue, 2019-10-29 at 15:33 +0100, Fabian Groffen wrote:
> > In addition, there are currently files there that aren't referenced from
> > ebuilds. Prefix uses these files during bootstrap, local mirrors are
> > often muc
to have such
official translation service on Gentoo hardware.
(I just wrote a small wsgi script that calculates the hash and generates
the redirect from Python, served via uwsgi/nginx, but there should be
many ways to achieve the same goals, if and only if a blake2b
implementation were available for it.)
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ream remaking release packages.
> >
>
> It's no longer valid.
Just wondering. Do you mean it isn't valid that some upstreams do this
(yes horror)? We surely need a way to work around that ...
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ted by the servers.
Would it be possible to run a service that sends a 302 for the
distfiles/foo-1.tar.gz to the appropriate bucket such that manual
fetching doesn't require to calculate the hash?
I prototyped this myself for distfiles.prefix, and seems like a nice
guesture for at least the transit
On 21-09-2019 09:06:01 +0200, Michał Górny wrote:
> On Sat, 2019-09-21 at 08:43 +0200, Fabian Groffen wrote:
> > Why not teach our tools (equery, quse, etc.) to print these USE-flags
> > like Portage does? (looking them up to be valid expands)
> > Then users have nothing
g users, we should
either do them all or stick to the current scheme.
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
# Fabian Groffen (2019-09-15)
# Incorporated in >=app-portage/portage-utils-0.80 as qmanifest
# Removal in 30 days. Bug #694428
app-portage/hashgen
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 19-08-2019 22:04:12 +0200, Michał Górny wrote:
> On Sun, 2019-08-11 at 13:21 +0200, Michał Górny wrote:
> > USE=magic is currently used consistently by 12 packages:
> >
>
> Merged.
>
> --
> Best regards,
> Michał Górny
>
--
Fabian Groffen
Gentoo
ithout need for EAPI bump,
>
> - I would like to have this implemented consistently both in Portage
> and pkgcore,
>
> - we will need to clearly define how to dump arrays.
>
>
> What do you think?
>
> --
> Best regards,
> Michał Górny
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
oach, surely, there are others.
Right, or we go for some (official) form of binpkgs distribution.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
> * Larry is the Gentoo Example
> * 2019-01-01 + 30 days is unclear, if we do not use UTC time
> * The new date format is easy to read and write and easy to parse
> internationally.
>
> Do you have any objections?
>
>
> By the way, you can get a formatted string of now in UTC with:
> date -u +"%Y-%m-%d"
>
> --
> Best,
> Jonas
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
e drop at least empty
> 'deprecated' file to notify users?
I cleaned it up, it isn't in use any more.
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
Pushed, thanks
On 10-01-2019 20:37:16 -0800, Zac Medico wrote:
> On 1/10/19 7:30 AM, Fabian Groffen wrote:
> > The reporting of files remaining can look somewhat odd since the report
> > interval is hardcoded to be per 1000 objects. Adjust this interval to
> > be ti
remaining ...
Possible output after this patch on a slower machine:
* checking 6158 files for package collisions
48% done, 3145 files remaining ...
96% done, 192 files remaining ...
100% done
Signed-off-by: Fabian Groffen
---
lib/portage/dbapi/vartree.py | 15 +--
1 file changed, 13
,
> > plib_collisions
> >
> > def _lstat_inode_map(self, path_iter):
> >
>
>
> --
> Thanks,
> Zac
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
remaining ...
Possible output after this patch on a slower machine:
* checking 6158 files for package collisions
48% done, 3145 files remaining ...
96% done, 192 files remaining ...
100% done
Signed-off-by: Fabian Groffen
---
lib/portage/dbapi/vartree.py | 13 +++--
1 file changed, 11
On 08-01-2019 20:59:34 +, M. J. Everitt wrote:
> On 08/01/19 19:15, Zac Medico wrote:
> > On 1/8/19 5:42 AM, Fabian Groffen wrote:
> >> The reporting of files remaining can look somewhat odd since the report
> >> interval is hardcoded to be per 1000 obj
remaining ...
Possible output after this patch on a slower machine:
* checking 6158 files for package collisions
48% done, 3145 files remaining ...
96% done, 192 files remaining ...
100% done
Signed-off-by: Fabian Groffen
---
lib/portage/dbapi/vartree.py | 11 +--
1 file changed, 9
On 08-01-2019 09:17:04 +0100, Ulrich Mueller wrote:
> >>>>> On Tue, 08 Jan 2019, Fabian Groffen wrote:
>
> > Output before this patch:
>
> > * checking 6111 files for package collisions
> > [...]
>
> > After:
>
> > * checkin
% done, 2050 files remaining ...
83% done, 1023 files remaining ...
100% done
Signed-off-by: Fabian Groffen
---
lib/portage/dbapi/vartree.py | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/lib/portage/dbapi/vartree.py b/lib/portage/dbapi/vartree.py
index
% done, 2050 files remaining ...
83% done, 1023 files remaining ...
Signed-off-by: Fabian Groffen
---
lib/portage/dbapi/vartree.py | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/lib/portage/dbapi/vartree.py b/lib/portage/dbapi/vartree.py
index 4b91caea8..4d0bf2789
On 26-11-2018 21:13:53 +, Andrey Utkin wrote:
> On Wed, Nov 21, 2018 at 11:45:54AM +0100, Fabian Groffen wrote:
> > We agree it is hackish, and we agree we can do without. You simply
> > exaggerate the problem, IMO, which mostly isn't there, because it works
> > fin
mention POSIX, which triggered me. I think it would be good to
specify which tar format to use.
POSIX.1-2001/pax format doesn't have a 100/256 char filename length
restriction, which is good but it is not (yet) used by default by GNU
tar. busybox tar can read pax tars, it seems.
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ages/sys-apps/sed-4.5.tbz2 | tar -jxf -
results in no warnings/errors from bzip about trailing garbage, possible
thanks to the spec being smart enough about this.
Not having to do this, when under stress and pressure to restore a
system to get it back into production, is a plus. Though, in that
scenario the trailing garbage warning wouldn't have been that bad
either.
> > > > > 3. **The file format should provide for partial fetching of binary
> > > > >packages.** It should be possible to easily fetch and read
> > > > >the package metadata without having to download the whole package.
> > > >
> > > > Like above, what is the use-case here? Why would you want this? I
> > > > think I'm missing something here.
> > >
> > > Does this harm anything? Even if there's little real use for this, is
> > > there any harm in supporting it? Are we supposed to do things the other
> > > way around with no benefit just because you don't see any real use for
> > > it?
> >
> > Well, you make a huge point out of it. And if it isn't used, then why
> > bother so much about it. Then it just looks like you want to use it as
> > an argument to get rid of something you just don't like.
> >
> > In my opinion you better just say "hey I would like to implement this
> > binpkg format, because I think it would be easier to support with
> > minimal tools since it doesn't have custom features". I would have
> > nothing against that. Simple and elegant is nice, you don't need to
> > invent arguments for that, in my opinion.
>
> The spec is now more focused on that.
Thank you, much appreciated.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 18-11-2018 10:38:51 +0100, Michał Górny wrote:
> On Sun, 2018-11-18 at 10:16 +0100, Fabian Groffen wrote:
> > On 17-11-2018 12:21:40 +0100, Michał Górny wrote:
> > > Problems with the current binary package format
> > > ---
having to recompress package files.
>
> 6. **The file format should account for easy recognition both through
>filename and through contents.** Preferably, it should have distinct
>features making it possible to detect it via file(1).
>
> 7. **The file format should allow
ould
> reduce the outer size of binary packages, I think the format is simply
> too obscure. It lives mostly as static library format, and the tooling
> for it is part of binutils. LSB considers it deprecated. While I don't
> see it going away anytime soon, I'd rather not rely on it in order to
> save a few KiB.
>
>
> Is there anything left to address?
>
> --
> Best regards,
> Michał Górny
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ing patches to this ML targets the right audience, yet
I welcome the contribution.
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
I think you misunderstood what I wrote, or I wasn't clear enough.
Richard summed up my intention nicely in his response.
Fabian
On 15-09-2018 00:46:24 +0300, Alon Bar-Lev wrote:
> On Sat, Sep 15, 2018 at 12:29 AM Fabian Groffen wrote:
> >
> > On 15-09-2018 00:07:12 +0300, Alo
E=upstream-cflags, which Gentoo
disables by default.
As maintainer and/or enthusiastic user, like you wrote for gnutls, I
would be more than happy to provide build logs/errors for all the arches
I have access to. So like I wrote before, I think we should consider
case-by-case basis to make it easy to do so.
Fab
venience would be worth it.
Perhaps, if one persists on going this route, only do this for platforms
that upstream supports, such that arches which will suffer from this
(typically ppc, sparc, ...) don't have to be blocked by this.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 13-09-2018 18:56:13 +0300, Alon Bar-Lev wrote:
> On Thu, Sep 13, 2018 at 6:51 PM Fabian Groffen wrote:
> >
> > On 12-09-2018 17:46:03 -0700, Matt Turner wrote:
> > > On Wed, Sep 12, 2018 at 5:11 PM Rich Freeman wrote:
> > > With new GCC comes new warnings,
xactly the sort of reason
> why we'd want to build with -Werror on packages where these issues are
> unacceptable?
Can you think of a way in which a new runtime issue would occur that
-Werror would have guarded? And that issue would also get through
maintainer and ~arch testing?
Fabian
a compiler or not)
then this should ideally stand out during ~arch testing, or even before
when the Gentoo maintainer examines the build (might even use -Werror
for his own purposes). If such code ends up in stable arch we just made
a stabilisation mistake, or got royally messed up by upstream, depending
how you look at it.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
g with this.
>
> With new GCC comes new warnings, and harmless as the vast majority are
> they cause the build to break with Werror.
To illustrate harmless:
warning: this statement may fall through [-Wimplicit-fallthrough=]
The warning message already has it in it that it's just a pure guess.
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
you add -Werror to your
CFLAGS you basically introduce breakage for some autoconf-based
packages.
What we really should be having is an easy way for post-configure CFLAGS
addition. Just to support devs/users who insist on this for their
setups.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
real security problems such as
races, which GCC doesn't do yet, as far as I'm aware. Let alone
trigger with -Werror.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
# runtime library
> + ;;
> + undefined)
> + eerror "please specify either --link or
> --run to get_libname"
> + eerror "for ming
, after two independent breakages
> > 2.) Revoking the commit access for 14 days
> >
> > These violations will be evaluated individually by all QA team members.
> > Warnings can be revoked, if during 6 months period a developer makes at
> > least 20 non trivial changes not producing more breakages.
> >
> >
>
> --
>
> Sergei
>
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
# actual sync
> command = rsynccommand[:]
> +
> + if self.repo.location != download_dir:
> + # Use shared hardlinks for files that
> are identical
> + # in the prev
in
the human SSD.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
Thanks :)
> [1]:https://dev.gentoo.org/~mgorny/dev-timeline.html
> [2]:https://dev.gentoo.org/~mgorny/active-devs.html
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ay". Yay. That doesn't make you "right".
> I'm seriously worried about the future of Gentoo. I'd really appreciate
> if you started focusing on that as well. I get that all this stuff looks
> cool on paper but few months or years from now, someone will curse
> 'whoever wrote that code
more obliged to fix them?
> Provided that the packages are still maintained, and it won't be
> 'hey, we just made it impossible to install this package, maybe someone
> will fix it one day'.
I agree, packages shouldn't suddenly start failing. Not during install,
not during runtime either. For changes like this EAPIs were invented.
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
_exporter
> * net-analyzer/prometheus-uwsgi_exporter
> * net-analyzer/prometheus-pushgateway
> * net-analyzer/prometheus-alertmanager
>
> With the growing adoption of prometheus I expect more exporters to be
> added (I have five more that I want to add in the near future).
>
&
ng snapshots (for emerge webrsync) and no rsync propagation.
>
> -A
>
>
>
> References:
>1. https://infra-status.gentoo.org/
>
> read_char: errno==EILSEQ; invalid byte sequence for UTF-8:
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 28-02-2018 22:08:54 +, Robin H. Johnson wrote:
> On Wed, Feb 28, 2018 at 04:10:52PM +0100, Fabian Groffen wrote:
> > Hi,
> >
> > I'm working on a verification implementation of
> > https://www.gentoo.org/glep/glep-0074.html and ran into the following
> > s
as it can be on this odd
file (I thought it used to complain about stray/unadded files).
Does anybody know or have a pointer to what the policies on files in our
ebuild dirs actually is?
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
) is it technically
possible to reject such commits?
3) if 2) should we decide on some clock skew and reject anything which
is beyond that?
How do others feel about this?
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
hat, I'd like to group
32/64 bits versions of arches. Basically djc converted into:
AMD64
X86
PPC64
PPC
ARM64
ARM
SPARC64 (?)
SPARC
ALPHA
IA64
HPPA
MIPS
...
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
USE=clang)
> + Support dumping LLVM bitcode sections in
> Mach-O files
> + (uses app-arch/libxar)
I think you mean app-arch/xar everywhere?
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
d", and I wonder if
in that case it wouldn't be better to introduce a new one instead?
Maybe I'm just one of a few who thinks the order is reversed now.
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
ht, I suggest to anyone who doesn't
like this direction that we move discussions to -project instead.
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
signature.asc
Description: PGP signature
On 14-12-2017 14:41:17 +0100, Michał Górny wrote:
> W dniu czw, 14.12.2017 o godzinie 13∶56 +0100, użytkownik Fabian Groffen
> napisał:
> > On 14-12-2017 13:39:18 +0100, Michał Górny wrote:
> > > Dnia 14 grudnia 2017 13:21:47 CET, Fabian Groffen <grob...@gentoo.org>
&g
see) contact Andrey upfront
to establish how honest his mistake was?
> Andrey pretty clearly stated that he did this *on purpose*.
Andreas also did his commit *on purpose*. Honestly. And he made things
worse, now actually *affecting* our users. ...
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a
for
> excuses and loopholes, and start doing something good for Gentoo.
So, breaking the tree, just because someone forgot to set the
maintainer field is doing something good for Gentoo? (That's called QA?)
https://archives.gentoo.org/gentoo-commits/message/7f34111f0e45f451d5b3a5a58b0
On 14-12-2017 13:39:18 +0100, Michał Górny wrote:
> Dnia 14 grudnia 2017 13:21:47 CET, Fabian Groffen <grob...@gentoo.org>
> napisał(a):
> >Can we make it a policy to list /what/ QA issues are the justification
> >for commits like these? A description in the commit messa
On 14-12-2017 13:39:18 +0100, Michał Górny wrote:
> Dnia 14 grudnia 2017 13:21:47 CET, Fabian Groffen <grob...@gentoo.org>
> napisał(a):
> >Can we make it a policy to list /what/ QA issues are the justification
> >for commits like these? A description in the commit messa
1 - 100 of 591 matches
Mail list logo
