.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1193590
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1390780
[3]
https://github.com/fedora-testing/bash/commit/87ac935a6643a9afee44a9575771418d7be15fcb
[4] https://bugzilla.redhat.com/show_bug.cgi?id=1193590#c20
--
--
Siteshwar Vas
_entries'{history_multiline_entries}
'int rl_persistent_signal_handlers'{rl_persistent_signal_handlers}
1 Changed variable:
[C]'int rl_readline_state' was changed to 'unsigned long int
rl_readline_state' at readline.h:500:1:
size of symbol (in bytes) changed from 4 to 8
type of variable changed:
type name changed from 'int' to 'unsigned long int'
type size changed from 32 to 64 bits
I would be happy to help if any package maintainers need my help with updating
to readline-7.0.
[1]
https://src.fedoraproject.org/cgit/rpms/gdb.git/commit/?id=194c0860de7383cb82bbc6d28c64ba07bb5bea72
--
--
Siteshwar Vashisht
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Readline-8.0 was released earlier this month[1]. I am going to rebase it in
rawhide in couple of weeks.
[1] http://lists.gnu.org/archive/html/bug-bash/2019-01/msg00064.html
--
--
Siteshwar Vashisht
___
devel mailing list -- devel
- Original Message -
> From: "Jason L Tibbitts III"
> To: "Siteshwar Vashisht"
> Cc: "Development discussions related to Fedora"
>
> Sent: Thursday, January 24, 2019 6:54:59 PM
> Subject: Re: [HEADS UP] Rebasing to Readline-8.0 in ra
iling_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
--
--
Siteshwar Vashisht
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
t; To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@l
__
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guid
.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
--
--
Siteshwar Va
email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
--
--
Si
t; List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
--
--
Siteshwar Vashisht
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code
s.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
[1] https://src.fedorap
On Sat, Jul 6, 2024 at 2:05 AM Siteshwar Vashisht
wrote:
> Hello,
>
> I am writing this message to get feedback from the community on possibly
> new defects identified by static analyzers in Critical Path Packages that
> have changed in Fedora 41. For context, please see my p
On Tue, Jul 9, 2024 at 1:16 PM Daniel P. Berrangé
wrote:
> On Sat, Jul 06, 2024 at 02:05:37AM +0200, Siteshwar Vashisht wrote:
> > Hello,
> >
> > I am writing this message to get feedback from the community on possibly
> > new defects identified by static analyzers in
On Tue, Jul 9, 2024 at 2:28 PM Richard W.M. Jones wrote:
> On Tue, Jul 09, 2024 at 01:37:20PM +0200, Siteshwar Vashisht wrote:
> > I request somebody from the tools team to comment on these concerns. We
> only
> > report the defects identified by gcc, clang etc.
>
> You w
On Wed, Jul 10, 2024 at 7:15 AM Tom Stellard wrote:
> On 7/5/24 17:05, Siteshwar Vashisht wrote:
> > Hello,
> >
> > I am writing this message to get feedback from the community on possibly
> new defects identified by static analyzers in Critical Path Packages that
>
On Tue, Jul 9, 2024 at 10:10 PM David Malcolm wrote:
> On Tue, 2024-07-09 at 13:37 +0200, Siteshwar Vashisht wrote:
> > On Tue, Jul 9, 2024 at 1:16 PM Daniel P. Berrangé
> >
> > wrote:
> >
> > > On Sat, Jul 06, 2024 at 02:05:37AM +0200, Siteshwar Vashisht wro
On Wed, Jul 10, 2024 at 12:21 PM Daniel P. Berrangé
wrote:
> On Wed, Jul 10, 2024 at 11:10:34AM +0200, Siteshwar Vashisht wrote:
> > On Tue, Jul 9, 2024 at 10:10 PM David Malcolm
> wrote:
> >
> > > On Tue, 2024-07-09 at 13:37 +0200, Siteshwar Vashisht wrote:
>
On Wed, Jul 10, 2024 at 1:30 AM Daniel P. Berrangé wrote:
>
> On Tue, Jul 09, 2024 at 04:03:10PM -0400, David Malcolm wrote:
> > On Tue, 2024-07-09 at 13:37 +0200, Siteshwar Vashisht wrote:
> > > On Tue, Jul 9, 2024 at 1:16 PM Daniel P. Berrangé
> > >
> > >
On Tue, Jul 16, 2024 at 4:55 PM Kamil Dudka wrote:
>
> On Tuesday, July 9, 2024 12:45:18 PM CEST Siteshwar Vashisht wrote:
> > On Sat, Jul 6, 2024 at 2:05 AM Siteshwar Vashisht
> > wrote:
> >
> > > Hello,
> > >
> > > I am writing this mes
On Wed, Jul 17, 2024 at 2:32 PM Siteshwar Vashisht wrote:
>
> On Wed, Jul 10, 2024 at 1:30 AM Daniel P. Berrangé
> wrote:
> >
> > On Tue, Jul 09, 2024 at 04:03:10PM -0400, David Malcolm wrote:
> > > On Tue, 2024-07-09 at 13:37 +0200, Siteshwar Vashisht wrote:
&g
On Wed, Jul 10, 2024 at 12:29 PM Siteshwar Vashisht
wrote:
>
>
>
> On Wed, Jul 10, 2024 at 12:21 PM Daniel P. Berrangé
> wrote:
>>
>> On Wed, Jul 10, 2024 at 11:10:34AM +0200, Siteshwar Vashisht wrote:
>> > On Tue, Jul 9, 2024 at 10:10 PM David Malcolm wrot
On Tue, Jul 9, 2024 at 2:28 PM Richard W.M. Jones wrote:
>
> On Tue, Jul 09, 2024 at 01:37:20PM +0200, Siteshwar Vashisht wrote:
> > I request somebody from the tools team to comment on these concerns. We only
> > report the defects identified by gcc, clang etc.
>
> You w
Hello,
I am writing this email to get feedback from the members of the Fedora
development community about OpenScanHub for Fedora.
# tl;dr
OpenScanHub does static and dynamic analysis of rpm packages and it may be
helpful in the Fedora community. Please take a look at our staging proof of
concept
On Tue, Dec 12, 2023 at 4:30 PM Siteshwar Vashisht
wrote:
> Hello,
>
> I am writing this email to get feedback from the members of the Fedora
> development community about OpenScanHub for Fedora.
>
> # tl;dr
>
> OpenScanHub does static and dynamic analysis of rpm packages
Hello,
This is a follow up on my previous email[1] about OpenScanHub Prototype for
Fedora.
Thank you to those who have provided early feedback. Your help is truly
appreciated!
I am writing this message to get feedback from the community on possibly
new defects identified by static analyzers in Co
R.F.
>
> [1] https://openscanhub.fedoraproject.org/task/135/log/stdout.log
>
>
> On 4/24/24 09:26, Siteshwar Vashisht wrote:
> > Hello,
> >
> > This is a follow up on my previous email[1] about OpenScanHub Prototype
> > for Fedora.
> > Thank you to t
ra 41?
> >
> > Thank you,
> > Carlos R.F.
> >
> > [1] https://openscanhub.fedoraproject.org/task/135/log/stdout.log
> >
> >
> > On 4/24/24 09:26, Siteshwar Vashisht wrote:
> >> Hello,
> >>
> >> This is a follow up on my previ
On Wed, Apr 24, 2024 at 6:26 PM Siteshwar Vashisht
wrote:
> Hello,
>
> This is a follow up on my previous email[1] about OpenScanHub Prototype
> for Fedora.
> Thank you to those who have provided early feedback. Your help is truly
> appreciated!
>
> I am writing this mess
://openscanhub.fedoraproject.org/task/
[5] https://fedoraproject.org/wiki/OpenScanHub
--
Siteshwar Vashisht
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
- Original Message -
> From: "Siteshwar Vashisht"
> To: devel@lists.fedoraproject.org
> Sent: Tuesday, May 2, 2017 3:42:14 PM
> Subject: RFC: Always sourcing /etc/bashrc for interactive mode in bash
>
> We are discussing about always sourcing /etc/bashrc f
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
[1] https://lists.fedoraproject.org/pipermail/devel/2011-July/154902.html
--
--
Siteshwar Vashisht
___
- Original Message -
> From: "Tomas Orsava"
> To: "Development discussions related to Fedora"
> , "David Kaspar" ,
> "Kamil Dudka" , "Miro Hrončok" ,
> "Petr Viktorin" ,
> "Siteshwar Vashisht"
- Original Message -
> From: "Vít Ondruch"
> To: devel@lists.fedoraproject.org
> Sent: Wednesday, May 2, 2018 4:46:12 PM
> Subject: Re: Prioritizing ~/.local/bin over /usr/bin on the PATH
>
>
>
> Dne 2.5.2018 v 16:35 Siteshwar Vashisht napsal(
TH
>
> On Wed, May 02, 2018 at 10:35:28AM -0400, Siteshwar Vashisht wrote:
> >
> >
> > - Original Message -
> > > From: "Tomas Orsava"
> > > To: "Development discussions related to Fedora"
> > > , "David Kaspar" ,
&
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
--
--
Siteshwar Vashisht
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
tps://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VB2E4CRXYFXXISRWK2YXPVSTM4OWSAJO/
>
[1] https://src.fedoraproject.org/rpms/bash/pull-request/7
--
--
Siteshwar Vashisht
___
devel mailing list -- devel@lists.fedo
On Thu, Nov 14, 2024 at 10:23 PM Richard W.M. Jones wrote:
>
> On Thu, Nov 14, 2024 at 08:47:36AM +0100, Siteshwar Vashisht wrote:
> > Hello,
> >
> > I am writing this message to get feedback from the community on new
> > findings by static analyzers in Cr
On Thu, Nov 14, 2024 at 10:47 PM Kevin Fenzi wrote:
>
> What does it mean when the table lists the package version as 'el8'?
I was trying to reuse some scripts that are used to generate reports
for RHEL and they did not work as expected. I have fixed it now.
Please take a look at the report again
Hello,
I am writing this message to get feedback from the community on new
findings by static analyzers in Critical Path Packages that have
changed in Fedora 42.
TLDR: This report[1] contains 37330 findings. Please review the report
and provide feedback.
A mass scan was performed this week on th
0], so we can hopefully squash the false
> > > > > > positives from the results (at least the ones repored by
> > > > > > gcc's -fanalyzer) and make them more useful.
> > > > > >
> > > > > > One thing that comes to mind (es
40 matches
Mail list logo
