Existing Papercuts

[deadwood]

I will be happy to verify the ones that are still present in Deadwoods backport.   However if some users could test a bug they find in the latest Icaros against a current nightly that would be greatly appreciated.    The more bugs we find the sooner we can start rewarding bug fixes.

Some comments from me:

1) I commit to back porting paper cuts fixes to ABIv0 where possible. ABIv0 codebase is still 3 years behind (2900 commits behind), so 100% will not be possible, but I'm pretty sure around 90% of paper cut fixes can be backported.

2) I still think we should let users find out bugs on where it is most convenient for them provided they are clear on what version they used for testing. If you want people to participate, you need to make entry threshold as low as possible. If they can verify on nightly from www.aros.org - even better. Seems I agree here with @terminills is saying.

[terminills]

terminills, the bugs you find in the Distribuzini, you find them in the nights as well, they are the same, I have reported many of them to Deadwoods and continue to do so.

If instead of chatting if he used that time to test the software many more bugs would be found.

Not all of them as already pointed out with the whole pen locking example.   The bug exists in Deadwoods branch but not in TRUNK.   Fact of the matter is the existing papercuts list is a decade old and needs to be verified so we can close out the ones that have been fixed at some point.

[AMIGASYSTEM]

Sorry from the online translation I don't know if I understood what you wrote correctly.
 I am not talking about the recompilation bugs in GCC 6.5.0 , the bugs reported by me have always existed even on the older Nightly Builds

[terminills]

Sorry from the online translation I don't know if I understood what you wrote correctly.
 I am not talking about the recompilation bugs in GCC 6.5.0 , the bugs reported by me have always existed even on the older Nightly Builds

Well what are those bugs?  How do you recreate them? Are they in the bug tracker?  Just a reminder not all developers read AE so the bugs really need to make their way into a bug tracker.

[AMIGASYSTEM]

You probably haven't followed the various threads on this forum in recent months, you can find some of my bug reports here:

https://github.com/deadw00d/AROS/issues

[terminills]

You probably haven't followed the various threads on this forum in recent months, you can find some of my bug reports here:

https://github.com/deadw00d/AROS/issues

You are correct I don't follow Deadwoods branch.  I follow the AROS project as a whole.  And there lies another problem Deadwood is one developer and the goal is to bring more developers not land all the issues in deadwwods lap. There needs to be a central location for bugs that all developers look at in order for the papercuts project to work.   

https://github.com/aros-development-team/AROS/issues

[AMIGASYSTEM]

As mentioned, the bugs I mentioned have always existed on AROS on any Branch.

I am not a developer but I am very experienced on many OS, I am very picky and I check every single file, both a basic AROS and my AROS One where you find everything and more, try it.

https://sites.google.com/view/arosone

[terminills]

As mentioned, the bugs I mentioned have always existed on AROS on any Branch.

I am not a developer but I am very experienced on many OS, I am very picky and I check every single file, both a basic AROS and my AROS One where you find everything and more, try it.

https://sites.google.com/view/arosone

My point was the bugs should be listed in the main repo bug tracker unless they are APP based.  but if they are in deadwoods and not the main repo I will compare with the latest nightlies and put the reports in the main repo bug tracker.

[deadwood]

My point was the bugs should be listed in the main repo bug tracker unless they are APP based.  but if they are in deadwoods and not the main repo I will compare with the latest nightlies and put the reports in the main repo bug tracker.

Just a hint: If an issues in my bugtracker is marked as Project:Core it is highly probabel that it exists also in https://github.com/aros-development-team/AROS. My master branch (=Core) is very close to that repository.

[terminills]

My point was the bugs should be listed in the main repo bug tracker unless they are APP based.  but if they are in deadwoods and not the main repo I will compare with the latest nightlies and put the reports in the main repo bug tracker.

Just a hint: If an issues in my bugtracker is marked as Project:Core it is highly probabel that it exists also in https://github.com/aros-development-team/AROS. My master branch (=Core) is very close to that repository.

Okay that helps. I'm just trying to make sure the bug tracker is up to date.

[deadwood]

Also you can skip everything that has Project:AxRuntime. It's not relavant in this excercise.

[Mysha]

So, if that link shows Papercuts, how will we recognise them between the other reports?

Bye,
Mysha

[deadwood]

This link shows existing (since around 2011) Papercuts:

https://sourceforge.net/p/aros/papercuts/

[Mysha]

This link shows existing (since around 2011) Papercuts:

https://sourceforge.net/p/aros/papercuts/

Ah, thanks.

Well, that gives us an interesting one (Should I start a new topic for every papercut?) -
#53 "File is not executable" instead of "Out of memory".
Which is the observed behaviour, and which is the desired behaviour?