bpmedley | LeePen : I can try. How do I start? | 00:07 |
---|---|---|
Gonarh | Hiall | 02:02 |
Gonarh | Have place in HDD, and good bandwidth for upload. Want help devuan, make mirror, but need manual how make it. Anybody can help me with it? | 02:05 |
onefang | http://pkgmaster.devuan.org/devuan_mirror_walkthrough.txt is the instructions we use. | 02:06 |
Gonarh | Thx | 02:07 |
onefang | That's for a package mirror, there are also ISO mirrors. Which sort do you wan to do? | 02:07 |
Gonarh | How many take place ISO mirrors? | 02:08 |
onefang | 54 GB for an ISO mirror. | 02:08 |
Gonarh | Then, all | 02:09 |
onefang | I suggest you make a package mirror first, following those instructions. Then you will know most of what you need to know to make an ISO mirror. | 02:10 |
Gonarh | Ok, thx | 02:11 |
onefang | And I should someday expand those instructions to include ISO mirrors. B-) | 02:13 |
Gonarh | No have time? | 02:14 |
onefang | I also suggest you have the package mirror at http://gonarh.net/devuan/ and the ISO one at http://gonarh.net/devuan-cd/. Or whatever your domain name will be. | 02:14 |
Gonarh | ok | 02:16 |
onefang | I'm working my way through my Devuan TODO list, I haven't gotten to the "Update the mirror walkthrough" one yet. | 02:16 |
golinux | onefang: Gonarh: https://files.devuan.org/MIRRORS.txt | 02:19 |
onefang | I keep forgetting about that file, thanks golinux. | 02:20 |
Gonarh | second manual simple than first | 02:20 |
Gonarh | Oh, its part | 02:21 |
onefang | This is why I have to "Update the mirror walkthrough". B-) | 02:21 |
LeePen | bpmedley: Have you done much packaging before? | 10:47 |
LeePen | I will need to write a basic guide. Most of the online documentation relating to debian is relevant. Except Devuan builds directly from git, so you need to test your builds with gbp-buildpackage. | 10:49 |
LeePen | You can create your own account on git.devuan.org. Clone a the package you want to work on from the devuan-packages group. | 10:50 |
LeePen | Merge the correct debian version (rmadison or http://tracker.debian.org is useful here) | 10:50 |
LeePen | Fixup. Test build. Lintian check. Redo. | 10:51 |
LeePen | Then push your tree for review, merge and build. | 10:51 |
LeePen | Does any of that make sense/help? | 10:52 |
* Evilham wants to try crazy things re: pkg building for beowulf++ but needs more time or a clone | 11:16 | |
LeePen | What things do you have in mind? | 11:17 |
onefang | Would Evilhams clone be the good twin? B-) | 11:18 |
onefang | We shall cal him Bacon, coz Bacon is always good. | 11:19 |
Evilham | I've been thinking about maintaining just one repo with the patches that are applied to debian's packages, kinda the way BSD ports work and I think that's realistic for most of the packages in devuan | 11:26 |
Evilham | but it's a non-trivial amount of work (though I think it can make maintenance significantly easier) | 11:27 |
Evilham | (also: obviously my clone would be spam) | 11:27 |
onefang | lol | 11:28 |
LeePen | Evilham: Yes, having been wading through this for the last few wees, I am not convinced what we have is neccessarily the most efficient or stable. | 11:30 |
LeePen | I am constantly amazed at the new failure modes I can trigger :-# | 11:30 |
Evilham | :-D good realisation | 11:30 |
LeePen | Ian Jackson was/is working on similar things in debian. | 11:31 |
LeePen | dgit.. | 11:31 |
Evilham | thing is: his proposal is a lot closer to what devuan does as to what debian does | 11:32 |
Evilham | but the scale of doing it for debian is totally different | 11:32 |
LeePen | I know, in one sense we are both chasing each other. | 11:32 |
LeePen | Absolutely. | 11:32 |
Evilham | so one of the reasons why I think having a monorepo with patches would be a decent idea, is that it makes the diff against debian more transparent and means that it's easier to know which issues are debian issues and which are devuan issues, so everyone wins | 11:33 |
LeePen | Yes, I see that. | 11:34 |
Evilham | for example your packages wouldn't necessarily be a good fit for that, since you have less friction to make libelogind the default and things like that | 11:34 |
LeePen | And for src:elogind we are the upstream for debian rather than the other way round. | 11:35 |
Evilham | exactly :-) | 11:35 |
LeePen | That might apply to eudev when gnu_srs1 gets it included. | 11:35 |
LeePen | Hmmmm. Definitely worth more thought. | 11:36 |
Evilham | but in any case, it's something I could totally propose for beowulf++ since that allows for more time to actually develop, implement, test and deploy things | 11:36 |
LeePen | OK. I am also keen that we don't get so far behind in the future which will also make things easier. | 11:37 |
Evilham | yup | 11:37 |
Evilham | aaanyway, back to taking a look at k8s because $reasons '-.- | 11:38 |
telmich | Evilham: poor you | 13:19 |
telmich | Evilham: I'm also looking at it every month, but the more I look the less I am convinced | 13:19 |
bpmedley | LeePen : Makes sense. I'll try, but I have little packaging experience.. | 13:20 |
Evilham | telmich: in this case I think it beats deploying an "enterprisy" thing by hand | 16:18 |
Evilham | "enterprisy" --> documentation sucks and it assumes all kinds of weird configs | 16:19 |
Evilham | aanyway, enough OT here :-D | 16:19 |
telmich | Evilham: :-) | 16:20 |
onefang | You forgot the most important part of being "enterprisy", overpriced. | 16:21 |
HumanGeek | hi | 18:34 |
HumanGeek | there is no backport stabe repo ? | 18:34 |
HumanGeek | E: The repository 'tor+http://devuanfwojg73k6r.onion/merged stable-backport Release' does not have a Release file. | 18:35 |
fsmithred | HumanGeek, ascii is still the stable release | 18:45 |
fsmithred | yet buster is stable in debian | 18:45 |
fsmithred | if you use "stable" in sources.list you will have problems | 18:46 |
fsmithred | ascii-backports | 18:46 |
HumanGeek | huum | 18:47 |
HumanGeek | ok | 18:48 |
plasma41 | LeePen Centurion_Dan: The fdisk package is missing from ascii. | 22:44 |
LeePen | plasma41: Thanks. I'll have a look tomorrow. | 22:45 |
plasma41 | Did a move in dak go awry? | 22:46 |
LeePen | Possibly... | 22:47 |
plasma41 | LeePen: Nevermind. The fdisk binary was included in the util-linux binary package in stretch. It wasn't moved to its own binary package until buster. My mistake. | 22:53 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!