Bug#831335: jessie-pu: package publicsuffix/20160703-1
On Mon, 2016-08-08 at 18:51 -0400, Daniel Kahn Gillmor wrote: > On Sat 2016-08-06 17:15:25 -0400, Adam D. Barratt wrote: > > Thanks; please feel free to upload that, with a small tweak: > > > > +publicsuffix (20160703-0+deb8u1) stable; urgency=medium > > + > > + * prepare for stable-proposed-updates. > > > > "jessie" is generally preferred as the changelog distribution and maybe > > "Upload to stable" or something similar? [...] > > Every couple of months is when we aim (not always successfully) to do a > > stable point release, so that hopefully works out well all around. > > I've never maintained this class of package before. do i just do > regular uploads to "jessie" as new versions of the package become > available, or do i need to do a jessie-pu bug report for each one? The latter, please. Regards, Adam
Bug#831335: jessie-pu: package publicsuffix/20160703-1
On Sat 2016-08-06 17:15:25 -0400, Adam D. Barratt wrote: > Thanks; please feel free to upload that, with a small tweak: > > +publicsuffix (20160703-0+deb8u1) stable; urgency=medium > + > + * prepare for stable-proposed-updates. > > "jessie" is generally preferred as the changelog distribution and maybe > "Upload to stable" or something similar? changed and uploaded (as a source-only upload; please let me know if that causes trouble; i always prefer to do source-only uploads where the build infrastructure supports it) >> The git tree's jessie branch which i'm proposing is at commit ID >> 6520ee81d3e2d73192e67685652ef6bccdb2e637, fwiw, so you don't have to >> worry about it changing. > > Thanks for that, but we'd still prefer p-u bug reports to be > free-standing. no problem, just providing multiple ways to access the data. > Every couple of months is when we aim (not always successfully) to do a > stable point release, so that hopefully works out well all around. I've never maintained this class of package before. do i just do regular uploads to "jessie" as new versions of the package become available, or do i need to do a jessie-pu bug report for each one? --dkg signature.asc Description: PGP signature
Bug#831335: jessie-pu: package publicsuffix/20160703-1
On Mon 2016-08-08 18:51:32 -0400, Daniel Kahn Gillmor wrote: > On Sat 2016-08-06 17:15:25 -0400, Adam D. Barratt wrote: >> Thanks; please feel free to upload that, with a small tweak: >> >> +publicsuffix (20160703-0+deb8u1) stable; urgency=medium >> + >> + * prepare for stable-proposed-updates. >> >> "jessie" is generally preferred as the changelog distribution and maybe >> "Upload to stable" or something similar? > > changed and uploaded (as a source-only upload; please let me know if > that causes trouble; i always prefer to do source-only uploads where the > build infrastructure supports it) hm, it looks like jessie can't handle source-only uploads that generate arch-indep packages, according to the rejection notice i just got. That's a shame. I guess i'll try again and include the arch-indep binary in my upload. Is there any chance that the jessie builders can learn to handle such a thing or is that just for unstable? --dkg signature.asc Description: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > # somehow these got removed after > # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833377;msg=29 > # ... > block 833377 by 833753 811674 833770 833756 831207 833776 831096 831074 > 833778 831149 831129 833773 831121 833780 833775 Bug #833377 [release.debian.org] transition: boost1.61 833377 was blocked by: 833794 833797 833377 was not blocking any bugs. Added blocking bug(s) of 833377: 833776, 831121, 833773, 833770, 833778, 831074, 833753, 831207, 833756, 811674, 833780, 833775, 831096, 831129, and 831149 > -- Stopping processing here. Please contact me if you need assistance. -- 833377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cegui-mk2: FTBFS with Boost 1.61
Processing commands for cont...@bugs.debian.org: > block 833377 by 833797 Bug #833377 [release.debian.org] transition: boost1.61 833377 was blocked by: 833794 833377 was not blocking any bugs. Added blocking bug(s) of 833377: 833797 > thanks Stopping processing here. Please contact me if you need assistance. -- 833377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: freeorion: FTBFS with boost1.61
Processing commands for cont...@bugs.debian.org: > clone 833773 -1 Bug #833773 [src:freeorion] freeorion: FTBFS with boost1.61 Bug 833773 cloned as bug 833794 833377 was blocked by: 833773 833770 833756 833775 833776 831074 831149 833780 833778 811674 831207 831129 833753 831121 831096 833377 was not blocking any bugs. Added blocking bug(s) of 833377: 833794; removed blocking bug(s) of 833377: 833753, 811674, 833770, 833756, 831207, 833776, 831096, 831074, 833778, 831149, 831129, 833773, 831121, 833780, and 833775 > reassign -1 src:boost1.61 Bug #833794 [src:freeorion] freeorion: FTBFS with boost1.61 Bug reassigned from package 'src:freeorion' to 'src:boost1.61'. No longer marked as found in versions freeorion/0.4.5+git20160707-1. Ignoring request to alter fixed versions of bug #833794 to the same values previously set > retitle -1 error: no type named 'types' in 'boost Bug #833794 [src:boost1.61] freeorion: FTBFS with boost1.61 Changed Bug title to 'error: no type named 'types' in 'boost' from 'freeorion: FTBFS with boost1.61'. > found -1 1.61.0+dfsg-2.1 Bug #833794 [src:boost1.61] error: no type named 'types' in 'boost Marked as found in versions boost1.61/1.61.0+dfsg-2.1. > forwarded -1 https://svn.boost.org/trac/boost/ticket/12349 Bug #833794 [src:boost1.61] error: no type named 'types' in 'boost Changed Bug forwarded-to-address to 'https://svn.boost.org/trac/boost/ticket/12349' from 'https://github.com/freeorion/freeorion/issues/777'. > affects -1 freeorion Bug #833794 [src:boost1.61] error: no type named 'types' in 'boost Added indication that 833794 affects freeorion > thanks Stopping processing here. Please contact me if you need assistance. -- 833377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833377 833773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833773 833794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Blocking bugs
Processing commands for cont...@bugs.debian.org: > block 833377 by 831129 833773 833775 831074 831096 833776 831149 831207 > 831121 833778 833780 Bug #833377 [release.debian.org] transition: boost1.61 833377 was blocked by: 833756 811674 833753 833773 833770 833377 was not blocking any bugs. Added blocking bug(s) of 833377: 831207, 833780, 831149, 833778, 831096, 831121, 831129, 833775, 831074, and 833776 > -- Stopping processing here. Please contact me if you need assistance. -- 833377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: blocking bugs
Processing commands for cont...@bugs.debian.org: > block 833377 by 811674 833770 833773 Bug #833377 [release.debian.org] transition: boost1.61 833377 was blocked by: 833753 833756 833377 was not blocking any bugs. Added blocking bug(s) of 833377: 811674, 833770, and 833773 > -- Stopping processing here. Please contact me if you need assistance. -- 833377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: blocking bugs
Processing commands for cont...@bugs.debian.org: > # boost1.61 > block 833377 by 833753 833756 Bug #833377 [release.debian.org] transition: boost1.61 833377 was not blocked by any bugs. 833377 was not blocking any bugs. Added blocking bug(s) of 833377: 833753 and 833756 > # icu57 > block 819530 by 833753 833754 833755 833756 Bug #819530 [release.debian.org] transition: icu 819530 was not blocked by any bugs. 819530 was not blocking any bugs. Added blocking bug(s) of 819530: 833754, 833756, 833755, and 833753 > # boost1.60 RM > block 833757 by 833758 833759 833760 Bug #833757 [ftp.debian.org] RM: boost1.60 -- RoQA; superseded by boost1.61 833757 was not blocked by any bugs. 833757 was not blocking any bugs. Added blocking bug(s) of 833757: 833758, 833759, and 833760 > -- Stopping processing here. Please contact me if you need assistance. -- 819530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819530 833377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833377 833757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 819530 https://release.debian.org/transitions/html/auto-icu.html Bug #819530 [release.debian.org] transition: icu Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-icu.html'. > -- Stopping processing here. Please contact me if you need assistance. -- 819530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#833747: nmu: binutils (<< 2.27) dependencies
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu please binNMU binutils (<< 2.27) dependencies: eztrace lush tulip, building with binutils (>= 2.27).
Bug#833720: transition: libzhuyin
Control: tags -1 confirmed On 08/08/16 11:29, ChangZhuo Chen (陳昌倬) wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > Due to ibus-libzhuyin, libzhuyin transition and opencc transition > (#833589) need to be done together. Since opencc transition starts, we > need to start this transition as well. > > Please tell me when I can do uploads to unstable, thanks. That's fine. Go ahead. Emilio
Processed: Re: Bug#833720: transition: libzhuyin
Processing control commands: > tags -1 confirmed Bug #833720 [release.debian.org] transition: libzhuyin Added tag(s) confirmed. -- 833720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#833720: transition: libzhuyin
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, Due to ibus-libzhuyin, libzhuyin transition and opencc transition (#833589) need to be done together. Since opencc transition starts, we need to start this transition as well. Please tell me when I can do uploads to unstable, thanks. Ben file: title = "libzhuyin"; is_affected = .depends ~ "libzhuyin6" | .depends ~ "libzhuyin7"; is_good = .depends ~ "libzhuyin7"; is_bad = .depends ~ "libzhuyin6"; Dependency: - ibus-libzhuyin: experimental version works -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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: systemd (via /run/systemd/system) -- ChangZhuo Chen (陳昌倬)Debian Developer (https://nm.debian.org/public/person/czchen) Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B signature.asc Description: PGP signature
Bug#833589: transition: opencc
On Sun, Aug 7, 2016 at 7:13 PM, ChangZhuo Chen (陳昌倬)wrote: > On Sun, Aug 07, 2016 at 12:33:45PM +0200, Emilio Pozuelo Monfort wrote: >> On 06/08/16 17:21, Aron Xu wrote: >> > - ibus-libzhuyin: experimental version works > > I will handle this package, thanks for the transition. > opencc is uploaded, please go ahead. Regards, Aron