similar to: CentOS Bug Tracker - Merge with Upstream?

Displaying 20 results from an estimated 100000 matches similar to: "CentOS Bug Tracker - Merge with Upstream?"

2016 Mar 01
1
[Bug 1053] New: connection tracker integration issue
https://bugzilla.netfilter.org/show_bug.cgi?id=1053 Bug ID: 1053 Summary: connection tracker integration issue Product: conntrack-tools Version: unspecified Hardware: i386 OS: All Status: NEW Severity: critical Priority: P5 Component: conntrack-daemon Assignee:
2013 Oct 02
1
Re: Bringing up a guest with network disabled
2013/10/2 Jorge Fábregas <jorge.fabregas@gmail.com> > On 10/01/2013 09:29 AM, James Gibbon wrote: > > Would be grateful if someone could suggest a way to disable the > networking in the > > cloned VM within the XML, if that's possible. > > I have no idea if it's possible to "disable" the NIC on the VM > definition but you could boot into
2018 Oct 20
1
Upstream and downstream (was Re: What are the differences between systemd and non-systemd Linux distros?)
On Fri Oct 19 00:52:12 UTC 2018 Japheth Cleaver wrote: > This brings to mind a video I was pointed to not long ago of Brendan > Conoboy's talk at a Dojo recently: > > https://www.youtube.com/watch?v=HQsUdLPJW20 Hey, that's me! Hi. By the way, Jim Perrin did an updated version of this talk *today* at CERN in my absence (thanks Jim!). Hopefully the video will be posted
2013 Jan 01
0
[PATCH] Added some news (including FLAC development moving to Xiph.org), replaced cvs-links by git-links and changing most links to the bug tracker with the new sourceforge link-style (for example replaced http://sourceforge.net/tracker/.... with
--- developers.html | 16 ++++++++-------- documentation.html | 4 ++-- documentation_bugs.html | 2 +- documentation_example_code.html | 2 +- documentation_tools.html | 2 +- download.html | 2 +- faq.html | 2 +- feeds/feed.rss | 31 +++++++++++++++++++++++++++++--
2013 Aug 13
2
Closing sf.net issue tracker
As part of the ongoing move of FLAC's project hosting from sourceforge.net to xiph.org, we're planning to remove the issue tracker there. Erik doesn't check it, so issues filed there are just rotting, and that's a poor experience. We don't have a decent alternative at xiph.org at the moment. We've variously discussed setting up a bugzilla instance or using github. In the
2006 Apr 05
0
The Asterisk bug tracker :: please think twice before opening a report!
Friends, At this point, we're close to 300 issues open in the bug tracker at http://bugs.digium.com Some of us spend many hours each week, if not each day, to work with the bug tracker. It's a tool for us, a very important tool to handle new features and find bugs in Asterisk, tracking them down. It is important that you consider a few things while using this tool: - If a bug marshal
2016 Oct 31
1
API/ABI changes tracker for libguestfs
Hello, The API/ABI interface of the libguestfs library is now checked for backward compatibility in the Upstream Tracker project: https://abi-laboratory.pro/tracker/timeline/libguestfs/ Hope the report will be helpful for users and maintainers of the library. Thank you.
2005 Jul 29
0
Feature requests :: For now, not in the bug tracker - please!
Dear Asterisk community, We are now working hard to complete Asterisk 1.2, testing and finalizing the existing patches and work that is going on in the developer team. Now is too late to file feature requests for 1.2 in the bug tracker. Unless you have a solid, working and tested patch, we will not consider the feature request on behalf of the developer team. A bug marshal will propably close
2013 Aug 19
0
Closing sf.net issue tracker
Ralph Giles wrote: > As part of the ongoing move of FLAC's project hosting from > sourceforge.net to xiph.org, we're planning to remove the issue tracker > there. Erik doesn't check it, so issues filed there are just rotting, > and that's a poor experience. > > We don't have a decent alternative at xiph.org at the moment. We've > variously discussed
2005 Feb 18
0
*** Important *** About the bug tracker
During the last week, we have had several support issues being reported as bugs on the bug tracker. Since we are going into a final development stage on version 1.1dev (CVS HEAD) in order to complete the 1.2 release we are under pressure to fix bugs and handle a lot of reports in a short time frame. Neither the bug tracker or the asterisk-dev mailing list is second-line support, they're
2005 Oct 03
1
*** Community alert :: Do you have open bugs in the bug tracker?
Asterisk buddies! If you have open issues in the bug tracker, please help us with providing fast responses. All developers are working real hard to close bugs pending the new release, so we kindly ask you for fast responses on our questions in the bug tracker. The quicker the better and we'll get 1.2 out of the door sooner. If you have new ideas, feature requests, thoughts - please keep the
2011 Jan 12
5
upstream merge status for 2.6.38?
Hi, I see a round of bug fixes and well as xenbus were pulled upstream. Is anything else going into .38? -- 2. That which causes joy or happiness. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2013 Oct 01
4
Re: Bringing up a guest with network disabled
On Tue, 01 Oct 2013 06:10:46 -0600 Eric Blake <eblake@redhat.com> wrote: > On 10/01/2013 06:04 AM, James Gibbon wrote: > > > > > > Hello all, > > > > I have a KVM guest VM which is a clone of a production machine > > running on a different physical server, incarnated from an > > image backup. > > Careful. You need to scrub more than
2006 Jul 08
0
Re: dell-lnx-pe] Re: RHEL4 vs CentOS-4
[newly cross-posted into the centos mailing list] On Thu, 6 Jul 2006, Stephen John Smoogen wrote: >> I understand that the following products [RHEL v the >> CentOS rebuilds] differ in price based on the extend of >> support. Apart from that, is there any other difference >> (i.e. performance, kernel stability etc)? CentOS is an outgrowth of early efforts of Lance
2006 Jul 19
0
Please Use The Bug Tracker
Hi Everyone, Just a friendly reminder that if you hit something you think is a bug, please use the bug tracker for it. http://rubyforge.org/tracker/index.php?group_id=1306&atid=5145 I have a hard time wading through the Forums, mailing list, and my personal e-mail box pulling out the bugs I need to fix. I just finished doing it for this last round and there was about 7 bugs and 5 feature
2015 Apr 01
2
os-release file doesn't match upstream?
On a fully patched C7 machine... % cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core) % cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7"
2013 Jun 04
1
centos 6' repositories against redhat 6 upstream
Hi ?Wonder how's the relationship between the centos 6's main OS/ repository and redhat 6's repositories. Let's say, Redhat 6 seperate RPMs into a series of repos like: ? ?redhat-6-server ?##(base redhat 6 OS/) ? ?redhat-6-server-optional ? ?redhat-6-server-supplementary ? ?redhat-6-server-rhev-agent ? ?rhel-6-server-cf-tools ? ?... Does centos 6 merge all the redhat 6 repos
2003 Jul 26
0
Bug Tracker Official Launch
ANNOUNCEMENT: Bug Tracker/Feature Request System http://bugs.digium.com/ Digium has introduced a bug tracking and feature request system for Asterisk developers and users. Due to the increased traffic on the mailing list, and an inadequate number of hours in the day to parse it, it has been decided that a more meaningful method of tracking bugs, features, and patches had to be implemented. The
2018 Oct 19
5
Upstream and downstream (was Re: What are the differences between systemd and non-systemd Linux distros?)
On 10/18/2018 4:41 PM, Warren Young wrote: > On Oct 18, 2018, at 9:41 AM, mark <m.roth at 5-cent.us> wrote: >> people are tired of screaming and yelling about >> systemd, because we've had years now of the response being "tough, it's >> the Wave of the Future" > We covered that back when RHEL 7 was still in beta: the time is far too late to change
2020 Apr 16
0
FYI: upstream bug reporting now using https://gitlab.com/libvirt
In keeping with our general aim to consolidate libvirt project infrastructure services on GitLab, we now wish to have issues for upstream libvirt projects reported on the appropriate https://gitlab.com/libvirt/ repository issue tracker. For further details see: https://libvirt.org/bugs.html Bugs against OS distro provided binary packages should continue to be filed against the OS distros'