Package: systemd
Followup-For: Bug #742322
Control: -1 tags moreinfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Is this the way systemd people generally respond to problem reports? Just
closing bugs and hide (possible) problems? I'm very disappointed. You know, in
Debian we do not hide probl
Package: systemd
Version: 204-8
Severity: grave
Justification: breaks other packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just upgraded from 204-7 to 204-8 and during the process all services which
needs to get restared fails to restart:
NOTE: I did *not* yet reboot; will check if
Package: libxapian22
Version: 1.2.17-1
Severity: serious
Justification: Policy 2.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
during testing of a script to check for Policy 2.5 requirments, I saw that
aptitude (priority important)
depends on libxapian22 (Prioity optional).
Quoting the
Package: libsqlite3-0
Severity: serious
Justification: Policy 2.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
during testing of a script to check for Policy 2.5 requirments, I saw that
aptitude (priority important)
depends on libsqlite3-0 (Prioity standard).
Quoting the policy:
Package
ne removal, at least of the original version (if the fork is not
affected)
- --
coldtobi
[1] (Sorry, German)
http://www.heise.de/newsticker/meldung/DNS-Server-des-CCC-Anfaellig-wegen-veralteter-Software-2112171.html
[2] http://www.your.org/dnscache/djbdns.pdf
- -- System Information:
Debi
Package: cubemap
Followup-For: Bug #737703
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Maybe this info helps:
I pedbuild' the pacakge sucessfully, then recreated the pbuilder enviorment
(pbuilder create) and then the build failed.
Attached are two logfiles,
cubemap_ok.txt -- the one which
Package: cubemap
Followup-For: Bug #737703
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear maintainer,
I tried to reproduce this on my local box in a chroot and using pdebuilder...
It built successfully here (amd64)...
So maybe this was some glitch in the buildd?
- -- System Information:
, but maybe this is an missing B-D.
- --
coldtobi
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8
nd in #701273)
Your response is appreciated, especially please let us know what your plans are.
Thanks for your contribution to Debian.
- --
coldtobi
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign
package from mentors is fine enough to just upload it?
(I did not check the quality of it, but at least it seems lintian clean)
Or this is a case where a NMU is justifiable?
After libwfmath1.0 entered unstable, this and all other related RC bugs
can be tackled.
- -- coldtobi
- -- System Inform
Package: bcrypt
Followup-For: Bug #700758
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I see two options:
1) Fix it
2) Remove it
1) Is probably out of scope (ends probably in a fork, breaks compatibiity...)
Maybe it should be removed from Debian? (I think we need to
maintain a certain level of
Package: abuse-lib
Followup-For: Bug #648272
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pinging
I agree with Markus, maybe the package should be removed from Debian?
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
A
Package: atlas-cpp
Followup-For: Bug #718711
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you are lack of a sponsor you should consider filing RFS bugs against
sponsorship-requests and actively searching for a new one...
- --
coldtobi
- -- System Information:
Debian Release: jessie/sid
packages (and in this case also the boost transition by the r-dependency
ember)
I intend to NMU this, but as I saw recent activity in your git repository, I
will delay this activities. (The bug is still present there)
- --
Best regards,
coldtobi
- -- System Information:
Debian Release: jessie/sid
to change the overrides.
Has already a bug filed against f.d.o to correct the override file?
coldtobi
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64
Package: libv8-i18n
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo,
libv8-i18n FTFS on armel/armhf.
This is RC as it previously built on armel.
(Also, this blocks the transistion of libv8)
coldtobi
Buildlog:
https://buildd.debian.org/status/fetch.php?pkg=libv8-i18n
Package: kumofs
Followup-For: Bug #666004
Dear maintainer,
Please note my intention to "NMU" this bug.
On April 3rd I will clone and reassign this bug to ftp.debian.org for a removal
request.
Best regards
Tobias Frost
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
AP
Package: src:sqlite3
Followup-For: Bug #665363
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raising severity to RC as this bug is blocking the transistion of
libtokyocabinet [1].
(As this bug is failing reason for bogofilter, which blocks the transition)
[1] http://release.debian.org/transiti
Package: bogofilter-sqlite
Followup-For: Bug #660717
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PS: Here's the complete buildlog using this commands:
(autoreconf; ./configure; make; make check) 2>&1 | tee -a
/tmp/bogofilter.buildlog
- -- System Information:
Debian Release: wheezy/sid
APT
Package: bogofilter-sqlite
Followup-For: Bug #660717
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PS: I tried to build this package on my amd64 machine,
and when I dpkg-buildpackage it fails,
but if I do just a
autoreconf; ./configure; make ; make check
the result is
==
Al
Package: bogofilter-sqlite
Followup-For: Bug #660717
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo,
is there any progress on this topic?
(I'm asking becasue bogofilter should be fixed ASAP due to the libtokyocabinet
transistion...)
Tobias
- -- System Information:
Debian Release: wheezy
Package: src:ruby-tokyocabinet
Followup-For: Bug #655860
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainers,
My idea was right. Only thing needed was to recompile against recent
libtokyocabinet.
I'll close this bug, feel free to reopen if you disagree.
Tobias
- -- System Informati
Package: python-gearman,python-gearman.libgearman
Followup-For: Bug #620469
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
attached is the patch to fix this issue I'm using for the NMU.
coldtobi
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy:
Package: src:gearman-interface
Severity: serious
Tags: patch
Justification: FTBFS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo,
as requested on debian-mentors, reporting and attaching this issue for the NMU
I'm currently preparing.
- -- System Information:
Debian Release: wheezy/sid
Package: gearman-interface
Followup-For: Bug #631820
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo,
as requested on debian-mentors, here is the patch used for the NMU
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing
Package: gearman-interface
Followup-For: Bug #631820
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo,
Ubuntu has a patch that works around this issue.
MAINTAINERS: PLEASE NOT THAT I AM INTENDING AN NMU
### I'm currently preparing an NMU. I will ask debian-mentors to upload this
into a dela
d.debian.org/status/fetch.php?pkg=haildb&arch=ia64&ver=2.3.2-1.1&stamp=1328018849
coldtobi
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: am
27 matches
Mail list logo
