Bug#1061212: Please upgrade to llvm-toolchain-17
Quoting Sylvestre Ledru (2024-01-20 22:02:43) > Source: emscripten > Severity: important > > Dear Maintainer, > > As part of the effort to limit the number of llvm packages in the > archive, it would be great if you could upgrade to -17. > > This package depends on 14. Please note that emscripten has been orphaned, so has no maintainer. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1041308: O: librem-ec-acpi -- dkms driver sources for EC ACPI in Purism Librem devices
Package: wnpp Severity: normal X-Debbugs-Cc: librem-ec-a...@packages.debian.org Control: affects -1 + src:librem-ec-acpi -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I have orphaned the librem-ec-acpi package. The package description is: The driver librem_ec_acpi provides Linux kernel support for the ACPI embedded controller of the following devices: * Purism Librem 14 laptop . Advanced Configuration and Power Interface (ACPI) is a protocol to discover and configure computer hardware components, to perform power management e.g. putting unused hardware components to sleep, to perform auto configuration e.g. Plug and Play and hot swapping, and to perform status monitoring. . This package provides sources for the librem_ec_acpi kernel module, for use with the Dynamic Kernel Module Support (dkms) framework. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmS1CtMACgkQLHwxRsGg ASEtbxAAlMvCSk/9ZyU29bRVimnGXc6I9Qbuled7BmhKi6z+S2Yo5RnkkgMddCR7 t49aPBah+ENBe/8sl+48VlQBBarYZhf1lZJ6ugXulkp6m+pcG2PVX1aYBKbGWHMg XmrInqHrvMIhVJuZLk9nZrVvozDwtmGAm6JbVb7HNbtb0ODtFndzDzKrYiOBuyJX 6x6Bx5htMmN+eCAjZqYsjN8uFZ5RrSACdsIMfEDBa1RDeupnPHddsMLNjw2u6FvF wXnFRKlc+4cpupY/aF4w5q1oxBHoueUu1NajpG6bj/HQWISSpl7ChaPmWuxev8gZ kf8doUpGtE28okpNKQPX0uJAGkgURT+6kkZU+aBLDOX3mZlhXkVr00OjD9attakT CI23u6tnhpcw6qRRPlEN2gIb2YJhlHnR+bns9YoLWI022bATccDVzPBuJ3K+dsgW aEIpVKmpqP+9GgU9OgXcJiigYJiLy0MtdctU1RbhqbRCRrvQ7BThxqghb5DOeJGF QLMCnEdWiuKng+7ELLUHZEZHe1PLLM076BAibSezpD+NrqZjv+uMl0dGo0O7/ohJ GPTW1MXXrTz0pr6Y6KWH+z5uDnSgEswDEB0JQbp3ah5odqExe2FVNbZPzR4sctM0 NydL7sJdAWT5J1iuysMrS9cbvjer83/c8+x3y+73R1ux2uQKGHg= =8BwQ -END PGP SIGNATURE-
Bug#1031452: [Pkg-javascript-devel] Bug#1031452: *: FTBFS: java.util.MissingResourceException: Can't find bundle for base name com.google.javascript.rhino.head.resources.Messages, locale en
Quoting Yadd (2023-02-17 08:21:59) > Control: reassign -1 closure-compiler > > On 2/17/23 10:49, Lucas Nussbaum wrote: > >> java.util.MissingResourceException: Can't find bundle for base name > >> com.google.javascript.rhino.head.resources.Messages, locale en > >> at > >> java.base/java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:2045) > >> at > >> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1683) > >> at > >> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1586) > >> at > >> java.base/java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1549) > >> at > >> java.base/java.util.ResourceBundle.getBundle(ResourceBundle.java:932) > >> at > >> com.google.javascript.rhino.head.ScriptRuntime$DefaultMessageProvider.getMessage(ScriptRuntime.java:4521) > >> at > >> com.google.javascript.rhino.head.ScriptRuntime.getMessage(ScriptRuntime.java:4501) > >> at > >> com.google.javascript.rhino.head.ScriptRuntime.getMessage0(ScriptRuntime.java:4446) > >> at > >> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:84) > >> at > >> com.google.javascript.jscomp.RhinoErrorReporter.(RhinoErrorReporter.java:32) > >> at > >> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:162) > >> at > >> com.google.javascript.jscomp.RhinoErrorReporter$OldRhinoErrorReporter.(RhinoErrorReporter.java:158) > >> at > >> com.google.javascript.jscomp.RhinoErrorReporter.forOldRhino(RhinoErrorReporter.java:119) > >> at com.google.javascript.jscomp.Compiler.(Compiler.java:176) > >> at > >> com.google.javascript.jscomp.CommandLineRunner.createCompiler(CommandLineRunner.java:858) > >> at > >> com.google.javascript.jscomp.AbstractCommandLineRunner.doRun(AbstractCommandLineRunner.java:741) > >> at > >> com.google.javascript.jscomp.AbstractCommandLineRunner.run(AbstractCommandLineRunner.java:380) > >> at > >> com.google.javascript.jscomp.CommandLineRunner.main(CommandLineRunner.java:980) > > Same error displayed on 4 packages using closure-compiler, looks like a > bug in closure-compiler itself closure-compiler is known for years to be heavily outdated. Unless those tools depend on *specific* features of closure-compiler (e.g. some ancient form of what is nowadays called "tree-shaking"), then I strongly recommend to patch those tools to instead use uglifyjs. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1023130: matrix-synapse: embeds several Rust crates
Package: rc:atrix-synapse Version: 1.70.1-1 Severity: important Tags: security X-Debbugs-Cc: Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This source package embeds 54 vendor projects (Rust crates), 25 of which is of same version as separately packaged for Debian, and additionally 26 of which is either same major version or needed only for Windows builds - i.e. amount of vendored projects can likely be reduced to 3. Debian Policy §4.13 says that this vendoring should be avoided. Please package the missing (possibly only 3) projects separately, and reorganize this package to instead depend on separately packaged Rust crates. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNeiosACgkQLHwxRsGg ASFWnw//YPMT/OSWcMZonWxCX/5DHbd6BY+O6I8OJLyJumAhy0qzAlCiNdCLXZj/ QcA51ho+23gPDhm5fpKUCQrHKY013IPsiORVnJPpZAD5L0WYY69gG3veLtrOCmZX yClx89A4X0RyLoCjAeoYYdnv0LE0BI7DhpzcrJ16obhYyWt7lS+6v7N0LEQEKagD muLEi4r8DNYD/Ok9sKhxk4CG/dBuYLElBkDPRkniMjHilqqME1iirYGSbwrqk/5Q hvfBTdvHVOivWj7ywNSWWckf6Bcnx5G+m4RU+kvmMptx7sVT/RByNZBOwYCp7pCb Ut9thDCPn7Z7IuP8PKmHhI8y792cTW7EJ/y1B2+YJEtDMscjgmFWF+i080OHQr9m xD6J2i11tNUQ+pYRb4qx1cV26+GzNaaqyr1YCcRQK23kG4ouz3iVhPIqD8dBrAbY YvqRUShgOICRcyfpPWuJiwO5dhI9BNoo4rtb3QkvjuiCf8msNKik9li/Cs86YhSs fYe29UN4OhDRJ3d+EMhHo+YrxKFZRMEhoAodXRjsENr0BsS91G3Wf24irI2xjedB GpUYBEROM/eniSePJTyB6a4+1DdiCLVZtixKg2GpmikB6qjUfEaHfvHR/zp1ImEY rcoigN5P9dr5K8nauRDC3sda1TlQcPpjdaO7xdgGsQPCnp2JcRw= =xeeq -END PGP SIGNATURE-
Bug#824168: apt-listchanges: Should not display news for libraries and other packages that the user does not care about
A somewhat related issue is that libraries installed by debian-installer is marked as manually-installed - see bug#742977 - 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#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails
Control: severity -1 serious Quoting Jonas Smedegaard (2020-12-29 23:30:11) > Quoting Graham Inggs (2020-12-29 20:35:03) > > The build of link-grammar/5.8.0-3 has already failed on ppc64el [1] > > (details below). > > > > As fun as it is, please let's avoid the BTS sports and leave this > > bug open until link-grammar builds and passes its autopkgtests > > reliably. > > I closed the bugreport when in -3 I optimistally expected the test > failures to be gone. I agree this bug should stay open when that's > not the case. > > I disagree, however, that the current level of flakiness renders the > package unsuitable for a stable Debian release. Ouch - I begin to understand now why others before ne had patches the build routines to fully avoid checking tests during build: autopkgtest can be marked build-needed and flaky, but apparently the build includes any build-time tests and failing those are not considered flaky. I am now in touch with upstream on getting to the bottom of the causes for the test failure. I will also try simplify autopkgtest to not need to rebuild all source. I've bumped severity back to serious: I thought that a) build-time failure was less frequent and b) I had succeeded in annotating this test as flaky for autopkgtest - but the latter is clearly not the case and I am not so sure about the former either... :-/ - 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#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails
Control: severity -1 important Quoting Graham Inggs (2020-12-29 20:35:03) > The build of link-grammar/5.8.0-3 has already failed on ppc64el [1] > (details below). > > As fun as it is, please let's avoid the BTS sports and leave this bug > open until link-grammar builds and passes its autopkgtests reliably. I closed the bugreport when in -3 I optimistally expected the test failures to be gone. I agree this bug should stay open when that's not the case. I disagree, however, that the current level of flakiness renders the package unsuitable for a stable Debian release. Please do clarify if you think that my reasoning is wrong. - 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#975696: [Pkg-sugar-devel] Bug#975696: link-grammar: multi-thread test fails
Control: severity -1 important Quoting Graham Inggs (2020-11-25 09:59:36) > The upload of link-grammar 5.8.0-1 intermittently FTBFS on several > architectures, e.g. arm64 [1], armel [2] and ppc64 [3]. The failures > all happen during the multi-thread test with various errors: > double free or corruption (fasttop) > free(): invalid pointer > malloc_consolidate(): invalid chunk size > Segmentation fault > corrupted double-linked list > > Giving back the builds eventually works, and link-grammar is currently > built on all release architectures. However, this same test is run > during the autopkgtest and for some reason always fails on armhf [4]. > This prevents the migration of link-grammar 5.8.0-1 to testing, and > will eventually cause the autoremoval of abiword and sugar from > testing. > > Would you please have a look? > > Regards > Graham > > > [1] > https://buildd.debian.org/status/fetch.php?pkg=link-grammar&arch=arm64&ver=5.8.0-1%2Bb1&stamp=1606121733&raw=0 > [2] > https://buildd.debian.org/status/fetch.php?pkg=link-grammar&arch=armel&ver=5.8.0-1%2Bb1&stamp=1605753701&raw=0 > [3] > https://buildd.debian.org/status/fetch.php?pkg=link-grammar&arch=ppc64&ver=5.8.0-1%2Bb1&stamp=1606118399&raw=0 > [4] https://ci.debian.net/packages/l/link-grammar/testing/armhf/ I tightened the test checking - enabled them during build and made them more verbose (and explicitly passed environment variable "srcdata" which might have previously failed). Those changed was finalized and released today as 5.8.0-2, and I hope it can shed some light on what more detailed fails when it does. To my surprise, the armhf failures are evidently no longer persistent even _before_ this latest release. I therefore relax severity of this bug. Thanks for the report, Graham, - 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#971252: gsutil: typo in long description: randstream -> Grandstream
Package: gsutil Version: 3.1-4 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Long description is missing a "G" in Grandstream. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl9xgncACgkQLHwxRsGg ASGZmA//btkrOpIQ2EjXbkEspZM+i7vrk/bxRcG8mFeLI9C9RmHUnlxh4vxIW2BM 6lUwxtBEmH1eofj4Iql4D3KqkpJb1LcrwYRJntksfph9XySBP0olQqIPHbBVz+Jx aQZ1XwCJl00VoGA5/TK935cZ8IK4o9ZcTAt9z8Vdozu9KI2zmo5M2EIHv4oJu+0u H/Q7VG00ljTpkU19FauYEBzmgDF1U6GuBtDBZFTL/zBScO6b+ecL69u1EJ16Qljf bRCDCXAbBAKCRErCWUl6EziZZ8J2jMhvJZPUvtw0OeKnx24mYWD3bFJXCmZhPJGr gZViaQeaaKVs3VczvER/L2iUELra+LK7kytBm8c4oP5BKZDraNi1YB6jumxjcT1i Iu5qXwU3XoUhPgdpA37sR78aN0SDVTfhGMFwJLWpNhRoY1hBCri+oJkcA5Wghfx6 /ObyNFgLbATyL8hH56R9yI4MdFimuAAz9gBAnYASE399IsiYySop+5Fi5cziJ9S+ wE5OA7KCZgy0FI2Js/7hNgt/Sy2jCr5jhnuZGkElfQTWsfoeTOqs9ixk2+rtymgD ziif4WzYvyeT//bZB3+PGmYlu5543Aue+vSD3XPBAnCd9H54AeI2r6bcPspyGe9U Au5KnbPrqg8jgZszpqQPi1AT/U+x4qPWMBvb84wmIDh/xguY6BE= =sTDY -END PGP SIGNATURE-
Bug#919571: This shouldn't need fixing: obsoleted by libical3
control: affects 926574 libical Please note that libical is superseded by libical3, and has now been requested removed from Debian - see bug#926574. - 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#837927: gxmessage: should register itself as alternative for xmessage
Package: gxmessage Version: 3.4.3-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The very purpose of gxmessage is to provide the interface of xmessage using GTK+. Therefore it makes good sense to register it with the alternatives system: This benefits hardcoded uses of xmessage - including Xmonad. - Jonas -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJX2rdXAAoJECx8MUbBoAEhfJgP/RrYQi6a0KggoHTn7YzK6fFa uxn7mj1JMmy8jjdcEWh6uPA1DAc4EVqnrakjFrg3QPLj311qiJak+RPXYt8rg1D+ BLU2OKOJKgla2KhWED0rQv03ASx7DF3d4/CGR/j7obfWWkmpfJuegG6tD+B1CfsA l9OqoB1C54gcsqXItp4wbq93/QdKNPf7ixoNKZaWvAjtc4AsC7RhkgvhkvQTqKrm VvHhBEmq6BR8HvXaKqWitSMYhfglQOJNlYw3FkZ6IfgH6dsWBzfjvdpZaD3c2syb np4kmOYdAiUYYIIy+VeguOZDsPJdin6hcPjODde17cSWfvh6GWt1G2TJox9VmCO7 TgYEtWZ7UC6Xu6TKymIVNzlhPKKBQWMXMdu700QGKXprkDL8XHWy3c13EQU0qadl y2CHwhbEhCf77Pnk4Td17aas8Jb+fEBjKLDhZSDRo94QWHTpTI9FJuw7+J8JuGmr 2TcEajPCGJXqWdajemRqPOjWUgUkvJb3niB35bQ4gcvcHfixILMTRyY9/weGfGhO MjRAdJAO4UHXjMB+7Y+I1B9TlZ+BS+F7qXykrVAYoEadjxVmH7J1Ar65AqL07d9f OicnQD96ex4V7Ccxh+AIr3xJdgMKdINIhFdtWTsvR2jwkIlWlA3JNseBQjDqMf7y LTy8bFn87OqQBa96NxSf =kGhT -END PGP SIGNATURE-
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting John Paul Adrian Glaubitz (2015-06-20 15:16:28) > You are still trying to boil this down to the mere problem with cmus, This bugreport is filed against cmus, is it not? > but that's just a side effect. The real point is that roaraudio > depends on an unmaintained piece of core software which Debian would > like to get rid of. Then please reassign and retitle the bugreport to discuss the real issue where it belongs. - 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
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting Don Armstrong (2015-06-20 14:38:25) > There's clearly a bug here, but even after reading this bug log, I've > had to do research on my own to determine what that issue is. > > If the libroar2 maintainers which to keep decnet support, then someone > should probably figure out how to circumvent waiting for the DECnet to > settle when it isn't actually configured, and propose a patch to do > that. > > Even just checking for the existence of dnet-common or similar would > probably be enough. As I understand it, these are the issues raised here: a) libdnet is unmaintained and thus potentially dangerous to link against b) dnet-common commonly (or always by default?) cause whole system to hang I disagree that any of above are bugs in cmus. - 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
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting John Paul Adrian Glaubitz (2015-06-20 13:00:53) > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 06/20/2015 07:56 PM, Jonas Smedegaard wrote: >>> I can't imagine that you cannot reproduce this on a clean >>> install, I could reproduce it on all machines running at least >>> Jessie. >> >> Please provide the command to reproduce _without_ --with-suggests >> option enabled! > > Jonas, I think you need to re-read what I wrote. Currently libroar2 is > a Recommends and _not_ a Suggests: > > glaubitz@ikarus:~$ apt-cache depends cmus | grep libroar2 > Recommends: libroar2 > glaubitz@ikarus:~$ I agree that cmus pulls in libroar2. Why is that dangerous? > My elaborations regarding "--with-suggests" were regarding the case > that Alessio would drop libroar2 from Recommends to Suggests. If you mean to say that "--with-suggests" is irrelevant to discuss here, then I agree: Use of special package install options should be irrelevant when dicussing whether cmus is dangerously broken or not. If you mean something else then please elaborate. > Currently cmus is definitely getting stuck on a _fresh_ install, simply > by installing with "apt-get install cmus". On those systems where you experience cmus being stuck, is the package "dnet-common" also installed (or was it ever)? If so, you will need to figure out how that got installed, and I am quite certain the cause is *not* cmus and therefore this bugreport against cmus is bogus. - 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
Re: Bug#789256: cmus: Pulls in unwanted and potentially dangerous DECnet packages through libroar2
Quoting John Paul Adrian Glaubitz (2015-06-20 12:34:25) > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 06/20/2015 01:03 PM, Stephan Jauernick wrote: > > Thanks for pointing that out. I was mistaken there. Sorry :( > > No worries, I don't think we disagree about the problem in general. > > > Can you maybe still provide a backtrace/strace log? > > This isn't really necessary as this isn't cmus crashing, it's cmus > getting stuck because it's apparently waiting for the DECnet stack > to become ready. > > I can't imagine that you cannot reproduce this on a clean install, > I could reproduce it on all machines running at least Jessie. Please provide the command to reproduce _without_ --with-suggests option enabled! - 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#785688: abiword: please enable introspection needed by recent sugar-write-activity
Package: abiword Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Recent releases of sugar-write-activity needs abiword introspection. Please enable that. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVWuseAAoJECx8MUbBoAEhbUQP/jSViRtfsbD2aii7Xu2kof1U VUkrQpEcb9lvnmm9+2Z/5lAS+7NNRajvYu5psvtDH7VPE0lJZ3lkHw4ZKlW58dWD OWGiPKjoWcpMaKWsdOQ87lxiuO3kFMfUtHY3M47EfT/lNvFiE8WJ8fKO7+OuXkcm m2xkyxjPki8HCg3yxqiC+r4SoQxMpOxvDpRrqpH+mmSjQ9Xt6v9LOi2B03pvow3R wJtEtI1q9tGLe4DOsPhtclPSJdYinPRa6bd0y2+arLxzgP2F0UVPY3LMtsDB/flj SwyAwTuaC0p2PbUUBUIyAYhVnI/DoPjFI4cGml2ei/HzFmNF+GEhGPNiPlRzgy0Y F9OGwE3ldbm5haRdb2lK2Lnltgh6tfbnHrpEfxHQ9SKdp1Kg5Cqvh0Tw2sHjz4zZ uE5T/PJOCOdZMsbhUT+04DMKUS4Du5saXpbqCpyxnLTKo33mOBLcN0rFJpNH7Xhx UR/J0r4pS21D9mxhz+anR4h6VoszboDHd9d1yetk7BvXbZfB04KPS33f4WQjimnw X8QdFoAY60k3VuP0IEnf+yxxJcOPATgDKLnnOhEioJGRVQ0X9RjJ8jjXt1jTbgCe NXuLd+P59WkbswoS03Ui+OZZHRemzhFO77dpKt6oi5SMfpPCUfWhAnyQHYGnPtyI AWPIDWbMff7ALceXqNcU =Xful -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150519074953.15263.22977.report...@bastian.jones.dk
Bug#778755: ekg2: should not recommend ekg2-dbg
Package: ekg2 Version: 1:0.4~pre+20120506.1-8+b1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ekg2 recommends ekg2-dbg. Recommandations are for relationships satisifying most uses of a package, and for a non-development tool like ekg2 that can hardly be true for debugging symbols. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJU5cG1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5RkUzRTlDMzY2OTFBNjlGRjUzQ0M2ODQy QzdDMzE0NkMxQTAwMTIxAAoJECx8MUbBoAEhdfIP/i0WRb+HR8PQ79aCZPPU/3d3 3r1BCxM1jzG94HjXcm2NVfnkNj0lskHmGybZ/t7GRUO89KRVnrIrGbWARGY+hVx9 xx9NRriI6kwKy8aKJE09Vm1YfIiQ+xsk8obtAsmdYuSZQE7UwKdrvdtu6uVfj2qW //uDnSh7QysQ60nl+RUNOZi/+aEaOfRBrd3uJHLfmfzY7FGcjcNTPc0c4+0mYKr2 IGQ22bJU3O737NnqOf/XQNe5nw1n7FlYmR+FSIVkGrZlEt8L0gfMWBd1ptcGreG1 ZiC1G/mYKkaWmHJEiRhVNmYyPAs6Z4rgy7YuTlBUTPA3Fjb88PKlz9JVK1b+IO4J GpN2+T0+XqXGrFdG6XEOjN6sYBpg5mbLRSOifGLhJkRxRfMrjoVvZPqrDgMxfHa8 CY2rTYZTVJNfWmEWfXpsidG0WPRnhhMnAYXLALgUWiXUrVnUWisbb+lRWvlNbRHD xnbAl0eNb08/iYjpJU7AOBjhowuOE5pUKRFn0pByhquYDY0tB/buumd4NaNvq+UD Y9j9nIA9pi/ky9CEd6XCUQ7YSf1kIbJUT57uXLbudTUiaCk4CpxDStbUZfcgrr16 3ODn6EgkDlphmUapRLoYl5tOh5kBN4jHIeGJgsJMXHaE/xrahq0J6w5i0fIsFgjz LtifeXElOeB4JIkgiVAU =4GD3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150219105801.29169.87903.report...@bastian.jones.dk
Bug#768428: libvisual-0.4-0: should only suggest plugins
Package: libvisual-0.4-0 Version: 0.4.0-6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Recommending is suitable for relations needed by most users. Looking isolated, the plugins for libvisual is obviously needed by most, but in the larger eco-system, it is not unusual to need GStreamer without needing libvisual plugins. Therefore, the libvisual library should only suggest its plugins, and other packages should recommend them directly. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUXKiUXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW2jAH/iTCACILDnZoI8NGGDc7am/g LzbJGVeoYFP/DJf0QafPLif9W+kAzMCRPmXaNWr7sutEMt1v+1kKeCNz/dD7JosK npIE3EB9gbnY5mllsMd90YVng2ndUm+PoNyxpqzznoCobQXPgPTsuivhzHWQcfsW lQxnGAllxesWfMuXVcWopAfNndGOV7jQfbEzJg04whBMDAsvNhKsepKoJFjBebIF avJBJyDl29AGQZN0otM/g5a0eyT6eo6kS1diLz1KQkigu80KeYvChyHBOte5j4wB ESd9m5ROxmT/T4wlF/3NJi8riJhCXR0oU1jvJNs1hpnT3s1mJWHEbU8afXqfm30= =Q6Zg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141107111016.16164.2802.report...@bastian.jones.dk
Bug#768277: openoffice.org-hyphenation-lt: should at most suggest libreoffice-writer
Package: openoffice.org-hyphenation-lt Version: 1.2.1-4 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package relations are directional: A hyphenation dataset arguably does not "depend" on being used, and certainly not by a specific consumer. Please do not recommend libreoffice-writer, as that causes needless baggage when used in other contexts, e.g. with scribus or frescobaldi. While at it, please consider drop provision of virtual package openoffice.org-hyphenation (i.e. singular form) - it seems a typo and is apparently unused by any consumer. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUWzRhXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWJxkH/jDb93S5JZGBrKleXcGXxfVv F2MpQ+gyRvwey5z9FWMmyE0qQIqVzGIVies+wOWY8CpFRnmwb4ePmxU02M1QSBGe 3YQGS/Klcgk35/O3oKVP9YC7o4f8I+cmIMJhh9F3WBk+OCO4EmNgRWce10cHZBZ5 AWsMzyeqSyl8AvkCoSsNB5kcY0NK7VzK/hGf9M2li42QNVu0OgtNKD8huj60IJV3 Jd+E5sqIuqnTLBU1dTHL2ImRcTSGb0ecxmaMw0FtqBjQI72zjgZGM4mhPMZrmyfN hE+N0UGgKZHniDKyjiM+aF0u0u3zd9EYJWY/kk5I8lXzjX0ufh34FgfyCa8CR4I= =oheS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141106084212.18051.20657.report...@bastian.jones.dk
Bug#706101: DFSG-violation reappeared in 0.22-1
reopen 706101 found 706101 0.22-1 thanks [ cc'ing Michael regarding the P.S. on 0.10 spec ] Quoting Debian Bug Tracking System (2013-04-27 20:51:08) > Source: qpid-python > Source-Version: 0.16+repack-1 > > We believe that the bug you reported is fixed in the latest version of > qpid-python, which is due to be installed in the Debian FTP archive. Correct - but unfortunately the later upstream fix was incomplete: Debian now since 0.22-1 ships the AMQP-licensed amqp.0-10.dtd file. - Jonas P.S. I am now preparing an update to amqp-specs which will include the DFSG-free specs distributed by Qpid project - including what seems to be non-derived 0.10 spec. -- * 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#666739: libnss-lwres: README.Debian wrongly says lwresd not started by default in Debian
Package: libnss-lwres Severity: normal README.Debian says lwresd is not started by default in Debian, yet the package depends on lwresd which properly contains init script. Looks like a leftover from ancient times to me. - Jonas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120401125202.1917.65828.reportbug@localhost.localdomain
Bug#539670: html2ps: should recommend ghostscript (not long time deprecated gs-gpl)
Package: html2ps Version: 1.0b5-5 Severity: important Hi, html2ps recommends gs-gpl which now only exist as a virtual package, and is expected to be dropped completely at some point. Please change to recommend ghostscript - or ghostscript-x if X11 support is needed. Kind regards, - Jonas -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-rc4-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages html2ps depends on: ii libhtml-parser-perl3.61-1collection of modules that parse H ii libpaper-utils 1.1.23+nmu1 library for handling paper charact ii libwww-perl5.829-1 WWW client/server library for Perl ii perl 5.10.0-24 Larry Wall's Practical Extraction ii perlmagick 7:6.5.1.0-1.1 Perl interface to the ImageMagick Versions of packages html2ps recommends: ii ghostscript-x [gs-gpl] 8.64~dfsg-13 The GPL Ghostscript PostScript/PDF Versions of packages html2ps suggests: ii evince-gtk [postscript-vie 2.26.2-1 Document (postscript, pdf) viewer ii ghostscript [postscript-vi 8.64~dfsg-13 The GPL Ghostscript PostScript/PDF ii gv [postscript-viewer] 1:3.6.7-1 PostScript and PDF viewer for X ii texlive-base 2007.dfsg.2-4 TeX Live: Essential programs and f ii weblint-perl 2.06+dfsg-1 syntax and minimal style checker f pn xhtml2ps (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509990: galrey: Please add fallback dependency on graphicsmagick-imagemagick-compat
Package: galrey Version: 1.0.2-3 Severity: minor graphicsmagick provides an alternative to imagemagick. Unfortunately galrey depends versioned on imagemagick, causing the "Provides:" field to be ignored. Please test if graphicsmagick is usable with galrey and if so then add an explicit fallback dependency on graphicsmagick. - Jonas -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.27-1-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages galrey depends on: ii imagemagick7:6.3.7.9.dfsg1-3 image manipulation programs ii perl 5.10.0-18 Larry Wall's Practical Extraction galrey recommends no packages. galrey suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#507189: asterisk: Depends on libc-client2007b which is not in unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Nov 30, 2008 at 11:06:37AM +1100, Mark Purcell wrote: >On Saturday 29 November 2008 10:28:44 Ben Hutchings wrote: >> libc-client2007b has been replaced by libc-client2007d in unstable. > >Thanks Ben. As you state this only effects sid, not lenny which is >(maybe) good for the rdepends. > >Jonas, > >Are you intending for libc-client2007d to migrate to lenny? Your >change log indicates that this maybe an important release. However I >haven't seen any discussion on debian-release nor any coordination with >the rdepends. No, I have no plans to special-case uw-imap 2007d regarding the freeze of Lenny. A security update contains virtually all of the contents of that new release. >If not you upload makes life difficult for the rdepends as we can no >longer upload any proposed lenny changes via unstable. I believe this to be a general complication of a long freeze period. And I believe it better to have such complication for developers at large than burdening the release team with requests for special-casing to bring Lenny in sync with Sid. On the other hand, I do not see any problem in allowing newest uw-imap into Lenny - now that release team is bothered about this issue after all. If release do not want the Sid released package into Lenny, but instead would want a specially crafted package only containing upstream changes and not any possible updates to the cdbs packaging routines, then I see no point in spending time on that: there is already a security update like that. >Has the ABI/API actually changed that has necessitated a new -dev >package and lib package. No. Historically, the uw-imap package was licensed requiring indication of any derivative work in the naming of the files (as I interpreted it), which is the reason for the current libname-based-on-package-version scheme. License since changed, but I did not get around to changing the naming scheme before the freeze. It is worth noting that the very shared library is a Debian-specific thing, discourages upstream. So there is no upstream soname, it is purely Debian-specific. As related security issue is that Alpine, using same codebase, uses its own duplicate of the code instead of the shared library offered as libc-clientXXX.so (its predecessor, the non-free pine, was patched to link against our libc-client library, but I have so far failed to convince the maintainer of alpine to the benefits of sharing code). >As you maybe aware a new -dev package means that all rdepends must be >changed and reloaded, whilst just a change in the lib package allows >for binNMU. Yes, I believe I do understand the issue of rdepends here. >Could I ask you to coordinate with the rdepends and discuss/ file bugs >for what you see as the way forward for integration with uw-imap. As I do not intend to bump the version in Lenny, I fail to see the need for coordination here. Please help me see the light if I somehow miss your point - I _do_ want to cooperate. :-) Kind regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkybr4ACgkQn7DbMsAkQLgj5gCfevdYIv3cCdvdBE0zSppBs0lV 9UkAn3ofMb2Eo/kbPKyCcSLQgsJYTtYe =FSNK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486955: [Debian-olpc-devel] Bug#486987: might be caused by a dpkg-dev regression?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 19, 2008 at 12:18:35PM +0200, Raphael Hertzog wrote: >On Thu, 19 Jun 2008, Lucas Nussbaum wrote: >> Hi, >> >> I figured this out too late, but it seems that all those bugs are caused >> by a dpkg-dev regression. >> Bug#486987: sugar-toolkit: FTBFS: new copyright notices >> Bug#486979: sugar-datastore: FTBFS: new copyright notices >> Bug#486975: sugar-web-activity: FTBFS: new copyright notices >> Bug#487002: sugar-pippy-activity: FTBFS: new copyright notices >> Bug#486961: sugar-chat-activity: FTBFS: new copyright notices >> Bug#486984: sugar: FTBFS: new copyright notices >> Bug#487001: sugar-journal-activity: FTBFS: new copyright notices > >Those are related to a licensecheck improvement. Those checks should >really go away and be run by the maintainer when he wants to check it >and not automatically on build. Yes - I saw this coming when licensecheck got updated a few days ago. I am convinced now that my copyright-check.mk cdbs snippet shouldn't check at each build. I'll fix this! >A few random packages analyzed: >> awstats >> moin >> yaird >=> also related to licensecheck There's an obvious pattern there - all of them are packaged by me: http://qa.debian.org/[EMAIL PROTECTED]&comaint=yes - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhaOB0ACgkQn7DbMsAkQLh4TgCdG7Bg6VmT4zn7m7MLQGbzspwm +hUAn1DzCARYZ8WeayhAkV+cORjj2x9S =OyU8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314261: Upgrade plan from libgd-gif1 to something else?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15-06-2005 17:01, Martin Michlmayr wrote: > * Jonas Smedegaard <[EMAIL PROTECTED]> [2005-06-15 15:35]: > >>I considered adopting libgd-gif1 myself, but it makes better sense to >>kill all 1.x variants and move to 2.x (which has GIF support again now >>that the compression patent has run out). > > > Do you know how hard it is to move from 1.x to 2.x, and is there any > good documentation about migrating? Sorry - don't know: I don't know how to code C at all, only how to package it... >>I suggest next step is to make the package maintainers of the above >>packages aware of this bugreport, if they are not already... > > > Not yet, but I'll do that soon. Great :-) - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCsFKln7DbMsAkQLgRAvzLAJ94Exq4DGiokZxkLAmESA5eCfa0tgCghOGh 8LVej58nYy6g2zKFOc0Q7hQ= =Dk2G -END PGP SIGNATURE-
Bug#314261: Upgrade plan from libgd-gif1 to something else?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15-06-2005 14:54, Martin Michlmayr wrote: > libgd-gif1 has been orphaned for ages, but there are still some > packages which depend on it, so I cannot remove it right now. Could > these packages move to some other libgd* package which we have in the > archive? > > At the moment, the following packages (build-)depend on libgd-gif: > nessus (depends) > boot-floppies (b-d) > gccchecker (b-d) > nessus-core (b-d) > png2html (b-d) libgd-gif1 is a (dead!) fork off of libgd 1.x made to preserve the GIF support dropped upstream. Switching would mean either dropping GIF support (which I believe is not really interesting, as only sane reason to use the fork is GIF support) or rewrite the code to support the newer (and actively maintained upstream!) libgd 2.x series. I considered adopting libgd-gif1 myself, but it makes better sense to kill all 1.x variants and move to 2.x (which has GIF support again now that the compression patent has run out). I suggest next step is to make the package maintainers of the above packages aware of this bugreport, if they are not already... - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCsC65n7DbMsAkQLgRAqiMAJ4/tVoFSLVJxBs/wdx/oix6f9ufrACggZ74 AC3dY3dM9TJ1g60hDzscigc= =uEc/ -END PGP SIGNATURE-
