Hi Marcel, On Mo 01 Jun 2020 18:04:15 CEST, marcel wrote:
On Mo 01 Jun 2020 10:41:45 CEST, Bernhard Miklautz wrote:Hi Mike, On Mon, Jun 01, 2020 at 08:30:22AM +0000, Mike Gabriel wrote:On Mo 01 Jun 2020 10:23:59 CEST, Bernhard Miklautz wrote: I saw that the ogon.git's HEAD e.g. is +40 commits further advanced than the 1.0.0 release. (I haven't checked the others, so far). Wouldn't it make sense to either tag some recent state with a release tag on the upstream side? Or package HEADs of master branches, instead (this was my recommendation).The tagged version is really heavily tested in production whereas any change after 1.0.0 aren't. Therefore I'd recommend to stay as close as possible to 1.0.0 for now. But if there is anything build/package related where a tag/release would help I gladly create one. Staying close to HEAD would also make sense but there are some (functional) PRs pending and this might break things at some point. So long, Bernhardok, this eases the packaging / upstream orig tarball retrieval. @Marcel: v1.0.0 it will be then...
Hi Mike,I had just finished the "HEAD" version and did first successful compiles with sbuild.
Oh well, I am sorry for having caused this confusion.
Now changed to the "stable" v1.0.0 release branch for all packages (besides libxfont, haven't yet figured out, how to do the version matching when a certain branch is needed).Maybe Bernhard can explain if (when) the libxfont package is needed at all.
Yeah, this is indeed interesting. Why do we need a separate libxfont for ogon? Is that still libxfont1? Or libxfont2? Porting from libxfont1 to libxfont2 is easy, btw.
However the 1.0.0 release of ogon does not compile with current freerdp :-((And I guess several other packages won't either, since I provided some patches to make that work myself).
Urgh. Bernhard, any feedback on this?
How to we deal with that? Cherry-picking the patches to make it compile?
I'd say so, if 1.0.0 is otherwise very well tested.
And some more questions about the (s)build stuff:- How do you compile packages that depend on other packages not available in the debian repo (like the ones I compiled myself: e.g. ogon <- ogon-apps) ?
I have my own reprepro instance for that: https://packages.sunweavers.net/debian/Unfortunately, Debian does not have "bikesheds" yet (which is a PPA-like concept for Debian).
If you need you own reprepro space, I can provide you with an SSH account on my server and set up a reprepro instance there for you. If you have SSH servers on the internet where you can install software yourself, please follow this howto:
https://wiki.debian.org/DebianRepository/SetupWithReprepro(I skipped over the howto with a scroll and it looks ok. If you stumble on any problems, don't hesitate to ask).
Greets, MikePS: I'd be happy if you could follow the bottom-posting mailing style for list (and in fact, any other) mailings:
https://en.wikipedia.org/wiki/Posting_style#Bottom-posting -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Attachment:
pgp0Pv8257PyB.pgp
Description: Digitale PGP-Signatur