A.k.a. raw development todo.
Some current notes/news about release planning:
I finally decided 1.0.29 to be sufficiently good to kick off 1.1.x development from there, and 1.0.x now again strictly for bugs only.
I will …
The current sid/stretch Debian development cycle was (and still is) very busy, and changes continuously broke mini-buildd ;).
Partly substantial changes to mini-buildd stable code was needed to keep things going. All in all, this stable development cycle compromises over 300 commits, closing about 25 actual Debian bugs and …
Some notes/news about release planning:
Within stretch development, lots of changes in 1.0.x were needed to accomodate for new versions of packages in sid.
As this needed/needs quite some elaborate changes to the code anyway, I also broadened the …
Newer apt versions warn if the repository release files are signed using "weak" digests algorithms like SHA1:
W: http://mini-buildd-uff.ta.ta:8066/repositories/test/dists/sid-test-unstable/InRelease: Signature by key FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF uses weak digest algorithm (SHA1)
This should usually not occur as mini-buildd is ignorant of the digest used …read more
For some time now, Debian supports automatic debug packages ("dbgsym"). These will just be available now, for any package now rebuild for sid/stretch, without any extra support needed in the source package.
So, does mini-buildd support this, too? Of course -- actually no change at all was needed …read more
This is rather "a note to self"; maybe this is of any worth for others too...
Since recently, I own a new Thinkpad T460s, including a "NVM Express" ('NVMe') SSD.
Unfortunately, plain jessie can't deal with initramfs creation for nvme properly, and also some other skylake related updates seem mandatory …read more
hyde is unmaintained as it seems, so this here website is now relaunched using the new hot shit on the sky of static web site generators, pelican. At least, it all-in-all provides less pain, and it's still maintained ;).
So I hope everything looks somewhat better now, and nothing is worse …read more
The Debian jessie release implicitly inflicts some mandatary (new apt keys!) as well as some recommended (jessie! stretch! backports-sloppy!) housekeeping on an existing mini-buildd installation.
So this is what I would recommend you to do:
Given how the configuration currently works (i.e., affecting dependencies when you change …
Some notes/news about the release planning concerning official Debian:
We are still in jessie freeze; for mini-buildd release planning, this means (basically purely due to practical considerations) the "1.2 dev kick off" will be delayed at least until jessie is actually …
Page 1 / 2 »