IRC log for #gnu-kbsd on 20080815

05:22.30*** join/#gnu-kbsd tarzeau_ (n=gurkan@bee.ethz.ch)
05:23.42NCommanderhey tarzeau_
07:46.21*** join/#gnu-kbsd kaeso (n=luca@debian/developer/kaeso)
09:05.33tarzeau_aurel32: ok
09:40.37tarzeau_NCommander: now what?
09:41.13NCommandertarzeau_, well, I imported the snapshot into dak, now I need to hack up wanna-build to properly handle setting binNMU status when reading in from quinn-diff
09:41.50NCommanderI already figured out how w-b does binNMU internally, I just need to write the code and properly test it :-)
09:42.56tarzeaugreat
09:59.45NCommanderIt's sad that you seem the only one really enthusastic about a kfreebsd release :-P
13:35.58*** join/#gnu-kbsd NCommander (n=mcasadev@cpe-69-207-147-100.rochester.res.rr.com)
14:35.46*** join/#gnu-kbsd otavio (n=otavio@debian/developer/otavio)
14:41.30aurel32NCommander: I have just got a discussion about dak with Ganneff
14:41.46aurel32I send me the scripts used by amd64 when it was not included in the main archive
14:41.55NCommander??
14:42.03NCommander(I fixed import-archive which is how I got everything working)
14:42.18NCommanderso if you want to migrate from mini-dak to dak, its possible
14:42.31aurel32there should be enough to sync the testing/unstable/experimental from the official archive
14:42.36aurel32http://amd64.debian.net/~joerg/scripts/
14:42.53aurel32there is no need to develop new scripts
14:43.16NCommanderOooh, I love him now
14:43.17aurel32yes, that's my plan to switch to dak, but probably not before a few eeks
14:43.18aurel32weeks
14:43.35aurel32the problem is to make sure we do not lose any features
14:43.43NCommanderI can give you my patch code to get import archive working
14:44.06aurel32why not, yes, but dak is not yet install on debian-ports.org
14:44.36NCommanderwell, I want to get it in the offical dak archive
14:44.43NCommanderBut I have someone of an allegeric reaction to git
14:44.46aurel32do you know if we can do something such as "unreleased" with dak ?
14:44.49NCommanderYeah
14:44.59NCommanderWell
14:45.00aurel32because that's really something we need
14:45.07NCommanderWait, you'll have to explain unreleased more to me
14:45.24NCommanderdak requires some internal consistantly, it would reject binaries that don't match the source version
14:45.38aurel32unreleased is a special suite to put packages that we are patching
14:45.43NCommanderRight, this I know
14:45.49NCommanderBut how does it vary from a normal suite
14:45.55aurel32so it need to handle the source + binary
14:46.07NCommanderWHy not simply have unreleased for each architecture
14:46.09aurel32so it means we can have different source for each architecture
14:46.16NCommanderunreleased-hurd-i386/unreleased-kfreebsd-*
14:46.25tarzeauwhere can i donwload the d-i gnu/kfreebsd cd?
14:46.35NCommandertarzeau, d-i doesn't exist for kfreebsd yet
14:46.38tarzeaubut...
14:46.42NCommander(I've just gotten into playing with its configuration scripts)
14:46.51NCommanderThe current installer is based off the freebsd installer
14:47.25NCommander(from what I can gather, its sorta a rather nasty hack to hook the configure part of install packages working)
14:47.25aurel32NCommander: well seems to looks ok, but that would mean one more change to /etc/apt/sources.list
14:47.33aurel32and I would try to avoid that
14:48.01NCommanderaurel32, ah, use a unionfs mount to join all the unreleased pools into one
14:48.02NCommander;-)
14:48.18aurel32the problem is not the pool
14:48.23aurel32is the Packages.gz
14:48.33NCommanderoh
14:48.34NCommanderright
14:48.35NCommanderd'ho
14:48.38NCommander... *d'oh
14:48.54NCommanderWell, internally, dak just uses apt-ftparchive with filelists to generate packages.gz
14:49.23NCommanderIt probably won't be that hard to mange dak make-suite-file-lists to do what you need it to do
14:49.41aurel32I'll have a closer look in the next weeks
14:49.56aurel32I will travel a lot in the next days/weeks
14:49.58NCommanderBe warned. Abandon all documentation for all those entire here ;-)
14:50.12aurel32so I won't have that much time
14:50.24NCommanderI can answer dak questions, I've done two installations
14:50.31NCommander(one on my laptop, and one on my ftp-master)
14:51.15NCommanderwhy the desire to replace mini-dak with dak?
14:51.38aurel32because it seems m68k will need it
14:51.59aurel32given all what you said about lenny sync
14:52.07NCommander*nods*
14:52.12NCommanderWell, dak isn't that picky about the pool
14:52.23NCommanderYou could get mini-dak and dak to co-exist without too many issues as long as they each managed seperate repos
14:52.35NCommander(have mini-dak handle unreleased, and dak handle u/t/s/os)
14:52.45aurel32that would be really to complicated
14:52.53aurel32that means two incoing queues and so on
14:52.57NCommanderyeah
14:53.58NCommanderwell, to mimic the current setup, mirror-split will have to be done for the pool
14:53.59NCommanderThat's easy
14:54.28NCommanderUnreleased, hrm
14:55.02NCommandereach architecture uses different source versions in unreleased I take it?
14:56.13NCommander(out of curosity, how is disk space looking on d-ports? I heard it was kinda full)
15:03.51aurel32yes
15:04.06NCommanderEw.
15:04.30aurel32at some point it was full, yes, but now we have changed the machine
15:04.42aurel32so we have still 200GB free
15:04.44NCommanderI dunno if you follow d-devel
15:04.49NCommanderWe just got our two weeks notice :-)
15:04.51aurel32not really those days
15:05.14NCommanderAh
15:05.24NCommanderSo you know we're being removed from the mirror
15:05.31NCommander(I posted a nice long rant about it but meh :-P
15:05.36aurel32well one other features of unreleased, is that a package upload with a higher version in unstable automatically remove the package from unreleased
15:05.45aurel32yes I know about that
15:06.05NCommanderso dak is going to need some extending to meet all the requirements of mini-dak
15:06.08guillemaurel32: snapshot used to take a lot of the space on gnuab most of the time
15:06.57guillemand obsolete as well, don't remember if that's being purged automatically now though
15:07.00NCommanderWell, I just want to make sure mini-dak isn't suitable for our needs. While I would perfer dak, simply because that's what the ftp-masters us, it may still be realistic to stay with mini-dak
15:07.40NCommanderdoesn't want to affect the kfreebsd/hurd ports any more than necessary
15:07.53NCommanderAlthough I'm making good progress on the kfreebsd lenny release work ;-)
15:09.15aurel32guillem: no, that's not purged, but we have 500GB of disk in total
15:09.49guillemok, just mentioning as that was what took most of the archive size
15:09.50aurel32NCommander: have you got a look at the link I just posted about Ganneff scripts?
15:10.11aurel32it seems there is already everything to sync testing
15:10.25NCommanderIt's more for syncing unstable
15:10.39NCommanderIt would require a britney installation
15:10.50aurel32well it told me that amd64 used those scripts to sync testing + unstable + experimental
15:11.02NCommanderIt could be used to sync the source for testing
15:11.23NCommanderThat would work (it probably needs a slight tweak, this looks like the really old dinstall based dak, not the current iteration)
15:11.23aurel32but then if you have the package with the same version in unstable that's ok
15:11.48aurel32yes, it's for an old version of dak, so this may need some tweaks, but that's a good basis I think
15:11.50NCommanderI've been working to modify w-b to binNMU in distirbution == testing
15:12.06NCommander(for reasons guillem brought up earlier)
15:12.11aurel32why do you want that?
15:12.37aurel32why can't you fetch the packages from unstable directly?
15:12.43NCommanderif we're missing a binary revision of a package, and it has to be built, either it has to be built as is, and then the changes file must be changed to get it to enter testing
15:12.51aurel32just using a build daemon for the missing packages
15:13.01NCommanderYeah, I know that :-P
15:13.15NCommanderBut the missing versions will go into unstable if the changes file isn't tweaked
15:13.31aurel32I still I don't see why
15:13.38NCommanderAnd as an older version did exist, but is now being built in a new environment, by definition, its a binNMU
15:13.40aurel32we already have testing buildds in debian
15:13.49NCommanderfor t-p-u
15:13.51aurel32and the uploads are going into the right queue
15:13.53NCommanderNot the actual testing suite
15:14.07aurel32t-p-u could be used for that actually
15:14.24NCommanderstill have the issue of butchering the changes file
15:14.30aurel32I have to admit I don't follow you
15:14.32NCommanderALthough thats less of an issue
15:14.38NCommanderguillem managed to explain it well
15:14.44NCommanderI guess I'm not good at repeating his words
15:15.33guillemaurel32: the problem is that most probably at some point we had a version present in the archive in sid
15:15.36aurel32do you have a pointer to that? There is such a huge backlog
15:15.39guillemand then it got obsoleted
15:15.55guillemaurel32: so rebuilding with the same name-version-arch tuple would be wrong
15:16.16guillemand for the packages that are out of syn between testing and sid, the cleanest is to binNMU
15:16.37guillembut I said, the best would be to try to fish them from snapshot and obsolete first
15:16.40aurel32Well but that only applies when we add support for testing
15:16.46guillemand only as a last resort binNMU the missing stuff
15:16.51aurel32when the script runs every day that won't happen
15:17.02guillemsure, I was only talking about the initial import
15:17.06aurel32so I am not sure it worth developping a complicated stuff for that
15:17.21aurel32it's a lot simpler to fetch the package from obsolete
15:17.35aurel32that will cover 98% of the cases
15:17.44guillemaurel32: sure, that's what I proposed
15:17.49aurel32and the other 2 % can be handled by hand
15:18.07guillemsid + (snapshot + obsolete) + possible binNMU for the missing stuff
15:18.08NCommanderaurel32, the script doesn't handle syncing binaries
15:18.19NCommanderand yeah, that's what I did
15:18.27NCommander(I imported a snapshot as the basis)
15:19.08aurel32NCommander: you mean it can't automatically move (or rather copy) binaries from unstable to testing when the source package make the same?
15:19.34NCommanderdak has no concept of testing or releasing
15:19.38NCommanderThat's all handled by britney
15:19.49NCommanderAnd that's done by freezing the archive and all the binaries in it
15:19.55NCommander^testing
15:20.08NCommanderSo in effect, nothing ever has to be built since nothing can enter testing if there is a gap so to speak
15:21.06aurel32well I am sure the amd64 were able to handle that nicely
15:21.30aurel32you have to ask for example ganneff about that, I am not sure it worth reinventing the wheel
15:21.37aurel32NCommander: speaking about dak:
15:22.02aurel32- it is able to automatically remove package from a suite when a newer version appears in another (for unreleased)
15:22.21aurel32- is it able to keep obsoleted packages like mini-dak ?
15:22.40NCommanderIt supports rejecting packages if something is newer/older than
15:22.50NCommanderIf it doesn't
15:22.58NCommanderextending dak won't be very hard since the basic support is there
15:23.13NCommander(I can't say for sure if it does or doesn't, mostly cause dak doesn't come with a manual)
15:23.25aurel32well it's not about rejecting packages
15:23.36aurel32it's about automatically removing packages
15:23.51NCommander"  cruft-report    Check for obsolete or duplicated packages"
15:23.55aurel32and that's really a showstopper for the switch to dak if it doesn't handle that
15:24.11NCommander"  clean-suites     remove cruft from the archive"
15:24.16NCommanderOff hand
15:24.19NCommanderI'd say yes it does
15:25.28NCommanderYou simply mark unreleased must be newer then stable
15:25.37NCommanderand then cruft-report/clean-queues/clean-suite should do what you want)
15:26.41aurel32what about removed packages? Are they deleted or simply moved somewhere?
15:28.39NCommanderlooks at the source
15:28.43NCommanderOh, dak rm?
15:28.46NCommanderUh
15:35.56aurel32I mean for automatically removed packages
15:36.08aurel32so probably for clean-suites
15:36.28NCommanderyeah
15:36.32NCommanderIt looks like it gets moved aside
15:36.34NCommander(not sure)
15:36.40NCommanderIf not, its easy to change the default ;-)
15:36.50azeemthere's the morgue, no?
15:37.47NCommanderyeah
15:37.50NCommanderTHat's where it should go
15:38.13NCommanderBah, I forgot to add arch all packages when I imported the database
15:38.14NCommanderBah
15:38.18NCommanderfixes his dak installation
15:39.51NCommanderaurel32, how/when could we possibly move unstable to d-ports? (sorta the pressing concern, and it should be easy with mini-dak)
15:40.07NCommander(I can help in any way possible)
15:40.59azeemdoes it make sense to move first to mini-dak, and then migrate to dak?
15:41.54NCommanderfor unstable, it doesn't really matter
15:41.58NCommanderEverything has to get imported anyway
15:42.03NCommanderand if I understand mini-dak right
15:42.16NCommanderAdding our unstable is a change in archive.conf, making the dirs, rsync, and then apt-ftparchive
15:42.17NCommanderIn that order
15:42.41NCommander(not counting moving the buildd's w-b)
15:43.13aurel32azeem: for hurd, that's ok to switch to mini-dak first, as it only has unstable/experimental
15:43.39aurel32azeem: and as we anyway have to import kfreebsd and hurd/unreleased, adding one more thing to import won't be difficult
15:43.42azeemaurel32: did you consider starting a discussion about ports.debian.org?
15:44.13aurel32NCommander: well w-b is already setup for a long time
15:44.23aurel32NCommander: I mean for m68k, I have been asked to add it
15:44.34aurel32NCommander: about the date, probably not before two weeks
15:44.36NCommanderYeah, that end is already covered :-)
15:44.40aurel32basically when I get back home
15:44.44NCommanderPerfect
15:44.54azeemI think Ganneff should be able to handle w-b access now?  If he is cooperative, it might make more sense for some bargain where we have a second dak on ports.debian.org, but keep/migrate back w-b on buildd.d.o
15:45.23aurel32azeem: you mean getting the the domain name?
15:45.25azeemhrm, on second thought, w-b access is probably done by a different set of people
15:45.38azeemaurel32: integrating it better into Debian, yes
15:45.40aurel32azeem: not sure he will be very cooperative when it concerns hurd and m68k
15:46.00aurel32azeem: yes, you can start such a discussion
15:46.18aurel32just keep in mind that ports.debian.org already exists
15:46.20NCommanderazeem, w-b is a different group
15:46.35NCommanderknows this from the head smacking experience we've gone through trying to get keys added
15:46.37aurel32it's a web page listing all the architecures in debian
15:46.38NCommanderTHere is some overlap though
15:46.44NCommanderOh, THAT ports.d.o
15:46.51NCommanderI thought it was d.o/ports
15:46.52azeemaurel32: it's just a redirect
15:47.06aurel32well concerning w-b, it's always better to have w-b and the archive on the same machine
15:47.16azeemnods
15:47.19NCommanderconsidering that page still has netbsd-* on it ...
15:47.20aurel32or machines in the same location
15:47.29azeemI'm mostly concerned about RM binNMUs
15:47.42azeemthat's something at least the Hurd port is sorely lacking currently
15:47.52NCommanderazeem, binNMU broken on Hurd?
15:47.53aurel32azeem: you mean the rght to do binNMU ?
15:48.17NCommanderazeem, if you have access to the w-b database, you can binNMU any package
15:48.27azeemaurel32: no, just getting all-ports binNMUs executed for hurd etc. as well
15:48.30NCommanderWe've binNMUed a few of our own packages
15:48.34NCommanderoh, those
15:48.35aurel32azeem: I see
15:48.43azeemNCommander: pfew, I thought that's what I did all the time, thanks for reassuring me
15:48.53aurel32azeem: one on the solution I am currently working on, is a mostly automated process
15:49.12aurel32azeem: it is possible to detect the transitions
15:49.45aurel32and I have even been to detect transitions unknown from the RM team
15:50.15aurel32but we can also give an account to the RM on debian-ports.org
15:50.16azeemaurel32: ok, but that's orthogonal
15:50.29aurel32in the hope that they will use it
15:50.42aurel32azeem: well I believe that something that can even benefit debian
15:50.46azeemI don't think there's a publically available place where all the buildd.d.o binNMUs are added in a RSS fashion?
15:51.12aurel32I mean the RM are spending a lot of time on transistions, while some parts can be automated
15:51.32aurel32azeem: some persons who are doing the binNMU sometimes have a file with a list
15:51.38aurel32vorlon for example
15:51.45aurel32but I am not sure it is the cas of all persons
15:52.11azeemyeah, but it's several files, and no time stamps
15:52.13aurel32also sometimes, it's not just a matter of reproducing the same binNMU
15:52.13azeemHE has one
15:52.26aurel32a lot of binNMUs have to be computed
15:52.31aurel32thinking for example of the perl transition
15:52.36aurel32or the python one
15:52.49aurel32sorry, but I have to go to Lunch now
15:52.49azeemright
15:52.52aurel32see you later
15:52.53azeemsee you
15:53.08azeemstill, having the information centrally available would be nice
16:45.11*** join/#gnu-kbsd uwe_ (n=uwe@dslb-084-056-006-076.pools.arcor-ip.net)
17:05.54*** join/#gnu-kbsd appaji (n=appaji@unaffiliated/appaji)
17:10.33*** join/#gnu-kbsd kaeso (n=luca@debian/developer/kaeso)
17:20.30*** join/#gnu-kbsd CIA-2 (n=CIA@208.69.182.149)
17:39.40*** join/#gnu-kbsd CIA-2 (n=CIA@208.69.182.149)
19:00.53*** join/#gnu-kbsd appaji (i=appaji@gateway/tor/x-2887cffef7d51407)
22:22.20*** join/#gnu-kbsd aurel32 (n=aurel32@hall.aurel32.net)
22:22.56*** join/#gnu-kbsd aurel32 (n=aurel32@hall.aurel32.net)
22:24.30*** join/#gnu-kbsd aurel32 (n=aurel32@hall.aurel32.net)
22:30.16*** join/#gnu-kbsd aurel32 (n=aurel32@hall.aurel32.net)
22:32.27*** join/#gnu-kbsd aurel32 (n=aurel32@hall.aurel32.net)
22:33.33*** join/#gnu-kbsd aurel32 (n=aurel32@hall.aurel32.net)
23:19.24*** join/#gnu-kbsd m00bie (n=chatzill@cpc1-bsfd3-0-0-cust305.cmbg.cable.ntl.com)
23:33.24*** join/#gnu-kbsd asac_ (n=asac@e177164237.adsl.alicedsl.de)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.