Hi Andreas et al, Here's another update on this: it got pointed out to me that I had actual upload rights for my packages and might not need a sponsor after all (I'm in https://ftp-master.debian.org/dm.txt). So I prepared all the packages again and ran dupload on them.
That seemed to go well, except I now got two rejections:
ticcutils_0.36-1_source.changes REJECTED
ACL dm: NEW uploads are not allowed
binary:libticcutils10 is NEW.
libfolia_2.21-1_source.changes REJECTED
ACL dm: NEW uploads are not allowed
binary:folialint is NEW.
binary:libfolia22 is NEW.
All other packages got ACCEPTED (however, they rely on the rejected ones
so things won't work).
The package counts as new because of the SO-bump we did, but it seems I
don't have the permissions to upload that? I don't really know how to proceed
now anymore...
>> Since these packages are depending from the first one I did not
>> continued. If you want to do your final sponsor a favour please
>> set the target distribution of those packages to "UNRELEASED" again
> Done, I reverted them to UNRELEASED and updated them (there was no
> routine-update in debian testing though, so I did it manually)
I had reverted the reversion again (can you still follow? they're back
to 'unstable' because I released them now). All 'debian/*' git tags are
also set and pushed now.
Regards,
--
Maarten van Gompel
Digital Infrastructure, Humanities Cluster,
Koninklijke Nederlandse Akademie van Wetenschappen (KNAW)
web: https://proycon.anaproy.nl
gpg: 0x39FE11201A31555C
signature.asc
Description: PGP signature
