Bug#1061743: Gramps in Debian

2024-06-10 Thread Dr. Tobias Quathamer

Am 03.06.24 um 06:55 schrieb Ross Gammon:

I will try and take a look this week. But if I fail, either of you are
welcome to lose patience, merge it to master, and upload it for me. :-)


Hi Ross,

I've decided to lose patience. :-)

No, seriously, I've built Gramps locally and did some test runs with it. 
Everything seems to work fine, so I've pushed my latest changes to 
salsa, merged it into the master branch, and uploaded to unstable.


Regards,
Tobias



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061743: Gramps in Debian

2024-06-02 Thread Ross Gammon

Hi both,

Thanks so much for doing this.

On 27.05.2024 19.49, Dr. Tobias Quathamer wrote:

Am 27.05.24 um 15:38 schrieb IOhannes m zmölnig (Debian GNU|Linux):

On 5/26/24 23:56, Dr. Tobias Quathamer wrote:


The package builds on my machine, although I had to disable a single
test for now. You'll find it in the newly created patch. Maybe you
have an idea what's causing the failure, so it can be fixed properly.


https://gramps-project.org/bugs/view.php?id=13305

i think this is just a wrong assumption on the side of the upstream
testsuite (shadowed by their workflows).

upstream evades this by ensuring that "~/.gramps/" is there before
running the tests (both in their GitHub action, and in their debian/
packaging).

i think that for now the proper resolution for the problem is to
simply do a `mkdir "$CURDIR)/build/.gramps` before running the tests.
(which i've now pushed to the 'experimental' branch)


Great, thanks! That's a cleaner approach.


as a sidenote: the testsuite now creates a *very* verbose buildlog
(~420MB).
is that ok?

gf,madsr
IOhannes


Hm, I guess that's because of the "--verbose" option when running the
tests. However, the buildlog has been similarly large in v5.1.6 as
well. Could that to be due to the switch from nosetest to unittest?

Maybe the --verbose option should be dropped? The buildlog gets
shrinked to 1.4 MB, but the tests are only displayed as dots.


Yes the build log is huge, and has been for a while. If you try and view
it in a browser it never loads!

I would be happy to turn the --verbose option off until it is needed one
day.



Regards,
Tobias



I will try and take a look this week. But if I fail, either of you are
welcome to lose patience, merge it to master, and upload it for me. :-)

Regards

Ross



Bug#1061743: Gramps in Debian

2024-05-27 Thread Dr. Tobias Quathamer

Am 27.05.24 um 15:38 schrieb IOhannes m zmölnig (Debian GNU|Linux):

On 5/26/24 23:56, Dr. Tobias Quathamer wrote:


The package builds on my machine, although I had to disable a single 
test for now. You'll find it in the newly created patch. Maybe you 
have an idea what's causing the failure, so it can be fixed properly.


https://gramps-project.org/bugs/view.php?id=13305

i think this is just a wrong assumption on the side of the upstream 
testsuite (shadowed by their workflows).


upstream evades this by ensuring that "~/.gramps/" is there before 
running the tests (both in their GitHub action, and in their debian/ 
packaging).


i think that for now the proper resolution for the problem is to simply 
do a `mkdir "$CURDIR)/build/.gramps` before running the tests.

(which i've now pushed to the 'experimental' branch)


Great, thanks! That's a cleaner approach.

as a sidenote: the testsuite now creates a *very* verbose buildlog 
(~420MB).

is that ok?

gf,madsr
IOhannes


Hm, I guess that's because of the "--verbose" option when running the 
tests. However, the buildlog has been similarly large in v5.1.6 as well. 
Could that to be due to the switch from nosetest to unittest?


Maybe the --verbose option should be dropped? The buildlog gets shrinked 
to 1.4 MB, but the tests are only displayed as dots.


Regards,
Tobias



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061743: Gramps in Debian

2024-05-27 Thread Debian GNU|Linux

On 5/26/24 23:56, Dr. Tobias Quathamer wrote:


The package builds on my machine, although I had to disable a single 
test for now. You'll find it in the newly created patch. Maybe you have 
an idea what's causing the failure, so it can be fixed properly.


https://gramps-project.org/bugs/view.php?id=13305

i think this is just a wrong assumption on the side of the upstream 
testsuite (shadowed by their workflows).


upstream evades this by ensuring that "~/.gramps/" is there before 
running the tests (both in their GitHub action, and in their debian/ 
packaging).


i think that for now the proper resolution for the problem is to simply 
do a `mkdir "$CURDIR)/build/.gramps` before running the tests.

(which i've now pushed to the 'experimental' branch)

as a sidenote: the testsuite now creates a *very* verbose buildlog (~420MB).
is that ok?

gf,madsr
IOhannes


OpenPGP_0xB65019C47F7A36F8.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061743: Gramps in Debian

2024-05-26 Thread Dr. Tobias Quathamer

Am 24.05.24 um 21:23 schrieb Ross Gammon:

Hi Tobias,

There are no blockers other than real life getting in the way. I did
start working on 5.2.0 in the experimental branch on Salsa. From memory,
there was a problem with fuzzy patches, and the tedious checking of
copyrights still to do. But I should probably merge the changes into
master, and then import 5.2.2.

If you have some spare cycles you are welcome to help move things along.
I use gbp + quilt.

Regards,

Ross


Hi Ross,

I took some time to update the experimental branch to v5.2.2 and fix 
some FTBFS with the new upstream version. I've pushed my work to Salsa, 
please take a look if you have some time.


The package builds on my machine, although I had to disable a single 
test for now. You'll find it in the newly created patch. Maybe you have 
an idea what's causing the failure, so it can be fixed properly.


I haven't looked at the copyrights for now.

Regards,
Tobias



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061743: Gramps in Debian

2024-05-24 Thread Ross Gammon

Hi Tobias,

There are no blockers other than real life getting in the way. I did
start working on 5.2.0 in the experimental branch on Salsa. From memory,
there was a problem with fuzzy patches, and the tedious checking of
copyrights still to do. But I should probably merge the changes into
master, and then import 5.2.2.

If you have some spare cycles you are welcome to help move things along.
I use gbp + quilt.

Regards,

Ross

On 28.04.2024 17.40, Dr. Tobias Quathamer wrote:

Hi Ross,

I'd like to get gramps back into Debian, and from my (very limited)
research it seems that gramps v5.2.1 fixed the build failure on Debian.

Are you planning to update the package? Or is there another blocker
which I didn't spot?

Thanks for taking care of gramps in Debian!

Regards,
Tobias




Bug#1061743: Gramps in Debian

2024-04-28 Thread Dr. Tobias Quathamer

Hi Ross,

I'd like to get gramps back into Debian, and from my (very limited) 
research it seems that gramps v5.2.1 fixed the build failure on Debian.


Are you planning to update the package? Or is there another blocker 
which I didn't spot?


Thanks for taking care of gramps in Debian!

Regards,
Tobias


OpenPGP_signature.asc
Description: OpenPGP digital signature