Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #171653 > unrolled thread
| Started by | "D. R. Evans" <doc.evans@gmail.com> |
|---|---|
| First post | 2016-08-31 22:50 +0200 |
| Last post | 2016-09-03 06:20 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.user
[jessie] how to file bug report against update that broke other packages? "D. R. Evans" <doc.evans@gmail.com> - 2016-08-31 22:50 +0200
Re: [jessie] how to file bug report against update that broke other packages? Jonathan Dowland <jmtd@debian.org> - 2016-09-01 11:10 +0200
Re: [jessie] how to file bug report against update that broke other packages? "D. R. Evans" <doc.evans@gmail.com> - 2016-09-01 15:30 +0200
Re: [jessie] how to file bug report against update that broke other packages? kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2016-09-03 06:20 +0200
| From | "D. R. Evans" <doc.evans@gmail.com> |
|---|---|
| Date | 2016-08-31 22:50 +0200 |
| Subject | [jessie] how to file bug report against update that broke other packages? |
| Message-ID | <sckCm-7aI-9@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
As of a few days ago the gscan2pdf program is no longer functioning properly in up-to-date jessie. The culprit seems to be one of the packages updated as part of the recent imagemagick security update. But I don't which of the updated files, or even which package, causes the problem (indeed, I am not 100% certain that it is the imagemagick update that is the source of the problem, but it sure looks very, very likely). So I am unsure how to proceed and let the developers know that the breakage needs to be fixed (ASAP, I hope), since the breakage appears in a package that was not updated, and I don't know precisely which package is responsible. Any advice as to how to notify the debian team of the problem in a way that will be useful to them would be gratefully received. Doc -- Web: http://www.sff.net/people/N7DR
[toc] | [next] | [standalone]
| From | Jonathan Dowland <jmtd@debian.org> |
|---|---|
| Date | 2016-09-01 11:10 +0200 |
| Message-ID | <scwat-7KC-1@gated-at.bofh.it> |
| In reply to | #171653 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Aug 31, 2016 at 02:44:13PM -0600, D. R. Evans wrote: > As of a few days ago the gscan2pdf program is no longer functioning properly > in up-to-date jessie. I'd report it against gscan2pdf in the first instance. The maintainers of the package which has broken will be best equipped to figure out whether or not the problem needs changes in the gscan2pdf package or elsewhere; the bug can always be reassigned later if needs be. -- Jonathan Dowland Please do not CC me, I am subscribed to the list.
[toc] | [prev] | [next] | [standalone]
| From | "D. R. Evans" <doc.evans@gmail.com> |
|---|---|
| Date | 2016-09-01 15:30 +0200 |
| Message-ID | <scAe6-2pX-9@gated-at.bofh.it> |
| In reply to | #171657 |
[Multipart message — attachments visible in raw view] — view raw
Jonathan Dowland wrote on 09/01/2016 03:07 AM: > > I'd report it against gscan2pdf in the first instance. The maintainers of the > package which has broken will be best equipped to figure out whether or not the > problem needs changes in the gscan2pdf package or elsewhere; the bug can always > be reassigned later if needs be. Thank you. After some thought, I had come to the same conclusion; so I'll do that when I get a chance later today. Doc -- Web: http://www.sff.net/people/N7DR
[toc] | [prev] | [next] | [standalone]
| From | kamaraju kusumanchi <raju.mailinglists@gmail.com> |
|---|---|
| Date | 2016-09-03 06:20 +0200 |
| Subject | Re: [jessie] how to file bug report against update that broke other packages? |
| Message-ID | <sdaAV-oe-7@gated-at.bofh.it> |
| In reply to | #171653 |
On Wed, Aug 31, 2016 at 4:44 PM, D. R. Evans <doc.evans@gmail.com> wrote: > As of a few days ago the gscan2pdf program is no longer functioning properly > in up-to-date jessie. I think you need to debug the problem a bit more before reporting it on any package. What do you mean by "no longer functioning properly"? What is the expected behavior and what is the current behavior? Is the problem reproducible? > The culprit seems to be one of the packages updated as part of the recent > imagemagick security update. But I don't which of the updated files, or even > which package, causes the problem (indeed, I am not 100% certain that it is > the imagemagick update that is the source of the problem, but it sure looks > very, very likely). > > So I am unsure how to proceed For issues like this, you should keep track of the list of installed packages before and after the upgrades. That makes it easier to debug if something goes wrong. For example, you can use this shell script https://gitlab.com/d3k2mk7/rutils/blob/master/bin/installed_packages.sh which will store the list of packages in ~/logs directory with a timestamp appended to the file name. Sample run % installed_packages.sh stored the list of installed packages in /home/rajulocal/logs/installed_packages_list_20160903_000640.txt hope that helps raju -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web