#931595 ITP: mutest -- testing framework for C

Package:
wnpp
Source:
wnpp
Submitter:
Arnaud Rebillout
Date:
2025-11-29 16:44:34 UTC
Severity:
wishlist
#931595#5
Date:
2019-07-08 04:34:43 UTC
From:
To:
* Package name    : mutest
  Version         : 2019.1
  Upstream Author : Emmanuele Bassi <ebassi@gmail.com>
* URL             : https://github.com/ebassi/mutest
* License         : MIT
  Programming Lang: C
  Description     : testing framework for C

µTest aims to be a small unit testing library for C projects, with an API
heavily modelled on high level Behavior-Driver Development frameworks like
Jasmine or Mocha.
.
µTest is written in C99, and can be used on multiple platforms.
----

I'd like to maintain this package with the GNOME packaging team.
#931595#10
Date:
2019-08-02 11:29:12 UTC
From:
To:
graphene already uses a bundled copy of mutest, so it would seem
appropriate to maintain the unbundled version in the GNOME team too.

However, at the moment mutest is explicitly not stable:

    **WARNING**: µTest's API is still in flux!

so I don't think it would be appropriate for packages like Graphene
to use a system copy at this stage. The documentation says:

    The preferred way to use µTest is to include it in your own projects
    using a Git sub-module, and then building µTest as a static library.

which I think meets the "unless the included package is explicitly
intended to be used in this way" criterion in Policy §4.13.

I'll try to review this at some point. Hopefully it'll be very similar
to the copy bundled in graphene.

I don't think this should be in unstable at the moment, but it could
go to experimental, alongside other specifically-not-stable projects
like gtk+4.0.

I would personally prefer Salsa.

Someone on the Owners list will have to do this; but if nobody gets round
to it, I can create an empty mutest project and give you access to it,
and you can work that way?

    smcv
#931595#15
Date:
2019-08-02 14:15:35 UTC
From:
To:

Alright, then maybe better wait for a release of mutest, no need to
review my packaging now. There's no rush. I will ping again on this
mailing list when mutest releases a version, and my packaging is ready.


Me as well, perfect.


Sounds good to me, thanks!

  Arnaud
#931595#20
Date:
2019-11-18 14:46:28 UTC
From:
To:
I've created an empty repository https://salsa.debian.org/gnome-team/mutest
and given you access. You should be able to push your WIP packaging there.

A gnome-team Owner (ah, biebl, bigon, jbicha, laney, mitya57, pochu or
seb128) will still need to give you access if you want to push directly
to other GNOME packages (I don't have enough access to do this), or you
can fork the package in your own namespace and send merge requests.

    smcv
#931595#25
Date:
2019-11-19 11:15:30 UTC
From:
To:
Thanks!

I just tried, and it doesn't work yet. An Owner must create the default
branch `debian/master` before I can push.

~~~~

$ git push -u origin debian/master
Enumerating objects: 708, done.
Counting objects: 100% (708/708), done.
Delta compression using up to 8 threads
Compressing objects: 100% (329/329), done.
Writing objects: 100% (708/708), 331.09 KiB | 47.30 MiB/s, done.
Total 708 (delta 443), reused 590 (delta 373)
remote: Resolving deltas: 100% (443/443), done.
remote: GitLab:
remote: A default branch (e.g. master) does not yet exist for
gnome-team/mutest
remote: Ask a project Owner or Maintainer to create a default branch:
remote:
remote: https://salsa.debian.org/gnome-team/mutest/-/project_members
remote:
To salsa.debian.org:gnome-team/mutest.git
  ! [remote rejected] debian/master -> debian/master (pre-receive hook
declined)
error: failed to push some refs to
'git@salsa.debian.org:gnome-team/mutest.git'
#931595#30
Date:
2019-11-20 14:08:21 UTC
From:
To:
I pushed the branches from https://salsa.debian.org/arnaudr-guest/mutest,
with debian/master as the default.

    smcv
#931595#35
Date:
2019-11-21 02:04:33 UTC
From:
To:
Thanks Simon,

I could push some more commits on the pristine-tar and upstream/latest
branches, I could push tags, but I'm still not allowed to push anything
on debian/master.

$ git push
Enumerating objects: 10, done.
Counting objects: 100% (10/10), done.
Delta compression using up to 8 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 844 bytes | 844.00 KiB/s, done.
Total 6 (delta 4), reused 0 (delta 0)
remote: GitLab: You are not allowed to push code to protected branches
on this project.
To salsa.debian.org:gnome-team/mutest.git
  ! [remote rejected] debian/master -> debian/master (pre-receive hook
declined)
error: failed to push some refs to
'git@salsa.debian.org:gnome-team/mutest.git'

  Arnaud
#931595#40
Date:
2019-11-21 08:29:43 UTC
From:
To:
Try now? I've copied the Protected Branches settings from gnome-team/glib.

    smcv
#931595#45
Date:
2019-11-21 08:33:23 UTC
From:
To:

Ok now, I could push everything, so this is all ready for review.

As you can see it's a snapshot, until upstream releases something.

Also, mind you that I have close to zero experience packaging libraries,
so expect the newby mistakes.

Cheers!

   Arnaud