Bug#410771: Re: Bug#410771: emacs-snapshot: error "Lisp nesting exceeds `max-lisp-eval-depth'"

Control: tags -1 moreinfo Control: retitle -1 emacspeak loops infinite on specific directory Hi Tim, Sorry for taking so long to respond to this bug, but the package emacspeak was orphaned and just got a new maintainer. On 24-02-07 12:04, Romain Francoise wrote: > I believe that this is a bug in

Bug#719757: openmotif: please package the man-pages separately so that they can be installed along with Lesstif

Control: reassign -1 motif On 15-08-13 01:56, G.raud wrote: > Having the OpenMotif manual pages in a separate package libmotif-doc instead > of > inside libmotif-dev would allow this new package not to conflict with any > Lesstif > packages; thus it would be possible to have some Motif manual pa

Re: [cluster3] please rebuild and possibly move to main

On 10-09-13 19:21, Thorsten Alteholz wrote: > thanks alot for your info. Unfortunately the motif license is not the > only hurdle to put cluster3 into main. Clear. > Anyway, if I understand you right, I just have to reupload the package > to get everything straight with the motif update (so no ne

Bug#1072302: src:gnome-shell-mailnag: fails to migrate to testing for too long: versioned dependency not yet in unstable

Source: gnome-shell-mailnag Version: 40.0-5 Severity: serious Control: close -1 40.0-7 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 d

Bug#1072780: src:transaction: fails to migrate to testing for too long: uploader built arch:all binary

Source: transaction Version: 3.0.0-1 Severity: serious Control: close -1 4.0-1 X-Debugs-CC: alexandre.deti...@gmail.com Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between

Bug#1072780: src:transaction: fails to migrate to testing for too long: uploader built arch:all binary

Hi, On 15-06-2024 11:38 p.m., Colin Watson wrote: This was fixed by transaction 4.0-2, and it looks like either you cancelled your upload or it was automatically dropped from the DELAYED queue. I cancelled my upload once I spotted 4.0-2. Paul OpenPGP_signature.asc Description: OpenPGP digit

Bug#1016828: poc-streamer: flaky autopkgtest: regularly times out on i386

Source: poc-streamer Version: 0.4.2-5 Severity: serious User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up on our "slow" page [1]. I noticed that there were several runs that took 8:21

Bug#1018739: src:libowfat: fails to migrate to testing for too long: FTBFS

Source: libowfat Version: 0.30-4 Severity: serious Control: close -1 0.32-3 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1014120 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstabl

Bug#1023804: git-remote-hg: autopkgtest needs update for new version of git: transport 'file' not allowed

Source: git-remote-hg Version: 1.0.3.2~ds-2 Severity: serious X-Debbugs-CC: g...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:git Dear maintainer(s), With a recent upload of git the autopkgtest of git-remote-hg fails in t

Bug#1023805: guilt: autopkgtest needs update for new version of git: git log --decorate slightly different output

Source: guilt Version: 0.36-2 Severity: serious X-Debbugs-CC: g...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:git Dear maintainer(s), With a recent upload of git the autopkgtest of guilt fails in testing when that autop

Bug#1025021: python-bayespy: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

Source: python-bayespy Version: 0.5.22-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.

Bug#1025197: zope.exceptions: (autopkgtest) needs update for python3.11: 'DummyTB' object has no attribute 'tb_lasti'

Source: zope.exceptions Version: 4.5-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11

Bug#1025021: python-bayespy: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

Control: reassign -1 python3-nose Control: tags -1 ftbfs patch pending upstream Control: tags -1 - bookworm sid Control: merge 1024235 -1 Control: affects -1 src:python-bayespy Hi Håvard, On 01-12-2022 19:16, Håvard F. Aasen wrote: File "/usr/lib/python3/dist-packages/nose/util.py", line 45

Bug#1028625: src:x-loader: fails to migrate to testing for too long: FTBFS

Source: x-loader Version: 1.5.1+git20110715+fca7cd2-2 Severity: serious Control: close -1 1.5.1+git20110715+fca7cd2-3 X-Debbugs-CC: Marcos Talau Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1026364 Dear maintainer(s), The Release Tea

Bug#1032235: Bug#1014110: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs

Hi, [Release Team here] On Thu, 2 Mar 2023 18:42:56 +0100 Bastian Germann wrote: On Thu, 2 Mar 2023 05:10:41 +0100 Guilhem Moulin wrote: > Ah no my bad, the changelog entry is probably incorrect and the > cryptsetup-initramfs breakage is caused by the recent libargon2 upload > indeed, but AFA

Bug#1032235: Bug#1014110: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs

Hi all, On 15-03-2023 23:28, Guilhem Moulin wrote: On Wed, 15 Mar 2023 at 22:43:31 +0100, Bastian Germann wrote: Am 15.03.23 um 22:39 schrieb Paul Gevers: Do I understand correctly that: 1) argon2 in testing isn't affected 2) this bug isn't solved yet, despite the closure? 3) the

Bug#1032235: Bug#1014110: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs

Hi Guilhem, On 16-03-2023 14:31, Guilhem Moulin wrote: cryptsetup can only migrate when argon2 migrates, I see that in the excuse page now but don't understand the reason why, It took me a while and the help of colleagues, but it's libcryptsetup12-udeb that has: Depends: libargon2-1-udeb (

Bug#1032235: Bug#1014110: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs

Hi, [@aurel32, glibc question at the bottom] On 16-03-2023 11:57, Bastian Germann wrote: Am 16.03.23 um 09:13 schrieb Paul Gevers: I'm not 100% sure I parse that sentence as you intended, so let me ask explicitly: if we binNMU (now or in the future) src:argon2 version 0~20171227-0

Bug#1032235: Bug#1014110: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs

Control: tags -1 d-i Hi Bastian, Guilhem, On 16-03-2023 13:44, Paul Gevers wrote: cryptsetup will need to migrate to mitigate the time bomb. Ack. As I already mentioned on this or some related bug, I would find it nice for #1014110 to be fixed in bookworm (threaded argon2 executable) but

Bug#1033512: zc.buildout: autopkgtest fails: cannot open /usr/share/python3-zope.testing/test_helper

Source: zc.buildout Version: 2.13.2-4 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output

Bug#1033514: xchain: autopkgtest fails: xvfb-run: command not found

Source: xchain Version: 1.0.1-10 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at th

Bug#1036249: closure-compiler: #1036159

Hi Markus, On 25-05-2023 23:47, Markus Koschany wrote: Since I could not find a targeted fix I decided to remove the dependency on rhino 1.7.14 and embedded rhino 1.7.7.2 instead, the last version that worked well for closure-compiler. I have rebuilt all reverse-dependencies and this would re

Bug#1050066: adequate: autopkgtest fails on !amd64

Source: adequate Version: 0.15.7 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails on all architectures but amd64. Can you please investigate the situation and fix it? I copied some of the out

Bug#1051413: src:gpsim-doc: fails to migrate to testing for too long: FTBFS

Source: gpsim-doc Version: 0.22.0-2.2 Severity: serious Control: close -1 0.22.0-3 X-Debbugs-CC: b...@debian.org Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Bug#1058627: src:zope.proxy: fails to migrate to testing for too long: autopkgtest regression

Source: zope.proxy Version: 4.5.0-1 Severity: serious Control: close -1 5.1-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as ha

Bug#1061175: src:pyocd: fails to migrate to testing for too long: triggers autopkgtest issues in valinor

Source: pyocd Version: 0.13.1+dfsg-3 Severity: serious Control: close -1 0.36.0-1 X-Debbugs-CC: Alexandre Detiste Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#1061456: src:pmacct: fails to migrate to testing for too long: Build-Depends not available on s390x

Source: pmacct Version: 1.7.7-1 Severity: serious Control: close -1 1.7.8-1 X-Debbugs-CC: Boyuan Yang Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable fo

Bug#689896: lastfmsubmitd is maintained by Debian QA group

Hi Zigo, As lastfmsubmitd is maintained by the Debian QA group, I will just go ahead and upload a new version of lastfmsubmitd with your patch applied. I will request an unblock after the upload. Paul signature.asc Description: OpenPGP digital signature

Bug#652814: lastfmsubmitd: Should we change permissions of /var/log/lastfmsubmitd?

Package: lastfmsubmitd Version: 1.0.6-3 Followup-For: Bug #652814 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The last reporter added the "su" part to logrotate. I am not comfortable with that. I don't understand why /var/log/lastfmsubmitd should be writable by the whole "spool" group. I think

Bug#690765: lastfmsubmitd: please delete log files on purge

Package: lastfmsubmitd Version: 1.0.6-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Policy 10.8 says: Log files should be removed when the package is purged (but not when it is only removed). This should be done by the postrm script when it is called with the argument purge (se

Bug#687597: openslp-dfsg: touch bug CVE-2012-4428

Package: openslp-dfsg Followup-For: Bug #687597 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As far as I can tell, no solution known yet, on 17 October 2012, 15:28 +0200. While going through Debian QA group owned RC bugs, I touched on this bug. http://security-tracker.debian.org/tracker/CVE-20

Bug#692342: update information on several apt-move bugs

ption: The use of implicit split call has been removed from perl in version 5.12 as it had been deprecated for 15 years Author: Paul Gevers Bug-Debian: http://bugs.debian.org/692342 Forwarded: no --- a/move3 +++ b/move3 @@ -42,7 +42,7 @@ } while (<>) { - split; + @_=split; if ($_[0]

Bug#691393: work in progress

tag -1 +pending thanks Hi, We are working on it. See [1] and bug 695130 [2]. Paul [1] http://anonscm.debian.org/gitweb/?p=collab-maint/motif.git [2] http://bugs.debian.org/bug=695130 signature.asc Description: OpenPGP digital signature

pre-approval of rename openmotif -> motif for main archive

Hi ftp-master(s), Maybe you have seen on debian-devel [1] that (open)motif is now released under a DSFG-free license and that we are working on getting [2] it in shape for debian/main. Actually, my intention is that it fully replaces lesstif2 (which is starting to look slightly bit-rotten) in jess

Please review package description of (open)motif

xec, flex, libsm-dev, libx11-dev, libxaw7-dev, libxext-dev, libxft-dev, libxmu-dev, libxt-dev, xbitmaps Maintainer: Graham Inggs Uploaders: Paul Gevers Standards-Version: 3.

Re: Please review package description of (open)motif

Hi Justin and the rest, On 19-01-13 15:00, Justin B Rye wrote: > Paul Gevers wrote: >> [Please keep cc in the loop.] >> Package: motif-clients > > What does this package name mean, anyway? Is the idea that it's a set > of executables that have a client relatio

Re: First motif commits

On 21-01-13 20:54, Graham Inggs wrote: > If you want. Do you want to start a new thread there? Just continue. > I still have the source code for every Debian package that depends on > libmotif-dev and lesstif2-dev on my PC, so I ran 'grep -i > XmPrintPopupPDM -l -r *' for each of the six missing

Bug#698661: unblock: openmotif/2.3.3-7

Improve 0005-sprintf-error-message-hardening-format-security.patch to use +strcpy i.s.o. sprintf and properly format string. + + -- Paul Gevers Sat, 05 Jan 2013 21:36:38 +0100 + +openmotif (2.3.3-6) unstable; urgency=low + + * QA upload. +- Set maintainer to QA group + * Allow multia

Re: Bug#698661: unblock: openmotif/2.3.3-7

On 22-01-13 15:21, Niels Thykier wrote: >> Openmotif 2.3.3-7 is an update to 2.3.3-5 to allow two release goals: >> - code hardening > > This does not appear to close a bug and therefore, I presume, is there > for not on the "target list" for Wheezy? If it is not on this list, > then I would pref

Re: Bug#698661: unblock: openmotif/2.3.3-7

m (see bug #698661) to allow for transition to Wheezy. + + -- Paul Gevers Tue, 22 Jan 2013 20:52:01 +0100 + +openmotif (2.3.3-7) unstable; urgency=low + + * QA upload. + * Improve 0005-sprintf-error-message-hardening-format-security.patch to use +strcpy i.s.o. sprintf and properly format

Re: First motif commits

On 31-01-13 21:11, Graham Inggs wrote: > Actually, it looks like we should ditch libmotif4 and name the separate > packages libXm4, libUil4 and libMrm4. Agree. > On 31 January 2013 21:41, Graham Inggs > wrote: > > I've had a look at incorporating > d/patches/

Re: First motif commits

On 01-02-13 08:31, Paul Gevers wrote: > On 31-01-13 21:11, Graham Inggs wrote: >> Actually, it looks like we should ditch libmotif4 and name the separate >> packages libXm4, libUil4 and libMrm4. > > Agree. Not perfect yet, but I did some of the work on the split (bed time n

Re: First motif commits

On 04-02-13 22:41, Graham Inggs wrote: > On 3 February 2013 23:34, Paul Gevers <mailto:elb...@debian.org>> wrote: > > > Not perfect yet, but I did some of the work on the split (bed time now > though). Pushed to the repo. > > > Ah, I actually did this

Re: First motif commits

On 05-02-13 19:06, Graham Inggs wrote: > I thought I had made it clear I was going to work on splitting > libmotif4, but no harm done. Sorry, slight misunderstanding. I thought it was your proposal. As I had time and hadn't seen any progress, I decided to try some of that work. Maybe the symbols

Re: First motif commits

On 07-02-13 07:03, Graham Inggs wrote: > On 6 February 2013 22:07, Paul Gevers <mailto:elb...@debian.org>> wrote: > >> I think that if we have the split of -common, it is time to upload >> the package to experimental, to see if the ftp-masters can let the >> n

Re: First motif commits

On 16-02-13 17:19, Graham Inggs wrote: > Stefano agreed with you about multiple -dev packages being overkill. I > did go ahead though, with splitting uil into its own package and marking > it multiarch: foreign, it could be used for multiarch cross-compiling. Ok, fine. > I decided to rename your

Re: [SCM] Motif widgetset library branch, master, updated. 10e3e364ae46c34cbb88cba0aecab1e053bca5fa

Hi Graham, On 16-02-13 23:30, Graham Inggs wrote: > The following commit has been merged in the master branch: > commit 10e3e364ae46c34cbb88cba0aecab1e053bca5fa > Author: Graham Inggs > Date: Sun Feb 17 00:24:02 2013 +0200 > > Mark transitional package libmotif4 Architecture: any, Multi-Ar

Re: [SCM] Motif widgetset library branch, master, updated. 4751c883f4b27e8e34c0da1e195555ff71740fa1

On 16-02-13 13:28, Graham Inggs wrote: > The following commit has been merged in the master branch: > commit 4751c883f4b27e8e34c0da1e19ff71740fa1 > Author: Graham Inggs > Date: Sat Feb 16 14:27:33 2013 +0200 > > Split non-libs from libxm4 into libmotif-common > > diff --git a/debian/co

Re: [SCM] Motif widgetset library branch, master, updated. 4751c883f4b27e8e34c0da1e195555ff71740fa1

On 17-02-13 09:20, Paul Gevers wrote: > Why did you remove the Breaks/Replaces? libmrm4 contains files that used > to be in libmotif3/libmotif4, so I believe they are needed to prevent > co-installation. Hmm, I think I understand. As you removed all common files, these packages should no

Re: [SCM] Motif widgetset library branch, master, updated. 4751c883f4b27e8e34c0da1e195555ff71740fa1

On 17-02-13 09:39, Paul Gevers wrote: > On 17-02-13 09:20, Paul Gevers wrote: >> Why did you remove the Breaks/Replaces? libmrm4 contains files that used >> to be in libmotif3/libmotif4, so I believe they are needed to prevent >> co-installation. > > Hmm, I think I und

Re: [SCM] Motif widgetset library branch, master, updated. dbe3bee6ec58bdaa141c94c66e85205408dc7d42

On 17-02-13 18:33, Graham Inggs wrote: > The following commit has been merged in the master branch: > commit dbe3bee6ec58bdaa141c94c66e85205408dc7d42 > Author: Graham Inggs > Date: Sun Feb 17 19:32:23 2013 +0200 > > Make the Multi-Arch: same package libxm4 Provides: libmotif3/4 instead of

Re: [SCM] Motif widgetset library branch, master, updated. 10e3e364ae46c34cbb88cba0aecab1e053bca5fa

On 17-02-13 18:26, Graham Inggs wrote: > Hi Paul > > Why don't you think this is the proper solution? See below. > Previously, there were multiple libmotif4 packages, True. > it makes sense that there should be a transitional package for each > one. I think transitional packages don't have an

Re: [SCM] Motif widgetset library branch, master, updated. dbe3bee6ec58bdaa141c94c66e85205408dc7d42

On 17-02-13 19:16, Graham Inggs wrote: > Ah, I didn't notice that the transitional libmotif4 provided libmotif3. > I have removed that, because it is a transitional package it can be > uninstalled after the transition, but we still need to show that our > libxm4 (and libmrm4 and libuil4 and libmoti

Re: [SCM] Motif widgetset library branch, master, updated. dbe3bee6ec58bdaa141c94c66e85205408dc7d42

On 17-02-13 20:35, Paul Gevers wrote: > On 17-02-13 19:16, Graham Inggs wrote: >> Ah, I didn't notice that the transitional libmotif4 provided libmotif3. >> I have removed that, because it is a transitional package it can be >> uninstalled after the transition, but we s

Re: [SCM] Motif widgetset library branch, master, updated. dbe3bee6ec58bdaa141c94c66e85205408dc7d42

On 17-02-13 21:13, Graham Inggs wrote: > but libmrm4 > and libuil4 both depend on libxm4, I had completely missed that. You are right, they do. But this can not be seen from the control file, it is added by ${misc:Depends}, ${shlibs:Depends}. > which depends on libmotif-common and > libxm4 recomm

Re: [SCM] Motif widgetset library branch, master, updated. dbe3bee6ec58bdaa141c94c66e85205408dc7d42

On 17-02-13 21:54, Graham Inggs wrote: > I finally see what you were hinting at. The missing piece was above. But > indeed, because you can not guarantee that all three will be installed > if somebody installs a package that requires libmotif3/libmotif4, I > don't think this is the

Re: [SCM] Motif widgetset library branch, master, updated. dbe3bee6ec58bdaa141c94c66e85205408dc7d42

On 18-02-13 07:47, Graham Inggs wrote: > I propose that the 'Provides: libmotif3, libmotif4' line be removed from > d/control altogether: This sounds good. Will upload tonight. Paul signature.asc Description: OpenPGP digital signature

Motif 2.3.4-1 uploaded to Debian

On 18-02-13 08:23, Paul Gevers wrote: > On 18-02-13 07:47, Graham Inggs wrote: >> I propose that the 'Provides: libmotif3, libmotif4' line be removed from >> d/control altogether: > > This sounds good. Will upload tonight. The package is waiting in NEW for approva

Re: First motif commits

On 24-02-13 07:43, Graham Inggs wrote: > Recent changes (19 February) > > Hi, I just wanted to clear up a few things regarding the recent changes > I committed. Good. I probably would have asked about 2 specifically. 1. FTBFS on Ubuntu Raring: > I'd like to rename (sorry) the patch and come up

Re: First motif commits

On 25-02-13 09:38, Graham Inggs wrote: > It seems other distributions, e.g. Fedora are also switching to DSO > linking [2]. > It's probably worth combining my patch along with Ubuntu's > 0003_fix_ftbfs_binutils-gold.patch [3] and pushing it upstream. Sounds good. >> Additionally, I was wondering

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-12-g64986ea

On 08-03-13 18:47, Graham Inggs wrote: > Clean debian/system.mwmrc-menu after installing Graham, I prefer to do this by adding that file to a file called debian/clean. That way you don't have to override dh_clean. Paul signature.asc Description: OpenPGP digital signature

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-10-g5f4f0e2

On 08-03-13 12:48, Graham Inggs wrote: > +++ b/debian/mwm.install > -/etc/X11/mwm/system.mwmrc-menu > +debian/system.mwmrc-menu /etc/X11/mwm > +++ b/debian/rules > - cp -a clients/mwm/system.mwmrc debian/tmp/etc/X11/mwm/system.mwmrc-menu > + cp clients/mwm/system.mwmrc debian/system.mwmrc-

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-10-g5f4f0e2

On 08-03-13 12:48, Graham Inggs wrote: > Include custom Unity Greeter badge for MWM > diff --git a/debian/custom_mwm_badge.png b/debian/custom_mwm_badge.png > new file mode 100644 > index 000..cfc1703 > Binary files /dev/null and b/debian/custom_mwm_badge.png differ Where did you get this

Re: First motif commits

On 03/13/13 09:46, Graham Inggs wrote: > I've cleaned up some things, added copyright info for > custom_mwm_badge.png and updated the changelog. Good. Are you sure you own the complete copyright of that file? I.e. didn't somebody else have the original copyright? > Maybe ac_find_xft.m4 should be

Re: First motif commits

On 03/14/13 07:29, Graham Inggs wrote: > After asking that question I tried to do more reading up symbols, but > I found the information very vague, especially about (optional) > symbols. Out of interest, why are there so many other (optional) > symbols? How did you determine they were optional?

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-31-g912bcbf

Hi Graham, On 17-03-13 09:16, Graham Inggs wrote: > The following commit has been merged in the master branch: > commit 0450ba5184ed53ecf6330e0accdd727509a75d48 > +Comment: Created in GIMP using /usr/share/unity-greeter/unknown_badge.png, > + from Ubuntu's unity-greeter package (copyright 2012 Can

Re: [SCM] Motif widgetset library branch, master, updated. debian/2.3.4-1-31-g912bcbf

Hi Graham, Maybe I was unclear. See what I mean below. On 17-03-13 10:54, Graham Inggs wrote: > I understood that this was OK since the new license was 2+. > Or is the problem more about changing from GPL to LGPL? The latter. > By the way, you really should add Canonical to the copyright ho

Re: First motif commits

[Seems like the mail servers of Debian were out yesterday, sending again] Hi Graham, I have some questions in return. On 24-03-13 08:40, Graham Inggs wrote: > You wrote that you wouldn't upload 2.3.4-2 until 2.3.4-1 had been reviewed. > Is it possible to re-upload our current effort as 2.3.4-1 (

Fwd: Re: First commits in git repository on Alioth [ Was: Re: openmotif is now LGPL, retirement of lesstif in jessie?]

[Mail servers were out yesterday, forwarding to the list] Original Message Subject: Re: First commits in git repository on Alioth [ Was: Re: openmotif is now LGPL, retirement of lesstif in jessie?] Date: Sun, 24 Mar 2013 08:38:17 +0100 From: Paul Gevers To: BERTRAND Joël CC

Fwd: Motif

Sat, 6 Apr 2013 00:59:59 +0200 From: Luca Falavigna To: Paul Gevers Hi! I saw on the IRC logs you pinged me, but unfortunately I wasn't online, so I'm writing you by mail :) There's a nasty bug in dak, which prevents accepting a package if components are already available i

Re: Motif

Hi, On 06-04-13 14:30, Graham Inggs wrote: > I think it is very late now to try and get motif into Raring with it not > being in Debian. Get it, and thought so. > Paul: when you re-upload motif in NEW, will you go straight to 2.3.4-2, > or upload 2.3.4-1 again? > (or just to mix things up, uploa

Re: Motif

Hi Luca, On 06-04-13 00:59, Luca Falavigna wrote: > There's a nasty bug in dak, which prevents accepting a package if > components are already available in a different section, as happened > with motif, which shares libmotif-dev and libmotif4 with openmotif > package. > > The workaround for this

lesstif2 to motif transition

Hi release team, I like to get your opinion and advise on the following. Motif has been released with a free license last year, and I would like to move it from non-free (called openmotif) to Debian main. Its former free replacement lesstif2 is unsupported upstream and should be retired (in Debia

Re: lesstif2 to motif transition

Hi Graham, On 06-05-13 23:01, Paul Gevers wrote: > My proposal would be (with your approval) to just get motif into > unstable/main and start converting the dependencies with the help of > their maintainers (the libraries can coexist). Because the -dev package > name has to chan

Re: lesstif2 to motif transition

On 07-05-13 07:55, Graham Inggs wrote: > I think the testing went very well. As we suspected, most packages only > required changing the build-depends on lesstif2-dev to libmotif-dev. > There were a few that required the addition of libxt-dev and one or two > that required libxext-dev and libxp-d

Re: lesstif2 to motif transition

Hi RT, On 06-05-13 23:01, Paul Gevers wrote: > So my question basically is, what would be the most appropriate order to > do things? > > My proposal would be (with your approval) to just get motif into > unstable/main and start converting the dependencies with the help of >

proposal for the reverse depending buggy packages [Was: Re: lesstif2 to motif transition]

Hi Graham, Before we file bugs again the packages below I like to discuss the phrasing. Do you agree with the following? """ Hi Maintainer, Your package build depends on libxt-dev/XXX but does not declare this relation in the debian/control file. This is currently no problem as this is pulled in

Re: proposal for the reverse depending buggy packages [Was: Re: lesstif2 to motif transition]

> though. > > On 7 May 2013 21:56, Paul Gevers <mailto:elb...@debian.org>> wrote: > > > This is currently no problem as > this is pulled in by the lesstif2-dev package that you do depend on. > > > I would say "This is current not a problem as

Bug#707211: [ferret-vis] please build-depend on libxt-dev

Source: ferret-vis User: openmo...@packages.debian.org Usertags: lesstif2motif Version: 6.6.2-1.1 Severity: normal X-Debbugs-CC: openmo...@packages.debian.org Hi Maintainer, Your package build depends on libxt-dev but does not declare this relation in the debian/control file. This is currently no

Seems like the bug was not forwarded, oh well

Seems like the bug was not forwarded, oh well The first example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707211 I go now. Paul signature.asc Description: OpenPGP digital signature

Bug#707621: [hotswap] please build-depend on libxt-dev, libxext-dev, libxp-dev

Source: hotswap User: openmo...@packages.debian.org Usertags: lesstif2motif Version: 0.4.0-12 Severity: normal X-Debbugs-CC: openmo...@packages.debian.org Hi Maintainer, Your package build depends on libxt-dev, libxext-dev and libxp-dev but does not declare this relation in the debian/control fil

Bug#707623: [xtel] please build-depend on libxp-dev

Source: xtel User: openmo...@packages.debian.org Usertags: lesstif2motif Version: 3.3.0-14 Severity: normal X-Debbugs-CC: openmo...@packages.debian.org Hi Maintainer, Your package build depends on libxp-dev but does not declare this relation in the debian/control file. This is currently not a pro

Bug#708462: lesstif2 to motif transition

https://lists.debian.org/debian-release/2013/05/msg00161.html or 51881a33.6030...@debian.org I like to request a transition slot for lesstif2 to (open)motif. To keep current unstable build-able and installable, I propose the follow transition path: On 07-05-13 21:32, Paul Gevers wrote: >

Re: Motif

Hi Luca On 06-05-13 00:22, Luca Falavigna wrote: > 2013/5/5 Paul Gevers : >> As the release of wheezy has happened this weekend. Is it now a good >> time to follow up on the actions above? > > It should, yes. > Feel free to upload motif to unstable, then I'll take

Re: Motif

Hi Luca, [What would be the appropriate mail-list or bug-tracker for this discussion to happen in the open? Should I add it to the transition bug?] On 20-05-13 09:03, Luca Falavigna wrote: > 2013/5/18 Paul Gevers : >> While we are waiting for the release team to respond to my questions

Re: Motif

On 20-05-13 11:55, Luca Falavigna wrote: > I just checked, openmotif has only two rdeps, all of them in non-free, > and just for i386 and amd64 architectures. I don't think removing > openmotif from non-free and immediately accepting motif in main would > cause a lot of trouble for those two packag

Re: Motif

[Summary of previous mails: we are discussing how/when to move openmotif to motif]. On 23-05-13 08:43, Luca Falavigna wrote: > 2013/5/22 Paul Gevers : >> Ok. Then we just have to wait until the RT grants us a transition slot. >> Will keep you updated. > > I don't thin

Re: Motif

Hi Luca, On 23-05-13 08:43, Luca Falavigna wrote: > 2013/5/22 Paul Gevers : >> Ok. Then we just have to wait until the RT grants us a transition slot. >> Will keep you updated. > > I don't think we need it for openmotif -> motif, as long as motif is > ABI-comp

Motif FTBFS on non-linux due to YYSTYPE

Hi Graham, Congratulations... Now that we have motif in Debian/main, I would like to fix the fact that motif FTBFS on non-linux systems. That is needed if we want to replace lesstif2 as that is now available on more Debian platforms than motif. I think I know where it goes wrong (I have to check

Re: Motif FTBFS on non-linux due to YYSTYPE

Hmm, Maybe I was too quick, although I don't understand why it works now, but kfreebsd now builds with motif 2.3.4, where it didn't build with openmotif 2.3.3. https://buildd.debian.org/status/package.php?p=motif&suite=sid Paul On 25-05-13 17:47, Paul Gevers wrot

iswpace [was: Motif FTBFS on non-linux due to YYSTYPE]

Hi Graham, [Side note: maybe we can stop using the @packages.debian.org address, I don't think anybody else is listening.] On 25-05-13 21:08, Graham Inggs wrote: > Thanks for uploading! Thank you for the nice cooperation so far, it has been a pleasure. > I will file the bugs against the reverse

Re: Bug#708462: lesstif2 to motif transition

On 09-06-13 11:05, Paul Gevers wrote: > On 04-06-13 08:31, Julien Cristau wrote: >> Do we know how many of the lesstif2 reverse dependencies are libraries >> whose ABI would change if rebuilt with motif instead? > > No, but I can try to find out. The original idea of lesstif

Re: Bug#708462: lesstif2 to motif transition

On 10-06-13 22:32, Paul Gevers wrote: > My findings: > via (include/via.h): no diff > xmhtml (include/XmHTML/XmHTML.h): ABI/API is not compatible > > I did not succeed with the others yet for different reasons. > dx: I fail to configure it (not understood yet) dx: (include/dx/

Bug#123276: Bug: 123276 still present?

tag 123276 moreinfo thanks I am currently running through old bugs of nedit. Could you please tell me if this bug is still present in the latest version: 1:5.5-3? Kind regards, Paul signature.asc Description: OpenPGP digital signature

Bug#308635: Bug: 308635 still present?

tag 308635 moreinfo thanks I am currently running through old bugs of nedit. Could you please tell me if this bug is still present in the latest version: 1:5.5-3? Kind regards, Paul signature.asc Description: OpenPGP digital signature

Bug#369317: What news?

> It's now been over two years since the last response from the former > maintainer (?), and the bug is still present in Lenny. What does the > time line look like for a fix? Upstream is (slowly) working on a maintainer release. I am adopting nedit and have a beta of the new upstream release pres

Bug#482936: QA package available

Just for the record of this bug: I made a QA package which fixes this bug. It is available for checking/suggestions at mentors.d.n [1]. Paul [1]http://mentors.debian.net/cgi-bin/maintainer-packages?action=details;package=ssystem signature.asc Description: OpenPGP digital signature

Bug#805370: mpage licensing

Ping... As a QA maintained package which is not going into the upcoming release with a license issue open for 1.5 years, shouldn't this package be removed from Debian? Paul signature.asc Description: OpenPGP digital signature

Bug#953682: src:dosage: fails to migrate to testing for too long

Source: dosage Version: 2.15-2 Severity: serious Control: fixed -1 2.15-3 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and u

Bug#958224: libpam-alreadyloggedin: autopkgtest regression: module 'string' has no attribute 'lowercase'

Source: libpam-alreadyloggedin Version: 0.3-8 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libpam-alreadyloggedin the autopkgtest of libpam-alreadyloggedin fails in testing when that au

  1   2   >