Bug#683400: freeze-exception for live-debconfig
On 08/01/2012 04:36 PM, Philipp Kern wrote: What do you expect us to do ftp-masters told me to ask the release-team to tell ftp-master that they are allowed to process my package and (accept or reject) it for unstable, or not. i suggest you either give them the permission to do so, or not (which would be kind of weird, but anyway). -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683400: freeze-exception for live-debconfig
On Thu, Aug 02, 2012 at 08:10:39PM +0200, Daniel Baumann wrote: On 08/01/2012 04:36 PM, Philipp Kern wrote: What do you expect us to do ftp-masters told me to ask the release-team to tell ftp-master that they are allowed to process my package and (accept or reject) it for unstable, or not. i suggest you either give them the permission to do so, or not (which would be kind of weird, but anyway). Thanks for not giving any further information. I'll still try to get one (hopefully last) constructive message out. I think the situation is this: If this is not intended for wheezy and if other -live components will not use or rely on it, that's ok. However, if so, we'd like to ask you to focus on the current set of -live issues so that you're ready in time. If not, it's highly unlikely that we'll accept a package split at this point, unless being presented with very good reasons. (So far I see none except pointers to communication unavailable to us.) We want -live stuff to be able to propagate through unstable, not t-p-u in any case. That said, it seems that communication with you is very hard, given your uncooperativeness. We're also wary in which state -live is in given [1] and your reply[2]. I guess somebody of the team has to sit down and evaluate how useful -live is at this point given that we're in freeze already. We might not be willing to block the release until you have all the foundation in place, which should already have been happened by now. Kind regards Philipp Kern [1] 20120801080758.ga28...@gmail.com [2] 50191874.4030...@progress-technologies.net signature.asc Description: Digital signature
Bug#683400: freeze-exception for live-debconfig
On 08/02/2012 08:32 PM, Philipp Kern wrote: Thanks for not giving any further information. let me re-iterate: ftp-master told me to do ask the release-team to give permission to ftp-master to process the package in NEW for unstable. that's excately what i did. wouldn't it make sense that ftp-masters and release-team do talk to each other if the one or other team needs more information for this, instead of having me in between? there's nothing that i can do about it on either side/team anyway. If this is not intended for wheezy and if other -live components will not use or rely on it, that's ok. it is intended for wheezy, but other live-* packages can make use of it, but do not rely on it. lxc on the other hand relies on it. That said, it seems that communication with you is very hard, given your uncooperativeness. 'uncooperativeness'? please elaborate. We're also wary in which state -live is in given [1] and your reply[2]. live-installer requires working d-i, d-i currently is still too fragile. but as said, we'll get there in time. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683400: freeze-exception for live-debconfig
tag 683400 + moreinfo thanks On Thu, Aug 02, 2012 at 09:14:54PM +0200, Daniel Baumann wrote: On 08/02/2012 08:32 PM, Philipp Kern wrote: Thanks for not giving any further information. let me re-iterate: ftp-master told me to do ask the release-team to give permission to ftp-master to process the package in NEW for unstable. that's excately what i did. wouldn't it make sense that ftp-masters and release-team do talk to each other if the one or other team needs more information for this, instead of having me in between? there's nothing that i can do about it on either side/team anyway. They were in Cc, but you seem to be unable to summarize past discussions, too. You also seem to be unable to describe your changes to the existing packages that you want to do except for handwaiving. I don't see how we could handle this request, so I'm tagging it moreinfo now, even if it might as well be closed unless there's more useful input. If this is not intended for wheezy and if other -live components will not use or rely on it, that's ok. it is intended for wheezy, but other live-* packages can make use of it, but do not rely on it. lxc on the other hand relies on it. How would lxc depend on something live-*'ish? And why should we accept a change to lxc that depends on something live-*'ish? So from the point of wheezy I'm inclined to say: doesn't affect it. We're also wary in which state -live is in given [1] and your reply[2]. live-installer requires working d-i, d-i currently is still too fragile. but as said, we'll get there in time. Please elaborate. What timeframe are you assuming? As for uncooperativeness it doesn't help that you ignore half of the mails. Maybe you need everything spelt out instead of blindly assuming that you'd somehow get what questions we're aiming at. Of course I should not assume malice, I guess. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#683400: freeze-exception for live-debconfig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 683400 ftp.debian.org
retitle 683400 please reject live-debconf from NEW
thanks
On 08/02/2012 09:54 PM, Philipp Kern wrote:
They were in Cc, but you seem to be unable to summarize past
discussions, too.
honestly, i'm not sure how/if i can summarize it in public, it was a
private discussion between me, ftp-master, and eventually dam and dpl.
You also seem to be unable to describe your changes to the existing
packages that you want to do except for handwaiving.
i've taken out the standalone preseeding backend stuff from
src:live-config into src:live-debconfig.
I don't see how we could handle this request, so I'm tagging it
moreinfo now, even if it might as well be closed unless there's
more useful input.
ok, let's close it then (or rather, reassign to ftp-masters.. so they
can reject live-debconfig 3 from NEW, and i'll re-upload it as version
4 for jessie, that they then can process without problems anytime soon.
How would lxc depend on something live-*'ish?
for container configuration; the generic name for this was rejected by
ftp-master, bottom line is they think it's live-* stuff (eventhough it
is not), so it needed to use a package name out of the debian-live
namespace.
Please elaborate. What timeframe are you assuming?
we'll be having alpha1 out in a couple of days, so we have a baseline
of what still needs work. i expect one week (plus one week for safety)
until live-{build,boot,config,tools} is good enough for wheezy, and
after that, another week (plus one week for safety) for live-installer
and debian-installer-launcher. that would be somewhen arround end of
august. for live-manual i don't know about Bens plans, but should be
somewhat similar i think.
As for uncooperativeness it doesn't help that you ignore half of
the mails.
i'm not aware to not have answered (or even ignored) any mails send to
this bug report, did i?
Maybe you need everything spelt out instead of blindly assuming
that you'd somehow get what questions we're aiming at.
i appreciate if you formulate questions in a direct, unambiguous and
an easy understandable way, yes.
I should not assume malice, I guess.
i prefer if you don't.
- --
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet: http://people.progress-technologies.net/~daniel.baumann/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAa34AACgkQ+C5cwEsrK55M0gCdFpHpq+wbvYIejYicoe5ip5HH
/hMAniIFMUW4V9xC0MEjCC2sZOFpFVHo
=bBtk
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683400: freeze-exception for live-debconfig
On Tue, Jul 31, 2012 at 03:12:21PM +0200, Daniel Baumann wrote: so.. does the release-team allow ftp-master to process that package? Don't know. There's not much content in here except for a rant and a pointer to a discussion not available to us. What do you expect us to do, given that we cannot even inspect the package in NEW? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#683400: freeze-exception for live-debconfig
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception On 07/31/2012 02:51 PM, Luca Falavigna wrote: I checked with Release Team, and they prefer to have written communication for upload approvals, so they asked if you could send a request to debian-release@lists.d.o anyway. done hereby (not sure if opening a freeze-exception bug is that accurate for this sort of request, but i didn't found anything more suitable, and bts is preferable over plain mails on the list). live-debconfig contains the stand-alone parts from live-config that's needed for 'build-time' configuration of systems, including live systems and lxc systems. it was split out from live-config due to popular demand, see ftp-masters thread for the history why it was in src:live-config in the first place rather than it's own src package (beginning of june). live-debconfig however is in NEW now since some days, and i need to know if ftp-masters will process the package so that it can go to unstable first, and eventually and if RM agrees, go to wheezy. if not, i will need to stuff the contend back into src:live-config. ftp-masters however say, that they need RM consent to even let it to unstable first (which actually confuses me a bit, since other completely new packages, e.g. crtools, were processed just fine and are now in unstable). at debconf, luk said that he agrees to have the package in unstable first, and then go from there and see, if it can go to wheezy at a later point (which is ok, since we'll need a few translation/documentation-update uploads of that package anyway before we consider asking for an unblock). so.. does the release-team allow ftp-master to process that package? unrelated to that, but similar: we'll intend to upload another new package, live-examples, that will carry the configuration trees for live-build for the official debian-live images for wheezy (see e.g. http://live.debian.net/gitweb/?p=config-gnome-desktop.git). do you need/want a seperate request for that too in order to allow ftp-masters to process the package (in advance, or afterwards?), or should i just upload the package normally? -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
