Sponsored Content
The Lounge What is on Your Mind? Bug Reporting and Feature Request Tracking on GitHub Post 303033647 by Neo on Friday 5th of April 2019 07:23:19 AM
Old 04-05-2019
Dear All,

I created a "new public repo" on GitHub (without the code for now but will post the code there as needed if anyone wants to fix a bug)

You can report any forum bugs and report issues in the GitHub "Issues Tab" for this repo here:

Code:
https://github.com/unixneo/unix.com.bugtracker

To report bugs, create issues, update the code wiki, etc, you will need a GitHub account.

FYI, all our code base on this site is managed in private repos on GitHub and has been that way for a few months now.

Cheers and Thanks.

Image
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

GitHub documentation :: GitHub for dummies

Hi I wish to "develop" for brew. It is hosted on GitHub. What book (or online documentation) do you recommend me for GitHub and/or Git? Prefer small physical book. (1 Reply)
Discussion started by: slashdotweenie
1 Replies

2. Shell Programming and Scripting

Newbie question: modulo operator with negative operand, bug or feature?

Hi, I'm new to the Ash shell so my apologies if this is well known. In normal maths and other shells and languages I've used, the modulo operator always returns a positive remainder. For example see this discussion (first post so I can't hyperlink it): ... (11 Replies)
Discussion started by: FleetFoot
11 Replies

3. Shell Programming and Scripting

Get data from GitHub using Curl

Dear friends, I am working on a bash script to get data from the github by hitting the API using curl and this is quite straight forward. However the authentication mechanism we have in our github servers makes this intricate. Here is the situation : * The github uses SSO / SAML / opensso... (0 Replies)
Discussion started by: Kochappa
0 Replies
repodiff(1)															       repodiff(1)

NAME
repodiff - list differences between two or more Yum repositories SYNOPSIS
repodiff --old=old_repo_baseurl --new=new_repo_baseurl DESCRIPTION
repodiff is a program which will list differences between two sets of repositories. Note that by default only source packages are com- pared. GENERAL OPTIONS
--old, -o Add a repo. as an old repo. Note that if you prefix the url with "mirror:" then the following url is treated as a mirror and not a baseurl. --new, -n Add a repo. as an new repo. Note that if you prefix the url with "mirror:" then the following url is treated as a mirror and not a baseurl. --archlist, -a Add architectures to change the default from just comparing source packages. Note that if you want the same as a native "x86_64" architecture machine you just need to pass "x86_64" (this is different from earlier versions where you needed to specify "x86_64,athlon,i686,i586,i486,i386,noarch" and you still got "src"). --size, -s Output additional data about the size of the changes. --compare-arch Normally packages are just compared based on their name, this flag makes the comparison also use the arch. So foo.i386 and foo.x86_64 are different. --simple Output a simple one line message for modified packages. --downgrade Split the data for modified packages between upgraded and downgraded packages. EXAMPLES
Compare source pkgs in two local repos: repodiff --old=/tmp/repo-old --new=/tmp/repo-new Compare x86_64 compat. binary pkgs in two remote repos, and two local one: repodiff -a x86_64 --old=http://example.com/repo1-old --old=/tmp/repo-old --new=http://example.com/repo1-new --new=/tmp/repo-new Compare x86_64 compat. binary pkgs, but also compare arch: repodiff -a x86_64 --compare-arch --old=http://example.com/repo1-old --old=/tmp/repo-old --new=http://example.com/repo1-new --new=/tmp/repo-new Compare two releases of Fedora (15 => 16): repodiff --old='mirror:https://mirrors.fedoraproject.org/metalink?repo=fedora-source-15&arch=i386' --new='mirror:https://mir- rors.fedoraproject.org/metalink?repo=fedora-source-16&arch=i386' --size --simple --downgrade SEE ALSO
yum.conf (5) http://yum.baseurl.org/ AUTHORS
See the Authors file included with this program. BUGS
There are of course no bugs, but should you find any, you should first consult the FAQ section on http://yum.baseurl.org/wiki/Faq and if unsuccessful in finding a resolution contact the mailing list: yum-devel@lists.baseurl.org. To file a bug use http://bugzilla.redhat.com for Fedora/RHEL/Centos related bugs and http://yum.baseurl.org/report for all other bugs. James Antill 21 October 2008 repodiff(1)
All times are GMT -4. The time now is 05:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy