Bug#736211: src:blackbox: FTBFS on x32
Package: src:blackbox
Version: 0.70.1-18
Severity: wishlist
Tags: patch
Hi! Blackbox fails to build on x32, for two reasons:
* it uses implicit casts between time_t and long, in template disambiguation
where exact types are needed
* its hand-written symbol arch table needs inclusion of x32
Patch attached.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'experimental')
Architecture: x32 (x86_64)
Kernel: Linux 3.13.0-x32+ (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -urd blackbox-0.70.1.0/debian/libbt0.symbols blackbox-0.70.1/debian/libbt0.symbols
--- blackbox-0.70.1.0/debian/libbt0.symbols 2013-11-20 14:25:58.0 +0100
+++ blackbox-0.70.1/debian/libbt0.symbols 2014-01-20 17:16:40.539105265 +0100
@@ -386,7 +386,7 @@
(optional)_ZNSbIjSt11char_traitsIjESaIjEE12_M_leak_hardEv@Base 0.70.1
(optional)_ZNSbIjSt11char_traitsIjESaIjEE12_S_constructIN9__gnu_cxx17__normal_iteratorIPKjS2_PjT_SA_RKS1_St20forward_iterator_tag@Base 0.70.1
(optional)_ZNSbIjSt11char_traitsIjESaIjEE15_M_replace_safeEjjPKjj@Base 0.70.1
- (arch=!any-i386 !alpha !armel !armhf !ia64 !m68k !mips !mipsel !powerpc !powerpcspe !ppc64 !s390 !s390x !sh4 !sparc !sparc64)_ZNSbIjSt11char_traitsIjESaIjEE15_M_replace_safeEmmPKjm@Base 0.70.1
+ (arch=!any-i386 !alpha !armel !armhf !ia64 !m68k !mips !mipsel !powerpc !powerpcspe !ppc64 !s390 !s390x !sh4 !sparc !sparc64 !x32)_ZNSbIjSt11char_traitsIjESaIjEE15_M_replace_safeEmmPKjm@Base 0.70.1
_ZNSbIjSt11char_traitsIjESaIjEE4_Rep20_S_empty_rep_storageE@Base 0.70.1
(optional)_ZNSbIjSt11char_traitsIjESaIjEE4_Rep8_M_cloneERKS1_j@Base 0.70.1
(optional)_ZNSbIjSt11char_traitsIjESaIjEE4_Rep8_M_cloneERKS1_m@Base 0.70.1
@@ -395,7 +395,7 @@
(optional)_ZNSbIjSt11char_traitsIjESaIjEE6appendEmj@Base 0.70.1
(optional)_ZNSbIjSt11char_traitsIjESaIjEE6assignERKS2_@Base 0.70.1
(optional)_ZNSbIjSt11char_traitsIjESaIjEE6resizeEjj@Base 0.70.1
- (arch=!any-i386 !alpha !armel !armhf !ia64 !m68k !mips !mipsel !powerpc !powerpcspe !ppc64 !s390 !s390x !sh4 !sparc !sparc64)_ZNSbIjSt11char_traitsIjESaIjEE6resizeEmj@Base 0.70.1
+ (arch=!any-i386 !alpha !armel !armhf !ia64 !m68k !mips !mipsel !powerpc !powerpcspe !ppc64 !s390 !s390x !sh4 !sparc !sparc64 !x32)_ZNSbIjSt11char_traitsIjESaIjEE6resizeEmj@Base 0.70.1
(arch=!amd64 !ia64 !kfreebsd-amd64 !mips64 !mips64el !s390 !s390x !alpha !ppc64 !sparc64)_ZNSbIjSt11char_traitsIjESaIjEE7replaceEjjPKjj@Base 0.70.1
(arch=amd64 ia64 kfreebsd-amd64 mips64 mips64el s390 s390x alpha ppc64 sparc64)_ZNSbIjSt11char_traitsIjESaIjEE7replaceEmmPKjm@Base 0.70.1
(arch=!amd64 !ia64 !kfreebsd-amd64 !mips64 !mips64el !s390 !s390x !alpha !ppc64 !sparc64)_ZNSbIjSt11char_traitsIjESaIjEE7reserveEj@Base 0.70.1
diff -urd blackbox-0.70.1.0/src/Toolbar.cc blackbox-0.70.1/src/Toolbar.cc
--- blackbox-0.70.1.0/src/Toolbar.cc 2005-04-12 09:38:00.0 +0200
+++ blackbox-0.70.1/src/Toolbar.cc 2014-01-20 17:12:33.059144580 +0100
@@ -44,8 +44,8 @@
{
timeval now;
gettimeofday(&now, 0);
- return (std::max(1000l, resolution - (now.tv_sec % resolution)) * 1000l))
- - (now.tv_usec / 1000l;
+ return (std::max((time_t)1000, resolution - (now.tv_sec % resolution)) * 1000))
+ - (now.tv_usec / 1000;
}
Bug#610266: freepats isn't necessarily needed
freepats isn't a hard-dependency, since people who use timidity are likely to get the patches from another source. Sadly, freepats are badly incomplete and of inferior quality. I think the recommendation should be switched to fluid-soundfont. -- 1KB // Yo momma uses IPv4! -- 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/20110819101648.ga25...@angband.pl
Bug#661999: vorbisgain: typo in -h: "recursivly"
Package: vorbisgain Version: 0.36-4 Severity: minor "vorbisgain -h" (or running it with no arguments) spells "recursivly" wrong. Such a terrible bug can make the Sun explode and milk go sour, you know. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vorbisgain depends on: ii libc6 2.13-27 ii libogg0 1.2.2~dfsg-1 ii libvorbis0a 1.3.2-1.1 ii libvorbisfile3 1.3.2-1.1 vorbisgain recommends no packages. vorbisgain 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 Archive: http://lists.debian.org/20120303111610.6863.41883.report...@umbar.angband.pl
Bug#519569: colorgcc: ZTDOUT
Package: colorgcc Version: 1.3.2.0-9 Severity: normal As perl says, "possible typo": Name "main::ZTDOUT" used only once: possible typo at /usr/bin/colorgcc line 248. binmode() on unopened filehandle ZTDOUT at /usr/bin/colorgcc line 248. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#380027: libgii1-target-x: missing Conflicts: or Replaces: on libgii0-target-x
Package: libgii1-target-x Version: 1:1.0.1-1 Severity: normal Selecting previously deselected package libgii1-target-x. Unpacking libgii1-target-x (from .../libgii1-target-x_1%3a1.0.1-1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libgii1-target-x_1%3a1.0.1-1_i386.deb (--unpack): trying to overwrite `/usr/lib/ggi/input/x.so', which is also in package libgii0-target-x Other dependencies make libgii0 go away, but not early enough to ensure clean upgrades. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#753557: reverted the fix
Control: reopen -1 Control: found -1 burp/1.3.8-1 burp/1.4.40-4 Per the advice of upstream, I've reverted the change: using "restart" breaks running backup jobs. -- A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. Filter out and throw away the fruits (can dump them into a cake, etc), let the drink age at least 3-6 months.
Bug#715066: QA upload in delayed
Control: tags -1 +pending As Simon McVittie NMUed #849932 which blocked this fix (currently in DELAYED/2), we can make this one follow. It's now in DELAYED/2 as well, with a 10 hours gap between them so gtk-sharp2 can get built first. Thanks Andreas for doing the real work! -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second ⠈⠳⣄ preimage for double rot13!
Bug#863679: could you say more about that system?
Control: tags -1 +moreinfo unreproducible > In the last few days, pm-powersave is being called roughly once per > second, which is logging to /var/log/pm-powersave.log until there's no > disk space left. I don't think I have any custom configuration of > pm-utils or related software. I'm trying to reproduce this on every x86 piece of hardware I have, without success. Could you say more especially about "in the last few days"? What did change? I assume you don't reboot daily, so the real reason is time shifted. Still, because of the freeze, changes don't happen often, so the packaged I'd suspect are systemd and the kernel, with a strong hunch about the former. If the bug is readily reproducible for you, would you care to downgrade either systemd or the kernel and check then? > Init: systemd (via /run/systemd/system) This may be the issue: systemd has a NIH implementation of pm stuff, which might be fighting with that of pm-utils. Generally, on systemd machines, keeping pm-utils is kind of pointless, while it is vital on any x86 box that gets suspended and uses other inits. As you filed this bug just days before the total freeze, there's rather little time to find out what might be wrong -- especially that no one else seems to have this problem. Meow! -- Don't be racist. White, amber or black, all beers should be judged based solely on their merits. Heck, even if occasionally a cider applies for a beer's job, why not? On the other hand, corpo lager is not a race.
Bug#872848: dav-text: please support line syntax "dav +42 file"
Package: dav-text Version: 0.8.6-1 Severity: wishlist Hi! There's an option to start at a given line: -l[#] Starts Dav at the line number [#]. However, every single editor I know that runs in a terminal accepts a standard syntax of prefixing the file to be opened by +# where # is the line number. dav has instead just -l# (which also needs to come after the filename, not before). It would be nice if you recognized +# as well. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.8+ (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages dav-text depends on: ii libc62.24-14 ii libncurses5 6.0+20170715-2 ii libtinfo56.0+20170715-2 dav-text recommends no packages. dav-text suggests no packages. -- no debconf information
Bug#863679: Debian Bug report logs - #863679
Control: severity -1 important On Fri, Sep 15, 2017 at 03:16:05PM +0200, Bruno Kohlberg wrote: > Hi, I am not sure how to register or log in on > https://bugs.debian.org/ -- so here is my email with the text which you > are welcome to publish on the website (or tell me how I can do this). To comment on a bug, you mail 863...@bugs.debian.org, like you just did. > Package: pm-utils > Version: 1.4.1-17 > Severity: critical > > On trying to install pm-utils on a pretty new system without many > changes (firmware-9.1.0-amd64-DVD-1.iso with kernel 4.9.0-3) on an ASUS > laptop, Synaptic gives the following message: > > "»critical Fehler von pm-utils (? 1.4.1-17) > b1 - #863679 - /usr/sbin/pm-powersave: repeatedly runs until > /var/log/pm-powersave.log fills up disk" The tool you're using is warning you about high-severity bugs someone reported. However, this one seems to be spurious -- no one else has managed to reproduce it, and the original reporter hasn't responded either. Thus, I've just downgraded the report; I'll ping the reporter to see if he has any new information. > As a novice, I rather would not like to downgrade systemd or the > kernel -- as suggested -- since the system does not run troublefree yet > (there are still a lot of hardware issues and I don't want to open > another can of worms). About every user of Debian who runs a GUI system has pm-utils installed, and most also have systemd (which is somewhat controversial, but not let's go into that here) -- thus it's very likely the failure on the original reporter's machine was unique. Thus, I'd say you should be safe. Of course, if you happen to see this particular symptom (/var/log/pm-powersave.log growing without bounds) it'd be nice if you could tell us so. > You further write that "on systemd machines, keeping pm-utils is kind of > pointless" -- does this mean that I can do without it or should I > install an alternative? Suspend and hibernate do not work yet on the > machine ... systemd can trigger suspend and hibernate by itself, and most GUIs know how to do this via systemd. pm-utils are useful for scripting, but it doesn't sound like you have this particular need. As for suspend and hibernate not working on your machine, this is a notorious pile of issues, with which I'm not in a position to really help you. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts ⣾⠁⢰⠒⠀⣿⡁ productivity. You can read it, too, you just need the ⢿⡄⠘⠷⠚⠋⠀ right music while doing so. I recommend Skepticism ⠈⠳⣄ (funeral doom metal).
Bug#863679: moreinfo on #863679 (pm-utils)
Hi! On 29 May 2017 you reported: > Package: pm-utils > Version: 1.4.1-17 > Severity: critical > File: /usr/sbin/pm-powersave > Justification: breaks the whole system > > In the last few days, pm-powersave is being called roughly once per > second, which is logging to /var/log/pm-powersave.log until there's no > disk space left. I then tried reproducing this on a bunch of machines, in different configurations -- without success. pm-utils also has a quite big popcon, yet no one else mentioned this problem either. It's not good to have a Severity:critical bug left alone -- it spooks users who don't know what "unreproducible" means, not to mention anyone who looks at QA. Thus, I've just downgraded the severity -- but, could you tell if you had any luck reproducing it? Meow! -- ⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts ⣾⠁⢰⠒⠀⣿⡁ productivity. You can read it, too, you just need the ⢿⡄⠘⠷⠚⠋⠀ right music while doing so. I recommend Skepticism ⠈⠳⣄ (funeral doom metal).
Bug#878090: xchain: Couldn't execute /usr/bin/wish
Control: reopen -1 On Thu, Oct 12, 2017 at 06:58:04PM +0200, Andreas Ronnquist wrote: > After updating xchain to 1.0.1-8 in unstable, I cannot run it - it says > > "Couldn't execute /usr/bin/wish8.5" > > - Before the update it worked just fine. > > I believe this is because I had the wish which is provided by the tk > package wish provide a /usr/bin/wish, and xchain is depending > on either tk8.5 OR wish. > > So - the change in xchain 1.0.1-8 will only be fulfilled if the tk8.5 > is installed, but not if the tk package is installed. Oif. -- ⢀⣴⠾⠻⢶⣦⠀ We domesticated dogs 36000 years ago; together we chased ⣾⠁⢰⠒⠀⣿⡁ animals, hung out and licked or scratched our private parts. ⢿⡄⠘⠷⠚⠋⠀ Cats domesticated us 9500 years ago, and immediately we got ⠈⠳⣄ agriculture, towns then cities. -- whitroth on /.
Bug#944527: platform.linux_distribution is gone in 3.8
On Mon, Nov 11, 2019 at 05:18:47PM +0100, Håvard Flaget Aasen wrote: > I updated the package according to Matthias Klose's patch. Do you Adam, wish > to sponsor this package as well, so we can clear the bug? Sure, uploaded. As there's no version of python3-defaults that points to 3.8 anywhere I see, I did not bother re-testing -- if anyone of us did something wrong, we'll just upload again. > Is it possible that you can give me write access to the original repository, > so i can merge my changes? ✓ > On 11.11.2019 13:40, Matthias Klose wrote: > > Package: src:wand > > Version: 0.5.7-1 > > platform.linux_distribution is gone in 3.8. > > patch at > > http://launchpadlibrarian.net/450861215/wand_0.5.7-1_0.5.7-1ubuntu1.diff.gz Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.
Bug#930869: Please keep pm-utils
On Thu, Nov 14, 2019 at 09:13:51AM +0100, Andras Korn wrote: > I just stumbled on this bugreport. > > I'm a happy pm-utils user and would like the package to stick around. I use > it on dozens of computers ranging from servers to desktops to laptops. > > From reading the bugreport, there doesn't appear to be any identifiable, > specific, actionable reason for removing it, does there? There's none as far as I can tell, indeed. After a thought, even cleaning away the quirks would be counterproductive. They apply to old i386 machines that need real mode BIOS calls; while I and most of us have no such hardware to test, it's still used by some users. But keeping such i386 support is not _my_ itch to scratch, I personally wouldn't cry if those parts were trimmed away. Thus: * on old buggy hardware pm-utils works while new stuff doesn't * on old non-buggy, and on modern hardware, pm-utils works and is more convenient to use (eg. on headless boxes) Ie, this bug report is outright bogus. Without even a single identifiable actionable problem, there's nothing to fix. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.
Bug#897281: RM time
Control: clone -1 -2 Control: retitle -2 RM: doc-debian-fr -- RoQA; ancient docs Control: severity -2 normal Control: reassign -2 ftp.debian.org On 2018-05-01, Moritz Muehlenhoff wrote: > These docs have been updated the last time over 12 years ago, is this > actually still useful or rather misleading and should be removed? 19½ months later, it is clear no one cares about this package. Reassigning to our fine FTPfolks to do the last rites. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.
Bug#951522: FTBFS: wants long-removed emacs25
Source: a2ps Version: 1:4.14-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid this package build-depends on emacs25, which is long since gone. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-rc1-00073-g6af17278568f (SMP w/64 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#886202: FTBFS: chown: cannot access '.../fcoll_8cpp__incl.dot': No such file or directory
Source: zipios++ Version: 0.1.5.9+cvs.2007.04.28-10 Severity: serious Justification: fails to build from source Hi! I'm afraid your package fails to build on current unstable: dh_fixperms chown: cannot access 'debian/libzipios++-doc/usr/share/doc/libzipios++-doc/html/fcoll_8cpp__incl.dot': No such file or directory dh_fixperms: find debian/libzipios++-doc -true -print0 2>/dev/null | xargs -0r chown --no-dereference 0:0 returned exit code 123 dh_fixperms: Aborting due to earlier error Tried on armhf amd64. Log attached. Meow! -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 4.15.0-rc6-00023-g1414bf97abd7 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#885967: #885967: FTBFS: FAILED test of gethostid ENOENT
} PATH=`pwd`/bin:$PATH /bin/sh test/07/t0705a.sh } 2,3c2,3 } < (ENOENT) because there is no "hostid" regular file in the pathname "/etc" } < directory; did you mean the "hosts" regular file instead? } --- } > (ENOENT) because there is no "hostid" regular file in the pathname } > "/etc" directory } FAILED test of gethostid ENOENT Adrian Bunk wrote: > /etc/hosts is created in the postinst of the netbase package, > so "missing build dependency on netbase" would be another way > to describe the problem. Not sure if this is the best way to fix the failure, although it _would_ make the error message find /etc/hosts there so it can be suggested. This test is fragile, though -- if you have a file named /etc/hosting or such, it'll be picked instead of "hosts". The root cause, though, is that libexplain knows about gethostid, thus it can rule out an user making a typo -- the function looks for /etc/hostid and hothing else. Meow! -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices.
Bug#886202: same as #886120
This looks same as #886120 -- ie, a bug in either doxygen, graphviz or both. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out, ⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the ⠈⠳⣄ sky. Your cat demands food. The priority should be obvious...
Bug#886202: actually, gzipped
Not like #886120, sorry. The file doesn't exist under that name there -- but one .dot.gz does. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out, ⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the ⠈⠳⣄ sky. Your cat demands food. The priority should be obvious...
Bug#885967: #885967: FTBFS: FAILED test of gethostid ENOENT
On Fri, Feb 02, 2018 at 05:12:36PM +0200, Adrian Bunk wrote: > On Sun, Jan 28, 2018 at 05:55:19AM +0100, Andreas Beckmann wrote: > >... > > Can this bug be reproduced in stretch or jessie buildd chroots - or can > > we tag it sid+buster? > > It cannot even be reproduced in the sid buildd chroots, > only with "debootstrap --variant=minbase" - fixing in > jessie or stretch is therefore not required. ｢debootstrap --variant=buildd｣ → no /etc/hosts either. This said, your fix works for now, a better one is a matter for the upstream. And as libexplain seems to be dead upstream, despite it being a nifty concept, no one is likely to use it in new project, meaning the issue will fix itself. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration ⣾⠁⢰⠒⠀⣿⡁ camps is back. What about KL Warschau (operating until 1956)? ⢿⡄⠘⠷⠚⠋⠀ Zgoda? Łambinowice? Most ex-German KLs? If those were "soviet ⠈⠳⣄ puppets", Bereza Kartuska? Sikorski's camps in UK (thanks Brits!)?
Accepted vusb-analyzer 1.1-7 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Feb 2018 00:28:00 +0100 Source: vusb-analyzer Binary: vusb-analyzer Architecture: source Version: 1.1-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: vusb-analyzer - tool for visualizing logs of USB packets Closes: 884998 Changes: vusb-analyzer (1.1-7) unstable; urgency=medium . * QA upload. * Drop Recommends on removed python-gnome2. (Closes: #884998) * dh 11. * R³. Checksums-Sha1: 7dab8f51681a66885a4f27956bb458e93b05a97e 1802 vusb-analyzer_1.1-7.dsc a8c9d324ecccf93ff2bd744ba477e312d3d18017 7732 vusb-analyzer_1.1-7.debian.tar.xz 5780da588df162714016f5e7088d9ffb4bb999d7 6016 vusb-analyzer_1.1-7_source.buildinfo Checksums-Sha256: f152467812497ed57347c4ac10f08631890217b0cd44c2b89d1f01b354ffa3e0 1802 vusb-analyzer_1.1-7.dsc 539997552194c663804762a5abadd66361361258ce927bb02d90a470935a5cb7 7732 vusb-analyzer_1.1-7.debian.tar.xz 310eac994cc713a28ffe65516bc8615e85b00080dd47eaf9abe53cd9543c1aa8 6016 vusb-analyzer_1.1-7_source.buildinfo Files: 9a7b7402a2a550aa2b10b6ea33012908 1802 contrib/utils optional vusb-analyzer_1.1-7.dsc 8c2b397a95b2b647bd7094cc8bea539f 7732 contrib/utils optional vusb-analyzer_1.1-7.debian.tar.xz f584c22a217cdd172425dd0eae2e8318 6016 contrib/utils optional vusb-analyzer_1.1-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlp2RYwUHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH6VBBAA9p+NbDkREE/x3+pENJxSyJ/McXkt 2xniF7Uk9ArbMSxE5FiMdIpsI1XYOWHxLezgV3jK8l356sQJ5guFZUnvHceeD+Pq NxN0fcH8jx6L5QnWLMBBsj6bQUmBD85tQatRJarv0CTGalgwQpHUntCAyXLGV9lz kGXh1W1ftOA53aNVkP9Av6DAa6kokqXStK6ExAcKnFnCAII84WOW9KRwAwOrBiAH 2oSpFdsYEnATXN9v3NSD/tgTgPbY7sMexWW3jv4e3GoFd1tQHMqU7XwqyQKaub+j LUouFU9f7pRKl7b0oi7kFaVgaizVvLBCiZxMV59q//KOIxgNmCh4mQOmj2D6qUZs nTGMuKvQ3ChgCeVq01o9YgebvEjhGRSTW3W41cFIYqJ8wUgRB7OjW5+VdeO9tDwT L9yD9pV3K1xdb8PVRvD3xrXwONwjW2e6R1Ubl1DfF+RxsllnMWxDuBpFgsOvgUeT VHjNVauztZFcC36H+SEyNXOGG2Oc31Dpq60BaONlhLSbGODteod6zVQyCRYPeXT4 sTam6XGstQq5uutPHfylU7++bJ6hTckqgFAjbv2acid//3U+L+tNdpjCI1W097Us 6SsFL43u+yIgaUtNffdPIcJVlX3dbHr8GMpoPYJw5d7N1yeJNsvPx0LmQhDPX809 UIxpBArqSpp36pY= =NmV6 -END PGP SIGNATURE-
Bug#890135: glhack: tramples upon display (xrandr) settings
Package: glhack Version: 1.2-4 Severity: normal If your display requires any non-trivial xrandr settings (such as most multi-monitor setups), glhack replaces them on startup with some nonsense: its full-screen window partially out of screen, strange rotation, reflection and resolution. Even worse, not only it doesn't restore this upon exit (what's quite notorious among SDL1.2 programs) but also requests the bogus values to be saved. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.2+ (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages glhack depends on: ii libc62.26-6 ii libgl1 1.0.0-2 ii libpng16-16 1.6.34-1 ii libsdl1.2debian 1.2.15+dfsg2-0.1 glhack recommends no packages. glhack suggests no packages. -- no debconf information
Accepted glhack 1.2-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Feb 2018 14:18:36 +0100 Source: glhack Binary: glhack Architecture: source Version: 1.2-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: glhack - Fullscreen SDL/OpenGL version of NetHack Changes: glhack (1.2-4) unstable; urgency=medium . * QA upload. * R³: yes. * dh 11. * Priority: optional. Checksums-Sha1: 792c7d0f8baa993f0402f32bd65c77457abbdf51 1772 glhack_1.2-4.dsc 90e5b20f010e565a7dbefc88142845d8ef457a26 21752 glhack_1.2-4.debian.tar.xz 65eb4a585aadfabf6de592b291e4a6602952e740 5566 glhack_1.2-4_source.buildinfo Checksums-Sha256: 372ca6cc71de72a360de6c952c4c3cd873db306a79ed055c5eccce8b7917a647 1772 glhack_1.2-4.dsc 25f43b0cede71cf73573c814e3658ab2644b66de3957202c7eb24989fc6319dc 21752 glhack_1.2-4.debian.tar.xz a7f5c507c53d3a70879458342094421beaea0fff1dcc745fe43ab6cdd9b084e7 5566 glhack_1.2-4_source.buildinfo Files: 94cfaab5855a2d8f865e872ff151d565 1772 games optional glhack_1.2-4.dsc 04c32f75d68421a0dd656b9dc5f65172 21752 games optional glhack_1.2-4.debian.tar.xz 6b482323ddab8856a767e0492cd7a544 5566 games optional glhack_1.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlqAQtwUHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH6TPQ/+I9bLZE0Szu2VNePA8ZMpmbxaAKUj 22JZaUcjEIHTpUPqvCloNinFjkfH6jqaAp4UrezQrGghsuuPkfOG9k2URP+uqQIH AMg/g9H6sQs5BUZfjd9UCys5NP7gAdiz524Qp0nTm5mW8+NqLAQeWmSLoUchTj5C HbQX2ehYYyH79R1IbBEAlPQ6dHggo9wI80oJhaoE/hC4rT3xWOHj0OJOF8j+jyN8 9SFdvkDwW5bss7isCJH9vDEwPTFHPbzsPaCb+ZOyG0EGifgPuOaZC7LC4tJjMQGr 5YY414OPh330y1e4+GCrbcq28tTKZv/+dap19lbPcmGTJEW/oSOVLh5FWkWxI7gA YTNWOgJA3ZV54psFDi4MBBE3Z3ItAGGJuQJvbPkeLG36MGM2FRUbKa4m8bJR0Win EHq4TQQRmHRpCOWDoNd809fZOO4xAo4cbJAkfNJKf24bGC8nNaOPT3vRRUdGGZeH 4UEiaIhpOa2nbRiizlHWNBEFDHcoDf9BrFB7WjXNi1SWRlvaeoToWYqMxceyzV7t 1+xxKxysTC0ImpO7qfey1b1sTEV+DS1tcMR5ugwoaXHtSKvVH6FTZgHfHRPN4pwA wNKlJq+ZWkxQEsSu5vP92jZ2wdCHDjc3uQ42LrMawiqMkvSB/sSL4X7MnTBwf3yT 8sfG3iO142r8ylo= =KQA8 -END PGP SIGNATURE-
Accepted splitvt 1.6.6-13 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Mar 2018 00:03:37 +0100 Source: splitvt Binary: splitvt Architecture: source Version: 1.6.6-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: splitvt- run two programs in a split screen Changes: splitvt (1.6.6-13) unstable; urgency=medium . * QA upload. * Compat 11. * Rules-Requires-Root: yes. * Move Vcs to Salsa. Checksums-Sha1: 91ba4d21c6cc607d765fe8e7c80b3f8ff7fc22a6 1907 splitvt_1.6.6-13.dsc 724485db9a3be8bf639e078851964599a49f3ee5 16896 splitvt_1.6.6-13.debian.tar.xz 90acd16365031c1d450f5a49df9cfde0cc0bd548 5435 splitvt_1.6.6-13_source.buildinfo Checksums-Sha256: 054bb613641b93b57ee8d7e01104dbda1dcee055bc77f45de23ed4c7252342d6 1907 splitvt_1.6.6-13.dsc 41a0d60ca73b6bcd4f0d62051b6861a8b9ba58950955176926c402661a7c4ef0 16896 splitvt_1.6.6-13.debian.tar.xz fb5269c269ca50da2956e7b6c4d468b16c41c73b7340998c7387fb42463d407b 5435 splitvt_1.6.6-13_source.buildinfo Files: 59fa282bf1e209364a2fc0caa88bd52f 1907 utils optional splitvt_1.6.6-13.dsc a4e955c79a6077b92638497a2c9c5d01 16896 utils optional splitvt_1.6.6-13.debian.tar.xz 598583feaae69feeedbd7910fe86677a 5435 utils optional splitvt_1.6.6-13_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlqXNV4UHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH5BGBAAzYEwFg5y2KTGS13DXcNEYSFRvWcL Z+56apAYkrSG7U8tWBRVNkQ9VUfNDsdaHfne5cQHveq5uWldlp+XJvBfNR0SoLXh ZRWJ0IEDYSEVCh484eRoQnY7WHkA/Cmz73MQWJX2S/Afvq1rp8IH0YUJmN8iHvjf TDWdU5/rcFOFWqq2fsauQroh9uyB7kIomUrRfWRc9hJ+z5eyB7CP2xQy8QOYZ2Dp ezwfgWAqMgst2C5VK1/Ru01nAZm3ULM+4hIAnWh8+SDnWJJYBdBMOchbm0GEmZ6e zjO5gMtglFn8nai6GHeYy0Dx5GZYdW6uVhzOPXOhL+MoRneUo+80K/CIQEm0SmEM FXnSshlHdesb4a4sj7S3Iw+PQ8IyA183CTEwmJTmL/Hu0hN0PgzYqkTecdenLEE/ MIvzhncUOEBdZli9AkNjiEB91DVlAMAIypxyqEFKnPYVhkksb4uGXf1uXq/GVEko nyCxrHVqei90QBcVbs66YAmvrDnhQhnYPYcaqBnr8oYN/03731ODYftSWuT/adfg p8+tv60U3nSf+Kx+NTmr6XI0UHQyslaSAbU1JuRCrgRfZvnPWnWEnOarj3A5oNXr Uqla+zS71QrJtImi/8tWmCPIOxGHZ37+OQ/Wo79UI4xDwgmzIZ3403qWKxnTyqyo 2SenPl8uF0EnuJY= =iQYF -END PGP SIGNATURE-
Accepted maelstrom 1.4.3-L3.0.6+main-9 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Mar 2018 01:04:45 +0100 Source: maelstrom Binary: maelstrom Architecture: source Version: 1.4.3-L3.0.6+main-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: maelstrom - Arcade-style game resembling Asteroids Changes: maelstrom (1.4.3-L3.0.6+main-9) unstable; urgency=medium . * QA upload. * Compat 11. * Rules-Requires-Root: yes. * Drop redundant B-Dep on autotools-dev. * Drop Debian menu. Checksums-Sha1: 833afc5ee25a9028e52bca79055023a858ed868b 1882 maelstrom_1.4.3-L3.0.6+main-9.dsc 4e053805cbbff2fc5610305e5d20750dccd7fac3 22764 maelstrom_1.4.3-L3.0.6+main-9.debian.tar.xz e30321f08f9febf97fc85b78b785b842dae85bd9 5436 maelstrom_1.4.3-L3.0.6+main-9_source.buildinfo Checksums-Sha256: 7d58327b6c5b4cb91402de9a8b14df422c4504e276e11246dc6711ece63da672 1882 maelstrom_1.4.3-L3.0.6+main-9.dsc cb3cd8ba7b0c563b55245454dc9ea88cd832a53cd28ecca2c5979b9b7914f54a 22764 maelstrom_1.4.3-L3.0.6+main-9.debian.tar.xz 948e3becfcfca89cc2171bb50549cdb8845d336af506122c3054a07065fec414 5436 maelstrom_1.4.3-L3.0.6+main-9_source.buildinfo Files: 0c115d1f03a755b185cfad4f7b532664 1882 games optional maelstrom_1.4.3-L3.0.6+main-9.dsc 2b00585b18b9c8dee0106e766607c631 22764 games optional maelstrom_1.4.3-L3.0.6+main-9.debian.tar.xz 7ba31b2b27e07bf00d02f745290d99af 5436 games optional maelstrom_1.4.3-L3.0.6+main-9_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlqXQ8IUHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH4TQg//VB9effH97xq2UEMIonXFaGj1/xl9 2ypYw1T+2neudP+XRIJNRItd1FKEBkn1IDuH0JmpYy2GgNkc77/UYYD7i10JWGvh w2//W5eyMA9NgE8MjPSN1RiMz9Kv57IZ0+J9bAQZgem9zwfdrDbg5A0MfRh3p9qY x4ZfRVqkMQyZ0yPKqHXy2sXqGF0qrETswRktajhULtl4wduOCl/zrSEH7EnmYIeq CU3K5vYJ1Fi9Tcu9Dnq9xjApeI6yYfughSF4fi5TH5ZCQm6AFK4MK3h+g5uvmRtQ CmPxXHDJcDizPzuJMnJF5XkTngs6nCHs0ITUCJVLqgt3l5mbzsawxIRa9EVuANRt i/ABGlYQ/+L4NrqQ6CO4xsG27EgsOh08xrBPEp3iiLzdfDB9rNcV4Bes7U/PZOqP Z9jXQ1X5g3UeGmbtVdCbLri7WDlpg4KxrvYs6HCXhEwOXcgPjduO8SfrKSBYUb+i FiT8npuUrafQ6ySEVQNpf44BiWu9D+sN2toOfTxeZ7d9MZBGmb7+JRctHog5pWYF JV+6fsmXo6PCXTksKmidNnHDAm2waxBOktRyyN420LHNJ3npk9uLs8GmX+iQ9/XS SNdWgTC8czeuhv+mnWGPSJJLsqgT1vnr6mE7inc/F9tebsdqq+p86dwPr4SM5tut tTx9FPym0oOiXLs= =U4/g -END PGP SIGNATURE-
Accepted xsoldier 1:1.8-5 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Mar 2018 01:36:53 +0100 Source: xsoldier Binary: xsoldier Architecture: source Version: 1:1.8-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Description: xsoldier - shoot 'em up game with the "not shooting" bonus Changes: xsoldier (1:1.8-5) unstable; urgency=medium . * QA upload. * Move the Vcs to Salsa. * Compat 11. * Rules-Requires-Root: yes. Checksums-Sha1: 8e71a07003c0f7fea72ab9d72997a209b3fad1bc 1989 xsoldier_1.8-5.dsc e9b7298fccdbdb649c11d179c7b2358687dcda64 9856 xsoldier_1.8-5.debian.tar.xz da05c40227a2d84266efd3b0b31773f682c6c9f1 5377 xsoldier_1.8-5_source.buildinfo Checksums-Sha256: b7fa42d8ca9e333253f4c8e9e14f5e181499690446f35d889f6d13f646bf98a3 1989 xsoldier_1.8-5.dsc bbc32478c9ead596569b7dc2392b9bbd19e713161442a03cdaade9b2e57dfeda 9856 xsoldier_1.8-5.debian.tar.xz 794e286a068a8af4a3e0b9b96c7c3c4287c3a80a5579c945c618840cef398291 5377 xsoldier_1.8-5_source.buildinfo Files: abf9f19da013f7a3d46fc577e6b1dc8c 1989 games optional xsoldier_1.8-5.dsc fba4606fbf632b7f7179905e8626a79a 9856 games optional xsoldier_1.8-5.debian.tar.xz 9f7f6daaff70d4091ab136c595be3c01 5377 games optional xsoldier_1.8-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlqXS3wUHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH6lTRAA9jzLwoU+BBPA1YpMdbo0PpR1hVS7 a4O0fpwkBk/RZAIuIRVWX3EYZR1akAxbs8mxsIA9XLpTeNU59pz0SIYGbJaCPUMm 90n0hihPoSA864SRqQ2sRpcrmbqGBDQb5VQUu8OFsWzfaTx6DoNNqu55ZzCi69PM edsLe+JHmvKkcIC7sf6WOhL9YfP62CHuDF+0b7Z5+AHGEVxTnMfQNEV+mIsReA3y RJAYCqAtEctwtDxggs/MbTB2e72qsK25LrDG4s4KFiW1ov3XqNr6dLL9spOi9nJJ 4lOnrpOhSBNNqX4gbtE0LdoOJErncE4aPCC5s1awKiACGwA4+iNcYhSUGPwMKkFs W6aCAvNd1y6b5cMOHZTYf7bQic4kBLhTDkrsojCGy6l3ZcFLjZ4vJFjAjjls0Y4N zjhsLzcJsp9MAtUervA+lH6J/czqq2n6K7226fBuuaSR/l4V9TpBaOYJy117LGan VVcS+tbXekdOPFwKgeOE+e+KdJNt5eEYVFbj08HryhriO3y1v/erB2hyStpXBnXY c1KpC6o/BOu2W/O2QmzORmAl373iWirjoZYabJwRQGI6tOaxBp0FL6vUkYxygRNA bHWTPNIqZhOpCWq2BJr2HxVl8ZuvdUWZtoV77HqP9GID6d1pakPuix5EQqp0mopZ 1NXMBRQxoIbR0k0= =WV16 -END PGP SIGNATURE-
Bug#818787: Mar 2016 rebuild results
> > In other words, my solution to this bug would be to make doxygen exit with > > an > > error code when calling dot fails. Then make will fail, it's an FTBFS, it > > gets > > fixed, and everyone is happy. > I've started a rebuild of all 552 packages in unstable that build-depend on > doxygen or anything that recursively pulls doxygen (eclipse-eclox doxyqml > doxygen-latex doxygen-gui doxygen-dbg python3-breathe python-breathe). > My build environment has a /usr/bin/dot that aborts the build when called, > which should detect this error even if doxygen output is redirected or > mangled. I'll let you know how widespread the FTBFS are when finished. > On a slow-ass machine, 57 builds done in 2.5 hours so far, so it'll take a > while. Then, in https://lists.debian.org/debian-devel/2016/03/msg00288.html but not CCed to this bug, there's: =✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂= Here are the results: 60 packages call /usr/bin/dot without depending on graphviz. During the rebuild, there was a number of unrelated FTBFSes (7 failed, 36 attempted), some of them might possibly try calling dot later. I'll investigate/retry/file bugs todorrow. alsa-lib apr apr-util asl cmocka coinor-ipopt cppunit frei0r gammu gazebo gconfmm2.6 gnuradio gtkspellmm hamlib jaula libaccounts-qt libaqbanking libassa libccrtp libevhtp libgadu libgnomecanvasmm2.6 libgpiv libgwenhywfar liblightify libmediainfo libmpdclient libmusicbrainz3 libopenobex libpqxx libsdl2 libsidplayfp libssh libsyncml libwibble linphone log4c lucene++ mpqc netcdf netcdf-cxx nifticlib open-vm-tools openafs openigtlink opensurgsim pidgin qca2 roboptim-core scim sdformat silly sipxtapi sombok tango thepeg vdk2 wimlib wxwidgets3.0 zipios++ =✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂=✂= Obviously, two years later, this list is outdated, but without an incentive to fix any of those, the scale should remain similar. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄ A master species delegates.
Bug#886120: doxygen = scapegoat ?
On Wed, Mar 14, 2018 at 09:34:36PM +0100, Paolo Greppi wrote: > @kilobyte, let me see if I can understand your purpose with this bug report. > > What happened is: > 1) you find a serious bug in ctpp2 (popcon: 14) > 2) you decide it's RC > 3) it's doxygen fault so you reassign it to doxygen (popcon: 8381), and it > stays RC > > Now let's look at the effect of all this: > 1) doxygen is currently orphaned (https://bugs.debian.org/888580) > 2) therefore nobody will take care of this unless someone adopts it > 3) the average Johanna trying to decide whether she should adopt it will >be repelled by this RC bug and the perspective that anybody anytime can >file RC bugs because any obscure package fails to build and it's >doxygen fault > 4) consequently doxygen will not make it to buster > 4) ctpp2-doc is also dropped from stable, and all other packages that >depend on doxygen for building, which if I am not mistaken are 443: > > grep-dctrl -FBuild-Depends doxygen -sPackage /var/lib/apt/lists/*Sources | wc > 443 8868612 > > Is that your wish ? Your reasoning is: https://en.wikipedia.org/wiki/Appeal_to_consequences which is not a reason for dismissing a bug. It _may_ be a valid reason for the Release Team to mark the bug as buster-ignore, or to temporarily reduce its severity, but this won't make it disappear. The problem is not that random packages sometimes fail to build (not just ctpp2, but obscure races are pretty hard to reproduce and/or debug). The problem is that packages _succeed_ where they shouldn't. Doxygen turns bugs that usually would be obvious, easy to fix breakage into random rare failures that appear to build the vast majority of the time. And, packages that have enough impact (such as doxygen) are already immune to autoremoval, which addresses your 4) and 4). Because of ignoring the failures, we don't know how widespread problems like misgenerated output that's then (correctly) rejected by graphviz, are. Only then we'd be able to correctly assess reasonable severities to individual bugs. Here, doxygen causes at least one package to FTBFS which might or might not be RC (we'd know more only once it's no longer leakily papered over). Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄ A master species delegates.
Bug#834577: needs more work
lamby wrote: > I believe there is a typo in debian/rules: > > override_dh_autoconfigure -> override_dh_auto_configure > > Patch attached. I'm afraid your patch is 0 bytes long. If what you intended is the obvious one character change, then plugwash tried it in #897114: } The only tricky bit was that there seems to have been a typo in } debian/rules, there was a target called override_dh_autoconfigure which I } presume was a typo for override_dh_autoconfigure , I tried fixing said } typo but that seemed to cause more problems than it solved, so I left it } alone and added my own override target. You might want to consider either } fixing or removing the dead code. Thus, it would need more attention at than my drive-by QA upload to fix the FTBFS has tuits allotted for. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Certified airhead; got the CT scan to prove that! ⠈⠳⣄
Bug#612950: bug still valid
Control: notforwarded -1 Control: tag -1 -wontfix Was marked such by bts-link, wontfixed not because of the bug's value, but because of upstream having switched to systemd. But Debian is not Red Hat, and carries inits that are not , and needs pm-utils or an equivalent. I have no real opinion about this bug, though, all three of my laptops using eMMC not SSD. But it needs to be decided on its merits. Meow! -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices.
Bug#897761: patch
Control: tags -1 +patch
Here's a patch for this one. Alas, fixing the gcc-8 FTBFS uncovers an
unrelated FTBFS with tex crap, which would need to be fixed as well.
--
⢀⣴⠾⠻⢶⣦⠀ So a Hungarian gypsy mountainman, lumberjack by day job,
⣾⠁⢰⠒⠀⣿⡁ brigand by, uhm, hobby, invented a dish: goulash on potato
⢿⡄⠘⠷⠚⠋⠀ pancakes. Then the Polish couldn't decide which of his
⠈⠳⣄ adjectives to use for the dish's name.
--- gnuift-0.1.14+ds.orig/libGIFTAcDistanceMatrix/include/CPersistentMatrix.h
+++ gnuift-0.1.14+ds/libGIFTAcDistanceMatrix/include/CPersistentMatrix.h
@@ -58,7 +58,7 @@ public:
bool putLineVector(long inY,
CLineVector const& outVector);
- bool setValue(long inX,
+ void setValue(long inX,
long inY,
T const& inValue);
@@ -190,19 +190,17 @@ bool CPersistentMatrix::putLineVector
}
template
-bool CPersistentMatrix::setValue(long inX,
+void CPersistentMatrix::setValue(long inX,
long inY,
T const& inValue){
if(!mContent)
-return false;
+return;
mContent->seekp((inY * mXSize + inX) * sizeof(T) );
mContent->write(&inValue,sizeof(inValue));
mContent->flush();
-
- return (*mContent);
}
///
--- gnuift-0.1.14+ds.orig/libGIFTAcDistanceMatrix/include/CPersistentVector.h
+++ gnuift-0.1.14+ds/libGIFTAcDistanceMatrix/include/CPersistentVector.h
@@ -59,7 +59,7 @@ public:
bool read(istream& inStream,
long inNumRecords);
///
- bool write(ostream& outStream)const;
+ void write(ostream& outStream)const;
///
void init(T const& inDefaultValue);
};
@@ -117,7 +117,7 @@ bool CPersistentVector::read(istream&
}
template
-bool CPersistentVector::write(ostream& outStream)const{
+void CPersistentVector::write(ostream& outStream)const{
for(typename CPersistentVector::const_iterator i=this->begin();
i!=this->end();
i++){
@@ -125,7 +125,6 @@ bool CPersistentVector::write(ostream
*i);
}
outStream << flush;
- return outStream;
}
#endif
Bug#906032: FTBFS: LaTeX first run problem.
Source: gnuift Version: 0.1.14+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! After applying the patch for gcc-8 FTBFS (#897761), the build fails later on due to SGML issues: Processing file configuring-and-hacking-the-gift.sgml Use of uninitialized value in hash element at /usr/share/texinfo/Texinfo/Structuring.pm line 687. /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1297: warning: @appendix missing argument /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:919: @node `plug_in_fo-cc' previously defined /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:636: here is the previous definition as @node /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1023: @node `Some summarizing remarks' previously defined /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:747: here is the previous definition as @node /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1041: @node `Typing' previously defined /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:765: here is the previous definition as @node /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1049: @node `How to obtain parameters' previously defined /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:773: here is the previous definition as @node /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1062: @node `Administrative code' previously defined /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:787: here is the previous definition as @node /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1076: @node `Interfacing with query engines' previously defined /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:800: here is the previous definition as @node /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1098: @node `Makefiles' previously defined /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:822: here is the previous definition as @node /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:636: warning: node next `plug_in_fo-cc' in menu `Static linking' and in sectioning `CAFHierarchy' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:636: warning: node up `plug_in_fo-cc' in menu `libGIFTQuHierarchy browsing fixed hierarchies' and in sectioning `libGIFTAcHierarchy a simple hierarchy accessor' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:747: warning: node prev `Some summarizing remarks' in menu `libGIFTQuHierarchy browsing fixed hierarchies' and in sectioning `libGIFTAcHierarchy a simple hierarchy accessor' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:747: warning: node up `Some summarizing remarks' in menu `How to write an Query Proccessor plugin' and in sectioning `How to write an Accessor plugin' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:765: warning: node `Accessor lifecycle' is prev for `Typing' in menu but not in sectioning /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:800: warning: node next `Interfacing with query engines' in menu `CQuery lifecycle' and in sectioning `Accessor lifecycle' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:810: warning: node `Typing' is next for `Accessor lifecycle' in menu but not in sectioning /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:822: warning: node up `Makefiles' in menu `How to write an Query Proccessor plugin' and in sectioning `How to write an Accessor plugin' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:873: warning: node next `libGIFTQuHierarchy browsing fixed hierarchies' in menu `Some summarizing remarks' and in sectioning `' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:947: warning: node prev `Static linking' in menu `plug_in_fo-cc' and in sectioning `' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1086: warning: node prev `CQuery lifecycle' in menu `Interfacing with query engines' and in sectioning `' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1086: warning: node up `CQuery lifecycle' in menu `Some summarizing remarks' and in sectioning `' differ /tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1023: node `' lacks menu item for `CQuery lifecycle' despite being its Up target /tmp/linuxdoc-tools.en1t
Bug#913249: needs Depends: perl
Fix: Depends: perl Term/ReadLine.pm lives in perl-modules-5.28, but its description wants packages to depend on "perl". Let's do so. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Ivan was a wordly man: born in St. Petersburg, raised in ⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned ⠈⠳⣄ to the city of his birth to die.
Bug#886120: Doxygen makes ctpp2 randomly FTBFS, syntax errors, hides problems
On Sat, Dec 01, 2018 at 04:17:13PM +0100, Agustin Henze wrote: > Control: tag -1 +moreinfo +unreproducible > Control: severity -1 normal > > Hi Adam, > > I have been trying to reproduce the FTBFS of the cttp2 package (more than 20 > times) you are saying without success. I've used the following script to do > that That's the whole problem! The FTBFS is random -- comes and goes; on current unstable I can't seem to reproduce the build failure on either the amd64 machine nor the armhf one; when something else changes the issue will come back. Whether it ends up in a build failure or not depends on _something_ that might be phase of the moon, some race inside the build that semi-reliably gets won by one of the sides for a given state of the toolchain, etc. But that's only a symptom, not the cause. The cause reproduces reliably: Running dot for graph 763/1263 Running dot for graphError: /<>/doc/html/a01347_a236ee5e58731c059affd0e50b4d0aee4_cgraph.dot: syntax error in line 18 near '-' error: Problems running dot: exit code=1, command='dot', arguments='"/<>/doc/html/a01347_a236ee5e58731c059affd0e50b4d0aee4_cgraph.dot" -Tsvg -o "/<>/doc/html/a01347_a236ee5e58731c059affd0e50b4d0aee4_cgraph.svg"' error: Problems running dot: exit code=1, command='dot', arguments='"/<>/doc/html/a01347_ab353c212082bbd71bd9c3c69f136f3bf_cgraph.dot" -Tsvg -o "/<>/doc/html/a01347_ab353c212082bbd71bd9c3c69f136f3bf_cgraph.svg"' Error: /<>/doc/html/a01347_a39915107bcf5ac712b6a28163a2653e2_cgraph.dot: syntax error in line 14 near '-' error: Problems running dot: exit code=1, command='dot', arguments='"/<>/doc/html/a01347_a39915107bcf5ac712b6a28163a2653e2_cgraph.dot" -Tsvg -o "/<>/doc/html/a01347_a39915107bcf5ac712b6a28163a2653e2_cgraph.svg"' Error: /<>/doc/html/a01347_ad9290c6979f4d804ed33483beb548c14_cgraph.dot: syntax error in line 34 near '-' error: Problems running dot: exit code=1, command='dot', arguments='"/<>/doc/html/a01347_ad9290c6979f4d804ed33483beb548c14_cgraph.dot" -Tsvg -o "/<>/doc/html/a01347_ad9290c6979f4d804ed33483beb548c14_cgraph.svg"' Error: /<>/doc/html/a01359_ae99959d42c4f7f886dd420aa119b29e2_cgraph.dot: syntax error in line 75 near '-' error: Problems running dot: exit code=1, command='dot', arguments='"/<>/doc/html/a01359_ae99959d42c4f7f886dd420aa119b29e2_cgraph.dot" -Tsvg -o "/<>/doc/html/a01359_ae99959d42c4f7f886dd420aa119b29e2_cgraph.svg"' Error: /<>/doc/html/a01359_a98233ab4534754a671fae8ab588ef5e7_cgraph.dot: syntax error in line 49 near '-' error: Problems running dot: exit code=1, command='dot', arguments='"/<>/doc/html/a01359_a98233ab4534754a671fae8ab588ef5e7_cgraph.dot" -Tsvg -o "/<>/doc/html/a01359_a98233ab4534754a671fae8ab588ef5e7_cgraph.svg"' Error: /<>/doc/html/a01359_aa0295dae085e2be96737ed0fd19ad714_cgraph.dot: syntax error in line 49 near '-' (and so on) > For this reason I'm changing the severity, feel free to provide more > information about the FTBFS and what environment are you using to get them. The proper severity is RC: silently ignoring errors here: * is a violation of a "must" clause of the Policy * notoriously wastes maintainers' and QA's time dealing with heisenbugs like this FTBFS of ctpp2 > Also, please find more answer below > > On Fri, 2 Feb 2018 02:45:00 +0100 Adam Borowski wrote: > [...] > > As I don't see anything obvious in the way ctpp2 calls doxygen + graphviz, > > there's no point in having the bug stay here. The culprit here is doxygen > > as it's where the syntax errors come from. > > > > Generating calError: > > /<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.dot: > > syntax error in line 67 near '-' > > error: Problems running dot: exit code=1, command='dot', > > arguments='"/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.dot" > > -Tsvg -o > > "/<>/doc/html/a00332_a3c04138a5bfe5d72780bb7e82a18e627_cgraph.svg"' > > Running Error: > > /<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.dot: > > syntax error in line 8 near '-' > > error: Problems running dot: exit code=1, command='dot', > > arguments='"/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.dot" > > -Tsvg -o > > "/<>/doc/html/a00603_a6824947e6525f4afddb3bfa083f950d9_icgraph.svg"&
Bug#749559: sysvinit: Can't power off jessie from gnome poweroff menu
On Wed, Jan 02, 2019 at 09:59:55AM +, Mark Hindley wrote: > control: reassign -1 systemd-shim systemd-shim has been already removed from unstable. > On Tue, Jan 01, 2019 at 10:38:24PM +, Dmitry Bogatov wrote: > > Reassigning to elogind, that, as I understand it should provide required > > compatibility layer. > > Dmitry, > > elogind can provide this functionality now. However, isn't wasn't even present > in the archive for Jessie! Yet it doesn't actually work yet: the icon is no longer grayed, but after logout, nothing happens. This is the reason you provided elogind-dev packages so policykit can get elogind support, but it doesn't have it yet. > I agree with Simon that, for the subitter, this seems likely to be a > systemd-shim bug. Yeah, but (for different direct causes) elogind suffers from it as well. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Hans 1 was born and raised in Johannesburg, then moved to Boston, ⣾⠁⢠⠒⠀⣿⡁ and has just became a naturalized citizen. Hans 2's grandparents ⢿⡄⠘⠷⠚⠋⠀ came from Melanesia to Düsseldorf, and he hasn't ever been outside ⠈⠳⣄ Germany until yesterday. Which one is an African-American?
Bug#930869: Don't release with buster
On Fri, Jun 21, 2019 at 07:42:00PM +0200, Michael Biebl wrote: > Package: pm-utils > Version: 1.4.1-18 > Severity: serious > > As former maintainer of pm-utils, I don't want to see pm-utils released > with buster. > pm-utils is a set of hacks/scripts which back in the days were necessary > to successfully suspend/hibernate your system. But, do we even have an alternative for suspending remotely? Until that is present, pm-utils is needed -- and even then, it should preferably be replaced by wrappers, not removed. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Autotools hint: to do a zx-spectrum build on a pdp11 host, type: ⢿⡄⠘⠷⠚⠋⠀ ./configure --host=zx-spectrum --build=pdp11 ⠈⠳⣄
Bug#930869: Don't release with buster
On Fri, Jun 21, 2019 at 08:53:32PM +0200, Michael Biebl wrote: > Am 21.06.19 um 20:05 schrieb Adam Borowski: > > But, do we even have an alternative for suspending remotely? > > What do you mean by that? So here we have a computer. No GUI tools. No emulation of GUI tools. And I want to suspend it (then WoL back). > > Until that is present, pm-utils is needed -- and even then, it should > > preferably be replaced by wrappers, not removed. > > Not really, pm-utils is not needed. Could you then please educate me what the replacement is? Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. ⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift ⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters ⠈⠳⣄ relevant to duties], shall be punished by death by shooting.
Bug#930869: needed then
Control: severity -1 wishlist Control: retitle -1 needs purging of quirks On Fri, Jun 21, 2019 at 10:22:16PM +0200, Michael Biebl wrote: > >>> But, do we even have an alternative for suspending remotely? > >> Not really, pm-utils is not needed. > > Could you then please educate me what the replacement is? > > I'm not here to educate you. > You are too smart anyways. Thanks for kind words. No alternative means we can't remove pm-utils. You're right that the quirks are obsolete and unmaintained, and should be purged away. There's no hope for machine vendors' ACPI implementations to get into sane states within our lifetime, but handling the brokenness is done in the kernel these days. But, such clean-up is not a task for deepest parts of the freeze. For now, pm-utils works fine, at least within my use cases. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!? ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din ⠈⠳⣄
Bug#930869: Processed: severity of 930869 is serious, retitle 930869 to Don't release with buster
On Sat, Jun 22, 2019 at 08:06:08AM +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > severity 930869 serious > Bug #930869 [pm-utils] needs purging of quirks > Severity set to 'serious' from 'wishlist' > > retitle 930869 Don't release with buster > Bug #930869 [pm-utils] needs purging of quirks > Changed Bug title to 'Don't release with buster' from 'needs purging of > quirks'. Could you please name _any_ problem with pm-utils that would warrant emergency, 4-days-before-absolute-freeze, removal of it from Buster? Especially that you do no longer use it, while I use it daily -- and at least for me, it works, unlike a certain alternative you seem to imply, -- and I am not aware of pm-utils having regressed. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start ⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax ⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child: ⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall
Bug#930869: Don't release with buster
Control: severity -1 wishlist On Thu, Jun 27, 2019 at 09:00:38PM +0200, Michael Biebl wrote: > Am 24.06.19 um 00:46 schrieb Ivo De Decker: > > acpi-support depends on it, so removal is not possible. And even if it was, > > it > > would probably be too late for that. > > > > Tagging this bug buster-ignore accordingly. > > Ok, I missed that. While this is unfortunate, I would still like to keep > this bug report as RC, so users of pm-utils are properly notified that > it is better to not use this package in buster. But, as I repeatedly asked and you did not answer: WHY would it be better to not use this package in buster? Could you please name a case where it's harmful? Or even name a replacement that fits its use case and actually works? > Hopefully we can sort this out properly in buster+1. If you demand that obsolete quirks are deleted, that can be done. But that's in no way a bug of RC severity -- "wishlist" is appropriate unless you can demonstrate a quirk that actually can cause serious damage. And about the last part... after going out of my way to try to debug a certain broken piece of software that's not my itch to scratch, I was rewarded by my new expensive machine failing to power on, with main remaining suspiction being invalid pokes specifically to power management. Fortunately, after a few hours of random panicked actions such as reseating all motherboard-mounted pieces of hardware and so on, it did finally start up. Thus no -- there's no way I'm going to try that again. If you wish for a clean-up... at this moment I can't spare any real tuits, but we're in deep freeze anyway. _Then_ I, or someone else, can consider looking at this _wishlist_ thing. I obviously care mostly about my personal use cases -- none of machines I own match any of the quirks -- thus, if per your advice as the former maintainer, the quirks should go, then I have no means to test them anyway. Not can I test support for Apple PMU (I don't know how many people have/care about powerpc Macs). But... as the quirks affect only old machines, which were already there by the time you maintained the package, what's exactly the problem with them? Especially one that would warrant urgent action. I can drop that if you wish, but the package itself is needed to suspend _my_ hardware. I'm concerned with breaking other people's toys, though... Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Packager's rule #1: upstream _always_ screws something up. This ⢿⡄⠘⠷⠚⠋⠀ is true especially if you're packaging your own project. ⠈⠳⣄
Bug#930869: feedback from an user
Just received this feedback from an user: 06:34 thanks for #930869, also heavy pm-utils users 06:37 */59 21-6 * * 1-5 root/usr/sbin/pm-suspend 06:37 */59 * * * 6-7 root/usr/sbin/pm-suspend 06:37 with hooks when it's ok to save or not 06:38 /etc/pm/sleep.d/99-$SOMEORG see for our implementation 06:39 pretty cool, to have automatic power saving on multiuser/multimachine managed machines (when people have cronjobs, day/week long running jobs and in-between-nfs mountes between the managed machines) So it's not like pm-utils is not used or used little. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Latin: meow 4 characters, 4 columns, 4 bytes ⣾⠁⢠⠒⠀⣿⡁ Greek: μεου 4 characters, 4 columns, 8 bytes ⢿⡄⠘⠷⠚⠋ Runes: ᛗᛖᛟᚹ 4 characters, 4 columns, 12 bytes ⠈⠳⣄ Chinese: 喵 1 character, 2 columns, 3 bytes <-- best!
Bug#930869: Asked to try and mediate this bug.
Control: severity -1 wishlist
Control: tags -1 +moreinfo
On Sun, Jun 30, 2019 at 11:26:01AM -0400, Sam Hartman wrote:
> Unfortunately, to do that, I'm going to need to ask at least one
> question that Adam is already asked.
[...]
Michael: if you have trouble naming either any particular problem, or a
viable replacement for this package, I assume there are none. If that's
incorrect, please provide more info before bumping the severity again.
The only remaining actionable part of this bug are the hacks ("quirks")
for buggy machines. Having researched the package a bit more, I see that
they talk to real-mode display BIOS -- such machines generally stopped
being manufactured roughly at the time pm-utils became unmaintained
upstream, thus I wonder whether that particular part of the code can be
said to "do more more harm then good". I'd wary before pulling the quirks
from under potentially working hardware.
But, I have no way to check that: none of 5 laptops I have even _has_ a
real-mode BIOS (three because of being non-x86, two because of level 3
UEFI without CSM). And for my non-laptops, which range from a 2004 box to
this year's stuff, pm-utils work perfectly without quirks.
So there are two questions:
* are pm-utils useful on non-quirk hardware?
• my answer is a strong "yes"
* should code for legacy hardware be kept if it can't be tested?
• this part I can't answer
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ According to recent spams, "all my email accounts are owned
⢿⡄⠘⠷⠚⠋ by a hacker". So what's the problem?
⠈⠳⣄
Bug#932865: python-qrtools: not installable: depends on python2 version of zbar
Package: python-qrtools Version: 1.4~bzr32-1 Severity: grave Justification: renders package unusable Hi! This package depends on python-zbar, which has already been removed as part of the python2-rm transition. This obviously makes it non-installable. Meow! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.1-00036-gf2c1d208af28 (SMP w/64 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages python-qrtools depends on: ii python 2.7.16-1 pn python-pil pn python-zbar pn qrencode python-qrtools recommends no packages. python-qrtools suggests no packages.
Bug#978950: rox-filer: black-on-black text with a dark GTK theme
Package: rox-filer Version: 1:2.11-2 Severity: normal Hi! The rox-filer is unusable with a dark theme, as it displays text in black even if the background is black as well. It must either obey both foreground and background color from the theme, or neither. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.0-rc1-umbar-00014-g59361a5e5d24 (SMP w/6 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages rox-filer depends on: ii libc62.31-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk2.0-0 2.24.33-1 ii libice6 2:1.0.10-1 ii libpango-1.0-0 1.46.2-3 ii libsm6 2:1.2.3-1 ii libx11-6 2:1.6.12-1 ii libxml2 2.9.10+dfsg-6.3+b1 ii shared-mime-info 2.0-1 Versions of packages rox-filer recommends: pn zeroinstall-injector Versions of packages rox-filer suggests: ii file 1:5.39-3 pn menu -- no debconf information
Bug#988642: open-invaders: destroys multi-monitor configuration
Package: open-invaders Version: 0.3-6 Severity: important I'm afraid that running the game permanently destroys configuration of a multi-monitor setup -- forcing you to either search how to restore RandR configuration from backup, or to manually re-configure every monitor (resolution, rotation, position, panel stuff, etc). Meow! -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-rc2-00014-ge7e192278148 (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages open-invaders depends on: ii libaldmb1 1:0.9.3-6+b3 ii liballegro4.4 2:4.4.3.1-2 ii libc6 2.31-12 ii libdumb11:0.9.3-6+b3 ii libgcc-s1 11-20210404-1 ii libstdc++6 11-20210404-1 ii open-invaders-data 0.3-6 open-invaders recommends no packages. open-invaders suggests no packages. -- no debconf information
Bug#484205: doesn't seem to be worth inclusion to me
Meow! It looks like hovercar does nothing but add "lol" at ends of sentences. That's... not very lulzworthy. I'd vote against including it in 'filters'. -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141109201156.ga16...@angband.pl
Bug#634685: let's axe fanboy
Meow! What "fanboy" does is removing everything except a handful words (and format them, preserving > markers). The joke is lost on anyone who doesn't read the source, and even then it's, well, not matching my sense of humor. Even on a long text relevant to Unix development like "man bash", the whole output is: pushed pushed branch I'd say, let's put "fanboy" to the pasture... -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141109201759.gb16...@angband.pl
Bug#508003: most filters break UTF-8
Meow! Actually, most filters break UTF-8. As I say any software that can't handle Unicode should have no place in Debian, this is not tolerable especially in a package as vital as "filters". Francois, as you snatched "filters" first[1], can you fix them yourself, or should I help with patches? [1]. I'm not a DD so it's easier for you to upload stuff anyway. -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141109202647.gc16...@angband.pl
Bug#439742: Processed: your mail
Meh, English language sucks here. In Polish, we got "Indians" and "Hindus", no confusion possible. On the other hand, the quality of .pl lletters is a bad joke and would be better removed. Half of words come from random other languages, some letters not in Polish alphabet (q, v, x) exist while lots of Polish letters (ą, ć, ę, ł, ń, ó, ś, ź, ż) are missing. -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141115151645.ga6...@angband.pl
Bug#777386: vbetool: please enable building on x32
Package: vbetool
Version: 1.1-3
Severity: wishlist
Tags: patch
Hi!
Please add x32 to the list of architectures vbetool is built on.
It's an x86 architecture, just like i386, amd64 or lpia.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental')
Architecture: x32 (x86_64)
Kernel: Linux 3.18.5-x32 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
diff -Nru vbetool-1.1/debian/changelog vbetool-1.1/debian/changelog
--- vbetool-1.1/debian/changelog 2012-12-15 22:29:39.0 +0100
+++ vbetool-1.1/debian/changelog 2015-02-07 22:42:28.0 +0100
@@ -1,3 +1,9 @@
+vbetool (1.1-3+x32) jessie-x32; urgency=medium
+
+ * Build on x32.
+
+ -- Adam Borowski Sat, 07 Feb 2015 22:41:48 +0100
+
vbetool (1.1-3) unstable; urgency=low
* QA upload.
diff -Nru vbetool-1.1/debian/control vbetool-1.1/debian/control
--- vbetool-1.1/debian/control 2012-12-15 18:25:13.0 +0100
+++ vbetool-1.1/debian/control 2015-02-07 22:32:59.0 +0100
@@ -9,7 +9,7 @@
Vcs-Browser: http://git.brad-smith.co.uk/?p=debian-old/pkg-vbetool.git
Package: vbetool
-Architecture: i386 amd64 lpia kfreebsd-i386 kfreebsd-amd64
+Architecture: i386 amd64 lpia kfreebsd-i386 kfreebsd-amd64 x32
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: run real-mode video BIOS code to alter hardware state
vbetool uses lrmi in order to run code from the video BIOS. Currently, it
Bug#809882: fix is in git, not uploaded
Hi! I've prepared a fix, however, I've been unable to test it as there's a massive chain of dependencies that need updating; some can be simply recompiled but some FTBFS on their own. It's pushed to the collab-maint git. -- A tit a day keeps the vet away.
Bug#809896: analog: builds for me
Control: tag -1 +unreproducible moreinfo Hi! I can't seem to reproduce the build failure from #809896. In the log you provided, it builds successfully too, just for some reason hangs after a successful build. -- A tit a day keeps the vet away.
Bug#793314: let's remove then
There's no separate QA team, everyone of us is a "member". You, as the former maintainer, are the person best informed about this package. And if you say it should be removed instead of trying to fix -- let's do so. -- A tit a day keeps the vet away.
Bug#809882: patch filed upstream, uploading
> Yepp, it builds fine now. Cool, uploading then! I filed the patch upstream at http://bugzilla.abisource.com/show_bug.cgi?id=13753 -- A tit a day keeps the vet away.
Bug#809882: new FTBFS
Hrm, not so fast :( It just gained a new unrelated FTBFS on current unstable: tls_tunnel.cpp:404:67: error: 'gnutls_cipher_set_priority' was not declared in this scope return_val_if_neg(gnutls_cipher_set_priority(*session_ptr,CIPHERS), session_ptr_t()); -- A tit a day keeps the vet away.
Bug#907767: time to go, then
Control: clone -1 -2 Control: retitle -2 RM: mozplugger -- RoQA; useless; dead upstream Control: reassign -2 ftp.debian.org In Sep 2018, Adrian Bunk wrote: > As far as I can see, not a single one of the 15 (sic) browser packages > in the dependencies does both still exist in unstable and still work > with mozplugger. So what's the reason to keep it? I happen to know a group of guys (11 humans, 1 cat/god) who are good at dealing with "package X exists when it shouldn't". Have at it! drill -t any mozplugger.mozdev.org → NXDOMAIN Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄ A master species delegates.
Bug#967990: FTBFS for real now
Control: tags -1 +ftbfs Control: severity -1 serious Bookworm has glibc 2.32, thus this fail happens in unstable and testing. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ How to exploit the Bible for weight loss: ⢿⡄⠘⠷⠚⠋⠀ Pr28:25: he that putteth his trust in the ʟᴏʀᴅ shall be made fat. ⠈⠳⣄
Bug#1011643: jetring: pointless R³:yes
Source: jetring Version: 0.30 Severity: minor Hi! The package currently declares Rules-Requires-Root: binary-targets but doesn't actually require that. Please change that to "no". Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-00017-g251fbd8b0fa2 (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
