Summary: | net-misc/gsutil-4.6: fails tests, tries to contact the Internet | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jer, pacho, rich0 |
Priority: | Normal | Keywords: | PMASKED, TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
tinderbox log
build.log |
Description
Diego Elio Pettenò (RETIRED)
2014-10-31 11:58:39 UTC
logs must be attached Created attachment 387892 [details]
tinderbox log
Created attachment 387894 [details]
build.log
(In reply to SpanKY from comment #1) > logs must be attached Says who, exactly? Comment on attachment 387892 [details]
tinderbox log
Jer's one is displayed in a more understandable way ;)
(In reply to Jeroen Roovers from comment #4) > (In reply to SpanKY from comment #1) > > logs must be attached > > Says who, exactly? I think he is thinking on: https://wiki.gentoo.org/wiki/Bugzilla_HOWTO#Required_Information @vapier, personally, I would simply modify that rule there. The sense of the rule is to ensure logs are not dropped and are accessible even if the external provider decides to remove them at some point (like pastebin). But, *in this concrete case* the logs won't be removed if flameeyes keeps paying for that to Amazon and, in the worst case, I think you could still close as NEEDINFO if the log disappears at some point and, obviously, you cannot access to them for fixing bugs. But, as soon as the file is accessible (and will be accessible for the future), I see no reason on forcing flameeyes to attach it here too. (In reply to Pacho Ramos from comment #6) i already told Diego about the problems with his system, and it's trivial to resolve -- we already have python code to attach files. relying on one developer to keep files in place & pay money to amazon is not acceptable. Comment on attachment 387894 [details]
build.log
Jer: cut the sh*t
(In reply to SpanKY from comment #7) > (In reply to Pacho Ramos from comment #6) > > i already told Diego about the problems with his system, and it's trivial to > resolve -- we already have python code to attach files. relying on one > developer to keep files in place & pay money to amazon is not acceptable. I'd love to see an infra-hosted tinderbox but nobody has stepped up to build one yet. Likewise, nobody is stepping up to attach the files. Since nobody wants to do anything, the question is what to do with the information we do have. Closing bugs won't make the problem go away. I'm all for building better solutions, but in their absence the question is what to do with the solutions we have. This is a volunteer effort, so we can no more force a maintainer to fix a bug than we can force somebody to report a bug. I can say that we'll all be better off if people contribute where they can. The typical model is one maintainer has to deal with lots of bugs, so the bug submitters can make the job of the maintainer easier by doing the work up-front to document the bug. Since submitter time is usually more plentiful that maintainer time it is in everybody's interest to do this. However, with a tinderbox the dynamic changes. You end up with one tinderbox caretaker and many maintainers/bugs. It can make sense to distribute the tinderbox report cleanup and not just dump that on the tinderbox operator. Of course, the best possible solution is to improve the tinderbox, and if somebody can make that happen constructively that would be wonderful. Simply asking somebody to improve things won't necessarily make it happen. (In reply to Richard Freeman from comment #9) there's already a tool that supports attaching files to bugs via command line or python (pybugz), so there's really no reason the code Diego has written & running can't be updated to use it. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e6d4c9e216ec158e7f2e5d866e5928a0667781e6 commit e6d4c9e216ec158e7f2e5d866e5928a0667781e6 Author: David Seifert <soap@gentoo.org> AuthorDate: 2023-03-18 16:42:41 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2023-03-18 16:42:41 +0000 net-misc/gsutil: treeclean Closes: https://bugs.gentoo.org/527608 Closes: https://bugs.gentoo.org/687694 Closes: https://bugs.gentoo.org/718976 Closes: https://bugs.gentoo.org/857900 Closes: https://bugs.gentoo.org/861632 Signed-off-by: David Seifert <soap@gentoo.org> net-misc/gsutil/Manifest | 1 - net-misc/gsutil/files/dummy.boto | 6 -- net-misc/gsutil/files/gsutil-4.41-tests.patch | 14 ---- net-misc/gsutil/files/gsutil-4.50-boto-tests.patch | 44 ----------- net-misc/gsutil/files/gsutil-4.50-tests.patch | 57 -------------- net-misc/gsutil/gsutil-5.9.ebuild | 91 ---------------------- net-misc/gsutil/metadata.xml | 16 ---- profiles/package.mask | 1 - 8 files changed, 230 deletions(-) |