Bug#1029748: All bugs with submitter=... package=all, latest first, limit 30
Package: qa.debian.org Severity: wishlist User: qa.debian@packages.debian.org Usertags: udd I wish there was a way to use the https://wiki.debian.org/UltimateDebianDatabase/ to find all the bugs I have submitted, for all packages in Debian, latest first, limit=30. https://bugs.debian.org/cgi-bin/pkgreport.cgi?&submitter=jida...@jidanni.org finds too many, and no way to make latest first.
user thwarted in reporting imagemagick bug
user used reportbug to file imagemagick bug maintainer responded that in the readme.debian files it says to report bugs yourself. user then tries the addresses in the readme files which fail. Therefore /usr/share/doc/imagemagick/ needs to have warnings about invalid addresses there, and a warning that the final answer is if you want to report an imagemagick bug, you must be a member of the imagemagick mailing list, else forget about reporting your bug. To: [EMAIL PROTECTED] From: Ryuichi Arafune <[EMAIL PROTECTED]> Subject: Re: Bug#161349: imagemagick: i clicked on 'rotate right' and 'display' crashed on my .tif file Please let see the webpage: http://www.imagemagick.org You can see the way haw to submit a bug report to the upstraem author. From: Dan Jacobson <[EMAIL PROTECTED]> Subject: Re: Bug#161349: imagemagick: i clicked on 'rotate right' and 'display' crashed on my .tif file Date: 30 Sep 2002 06:35:37 +0800 Message-ID: <[EMAIL PROTECTED]> jidanni> >>>>> "Ryuichi" == Ryuichi Arafune <[EMAIL PROTECTED]> writes: jidanni> jidanni> Ryuichi> Please submit the upstream BTS. I won't fix the upstream bug. (and jidanni> Ryuichi> See the README.Debian.) jidanni> jidanni> http://www.simplesystems.org/ImageMagick/bugs.html jidanni> does not exist, like it says in /usr/doc/imagemagick/README.txt.gz = From: Dan Jacobson <[EMAIL PROTECTED]> Subject: imagemagick: Forget about reporting imagemagic bugs To: Debian Bug Tracking System <[EMAIL PROTECTED]> X-Sent: 15 hours, 54 minutes, 57 seconds ago Package: imagemagick Version: 4:5.4.4.5-1 Severity: important The debian provider says report bugs to the upstream provider. /usr/doc/imagemagick/README.txt.gz says to use http://www.simplesystems.org/ImageMagick/bugs.html which doesn't exist. It also says "The author is [EMAIL PROTECTED]" which bounces. When one finally gets to www.imagemagick.org it says How You Can Help Describes how you can contribute to the ImageMagick project. Reporting Bugs Bugs should be reported by posting to the Magick-bugs mailing list. But first you must subscribe to the list! Forget it. I give up. With my modem I can't subscribe to a list just to report a bug. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux debian 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686 Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 Versions of packages imagemagick depends on: ii libmagick5 4:5.4.4.5-1 Image manipulation library (free v -- http://jidanni.org/ Taiwan(04)25854780
is libdb3-util documentation deficient?
Am I correct that the libdb3-util package is not up to par, as it has no man pages, seemly no --help, no doc/README... Indeed the most I can learn about it is its 2 lines of description in aptitude. Anyway, you qa guys take it from here. -- http://jidanni.org/ Taiwan(04)25854780
Re: user thwarted in reporting imagemagick bug
Thanks for making reporting bugs easier for use mere "one night stand" users. Just like the police: if you make reporting convenient, you get more crime tips. -- http://jidanni.org/ Taiwan(04)25854780
debian packages too active after mere installation
By the way, another thing I hate about debian is: I want to install a program, slowly read its documents and man pages, then activate the features I want. But no, e.g. ledcontrol and indeed other led programs start playing with your leds right after you install them. So, I suppose the safe way to learn about a debian package is to poke around in the .deb on the CD, yuck. -- http://jidanni.org/ Taiwan(04)25854780
ledcontrol: PID muncher
I don't know if this bad or just a matter of taste. I sent it 6 weeks ago: Bug#159386: (ledcontrol: a new sleep executed every 5 sec, you are the process number user champion) Package: ledcontrol Version: 0.5.2-4 Severity: minor Not that this is good or bad, but I noticed your program, doing a new "sleep 5' etc. repeatedly, is the champion process number user on my system. I've only rebooted an hour ago, and already "ps aux" shows PID in the 4000 range. -- http://jidanni.org/ Taiwan(04)25854780
Bug#173231: qa.debian.org: some messages flitting past on rebooting are not also seen in /var/log
Package: qa.debian.org Version: unavailable; reported 2002-12-16 Severity: wishlist Gentlemen, when we (re)boot, like I do every day [I power off when not in use] we start to notice that there's some console messages that flit by fast, and aren't found by e.g. # uptime 06:08:57 up 32 min, 3 users, load average: 0.02, 0.08, 0.19 # find /var/log -mmin -60 -type f|xargs grep -i checking which didn't find 'checking module dependencies' which I remember flitting by. Of course there was a more alarming 'cannot' that filtted by fast and cannot be found... Anyway. please be sure that all that stuff can be found somehow. dmesg(1) of course is not enough. Anything before say [one's] x windows starts I suppose should be a candidate, as doing a alt-crt-f1 just shows the last bits... -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux debian 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686 Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5
Bug#173275: qa.debian.org: still lots of commands without man pages
Package: qa.debian.org Version: unavailable; reported 2002-12-16 Severity: wishlist if a command doesn't have a man page, the best one can do is do a risky $command --help to guess what it does. E.g. with lspgpot ... -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux debian 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686 Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5
Bug#178394: qa.debian.org: find out problems before cron.monthly does
Package: qa.debian.org Version: unavailable; reported 2003-01-26 Severity: minor sorry but here's some examples of somethings maybe packages should check: things that won't be discovered until cron.monthly does. e.g. the HylaFAX folks never thought i wouldn't even have faxed once this month. the Nautilus people had some other problem... i don't really know what Nautilus is all about but i seem to have it installed :-) both i have probably reported and perhaps are fixed already... next time i do apt-zip i will know... anyways the point is: maybe in the lintian or policy areas, such problems could be caught before cron.monthly catches them and sends worrisome messages to the user. From: [EMAIL PROTECTED] (Anacron) To: [EMAIL PROTECTED] Subject: Anacron job 'cron.monthly' /etc/cron.monthly/hylafax: awk: /tmp/fileah3jWf:267: fatal: cannot open file `/var/spool/hylafax/log/xferfaxlog' for reading (No such file or directory) Null message body; hope that's ok awk: /tmp/fileMjGeyC:300: fatal: cannot open file `/var/spool/hylafax/log/xferfaxlog' for reading (No such file or directory) Null message body; hope that's ok /etc/cron.monthly/scrollkeeper: /usr/share/omf/nautilus/nautilus-quick-reference-es.omf:5: error: Input is not proper UTF-8, indicate encoding ! Referencia R嫚ida de Nautilus ^ /usr/share/omf/nautilus/nautilus-quick-reference-es.omf:5: error: Bytes: 0xE1 0x70 0x69 0x64 Referencia R嫚ida de Nautilus ^ /usr/share/omf/nautilus/nautilus-quick-reference-ko.omf:5: error: Input is not proper UTF-8, indicate encoding ! 喻⼂楝蝶 緒艇 紫遺蜓 ^ /usr/share/omf/nautilus/nautilus-quick-reference-ko.omf:5: error: Bytes: 0xB3 0xEB 0xC6 0xBF 喻⼂楝蝶 緒艇 紫遺蜓 ^ /usr/share/omf/nautilus/nautilus-user-manual-es.omf:8: error: Input is not proper UTF-8, indicate encoding ! GNOME|N�cleo del Escritorio ^ /usr/share/omf/nautilus/nautilus-user-manual-es.omf:8: error: Bytes: 0xFA 0x63 0x6C 0x65 GNOME|N�cleo del Escritorio ^ /usr/share/omf/nautilus/nautilus-user-manual-ko.omf:5: error: Input is not proper UTF-8, indicate encoding ! 喻⼂楝蝶 餌辨濠 撲貲憮 ^ /usr/share/omf/nautilus/nautilus-user-manual-ko.omf:5: error: Bytes: 0xB3 0xEB 0xC6 0xBF 喻⼂楝蝶 餌辨濠 撲貲憮 ^ = btw, those lines look Chinese to me of course here in gnus with my locale. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux debian 2.4.19-k7 #1 Sun Oct 6 20:29:56 EST 2002 i686 Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5
Re: Bug#178656: netselect: many trailing whitespaces
Dear QA group, was I wrong in encouraging efficiency? >>>>> "Avery" == Avery Pennarun <[EMAIL PROTECTED]> writes: Avery> On Tue, Jan 28, 2003 at 02:51:03AM +0800, Dan Jacobson wrote: >> Package: netselect >> Version: 0.3-4 >> Severity: minor >> File: /usr/share/doc/netselect/README.gz >> Tags: upstream >> >> the above file has many trailing blanks, and even whole lines of >> blanks. >> >> grep ' $' >> can find them. Avery> Why on earth do we care? gzip is happy to "remove" them for us. Avery> Have fun, Avery> Avery -- http://jidanni.org/ Taiwan(04)25854780
Bug#192739: qa.debian.org: http://packages.qa.debian.org/*/* not clear
Package: qa.debian.org Version: unavailable; reported 2003-05-10 Severity: wishlist Lets say the user has just jumped to, oh, http://packages.qa.debian.org/w/wwwoffle.html Todo You should update the package to follow the last version of [26]Debian Policy (Standards-Version 3.5.9 instead of 3.5.1). The "you" isn't clear: the user? the developer?... Warning: the "Latest News" section is not yet automatically updated. I'm waiting that master.debian.org is upgraded to woody (stable) in The "I" isn't clear: the developer? the qa site maintainer?... order to be able to setup the required scripts. Those scripts will automatically update the "Latest News" and they'll let you add your own news items. Please be patient. The "you" isn't clear, but probably the developer.
Bug#192739: qa.debian.org: http://packages.qa.debian.org/*/* not clear
>>>>> "Lukas" == Lukas Geyer <[EMAIL PROTECTED]> writes: Lukas> Dan Jacobson <[EMAIL PROTECTED]> writes: >> Lets say the user has just jumped to, oh, >> http://packages.qa.debian.org/w/wwwoffle.html >> >> Todo >> >> You should update the package to follow the last version of >> [26]Debian Policy (Standards-Version 3.5.9 instead of 3.5.1). >> >> The "you" isn't clear: the user? the developer?... Lukas> Come on, the package tracking system is for developers, "pure" users Lukas> will not even know it exists. Well, I am a pure user and I somehow got to that page. >> Warning: the "Latest News" section is not yet automatically updated. >> I'm waiting that master.debian.org is upgraded to woody (stable) in >> >> The "I" isn't clear: the developer? the qa site maintainer?... Lukas> The script which produces this output... OK, make that clear on that page >> order to be able to setup the required scripts. Those scripts will >> automatically update the "Latest News" and they'll let you add your >> own news items. Please be patient. >> >> The "you" isn't clear, but probably the developer. Lukas> I suggest you find some more productive use of your time. There are Lukas> _real_ bugs out there, please do not clutter the BTS with pointless Lukas> nitpicking. I was giving you a rare glimpse about what your site looks like to outsiders, and some simple suggestions about what could be easily adjusted.
Grass is in a sorry state in Debian
Grass is in a sorry state in Debian. For instance, on the latest upgrade, 557 man pages became just empty files. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=220293
Re: Grass is in a sorry state in Debian
Matthew> Yes, that does look pretty unpleasant. I don't know what's going on with Matthew> Federico, there are other major bugs in there, too. Matthew> If he hasn't surfaced in the next few days, I'll whip up an NMU to fix up Matthew> the problems, probably upgrading to the latest upstream while I'm at it. Indeed, upgrading to the latest upstream would be super too! That simple step is what one could never get previous maintainers to do. I.e. you might as well become the new maintainer.
the Packages files should get to mirrors last
On the Debian mirrors, each day there is a period, perhaps a few hours, between the time the Packages files arrive, and the time packages themselves arrive. This is not a problem, because it happens early in the morning when all Debian users are of course asleep... except for me. It would seem to be a no-brainer to make sure the Packages files come last. M below stands for an average Debian mirror. # apt-get update Get:1 M sid/main Packages [3215kB] Get:2 M sid/main Release [82B]... # apt-get dist-upgrade 567 packages upgraded, 8 newly installed, 0 to remove and 0 not upgraded. Need to get 20.0MB/615MB of archives. After unpacking 52.8MB will be used. Get:1 M sid/main debconf-i18n 1.4.32 [77.4kB] Get:2 M sid/main debconf 1.4.32 [99.6kB] Err M sid/main libgcc1 1:3.4.1-7 404 Not Found Err M sid/main makedev 2.3.1-75 404 Not Found Err M sid/main procps 1:3.2.3-1 404 Not Found... Isn't this just plain nuts? Sure looks unprofessional. If Mirror Central Command has "no way to ensure the Packages files are updated last", then they should still please think up a way, just like find(1) has a -depth. Or they could break updates into two updates, the latter just for the Packages files. What if UNIX directories listed inodes before they existed or whatever? Of course the workaround for the end user is "just try again a couple hours later". Maybe if the Mirror Central Command people ran the list of what to update thru tac(1) the big P of Packages would end up at the bottom or something, and all would be well.
breaks Debian package system worldwide several hours a day
severity 217957 critical severity 6786 critical merge 6786 217957 # critical: breaks Debian package system worldwide several hours a day. # How to fix: Packages files should get to mirrors last.
Bug#906267: UDD: add bug search on submitter
Package: qa.debian.org Severity: wishlist I was at DebConf18 and told a developer I had recently submitted a bug regarding his stuff but forgot the exact package name. He was unable to find it in the UDD as there is no way to search on bug submitter, so he was forced to search the BTS. He should have been able to query on bugs submitted by jida...@jidanni.org, with output ordered by date, most recent first.
Bug#906267: UDD: add bug search on submitter
Anyway the BTS is more "ultimate" until a submitter search field is added to UDD.
