Changes regarding debian.sur5r.net
(too old to reply)
Jakob Haufe
2017-06-22 14:38:23 UTC
Hi everyone,

- - New repository debian.sur5r.net/rofi
- - New repository debian.sur5r.net/suckless-tools
- - suckless-tools will be removed from debian.sur5r.net/i3

If you want or need more details, please read on.

As many of you know, I've been providing a repository containing backports of
i3 for Ubuntu (and inofficially for Debian as well) for several years now.

I noticed that I never publicly documented how I operate the repository, so I
will finally do so, together with some upcoming changes.

== How debian.sur5r.net/i3 operates ==

1. For each distribution supported by my repository, the current official
version of the packages will be imported. No changes are applied.

2. Whenever a new version of i3{,lock,status} gets
uploaded to Debian sid or experimental, the source package gets imported
as-is to an internal-only distribution named "upstream-sources".

3. For each distribution, a new source package is generated. The only change
applied to it is a new changelog entry mentioning the backport. The version
is amended in such a way that any official package matching the upstream
version will supersede my package.

Example: The current version of i3lock in Debian stretch is 2.8-1. The
current version of i3lock in Debian unstable is 2.9.1-1. In case 2.9.1-1 gets
backported by Debian itself, it will be versioned 2.9.1-1~bpo9+1. My backport
for stretch would is versioned 2.9.1-1~~stretch1. As the tilde character sorts
lower than anything else (in a version comparison by dpkg), my package gets
only installed if no official backport is available.

4. Binary packages for amd64, i386 and armhf are built using sbuild.

5. In case there are missing dependencies, those will be backported in the
same manner.

6. Once everything is built the new state of the repository is released to the public.

Please feel free to ask me any questions you might have about this process.

== Upcoming changes to debian.sur5r.net ==

Several years ago, I was asked to provide packages for suckless-tools as
well. Since it was not a lot of work, I added them to debian.sur5r.net/i3.

This has been a bad decision. Suddenly, users end up with an unexpected
update to suckless-tools from a repository which is supposed to only contain i3.

I did not realize this back then and nobody complained, so it stayed that way
for several years.

Fast-forward November 2016: I was asked on #i3 whether I could provide
backports for rofi as well. I said I would look into it again was not much
work, did so. This time I created a separate repository,
debian.sur5r.net/rofi, while realizing that suckless-tools should have been
separated as well.

A couple of days ago, I finally created debian.sur5r.net/suckless-tools, so
everything has its separate place.

Right now, suckless-tools are still part of debian.sur5r.net/i3, but I will
remove them from that repository by the upcoming weekend.

I hope I could clarify a little what I'm doing behind the curtain. Again, if
there are any questions, please feel free to contact me.

ceterum censeo microsoftem esse delendam.
Boruch Baum
2017-06-22 16:56:00 UTC
Post by Jakob Haufe
Hi everyone,
I hope I could clarify a little what I'm doing behind the curtain.
Again, if there are any questions, please feel free to contact me.
Thanks for all the work.

CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0