Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
Could you PLEASE stop posting to debian-ports@? You are sending these mails to
every Debian Ports architecture mailing list.
I already asked for the third time now.
Thank You,
Adrian
> On May 26, 2019, at 5:34 AM, wrote:
>
> Sorry if this is off-topic, but I can't help asking if that "15381 March
> 1977" was on purpose or just from some wonky email client: 15380 days after
> March 1st 1977 happens to be April 10th 2019, so...
>
> --
> Pengcheng Xu
> https://jsteward.moe/
>
>
>> -Original Message-
>> From: Aurelien Jarno
>> Sent: Saturday, May 25, 2019 4:56 PM
>> To: debian-h...@lists.debian.org; debian-...@lists.debian.org; debian-
>> de...@lists.debian.org; debian-po...@lists.debian.org; ftpmaster@ports-
>> master.debian.org
>> Subject: Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
>>
>> Hi,
>>
>>> On 2019-04-24 12:34, Joerg Jaspert wrote:
>>> On 15381 March 1977, Aurelien Jarno wrote:
> ^^^ HERE
>>>
>>>>>> It would be nice to have a bit more than 2 weeks to do all of that.
>>>>> Ok. How much? Is 6 or 8 weeks better? I don't think, given how
>>>>> long this is on the table already, it doesn't make much difference if its
>>>>> 2
>> or 8.
>>>>> Just something thats clear defined and not some random, non-clear
>>>>> "sometime in the future" point.
>>>> The hurd-i386 architecture has been moved to to debian-ports yesterday.
>>>> I hope it shows the willingness to do that. Please give us at least
>>>> 4 more weeks to do the remaining kfreebsd-*. That will provide some
>>>> margin to account for the non-infinite free time to work on that
>>>> (especially in the freeze period) and possibly to get more disk
>>>> space for the debian-ports machine.
>>>
>>> Thats ok, end of May is a nice point to take.
>>>
>>> Thanks for the work and the timeframe for the rest!
>>
>> kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports.
>> As
>> hurd-i386 has been moved earlier, it means that all the 3 architectures have
>> now been moved.
>>
>> Aurelien
>>
>> --
>> Aurelien Jarno GPG: 4096R/1DDD8C9B
>> aurel...@aurel32.net http://www.aurel32.net
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 15413 March 1977, Aurelien Jarno wrote: Thats ok, end of May is a nice point to take. Thanks for the work and the timeframe for the rest! kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As hurd-i386 has been moved earlier, it means that all the 3 architectures have now been moved. Thank you! -- bye, Joerg
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 2019-05-25 13:00, Manuel A. Fernandez Montecelo wrote: > Hi, > > Em sáb, 25 de mai de 2019 às 10:57, Aurelien Jarno > escreveu: > > > > kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As > > hurd-i386 has been moved earlier, it means that all the 3 architectures > > have now been moved. > > Nice :-) > > Not sure who's the admin (I couldn't find the admin address in the > main pages), but they're not registered in the graphs (while > powerpcpse, recently removed, still is). > > https://buildd.debian.org/stats/graph-ports-week-big.png There are still available on the on the main graph: https://buildd.debian.org/stats/graph-week-big.png I'll move hurd and kbsd-* plots from the main one to the ports one, but unless we do not keep the history, it's not a trivial task as it requires migrating the data from one text database to the other database. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
Hi, Em sáb, 25 de mai de 2019 às 10:57, Aurelien Jarno escreveu: > > kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As > hurd-i386 has been moved earlier, it means that all the 3 architectures > have now been moved. Nice :-) Not sure who's the admin (I couldn't find the admin address in the main pages), but they're not registered in the graphs (while powerpcpse, recently removed, still is). https://buildd.debian.org/stats/graph-ports-week-big.png -- Manuel A. Fernandez Montecelo
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
Hi, On 2019-04-24 12:34, Joerg Jaspert wrote: > On 15381 March 1977, Aurelien Jarno wrote: > > > > > It would be nice to have a bit more than 2 weeks to do all of that. > > > Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this > > > is on the table already, it doesn't make much difference if its 2 or 8. > > > Just something thats clear defined and not some random, non-clear > > > "sometime in the future" point. > > The hurd-i386 architecture has been moved to to debian-ports yesterday. > > I hope it shows the willingness to do that. Please give us at least 4 > > more weeks to do the remaining kfreebsd-*. That will provide some margin > > to account for the non-infinite free time to work on that (especially in > > the freeze period) and possibly to get more disk space for the > > debian-ports machine. > > Thats ok, end of May is a nice point to take. > > Thanks for the work and the timeframe for the rest! kfreebsd-amd64 and kfreebsd-i386 have now been moved to debian-ports. As hurd-i386 has been moved earlier, it means that all the 3 architectures have now been moved. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 15381 March 1977, Aurelien Jarno wrote: > It would be nice to have a bit more than 2 weeks to do all of that. Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this is on the table already, it doesn't make much difference if its 2 or 8. Just something thats clear defined and not some random, non-clear "sometime in the future" point. The hurd-i386 architecture has been moved to to debian-ports yesterday. I hope it shows the willingness to do that. Please give us at least 4 more weeks to do the remaining kfreebsd-*. That will provide some margin to account for the non-infinite free time to work on that (especially in the freeze period) and possibly to get more disk space for the debian-ports machine. Thats ok, end of May is a nice point to take. Thanks for the work and the timeframe for the rest! -- bye, Joerg
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 2019-04-13 17:01, Joerg Jaspert wrote: > On 15371 March 1977, Aurelien Jarno wrote: > > > > How is the move to debian-ports supposed to happen? I won't have the > > > time to do anything about it within the 2 weeks. > > > The process to inject all packages to debian-ports is to get all the > > deb, udeb and buildinfo files from the archives (main and debug) and > > associate them with the .changes files that are hosted on coccia. We'll > > also need to fetch all the associated GPG keys used to sign the changes > > files. Then we can inject that in the debian-ports archive. > > > It would be nice to have a bit more than 2 weeks to do all of that. > > Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this > is on the table already, it doesn't make much difference if its 2 or 8. > Just something thats clear defined and not some random, non-clear > "sometime in the future" point. The hurd-i386 architecture has been moved to to debian-ports yesterday. I hope it shows the willingness to do that. Please give us at least 4 more weeks to do the remaining kfreebsd-*. That will provide some margin to account for the non-infinite free time to work on that (especially in the freeze period) and possibly to get more disk space for the debian-ports machine. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 13.04.19 17:01, Joerg Jaspert wrote: > On 15371 March 1977, Aurelien Jarno wrote: > >>> How is the move to debian-ports supposed to happen? I won't have the >>> time to do anything about it within the 2 weeks. > >> The process to inject all packages to debian-ports is to get all the >> deb, udeb and buildinfo files from the archives (main and debug) and >> associate them with the .changes files that are hosted on coccia. We'll >> also need to fetch all the associated GPG keys used to sign the changes >> files. Then we can inject that in the debian-ports archive. > >> It would be nice to have a bit more than 2 weeks to do all of that. > > Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this > is on the table already, it doesn't make much difference if its 2 or 8. > Just something thats clear defined and not some random, non-clear > "sometime in the future" point. well, please go back in history to see the same short notice for the hppa removal, and then do the exercise how long it took to integrate that architecture on debian-ports. >
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 15371 March 1977, Aurelien Jarno wrote: How is the move to debian-ports supposed to happen? I won't have the time to do anything about it within the 2 weeks. The process to inject all packages to debian-ports is to get all the deb, udeb and buildinfo files from the archives (main and debug) and associate them with the .changes files that are hosted on coccia. We'll also need to fetch all the associated GPG keys used to sign the changes files. Then we can inject that in the debian-ports archive. It would be nice to have a bit more than 2 weeks to do all of that. Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this is on the table already, it doesn't make much difference if its 2 or 8. Just something thats clear defined and not some random, non-clear "sometime in the future" point. -- bye, Joerg
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 4/13/2019 12:49 PM, Aurelien Jarno wrote: > The process to inject all packages to debian-ports is to get all the > deb, udeb and buildinfo files from the archives (main and debug) and > associate them with the .changes files that are hosted on coccia. We'll > also need to fetch all the associated GPG keys used to sign the changes > files. Then we can inject that in the debian-ports archive. I'm curious how the GPG bit works given that there is no guarantee that the signature can be validated at any other point in time than ingestion on ftp-master - especially considering the rotation/expiry of subkeys and buildd keys. In this case the files already come from a trusted source and should be ingested as-is, I guess? (Not that I particularly like the fact that it's only a point in time validation.) Kind regards Philipp Kern
Re: Hurd-i386 and kfreebsd-{i386,amd64} removal
On 2019-04-12 23:01, Samuel Thibault wrote: > Hello, > > Joerg Jaspert, le ven. 12 avril 2019 22:48:42 +0200, a ecrit: > > back in August 2018 we discussed architecture inclusion into > > unstable/experimental. > > > > Today we had our regular FTPMaster meeting and discussed hurd and both > > kfreebsd architecture and decided to remove them from unstable and > > experimental 2 weeks from now. > > Just before the Buster release? That's far from the easiest timing. > > I was hoping to do a non-official relase of Debian Hurd along Buster as > usual, but a change of archive, which means uploading packages, fixing > scripts, etc. will take a lot of time, which I simply just will not have > within the coming two-three months (I am already struggling to find time > to do what I engaged to). Basically, it means no non-official release of > Debian Hurd along Buster. Or at best I could just make that non-official > release now, with all the still pending RC bugs. > > How is the move to debian-ports supposed to happen? I won't have the > time to do anything about it within the 2 weeks. The process to inject all packages to debian-ports is to get all the deb, udeb and buildinfo files from the archives (main and debug) and associate them with the .changes files that are hosted on coccia. We'll also need to fetch all the associated GPG keys used to sign the changes files. Then we can inject that in the debian-ports archive. It would be nice to have a bit more than 2 weeks to do all of that. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
