Search results for query "contribute to wiki"
- 27656 messages
Re: automated rpm signing woes
by John Florian
I saw mention of FPO's rollout of new koji hubs and builders and am
wondering does that mean integration is now possible again with sigul?
If so, are any special side repos for special builds necessary? Is it
best to deploy all of koji and sigul both on F35 or is there some other
combination that works better or is required?
John Florian
On 2021-11-16 10:36, John Florian wrote:
> On 2021-11-11 18:38, Kevin Fenzi wrote:
>> On Thu, Nov 11, 2021 at 09:14:56AM -0500, John Florian wrote:
>>> What is the recommended solution for this these days? What is
>>> fedoraproject.org using?
>> sigul.
>>
>>> I presently have a setup using Sigul on CentOS 7 but that's leading to my
>>> current problem of being unable to upgrade anything. I can't find anything
>>> workable with CentOS 8, meanwhile my Koji Hub is stuck at 1.21.1 because I'm
>>> unaware of any newer builds via epel7. My Koji Builders are now stuck at
>>> Fedora 33 because tasks fail if they have a newer version of Koji than the
>>> Hub.
>> koji has moved to python3, so I can't update epel7 koji until I move it
>> to python3. There's still some prereq packages needed:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1862810
>> I keep wanting to work on this, but have had no time. ;(
>>
>> Perhaps with holidays up soon I can finally get to it.
>
>
> Please let me know if I can be of any help. I do Python all day and
> have been under the hood of koji a fair bit, but sigul much less.
> Like everyone else, I'm always busy, but I like to help where I can,
> even if it's just testing or writing docs.
>
>
>>> My attempts at moving Sigul to CentOS 8 Stream have just led to one bug
>>> after another using the only build I could find, located athttps://kojipkgs.fedoraproject.org/repos-dist/epel$releasever-infra/lat....
>>> I've fumbled my way through a few fixes and would be happy to contribute
>>> when I can or, at least, report bugs. However, whenever I go to
>>> https://pagure.io/sigul/, the apparent upstream for the project, I see the
>>> last commit as 10 months ago, the last comment on any issue as 7 months ago,
>>> no issues closed, no PRs merged. Is it dead?
>> it's... sleeping. :)
>>
>> The primary developer, Patrick is busy on other stuff and hasn't had
>> much time for it lately.
>
> That's fair. We all have fires to put out and I'm not going to tell
> anyone which fire is bigger. I saw he's put a lot of work into
> improvements and I've been hoping to benefit from those, but ... (below)
>
>> We are using a el8 version from our infra tags:
>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1668924
> I found that and have tried to use it, but without docs for migrating
> the schema I wasn't sure how to populate the new keys.keytype field
> that didn't exist back with sigul-0.101-1.el7. (The new field was
> preventing a simple dump & load.) I thought I'd be clever and `sigul
> new-key tempkey` to see what value a brand new key would have and
> mimic that by editing a data dump from the old server before importing
> into the new server. However, that failed, first with an error because
> the variable key_name was undefined. I took a reasonable guess at a
> patch for that problem but then ran into a unique constraint error
> from the database. Since the project is "sleeping" I just now created
> https://pagure.io/sigul/issue/15 to report this problem, but am
> confounded how fpo is making this work.
>> We don't have it in epel8 because python-nss was dropped there (and
>> upstream). Patrick plans to re-write things so it doesn't use python-nss
>> anymore, but hasn't yet done so.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1933855
>> tracks sigul in epel8.
>>
>> Sorry this is such a mess. ;(
>>
>> kevin
> No apologies needed, it's FOSS. I do really appreciate the effort of
> all involved and the difficulty of taming so many finicky parts to
> harmonize.
>>
>> _______________________________________________
>> buildsys mailing list --buildsys(a)lists.fedoraproject.org
>> To unsubscribe send an email tobuildsys-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:https://lists.fedoraproject.org/archives/list/buildsys@lists.fed...
>> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
>
> John Florian
>
> _______________________________________________
> buildsys mailing list --buildsys(a)lists.fedoraproject.org
> To unsubscribe send an email tobuildsys-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:https://lists.fedoraproject.org/archives/list/buildsys@lists.fed...
> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
2 years, 2 months
Re: F26 Release Notes help needed
by Petr Bokoc
Correction: Turns out I remembered the registration process wrong. After
you register in FAS, log in to pagure once, and then send me your
nickname either in a mail (off-list) or on IRC - I have to add you to
the "fedora-docs" Pagure group before you're able to assign issues to
yourself.
Apologies for the confusion.
Petr
On 06/22/2017 12:58 PM, Petr Bokoc wrote:
> Hi everyone, let's revive this a little bit.
>
> We're going to have to produce some release notes for Fedora 26. I've
> seen a few people on the list in the past mention they'd like to help,
> and writing these is probably the best way to start with that.
>
> Note: There seems to be some confusion among newcomers: the Docs
> Project doesn't maintain the Wiki, we take care (well,
> occasionally...) of docs.fedoraproject.org. The guides published there
> are currently written in DocBook XML[0], stored in Git repositories on
> Pagure[1], and published using publican[2]. We have some vague-ish
> plans to replace most of that with something more modern and
> accessible to newcomers, since docbook really isn't user friendly, but
> that's not going to happen for F26, so for this release we'll have to
> stick with our current tools.
>
> Luckily, Release Notes in particular can be done in a way that avoids
> DocBook, Git, and Publican altogether; they're short bits of text I or
> someone else with experience can mark up and commit for you - you just
> need find the right information and write them.
>
> The only thing you will need is a Pagure account - which is actually
> your FAS account. If you don't have one yet, make one[3], make sure to
> sign the CLA (Contributor License Agreement), log in to FAS, and apply
> to join the "docs" group; I'll approve you once I see your
> application. That should give you permissions to comment on Pagure
> issues, which is where I'd like you to save what you write for release
> notes unless we agree on some other approach. Also, I'm pretty sure
> gaining membership in a group will allow you to edit the wiki, if
> you're interested in that - wheee!
>
> If anyone has any questions, contact me on this mail or in
> #fedora-docs on IRC; my time zone is CEST (UTC+2) and I'm online
> mostly during afternoons on workdays.
>
> ===HOW DO I ACTUALLY CONTRIBUTE?===
>
> Lately our main focus was covering Accepted Changes in our release
> notes, since that's an easy and expansive source of information about
> changes in each release.
>
> I took the liberty of opening an Issue on Pagure for every change; you
> can see them here: https://pagure.io/release-notes/issues
>
> Contributors should:
>
> * go through the list and find something to write about that isn't
> assigned to anyone yet (the rightmost column), open the issue and the
> link to Wiki inside it
>
> * on the wiki page, you'll find three important pieces of info: 1) a
> tracker bug in Bugzilla, 2) change owner(s) and 3) a short, hopefully
> coherent description of the change.
>
> 1) the tracker bug is somewhat useful when trying to determine if
> the change actually made it into the release. Don't count on it really
> being there, in theory changes that are postponed or canceled should
> be deleted from the wiki or at least marked somehow, but they often
> aren't. Therefore, check the bug's status: if it's on ON_QA, VERIFIED,
> RELEASE_PENDING or CLOSED-CURRENTRELEASE, it's safe to assume it did
> make it in. If it has a status like NEW, ASSIGNED, or MODIFIED,
> contact the owner before you start writing and ask them if the change
> made it to F26. If it didn't, we shouldn't be writing about it.
>
> 2) the change owners are people you should contact a) to check if
> the change still applies if required (see above), and b) when you
> write a draft release note so they can check it for technical accuracy.
>
> 3) the description should give you some information so you can get
> started on your draft.
>
> * once you have something you believe to be publishable, go back to
> the Issue on pagure and save your text as a comment there.
>
> Some additional notes:
>
> * the current issue list (or the changeset wiki page) is by no means
> exhaustive. You're very welcome to add more release notes for things
> like changes in widely used components from kernel to firefox to
> freeciv. Just make sure you're writing about a component version that
> will be available in Fedora 26 upon release, not a previous version,
> *not the latest upstream version*. It's common for Fedora to come out
> with something like Firefox X, but on its website you can already
> download version X+1 at the same time. We're writing this about
> Fedora, so keep that in mind. The previous sentence also means that we
> shouldn't be covering any third-party repos, proprietary drivers, etc.
> - Fedora only.
>
> * there often are upstream release notes that are much more exhaustive
> than what we would write, so use them. I'm talking about changes like
> "upgrade Boost to 1.63" - Boost version 1.63 already has its own
> release notes, and this change just means Fedora is using that
> version. In that case, you can just write as much, maybe provide a
> short list of the most important changes, and then link to Boost's
> website for the full version, like we usually do[4].
>
> * the current release date is July 11, so please, make sure you're
> done two days before so I have time to convert everything. If you
> can't make it, please send me an e-mail and drop (unassign) any issues
> you can't do in time. There's no shame in backing out, we all have
> other things to do, but please make sure someone can still pick it up.
>
> ===BUT PETR, HOW ARE WE GOING TO PUBLISH? WE STILL NEED THAT ANCIENT
> PUBLICAN VERSION THAT ONLY RUNS ON A FEDORA RELEASE THAT CAN'T PUSH TO
> PAGURE!===
>
> Yeah, but we should be able to publish by building the website in the
> VM like we used to until now, and then mounting the VM's storage on a
> more modern system that can push and doing the last step that way.
>
> Good luck everyone, and again, ping or e-mail me if you have any
> questions.
>
> Petr
>
> ---
> [0] http://tdg.docbook.org/tdg/4.5/docbook.html
> [1] https://pagure.io/group/fedora-docs
> [2] https://jfearn.fedorapeople.org/en-US/Publican/
> [3] https://admin.fedoraproject.org/accounts/
> [4]
> https://docs.fedoraproject.org/en-US/Fedora/25/html/Release_Notes/sect-Re...
> _______________________________________________
> docs mailing list -- docs(a)lists.fedoraproject.org
> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
--
Petr Bokoc (irc: pbokoc)
Technical Writer
Customer Content Services
Red Hat Czech, s. r. o.
Purkynova 99
612 45 Brno, Czech Republic
6 years, 10 months
sgallagh pushed to js-jquery (epel8). "Merge branch 'master' into
epel8"
by notifications＠fedoraproject.org
Notification time stamped 2020-04-17 17:47:38 UTC
From 99c445f613c64c6e36fe0a25b4c0fb4d1705be98 Mon Sep 17 00:00:00 2001
From: Stephen Gallagher <sgallagh(a)redhat.com>
Date: Apr 17 2020 17:47:28 +0000
Subject: Merge branch 'master' into epel8
---
diff --git a/.gitignore b/.gitignore
index e69de29..77cd870 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1,9 @@
+*.swp
+jquery-*/*
+/js-jquery-4dec426aa2a6cbabb1b064319ba7c272d594a688.tar.gz
+/js-jquery-8f2a9d9272d6ed7f32d3a484740ab342c02541e0.tar.gz
+/jquery-2.2.4.tar.gz
+/jquery-3.2.1.tar.gz
+/jquery-3.3.1.tar.gz
+/jquery-3.5.0.tar.gz
+/jquery_3.5.0_node_modules.tar.gz
diff --git a/js-jquery-disable-gzip-js.patch b/js-jquery-disable-gzip-js.patch
new file mode 100644
index 0000000..a76ca1c
--- /dev/null
+++ b/js-jquery-disable-gzip-js.patch
@@ -0,0 +1,29 @@
+From da2978fde58fb84175ae0b9b7a83c963430a7747 Mon Sep 17 00:00:00 2001
+From: Stephen Gallagher <sgallagh(a)redhat.com>
+Date: Mon, 13 Apr 2020 14:04:00 -0400
+Subject: [PATCH] Disable gzip-js
+
+Signed-off-by: Stephen Gallagher <sgallagh(a)redhat.com>
+---
+ Gruntfile.js | 1 -
+ 1 file changed, 1 deletion(-)
+
+diff --git a/Gruntfile.js b/Gruntfile.js
+index 486a0f303932734b868b065d3c7b99a36002fac5..5ff8cdec4810d0cdf2180da2f4432020f91e6b10 100644
+--- a/Gruntfile.js
++++ b/Gruntfile.js
+@@ -11,11 +11,10 @@ module.exports = function( grunt ) {
+ } catch ( e ) {}
+ return data;
+ }
+
+ var fs = require( "fs" ),
+- gzip = require( "gzip-js" ),
+ isTravis = process.env.TRAVIS,
+ travisBrowsers = process.env.BROWSERS && process.env.BROWSERS.split( "," );
+
+ if ( !grunt.option( "filename" ) ) {
+ grunt.option( "filename", "jquery.js" );
+--
+2.26.0
+
diff --git a/js-jquery.spec b/js-jquery.spec
new file mode 100644
index 0000000..cbd3061
--- /dev/null
+++ b/js-jquery.spec
@@ -0,0 +1,153 @@
+Name: js-jquery
+Version: 3.5.0
+Release: 3%{?dist}
+Summary: JavaScript DOM manipulation, event handling, and AJAX library
+BuildArch: noarch
+
+%global ver_x %(echo %{version} | cut -d. -f1)
+%global ver_y %(echo %{version} | cut -d. -f2)
+%global ver_z %(echo %{version} | cut -d. -f3)
+
+License: MIT
+URL: https://jquery.com/
+Source0: https://github.com/jquery/jquery/archive/%{version}/jquery-%{version}.tar.gz
+# Created by ./update_sources.sh <version>
+Source1: jquery_%{version}_node_modules.tar.gz
+
+# disable gzip-js during build
+Patch1: %{name}-disable-gzip-js.patch
+
+
+BuildRequires: web-assets-devel
+BuildRequires: nodejs-packaging
+BuildRequires: nodejs
+
+Provides: jquery = %{version}-%{release}
+Provides: %{name}-static = %{version}-%{release}
+Provides: %{name}%{ver_x} = %{version}-%{release}
+Provides: %{name}%{ver_x}-static = %{version}-%{release}
+
+Requires: web-assets-filesystem
+
+# Bundles sizzle (https://github.com/jquery/sizzle/) in node_modules/sizzle
+# Get version from package.json
+Provides: bundled(sizzle) = 2.3.5
+Provides: bundled(js-sizzle) = 2.3.5
+
+
+%description
+jQuery is a fast, small, and feature-rich JavaScript library. It makes things
+like HTML document traversal and manipulation, event handling, animation, and
+Ajax much simpler with an easy-to-use API that works across a multitude of
+browsers. With a combination of versatility and extensibility, jQuery has
+changed the way that millions of people write JavaScript.
+
+%prep
+%autosetup -n jquery-%{version} -v -p1
+
+#remove precompiled stuff
+rm -rf dist/*
+
+# Install the cached node modules
+tar xf %{SOURCE1}
+
+
+%build
+./node_modules/grunt-cli/bin/grunt -v 'build:*:*' uglify
+
+
+%check
+./node_modules/grunt-cli/bin/grunt -v 'build:*:*' test:prepare test:fast
+
+
+%install
+%global installdir %{buildroot}%{_jsdir}/jquery
+
+mkdir -p %{installdir}/%{version}
+cp -p dist/* %{installdir}/%{version}
+
+mkdir -p %{buildroot}%{_webassetdir}
+ln -s ../javascript/jquery %{buildroot}%{_webassetdir}/jquery
+
+ln -s %{version} %{installdir}/latest
+ln -s %{version} %{installdir}/%{ver_x}
+ln -s %{version} %{installdir}/%{ver_x}.%{ver_y}
+
+
+%files
+%{_jsdir}/jquery
+%{_webassetdir}/jquery
+%doc AUTHORS.txt CONTRIBUTING.md LICENSE.txt README.md
+
+
+%changelog
+* Fri Apr 17 2020 Stephen Gallagher <sgallagh(a)redhat.com> - 3.5.0-3
+- Add explicit dependency on nodejs
+
+* Wed Apr 15 2020 Stephen Gallagher <sgallagh(a)redhat.com> - 3.5.0-2
+- Add virtual Provides: for bundled sizzle
+
+* Mon Apr 13 2020 Stephen Gallagher <sgallagh(a)redhat.com> - 3.5.0-1
+- Update to 3.5.0
+- Bundle the build dependencies in the source RPM
+- Drop unneeded patches
+
+* Wed Jan 29 2020 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.3.1-4
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
+
+* Thu Jul 25 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.3.1-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
+
+* Fri Feb 01 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.3.1-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
+
+* Wed Jul 18 2018 Christopher Tubbs <ctubbsii(a)fedoraproject.org> - 3.3.1-1
+- Update to 3.3.1; fixes rhbz#1536772 rhbz#1445079 rhbz#1591846 Security fix for
+ CVE-2012-6708
+
+* Fri Jul 13 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.2.1-4
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
+
+* Wed Feb 07 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.2.1-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
+
+* Wed Jul 26 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 3.2.1-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
+
+* Wed Apr 12 2017 Christopher Tubbs <ctubbsii(a)fedoraproject.org> - 3.2.1-1
+- Update to jQuery 3.2.1
+
+* Tue Apr 11 2017 Christopher Tubbs <ctubbsii(a)fedoraproject.org> - 2.2.4-3
+- Update provides in prep for js-jquery package rename to js-jquery2
+
+* Fri Feb 10 2017 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.2.4-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
+
+* Tue Dec 20 2016 Christopher Tubbs <ctubbsii(a)fedoraproject.org> - 2.2.4-1
+- Update to 2.2.4 and backport XSS patch (bz#1399550,bz#1399549)
+
+* Thu Feb 04 2016 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.1.3-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
+
+* Wed Jun 17 2015 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org> - 2.1.3-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
+
+* Wed Mar 04 2015 T.C. Hollingsworth <tchollingsworth(a)gmail.com> - 2.1.3-1
+- new upstream release 2.1.3
+ http://blog.jquery.com/2014/12/18/jquery-1-11-2-and-2-1-3-released-safari...
+
+* Tue Oct 21 2014 T.C. Hollingsworth <tchollingsworth(a)gmail.com> - 2.1.1-4
+- drop unneccessary symlinks
+
+* Tue Jun 03 2014 T.C. Hollingsworth <tchollingsworth(a)gmail.com> - 2.1.1-3
+- follow the github SourceURL guidelines
+
+* Sat May 31 2014 T.C. Hollingsworth <tchollingsworth(a)gmail.com> - 2.1.1-2
+- drop sed hack now that grunt is fixed
+
+* Fri May 30 2014 T.C. Hollingsworth <tchollingsworth(a)gmail.com> - 2.1.1-1
+- update to 2.1.1
+- use system packages for build (with help from Jamie Nguyen)
+
+* Wed Mar 19 2014 T.C. Hollingsworth <tchollingsworth(a)gmail.com> - 2.1.0-0.1
+- initial package
diff --git a/sources b/sources
index e69de29..80c4549 100644
--- a/sources
+++ b/sources
@@ -0,0 +1,2 @@
+SHA512 (jquery-3.5.0.tar.gz) = a59782f614915ccca99b2529d473961697a28533e85f186e014cc481690fb7480e7c7f7cb9ace49fa0494fa7ab270487c914ce0d9109eb9cdd6e4b58c931ac91
+SHA512 (jquery_3.5.0_node_modules.tar.gz) = b41a3989334a9fa77ff19694459506f50476a0d7de4c022ace904546dd2c18c05d5b3057e36196cf8f0a47de6dec5bd78f32275eddc49cc3fdfefb8000b6a168
diff --git a/update-sources.sh b/update-sources.sh
new file mode 100755
index 0000000..b9059c2
--- /dev/null
+++ b/update-sources.sh
@@ -0,0 +1,118 @@
+#!/bin/bash
+
+# Created by argbash-init v2.8.1
+# ARG_POSITIONAL_SINGLE([version])
+# ARG_DEFAULTS_POS()
+# ARG_HELP([Download and cache all build dependencies for jquery])
+# ARGBASH_GO()
+# needed because of Argbash --> m4_ignore([
+### START OF CODE GENERATED BY Argbash v2.8.1 one line above ###
+# Argbash is a bash code generator used to get arguments parsing right.
+# Argbash is FREE SOFTWARE, see https://argbash.io for more info
+
+
+die()
+{
+ local _ret=$2
+ test -n "$_ret" || _ret=1
+ test "$_PRINT_HELP" = yes && print_help >&2
+ echo "$1" >&2
+ exit ${_ret}
+}
+
+
+begins_with_short_option()
+{
+ local first_option all_short_options='h'
+ first_option="${1:0:1}"
+ test "$all_short_options" = "${all_short_options/$first_option/}" && return 1 || return 0
+}
+
+# THE DEFAULTS INITIALIZATION - POSITIONALS
+_positionals=()
+_arg_version=
+# THE DEFAULTS INITIALIZATION - OPTIONALS
+
+
+print_help()
+{
+ printf '%s\n' "Download and cache all build dependencies for jquery"
+ printf 'Usage: %s [-h|--help] <version>\n' "$0"
+ printf '\t%s\n' "-h, --help: Prints help"
+}
+
+
+parse_commandline()
+{
+ _positionals_count=0
+ while test $# -gt 0
+ do
+ _key="$1"
+ case "$_key" in
+ -h|--help)
+ print_help
+ exit 0
+ ;;
+ -h*)
+ print_help
+ exit 0
+ ;;
+ *)
+ _last_positional="$1"
+ _positionals+=("$_last_positional")
+ _positionals_count=$((_positionals_count + 1))
+ ;;
+ esac
+ shift
+ done
+}
+
+
+handle_passed_args_count()
+{
+ local _required_args_string="'version'"
+ test "${_positionals_count}" -ge 1 || _PRINT_HELP=yes die "FATAL ERROR: Not enough positional arguments - we require exactly 1 (namely: $_required_args_string), but got only ${_positionals_count}." 1
+ test "${_positionals_count}" -le 1 || _PRINT_HELP=yes die "FATAL ERROR: There were spurious positional arguments --- we expect exactly 1 (namely: $_required_args_string), but got ${_positionals_count} (the last one was: '${_last_positional}')." 1
+}
+
+
+assign_positional_args()
+{
+ local _positional_name _shift_for=$1
+ _positional_names="_arg_version "
+
+ shift "$_shift_for"
+ for _positional_name in ${_positional_names}
+ do
+ test $# -gt 0 || break
+ eval "$_positional_name=\${1}" || die "Error during argument parsing, possibly an Argbash bug." 1
+ shift
+ done
+}
+
+parse_commandline "$@"
+handle_passed_args_count
+assign_positional_args 1 "${_positionals[@]}"
+
+# OTHER STUFF GENERATED BY Argbash
+
+### END OF CODE GENERATED BY Argbash (sortof) ### ])
+# [ <-- needed because of Argbash
+
+version=$_arg_version
+rm -rf jquery-$version jquery-$version.tar.gz jquery_${version}_node_modules.tar.gz
+wget https://github.com/jquery/jquery/archive/$version/jquery-$version.tar.gz
+
+tar xf jquery-$version.tar.gz
+
+pushd jquery-$version
+npm install --save-dev
+tar cfz ../jquery_${version}_node_modules.tar.gz node_modules
+
+# Husky tries to install a git hook that doesn't play well with dist-git
+npm uninstall husky
+popd
+
+fedpkg new-sources jquery-$version.tar.gz jquery_${version}_node_modules.tar.gz
+
+# ] <-- needed because of Argbash
https://src.fedoraproject.org/rpms/js-jquery/c/99c445f613c64c6e36fe0a25b4...
4 years
[389-users] Re: cockpit doubt, or rebuild Cockpit plugin
by Mark Reynolds
On 3/4/20 10:06 PM, William Brown wrote:
>
>> On 4 Mar 2020, at 23:14, Alberto Viana <albertocrj(a)gmail.com> wrote:
>>
>> William/Mark
>>
>> In master branch this function is checkPackageAndLoad() and it's found in src/cockpit/389-console/src/ds.jsx, or in older versions it's somewhere in ds.js (it has a different function name though), then just rebuild cockpit
>>
>> Already did that (even before your suggestion), but I just wonder like William if there's no "smart" way to check if already has 389 in the system.
> William does wonder, and William also knows Mark and Simon who wrote the cockpit tooling are very smart. So perhaps there is a reason for why it was done like this that I'm not aware of.
>
> Generally the main reason I hit things like this is because I use prefix builds in my environment, so /opt/dirsrv. I'm wondering if an alternate option here Mark is to use the presence of a defaults.inf in one of the known locations or via PREFIX, similar to src/lib389/lib389/paths.py, or even exposing that in a tool like ds_present that returns a 1/0 based on if a defaults.inf can be found. That would solve the case with lib389 present but not a 389-ds-base. Simply loading Paths() isn't enough, because it's lazy loaded. but you could do Paths().with_systemd to trigger the read?
>
> Just an idea :)
There are several checks we do before we load the Directory Server UI.
First we check if 389-ds-base is even installed. This is the rpm
check. If it is installed, then we check if there is at least one
instance available (via lib389). If any of these conditions are not met
we load a unique page describing the problem and how to fix it.
At this time the cockpit plugin will NOT work with custom PREFIX'ed
builds as there is no way to tell cockpit or lib389 that DS is under a
custom location. Checking for defaults.inf might be an option to find
and set the PREFIX env var when calling the CLI from the UI, but it
would still require a significant amount of grunt work to the UI source
code to make this work. I wonder if the ".dsrc" functionality could be
extended to handler this case and set the PREFIX in lib389 for us?
Contributions are always welcome :-)
>
>
>> Thanks anyway.
>>
>> Alberto Viana
>>
>> On Tue, Mar 3, 2020 at 9:32 PM William Brown <wbrown(a)suse.de> wrote:
>>
>>
>>> On 4 Mar 2020, at 04:07, Mark Reynolds <mreynolds(a)redhat.com> wrote:
>>>
>>>
>>>
>>> On 3/3/20 1:01 PM, Mark Reynolds wrote:
>>>>
>>>> On 3/3/20 12:28 PM, Alberto Viana wrote:
>>>>> Hi Guys,
>>>>>
>>>>> I'm testing some versions of 389 and I realise that in newer versions, cockpit stopped to work to me:
>>>>>
>>>>> There is no 389-ds-base package installed on this system. Sorry there is nothing to manage...
>>>>>
>>>>> In my case (due to internal reasons) we compile our version of 389.
>>>>>
>>>>> Is this an expected behavior? Is it suppose to only work if I have a 389 package installed in the system? There's any workaround for that?
>>>> It's looking for an rpm via:
>>>>
>>>> rpm -q 389-ds-base
>>>>
>>>> Just install the official rpm, and overwrite it with your private build.
>>>>
>>> If you are doing a private build anyway, you could just remove this check from the UI code:
>>>
>>> In master branch this function is checkPackageAndLoad() and it's found in src/cockpit/389-console/src/ds.jsx, or in older versions it's somewhere in ds.js (it has a different function name though), then just rebuild cockpit
>> Couldn't we do an instance list instead? That way it would catch anything that's in /etc/dirsrv or /data?
>>
>>
>>>
>>>
>>>>
>>>> HTH,
>>>>
>>>> Mark
>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 389-users mailing list --
>>>>> 389-users(a)lists.fedoraproject.org
>>>>>
>>>>> To unsubscribe send an email to
>>>>> 389-users-leave(a)lists.fedoraproject.org
>>>>>
>>>>> Fedora Code of Conduct:
>>>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>>>>
>>>>> List Guidelines:
>>>>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>>>>
>>>>> List Archives:
>>>>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
>>>> --
>>>>
>>>> 389 Directory Server Development Team
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 389-users mailing list --
>>>> 389-users(a)lists.fedoraproject.org
>>>>
>>>> To unsubscribe send an email to
>>>> 389-users-leave(a)lists.fedoraproject.org
>>>>
>>>> Fedora Code of Conduct:
>>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>>>
>>>> List Guidelines:
>>>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>>>
>>>> List Archives:
>>>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
>>> --
>>>
>>> 389 Directory Server Development Team
>>>
>>> _______________________________________________
>>> 389-users mailing list -- 389-users(a)lists.fedoraproject.org
>>> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
>>> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
>> —
>> Sincerely,
>>
>> William Brown
>>
>> Senior Software Engineer, 389 Directory Server
>> SUSE Labs
>>
> —
> Sincerely,
>
> William Brown
>
> Senior Software Engineer, 389 Directory Server
> SUSE Labs
> _______________________________________________
> 389-users mailing list -- 389-users(a)lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
--
389 Directory Server Development Team
4 years, 2 months
[java-1.8.0-openjdk/f19] Sync with f20
by jiri vanek
commit 466fe3e69b8c6e441ca9afefe67fbdce9deb026f
Author: Jiri Vanek <jvanek(a)redhat.com>
Date: Fri Oct 24 14:22:33 2014 +0200
Sync with f20
java-1.8.0-openjdk.spec | 48 +++++++++++++++++++++++++++++++---
removeSunEcProvider-RH1154143.patch | 23 ++++++++++++++++
2 files changed, 66 insertions(+), 5 deletions(-)
---
diff --git a/java-1.8.0-openjdk.spec b/java-1.8.0-openjdk.spec
index 8f45046..314cdb7 100644
--- a/java-1.8.0-openjdk.spec
+++ b/java-1.8.0-openjdk.spec
@@ -128,7 +128,7 @@
Name: java-%{javaver}-%{origin}
Version: %{javaver}.%{updatever}
-Release: 0.%{buildver}%{?dist}
+Release: 2.%{buildver}%{?dist}
# java-1.5.0-ibm from jpackage.org set Epoch to 1 for unknown reasons,
# and this change was brought into RHEL-4. java-1.5.0-ibm packages
# also included the epoch in their virtual provides. This created a
@@ -194,6 +194,7 @@ Patch6: disable-doclint-by-default.patch
Patch7: include-all-srcs.patch
# Problem discovered with make 4.0
Patch11: hotspot-build-j-directive.patch
+Patch12: removeSunEcProvider-RH1154143.patch
#
# OpenJDK specific patches
@@ -279,7 +280,6 @@ Provides: java8-fonts = %{epoch}:%{version}
%description
The OpenJDK runtime environment.
-
%package headless
Summary: OpenJDK Runtime Environment
Group: Development/Languages
@@ -429,6 +429,10 @@ sh %{SOURCE12}
%patch3
%patch4
%patch5
+%patch6
+%patch7
+%patch11
+%patch12
%patch99
@@ -589,6 +593,9 @@ if [ -f "$ZERO_JVM" ] ; then
nm -aCl "$ZERO_JVM" | grep javaCalls.cpp
fi
+# Check src.zip has all sources. See RHBZ#1130490
+jar -tf $JAVA_HOME/src.zip | grep Unsafe
+
%install
rm -rf $RPM_BUILD_ROOT
STRIP_KEEP_SYMTAB=libjvm*
@@ -1126,20 +1133,51 @@ exit 0
%{_jvmdir}/%{jredir}/lib/accessibility.properties
%changelog
+* Fri Oct 24 2014 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.25-2.b18
+- added patch12,removeSunEcProvider-RH1154143
+- Add check for src.zip completeness. See RH1130490 (by sgehwolf(a)redhat.com)
+- Resolves: rhbz#1125260
+
+* Mon Oct 20 2014 Omair Majid <omajid(a)redhat.com> - 1:1.8.0.25-1.b18
+- Apply patches accidentally left out
+
* Wed Oct 15 2014 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.25-0.b18
- updated to security u25
-- sync with f20
+- partial sync with f21
+
+* Wed Sep 17 2014 Omair Majid <omajid(a)redhat.com> - 1:1.8.0.10-10.b26
+- Remove LIBDIR and funny definition of _libdir.
+- Fix rpmlint warnings about macros in comments.
+
+* Fri Aug 22 2014 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.11-9.b12
+- fixed update to f21
+ - alternatrives forced to removal if there is more then one jdk even if it si update
+ - and of course in case of removal
+ - note: jdk f20 do not support multiple installs, jdk f21 do
+
+* Fri Aug 15 2014 Omair Majid <omajid(a)redhat.com> - 1:1.8.0.11-8.b12
+- Include all sources in src.zip
+- Resolves rhbz#1130490
* Mon Jul 21 2014 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.11-7.b12
- removed legacy aarch64 switches
- --with-jvm-variants=client and --disable-precompiled-headers
- added patch patch9999 enableArm64.patch to enable new hotspot
+
+* Tue Jul 15 2014 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.11-5.b12
- Attempt to update aarch64 *jdk* to u11b12, by resticting aarch64 sources to hotpot only
-- partial sync with f20
+- partial sync with f21
* Tue Jul 15 2014 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.11-1.b12
- updated to security u11b12
+* Wed May 28 2014 Omair Majid <omajid(a)redhat.com> - 1:1.8.0.5-4.b13
+- Backport fix for JDK-8012224
+
+* Fri May 16 2014 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.5-3.b13
+- Disable doclint for compatiblity
+- Patch contributed by Andrew John Hughes
+
* Wed Apr 23 2014 Omair Majid <omajid(a)redhat.com> - 1:1.8.0.5-2.b13
- Change make flags to fix debuginfo generation
- Fix suggested by Yasumasa Suenaga
@@ -1228,7 +1266,7 @@ exit 0
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
* Fri Aug 02 2013 Deepak Bhole <dbhole(a)redhat.com> - 1:1.8.0.0-0.15.b89
-- Added a missing includes patch (#302/%{name}-arm64-missing-includes.patch)
+- Added a missing includes patch (#302/%%{name}-arm64-missing-includes.patch)
- Added --disable-precompiled-headers for arm64 build
* Mon Jul 29 2013 Jiri Vanek <jvanek(a)redhat.com> - 1:1.8.0.0-0.14.b89
diff --git a/removeSunEcProvider-RH1154143.patch b/removeSunEcProvider-RH1154143.patch
new file mode 100644
index 0000000..8b9ced9
--- /dev/null
+++ b/removeSunEcProvider-RH1154143.patch
@@ -0,0 +1,23 @@
+--- jdk8/jdk/src/share/lib/security/java.security-linux
++++ jdk8/jdk/src/share/lib/security/java.security-linux
+@@ -67,13 +67,13 @@
+ #
+ security.provider.1=sun.security.provider.Sun
+ security.provider.2=sun.security.rsa.SunRsaSign
+-security.provider.3=sun.security.ec.SunEC
+-security.provider.4=com.sun.net.ssl.internal.ssl.Provider
+-security.provider.5=com.sun.crypto.provider.SunJCE
+-security.provider.6=sun.security.jgss.SunProvider
+-security.provider.7=com.sun.security.sasl.Provider
+-security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
+-security.provider.9=sun.security.smartcardio.SunPCSC
++security.provider.3=com.sun.net.ssl.internal.ssl.Provider
++security.provider.4=com.sun.crypto.provider.SunJCE
++security.provider.5=sun.security.jgss.SunProvider
++security.provider.6=com.sun.security.sasl.Provider
++security.provider.7=org.jcp.xml.dsig.internal.dom.XMLDSigRI
++security.provider.8=sun.security.smartcardio.SunPCSC
++
+
+ #
+ # Sun Provider SecureRandom seed source.
9 years, 6 months
release-notes/devel/po nb.po,1.21,1.22
by fedora-docs-commits＠redhat.com
Author: libbe
Update of /cvs/docs/release-notes/devel/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10622
Modified Files:
nb.po
Log Message:
Updated Norwegian Bokmaal translation
Index: nb.po
===================================================================
RCS file: /cvs/docs/release-notes/devel/po/nb.po,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- nb.po 17 Oct 2007 14:14:09 -0000 1.21
+++ nb.po 18 Oct 2007 16:14:05 -0000 1.22
@@ -4,7 +4,7 @@
"Project-Id-Version: Release notes\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2007-10-08 19:42-0400\n"
-"PO-Revision-Date: 2007-10-17 16:13+0100\n"
+"PO-Revision-Date: 2007-10-18 18:13+0100\n"
"Last-Translator: Espen Stefansen <espens(a)svn.gnome.org>\n"
"Language-Team: Norwegian/Bokmaal <i18n-nb(a)lister.ping.uio.no>\n"
"MIME-Version: 1.0\n"
@@ -316,7 +316,7 @@
#: en_US/Security.xml:42(para)
#: en_US/OverView.xml:195(para)
msgid "The <package>glibc</package> package in Fedora 8 now has <ulink url=\"http://people.redhat.com/drepper/sha-crypt.html\">support</ulink> for passwords using SHA256 and SHA512 hashing. Before only DES and MD5 were available. The tools to create passwords have not been extended yet, but if such passwords are created in others ways, <package>glibc</package> will recognize and honor them."
-msgstr ""
+msgstr "<package>glibc</package>-pakken i Fedora 8 har n�� <ulink url=\"http://people.redhat.com/drepper/sha-crypt.html\">st��tte</ulink> for passord som bruker SHA256 og SHA512 hasher. F��r var bare DES og MD5 tilgjengelig. Verkt��yene for �� opprette slike passord har ikke denne muligheten enda, men hvis slike passord er laget p�� andre m��ter, s�� vil <package>glibc</package> gjenkjenne og bruke dem."
#: en_US/Security.xml:52(para)
#: en_US/OverView.xml:205(para)
@@ -365,11 +365,11 @@
#: en_US/ProjectOverview.xml:7(para)
msgid "The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. The Fedora Project is driven by the individuals that contribute to it. As a tester, developer, documenter, or translator, you can make a difference. Refer to <ulink url=\"http://fedoraproject.org/join-fedora.html\"/> for details. For information on the channels of communication for Fedora users and contributors, refer to <ulink url=\"http://fedoraproject.org/wiki/Communicate\"/>."
-msgstr ""
+msgstr "M��let med Fedora Project er �� arbeide med Linux-samfunnet for �� lage en komplett, allmenn-nyttig operativsystem, basert bare p�� programmer av ��pen-kildekode. Fedora Project er drevet av individer som bidrar til det. Som en tester, utvikler, skribent eller oversetter, kan du gj��re en forskjell. G�� til <ulink url=\"http://fedoraproject.org/join-fedora.html\"/> for detaljer. For informasjon om mulige informasjonskanaler for brukere og bidragsytere til Fedora, g�� til <ulink url=\"http://fedoraproject.org/wiki/Communicate\"/>."
#: en_US/ProjectOverview.xml:19(para)
msgid "The Fedora Project is driven by the individuals that contribute to it. As a tester, developer, documenter, or translator, you can make a difference. See <ulink url=\"http://fedoraproject.org/wiki/Join\">http://fedoraproject.org/wiki/Join</ulink> for details. For information on the channels of communication for Fedora users and contributors, refer to <ulink url=\"http://fedoraproject.org/wiki/Communicate\">http://fedoraproject.org/wiki/Communicate</ulink>."
-msgstr ""
+msgstr "Fedora Project er drevet av individer som bidrar til det. Som en tester, utvikler, skribent eller oversetter, kan du gj��re en forskjell. Se <ulink url=\"http://fedoraproject.org/wiki/Join\">http://fedoraproject.org/wiki/Join</ulink> for detaljer. For informasjon om mulige informasjonskanaler for brukere og bidragsytere til Fedora, g�� til <ulink url=\"http://fedoraproject.org/wiki/Communicate\">http://fedoraproject.org/wiki/Communicate</ulink>."
#: en_US/ProjectOverview.xml:29(para)
msgid "In addition to the website, the following mailing lists are available:"
@@ -389,11 +389,11 @@
#: en_US/ProjectOverview.xml:54(para)
msgid "<ulink url=\"mailto:fedora-docs-list@redhat.com\">fedora-docs-list(a)redhat.com</ulink>, for participants of the Documentation Project"
-msgstr ""
+msgstr "<ulink url=\"mailto:fedora-docs-list@redhat.com\">fedora-docs-list(a)redhat.com</ulink>, for deltagere i Documentation Project"
#: en_US/ProjectOverview.xml:61(para)
msgid "To subscribe to any of these lists, send an email with the word \"subscribe\" in the subject to <replaceable><listname>-request</replaceable>, where <replaceable><listname></replaceable> is one of the above list names. Alternately, you can subscribe to Fedora mailing lists through the Web interface at <ulink url=\"http://www.redhat.com/mailman/listinfo/\">http://www.redhat.com/mailman/listinfo/</ulink>."
-msgstr ""
+msgstr "For �� abonnere p�� noen av disse listene, send en e-post med ordet ��subscribe�� i emnefeltet til <replaceable><listenavn>-request</replaceable>, hvor <replaceable><listenavn></replaceable> er en av listenavnene over. Alternativt kan du abonnere p�� Fedoras e-postlister gjennom web-grensesnittet p�� <ulink url=\"http://www.redhat.com/mailman/listinfo/\">http://www.redhat.com/mailman/listinfo/</ulink>."
#: en_US/ProjectOverview.xml:70(para)
msgid "The Fedora Project also uses several IRC (Internet Relay Chat) channels. IRC is a real-time, text-based form of communication, similar to Instant Messaging. With it, you may have conversations with multiple people in an open channel, or chat with someone privately one-on-one. To talk with other Fedora Project participants via IRC, access the Freenode IRC network. Refer to the Freenode website at <ulink url=\"http://www.freenode.net/\">http://www.freenode.net/</ulink> for more information."
@@ -401,7 +401,7 @@
#: en_US/ProjectOverview.xml:82(para)
msgid "Fedora Project participants frequent the #fedora channel on the Freenode network, while Fedora Project developers may often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well. This information may be found on the webpage for the project, and at <ulink url=\"http://fedoraproject.org/wiki/Communicate\">http://fedoraproject.org/wiki/Communicate</ulink>."
-msgstr ""
+msgstr "Deltagere i Fedora Project holder ofte til i kanalen #fedora p�� Freenode-nettverket, mens utviklere ofte kan bli funnet i kanalen #fedora-devel. Noen av de st��rre prosjektene kan ha deres egne kanaler ogs��. Denne informasjonen kan bli funnet p�� prosjektets egne nettsider og p�� <ulink url=\"http://fedoraproject.org/wiki/Communicate\">http://fedoraproject.org/wiki/Communicate</ulink>."
#: en_US/ProjectOverview.xml:91(para)
msgid "In order to talk on the #fedora channel, you need to register your nickname, or <firstterm>nick</firstterm>. Instructions are given when you <command>/join</command> the channel."
@@ -457,7 +457,7 @@
#: en_US/PackageChanges.xml:10(title)
msgid "Package Changes"
-msgstr ""
+msgstr "Pakkeendringer"
#. <note>
#. <title>This list is automatically generated</title>
@@ -805,7 +805,7 @@
#: en_US/Live.xml:112(para)
msgid "This is <emphasis>not</emphasis> a destructive process; any data you currently have on your USB stick <emphasis>is preserved</emphasis>."
-msgstr ""
+msgstr "Dette er <emphasis>ikke</emphasis> en destruktiv prosess; all data du allerede har p�� USB-minnepinnen <emphasis>blir tatt vare p��</emphasis>."
#: en_US/Live.xml:120(title)
msgid "Differences From a Regular Fedora Install"
@@ -970,7 +970,7 @@
#: en_US/Kernel.xml:165(para)
msgid "Refer to <ulink url=\"http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html\">http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html</ulink> for information on reporting bugs in the Linux kernel. You may also use <ulink url=\"http://bugzilla.redhat.com\">http://bugzilla.redhat.com</ulink> for reporting bugs that are specific to Fedora."
-msgstr ""
+msgstr "G�� til <ulink url=\"http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html\">http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html</ulink> for informasjon om hvordan rapportere feil i Linux-kjernen. Du kan ogs�� bruke <ulink url=\"http://bugzilla.redhat.com\">http://bugzilla.redhat.com</ulink> for �� rapportere feil som er spesifikke for Fedora."
#: en_US/Kernel.xml:176(title)
msgid "Preparing for Kernel Development"
@@ -1126,11 +1126,11 @@
#: en_US/Installer.xml:38(title)
msgid "Downloading Large Files"
-msgstr ""
+msgstr "Nedlasting av store filer"
#: en_US/Installer.xml:39(para)
msgid "If you intend to download the Fedora DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2 GiB in size. Tools without this limitation include <command>wget</command> 1.9.1-16 and above, <command>curl</command>, and <command>ncftpget</command>. <application>BitTorrent</application> is another method for downloading large files. For information about obtaining and using the torrent file, refer to <ulink url=\"http://torrent.fedoraproject.org/\">http://torrent.fedoraproject.org/</ulink>."
-msgstr ""
+msgstr "Hvis du har tenkt til �� laste ned Fedora DVD ISO-avbildet, husk p�� at ikke alle nedlastningsverkt��y kan h��ndtere filer som er st��rre enn 2 GB. Verkt��y uten disse begrensningene inkluderer <commend>wget</command> 1.9.1-16 og h��yere, <command>curl</command> og <command>ncftpget</command>. <application>BitTorrent</application> er en annen m��te �� laste ned store filer p��. For informasjon om �� f�� tak i og bruke torrent-filer, g�� til <ulink url=\"http://torrent.fedoraproject.org/\">http://torrent.fedoraproject.org/</ulink>."
#: en_US/Installer.xml:50(para)
msgid "<application>Anaconda</application> tests the integrity of installation media by default. This function works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. The Fedora Project recommends that you test all installation media before starting the installation process and before reporting any installation-related bugs. Many of the bugs reported are actually due to improperly-burned CDs or DVDs."
@@ -1174,11 +1174,11 @@
#: en_US/Installer.xml:119(para)
msgid "Improved Live images support"
-msgstr ""
+msgstr "Forbedret st��tte for Live-avbilder"
#: en_US/Installer.xml:122(para)
msgid "Ability to install from Live image running from RAM or USB stick"
-msgstr ""
+msgstr "Mulighet for �� installere fra et Live-avbilde som kj��rer fra RAM eller USB-minnepinne"
#: en_US/Installer.xml:126(para)
msgid "Improved IEEE-1394 (Firewire) support"
@@ -1334,14 +1334,12 @@
msgstr "Denne seksjonen inneholder informasjon om spr��kst��tte i Fedora 8."
#: en_US/I18n.xml:20(para)
-#, fuzzy
msgid "Localization (translation) of Fedora is coordinated by the <ulink url=\"http://fedoraproject.org/wiki/L10N\">Fedora Localization Project</ulink>."
-msgstr "Send e-post til <ulink url=\"mailto:relnotes@fedoraproject.org\">relnotes(a)fedoraproject.org</ulink>"
+msgstr "Lokaliseringen (oversettelsen) av Fedora er koordinert av <ulink url=\"http://fedoraproject.org/wiki/L10N\">Fedora Localization Project</ulink>."
#: en_US/I18n.xml:25(para)
-#, fuzzy
msgid "Internationalization of Fedora is maintained by the <ulink url=\"http://fedoraproject.org/wiki/I18N\">Fedora I18n Project</ulink>."
-msgstr "Send e-post til <ulink url=\"mailto:relnotes@fedoraproject.org\">relnotes(a)fedoraproject.org</ulink>"
+msgstr "Internasjonalisering av Fedora er vedlikeholdt av <ulink url=\"http://fedoraproject.org/wiki/I18N\">Fedora I18n Project</ulink>."
#: en_US/I18n.xml:31(title)
#, fuzzy
@@ -1703,11 +1701,11 @@
#: en_US/Devel.xml:89(para)
msgid "CDT (<ulink url=\"http://www.eclipse.org/cdt\">http://www.eclipse.org/cdt</ulink>, for C/C++ development;"
-msgstr ""
+msgstr "CDT (<ulink url=\"http://www.eclipse.org/cdt\">http://www.eclipse.org/cdt</ulink>, for utvikling i C/C++;"
#: en_US/Devel.xml:94(para)
msgid "GEF (<ulink url=\"http://www.eclipse.org/gef\">http://www.eclipse.org/gef</ulink>), the Graphical Editing Framework; and"
-msgstr ""
+msgstr "GEF (<ulink url=\"http://www.eclipse.org/gef\">http://www.eclipse.org/gef</ulink>), Graphical Editing Framework; og"
#: en_US/Devel.xml:99(para)
msgid "Mylyn (<ulink url=\"http://www.eclipse.org/mylyn\">http://www.eclipse.org/mylyn</ulink>), a task-focused UI for Eclipse, along with task connectors for Bugzilla and Trac."
@@ -1715,7 +1713,7 @@
#: en_US/Devel.xml:105(para)
msgid "Other Eclipse projects available in Fedora include:"
-msgstr ""
+msgstr "Andre Eclipse-prosjekter i Fedora er:"
#: en_US/Devel.xml:108(para)
msgid "Subclipse (<ulink url=\"http://subclipse.tigris.org/\">http://subclipse.tigris.org/</ulink>), for integrating Subversion version control;"
@@ -1936,7 +1934,7 @@
#: en_US/Desktop.xml:129(para)
msgid "Close all <application>Firefox</application> windows, and then relaunch <application>Firefox</application>."
-msgstr ""
+msgstr "Lukk alle <application>Firefox</application>-vinduene, og start <application>Firefox</application> p�� nytt."
#: en_US/Desktop.xml:141(title)
msgid "Mail Clients"
@@ -1968,15 +1966,15 @@
#: en_US/DatabaseServers.xml:17(para)
msgid "Fedora now provides MySQL 5.0.45. For a list of the enhancements provided by this version, refer to <ulink url=\"http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html\"/>."
-msgstr ""
+msgstr "Fedora tilbyr n�� MySQL 5.0.45. For en liste med forbedringer i denne versjonen, g�� til <ulink url=\"http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html\"/>."
#: en_US/DatabaseServers.xml:22(para)
msgid "For more information on upgrading databases from previous releases of MySQL, refer to the MySQL website at <ulink url=\"http://dev.mysql.com/doc/refman/5.0/en/upgrade.html\"/>."
-msgstr ""
+msgstr "For mer informasjon om oppgradering av databaser fra tidligere versjoner av MySQL, g�� til nettsiden til MySQL p�� <ulink url=\"http://dev.mysql.com/doc/refman/5.0/en/upgrade.html\"/>."
#: en_US/DatabaseServers.xml:29(title)
msgid "DBD Driver"
-msgstr ""
+msgstr "DBD-driver"
#: en_US/DatabaseServers.xml:30(para)
msgid "The MySQL DBD driver has been dual-licensed and the related licensing issues have been resolved (<ulink url=\"https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=222237\"/>). The resulting <package>apr-util-mysql</package> package is now included in the Fedora software repositories."
@@ -1988,31 +1986,31 @@
#: en_US/DatabaseServers.xml:42(para)
msgid "This release of Fedora includes PostgreSQL 8.2.4. For more information on this new version, refer to <ulink url=\"http://www.postgresql.org/docs/whatsnew\"/>."
-msgstr ""
+msgstr "Denne utgivelsen av Fedora inkluderer PostgreSQL 8.2.4. For mer informasjon om denne versjonen, g�� til <ulink url=\"http://www.postgresql.org/docs/whatsnew\"/>."
#: en_US/DatabaseServers.xml:49(title)
msgid "Upgrading Databases"
-msgstr ""
+msgstr "Oppgradere databaser"
#: en_US/DatabaseServers.xml:50(para)
msgid "Before upgrading an existing Fedora system with a PostgreSQL database, it could be necessary to follow the procedure described at <ulink url=\"http://www.postgresql.org/docs/8.2/interactive/install-upgrading.html\"/>. Otherwise the data may be not accessible by the new version of PostgreSQL."
-msgstr ""
+msgstr "F��r oppgradering av et eksisterende Fedora-system med en PostgreSQL-database, kan det v��re n��dvendig �� f��lge prosedyrene som er beskrevet p�� <ulink url=\"http://www.postgresql.org/docs/8.2/interactive/install-upgrading.html\"/>. Hvis ikke s�� kan det hende at dataene ikke er tilgjengelig i den nye versjonen av PostgreSQL."
#: en_US/Colophon.xml:5(title)
msgid "Colophon"
-msgstr ""
+msgstr "Kolofon"
#: en_US/Colophon.xml:7(para)
msgid "As we use the term, a <emphasis>colophon</emphasis>:"
-msgstr ""
+msgstr "Slik som vi bruker termen, en <emphasis>kolofon</emphasis>:"
#: en_US/Colophon.xml:13(para)
msgid "recognizes contributors and provides accountability, and"
-msgstr ""
+msgstr "anerkjenner bidragsytere og gir ansvarlighet, og"
#: en_US/Colophon.xml:17(para)
msgid "explains tools and production methods."
-msgstr ""
+msgstr "forklarer verkt��y og produksjonsmetoder."
#: en_US/Colophon.xml:24(title)
msgid "Contributors"
@@ -2032,43 +2030,43 @@
#: en_US/Colophon.xml:45(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/AndrewOverholt\">Andrew Overholt</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/AndrewOverholt\">Andrew Overholt</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:51(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/AnthonyGreen\">Anthony Green</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/AnthonyGreen\">Anthony Green</ulink> (gebetskribent)"
#: en_US/Colophon.xml:57(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/BrandonHolbrook\">Brandon Holbrook</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/BrandonHolbrook\">Brandon Holbrook</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:63(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/BobJensen\">Bob Jensen</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/BobJensen\">Bob Jensen</ulink> (gebetskribent)"
#: en_US/Colophon.xml:69(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/ChrisLennert\">Chris Lennert</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/ChrisLennert\">Chris Lennert</ulink> (gebetskribent)"
#: en_US/Colophon.xml:75(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/DaveMalcolm\">Dave Malcolm</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/DaveMalcolm\">Dave Malcolm</ulink> (gebetskribent)"
#: en_US/Colophon.xml:81(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/DavidEisenstein\">David Eisenstein</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/DavidEisenstein\">David Eisenstein</ulink> (gebetskribent)"
#: en_US/Colophon.xml:87(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/DavidWoodhouse\">David Woodhouse</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/DavidWoodhouse\">David Woodhouse</ulink> (gebetskribent)"
#: en_US/Colophon.xml:93(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/DeepakBhole\">Deepak Bhole</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/DeepakBhole\">Deepak Bhole</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:99(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/DiegoZacarao\">Diego Burigo Zacarao</ulink> (translator - Brazilian Portuguese)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/DiegoZacarao\">Diego Burigo Zacarao</ulink> (oversetter - brasiliansk portugisisk)"
#: en_US/Colophon.xml:105(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/DimitrisGlezos\">Dimitris Glezos</ulink> (translator - Greek, tools)"
@@ -2084,11 +2082,11 @@
#: en_US/Colophon.xml:123(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/GavinHenry\">Gavin Henry</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/GavinHenry\">Gavin Henry</ulink> (gebetskribent)"
#: en_US/Colophon.xml:129(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/HugoCisneiros\">Hugo Cisneiros</ulink> (translator - Brazilian Portuguese)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/HugoCisneiros\">Hugo Cisneiros</ulink> (oversetter - brasiliansk portugisisk)"
#: en_US/Colophon.xml:135(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/IgorMiletic\">Igor Miletic</ulink> (translator - Serbian)"
@@ -2096,20 +2094,19 @@
#: en_US/Colophon.xml:141(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/JeffJohnston\">Jeff Johnston</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/JeffJohnston\">Jeff Johnston</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:147(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/JensPetersen\">Jens Petersen</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/JensPetersen\">Jens Petersen</ulink> (gebetskribent)"
#: en_US/Colophon.xml:153(para)
-#, fuzzy
msgid "<ulink url=\"http://fedoraproject.org/wiki/JesseKeating\">Jesse Keating</ulink> (beat contributor)"
-msgstr "Send e-post til <ulink url=\"mailto:relnotes@fedoraproject.org\">relnotes(a)fedoraproject.org</ulink>"
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/JesseKeating\">Jesse Keating</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:158(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/JoeOrton\">Joe Orton</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/JoeOrton\">Joe Orton</ulink> (gebetskribent)"
#: en_US/Colophon.xml:164(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/JosePires\">Jose Nuno Coelho Pires</ulink> (translator - Portuguese)"
@@ -2117,23 +2114,23 @@
#: en_US/Colophon.xml:170(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/JoshBressers\">Josh Bressers</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/JoshBressers\">Josh Bressers</ulink> (gebetskribent)"
#: en_US/Colophon.xml:176(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/KarstenWade\">Karsten Wade</ulink> (beat writer, editor, co-publisher)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/KarstenWade\">Karsten Wade</ulink> (gebetskribent, redakt��r, med-utgiver)"
#: en_US/Colophon.xml:182(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/KyuLee\">Kyu Lee</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/KyuLee\">Kyu Lee</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:188(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/LicioFonseca\">Licio Fonseca</ulink> (translator - Brazilian Portuguese)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/LicioFonseca\">Licio Fonseca</ulink> (oversetter - brasiliansk portugisisk)"
#: en_US/Colophon.xml:194(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/LuyaTshimbalanga\">Luya Tshimbalanga</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/LuyaTshimbalanga\">Luya Tshimbalanga</ulink> (gebetskribent)"
#: en_US/Colophon.xml:200(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/MagnusLarsson\">Magnus Larsson</ulink> (translator - Swedish)"
@@ -2141,7 +2138,7 @@
#: en_US/Colophon.xml:206(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/MartinBall\">Martin Ball</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/MartinBall\">Martin Ball</ulink> (gebetskribent)"
#: en_US/Colophon.xml:212(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/MaximDziumanenko\">Maxim Dziumanenko</ulink> (translator - Ukrainian)"
@@ -2153,15 +2150,15 @@
#: en_US/Colophon.xml:225(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/OrionPoplawski\">Orion Poplawski</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/OrionPoplawski\">Orion Poplawski</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:231(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/PatrickBarnes\">Patrick Barnes</ulink> (beat writer, editor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/PatrickBarnes\">Patrick Barnes</ulink> (gebetskribent, redakt��r)"
#: en_US/Colophon.xml:237(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/PaulWFrields\">Paul W. Frields</ulink> (tools, editor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/PaulWFrields\">Paul W. Frields</ulink> (verkt��y, redakt��r)"
#: en_US/Colophon.xml:243(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/PawelSadowski\">Pawel Sadowski</ulink> (translator - Polish)"
@@ -2169,15 +2166,15 @@
#: en_US/Colophon.xml:249(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/PatrickErnzer\">Patrick Ernzer</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/PatrickErnzer\">Patrick Ernzer</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:255(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/RahulSundaram\">Rahul Sundaram</ulink> (beat writer, editor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/RahulSundaram\">Rahul Sundaram</ulink> (gebetskribent, redakt��r)"
#: en_US/Colophon.xml:261(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/SamFolkWilliams\">Sam Folk-Williams</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/SamFolkWilliams\">Sam Folk-Williams</ulink> (gebetskribent)"
#: en_US/Colophon.xml:267(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/SekineTatsuo\">Sekine Tatsuo</ulink> (translator - Japanese)"
@@ -2189,7 +2186,7 @@
#: en_US/Colophon.xml:279(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/SteveDickson\">Steve Dickson</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/SteveDickson\">Steve Dickson</ulink> (gebetskribent)"
#: en_US/Colophon.xml:285(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/TetaBilianou\">Teta Bilianou</ulink> (translator - Greek)"
@@ -2205,7 +2202,7 @@
#: en_US/Colophon.xml:303(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/ThomasGraf\">Thomas Graf</ulink> (beat writer)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/ThomasGraf\">Thomas Graf</ulink> (gebetskribent)"
#: en_US/Colophon.xml:309(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/TommyReynolds\">Tommy Reynolds</ulink> (tools)"
@@ -2213,11 +2210,11 @@
#: en_US/Colophon.xml:315(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/ValnirFerreiraJr\">Valnir Ferreira Jr.</ulink> (translator - Brazilian Portuguese)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/ValnirFerreiraJr\">Valnir Ferreira Jr.</ulink> (oversetter - brasiliansk portugisisk)"
#: en_US/Colophon.xml:321(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/WillWoods\">Will Woods</ulink> (beat contributor)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/WillWoods\">Will Woods</ulink> (gebet-bidragsyter)"
#: en_US/Colophon.xml:327(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/YoshinariTakaoka\">Yoshinari Takaoka</ulink> (translator, tools)"
@@ -2225,19 +2222,19 @@
#: en_US/Colophon.xml:333(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/YuanYijun\">Yuan Yijun</ulink> (translator - Simplified Chinese)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/YuanYijun\">Yuan Yijun</ulink> (oversetter - forenklet kinesisk)"
#: en_US/Colophon.xml:339(para)
msgid "<ulink url=\"http://fedoraproject.org/wiki/ZhangYang\">Zhang Yang</ulink> (translator - simplified Chinese)"
-msgstr ""
+msgstr "<ulink url=\"http://fedoraproject.org/wiki/ZhangYang\">Zhang Yang</ulink> (oversetter - forenklet kinesisk)"
#: en_US/Colophon.xml:345(para)
msgid "... and many more translators. Refer to the Web-updated version of these release notes as we add translators after release:"
-msgstr ""
+msgstr "... og mange andre oversettere. G�� til nettsiden for siste versjon av disse utgivelsesnotatene, siden vi legger til oversettere etter utgivelsen:"
#: en_US/Colophon.xml:355(title)
msgid "Production Methods"
-msgstr ""
+msgstr "Produksjonsmetoder"
#: en_US/Colophon.xml:356(para)
msgid "Beat writers produce the release notes directly on the Fedora Project Wiki. They collaborate with other subject matter experts during the test release phase of Fedora to explain important changes and enhancements. The editorial team ensures consistency and quality of the finished beats, and ports the Wiki material to DocBook XML in a revision control repository. At this point, the team of translators produces other language versions of the release notes, and then they become available to the general public as part of Fedora. The publication team also makes them, and subsequent errata, available via the Web."
@@ -2297,7 +2294,7 @@
#: en_US/ArchSpecific.xml:54(title)
msgid "Hardware Requirements for PPC"
-msgstr ""
+msgstr "Maskinvarekrav for PPC"
#: en_US/ArchSpecific.xml:56(title)
#: en_US/ArchSpecific.xml:290(title)
16 years, 6 months
Re: How do I de-blur a picture?
by j.halifax2＠seznam.cz
Great contribution, Willi!
Thank u so much as well. :)
jh
---------- Původní e-mail ----------
Od: William Oliver <vendor(a)billoblog.com>
Komu: users(a)lists.fedoraproject.org
Datum: 23. 7. 2019 15:30:05
Předmět: Re: How do I de-blur a picture?
"This really isn't a Fedora question but...
Blurring a pixel is simply replacing it with a weighted average of it
and the surrounding pixels. The mathematical process is called a
"convolution."
Classically, in order to deblur an image, you need to know the blurring
function (the set of weights on the surrounding pixels, the shape of
the group of pixels used in the blur, and the size of the region used
in the blur). When done directly, this blurring function is called the
"point spread function" for obvious reasons. It turns out that there's
a neat thing about this in that the process of blurring is
computationally expensive when done directly, but if you do a fourier
transform of the image, it's just a multiplication of the image with
the blur function (called the "modulation transfer function" in
frequency space).
Reversing the convolution that resulted in the blurred image is called
"deconvolution."
The down side of doing things in frequency space is that many of the
coefficients are very small, or zero, usually, and 1) you can't divide
by zero, 2) small errors in very small numbers lead to very big errors
when you divide by them. So, if you don't have your point spread
function perfectly characterized, your error blows up. There are all
sorts of ways to try to get around this, both in image space and
frequency space, but the bottom line is that if you know your point
spread function well, you can deblur well, and if you don't, you can't.
The well-known "unsharp mask" function is basically one iteration of a
multi-iteration deconvolution method in image space that assumes the
blur function is a gaussian/binomial. Thus, it doesn't look too bad if
you do it a little, but looks horrible if you do it a lot -- because
the real blurring function is likely not a gaussian. The more you do
it, the more the error becomes dominant.
You can try to do this without knowing the blurring function. This is
called "blind deconvolution." However, these methods usually force you
to make assumptions about things in the image, and then modify the
image to fit those things. The classic example here is astronomy
photography where you can assume that a distant star it just a dot, or
microscopy where they sell tiny little spheres that you then photograph
and modify the image so that they look like little spheres. That way
you can estimate the point spread function and go from there.
Deblurring was a big deal in the 1980s when they put up the Hubble
telescope and found out they had polished the mirrors incorrectly. The
US government dumped millions of dollars in (successfully) trying to
correct for the Hubble blur. It then became very popular in
specialized microscopy, such as confocal microscopy, where you are
pushing the optics to their limits.
The other big advance was for smartphones. There are two common ways
to make sure you take good photos. The first is to have excellent
lenses with great optics, and try to do as little post processing as
possible. The second is to have a cheap lens that is well
characterized mathematically and designed to have few of those bad
coefficients, so you can easily post process it to get a good image.
Thus, you can either buy a really good camera with expensive lenses and
take a good picture to start with, or you can put a cheap lousy lens in
a smartphone and process the bejeezus out of it.
There are a number of freeware programs out there for deconvolution,
and a whole industry of proprietary stuff. Unfortunately, you usually
have to start by characterizing your point spread function, and that's
always a hassle. Some places have standardized point spread functions
for well-known lenses, but they can be hard to find.
One piece of software that has a number of deconvolution plugins
(primarily for microscopy) is ImageJ or Fiji (a not-quite-fork of
ImageJ). ImageJ is maintained by the National Institutes of Health in
the US, and is free. Fiji is maintained by an academic institution,
but I can't remember which.
So, do searches on "deconvolution," "blind deconvolution",
"deblurring," and "ImageJ deconvolution", "Fiji deconvolution." That
will get you started.
In particular, see:
https://imagej.net/Deconvolution
billo
On Tue, 2019-07-23 at 01:09 -0700, ToddAndMargo via users wrote:
> Hi All,
>
> Fedora 30, x64
>
> Anyone know of a way to remove the blur from this picture?
>
> https://ibb.co/cTPNHLf
>
>
> Many thanks,
> -T
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.
org
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of
-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.
fedoraproject.org
"
4 years, 9 months
nickblack pushed to notcurses (epel7). "Merge branch 'f33' into epel7"
by notifications＠fedoraproject.org
Notification time stamped 2021-07-29 09:19:24 UTC
From 1e6d133ed4c7336e26a66652d2fbfa7cccbf8136 Mon Sep 17 00:00:00 2001
From: Nick Black <dankamongmen(a)gmail.com>
Date: Jul 29 2021 09:19:08 +0000
Subject: Merge branch 'f33' into epel7
---
diff --git a/.gitignore b/.gitignore
index 519bad7..283eaa2 100644
--- a/.gitignore
+++ b/.gitignore
@@ -115,5 +115,50 @@
/notcurses_2.1.8+dfsg.1.orig.tar.xz.asc
/notcurses_2.2.0+dfsg.1.orig.tar.xz
/notcurses_2.2.0+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.1+dfsg.1.orig.tar.xz
+/notcurses_2.2.1+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.2+dfsg.1.orig.tar.xz
+/notcurses_2.2.2+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.3+dfsg.1.orig.tar.xz
+/notcurses_2.2.3+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.4+dfsg.1.orig.tar.xz
+/notcurses_2.2.4+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.5+dfsg.1.orig.tar.xz
+/notcurses_2.2.5+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.6+dfsg.1.orig.tar.xz
+/notcurses_2.2.6+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.8+dfsg.1.orig.tar.xz
+/notcurses_2.2.8+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.9+dfsg.1.orig.tar.xz
+/notcurses_2.2.9+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.10+dfsg.1.orig.tar.xz
+/notcurses_2.2.10+dfsg.1.orig.tar.xz.asc
+/notcurses_2.2.11+dfsg.1.orig.tar.xz
+/notcurses_2.2.11+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.0+dfsg.1.orig.tar.xz
+/notcurses_2.3.0+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.1+dfsg.1.orig.tar.xz
+/notcurses_2.3.1+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.2+dfsg.1.orig.tar.xz
+/notcurses_2.3.2+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.3+dfsg.1.orig.tar.xz
+/notcurses_2.3.3+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.4+dfsg.1.orig.tar.xz
+/notcurses_2.3.4+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.5+dfsg.1.orig.tar.xz
+/notcurses_2.3.5+dfsg.1.orig.tar.xz.asc
+/0001-don-t-allow-a-format-string-attack-via-endasu-sequen.patch
+/notcurses-2.3.5-1.fc35.src.rpm
+/notcurses_2.3.6+dfsg.1.orig.tar.xz
+/notcurses_2.3.6+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.7+dfsg.1.orig.tar.xz
+/notcurses_2.3.7+dfsg.1.orig.tar.xz.asc
/notcurses_2.3.8+dfsg.1.orig.tar.xz
/notcurses_2.3.8+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.9+dfsg.1.orig.tar.xz
+/notcurses_2.3.9+dfsg.1.orig.tar.xz.asc
+/notcurses-2.3.11-1.fc35.src.rpm
+/notcurses_2.3.11+dfsg.1.orig.tar.xz
+/notcurses_2.3.11+dfsg.1.orig.tar.xz.asc
+/notcurses_2.3.12+dfsg.1.orig.tar.xz
+/notcurses_2.3.12+dfsg.1.orig.tar.xz.asc
diff --git a/changelog b/changelog
new file mode 100644
index 0000000..4a000b7
--- /dev/null
+++ b/changelog
@@ -0,0 +1,189 @@
+* Thu Jul 22 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.11-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
+
+* Wed Jul 21 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.11-1
+- New upstream release, add zlib-devel dep
+
+* Mon Jul 12 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.9-1
+- New upstream release, bugfix-oriented
+
+* Tue Jun 29 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.7-1
+- New upstream release
+
+* Wed Jun 23 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.6-1
+- New upstream release
+
+* Sat Jun 12 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.4-1
+- New upstream release, new notcurses-info binary
+
+* Mon Jun 07 2021 Python Maint <python-maint(a)redhat.com> - 2.3.2-2
+- Rebuilt for Python 3.10
+
+* Sun Jun 06 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.2-1
+- New upstream release
+
+* Fri Jun 04 2021 Python Maint <python-maint(a)redhat.com> - 2.3.1-3
+- Rebuilt for Python 3.10
+
+* Wed May 19 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.1-2
+- Apply patch from @scauligi for cffi on arch
+
+* Tue May 18 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.1-1
+- New upstream
+
+* Sun May 09 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.0-1
+- New upstream
+
+* Wed May 05 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.10-1
+- New upstream, brown-bagger fixes assert failures
+
+* Mon May 03 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.9-1
+- New upstream
+
+* Sun Apr 18 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.8-1
+- New upstream
+
+* Mon Apr 12 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.6-3
+- New upstream, add explicit -DUSE_QRCODEGEN=ON
+
+* Tue Mar 09 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.3-2
+- New upstream, add CMAKE_POSITION_INDEPENDENT_CODE=ON
+
+* Thu Feb 18 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.2-1
+- New upstream
+
+* Tue Feb 09 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.1-1
+- New upstream, fixes Direct Mode UTF8 detection brown-bagger
+
+* Mon Feb 08 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.0-1
+- New upstream
+
+* Wed Feb 03 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.8-1
+- New upstream
+
+* Tue Jan 26 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.1.7-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
+
+* Thu Jan 21 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.7-1
+- New upstream, split notcurses and notcurses-core
+
+* Fri Jan 15 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.5-1
+- New upstream version, add readline-dev dep
+
+* Sun Jan 03 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.4-1
+- New upstream version
+
+* Thu Dec 31 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.3-1
+- New upstream version, fixes crash in notcurses-demo
+
+* Sat Dec 26 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.2-1
+- New upstream version, sexblitter by default on some terms
+
+* Wed Dec 16 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.1-1
+- New upstream version, progress bar widget
+
+* Sun Dec 13 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.0-1
+- New upstream version, fixes resize cascade
+
+* Wed Dec 09 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.11-1
+- New upstream version, fixes many big-endian issues
+
+* Sun Dec 06 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.10-1
+- New upstream version
+
+* Tue Dec 01 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.9-1
+- New upstream version, several important bugfixes, add "ncls"
+
+* Fri Nov 27 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.8-1
+- New upstream version, relaxes pypandoc depend version
+
+* Sat Nov 21 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.7-1
+- New upstream version
+
+* Tue Nov 10 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.4-1
+- New upstream version, fixes unit tests for non-UTF8
+
+* Mon Nov 9 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.3-1
+- New upstream version including sexblitter, keller demo
+
+* Sun Oct 25 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.2-1
+- New upstream version, ncvisual_decode_loop()
+
+* Mon Oct 19 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.1-1
+- New upstream version, quadblitter perf+transparency improvements
+
+* Tue Oct 13 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.0-1
+- New upstream version, stable API!
+
+* Sat Oct 10 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.6-1
+- New upstream version
+
+* Tue Sep 29 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.5-1
+- New upstream version, drop notcurses-ncreel binary
+
+* Sun Sep 20 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.4-1
+- New upstream version
+
+* Sat Sep 19 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.3-1
+- New upstream version
+
+* Fri Sep 11 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.2-1
+- New upstream version
+
+* Thu Aug 27 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.19-1
+- New upstream version, reenable unit tests for s390
+
+* Wed Aug 12 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.12-1
+- New upstream version, many small bugfixes
+
+* Mon Aug 03 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.11-1
+- New upstream version with new 'zoo' demo
+
+* Sun Aug 02 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.10-1
+- New upstream version with Linux console font reprogramming
+
+* Sun Jul 12 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.1-1
+- New upstream version, purge vt100 patch (applied upstream), install TERMS.md
+
+* Sat Jul 04 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.0-1
+- New upstream version, backport patch to work on vt100 autobuilder, enable all tests
+
+* Sun Jun 28 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.3-1
+- New upstream version
+
+* Fri Jun 19 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.2-1
+- New upstream version, new binary 'ncneofetch'
+
+* Sun Jun 14 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.1-1
+- New upstream version
+
+* Mon Jun 08 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.0-1
+- New upstream version
+
+* Sat Jun 06 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.5-1
+- New upstream version, disable Ncpp,Exceptions unit tests for now
+
+* Tue Jun 02 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.4.1-1
+- New upstream version
+
+* Tue May 26 2020 Miro Hrončok <mhroncok(a)redhat.com> - 1.4.3-3
+- Rebuilt for Python 3.9
+
+* Sun May 24 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.3-2
+- Dep on doctest-devel, run tests, use _target_platform in place of "build"
+
+* Fri May 22 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.3-1
+- New upstream version
+
+* Wed May 20 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.2.4-1
+- New upstream version, add python3-setuptools dep
+
+* Sun May 17 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.2.3-1
+- New upstream version
+
+* Sat Apr 25 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.1-1
+- New upstream version, incorporate review feedback
+- Build against OpenImageIO, install notcurses-view and data
+
+* Tue Apr 07 2020 Nick Black <dankamongmen(a)gmail.com> - 1.3.3-1
+- Initial Fedora packaging
diff --git a/notcurses.spec b/notcurses.spec
index 027a3aa..c86aa27 100644
--- a/notcurses.spec
+++ b/notcurses.spec
@@ -1,5 +1,5 @@
Name: notcurses
-Version: 2.3.8
+Version: 2.3.12
Release: 1%{?dist}
Summary: Character graphics and TUI library
License: ASL 2.0
@@ -17,6 +17,7 @@ BuildRequires: gcc-c++
BuildRequires: libunistring-devel
#BuildRequires: readline-devel
#BuildRequires: OpenImageIO-devel
+BuildRequires: zlib-devel
BuildRequires: pandoc
#BuildRequires: python36-cffi
#BuildRequires: python3-devel
@@ -89,7 +90,7 @@ cd cffi
%ldconfig_scriptlets
%files
-%doc doc/CONTRIBUTING.md INSTALL.md doc/OTHERS.md README.md USAGE.md NEWS.md TERMINALS.md
+%doc CONTRIBUTING.md doc/CURSES.md doc/HACKING.md doc/HISTORY.md INSTALL.md doc/OTHERS.md README.md USAGE.md NEWS.md TERMINALS.md
%license COPYRIGHT
%{_libdir}/libnotcurses-core.so.%{version}
%{_libdir}/libnotcurses-core.so.2
@@ -124,6 +125,7 @@ cd cffi
%{_bindir}/ncplayer
%{_bindir}/nctetris
%{_bindir}/notcurses-demo
+%{_bindir}/notcurses-info
%{_bindir}/notcurses-input
%{_bindir}/notcurses-tester
%{_mandir}/man1/ncls.1*
@@ -131,140 +133,71 @@ cd cffi
%{_mandir}/man1/ncplayer.1*
%{_mandir}/man1/nctetris.1*
%{_mandir}/man1/notcurses-demo.1*
+%{_mandir}/man1/notcurses-info.1*
%{_mandir}/man1/notcurses-input.1*
%{_mandir}/man1/notcurses-tester.1*
%{_datadir}/%{name}
%changelog
-* Sat Jul 10 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.8-1
-- New upstream
-
-* Wed Feb 03 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.8-1
-- New upstream
-
-* Tue Jan 26 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.1.7-2
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
-
-* Thu Jan 21 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.7-1
-- New upstream, split notcurses and notcurses-core
-
-* Fri Jan 15 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.5-1
-- New upstream version, add readline-dev dep
-
-* Sun Jan 03 2021 Nick Black <dankamongmen(a)gmail.com> - 2.1.4-1
-- New upstream version
-
-* Thu Dec 31 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.3-1
-- New upstream version, fixes crash in notcurses-demo
-
-* Sat Dec 26 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.2-1
-- New upstream version, sexblitter by default on some terms
-
-* Wed Dec 16 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.1-1
-- New upstream version, progress bar widget
-
-* Sun Dec 13 2020 Nick Black <dankamongmen(a)gmail.com> - 2.1.0-1
-- New upstream version, fixes resize cascade
-
-* Wed Dec 09 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.11-1
-- New upstream version, fixes many big-endian issues
-
-* Sun Dec 06 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.10-1
-- New upstream version
-
-* Tue Dec 01 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.9-1
-- New upstream version, several important bugfixes, add "ncls"
-
-* Fri Nov 27 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.8-1
-- New upstream version, relaxes pypandoc depend version
+* Thu Jul 29 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.12-2
+- New upstream, many bugfixen
-* Sat Nov 21 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.7-1
-- New upstream version
+* Thu Jul 22 2021 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.3.11-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
-* Tue Nov 10 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.4-1
-- New upstream version, fixes unit tests for non-UTF8
+* Wed Jul 21 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.11-1
+- New upstream release, add zlib-devel dep
-* Mon Nov 9 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.3-1
-- New upstream version including sexblitter, keller demo
+* Mon Jul 12 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.9-1
+- New upstream release, bugfix-oriented
-* Sun Oct 25 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.2-1
-- New upstream version, ncvisual_decode_loop()
+* Tue Jun 29 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.7-1
+- New upstream release
-* Mon Oct 19 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.1-1
-- New upstream version, quadblitter perf+transparency improvements
+* Wed Jun 23 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.6-1
+- New upstream release
-* Tue Oct 13 2020 Nick Black <dankamongmen(a)gmail.com> - 2.0.0-1
-- New upstream version, stable API!
+* Sat Jun 12 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.4-1
+- New upstream release, new notcurses-info binary
-* Sat Oct 10 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.6-1
-- New upstream version
+* Mon Jun 07 2021 Python Maint <python-maint(a)redhat.com> - 2.3.2-2
+- Rebuilt for Python 3.10
-* Tue Sep 29 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.5-1
-- New upstream version, drop notcurses-ncreel binary
+* Sun Jun 06 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.2-1
+- New upstream release
-* Sun Sep 20 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.4-1
-- New upstream version
+* Fri Jun 04 2021 Python Maint <python-maint(a)redhat.com> - 2.3.1-3
+- Rebuilt for Python 3.10
-* Sat Sep 19 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.3-1
-- New upstream version
+* Wed May 19 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.1-2
+- Apply patch from @scauligi for cffi on arch
-* Fri Sep 11 2020 Nick Black <dankamongmen(a)gmail.com> - 1.7.2-1
-- New upstream version
-
-* Thu Aug 27 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.19-1
-- New upstream version, reenable unit tests for s390
-
-* Wed Aug 12 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.12-1
-- New upstream version, many small bugfixes
-
-* Mon Aug 03 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.11-1
-- New upstream version with new 'zoo' demo
-
-* Sun Aug 02 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.10-1
-- New upstream version with Linux console font reprogramming
-
-* Sun Jul 12 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.1-1
-- New upstream version, purge vt100 patch (applied upstream), install TERMS.md
-
-* Sat Jul 04 2020 Nick Black <dankamongmen(a)gmail.com> - 1.6.0-1
-- New upstream version, backport patch to work on vt100 autobuilder, enable all tests
-
-* Sun Jun 28 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.3-1
-- New upstream version
-
-* Fri Jun 19 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.2-1
-- New upstream version, new binary 'ncneofetch'
-
-* Sun Jun 14 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.1-1
-- New upstream version
-
-* Mon Jun 08 2020 Nick Black <dankamongmen(a)gmail.com> - 1.5.0-1
-- New upstream version
+* Tue May 18 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.1-1
+- New upstream
-* Sat Jun 06 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.5-1
-- New upstream version, disable Ncpp,Exceptions unit tests for now
+* Sun May 09 2021 Nick Black <dankamongmen(a)gmail.com> - 2.3.0-1
+- New upstream
-* Tue Jun 02 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.4.1-1
-- New upstream version
+* Wed May 05 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.10-1
+- New upstream, brown-bagger fixes assert failures
-* Tue May 26 2020 Miro Hrončok <mhroncok(a)redhat.com> - 1.4.3-3
-- Rebuilt for Python 3.9
+* Mon May 03 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.9-1
+- New upstream
-* Sun May 24 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.3-2
-- Dep on doctest-devel, run tests, use _target_platform in place of "build"
+* Sun Apr 18 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.8-1
+- New upstream
-* Fri May 22 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.3-1
-- New upstream version
+* Mon Apr 12 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.6-3
+- New upstream, add explicit -DUSE_QRCODEGEN=ON
-* Wed May 20 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.2.4-1
-- New upstream version, add python3-setuptools dep
+* Tue Mar 09 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.3-2
+- New upstream, add CMAKE_POSITION_INDEPENDENT_CODE=ON
-* Sun May 17 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.2.3-1
-- New upstream version
+* Thu Feb 18 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.2-1
+- New upstream
-* Sat Apr 25 2020 Nick Black <dankamongmen(a)gmail.com> - 1.4.1-1
-- New upstream version, incorporate review feedback
-- Build against OpenImageIO, install notcurses-view and data
+* Tue Feb 09 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.1-1
+- New upstream, fixes Direct Mode UTF8 detection brown-bagger
-* Tue Apr 07 2020 Nick Black <dankamongmen(a)gmail.com> - 1.3.3-1
+* Mon Feb 08 2021 Nick Black <dankamongmen(a)gmail.com> - 2.2.0-1
- Initial Fedora packaging
diff --git a/sources b/sources
index 9dc6c21..92ed4da 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (notcurses_2.3.8+dfsg.1.orig.tar.xz) = 88c44b6e2d709ab55af6567f82c0c632ecd9f1ec25ae12f50ecb2fab42829d0d5132648c7dd647a92af945ac28af86558e31d46b29de69326d6ffbe3baf1b296
-SHA512 (notcurses_2.3.8+dfsg.1.orig.tar.xz.asc) = ca34b1a93e15e3950cfce997be07fac705227a9a23a0ba47858f2e9733555dd0f391c65850195043975da759450a740e035b06c4793022a8ce7a2e64f9e32430
+SHA512 (notcurses_2.3.12+dfsg.1.orig.tar.xz) = 94c27ea051e2b8755836d8770280ada8ebba881f3ef1b67883b0afc20335b6e7ae5eef0e6174d2989b5e1cfdbb7795a486c24e14320c960ae6b87303e3ef3c08
+SHA512 (notcurses_2.3.12+dfsg.1.orig.tar.xz.asc) = 9d40f11456da6bc62686ddffd50291f71717fb8cb0b94ebae8fd33967a30f544dea3e3c319b836e6c3229930dfd6275c4386ee053d3a2db09cbb1a4c7d611145
https://src.fedoraproject.org/rpms/notcurses/c/1e6d133ed4c7336e26a66652d2...
2 years, 9 months
Re: [RFC PATCH 0/3] Make TRex profiles extensible
by Ondrej Lichtner
On Mon, Jun 15, 2020 at 06:22:53PM +0200, Adrian Moreno wrote:
> Currently the TRex Test has a hardcoded set of streams.
>
> In order to make it more generic and extendable, this RFC first refactors
> the client and server code into a library that does not depend on other
> LNST code.
I'm OK with refactoring the LNST TRex test module code into a more
generic wrapper layer used by both the test module as well as the tperf
tool.
I think we need to be a little careful about how to approach that so
that this doesn't become "too big" at that point it probably makes more
sense to completely split that into a separate project that wraps TRex
(because TRex is a pain) and also provides a tperf cli for ease of use
and then implementing an LNST Test module that further builds on top of
this wrapper library. I think this has a lot of issues - such as
supporting another project, or the fact that this really just means that
TRex itself should be made better.
Also, at this point the lnst.Tests.TRex module doesn't have a very big
dependency on LNST - it uses a couple of parameters for type checking
and defines a module interface API, which is just that there's a "run"
method, but you still kept that in the standalone library. I guess this
is your main point for possible future extensions?
> That way, a small cli appliation can be implemented to inject
> traffic using the same code as LNST would. This is useful for early prototyping.
>
> An example of such as tool is introduced: test_tools/tperf. It basically runs the
> client and server as LNST would and report the aggregated throughput.
I also like the idea of this small "tperf" tool to help with prototyping,
that definitelly sounds interesting since TRex can be a lot of pain...
probably not worth investigating a generic solution at this point as
everything else is much simpler IMO.
>
> Finally, the stream can be modularized into TRex compatible modules so that:
> - New stream generators can be easily implemented
> - TRex tools (e.g: stl-sym) can be used for stream generator development
This took me a bit to understand... I was confused by the module
implementation with a "register" function... I now see that it's another
one of TRex weirdnes, I would personally prefer a class based approach
but I guess this is fine since it follows some "standard"
>
> The current stream generation is modularized as an example: udp_simple
So does this patchset require any other changes to the recipes that
currently use TRex? or is it drop in? Haven't tested this since I don't
have a pre-setup dpdk environment...
>
> I'm only a sporadic contributor to LNST so sending this RFC to get some feedback.
I think the only thing I would complain about is the placement of the
"lnst.TRex" module... I'm not sure I want it at this top level, I think
it also contributed to my slower understanding of the RFC. Not exactly
sure where to put it though. I'll keep thinking about this
-Ondrej
>
> Adrian Moreno (3):
> lnst.Tests.TRex Refactor TRex client and server
> test_tools: Add tperf
> lnst.TRex Use stl compatible modules to generate streams
>
> lnst/TRex/TRex.py | 205 ++++++++++++++++++++++++++++++++++++++++
> lnst/TRex/__init__.py | 0
> lnst/TRex/udp_simple.py | 38 ++++++++
> lnst/Tests/TRex.py | 137 ++++-----------------------
> test_tools/tperf/tperf | 192 +++++++++++++++++++++++++++++++++++++
> 5 files changed, 452 insertions(+), 120 deletions(-)
> create mode 100644 lnst/TRex/TRex.py
> create mode 100644 lnst/TRex/__init__.py
> create mode 100644 lnst/TRex/udp_simple.py
> create mode 100755 test_tools/tperf/tperf
>
> -- ,
> 2.26.2
>
> _______________________________________________
> LNST-developers mailing list -- lnst-developers(a)lists.fedorahosted.org
> To unsubscribe send an email to lnst-developers-leave(a)lists.fedorahosted.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedorahosted.org/archives/list/lnst-developers@lists.fedora...
3 years, 10 months
Re: Computer
by Alejandro López
Greetings to Matthew and all the Fedora staff,
(I'm sending this email to the mailing list because I haven't received a
response from direct email addresses for months.I hope this is not a
problem.)
I'm sorry that this project stopped, I don't know the reason, but I must
have done something wrong. So I wanted to ping you and check if
everything is going well over there. I really hope so :)
I have just checked the video of Matthew Miller playing around with the
Framework laptop. Nice video! It's encouraging to see distributions
joining those of us who make hardware.
Does that mean that you guys are going to do a collab together?
This is very good news for the Linux ecosystem, no matter if we really
want to do so too,
I take my hat off (or fedora) to them, Framework, because their
marketing campaign has been nothing but amazing success. They managed to
have it marketed as a Lego-like easy to repair device. But as hardware
experts, we can easily tell that this device is not easier to repair
than any of our products, really. We still supply spare parts for 7 year
old models from our catalog, like the Slimbook Classic or first gen
Katana because we are concerned about the longevity and sustainability
as well (so much that we are Greenpeace’s Spain hardware provider!).
Still, it fills us with joy to see that after a few years around
Windows, the Framework has decided to show interest in Linux. The more
we are in the game, the better for the Linux ecosystem.
Either way, that's a lot of rambling. We are still really interested in
a collab with you with a Fedora Slimbook or anything else, swapping
laptops or helping on source code. As long as it contributes to the
GNU/Linux ecosystem, anything is fine!
Best regards,
*Alejandro López*
/CEO/
<http://grupoodin.es/google-partner-valencia-certificados-adwords?utm_sour...>
Teléfono: 902 931 064
Ronda de la Química 28 - 71
Edificio ABM L'Andana
Parque Tecnológico de Valencia
46980 Paterna, España
alejandrolopez(a)slimbook.es
www.slimbook.es
<http://slimbook.es/?utm_source=mailfirma&utm_medium=free&utm_campaign=enl...>
Redes Sociales:
Twitter <https://twitter.com/SlimbookEs>
Instagram <https://www.instagram.com/slimbookes/?hl=es>
Linkedin <https://www.linkedin.com/company/80486053/admin/>
TikTok <https://www.tiktok.com/@slimbook>
Facebook <https://www.facebook.com/slimbook.es>
Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su
destinatario, pudiendo contener información confidencial sometida a
secreto profesional. No está permitida su reproducción o distribución
sin nuestra autorización expresa. Si usted no es el destinatario final
por favor elimínelo e infórmenos por esta vía. Derechos: Tiene derecho a
acceder, rectificar y suprimir los datos, así como otros derechos,
indicados en la información adicional, que puede ejercer en
info(a)grupoodin.es. Responsable: Grupo Odín Soluciones Informáticas, S.L;
Finalidad: prestarle los servicios que nos ha solicitado, atender sus
solicitudes de información y enviarle comunicaciones comerciales.
Información adicional: Puede consultar información adicional y detallada
sobre Protección de Datos en www.grupoodin.es/politica-de-privacidad o
en info(a)grupoodin.es
On 17/6/22 9:55, Carlos Soriano Sanchez wrote:
> I was just talking with Alejandro about this last week, Alejandro asked me to share my opinion on this initiative here.
>
> I believe this is a great opportunity to differentiate Fedora from other vendors and form a partnership, and for Slimbook to have an opportunity to be one of the distinct choices for Fedora users/contributors. I see the project going towards something similar to the HP dev one, where a specific laptop could be Fedora exclusive an tailored for a excellent Fedora experience, by choosing the components (if possible) that have good support upstream both in the kernel and user space with that Fedora version.
>
> Just my 2 cents, looking forward to see where this initiative goes!
>
> Carlos
> _______________________________________________
> desktop mailing list -- desktop(a)lists.fedoraproject.org
> To unsubscribe send an email to desktop-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject...
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
1 year, 7 months