(improves… tastes are very different I guess, but that is fine.
It reminds me of an unfinished branch though… a well, one day.)
Yes, improves here is very subjective, I agree.
Anyway, 'undo' in relation to Upgrades triggers my spider-senses as
downgrades are in general not supported.
I should probably update this in the readme, but rolling back upgrades
is unsupported in Nala. You will receive an error if you run `undo` on
an upgrade transaction
I have considered attempting to implement this, but it does seem like a
bad idea. Maybe one day with a warning and an explicit flag, but for now
there is too much other work to do.
As your entire downloading and verification process is written by you
rather than using libapt I would prefer a note here mentioning this.
I can definitely add a disclaimer saying that apt has no hand in
downloading or verification when using Nala.
(Again, see Disclaimer. This is not a security review. I also don't
want
to imply that you have security bugs. Heck, perhaps libapt has more.
My point is entirely on: Please be upfront on rolling your own)
Nala is still in active development, but it is very usable. I've had
many people ask me about getting this into the Official Debian repos
so
this is my request for that.
I assume that I would be in need of a sponser considering I've never
uploaded anything into a Debian repository. But I did try my best to
make the debian files proper, and I personally use sbuild for building
the software.
Your 'critical' bugfix in v0.6.0 e.g.
is a bug worthy of a CVE and would need to be backported into older
versions for stable and every other release supported by Debian
(ideally
with coordination with the other distros with embargos and such).
If Upstreams solution to that problem was so far to "just upgrade to
the
newest version" at least one of you is in for some work (I know you are
both, its just easier to realize that these are two different jobs if
we
pretend you are not).
There will definitely be a lot of things to get use to with having this
in
the main repositories. But I am willing and excited to learn. I have
packaged a few things with quilt patches so I'm a little familiar on how
that would go for backporting.
And last but not least: If you decide you want to be a maintainer, head
over to debian-mentors and read about Requests For Sponsorship (RFS)
which helps you getting your ITP package you prepared into Debian while
you are still learning the ropes and hence do not have rights to upload
unsupervised into Debian yourself yet.
(As this is python, the python team might be interested in helping
maintaining it if you apply to them. While I would be happy if you
would try to interact with us from the apt team, I don't think we
have the resources to help you with packaging through.)
I will find some time today to read up on this. I would like to be the
maintainer as I think that may be the easiest path forward once I learn
the ropes.
Thanks,
Blake
