Re: automated CI on salsa to prepare MR for new upstream version
Am Sat, Feb 18, 2023 at 11:25:11AM +0100 schrieb Andreas Tille: > > Does it call deb-new-upstream as well? That's the one that mainly seems > > relevant here. > > I just learned about deb-new-upstream. Its parsing uscan manually but its not > very robust and I should probably switch to use deb-new-upstream. I just learned that routine-update is currently broken due to a changed output by uscan (need to check this later when I have more time). This gave me sufficient motivation to check out deb-new-upstream. I admit that bug #1031913 is some kind of show stopper for me currently to consider it as a replacement for the current strategy in routine-update to simply use uscan. How to you work around this in janitor? Kind regards Andreas. -- http://fam-tille.de
Re: icc-profiles_2.2_source.changes REJECTED
Le vendredi 24 février 2023, 06:13:48 UTC Shengjing Zhu a écrit : > Hi, > > On Fri, Feb 24, 2023 at 7:38 AM Jonas Smedegaard wrote: > > > > What to do when a package is blocked from getting updated due to it > > being itself? > > > > I have tried replying to FTPmasters as invited in the rejection message, > > but have been met with silence. > > > > I have tried filing bug#1030961 but have so far seen no response on that > > either. > > > > Will it make sense to reassing that bugreport to the technical > > committee? Or to the release team? Or should I request removal of the > > package, because security bugfixes (however unlikely for a package > > containing purely static data files) is impossible? > > > > > > - Jonas > > > > Quoting Debian FTP Masters (2023-02-09 04:19:39) > > > > > > icc-profiles source: lintian output: > > > 'license-problem-md5sum-non-free-file ECI-RGB.V1.0.icc usual name is > > > ECI-RGB.V1.0.icc. Does not allow modification See also > > > https://packages.debian.org/sid/icc-profiles.', automatically rejected > > > package. Seems like a bug on lintian Feel free to prod me with a small testcase or a patch will try to do something Bastien > [snip] > > > icc-profiles source: lintian output: > > > 'source-only-upload-to-non-free-without-autobuild ', automatically > > > rejected package. > > > icc-profiles source: If you have a good reason, you may override this > > > lintian tag. > > It's auto rejected. So I think it can be technically solved. > For license-problem-md5sum-non-free-file, it's obviously a false > positive from lintian. It should not emit such if the source is the > non-free section. It should be reported as a bug for the lintian > package. And you can submit patches as well, backport to the version > that ftp-master server uses. > For source-only-upload-to-non-free-without-autobuild, it's really a > bug in your upload. You should fix it. > > signature.asc Description: This is a digitally signed message part.
Bug#1031936: ITP: python-a2wsgi -- Convert between ASGI and WSGI apps
Package: wnpp Severity: wishlist Owner: Michael Fladischer X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-a2wsgi Version : 1.7.0 Upstream Contact: abersheeran * URL : https://github.com/abersheeran/a2wsgi * License : Apache-2 Programming Lang: Python Description : Convert between ASGI and WSGI apps Convert WSGI app to ASGI app or ASGI app to WSGI app in pure Python with no dependencies outside the standard library. Compared with other converters, the advantage is that a2wsgi will not accumulate the requested content or response content in the memory, so you don't have to worry about the memory limit. This problem exists in converters implemented by uvicorn/startlette or hypercorn. I intend to maintain this package as part of the DPT. -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmP6MBQRHGZsYWRpQGRl Ymlhbi5vcmcACgkQ/9PIi5l90WoUXAgAk/PbepnDuFPvNTD5Spe1M0mkWlYp5WPn cXQ0qBZtJa4FS2wvSmgQbdugUkCYO7JMsmOeqeUeWxD3UqXp8TPPf71uLzUOOLSq VFb33bY/8XGj4SxjhXTVw1UCgeMqDby2kD8RrPd/p+rp2gjz3IK3lH7xmHo70nhf 0IbjIjlPkHTuVg7mBpaaqtMQZ0hPI1aCJoR7IKO1cztpA9bcXys5P9HRLpGmBHhB rPLDhOxyHIidYOgQmjH6H3zXEybbL1O0n4w1sE/0veiV8VVZJi4xpC+Edlbuy1gt 5PFMZ1iA45UKr+XoC8WdRrcF9wSSdMNwyZ4GtNQ3ECWOYxpq50oK5g== =CjF/ -END PGP SIGNATURE-
Re: MariaDB 10.11 in Bookworm - call for contributions
Hi! On Thu, 23 Feb 2023 at 08:22, Otto Kekäläinen wrote: > > Hello! > > (Stop reading if you don't use MariaDB) > > I am currently preparing the upload of MariaDB 10.11.2-2 to Debian > unstable and aim for the highest possible quality. I am currently > doing the bulk of the testing and packaging alone and to make sure > that the quality is top notch, I would be glad to see more people > contribute. > > If you have time to help, please consider these (in order of importance): > > 1. Review current open MRs at > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests > > 2. Review items highlighted by Debian QA systems (Lintian, builds etc) > and submit a fix to improve the quality: > https://tracker.debian.org/pkg/mariadb > > 3. Review what testing we have at > https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and > think about potential gaps - CI is very important as it is the only > way we can prevent regressions in a scalable way > > 4. Review/follow-up on existing bugs that currently need more > information: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb&src=mariadb-10.6&src=mariadb-10.5&src=mariadb-10.3&src=mariadb-10.1 > > MariaDB and C++ skills are useful, but not required. For example > reviewing the NEWS for 10.11 requires no coding skills: > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37 One more items I am requesting help with: 5. If you know C/C++ compatibility on armhf and care about e.g. Raspberry PI your help would be very useful. Upstream does not test/target armhf and there are many minor places in upstream code that would need some armhf tweaks. You could for example install the mariadb-test package and run the full upstream test suite with 7227 tests and see which ones currently break on armhf (details in https://optimizedbyotto.com/post/grokking-mariadb-test-run-mtr/). - Otto
Bug#1031972: ITP: nvidia-cudnn-frontend -- c++ wrapper for the cudnn backend API
Package: wnpp Severity: wishlist Owner: Mo Zhou X-Debbugs-Cc: debian-devel@lists.debian.org, pkg-nvidia-de...@lists.alioth.debian.org * Package name: nvidia-cudnn-frontend * URL : https://github.com/NVIDIA/cudnn-frontend * License : MIT (but will enter contrib due to non-free deps) Programming Lang: C++ Description : c++ wrapper for the cudnn backend API This is needed for the cuda version of pytorch. The package will be maintained by Debian NVIDIA Maintainers
Bug#1031973: ITP: nvidia-cutlass -- CUDA Templates for Linear Algebra Subroutines
Package: wnpp Severity: wishlist Owner: Mo Zhou X-Debbugs-Cc: debian-devel@lists.debian.org, pkg-nvidia-de...@lists.alioth.debian.org * Package name: nvidia-cutlass * URL : https://github.com/NVIDIA/cutlass * License : BSD-3-Clause (has to enter contrib due to non-free deps) Programming Lang: C++ Description : CUDA Templates for Linear Algebra Subroutines This is needed for the cuda version of pytorch. The package will be maintained by Debian NVIDIA Maintainers
need GBP help with groff 1.23.0 (1.23.0~rc3-1 package prepared)
Background: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011666
Can someone advise me as to the correct procedure for merging upstream
release candidate archives into https://salsa.debian.org/debian/groff ?
I am not a proficient gbp user, but I think I have done what is
necessary.
...except that I don't think I did the upstream merge/tagging right.
I suspect this because if I do a "git rebase -i origin", git goes crazy
and tells me I have merge conflicts. None of the release candidates
were already staged even as reference points, so I had to wade into the
gbp documentation myself, and I probably screwed it up.
*** I have not PUSHED anything. ***
Some relevant shell history is at the end of this message.[1]
But after the point where I merged the upstream tarballs, things are
clean and I can rebase at will.
The upstream diffs are too gigantic to enclose (4,500+ commits since
groff 1.22.4), and not very interesting as they can be seen at groff's
own Git repo.
I'm attaching a git diff -p of my changes after that, meaning the actual
packaging work.
For the benefit of people reading this message, here are the commit
messages themselves (git log -r HEAD~21..HEAD).
commit 3cff7c6967e89d187efb160ce7d2a09af5ea82aa (HEAD -> master)
Author: G. Branden Robinson
Date: Sat Feb 25 22:53:06 2023 -0600
debian/changelog: Add upstream bug closers.
commit 1fd80f4151713e9f1d3cb52a4b749fa643776908
Author: G. Branden Robinson
Date: Sat Feb 25 22:29:27 2023 -0600
debian/groff{,-base}.install: Add new files
...provided upstream (en.tmac, hyphen.it, it.tmac, groff_font.5,
groff_out.5, groff_tmac.5, groff_man_style.7, groff_rfc1345.7,
FontMap-X11, ptx.tmac, rfc1345.tmac, sanitize.tmac, sboxes.tmac; see
upstream NEWS).
commit 56bf101afd21b9516775f58511e51d85dde06ef1
Author: G. Branden Robinson
Date: Sat Feb 25 22:09:23 2023 -0600
debian/groff{,-base}.install: Drop files
...that are no longer produced upstream (see upstream NEWS).
commit 9e99a662a4512e1f6656da2b9408f0f411abd311
Author: G. Branden Robinson
Date: Sat Feb 25 21:53:50 2023 -0600
debian/rules (confflags): Migrate option name.
...to "--with-appdefdir" from "--with-appresdir" per upstream NEWS.
commit 21ca0ea6c2162a95faf850b7f9c208b4d6d05374
Author: G. Branden Robinson
Date: Sat Feb 25 21:47:03 2023 -0600
Drop {meintro,meref,pic}.txt.
commit 58720f040d16da8bc868eca5466c91ee1a343889
Author: G. Branden Robinson
Date: Sat Feb 25 21:17:45 2023 -0600
debian/patches/clamp-negative-tab-stop*: Drop
Applied upstream in commit 6692653f7cae4116d4e70318f71b3d0808f2261f,
2021-09-11.
commit 01d76131b10c44f05ba7378a6193a5ce74f10fb9
Author: G. Branden Robinson
Date: Sat Feb 25 21:14:29 2023 -0600
debian/patches/destructor-segv.patch: Drop
Applied upstream in commit c788cf8c6bbe939fa11f7ec032e525a7e33f41b6,
2020-09-29.
commit 0323958c2ea85b86d24e07907e5718584fe5e746
Author: G. Branden Robinson
Date: Sat Feb 25 21:11:54 2023 -0600
debian/patches/document-sgr.patch: Resync
...with upstream.
commit 34942d9ebdb365be2765d1cf05850f7a8a6b78ad
Author: G. Branden Robinson
Date: Sat Feb 25 21:07:36 2023 -0600
debian/patches/bsd-updates.patch: Drop
Applied upstream in commit 5a8af7104f1c581bcfbad12b56033ad403b0afe1,
2019-12-21.
commit 915e5df22c31ce935de36322f1fa4db933c923e5
Author: G. Branden Robinson
Date: Sat Feb 25 21:04:51 2023 -0600
debian/patches/mdoc-Lk-arguments.patch: Drop
Applied upstream in commit 76e4db6e839904d2e2a28b29b483678214598f3b,
2019-01-12.
commit 34fe473ff1c2853d823d5acd3362aeef3e634c7b
Author: G. Branden Robinson
Date: Sat Feb 25 21:00:23 2023 -0600
debian/patches/avoid-perl-diamond.patch: Drop
Applied upstream in commit 27472b5ae548d3dbe933713d488d676708996253,
2019-01-24.
commit 4266e24f1d65d5e7c06ac3c2ae2a202c3d0629ce
Author: G. Branden Robinson
Date: Sat Feb 25 20:57:25 2023 -0600
debian/patches/sort-perl-hash-keys.patch: Drop
Applied upstream in commit fcf3dc68839d83bfba206d1febffd9514a71ee82,
2015-11-06.
commit cb1cbb55e73e877c73a45d070eed89179699f316
Author: G. Branden Robinson
Date: Sat Feb 25 20:52:43 2023 -0600
debian/patches/series: Drop display-utc-times.*
commit 2ec0236804bf60e18282526d343068e9c26d6df2
Author: G. Branden Robinson
Date: Sat Feb 25 20:49:14 2023 -0600
debian/patches/mmse-note.patch: Resync w/ upstream
commit e8e7c6ce1e8267bbf6c65ce5910140ccc5a8993a
Author: G. Branden Robinson
Date: Sat Feb 25 20:45:39 2023 -0600
debian/patches/load-desc-failure.patch: Resync
...with upstream.
commit b7dc5d92ac984184ab30aef76e5d21752a044fe9
Author: G. Branden Robinson
Date: Sat Feb 25 20:40:55 2023 -0600
debian/patches/papersize-config.patch: Resync
...with upstream.
commit bb6d8e31ae4f60afd1ede232618dbff17e64ac87
Author: G. Branden Robinson
Date: Sat Feb 25 20:35:20 2023 -0600
debian/patches/extratmacdirs.p
