Bug#1011377: RFS: ngraph-gtk/6.09.06-1 -- create scientific 2-dimensional graphs
Control: tags 1011377 - moreinfo Thank you for the review. I have fixed the problems. > * copyright: > + CC0-1.0 is in common-licenses, no need to have the full license > text verbatim in d/copyright remove full license text and add location of the license text. > + src/gettext.h is under LGPL, not GPL fixed. > + missing copyright holders and license info for various files under > src/gtk/* (at least sourcecompletionwords.*, ruler.c) add license informations for sourcecompletionwords.* and gtk_ruler.c. > * control: this combination of build-deps makes no sense: debhelper > (>= 12.0.0), debhelper-compat (= 13); you probably want to remove > the (leftover?) debhelper one remove debhelper (>= 12.0.0). > * docs: README and NEWS files aren't useful as documentation (the > former only mentions the project's homepage, already documented in > the packaging; the latter is but a list of released versions) README and NEWS are removed from docs. > Nitpicking: > * changelog: entry about AC_CHECK_FILE concerns an upstream rather > than a debian packaging change the entry is removed. > * rules: could make use dh_bash-completion or "execute_after" instead > of an override use dh_bash-completion instead of override_dh_auto_install. I have uploaded revised packages to mentors.debian.org.
Bug#1011956: ITP: fonts-nunito -- Well balanced Sans Serif with rounded terminals
Hi Paul, thanks for your feedback. I've just mailed the FTP team and asked them to reject the upload. I'll prepare another package with proper sources. Regards, Tobias
Bug#994911: error modifying deb822 object while iterating
Control: tags -1 moreinfo unreproducible On Thu, 14 Oct 2021 19:17:47 + Jelmer Vernooij wrote: > [...] > Yep, this is standard behaviour with a dict - so I wouldn't be surprised if > this was happening generally, but the default deb822 doesn't exhibit > this so it makes migrating a bit harder. > > Unfortunately I've lost track of the run in the janitor that > showed this issue so we'll just have to re-enable and see > if it's fixed now. > > Jelmer > > > Hi Jelmer, Can you still reproduce this bug? I suspect it might have been fixed as a side-effect of another change already. Alternative, if you can reproduce it, please attach the code + file that triggers the bug so I can investigate it in detail. Thanks, ~Niels
Bug#1011974: RFS: mosh/1.3.2-2.2 [NMU] [RC] -- Mobile shell that supports roaming and intelligent local echo
Package: sponsorship-requests Severity: important Control: block 1005718 by -1 Dear mentors, I am looking for a sponsor for the package "mosh": * Package name : mosh Version : 1.3.2-2.2 Upstream Author : Keith Winstein * URL : https://mosh.org * License : GPL-2+, GPL-3+ with Autoconf exception, public-domain, GPL-3+ with OpenSSL exception, ISC * Vcs : https://github.com/mobile-shell/mosh Section : net The source builds the following binary packages: mosh - Mobile shell that supports roaming and intelligent local echo To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mosh/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mosh/mosh_1.3.2-2.2.dsc Changes since the last upload: mosh (1.3.2-2.2) unstable; urgency=medium . * Non-maintainer upload. * Lower warning level to distcheck to solve build against OpenSSL 3.0 with permitted deprecated declarations. (Closes: #1005718) Regards, signature.asc Description: This is a digitally signed message part
Bug#1005718: mosh: FTBFS with OpenSSL 3.0
To prevent mosh from being deleted from testing in a few days, I am proposing to change warnings level to distcheck. This option effectively adds `-Wno-error=unused-parameter -Wno-error=deprecated-declarations` compiler flags. This solution will buy us time to rewrite related code before the deprecated low-level functions get removed away. diffstat for mosh-1.3.2 mosh-1.3.2 changelog |8 rules |2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff -Nru mosh-1.3.2/debian/changelog mosh-1.3.2/debian/changelog --- mosh-1.3.2/debian/changelog 2018-08-08 20:45:44.0 +0300 +++ mosh-1.3.2/debian/changelog 2022-05-28 10:01:51.0 +0300 @@ -1,3 +1,11 @@ +mosh (1.3.2-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Lower warning level to distcheck to solve build against OpenSSL 3.0 with +permitted deprecated declarations. (Closes: #1005718) + + -- Nicholas Guriev Sat, 28 May 2022 10:01:51 +0300 + mosh (1.3.2-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru mosh-1.3.2/debian/rules mosh-1.3.2/debian/rules --- mosh-1.3.2/debian/rules 2017-08-25 01:04:25.0 +0300 +++ mosh-1.3.2/debian/rules 2022-05-28 10:01:46.0 +0300 @@ -22,7 +22,7 @@ --disable-silent-rules \ --enable-ufw \ --enable-completion \ - --enable-compile-warnings=error + --enable-compile-warnings=distcheck override_dh_perl: # mosh only uses Perl modules in perl-base. signature.asc Description: This is a digitally signed message part
Bug#1010663: RFS: strawberry/1.0.4-1 [ITP] -- Audio player and music collection organizer
Hi Jeroen and others, I'm sorry I won't have time to retry a new packaging upload for Strawberry. I already have a lot to fix on other packages I maintain and I miss time. So anyone who want to go on on this is welcome. If I remember there where no big issues or blocking points left but all the copyrights need to be well rechecked. For some files it's also a bit tricky because some headers have been rewritten since the fork of Clementine (it's forked from amarok...). So the main job left should be to ensure the copyright file is really completed and accurate. And as I'm not a DD I can't help for sponsoring so you will have to find one. Thomas
Bug#1011976: swetest disregards -ut option
Package: libswe-dev Version: 1.80.00.0002-1.1 Dear Maintainer, swetest command included in this package disregards -ut option, and always returns values at 00:00:00. I notice the bug when executing it by horoscop.sty in texlive-games.
Bug#1011977: FTBFS with OpenJDK 17: 5 failing tests
Source: htsjdk Version: 2.24.1+dfsg-3 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 htsjdk fails to build with OpenJDK 17, the jar can be built but then 5 tests fail, although all of them pass with OpenJDK 11: Gradle suite > Gradle test > htsjdk.samtools.fastq.BasicFastqWriterTest.testFlushNotSpammed FAILED java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:513) at org.testng.Assert.assertTrue(Assert.java:42) at org.testng.Assert.assertTrue(Assert.java:52) at htsjdk.samtools.fastq.BasicFastqWriterTest.testFlushNotSpammed(BasicFastqWriterTest.java:41) Gradle suite > Gradle test > htsjdk.samtools.filter.JavascriptSamRecordFilterTest.testJavascriptFilters[0](unsorted.sam, samFilter01.js, 8) FAILED htsjdk.samtools.util.RuntimeScriptException: The embedded 'javascript' engine is not available in java. Do you use the SUN/Oracle Java Runtime ? at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:90) at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:65) at htsjdk.samtools.filter.JavascriptSamRecordFilter.(JavascriptSamRecordFilter.java:58) at htsjdk.samtools.filter.JavascriptSamRecordFilterTest.testJavascriptFilters(JavascriptSamRecordFilterTest.java:58) Gradle suite > Gradle test > htsjdk.samtools.filter.JavascriptSamRecordFilterTest.testJavascriptFilters[1](unsorted.sam, samFilter02.js, 10) FAILED htsjdk.samtools.util.RuntimeScriptException: The embedded 'javascript' engine is not available in java. Do you use the SUN/Oracle Java Runtime ? at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:90) at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:65) at htsjdk.samtools.filter.JavascriptSamRecordFilter.(JavascriptSamRecordFilter.java:58) at htsjdk.samtools.filter.JavascriptSamRecordFilterTest.testJavascriptFilters(JavascriptSamRecordFilterTest.java:58) Gradle suite > Gradle test > htsjdk.variant.variantcontext.filter.JavascriptVariantFilterTest.testJavascriptFilters[0](ILLUMINA.wex.broad_phase2_baseline.2014.both.exome.genotypes.1000.vcf, variantFi lter01.js, 61) FAILED htsjdk.samtools.util.RuntimeScriptException: The embedded 'javascript' engine is not available in java. Do you use the SUN/Oracle Java Runtime ? at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:90) at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:65) at htsjdk.variant.variantcontext.filter.JavascriptVariantFilter.(JavascriptVariantFilter.java:54) at htsjdk.variant.variantcontext.filter.JavascriptVariantFilterTest.testJavascriptFilters(JavascriptVariantFilterTest.java:57) Gradle suite > Gradle test > htsjdk.variant.variantcontext.filter.JavascriptVariantFilterTest.testJavascriptFilters[1](ILLUMINA.wex.broad_phase2_baseline.2014.both.exome.genotypes.1000.vcf, variantFi lter02.js, 38) FAILED htsjdk.samtools.util.RuntimeScriptException: The embedded 'javascript' engine is not available in java. Do you use the SUN/Oracle Java Runtime ? at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:90) at htsjdk.samtools.filter.AbstractJavascriptFilter.(AbstractJavascriptFilter.java:65) at htsjdk.variant.variantcontext.filter.JavascriptVariantFilter.(JavascriptVariantFilter.java:54) at htsjdk.variant.variantcontext.filter.JavascriptVariantFilterTest.testJavascriptFilters(JavascriptVariantFilterTest.java:57) Best, -- Pierre
Bug#1011978: kakoune FTBFS on big endian
Source: kakoune Version: 2021.11.08-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-s...@lists.debian.org Control: block 1010335 by -1 https://buildd.debian.org/status/logs.php?pkg=kakoune&ver=2021.11.08-1 ... Fatal error: assert failed "hash_data(data, strlen(data)) == 0xf816f95b" at hash.cc:76 ... debian-s390 list is Cc'ed on this bug.
Bug#917789: Wrong tarball id (pristine-tar) when import-orig with --components
Hi Mo, Mattia, On Tue, Jan 08, 2019 at 08:16:58PM +0100, Guido Günther wrote: > On Tue, Jan 08, 2019 at 06:19:32PM +0100, Mattia Rizzolo wrote: > > On Thu, Jan 03, 2019 at 06:00:18PM +0100, Guido Günther wrote: > > > > It's quite strange that I cannot reproduce this problem anymore > > > > on the commit in question. > > > > > > > > @Mattia: Are you able to reproduce this problem? > > > > Weird, indeed I can't reproduce this right now :\ > > So upsetting, consider how many headaches it gave me over the years. > > > > > That does not work you want to use gbp export-orig to export the > > > tarballs and pass the subtarball names with --component (it's symmetric > > > to the import) since you otherwise lack the needed trees. Check the tb > > > package. So far I don't see a bug here. > > > > > > gbp export-orig --component contrib > > > > Could you please explain what `gbp export-orig` does? > > I never heard of that command, and till now I always called > > `pristine-tar checkout ../foobar_ver.tar.xz`. And to be honest I expect > > that to work regardless of what wrapper was used to do the initial > > `pristine-tar commit`. > > > > What particulare tree are you expecting? > > The only thing I can think of is a tree with the main tarball without > > the additonal tarball committed, are you having `export-orig` generate > > such a thing each time somehow (how would you get the same sha1??) > > You need a tree that has the component's tarball dirs dropped: > > https://github.com/agx/git-buildpackage/blob/master/gbp/scripts/export_orig.py#L77 > > gbp-buildpackage uses the same code when generating tarballs. Is there still an issue with opencv and it's additional tarball that I could reproduce? > Cheers, > -- Guido
Bug#1011979: ITP: ros2-performance-test-fixture -- Performance test fixture for ROS 2 benchmarks
Package: wnpp Severity: wishlist X-Debbugs-Cc: roehl...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Subject: ITP: ros2-performance-test-fixture -- Performance test fixture for ROS 2 benchmarks Package: wnpp Owner: Timo Röhling Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org * Package name: ros2-performance-test-fixture Version : 0.0.8 Upstream Author : Open Source Robotics Foundation, Inc * URL : https://github.com/ros2/performance_test_fixture * License : Apache-2 Programming Lang: C++ Description : Performance test fixture for ROS 2 benchmarks This package is part of ROS 2, the Robot Operating System. The performance test fixture provides a framework to run Google Benchmark driven performance tests for your ROS 2 packages. The package will be team-maintained under the umbrella of Debian Robotics Team at https://salsa.debian.org/robotics-team/ros2-performance-test-fixture -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmKR5ykACgkQ+C8H+466 LVnbJgwAlV+NIbC9UVsxmI7BdJVOiJy6zSUPZbkK7FQxltF215S/J2Rbaa+Knb3W r1sXRtj6l942iBZmay0fI8ktFpd4tFi695+vWqKyb45E4ii/SoOkq0016Z5Z6IZf Ji4mEtZFduhdRMksG6JdSfxC/dPtQyioXQPvwpjjgJSWY6r/C4ujaEyidaTUca0o lPruOmbSsHP9hBb/UhXxHKXhJYKwqzePd+EDBqz8HUOxg0I5LSpqY9efPHzlJfb6 w0p+q28b99YY4Hkol9MxxUoeRxbpFwaYxTYW6CaZMk+WGgXUmVj/oTsmWKvuS6hE B1XrydCpg7JCCyIhDl1g/e7uDMNcDw9yy1VRJyMQ3FiTYdpqYFniTGNSaTQWTkTc cHlzmxP/kheNjZMqGlkE6VN7L6WvCYxrBB5eruHkBxwxtJkzK/46yCZ93oB7+fpy 3EisAFYxGGw7R1ZR4DulVV0ln57Ad4HHKLpVJGyBjd6Vd1hxguqcAwNl2bl0F3O2 2uBrN6nK =LzSB -END PGP SIGNATURE-
Bug#917789: Wrong tarball id (pristine-tar) when import-orig with --components
On Sat, May 28, 2022 at 11:10:26AM +0200, Guido Günther wrote: > > You need a tree that has the component's tarball dirs dropped: > > > > https://github.com/agx/git-buildpackage/blob/master/gbp/scripts/export_orig.py#L77 > > > > gbp-buildpackage uses the same code when generating tarballs. > > Is there still an issue with opencv and it's additional tarball that I > could reproduce? I don't think so. I understand now that in those cases I need to use `gbp export-orig` instead of just running `pristine-tar checkout`. However, now I'm mostly confused why you're requiring such special tree when in my tests a plain `pristine-tar` using the main tree seemed to just work, mhh. (or at least, that's what my memory of this old matter claims) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#830490: Auto register components
Hi, On Fri, Jul 08, 2016 at 03:54:51PM +0200, Guido Günther wrote: > Package: git-buildpackage > Version: 0.8.0 > Severity: wishlist > > Additional tarballs should be added automatically to gbp.conf when > importing a dsc. We can also autodetect things on `import-orig --uscan`. Question is what should take precedence as the list in gbp.conf should be the "relevant" one. Cheers, -- Guido > -- Guido > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), > (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages git-buildpackage depends on: > ii devscripts2.16.2 > ii git 1:2.8.1-1 > ii man-db2.7.5-1 > ii python-dateutil 2.4.2-1 > ii python-pkg-resources 20.10.1-1.1 > ii python-six1.10.0-3 > pn python:any > > Versions of packages git-buildpackage recommends: > ii cowbuilder 0.80 > ii pbuilder 0.224 > ii pristine-tar 1.34 > ii python-requests 2.10.0-2 > ii sbuild 0.69.0-2 > > Versions of packages git-buildpackage suggests: > ii python-notify 0.1.1-4 > ii sudo 1.8.15-1.1 > ii unzip 6.0-20 > > -- no debconf information
Bug#1010663: RFS: strawberry/1.0.4-1 [ITP] -- Audio player and music collection organizer
On 27/05/2022 14:58, Peter wrote: Regarding the latest Salsa CI fails; Its not clear to me why changing the copyright file causes crossbuild & reprotest to fail, https://salsa.debian.org/debian/strawberry/-/pipelines/382967 when they both passed on the first upload ?? https://salsa.debian.org/debian/strawberry/-/pipelines/382861 reprotest passes when I run it locally === Reproduction successful === No differences in ./../*.deb 359c55b631de43ae319787bbacfb65fccafee48be9799b402505e08301fbb763 ./../strawberry-dbgsym_1.0.4-1_amd64.deb 3483b1d23b0d0f6ede8f1219c132a3de45afc9a649ef1712d09cce7387f6ad51 ./../strawberry_1.0.4-1_amd64.deb Cheers, Peter On rerun, crossbuild passes, but reprotest now fails with | failed with status 22| |ERROR: Job failed: exit code 1 ||22 -> 'Device disabled' |
Bug#1011339: marked as done (openssl: missing errors strings on mipsel)
Le ven. 27 mai 2022 à 16:54, Debian Bug Tracking System <
ow...@bugs.debian.org> a écrit :
> Subject: openssl: missing errors strings on mipsel
> Package: openssl
> Version: 3.0.3-4
> Severity: normal
>
> Hi,
>
> nodejs dynamically links to openssl, and since openssl >= 3,
> on mipsel, some of its tests are failing, see
> https://buildd.debian.org/status/package.php?p=nodejs
>
> The failures look like openssl was configured with no-err, e.g:
> AssertionError [ERR_ASSERTION]: Expected values to be strictly
> deep-equal:
> + actual - expected
>
> Comparison {
> + message: 'error:1C8000A5:Provider routines::reason(165)'
> - message: 'error:1C8000A5:Provider routines::illegal or unsupported
> padding mode'
> }
> at Object.
> (/root/debian/nodejs-16.14.2+dfsg/test/parallel/test-crypto-sign-verify.js:59:10)
>
> I did not find if nodejs was doing a specific configuration for mipsel.
>
> Note that mips64el and other supported archs have no such test failures.
>
> Could it be that openssl 3 disables error strings on 32-bits platforms ?
>
>
>* Update openssl.cnf to fix tests on mipsel (Closes: #1011339)
>
That didn't fix the issue we're seeing.
I tried nodejs in a qemu mips, but couldn't reproduce, so will try on a
porter box.
Bug#1011980: RM: libperl5i-perl -- ROM; RC-buggy, low popcon, broken upstream
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: debian-p...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please remove libperl5i-perl from the archive. RC bug: #959193 According to the upstream ticket chances are low that there will be a fix: https://rt.cpan.org/Public/Bug/Display.html?id=131226 Last upstream commit: 2016 Popcon: vote: 2 + old: 10 Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmKR6y9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgarJxAAknqvBQmYYmpKZgY0vuB0/pfse8Wry2ZIbcHfkbIM/hliDihB/Lb3EJBr JAQBPxS1gxalG9icrCE4hdQC1gvbxLii83lBqV7uc+XmRJ9zYegnzg9twDjZPD6f Krt1Gkf1jQipAIvsIw/4jzHFaI+teh3zpkumQMFW3B+YlEhXYa99/PmBqd4giDmU uhxdAKtauLgLeYefoqOaf8XFtwXbkDYS6HiiIYyDBVLfILDdojm/+XcOK9jxbaz7 58eOJ6Qp1iwt8f0uCaP5Mg0Di75z8sfszMF35E+PewXOuG9IXaMFXHJwwpmcaX1C AGWJu9rseSt5N77Nu5lWFfcpYZt3XnkgKaHFayoeH1MtPOuRT51S19a3vUhlxrxd 1byudCRhOvdKUyhKitXp6q5Xghm7f3iW9YEckagslo695b25/e7aOOqxUwI7rPek n0IcAvEA/22jzHpLIJQgJi0/wkzLgcKhES0si28KdpUYQSFMSA8RttaGemDlL2IS X+G8AEvelpk/QnnqHJyWv6czQe2xHPvD7y8Io7DgNMWbNTopWIoCum60zJrACix1 nyaCeIz59ZTrWnUprfMSVlgdE/DG2V0cIQo38NpERux/dcU4cWXaQjevSrRpbKUV fKvRiOymWo9VORu0EP4IwBwbPVvlAgwbbCjyJSdKMfqCVHbqYi0= =LDtl -END PGP SIGNATURE-
Bug#1011981: RM: libdbd-sqlite2-perl -- ROM; RC-buggy, obsolete
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: debian-p...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please remove libdbd-sqlite2-perl from the archive. As noted in #998351, its time is long over. The last (optional) reverse dependency (beancounter) has been fixed a couple of days ago. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmKR6+dfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZEARAAhyI8gHs/OdHNrIqObNvCD8VrIVU/d8KrgM0bGKhSG8xR+F1/9dHPv+Lp DHEctsHGx/jGqIsaNQcHx6EDANNtbW3dsuqkJrGfIOoPuVy5m4B6P/M06CXdWesT KKHvL1rChvDXRflMXc13eqfVNJVUi+yn792Xk7T8UjR0Pacjq+dBiNqDckEdq/K/ sIDJPuEArYAdLFSkqzMWOK9luO0Gvlhk61eLz1kQWItwcsZOct6zucMLpsBKSa5s NgRXc3aQTPLJYJ6glG8DlxciUDfLyHEWlxJG37y1CDq2BzRta8DKhtPErtSERpup OdRTqZCIFhjPocaltp6Bq7/r2WZLs48+K42Z1oPuNglo8lyTxNHaILZUWyehouse iB7/njVON1qnStpSC+/kmxiJKnj5E65Hq1hUwu3+MV1HQhaiBFgo/TuPeSlKk2Ei Bo8H2cCcxMjcRt/rqrEgaeQ4GAgj+mlM7GaPvDfCsmjt1YynVa+caVxUO9JL2HVW 9ZcQKnOZm4IH85/qbjKIWUlnWrsAJu1U4Ahp/f3hbkvA59XkdayFFhHvAjFtOvvW TrqmtVBWm2DsdlNqCKxy0qmXysMl8Z+8hokL+IwQwT435W9owDFOykZTjb9vNtTh 27cf/gj5WomWb2tbZ+FGeUOmdKN/CzTPSfnqoQO/3DcnctqAhWM= =EbzK -END PGP SIGNATURE-
Bug#934200: [git-buildpackage/master] docs: Make --component more prominent
tag 934200 pending thanks Date: Sat May 28 11:25:36 2022 +0200 Author: Guido Günther Commit ID: 613fcb893cfe4f64a6c7060a5ab489d529510139 Commit URL: https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=613fcb893cfe4f64a6c7060a5ab489d529510139 Patch URL: https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=613fcb893cfe4f64a6c7060a5ab489d529510139 docs: Make --component more prominent Closes: #934200
Bug#934200: gbp import-orig is broken with multiple source tarballs
Hi, On Mon, Feb 17, 2020 at 09:25:51PM -0500, Sandro Tosi wrote: > > this is still happening: i'm trying to upgrade dblatex to the latest > > upstream release and the source package has 2 upstream tarballs. > > > > `gbp import-orig --uscan` imports only the "main" tarball but not the > > additional component (`examples`, > > https://salsa.debian.org/debian/dblatex/tree/pristine-tar) and `gbp > > import-orig ../../dblatex*orig*` complains multiple files are > > specified on the command-line, and i did not find a combination of > > commands to import 2 tarballs one after the other. > > > > I'm not sure how frequent is the case of multiple tarballs, but it > > would still be extra-useful if this bug could be addressed soon. > > nevermind (i guess?), upon further reading i found out i need to use > the `--component` cli option; maybe an example in the doc/manpage > would be useful? thanks for maintaining gbp! I've added more mentions to the manpage. If there's a reproducer where importing with uscan fails when the components are given it would be great to have a reproducer (preferably in a new issue as this one mixes several things already). We can certainly make component tarballs more automatic (#830490). Cheers, -- Guido
Bug#1010468: transition: gnat-11
Package: release.debian.org Followup-For: Bug #1010468 Hello. As far as I understand, the gnat-11 transition is complete and this bug can be closed.
Bug#917789: Wrong tarball id (pristine-tar) when import-orig with --components
Hi,
On Sat, May 28, 2022 at 11:13:20AM +0200, Mattia Rizzolo wrote:
> On Sat, May 28, 2022 at 11:10:26AM +0200, Guido Günther wrote:
> > > You need a tree that has the component's tarball dirs dropped:
> > >
> > > https://github.com/agx/git-buildpackage/blob/master/gbp/scripts/export_orig.py#L77
> > >
> > > gbp-buildpackage uses the same code when generating tarballs.
> >
> > Is there still an issue with opencv and it's additional tarball that I
> > could reproduce?
>
> I don't think so. I understand now that in those cases I need to use
> `gbp export-orig` instead of just running `pristine-tar checkout`.
>
> However, now I'm mostly confused why you're requiring such special tree
> when in my tests a plain `pristine-tar` using the main tree seemed to
> just work, mhh.
I assume that worked since you still had the tree in your git repo
(which is the same tree gbp-export-orig regenerates). If you drop unused
trees it fails (i'm using selinux-python as example as it's pretty small):
$ git reflog expire --expire=now --all
$ git gc --prune=now
Enumerating objects: 594, done.
Counting objects: 100% (594/594), done.
Delta compression using up to 4 threads
Compressing objects: 100% (304/304), done.
Writing objects: 100% (594/594), done.
Total 594 (delta 269), reused 594 (delta 269), pack-reused 0
$ pristine-tar checkout selinux-python_3.4.orig.tar.gz
fatal: ambiguous argument '66959325048ceffde0999354208467adc63a5ec6^{tree}':
unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
fatal: not a valid object name: 66959325048ceffde0999354208467adc63a5ec6^{tree}
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar
66959325048ceffde0999354208467adc63a5ec6\^\{tree\} | (cd
'/tmp/pristine-tar.M6ynn876_U' && tar x)
while gbp export-orig recreates it
$ gbp export-orig -v
…
gbp:debug: pristine-tar [] ['verify',
'/tmp/a/selinux-python/../selinux-python_3.4.orig.tar.gz']
gbp:debug: pristine-tar [] ['verify',
'/tmp/a/selinux-python/../selinux-python_3.4.orig-sandbox.tar.gz']
gbp:debug: pristine-tar [] ['verify',
'/tmp/a/selinux-python/../selinux-python_3.4.orig-gui.tar.gz']
Which then also makes pristine-tar work again (until the tree is pruned again):
$ pristine-tar checkout selinux-python_3.4.orig.tar.gz
pristine-tar: /tmp/a/selinux-python/selinux-python_3.4.orig.tar.gz already
exists and is valid
pristine-tar: successfully generated selinux-python_3.4.orig.tar.gz
Cheers,
-- Guido
> (or at least, that's what my memory of this old matter claims)
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
> More about me: https://mapreri.org : :' :
> Launchpad user: https://launchpad.net/~mapreri `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Bug#973755: git-buildpackage: gbp clone and import-* should defuse git attributes
Hi, On Fri, Jan 29, 2021 at 04:45:44PM +0100, Andrej Shadura wrote: > Hi, > > On Wed, 04 Nov 2020 16:02:01 +0100 Andrej Shadura > wrote:> Quite a lot of packages ship .gitattributes in their tarballs, > leading > > to strange effects while building packages and, most importantly, > > leading to the imports not creating Git trees identical to the tarballs. > > > > A remedy to this would be git-buildpackage creating .git/info/attributes > > with this content: > > > > * -text -eol -crlf -ident -filter -working-tree-encoding > > > > This disables any transformation of the version-controlled file. > > > > Even better would be if gbp created the Git trees manually using > > low-level Git commands which don’t take Git attributes into account. > > > > Fixing this bug will also fix #719363. > > Any update on this? Can we close this as we have git-setup-gitattributes and an option to gbp-clone now? Cheers, -- Guido > > Thanks! > > -- > Cheers, > Andrej
Bug#1010468: transition: gnat-11
On 2022-05-28 11:39:40 +0200, Nicolas Boulenguez wrote: > Package: release.debian.org > Followup-For: Bug #1010468 > > Hello. > As far as I understand, the gnat-11 transition is complete and this > bug can be closed. Almost … phcpack still needs to migrate. Best Sebastian -- Sebastian Ramacher
Bug#1011935: (no subject)
On Fri, May 27, 2022 at 10:58:24AM -0600, tsteven4 wrote: > Why do many qt6 packages have a dependency on qtchooser if you are not > supporting Qt6 with qtchooser? > > qt6-webengine-dev-tools > qt6-l10n-tools > qt6-documentation-tools > qt6-declarative-dev-tools > qt6-base-dev-tools > qmlscene-qt6 > qml-qt6 > assistant-qt6 > linguist-qt6 > designer-qt6 I discussed this with my co-maintainers, and we decided to remove these dependencies. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1011345: transition: rakudo
Control: tags -1 confirmed On 2022-05-20 10:36:34 -0400, M. Zhou wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Dear release team, > > We have uploaded rakudo 2022.04 to experimental, and would like to > start the transition and rebuild packages Please go ahead Cheers > > Ben file: > > title = "rakudo"; > is_affected = .depends ~ "raku-api-2022.02" | .depends ~ "raku-api-2022.04"; > is_good = .depends ~ "raku-api-2022.04"; > is_bad = .depends ~ "raku-api-2022.02"; > Thank you for using reportbug > -- Sebastian Ramacher
Bug#984516: git-buildpackage: import-dsc shows wrong error message when debian branch is missing
Hi, On Thu, Mar 04, 2021 at 10:01:25PM +0700, Arnaud Rebillout wrote: > Package: git-buildpackage > Version: 0.9.22 > Severity: normal > Tags: patch > User: de...@kali.org > Usertags: origin-kali > > Dear Maintainer, > > When running 'gbp import-dsc ...', if gbp does not find the debian > branch, it shows an error message that mentions the upstream branch. It > proposes to use --upstream-branch=, while what's really needed is > --debian-branch=. I've applied your patch now, thanks and sorry for the delay! -- Guido > > Logs: > > # initial failure > $ gbp import-dsc apt:desktop-base/sid > gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... > gbp:info: Tag 11.0.2 not found, importing Debian tarball > gbp:error: > Repository does not have branch 'master' for upstream sources. If there is > none see > > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT > on howto create it otherwise use --upstream-branch to specify it. > > Also check the --create-missing-branches option. > > # trying as suggested > $ gbp import-dsc --upstream-branch=debian apt:desktop-base/sid > gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... > gbp:info: Tag 11.0.2 not found, importing Debian tarball > gbp:error: > Repository does not have branch 'master' for upstream sources. If there is > none see > > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT > on howto create it otherwise use --upstream-branch to specify it. > > Also check the --create-missing-branches option. > > # in fact it's the debian branch! > $ gbp import-dsc --debian-branch=debian apt:desktop-base/sid > gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... > gbp:info: Tag 11.0.2 not found, importing Debian tarball > gbp:info: Version '11.0.2' imported under '/home/user/src/desktop-base' > > Thanks! > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages git-buildpackage depends on: > ii devscripts 2.21.1 > ii git1:2.30.1-1 > ii man-db 2.9.4-2 > ii python33.9.1-1 > ii python3-dateutil 2.8.1-5 > ii python3-pkg-resources 52.0.0-1 > ii sensible-utils 0.0.14 > > Versions of packages git-buildpackage recommends: > ii pristine-tar 1.49 > ii python3-requests 2.25.1+dfsg-2 > ii sbuild0.81.2 > > Versions of packages git-buildpackage suggests: > pn python3-notify2 > ii sudo 1.9.5p2-2 > ii unzip6.0-26 > > -- no debconf information > >From c7a7d48462708dc6ed7f4813253c7aed9238aaeb Mon Sep 17 00:00:00 2001 > From: Arnaud Rebillout > Date: Thu, 4 Mar 2021 21:23:48 +0700 > Subject: [PATCH] import-dsc: Fix error message when missing debian branch > > The error message mistakenly talks about the upstream branch when it > should be talking about the debian branch. Logs: > > # initial failure > $ gbp import-dsc apt:desktop-base/sid > gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... > gbp:info: Tag 11.0.2 not found, importing Debian tarball > gbp:error: > Repository does not have branch 'master' for upstream sources. If there > is none see > > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT > on howto create it otherwise use --upstream-branch to specify it. > > Also check the --create-missing-branches option. > > # trying as suggested > $ gbp import-dsc --upstream-branch=debian apt:desktop-base/sid > gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... > gbp:info: Tag 11.0.2 not found, importing Debian tarball > gbp:error: > Repository does not have branch 'master' for upstream sources. If there > is none see > > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT > on howto create it otherwise use --upstream-branch to specify it. > > Also check the --create-missing-branches option. > > # in fact it's the debian branch! > $ gbp import-dsc --debian-branch=debian apt:desktop-base/sid > gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... > gbp:info: Tag 11.0.2 not found, importing Debian tarball > gbp:info: Version '11.0.2' imported under '/home/user/src/desktop-base' > --- > gbp/config.py | 6 ++ > gbp/scripts/import_dsc.py | 14 -- > 2 files changed, 14 insertions(+), 6 deletions(-) > > diff --git a/gbp/config.py b/gbp/config.py > index 1ca8defd..d9e7c57e 100644 > --- a
Bug#984516: [git-buildpackage/master] import-dsc: Fix error message when missing debian branch
tag 984516 pending thanks Date: Thu Mar 4 21:23:48 2021 +0700 Author: Arnaud Rebillout Commit ID: abce93c865b6592aaa3940bde7db776af8e98604 Commit URL: https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=abce93c865b6592aaa3940bde7db776af8e98604 Patch URL: https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=abce93c865b6592aaa3940bde7db776af8e98604 import-dsc: Fix error message when missing debian branch The error message mistakenly talks about the upstream branch when it should be talking about the debian branch. Logs: # initial failure $ gbp import-dsc apt:desktop-base/sid gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... gbp:info: Tag 11.0.2 not found, importing Debian tarball gbp:error: Repository does not have branch 'master' for upstream sources. If there is none see file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT on howto create it otherwise use --upstream-branch to specify it. Also check the --create-missing-branches option. # trying as suggested $ gbp import-dsc --upstream-branch=debian apt:desktop-base/sid gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... gbp:info: Tag 11.0.2 not found, importing Debian tarball gbp:error: Repository does not have branch 'master' for upstream sources. If there is none see file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT on howto create it otherwise use --upstream-branch to specify it. Also check the --create-missing-branches option. # in fact it's the debian branch! $ gbp import-dsc --debian-branch=debian apt:desktop-base/sid gbp:info: Downloading 'desktop-base/sid' using 'apt-get'... gbp:info: Tag 11.0.2 not found, importing Debian tarball gbp:info: Version '11.0.2' imported under '/home/user/src/desktop-base' Closes: #984516
Bug#998645: git-buildpackage.zsh-completion: duplicated functions, leading to bogus completion
Hi,
On Fri, Nov 05, 2021 at 02:35:21PM +0100, Romain Porte wrote:
> Package: git-buildpackage
> Version: 0.9.23
> Severity: normal
> X-Debbugs-Cc: deb...@microjoe.org
>
> Dear Maintainer,
>
> The debian/git-buildpackage.zsh-completion is full of duplicated
> function implementations:
>
> $ cat debian/git-buildpackage.zsh-completion| grep -E '.*() {' | sort | uniq
> -c
> 2 _gbp() {
> 2 __gbp_branch_options() {
> 2 _gbp-buildpackage() {
> 2 _gbp-clone() {
> 2 __gbp_common_options() {
> 1 _gbp-config() {
> 2 _gbp-create-remote-repo() {
> 2 _gbp-dch () {
> 1 _gbp-export-orig() {
> 2 _gbp-import-dsc() {
> 2 _gbp-import-dscs() {
> 2 _gbp-import-orig() {
> 1 _gbp-import-ref() {
> 2 _gbp-pq() {
> 1 _gbp-pristine-tar() {
> 2 _gbp-pull() {
> 1 _gbp-push() {
> 1 _gbp-tag() {
> 2 __gbp_tag_format_options() {
> 2 __gbp_tag_sign_options() {
>
> In particular, the _gbp() function that is defined twice does define the
> `tag` subcommand in one of the implementations, but not in the other.
>
> This is leading to the following bogus completion behavior:
>
> * start a new zsh instance
> * type `gbp`
> * press to complete
> * the `tag` option is displayed
> * press again to select one of the options
> * the `tag` option dissapears and will never be suggested during the zsh
> session
>
> I feel that the duplication of the functions is not intentional and that
> it is the root cause of this behavior. The solution could be to remove
> the duplicate implementations, by keeping the most complete ones, in
> order to fix this issue.
I'm not a zsh user so I appreciate patches to improve zsh completion.
Cheers,
-- Guido
>
> BRs,
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages git-buildpackage depends on:
> ii devscripts 2.21.4
> ii git1:2.33.1-1
> ii man-db 2.9.4-2
> ii python33.9.7-1
> ii python3-dateutil 2.8.1-6
> ii python3-pkg-resources 58.2.0-1
> ii sensible-utils 0.0.17
>
> Versions of packages git-buildpackage recommends:
> ii pristine-tar 1.49
> ii python3-requests 2.25.1+dfsg-2
> ii sbuild0.81.2
>
> Versions of packages git-buildpackage suggests:
> pn python3-notify2
> ii sudo 1.9.5p2-3
> ii unzip6.0-26
>
> -- no debconf information
Bug#1011982: science-config: configuration file "90science-config" is missing semi-colon. Causes "unable to parse the config file" errors
Package: science-config
Version: 1.14.2
Severity: normal
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com
Dear Maintainer,
Using a tool like cupt results in warnings like
E: syntax error: line 8, character 1: expected: semicolon (';')
E: unable to parse the config file '//etc/apt/apt.conf.d/90science-config'
W: skipped the configuration file '//etc/apt/apt.conf.d/90science-config'
The contents of that file are:
/*
* APT configuration file for science-config package
*/
DPkg {
Post-Invoke {"test -f /var/run/science-config.usermenu && if [ -x
/usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus
science ; fi ; rm -f /var/run/science-config.usermenu";};
}
And it appears that indeed it is missing the semi-colon to end the DPkg scope.
The file should be
/*
* APT configuration file for science-config package
*/
DPkg {
Post-Invoke {"test -f /var/run/science-config.usermenu && if [ -x
/usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus
science ; fi ; rm -f /var/run/science-config.usermenu";};
};
Hope that helps.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-14-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages science-config depends on:
ii adduser3.118
ii blends-common 0.7.2
ii debconf [debconf-2.0] 1.5.77
ii menu 2.1.48
science-config recommends no packages.
science-config suggests no packages.
-- debconf information:
* science-config/group:
shared/science-config/useusermenus:
Bug#1011983: RFS: mutt-wizard/3.3-1~exp1 [ITP] -- Neomutt configuration from command line
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "mutt-wizard": * Package name: mutt-wizard Version : 3.3-1~exp1 Upstream Author : https://github.com/LukeSmithxyz/mutt-wizard/issues * URL : https://github.com/LukeSmithxyz/mutt-wizard * License : GPL-3 * Vcs : https://salsa.debian.org/debian/mutt-wizard Section : mail The source builds the following binary packages: mutt-wizard - Neomutt configuration from command line To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mutt-wizard/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mutt-wizard/mutt-wizard_3.3-1~exp1.dsc https://salsa.debian.org/nilsonfsilva/mutt-wizard Changes for the initial release: mutt-wizard (3.3-1~exp1) experimental; urgency=medium . * Initial release (Closes: #1009761) Regards, -- Josenilson Ferreira da SIlva
Bug#1011984: liblouis: CVE-2022-31783
Source: liblouis Version: 3.21.0-1 Severity: important Tags: security upstream Forwarded: https://github.com/liblouis/liblouis/issues/1214 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for liblouis. CVE-2022-31783[0]: | Liblouis 3.21.0 has an out-of-bounds write in compileRule in | compileTranslationTable.c, as demonstrated by lou_trace. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-31783 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31783 [1] https://github.com/liblouis/liblouis/issues/1214 [2] https://github.com/liblouis/liblouis/commit/ff747ec5e1ac54d54194846f6fe5bfc689192a85 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1011985: claws-mail: [backport request] for compatibility with gmail
Package: claws-mail Version: 3.17.8-1+b1 Severity: important X-Debbugs-Cc: okgomdjgbm...@gmail.com Dear Maintainer, Google is forcing OAUTH2 for use with gmail. The current stable version doesn't support that. You need 3.18 . So i'm making a backport request. 3.18/3.19 should be enough. Not been able to use gmail is quite a big flaw, this is why i'm giving it a severity of important.
Bug#1011078: chromium: arm64 package not available in bullseye-security
Hi Andres, On Fri, May 27, 2022 at 09:18:02PM -0400, Andres Salomon wrote: > I uploaded chromium-102 to bullseye-security, and I don't see armhf binary > packages. Salvatore, can you please tell me if that build failed? Sorry bit late, but yes it did fail the build. build log: https://people.debian.org/~carnil/buildd-logs/chromium/chromium_102.0.5005.61-1~deb11u1_armhf-2022-05-25T07:02:35Z.gz Regards, Salvatore
Bug#1011609: bogl-bterm: [PATCH] Several improvements
Hi,
Here is another small patch. Please see the commit message of the patch
for details. The merge request on salsa is also updated.
Best Regards,
Zhang BoyangFrom 36020995b989563efed3cfe6028cd93c192c0208 Mon Sep 17 00:00:00 2001
From: Zhang Boyang
Date: Sat, 28 May 2022 16:39:23 +0800
Subject: [PATCH] Fix rightmost pixel of each line not cleared by
bogl_vga16_text()
The bogl_vga16_clear() function use [x1, x2) as clear range, so there is
no need to minus x2 by 1.
---
bogl-vga16.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bogl-vga16.c b/bogl-vga16.c
index 6c2cbcf..3fcbe51 100644
--- a/bogl-vga16.c
+++ b/bogl-vga16.c
@@ -373,7 +373,7 @@ bogl_vga16_text (int xx, int yy, const char *s, int n, int fg, int bg, int ul,
{
int x2 = xx + bogl_metrics (s, n, font);
if (x2 >= bogl_xres)
- x2 = bogl_xres - 1;
+ x2 = bogl_xres;
bogl_vga16_clear (xx, yy, x2, yy + h, bg);
}
--
2.30.2
Bug#1011913: haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Control: reassign -1 haskell-devscripts Control: retitle -1 haskell-devscripts: DEB_ENABLE_TESTS ignored Control: affects -1 haskell-swish Quoting Lucas Nussbaum (2022-05-26 21:04:50) > During a rebuild of all packages in sid, [haskell-swish] failed to build > on amd64. [...] > > Running debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct > > Non-zero exit code 1. > > hlibrary.setup: No test suites enabled. Did you remember to configure with > > '--enable-tests'? haskell-swish built successfully when released in January, and contains this in debian/rules: > DEB_ENABLE_TESTS = yes Perhaps this really is bug#1010179 and the "fix" only papered over the underlying problem: @Scott, did you test packages _enabling_ tests or only the default of having tests disabled? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#987324: rust-hashbrown: missing ahash feature makes building hashlink crate impossible
Package rust-ahash is now in Debian, which should help fix this bug. - Jonas I looked but the new packages don't seem to be installable. 2 binary packages have unsatisfiable dependencies high The dependencies of librust-ahash+compile-time-rng-dev=0.7.6-3 cannot be satisfied in unstable on amd64 because: unsatisfied dependency on librust-const-random-0.1+default-dev (>= 0.1.12) | librust-const-random-0.1+default-dev (>= 0.1.12) The dependencies of librust-ahash-dev=0.7.6-3 cannot be satisfied in unstable on amd64 because: unsatisfied dependency on librust-atomic-polyfill-0.1+default-dev
Bug#1011988: Package: installation-reports
Package: installation-reports Boot method: USB netinstall Legacy mode Image version: firmware-11.3.0-amd64-netinst.iso Date: May 27 2022 . 9am Pacific time Machine: HP Z840 Workstation Processor: Intel Xeon E5-2697 v3 x2 Memory: 62.81 GiB Partitions: root@z840d11-3:~# df -Tl Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs 32906668 0 32906668 0% /dev tmpfs tmpfs 6586280 2504 6583776 1% /run /dev/sde7 ext4 47745772 8800748 36487220 20% / tmpfs tmpfs 32931388 0 32931388 0% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock /dev/sde6 ext4 185880456 114483720 62855036 65% /home tmpfs tmpfs 6586276 932 6585344 1% /run/user/1000 Output of lspci -knn (or lspci -nn): $ lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 [8086:2f00] (rev 02) Subsystem: Hewlett-Packard Company Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 [103c:2129] 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1 [8086:2f02] (rev 02) Kernel driver in use: pcieport 00:01.1 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1 [8086:2f03] (rev 02) Kernel driver in use: pcieport 00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 2 [8086:2f04] (rev 02) Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3 [8086:2f08] (rev 02) Kernel driver in use: pcieport 00:05.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Address Map, VTd_Misc, System Management [8086:2f28] (rev 02) 00:05.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Hot Plug [8086:2f29] (rev 02) 00:05.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 RAS, Control Status and Global Errors [8086:2f2a] (rev 02) 00:05.4 PIC [0800]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC [8086:2f2c] (rev 02) Subsystem: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC [8086:] 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR [8086:8d7c] (rev 05) Subsystem: Hewlett-Packard Company C610/X99 series chipset SPSR [103c:2129] 00:11.4 RAID bus controller [0104]: Intel Corporation C610/X99 series chipset sSATA Controller [RAID mode] [8086:2827] (rev 05) DeviceName: sSATA Subsystem: Hewlett-Packard Company C610/X99 series chipset sSATA Controller [RAID mode] [103c:2129] Kernel driver in use: ahci Kernel modules: ahci 00:14.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB xHCI Host Controller [8086:8d31] (rev 05) Subsystem: Hewlett-Packard Company C610/X99 series chipset USB xHCI Host Controller [103c:2129] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation C610/X99 series chipset MEI Controller #1 [8086:8d3a] (rev 05) Subsystem: Hewlett-Packard Company C610/X99 series chipset MEI Controller [103c:2129] Kernel driver in use: mei_me Kernel modules: mei_me 00:16.3 Serial controller [0700]: Intel Corporation C610/X99 series chipset KT Controller [8086:8d3d] (rev 05) Subsystem: Hewlett-Packard Company C610/X99 series chipset KT Controller [103c:2129] Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I218-LM [8086:15a0] (rev 05) DeviceName: LAN (AMT) Subsystem: Hewlett-Packard Company Ethernet Connection (2) I218-LM [103c:2129] Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 [8086:8d2d] (rev 05) Subsystem: Hewlett-Packard Company C610/X99 series chipset USB Enhanced Host Controller [103c:2129] Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: Intel Corporation C610/X99 series chipset HD Audio Controller [8086:8d20] (rev 05) DeviceName: HD Audio Subsystem: Hewlett-Packard Company C610/X99 series chipset HD Audio Controller [103c:2129] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 [8086:8d10] (rev d5) Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 [8086:8d16] (rev d5) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation C610/X99 series chipset PCI Express Root Port #5 [8086:8d18] (rev d5) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset
Bug#1011989: FTBFS: : commitBuffer: invalid argument (invalid character)
Source: haskell-tasty-lua Version: 0.2.2-2 Severity: serious Tags: ftbfs Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 haskell-tasty-lua fails to build from source: Running debian/hlibrary.setup register --builddir=dist-ghc --gen-pkg-config --verbose=verbose+nowrap Non-zero exit code 1. /usr/bin/ghc --abi-hash -fbuilding-cabal-package -O -outputdir dist-ghc/build -odir dist-ghc/build -hidir dist-ghc/build -stubdir dist-ghc/build -i -idist-ghc/build -isrc -idist-ghc/build/autogen -idist-ghc/build/global-autogen -Idist-ghc/build/autogen -Idist-ghc/build/global-autogen -Idist-ghc/build -optP-include -optPdist-ghc/build/autogen/cabal_macros.h -this-unit-id tasty-lua-0.2.2-F8d0iSXAcfI2gsDTgxUog4 -hide-all-packages -Wmissing-home-modules -no-user-package-db -XHaskell2010 Test.Tasty.Lua Test.Tasty.Lua.Core Test.Tasty.Lua.Module Test.Tasty.Lua.Translate -Wall -optl-Wl,-z,relro name: tasty-lua version: 0.2.2 visibility: public id: tasty-lua-0.2.2-F8d0iSXAcfI2gsDTgxUog4 key: tasty-lua-0.2.2-F8d0iSXAcfI2gsDTgxUog4 license: MIT copyright:: commitBuffer: invalid argument (invalid character) make: *** [/usr/share/cdbs/1/class/hlibrary.mk:172: install/libghc-tasty-lua-dev] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKSLcwACgkQLHwxRsGg ASGpIRAApbsNdoKG4wARtWZHUz9jylBYKjC/MvsMuWcH+WLevQNA1O4EWRnvPDBQ MLUOMRM2MjpyF11dTRNGLHHdm6Er4xxRN3FrSJ8ZUul3qtTAYczGVAk6GJ3kRYz+ GJ4Tr5VIJZYsVC8R7OZykxmaVJA1IIMQemGiAdSYRHSyfODUsKuRZXPLMFzqpOZU Z79V4rz9uhnBQvDqGpbTc67vhTyBKFVjupTx+nlpYmAsn7h2qvN/zeikoe8KXy9n ctxTX8Yfi7UGHXBF21tOHNfmLEKzq6RCw3ebV+ObYkt4YJb7HOLlzSOjCnA71e8H Su8+kdExGdTOv+OSDxEIdhgkE8oT5tlFgtVf6WvHG7PPsyn6AYw8y+bf4q/zbO8t RXGZLWJuVGmOINC3nRabVmIDlyBaNtQf81ZYc9ZfptXaCZw/clu0u4RgcSoZlTd4 uibOM2C3hL1UZTwm87dEVgZjvaDIS0Q0bvevYaQLB0rfbaxo+uEy/Pphd8kKWs/e saNQb1vui7UhYzzEwePf3pDoi4/Lo3n7/73i4HZPtPLejxSZv6peS6ylp6MUsPm4 pAyYT5fVzVCwgrRwBdOfYtkU8CxY9czvTMA7+s4ojJpz0am8ORhypgC1yhoKpp7p 6jOVSC6BenRIzhsxC663Iv7LpmGj/PTEVd/uOHrYM3+T32InhDE= =F/Hz -END PGP SIGNATURE-
Bug#987324: rust-hashbrown: missing ahash feature makes building hashlink crate impossible
Quoting peter green (2022-05-28 14:49:00) > > Package rust-ahash is now in Debian, which should help fix this bug. > > > > - Jonas > > > I looked but the new packages don't seem to be installable. > > > 2 binary packages have unsatisfiable dependencies high > > > > The dependencies of librust-ahash+compile-time-rng-dev=0.7.6-3 cannot > > be satisfied in unstable on amd64 because: unsatisfied dependency on > > librust-const-random-0.1+default-dev (>= 0.1.12) | > > librust-const-random-0.1+default-dev (>= 0.1.12) > > The dependencies of librust-ahash-dev=0.7.6-3 cannot be satisfied in > > unstable on amd64 because: unsatisfied dependency on > > librust-atomic-polyfill-0.1+default-dev > > Yeah - as you know (since you filed the bugreport), all packages involving librust-once-cell-dev currently fails to build from source due to bug#1011645 :-( I meant to say that the availability of the package is a step towards this bugreport getting fixed - not that it was possible to fix right now. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1005873: [git-buildpackage/master] pq: Check if repo is clean before importing patches
Control: severity -1 serious
Hi,
On Thu, 17 Feb 2022 10:30:31 + Ian Jackson
wrote:
Sean Whitton writes ("Bug#1005873: [git-buildpackage/master] pq: Check if repo is
clean before importing patches"):
> On Wed 16 Feb 2022 at 02:39PM +01, Andrej Shadura wrote:
> > gbp:error: Use --ignore-new to ignore.
> > dgit: failed command: sh -ec 'exec >/dev/null; exec "$@"' x gbp pq import
>
> Sounds like dgit should start passing --ignore-new in this case?
Well, maybe. If done via the command line, dgit ought to do some kind
of dance to work with old gbp, which compplicates matters. But maybe
dgit should provide a .git/gbp.conf in the playtree, which could be
used to override any other troublesome settings.
The difficulty here is just the .pc directory. Perhaps dgit ought to
remove it or move it aside, before running gbp pq.
If we did that then we might want to explicitly *enable* the new
checks.
Seems like the autopkgtest of dgit is now blocking progression of
git-buildpackage related to this change.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1011570: O: libcaca -- development files for libcaca
Hi, I started to prepare a small QA upload, I don't have a big time so I would prefer another maintainer to adopt it, in the meantime if no one comes forward I will do a first small QA upload with security fixes and some other small things and if I'll have enough time in the next weekends a bigger one with packaging improvements and with the new upstream version. the actual git in salsa (https://salsa.debian.org/debian/libcaca) is only an auto import not full, one small additional commit and without pristine-tar, I redid full import using pristine-tar: https://salsa.debian.org/fantu/libcaca I think is good replace itwith the one I created for a "better" starting repository. OpenPGP_signature Description: OpenPGP digital signature
Bug#1011990: pappl: autopkgtest regression: fails on output to stderr
Source: pappl
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of pappl the autopkgtest of pappl fails in testing
when that autopkgtest is run with the binary packages of pappl from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
pappl from testing1.2.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. The test
itself seems to pass, but there's output to stderr. Output to stderr is
by default treated as failure by autopkgtest, unless the allow-stderr
restriction is set.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pappl
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pappl/22174962/log.gz
testsuiteFAIL stderr: Starting tests...
autopkgtest [18:13:16]: test testsuite: - - - - - - - - - - stderr - -
- - - - - - - -
Starting tests...
api: papplSystemFindLoc('de'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Ein Drucker mit diesem Namen existiert bereits.')
api: papplSystemFindLoc('en'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'A printer with that name already exists.')
api: papplSystemFindLoc('es'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Una impresora con ese nombre ya existe.')
api: papplSystemFindLoc('fr'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Une imprimante avec ce nom existe déjà.')
api: papplSystemFindLoc('it'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Una stampante con quel nome esiste già.')
api: papplSystemFindLoc('ja'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got '既に存在している名前のプリンター。')
api: papplSystemFindLoc('zz'): PASS (got NULL)
api: papplLocGetString('A printer with that name already exists.'): PASS
(got key string)
api: papplSystemGetAdminGroup: PASS
api: papplSystemGet/SetAdminGroup('admin-0'): PASS
api: papplSystemGet/SetAdminGroup('admin-1'): PASS
api: papplSystemGet/SetAdminGroup('admin-2'): PASS
api: papplSystemGet/SetAdminGroup('admin-3'): PASS
api: papplSystemGet/SetAdminGroup('admin-4'): PASS
api: papplSystemGet/SetAdminGroup('admin-5'): PASS
api: papplSystemGet/SetAdminGroup('admin-6'): PASS
api: papplSystemGet/SetAdminGroup('admin-7'): PASS
api: papplSystemGet/SetAdminGroup('admin-8'): PASS
api: papplSystemGet/SetAdminGroup('admin-9'): PASS
api: papplSystemGet/SetAdminGroup(NULL): PASS
api: papplSystemGetContact: PASS
api: papplSystemGet/SetContact('Admin 0'): PASS
api: papplSystemGet/SetContact('Admin 1'): PASS
api: papplSystemGet/SetContact('Admin 2'): PASS
api: papplSystemGet/SetContact('Admin 3'): PASS
api: papplSystemGet/SetContact('Admin 4'): PASS
api: papplSystemGet/SetContact('Admin 5'): PASS
api: papplSystemGet/SetContact('Admin 6'): PASS
api: papplSystemGet/SetContact('Admin 7'): PASS
api: papplSystemGet/SetContact('Admin 8'): PASS
api: papplSystemGet/SetContact('Admin 9'): PASS
api: papplSystemGetDefaultPrinterID: PASS (1)
api: papplSystemSetDefaultPrinterID(2): PASS
api: papplSystemSetDefaultPrinterID(1): PASS
api: papplSystemGetDefaultPrintGroup: PASS
api: papplSystemGet/SetDefaultPrintGroup('users-0'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-1'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-2'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-3'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-4'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-5'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-6'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-7'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-8'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-9'): PASS
api: papplSystemGet/SetDefaultPrintGroup(NULL): PASS
api: papplSystemGetDNSSDName: PASS
api: papplSystemGet/SetDNSSDName('System Test A'): PASS
api: papplSystemGet/SetDNSSDName('System Test B'): PASS
api: papplSystemGet/SetDNSSDName('System Test C'): PASS
api: papplSystemGet/SetDNSSDName('System Test D'): PASS
api: papplSystemGet/SetDNSSDName('System Test E'): PASS
api: papplSystemGet/SetDNSSDName('System Test F'): PASS
api: papplSystemGet/SetDNSSDName('System Test G'): PASS
api: papplSystemGet/SetDNSSDName('System Test H'): PASS
api: papplSystemGet/SetDNSSDName('System Test I'): PASS
api: papplSystemGet/SetDNSSDName('System Test J'): PASS
api: papplSystemGet/SetDNSSDName(NULL): PASS
api: papplSystemGetFooterHTML: PASS
api: papplSystemSetFooterH
Bug#1011991: RM: libgnatcoll-python -- ROM; NPOASR; temporary package not needed anymore
Package: ftp.debian.org
Severity: normal
Control: unblock 936624 by 936869
Hello.
Please remove these packages from unstable:
libgnatcoll-python:src
libgnatcoll-python19
libgnatcoll-python19-dev
I am the maintainer of libgnatcoll-bindings and libgnatcoll-python.
The normal situation is that
the libgnatcoll-bindings source package produces
libgnatcoll-${COMPONENT}{SOVERSION} and
libgnatcoll-${COMPONENT}{ALIVERSION}-dev
for various COMPONENTs including python.
A few years ago, the python component was ready for both python2&3,
but its only reverse dependency gnat-gps was requiring python2.
As a temporary measure, the separate libgnatcoll-python source package
was introduced. This allowed the other components to be updated in
testing, while the python(2) component and gnat-gps were RC-buggy in
unstable (#936869 and #936624 respectively).
Nowadays
* gnat-gps has been RC-buggy for a while.
It depends on libgnatcoll-python18 that no one is building anymore.
* If/when we manage to rebuild gnat-gps, latest upstream version is
ready for python3. Hence the unblock command above.
There is no need for a separate package anymore, so
libgnatcoll-bindings builds the python(3) component again.
libgnatcoll-python3.1
libgnatcoll-python3.1-dev
These fully replace the removed packages.
Thanks.
Bug#1011992: ftbfs: : commitBuffer: invalid argument (invalid character)
Source: haskell-hslua-module-text Version: 0.2.1-2 Severity: serious Tags: ftbfs Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 haskell-hslua-module-text fails to build from source: Running debian/hlibrary.setup register --builddir=dist-ghc --gen-pkg-config --verbose=verbose+nowrap Non-zero exit code 1. /usr/bin/ghc --abi-hash -fbuilding-cabal-package -O -outputdir dist-ghc/build -odir dist-ghc/build -hidir dist-ghc/build -stubdir dist-ghc/build -i -idist-ghc/build -isrc -idist-ghc/build/autogen -idist-ghc/build/global-autogen -Idist-ghc/build/autogen -Idist-ghc/build/global-autogen -Idist-ghc/build -optP-include -optPdist-ghc/build/autogen/cabal_macros.h -this-unit-id hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 -hide-all-packages -Wmissing-home-modules -no-user-package-db -XHaskell2010 Foreign.Lua.Module.Text -optl-Wl,-z,relro name: hslua-module-text version: 0.2.1 visibility: public id: hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 key: hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 license: MIT copyright:: commitBuffer: invalid argument (invalid character) make: *** [/usr/share/cdbs/1/class/hlibrary.mk:172: install/libghc-hslua-module-text-dev] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKSMbIACgkQLHwxRsGg ASFndw/+M6U4U1Khb4eTbWPYpgKX/zQi9JvMs0yEnLhHrZVQRj+yr7X0LzLTv8Sp rjfT484Xp14nZrjd1qg6FnYCV4EEBBOmT4RBZP8+k1QwZZlLeOU4cOHmbdn6lK+p vgw8sOukuy00V6Y6Xupqvauh9OsQah7ORwxGqUsGtlrChMxEf58D/u2553598Cib RDfEUD89CbdtVbdrhQCRDjbgnpFwQSUIc/DtTbsUmqW41+nBoWTBn4PeZaX4pRd9 ZNjmweRoGVEdAVBs/cGHLmxjckyNfs0t4j+g1wAiRen34cn9pMR77kQAu2LVlPHZ LYuxfqxw5ysAkllymoSmX3OthoLiZWXQwCfROQ0/NkY9+u0PfoCL063RuHlE0Fk6 wAJdZIHJeCtgM1dxB9D6Pt4URAnaXmtKk8Lg8bm+EOcCDcO6vl0BxL85hB+f949V 0CHeAcSmtdz1RhMtPWM64iY67d5/3F65XZ41hVs4QoTE7y2RcWGgruXzYq2jyB6z qnpR22hf7qWg/LiegqyXoze+MndoHyl9M1kZX0AFCTi6+q95qtEROHof+N7XLhAD oqFeBxIkdRXeaTkcdcsbkZUiyz2IqgbxUK/aTKLC5IItq5Z5TV+x8GtdqwjDXlVQ Cm7fb56x4dZ2ynzUeVAdHxAYpq1rtNzk36UGRLOVamEpxHK1UMA= =ytyU -END PGP SIGNATURE-
Bug#1011993: ITP: ros2-rosidl -- ROS 2 IDL support
Package: wnpp Severity: wishlist X-Debbugs-Cc: roehl...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Subject: ITP: ros2-rosidl -- ROS 2 IDL support Package: wnpp Owner: Timo Röhling Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org * Package name: ros2-rosidl Version : 3.2.0 Upstream Author : Open Source Robotics Foundation, Inc * URL : https://github.com/ros2/rosidl * License : Apache-2 Programming Lang: Python, C++, C Description : ROS 2 IDL support This package is part of ROS 2, the Robot Operating System. ROS 2 uses the OMG Data Distribution Standard (DDS) as middleware layer, which in turn relies on the Interface Definition Language (IDL) to define the messages which can be exchanged between ROS network participants. ROS has (for historical reasons) its own message definition format; the ROS 2 IDL support layer is responsible for transforming the ROS message format to the IDL format. The package will be team-maintained under the umbrella of Debian Robotics Team at https://salsa.debian.org/robotics-team/ros2-idl -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmKSNFkACgkQ+C8H+466 LVlGSAwArVevcasUnX+wZrOCaXZNbjvtok83O2aGt16COnxZLbN8z95ySPW+M8LO uKcmvFsRLlk+1IvD/0EwL523Qr177sjyerYAPehVFh19Zgch5Y+IU3MgDcOFgGvM BTIpPts13KUDA5nfnUZ+KTEYGcapUOHypynQ5LiHJiUCZ5btgnAAFVlO1HKd7I1X aqGcWLmL0Wa/qRFobe/gVTboS9/n7H8flSKQexdJemUzhHHr6eos93Tm1eDWr9V8 SMaiq8UYRy4QNtVpYP10IZNiKg3RPO2HYHgfMFicCvQG2VRM7bS9uGL4c9bcbZ1z 1YASISOp7+qyWhvYOX55kJbp3rIRoiVCmk+/94N2FE6HepZo7RrSlupbVYDYjJv8 RCgQBBpJx1Lrz8lUsJlhOfksKU2f6CVmlLp3JBl0MLggGw5vGRhjOE1ckH8Ms3vh aaK2nabbtPhy5TpU4ypQ1UEyvt09i2GtnM/t6al3q7hjErrzUF8IPml2oY1Ieda7 o0f1jkCA =B/hL -END PGP SIGNATURE-
Bug#879495: [git-buildpackage/master] dch: Don't crash when we fail to get an upstream version
tag 879495 pending thanks Date: Sat May 28 16:40:48 2022 +0200 Author: Guido Günther Commit ID: 14170d60f173e3df2923e1fd1a9ab36860ce2c1b Commit URL: https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=14170d60f173e3df2923e1fd1a9ab36860ce2c1b Patch URL: https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=14170d60f173e3df2923e1fd1a9ab36860ce2c1b dch: Don't crash when we fail to get an upstream version Closes: #879495
Bug#995636: transition: openssl
Hi On 2022-05-27 15:36:53 +0200, Kurt Roeckx wrote: > On Thu, May 26, 2022 at 06:26:57PM +0200, Sebastian Ramacher wrote: > > > > That leaves #1011051. What's your view on that bug? > > So my understanding is that 1.1.1 doesn't understand the new > configuration file and tries to load an engine (instead of a > provider). > > We could ship a file that's comptabile with 1.1.1. That would make it > a little bit harder to load some providers by default, but maybe that's > something you want to do per application anyway. If that works, let's do that. Otherwise I'd fear that the only other options are openssl breaking libssl1.1 or renaming /etc/ssl/openssl.cnf to have a version specific name. Given the high number reverse dependencies involved in this transition (and also those depending on bin:openssl), I'd prefer to avoid a Breaks that could have the potential to force the libssl1.1 -> libssl3 upgrade to be more of a lockstep transition than needed. Best Sebastian -- Sebastian Ramacher
Bug#801429: ebook-tools: diff for NMU version 0.2.2-4.2
Control: tags 801429 + patch
Control: tags 801429 + pending
Dear maintainer,
I've prepared an NMU for ebook-tools (versioned as 0.2.2-4.2) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru ebook-tools-0.2.2/debian/changelog ebook-tools-
0.2.2/debian/changelog
--- ebook-tools-0.2.2/debian/changelog 2022-05-16 13:00:40.0 -0400
+++ ebook-tools-0.2.2/debian/changelog 2022-05-28 10:43:26.0 -0400
@@ -1,3 +1,11 @@
+ebook-tools (0.2.2-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop manual -dbg package in favor of automatic -dbgsym package.
+(Closes: #801429)
+
+ -- Boyuan Yang Sat, 28 May 2022 10:43:26 -0400
+
ebook-tools (0.2.2-4.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru ebook-tools-0.2.2/debian/control ebook-tools-0.2.2/debian/control
--- ebook-tools-0.2.2/debian/control2022-05-16 12:59:07.0 -0400
+++ ebook-tools-0.2.2/debian/control2022-05-28 10:41:53.0 -0400
@@ -32,21 +32,6 @@
.
This package provides the main epub library.
-Package: ebook-tools-dbg
-Section: debug
-Architecture: any
-Priority: extra
-Depends: libepub0 (= ${binary:Version}), ${misc:Depends}
-Description: library and tools to work with the EPUB file format - debug
symbols
- The ebook-tools provide ways for accessing and converting different
- ebook file formats.
- .
- This C library is free and portable. It includes methods to parse
- EPUB files and extract their contents.
- .
- This package provides the debug symbols for the epub library and the
- utilities.
-
Package: epub-utils
Section: graphics
Architecture: any
diff -Nru ebook-tools-0.2.2/debian/rules ebook-tools-0.2.2/debian/rules
--- ebook-tools-0.2.2/debian/rules 2022-05-16 12:59:07.0 -0400
+++ ebook-tools-0.2.2/debian/rules 2022-05-28 10:42:38.0 -0400
@@ -11,6 +11,6 @@
dh_install --fail-missing
override_dh_strip:
- dh_strip --dbg-package=ebook-tools-dbg
+ dh_strip --dbgsym-migration='ebook-tools-dbg (<< 0.2.2-4.1~)'
.PHONY: override_dh_auto_test
signature.asc
Description: This is a digitally signed message part
Bug#1011937: python-debian: Please consider moving deb822 to a standalone distro-independent Python package
Hi Stephan,
On Friday, 27 May 2022 20:09:29 AEST Jelmer Vernooij wrote:
> On Fri, May 27, 2022 at 12:01:17PM +0200, Stephan Lachnit wrote:
> > I'm not an expert on python-debian and I don't use other distros than
> > Debian, so I can only forward you some bug reports from
Thanks! I'd spotted one of these in the past but not others.
> > https://github.com/fsfe/reuse-tool/issues/466:
I'd definitely rather make python-debian more portable than have projects
forking bits of it into local vendored versions. Vendoring code creates
technical debt and is somewhat antithetical to the idea of making code more
reusable.
> > - https://github.com/fsfe/reuse-tool/issues/425: `apt_pkg.Error:
> > W:Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such
> > file or directory), E:Unable to determine a suitable packaging system
> > type`
As already noted, python-debian works fine without python-apt installed; the
unexpected situation here is that python-apt is installed but non-functional
in some way. I'm not sure whether the bug is really that a non-functional
python-apt is installed, but if we can work around it, then even better.
I have a feeling that we can change the way we use apt_pkg these days and that
we can avoid generating that error. I need to talk to the python-apt people
about that, but also I also need a way of reproducing an environment where a
non-functional python-apt is installed so that I can test this out.
From https://salsa.debian.org/python-debian-team/python-debian/-/
merge_requests/85
> > Since Alpine really doesn't offer anything, a lot of fail because of
> > missing `bin/ar`, which is an excellent test for a non-Debian-standard
> > environment. Not sure how this should be handled best though: maybe
> > something similar to the `have_apt_pkg` variable?
This is only the tests and in particular, it's making the test data -- ArFile
and DebFile are actually much more portable (except for the zstd compressed
.debs where there remain portability problems because of the requirement for a
zstd binary). It's only the tests that need the 'ar' binary and nothing in the
module code itself.
There's a few options here:
* require that ar be installed for the purposes of testing just as we do in
Debian; this is an explicit dependency in Debian, not something that happens
to be there because more batteries are included. The binutils package gives us
ar and is listed in debian/control, it's just that Python hasn't come up with
a way of expressing such dependencies in setup.py or similar. For alpine, ar
is in the binutils package and there are a few different versions available
for windows, such as via a gcc package from choco.
* use something else to make the .deb files for the test suite. I could imagine
a fallback for missing ar(1) that uses a pure python ar implementation that
can be installed via pip on these other platforms. The arpy module can't make
ar files at present which is a shame; the `unix_ar` or `ar` modules look
promising for that, there might be others.
https://github.com/getninjas/unix_ar
https://github.com/vidstige/ar
* skip the tests that need ar; in practice, that's probably all the tests from
debian/tests/test_debfile.py, and so a module level skip might be appropriate,
with something like
```
pytestmark = pytest.mark.skipif(not shutil.which("ar"), reason="...")
```
I'm cautious about automatically skipping tests because that's a route to non-
determinism, accidentally skipping tests, and therefore missing problems.
However, we do that for python-apt already, so there's precedent already in
the code; I'd be fine with that as a short term solution in advance of
something better.
Thanks in advance for your contribution to python-debian :)
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#1011957: aideinit fails in amanda-server processing
Hi Barry, On Fri, May 27, 2022 at 04:29:54PM -0500, Barry Trent wrote: > *** disklist > zmoby.atcorp.com / comp-root-tar > > symposium.atcorp.com / comp-root-tar > symposium.atcorp.com /bbbcomp-root-tar > moby.atcorp.com / comp-root-tar > coelacanth.atcorp.com / comp-root-tar > sawfish.atcorp.com / comp-root-tar > sawfish.atcorp.com /varcomp-root-tar Is there an empty line in the disklist file? If so, can you please remove this line and try again? Best regards Hannes
Bug#879495: gbp dch fails with UnboundLocalError
Hi, On Tue, Apr 03, 2018 at 08:52:06AM +0200, Didier 'OdyX' Raboud wrote: > Le mardi, 7 novembre 2017, 10.00:01 h CEST Guido Günther a écrit : > > Can you point me to a repo where I can reproduce this? > > I just did that: > > git clone https://salsa.debian.org/printing-team/cups.git > cd cups > # Let the upstream/latest branch exist > git checkout upstream/latest > # Put debian/master to a commit that triggers the bug > git checkout debi an/master > git reset --hard 7210eeb6f1d0d99cb008a4567127b7762a29f5a7 > gbp dch --release --verbose I can reproduce with that, thanks! The issue is $ 'git' 'describe' '--match' 'upstream/*' '--abbrev=0' '7210eeb6f1d0d99cb008a4567127b7762a29f5a7' warning: tag 'upstream/2.2.6' is externally known as 'v2.2.6' v2.2.6-4879-g7210eeb6f1d0d99cb008a4567127b7762a29f5a7 There's a long explanation how this comes about: https://github.com/git/git/commit/ff165f00c1065d94c0bcab8708364e6dc5655f5d I changed the code to not crash on that anymore. Cheers, -- Guido > gbp:debug: ['git', 'rev-parse', '--show-cdup'] > gbp:debug: ['git', 'rev-parse', '--is-bare-repository'] > gbp:debug: ['git', 'rev-parse', '--git-dir'] > gbp:debug: ['git', 'symbolic-ref', 'HEAD'] > gbp:debug: ['git', 'show-ref', 'refs/heads/debian/master'] > gbp:debug: ['git', 'tag', '-l', 'debian/2.2.7-1'] > gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'debian/2.2.7-1^0'] > gbp:info: Found tag for topmost changelog version > '46e03e2adff54390721b1a725ab9a6472e2cba39' > gbp:debug: ['git', 'log', '--pretty=format:%H', > '46e03e2adff54390721b1a725ab9a6472e2cba39..HEAD', '--no-merges', '--'] > gbp:debug: ['git', 'merge-base', 'HEAD', 'upstream/latest'] > gbp:debug: ['git', 'describe', '--match', 'upstream/*', '--abbrev=0', > '18a1649286d8978552c6334934a23dc6efe5fc0d'] > gbp:debug: Found upstream version None. > gbp:debug: /usr/bin/dpkg ['--compare-versions'] [None, 'lt', '2.2.7-1'] > > The temporary workaround is to run: > $ git branch -d upstream/latest
Bug#1011996: Updating the ri-li Uploaders list
Source: ri-li Version: 2.0.1+ds2-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Stuart Teasdale has retired, so can't work on the ri-li package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#1010751: clone: handle -b optional branch specification in VCS-Git
Hi,
Thanks, makes sense, some comments:
On Sun, May 08, 2022 at 05:21:15PM +0200, Nicolas Boulenguez wrote:
> def vcs_git_url(pkg):
> +"""
> +Content of the latest available VCS-Git field, as a str.
> +None when the field is missing.
> +(url, branch) when the value specifies a branch with -b.
> +"""
I think we should always return a tuple and have branch = None when
there's no -b so we can also avoid the isinstance() below. It would also
be great to have a test (e.g. by just having a test that parses some
pre fetched apt output (so we don't need to run it in the tests).
Cheers,
-- Guido
> repos = {}
>
> out = apt_showsrc(pkg)
> -vcs_re = re.compile(r'(x-)?vcs-git:\s*(?P[^ ]+)$', re.I)
> +vcs_re = re.compile(r'(x-)?vcs-git:\s*(?P[^
> ]+)(\s*-b\s*(?P[^ ]+))?$', re.I)
> version_re = re.compile(r'Version:\s*(?P.*)$', re.I)
> end_re = re.compile(r'\s*$')
>
> @@ -58,6 +63,8 @@ def vcs_git_url(pkg):
> m = vcs_re.match(line)
> if m:
> repo = m.group('repo')
> +if m.group('branch'):
> +repo = (repo, m.group('branch'))
> continue
> m = version_re.match(line)
> if m:
> @@ -85,6 +92,9 @@ def repo_to_url(repo):
> 'https://salsa.debian.org/agx/git-buildpackage.git'
> >>> repo_to_url("github:agx/git-buildpackage")
> 'https://github.com/agx/git-buildpackage.git'
> +
> +None when VCS-Git is required but missing.
> +(url, branch) when VCS-Git specifies a branch with -b.
> """
> parts = repo.split(":", 1)
> if len(parts) != 2:
> @@ -167,6 +177,10 @@ def main(argv):
> source = repo_to_url(args[1])
> if not source:
> return 1
> +elif isinstance(source, tuple):
> +source, vcs_git_branch = source
> +else:
> +vcs_git_branch = None
>
> clone_to, auto_name = (os.path.curdir, True) if len(args) < 3 else
> (args[2], False)
> try:
> @@ -187,6 +201,10 @@ def main(argv):
> postclone = options.postclone
> (options, args) = parse_args(argv)
>
> +if vcs_git_branch not in (None, options.debian_branch):
> +gbp.log.warn(f'VCS-Git: -b {vcs_git_branch} overrides
> --debian-branch={options.debian_branch}')
> +options.debian_branch = vcs_git_branch
> +
> # Track all branches:
> if options.all:
> remotes = repo.get_remote_branches()
> --
> 2.30.2
>
Bug#1011994: Updating the ganglia-web Uploaders list
Source: ganglia-web Version: 3.7.5+debian-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Stuart Teasdale has retired, so can't work on the ganglia-web package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1011995: Updating the ganglia Uploaders list
Source: ganglia Version: 3.7.2-6 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Stuart Teasdale has retired, so can't work on the ganglia package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks.
Bug#1011336: neomutt: New upstream version available
On Fri, May 20, 2022 at 11:46:09AM +0200, Michael Prokop wrote: > Package: neomutt > Version: 20211029+dfsg1-1 > Severity: wishlist > > Hi, > > NeoMutt versions 2022-04-08, 2022-04-15 + 2022-04-29 got released > since the latest upload on 2021-12-11, would be nice to have a > recent version in Debian. :) Thanks for submitting this bug, I will update it tomorrow.
Bug#1011997: bvi: search&replace crashes
Package: bvi Version: 1.4.0-1+b3 bvi crashes every time I try to search&replace: $ bvi -c 's/x/y/' /usr/bin/bvi 0010 03 00 03 00 01 00 00 00 30 35 00 00 34 00 00 00 05..4... 0020 B8 35 01 00 00 00 00 00 34 00 20 00 09 00 28 00 .5..4. ...(. 0030 1C 00 1B 00 06 00 00 00 34 00 00 00 34 00 00 00 4...4... 0040 34 00 00 00 20 01 00 00 20 01 00 00 04 00 00 00 4... ... ... 0050 04 00 00 00 03 00 00 00 54 01 00 00 54 01 00 00 T...T... 0060 54 01 00 00 13 00 00 00 13 00 00 00 04 00 00 00 T... 0070 01 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 F0 25 01 00 F0 25 01 00 05 00 00 00 .%...%.. 0090 00 10 00 00 01 00 00 00 BC 2E 01 00 BC 3E 01 00 .>.. 00A0 BC 3E 01 00 CC 05 00 00 AC 64 00 00 06 00 00 00 .>...d.. 00B0 00 10 00 00 02 00 00 00 C4 2E 01 00 C4 3E 01 00 .>.. 00C0 C4 3E 01 00 00 01 00 00 00 01 00 00 06 00 00 00 .>.. 00D0 04 00 00 00 04 00 00 00 68 01 00 00 68 01 00 00 h...h... 00E0 68 01 00 00 44 00 00 00 44 00 00 00 04 00 00 00 h...D...D... 00F0 04 00 00 00 50 E5 74 64 BC EA 00 00 BC EA 00 00 P.td 0100 BC EA 00 00 C4 02 00 00 C4 02 00 00 04 00 00 00 0110 04 00 00 00 51 E5 74 64 00 00 00 00 00 00 00 00 Q.td 0120 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 00 0130 10 00 00 00 52 E5 74 64 BC 2E 01 00 BC 3E 01 00 R.td.>.. 0140 BC 3E 01 00 44 01 00 00 44 01 00 00 04 00 00 00 .>..D...D... 0150 01 00 00 00 2F 6C 69 62 2F 6C 64 2D 6C 69 6E 75 /lib/ld-linu 0160 78 2E 73 6F 2E 32 00 00 04 00 00 00 10 00 00 00 x.so.2.. Segmentation fault (core dumped) bytes Backtrace: #0 __GI___libc_realloc (oldmem=0x6f732e78, bytes=1) at malloc.c:3349 #1 0x565f108e in alloc_buf (n=6223891946776035329, buffer=0x578a5970) at io.c:451 #2 0x565ef515 in do_substitution (delim=, line=0xffa84b5e "x/y/", startpos=, endpos=0x578b9227 "") at re.c:352 #3 0x565ec5aa in docmdline (cmdline=0x565fb4e0 "s/x/y/") at comm.c:224 #4 0x565e8ce0 in main (argc=, argv=) at bvi.c:302 -- System Information: Architecture: i386 Versions of packages bvi depends on: ii libc62.33-7 ii libncurses6 6.3+20220423-2 ii libtinfo66.3+20220423-2 -- Jakub Wilk
Bug#1011761: vim: Vim ignores mouse= in global config
On Sat, May 28, 2022 at 04:45:43PM +0200, Helge Kreutzmann wrote: > On Fri, May 27, 2022 at 05:01:00PM -0400, James McCoy wrote: > > This is mentioned at the top of /etc/vim/vimrc: > > > > > > " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc. > > On my freshly installed machine (for root), $VIMRUNTIME is not set, $VIMRUNTIME is an internal variable Vim sets -- ":help $VIMRUNTIME". I can add an example value here to make it more obvious what the path is. > nor is there a "defaults.vim" neither below /etc nor /root. "dpkg -S defaults.vim" > If this is related to /usr/share/vim/vim82/defaults.vim, then this is > indeed not what I was looking for. Yes, it is what you're looking for, since that's what influences the behavior when there's no user vimrc. See ":help defaults.vim" and previous discussion in #842833. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1011998: Updating the doctorj Uploaders list
Source: doctorj Version: 5.0.0-6 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Paul Cupis has not been working on the doctorj package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1012000: O: python-pam -- Python interface to the PAM library
Package: wnpp The current maintainer of python-pam, Dima Barsky , has retired. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: python-pam Binary: python3-pam Version: 0.4.2-13.4 Maintainer: Dima Barsky Build-Depends: debhelper (>= 9), python3-all-dev, libpam0g-dev, dh-python Architecture: any Standards-Version: 4.5.0 Format: 1.0 Files: 0a71dd1cc992a3c02b2b0777e2fc80c2 1729 python-pam_0.4.2-13.4.dsc e6e78959da5482b9a1aea1171589dd16 15115 python-pam_0.4.2.orig.tar.gz 663bc2b64b4ca1dba193c9a2bea1d015 3808 python-pam_0.4.2-13.4.diff.gz Checksums-Sha256: 453b9c251b6cc6ff2d87214e842da4edad7fe448409034b78810478eeb362848 1729 python-pam_0.4.2-13.4.dsc 9ccce2e494c5869d99b20034fd40e368c35add4ef60ce3a33f5573c49a1e2edf 15115 python-pam_0.4.2.orig.tar.gz d6c467bf2858f3cff8b2c1e0a4da604a58f4f2e2560793da4f75590b1527 3808 python-pam_0.4.2-13.4.diff.gz Package-List: python3-pam deb python optional arch=any Directory: pool/main/p/python-pam Priority: source Section: python Package: python3-pam Source: python-pam (0.4.2-13.4) Version: 0.4.2-13.4+b3 Installed-Size: 70 Maintainer: Dima Barsky Architecture: amd64 Depends: python3 (<< 3.11), python3 (>= 3.9~), libc6 (>= 2.4), libpam0g (>= 0.99.7.1) Suggests: python3-pam-dbg Description: Python interface to the PAM library Description-md5: 4bae7680ea768021b6726c1ec6ac6cb8 Section: python Priority: optional Filename: pool/main/p/python-pam/python3-pam_0.4.2-13.4+b3_amd64.deb Size: 12236 MD5sum: 432f0888c6851365091e151153616be3 SHA256: aae55da67f621ac1ff4bcdf9828b4b0908b02cecf3b9679a64a30ef86289aaf1 -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1011999: Updating the esniper Uploaders list
Source: esniper Version: 2.35.0+git20190805.7930bb4-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Dima Barsky has retired, so can't work on the esniper package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1011078: chromium: arm64 package not available in bullseye-security
reopen 1011078 thanks ./../base/allocator/partition_allocator/base/sys_byteorder.h:66:12: note: non-constexpr function 'ByteSwap' cannot be used in a constant expression Hah, because of course chromium has multiple copies of the same broken header file. I'll fix it (again) in the next upload. Thank you! On Sat, May 28, 2022 at 14:04, Salvatore Bonaccorso wrote: Hi Andres, On Fri, May 27, 2022 at 09:18:02PM -0400, Andres Salomon wrote: I uploaded chromium-102 to bullseye-security, and I don't see armhf binary packages. Salvatore, can you please tell me if that build failed? Sorry bit late, but yes it did fail the build. build log: https://people.debian.org/~carnil/buildd-logs/chromium/chromium_102.0.5005.61-1~deb11u1_armhf-2022-05-25T07:02:35Z.gz Regards, Salvatore
Bug#1012001: O: xwrits -- reminds you to take a break from typing
Package: wnpp The current maintainer of xwrits, Helen Faulkner , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: xwrits Binary: xwrits Version: 2.21-6.1 Maintainer: Helen Faulkner Build-Depends: debhelper (>= 7.1), perl (>= 5.6), texinfo (>= 4.2), libice-dev, libsm-dev, libx11-dev, libxext-dev, xutils-dev Architecture: any Standards-Version: 3.8.4 Format: 3.0 (quilt) Files: 471b7ca8da391e0dcc27e78b51f6daa9 1103 xwrits_2.21-6.1.dsc cb51e789f0e0c1e6ca147caee8e537da 133755 xwrits_2.21.orig.tar.gz de4e77b44faba73fe6590921ea771a0d 5016 xwrits_2.21-6.1.debian.tar.gz Checksums-Sha256: 889ffcaebd3ab57aece1f45dc071ed63ebde69ac6a6cb6e39afe05e1f1422bda 1103 xwrits_2.21-6.1.dsc e395aa843a290de5c15cfe58b696f017c3c85ae4aa9777b784b971679fa33954 133755 xwrits_2.21.orig.tar.gz 00a762ab5df624fae289e5533c1c11d0fae657d2a91b634c324d060fef9a84b8 5016 xwrits_2.21-6.1.debian.tar.gz Homepage: http://www.lcdf.org/~eddietwo/xwrits Directory: pool/main/x/xwrits Priority: source Section: x11 Package: xwrits Source: xwrits (2.21-6.1) Version: 2.21-6.1+b2 Installed-Size: 157 Maintainer: Helen Faulkner Architecture: amd64 Depends: libc6 (>= 2.14), libx11-6 Description: reminds you to take a break from typing Description-md5: 329763cc331c3d43b6697bb82118bea6 Homepage: http://www.lcdf.org/~eddietwo/xwrits Tag: hardware::input, implemented-in::c, interface::graphical, interface::x11, role::program, scope::utility, uitoolkit::xlib, use::timekeeping, x11::application Section: x11 Priority: optional Filename: pool/main/x/xwrits/xwrits_2.21-6.1+b2_amd64.deb Size: 93010 MD5sum: 8a94e9e253a8cb55d4d6a97bccde6284 SHA256: b7587541401d5d558416bbb4911350227166794e98d2e043e0a8301345e878b7 -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1011997: bvi: search&replace crashes
Am 28.05.2022 um 17:09 schrieb Jakub Wilk: Package: bvi Version: 1.4.0-1+b3 bvi crashes every time I try to search&replace: Thank you for reporting this bug! Please have a look if the upcoming version has already fixed the bug: https://puon.at/_tmp/bvi-1.4.2rc.src.tar.gz Gerhard Bürgmann
Bug#1012002: O: ssh-askpass-fullscreen -- Under Gnome2, asks user for a passphrase for ssh-add
Package: wnpp The current maintainer of ssh-askpass-fullscreen, Marco Presi (Zufus) , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: ssh-askpass-fullscreen Binary: ssh-askpass-fullscreen Version: 0.3-3.1 Maintainer: Marco Presi (Zufus) Build-Depends: debhelper (>= 7.0.50~), libgtk2.0-dev, cdbs, patchutils (>= 0.2.25), libx11-dev Architecture: any Standards-Version: 3.8.3 Format: 1.0 Files: 02b03607f87b431d7adebb3532acb798 1817 ssh-askpass-fullscreen_0.3-3.1.dsc c46ad80b6bb150270514317001a2cedc 10128 ssh-askpass-fullscreen_0.3.orig.tar.gz 241140fd0c18819e92d61e9344415320 5940 ssh-askpass-fullscreen_0.3-3.1.diff.gz Checksums-Sha256: 75e508a81d6d35e22e21753e7f30266c441a8ddae783f795ccfdb17d4c3074b1 1817 ssh-askpass-fullscreen_0.3-3.1.dsc 8a9b10c5a7374247fb03e5751e395f4f0cf03d1be45c09f8df678eedc713846b 10128 ssh-askpass-fullscreen_0.3.orig.tar.gz c1f34029444c5003f1066441b26097ba2311482377cfcbfd4659167591b1205d 5940 ssh-askpass-fullscreen_0.3-3.1.diff.gz Package-List: ssh-askpass-fullscreen deb x11 optional Directory: pool/main/s/ssh-askpass-fullscreen Priority: source Section: x11 Package: ssh-askpass-fullscreen Source: ssh-askpass-fullscreen (0.3-3.1) Version: 0.3-3.1+b3 Installed-Size: 50 Maintainer: Marco Presi (Zufus) Architecture: amd64 Provides: ssh-askpass Depends: libc6 (>= 2.2.5), libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.12.0), libgtk2.0-0 (>= 2.14.0), libx11-6 Description-en: Under Gnome2, asks user for a passphrase for ssh-add It does the same work that ssh-askpass and ssh-askpass-gnome do. It adds shadowing and looks more beautiful under Gnome2. Description-md5: aeb8e7c8b297ccd6c159abd6fc9a2b3f Tag: interface::graphical, interface::x11, protocol::ssh, role::program, scope::utility, security::authentication, uitoolkit::gtk, use::login, x11::application Section: x11 Priority: optional Filename: pool/main/s/ssh-askpass-fullscreen/ssh-askpass-fullscreen_0.3-3.1+b3_amd64.deb Size: 10340 MD5sum: c124f4b00eeb49647b9b0f8fe5d557a0 SHA256: 80a8f470238d0b8cd154a6f290cd5742996895cd6e9e1597e6c88feb263d349f signature.asc Description: PGP signature
Bug#993957: (no subject)
Control: tags 993957 moreinfo lkcl wrote... > schroot 1.6.10 (04 May 2014) fails with a continuous attempt to read > a non-existent subdirectory, /run/systemd/userdb, when operating a > type "directory" schroot. > > a type "plain" does not have this same issue. > > creating the missing subdirectory manually "allows" the schroot to "proceed" > without errors. As asked earlier, please provide more details about your setup, also the schroot.conf snippet. Since I couldn't reproduce your issue here, but based on the few information avaiable I might have done things slightly different. From reading the Ubuntu bug (also #763896) I assume this was fixed upstream, we'll include that commit in the next uploads. Christoph signature.asc Description: PGP signature
Bug#1011761: vim: Vim ignores mouse= in global config
Hello James, thanks for the quick response and the explanation! Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#1011168: linux-image-5.17.0-2-amd64: rebooting KVM guest crashes kernel
Still happens with the new v5.17.11 kernel package, in fact it may have gotten worse because at one point the box crashed shortly after starting a guest VM: [ 2256.562873] BUG: kernel NULL pointer dereference, address: 000b [ 2256.585773] #PF: supervisor write access in kernel mode [ 2256.602946] #PF: error_code(0x0002) - not-present page [ 2256.619832] PGD 0 P4D 0 [ 2256.628138] Oops: 0002 [#1] PREEMPT SMP PTI [ 2256.641880] CPU: 15 PID: 3258 Comm: qemu-system-x86 Kdump: loaded Not tainted 5.17.0-3-amd64 #1 Debian 5.17.11-1 [ 2256.675643] Hardware name: Intel Corporation T5520UR/T5520UR, BIOS S5500.86B.01.00.0061.030920121535 03/09/2012 [ 2256.708831] RIP: 0010:kvm_replace_memslot+0xcf/0x390 [kvm] [ 2256.726925] Code: 44 24 08 48 85 db 0f 84 3b 02 00 00 48 89 ea 48 c1 e2 04 48 01 da 48 8b 4a 08 48 85 c9 74 1e 48 8b 32 48 89 31 48 85 f6 74 04 <48> 89 4e 08 48 c7 02 00 00 00 00 48 c7 42 08 00 00 00 00 48 8d 54 [ 2256.788713] RSP: 0018:b8dd467dfd70 EFLAGS: 00010206 [ 2256.805885] RAX: b8dd468518b8 RBX: 8b57b7598e00 RCX: b8dd46851af8 [ 2256.829350] RDX: 8b57b7598e00 RSI: 0003 RDI: b8dd46851000 [ 2256.852815] RBP: R08: 0001 R09: 0860 [ 2256.876279] R10: 000b R11: 0004 R12: [ 2256.899744] R13: R14: 0001 R15: b8dd46851000 [ 2256.923207] FS: 7f85ddf10640() GS:8b5d97bc() knlGS: [ 2256.949816] CS: 0010 DS: ES: CR0: 80050033 [ 2256.968704] CR2: 000b CR3: 000675c84004 CR4: 000226e0 [ 2256.992168] Call Trace: [ 2257.000193] [ 2257.007071] ? _raw_read_unlock+0x18/0x30 [ 2257.020245] kvm_set_memslot+0x3c2/0x4a0 [kvm] [ 2257.034888] kvm_vm_ioctl+0x2cb/0xd80 [kvm] [ 2257.048674] ? handle_mm_fault+0xb2/0x280 [ 2257.061848] __x64_sys_ioctl+0x82/0xb0 [ 2257.074164] do_syscall_64+0x3b/0xc0 [ 2257.085908] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2257.102511] RIP: 0033:0x7f85e12c0397 [ 2257.114249] Code: 3c 1c e8 1c ff ff ff 85 c0 79 87 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 da 0d 00 f7 d8 64 89 01 48 [ 2257.176038] RSP: 002b:7f85ddf0eea8 EFLAGS: 0246 ORIG_RAX: 0010 [ 2257.200933] RAX: ffda RBX: 4020ae46 RCX: 7f85e12c0397 [ 2257.224398] RDX: 7f85ddf0ef70 RSI: 4020ae46 RDI: 000c [ 2257.247861] RBP: 5643173201f0 R08: 0007 R09: 7f85d40e9ad0 [ 2257.271326] R10: fd00 R11: 0246 R12: 7f85ddf0ef70 [ 2257.294791] R13: 0100 R14: 564317dac470 R15: fd00 [ 2257.318258] [ 2257.325420] Modules linked in: nf_conntrack_netlink xfrm_user xfrm_algo br_netfilter bridge stp llc overlay autofs4 ip6_tables ip6t_rpfilter nft_chain_nat xt_MASQUERADE nf_nat xt_addrtype ip_tables xt_conntrack ipt_REJECT nf_reject_ipv4 nf_conntrack_tftp nf_conntrack_ftp xt_tcpudp ipt_rpfilter xt_CT nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables x_tables nfnetlink nfsd auth_rpcgss nfs_acl nfs lockd grace fscache netfs sunrpc jc42 vhost_vsock vmw_vsock_virtio_transport_common vsock vhost_net tun vhost vhost_iotlb tap ipmi_watchdog nbd squashfs loop dm_crypt dm_mod intel_powerclamp coretemp kvm_intel ipmi_ssif kvm irqbypass mgag200 ghash_clmulni_intel drm_shmem_helper drm_kms_helper aesni_intel cec crypto_simd acpi_ipmi cryptd rc_core ipmi_si intel_cstate iTCO_wdt intel_pmc_bxt iTCO_vendor_support ipmi_devintf drm evdev intel_uncore watchdog sg ipmi_msghandler ioatdma i5500_temp i7core_edac button acpi_cpufreq xfs libcrc32c crc32c_generic uas hid_generic sd_mod ses t10_pi [ 2257.325496] usbhid enclosure usb_storage crc_t10dif hid scsi_transport_sas crct10dif_generic ata_generic uhci_hcd ehci_pci megaraid_sas igb ata_piix ehci_hcd libata i2c_algo_bit dca crct10dif_pclmul crct10dif_common scsi_mod ptp i2c_i801 crc32_pclmul usbcore crc32c_intel i2c_smbus lpc_ich scsi_common usb_common pps_core [ 2257.706780] CR2: 000b -- Jon Doge Wrangler X(7): A program for managing terminal windows. See also screen(1) and tmux(1).
Bug#1010061: git-buildpackage: FTBFS on bookworm and sid: multiple issues
Hi Ian, On Wed, May 11, 2022 at 12:40:35PM +0100, Ian Jackson wrote: > Guido: > > These all make sense. Pushed, thanks! > > Would you mind doing an upload ? My grep-excuses is warning me about > autoremovals. > > If you don't have time I would be willing to do it myself from the > relevant git branch, but I certainly wouldn't want to do that without > coordinating with you... Thanks. I did an upload a while back but now dgit's tests fail: https://tracker.debian.org/pkg/git-buildpackage https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/22182444/log.gz Maybe you have an idea what has triggered this (not all of them look gbp related but looking at the tests many of them seem to pull in gbp): debpolicy-quilt-gbp FAIL non-zero exit status 16 TEST FAILED gbp-orig FAIL non-zero exit status 16 TEST FAILED overwrite-splitbrains FAIL non-zero exit status 16 TEST FAILED quilt-gbpFAIL non-zero exit status 16 + echo 'OPERATION FAILED' TEST FAILED quilt-gbp-build-modes FAIL non-zero exit status 16 TEST FAILED quilt-splitbrainsFAIL non-zero exit status 16 TEST FAILED rpush-quilt FAIL non-zero exit status 16 baredebian-multitar FAIL non-zero exit status 16 baredebian-plusgit FAIL non-zero exit status 16 baredebian-push FAIL non-zero exit status 16 baredebian-tarball FAIL non-zero exit status 16 gdr-import-dgit FAIL non-zero exit status 16 gdr-diverge-nmu FAIL non-zero exit status 16 gdr-diverge-nmu-dgit FAIL non-zero exit status 16 gdr-editsFAIL non-zero exit status 16 gdr-import-dgitview FAIL non-zero exit status 16 gdr-makepatches7 FAIL non-zero exit status 16 gdr-subcommands FAIL non-zero exit status 16 gdr-unprocessableFAIL non-zero exit status 16 gdr-unprocessable-hints FAIL non-zero exit status 16 tagupl-baredebianFAIL non-zero exit status 16 tagupl-gbp FAIL non-zero exit status 16 debpolicy-quilt-gbp FAIL non-zero exit status 16 gbp-orig FAIL non-zero exit status 16 overwrite-splitbrains FAIL non-zero exit status 16 quilt-gbpFAIL non-zero exit status 16 quilt-gbp-build-modes FAIL non-zero exit status 16 quilt-splitbrainsFAIL non-zero exit status 16 rpush-quilt FAIL non-zero exit status 16 Cheers, -- Guido > > Thanks, > Ian. > > -- > Ian JacksonThese opinions are my own. > > Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, > that is a private address which bypasses my fierce spamfilter. >
Bug#992430: schroot: user password does not match
Conrol: tags 992430 moreinfo Sergey Vlasov wrote... > When doing schroot into a buster chroot environment, sudo > commands fail due to password not matching the current user password. > There is no such problem for bullseye chroot environment. > > To reproduce: > > 0. make sure your current user belongs to sudo group > > 1. create buster chroot environment: > > $ sudo debootstrap buster /schroot-bug/buster > > 2. create schroot configuration file: > > $ cat << EOF | sudo tee /etc/schroot/chroot.d/buster > [buster] > type=directory > directory=/schroot-bug/buster > users=$USER > profile=desktop > personality=linux > preserve-environment=false > EOF Unless I misunderstood, also install sudo in the chroot. > 3. enter chroot: > > $ schroot -c buster > > 4. test sudo with your current password: > > $ sudo true (...) The following changes made the check pass: 1. On the *host*, change "yescrypt" to "sha512" in /etc/pam.d/common-password 2. Change the password of that user (feel free to re-use the old one, but we need the right hash). 3. Reboot (possibly not needed if you do the right things). Can you confirm? Then this is stuff for README.Debian but otherwise little schroot can do. Regards, Christoph signature.asc Description: PGP signature
Bug#857018: schroot: Setup script not running, --session-name not working
Control: tags 857018 moreinfo Mike Hommey wrote... > I installed a new machine some time ago, and setup schroot for the first > time on it... Hi, it's been a while, and I failed to reproduce your report. Can you please check whether the problems still exist on your side? Quite frankly, this feels like a broken installation (missing executable bits or some weird noexec mount) Regards, Christoph signature.asc Description: PGP signature
Bug#1011957: aideinit fails in amanda-server processing
Yes! Removing all blank (and "#" comment) lines from disklist solved the problem on 3 different machines. So you've found the issue but, of course, blanks and comments are valid in the disklist and are even present in the disklist installed as a sample with amanda-server in DailySet1. I had to remove the DailySet1 which was still present on one machine to get aideinit to complete without the error. On 5/28/2022 9:46 AM, Hannes von Haugwitz wrote: Hi Barry, On Fri, May 27, 2022 at 04:29:54PM -0500, Barry Trent wrote: *** disklist zmoby.atcorp.com/ comp-root-tar symposium.atcorp.com/ comp-root-tar symposium.atcorp.com/bbbcomp-root-tar moby.atcorp.com / comp-root-tar coelacanth.atcorp.com / comp-root-tar sawfish.atcorp.com / comp-root-tar sawfish.atcorp.com /varcomp-root-tar Is there an empty line in the disklist file? If so, can you please remove this line and try again? Best regards Hannes -- Barry A. Trent 952-829-5864, x109 barry.tr...@atcorp.com smime.p7s Description: S/MIME Cryptographic Signature
Bug#1012004: srpc: Unorthodox binary package content organization
Source: srpc Source-Version: 0.9.6-1 Severity: normal Hi! This package has a rather unorthodox package contents organization. There are two binary packages generated: a) libsrpc-dev: Contains the usual headers (but no .a archive nor .so symlink or linker script). b) libsrpc: Is an unversioned package (given that there's no actual shared library), that contains the .a, .so and versioned .so symlink, in addition to an IDL generator program. This is rather non-standard, and problematic for multi-arch, and is not future-proof, in case upstream starts providing/supporting a shared library. Ideally the .a archive and the .so linked script (which just redirects the linker to always use the .a archive, so there's no actual shared library), should be moved into the libsrpc-dev package as the usual convention. The versioned .so symlink (libsrpc.so.0.9.5) should be removed, as there should be no object dynamically linked against that (given that it points back to the .so linker script which does not resolve at run-time) to avoid confusion. Then the srpc_generator program would be moved into a new libsrcp-bin binary package to make this separation more clear. And the libsrpc binary package can then be dropped. (All with the required Replaces/Breaks relationships.) At that point the libsrpc-dev can be marked as Multi-Arch: same, and the libsrpc-bin (assuming the generated contents are arch-independent) can be marked Multi-Arch: foreign. If there's ever an actual shared library, then it would be packaged as say libsrpcN (with N being the SOVERSION), containing the .so.N.O shared library. Thanks, Guillem
Bug#939229: closed by Dmitry Smirnov (Bug#939229: fixed in golang-gogoprotobuf 1.3.0-1)
Control: affects -1 src:syncthing This bug has not affected syncthing since the following upload: syncthing (1.12.1~ds1-2) unstable; urgency=medium * golang-gogoprotobuf-dev -> golang-github-gogo-protobuf-dev. -- Alexandre Viau Thu, 04 Feb 2021 11:26:39 -0500 Cheers, Nicholas signature.asc Description: PGP signature
Bug#1004658: [Pkg-javascript-devel] Bug#1004658: Bug#1004658: Help to compile a wasm package
anywhere else). The job is done (see debian/rules), we just have to find the good dependencies and fix the build since built wasm isn't exactly what upstream embeds in node-source-map, maybe some unpublished work... I'm not exactly sure if the build is broken. The artifact generated by the rust code goes through multiple tools - rust-opt, rust-gc, etc... It is likely that one of these tools have changed how they work in the past 4 years. But the actual npm package and crate were all last released 4 years ago. In all, I feel like all that's happening is we are unable to build a byte to byte matching reproducible build. How exactly are we testing the output? For one the node-clean-css package seems to be doing some of its own wrapping on the originalPositionFor function and the error in clean-css tests could be because of an error in that.
Bug#1009332: maxima-emacs: Imaxima fails to render latex
tags 1009332 +unreproducible thanks Greetings, and thanks for your report. Just tested in a fresh chroot, and all works fine once ghostscript is installed, which is a dependency issue that needs addressing. This would not account for your latex error. More log info please if this is still live. Take care, -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its citizens." -- Baha'u'llah
Bug#941825: syncthing: 2Gb index-v0.14.0.db
Control: tag -1 -moreinfo Hi Sergio, First, sorry it took me so long to follow up on this bug! [this reply has been sitting in my drafts folder for almost two years :/] With the info you've provided it looks like the issue has been resolved. Rebuilding the index was a good idea :-) That said, did the problem ever come back, or do you think it was fixed as early as Syncthing 1.1.4~ds1-5 ? If it came back, but then went away again, then maybe this bug can be closed as fixed with 1.12.1~ds1-4, or possibly as late as 1.18.6~ds1-1. If I remember correctly there was another round of database optimisations and fixes in between these two versions. Regards, Nicholas signature.asc Description: PGP signature
Bug#1011973: node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function
with node-source-map 0.7 built from salsa master branch, there is only 1 failure. 26 tests were failing earlier with node-source-map 0.6. This is a red herring. The autopkgtest fails aren't related to node-source-map at all. Specifically, the tests don't fail in gbp buildpackage, but only in autopkgtest, that too only in one particular stage. That's because the __mocks__ that jest relies on are in the lib/helpers/ directory and that's not available somehow to the autopkgtest run. For example, if you do autopkgtest with --shell-fail and after it fails copy __mocks__ to /usr/share/nodejs/webpack-sources/lib/helpers and rerun the test with /usr/share/pkg-js-autopkgtest/runner it passes You can replicate it by downloading upstream code and removing `__mocks__` folder and running yarnpkg test https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices#Recommendations > Use upstream test-suite if they have as-installed test The jest tests are not as-installed
Bug#1012006: Updating the genetic Uploaders list
Source: genetic Version: 0.1.1b+git20170527.98255cb-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Angel Ramos has not been working on the genetic package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#1011191: dpkg: let buildinfo record whether host architecture binaries can be executed when cross-compiling
Hi!
On Wed, 2022-05-18 at 07:26:02 +0200, Johannes Schauer Marin Rodrigues wrote:
> Package: dpkg
> Version: 1.21.7
> Severity: wishlist
> Tags: patch
> X-Debbugs-Cc: jo...@debian.org
> when cross compiling, one property of the build system that can
> influence the contents of the generate binary packages is whether or not
> the host architecture can be executed. While some platforms can natively
> execute others (like amd64 can execute i386), other combinations are
> more surprising. When installing the qemu-user-static package on a
> system with binfmt-support, then foreign architecture binaries for all
> architectures qemu supports will suddenly become executable. This is
> especially tricky because this will also transparently affect chroot
> builds with sbuild and neither schroot nor unshare isolation can prevent
> the emulation from happening. The only ways to stop automatic emulation
> are uninstalling qemu-user-static on the outside of the build chroot,
> writing 0 to /proc/sys/fs/binfmt_misc/qemu-$arch or running the build
> with QEMU_VERSION=1 (unreliable). Since transparent foreign architecture
> emulation is easily present on a developer's machine and thus
> influencing the build (even when done inside a chroot) it would be
> useful to record whether or not foreign architecture binaries can be
> executed in the buildinfo file.
Hmm right. To me it feels more like a taint flag though. The
compilation and execution of the host program feels a bit meh, but
there's certainly no other way to fetch that information otherwise.
> I attached a proof-of-concept patch that does exactly that. Since we
> cannot rely on arch-test being installed in the build environment, this
> approach cross compiles a small true.c executable for the host
> architecture. This should always work because gcc is build-essential.
> The binary outputs a small string instead of just relying on the exit
> code to guard against QEMU_VERSION=1 "disabling" of emulation. The field
> 'Can-Execute-Host-Architecture is only added when cross-compiling, i.e
> when host and build architectures mismatch.
I'm attaching the slightly revised version with few fixes/changes.
> >From 62179358b57d09fc8c6bb7a59deb128c67cbe522 Mon Sep 17 00:00:00 2001
> From: Johannes Schauer Marin Rodrigues
> Date: Wed, 18 May 2022 07:11:39 +0200
> Subject: [PATCH] dpkg-genbuildinfo: when cross-compiling add
> Can-Execute-Host-Architecture field
> +use File::Temp qw(tmpnam);
This function is marked as obsolete by POSIX, the File::Temp object
provides a nice interface that can be used instead, perhaps you used
it but were hit by ETXTBSY errors? (If so closing the descriptor fixes
the issue, which is what I've done now.) This also means we do not
need to cleanup the file as the object will do it on its destructor
when going out of scope.
> +spawn(exec => [ debarch_to_gnutriplet(get_host_arch()) . '-gcc', '-x',
> 'c', '-o', $tmpname, '-' ],
I added honoring the CC envvar, but can potentially result in building
for the build instead of host arch, as unfortunately we cannot rely on
an "external build driver" setting a coherent build environment. So
should probably go back to hardcoding it, but I'm thinking I should
move all gcc hardcoding into a new vendor-hook that gets the default
compiler name.
> +if ($? == 0 && $stdout eq "ok") {
> + $fields->{'Can-Execute-Host-Architecture'} = "true";
> +} else {
> + $fields->{'Can-Execute-Host-Architecture'} = "false";
I think a taint flag makes more sense. But it has the problem that
then you might need to check the dpkg version used to see whether
the check might have been performed, but I'm not sure whether that'd
be a concern at all? (If its own field would be strongly favored then
I think it should use the usual "yes"/"no" values used elsewhere.)
Thanks,
Guillem
From cd5f2c47f8aa60e19a7906d3e38b6e53b899a51d Mon Sep 17 00:00:00 2001
From: Johannes Schauer Marin Rodrigues
Date: Fri, 27 May 2022 01:33:19 +0200
Subject: [PATCH] dpkg-genbuildinfo: Add new can-execute-cross-built-programs
tainted flag
[guil...@debian.org:
- Use File::Temp instead of tmpnam() and push_exit_handler().
- Set a taint flag instead of a new field.
- Refactor into a function.
- Honor CC environment variable.
- Style fixes. ]
Closes: #1011191
---
scripts/dpkg-genbuildinfo.pl | 48 ++--
1 file changed, 46 insertions(+), 2 deletions(-)
diff --git a/scripts/dpkg-genbuildinfo.pl b/scripts/dpkg-genbuildinfo.pl
index e05fce048..81e4636e5 100755
--- a/scripts/dpkg-genbuildinfo.pl
+++ b/scripts/dpkg-genbuildinfo.pl
@@ -28,13 +28,15 @@ use warnings;
use List::Util qw(any);
use Cwd;
use File::Basename;
+use File::Temp;
use POSIX qw(:fcntl_h :locale_h strftime);
use Dpkg ();
use Dpkg::Gettext;
use Dpkg::Checksums;
use Dpkg::ErrorHandling;
-use Dpkg::Arch qw(get_build_arch get_host_arch debarch_eq);
+use Dpkg::IPC;
+use Dpkg::Arch qw(get_build_arch get_host_arch debarch_eq debar
Bug#987324: rust-hashbrown: missing ahash feature makes building hashlink crate impossible
Quoting Jonas Smedegaard (2022-05-28 16:18:26) > Quoting peter green (2022-05-28 14:49:00) > > > Package rust-ahash is now in Debian, which should help fix this bug. > > > > > > - Jonas > > > > > > I looked but the new packages don't seem to be installable. > > > > > 2 binary packages have unsatisfiable dependencies high > > > > > > The dependencies of librust-ahash+compile-time-rng-dev=0.7.6-3 cannot > > > be satisfied in unstable on amd64 because: unsatisfied dependency on > > > librust-const-random-0.1+default-dev (>= 0.1.12) | > > > librust-const-random-0.1+default-dev (>= 0.1.12) > > > The dependencies of librust-ahash-dev=0.7.6-3 cannot be satisfied in > > > unstable on amd64 because: unsatisfied dependency on > > > librust-atomic-polyfill-0.1+default-dev > > > > > Yeah - as you know (since you filed the bugreport), all packages > involving librust-once-cell-dev currently fails to build from source due > to bug#1011645 :-( > > I meant to say that the availability of the package is a step towards > this bugreport getting fixed - not that it was possible to fix right > now. Thanks for the quick fix of bug#1011645. I have now released rust-ahash with a fix for the first of the above bugs. I don't recognize librust-atomic-polyfill-0.1+default-dev being declared anywhere, however. Please double-check that you used a pristine Debian unstable system where you experience that error, and if it persists then please file a bugreport. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1010663: RFS: strawberry/1.0.4-1 [ITP] -- Audio player and music collection organizer
Paul, Thomas, thanks for digging up the old reject. Peter, I did some more digging and found one unresolved copyright issue from my previous comment as well as some fresh ones: * copyright holder Pascal Below for various scrobbler-related files is still missing * copyright holder Nick Lanham missing for savedgroupingmanager.cpp; note that copyright for both .cpp and .h is shared with Jonas Kvinge * missing entry for src/core/lazy.h * as the info for src/dbus/*.xml doesn't seem to exist anywhere in the sources, please add a comment field to that paragraph explaining what the entry is based on * the license paragraph for GPL-3 doesn't restrict the version to v3 only (other than the shortname suggesting so) and lacks a link to the full text of the license on debian systems I noticed you changed the build to qt6 and while that works fine, it does seem that at the moment qt5 is very much the standard qt release in the distribution. A quick comparison using `reverse-depends -b qt6-tools-dev` vs the same for qttools5-dev showed 6 packages build-depending on the former and around 300 on the latter. Is there any particular advantage to using qt6 for strawberry? Don't worry too much about the reprotest, sometimes these things throw a tantrum. pgpJnLp0Q7Zac.pgp Description: OpenPGP digital signature
Bug#1011510: dpkg-statoverride does *not* run chmod
Hi! On Tue, 2022-05-24 at 09:36:45 +0200, Harald Dunkel wrote: > Package: dpkg > Version: 1.20.9 > Severity: wishlist > To avoid confusion the man page to dpkg-statoverride should > mention explicitly that it does *not* run chmod or others to > actually change the access permissions to already installed > files, or to files that are not part of a Debian package, or > to files that are generated by a package maintainer script. It does not change the owner or permissions as long as --update is not used, otherwise it will change the attributes for any pathname in the filesystem regardless of it being (currently) known dpkg or not. If no --update is used, then if the pathname is "never" unpacked then it will never receive an override, yes. (I'm assuming the confusion is about the attribute change semantics and not whether it forks the chmod(1) and chown(1) tools though.) But I can see how this can be not entirely clear from the man page and I'll try to clarify. Thanks, Guillem
Bug#1002382: nbsphinx: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar'
Control: reassign -1 src:nbconvert 6.1.0-1 Control: unarchive 1002372 Control: forcemerge 1002372 -1 Control: archive 1002372 On Wed, Dec 22, 2021 at 09:05:08AM +0100, Lucas Nussbaum wrote: > Source: nbsphinx > Version: 0.8.7+ds-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > PYTHONPATH=/<>/src python3 -m sphinx -b html doc > > /<>/debian/python-nbsphinx-doc/usr/share/doc/python-nbsphinx/html > > Running Sphinx v4.3.2 > > > > Exception occurred: > > File > > "/usr/lib/python3/dist-packages/nbconvert/filters/markdown_mistune.py", > > line 31, in > > class MathBlockGrammar(mistune.BlockGrammar): > > AttributeError: module 'mistune' has no attribute 'BlockGrammar' It is a bug in nbconvert, same as #1002372. And already fixed. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1011962: librust-serde+derive-dev: Installation is broken
Package: librust-serde+derive-dev Version: 1.0.130-2 Followup-For: Bug #1011962 This bug exists in version 1.0.130-2 of librust-serde+derive-dev. Please close with the version that actually solves the reported issue. - Jonas
Bug#1012008: Updating the build-essential-mipsen Uploaders list
Source: build-essential-mipsen Version: 12.9 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Scott James Remnant has retired, so can't work on the build-essential-mipsen package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#1012007: Updating the build-essential Uploaders list
Source: build-essential Version: 12.9 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Scott James Remnant has retired, so can't work on the build-essential package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#1003261: postfix 3.5.13-0+deb11u1 flagged for acceptance
package release.debian.org tags 1003261 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: postfix Version: 3.5.13-0+deb11u1 Explanation: new upstream stable release; do not override user set default_transport in postinst; if-up.d: do not error out if postfix can't send mail yet
Bug#1003713: telegram-desktop 3.1.1+ds-1~deb11u2 flagged for acceptance
package release.debian.org tags 1003713 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: telegram-desktop Version: 3.1.1+ds-1~deb11u2 Explanation: new upstream stable release, restoring functionality
Bug#1011287: orca 3.38.2-2 flagged for acceptance
package release.debian.org tags 1011287 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: orca Version: 3.38.2-2 Explanation: fix usage with webkitgtk 2.36
Bug#1011359: python-scrapy 2.4.1-2+deb11u1 flagged for acceptance
package release.debian.org tags 1011359 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: python-scrapy Version: 2.4.1-2+deb11u1 Explanation: don't send authentication data with all requests [CVE-2021-41125]; don't expose cookies cross-domain when redirecting [CVE-2022-0577]
Bug#1011626: Nearly no icons since several releases
On Wed, May 25, 2022 at 04:09:51PM +0100, Klaus Ethgen wrote: > > Regardless, please try running: > > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders > > and verify that you have a section such as this: > > It is included and looks like the section you posted. That's good. > > If it is, then also check that > > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache contains > > the same entry. > > Nope, that is NOT including a similar section. > > ~> grep -c svg /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache > 0 Here is the problem. I wonder what happened that didn't update that file. Try reinstalling it: # apt install --reinstall librsvg2-common You should see a line such as: ... Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1) ... ... Which is exactly what is supposed to update loaders.cache. After that, please check whether that grep above returns something else (in my case, I get 6 matches!). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1000355: nano 5.4-2+deb11u1 flagged for acceptance
package release.debian.org tags 1000355 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nano Version: 5.4-2+deb11u1 Explanation: several bug fixes, including crashes
Bug#994622: network-manager 1.30.6-1+deb11u1 flagged for acceptance
package release.debian.org tags 994622 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: network-manager Version: 1.30.6-1+deb11u1 Explanation: new upstream stable release
Bug#1011939: hdmi2usb-mode-switch 0.0.1-2+deb11u1 flagged for acceptance
package release.debian.org tags 1011939 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: hdmi2usb-mode-switch Version: 0.0.1-2+deb11u1 Explanation: udev: Add a suffix to /dev/video device nodes to disambiguate them; move udev rules to priority 70, to come after 60-persistent-v4l.rules
Bug#1003713: libtgowt 0~git20210627.91d836d+dfsg-3~deb11u1 flagged for acceptance
package release.debian.org tags 1003713 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: libtgowt Version: 0~git20210627.91d836d+dfsg-3~deb11u1 Explanation: new upstream stable release, to support newer telegram-desktop
Bug#1011365: nvidia-cuda-toolkit 11.2.2-3+deb11u2 flagged for acceptance
package release.debian.org tags 1011365 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-cuda-toolkit Version: 11.2.2-3+deb11u2 Explanation: use OpenJDK8 snapshots for amd64 and ppc64el; check usability of the java binary; nsight-compute: Move the 'sections' folder to a multiarch location
Bug#1012010: matrix-hydrogen: build-depends on no longer available node-commander (< 7)
Source: matrix-hydrogen Version: 0.1.30~dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, matrix-hydrogen can no longer be built since one of its Build-Depends has moved on: The following packages have unmet dependencies: builddeps:matrix-hydrogen : Depends: node-commander (< 7) but 9.2.0-1 is to be installed Andreas
Bug#1010349: librecad: CVE-2021-21897 - heap-based buffer overflow loading a DXF file via embedded dxflib
Hello Neil, I'm triaging this vulnerability for Debian LTS / stretch. It appears librecad is not affected (all dists): - the package uses system dxflib, cf. debian/patches/debian_build.patch - while there appears to be similar vulnerable code in libraries/jwwlib/src/dl_jww-copy.cpp (grep for 'groupCode==42'), this particular file is not used in the build process AFAICT Can you confirm and update the security tracker accordingly? Cheers! Sylvain Beucler Debian LTS Team On Fri, 29 Apr 2022 11:09:43 +0100 Neil Williams wrote: Source: librecad Version: 2.1.3-3 Severity: important Tags: security X-Debbugs-Cc: codeh...@debian.org, Debian Security Team Hi, The following vulnerability was published for librecad. CVE-2021-21897[0]: | A code execution vulnerability exists in the | DL_Dxf::handleLWPolylineData functionality of Ribbonsoft dxflib | 3.17.0. A specially-crafted .dxf file can lead to a heap buffer | overflow. An attacker can provide a malicious file to trigger this | vulnerability. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-21897 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21897 Please adjust the affected versions in the BTS as needed.
Bug#1012011: recap: errors on Cron job
Package: recap Version: 2.1.0-1 Severity: normal X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation?running cron job * What exactly did you do (or not do) that was effective (or ineffective)? install from apt-get * What was the outcome of this action? receive multiple notices about "df: /root/.cache/doc: Operation not permitted" from Cron Daemon * What outcome did you expect instead? none of these warnings *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages recap depends on: ii gawk 1:5.1.0-1 ii iotop 0.6-24-g733f3f8-1.1 ii iproute2 5.17.0-2 ii links 2.26-1 ii procps2:3.3.17-7+b1 ii sysstat 12.5.6-1 recap recommends no packages. recap suggests no packages. -- no debconf information
