Bug#1014815: kiwipy initial packaging
I'm currently busy and don't have time to package kiwipy so I change the package status to RFS -- Guilherme de Paula Xavier Segundo GPG: 4096R/976B8AC9 GPG Fingerprint: 1808D92674863C2E07B7B08C1B140644976B8AC9
Bug#1014815: kiwipy initial packaging
Am 15.10.22 um 19:06 schrieb Bastian Germann: any news on downgrading aio-pika? Forget, just saw 8.0 being released which should have this fixed. So no need to downgrade.
Bug#1014815: kiwipy initial packaging
Hi Guilherme, any news on downgrading aio-pika? Thanks, Bastian
Bug#1014815: kiwipy initial packaging
Hi Bastian, I did check the correct package dependencies. I believe that if you had researched I sent the aio-pika package on 03/08/2022 (https://tracker.debian.org/news/1351353/accepted-python-aio-pika-803-1-source-all- into-unstable-unstable/) and the kiwipy package upstream entered the package's dependency version information in the develop branch on 5/8/2022 (https://github.com/aiidateam/kiwipy/commit/7750921d7f69f55005a9f69a854f5e0d1a16feb0). Best, Guilherme Em qui., 6 de out. de 2022 às 19:04, Eriberto escreveu: > > Em qui., 6 de out. de 2022 às 18:45, Bastian Germann > escreveu: > > > > Am 06.10.22 um 20:19 schrieb Eriberto Mota: > > > Am 05.10.22 um 14:59 schrieb Guilherme Xavier: > > >>> Hi, > > >>> > > >>> Agree, downgrading would be an option. > > >>> I don't know how this can be done, but I'm open to doing it. > > >> > > >> You import the older version as 8.1.1+really6.8.1-1 > > > > > > > > > Nope. Downgrading is a workaround for new upstream versions full broken, > > > but already sent to Debian. Is dangerous and undesirable to reintroduce > > > an old version of a software to make it "a good dependency". This action > > > may generate critical bugs or introduce security holes. The right way is > > > ask to the upstream to update the software to use the current version of > > > a dependency. In other words, "+really" must be used in very extreme > > > cases only, not for adjustments. > > > > In general, I agree with you. But as far as I can see, Guilherme introduced > > python-aio-pika for the sake of packaging kiwipy and probably has not > > checked > > compatiblity before packaging that. It is not in use by any other package. > > So for me this would be okay. It is in the archive for two months now and > > popcon is at 1. I do not think that upstream will have the issue fixed soon > > and it would be a pity if Guilherme's packaging work (there are some more > > deps > > introduced for kiwipy) would not be fruitful for him in the sense of having > > it > > available in bookworm. > > Ok, this is commendable. However, keeping Debian (as OS) secure is > more important than any effort to package anything. -- Guilherme de Paula Xavier Segundo GPG: 4096R/976B8AC9 GPG Fingerprint: 1808D92674863C2E07B7B08C1B140644976B8AC9
Bug#1014815: kiwipy initial packaging
Em qui., 6 de out. de 2022 às 18:45, Bastian Germann escreveu: > > Am 06.10.22 um 20:19 schrieb Eriberto Mota: > > Am 05.10.22 um 14:59 schrieb Guilherme Xavier: > >>> Hi, > >>> > >>> Agree, downgrading would be an option. > >>> I don't know how this can be done, but I'm open to doing it. > >> > >> You import the older version as 8.1.1+really6.8.1-1 > > > > > > Nope. Downgrading is a workaround for new upstream versions full broken, > > but already sent to Debian. Is dangerous and undesirable to reintroduce > > an old version of a software to make it "a good dependency". This action > > may generate critical bugs or introduce security holes. The right way is > > ask to the upstream to update the software to use the current version of > > a dependency. In other words, "+really" must be used in very extreme > > cases only, not for adjustments. > > In general, I agree with you. But as far as I can see, Guilherme introduced > python-aio-pika for the sake of packaging kiwipy and probably has not checked > compatiblity before packaging that. It is not in use by any other package. > So for me this would be okay. It is in the archive for two months now and > popcon is at 1. I do not think that upstream will have the issue fixed soon > and it would be a pity if Guilherme's packaging work (there are some more deps > introduced for kiwipy) would not be fruitful for him in the sense of having it > available in bookworm. Ok, this is commendable. However, keeping Debian (as OS) secure is more important than any effort to package anything.
Bug#1014815: kiwipy initial packaging
Am 06.10.22 um 20:19 schrieb Eriberto Mota: Am 05.10.22 um 14:59 schrieb Guilherme Xavier: Hi, Agree, downgrading would be an option. I don't know how this can be done, but I'm open to doing it. You import the older version as 8.1.1+really6.8.1-1 Nope. Downgrading is a workaround for new upstream versions full broken, but already sent to Debian. Is dangerous and undesirable to reintroduce an old version of a software to make it "a good dependency". This action may generate critical bugs or introduce security holes. The right way is ask to the upstream to update the software to use the current version of a dependency. In other words, "+really" must be used in very extreme cases only, not for adjustments. In general, I agree with you. But as far as I can see, Guilherme introduced python-aio-pika for the sake of packaging kiwipy and probably has not checked compatiblity before packaging that. It is not in use by any other package. So for me this would be okay. It is in the archive for two months now and popcon is at 1. I do not think that upstream will have the issue fixed soon and it would be a pity if Guilherme's packaging work (there are some more deps introduced for kiwipy) would not be fruitful for him in the sense of having it available in bookworm.
Bug#1014815: kiwipy initial packaging
Am 05.10.22 um 14:59 schrieb Guilherme Xavier: >> Hi, >> >> Agree, downgrading would be an option. >> I don't know how this can be done, but I'm open to doing it. > > You import the older version as 8.1.1+really6.8.1-1 Nope. Downgrading is a workaround for new upstream versions full broken, but already sent to Debian. Is dangerous and undesirable to reintroduce an old version of a software to make it "a good dependency". This action may generate critical bugs or introduce security holes. The right way is ask to the upstream to update the software to use the current version of a dependency. In other words, "+really" must be used in very extreme cases only, not for adjustments. Eriberto
Bug#1014815: kiwipy initial packaging
Am 05.10.22 um 14:59 schrieb Guilherme Xavier: Hi, Agree, downgrading would be an option. I don't know how this can be done, but I'm open to doing it. You import the older version as 8.1.1+really6.8.1-1 I believe we have no other use of this package apart from kiwipy. Em ter., 4 de out. de 2022 às 15:21, Bastian Germann escreveu: Am 04.10.22 um 20:20 schrieb Guilherme de Paula Xavier Segundo: Yes, I believe it is the best solution. If there is any other suggestion I am available. Another solution would be downgrading. Is the package used by something else in the archive?
Bug#1014815: kiwipy initial packaging
Hi, Agree, downgrading would be an option. I don't know how this can be done, but I'm open to doing it. I believe we have no other use of this package apart from kiwipy. Em ter., 4 de out. de 2022 às 15:21, Bastian Germann escreveu: > > Am 04.10.22 um 20:20 schrieb Guilherme de Paula Xavier Segundo: > > Yes, > > I believe it is the best solution. If there is any other suggestion > > I am available. > > Another solution would be downgrading. Is the package used by something else > in the archive? > -- Guilherme de Paula Xavier Segundo GPG: 4096R/976B8AC9 GPG Fingerprint: 1808D92674863C2E07B7B08C1B140644976B8AC9
Bug#1014815: kiwipy initial packaging
Hi Bastian, I'm working on packaging kiwipy. I've packaged several dependencies on it so far but it currently depends on python-aio-pika <6.8.2 but the version we have on Debian is 8.1.1 On 22/10/04 02:01, Andrius Merkys wrote: > Hi Bastian, > > On 2022-10-04 02:12, Bastian Germann wrote: > > What is the status on kiwipy? > > For some time kiwipy was blocked by pytray, but pytray is in unstable > now. I will revisit kiwipy. > > Best, > Andrius signature.asc Description: PGP signature
Bug#1014815: kiwipy initial packaging
Am 04.10.22 um 19:45 schrieb Guilherme de Paula Xavier Segundo: Hi Bastian, I'm working on packaging kiwipy. I've packaged several dependencies on it so far but it currently depends on python-aio-pika <6.8.2 but the version we have on Debian is 8.1.1 So we should wait until https://github.com/aiidateam/kiwipy/pull/113 has settled? On 22/10/04 02:01, Andrius Merkys wrote: Hi Bastian, On 2022-10-04 02:12, Bastian Germann wrote: What is the status on kiwipy? For some time kiwipy was blocked by pytray, but pytray is in unstable now. I will revisit kiwipy. Best, Andrius
Bug#1014815: kiwipy initial packaging
Am 04.10.22 um 20:20 schrieb Guilherme de Paula Xavier Segundo: Yes, I believe it is the best solution. If there is any other suggestion I am available. Another solution would be downgrading. Is the package used by something else in the archive?
Bug#1014815: kiwipy initial packaging
Yes, I believe it is the best solution. If there is any other suggestion I am available. On 22/10/04 08:02, Bastian Germann wrote: > Am 04.10.22 um 19:45 schrieb Guilherme de Paula Xavier Segundo: > > Hi Bastian, > > > > I'm working on packaging kiwipy. > > I've packaged several dependencies on it so far but it currently depends > > on python-aio-pika <6.8.2 but the version we have on Debian is 8.1.1 > > So we should wait until https://github.com/aiidateam/kiwipy/pull/113 has > settled? > > > On 22/10/04 02:01, Andrius Merkys wrote: > > > Hi Bastian, > > > > > > On 2022-10-04 02:12, Bastian Germann wrote: > > > > What is the status on kiwipy? > > > > > > For some time kiwipy was blocked by pytray, but pytray is in unstable > > > now. I will revisit kiwipy. > > > > > > Best, > > > Andrius >
Bug#1014815: kiwipy initial packaging
Hi Bastian, On 2022-10-04 02:12, Bastian Germann wrote: > What is the status on kiwipy? For some time kiwipy was blocked by pytray, but pytray is in unstable now. I will revisit kiwipy. Best, Andrius
Bug#1014815: kiwipy initial packaging
What is the status on kiwipy?
Bug#1014815: kiwipy initial packaging
Hi Guilherme, On 2022-07-12 17:43, Guilherme de Paula Xavier Segundo wrote: Cool, I'll review your previous packaging, it will be a pleasure. You can be sure it will help and I thank you for your help. Good to hear! Initially what caught my attention was that it was a Python package. Currently I have focused my studies on this language and I have been looking to package programs along this line. However we are currently deploying a queue service in the company and we are between Kafka and RabbitMQ so I merged those two things. This makes sense. I have interest in packages depending on kiwipy, thus this would be great help to my cause as well. One question, are you interested in being my Sponsor in this package? If it's a problem, ignore it. Sure, just ping me whenever you need a review and upload for this package or its dependencies. Best, Andrius
Bug#1014815: kiwipy initial packaging
Andrius, Cool, I'll review your previous packaging, it will be a pleasure. You can be sure it will help and I thank you for your help. Initially what caught my attention was that it was a Python package. Currently I have focused my studies on this language and I have been looking to package programs along this line. However we are currently deploying a queue service in the company and we are between Kafka and RabbitMQ so I merged those two things. One question, are you interested in being my Sponsor in this package? If it's a problem, ignore it. Thanks. On 22/07/12 05:35, Andrius Merkys wrote: > Hi Guilherme, > > On 2022-07-12 17:21, Guilherme de Paula Xavier Segundo wrote: > > Thank you for your contact. > > I started kiwipy packaging. But it's okay to give you the ITP. > > > > Do you want me to give you the ITP? > > > > If not, I will follow the packaging and keep the package on the team. At > > the moment I'm not part of the team yet, but I'm waiting for approval. > > No, I am fine with you having it. I did not notice RFP -> ITP transition, so > I decided to update and push my local attempt to package kiwipy. Feel free > to reuse anything, rewrite (once you are in the team) or ignore if you want. > > Just out of curiosity, what caught your interest to kiwipy/plumpy? > > Best, > Andrius signature.asc Description: PGP signature
Bug#1014815: kiwipy initial packaging
Hi Guilherme, On 2022-07-12 17:21, Guilherme de Paula Xavier Segundo wrote: Thank you for your contact. I started kiwipy packaging. But it's okay to give you the ITP. Do you want me to give you the ITP? If not, I will follow the packaging and keep the package on the team. At the moment I'm not part of the team yet, but I'm waiting for approval. No, I am fine with you having it. I did not notice RFP -> ITP transition, so I decided to update and push my local attempt to package kiwipy. Feel free to reuse anything, rewrite (once you are in the team) or ignore if you want. Just out of curiosity, what caught your interest to kiwipy/plumpy? Best, Andrius
Bug#1014815: kiwipy initial packaging
Hi Andrius, Thank you for your contact. I started kiwipy packaging. But it's okay to give you the ITP. Do you want me to give you the ITP? If not, I will follow the packaging and keep the package on the team. At the moment I'm not part of the team yet, but I'm waiting for approval. Thanks! On 22/07/12 04:26, Andrius Merkys wrote: > Hello, > > I have pushed my initial packaging of kiwipy to salsa [1]. Everyone in > Python Team are welcome to contribute. > > [1] https://salsa.debian.org/python-team/packages/python-kiwipy > > Best, > Andrius signature.asc Description: PGP signature
Bug#1014815: kiwipy initial packaging
Hello, I have pushed my initial packaging of kiwipy to salsa [1]. Everyone in Python Team are welcome to contribute. [1] https://salsa.debian.org/python-team/packages/python-kiwipy Best, Andrius
