Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "theme-d"
Package name : theme-d
Version : 1.1.7-1
Upstream Author : Tommi Höynälänmaa
URL : http://www.iki.fi/tohoyn/theme-d/
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "theme-d-gnome"
Package name : theme-d-gnome
Version : 0.7.0-1
Upstream Author : Tommi Höynälänmaa (tommi.hoynalan...@iki.fi)
URL : http://
Hi
How can I file a follow-up request to a RFS bug?
- Tommi Höynälänmaa
I got the term "follow-up request" from the following page:
https://mentors.debian.net/intro-maintainers
I says: "File a follow-up request to your existing
/sponsorship-requests/ pseudo-package."
Regards,
Tommi Höynälänmaa
sion : 1.1.7-1
> Upstream Author : Tommi Höynälänmaa
> URL : http://www.iki.fi/tohoyn/theme-d/
> License : GPL-3, LGPL-3, and GFDL-1.3
> Section : lisp
>
I'm filing a follow-up as it tells in the manual.
- Tommi Höynälänmaa
I have found a sponsor for my packages and hence RFS bugs #910604 and
#910663 may be closed. How is this done or do the mentors close them?
Regards,
Tommi Höynälänmaa
Hi
I'm building a package with sbuild and the package uses guile. Now I get
error messages like:
---
;;; compiling ../../theme-d/translator/theme-d-compiler.scm
;;; WARNING: compilation of
../../theme-d/translator/theme-d-compiler.scm failed:
;;; ERROR: failed to create path for auto-compile
I'm fixing the packaging of guile-cairo. I get the following warnings
and notes related to the VCS fields:
vcs-obsolete-in-debian-infrastructure, vcs-field-not-canonical, and
vcs-field-uses-insecure-uri. Shall I ignore these or remove the VCS
fields from debian/control?
-
ge on salsa? I am asking to see it try to help you
El mié., 12 de dic. de 2018 a la(s) 11:03, Tommi Höynälänmaa
(tommi.hoynalan...@gmail.com <mailto:tommi.hoynalan...@gmail.com>)
escribió:
I'm fixing the packaging of guile-cairo. I get the following warnings
and notes re
sa.debian.org/tohoyn-guest/theme-d-gnome.git
bb3d0ea..f64909b master -> master
c7f124b..a076860 pristine-tar -> pristine-tar
e149d42..992e02b upstream -> upstream
---cut here---
What kind of merges do these requests mean?
- Tommi Höynälänmaa
to do
so by B. Martens.
Could you check what is the situation of this package?
- Tommi Höynälänmaa
On 26.01.2019 17:24, Mattia Rizzolo wrote:
On Sat, Jan 26, 2019 at 04:…
That said, I could find no trace of your upload, so could you please try
uploading again?
Just done.
- Tommi Höynälänmaa
#BzvvY3zOqE9m86Joo23alsLXw4jrPmgMVIWJvxk2WmY=
The package contains the same file as my last upload to mentors.
- Tommi Höynälänmaa
dput. The method was probably https.
- Tommi Höynälänmaa
On 27.01.2019 17:54, Tommi Höynälänmaa wrote:
The package contains the same file as my last upload to mentors.
s/file/files/g
- Tommi Höynälänmaa
eme-d-gnome_0.7.5-2_amd64.buildinfo: done.
Uploading theme-d-gnome_0.7.5-2_amd64.changes: done.
Successfully uploaded packages.
---cut here---
- Tommi Höynälänmaa
ckage
once more so we can check that everything goes well?
Shall I update the .asc file, too? What about the orig.tar.gz file? Can
I just upload the .asc file with a separate dput command before or after
uploading the package?
- Tommi Höynälänmaa
I just made an upload with both orig.tar.gz and .asc files.
- Tommi Höynälänmaa
On 28.01.2019 10:10, Baptiste BEAUPLAT wrote:
I have to admit, I'm not sure.
Try to upload both so the upload works for sure.
On 1/28/19 8:55 AM, Tommi Höynälänmaa wrote:
Shall I update the .asc file
-Gnome (<< 0.8.2)" in the
debian/control file of Theme-D?
- Tommi Höynälänmaa
Hello
I have the following field in package theme-d-rte:
---
Depends: guile-2.2, guile-2.2-dev, libthemedsupport (= 1.4.1-1), th-
scheme-utilities (= 1.4.1-1)
---
Now dpkg still allows me to upgrade package libthemedsupport from
1.4.1-1 to version 1.4.1-2. Why is this so?
- Tommi
Actually the Depends field in debian/control is:
---
Depends: guile-${guile-version}, guile-${guile-version}-dev,
libthemedsupport (= ${binary:Version}),
th-scheme-utilities (= ${source:Version}),
${misc:Depends}
---
- Tommi Höynälänmaa
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "theme-d":
* Package name: theme-d
Version : 3.0.3-1
Upstream Author : Tommi Höynälänmaa
* URL : http://www.iki.fi/tohoyn/theme-d/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "theme-d-gnome":
* Package name: theme-d-gnome
Version : 0.9.4-1
Upstream Author : Tommi Höynälänmaa
* URL : http://www.iki.fi/tohoyn/theme-d-gnome/
WWW page https://wiki.debian.org/binNMU doesn't mention the case
arch:all package depending another arch:all package when it discussed
making packages binNMU safe. How is this case handled?
- Tommi Höynälänmaa
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E
I just want to ensure that my packages are binNMU safe.
- Tommi
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FM, Debian-ylläpitäjä / M.Sc., Debian Maintain
Hello
If the dependency graph of a binary package in the unstable distribution
is changed (e.g. because of the 64-bit time_t transition) shall the
binary package be rebuilt in the distribution?
- Tommi
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan
Hello
I'm maintaining a package having a direct dependency on a library
package changing name due to the t64 transition. Is it OK to upload a
new version of this package to Debian unstable?
- Tommi
Wookey kirjoitti 5.3.2024 klo 13.06:
Any package that has a direct dependency on a libr
guile. How can I
prevent the autoremoval of packages theme-d and theme-d-intr?
- Tommi Höynälänmaa
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FM, Debian
Hello
In https://wiki.debian.org/binNMU it says that declaring dependency
between an arch: all to an arch: any package should be done by "Depends:
foo (>= ${source:Version}), foo (<< ${source:Version}.1~)". What is the
purpose of the latter condition?
- Tommi Höynä
Hello
I accidentally uploaded package g-golf_0.8.0~rc5-2 to mentors. Could
someone delete this package from mentors?
- Tommi Höynälänmaa
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528
Sorry for the previous message. I deleted the package myself.
- Tommi Höynälänmaa
--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FT, Debian-ylläpitäjä / PhD
d for removal". Can somebody help me with this?
- Tommi Höynälänmaa
OpenPGP_0xBB861FDE40460F83.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Hello
The removal is OK now.
- Tommi
OpenPGP_0xBB861FDE40460F83.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
33 matches
Mail list logo
