libera/#devuan-dev/ Friday, 2021-04-16

tuxd3vDoes any one here, verify kernels signatures, against autosigner + kernel Developers from Mainline repo?03:57
tuxd3vI am receiving this output when I try to fecth the keys..03:57
tuxd3vhttps://paste.debian.net/hidden/66607756/03:58
tuxd3vgpg: WARNING: unacceptable HTTP redirect from server was cleaned up03:58
tuxd3vthe signatures all mach and the checksum too04:00
tuxd3vbut I don't know why this redirect..04:00
rrqnote: alpha version(s) of chimaera netinstall installer-iso is set up to be published on Mondays at files.devuan.org04:25
rrqonly amd64 atm04:25
fsmithredI'm confused about who owns my projects. I thought I tranferred clearlooks-phenix-deepsea-theme and deepsea-icon-theme to devuan, but they don't come up when I search for them on the dashboard.12:59
fsmithredIf I replace my name in the url with 'devuan' I can find the icon theme, but I get a 404 on the desktop theme. Both projects still appear in my profile as personal projects. Both have been built and have packages in the repo. What's going on?13:01
fsmithredI'd like to remove them from my personal projects, but I want to make sure they exist as devuan projects before I do that.13:02
rrqmmm devuan/clearlooks-phenix-deepsea-theme says it's a fork of fsmithred/... not sure what that means13:05
fsmithredI guess I can just go ahead and delete them. If it deletes the devuan project, I can re-create it and push.13:05
rrqdevuan/deepsea-icon-theme is "normal" (not saying it's a fork)13:06
fsmithredI don't recall what I did differently.13:06
rrqgo ahead13:06
rrqI think the better way would be if the personal is a fork of devuan's ... that would make more sence for merging13:07
rrqnot sure it makes a practical difference though13:08
fsmithredok, I deleted deepsea-icon-theme and now I can't find it on dashboard13:08
rrqI added "packages" team to it ... try agai?13:09
fsmithredclearlooks-phenix-deepsea comes up but not the icon theme13:10
rrqtoo fast :) I just added "packages" to its collaborators as well13:11
rrqmaybe they need "editors" access as well?13:11
fsmithredand it now shows up13:11
fsmithredthinking...13:12
fsmithrednot awake enough yet to answer that13:12
rrq... technically you have admin powers; when the synapses shake13:13
fsmithredmaybe not. I finally figured out the right way to do it.13:13
fsmithredhow to make a patch to apply all the changes.13:13
fsmithredI have the plain clearlooks-phenix theme as a personal repo. That's just what we forked. And that's why you saw it was a fork.13:17
fsmithreddeepsea a fork, I mean13:17
rrqyes, I don't mind ... just that the notion "A is fork of B" to me suggests that B is a "master" into which changes to A are merged.13:21
rrqbut I can handle the "dissonance" :)13:22
fsmithredwhich one is listed as a fork?13:22
rrqdevuan/clearlooks-phenix-deepsea-theme is said to be a fork from fsmithred/clearlooks-phenix-theme13:23
rrqon the gui13:23
fsmithredthe fork is the one that is changed and different from the original/source13:23
fsmithredisn't that correct?13:23
rrqmmm probably there are two competing uses of "fork" ...13:24
rrqthe other is that the "main project" are forked by various developers who then issue "pull requests" for merging in their updates13:25
fsmithredthe personal theme is not mine. I just copied it.13:25
rrqmaybe there are left-handed and right-handed forks :)13:26
fsmithredlol13:26
fsmithredhow do we do it for the packages we sanitize from debian?13:27
onefangDon't forget sporks.13:27
rrq:)13:27
fsmithredand how can I clone a repo from salsa.debian.org?13:28
fsmithredwill they let me create an account there?13:28
rrqdon;t need an account; just use the https access. I usually set it up as a "secondary" remote13:30
rrqto pull from13:30
fsmithredI thought I got asked for a login with that, but maybe I just tried the ssh13:30
rrqif the source is public it shouldn't need login for https access13:31
fsmithredok13:31
fsmithredcan a secondary remote be applied only to one branch?13:31
rrqgit remote add debian https://salsa.debian.org/jadajadajada13:32
fsmithredfor the desktop theme, there's a debian-master branch that I don't change13:32
rrqthen: git pull debian13:32
rrqgives you a branch named "debian/master"13:33
rrqas opposed to the previous "origin/master"13:33
fsmithredI can try that with the clearlooks-phenix theme13:33
rrqalso useful: git log --oneline --all --graph13:37
fsmithredoh, I already have a debian/master branch, and it's the only branch.13:37
rrqright; is that attached to salsa?13:38
fsmithredno, it shows my repo as origin13:38
fsmithredeven after adding debian13:38
rrqah, there is a branch "origin/debian/master"13:39
fsmithredcan I do a set-url on just the fetch?13:39
rrqno I think you need to separate it into 2 remotes13:39
fsmithredwhere do you see origin/debian/master?13:40
rrqgit branch -r13:40
fsmithredso checkout -b master?13:40
fsmithredor some other name?13:40
rrqwell git is a bit funny in applying defaults when possible13:41
fsmithred  origin/HEAD -> origin/debian/master13:41
fsmithred  origin/debian/master13:41
fsmithred  origin/pristine-tar13:41
fsmithred  origin/upstream/latest13:41
rrqgit checkout debian/master13:41
rrqwill focus the workspace on origin/debian/master13:42
fsmithred'already on...13:42
rrqbut you need a second remote .. maybe name it "salsa" then, to avoid confusion13:42
fsmithredwhich one would be the one I would alter if I wanted to do that?13:43
rrqyou need to think in terms of two separate remote stores; the first one called "origin" and the second called "salsa"13:44
rrqeach of them have branches13:45
fsmithredI'm stuck on thinking that one branch is identical to what debian has and one is a branch that I can mess with and change13:45
fsmithredbut both of the names belong to debian13:45
fsmithredthat's what is confusing me13:45
fsmithredwhere's my branch?13:46
rrqprobably the commits on "origin/debian/master" will coinside with (some) commits of "salsa/master"13:46
fsmithredI havfe made no commits13:46
fsmithredother than to put the repo there13:46
rrqyes.. when you copied that first time you got those commits .. maybe you should have used the dual remote notion already then13:48
fsmithredyeah, it would be nice to be able to pull any new changes from debian13:48
fsmithred...just in case he ever notices my bug report.13:50
rrqone option could be to hand-edit the config to "move" the origin remote into a "salsa" remote and link it up with salsa ... a bit complex though13:50
rrqthe easiest is to rather create that second remote and pull; I think git will discover equivalences13:51
rrq(or maybe not)13:51
rrqthen you can delete any unused/unchanged origin branches so that the origin is focussed on suites/unstable13:52
rrqif git doesn't discover equivalences you may need to merge into suites/unstable appropriately13:54
rrqby hand13:54
fsmithredYou asked to pull from the remote 'salsa', but did not specify13:56
fsmithreda branch. Because this is not the default configured remote13:56
fsmithredfor your current branch, you must specify a branch on the command line.13:56
rrqright; how about: git fetch --all13:56
fsmithredwhy can't I just use debian/master?13:56
fsmithredfor pulling from debin13:57
fsmithredFetching origin13:58
fsmithredFetching debian13:58
fsmithredwarning: redirecting to https://salsa.debian.org/desktop-themes-team/clearlooks-phenix-theme.git/13:58
fsmithredFrom https://salsa.debian.org/desktop-themes-team/clearlooks-phenix-theme13:58
fsmithred * [new branch]      debian/master   -> debian/debian/master13:58
fsmithred * [new branch]      pristine-tar    -> debian/pristine-tar13:58
fsmithred * [new branch]      upstream/latest -> debian/upstream/latest13:58
fsmithredFetching salsa13:58
fsmithred'13:58
rrqthat looks good13:58
fsmithredI'm lost13:59
rrquse: git log --oneline --all --graph13:59
fsmithredis debian/master the same as debian/master?13:59
fsmithredor are they different?13:59
rrqcheck with: git log --oneline --all --graph14:00
fsmithredyeah, I'm looking at that14:00
rrqit'll tell where in the total workspace history those branch heads are14:00
rrqit's origin/debian/master vs salsa/debian/master14:01
rrqthe origin one should be on the trail of the salsa one14:01
rrqunless you have changed it (the origin one)14:02
rrqcommit af1fc20 is head of origin/debian/master)14:03
fsmithredwhat does that mean?14:03
rrq"commit af1fc20" is that particular version in the history, and that is where the branch origin/debian/master is (or was when I cloned some moments ago)14:05
fsmithredok, so I know where it is14:05
rrqideally that commit is also in the history of the salsa/debian/master branch14:05
fsmithredbut I dont' know what it is14:05
fsmithredthere's a debian/master on salsa and a debian/master on gdo. Can they be identical?14:06
fsmithredis that a foolish request>?14:06
rrqI hoped that origin/debian/master (on gdo) corrspnds to the tail of salsa/debian/master14:07
rrqi.e. the origin one was cloned from the salsa one some time ago14:07
rrqbut salsa may have had changes14:08
fsmithredlol14:08
rrqwhils origin shouldn't14:08
fsmithredI don't think so14:08
fsmithredyeah, but why can't I just set origin to pull from salsa and get updated with any changes?14:08
rrqwith "git log .." what's the commit labelled salsa/debian/master14:09
fsmithredthen I won't get messages from git about having a different name14:09
fsmithredcommit af1fc20fb51896041c182528f2d9acad680a8da1 (HEAD -> salsa, salsa/debian/master, origin/debian/master, origin/HEAD, debian/debian/master, debian/master)14:09
rrqright; good; so that's the same commit af1fc20....14:10
rrqso now you can delete the origin/debian/master branch14:10
rrqthat does not delete those commits14:10
rrqit deletes "the branch pointer"14:11
rrqmake it no longer existent14:11
fsmithredand then I'll only have a salsa branch?14:11
rrqyes14:11
fsmithredwhy do I want that?14:11
rrqand only a fond, personal memory of the origin/debian/master branch14:12
rrqit doesn't need any such branch pointer in origin14:12
rrqbecause you wouldn't want origin changes to it separate from salsa's changes14:13
rrqless confusion14:13
rrq(if that's possible with git)14:13
fsmithredis there an advantage to having different names between what's on salsa.debian.org and what's on git.devuan.org?14:15
rrqmmm only if you want to track branch changes in that way14:17
fsmithredto me it makes sense that whatever I have that tracks the repo on salsa.debian.org should have the same name14:17
fsmithredI can remeber that debian/master branch is the same as debian/master14:18
rrqmm  isn't it a matter of keeping the tung in the right mouth?14:19
fsmithred?14:19
rrqnote that a branch "origin/debian/master" is a pointer into the pool of commits, and so is "salsa/debian/master"14:19
rrqif the remote salsa changes its "salsa/debian/master" then they two will point at different commits14:20
rrqand the gdo maintainer would need to update so as to move origin/debian/master accordingly14:21
rrqbasically I would delete origin/debian/master14:22
rrqand only keep "salsa/debian/master" since that's the "owner" of that branch14:22
rrqlikewise for the other "duplicated" branch names14:23
rrqleaving only suites/unstable as special for origin14:23
fsmithredthere's no suites/unstable14:24
rrqthere's an origin/suites/unstable isn't there?14:24
fsmithred$ git branch14:25
fsmithred  debian/master14:25
fsmithred* salsa14:25
rrqgit branch -r14:25
rrq(it's not your current branch)14:25
fsmithred debian/debian/master14:25
fsmithred  debian/pristine-tar14:25
fsmithred  debian/upstream/latest14:25
fsmithred  origin/HEAD -> origin/debian/master14:25
fsmithred  origin/debian/master14:25
fsmithred  origin/pristine-tar14:25
fsmithred  origin/upstream/latest14:25
fsmithred  salsa/debian/master14:25
fsmithred  salsa/pristine-tar14:25
fsmithred  salsa/upstream/latest14:25
rrqnice :) lots of confusion to welter in14:26
fsmithredI thought we were in pm14:27
rrqthus, there are 3 remotes: debina, origin and salsa14:27
fsmithredso what do I need to do?14:29

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!