Re: Using a build profile on a buildd build
Quoting Scott Talbert (2022-06-15 22:30:13) > Is it possible to instruct the buildds to use a build profile when performing > an official build (e.g., using nocheck to break a dependency loop)? If so, > how? No, it is not. Main reason is probably that nobody has found the time to implement it yet. Thanks! cheers, josch signature.asc Description: signature
Using a build profile on a buildd build
Hi, Is it possible to instruct the buildds to use a build profile when performing an official build (e.g., using nocheck to break a dependency loop)? If so, how? Thanks, Scott
Bug#1012839: ITP: ros-catkin-tools -- Command line tools for catkin workspaces
Package: wnpp Severity: wishlist Owner: Timo Röhling X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: ros-catkin-tools Version : 0.9.0 Upstream Author : Open Source Robotics Foundation, Inc * URL : https://github.com/catkin/catkin_tools * License : Apache-2 Programming Lang: Python Description : Command line tools for catkin workspaces This package is part of ROS, the Robot Operating System. The catkin tools provide similar functionality to ROS 1 as the colcon tools do for ROS 2, such as building and testing packages. The package will be team-maintained under the umbrella of Debian Robotics Team at https://salsa.debian.org/robotics-team/ros-catkin-tools -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmKpnUMACgkQ+C8H+466 LVlnuwwAofS3gQHzd9BI1MhMsorcnUB8EoIDdGZulLqTpb782cxLLKxK09ZxBMX6 oYfxGcEWTZhR29kS5bBfF3w5t8eWCB3RMeb0/TFcC2cmBGbqZermiC/SHFRxgtL7 xkWPM+a9K3P4JYmtZiJboscb+hHSfDS5J4G8gHzu54GGFl9J87DEcrM1stWx9HwP DpW68Rv8MeWInJU4VtQDVkP1urvPvMyALb6iJetm8fAmE9PjDJbKns0VEeibRlJN LWfN79Ss74tohC2dJ1DT+NreZYJxcKuuqFCEu/OSpw7RKMWJIuNfi1Bsb76o1V+J OaqYd4JhQDF/xJe9JyM8ITtcfb5db2A/wele2H9URGnbbgSfrmMnCwDi2yHThVvo mMDeoCmf3xQZ8xFnCMYZqerhHRwENYG75JsdBkD+88Fw2ywAIdMw7764sPgNhhIu oTFPqQuN4T1RKQ+W1U6cA1XwptoV74JZid+HrOcnxEqhS2BLF00tIOdRdTdFnQEl 1UIeZTl8 =HrFV -END PGP SIGNATURE-
Re: guile-cairo
ke, 2022-06-15 kello 09:55 +0200, julien.pu...@gmail.com kirjoitti: > > Let your new package migrate to testing, since it's that one which > doesn't have the autoremoval issue? > I'm not sure I understand what you mean. The Guile 2.2 dependency issue is solved in the new package guile-cairo 1.11.2-5, which should not be autoremoved. The new package should migrate to testing in a few days. - Tommi -- Kotisivu / Homepage: http://www.iki.fi/tohoyn/ Sähköposti / E-Mail: tommi.hoynalan...@iki.fi GPG-sormenjälki / GPG fingerprint: 55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83 FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer
Bug#1012837: ITP: qoi -- “Quite OK Image Format” for fast, lossless image compression
Package: wnpp Severity: wishlist Owner: Gürkan Myczko X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: qoi Version : 0+git20220615+ds Upstream Authors: Dominic Szablewski URL : https://github.com/phoboslab/qoi * License : MIT Description : “Quite OK Image Format” for fast, lossless image compression This is the original QOI implementation to work with images with C or C++.
Re: guile-cairo
Le mercredi 15 juin 2022 à 11:11 +0300, Tommi Höynälänmaa a écrit : > ke, 2022-06-15 kello 09:55 +0200, julien.pu...@gmail.com kirjoitti: > > > > Let your new package migrate to testing, since it's that one which > > doesn't have the autoremoval issue? > > I'm not sure I understand what you mean. The Guile 2.2 dependency > issue is solved in the new package guile-cairo 1.11.2-5, which should > not be autoremoved. The new package should migrate to testing in a > few days. > The autoremoval from testing concerns the old package, which does depend on guile 2.2. Normally your new package should migrate to testing before the old one gets kicked out. Don't worry! J.Puydt
Re: guile-cairo
Le mercredi 15 juin 2022 à 10:29 +0300, Tommi Höynälänmaa a écrit : > > I recently received e-mail that package guile-cairo is to be > autoremoved 2022-07-09. The reason is that it depended on guile 2.2. > However, I made new version guile-cairo-1.11.2-5 that depends only on > guile 3.0. What shall I do in order to cancel the autoremoval? Let your new package migrate to testing, since it's that one which doesn't have the autoremoval issue? Cheers, J.Puydt
guile-cairo
Hello I recently received e-mail that package guile-cairo is to be autoremoved 2022-07-09. The reason is that it depended on guile 2.2. However, I made new version guile-cairo-1.11.2-5 that depends only on guile 3.0. What shall I do in order to cancel the autoremoval? - Tommi Höynälänmaa -- Kotisivu / Homepage: http://www.iki.fi/tohoyn/ Sähköposti / E-Mail: tommi.hoynalan...@iki.fi GPG-sormenjälki / GPG fingerprint: 55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83 FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer
